Unicenter CA-Scheduler Job Management for VSE User Guide

More documents

Recommendations

Info

3.9 Defining Jobs However, sometimes production JCL requires editing before it can be submitted. STAGE JCL fields on the schedule and job base records identify which jobs have JCL that requires editing before submission. Again, the value of STAGE JCL on the job record overrides the one defined for the schedule. If STAGE JCL = YES, Unicenter CA-Scheduler copies that job's production JCL into the staging library when the job is selected. You can then define an EARLIEST START TIME that allows plenty of time to edit the staged JCL before this job is submitted. Or you can ensure that the JCL has been edited before submission by defining another record for this job at station 39 (JCL setup). Defining a job record for station 39 guarantees that Unicenter CA-Scheduler will not submit this job for processing until that JCL has been edited and staging is complete. In the case where the JCL for a specific job is stored in a CA-Panvalet library, Unicenter CA-Scheduler will submit a batch job that is a library access job. This job will run in a partition and extract the actual job JCL from the library and submit this JCL to POWER to be run so that this JCL may not be staged. Once the JCL is staged, you can use a variety of editor commands to prepare it for submission. In addition to usual text editing, you can perform some special functions within the editor: ■ ■ ■ Expansion of Unicenter CA-Driver procedures embedded in the JCL Display of current values of all Unicenter CA-Driver reserved-name variable parameters in the JCL Change of values of any Unicenter CA-Driver reserved-name variable parameters in the JCL For detailed explanations of the editor commands, see the appendix "Editor Commands" of the Unicenter CA-Scheduler Reference Guide Part 2. 3.9.3.6 On Which CPU Should Jobs Be Run? Unicenter CA-Scheduler uses three fields on both schedule and job base records to record where jobs run: ■ ■ ■ NODE ID NODE SYSID RUN ON SYSID Whether you need to define these fields depends on the CPU configuration at your site: If You Only have one CPU Do This Leave all three fields blank on both schedule and job records. 3-66 Unicenter CA-Scheduler User Guide
3.9 Defining Jobs If You Have multiple CPUs at one site with shared DASD Have a network of CPUs using the POWER/VSE option Do This Define RUN ON SYSID. See the instructions following. Specify NODE ID and possibly NODE SYSID. How you define these fields on schedule and job records is explained following. RUN ON SYSID is only used in a multi-CPU environment with a shared spool complex. Notice that the value on a job record does not override what is specified on the schedule record. Instead, the SYSID on the schedule record selects and submits all jobs in that schedule. You specify which CPU the jobs execute on using RUN ON SYSID on the job record. The schedule record identifies which CPU scans this schedule while selecting the day's workload. The same CPU also submits that schedule's jobs, but those jobs do not necessarily have to execute on that CPU. You can cause a job to execute on another CPU by specifying the POWER SYSID of that CPU in the RUN ON SYSID field of the job's base record. If your site has one CPU perform scheduling for all of them, it is called your Master CPU. It is the first CPU listed on the SYSID= installation generation macro parameter. Since that value is the default for a schedule's RUN ON SYSID, you must leave that field blank on the schedule base record if your site has a Master CPU. NODE ID and NODE SYSID are only used at sites that are part of a network that uses POWER/VSE at each node and Unicenter CA-Scheduler on each CPU at every node. Only use NODE SYSIDs if there are multiple CPUs using shared POWER spool at a NODE ID. Also notice that values for these fields mean different things on schedule and job records. NODE ID on the schedule record indicates the default NODE ID for the jobs in that schedule. A job's NODE ID identifies which node the job's JCL is submitted to. If a job runs on the node specified as the schedule's NODE ID, you can leave NODE ID blank on the job record. To submit a job to another node, specify its node ID on the job base record. Suppose there are multiple CPUs at this node. Use NODE SYSID to specify a particular CPU if the node has multiple CPUs that each run Unicenter CA-Scheduler and share a POWER location. For NODE SYSID, enter the POWER SYSID of the remote CPU where the job is to run. NODE SYSID is only valid if NODE ID is also specified on the same record. When NODE ID and NODE SYSID are given, that job base record's value for RUN ON SYSID is ignored. Chapter 3. Maintaining the Database 3-67
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 20 and 21:
1.3 Additional Features ■ Which j
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:
Page 38 and 39:
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
Page 71 and 72:
3.1 Defining Schedules Sequence By
Page 73 and 74: 3.1 Defining Schedules If your site
Page 75 and 76: 3.1 Defining Schedules A Value Of U
Page 77 and 78: 3.2 Defining Optional Schedule Reco
Page 87 and 88: 3.3 Copying Schedules 3.3 Copying S
Page 89 and 90: 3.3 Copying Schedules To Copy A Sch
Page 91 and 92: 3.4 Displaying Schedules SCHD-SU S
Page 93 and 94: 3.4 Displaying Schedules PRESS ENTE
Page 95 and 96: 3.5 Deleting Schedules SCHD-SD SC
Page 97 and 98: 3.5 Deleting Schedules If you are n
Page 99 and 100: 3.6 Analyzing Schedules SCHD-UTIL
Page 101 and 102: 3.6 Analyzing Schedules Unicenter C
Page 103 and 104: 3.7 Automatic Console Replies for S
Page 109 and 110: 3.8 Summary of Schedule Maintenance
Page 111 and 112: 3.9 Defining Jobs 3.9 Defining Jobs
Page 113 and 114: 3.9 Defining Jobs SCHD-JU JOB DEF
Page 115 and 116: 3.9 Defining Jobs SCHD-JM JOB MAIN
Page 117 and 118: 3.9 Defining Jobs 3.9.3.3 When Will
Page 119 and 120: 3.9 Defining Jobs The chart precedi
Page 121 and 122: 3.9 Defining Jobs those with earlie
Page 123: 3.9 Defining Jobs 3.9.3.5 What JCL
Page 127 and 128: 3.9 Defining Jobs ■ ■ ■ ■ O
Page 129 and 130: 3.9 Defining Jobs When you are read
Page 131 and 132: 3.9 Defining Jobs If You Want Notif
Page 133 and 134: 3.9 Defining Jobs If You Want To Se
Page 135 and 136: 3.9 Defining Jobs The Job Criteria
Page 137 and 138: 3.9 Defining Jobs The criteria stat
Page 139 and 140: 3.9 Defining Jobs ■ MAXIMUM TIMEs
Page 141 and 142: 3.9 Defining Jobs DESTINATIONS and
Page 143 and 144: 3.9 Defining Jobs For These Message
Page 145 and 146: 3.9 Defining Jobs To Separate All J
Page 147 and 148: 3.9 Defining Jobs 3.9.4.6 Defining
Page 149 and 150: 3.10 Displaying and Updating a Job
Page 155 and 156: 3.11 Deleting Job Records 3.11 Dele
Page 157 and 158: 3.11 Deleting Job Records SCHD-JM
Page 159 and 160: 3.12 Analyzing Jobs 3.12 Analyzing
Page 161 and 162: 3.12 Analyzing Jobs To display a fu
Page 163 and 164: 3.13 Automatic Console Replies for
Page 169 and 170: 3.14 Summary of Job Maintenance 3.1
Page 171: 3.14 Summary of Job Maintenance To
Page 174 and 175:
4.1 Online Monitoring Panel 4.1 Onl
Page 176 and 177:
4.1 Online Monitoring Panel This ch
Page 178 and 179:
4.2 Displaying Status Schedules and
Page 180 and 181:
4.2 Displaying Status The table fol
Page 182 and 183:
4.2 Displaying Status To Restrict T
Page 184 and 185:
4.2 Displaying Status 4.2.4.1 Defau
Page 186 and 187:
4.2 Displaying Status SCHD-CP SCHE
Page 188 and 189:
4.2 Displaying Status If the schedu
Page 190 and 191:
4.2 Displaying Status or backlogged
Page 192 and 193:
4.2 Displaying Status The last two
Page 194 and 195:
4.2 Displaying Status WAITING FOR S
Page 196 and 197:
4.3 Handling Messages If your messa
Page 198 and 199:
4.4 Handling Predecessor Conditions
Page 200 and 201:
4.5 Handling Global Parameters 4.5.
Page 202 and 203:
4.7 Displaying Data Set Mask Names
Page 204 and 205:
4.9 Controlling Schedules 4.9 Contr
Page 206 and 207:
4.10 Controlling Jobs 4.10 Controll
Page 208 and 209:
4.10 Controlling Jobs Enter RELE CA
Page 210 and 211:
4.10 Controlling Jobs SCHD-DADP D
Page 212 and 213:
4.11 Summing Up To Specify Abbrevia
Page 214 and 215:
4.11 Summing Up This Command Affect
Page 216 and 217:
The criteria language uses three ty
Page 218 and 219:
5.1 Criteria Vocabulary job. Normal
Page 220 and 221:
5.1 Criteria Vocabulary Example SCD
Page 222 and 223:
5.1 Criteria Vocabulary Given the e
Page 224 and 225:
5.2 Calendar Mechanisms 5.2 Calenda
Page 226 and 227:
5.2 Calendar Mechanisms 5.2.2.1 Wor
Page 228 and 229:
5.2 Calendar Mechanisms Suppose you
Page 230 and 231:
5.2 Calendar Mechanisms datetable o
Page 232 and 233:
5.2 Calendar Mechanisms The panel f
Page 234 and 235:
5.3 Some Examples 5.3 Some Examples
Page 236 and 237:
5.3 Some Examples Example 7 A payro
Page 238 and 239:
5.3 Some Examples ■ ■ If the la
Page 240 and 241:
5.4 What Is Wrong with These Exampl
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:
Page 281 and 282:
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 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
show all

Unicenter CA-Scheduler Job Management for VSE User Guide

Create successful ePaper yourself

Delete template?

Save as template?