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.6 NJE Processing 7.6 NJE Processing NJE processing provides the ability to go beyond one data center complex. That is, you can schedule and control production at different locations (even in different cities). The different locations can have just one CPU or they may have a multi-CPU environment, though each CPU must be a node on the VTAM network. In some cases, you may want to have just interdependencies across locations properly handled. In other cases, you may want to go beyond this and have jobs at one location submitted to execute at another location. These locations are called nodes in the network of computer sites (or systems). The network consists of two or more of these interconnected systems (nodes) that participate in a VTAM communications network. Using more common terminology, a job at one node can have a predecessor at another node and Unicenter CA-Scheduler will know to wait for it. Each node will be able to schedule its own work as if it were autonomous, but when it has interrelationships with other nodes, they will be upheld properly. This is a decentralized (Master/Master) environment. Each of these Master environments (nodes) can have its own Master/Master or Master/Slave environment and may be one or more CPUs themselves that utilize shared spool. Following are some samples that describe: ■ ■ ■ Cross-node job submission Cross-node dependencies Cross-node communications. 7.6.1 Cross-Node Job Submission In a NJE environment, it is possible to have Unicenter CA-Scheduler cause work to be submitted to run on other nodes. The appropriate VSE/POWER JECL parameters (if omitted from the submitted JCL) are generated to handle this, but what you want to accomplish here is to have you understand how Unicenter CA-Sheduler operates in this environment. The following depicts the general environment that the samples will reference. 7-26 Unicenter CA-Scheduler User Guide
7.6 NJE Processing In the preceding diagram, the NODEA site is a single CPU using VSE\POWER with NJE, and CA†SCHEDULER with the NJE option activated. Each CPU is a node on a VTAM Network. Sample 1 Sample 2 Sample 3 Schedule SCHDA is defined at node NODEA with no NODE ID specified. This is the normal case and it will always be controlled by NODEA. Schedule SCHDB is defined at node NODEB with no NODE ID specified. This is also the normal case and it will be controlled by NODEB. Schedule SCHDX is defined at node NODEA with a NODE ID of NODEB. JOB1 is defined as part of schedule SCHDX and has no NODE ID specified. In this case, NODEA controls and submits JOB1. JOB1 will be routed to NODEB where it will run and NODEB will know to send its status back to NODEA for posting and control. Notice that since the NODE ID for the job was not defined, it uses the one defined for the schedule. Sample 4 Schedule SCHDX is defined at node NODEA. JOB1 is defined as part of schedule SCHDX and has a NODE ID of NODEB, which means that JOB1 is to execute on the CPU defined as NODEB. In this case, NODEA controls the schedule SCHDX. JOB1 within SCHDX, however, has a NODE ID defined which means that JOB1 will have its JCL routed to NODEB through NJE. Chapter 7. Techniques 7-27
- Page 242 and 243: 5.4 What Is Wrong with These Exampl
- Page 245 and 246: Chapter 6. Tips This topic of the m
- Page 247 and 248: 6.1 Commonly Asked Questions 6.1.1.
- Page 249 and 250: 6.1 Commonly Asked Questions Keep i
- 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: 7.5 Multiple CPU Considerations CAJ
- 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 and 302: 7.7 Summing Up Prefix PW DM Transac
- Page 303 and 304: Glossary This glossary defines term
- 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.6 NJE Processing<br />
In the preceding diagram, the NODEA site is a single CPU using <strong>VSE</strong>\POWER<br />
with NJE, and <strong>CA</strong>†SCHEDULER with the NJE option activated. Each CPU is a<br />
node on a VTAM Network.<br />
Sample 1<br />
Sample 2<br />
Sample 3<br />
Schedule SCHDA is defined at node NODEA with no NODE<br />
ID specified.<br />
This is the normal case and it will always be controlled by<br />
NODEA.<br />
Schedule SCHDB is defined at node NODEB with no NODE<br />
ID specified.<br />
This is also the normal case and it will be controlled by<br />
NODEB.<br />
Schedule SCHDX is defined at node NODEA with a NODE ID<br />
of NODEB. JOB1 is defined as part of schedule SCHDX and<br />
has no NODE ID specified.<br />
In this case, NODEA controls and submits JOB1. JOB1 will be<br />
routed to NODEB where it will run and NODEB will know to<br />
send its status back to NODEA <strong>for</strong> posting and control. Notice<br />
that since the NODE ID <strong>for</strong> the job was not defined, it uses<br />
the one defined <strong>for</strong> the schedule.<br />
Sample 4<br />
Schedule SCHDX is defined at node NODEA. JOB1 is defined<br />
as part of schedule SCHDX and has a NODE ID of NODEB,<br />
which means that JOB1 is to execute on the CPU defined as<br />
NODEB.<br />
In this case, NODEA controls the schedule SCHDX. JOB1<br />
within SCHDX, however, has a NODE ID defined which<br />
means that JOB1 will have its JCL routed to NODEB through<br />
NJE.<br />
Chapter 7. Techniques 7-27
Change language