Then modify that trigger.
I'm suspecting this is a standard program that launches another and as such the OP has little control over it without going down the customisation route.
It might be a bit overkill but you could always put the child program on a separate concurrent manager and either don't start that manager or have a schedule as you require (i.e. is it that you want the job to kick off at a later time? If so just have the manager shifts set up to do that).
Correct it is standard program that gets launched.
how do we put it in a separate conc manager?
Yes i want the job to kick off at a later time
1 person found this helpful
Again, this might be overkill for a single program, however....
This can all be done through the System Administrator responsibility - Concurrent -> Manager... menu.
1) You would need to first define the schedule for your concurrent manager, and then define the manager.
2) You would add a specialization rule to the new manager to include the program.
3) You would add a specialization rule to the standard manager to exclude the program.
4) Start the new manager.
Steps 2 and 3 above are both done on the define manager screen.
Will try this approach