If you really do want a loop where you get a sequence of A, B, A, B, A, B, and so on, starting every hour or so, then you need to have one job control the cycle. The other job's cycle could be 0, 5, 10 but it doesn't really matter as it is less than that of the 'controlling job. And yes, I did say i...

Firstly, you should know that any cyclic job is set automatically back to wait condition after it completes, assuming that there are no limits on the number of runs or you haven't processed a 'stop cyclic' command, or something else similar. I don't completely understand your need as I am not sure i...

The adhoc nature of job is all related to the scheduling. If you wish to create an adhoc job or table you can do two things: (1) Do not schedule the job - so that it needs to be ordered manually. This is done in the Scheduling tab of the job definition. (2) Leave the user daily field in the table bl...

It seems to me that you have two jobs and only one of them is cyclic. If you wish the first job to continue to trigger the second job, then you need the second one to be cyclic as well. But you need to be more careful as you don't want the second job to just run on its scheduled time. Are you just w...

You can avoid the relatively complex ctmpsm command by doing the following: (1) Make all jobs cyclic. (2) Give the first job an interval of 60 minutes. This is the 'controlling job' (3) Give every other job an interval of 5 minutes (the exact interval doesn't really matter as they won't run until th...

Hubba, You are definitely missing something here. According to what you are saying, there is nothing that you need to do (except ensure that the max wait on each job is long enough to ensure that they remain in the AJF for long enough). They are both scheduled on the same day and the conditions ther...

Sounds like you have a firewall issue, as Philmalmaison was suggesting in the first post. If your ctm agent cannot communicate with the ctm server, then it cannot tell the ctm server that the job is complete. So the ctm server only finds out when it does a scheduled check of all agents, which by def...

The AlertOnABend parameter creates a standard alert (I think the text is 'Job Ended NOTOK') whenever a job or group fails. If you set the AlertOnAbend to 0, you will get no alert for either the job or the group. If you are relying on this standard alert for notification of failures then this will ca...

Root Menu is not applicable for Windows applications. It is only relevant for UNIX. You can use the Windows 'Services' to manage your EM components on a Windows installation.

Thanks for that.
I assume that the MAXRUNS and MINIMUM parameters also apply only to z/OS.

Hi,
Does anybody know what the MAXDAYS paramete is for. I'm sure that it is different to the MAXWAIT parameter, as they can both be used as functions in a template definition.
Thanks.