Diagnosing platform errors

CICS Explorer and CICSPlex SM provide diagnostic information about platform configuration and operation. The resolution depends on whether the issue surfaced when you create the platform definition, install the platform, or during run time.

Finding diagnostic information about platforms

See Setting up a platform for information about the processing that is involved in setting up a platform.

If an error occurs when you create or install a platform, the installation fails and all resources modified to that point get restored to their original state. Errors are reported in CICS Explorer® and you can use these errors as a starting point for troubleshooting.

CICS Explorer issues the error message CNX0592E for errors that occur when you are creating or installing a platform. This message is always preceded in the Error Log view by a CNX06xxE message that describes the action performed. When you receive message CNX0592E, review the attribute and error information in the message, and review the Error log view to determine the failing command and condition.

CICSPlex® SM issues error messages to the CICSPlex SM output log (the EYULOG) for the maintenance point CMAS.

Look up the error codes for platforms in the PLATDEF Resource Table for platform definitions (PLATDEF), and the PLATFORM Resource Table for PLATFORM resources.

Problems when you create a platform

If you experience a problem when you are creating a platform definition (PLATDEF), check that your specified values are valid:

Check that the platform NAME value is valid. Only alphanumeric, national, and special characters are valid.
Check that the platform directory in zFS has a valid UNIX System Services path. The PLATDIR field uses CICSPlex SM PATH validation to validate the platform directory. In CICS Explorer, click Browse to navigate to a valid path.
For more information, see Platform directory structure in z/OS UNIX and Preparing zFS for platforms.

Problems when you install a platform

If the platform install fails, check the CICSPlex SM output log for the maintenance point CMAS for details of the problem that occurred while the platform was being installed.

Messages beginning with EYUTI are issued when there is a problem with the platform descriptor XML. For example, the XML files might contain region types or CICS regions with duplicate names, or an invalid value might be present in one of the definitions for a created CICS region. The message explains how to correct the problem. When you have checked and fixed the XML files in the platform bundle, export the platform bundle again and retry the platform install.
If your platform bundle cannot be found, check your zFS setup.
- This error can occur when a platform is spread across different systems (LPARs) in the same sysplex, but the platform home directory in the zFS file system is not shared across the sysplex. You must either use FTP by using a connection to the same zFS that your CMAS is running on, or set up sysplex-wide sharing of your platform home directory.
- This error can also occur if you have exported the platform bundle and created the platform home directory on a different sysplex from the sysplex where you are installing the platform. Ensure that the platform home directory is on the sysplex where you are installing the platform.
For more information, see Preparing zFS for platforms .
The CICSPlex SM data repository for the CMAS might be full, in which case you need to increase its size. To expand the data repository, use the REPRO function of the IDCAMS utility. An example of the JCL to do this is in the EYUJXDRP member of the CICSTS55.CPSM.SEYUSAMP library. In that JCL, on the RECORDS(xx,yy) statement, specify a primary (xx) and a secondary (yy) value that are appropriate for your environment. The initial values are 500 and 3000.

If the platform install succeeds, but the enable status of the platform is displayed as INCOMPLETE or EMPTY, there is a problem with the CICS bundles that should be installed with the platform. Investigate the individual CICS bundles that are named in each management part:

If the status of a management part is INVALIDSCOPE, check the definition for the CICS bundle to see whether the target CICS system group was specified correctly.
If the status of a management part is EMPTY, check whether the CICS regions where the CICS bundle should have been installed are active and connected to the CMAS. If the CICS regions are available, check the definition for the CICS bundle for any errors.
Check the CICSMSG log for the CICS regions in the region type of the affected CICS bundle, and look for messages that provide more information about why the CICS bundle was not installed.
If the CICS bundle cannot be found, check your zFS setup as described previously for the platform bundle. This error can occur if the platform home directory in the zFS file system is not shared across the sysplex, or if the platform home directory is on a different sysplex from the sysplex where you are installing the platform.

Problems when you enable a platform

If the status of a platform is PARTIAL or INACTIVE, investigate the status of each CICS region in the platform. A status of PARTIAL or INACTIVE means that one or more region types in the platform contains no active CICS regions. In the Cloud Explorer view, expand the region types for the platform, then expand the Regions list for each region type to see which of its CICS regions are active or inactive. Double-click any inactive CICS region to work with it.

If the enable status of a platform is DISABLED or SOMEDISABLED, try to enable the management parts for the platform. To enable the whole platform, in the Cloud Explorer view, right-click the platform and click Enable. If the platform still is not enabled, investigate the individual CICS bundles that are named in each management part.

If the status of a management part is DISABLED or SOMEDISABLED, try to enable the individual CICS bundles in each CICS region where they are installed. To enable a CICS bundle, open the Bundles view by clicking Operations > Bundles. Alternatively, double-click the management part in the Cloud Explorer view, or right-click the management part and select Show Installed Bundles. Select the record for the CICS bundle in the CICS region where you want to enable it, right-click, and click Enable. If the CICS bundle remains disabled, check its definition to see if it has a dependency on an import for a resource that is not present in the CICS region.

Problems when you modify a platform

If you try to add an existing CICS region to a region type, or to remove an existing >CICS region from a region type, and receive an error message, verify that the CICS region has been shut down. Note that the Stop action for a CICS region in the Cloud Explorer view does not shut down the region. It only disconnects the region from CICSPlex SM. The CICS region must be shut down and restarted in order to install the required bundles for the new region type. If the CICS region has been shut down and you still receive an error message, look up the error code in the PLATFORM Resource Table to see why the action has failed.

If you try to add a CICS bundle to a platform, and receive an error message, select the platform in the Cloud Explorer view and check the status of each CICS bundle that you attempted to add. If an error occurs when you add a bundle to a platform or remove a bundle from a platform, the operation fails and all resources modified to that point get restored to their original state.

If the status of a management part is INVALIDSCOPE, check the definition for the CICS bundle to see whether the target CICS system group was specified correctly.
If the status of a management part is EMPTY, check whether the CICS regions where the CICS bundle should have been installed are active and connected to the CMAS. If the CICS regions are available, check the definition for the CICS bundle for any errors.
If the error code relates to bundle failure or partial install, check the CICSMSG log of the CICS regions in the region type of the affected bundle for more information about why the bundle was not installed.
If the CICS bundle cannot be found, check your zFS setup. This error can occur when a platform is spread across different systems (LPARs) in the same sysplex, but the platform home directory in the zFS file system is not shared across the sysplex. You must either use FTP by using a connection to the same zFS that your CMAS is running on, or set up sysplex-wide sharing of your platform home directory. Another possibility is that the platform home directory is on a different sysplex from the sysplex where the platform is installed. Ensure that the platform home directory is on the sysplex where you have installed the platform.