DSXchange

Hi,

I have gone through numerous posts for this issue but still not able to understand the cause for the following behavoir.

I have a master sequence which in turn calls a child sequence. I have 3 conditions for checking the completion of the child sequence and taking the required actions:
1. OK - Runs a post script to create files
2. DSJS.RUNOK or DSJS.RUNWARN to email some reject files
3. Otherwise - to send email notication that the child sequenec aborted.

This functionality works perfect for either cases when I run the Master job sequence manually. However, when I schedule the master sequence, and during an error - Both Master and child sequenec goes in a Aborted/Restartable stage, but I do not see the email notfication that the child sequenec has been aborted. There is no entry in the Master log about triggering the emailnotification activity at all..

This works perfectly fine when I start the entire sequenec manually.

Any thoughs/suggestions as to what am I missing.

Thanks in advance.

Navneet Mandhani

How are you 'scheduling' - via Director so cron? Is the scheduling being done under the same user as the manual run?

chulett wrote:How are you 'scheduling' - via Director so cron? Is the scheduling being done under the same user as the manual run? ...

Hi Chulett,

I am scheduling the jobs through director (DS Schedular). Its the same user id that I am using to schedule and run manually.

Please let me know if you need any additional information.

Thanks,
Navneet Mandhani

nmandhani wrote:

chulett wrote:How are you 'scheduling' - via Director so cron? Is the scheduling being done under the same user as the manual run? ...

Has anybody experienced this issue. Any thoughts or suggestions please...

Thanks
Navneet Mandhani

Sorry, I didn't reply back because I've never seen such a thing and honestly have no idea what may be causing it. How about you open a case with your official support provider and let us know what they say?

chulett wrote:Sorry, I didn't reply back because I've never seen such a thing and honestly have no idea what may be causing it. How about you open a case with your official support provider and let us know what they say?

Thanks for the response.
I opened a ticket with IBM support and they did not have any resolution for this. Looking into the design of my Master seq, I changed the abort on warnings limit to >1 and this helped solve the problem.

The only issue with this approach is that it leaves my master seq status as Finished(See Log) instead of Aborted/Restartable.

For now, this works fine. If anybody has a better solution please post here.

Thanks
Navneet Mandhani