DSXchange

If you are paying an official support provider they are obliged to help you.

DSXchange is an all-volunteer site which, among other things, means that there can be no compulsion. Members post as, when and if they can.

Typically (depending on stage type) there is an explicit entry showing the SQL that was executed. "Query" the log by finding that entry.

Yes, several.

There is a SLEEP command (argument in seconds or as HH:MM (24 hour clock)).

There are statements SLEEP (argument in seconds) and NAP (argument in milliseconds) that you can use in a server routine.

You have access to the operating system sleep command by various means.

Probably wrong. At least not for that reason. The before SQL is executed on the same connection as the main part of the stage.

How about this one?

You have specified a field delimiter but it's not found. The first line of your file appears to contain - or at least to begin with - "COLUMN_NAME". Perhaps your column headings are not correctly delimited, not correctly quoted, etc.

Join to a generated data stream containing 1, 2, 3, 4, 5. Use a left outer join, with the generated data being the left input. Convert the null to a zero.

Then please prove to us that the shell variables all have values assigned.

Arnd asked you to tell us what is in the job log when you run the job from the dsjob command. You have not yet done so.

Only by running the job from the after-job subroutine without waiting for the second job to finish. But we still have no idea why you want to do this.

So what ARE you getting?
A funnel should produce the results you expect.

No, but you can use the DataStage macro DSJobName or the DataStage function DSGetJobInfo(DSJ.ME, DSJ.JOBNAME).

Officially (in any form of database query) joining on NULL is not permitted. For the purposes of the join, you can create a new column containing a particular value (an "in-band null") if your "join key" is null, and the actual value otherwise. Use these created columns to effect...

The step at which it's hanging appears to be reading your licensing XML file. Did you give it the correct location for that file?

I'm surprised that it's hanging at this point - I would have expected a fatal error to be thrown.

Does your PATH include the parent directory of osh executable? If not you need either to include it or to use the full pathname of osh. Standard operating system stuff.