Problem: Loss of group buffer pool structure (duplexed)

In your data sharing environment, you might encounter an error that is caused by the loss of a duplexed group buffer pool structure.

System action

The following messages will appear if the secondary group buffer pool structure is lost:

DSNB743 csect-name DUPLEXING IS BEING STOPPED FOR GROUP BUFFER POOL gbpname
			FALLING BACK TO PRIMARY,
			REASON = STRFAILSEC
			DB2 REASON CODE = xxxxxxxx

DSNB745 csect-name THE TRANSITION BACK TO SIMPLEX MODE HAS COMPLETED FOR
        GROUP BUFFER POOL gbpname

The following messages will appear if the primary group buffer pool structure is lost:

DSNB744 csect-name DUPLEXING IS BEING STOPPED FOR GROUP BUFFER POOL gbpname
			SWITCHING TO SECONDARY,
			REASON = STRFAILPRI
			DB2 REASON CODE = xxxxxxxx

DSNB745 csect-name THE TRANSITION BACK TO SIMPLEX MODE HAS COMPLETED FOR
        GROUP BUFFER POOL gbpname

System programmer action

No action is required at this time.

If there are 2 coupling facilities originally: When the CF that failed is brought back online, the structures will duplex themselves automatically if DUPLEX(ENABLED) was specified as recommended in the CFRM policy.

If there are more than 2 coupling facilities specified in the preference list of the CFRM policy for the structure: The structure will duplex itself using the remaining coupling facilities if DUPLEX (ENABLED) was specified in the structure statement of the CFRM policy.

After all coupling facilities have been restored to service, you should issue the SETXCF START,REALLOCATE at a low time of activity, to ensure that the group buffer pools are restored to their preferred coupling facilities.