DSXchange

If the hashed file was created in a project (account), use CREATE.FILE from within the DataStage environment. If the hashed file was created as a dynamic hashed file in a directory, use a recursive delete command (rm -rf in UNIX, DEL /S in Windows). This deletes the three files DATA.30, OVER.30 and ...

Better is to use the -export and -import options of FORMAT.CONV for the move. Or uvbackup and uvrestore commands.

Why don't you clean up the "variable not previously defined" messages from your two routines - it may be that these have caused invalid data to be sent to the SQLExecDirect function. If you're struggling with that, look for any path through the code that gets to the indicated line number without ass...

No. There is no per-project .odbc.ini file (by default). The uvodbc.config file in a project serves only to limit the DSNs that are accessible from that particular project.

ashishpascal wrote: the very function of Load pack is to Reduce the Transfer time.

Compared to what?

SAP is going to do an immense amount of validation of data being sent into it. DataStage sends data as fast as SAP is prepared to accept them.

What are the data types of the two columns mentioned, both in Oracle as as used in DataStage?

Select the required project, click the command button captioned Command

Assuredly.

1. Set the system clock back while the job is running.

2. Use a different parallel configuration file. Set APT_CONFIG_FILE to point to it.

You can't include "A" and "B" as values to be summed. DataStage substitutes zero, and probably logs a warning of the form "non-numeric where numeric required, zero used".

What version of Windows? DataStage 7.5x2 will not install on Windows NT, on Windows XP home, or on Windows Vista.

Do you already have your .NET C++ compiler installed? You'll need it.

Well, there's always a specific-to-purpose parallel routine that you could implement. What are the three possible formats? C should be fast enough to do range checks on the components. (I am getting above 15000 rows/sec through a server job Transformer stage using that IsValid function, and more usi...

Read your UniVerse/SQL help/manual for information about the ASSOC.WITH keyword.

In the calling sequence (A) you must explicitly handle the failure of the called sequences. In that way, the automatic handling (abort the controlling sequence) is pre-empted. Read the help on automatic handling in job sequences to learn how it works.

An after-job subroutine, or a routine or command (shell script) invoked from a job sequence, are the obvious choices. In either case you can pass a list of names of things to be deleted. Don't forget, in the case of dynamic hashed files, that you'll need a recursive deletion command.