DSXchange

Please don't post the same question in multiple forums.

The other post here, which I've responded to, for whatever that is worth:

http://www.dsxchange.com/viewtopic.php?t=117603

Define "wouldnt take". And if your example code is what you are actually using, you'd need to remove the quotes around the string to allow the parameter to substitute properly:

Best bet would be to move to the 'BP' subdirectory for job 6074 in its Project directory and check the 'JOB.554786582.DT.1469725302.TRANS1' file around line 810. See where in your job the error is coming from.

So far, yes... as long as there's no 'extended ascii' to worry about that is.

As noted, how would you do this without DataStage? The answer is the same with it.

So you are doing all of the XML manually? The XML Output stage will automatically do all of those replacements.

First suggestion would be to turn on email notifications (that option is at the bottom of the 'Post a reply' dialog) you'll get one every time a thread you've created or posted in is updated. Another option is to go to the Forum Index and use the 'View posts since last visit' link. We're missing a c...

My input date is in mm/dd/yyyy format... A general question: Does the date format need to be necessarily converted to YYYY-MM-DD format before applying any date functions using a routine... No. Where can I find the different format codes for the iconv and oconv functions? In the online help for eit...

I am trying to use this in a PX routine activity in the sequence... Not really any such thing as a 'PX routine activity'. There is the Routine Activity stage in a Sequence job, which has no 'PX' aspect to it and which runs routines written in DataStage BASIC. So, yes, you'd need to be able to code ...

sri75 wrote:I tries to get the value like this JOB1.$UserStatus but it is not returning the value from 1st job

Make sure "JOB1" is the name of the Job Activity stage that runs the job, the name of the actual job doesn't matter.

Welcome aboard, blue devil.

Short answer is 'no'. It's all about what's in the shared (or local) container, the fact that job components are in a shared container has no impact on performance.

Search for DSParams and you'll find this has been asked and answered before.

Depends. Where do you want it to start from?

There's no rule that says you have to have a even number of nodes. 1 is an odd number, after all. And the loneliest number, of course.

Depends on whom you ask. Some believe that all transformations should be done in the ETL. Others hold that it is OK to 'push' some of that work back into the database where possible, sometimes even all of it. I tend to fall more into the second camp as long as that push doesn't adversely impact its ...