OC STATUS,CICSPLEX command
You can issue a command to determine which CICSplex groups are known by the OMEGAMON AI for CICS agent and the status of each one.
/F agent,OC STATUS,CICSPLEX
This command generates the output in the RKLVLOG similar to the following
example: KCP9030: ATC PROCESSING THE FOLLOWING COMMAND:
STATUS,CICSPLEX
KCP9329I: DISPLAYING INFORMATION FOR CICSPLEX CICSPLX1:
KCP9330I: ORIGIN NODE: CICSPLX1::CICSplex
KCP9331I: NUMBER OF CICS REGIONS: 1
KCP9332I: REGISTERED BY THIS AGENT: NO
KCP9329I: DISPLAYING INFORMATION FOR CICSPLEX CICSPLX2:
KCP9330I: ORIGIN NODE: CICSPLX2::CICSplex
KCP9331I: NUMBER OF CICS REGIONS: 2
KCP9332I: REGISTERED BY THIS AGENT: YES
In this example, CICSplex CICSPLX1 and CICSPLX2 are known by the agent. This agent has one active CICS region in the CICPLX1 CICSplex. The IBM Tivoli Monitoring managed object name for CICSPLX1 is CICSPLX1::CICSplex. The CICSPLX1 CICSplex was registered by another agent. The CICSPLX1::CICSplex managed object was defined to IBM Tivoli Monitoring by another agent. The CICS agent has two active CICS regions in the CICPLX2 CICSplex. The IBM Tivoli Monitoring managed object name for CICSplex CICSPLX2 is CICSPLX2::CICSplex; the CICSPLEX CICSPLX2 was registered by this agent. The CICSPLX2::CICSplex managed object was defined to IBM Tivoli Monitoring by the agent that is being queried.
/F agent,OC DISPLAY,PLEX=CICSPLX2
You can use this command and the OC DISPLAY,PLEXRULES command to determine why a CICS region is assigned to a particular CICSplex.