Found this on the Forum some time back, how to delay 20 seconds via Self-Completing task predecessor; Haven't tried it myself but perhaps this may help you Loren? Delay a CA WA ESP job by nn seconds instead of nn minutes using the RELDELAY statement Summary: In some cases there needs to be a delay between the predecessor and successor job. The RELDELAY command only allows whole MINUTE values. By using a SELF COMPLETING TASK it IS possible to delay by SECONDS. Background: The RELDELAY x command only allows whole MINUTE values. Instructions: The self completing task in the example below sets the start time for the following job. JOB DELAYJOB TASK SELFCOMPLETING RUN DAILY ESPNOMSG AJ DELAYED.JOB RESET DELAYSUB('REALNOW + PLUS 20 SECONDS') APPL(%ESPAPPL..%ESPAPGEN) RELEASE ADD(DELAYED.JOB) ENDJOB JOB DELAYED.JOB RUN DAILY ENDJOB
This Email message and any attachment may contain information that is proprietary, legally privileged, confidential and/or subject to copyright belonging to Exelon Corporation or its affiliates ("Exelon"). This Email is intended solely for the use of the person(s) to which it is addressed. If you are not an intended recipient, or the employee or agent responsible for delivery of this Email to the intended recipient(s), you are hereby notified that any dissemination, distribution or copying of this Email is strictly prohibited. If you have received this message in error, please immediately notify the sender and permanently delete this Email and any copies. Exelon policies expressly prohibit employees from making defamatory or offensive statements and infringing any copyright or any other legal right by Email communication. Exelon will not accept any liability in respect of such communications. -EXCIP
Sorry about the triple send. It wasn't real obvious that Broadcom received my original 'send'
Thank you for the idea Michael. That is a possibility.The shortcoming for me of REALNOW is that REALNOW reflects the actual time of event trigger. Much of my organization's setup has the event being triggered to bring in an appl generation, but by design our appls do not begin until hours later. This allows us to review and adjust during our business day all the batch processing which won't begin until the evening.I have wanted for years for CA to provide a time delay relative to a job's predecessor job - not a time reference bound to when the event was triggered. JobA runs - wait twenty seconds - JobB runs - wait twenty seconds - JobC runs.For this simple design, the length of time is in relation to the predecessor jobDon't worry about the triple post. It feels like Broadcom has bugs to work out in their transition. I have a a great deal of trouble using Communities since the CA transition.