DSXchange

And crap, just like that not the answer you are looking for. Didn't notice you posted Server code in the PX forum, let's get you over into the right one and see how we can approach this with our old friends the 'Conv Brothers'.

Warning (pet peeve alert) but that is not a Julian date, which may explain your difficulty in finding the proper solution. From the docs: A Julian day specifies the date as the number of days from 4713 BCE January 1, 12:00 hours (noon) GMT What you are looking is called an ordinal date - the two dig...

Ah... I see our old friend Vincent is still hard at work over there.

Interesting, we're currently implementing Control-M at our site, I'll dig around and see if they can support that kind of triggering mechanism...

True that.

Silly it may be but I don't recall them ever adding the ability to parameterize the body of the email, unfortunately. Unless they've added that in more recent versions, the solution has been to take the DSSendMail routine and create a tweaked version of it to include that functionality.

Have the email sent to you and when you get it, press the button?

Somewhat facetious answer but may be the only one.

Can you post the parameter names involved, please, the ones controlling your two options? Just so we make sure we're all on the same page, terminology-wise.

It would help if you answered my question, provided us with details of exactly how your script works. Otherwise we may just have to stick with "Huh, that's odd".

Let's start by getting you in the actual QualityStage forum, hold on a sec... there you go.

How exactly is your script capturing the log details - using the various dsjob options? And specifically are you saying that all of the log messages for a particular job run were successfully extracted by your script except for those three? Records before and after were captured? If so, not sure how...

Seems to be a bit of a serial repeater.

Was going to mention that - the Director essentially uses a 'view' into the log table driven by each Invocation ID which makes it look like they are separate when in fact they are not. From what I recall, you can see them all mixed together if you look at the logs for the 'base' job in the Director....

True... and mentioned as the solution in the very first reply as well.

Ray, the SQL was just there as an example of how they would do it if a database was involved. One isn't. These are two files they need to work with.