KCN messages

The messages that begin with the KCN prefix are associated with OMNIMON Base. Return codes associated with these messages can be found in z/OS status codes and return codes.

KCNCA001E UNABLE TO OBTAIN PRIVATE STORAGE, COUPLING FACILITY COLLECTION NOT AVAILABLE

Explanation

This message comes from the OMEGAMON® Subsystem attached subtask designed to issue IXCQUERY requests for CF_ALLDATA and STR_ALLDATA information (KCNCFAT). It indicates that working storage for this subtask cannot be obtained. Data collection is terminated.

System action

None.

User response

Recycle the OMEGAMON Subsystem associated with this message. If the problem persists, call IBM® Software Support for further assistance.

KCNCA002E SUBTASK PARMS INVALID, COLLECTION TERMINATED

Explanation

This message comes from the OMEGAMON Subsystem attached subtask designed to issue IXCQUERY requests for CF_ALLDATA and STR_ALLDATA information (KCNCFAT). A parameter area passed to the collection subtask does not have the correct identification text (eyecatcher). The subtask must assume the parameters area has been corrupted. Data collection is terminated.

System action

None.

User response

Recycle the OMEGAMON Subsystem associated with this message. If the problem persists, call IBM Software Support for further assistance.

KCNCA003E IXCQUERY XXX_ALLDATA FAILED RC(XXXXXXXX),REASON(XXXXXXXX)

Explanation

This message comes from the OMEGAMON Subsystem attached subtask designed to issue IXCQUERY requests for CF_ALLDATA and STR_ALLDATA information (KCNCFAT). The XXX in XXX _ALLDATA may be either STR or CF. This message indicates that a severe error occurred while trying to get IXCQUERY data. The return code (RC) and reason code (REASON) from the attempt are documented and can be found in the IBM z/OS® MVS Programming Sysplex Services Reference for Return and Reason Codes for IXCQUERY. This message may appear up to 6 times if the problem persists. After 6 attempts the OMEGAMON Subsystem will stop trying to get this data.

System action

None.

User response

Verify that the authorized OMEGAMON Subsystem is running and that the Coupling Facility Resource Management (CFRM) data set is accessible from this LPAR. If the problem persists, call IBM Software Support for further assistance. If it is running and the problem persists, contact IBM Software Support for further assistance.

KCNCA004E UNABLE TO OBTAIN LARGER XXX_ALLDATA ANSWER AREA, SIZE(XXXXXXXX). COLLECTION NOT AVAILABLE

Explanation

This message comes from the OMEGAMON Subsystem attached subtask designed to issue IXCQUERY requests for CF_ALLDATA and STR_ALLDATA information (KCNCFAT). The XXX in XXX _ALLDATA may be either STR or CF. The value following SIZE is the storage area size, in hexadecimal, that is needed. Subtask collection is terminated.

System action

None.

User response

Recycle the OMEGAMON Subsystem associated with this message. If the problem persists, call IBM Software Support for further assistance.

KCNCI001E UNABLE TO OBTAIN PRIVATE STORAGE, COUPLING FACILITY COLLECTION NOT AVAILABLE.

Explanation

This message comes from the main module supporting Coupling Facility data collection in the OMEGAMON Subsystem (KCNCFIN). Work area storage for this module could not be obtained. The module is terminating and will not be available to support Coupling Facility collection.

System action

None.

User response

Recycle the OMEGAMON Subsystem associated with this message. If the message is seen again, call IBM Software Support for further assistance.

KCNCI002W COUPLING FACILITY DATA COLLECTION SUBTASK TERMINATED UNEXPECTEDLY.

Explanation

This message comes from the main module supporting Coupling Facility data collection in the OMEGAMON Subsystem (KCNCFIN). The collection subtask terminated unexpectedly.

System action

None.

User response

None. If this message appears frequently, call IBM Software Support for further assistance.

KCNCI003E COUPLING FACILITY DATA COLLECTION SUBTASK START FAILED, RELINQUISHING COLLECTOR STATUS

Explanation

This message comes from the main module supporting Coupling Facility data collection in the OMEGAMON Subsystem (KCNCFIN). The collection subtask attach failed. This address space will stop trying to collect Coupling Facility data. It will participate as a receiver when another OMEGAMON Subsystem takes over the collection function.

System action

None.

User response

None. If this message appears frequently, call IBM Software Support for further assistance.

KCNCI004E ERROR: KCNDLCF FUNCTION PARMS NOT FOUND

Explanation

This message comes from the main module supporting Coupling Facility data collection in the OMEGAMON Subsystem (KCNCFIN). This is a severe internal error for this function and it cannot continue.

System action

None.

User response

Recycle the OMEGAMON Subsystem associated with this message. If this message appears again, call IBM Software Support for further assistance.

