DSXchange

I had completely forgotten about that! Much easier, and caters for any file sizes as well. Thanks!

The dump is coming from the Transform stage, not the bulk load stage. If you put a constraint "1=2" in the transform so that no rows are passed to the ORA passive stage does the error still occur?

Stage variables are computed for each row; so there is no additional looping possible with them use in the normal way. Since a sequential file is in reality just a long string with one or two special characters that denote new lines (either <cr> or <cr><lf>) you could always put together your own st...

If you have a multi-cpu SMP system then by all means use IPC stages and also set interprocess row buffering in your job properties. This will not make a huge difference as the I/O to both sequential and Hashed files does not consume as much CPU time as your transform computations.

Since your source file has nothing at all to do with the output file why not approach the matter differently. Take a dummy source file with more rows than you want to generate and read it in a simple job. Ignore any columns from that source file, in your transform stage just set the output column va...

Anji,

what is your question?

If you have a dummy file or any file for that matter, you could use a DataStage job with a single transform stage that uses the internal value @INROWNUM to generate a sequence of values to be written to the output file.

Hashed files are unlike SQL tables in that the DDL is completely disassociated from the data itself. The first field of the the record in this file does contain the key value you are looking for, but the DICTionary of that hashed file just doesn't contain a reference to it.

Thiru, please be aware that normally post with "urgent" and "asap" are handled with lower priority in this forum. If you have a service provider you can go to them and expect quick turnaround, but DSXchange is a community of volunteers. The question you have asked has been posed before and is also o...

It timed out after exactly 1 minute... Were the DataStage machine or the FTP target machine exceptionally busy when you tried this?

In the BASIC interface you can use DSGetLinkInfo() to get the number of rows passed through any link in a job; so you can get some of your required data there. The normal log file entries will also, for some stage types, list the number of update/inserts executed and you can retrieve and parse that ...

DataStage 7.5.1a has bugs. So does 7.1. Some of the 7.1 bugs are fixed at 7.5.1a and some of them are new. Most migrations from 7.1 up to 7.5.1a are easy and cause no problems. Sometimes small differences have been shown to be bothersome, but nothing insurmountable and no reason not to upgrade if yo...

The way you have the BASIC coded will open and overwrite (potentially only partially overwrite) the sequential file. The statement "WEOFSEQ {FilePtrVariable}" will truncate a file at the current position, and the statement "SEEK {FilePtrVariable},0,2" to position the file pointer to offset 0 relativ...

IPC was added to explicitly allow a job to be split into several processes for performance purposes.

nasimul,

I guess I shouldn't have asked the question since it won't solve your problem. It might help narrow down your problem of the job not finding the dataset descriptor file where it expects, though. Good luck.

You are getting a UNIX error. The environment variable you are referencing with "${DSBINDIR}" is empty in your script so it is looking for the dsjob program in the root directory. It might be better to use either $DSHOME if you have it set or resort to using "`cat /.dshome`/bin"