Validate cross-system coupling facility

Use the messages to validate the cross-system coupling facility (OMEGAMON/XCF) setup.

Procedure

  1. Use message KO2Z638I to validate. KO2Z638I is issued to indicate that a Classic or Common Collector session has joined the OMPEXCF group. For example, KO2Z638I OMPE V550 Session BPMYD2C/IPV$TCE0 joined XCF group OMPEXCF/PMO1SGP1DM520001
    Value Explanation
    OMPE Identifies the subsystem name assigned to the OMEGAMON® Collector
    V550 Identifies the OMEGAMON Collector release
    BPMYD2C Identifies the OMEGAMON Collector VTAM® ACB name
    IPV$TCE0 Identifies the VTAM terminal ID
    / Group name and member name separator
    OMPEXCF Identifies the OMEGAMON Collector XCF gateway group name
    PMO1 Identifies the SMF system ID
    SGP1DM52 Identifies the name of the OMEGAMON Collector STC address space
    0001 Identifies the joined unique XCF gateway connection ID
  2. Use message KO2Z806I to validate. KO2Z806I is issued to indicate that a Classic or Common Collector session has been disconnected from the OMPEXCF group. For example, KO2Z608I OMPE V550 Session BPMYD2C/IPV$TCE0 disconnected from XCF group OMPEXCF/PMO1SGP1DM520001
    Value Explanation
    OMPE Identifies the subsystem name assigned to the OMEGAMON Collector
    V550 Identifies the OMEGAMON Collector release
    BPMYD2C Identifies the OMEGAMON Collector VTAM ACB name
    IPV$TCE0 Identifies the VTAM terminal ID
    / Group name and member name separator
    OMPEXCF Identifies the OMEGAMON Collector XCF gateway group name
    PMO1 Identifies the SMF system ID
    SGP1DM52 Identifies the name of the OMEGAMON Collector STC address space
    0001 Identifies the joined unique XCF gateway connection ID

    This OMEGAMON Collector XCF gateway parameter specifies the number of receive tasks to attach in the OMEGAMON Collector address space. These tasks are used to receive and process OMEGAMON Collector service requests from other local or remote OMEGAMON Collector connected to the same OMPEXCF group name.

    The default number of tasks that are attached at OMEGAMON Collector initialization time is MAXTASKS=04. The minimum number of tasks that can be specified is MAXTASKS=2. At task initialization time, each receive task connects to the OMEGAMON Collector XCF gateway using the XCFGROUP=OMPEXCF. The XCF connection for each attached receive task persists for the life of the OMEGAMON Collector address space. When the OMEGAMON Collector is normally shut down, these XCF connections are terminated. When the OMEGAMON Collector is canceled or forced, these XCF connections remain defined to the z/OS® XCF and will be reused by the OMEGAMON Collector on subsequent start up.

    You can display all XCF gateway connections by issuing the D XCF,GROUP,0MPEXCF z/OS XCF command. For example:

     
D XCF,GROUP,OMPEXCF

IXC332I  22.45.54  DISPLAY XCF 992
 GROUP OMPEXCF:

          PMO1SGP1DM52X000	PMO1SGP1DM52X001	PMO1SGP1DM52X002
					PMO1SGP1DM52X003	PMO1SGP1DM52X004	PMO1SGP1DM52X005
					PMO1SGP1DM52X006	PMO1SGP1DM52X007	PMO1SGP1DM52X008
					PMO1SGP1DM52X009	PMO1SGP1DM52X010	PMO1SGP1DM52X011
					PMO1SGP1DM52X012	PMO1SGP1DM52X013	PMO1SGP1DM52X014
					PMO1SGP1DM52X015
    Value Explanation
    OMPEXCF Identifies the OMEGAMON Collector XCF gateway group name
    PMO1 Identifies the SMF system ID
    SGP1DM52 Identifies the name of the OMEGAMON Collector STC address space
    X Identifies the member name as a receive task member name
    0001 Identifies the joined unique XCF gateway connection ID

    The default XCFTIMER=30 parameter specifies the maximum elapsed time in seconds required to complete a send request from one OMEGAMON Collector to another collector, connected to the same OMPEXCF group. If a response is not received within the 30 seconds default elapsed time interval, the request is terminated and the KO2Z810E error message is issued. For example: KO2Z810E OMPE V510 OMPE Collector SGP1DM5S SSID=D91A MEMBER=PM01SGP1DM5S0010 response not received

    This error condition might be caused by one or more of the following:
    • The remote OMEGAMON Collector address space terminated either normally or abnormally.
    • All receive tasks specified by the MAXTASKS parameter are busy.
    • The remote LPAR/VMID has failed or is being restarted.
    • The OMEGAMON Collector WLM dispatch priority is too low.
    Take the following action(s):
    • Verify that the remote OMEGAMON Collector is still active.
    • Increase the number of receive tasks defined by the XCFTASKS parameter.
    • Increase the XCFTIMER elapsed time seconds value.
    • Verify that the OMEGAMON Collector is executing with the same priority or higher as your Db2 subsystem.
    The default DSPSIZE=128M parameter specifies the size of the XCF gateway data space (in megabytes) that is created when a Classic or Common Collector session is connected to the OMEGAMON Collector XCF gateway. The date space is used to collect remote thread CPU data. Up to 20,000 remote threads CPU usage data can be collected in a single XCF send service request.
    Note: z/OS page data set space is only incurred when remote thread CPU data is being retrieved. When remote thread CPU data is not being collected, the paging space is released and not used.