Unexpected messages
Sometimes the first indication of a problem is a message received at the console.
VTAM example
Message DSNL013I VTAM® OPEN ACB FAILED ERROR=90 is received. This message indicates a problem was encountered while DDF was trying to open its ACB.
In this case, an error code of 90 means that VTAM could not find a resource in the VTAM definitions that matches the name in the ACB's APPLID field. This is probably because the application major node is not active. Often an open ACB error is because of the ACB not closing properly when the application was last deactivated. The console log should be checked around the time of the last deactivation for any sign of an error.
TCP/IP example
A Db2 data sharing group consists of 2 members, DB2A and DB2B. These messages appear on the z/OS® console of member DB2B when DDF starts on DB2B:
DSNL512I -DSNB DSNLILNR TCP/IP LISTEN FAILED WITH
RETURN CODE=1115 AND REASON CODE=12E00291
DSNL004I -DSNB DDF START COMPLETE
LOCATION STLEC2
LU USIBMSY.SYEC2B
GENERICLU -NONE
DOMAIN V8EC113.STL.IBM.COM
TCPPORT 446All members of the data sharing group share port number for incoming requests. In this instance, DB2A is already using the port number (446), so DB2B gets error DSNL512I, which indicates that the LISTEN socket call failed. This means that DB2B cannot service incoming connection requests. Db2 retries the LISTEN call every 3 minutes. When DB2A stops, DB2B can use port 446, and Db2 issues message DSNL004I, which indicates that DDF started successfully on DB2B.