Iterate through all job logs to identify those that finished in the last hour. To do this create a Select List of job names from DS_JOBS, get the job number of each, and use DSGetNewestLogId to get the "finished" message from each then DSGetLogEntry to read the detail of that entry. The timestamp ca...
You can't do it this way. You need a master controller that iteratively checks whether there are data to be processed and runs your main job sequence if there are, finishing when there are none.
The penultimate entry in a job sequence's log is "summary of sequence run". This may contain what you require. You can get this with the DSGetLog... functions.
Not necessarily. Someone else (DataStage or otherwise) may have been performing tasks that caused locks to exist on your target tables. This can also manifest itself as slow throughput, as the DataStage job spends a lot of time waiting for locks to be released. The clock ("per second") is still runn...
Can you have two separate links, one with an INSERT statement that lacks the timestamp column from its column list and VALUES list (used when null occurs) and the other that supplies a non-null timestamp?
FUNCTION FindIt(String, SearchString, Delimiter) $OPTIONS INFO.LOCATE * Make a copy of the string TestString = String * Convert delimiter into dynamic array delimiter Convert Delimiter To @FM In TestString * Search for search string returning field position Locate SearchString In TestString...
Read the manual about the Operator role. It can only see/run released jobs, and can not view all log entries unless this is explicitly enabled in the Administrator client.
I seriously doubt that the UniVerse decompiler will work with DataStage version 6.0 or later. There are traps in the object code to reflect that they are different products; code compiled on the one can not be executed on the other. You can visit Source Recovery Service to find out about the UniVers...
Yes, or CygWin or any other UNIX shell for Windows. Definitely worth having one. Of course, if you have one then you can use the UNIX shell scripting language, which is more flexible than BAT files. If you can get the "suppress line terminator" switch to work, then you wouldn't need tr.
Needing "x" permission to a directory higher up the pathname?
To use any directory in a pathname one requires at least "x" permission to that directory. To search a directory (for example if there are wildcards in intermediate directories in the pathname) also requires "r" permission.
However, unless you change the jobs referred to in the Job activities, they will still be the server jobs. There is no magic means by which jobs can automatically be migrated to parallel equivalents merely because you have installed Enterprise Edition.