DSXchange

COMMAND: dump [ -options... ] descriptor-files... Dump the specified ORCHESTRATE parallel files as text to the standard output. If no options are specified, all records are dumped in order from the first record of the first partition to the last record of the last partition. Each field value is fol...

try "save as" of your job sequence under a completely different name, compiling and running it - do you get the same problem?

No, there is not one specific cause for this error, there are many. Without additional information no further analysis is possible.

(Unless the "RMM" [read-my-mind] stage that is being developed here on DSXChange has gone past the development phase )

Use a loop in your shell script, the first call gets the list of jobs in a project with "dsjob -ljobs", then loop through the call for each job found.

I just realized that the shell used by DataStage is determined by the uvconfig file setting of SHDISPATCH. Just a fyi.

Are you 100% certain that in the Job Activity stage you don't have "validate" set and that you've recompiled the sequence since making any changes?

sharma wrote:I...and getting problem while compiling my C++ code...

That doesn't give anyone any information to help solve your problem.

The only ways are by using a DataStage job or "orchadmin dump"

balu356 - Ray suggested you use the Search to find the many threads that deal with this question of vertical pivoting. If you search those threads and don't find the information you are seeking then please ask on this thread.

Spring,

that sounds like a good idea. What is your problem or question?

There is no supported method to rename jobs in DataStage from the command line. At V7 the job name is stored in a hashed file called DS_JOBS as well as in hashed file DS_JOBOBJECTS. Both need to be changed. Making a mistake on either file might destroy the project and require a restore.

I'm not sure that the OP is doing that - calling the preferred shell from whatever shell DataStage opens.

The execute command SH calls up "/bin/sh"

How about using RawToHex('Hello') in your SQL, does that work?

It can be done, but could you give an example, i.e. what should the strings "Hello" and "123" look like in Hex?