Chapter 4. IBM Tivoli Workload Scheduler Distributed implementation 91
Push method and real-time operations
As discussed earlier, there are two options for moving data from IBM Tivoli
Workload Scheduler to the OnDemand Server: real-time or batch mode. In the
real-time option, the job stdlists will be loaded to the OnDemand Server as soon
as the job completes, provided that the network and OnDemand Server are
available.
Real-time loading requires that the ARSLOAD program be configured as
documented in step 1.d of “Push method and additional requirements” on
page 92. The OnDemand ARSLOAD program is invoked at system startup and
must be running for the loads on the OnDemand Server to occur as soon as the
jobs complete.
Under normal operations, a PUSH-CPU will launch a IBM Tivoli Workload
Scheduler job. This job will execute the modified jobmanrc script that will initiate
scripts that start the load process when the job completes. The scripts will
determine if the OnDemand Server is available; if the server is available, the
job’s stdlist will be loaded onto the OnDemand Server.
If the network is down or the OnDemand Server is unavailable, a link to the
original job stdlist called os_type.stdlist.yyyymmdd.Opid_num.hhmm.log will be
created in the TWShome/stdlist/ondemand directory. These files will be loaded to
the OnDemand Server by the ARSLOAD program that is running in the
background when the OnDemand Server is available.
The Push method is the most efficient method for loading data, since the pushing
of the jobs stdlists is spread over the entire day.
Push method and batch mode operations
The other option for loading data to the OnDemand Server is the batch mode.
When the jobs complete, a link to the original job stdlist called
os_type.stdlist.yyyymmdd.Opid_num.hhmm.log will be created in the
TWShome/stdlist/ondemand directory.
Note: The solution provided for the Push method was designed for UNIX.
Because of the many possible options for shell or programming languages
that can be used to create and run scripts on Windows systems, this solution
did not include converting the UNIX scripts to a format that would work on
Windows. The UNIX scripts may be converted for Windows, in which case the
Windows systems (Master Domain Manager, Backup Master, Domain
Manager, and Fault Tolerant Agent) will then be able to function as
PUSH-CPU. If the scripts are converted, please see the notes in the scripts
that apply to PUSH-CPUs and replace the logic where for variable OS=win-p.