|
- 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® values:
- The following shows the default keywords for the check, which
you can override on either a POLICY statement in the HZSPRMxx parmlib
member or on a MODIFY command. This statement may be copied and modified
to override the check defaults:
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.
The default is PARM(' MAXFILESOCKETS=64000,MAXFILEPROC=64000').You
can also specify these parameters without keywords, as PARM('maxsockets,maxfileproc').
- Reference:
- See:
- Messages:
- This check issues the following exception messages:
See the BPXH messages in z/OS MVS System Messages, Vol 3 (ASB-BPX).
- SECLABEL recommended for multilevel security users:
- SYSLOW - see z/OS Planning for Multilevel Security and the Common Criteria for
information on using SECLABELs.
|