DSXchange

OK... you could extend that portion of the code where it logs the names of the jobs that aborted and, in addition to that, send the same information out in an email using the DSSendMail routine. The list could go into the email body or optionally to a file and included as an attachment.

Assuming that last "unpacked" should say "packed"... no, not as far as I know. Happy for someone to prove me wrong, however.

No clue, you'd have to explain what your "Master_Run_Utility" is... a Sequence job? If it is, would you be allowed to add this notification to it or would it need to be something separate?

Once they're "unpacked" then sure, those functions should work fine.

True, but not knowing what is going on inside the routine... could be passing back DSExecute output for all we know.

Routine output is a dynamic array and so, depending on how you built the returned value, you may need to remove "field marks" from the output before you check for your value. For example: Convert(@FM,"",RA1.$ReturnValue) = 0 Or try referencing only the first element of the array:...

Those functions are expecting ASCII data, AFAIK, so you'd need to convert the field to use them. These aren't packed fields, are they?

To use it in a routine you need to add the appropriate "include" statement:

No such option in the Server sort stage, checking and removing duplicates would need to happen downstream from the Sort.

What's unclear about that? For UNIX rather than DOS, use "cat". And in DOS you can use "type" as well.

Then why is it marked as resolved?

So, are you not passing these values to the routine? Instead, you want to lookup the job parameter values from the job that is calling the routine? That's quite different than what you originally posted.

Server not PX job, so no "Col Gen" stage and a UNIX server so no ExecDOS or "copy" command, guys. This is an easy problem to solve and I posted a complete solution. Sure, you can cat in the Filter if you like rather than before job but I find that problematic at times and harder ...

Meaning, you must be sitting in the project directory when you run this. That and know what all the variables are that it is expecting, like what !CommandeDS! is.

The OP has yet to post anything that looks like the actual start and end times of the jobs in question but rather has posted routine messages ("Dataset .. is deleted" ??) instead. I wouldn't make any judgments on what starts when until we see that. And we're just looking for a simple list:...

Yes, a "batch file" would be a DOS script file, one with an extension of ".bat" that you would run from the command line of a Windows PC.