The OSFRUN parameter determines how long CA OPS/MVS allows a TSO transaction to execute in an OSF TSO server. This is an elapsed time limit; in comparison, the OSFCPU parameter limits execution time.
When any OSF TSO server transaction exceeds the time limit set by OSFRUN, CA OPS/MVS terminates the server with the hung or looping transaction and starts another server to accept new commands.
120 (seconds)
Any number of seconds between 1 and 604800 (7 days), inclusive
Anytime
Example: OSFRUN
This function sets a 60-second time limit for TSO transactions.
OPSPRM('SET','OSFRUN','60')
Note: The OSF TSO servers are intended to execute relatively short pieces of asynchronous automation. While this parameter does not enforce a maximum transaction runtime value, we strongly recommend that this value not be set higher than 300 seconds (5 minutes). Long-running transactions should be run in OSF TSL servers or in a separate address spaces (either started tasks or batch jobs). Using the OSF TSO servers to execute long running transactions may result in other automation that is time-critical to not execute in a timely fashion, since all of the OSF TSO servers may be busy executing long-running work. It may also result in the OSF TSO execute queue filling up, which in turn may result in transactions being lost.
|
Copyright © 2014 CA.
All rights reserved.
|
|