DSXchange

You don't need the function if the environment variable is already being passed in as a job parameter. And the function is expecting a literal, so enclose it in quotes to get the red out.

While I believe you can regen with the engine running, I never do. You will need to bounce the 'service' for it to see the changes, one way or the other.

Are you on AIX by any chance? How many jobs is "a lot"?

Do not include the dollar sign with GetEnvironment(), it assumes that part and just wants the actual name of the variable.

1. Seeing as how you need to shut down DataStage to regen, it will get 'bounced' in the process.

2. Yes.

Ah... appended to each record, almost missed that part. If you wanted to work outside of a job, this could be done in shell script. Seems like you could pick up the one record with a Lookup using a 'hard coded' key value as well.

File Patterns are a source option, not a target option... reads, not writes.

Yes, with some confused cross-talk but maybe that was just me.

Don't forget the pink hearts, yellow moons, orange stars and green clovers!

(sorry, move along, nothing to see here)

Assuming you don't know what it is currently, have root change it from the command line using "passwd".

Hard to say unless you post the actual error. Your db supports if-then-else constructs?

Sure... www.google.com with a suggested search string of 'sqlldr control file'.

A limit of zero means 'no limit' so you'd need to set it to 1, and dsjob will default to 50 unless overriden with the -warn option. And it is a warning limit, a fatal will still kill ya dead.

It creates everything for you... and there's no persistent 'data file' in the traditional sense, it uses a fifo pipe instead.

Right... you can check but it will always show 'Running'. Bigger problem there is trying to issue an attach to yourself, that will hang - so make sure your list of job names does not include the checking job.