DSXchange

From the job sequence's log, for example from the "job run requested" event.

Use a job parameter for the entire SQL statement. Mark the SQL type "user defined".

Use an Execute Command activity to read the file and pass the output of that command, stripped of line terminators (or equivalents) as the value for the job parameter.

What you most recently propose is not possible.

There's no workaround of which I am aware. Switch to Windows 2003 Server (or, if you must, Windows XP pro).

Procedural Note We don't do "urgent". If you want urgent support sign up for premium service from your support provider, and learn the true cost of "urgent". DSXchange is an all-volunteer site; people post as and when they can. Tell us how you propose to do this in DataStage TX. If it really is a s...

Do you mean in the Palette or in the Stage Types category?
The Palette is fully customizable.

In short, the answer to the second question is "no".

You can use the DataStage API functions (such as DSGetJobInfo) in before/after job subroutines in parallel jobs.

One way is to use a single ODBC stage, with one input link for each table, and then you will find a tab called Transaction Management where you can group all as a single transaction.

Welcome aboard.

Run the first job. Then have an Execute Command activity read (cat) the file. Capture the output and extract the field containing the value in a custom trigger that determines whether the second job runs.

I would strongly advise that you take an entry level DataStage (Enterprise Edition) class, based on the knowledge level manifested in your question.

Yes, unless the middle fifteen don't do anything in particular, in which case replace those with "the one sequence to rule them all".

Please post two things:

the value of the File property in the Sequential File stage (that is, the pathname copied/pasted from the job design)

an ls -l listing of that pathname from UNIX