DSXchange

the orchestrate command "orchdbutil" is not normally called by users. It is called as part of the generated scripts that are run by DataStage jobs. You can call up "orchdbutil" from the command line to see the options, but be aware that it depends upon other settings and parameters as well.

What kind of a file are you writing to? If a text file then your output will be "display" format and not internal format.

Have you identified what your performance bottleneck for this job is?

The script can write straight to a sequential file by you cannot do that to a dataset. If you need to write into a dataset then you should do everything in a job DB2 -> DataSet.

What happens when you try to compile the jobs in Testing? Perhaps all you need to do is use the multiple job compile option on all imported jobs.

Why are you asking twice? And since the OCONV() function doesn't exist in Parallel Extender/PX this is the wrong forum to post the question in.

I think the best stage to use is Modify, since this is precisely what it was designed for. Although a copy stage can do it, I prefer not to use it - but that is more a matter of personal taste than anything else.

BIuser - that is simple in Server, it is Oconv(@date-1,'D-YMD[4,2,2]')

Naveen,

what have you tried so far?

p.s. "ur" and "u" are not valid forms of "your" and "you"; this isn't an SMS site.

I fully agree with the documentation of the modify stage being less than helpful and, in some cases, it is outright wrong! I finally gave up using a modify stage for a job yesterday since no matter what I tried I was getting warnings and ended up using a transform stage for expediency. In your case ...

Yes, it is possible. I am not going to ask you why you aren't doing this in a DataStage job as you have hopefully thought of that.

You can execute a shell program and do your DB2 connect and query routines from there.

Priyadarshi - this is a reject link he is asking about, where the attributes cannot be changed.

These internal tables (actually, hashed files) are not officially documented anywhere. If you look thorugh this site you will find some references and descriptions - more than you would get from Ascential/IBM.

In your after-job subroutine you need to do the following calls for each of the other files (4,5,6 7,8,9)

DSAttachJob(),
DSGetLinkLinkInfo(Handle,{StageName}, {LinkName}, DSJ.LINKROWCOUNT),
DSDetachJob()

For Job A you don't need to do a DSAttachJob() or DSDetachJob(), just use DSJ.ME

Is there no more output at all as to why this error is happening? Try doing a "reset" and see if you have a log entry "from previous run", this might contain the reason that the batch is failing.

Put a Transform or Modify stage at the end of the output reject link so you can change the column metadata and values as described by dspxlearn.