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.