Operations › How to Protect Your System from User Errors in Servers › OSF Safeguards

OSF Safeguards

The OSF provides built-in safeguards to protect against runaway commands, programs, or CLISTs. An OPSOSF address space terminates itself under the following conditions:

• A request consumes too much CPU time. The values of the OSFCPU, OSFTSLCPU, and OSFTSPCPU parameters determine the length of time that is unacceptable for each class of OSF TSO servers.
• A request issues too many PUTLINE requests. The values of the OSFOUTLIM, OSFTSLOUTLIM, and OSFTSPOUTLIM parameters determine the number of PUTLINE requests that are unacceptable for each class of OSF TSO servers.
• A request is in a wait state for too long. The values of the OSFWAIT, OSFTSLWAIT, and OSFTSPWAIT parameters determine the length of time that is unacceptable for each class of OSF TSO servers.
• A request takes too much elapsed time to complete execution. The values of the OSFRUN, OSFTSLRUN, and OSFTSPRUN parameters determine the length of time that is unacceptable for each class of OSF TSO servers.
• A command or program issues a GETLINE request for additional input.
• The OPSMAIN address space terminates.

Note: The OPSRMT command and the OPSCMD command with the SYSID keyword are valid on systems that are not licensed to use the MSF. However, without the MSF you are restricted to specifying an asterisk (*) as the destination system ID for any command you enter. OPSRMT sends commands only to OSF TSO servers.

Since many of the conditions above are related to parameters, you can use the parameters to trace and resolve the related problem.

If possible, the OSF writes messages to OPSLOG and SYSLOG to identify the request that it was executing when a server terminates abnormally.

After an OPSOSF server termination, OSF automatically replaces it by starting another. This is true unless the OPSMAIN address space also came down or some system problem prevents a new OSF server address space from being created.

Notes:

• Users authorized to send commands to other systems must have security profiles defined for them on all such systems. Failure to have all the necessary definitions in place when a command arrives results in security product-dependent error messages.
• CA OPS/MVS assigns all OPSOSF servers SUBMIT and OPER privileges by default.