Руководство Пользователя для Cisco Cisco Tidal Enterprise Scheduler 6.2
25
Cisco Tidal Enterprise Scheduler z/OS Agent and Gateway Adapter Guide
6.2.1 SP3
Chapter 3 Configuring the z/OS Agent
Configuring the z/OS Agent
mvs.filepollint–Dataset Polling Interval
At regular intervals, the z/OS agent polls datasets for dependencies. This option defines the maximum
amount of time (in seconds) between when a dependency exists and when it is recognized by the z/OS
agent. If polling is done too frequently, unnecessary CPU cycles are generated, wasting system
resources. The polling of datasets can be adjusted to an optimal interval for individual systems. The
default value for dataset polling is 15 seconds.
amount of time (in seconds) between when a dependency exists and when it is recognized by the z/OS
agent. If polling is done too frequently, unnecessary CPU cycles are generated, wasting system
resources. The polling of datasets can be adjusted to an optimal interval for individual systems. The
default value for dataset polling is 15 seconds.
Example: mvs.filepollint=15
mvs.jobclass–Releasing held job output
The job output from the z/OS jobs that are run by TES must be stored in the held output queue as
described earlier. Use the mvs.jobclass parameter to release the job output from the held queue. If
not specified, the output remains in the held queue.
described earlier. Use the mvs.jobclass parameter to release the job output from the held queue. If
not specified, the output remains in the held queue.
Example: mvs.jobclass=A
msv.pollint–JCL Polling Interval
Once a job is launched from TES, the z/OS agent monitors the progress of the JCL running in JES. The
frequency of polling by the z/OS agent can be adjusted as needed by changing the polling interval.
Polling more frequently than necessary generates excess CPU cycles and wastes system resources. The
default value for JCL polling is 5 seconds.
frequency of polling by the z/OS agent can be adjusted as needed by changing the polling interval.
Polling more frequently than necessary generates excess CPU cycles and wastes system resources. The
default value for JCL polling is 5 seconds.
Example: mvs.pollint=5
mvs.primary–ISFOUT/TSIOUT Primary Storage
You can designate how much space should be allocated for temporary storage of the job output. If this
storage space fills up, you can designate another storage space as a secondary storage area in tracks. The
msvjob_primary
storage space fills up, you can designate another storage space as a secondary storage area in tracks. The
msvjob_primary
item specifies the size of the primary storage area The primary default storage
space is 0. The default of 0 indicates two cylinders.
Example: mvs.primary=0
mvs.purge–Held Output Disposition
If you want to automatically purge the output of a job from the held output queue after it has been sent
to the master, set the mvs.purge_output option to 1.
to the master, set the mvs.purge_output option to 1.
The default,
0
, is not to purge the output.
Example:
mvs.purge.output=1
mvs.secondary–ISFOUT/TSIOUT Secondary Storage
You can designate how much space should be allocated for temporary storage of the job output if the
output exceeds the primary storage area. The msvjob_secondary item specifies the size of the
secondary storage area in tracks. The default secondary storage space is 0. The default of 0 is currently
one cylinder.
output exceeds the primary storage area. The msvjob_secondary item specifies the size of the
secondary storage area in tracks. The default secondary storage space is 0. The default of 0 is currently
one cylinder.
Example:
mvs.secondary=0
mvs.selclass–Processing Job Output Only from Specific Classes
The agent can be configured to only retrieve job output from designated output classes. A maximum of
32 output classes can be designated. Multiple classes are listed without any separators (as in the example
that lists four classes). If the mvs.jobclass parameter is also specified for the agent, any job output
that is processed from the selected classes specified in this parameter is released and moved to the classes
specified in mvs.jobclass.
32 output classes can be designated. Multiple classes are listed without any separators (as in the example
that lists four classes). If the mvs.jobclass parameter is also specified for the agent, any job output
that is processed from the selected classes specified in this parameter is released and moved to the classes
specified in mvs.jobclass.
Example: mvs.selclass=AH9L