Tivoli Workload Scheduler

Job Scheduling Console 

Version 8.3

User’s Guide

SC32-1257-06
 Tivoli Workload Scheduler
®

Job Scheduling Console 

Version 8.3

User’s Guide

SC32-1257-06
 Note

Before using this information and the product it supports, read the information in “Notices” on page 437.

Seventh Edition (December 2006)

This edition applies to version 8, release 3, modification level 0, fix pack 02, of IBM Tivoli Workload Scheduler Job
Scheduling Console (program number 5697-WSZ, 5698-WSH) and to all subsequent releases and modifications until
otherwise indicated in new editions.
This edition replaces SC32–1257–05.
© Copyright International Business Machines Corporation 1991, 2006. All rights reserved.
US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contract
with IBM Corp.
 Contents
List of figures . . . . . . . . . . . . ix Chapter 4. Importing Job Scheduling
Console user preferences . . . . . . 17
List of tables . . . . . . . . . . . . xi | Importing Job Scheduling Console user preferences
| from versions prior to 8.3 . . . . . . . . . . 17
About this publication . . . . . . . . xiii | Importing Job Scheduling Console user preferences
What is new in this release . . . . . . . . . xiii | from versions 8.3 . . . . . . . . . . . . 18
What is new in this publication . . . . . . . xiii
What is new in this publication for Fix Pack 01 xiii Chapter 5. Installing and adding
What is new in this publication for Fix Pack 02 xiv language packs . . . . . . . . . . . 21
Who should read this publication . . . . . . . xv Installing language packs . . . . . . . . . . 21
What this publication contains . . . . . . . . xv Installing language packs using the installation
Publications . . . . . . . . . . . . . . xix wizard . . . . . . . . . . . . . . . 21
Tivoli Workload Scheduler library . . . . . xix Installing language packs in silent mode . . . . 21
Related publications . . . . . . . . . . xxiii Adding language packs to an existing installation 21
Accessing publications online . . . . . . . xxv
Ordering publications . . . . . . . . . xxvi Chapter 6. Uninstalling . . . . . . . . 23
Accessibility . . . . . . . . . . . . . xxvi Uninstalling language packs . . . . . . . . . 23
Tivoli technical training . . . . . . . . . xxvii Uninstalling the Job Scheduling Console . . . . . 23
Support information . . . . . . . . . . xxvii Uninstalling the Job Scheduling Console using
Conventions used in this publication . . . . . xxvii the Software Distribution CLI . . . . . . . 24
Typeface conventions . . . . . . . . . xxvii Uninstalling the z/OS connector . . . . . . . 24
Operating system-dependent variables and
paths . . . . . . . . . . . . . . xxviii
Command syntax . . . . . . . . . . xxviii Part 2. Getting started . . . . . . . 25

Part 1. Planning and installation . . . 1 Chapter 7. Job Scheduling Console

objects and scheduling concepts . . . 27
Chapter 1. Job Scheduling Console Job Scheduling Console objects . . . . . . . . 27
Common objects . . . . . . . . . . . . 27
overview . . . . . . . . . . . . . . 3 | z/OS engine specific objects . . . . . . . . 28
Tivoli Workload Scheduler topology . . . . . . 3 Distributed engine specific objects . . . . . . 29
Where the Job Scheduling Console fits in the Lists . . . . . . . . . . . . . . . . 31
topology . . . . . . . . . . . . . . . 3 Database . . . . . . . . . . . . . . 31
Connection . . . . . . . . . . . . . . 6 Plan . . . . . . . . . . . . . . . . 31
Scheduling job streams using defined objects . . . 32
Chapter 2. Planning and installing the Time restrictions . . . . . . . . . . . . 32
Job Scheduling Console . . . . . . . 9 Dependencies. . . . . . . . . . . . . 32
Planning installation of the Job Scheduling Console . 9 Distributed dependencies . . . . . . . . . 33
The installation CDs . . . . . . . . . . . 9 Time Zones and the Job Scheduling Console . . 33
Installation methods . . . . . . . . . . 10 Run cycles . . . . . . . . . . . . . . 34
Installing using the installation wizard . . . . . 10
Installing the Job Scheduling Console in Chapter 8. Job Scheduling Console
interactive mode . . . . . . . . . . . . 11 task guide . . . . . . . . . . . . . 37
Installing the Job Scheduling Console in silent Task types . . . . . . . . . . . . . . . 37
mode . . . . . . . . . . . . . . . 11 Definition tasks . . . . . . . . . . . . 37
Installing using Software Distribution . . . . . 12 Management tasks . . . . . . . . . . . 37
Installing the Java Virtual Machine . . . . . 13 Task flows . . . . . . . . . . . . . . . 37
Definition task flows . . . . . . . . . . 37
Chapter 3. Planning and installing the Management task flows . . . . . . . . . 38
z/OS connector . . . . . . . . . . . 15 Task mapping . . . . . . . . . . . . . 40
Planning connector installations . . . . . . . 15 Command-line mapping . . . . . . . . . . 42
| Installing the z/OS connector . . . . . . . . 15 Terminology mapping . . . . . . . . . . . 42
| Performing a silent installation . . . . . . . 16

© Copyright IBM Corp. 1991, 2006 iii

 Chapter 9. Starting the Job Scheduling Chapter 16. Creating engines . . . . . 95
Console . . . . . . . . . . . . . . 45
Logging on to an engine . . . . . . . . . . 46 Chapter 17. Creating workstations . . . 97
Standard functions . . . . . . . . . . . . 48 Creating a z/OS workstation . . . . . . . . 98
Standard buttons . . . . . . . . . . . 48 General page . . . . . . . . . . . . . 98
Wildcards . . . . . . . . . . . . . . 48 Resources page . . . . . . . . . . . . 101
Unsupported characters . . . . . . . . . 48 Open Time Intervals page . . . . . . . . 102
Finding objects . . . . . . . . . . . . 48 Creating a distributed workstation . . . . . . 103
Deleting objects from a list . . . . . . . . 49
Pop-up menus . . . . . . . . . . . . 49 Chapter 18. Creating resources. . . . 107
Required data . . . . . . . . . . . . 49 Creating a z/OS resource . . . . . . . . . 107
General page . . . . . . . . . . . . 108
Part 3. Quick reference guide . . . . 51 Default Workstations page . . . . . . . . 109
Availability Intervals page . . . . . . . . 110
Chapter 10. Quick reference overview 53 Creating a distributed resource . . . . . . . 111

Chapter 11. Interface quick reference 55 Chapter 19. Creating Windows users 113
Actions list pane . . . . . . . . . . . . . 55
Work with engines pane . . . . . . . . . . 56 Chapter 20. Creating parameters . . . 115
| Object list pane . . . . . . . . . . . . . 56
| Impact View . . . . . . . . . . . . . . 57 Chapter 21. Creating predefined
Job stream editor . . . . . . . . . . . . 58 prompts . . . . . . . . . . . . . . 117
The main menu bar . . . . . . . . . . . 59
The distributed job stream editor menu bar . . . . 60
Chapter 22. Creating calendars . . . . 119
The z/OS job stream editor menu bar . . . . . 60
Creating a calendar . . . . . . . . . . . 119
The main window toolbar . . . . . . . . . 60
Defining a calendar . . . . . . . . . . . 120
The distributed job stream editor toolbar . . . . 61
The z/OS job stream editor toolbar . . . . . . 62
The impact view toolbar . . . . . . . . . . 63 Chapter 23. Creating domains . . . . 123

Chapter 12. z/OS quick reference . . . 65 Chapter 24. Creating workstation

Quick definition steps for a z/OS environment . . 65 classes . . . . . . . . . . . . . . 125
Create workstations . . . . . . . . . . . 65 General page . . . . . . . . . . . . . 125
Create resources . . . . . . . . . . . . . 65 Workstations page . . . . . . . . . . . . 126
Create job streams . . . . . . . . . . . . 67
Create jobs . . . . . . . . . . . . . . 68 Chapter 25. Creating job definitions 127
General page . . . . . . . . . . . . . 128
Chapter 13. Distributed quick reference 73 Task page . . . . . . . . . . . . . . 130
Quick definition steps for a distributed environment 73 Adding parameters to jobs . . . . . . . . 131
Create domains and workstations . . . . . . . 73 Extended agent . . . . . . . . . . . . 131
Create parameters . . . . . . . . . . . . 75 SAP job . . . . . . . . . . . . . . 131
Create job definitions . . . . . . . . . . . 76
Create calendars . . . . . . . . . . . . . 79 Chapter 26. Creating job streams . . . 133
Create prompts . . . . . . . . . . . . . 81 Creating z/OS job streams . . . . . . . . . 133
Create job streams . . . . . . . . . . . . 82 Creating the job stream . . . . . . . . . 134
Creating a job . . . . . . . . . . . . 136
Chapter 14. Explorer View quick Creating distributed job streams . . . . . . . 147
reference . . . . . . . . . . . . . . 87 General page . . . . . . . . . . . . 148
Opening a job stream in the Explorer View . . . . 87 Comments page . . . . . . . . . . . 149
Adding a new job to a job stream in the Explorer Dependency Resolution page . . . . . . . 149
View . . . . . . . . . . . . . . . . 89 Time Restrictions page . . . . . . . . . 150
Resources page . . . . . . . . . . . . 151
Chapter 15. Troubleshooting quick | Prompts page . . . . . . . . . . . . 152
Files page . . . . . . . . . . . . . 152
reference . . . . . . . . . . . . . . 91
Chapter 27. Creating forecast and trial
Part 4. Defining objects . . . . . . 93 plans . . . . . . . . . . . . . . . 155

iv IBM Tivoli Workload Scheduler Job Scheduling Console: User’s Guide

Chapter 28. Creating objects using Managing a distributed engine . . . . . . . 193
Create Another . . . . . . . . . . . 157 General page . . . . . . . . . . . . 193
Engine Data page . . . . . . . . . . . 194

Part 5. Creating and using lists 159 Chapter 35. Managing workstations 197
Chapter 29. Creating database lists 161 Chapter 36. Managing z/OS job
Creating job stream lists in the database . . . . 163
streams . . . . . . . . . . . . . . 199
Creating a z/OS job stream list . . . . . . 163
Creating dependencies between jobs . . . . . . 199
Creating a distributed job stream list . . . . 164
Creating dependencies within a job stream . . 199
Creating workstation lists in the database . . . . 165
Creating dependencies between job streams . . 200
Creating a z/OS workstation list . . . . . . 165
Scheduling z/OS job streams . . . . . . . . 202
Creating a distributed workstation list . . . . 165
Creating rule-based run cycles . . . . . . . 202
Creating resource lists in the database . . . . . 166
Creating offset-based run cycles . . . . . . 209
Creating a z/OS resource list . . . . . . . 166
Adding, modifying, and deleting jobs and
Creating a distributed resource list . . . . . 167
dependencies . . . . . . . . . . . . . 214
Creating job definition lists in the database . . . 167
Modifying a job in the Graph View . . . . . 214
Creating workstation class lists in the database . . 168
Deleting a job or external job . . . . . . . 214
Creating prompt lists in the database . . . . . 168
| Deleting jobs simultaneously from a job stream 214
Creating parameter lists in the database . . . . 168
Editing another job stream from an external job 215
Creating Windows user lists in the database . . . 169
Removing a dependency between jobs in the
Creating domain lists in the database . . . . . 169
Graph View . . . . . . . . . . . . . 215
Creating calendar lists in the database . . . . . 170
Viewing and modifying time restrictions . . . . 215
Changing time restrictions in the Timeline View 215
Chapter 30. Creating plan lists . . . . 171 Using the copy function to add an external job . . 217
Creating job stream instance lists in the plan . . . 171
Creating z/OS job stream instance lists in the
Chapter 37. Managing distributed job
plan . . . . . . . . . . . . . . . 171
Creating distributed job stream instance lists in streams . . . . . . . . . . . . . . 219
the plan . . . . . . . . . . . . . . 173 Adding external dependencies to a job stream in
Creating job instance lists in the plan . . . . . 174 the Graph View . . . . . . . . . . . . 219
Creating z/OS job instance lists in the plan . . 175 Add an external job stream dependency . . . 220
Creating distributed job instance lists in the Add an internetwork dependency . . . . . 220
plan . . . . . . . . . . . . . . . 176 Add an external job dependency . . . . . . 220
Creating workstation status lists in the plan . . . 178 Adding external dependencies to a job stream in
Creating resource status lists in the plan . . . . 178 the Explorer View . . . . . . . . . . . . 221
Creating file status lists in the plan . . . . . . 178 Adding a job to a job stream in the Graph View 222
Creating prompt status lists in the plan. . . . . 179 General page . . . . . . . . . . . . 223
Creating domain status lists in the plan . . . . 179 Time Restrictions page . . . . . . . . . 223
Resources page . . . . . . . . . . . . 225
Files page . . . . . . . . . . . . . 225
Chapter 31. Creating a group of lists 181
| Prompts page . . . . . . . . . . . . 225
Adding a job to a job stream in the Explorer View 226
Chapter 32. Creating common plan Using the copy function to add an external job to a
lists . . . . . . . . . . . . . . . 183 job stream . . . . . . . . . . . . . . 227
Creating a common list of job stream instances . . 183 Adding an internetwork dependency to a job in
Creating a common list of job instances . . . . 183 the Graph View . . . . . . . . . . . . 228
Adding an external job stream to a job stream . . 228
Chapter 33. Working with lists . . . . 185 Adding an external job to a job stream . . . . . 229
Displaying a list of objects . . . . . . . . . 185 Creating dependencies between jobs in a job
Detaching a list . . . . . . . . . . . . . 186 stream . . . . . . . . . . . . . . . . 230
Modifying a list . . . . . . . . . . . . 186 Adding run cycles to a job stream . . . . . . 231
Unlocking locked distributed objects in a list . . . 187 Rule page . . . . . . . . . . . . . 232
Time Restrictions page . . . . . . . . . 234
Deleting external dependencies from a job stream 235
Part 6. Managing database objects 189 Deleting run cycles from a job stream . . . . . 236
| Deleting jobs simultaneously from a job stream . . 236
Chapter 34. Managing engines . . . . 191 Checking time restrictions in the Timeline View 236
Managing a z/OS engine . . . . . . . . . 191 Activity bars . . . . . . . . . . . . 237
General page . . . . . . . . . . . . 192 Table frame . . . . . . . . . . . . . 237
Scheduler Information page . . . . . . . 192 Time restrictions . . . . . . . . . . . 237

Contents v
 Other tasks . . . . . . . . . . . . . 238 Changing the limit of a job stream instance . . . 275
Changing the priority of a job stream instance . . 275
Chapter 38. Managing resources . . . 239 Releasing a job stream instance from dependencies 276
Resubmitting a job stream instance . . . . . . 276
| Deleting jobs simultaneously from a job stream
Chapter 39. Managing job definitions 241
| instance . . . . . . . . . . . . . . . 276
Displaying and modifying job definitions . . . . 241
Displaying job definition details . . . . . . . 241
Chapter 48. Managing z/OS job
Chapter 40. Managing workstation instances . . . . . . . . . . . . . 277
Browsing and modifying z/OS job instances . . . 277
classes . . . . . . . . . . . . . . 243
General page . . . . . . . . . . . . 278
Task page . . . . . . . . . . . . . 279
Chapter 41. Managing domains . . . . 245 Time Restrictions page . . . . . . . . . 279
Details page . . . . . . . . . . . . . 280
Chapter 42. Managing Windows users 247 Options page . . . . . . . . . . . . 281
Resources page . . . . . . . . . . . . 282
Chapter 43. Managing calendars . . . 249 | Automation page . . . . . . . . . . . 284
Browsing and modifying job instance dependencies 285
Predecessors page . . . . . . . . . . . 286
Chapter 44. Managing prompts . . . . 251 Successors page . . . . . . . . . . . 286
Changing time restrictions in the Timeline View 287
Chapter 45. Managing parameters . . 253 Elements of the Timeline View . . . . . . 287
Rescheduling a job instance . . . . . . . 288
Part 7. Managing plans . . . . . . 255 Rescheduling a job instance start time . . . . 288
Rescheduling a job instance deadline time . . . 288
Deleting a job instance . . . . . . . . . . 288
Chapter 46. Managing z/OS job stream Deleting all job instances . . . . . . . . 288
instances . . . . . . . . . . . . . 257 Holding a job instance . . . . . . . . . . 289
Submitting a job stream . . . . . . . . . . 257 Holding a single job instance . . . . . . . 289
Browsing and modifying job stream instances . . 259 Holding all job instances . . . . . . . . 289
General page . . . . . . . . . . . . 260 Releasing a job instance . . . . . . . . . . 289
Time Restrictions page . . . . . . . . . 260 Releasing a single job instance . . . . . . . 289
Rerunning a job stream instance . . . . . . . 260 Releasing all job instances . . . . . . . . 289
| Deleting jobs simultaneously from a job stream Showing dependencies in the Impact View . . . 290
| instance . . . . . . . . . . . . . . . 260 Displaying dependencies . . . . . . . . 290
Set as root . . . . . . . . . . . . . 291
Chapter 47. Managing distributed job Browsing the job log . . . . . . . . . . . 291
stream instances in the plan . . . . . 263 Setting a job instance to a non operational state
Submitting a job stream into the plan . . . . . 263 (NOP) in the plan . . . . . . . . . . . . 291
Displaying and changing the properties of a job Restoring a job instance to operational in the plan
stream instance . . . . . . . . . . . . . 264 (UN-NOP) . . . . . . . . . . . . . . 291
General page . . . . . . . . . . . . 265 | Killing a job instance running on a fault-tolerant
Time Restrictions page . . . . . . . . . 266 | agent . . . . . . . . . . . . . . . . 291
Resources page . . . . . . . . . . . . 267 Running a job instance immediately . . . . . . 292
Files page . . . . . . . . . . . . . 268 Changing the status of a job instance . . . . . 292
| Prompts page . . . . . . . . . . . . 268 Editing JCL . . . . . . . . . . . . . . 292
Predecessors page . . . . . . . . . . . 270 Viewing operator instructions . . . . . . . . 292
| Internetwork Predecessors page . . . . . . 270 Modifying job setup . . . . . . . . . . . 292
Displaying and changing the follows dependencies Restart and cleanup . . . . . . . . . . . 293
of a job stream instance . . . . . . . . . . 271 Recovery information. . . . . . . . . . . 294
Predecessors page . . . . . . . . . . . 272 Automatic recovery . . . . . . . . . . . 294
Internetwork Predecessors page . . . . . . 273 | Critical Path . . . . . . . . . . . . . . 295
Successors page . . . . . . . . . . . 273
Holding a job stream instance . . . . . . . . 274 Chapter 49. Managing distributed job
Releasing a job stream instance . . . . . . . 274 instances in the plan . . . . . . . . 297
Showing predecessors and successors in the Impact Submitting a job . . . . . . . . . . . . 297
View . . . . . . . . . . . . . . . . 274 Into a default job stream. . . . . . . . . 297
Cancelling a job stream instance . . . . . . . 275 Into a specific job stream . . . . . . . . 299
| Performing a cancel pending of a job stream Submitting an ad hoc job . . . . . . . . . 299
| instance . . . . . . . . . . . . . . . 275 Into a specific job stream . . . . . . . . 299

vi IBM Tivoli Workload Scheduler Job Scheduling Console: User’s Guide

 Into a default job stream. . . . . . . . . 307 Managing z/OS resources . . . . . . . . . 331
Modifying the properties of a job instance . . . . 307 Browsing and modifying resources . . . . . 331
General page . . . . . . . . . . . . 308 Displaying the job instances associated with a
Task page . . . . . . . . . . . . . 309 resource . . . . . . . . . . . . . . 333
Time Restrictions page . . . . . . . . . 310 Modifying job instances associated with a
Resources page . . . . . . . . . . . . 311 resource . . . . . . . . . . . . . . 334
| Prompts page . . . . . . . . . . . . 311 Managing distributed resources . . . . . . . 335
Files page . . . . . . . . . . . . . 313 Displaying resource dependencies status . . . 335
Displaying and modifying job instance Displaying and modifying the properties of a
dependencies . . . . . . . . . . . . . 314 resource dependency . . . . . . . . . . 335
Predecessors page . . . . . . . . . . . 314 Changing the number of units of a resource
Internetwork Predecessors page . . . . . . 315 dependency . . . . . . . . . . . . . 336
Successors page . . . . . . . . . . . 316
| Deleting a job instance . . . . . . . . . . 316 Chapter 52. Managing distributed file
| Deleting all job instances . . . . . . . . 316 dependencies in the plan . . . . . . 337
Holding a job instance . . . . . . . . . . 316
Displaying file dependencies status . . . . . . 337
Holding a single job instance . . . . . . . 317
Holding all job instances . . . . . . . . 317
Releasing a job instance . . . . . . . . . . 317 Chapter 53. Managing distributed
Releasing a single job instance . . . . . . . 317 prompt dependencies in the plan . . . 339
Releasing all job instances . . . . . . . . 317 Displaying prompt dependencies status . . . . 339
Showing job instance predecessors and successors Replying to a prompt dependency . . . . . . 339
using the Impact View . . . . . . . . . . 317
Browsing the job log . . . . . . . . . . . 318 Chapter 54. Managing domains in the
Rerunning a job instance . . . . . . . . . 319 plan . . . . . . . . . . . . . . . 341
Cancelling a job instance . . . . . . . . . 319 Starting the workstations in a domain . . . . . 341
| Performing a cancel pending of a job instance . . 320 Stopping the workstations in a domain . . . . . 341
| Killing a job instance . . . . . . . . . . . 320 Linking the workstations in a domain . . . . . 341
Confirming a job instance status . . . . . . . 320 Unlinking the workstations in a domain . . . . 342
Releasing a job instance from dependencies . . . 320 Switching the domain manager in a domain . . . 342

Chapter 50. Managing workstations in Chapter 55. Changing Windows user

the plan . . . . . . . . . . . . . . 321 passwords in the plan . . . . . . . 343
Managing z/OS workstations in the plan . . . . 321
Displaying the status of z/OS workstations in
the plan . . . . . . . . . . . . . . 321
Chapter 56. Setting an alternate plan 345
Modifying z/OS workstation properties in the
plan . . . . . . . . . . . . . . . 322 | Chapter 57. Restoring a plan . . . . . 347
Linking fault-tolerant workstations . . . . . 324
Changing workstation status and rerouting Part 8. Troubleshooting . . . . . . 349
scheduled job instances . . . . . . . . . 324
Displaying workstation job instances by status 325
Modifying z/OS job instances scheduled on a Chapter 58. Setting traces for the Job
workstation . . . . . . . . . . . . . 325 Scheduling Console . . . . . . . . 351
Managing distributed workstations in the plan . . 326
Displaying the status of distributed Chapter 59. Troubleshooting . . . . . 353
workstations in the plan . . . . . . . . . 326 Installation troubleshooting . . . . . . . . . 353
Displaying distributed workstation instance Job Scheduling Console installation log . . . . 353
properties . . . . . . . . . . . . . 328 Connector installation log . . . . . . . . 353
Changing the job limit of a workstation in the Installation troubleshooting . . . . . . . . 353
plan . . . . . . . . . . . . . . . 328 General troubleshooting . . . . . . . . . . 354
Changing the job fence of a workstation in the Repairing the installation . . . . . . . . . 356
plan . . . . . . . . . . . . . . . 329
Starting a workstation instance . . . . . . 329 Chapter 60. Job Scheduling Console
Stopping a workstation instance . . . . . . 329
Linking a workstation instance . . . . . . 329
messages . . . . . . . . . . . . . 357
Unlinking a workstation instance . . . . . . 329 Job Scheduling Console base messages . . . . . 357
Job Scheduling Console z/OS messages . . . . 376
Job Scheduling Console distributed messages . . . 382
Chapter 51. Managing resources in Job Scheduling Console starting and stopping
the plan . . . . . . . . . . . . . . 331 messages . . . . . . . . . . . . . . . 406

Contents vii
| Part 9. Administration . . . . . . . 407 | Appendix B. Starting the Job
| Scheduling Console from an external
| Chapter 61. Changing the TWSUser | application . . . . . . . . . . . . 421
| password for the z/OS connector . . . 409
| Step 1: change the local operating system password 409 Appendix C. Setting security . . . . . 423
| Step 2: change WebSphere Application Server user
| ID password . . . . . . . . . . . . . 409 Appendix D. Status description and
| Step 3: change passwords used to connect to the mapping . . . . . . . . . . . . . 425
| engine . . . . . . . . . . . . . . . . 411
| Step 4: change the Windows services password . . 411
Appendix E. Support information . . . 429
Using IBM Support Assistant . . . . . . . . 429
| Chapter 62. Managing z/OS engines Searching knowledge bases . . . . . . . . . 430
| using WebSphere Application Server Searching the local information center . . . . 430
| tools . . . . . . . . . . . . . . . 413 Searching the Internet . . . . . . . . . 430
| Create a z/OS connector instance . . . . . . 413 Obtaining fixes . . . . . . . . . . . . . 431
| Displaying the properties of a z/OS connector Receiving weekly support updates . . . . . . 432
| instance . . . . . . . . . . . . . . . 414 Contacting IBM Software Support . . . . . . 433
| Updating the properties of a z/OS connector Determining the business impact . . . . . . 434
| instance . . . . . . . . . . . . . . . 415 Describing problems and gathering information 434
| Listing all the z/OS connector instances . . . . 415 Submitting problems . . . . . . . . . . 434
| Remove a z/OS connector instance . . . . . . 416
Notices . . . . . . . . . . . . . . 437
Appendix A. Accessibility . . . . . . 417 Trademarks . . . . . . . . . . . . . . 438
Navigating the interface using the keyboard . . . 417
Magnifying what is displayed on the screen . . . 417 Glossary . . . . . . . . . . . . . 441
General mnemonics . . . . . . . . . . . 418
Main window mnemonics . . . . . . . . . 418
Index . . . . . . . . . . . . . . . 449
Menu mnemonics . . . . . . . . . . . . 419

viii IBM Tivoli Workload Scheduler Job Scheduling Console: User’s Guide
 List of figures
1. Single tier topology . . . . . . . . . . 4 10. Example Properties panel for z/OS job stream
2. Multi-tier topology . . . . . . . . . . 5 list . . . . . . . . . . . . . . . 163
3. End-to-end topology with Job Scheduling | 11. Example rule . . . . . . . . . . . 206
Console . . . . . . . . . . . . . . 6 | 12. Rule-based run cycle . . . . . . . . . 207
| 4. Job Scheduling Console connection . . . . . 7 | 13. Exclusive run cycle . . . . . . . . . 208
5. Illustration of the dead zone . . . . . . . 34 14. Exclusive run cycle defined . . . . . . . 209
6. Definition task flows . . . . . . . . . 38 | 15. Example 1: Offset-based run cycle . . . . 212
7. Management task flows . . . . . . . . 39 16. Example 2: Offset-based run cycle defined 213
| 8. Example z/OS Job Stream Editor . . . . . 59 17. Timeline View . . . . . . . . . . . 216
9. Example Properties panel for distributed
engines . . . . . . . . . . . . . 162

© Copyright IBM Corp. 1991, 2006 ix

x IBM Tivoli Workload Scheduler Job Scheduling Console: User’s Guide
 List of tables
1. Command syntax . . . . . . . . . xxviii 9. Logging properties keys . . . . . . . . 351
| 2. Default variable value for operating system 12 10. Job Scheduling Console job states . . . . . 425
3. Operating system variables . . . . . . . 12 11. Tivoli Workload Scheduler internal job states 425
4. Language variables . . . . . . . . . . 13 12. Job Scheduling Console job stream states 427
5. z/OS and distributed task mapping . . . . 40 13. Tivoli Workload Scheduler internal job stream
6. Job Scheduling Console terminology mapping 42 states . . . . . . . . . . . . . . 427
7. Starting the Job Scheduling Console . . . . 45 14. Job status mapping . . . . . . . . . 428
8. Job stream recovery options . . . . . . . 129 15. Job stream status mapping . . . . . . . 428

© Copyright IBM Corp. 1991, 2006 xi

xii IBM Tivoli Workload Scheduler Job Scheduling Console: User’s Guide
About this publication
This IBM® Tivoli® Workload Scheduler: Job Scheduling Console User’s Guide describes
IBM Tivoli Workload Scheduler Job Scheduling Console version 8.3. It explains
how to install the console and provides instructions for performing scheduling
tasks using IBM Tivoli Workload Scheduler for z/OS and Tivoli Workload
Scheduler for distributed engines.

What is new in this release

For information about the new or changed functionality in this release, see IBM
Tivoli Workload Scheduling Suite: General Information.

For information about the APARs that this release addresses, see IBM Tivoli
Workload Scheduler: Release Notes.

What is new in this publication

This section describes what has changed in this publication since version 8.3. It is
divided into the following sections:
v “What is new in this publication for Fix Pack 01”
v “What is new in this publication for Fix Pack 02” on page xiv

Note: Changed or added text is marked by a revision bar in the left margin.

What is new in this publication for Fix Pack 01

Part 6. Managing database objects
v Chapter 36, “Managing z/OS job streams,” on page 199 has been
updated with the “Deleting jobs simultaneously from a job stream” on
page 214 procedure.
v Chapter 37, “Managing distributed job streams,” on page 219 has been
updated with the “Deleting jobs simultaneously from a job stream” on
page 236 procedure.
Part 7. Managing plans
v Chapter 46, “Managing z/OS job stream instances,” on page 257 has
been updated to add the “Deleting jobs simultaneously from a job
stream instance” on page 260 procedure.
v Chapter 47, “Managing distributed job stream instances in the plan,” on
page 263 has been updated to add:
– The “Internetwork Predecessors page” on page 270 in the “Displaying
and changing the properties of a job stream instance” on page 264
– “Performing a cancel pending of a job stream instance” on page 275
– The “Deleting jobs simultaneously from a job stream instance” on
page 276 procedure.
v Chapter 49, “Managing distributed job instances in the plan,” on page
297 has been updated to add:
– The “Internetwork Predecessors page” on page 306 in the “Modifying
the properties of a job instance” on page 307.

© Copyright IBM Corp. 1991, 2006 xiii

What is new in this publication for Fix Pack 01

– The “Performing a cancel pending of a job instance” on page 320

procedure.

What is new in this publication for Fix Pack 02

For Fix Pack 02, the following additional changes have been made:
Part 1. Planning and Installation
v Chapter 2, “Planning and installing the Job Scheduling Console,” on
page 9 has been updated to reflect the new CDs for HP-UX for Integrity.
v Chapter 3, “Planning and installing the z/OS connector,” on page 15 has
been updated to improve the z/OS® connector installation procedure.
v Chapter 4, “Importing Job Scheduling Console user preferences,” on
page 17 has been updated to add the “Importing Job Scheduling Console
user preferences from versions prior to 8.3” on page 17 procedure.
Part 2. Getting Started
Chapter 7, “Job Scheduling Console objects and scheduling concepts,” on
page 27 has been updated to reflect the new z/OS functions.
Part 3. Quick Reference Guide
v Chapter 7, “Job Scheduling Console objects and scheduling concepts,” on
page 27 has been updated to reflect the new z/OS functions.
v Chapter 13, “Distributed quick reference,” on page 73 has been
improved.
Part 4. Defining objects
All the object definitions have been updated to reflect the new functions.
Part 5. Creating and using lists
All the lists have been updated to reflect the new functions.
Part 6. Managing database objects
All the procedure to manage objects have been updated to reflect the new
functions.
Part 7. Managing plans
All the chapters have been updated to reflect the new functions. In
particular,
v Chapter 48, “Managing z/OS job instances,” on page 277 has been
updated to add the following procedures:
– “Deleting a job instance” on page 288
– “Holding a job instance” on page 289
– “Releasing a job instance” on page 289
– “Killing a job instance running on a fault-tolerant agent” on page 291
– “Critical Path” on page 295
v Chapter 49, “Managing distributed job instances in the plan,” on page
297 has been updated to add the “Deleting a job instance” on page 316.
v Chapter 57, “Restoring a plan,” on page 347 has been added.
Part 9. Administration
This part has been added with the following content:
v Chapter 61, “Changing the TWSUser password for the z/OS connector,”
on page 409.
v Chapter 62, “Managing z/OS engines using WebSphere Application
Server tools,” on page 413.

xiv IBM Tivoli Workload Scheduler Job Scheduling Console: User’s Guide
 Audience

Who should read this publication

This guide is intended for the following audience:
v System administrators responsible for installing the Job Scheduling Console.
They should be familiar with one or more of the following operating systems:
Microsoft® Windows®
AIX®
HP-UX
Solaris Operating Environment
Linux®
v Administrators responsible for creating and updating object definitions and lists
in the scheduler database and plan.
v Operators responsible for monitoring the scheduler plan.

What this publication contains

This guide contains the following sections:

Part 1. Planning and installation

Part 1 provides the information needed to plan and install the Job Scheduling
Console. It contains the following chapters:
v Chapter 1, “Job Scheduling Console overview,” on page 3
Describes where the Job Scheduling Console fits in the topology of Tivoli
Workload Scheduler.
v Chapter 2, “Planning and installing the Job Scheduling Console,” on page 9
Describes how to plan and install the Job Scheduling Console.
v Chapter 3, “Planning and installing the z/OS connector,” on page 15
Describes how to plan and install the z/OS connector.
v Chapter 4, “Importing Job Scheduling Console user preferences,” on page 17
Describes how to migrate the Job Scheduling Console user preferences.
v Chapter 5, “Installing and adding language packs,” on page 21
Describes how to install and change languages.
v Chapter 6, “Uninstalling,” on page 23
Describes how to uninstall the various components that comprise the Job
Scheduling Console.

Part 2. Getting started

Part 2 provides an overview of the Job Scheduling Console and a quick start to
working with it. It contains the following chapters:
v Chapter 7, “Job Scheduling Console objects and scheduling concepts,” on page
27
Describes the objects that are created and managed using the Job Scheduling
Console.
v Chapter 8, “Job Scheduling Console task guide,” on page 37
Describes the tasks that you perform using the Job Scheduling Console, a flow
of the task order, and links to those tasks.
v Chapter 9, “Starting the Job Scheduling Console,” on page 45
Describes the information you need to sign on to the console.

About this publication xv

Guide contents

Part 3. Quick reference guide

Part 3 provides a three part quick reference guide that describes the interface,
working in a distributed environment, and working in a z/OS environment. It
contains the following chapters:
v Chapter 10, “Quick reference overview,” on page 53
Describes how the quick reference guide is organized.
v Chapter 11, “Interface quick reference,” on page 55
Describes the Job Scheduling Console interface.
v Chapter 12, “z/OS quick reference,” on page 65
Describes the quick steps you perform in the z/OS environment and then gives
more detail for each of those steps.
v Chapter 13, “Distributed quick reference,” on page 73
Describes the quick steps you perform in the distributed environment and then
gives more detail for each of those steps.
v Chapter 14, “Explorer View quick reference,” on page 87
Describes how to access the new Explorer View in the job stream editor.
v Chapter 15, “Troubleshooting quick reference,” on page 91
Describes the locations of the various log files.

Part 4. Defining objects

Part 4 provides the information necessary for you to define database objects, and
create the lists you use to manage them. It contains the following chapters:
v Chapter 16, “Creating engines,” on page 95
Describes how to create engines in the z/OS and distributed environments.
v Chapter 17, “Creating workstations,” on page 97
Describes how to create workstations in the z/OS and distributed environments.
v Chapter 18, “Creating resources,” on page 107
Describes how to create resources in the z/OS and distributed environments.
v Chapter 19, “Creating Windows users,” on page 113
Describes how to create Windows users in the distributed environment.
v Chapter 20, “Creating parameters,” on page 115
Describes how to create parameters in the distributed environment.
v Chapter 21, “Creating predefined prompts,” on page 117
Describes how to prompts in the distributed environment.
v Chapter 22, “Creating calendars,” on page 119
Describes how to create calendars for the distributed environment.
v Chapter 23, “Creating domains,” on page 123
Describes how to create domains for the distributed environment.
v Chapter 24, “Creating workstation classes,” on page 125
Describes how to create workstation classes in the distributed environment.
v Chapter 25, “Creating job definitions,” on page 127
Describes how to create job definitions in the distributed environment.
v Chapter 26, “Creating job streams,” on page 133
Describes how to create job streams in the z/OS and distributed environments.
v Chapter 27, “Creating forecast and trial plans,” on page 155

xvi IBM Tivoli Workload Scheduler Job Scheduling Console: User’s Guide
 Guide contents

Describes how to create forecast and trial plans in the distributed environment.
v Chapter 28, “Creating objects using Create Another,” on page 157
Describes how to clone objects in the z/OS and distributed environments.

Part 5. Creating and using lists

Part 5 provides the information necessary for you to create and use plan and
database lists. It contains the following chapters:
v Chapter 29, “Creating database lists,” on page 161
Describes how to create database lists.
v Chapter 30, “Creating plan lists,” on page 171
Describes how to create plan lists.
v Chapter 31, “Creating a group of lists,” on page 181
Describes how to create a group of lists.
v Chapter 32, “Creating common plan lists,” on page 183
Describes how to create plan lists that are common to z/OS and distributed
engines.
v Chapter 33, “Working with lists,” on page 185
Describes how to filter database and plan objects using lists.

Part 6. Managing database objects

Part 6 provides the information necessary for you to manage objects in the
database after you have created them. It contains the following chapters:
v Chapter 34, “Managing engines,” on page 191
Describes how to manage engines in the database.
v Chapter 35, “Managing workstations,” on page 197
Describes how to manage workstations in the database.
v Chapter 36, “Managing z/OS job streams,” on page 199
Describes how to manage z/OS job streams in the database.
v Chapter 37, “Managing distributed job streams,” on page 219
Describes how to manage distributed job streams in the database.
v Chapter 38, “Managing resources,” on page 239
Describes how to manage z/OS and distributed resources in the database.
v Chapter 39, “Managing job definitions,” on page 241
Describes how to manage distributed job definitions in the database.
v Chapter 40, “Managing workstation classes,” on page 243
Describes how to manage distributed workstation classes in the database.
v Chapter 41, “Managing domains,” on page 245
Describes how to manage distributed domains in the database.
v Chapter 42, “Managing Windows users,” on page 247
Describes how to manage distributed Windows users in the database.
v Chapter 43, “Managing calendars,” on page 249
Describes how to manage distributed calendars in the database.
v Chapter 44, “Managing prompts,” on page 251
Describes how to manage distributed prompts in the database.
v Chapter 45, “Managing parameters,” on page 253

About this publication xvii

Guide contents

Describes how to manage distributed parameters in the database.

Part 7. Managing plans

Part 7 provides the information necessary for you to manage objects in z/OS and
distributed plans. It contains the following chapters:
v Chapter 46, “Managing z/OS job stream instances,” on page 257
Describes how to manage z/OS job stream instances in the plan.
v Chapter 47, “Managing distributed job stream instances in the plan,” on page
263
Describes how to manage distributed job stream instances in the plan.
v Chapter 48, “Managing z/OS job instances,” on page 277
Describes how to manage z/OS job instances in the plan.
v Chapter 49, “Managing distributed job instances in the plan,” on page 297
Describes how to manage distributed job instances in the plan.
v Chapter 50, “Managing workstations in the plan,” on page 321
Describes how to manage workstations in the plan.
v Chapter 51, “Managing resources in the plan,” on page 331
Describes how to manage resources in the plan.
v Chapter 52, “Managing distributed file dependencies in the plan,” on page 337
Describes how to manage distributed file dependencies in the plan.
v Chapter 53, “Managing distributed prompt dependencies in the plan,” on page
339
Describes how to manage distributed prompt dependencies in the plan.
v Chapter 54, “Managing domains in the plan,” on page 341
Describes how to manage distributed domains in the plan.
v Chapter 55, “Changing Windows user passwords in the plan,” on page 343
Describes how to manage Windows user passwords in the plan.
v Chapter 56, “Setting an alternate plan,” on page 345
Describes how to set an alternate plan.
v Chapter 57, “Restoring a plan,” on page 347
Describes how to set an alternate plan.

Part 8. Troubleshooting

Part 8 provides troubleshooting information. It contains the following chapters:

v Chapter 58, “Setting traces for the Job Scheduling Console,” on page 351
Describes how to set traces for the Job Scheduling Console.
v Chapter 59, “Troubleshooting,” on page 353
Describes the most common problems and how they are resolved.
v Chapter 60, “Job Scheduling Console messages,” on page 357
Describes the messages.

Part 9. Administration

Part 9 provides information about administration activities. It contains the

following chapter:

xviii IBM Tivoli Workload Scheduler Job Scheduling Console: User’s Guide
 Guide contents

v Chapter 61, “Changing the TWSUser password for the z/OS connector,” on page
409
Describes how to change the TWSUser password.
v Chapter 62, “Managing z/OS engines using WebSphere Application Server
tools,” on page 413
Describes how to manage z/OS engines using WebSphere® Application Server
(WAS) tools.

Part 10. Appendixes

Part 9 provides general information. It contains the following appendixes:

v Appendix A, “Accessibility,” on page 417
Describes the accessibility features of the Job Scheduling Console.
v Appendix B, “Starting the Job Scheduling Console from an external application,”
on page 421
Describes how to start the Job Scheduling Console from an external application.
v Appendix D, “Status description and mapping,” on page 425
Describes job and job stream states within the Job Scheduling Console and how
to map between the console and engine states.
v Appendix E, “Support information,” on page 429
Describes how to contact IBM support.

Publications
This section lists publications in the Tivoli Workload Scheduler library and any other
related publications. It also describes how to access Tivoli publications online and
how to order Tivoli publications.

Tivoli Workload Scheduler library

Tivoli Workload Scheduler comprises several separate products available for a
variety of operating systems. The library is divided into:
IBM Tivoli Workload Scheduling suite library
This library contains all cross-platform and cross-product publications for
Tivoli Workload Scheduler.
IBM Tivoli Workload Scheduler distributed library
This library contains all of the publications that refer to the use of Tivoli
Workload Scheduler on operating systems other than z/OS.
IBM Tivoli Workload Scheduler for z/OS library
This library contains all publications that apply only to IBM Tivoli
Workload Scheduler for z/OS.
IBM Tivoli Workload Scheduler for Applications library
This library contains all publications that apply only to IBM Tivoli
Workload Scheduler for Applications.
IBM Tivoli Workload Scheduler for Virtualized Data Centers library
This library contains all publications that apply only to IBM Tivoli
Workload Scheduler for Virtualized Data Centers.

About this publication xix

Tivoli Workload Scheduling suite library

IBM Tivoli Workload Scheduling suite library

The following publications are available in the IBM Tivoli Workload Scheduling
suite library. This library includes publications that are common to all products,
operating systems, and components.
v IBM Tivoli Workload Scheduling Suite: General Information, SC32-1256
Provides general information about all Tivoli Workload Scheduler products. It
gives an overview of the way they can be used together to provide workload
management solutions for your whole enterprise.
v IBM Tivoli Workload Scheduler: Job Scheduling Console User’s Guide, SC32-1257
Describes how to work with Tivoli Workload Scheduler, regardless of operating
system, using a common GUI called the Job Scheduling Console.
v IBM Tivoli Workload Scheduler: Job Scheduling Console Release Notes, SC32-1258
Provides late-breaking information about the Job Scheduling Console.
v IBM Tivoli Workload Scheduler, version 8.3: Warehouse Enablement Pack version 1.1.1
Implementation Guide for Tivoli Data Warehouse, versions 1.2 and 1.3
Provides information about enabling Tivoli Workload Scheduler for Tivoli Data
Warehouse. This publication is only available on the Tivoli Workload Scheduler
Engine Installation CD 8, in the following path: TDW_enablement_pack/tdw_weps/
aws/v8300/doc/itws_for_TDW.doc
You cannot access it online, in the same way that you can the other books (see
“Accessing publications online” on page xxv).
v IBM Tivoli Dynamic Workload Console: Installation and Troubleshooting Guide,
SC32-1572
Describes how to install and uninstall the IBM Tivoli Dynamic Workload
Console in a Tivoli environment, and provides troubleshooting and message
information.

IBM Tivoli Workload Scheduler distributed library

The following publications are available in the IBM Tivoli Workload Scheduler
distributed library. This library contains publications that refer to using the product
on distributed operating systems (all operating systems except z/OS).
v IBM Tivoli Workload Scheduler: Read This First, GI11-6456
Provides a brief description of the contents of the IBM Tivoli Workload
Scheduler, Version 8.3 delivered package. It also indicates which CD is used to
install a specific component on a specific platform and provides a brief roadmap
of the documentation CD.
v IBM Tivoli Workload Scheduler: Release Notes, SC32-1277
Provides late-breaking information about Tivoli Workload Scheduler on
distributed operating systems.
v IBM Tivoli Workload Scheduler: Information Roadmap, GI11-6455
Provides a guide to where specific topics are described within the
documentation set for distributed operating systems.
v IBM Tivoli Workload Scheduler: Planning and Installation Guide, SC32-1273
Describes how to plan for and install IBM Tivoli Workload Scheduler on
distributed operating systems, and how to integrate Tivoli Workload Scheduler
with NetView®, Tivoli Data Warehouse, Tivoli Monitoring, and Tivoli Enterprise
Console®.

xx IBM Tivoli Workload Scheduler Job Scheduling Console: User’s Guide

 Tivoli Workload Scheduler distributed library

v IBM Tivoli Workload Scheduler: Reference Manual, SC32-1274

Describes the Tivoli Workload Scheduler command line used on distributed
operating systems, and how extended and network agents work.
v IBM Tivoli Workload Scheduler: Administration and Troubleshooting, SC32-1275
Provides information about how to administer Tivoli Workload Scheduler on
distributed operating systems, and what to do if things go wrong. It includes
help on many messages generated by the main components of Tivoli Workload
Scheduler.
v IBM Tivoli Workload Scheduler: Database Views, SC32-2261
Provides information about the views of the IBM Tivoli Workload Scheduler
database.
v IBM Tivoli Workload Scheduler: Using Microsoft Cluster Service on Windows Server
2003, SC23-6119
Describes how to use Tivoli Workload Scheduler with the Microsoft Cluster
service on Windows Server 2003 to achieve high availability.
v IBM Tivoli Workload Scheduler: Limited Fault-tolerant Agent for OS/400®, SC32-1280
Describes how to install, configure, and use Tivoli Workload Scheduler limited
fault-tolerant agents on AS/400®.
v Java™ API documentation.
Provides information about using the Java Application Programming Interface
(API). This is a set of available classes and methods running in a JAVA
environment that you use to create a custom interface to manage scheduling
objects in the database and in the plan. They cannot be used to manage the plan
or to set global options.
Documentation for the API is provided on all distributed product CDs. Mount
the CD for your platform and open the following file with your Internet
browser: <CD_drive>/API/doc/index.html.

See http://www.ibm.com/software/tivoli/products/scheduler/ for an

introduction to the product.

IBM Tivoli Workload Scheduler for z/OS library

The following publications are available in the Tivoli Workload Scheduler for z/OS
library:
v IBM Tivoli Workload Scheduler for z/OS: Getting Started, SC32-1262
Discusses how to define your installation data for Tivoli Workload Scheduler for
z/OS and how to create and modify plans.
v IBM Tivoli Workload Scheduler for z/OS: Installation Guide, SC32-1264
Describes how to install Tivoli Workload Scheduler for z/OS.
v IBM Tivoli Workload Scheduler for z/OS: Customization and Tuning, SC32-1265
Describes how to customize Tivoli Workload Scheduler for z/OS.
v IBM Tivoli Workload Scheduler for z/OS: Managing the Workload, SC32-1263
Explains how to plan and schedule the workload and how to control and
monitor the current plan.
v IBM Tivoli Workload Scheduler for z/OS: Quick Reference, SC32-1268
Provides a quick and easy consultation reference to operate Tivoli Workload
Scheduler for z/OS.

About this publication xxi

Tivoli Workload Scheduler for z/OS library

v IBM Tivoli Workload Scheduler for z/OS: Diagnosis Guide and Reference, SC32-1261
Provides information to help diagnose and correct possible problems when using
Tivoli Workload Scheduler for z/OS.
v IBM Tivoli Workload Scheduler for z/OS: Messages and Codes, SC32-1267
Explains messages and codes in Tivoli Workload Scheduler for z/OS.
v IBM Tivoli Workload Scheduler for z/OS: Programming Interfaces, SC32-1266
Provides information to write application programs for Tivoli Workload
Scheduler for z/OS.
v IBM Tivoli Workload Scheduler for z/OS: Scheduling End-to-end, SC32-1732
Provides information on how to integrate Tivoli Workload Scheduler for z/OS
with Tivoli Workload Scheduler, controlling workload in a distributed
environment from a z/OS master domain manager.
v IBM Tivoli Workload Scheduler for z/OS: Memo for Program 5697-WSZ, GI11-4209
Provides a summary of changes for the current release of the product.
v IBM Tivoli Workload Scheduler for z/OS: Program Directory for Program, GI11-4248
Provided with the installation tape for Tivoli Workload Scheduler for z/OS
(program number 5698-A17), describes all of the installation materials and gives
installation instructions specific to the product release level or feature number.
v IBM Tivoli Workload Scheduler for z/OS: Master Index, GI11-6463
Provides a master index for the whole Tivoli Workload Scheduler for z/OS
library.

See http://www.ibm.com/software/tivoli/products/scheduler-zos/ for an

introduction to the product.

IBM Tivoli Workload Scheduler for Applications library

The following publications are available in the IBM Tivoli Workload Scheduler for
Applications library:
v IBM Tivoli Workload Scheduler for Applications: User’s Guide, SC32-1278
Provides information on how to install, set up, and use the IBM Tivoli Workload
Scheduler access methods that run and control jobs of the following applications:
– Oracle
– PeopleSoft
– R/3
– z/OS
v IBM Tivoli Workload Scheduler for Applications: Quick Start Guide
Gives an overview on how to get started with Tivoli Workload Scheduler for
Applications.

There is now no Release Notes document for Tivoli Workload Scheduler for
Applications. The information previously found in this document has been
relocated, as follows:
v All information that would help you decide whether you wanted to install and
use the release has been moved to the download document (for example,
hardware and software requirements and APARS fixed). To locate the download
document, see Step 1 in the IBM Tivoli Workload Scheduler for Applications: Quick
Start Guide.
v All information that tells you how to use this release or integrate it with other
releases of this product, or other products, can be found in the IBM Tivoli
Workload Scheduler for Applications: User’s Guide.

xxii IBM Tivoli Workload Scheduler Job Scheduling Console: User’s Guide
 Tivoli Workload Scheduler for Applications library

See http://www.ibm.com/software/tivoli/products/scheduler-apps/ for an

introduction to the product.

IBM Tivoli Workload Scheduler for Virtualized Data Centers

library
The following publications are available in the IBM Tivoli Workload Scheduler for
Virtualized Data Centers library:
v IBM Tivoli Workload Scheduler for Virtualized Data Centers: User’s Guide, SC32-1454
Describes how to extend the scheduling capabilities of Tivoli Workload
Scheduler to workload optimization and grid computing by enabling the control
of IBM LoadLeveler® and IBM Grid Toolbox jobs.
v IBM Tivoli Workload Scheduler for Virtualized Data Centers: Release Notes, SC32-1453
Provides late-breaking information about Tivoli Workload Scheduler for
Virtualized Data Centers.
See http://www.ibm.com/software/info/ecatalog/en_US/ products/
Y614224T20392S50.html for an introduction to the product.

Related publications
The following publications provide additional information:
v IBM Redbooks™: Getting Started with IBM Tivoli Workload Scheduler V8.3: Best
Practices and Performance Improvements, SG24-7237
Abstract: IBM Tivoli Workload Scheduler is an IBM strategic scheduling product
that runs on different platforms including the mainframe. The new version of
the product, IBM Tivoli Workload Scheduler V8.3, comes with some important
enhancements, such as relational database management system support, new
advanced planning system, which allows the definition of plans that span more
that 24 hours, removal of framework requirements, new application
programming interface (API), Job Scheduling Console enhancements, and so on.
This IBM Redbook documents the architecture, deployment, best practices, and
migration scenarios for IBM Tivoli Workload Scheduler V8.3 in a distributed
environment. In addition, it covers IBM Tivoli Workload Scheduler V8.3 security,
IBM DB2® and IBM WebSphere considerations, troubleshooting, tuning for
performance, application programming interface, and JnextPlan, which has
replaced the JnextDay process in this release.
Clients and Tivoli professionals who are responsible for installing, administering,
maintaining, or using IBM Tivoli Workload Scheduler V8.3 will find this book a
major reference.
This Redbook can be found on the Redbooks Web site at http://
www.redbooks.ibm.com/abstracts/sg247237.html
v IBM Redbooks: Customizing IBM Tivoli Workload Scheduler for z/OS V8.2 to Improve
Performance, SG24-6352
Abstract: This IBM Redbook covers the techniques that can be used to improve
the performance of Tivoli Workload Scheduler for z/OS (including end-to-end
scheduling).
This Redbook can be found on the Redbooks Web site at http://
www.redbooks.ibm.com/abstracts/sg246352.html
v IBM Redbooks: IBM Tivoli Workload Scheduler for z/OS: Best Practices, SG24-7156
Abstract: This IBM Redbook describes best practices for using Tivoli Workload
Scheduler for z/OS. Topics covered include:
– Installation best practices
– Installation verification
– Started tasks
About this publication xxiii
Related publications

– Communication
– Initialization statements and parameters
– Security
– Exits
– Restart and cleanup
– Dataset triggering and event trigger tracking
– Variables
– Audit report facility
This Redbook can be found on the Redbooks Web site at http://
www.redbooks.ibm.com/abstracts/sg247156.html
v IBM Redbooks: Integrating IBM Tivoli Workload Scheduler with Tivoli Products,
SG24-6648
Abstract: This IBM Redbook explains the benefits and technical merits of
integrating IBM Tivoli Workload Scheduler Distributed and IBM Tivoli Workload
Scheduler for z/OS with other IBM products. Scheduling is a mission critical
process for any company. However, when you talk about scheduling, you are
really talking about an ecosystem. In this ecosystem, each solution is a building
block that adds value to the overall solution. With IBM Tivoli Workload
Scheduler, you can collect and add data to and from each component. In
addition, expanding the scheduling ecosystem to include monitoring,
management, help desk, storage, and business systems management provides
greater value.
This book discusses all these integration points and provides detailed scenarios
on how to integrate IBM Tivoli Workload Scheduler with these types of
applications. Because workload management is widely considered the nucleus of
the data center, there are numerous opportunities for you to integrate IBM Tivoli
Workload Scheduler with other products. This book addresses just some of these
many opportunities. In terms of integration with IBM Tivoli Workload Scheduler,
do not limit yourself to the products that this book discusses. Integration points
discussed in this book should give you an idea of the potential value that IBM
Tivoli Workload Scheduler integration can provide for your company.
This Redbook can be found on the Redbooks Web site at http://
www.redbooks.ibm.com/abstracts/sg246648.html
v IBM Redbooks: WebSphere Application Server V6 System Management & Configuration
Handbook, SG24-6451
Abstract: This IBM Redbook provides system administrators, developers, and
architects with the knowledge to configure a WebSphere Application Server V6
runtime environment, to package and deploy Web applications, and to perform
ongoing management of the WebSphere environment.
One in a series of handbooks, the entire series is designed to give you in-depth
information about the entire range of WebSphere Application Server products. In
this book, we provide a detailed exploration of the WebSphere Application
Server V6 runtime environments and administration process.
This Redbook can be found on the Redbooks Web site at http://
www.redbooks.ibm.com/abstracts/sg246451.html

The Tivoli Software Glossary includes definitions for many of the technical terms
related to Tivoli software. The Tivoli Software Glossary is available, in English only,
at the following Web site:

http://publib.boulder.ibm.com/tividd/glossary/termsmst04.htm

xxiv IBM Tivoli Workload Scheduler Job Scheduling Console: User’s Guide
 Accessing publications online

Accessing publications online

The Tivoli Workload Scheduler documentation CD contains the publications that
are in the product library. The format of the publications is PDF, HTML, or both.
The publications are found within a Tivoli Information Center. Place the CD in the
CD drive of a Windows computer and the Information Center automatically opens.
If the Information Center does not open automatically, or you require more
information, consult the readme.txt file in the root of the CD.

IBM posts publications for this and all other Tivoli products, as they become
available and whenever they are updated, to the Tivoli software information center
Web site. There are two ways of accessing the Tivoli software information center:
Directly access the IBM Tivoli Workload Scheduler Information Center
Go directly to the Information Center at the following Web address:
http://publib.boulder.ibm.com/infocenter/tivihelp/v3r1/index.jsp?toc=/
com.ibm.tivoli.itws.doc/toc.xml
Access the IBM Tivoli Workload Scheduler Information Center from the Tivoli
Technical Product Documents Web site
Access the Tivoli software information center by following these steps:
1. Go to the Tivoli library at the following Web address:
http://www.ibm.com/software/tivoli/library/
2. Click Tivoli product manuals
3. In the Tivoli Technical Product Documents Alphabetical Listing
window, click W (for Workload Scheduler) or scroll down to the W
section of the product list
4. Click the appropriate Tivoli Workload Scheduler product link to access
your product libraries at the Tivoli software information center. All
publications in the Tivoli Workload Scheduler suite library, distributed
library, and z/OS library can be found under the entry Tivoli Workload
Scheduler. The Tivoli software information center page for Tivoli
Workload Scheduler is displayed. It gives you access to the publications
relating to the latest version of the product. Links are provided to the
documentation of prior versions.

5. Click to access the Tivoli Workload Scheduler Information Center.

The Information Center is Eclipse-based, and contains full instructions
on how to use it to obtain information and search the publications for
specific terms.

Note: If you print PDF publications on other than letter-sized paper, set the option
in the File → Print window that enables Adobe Reader to print letter-sized
pages on your local paper.

For all types of information about DB2, go to the DB2 Information Center:
http://publib.boulder.ibm.com/infocenter/db2luw/v8//index.jsp

For all types of information about the embedded version of WebSphere Application
Server, go to the WebSphere Application Server Information Center:
http://publib.boulder.ibm.com/infocenter/wasinfo/v6r0/index.jsp

For all types of information about the Oracle database, consult the documentation
of Oracle Corporation. When this manual was published, the relevant
documentation could be found on http://www.oracle.com/technology/
documentation/index.html.

About this publication xxv

Accessing publications online

Note: This information has been included as a courtesy, and IBM cannot guarantee
that this URL will continue to be correct.

Tivoli Workload Scheduler online books

All the books in the Tivoli Workload Scheduler for z/OS library are available in
displayable softcopy form on CD in the IBM Online Library: z/OS Software Products
Collection Kit, SK3T-4270. You can read the softcopy books on CD using these IBM
licensed programs:
v BookManager® READ/2 (program number 5601-454)
v BookManager READ/DOS (program number 5601-453)
v BookManager READ/6000 (program number 5765-086)
All the BookManager programs need a personal computer equipped with a CD
drive (capable of reading disks formatted in the ISO 9660 standard) and a
matching adapter and cable. For additional hardware and software information,
refer to the publications for the specific BookManager product you are using.

Updates to books between releases are provided in softcopy only.

Ordering publications
You can order many Tivoli publications online at the following Web site:
http://www.elink.ibmlink.ibm.com/public/applications/ publications/cgibin/
pbi.cgi

You can also order by telephone by calling one of these numbers:

v In the United States: 800-879-2755
v In Canada: 800-426-4968
v In other countries, contact your software account representative to order Tivoli
publications. To locate the telephone number of your local representative
perform the following steps:
1. Go to the following Web site:
http://www.elink.ibmlink.ibm.com/public/applications/
publications/cgibin/pbi.cgi
2. Select your country from the list and click . The IBM Publications Center
page is displayed.
3. Click About this site in the main panel to see an information page which
includes the telephone number of your local representative.

Accessibility
Accessibility features help users with a physical disability, such as restricted
mobility or limited vision, to use software products successfully. With this product,
you can use assistive technologies to hear and navigate the interface. You can also
use the keyboard instead of the mouse to operate all features of the graphical user
interface.

For additional information, see Appendix A, “Accessibility,” on page 417.

xxvi IBM Tivoli Workload Scheduler Job Scheduling Console: User’s Guide
 Training

Tivoli technical training

For Tivoli technical training information, refer to the following IBM Tivoli
Education Web site:

http://www.ibm.com/software/tivoli/education

Support information
If you have a problem with your IBM software, you want to resolve it quickly. IBM
provides the following ways for you to obtain the support you need:
v Searching knowledge bases: You can search across a large collection of known
problems and workarounds, Technotes, and other information.
v Obtaining fixes: You can locate the latest fixes that are already available for your
product.
v Contacting IBM Software Support: If you still cannot solve your problem, and
you need to work with someone from IBM, you can use a variety of ways to
contact IBM Software Support.

For more information about these three ways of resolving problems, see
Appendix E, “Support information,” on page 429.

Conventions used in this publication

This publication uses several conventions for special terms and actions, operating
system-dependent commands and paths, command syntax, and margin graphics.

Typeface conventions
This publication uses the following typeface conventions:
Bold
v Lowercase commands and mixed case commands that are otherwise
difficult to distinguish from surrounding text
v Interface controls (check boxes, push buttons, radio buttons, spin
buttons, fields, folders, icons, list boxes, items inside list boxes,
multicolumn lists, containers, menu choices, menu names, tabs, property
sheets), labels (such as Tip:, and Operating system considerations:)
v Keywords and parameters in text
Italic
v Words defined in text
v Emphasis of words (words as words)
v New terms in text (except in a definition list)
v Variables and values you must provide
Monospace
v Examples and code examples
v File names, programming keywords, and other elements that are difficult
to distinguish from surrounding text

About this publication xxvii

Conventions

v Message text and prompts addressed to the user

v Text that the user must type
v Values for arguments or command options

Operating system-dependent variables and paths

This publication uses the UNIX® convention for specifying environment variables
and for directory notation.

When using the Windows command line, replace $variable with % variable% for
environment variables and replace each forward slash (/) with a backslash (\) in
directory paths. The names of environment variables are not always the same in
Windows and UNIX environments. For example, %TEMP% in Windows is
equivalent to $tmp in UNIX environments.

Note: If you are using the bash shell on a Windows system, you can use the UNIX
conventions.

Command syntax
This publication uses the following syntax wherever it describes commands:
Table 1. Command syntax
Syntax Description Example
convention
Name of The first word or set of consecutive conman
command characters.
Brackets ([ The information enclosed in brackets [-file definition_file]
]) ([ ]) is optional. Anything not
enclosed in brackets must be
specified.
Braces ({ }) Braces ({ }) identify a set of mutually {-prompts | -prompt prompt_name }
exclusive options, when one option is
required.
Underscore An underscore (_) connects multiple prompt_name
(_) words in a variable.
Vertical bar Mutually exclusive options are {-prompts | -prompt prompt_name }
(|) separated by a vertical bar ( | ).

You can enter one of the options

separated by the vertical bar, but you
cannot enter multiple options in a
single use of the command.
Bold Bold text designates literal composer add file_name
information that must be entered on
the command line exactly as shown.
This applies to command names and
non-variable options.
Italic Italic text is variable and must be file_name
replaced by whatever it represents. In
the example to the right, the user
would replace file_name with the
name of the specific file.

xxviii IBM Tivoli Workload Scheduler Job Scheduling Console: User’s Guide
 Conventions

Table 1. Command syntax (continued)

Syntax Description Example
convention
Ellipsis (...) An ellipsis (...) indicates that the [–x file_name]...
previous option can be repeated
multiple times with different values. It An ellipsis outside the brackets
can be used inside or outside of indicates that –x file_name is optional
brackets. and may be repeated as follows: –x
file_name1 –x file_name2–x file_name3

[–x file_name...]

An ellipsis inside the brackets

indicates that –x file_name is optional,
and the file variable can be repeated
as follows: –x file_name1 file_name2
file_name3

–x file_name [–x file_name]...

An ellipsis used with this syntax

indicates that you must specify –x
file_name at least once.

About this publication xxix

Conventions

xxx IBM Tivoli Workload Scheduler Job Scheduling Console: User’s Guide
Part 1. Planning and installation

© Copyright IBM Corp. 1991, 2006 1

2 IBM Tivoli Workload Scheduler Job Scheduling Console: User’s Guide
Chapter 1. Job Scheduling Console overview
This chapter describes the overall topology of Tivoli Workload Scheduler and
where the Job Scheduling Console fits into that topology. It is divided into the
following sections:
v “Tivoli Workload Scheduler topology”
v “Setting your local time zone” on page 34

Tivoli Workload Scheduler topology

The Job Scheduling Console is an interface for creating, modifying, monitoring,
controlling, and deleting Tivoli Workload Scheduler objects.

Although the Job Scheduling Console is part of the Tivoli Workload Scheduler
distributed topology, you can use it to work with both z/OS and distributed
engines.

For a definition of the components of a Tivoli Workload Scheduler network, see

IBM Tivoli Workload Scheduling Suite: General Information.

Where the Job Scheduling Console fits in the topology

Your Tivoli Workload Scheduler topology can be complex or simple according to
your job scheduling requirements.

Figure 1 on page 4 shows a single tier hierarchy in a distributed environment,

where the agents are directly connected to the master domain manager.

© Copyright IBM Corp. 1991, 2006 3

Topology

JSC
Master
Domain
Manager

Agents

AIX Linux Windows Solaris

Figure 1. Single tier topology

Figure 2 on page 5 shows a multi–tier hierarchy in a distributed environment

where the agents are connected to a domain manager at the various tiers of the
topology.

4 IBM Tivoli Workload Scheduler Job Scheduling Console: User’s Guide

 Topology

Master Domain

JSC Master Backup

Domain Master
Manager

Agent

DomainA DomainB

Domain Domain
Backup
Manager Manager
Domain
Manager

Agent Agent Agent Agent

DomainC DomainD DomainE

Domain Domain Domain

Manager Manager Manager

Agent Agent Agent Agent Agent Agent

Figure 2. Multi-tier topology

Domain A is the parent domain for domain C, and domain B is the parent domain
for domains D and E.

Chapter 1. Job Scheduling Console overview 5

 Topology

Figure 3 shows an end-to-end topology with the Job Scheduling Console connected
to the z/OS master domain.

OPCMASTER
z/OS
JSC
Master
Domain
Manager

DomainZ

Domain
AIX
Manager

DomainA DomainB

AIX Domain Domain HPUX

Manager Manager

Agent Agent Agent Agent

Figure 3. End-to-end topology with Job Scheduling Console

Connection
Normally you connect the Job Scheduling Console to the master domain manager,
however, you can connect to a domain manager or a fault-tolerant agent.

| The Job Scheduling Console connects to engines through the embedded version of
| WebSphere Application Server - Express and the relevant connector. When
| connection is involved, if you want to use the Job Scheduling Console on a
| fault-tolerant agent directly, you need to install a connector for the distributed
| connection, as illustrated in Figure 4 on page 7. The Job Scheduling Console
| communicates with the engine through the connector that translates Job Scheduling
| Console instructions into scheduler commands.
|

6 IBM Tivoli Workload Scheduler Job Scheduling Console: User’s Guide

 Connection

JSC

WebSphere Application WebSphere Application

Server Server

z/OS Distributed
connector connector

|
| Figure 4. Job Scheduling Console connection
|
| You can manage database objects using the Job Scheduling Console connected to a
| master or you can manage plan objects using the Job Scheduling Console
| connected to a master or to agent workstations.

Chapter 1. Job Scheduling Console overview 7

Connection

8 IBM Tivoli Workload Scheduler Job Scheduling Console: User’s Guide

 Chapter 2. Planning and installing the Job Scheduling
Console
This chapter describes installation of the Job Scheduling Console. It is divided into
the following sections:
v “Planning installation of the Job Scheduling Console”
v “Installing using the installation wizard” on page 10
v “Installing using Software Distribution” on page 12

Planning installation of the Job Scheduling Console

The Job Scheduling Console can be installed on any workstation that has a TCP/IP
connection. For information about supported platforms and system requirements,
refer to the Release Notes.

Do not install more than one instance of the Job Scheduling Console on each
computer, for example by logging on as a different user. Although this does not
create problems for running the Job Scheduling Console, it does cause difficulties
when migrating or uninstalling.

The connectors for the distributed environment are installed with the engine. For
information about installing them, see IBM Tivoli Workload Scheduler: Planning and
Installation Guide. For information about installing the z/OS connectors, see
Chapter 3, “Planning and installing the z/OS connector,” on page 15.

The installation CDs

There are the following Job Scheduling Console installation CDs:
CD 1 Contains the INSTALLER and LANG_PACK directories for Linux, Linux
PPC, and Windows, and the RESPONSE_FILE directory required for
performing a silent installation.
CD 2 Contains the INSTALLER and LANG_PACK directories for AIX, HP-UX
for PA-RISC, and Solaris, and the RESPONSE_FILE directory required
for performing a silent installation.
CD 3 Contains the software package blocks for the Java Virtual Machine
installation.
| CD 4 Contains the INSTALLER and LANG_PACK directories for HP-UX for
| Integrity, and the RESPONSE_FILE directory required for performing
| a silent installation.

There are the following z/OS connector installation CDs:

CD 1 Contains the connector installation directories for AIX and Solaris,
and the RESPONSE_FILE directory required for performing a silent
installation.
CD 2 Contains the connector installation directories for Linux I386 and
Windows, and the RESPONSE_FILE directory required for performing
a silent installation.
CD 3 Contains the connector installation directories for Linux s390,

© Copyright IBM Corp. 1991, 2006 9

 Installation CDs

Linux PPC, and Windows, and the RESPONSE_FILE directory

required for performing a silent installation.
CD 4 Contains the connector installation directories for HP-UX for
PA-RISC, and the RESPONSE_FILE directory required for performing
a silent installation.
| CD 5 Contains the connector installation directories for HP-UX for
| Integrity, and the RESPONSE_FILE directory required for performing
| a silent installation.

Installation methods
You can use the following methods to install the Job Scheduling Console:
v “ISMP Installation wizard”
v “Software Distribution”

ISMP Installation wizard

When you are installing the Job Scheduling Console on a single workstation, you
can use the installation wizard in interactive or silent mode. In interactive mode,
the wizard guides you through the installation steps. In silent mode a response file
provides the relevant information to the install process, which is run in
background without user intervention. For information about installing using the
wizard, see “Installing using the installation wizard.”

Software Distribution
When you are installing the Job Scheduling Console on more than one workstation
simultaneously, you can use a software package block (SPB) of Tivoli Configuration
Manager in interactive or silent mode. In interactive mode, the Tivoli Desktop
guides you through the installation steps. In silent mode, you can use a connected
Tivoli Configuration Manager command line interface. For information about
installing using Software Distribution, see “Installing using Software Distribution”
on page 12 and IBM Tivoli Configuration Manager, User’s Guide for Software
Distribution.

Installing using the installation wizard

Using the wizard you can install directly from the CDs. On UNIX operating
systems, you can copy the CD to a file system and mount that file system. On
Windows operating systems, you can copy the CD to a network drive and map
that network drive.

Installation uses a temporary directory for ISMP and a temporary directory for the
Job Scheduling Console. You can set the installation wizard temporary directory
using the -is:tempdirdirectory_name. The Job Scheduling Console temporary
directory contains the installation log files. See “Job Scheduling Console installation
log” on page 353.

This section is divided into the following subsections:

v “Installing the Job Scheduling Console in interactive mode” on page 11
v “Installing the Job Scheduling Console in silent mode” on page 11

When you are installing onto Windows operating systems using the installation
wizard, perform the following steps before starting the installation:
1. Click Start  Run in the Windows task bar.
2. Type dxdiag and click OK.

10 IBM Tivoli Workload Scheduler Job Scheduling Console: User’s Guide

 Using the installation wizard

The DirectX Diagnostic tool opens.

3. Click on Display and disable DirectDraw Acceleration and Direct3D
Acceleration.

Installing the Job Scheduling Console in interactive mode

To perform a first-time product installation, complete the following steps:
1. Insert the relevant CD in the CD ROM drive. See “The installation CDs” on
page 9.
2. Navigate to the <operating_system>\INSTALLER directory.
3. Run the installation executable:
v Windows operating systems: setup.exe
v UNIX and Linux operating systems: ./setup.bin
4. Select the language of the installation wizard. Click OK.
5. Read the welcome information. Click Next.
6. Read and accept the license agreement. Click Next.
7. Accept the default installation directory, or click Browse, or type the path
name to select a different directory. Click Next.

Note: The Job Scheduling Console installation directory inherits the access
rights of the directory where the installation is performed. Because the
Job Scheduling Console requires user settings to be saved, it is
important to select a directory in which users are granted access rights.
8. Select the locations for the Job Scheduling Console icons. Click Next.
9. Review the installation settings. Click Next. The installation is started.
When the installation completes, a panel displays a successful installation or
contains a list of items that failed to install and the location of the log file. See
“Job Scheduling Console installation log” on page 353.
10. Click Finish.

Installing the Job Scheduling Console in silent mode

Silent installation allows you to install in background.

A template for a response file is provided in the <CD>\RESPONSE_FILE directory. See

“The installation CDs” on page 9. You can copy the response file to your system
and edit it as required. Instructions for editing the response file are provided in the
response file itself.

The following options are available:

v Installation location
v Icon location
v Whether to overwrite existing Java Virtual Machine

To start the installation in silent mode on Windows systems, navigate to the

directory where the setup.exe file resides and enter the following command:
setup.exe -silent -options filename

To start the installation in silent mode on UNIX and Linux operating systems,
navigate to the directory where the setup file is located and enter the following
command:
./setup.bin -silent -options filename

Chapter 2. Planning and installing the Job Scheduling Console 11

 Installing the Job Scheduling Console in interactive mode

specifying the fully qualified path to the response file.

Notes:
1. The parameters of the silent installation are described in detail as comments in
the response file.
2. When you perform a silent installation on Windows you must use the Task
Manager to check if the installation is running.
3. When you perform a silent installation on UNIX you must use the ps
command to check if the installation is running.

Installing using Software Distribution

The Job Scheduling Console can be installed by distributing a software package
block (SPB) using the software distribution component of Tivoli Configuration
Manager, Version 4.1, 4.2, and 4.2.1. You can distribute the SPB locally or remotely,
using either the command line interface or the Tivoli desktop.

On the Tivoli Workload Scheduler Job Scheduling Console CD 1, locate the

directory of the platform where you want to install the Job Scheduling Console.
The following two software package blocks exist for each supported platform:
TWSConsole.spb
Installs the Job Scheduling Console.
TWSConsoleLanguages.spb
Installs one or more language packs.

| The Job Scheduling Console parameter used by the software package block to
| define the installation directory is the INSTALL_DIR variable. This variable is
| defined as a default variable in the software package and assumes a different value
| depending on the operating system you are working on as shown in Table 2. The
| INSTALL_DIR variable represents the fully qualified path to the location of the Job
| Scheduling Console installation. The INSTALL_DIR variable is optional because the
| path is created if it does not already exist.
| Table 2. Default variable value for operating system
| Default variable value Operating system
| INSTALL_DIR_Linux Linux
| INSTALL_DIR_Windows_NT Windows
| INSTALL_DIR_AIX AIX
| INSTALL_DIR_HP-UX HP-UX
| INSTALL_DIR_SunOS Solaris
|

| The INSTALL_DIR variable is resolved to the appropriate value depending on the

operating system where you are installing. Default values for each operating
system are listed in the Table 3. When you specify the INSTALL_DIR variable it
overrides the operating system variables.
Table 3. Operating system variables
Default variable Default value
INSTALL_DIR_Linux /opt/JSC_8_3
INSTALL_DIR_Windows_NT $(program_files)\JSC_8_3
INSTALL_DIR_AIX /opt/JSC_8_3

12 IBM Tivoli Workload Scheduler Job Scheduling Console: User’s Guide

 Using Software Distribution

Table 3. Operating system variables (continued)

Default variable Default value
INSTALL_DIR_HP-UX /opt/JSC_8_3
INSTALL_DIR_SunOS /opt/JSC_8_3

All languages are installed by default. Table 4 describes the language variables.
Table 4. Language variables
Language variable Description
de German
es Spanish
fr French
it Italian
ko Korean
ja Japanese
pt_BR Brazilian Portuguese
zh_CN Simplified Chinese
zh_TW Traditional Chinese

To perform the installation, complete the following steps:

1. Import the software package block.
2. Install the software package block.
For complete instructions on performing these tasks, refer to the Tivoli Configuration
Manager, User’s Guide for Software Distribution.

Installing the Java Virtual Machine

When you install using software distribution, the Java Virtual Machine is not
installed together with the Job Scheduling Console. You have to install it separately
after installing the Job Scheduling Console using the software package blocks
provided on CD 3 in the JVM_CM folder. A software package block is provided for
each supported operating system.

| Note: You are required to install this version of the Java Virtual Machine even if
| you have another Java Virtual Machine already installed on your computer.

The Java Virtual Machine software packages are to be installed in the Job
Scheduling Console installation directory.

To perform the installation, complete the following steps:

1. Import the software package block.
2. Install the software package block.
For complete instructions on performing these tasks, refer to the Tivoli Configuration
Manager, User’s Guide for Software Distribution.

To install the Java Virtual Machine using software packages, enter the following
command:
winstsp –f JRE142_operatingsystem.spb
-D install_dir

Chapter 2. Planning and installing the Job Scheduling Console 13

Using Software Distribution

where:
JRE142_operatingsystem.spb
Specifies the path to the directory where the Java Virtual Machine
software package for each supported operating system is located.
install_dir Specifies the installation directory of the Job Scheduling Console.

14 IBM Tivoli Workload Scheduler Job Scheduling Console: User’s Guide

 Chapter 3. Planning and installing the z/OS connector
This chapter describes installation of the z/OS connector. It is divided into the
following sections:
v “Planning connector installations”
v “Installing the z/OS connector”

Note: For information about installing the connector for distributed engines, refer
to IBM Tivoli Workload Scheduler: Planning and Installation Guide.

Planning connector installations

The z/OS connector requires the embedded version of WebSphere Application
Server - Express version 6.0.

If you have a previous version of the z/OS connector installed, uninstall it before
you install the new version.

| Installing the z/OS connector

| To install the connector, perform the following steps:
| 1. Insert the relevant CD in the CD-ROM drive. See “The installation CDs” on
| page 9.
| 2. Navigate to the operating system directory.
| 3. Run the setup according to the operating system where you are installing:
| v Windows: setup.exe
| v UNIX: setup
| 4. Select the language of the installation wizard. Click OK.
| 5. Read the Welcome information. Click Next. The installation verifies that you
| have the necessary rights to perform the installation. The installation checks
| for previous installations of WebSphere Application Server Express and the
| connectors.
| 6. Read and accept the license agreement. Click Next.
| 7. Specify the user name and password of the TWSuser for which you are
| installing the connector. In Windows if the specified user does not exist it is
| created with the permission necessary to work with Tivoli Workload
| Scheduler. Click Next.
| 8. Browse for or type the directory where you want to install the z/OS
| connector.
| 9. Specify the relevant port data. Possible values are:
| HTTP Transport
| Set the port composer uses when the HTTP protocol is
| selected. The default value is 31125.
| HTTPS Transport
| Set the port composer uses when the HTTPS protocol is
| selected. The default value is 31126.

© Copyright IBM Corp. 1991, 2006 15

 Using the installation wizard

| Bootstrap / RMI
| Set the port the Job Scheduling Console uses when bootstrap
| / RMI protocol is selected. The default value is 31127.
| SOAP Connector
| Set the port the SOAP connector uses. The default value is
| 31128.

| Use the defaults unless you are sure they are already in use. Click Next.
| 10. Select Configure a connection to a Tivoli Workload Scheduler for z/OS host
| to supply connection configuration data to configure the z/OS connector. If
| you do not select it you can create the connector instance later using the
| createZosEngine WAS tool: Possible values are:
| Tivoli Workload Scheduler for z/OS Engine Name
| The name of the new instance.
| Tivoli Workload Scheduler for z/OS Remote Host
| The IP address or host name of the remote z/OS system
| where the scheduler subsystem is installed.
| Tivoli Workload Scheduler for z/OS Remote TCP/IP Port
| The TCP/IP port number of the remote z/OS system.

| Click Next.
| 11. Review the installation settings and click Next. The installation is started.
| When the installation completes, a panel displays a successful installation or
| contains a list of the items that failed to install and the location of the log file.
| 12. Click Finish.

| Performing a silent installation

| You use silent installation to install in background.

| A template for a response file is provided on the installation CDs in the

| RESPONSE_FILE folder. You can copy the response file to your system and edit it as
| necessary. See “The installation CDs” on page 9.

| The following options are available in the response file:

| v WebSphere Application Server Express installation location
| v Connector instance creation

| To install in silent mode on Windows, navigate to the directory where the

| setup.exe file resides and enter the following command:
| setup.exe -silent -options filename

| To install in silent mode on UNIX, navigate to the directory where the setup.bin
| enter the following command:
| ./setup -silent -options filename

| specifying the fully qualified path to the response file.

| Note: The silent installation parameters are described in detail as comments in the
| response file.

16 IBM Tivoli Workload Scheduler Job Scheduling Console: User’s Guide

|

Chapter 4. Importing Job Scheduling Console user

preferences
This chapter describes how to import user preferences from existing Job
Scheduling Console versions to Job Scheduling Console version 8.3. Because of a
change of the database of Tivoli Workload Scheduler from a flat database to DB2, it
is not possible to upgrade existing versions of the Job Scheduling Console. You
must install the Job Scheduling Console version 8.3 and then import the user
preferences.

The user preferences in version 8.3 are contained in the preferences.xml and
Engines.xml files. These files are stored in user_home_directory/.twsconsole/
userdata. The chapter is divided into the following sections:
v “Importing Job Scheduling Console user preferences from versions 8.3” on page
18
v “Importing Job Scheduling Console user preferences from versions prior to 8.3”

| Importing Job Scheduling Console user preferences from versions

| prior to 8.3
| To import Job Scheduling Console user preferences from versions prior to 8.3,
| perform the following steps:
| 1. Open the user_home_directory/.tmeconsole/username@hostname_language/
| preferences.xml user preferences file.
| 2. Change all the occurrences of node name to reflect the engine names you
| defined in the preferences.xml file of the version of the Job Scheduling Console
| you are importing. For example, if you are importing your preferences file from
| version 8.2.1 to version 8.3 and in version 8.2.1 the node name was
| zos821Engine and in version 8.3 it is zos83Engine change all the node name
| occurrences from:
| <node name="zos821Engine>
| <map/>
| </node>

| to
| <node name="zos83Engine>
| <map/>
| </node>
| 3. Start the Job Scheduling Console version 8.3. See Chapter 9, “Starting the Job
| Scheduling Console,” on page 45.
| The Load Preferences file panel displays.

© Copyright IBM Corp. 1991, 2006 17

 Importing Job Scheduling Console user preferences from versions prior to 8.3

|
| 4. Browse to the user_home_directory/.twsconsole and select the
| preferences.xml file.
| 5. Leave the Engine files field blank.
| 6. Click OK.
| The Job Scheduling Console main window opens.
|

|
| 7. Verify that all the engines and lists you defined in the previous version are
| present.
| You can now use the preferences.xml and Engines.xml files as common files for
| each of the Job Scheduling Console instances that require the same connection
| profiles.

| Importing Job Scheduling Console user preferences from versions 8.3

| To import user preferences from a Job Scheduling Console version 8.3, perform the
| following steps:
| 1. Start the Job Scheduling Console version 8.3. See Chapter 9, “Starting the Job
| Scheduling Console,” on page 45.
| The Load Preferences file panel displays.

18 IBM Tivoli Workload Scheduler Job Scheduling Console: User’s Guide

 Importing Job Scheduling Console user preferences from versions 8.3

|
| 2. Browse to the user_home_directory/.twsconsole and select the
| preferences.xml file.
| 3. Browse to the user_home_directory/.twsconsole and select the Engines.xml
| file.
| 4. Click OK.
| The Job Scheduling Console main window opens.
|

|
| 5. Right-click an engine and select Properties.
| The Properties - Engine panel displays.

Chapter 4. Importing Job Scheduling Console user preferences 19

 Importing Job Scheduling Console user preferences from versions 8.3

|
| 6. Define the connection profile and default properties for lists. Click OK.
| 7. Perform this operation for each engine defined in your Engines.xml file.
| 8. Close the Job Scheduling Console.
| You can now use the preferences.xml and Engines.xml files as common files for
| each of the Job Scheduling Console instances that require the same connection
| profiles.

20 IBM Tivoli Workload Scheduler Job Scheduling Console: User’s Guide

Chapter 5. Installing and adding language packs
This chapter describes how you install or modify language packs.

Installing language packs

When you are installing language packs, you can use the installation wizard or a
script.

Installing language packs using the installation wizard

To install languages, perform the following steps:
1. Insert the relevant CD in the CD-ROM drive. See “The installation CDs” on
page 9.
2. Navigate to the operating system\LANG_PACK directory.
3. Run the setup according to the operating system where you are installing:
v Windows operating systems: setup.exe
v UNIX and Linux operating systems: ./setup.bin
4. Select the language of the installation wizard. Click OK.
5. Read the welcome information. Click Next.
6. Read and accept the license agreement. Click Next.
7. Select the languages you want to install. Click Next.
8. Review the installation settings. Click Next.
When the installation completes, a panel displays a successful installation or
contains a list of the items that failed to install and the location of the log file.
9. Click Finish.

Installing language packs in silent mode

To start the installation in silent mode on Windows systems, enter the following
command:
SETUP.exe -silent -options filename

To start the installation in silent mode on UNIX and Linux operating systems,
navigate to the directory where the setup is located and enter the following
command:
./setup.bin -silent -options filename

specifying the fully qualified path to the response file.

Note: The parameters of the silent installation are described in detail as comments
in the response file.

Adding language packs to an existing installation

To change languages installed on an existing installation, perform the following
steps:
1. Insert the relevant CD in the CD-ROM drive.
2. Navigate to the operating system\LANG_PACK directory.
3. Run the setup according to the operating system where you are installing:
© Copyright IBM Corp. 1991, 2006 21
Adding language packs to an existing installation

v Windows operating systems: setup.exe

v UNIX and Linux operating systems: ./setup.bin
4. Select the language of the installation wizard. Click OK.
5. Read the welcome information. Click Next.
6. Read and accept the license agreement. Click Next.
7. Select the languages you want to install. Click Next.
8. Review the installation settings. Click Next.
When the installation completes, a panel displays a successful installation or
contains a list of which items failed to install and the location of the log file.
9. Click Finish.

Note:

When you change a language, you must edit the appropriate console file
(for example, NTConsole.bat, LinuxConsole.sh) and add the following lines:
-Duser.language=xx
-Duser.region=yy

where xx is the standard two-digit language code and yy is the standard

two-digit region code. For example:
-Duser.language=it
-Duser.region=IT

22 IBM Tivoli Workload Scheduler Job Scheduling Console: User’s Guide

Chapter 6. Uninstalling
This chapter describes how to uninstall:
v “Uninstalling language packs”
v “Uninstalling the Job Scheduling Console”
v “Uninstalling the z/OS connector” on page 24
the Job Scheduling Console and all prerequisite components.

Uninstalling language packs

This section describes how to uninstall the language packs.

Note: When you uninstall languages, all language packs are uninstalled. You
cannot uninstall individual language packs.

To uninstall language packs, perform the following steps:

1. Close the Job Scheduling Console.
2. Navigate to the language uninstall directory (\langsUninstaller on Windows, or
./langsUninstaller on UNIX).
3. Run the language uninstall according to the operating system from where you
are uninstalling:
v Windows: uninstallLanguages.exe
v UNIX: uninstallLanguages.bin
or use the shortcut icons if they were created at installation time.
The Uninstall panel displays. Click Next
4. When uninstall completes, it lists the files that were not uninstalled. Delete
those files manually. In addition, the .twsconsole directory is maintained in the
user home directory. If the installation completes with errors, the log file is
maintained in the product installation directory.
5. Click Finish.

Uninstalling the Job Scheduling Console

To uninstall the Job Scheduling Console, perform the following steps:
1. Close the Job Scheduling Console.
2. Navigate to the interface uninstall directory (\uninstaller on Windows, or
./uninstaller on UNIX).
3. Run the uninstall according to the operating system from where you are
uninstalling:
v Windows: uninstall.exe
v UNIX: uninstall.bin
or use the shortcut icons if they were created at installation time.
The Uninstall panel displays. Click Next
4. When uninstall completes, it lists the files that were not uninstalled. Delete
those files manually. In addition, the .twsconsole directory is maintained in the
user home directory. In case the uninstallation completes with errors, the log
file is maintained in the product installation directory.

© Copyright IBM Corp. 1991, 2006 23

Uninstalling the Job Scheduling Console

5. Click Finish.

Uninstalling the Job Scheduling Console using the Software

Distribution CLI
You can uninstall Job Scheduling Console using the Software Distribution
command wremovsp as follows:
wremovsp @TWSConsole.8.2.1 [subscribers...]

Uninstalling the z/OS connector

To uninstall the z/OS connector, perform the following steps:
1. Close the Job Scheduling Console.
2. Navigate to the interface uninstall directory (\uninstall on Windows, or
./uninstall on UNIX).
3. Run the uninstall according to the operating system from where you are
uninstalling:
v Windows: uninstall.exe
v UNIX: uninstall.bin
or use the shortcut icons if they were created at installation time.
The Uninstall panel displays. Click Next
4. When the uninstallation completes, a panel displays a successful completion or
contains a list of items that failed to uninstall and the location of the log file.
5. Click Finish.

24 IBM Tivoli Workload Scheduler Job Scheduling Console: User’s Guide

Part 2. Getting started

© Copyright IBM Corp. 1991, 2006 25

26 IBM Tivoli Workload Scheduler Job Scheduling Console: User’s Guide
Chapter 7. Job Scheduling Console objects and scheduling
concepts
This chapter describes the objects of the Job Scheduling Console interface and the
scheduling concepts. It is divided into the following sections:
v “Job Scheduling Console objects”
v “Scheduling job streams using defined objects” on page 32

Job Scheduling Console objects

This section describes the main objects in the database. It is divided into the
following subsections:
v “Common objects”
v “Distributed engine specific objects” on page 29
v “Lists” on page 31
v “Database” on page 31
v “Plan” on page 31

Common objects
Objects common to both the z/OS and distributed environments are:
v “Workstations”
v “Resources” on page 28
v “Job streams” on page 28

Workstations
Although workstations are common for both z/OS and distributed environments,
their definitions differ:
z/OS workstations
The Tivoli Workload Scheduler z/OS environment is defined in
terms of resources and workstations. A workstation describes how
jobs have to be run. A workstation is not necessarily hardware. It is
a stage in the processing that is controlled by the scheduler.
Workstations are usually created to represent specific elements in
your system configuration. The availability of these workstations
reflects the availability of those elements in the real world. For
instance, a computer workstation might be created for each z/OS
system in a scheduler complex. The availability of the computer
workstation reflects the availability of the z/OS system it
represents. This prevents the scheduler from submitting work to a
z/OS system that is not physically available. Also, the accuracy of
any planning predictions that the scheduler produces depends on
how accurately you have described the installation to the
scheduler.
The scheduler establishes the availability of a workstation by using
open intervals in the list of available workstations in the database.
These are the times when workstation resources and parallel
servers are available to process work. Parallel servers and resources
are usually necessary to run work at the workstation.

© Copyright IBM Corp. 1991, 2006 27

 Job Scheduling Console object descriptions

| z/OS workstations can also be used as the interface in the

| integration between Tivoli Workload Scheduler for z/OS and IBM
| Tivoli System Automation for z/OS. Integrate these two products
| to combine the scheduling power of the former and the "desired
| state" system maintenance of the latter.
Distributed workstations
A workstation is usually an individual computer, on which jobs
and job streams are run. A workstation definition is required for
every computer that runs jobs in the Tivoli Workload Scheduler
network.
Primarily workstation definitions refer to physical workstations.
However, in the case of extended agents, the workstations are
logical definitions that must be hosted by a physical workstation.

Resources
Resources can represent either physical or logical resources on your system. After
they are defined in Tivoli Workload Scheduler database, they can be used as
dependencies for jobs and job streams. For example, you can define a resource
named tapes with a unit value of two. Then, define jobs that require two available
tape drives as a dependency. Jobs with this dependency cannot run concurrently
because each time a job is run the tapes resource is in use.

Job streams
A job stream consists of a list of jobs that run as a unit (such as running a weekly
backup), along with times, priorities and other dependencies that determine the
order in which the jobs run.

| z/OS engine specific objects

| The following are objects that are specific to the z/OS environment:
| Special Resources
| Special resources are a special case of normal resources, and can be
| used to control the running of jobs that run outside Tivoli
| Workload Scheduler for z/OS.
| For example, consider the following scenario.
| v You have a daily job running outside the control of Tivoli
| Workload Scheduler for z/OS
| v The job is a predecessor of a Tivoli Workload Scheduler for z/OS
| job, because it creates a file that the Tivoli Workload Scheduler
| for z/OS job needs to use
| v You need to find a way to make the external job trigger the
| Tivoli Workload Scheduler for z/OS job, but only when it has
| completed.

| A special resource can be used in the following way to resolve this

| scenario:
| 1. Create a special resource "file", set by default to Not available,
| 2. Define a data set triggering table that tells the event tracker to
| create a "Special resource availability" event for the special
| resource "file". Every time the data set in question is created or
| modified; the event sets the resource to Available

28 IBM Tivoli Workload Scheduler Job Scheduling Console: User’s Guide

 z/OS engine specific objects

| 3. Create the Tivoli Workload Scheduler for z/OS job, defining

| that it must set the special resource "file" to Not available, on
| successful completion
| 4. When the job is inserted into the current plan (either by the
| daily plan batch or directly by a user) and uses the special
| resource "file", the job cannot start because the resource is Not
| available
| 5. When the external process creates or modifies the data set, the
| event tracker creates the "Special resource availability" event,
| and the controller modifies the special resource "file" to make it
| Available
| 6. Tivoli Workload Scheduler for z/OS finds the resource available
| and runs the Tivoli Workload Scheduler for z/OS job, using the
| data in the file. On successful completion it sets the resource to
| Not available.
| When the plan is generated next day, the resource is thus Not
| available again, and remains so until the external job is run
| successfully again.

| In summary, you can define the following for each special resource:
| v A behavior on successful completion
| v An availability quantity that is decreased each time the resource
| is used and a behavior for when the quantity is exhausted
| Also, the "Special resource availability" event can set a time limit
| for the availability of the resource.

Distributed engine specific objects

The following are objects that are specific to the distributed environment:
Job definitions
You can create job definitions in the database before you create a
job stream, or you can create a job definition at the same time you
are creating its job stream. A job definition consists of task
information and recovery options.
Workstation classes
| A workstation class is a group of workstations. Any number of
| workstations can be placed in a class. Job streams and jobs can be
| assigned to run on a workstation class, making replication across
| many workstations easy. If a job stream is defined on a workstation
| class, each job added to the job stream must be defined either on a
| single workstation or on the same workstation class that the job
| stream was defined on. If a resource is defined on a workstation
| class, each resource added must be defined either on a single
| workstation or on the same workstation class. If a file dependency
| is defined on a workstation class, each file dependency added must
| be defined either on a single workstation or on the same
| workstation class.
Domains A domain is a named group of Tivoli Workload Scheduler
workstations, consisting of one or more workstations and a domain
manager acting as the management hub. All domains have a
parent domain, except for the master domain.

Chapter 7. Job Scheduling Console objects and scheduling concepts 29

 Distributed engine specific objects

Windows Users
| When you are running jobs in a Windows environment, you need
| to create the user details in the Tivoli Workload Scheduler
| database. Windows users must be defined on the workstation
| where they launch job.
Calendars A calendar is a list of scheduling dates defined in the scheduler
database. Assigning a calendar run cycle to a job stream causes
that job stream to be run on the days specified in the calendar. As
a calendar is defined to the scheduler database, it can be assigned
to multiple job streams.
You can create as many calendars as required to meet your
scheduling needs. For example:
PAYDAYS
Could contain a list of days on which payment is made.
MONTHEND
Could contain a list of the last working day of each month.

Two default calendars are provided:

HOLIDAYS
The HOLIDAYS calendar is used to determine
non-workdays for the purpose of defining run cycles for
your job streams. It also affects the definition of the
workdays keyword as follows:
workdays=everyday except saturday, sunday and all
the dates appearing in the HOLIDAYS calendar

Create a HOLIDAYS calendar with the dates of your

holidays. A default HOLIDAYS calendar is supplied with
the Job Scheduling Console.
FREEDAYS
Freedays calendars are intended as non-workdays for the
purpose of defining run cycles for your job streams. The
freedays calendar extends the role of the HOLIDAYS
calendar by providing additional flexibility in defining
workdays. When defining a job stream, if you decide to use
a freedays calendar instead of HOLIDAYS, then the
definition of workdays becomes:
workdays=everyday except saturday, sunday and
all the dates appearing in the specified freedays calendar

If you decide to create a freedays calendar for a job stream,

the redefined meaning of workdays is limited to that job
stream. You might define more than one freedays calendar
when your organization has different international
locations, and the calendar must respond to local
requirements.

When you do not specify a freedays calendar for a job

stream the HOLIDAYS is used, if available.

There is a freedays calendar provided with the Job

Scheduling Console that you can use when you are
defining your job stream time restrictions.

30 IBM Tivoli Workload Scheduler Job Scheduling Console: User’s Guide

 Distributed engine specific objects

Prompts Prompts are used as dependencies for jobs and job streams. A
prompt must be answered affirmatively for the dependent job or
job stream to launch. For example, you can issue a prompt to make
sure that a printer is online before a job that prints a report runs.
There are two types of prompt:
Ad hoc prompt
This is defined within the properties of a job or job
stream and is unique to that job or job stream.
Predefined prompt
This is defined in the Tivoli Workload Scheduler
database and can be used by any job or job stream.
Parameters Parameters are used to substitute values in jobs and job streams.
As parameters are stored in the Tivoli Workload Scheduler
database, all jobs and job streams that use the parameter are
updated automatically when the value changes. For scheduling, a
parameter can be used as a substitute for all or part of:
v File dependency path names
v Text for prompts
v Logon, command, and script file names
Parameters cannot be used when scripting Extended Agent jobs.
| Files Files are not database objects as such, but dependencies whose
| existence a job or job stream must verify before they can start.

Lists
Lists are filters that allow objects in the database and in the plan to be filtered.
There are standard default lists available in the Job Scheduling Console, or you can
create lists that are specific to your needs.

When you create a list, you give it a name and specify the filtering criteria. When
you run a list, it displays a filtered table of objects. Each list you create is
represented by an icon in the Work with engines pane.

Default plan and database lists are provided. Common plan and database lists that
relate to both the z/OS and the distributed environments are also provided.

Database
The scheduler database stores scheduling object definitions. Examples of common
scheduling object definitions are:
v Workstations
v Resources
v Job Streams

Plan
The plan is the master control for the current production day. Object definitions in
the database become instances in the current production day plan, where they can
be monitored and modified. Examples of common object instances are:
v Job Streams
v Jobs

There are the following types of plan:

Chapter 7. Job Scheduling Console objects and scheduling concepts 31

Distributed engine specific objects

Forecast plan The forecast plan is a projection over a selected time frame based
on the job streams and dependencies defined in the database.
Preproduction plan
The preproduction plan is a high-level plan of system activity
containing job streams and dependencies. It is created
automatically when the production plan is created for the first
time. It is extended if the production plan is extended. It is similar
to the long-term plan used in Tivoli Workload Scheduler for z/OS.
Production plan
The production plan contains all job scheduling activity planned
for a period. The plan is created or extended by the Jnextplan job
or by planman. It is stored in the Symphony file, and consists of all
the jobs, job streams, and dependency objects that are scheduled to
run for that period, including any jobs or job streams carried
forward from the previous plan.
Trial plan The trial plan is a projection of the current production plan for a
different period, using the same start date. You can use the trial
plan to determine the effect of different plan decisions.

Scheduling job streams using defined objects

This section describes the main concepts of scheduling using the Job Scheduling
Console.

You schedule your job streams and define their behavior using the following:
v “Time restrictions”
v “Dependencies”
v “Time Zones and the Job Scheduling Console” on page 33
v “Run cycles” on page 34

Time restrictions
Time restrictions determine the times before which, after which, or both, that a job
or job stream cannot be run. Specifying both defines a time frame within which a
job or job stream runs. Jobs can also have a repetition rate. For example Tivoli
Workload Scheduler can launch the same job every 30 minutes between the hours
of 8:30 a.m. and 1:30 p.m.

Dependencies
Dependencies are prerequisites that must be satisfied before a job stream or a job
can start. The type of dependency that you can specify differs depending on the
type of engine:
v “z/OS dependencies”
v “Distributed dependencies” on page 33

z/OS dependencies
When you create z/OS dependencies, you link jobs in a sequence. A successor job
cannot begin until the predecessor job is complete. Dependencies determine when
the successor job runs, even if the successor job has time restrictions.

For example, to print bank account statements, you must first subtract withdrawals
from an account (Job A) before you calculate the account balance (Job B). Job A is
the predecessor and Job B the successor.

32 IBM Tivoli Workload Scheduler Job Scheduling Console: User’s Guide

 Scheduling concepts

External jobs represent jobs that are part of other job streams. You create a
dependency between jobs in different job streams by creating a dependency on an
external job. For example, if Job C in the Accounts job stream depends on Job B in
the Reports job stream, you create an external job in the Accounts job stream to
represent Job B, then you create a dependency between Job C and the external job.

Distributed dependencies
There are different types of dependencies in the distributed environment:
v “Internetwork dependencies”
v “External job stream dependencies”
v “External job dependencies”
Dependencies create predecessors for job streams. A predecessor must complete
successfully before the successor job is launched.

Internetwork dependencies
An internetwork dependency is a dependency on a job that runs in another Tivoli
Workload Scheduler network. Internetwork dependencies require a network agent
workstation to communicate with the external scheduler network. For more
information about configuring a network agent, refer to the IBM Tivoli Workload
Scheduler: Reference Manual.

You add internetwork dependencies in a job stream using the job stream editor. See
Chapter 37, “Managing distributed job streams,” on page 219 for more information.

External job stream dependencies

An external job stream dependency is a dependency on a job stream that runs in
the same Tivoli Workload Scheduler network.

You add external job stream dependencies in a job stream using the job stream
editor. See Chapter 37, “Managing distributed job streams,” on page 219 for more
information.

External job dependencies

An external job dependency is a dependency on a job that runs in the same Tivoli
Workload Scheduler network.

You external job dependencies in a job stream using the job stream editor. See
Chapter 37, “Managing distributed job streams,” on page 219 for more information.

Time Zones and the Job Scheduling Console

Time zone support is an optional feature that is enabled by default. When enabled,
you can use time zone support to manage workloads at a global level.

Time zone implementation also enables easy scheduling across multiple time zones
and for jobs that need to run in the dead zone. The dead zone is the difference
between the start of day time on the master domain manager and the time on the
fault-tolerant agent in another time zone. For example, if an eastern master with a
start of day of 6 a.m. initializes a western agent with a 3-hour time zone difference,
the dead zone for this fault-tolerant agent is between the hours of 3 a.m. and 6
a.m. See Figure 5 on page 34.

Chapter 7. Job Scheduling Console objects and scheduling concepts 33

Time Zones and the Job Scheduling Console

6 am 6 am

24h

Master Start of Day Start of Day

3h 3h

Start of Start of
Fault-tolerant Day Day
agent
Dead zone Dead zone
3 am 3 am
Figure 5. Illustration of the dead zone

In the Job Scheduling Console you can set time zone data at the following levels:
v Engines
v Workstations
v Job streams
v Time restrictions
v Forecast and trial plans

When the time zone feature is not enabled at the engine level, the Job Scheduling
Console does not provide time zone support for the listed objects.

For information about enabling the time zone, see Planning and Installation Guide.

Setting your local time zone

Because of the expansion of time zone support, it is now possible for you to set
your local time zone in the preferences.xml file. The user preferences file is
located in user_home_directory/.twsconsole/.

To set your local time zone, add the following tag to your preferences.xml file
under the consoleUserPreferences node:
<entry key=defaultTimeZone” value=”time zone ID”/>

where time zone ID is the extended ID of your time zone. For example:
<entry key=defaultTimeZone” value=”Europe/Rome”/>

For a list of the available time zone IDs, refer to the IBM Tivoli Workload Scheduler:
Reference Manual.

Run cycles
Run cycles specify when a job stream in the database is to run in the plan.
Combinations of run cycles are used to include and exclude certain dates. Types of
run cycle vary depending on the type of engine:
v “z/OS run cycles” on page 35
v “Distributed run cycles” on page 35

34 IBM Tivoli Workload Scheduler Job Scheduling Console: User’s Guide

 Time Zones and the Job Scheduling Console

z/OS run cycles

After creating z/OS jobs and defining dependencies, you specify the scheduling
information for the job stream using run cycles. Run cycles are generated from a
combination of the following information:
v A calendar of workdays and freedays. The calendar is defined in Tivoli
Workload Scheduler for z/OS. You specify its name in the Job Stream Properties
panel (see “Creating z/OS job streams” on page 133).
v The validity date of the job stream, which you specify in the Job Stream
Properties panel.

You can create two types of run cycle for z/OS:

v Offset-based
Uses a combination of user-defined periods and offsets. For example, an offset of
3 in a period of 15 days is the third day from the beginning of the period. It is
more practical to use offset-based run cycles when the cycle is based on cyclic
periods.
v Rule-based
Uses rules based on lists of ordinal numbers, types of days, and common
calendar intervals or period names. For example, the last Thursday of every
month. Rule-based run cycles are based on conventional periods, such as
calendar months, weeks of the year, and days of the week, or periods that you
define, such as a semester.

You can specify multiple run cycles when you create a job stream and add new
ones afterwards. You can also mix rule-based and offset-based run cycles.

Run cycles can be either inclusive or exclusive. Inclusive run cycles specify the days
that the job stream must run. Exclusive run cycles specify the days that the job
stream must not run. You can add run cycles to generate more days, or to have
multiple instances on the same day. You can add exclusive run cycles to exclude
some of the days already generated.

| You can also specify the frequency with which you want to run a job stream
| starting from the input arrival time by setting the every option. For example, if you
| want to run a job stream every 30 minutes from input arrival time, set the every
| option to 00:30. See “Time Restrictions page” on page 211 for detailed information
| on how to set the every option.

Distributed run cycles

For the distributed environment there are the following types of run cycle:
Simple Run Cycles
Based on specific calendar dates.
Calendar Run Cycles
Based on predefined calendars. For details about creating
calendars, see Chapter 22, “Creating calendars,” on page 119.
Daily Run Cycles
Based on the frequency a run is performed in days.
Weekly Run Cycles
Based on days of the week.
Monthly by Date
Based on numeric days of the month, such as 1st day of the
month.

Chapter 7. Job Scheduling Console objects and scheduling concepts 35

Time Zones and the Job Scheduling Console

Monthly by Day
Based on days of the month by day, such as 1st Sunday of the
month.

As well as the types of run cycle, for distributed run cycles you also define:
v “Inclusive or exclusive run cycles”
v “Rule for freedays”

Inclusive or exclusive run cycles

You specify distributed run cycles for a job stream using the Run Cycle view of the
Job Stream Editor. See “Adding run cycles to a job stream” on page 231.

When you define a run cycle, you must specify if it designates the days when the
job stream is to run (inclusive) or when the job stream is not to run (exclusive).
v The days you mark in an inclusive run cycle are displayed as Days Included in
the list of run cycles applied to the job stream.
v The days you mark in an exclusive run cycle are displayed as Days Excluded in
the list of run cycles applied to the job stream. Excluded days always take
precedence over included days.

For each job stream, you can define as many inclusive and exclusive run cycles as
you want.

Rule for freedays

This rule is based on the definition of freedays. Freedays are non-workdays, such
as holidays or weekends, and can be defined in one or more specific calendars.
Freedays calendars can in other terms be considered as the list of non-workdays
when there is no activity in your enterprise.

Based on a freedays calendar, you can specify a rule when you define the run cycle
of a job stream. The rule determines what action Tivoli Workload Scheduler must
take when the schedule of a job stream falls on a freeday. If the schedule date falls
on a freeday, the scheduler can do one of the following:
v Run the job stream
v Not run the job stream
v Run the job stream on the closest workday before the freeday
v Run the job stream on the closest workday after the freeday

If no freeday rule is specified, the scheduler proceeds by default and runs the job
stream even if the selected run date is a freeday.

Tivoli Workload Scheduler does not reschedule the same job stream more than
once on a given production day if its run date was moved because of a freeday
rule application.

36 IBM Tivoli Workload Scheduler Job Scheduling Console: User’s Guide

Chapter 8. Job Scheduling Console task guide
This chapter describes the flow of tasks you perform using the Job Scheduling
Console, and provides a map between those tasks that are common to both z/OS
and distributed engines, and those tasks that are unique to each. It is divided into
the following sections:
v “Task types”
v “Task flows”
v “Task mapping” on page 40
v “Command-line mapping” on page 42
v “Terminology mapping” on page 42

Task types
This section describes the task types that you can utilize in the Job Scheduling
Console.

Definition tasks
You use the definition tasks to create the scheduling network, job streams and jobs,
defining their resources and parameters depending on the type of engine to which
they relate: z/OS or distributed. The types of resources and parameters vary
according to the engine type, and for a clearer view of these differences refer to
“Task flows.” When you have defined the environment, you can create filters to
display monitoring information for database and plan objects.

Management tasks
You use management tasks to monitor the status of job streams and make
adjustments both in the database and the plan.

Task flows
Task flows in the Job Scheduling Console can be grouped into definition tasks and
management tasks.

Definition task flows

Figure 6 on page 38 illustrates the flow of definition tasks. The task flow depends
on the type of environment in which you are working. For example, in a z/OS
environment you create your job definitions while you are creating or modifying a
job stream, but in a distributed environment you should create Windows users
(when relevant), parameters, and job definitions before you create your job stream.
You can perform the other activities for a distributed definition in the order you
prefer, but you should be aware that for your job streams to function correctly you
must complete most of the definition tasks.

© Copyright IBM Corp. 1991, 2006 37

Task flows

Defining
Creating
Engines

Creating
Workstations

Creating
Resources
Creating
Windows
Users

Creating
Parameters

Creating
Prompts

Creating
Calendars

Creating
Domains

Creating
Workstation
Classes
Creating Creating
Job Definitions Job Streams
on the fly
Creating
Job Definitions
Creating
Object Lists
Common tasks Creating
Trial and
Distributed tasks Forecast Plans

Figure 6. Definition task flows

Creating Object Lists in the definition task flow is important, because most of
your monitoring activity is performed using lists. Create object lists before
beginning any management tasks.

Management task flows

Figure 7 on page 39 illustrates the flow of management tasks. Using Object Lists is
the first step in the management flow, because you use object lists to filter for the
objects with which you want to work.

38 IBM Tivoli Workload Scheduler Job Scheduling Console: User’s Guide

 Task flows

Managing
Using
Object Lists

Database Objects z/OS Plans Distributed Plans

Managing Job Job

Workstations Stream Stream
Instances Instances

Managing Job Job

Job Streams Instances Instances

Managing Submitting
Resources Workstations Jobs and
Job Streams

Managing
Job Resources
Definitions Workstations

Managing
Workstation
Classes Domains

Managing
Domains File
Dependencies

Managing
Windows
Users Prompt
Dependencies

Managing
Calendars
Resource
Dependencies

Managing
Prompts Setting
Alternate
Plan
Managing
Parameters

Common tasks

z/OS tasks

Distributed tasks

Figure 7. Management task flows

Chapter 8. Job Scheduling Console task guide 39

Task mapping

Task mapping
The Job Scheduling Console has different task groups: administrative tasks, and
operator tasks. The tasks that you can use are further divided by the type of
engine: z/OS or distributed.
Table 5. z/OS and distributed task mapping
Task z/OS Distributed Link
Definition tasks
Creating engines Yes Yes Chapter 16, “Creating
engines,” on page 95
Creating workstations Yes Yes Chapter 17, “Creating
workstations,” on page 97
Creating job streams Yes Yes Chapter 26, “Creating job
streams,” on page 133
Creating resources Yes Yes Chapter 18, “Creating
resources,” on page 107
Creating job definitions No Yes Chapter 25, “Creating job
definitions,” on page 127
Creating workstation classes No Yes Chapter 24, “Creating
workstation classes,” on
page 125
Creating domains No Yes Chapter 23, “Creating
domains,” on page 123
Creating Windows users No Yes Chapter 19, “Creating
Windows users,” on page
113
Creating calendars No Yes Chapter 22, “Creating
calendars,” on page 119
Creating prompts No Yes Chapter 21, “Creating
predefined prompts,” on
page 117
Creating parameters No Yes Chapter 20, “Creating
parameters,” on page 115
Creating forecast and trial No Yes Chapter 27, “Creating
plans forecast and trial plans,” on
page 155
Creating using Create Another Yes Yes Chapter 28, “Creating
objects using Create
Another,” on page 157
Creating and using lists
Creating database lists Yes Yes Chapter 29, “Creating
database lists,” on page 161
Creating plan lists Yes Yes Chapter 30, “Creating plan
lists,” on page 171
Creating a group of lists Yes Yes Chapter 31, “Creating a
group of lists,” on page 181
Creating common plan lists Yes Yes Chapter 32, “Creating
common plan lists,” on page
183

40 IBM Tivoli Workload Scheduler Job Scheduling Console: User’s Guide

 Task mapping

Table 5. z/OS and distributed task mapping (continued)

Task z/OS Distributed Link
Working with lists Yes Yes Chapter 33, “Working with
lists,” on page 185
Management Tasks
Managing engines Yes Yes Chapter 34, “Managing
engines,” on page 191
Managing workstations Yes Yes Chapter 35, “Managing
workstations,” on page 197
Managing job streams Yes Yes Chapter 36, “Managing
z/OS job streams,” on page
199 and Chapter 37,
“Managing distributed job
streams,” on page 219
Managing resources Yes Yes Chapter 38, “Managing
resources,” on page 239
Managing job definitions No Yes Chapter 39, “Managing job
definitions,” on page 241
Managing workstation classes No Yes Chapter 40, “Managing
workstation classes,” on
page 243
Managing domains No Yes Chapter 41, “Managing
domains,” on page 245
Managing Windows users No Yes Chapter 42, “Managing
Windows users,” on page
247
Managing calendars No Yes Chapter 43, “Managing
calendars,” on page 249
Managing prompts No Yes Chapter 44, “Managing
prompts,” on page 251
Managing parameters No Yes Chapter 45, “Managing
parameters,” on page 253
Managing job stream instances Yes Yes Chapter 46, “Managing
in the plan z/OS job stream instances,”
on page 257 and Chapter 47,
“Managing distributed job
stream instances in the
plan,” on page 263
Managing job instances in the Yes Yes Chapter 48, “Managing
plan z/OS job instances,” on
page 277 and Chapter 49,
“Managing distributed job
instances in the plan,” on
page 297
Managing workstations in the Yes Yes Chapter 50, “Managing
plan workstations in the plan,”
on page 321
Managing resources in the plan Yes Yes Chapter 51, “Managing
resources in the plan,” on
page 331

Chapter 8. Job Scheduling Console task guide 41

 Task mapping

Table 5. z/OS and distributed task mapping (continued)

Task z/OS Distributed Link
| Managing file dependencies in No Yes Chapter 52, “Managing
| the plan distributed file dependencies
| in the plan,” on page 337
| Managing prompt No Yes Chapter 53, “Managing
| dependencies in the plan distributed prompt
| dependencies in the plan,”
| on page 339
| Managing domains in the plan No Yes Chapter 54, “Managing
| domains in the plan,” on
| page 341
| Managing Windows users in No Yes Chapter 55, “Changing
| the plan Windows user passwords in
| the plan,” on page 343
| Setting an alternate plan No Yes Chapter 56, “Setting an
| alternate plan,” on page 345
| Restore a plan No Yes Chapter 57, “Restoring a
| plan,” on page 347

For a quick start to these tasks, see Part 3, “Quick reference guide,” on page 51.

Command-line mapping
The Job Scheduling Console and the command-line interface have some actions in
common. Wherever there is an interrelation between a command and a task it is
listed in the IBM Tivoli Workload Scheduler: Reference Manual, under the See Also
section of each command description.

Terminology mapping
The terminology used in the Job Scheduling Console varies from that used in
Tivoli Workload Scheduler. Table 6 lists Tivoli Workload Scheduler distributed and
z/OS terms and their Job Scheduling Console equivalents.
Table 6. Job Scheduling Console terminology mapping
Tivoli Workload
Tivoli Workload Scheduler for Job Scheduling
Scheduler z/OS Console Explanation
Schedule Application Job stream A sequence of jobs, including the
resources and workstations that
support them, and scheduling
information.
Not applicable Application Job stream A group of job streams that
group template provides scheduling information,
such as a calendar, a free-day rule,
and run cycles that can be
inherited by all the job streams
that were created using the
template.

42 IBM Tivoli Workload Scheduler Job Scheduling Console: User’s Guide

 Terminology mapping

Table 6. Job Scheduling Console terminology mapping (continued)

Tivoli Workload
Tivoli Workload Scheduler for Job Scheduling
Scheduler z/OS Console Explanation
Symphony Current plan Plan A detailed plan of system activity.
The plan encompasses all job and
job stream instances and the
resources and workstations
involved in running them.
External External External job, A job or job stream that is a
dependency dependency external job predecessor for a job in another
stream job stream.
Not applicable In-effect date for Valid from The first date that a run cycle is
run cycles valid.
| Start Time Input arrival time (Earliest) start The time when a job or job stream
| time is planned to be ready for
| processing.
| Exclusive run Negative run Exclusive run Specifies when a job stream must
| cycle cycle cycle not run.
Schedule Occurrence Job stream A job stream that is scheduled for
instance a specific run date in the plan.
Engine Controller Engine The component that runs on the
controlling system, and that
contains the tasks that manage the
plans and databases.
Job Operation Job A unit of work that is part of a
job stream and that is processed
at a workstation.
Job identifier Operation Job identifier The number that identifies a job.
number
Job (in the plan) Operations in the Job instances A job scheduled for a specific run
current plan date in the plan.
Not applicable Out-of-effect date Valid to The last date that a run cycle is
for run cycles valid.
Not applicable Run cycle with Offset-based run Includes a user-defined period
offsets cycle and an offset, such as the 3rd day
in a 90-day period.
Not applicable Run cycle with Rule-based run Includes a rule, such as the first
rules cycle Friday of March or the second
workday of the week.
| Resources Special resources Logical Any type of limited resource, such
| resources as tape drives, communication
| lines, databases, files, or printers,
| that is needed to run a job.
Not applicable Task Job A job performed at a computer
workstation.

Chapter 8. Job Scheduling Console task guide 43

Terminology mapping

44 IBM Tivoli Workload Scheduler Job Scheduling Console: User’s Guide

Chapter 9. Starting the Job Scheduling Console
This chapter describes the information necessary to sign on to the Job Scheduling
Console.

Start the Job Scheduling Console in one of the ways described in Table 7.
Table 7. Starting the Job Scheduling Console
On this operating system ... In the ..\bin\java subdirectory of the installation path ...
Microsoft Windows Enter NTconsole, or double-click the Job Scheduling Console
icon on the Windows Desktop, or from the Start menu, if
created at installation time.
AIX Enter . /AIXconsole.sh or use the shortcut icons, if created
at installation time.
SUN Solaris Enter . /SUNconsole.sh or use the shortcut icons, if created
at installation time.
HP-UX Enter . /HPconsole.sh or use the shortcut icons, if created
at installation time.
Linux Enter . /LINUXconsole.sh or use the shortcut icons, if
created at installation time.

The first time you log on the Load Preferences Files panel displays.

You can use this panel to load a common preferences file, and a common engines
file thereby negating the need to set preferences in the Job Scheduling Console.
Type the location of the common files, or browse for them. If you do not have a
common files, click Cancel to continue.

Note: If there is a tag error in the preferences file, you can exit and correct the
error, or continue and the default preferences file is used. When you
continue, any modifications to the preferences file are lost.

Startup automatically opens TCP/IP port 9992 to listen for user commands
directed to the logging utility. If you are concerned that this default might expose
performance to network malfunctions, you can disable the mechanism by adding
the following line to one of the startup commands listed in Table 7:
–Djava jlog.noLogCmd=true

© Copyright IBM Corp. 1991, 2006 45

 Starting the Job Scheduling Console

The port though which the logging utility listens can be changed by setting the
system property jlog.logCmdPort.

Logging on to an engine
| The first time you start the Job Scheduling Console, the Job Scheduling Console
| displays the following message:
| The Job Scheduling Console did not find any engine defined.
| The Define a New Engine wizard starts to allow new engine definition

| Click OK, the Define a New Engine panel displays.

|

| For information about creating engines, see Chapter 16, “Creating engines,” on
page 95.

To access an engine, perform the following steps:

1. Click the engine icon in the Work with engines pane.
If the login credentials of the engine have not been saved, the Engine Login
panel displays.

46 IBM Tivoli Workload Scheduler Job Scheduling Console: User’s Guide

 Logging on to an engine

The panel consists of the following:

User Name Type the user name of the administrator for the computer
where the engine is installed.
Password Type the password of the administrator of the computer where
the engine is installed.
Save Password
When you select to save the login credentials it is not necessary
to enter the administrator name and password each time that
you access the engine.

The Job Scheduling Console main window opens.

For a description of the interface, see Chapter 11, “Interface quick reference,” on
page 55.

Chapter 9. Starting the Job Scheduling Console 47

Standard functions

Standard functions
This section lists the functionality that is standard throughout the Job Scheduling
Console.

Standard buttons
When you have finished a procedure, perform the following operations:
v Click OK to close the window and save.
v Click Cancel to close the window without saving.
v Click Apply to save without closing the window.
v Click Reset to return all fields to the values of the last save.

Wildcards
The wildcards for Job Scheduling Console are:
? Replaces one alphanumeric character.
% Replaces one numeric character.
* Replaces zero or more alphanumeric characters.

Unsupported characters
When you enter a character that is not supported, the field border turns red and a
cross appears to the left of the field indicating that it is not supported.

Finding objects
The Job Scheduling Console uses a standard search functionality for finding objects
in the database or plan. Whenever you see three ellipses (...), or an icon
representing a torch, you can search for objects using a find pane. When searching
you can use wildcard characters, such as an asterisk (*) to represent a string of
characters, or a question mark (?) to represent a single character. Although the
appearance of the Find panel varies slightly according to the type of object you are
finding, the functionality is standard.

You start the search using Start. You can stop the search using Stop. You can
cancel the search using Cancel. When the search is complete, you select the
required object and click OK to enter it in the relevant field.

48 IBM Tivoli Workload Scheduler Job Scheduling Console: User’s Guide

 Standard functions

Deleting objects from a list

| You can delete objects from any list and therefore from the database using the
| Delete function of the relevant pop-up menu. Run the list and select the object or
| objects you want to delete. Right-click and select Delete in the menu.

Pop-up menus
You can right-click objects in the panes to display a pop-up menu of tasks related
to the object.

Required data
| When data is required, it is indicated by an asterisk and a yellow background.
| When a notebook contains a page that has required fields or objects within it, the
| page has a yellow strip with an asterisk before the page name. When a field is
| required it has a yellow strip with an asterisk in it and a pale yellow background.
| All other data elements, are optional.

Chapter 9. Starting the Job Scheduling Console 49

50 IBM Tivoli Workload Scheduler Job Scheduling Console: User’s Guide
Part 3. Quick reference guide

© Copyright IBM Corp. 1991, 2006 51

52 IBM Tivoli Workload Scheduler Job Scheduling Console: User’s Guide
Chapter 10. Quick reference overview
This quick reference guide is intended as a tool to help you quickly learn the
basics of the Job Scheduling Console when you are a new user, or to refresh your
memory when you are an expert user. It is divided into the following chapters:
v Chapter 11, “Interface quick reference,” on page 55
v Chapter 12, “z/OS quick reference,” on page 65
v Chapter 13, “Distributed quick reference,” on page 73
v Chapter 14, “Explorer View quick reference,” on page 87
v Chapter 15, “Troubleshooting quick reference,” on page 91

The interface quick reference describes the interface panels and panes, the menu
bars, the toolbars and their icons.

The distributed and z/OS quick references list quick steps you perform in the
environments and then describes in more detail each of those steps.

The troubleshooting quick reference describes the locations of the various log files.

© Copyright IBM Corp. 1991, 2006 53

54 IBM Tivoli Workload Scheduler Job Scheduling Console: User’s Guide
Chapter 11. Interface quick reference
The user interface consists of the following main components:
v Actions list pane
v Work with engines pane
v Object list pane
v Job Stream Editor panel

Actions list pane

The Actions list pane appears on the left side of the main window.

You can expand ( ) and collapse ( ) the nodes of this tree to navigate to the
main definition functions, create engines, change password for Windows, submit
job streams and jobs into the plan, generate new plans, set alternate plans, or
restore plans.

You can hide ( ) the Action list pane when you are performing tasks that are
not definition tasks. You can reattach ( ) the Actions list pane when you are
performing definition tasks.

© Copyright IBM Corp. 1991, 2006 55

 Work with engines pane

Work with engines pane

The Work with engines pane appears on the left side of the main window, to the
right of the Actions list pane.

| You can expand ( ) and collapse ( ) the nodes of this engine tree to navigate to
| the lists used in Job Scheduling Console to monitor and modify all the various
| objects. You can right-click on the icons at the various levels of the tree to open a
| pop-up menu that provides actions you can perform on that item in the tree. You
| can close ( ) the Work with engines pane when you are performing definition
| tasks, or when you need more space for the object list view pane. You can open (
| ) the 'Work with engines' pane when you want to create a new list, or filter for
| objects to view in the object list view pane.

| Object list pane

| The Object list pane appears on the right side of the main window.

| The view is in table format for all the objects:

|

|
| For jobs and job streams in the plan the view can be in:
| v Explorer format:

56 IBM Tivoli Workload Scheduler Job Scheduling Console: User’s Guide

 Object list pane

|
| From the Explorer view pop-up menu, you can Expand all that expands all the
| nodes of the tree that you have previously expanded, or collapse all.
| v Hyperbolic format:
|

|
| v Timeline format:
|

| You can right-click on a row to open a pop-up menu that provides actions you can
| perform on the object in the view. You can detach ( ) a view, allowing you to

| work with different filtered tables at the same time. You can reattach ( ) a table.

| Impact View
| You can display predecessor and successor information of your job and job stream
| instances in an impact view. To display predecessor and successor information run
| a list of jobs and job stream instances, right-click one of them, and from the pop-up
| menu select Impact View:

Chapter 11. Interface quick reference 57

 Object list pane

|
|
Job stream editor
The Job Stream Editor panel is a detached panel that you can position anywhere
on your screen and can minimize when you are not using it. The Job Stream Editor
panel varies according to the type of engine with which you are working. To
display the Job Stream Editor, run a list of job streams and double-click on the one
you want to edit.

58 IBM Tivoli Workload Scheduler Job Scheduling Console: User’s Guide

 Job stream editor

|
| Figure 8. Example z/OS Job Stream Editor
|
In the Job Stream Editor panel, you can right-click graphic representations of jobs
to open a pop-up menu that provides actions you can perform on the job. You can
add jobs to the job stream using the relevant buttons and menu options.

The main menu bar

Menu Use this menu to...
Console Detach an Objects list view pane, close an Objects list view pane,
exit from the Job Scheduling Console
Selected Perform an action on the object selected in the Object list pane
Edit Undo the previous action, cut, copy, paste, and delete objects
View Refresh the contents of the Objects list view pane, open and close
the Actions list and Work with engines panes, export the current
table
Window Customize a session, including its look and feel, detach all the
Objects list view panes you currently have open, reattach all the
Objects list view panes you currently have detached, close all
Objects list view panes you currently have open
Help Launch the comprehensive online Help system, view Help for the
current window, and display information about the product such
as version and copyright information

Chapter 11. Interface quick reference 59

Distributed job stream editor menu bar

The distributed job stream editor menu bar

Menu Use this menu to...
File View the properties of a job stream, add external dependencies to a
job stream, save a job stream, and close the job stream editor
Edit Copy, paste, delete objects, and undo previous delete
View Toggle between graph, explorer, timeline, and run cycle views
Actions Add a job, add a job dependency, add a link between jobs, and set
whether jobs should be monitored
Help Launch the comprehensive online Help system, view Help for the
current window, and display information about the product such
as version and copyright information

The z/OS job stream editor menu bar

Menu Use this menu to...
File View the properties of a job stream, save a job stream, and close
the job stream editor
Edit Copy, paste, delete objects, and undo previous delete
View Toggle between graph, explorer, timeline, and run cycle views
Actions Add a job, add an external job dependency, add a link between
jobs, and set whether jobs should be monitored
Help Launch the comprehensive online Help system, view Help for the
current window, and display information about the product such
as version and copyright information

The main window toolbar

Button Use this button to...
Cut the currently selected object

Copy the currently selected object

Paste the contents of the clipboard

Open the Work with engines pane

Refresh the contents of the current Object list view

Stop the current server request. This button becomes active when a
request is made to the server and the Job Scheduling Console is
waiting for a response.

60 IBM Tivoli Workload Scheduler Job Scheduling Console: User’s Guide

 Distributed job stream editor toolbar

The distributed job stream editor toolbar

Button Use this button to...
Add a job definition to the job stream you are working on

Add multiple job definitions to the job stream you are working on.

Add an internetwork dependency to the job stream you are

working on

Add a dependency on a job that is in a job stream other than the

one you are working on

Add a dependency on a job stream other than the one you are
working on

Add a link between job definitions in the job stream you are
working on

Switch to the graph view

Switch to the explorer view

Switch to the timeline view

Switch to the run cycle view

Chapter 11. Interface quick reference 61

 z/OS job stream editor toolbar

The z/OS job stream editor toolbar

Button Use this button to...
Add a JCL type job to the job stream you are editing

Add a started task type job to the job stream you are editing

Add a printer type job to the job stream you are editing

Add a general type job to the job stream you are editing

Add a setup type job to the job stream you are editing

Add a write to operator type job to the job stream you are editing

Add a fault-tolerant workstation (FTW) task to the job stream you

are editing

| Add an automation task to the job stream you are editing

|
|
Add a dependency to a job that runs in a job stream other than the
one you are editing

Add a link between jobs in the job stream you are editing

Switch to the explorer view

Switch to the graph view

Switch to the timeline view

62 IBM Tivoli Workload Scheduler Job Scheduling Console: User’s Guide

 z/OS job stream editor toolbar

Button Use this button to...

Switch to the run cycle view

The impact view toolbar

Button Use this button to...
View the predecessors or successors radiating from the job icon

View the predecessors or successors to the left of the job icon

View the predecessors or successors to the right of the job icon

View the predecessors or successors above the job icon

View the predecessors or successors below the job icon

Predecessors Toggle to the predecessors view

Successors Toggle to the successors view

Chapter 11. Interface quick reference 63

Impact view toolbar

64 IBM Tivoli Workload Scheduler Job Scheduling Console: User’s Guide

Chapter 12. z/OS quick reference
This section describes the steps you need to take to get up and running in a z/OS
environment.

Quick definition steps for a z/OS environment

The following steps provide an overview of how to start defining objects in a z/OS
environment.

When and how often should I do

Step Why do this? this?
1. Create Perform this step to create your z/OS workstations. Typically, you perform this step
workstations immediately after installing the Job
Scheduling Console.

After you have created your

workstations, you perform this step
when changes within your
organization require it.
2. Create When your jobs use resources, you must create them in You perform this task each time you
resources the database. have a job that requires use of a
resource. You must create the
resource before you create the job.
3. Create job You must group your jobs into job streams for them to You perform this task each time you
streams be able to run. A job stream can consist of a single job. need a new job stream.
4. Create jobs You must create at least one job for each job stream that You perform this task each time you
you create. need a new job, or each time you
create a new job stream.

Create workstations
The steps involved in creating workstations are the same for z/OS and distributed.
See “Create domains and workstations” on page 73.

Create resources
Perform these steps to create resources in the database:

Action Result Notes

1. Expand the
New Resource
node of the Action
list pane.

© Copyright IBM Corp. 1991, 2006 65

z/OS quick reference

Action Result Notes

2. Select a z/OS Complete the data according to the
engine from the information provided in “General
expanded list. page” on page 108.

Maximum characters for the resource

name is 44.

3. Click Default Complete the data according to the

Workstations. information provided in “Default
Workstations page” on page 109.

Use to search for workstations.

4. Click Complete the data according to

Availability “Availability Intervals page” on page
Intervals. 110.

66 IBM Tivoli Workload Scheduler Job Scheduling Console: User’s Guide

 z/OS quick reference

Create job streams

Perform these steps to create job streams in the database:

Action Result Notes

1. Expand the
New Job Stream
node of the Action
list pane.

| 2. Select a z/OS Complete the data according to

| engine from the “Creating z/OS job streams” on page
| expanded list. 133.

|
|
3. Click OK When you set the job stream as a
template, the Job Stream Editor opens
in the Timeline view and you can
only add run cycle information.

You must add at least one job to a

z/OS job stream before you can save
it. See “Create jobs” on page 68.

Chapter 12. z/OS quick reference 67

 z/OS quick reference

Create jobs
Perform these steps to create a z/OS job in the database:

Action Result Notes

1. Expand a z/OS The job stream list could be
engine in the somewhere other than under Default
Work with Database Lists. See Chapter 33,
engines pane, and “Working with lists,” on page 185.
any sub-lists until
a list containing If you have just created the job
the relevant job stream this step is not necessary.
stream opens.
2. Select the job If you have just created the job
stream where you stream this step is not necessary.
want to create the
job.

| 3. Click a job See “The z/OS job stream editor

| button according toolbar” on page 62.
| to the type of job
| you are adding. The tabs for the different job types
| are the same, however when you
| save the job stream different
| validation policies are applied to the
| properties according to the job type
| you specified.

| Complete the data according to

| “General page” on page 139.

|
|

68 IBM Tivoli Workload Scheduler Job Scheduling Console: User’s Guide

 z/OS quick reference

Action Result Notes

| 4. Click Task. Complete the data according to “Task
| page” on page 141.

|
|
| 4. Click Options. Complete the data according to
| “Options page” on page 141.

|
|

Chapter 12. z/OS quick reference 69

 z/OS quick reference

Action Result Notes

| 5. Click Time Complete the data according to
| Restrictions. “Time Restrictions page” on page
| 143.

|
|
| 6. Click Resources. You must create resources before you
| create the jobs that use them.

| Complete the data according to

| “Resources page” on page 143.

|
|

70 IBM Tivoli Workload Scheduler Job Scheduling Console: User’s Guide

 z/OS quick reference

Action Result Notes

| 7. Click If the job is to run on Tivoli System
| Automation. Automation for z/OS, complete the
| data according to “Automation page”
| on page 145.

|
|

Chapter 12. z/OS quick reference 71

z/OS quick reference

72 IBM Tivoli Workload Scheduler Job Scheduling Console: User’s Guide

 Chapter 13. Distributed quick reference
This section describes the steps you need to take to get up and running in a
distributed environment.

Quick definition steps for a distributed environment

The following steps provide an overview of how to start defining objects in a
distributed environment.

When and how often should I do

Step Why do this? this?
1. Create Perform this step to configure your scheduling network. Typically, you perform this step
workstations and immediately after installing the Job
domains Scheduling Console.

After your Tivoli Workload Scheduler

network is configured, you perform
this step when changes within your
organization require it.
| 2. Create When your job definitions or job streams have values You perform this task each time you
| parameters that are relevant to several fields, you can create a have a parameter that represents a
| parameter so that you do not need to enter the value value for an object.
| each time you create a new object.
3. Create job You can create job definitions before you create a job You perform this task each time you
definitions stream or at the same time you create a job stream. need to create a new job stream.
4. Create When you have a job stream that requires a calendar You perform this task each time you
calendars other than the calendars provided, you need to create a need a job stream to run with a
calendar. calendar structure different from
those calendars provided.
5. Create prompts When you have a job or a job stream that requires a You perform this task each time you
prompt to be answered before it starts, you must create create a job or job stream that
the prompt before you create the job stream. requires a prompt to be answered
before it begins to run.
| 6. Create job When you want to run jobs as a unit (such as running a You perform this task each time you
| streams weekly backup), along with times, priorities and other need a new job stream.
| dependencies that determine the order in which the jobs
| run, you must group your jobs into job streams. A job
| stream can consist of a single job.

Create domains and workstations

Perform this step to configure your scheduling network.
|| Action Result Notes
| 1. Plan your To correctly configure your
| domain structure. scheduling network domain, you
| need to decide the structure and the
| names of the domains and domain
| managers.

© Copyright IBM Corp. 1991, 2006 73

 Distributed quick reference

| Action Result Notes

| 2. Expand the
| New Domain
| node of the Action
| list pane.

|
|
| 3. Select an engine Complete the data according to the
| from the expanded information provided in Chapter 23,
| list. “Creating domains,” on page 123.
| Perform these actions until you have
| created all the domains for your
| network.

| Maximum length for a domain name

| is 16 characters.

|
|
| 4. Expand the The number of engines listed
| New Workstation depends on your organization.
| node of the Action
| list pane.

|
|

74 IBM Tivoli Workload Scheduler Job Scheduling Console: User’s Guide

 Distributed quick reference

| Action Result Notes

| 5. Select a Complete the data according to the
| distributed engine information provided in “Creating a
| from the expanded distributed workstation” on page 103.
| list. Creating z/OS workstations uses the
| same steps, but the properties are
| different. See “Creating a z/OS
| workstation” on page 98. Create as
| many workstations as you need.

| Maximum length for a distributed

| workstation name is 16 characters.
| Maximum length for a z/OS
| workstation name is four characters.

| For distributed, eight workstations is

| a good size for a domain to remain
| efficient.

|
|
|

Create parameters
Perform this step to create parameters in the database.

Action Result Notes

1. Expand the You can create parameters for the
New Parameter following fields for your job
node of the Action definitions:
| list pane. v Login
| v Script
| v Command
| v Prompt
| v File Dependencies

Chapter 13. Distributed quick reference 75

Distributed quick reference

Action Result Notes

2. Select an engine Complete the data according to the
from the expanded information provided in Chapter 20,
list. “Creating parameters,” on page 115.

Maximum length for a parameter

name is eight characters.

Maximum length for the value is 72

characters.

The parameter you provide is

substituted at runtime. For example,
when you create a job definition you
can substitute the Script value with a
parameter, thereby removing the
need to retype the script value each
time you use it.

When you create parameters that are

going to be used in UNIX or
Windows scripts or commands, you
cannot use the double-quotes (″)
character in the value.

Create job definitions

Perform these steps to create job definitions in the database:

Action Result Notes

1. Expand the You can also create your job
New Job definitions at the same time as you
Definition node create your job streams. See “Create
of the Action list job streams” on page 82.
pane.

76 IBM Tivoli Workload Scheduler Job Scheduling Console: User’s Guide

 Distributed quick reference

Action Result Notes

| 2. Select an engine The task types that you can select
| from the expanded provide the same properties panel.
| list. This scenario is to create a Windows
| Script. For a description of the task
| types, see Chapter 25, “Creating job
| definitions,” on page 127.

Complete the data according to the

information provided in Chapter 25,
“Creating job definitions,” on page
127.

Maximum length for the job

definition name is 40 characters.

When you created a parameter for

the login details of a job definition,
you can add it now using Add
Parameter. In Workstation Name you
can nominate a class to indicate that
the job definition is relevant to more
than one workstation.

3. Click Add You can type the name of a

Parameter. parameter, or leave the field blank if
you want to display all parameters.

Chapter 13. Distributed quick reference 77

 Distributed quick reference

Action Result Notes

| 4. Click Start. Select a parameter from the list.

5. Click OK. Complete the Recovery Options

according to the information
provided in Chapter 25, “Creating job
definitions,” on page 127. In
Workstation Name you can nominate
a class to indicate that the job
definition is relevant to more than
one workstation.

78 IBM Tivoli Workload Scheduler Job Scheduling Console: User’s Guide

 Distributed quick reference

Action Result Notes

6. Click Task. You can use the same find
functionality to add a parameter to
the script field. Complete the Return
Code Mapping as described in
Chapter 25, “Creating job
definitions,” on page 127.

Create calendars
Perform these steps to create calendars in the database:

Action Result Notes

1. Expand the If the default calendars are not
New Calendar sufficient for your job streams, you
node of the Action can create your own calendars.
list pane.

Chapter 13. Distributed quick reference 79

Distributed quick reference

Action Result Notes

2. Select an engine Maximum length for the calendar
from the expanded name is eight characters.
list.
You can type a description for the
calendar. Maximum length for the
description is 64 characters.

3. Click Define Specify days to the calendar

Calendar. definitionn. You can define these
days on a monthly or an annual basis
by selecting Monthly or Yearly. You
can use the Select menu to select
common days for each month over a
given time range.

80 IBM Tivoli Workload Scheduler Job Scheduling Console: User’s Guide

 Distributed quick reference

Action Result Notes

4. Select Select > You can choose the last day of each
Day of Month. month in the start and end range by
selecting Last Day Of Month.

Click OK to apply your day of

month selections to the calendar.

Create prompts
Perform these steps to create prompts in the database:

Action Result Notes

1. Expand the
New Prompts
node of the Action
list pane.

2. Select an engine Type the name and the text of the

from the expanded prompt.
list.
Maximum length of the prompt name
is eight characters.

Chapter 13. Distributed quick reference 81

Distributed quick reference

Create job streams

Perform these steps to create job streams in the database:

Note: It is not necessary to perform all of the steps documented here to create a
job stream. Similarly, there are steps that are not documented here that you
might need to perform. For a complete description of creating a distributed
job stream, see “Creating distributed job streams” on page 147.

Action Result Notes

1. Expand the If you intend to use workstation
New Job Stream classes, calendars, predefined
node of the Action prompts, or resources in your job
list pane. stream, you must create them first.
See Chapter 24, “Creating
workstation classes,” on page 125,
Chapter 22, “Creating calendars,” on
page 119, Chapter 21, “Creating
predefined prompts,” on page 117,
Chapter 18, “Creating resources,” on
page 107.
2. Select a Complete the page according to the
distributed engine information provided in “General
from the expanded page” on page 148.
list.
Maximum length for the job stream
name is 16 characters.

Use the Comments page to add

additional information about the job
stream.

3. Click Complete the page according to the

Dependency information provided in
Resolution “Dependency Resolution page” on
page 149.

82 IBM Tivoli Workload Scheduler Job Scheduling Console: User’s Guide

 Distributed quick reference

Action Result Notes

4. Click Time Complete the page according to the
Restrictions. information provided in “Time
Restrictions page” on page 150.

5. Click Resources. Complete the page according to the

information provided in “Resources
page” on page 151.

6. Click Prompts. Complete the page according to the

information provided in “Prompts
page” on page 152.

7. Click Files. Complete the page according to the

information provided in “Files page”
on page 152.

Chapter 13. Distributed quick reference 83

Distributed quick reference

Action Result Notes

8. Click OK. The Job Stream Editor opens with the
newly created job stream. You can
now add the job definitions that you
created earlier, add new job
definitions, modify the job stream
properties, add dependencies
between jobs and job streams, and so
on.

Click... You add a job to a job stream.

You can type a job definition name or

use ... (find). When you use ... the
workstation of the job definition is
completed automatically. For
information about completing the job
definition tabs, see “Adding a job to
a job stream in the Graph View” on
page 222.

Click... You can add multiple job definitions.

84 IBM Tivoli Workload Scheduler Job Scheduling Console: User’s Guide

 Distributed quick reference

Action Result Notes

| Click... You add internetwork dependencies.

Click ... to find the network agent.

Type the dependency in the format
workstation#jobstreamname.jobname

Maximum length for the dependency

is 16 characters for the workstation,
16 characters for the job stream and
40 characters for the job.

| Click... You add an external job dependency.

If you use ... to find the job stream

name, the workstation is
automatically completed.

Click Show Jobs to list the jobs in

the job stream and select the job you
want.

Click OK.

| Click... You add an external job stream

| dependency

Click Show Job Streams to list the

job streams on the workstation and
select the job stream you want.

Click OK.

Chapter 13. Distributed quick reference 85

 Distributed quick reference

Action Result Notes

| Click... You add a link between job
| definitions in the job stream you are
| working on.

There is no visible result when you

click add link. You must click the
first icon you want to link, hold
down the left mouse button and click
the second icon.

86 IBM Tivoli Workload Scheduler Job Scheduling Console: User’s Guide

Chapter 14. Explorer View quick reference
The Explorer View consists of the following main components:
v Tree View pane
v Table View pane
v Properties View pane
This chapter describes the fundamental tasks you can perform using the Explorer
View. The Explorer View is fundamentally the same for distributed and z/OS, but
the functionality does change according to what type of Job Stream editor you are
using. For the differences in functionality, refer to the descriptions of the two Job
Stream editor types.

This quick reference uses the distributed type Job Stream editor for reference. It is
divided into the following sections:
v “Opening a job stream in the Explorer View”
v “Adding a new job to a job stream in the Explorer View” on page 89

Opening a job stream in the Explorer View

Perform these steps to open the Explorer View.

Action Result Notes

1. Expand an
engine and the
Default Database
Lists in the Work
with engines
pane.

© Copyright IBM Corp. 1991, 2006 87

Explorer View quick reference guide

Action Result Notes

2. Select All Job
Streams.

3. Double-click the
relevant job
stream in the table
view.

The job stream editor Explorer View

consists of a:
Click... v Tree View
v Table View
v Properties View

88 IBM Tivoli Workload Scheduler Job Scheduling Console: User’s Guide

 Explorer View quick reference guide

Adding a new job to a job stream in the Explorer View

Perform these steps to add a job to a job stream using the Explorer View.

Action Result Notes

1. Expand an
engine and the
Default Database
Lists in the Work
with engines
pane.

2. Select All Job

Streams.

3. Double-click the
relevant job
stream in the table
view.

Chapter 14. Explorer View quick reference 89

 Explorer View quick reference guide

Action Result Notes

4. Click .

|
| 5. Click .

|
|
7. Click OK.

90 IBM Tivoli Workload Scheduler Job Scheduling Console: User’s Guide

Chapter 15. Troubleshooting quick reference
To trace Job Scheduling Console errors, set the trace parameters described in
Chapter 58, “Setting traces for the Job Scheduling Console,” on page 351.

Job Scheduling Console installation errors are traced in the following files:

On Windows operating systems:

C:\Documents and Settings\<user_name>\Local Settings\Temp

On UNIX and Linux operating systems:

<user_home_dir>/tmp

The log file names are twsconsole_ismp.log (ISMP) and TWSJSC^8.3.log (Software
Distribution).

Connector installation errors are logged in the following directories:

On Windows operating systems:

C:\Documents and Settings\<username>\Local Settings\Temp

On UNIX operating systems:

<user_home_dir>/tmp

The log file name is tws4zosconn.log.

Note: For UNIX operating systems when the user does not have a home directory
set, logs, errors, and stdout data are written to the stdout file and any user
customization is not saved.

© Copyright IBM Corp. 1991, 2006 91

92 IBM Tivoli Workload Scheduler Job Scheduling Console: User’s Guide
Part 4. Defining objects

© Copyright IBM Corp. 1991, 2006 93

94 IBM Tivoli Workload Scheduler Job Scheduling Console: User’s Guide
 Chapter 16. Creating engines
This chapter describes how you create engines.

To create an engine, perform the following steps:

1. In the Actions list pane, click New Engine.
2. Select the engine.

The Define a New Engine for Job Scheduling Console panel displays.

The panel consists of the following:

| Engine Name Type a name for the engine that you are creating.
| Engine Type The type of engine you are creating. Possible values are:
| Distributed
| The engine is a distributed engine.

© Copyright IBM Corp. 1991, 2006 95

 Creating engines for the Job Scheduling Console

| z/OS The engine is a z/OS engine.

| Host Name Type the host name or TCP/IP address of the computer where the
| connector is installed.
| Port Number Type the port number that is used to connect to the computer
| where the connector is installed. The default port number is 31117.
| Remote Server Name
| Specify it when the engine is a z/OS engine. The name of the
| instance of the connector specified in the Engine Name field
| during the installation of the z/OS connector or when you create
| the instance using the createZosEngine WAS tool. See Chapter 62,
| “Managing z/OS engines using WebSphere Application Server
| tools,” on page 413.
| User Name Type the user name of the TWSuser who accesses the computer
| where the connector is installed.
| Password Type the password of the user.

| Note: For some operating systems only the first eight characters of
| the password are used for authentication.
| Save Password
| Save password is enabled when you type a password. When you
| save the password it is not necessary to enter the user name and
| password each time that you access the engine.

96 IBM Tivoli Workload Scheduler Job Scheduling Console: User’s Guide

Chapter 17. Creating workstations
This chapter describes how you create workstations.

To create a workstation, perform the following steps:

1. In the Actions list pane, click New Workstation.
2. Select the engine.

The Properties - Workstation in Database panel depends on whether you are:

v “Creating a z/OS workstation” on page 98
v “Creating a distributed workstation” on page 103

© Copyright IBM Corp. 1991, 2006 97

 Creating a z/OS workstation

Creating a z/OS workstation

| The Properties - Workstation in Database panel displays.
|

|
| The panel consists of the following:
| v “General page”
| v “Resources page” on page 101
| v “Open Time Intervals page” on page 102

General page
Use the General page to enter general information about the workstation.

The page consists of the following:

Name The name of the workstation. The maximum length is 4 characters.
Description A description of the workstation. The maximum length is 32
characters.

98 IBM Tivoli Workload Scheduler Job Scheduling Console: User’s Guide

 Creating a z/OS workstation

Workstation Type
| The type of workstation. Possible values are:
| General For control of jobs and operations not normally
| controlled automatically.
| Printer For tracking, but not controlling the production of
| print output.
| Computer For running batch jobs and started tasks.
Reporting Attribute
A mechanism for reporting status updates on the jobs defined on
the workstation:
Non reporting When jobs on this workstation are set to complete
as they become ready to start. Typically, you use
this mechanism for dummy jobs created to simplify
the sequencing of other jobs.
Automatic When status changes of jobs are reported
automatically in response to event records created
by Tivoli Workload Scheduler. Typically, you use
this mechanism for computer and print
workstations, or for workstations that specify a
user-defined destination.
Manual start and completion
When status changes of jobs are reported from the
Ready List ISPF panel on the host, or from the
results of a workstation status list. Typically, you
use this mechanism for general workstations used
for job preparation, or other general workstations
when the duration of a task needs to be tracked.
Completion only
When status changes of jobs are reported from the
Ready List ISPF panel on the host or from the
results of a workstation status list. Typically, you
use this mechanism for general workstations that
are not used for job preparation.
| Fault-tolerant Use fault-tolerant workstations to run distributed jobs in a z/OS
| plan. Fault-tolerant workstations are automatically defined as
| computer workstations with an automatic reporting attribute.
| When you select this box, all the properties for this workstation are
| disabled and set to their default value. Also the Resources and
| Open Time Interval pages are disabled.
| Automation Use this workstation to interface with Tivoli System Automation
| for z/OS. Tivoli System Automation for z/OS jobs can be defined
| to run on this workstation. Automation workstations are
| automatically defined as General workstations with an Automatic
| reporting attribute. When you select this box, the only property
| you can choose is splittable.
Printout Routing
A data definition name (ddname) of the daily printout data set
where reports for this workstation are to be written.
Destination A destination that corresponds to that specified on a ROUTOPTS
initialization statement. For computer workstations and WTO
general workstations, this is the name of the tracker. The default
destination is the system where the engine is started.

Chapter 17. Creating workstations 99

 Creating a z/OS workstation

Control on servers
The parallel servers required for jobs to start are available on the
workstation. See “Parallel servers” on page 101.
Planning on servers
The parallel servers are for planning purposes only. Submit ready
jobs regardless of the number of servers in use. See “Parallel
servers” on page 101.
Options: Splittable
The jobs on the workstation can be interrupted. Use this attribute
for general workstation jobs where you prepare JCLs for
submission, or on printer workstations. When preparation of the
JCL is interrupted by the issuing a TSAVE command, the operation
is assigned status I. Preparation of the JCL job can continue at a
later time. Computer workstations are not splittable.
Options: Job Setup
When using a general workstation to prepare job JCLs or started
task JCLs manually. This attribute is not necessary when Tivoli
Workload Scheduler can resolve JCL variables automatically.
Options: Started task, STC
When using a computer workstation that runs started tasks rather
than jobs.
Options: WTO
When using a general workstation on which the scheduling
facilities can issue a write-to-operator message to the operator
console designated in Destination.
| Options: Wait Select this check box to define a workstation on which to run a
| general job that waits for the period of time defined in its duration.
| In this way you obtain a controlled delay between a sequence of
| jobs. To define a wait workstation you must set the Workstation
| Type to General and the Reporting Attribute to Non reporting.
| When running, jobs on wait workstations have the Status Details
| set to Running on a WAIT workstation to remind users that a delay
| in the defined sequence of jobs is occurring. When they complete
| the Status Details is blank.
Defaults: Transport Time
The time in HH:MM between the end of a predecessor job and the
beginning of the present job. The transport time of the workstation
is the default transport time for all the jobs defined on the
workstation and is used for planning purposes only.
Defaults: Duration
| The default estimated processing time in HH:MM:SS for all jobs on
| that workstation. Tivoli Workload Scheduler uses the estimated
| processing time when creating the plan, to work out a timetable for
| all jobs. You do not need to give an exact figure, because Tivoli
| Workload Scheduler can adjust it dynamically using actual
| durations. However, your estimation should be as accurate as
| possible. You can override this value by specifying a duration
| when you create a new job. The maximum is 99:59:01.
Access methods: Name
The name of the access method that handles the third-party
product.

100 IBM Tivoli Workload Scheduler Job Scheduling Console: User’s Guide
 Creating a z/OS workstation

Access methods: Node Address

The TCP/IP address or host name of the fault–tolerant agent that
is hosting the access method.
Access methods: Port number
The TCP/IP port number of the tracker agent that is hosting the
access method.

Parallel servers
Use Control on servers and Planning on servers to specify how the workstation
uses parallel servers. When you create a job, you specify how many parallel
servers it requires. The workstation that the job is using must have that number of
parallel servers available before the job can run. You set this value when you create
the workstation. Select both Control on servers and Planning on servers so that
Tivoli Workload Scheduler submits jobs only up to the limit of the number of
servers specified.

If you select Planning on servers only, or nothing, then Tivoli Workload Scheduler
does not evaluate the number of parallel servers when deciding when to start an
operation. The number of parallel servers is used for planning purposes only, and
plans cannot accurately predict the behavior of work in your system because Tivoli
Workload Scheduler submits as many jobs as are ready.

If you select both Control on servers and Planning on servers, or Control on

servers only, the number of parallel servers required by the job must also be
available on the workstation before the job can start.

Resources page
Use the Resources page to define the resources for your workstation. You can
define a maximum of fixed resources called Resource 1 (R1) and Resource 2 (R2),
to schedule or run jobs on a workstation. The names R1 and R2 are provided by
default.

The page consists of the following for each of the two fixed resources:
Name A 2-character unique name for the resource.
Used for Planning
The resource is considered when a plan involving this workstation
is built.
Used for Control
The resource is used when a job runs on this workstation.

Note: The plan contains the best estimation of the time when
operations start. If an unexpected problem occurs, such as a
job exceeds its expected run time, Tivoli Workload Scheduler
might need to reassess the start time of some of the
operations. If you selected Control on servers, Tivoli
Workload Scheduler considers the workstation resource
when rescheduling its operations.

When defined, the two resources are associated to the workstation and are
recognized automatically when you schedule and run jobs on the workstation.
Resources are subject to the following limitations that might make it more practical
to use logical resources:
v The maximum quantity for each resource is 99

Chapter 17. Creating workstations 101

Creating a z/OS workstation

v They cannot be shared by other workstations

v Their name is limited to two characters
R1 and R2 can represent any physical resource in your system that is significant for
scheduling purposes. When you create a new job, you can specify how many
workstation resources (R1, R2, or both) the job uses. If the specified quantity of
resources is not available, the job does not start.

Open Time Intervals page

Use the Open Time Intervals page to define the availability of parallel servers, the
capacity of workstation resources, and the name of an alternate workstation that
enables jobs to run on the workstation. To add an open time interval, click Add
Row. To delete an open time interval, select it and click Remove Row. Modify the
values by double-clicking in the relevant cell.

The page consists of the following:

Day A day of the week. Possible values are:
Standard Standard defines the values that are true at all
times. The additional intervals that you specify
indicate exceptions to the standard. When you
define a new workstation there is a default
Standard row. Use this row to enter the name of an
alternate workstation and the quantities of parallel
servers and workstation resources that you want to
be available.
Specific Date A specific date.
Status The availability status of the workstation. Possible values are:
Defined
To specify that during the interval the workstation is available
in the quantities and with the properties defined in the current
row.
Closed
To specify that the workstation is not available during the
interval. If you select this value, the remaining cells in the row
are disabled.
From Time The start time of the interval time range. The default time range
format is HH:MM AM/PM. The format depends on the setting of
the z/OS workstation.
To Time The end time of the interval time range. The default time range
format is HH:MM AM/PM. The format depends on the setting of
the z/OS workstation.
Parallel Servers
The quantity of parallel servers available to the workstation during
the time interval. Leave this field blank if you did not specify
parallel servers in the “General page” on page 98. The maximum
value is 99.
R1 Capacity The available R1 resource quantities for each interval when you
specified resources for this workstation in the “Resources page” on
page 101. The maximum value is 99.
R2 Capacity The available R2 resource quantities for each interval when you
specified resources for this workstation in the “Resources page” on
page 101. The maximum value is 99.

102 IBM Tivoli Workload Scheduler Job Scheduling Console: User’s Guide
 Creating a z/OS workstation

Alternate Workstation
The name of a workstation of the same type that can be used
during the interval if this workstation becomes unavailable.
Alternate Workstation is available for computer and WTO general
workstations only.

Note: For the best results the configuration of the two

workstations should be symmetrical.

Creating a distributed workstation

The Properties - Workstation in Database panel displays.

The panel consists of the following:

Chapter 17. Creating workstations 103

 Creating a distributed workstation

| Ignore The scheduler does not include this workstation in the plan. Ignore
| can be used to define workstations as database objects before they
| are installed.
Name The name of the workstation. The name must start with a letter
and can contain alphanumeric characters, dashes, and underscores.
The maximum length is 16 characters. Workstation names must be
unique and cannot be the same as workstation class and domain
names.
Domain The workstation domain name. The name must start with a letter
and can contain alphanumeric characters, dashes, and underscores.
The maximum length is 16 characters. Domain names must be
unique and cannot be the same as workstation and workstation
class names.
Use Master Click Use Master to specify that the workstation is in the master
domain.
Description A description of the workstation. The maximum length is 120
characters.
Workstation Type
The type of workstation. Possible values are:
Domain Manager
An agent workstation that is the manager of a
domain of workstations.
Fault-tolerant Agent
An agent workstation that launches jobs and
resolves local dependencies without a domain
manager.
Extended Agent
An agent workstation that launches jobs only
under the direction of its host. Extended agents can
be used to interface Tivoli Workload Scheduler
with non-Tivoli systems and applications. For more
information refer to the user manual for the
extended agent.
Standard Agent
An agent workstation that launches jobs only
under the direction of its domain manager.
Operating System
The operating system of the workstation. Possible values are:
v UNIX
v Windows
v Other
Full Status Full Status is for fault-tolerant agents only. When you select Full
Status the agent is updated with the status of jobs and job streams
running on all other workstations in its domain and subordinate
domains. Otherwise, the agent is updated with the status of jobs
and job streams on other workstations that affect its own jobs and
job streams. Select Full Status to keep an agent production plan at
the same level of detail as its domain manager. Backup domain
managers must always be full status.
Time Zone The time zone of the workstation. Choose a time zone from the
drop-down list. For a description of time zone names, refer to the
IBM Tivoli Workload Scheduler: Reference Manual. To ensure the

104 IBM Tivoli Workload Scheduler Job Scheduling Console: User’s Guide
 Creating a distributed workstation

accuracy of scheduling times, this time zone must be the same as

the workstation operating system time zone. The Time Zone
feature is enabled using the optman command. See IBM Tivoli
Workload Scheduler: Planning and Installation Guide.
Node Name The host name or the IP address of the workstation. You can use
fully-qualified domain names.
TCP Port The netman TCP/IP port number that Tivoli Workload Scheduler
uses for communication on the workstation. The default is 31111.
The netman TCP/IP port number is defined in the localopts
parameter nm port. The port number range is 1-65535.
SSL Communication
The type of Secure Socket Layer (SSL) communication. Possible
values are:
Disabled The workstation does not use SSL authentication.
Allow Incoming
The workstation uses SSL authentication to accept
any incoming connection from its parent domain
manager if it is not an SSL connection.
Upward Forced
The workstation uses SSL authentication when it
connects with its domain manager. The domain
manager uses SSL authentication when it connects
to a parent domain manager, and the master
domain manager has SSL authentication enabled.
All Forced The workstation uses SSL authentication for all of
its connections. It will refuse any incoming
connection if it is not an SSL connection.

Disable SSL by selecting the blank space in the drop-down list.

SSL Port The number of the secure port to be used for SSL communication.
The default value is 31113. The range is 1-65535.
Mailman Server
Mailman Server is for fault-tolerant and standard agents only. It is
a mailman server on the domain manager that handles
communication with agents. Using servers reduces agent
initialization time and improves message efficiency.
To specify a server, select a letter or a number (A-Z and 0-9) from
the drop-down list. The IDs are unique to each domain manager,
so you can use the same IDs in other domains without conflict. If
more than 36 server IDs are required in a domain, consider
dividing it into two or more domains.
When you do not specify a server, communication with agents is
handled by the main mailman process on the domain manager.
When a domain manager starts it creates a separate server for each
unique server ID. If the same ID is used for multiple agents, a
single server is created to handle their communication. Define a
server for groups of 8 agents.
Behind Firewall
A firewall exists between the workstation and its domain manager.
Auto Link Whether to open the link between workstations at startup. For
fault-tolerant and standard agents, select this option to have the

Chapter 17. Creating workstations 105

 Creating a distributed workstation

domain manager open the link to the agent when the domain
manager is started. For a domain manager, select this option to
have its agents open links to the domain manager when they are
started. See IBM Tivoli Workload Scheduler: Planning and Installation
Guide.
Access Method
An access method for extended agents and network agents. Access
Method is the name of a method file that resides in the
TWShome/methods directory on the agent host workstation. For local
UNIX extended agents, the method name is unixlocl. For remote
UNIX extended agents the method name is unixrsh. For network
agents, the method name is netmth. For more information about
extended agents, refer to the extended agent user guide. For more
information about network agents, refer to the IBM Tivoli Workload
Scheduler: Reference Manual.
| Host The name of the agent host workstation. Host is required for
| extended agents. The host is the workstation with which the
| extended agent communicates and where its access method resides.
| The host for an extended agent must be a master, domain manager,
| or fault-tolerant agent. The host can be specified as $MASTER,
| which assigns the master domain manager as host, and is useful if
| you need to switch masters in the domain. In this case the
| extended agent automatically connects to the new manager.

106 IBM Tivoli Workload Scheduler Job Scheduling Console: User’s Guide
Chapter 18. Creating resources
This chapter describes how you create resources.

To create a resource, perform the following steps:

1. In the Actions list pane, click New Resource.
2. Select the engine.
The Properties - Resource in Database panel depends on whether you are:
v “Creating a z/OS resource”
v “Creating a distributed resource” on page 111

Creating a z/OS resource

The Resource in Database panel displays.

The panel consists of the following:

v “General page” on page 108
v “Default Workstations page” on page 109
v “Availability Intervals page” on page 110

© Copyright IBM Corp. 1991, 2006 107

 Creating z/OS resources

General page
Use the General page to enter general information about the resource.

The page consists of the following:

Name The name of the resource.
Description A description of the resource.
Hiperbatch™ Whether the resource is a data set eligible for Hiperbatch.
Hiperbatch is a host performance enhancement that works with the
Data Lookaside Facility (DLF) to enable batch jobs and started
tasks to share access to data sets.
Group ID An identifier of the group to which the resource belongs. The
group ID can be used as a list filter for selecting subsets of
resources. The maximum length for this field is 8 characters.
Used for At which stage availability of the resource should be checked.
Possible values are:
Planning When the current plan is extended. For example,
this ensures that jobs with a high output that could
slow your system do not run at the same time.
Control When a job that uses the resource starts.
Planning and control
When the current plan is extended and the a job
that uses the resource starts.
Neither planning nor control
When the availability of the resource is not for
planning or control.
On error The action to take when a job that allocates this resource ends in
error and does not have an overriding keep-on-error specification
in the job definition. Possible values are:
Free Free the full allocation of this resource, both
exclusive and shared.
Keep Keep the full allocation of this resource. You might
want critical jobs to keep their resources even
when they fail, to avoid having to wait for
resources when the job is restarted.
Free if exclusive
Free the full exclusive allocation of this resource.
Free if shared Free the full shared allocation of this resource.
Assume system default
Use the default specified in the ONERROR
keyword of the RESOPTS statement. The default
value is FREESR.
| On Complete The action to take when the job finishes successfully (complete
| status). Possible values are:
| Available Switch the global availability status of the resource
| to yes when a job that uses this resource completes
| successfully.
| Unavailable Switch the global availability status of the resource
| to no when a job that uses this resource completes
| successfully.

108 IBM Tivoli Workload Scheduler Job Scheduling Console: User’s Guide
 Creating z/OS resources

| Automatically reset
| Switch the global availability status of the resource
| to blank when a job that uses this resource
| completes successfully.
| Assume system default
| Switch the global availability status and quantity of
| the resource to the default value when a job that
| uses this resource completes successfully. The
| system checks for the following, in order:
| 1. If the Default: Is Available field (see below)
| has been set for the resource, it makes the
| resource available, using the Default: Quantity
| value
| 2. If Default: Is Available is not set, the system
| uses the value in the ONCOMPLETE keyword
| of the RESOPTS statement to determine the
| availability status.
| Max Usage Type
| Indicates how to change the resource availability when Max Usage
| Limit is exceeded. It is optional and is valid only if Max Usage
| Limit is nonzero. Possible values are:
| Available Switch the global availability status of the resource
| instance to yes when the usage counter exceeds the
| value specified in Max Usage Limit
| Unavailable Switch the global availability status of the resource
| instance to no when the usage counter exceeds the
| value specified in Max Usage Limit
| Automatically reset
| Switch the global availability status of the resource
| instance to blank when the usage counter exceeds
| the value specified in Max Usage Limit
| Max Usage Limit
| Specifies the maximum number of allocations (quantity is not
| considered) after which the resource global availability is changed.
| An internal usage counter is increased each time an operation
| allocates the resource. When this internal counter reaches Max
| Usage Limit the global availability is changed as specified by Max
| Usage Type. The default is zero, which means that no usage
| counter check is done. Possible values for this field are between 0
| and 999999.
Default: Is Available
Whether the resource is usually available. Use the “Availability
Intervals page” on page 110 to specify when the resource is not
available.
Default: Quantity
A number in the range of 1-999 999 of this resource to be reserved
when you select Is Available for the availability intervals
associated with the resource. This information is used as the
default.

Default Workstations page

Use the Default Workstations page to list the workstations associated with and
reserved for the resource.

Chapter 18. Creating resources 109

Creating z/OS resources

By default, all workstations are already added when the Resource Editor panel for
a new resource opens.

To add one or more workstations, click Find.

To remove a workstation from the list, select it and click Delete From Table.

Availability Intervals page

Use the Availability Intervals page to define the time intervals when the resource
can be used.

To add an availability interval, click Add Row and select the interval.

The page consists of the following:

Day The day of the availability interval. Possible values are:
Standard Represents the norm where the resource is used
with the values you entered in the other tabs.
Specific Date Select a day or specific date when the resource is
available with different Quantity, Availability, and
Connected Workstations characteristics that you
specify in the row.
From Time Together with To Time specifies the time interval when the
resource is available.
To Time Together with From Time specifies the time interval when the
resource is available.
Quantity The quantity of the resource that is available during the time
interval.
Is Available Whether the resource is available during the time interval. Possible
values are:
Available The resource is available during the time interval.
Not Available The resource is not available during the time
interval.
Default The availability of the resource is specified in the
“General page” on page 108.
Workstations The names of one or more connected workstations, each separated
by a blank or double-click the Workstation column and click Find
Workstation.

110 IBM Tivoli Workload Scheduler Job Scheduling Console: User’s Guide
 Creating distributed resources

Creating a distributed resource

The Properties - Resource in Database panel displays.

The panel consists of the following:

Name The name of the resource. The name must start with a letter and
can contain alphanumeric characters, dashes, and underscores. The
maximum length is 8 characters.
Workstation Name
| The name of the workstation or workstation class on which the
| resource is defined.
| Description A description of the resource. The maximum length is 120
| characters.
Quantity The number of available resource units. Values can be 0 through
1024.

Chapter 18. Creating resources 111

Creating distributed resources

112 IBM Tivoli Workload Scheduler Job Scheduling Console: User’s Guide
Chapter 19. Creating Windows users
This chapter describes how you create Windows users in a distributed
environment.

To create Windows users, perform the following steps:

1. In the Actions list pane, click New Windows User.
2. Select the engine.

The Properties - Windows User panel displays.

The panel consists of the following:

User Name The Windows user name. The maximum length is 31 characters.
Windows user names are case-sensitive. A Windows user needs
access to the workstation where Tivoli Workload Scheduler
launches jobs, and have the right to Log on as batch. When a
name is not unique it is considered to be a local user, a domain
user, or a trusted domain user, in that order.
Windows Domain
The Windows domain of the user. If the name is not fully qualified
(that is, no Windows domain is entered) or is not unique, it is
considered to be a local user, a domain user, or a trusted domain
user, in that order.
Windows Workstation
The name of the Tivoli Workload Scheduler workstation where the
user can launch jobs.
Password The user password as defined on the Windows computer.
Confirmation The user password again for confirmation.

© Copyright IBM Corp. 1991, 2006 113

114 IBM Tivoli Workload Scheduler Job Scheduling Console: User’s Guide
 Chapter 20. Creating parameters
This chapter describes how you create parameters for the distributed environment.

| Note: If you rename a parameter and submit a job that refers to the old name an
| error occurs.

To create a new parameter, perform the following steps:

1. In the Actions list pane, click New Parameter.
2. Select the engine.
The Properties - Parameter panel displays.

The panel consists of the following:

Name The name of the parameter. The name must start with a letter and
can contain alphanumeric characters, dashes, and underscores. The
maximum length is 8 characters.
Value The value assigned to the parameter. Do not include the names of
other parameters. If you are creating a parameter that is to be used
in job scripts or commands, you cannot use double-quotes (″) in
the value.

© Copyright IBM Corp. 1991, 2006 115

116 IBM Tivoli Workload Scheduler Job Scheduling Console: User’s Guide
 Chapter 21. Creating predefined prompts
This chapter describes how you create predefined prompts for the distributed
environment. For information about how to create ad hoc prompts, see “Creating
distributed job streams” on page 147

To create a prompt, perform the following steps:

1. In the Actions list pane, click New Prompt.
2. Select the engine.
The Properties - Prompt panel displays.

The panel consists of the following:

Name The name of the prompt. The name must start with a letter and
can contain alphanumeric characters, dashes, and underscores. The
maximum length is 8 characters.
| Text The text of a prompt. The default behavior of a prompt is to
| display a message and wait for a reply. Based on the character
| preceding the text, the prompt can behave differently:
| v If the text begins with a colon (:), the prompt is displayed, but
| no reply is required to continue processing.
| v If the text begins with an exclamation mark (!), the prompt is
| displayed, but it is not recorded in the log file.
| Refer to the IBM Tivoli Workload Scheduler: Reference Manual for a
| detailed explanation on how to specify the text of a prompt.

© Copyright IBM Corp. 1991, 2006 117

118 IBM Tivoli Workload Scheduler Job Scheduling Console: User’s Guide
 Chapter 22. Creating calendars
This chapter describes how you create calendars for distributed engines. It is
divided into the following sections:
v “Creating a calendar”
v “Defining a calendar” on page 120

Creating a calendar
To create a calendar in the database, perform the following steps:
1. In the Actions list pane, click New Calendar.
2. Select an engine.
The Properties - Calendar panel displays.

The panel consists of the following:

Name The name of the calendar. The name must start with a letter and
can contain alphanumeric characters, dashes, and underscores. The
maximum length is 8 characters.

Note: You cannot use Tivoli Workload Scheduler keywords (for

example, freedays and schedule).
Description A description of the calendar. The maximum length is 120
characters.
Define Calendar
| Click Define Calendar to specify the dates of the calendar. See
| “Defining a calendar” on page 120.

Note: The maximum size of the calendars you create and manage depends on the
size of your system RAM. For example, the maximum calendar size for a
computer with 256 MB RAM is 1000 consecutive days (3 years). If you select
a calendar for a job stream that is larger than your RAM can manage, the
job stream definition process hangs, and must be stopped.

© Copyright IBM Corp. 1991, 2006 119

Defining a calendar

Defining a calendar
To define the dates of a calendar, perform the following steps:
1. Click Define Calendar. The Monthly Yearly Calendar panel displays.

2. Select Monthly or Yearly to view a monthly or yearly calendar.

3. To add a specific date to the calendar, click the date in the calendar view.
4. To add a specific day of the month, select Day of Month from the Select menu.
The Day of Month panel displays.

120 IBM Tivoli Workload Scheduler Job Scheduling Console: User’s Guide
 Defining a calendar

5. To add a day of the month by number, select the day number in the Day
drop-down list. To add the last day of the month, select the Last Day of Month
option.
6. Select start and end dates for the calendar by selecting the month and year
from the Start and End drop-down lists. The days you specify are selected for
every month in this range. Click OK.
7. Click OK to close and save the calendar.

Chapter 22. Creating calendars 121

Defining a calendar

122 IBM Tivoli Workload Scheduler Job Scheduling Console: User’s Guide
 Chapter 23. Creating domains
This chapter describes how you create domains for distributed engines.

To create a domain, perform the following steps:

1. In the Actions list pane, click New Domain.
2. Select the engine.

The Properties - Domain panel displays.

The panel consists of the following:

Domain Name
The name of the domain. The name can start with a letter or with
a number and can contain alphanumeric characters, dashes, and
underscores. The maximum length is 16 characters.

Note: Domain names must be unique and cannot be the same as

workstation and workstation class names.
Description A description of the domain. The maximum length is 120
characters.
Parent Domain
| The name of the parent domain. The default is the master domain.
Domain Manager
The name of the domain manager workstation. The domain
manager must be a workstation defined:
| v In the same domain
| v As fault-tolerant agent with Full Status selected.

© Copyright IBM Corp. 1991, 2006 123

Creating domains

Note: When creating a new domain, you can specify a domain

manager workstation that does not yet exist.
Is Master This read-only check box indicates that the domain is the master
domain.

124 IBM Tivoli Workload Scheduler Job Scheduling Console: User’s Guide
Chapter 24. Creating workstation classes
This chapter describes how you create workstation classes for distributed engines.

To create a new workstation class, perform the following steps:

1. In the Actions list pane, click New Workstation Class.
2. Select the engine.

The Properties - Workstation Class panel displays.

The panel consists of the following:

v “General page”
v “Workstations page” on page 126

General page
Use the General page to enter general information for the workstation class.

The page consists of the following:

Name The name of the workstation class. The name must start with a
letter and can contain alphanumeric characters, dashes, and
underscores. The maximum length is 16 characters.

Note: Workstation class name must be unique and cannot be the

same as workstation and domain names.
Description A description of the workstation class. Maximum length is 120
characters.
Ignore The jobs that belong to this workstation class are not submitted
into the plan.

© Copyright IBM Corp. 1991, 2006 125

 Creating a distributed workstation class

Workstations page
Use the Workstations page to associate the workstations to the workstation class.

The page consists of the following:

| Find Workstation
| Click Find Workstations to search for the workstations to associate
| to the workstation class. In the Find Workstation panel, click
| Apply to add the workstation to the workstation class and keep
| the panel open to perform another selection, click OK to add the
| workstation to the workstation class and close the panel.
Add All Workstations

Click to add all the workstations in the database to the

workstation class.
Delete From Table

Select a row and click to remove a workstation from the

workstation class.

126 IBM Tivoli Workload Scheduler Job Scheduling Console: User’s Guide
Chapter 25. Creating job definitions
This chapter describes how to create a job definition for a distributed engine.

To create a job definition, perform the following steps:

1. In the Actions list pane, click New Job Definition.

Note: You can also create a job definition from the job stream editor. See
“Adding a job to a job stream in the Graph View” on page 222.
2. Select the engine.

The Properties - Job Definition panel displays.

The panel consists of the following:

v “General page” on page 128
v “Task page” on page 130

© Copyright IBM Corp. 1991, 2006 127

 General page

General page
Use the General page to provide general information about the new job definition.

The page consists of the following:

Task Type Select the type of task. Possible values are:
| Windows The job is an executable file or a command on a
Windows workstation.
| UNIX The job is an executable file or a command on a
UNIX workstation.
| Other The job is an executable file or a command that
runs on a workstation other than UNIX or
Windows.
SAP The job is a SAP job that runs on an Tivoli
Workload Scheduler Extended Agent for SAP. The
SAP task type is only displayed if the Extended
Agent for SAP has been installed. For more
information on SAP jobs, refer to IBM Tivoli
Workload Scheduler for Applications: User’s Guide.
Name The name of the job. The name must start with a letter, and can
contain alphanumeric characters, dashes, and underscores. The
maximum length 40 characters.
Workstation Name
The name of the workstation or workstation class where the job
runs.
Description A description of the job. The maximum length is 120 characters.
Login The name of the user who launches the job. The maximum length
is 47 characters. Specify a user that can log on to the workstation
where the job runs. For Windows jobs, the user must also be
defined in the database. For more information, see Chapter 19,
“Creating Windows users,” on page 113. To include a parameter,
perform the steps described in “Adding parameters to jobs” on
page 131.
| Recovery Options: Stop
| If the job ends in error and there is a follow dependency,
| processing does not continue with the next job. Stop is the default.
| Recovery Options: Continue
| If the job ends in error and there is a follow dependency,
| processing continues with the next job.
Recovery Options: Rerun
If the job ends in error, rerun the job.
Recovery Options: Message
| The text of a recovery prompt to be displayed if the job ends in
| error. The text can contain up to 64 characters. The recovery
| prompt is an ad hoc prompt. The Status of All Prompts plan list
| shows all prompts. If the job ends in error the prompt status
| changes from Not Asked to Asked. If the job ends successfully, the
| status is Not Asked. A message is always displayed.

128 IBM Tivoli Workload Scheduler Job Scheduling Console: User’s Guide
 General page

Recovery Options: Job

The name of a recovery job to run if the parent job ends in error.
Recovery jobs are run only once for each instance of the parent job
ended in error.
Recovery Options: Workstation Name
The name of the workstation where the recovery job runs. The
name is entered automatically when you select a recovery job.
Not all jobs are eligible to have recovery jobs run on a different
workstation. Follow these guidelines:
v If either workstation is an extended agent, it must be hosted by
a domain manager or a fault-tolerant agent that runs in Full
Status mode.
v The recovery job workstation must be in the same domain as the
parent job workstation.
v If the recovery job workstation is a fault-tolerant agent, it must
run in Full Status mode.

Table 8 summarizes possible combinations of recovery options and actions. The

table is based on the following criteria from a job stream called sked1:
v Job stream sked1 has two jobs, job1 and job2.
v If selected for job1, the recovery job is jobr.
v job2 is dependent on job1 and will not start until job1 is complete.
Table 8. Job stream recovery options
Prompt / Job Stop Continue Rerun
Recovery prompt: No Intervention is Run job2. Rerun job1. If job1 ends
Recovery job: No required. in error, issue scheduler
prompt. If reply is yes,
repeat above. If job1 is
successful, run job2.
Recovery prompt: Yes Issue recovery Issue recovery Issue recovery prompt.
Recovery job: No prompt. prompt. If reply is If reply is yes, rerun
Intervention is yes, run job2. job1. If job1 ends in
required. error, repeat above. If
job1 is successful, run
job2.
Recovery prompt: No Run jobr. If it ends Run jobr. Run Run jobr. If jobr ends in
Recovery job: Yes in error, job2. error, intervention is
intervention is required. If jobr is
required. If it is successful, rerun job1. If
successful, run job1 ends in error, issue
job2. scheduler prompt. If
reply is yes, repeat
above. If job1 is
successful, run job2.
Recovery prompt: Yes Issue recovery Issue recovery Issue recovery prompt.
Recovery job: Yes prompt. If reply is prompt. If reply is If reply is yes, run jobr.
yes, run jobr. If it yes, run jobr. Run If jobr ends in error,
ends in error, job2. intervention is required.
intervention is If jobr is successful,
required. If it is rerun job1. If job1 ends
successful, run in error, repeat above. If
job2. job1 is successful, run
job2.

Chapter 25. Creating job definitions 129

General page

Notes:
1. Intervention is required means that job2 is not released from its dependency
on job1, and therefore must be released by the operator.
2. The continue recovery option overrides the abend state, which may cause the
schedule containing the job ended in error to be marked as successful. This will
prevent the schedule from being carried forward to the next day.
3. If you select the Rerun option without supplying a recovery prompt, when the
job is unsuccessful Tivoli Workload Scheduler creates a prompt that requests
whether to proceed.
4. To reference a recovery job in conman, you must use the name of the original
job (job1 in the scenario above, not jobr). Recovery jobs are run only one per
abend.

Task page
Use the Task page to define the task.

The page consists of the following:

Script When the task is a script, this is the file name and any options and
arguments. The maximum length is 4095 characters. For Windows
jobs, include the file extensions. Universal Naming Convention
(UNC) names are permitted. Do not specify files on mapped
drives. For task types other than Windows, if the file name
contains spaces type the name in a file that does not have spaces
and use the second file. For task types other than Windows, double
quotes (") are not permitted.
Command When the task is a command, this is the name of the command the
job runs and any options and arguments. The maximum length is
4095 characters. Commands are run directly and the jobmanrc
standard configuration script is not run. To include a parameter in
the Command field, perform the steps described in “Adding
parameters to jobs” on page 131. For task types other than
Windows, double-quotes (″) are not permitted.
Add Parameter
The script or command definition requires a parameter. For
information about adding parameters, see “Adding parameters to
jobs” on page 131.
Is Interactive For Windows jobs, the job runs interactively on the Windows
desktop.
Return Code Mapping Expression
The Return Code Mapping section enables users to define which
return codes qualify the job as having completed successfully. In
the Expression field, enter a logical expression that defines the
success condition. Use the following syntax:
(RC <operator> <operand>)

where:
RC The instruction keyword
operator
The comparison operator. Allowed operators are
comparison operators (=, != or <>, >, >=, <, <=) that can be
combined with logical operators (AND, OR, NOT).

130 IBM Tivoli Workload Scheduler Job Scheduling Console: User’s Guide
 Taskl page

operand
Any integer between -2147483647 and 2147483647.

For example, to accept a job as successful when the job ends with a
return code less than or equal to 3, you enter the following
expression:
(RC<=3)

The success condition can be a maximum of 256 characters.

Adding parameters to jobs

You can add parameters to Script, Command, or Login fields.

To include a parameter in a task, perform the following steps:

| 1. Type the parameter name within ^ (caret) or
| place the cursor in the field where you want to insert the parameter and click
| Add Parameter. The Find Parameters panel displays.
| a. Type a parameter name. The name can contain wildcard characters.
| b. Click Start. A list of all the parameters defined displays.
| c. Select a parameter name in the list and click OK.
| The parameter name displays in the related field.
| 2. Proceed with the other information.

Extended agent
Refer to the specific user guide for the Extended Agent you are working with for
more information.

SAP job
Refer to the Tivoli Workload Scheduler for Applications User’s Guide for information
about defining the task.

Chapter 25. Creating job definitions 131

Taskl page

132 IBM Tivoli Workload Scheduler Job Scheduling Console: User’s Guide
 Chapter 26. Creating job streams
| This chapter describes how you create job streams. For information about
| managing job streams, see Chapter 36, “Managing z/OS job streams,” on page 199
| and Chapter 37, “Managing distributed job streams,” on page 219.

To create a job stream, perform the following steps:

1. In the Actions list pane, click New Job Stream.
2. Select the engine.
The Job Stream panel depends on whether you are:
v “Creating z/OS job streams”
v “Creating distributed job streams” on page 147

Creating z/OS job streams

Creating a z/OS job stream consists of the following:
v “Creating the job stream” on page 134
v “Creating a job” on page 136

After you have created a job stream and added at least one job, you use the job
stream editor to manage it. See Chapter 36, “Managing z/OS job streams,” on page
199

© Copyright IBM Corp. 1991, 2006 133

 Creating a job stream for a z/OS engine

Creating the job stream

| The Properties – Job Stream panel displays.
|

| The panel consists of the following:

Job Stream Name
A name for the job stream or template.

Note: The name, valid date, and status uniquely identify each job
stream or template. You can define up to four job streams
and job stream templates that share the same name but have
different valid dates.
Description A description of the job stream or template.
Owner Any information relevant to the owner of the job stream.
Owner Description
Any additional information about the owner of the job stream.
Template That this is a job stream template. A job stream template contains

134 IBM Tivoli Workload Scheduler Job Scheduling Console: User’s Guide
 Creating a job stream for a z/OS engine

run cycles but no jobs. All job streams defined as belonging to a

template inherit the run cycles defined for the template.
| Is Active That the job stream is ready.
Inherits from Template
The name of the template if you are defining a job stream that
belongs to a job stream template. The job stream is scheduled
using the template run cycle information.
Contains Monitored Job
Whether any of the jobs in this job stream are monitored by IBM
Tivoli Business Systems Manager. Possible values are:
Yes The job stream contains a job with Monitored Job
selected.
No The job stream does not contain a job with
Monitored Job selected.

When you are creating a new job stream this field is always set to
no.
Authority Group Name
A name to be used to generate a RACF® resource name for
authority checking.
Calendar The name of the calendar of workdays and free days, including
holidays, that you associate to the job stream. If you leave this field
blank, the scheduler uses the calendar specified in the initialization
parameter CALENDAR during startup of the TCP/IP server.

Note: The calendar that you specify here is used to display the run
days of the job stream in the Run Cycle view of the Job
Stream Editor. It is not necessarily the calendar that is used
to determine the actual run days of the job stream instances
that are generated.
Priority The priority of the job stream. The lowest priority is 1 and the
highest priority is 9. For example when job streams are competing
for resources a job stream with a priority of 3 runs before a job
stream with a priority of 1. Other factors such as resource and
workstation dependencies are considered in determining priority.
This field does not apply to job stream templates.
Valid Date The interval of time for which the job stream is valid in the From
and To range you specify. You can create up to four job streams
with the same name but with different From dates. The scheduler
selects the correct version for the day being planned. The To field
is an information field that indicates the job stream is valid until
12/31/2071.
| Feedback Options
| The scheduler automatically monitors the actual deadline of job
| streams. It can use this deadline to modify the estimates in the
| application description (AD) database. Possible values are:
| Smoothing Factor
| A number from 0 to 999 that determines how much
| a measured duration changes existing values in the
| AD database. If a measured deadline is outside the

Chapter 26. Creating job streams 135

 Creating a job stream for a z/OS engine

| limit set by Limit for feedback, the smoothing

| factor is not applied and the AD database is not
| updated.
| Limit for Feedback
| A number from 100 to 999 to set the limit within
| which measured values are regarded as acceptable.
| A measured value outside the limit is ignored, no
| smoothing factor is applied, and the AD database
| is not updated.

| Values entered in these fields override the default values in the

| JTOPTS options engine parameter.

Click OK.

Note: When you are creating a job stream template, the job stream editor opens
the Timeline view, where you can open the Run Cycle view. You can add
only run cycle information to a job stream template. See “Scheduling z/OS
job streams” on page 202.
When you have created the job stream, you must create at least one job.

Creating a job
To create a job for a z/OS job stream, perform the following steps.
1. Run a list of z/OS job streams that contains the job stream where you want to
add the job. See Chapter 33, “Working with lists,” on page 185.

Note: When you have just created the job stream, the Job Stream Editor opens
automatically.
2. Double-click the job stream in the list.
The Job Stream Editor opens.

136 IBM Tivoli Workload Scheduler Job Scheduling Console: User’s Guide
 Creating a job stream for a z/OS engine

3. Click the icon relevant to the type of job you are adding. Possible icons are:

Add a JCL type job to the job stream you are editing. A JCL job
consists of JCL statements and runs on computer workstations.

Add a started task type job to the job stream you are editing. A
started task runs on computer workstations on which a started
task (STC) is selected.

Add a printer type job to the job stream you are editing. A
printer job is a job to print the output of a predecessor job and
runs on printer workstations.

Add a general type job to the job stream you are editing. A
general job is a job that includes activities other than printing
and processing, such as manual activities and runs on general
workstations.

Chapter 26. Creating job streams 137

 Creating a job stream for a z/OS engine

Add a setup type job to the job stream you are editing. A setup
job is a job that contains a set of JCL statements for a JCL or
started task job and runs on general workstations on which Job
setup is selected.

Add a write to operator type job to the job stream you are
editing. A write-to-operator job is a job that contains an
operator instruction displayed on the system console and runs
on general workstations on which WTO is selected.

Add a fault-tolerant workstation (FTW) task to the job stream

you are editing. An FTW job is a job to run on a fault-tolerant
workstation.
|

|
| Add an automation task to the job stream you are editing.
| The Properties - Job Type panel displays.

138 IBM Tivoli Workload Scheduler Job Scheduling Console: User’s Guide
 Creating a job stream for a z/OS engine

|
| The property panels for the different job types are identical. However, when
you save the job stream, Tivoli Workload Scheduler applies different validation
policies to the properties that you specified, based on the job type. When you
search for a target workstation, only workstations compatible with the specific
job type are listed.
The panel consists of the following:
v “General page”
v “Task page” on page 141
v “Options page” on page 141
v “Time Restrictions page” on page 143
v “Resources page” on page 143
v “Automation page” on page 145

General page
Use the General page to enter general information for the job.

| The page consists of the following:

| Name The job name. The job name can be a number from 1-255.
| Target Workstation
| The name of the workstation where the job is run. Click ... (find) to
| search for and select the workstation.
| Description A description of the job. The maximum length is 24 characters.

Chapter 26. Creating job streams 139

 Creating a job stream for a z/OS engine

| Auto Hold Release

| Release the job when it is not submitted by Tivoli Workload
| Scheduler and is in HOLD status. The job is released when all
| dependencies are satisfied and the requested resources are
| available. Auto Hold Release is the default.
| Cancel if Late Prevent the job from being started if it is late. Cancel if Late and
| No Restrictions in the Time Restrictions page are mutually
| exclusive. See “Time Restrictions page” on page 143.
| Auto Error Completion
| Mark the job ended-in-error (E) if an error occurs when it runs. If
| you clear it, the job is marked complete (C) when it ends regardless
| of the outcome.
| Auto Job Submission
| Start the job automatically or issue a WTO message (when all
| dependencies have been satisfied and all required resources are
| available). Auto Job Submission is selected by default.
| Deadline WTO
| Issue an operator message if the job passes its deadline. The
| message is also written to the message log.
| Monitored Job
| The running of this job is to be monitored by Tivoli Business
| Systems Manager. Changes to the monitored job status are not
| displayed in the job stream properties until you close and reopen
| the job stream.
| Centralized Script
| The script associated with the job resides on the master domain
| manager.
| Highest Acceptable Return Code
| The highest acceptable return code from any step in the job before
| the job is set to ended-in-error (E) status. If you leave this field
| blank, Tivoli Workload Scheduler for z/OS uses the value specified
| in HIGHRC in the initialization parameter JTOPTS. The range is
| from 0 to 4095.
| Critical Job The job is a critical job, which makes the job eligible for Tivoli
| Workload Scheduler internal or Workload Manager (WLM) service
| class promotion when the job runs late. Possible values are:
| No The job is not on the critical path.
| Critical Path Target
| The job is on the critical path, and must be
| managed by the Tivoli Workload Scheduler internal
| critical path prioritizing algorithms.
| WLM The job is on the critical path, and must be
| managed by Workload Manager (WLM). If you
| select this option, also supply the WLM Policy and
| Class.
| WLM Policy The WLM policy applied for WLM service class promotion when
| this job is late. Only applied if you select the WLM option for
| Critical Job. Possible values are:
| Blank No WLM policy is applied. This is the default
| value.

140 IBM Tivoli Workload Scheduler Job Scheduling Console: User’s Guide
 Creating a job stream for a z/OS engine

| Deadline The scheduler intervenes if the job runs beyond the

| deadline.
| Conditional The scheduler uses an algorithm to determine
| whether to apply the Deadline or the Latest start
| option.
| Long Duration
| The scheduler intervenes if the job takes longer
| than it should as compared to the statistics that it
| keeps.
| Latest start The scheduler intervenes immediately if the job
| starts after the latest start time.
| WLM Class The WLM class applied for WLM service class promotion when
| this job is late. Only applied if you select the WLM option for
| Critical Job.

Task page
Use the Task page to enter information about a program associated with the job.

The page consists of the following:

Task Name The name of the task associated with the job. Together with the
identifier you specified in the previous page, the task name labels
the job in the Graph view of the job stream editor. The maximum
length is 8 characters.
Form Number The printer form number that appears on the daily plan and ready
lists. For printer workstations with automatic reporting, it enables
the engine to identify the different print operations that belong to a
specific job. The maximum length is 8 characters.
Job Class A single letter from A-Z that matches the host job class.
Output Class A single letter from A-Z that matches the host output class.
Use Extended Information
The Extended task name is enabled.
Extended Task Name
A descriptive name for the job. The maximum length is 54
characters.
| Use Scheduling Environment
| The WorkLoad Manager scheduling environment task name is
| enabled.
| Scheduling Environment Name
| A descriptive name of the WorkLoad Manager scheduling
| environment associated with the job. The maximum length is 16
| characters.

| Options page
| Use the Options page to enter information about the options that apply to the job.

| The page consists of the following:

| Restartable Whether to restart the job if the related workstation becomes
| inactive. Possible values are:
| Yes The job can be restarted if the workstation becomes
| inactive and an alternate workstation has been
| specified.

Chapter 26. Creating job streams 141

 Creating a job stream for a z/OS engine

| No The job is not restarted if the workstation becomes

| inactive.
| Default The installation default action specified in the
| OPRESTARTDEFAULT keyword of the JTOPTS
| statement is used. This is selected by default.
| Reroutable Whether to make the job eligible to be rerouted if its workstation
| becomes inactive. This option applies to the job only when it is in
| ready (R) or waiting (W) state. Possible values are:
| Yes The job is reroutable.
| No The job is not reroutable.
| Default The installation default action specified in the
| OPREROUTDEFAULT keyword of the JTOPTS
| statement is used. This is selected by default.
| Restart and Cleanup
| Which data set and job restart actions must be performed if the job
| ends in error. This option is not available for fault-tolerant
| workstations. Possible values are:
| None No cleanup and restart actions are performed. This
| is the default.
| Immediate Data set cleanup is performed immediately if the
| job ends in error. This option is not linked to a
| restart, which must be initiated separately.
| Automatic A data set cleanup is inserted automatically as the
| first step to be performed during the rerun of the
| failed job. This is the preferred method of running
| restart and cleanup.
| Manual Restart and cleanup actions are initiated manually
| from the Modify Current Plan ISPF panel.
| Restart and CleanUp: Expanded JCL
| The JCL used for step-level restarts and job reruns is the JCL image
| captured from the JESJCL sysout data set.
| Restart and CleanUp: Use Sysout
| The sysout data sets are used for job restarts.
| Feedback Options
| The scheduler automatically monitors the actual durations of jobs.
| It can use these durations to modify the estimates in the
| application description (AD) database. Possible values are:
| Smoothing factor
| A number from 0 to 999 that determines how much
| a measured duration changes existing values in the
| AD database. If a measured duration is outside the
| limit set by Limit for feedback, the smoothing
| factor is not applied and the AD database is not
| updated.
| Limit for feedback
| A number from 100 to 999 to set the limit within
| which measured values are regarded as acceptable.
| A measured value outside the limit is ignored, no
| smoothing factor is applied, and the AD database
| is not updated.

142 IBM Tivoli Workload Scheduler Job Scheduling Console: User’s Guide
 Creating a job stream for a z/OS engine

| Values entered in these fields override the default values in the

| JTOPTS options.

Time Restrictions page

Use the Time Restrictions page to specify the period of time that the job is
allowed to run and the amount of time the job requires.

The page consists of the following:

Start The time at which the job can start. Possible values are:
No Restrictions
The job runs as soon as all dependencies are met.
No time restrictions can result in more efficient
processing for certain jobs when extending a plan.

Note: This choice is not valid if you selected

Cancel if Late in the “General page” on
page 139.
| Follow Job Stream Rules
| The earliest time the job can start is when the job
| stream starts. This is the default. This option is
| ignored if you clear No Restrictions.
Specify Earliest Start Time
The time before which the job does not start.
Possible values are:
At Type a time according to your
locale settings. For example type
12:00 if you do not want the job to
start before noon.
Delay for days
Type a number of days to defer the
start time. For example if you type
3 the job starts three days after the
time you specify in At.
Deadline The latest time that the job can end. Select Specify to enable the
time fields. Possible values are:
At Type a time according to your locale settings. For
example type 12:00 if you want the job to end
before noon.
Delay for days
Type a number of days to defer the deadline. For
example if you type 3 the job must end three days
after the time you specify in At.
| Duration How long the job is expected to run, in hours, minutes, and
| seconds. The maximum is 99:59:01.

Resources page
Use the Resources page to define the parallel servers and the logical and
workstation resources that the job uses.

The page gives you access to two types of resources, as follows:

Target Resources
Set the quantity of resources that the workstation needs to run the
job. You cannot change the target resources listed, only the
quantity of them required.

Chapter 26. Creating job streams 143

 Creating a job stream for a z/OS engine

To set the quantity of target resources, perform the following steps:

| 1. If Logical Resources is shown, click its pull-down icon and
| select Target Resources.
2. Double-click each cell in the Quantity column to edit the
amount of resources (Resource 1 and Resource 2) needed by the
job.
Logical Resources
Set the logical resources, such as printers, tapes, or disk space that
are needed to run the job. You can add and remove logical
resources, as follows:
Resource
For target resources this is an information field that lists
the target resources. The Parallel Servers target resource
represents the number of processes that can be run
concurrently by the workstation. For logical resources this
is an alphanumeric name for the resource. Click ... (find) to
search for and select a resource. The maximum length is 44
characters.
Quantity
The quantity of the resource needed to run the job.
Access Type
For logical resources, the type of access for the resource.
Possible values are:
Shared Other jobs use the resource.
Exclusive Only the current job uses the resource.
Keep on Error
For logical resources, the action to take on the resource if
the job ends in error. Possible values are:
Yes The resource is reserved for the job when
an error occurs.
No The resource is released from the job when
an error occurs.
Default The default option specified for the
ONERROR keyword in the RESOPTS
statement is used.
| Available on complete
| The action to take when the job finishes successfully
| (complete status). Possible values are:
| Available Switch the global availability status of the
| resource to yes when a job that uses this
| resource completes successfully.
| Unavailable Switch the global availability status of the
| resource to no when a job that uses this
| resource completes successfully.
| Automatically reset
| Switch the global availability status of the
| resource to blank when a job that uses this
| resource completes successfully.

144 IBM Tivoli Workload Scheduler Job Scheduling Console: User’s Guide
 Creating a job stream for a z/OS engine

| Assume system default

| Switch the global availability status and
| quantity of the resource to the default
| value when a job that uses this resource
| completes successfully. The system will
| check for the following, in order:
| 1. If the Default: Is Available field (see
| below) has been set for the resource, it
| makes the resource available, using the
| Default: Quantity value
| 2. If Default: Is Available is not set, the
| system uses the value in the
| ONCOMPLETE keyword of the
| RESOPTS statement to determine the
| availability status.
To set logical resources, perform the following steps:
| 1. If Target Resources is shown, click its pull-down icon and
| select Logical Resources.

2. Click the to add a row to the table.

3. Type the name of the resource or click ... (find) to search and
select a resource.

| Automation page
| Use the Automation page for jobs that are to be run on Tivoli System Automation.
| These jobs must be defined on workstations with the automatic attribute set.

| The page consists of the following:

| Command Text
| The text string of the command to be run by Tivoli System
| Automation for z/OS. The string can contain Tivoli Workload
| Scheduler variables; before the operations are passed to Tivoli
| System Automation for z/OS, Tivoli Workload Scheduler performs
| the variable substitution processing. If any error occurs during this
| phase the job state is set to E with error code OJCV.
| Completion Info
| A string (maximum 64 characters) containing one or more of the
| following parameters, separated by a comma.
| Maximum wait time
| The maximum wait time (optional). Specify the
| longest interval of time that the command is
| expected to take to complete under normal
| operating conditions, plus a small margin to cover
| items like minor delays and heavy network traffic.
| If this value is specified, and the command does
| not complete within the indicated time interval,
| Tivoli System Automation for z/OS returns an
| error to Tivoli Workload Scheduler.

| Note: In the case of an INGREQ command, the

| command is considered complete when the
| specified resource has reached the requested
| state or is already in the requested state. If

Chapter 26. Creating job streams 145

 Creating a job stream for a z/OS engine

| more than one resource is specified in the

| INGREQ command, all resources must be in
| the requested state before the command is
| considered complete.

| Various time formats are accepted. See the Tivoli

| System Automation for z/OS documentation for
| details.
| Maximum return code accepted as OK
| The highest return code value from Tivoli System
| Automation for z/OS that Tivoli Workload
| Scheduler must treat as successful (optional). The
| default is 0.
| Completion checking routine
| The name of your completion checking routine
| (optional).
| If this value is specified, the completion checking
| routine is responsible for ensuring that the
| command achieved the expected results before
| posting the operation complete. This allows you to
| perform commands that are independent of a
| Tivoli System Automation for z/OS controlled
| resource, for example a VTAM® major node. In this
| case, the command could be the activation of the
| VTAM major node, while the checking routine
| could “ping” the target node before posting the
| OPC operation complete by means of the
| OPCAPOST command. If Maximum wait time is
| also supplied, it can be passed to the checking
| routine, allowing the checking routine to return an
| error if the command does achieve the expected
| result within the indicated time.
| The full syntax of the Completion Info string is as follows:
| [maximum_wait_time],
| [maximum_return_code],
| [completion_checking_routine]

| However, note that trailing commas must not be supplied. For

| example, to specify just the first two parameters, the field might
| look like this:
| 2:30,3

| To specify just the third parameter, the field might look like this:
| ,,CHKEND

| To not supply any of the parameters, leave the whole Completion

| Info field blank.
| Automated Function
| Specify the automated function (optional). When specified, the
| command is run on the NetView task associated with the indicated
| automated function in Tivoli System Automation for z/OS. You can
| use this parameter to serialize the commands. If this parameter is
| not specified, the command is run by any of the locally available
| NetView tasks.

146 IBM Tivoli Workload Scheduler Job Scheduling Console: User’s Guide
 Creating a job stream for a z/OS engine

| Security Element
| A token used for security tracking of the operation in the Tivoli
| System Automation for z/OS AOFEXC20 exit routine (optional).
| Use it as an alternative to, or in conjunction with the job name.

Creating distributed job streams

The Properties - Job Stream panel displays.

The panel consists of the following:

v
v “Comments page” on page 149
v “Dependency Resolution page” on page 149
v “Time Restrictions page” on page 150
v “Resources page” on page 151
v “Prompts page” on page 152
v “Files page” on page 152

| After you complete the pages described below, you can perform any of the actions
| described in Chapter 37, “Managing distributed job streams,” on page 219 by
| clicking the icon relevant to the type of job you are adding. Possible icons are:
|

|
| Add a job definition to the job stream you are working on.

Chapter 26. Creating job streams 147

 Creating distributed job streams

|
| Add multiple job definitions to the job stream you are working on.
|

|
| Add an internetwork dependency to the job stream you are
| working on.
|

|
| Add a dependency on a job that is in a job stream other than the
| one you are working on.
|

|
| Add a dependency on a job stream other than the one you are
| working on.
|

|
| Add a link between the following objects:
| v Job definitions in the job stream
| v External job stream and job definitions
| v External job and job definitions
| v Internetwork dependency and job definitions

| General page
| Use the General page to enter general information for the job stream.

| The page consists of the following:

| Name The name of the job stream. The name must start with a letter, and
| can contain alphanumeric characters, underscores, and dashes.
| Maximum length is 16 characters.
| Workstation Name
| The name of the workstation or workstation class on which the job
| stream is launched. If you specify a workstation class, it must
| match the workstation class of any jobs, resources, or file
| dependencies used in the job stream.
Valid from The date when the job stream first becomes active.
Valid to The date from when the job stream is no longer active.
Description A description of the job stream.
Time Zone The time zone in which you specify time restrictions. This list is
available only if time zone support is enabled. For information
about enabling the time zone, refer to IBM Tivoli Workload
Scheduler: Planning and Installation Guide.
Priority The priority of the job stream. Type a priority value or click:

148 IBM Tivoli Workload Scheduler Job Scheduling Console: User’s Guide
 Creating distributed job streams

Hold Sets the priority to 0.

High Sets the priority to 100.
Go Sets the priority to 101.

Possible priority values are 0 through 101, where 101 is the highest
priority. A priority value of zero prevents the job stream from
launching. High and Go jobs are launched as soon as their
dependencies are satisfied, overriding the workstation job limit, but
not overriding the job stream job limit or the workstation job fence.
| Limit The number of jobs that can be running at the same time in the job
| stream. Possible values are 0 through 1024. If you specify a job
| limit of 0, no jobs are launched in the job stream.
Is Draft The job stream is still in the development phase and is not
included in the plan.
Carry Forward
The job stream is eligible to be carried forward to the next day
production plan if it is not completed before the end of the current
production day. Job streams that are carried forward retain the
carryforward option and are carried forward again. You can
control the number of days a job stream is carried forward by
specifying a deadline time (UNTIL keyword) plus x number of
days.
Monitored Job Stream
The job stream is monitored by Tivoli Business Systems Manager
(TBSM) when it runs.
Use Default Use the default free days calendar (usually named Holidays). The
free days calendar is used during the definition of the run cycles
for the job stream. It is associated with the free day rule, where
you tell Tivoli Workload Scheduler how to handle a job stream if
the schedule falls on a freeday.
| Specify Calendar
| Specify a freeday calendar other than the default calendar. When
| you select Specify Calendar, the Calendar Name is obligatory.
| Calendar Name
| The name of the freeday calendar. You can use ... (find) to search
| for the calendar.
Saturday Whether Saturday is considered as a free day.
Sunday Whether Sunday is considered as a free day.

Comments page
Use the Comments page to add any additional comments about the job stream.

Dependency Resolution page

| Use the Dependency Resolution page to specify the defaults for resolving follows
| dependencies when the Use Defaults option is selected during follows dependency
| creation for job stream and its jobs.

| The page consists of the following:

Chapter 26. Creating job streams 149

 Creating distributed job streams

| Closest Preceding
| The follows dependencies used for resolution are the closest that
| preceded the job stream.
| Same Scheduled Date
| The dependencies used for resolution are those on the same
| scheduled date as the current job stream.
| Within a Relative Interval
| The dependencies used for resolution are those within the relative
| interval you specify in the Relative Interval Selection section.
| Within an Absolute Interval
| The dependencies used for resolution are those within the absolute
| interval you specify in the Absolute Interval Selection section.
| Relative Interval Selection
| This field is enabled when you select Within a Relative Interval.
| Type the From and To range of the relative interval. Select whether
| the interval starts before or after the job stream start time. The
| range is from 0 to 167 hours and 59 minutes.
| Absolute Interval Selection
| This field is enabled when you select Within an Absolute Interval.
| Type the At time and the number of days (For Days) for the
| absolute interval. Select whether the interval starts before or after
| the job stream. To select Before start time the For Days value must
| be greater than 0.

Time Restrictions page

Use the Time Restrictions page to specify the time constraints for the job stream.

The page consists of the following:

Time Zone The time zone of the job stream time restrictions. This list is
available only if time zone support is enabled. For information
about enabling the time zone, refer to IBM Tivoli Workload
Scheduler: Planning and Installation Guide.
Start The time before which the job stream must not start.
Specify Time Select Specify Time when you want to set a start
time for the job stream.
| Time Dependent
| The job stream has a time dependency. When you
| do not specify that the job stream is time
| dependent, the Start time indicates the time when
| the job stream is entered into the plan. This check
| is enabled only if you select Specify Time.
At The time before which the job stream must not
start. The time format is according to your locale.
Delay for Days
The number of days to offset the start time from
the day the job stream is selected for inclusion in
the production plan.
Latest Start Time
The latest time at which the job stream is allowed to start.

150 IBM Tivoli Workload Scheduler Job Scheduling Console: User’s Guide
 Creating distributed job streams

Specify Time
Select Specify Time when you want to set a latest start
time for the job stream.
| At The latest possible start time at which the job stream is
| allowed to start.
Delay for Days
The number of days to offset the latest start time from the
day the job stream is selected for inclusion in the
production plan.
Action The action to be performed in case the job stream does not start
and the Latest Start Time expires.
Suppress To specify that the job stream does not start, even
if the error condition that prevented it from
starting is corrected, and dependencies are not
released. Suppress is the default.
| Continue To specify that the job stream starts when all
| necessary conditions are met and a notification
| message is written to the log when the until time
| elapses.
Cancel To specify that the job stream is cancelled and
dependencies are released.
Termination Deadline
The time by which the job stream must complete. Job streams that
have not yet started or that are still running when the deadline
time expires, are considered late in the plan. A message is written
in the job log. The termination deadline does not prevent job
streams from starting.
Specify Time Select Specify Time when you want to set a
deadline time for the job stream.
| At The time within which a job stream should
| complete.
Delay for Days
The number of days to offset the deadline time
from the day the job stream is selected for
inclusion in the production plan.

Resources page
To add a resource dependency for the job stream, perform the following steps:

1. Click .
2. Click in Resource cell and click ... (find) to search for and select a resource.
3. Double-click in the Workstations cell to type the name of the workstation
where the resource resides.
4. Double-click in the Quantity column and enter the number of resource units
required by the job stream. The default is one. Resources can be defined with
up to 1024 units, but they can only be allocated in increments of 32. For
example, to allocate 1024 units of a resource to a job stream or job you would
need to create 32 entries for the resource with 32 units each. The number of
jobs and schedules using a resource at the same time cannot exceed 32.

To remove a resource dependency for the job stream, select the resource row in the

list and click .

Chapter 26. Creating job streams 151

 Creating distributed job streams

| Prompts page
| Use the Prompts page to set ad hoc or predefined prompt dependencies for the job
| stream.

| To add an ad hoc prompt for the job stream, perform the following steps:
| 1. From the drop-down list, select Ad Hoc Prompt.

| 2. Click .
| 3. Double-click in the Text cell and type the text of the prompt. The default
| behavior of a prompt is to display a message and wait for a reply. Based on the
| character preceding the text, the prompt can behave differently:
| v If the text begins with a colon (:), the prompt displays, but no reply is
| required to continue processing.
| v If the text begins with an exclamation mark (!), the prompt displays, but it is
| not recorded in the log file.
| Refer to the IBM Tivoli Workload Scheduler: Reference Manual for a detailed
| explanation on how to specify the text of a prompt.
| You can include one or more scheduler parameters as part or all of the text
| string. To use a parameter, place its name between carets (^) .

| To add a predefined prompt for the job stream, perform the following steps:
| 1. From the drop-down list, select Predefined Prompt.

| 2. Click .
| 3. Type the name of the prompt in the Name cell or click ... (find) to search for
| and select the prompt. The Text cell displays the text of the predefined prompt
| message. This field is read-only.

| To remove a prompt dependency for the job stream, select the prompt row in the

| list and click .

Files page
To add a file dependency for the job stream, perform the following steps:

1. Click .
| 2. Double-click in the Filename cell and click ... (find) to search for and select a
| file. You can search for a file only if it resides on the workstation where the Job
| Scheduling Console resides.
3. Double-click in the Workstation cell and click ... (find) to search for and select a
workstation.
4. Double-click in the Qualifiers cell and enter the test conditions for the file
dependency. On UNIX, the valid qualifiers are the same as UNIX test
command conditions. For more information, refer to your UNIX system
documentation.
On Windows , only the following qualifiers are valid:
-d %p
True if the file exists and is a directory.
-e %p
True if the file exists.
-f %p
True if the file exists and is a regular file.

152 IBM Tivoli Workload Scheduler Job Scheduling Console: User’s Guide
 Creating distributed job streams

-r %p
True if the file exists and is readable.
-s %p
True if the file exists and its size is greater than zero.
-w %p
True if the file exists and is available for editing.
Notes:
a. On both UNIX and Windows , the expression %p inserts the file name.
b. Entering notempty is the same as entering -s %p. If no qualifier is specified,
the default is -f %p.

To remove a file dependency for the job stream, select the file row in the list and

click .

Chapter 26. Creating job streams 153

Creating distributed job streams

154 IBM Tivoli Workload Scheduler Job Scheduling Console: User’s Guide
 Chapter 27. Creating forecast and trial plans
This chapter describes how you create forecast and trial plans for the distributed
environment.

To create a plan, perform the following steps:

1. In the Actions list pane, click Generate New Plan.
2. Select the engine.
The Generate New Plan panel displays.

The panel consists of the following:

Plan Type Select the type of plan to generate. Possible values are:
v Trial
v Forecast
See “Plan” on page 31.
| File Name Type the name of the file that contains the type of plan you
| selected.
| Start Time When the plan is a forecast plan, select the date and the time
| when the plan starts.
Duration Select the duration of the plan in Hours and Minutes. Select
the time zone of the plan from the drop-down.

© Copyright IBM Corp. 1991, 2006 155

Creating trial and forecast plans

Switch to the generated plan

Select Switch to the generated plan when you want the
generated plan to be set as the alternate plan immediately.

156 IBM Tivoli Workload Scheduler Job Scheduling Console: User’s Guide
Chapter 28. Creating objects using Create Another
This chapter describes how to create objects using the Create Another option.

To create a new object in the database using a copy, perform the following steps:
1. Run a list that contains the object you want to copy. See Chapter 33, “Working
with lists,” on page 185 for more information.
2. In the list results, right-click the object you want to copy and select Create
another.
This displays a copy of the object in the relevant properties window.
3. In Name, change the name to the name of the new object.
4. Change the other properties as needed to define the new object.

Note: When you create job streams using Create Another, you can create another
job stream with a new name, or you can create another version of the
existing job stream maintaining the name. When you create a new job
stream with a new name you cannot then rename the job stream to the
original name.

© Copyright IBM Corp. 1991, 2006 157

Creating using Create Another

158 IBM Tivoli Workload Scheduler Job Scheduling Console: User’s Guide
Part 5. Creating and using lists

© Copyright IBM Corp. 1991, 2006 159

160 IBM Tivoli Workload Scheduler Job Scheduling Console: User’s Guide
 Chapter 29. Creating database lists
This chapter describes how you create database lists. It is divided into the
following sections:
v “Creating job stream lists in the database” on page 163
v “Creating job definition lists in the database” on page 167
v “Creating workstation lists in the database” on page 165
v “Creating resource lists in the database” on page 166
v “Creating workstation class lists in the database” on page 168
v “Creating prompt lists in the database” on page 168
v “Creating parameter lists in the database” on page 168
v “Creating Windows user lists in the database” on page 169
v “Creating domain lists in the database” on page 169
v “Creating calendar lists in the database” on page 170
Notes:
| 1. Use the Properties - Engine panel to modify the default properties for lists, for
| example, the rate interval to refresh the content of your list. See Chapter 34,
| “Managing engines,” on page 191.
2. Filters for the database lists are case sensitive.

To create a database list, perform the following steps:

1. Right-click an engine or a group of lists in the Work with engines pane.
2. Select the type of list you want to create. Possible values are:
v Job Stream
v Job
v Workstation
v Resource
v Workstation Class
v Prompt
v Parameter
v Windows User
v Domain
v Calendar
The properties panel of the list type you selected displays.

Figure 9 on page 162 illustrates the properties panel for a distributed job stream
list.

© Copyright IBM Corp. 1991, 2006 161

Creating database lists

Figure 9. Example Properties panel for distributed engines

Figure 10 on page 163 illustrates the properties panel for a z/OS job stream list.

162 IBM Tivoli Workload Scheduler Job Scheduling Console: User’s Guide
 Creating job stream lists

Figure 10. Example Properties panel for z/OS job stream list

Creating job stream lists in the database

You can create job stream lists for both the distributed and the z/OS environments.

The Properties - Job Stream List panel depends on whether you are:
v “Creating a z/OS job stream list”
v “Creating a distributed job stream list” on page 164

Creating a z/OS job stream list

The panel consists of the following:
Name A name for the list. The maximum length is 80 characters.
Periodic Refresh
An automatic refresh interval in seconds.
Period (seconds)
The frequency of the refresh rate in seconds. The minimum value
is 30 seconds.

Chapter 29. Creating database lists 163

 Creating a z/OS job stream list

Apply Defaults
The defaults specified in the engine properties panel are applied.
Job Stream Filter for job streams with this name.
Task Name Filter job streams where this task or JCL is used.
Extended Task Name
Filter the job streams containing jobs that use a specific extended
task name.
Owner Filter for job streams that belong to this owner.
Job Stream Template
Filter for job streams that are part of this template.
Authority Group
Filter for job streams that use this authority group for RACF
authority checking.
Calendar Filter for job streams that use this calendar.
Workstation Filter for job streams containing jobs that run on this workstation.
| Scheduling Environment Name
| Filter for job streams that contain jobs associated with this
| WorkLoad Manager scheduling environment. The maximum length
| is 16 characters.
Is a template Filter for job streams that are templates.
Exclude template
Filter for job streams that are not templates.
Priority Filter for job streams that have a priority in the range of From and
To.
Dates Filter for job streams that have a date in the range of From and To.
Status of Job Stream
Filter for job streams according to whether they are active or
inactive.
Contains Monitored Job
Filter for job streams that contain a monitored or umonitored job.

Creating a distributed job stream list

The panel consists of the following:
Name A name for the list. The maximum length is 80 characters.
Periodic Refresh
An automatic refresh interval in seconds.
Period (seconds)
The frequency of the refresh rate in seconds. The minimum value
is 30 seconds.
Apply Defaults
The defaults specified in the engine properties panel are applied.
Job Stream Name
Filter for job streams with this name.
Workstation Name
Filter for job streams related to the workstations you specify.

164 IBM Tivoli Workload Scheduler Job Scheduling Console: User’s Guide
 Creating a distributed job stream list

Job Stream Status

Filter for job streams according to whether they are active.
Validity Range
Filter for job streams that have a validity in the range of From
Date and To Date.

Use the Column Definition page to define the columns displayed in the list.

For a definition of the columns, refer to the Job Scheduling Console online help.

Creating workstation lists in the database

You can create workstation lists for both the distributed and the z/OS
environments.

The Properties - Database Workstation List panel depends on whether you are:
v “Creating a z/OS workstation list”
v “Creating a distributed workstation list”

Creating a z/OS workstation list

The panel consists of the following:
Name A name for the list. The maximum length is 80 characters.
Periodic Refresh
An automatic refresh interval in seconds.
Period (seconds)
The frequency of the refresh rate in seconds. The minimum value
is 30 seconds.
Apply Defaults
The defaults specified in the engine properties panel are applied.
Workstation Filter for workstations with the name you specify.
Reporting Attributes
Filter for workstations according to their reporting attributes. You
can select any number of reporting attributes.
Workstation Types
Filter for workstations according to their workstation type. You can
select any number of workstation types.
Is Fault-tolerant
Filter for workstations according to whether they are fault-tolerant.
| Is For Automation
| Filter for workstations according to whether they are used for the
| integration with Tivoli System Automation for z/OS.
| Is Wait Filter for Wait workstations.

Creating a distributed workstation list

The panel consists of the following:
Name A name for the list. The maximum length is 80 characters..
Periodic Refresh
An automatic refresh interval in seconds.

Chapter 29. Creating database lists 165

Creating a distributed workstation list

Period (seconds)
The frequency of the refresh rate in seconds. The minimum value
is 30 seconds.
Apply Defaults
The defaults specified in the engine properties panel are applied.
Workstation Name
Filter for workstations with the name you specify.
Workstation Type
Filter workstations according to the workstation type.
Domain Name
Filter for workstations that belong to this domain.
Host Workstation Name
Filter for the host workstation of extended agents.

Use the Column Definition page to define the columns displayed in the list.

For a definition of the columns, refer to the Job Scheduling Console online help.

Creating resource lists in the database

You can create resource lists for both the distributed and the z/OS environments.

The Properties - Database Resource List panel depends on the type of engine:
v “Creating a z/OS resource list”
v “Creating a distributed resource list” on page 167

Creating a z/OS resource list

The panel consists of the following:
Name A name for the list. The maximum length is 80 characters.
Periodic Refresh
An automatic refresh interval in seconds.
Period (seconds)
The frequency of the refresh rate in seconds. The minimum value
is 30 seconds.
Apply Defaults
The defaults specified in the engine properties panel are applied.
Resource Filter for resources according to the criteria you select in Treat
Input As.
Treat Input As
How the string that you specify in Resource is interpreted.
Possible values are:
v Wildcard
v Exact match
v Prefix
v Suffix
Group ID Filter for all resources that belong to this group.
Hiperbatch Whether to list or exclude resources that can work with
Hiperbatch.

166 IBM Tivoli Workload Scheduler Job Scheduling Console: User’s Guide
 Creating a distributed resource list

Creating a distributed resource list

The panel consists of the following:
Name A name for the list. The maximum length is 80 characters..
Periodic Refresh
An automatic refresh interval in seconds.
Period (seconds)
The frequency of the refresh rate in seconds. The minimum value is 30
seconds.
Apply Defaults
The defaults specified in the engine properties panel are applied.
Resource Name
Filter for all the resources with this name.
Workstation Name
Filter for all workstations with this name.

Use the Column Definition page to define the columns displayed in the list.

For a definition of the columns, refer to the Job Scheduling Console online help.

Creating job definition lists in the database

You can create a list of job definitions for the distributed environment only.

The Properties - Job List panel displays.

The panel consists of the following:

Name A name for the list. The maximum length is 80 characters.
Periodic Refresh
An automatic refresh interval in seconds.
Period (seconds)
The frequency of the refresh rate in seconds. The minimum value is 30
seconds.
Apply Defaults
The defaults specified in the engine properties panel are applied.
Job Name
Filter for all job definitions with this name.
Workstation Name
Filter for all job definitions related to workstations of this name.

Use the Column Definition page to define the columns displayed in the list.

For a definition of the columns, refer to the Job Scheduling Console online help.

Chapter 29. Creating database lists 167

Creating distributed workstation class lists

Creating workstation class lists in the database

You can create a list of workstation classes for the distributed environment only.

The Properties - Workstation Class List panel displays.

The panel consists of the following:

Name A name for the list. The maximum length is 80 characters.
Periodic Refresh
An automatic refresh interval in seconds.
Period (seconds)
The frequency of the refresh rate in seconds. The minimum value is 30
seconds.
Apply Defaults
The defaults specified in the engine properties panel are applied.
Workstation Class Name
Filter for all workstation classes with this name.

Use the Column Definition page to define the columns displayed in the list.

For a definition of the columns, refer to the Job Scheduling Console online help.

Creating prompt lists in the database

You can create a list of prompts for the distributed environment only.

The Properties - Prompt List panel displays.

The panel consists of the following:

Name A name for the list. The maximum length is 80 characters.
Periodic Refresh
An automatic refresh interval in seconds.
Period (seconds)
The frequency of the refresh rate in seconds. The minimum value is 30
seconds.
Apply Defaults
The defaults specified in the engine properties panel are applied.
Prompt Name
Filter for prompts with this name.

Use the Column Definition page to define the columns displayed in the list.

For a definition of the columns, refer to the Job Scheduling Console online help.

Creating parameter lists in the database

You can create a list of parameters for the distributed environment only.

The Properties - Parameter List panel displays.

The panel consists of the following:

168 IBM Tivoli Workload Scheduler Job Scheduling Console: User’s Guide
 Creating distributed parameter lists

Name A name for the list. The maximum length is 80 characters.

Periodic Refresh
An automatic refresh interval in seconds.
Period (seconds)
The frequency of the refresh rate in seconds. The minimum value is 30
seconds.
Apply Defaults
The defaults specified in the engine properties panel are applied.
Parameter Name
Filter for parameters with this name.

Use the Column Definition page to define the columns displayed in the list.

For a definition of the columns, refer to the Job Scheduling Console online help.

Creating Windows user lists in the database

You can create a list of Windows users for the distributed environment only.

The Properties - Windows User List panel displays.

The panel consists of the following:

Name A name for the list. The maximum length is 80 characters.
Periodic Refresh
An automatic refresh interval in seconds.
Period (seconds)
The frequency of the refresh rate in seconds. The minimum value is 30
seconds.
Apply Defaults
The defaults specified in the engine properties panel are applied.
Windows Domain\User Name
Filter for users with this user name. You can use fully qualified domain
names.
Workstation
Filter for the workstation of the Windows user.

Use the Column Definition page to define the columns displayed in the list.

For a definition of the columns, refer to the Job Scheduling Console online help.

Creating domain lists in the database

You can create a list of domains for the distributed environment only.

The Properties - Domain List panel displays.

The panel consists of the following:

Name A name for the list. The maximum length is 80 characters.
Periodic Refresh
An automatic refresh interval in seconds.

Chapter 29. Creating database lists 169

Creating distributed domain lists

Period (seconds)
The frequency of the refresh rate in seconds. The minimum value is 30
seconds.
Apply Defaults
The defaults specified in the engine properties panel are applied.
Domain Name
Filter for domains with this name.
Parent Domain
Filter for the domains that belong to this parent domain.

Use the Column Definition page to define the columns displayed in the list.

For a definition of the columns, refer to the Job Scheduling Console online help.

Creating calendar lists in the database

You can create a list of calendars for the distributed environment only.

The Properties - Calendar List panel displays.

The panel consists of the following:

Name A name for the list. The maximum length is 80 characters.
Periodic Refresh
An automatic refresh interval in seconds.
Period (seconds)
The frequency of the refresh rate in seconds. The minimum value is 30
seconds.
Apply Defaults
The defaults specified in the engine properties panel are applied.
Calendar Name
Filter for calendars with this name.

Use the Column Definition page to define the columns displayed in the list.

For a definition of the columns, refer to the Job Scheduling Console online help.

170 IBM Tivoli Workload Scheduler Job Scheduling Console: User’s Guide
Chapter 30. Creating plan lists
This chapter describes how you create plan lists. It is divided into the following
sections:
v “Creating job stream instance lists in the plan” on page 171
v “Creating job instance lists in the plan” on page 174
v “Creating workstation status lists in the plan” on page 178
v “Creating resource status lists in the plan” on page 178
v “Creating file status lists in the plan” on page 178
v “Creating prompt status lists in the plan” on page 179
v “Creating domain status lists in the plan” on page 179

To create a plan list right-click an engine or group of lists, choose Create Plan List
in the pop-up menu and select the list type you want to create.
Notes:
1. Use the Properties - Engine panel to modify the properties of a list. See
Chapter 34, “Managing engines,” on page 191.
2. Filters for plan lists are not case sensitive.

Creating job stream instance lists in the plan

You can create job stream instance lists for both the distributed and the z/OS
environments.

The Properties - Job Stream Instance List panel depends on whether you are:
v “Creating z/OS job stream instance lists in the plan”
v “Creating distributed job stream instance lists in the plan” on page 173

Creating z/OS job stream instance lists in the plan

The Properties - Job Stream Instance List panel displays.

The panel consists of the following:

Name A name for the list. The maximum length is 80 characters.
Periodic Refresh
An automatic refresh interval in seconds.
Period (seconds)
The frequency of the refresh rate in seconds. The minimum value is 30
seconds.
Apply Defaults
The defaults specified in the engine properties panel are applied.
Job Stream
Filter for job stream instances with this name.
Job Stream Template
Filter for job stream instances that are part of this template.

© Copyright IBM Corp. 1991, 2006 171

 Creating job stream instance lists

Occurrence Token
Filter for job stream instance that is identified by this occurrence token in
the plan. The token is a unique 16 character hexadecimal string assigned to
the job stream by the scheduler. Wildcards and filter on first characters are
not allowed for this field.
Owner
Filter for job stream instances that belong to this owner.
Authority Group
Filter for job stream instances that use this authority group for RACF
authority checking.
Extended Task Name
Filter for job stream instances containing jobs that use a specific extended
task name.
| Scheduling Environment Name
| Filter for job stream instances that contain jobs associated with this
| WorkLoad Manager scheduling environment.
Dates Filter for job stream instances scheduled to run in the range you specify in
Date and Time fields.
Priority
Filter for job stream instances that have a priority within the range you
specify in the From and To fields.
Manually Added
Filter for job stream instances according to whether they were manually
added to the plan.
Rerun Requested
Filter for job stream instances according to whether a rerun of the job
stream was requested.
Contains Monitored Job
Filter for job stream instances according to whether they contain a
monitored job.
| Waiting for Scheduling Environment
| Filter for job stream instances according to whether the associated jobs are
| waiting for a WorkLoad Manager scheduling environment.
| Running on Wait Workstation
| Filter for job stream instances according to whether the associated jobs are
| running on a Wait workstation.
Most Critical Job
Filter for job stream instances according to the start time of the most
critical job in Hours and Minutes.
Status Filter for job stream instances according to their status codes.
For a definition of the states see Appendix D, “Status description and
mapping,” on page 425.
Internal Status
Filter for job stream instances their internal status codes.
For a definition of the states see Appendix D, “Status description and
mapping,” on page 425.

172 IBM Tivoli Workload Scheduler Job Scheduling Console: User’s Guide
 Creating job stream instance lists

Note: Status and internal status are mutually exclusive. However, they are both
displayed among the properties of job stream instances. Internal status refers
to the status code assigned by the specific job scheduling engine. It provides
more detail than the broader status code assigned by the Job Scheduling
Console.

Use the Column Definition page to define the columns displayed in the list.

For a definition of the columns, refer to the Job Scheduling Console online help.

Creating distributed job stream instance lists in the plan

The Properties - Job Stream Instance List panel displays.

The panel consists of the following:

v “General page”
v “Time Data page” on page 174
v “Dependencies page” on page 174

General page
The page consists of the following:
Name A name for the list. The maximum length is 80 characters.
Periodic Refresh
An automatic refresh interval in seconds.
Period (seconds)
The frequency of the refresh rate in seconds. The minimum value is 30
seconds.
Apply Defaults
The defaults specified in the engine properties panel are applied.
Job Stream Name
Filter for job stream instances with this name.
Workstation Name
Filter for workstations with this name.
Status Filter for job stream instances according to their status codes.
For a definition of the states see Appendix D, “Status description and
mapping,” on page 425.
Internal Status
Filter for job stream instances according to their internal status codes.
For a definition of the states see Appendix D, “Status description and
mapping,” on page 425.
Priority
Filter for job stream instances with a priority in the range of From to To.
Possible priority values are 0 through 101, where 101 is the highest priority.
Click Hold to select priority 0, High to select priority 100, or Go to select
priority 101.

Note: Status and internal status are mutually exclusive. However, they are both
displayed among the properties of job stream instances. Internal status refers

Chapter 30. Creating plan lists 173

Creating job stream instance lists

to the status code assigned by the specific job scheduling engine. It provides
more detail than the broader status code assigned by the Job Scheduling
Console.

Time Data page

The page consists of the following:
Actual Start Time Range
Filter for all job streams that start running within this time range.
Latest Start Time
Filter for all job streams that have a latest start time set within this time
range.
Finish Time Range
Filter for job streams that are set to finish within this time range.

Dependencies page
The page consists of the following:
Workstation Name
Filter for job stream instances with job, job stream, resource, and file
dependencies according to their associated workstation.
Job Stream
Filter for job stream instances with this job stream as a dependency.
Job Filter for job stream instances with this job as a dependency.
Name Filter for job stream instances with this resource as a dependency.
File Name
Filter for job stream instances with this file as a dependency.
Name Filter for job stream instances with this prompt as a dependency.
Prompt Number
The number of the prompt indicated in the Name field.

When you are creating lists, you can use the Column Definition page to define the
columns displayed in the list. The Column Definition page for a distributed job
stream instance list consists of three sections: Job Stream Table, Job Table and
Dependency.

You can choose the columns to display in each section of the list (job instance, job
stream instance, or dependency) selecting or clearing the corresponding check box.

For a definition of the columns, refer to the Job Scheduling Console online help.

Creating job instance lists in the plan

You can create job instance lists for both the distributed and the z/OS
environments.

The Properties - Job Instance List panel depends on whether you are:
v “Creating z/OS job instance lists in the plan” on page 175
v “Creating distributed job instance lists in the plan” on page 176

174 IBM Tivoli Workload Scheduler Job Scheduling Console: User’s Guide
 Creating job instance lists

Creating z/OS job instance lists in the plan

The Properties - Job Instance List panel displays.

The panel consists of the following:

Name A name for the list. The maximum length is 80 characters.
Periodic Refresh
An automatic refresh interval in seconds.
Period (seconds)
The frequency of the refresh rate in seconds. The minimum value is 30
seconds.
Apply Defaults
The defaults specified in the engine properties panel are applied.
Job Stream
Filter for job instances that are part of this job stream.
Job Identifier
Filter for job instances that have this identifier.
Task Name
Filter for job instances that are associated with this JCL task.
Extended Task Name
Filter for job instances that use this extended task name.
Workstation
Filter for job instances that run on this workstation.
Owner
Filter for job instances that belong to this owner.
Authority Group
Filter for job instances that use this authority group for RACF checking.
| Scheduling Environment Name
| Filter for job instances associated with the specified WorkLoad Manager
| scheduling environment.
Dates Filter for job instances that are scheduled to run in the From and To range
you specify.
Priority
Filter for job instances that have a priority in the range of From and To.
Contains Monitored Job
Filter for job instances according to whether they contain a monitored job.
Restart Option: CleanUp Type
Filter for job instances that have the cleanup and restart options that you
select.
Restart Option: CleanUp Status
Filter for job instances that have the cleanup state that you select.
Status Filter for job instances according to their status codes.
For a definition of the states see Appendix D, “Status description and
mapping,” on page 425.
Internal Status
Filter for job instances according to their internal status codes.

Chapter 30. Creating plan lists 175

 Creating job instance lists

For a definition of the states see Appendix D, “Status description and

mapping,” on page 425.
| Critical Job
| Filter for critical jobs, which are jobs that are eligible for Tivoli Workload
| Scheduler internal or Workload Manager (WLM) service class promotion
| when the job runs late. Possible values are:
| No Select jobs which are not marked as Critical jobs.
| Critical Path Select critical jobs which are managed by the Tivoli
| Workload Scheduler internal critical path prioritizing
| algorithms.
| WLM Select critical jobs which are managed by Workload
| Manager (WLM).
| Ignore Criteria
| Select jobs regardless of whether they are marked as
| critical.
WLM Policy
Filter for job instances that are defined as critical jobs and have the selected
WLM policy defined.
| Waiting for Scheduling Environment
| Filter for job instances waiting for a WorkLoad Manager scheduling
| environment.
| Running on Wait Workstation
| Filter for job instances running on a Wait workstation. Jobs started on wait
| workstations have the Status Details set to Running on a WAIT workstation
| to remind users that a delay in the defined sequence of jobs is occurring.

Note: Status and internal status are mutually exclusive. However, they are both
displayed among the properties of job stream instances. Internal status refers
to the status code assigned by the specific job scheduling engine. It provides
more detail than the broader status code assigned by the Job Scheduling
Console.

Use the Column Definition page to define the columns displayed in the list.

For a definition of the columns, refer to the Job Scheduling Console online help.

Creating distributed job instance lists in the plan

The Properties - Job Instance List panel displays.

The panel consists of the following:

v “General page”
v “Time Data page” on page 177
v “Dependencies page” on page 178

General page
The page consists of the following:
Name A name for the list. The maximum length is 80 characters.
Periodic Refresh
An automatic refresh interval in seconds.

176 IBM Tivoli Workload Scheduler Job Scheduling Console: User’s Guide
 Creating job instance lists

Period (seconds)
The frequency of the refresh rate in seconds. The minimum value is 30
seconds.
Apply Defaults
The defaults specified in the engine properties panel are applied.
Job Name
Filter for job instances with this job name.
Job Stream Name
Filter for job instances that are part of this job stream.
Workstation (Job Stream)
Filter for job instances for the job streams that run on this workstation.
Login Filter for job instances that are associated with the user with this login.
Status Filter for job instances according to their status codes.
For a definition of the states see Appendix D, “Status description and
mapping,” on page 425.
Internal Status
Filter for job instances according to their internal status codes.
For a definition of the states see Appendix D, “Status description and
mapping,” on page 425.
Always Show Rerun Instances
Filter for all job instances that were rerun regardless of the status you
specified.
Notes:
1. This option is significant only if you also specified a status for Status.
2. It makes no difference if the job status is the same as the rerun status.
Recovery Options
Filter for job instances with the recovery options you specify.
Priority
Filter for job instances with a priority in the range of From to To. Possible
priority values are 0 through 101, where 101 is the highest priority. Click
Hold to select priority 0, High to select priority 100, or Go to select
priority 101.

Note: Status and internal status are mutually exclusive. However, they are both
displayed among the properties of job instances. Internal status refers to the
status code assigned by the specific job scheduling engine. It provides more
detail than the broader status code assigned by the Job Scheduling Console.

Time Data page

The page consists of the following:
Actual Start Time Range
Filter for job instances according to their actual start time. When you use
this filter, specify both a From Date and a To Date.
Latest Start Time
Filter for job instances according to their specified latest start time. When
you use this filter, specify both a From Date and a To Date.

Chapter 30. Creating plan lists 177

Creating job instance lists

Finish Time Range

Filter for job instances according to when they finished. When you use this
filter, specify both a From Date and a To Date.

Dependencies page
The page consists of the following:
Job/Job Stream Dependency
Filter for job instances according to their job and job stream dependencies.
Resource Dependency
Filter for job instances according to their resource dependencies.
Prompt Dependency
Filter for job instances according to their prompt dependencies.

Use the Column Definition page to define the columns displayed in the list.

For a definition of the columns, refer to the Job Scheduling Console online help.

Creating workstation status lists in the plan

You can create workstation lists for both the distributed and the z/OS
environments.

The Properties - Plan Workstation Status List panel depends on whether you are
creating a z/OS or a distributed list.

“Creating workstation lists in the database” on page 165 defines the information
necessary to create the workstation list. The workstation list for distributed engines
in the plan has the following additional field:
Domain Name
Filter for workstations belonging to domains with this name.

Use the Column Definition page to define the columns displayed in the list.

For a definition of the columns, refer to the Job Scheduling Console online help.

Creating resource status lists in the plan

You can create resource status lists for both the distributed and the z/OS
environments.

The Properties - Plan Resource Status List panel depends on whether you are
creating a z/OS or distributed list.

“Creating resource lists in the database” on page 166 defines the information
necessary to create a resource status list.

Creating file status lists in the plan

You can create file status lists for distributed engines only.

The Properties - File Status List panel displays.

The panel consists of the following:

178 IBM Tivoli Workload Scheduler Job Scheduling Console: User’s Guide
 Creating distributed file status lists

Name A name for the list. The maximum length is 80 characters.

Periodic Refresh
An automatic refresh interval in seconds.
Period (seconds)
The frequency of the refresh rate in seconds. The minimum value is 30
seconds.
Apply Defaults
The defaults specified in the engine properties panel are applied.
Filename
Filter for file dependencies with this name.
Workstation Name
Specify the workstation where the file dependency resides.

Creating prompt status lists in the plan

You can create prompt status lists for distributed engines only.

The Properties - Prompt Status List panel displays.

The panel consists of the following:

Name A name for the list. The maximum length is 80 characters.
Periodic Refresh
An automatic refresh interval in seconds.
Period (seconds)
The frequency of the refresh rate in seconds. The minimum value is 30
seconds.
Apply Defaults
The defaults specified in the engine properties panel are applied.
Prompt Name
Filter for prompts with this name.
Status Filter for prompts according to their asked and answered states.

Creating domain status lists in the plan

You can create domain status lists for distributed engines only.

The Properties - Plan Domain Status List panel displays.

The panel consists of the following:

Name A name for the list. The maximum length is 80 characters.
Periodic Refresh
An automatic refresh interval in seconds.
Period (seconds)
The frequency of the refresh rate in seconds. The minimum value is 30
seconds.
Apply Defaults
The defaults specified in the engine properties panel are applied.

Chapter 30. Creating plan lists 179

Creating distributed domain status lists

Domain Name
Filter for domains with this name.

180 IBM Tivoli Workload Scheduler Job Scheduling Console: User’s Guide
Chapter 31. Creating a group of lists
You can use the Job Scheduling Console to organize your lists into groups. You can
organize your groups of lists by any criteria that help you to quickly display the
objects that you want to work with. For example, you can create a group of lists
that you then use to work with all the objects associated with a particular plan.

First you create a group and then you create the lists that you want in it. You can
create a group of lists within an engine or within another group of lists available
for each engine. To create a group of lists, perform the following steps:
1. In the Work with engines pane, right-click where you want to create the group
and select Create Group. The Properties - Group of Lists panel displays.
2. Enter a name for the group. You can use the same name for more than one
group. Different groups maintain their individual properties even if they have
the same name. Use only alphanumeric and blank characters. The maximum
supported length for this field is 80 characters.
3. Create the lists contained in the group as described inChapter 29, “Creating
database lists,” on page 161 and Chapter 30, “Creating plan lists,” on page 171.

© Copyright IBM Corp. 1991, 2006 181

Creating list groups

182 IBM Tivoli Workload Scheduler Job Scheduling Console: User’s Guide
Chapter 32. Creating common plan lists
This chapter describes how you create default common plan lists. It is divided into
the following sections:
v “Creating a common list of job stream instances”
v “Creating a common list of job instances”

Creating a common list of job stream instances

To create a common job stream instance list, perform the following steps:
1. In the Work with engines pane, right-click Common Default Plan Lists and
select Job Stream Instance.
2. The Properties - Job Stream Instance Common List panel displays.

The fields in this dialog are a subset of the fields available in Properties - Job
Stream Instance List described in “Creating z/OS job stream instance lists in the
plan” on page 171. Use the Engine pull-down menu to specify which engines are
used when creating the list. By default, all the engines to which the Job Scheduling
Console is connected are selected.

Use the Column Definition page to define the columns displayed in the list.

For a definition of the columns, refer to the Job Scheduling Console online help.

Creating a common list of job instances

To create a common job instance list, perform the following steps:
1. In the Work with engines pane, right-click Common Default Plan Lists and
select Job Instance.
2. The Properties - Job Instance Common List panel displays.

The fields in this dialog are a subset of the fields available in Properties - Job
Instance List described in “Creating z/OS job instance lists in the plan” on page
175. Use the Engine pull-down menu to specify which engines are used when
creating the list. By default, all the engines to which the Job Scheduling Console is
connected are selected.

Use the Column Definition page to define the columns displayed in the list.

For a definition of the columns, refer to the Job Scheduling Console online help.

© Copyright IBM Corp. 1991, 2006 183

184 IBM Tivoli Workload Scheduler Job Scheduling Console: User’s Guide
Chapter 33. Working with lists
This chapter describes how you work with lists. It is divided into the following
sections:
v “Displaying a list of objects”
v “Detaching a list” on page 186
v “Modifying a list” on page 186
v “Unlocking locked distributed objects in a list” on page 187

Most of your monitoring activities require a list of objects from which you can
work. Creating lists is described in Chapter 29, “Creating database lists,” on page
161 and Chapter 30, “Creating plan lists,” on page 171.

Displaying a list of objects

To display a list:
1. In the Work with engines pane, expand the engine tree until the list you want
to work with displays.
2. Click the list you want to run. The list results are displayed in the right-hand
pane.

You can display several lists in sequence. The newest list displays first. However,
as long as a list is kept open, it is maintained and refreshed according to the
refresh options specified.

The properties of lists are described in Part 6, “Managing database objects,” on

page 189.

When you display a list of All scheduled jobs, or All scheduled job streams for
z/OS or distributed engines (not common lists) an Explorer view pane is also
present.

© Copyright IBM Corp. 1991, 2006 185

Displaying a list

In end-to-end scheduling environments the start times displayed for job stream
instances in the All Scheduled Job Streams view and those shown for job instances
in the All Scheduled Jobs view might be different. This is due to a time zone
difference: the job streams that are defined on OPCMASTER are bound to follow the
UTC time zone, whereas the jobs defined on the fault-tolerant workstations follow
the time zones specified locally.

Detaching a list
Detaching a list frees the right-pane of the Job Scheduling Console to display other
objects. You can detach multiple lists to view several objects simultaneously.

To detach a list display, perform the following steps:

1. Select a list and wait for the results to be displayed.
2. Select Detach Task in the upper right-corner of the panel. The list panel
displays separately from the main window.
3. To reattach the list select Attach Task in the upper right-corner of the detached
pane.
Notes:
1. The right-hand pane of the console is not disabled. This is so that you can run
other lists or perform other tasks.
2. To prevent your system from overloading, do not have frequent refreshes of
many detached panes open at the same time.

Modifying a list
To modify the properties of a list:
1. In the Work with engines pane, select the engine.
2. Right-click the list you want to modify and select Properties.
3. The properties panel of the list displays.

186 IBM Tivoli Workload Scheduler Job Scheduling Console: User’s Guide
 Modifying a list

4. Make your changes.

The properties of lists are described in Chapter 34, “Managing engines,” on page
191.

Unlocking locked distributed objects in a list

While you work on a distributed object in the database or in the plan it is locked,
and can be viewed by other users only in read-only mode. When you have more
than one session open you can unlock an object that you locked in another session.

To unlock an object in a list, perform the following steps:

1. Run a list that contains the object you want to unlock. See Chapter 33,
“Working with lists,” on page 185.
2. Right-click the list and select Unlock from the pop-up menu.

Chapter 33. Working with lists 187

Unlocking objects in a list

188 IBM Tivoli Workload Scheduler Job Scheduling Console: User’s Guide
Part 6. Managing database objects

© Copyright IBM Corp. 1991, 2006 189

190 IBM Tivoli Workload Scheduler Job Scheduling Console: User’s Guide
Chapter 34. Managing engines
This chapter describes how you manage engines. To display and modify the
properties of an engine, perform the following steps:
1. In the Work with engines pane, right-click the engine and select Properties.
The Properties - Engine panel depends on whether you are:
v “Managing a z/OS engine”
v “Managing a distributed engine” on page 193

Managing a z/OS engine

The Properties - z/OS Engine panel displays.

The panel consists of the following:

v “General page” on page 192
v “Scheduler Information page” on page 192

© Copyright IBM Corp. 1991, 2006 191

 General page

General page
Use the General page to enter general information for the engine.

The page consists of the following:

| Engine Name
| Type a name for the engine that you are creating.
| Host Name
| Type the host name or TCP/IP address of the computer where the
| connector is installed.
| Port Number
| The port number that is used to connect to the computer where the
| connector is installed. The default port number is 31117.
| Remote Server Name
| The name of the instance of the connector specified at installation time.
| User Name
| Type the name of the TWSuser who accesses the computer where the
| engine is installed.
| Password
| Type the password of the user.

| Note: For some operating systems only the first eight characters of the
| password are used for authentication.
| Save Password
| Save password is enabled when you type a password. When you save the
| password it is not necessary to enter the user name and password each
| time that you access the engine.
| Periodic Refresh
| Whether the engine lists are periodically refreshed.
| Period (seconds)
| When Periodic Refresh is set, the frequency with which the engine lists are
| refreshed. The range is 30 to 7200 seconds.
| Buffer Size for Lists
| Select a value from the drop-down list. The value determines at which rate
| the results of a list are sent to your screen. For example if you select 100,
| the results of a list are sent in blocks of 100 lines. The default value is 250.
| If you select a higher number, it takes more time to display the list initially,
| but less time to display the entire list when it is scrolled. The maximum
| value is 400.

Scheduler Information page

Use the Scheduler Information page to view data about the engine.

The page consists of the following:

Engine Time Zone
The time zone of the engine indicated as an offset of GMT.
| Code Page
| Display the code page defined on the engine.

192 IBM Tivoli Workload Scheduler Job Scheduling Console: User’s Guide
 Scheduler Information page

Default for Submissions

Whether submissions should be according to the engine time or
workstation time.

Managing a distributed engine

The Properties - Distributed Engine panel displays.

The panel consists of the following:

v “General page”
v “Engine Data page” on page 194

General page
Use the General page to enter general information for the engine.

The page consists of the following:

| Engine Name
| Type a name for the engine that you are creating.
| Engine Type
| The type of engine.
Chapter 34. Managing engines 193
 General page

| Host Name
| Type the host name or TCP/IP address of the connector where the
| connector is installed.
| Port Number
| The port number that is used to connect to the computer where the
| connector is installed. The default port number is 31117.
| User Name
| Type the user name of the TWSuser who accesses the computer where the
| engine is installed.
| Password
| Type the password of the user.

| Note: For some operating systems only the first 8 characters of the
| password are used for authentication.
| Save Password
| Save password is enabled when you type a password. When you save the
| password it is not necessary to enter the user name and password each
| time that you access the engine.
| Periodic Refresh
| Whether the engine lists are periodically refreshed.
| Period (seconds)
| When Periodic Refresh is set, the frequency with which the engine lists are
| refreshed. The range is 30 to 7200 seconds.
| Buffer Size for Lists
| Select a value from the drop-down list. The value determines at which rate
| the results of a list are sent onto your screen. For example if you select 100,
| the results of a list are sent in blocks of 100 lines. The default value is 250.
| If you select a higher number, it takes more time to display the list initially,
| but less time to display the entire list when it is scrolled. The maximum
| value is 400.

Engine Data page

Use the Engine Data page to browse information about the engine.

The page consists of the following:

Engine Type
TWS
Version
The version of the engine.
Type The type of workstation where the engine resides. Possible values are:
MDM The workstation is a master domain manager.
BKM The workstation is a backup master.
FTA The workstation is a fault-tolerant agent, domain manager, or
backup domain manager.
SA The workstation is a standard agent.
Name The name of the workstation.

194 IBM Tivoli Workload Scheduler Job Scheduling Console: User’s Guide
 Engine Data page

Domain
The domain of the workstation.
Master Workstation
The workstation where the master domain manager resides.
Master Domain
The domain of the master domain manager.
Enabled
Whether the time zone feature is enabled for this engine.
Database
The time zone of the workstation where the database is installed.
Plan The time zone of the workstation where the plan is installed.
Batchman Status
The status of the batchman process.
Run Number
The number of times jnextday has run.
Schedule Date
The date of the last run of jnextday.

Chapter 34. Managing engines 195

Engine Data page

196 IBM Tivoli Workload Scheduler Job Scheduling Console: User’s Guide
Chapter 35. Managing workstations
This chapter describes managing workstations in the database. To display and
modify the properties of a workstation, perform the following steps:
1. Run a list of workstations that contains the workstation you want to manage.
See Chapter 33, “Working with lists,” on page 185.
2. In the list results, double-click the workstation you want to display, or
right-click the workstation and select Properties.
The Properties - Workstation in Database panel displays.
3. Make your changes. See “Creating a z/OS workstation” on page 98 and
“Creating a distributed workstation” on page 103.

© Copyright IBM Corp. 1991, 2006 197

198 IBM Tivoli Workload Scheduler Job Scheduling Console: User’s Guide
 Chapter 36. Managing z/OS job streams
This chapter explains how to modify job streams for z/OS engines. It is divided
into the following sections:
v “Creating dependencies between jobs”
v “Scheduling z/OS job streams” on page 202
v “Adding, modifying, and deleting jobs and dependencies” on page 214
v “Viewing and modifying time restrictions” on page 215
v “Using the copy function to add an external job” on page 217

Note: You can also perform the functions described here using the Explorer View.
For a brief description of the Explorer View, see Chapter 14, “Explorer View
quick reference,” on page 87.

Creating dependencies between jobs

This section describes how you create dependencies in a z/OS environment. it is
divided into the following subsections:
v “Creating dependencies within a job stream”
v “Creating dependencies between job streams” on page 200

Creating dependencies within a job stream

To create a dependency between jobs within the same job stream, perform the
following steps:
1. Run a list of job streams that contains the job stream you want to manage. See
Chapter 33, “Working with lists,” on page 185.
2. Double-click the job stream.
| The Job Stream Editor opens.

© Copyright IBM Corp. 1991, 2006 199

 Creating dependencies within a job stream

| 3. Click .
4. Click the predecessor job and drag the link to the successor job. A line displays
between the two jobs, with an arrow pointing to the successor job.
5. Repeat the previous steps to create as many dependencies as you need.

Creating dependencies between job streams

This section describes one way to add an external job to a job stream. Another
method, based on the use of job stream lists, is described in “Using the copy
function to add an external job” on page 217.

To create a dependency between job streams, perform the following steps:

1. Run a list of job streams that contains the job stream you want to manage. See
Chapter 33, “Working with lists,” on page 185.
2. Double-click the job stream.
| The Job Stream Editor displays.

200 IBM Tivoli Workload Scheduler Job Scheduling Console: User’s Guide
 Creating dependencies between job streams

| 3. Click .
The Properties - External Job panel displays.

Chapter 36. Managing z/OS job streams 201

 Creating dependencies between job streams

4. In Job Stream, type the name of the job stream containing the external job or
click ... to search for and select a job stream.
5. Click Show Jobs. The jobs in the job stream are displayed.
6. Select a job and click OK. An icon for the external job displays in the Graph
view.
7. Repeat the steps explained in “Creating dependencies between jobs” on page
199 to define links with the other jobs.

Scheduling z/OS job streams

This sections describes how you schedule z/OS job streams. It is divided into the
following subsections:
v “Creating rule-based run cycles”
v “Creating offset-based run cycles” on page 209

Creating rule-based run cycles

To create a rule-based run cycle, perform the following steps:
1. Run a list that contains the job stream you want to modify. See Chapter 33,
“Working with lists,” on page 185.
| 2. Double-click the job stream in the list. The Job Stream Editor opens.

3. Click to open the Run Cycle view of the job stream.

4. Click .

| The Properties - Rule-based Run Cycle panel displays.

|

202 IBM Tivoli Workload Scheduler Job Scheduling Console: User’s Guide
 Creating rule-based run cycles

| The panel consists of the following:

v “General page”
v “Time Restrictions page”
v “Rules page” on page 204

General page
Use the General page to enter general information about the run cycle.

The page consists of the following:

Name Type a name for the run cycle.
Description Type a description of the run cycle.
Rule for Freedays
Specify how you want Tivoli Workload Scheduler for z/OS to treat
freedays when calculating the rundays of the job stream, by
selecting one of the following:
Count workdays only
Excludes freedays when calculating on which days the job
stream runs.
Schedule on last workday before freeday
Counts both workdays and freedays. If the runday falls on a
freeday, it is shifted to the closest workday before the freeday.
Schedule on next workday after freeday
Counts both workdays and freedays. If the runday falls on a
freeday, it is shifted to the closest workday after the freeday.
Count workdays and freedays alike
Counts both workdays and freedays. The job stream is
scheduled on the runday, regardless of whether it is a freeday
or a workday. This is the default.
If freeday, do not schedule at all
Counts both workdays and freedays. If the runday falls on a
freeday, the job stream is not scheduled to run.
JCL Variable Table
Type the name of the variable table that the scheduler can use on
the days generated by this run cycle. Click ... (find) to search for
and select a variable table.
| Exclusive Run Cycle
| Specify the days and times that a job stream cannot be run.
Valid Date Set a time interval for which the run cycle is valid in the From and
To range you specify.

Time Restrictions page

Use the Time Restrictions page to specify when and for how long the job stream
must run.

The page consists of the following:

Start Type the time at which the job stream must start running. The default is
00:00 of the scheduled day.
| Deadline
| Specify the latest time by which the job stream must complete.
| At Type a time according to your locale settings. For example,
| type 12:00 if you want the job stream to end before noon.

Chapter 36. Managing z/OS job streams 203

 Time Restrictions page

| Delay for
| days Type a number of days to defer the deadline. For example,
| if you type 3 the job stream must end three days after the
| time you specify in At.
| Repeat Option
| Select Specify time when you want to set how frequently a job stream
| must run. If you select Specify time, specify both a Repeat Every and a
| Repeat End Time.
| Repeat Every
| Type the frequency at which the job stream must run in the format
| hh mm. For example, if you specify 01 10, the job stream runs
| every hour and 10 minutes.
| Repeat End Time
| Type the end time until which the Repeat Every option applies in
| a format specific to your locale settings. It must be a value between
| one minute after the input arrival time of the run cycle and one
| minute before the calendar work day end time of the job stream.
| After you set the Repeat Option, you can see the following information in
| the Run Cycle view:
| v In the left-hand pane, the Number of Generated Instances column
| shows the number of instances generated.
| v In the right-hand pane, the Calendar shows the day when the first
| generated instance runs.
| v If an instance runs on the following day the Run Cycle view shows a
| message that indicates the number of instances that run on each day.

Rules page
Use the Rules page to specify the rules on which the run cycle is based.

The page consists of the following:

Periods
The period rules for the run cycle. Possible values are:
Week
The run cycle is based on a weekly period.
Month
The run cycle is based on a monthly period.
Year
The run cycle is based on an annual period.
User-defined
The run cycle is based on a calendar defined by the user in the
scheduler.
Available Days
The days of the period to which the rule applies. The number of
available days changes according to the period you select. You can also
specify ordinal-last days to count backwards from the end of the
period. The days you select are displayed in the Selected Days field.
Available Types of Days
The types of days to which the rule applies. The types of days you
select are displayed in Selected Types of Days.
In the Following
The period names to which you want the rule to apply. Depending on
the period you select (Week, Month, Year, User-defined), this option
displays lists of weeks of the year by number, or months by name. If

204 IBM Tivoli Workload Scheduler Job Scheduling Console: User’s Guide
 Rules page

you selected a user-defined period, a list of available periods displays

in the In the Following Periods group. Select the check box next to the
period you want to use.

You can set more than one period at a time for complex rules specifying
more run cycles. For example you can select Week and Month and choose
the days that apply to both rules. You do not need to select the same days
twice because they are applied automatically to all run cycles. The
highlighted period affects the other options of the periods group. The
period that you select affects the number of days listed in the Available
Days scroll-list. The In the Following group changes depending on the
period you select.
Frequency
The frequency applied to the run cycle. Possible values are:
Only Select this if the rule applies to only one day in the
specified period. The rule does not repeat within the
period. For example, Only last Monday in Month schedules
the job stream to run on the last Monday of the month.
Every Select this if the rule is used to calculate more than one
day within the period. For example, Every last Monday in
Month schedules the job stream to run on every last
Monday in the month, because this rule generates a series
of Mondays starting from the last Monday.

Note: Every first day yields the same run days as Every day.
Shift Origin If you use Every, you can shift the origin of the run cycle
by the number of days you set in Shift Origin. You shift
the origin of the run cycle with respect to the default
origin, which is Monday in the Week period, and the first
week with at least 4 days in the Month and Year periods.
You can also shift the origin from the end, if you specify a
combination of Every and ordinal-last days.

Figure 11 on page 206 illustrates a rule that schedules the job stream to run on the
first day of every week where workdays and freedays are both counted..

Chapter 36. Managing z/OS job streams 205

 Rules page

|
| Figure 11. Example rule
|

Example 1: Rule-based run cycle

| Figure 12 on page 207 illustrates a rule-based run cycle starting from a Valid Date
| of November, 04, 2006, and where workdays and freedays are both counted. The
| number of generated instances is 361. In the right-hand pane, the Calendar shows
| that the day when the first generated instance occurs is November, 04, 2006. The
| Run Cycle view shows a message indicating that there are 360 instances that run
| on each day and one on the following day.

206 IBM Tivoli Workload Scheduler Job Scheduling Console: User’s Guide
 Rules page

|
| Figure 12. Rule-based run cycle
|

Example 2: Exclusive run cycle

| Figure 13 on page 208 illustrates an exclusive run cycle WPREXCEP that prevents
| job stream TC1CLA from running on the 3rd and 4th Friday of October 2006.

Chapter 36. Managing z/OS job streams 207

 Rules page

|
| Figure 13. Exclusive run cycle
|

Example 3: Exclusive run cycle defined

Figure 14 on page 209 illustrates a rule defined for the WPREXCEP exclusive run
cycle. The selected days are equal to those for the WEEKLYPR run cycle. The week
when the job stream must not run is specified in In the following weeks.

208 IBM Tivoli Workload Scheduler Job Scheduling Console: User’s Guide
 Creating offset-based run cycles

Figure 14. Exclusive run cycle defined

Creating offset-based run cycles

To create an offset-based run cycle, perform the following steps:
1. Run a list that contains the job stream you want to modify. See Chapter 33,
“Working with lists,” on page 185.
2. Double-click the job stream in the list.

3. Click to open the Run Cycle view of the job stream.

4. Click .

| The Properties - Offset-based Run Cycle panel displays.

Chapter 36. Managing z/OS job streams 209

 Creating offset-based run cycles

| The panel consists of the following:

v “General page”
v “Time Restrictions page” on page 211
v “Offsets page” on page 212

General page
Use the General page to enter general information about the run cycle.

The page consists of the following:

| Name Automatically generated when you identify the period in the In
| the Following Period field on the Offsets page.
Description Type a description of the run cycle.
Rule for Freedays
Specify how you want Tivoli Workload Scheduler for z/OS to treat
freedays when calculating the rundays of the job stream, by
selecting one of the following:
Count workdays only
Excludes freedays when calculating on which days the job
stream runs.
Schedule on last workday before freeday
Counts both workdays and freedays. If the runday falls on a
freeday, it is shifted to the closest workday before the freeday.
Schedule on next workday after freeday
Counts both workdays and freedays. If the runday falls on a
freeday, it is shifted to the closest workday after the freeday.
Count workdays and freedays alike
Counts both workdays and freedays. The job stream is
210 IBM Tivoli Workload Scheduler Job Scheduling Console: User’s Guide
 Creating offset-based run cycles

scheduled on the runday, regardless of whether it is a freeday

or a workday. This is the default.
If freeday, do not schedule at all
Counts both workdays and freedays. If the runday falls on a
freeday, the job stream is not scheduled to run.
JCL Variable Table
Type the name of the variable table that the scheduler can use on
the days generated by this run cycle. Click ... (find) to search for
and select a variable table.
| Exclusive Run Cycle
| Specify the days and times that a job stream cannot be run.
Valid Date Set a time interval for which the run cycle is valid in the From and
To range you specify.

Time Restrictions page

Use the Time Restrictions page to specify when and for how long the job stream
must run.

The page consists of the following:

Start The time at which the job stream must start running. The default is 00:00
of the scheduled day.
| Deadline
| Specify the latest time by which the job stream must complete.
| At Type a time according to your locale settings. For example,
| type 12:00 if you want the job stream to end before noon.
| Delay for
| days Type a number of days to defer the deadline. For example,
| if you type 3 the job stream must end three days after the
| time you specify in At.
| Repeat Option
| Select Specify time when you want to set how frequently a job stream
| must run. If you select Specify time, specify both a Repeat Every and a
| Repeat End Time.
| Repeat Every
| Type the frequency at which the job stream must run in the format
| hh mm. For example, if you specify 01 10, the job stream runs
| every hour and 10 minutes.
| Repeat End Time
| Type the end time until which the repeat every option applies in a
| format specific to your locale settings. It must be a value between
| one minute after the input arrival time of the run cycle and one
| minute before the calendar work day end time of the job stream.
| After you set the Repeat Option, you can see the following information in
| the Run Cycle view:
| v In the left-hand pane, the Number of Generated Instances column
| shows the number of instances generated.
| v In the right-hand pane, the Calendar shows the day when the first
| generated instance runs.
| v If an instance runs on the following day the Run Cycle view shows a
| message that indicates the number of instances that run on each day.

Chapter 36. Managing z/OS job streams 211

 Creating offset-based run cycles

Offsets page
Use the Offsets page to define the offsets for the run cycle.

The page consists of the following:

In the Following Period
Type the name of a period or click ... (find) to search for and select a
period. The period is also used as the run cycle name.
Available Offsets
The days when you want the job stream to run in the period. Select ordinal
last days to count the days from the end of the period. The days you select
are displayed in Selected Offsets.

Example 1: Offset-based run cycle

Figure 15 illustrates an offset-based run cycle named PER1. This run cycle
schedules job stream PAYRO21 to run on every second day of each cycle,
beginning from a Valid date of May 21, 2003.

|
| Figure 15. Example 1: Offset-based run cycle
|
Example 2: Offset-based run cycle defined
Figure 16 on page 213 illustrates the offset for run cycle PER1. The offset is the
second day of the user defined period, also named PER1.

212 IBM Tivoli Workload Scheduler Job Scheduling Console: User’s Guide
 Creating offset-based run cycles

Figure 16. Example 2: Offset-based run cycle defined

Chapter 36. Managing z/OS job streams 213

 Adding, modifying, and deleting jobs and dependencies

Adding, modifying, and deleting jobs and dependencies

To add, modify, or delete jobs and dependencies in an existing job stream:
1. Run a job stream list that contains the job stream you want to modify. See
Chapter 33, “Working with lists,” on page 185.
2. Double-click the job stream you want to open. The Job Stream Editor opens.
You can perform your tasks using the following options:
v “Modifying a job in the Graph View”
v “Deleting a job or external job”
| v “Deleting jobs simultaneously from a job stream”
v “Editing another job stream from an external job” on page 215
v “Removing a dependency between jobs in the Graph View” on page 215

Modifying a job in the Graph View

To modify a job in the Graph View, perform the following steps.
1. Right-click the job and select Properties from the pop-up menu.

Note: If any of the job icons in the Graph view display a superimposed
question mark, this is an indication that the definition of the workstation
associated with the particular job cannot be found in the database. If job
label displays (Not Found), an external job is missing because the job or
the job stream to which it belongs was deleted.
2. Change the settings as necessary. See “Creating a job” on page 136.
3. Click Save.

Deleting a job or external job

To delete a job or external job from the job stream, perform the following steps:
1. Right-click the job or external job and select Delete from the pop-up menu, or
click Delete in the toolbar.
2. Click OK in the confirmation window. The job is deleted from the job stream.

Note: You can use the Undo Delete option in the same pop-up menu or in the
toolbar of the Graph view to put the job back in the job stream. This
option is valid until you save the job stream. A job stream must have at
least one job.
3. Click Save.

| Deleting jobs simultaneously from a job stream

| To delete jobs simultaneously from the job stream, perform the following steps:
| 1. Click the
|

|
| The Explorer View Editor opens.
| 2. In the Table View select the jobs you want to delete.
| 3. Rick-click and select Delete from the pop-up menu.
| 4. Click OK in the confirmation window. The jobs are deleted from the job
| stream.
| 5. Click Save.

214 IBM Tivoli Workload Scheduler Job Scheduling Console: User’s Guide
 Editing another job stream from an external job

Editing another job stream from an external job

To open a second Job Stream Editor and edit the job stream to which an external
job belongs, perform the following steps:
1. Right-click the external job and select Edit  External Job Stream. An
additional Job Stream Editor panel displays.
2. Use the job stream editor views to work on the job stream and its components.

Removing a dependency between jobs in the Graph View

To remove a dependency between jobs in the Graph View, perform the following
steps:
1. Right-click the line that represents the dependency. The line becomes red and a
pop-up menu opens.
2. Select Delete from the pop-up menu. A confirmation panel displays.
3. Click OK in the confirmation panel. The dependency is removed.
4. Click Save.

Viewing and modifying time restrictions

The Timeline view of the Job Stream Editor shows the time restrictions of the jobs
and run cycles of a job stream. You can modify the time restrictions of a job or of a
run cycle in the same way you created them, by using either the Job Properties
panel of the Graph view, or the Run Cycle Properties panel of the Run Cycle view.

In addition, you can view and modify time restrictions for more than one run cycle
and more than one job in the Timeline view.

Changing time restrictions in the Timeline View

To change time restrictions in the Timeline View, perform the following steps:
1. Run a list of job streams that contains the job stream you want to modify. See
Chapter 33, “Working with lists,” on page 185.
2. Double-click the job stream.
The Job Stream Editor opens.

3. Click .
The Timeline View opens.

The left-hand pane of the Timeline View displays the following job stream instance
details:

Chapter 36. Managing z/OS job streams 215

Changing time restrictions in the Timeline View

Figure 17. Timeline View

The right-hand pane has activity bars that show the actual run time if the instances
have begun, as well as the specified time restrictions for the instances.

By moving components of the activity bars, you can change the time restrictions of
each instance and view the results of your changes, as you would by following the
steps described in “Browsing and modifying job stream instances” on page 259 and
going directly to the Time Restrictions tab of the Properties - Job Stream Instance
panel.

The activity bar shows the runtime of a job stream instance in terms of the start
and deadline times that were specified as time restrictions for the job stream. The
deadline is indicated by a vertical black stripe at the end of the blue activity bar.
As the instance starts, a horizontal black line unfolds inside the activity bar to
show the actual runtime.

You can change the time restrictions of an instance that has yet to run, or that is
running by performing one of the following operations:
v “Changing the instance”
v “Rescheduling the start time” on page 217
v “Rescheduling the deadline time” on page 217

Changing the instance

To change the instance, perform the following steps:
1. Move the activity bar by positioning the mouse pointer inside the bar and,
when the pointer becomes cross-shaped, hold down the left mouse button
while moving the bar in either direction.
As you move the bar, a tooltip tells you the new deadline time at every
position of the right end of the bar.

216 IBM Tivoli Workload Scheduler Job Scheduling Console: User’s Guide
 Changing time restrictions in the Timeline View

2. When you find the position you want, release the mouse button. The Properties
- Job Stream Instance panel displays, showing the new start and deadline times.

Rescheduling the start time

To reschedule the start time, perform the following steps:
1. Position the mouse pointer on the left end of the bar. When the pointer
becomes pointer becomes cross-shaped, hold down the left mouse button while
moving the end of the bar. As you move your mouse, a tooltip tells you the
corresponding start time at every new position of the left end of the bar.
2. When you find the position you want, release the mouse button. The Properties
- Job Stream Instance panel displays, showing the new start time.

Rescheduling the deadline time

To reschedule the deadline time, perform the following steps:
1. Position the mouse pointer on the right end of the bar. When the pointer
becomes cross-shaped, hold down the left mouse button while moving the end
of the bar. As you move your mouse, a tooltip tells you the corresponding
deadline time at every new position of the right end of the bar.
2. When you find the position you want, release the mouse button. The Properties
- Job Stream Instance panel displays, showing the new deadline time.

Using the copy function to add an external job

You can use the copy function on a listed job stream to add any of the jobs that
comprise it as external jobs to another job stream, as described in the following
example:
1. Run a job stream list that contains the job stream you want to manage. See
Chapter 33, “Working with lists,” on page 185.
2. Right-click a job stream and select Open. The Job Stream Editor opens.
3. Right-click another job stream in the list and select Copy from the pop-up
menu.
4. Go to the Job Stream Editor where the first job stream is open.
5. Right-click anywhere in the panel and select Paste from the pop-up menu.
6. In the Properties - External Job panel, select Show jobs. All the jobs that
comprise the second job stream are displayed.
7. Select the job or jobs that you want to add as external jobs of the first job
stream.
8. Click OK to close the Properties - External Job panel. Icons for the added jobs
are displayed in the Graph view of the first job stream.

Note: You can use Add Link to define dependencies between the jobs in the Job
Stream Editor. For more information, see “Creating dependencies between
job streams” on page 200.

Chapter 36. Managing z/OS job streams 217

Changing time restrictions in the Timeline View

218 IBM Tivoli Workload Scheduler Job Scheduling Console: User’s Guide
 Chapter 37. Managing distributed job streams
This chapter describes how to modify distributed job streams. It is divided into the
following sections:
v “Adding external dependencies to a job stream in the Graph View”
v “Adding external dependencies to a job stream in the Explorer View” on page
221
v “Adding a job to a job stream in the Graph View” on page 222
v “Adding a job to a job stream in the Explorer View” on page 226
v “Using the copy function to add an external job to a job stream” on page 227
v “Adding an internetwork dependency to a job in the Graph View” on page 228
v “Adding an internetwork dependency to a job in the Graph View” on page 228
v “Adding an external job stream to a job stream” on page 228
v “Adding an external job to a job stream” on page 229
v “Creating dependencies between jobs in a job stream” on page 230
v “Adding run cycles to a job stream” on page 231
v “Deleting external dependencies from a job stream” on page 235
v “Deleting run cycles from a job stream” on page 236
| v “Deleting jobs simultaneously from a job stream” on page 236
v “Checking time restrictions in the Timeline View” on page 236

Adding external dependencies to a job stream in the Graph View

To add external dependencies to a job stream, perform the following steps:
1. Run a list of job streams that contains the job stream you want to modify. See
Chapter 33, “Working with lists,” on page 185.
2. Double-click the job stream in the list.
The Job Stream Editor opens.
3. Select External Dependencies from the File menu.
The Job Stream External Dependencies panel displays.

© Copyright IBM Corp. 1991, 2006 219

 Managing distributed job streams in the database

From the drop-down list, select whether to:

v “Add an external job stream dependency”
v “Add an internetwork dependency”
v “Add an external job dependency”

Add an external job stream dependency

To add an external job stream dependency, perform the following steps:

1. Click .
2. Double-click in the Job Name column of the new row.
3. Click ... (find) to search for and select a job stream. The following information
displays:
| Job Stream Name
| The name of the external job stream on which the job stream depends.
| Workstation
| The name of the workstation the job stream on which the job stream
| depends, is defined to run on.
| Dependency Resolution
| The dependency resolution criteria used for resoling dependencies. See
| “Dependency Resolution page” on page 149

Add an internetwork dependency

To add an internetwork dependency, perform the following steps:

1. Click .
2. Double-click in the Network Agent column of the new row.
3. Click ... (find) in the Network Agent column to search for and select the name
of the network agent. Internetwork dependencies require that a network agent
is configured to communicate with the external scheduler network. For
information about configuring a network agent, refer to the IBM Tivoli Workload
Scheduler: Reference Manual.
4. Double-click the Dependency cell enter either a dependency, or the job or job
stream predecessor in the form workstation#jobstream.job.

Add an external job dependency

To add an external job dependency, perform the following steps:

1. Click .
2. Double-click in the Job Name column of the new row.
3. Click the ... (find) in the Job Name column to search for and select a job.
| Job Name
| The name of the job on which the job stream depends.
| Job Stream Name
| The name of the job stream that contains the job.
| Job Stream Workstation Name
| The name of the workstation the job stream containing the job, is
| defined to run on.

220 IBM Tivoli Workload Scheduler Job Scheduling Console: User’s Guide
 Managing distributed job streams in the database

| Dependency Resolution
| The dependency resolution criteria used for resoling dependencies. See
| “Dependency Resolution page” on page 149

Adding external dependencies to a job stream in the Explorer View

To add external dependencies to a job stream in the Explorer View, perform the
following steps:
1. Run a list of job streams that contains the job stream you want to modify. See
Chapter 33, “Working with lists,” on page 185.
2. Double-click the job stream in the list.
The Job Stream Editor opens.

3. Click .
The Explorer View opens.

4. Select the job in the Table View and click Predecessors in the Properties pane.

5. Click .
6. Select External from the Dependency Type column.
7. Double-click in the Job Stream column and click ... (find) to search for and
select the job stream.
8. Double-click in the Job Name column and click ... (find) to search for and
select the job.
9. Double-click in the Workstation column and click ... (find) to search for and
select the workstation.

Chapter 37. Managing distributed job streams 221

Managing distributed job streams in the database

10. Select how the dependencies of the job stream are resolved in the
Dependency Resolution column.

Note: When you add dependencies in the Explorer View, you work with the links
of the dependency and not the with the graphic icon in the Graph View. To
remove the icon, switch to the Graph View and use the delete function.

Adding a job to a job stream in the Graph View

To add a job to a job stream in the Graph View, perform the following steps:
1. Run a list of job streams that contains the job stream you want to manage. See
Chapter 33, “Working with lists,” on page 185.
2. Double-click the job stream in the list.
The Job Stream Editor opens.

3. Click to open the Graph View.

4. Click in the toolbar.

The Properties - Job panel displays.

The panel consists of the following:

v “General page” on page 223
v “Time Restrictions page” on page 223

222 IBM Tivoli Workload Scheduler Job Scheduling Console: User’s Guide
 Managing distributed job streams in the database

v “Resources page” on page 225

v “Files page” on page 225
v “Prompts page” on page 225

General page
Use the General page to add general information about the job.

The page consists of the following:

Name The name of the job. If you do not specify it the default is the name of the
job definition.
Job Definition
The name of an existing job definition. Click ... (find) to search for and
select a job definition.
Workstation Name
The workstation the job is defined to run on.
New Click New to create a new job definition to add to the job stream.
Edit Click Edit to edit the properties of an existing job definition.
Description
A description of the job definition.
Priority
The priority of the job. Type a priority value or click:
Hold Sets the priority to zero.
High Sets the priority to 100.
Go Sets the priority to 101.

Possible priority values are 0 through 101, where 101 is the highest priority.
A priority value of zero prevents the job from launching.
Requires Confirmation
| The job completion must be confirmed by the operator. When a job that
| requires confirmation completes, it remains in PEND until confirmation is
| received. Job and job stream successors are not released until confirmation
| is received. If confirmation is received before the job completes, its internal
| status is either SUCCP or ABENDP and other job and job stream
| successors are not released until the job completes. When the job completes
| its internal status is either SUCC or ABEND.
Monitored Job
The running of this job must be monitored by Tivoli Business Systems
Manager. Changes to the monitored job status are not displayed in the job
stream properties until you close and reopen the job stream.

Time Restrictions page

Use the Time Restrictions page to specify the time constraints for the job.

The page consists of the following:

Time Zone The time zone of the job time restrictions. This list is available only
if time zone support is enabled. For information about enabling the
time zone, refer to IBM Tivoli Workload Scheduler: Planning and
Installation Guide.
Start The time before which the job must not start.

Chapter 37. Managing distributed job streams 223

 Managing distributed job streams in the database

Specify Time
Select Specify Time when you want to set a start time for
the job.
| Time Dependent
| The job has a time dependency. When you do not specify
| that the job is time dependent, the Start time indicates the
| time when the job is entered into the plan. This check is
| enabled only if you select Specify Time.
At The time before which the job must not start. The time
format is according to your locale.
Delay for Days
The number of days to offset the start time from the day
the job is selected for inclusion in the production plan.
Latest Start Time
The latest time at which the job is allowed to start.
Specify Time
Select Specify Time when you want to set a latest start
time for the job.
Delay for Days
The number of days to offset the latest start time from the
day the job is selected for inclusion in the production plan.
Action The action to be performed in case the job does not start and the
Latest Start Time expires.
Suppress
To specify that the job does not start, even if the error condition
that prevented it from starting is corrected, and dependencies
are not released. Suppress is the default.
Continue
To specify that the job starts when the error condition that
prevented it from starting is corrected.
Cancel
To specify that the job is cancelled and dependencies are
released.
Termination Deadline
The time by which the job must complete. Jobs that have not yet
started or that are still running when the deadline time expires, are
considered late in the plan. The termination deadline does not
prevent jobs from starting.
Specify Time
Select Specify Time when you want to set a deadline time
for the job.
Delay for Days
The number of days to offset the deadline time from the
day the job is selected for inclusion in the production plan.
Repeat Range The interval of time in Hours and Minutes for each job run to be
repeated. Using the Repeat Range information with the Start and
Termination Deadline times allows you to run a job instance, for
example every 15 minutes from 1:00 p.m. to 5:00 p.m.
Normal Elapsed Time
The estimated average time the job needs to run based on previous
runs.

224 IBM Tivoli Workload Scheduler Job Scheduling Console: User’s Guide
 Managing distributed job streams in the database

Resources page
To add a resource dependency for the job, perform the following steps:

1. Click .
2. Double-click in the Resources cell and click ... (find) to search for and select a
resource.
3. Double-click in the Workstation cell to type the name of the workstation where
the resource resides.
4. Double-click in the Quantity cell and enter the number of resource units
required by the job. The number of jobs and schedules using a resource at any
one time cannot exceed 32.

To remove a resource dependency for the job, select the resource row in the list

and click .

Files page
To add a file dependency for the job, perform the following steps:

1. Click .
2. Double-click in the Filename cell and click ... (find) to search for and select a
file. You can search for a file only if it resides on the workstation where the Job
Scheduling Console resides.
3. Double-click in the Workstation cell to search for and select a workstation.
4. Double-click in the Qualifiers column and enter the test conditions for the file
dependency. On UNIX, the valid qualifiers are the same as UNIX test
command conditions. For more information, refer to your UNIX system
documentation.
For a list of the Windows qualifiers, see “Files page” on page 152.
On both UNIX and Windows, the expression %p inserts the file name.
Entering notempty is the same as entering -s %p. If no qualifier is specified,
the default is -f %p.

To remove a file dependency for the job, select the file row in the list and

click .

| Prompts page
| Use the Prompts page to set ad hoc or predefined prompt dependencies for the
| job.

| To add an ad hoc prompt for the job, perform the following steps:
| 1. From the drop-down list, select Ad Hoc Prompt.

| 2. Click .
| 3. Double-click in the Text cell and type the text of the prompt. The default
| behavior of a prompt is to display a message and wait for a reply. Based on the
| character preceding the text, the prompt can behave differently:
| v If the text begins with a colon (:), the prompt displays, but no reply is
| required to continue processing.

Chapter 37. Managing distributed job streams 225

 Managing distributed job streams in the database

| v If the text begins with an exclamation mark (!), the prompt displays, but it is
| not recorded in the log file.
| Refer to the IBM Tivoli Workload Scheduler: Reference Manual for a detailed
| explanation on how to specify the text of a prompt.
| You can include one or more scheduler parameters as part or all of the text
| string. To use a parameter, place its name between carets (^) .

| To add a predefined prompt for the job, perform the following steps:
| 1. From the drop-down list, select Predefined Prompt.

| 2. Click .
| 3. Type the name of the prompt in the Name cell or click ... (find) to search for
| and select the prompt. The Text cell displays the text of the predefined prompt
| message. This field is read-only.

| To remove a prompt dependency for the job, select the prompt row in the list and

| click .

Adding a job to a job stream in the Explorer View

To add a job to a job stream using the Explorer View, perform the following steps:
1. Run a list of job streams that contains the job stream you want to manage. See
Chapter 33, “Working with lists,” on page 185.
2. Double-click the job stream in the list.
The Job Stream Editor opens.

3. Click to open the Explorer View.

4. Click in the toolbar.

The Properties - Job panel displays.

226 IBM Tivoli Workload Scheduler Job Scheduling Console: User’s Guide
 Managing distributed job streams in the database

The panel consists of the following:

v “General page” on page 223
v “Time Restrictions page” on page 223
v “Resources page” on page 225
v “Files page” on page 225
v “Prompts page” on page 225

Note: You can also add multiple jobs to a job stream using . When you add
multiple jobs you can edit their properties one at a time.

Using the copy function to add an external job to a job stream

To use the copy function to add an external job to a job stream, perform the
following steps:
1. Run a list that contains the job stream you want to modify. See Chapter 33,
“Working with lists,” on page 185.
2. Right-click a job stream and select Open. The job stream opens in the Graph
view of the job stream editor.
3. Right-click another job stream in the list and this time select Copy from the
pop-up menu.
4. Go to the job stream editor where the first job stream is open.
5. Right-click anywhere in the window and select Paste from the pop-up menu.

Chapter 37. Managing distributed job streams 227

Managing distributed job streams in the database

6. In the Dependencies Properties - External Job panel, select Show jobs. All the
jobs that comprise the second job stream are displayed.
7. Select the job that you want to add as an external job of the first job stream.
8. Click OK to close the Properties - External Job panel. Icons for the added jobs
are displayed in the Graph view of the first job stream.

Note: You must use Add Link to define dependencies between the jobs in the job
stream editor. For more information, see “Adding external dependencies to a
job stream in the Graph View” on page 219.

Adding an internetwork dependency to a job in the Graph View

To add an internetwork dependency, perform the following steps:
1. Run a list that contains the job stream you want to modify. See Chapter 33,
“Working with lists,” on page 185.
2. Double-click the job stream that you want to modify. The Job stream Editor
opens.

3. Click to open the Graph View.

4. Click Add Dependency on Internetwork in the toolbar. The Internetwork
Dependency panel displays.
5. Click ... (find) to search for and select a network agent.
6. In Dependency, specify either the dependency, or the job or job stream
predecessor in the format workstation#jobstream.job. The maximum length of
this field is:
v 16 for the workstation
v 16 for the job stream
v 40 for the job

Note: You must use Add Link to define dependencies between the jobs in the job
stream editor. For more information, see “Adding external dependencies to a
job stream in the Graph View” on page 219.

For information about using an internetwork dependency as a predecessor, see

“Creating dependencies between jobs in a job stream” on page 230.

Adding an external job stream to a job stream

You add external job streams to a job stream to create predecessors for the jobs in
the job stream you are editing.

To add an external job stream, perform the following steps:

1. Run a list that contains the job stream you want to modify. See Chapter 33,
“Working with lists,” on page 185.
2. Double-click the job stream that you want to modify. The Job stream Editor
opens.

3. Click to open the Graph View.

4. Click Add Dependency on External Job Stream in the toolbar. The External Job
Stream Dependency panel displays.

228 IBM Tivoli Workload Scheduler Job Scheduling Console: User’s Guide
 Managing distributed job streams in the database

5. Click ... (find) to search for and select the workstation on which the job stream
runs.
6. Click Show Job Streams to list the job streams that run on the workstation.
7. Select a job stream from the list.
8. Add a link between the external job stream and its successor jobs.

For information about using an external job stream as a predecessor, see “Creating
dependencies between jobs in a job stream” on page 230.

Adding an external job to a job stream

You add external jobs to a job stream to create predecessors for the jobs in the job
stream you are editing. A predecessor must complete successfully before the
successor job is launched.

You add external jobs in a job stream using the Graph view of the job stream
editor. For more information, see Chapter 37, “Managing distributed job streams,”
on page 219.

To add an external job, perform the following steps:

1. Run a list that contains the job stream you want to modify. See Chapter 33,
“Working with lists,” on page 185.
2. Double-click the job stream that you want to modify. The Job stream Editor
displays.

Chapter 37. Managing distributed job streams 229

Managing distributed job streams in the database

3. Click Add Dependency on External Job in the toolbar. The External Job
Dependency panel displays.

4. Click ... (find) to search for and select the job stream in which the job runs.
5. Click Show Jobs to list the jobs in the selected job stream that run on the
selected workstation.
6. Select a job in the list.
7. Add a link between the external job and its successor jobs.

For information about using an external job as a predecessor, see “Creating

dependencies between jobs in a job stream.”

Creating dependencies between jobs in a job stream

You can add dependencies between jobs to specify the order in which they run. A
job that depends on the successful completion of another job is called a successor
and the job or job stream that it depends on is called a predecessor.

You add dependencies between jobs in the Graph view of the job stream editor.
For more information, see Chapter 37, “Managing distributed job streams,” on page
219. The dependencies are represented by arrows.

230 IBM Tivoli Workload Scheduler Job Scheduling Console: User’s Guide
 Managing distributed job streams in the database

To add a dependency between jobs, perform the following steps:

1. Run a list that contains the job stream you want to modify. See Chapter 33,
“Working with lists,” on page 185.
2. Double-click the job stream that you want to modify. The Job stream Editor
displays.
3. Click Add Link in the toolbar.
4. Click the predecessor job or job stream and drag it to the successor job. When
you release the mouse button, an arrow is drawn from the predecessor to the
successor.
Notes:
1. Internetwork dependencies, external jobs, and external job streams cannot be
successors.
2. Internetwork dependencies, external jobs, and external job streams that are not
linked are not saved when the Job Stream Editor is closed.

To remove a dependency between jobs, select the arrow between the predecessor
and the successor, then right-click the arrow and select Delete from the pop-up
menu.

Adding run cycles to a job stream

You specify run cycles using the Job Stream Editor. To do this, perform the
following steps:
1. Run a list that contains the job stream you want to modify. See Chapter 33,
“Working with lists,” on page 185.
2. Double-click the job stream that you want to modify. The Job Stream Editor
displays.

3. Click .
The Run Cycle View displays.

Chapter 37. Managing distributed job streams 231

Managing distributed job streams in the database

4. Click . The Run Cycle panel displays.

The panel consists of the following:

v “Rule page”
v “Time Restrictions page” on page 234

Rule page
Use the Rule page to set rules for the run cycle.

The page consists of the following:

Name Type a name for the run cycle that you are creating.
Description Type a description for the run cycle that you are creating.
Starting The date at which the run cycle begins. The default is the current
date.
Ending The date at which the run cycle ends.
Rule for freedays
Select the rule to follow on free days. Possible values are:
None
Follow no rule. Run the job stream regardless of whether the
schedule falls on a freeday or on a workday.

232 IBM Tivoli Workload Scheduler Job Scheduling Console: User’s Guide
 Managing distributed job streams in the database

If freeday, do not select

If the scheduled date falls on a freeday, do not run the job
stream.
Select nearest workday before freeday
If the scheduled date falls on a freeday, run the job stream on
the preceding workday.
Select nearest workday after freeday
If the scheduled date falls on a freeday, run the job stream on
the following workday.
Inclusive Select when the run cycle is to include the days set.
Exclusive Select when the run cycle is to exclude the days set.
Type Select the type of run cycle you are creating. Possible values are:
v “Simple run cycles”
v “Calendar run cycles”
v “Daily run cycles”
v “Weekly run cycles” on page 234
v “Monthly by date run cycles” on page 234
v “Monthly by day run cycles” on page 234
v “Yearly run cycles” on page 234

Simple run cycles

Note: It is not possible to create simple run cycles without using a mouse. If you
need to create a run cycle and do not have access to a mouse, create another
type of run cycle.
When you select to create a Simple run cycle, the Type data consists of the
following:
Month Select Month to set dates for your simple run cycle by month.
Year Select Year to set dates for you simple run cycle by year.

Calendar run cycles

When you select to create a Calendar run cycle, the Type data consists of the
following:
Calendar Type the name of the calendar, or click ... (find) to search for and
select the calendar.
Offset Specify the offset for the run cycle. You can specify a negative or a
positive offset, whether the offset should include all Days,
Workdays only, or Weekdays only.

Daily run cycles

When you select to create a Daily run cycle, the Type data consists of the
following:
Frequency Specify the frequency of the run cycle as days, such as Every 3
Days.
On Specify the types of day the run cycle is run. Possible values are:
v Everyday
v Workdays
v Freedays

Chapter 37. Managing distributed job streams 233

 Managing distributed job streams in the database

Weekly run cycles

When you select to create a Weekly run cycle, the Type data consists of the
following:
Frequency Specify the frequency of the run cycle in weeks, such as Every 3
Weeks.
On Specify the day of the week.

Monthly by date run cycles

When you select to create a Monthly by Date run cycle, the Type data consists of
the following:
Frequency Specify the frequency of the run cycle in months, such as Every 3
Months.
On the (ascending order)
Specify the numeric day of the month when the run cycle runs in
ascending order: 1st day, 2nd day, and so on.
On the (descending order)
Specify the numeric day of the month when the run cycle runs in
descending order: Last day, 2nd last day, and so on.

Monthly by day run cycles

When you select to create a Monthly by Day run cycle, the Type data consists of
the following:
Frequency Specify the frequency of the run cycle in months, such as Every 3
Months.
On the (ascending order)
Specify the day of the month in days when the run cycle runs in
ascending order: 1st Sunday, 2nd Sunday, and so on.
On the (descending order)
Specify the day of the month in days when the run cycle runs in
descending order: Last Sunday, 2nd last Sunday, and so on.

Yearly run cycles

When you select to create a Yearly run cycle, the Type data consists of the
following:
Frequency Specify the frequency of the run cycle in years, such as Every 2
Years.

Time Restrictions page

The page consists of the following:
Time Zone The time zone set in the job stream properties panel. This list is
available only if time zone support is enabled. For information
about enabling the time zone, refer to IBM Tivoli Workload
Scheduler: Planning and Installation Guide.
Start The time before which the job stream must not start.
Specify time Select Specify time when you want to set a start
time for the job stream.
| Time dependent
| Select Time dependent when the job stream is time
| dependent. This check is enabled only if you select
| Specify Time.

234 IBM Tivoli Workload Scheduler Job Scheduling Console: User’s Guide
 Managing distributed job streams in the database

At The time before which the job stream must not

start. The time format is according to your locale.
Delay for Days
The number of days to offset the start time from
the day the job stream is selected for inclusion in
the production plan.
Latest Start Time
The latest time at which the job stream is allowed to start.
Specify Time
Select Specify Time when you want to set a latest start
time for the job stream.
Delay for Days
The number of days to offset the latest start time from the
day the job stream is selected for inclusion in the
production plan.
Action The action to be performed in case the job stream does not start
and the Latest Start Time expires.
Suppress To specify that the job stream does not start, even
if the error condition that prevented it from
starting is corrected, and dependencies are not
released. Suppress is the default.
Continue To specify that the job stream starts when the error
condition that prevented it from starting is
corrected.
Cancel To specify that the job stream is cancelled and
dependencies are released.
Termination Deadline
The time by which the job stream must complete. Job streams that
have not yet started or that are still running when the deadline
time expires, are considered late in the plan. The termination
deadline does not prevent job streams from starting. Possible
values are:
Specify Time Select Specify Time when you want to set a
deadline time for the job stream.
Delay for Days
The number of days to offset the deadline time
from the day the job stream is selected for
inclusion in the production plan.

Deleting external dependencies from a job stream

Job streams can be dependent on the successful running of other job streams, jobs
in other job streams, and jobs or job streams in other Tivoli Workload Scheduler
networks (internetwork dependecies). These external dependencies are also called
predecessors.

To delete external dependencies for a job stream, perform the following steps:
| 1. Run a list that contains the relative job stream. See Chapter 33, “Working with
| lists,” on page 185.
| 2. Double-click the job stream. The Job Stream Editor displays.
3. Select External Dependencies from the File menu. This displays the Job Stream
External Dependencies panel.

Chapter 37. Managing distributed job streams 235

 Managing distributed job streams in the database

4. Select External Job Stream, Internetwork, or External Job from the drop-down
menu.
5. Click the row of the dependency in the list you want to delete and click Delete
Row.

Deleting run cycles from a job stream

To delete a run cycle from a job stream, perform the following steps:
1. Run a list that contains the relative job stream. See Chapter 33, “Working with
lists,” on page 185.
2. Double-click the job stream. The Job Stream Editor displays.

3. Click . The Run Cycle view displays.

4. Select the run cycle you want to delete from the job stream.
5. Click Delete. If the run cycle was a calendar it is deleted from this job stream,
but it is not deleted from the database and can still be used by other job
streams.

| Deleting jobs simultaneously from a job stream

| To delete jobs simultaneously from the job stream, perform the following steps:
| 1. Run a list that contains the relative job stream. See Chapter 33, “Working with
| lists,” on page 185.
| 2. Double-click the job stream. The Job Stream Editor displays.
| 3. Click the
|

|
| The Explorer View Editor displays.
| 4. In the Table View select the jobs you want to delete
| 5. Rick-click and select Delete from the pop-up menu.
| 6. Click OK in the confirmation window. The jobs are deleted from the job
| stream.
| 7. Click Save.

Checking time restrictions in the Timeline View

The Timeline view of the Job Stream Editor shows graphically the time restrictions
of the jobs and run cycles of a job stream in the database. While you create a job
stream, the Timeline view helps you to ensure that the time dependencies you
specified are correct and coherent. The view can point out inconsistencies between
the time restrictions of jobs and those of run cycles. It can also show if there are
inconsistencies within the time restrictions of individual jobs.

To open the Timeline view of a job stream, click Timeline in the toolbar of any of
the other views of the Job Stream Editor.

The Timeline view displays.

236 IBM Tivoli Workload Scheduler Job Scheduling Console: User’s Guide
 Checking time restrictions

The panel has four panes. You can size the panes by dragging the horizontal and
vertical lines that divide the panel. The left half of the window lists the job stream
run cycles in the top pane, and the job stream jobs in the lower pane.

Activity bars
The right half of the window contains activity bars that represent, on a daily and
hourly scale, the time restrictions defined for every run cycle and job. You can
customize the timescale in the following way:
1. Right-click anywhere along the lower scale. A pop-up menu displays.
2. Move your pointer to Timescale to display available choices.
3. Select the radio button that matches your preference.

Table frame
The left half of the window contains columns that display the following
information:
v A warning button for inconsistencies in time restrictions. This button marks a
run cycle when Tivoli Workload Scheduler for z/OS detects that there are jobs
with time restrictions outside the time restrictions of the run cycle.
v The run cycle name or job identifier.
v The expected start and deadline times of the run cycle or job.
v The expected duration of the job.

Time restrictions
In the upper right pane, the run cycle time restrictions are displayed by a blue bar
that represents the time interval from the start to the deadline of the run cycle. The
deadline is indicated by a vertical black line at the end of the blue bar. You can
change the start and the deadline by dragging the left and right ends of the two
bars, or by dragging the whole activity bar. As you move the bar, an indicator
displays the selected time.

Chapter 37. Managing distributed job streams 237

Checking time restrictions

Note: The run cycle time restrictions inherited from a template are displayed in
read-only mode. To modify them, you have to open the Job Stream Editor
window of the specific template.

Time restrictions for a job are shown by a thick blue bar that represents the time
interval from the start to the deadline of the job, and by a thinner, light blue line
that represents the expected duration. You can move the interval of time between
the start and the deadline times of the job by dragging either end of the thicker bar
(or the whole bar). You can only move the right end of the thinner bar because the
start position is calculated automatically based on the job dependencies. The job
deadline is indicated by a black vertical line. If a job has no specified deadline, the
thick bar is replaced by a vertical stripe indicating the start. You can only move it
forward or backward. To specify a deadline for the job, you have to double-click
the job in the upper left pane and open a Time Restrictions page.

Other tasks
In the Timeline view you can also perform the following activities:
v View the earliest start time of the first job and latest deadline time for the last
job to see the total run time of the job stream.
v Click a run cycle to see how it affects the jobs that start with the job stream. The
activity bars for jobs that start with the job stream change position when you
select different run cycles.
v Open the Time Restrictions page of a Run Cycle Properties panel or of a Job
Properties panel by double-clicking on a run cycle or job in the Table frame.
v Change the earliest start time, duration, and deadline time of a job by moving
different components of the activity bar. In the same way, you can change the
earliest start time and deadline of a run cycle.
v See which jobs start according to the start time of the job stream, and how those
jobs are affected by various rules.

238 IBM Tivoli Workload Scheduler Job Scheduling Console: User’s Guide
Chapter 38. Managing resources
This chapter describes how you manage resources in the database. To display and
modify the properties of a resource, perform the following steps:
1. Run a list of resources that contains the resource you want to manage. See
Chapter 33, “Working with lists,” on page 185.
2. In the list results, double-click the resource you want to modify or right-click
the resource and select Properties from the pop-up menu. The Properties -
Resource in Database panel displays.
3. Make your changes. See “Creating a z/OS resource” on page 107 and “Creating
a distributed resource” on page 111.

© Copyright IBM Corp. 1991, 2006 239

240 IBM Tivoli Workload Scheduler Job Scheduling Console: User’s Guide
Chapter 39. Managing job definitions
This chapter describes how you manage job definitions in the database. It consists
of the following sections:
v “Displaying and modifying job definitions”
v “Displaying job definition details”

Displaying and modifying job definitions

To display a job in the database, perform the following steps:
1. Run a list of jobs that contains the job you want to display. See Chapter 33,
“Working with lists,” on page 185.
2. In the list results, double-click the job you want to display or right-click on the
job and select Properties from the pop-up menu.
This displays the job in the Properties - Job Definition panel.
3. Make your changes. See “Adding a job to a job stream in the Graph View” on
page 222.

Displaying job definition details

To display job details in the database, perform the following steps:
1. Run a list of jobs that contains the job you want to display. See Chapter 33,
“Working with lists,” on page 185.
2. In the list results, right-click the job you want to display and select Job Details
from the pop-up menu.
The Details for Job panel displays.
The panel consists of the following:
Logon The user logon for the workstation where the job runs.
Description A description of the job.
Script File The name of the job script file.
Options The job recovery options. Possible values are:
v Stop
v Continue
v Rerun
Job The name of the recovery job for the job.
Prompt The prompt for the recovery job.
Total Runs The total number of times the job has run.
Aborted Runs The total number of job runs that ended in error.
Successful Runs
The total number of job runs that ended in success.
Total CPU Time
The total CPU time of the job.
Total Elapsed Time
The total elapsed time of the job.

© Copyright IBM Corp. 1991, 2006 241

Displaying job definition details

Normal Elapsed Time

The average elapsed time based on previous runs of the job.
Run Date The date of the last job run.
CPU Time The last minimum and maximum CPU times for the job.
Elapsed Time The last minimum and maximum times for the job.

242 IBM Tivoli Workload Scheduler Job Scheduling Console: User’s Guide
Chapter 40. Managing workstation classes
This chapter describes how you manage workstation classes. You can specify
workstation classes for distributed engines only. To display and modify the
properties of a workstation class, perform the following steps:
1. Run a list of workstation classes that contains the workstation class you want
to manage. See Chapter 33, “Working with lists,” on page 185.
2. In the list results, double-click the workstation class you want to display or
right-click the workstation class and select Properties from the pop-up menu.
The Properties - Workstation Class in Database panel displays.
3. Make your changes. See Chapter 24, “Creating workstation classes,” on page
125.
4. Click OK.

© Copyright IBM Corp. 1991, 2006 243

244 IBM Tivoli Workload Scheduler Job Scheduling Console: User’s Guide
Chapter 41. Managing domains
This chapter describes how you manage domains. You can specify domains for
distributed engines only. To display and modify the properties of a domain,
perform the following steps:
1. Run a list of domains that contains the domain you want to display. See
Chapter 33, “Working with lists,” on page 185.
2. In the list results, double-click the domain you want to display or right-click
the domain and select Properties from the pop-up menu.
The Properties - Domain panel displays.
3. Make your changes. See Chapter 23, “Creating domains,” on page 123.
4. Click OK.

© Copyright IBM Corp. 1991, 2006 245

246 IBM Tivoli Workload Scheduler Job Scheduling Console: User’s Guide
Chapter 42. Managing Windows users
This chapter describes how you manage Windows users. You can specify Windows
users for distributed engines only. To display and modify the properties of a
Windows user, perform the following steps:
1. Run a list of users that contains the Windows user you want to manage. See
Chapter 33, “Working with lists,” on page 185.
2. In the list results, double-click the Windows user you want to display or
right-click on the Windows user and select Properties from the pop-up menu.
The Properties - Windows User panel displays.
3. Make your changes. See Chapter 19, “Creating Windows users,” on page 113

© Copyright IBM Corp. 1991, 2006 247

248 IBM Tivoli Workload Scheduler Job Scheduling Console: User’s Guide
Chapter 43. Managing calendars
This chapter describes how you manage calendars. You can specify calendars for
distributed engines only. To display and modify the properties of a calendar,
perform the following steps:
1. Run a list of calendars that contains the calendar you want to manage. See
Chapter 33, “Working with lists,” on page 185.
2. Right-click the calendar and select Properties from the pop-up menu.
The Properties - Calendar panel displays.
3. Make your changes. See “Creating a calendar” on page 119.

© Copyright IBM Corp. 1991, 2006 249

250 IBM Tivoli Workload Scheduler Job Scheduling Console: User’s Guide
Chapter 44. Managing prompts
This chapter describes how you manage prompts. You can specify prompts for
distributed engines only. To display and modify the properties of a prompt,
perform the following steps:
1. Run a list of prompts that contains the prompt you want to manage. See
Chapter 33, “Working with lists,” on page 185.
2. In the list results, double-click the prompt you want to display or right-click
the prompt and select Properties from the pop-up menu. The Properties -
Prompt panel displays.
3. Make your changes. See Chapter 21, “Creating predefined prompts,” on page
117.

© Copyright IBM Corp. 1991, 2006 251

252 IBM Tivoli Workload Scheduler Job Scheduling Console: User’s Guide
Chapter 45. Managing parameters
This chapter describes how you manage parameters You can specify parameters for
distributed engines only. To display and modify the properties of a parameter,
perform the following steps:
1. Run a list of parameters that contains the parameter you want to manage. See
Chapter 33, “Working with lists,” on page 185.
2. In the list results, double-click the parameter you want to display or right-click
the parameter and select Properties from the pop-up menu. The Properties -
Parameter panel displays.
3. Make your changes. See Chapter 20, “Creating parameters,” on page 115.

© Copyright IBM Corp. 1991, 2006 253

254 IBM Tivoli Workload Scheduler Job Scheduling Console: User’s Guide
Part 7. Managing plans

© Copyright IBM Corp. 1991, 2006 255

256 IBM Tivoli Workload Scheduler Job Scheduling Console: User’s Guide
 Chapter 46. Managing z/OS job stream instances
This chapter explains how to manage z/OS job stream instances in the plan. It is
divided into the following sections:
v “Submitting a job stream”
v “Browsing and modifying job stream instances” on page 259
| v “Rerunning a job stream instance” on page 260
| v “Deleting jobs simultaneously from a job stream instance” on page 260
As well as the actions listed above, you can perform the following actions using
the pop-up menu:
v Set to Complete
v Set to Waiting
v Set All Jobs Monitored
v Unset All Jobs Monitored

Submitting a job stream

To submit an existing job stream into the plan, perform the following steps:
1. In the Actions list, select Submit  Job Stream.
2. Select a z/OS engine.
The Submit Job Stream panel displays.

© Copyright IBM Corp. 1991, 2006 257

Managing z/OS job stream instances in the plan

The panel consists of the following:

Job Stream Name
The name of the job stream. You can use ... (find) to search for and select
the job stream.
Properties
Click Properties to change the properties of the job stream you are
submitting. Properties are:
Priority The priority of the job stream. The lowest priority is 1 and
the highest priority is 9. A job stream with a priority of 3
runs before a job stream with a priority of 1 when they
share resources or workstations. This value can be
overridden by other factors, such as resource and
workstation dependencies. This field does not apply to job
stream templates.
JCL Variable Table
The name of the variable table that the scheduler can use
on the days generated by this run cycle.

258 IBM Tivoli Workload Scheduler Job Scheduling Console: User’s Guide
 Managing z/OS job stream instances in the plan

Owner The name of the person responsible for the job stream.
Owner Description
A brief description of the job stream owner.
Authority Group Name
The name used to generate a RACF resource name for
authority checking.
Job Stream Template
The name of the job stream template to which the job
stream belongs.
Description A brief description of the job stream.
Start The Date and Time when the job stream is scheduled to run. The default
Engine Time Zone is that of the current Job Scheduling Console. You can
modify it in the Settings tab of the engine properties or the Job Scheduling
Console properties panels. After you modified the Properties of a job
stream, you cannot modify the Scheduled Time.
Deadline
The latest Date and Time when the job stream can end. The defaults are
the values in the first run cycle. The default Engine Time Zone is that of
the current Job Scheduling Console. You can modify it in the Settings tab
of the engine properties or Job Scheduling Console properties panels.
Action Type
The type of action for the submit. Possible values are:
Simple Submit
A job stream instance is created and is run when
dependencies are satisfied.
Submit & Hold
A job stream instance is created, all jobs without a
predecessor held so that you can modify the job stream at
a later interval.
Submit & Edit
A job stream instance is created and the Job Stream
Instance Editor displays to edit the job stream instance. The
job stays in hold.
Dependencies Resolution
Dependency resolution for the job stream. Possible values are:
None No dependency resolution is necessary.
Predecessors Predecessor dependencies must be resolved.
Successor Successor dependencies must be resolved.
All Both predecessor and successor dependencies must be
resolved.

Browsing and modifying job stream instances

To browse and modify a job stream instance, perform the following steps:
1. Run a list of job stream instances that contains the job stream instance you
want to modify. See Chapter 33, “Working with lists,” on page 185.
2. Right-click the job stream instance you want to modify and select Properties.
The Properties - Job Stream Instance panel displays.

The panel consists of the following:

v “General page” on page 260

Chapter 46. Managing z/OS job stream instances 259

 Managing z/OS job stream instances in the plan

v “Time Restrictions page”

General page
Most of the fields are read-only. However, you can modify the following settings:
v The name of the table of JCL variables used by the job stream. You can enter or
change the name of a table. Click ... (find) to search for and select the variable
table.
v The priority level. You can raise it or lower it if the instance has not yet started.
v Job stream template. The name of the job stream template, if any, to which the
job stream belongs.

Time Restrictions page

The Time Restrictions page contains the earliest start time and deadline that you
specified when you created the job stream. You can change the following time
restrictions:
Start The actual start time.
Deadline The planned deadline.

Rerunning a job stream instance

To rerun a job stream instance, perform the following steps:
1. Run a list of job stream instances that contains the job stream instance you
want to modify. See Chapter 33, “Working with lists,” on page 185.
2. Right-click the job stream instance and select Rerun from the pop-up menu.
The Job Stream Instance Editor displays.
3. Right-click the job where you want to start the rerun and select Start From. A
panel displays, showing information about the instance.
| 4. Click Use Restart and Cleanup.
5. Select a step from subset of the steps, excluding the one that you selected, in
the following order:
Step Restart Select this to specify at which point in the JCL the job should
restart.
Data Set List Select this to specify with which data set to restart.
Edit JCL Select this to edit the JCL for the job. When you click OK, the
job stream instance is automatically run.
Execute Select this to run the restart and cleanup without specifying
any instructions.

For more information on rerunning jobs, see “Restart and cleanup” on page 293.

| Deleting jobs simultaneously from a job stream instance

| To delete jobs simultaneously from the job stream instance, perform the following
| steps:
| 1. Click the
|

|
| The Explorer View Editor displays.
| 2. In the Table View select the jobs you want to delete.
| 3. Rick-click and select Delete from the pop-up menu.

260 IBM Tivoli Workload Scheduler Job Scheduling Console: User’s Guide
 Managing z/OS job stream instances in the plan

| 4. Click OK in the confirmation window. The jobs are deleted from the job stream
| instance.
| 5. Click Save.

Chapter 46. Managing z/OS job stream instances 261

Managing z/OS job stream instances in the plan

262 IBM Tivoli Workload Scheduler Job Scheduling Console: User’s Guide
 Chapter 47. Managing distributed job stream instances in the
plan
This chapter describes how you manage distributed job stream instances in the
plan. It is divided into the following sections:
v “Submitting a job stream into the plan”
v “Displaying and changing the properties of a job stream instance” on page 264
v “Displaying and changing the follows dependencies of a job stream instance” on
page 271
v “Holding a job stream instance” on page 274
v “Releasing a job stream instance” on page 274
v “Showing predecessors and successors in the Impact View” on page 274
v “Cancelling a job stream instance” on page 275
| v “Performing a cancel pending of a job stream instance” on page 275
v “Changing the limit of a job stream instance” on page 275
v “Changing the priority of a job stream instance” on page 275
v “Releasing a job stream instance from dependencies” on page 276
v “Resubmitting a job stream instance” on page 276
| v “Deleting jobs simultaneously from a job stream instance” on page 276
In addition you can perform the following actions using the pop-up menu:
v Select all Jobs for Monitoring
v Deselect all Jobs for Monitoring

Submitting a job stream into the plan

To submit a job stream that already exists in the database into the plan, perform
the following steps:
1. In the Actions list pane, select Submit.
2. Click Job Stream and select an engine.
The Submit Job Stream into Plan panel displays.

© Copyright IBM Corp. 1991, 2006 263

 Managing distributed job stream instances

The panel consists of following:

Job Stream The name of the job stream you want to submit into the plan.
Workstation Name
The name of the workstation where the job stream runs.
| Scheduled Time
| The time when the job stream is scheduled to run. The default is
| the current time. After you modified the Properties of a job stream,
| you cannot modify the Scheduled Time.
Alias An alias for the job stream.
| Properties Click Properties to specify the properties of the job stream you are
| submitting. The Properties - Job Stream Instance panel displays.
| For information, see “Displaying and changing the properties of a
| job stream instance.” For information about the Predecessors page,
| see “Predecessors page” on page 270.

Displaying and changing the properties of a job stream instance

To display and modify the properties of a job stream instance in the plan, perform
the following steps:
1. Run a list of job stream instances that contains the job stream instance you
want to manage. See Chapter 33, “Working with lists,” on page 185.
2. Right-click the job stream instance and select Properties from the pop-up menu.
3. The Properties - Job Stream Instance panel displays.

The panel consists of the following:

v “General page” on page 265
v “Time Restrictions page” on page 266
v “Resources page” on page 267
v “Prompts page” on page 268
v “Files page” on page 268
v “Predecessors page” on page 270

264 IBM Tivoli Workload Scheduler Job Scheduling Console: User’s Guide
 Changing job stream instance properties

v “Internetwork Predecessors page” on page 270

After you modified the Properties of a job stream instance, you cannot modify the
Scheduled Time.

General page
Use the General page to manage general information for the job stream instance in
the plan.

The page consists of the following:

Note: Most of the information provided in the General page is read-only.

Name The name of the job stream instance.
Workstation Name
The name of the workstation on which the job stream instance is launched.
Original Name
The original name of the job stream when the job stream instance is
submitted with an alias.
Workstation Class Name
The name of the workstation class on which the job stream instance is
launched.
| Limit The number of jobs that can be running at the same time in the job stream.
| Possible values are 0 through 1024. If you specify a job limit of 0, no jobs
| within the job stream instance are launched.
Information
Additional information about the job stream instance.
Production Date
The current date of the production cycle.
Priority
The priority of the job stream. Possible values are:
Hold
Sets the priority to 0.
High
Sets the priority to 100.
Go
Sets the priority to 101.

Possible priority values are 0 through 101, where 101 is the highest priority.
A priority value of zero prevents the job stream from launching. High and
Go jobs are launched as soon as their dependencies are satisfied,
overriding the workstation job limit, but not overriding the job stream job
limit or the workstation job fence.
Carry Forward
This job stream instance is carried forward to the next processing day if it
does not complete before the end of the current production day.
Monitored Job Stream
The job stream instance and every job that it contains are monitored by
Tivoli Business Systems Manager. Changes to the monitored job status are
not displayed in the job stream properties until you close and reopen the
job stream.

Chapter 47. Managing distributed job stream instances in the plan 265
 Changing job stream instance properties

Status The status of the job stream instance. See Appendix D, “Status description
and mapping,” on page 425.
Internal Status
The Tivoli Workload Scheduler internal status of the job stream instance.
See Appendix D, “Status description and mapping,” on page 425.
Number of Jobs
The total number of job instances in the job stream.
Number of Jobs Not Run
The number of job instances in the job stream that have not run.
Number of Jobs Abended
| The number of job instances in the job stream that ended abnormally.
Number of Successful Jobs
The number of job instances in the job stream that ended successfully.
Number of Executing Jobs
The number of job instances in the job stream that are running.
Number of Failed Jobs
The number of job instances in the job stream that have failed to start
running.
Start Time
The time and day the job stream instance started running.
Runtime
The duration of the job stream instance.
Est. Duration
The estimated duration of the job stream instance.

Time Restrictions page

Use the Time Restrictions page to specify time constraints for the job stream
instance.

The page consists of the following:

Start The time that the job stream instance should start. The job stream instance
is not launched before this time.
Specify Date and Time
Select this to specify that entry of a start time is enabled.
Date The start date that the job stream instance should start.
Time The start time that the job stream instance should start.
Latest Start Time
The latest start time by which the job stream instance should start.
Specify Date and Time
Select this to specify that entry of a latest start time is enabled.
Date The latest start date by which the job stream instance should start.
Time The latest start time by which the job stream instance should start.
Action
The action to be performed in case the job stream instance does not start
and the Latest Start Time expires.
Suppress
| Select Suppress to specify that the job stream instance does not start,

266 IBM Tivoli Workload Scheduler Job Scheduling Console: User’s Guide
 Changing job stream instance properties

| even if the not resolved dependency that prevented it from starting is

| corrected, and dependencies are not released. Suppress is the default.
Continue
Select Continue to specify that the job stream instance starts when the
error condition that prevented it from starting is corrected.
Cancel
Select Cancel to specify that the job stream instance is cancelled and
dependencies are released.
Termination Deadline
The time within which a job stream must complete. Jobs or job streams
that have not yet started or that are still running when the deadline time
expires, are considered late in the plan. The termination deadline does not
prevent jobs and job streams from starting.
Specify Date and Time
Select this to specify that entry of a termination deadline is
enabled.
Date The termination deadline date by which the job stream instance
should end.
Time The termination deadline time by which the job stream instance
should end.
Time Zone
The time zone in which you specify time restrictions. This list is available
only if time zone support is enabled. For information about enabling the
time zone, refer to IBM Tivoli Workload Scheduler: Planning and Installation
Guide.

Resources page
Use the Resources page to specify resource dependencies for the job stream
instance.

The page consists of the following:

Resource The name of the resource dependency.
Workstation The workstation on which the resource resides.
Quantity The number of units of the resource that are needed by the job
stream instance to satisfy the dependency.
Available The number of units of the resource that are currently available.
Release Status
The status of the resource dependency. The possible values are:
Not Released
The job stream instance is not released from the resource
dependency.
Released
The job stream instance is released from the resource
dependency.

To release the job instance from the resource dependency, click in

the Status column and select Released from the drop-down menu.

For information about adding a resource dependency, see “Resources page” on

page 151.

Chapter 47. Managing distributed job stream instances in the plan 267
 Changing job stream instance properties

Files page
Use the Files page to specify file dependencies for the job stream instance.

The page consists of the following:

Filename
The name of the file dependency.
Workstation
The workstation on which the file dependency resides.
Qualifiers
The test conditions for the file dependency. See “Files page” on page 152.
Release Status
The status of the file dependency. Possible values are:
Not Released
The job stream instance is not released from the file dependency.
Released
The job stream instance is released from the file dependency.

To release the job instance from the file dependency, click in the Status
column and select Released from the drop-down menu.
Internal Status
The internal status of the file dependency. Possible values are:
Not Checked
The file dependency has not been checked.
Checking
The file dependency is being checked.
Exists
The file dependency is satisfied.
Does Not Exist
The file dependency is not satisfied.

For information about adding a file dependency, see “Files page” on page 152.

| Prompts page
| Use the Prompts page to set ad hoc or predefined prompt dependencies for the job
| stream instance.

| To add an ad hoc prompt for the job stream instance, perform the following steps:
| 1. From the drop-down list, select Ad Hoc Prompt.

| 2. Click .
| 3. Double-click in the Message Text cell and type the text of the prompt. The
| default behavior of a prompt is to display a message and wait for a reply.
| Based on the character preceding the text, the prompt can behave differently:
| v If the text begins with a colon (:), the prompt displays, but no reply is
| required to continue processing.
| v If the text begins with an exclamation mark (!), the prompt displays, but it is
| not recorded in the log file.
| Refer to the IBM Tivoli Workload Scheduler: Reference Manual for a detailed
| explanation on how to specify the text of a prompt.
| You can include one or more scheduler parameters as part or all of the text
| string. To use a parameter, place its name between carets (^) . In the row you

268 IBM Tivoli Workload Scheduler Job Scheduling Console: User’s Guide
 Changing job stream instance properties

| can see also the information described in the list below. This information is
| filled in when the job stream instance is included in the plan.
| Number
| The number of the prompt dependency.
| Release Status
| The status of the prompt dependency. Possible values are:
| Not Released
| The job stream instance is not released from the prompt
| dependency.
| Released
| The job stream instance is released from the prompt dependency.
| Internal Status
| The internal status of the prompt dependency. Possible values are:
| Not Asked
| The prompt has not been asked.
| Asked
| The prompt has been asked, but no response has been received.
| Answered Yes
| The prompt has been answered affirmatively.
| Answered No
| The prompt has been answered negatively.
| Reply The reply to the prompt dependency. To reply to a prompt that is in the
| ASKED state, click in this column and select Yes or No from the
| drop-down menu.

| To add a predefined prompt for the job stream instance, perform the following
| steps:
| 1. From the drop-down list, select Predefined Prompt.

| 2. Click .
| 3. Type the name of the prompt in the Name cell or click ... (find) to search for
| and select the prompt. The following information displays:
| Message Text
| The text of the prompt.
| Number
| The number of the prompt dependency.
| Release Status
| The status of the prompt dependency. Possible values are:
| Not Released
| The job stream instance is not released from the prompt
| dependency.
| Released
| The job stream instance is released from the prompt dependency.
| Internal Status
| The internal status of the prompt dependency. Possible values are:
| Not Asked
| The prompt has not been asked.
| Asked
| The prompt has been asked, but no response has been received.
| Answered Yes
| The prompt has been answered affirmatively.

Chapter 47. Managing distributed job stream instances in the plan 269
 Changing job stream instance properties

| Answered No
| The prompt has been answered negatively.
| Reply The reply to the prompt dependency. To reply to a prompt that is in the
| ASKED state, click in this column and select Yes or No from the
| drop-down menu.

| To remove a prompt dependency for the job stream instance, select the prompt row

| in the list and click .

Predecessors page
Use the Predecessors page to add predecessor dependencies to the job stream
instance.

The page consists of the following:

Job Stream
The name of the predecessor job stream. Click ... (find) to search for and
select a job stream.
Job The name of job in the predecessor job stream.
Workstation
The name of the workstation of the predecessor job stream.
Scheduled Time
The time when the predecessor job stream is scheduled to run. The default
is the current time.
Release Status
The status of the predecessor job or job stream.
Internal Status
The Tivoli Workload Scheduler internal status of the predecessor job or job
stream.
For more information on job or job stream status refer to Appendix D,
“Status description and mapping,” on page 425.

To add an predecessor dependency to a job stream instance, perform the following

steps:

1. Click .
2. In the Job Stream and Job, cells click ... (find) to search for and select a job
stream and a job. To insert this data in the row you are working on, click
Apply in the Find panel.

| Select a row and click to remove a row from the list.

For information about adding predecessor dependencies, see Chapter 37,

“Managing distributed job streams,” on page 219.

| Internetwork Predecessors page

| Use the Internetwork Predecessors page to add internetwork dependencies to the
| job stream instance.

| The page consists of the following:

270 IBM Tivoli Workload Scheduler Job Scheduling Console: User’s Guide
 Changing job stream instance properties

| Network Agent
| The network agent workstation to which the predecessor belongs.
| Dependency
| A dependency on the job or job stream predecessor in the format
| workstation#jobstream.job. The maximum length is 16 characters for
| workstation, 16 characters for the job stream, and 40 characters for the job.
| Release Status
| The release status of the internetwork predecessors. The possible states are:
| v Released
| v Not Released
| To release the job stream instance from the internetwork predecessor
| dependency, click in the Release Status column and select Released from
| the drop-down menu.
| Internal Status
| The Tivoli Workload Scheduler internal status of the predecessor job or job
| stream. See Appendix D, “Status description and mapping,” on page 425.

| To add an internetwork predecessor dependency to a job stream instance, perform

| the following steps:

| 1. Click .
| 2. In the Network Agent cell click ... (find) to search for and select an agent.
| 3. Double-click in the Dependency cell and type the dependency.

| Select a row and click to remove a row from the list.

| For information about adding internetwork dependencies to a job stream, see

| Chapter 37, “Managing distributed job streams,” on page 219.

Displaying and changing the follows dependencies of a job stream

instance
To display the follows dependencies of a job stream instance, perform the
following steps:
1. Run a list that contains the job stream instance you want to manage. See
Chapter 33, “Working with lists,” on page 185.
2. Right-click the job stream instance in the list and select Dependencies.
The Dependencies - Job Stream Instance panel displays.

Chapter 47. Managing distributed job stream instances in the plan 271
Displaying and modifying dependencies

The panel consists of the following:

v “Predecessors page”
v “Internetwork Predecessors page” on page 273
v “Successors page” on page 273

Predecessors page
Use the Predecessors page to add predecessors to the job stream instance.

The page consists of the following:

Job Stream
The name of a predecessor job stream instance.
Job The name of the job instance contained in the job stream instance.
Workstation
The workstation of the predecessor job or job stream instance.
Released Status
The status of the predecessor dependency. The possible values are:
v Released
v Not Released
To release the job stream instance from the predecessor dependency, click
in the Release Status column and select Released from the drop-down
menu.
Internal Status
The Tivoli Workload Scheduler internal status of the predecessor job or job
stream instance. See Appendix D, “Status description and mapping,” on
page 425.
Scheduled Time
The date and time when the job stream is scheduled to run.

To add an predecessor dependency to a job stream instance, perform the following

steps:

1. Click .
2. In the Job Stream and Job, cells click ... (find) to search for and select a job
stream and a job. To insert this data in the row you are working on, click
Apply in the Find panel.

272 IBM Tivoli Workload Scheduler Job Scheduling Console: User’s Guide
 Displaying and modifying dependencies

| Select a row and click to remove a row from the list.

For information about adding predecessor dependencies to a job stream, see

Chapter 37, “Managing distributed job streams,” on page 219.

Internetwork Predecessors page

Use the Internetwork Predecessors page to add internetwork dependencies to the
job stream instance.

The page consists of the following:

Network Agent
The network agent workstation to which the predecessor belongs.
Dependency
A dependency on the job or job stream predecessor in the format
workstation#jobstream.job. The maximum length 16 characters for
workstation, 16 characters for the job stream, and 40 characters for the job.
Release Status
The release status of the internetwork predecessors. The possible states are:
v Released
v Not Released
To release the job stream instance from the internetwork predecessor
dependency, click in the Release Status column and select Released from
the drop-down menu.
Internal Status
The Tivoli Workload Scheduler internal status of the predecessor job or job
stream. See Appendix D, “Status description and mapping,” on page 425.

| To add an internetwork predecessor dependency to a job instance, perform the

| following steps:

| 1. Click .
| 2. In the Network Agent cell click ... (find) to search for and select an agent.
| 3. Double-click in the Dependency cell and type the dependency.

| Select a row and click to remove a row from the list.

For information about adding internetwork dependencies to a job stream, see

Chapter 37, “Managing distributed job streams,” on page 219.

Successors page
Use the Successors page to view successor information for the job stream instance.
Successors are jobs or job streams that have the job stream instance as predecessor.

The page consists of the following:

Job Stream Name
The name of the job stream to which the successor belongs.
Job The name of the successor job.

Chapter 47. Managing distributed job stream instances in the plan 273
Displaying and modifying dependencies

Workstation
The name of workstation to which the successor belongs.
Status The release status of the Internetwork successors. The possible states are:
v Released
v Not Released
To release the job stream instance from the successor dependency, click in
the Release Status column and select Released from the drop-down menu.
Internal Status
The Tivoli Workload Scheduler internal status of the successor job. See
Appendix D, “Status description and mapping,” on page 425.
Scheduled Time
The date and time when the job stream is scheduled to run.

Holding a job stream instance

Changing a job stream instance to Hold sets the priority of the job instance to zero.
Use Release to change the priority back to its original level at the start of the
processing day.

To change a job stream instance to Hold:

1. Run a job stream instance list that contains the job stream instance you want to
hold. See Chapter 33, “Working with lists,” on page 185.
2. Right-click the job stream instance you want to hold.
3. Select Hold from the pop-up menu.

Releasing a job stream instance

Release changes the status of a job stream instance from Hold. Release sets the
priority back to the original setting at the start of the processing day.

To release a job stream instance, perform the following steps:

1. Run a job stream instance list that contains the job stream instance you want to
release. See Chapter 33, “Working with lists,” on page 185.
2. In the list results, right-click the job stream instance you want to release.
3. Select Release from the pop-up menu and click Yes.

Showing predecessors and successors in the Impact View

To show the predecessors of a job stream instance or its successors, right-click a job
stream instance and select Impact View from the pop-up menu, then either
Predecessors or Successors. The Impact View panel displays.

You can define the level of dependencies displayed in the Impact View by
choosing Dependency Level in the Layout menu. In the Dependency Level panel,
type a number ranging from 1 to 5 and click OK. The predecessors or successors
up to the specified level are displayed in the Impact View.

Use Predecessors/Successors to toggle the view.

274 IBM Tivoli Workload Scheduler Job Scheduling Console: User’s Guide
 Displaying and modifying dependencies

Cancelling a job stream instance

Cancelling a job stream instance in the plan prevents the job stream instance from
running. A cancelled job stream instance can be resubmitted using an alias. For
more information, see “Resubmitting a job stream instance” on page 276.

To cancel a job stream instance, perform the following steps:

1. Run a job stream instance list that contains the job stream instance you want to
cancel. See Chapter 33, “Working with lists,” on page 185.
2. In the list results, right-click the job stream instance.
3. Select Cancel from the pop-up menu.

| Performing a cancel pending of a job stream instance

| Use this function to cancel a job stream instance when all its dependencies are
| resolved. To cancel a job stream instance, perform the following steps:
| 1. Run a list of job stream instances that contains the job stream instance you
| want to cancel. See Chapter 33, “Working with lists,” on page 185.
| 2. Right-click the job stream instance and select Cancel Pending from the pop-up
| menu.
| If the job stream has not been launched, cancellation is deferred until all of the
| dependencies, including an at time, are resolved. When all the dependencies
| are resolved, the job stream is cancelled and any jobs or job streams that are
| dependent on the cancelled job stream are released from the dependency. If the
| job stream has been launched, the job stream is cancelled when it completes
| and is moved to its final status.

Changing the limit of a job stream instance

To change the limit of a job stream instance in the plan, perform the following
steps:
1. Run a job stream instance list that contains the job stream instance you want to
modify. See Chapter 33, “Working with lists,” on page 185.
2. In the list results, right-click the job stream instance.
3. Select Limit from the pop-up menu.
The Change Limit - Job Stream Instance panel displays.
4. Specify a new job limit in the New Limit field.

Changing the priority of a job stream instance

To change the priority of a job stream instance, perform the following steps:
1. Run a job stream instance list that contains the job stream you want to modify.
See Chapter 33, “Working with lists,” on page 185.
2. In the list results, right-click the job stream instance.
3. Select Priority from the pop-up menu.
The Change Priority - Job Stream Instance panel displays.
4. Specify a new priority.

Note: If a single job stream instance is selected, Default sets the priority to the
original value of the job stream instance at the start of the processing
day. If multiple job stream instances are selected, the priority of each job
stream instance is set back to what it was at start of the processing day.

Chapter 47. Managing distributed job stream instances in the plan 275
 Displaying and modifying dependencies

Releasing a job stream instance from dependencies

Releasing a job stream instance from its dependencies removes dependencies on
the following objects:
v Time restrictions
| v Predecessor jobs and job streams included internetwork dependencies
v Resources
v Files
v Prompts
You can release job stream instances that are in the waiting state.

To release a job stream instance from its dependencies, perform the following
steps:
1. Run a job stream instance list that contains the job stream you want to release.
See Chapter 33, “Working with lists,” on page 185.
2. In the list results, right-click the job stream instance.
3. Select Release All Dependencies from the pop-up menu.

Resubmitting a job stream instance

To resubmit a job stream instance in the plan, perform the following steps:
1. Run a job stream instance list that contains the job stream instance you want to
submit. See Chapter 33, “Working with lists,” on page 185.
2. In the list results, right-click the job stream instance.
3. Select Re-Submit from the pop-up menu. The Re-Submit Job Stream Instance
panel displays.
4. Specify an alias for the resubmitted job stream instance in Alias. If you do not
specify an alias, a name is generated by Tivoli Workload Scheduler. The
instance starts with the first six characters of the original job stream instance
name followed by ten random numbers.
When the job stream definition is not found in the plan, it is loaded from the
database.

| Deleting jobs simultaneously from a job stream instance

| To delete jobs simultaneously from the job stream instance, perform the following
| steps:
| 1. Run a list that contains the relative job stream. See Chapter 33, “Working with
| lists,” on page 185. 2.
| 2. Double-click the job stream. The Job Stream Editor displays.
| 3. Click the
|

|
| The Explorer View Editor displays.
| 4. In the Table View select the jobs you want to delete.
| 5. Rick-click and select Delete from the pop-up menu.
| 6. Click OK in the confirmation window. The jobs are deleted from the job stream
| instance.
| 7. Click Save.

276 IBM Tivoli Workload Scheduler Job Scheduling Console: User’s Guide
 Chapter 48. Managing z/OS job instances
This section describes how to manage z/OS job instances in the plan. It is divided
into the following sections:
v “Browsing and modifying z/OS job instances”
v “Browsing and modifying job instance dependencies” on page 285
v “Changing time restrictions in the Timeline View” on page 287
| v “Deleting a job instance” on page 288
| v “Holding a job instance” on page 289
| v “Releasing a job instance” on page 289
v “Showing dependencies in the Impact View” on page 290
v “Browsing the job log” on page 291
v “Setting a job instance to a non operational state (NOP) in the plan” on page 291
v “Restoring a job instance to operational in the plan (UN-NOP)” on page 291
| v “Killing a job instance running on a fault-tolerant agent” on page 291
v “Running a job instance immediately” on page 292
v “Changing the status of a job instance” on page 292
v “Editing JCL” on page 292
v “Viewing operator instructions” on page 292
v “Modifying job setup” on page 292
v “Restart and cleanup” on page 293
v “Recovery information” on page 294
v “Automatic recovery” on page 294
| v “Critical Path” on page 295

Browsing and modifying z/OS job instances

To browse or modify a job instance, perform the following steps:
1. Run a list of job instances in the plan. See Chapter 33, “Working with lists,” on
page 185.
2. Right-click on one of the job instances.
3. Select Properties from the pop-up menu.
The Properties - Job Instance panel displays.

The panel consists of the following:

v “General page” on page 278
v “Task page” on page 279
v “Time Restrictions page” on page 279
v “Details page” on page 280
v “Options page” on page 281
v “Resources page” on page 282
v “Automation page” on page 284

© Copyright IBM Corp. 1991, 2006 277

 Browsing and modifying z/OS job instances in the plan

General page
Use the General page to view general information about the job instance in the
plan.

The page consists of the following:

Note: Most of the data on this page is read-only.

Identifier The job identifier.
Workstation The name of the workstation running the job.
Belongs To Job Stream
The name of the job stream to which the job belongs.
| Occurrence Token
| The token is a unique 16-character hexadecimal string assigned to
| the job stream by the scheduler.
JES Job Number
The job number assigned by JES.
Description A description of the job. The information in this field can be
modified.
Authority group
The name of the authority group of the job stream.
Priority The priority level of the job stream to which the job belongs.
Started The actual date the job instance started.
Runtime The time it took the instance to run if completed.
Status: Internal status
The status of the job instance. Use the Set Status menu option to
change the status.
Status: Status details
Additional information about the status of the job instance, where
available.
Status: Error code
The code with which the instance ended in error, when applicable.
Start time: Earliest
The earliest time at which the job instance can start. This value is
produced based on the relative earliest start time that you specified
when you created the job.
Start time: Planned
The estimated start time, based on the durations of predecessors,
that Tivoli Workload Scheduler for z/OS evaluates when the job
instance starts.
Start time: Latest
The latest that the job can start without making successor jobs and
the job stream miss their deadline.
Start time: Actual
The time the job started.

278 IBM Tivoli Workload Scheduler Job Scheduling Console: User’s Guide
 Browsing and modifying z/OS job instances in the plan

Task page
Use the Task page to view task information about the job instance in the plan.

The page consists of the following:

Task Name The name of the task associated with the job instance.
Form Number The printer form number if the job is a printer job.
Job Class A single letter from A-Z that matches the host job class.
Extended Task Name
The job instance descriptive name.
| Scheduling Environment Name
| A descriptive name of the WorkLoad Manager scheduling
| environment associated with the job. The maximum length is 16
| characters.

Time Restrictions page

Use the Time Restrictions page to view time restrictions information about the job
instance in the plan.

The page consists of the following:

Start The time at which the job can start. Possible values are:
No Restrictions
The job runs as soon as all dependencies are met.
No time restrictions can result in more efficient
processing for certain jobs when extending a plan.

Note: This choice is not valid if you selected

Cancel if Late in the “General page” on
page 139.
Follow Job Stream Rules
The earliest time the job can start is when the job
stream starts. This is the default. This option is not
valid if you clear No Restrictions.
Specify Earliest Start Time
The date and time before which the job does not
start:
Date Type the date or select a date from
the calendar.
Time Type a time in a format specific to
your locale.
Deadline The latest time that the job can end. Select Specify to enable the
time fields. Possible values are:
At Type a time according to your locale settings. For
example type 12:00 if you want the job to end
before noon.
Delay for days
Type a number of days to defer the start time. For
example if you type 3 the job must end three days
after the time you specify in At.
Duration How long the job is expected to run, in hours, minutes, and
seconds. The maximum is 99:59:01.

Chapter 48. Managing z/OS job instances 279

 Browsing and modifying z/OS job instances in the plan

Details page
Use the Details page to view details of the job instance in the plan.

The page consists of the following:

CleanUp Status
The status code of the data set cleanup action. Possible values are:
v Completed
v Error ended
If no status displays, either data set cleanup has been reset or has
not yet started.
Latest Out Passed
Indicates whether a job has not yet started and the latest start time
has passed.
JCL Preparation
Indicates whether the job instance requires JCL preparation.
Urgent Indicates whether the job instance requires JCL preparation. This
happens if its priority is 9, or it is not yet started, or both, and the
conditions for Latest Out Passed are true.
Monitored Job
Whether the job is monitored by Tivoli Business Systems Manager.
Changes to the monitored job status are not displayed in the job
stream properties until you close and reopen the job stream.
Centralized Script
Whether the script associated to the job resides on the domain
master or on the local machine.
| Critical Job Whether the job is defined as a critical job. If a critical job runs
| late, it is eligible for Tivoli Workload Scheduler internal or for
| Workload Manager (WLM) service class promotion. If you are
| using Tivoli Workload Scheduler version 8.3, possible values are:
| No The job is not on the critical path.
| Critical Path Target
| The job is on the critical path, and must be
| managed by the Tivoli Workload Scheduler internal
| critical path prioritizing algorithms.
| WLM The job is on the critical path, and must be
| managed by Workload Manager (WLM). If you
| select this option, also supply the WLM Policy and
| Class.
On Critical Path in Job Stream
Indicates whether the job instance is on the internal critical path
for the job stream.
WLM Policy The policy applied for WLM service class promotion if the job is
late. Select Critical Job to enable WLM Policy. Possible values are:
Conditional
The scheduler uses an algorithm to determine whether to apply
the Deadline or the Latest start option.
Deadline
The scheduler intervenes if the job runs beyond the deadline.

280 IBM Tivoli Workload Scheduler Job Scheduling Console: User’s Guide
 Browsing and modifying z/OS job instances in the plan

Long Duration
The scheduler intervenes if the job takes longer than it should
as compared to the statistics that it keeps.
Latest Start
The scheduler intervenes immediately if the job starts after the
latest start time.
| WLM Class The class applied for WLM service class promotion if the job is
| late. Select the value WLM for Critical Job to enable WLM Class.
Planned Duration
The estimated processing time for the job.
Intermediate Start
If the job is interrupted, the time it restarts.
Actual End The time the job instance ended.
Transport Time
The time needed for data to be transported from one workstation
to another between jobs.
Predecessors The number of jobs whose completion is necessary for this instance
to run. See “Predecessors page” on page 286.
Completed Predecessors
The number of predecessors that have completed.
Successors The number of jobs that depend on the completion of this instance.
See “Successors page” on page 286.
Logical Resources
The number of logical resources reserved for the job.

Options page
Use the Options page to view option information about the job instance in the
plan.

The page consists of the following:

Auto Hold Release
Whether the instance should be automatically released.
Cancel if Late
Whether the instance should be cancelled automatically if late.
Auto Error Completion
Whether the instance should be automatically completed when it ends in
error.
Auto Job Submission
Whether the instance should be submitted automatically.
Highest Acceptable Return Code
The highest acceptable return code for the instance.
User Data
Indicates user data is available for editing.
Deadline WTO
Whether a write-to-operator message should be sent when the job misses
its deadline.

Chapter 48. Managing z/OS job instances 281

 Browsing and modifying z/OS job instances in the plan

Restart and CleanUp

Whether Restart and CleanUp is used if the job instance ends in error.
Possible values are:
v None
v Immediate
v Automatic
v Manual
Expanded JCL
Indicates that the JCL used for step-level restarts and job reruns is the JCL
image captured from the JESJCL sysout data set.
Use Sysout
Indicates that the sysout data sets are used for job restarts.
Restartable
Whether the instance should be made restartable. Possible values are:
v Yes
v No
v Default
Default maintains the original job definition value.
Reroutable
Whether the instance should be made reroutable. Possible values are:
v Yes
v No
v Default
Default maintains the original job definition value.

Resources page
Use the Resources page to define the parallel servers and the logical and
workstation resources that the job uses.

The page gives you access to two types of resources, as follows:

Target Resources
Set the quantity of resources that the workstation needs to run the
job. You cannot change the target resources listed, only the
quantity of them required.
To set the quantity of target resources, perform the following steps:
| 1. If Logical Resources is shown, click its pull-down icon and
| select Target Resources.
2. Double-click each cell in the Quantity column to edit the
amount of resources (Resource 1 and Resource 2) needed by the
job.
Logical Resources
Set the logical resources, such as printers, tapes, or disk space that
are needed to run the job. You can add and remove logical
resources, as follows:
Resource
For target resources this is an information field that lists
the target resources. The Parallel Servers target resource
represents the number of processes that can be run
concurrently by the workstation. For logical resources this

282 IBM Tivoli Workload Scheduler Job Scheduling Console: User’s Guide
 Browsing and modifying z/OS job instances in the plan

is an alphanumeric name for the resource. Click ... (find) to

search for and select a resource. The maximum length is 44
characters.
Quantity
The quantity of the resource needed to run the job.
Access Type
For logical resources, the type of access for the resource.
Possible values are:
Shared Other jobs use the resource.
Exclusive Only the current job uses the resource.
Keep on Error
For logical resources, the action to take on the resource if
the job ends in error. Possible values are:
Yes The resource is reserved for the job when
an error occurs.
No The resource is released from the job when
an error occurs.
Default The default option specified for the
ONERROR keyword in the RESOPTS
statement is used.
| Available on complete
| The action to take when the job finishes successfully
| (complete status). Possible values are:
| Available Switch the global availability status of the
| resource to yes when a job that uses this
| resource completes successfully.
| Unavailable Switch the global availability status of the
| resource to no when a job that uses this
| resource completes successfully.
| Automatically reset
| Switch the global availability status of the
| resource to blank when a job that uses this
| resource completes successfully.
| Assume system default
| Switch the global availability status and
| quantity of the resource to the default
| value when a job that uses this resource
| completes successfully. The system will
| check for the following, in order:
| 1. If the Default: Is Available field (see
| below) has been set for the resource, it
| makes the resource available, using the
| Default: Quantity value
| 2. If Default: Is Available is not set, the
| system uses the value in the
| ONCOMPLETE keyword of the
| RESOPTS statement to determine the
| availability status.

Chapter 48. Managing z/OS job instances 283

 Browsing and modifying z/OS job instances in the plan

To set logical resources, perform the following steps:

| 1. If Target Resources is shown, click its pull-down icon and
| select Logical Resources.

2. Click the to add a row to the table.

3. Type the name of the resource or click ... (find) to search and
select a resource.

| Automation page
| Use the Automation page for jobs that are to be run on Tivoli System Automation
| for z/OS. These jobs must be defined on workstations with the automatic attribute
| set.

| The page consists of the following:

| Command Text
| The text string of the command to be run by Tivoli System
| Automation for z/OS. The string can contain Tivoli Workload
| Scheduler variables; before the operations are passed to Tivoli
| System Automation for z/OS, Tivoli Workload Scheduler for z/OS
| performs the variable substitution processing. If any error occurs
| during this phase the job state is set to E with error code OJCV.
| Completion Info
| A string (maximum 64 characters) containing one or more of the
| following parameters, separated by a comma.
| Maximum wait time
| The maximum wait time (optional). Specify the
| longest interval of time that the command is
| expected to take to complete under normal
| operating conditions, plus a small margin to cover
| items like minor delays and heavy network traffic.
| If this value is specified, and the command does
| not complete within the indicated time interval,
| Tivoli System Automation for z/OS returns an
| error to Tivoli Workload Scheduler for z/OS.

| Note: In the case of an INGREQ command, the

| command is considered complete when the
| specified resource has reached the requested
| state or is already in the requested state. If
| more than one resource is specified in the
| INGREQ command, all resources must be in
| the requested state before the command is
| considered complete.

| Various time formats are accepted. See the Tivoli

| System Automation for z/OS documentation for
| details.
| Maximum return code accepted as OK
| The highest return code value from Tivoli System
| Automation for z/OS that Tivoli Workload
| Scheduler for z/OS must treat as successful
| (optional). The default is 0.

284 IBM Tivoli Workload Scheduler Job Scheduling Console: User’s Guide
 Browsing and modifying z/OS job instances in the plan

| Completion checking routine

| The name of your completion checking routine
| (optional).
| If this value is specified, the completion checking
| routine is responsible for ensuring that the
| command achieved the expected results before
| posting the operation complete. This allows you to
| perform commands that are independent of a
| Tivoli System Automation for z/OS controlled
| resource, for example a VTAM major node. In this
| case, the command could be the activation of the
| VTAM major node, while the checking routine
| could “ping” the target node before posting the
| OPC operation complete by means of the
| OPCAPOST command. If Maximum wait time is
| also supplied, it can be passed to the checking
| routine, allowing the checking routine to return an
| error if the command does achieve the expected
| result within the indicated time.
| The full syntax of the Completion Info string is as follows:
| [maximum_wait_time],
| [maximum_return_code],
| [completion_checking_routine]

| However, note that trailing commas must not be supplied. For

| example, to specify just the first two parameters, the field might
| look like this:
| 2:30,3

| To specify just the third parameter, the field might look like this:
| ,,CHKEND

| To not supply any of the parameters, leave the whole Completion

| Info field blank.
| Automated Function
| Specify the automated function (optional). When specified, the
| command is run on the NetView task associated with the indicated
| automated function in Tivoli System Automation for z/OS. You can
| use this parameter to serialize the commands. If this parameter is
| not specified, the command is run by any of the locally available
| NetView tasks.
| Security Element
| A token used for security tracking of the operation in the Tivoli
| System Automation for z/OS AOFEXC20 exit routine (optional).
| Use it as an alternative to, or in conjunction with the job name.

Browsing and modifying job instance dependencies

To browse and modify job instance dependencies, perform the following steps:
1. Display a job instance list that contains the instance you want to modify. See
Chapter 33, “Working with lists,” on page 185.
2. Right-click on the job instance and select Dependencies from the pop-up menu.

Chapter 48. Managing z/OS job instances 285

Browsing and modifying z/OS job instance dependencies in the plan

The Dependencies - Job Instance panel displays.

The panel consists of the following:

v “Predecessors page”
v “Successors page”

Predecessors page
Use the Predecessors page to view and modify information about the job instances
that must complete before this instance can start running.

The page consists of the following:

Job Stream Name
The name of the job stream to which the predecessor belongs, if it is
external.
Job Stream Start
The start time of the job stream to which the predecessor belongs.
Task Name
The name of the task associated with the predecessor job.
Identifier
The identifier of the predecessor job.
Extended Task Name
Any extension to the job name.
On Critical Path
Whether the predecessor is on the critical path.

To add a predecessor, perform the following steps:

1. Click .
2. Click ... (find) to search for the Job Stream Name, Identifier, or Job Stream
Start. To insert this data in the row you are working on, click Apply in the
Find Job Instance panel.
3. Double-click each table cell to modify the values.
To remove a dependency, select the predecessor and click Delete From Table.

Successors page
Use the Successors page to view information about the job instances that depend
on completion of this instance before they can start running.

The page consists of the following:

Job Stream Name
The name of the job stream to which the successor belongs, if it is external.
Job Stream Start
The start time of the job stream to which the successor belongs.
Task Name
The name of the task associated with the successor job.
Identifier
The identifier of the successor job.

286 IBM Tivoli Workload Scheduler Job Scheduling Console: User’s Guide
 Browsing and modifying z/OS job instance dependencies in the plan

Extended Task Name

Any extension to the job name.
On Critical Path
Whether the successor job is on the critical path

To add a successor, perform the following steps:

1. Click .
2. Click ... (find) to search for the Job Stream Name, Identifier, or Job Stream
Start. To insert this data in the row you are working on, click Apply in the
Find Job Instance panel.
3. Double-click each table cell to modify the values.
To remove a dependency, select the successor and click Delete From Table.

Click Apply to save the changes and keep the panel open, click OK to save any
changes you made and close the panel.

Changing time restrictions in the Timeline View

This section describes how you make changes to time restrictions in the Timeline
View. It consists of the following subsections:
v “Elements of the Timeline View”
v “Rescheduling a job instance” on page 288
v “Rescheduling a job instance start time” on page 288
v “Rescheduling a job instance deadline time” on page 288

Elements of the Timeline View

The left-hand pane of the Timeline View displays the following job instance
details:
Name The job name.
Status The current status.
Started The actual start time.
Runtime The actual duration.
Start at The planned start time.
Duration The planned duration.
Deadline The planned deadline.

The right-hand pane has activity bars that show the runtime of a job instance in
terms of start, duration, and deadline times.

The deadline is indicated by a black stripe at the end of the blue activity bar. The
activity bar represents the time difference between the earliest planned start and
the planned end that were specified as time restrictions for the job. A pale blue bar
represents the duration of the job. It turns red if the duration exceeds the deadline
and it becomes diamond shaped if the duration is zero. A black line represents the
actual runtime of the job instance.

By moving components of the activity bars, you can change the time restrictions of
each instance and view the results of your changes.

Chapter 48. Managing z/OS job instances 287

Changing z/OS job instance time restrictions in the Timeline View

Rescheduling a job instance

To reschedule a job instance in ready status, perform the following steps:
1. Move the activity bar by positioning the mouse pointer inside the bar. When
the pointer becomes cross-shaped, hold down the left mouse button while
moving the bar in either direction.
2. When you find the position you want, release the mouse button. The Properties
- Job Instance Properties Time Restrictions page displays.
3. Click OK to save the new settings. The activity bar is set on the new position.

Rescheduling a job instance start time

To reschedule a job instance start time, perform the following steps:
1. Position the mouse pointer on the left end of the bar. When the pointer
becomes a double-headed arrow, hold down the left mouse button while
moving the end of the bar.
2. When you find the position you want, release the mouse button. The Properties
- Job Instance Properties Time Restrictions tab displays, showing the new start
time.
3. Click OK to save the new settings. The left end of the activity bar is set in the
new position.

Rescheduling a job instance deadline time

To reschedule the deadline time, perform the following steps:
1. Position the mouse pointer on the right end of the bar. When the pointer
becomes a double arrow, hold down the left mouse button while moving the
end of the bar.
2. When you find the position you want, release the mouse button. The Properties
- Job Instance Time Restrictions tab displays, showing the new deadline time.
3. Click OK to save the new settings. The right end of the activity bar is set in the
new position.

Deleting a job instance

You can delete a single job instance or delete all jobs in a group of job instances. To
delete a single job instance see “Deleting objects from a list” on page 49, to delete
all jobs in a group of job instances follow the procedure described in the section
below:

Deleting all job instances

To delete all jobs in a group of job instances in the Timeline View, perform the
following steps:
1. Run a list of job instances that contains the instances you want to delete. See
Chapter 33, “Working with lists,” on page 185

2. Click to switch to the Timeline View.

3. Right-click the arrow next to the job instance group.
4. Click Delete All.

288 IBM Tivoli Workload Scheduler Job Scheduling Console: User’s Guide
 Holding a job instance

Holding a job instance

This section describes how to hold job instances. It consists of the following
subsections:
v “Holding a single job instance”
v “Holding all job instances”

Holding a single job instance

To change a single job instance to Hold, perform the following steps:
1. Run a list of job instances that contains the job you want to hold. See
Chapter 33, “Working with lists,” on page 185.
2. Right-click the job instance and select Hold from the pop-up menu.

Holding all job instances

To hold all jobs in a group of job instances in the Timeline View, perform the
following steps:
1. Run a list of job instances that contains the instances you want to hold. See
Chapter 33, “Working with lists,” on page 185

2. Click to switch to the Timeline View.

3. Right-click the arrow next to the job instance group.
4. Click Hold All.

Releasing a job instance

This section describes how to release a job instance that is in Hold, returning the
job priority to its start of production day state. It consists of the following
subsections:
v “Releasing a single job instance”
v “Releasing all job instances”

Note: Do not confuse Release with Release All Dependencies. It has no effect on
job dependencies.

Releasing a single job instance

To change a single job instance to Release, perform the following steps:
1. Run a list of job instances that contains the job instance you want to release.
See Chapter 33, “Working with lists,” on page 185.
2. Right-click the job instance you want release.
3. Select Release from the pop-up menu.

Releasing all job instances

To release all jobs in a group of job instances, perform the following steps:
1. Run the list of job instances. See Chapter 33, “Working with lists,” on page 185

2. Click to switch to the Timeline View.

3. Right-click the arrow next to the job instance group.
4. Click Release All.

Chapter 48. Managing z/OS job instances 289

 Viewing z/OS job instance dependencies in the Impact View

Showing dependencies in the Impact View

| To show job instance predecessors or successors in the Impact View, perform the
| following steps:
| 1. Display a job instance list. See Chapter 33, “Working with lists,” on page 185.
| 2. Right-click on the job instance you want to view.
| 3. Select Impact View from the pop-up menu.
| 4. Select either Predecessors or Successors from the pop-up menu.
| The Impact View panel displays.
|

| The Layout menu contains Direction and Dependency Level. Direction enables
you to graphically show the job instances and their dependencies in the panel you
choose.

Dependency Level helps you to define the level of dependencies displayed in the
Impact View. In the Dependency Level panel, type a number ranging from 1 to 5
and click OK. The predecessors or successors up to the specified level, if any, are
displayed in the Impact View. The value defined in the Dependency Level panel is
stored and used whenever a new view is opened.

Use Predecessors/Successors to refresh the view.

Displaying dependencies
To display a dependency of a job instance, right-click the job instance and select
Show Dependencies from the pop-up menu. Any dependent job instances are
displayed.

Only the first level of dependent job instances displays. To display more than one
level of dependency, right-click each dependent job instances and select Show
Dependencies from the pop-up menu.

Note: If you display dependencies for more than one job, then refresh the display,
only the first level of dependent job instances displays.

290 IBM Tivoli Workload Scheduler Job Scheduling Console: User’s Guide
 Set as root

Set as root
You can reset the display using a job instance as the root job instance. Right-click
the job instance you want as root and select Set As Root from the pop-up menu.
The display is refreshed, showing the selected job instance as the root instance.

To reset the display in a separate panel, right-click the job instance you want as
root and select Set As Root In New Frame from the pop-up menu.

Browsing the job log

To browse the job instance log, right-click a job instance and select Browse Job Log
from the pop-up menu. The Job Instance Output panel displays.

Click Cancel to close the panel.

Setting a job instance to a non operational state (NOP) in the plan

You can use the NOP option to set a job instance that is already in the plan and is
ready or waiting to run in a non-operational state (NOP). Use this option on job
instances whose internal status is one of the following:
v Arriving
v Ready
v Ready-non reporting workstation
v Waiting
v Completed (only for workstations with automatic reporting)

To use the NOP option, right-click the name of a job instance and select NOP from
the pop-up menu.

Restoring a job instance to operational in the plan (UN-NOP)

You can use the UN-NOP option to make an non-operational job instance to an
operational job instance.

To do this, right-click the name of a job instance and select UN-NOP from the
pop-up menu. The job instance is restored to the plan.

| Killing a job instance running on a fault-tolerant agent

| Use the kill function to stop a job instance that is currently running on a
| fault-tolerant agent or on a standard agent. To kill a job instance, perform the
| following steps:
| 1. Run a list of job instances that contains the job instance you want to kill. See
| Chapter 33, “Working with lists,” on page 185.
| 2. Right-click the job instance and select Kill from the pop-up menu. A
| confirmation message displays. When you kill a job instance both the Status
| and the Internal Status are set to Error. If the job instance has a recovery job
| associated and you want to stop it running too, see “Recovery information” on
| page 294.

Chapter 48. Managing z/OS job instances 291

Running a job instance immediately

Running a job instance immediately

You can use the Execute option to immediately run a job instance that is ready to
run regardless of normal scheduling rules excluding dependencies. In order to run,
the resources the job instance depends on must be available.

To run a job instance immediately, right-click the name and select Execute from the
pop-up menu. If all conditions are met, the job instance is run immediately.

Changing the status of a job instance

You can set the status of a job instance manually. To do this, perform the following
steps:
1. Right-click the name of a job instance and select Set Status from the pop-up
menu. The Change Status panel displays.
2. Select the status you want. When you are changing to an Error status, you can
type a code that you want to appear in the Properties panel of the job instance.

Editing JCL
You can modify the variables and instructions associated with a job instance before
submitting a job, by editing the JCL associated with the instance.

To edit the JCL, perform the following steps:

1. In a list, right-click a job instance and select Edit JCL from the pop-up menu.
The Edit JCL panel displays.
2. Make the changes you want.
3. Click Import to open a JCL file and copy JCL into the edit panel.
4. Click Export to save any JCL from the job you are editing.

Click OK to save the changes and close the panel.

Viewing operator instructions

You can view any operator instructions associated with a job instance. To do this,
perform the following steps:
1. Right-click the name of a job instance and select Browse Operator Instruction
from the pop-up menu. The Browse Operator Instruction panel displays.
2. Click OK.

Modifying job setup

The Job Setup option allows you to customize a job before it is submitted. To do
this, right-click a job instance and select Job Setup from the pop-up menu. If there
are promptable variables that have not yet been set, the Job Setup panel displays
where you can change the values of the variables.
Notes:
1. You can only change the variable value. A default value displays, if it has been
set beforehand.
2. After you save your changes, the job stays in the ready state. You can select Set
Status to change the job status to COMPLETE that automatically starts the
successors of the job.

292 IBM Tivoli Workload Scheduler Job Scheduling Console: User’s Guide
 Modifying job setup

When you have made your changes, click OK. A second Job Setup panel displays
for each successor job instance. Each panel shows the JCL for the instance,
reflecting the change made to the promptable variables.

For each Job Setup JCL panel, click OK to save the changes and close the panel.

Restart and cleanup

Note: Before using this function, you should refer to the Restart and Cleanup
description in Tivoli Workload Scheduler for z/OS Planning and Scheduling.

| You can restart a job instance or a step and perform cleanup operations, as follows.

| Right-click a job instance and select Restart from the menu. Select one of the
| following:
| Restart and Cleanup
| The Restart and Cleanup panel displays. Some of the options listed below
| might not be available, depending on factors such as whether the job is
| restartable. Select one of the following:
| Step Restart
| Restarts the job or the started task at the JCL step level and
| performs the appropriate cleanup actions. When you request a step
| restart, the scheduler shows you which steps are restartable and
| which is the best step, but you can choose to ignore the suggestion
| and restart at a different step.
| Job Restart
| Completely restarts the job, including the necessary cleanup
| actions. The scheduler shows you the list of data sets with the
| related steps, or the JCL before restarting.
| Start Cleanup
| Runs the subtask that simply cleans up the data set.
| Start Cleanup with AR
| Performs the same operation as Start Cleanup. In addition, the
| cleanup list is built respecting the restart step selected by the
| Automatic Recovery task. This option is allowed only for jobs in
| the error state defined with manual cleanup. When you select this
| option, the clean up list displays with the restart step name and
| number at the bottom of the panel.
| Display Clean Up Result
| View the results of the last cleanup.
| Use Expanded JCL
| This is for information only. If selected, the Job or Step restart uses
| Extended JCL. It can be enabled by selecting Expanded JCL in the
| Properties - Options page of the job prior to selecting one of the
| restart options described in this section.
| Expanded JCL is the JCL extracted from the JOBLOG of the last
| run and is built from data store. When data store builds the
| expanded JCL, the EXEC statements that call for procedures are
| commented out and the called procedures are inserted in their
| expanded form. The result is a linear JCL without procedure calls.

Chapter 48. Managing z/OS job instances 293

 Restart and cleanup

| When you use expanded JCL, the same steps (along with the ones
| in the called procedures and INCLUDE) are rerun exactly as they
| were in the original run.
| Fast Job Restart
| Performs a Job Restart without giving you the option to modify the list of
| data sets with the related steps, or the JCL.
| Fast Step Restart
| Performs a Step Restart from the best step determined by the scheduler,
| without giving you the option to select a different step or modify any
| other aspects of the job.

| Note: When run for the first time on a job or step, these options only create the
| job log. You must wait a few seconds and then launch the option again to
| use that job log to restart the job or step. If the job or step does not restart,
| repeat this operation until it does.

Recovery information
Recovery Info displays the recovery options defined in the job script, and can be
displayed only in case the job fails. Most of the fields in the panel are read-only,
because the recovery statements are coded within the job script, and cannot be
modified using the graphical interface.

Right-click a job instance and select Recovery Info from the menu.

Recovery Option displays the recovery option specified in the job script. For more
information on the recovery options, refer to IBM Tivoli Workload Scheduler for z/OS:
Customization and Tuning.

Prompt Information displays the information about prompt options defined in the
job script, such as, Identifier and Status. If a message was defined in the job
script, it displays in Message. Click Reply to Prompt to select an answer to the
prompt. If you select Yes, the operation specified in Recovery Option is
performed, if you select No, no operation is performed.

| Recovery Job Information displays details concerning the recovery job, if any, to
| run if the parent job ends in error. In Recovery Job Information section you can
| perform the following actions:
| Browse Job Log
| To display the Job Instance Log File panel.
| Kill To stop the recovery job instance that is currently running on a
| fault-tolerant agent or on a standard agent. To stop the recovery job
| instance the Status must be Started. When you kill a job instance the Status
| is set to Error. Click Reload to refresh the screen and display the new
| status.

Click OK to save your selection and close the panel.

Automatic recovery
You use Automatic Recovery to request an automatic job recovery for jobs that
ended in error, and that have a cleanup type other than automatic.

| Right-click a job instance and select Automatic Recovery from the menu.

294 IBM Tivoli Workload Scheduler Job Scheduling Console: User’s Guide
 Critical Path

| Critical Path
| You use Critical Path to view a list of all jobs that are on the critical path of the
| selected job.

| Right-click a job instance and select Critical Path from the menu. A list of the jobs
| in the critical path displays.

| In the list results you can:

| v Right-click any field in the record and perform the allowed actions.
| v Double-click any field in the record to modify the properties.

Chapter 48. Managing z/OS job instances 295

Critical Path

296 IBM Tivoli Workload Scheduler Job Scheduling Console: User’s Guide
 Chapter 49. Managing distributed job instances in the plan
This section describes how to manage distributed job instances in the plan. It is
divided into the following sections:
v “Submitting a job”
v “Submitting an ad hoc job” on page 299
v “Modifying the properties of a job instance” on page 307
v “Displaying and modifying job instance dependencies” on page 314
| v “Deleting a job instance” on page 316
v “Holding a job instance” on page 316
v “Releasing a job instance” on page 317
v “Showing job instance predecessors and successors using the Impact View” on
page 317
v “Browsing the job log” on page 318
v “Rerunning a job instance” on page 319
v “Cancelling a job instance” on page 319
v “Killing a job instance” on page 320
v “Confirming a job instance status” on page 320
v “Releasing a job instance from dependencies” on page 320

Submitting a job
There are two methods to submit a job into a job stream:
v “Into a default job stream”
v “Into a specific job stream” on page 299

Into a default job stream

To submit a job using the default job stream instance, perform the following steps:
1. In the Actions list pane, click Submit.
2. Click Job and select an engine.
The Submit Job into Plan panel displays.

© Copyright IBM Corp. 1991, 2006 297

 Into a default job stream

The panel consists of the following:

Job Set the information of the job you are submitting. Possible values
are:
Name The name of the job that you want to submit to the plan.
Click ... (find) to search for and select a job to submit into
the plan.
Workstation
The name of the workstation on which the job instance
runs. This field is completed automatically when you select
a job using ... (find).
Alias An alias name for the submitted job. An alias is needed
only if JOBS contains another job instance of the same
name. An error message displays if JOBS already has a job
instance of the same name and you do not specify an alias.
Into Set the information about the job stream you are submitting into.
Possible values are:
Job Stream
This field displays the name of the default job stream,
JOBS.
Workstation
The name of the workstation on which the job stream
instance runs. You can specify a different workstation.
Click ... (find) to search for and select a workstation.
| Scheduled Time
| The time at which the job stream is scheduled to run. After
| you modified the Properties of a job instance, you cannot
| modify the Scheduled Time .

298 IBM Tivoli Workload Scheduler Job Scheduling Console: User’s Guide
 Into a default job stream

If you want to view or modify the properties of the job, click on Properties. See
“Modifying the properties of a job instance” on page 307 for details. If you want to
submit the job and close the panel, click OK.

Into a specific job stream

To submit a job using a specific job stream instance, perform the following steps:
1. Run a job stream instance list that contains the job stream into which you want
to submit a job. See Chapter 33, “Working with lists,” on page 185.
2. Right-click the job stream instance.
3. Select Submit, then Job from the pop-up menu.

The Submit Job into Plan panel displays.

The panel consists of the following:

Job Set the information of the job you are submitting. Possible values
are:
Name The name of the job that you want to submit to the plan.
Click ... (find) to search for and select a job to submit into
the plan.
Workstation
The name of the workstation on which the job instance
runs. This field is completed automatically when you select
a job using ... (find).
Into Set the information about the job stream you are submitting into.
Possible values are:
Job Stream
This read only field displays the name of the job stream.
Workstation
The name of the workstation on which the job stream
instance runs. You can specify a different workstation.
Click ... (find) to search for and select a workstation.
Alias An alias for the job. An alias is needed only if JOBS contains
another job instance of the same name.

If you want to view or modify the properties of the job, click Properties. See
“Modifying the properties of a job instance” on page 307 for details. If you want to
submit the job and close the panel, click OK.

When you submit a job, you can also modify the job predecessors. See
“Predecessors page” on page 305.

Submitting an ad hoc job

There are two methods to submit an ad hoc job into the plan:
v “Into a specific job stream”
v “Into a default job stream” on page 307

Into a specific job stream

To submit an ad hoc job into a specific job stream instance, perform the following
steps:
1. Run a job stream instance list that contains the job stream into which you want
to submit a job. See Chapter 33, “Working with lists,” on page 185.

Chapter 49. Managing distributed job instances in the plan 299

Submitting a distributed ad hoc job into a specific job stream

2. Right-click the job stream instance and select Submit  Ad Hoc Job from the
pop-up menu. The Properties - Job Instance panel displays.

The panel consists of the following:

v “General page”
v “Task page” on page 301
v “Time Restrictions page” on page 302
v “Files page” on page 305
v “Prompts page” on page 303
v “Resources page” on page 303
v “Predecessors page” on page 305
v “Internetwork Predecessors page” on page 306

General page
Use the General page to enter general information for the ad hoc job.

The page consists of the following:

Task Type Select the type of task from the drop-down menu. Possible values
are:
v Windows
v UNIX
v Other
v SAP
Login The UNIX or Windows user ID that launches the ad hoc job.
Priority The priority of the submitted job. To change the priority, enter a
value in the field or select one of:
Hold Sets the priority to 0. This job will not run until the
priority is raised.
High Sets the priority to 100.
Go Sets the priority to 101.
Default Sets the priority to the default priority of the
selected job.

Possible priority values are 0 through 101, where 101 is the highest
priority. A priority value of zero prevents the ad hoc job from
launching.
Alias An alias for the ad hoc job.
Workstation The name of the workstation of the ad hoc job. When you use ...
(find) to search for a workstation, make sure the workstation you
select is correct for the type of ad hoc job you are submitting.
Job Stream The name of the job stream for the ad hoc job. The workstation for
this job stream instance displays only when the you selected to
submit an ad hoc job from a job stream instance list. Otherwise, the
job instance is submitted into JOBS on the workstation for the
specified job.
Scheduled Time
The date and time when the job stream is scheduled to run.

300 IBM Tivoli Workload Scheduler Job Scheduling Console: User’s Guide
 Submitting a distributed ad hoc job into a specific job stream

Recovery Options
The behavior of the ad hoc job in case it ends in failure. Possible
values are:
Action The recovery action for the submitted ad hoc job. It
can be Stop, Continue, or Rerun.
Message The text of a recovery prompt. The maximum
length is 64 characters. The default behavior of a
prompt is to display a message and wait for a
reply. If the string begins with a colon (:), the
message displays but no reply is necessary. If the
string begins with an exclamation mark (!), the
message displays but not logged.
Job Name The name of a recovery job to run if the parent job
abends. Recovery jobs are run only once for each
abended instance of the parent ad hoc job.
Workstation Name
Displays the name of the workstation on which the
recovery job runs. The name is entered
automatically when you select a recovery job.
Not all jobs are eligible to have recovery jobs run
on a different workstation. Follow these guidelines:
v If either workstation is an extended agent, it
must be hosted by a domain manager or a
fault-tolerant agent that runs in Full Status
mode.
v The recovery workstation of the recovery job
must be in the same domain as the workstation
of the parent domain.
v If the recovery workstation of the recovery job is
a fault-tolerant agent, it must run in Full Status
mode.
Requires Confirmation
The ad hoc job completion must be confirmed by the operator.
Monitored Job
The ad hoc job is monitored by Tivoli Business Systems Manager
(TBSM).

Task page
Use the Task page to set task information for the job.

The page consists of the following:

Script When the task is a script, this is the file name and any options and
arguments. The maximum length is 4095 characters. For Windows
jobs, include the file extensions. Universal Naming Convention
(UNC) names are permitted. Do not specify files on mapped
drives. For task types other than Windows, if the file name
contains spaces, type the name in a file that does not have spaces
and use the second file. If spaces or special characters are included,
other than slashes (/) and backslashes (\), the entire string must be
enclosed in quotes (’). For task types other than Windows, double
quotes (") are not permitted. To include a parameter in the
Command field, perform the steps described in “Adding
parameters to jobs” on page 131.
Command When the task is a command, this is the name of the command the
Chapter 49. Managing distributed job instances in the plan 301
Submitting a distributed ad hoc job into a specific job stream

job runs and any options and arguments. The maximum length is
4095 characters. Commands are run directly and the jobmanrc
standard configuration script is not run. For task types other than
Windows, double-quotes (″) are not permitted. To include a
parameter in the Command field, perform the steps described in
“Adding parameters to jobs” on page 131.
Add Parameter
The script or command definition requires a parameter. For
information about adding parameters, see “Adding parameters to
jobs” on page 131.
Is Interactive For Windows jobs, the job runs interactively on the Windows
desktop.
Return Code Mapping Expression
Which return codes cause the job to be successful. Enter a logical
expression that defines the success condition. Allowed operators
are comparison operators (=, != or <>, >, >=, <, <=) and logical
operators (AND, OR, NOT).

Note: For task type SAP Job, refer to the IBM Tivoli Workload Scheduler for
Applications: User’s Guide for information about defining the task.

Time Restrictions page

Use the Time Restrictions page to set time restrictions for the ad hoc job.

The page consists of the following:

Start The time before which the ad hoc job does not start.
Latest Start Time
The time before which the ad hoc job must start. Specify a date
and a time in the format specific to your locale.
Action The action performed when the job instance does not start before
the latest start time.
Suppress The job instance does not start, even if the error
condition that prevented it from starting is
corrected, and dependencies are not released. This
radio button is selected by default.
Continue The job instance starts when the error condition
that prevented it from starting is corrected.
Cancel The job instance is cancelled and dependencies are
released.
Termination Deadline
The time within which a job or job stream must complete. Jobs or
job streams that have not yet started or that are still running when
the deadline time expires, are considered late in the plan. The
termination deadline does not prevent jobs and job streams from
starting. Specify the date and time in a format specific to your
locale.
Repeat Range The range in hours and minutes at which the ad hoc job is
repeated. The hour range is 00 to 23. The minute range is 00 to 59.

302 IBM Tivoli Workload Scheduler Job Scheduling Console: User’s Guide
 Submitting a distributed ad hoc job into a specific job stream

Resources page
Use the Resources page to set resource dependencies for the ad hoc job.

The page consists of the following:

Resource The name of the resource.
Workstation The workstation on which the resource resides.
Quantity The number of units of the resource that are needed by the ad hoc
job to satisfy the dependency.
Available The number of units of the resource that are currently available.
Release Status
Whether the resource dependency is released. This field is
read-only for submitted job instances. Possible values are:
Not Released The job instance is not released from the resource
dependency.
Released The job instance is released from the resource
dependency.

To add a resource dependency for the ad hoc job instance, perform the following
steps:

1. Click .
2. Double-click in the Workstation cell and click ... to search for and select a
workstation.
3. Double-click in the Name cell and click ... to search for and select a resource
name.
4. Double-click in the Quantity cell and specify the number of resource units
required by the ad hoc job instance. The default is one.

To delete a resource dependency, select it and click .

| Prompts page
| Use the Prompts page to set ad hoc or predefined prompt dependencies for the ad
| hoc job.

| To add an ad hoc prompt for the job stream instance, perform the following steps:
| 1. From the drop-down list, select Ad Hoc Prompt.

| 2. Click .
| 3. Double-click in the Message Text cell and type the text of the prompt. The
| default behavior of a prompt is to display a message and wait for a reply.
| Based on the character preceding the text, the prompt can behave differently:
| v If the text begins with a colon (:), the prompt displays, but no reply is
| required to continue processing.
| v If the text begins with an exclamation mark (!), the prompt displays, but it is
| not recorded in the log file.
| Refer to the IBM Tivoli Workload Scheduler: Reference Manual for a detailed
| explanation on how to specify the text of a prompt.
| You can include one or more scheduler parameters as part or all of the text
| string. To use a parameter, place its name between carets (^) .In the row you

Chapter 49. Managing distributed job instances in the plan 303

 Submitting a distributed ad hoc job into a specific job stream

| can see also the information described in the list below. This information is
| filled in when the job stream instance is included in the plan.
| Number
| The number of the prompt dependency.
| Release Status
| The status of the prompt dependency. Possible values are:
| Not Released
| The job stream instance is not released from the prompt
| dependency.
| Released
| The job stream instance is released from the prompt dependency.
| Internal Status
| The internal status of the prompt dependency. Possible values are:
| Not Asked
| The prompt has not been asked.
| Asked
| The prompt has been asked, but no response has been received.
| Answered Yes
| The prompt has been answered affirmatively.
| Answered No
| The prompt has been answered negatively.
| Reply The reply to the prompt dependency. To reply to a prompt that is in the
| ASKED state, click in this column and select Yes or No from the
| drop-down menu.

| To add a predefined prompt for the job stream instance, perform the following
| steps:
| 1. From the drop-down list, select Predefined Prompt.

| 2. Click .
| 3. Type the name of the prompt in the Name cell or click ... (find) to search for
| and select the prompt. The following information displays:
| Message Text
| The text of the prompt.
| Number
| The number of the prompt dependency.
| Release Status
| The status of the prompt dependency. Possible values are:
| Not Released
| The job stream instance is not released from the prompt
| dependency.
| Released
| The job stream instance is released from the prompt dependency.
| Internal Status
| The internal status of the prompt dependency. Possible values are:
| Not Asked
| The prompt has not been asked.
| Asked
| The prompt has been asked, but no response has been received.
| Answered Yes
| The prompt has been answered affirmatively.

304 IBM Tivoli Workload Scheduler Job Scheduling Console: User’s Guide
 Submitting a distributed ad hoc job into a specific job stream

| Answered No
| The prompt has been answered negatively.
| Reply The reply to the prompt dependency. To reply to a prompt that is in the
| ASKED state, click in this column and select Yes or No from the
| drop-down menu.

| To remove a prompt dependency for the job stream, select the prompt row in the

| list and click .

Files page
Use the Files page to set file dependencies for the ad hoc job.

The page consists of the following:

Filename The path and name of the file.
Workstation The workstation on which the file resides.
Qualifiers The test conditions for the file dependency.
Release Status
Whether the file dependency is released. This field is read-only for
submitted job instances. Possible values are:
Not Released The ad hoc job is not released from the file
dependency.
Released The ad hoc job is released from the file
dependency.
Internal Status
The internal status of the file dependency. This field is read-only
for submitted job instances. Possible values are:
Not Checked The file dependency has not been checked.
Checking The file dependency is being checked.
Exists The file dependency is satisfied.
Does Not Exist
The file dependency is not satisfied.

To add a file dependency to the ad hoc job instance, perform the following steps:

1. Click .
2. Double-click the Filename cell and type a file name and path, or click ... (find)
to search for and add a file.
3. Double-click the Workstation cell and click ... (find) to search for and select the
workstation where the file exists or will be created.
4. Double-click the Qualifiers cell and specify the test conditions for the file
dependency. For a description of the possible qualifiers see “Files page” on
page 152.

To delete a file dependency, select it and click .

Predecessors page
Use the Predecessors page to set predecessor dependencies for the ad hoc job.

The page consists of the following:

Chapter 49. Managing distributed job instances in the plan 305

 Submitting a distributed ad hoc job into a specific job stream

Job Stream The name of the predecessor job stream instance or the job stream
that owns the predecessor job.
Job The name of a predecessor job instance.
Workstation The workstation of the predecessor job stream.
Release Status
Whether the predecessor dependency is released. Possible values
are:
Released
The job instance is released from the predecessor dependency.
Not Released
The job instance is not released from the predecessor
dependency.
Internal Status
The Tivoli Workload Scheduler internal status of the predecessor
job or job stream.
For more information on job or job stream status refer to
Appendix D, “Status description and mapping,” on page 425.
Scheduled Time
The time at which the job stream is scheduled to run.

To add a predecessor to the ad hoc job instance, perform the following steps:

1. Click .
2. To specify a predecessor job stream, double-click in the Job Stream cell and
click ... (find) to search for and insert the name of a predecessor job stream
instance.
3. To specify a predecessor job, double-click in the Job cell and click ... (find) to
search for and insert the name of a predecessor job instance.

To delete a predecessor from the ad hoc job instance, select it and click .

| Internetwork Predecessors page

| Use the Internetwork Predecessors page to add predecessor dependencies from a
| remote Tivoli Workload Scheduler network.

| The page consists of the following:

| Network Agent
| The network agent workstation to which the predecessor belongs.
| Dependency
| A dependency or the job or job stream predecessor in the format
| workstation#jobstream.job. The maximum length is 16 for workstation, 16
| for the job stream, and 40 for the job.
| Release Status
| Whether the internetwork predecessor dependency is released. Possible
| values are:
| Released The job instance is released from the internetwork
| predecessor dependency.
| Not Released The job instance is not released from the internetwork
| predecessor dependency.

306 IBM Tivoli Workload Scheduler Job Scheduling Console: User’s Guide
 Submitting a distributed ad hoc job into a specific job stream

| To release the job instance from the predecessor dependency, double-click

| in the Release Status column and select Released from the drop-down
| menu.
| Internal Status
| The Tivoli Workload Scheduler internal status of the predecessor job or job
| stream instance.
| For more information about job or job stream status, see Appendix D,
| “Status description and mapping,” on page 425.

| To add an internetwork predecessor dependency to a job instance, perform the

| following steps:

| 1. Click .
| 2. In the Network Agent cell click ... (find) to search for and select an agent.
| 3. Double-click in the Dependency cell and type the dependency.

| To delete a predecessor, select it and click .

Into a default job stream

To submit an ad hoc job using the default job stream instance, perform the
following steps:
1. In the Action list pane, click Submit.
2. Click Ad hoc and select submit. The Properties job instance panel displays.

The panel consists of the following:

v “General page” on page 300
v “Task page” on page 301
v “Time Restrictions page” on page 302
v “Files page” on page 305
v “Prompts page” on page 303
v “Resources page” on page 303
v “Predecessors page” on page 305
v “Internetwork Predecessors page” on page 306

Modifying the properties of a job instance

To display the properties of a job instance in the plan, perform the following steps:
1. Run a job instance list that contains the job instance you want to modify. See
Chapter 33, “Working with lists,” on page 185.
2. Right-click the job instance and select Properties from the pop-up menu.
The Properties - Job Instance panel displays.
The panel consists of the following:
v “General page” on page 308
v “Task page” on page 309
v “Time Restrictions page” on page 310
v “Resources page” on page 311
v “Prompts page” on page 311
v “Files page” on page 313

Chapter 49. Managing distributed job instances in the plan 307

Modifying job instance properties in the plan

After you modified the Properties of a job instance, you cannot modify the
Scheduled Time .

General page
Use the General page to modify the general properties of the job instance.

The page consists of the following:

Name The name of the job instance.
Workstation (Job)
The name of the workstation on which the job instance is
launched.
Job Stream Name
The name of the job stream this job instance belongs to.
Scheduled Time
The date and time when the job is scheduled to run.
Workstation (Job Stream)
The name of the workstation on which the job stream instance is
launched.
Job Number The PID assigned by the operating system when a job instance has
been run in the production plan.
Login The user ID of the person running the job instance.
Information Additional information about the job instance.
Rerun Options
Whether this job instance has been rerun.
Requires Confirmation
The job instance does not go into the final state without
confirmation.
Monitored Job
The running of this job is to be monitored by Tivoli Business
Systems Manager. Changes to the monitored job status are not
displayed in the job stream properties until you close and reopen
the job stream.
Is Interactive Whether this job instance is an interactive job. This information
appears only for Windows jobs.
Priority The priority of the job instance. Type a priority value or click:
Hold
Sets the priority to 0.
High
Sets the priority to 100.
Go
Sets the priority to 101.

Possible priority values are 0 through 101, where 101 is the highest
priority. A priority value of zero prevents the job from launching.
High and Go jobs are launched as soon as their dependencies are
satisfied, overriding the workstation job limit, but not overriding
the job stream job limit or the workstation job fence.
Status The Job Scheduling Console status of the job instance.

308 IBM Tivoli Workload Scheduler Job Scheduling Console: User’s Guide
 Modifying job instance properties in the plan

For more information on job or job stream status refer to

Appendix D, “Status description and mapping,” on page 425.
Internal Status
The Tivoli Workload Scheduler internal status of the job instance.
For more information on job or job stream status refer to
Appendix D, “Status description and mapping,” on page 425.
Start Time The actual start time of the job instance, if it has completed
running.
Duration The actual duration of the job instance, if it has completed running.
The actual time duration is calculated as the execution time
rounded up to one minute for the elapsed time. For example, an
execution time of 4 minutes 20 seconds would be rounded to 5
minutes, or an execution time of 10 minutes would be rounded to
11 minutes.
Recovery Options
The recovery options if the job instance ends in error. Possible
values are:
Stop Do not continue with the next job instance.
Continue Continue with the next job instance.
Rerun Rerun the job instance.
Job Name The name of a recovery job to run. Recovery jobs
are run only once for each instance of the parent
job instance.
Workstation Name
The name of the workstation on which the
recovery job runs. The name is entered
automatically when you select a recovery job.
Not all jobs are eligible to have recovery jobs run
on a different workstation. Follow these guidelines:
v If either workstation is an extended agent, it
must be hosted by a domain manager or a
fault-tolerant agent that runs in Full Status
mode
v The recovery job workstation must be in the
same domain as the parent job workstation
v If the recovery job workstation is a fault-tolerant
agent, it must run in Full Status mode
Message The text of the recovery prompt when a job
instance ends in error. The maximum length is 64
characters. The recovery prompt is local and you
respond using the Job Scheduling Console.

Task page
Use the Task page to review information about the job instance task.

The page consists of the following:

Task Type
The task type of the job instance.
Command
The command or script that is called by the task.

Chapter 49. Managing distributed job instances in the plan 309

Modifying job instance properties in the plan

Return Code
The return code assigned to the job instance.
Expression
The logical expression that defines the success condition.

Time Restrictions page

Use the Time Restrictions page to modify the time restriction properties of the job
instance.

The page consists of the following:

Start The date and time before which the job stream does not start.
Possible values are:
Specify Date and Time
Select Specify Date and Time when you want to
specify a start time for the job instance.
Date The date before which the job stream does not
start.
Time The time before which the job stream does not
start. The format is specific to your locale.
Latest Start Time
The latest time at which the job instance should start.
Specify Date and Time
Select Specify Date and Time when you want to
specify a latest start time for the job instance.
Date The date by which the job stream should start.
Time The time by which the job stream should start. The
format is specific to your locale.
Action The action to be performed in case the job instance does not start
before the Latest Start Time. Possible values are:
Suppress
Select Suppress to specify that the job instance does not start,
even if the error condition that prevented it from starting is
corrected, and dependencies are not released. Suppress is the
default.
Continue
Select Continue to specify that the job instance starts when the
error condition that prevented it from starting is corrected.
Cancel
Select Cancel to specify that the job instance is cancelled and
dependencies are released.
Termination Deadline
The time by which the job instance should complete. Job instances
still running at termination deadline are considered late in the
plan. The termination deadline does not prevent jobs and job
streams from starting. Possible values are:
Specify Date and Time
Select Specify Date and Time when you want to
specify a deadline time for the job instance.
Date The date by which the job stream should end.
Time The time by which the job stream should end. The
format is specific to your locale.
Repeat Range The interval of time in hours and minutes for each run of the job
to be repeated. Using the Repeat Range with the Start and
Termination Deadline times allows you to run a job instance, for
example, every 15 minutes from 1:00 p.m. to 5:00 p.m.

310 IBM Tivoli Workload Scheduler Job Scheduling Console: User’s Guide
 Modifying job instance properties in the plan

Resources page
Use the Resources page to set resource dependencies for the job instance.

The page consists of the following:

Resource
The name of the resource.
Workstation
The workstation on which the resource resides.
Quantity
The number of units of a resource are needed by the job instance to satisfy
the dependency.
Available
The number of units of the resource that are currently available.
Release Status
Whether the resource dependency is released. Possible values are:
Not Released The job instance is not released from the resource
dependency.
Released The job instance is released from the resource dependency.

To release the job instance from the resource dependency, double-click in

the Release Status column and select Released from the drop-down menu.

To add a resource dependency to the job instance, perform the following steps:

1. Click .
2. Double-click in the Workstation cell and click ... to search for and select a
workstation.
3. Double-click in the Resource cell and click ... to search for and select a resource
name.
4. Double-click in the Quantity cell and specify the number of resource units
required by the ad hoc job instance. The default is one.

To delete a resource dependency, select it and click .

| Prompts page
| Use the Prompts page to set ad hoc or predefined prompt dependencies for the job
| instance.

| To add an ad hoc prompt for the job instance, perform the following steps:
| 1. From the drop-down list, select Ad Hoc Prompt.

| 2. Click .
| 3. Double-click in the Message Text cell and type the text of the prompt. The
| default behavior of a prompt is to display a message and wait for a reply.
| Based on the character preceding the text, the prompt can behave differently:
| v If the text begins with a colon (:), the prompt displays, but no reply is
| required to continue processing.
| v If the text begins with an exclamation mark (!), the prompt displays, but it is
| not recorded in the log file.

Chapter 49. Managing distributed job instances in the plan 311

 Modifying job instance properties in the plan

| Refer to the IBM Tivoli Workload Scheduler: Reference Manual for a detailed
| explanation on how to specify the text of a prompt.
| You can include one or more scheduler parameters as part or all of the text
| string. To use a parameter, place its name between carets (^) .In the row you
| can see also the information described in the list below. This information is
| filled in when the job stream instance is included in the plan.
| Number
| The number of the prompt dependency.
| Release Status
| The status of the prompt dependency. Possible values are:
| Not Released
| The job instance is not released from the prompt dependency.
| Released
| The job instance is released from the prompt dependency.
| Internal Status
| The internal status of the prompt dependency. Possible values are:
| Not Asked
| The prompt has not been asked.
| Asked
| The prompt has been asked, but no response has been received.
| Answered Yes
| The prompt has been answered affirmatively.
| Answered No
| The prompt has been answered negatively.
| Reply The reply to the prompt dependency. To reply to a prompt that is in the
| ASKED state, click in this column and select Yes or No from the
| drop-down menu.

| To add a predefined prompt for the job instance, perform the following steps:
| 1. From the drop-down list, select Predefined Prompt.

| 2. Click .
| 3. Type the name of the prompt in the Name cell or click ... (find) to search for
| and select the prompt. The following information displays:
| Message Text
| The text of the prompt.
| Number
| The number of the prompt dependency.
| Release Status
| The status of the prompt dependency. Possible values are:
| Not Released
| The job instance is not released from the prompt dependency.
| Released
| The job instance is released from the prompt dependency.
| Internal Status
| The internal status of the prompt dependency. Possible values are:
| Not Asked
| The prompt has not been asked.
| Asked
| The prompt has been asked, but no response has been received.

312 IBM Tivoli Workload Scheduler Job Scheduling Console: User’s Guide
 Modifying job instance properties in the plan

| Answered Yes
| The prompt has been answered affirmatively.
| Answered No
| The prompt has been answered negatively.
| Reply The reply to the prompt dependency. To reply to a prompt that is in the
| ASKED state, click in this column and select Yes or No from the
| drop-down menu.

| To remove a prompt dependency for the job instance, select the prompt row in the

| list and click .

Files page
Use the Files page to set file dependencies for the job instance.

The page consists of the following:

Filename
The path and name of the file. If the file resides on another workstation, it
must have the Job Scheduling Console installed.
Workstation
The workstation on which the file resides.
Qualifiers
The test conditions for the file dependency. For a description of the
possible qualifiers see “Files page” on page 152.
Release Status
Whether the file dependency is released. Possible values are:
Not Released The job instance is not released from the file dependency.
Released The job instance is released from the file dependency.

To release the job instance from the file dependency, double-click in the
Release Status column and select Released from the drop-down menu.
Internal Status
The internal status of the file dependency. Possible values are:
Not Checked
The file dependency has not been checked.
Checking
The file dependency is being checked.
Exists
The file dependency is satisfied.
Does Not Exist
The file dependency is not satisfied.

To add a file dependency to the job instance, perform the following steps:

1. Click .
2. Double-click the Filename cell and type a file name and path, or click ... (find)
to search for and add a file name.
3. Double-click the Workstation cell and click ... (find) to search for and select the
workstation where the file exists or will be created.
4. Double-click the Qualifiers cell and specify the test conditions for the file
dependency. For a description of the possible qualifiers see “Files page” on
page 152.

Chapter 49. Managing distributed job instances in the plan 313

Modifying job instance properties in the plan

To remove a file dependency from the job instance, select it and click .

Displaying and modifying job instance dependencies

To display and modify the dependencies of a job instance, perform the following
steps:
1. Run a list of job instances that contains the job instance you want to modify.
See Chapter 33, “Working with lists,” on page 185.
2. Right-click the job instance and select Dependencies from the pop-up menu.
The Dependencies - Job Instance panel displays.

The panel consists of the following:

v “Predecessors page”
v “Internetwork Predecessors page” on page 315
v “Successors page” on page 316

Predecessors page
Use the Predecessors page to set predecessor dependencies for the job instance.

The page consists of the following:

Job Stream
The name of a predecessor job stream instance or the job stream that owns
the predecessor job.
Job The name of a predecessor job instance.
Workstation
The workstation of the predecessor job or job stream.
Release Status
Whether the predecessor dependency is released. Possible values are:
Released The job instance is released from the predecessor
dependency.
Not Released The job instance is not released from the predecessor
dependency.

To release the job instance from the predecessor dependency, double-click

in the Release Status column and select Released from the drop-down
menu.

314 IBM Tivoli Workload Scheduler Job Scheduling Console: User’s Guide
 Modifying job instance properties in the plan

Internal Status
The Tivoli Workload Scheduler internal status of the predecessor job or job
stream instance.
For more information about job or job stream status, see Appendix D,
“Status description and mapping,” on page 425.
Scheduled Time
The time at which the job instance is scheduled to run.

To add a predecessor dependency to a job instance, perform the following steps:

1. Click .
2. To specify a predecessor job instance, double-click in the Job cell and click ...
(find) to search for and select a predecessor job instance. This operation
automatically displays the job stream to which the job belongs in the Job
Stream cell.
3. To specify a predecessor job stream instance, double-click in the Job Stream cell
and click ... (find) to search for and select the name of a predecessor job stream
instance.

To delete a predecessor, select it and click .

Internetwork Predecessors page

Use the Internetwork Predecessors page to add predecessor dependencies from a
remote Tivoli Workload Scheduler network.

The page consists of the following:

Network Agent
The network agent workstation to which the predecessor belongs.
Dependency
A dependency or the job or job stream predecessor in the format
workstation#jobstream.job. The maximum length is 16 characters for
workstation, 16 characters for the job stream, and 40 characters for the job.
Release Status
Whether the internetwork predecessor dependency is released. Possible
values are:
Released The job instance is released from the internetwork
predecessor dependency.
Not Released The job instance is not released from the internetwork
predecessor dependency.

To release the job instance from the predecessor dependency, double-click

in the Release Status column and select Released from the drop-down
menu.
Internal Status
The Tivoli Workload Scheduler internal status of the predecessor job or job
stream instance.
For more information about job or job stream status, see Appendix D,
“Status description and mapping,” on page 425.

To add an internetwork predecessor dependency to a job instance, perform the

following steps:
Chapter 49. Managing distributed job instances in the plan 315
 Modifying job instance properties in the plan

1. Click .
2. In the Network Agent cell click ... (find) to search for and select an agent.
3. Double-click in the Dependency cell and type the dependency.

To delete a predecessor, select it and click .

Successors page
Use the Successors page to view information about successor dependencies.

The page consists of the following:

Job Stream Name
The name of the successor job stream instance or the name of the job
stream that owns the successor job.
Job The name of the successor job.
Workstation
The workstation to which the successor belongs.
Status The status of the job.
Internal Status
The Tivoli Workload Scheduler internal status of the successor job.
Scheduled Time
The time at which the job instance is scheduled to run.

| Deleting a job instance

| You can delete a single job instance or delete all jobs in a group of job instances. To
| delete a single job instance see “Deleting objects from a list” on page 49, to delete
| all jobs in a group of job instances follow the procedure described in “Deleting all
| job instances.”

| Deleting all job instances

| To delete all jobs in a group of job instances in the Timeline View, perform the
| following steps:
| 1. Run a list of job instances that contains the instances you want to delete. See
| Chapter 33, “Working with lists,” on page 185.

| 2. Click to switch to the Timeline View.

| 3. Right-click the arrow next to the job instance group.
| 4. Click Delete All.

Holding a job instance

This section describes how to hold job instances. It consists of the following
subsections:
v “Holding a single job instance” on page 317
v “Holding all job instances” on page 317

316 IBM Tivoli Workload Scheduler Job Scheduling Console: User’s Guide
 Deleting a job instance

Holding a single job instance

To change a single job instance to Hold, perform the following steps:
1. Run a list of job instances that contains the job you want to hold. See
Chapter 33, “Working with lists,” on page 185.
2. Right-click the job instance and select Hold from the pop-up menu.

Holding all job instances

To hold all jobs in a group of job instances in the Timeline View, perform the
following steps:
1. Run a list of job instances that contains the instances you want to hold. See
Chapter 33, “Working with lists,” on page 185

2. Click to switch to the Timeline View.

3. Right-click the arrow next to the job instance group.
4. Click Hold All.

Releasing a job instance

This section describes how to release a job instance that is in Hold, returning the
job priority to its start of production day state. It consists of the following
subsections:
v “Releasing a single job instance”
v “Releasing all job instances”

Note: Do not confuse Release with Release All Dependencies. It has no effect on
job dependencies.

Releasing a single job instance

To change a single job instance to Release, perform the following steps:
1. Run a list of job instances that contains the job instance you want to release.
See Chapter 33, “Working with lists,” on page 185.
2. Right-click the job instance you want release.
3. Select Release from the pop-up menu.

Releasing all job instances

To release all jobs in a group of job instances, perform the following steps:
1. Run the list of job instances. See Chapter 33, “Working with lists,” on page 185

2. Click to switch to the Timeline View.

3. Right-click the arrow next to the job instance group.
4. Click Release All.

Showing job instance predecessors and successors using the Impact

View
To show the predecessors or successors of a job instance in the Impact View,
perform the following steps:

Chapter 49. Managing distributed job instances in the plan 317

 Deleting a job instance

1. Run a list of job instances that contains the job instance you want to view. See
Chapter 33, “Working with lists,” on page 185.
2. Right-click the job instance and select Impact View  Predecessors or
Successors.
| The Impact View panel displays.
|

| Use the Layout menu to set Direction and Dependency Level.

Direction graphically shows the job instances and their dependencies in the panel.

Dependency Level sets the level of dependencies displayed in the Impact View
ranging from 1 to 5. The predecessors or successors up to the specified level, if any,
are displayed in the Impact View. The value defined in the Dependency Level
panel is stored and used whenever you open another view.

At any time, you can reset the display using a job instance as the root job instance.
Right-click the job instance you want to use as the root job instance and select Set
As Root from the pop-up menu. The display is refreshed, showing the selected job
instance as the root instance.

To reset the display in a separate panel, right-click the job instance you want to use
as the root job instance and select Set As Root In New Frame from the pop-up
menu.

Predecessors/Successors toggles the view.

Browsing the job log

A job instance log file is created for each job instance launched by Tivoli Workload
Scheduler. Log files contain header and trailer banners, echoed commands, and
errors and warnings. These files can be used to troubleshoot problems when jobs
run.

To view the job instance log, perform the following steps:

318 IBM Tivoli Workload Scheduler Job Scheduling Console: User’s Guide
 Deleting a job instance

1. Run a list of job instances that contains the job instance you want to browse.
See Chapter 33, “Working with lists,” on page 185.
2. In the list results, right-click the job instance you want to display.
3. Select Browse Job Log from the pop-up menu.
The job instance log file panel displays.

Rerunning a job instance

You can rerun a job instance when its internal state is one of the following:
v SUCC
v ABEND

To rerun a job instance, perform the following steps:

1. Run a list of job instances that contains the job instance you want to rerun. See
Chapter 33, “Working with lists,” on page 185.
2. In the list results, right-click the job instance you want to rerun.
3. Select Rerun from the pop-up menu.
The Rerun Job panel displays.

The panel consists of the following:

From Job Definition
The job definition from which you want the job to taken.
Workstation Name
The workstation to run the job.
Step The step from which you would like to rerun this job. The new job
instance assumes the name specified here.
Specify Date and Time
Select this to specify that entry of a from time is enabled.
Date The date from which the job can start.
Time The time from which the job can start.
Priority The priority of the submitted job. Possible values are:
Hold The priority of the submitted job. To change the priority,
enter a value in the field or select one of:
Hold Sets the priority to 0. This job will not run
until the priority is raised.
High Sets the priority to 100.
Go Sets the priority to 101.

Possible priority values are 0 through 101, where 101 is the

highest priority. A priority value of zero prevents the ad
hoc job from launching.

Cancelling a job instance

Cancelling a job instance in the plan prevents the job from running. A cancelled job
instance can be submitted anytime during the production cycle using an alias
name. For more information, see “Submitting a job” on page 297.

To cancel a job instance, perform the following steps:

Chapter 49. Managing distributed job instances in the plan 319

 Deleting a job instance

1. Run a list of job instances that contains the job instance you want to cancel. See
Chapter 33, “Working with lists,” on page 185.
2. Right-click the job instance and select Cancel from the pop-up menu.

| Performing a cancel pending of a job instance

| Use this function to cancel a job stream when all its dependencies are resolved. To
| cancel a job instance, perform the following steps:
| 1. Run a list of job instances that contains the job instance you want to cancel. See
| Chapter 33, “Working with lists,” on page 185.
| 2. Right-click the job instance and select Cancel Job Pending from the pop-up
| menu.
| If the job has not been launched, cancellation is deferred until all of the
| dependencies, including an at time, are resolved. When all the dependencies
| are resolved, the job is cancelled and any jobs or job streams that are dependent
| on the cancelled job are released from the dependency. If the job has been
| launched, the job is cancelled when it completes and is moved to its final
| status.

| Killing a job instance

| Use the kill function to stop a job instance that is currently running. To kill a job
| instance, perform the following steps:
| 1. Run a list of job instances that contains the job instance you want to kill. See
| Chapter 33, “Working with lists,” on page 185.
| 2. Right-click the job instance and select Kill from the pop-up menu. A
| confirmation message displays. When you kill a job instance the Status is set to
| Error and the Internal Status is set to Abend.

Confirming a job instance status

Confirming a job instance status as SUCC or ABEND allows you to force the job
instance into a state where either its successors can continue processing or job
recovery options are started.

To confirm a job instance status to SUCC or ABEND, perform the following steps:
1. Run a list of job instances that contains the job instance you want to confirm.
See Chapter 33, “Working with lists,” on page 185.
2. Right-click the job instance and select Confirm  SUCC or ABEND from the
pop-up menu.

Releasing a job instance from dependencies

To release a job instance from its dependencies, perform the following steps:
1. Run a list of job instances that contains the job instance you want to release.
See Chapter 33, “Working with lists,” on page 185.
2. Right-click the job instance and select Release All Dependencies from the
pop-up menu. This allows the job instance to run unless there are other higher
priority jobs waiting to run, or if the job instance priority is below the fence for
the workstation.

320 IBM Tivoli Workload Scheduler Job Scheduling Console: User’s Guide
Chapter 50. Managing workstations in the plan
This chapter describes how you manage workstations in the plan. It is divided into
the following sections:
v “Managing z/OS workstations in the plan”
v “Managing distributed workstations in the plan” on page 326

Managing z/OS workstations in the plan

This section describes how to monitor and update z/OS workstations in the plan.
It consists of the following subsections:
v “Displaying the status of z/OS workstations in the plan”
v “Modifying z/OS workstation properties in the plan” on page 322
v “Linking fault-tolerant workstations” on page 324
v “Changing workstation status and rerouting scheduled job instances” on page
324
v “Displaying workstation job instances by status” on page 325
v “Modifying z/OS job instances scheduled on a workstation” on page 325

Displaying the status of z/OS workstations in the plan

To display a list of workstations in the plan, perform the following steps:
1. Run a the Status of all Workstations plan list. See Chapter 33, “Working with
lists,” on page 185.
The Status of all Workstations table displays in the Object list pane.

The table consists of the following:

Name The name of the workstation.
Status The status of the workstation. Possible values are:
Available The workstation is free to run the job.
Not Available The workstation is not free to run the job.
Unknown The status of the workstation is not known.
Active When the workstation is fault-tolerant, it is ready
to run a job.
Offline When the workstation is fault-tolerant, it is not
connected.
Internal Status
The internal status of the workstation is listed only when the status
of the workstation is Not Available.

© Copyright IBM Corp. 1991, 2006 321

 Displaying z/OS workstation status in the plan

Fault Tolerant Whether the workstation is fault-tolerant.

| Automation Whether the workstation is defined for integration with Tivoli
| System Automation for z/OS.
Linked Whether the workstation is connected. Possible values are:
Yes The workstation is connected.
No The workstation is not connected.
Reporting Attribute
The reporting attribute for the workstation. Possible values are:
Manual start and completion
Status changes of jobs are reported from the Ready
List ISPF panel on the host, or from the results of a
workstation status list.
Non reporting Jobs on this workstation are set to complete as they
become ready to start.
Automatic Status changes of jobs are reported automatically in
response to event records created by Tivoli
Workload Scheduler.
Completion only
Status changes of jobs are reported from the Ready
List ISPF panel on the host or from the results of a
workstation status list.
Type The type of workstation. Possible values are:
v General
v Computer
v Printer
Jobs Running The number of jobs that are currently running on the workstation.
Jobs Successful
The number of current plan jobs that completed successfully on the
workstation.
Total Runtime The total time that completed jobs took to complete, in hours and
minutes.
Jobs Remaining
The number of current jobs scheduled to run on the workstation.
Expected Runtime
The time that the remaining current plan jobs are expected to take
to run, in hours and minutes.

Modifying z/OS workstation properties in the plan

To change the properties of a z/OS workstation in the plan, perform the following
steps:

Note: The changes you make to a workstation in the plan do not change the
workstation properties in the database.
1. Run a Status of all Workstations list that contains the workstation you want to
modify. See Chapter 33, “Working with lists,” on page 185.
2. Right-click the workstation and select Properties from the pop-up menu.
The Properties - Workstation in Plan panel displays. Several of the fields are
read only.

322 IBM Tivoli Workload Scheduler Job Scheduling Console: User’s Guide
 Displaying z/OS workstation status in the plan

See “Creating a z/OS workstation” on page 98 for an idea of the panel

appearance.
The panel consists of the following:
v “General page”
v “Resources page”
v “Job Summary tab”
v “Open Time Intervals page”

General page
Use the General page to review general information about the workstation, or to
set the Reporting Attribute of the workstation. For a definition of the fields, see
“Creating a z/OS workstation” on page 98.

Resources page
Use the Resources page to review details of the workstation resources. For each of
the two resources the panel displays the name, the amount in use, and the type of
use. For a definition of the fields, see “Creating a z/OS workstation” on page 98.

To change the type of use of each resource, select Used for control. This means
that, if an unexpected event happens while job instances are running, the system
considers the resource when it reschedules them.

Job Summary tab

Use the Job Summary page review a summary of the job instances scheduled to
run on the workstation.

This page displays the number, estimated duration, and actual duration (where
applicable) of all the job instances scheduled to run on the workstation. The
information is provided for instances in the following status:
v Completed
v Interrupted
v Started
v Ready
v Jobs Waiting

Open Time Intervals page

Use the Open Time Intervals to review and modify the boundaries and modified
values of the workstation open time intervals.

To add an open time interval for the workstation, perform the following steps:

1. Click .
2. Double-click the Start Date cell and add a new day.
3. Double-click in the Start Time cell and enter the new time.
4. Double-click in the End Date cell and enter the new end date.
5. Double-click in the End Time cell and enter the new end time.
6. Double-click in the Planned PS cell and enter the number of parallel servers
defined for the workstation.
7. Double-click in the Planned R1 cell and enter the quantity of available
resources.
8. Double-click in the Planned R2 cell and enter the quantity of available
resources.

Chapter 50. Managing workstations in the plan 323

Displaying z/OS workstation status in the plan

9. Double-click in the Planned Alternate cell and enter a workstation that can
substitute the workstation if it is unavailable.
10. Double-click the Modified PS cell and enter the new parallel server quantity.
11. Double-click the Modified R1 cell and enter the new resource quantity.
12. Double-click in the Modified R2 cell and enter the new resource quantity.
13. Double-click in the Modified Alternate cell and to click ... (find) to search for
and select an alternate workstation.

To delete an open time interval, select it and click .

Linking fault-tolerant workstations

To link a fault-tolerant workstation to the master workstation, perform the
following steps:
1. Run a Status of all Workstations list that contains the workstation you want to
modify. See Chapter 33, “Working with lists,” on page 185.
2. Right-click the workstation and select Link from the pop-up menu.

Changing workstation status and rerouting scheduled job

instances
You can manually change the status of a workstation and reroute scheduled job
instances to an alternate workstation. This overrides, for the duration of the current
plan, the corresponding values defined in the database.

To do this, perform the following steps:

1. Run a Status of all Workstations list that contains the workstation you want to
modify. See Chapter 33, “Working with lists,” on page 185.
2. Right-click the workstation and select Set Status from the pop-up menu.
The Change Status - Workstation panel displays.

The panel consists of the following:

Active When the workstation is functioning and available.
Offline When communication fails between Tivoli Workload Scheduler for
z/OS and the workstation.
Failed When system failure makes the workstation unavailable.
Started Jobs Select the action to perform on started jobs. Possible values are:

324 IBM Tivoli Workload Scheduler Job Scheduling Console: User’s Guide
 Displaying z/OS workstation status in the plan

v Restart
v Leave
v Set to error
Reroute Jobs Select to reroute jobs to the alternate workstation you specify in
Alternate Workstation

Note: If the workstation is fault-tolerant, only the Active and Offline options are
available.

Displaying workstation job instances by status

To display workstation job instances by status, perform the following steps:
1. Run a Status of all Workstations list that contains the workstation you want to
modify. See Chapter 33, “Working with lists,” on page 185.
2. Right-click the workstation and select List Jobs  status from the pop-up menu.
Possible states are:
Arriving The job instances are scheduled to run on the workstation.
Complete The job instances completed without errors.
Deleted The job instances were cancelled.
Error The job instances ended in error.
Interrupted The job instances were interrupted.
Ready The job instances are ready to run.
Ready List The job instances are ready to run on the selected workstation, but
have a predecessor on a non-reporting workstation.
Ready - Non Reporting Workstation
The job instances are ready to run on the selected workstation, but
have a predecessor on a non-reporting workstation.
Started The job instances are running.
Undecided The job instances have an unknown status.
Waiting The job instances are running on the selected workstation, but are
keeping other scheduled jobs from running on the same
workstation.

Modifying z/OS job instances scheduled on a workstation

To modify z/OS job instances scheduled on a workstation, perform the following
steps:
1. Run a list of jobs scheduled on a workstation that contains the job instance you
want to modify. See Chapter 33, “Working with lists,” on page 185.
2. Right-click a selected job and select one of the options from the pop-up menu.

Possible options are:

Properties Browse and modify the properties of the job instance.
Dependencies Browse and modify the dependencies of the job instance.
Delete Delete the job instance from the plan.
Hold Hold the job instance.
Release Release the job instance.

Chapter 50. Managing workstations in the plan 325

 Displaying z/OS workstation status in the plan

Impact View Show the predecessors and successors of the job instance
Browse Job Log
View the job log file.
| NOP or UN-NOP
| Set a job instance that is already in the plan and is in ready or
| waiting status to run in a non-operational state (NOP), or change a
| non-operational job instance to an operational job instance
| (UN-NOP).
| Kill Stop a job instance that is currently running on a fault-tolerant
| agent or on a standard agent.
Execute Run the job instance immediately.
Set status Change the status of the job instance.
Edit JCL Modify the variables and instructions associated with a job
instance.
Browse Operator Instruction
View operator instructions associated with a job instance.
Job Setup Tailor job statements.
Restart Restart a job instance and perform cleanup operations.
Recovery Info Displays the recovery options defined in the job script.
Automatic Recovery
Displays whether automatic recovery is set.
| Critical Path Displays all jobs on the same critical path as the selected job.

For an explanation about how to use these options, see Chapter 48, “Managing
z/OS job instances,” on page 277.

Managing distributed workstations in the plan

This section describes how to monitor and update distributed workstations in the
plan. It consists of the following subsections:
v “Displaying the status of distributed workstations in the plan”
v “Displaying distributed workstation instance properties” on page 328
v “Changing the job limit of a workstation in the plan” on page 328
v “Changing the job fence of a workstation in the plan” on page 329
v “Starting a workstation instance” on page 329
v “Stopping a workstation instance” on page 329
v “Linking a workstation instance” on page 329
v “Unlinking a workstation instance” on page 329

Displaying the status of distributed workstations in the plan

To display the status of workstations in the plan, perform the following steps:
1. Run a Status of All Workstations plan list. See Chapter 33, “Working with
lists,” on page 185.
The Status of all Workstations table displays in the Object list pane.

326 IBM Tivoli Workload Scheduler Job Scheduling Console: User’s Guide
 Managing distributed workstations in the plan

The table consists of the following:

Name The workstation instance name.
Jobman Running
Whether or not the Jobman process on the workstation is running.
Link Status The current link status of the workstation. A workstation can either
be LINKED or UNLINKED.
Writer Running
Whether the writer process is able to send messages from the
fault-tolerant agent to the master when the fault-tolerant agent is
directly connected to the master. Possible values are: Yes or blank
when the writer is down, or the state is unknown.
Limit The total number of jobs that can be run concurrently on this
workstation.
Fence The job fence for this workstation. The job fence is the priority a
job must exceed to run on this workstation. Setting the fence to 40,
for example, prevents jobs with priorities of 40 or less from being
launched. Valid values are from 0 to 101.
Node The type of workstation and operating system in the format
os_wkstat.
Possible os values are:
WNT Windows.
UNIX UNIX.
Other Other workstation operating system.

Possible wkstat values are:

FTA Fault-tolerant agent.
Master Master.
Manager Domain manager.
SAGENT Standard agent.
XAGENT Extended agent.
Time Zone The time zone of the workstation.
Node Port The port address of the workstation.
CPU Type The scheduler workstation type. Possible values are:
FTA Fault-tolerant agent.
MASTER Master.
MANAGER Domain manager.
SAGENT Standard agent.
XAGENT Extended agent.

Chapter 50. Managing workstations in the plan 327

Managing distributed workstations in the plan

Host The scheduler workstation that is hosting this workstation

definition. For extended agents and network agents only.
Run The run number of the production plan of the workstation. This
number is used to synchronize the workstations in the network.
Start Time The date and time the batchman process started on the
workstation.
Jobman Init Whether the jobman process on the workstation completed its
startup initialization.
Method The name of the access method when the workstation is an
extended or network agent.
Domain The domain to which the workstation belongs.
Version The version of Tivoli Workload Scheduler installed on this
workstation.
Node Information
Operating system information about the workstation.
Node Name The node name of the workstation.
SSL Communication
Indicates whether the Secure Sockets Layer (SSL) protocol is
enabled.
Behind Firewall
Indicates that a firewall exists between the workstation and its
domain manager.
SSL Port Indicates the number of the secure port used for SSL
communication.
Mailman Server
The name of the mailman server for the workstation.

Displaying distributed workstation instance properties

To display a workstation instance in the plan, perform the following steps:
1. Run a Status of All Workstations plan list. See Chapter 33, “Working with
lists,” on page 185.
2. Right-click the workstation and select Properties from the pop-up menu.
The Properties - Workstation in Plan panel displays. For descriptions of the
field values, see “Displaying the status of distributed workstations in the plan”
on page 326.

Changing the job limit of a workstation in the plan

To change the job limit of a workstation instance in the plan, perform the following
steps:
1. Run a Status of All Workstations plan list. See Chapter 33, “Working with
lists,” on page 185.
2. Right-click the workstation you want to modify and select Limit from the
pop-up menu.
The Change Limit - Workstation panel displays.
3. Specify a new job limit in the New Limit field.

328 IBM Tivoli Workload Scheduler Job Scheduling Console: User’s Guide
 Managing distributed workstations in the plan

Changing the job fence of a workstation in the plan

To change the job fence of a workstation instance in the plan, perform the
following steps:
1. Run a list of workstations. See Chapter 33, “Working with lists,” on page 185.
2. In the list results, right-click the workstation you want to modify.
3. Select Fence from the pop-up menu. The Change Fence - Workstation panel
displays.
4. Specify a new job fence value or click one of the following:
High Sets the fence to 100.
Go Sets the fence to 101.

Starting a workstation instance

To start Tivoli Workload Scheduler running on a workstation instance, in a list of
workstations, right-click the workstation you want to start and select Start from
the pop-up menu.

Note: To start all the workstations in a domain, refer to “Starting the workstations
in a domain” on page 341.

Stopping a workstation instance

To stop Tivoli Workload Scheduler running on a workstation instance, in a list of
workstations, right-click the workstation you want to stop and select Stop from the
pop-up menu.

Note: To stop all of the workstations in a domain, refer to “Stopping the

workstations in a domain” on page 341.

Linking a workstation instance

To link a workstation instance, right-click the workstation you want to link and
select Link from the pop-up menu.

Note: To link all of the workstations in a domain, refer to “Linking the

workstations in a domain” on page 341.

Unlinking a workstation instance

To unlink a workstation instance, right-click the workstation you want to stop and
select Unlink from the pop-up menu.

Note: To unlink all of the workstations in a domain, refer to “Unlinking the

workstations in a domain” on page 342.

Chapter 50. Managing workstations in the plan 329

Managing distributed workstations in the plan

330 IBM Tivoli Workload Scheduler Job Scheduling Console: User’s Guide
Chapter 51. Managing resources in the plan
This chapter describes how you manage resources in the plan. It is divided into the
following sections:
v “Managing z/OS resources”
v “Managing distributed resources” on page 335

Managing z/OS resources

This section describes how to monitor and update z/OS resources allocated to the
plan. It is divided into the following subsections:
v “Browsing and modifying resources”
v “Displaying the job instances associated with a resource” on page 333
v “Modifying job instances associated with a resource” on page 334

Browsing and modifying resources

To browse and modify the z/OS resources in the plan, perform the following steps:
1. Run a plan list of z/OS resources that contains the resource you want to
modify. See Chapter 33, “Working with lists,” on page 185.
2. Right-click the resource in the list and select Properties from the pop-up menu.
The Properties - Resource in Plan Resource page displays.

The changes you make to a resource in the current plan do not affect the resource
in the database.

General page
Use the General page to browse and modify general information about the
resource. Some of the information displayed is read-only.

The page consists of the following:

Name The name of the resource.
Description A description of the resource.
Hiperbatch Whether the resource is enabled for Hiperbatch.
Group ID The ID of the resource group.
Used for Select the type of use made of the resource. Possible values are:
v Planning
v Control
v Planning and control
v Neither planning nor control
On Error Specify the action to be taken if the job instance that allocates the
resource ends in error. Possible values are:
v Free
v Keep
v Free if exclusive
v Free if shared
v Assume system default
Deviation Specify a deviation in the resource quantity that must be available

© Copyright IBM Corp. 1991, 2006 331

 Managing z/OS resources in the plan

while the plan is running. To change the deviation, enter a value.

The deviation is an additional quantity with respect to the default
quantity. A value of 0 means that no change in quantity was made
for the plan.

Note: If you change the deviation, then verify in the Quantity

field the new total quantity available as the sum of the
default and deviation quantities. If you did not specify any
changes, the Deviation field displays 0, meaning that no
change in quantity was made for the plan.
Quantity Specify the quantity of the resource for the plan. It is the sum of
the default quantity and the deviation. The value that you enter in
this field overrides the value in the default Quantity field and
remains in effect for all future plans until you change it to blank.
| On complete Specify the action to take when the job finishes successfully
| (complete status). Possible values are:
| v Available
| v Unavailable
| v Automatically reset
| v Assume System Default
| Max Usage Limit
| Specifies the maximum number of allocations (quantity is not
| considered) after which the resource global availability is changed.
| The usage counter is increased each time an operation allocates the
| resource. When this internal counter reaches Max Usage Limit the
| global availability is changed as specified by Max Usage Type. The
| default is zero, which means that no usage counter check is done.
| Possible values for this field are between 0 and 999999.
| Max Usage Type
| Indicates how to change the resource availability when Max Usage
| Limit is exceeded. It is optional and is valid only if Max Usage
| Limit is nonzero. Possible values are:
| v Available
| v Unavailable
| v Automatically reset
| Usage Counter
| Contains the count of the current number of allocations. Change it
| to any value between 0 and Max Usage Limit.
| Available Indicates whether the resource is available in the plan.
| Last Updated Details of the most recent update of the resource in the plan, as
| follows:
| Updated by
| The user that updated the resource
| On The date and time of the update
| Last Change Action
| The change that was made. Possible values are:
| v Event Change
| v Max Usage Limit Change
| v On Complete Change
| v Lifespan Change

332 IBM Tivoli Workload Scheduler Job Scheduling Console: User’s Guide
 Managing z/OS resources in the plan

| v Usage Counter Increase

| Active Lifespan
| The expiry date and action for the resource, as follows:
| Action
| The action that the system takes when the resource expires.
| The global availability will be switched to one of the
| following:
| v Available
| v Unavailable
| v Automatically reset
| Expiration Date
| The date and time when the resource expires.
| v Expiration Date -
Default Modify the default Is Available and Quantity values.

Note: Updates in the Quantity and Deviation fields are retained also through plan
extensions, unless they are changed manually.

Default Workstations page

Use the Default Workstations page to add and remove default workstations.

Availability Intervals page

Use the Availability Intervals page to add, remove, or modify the availability of
the resource.

The table consists of the following:

Date Select the date when the resource is available.
From Time Specify the time at which the resource becomes available.
To Time Specify the time from which the resource is no longer available.
Quantity Specify the quantity of the resource that is available during the
availability interval.
Is Available Specify whether the resource is available or not available during
the availability interval. Possible values are:
v Available
v Not available
v Default
Default uses the value specified in the database.
Workstations View the workstations defined for the resource. You can also
modify the workstations defined in the “Default Workstations
page.”

To add an availability interval, click .

To remove an availability interval select it and click .

Displaying the job instances associated with a resource

To display the job instances associated with a resource, perform the following
steps:

Chapter 51. Managing resources in the plan 333

 Managing z/OS resources in the plan

1. Run a plan list that contains the resource you want to view. See Chapter 33,
“Working with lists,” on page 185.
2. Right-click the resource and select List Jobs  Waiting for Resource or Using
Resource.

All the job instances scheduled to use the resource and in the status you selected
are displayed in the bottom pane of the panel.

Modifying job instances associated with a resource

To modify job instances associated with a resource, perform the following steps:
1. Run a plan list that contains the resource you want to view. See Chapter 33,
“Working with lists,” on page 185.
2. Right-click the resource and select List Jobs  Waiting for Resource or Using
Resource.
3. Right-click the job instance in the table and select the relevant action from the
pop-up menu.
The actions you can perform on the job instance include:
| Properties
| Browse and modify the properties of the job instance.
| Dependencies
| Browse and modify the dependencies of the job instance.
| Delete Delete the job instance from the plan.
| Hold Hold the job instance.
| Release
| Release the job instance.
| Impact View
| Display predecessor and successor information of your job instance.
| Brows Job Log
| View the job instance log file.
| NOP Set the job instance to NOP.
| UN-NOP
| Set the job instance to UN-NOP.
| Execute
| Run the job instance immediately.
| Set Status
| Change the status of the job instance.
| Edit JCL
| Edit the JCL for the job instance.
| Browse Operation Instructions
| Browse the operation instructions associated to the job instance using the
| ISPF panels.
| Job Setup
| Tailor job statements.
| Restart
| Restart a job instance or a step and perform cleanup operations.

334 IBM Tivoli Workload Scheduler Job Scheduling Console: User’s Guide
 Managing z/OS resources in the plan

| Recovery Info
| Manage the recovery options.
| Automatic Recovery
| Manage the automatic recovery of the job instance.
| Critical Path
| View a list of all jobs that are on the critical path of the selected job
| instance.

For an explanation on how to use these options, see Chapter 48, “Managing z/OS
job instances,” on page 277.

Managing distributed resources

This section describes how to monitor and update distributed resources allocated
to the plan. It is divided into the following subsections:
v “Displaying resource dependencies status”
v “Displaying and modifying the properties of a resource dependency”
v “Changing the number of units of a resource dependency” on page 336

Displaying resource dependencies status

To display a list of resource dependencies in the plan, perform the following steps:
1. Run a Status of all Resources plan list. See Chapter 33, “Working with lists,”
on page 185.
The resource status table displays.
The table consists of the following:
Name The name of the resource.
Workstation The name of the workstation where the resource resides.
Status The status of the resource. Possible values are:
Available The resource has units available.
Not Available The resource has no units available.
Unknown The status of the resource is unknown.
Quantity Defined
The total number of units defined for the resource.
Quantity Available
The number resource units that are not in use.
In Use The number of resource units that are currently in use.
| Holders The names of job and job stream instances that require units of the
| resource and the number of units required.

Displaying and modifying the properties of a resource

dependency
To display a resource dependency in the plan, perform the following steps:
1. Run a Status of all Resources plan list. See Chapter 33, “Working with lists,”
on page 185.
2. Right-click the resource in a resource list and choose Properties from the
pop-up menu.
The Properties - Resource in Plan panel displays.

Chapter 51. Managing resources in the plan 335

Managing distributed resource dependencies in the plan

3. Change the units of the resource as required.

Changing the number of units of a resource dependency

To change the total number of defined units of a resource dependency, perform the
following steps:
1. Run a Status of all Resources plan list. See Chapter 33, “Working with lists,”
on page 185.
2. In the list results, right-click the resource you want to modify and select
Change Units from the pop-up menu.
The Change Units - Resource in Plan panel displays.

3. Specify a new Quantity Defined value.

336 IBM Tivoli Workload Scheduler Job Scheduling Console: User’s Guide
Chapter 52. Managing distributed file dependencies in the
plan
This chapter describes how you manage distributed file dependencies in the plan.
It is divided into the following sections:
v “Displaying file dependencies status”

Displaying file dependencies status

To display a list of file dependency states in the plan, perform the following step:
1. Run a Status of All Files plan list. See Chapter 33, “Working with lists,” on
page 185.
The Status of all Files table displays.

The table consists of the following:

Full Path Name
The path and name of the file.
Workstation The name of the workstation that owns the file.
Qualifiers Any qualifiers used with this file dependency. See “Files page” on
page 152.
Status The status of the file. Possible values are:
Not Checked Not yet checked or the file was available and used
to satisfy a job or job stream dependency.
Checking File availability is being checked.
Exists The file exists and is available.
Does Not Exist
The file does not exist or is not available.

© Copyright IBM Corp. 1991, 2006 337

338 IBM Tivoli Workload Scheduler Job Scheduling Console: User’s Guide
Chapter 53. Managing distributed prompt dependencies in the
plan
This chapter describes how you manage distributed prompt dependencies in the
plan. It is divided into the following sections:
v “Displaying prompt dependencies status”
v “Replying to a prompt dependency”

Displaying prompt dependencies status

To display a list of prompt dependencies states in the plan, perform the following
steps:
1. Run a Status of all Prompts plan list. See Chapter 33, “Working with lists,” on
page 185.
The Status of all Prompts table displays.
The table consists of the following:
Name The name of a predefined prompt or the number of an ad hoc
prompt.
Dependency The jobs or job stream names that are dependent on this prompt.
Release Status
The status of the prompt. Possible values are:
ASKED The prompt has been issued, but no response has
been received.
NOT ASKED The prompt has not been issued.
YES The prompt has been issued and a YES response
has been received.
NO The prompt has been issued and a NO response
has been received.
Number The internal ID of the prompt.
Type The prompt type. Possible values are:
Ad Hoc The prompt is locally defined in a job or job
stream.
Predefined The prompt has a name and is defined in the
database.
Recovery The prompt is locally defined in a job as a recovery
prompt.
Message Text The text of the prompt message.

Replying to a prompt dependency

To reply to a prompt dependency, perform the following steps:
1. Run a Status of all Prompts plan list. See Chapter 33, “Working with lists,” on
page 185.
2. In the list results, right-click the prompt dependency you want to reply to.
3. Select Reply then Yes, or Reply then No from the pop-up menu.

© Copyright IBM Corp. 1991, 2006 339

Replying to a prompt dependency

340 IBM Tivoli Workload Scheduler Job Scheduling Console: User’s Guide
Chapter 54. Managing domains in the plan
This chapter describes how you manage domains in the plan. It is divided into the
following sections:
v “Starting the workstations in a domain”
v “Stopping the workstations in a domain”
v “Linking the workstations in a domain”
v “Unlinking the workstations in a domain” on page 342
v “Switching the domain manager in a domain” on page 342

Starting the workstations in a domain

To start Tivoli Workload Scheduler running on all of the workstations in a domain:
1. Run a Status of all Domains plan list. See Chapter 33, “Working with lists,” on
page 185.
The Status of all Domains table displays.
2. Right-click the domain you want to start and select Start Workstations from
the pop-up menu..

Note: To start individual workstations, see “Starting a workstation instance” on

page 329.

Stopping the workstations in a domain

To stop Tivoli Workload Scheduler running on all of the workstations in a domain:
1. Run a Status of all Domains plan list. See Chapter 33, “Working with lists,” on
page 185.
The Status of all Domains table displays.
2. Right-click the domain you want to stop and select Stop Workstations from the
pop-up menu.

Note: To stop individual workstations, see “Stopping a workstation instance” on

page 329.

Linking the workstations in a domain

To link all of the workstations in a domain, perform the following steps:
1. Run a Status of all Domains plan list. See Chapter 33, “Working with lists,” on
page 185.
The Status of all Domains table displays.
2. Right-click the domain you want to link and select Link Workstations from the
pop-up menu.

Note: To link individual workstations, see “Linking a workstation instance” on

page 329.

© Copyright IBM Corp. 1991, 2006 341

 Unlinking the workstations in a domain

Unlinking the workstations in a domain

To unlink all of the workstations in a domain, perform the following steps:
1. Run a Status of all Domains plan list. See Chapter 33, “Working with lists,” on
page 185.
The Status of all Domains table displays.
2. Right-click the domain you want to unlink and select Unlink Workstations
from the pop-up menu.

Note: To unlink individual workstations, see “Unlinking a workstation instance”

on page 329.

Switching the domain manager in a domain

To switch the domain manager to a different workstation in a domain, perform the
following steps:
1. Run a Status of all Domains plan list. See Chapter 33, “Working with lists,” on
page 185.
The Status of all Domains table displays.
2. Right-click the domain and select Switch Manager from the pop-up menu.
The Switch manager - Domain panel displays.
| 3. Type the name of the domain or click ... (find) to search for and add the name
| of the new domain manager workstation. The new domain manager must be a
| member of the domain and it must be a fault-tolerant agent with Full Status
| selected or a workstation that you defined as backup master domain manager.

342 IBM Tivoli Workload Scheduler Job Scheduling Console: User’s Guide
Chapter 55. Changing Windows user passwords in the plan
This chapter describes how to change a Windows user password in the plan. To
change a Windows user password in the plan, perform the following steps:
1. In the Actions list pane, select Change Password.
2. Select the engine.
The Change Password panel displays.

Note: When you change a Windows user password, it is only relevant to the
current plan. Jnextplan restores the Windows user password the next time it
is run.

The panel consists of the following:

Name The name of the user whose password you are changing. Click ... (find) to
search for and select the user.
Windows Domain
The domain of the Windows user whose password you are changing. If
you used ... (find) to find the user, this information is completed
automatically when relevant.
Windows Workstation
The workstation of the user whose password you are changing. If you
used ... (find) to find the user, this information is completed automatically
when relevant.
New Password
Type the new password for the user. This password is restored to the
database password the next time jnextplan is run.
Confirmation
Confirm the new password.

© Copyright IBM Corp. 1991, 2006 343

344 IBM Tivoli Workload Scheduler Job Scheduling Console: User’s Guide
 Chapter 56. Setting an alternate plan
| This chapter describes how you can set a plan different from the production plan
| to analyze it and query on the objects in it.

To select a plan different from the production plan, perform the following steps:
1. In the Actions list pane, open Set alternate plan.
2. Select the engine.
The Set Alternate Plan Files panel displays.

The panel consists of the following:

Symphony Type
| The type of plan you want to set. Possible values are:
| v Trial
| v Forecast
| v Archived
Filename The name of the log file assigned by the stageman command.
Schedule Date
The date the schedule file was created.
Last Updated The time the symphony file was last updated.

© Copyright IBM Corp. 1991, 2006 345

Setting an alternate plan

Start Time The actual date and time the plan began running. This column is
blank for trial and forecast plans.
Run Number The run number of times the plan was run. For trial and forecast
plans this is always 0.
Size The size of the log file, in records.
Plan Start The lowermost limit of plan extension expressed as date and time.
Plan End The uppermost limit of plan extension expressed as date and time.

346 IBM Tivoli Workload Scheduler Job Scheduling Console: User’s Guide
|

| Chapter 57. Restoring a plan

| This chapter describes how you can restore the production plan after having set a
| plan different from it using the procedure described in Chapter 56, “Setting an
| alternate plan,” on page 345.

| To restore a plan, perform the following steps:

| 1. In the Actions list pane, open Restore plan.
| 2. Select the engine. The following message displays:
| The restore plan has been completed successfully

© Copyright IBM Corp. 1991, 2006 347

Restoring a plan

348 IBM Tivoli Workload Scheduler Job Scheduling Console: User’s Guide
|

Part 8. Troubleshooting

© Copyright IBM Corp. 1991, 2006 349

350 IBM Tivoli Workload Scheduler Job Scheduling Console: User’s Guide
Chapter 58. Setting traces for the Job Scheduling Console
This chapter explains how to set tracing facilities for the Job Scheduling Console.

The first time you log in to the Job Scheduling Console, the logging.properties
configuration file is copied to the user home directory in the .twsconsole
subdirectory. This procedure prevents the information in the logging.properties
file from being overwritten when another user logs in to the Job Scheduling
Console. If you want to refresh the file contents, you can rename or move the
existing logging.properties file so that the Job Scheduling Console creates a new
one when you next log in.

Table 9 defines the keys in the logging.properties file that you can customize.
Table 9. Logging properties keys
Key Function
com.tivoli.logging Enables and disables the tracing function. Possible values
are true and false. The default value is false.
com.tivoli.level Sets the error level to be recorded in the log file. Possible
values are as follows:
OFF No data is traced.
INFO Informational messages are traced.
WARNING
Warning information is traced.
ERROR
Error information is traced. ERROR is the default.
FATAL Information on fatal errors is traced.
ALL All of the above data is traced.

All tracing levels, excluding OFF, also include the data

recorded by lower tracing levels.
handler.file.fileName Specifies the name for the log file. The file is created in
.xml format.
handler.file.fileDir Specifies the path where the log file is created. When you
first log in to the Job Scheduling Console, the default
value for the log file directory is changed to
user_home_directory/.twsconsole/userdata. This
procedure prevents the information in the log file being
overwritten when another user logs in to the Job
Scheduling Console.

handler.file.maxFiles Specifies the maximum number of log files that can be

created. The default value is 3.
handler.file.maxFileSize Specifies the maximum size of the log files. The default
value is 3072. If this value is exceeded, a new file is
created. If the maximum number of log files is exceeded,
the log files are overwritten in the order they were created.
handler.file.appending Specifies whether the new information is appended in the
log file, or if a new file is created. Possible values are true
and false. The default value is false.

© Copyright IBM Corp. 1991, 2006 351

Setting traces

352 IBM Tivoli Workload Scheduler Job Scheduling Console: User’s Guide
Chapter 59. Troubleshooting
This chapter provides information to help you diagnose common problems
encountered with the Job Scheduling Console.

Note: For UNIX operating systems when the user does not have a home directory
set, logs, errors, and stdout data are written to the stdout file and any user
customization is not saved.
It is divided into the following sections:
v “Installation troubleshooting”
v “General troubleshooting” on page 354

Installation troubleshooting
This section describes how to locate the installation log files that assist you in
finding and repairing installation problems.

Job Scheduling Console installation log

When using the installation wizard, a log file is generated in the following
location:

on Windows operating systems:

C:\Documents and Settings\<user_name>\Local Settings\Temp

on UNIX and Linux operating systems:

<user_home_dir>/tmp

The log file names are twsconsole_ismp.log (ISMP) and TWSJSC^8.3.log (Software
Distribution).

Connector installation log

When using the installation wizard, a log file is created in the following location:

on Windows operating systems:

C:\Documents and Settings\<username>\Local Settings\Temp

on UNIX and Linux operating systems:

<user_home_dir>/temp

The log file name is tws4zosconn.log.

Installation troubleshooting
The following problems might be encountered:
Symptom: When performing a language pack installation, or an uninstall, the
installation wizard does not start.
Cause and solution:
This is probably due to the fact that installation wizard cannot find the
user profile necessary to set the TWS_JDKHOME environment variable.

© Copyright IBM Corp. 1991, 2006 353

Troubleshooting

Make sure that the TWS_JDKHOME environment variable is set. If it is

not set, set it using is:javahome jsc_installation_path\jvm_path where for
HP-UX and Solaris systems the path to specify is jsc_installation_path\
tools\_jvm\bin and for all other systems jsc_installation_path\tools\
_jvm\jre\bin.
Symptom: Installation fails on AIX with the messages "DISSE0125E Error
writing file <filename and path>" and "DISSE0005E Operation unsuccessful. An
error occurred and the product installation failed. Look at the log file
/tmp/twsconsole_ismp.log for details."
Cause and solution:
The installation wizard does detect the lack of file space, but does not
allocate sufficient space to successfully perform the installation. The
following rules should be considered:
v When file system expansion is required a warning is given in the
summary panel of the installation wizard. You can choose to cancel
installation if you do not want to expand the file system.
v When you are performing a silent installation, file system expansion is
automatic.
v Only installation file systems can be expanded. File system expansion of
temporary directories does not occur and therefore sufficient temporary
directory space must be allocated before starting installation.
v Only a root user can expand the file system. If installation is performed
by a non-root user the file system expansion does not occur.
v To prevent over expansion of the root file system on AIX versions earlier
than version 5.0 you should create a separate file system for the default
installation directory /opt/.
Symptom: For Windows operating systems, after starting the Job Scheduling
Console installation the launch crashes after the splash screen and a system
reboot is performed.
The installation launch seems to have been successful, however the
installation hangs after the splash screen.
Cause and solution:
This problem is a known incompatibility issue between the Java rendering
engine and DirectDraw acceleration. The problem is also related to the
type of video card on your system.
You can resolve this problem performing the following steps:
1. Click Start  Run in the Windows task bar.
2. Type dxdiag and click OK.
The DirectX Diagnostic tool displays.
Click on Display and disable DirectDraw Acceleration and Direct3D
Acceleration.

General troubleshooting
This section describes general problems that you might encounter.

The tracing of Job Scheduling Console errors is optional. See Chapter 58, “Setting
traces for the Job Scheduling Console,” on page 351.

The following problems might be encountered:

354 IBM Tivoli Workload Scheduler Job Scheduling Console: User’s Guide
 Troubleshooting

Symptom: When working with the Job Scheduling Console a request fails with
a message similar to the following:
GJS0012E The job stream cannot load. Reason: AWSJCO005E WebSphere
Application Server has given the following error: CORBA COMM_FAILURE
0x49421070 No; nested exception is: org.omg.CORBA.COMM_FAILURE:
CONNECT_FAILURE_ON_SSL_CLIENT_SOCKET - JSSL0130E:
java.io.IOException: Signals that an I/O exception of some sort has occurred.
Reason: Connection refused: connect vmcid: 0x49421000 minor code: 70
completed: No.
A similar message appears for any task you attempt to perform.
Cause and solution:
The connector has been stopped and restarted. Close and reopen the Job
Scheduling Console.
Symptom: When working with the Job Scheduling Console from a remote
connection there are problems with screen repainting.
An error message displays indicating problems with repainting. When you
close the message, the Job Scheduling Console continues normally.
Cause and solution:
This problem occurs when you are connecting using a remote terminal
connector that is not supported. You can remotely connect to the Job
Scheduling Console using Exceed or Terminal Server only.
Symptom: When you open the job stream editor, the buttons in the toolbar are
not visible.
Buttons for Add Job Definition, Add Dependency on Internetwork, Add
Dependency on External Job, Add Dependency on External Job Stream,
Add Links.
Cause and solution:
This problem is a known incompatibility issue between the Java rendering
engine and DirectDraw acceleration. The problem is also related to the
type of video card on your system.
You can resolve this problem performing the following steps:
1. Click Start  Run in the Windows task bar.
2. Type dxdiag and click OK.
The DirectX Diagnostic tool opens.
Click on Display and disable DirectDraw Acceleration and Direct3D
Acceleration.
Symptom: After starting the Job Scheduling Console and entering the user
name, server, and password data the launch hangs.
The launch seems to have been successful, however the initial window of
the panel hangs in a grey state.
Cause and solution:
This problem is a known incompatibility issue between the Java rendering
engine and DirectDraw acceleration. The problem is also related to the
type of video card on your system.
You can resolve this problem performing the following steps:
1. Click Start  Run in the Windows task bar.
2. Type dxdiag and click OK.
The DirectX Diagnostic tool opens.

Chapter 59. Troubleshooting 355

Troubleshooting

Click on Display and disable DirectDraw Acceleration and Direct3D

Acceleration.
Symptom: The installation wizard, or the Job Scheduling Console will not start.
When you are attempting to start the installation wizard, or the Job
Scheduling Console, nothing happens.
Cause and solution:
This usually occurs when you are running JRE 1.4.2 for Linux Red Hat
Advanced Server 3.0 because it only supports KDE graphical environments
and not Gnome.
Symptom: The job stream definition process hangs and must be stopped.
When creating a job stream, the process hangs and you must manually
stop it.
Cause and solution:
This usually occurs when you are using a calendar that is too large for
your system RAM to handle. For example, the maximum calendar size for
a workstation with 256 MB RAM is 1000 days.
Create a new calendar with a size that is less than that you are currently
trying to use, estimating 1000 days for every 256 MB of RAM.

Repairing the installation

In case the installed Job Scheduling Console is damaged or corrupted, you can
repair the installation. To repair the installation, complete the following steps:
1. Navigate to the JSC directory. See “The installation CDs” on page 9.
2. Run the setup according to the operating system where you are installing:
v Windows operating systems: setup.exe
v UNIX and Linux operating systems: ./setup.bin
3. Select the language of the installation wizard. Click OK.
4. Read the welcome information. Click Next.
5. Select Repair installation. Click Next.
6. Review the installation settings. Click Next. The installation is started.
7. When the installation completes, a panel displays a successful installation or
contains a list of which items failed to install and the location of the log file
containing the details of the errors.
8. Click Finish.

356 IBM Tivoli Workload Scheduler Job Scheduling Console: User’s Guide
Chapter 60. Job Scheduling Console messages
This chapter lists the Job Scheduling Console messages. Many of the messages
refer directly to the engine messages, and should be read in conjunction with the
IBM Tivoli Workload Scheduler: Administration and Troubleshooting. When a message is
related to an engine message, the engine message number is returned as the reason
code.

It is divided into the following message sets:

“Job Scheduling Console base messages”
These messages are common to both the z/OS and distributed
environments.
“Job Scheduling Console z/OS messages” on page 376
These messages are unique to the z/OS environment.
“Job Scheduling Console distributed messages” on page 382
These messages are unique to the distributed environment.
“Job Scheduling Console starting and stopping messages” on page 406
These messages are issued when the Job Scheduling Console starts
or finishes.

Job Scheduling Console base messages

Administration and Troubleshooting manual.
GJS0001E The job stream list cannot load.
Reason: VALUE_0
GJS0003E The resource list cannot load.
Explanation: The job stream list could not be loaded
Reason: VALUE_0
due to an error that occurred in the Tivoli Workload
Scheduler engine. The error code is specified in the Explanation: The resource list could not be loaded
message text. due to an error that occurred in the Tivoli Workload
Scheduler engine. The error code is specified in the
System action: The requested action did not complete
message text.
successfully.
System action: The requested action did not complete
Operator response: The reason displayed in the
successfully.
message text represents an error code reported by the
Tivoli Workload Scheduler engine. Refer to the Operator response: The reason displayed in the
Administration and Troubleshooting manual. message text represents an error code reported by the
Tivoli Workload Scheduler engine. Refer to the
See also:: com.tivoli.jsc.views.JsBaseNavigator method
Administration and Troubleshooting manual.
runQuery()
See also:: com.tivoli.jsc.views.JSResourceQueryGUI
method runQuery()
GJS0002E The plan view cannot load.
Reason: VALUE_0
GJS0004E The resource plan view cannot load.
Explanation: The plan view could not be loaded due
Reason: VALUE_0
to an error that occurred in the Tivoli Workload
Scheduler engine. The error code is specified in the Explanation: The resource plan view could not be
message text. loaded due to an error that occurred in the Tivoli
Workload Scheduler engine. The error code is specified
System action: The requested action did not complete
in the message text.
successfully.
System action: The requested action did not complete
Operator response: The reason displayed in the
successfully.
message text represents an error code reported by the
Tivoli Workload Scheduler engine. Refer to the Operator response: The reason displayed in the

© Copyright IBM Corp. 1991, 2006 357

GJS0005E • GJS0012E

message text represents an error code reported by the System action: The requested action did not complete
Tivoli Workload Scheduler engine. Refer to the successfully.
Administration and Troubleshooting manual.
Operator response: The reason displayed in the
message text represents an error code reported by the
GJS0005E The workstation list cannot load. Tivoli Workload Scheduler engine. Refer to the
Reason: VALUE_0 Administration and Troubleshooting manual.
Explanation: The workstation list could not be loaded
due to an error that occurred in the Tivoli Workload GJS0009E The Job Stream Instance Editor cannot
Scheduler engine. The error code is specified in the open.
message text. Reason: VALUE_0
System action: The requested action did not complete Explanation: The Job Stream Instance Editor could not
successfully. be opened due to an error that occurred in the Tivoli
Workload Scheduler engine. The error code is specified
Operator response: The reason displayed in the
in the message text.
message text represents an error code reported by the
Tivoli Workload Scheduler engine. Refer to the System action: The requested action did not complete
Administration and Troubleshooting manual. successfully.
See also:: com.tivoli.jsc.views.JSWorkstationQueryGUI Operator response: The reason displayed in the
method runQuery() message text represents an error code reported by the
Tivoli Workload Scheduler engine. Refer to the
Administration and Troubleshooting manual.
GJS0006E The job stream instance VALUE_0
cannot open.
Reason: VALUE_1 GJS0010E The Resource Editor cannot open.
Reason: VALUE_0
Explanation: The job stream instance could not be
loaded due to an error that occurred in the Tivoli Explanation: The Resource Editor could not be
Workload Scheduler engine. The error code is specified updated due to an error that occurred in the Tivoli
in the message text. Workload Scheduler engine. The error code is specified
in the message text.
System action: The requested action did not complete
successfully. System action: The requested action did not complete
successfully.
Operator response: The reason displayed in the
message text represents an error code reported by the Operator response: The reason displayed in the
Tivoli Workload Scheduler engine. Refer to the message text represents an error code reported by the
Administration and Troubleshooting manual. Tivoli Workload Scheduler engine. Refer to the
Administration and Troubleshooting manual.
GJS0007E The job stream VALUE_0 cannot be
updated. GJS0011E The structure cannot build.
Reason: VALUE_1 Reason: VALUE_0
Explanation: The job stream could not be updated due Explanation: The structure could not be built due to
to an error that occurred in the Tivoli Workload an error that occurred in the Tivoli Workload Scheduler
Scheduler engine. The error code is specified in the engine. The error code is specified in the message text.
message text.
System action: The requested action did not complete
System action: The requested action did not complete successfully.
successfully.
Operator response: The reason displayed in the
Operator response: The reason displayed in the message text represents an error code reported by the
message text represents an error code reported by the Tivoli Workload Scheduler engine. Refer to the
Tivoli Workload Scheduler engine. Refer to the Administration and Troubleshooting manual.
Administration and Troubleshooting manual.
GJS0012E The job stream cannot load.
GJS0008E The Job Stream Editor cannot open. Reason: VALUE_0
Reason: VALUE_0
Explanation: The job stream could not be loaded due
Explanation: The Job Stream Editor could not be to an error that occurred in the Tivoli Workload
opened due to an error that occurred in the Tivoli Scheduler engine. The error code is specified in the
Workload Scheduler engine. The error code is specified message text.
in the message text.

358 IBM Tivoli Workload Scheduler Job Scheduling Console: User’s Guide
 GJS0013E • GJS0021E

System action: The requested action did not complete System action: The requested action did not complete
successfully. successfully.
Operator response: The reason displayed in the Operator response: The reason displayed in the
message text represents an error code reported by the message text represents an error code reported by the
Tivoli Workload Scheduler engine. Refer to the Tivoli Workload Scheduler engine. Refer to the
Administration and Troubleshooting manual. Administration and Troubleshooting manual.

GJS0013E The resource availability definition GJS0017E The resource VALUE_0 cannot be saved.
cannot load. Reason: VALUE_1
Reason: VALUE_0
Explanation: The resource could not be saved due to
Explanation: The resource availability definition could an error that occurred in the Tivoli Workload Scheduler
not be loaded due to an error that occurred in the engine. The error code is specified in the message text.
Tivoli Workload Scheduler engine. The error code is
System action: The requested action did not complete
specified in the message text.
successfully.
System action: The requested action did not complete
Operator response: The reason displayed in the
successfully.
message text represents an error code reported by the
Operator response: The reason displayed in the Tivoli Workload Scheduler engine. Refer to the
message text represents an error code reported by the Administration and Troubleshooting manual.
Tivoli Workload Scheduler engine. Refer to the
Administration and Troubleshooting manual.
GJS0018E The dependency cannot be added.
Explanation: The dependency between the jobs could
GJS0014E The job stream cannot be saved if it
not be added because they are in the same job stream.
does not contain at least one job.
Reason: VALUE_0 System action: The requested action did not complete
successfully.
Explanation: Before saving a job stream it is necessary
to insert a job. Operator response: Select a dependency on a job that
is in another job stream.
System action: The requested action did not complete
successfully.
GJS0019E All of the fields in this window are
Operator response: The reason displayed in the
obligatory.
message text represents an error code reported by the
Tivoli Workload Scheduler engine. Refer to the Error Explanation: All of the fields in this window are
Messages Manual for a recovery action. required fields.
System action: The requested action did not complete
GJS0015E The job stream cannot be saved. successfully.
Reason: VALUE_0
Operator response: Complete all the fields in the
Explanation: The job stream could not be saved due window before pressing OK.
to an error that occurred in the Tivoli Workload
Scheduler engine. The error code is specified in the
message text. GJS0020E The jobs in the job stream instance were
not found. Type different filter criteria
System action: The requested action did not complete and run the list again.
successfully.
Explanation: The jobs in the job stream instance were
Operator response: The reason displayed in the not found.
message text represents an error code reported by the
Tivoli Workload Scheduler engine. Refer to the System action: The jobs list is shown as empty.
Administration and Troubleshooting manual. Operator response: Try a new list by specifying
different filter criteria.
GJS0016E The resource VALUE_0 cannot be saved.
Reason: VALUE_1 GJS0021E The job stream instance was not found.
Explanation: The resource could not be saved due to Type different filter criteria and run the
an error that occurred in the Tivoli Workload Scheduler list again.
engine. The error code is specified in the message text. Explanation: The job stream instance was not found.

Chapter 60. Job Scheduling Console messages 359

GJS0022E • GJS0030E

System action: The requested action did not complete

GJS0027E The workstation VALUE_0 cannot be
successfully.
saved.
Operator response: Type different filter criteria and Reason: VALUE_1
run the list again.
Explanation: The workstation could not be updated
due to an error that occurred in the Tivoli Workload
GJS0022E The dependency cannot be created Scheduler engine. The error code is specified in the
because it creates a loop. Define a valid message text.
dependency.
System action: The requested action did not complete
Explanation: The current dependency cannot be successfully.
created because it produces a loop.
Operator response: The reason displayed in the
System action: The requested action did not complete message text represents an error code reported by the
successfully. Tivoli Workload Scheduler engine. Refer to the
Administration and Troubleshooting manual.
Operator response: Define a valid dependency.

GJS0028E Class Cast Exception.

GJS0024E A job stream must be saved in the Reason: VALUE_0
database before it can be scheduled.
Explanation: There was a class cast exception due to
Explanation: A job stream must be saved in the an error that occurred in the Tivoli Workload Scheduler
database before it can be scheduled. engine. The error code is specified in the message text.
System action: The requested action did not complete System action: The requested action did not complete
successfully. successfully.
Operator response: Save the job stream in the Operator response: The reason displayed in the
database and schedule it. message text represents an error code reported by the
Tivoli Workload Scheduler engine. Refer to the
GJS0025E The job stream instance cannot be Administration and Troubleshooting manual.
loaded because it is unknown. Try a
different name. GJS0029E There is a problem with the job
Explanation: The job stream name cannot be loaded scheduling engine.
because it is unknown. Reason: VALUE_0

System action: The requested action did not complete Explanation: There is a problem with the Tivoli
successfully. Workload Scheduler engine. The error code is specified
in the message text.
Operator response: Type a different name for the job
stream. System action: The requested action did not complete
successfully.

GJS0026E The workstation VALUE_0 cannot be Operator response: The reason displayed in the
saved. message text represents an error code reported by the
Reason: VALUE_1 Tivoli Workload Scheduler engine. Refer to the
Administration and Troubleshooting manual.
Explanation: The workstation could not be saved due
to an error that occurred in the Tivoli Workload
Scheduler engine. The error code is specified in the GJS0030E The window cannot close.
message text. Reason: VALUE_0

System action: The requested action did not complete Explanation: The window could not be closed due to
successfully. an error that occurred in the Tivoli Workload Scheduler
engine. The error code is specified in the message text.
Operator response: The reason displayed in the
message text represents an error code reported by the System action: The requested action did not complete
Tivoli Workload Scheduler engine. Refer to the successfully.
Administration and Troubleshooting manual. Operator response: The reason displayed in the
message text represents an error code reported by the
Tivoli Workload Scheduler engine. Refer to the
Administration and Troubleshooting manual.

360 IBM Tivoli Workload Scheduler Job Scheduling Console: User’s Guide
 GJS0031E • GJS0038E

GJS0031E The job dependency cannot be added. GJS0035E The instance cannot be modified.
Reason: VALUE_0 Reason: VALUE_0
Explanation: The job dependency could not be added Explanation: The instance could not be modified due
due to an error that occurred in the Tivoli Workload to an error that occurred in the Tivoli Workload
Scheduler engine. The error code is specified in the Scheduler engine. The error code is specified in the
message text. message text.
System action: The requested action did not complete System action: The requested action did not complete
successfully. successfully.
Operator response: The reason displayed in the Operator response: The reason displayed in the
message text represents an error code reported by the message text represents an error code reported by the
Tivoli Workload Scheduler engine. Refer to the Tivoli Workload Scheduler engine. Refer to the
Administration and Troubleshooting manual. Administration and Troubleshooting manual.

GJS0032E The OK request cannot process. GJS0036E The instance cannot be deleted.
Reason: VALUE_0 Reason: VALUE_0
Explanation: The OK request could not be processed Explanation: The instance could not be deleted due to
due to an error that occurred in the Tivoli Workload an error that occurred in the Tivoli Workload Scheduler
Scheduler engine. The error code is specified in the engine. The error code is specified in the message text.
message text.
System action: The requested action did not complete
System action: The requested action did not complete successfully.
successfully.
Operator response: The reason displayed in the
Operator response: The reason displayed in the message text represents an error code reported by the
message text represents an error code reported by the Tivoli Workload Scheduler engine. Refer to the
Tivoli Workload Scheduler engine. Refer to the Administration and Troubleshooting manual.
Administration and Troubleshooting manual.
GJS0037E The instance cannot be held.
GJS0033E The job cannot be changed. Reason: VALUE_0
Reason: VALUE_0
Explanation: The instance could not be held due to an
Explanation: The job could not be changed due to an error that occurred in the Tivoli Workload Scheduler
error that occurred in the Tivoli Workload Scheduler engine. The error code is specified in the message text.
engine. The error code is specified in the message text.
System action: The requested action did not complete
System action: The requested action did not complete successfully.
successfully.
Operator response: The reason displayed in the
Operator response: The reason displayed in the message text represents an error code reported by the
message text represents an error code reported by the Tivoli Workload Scheduler engine. Refer to the
Tivoli Workload Scheduler engine. Refer to the Administration and Troubleshooting manual.
Administration and Troubleshooting manual.
GJS0038E The instance cannot be released.
GJS0034E The job cannot be added. Reason: VALUE_0
Reason: VALUE_0
Explanation: The instance could not be released due
Explanation: The job could not be added due to an to an error that occurred in the Tivoli Workload
error that occurred in the Tivoli Workload Scheduler Scheduler engine. The error code is specified in the
engine. The error code is specified in the message text. message text.
System action: The requested action did not complete System action: The requested action did not complete
successfully. successfully.
Operator response: The reason displayed in the Operator response: The reason displayed in the
message text represents an error code reported by the message text represents an error code reported by the
Tivoli Workload Scheduler engine. Refer to the Tivoli Workload Scheduler engine. Refer to the
Administration and Troubleshooting manual. Administration and Troubleshooting manual.

Chapter 60. Job Scheduling Console messages 361

GJS0039E • GJS0046E

GJS0039E The object cannot be deleted. GJS0043E The job dependency cannot be removed.
Reason: VALUE_0 Reason: VALUE_0
Explanation: The object could not be deleted due to Explanation: The job dependency could not be
an error that occurred in the Tivoli Workload Scheduler removed due to an error that occurred in the Tivoli
engine. The error code is specified in the message text. Workload Scheduler engine. The error code is specified
in the message text.
System action: The requested action did not complete
successfully. System action: The requested action did not complete
successfully.
Operator response: The reason displayed in the
message text represents an error code reported by the Operator response: The reason displayed in the
Tivoli Workload Scheduler engine. Refer to the message text represents an error code reported by the
Administration and Troubleshooting manual. Tivoli Workload Scheduler engine. Refer to the
Administration and Troubleshooting manual.
GJS0040E The object cannot be undeleted.
Reason: VALUE_0 GJS0044E The dependency cannot be removed.
Reason: VALUE_0
Explanation: The object could not be undeleted due to
an error that occurred in the Tivoli Workload Scheduler Explanation: The dependency could not be removed
engine. The error code is specified in the message text. due to an error that occurred in the Tivoli Workload
Scheduler engine. The error code is specified in the
System action: The requested action did not complete
message text.
successfully.
System action: The requested action did not complete
Operator response: The reason displayed in the
successfully.
message text represents an error code reported by the
Tivoli Workload Scheduler engine. Refer to the Operator response: The reason displayed in the
Administration and Troubleshooting manual. message text represents an error code reported by the
Tivoli Workload Scheduler engine. Refer to the
Administration and Troubleshooting manual.
GJS0041E The status in the database cannot be
modified.
Reason: VALUE_0 GJS0045E The external dependency cannot be
removed.
Explanation: The status in the database could not be
Reason: VALUE_0
modified due to an error that occurred in the Tivoli
Workload Scheduler engine. The error code is specified Explanation: The external dependency could not be
in the message text. removed due to an error that occurred in the Tivoli
Workload Scheduler engine. The error code is specified
System action: The requested action did not complete
in the message text.
successfully.
System action: The requested action did not complete
Operator response: The reason displayed in the
successfully.
message text represents an error code reported by the
Tivoli Workload Scheduler engine. Refer to the Operator response: The reason displayed in the
Administration and Troubleshooting manual. message text represents an error code reported by the
Tivoli Workload Scheduler engine. Refer to the
Administration and Troubleshooting manual.
GJS0042E The job cannot be removed.
Reason: VALUE_0
GJS0046E The action on the selected objects
Explanation: The job could not be removed due to an
cannot be performed.
error that occurred in the Tivoli Workload Scheduler
Reason: VALUE_0
engine. The error code is specified in the message text.
Explanation: The action could not be performed due
System action: The requested action did not complete
to an error that occurred in the Tivoli Workload
successfully.
Scheduler engine. The error code is specified in the
Operator response: The reason displayed in the message text.
message text represents an error code reported by the
System action: The requested action did not complete
Tivoli Workload Scheduler engine. Refer to the
successfully.
Administration and Troubleshooting manual.
Operator response: The reason displayed in the
message text represents an error code reported by the
Tivoli Workload Scheduler engine. Refer to the

362 IBM Tivoli Workload Scheduler Job Scheduling Console: User’s Guide
 GJS0047E • GJS0054E

Administration and Troubleshooting manual. Operator response: The reason displayed in the
message text represents an error code reported by the
Tivoli Workload Scheduler engine. Refer to the
GJS0047E The job stream operation cannot be
Administration and Troubleshooting manual.
performed.
Reason: VALUE_0
GJS0051E The action specified on the selected
Explanation: The job stream operation could not be
object cannot be performed.
performed due to an error that occurred in the Tivoli
Reason: VALUE_0
Workload Scheduler engine. The error code is specified
in the message text. Explanation: The action could not be performed due
to an error that occurred in the Tivoli Workload
System action: The requested action did not complete
Scheduler engine. The error code is specified in the
successfully.
message text.
Operator response: The reason displayed in the
System action: The requested action did not complete
message text represents an error code reported by the
successfully.
Tivoli Workload Scheduler engine. Refer to the
Administration and Troubleshooting manual. Operator response: The reason displayed in the
message text represents an error code reported by the
Tivoli Workload Scheduler engine. Refer to the
GJS0048E The action on the selected object cannot
Administration and Troubleshooting manual.
be performed.
Reason: VALUE_0
GJS0052E The action specified on the selected
Explanation: The actioncould not be performed due to
objects cannot be performed.
an error that occurred in the Tivoli Workload Scheduler
Reason: VALUE_0
engine. The error code is specified in the message text.
Explanation: The action could not be performed due
System action: The requested action did not complete
to an error that occurred in the Tivoli Workload
successfully.
Scheduler engine. The error code is specified in the
Operator response: The reason displayed in the message text.
message text represents an error code reported by the
System action: The requested action did not complete
Tivoli Workload Scheduler engine. Refer to the
successfully.
Administration and Troubleshooting manual.
Operator response: The reason displayed in the
message text represents an error code reported by the
GJS0049E The action on the selected objects
Tivoli Workload Scheduler engine. Refer to the
cannot be performed.
Administration and Troubleshooting manual.
Reason: VALUE_0
Explanation: The action could not be performed due
GJS0053E The action specified on the selected
to an error that occurred in the Tivoli Workload
objects cannot be performed.
Scheduler engine. The error code is specified in the
Reason: VALUE_0
message text.
Explanation: The action could not be performed due
System action: The requested action did not complete
to an error that occurred in the Tivoli Workload
successfully.
Scheduler engine. The error code is specified in the
Operator response: The reason displayed in the message text.
message text represents an error code reported by the
System action: The requested action did not complete
Tivoli Workload Scheduler engine. Refer to the
successfully.
Administration and Troubleshooting manual.
Operator response: The reason displayed in the
message text represents an error code reported by the
GJS0050E The instance cannot be updated from
Tivoli Workload Scheduler engine. Refer to the
services.
Administration and Troubleshooting manual.
Reason: VALUE_0
Explanation: The instance could not be updated due
GJS0054E The action cannot be performed.
to an error that occurred in the Tivoli Workload
Reason: VALUE_0
Scheduler engine. The error code is specified in the
message text. Explanation: The action could not be performed due
to an error that occurred in the Tivoli Workload
System action: The requested action did not complete
Scheduler engine. The error code is specified in the
successfully.
message text.

Chapter 60. Job Scheduling Console messages 363

GJS0055E • GJS0062E

System action: The requested action did not complete System action: The requested action did not complete
successfully. successfully.
Operator response: The reason displayed in the Operator response: The reason displayed in the
message text represents an error code reported by the message text represents an error code reported by the
Tivoli Workload Scheduler engine. Refer to the Tivoli Workload Scheduler engine. Refer to the
Administration and Troubleshooting manual. Administration and Troubleshooting manual.

GJS0055E The workstation cannot open. GJS0059E The selected workstations cannot be
Reason: VALUE_0 deleted.
Reason: VALUE_0
Explanation: The workstation could not be opened
due to an error that occurred in the Tivoli Workload Explanation: The selected workstations could not be
Scheduler engine. The error code is specified in the deleted due to an error that occurred in the Tivoli
message text. Workload Scheduler engine. The error code is specified
in the message text.
System action: The requested action did not complete
successfully. System action: The requested action did not complete
successfully.
Operator response: The reason displayed in the
message text represents an error code reported by the Operator response: The reason displayed in the
Tivoli Workload Scheduler engine. Refer to the message text represents an error code reported by the
Administration and Troubleshooting manual. Tivoli Workload Scheduler engine. Refer to the
Administration and Troubleshooting manual.
GJS0056E The workstation editor cannot open.
Reason: VALUE_0 GJS0060E The schedule specifications cannot be
added.
Explanation: The workstation editor could not be
Reason: VALUE_0
opened due to an error that occurred in the Tivoli
Workload Scheduler engine. The error code is specified Explanation: The schedule specifications could not be
in the message text. added due to an error that occurred in the Tivoli
Workload Scheduler engine. The error code is specified
System action: The requested action did not complete
in the message text.
successfully.
System action: The requested action did not complete
Operator response: The reason displayed in the
successfully.
message text represents an error code reported by the
Tivoli Workload Scheduler engine. Refer to the Operator response: The reason displayed in the
Administration and Troubleshooting manual. message text represents an error code reported by the
Tivoli Workload Scheduler engine. Refer to the
Administration and Troubleshooting manual.
GJS0057E The action specified on the selected
objects cannot be performed.
Reason: VALUE_0 GJS0061E Another run cycle cannot be created.
Reason: VALUE_0
Explanation: The action could not be performed due
to an error that occurred in the Tivoli Workload Explanation: Another could not be created due to an
Scheduler engine. The error code is specified in the error that occurred in the Tivoli Workload Scheduler
message text. engine. The error code is specified in the message text.
System action: The requested action did not complete System action: The requested action did not complete
successfully. successfully.
Operator response: The reason displayed in the Operator response: The reason displayed in the
message text represents an error code reported by the message text represents an error code reported by the
Tivoli Workload Scheduler engine. Refer to the Tivoli Workload Scheduler engine. Refer to the
Administration and Troubleshooting manual. Administration and Troubleshooting manual.

GJS0058E The workstation cannot be deleted. GJS0062E The action cannot be performed.
Reason: VALUE_0 Reason: VALUE_0
Explanation: The workstation could not be deleted Explanation: The action could not be performed due
due to an error that occurred in the Tivoli Workload to an error that occurred in the Tivoli Workload
Scheduler engine. The error code is specified in the Scheduler engine. The error code is specified in the
message text. message text.

364 IBM Tivoli Workload Scheduler Job Scheduling Console: User’s Guide
 GJS0063E • GJS0070E

System action: The requested action did not complete System action: The requested action did not complete
successfully. successfully.
Operator response: The reason displayed in the Operator response: The reason displayed in the
message text represents an error code reported by the message text represents an error code reported by the
Tivoli Workload Scheduler engine. Refer to the Tivoli Workload Scheduler engine. Refer to the
Administration and Troubleshooting manual. Administration and Troubleshooting manual.

GJS0063E The operation cannot be interrupted. GJS0067E The resource cannot be opened.
Reason: VALUE_0 Reason: VALUE_0
Explanation: The operation could not be interrupted Explanation: The resource could not be opened due to
due to an error that occurred in the Tivoli Workload an error that occurred in the Tivoli Workload Scheduler
Scheduler engine. The error code is specified in the engine. The error code is specified in the message text.
message text.
System action: The requested action did not complete
System action: The requested action did not complete successfully.
successfully.
Operator response: The reason displayed in the
Operator response: The reason displayed in the message text represents an error code reported by the
message text represents an error code reported by the Tivoli Workload Scheduler engine. Refer to the
Tivoli Workload Scheduler engine. Refer to the Administration and Troubleshooting manual.
Administration and Troubleshooting manual.
GJS0068E The resource dependency changes
GJS0064E The resource cannot be deleted. cannot be saved.
Reason: VALUE_0 Reason: VALUE_0
Explanation: The resource could not be deleted due to Explanation: The resource dependency could not be
an error that occurred in the Tivoli Workload Scheduler saved due to an error that occurred in the Tivoli
engine. The error code is specified in the message text. Workload Scheduler engine. The error code is specified
in the message text.
System action: The requested action did not complete
successfully. System action: The requested action did not complete
successfully.
Operator response: The reason displayed in the
message text represents an error code reported by the Operator response: The reason displayed in the
Tivoli Workload Scheduler engine. Refer to the message text represents an error code reported by the
Administration and Troubleshooting manual. Tivoli Workload Scheduler engine. Refer to the
Administration and Troubleshooting manual.
GJS0065E The selected resources cannot be
deleted. GJS0069E The scheduling specifications cannot be
Reason: VALUE_0 added.
Reason: VALUE_0
Explanation: The resources could not be deleted due
to an error that occurred in the Tivoli Workload Explanation: The schedulign specifications could not
Scheduler engine. The error code is specified in the be added due to an error that occurred in the Tivoli
message text. Workload Scheduler engine. The error code is specified
in the message text.
System action: The requested action did not complete
successfully. System action: The requested action did not complete
successfully.
Operator response: The reason displayed in the
message text represents an error code reported by the Operator response: The reason displayed in the
Tivoli Workload Scheduler engine. Refer to the message text represents an error code reported by the
Administration and Troubleshooting manual. Tivoli Workload Scheduler engine. Refer to the
Administration and Troubleshooting manual.
GJS0066E Cannot get the resource header.
Reason: VALUE_0 GJS0070E The scheduling specifications cannot be
added.
Explanation: The resource header could not be
Reason: VALUE_0
retrieved due to an error that occurred in the Tivoli
Workload Scheduler engine. The error code is specified Explanation: The scheduling specifications could not
in the message text. be added due to an error that occurred in the Tivoli

Chapter 60. Job Scheduling Console messages 365

GJS0071W • GJS0077E

Workload Scheduler engine. The error code is specified

GJS0073W The resource might be part of a
in the message text.
dependency for a job scheduler object
System action: The requested action did not complete in the database. If it is renamed, all the
successfully. dependency objects are also modified.
Operator response: The reason displayed in the Explanation: A resource might be part of a
message text represents an error code reported by the dependency for a job scheduler object in the database.
Tivoli Workload Scheduler engine. Refer to the When the resource is renamed, related objects are also
Administration and Troubleshooting manual. modified.
System action: If OK is clicked the selected object is
GJS0071W The resource might be part of a deleted. Otherwise the request is ignored.
dependency for a job scheduler object
Operator response: Click OK to delete the resource, or
in the database. If it is renamed any
click Cancel to cancel the delete action.
action performed that refers to the old
name returns an error.
GJS0075E The connector cannot be linked. The
Explanation: A resource might be part of a
connector is not present on the server.
dependency for a job scheduler object in the database.
When the resource is renamed, any action performed Explanation: The connector could not be linked to
that refers to the old name returns an error. because it is not present on the server being used.
System action: If OK is clicked the selected object is System action: The requested action did not complete
renamed. Otherwise the request is ignored. successfully.
Operator response: Click OK to rename the resource, Operator response: Ensure that a connector is
or select Cancel to cancel the rename action. installed on the server. If a connector is not installed,
create an instance. See the IBM Tivoli Workload
Sheduler Job Scheduling Console User’s guide for
GJS0072W The workstation might be part of a
instructions.
dependency for a job scheduler object
in the database. If it is renamed any
action performed that refers to the old GJS0076E This view cannot be detached. The
name returns an error. maximum number of concurrent
detachable views allowed is reached.
Explanation: A workstation might be part of a
Close one of the open views.
dependency for a job scheduler object in the database.
When the workstation is renamed, any action Explanation: This view cannot be detached. You
performed that refers to the old name returns an error. reached the maximum number of concurrent detachable
views allowed.
System action: If OK is clicked the workstation is
renamed. Otherwise the request is ignored. System action: The requested action did not complete
successfully.
Operator response: Click OK to rename the
workstation, or click Cancel to cancel the rename Operator response: Close one of the open views try to
action. detach the view again.

GJS0073E This object is currently locked because GJS0077E The job stream cannot be saved. The
it is being updated by another user. It is Job Stream cannot contain an external
displayed in read-only mode until the job that has no link.
user releases it. Try again later. Remove the external job that has no
Reason: VALUE_0 link or link it with another job.
Explanation: This object is currently locked because it Explanation: Cannot save the job stream. The Job
is being updated by another user. Stream cannot contain an external job that has no link.
System action: Processing continues but the object System action: The requested action did not complete
displays in read-only mode. successfully.
Operator response: Try to update the object later, after Operator response: Remove the external job that has
it has been released. no link or link it with another job.

366 IBM Tivoli Workload Scheduler Job Scheduling Console: User’s Guide
 GJS0078E • GJS0085E

Administration and Troubleshooting manual.

GJS0078E The external dependency cannot be
pasted. A job stream cannot have
external dependencies from other job GJS0082E The view cannot be attached.
scheduling engines. Reason: VALUE_0
Explanation: The external dependency could not be Explanation: Cannot attach the view.
pasted. An attempt was made to paste a dependency
from a different job scheduling engine. A job stream System action: The requested action did not complete
cannot have external dependencies from other job successfully.
scheduling engines. Operator response: The selected view has a pending
System action: The requested action did not complete dialog. Close it before attaching the view.
successfully.
Operator response: Paste the dependency into a job GJS0083E The workstation plan view cannot be
stream on the same engine. loaded.
Reason: VALUE_0

GJS0079E The search objects cannot be found. Explanation: The workstation plan view could not be
Reason: VALUE_0 loaded due to an error that occurred in the Tivoli
Workload Scheduler engine. The error code is specified
Explanation: The search objects could not be found in the message text.
due to an error that occurred in the Tivoli Workload
Scheduler engine. The error code is specified in the System action: The requested action did not complete
message text. successfully.

System action: The requested action did not complete Operator response: The reason displayed in the
successfully. message text represents an error code reported by the
Tivoli Workload Scheduler engine. Refer to the
Operator response: The reason displayed in the Administration and Troubleshooting manual.
message text represents an error code reported by the
Tivoli Workload Scheduler engine. Refer to the
Administration and Troubleshooting manual. GJS0084E The job output cannot be loaded. The
job output uses an unsupported
encoding. Reason: VALUE_0
GJS0080W This job stream may be part of a
dependency for a job scheduler object Explanation: The job output could not be loaded
in the database. If the job stream is because it uses an unsupported encoding.
renamed, all dependency objects are System action: The requested action did not complete
also modified. successfully.
Explanation: A job stream may be part of a Operator response: Select another job that uses the
dependency for a job scheduler object in the database. correct encoding.
If this job stream is renamed, all dependency objects
are also modified.
GJS0085E The job output cannot be loaded.
System action: If OK is clicked the selected object is Reason: VALUE_0
renamed. Otherwise the request is ignored.
Explanation: The job output could not be loaded due
Operator response: Click OK to rename the job to an error that occurred in the Tivoli Workload
stream, or click Cancel to cancel the rename action. Scheduler engine. The error code is specified in the
message text.
GJS0081E The selected engine is not available. System action: The requested action did not complete
Reason: VALUE_0 successfully.
Explanation: The selected engine is not available due Operator response: The reason displayed in the
to an error that occurred in the Tivoli Workload message text represents an error code reported by the
Scheduler engine. The error code is specified in the Tivoli Workload Scheduler engine. Refer to the
message text. Administration and Troubleshooting manual.
System action: The requested action did not complete
successfully.
Operator response: The reason displayed in the
message text represents an error code reported by the
Tivoli Workload Scheduler engine. Refer to the

Chapter 60. Job Scheduling Console messages 367

GJS0086E • GJS0097E

Administration and Troubleshooting manual.

GJS0086E The common plan view for VALUE_1
cannot be loaded.
Reason: VALUE_0 GJS0093W The object that was locked in editing
has been unlocked by another user or
Explanation: The plan view could not be loaded due
session. The data in the database might
to an error that occurred in the Tivoli Workload
have been changed.
Scheduler engine. The error code is specified in the
Do you want to continue?
message text.
Explanation: The object being saved was locked
System action: The requested action did not complete
during editing and then unlocked by another user or
successfully.
session. Changes that occurred after the object was
Operator response: The reason displayed in the unlocked will be overwritten.
message text represents an error code reported by the
System action: If the answer to the previous question
Tivoli Workload Scheduler engine. Refer to the
was Yes, the object in the database is overwritten.
Administration and Troubleshooting manual.
Otherwise the object is left unchanged.
See also::
Operator response: Click Yes to overwrite the object
com.tivoli.jsc.commonviews.JsCommonPlanNavigator
in the database, or click No to cancel the save.
method runQuery()

GJS0094E The window cannot be closed.

GJS0087E The selected engine is not available.
The VALUE_0 list cannot be created
There might be a connection problem or
because a list with the same name and
it might have a version that is not valid.
the same path already exists.
Explanation: The selected engine not available,
Explanation: Two lists cannot be created with the
because it either has a connection problem or the
same name in the same path.
engine version is not valid.
System action: The requested action did not complete
System action: The requested action did not complete
successfully.
successfully.
Operator response: Type a new list name.
Operator response: Verify the connection for the
selected engine and make sure that the version is
compatible and try again. GJS0095E The job stream cannot be loaded
because it is unknown. Try a different
name.
GJS0088W This job stream might be part of a
dependency for a job scheduler object Explanation: The job stream was not found.
in the database. If it is renamed, all the
dependency objects are also renamed. System action: The requested action did not complete
successfully.
Explanation: A workstation might be part of a
dependency for a job scheduler object in the database. Operator response: Type different filter criteria and
If it is renamed, all the dependency objects are also run the list again.
modified.
System action: If OK is clicked the selected object is GJS0096I The specified engine uses an
renamed. Otherwise the request is ignored. unsupported API level.

Operator response: Click OK to rename the Explanation: This product version cannot work with
workstation or click Cancel to cancel the rename action. the specified engine because it has an unsupported API
level.

GJS0089E The job VALUE_0 cannot be updated. System action: The requested action did not complete
Reason: VALUE_1 successfully.

Explanation: The job could not be updated due to an Operator response: Try a different engine or upgrade
error that occurred in the Tivoli Workload Scheduler the product.
engine. The error code is specified in the message text.
System action: The requested action did not complete GJS0097E The window cannot be closed.
successfully. Reason: You cannot create the list
VALUE_0 because a list with the same
Operator response: The reason displayed in the name and the same path already exists.
message text represents an error code reported by the
Tivoli Workload Scheduler engine. Refer to the Explanation: Two lists cannot be created with the

368 IBM Tivoli Workload Scheduler Job Scheduling Console: User’s Guide
 GJS3001W • GJS3009E

same name in the same path. Tivoli Workload Scheduler engine. Refer to the
Administration and Troubleshooting manual.
System action: The requested action did not complete
successfully.
GJS3006E The plan view cannot be loaded.
Operator response: Type a new list name.
Reason: VALUE_0
Explanation: The plan view could not be loaded due
GJS3001W The number format is not correct.
to an error that occurred in the Tivoli Workload
Explanation: The number format is not correct. The Scheduler engine. The error code is specified in the
value remains unchanged. message text.
System action: The requested action did not complete System action: The requested action did not complete
successfully. successfully.
Operator response: Type a new number in the correct Operator response: The reason displayed in the
format. message text represents an error code reported by the
Tivoli Workload Scheduler engine. Refer to the
Administration and Troubleshooting manual.
GJS3003E The Workstation definition for VALUE_0
cannot be loaded.
Reason: VALUE_1 GJS3007E The resource list cannot be loaded.
Reason: VALUE_0
Explanation: The workstation definition could not be
loaded due to an error that occurred in the Tivoli Explanation: The resource list could not be loaded
Workload Scheduler engine. The error code is specified due to an error that occurred in the Tivoli Workload
in the message text. Scheduler engine. The error code is specified in the
message text.
System action: The requested action did not complete
successfully. System action: The requested action did not complete
successfully.
Operator response: The reason displayed in the
message text represents an error code reported by the Operator response: The reason displayed in the
Tivoli Workload Scheduler engine. Refer to the message text represents an error code reported by the
Administration and Troubleshooting manual. Tivoli Workload Scheduler engine. Refer to the
Administration and Troubleshooting manual.
GJS3004E The resource availability definition
cannot be loaded. GJS3008E The workstation plan view cannot be
Reason: VALUE_0 loaded.
Reason: VALUE_0
Explanation: The resource availability definition could
not be loaded due to an error that occurred in the Explanation: The workstation plan view could not be
Tivoli Workload Scheduler engine. The error code is loaded due to an error that occurred in the Tivoli
specified in the message text. Workload Scheduler engine. The error code is specified
in the message text.
System action: The requested action did not complete
successfully. System action: The requested action did not complete
successfully.
Operator response: The reason displayed in the
message text represents an error code reported by the Operator response: The reason displayed in the
Tivoli Workload Scheduler engine. Refer to the message text represents an error code reported by the
Administration and Troubleshooting manual. Tivoli Workload Scheduler engine. Refer to the
Administration and Troubleshooting manual.
GJS3005E The job stream list cannot be loaded.
Reason: VALUE_0 GJS3009E The workstation list cannot be loaded.
Reason: VALUE_0
Explanation: The job stream list could not be loaded
due to an error that occurred in the Tivoli Workload Explanation: The workstation list could not be loaded
Scheduler engine. The error code is specified in the due to an error that occurred in the Tivoli Workload
message text. Scheduler engine. The error code is specified in the
message text.
System action: The requested action did not complete
successfully. System action: The requested action did not complete
successfully.
Operator response: The reason displayed in the
message text represents an error code reported by the Operator response: The reason displayed in the

Chapter 60. Job Scheduling Console messages 369

GJS3010E • GJS3030E

message text represents an error code reported by the

GJS3014E The date format is incorrect.
Tivoli Workload Scheduler engine. Refer to the
Administration and Troubleshooting manual. Explanation: The format of the date is incorrect. The
date must be in the same format as the locale settings
of the computer.
GJS3010E The resource VALUE_0 cannot be saved.
Reason: VALUE_1 System action: The requested action did not complete
successfully.
Explanation: The resource could not be saved due to
an error that occurred in the Tivoli Workload Scheduler Operator response: Type the date, month, and year in
engine. The error code is specified in the message text. the format specified in the locale settings on the
computer.
System action: The requested action did not complete
successfully.
GJS3015E The typed deadline occurs before the
Operator response: The reason displayed in the
start time. Type a later deadline.
message text represents an error code reported by the
Tivoli Workload Scheduler engine. Refer to the Explanation: The typed deadline occurs before the
Administration and Troubleshooting manual. start time. A deadline must occur after the start time.
System action: The requested action did not complete
GJS3011E The resource availability definition for successfully.
VALUE_0 cannot be loaded.
Operator response: Type a deadline that is later than
Reason: VALUE_1
the start time.
Explanation: The resource availability definition could
not be loaded due to an error that occurred in the
GJS3016E The range for the deadline, in days
Tivoli Workload Scheduler engine. The error code is
VALUE_0, hours VALUE_0, minutes,
specified in the message text.
must be greater than zero and less than
System action: The requested action did not complete or equal to 99VALUE_023VALUE_059.
successfully.
Explanation: The indicated deadline is not in the
Operator response: The reason displayed in the correct range.
message text represents an error code reported by the
System action: The requested action did not complete
Tivoli Workload Scheduler engine. Refer to the
successfully.
Administration and Troubleshooting manual.
Operator response: Type a deadline within the correct
in the range.
GJS3012E The resource instance for VALUE_0
cannot be loaded.
Reason: VALUE_1 GJS3029E The operation cannot be performed on
this job instance.
Explanation: The resource instance could not be
loaded due to an error that occurred in the Tivoli Explanation: The operation could not be performed
Workload Scheduler engine. The error code is specified on this job instance.
in the message text.
System action: The requested action did not complete
System action: The requested action did not complete successfully.
successfully.
Operator response: Select another instance on which
Operator response: The reason displayed in the to perform the operation.
message text represents an error code reported by the
Tivoli Workload Scheduler engine. Refer to the
Administration and Troubleshooting manual. GJS3030E The specified calendar cannot be found.
Explanation: The calendar could not be found.
GJS3013E Class Name: VALUE_0 is not Fully System action: The requested action did not complete
Qualified. successfully.
Explanation: The current Class Name is not Fully Operator response: Specify another calendar.
Qualified.
System action: The requested action did not complete
successfully.
Operator response: Specify a fully qualified class
name.

370 IBM Tivoli Workload Scheduler Job Scheduling Console: User’s Guide
 GJS3031E • GJS3045E

GJS3031E Name is a required field. Type a name GJS3041E The value is less than the minimum
for the object. length of VALUE_0 characters.
(Single Byte Character Set)
Explanation: The Name field is a mandatory field.
Explanation: The typed value is less than the
System action: The requested action did not complete
minimum length for the field.
successfully.
System action: The requested action did not complete
Operator response: Type a name for the object.
successfully.
Operator response: Type a value with a number of
GJS3032E Owner is a required field. Type the
characters that is greater than the minimum length.
owner’s name.
Explanation: The Owner field is mandatory.
GJS3042E The input is incorrect. Type a valid IP
System action: The requested action did not complete address (for example 125.12.50.255) or a
successfully. valid node name (for example
Edison.rome.tivoli.com).
Operator response: Type the owner’s name.
Explanation: The node input is incorrect.
GJS3033E Target workstation is a required field. System action: The requested action did not complete
Type the target workstation. successfully.
Explanation: The target workstation is mandatory. Operator response: Type a valid IP address (for
example: 125.12.50.255) or a valid node name (for
System action: The requested action did not complete example: Edison.rome.tivoli.com).
successfully.
Operator response: Specify the target workstation. GJS3043E The string contains one or more
characters that are not valid.
GJS3034E Task is a required field. Type the task Explanation: The string contains one or more
name. characters that are not alphanumeric.
Explanation: Task is a required field. System action: The requested action did not complete
System action: The requested action did not complete successfully.
successfully. Operator response: Type a string using alphanumeric
Operator response: Type the task name. characters only.

GJS3039E The input field is mandatory. GJS3044E There has been an internal application
error in the job stream editor.
Explanation: The input field is mandatory.
Explanation: Internal application error.
System action: The requested action did not complete
successfully. System action: The requested action did not complete
successfully.
Operator response: Complete all mandatory fields.
Mandatory fields are indicated by a yellow Operator response: Contact customer support.
background.
GJS3045E The view must run within a IBM Tivoli
GJS3040E The value exceeds the maximum length Workload Scheduler Job Scheduling
of VALUE_0 characters. Console.

Explanation: The typed value exceeds the maximum Explanation: Internal application error.
length for the field. System action: The requested action did not complete
System action: The requested action did not complete successfully.
successfully. Operator response: Contact customer support.
Operator response: Type a value with a number of
characters that is less than or equal to the allowed
maximum length.

Chapter 60. Job Scheduling Console messages 371

GJS3046E • GJS3060E

GJS3046E JSDefaultRunCyclePlugIn::throwing GJS3051E The string is not a numeric value.

runtime exception
Explanation: The string is not valid because it is not a
Explanation: Internal application error. numeric value.
System action: The requested action did not complete System action: The requested action did not complete
successfully. successfully.
Operator response: Contact customer support. Operator response: Type a numeric string.

GJS3047E The Job Stream Editor cannot be GJS3052E The input is outside the accepted range
opened. of VALUE_0 to VALUE_1.
Reason: VALUE_0
Explanation: The input is outside the accepted range.
Explanation: The Job Stream Editor could not be
System action: The requested action did not complete
opened due to an error that occurred in the Tivoli
successfully.
Workload Scheduler engine. The error code is specified
in the message text. Operator response: Type an input within the accepted
range.
System action: The requested action did not complete
successfully.
GJS3057E The resource editor cannot be opened.
Operator response: The reason displayed in the
Reason: VALUE_0
message text represents an error code reported by the
Tivoli Workload Scheduler engine. Refer to the Explanation: The resource editor could not be opened
Administration and Troubleshooting manual. due to an error that occurred in the Tivoli Workload
Scheduler engine. The error code is specified in the
message text.
GJS3048E There is a connection error caused by an
oserv failure when running the System action: The requested action did not complete
connector. successfully.
Details are logged in the Job Scheduling
Console trace file. Operator response: The reason displayed in the
message text represents an error code reported by the
Explanation: There is an internal application error in Tivoli Workload Scheduler engine. Refer to the
for the connector. Administration and Troubleshooting manual.
System action: The requested action did not complete
successfully. GJS3058E The resource name is required.
Operator response: Contact customer support. Explanation: The resource name is a mandatory field.
System action: The requested action did not complete
GJS3049E A job stream must contain at least one successfully.
job before it can be saved.
Operator response: Type a name for the resource and
Explanation: A job stream must have at least one job save again.
defined before it can be saved.
System action: The requested action did not complete GJS3060E The typed start time occurs after the
successfully. deadline time.
Operator response: Define at least one job before Explanation: The typed start time comes after the
saving the job stream. deadline time. The start time must occur before the
deadline.
GJS3050E The necessary localization resources System action: The requested action did not complete
were not found. successfully.
Explanation: The resources necessary to show the Operator response: Type a start time that is earlier
localized version were not found. than the deadline time.
System action: Processing continues but the dialogs
are shown without messages.
Operator response: Contact customer support.

372 IBM Tivoli Workload Scheduler Job Scheduling Console: User’s Guide
 GJS3061E • GJS3089W

GJS3061E The job stream is not empty. A job GJS3069W This workstation might be part of a
stream template cannot contain jobs. dependency for a job scheduler object
in the database. If so, any action
Explanation: A Job Stream has to be empty before it is
performed that refers to the old name
saved as a template.
returns an error.
System action: The requested action did not complete
Explanation: A workstation might be part of a
successfully.
dependency for a job scheduler object in the database.
Operator response: Remove any jobs in the job stream If the workstation is renamed, any action performed
before saving it as a template. that refers to the old name returns an error.
System action: If OK is clicked then the selected object
GJS3063E The time format is not correct. The is renamed. Otherwise the rename action is ignored.
correct format is VALUE_0.
Operator response: Click OK to rename the
Explanation: The format used for the time is not workstation. Otherwise click Cancel to cancel the
correct. rename action.
System action: The requested action did not complete
successfully. GJS3070E Blank is not a valid character.
Operator response: Type a correct format time. Explanation: The blank character is not a valid
character.
GJS3064E The Job Scheduler Explorer Console System action: The requested action did not complete
must run within the Tivoli Console. successfully.
Explanation: Internal application error. Operator response: Type the string again without
using the blank character.
System action: The requested action did not complete
successfully.
GJS3071E The rule is not valid. Ensure that the
Operator response: Contact customer support. shift origin field is consistent with the
periods selected.
GJS3065E There was an unexpected error while Explanation: The rule not valid.
updating. Repeat the operation.
System action: The requested action did not complete
Explanation: Unexpected error while updating. successfully.
System action: The requested action did not complete Operator response: Type an inclusive shift origin
successfully. value in the periods selected.
Operator response: Repeat the operation.
GJS3073E The duration of the job instance cannot
GJS3067E Value: VALUE_0 must be a Time Zone. be 0.

Explanation: Internal application error. Explanation: The duration of the job instance has been
set to 0. 0 is not a valid value for the duration of a job.
System action: Processing continues.
System action: The requested action did not complete
Operator response: Contact customer support. successfully.
Operator response: Set the duration of the job
GJS3068E The workstation name is required. instance to a value different from 0.
Explanation: The workstation name is a mandatory
field. GJS3089W These resources might be part of a
System action: The requested action did not complete dependency for a job scheduler object
successfully. in the database. If they are deleted any
action performed that refers to the old
Operator response: Type a name for the workstation resources returns an error.
and save again.
Explanation: The resources might be part of a
dependency for a job scheduler object in the database.
If they are deleted any action performed that refers to
the old resources returns an error.
System action: If OK is clicked then the selected

Chapter 60. Job Scheduling Console messages 373

GJS3090E • GJS3103E

objects are deleted. Otherwise the delete action is System action: The requested action did not complete
ignored. successfully.
Operator response: Operator response: Check the trace file and correct
the cause of the error.
GJS3090E In the Dates section, the To Date is
earlier than the From Date. Type an GJS3095E The host name could not be determined.
earlier From Date, or type a later To
Explanation: The specified host name could nor be
Date.
resolved.
Explanation: The query deos not return any results
System action: The requested action did not complete
because the From Date is later than the To Date.
successfully.
System action: The requested action did not complete
Operator response: Check the host name and make
successfully.
sure the computer where the host is running is active.
Operator response: Type an earlier From Date, or type
a later To Date.
GJS3097E The object VALUE_0 cannot be loaded.
Reason: VALUE_1
GJS3091E In the Dates section, when you set a
Explanation: The object could not be loaded due to an
value for the Date field you must also
error that occurred in the Tivoli Workload Scheduler
set a value for the Time field.
engine. The error code is specified in the message text.
Explanation: The query does not return any results
System action: The requested action did not complete
because the Date filter is not set correctly.
successfully.
System action: The requested action did not complete
Operator response: The reason displayed in the
successfully.
message text represents an error code reported by the
Operator response: Set values for both Date and Time Tivoli Workload Scheduler engine. Refer to the
fields, or do set values for either Date and Time fields. Administration and Troubleshooting manual.

GJS3092E In the Dates section, when a value is set GJS3100E A run cycle with the same name already
for the Time field a value must also be exists in the job stream.
set for the Date field.
Explanation: Two run cycles with the same name
Explanation: The query does not return any results cannot exist for the same job stream.
because the Date filter is not set correctly.
System action: The requested action did not complete
System action: The requested action did not complete successfully.
successfully.
Operator response: Type a different name for the new
Operator response: Set values both for Time and Date run cycle.
fields, or do not set values for either Date and Time
fields.
GJS3102E The input is outside the accepted upper
limit of VALUE_0.
GJS3093E The engine with the specified name
Explanation: The input is outside the accepted upper
already exists.
limit.
Explanation: Two engines with the same name cannot
System action: The requested action did not complete
exist for the same Job Scheduling Console.
successfully.
System action: The requested action did not complete
Operator response: Type an input within the accepted
successfully.
upper limit.
Operator response: Type another engine name.
GJS3103E The imported Engine.xml file is corrupt.
GJS3094E There is an error saving the engines to The Job Scheduling Console does not
the engines file. function correctly. Close the Job
Details are logged in the Job Scheduling Scheduling console and delete the
Console trace file. Engine.xml file from the
user_home_directory/.twsconsole.
Explanation: An error occurred attempting to save the
engines data to the engines file. Explanation: An error occurred while loading

374 IBM Tivoli Workload Scheduler Job Scheduling Console: User’s Guide
 GJS3104E • GJS3116E

Engine.xml file. The Job Scheduling Console does not

| GJS3109E Cannot find the specified external
function correctly.
| dependency.
System action: The requested action did not complete
| Explanation: See the message text.
successfully.
| System action: The requested action did not complete
Operator response: Ignore any other messages and
| successfully.
close the application. Delete the user_home_directory/
.twsconsole/Engine.xml file and restart the Job | Operator response: Verify that the specified external
Scheduling Console. | dependency exists and try again.

| GJS3104E The job stream VALUE_0 cannot be | GJS3110E Cannot find the specified Job
| submitted. | Definition. Please specify another.
| Reason: VALUE_1
| Explanation: See the message text.
| Explanation: An error occurred while submitting the
| System action: The requested action did not complete
| job stream.
| successfully.
| System action: The requested action did not complete
| Operator response: Verify that the specified job
| successfully.
| definition exists and try again.
| Operator response: Analyze the reason displayed in
| the message text and submit the job stream again.
| GJS3111E Cannot write file VALUE_0.\nReason:
| VALUE_1.
| GJS3105E Unable to add a dependency to the
| Explanation: See the message text.
| selected object.
| System action: The requested action did not complete
| Explanation: See the message text.
| successfully.
| System action: The requested action did not complete
| Operator response: Verify that you have the correct
| successfully.
| permissions or that the file is not locked and try again.
| Operator response: Analyze the reason displayed in
| the message text and submit the job stream again.
| GJS3112E Cannot open file VALUE_0.\nReason:
| VALUE_1.
| GJS3106E Unable to add the dependency from
| Explanation: See the message text.
| VALUE_0 to VALUE_1Reason: VALUE_2
| System action: The requested action did not complete
| Explanation: See the message text.
| successfully.
| System action: The requested action did not complete
| Operator response: Verify that you have the correct
| successfully.
| permissions or that the file is not locked and try again.
| Operator response: Analyze the reason displayed in
| the message text and try again.
| GJS3113E File VALUE_0 does not exist.
| Explanation: See the message text.
| GJS3107E Cannot find the specified internal job.
| System action: The requested action did not complete
| Explanation: See the message text.
| successfully.
| System action: The requested action did not complete
| Operator response: Verify that you have specified the
| successfully.
| correct name.
| Operator response: Verify that the specified internal
| job exists and try again.
GJS3116E The same dependency cannot be
defined twice in the same job stream.
| GJS3108E Job can not depend on itself.
Explanation: A dependency between job streams must
| Explanation: See the message text. be unique.
| System action: The requested action did not complete System action: The requested action did not complete
| successfully. successfully.
| Operator response: Correct the job name and try Operator response: Modify one or both dependencies
| again. to make them unique.

Chapter 60. Job Scheduling Console messages 375

GJS3117E • GJS3118E

GJS3117E A run cycle with the same name already GJS3118E Cannot logon to the remote server.
exists in the Job Stream.
Explanation: The remote server is not reachable.
Explanation: Run cycle names in job streams must be
System action: The requested action did not complete
unique.
successfully.
System action: The requested action did not complete
Operator response: Check the validity of the user
successfully.
name and password. Check if the connection with the
Operator response: Modify one or both run cycles to remote server is available. Check if the remote server is
make their names unique. started.

Job Scheduling Console z/OS messages

Administration and Troubleshooting manual.
GJS1001E The z/OS engine engine_name is not
supported.
GJS1005E There was an error in setting the step
Explanation: The z/OS engine version selected is not
list.
supported.
error_message
System action: The requested action did not complete
Explanation: An error occurred when setting step list
successfully.
because of one of the followings reasons:
Operator response: Select a supported engine version. The selected Start Step is not restartable. Possible
reasons are the JCL logic or the RCLOPTS initial
parameter setting.
GJS1002E The selected period was not found.
The action field cannot be set to Start for more than
Period:period
one step.
Explanation: The selected period was not found in the The action field cannot be set to End for more than one
z/OS database. step.
A step marked as always executable was excluded from
System action: The requested action did not complete the selected Step List because of the RCLOPTS initial
successfully. parameter setting.
Operator response: Specify a valid period. A step marked as not executable was included in the
selected Step List because of the RCLOPTS initial
parameter setting.
GJS1003E The setup of the selected job instance The selected End Step must follow the selected Start
cannot be performed. Step.
There are no valid successors for
object_name. System action: The requested action did not complete
successfully.
Explanation: There are no valid successors for the
selected object. Operator response: Identify which of the error
conditions has occurred from the information in
System action: The requested action did not complete Explanation. Correct the input and retry..
successfully.
Operator response: Select at least one valid successor GJS1006E The selected workstation cannot be
for the selected job instance. linked.
Reason: reason
GJS1004E The setup of the selected job instance Explanation: The selected workstation could not be
cannot be performed. linked due to an error that occurred in the Tivoli
Reason: reason Workload Scheduler engine. The error code is specified
Explanation: The setup of the selected job instance in the message text.
could not be performed due to an error that occurred System action: The requested action did not complete
in the Tivoli Workload Scheduler engine. The error successfully.
code is specified in the message text.
Operator response: The reason displayed in the
System action: The requested action did not complete message text represents an error code reported by the
successfully. Tivoli Workload Scheduler engine. Refer to the
Operator response: The reason displayed in the Administration and Troubleshooting manual.
message text represents an error code reported by the
Tivoli Workload Scheduler engine. Refer to the

376 IBM Tivoli Workload Scheduler Job Scheduling Console: User’s Guide
 Job Scheduling Console z/OS messages

PARALLELLSERVERS resource that is within the range

GJS1007E The selected workstation cannot be
1 to 99.
unlinked.
Reason: reason
GJS1012E The specified job stream
Explanation: The selected workstation could not be
"job_stream_name" does not exist.
unlinked due to an error that occurred in the Tivoli
Workload Scheduler engine. The error code is specified Explanation: The job stream does not exist.
in the message text.
System action: Processing continues.
System action: The requested action did not complete
successfully. Operator response: Click OK to continue, or Cancel
to specify a new job stream.
Operator response: The reason displayed in the
message text represents an error code reported by the
Tivoli Workload Scheduler engine. Refer to the GJS1013E The repeat time interval must be at least
Administration and Troubleshooting manual. 1 minute. Specify a different interval.
Explanation: The repeat time interval should be not
GJS1008E The rerun operations on the selected job less than 1 minute and not more than 23 hours and 59
stream instance cannot be performed. minutes.
Reason: reason System action: Processing continues.
Explanation: The rerun operation could not be Operator response: Click Close and specify a new
performed on selected job stream instance due to an interval.
error that occurred in the Tivoli Workload Scheduler
engine. The error code is specified in the message text.
GJS1014E The repeat end time must be between
System action: The requested action did not complete one minute after the start time of the
successfully. run cycle and one minute before the
Operator response: The reason displayed in the calendar work day end time of the job
message text represents an error code reported by the stream.
Tivoli Workload Scheduler engine. Refer to the Specify a different repeat end time.
Administration and Troubleshooting manual. Explanation: See message.
System action: The properties are not saved.
GJS1009E The restart and cleanup operations on
selected job instance cannot be Operator response: Click Close to dismiss the
performed. message and specify a repeat end time that is between
Reason: reason one minute after the start time of the run cycle and one
minute before the calendar work day end time of the
Explanation: The restart and cleanup operations could job stream.
not be performed on selected job instance due to an
error that occurred in the Tivoli Workload Scheduler
engine. The error code is specified in the message text. GJS4001E The availability interval cannot be
defined if the "To Time" is equal to the
System action: The requested action did not complete "From Time".
successfully.
Explanation: The availability interval cannot be
Operator response: The reason displayed in the defined if the To Time is equal to the From Time
message text represents an error code reported by the
Tivoli Workload Scheduler engine. Refer to the System action: The requested action did not complete
Administration and Troubleshooting manual. successfully.
Operator response: Type a To Time that is later than
GJS1011E The specified value is not valid for the the From Time.
PARALLELSERVERS resource. The
valid range is from 1 to 99. GJS4002E The specified calendar was not found in
Explanation: The PARALLELSERVERS resource values the z/OS database. Specify a valid
range is from 1 to 99. calendar name.

System action: The requested action did not complete Explanation: The specified calendar was not found in
successfully. the z/OS database.

Operator response: Type a value for the System action: The requested action did not complete
successfully.

Chapter 60. Job Scheduling Console messages 377

Job Scheduling Console z/OS messages

Operator response: Specify a valid calendar name.

GJS4011W Do you want to UN-NOP the selected
scheduled instances?
GJS4003E The option "Cancel if late" and the
Explanation: See message.
"Start time" specifications are in conflict.
To cancel the job if it is late, an earliest System action: The program waits for your response.
start time and a deadline must be
Operator response: Select Yes to UN-NOP the selected
defined.
instances or No to cancel the request.
Explanation: The selected options are in conflict. Read
the message text for a solution.
GJS4012W Do you want to NOP scheduled instance
System action: The requested action did not complete instance_identifier?
successfully.
Explanation: See message.
Operator response: Correct the conflicting properties
System action: The program waits for your response.
and save again.
Operator response: Select Yes to NOP the selected
scheduled instance or No to cancel the request.
GJS4004E A dependency already exists. Define
only one dependency between two jobs.
GJS4013W Do you want to set the status of the
Explanation: Only one dependency between two jobs
scheduled instance instance_identifier to
can be defined.
"complete"?
System action: The requested action did not complete
Explanation: See message.
successfully.
System action: The program waits for your response.
Operator response: Define only one dependency.
Operator response: Select Yes to set the selected
scheduled instance to "complete" or No to cancel the
GJS4008E If the job stream inherits scheduling
request.
information from a template, it cannot
use the specified calendar. Complete
either the "Inherits from template" field GJS4014W Do you want to set the status of the
or the "Calendar" field, but not both. selected scheduled instances to
complete?
Explanation: The Inherits from template field and the
Calendar field are mutually exclusive. Explanation: See message.
System action: The requested action did not complete System action: The program waits for your response.
successfully.
Operator response: Select Yes to set the selected
Operator response: Complete either the Inherits from scheduled instances to "complete" or No to cancel the
template field or the Calendar field, but not both. request.

GJS4009E The specified template in the "Inherits GJS4015W Do you want to set the status of the
from template" field does not exist. selected scheduled instances to
Specify a valid template. "waiting"?
Explanation: A template has been inserted in the Explanation: See message.
Inherits from template field that does not exist.
System action: The program waits for your response.
System action: The requested action did not complete
successfully. Operator response: Select Yes to set the selected
scheduled instances to "waiting" or No to cancel the
Operator response: Specify a valid template in the request.
Inherits from template field.

GJS4016W Do you want to set the status of the

GJS4010W Do you want to NOP the selected scheduled instance instance_identifier to
scheduled instances? "waiting"?
Explanation: See message. Explanation: See message.
System action: The program waits for your response. System action: The program waits for your response.
Operator response: Select Yes to NOP the selected Operator response: Select Yes to set the selected
scheduled instances or No to cancel the request.

378 IBM Tivoli Workload Scheduler Job Scheduling Console: User’s Guide
 Job Scheduling Console z/OS messages

scheduled instances to "waiting" or No to cancel the

GJS4022E The default calendar was not found in
request.
z/OS. All days will be counted as
workdays.
GJS4017W Do you want to UN-NOP scheduled
Explanation: The default calendar was not found in
instance instance_identifier?
z/OS. All days will be counted as workdays.
Explanation: See message.
System action: The requested action did not complete
System action: The program waits for your response. successfully.
Operator response: Select Yes to UN-NOP the selected Operator response: Type a valid calendar name.
scheduled instance or No to cancel the request.
GJS4023E The specified target workstation does
GJS4018E The Node Address field is mandatory not exist, or cannot run the type of task
when the port number is specified. associated with this job. Type a valid
Specify a Node Address in the Access workstation name.
Methods section.
Explanation: The target workstation specified in the
Explanation: The Node Address field is mandatory job page must exist.
when the port number is specified.
System action: The requested action did not complete
System action: The requested action did not complete successfully.
successfully.
Operator response: Type a valid workstation name.
Operator response: Specify a valid "Node Address" in
the "Access Methods" section.
GJS4024E The Offset-based Run Cycle cannot
contain offsets outside the defined
GJS4019E The Name field is mandatory when the interval.
Node Address is specified. Specify a
Explanation: The Offset-based Run Cycle cannot
Name in the Access Methods section.
contain offsets outside the defined interval.
Explanation: The Name field is mandatory when the
System action: The requested action did not complete
Node Address is specified.
successfully.
System action: The requested action did not complete
Operator response: Insert offsets that are included in
successfully.
the defined interval.
Operator response: Specify a valid Name in the
Access Methods section.
GJS4025E The Rule-based Run Cycle cannot
contain days outside the user-defined
GJS4020E The Name and Node Address fields are period.
mandatory when the Port Number is
Explanation: The Rule-based Run Cycle cannot
specified. Specify a Name and a Node
contain days outside the user-defined period.
Address in the Access Methods section.
System action: The requested action did not complete
Explanation: The Name and Node Address fields are
successfully.
mandatory when the Port Number is specified.
Operator response: Insert days that are included in
System action: The requested action did not complete
the user-defined period.
successfully.
Operator response: Specify a Name and a Node
GJS4027E The To Time precedes the From Time.
Address in the Access Methods section.
Type a later To Time or an earlier From
Time, or both.
GJS4021E The identifier is not unique.
Explanation: See message.
Explanation: The identifier must be unique.
System action: The requested action did not complete
System action: The requested action did not complete successfully.
successfully.
Operator response: Type a later To Time or an earlier
Operator response: Type a unique identifier. From Time, or both.

Chapter 60. Job Scheduling Console messages 379

Job Scheduling Console z/OS messages

GJS4028E The specified target workstation cannot GJS4033E The start time is earlier than the job
run the type of task associated with this stream Valid From date. Type a later
job. Type the name of a workstation that start time.
is enabled to run the task.
Explanation: The start time that you typed comes
Explanation: The target workstation must be enabled before the job stream Valid From date.
to run the type of task associated with a job.
System action: The requested action did not complete
System action: The requested action did not complete successfully.
successfully.
Operator response: Type a later start time.
Operator response: Type a name of a workstation that
is enabled to run the task.
GJS4034W The logical resource resource_name is not
defined. Do you want to proceed?
GJS4029W The job you want to delete is the last
Explanation: See message.
one in the job stream. The job stream
will also be deleted. Do you want to System action: The program waits for your response.
proceed?
Operator response: Select Yes to continue, even
Explanation: See message. though the resource is not defined, or No to cancel the
request.
System action: The program waits for your response.
Operator response: Select Yes to delete the last job and
GJS4035W The logical resources resource_names are
the job stream or No to cancel the request.
not defined. Do you want to proceed?
Explanation: See message.
GJS4030E A job stream cannot contain unlinked
jobs. System action: The program waits for your response.
Explanation: In the Job Stream definition there is a job Operator response: Select Yes to continue, even
that is unlinked to any of the remaining jobs. though the resources are not defined, or No to cancel
the request.
System action: The requested action did not complete
successfully.
GJS4036W No duration alert will be issued for
Operator response: Link the job to other jobs or
99.59.01. Do you want to proceed?
remove it from the job stream.
Explanation: The duration of the job has been set to
99 H, 59 M, 1 S. This is an acceptable value but no alert
GJS4031E The job duration cannot be zero.
will be displayed
Explanation: The duration of the job has been set to
System action: The program waits for your response.
zero.
Operator response: Select Yes to continue, even
System action: The requested action did not complete
though the alert will not be displayed, or No to cancel
successfully.
the request.
Operator response: Set the duration of the job to a
value greater than zero.
GJS4037E The job duration cannot be greater than
99.59.01.
GJS4032E The specified Open Time interval is not
Explanation: The duration of the job has been set
valid.
greater than 99 H, 59 M, 1 S.
Explanation: The resulting duration value is zero,
System action: The requested action did not complete
which is not an acceptable value.
successfully.
System action: The requested action was not
Operator response: Set the duration of the job to a
completed successfully.
value that is less than or equal to 99.59.01.
Operator response: Set the requested values to define
a duration different from zero.
GJS4038W A Start Cleanup with AR action is being
requested, but no restart step is
available. The complete cleanup list will
be returned.
Explanation: The action you have requested suggests

380 IBM Tivoli Workload Scheduler Job Scheduling Console: User’s Guide
 Job Scheduling Console z/OS messages

that you expected to find a step, but no steps are Explanation: See message.
available.
System action: The program waits for your response.
System action: The complete cleanup list is returned.
Operator response: Select Yes to set all jobs to
Operator response: Ensure you are working with the "monitored" for the selected instance or No to cancel
correct job before continuing with the cleanup. the request.

GJS4039W A Start Cleanup action was requested, GJS4044W Do you want to set all jobs to
but the JCL contains recovery "unmonitored" for the scheduled
statements. Perform the Start Cleanup instance instance_identifier?
with AR action.
Explanation: See message.
Explanation: See message.
System action: The program waits for your response.
System action: The Start Cleanup action is not
Operator response: Select Yes to set all jobs to
commenced.
"unmonitored" for the selected instance or No to cancel
Operator response: Perform the Start Cleanup with the request.
AR action.
GJS4045W Do you want to "kill" the selected
GJS4040E The selected period was not found in scheduled instances?
the z/OS database.
Explanation: See message.
Explanation: The selected period was not found in the
System action: The program waits for your response.
z/OS database.
Operator response: Select Yes to "kill" the selected
System action: The requested action did not complete
scheduled instances or No to cancel the request.
successfully.
Operator response: Specify a valid period.
GJS4046W Do you want to kill scheduled instance
instance_identifier?
GJS4041E The "From" priority cannot be greater
Explanation: See message.
than the "To" priority.
System action: The program waits for your response.
Explanation: The availability interval cannot be
defined if the From priority is greater than the To Operator response: Select Yes to "kill" the selected
priority. scheduled instance or No to cancel the request.
System action: The requested action did not complete
successfully. GJS4047W The chosen object can be viewed but
not modified because it was created or
Operator response: Type a To priority greater than the
modified with a version of the engine,
From priority.
Job Scheduling Console, or application
that is later than the version of the Job
GJS4042E In the section_name section, the "To Date" Scheduling Console or application you
is earlier than the "From Date". Type an are currently using. To modify the
earlier "From Date", or a later "To Date". object, upgrade the Job Scheduling
Console or the application.
Explanation: The query does not return any results
because the From Date is later than the To Date. Explanation: See message.
System action: The requested action did not complete System action: The object cannot be accessed.
successfully.
Operator response: Upgrade the Job Scheduling
Operator response: Type an earlier From Date, or type Console or the application.
a later To Date.

GJS4043W Do you want to set all jobs to

"monitored" for the scheduled instance
instance_identifier?

Chapter 60. Job Scheduling Console messages 381

GJS2001E • GJS2012E

Job Scheduling Console distributed messages

GJS2001E The version of the scheduler engine GJS2007E You cannot define the same dependency
VALUE_0 is not supported. twice in the same job.
Explanation: The scheduler engine version selected is Explanation: Dependencies between a job stream and
not supported. a job must be unique.
System action: The requested action did not complete System action: The requested action did not complete
successfully. successfully.
Operator response: Choose a scheduler engine that is Operator response: Modify a dependency in a job
a supported version. stream.

GJS2002E The From priority cannot be greater GJS2008E A job stream cannot have a follows
than the To priority. dependency from one of its own jobs.
Explanation: The availability interval cannot be Explanation: A follows dependency between a job
defined if the From priority is greater than the To stream and one of its job is not allowed.
priority.
System action: The requested action did not complete
System action: The requested action did not complete successfully.
successfully.
Operator response: Delete the dependency.
Operator response: Type a To priority greater than the
From priority.
GJS2009E A job stream cannot have a dependency
on itself.
GJS2004E The job definition name is mandatory.
Explanation: A job stream cannot have itself as a
Explanation: The job definition name field is dependency.
mandatory.
System action: The requested action did not complete
System action: The requested action did not complete successfully.
successfully.
Operator response: Delete the dependency.
Operator response: Type a valid job definition name
and all the other mandatory fields present in the panel.
GJS2010E The same dependency cannot be
defined twice in the same job stream.
GJS2005E The number of scheduled dependencies
Explanation: A dependency between job streams must
exceeds the maximum number allowed.
be unique.
Explanation: The maximum number of scheduled
System action: The requested action did not complete
dependencies has been reached.
successfully.
System action: The requested action did not complete
Operator response: Modify the dependency in a job
successfully.
stream and another job stream to make them unique.
Operator response: Remove the excess scheduled
dependencies.
GJS2011E Resource dependencies can be defined
at the job stream level or at the job
GJS2006E A job stream cannot contain two jobs level, but not at both levels.
with the same name.
Explanation: Resource dependencies can be defined
Explanation: The job name has to be unique in a job for Jobs or Job Streams, but not for both.
stream.
System action: The requested action did not complete
System action: The requested action did not complete successfully.
successfully.
Operator response: Delete one of the resource
Operator response: It is necessary to modify the dependencies at the job level or job stream level.
names of the jobs to make them unique.
GJS2012E The submit into job stream workstation
name is mandatory.

382 IBM Tivoli Workload Scheduler Job Scheduling Console: User’s Guide
 GJS2013E • GJS2023E

Explanation: The job stream workstation name field is

GJS2018E The login field is mandatory.
mandatory.
Explanation: The login field is mandatory.
System action: The requested action did not complete
successfully. System action: The requested action did not complete
successfully.
Operator response: Type a valid job stream
workstation name and all the other mandatory fields Operator response: Type a valid login and all the
present in the panel. other mandatory fields present in the panel.

GJS2013E The workstation name is mandatory. GJS2019E The workstation class name is
mandatory.
Explanation: The workstation name field is
mandatory. Explanation: The workstation class name field is
mandatory.
System action: The requested action did not complete
successfully. System action: The requested action did not complete
successfully.
Operator response: Type a valid workstation name
and all the other mandatory fields present in the panel. Operator response: Type a valid workstation class
name and all the other mandatory fields present in the
panel.
GJS2014E The script field is mandatory.
Explanation: The script field is mandatory.
GJS2020E The workstation class must contain at
System action: The requested action did not complete least one workstation or a wildcard.
successfully.
Explanation: The workstation class field must contain
Operator response: Type a valid script and all the at least one workstation or a wildcard.
other mandatory fields present in the panel.
System action: The requested action did not complete
successfully.
GJS2015E The command field is mandatory.
Operator response: Type a valid workstation class or
Explanation: The command field is mandatory. use a wildcard.
System action: The requested action did not complete
successfully. GJS2021E The parameter name is mandatory.
Operator response: Type a valid command and all the Explanation: The parameter name field is mandatory.
other mandatory fields present in the panel.
System action: The requested action did not complete
successfully.
GJS2016E The parameter in the task string is not
Operator response: Type a valid parameter name and
valid. The ^ character must precede the
all the other mandatory fields present in the panel.
first letter and follow the last letter of a
valid parameter name.
GJS2022E The prompt name is mandatory.
Explanation: The format for the parameter in the task
string is not valid. Explanation: The prompt name field is mandatory.
System action: The requested action did not complete System action: The requested action did not complete
successfully. successfully.
Operator response: Enclose the parameter name in the Operator response: Type a valid prompt name and all
^ character. the other mandatory fields present in the panel.

GJS2017E The job file field is mandatory. GJS2023E The domain manager name is
mandatory.
Explanation: The job file field is mandatory.
Explanation: The domain manager name field is
System action: The requested action did not complete
mandatory.
successfully.
System action: The requested action did not complete
Operator response: Type a valid job file and all the
successfully.
other mandatory fields present in the panel.
Operator response: Type a valid domain manager

Chapter 60. Job Scheduling Console messages 383

GJS2024E • GJS2033E

name and all the other mandatory fields present in the

GJS2030E The SAP job on the task panel was not
panel.
selected for this workstation. Select a
new SAP job on the task panel, or
GJS2024E The domain name is mandatory. change the workstation to the
workstation the SAP job is defined on.
Explanation: The domain name field is mandatory.
Explanation: The selected SAP Job is not defined for
System action: The requested action did not complete the selected workstation.
successfully.
System action: The requested action did not complete
Operator response: Type a valid domain name and all successfully.
the other mandatory fields present in the panel.
Operator response: Select a new SAP Job on the task
panel, or change the workstation to the workstation the
GJS2025E The calendar name is mandatory. SAP job is defined on.
Explanation: The calendar name field is mandatory.
System action: The requested action did not complete GJS2031E Unable to validate r3batch workstation
successfully. because it is not in the plan or the
connection with r3batch system failed
Operator response: Type a valid calendar name and
all the other mandatory fields present in the panel. Explanation: It is not possible to establish a
connection with the R/3 system.

GJS2026E At least one day must be defined for a System action: The requested action did not complete
calendar. successfully.

Explanation: At least one day must be defined for a Operator response: Try again later.
calendar.
System action: The requested action did not complete GJS2032E The job definition cannot be saved.
successfully. Reason: VALUE_0

Operator response: Type at least one day for the Explanation: The job definition could not be saved
calendar. due to an error that occurred in the Tivoli Workload
Scheduler engine. The error code is specified in the
message text.
GJS2027E The R/3 job information is mandatory.
System action: The requested action did not complete
Explanation: The R/3 job information is mandatory. successfully.
System action: The requested action did not complete Operator response: The reason displayed in the
successfully. message text represents an error code reported by the
Operator response: Type the R/3 job information and Tivoli Workload Scheduler engine. Refer to the
all the other mandatory fields present in the panel. Administration and Troubleshooting manual.

GJS2028E A job stream must be selected in the GJS2033E The job definition cannot be retrieved.
list. Reason: VALUE_0

Explanation: At least one job stream must be selected Explanation: The job definition could not be retrieved
in the list. due to an error that occurred in the Tivoli Workload
Scheduler engine. The error code is specified in the
System action: The requested action did not complete message text.
successfully.
System action: The requested action did not complete
Operator response: Select a job stream in the list. successfully.
Operator response: The reason displayed in the
GJS2029E A job must be selected in the list. message text represents an error code reported by the
Explanation: At least one job must be selected in the Tivoli Workload Scheduler engine. Refer to the
list. Administration and Troubleshooting manual.

System action: The requested action did not complete

successfully.
Operator response: Select a job from the list.

384 IBM Tivoli Workload Scheduler Job Scheduling Console: User’s Guide
 GJS2034E • GJS2041E

GJS2034E The job definition list cannot be loaded. GJS2038E The workstation classes cannot be
Reason: VALUE_0 loaded.
Reason: VALUE_0
Explanation: The job definition list could not be
loaded due to an error that occurred in the Tivoli Explanation: The workstation classes could not be
Workload Scheduler engine. The error code is specified loaded due to an error that occurred in the Tivoli
in the message text. Workload Scheduler engine. The error code is specified
in the message text.
System action: The requested action did not complete
successfully. System action: The requested action did not complete
successfully.
Operator response: The reason displayed in the
message text represents an error code reported by the Operator response: The reason displayed in the
Tivoli Workload Scheduler engine. Refer to the message text represents an error code reported by the
Administration and Troubleshooting manual. Tivoli Workload Scheduler engine. Refer to the
Administration and Troubleshooting manual.
GJS2035E The job definition cannot be deleted.
Reason: VALUE_0 GJS2039W The workstation class cannot be loaded.
Reason: VALUE_0
Explanation: The job definition could not be deleted
due to an error that occurred in the Tivoli Workload Explanation: The workstation class could not be
Scheduler engine. The error code is specified in the loaded due to an error that occurred in the Tivoli
message text. Workload Scheduler engine. The error code is specified
in the message text.
System action: The requested action did not complete
successfully. System action: The requested action did not complete
successfully.
Operator response: The reason displayed in the
message text represents an error code reported by the Operator response: The reason displayed in the
Tivoli Workload Scheduler engine. Refer to the message text represents an error code reported by the
Administration and Troubleshooting manual. Tivoli Workload Scheduler engine. Refer to the
Administration and Troubleshooting manual.
GJS2036E Another job definition cannot be
created. The task type is unknown for GJS2040E Multiple workstation classes cannot be
job VALUE_0. Edit the properties for this deleted.
job and select a new task type and Reason: VALUE_0
workstation.
Explanation: The multiple workstation classes could
Explanation: Another job definition could not be not be deleted due to an error that occurred in the
created because the task type is unknown for the Tivoli Workload Scheduler engine. The error code is
selected job. specified in the message text.
System action: The requested action did not complete System action: The requested action did not complete
successfully. successfully.
Operator response: Edit the properties for this job and Operator response: The reason displayed in the
select a new task type and workstation. message text represents an error code reported by the
Tivoli Workload Scheduler engine. Refer to the
Administration and Troubleshooting manual.
GJS2037E Multiple job definitions cannot be
deleted.
Reason: VALUE_0 GJS2041E The workstation class cannot be saved.
Reason: VALUE_0
Explanation: The job definitions could not be deleted
due to an error that occurred in the Tivoli Workload Explanation: The workstation class could not be saved
Scheduler engine. The error code is specified in the due to an error that occurred in the Tivoli Workload
message text. Scheduler engine. The error code is specified in the
message text.
System action: The requested action did not complete
successfully. System action: The requested action did not complete
successfully.
Operator response: The reason displayed in the
message text represents an error code reported by the Operator response: The reason displayed in the
Tivoli Workload Scheduler engine. Refer to the message text represents an error code reported by the
Administration and Troubleshooting manual. Tivoli Workload Scheduler engine. Refer to the

Chapter 60. Job Scheduling Console messages 385

GJS2042E • GJS2049E

Administration and Troubleshooting manual. message text represents an error code reported by the
Tivoli Workload Scheduler engine. Refer to the
Administration and Troubleshooting manual.
GJS2042E The workstation class cannot be deleted.
Reason: VALUE_0
GJS2046W The Windows user cannot be retrieved.
Explanation: The workstation class could not be
Reason: VALUE_0
deleted due to an error that occurred in the Tivoli
Workload Scheduler engine. The error code is specified Explanation: The Windows user could not be
in the message text. retrieved due to an error that occurred in the Tivoli
Workload Scheduler engine. The error code is specified
System action: The requested action did not complete
in the message text.
successfully.
System action: The requested action did not complete
Operator response: The reason displayed in the
successfully.
message text represents an error code reported by the
Tivoli Workload Scheduler engine. Refer to the Operator response: The reason displayed in the
Administration and Troubleshooting manual. message text represents an error code reported by the
Tivoli Workload Scheduler engine. Refer to the
Administration and Troubleshooting manual.
GJS2043E The Windows user list cannot be
loaded.
Reason: VALUE_0 GJS2047E The Windows user cannot be saved.
Reason: VALUE_0
Explanation: The Windows user list could not be
loaded due to an error that occurred in the Tivoli Explanation: The Windows user could not be saved
Workload Scheduler engine. The error code is specified due to an error that occurred in the Tivoli Workload
in the message text. Scheduler engine. The error code is specified in the
message text.
System action: The requested action did not complete
successfully. System action: The requested action did not complete
successfully.
Operator response: The reason displayed in the
message text represents an error code reported by the Operator response: The reason displayed in the
Tivoli Workload Scheduler engine. Refer to the message text represents an error code reported by the
Administration and Troubleshooting manual. Tivoli Workload Scheduler engine. Refer to the
Administration and Troubleshooting manual.
GJS2044E The Windows user cannot be deleted.
Reason: VALUE_0 GJS2048E The Windows user instance cannot be
saved.
Explanation: The Windows user could not be deleted
Reason: VALUE_0
due to an error that occurred in the Tivoli Workload
Scheduler engine. The error code is specified in the Explanation: The Windows user instance could not be
message text. saved due to an error that occurred in the Tivoli
Workload Scheduler engine. The error code is specified
System action: The requested action did not complete
in the message text.
successfully.
System action: The requested action did not complete
Operator response: The reason displayed in the
successfully.
message text represents an error code reported by the
Tivoli Workload Scheduler engine. Refer to the Operator response: The reason displayed in the
Administration and Troubleshooting manual. message text represents an error code reported by the
Tivoli Workload Scheduler engine. Refer to the
Administration and Troubleshooting manual.
GJS2045E The selected Windows users cannot be
deleted.
Reason: VALUE_0 GJS2049E The parameters cannot be loaded.
Reason: VALUE_0
Explanation: The selected Windows user list could not
be deleted due to an error that occurred in the Tivoli Explanation: The parameters could not be loaded due
Workload Scheduler engine. The error code is specified to an error that occurred in the Tivoli Workload
in the message text. Scheduler engine. The error code is specified in the
message text.
System action: The requested action did not complete
successfully. System action: The requested action did not complete
successfully.
Operator response: The reason displayed in the

386 IBM Tivoli Workload Scheduler Job Scheduling Console: User’s Guide
 GJS2050W • GJS2057E

Operator response: The reason displayed in the Operator response: The reason displayed in the
message text represents an error code reported by the message text represents an error code reported by the
Tivoli Workload Scheduler engine. Refer to the Tivoli Workload Scheduler engine. Refer to the
Administration and Troubleshooting manual. Administration and Troubleshooting manual.

GJS2050W The parameter cannot be retrieved. GJS2054E The prompts cannot be loaded.
Reason: VALUE_0 Reason: VALUE_0
Explanation: The parameter could not be retrieved Explanation: The prompts could not be loaded due to
due to an error that occurred in the Tivoli Workload an error that occurred in the Tivoli Workload Scheduler
Scheduler engine. The error code is specified in the engine. The error code is specified in the message text.
message text.
System action: The requested action did not complete
System action: The requested action did not complete successfully.
successfully.
Operator response: The reason displayed in the
Operator response: The reason displayed in the message text represents an error code reported by the
message text represents an error code reported by the Tivoli Workload Scheduler engine. Refer to the
Tivoli Workload Scheduler engine. Refer to the Administration and Troubleshooting manual.
Administration and Troubleshooting manual.
GJS2055W The prompt cannot be retrieved.
GJS2051E The multiple parameters cannot be Reason: VALUE_0
deleted.
Explanation: The prompt could not be retrieved due
Reason: VALUE_0
to an error that occurred in the Tivoli Workload
Explanation: The multiple parameters could not be Scheduler engine. The error code is specified in the
deleted due to an error that occurred in the Tivoli message text.
Workload Scheduler engine. The error code is specified
System action: The requested action did not complete
in the message text.
successfully.
System action: The requested action did not complete
Operator response: The reason displayed in the
successfully.
message text represents an error code reported by the
Operator response: The reason displayed in the Tivoli Workload Scheduler engine. Refer to the
message text represents an error code reported by the Administration and Troubleshooting manual.
Tivoli Workload Scheduler engine. Refer to the
Administration and Troubleshooting manual.
GJS2056E The multiple prompts cannot be
deleted.
GJS2052E The parameter cannot be saved. Reason: VALUE_0
Reason: VALUE_0
Explanation: The multiple prompts could not be
Explanation: The parameter could not be saved due to deleted due to an error that occurred in the Tivoli
an error that occurred in the Tivoli Workload Scheduler Workload Scheduler engine. The error code is specified
engine. The error code is specified in the message text. in the message text.
System action: The requested action did not complete System action: The requested action did not complete
successfully. successfully.
Operator response: The reason displayed in the Operator response: The reason displayed in the
message text represents an error code reported by the message text represents an error code reported by the
Tivoli Workload Scheduler engine. Refer to the Tivoli Workload Scheduler engine. Refer to the
Administration and Troubleshooting manual. Administration and Troubleshooting manual.

GJS2053E The parameter cannot be deleted. GJS2057E The prompt cannot be saved.
Reason: VALUE_0 Reason: VALUE_0
Explanation: The parameter could not be deleted due Explanation: The prompt could not be saved due to
to an error that occurred in the Tivoli Workload an error that occurred in the Tivoli Workload Scheduler
Scheduler engine. The error code is specified in the engine. The error code is specified in the message text.
message text.
System action: The requested action did not complete
System action: The requested action did not complete successfully.
successfully.
Operator response: The reason displayed in the

Chapter 60. Job Scheduling Console messages 387

GJS2058E • GJS2065W

message text represents an error code reported by the message text represents an error code reported by the
Tivoli Workload Scheduler engine. Refer to the Tivoli Workload Scheduler engine. Refer to the
Administration and Troubleshooting manual. Administration and Troubleshooting manual.

GJS2058E The prompt cannot be deleted. GJS2062E The calendar cannot be saved.
Reason: VALUE_0 Reason: VALUE_0
Explanation: The prompt could not be deleted due to Explanation: The calendar could not be saved due to
an error that occurred in the Tivoli Workload Scheduler an error that occurred in the Tivoli Workload Scheduler
engine. The error code is specified in the message text. engine. The error code is specified in the message text.
System action: The requested action did not complete System action: The requested action did not complete
successfully. successfully.
Operator response: The reason displayed in the Operator response: The reason displayed in the
message text represents an error code reported by the message text represents an error code reported by the
Tivoli Workload Scheduler engine. Refer to the Tivoli Workload Scheduler engine. Refer to the
Administration and Troubleshooting manual. Administration and Troubleshooting manual.

GJS2059E The calendars cannot be loaded. GJS2063E The calendar cannot be deleted.
Reason: VALUE_0 Reason: VALUE_0
Explanation: The calendars could not be loaded due Explanation: The calendar could not be deleted due to
to an error that occurred in the Tivoli Workload an error that occurred in the Tivoli Workload Scheduler
Scheduler engine. The error code is specified in the engine. The error code is specified in the message text.
message text.
System action: The requested action did not complete
System action: The requested action did not complete successfully.
successfully.
Operator response: The reason displayed in the
Operator response: The reason displayed in the message text represents an error code reported by the
message text represents an error code reported by the Tivoli Workload Scheduler engine. Refer to the
Tivoli Workload Scheduler engine. Refer to the Administration and Troubleshooting manual.
Administration and Troubleshooting manual.
GJS2064E The domains cannot be loaded.
GJS2060W The calendar cannot be retrieved. Reason: VALUE_0
Reason: VALUE_0
Explanation: The domains could not be loaded due to
Explanation: The calendar could not be retrieved due an error that occurred in the Tivoli Workload Scheduler
to an error that occurred in the Tivoli Workload engine. The error code is specified in the message text.
Scheduler engine. The error code is specified in the
System action: The requested action did not complete
message text.
successfully.
System action: The requested action did not complete
Operator response: The reason displayed in the
successfully.
message text represents an error code reported by the
Operator response: The reason displayed in the Tivoli Workload Scheduler engine. Refer to the
message text represents an error code reported by the Administration and Troubleshooting manual.
Tivoli Workload Scheduler engine. Refer to the
Administration and Troubleshooting manual.
GJS2065W The domain cannot be retrieved.
Reason: VALUE_0
GJS2061E The multiple calendars cannot be
Explanation: The domain could not be retrieved due
deleted.
to an error that occurred in the Tivoli Workload
Reason: VALUE_0
Scheduler engine. The error code is specified in the
Explanation: The multiple calendars could not be message text.
deleted due to an error that occurred in the Tivoli
System action: The requested action did not complete
Workload Scheduler engine. The error code is specified
successfully.
in the message text.
Operator response: The reason displayed in the
System action: The requested action did not complete
message text represents an error code reported by the
successfully.
Tivoli Workload Scheduler engine. Refer to the
Operator response: The reason displayed in the Administration and Troubleshooting manual.

388 IBM Tivoli Workload Scheduler Job Scheduling Console: User’s Guide
 GJS2066E • GJS2073E

GJS2066E The multiple domains cannot be GJS2070E The multiple prompts cannot be replied
deleted. to.VALUE_0.
Reason: VALUE_0 Reason: VALUE_1
Explanation: The multiple domains could not be Explanation: The selected multiple prompts could not
deleted due to an error that occurred in the Tivoli be replied to due to an error that occurred in the Tivoli
Workload Scheduler engine. The error code is specified Workload Scheduler engine. The error code is specified
in the message text. in the message text.
System action: The requested action did not complete System action: The requested action did not complete
successfully. successfully.
Operator response: The reason displayed in the Operator response: The reason displayed in the
message text represents an error code reported by the message text represents an error code reported by the
Tivoli Workload Scheduler engine. Refer to the Tivoli Workload Scheduler engine. Refer to the
Administration and Troubleshooting manual. Administration and Troubleshooting manual.

GJS2067E The domain cannot be saved. GJS2071E The link action for the domain VALUE_0
Reason: VALUE_0 cannot be performed.
Reason: VALUE_1
Explanation: The domain could not be saved due to
an error that occurred in the Tivoli Workload Scheduler Explanation: The link action for selected domain
engine. The error code is specified in the message text. could not be performed due to an error that occurred
in the Tivoli Workload Scheduler engine. The error
System action: The requested action did not complete
code is specified in the message text.
successfully.
System action: The requested action did not complete
Operator response: The reason displayed in the
successfully.
message text represents an error code reported by the
Tivoli Workload Scheduler engine. Refer to the Operator response: The reason displayed in the
Administration and Troubleshooting manual. message text represents an error code reported by the
Tivoli Workload Scheduler engine. Refer to the
Administration and Troubleshooting manual.
GJS2068E The domain cannot be deleted.
Reason: VALUE_0
GJS2072E The link action for the
Explanation: The domain could not be deleted due to
domainsVALUE_0cannot be performed.
an error that occurred in the Tivoli Workload Scheduler
Reason: VALUE_1
engine. The error code is specified in the message text.
Explanation: The link action for the selected domains
System action: The requested action did not complete
cannot be performed due to an error that occurred in
successfully.
the Tivoli Workload Scheduler engine. The error code is
Operator response: The reason displayed in the specified in the message text.
message text represents an error code reported by the
System action: The requested action did not complete
Tivoli Workload Scheduler engine. Refer to the
successfully.
Administration and Troubleshooting manual.
Operator response: The reason displayed in the
message text represents an error code reported by the
GJS2069E The prompt cannot be replied to.
Tivoli Workload Scheduler engine. Refer to the
VALUE_0.
Administration and Troubleshooting manual.
Reason: VALUE_1
Explanation: The selected prompt could not be replied
GJS2073E The unlink action for the
to due to an error that occurred in the Tivoli Workload
domainVALUE_0cannot be performed.
Scheduler engine. The error code is specified in the
Reason: VALUE_1
message text.
Explanation: The unlink action for the selected
System action: The requested action did not complete
domain could not be performed due to an error that
successfully.
occurred in the Tivoli Workload Scheduler engine. The
Operator response: The reason displayed in the error code is specified in the message text.
message text represents an error code reported by the
System action: The requested action did not complete
Tivoli Workload Scheduler engine. Refer to the
successfully.
Administration and Troubleshooting manual.
Operator response: The reason displayed in the

Chapter 60. Job Scheduling Console messages 389

GJS2074E • GJS2079E

message text represents an error code reported by the Operator response: Select a recognized time zone
Tivoli Workload Scheduler engine. Refer to the value.
Administration and Troubleshooting manual.
GJS2076E The start action for the
GJS2074E The unlink action for the domainsVALUE_0cannot be performed.
domainsVALUE_0 cannot be performed. Reason: VALUE_1
Reason: VALUE_1
Explanation: The start action for the selected domains
Explanation: The unlink action for the selected cannot be performed due to an error that occurred in
domains could not be performed due to an error that the Tivoli Workload Scheduler engine. The error code is
occurred in the Tivoli Workload Scheduler engine. The specified in the message text.
error code is specified in the message text.
System action: The requested action did not complete
System action: The requested action did not complete successfully.
successfully.
Operator response: The reason displayed in the
Operator response: The reason displayed in the message text represents an error code reported by the
message text represents an error code reported by the Tivoli Workload Scheduler engine. Refer to the
Tivoli Workload Scheduler engine. Refer to the Administration and Troubleshooting manual.
Administration and Troubleshooting manual.
GJS2077E Some of the stop actions for the
GJS2074W An unrecognized time zone value for domainVALUE_0were not completed.
the VALUE_0was specified. Reason: VALUE_1
Select a recognized time zone value, or
Explanation: Some of the stop actions were not
no time zone is set for VALUE_0.
completed for selected domain due to an error that
Explanation: See message. occurred in the Tivoli Workload Scheduler engine. The
error code is specified in the message text.
System action: Processing continues.
System action: The requested action did not complete
Operator response: Select a recognized time zone
successfully.
value, or leave the field blank.
Operator response: The reason displayed in the
message text represents an error code reported by the
GJS2075E Some of the start actions for the
Tivoli Workload Scheduler engine. Refer to the
domainVALUE_0were not completed.
Administration and Troubleshooting manual.
Reason: VALUE_1
Explanation: Some of the start actions were not
GJS2078E The stop action for the
completed for the domain due to an error that occurred
domainsVALUE_0cannot be performed.
in the Tivoli Workload Scheduler engine. The error
Reason: VALUE_1
code is specified in the message text.
Explanation: The stop action for the selected domains
System action: The requested action did not complete
could not be performed due to an error that occurred
successfully.
in the Tivoli Workload Scheduler engine. The error
Operator response: The reason displayed in the code is specified in the message text.
message text represents an error code reported by the
System action: The requested action did not complete
Tivoli Workload Scheduler engine. Refer to the
successfully.
Administration and Troubleshooting manual.
Operator response: The reason displayed in the
message text represents an error code reported by the
GJS2075W An unrecognized time zone for the
Tivoli Workload Scheduler engine. Refer to the
VALUE_0was specified.
Administration and Troubleshooting manual.
The time zone displayed is that
specified for the master domain
manager. GJS2079E The manager for the
Select a recognized time zone value or domainsVALUE_0cannot be switched.
the master domain manager time zone Reason: VALUE_1
value is used.
Explanation: The manager for the selected domains
Explanation: See message. could not be switched due to an error that occurred in
the Tivoli Workload Scheduler engine. The error code is
System action: Processing continues.
specified in the message text.

390 IBM Tivoli Workload Scheduler Job Scheduling Console: User’s Guide
 GJS2080E • GJS2089W

System action: The requested action did not complete System action: The requested action did not complete
successfully. successfully.
Operator response: The reason displayed in the Operator response: Type the password and
message text represents an error code reported by the confirmation password again, making sure they are
Tivoli Workload Scheduler engine. Refer to the identical.
Administration and Troubleshooting manual.
GJS2085E Passwords cannot exceed VALUE_0
GJS2080E There is an internal calendar error. characters.
An unanticipated condition was
Explanation: The password length cannot exceed the
encountered during the last operation:
maximum length.
VALUE_0
System action: The requested action did not complete
Explanation: An internal calendar error occurred.
successfully.
System action: The requested action did not complete
Operator response: Type a password with a number
successfully.
of characters that is less than or equal to the maximum
Operator response: Select another calendar. length.

GJS2081E A calendar name is required for all GJS2086E A problem occurred during password
calendars. There is at least one calendar encryption.
that has not been assigned a name.
Explanation: A problem occurred during password
Explanation: Every calendar must have a name. There encryption.
is at least one calendar that has not been assigned a
System action: The requested action did not complete
name.
successfully.
System action: The requested action did not complete
Operator response: Contact customer support.
successfully.
Operator response: Make sure that all the calendars
GJS2087E Workstation Name is a required field.
have a name defined.
Explanation: The Workstation Name field is
mandatory.
GJS2082E There are no days selected in the
calendar. System action: The requested action did not complete
successfully.
Explanation: At least one day must be defined for
every calendar. Operator response: Type a valid Workstation Name
and all the other mandatory fields present in the panel.
System action: The requested action did not complete
successfully.
GJS2088E The file name must include a path.
Operator response: Type at least one day for the
calendar. Explanation: The file name field must include a path.
System action: The requested action did not complete
GJS2083E No check boxes are selected. successfully.
Explanation: At least one check box must be selected Operator response: Type a valid file name: path + file
in the rule panel. name.
System action: The requested action did not complete
successfully. GJS2089W The workstation class is being renamed.
VALUE_0
Operator response: Select at least one check box from
the rule panel. Explanation: The workstation class is being renamed.
All dependencies for job scheduler objects in the
database that include it are also updated.
GJS2084E The password and confirmation
password do not coincide. Type the System action: If OK is clicked the workstation class
passwords again. is renamed. Otherwise the rename action is ignored.
Explanation: The password and confirmation Operator response: Click OK to rename the
password must coincide. workstation class or Cancel to cancel the rename action.

Chapter 60. Job Scheduling Console messages 391

GJS2090E • GJS2095E

GJS2090E All dependencies for job scheduler GJS2093W The parameter is being renamed:
objects in the database that include this VALUE_0
workstation name are also updated.
Explanation: The parameter might be part of a
Explanation: A workstation class might be part of a dependency for a job scheduler object in the database.
dependency for a job scheduler object in the database. If so, the dependency is also updated with the new
If so, the dependency is also updated with the new name.
name.
System action: If OK is clicked the parameter is
System action: If OK is clicked the workstation class renamed. Otherwise the rename action is ignored.
is renamed. Otherwise the rename action is ignored.
Operator response: Click OK to rename the parameter
Operator response: Click OK to rename the or click cancel to cancel the rename action.
workstation class or click Cancel to cancel the rename
action.
GJS2094E The parameter might be part of a
dependency for a job scheduler object
GJS2091W The prompt is being renamed: in the database. If so, the dependency is
VALUE_0 also updated with the new name.
Explanation: The prompt might be part of a Explanation: The parameter might be part of a
dependency for a job scheduler object in the database. dependency for a job scheduler object in the database.
If so, the dependency is also updated with the new If so, the dependency is also updated with the new
name. name.
System action: If OK is clicked the prompt is System action: If OK is clicked the parameter is
renamed. Otherwise the rename action is ignored. renamed. Otherwise the rename action is ignored.
Operator response: Click OK to rename the prompt or Operator response: Click OK to rename the parameter
Cancel to cancel the rename action. or click Cancel to cancel the rename action.

GJS2092E The prompt might be part of a GJS2094W The parameter is being deleted. The
dependency for a job scheduler object parameter might be part of a
in the database. If so, the dependency is dependency for a job scheduler object
also updated with the new name. in the database. If so, any later action
performed that refers to the old
Explanation: The prompt might be part of a
parameter returns an error.
dependency for a job scheduler object in the database.
If so, the dependency is also updated with the new Explanation: The parameter might be part of a
name. dependency for a job scheduler object in the database.
If so, any later action performed that refers to the old
System action: If OK is clicked the prompt is
parameter returns an error.
renamed. Otherwise the rename action is ignored.
System action: If OK is clicked the parameter is
Operator response: Click OK to rename the prompt or
deleted. Otherwise the delete action is ignored.
click Cancel to cancel the rename action.
Operator response: Click OK to delete the parameter
or click Cancel to cancel the delete action.
GJS2092W This prompt might be part of a
dependency for a job scheduler object
in the database. If so, any future action GJS2095E One or more errors occurred while the
performed that refers to the old prompt job list was being loaded.
returns an error. VALUE_0
Explanation: The prompt might be part of a Explanation: One or more errors occurred while the
dependency for a job scheduler object in the database. job list was being loaded.
If it is deleted, any future action performed that refers
System action: The requested action did not complete
to the old prompt returns an error.
successfully.
System action: If OK is clicked the prompt is deleted.
Operator response: Contact customer support.
Otherwise the delete action is ignored.
Operator response: Click OK to delete the prompt or
Cancel to cancel the delete action.

392 IBM Tivoli Workload Scheduler Job Scheduling Console: User’s Guide
 GJS2096W • GJS2103E

Operator response: Click OK to rename the domain or

GJS2096W The calendar is being renamed.
click Cancel to cancel the rename action.
VALUE_0
Explanation: The calendar might be part of a run
GJS2100E This domain might be part of a
cycle for a scheduler object in the database. If so, the
dependency for a job scheduler object
run cycle is also updated with the new name.
in the database. If so, the dependency is
System action: If OK is clicked the calendar is also updated with the new name.
renamed. Otherwise the rename action is ignored.
Explanation: A domain might be part of a
Operator response: Click OK to rename the calendar dependency for a job scheduler object in the database.
or click Cancel to cancel the rename action. If so, the dependency is also updated with the new
name.
GJS2097W See the error.log file for details. System action: If OK is clicked, the domain is
renamed. Otherwise the rename action is ignored.
Explanation: An error has occurred. See the error.log
file for details. Operator response:
System action: Processing continues.
GJS2101W This job might be part if a dependency
Operator response: See the error.log file for details.
for a job scheduler object in the
database. If so, the dependency is also
GJS2098E The calendar might be part of a run updated with the new name.
cycle for a scheduler object in the VALUE_0
database. If so, the run cycle is also
Explanation: This job might be part if a dependency
updated with the new name.
for a job scheduler object in the database. If so, the
Explanation: The calendar might be part of a run dependency is also updated with the new name.
cycle for a scheduler object in the database. If so, the
System action: If OK is clicked the job is renamed.
run cycle is also updated with the new name.
Otherwise the rename action is ignored.
System action: If OK is clicked the calendar is
Operator response: Click OK to rename the job, or
renamed. Otherwise the rename action is ignored.
click Cancel to cancel the rename action.
Operator response: Click OK to rename the calendar
or click Cancel to cancel the rename action.
GJS2102W This job might be part of a dependency
for a job scheduler object in the
GJS2098W This calendar might be part of a database. If so, the dependency is also
dependency for a job scheduler object updated with the new workstation data.
in the database. If so, any future action
Explanation: This job might be part of a dependency
performed that refers to the old calendar
for a job scheduler object in the database. If so, the
returns an error.
dependency is also updated with the new workstation
Explanation: The calendar might be part of a data.
dependency for a job scheduler object in the database.
System action: If OK is clicked the workstation is
If it is deleted any future action performed that refers
modified. Otherwise the request is ignored.
to the old calendar returns an error.
Operator response: Click OK to modify the
System action: If OK is clicked the calendar is deleted.
workstation, or click Cancel to cancel the modification
Otherwise the delete action is ignored.
request.
Operator response: Click OK to delete the calendar or
click Cancel to cancel the delete action.
GJS2103E This job might be part of a dependency
for a job scheduler object in the
GJS2099W The domain is being renamed: database. If so, the dependency is also
VALUE_0 updated with the new workstation data.
Explanation: This domain might be part of a Explanation: This job might be part of a dependency
dependency for a job scheduler object in the database. for a job scheduler object in the database. If so, the
If so, the dependency is also updated with the new dependency is also updated with the new workstation
name. data.
System action: If OK is clicked the domain is System action: If OK is clicked the workstation is
renamed. Otherwise the rename action is ignored. modified. Otherwise the request is ignored.

Chapter 60. Job Scheduling Console messages 393

GJS2104W • GJS2112E

Operator response: Click OK to modify the System action: The requested action did not complete
workstation, or click Cancel to cancel the modify successfully.
request.
Operator response: Type the ^ character before the
first letter and after the last letter of the parameter
GJS2104W This resource might be a dependency name.
for a job scheduler object. If so, the
dependency is also updated with the
GJS2108E The user login format for the MPE job
new workstation data.
is not valid.
Explanation: This resource might be a dependency for The user login must have the following
a job scheduler object. If so, the dependency is also format: [user].[account]<,group>
updated with the new workstation data. where each section can have a maximum
of eight characters.
System action: If OK is clicked the workstation is
modified. Otherwise the request is ignored. Explanation: The user login format for the MPE job is
not valid.
Operator response: Click OK to modify the
workstation, or click Cancel to cancel the modify System action: The requested action did not complete
request. successfully.
Operator response: Type the user login in the
GJS2105W This job stream might be part of a following format: [user].[account]<,group>, where each
dependency for a job scheduler object section can have a maximum of eight characters.
in the database. If so, the dependency is
also updated with the new workstation
GJS2109E The details field is mandatory.
data.
VALUE_0
Explanation: This job stream might be part of a
Explanation: The details field is mandatory.
dependency for a job scheduler object in the database.
If so, the dependency is also updated with the new System action: The requested action did not complete
workstation data. successfully.
System action: If OK is clicked the workstation is Operator response: Type valid details and all the
modified. Otherwise the request is ignored. other mandatory fields presents in the panel.
Operator response: Click OK to modify the
workstation, or click Cancel to cancel the modify GJS2110E The time restrictions field contains a
request. character that is not valid.
Explanation: The time restrictions field has a character
GJS2106E This job might be part of a dependency that is not valid.
for a job scheduler object in the
database. If so, the dependency is also System action: The requested action did not complete
updated with the new job name. successfully.

Explanation: This job might be part of a dependency Operator response: Type a valid time restriction and
for a job scheduler object in the database. If so, the all the other mandatory fields presents in the panel.
dependency is also updated with the new job name.
System action: If OK is clicked the job is renamed. GJS2111E The repeat every field contains a
Otherwise the rename request is ignored. character that is not valid.

Operator response: Click OK to rename the job, or Explanation: The repeat every field contains a
click Cancel to cancel the rename request. character that is not valid.
System action: The requested action did not complete
GJS2107E The parameter format for the login successfully.
string is not valid. Operator response: Type a valid repeat every and all
The ^ character must precede the first the other mandatory fields in the panel.
letter and follow the last letter of a
parameter name.
GJS2112E The start year must precede the end
Explanation: The format for the parameter in the login year.
string is not valid. The ^ character must precede the
first letter and follow the last letter of a parameter Explanation: In the "Day of Month" section, the start
name. year field must precede the end year.

394 IBM Tivoli Workload Scheduler Job Scheduling Console: User’s Guide
 GJS2113E • GJS2122E

System action: The requested action did not complete

GJS2118E There are too many quote characters in
successfully.
the dependency field.
Operator response: Type a start year that precedes the
Explanation: There are too many quote characters in
end year.
the dependency field.
System action: The requested action did not complete
GJS2113E The start month must precede the end
successfully.
month.
Operator response: Make sure that the dependency
Explanation: In the "Day of Month" section, the start
field has quote character only at the beginning and at
month field must precede the end month.
the end.
System action: The requested action did not complete
successfully.
GJS2119E This dependency contains a workstation
Operator response: Type a start month that precedes name that is not valid.
the end month.
Explanation: The workstation name in the
dependency field is not a valid workstation name.
GJS2114W The job name field is mandatory.
System action: The requested action did not complete
Explanation: The job name field is mandatory. successfully.
System action: The requested action did not complete Operator response: Correct the workstation name in
successfully. the dependency field.

Operator response: Type a valid job name and all the

other mandatory fields in the panel. GJS2120E This dependency contains a job stream
name that is not valid.
GJS2115E The network agent field is mandatory. Explanation: The job stream name in the dependency
field is not valid.
Explanation: The network agent field is mandatory.
System action: The requested action did not complete
System action: The requested action did not complete successfully.
successfully.
Operator response: Correct the job stream name in the
Operator response: Type a valid network agent and dependency field.
all the other mandatory fields in the panel.

GJS2121E This dependency contains a job name

GJS2116E The dependency value has exceeded the that is not valid.
maximum field length.
Explanation: The job name in the dependency field is
Explanation: The dependency value cannot exceed the not valid.
maximum field length.
System action: The requested action did not complete
System action: The requested action did not complete successfully.
successfully.
Operator response: Correct the job name in the
Operator response: Type a dependency value with a dependency field.
character number less than or equal to the maximum
field length.
GJS2122E The successors for the job stream cannot
be retrieved.
GJS2117E If the dependency value begins with a Reason: VALUE_0
quote character it must end with a quote
character. Explanation: The successor for the job stream could
not be retrieved due to an error that occurred in the
Explanation: If the dependency value begins with a Tivoli Workload Scheduler engine. The error code is
quote character it must end with a quote character. specified in the message text.
System action: The requested action did not complete System action: The requested action did not complete
successfully. successfully.
Operator response: Make sure that the dependency Operator response: The reason displayed in the
field begins and ends with a quote character. message text represents an error code reported by the
Tivoli Workload Scheduler engine. Refer to the
Administration and Troubleshooting manual.

Chapter 60. Job Scheduling Console messages 395

GJS2123E • GJS2131E

GJS2123E The successors of the job cannot be GJS2128E The specified workstation and/or job
retrieved. name was not found.
Reason: VALUE_0
Explanation: The specified workstation and/or job
Explanation: The successors for the job could not be name was not found.
retrieved due to an error that occurred in the Tivoli
System action: The requested action did not complete
Workload Scheduler engine. The error code is specified
successfully.
in the message text.
Operator response: Type a valid workstation and/or a
System action: The requested action did not complete
valid job name.
successfully.
Operator response: The reason displayed in the
GJS2129E The SAP job definition cannot be saved.
message text represents an error code reported by the
Reason: VALUE_0
Tivoli Workload Scheduler engine. Refer to the
Administration and Troubleshooting manual. Explanation: The SAP job definition could not be
saved due to an error that occurred in the Tivoli
Workload Scheduler engine. The error code is specified
GJS2124E The job or job stream cannot be
in the message text.
submitted.
Reason: VALUE_0 System action: The requested action did not complete
successfully.
Explanation: The job or job stream could not be
submitted due to an error that occurred in the Tivoli Operator response: The reason displayed in the
Workload Scheduler engine. The error code is specified message text represents an error code reported by the
in the message text. Tivoli Workload Scheduler engine. Refer to the
Administration and Troubleshooting manual.
System action: The requested action did not complete
successfully.
GJS2130W This action modifies the SAP Job ID in
Operator response: The reason displayed in the
the Tivoli Workload Scheduler job
message text represents an error code reported by the
definition.
Tivoli Workload Scheduler engine. Refer to the
Modifying the SAP Job creates a new
Administration and Troubleshooting manual.
SAP Job and deletes the current one.
The Tivoli Workload Scheduler job
GJS2125E The time zone field is required for the definition must be saved to save the
master when time zones are enabled. new SAP Job ID. Otherwise, the Tivoli
Workload Scheduler job definition is
Explanation: If the time zones are enabled, the time
not valid.
zone field is mandatory for the master.
Explanation: This action modifies the SAP Job ID in
System action: The requested action did not complete
the Tivoli Workload Scheduler job definition. Modifying
successfully.
the SAP Job creates a new SAP Job and deletes the
Operator response: Type a valid time zone. current one. The Tivoli Workload Scheduler job
definition must be saved to save the new SAP Job ID.
Otherwise, the Tivoli Workload Scheduler job definition
GJS2126W There is a Modify Step Error. is not valid.
Reason: VALUE_0
System action: If OK is clicked the SAP Job ID is
Explanation: There is a Modify Step Error due to an modified. Otherwise the request is ignored.
error that occurred in the Tivoli Workload Scheduler
engine. The error code is specified in the message text. Operator response: Click OK to modify the SAP job
ID or click Cancel to cancel the modify request.
System action: The requested action did not complete
successfully.
GJS2131E The SAP job definition cannot be
Operator response: The reason displayed in the renamed. This is not valid for a modify
message text represents an error code reported by the operation.
Tivoli Workload Scheduler engine. Refer to the
Administration and Troubleshooting manual. Explanation: The SAP job definition could not be
renamed.
System action: The requested action did not complete
successfully.
Operator response: Click Save and Close to rename

396 IBM Tivoli Workload Scheduler Job Scheduling Console: User’s Guide
 GJS2132E • GJS2143E

the job. Otherwise, enter the original job name and Operator response: Data has exceeded the limit.
click Modify and Close to modify the job.
GJS2137E The specified calendar does not exist.
GJS2132E The file plan view cannot be loaded.
Explanation: The specified calendar does not exist.
Reason: VALUE_0
System action: The requested action did not complete
Explanation: The file plan view could not be loaded
successfully.
due to an error that occurred in the Tivoli Workload
Scheduler engine. The error code is specified in the Operator response: Specify another calendar
message text.
System action: The requested action did not complete GJS2138W The specified domain VALUE_0 does not
successfully. exist.
Operator response: The reason displayed in the Explanation: The domain does not exist.
message text represents an error code reported by the
Tivoli Workload Scheduler engine. Refer to the System action: Processing continues.
Administration and Troubleshooting manual. Operator response: Click OK to continue, or click
Cancel to specify a new domain.
GJS2133E The job output could not be loaded
because it uses an unsupported GJS2139E The specified workstation was not
encoding. found.
Explanation: The job output could not be loaded Explanation: The specified workstation was not found.
because it uses a unsupported encoding.
System action: The requested action did not complete
System action: The requested action did not complete successfully.
successfully.
Operator response: Type a valid workstation.
Operator response: Contact customer support.

GJS2141E The specified recovery workstation and

GJS2134W The deadline precedes or is equal to the job name combination was not found.
start time.
Do you want to proceed? Explanation: The workstation and job name
combination specified as a recovery option was not
Explanation: The deadline precedes or is equal to the found. Either the workstation, or the job name, or both
start time. are incorrect.
System action: The requested action did not complete System action: The requested action did not complete
successfully. successfully.
Operator response: The deadline must be greater than Operator response: Make sure that the specified
the start time, or one of two must be disabled. workstation and specified job name exist and are typed
correctly.
GJS2135E The specified workstation and/or job
stream name was not found. GJS2142E The recovery option job cannot have the
Explanation: The specified workstation and/or job same name as the job being defined.
stream name was not found. Explanation: The job name specified for the recovery
System action: The requested action did not complete option is the same as the job that is being defined.
successfully. System action: The requested action did not complete
Operator response: Type a valid workstation and/or a successfully.
valid job stream name. Operator response: Type a recovery option job name
that is different from the job being defined.
GJS2136E There is not enough memory to
complete this action successfully. GJS2143E A job stream cannot have a dependency
Explanation: The CPU memory has reached the 100% on one of its jobs when the resolution
level. It is not possible to perform this action criteria is other than the default or the
successfully. closest preceding.

System action: The action requested has not Explanation: To create a dependency between a job
completed successfully. stream and one of its jobs the resolution criteria must

Chapter 60. Job Scheduling Console messages 397

GJS2144E • GJS5005E

be either "Use default" or "Closest preceding".

GJS5001I A new run cycle is being created. If
System action: The requested action did not complete another run cycle of this kind already
successfully. exists for this job stream, the two run
cycles are merged by the mapper.
Operator response: Change the resolution criteria for
the dependencies of the job stream jobs. Explanation: A new run cycle is being created. If
another run cycle of this kind already exists for this job
stream, the two run cycles are merged by the mapper.
GJS2144E A job stream cannot have a dependency
on itself when the resolution criteria is System action: If the answer to previous question is
other than the default or the closest Yes then a new run cycle is created. Otherwise the
preceding. request is ignored.
Explanation: To create a dependency on a job stream Operator response: Click Yes to create the new run
with itself the resolution criteria must be either "Use cycle or click No to cancel the create request.
default" or "Closest preceding".
System action: The requested action did not complete GJS5002W Do you want cancel the selected job
successfully. instances?
Operator response: Change the resolution criteria for Explanation: The selected job instances are being
the dependencies of the job stream. deleted.
System action: If the answer to previous question is
GJS2145W The following jobs are already in the Yes then the selected job instances are deleted.
job stream: Otherwise the request is ignored.
VALUE_0
Operator response: Click Yes to delete the job
Explanation: Some of the selected jobs are already instances, or click No to cancel the delete request.
present in the job stream. Continuing the action
prevents those jobs from entering.
GJS5003W Do you want cancel the selected job
System action: When Yes is selected, the jobs already stream instances?
present are prevented from entering the job stream.
Explanation: The selected job stream instances are
Otherwise the action is cancelled.
being deleted.
Operator response: Click Yes to submit the selected
System action: If the answer to previous question is
jobs that are not already present in the job stream. Click
Yes then the selected job stream instances are deleted.
No to cancel the operation.
Otherwise the request is ignored.
Operator response: Click Yes to delete the job stream
GJS2146E The parameter in the login string is not
instances, or click No to cancel the delete request.
valid. The ^ character must precede the
first letter and follow the last letter of a
valid parameter name. GJS5004W Do you want to confirm the selected job
instances?
Explanation: The format for the parameter in the login
string is not valid. Explanation: The selected job instances are being
confirmed.
System action: The requested action did not complete
successfully. System action: If the answer to previous question is
Yes then the selected job instances are confirmed.
Operator response: Enclose the parameter name in the
Otherwise the request is ignored.
^ character.
Operator response: Click Yes to confirm the job
instances, or click No to cancel the request.
GJS2147E The resource VALUE_0 does not exist.
Explanation: The specified resource does not exist.
GJS5005E A job stream instance cannot have a
System action: The requested action did not complete dependency on itself or on its jobs.
successfully.
Explanation: A job stream instance cannot have a
Operator response: Choose a resource that exists. dependency on itself or on its jobs
System action: The requested action did not complete
successfully.
Operator response: Remove the job stream instance

398 IBM Tivoli Workload Scheduler Job Scheduling Console: User’s Guide
 GJS5006E • GJS5048W

dependency on itself or on its jobs. or click No to cancel the request.

GJS5006E A job instance cannot have a GJS5042W Do you want to stop the selected
dependency on itself or on its job workstations?
stream instance.
Explanation: You are requesting a stop action on the
Explanation: A job instance cannot have a dependency selected workstations.
on itself or on its job stream instance.
System action: If the answer to previous question is
System action: The requested action did not complete Yes the selected workstations are stopped. Otherwise
successfully. the request is ignored.
Operator response: Remove the job instance Operator response: Click Yes to stop all the selected
dependency on itself or on its job stream instance. workstations or click No to cancel the request.

GJS5027W Do you want to release all dependencies GJS5043W Do you want to stop workstation
on the selected job instances? VALUE_0?
Explanation: You are requesting that all the Explanation: You are requesting to stop the selected
dependencies of the job instance are released. workstation.
System action: If the answer to previous question is System action: If the answer to previous question is
Yes all dependencies on the selected job instances are Yes the selected workstation is stopped. Otherwise the
released. Otherwise the request is ignored. request is ignored.
Operator response: Click Yes to release the Operator response: Click Yes to stop the workstation
dependencies or click no to cancel the release request. or click No to cancel the request.

GJS5028W Do you want to release all dependencies GJS5046W Do you want to unlink the selected
on the selected job stream instances? workstations?
Explanation: You are requesting that all the Explanation: You are requesting that the selected
dependencies of the job stream instance are released. domains are unlinked.
System action: If the answer to previous question is System action: If the answer to previous question is
Yes then all dependencies on the selected job stream Yes the selected workstations are unlinked. Otherwise
instances are released. Otherwise the request is ignored. the request is ignored.
Operator response: Click Yes to release the Operator response: Click Yes to unlink the selected
dependencies or click no to cancel the release request. workstations or click No to cancel the request.

GJS5034W Do you want rerun the selected job GJS5047W Do you want to unlink workstation
instances? VALUE_0?
Explanation: You are requesting a rerun of the Explanation: You are requesting that the selected
selected job instances. workstation is unlinked.
System action: If the answer to previous question is System action: If the answer to previous question is
Yes then the selected job instances are rerun. Otherwise Yes the selected workstation is unlinked. Otherwise the
the request is ignored. request is ignored.
Operator response: Click Yes to rerun the selected job Operator response: Click Yes to unlink the selected
instances or click No to cancel the request. workstation or click No to cancel the request.

GJS5035W Do you want to resubmit all the selected GJS5048W There is an error.
instances? Reason: VALUE_0
Explanation: You are requesting a resubmit of the Explanation: A problem has arisen due to an error
selected instances. that occurred in the Tivoli Workload Scheduler engine.
The error code is specified in the message text.
System action: If the answer to previous question is
Yes the selected instances are resubmitted. Otherwise System action: The requested action did not complete
the request is ignored. successfully.
Operator response: Click Yes to resubmit the instances Operator response: The reason displayed in the

Chapter 60. Job Scheduling Console messages 399

GJS5049W • GJS5059E

message text represents an error code reported by the

GJS5054W Return code expression contains some
Tivoli Workload Scheduler engine. Refer to the
invalid operands:\nVALUE_0 is not
Administration and Troubleshooting manual.
correct
Explanation: Only boolean operator can be used.
GJS5049W The start time is later than the latest
start time. System action: The requested action did not complete.
Do you want to proceed? Return code expression must be corrected to finish the
action
Explanation: The typed start time is later than the
latest start time. Operator response: Type a correct return code
expression
System action: The requested action did not complete
successfully.
GJS5055W The plan cannot be submitted because
Operator response: Type an earlier start time.
an alternative plan was selected for the
current engine.
GJS5050W The latest start time is later than the
Explanation: If an alternative plan is selected for an
deadline time.
engine, its jobs or job streams cannot be submitted.
Do you want to proceed?
System action: The requested action did not complete
Explanation: The typed latest start time is later than
successfully.
the deadline time.
Operator response: Restore the plan before submitting
System action: The requested action did not complete
it.
successfully.
Operator response: Type an earlier start time.
GJS5056W The restore operation can be performed
only if an alternative plan was
GJS5051W The parenthesis in the return code previously selected for the current
expression are not valid. VALUE_0 is not engine.
correct.
Explanation: The current engine symphony file has
Explanation: Each open parenthesis must match a not been modified, therefore the plan cannot be
corresponding closed parenthesis restored.
System action: The requested action did not complete. System action: The requested action did not complete
Return code expression must be corrected to finish the successfully.
action
Operator response: Select an alternate plan before
Operator response: Type a correct return code performing the restore operation.
expression
GJS5058E Job is hosted by cpuVALUE_0, resource
GJS5052W The return code expression contains VALUE_1is hosted by cpu VALUE_2
some operators that are not valid:
Explanation: To add a resource it must have the same
VALUE_0 is not correct.
workstation as the job.
Explanation: Only greater than or less than operands
System action: The requested action did not complete
can be used.
successfully.
System action: The requested action did not complete.
Operator response: Select a resource that is resident
Operator response: Type a correct return code on the same workstation as the job.
expression using only boolean operators.
GJS5059E The job output cannot be loaded
GJS5053W The return code expression is not valid: because the STDLIST file is too large.
VALUE_0 is not correct.
Explanation: The job output could not be loaded
Explanation: The return code expression is not valid. because the STDLIST file is too large.

System action: The requested action did not complete. System action: The requested action did not complete
successfully.
Operator response: Type a correct return code
expression. Operator response: Remove some of the entries in the
STDLIST file.

400 IBM Tivoli Workload Scheduler Job Scheduling Console: User’s Guide
 GJS5059W • GJS5070I

dependency for a job scheduler object in the database.

GJS5059W The Windows user password cannot be
If they are deleted, any future action performed that
changed because an alternate plan was
refers to the parameters returns an error.
selected for the selected engine.
System action: If the answer to previous question is
Explanation: When an alternate plan is selected for
Yes the parameters are deleted. Otherwise the request is
the engine, the Windows user password cannot be
ignored.
changed.
Operator response: Check that you have selected the
System action: The requested action did not complete
correct parameters
successfully.
Operator response: Restore the plan and then change
GJS5067W The selected prompts might be part of a
the Windows user password.
dependency for a job scheduling object
in the database. If so, any future action
GJS5063W The following external job performed that refers to the prompts
dependencies do not exist: VALUE_0. returns an error.
Explanation: The given list of external job Explanation: These prompts might be part of a
dependencies contains one or more inexistent jobs. dependency for a job scheduler object in the database.
If they are deleted, any future action performed that
System action: Processing continues.
refers to the prompts returns an error.
Operator response: Make sure that all the specified
System action: If OK is clicked the prompts are
dependencies are correctly defined before the job
deleted. Otherwise the request is ignored.
stream is run.
Operator response: Click OK to delete the prompts or
click Cancel to cancel the delete request.
GJS5064W The following external job stream
dependencies do not exist: VALUE_0.
GJS5069I The job requires VALUE_0 units of
Explanation: The given list of external job stream
resource VALUE_1, but only 1 is
dependencies contains one or more inexistent job
available.
streams.
Explanation: A number of units of the specified
System action: Processing continues.
resource has been requested for the selected job, but the
Operator response: Make sure that all the specified number exceeds the available resources.
dependencies are correctly defined at before the job
System action: The requested action did not complete
stream is run.
successfully.
Operator response: Modify the number of units of the
GJS5065W The selected calendars might be part of
specified resource to a value less than or equal to the
a dependency for a job scheduler object
number of units available, or remove the resource
in the database. If so, any future action
dependency from the job.
performed that refers to the calendars
returns an error.
GJS5070I The job requires VALUE_0 units of
Explanation: The selected calendars might be part of a
resource VALUE_1, but only VALUE_2
dependency for a job scheduler object in the database.
are available.
If so, and they are deleted, any future action performed
that refers to the old calendars returns an error. Explanation: A number of units of the specified
resource has been requested for the selected job, but the
System action: If the answer to previous question is
number exceeds the available resources.
Yes the calendars are deleted. Otherwise the request is
ignored. System action: The requested action did not complete
successfully.
Operator response: Click Yes to delete the selected
calendars or click No to cancel the delete request. Operator response: Modify the number of units of the
specified resource to a value less than or equal to the
number of units available, or remove the resource
GJS5066W The selected parameters might be part
dependency from the job
of a dependency for a job scheduling
object in the database. If so, any future
action performed that refers to the
parameters returns an error.
Explanation: These parameters might be part of a

Chapter 60. Job Scheduling Console messages 401

GJS5071E • GJS5079W

GJS5071E The job stream cannot be saved because GJS5075E In the VALUE_0 section, when a value
either the resource VALUE_0 does not for the Date field is set, a value for the
exist, or the rights required to use it are Time field must also be set.
not sufficient to use the resource.
Explanation: The query does not return any results
Explanation: A dependency was specified on a because the date filter is not set correctly.
resource that does not exist, or the rights of the
System action: The requested action did not complete
specifying user are not sufficient to use the resource.
successfully.
The resource might have been removed from the
database after the dependency was added. Operator response: Set values for both Date and Time
fields, or do set values for either Date and Time fields.
System action: The requested action did not complete
successfully.
GJS5076E In the VALUE_0 section, when a value
Operator response: Remove the resource dependency.
for the Time field is set, a value for the
Create the resource and recreate the dependency.
Date field must also be set.
Explanation: The query does not return any results
GJS5072E The job stream cannot have an external
because the date filter is not set correctly.
dependency on a job defined in the
same job stream. System action: The requested action did not complete
successfully.
Explanation: A job stream can have an external
dependency on a job defined in another job stream. Operator response: Set values both for Time and Date
Therefore, a job defined in a job stream different from fields, or do not set values for either Date and Time
the one for where the dependency is being defined fields.
must be selected.
System action: The requested action did not complete GJS5077E The password for the Windows user
successfully. VALUE_0cannot be changed. Reason:
VALUE_1
Operator response: Select a different job stream from
the one where an external dependency is being defined. Explanation: The specified password for the Windows
user password could not be set. Some problem has
been encountered during this operation.
GJS5073E A positive number of resource units
must be specified. System action: The requested action did not complete
successfully.
Explanation: A negative or null number of units for
the resource was specified. Operator response: Make sure that the specified user
name, Windows domain and workstation correctly
System action: The requested action did not complete
correspond to an existing Windows user.
successfully.
Operator response: Modify the number of units for
GJS5078E The object cannot be unlocked. Reason:
the specified resource to a positive value less than or
VALUE_0
equal to the number of units available.
Explanation: It is not possible to unlock the object.
Some problem has been encountered during this
GJS5074E In the VALUE_0 section, the To Date is
operation.
earlier than the From Date. Type an
earlier From Date, or type a later To System action: The requested action did not complete
Date. successfully.
Explanation: The query does not return any results Operator response: Refer to the reason indicated in
because the From Date is later than the To Date. the message to resolve the issue.
System action: The requested action did not complete
successfully. GJS5079W The value specified for the upper limit
of the time interval is lower than the
Operator response: Type an earlier From Date, or type
one specified for the lower limit.
a later To Date.
Explanation: The values specified for the upper limit
of the time interval is lower than that specified for the
lower limit.
System action: Processing continues.

402 IBM Tivoli Workload Scheduler Job Scheduling Console: User’s Guide
 GJS5080E • GJS5093E

Operator response: Change one of the limits to grant

GJS5085W The value specified for the upper limit
consistent definition of the interval.
of the time interval is equal to the one
specified for the lower limit.
GJS5080E The value specified for validity interval
Explanation: As the upper and lower limits for the
end is lower than the one specified for
time interval are equal, the interval itself is empty.
the validity interval start.
System action: Processing continues.
Explanation: The value specified for validity interval
end is lower than the one specified for the validity Operator response: Change one of the limits to define
interval start. relevant interval.
System action: Processing continues.
GJS5086E The run cycle cannot be saved because
Operator response: Change one of the limits to grant
no days were selected in the list.
consistent definition of the interval.
Explanation: To save a run cycle a run cycle frequency
must be specified.
GJS5081E The Start time must be defined for a
time dependent job.VALUE_0 System action: The requested action did not complete
successfully.
Explanation: When the job is a time dependent job it
must have a start time defined. Operator response: Select one or more days in the list
in order to specify the Run Cycle frequency.
System action: The requested action did not complete
successfully.
GJS5089E The start date is later than the end date.
Operator response: Define start time or set the job as
time independent. Explanation: The end date must be later than the start
date.
GJS5082E The name specified for the Run Cycle is System action: The requested action did not complete
not valid. successfully.
Explanation: The name specified for the run cycle is Operator response: Enter an end date that is later
not valid. than the start date or leave the end date blank.
System action: The requested action did not complete
successfully. GJS5091E The offset field contains an value that is
not valid.
Operator response: Specify a valid name for the run
cycle. Explanation: A value that is not valid was inserted in
the offset field. The offset value must be numeric.
GJS5083E It is mandatory to specify a Run Cycle System action: The requested action did not complete
name. successfully.
Explanation: The run cycle name field is a mandatory Operator response: Type a valid number of days in
field. the offset field.
System action: The requested action did not complete
successfully. GJS5092E The selected workstation must have
Other as its operating system.
Operator response: Type a name for the run cycle.
Explanation: The selected workstation must have
Other as the workstation type.
GJS5084E One or more jobs in the job stream are
defined on a different workstation class. System action: The requested action did not complete
successfully.
Explanation: If a job stream is defined in a
workstation class, then all of its jobs must be defined Operator response: Select another workstation that
either on a workstation, or in the same workstation has Other as its operating system.
class.
System action: The requested action did not complete GJS5093E The prompt VALUE_0 does not exist.
successfully.
Explanation: A dependency was specified on a
Operator response: Set the workstation of this job prompt that does not exist. The prompt might have
stream to the original value or hit Cancel. been removed from the database after the dependency
was added.

Chapter 60. Job Scheduling Console messages 403

GJS5094E • GJS5103I

System action: The requested action did not complete the IBM Tivoli Workload Scheduler for Applications
successfully. User’s Guide.
Operator response: Remove the prompt dependency.
Create the prompt and recreate the dependency. GJS5098E The requested action cannot be
performed because it is supported from
XBP level 2.0 and ITWS for
GJS5094E The job VALUE_0cannot be submitted.
Applications 8.2.1 FP1.
Reason: VALUE_1
Explanation: The XBP level available does not support
Explanation: The job could not be submitted due to
the requested action. The action is supported from XBP
an error that occurred in the Tivoli Workload Scheduler
2.0 and ITWS for Applications 8.2.1 FP1.
engine. The error code is specified in the message text.
System action: The requested action did not complete
System action: The requested action did not complete
successfully.
successfully.
Operator response: Choose another action, or upgrade
Operator response: The reason displayed in the
to a supported level of XBP.
message text represents an error code reported by the
Tivoli Workload Scheduler engine. Refer to the
Administration and Troubleshooting manual. GJS5100E The specified plan cannot be generated.
Reason: VALUE_0
GJS5095E The Raise Event did not complete Explanation: It is not possible to generate the plan.
successfully. The error reason is given in the message text.
Reason:VALUE_0
System action: The requested action did not complete
Explanation: It is not possible to raise the specified successfully.
event due to an error in the Tivoli Workload Scheduler
Operator response: Fix the problem and try again.
for Applications. The error code is specified in the
message text.
GJS5101E The newly generated plan cannot be
System action: The requested action did not complete
used as an alternate plan. Reason:
successfully.
VALUE_0
Operator response: The reason displayed in the
Explanation: The new plan was generated but it is not
message text represents an error code reported by the
possible to set it as an alternate plan. The error reason
Tivoli Workload Scheduler for Applications. Refer to
is given in the message text.
the IBM Tivoli Workload Scheduler for Applications
User’s Guide. System action: The requested action did not complete
successfully.
GJS5096E The Raise Event field is mandatory. Operator response: Fix the problem and try again.
Explanation: The Raise Event field is a mandatory
field. GJS5102E There is more than one instance of the
selected job stream.
System action: The requested action did not complete
Submit the job into the job stream with
successfully.
the ID VALUE_0?
Operator response: Type a valid values in the Raise
Explanation: There is more than one instance of the
Event field.
selected job stream. Tivoli Workload Scheduler
proposed an instance to be submitted in.
GJS5097E The Table Criteria is in error.
System action: If OK is clicked, the job is submitted
Reason:VALUE_0
into the proposed job stream instance. If cancel is
Explanation: There is a problem with Table Criteria clicked the submit action is ignored.
due to an error in the Tivoli Workload Scheduler for
Operator response: Click OK to submit or click Cancel
Applications. The error code is specified in the message
to cancel the submit action.
text.
System action: The requested action did not complete
GJS5103I The job definition "VALUE_0" is being
successfully.
moved on the workstation class
Operator response: The reason displayed in the "VALUE_1", verify that job streams that
message text represents an error code reported by the are using the job definition are defined
Tivoli Workload Scheduler for Applications. Refer to on the workstation class "VALUE_0".
Do you want to continue?

404 IBM Tivoli Workload Scheduler Job Scheduling Console: User’s Guide
 GJS5104W • GJS5110W

Explanation: The selected job definition is used by one

GJS5107W The job stream is being defined on a
or more job streams. Verify that these job streams are
workstation class. Do you want to
defined on the same workstation class
continue?
System action: If OK is clicked, the job definition is
Explanation: You are defining this job stream on a
saved. If cancel is clicked the save action is ignored.
workstation class. You can choose to continue, or
Operator response: Click OK to submit or click Cancel change the workstation for this job stream.
to cancel the submit action.
System action: If the answer to previous question is
yes the job stream is associated to the selected
GJS5104W The plan cannot be generated because workstation class. Otherwise the request is ignored.
an alternative plan was selected for the
Operator response: Click OK to add the job stream to
current engine.
the workstation class, or click Cancel to cancel the
Explanation: If an alternative plan is selected for an action.
engine, neither a trial nor a forecast plan can be
generated.
GJS5108W The resource is being defined on a
System action: The requested action did not complete workstation class. Do you want to
successfully. continue?
Operator response: Restore the plan before generate a Explanation: You are defining this resource on a
new one. workstation class. You can choose to continue, or
change the workstation for this resource.

GJS5105W This instance of the job stream does not System action: If the answer to previous question is
fall within the scheduled time range. Do yes the resource is associated to the selected
you want to submit an instance of the workstation class. Otherwise the request is ignored.
job stream that falls within the
Operator response: Click OK to add the resource to
scheduled time range?
the workstation class, or click Cancel to cancel the
Explanation: The job stream instance that you selected action.
in the search panel has a valid time range that is
outside the scheduled time you set. You can choose to
GJS5109W You are renaming the Job Stream.
accept the suggested alternative, or change the
Do you want to proceed?
scheduled time range.
Explanation: The Job Stream will be renamed.
System action: If the answer to previous question is
yes a job stream instance that falls within the scheduled System action:
time range is submitted. Otherwise the request is
Operator response:
ignored.
Operator response: Click OK to submit the job stream
GJS5110W You are renaming the Job.
instance, or click Cancel to cancel the request and
Do you want to proceed?
change the scheduled time range.
Explanation: The Job will be renamed.
GJS5106W This instance of the job stream does not System action:
fall within the scheduled time range. Do
you want to load an instance of the job Operator response:
stream that falls within the scheduled
time range?
Explanation: The job stream instance that you selected
in the search panel has a valid time range that is
outside the scheduled time you set. You can choose to
accept the suggested alternative, or change the
scheduled time range.
System action: If the answer to previous question is
yes a job stream instance that falls within the scheduled
time range is loaded. Otherwise the request is ignored.
Operator response: Click OK to open the job stream
instance properties, or click Cancel to cancel the request
and change the scheduled time range.

Chapter 60. Job Scheduling Console messages 405

GJS6001E • GJS6011E

Job Scheduling Console starting and stopping messages

GJS6001E Error logging in to the TMR host. GJS6008E URL entered is empty. Please enter a
Please check the following: new URL.
On local workstation:
Explanation: No additional information is available
- password is spelled correctly
for this message.
- Caps Lock is on / off.
On TMR host:
- remote connections are enabled GJS6009E An error occurred while loading the
- login account is a TME® Administrator preferences. Restart the Job Scheduling
- login account has a valid group Console and import non corrupted
property on the TMR host. preferences files or load the default
values.
Explanation: Error logging in to the TMR host.
Explanation: The only change allowed to the
System action: The requested action did not complete
preferences.xml file is the addition of the time zone tag.
successfully.
Any other change, including comments, corrupts the
Operator response: Check if on local workstation the file.
password is spelled correctly and the Caps Lock is on /
System action: The requested action did not complete
off, and if on TMR host the remote connections are
successfully and the Job Scheduling Console is not
enabled, the login account is a TME Administrator and
started.
the login account has a valid group property.
Operator response: Make sure no changes were made
to the preferences files other than the addition of the
GJS6004E Fields are incorrectly specified. Re-enter
time zone tag.
the user name and password.
Explanation: No additional information is available
GJS6010I File VALUE_0
for this message.
already exist.
Do you want to replace it?
GJS6005E File VALUE_0 not found.
Explanation: The file that the user is saving already
Please enter a new file name.
exist.
Explanation: No additional information is available
System action: The system will overwrite the existing
for this message.
file if you choose the "OK" button. The system will
display the file browser window if you choose the
GJS6005W You specified an unrecognized time "Cancel" button.
zone. Job Scheduling Console will use
Operator response: Choose the option you require.
the workstation time zone where it is
installed.
GJS6011E The specified file VALUE_0 cannot be
Explanation: See message.
saved in the specified path VALUE_1.
System action: The Job Scheduling Console proceeds. Make sure that the file is not locked by
another application and that you have
Operator response: Set a recognized time zone value.
the correct permissions on the path or
file.
GJS6006E URL entered is in error. Please enter a
Explanation: The selected file might already be open
new URL.
or you do not have the permissions necessary to
Explanation: No additional information is available modify or to access it. Only on Unix Systems the
for this message. selected path might be a NFS path containig blanks.
System action: The new version of the file cannot be
GJS6007E Input/Output Error while attempting to saved.
get data from server.
Operator response: Make sure the file is not already
Explanation: No additional information is available open or in use by another application and that you
for this message. have the correct permissions.

406 IBM Tivoli Workload Scheduler Job Scheduling Console: User’s Guide
|

| Part 9. Administration

© Copyright IBM Corp. 1991, 2006 407

408 IBM Tivoli Workload Scheduler Job Scheduling Console: User’s Guide
|

| Chapter 61. Changing the TWSUser password for the z/OS

| connector
| When you installed the Job Scheduling Console you supplied a TWSUser and
| password. You also used this user ID and password to create engines. You might
| also use it to access the engines, unless, when you created the engine, you asked
| the Job Scheduling Console to remember the ID and password. This chapter
| describes how to change the password of the TWSUser, which you might be
| required to do to satisfy your enterprise's security policy.

| If you want to change the TWS_user, there are three or four macro steps to
| perform, depending on the type of operating system on which it is used.

| The steps required to change the password are as follows:

| v “Step 1: change the local operating system password”
| v “Step 2: change WebSphere Application Server user ID password”
| v “Step 3: change passwords used to connect to the engine” on page 411
| v “Step 4: change the Windows services password” on page 411
|
| Step 1: change the local operating system password
| The first step is to change this password, using the options of the operating
| system.

| If the user is an LDAP user, use your local mechanisms to change the LDAP user
| password.
|
| Step 2: change WebSphere Application Server user ID password
| Follow this procedure:
| 1. Log on to the computer where Tivoli Workload Scheduler is installed as the
| following user:
| UNIX root
| Windows Any user in the Administrators group.
| 2. Access the directory: TWS_home/wastools
| 3. Run the following script to stop the application server:
| UNIX stopWas.sh -user TWSUser -password TWSUser_password
| Windows stopWas.bat
| 4. From that same directory run the following script to create a file containing the
| current security properties:
| UNIX showSecurityProperties.sh > my_file_name
| Windows showSecurityProperties.bat > my_file_name
| The contents of the file should look something like this:
| WASX7357I: By request, this scripting client is not connected to any
| server process. Certain configuration and application operations will
| be available in local mode.
| ################################################################
| Global Security Panel

© Copyright IBM Corp. 1991, 2006 409

 Change WebSphere Application Server user ID password

| ################################################################
| enabled=true
| enforceJava2Security=false
| useDomainQualifiedUserNames=false
| cacheTimeout=600
| issuePermissionWarning=true
| activeProtocol=CSI
| activeAuthMechanism=SWAM
| activeUserRegistry=LocalOS
|
| ################################################################
| Local OS Registry
| ################################################################
| LocalOSServerID=twsuser
| LocalOSServerpassword=********
| LocalOSServerREALM=IBM-30B537EAD92
|
|
| ################################################################
| LDAP Panel
| ################################################################
| LDAPServerId=twsuser
| LDAPPassword=********
| LDAPServerType=IBM_DIRECTORY_SERVER
| LDAPHostName=
| LDAPPort=389
| LDAPBaseDN=
| LDAPBindDN=
| LDAPBindPassword=
| LDAPsearchTimeout=120
| LDAPreuseConnection=true
| LDAPIgnoreCase=true
| LDAPsslEnabled=false
| LDAPsslConfig=DefaultNode/DefaultSSLSettings
|
|
| ################################################################
| Advanced LDAP Panel
| ################################################################
| LDAPUserFilter=(&(uid=%v)(objectclass=ePerson))
| LDAPGroupFilter=(&(cn=%v)(|(objectclass=groupOfNames)
| (objectclass=groupOfUniqueNames)))
| LDAPUserIdMap=*:uid
| LDAPGroupIdMap=*:cn
| LDAPGroupMemberIdMap=ibm-allGroups:member;ibm-allGroups:uniqueMember
| LDAPCertificateFilter=
| LDAPCertificateMapMode=EXACT_DN
|
|
| ################################################################
| SSL Panel
| ################################################################
| alias=DefaultSSLSettings
| keyFileName=${USER_INSTALL_ROOT}/etc/TWSServerKeyFile.jks
| keyFilePassword=default
| keyFileFormat=JKS
| trustFileName=${USER_INSTALL_ROOT}/etc/TWSServerTrustFile.jks
| trustFilePassword=default
| trustFileFormat=JKS
| clientAuthentication=false
| securityLevel=HIGH
| enableCryptoHardwareSupport=false

| The fields you are interested in are highlighted.

410 IBM Tivoli Workload Scheduler Job Scheduling Console: User’s Guide
 Change WebSphere Application Server user ID password

| 5.

| Note: A template file of properties exists in this directory, but if you edit and
| use it in the command described below you overwrite the current
| settings with those in the template file, which are almost certainly
| incorrect.
| a. Edit my_file_name and delete the text of the WASX7357I message.
| b. Locate the LocalOSServerpassword and LDAPPassword entries. If you are not
| using LDAP authentication, you do not need to edit LDAPPassword, but you
| are advised to change both, regardless of the authentication method you are
| using.

| Note: If you want to know which authentication system you are using, check
| the entry activeUserRegistry.
| 6. Change the appropriate entry or entries to the actual password value and save
| the file.
| 7. Change the password by running the command:
| Windows changeSecurityProperties.bat my_file_name
| UNIX changeSecurityProperties.sh my_file_name
| Notes:
| a. This command might display a message from the application server
| (WASX7357I:). You can ignore this message.
| b. The passwords are encrypted before being saved in the WebSphere
| Application Server configuration files.
| 8. Delete the file my_file_name that you created (to leave it on the disk with
| unencrypted passwords in it is a security risk).
| 9. Run the following script to restart the application server:
| UNIX startWas.sh
| Windows startWas.bat
|
| Step 3: change passwords used to connect to the engine
| Change the password for every engine defined using the Job Scheduling Console
| on this computer, as follows:
| 1. Open the Job Scheduling Console.

| Note: The engine icon shows with the unavailable icon: .

| 2. For each engine in turn, do the following:
| a. Right-click the engine in the Work with Engines pane, and select Properties.
| (see Chapter 16, “Creating engines,” on page 95 for information about the
| fields on this panel).
| b. Type the new password in the Password field under the Connection Profile
| heading.
| c. Click OK. The engine icon changes to show that it is available.
|
| Step 4: change the Windows services password
| On Windows, the TWS_user account is used to start the following service that runs
| the z/OS Connector's application server:

Chapter 61. Changing the TWSUser password for the z/OS connector 411
 Change the Windows services password

| v IBM WebSphere Application Server V6 - TWSZCONNECTOR(TWS_user)

| The password must be updated in the properties of this service, or it is not able to
| start at next reboot. This is done as follows:
| 1. Stop the Job Scheduling Console if it is not already stopped.
| 2. Open the Services panel (on Windows XP, for example, select Start → Settings →
| Control panel → Administrative Tools → Services).
| 3. Right-click the service and select Stop, or select the service and then select
| Action → Stop.
| 4. Right-click the service and select Properties, or select the service and then
| select Action → Properties.
| 5. Click the Log On tab and enter and confirm the current password assigned to
| the indicated user ID.
| 6. Click OK.
| 7. Right-click the service and select Start, or select the service and then select
| Action → Start.
| The service starts.
| 8. Close the Services panel.

| Note: There is a script updateWasService.bat in the TWS_home/wastools directory,

| but it cannot be used to change the Windows services password.
|

412 IBM Tivoli Workload Scheduler Job Scheduling Console: User’s Guide
|

| Chapter 62. Managing z/OS engines using WebSphere

| Application Server tools
| This section describes how to manage z/OS engines using the WebSphere
| Application Server tools. These tools are located in the following directory:
| UNIX installation_directory/wastools
| Windows installation_directory\wastools

| Using the tools you can:

| v Create a z/OS connector instance using the createZosEngine tool. See “Create a
| z/OS connector instance.”
| v Display the properties of a z/OS connector instance using the displayZosEngine
| tool. See “Displaying the properties of a z/OS connector instance” on page 414.
| v Update the properties of a z/OS connector instance using the updateZosEngine
| tool. See “Updating the properties of a z/OS connector instance” on page 415.
| v List all the z/OS connector instances using the listZosEngine tool. See “Listing
| all the z/OS connector instances” on page 415.
| v Remove a z/OS connector instance using the removeZosEngine tool. See
| “Remove a z/OS connector instance” on page 416
|
| Create a z/OS connector instance
| This section describes how to create a z/OS connector instance using the
| createZosEngine tool. Follow this procedure if installing the z/OS connector you:
| v Did not supply the data to configure the z/OS connector by selecting the
| Configure a connection to a Tivoli Workload Scheduler for z/OS host .
| v Want to create another instance.

| To create a z/OS connector instance, perform the following steps:

| 1. Log on to the computer where Tivoli Workload Scheduler is installed as the
| following user:
| UNIX root
| Windows Any user in the Administrators group.
| 2. Access the wastools directory.
| 3. Run the following script to stop the application server:
| UNIX stopWas.sh -user TWSUser -password TWSUser_password
| Windows stopWas.bat

| Note: The user is the TWSUser you defined during the installation.
| 4. From this directory run the following script to create a file containing the
| current security properties:
| UNIX
| createZosEngine.sh -name engineName -hostName hostName
| -portNumber portNumber [-connectionTimeoutCleanup timeout]
| [-maxConnections number] [-connectionTimeout timeout]
| [-unusedTimeout timeout] [-reapTime timeout]
| [-scaffoldSwitch boolean]

© Copyright IBM Corp. 1991, 2006 413

 Create a z/OS connector instance

| Windows
| createZosEngine.bat -name engineName -hostName hostName
| -portNumber portNumber [-connectionTimeoutCleanup timeout]
| [-maxConnections number] [-connectionTimeout timeout]
| [-unusedTimeout timeout] [-reapTime timeout]
| [-scaffoldSwitch boolean]

| where:
| engineName
| Specify the name of the new instance.
| hostName
| Specify the TCP/IP address or host name of the remote z/OS system
| where the scheduler subsystem is installed.
| portNumber
| Specify the TCP/IP port number of the remote z/OS system.
| 5. Run the following script to restart the application server:
| UNIX startWas.sh
| Windows startWas.bat
|
| Displaying the properties of a z/OS connector instance
| This section describes how to display the properties of a z/OS connector instance
| using the displayZosEngine tool.

| To display a z/OS connector instance, perform the following steps:

| 1. Log on to the computer where Tivoli Workload Scheduler is installed as the
| following user:
| UNIX root
| Windows Any user in the Administrators group.
| 2. Access the wastools directory.
| 3. From this directory run the following command:
| UNIX
| displayZosEngine.sh engineName
| Windows
| displayZosEngine.bat engineName

| where:
| engineName
| Specify the name of the instance whose properties you want to display.
| The following is an example of the output you receive when you submit the
| displayZosEngine tool for the zosengine engine:
| name : zosengine
| hostName : 9.87.130.95
| portNumber : 20023
| connectionTimeoutCleanup : 60 minutes
| scaffoldSwitch : false
| maxConnections : 10
| connectionTimeout : 180 seconds
| unusedTimeout : 1800 seconds
| reapTime : 180 seconds

414 IBM Tivoli Workload Scheduler Job Scheduling Console: User’s Guide
 Display the properties of a z/OS connector instance

|
| Updating the properties of a z/OS connector instance
| This section describes how to update the properties of a z/OS connector instance
| using the displayZosEngine tool.

| To update a z/OS connector instance, perform the following steps:

| 1. Log on to the computer where Tivoli Workload Scheduler is installed as the
| following user:
| UNIX root
| Windows Any user in the Administrators group.
| 2. Access the wastools directory.
| 3. Run the following script to stop the application server:
| UNIX stopWas.sh -user TWSUser -password TWSUser_password
| Windows stopWas.bat

| Note: The user is the TWSUser you defined during the installation.
| 4. From this directory run the following command:
| UNIX
| updateZosEngine.sh -name engineName -hostName hostname
| -portNumber portNumber [-connectionTimeoutCleanup timeout]
| [-maxConnections number] [-connectionTimeout timeout]
| [-unusedTimeout timeout] [-reapTime timeout]
| [-scaffoldSwitch boolean]
| Windows
| updateZosEngine.bat -name engineName -hostName hostname
| -portNumber portNumber [-connectionTimeoutCleanup timeout]
| [-maxConnections number] [-connectionTimeout timeout]
| [-unusedTimeout timeout] [-reapTime timeout]
| [-scaffoldSwitch boolean]

| where:
| engineName
| Specify the name of the new instance.
| hostName
| Specify the TCP/IP address or host name of the remote z/OS system
| where the scheduler subsystem is installed.
| portNumber
| Specify the TCP/IP port number of the remote z/OS system.
| 5. Run the following script to restart the application server:
| UNIX startWas.sh
| Windows startWas.bat
|
| Listing all the z/OS connector instances
| This section describes how to list all the z/OS connector instances you defined
| using the listZosEngine tool.

| To list all the z/OS connector instances perform the following steps:
| 1. Log on to the computer where Tivoli Workload Scheduler is installed as the
| following user:

Chapter 62. Managing z/OS engines using WebSphere Application Server tools 415
 Listing all the z/OS connector instances

| UNIX root
| Windows Any user in the Administrators group.
| 2. Access the directory: wastools.
| 3. From this directory run the following command:
| UNIX
| listZosEngine.sh
| Windows
| listZosEngine.bat
|
| Remove a z/OS connector instance
| This section describes how to remove a z/OS connector instance using the
| removeZosEngine tool.

| To remove a z/OS connector instance perform the following steps:

| 1. Log on to the computer where Tivoli Workload Scheduler is installed as the
| following user:
| UNIX root
| Windows Any user in the Administrators group.
| 2. Access the wastools directory.
| 3. Run the following script to stop the application server:
| UNIX stopWas.sh -user TWSUser -password TWSUser_password
| Windows stopWas.bat

| Note: The user is the TWSUser, not necessarily the user that you used to log in
| with.
| 4. From this directory run the following command:
| UNIX
| removeZosEngine.sh engineName
| Windows
| removeZosEngine.bat engineName

| where:
| engineName
| Specify the name of the instance you want to remove.
| 5. Run the following script to restart the application server:
| UNIX startWas.sh
| Windows startWas.bat
|

416 IBM Tivoli Workload Scheduler Job Scheduling Console: User’s Guide
|

| Appendix A. Accessibility
| This appendix lists the accessibility features of the Job Scheduling Console. It is
| divided into the following sections:
| v “Navigating the interface using the keyboard”
| v “Magnifying what is displayed on the screen”
| v “General mnemonics” on page 418
| v “Main window mnemonics” on page 418
| v “Menu mnemonics” on page 419

| Accessibility features help users with physical disabilities, such as restricted

| mobility or limited vision, to use software products successfully. Depending on the
| operating system installed, the major accessibility features in this product enable
| users to do the following:
| v Use assistive technologies, such as screen-reader software and digital speech
| synthesizer, to hear what is displayed on the screen. Consult the product
| documentation of the assistive technology for details on using those technologies
| with this product.
| v Operate specific or equivalent features using only the keyboard.
| v Magnify what is displayed on the screen.

| In addition, the product documentation was modified to include features to aid

| accessibility:
| v All documentation is available in both HTML and convertible PDF formats to
| give the maximum opportunity for users to apply screen-reader software.
| v All images in the documentation are provided with alternative text so that users
| with vision impairments can understand the contents of the images.
|
| Navigating the interface using the keyboard
| Standard shortcut and accelerator keys are used by the product and are
| documented by the operating system. Refer to the documentation provided by
| your operating system for more information.
|
| Magnifying what is displayed on the screen
| You can enlarge information on the product windows using facilities provided by
| the operating systems on which the product is run. For example, in a Microsoft
| Windows environment, you can lower the resolution of the screen to enlarge the
| font sizes of the text on the screen. Refer to the documentation provided by your
| operating system for more information.

| To set a high contrast for your Job Scheduling Console you need to modify the
| NTConsole.bat file and add the following option:
| -Dswing.defaultlaf="com.sun.java.swing.plaf.windows.WindowsLookAndFeel"

| The NTConsole.bat file is located in the JSCHome/bin/java directory. When you are
| running in a UNIX type environment there is an operating system script where
| you can add the option, such as LINUXconsole.sh, or SUNconsole.sh.

© Copyright IBM Corp. 1991, 2006 417

 Accessibility

| To change the font sizes of the Job Scheduling Console interface objects, you add
| the fontSize key to the preferences.xml file. The preferences.xml file is located in
| user_home_directory/.twsconsole/.

| You can choose the font size from the following:

| Small The font is 2 points down on the default.
| Medium The font is the default font size.
| XLarge The font is 4 points up on the default.
| XXLarge The font is 6 points up on the default.
| XXXLarge The font is 8 points up on the default.

| The following is an example of the font size settings in preferences.xml file:

| <?xml version="1.0" encoding="UTF-8"?>
| <!DOCTYPE preferences SYSTEM "http://java.sun.com/dtd/preferences.dtd">
|
| <preferences EXTERNAL_XML_VERSION="1.0">
| <root type="user">
| <map>
| <entry key="portfolioHeight" value="602"/>
| <entry key="consoleHeight" value="746"/>
| <entry key="fontSize" value="XXXLarge"/>
| <entry key="infoAreaWidth" value="90"/>
| <entry key="infoAreaHeight" value="21"/>
| <entry key="consoleWidth" value="1032"/>
| <entry key="portfolioWidth" value="200"/>
| </map>
|
| General mnemonics
| The following general mnemonics are available:
| Ctrl+A Select all.
| Ctrl+shift+A Deselect all.
| Alt+F4 Close current window.
| Shift F10 Open the pop-menu on the selected item.
|
| Main window mnemonics
| The following mnemonics are included in the main window:
| Ctrl+T Show or hide the Actions list.
| Ctrl+E Show or hide the Work with engines pane.
| Atl+C Open the Console menu.
| Alt+S Open the Selected menu.
| Alt+E Open the Edit menu.
| Alt+V Open the View menu.
| Alt+W Open the Window menu.
| Alt+H Open the Help menu.
| Up and down arrows
| Navigate up and down in open menus.

418 IBM Tivoli Workload Scheduler Job Scheduling Console: User’s Guide
 Accessibility

| Right arrow Open submenus.

|
| Menu mnemonics
| The following mnemonics are available in the Console menu:
| Alt+D Detach the selected list.
| Alt+l Close the current task.
| Alt+x Exit.

| The following mnemonics are available in the Edit menu:

| Alt+U Undo the previous action.
| Alt+t Cut the selected object.
| Alt+C Copy the selected object.
| Alt+P Paste the previously cut or copied object.
| Alt+D Delete the selected object.

| The following mnemonics are available in the View menu:

| Alt+R Refresh.
| Alt+E Export the current table view.

| The following mnemonics are available in the Window menu:

| Alt+D Detach all tasks.
| Alt+A Attach all tasks.
| Alt+C Close all tasks.
| Alt+number To switch between open views, where number is the number
| automatically allocated to the view.

| The following mnemonics are available in the Help menu:

| Alt+O Open the task assistant.
| Alt+D Detach the task assistant.
| Alt+i Open the topic index.
| Alt+S Search for a topic.
| Alt+T Open the task assistant table of contents.
| Alt+B Open the About the Job Scheduling Console panel.

Appendix A. Accessibility 419

420 IBM Tivoli Workload Scheduler Job Scheduling Console: User’s Guide
|

| Appendix B. Starting the Job Scheduling Console from an

| external application
| This appendix describes how to start the Job Scheduling Console from an external
| application to display a list of jobs or job streams in the plan using the
| LIC_JSC_operating_system script.

| To start the Job Scheduling Console from an external application, perform the
| following steps:
| 1. From the installation_directory\configuration directory, edit the
| launchInContext.properties file to set the following options:
| launchInContext.enable=false
| Specifies to enable (true) or disable (false) the running of this script.
| false is the default value.
| launchInContext.waitingTime=10
| Specifies the number of seconds the script waits before attempting to
| open the Job Scheduling Console. 10 seconds is the default value.
| launchInContext.portNumber=39392
| Specifies the TCP/IP port number to use to start the Job Scheduling
| Console from an external application. Both the connection and the
| handshake protocol are protected. 39392 is the default value.
| 2. From the installation_directory\bin\java directory, run the following script
| to start the Job Scheduling Console:
| Windows
| LIC_JSC_WIN.bat ENGINE_NAME=engine_name OBJ_TYPE=object_type
| JS_NAME=job_stream_name JOB_NAME=job_name WKS_NAME=workstation_name
| TIME=input_arrival_time

| Note: Enclose all the option values within double quotes (″).
| AIX
| LIC_JSC_AIX.sh ENGINE_NAME=engine_name OBJ_TYPE=object_type
| JS_NAME=job_stream_name JOB_NAME=job_name WKS_NAME=workstation_name
| TIME=input_arrival_time
| HP-UX
| LIC_JSC_HP.sh ENGINE_NAME=engine_name OBJ_TYPE=object_type
| JS_NAME=job_stream_name JOB_NAME=job_name WKS_NAME=workstation_name
| TIME=input_arrival_time
| Linux
| LIC_JSC_LINUX.sh ENGINE_NAME=engine_name OBJ_TYPE=object_type
| JS_NAME=job_stream_name JOB_NAME=job_name WKS_NAME=workstation_name
| TIME=input_arrival_time
| Solaris
| LIC_JSC_SUN.sh ENGINE_NAME=engine_name OBJ_TYPE=object_type
| JS_NAME=job_stream_name JOB_NAME=job_name WKS_NAME=workstation_name
| TIME=input_arrival_time

| where:
| engine_name
| Specify the name of the engine on which you want to run the query.
| This is the name you specify in the Engine Name field of the Define a
| New Engine for the Job Scheduling Console panel. This parameter is
| required.

© Copyright IBM Corp. 1991, 2006 421

 Starting the Job Scheduling Console from an external application

| object_type
| Specify the type of object for which you are submitting the query.
| Possible values are job or jobstream. This parameter is required.
| job_stream_name
| Specify the name of the job stream for which you are submitting the
| query. You can use wildcards, see “Wildcards” on page 48. This
| parameter is required.
| job_name
| Specify the name of the job for which you are submitting the query.
| You can use wildcard, see “Wildcards” on page 48. This parameter is
| required if object_type is job. This parameter is ignored if object_type is
| jobstream.
| workstation_name
| Specify the name of the workstation where the job or job stream runs.
| You can use wildcards, see “Wildcards” on page 48.
| input_arrival_time
| Specify the time when a job or job stream is planned to be ready for
| processing in the format aaaa/mm/gg hh:mm. In a z/OS environment
| it is the input arrival time. In a distributed environment it is the
| scheduled time. When the query displays, this value is reported in the
| Start at column.
| The Job Scheduling Console displays the list of All scheduled jobs or All
| scheduled job streams that matches the selected criteria.

422 IBM Tivoli Workload Scheduler Job Scheduling Console: User’s Guide
Appendix C. Setting security
The Job Scheduling Console is installed with default SSL certificates called default.
Using OpenSSL it is possible to customize the SSL communication. This is
described in detail in Planning and Installation Guide.

© Copyright IBM Corp. 1991, 2006 423

424 IBM Tivoli Workload Scheduler Job Scheduling Console: User’s Guide
Appendix D. Status description and mapping
This appendix provides information about job and job stream status for the Job
Scheduling Console and Tivoli Workload Scheduler.

For information about job and job stream status for Tivoli Workload Scheduler for
z/OS, refer to Tivoli Workload Scheduler for z/OS Controlling and Monitoring the
Workload.

Status overview
There are two types of status:
Job Scheduling Console status
This is a subset of internal status and is common for both Tivoli Workload
Scheduler and Tivoli Workload Scheduler for z/OS.
Internal status
This refers to the Tivoli Workload Scheduler internal or engine status for the job
or job stream. The internal status messages are unique to the scheduler.

Job status
This section describes the job status for both Job Scheduling Console and Tivoli
Workload Scheduler internal status.

Job Scheduling Console job status

Table 10 lists Job Scheduling Console job states.
Table 10. Job Scheduling Console job states
This job status ... Means that ...
Waiting The job instance is waiting for its dependencies to be resolved.
Ready The dependencies of the job instance have been resolved and
the job instance is ready to run.
Running The job instance is running.
Successful The job instance completed successfully.
Error The job instance has stopped running with an error.
Cancelled The job instance was cancelled.
Held The job instance was put in hold.
Undecided The job status is currently being checked.
Blocked The job instance was blocked due to unfulfilled dependencies.

Tivoli Workload Scheduler internal job status

Table 11 lists internal job states.
Table 11. Tivoli Workload Scheduler internal job states
This job status ... Means that ...
ABEND The job terminated with a non zero exit code.

© Copyright IBM Corp. 1991, 2006 425

Job status

Table 11. Tivoli Workload Scheduler internal job states (continued)

This job status ... Means that ...
ABEND P An ABEND confirmation was received, but the job is not
completed.
ADD The job is being submitted.
CANCEL The job was cancelled.
CANCEL P The job instance is pending cancellation. Cancellation is
deferred until all of the dependencies, including an at time, are
resolved.
DONE The job completed in an unknown state.
ERROR For internetwork dependencies only, an error occurred while
checking for the remote status.
EXEC The job is running.
EXEC+ Transitory state when the job that is launched is managed by
the local batchman process.
EXTRN For internetwork dependencies only, the status is unknown. An
error occurred, a rerun action was just performed on the job in
the external job stream, or the remote job or job stream does
not exist.
FAILED Unable to launch the job.
FENCE The job’s priority is below the fence.
HOLD The job is awaiting dependency resolution.
INTRO The job is introduced for launching by the system.
INTRO+ Transitory state when the job that is introduced is managed by
the local batchman process.
PEND The job completed, and is awaiting confirmation.
READY The job is ready to launch, and all dependencies are resolved.
R JOB The job is running.
SCHED The job’s at time has not arrived.
SUCC The job completed with an exit code of zero.
SUCC P A SUCC confirmation was received, but the job is not
completed.
SUSP The job was blocked due to unfulfilled dependencies.
USER STAT The job was put in hold by the user.
WAIT The job is waiting to fulfill its dependencies.
WAITD The job is waiting to fulfill its dependencies.

426 IBM Tivoli Workload Scheduler Job Scheduling Console: User’s Guide
 Job stream status

Job stream status

This section describes the job stream status for both Job Scheduling Console and
Tivoli Workload Scheduler internal status.

Job Scheduling Console job stream status

Table 12 lists Job Scheduling Console job stream states.
Table 12. Job Scheduling Console job stream states
This job status ... Means that ...
Waiting The job stream instance is waiting for its dependencies to be
resolved.
Ready The dependencies of the job stream instance have been resolved
and the job stream instance is ready to run.
Running The job stream instance is running.
Successful The job stream instance completed successfully.
Error The job stream instance has stopped running with an error.
Cancelled The job stream instance was cancelled.
Held The job stream instance was interrupted.
Undecided The job stream status is currently being checked.
Blocked The job stream instance was blocked due to unfulfilled
dependencies.

Tivoli Workload Scheduler internal job stream status

Table 13 lists internal job stream states.
Table 13. Tivoli Workload Scheduler internal job stream states
This job status ... Means that ...
READY The dependencies for the job stream have been met but the
time restrictions for the job stream have not.
HOLD The job stream instance is awaiting dependency resolution.
EXEC The job stream instance is running.
STUCK Job stream instance was interrupted. No jobs are launched
without operator intervention.
ABEND The job stream instance terminated with a non zero exit code.
SUCC The job stream instance completed successfully.
CANCEL The job stream instance was cancelled.
CANCEL P The job stream instance is pending cancellation. Cancellation is
deferred until all of the dependencies, including an at time, are
resolved.
ADD The job stream instance was added with operator intervention.
EXTRN The job stream instance is in a remote Tivoli Workload
Scheduler network and its status is unknown. An error
occurred, a Rerun action was performed on the EXTERNAL job
stream, or the INET job or job stream does not exist.
Get Job Status Error This is for internetwork job streams and specifies that an error
occurred while checking for the remote status.

Appendix D. Status description and mapping 427

Status mapping

Status mapping
This section provides a table of how Job Scheduling Console status maps to Tivoli
Workload Scheduler internal status for jobs and job streams.

Job status mapping

Table 14 describes how Job Scheduling Console status correlates to Tivoli Workload
Scheduler internal status for jobs.
Table 14. Job status mapping
This console status ... Maps to this Tivoli Workload Scheduler internal status ...
Waiting ADD, PEND, WAIT, WAITD, INTRO, HOLD, INTRO+
Ready READY
Running EXEC, EXEC+, SUCC P, ABEND P, R JOB
Successful SUCC
Error ABEND, FAILED
Cancelled Status of the job when it was cancelled. Cancelled flag is
set.
Held Priority = 0, WAITING, READY, USER STAT
Undecided ERROR, EXTRN
Blocked SUSP

Job stream status mapping

Table 15 describes how Job Scheduling Console status correlates to Tivoli Workload
Scheduler internal status for job streams.
Table 15. Job stream status mapping
This console status ... Maps to this Tivoli Workload Scheduler internal status ...
Waiting ADD, PEND, WAIT, WAITD, INTRO, HOLD
Ready READY
Running EXEC
Successful SUCC
Error ABEND, FAIL
Cancelled CANCEL, HOLD, CANCEL P
Held HOLD
Undecided EXTRN, ERROR
Blocked STUCK

428 IBM Tivoli Workload Scheduler Job Scheduling Console: User’s Guide
Appendix E. Support information
If you have a problem with your IBM software, you want to resolve it quickly. This
section describes the following options for obtaining support for IBM software
products:
v “Using IBM Support Assistant”
v “Searching knowledge bases” on page 430
v “Obtaining fixes” on page 431
v “Receiving weekly support updates” on page 432
v “Contacting IBM Software Support” on page 433

Using IBM Support Assistant

The IBM Support Assistant is a free, stand-alone application that you can install on
any workstation. You can then enhance the application by installing
product-specific plug-in modules for the IBM products you use.

The IBM Support Assistant saves you time searching product, support, and
educational resources. The IBM Support Assistant helps you gather support
information when you need to open a problem management record (PMR), which
you can then use to track the problem.

The product-specific plug-in modules provide you with the following resources:
v Support links
v Education links
v Ability to submit problem management reports

The IBM Support Assistant Web site is at http://www.ibm.com/software/support/

isa/. Use this site for the following:
v Obtain general information about the IBM Support Assistant
v Download and install the IBM Support Assistant application. Full instructions
are provided.
v Determine if a plug-in is available for a specific product (or go direct to the
plug-ins page at http://www.ibm.com/software/support/isa/plugins.html)
To locate and download the plug-in for a product, use the IBM Support Assistant's
interface. Full instructions on how to use the application and plugin are provided
within the interface. For example, on version 3.0.1 of the IBM Support Assistant,
click Updater, click New products and tools, expand Tivoli, select the plug-in, and
click Install.

If you cannot find the solution to your problem in the IBM Support Assistant, see
“Searching knowledge bases” on page 430.

© Copyright IBM Corp. 1991, 2006 429

Searching knowledge bases

Searching knowledge bases

You can search the available knowledge bases to determine whether your problem
was already encountered and is already documented.

Searching the local information center

IBM provides extensive documentation that you can install on your local computer
or on an intranet server. You can use the search function of this information center
to query conceptual information, instructions for completing tasks, and reference
information.

The information center is included on the separate Publications CD available as

part of the product bundle. Insert the CD in a CD drive on a Windows computer,
and the information centre automatically opens.

Searching the Internet

If you cannot find an answer to your question in the information center, search the
Internet for the latest, most complete information that might help you resolve your
problem.

To search multiple Internet resources for your product, use the Web search topic in
your information center. In the navigation frame, click Troubleshooting and
support  Searching knowledge bases and select Web search. From this topic, you
can search a variety of resources, including the following:
v IBM technotes
v IBM downloads
v IBM Redbooks
v IBM developerWorks®
v Forums and newsgroups
v Google

Search the information center at the IBM support Web site

The IBM software support Web site has many publications available online, one or
more of which might provide the information you require:
1. Go to the IBM Software Support Web site (http://www.ibm.com/software/
support).
2. Click Tivoli under the Find product support heading.
3. Click the Products A - Z tab
4. Click W for Workload Scheduler and then locate the links for Tivoli Workload
Scheduler (you might need to scroll down to the product section for Tivoli
Workload Scheduler. Here there are links that open product-specific sites.
5. Click Support under the V8 heading. The Tivoli Workload Scheduler support
page is displayed.
6. Under the Self help heading and Learn subheading, choose from the list of
different types of product support publications:
v Product documentation and manuals
v White papers

430 IBM Tivoli Workload Scheduler Job Scheduling Console: User’s Guide
 Searching knowledge bases

v Redbooks
v IBM Tivoli software training
A search for the selected documentation type is performed, and the results
displayed.
7. Use the on-screen navigation to look through the displayed list for the
document you require, or use the options in the Refine your results section to
narrow the search criteria. You can add Additional search terms or select a
specific Document type. You can also change the sort order of the results (Sort
results by). Then click to start the search.

To access some of the publications you need to register (indicated by a key icon
beside the publication title). To register, select the publication you want to look at,
and when asked to sign in follow the links to register yourself. There is also a FAQ
available on the advantages of registering.

Obtaining fixes
A product fix might be available to resolve your problem. To determine what fixes
are available for your IBM software product, follow these steps:
1. Go to the IBM Software Support Web site (http://www.ibm.com/software/
support).
2. Click Tivoli under the Find product support heading.
3. Click Products A - Z.
4. Click W for Workload Scheduler and then locate the links for Tivoli Workload
Scheduler (you might need to scroll down to the product section for Tivoli
Workload Scheduler.
5. Click Support under the Tivoli Workload Scheduler V8 product heading. The
Tivoli Workload Scheduler support page is displayed.
6. Under the Self-help heading and Download, subheading, either choose one of
the displayed most-popular downloads, or click All downloads. A search for
the downloads is performed, and the results displayed.
7. Use the on-screen navigation to look through the displayed list for the
download you require, or use the options in the Refine your results section to
narrow the search criteria. You can add Additional search terms, or select a
specific Download type, Software version, and range of availability and
modification dates for fixes (Modified date), and then click to start the
search.
8. Click the name of a fix to read the description of the fix and to optionally
download the fix.

For more information about the types of fixes that are available, see the IBM
Software Support Handbook at http://techsupport.services.ibm.com/guides/
handbook.html.

Appendix E. Support information 431

Receiving support updates

Receiving weekly support updates

To receive weekly e-mail notifications about fixes and other software support news,
follow these steps:
1. Go to the IBM Software Support Web site at http://www.ibm.com/software/
support.
2. Click My support under the Personalized support heading in the upper-right
corner of the page.
3. If you have already registered for My support, sign in and skip to the next
step. If you have not registered, click register now. Complete the registration
form using your e-mail address as your IBM ID and click Submit.
4. Click Edit profile.
5. In the Products list, select Software. A second list is displayed.
6. In the second list, select a product segment, for example, Systems
Management. A third list is displayed.
7. In the third list, select a product sub-segment, for example, Job Scheduling. A
list of applicable products is displayed.
8. Select the products for which you want to receive updates, for example, IBM
Tivoli Workload Scheduler and IBM Tivoli Management Framework.
9. Click Add products.
10. After selecting all products that are of interest to you, click Subscribe to email
on the Edit profile page.
11. In the Documents list, select Software.
12. Select Please send these documents by weekly email from the list.
13. Update your e-mail address as needed.
14. Select the types of documents that you want to receive information about.
15. Click Update.

If you experience problems with the My support feature, you can obtain help in
one of the following ways:
Online
Send an e-mail message to [email protected], describing your problem.
By phone
Call 1-800-IBM-4You (1-800-426-4968).

432 IBM Tivoli Workload Scheduler Job Scheduling Console: User’s Guide
 Receiving support updates

Contacting IBM Software Support

IBM Software Support provides assistance with product defects.

Before contacting IBM Software Support, your company must have an active IBM
software maintenance contract, and you must be authorized to submit problems to
IBM. The type of software maintenance contract that you need depends on the
type of product you have:
v For IBM distributed software products (including, but not limited to, Tivoli,
Lotus®, and Rational® products, as well as DB2 and WebSphere products that
run on Windows, or UNIX operating systems), enroll in Passport Advantage® in
one of the following ways:
Online
Go to the Passport Advantage Web site at http://www.lotus.com/
services/passport.nsf/ WebDocs/Passport_Advantage_Home and click
How to Enroll.
By phone
For the phone number to call in your country, go to the IBM Software
Support Web site at http://techsupport.services.ibm.com/guides/
contacts.html and click the name of your geographic region.
v For customers with Subscription and Support (S & S) contracts, go to the
Software Service Request Web site at https://techsupport.services.ibm.com/ssr/
login.
v For customers with IBMLink™, CATIA, Linux, S/390®, iSeries™, pSeries®,
zSeries®, and other support agreements, go to the IBM Support Line Web site at
http://www.ibm.com/services/us/index.wss/so/its/a1000030/dt006.
v For IBM eServer™ software products (including, but not limited to, DB2 and
WebSphere products that run in zSeries, pSeries, and iSeries environments), you
can purchase a software maintenance agreement by working directly with an
IBM sales representative or an IBM Business Partner. For more information
about support for eServer software products, go to the IBM Technical Support
Advantage Web site at http://www.ibm.com/servers/eserver/techsupport.html.

If you are not sure what type of software maintenance contract you need, call
1-800-IBMSERV (1-800-426-7378) in the United States. From other countries, go to
the contacts page of the IBM Software Support Handbook on the Web at
http://techsupport.services.ibm.com/guides/contacts.html and click the name of
your geographic region for phone numbers of people who provide support for
your location.

To contact IBM Software support, follow these steps:

1. “Determining the business impact” on page 434
2. “Describing problems and gathering information” on page 434
3. “Submitting problems” on page 434

Appendix E. Support information 433

Receiving support updates

Determining the business impact

When you report a problem to IBM, you are asked to supply a severity level.
Therefore, you need to understand and assess the business impact of the problem
that you are reporting. Use the following criteria:
Severity 1
The problem has a critical business impact. You are unable to use the
program, resulting in a critical impact on operations. This condition
requires an immediate solution.
Severity 2
The problem has a significant business impact. The program is usable, but
it is severely limited.
Severity 3
The problem has some business impact. The program is usable, but less
significant features (not critical to operations) are unavailable.
Severity 4
The problem has minimal business impact. The problem causes little impact
on operations, or a reasonable circumvention to the problem was
implemented.

Describing problems and gathering information

When describing a problem to IBM, be as specific as possible. Include all relevant
background information so that IBM Software Support specialists can help you
solve the problem efficiently. To save time, know the answers to these questions:
v What software versions were you running when the problem occurred?
v Do you have logs, traces, and messages that are related to the problem
symptoms? IBM Software Support is likely to ask for this information.
v Can you re-create the problem? If so, what steps were performed to re-create the
problem?
v Did you make any changes to the system? For example, did you make changes
to the hardware, operating system, networking software, and so on.
v Are you currently using a workaround for the problem? If so, be prepared to
explain the workaround when you report the problem.

Submitting problems
You can submit your problem to IBM Software Support in one of two ways:
Online
Click Submit and track problems on the IBM Software Support site
athttp://www.ibm.com/software/support/probsub.html. Type your
information into the appropriate problem submission form.
By phone
For the phone number to call in your country, go to the contacts page of
the IBM Software Support Handbook at http://techsupport.services.ibm.com/
guides/contacts.html and click the name of your geographic region.

If the problem you submit is for a software defect or for missing or inaccurate
documentation, IBM Software Support creates an Authorized Program Analysis
Report (APAR). The APAR describes the problem in detail. Whenever possible,
IBM Software Support provides a workaround that you can implement until the
APAR is resolved and a fix is delivered. IBM publishes resolved APARs on the

434 IBM Tivoli Workload Scheduler Job Scheduling Console: User’s Guide
 Receiving support updates

Software Support Web site daily, so that other users who experience the same
problem can benefit from the same resolution.

Appendix E. Support information 435

436 IBM Tivoli Workload Scheduler Job Scheduling Console: User’s Guide
Notices
This information was developed for products and services offered in the U.S.A.
IBM may not offer the products, services, or features discussed in this document in
other countries. Consult your local IBM representative for information on the
products and services currently available in your area. Any reference to an IBM
product, program, or service is not intended to state or imply that only that IBM
product, program, or service may be used. Any functionally equivalent product,
program, or service that does not infringe any IBM intellectual property right may
be used instead. However, it is the user’s responsibility to evaluate and verify the
operation of any non-IBM product, program, or service.

This information was developed for products and services offered in the U.S.A.
IBM may not offer the products, services, or features discussed in this publication
in other countries. Consult your local IBM representative for information on the
products and services currently available in your area. Any reference to an IBM
product, program, or service is not intended to state or imply that only that IBM
product, program, or service may be used. Any functionally equivalent product,
program, or service that does not infringe any IBM intellectual property right may
be used instead. However, it is the user’s responsibility to evaluate and verify the
operation of any non-IBM product, program, or service.

IBM may have patents or pending patent applications covering subject matter
described in this publication. The furnishing of this publication does not give you
any license to these patents. You can send license inquiries, in writing, to:

IBM Director of Licensing

IBM Corporation
North Castle Drive
Armonk, NY 10504-1785 U.S.A.

For license inquiries regarding double-byte (DBCS) information, contact the IBM
Intellectual Property Department in your country or send inquiries, in writing, to:

IBM World Trade Asia Corporation

Licensing
2-31 Roppongi 3-chome, Minato-ku
Tokyo 106, Japan

The following paragraph does not apply to the United Kingdom or any other
country where such provisions are inconsistent with local law:

INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS

PUBLICATION ″AS IS″ WITHOUT WARRANTY OF ANY KIND, EITHER
EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
WARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS
FOR A PARTICULAR PURPOSE.

Some states do not allow disclaimer of express or implied warranties in certain

transactions, therefore, this statement might not apply to you.

This information could include technical inaccuracies or typographical errors.

Changes are periodically made to the information herein; these changes will be

© Copyright IBM Corp. 1991, 2006 437

Notices

incorporated in new editions of the publication. IBM may make improvements

and/or changes in the product(s) and/or the program(s) described in this
publication at any time without notice.

Any references in this information to non-IBM Web sites are provided for
convenience only and do not in any manner serve as an endorsement of those Web
sites. The materials at those Web sites are not part of the materials for this IBM
product and use of those Web sites is at your own risk.

IBM may use or distribute any of the information you supply in any way it
believes appropriate without incurring any obligation to you.

Licensees of this program who wish to have information about it for the purpose
of enabling: (i) the exchange of information between independently created
programs and other programs (including this one) and (ii) the mutual use of the
information which has been exchanged, should contact:

IBM Corporation
2Z4A/101
11400 Burnet Road
Austin, TX 78758 U.S.A.

Such information may be available, subject to appropriate terms and conditions,

including in some cases payment of a fee.

The licensed program described in this publication and all licensed material
available for it are provided by IBM under terms of the IBM Customer Agreement,
IBM International Program License Agreement or any equivalent agreement
between us.

Information concerning non-IBM products was obtained from the suppliers of

those products, their published announcements or other publicly available sources.
IBM has not tested those products and cannot confirm the accuracy of
performance, compatibility or any other claims related to non-IBM products.
Questions on the capabilities of non-IBM products should be addressed to the
suppliers of those products.

This information contains examples of data and reports used in daily business
operations. To illustrate them as completely as possible, the examples include the
names of individuals, companies, brands, and products. All of these names are
fictitious and any similarity to the names and addresses used by an actual business
enterprise is entirely coincidental.

Trademarks
AIX, AS/400,BookManager, DB2, developerWorks, eServer, Hiperbatch, IBM,
IBMLink, iSeries, LoadLeveler, Lotus, NetView, OS/400, Passport Advantage.
pSeries, RACF, Rational, Redbooks, S/390,Tivoli, the Tivoli logo, Tivoli Enterprise
Console, TME, VTAM, WebSphere, z/OS, and zSeries are trademarks or registered
trademarks of International Business Machines Corporation in the United States,
other countries, or both.

Linux is a trademark of Linus Torvalds in the United States, other countries. or

both.

Intel is a registered trademark of Intel Corporation.

438 IBM Tivoli Workload Scheduler Job Scheduling Console: User’s Guide
 Notices

Microsoft and Windows are registered trademarks of Microsoft Corporation in the

United States, other countries, or both.

UNIX is a registered trademark of The Open Group in the United States and other
countries.

Java and all Java-based trademarks and logos are trademarks or registered
trademarks of Sun Microsystems, Inc. in the United States and other countries.

Other company, product, and service names may be trademarks or service marks
of others.

Notices 439
440 IBM Tivoli Workload Scheduler Job Scheduling Console: User’s Guide
Glossary
A and updates it, resolving dependencies. It is the only
process that can update the Symphony file. See also:
access method. An executable file used by extended v "processes"
agents to connect to and control jobs on other operating v "production period"
systems (for example, z/OS) and applications (for v "symphony file"
example, Oracle Applications, PeopleSoft, and SAP
R/3). The access method is specified in the workstation backup domain manager. An agent in a distributed
definition for the extended agent. See also "extended Tivoli Workload Scheduler network that can assume the
agent". responsibilities of its domain manager. It is installed as
a full status, fault-tolerant agent. See also:
actual start time. The time that a Tivoli Workload
Scheduler job instance or job stream instance actually v "fault-tolerant agent"
starts. See also: v "full status"
v "earliest start time" v "domain manager"
v ″latest start time″
backup master domain manager. An agent in a
v "planned start time" distributed Tivoli Workload Scheduler network that can
v "scheduled time" assume the responsibilities of the master domain
manager. It is installed as a full status, fault-tolerant
ad hoc job. A job that is inserted into the current agent. See also:
production plan. These jobs are unique to the plan, and v "fault-tolerant agent"
are not saved in the database. See also:
v "full status"
v "database"
v "master domain manager"
v "plan"

ad hoc prompt dependency. A prompt dependency C

that is defined within the properties of a job or job
stream and is unique to that job or job stream. See also calendar. A list of scheduling dates. Calendars are
"prompt dependency". defined in the database and are mostly assigned to run
cycles. Calendars can be used either to identify the
agent. An installed component that enables jobs to be dates when job streams or jobs can be run (when used
run on a computer or a computer partition, provided with inclusive run cycles), or when they cannot be run
that the computer or computer partition is also defined (when used with exclusive run cycles). A calendar can
as a workstation in the Tivoli Workload Scheduler also be designated for use as a freedays calendar in a
database. Agents can be standard, fault-tolerant, job stream. See also:
extended, or network. Specially configured agents are
v "exclusive run cycle"
also used as backups for domain managers and the
master domain manager. See also: v "freedays calendar"
v "backup domain manager" v "inclusive run cycle"
v "backup master domain manager" carry forward. If a job stream is not completed before
v "fault-tolerant agent" the end of the current production period it can be
v "network agent" carried forward to the next and then to subsequent
periods, until the latest start time is reached or the job
v "standard agent"
completes. See also "latest start time".
v "extended agent"
command-line client. A component you use to run
audit. A process that logs modifications to the selected Tivoli Workload Scheduler master domain
database and plan. manager commands from any workstation where it is
installed. It communicates by TCP/IP with the
B command-line server, which is part of the master
domain manager. The command-line client does not
batchman. A production control process that interacts need to be installed on the master domain manager,
directly with a copy of the Symphony file distributed to and is a selectable option for installation on other
workstations at the beginning of the production period nodes in the network. For details of the supported

© Copyright IBM Corp. 1991, 2006 441

command-line server • engine

commands see the IBM Tivoli Workload Scheduler: distributed workstation. A workstation on which jobs
Planning and Installation Guide. See also "master domain and job streams are run using the distributed engine.
manager". See also:
v "engine"
command-line server. See "command line client".
v "workstation"
conman. A command-line program for monitoring and
managing the production environment. See also domain. A named group of workstations in a
"processes". distributed Tivoli Workload Scheduler network,
consisting of one or more agents and a domain
composer. A command-line program for managing the manager acting as the management hub. All domains
definitions of scheduling objects in the database. See have a parent domain except for the master domain.
also "database". See also:
v "domain manager"
connector. An installed component that provides the
interface between the Job Scheduling Console and the v ″master domain manager"
engine. See also:
domain manager. An installed component in a
v "engine" distributed Tivoli Workload Scheduler network that is
v "job scheduling console" the management hub in a domain. All communication
to and from the agents in the domain is routed through
CPU. See "workstation". the domain manager. See also "workstation"

cpu time. The processor time used by a job. See also duration. The elapsed time that a job is expected to
"duration". take to complete (estimated duration) and actually
takes (actual duration). See also:
D v "cpu time"
v "time restriction"
database. Contains definitions for scheduling objects
(such as jobs, job streams, resources, and workstations).
The database also contains data such as job and job E
stream statistics, user data, and the last time an object
was modified. See also "plan". earliest start time. The time before which a job or job
stream cannot start. The job or job stream can start after
deadline. The time by which a job or job stream is set the earliest start time provided that all other time
to complete. When a job or job stream passes the restrictions and dependencies are satisfied. It is set
deadline, notifications are sent to users and integrated using the at Job Scheduling Console option or in the
applications, but the job or job stream is not prevented command-line scheduling language using the at
from running if all time restrictions and dependencies keyword . See also:
are satisfied. Jobs or job streams that have not yet v ″actual start time″
started or that are still running after the deadline time v ″latest start time″
has expired are considered ″late″ in the plan. See also
"plan". v ″planned start time″
v "scheduled time"
dependency. A prerequisite that must be satisfied
before a job or job stream can start. See also: end-to-end network. A network obtained by
v "external dependency" connecting one or more Tivoli Workload Scheduler
fault-tolerant agents in a distributed network to a Tivoli
v "file dependency" Workload Scheduler for z/OS node in a z/OS network
v "follows dependency" using TCP/IP, to perform workload scheduling. In this
v "prompt dependency" configuration, the Tivoli Workload Scheduler for z/OS
node becomes the master domain manager of the
v "resource dependency"
fault-tolerant agents to schedule and manage jobs in
distributed network. A connected group of the distributed network. See also:
workstations that use the Tivoli Workload Scheduler v "engine"
distributed engine to perform workload scheduling. See v "workstation"
also:
v "engine" engine. The core software for the scheduling
environment. The engine can be either a z/OS engine
v "workstation"
(installed as part of the product "Tivoli Workload
Scheduler for z/OS") or a distributed engine (installed
as part of the product "Tivoli Workload Scheduler").

442 IBM Tivoli Workload Scheduler Job Scheduling Console: User’s Guide
 exclusive run cycle • iCalendar

exclusive run cycle. A run cycle that specifies the days v "plan"
and times that a job stream cannot be run. Exclusive
run cycles take precedence over inclusive run cycles. freedays calendar. A calendar assigned to a job stream
See also "run cycle″. to represent the non-working days when job streams
and jobs are not to be run. It can also be used to
explorer view. A graphical view in the Job Scheduling designate Saturdays or Sundays, or both, as workdays.
Console used to modify and maintain job streams in See also:
the database and the plan. See also: v ″calendar"
v "database" v ″holidays calendar"
v "plan"
FTA. See "fault-tolerant agent"
v "views"
full status. An attribute of an agent that enables it to
extended agent. An agent used to integrate Tivoli
be updated with the status of jobs and job streams
Workload Scheduler job control features with other
running on all other workstations in its domain and in
operating systems (for example, z/OS) and applications
subordinate domains, but not on peer or parent
(for example, Oracle Applications, PeopleSoft, and SAP
domains. A backup domain manager or master domain
R/3). Extended agents must be hosted by a master
manager must be full status. See also:
domain manager, domain manager, or an agent (not
another extended agent), and use access methods to v ″backup domain manager"
communicate with external systems. See also "access v ″domain"
method″. v ″master domain manager"
external dependency. A dependency defined in one
job or job stream that refers to another job stream or to G
a job in another job stream.
global options. Configuration options defined on the
external job. A job referred to in an external master domain manager using optman. These options
dependency. See also "external dependency″. apply to all workstations in the Tivoli Workload
Scheduler network. See also:
F v ″local options″
v ″optman″
fault-tolerant agent. A installed agent component in a
v ″user options″
distributed Tivoli Workload Scheduler network capable
of resolving local dependencies and launching its jobs graph view. A graphical view in the Job Scheduling
in the absence of a domain manager. Console used to modify and maintain job streams in
the database and the plan. See also:
fence. Regulates whether a job can be run on a
workstation. The job fence is a priority level that the v "database"
priority of a job must exceed before it can run. v "plan"
v "views"
file dependency. A dependency where a job or job
stream cannot start until it finds a specific file is
present in a specific path on a specific workstation. H
Sometimes called an opens file dependency. See also
"dependency". holidays calendar. The default freedays calendar for
all job streams. It is called "holidays". See also:
final job stream. The last job stream that is run in a
v ″calendar"
production period. It contains scripts that generate the
next production plan. See also: v ″freedays calendar"
v "production period″ host. A workstation required by extended agents. It
v "production plan″ can be any Tivoli Workload Scheduler workstation
except another extended agent.
follows dependency. A dependency where a job or
job stream cannot start until other jobs or job streams
have completed successfully. See also "dependency". I
forecast plan. A projection over a selected timeframe iCalendar. A standard (RFC 2445) for calendar data
based on the job streams and dependencies defined in exchange. Specific iCalendars can be supplied in place
the database. See also of Tivoli Workload Scheduler calendars to determine
v "database" the dates on which jobs or job streams should run. See
also "calendar".

Glossary 443
impact view • local options

impact view. A graphical view in the Job Scheduling times, priorities, and other dependencies that determine
Console used to modify and maintain job stream the exact order in which the jobs run.
instance dependencies in the plan. See also:
job stream instance. A job stream that is scheduled
v "plan"
for a specific run date in the plan. See also "job stream″.
v "views"
jobman. A job management process that controls the
inclusive run cycle. A run cycle that specifies the days launching of jobs under the direction of batchman and
and times that a job stream is scheduled to be run. reports job status back to mailman. The jobman
Exclusive run cycles take precedence over inclusive run process is responsible for tracking job states and for
cycles. See also "run cycle″. setting the environment as defined in jobmanrc and
.jobmanrc when requesting job launches. See also:
interactive jobs. A job that runs interactively on a
Windows desktop. v ″batchman"
v ″jobmon"
internal status. The current status of jobs and job
v ″mailman"
streams in the Tivoli Workload Scheduler engine. The
internal status is unique to Tivoli Workload Scheduler. jobmon. A job management and monitoring process in
See also "status″. the Windows version of Tivoli Workload Scheduler. A
separate jobmon process is spawned to launch and
internetwork dependencies. A dependency between
monitor each job. It reports job status back to jobman.
jobs or job streams in separate Tivoli Workload
See also:
Scheduler networks. See also "network agent″.
v ″jobman"
internetwork job or job stream. A job or job stream in v ″processes"
a remote Tivoli Workload Scheduler network that is
referenced by an internetwork dependency defined for JSC. See "job scheduling console".
a job or job stream in the local network. See also
"network agent″.
L
J latest start time. The time before which the job or job
stream must start. The job or job stream can start before
Jnextday. The previously used term for: ″JnextPlan″. the latest start time provided that all other
dependencies are satisfied. It is set in the command-line
Jnextplan. A job that creates or extends the production scheduling language using the until keyword. See also:
plan. See also ″production plan″.
v ″actual start time″
job. A unit of work that is processed at a workstation. v ″earliest start time″
The job definition consists of a unique job name in the v ″planned start time″
database along with other information necessary to run
v "scheduled time"
the job. See also "job definition".
limit. A means of allocating a specific number of job
job definition. A definition of a unit of work that
slots into which Tivoli Workload Scheduler is allowed
resides in the database of the distributed Tivoli
to launch jobs. A job limit can be set for each job
Workload Scheduler engine and can be added to a job
stream, and for each workstation. For example, setting
stream. Job definitions can be created before creating a
the workstation job limit to 25 permits Tivoli Workload
job stream, or can be created as part of the creation or
Scheduler to have no more than 25 jobs running
modification of a job stream. See also "“job stream”".
concurrently on the workstation.
job instance. A job scheduled for a specific run date
list. A means of filtering plan and database objects
in the plan. See also "job″.
and presenting them in a table.
job scheduling console. A Java graphical user
local options. Configuration options defined on each
interface used to create, modify, and maintain job
workstation in the localopts file. Each workstation in
scheduling objects, and to manage the production
the Tivoli Workload Scheduler network must have a
environment. See also "“views” on page 447".
localopts file. The settings in this file are changed
job limit. See "limit" using a text editor, and apply only to that workstation.
See also:
job status. See ″status″. v ″global options″
v ″user options″
job stream. A list of jobs that run as a unit (such as a
weekly backup application), along with run cycles,

444 IBM Tivoli Workload Scheduler Job Scheduling Console: User’s Guide
 logman • predefined prompt dependency

logman. A command that produces job statistics from

the previous production plan log file, and updates the
O
preproduction plan.
offset-based run cycle. A run cycle that uses a
combination of user-defined periods and offsets. For
M example, an offset of 3 in a period of 15 days is the
third day from the beginning of the period. It is more
makesec. A command-line utility that compiles the practical to use offset-based run cycles when the cycle
security file. See also "security file". is based on cyclic periods. This term is only used as
such in Tivoli Workload Scheduler for z/OS, but the
mailman. A mail management process. It routes concept applies also to the distributed product. See
messages to local and remote workstations. Additional also:
mailman processes named ServerIDs are created on v "rule-based run cycle"
domain managers to divide the load on mailman and
improve the efficiency of message handling. When the v "run cycle"
domain manager starts up, it creates a separate
opens file dependency. See ″file dependency″.
mailman process instance for each ServerID specified
in the workstation definitions of the agents it manages. optman. A command-line program that maintains the
Each workstation then contacts its own ServerID on global options in the product database.
the domain manager instead of contacting the main
mailman process. See also "processes".
P
master domain manager. An installed component that
performs the role of management hub of the top-level parameter. An entity that enables job instance-specific
domain in the Tivoli Workload Scheduler network. It values to be substituted in job and job stream scripts,
maintains the database of all scheduling objects in the either from values in the database or at run time.
domain and the central configuration files. The master Parameters cannot be used when scripting extended
domain manager generates the plan and creates and agent jobs.
distributes the Symphony file. In addition, logs and
reports for the network are maintained on the master plan. The means of scheduling jobs. Objects in the
domain manager. See also: database become instances in the plan. See also:
v ″backup master domain manager″ v "database"
v ″database″ v ″final job stream″
v ″domain″ v "forecast plan"
v ″plan″ v ″JnextPlan″
v "planman"
MDM. See ″master domain manager".
v "preproduction plan"
metronome. An application that takes a snapshot of v "production plan"
the Tivoli Workload Scheduler configuration and v "trial plan"
generates an HTML report. It is used in problem
determination to provide information to IBM Software planman. An application you use to create, extend,
Support. and reset plans of all types. See also "plan".

mozart. The previously used term for the "database". planned start time. The time that Tivoli Workload
Scheduler estimates a job instance will start. This
N estimate is based on start times of previous instances of
the job. See also:
netman. A network management process that is v ″actual start time″
started by the Startup script in UNIX, or as a service in v ″earliest start time″
Windows. Netman behaves like a network listener v ″latest start time″
program which receives conman start, stop, link or
unlink requests from the network. The netman process v "scheduled time"
examines each request received and either implements
predecessor. A job or job stream that must complete
the request itself or spawns a local Tivoli Workload
successfully before successor jobs or job streams can be
Scheduler process to do so. See also "processes".
started. See also "successor″.
network agent. A logical extended agent used to
predefined prompt dependency. A prompt
create dependencies between jobs and job streams on
dependency that is defined in the database and can be
separate Tivoli Workload Scheduler networks. See also
associated to any job or job stream. See also "prompt
"internetwork dependencies″.
dependency″.

Glossary 445
priority • Symphony file

priority. A way of determining the order in which Tivoli Workload Scheduler for z/OS, run cycles can
jobs and job streams start. Priorities for each job and also be based on periods that you define, such as a
job stream range from 0 to 101. A job or job stream semester. This term is only used as such in Tivoli
with a priority of 0 does not run. Workload Scheduler for z/OS, but the concept applies
also to the distributed product. See also:
preproduction plan. A high-level plan of system
v "offset-based run cycle"
activity containing job streams and dependencies. It is
created automatically when the production plan is v "run cycle"
created for the first time. It is extended if the
run cycle. Specifies the days that a job stream is
production plan is extended. It is similar to the
scheduled to run. See also:
long-term plan used in Tivoli Workload Scheduler for
z/OS. See also "plan". v "calendar"
v "exclusive run cycle"
production period. The timeframe covered by the
v "iCalendar"
production plan. See also "production plan".
v "inclusive run cycle"
production plan. Contains all job scheduling activity v "rule-based run cycle"
planned for a period. The plan is created or extended
v "simple run cycle"
by the Jnextplan job or by planman. It is stored in the
Symphony file, and consists of all the jobs, job streams, v "weekly run cycle"
and dependency objects that are scheduled to run for
that period, including any jobs or job streams carried
forward from the previous plan. See also:
S
v "carry forward" schedule. See ″job stream″.
v "JnextPlan"
scheduled time. The time when a job or job stream is
v "plan" scheduled to run. See also:
processes. Network processes that control the v ″actual start time″
production environment and network traffic. See also: v ″earliest start time″
v "batchman" v ″latest start time″
v "jobman" v "planned start time"
v "jobmon"
security file. The file where access rights of users to
v "mailman" objects in the database are defined. It is created by
v "netman" makesec. See also "makesec".
v "writer"
simple run cycle. A specific set of user-defined days a
prompt dependency. A dependency where an job stream is run. A simple run cycle is defined for a
operator must respond affirmatively to a prompt so specific job stream and cannot be used by other job
that the dependent job or job stream can run. See also: streams. See also "run cycle″.
v "ad hoc prompt dependency" standard agent. An installed agent component in a
v "predefined prompt dependency" distributed Tivoli Workload Scheduler network that
runs jobs, but requires a domain manager to resolve
R local dependencies and launch the jobs.

status. The current job or job stream status within the

resource. Either physical or logical system resources. Job Scheduling Console. The Job Scheduling Console
Resources are used as dependencies for jobs and job status is common to Tivoli Workload Scheduler and
streams. See also "resource dependency″. Tivoli Workload Scheduler for z/OS. See also "internal
status″.
resource dependency. A dependency where a job or
job stream cannot start until the required quantity of successor. A job that cannot start until all of the
the defined resource is available. See also "resource″. predecessor jobs or job streams on which it is
dependent are completed successfully. See also:
rule-based run cycle. A run cycle that uses rules
"predecessor″.
based on lists of ordinal numbers, types of days, and
common calendar intervals (or period names in Tivoli Symphony file. A file containing the scheduling
Workload Scheduler for z/OS). For example, the last information needed by the production control process
Thursday of every month. Rule-based run cycles are (batchman) to run the plan. The file is built and loaded
based on conventional periods, such as calendar when the production plan is created or extended on the
months, weeks of the year, and days of the week. In

446 IBM Tivoli Workload Scheduler Job Scheduling Console: User’s Guide
 table view • z/OS network

master domain manager. During the production phase,

it is continually updated to indicate the current status
V
of production processing: work completed, work in
views. Elements of the graphical user interface of the
progress, and work to be done. To manage production
Job Scheduling Console used for viewing and
processing, the contents of the Symphony file (plan) can
modifying scheduling objects. See also:
be displayed and altered using conman or the Job
Scheduling Console. See also: v "explorer view"
v ″batchman" v "graph view"
v ″conman" v "impact view"
v "job scheduling console" v "table view"
v "plan" v "timeline view"

T W
table view. A graphical view in the Job Scheduling weekly run cycle. A run cycle that specifies the days
Console used to display database and plan object data of the week that a job stream is run. For example, a job
in tabular format. See also: stream can be specified to run every Monday,
Wednesday, and Friday using a weekly run cycle. A
v "database"
weekly run cycle is defined for a specific job stream
v "job scheduling console" and cannot be used by multiple job streams. See also
v "plan" "run cycle″.
v "views"
workstation. A definition of an individual computer
timeline view. A graphical view in the Job Scheduling or computer partition on which jobs and job streams
Console used to modify and maintain job stream are run. Types of workstation vary depending on the
instance time restrictions. See also: type of engine. See also:
v "job scheduling console" v "distributed workstation"
v "time restriction" v ″z/OS workstation"
v "views" workstation class. A workstation class is a group of
workstations with similar job-scheduling characteristics.
time restriction. Determines the times before which, Any number of workstations can be placed in a class.
after which, or both, that a job or job stream cannot be Job streams and jobs can be assigned to run on a
run. Specifying both defines a time frame within which workstation class. This makes replication of a job or job
a job or job stream runs. Jobs can also have a repetition stream across many workstations easy. See also
rate. For example, Tivoli Workload Scheduler can "workstation"
launch the same job every 30 minutes between the
hours of 8:30 a.m. and 1:30 p.m. writer. A process started by netman. The writer
process passes incoming messages to the local mailman
trial plan. A projection of the current production plan process. The writer processes (there may be more than
for a different period, using the same start date. It is one on a domain manager workstation) are started by
used to determine the effect of different plan decisions. link requests and are stopped by unlink requests or
See also "plan". when the communicating mailman process ends. See
also "processes".
U
user options. Configuration options defined for each
X
user on a workstation, in a useropts file for each user x-agent. See ″extended agent″.
on a workstation. The settings in this file apply only to
that user on that workstation. See also:
v ″local options″ Z
v ″global options″ z/OS network. A connected group of workstations
that use the Tivoli Workload Scheduler z/OS engine to
utility commands. A set of utilities invoked from the
perform workload scheduling. See also:
operating system's command line for managing Tivoli
Workload Scheduler. v "engine"
v "workstation"

Glossary 447
z/OS workstation

z/OS workstation. A representation of system

configuration elements in the Tivoli Workload
Scheduler for z/OS network. For the z/OS engine,
workstations can be:
v Computer
v General
v Printer
See also "workstation".

448 IBM Tivoli Workload Scheduler Job Scheduling Console: User’s Guide
Index
Numerics changing the job limit
workstation 328
creating (continued)
workstation class 125
5601-453, program number xxvi changing the limit z/OS job stream 133
5601-454, program number xxvi job stream instance 275 z/OS resource 107
5765-086, program number xxvi command and task mapping z/OS workstation 98
quick start 42 creating z/OS connector instance
commands using WebSphere Application Server
A ps 12 tool 413
accessibility 417 setup.exe 11 customer support
font sizes wrmvsp 24 See Software Support
medium 418 common object
small 418 engine 191
XLarge 418 job stream 133
components
D
XXLarge 418 daily run cycle 233
XXXLarge 418 installing 15
data lookaside facility 108
Actions list pane 55 uninstalling 23
database
ad hoc job uninstalling language packs 23
definitions 31
submitting into a default job connection
dead zone
stream 307 Job Scheduling Console 6
time zone 33
submitting into a specific job TCP/IP for Job Scheduling
defining
stream 299 Console 9
calendar 120
ad hoc prompts connector instance z/OS creating
domain 123
definitions 31 using WebSphere Application Server
definition
adding tool 413
dependency 32
jobs and dependencies 214 connector instance z/OS displaying
distributed dependencies 33
language packs using silent mode 21 properties using WebSphere
external job dependency 33
adding external dependencies Application Server tool 414
external job stream dependencies 33
distributed job stream 219 connector instance z/OS listing
internetwork dependency 33
alternate plan properties using WebSphere
job definitions 29
setting 345 Application Server tool 415
job stream 28
automatic recovery connector instance z/OS removing
resource 28
z/OS job instance in plan 294 properties using WebSphere
run cycle 34
Application Server tool 416
special resource 28
connector instance z/OS updating
time restrictions 32
B properties using WebSphere
Application Server tool 415
workstation classes 29
backup domain manager, z/OS dependency 32
conventions, typeface xxvii
requirements 342 z/OS workstation 27
Create Another
BookManager xxvi definition tasks
using for creating objects 157
books Job Scheduling Console 37
creating
online xix quick start 37
calendar 119
ordering xix definitions
dependencies between job
ad hoc prompts 31
streams 200
calendars 30
dependencies between jobs 199
C dependencies within a job
database 31
distributed workstations 28
calendar stream 199
domains 29
creating 119 distributed job stream 147
file dependencies 31
defining 120 distributed resource 111
holidays calendar 30
list distributed workstation 103
lists 31
distributed 170 engine 95
monthend calendar 30
calendar run cycle 233 forecast and trial plans 155
parameters 31
calendar types job definition 127
paydays calendar 30
freedays 30 job stream 133
plan 31
holidays 30 objects using Create Another 157
predefined prompt 31
paydays 30 offset-based run cycle 209
prompts 31
CDs parameter 115
Windows users 30
installation 9 predefined prompt 117
deleting
changing resource 107
a job or external job 214
Windows user passwords 343 rule-based run cycle 202
jobs and dependencies 214
changing number of resource units 336 Windows user 113
run cycle 236
changing the job fence, workstation 329 workstation 97

© Copyright IBM Corp. 1991, 2006 449

deleting for distributed distributed ad hoc job properties distributed job definition properties
all job instance 316 (continued) (continued)
job instance 316 task (continued) task type
deleting for z/OS is interactive 302 extended agent workstation 128
job instance 288 return code mapping other task 128
job instance all 288 expression 302 UNIX script 128
deleting objects script 301 Windows script 128
Job Scheduling Console 49 time restrictions distributed job definition time restrictions
dependencies distributed action 302 at 224
definition 33 latest start time 302 delay for days 224
dependency repeat range 302 specify time 224
definition 32 start 302 distributed job definitions
dependency z/OS termination deadline 302 adding to a job stream 222
definition 32 distributed calendar properties distributed job definitions in job streams
description define calendar 119 general
Job Scheduling Console objects 27 description 119 description 223
directory names, notation xxviii name 119 edit 223
disability 417 distributed calendar run cycle job definition 223
displaying z/OS connector instance properties monitored job 223
properties, using WebSphere calendar 233 name 223
Application Server tool 414 offset 233 new 223
distributed ad hoc job distributed domain properties priority 223
submitting into a default job description 123 requires confirmation 223
stream 307 domain manager 123 workstation name 223
submitting into a specific job domain name 123 time restrictions
stream 299 is master 124 action 224
distributed ad hoc job properties parent domain 123 latest start time 224
files distributed engine normal elapsed time 224
filename 305 managing 193 repeat range 224
internal status 305 specific objects 29 start 223
qualifiers 305 distributed forecast plan properties termination deadline 224
release status 305 duration 155 time zone 223
workstation 305 file name 155 distributed job definitions in the database
general plan type 155 job details
alias 300 start time 155 aborted runs 241
job stream 300 Switch to the generated plan 156 CPU time 242
login 300 distributed job description 241
monitored job 301 submit into plan elapsed time 242
priority 300 alias 298, 299 logon 241
recovery options 301 into job stream 298 normal elapsed time 242
requires confirmation 301 into workstation 298, 299 recovery options 241
scheduled time 300 job stream 299 run date 242
task type 300 name 298, 299 script file 241
workstation 300 workstation 298, 299 successful runs 241
predecessor dependencies submitting into a default job total CPU time 241
internal status 306 stream 297 total elapsed time 241
job 306 submitting into a specific job total runs 241
job stream 306 stream 299 recovery options
release status 306 distributed job definition properties continue 241
scheduled time 306 general job 241
workstation 306 continue 128 prompt 241
recovery options description 128 rerun 241
continue 301 job 129 stop 241
job name 301 login 128 distributed job instance
message 301 message 128 priority types
rerun 301 name 128 go 308
stop 301 rerun 128 high 308
workstation name 301 stop 128 hold 308
resource dependencies task type 128 distributed job instance dependencies
available 303 workstation name 128, 129 internetwork predecessors
quantity 303 task dependency 306, 315
release status 303 add parameter 130 internal status 307, 315
resource 303 command 130 network agent 306, 315
workstation 303 is interactive 130 release status 306, 315
task return code mapping predecessors
add parameter 302 expression 130 internal status 315
command 301 script 130 job 314

450 IBM Tivoli Workload Scheduler Job Scheduling Console: User’s Guide
distributed job instance dependencies distributed job stream in the database distributed job stream instances in the
(continued) (continued) plan (continued)
predecessors (continued) run cycle properties (continued) resources
job stream 314 ending 232 available 267
release status 314 exclusive 233 quantity 267
distributed job instance in the plan inclusive 233 release status 267
prompts latest start time 235 resource 267
internal status 312 name 232 workstation 267
message text 312 rule for freedays 232 submit
number 312 specify time 234 alias 264
release status 312 start 234 job stream 264
distributed job instance properties starting 232 properties 264
files termination deadline 235 scheduled time 264
filename 313 time zone 234 workstation name 264
general type 233 submit predecessors
duration 309 distributed job stream instance internal status 270
information 308 priority types job 270
internal status 309 go 265 job stream instance 270
is interactive 308 high 265 release status 270
job number 308 hold 265 scheduled time 270
job stream name 308 distributed job stream instances in the workstation 270
job stream workstation 308 plan successors
job workstation 308 files internal status 274
login 308 filename 268 job 273, 274
monitored job 308 internal status 268 job stream name 273
name 308 qualifiers 268 scheduled time 274
priority 308 release status 268 status 274
recovery options 309 workstation 268 time restrictions
requires confirmation 308 general action 266
rerun options 308 carry forward 265 latest start time 266
scheduled time 308 est. duration 266 start 266
start time 309 information 265 termination deadline 267
status 308 internal status 266 time zone 267
resources limit 265 distributed job stream properties
available 311 monitored job stream 265 dependency resolution
quantity 311 name 265 absolute interval selection 150
release status 311 number of executing jobs 266 closest preceding 150
resource 311 number of failed jobs 266 relative interval selection 150
workstation 311 number of jobs 266 same day 150
task number of jobs abended 266 within a relative interval 150
command 309 number of jobs not run 266 within an absolute interval 150
expression 310 number of successful jobs 266 general
return code 310 original name 265 calendar name 149
task type 309 priority 265 carry forward 149
time restrictions runtime 266 description 148
action 310 start time 266 is draft 149
latest start time 310 status 266 limit 149
repeat range 310 workstation class name 265 monitored job stream 149
start 310 workstation name 265 name 148
termination deadline 310 internetwork predecessors priority 148
distributed job instance recovery options dependency 271, 273 Saturday is free day 149
continue 309 internal status 271, 273 specify calendar 149
job name 309 network agent 271, 273 Sunday is free day 149
message 309 release status 271, 273 time zone 148
rerun 309 predecessors use default calendar 149
stop 309 internal status 272 valid from 148
workstation name 309 job 272 valid to 148
distributed job instance status job stream 272 workstation name 148
ABEND 320 released status 272 go priority 149
SUCC 320 scheduled time 272 high priority 149
distributed job stream workstation 272 hold priority 148
adding external dependencies 219 prompts time restrictions
creating 147 internal status 269, 304 action 151
distributed job stream in the database message text 269, 304 latest start time 150
run cycle properties number 269, 304 start 150
action 235 release status 269, 304 termination deadline 151
description 232 time dependent 150

Index 451
distributed job stream properties distributed trial plan properties engine properties (continued)
(continued) (continued) domain 195
time restrictions (continued) file name 155 enabled 195
time zone 150 plan type 155 engine name 95, 193
distributed job stream run cycles Switch to the generated plan 156 engine type 95, 193, 194
calendar 35 distributed Windows user properties host name 96, 194
simple 35 password 113 master domain 195
weekly 35 user name 113 master workstation 195
distributed job stream time restrictions Windows domain 113 name 194
delay for days 150 Windows workstation 113 password 194
specify time 150 distributed Windows users plan 195
distributed job streams password confirmation 113 port number 96, 194
add dependency on internetwork distributed workstation class properties remote server name 96
icon 148 description 125 run number 195
dependency on external job icon 148 ignore 125 save password 194
dependency on external job stream name 125 schedule date 195
icon 148 distributed workstation properties type 194
job definition icon 147 access method 106 BKM 194
link icon 148 auto link 105 FTA 194
multiple job definition icon 148 behind firewall 105 MDM 194
time restrictions description 104 SA 194
time dependent 224 domain name 104 user name 194
distributed job streams time restrictions full status 104 version 194
at 150 host 106 engines z/OS managing
distributed object ignore 104 with WebSphere Application Server
calendar 119, 120 node 105 tools. 413
domain 123 operating system 104 environment variables, notation xxviii
job definition 127 server 105 exclusive run cycle
parameter 115 SSL communication 105 example 207, 208
prompt 117 SSL port 105 Explorer View 56
resource 111 TCP port 105 external application
Windows user 113 time zone 104 starting Job Scheduling Console
workstation 103 use master 104 from 421
workstation class 125 workstation name 104 external dependencies
distributed objects workstation type 104 deleting 235
calendars distributed workstation types external job
freedays 30 domain manager 104 adding to a job stream 220, 229
holidays 30 extended agent 104 deleting from job stream 214
job definitions 241 fault-tolerant agent 104 external job dependency
parameter 115 standard agent 104 definition 33
parameters 253 distributed workstations external job stream
prompts 117, 251 definitions 28 adding to a job stream 220
distributed parameter properties domain external job stream dependencies
name 115 defining 123 definition 33
value 115 distributed quick reference 73
distributed predefined prompt properties linking workstations 341
name 117
text 117
list
distributed 169
F
file dependencies
distributed quick reference starting the workstations 341
definitions 31
domain 73 stopping workstations 341
file dependency
workstation 73 switching domain managers 342
status 337
distributed resource unlinking workstations 342
files
creating 111
localopts 105
distributed resource properties
preferences.xml 34
description 111
name 111
E RESPONSE_FILE 11
education xxvii, 429 tws4zosconn.log 91, 353
quantity 111
end-to-end twsconsole_ismp.log 91, 353
workstation name 111
hierarchy 6 TWSJSC^8.3.log 91, 353
distributed run cycle properties
engine filter criteria
at 235
creating 95 distributed job stream instance in plan
delay for days 235
engine login dependency data
distributed simple run cycle
password 47 file name 174
properties
save password 47 job 174
month 233
user name 47 job stream 174
year 233
engine properties prompt number 174
distributed trial plan properties
batchman status 195 resource name 174
duration 155
database 195 workstation name 174

452 IBM Tivoli Workload Scheduler Job Scheduling Console: User’s Guide
finding objects installation method job instance
Job Scheduling Console 48 Job Scheduling Console 10 common list 183
fix packs installation program confirm 320
obtaining 431 z/OS connector 15 holding 289, 317
fixes installing killing fault-tolerant agent, z/OS 291
See fix packs components 15 killing, distributed 320
forecast and trial plans Job Scheduling Console 9 rerun 319
creating 155 language packs 21 job instance all
freedays calendar language packs using silent mode 21 deleting for z/OS 288
definition 30 language packs using the installation holding 289
rules 36 wizard 21 job instance for distributed
fresh install 11 installing Job Scheduling Console deleting 316
using ISMP wizard 10 deleting all 316
using Software Distribution 10 job instance for z/OS
G interactive mode
installation 11
deleting 288
job instance z/OS
graph view
internal job states restoring to operational
distributed, adding external
abend 425, 426 (UN-NOP) 291
dependencies 219
abend p 426 setting to non operational (NOP) 291
Graph View
add 426 job limit, changing for a
modifying a job 214
cancel 426 workstation 328
group of lists
cancel p 426 Job Scheduling Console
creating 181
done 426 connection 6
error 426 definition tasks 37
exec 426 deleting objects 49
H exec+ 426 find 48
hierarchy extrn 426 installation methods 10
end-to-end 6 failed 426 installing 9
multi– 4 fence 426 installing using ISMP wizard 10
Hiperbatch 108 hold 426 installing using Software
holding intro 426 Distribution 10
job instance 289 intro+ 426 management tasks 37
job instance all 289 pend 426 planning 9
holding a job stream instance 274 r job 426 pop-up menus 49
holidays calendar 30 ready 426 required data 49
sched 426 response file 11
succ 426 silent installation 11
I succ p 426
susp 426
standard buttons 48
standard functionality 48
IBM Redbooks 429
user stat 426 starting 45
IBM support assistant 429
waitd 426 starting from an external
Impact View 57
Internet, searching for problem application 421
importing
resolution 430 task flow 37
user preferences for Job Scheduling
internetwork dependency task guide 37
Console 17
adding to a job 228 task type 37
importing from versions 8.3
adding to a job stream 220 TCP/IP connection for 9
user preferences for Job Scheduling
definition 33 unattended installation 11
Console 18
ISMP wizard uninstalling 23
importing from versions prior to 8.3
installing Job Scheduling Console 10 uninstalling with wrmvsp 24
user preferences for Job Scheduling
unsupported characters 48
Console 17
user preferences 17
Inclusive or exclusive
run cycle 36 J user preferences from versions 8.3 18
user preferences from versions prior
information centers job
to 8.3 17
at IBM support Web site, searching for deleting from job stream 214
wildcards 48
problem resolution 430 list
Job Scheduling Console languages
local, searching for problem distributed 167
adding language packs 21
resolution 430 modifying using Graph View 214
installing 21
installation submitting into a default job
repairing 356
CDs 9 stream 297
Job Scheduling Console objects
fresh install 11 submitting into a specific job
description 27
Java Virtual Machine (JVM) 13 stream 299
Job Scheduling Console to an engine
number of instances 9 job ad hoc
logging 46
operating system variables 12 submitting into a default job
job states
silent 11 stream 307
blocked 425
Software Distribution 12 job definition
cancelled 425
software package blocks 12 creating 127
error 425
using ISMP wizard 10 job fence, changing 329

Index 453
job states (continued)
held 425
L list filter criteria (continued)
distributed Windows users in
ready 425 language packs database
running 425 adding 21 domain name 169
successful 425 installing 21 user name 169
undecided 425 installing using silent mode 21 workstation 169
waiting 425 installing using the installation distributed workstation classes in
job stream wizard 21 database
creating 133 uninstalling 23 workstation class name 168
creating dependencies between 200 library xix distributed workstation in database
creating dependencies within 199 linking a workstation 329 domain name 166
definition 28 linking workstations, domain 341 host workstation name 166
deleting run cycle 236 list filter criteria workstation name 166
list distributed calendars in database workstation type 166
distributed 163 apply defaults 170 distributed workstations in plan
z/OS 163 distributed domain states in plan domain name 178
job stream distributed domain name 180 z/OS job instance in plan
adding external dependencies 219 distributed domains in database authority group 175
creating 147 domain name 170 cleanup status 175
Job Stream Editor 58 parent domain 170 cleanup type 175
job stream instance distributed files in plan contains monitored job 175
common list 183 filename 179 critical job 176
holding 274 workstation name 179 dates 175
limit 275 distributed job definition in database extended task name 175
list job name 167 internal status 175
distributed 173 workstation name 167 job identifier 175
z/OS 171 distributed job instance in plan job stream 175
job stream internal states actual start time range 177 owner 175
abend 427 always show rerun instances 177 priority 175
add 427 finish time range 178 restart options 175
cancel 427 internal status 177 running on wait workstation 176
cancel p 427 job stream name 177 status 175
exec 427 job/job stream dependency 178 task name 175
extrn 427 latest start time range 177 waiting for scheduling
get job status error 427 login 177 environment 176
hold 427 name 177 WLM policy 176
ready 427 priority 177 workstation 175
stuck 427 prompt dependency 178 z/OS job stream in database
succ 427 recovery options 177 authority group 164
job stream states resource dependency 178 calendar 164
blocked 427 status 177 contains monitored job 164
cancelled 427 workstation 177 dates 164
error 427 distributed job stream in database exclude template 164
held 427 job stream name 164 extended task name 164
ready 427 job stream status 165 is a template 164
running 427 validity range 165 job stream 164
successful 427 workstation name 164 job stream template 164
undecided 427 distributed job stream instance in plan owner 164
waiting 427 general priority 164
job stream z/OS internal status 173 status of job stream 164
creating 133 job stream name 173 task name 164
jobs status 173 workstation 164
creating dependencies between 199 workstation name 173 z/OS job stream instance in plan
jobs and dependencies distributed job stream instance in plan authority group 172
adding, modifying, deleting 214 time data contains monitored job 172
actual start time 174 extended task name 172
finish time 174 internal status 172
latest start time 174
K distributed parameters in database
job stream 171
job stream template 171
keyboard shortcut 417 parameter name 169 most critical job 172
killing distributed prompt states in plan occurrence token 172
job instance, distributed 320 prompt name 179 owner 172
killing fault-tolerant agent status 179 priority 172
job instance, z/OS 291 distributed prompts in database rerun requested 172
knowledge bases, searching for problem apply defaults 168 running on wait workstation 172
resolution 430 distributed resource in database status 172
resource name 167 time range 172
workstation name 167

454 IBM Tivoli Workload Scheduler Job Scheduling Console: User’s Guide
list filter criteria (continued)
z/OS job stream instance in plan
list properties (continued)
distributed prompt states in plan
M
(continued) (continued) management task
waiting for scheduling period 179 quick start 38
environment 172 periodic refresh 179 management tasks
z/OS resource in database distributed prompts in database Job Scheduling Console 37
group ID 166 apply defaults 168 managing
Hiperbatch 166 name 168 distributed engine 193
resource 166 period 168 workstation 197
treat input as 166 periodic refresh 168 z/OS engine 191
z/OS workstation in database distributed resource in database z/OS job stream 199
is fault-tolerant 165 apply defaults 167 managing z/OS engines
is for automation 165 name 167 with WebSphere Application Server
is wait 165 period 167 tools. 413
reporting attributes 165 periodic refresh 167 manuals
workstation 165 distributed Windows users in online xix
workstation types 165 database ordering xix
list properties apply defaults 169 mapping terminology 42
distributed calendars in database name 169 Max Usage Type
apply defaults 170 period 169 automatically reset 109
name 170 periodic refresh 169 available 109
period 170 distributed workstation classes in unavailable 109
periodic refresh 170 database menu descriptions
distributed domain states in plan apply defaults 168 distributed job stream editor menu
apply defaults 179 name 168 bar 60
name 179 period 168 actions 60
period 179 periodic refresh 168 edit 60
periodic refresh 179 distributed workstation in database file 60
distributed domains in database apply defaults 166 help 60
apply defaults 170 name 165 view 60
name 169 period 166 main menu bar 59
period 170 periodic refresh 165 console 59
periodic refresh 169 z/OS job instance in plan edit 59
distributed files in plan apply defaults 175 help 59
apply defaults 179 name 175 selected 59
name 179 period 175 view 59
period 179 periodic refresh 175 window 59
periodic refresh 179 z/OS job stream in database z/OS job stream editor menu bar 60
distributed job definition in database apply defaults 164 actions 60
apply defaults 167 name 163 edit 60
name 167 period 163 file 60
period 167 periodic refresh 163 help 60
periodic refresh 167 z/OS job stream instance in plan view 60
distributed job instance in plan apply defaults 171 messages 357
apply defaults 177 name 171 GJS0001E 357
name 176 period 171 GJS0002E 357
period 177 periodic refresh 171 GJS0003E 357
periodic refresh 176 z/OS resource in database GJS0004E 357
distributed job stream in database apply defaults 166 GJS0005E 358
apply defaults 164 name 166 GJS0006E 358
name 164 period 166 GJS0007E 358
period 164 periodic refresh 166 GJS0008E 358
periodic refresh 164 z/OS workstation in database GJS0009E 358
distributed job stream instance in plan apply defaults 165 GJS0010E 358
general name 165 GJS0011E 358
apply defaults 173 period 165 GJS0012E 358
name 173 periodic refresh 165 GJS0013E 359
period 173 listing all z/OS connector instance GJS0014E 359
periodic refresh 173 using WebSphere Application Server GJS0015E 359
distributed parameters in database tool 415 GJS0016E 359
apply defaults 169 lists GJS0017E 359
name 169 definitions 31 GJS0018E 359
period 169 local time zone GJS0019E 359
periodic refresh 169 overview 34 GJS0020E 359
distributed prompt states in plan logging GJS0021E 359
apply defaults 179 Job Scheduling Console to an GJS0022E 360
name 179 engine 46 GJS0024E 360
GJS0025E 360

Index 455
messages (continued) messages (continued) messages (continued)
GJS0026E 360 GJS0095E 368 GJS2052E 387
GJS0027E 360 GJS0096I 368 GJS2053E 387
GJS0028E 360 GJS0097E 368 GJS2054E 387
GJS0029E 360 GJS1001E 376 GJS2055W 387
GJS0030E 360 GJS1002E 376 GJS2056E 387
GJS0031E 361 GJS1003E 376 GJS2057E 387
GJS0032E 361 GJS1004E 376 GJS2058E 388
GJS0033E 361 GJS1005E 376 GJS2059E 388
GJS0034E 361 GJS1006E 376 GJS2060W 388
GJS0035E 361 GJS1007E 377 GJS2061E 388
GJS0036E 361 GJS1008E 377 GJS2062E 388
GJS0037E 361 GJS1009E 377 GJS2063E 388
GJS0038E 361 GJS1011E 377 GJS2064E 388
GJS0039E 362 GJS1012E 377 GJS2065W 388
GJS0040E 362 GJS1013E 377 GJS2066E 389
GJS0041E 362 GJS1014E 377 GJS2067E 389
GJS0042E 362 GJS2001E 382 GJS2068E 389
GJS0043E 362 GJS2002E 382 GJS2069E 389
GJS0044E 362 GJS2004E 382 GJS2070E 389
GJS0045E 362 GJS2005E 382 GJS2071E 389
GJS0046E 362 GJS2006E 382 GJS2072E 389
GJS0047E 363 GJS2007E 382 GJS2073E 389
GJS0048E 363 GJS2008E 382 GJS2074E 390
GJS0049E 363 GJS2009E 382 GJS2074W 390
GJS0050E 363 GJS2010E 382 GJS2075E 390
GJS0051E 363 GJS2011E 382 GJS2075W 390
GJS0052E 363 GJS2012E 382 GJS2076E 390
GJS0053E 363 GJS2013E 383 GJS2077E 390
GJS0054E 363 GJS2014E 383 GJS2078E 390
GJS0055E 364 GJS2015E 383 GJS2079E 390
GJS0056E 364 GJS2016E 383 GJS2080E 391
GJS0057E 364 GJS2017E 383 GJS2081E 391
GJS0058E 364 GJS2018E 383 GJS2082E 391
GJS0059E 364 GJS2019E 383 GJS2083E 391
GJS0060E 364 GJS2020E 383 GJS2084E 391
GJS0061E 364 GJS2021E 383 GJS2085E 391
GJS0062E 364 GJS2022E 383 GJS2086E 391
GJS0063E 365 GJS2023E 383 GJS2087E 391
GJS0064E 365 GJS2024E 384 GJS2088E 391
GJS0065E 365 GJS2025E 384 GJS2089W 391
GJS0066E 365 GJS2026E 384 GJS2090E 392
GJS0067E 365 GJS2027E 384 GJS2091W 392
GJS0068E 365 GJS2028E 384 GJS2092E 392
GJS0069E 365 GJS2029E 384 GJS2092W 392
GJS0070E 365 GJS2030E 384 GJS2093W 392
GJS0071W 366 GJS2031E 384 GJS2094E 392
GJS0072W 366 GJS2032E 384 GJS2094W 392
GJS0073E 366 GJS2033E 384 GJS2095E 392
GJS0073W 366 GJS2034E 385 GJS2096W 393
GJS0075E 366 GJS2035E 385 GJS2097W 393
GJS0076E 366 GJS2036E 385 GJS2098E 393
GJS0077E 366 GJS2037E 385 GJS2098W 393
GJS0078E 367 GJS2038E 385 GJS2099W 393
GJS0079E 367 GJS2039W 385 GJS2100E 393
GJS0080W 367 GJS2040E 385 GJS2101W 393
GJS0081E 367 GJS2041E 385 GJS2102W 393
GJS0082E 367 GJS2042E 386 GJS2103E 393
GJS0083E 367 GJS2043E 386 GJS2104W 394
GJS0084E 367 GJS2044E 386 GJS2105W 394
GJS0085E 367 GJS2045E 386 GJS2106E 394
GJS0086E 368 GJS2046W 386 GJS2107E 394
GJS0087E 368 GJS2047E 386 GJS2108E 394
GJS0088W 368 GJS2048E 386 GJS2109E 394
GJS0089E 368 GJS2049E 386 GJS2110E 394
GJS0093W 368 GJS2050W 387 GJS2111E 394
GJS0094E 368 GJS2051E 387 GJS2112E 394

456 IBM Tivoli Workload Scheduler Job Scheduling Console: User’s Guide
messages (continued) messages (continued) messages (continued)
GJS2113E 395 GJS3051E 372 GJS4032E 380
GJS2114W 395 GJS3052E 372 GJS4033E 380
GJS2115E 395 GJS3057E 372 GJS4034W 380
GJS2116E 395 GJS3058E 372 GJS4035W 380
GJS2117E 395 GJS3060E 372 GJS4036W 380
GJS2118E 395 GJS3061E 373 GJS4037E 380
GJS2119E 395 GJS3063E 373 GJS4038W 380
GJS2120E 395 GJS3064E 373 GJS4039W 381
GJS2121E 395 GJS3065E 373 GJS4040E 381
GJS2122E 395 GJS3067E 373 GJS4041E 381
GJS2123E 396 GJS3068E 373 GJS4042E 381
GJS2124E 396 GJS3069W 373 GJS4043W 381
GJS2125E 396 GJS3070E 373 GJS4044W 381
GJS2126W 396 GJS3071E 373 GJS4045W 381
GJS2128E 396 GJS3073E 373 GJS4046W 381
GJS2129E 396 GJS3089W 373 GJS4047W 381
GJS2130W 396 GJS3090E 374 GJS5001I 398
GJS2131E 396 GJS3091E 374 GJS5002W 398
GJS2132E 397 GJS3092E 374 GJS5003W 398
GJS2133E 397 GJS3093E 374 GJS5004W 398
GJS2134W 397 GJS3094E 374 GJS5005E 398
GJS2135E 397 GJS3095E 374 GJS5006E 399
GJS2136E 397 GJS3097E 374 GJS5027W 399
GJS2137E 397 GJS3100E 374 GJS5028W 399
GJS2138W 397 GJS3102E 374 GJS5034W 399
GJS2139E 397 GJS3103E 374 GJS5035W 399
GJS2141E 397 GJS3104E 375 GJS5042W 399
GJS2142E 397 GJS3105E 375 GJS5043W 399
GJS2143E 397 GJS3106E 375 GJS5046W 399
GJS2144E 398 GJS3107E 375 GJS5047W 399
GJS2145W 398 GJS3108E 375 GJS5048W 399
GJS2146E 398 GJS3109E 375 GJS5049W 400
GJS2147E 398 GJS3110E 375 GJS5050W 400
GJS3001W 369 GJS3111E 375 GJS5051W 400
GJS3003E 369 GJS3112E 375 GJS5052W 400
GJS3004E 369 GJS3113E 375 GJS5053W 400
GJS3005E 369 GJS3116E 375 GJS5054W 400
GJS3006E 369 GJS3117E 376 GJS5055W 400
GJS3007E 369 GJS3118E 376 GJS5056W 400
GJS3008E 369 GJS4001E 377 GJS5058E 400
GJS3009E 369 GJS4002E 377 GJS5059E 400
GJS3010E 370 GJS4003E 378 GJS5059W 401
GJS3011E 370 GJS4004E 378 GJS5063W 401
GJS3012E 370 GJS4008E 378 GJS5064W 401
GJS3013E 370 GJS4009E 378 GJS5065W 401
GJS3014E 370 GJS4010W 378 GJS5066W 401
GJS3015E 370 GJS4011W 378 GJS5067W 401
GJS3016E 370 GJS4012W 378 GJS5069I 401
GJS3029E 370 GJS4013W 378 GJS5070I 401
GJS3030E 370 GJS4014W 378 GJS5071E 402
GJS3031E 371 GJS4015W 378 GJS5072E 402
GJS3032E 371 GJS4016W 378 GJS5073E 402
GJS3033E 371 GJS4017W 379 GJS5074E 402
GJS3034E 371 GJS4018E 379 GJS5075E 402
GJS3039E 371 GJS4019E 379 GJS5076E 402
GJS3040E 371 GJS4020E 379 GJS5077E 402
GJS3041E 371 GJS4021E 379 GJS5078E 402
GJS3042E 371 GJS4022E 379 GJS5079W 402
GJS3043E 371 GJS4023E 379 GJS5080E 403
GJS3044E 371 GJS4024E 379 GJS5081E 403
GJS3045E 371 GJS4025E 379 GJS5082E 403
GJS3046E 372 GJS4027E 379 GJS5083E 403
GJS3047E 372 GJS4028E 380 GJS5084E 403
GJS3048E 372 GJS4029W 380 GJS5085W 403
GJS3049E 372 GJS4030E 380 GJS5086E 403
GJS3050E 372 GJS4031E 380 GJS5089E 403

Index 457
messages (continued) on error prompt
GJS5091E 403 assume system default 108 list
GJS5092E 403 free 108 distributed 168
GJS5093E 403 free if exclusive 108 replying 339
GJS5094E 404 free if shared 108 status 339
GJS5095E 404 keep 108 prompts
GJS5096E 404 online publications definitions 31
GJS5097E 404 accessing xxv properties z/OS connector instance
GJS5098E 404 operational UN-NOP displaying using WebSphere
GJS5100E 404 setting z/OS job instance to 291 Application Server tool 414
GJS5101E 404 ordering publications xxvi updating using WebSphere
GJS5102E 404 Application Server tool 415
GJS5103I 404 publications
GJS5104W 405
GJS5105W 405
P accessing online xxv
library xix
pane descriptions
GJS5106W 405 online xix, xxvi
Actions list 55
GJS5107W 405 ordering xix, xxvi
Explorer View 56
GJS5108W 405
Hyperbolic View 57
GJS5109W 405
Object list 56
GJS5110W 405
GJS6001E 406
Timeline View 57 Q
Work with engines 56 quick start
GJS6004E 406
panel descriptions command and task mapping 42
GJS6005E 406
Impact View 57 definition tasks 37
GJS6005W 406
Job Stream Editor 58 creating a group of lists 40
GJS6006E 406
panel elements creating calendars 40
GJS6007E 406
create engine Creating common plan lists 40
GJS6008E 406
password 96 creating database lists 40
GJS6009E 406
save password 96 creating domains 40
GJS6010I 406
user name 96 creating forecast and trial
GJS6011E 406
parallel server settings plans 40
methods
control on servers 101 creating job definitions 40
to install Job Scheduling Console 10
planning on servers 101 creating job streams 40
modifying
parameter creating parameters 40
a job in the Graph View 214
creating 115 creating plan lists 40
jobs and dependencies 214
list creating prompts 40
multi–
distributed 168 creating resources 40
hierarchy 4
parameters creating using Create Another 40
definitions 31 creating Windows users 40
password for z/OS connector creating workstation classes 40
N TWSUser, changing 409 creating workstations 40
network topology path names, notation xxviii management task 38
Tivoli Workload Scheduler 3 plan management tasks
non operational NOP definitions 31 managing calendars 41
setting z/OS job instance to 291 restoring 347 managing domains 41
NOP z/OS job instance setting 345 managing domains in the plan 42
setting to non operational 291 planning managing engines 41
notation installation 9 managing file dependencies in the
environment variables xxviii pop-up menus plan 42
path names xxviii Job Scheduling Console 49 managing job definitions 41
typeface xxviii predefined prompt managing job instances in the
creating 117 plan 41
definitions 31 managing job stream instances in
O preferences.xml 34
problem determination
the plan 41
managing job streams 41
object
describing problems 434 managing parameters 41
distributed engine 29
determining business impact 434 managing prompts 41
z/OS engine 28
submitting problems 434 managing prompts dependencies
objects Job Scheduling Console
problem resolution 429 in the plan 42
description 27
processes managing resources 41
offset-based run cycle
netman 105 managing resources in the
creating 209
product plan 41
example 212
library xix managing Windows users 41
on complete
program numbers managing Windows users in the
assume system default 109
5601-453 xxvi plan 42
automatically reset 109
5601-454 xxvi managing workstation classes 41
available 108
5765-086 xxvi managing workstations 41
unavailable 108

458 IBM Tivoli Workload Scheduler Job Scheduling Console: User’s Guide
quick start (continued) setting (continued) task type
management tasks (continued) z/OS job instance to non operational Job Scheduling Console 37
managing workstations in the (NOP) 291 TCP/IP
plan 41 shortcut keys 417 connection for Job Scheduling
restore a plan 42 silent installation Console 9
setting an alternate plan 42 Job Scheduling Console 11 technical training xxvii
working with lists 41 z/OS Connector 16 term definitions
task mapping 40 simple run cycle 233 distributed
single tier engine 43
topology 3 exclusive run cycle 43
R softcopy books xxvi
Software Distribution
external dependency 43
job 43
RACF authority group 135
installing Job Scheduling Console 10 job identifier 43
recovery information
software package blocks job in the plan 43
z/OS job instance in plan 294
install_dir 14 resources 43
Redbooks, IBM 429
JRE142_operating system.spb 14 schedule 42, 43
removing z/OS connector instance
TWSConsole.spb 12 start time 43
using WebSphere Application Server
TWSConsoleLanguages.spb 12 symphony 43
tool 416
software support 429 Job Scheduling Console
replying
Software Support earliest start time 43
prompt 339
contacting 433 engine 43
replying to a prompt 339
describing problems 434 exclusive run cycle 43
required data
determining business impact 434 external job 43
Job Scheduling Console 49
receiving weekly updates 432 external job stream 43
resource
submitting problems 434 job 43
changing units 336
special resource job identifier 43
creating 107
definition 28 job instances 43
definition 28
SSL communication job stream 42
status 335
all forced 105 job stream instance 43
viewing plan properties 335
allow incoming 105 job stream template 42
resource distributed
disabled 105 logical resources 43
creating 111
upward forced 105 offset-based run cycle 43
resource editor 110
standard buttons plan 43
resource in database
Job Scheduling Console 48 rule-based run cycle 43
list
starting valid from 43
distributed 166
Job Scheduling Console 45 valid to 43
z/OS 166
Job Scheduling Console from an z/OS
resource z/OS
external application 421 application 42
creating 107
starting a workstation 329 application group 42
response file
starting workstations, domain 341 controller 43
z/OS Connector 16
status current plan 43
restoring
prompt 339 external dependency 43
plan 347
stopping a workstation 329 in-effect date for run cycles 43
z/OS job instance to operational
stopping workstations, domain 341 input arrival time 43
(UN-NOP) 291
submitting a distributed ad hoc job negative run cycle 43
rule-based run cycle
into a specific job stream 299 occurrence 43
creating 202
submitting a distributed job operation 43
example 206
into a default job stream 297 operation number 43
rules
into a specific job stream 299 operations in the current plan 43
freedays calendar 36
submitting ad hoc job out-of-effect date for run
run cycle
into a default job stream 307 cycles 43
calendar 233
support 429 run cycle with offsets 43
daily 233
support assistant 429 run cycle with rules 43
definition 34
support Web site, searching to find special resources 43
deleting 236
software problem resolution 430 task 43
inclusive or exclusive 36
switch manager command 342 terminology mapping 42
simple 233
switching domain managers 342 time restrictions
weekly 234
definition 32
time zone

S T dead zone 33
overview 33
task flow
set parallel servers time zone local
Job Scheduling Console 37
control on servers 101 overview 34
task guide
planning on servers 101 Timeline View 57
Job Scheduling Console 37
setting Tivoli software information center xxv
task mapping
alternate plan 345 Tivoli Workload Scheduler
quick start 40
traces 351 topology 3

Index 459
tool WebSphere Application Server
managing z/OS engines 413
U WebSphere Application Server tool
z/OS connector instance 413
z/OS connector instance 413 UN-NOP z/OS job instance z/OS connector instance displaying
z/OS connector instance displaying restoring to operational 291 properties 414
properties 414 unattended installation z/OS connector instance listing 415
z/OS connector instance listing 415 z/OS Connector 16 z/OS connector instance
z/OS connector instance uninstalling removing 416
removing 416 components 23 z/OS connector instance updating
z/OS connector instance updating Job Scheduling Console 23 properties 415
properties 415 Job Scheduling Console with weekly run cycle 234
toolbar descriptions wrmvsp 24 wildcards
distributed job stream editor 61 language packs 23 Job Scheduling Console 48
add dependency on external z/OS connector 24 Windows user
job 61 unlinking a workstation 329 creating 113
add dependency on external job unlinking workstations, domain 342 list
stream 61 unsupported characters distributed 169
add dependency on Job Scheduling Console 48 Windows user passwords
internetwork 61 updating z/OS connector instance changing 343
add job definition 61 properties, using WebSphere Work with engines pane 56
add link 61 Application Server tool 415 workstation
add multiple job definitions 61, used for creating 97
84 control 108 distributed creating 103
explorer view 61, 62 neither planning nor control 108 distributed quick reference 73
graph view 61 planning 108 linking 329
run cycle view 61 planning and control 108 managing 197
timeline view 61 user preferences starting 329
impact view 63 Job Scheduling Console 17 stopping 329
down view 63 user preferences from versions 8.3 unlinking 329
left view 63 Job Scheduling Console 18 z/OS creating 98
predecessors view 63 user preferences from versions prior to workstation class
radial view 63 8.3 creating 125
right view 63 Job Scheduling Console 17 list
successors view 63 distributed 168
up view 63 workstation in database
main window 60 V list
copy 60 variables distributed 165
cut 60 install z/OS 165
paste 60 INSTALL_DIR_AIX 12 wrmvsp 24
refresh 60 INSTALL_DIR_HP-UX 12, 13
stop 60 INSTALL_DIR_Linux 12
tree 60
z/OS job stream editor 62
INSTALL_DIR_SunOS 12, 13 Z
INSTALL_DIR_Windows_NT 12 z/OS connector
add automation task 62 INSTALL_DIR 12 installation program 15
add external dependency 62 INSTALL_DIR_AIX 12 uninstalling 24
add FTW job 62 INSTALL_DIR_SunOS 12, 13 wizard 15
add general job 62 language z/OS Connector
add JCL job 62 Brazilian Portuguese 13 response file 16
add link 62 French 13 silent installation 16
add printer job 62 German 13 unattended installation 16
add setup job 62 Italian 13 z/OS connector instance creating
add started task job 62 Japanese 13 using WebSphere Application Server
add write-to-operator job 62 Korean 13 tool 413
graph 63 Simplified Chinese 13 z/OS connector instance displaying
graph view 62 Spanish 13 properties using WebSphere
timeline view 62 Traditional Chinese 13 Application Server tool 414
topology variables, environment, notation xxviii z/OS connector instance listing
single tier 3 viewing prompt status 339 using WebSphere Application Server
Tivoli Workload Scheduler 3 viewing resource properties in the tool 415
traces plan 335 z/OS connector instance removing
setting 351 viewing resource status 335 using WebSphere Application Server
training
tool 416
technical xxvii
z/OS connector instance updating
TWSUser,
changing password for z/OS
W properties using WebSphere
WebSphere Application Server Application Server tool 415
connector 409
changing password for z/OS z/OS critical job filter criteria
typeface conventions xxvii
connector 409 critical path 176
managing z/OS engines 413 no 176

460 IBM Tivoli Workload Scheduler Job Scheduling Console: User’s Guide
z/OS critical job filter criteria (continued) z/OS job instance in plan (continued) z/OS job instances in plan (continued)
WLM 176 general (continued) resources (continued)
z/OS critical job values latest start time 278 logical resources 282
critical path 140 planned start time 278 on complete 283
no 140 priority 278 quantity 283
WLM 140 runtime 278 resource 282
z/OS critical job values in plan started 278 target resources 282
critical path 280 workstation 278 successors
no 280 killing a job instance on fault-tolerant extended task name 287
WLM 280 agent 291 identifier 286
z/OS engine options job stream name 286
managing 191 auto error completion 281 job stream start 286
specific objects 28 auto hold release 281 on critical path 287
z/OS engine properties auto job submission 281 task name 286
engine name 192 cancel if late 281 timeline view
host name 192 deadline WTO 281 deadline 287
password 192 expanded JCL 282 duration 287
port number 192 highest acceptable return name 287
remote server name 192 code 281 runtime 287
save password 192 reroutable 282 start at 287
user name 192 restart and cleanup 282 started 287
z/OS engines managing restartable 282 z/OS job properties
with WebSphere Application Server use sysout 282 automation
tools. 413 user data 281 automated function 146, 285
z/OS job recovery information 294 command text 145, 284
access types task completion info 145, 284
exclusive 144 extended task name 279 security element 147, 285
shared 144 form number 279 general
z/OS job feedback option values job class 279 auto error completion 140
limit for feedback 142 scheduling environment auto hold release 140
smoothing factor 142 name 279 auto job submission 140
z/OS job instance task name 279 cancel if late 140
restoring to operational time restrictions centralized script 140
(UN-NOP) 291 deadline 279 critical job 140
setting to non operational (NOP) 291 duration 279 deadline WTO 140
z/OS job instance in plan start 279 description 139
automatic recovery 294 z/OS job instance in the plan expanded JCL 142
critical path 295 restart and cleanup options feedback options 142
details display clean up result 293 highest acceptable return
actual end 281 job restart 293 code 140
centralized script 280 start cleanup 293 monitored job 140
cleanup status 280 start cleanup with AR 293 name 139
completed predecessors 281 step restart 293 target workstation 139
intermediate start 281 use expanded JCL 293 use sysout 142
JCL preparation 280 restart options WLM class 141
latest out passed 280 fast job restart 294 WLM policy 140
logical resources 281 fast step restart 294 options
monitored job 280 restart and cleanup 293 reroutable 142
on critical path 280 z/OS job instance WLM policies restart and cleanup 142
planned duration 281 conditional 280 restartable 141
predecessors 281 deadline 280 resources
successors 281 latest start 281 access type 144
transport time 281 long duration 281 keep on error 144
urgent 280 z/OS job instances in plan logical resources 144
WLM class 281 access types on complete 144
WLM policy 280 exclusive 283 quantity 144
general shared 283 resource 144
actual start time 278 predecessors target resources 143
authority group 278 extended task name 286 task
belongs to job stream 278 identifier 286 extended task name 141
critical job 280 job stream name 286 form number 141
description 278 job stream start 286 job class 141
earliest start time 278 on critical path 286 scheduling environment
error code 278 task name 286 name 141, 164
identifier 278 resources task name 141
internal status 278 access type 283 use extended information 141
JES job number 278 keep on error 283 use scheduling environment 141

Index 461
z/OS job properties (continued) z/OS job streams (continued) z/OS resource properties (continued)
time restrictions fault-tolerant-workstation task job resource description 108
deadline 143 icon 138 resource editor 110
duration 143 general job icon 137 used for 108
start 143 JCL job icon 137 planning 108
z/OS job instance in plan printer job icon 137 z/OS resources
scheduling environment setup job icon 138 used for
name 175 started task job icon 137 control 108
z/OS job stream instance in plan write-to-operator job icon 138 neither planning not control 108
scheduling environment z/OS object planning and control 108
name 172 resource 107 z/OS resources in plan
z/OS job reroutable values workstation 98 active lifespan
default 142 z/OS offset-based run cycle action 333
no 142 description 210 expiration date 333
yes 142 exclusive run cycle 211 deviation 331
z/OS job restart and cleanup values JCL variable table 211 last updated
automatic 142 name 210 last change action 332
immediate 142 offsets on 332
manual 142 available offsets 212 updated by 332
none 142 in the following period 212 quantity 332
z/OS job restartable values rule for freedays 210 usage counter 332
default 142 start 211 z/OS rule for freedays
no 142 valid date 211 count workdays and freedays
yes 141 z/OS resource alike 203, 210
z/OS job start values creating 107 count workdays only 203, 210
follow job stream rules 143, 279 z/OS resource availability intervals if freeday do not schedule at all 203,
no restrictions 143, 279 available 110 211
specify earliest start time 143, 279 default 110 schedule on last workday before
z/OS job stream not available 110 freeday 203, 210
creating 133 specific date 110 schedule on next workday after
managing 199 standard 110 freeday 203, 210
z/OS job stream feedback option values z/OS resource in database z/OS rule-based run cycle
limit for feedback 136 treat input as deadline 203, 211
smoothing factor 135 exact match 166 description 203
z/OS job stream instances in the plan prefix 166 exclusive run cycle 203
submit suffix 166 frequency 205
action type 259 wildcard 166 JCL variable table 203
authority group name 259 z/OS resource properties name 203
dependencies resolution 259 availability intervals 110 periods 204
description 259 day 110 repeat end time 204, 211
JCL variable table 258 from time 110 repeat every 204, 211
job stream name 258 is available 110 repeat option 204, 211
job stream template 259 quantity 110 rule for freedays 203
owner 259 to time 110 start 203
owner description 259 workstations 110 valid date 203
priority 258 default workstations 109 z/OS run cycles
start 259 default: is available 109 offset-based 35
timeline view default: quantity 109 rule-based 35
dealine 260 group ID 108 z/OS WLM policy values
start 260 Hiperbatch 108 blank 140
z/OS job stream properties Max Usage Limit 109 conditional 141
authority group name 135 Max Usage Type 109 deadline 140
calendar 135 automatically reset 109 latest start 141
contains monitored job 135 available 109 long duration 141
description 134 unavailable 109 z/OS workstation
feedback options 135 name 108 definition 27
inherits from template 135 on complete 108 z/OS workstation day
is active 135 assume system default 109 specific date 102
job stream name 134 automatically reset 109 standard 102
owner 134 available 108 z/OS workstation open time intervals
owner description 134 unavailable 108 status
priority 135 on error 108 closed 102
template 134 assume system defaults 108 defined 102
valid from 135 free 108 z/OS workstation properties
z/OS job streams free if exclusive 108 general
automation task job icon 138 free if shared 108 automation 99
keep 108 control on servers 100

462 IBM Tivoli Workload Scheduler Job Scheduling Console: User’s Guide
z/OS workstation properties (continued)
general (continued)
destination 99
duration 100
fault-tolerant 99
job setup 100
name 100
node address 101
planning on servers 100
port number 101
printout routing 99
reporting attribute 99
splittable 100
started task, stc 100
transport time 100
workstation description 98
workstation name 98
workstation type 99
WTO 100
open time intervals
alternate workstation 103
day 102
from time 102
parallel servers 102
R1 capacity 102
R2 capacity 102
status 102
to time 102
resources
resource name 101
used for control 101
used for planning 101
z/OS workstation reporting attributes
automatic 99, 322
completion only 99, 322
manual start and completion 99, 322
non reporting 99, 322
z/OS workstation types
computer 99
general 99
printer 99

Index 463
464 IBM Tivoli Workload Scheduler Job Scheduling Console: User’s Guide


Program Number: 5697–WSZ, 5698-WSH

Printed in USA

SC32-1257-06
Spine information:

IBM Tivoli Workload Scheduler Job Scheduling Console Version 8.3 User’s Guide