INACTIVE status

Whenever either a MAS or a CMAS is started, CICSPlex SM attempts to activate communication between the MAS and the CMAS. If both the CMAS and the MAS are running and the status on the MASs know to CICSplex view shows INACTIVE, you need to look at the JESMSGLG of the MAS and the EYULOG of the CMAS.

They may contain messages indicating that the connection process failed and suggesting what could be wrong.

It could be that the CICS system definition name does not match the EYUPARM parameter NAME in the startup JCL for the MAS. It is also a possibility that, if the default for the EYUPARM NAME is taken, EYUMAS1A is not the z/OS Communications Server APPLID. Here is an example of the JESMSGLG of the MAS when the NAME parameter is incorrect:
Figure 1. Example of JESMSGLG when EYUPARM NAME parameter is incorrect
DFHSI1517 EYUMAS1A Control is being given to CICS.
EYUXL0003I EYUMAS1A  CPSM Version 320 LMAS startup in progress
EYUXL0022I EYUMAS1A  LMAS Phase I initialization complete
EYUXL0004I EYUMAS1A  ESSS connection complete
EYUCL0112E EYUMAS1A  Protocol Services initialization unable to perform ICT Attach
EYUCL0101E EYUMAS1A  Protocol Services initialization failed
EYUCI0101E EYUMAS1A  Communications initialization failed
EYUXL0112E EYUMAS1A  LMAS initialization failed

The EYUPARM parameter CICSplex in the startup JCL for the MAS may not match the CICSplex name being used as the context for the MASs know to CICSplex view. If the CICSplex named in the EYUPARM is valid, the MAS probably connected successfully to that CICSplex, instead of to the CICSplex used as the context for the MASs know to CICSplex view that shows INACTIVE.

If SEC(NO) is coded in the EYUPARM parameters for a CMAS, and SEC(YES) is coded for a MAS that is connecting to that CMAS, the attempt to establish the connection between the CMAS and the MAS fails. The following message appears in the EYULOG of the CMAS:
EYUCR0007E 'Security mismatch between CMAS EYUCMS1A and MAS EYUMAS1A  .
            Connection Terminating.'

It is also possible to terminate the connection between a CMAS and a MAS using the Stop button on the MASs know to CICSplex view.

The preceding causes of the INACTIVE status have not dealt with the case where a CICSplex is managed by multiple CMASs. Consider the CICSplex shown in Figure 2.
Figure 2. Example of a CICSplex managed by multiple CMASs
eyus1007
Let's say you are connected to CICSPlex SM with a context of EYUPLX01 and your server CMAS is EYUCMS1A. Set the context for the CICSplex on the main menu, using the following values:
CMAS context: EYUCMS1A
Context:      EYUPLX01
You know that all eight MAS regions are running, yet the MASs known to CICSplex view with a scope of EYUPLX01 shows an ACTIVE status for EYUMAS1A, EYUMAS1A, EYUMAS1A, and EYUMAS1A, but an INACTIVE status for EYUMAS1B, EYUMAS2B, EYUMAS3B, and EYUMAS4B.

In general, the CMAS serving a WUI request must have connectivity to the CMAS to which a MAS is connected; if it does not, that MAS does not appear active to the WUI.

The CMASs managing CICSplex view shows (from the perspective of one CMAS) the connectivity to the other CMASs managing a CICSplex. To access this view, from the main menu, click CICSplex SM operations view > CMASs managing CICSplex. On the CMASs managing CICSplex tabular view, set the context to the CMAS that is serving your WUI session (EYUCMS1A) and click the Refresh button.

If the CMASs managing CICSplex tabular view shows a CMAS with INACTIVE status, but you know that CMAS is running, you must investigate the communication links. CMAS-to-CMAS communication uses CICS® services. Therefore, the MSGUSR log is likely to contain information concerning the nature of the communication failure.



eyus1c0055.html | Timestamp icon Last updated: Monday, 5 June 2017