Starting in CA Jobtrac R3.5, CA Product Development began to tighten up the Scheduling Control Language (SCL) to force load errors if SCL parameters were found to be in the incorrect field. This project was completed with Jobtrac r11. With this in place, users should test all SCLs to make sure that once you migrate to CA Jobtrac r11, errors will not be encountered during schedule loads.
Below are two methods of testing your existing schedules:
In the first sample SCL, use of the '+TODAY=yyddd' global control record is demonstrated. The '+TODAY' performs a test schedule run using a date defined by this control record.
+TODAY=09029 *EVENTNM TIME DATE DEPS RELEASE1RELEASE2RELEASE3RELEASE4 PROCESSP OPDCCDELOCVV TEST1 ASAP * TEST2 TEST3 TEST4 TEST5 =MTWTF.. TEST2 ASAP * TEST3 TEST4 TEST5 =MTWTF.. TEST3 ASAP * TEST4 TEST5 =MTWTF.. TEST4 ASAP * TEST5 =MTWTF.. TEST5 ASAP * =MTWTF..
In the second method, you would need to modify your SCL to have an Event Type 'D' in column 19 of the primary control record to indicate that the event is a dummy job. A test simulation is done which provides a schedule resolution that can be viewed by selecting the schedule with an 'O' from the 'Schedule Event Display' panel.
*EVENTNM TIME DATE DEPS RELEASE1RELEASE2RELEASE3RELEASE4 PROCESSP OPDCCDELOCVV TEST1 ASAP * D TEST2 TEST3 TEST4 TEST5 =MTWTF.. TEST2 ASAP * D TEST3 TEST4 TEST5 =MTWTF.. TEST3 ASAP * D TEST4 TEST5 =MTWTF.. TEST4 ASAP * D TEST5 =MTWTF.. TEST5 ASAP * D =MTWTF..