158 IBM Tivoli Workload Scheduler for z/OS Best Practices
6.1.9 EQQUX009 - the operation initiation exit
Tivoli Workload Scheduler for z/OS has supplied trackers for OS/390® systems
and via the end-to-end feature to several other platforms, such as UNIX®.
However, if you wish to schedule batch, controlled by Tivoli Workload Scheduler,
on an unsupported platform, it is possible to write your own code to handle this.
This exit is called when an operation is ready to start, and uses a workstation that
has been defined in the Controller with a USER destination.
Several EQQUX009 samples are supplied with Tivoli Workload Scheduler, one
for each of the following operating systems:
VM, using NJE (EQQUX9N)
OS/2®, using TCP/IP (EQQX9OS2)
AIX, using TCP/IP (EQQX9AIX)
6.1.10 EQQUX011 - the job tracking log write exit
This can be used to write a copy of some (or all) Controller events. It passes
them to a process that will maintain a job-tracking log copy at a remote site, that
may be treated as a disaster recovery site.
The EQQUX011 sample provided by Tivoli Workload Scheduler for z/OS
describes a scenario for setting up an effective disaster recovery procedure.
6.2 EQQaaaaa exits
These exits are called by other processes around Tivoli Workload Scheduler; for
example, EQQUXCAT is called by the EQQDELDS sample.
Table 6-2 on page 159 lists these and the sample or function that uses them.
Attention: If you plan to use the SA/390 “bridge” to Tivoli Workload
Scheduler, you should be aware that this process uses a version of
EQQUX007 which is a driver program that will attempt to call, in turn, modules
called UX007001 through to UX007010. Therefore you should use one of
these (unused) names for your exit code.
Chapter 6. Tivoli Workload Scheduler for z/OS exits 159
Table 6-2 EQQaaaaa Exits
6.2.1 EQQUXCAT - EQQDELDS/EQQCLEAN catalog exit
The exit can be used to prevent the EQQDELDS or EQQCLEAN programs from
deleting specific data sets.
EQQDELDS is provided to tidy up data sets that would cause a not-cataloged 2
error. It is sometimes inserted in jobs by the EQQUX001 or EQQUX002 exits.
EQQCLEAN is called by the Restart & Cleanup function of Tivoli Workload
Scheduler for z/OS when data set cleanup is required before a step restart or
rerun of a job.
The sample EQQUXCAT provided by Tivoli Workload Scheduler for z/OS checks
the data set name to be deleted and prevents deletion if it starts with SYS1.MAC.
6.2.2 EQQDPUE1 - daily planning report exit
Called by the daily planning batch job, this exit enables manipulation of some of
the lines in some of the reports.
6.2.3 EQQUXPIF - AD change validation exit
This exit can be called by the Server or PIF during INSERT or REPLACE AD
action.
The sample EQQUXPIF exit supplied by Tivoli Workload Scheduler for z/OS is a
dummy that needs validation code building, depending on your requirements.
6.2.4 EQQUXGDG - EQQCLEAN GDG resolution exit
This exit prevents EQQCLEAN from simulating a GDG data set when setting up
a job for restart or rerun. This means it does not cause the job to reuse the GDG
data set used previously, but allows it to roll the GDG forward as normal.
Exit Description Used by
EQQUXCAT EQQDELDS/EQQCLEAN Catalog exit EQQDELDS sample or
EQQCLEAN program
EQQDPUE1 Daily Planning Report Daily Planning job
EQQUXPIF Validation of changes done in AD Job Scheduling Console
EQQUXGDG EQQCLEAN GDG resolution exit EQQCLEAN program

Get IBM Tivoli Workload Scheduler for z/OS Best Practices: End-to-end and mainframe scheduling, 2nd Edition now with the O’Reilly learning platform.

O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.