DSXchange

That, too.

Not sure. Does it work if you use a dsx file rather than xml? Are the routine(s) read only?

I asked because, unless I was wrong back when I posted this:

chulett wrote:it seems that wasn't added until the 7.5.2 release

That would be a 'vertical pivot'.

Call DSUserstatus( Arg1:'|':Arg2) would be better. Then Field(job1.$UserStatus,'|',1,1) for Arg1 and Field(job1.$UserStatus,'|',2,1) for Arg2. When you put quotes around the Args they become a literal string.

I was thinking you were talking about PAE but that's actually for usage of more than 4GB of memory in a 32bit world. Not sure what patch you would be refering to... this would be a Windows patch or a DataStage patch?

Your "scratch" area, from what I recall.

The "Wait For File" stage does not support wildcards, so you'll need to "work around" that by building your own mechanism. I've coded this in the past as a shell script that loops / checks / sleeps over the X hour period needed, you can then use an Execute Command stage to run it.

Conditionally call DSLogFatal() ...with all of the consequences that brings.

As noted, it's an additional property you can add, just like any of the other additional properties. What version of DataStage do you have?

Have you used any of the native Oracle stages yet? They are configured in a different manner than ODBC. Do you have an Oracle client installed on your DataStage server?

You are very right and noted pretty much everything I did in my reply. However, the post is marked as 'Resolved', something I did after receiving a private message from the OP saying that everything now worked, so I don't think they'll be back to this thread.

It's an option in the Connector?

"I want to download them"? What do you mean by that?

synsog wrote:Our server is on AIX.

And yet your first post categorized it as a Windows server, hence the replies you received. I've corrected that.