DSNB743I csect-name DUPLEXING IS BEING STOPPED FOR GROUP BUFFER POOL gbpname FALLING BACK TO PRIMARY REASON = reason1 DB2 REASON CODE = reason2
Explanation
Duplexing is being stopped for the named group buffer pool. To stop the duplexing, the secondary group buffer pool will be deallocated, and DB2® will go back to simplex mode on the primary group buffer pool.
- OPERATOR
- The operator initiated an MVS™ command to stop duplexing.
- POLICY
- A new CFRM policy has been activated which specifies DUPLEX(DISABLED) for the group buffer pool.
- LOSSCONNSEC
- One or more of the DB2 members lost connectivity to the secondary group buffer pool structure.
- STRFAILSEC
- The secondary group buffer pool structure failed.
- DB2REASON
- DB2 decided to stop duplexing. The reason code given in reason2 indicates why DB2 stopped duplexing.
- DUPCONNCHG
- Duplexing rebuild stopped because of insufficient connectivity due to a change in the set of connectors.
If reason1 indicates 'DB2REASON', then reason2 specifies a DB2 reason code that indicates why DB2 stopped duplexing. If reason1 is not 'DB2REASON', then reason2 is zero.
This message is issued by each DB2 member connected to the duplexed group buffer pool.
System action
The secondary group buffer pool structure is discarded, and DB2 enters back into simplex mode on the primary group buffer pool structure. If DUPLEX(AUTO) is specified in the active CFRM policy for the group buffer pool, then duplexing will be automatically reinitiated, if duplexing is still possible.
System programmer response
If the rebuild stopped because of "DB2REASON", see the explanation for the reason code given. If duplexing is not automatically reinitiated and duplexing is needed for the group buffer pool, then use the MVS SETXCF command to reestablish duplexing.