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

supportcontent.ca.com
from supportcontent.ca.com More from this publisher
03.03.2015 Views

6.1 Commonly Asked Questions plan of what to expect and when to expect it. When you do this, you can optionally use the simulated start times as the early time of the jobs for submission. When you do, it ignores the early start time that you had on the database. 6.1.3.4 How Do I Plan when To Run a New Application? You first define your application completely. Temporarily set LIBTYPE = TESTLIB in schedule base records. Now run simulation (see the discussion of simulation preceding) with a ONLY command just for the schedules in the new application. This will ensure that everything is the way you want it. If you have backlogged jobs in the simulation, you may want to run the Analyze Report to check for predecessor deadlocks. Once everything looks correct, you can run the application in test mode with the normal day's production and review its affect on the day's workload. 6.1.3.5 How Do I Verify a New Application? There are four steps you should follow in verifying a new application. Step #1 Analyze Report The Analyze Report provides a detailed audit of all information pertaining to the schedules being requested. From this report, you have a complete list of everything that you keyed in for the new application. You also get a set of error messages that identify predecessor/successor deadlocks as well as any references to jobs, predecessors, datetables, and stations that are not on the database. Review this report carefully. Sometimes you may prefer to print just the errors using the LIST=NO option. To obtain this report, use the JCL described in the the topic Reports in the Unicenter CA-Scheduler Reference Guide Part 2. You can also obtain it by issuing the ANALYZE command online in the Job Maintenance (SCHD-JM) or Schedule Maintenance (SCHD-SM) panel. This example analyzes all schedules that begin with the characters "APPLIS." // JOB ANALYZE // EXEC CAJUTIL,SIZE=48K ANALYZE SCHEDULE NAME=APPLIS / /& Step #2 Forecast Run the forecast component for at least a month of dates and obtain the Job Summary Report (SUMMARY). You do this for the schedules that were built for the new application. Through 6-12 Unicenter CA-Scheduler User Guide

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

6.1 Commonly Asked Questions<br />

plan of what to expect and when to expect it. When you do this, you can<br />

optionally use the simulated start times as the early time of the jobs <strong>for</strong><br />

submission. When you do, it ignores the early start time that you had on the<br />

database.<br />

6.1.3.4 How Do I Plan when To Run a New Application?<br />

You first define your application completely. Temporarily set LIBTYPE =<br />

TESTLIB in schedule base records. Now run simulation (see the discussion of<br />

simulation preceding) with a ONLY command just <strong>for</strong> the schedules in the<br />

new application. This will ensure that everything is the way you want it.<br />

If you have backlogged jobs in the simulation, you may want to run the<br />

Analyze Report to check <strong>for</strong> predecessor deadlocks.<br />

Once everything looks correct, you can run the application in test mode with<br />

the normal day's production and review its affect on the day's workload.<br />

6.1.3.5 How Do I Verify a New Application?<br />

There are four steps you should follow in verifying a new application.<br />

Step #1 Analyze Report<br />

The Analyze Report provides a detailed audit of all in<strong>for</strong>mation<br />

pertaining to the schedules being requested. From this report,<br />

you have a complete list of everything that you keyed in <strong>for</strong> the<br />

new application. You also get a set of error messages that<br />

identify predecessor/successor deadlocks as well as any<br />

references to jobs, predecessors, datetables, and stations that are<br />

not on the database. Review this report carefully. Sometimes<br />

you may prefer to print just the errors using the LIST=NO<br />

option.<br />

To obtain this report, use the JCL described in the the topic<br />

Reports in the <strong>Unicenter</strong> <strong>CA</strong>-<strong>Scheduler</strong> Reference <strong>Guide</strong> Part 2.<br />

You can also obtain it by issuing the ANALYZE command<br />

online in the <strong>Job</strong> Maintenance (SCHD-JM) or Schedule<br />

Maintenance (SCHD-SM) panel.<br />

This example analyzes all schedules that begin with the<br />

characters "APPLIS."<br />

// JOB ANALYZE<br />

// EXEC <strong>CA</strong>JUTIL,SIZE=48K<br />

ANALYZE SCHEDULE NAME=APPLIS<br />

/<br />

/&<br />

Step #2 Forecast<br />

Run the <strong>for</strong>ecast component <strong>for</strong> at least a month of dates and<br />

obtain the <strong>Job</strong> Summary Report (SUMMARY). You do this <strong>for</strong><br />

the schedules that were built <strong>for</strong> the new application. Through<br />

6-12 <strong>Unicenter</strong> <strong>CA</strong>-<strong>Scheduler</strong> <strong>User</strong> <strong>Guide</strong>

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!