Unicenter CA-Scheduler Job Management for VSE User Guide
Unicenter CA-Scheduler Job Management for VSE User Guide
Unicenter CA-Scheduler Job Management for VSE User Guide
Create successful ePaper yourself
Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.
6.1 Commonly Asked Questions<br />
use of the ONLY command, only the new schedule names are<br />
supplied causing just the new application to be analyzed.<br />
Through use of the FORE<strong>CA</strong>ST command with the object of<br />
SUMMARY, you will obtain just the <strong>Job</strong> Summary Report. The<br />
following example contains three schedules to be selected over a<br />
one month period with only the <strong>Job</strong> Summary Report being<br />
produced.<br />
// JOB FOR<strong>CA</strong>ST<br />
// EXEC <strong>CA</strong>JUTIL,SIZE=48K<br />
ONLY SCHEDULE N=APPL1S1<br />
ONLY SCHEDULE N=APPL1S2<br />
ONLY SCHEDULE N=APPL1S3<br />
FORE<strong>CA</strong>ST SUMMARY MONTHOF=795<br />
/<br />
/&<br />
Step #3 Simulation<br />
Run the Simulation component <strong>for</strong> each unique day on which<br />
the new application will run. During a month, this may only be<br />
three days: a daily, a weekly, and a monthly.<br />
Step #4 Test<br />
You would use the ONLY and SIMULATE commands to<br />
accomplish this.<br />
You want to verify that the jobs were selected on the days on<br />
which you intended them to be. Then you want to verify that<br />
they were scheduled in the proper sequence: predecessor<br />
relationships are properly followed. If you have jobs that are<br />
backlogged, there is a good chance they may have a predecessor<br />
deadlock. Also, if jobs are backlogged, check the accuracy of<br />
early start times and run times.<br />
Run the schedule in test mode. Use the online tracking RUN S<br />
command with the DATE=date keyword <strong>for</strong> each unique day on<br />
which the new application will run.<br />
Use the STATUS command to verify that jobs are scheduled<br />
correctly, on those dates, and with the correct predecessors.<br />
Keep in mind that since LIBTYPE=TESTLIB, <strong>Unicenter</strong><br />
<strong>CA</strong>-<strong>Scheduler</strong> will submit jobs that execute the <strong>CA</strong>JUTSTA test<br />
program. You can use TESTPARM=testparm on individual jobs<br />
to cause the test program to abend, to pass a nonzero return<br />
code, and to have it wait <strong>for</strong> a number of seconds. By doing<br />
that, you can test the effect of abending and failing jobs on the<br />
rest of the schedule.<br />
After the jobs in the schedule run to your satisfaction, you can<br />
now alter LIBTYPE=TESTLIB, in the SBR, to your production<br />
LIBTYPE. Also make sure that AUTO SELECT is set to YES.<br />
Once you do that, the schedule and its jobs will be automatically<br />
selected, starting at the next AUTOS<strong>CA</strong>N.<br />
Chapter 6. Tips 6-13