Sysplex Problem Detection and Recovery (SPDR) storage messages

Critical storage shortages for CSM, ECSA, or PRIVATE are always detected by SPDR. Storage failures (when GLOBALCONFIG LIMITS values are not coded) are detected only when an allocation in the Sysplex code fails.

Sysplex Problem Detection and Recovery (SPDR) issues one of the following messages when a storage request for common, private, or CSM storage cannot be satisfied.

EZD1170E
EZD1187E
EZZ9679E

EZD1170E: tcpstackname WAS NOT ABLE TO GET TCP/IP storagetype STORAGE
When the TCP/IP profile GLOBALCONFIG statement ECSALIMIT or POOLLIMIT parameter is not coded, message EZD1170E is issued. In this situation, the storage request fails because ECSA or private storage is exhausted.
EZD1187E: tcpstackname WAS NOT ABLE TO GET TCP/IP storagetype STORAGE
When TCP/IP profile GLOBALCONFIG statement ECSALIMIT or POOLLIMIT is coded, EZD1187E is issued. In this situation the storage request fails because ECSA or private storage is critical.
EZZ9679E: tcpstackname DETERMINED THAT CSM WAS CRITICAL FOR AT LEAST timevalue SECONDS
SPDR issues EZZ9679E when CSM storage problems are detected. This message is issued when CSM storage has been critical for the configured value specified on the GLOBALCONFIG SYSPLEXMONITOR TIMERSECS parameter or the default value of 60 seconds if the parameter is not specified.

See z/OS Communications Server: IP Messages Volume 2 (EZB, EZD) for debug information when these messages are issued. See z/OS Communications Server: IP Configuration Guide for more information about Sysplex Problem Detection and Recovery.