KCNCI005I COUPLING FACILITY COLLECTOR SUBTASK STARTED

Explanation

This message comes from the main module supporting Coupling Facility data collection in the OMEGAMON Subsystem (KCNCFIN). It indicates that this OMEGAMON Subsystem is collecting Coupling Facility data for the Sysplex.

System action

None.

User response

None. This is an informational message.

KCNCI006W COUPLING FACILITY COLLECTOR STARTING LOCAL COLLECTION

Explanation

This message comes from the main module supporting Coupling Facility data collection in the OMEGAMON Subsystem (KCNCFIN). The OMEGAMON Subsystem associated with this message has stopped receiving coupling facility data from the Sysplex collector. It has started collecting data itself for the OMEGAMON products on this system image.

System action

None.

User response

This message may appear occasionally if the XCF message processing facility is heavily burdened, or if the collecting OMEGAMON Subsystem has stalled or failed. If neither message KCNCI007W nor message KCNCI008W is seen shortly, try cancelling the last known collecting OMEGAMON Subsystem (see message KCNCI005I). If the problem persists, call IBM Software Support for further assistance.

KCNCI007I COUPLING FACILITY COLLECTOR RESUMING PLEX RECEPTION

Explanation

This message comes from the main module supporting Coupling Facility data collection in the OMEGAMON Subsystem (KCNCFIN). This message indicates that the problem, wich caused message KCNCI006W to appear, has been resolved. Another OMEGAMON Subsystem has begun sending Coupling Facility data and this address space is receiving that data.

System action

None.

User response

None. This message indicates that a problem state has been resolved. It may also indicate that one of the OMEGAMON Subsystems in the Sysplex has failed and some action should be taken for that address space.

KCNCI008I COUPLING FACILITY COLLECTOR RESUMING PLEX COLLECTION

Explanation

This message comes from the main module supporting Coupling Facility data collection in the OMEGAMON Subsystem (KCNCFIN). This message indicates that the problem, which caused message KCNCI006W to appear, has been resolved. This OMEGAMON Subsystem has begun collecting Coupling Facility data and is sending data to other OMEGAMON Subsystems in its XCF group.

System action

None.

KCNCI009E ERROR JOINING XCF GROUP TYPE=XXXXXXXXXXXXXXXX. FUNCTION TERMINATING.

Explanation

This message comes from the main module supporting Coupling Facility data collection in the OMEGAMON Subsystem (KCNCFIN). The Coupling Facility collection function tried to join the XCF group to determine the identity of other group members. A problem occurred while trying to perform this task. The specific condition is given by the text following the TYPE= phrase, where XXXXXXXXXXXXXXXX is:
  • QUERY GROUP RC>4: the IXCQUERY for group information ended with a return code greater than 4
  • QUERY GROUP NOT4: the IXCQUERY for group information ended with a return code 4 but the reason code was not also 4. When both return and reason codes are 4, it is just a matter of resizing the answer area. Otherwise, some serious error has occurred.
  • QUERY GROUP LNG< – :the IXCQUERY for group information ended with indication that we should resize. However, the buffer area we used is already big enough for the complete data. This contradiction cannot be resolved.
  • QUERY GROUP REPT: Attempts to resize and get group information have failed repeatedly.
  • XCF JOIN FAILED: The IXCJOIN to join the XCF group failed. Check the group name for valid characters.

System action

None.

User response

Recycle the OMEGAMON Subsystem associated with this message. If this message appears again, call IBM Software Support for further assistance.

KCNCI010i COUPLING FACILITY COLLECTION PARMS IN EFFECT ARE: XCF GROUP NAME=XXXXXXXX ADDRESS=XXXXXXXX REFRESH INTERV=XXXXXXXX ADDRESS=XXXXXXXX WTO MESSAGES=XXXXX ADDRESS=XXXXXXXX PLEX COLLECT=XXX ADDRESS=XXXXXXXX

Explanation

