DSXchange

You might like to put Nested Condition activities immediately after the Sequencer to make the decision about whether to run each particular downstream job, perhaps based on an activity variable from one or more of the upstream activities.

This message can indicate that indexing in the DataStage Repository has become out of synch. When you can get exclusive access to the project, execute the DS.REINDEX ALL command (through the Administrator client Command window perhaps) and service is likely to resume.

Before-after subroutines can not be tested in the routines editor.

In UNIX ren is meaningless, except as something to do with stimpy (these were a pair of hostnames at one of my client sites).

Greg's sample data are all upper-case, but this might be a valid point if the sort were case sensitive and he advised the Aggregator otherwise.

Can you add either -wait or -jobstatus to the dsjob command, to make it synchronous? Check also that all the environment variables referred to have properly been set. If not, your dsjob command will have a syntax error.

Seems to be related to that other SQL Server idiosyncracy, the GUID (guaranteed unique ID). Can you ask your DBA whether it's the same? (I'm just curious, having solved GUID issues with DataStage in the past. You can search the forum for those solutions.)

Seems to be related to that other SQL Server idiosyncracy, the GUID (guaranteed unique ID). Can you ask your DBA whether it's the same? (I'm just curious, having solved GUID issues with DataStage in the past. You can search the forum for those solutions.)

The answer is in two parts - the operating system permissions and the DataStage roles. Other posters have addressed the first; you check the Permissions tab in the Administrator client to view the second.

Part of which is "less than US$1 per week".

(There are also corporate premum memberships available that discount this even further!)

Buy now! Send money, for free receipt!

This is NOT a recursive lookup. You do a lookup, the lookup does not succeed, so you write a new record into the hashed file. The next lookup attempt does not occur until you are processing the next row. It is not recursive. In the job design, the link that performs the lookup should have read cache...

Hi, I need to call a Routine in the Before-Job Subroutine to create the hashfile,if it does not exists in the specified path.If exists then dont need to do any thing. Planning to pass hashfilename as a parameters to the routine. Only one column need to be in the hashfile with data type Char(100). n...

You can't believe me, believe me!

No you are not doing anything wrong, this is one of those strange behaviours of DataStage. If you run the job, and retrieve the parameter values afterwards with DSJ.PARAMVALUE, you will get back what you set. But, until the job has run, you do not. It is sufficient, in your case, to test the value r...

No, he means parallel Transformer. The binary ("object") code produced by your C++ compiler is almost certainly not portable to other platforms.

Of course, with nearly a year gone by, Rachana may no longer be there.