USS_MAXSOCKETS_MAXFILEPROC
- Description:
- MAXSOCKETS (AF_INET) and MAXFILEPROC are set high enough
- Reason for check:
- This check will look at the values for MAXSOCKETS and MAXFILEPROC and give an exception message if either is too low. If set too low, you can run out of sockets or file descriptors that can be used. MAXSOCKETS and MAXFILEPROC values will each be compared to 64000 unless the value is overridden in HZSPRMxx.
- z/OS® releases the check applies to:
- z/OS V1R4 and later.
- User override of IBM® value:
- The following sample shows the defaults for customizable values for this check. Use this sample
to make permanent check customizations in an HZSPRMxx parmlib member used at IBM Health Checker for z/OS startup. If you
just want a one-time only update to the check defaults, omit the first line (ADDREPLACE POLICY) and
use the UPDATE statement on a MODIFY hzsproc command. Note that using non-POLICY UPDATE statements
in HZSPRMxx can lead to unexpected results and is therefore not
recommended.
ADDREPLACE POLICY[(policyname)] [STATEMENT(name)] UPDATE CHECK(IBMUSS,USS_MAXSOCKETS_MAXFILEPROC) SEVERITY(LOW) INTERVAL(24:00) PARM('MAXSOCKETS=64000,MAXFILEPROC=64000') DATE('date_of_the_change') REASON('Your reason for making the update.') - Debug support:
- No
- Verbose support:
- No
- Parameters accepted:
- Yes. PARM('MAXSOCKETS=maxsockets,MAXFILEPROC=maxfileproc')
MAXSOCKETS and MAXFILEPROC are required integer values to be compared
with internal values.
- The valid range for MAXSOCKETS is 0 through 16777215.
- The valid range for MAXFILEPROC is 3 through 524287.
You can also specify these parameters without keywords, as PARM('maxsockets,maxfileproc').
- Reference:
- See:
- z/OS MVS System Commands for information on the SETOMVS command.
- z/OS UNIX System Services Planning for information on how to change the MAXSOCKETS and MAXFILEPROC values using the SETOMVS command.
- Messages:
- This check issues the following messages:
- BPXH032E
- BPXH033E
- SECLABEL recommended for multilevel security users:
- SYSLOW. For information about using security labels, see Security labels in z/OS Planning for Multilevel Security and the Common Criteria.