Consider this example of incomplete data that is returned to the end-user interface in response to an operations view command:
27FEB2005 07:02:28 ----------- INFORMATION DISPLAY --------------------------- COMMAND ===> SCROLL ===> CURR WIN ===> 1 ALT WIN ===> W1 =CICSRGN===========EYUPLX01=EYUCSG01=27FEB2005==07:01:51=CPSM============== BBMXBD15I There is no data that satisfies your request
In the example shown in Figure 50, there is a CICS® system known as EYUMAS1A. EYUMAS1A has been installed as a MAS. It is currently running, yet it does not show up as expected on the CICSRGN view.
A good first step to determine what is wrong is to issue the MAS view command, using the same context (EYUPLX01) and scope (EYUCSG01) as the failing CICSRGN view. The result of issuing this command is one of the following:
Three possible causes for there being no entry for EYUMAS1A in the MAS view are:
If EYUMAS1A is not a member of the CICS system group EYUCSG01, the scope is incorrect. To test that possibility, use the SCOPE command to change the scope to either the entire CICSplex (EYUPLX01) or the MAS itself (EYUMAS1A). If the refreshed MAS view with the new scope shows an entry for EYUMAS1A, the problem was an incorrect scope.
EYUPLX01 should have been the context when the CICSSYS definition for EYUMAS1A was created. If it was not, use the CONTEXT command to refresh the MAS view, using the correct context.
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 MAS 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 CICSSYS 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 VTAM® APPLID. Here is an example of the JESMSGLG of the MAS when the NAME parameter is incorrect:
DFHSI1517 EYUMAS1A Control is being given to CICS.
EYUXL0003I EYUMAS1A CPSM Version 210 LMAS startup in progress
EYUXL0022I EYUMAS1A LMAS Phase I initialization complete
EYUXL0020I EYUMAS1A ESSS connection in progress to CICSplex(EYUPLX01)
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 MAS 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 MAS 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 action command on the MAS 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 52.
Let’s say you are connected to CICSPlex SM with a context of EYUPLX01 and your server CMAS is EYUCMS1A. You could use the following command to specify that context:
CONtext EYUPLX01 CPSM EYUCMS1A
You know that all eight MAS regions are running, yet a MAS command with a scope of EYUPLX01 returns the following:
27FEB2005 06:57:38 ----------- INFORMATION DISPLAY --------------------------- COMMAND ===> SCROLL ===> CURR WIN ===> 1 ALT WIN ===> >W1 =MAS===============EYUPLX01=EYUPLX01=27FEB2005==06:57:37=CPSM====8========= CMD Name Type CMAS Status MON RTA WLM Description --- -------- ------ -------- -------- Act Act Act ----------------------------- EYUMAS1A EYUCMS1A ACTIVE NO YES YES EYUMAS2A EYUCMS1A ACTIVE NO YES YES EYUMAS3A EYUCMS1A ACTIVE YES NO YES EYUMAS4A EYUCMS1A ACTIVE YES NO YES EYUMAS1B N/A INACTIVE N/A N/A N/A EYUMAS2B N/A INACTIVE N/A N/A N/A EYUMAS3B N/A INACTIVE N/A N/A N/A EYUMAS4B N/A INACTIVE N/A N/A N/A
The result shown in Figure 53 occurs if EYUCMS1B is not running, or if communication between EYUCMS1A and EYUCMS1B has failed. In general, the CMAS serving an end-user interface 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 end-user interface.
The CICSPLEX view shows (from the perspective of one CMAS) the connectivity to the other CMASs managing a CICSplex. To use this view, set the context to the CMAS that is serving your end-user interface session (EYUCMS1A), then issue the CICSPLEX command, as follows:
CONtext EYUCMS1A;CICSPLEX EYUPLX01
Figure 54 shows the result:
27FEB2005 07:41:08 ----------- INFORMATION DISPLAY --------------------------- COMMAND ===> SCROLL ===> CURR WIN ===> 1 ALT WIN ===> W1 =CICSPLEX==========EYUCMS1A=EYUPLX01=27FEB2005==07:40:42=CPSM====2========= CMD CICSPlex CMAS Status MP Access Transit Transit --- -------- -------- -------- --- Type---- --CMAS-- -Count- EYUPLX01 EYUCMS1A ACTIVE YES LOCAL 0 EYUPLX01 EYUCMS1B INACTIVE NO N/A 0
If the CICSPLEX 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.
An ACTIVE status indicates that a MAS is properly connected to the CICSplex. There should be no problem with missing data.
[[ Contents Previous Page | Next Page Index ]]