DSXchange

Odd... I didn't think it was possible to not have that pointer to $DSHOME on a UNIX system.

Can you simply do a "cd $DSHOME" instead? All you are trying to do is get to the DSEngine directory so that you can 'source' the dsenv file to properly initialize your environment for dsjob.

There's a space between the "t" and the "/":

Talk to your DataStage admin. If it was installed, the stages would be showing up for you, so I'll wager it has not been.

There's a Server component that needs to be installed as well, from what I recall.

kondeti - that's not a "workaround", that is the answer. Constrain your output to only the lookup rows that succeeded = inner join.

Then everyone was in fact not out of the project and the REINDEX failed. You should try again.

In other words, all child jobs inherit the parent job's warning limit when run via the Job Activity stage in a Sequence. Is that what you want to happen?

You have to use a real job name, not literally 'JOBNAME' in the select.

Two suggestions: 1) You start using better thread subjects rather than your "anyone" pleas. Of course, there are all kinds of "anyones" that can help with or look into issues here, that's the whole point of our existence. 2) 'Details' regarding RCP can be had by reading the documentation. Then come ...

ray.wurlod wrote:Prove (perhaps using echo commands) that all the environment variables you have specified on the command line actually have values assigned.

Rather than worrying about the "-server" bit, suggest you answer this instead.

Why convert everything to PX? Continue to use a Server job for the first part. USERSTATUS is only supported in PX using a BASIC Transformer.

So is this being purposefully obfuscated?

You don't approach this at all, in my opinion. You hand this requirement to your AutoSys folks and tell them when it needs to run. Their problem, not yours.

So... where are we at with this? I don't see a question in your latest post, so not sure if you have a direction, the answers you need...

Exactly - two things will typically generate that 'invalid character' error in Oracle: a semi-colon or untranslated job parameters.