Use the display TCP/IP storage command D TCPIP,,STOR to determine the current status of TCP/IP PRIVATE and ECSA storage. See the information about the DISPLAY TCPIP,,STOR command in z/OS Communications Server: IP System Administrator's Commands for more information about using this command.

Storage limits were set using the GLOBALCONFIG ECSALIMIT or GLOBALCONFIG POOLLIMIT statement. It might be necessary to raise these limits to correct this problem; look for earlier TCP/IP warning messages that are issued each time a storage limit boundary is crossed (OK, CONSTRAINED, CRITICAL, and EXHAUSTED).

See the information about the GLOBALCONFIG statement in z/OS Communications Server: IP Configuration Reference for the definitions of the ECSALIMIT and POOLLIMIT. For ECSA storage exhaustion, it is necessary to determine which jobs or address spaces are using an excessive amount of storage. To determine the users of ECSA storage, common storage tracking should be enabled. See the z/OS MVS Initialization and Tuning Guide for information about requesting common storage tracking. Use the VERBEXIT VSMDATA OWNCOMM SUMMARY command to determine how much storage is used by each job. See the z/OS MVS Diagnosis: Tools and Service Aids for information about the IPCS VERBEXIT VSMDATA command.

If the storage problem cannot be corrected, contact IBM® software support services with all supporting documentation.

If this problem can be corrected, this operator message will be deleted.

If RECOVERY and NOAUTOREJOIN are active, then issue the VARY TCPIP,,SYSPLEX,JOINGROUP command to cause the saved DVIPA definitions to be processed, and the stack to rejoin the TCP/IP sysplex group.

If RECOVERY and AUTOREJOIN are active, no further actions are needed. The stack will process the DVIPA definitions and rejoin the TCP/IP sysplex group.

If NORECOVERY is active, no further actions are needed.