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
7.7 Summing Up 7.7.6 NJE Processing The node where a schedule is defined is the node that controls that schedule and submits its jobs. A job's NODE ID identifies where that job will run. A schedule's NODE ID identifies the CPU that will track and control that schedule and its jobs, and will submit those jobs to the appropriate CPUs. NODE SYSID identifies which CPU a job will run on at the specified NODE ID. Predecessor events can be fed between nodes if: ■ ■ Jobs are preceded by the keyword NJE in the successors' criteria statements and the predecessor's job node record is defined to notify every successor's node of the predecessor's status Output data set names are preceded by the keyword DSN in the successors' criteria statements and have been specified to the CAIJ$DSN macro with the successors' nodes that require notification and DSNINFM=YES in the CAIJGEN macro 7-36 Unicenter CA-Scheduler User Guide
Glossary This glossary defines terms used in all volumes of Unicenter CA-Scheduler's documentation, but sometimes one new term leads to another. To help you grasp these new ideas quickly, we have used italics to highlight related terms worth cross-referencing. abend. Abnormal ending. An early termination of a program due to an error. accounting day. A day designated on a datetable as part of a cyclic production, sales, or accounting period. accounting period. One or more accounting days. accounting week. A week containing at least one accounting day. active. Schedules and jobs that are: ■ ■ ■ ■ Waiting at any workstation for predecessors, start time, or defined resources Waiting at a non-CPU station to be started manually Submitted, held, or started Completed, interrupted, abended, or failed The opposite of inactive. array. A variable parameter with multiple values. authority level. One of three different types of access assigned to users using the TYPE field on a user record. Each authority level places different restrictions on what those Unicenter CA-Scheduler users can do. See General, Supervisor, and Manager authority levels. authorized users. Users with General authority level who are allowed to maintain and control a schedule and its jobs because they are listed in the USERS field on that schedule's base record. (Users with Supervisor or Manager authority level do not require specific authorization to maintain or control schedules.) autoscan. The automatic selection of a day's workload. Unicenter CA-Scheduler scans the database at a set time every day to determine the workload for the next 24 hours. autoscan day. The 24-hour period starting with autoscan. Also called the production day. AUTOTIME. The time when Unicenter CA-Scheduler automatically scans its database for workload selection. This defaults to midnight, but may be modified with the AUTOTIM installation option. Also called autoscan time. available. Ready for processing by Unicenter CA-Scheduler. A schedule is available (ready to start) when its early start time has been reached and all of its predecessors have been satisfied. A job is available (ready to be submitted) when its schedule has started, the job's early start time has been reached, all the job's predecessors have been satisfied, and the resources defined for that job are available (not in use). backlog. Work that was not completed one day and was carried over to the next. References to a backlogged schedule or job pertain to a previous day's schedule or job which is included in today's workload. backout job. A replacement job that is automatically submitted by Unicenter CA-Scheduler when a job abends provided that ABEND=BACKOUT on the abended job's base record. base record. The record which is required to define a schedule or job. There is a schedule base record (SBR) and a job base record (JBR). Glossary X-1
- Page 251 and 252: 6.1 Commonly Asked Questions 6.1.2.
- Page 253 and 254: 6.1 Commonly Asked Questions To all
- Page 255 and 256: 6.1 Commonly Asked Questions For de
- Page 257 and 258: 6.1 Commonly Asked Questions use of
- Page 259 and 260: 6.1 Commonly Asked Questions 6.1.4
- Page 261 and 262: 6.1 Commonly Asked Questions If the
- Page 263 and 264: 6.1 Commonly Asked Questions Status
- Page 265 and 266: 6.2 Pitfalls predecessor criteria o
- Page 267 and 268: Chapter 7. Techniques This chapter
- Page 269 and 270: 7.1 On-Request Schedules and Jobs 7
- Page 271 and 272: 7.1 On-Request Schedules and Jobs 7
- Page 273 and 274: 7.1 On-Request Schedules and Jobs W
- Page 275 and 276: 7.2 Backlogged Work completes on We
- Page 277 and 278: 7.3 Issuing Online Commands in Batc
- Page 279 and 280: 7.3 Issuing Online Commands in Batc
- Page 281 and 282: 7.3 Issuing Online Commands in Batc
- Page 283 and 284: 7.4 Restart/Recovery of Scheduled J
- Page 285 and 286: 7.5 Multiple CPU Considerations 7.5
- Page 287 and 288: 7.5 Multiple CPU Considerations Nor
- Page 289 and 290: 7.5 Multiple CPU Considerations exe
- Page 291 and 292: 7.5 Multiple CPU Considerations CAJ
- Page 293 and 294: 7.6 NJE Processing In the preceding
- Page 295 and 296: 7.6 NJE Processing 7.6.2.1 NJE Job
- Page 297 and 298: 7.6 NJE Processing 7.6.4 Installati
- Page 299 and 300: 7.6 NJE Processing Status BUSY Mean
- Page 301: 7.7 Summing Up Prefix PW DM Transac
- Page 305 and 306: documentation batch command. A comm
- Page 307 and 308: Unicenter CA-Scheduler uses when or
- Page 309 and 310: The payroll department's month-end
- Page 311 and 312: Index Special Characters "Who is lo
- Page 313 and 314: Commands (continued) operator (cont
- Page 315 and 316: F FAIL CODE field 7-16 FAILED queue
- Page 317 and 318: MBR SUBID field 3-65 MCPU installat
- Page 319 and 320: Predecessors (continued) types (con
- Page 321 and 322: Scheduling (continued) jobs 1-5, 5-
- Page 323: User (continued) authority levels 2
7.7 Summing Up<br />
7.7.6 NJE Processing<br />
The node where a schedule is defined is the node that controls that schedule<br />
and submits its jobs.<br />
A job's NODE ID identifies where that job will run. A schedule's NODE ID<br />
identifies the CPU that will track and control that schedule and its jobs, and<br />
will submit those jobs to the appropriate CPUs.<br />
NODE SYSID identifies which CPU a job will run on at the specified NODE<br />
ID.<br />
Predecessor events can be fed between nodes if:<br />
■<br />
■<br />
<strong>Job</strong>s are preceded by the keyword NJE in the successors' criteria statements<br />
and the predecessor's job node record is defined to notify every successor's<br />
node of the predecessor's status<br />
Output data set names are preceded by the keyword DSN in the<br />
successors' criteria statements and have been specified to the <strong>CA</strong>IJ$DSN<br />
macro with the successors' nodes that require notification and<br />
DSNINFM=YES in the <strong>CA</strong>IJGEN macro<br />
7-36 <strong>Unicenter</strong> <strong>CA</strong>-<strong>Scheduler</strong> <strong>User</strong> <strong>Guide</strong>
Change language