There are various ways to startup CICS regions depending upon how the regions are configured. For example, started task vs. jcl. You need to work with your CICS systems programmers to find out how they are started in your environment.

Make sure that on the cyclic definition that you specify from job's End rather than Start.

kolsasha - Are you talking about Control-M jobs??? Sounds like me you are talking about a differnet scheduler, such as Appworx, which uses conditions for a different purpose. I agree with Epping - It is just like setting any other condition. I use some dummy jobs to set global conditions. You just h...

We are running nearly 90,000 jobs per day on one data center (Control-M server). We are running Control-M 6.3 on UNIX with an Oracle 10 database. Most of these are short running cyclic jobs. Most are running on just two agents. We did run into an issue a couple of years ago where we had to convert t...

Sorry I don't speak Ferench. Only U.S. English. The STOP CYCLIC command is your problem. You are telling the job to stop running as cyclic. If you want this job to continue running on the scheduled cycle, regardless if it is successful or not, then you need to remove the STOP CYCLIC command from the...

If JOBB is running on the scheduled cycle then you don't have something coded properly with the condition handling for the condition passed between the jobs. JOBB should be waiting for a Condition from JOBA most of the time. JOBB should only run after JOBA adds the condition. Is JOBB deleting the co...

We have lots of cyclic jobs and most of them have a JOBA creating a condition that JOBB is waiting for. JOBA contains the desired scheduling criteria. JOBB is scheduled with a 1 minute cycle time and scheduled for 00:15 - 23:50. Therefore JOBB is sitting in Control-M waiting on the condition from JO...

Have you looked at your log to see what piece of New Day is taking all of the time? This could provide you a good place to start looking for the issue. We load about 5000 jobs per day. Less than 100 of then have an AJF retention greater than one day. It takes about 4 minutes for our New Day process ...

I have thousands of cyclic jobs in Control-M 6.3. Ending NOTOK does not stop the next cycle from running. Check your "Steps" tab in the job definition. You probably have a "Stop Cyclic" coded under the NOTOK.

Eric T.

I have been involved with our company licensing recently. Licensing can vary from one company to another. Our company has a custom negotiated agreement from several years ago. I am not positive which pieces are "standard" and which are negotiated. I suggest contatcing your sales representative and a...

I have started seeing a new message that last few days that I had not seen before. When I do a "Why" on a job to add a condition there is sometimes a message in the window under the missing condition name(s) that says " There is an operator'or' or 'and' or parentheses missing". What makes this even ...

ctmcontb

Sounds to me like an authorizations issue. I suspect if you compare the security between the userids that you will find differences. I suggest starting by looking at the "privilages" tab and "member of" tab under authorizations. If you still think it is a desktop issue then try logging onto the desk...

I gather the information by running a report from the Control-M Reporting Center. We are running 6.03.01. I use an Active Jobs Report template. On the "Data Source" tab I select the "Load report data..." from the "Latest Archived Network". On the "Filters" tab I use a Rerun Counter > 0. This elimina...

I fell that a better approach is to look for specific values in COMPSTAT. The majority of our jobs are coded to end NOTOK if anything other han zero is detected. However, we do have some jobs setup that take different actions based upon various values. We also learned an interesting lesson a couple ...