DSXchange

Not at the moment. I'm working on a non-PX site. If it's there, by all means plug it in and use it.

This is actually what Craig said, if you re-read his post carefully.

Be very careful if using runtime column propagation. Propagated columns can not be traced using MetaStage, since there is no linkage between them and the table definition in the DataStage repository.

I posted such a routine earlier today. Search for ReadV

I have grave doubts that a Routine is what you want. From your - albeit incomplete - specification, I'd suggest an approach that sorts the input file then performs change detection via stage variables is more appropriate.

That's pretty horrible, since the Administrator client Command window does not have terminal formatting capability, and DS.TOOLS is a menu. Better is to establish a telnet connection to the DataStage server machine, connecting to the project in question. (On Windows, telnet is a DataStage service.) ...

The -jobstatus option is used as a suboption with the -run main option. The actual option you require is -jobinfo.

EventMessage is wrong. The message begins in field number 4, and may include backslashes. You want something like Field(Str, "\", 4, 999) Str was a poor choice of variable name, since it is also the name of an intrinsic function. Your code is horribly cumbersome. You process the lo...

If you want to do it in one Transformer stage you will find that the stage editor does not let you drag any column from the earlier reference input link to the second. Nor to build a reference key expression containing a column from that link. Nonetheless it is legal, but you must type the fully qua...

DataStage doesn't define data types at all. DataStage server jobs don't even use data types! When you imported the table definition, it was the database server that asserted "Binary". You will need to research exactly what this means. Only then can you reasonably expect to be able to convert the dat...

A re-hired employee using a previously allocated number would be an UPDATE instead of an INSERT. Use the sequence to generate keys only for INSERT. Otherwise, if you need to preserve history, then your table needs a new design, featuring a completely artificial key that contains no information whats...

You may like to convert both the search string and the main string to upper case, in order to perform a case-insensitive search.

Persistent data set control files conventionally have a ".ds" suffix.

It does something completely unnecessary to recover from a locked job; it sets a "read only" flag to 'NRO' when it was already 'NRO'! The long and short of your original problem is that you tried to take a copy of a job that was already open - whether in Designer, Manager or Director (Monitor) - or ...

Post a new thread. We don't hijack threads - it renders the search mechanism inefficient. Yours is an almost completely different requirement.