Technical Notes › Regulate the OSF Servers › Establish OSF Server Specifications

Establish OSF Server Specifications

To regulate the OSF servers, set the parameters described in Parameters Regulating TSO Servers in this chapter to the values you want. The CA OPS/MVS product automatically uses these values, after checking their validity, the next time the OSF execute processor receives a new server command.

Validity checking of the parameter values occurs every time the OSF execute processor receives a command intended for a server, to ensure that the parameter values have not changed since the last server command. The first part of the check ensures that the OSFMAX value is not less than the OSFMIN value. If it is less, CA OPS/MVS automatically raises the OSFMAX value to the same value as OSFMIN.

The remaining validity checking observes the following rules:

• When the current number of servers exceeds the OSFMAX value,
  CA OPS/MVS terminates the number of dormant servers that exceed OSFMAX.
• When the current number of servers is less than the OSFMIN value,
  CA OPS/MVS adds the number of new servers required to equal OSFMIN.
• When the current number of servers at least equals the OSFMIN value but is less than the OSFMAX value, and the number of pending (queued) transactions on the OSF execute queue exceeds the threshold set with the OSFQADD parameter, CA OPS/MVS starts one additional server.
• When the current number of servers exceeds the OSFMIN value and is not greater than the OSFMAX value, the server address spaces that have been dormant for the number of seconds specified with the OSFDORM value are terminated if no transactions exist on the OSF execute queue. See Server Termination in this chapter.

Note: All of the information about OSFxxx server parameters in this section applies to the OSFTSLxxx and OSFTSPxxx parameters as well. The USS servers have the equivalents of the OSFRUN and OSFOUTLIM parameters only.