390
IBM Tivoli Workload Scheduler for z/OS Customization and Tuning Version 8.1 (Maintenance Release October 2003) SH19-4544-01
IBM
Tivoli
Workload
Scheduler
for
z/OS
Customization
and
Tuning
Version
8.1
(Maintenance
Release
October
2003)
SH19-4544-01
���
IBM
Tivoli
Workload
Scheduler
for
z/OS
Customization
and
Tuning
Version
8.1
(Maintenance
Release
October
2003)
SH19-4544-01
���
Note
Before
using
this
information
and
the
product
it
supports,
read
the
information
in
“Notices”
on
page
343.
Refreshed
Edition
(October
2003)
This
refreshed
edition
applies
to
version
8,
release
1,
modification
0
of
IBM
Tivoli
Workload
Scheduler
for
z/OS
(program
number
5697-WSZ)
and
to
all
subsequent
releases
and
modifications
until
otherwise
indicated
in
new
editions.
Contents
Preface
.
.
.
.
.
.
.
.
.
.
.
.
.
. vii
Maintenance
Release
.
.
.
.
.
.
.
.
.
.
. vii
Who
Should
Read
This
Guide
.
.
.
.
.
.
.
. viii
What
This
Guide
Contains
.
.
.
.
.
.
.
.
. viii
Publications
.
.
.
.
.
.
.
.
.
.
.
.
.
. x
Publications
for
Tivoli
Workload
Scheduler
for
z/OS
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. x
Using
LookAt
to
Look
Up
Message
Explanations
x
Accessing
Publications
Online
.
.
.
.
.
.
. xi
Softcopy
Collection
Kit
.
.
.
.
.
.
.
.
.
. xi
Ordering
Publications
.
.
.
.
.
.
.
.
.
. xi
Providing
Feedback
about
Publications
.
.
.
. xii
Contacting
IBM
Software
Support
.
.
.
.
.
.
. xii
Conventions
Used
in
This
Guide
.
.
.
.
.
.
. xii
How
to
Read
Syntax
Diagrams
.
.
.
.
.
.
.
. xii
Part
1.
Customizing
Tivoli
Workload
Scheduler
for
z/OS
.
.
.
.
.
.
.
.
. 1
Chapter
1.
Initialization
Statements-Reference
.
.
.
.
.
.
.
.
. 3
Specifying
the
Statements
.
.
.
.
.
.
.
.
.
. 3
Creating
the
Statements
.
.
.
.
.
.
.
.
.
. 3
Storing
the
Statements
.
.
.
.
.
.
.
.
.
. 4
Overriding
the
EQQPARM
Statements
.
.
.
.
. 4
Selecting
Statements
for
the
Tracker
and
Controller
4
Other
Initialization
Statements
.
.
.
.
.
.
. 5
Chapter
2.
Identifying
Related
Initialization-Statement
Parameters
.
. 123
Configuration
.
.
.
.
.
.
.
.
.
.
.
.
. 124
Security
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. 124
Generating
Audit
Information
(JT
Log
Data)
.
.
. 125
Determining
the
Success
or
Failure
of
a
Job
.
.
. 126
Recovery
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. 127
Restart
and
Cleanup
.
.
.
.
.
.
.
.
.
. 127
Job
Log
Retrieval
.
.
.
.
.
.
.
.
.
.
. 128
Automatic
Job
Recovery
.
.
.
.
.
.
.
.
. 128
Workload
Restart
.
.
.
.
.
.
.
.
.
.
. 128
Performance
.
.
.
.
.
.
.
.
.
.
.
.
.
. 129
Reporting
.
.
.
.
.
.
.
.
.
.
.
.
.
. 130
RODM
Monitoring
.
.
.
.
.
.
.
.
.
.
. 130
Output
Processing
.
.
.
.
.
.
.
.
.
.
.
. 131
Chapter
3.
Implementing
Security
.
.
. 133
Planning
Security
Implementation
.
.
.
.
.
. 133
How
Tivoli
Workload
Scheduler
for
z/OS
Verifies
Access
Authority
.
.
.
.
.
.
.
. 134
Identifying
Users
.
.
.
.
.
.
.
.
.
.
. 135
Establishing
Naming
Conventions
for
Tivoli
Workload
Scheduler
for
z/OS
Resources
.
.
. 136
Grouping
RACF
Users
and
Resources
.
.
.
. 136
General
Security
Considerations
.
.
.
.
.
. 137
Controlling
Access
to
Tivoli
Workload
Scheduler
for
z/OS
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. 137
Controlling
Access
to
the
Tivoli
Workload
Scheduler
for
z/OS
Subsystem
.
.
.
.
.
. 138
Controlling
Access
to
Tivoli
Workload
Scheduler
for
z/OS
Fixed
Resources
.
.
.
.
.
.
.
. 138
Controlling
Access
to
Tivoli
Workload
Scheduler
for
z/OS
Subresources
.
.
.
.
.
.
.
.
. 139
Controlling
Access
to
Tivoli
Workload
Scheduler
for
z/OS
from
APPC
.
.
.
.
.
.
.
.
.
. 141
Controlling
Access
to
Tivoli
Workload
Scheduler
for
z/OS
Using
Tivoli
Job
Scheduling
Console
. 142
Controlling
Access
through
TSO
Commands
145
Functions
and
Data
that
You
Can
Protect
.
.
.
. 146
Access
Requirements
to
Fixed
Resources
for
Dialog
Users
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. 150
Examples
of
Security
Strategies
.
.
.
.
.
.
. 154
A
Centralized
Security
Strategy
.
.
.
.
.
. 154
A
Decentralized
Security
Strategy
.
.
.
.
. 155
Chapter
4.
Tivoli
Workload
Scheduler
for
z/OS
Exits
.
.
.
.
.
.
.
.
.
.
. 159
Tivoli
Workload
Scheduler
for
z/OS
User
Exits
Invocation
.
.
.
.
.
.
.
.
.
.
.
.
.
. 160
Start/Stop
Exit
(EQQUX000)
.
.
.
.
.
.
. 160
Job-Submit
Exit
(EQQUX001)
.
.
.
.
.
.
. 160
Job-Library-Read
Exit
(EQQUX002)
.
.
.
.
. 160
Application-Description-Feedback
Exit
(EQQUX003)
.
.
.
.
.
.
.
.
.
.
.
. 160
Event-Filtering
Exit
(EQQUX004)
.
.
.
.
.
. 161
SYSOUT
Archiving
Exit
(EQQUX005)
.
.
.
. 161
Incident-Record-Create
Exit
(EQQUX006)
.
.
. 161
Operation-Status-Change
Exit
(EQQUX007)
.
. 161
Operation-Initiation
Exit
(EQQUX009)
.
.
.
. 161
Job-Tracking
Log
Write
Exit
(EQQUX011)
.
.
. 161
JCL-Imbed
Exit
(on
FETCH
directive)
.
.
.
. 161
JCL-Variable-Substitution
Exit
(on
JCL
Variable)
161
Automatic-Job-Recovery
Exit
(on
RECOVER
statement)
.
.
.
.
.
.
.
.
.
.
.
.
. 161
Daily-Planning-Report
Exit
(EQQDPUE1)
.
.
. 162
EQQDELDS/EQQCLEAN
Catalog
Exit
(EQQUXCAT)
.
.
.
.
.
.
.
.
.
.
.
. 162
EQQCLEAN
GDG
Resolution
Exit
(EQQUXGDG)
.
.
.
.
.
.
.
.
.
.
.
. 162
Tivoli
Workload
Scheduler
for
z/OS
Start/Stop
Exit
(EQQUX000)
.
.
.
.
.
.
.
.
.
.
.
. 162
Installing
the
Exit
.
.
.
.
.
.
.
.
.
.
. 162
Interface
to
the
Exit
.
.
.
.
.
.
.
.
.
. 162
Job-Submit
Exit
(EQQUX001)
.
.
.
.
.
.
.
. 163
Installing
the
Exit
.
.
.
.
.
.
.
.
.
.
. 163
Interface
to
the
Exit
.
.
.
.
.
.
.
.
.
. 163
Job-Library-Read
Exit
(EQQUX002)
.
.
.
.
.
. 166
Installing
the
Exit
.
.
.
.
.
.
.
.
.
.
. 166
Interface
to
the
Exit
.
.
.
.
.
.
.
.
.
. 166
Application-description-feedback
Exit
(EQQUX003)
170
iii
||
||||||||||||
|
|
|
|
|
|
Installing
the
Exit
.
.
.
.
.
.
.
.
.
.
. 170
Interface
to
the
Exit
.
.
.
.
.
.
.
.
.
. 170
Event-filtering
Exit
(EQQUX004)
.
.
.
.
.
.
. 171
Installing
the
Exit
.
.
.
.
.
.
.
.
.
.
. 171
Interface
to
the
Exit
.
.
.
.
.
.
.
.
.
. 171
SYSOUT
Archiving
Exit
(EQQUX005)
.
.
.
.
. 172
Installing
the
Exit
.
.
.
.
.
.
.
.
.
.
. 172
Interface
to
the
Exit
.
.
.
.
.
.
.
.
.
. 172
Incident-record-create
Exit
(EQQUX006)
.
.
.
. 174
Installing
the
Exit
.
.
.
.
.
.
.
.
.
.
. 175
Interface
to
the
Exit
.
.
.
.
.
.
.
.
.
. 175
Operation-Status-Change
Exit
(EQQUX007)
.
.
. 176
Installing
the
Exit
.
.
.
.
.
.
.
.
.
.
. 177
Interface
to
the
Exit
.
.
.
.
.
.
.
.
.
. 177
Operation-initiation
Exit
(EQQUX009)
.
.
.
.
. 180
Installing
the
Exit
.
.
.
.
.
.
.
.
.
.
. 180
Interface
to
the
Exit
.
.
.
.
.
.
.
.
.
. 181
Job-tracking
Log
Write
Exit
(EQQUX011)
.
.
.
. 182
Installing
the
Exit
.
.
.
.
.
.
.
.
.
.
. 182
Interface
to
the
Exit
.
.
.
.
.
.
.
.
.
. 182
EQQDELDS/EQQCLEAN
Catalog-Exit
(EQQUXCAT)
.
.
.
.
.
.
.
.
.
.
.
.
. 184
Installing
the
Exit
.
.
.
.
.
.
.
.
.
.
. 184
Interface
to
the
Exit
.
.
.
.
.
.
.
.
.
. 184
EQQCLEAN
GDG
Resolution
Exit
(EQQUXGDG)
185
DDPROT/DSNPROT
Interactions
.
.
.
.
. 185
Installing
the
Exit
.
.
.
.
.
.
.
.
.
.
. 186
Interface
to
the
Exit
.
.
.
.
.
.
.
.
.
. 186
JCL-imbed
Exit
.
.
.
.
.
.
.
.
.
.
.
.
. 187
Installing
the
Exit
.
.
.
.
.
.
.
.
.
.
. 187
Interface
to
the
Exit
.
.
.
.
.
.
.
.
.
. 187
JCL-variable-Substitution
Exit
.
.
.
.
.
.
.
. 189
Installing
the
Exit
.
.
.
.
.
.
.
.
.
.
. 189
Interface
to
the
Exit
.
.
.
.
.
.
.
.
.
. 189
Automatic-job-Recovery
Exit
.
.
.
.
.
.
.
. 191
Installing
the
Exit
.
.
.
.
.
.
.
.
.
.
. 191
Interface
to
the
Exit
.
.
.
.
.
.
.
.
.
. 191
Daily-planning-report
Exit
(EQQDPUE1)
.
.
.
. 193
Installing
the
Exit
.
.
.
.
.
.
.
.
.
.
. 193
Interface
to
the
Exit
.
.
.
.
.
.
.
.
.
. 193
Chapter
5.
Reporting
Events
to
Tivoli
Workload
Scheduler
for
z/OS
.
.
.
. 195
Supplying
Event
Information
to
Tivoli
Workload
Scheduler
for
z/OS
.
.
.
.
.
.
.
.
.
.
. 195
General
Information
about
Tivoli
Workload
Scheduler
for
z/OS
Subroutines
.
.
.
.
.
. 196
Using
the
General
Tivoli
Workload
Scheduler
for
z/OS
Subroutine
(EQQUSIN)
.
.
.
.
.
.
.
. 197
Invocation
Requirements
.
.
.
.
.
.
.
. 197
EQQUSIN
Parameters
.
.
.
.
.
.
.
.
. 197
Specifying
Selection
Criteria
.
.
.
.
.
.
. 202
Specifying
Object
Fields
to
Update
.
.
.
.
. 206
Return
Codes
and
Reason
Codes
Generated
by
EQQUSIN
.
.
.
.
.
.
.
.
.
.
.
.
. 210
Using
Individual
Tivoli
Workload
Scheduler
for
z/OS
Subroutines
.
.
.
.
.
.
.
.
.
.
.
. 211
Using
EQQUSINB
.
.
.
.
.
.
.
.
.
.
. 211
Using
EQQUSINO
.
.
.
.
.
.
.
.
.
.
. 211
Using
EQQUSINS
.
.
.
.
.
.
.
.
.
.
. 213
Using
EQQUSINT
.
.
.
.
.
.
.
.
.
.
. 214
Using
EQQUSINW
.
.
.
.
.
.
.
.
.
. 216
Chapter
6.
Using
the
Job
Completion
Checker
.
.
.
.
.
.
.
.
.
.
.
.
.
. 219
JCC
Message
Tables
.
.
.
.
.
.
.
.
.
.
. 219
Incident
Logging
Function
.
.
.
.
.
.
.
.
. 220
Defining
Message
Tables
using
EQQJCCT
.
.
. 222
Chapter
7.
Using
the
Data
Store
.
.
. 229
Overview
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. 229
Prerequisites
.
.
.
.
.
.
.
.
.
.
.
.
.
. 230
Installing
the
Data
Store
.
.
.
.
.
.
.
.
.
. 231
Run
EQQJOBS
to
Create
Installation
Samples
.
.
. 231
Estimating
the
size
of
Data
Store
VSAM
data
files
231
Data
files
.
.
.
.
.
.
.
.
.
.
.
.
.
. 232
Primary
Index
.
.
.
.
.
.
.
.
.
.
.
. 233
Secondary
Index
.
.
.
.
.
.
.
.
.
.
. 233
Characteristics
of
the
Local
Data
Store
.
.
.
. 234
Allocate
Data
Store
VSAM
.
.
.
.
.
.
.
.
. 234
Data
Files
.
.
.
.
.
.
.
.
.
.
.
.
. 234
Primary
index
.
.
.
.
.
.
.
.
.
.
.
. 234
Secondary
index
.
.
.
.
.
.
.
.
.
.
. 235
Initialize
Data
Store
VSAM
Files
.
.
.
.
.
.
. 235
Data
files
.
.
.
.
.
.
.
.
.
.
.
.
.
. 235
Primary
index
.
.
.
.
.
.
.
.
.
.
.
. 235
Secondary
index
.
.
.
.
.
.
.
.
.
.
. 236
Configuring
the
Data
Store
.
.
.
.
.
.
.
.
. 236
Data
Store
Initialization
Statements
.
.
.
.
. 236
Set
UP
Controller/Tracker
Initialization
Statements
.
.
.
.
.
.
.
.
.
.
.
.
. 237
Activating
the
Data
Store
.
.
.
.
.
.
.
.
. 237
Chapter
8.
Miscellaneous
Customization
.
.
.
.
.
.
.
.
.
.
. 239
Customizing
Tivoli
Workload
Scheduler
for
z/OS
Messages
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. 239
Customizing
Tivoli
Workload
Scheduler
for
z/OS
Panels
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. 240
Customizing
Ended-in-error-list
and
Ready-list
Default
Layouts
.
.
.
.
.
.
.
.
.
.
.
. 241
Invoking
Hiperbatch
Support
.
.
.
.
.
.
.
. 241
Monitoring
Special
Resources
through
RODM
.
. 242
Creating
Case-Code-Definition
Modules
.
.
.
. 244
Invoking
the
Data
Set
Deletion
Utility
.
.
.
.
. 245
Part
2.
Data
Integrity
.
.
.
.
.
.
. 247
Chapter
9.
Backup
and
Recovery
of
Data
Sets
.
.
.
.
.
.
.
.
.
.
.
.
. 249
Backup
Procedures
.
.
.
.
.
.
.
.
.
.
. 249
How
Tivoli
Workload
Scheduler
for
z/OS
Manages
Recovery
of
the
Current
Plan
.
.
.
.
.
.
.
. 250
Current-plan
Recovery
Principles
.
.
.
.
.
. 250
Current-plan
Recovery
Processing
.
.
.
.
. 252
Current-plan
Processing
at
Tivoli
Workload
Scheduler
for
z/OS
Startup
.
.
.
.
.
.
.
. 253
Avoiding
Corruption
of
the
Current
Plan
Backup
.
.
.
.
.
.
.
.
.
.
.
.
.
. 254
iv
Tivoli
Workload
Scheduler
for
z/OS
Customization
and
Tuning
||||||||
Restoring
a
Damaged
Tivoli
Workload
Scheduler
for
z/OS
File
from
Backup
.
.
.
.
.
.
.
.
. 255
Restoring
the
Workstation
Description
(WS)
Data
Set
.
.
.
.
.
.
.
.
.
.
.
.
.
. 255
Restoring
the
Application
Description
(AD)
Data
Set
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. 256
Restoring
the
Operator
Instruction
(OI)
Data
Set
256
Restoring
the
Special
Resource
Description
(RD)
Data
Set
.
.
.
.
.
.
.
.
.
.
.
.
.
. 256
Restoring
the
Side
Information
(SI)
Data
Set
.
. 256
Restoring
the
Long-term
Plan
(LTP)
Data
Set
257
Restoring
the
JCL
Repository
(JS)
Data
Set
.
.
. 257
Re-creating
the
Current
plan
from
the
Long-term
Plan
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. 257
Re-creating
the
Current
Plan
from
the
New-current-plan
and
the
JT
Archive
Log
.
.
.
. 258
Recovering
from
Errors
on
the
Job-Tracking
Log
259
Dual
JT
Log
data
set
Problems
.
.
.
.
.
.
. 259
Recovering
from
Errors
on
the
JT
Archive
Log
.
. 259
Recovering
from
Errors
on
the
Checkpoint
Data
Set
260
Recovering
from
Errors
on
an
Event
Data
Set
.
. 261
Recovering
from
Errors
on
a
Submit/Release
Data
Set
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. 261
Recovering
from
Errors
on
the
Current-plan-extension
Data
Set
.
.
.
.
.
.
. 261
Automatic
Recovery
from
Controller
Failures
.
.
. 262
Notification
of
Controller
Failures
.
.
.
.
. 263
Re-creating
the
Symphony
file
from
the
Current
Plan
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. 263
Chapter
10.
Cleanup
and
Recovery
of
Data
Store
Data
Sets
.
.
.
.
.
.
.
. 265
Deleting
Data
from
the
Database
.
.
.
.
.
.
. 265
Exporting
Data
to
a
Backup
File
.
.
.
.
.
.
. 266
Importing
Data
from
a
Backup
File
.
.
.
.
.
. 266
Recovering
from
Failure
.
.
.
.
.
.
.
.
.
. 267
What
to
Do
when
Data
Files
Fill
Up
.
.
.
.
.
. 267
Cleanup
Subtask
.
.
.
.
.
.
.
.
.
.
.
. 268
Chapter
11.
Disaster
Recovery
Planning
.
.
.
.
.
.
.
.
.
.
.
.
. 269
Designing
your
Tivoli
Workload
Scheduler
for
z/OS
DRP
.
.
.
.
.
.
.
.
.
.
.
.
.
. 269
Secondary-center
Options
.
.
.
.
.
.
.
. 269
Standardizing
the
Environment
.
.
.
.
.
. 270
Implementing
your
Tivoli
Workload
Scheduler
for
z/OS
DRP
.
.
.
.
.
.
.
.
.
.
.
.
.
. 271
Recovery
to
Start-of-day
Processing
.
.
.
.
. 271
Recovery
to
a
Predefined
Recovery
Point
.
.
. 274
Recovery
to
Point-of-failure
.
.
.
.
.
.
. 276
Part
3.
Open
Systems
Integration
281
Chapter
12.
End-to-end
Scheduling
283
Overview
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. 283
The
End-to-end
Environment
.
.
.
.
.
.
.
. 283
Distributed
Agents
.
.
.
.
.
.
.
.
.
. 283
Tivoli
Workload
Scheduler
Domains
.
.
.
.
. 284
End-to-end
Scheduling
Architecture
.
.
.
.
. 284
Setting
the
Customization
Parameters
.
.
.
. 286
Configuring
the
SCRPTLIB
.
.
.
.
.
.
.
. 287
Configuring
for
Sysplex
.
.
.
.
.
.
.
.
. 290
Controlling
the
Distributed
Plan
.
.
.
.
.
.
. 290
Controlling
the
Plan
with
Conman
.
.
.
.
. 290
Controlling
the
Plan
with
the
Tivoli
Job
Scheduling
Console
.
.
.
.
.
.
.
.
.
. 291
Conventions
Used
for
the
End-to-end
Scheduling
Plan
.
.
.
.
.
.
.
.
.
.
. 292
Tracing
the
Additional
Processes
on
Open
Edition
293
Migrating
from
a
Tracker
Agent
to
a
Distributed
Agent
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. 293
Migrating
Backwards
.
.
.
.
.
.
.
.
.
. 294
Chapter
13.
Open
Systems
Integration
295
Controlling
Heterogeneous
Systems
.
.
.
.
.
. 295
Setting
Up
the
Environment
.
.
.
.
.
.
. 296
Submitting
and
Tracking
the
Workload
.
.
.
. 297
An
Alternate
Method
for
Controlling
VM
Processing
.
.
.
.
.
.
.
.
.
.
.
.
.
. 297
Method
of
Use
.
.
.
.
.
.
.
.
.
.
.
. 298
Part
4.
Tuning
.
.
.
.
.
.
.
.
.
. 301
Chapter
14.
Analyzing
Performance
303
Setting
Performance
Objectives
.
.
.
.
.
.
. 303
Measuring
Performance
.
.
.
.
.
.
.
.
.
. 304
Performance
Reporter
for
MVS
and
Tivoli
Decision
Support
for
OS/390
.
.
.
.
.
.
. 304
RMF
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. 305
ACF/VTAM
.
.
.
.
.
.
.
.
.
.
.
.
. 306
VSAM
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. 307
Tivoli
Workload
Scheduler
for
z/OS
Performance
Data
.
.
.
.
.
.
.
.
.
.
. 307
Chapter
15.
Basic
Tuning
Activities
309
System
Resources
.
.
.
.
.
.
.
.
.
.
.
. 309
I/O
Activity
.
.
.
.
.
.
.
.
.
.
.
.
. 309
Processor
.
.
.
.
.
.
.
.
.
.
.
.
.
. 313
Processor
Storage
.
.
.
.
.
.
.
.
.
.
. 313
Indicators
for
Performance-related
Problems
.
.
. 314
Preventing
Bottlenecks
.
.
.
.
.
.
.
.
.
. 314
Chapter
16.
Tuning
the
Controller
and
the
Tracker
.
.
.
.
.
.
.
.
.
.
.
. 315
Tuning
the
Controller
.
.
.
.
.
.
.
.
.
.
. 315
Job
Submission
.
.
.
.
.
.
.
.
.
.
.
. 315
Job
Tracking
.
.
.
.
.
.
.
.
.
.
.
.
. 316
Dialog
Response
.
.
.
.
.
.
.
.
.
.
. 317
Background
Batch
Processing
.
.
.
.
.
.
.
. 318
Recognizing
the
Indicators
.
.
.
.
.
.
.
. 318
Recommendations
.
.
.
.
.
.
.
.
.
.
. 318
Tuning
the
Tracker
.
.
.
.
.
.
.
.
.
.
. 318
Event
Creation
and
Communication
.
.
.
.
. 319
Factors
Influencing
Performance
.
.
.
.
.
. 319
JCC
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. 320
Restart
and
Cleanup
.
.
.
.
.
.
.
.
.
.
. 320
Part
5.
Appendixes
.
.
.
.
.
.
.
. 321
Contents
v
||
|
|
|
|
Appendix
A.
NetView
Generic-alert
Vectors
.
.
.
.
.
.
.
.
.
.
.
.
.
. 323
Subsystem-failed
Alert
.
.
.
.
.
.
.
.
.
. 323
Subtask-failed
Alert
.
.
.
.
.
.
.
.
.
.
. 324
Operation-in-error
Alert
.
.
.
.
.
.
.
.
.
. 324
Late-operation
Alert
.
.
.
.
.
.
.
.
.
.
. 325
Long-duration
Alert
.
.
.
.
.
.
.
.
.
.
. 325
Queue-threshold-exceeded
Alert
.
.
.
.
.
.
. 326
Appendix
B.
Tivoli
Workload
Scheduler
for
z/OS
Macros
.
.
.
.
. 327
Appendix
C.
Sample
Library
(SEQQSAMP)
.
.
.
.
.
.
.
.
.
.
. 329
EQQUSIN
Samples
.
.
.
.
.
.
.
.
.
.
. 331
Tivoli
Workload
Scheduler
for
z/OS
Exits
.
.
.
. 331
Start
or
Stop
Exit
.
.
.
.
.
.
.
.
.
.
. 331
Job-submit
Exit
.
.
.
.
.
.
.
.
.
.
.
. 332
Job-library-read
Exit
.
.
.
.
.
.
.
.
.
. 332
Event-filtering
Exit
.
.
.
.
.
.
.
.
.
. 333
SYSOUT
Archiving
Exit
.
.
.
.
.
.
.
.
. 333
Incident-record-create
Exit
.
.
.
.
.
.
.
. 333
Operation-status-change
Exit
.
.
.
.
.
.
. 333
Operation-initiation
Exit
.
.
.
.
.
.
.
.
. 334
JCL-variable-substitution
Exit
.
.
.
.
.
.
. 334
Job-tracking
Log
Write
Exit
.
.
.
.
.
.
.
. 334
EQQDELDS/EQQCLEAN
Catalog-Exit
.
.
.
. 334
Open
Systems
Integration
.
.
.
.
.
.
.
.
. 335
Tracker
for
VM
.
.
.
.
.
.
.
.
.
.
.
. 335
Tracker
for
OS/2
.
.
.
.
.
.
.
.
.
.
. 336
Tracker
for
AIX
.
.
.
.
.
.
.
.
.
.
.
. 337
Tivoli
Workload
Scheduler
for
z/OS
Audit
Package
337
Viewing
Output
from
the
Ended-in-error
List
.
.
. 340
NetView
Samples
.
.
.
.
.
.
.
.
.
.
.
. 340
Deadline
WTO
Message
.
.
.
.
.
.
.
.
. 340
Responding
to
WTO
Operations
.
.
.
.
.
. 341
Changing
Operation
Status
from
NetView
.
.
. 341
z/OS
Hiperbatch
Support
.
.
.
.
.
.
.
.
. 341
Deleting
data
sets
based
on
JCL
Disposition
and
Catalog
Status
.
.
.
.
.
.
.
.
.
.
.
.
. 341
Miscellaneous
Samples
.
.
.
.
.
.
.
.
.
. 342
MASS
Update
Samples
.
.
.
.
.
.
.
.
.
. 342
Notices
.
.
.
.
.
.
.
.
.
.
.
.
.
. 343
Trademarks
.
.
.
.
.
.
.
.
.
.
.
.
.
. 344
Glossary
.
.
.
.
.
.
.
.
.
.
.
.
. 345
Index
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. 357
vi
Tivoli
Workload
Scheduler
for
z/OS
Customization
and
Tuning
Preface
This
book
shows
you
how
to
install,
customize,
or
tune
Tivoli®®
Workload
Scheduler
for
z/OS™™.
You
can
use
this
book
for
reference
during
installation.
Your
workload
can
run
on
various
platforms,
but
you
control
it
from
a
central
z/OS
system
that
runs
the
Tivoli
Workload
Scheduler
for
z/OS
controller.
The
term
the
scheduler,
when
used
in
this
book,
refers
to
Tivoli
Workload
Scheduler
for
z/OS.
The
term
DB2®,
when
used
in
this
book,
also
applies
to
DATABASE2
and
DB2
Universal
Database™.
The
term
z/OS
is
used
in
this
guide
to
mean
z/OS
and
OS/390®
operating
systems.
Where
the
term
OS/390
appears,
the
related
information
applies
only
to
OS/390
operating
systems.
Maintenance
Release
This
is
a
maintenance
refresh
of
the
corresponding
IBM
Tivoli
Workload
Scheduler
for
z/OS
Version
8.1
manual,
form
number
SH19–4544–00.
It
contains
updates
for
the
following
APARS:
v
56193
v
56563
v
57606
v
58625
v
58860
v
61238
v
62198
v
63396
v
63594
v
65556
v
65694
v
65970
v
66373
v
67472
v
68038
v
68074
v
68675
v
68995
v
73699
v
73841
v
75982
Throughout
the
book,
the
changed
or
new
sections
are
marked
by
revision
bars.
The
name
of
the
APAR
causing
the
information
change
is
also
featured
within
the
vii
|
|||
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
||
changed
chapter,
section,
or
paragraph.
If
your
version
of
the
product
has
not
been
fixed
for
a
particular
APAR,
refer
to
the
original
version
of
the
manual
for
the
corresponding
information.
Who
Should
Read
This
Guide
This
book
is
intended
for
system
programmers,
security
administrators,
and
other
personnel
who
install,
customize,
or
tune
Tivoli
Workload
Scheduler
for
z/OS.
To
use
this
book
effectively,
you
need
a
working
knowledge
of
z/OS
and
JES
concepts
and
facilities.
You
should
be
familiar
with
the
Interactive
System
Productivity
Facility
(ISPF),
the
Interactive
System
Productivity
Facility/Program
Development
Facility
(ISPF/PDF),
and
the
Time-Sharing
Option
(TSO).
A
good
working
knowledge
of
Virtual
Storage
Access
Method
(VSAM)
is
desirable
but
not
essential.
To
implement
security,
you
must
know
the
Resource
Access
Control
Facility
(RACF®)
or
a
similar
product.
To
implement
Tivoli
Workload
Scheduler
for
z/OS
exits
or
subroutines,
you
must
know
job
control
language
(JCL)
and
have
a
good
working
knowledge
of
a
programming
language,
for
example,
assembler
or
PL/I.
You
can
use
programming
languages
that
support
OS/390
linkage
conventions
and
that
can
load
and
delete
an
assembler
program.
What
This
Guide
Contains
This
guide
contains
the
following
sections:
Part
I.
Customizing
Tivoli
Workload
Scheduler
for
z/OS
Part
I
contains
the
following
chapters:
v
Chapter
1,
“Initialization
Statements-Reference,”
on
page
3
Explains
how
you
specify
statements
and
describes
each
statement
in
detail.
v
Chapter
2,
“Identifying
Related
Initialization-Statement
Parameters,”
on
page
123
Helps
you
identify
different
statements
and
parameters
that
you
can
specify
to
implement
a
particular
function.
v
Chapter
3,
“Implementing
Security,”
on
page
133
Describes
procedures
for
maintaining
the
integrity
of
Tivoli
Workload
Scheduler
for
z/OS
user
data
and
applications.
Security
strategy
examples
are
included.
v
Chapter
4,
“Tivoli
Workload
Scheduler
for
z/OS
Exits,”
on
page
159
Describes
the
exits
that
can
be
called
by
a
tracker
and
a
controller.
Your
own
programs
can
use
the
information
passed
by
the
exits
to
perform
a
variety
of
functions.
v
Chapter
5,
“Reporting
Events
to
Tivoli
Workload
Scheduler
for
z/OS,”
on
page
195
Describes
the
Tivoli
Workload
Scheduler
for
z/OS
subroutines
that
you
can
invoke
to
report
events
that
cannot
be
detected
automatically
from
system
exits.
v
Chapter
6,
“Using
the
Job
Completion
Checker,”
on
page
219
Explains
how
you
can
scan
SYSOUT
to
determine
the
success
or
failure
of
a
job,
instead
of
using
only
completion
codes.
v
Chapter
7,
“Using
the
Data
Store,”
on
page
229
Explains
how
to
install
and
use
the
data
store.
v
Chapter
8,
“Miscellaneous
Customization,”
on
page
239
viii
Tivoli
Workload
Scheduler
for
z/OS
Customization
and
Tuning
|||
Describes
how
you
can
tailor
Tivoli
Workload
Scheduler
for
z/OS
by:
–
Customizing
Tivoli
Workload
Scheduler
for
z/OS
messages
–
Customizing
Tivoli
Workload
Scheduler
for
z/OS
panels
–
Customizing
ended-in-error-list
and
ready-list
layouts
–
Invoking
Hiperbatch™
support
–
Creating
case-code-definition
modules
that
are
used
by
automatic
job
recovery.
Part
II.
Data
Integrity
Part
II
contains
the
following
chapters:
v
Chapter
9,
“Backup
and
Recovery
of
Data
Sets,”
on
page
249
Describes
backup
procedures
and
how
you
restore
damaged
files.
v
Chapter
10,
“Cleanup
and
Recovery
of
Data
Store
Data
Sets,”
on
page
265
Explains
how
you
can
clean
up
and
recover
the
data
store
data
sets.
v
Chapter
11,
“Disaster
Recovery
Planning,”
on
page
269
Describes
how
you
can
implement
a
recovery
scenario
to
reduce
the
impact
of
a
major
disruption.
Part
III.
Open
System
Integration
Part
III
contains
the
following
chapter:
v
Chapter
13,
“Open
Systems
Integration,”
on
page
295
Describes
how
you
can
use
Tivoli
Workload
Scheduler
for
z/OS
to
control
the
workload
in
operating
environments
that
do
not
support
a
tracker.
Part
IV.
Tuning
Part
IV
contains
the
following
chapters:
v
Chapter
14,
“Analyzing
Performance,”
on
page
303
Provides
a
general
introduction
to
performance
issues.
v
Chapter
15,
“Basic
Tuning
Activities,”
on
page
309
Describes
system
resources
used
by
Tivoli
Workload
Scheduler
for
z/OS
and
provides
information
to
help
you
perform
basic
tuning.
v
Chapter
16,
“Tuning
the
Controller
and
the
Tracker,”
on
page
315
Describes
how
you
can
tune
Tivoli
Workload
Scheduler
for
z/OS
to
correct
performance
problems.
Part
V.
Appendixes
Part
V
contains
the
following
chapters:
v
Appendix
A,
″Netview
Generic
Alert
Vectors″,
on
page
317
Describes
the
format
of
the
generic
alerts
that
Tivoli
Workload
Scheduler
for
z/OS
sends
to
NetView®.
v
Appendix
B,
“Tivoli
Workload
Scheduler
for
z/OS
Macros,”
on
page
327
Provides
a
list
of
Tivoli
Workload
Scheduler
for
z/OS
macros
that
are
programming
interfaces.
v
Appendix
C,
“Sample
Library
(SEQQSAMP),”
on
page
329
Describes
the
members
of
the
sample
library
that
help
you
customize
and
tune
Tivoli
Workload
Scheduler
for
z/OS.
Preface
ix
Publications
This
section
lists
publications
in
the
Tivoli
Workload
Scheduler
for
z/OS
library
and
any
other
related
documents.
It
also
describes
how
to
access
Tivoli
publications
online,
how
to
order
Tivoli
publications,
and
how
to
make
comments
on
Tivoli
publications.
Publications
for
Tivoli
Workload
Scheduler
for
z/OS
The
following
table
lists
the
publications
in
the
Tivoli
Workload
Scheduler
for
z/OS
library.
Table
1.
List
of
Publications
Task
Publication
Order
number
Planning
Tivoli
Workload
Scheduler
for
z/OS
Licensed
Program
Specifications
GH19-4540
Understanding
the
Tivoli
Workload
Scheduling
Suite
General
Information
GH19-4539
Learning
concepts
and
terminology
Getting
Started
SH19-4542
Using
the
Java™
GUI
Tivoli
Job
Scheduling
Console
User’s
Guide
SH19-4552
Using
the
Java
GUI
Tivoli
Job
Scheduling
Console
Release
Notes
GI10-5781
Interpreting
messages
and
codes
Messages
and
Codes
SH19-4548
Installing
Tivoli
Workload
Scheduler
for
z/OS
Installation
Guide
SH19-4543
Planning
and
scheduling
the
workload
Planning
and
Scheduling
the
Workload
SH19-4546
Controlling
and
monitoring
the
current
plan
Controlling
and
Monitoring
the
Workload
SH19-4547
Writing
application
programs
Programming
Interfaces
SH19-4545
Quick
reference
Quick
Reference
GH19-4541
Diagnosing
failures
Diagnosis
Guide
and
Reference
LY19-6410
Using
LookAt
to
Look
Up
Message
Explanations
LookAt
is
an
online
facility
that
lets
you
look
up
explanations
for
most
messages
you
encounter,
as
well
as
for
some
system
abends
and
codes.
Using
LookAt
to
find
information
is
faster
than
a
conventional
search
because
in
most
cases
LookAt
goes
directly
to
the
message
explanation.
You
can
access
LookAt
from
the
Internet
at:
http://www.ibm.com/eserver/zseries/zos/bkserv/lookat/
or
from
anywhere
in
z/OS
or
z/OS.e
where
you
can
access
a
TSO/E
command
line
(for
example,
TSO/E
prompt,
ISPF,
z/OS
UNIX®
System
Services
running
OMVS).
The
LookAt
Web
site
also
features
a
mobile
edition
of
LookAt
for
devices
such
as
PCs,
Palm
OS,
or
Linux-based
handhelds.
So,
if
you
have
a
handheld
device
with
wireless
access
and
an
Internet
browser,
you
can
now
access
LookAt
message
information
from
almost
anywhere.
x
Tivoli
Workload
Scheduler
for
z/OS
Customization
and
Tuning
|
||||
||||
||||
http://www.ibm.com/eserver/zseries/zos/bkserv/lookat/
To
use
LookAt
as
a
TSO/E
command,
you
must
have
LookAt
installed
on
your
host
system.
You
can
obtain
the
LookAt
code
for
TSO/E
from
a
disk
on
your
(SK3T-4270)
or
from
the
LookAt
Web
site’s
Download
link.
Accessing
Publications
Online
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.
The
Tivoli
Software
Information
Center
is
located
at
the
following
Web
address:
http://publib.boulder.ibm.com/tividd/td/tdprodlist.html
Click
the
Tivoli
Workload
Scheduler
for
z/OS
link
to
access
the
product
library.
Note:
If
you
documents
on
other
than
letter-sized
paper,
select
the
Fit
to
page
check
box
in
the
Adobe
Acrobat
dialog.
This
option
is
available
when
you
click
File
→
Print.
Fit
to
page
ensures
that
the
full
dimensions
of
a
letter-sized
page
on
the
paper
that
you
are
using.
Softcopy
Collection
Kit
All
the
books
in
the
Tivoli
Workload
Scheduler
for
z/OS
library,
except
the
licensed
publications,
are
available
in
displayable
softcopy
form
on
CD-ROM
in
the
following
Softcopy
Collection
Kit:
v
OS/390,
SK2T-6951
You
can
read
the
softcopy
books
on
CD-ROMs
using
these
IBM®
licensed
programs:
v
Softcopy
Reader
v
BookManager®
READ/2
v
BookManager
READ/DOS
v
BookManager
READ/6000
All
the
BookManager
programs
need
a
personal
computer
equipped
with
a
CD-ROM
disk
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
documentation
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
In
other
countries,
see
the
following
Web
site
for
a
list
of
telephone
numbers:
http://www.ibm.com/software/tivoli/order-lit/
Preface
xi
|||
|
||||
|
|
||||
|
||||
||||||
|||||
|
|
|
|||
|
|
|
|
|
http://publib.boulder.ibm.com/tividd/td/tdprodlist.htmlhttp://www.elink.ibmlink.ibm.com/public/applications/publications/cgibin/pbi.cgihttp://www.ibm.com/software/tivoli/order-lit/
Providing
Feedback
about
Publications
If
you
have
comments
or
suggestions
about
Tivoli
products
and
documentation,
complete
the
customer
feedback
survey
at
the
following
Web
site:
http://www.ibm.com/software/sysmgmt/products/support
Contacting
IBM
Software
Support
If
you
have
a
problem
with
any
Tivoli
product,
you
can
contact
IBM
Software
Support.
See
the
IBM
Software
Support
Guide
at
the
following
Web
site:
http://techsupport.services.ibm.com/guides/handbook.html
The
guide
provides
information
about
how
to
contact
IBM
Software
Support,
depending
on
the
severity
of
your
problem,
and
the
following
information:
v
Registration
and
eligibility
v
Telephone
numbers
and
addresses,
depending
on
the
country
in
which
you
are
located
v
Information
you
must
have
before
contacting
IBM
Software
Support
Conventions
Used
in
This
Guide
The
guide
uses
several
typeface
conventions
for
special
terms
and
actions.
These
conventions
have
the
following
meanings:
Information
type
Style
convention
Example
Commands
All
capital
letters
CREATE
References
in
the
text
to
fields
on
panels
All
capital
letters
QUANTITY
Input
you
should
type
in
panel
fields
Monospace
MYAPPLICATION
First
time
new
term
introduced
Italics
Application
How
to
Read
Syntax
Diagrams
Throughout
this
book,
syntax
is
described
in
diagrams
like
the
one
shown
here,
which
describes
the
SRSTAT
TSO
command:
��
SRSTAT
'
resource
name
'
OPCA
SUBSYS(
subsystem
name
)
MSTR
�
�
KEEP
AVAIL(
RESET
)
NO
YES
KEEP
DEVIATION(
amount
)
RESET
�
xii
Tivoli
Workload
Scheduler
for
z/OS
Customization
and
Tuning
|
||
|
|
||
|
||
|
||
|
http://www.ibm.com/software/sysmgmt/products/supporthttp://techsupport.services.ibm.com/guides/handbook.html
�
KEEP
QUANTITY(
amount
)
RESET
YES
CREATE(
NO
)
�
�
0
TRACE(
trace
level
)
��
The
symbols
have
these
meanings:
��─────
The
statement
begins
here.
──────�
The
statement
is
continued
on
the
next
line.
�──────
The
statement
is
continued
from
a
previous
line.
─────��
The
statement
ends
here.
Read
the
syntax
diagrams
from
left
to
right
and
from
top
to
bottom,
following
the
path
of
the
line.
These
are
the
conventions
used
in
the
diagrams:
v
Required
items
appear
on
the
horizontal
line
(main
path):
��
STATEMENT
required
item
��
v
Optional
items
appear
below
the
main
path:
��
STATEMENT
optional
item
��
v
An
arrow
returning
to
the
left
above
the
item
indicates
an
item
that
you
can
repeat.
If
a
separator
is
required
between
items,
it
is
shown
on
the
repeat
arrow.
��
STATEMENT
'
,
repeatable
item
��
v
If
you
can
choose
from
two
or
more
items,
they
appear
vertically
in
a
stack.
–
If
you
must
choose
one
of
the
items,
one
item
of
the
stack
appears
on
the
main
path:
��
STATEMENT
required
choice
1
required
choice
2
��
–
If
choosing
one
of
the
items
is
optional,
the
entire
stack
appears
below
the
main
path:
Preface
xiii
��
STATEMENT
optional
choice
1
optional
choice
2
��
–
A
repeat
arrow
above
a
stack
indicates
that
you
can
make
more
than
one
choice
from
the
stacked
items:
��
STATEMENT
'
,
optional
choice
1
optional
choice
2
optional
choice
3
��
��
STATEMENT
'
,
required
choice
1
required
choice
2
required
choice
3
��
v
Parameters
that
are
above
the
main
line
are
default
parameters:
��
STATEMENT
default
alternative
��
v
Keywords
appear
in
uppercase
(for
example,
STATEMENT).
v
Parentheses
and
commas
must
be
entered
as
part
of
the
command
syntax,
as
shown.
v
For
complex
commands,
the
item
attributes
might
not
fit
on
one
horizontal
line.
If
that
line
cannot
be
split,
the
attributes
appear
at
the
bottom
of
the
syntax
diagram:
��
STATEMENT
required
choice
1
option
1
option
2
required
choice
2
required
choice
3
��
option
1
default
optional
choice
1(
alternative
)
option
2
default
optional
choice
2(
alternative
)
xiv
Tivoli
Workload
Scheduler
for
z/OS
Customization
and
Tuning
Part
1.
Customizing
Tivoli
Workload
Scheduler
for
z/OS
1
2
Tivoli
Workload
Scheduler
for
z/OS
Customization
and
Tuning
Chapter
1.
Initialization
Statements-Reference
This
chapter
describes
the
initialization
statements
that
Tivoli
Workload
Scheduler
for
z/OS
uses.
It
provides
information
about
specifying
the
statements,
and
then
describes
each
statement
in
detail.
The
statements
are
listed
in
alphabetical
order.
Diagrams
describe
the
syntax
of
each
statement.
See
“How
to
Read
Syntax
Diagrams”
on
page
xii.
Specifying
the
Statements
The
initialization
statements
determine
the
tasks
that
Tivoli
Workload
Scheduler
for
z/OS
starts,
how
Tivoli
Workload
Scheduler
for
z/OS
processes
work,
and
the
functions
that
you
can
use.
This
chapter
describes
the
syntax
rules
for
creating
statements,
where
you
store
the
statements,
and
the
statements
you
can
select
for
a
tracker
and
a
controller.
Creating
the
Statements
Each
statement
consists
of
a
statement
name,
keywords,
and
keyword
values,
and
follows
TSO
command
syntax
rules.
When
you
specify
Tivoli
Workload
Scheduler
for
z/OS
initialization
statements,
follow
these
rules:
v
Statement
data
must
be
in
columns
1
through
72.
Information
in
columns
73
through
80
is
ignored.
v
A
statement
cannot
exceed
455
records.
v
A
blank
or
comma
serves
as
the
delimiter
between
two
keywords;
if
you
supply
more
than
one
delimiter,
the
extra
delimiters
are
ignored.
v
Values
for
keywords
are
contained
within
parentheses.
If
a
keyword
can
have
multiple
values,
the
list
of
values
must
be
separated
by
valid
delimiters.
Delimiters
are
not
allowed
between
a
keyword
and
the
left
parenthesis
of
the
specified
value.
v
Some
keywords
have
multiple
values.
If
you
want
to
use
the
default
for
a
value
that
occurs
before
the
one
you
are
specifying
explicitly,
use
the
delimiter
shown
in
the
keyword
syntax.
For
example,
if
you
specify
TRACK(READYFIRST)
on
the
JTOPTS
statement,
the
default
ALL
is
used
for
the
first
value.
v
Type
/*
to
start
a
comment
and
*/
to
end
a
comment.
A
comment
can
span
record
images
in
the
parameter
member
and
can
appear
anywhere
except
in
the
middle
of
a
keyword
or
a
specified
value.
v
Only
comment
statements
can
appear
before
the
statement
name
on
a
record.
v
A
statement
continues
until
the
next
statement
or
until
the
end
of
records
in
the
member.
Continuation
characters
are
not
used
to
define
a
statement
that
spans
parameter
records.
v
You
can
abbreviate
keywords
to
the
smallest
unambiguous
length
in
the
current
statement.
Statement
names
cannot
be
abbreviated.
Notes:
1.
If
an
abbreviation
matches
more
than
one
keyword
on
a
statement,
Tivoli
Workload
Scheduler
for
z/OS
writes
to
the
message
log
the
TSO-parser
message
IKJ56704I
parameter
IS
AMBIGUOUS.
This
can
cause
a
subtask
to
end
or
Tivoli
Workload
Scheduler
for
z/OS
itself
to
end.
3
2.
The
names
of
RODM
classes,
objects,
and
fields
are
case-sensitive.
Ensure
you
preserve
the
case
if
you
specify
RODMOPTS
statements
in
the
parameter
library.
Also,
if
a
name
contains
anything
other
than
alphanumeric
or
national
characters,
you
must
enclose
the
name
in
double
quotation
marks.
Storing
the
Statements
Tivoli
Workload
Scheduler
for
z/OS
initialization
statements
are
kept
in
a
parameter
library
that
is
identified
by
the
EQQPARM
DD
statement
in
the
JCL
procedure.
This
library
is
a
partitioned
data
set
with
a
logical
record
length
of
80
bytes.
When
you
start
Tivoli
Workload
Scheduler
for
z/OS,
a
member
in
the
library
containing
initialization
statements
is
read.
This
member
is
identified
by
the
PARM
parameter
on
the
EXEC
PGM=EQQMAJOR
statement
in
the
JCL
procedure
and
can
contain:
ALERTS,
APPCROUT,
AUDIT,
AUTHDEF,
DBCSOPTS,
EXITS,
FLOPTS,
INTFOPTS,
JTOPTS,
NOERROR,
OPCOPTS,
RCLOPTS,
RCLDSNP,
RCLDDP,
RESOPTS,
ROUTOPTS,
TRROPTS,
XCFOPTS.
Each
of
these
statement
names
must
be
specified
in
separate
members
of
the
library:
AROPTS,
BATCHOPT,
ERDROPTS,
EWTROPTS,
JCCOPTS,
RODMOPTS.
You
specify
RESOURCE
statements
in
the
same
library
member
as
BATCHOPT.
If
you
specify
DBCSOPTS
in
the
main
member,
also
specify
this
statement
in
the
same
library
member
as
BATCHOPT.
You
specify
the
other
member
names
on
the
OPCOPTS
statement.
Overriding
the
EQQPARM
Statements
When
you
are
using
the
Tivoli
Workload
Scheduler
for
z/OS
program
interface
(PIF),
you
can
specify
a
second
parameter
file
in
the
EQQYPARM
DD
statement
in
the
JCL
of
the
PIF
application.
This
can
be
a
member
of
a
partitioned
data
set
or
a
sequential
file.
EQQYPARM
contains
an
initialization
statement,
INIT,
that
overrides
values
set
by
the
INTFOPTS
statement
in
EQQPARM.
Selecting
Statements
for
the
Tracker
and
Controller
The
statements
that
you
define
determine
the
Tivoli
Workload
Scheduler
for
z/OS
functions
that
you
can
use.
Table
2
shows
which
statements
you
can
define
for
a
tracker
and
a
controller.
You
specify
the
controller
statements
for
a
standby
controller.
Table
2.
Selecting
Initialization
Statements
for
the
Tracker
and
Controller
Name
Tracker
Controller
Specifies
options
for
ALERTS
U
U
Generating
NetView,
message
log,
and
WTO
alerts
APPCROUT
U
Routing
options
for
APPC-connected
tracker
agents
AROPTS
U
Automatic
job
recovery
AUDIT
U
Creating
audit
information
for
changes
to
Tivoli
Workload
Scheduler
for
z/OS
data
AUTHDEF
U
U
Security
checking
DBCSOPTS
U
Japanese
language
feature
ERDROPTS
U
U
Event
reader
task
EWTROPTS
U
Event
writer
task
4
Tivoli
Workload
Scheduler
for
z/OS
Customization
and
Tuning
Table
2.
Selecting
Initialization
Statements
for
the
Tracker
and
Controller
(continued)
Name
Tracker
Controller
Specifies
options
for
EXITS
U
U
Calling
Tivoli
Workload
Scheduler
for
z/OS
exits
FLOPTS
U
Communicating
with
data
store
(allowing
joblog
retrieval
and
restart
and
cleanup
funcions)
INCLUDE
U
NOERROR
table
definition
members
INTFOPTS
U
Requests
from
programming
interfaces
(required)
JCCOPTS
U
Job
completion
checker
task
JTOPTS
U
Determining
how
operations
behave
at
workstations
and
how
they
are
submitted
and
tracked
NOERROR
U
Treating
job-tracking
error
codes
as
normal
completion
codes
OPCOPTS
U
U
Starting
Tivoli
Workload
Scheduler
for
z/OS
subtasks
RCLOPTS
U
Defining
the
options
used
during
the
restart
and
cleanup
functions
RCLDSNP
U
Listing
protected
data
set
name
RCLDDP
U
Listing
protected
DDnames
RESOPTS
U
Controlling
special
resources
RODMOPTS
U
Monitoring
special
resources
through
RODM
ROUTOPTS
U
Communication
routes
to
tracker
destinations
TRROPTS
U
The
communication
route
to
the
controller
XCFOPTS
U
U
XCF
communications
Other
Initialization
Statements
Table
2
on
page
4
shows
initialization
statements
that
you
define
for
a
tracker
and
controller.
Other
initialization
statements
include:
BATCHOPT
specifies
options
for
all
batch
jobs.
CPUREC
specifies
the
configuration
options
for
a
fault-tolerant
workstation
DOMREC
defines
a
domain
for
distibuted
agents
network
DSTOPTS
specifies
options
for
the
data
store
DSTUTIL
specifies
options
for
data
store
batch
utilities
and
the
CleanUp
subtask
INIT
specifies
run-time
options
for
processing
requests
from
a
PIF
application
and
TCP/IP
server
RESOURCE
specifies
for
which
special
resources
daily
planning
should
produce
reports.
SERVOPTS
specifies
options
for
a
server
Chapter
1.
Initialization
Statements-Reference
5
USRREC
specifies
the
user
id
and
password
to
be
used
for
the
operations
running
on
fault-tolerant
workstations
TOPOLOGY
specifies
configuration
options
for
the
end-to-end
feature
The
following
sections
of
this
chapter
describe
each
initialization
statement.
6
Tivoli
Workload
Scheduler
for
z/OS
Customization
and
Tuning
ALERTS
Purpose:
The
ALERTS
statement
specifies
the
conditions
under
which
Tivoli
Workload
Scheduler
for
z/OS
should
generate
an
alert.
You
can
specify
this
statement
for
a
tracker,
controller,
or
standby
controller.
You
can
use
these
alert
actions
when
an
alert
condition
occurs:
v
Send
a
generic
alert
to
NetView.
v
Write
a
message
to
the
Tivoli
Workload
Scheduler
for
z/OS
message
log.
v
Generate
a
WTO
(write-to-operator)
message.
ALERTS
is
defined
in
the
member
of
the
EQQPARM
library
as
specified
by
the
PARM
parameter
on
the
JCL
EXEC
statement.
Syntax:
��
ALERTS
�
�
'
,
GENALERT(
DURATION
)
ERROROPER
NETVALRT
LATEOPER
RECEIVERID(
Alert
Receiver
ID
)
OPCERROR
QLIMEXCEED
�
�
'
OPCERROR
,
MLOG(
DURATION
)
ERROROPER
LATEOPER
QLIMEXCEED
RESCONT
'
,
WTO(
DURATION
)
ERROROPER
LATEOPER
OPCERROR
QLIMEXCEED
RESCONT
��
Parameters:
GENALERT(error
condition,...,error
condition)
Defines
the
conditions
under
which
Tivoli
Workload
Scheduler
for
z/OS
should
send
a
generic
alert
to
NetView.
RECEIVERID(Alert
Receiver
ID|NETVALRT)
Defines
the
NetView
alert
receiver
that
generic
alerts
are
sent
to.
Specify
this
keyword
if
the
alert
receiver
in
NetView
address
space
that
handles
Tivoli
Workload
Scheduler
for
z/OS
alert
automation
does
not
have
the
NetView
default
ID,
NETVALRT.
MLOG(error
condition,...,error
condition|OPCERROR)
Defines
the
conditions
under
which
Tivoli
Workload
Scheduler
for
z/OS
should
write
a
message
to
the
message
log.
WTO(error
condition,...,error
condition)
Defines
the
conditions
under
which
Tivoli
Workload
Scheduler
for
z/OS
should
generate
a
write-to-operator
(WTO)
message.
Error
Conditions:
You
can
specify
one
or
more
of
the
following
error
conditions
for
each
alert
type.
Note
that
only
OPCERROR
and
QLIMEXCEED
are
applicable
to
a
tracker;
other
error
conditions
are
ignored
if
you
specify
them.
DURATION
The
alert
action
is
taken
when
an
operation
in
the
current
plan
is
active
for
Chapter
1.
Initialization
Statements-Reference
7
an
unexpectedly
long
time.
This
means
that
an
operation
that
has
started
(extended
status
S)
must
be
active
longer
than
its
estimated
duration
multiplied
by
the
feedback
limit
divided
by
100.
For
example,
if
an
operation
has
an
estimated
duration
of
10
minutes
and
the
limit
for
feedback
is
200,
the
alert
action
is
taken
if
the
operation
is
active
for
longer
than
20
minutes.
The
alert
action
is
also
taken
if
the
operation
has
been
![Tivoli Workload Scheduler - IBMpublib.boulder.ibm.com/tividd/td/TWS/SH19-4557-00/ja_JA/PDF/SH19... · ^(,-vii \qNP]IT ..... vii \qNbF ..... vii](https://static.documents.pub/doc/80x56/5bb8a65f09d3f2931b8c6ca1/tivoli-workload-scheduler-vii-qnpit-vii-qnbf-vii.jpg)
