DSXchange

As noted, use whatever path is appropriate - i.e. fully path it starting from the drive letter.

Sorry, but you've posted this in a completely inappropriate forum. Please repost it in the "EE" or Enterprise Edition forum. Thanks.

*Note: Topic Relocated - Content Editor*

This isn't a "DataStage server" thing but rather a "Windows server" thing. Surely you have people looking after the box itself, operating sytem, etc etc?

Perhaps. Note that this is a Server answer, in which the OCI stage allows multiple inputs, it just means they must all connect to the same instance. PX doesn't allow it, however.

Of course you can use a single stage, it's a single link you can't use. Just create a link for each combination needed and send your data down the correct one.

I'd check with a SysAdmin what "Client was not authenticated" might mean. Does your user have the permissions it would need for this?

nagarjuna wrote:No craig ....I am using a parallel job .But , i took pivot stage from the folder server type .As far as i know , we have only one pivot stage in 8.0.1 .

That could very well be your problem right there. Do double-check.

So, those settings might be bad only on Tuesdays?

For these symptoms, I would say it is definitely other things running on that day. Just because you haven't found any doesn't mean they're not there.

That is the typical way that an 'unknown' character is displayed - it can mean 'I have no idea what this character really should be'. Kind of like us shrugging our shoulders.

Well... if they actually have the Enterprise Edition on Windows, then the MKS Toolkit is installed and UNIX scripts can be created and leveraged.

No clue where a UNIX script would come into play here. For the DataStage solution your derivation is incomplete. It should be more like: If (your null tests) And svFoundNulls = 0 Then 1 Else svFoundNulls This assumes your stage variable is called svFoundNulls and was set to an Initial Value of 0. Th...

And "LOOP" here means what, exactly? A Sequence job with the Start/End Loop stages? The loop counter is auto incremented, so it sounds like a setup issue but without details it's impossible to say.

You don't need a routine, just use ExecDOS after job and issue the del command from there, which is the DOS 'delete file' command.

This "?" you are seeing - is it a true question mark from the source or just the first symptom of a character set conversion error?

Welcome aboard. For something that old (assuming the MVS version is the same Server version that I think it is) you should be talking to IBM / your official support provider about this transition and how supported it may or may not be. I'd be surprised if anyone here has faced the same situation, bu...