z/OS MVS Setting Up a Sysplex
Previous topic | Next topic | Contents | Contact z/OS | Library | PDF


Common problems and solutions

z/OS MVS Setting Up a Sysplex
SA23-1399-00

Table 1 provides a reference to identify and solve common problems.

Table 1. Common System-Managed Duplexing Rebuild Problems
Problem Possible Causes Possible Solutions
Format utility (IXCL1DSU) does not recognize SMDUPLEX keyword. Running on a non-z/OS V1R2 system Upgrade system to z/OS® V1R2
System-managed duplexing rebuild is disabled Apply APAR OW41617
Cannot duplex the structure CFRM couple data set not migrated correctly To activate the system-managed duplexing rebuild function, the CFRM couple data set must be migrated. See CFRM parameters for format utility.
CF-to-CF links not defined Two coupling facilities of CFLEVEL=11 or higher with CF-to-CF connectivity are required. Issue the D CF command to determine whether the coupling facilities are remotely connected.
Insufficient coupling facility space If the coupling facility is space constrained, increase the CF storage. If the structure size is not large enough, increase the structure size.
Preference list does not contain appropriate coupling facilities Ensure that the preference list contains at least two coupling facilities of CFLEVEL=11 or higher with CF-to-CF link connectivity.
Structure is allocated in a downlevel coupling facility Rebuild the structure to a CFLEVEL=11 or higher coupling facility
DUPLEX(DISABLED) specified in CFRM policy Check CFRM policy keyword
CFRM policy change is pending for the structure Resolve pending policy change
Exploiter requirements not met Ensure exploiter software is at the correct level
Check messages IXC528I, IXC538I, IXC367I, or IXC574I to determine the actual cause of the problem.  
Structure allocation fails following a CFLEVEL upgrade or CFRM policy change. The CFRM policy SIZE value is substantially larger than the INITSIZE value.

To accommodate the maximum size to which the structure can grow (CFRM policy SIZE value) the CF might have to allocate so much control storage that a structure allocated at the size specified by the policy INITSIZE value has no room for anything else. In particular, the structure might contain an insufficient number of entries and elements for the owning application to use. When SIZE is much larger than INITSIZE, the CF might be unable to allocate a structure with a size of INITSIZE at all.

Increase the INITSIZE (or SIZE, if INITSIZE is not specified) in the CFRM policy until allocation is successful. IBM® recommends that the SIZE value be in a range of 1.5 - 2.0 times the INITSIZE value.

Use the CF Structure Sizer (CFSizer) tool or the Sizer utility to determine the appropriate structure size for the current CFLEVEL. These tools are available at http://www.ibm.com/systems/support/z/cfsizer.

The original (old) structure is not allocated in the “most preferred” coupling facility (according to the preference list). When a structure is a candidate for system-managed duplexing rebuild, the structure allocation algorithm will give preference to coupling facilities at CFLEVEL=11 or higher that have CF-to-CF link connectivity to at least one other coupling facility at CFLEVEL=11 or higher that is also in the preference list and that currently has sufficient space to allocate a secondary instance of the structure. As a result, it is possible that the structure is not allocated in the most preferred coupling facility according to the preference list. For a structure that exploits system-managed duplexing rebuild, consider placing two coupling facilities at CFLEVEL=11 or higher that have CF-to-CF link connectivity to each other at the beginning of the preference list.
The secondary (new) structure is not allocated in the “second most preferred” coupling facility (according to the preference list). The secondary (new) structure must be allocated in a coupling facility at CFLEVEL=11 or higher that has sufficient space and CF-to-CF connectivity to the coupling facility containing the primary (old) structure. If the second most preferred coupling facility does not meet this criteria, another coupling facility in the preference list may be used. Consider placing two coupling facilities at CFLEVEL=11 or higher that have CF-to-CF link connectivity to each other at the beginning of the preference list.
After stopping a system-managed duplexing rebuild, the primary (old) structure is no longer in the “most preferred” coupling facility. When a system-managed duplexing rebuild is stopped with a request to keep the new structure, the new structure becomes the primary structure. As a result, the primary (old) structure may no longer reside in the most preferred coupling facility. If the structure is re-duplexed, the primary (old) will remain where it is and the new structure may wind up in the most preferred coupling facility. If system-managed duplexing rebuilds are started and stopped multiple times, the location of the structures will flip-flop. This is normal. No action required.

Go to the previous page Go to the next page




Copyright IBM Corporation 1990, 2014