DSXchange

Well... "uv" or "uvsh"? Not quite the same thing. What kind of actions are you trying to script?

Exactly. Do an exact search for "Controller problem: Unhandled failure" and you'll find this has been discussed ad nauseum here.

Search the forums for "CLOB", it has been discussed here quite a bit.

There's also the question of what version did you install? The only pre-8 version that will run PX jobs on Windows is 7.5x2 - yes, with an 'x'. Others will let you build but not run.

Right - either rebuild the hashed file with the proper keys, or investigate the use of the UV stage. The ability to use it to access an account-based hashed file with fewer keys has been discussed here quite a bit. Far easier to just build a new hashed file, however.

Both of those macros in filenames work fine for me - H-PUX, 7.5.1a, Server. Are you saying they don't work in PX jobs? Or are you saying that your flavor of UNIX does not allow the colons in the filename?

I'm unsure why, assuming you've already made the checks, you don't use the syntax you posted? Your 'if-then-else' construct is perfectly valid and if that's really what you need, use it as the derivation.

Direct path sqlldr is non-transactional. However, a 'conventional' (DIRECT=FALSE) sqlldr load is.

Yes, you can add an "ascii" command just before the get and it will convert the file to UNIX record terminators during the transfer. Or you can do what you are doing and simply tell DataStage that you're reading a DOS file, one that has CR/LF pairs as record terminators. As to understandin...

I should have been more specific. I was wondering what about the job itself, not the data sets, would be cleaned up... since you mentioned both. But that's not important if the question is strictly in regards to 'temporary' datasets and if they're removed after the job runs. As to your eye-rolling D...

'Clean up'?

'Echo' is a command to write to the screen whatever information comes next, it doesn't run anything. Get rid of it, then see what happens.

I think it can change based on the architecture. For the PA-RISC based 11i Superdomes here it is $SHLIB_PATH... but I seem to recall that the Itanium boxes use $LD_LIBRARY_PATH.