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
1.3 Additional Features ■ Which jobs would have to be carried over in backlog to the next day What if your system goes down? You can run revised simulation reports that examine the current status of your workload and project what will happen given the time remaining. File Status reports allow you to check the status of the principle Unicenter CA-Scheduler files: ■ ■ ■ ■ ■ Master database Tracking file Staging file Documentation file Unicenter CA-Driver procedure library Use these reports to determine when the files require reorganization (REORG command). The Mailbox report provides a common area to route Unicenter CA-Scheduler messages so that any user can read them. Successor Chain List reports provide a way of listing a job's or schedule's successors either globally or up to a specified level. The reports can be generated online for the current workload or forecasted for a future date. Analysis reports can be used from batch or online to determine whether a schedule or job has any missing or illogical records. A variety of Advantage CA-Earl reports provide detailed information on the principle Unicenter CA-Scheduler files: ■ ■ ■ ■ ■ ■ Master database History file Tracking file Staging file Documentation file Unicenter CA-Driver procedure library A subset of Advantage CA-Earl is provided with Unicenter CA-Scheduler so that you can create Advantage CA-Earl reports to suit your data center's needs. In addition, many ready-to-use reports are provided for you to use as is or modify to your liking. The CAISERV facility allows you to produce diagnostic reports for checking the current values of product options and assisting in troubleshooting problems. To better monitor production, you can cause messages to be sent to different users when schedules or jobs: ■ ■ Start or end Are late starting or ending 1-12 Unicenter CA-Scheduler User Guide
1.3 Additional Features ■ ■ Abend, fail or are purged Run too long Routing of late messages can be defined globally as an installation option. You can specify recipients for other messages using a schedule or job option. Messages can also be logged to the CAICUI data set. Unicenter CA-Scheduler can run two different ways in a multi-CPU environment: ■ ■ All jobs can automatically be scheduled and submitted to one master CPU before they are routed by POWER to another CPU for execution. Or each CPU can schedule and submit its own work. In either event, Unicenter CA-Scheduler can cope with system failure by moving control to another CPU. You can implement Unicenter CA-Scheduler different ways within networks: ■ ■ To centralize scheduling, design a network following the master/slave principle: do job scheduling at one node of a centralized system and route jobs to other nodes for execution. Or let each node schedule its own work. Even if your network has decentralized scheduling, jobs on one network can still be predecessors to jobs scheduled on other networks. Unicenter CA-Scheduler can handle the production traffic of the busiest data centers. Chapter 1. Introduction 1-13
- Page 1 and 2: Unicenter ® CA-Scheduler ® Job Ma
- Page 3 and 4: Contents Chapter 1. Introduction .
- Page 5 and 6: 3.13.1.2 ALTer or REPlace an Auto-R
- Page 7: 7.1.2.1 Example 1 . . . . . . . . .
- Page 10 and 11: 1.1 Beginning with the Basics 1.1 B
- Page 12 and 13: 1.1 Beginning with the Basics To sh
- Page 14 and 15: 1.1 Beginning with the Basics This
- Page 16 and 17: 1.2 How Unicenter CA-Scheduler Work
- Page 18 and 19: 1.2 How Unicenter CA-Scheduler Work
- Page 22 and 23: 1.4 Summing Up 1.4 Summing Up The f
- Page 24 and 25: 2.1 Getting Started 2.1 Getting Sta
- Page 26 and 27: 2.1 Getting Started SCHD-MM MAIN
- Page 28 and 29: 2.1 Getting Started 2.1.4 Logging O
- Page 30 and 31: 2.2 Maintaining Stations SCHD-WM S
- Page 32 and 33: 2.2 Maintaining Stations SCHD-UTIL
- Page 34 and 35: 2.2 Maintaining Stations To submit
- Page 36 and 37: 2.2 Maintaining Stations SCHD-WM S
- Page 38 and 39: 2.2 Maintaining Stations SCHD-WM S
- Page 40 and 41: 2.2 Maintaining Stations SCHD-WD S
- Page 42 and 43: 2.3 Maintaining User Records 2.3 Ma
- Page 44 and 45: 2.3 Maintaining User Records SCHD-
- Page 46 and 47: 2.3 Maintaining User Records To All
- Page 48 and 49: 2.3 Maintaining User Records Unicen
- Page 50 and 51: 2.3 Maintaining User Records Users
- Page 52 and 53: 2.3 Maintaining User Records SCHD-
- Page 54 and 55: 2.3 Maintaining User Records Option
- Page 56 and 57: 2.3 Maintaining User Records If use
- Page 59 and 60: Chapter 3. Maintaining the Database
- Page 61 and 62: 3.1 Defining Schedules ■ ■ ■
- Page 63 and 64: 3.1 Defining Schedules AUTO SELECT
- Page 65 and 66: 3.1 Defining Schedules 3.1.3 Checki
- Page 67 and 68: 3.1 Defining Schedules Option Purpo
- Page 69 and 70: 3.1 Defining Schedules 3.1.4.2 When
1.3 Additional Features<br />
■<br />
Which jobs would have to be carried over in backlog to the next day<br />
What if your system goes down? You can run revised simulation reports that<br />
examine the current status of your workload and project what will happen<br />
given the time remaining.<br />
File Status reports allow you to check the status of the principle <strong>Unicenter</strong><br />
<strong>CA</strong>-<strong>Scheduler</strong> files:<br />
■<br />
■<br />
■<br />
■<br />
■<br />
Master database<br />
Tracking file<br />
Staging file<br />
Documentation file<br />
<strong>Unicenter</strong> <strong>CA</strong>-Driver procedure library<br />
Use these reports to determine when the files require reorganization (REORG<br />
command).<br />
The Mailbox report provides a common area to route <strong>Unicenter</strong> <strong>CA</strong>-<strong>Scheduler</strong><br />
messages so that any user can read them.<br />
Successor Chain List reports provide a way of listing a job's or schedule's<br />
successors either globally or up to a specified level. The reports can be<br />
generated online <strong>for</strong> the current workload or <strong>for</strong>ecasted <strong>for</strong> a future date.<br />
Analysis reports can be used from batch or online to determine whether a<br />
schedule or job has any missing or illogical records.<br />
A variety of Advantage <strong>CA</strong>-Earl reports provide detailed in<strong>for</strong>mation on the<br />
principle <strong>Unicenter</strong> <strong>CA</strong>-<strong>Scheduler</strong> files:<br />
■<br />
■<br />
■<br />
■<br />
■<br />
■<br />
Master database<br />
History file<br />
Tracking file<br />
Staging file<br />
Documentation file<br />
<strong>Unicenter</strong> <strong>CA</strong>-Driver procedure library<br />
A subset of Advantage <strong>CA</strong>-Earl is provided with <strong>Unicenter</strong> <strong>CA</strong>-<strong>Scheduler</strong> so<br />
that you can create Advantage <strong>CA</strong>-Earl reports to suit your data center's needs.<br />
In addition, many ready-to-use reports are provided <strong>for</strong> you to use as is or<br />
modify to your liking.<br />
The <strong>CA</strong>ISERV facility allows you to produce diagnostic reports <strong>for</strong> checking the<br />
current values of product options and assisting in troubleshooting problems.<br />
To better monitor production, you can cause messages to be sent to different<br />
users when schedules or jobs:<br />
■<br />
■<br />
Start or end<br />
Are late starting or ending<br />
1-12 <strong>Unicenter</strong> <strong>CA</strong>-<strong>Scheduler</strong> <strong>User</strong> <strong>Guide</strong>