DSXchange

No need to email anything, just copy/paste it (or a representative sample) here wrapped in Code tags. And it doesn't seem like formatting is the cause of your validation failure - it is telling you that 'ABS' is not a valid enumerated value for the bus-unit element. So, the first question is - is it...

Then it seems your requirement is flawed. Either switch to using $PROJDEF in the job and let us know if THAT works or open a support case with IBM. Ask them what the heck is going on.

Hmmm... turning it off gives you one long continous line of XML, there should be no formatting at all. And what you have now looks more like what formatting on should look like. Your original has too much white space / returns in it. Which makes me wonder if your issue isn't data related. Can you tr...

Turn off the formatted ouput option. It's not needed and the 'formatting' that option does is... odd.

Yes.

pravin1581 wrote:Do we need to use -local option as well in the dsjob command.

Could be, try it both ways and let us know.

What? $PROJDEF is 'job only' but $UNSET and $ENV are perfectly valid for use in the Administrator.

[shrug] Common widget, I assume.

Well... for me, it's a personal preference, so no.

Or land the value and then cat it into the Initial Value of a stage variable. Depends on where you need to use it in your job, it will need to be a job parameter to use in source SQL but a stage variable can be used without needing a Sequence (or other job control) to arrange the passing of same.

He means in the job, not in the database, in an effort to work around the simple fact that BLOBs are not officially supported. What datatype are you currently using?

Well... you know what the first question is going to be. What changed? Anything that you are aware of, O/S or Oracle-wise, on your DataStage server? Patches, upgrade of the Oracle client, etc etc.

Consider a 'Multi Instance' job if you'd like to run multiple 'plants' simultaneously, which could serve as the InvocationID. You would then use the DSJobInvocationId macro in place of the job parameter.

We're going around in circles here. If "the requirement" is to set the job's default value to $ENV then the proper value must exist in the environment before the job is started. You don't pass anything to it on the command line. So why not try setting the environment variable to the proper value in...

D'oh!

dodda wrote:but when i Run the DAta Stage Job i am Ending up With Error.

Please Post the Actual Error.