Unsolicited Db2 messages

Unsolicited subsystem messages can be sent to the z/OS® console that issues the START DB2 command. They also can be sent to consoles that have been assigned the routing codes that you listed in the DSNZPxxx module during Db2 installation.

However, the following messages from the IMS and the CICS® attachment facilities are exceptions:

• Specific IMS attachment facility messages are sent to the IMS master terminal.
• Unsolicited CICS messages are sent to the transient data entries that are specified for the MSGQUEUEn(name) attribute in the RDO (resource definition online).
• CICS statistics messages that are issued because of shutdown are sent to the transient data entry that is specified in the RDO (STATSQUEUE).

Some Db2 messages that are sent to the z/OS console are marked as critical with the WTO descriptor code (11). This code signifies critical eventual action requested by Db2. Preceded by an at sign (@) or an asterisk (*), critical Db2 messages remain on the screen until they are specifically deleted. This prevents the messages from being missed by the operator, who is required to take a specific action.