DSXchange

put a transform stage right before your DB write stage, and add a reject link to that transform. This is the way to capture rejects in DataStage server jobs.

No, neither before-job nor after-job routines can do anything with stream data!

The BASIC function "EREPLACE()" will do this, but it does not exist in PX. What problems do you have with the BASIC transform stage at V8 - I have seen that it works quite well and no longer shows sporadic comms issues as it has in the past.

Krisna - those aren't naming conventions, but limitations from the product on what characters jobs can contain.

The output of the VLIST command are the internal opcode generated by compiling a BASIC program. The opcodes are only documented in an old internal use only document (I think I got my copy in 1984) and it is not for public use. But if you have ever used any assembler language then the output is prett...

If the other post doesn't help, look at an existing project and ignore all files with numbers in the filename.

What date format does your Sybase use?

Create a new project, then "cd" to the directory and do an "ls" from your UNIX shell and you will see a list of the hashed files used.

Are you writing this internal format date to Sybase? In that case, use assuming your Sybase default date format is "yyyy/mm/dd"

Dean - lol, perhaps I have been giving "them" too much credit.

These are DataStage hashed files; there is no schema and there is no method of accessing them apart from the TCL command (or the command line tool in the administrator)

Hello and welcome to DSXChange, Pavan. Using terms such as "urgent" or "ASAP" in posts counterproductive. Many of the frequent posters tend to ignore posts containing those magic words. If you need immediate support then you will have to use your service provider - and that is far pricier than joini...

string_trim is the conversion to use, i.e. NewCol=string_trim(OldCol)

If you change your target sequential file to have the path "/dev/null" does the error still occur?

Moderator - please move to PX Forum Does this .fifo file actually exist? These are named pipe files that are used to communicate between processes. If the file is still present and cannot be accessed, then most likely it is still in use by some process. You can use the "fuser -fux" command to deter...