DSXchange

1. But there will be a warning logged which you can detect.

2. Either - you can limit the date range of the search.

You need double quotes and single quotes within the SQL command's syntax, therefore you need to surround the command itself with the third quote character - backslash. DQUOTE() yields double quote characters, which are used in the EVAL. cmd = \SELECT DS_JOBS.NAME AS JOB_NAME, \ cmd := \ EVAL DS_JOBO...

You can call other subroutines from your own after-job subroutines. Write one that calls the two. You need a "DSU." prefix.

handle_null() is apposite for any data type. The replacement value must be a constant, and compatible with the data type.

Actually there are some bugs in the DataStage Windows scheduler interface.

You can submit dsjob commands via AT. Search the forum or manuals for dsjob, and type AT /? for the syntax of the AT command.

If you insist upon using DataStage you can write a server routine and invoke it from a job sequence. The STATUS statement can report the date and time a file was created, modified and accessed.

Welcome aboard.

Can't see any reason why not. Have you tried it?

Director also has RT_CONFIGnnn and RT_STATUSnnn open for the currently selected job, and DS_JOBS and its CATEGORY index.

1. Three times, unless you use public shared cache.
2. Public shared cache requires some uvconfig parameters to be set, and that's how it knows.

A Stop request is just that, a request, to be processed by the job next time it pays attention to its RT_CONFIG table. There is no such thing as an immediate stop.

The job may indeed finish before it gets around (would have gotten around) to handling the stop request.

Report the bug in MJC to IBM. In the meantime you have your workaround; compile the job sequence separately.

1. Check the "log warning (in sequence) if activity does not finish successfully".
2. Scan the log with DSGetNewestLogId() looking for warnings or fatals.

Welcome aboard. Are you working in a European locale (as set in Windows and/or DataStage)?

TimestampToString, StringToDate, DateToString - what data type is your output column (date or string)?

Pass through the five columns. Mark ColumnA as Key (which will get it into the WHERE clause). The generated SQL should then be:
which should work.