This message comes from the main module supporting Coupling Facility data collection in the OMEGAMON Subsystem (KCNCFIN). This message documents the collection parameters in effect for this address space, as follows:
  • XCF Group Name – specifies the XCF group name we are using to pass Coupling Facility data from the collecting OMEGAMON Subsystem to the receiving OMEGAMON Subsystems. The name must be common to all participating OMEGAMON Subsystems in the Sysplex. The name should be unique from any other XCF group names used in this Sysplex.
  • REFRESH INTERV – shows the refresh interval in effect. The value is in seconds. This interval tells you how frequently we are refreshing Coupling Facility data in this address space. All OMEGAMON Subsystems that are part of the same XCF group should have the same refresh interval.
  • WTO MESSAGES – indicates the level of message logging used. There are 3 levels:
    • NO – no messages at all
    • ERROR – error, warning and informational messages that give key status indications for the service. ERROR is the default.
    • ALL – full debugging level messages. This should be used only with IBM Software Support involvement. The message volume can be extensive.
  • PLEX COLLECT – specifies whether or not this address space may become the collector for this Sysplex. There are 2 values:
    • YES indicates that this OMEGAMON Subsystem may become the Coupling Facility data collector for this Sysplex. Only one OMEGAMON Subsystem at a time is the collector. OMEGAMON Subsystems with this value may take over data collection should the current collector fail or be terminated. YES is the default.
    • NO indicates that this OMEGAMON Subsystem may not become the collector for this Sysplex. This OMEGAMON Subsystem may initiate local collection if the Sysplex collector cannot be located.
  • ADDRESS – Appended to each parameter, it is the storage location of this parameter within this address space. This value may be helpful for problem resolution efforts.

System action

None.

User response

This information documents the settings in use. It may be helpful to compare these to the other OMEGAMON Subsystems expected to be in the same XCF group for consistency.

KCNDR001E UNABLE TO OBTAIN PRIVATE STORAGE, COUPLING FACILITY COLLECTION NOT AVAILABLE

Explanation

This message comes from the client application using the OMEGAMON Subsystem for Coupling Facility data collection (KCNCFDR). The driver routine that connects to the OMEGAMON Subsystem cannot obtain working storage. The client will not be able to report on Coupling Facility information.

System action

None.

User response

Recycle the client application associated with this message. If the problem persists, call IBM Software Support for further assistance.

KCNDR002W KXCQUERY HAS RESUMED USING THE OMEGAMON SUBSYSTEM

Explanation

This message comes from the client application using the OMEGAMON Subsystem for Coupling Facility data collection (KCNCFDR). This application had lost contact with that subsystem but has now regained contact. Processing is continuing normally.

System action

None.

User response

None. If this message appears frequently, call IBM Software Support for further assistance.

KCNDR003W KXCQUERY HAS LOST USE OF THE OMEGAMON SUBSYSTEM, RESORTING TO LOCAL COLLECTION

Explanation

This message comes from the client application using the OMEGAMON Subsystem for Coupling Facility data collection (KCNCFDR). This application has lost contact with the OMEGAMON Subsystem. It has begun collection the data itself.

System action

None.

User response

Recycle the OMEGAMON Subsystem associated with this application. If message KCNDR002W is not received after several minutes have elapsed, call IBM Software Support for further assistance.

KCNDR004W OMEGAMON SUBSYSTEM REPORTED A COUPLING FACILITY COMMUNICATION ISSUE, SWITCHING TO A LOCAL COLLECTION

Explanation

This message comes from the client application using the OMEGAMON Subsystem for Coupling Facility data collection (KCNCFDR). This application has communicated with the subsystem, and the subsystem has reported a coupling facility communication failure. The application has begun collecting the data itself.

System action

The application has switched to the local mode of data collection, and it will no longer try to communicate with the subsystem. The local collection mode will be used until the application is recycled.

User response

No action is required.

KCNPR001W COUPLING FACILITY PARMS MAY NOT BE HONORED. RKANPAR FILE BLOCKSIZE IS LESS THAN THE EXPECTED 8880 SIZE. DEFAULTS MAY BE USED.

Explanation

This message comes from initialization functions in the OMEGAMON Subsystem (KCNPRSR). Parameters placed by the Configuration tool in the &hilev.RKANPAR data set help control Coupling Facility collection in the OMEGAMON Subsystem. The parsing code that reads these parameters is expecting the file block size to be the default size of 8880 bytes. This message indicates that the actual file blocksize is smaller than expected and that control parameters may not be properly found as a result. Default values will be used for parameters that are not located.

System action

None.

User response

Default values for parameters should be reasonable for most users. If the default parameters do not suit local needs, call IBM Software Support for further assistance. Resizing the RKANPAR file to its standard 8880 size should relieve this problem.

KCNPR002I PARMS NOT FOUND. DEFAULTS USED FOR:

Explanation

This message comes from initialization functions in the OMEGAMON Subsystem (KCNPRSR). There are parameters placed by the Configuration Software in the &hilev.RKANPARU data set to help control Coupling Facility collection in the OMEGAMON Subsystem. The parsing code that reads these parameters is expecting values for four keywords:
  • XCF=
  • REFRESH=
  • PLEXCOLLECT=
  • KCN_WTO=
This message documents those values that are not found. Built in defaults will be used for their value.

System action

None.

User response

None required. If an overriding parameter was specified but not detected, verify that it was spelled correctly, that there are no blanks after the = sign, and that the entire KCNSTR00 member is less than 8880 bytes long.