OMEGAMON for MVS EPILOG EDS maintenance and EC566, EC536, EC242

Resolving The Problem

EC242, EC536 and EC566 are related, and the following are possible causes:
1. The OMEGAMON II for MVS or CMS/TEMS VTAM Nodes and/or Appl IDs have not been activated.

2. There could be a mismatch between the VTAM Node(s) definition and the product configuration (e.g. RKANPAR(U) members). In the ..RKANPARU dataset for the RTE, look at the KEPOPTN and KEPEDS members. The EDSLIST in KEPOPTN should point to the same datasets as in the KEPEDS.

3. The LU 62 VTAM Log Mode table (default KDSMTAB1) is not in sys1.VTAMLIB.

4. TEMS may not be defined correctly to VTAM.
The SYS1.VTAMLST (or maybe SYS1.**.VTAMLST) contains a member which defines the TEMS.
Check that member and make sure the TEMS is defined correctly. If you are unsure about the SYS1.**.VTAMLST member that defines the TEMS, then search that dataset for a member that has "DS" in the name, such as xxxxDSx.

5. There is a mismatch between the Log Mode Table and VTAM node definition.


Information for the messages follows...

EC536: SQL1 CREATE PATH FAILURE, RC = 101
Explanation:
This EC536 message is issued when the collector is unable to establish a connection to the data server, TEMS.
System Action:
Data collection for data that is obtained from the TEMS data server is discontinued.
User Response:
Check to see that the data server is active, and that the input parms related to the data server connection are correct (e.g., LOCALID, REMOTEID, etc.).

+---------------------------------------------------------------------

EC242: CT/DS RECONNECT NOT SUCCESSFUL
Explanation: The EPILOG collector was not able to reconnect to the CMS.
System Action: None.
User Response: Examine the CMS task to determine why the collector is not able to reconnect.


The VTAM sysadmin at customer's site should check and ensure the VTAM APPLID "XXXXDSDS" is active and in CONNECTED state. If not active and CONNECTED, then have the VTAM sysadmin activate and connect the APPLID.

+---------------------------------------------------------------------

EC566: UNABLE TO INITIALIZE CMS CONNECTION
Explanation: The historical collector encountered an error that prevented it from establishing a connection to the TEMS (aka: Candle Management Server).
System Action:
The historical collector continues without attempting to collect data from the TEMS/CMS. Historical collection will be limited to data that can be obtained without the TEMS/CMS.
User Response:
Examine the collector's RKM2OUTM message file. It should contain additional messages providing further details about the error.
>>A common cause for this is an incorrectly specified REMOTEID or
>>LOCALID on the OPTIONS command in the RKANPAR/RKANPARU file.

If the TEMS was re-started during this error sequence, then check the timing for TEMS starting in TEMS RKLVLOG to compare to EPILOG start...
EC566 message may occur because EPILOG comes up before the TEMS. The TEMS should be allowed to initialize completely before any of the other OMEGAMONs are started and before EPILOG is started. TEMS should initialize completely then your EPILOG applid should come up.


If the above all looks good, open a Service Request call (ETR) with OMEGAMON defect support and send in the RKLVLOGs from the tasks for the TEMS and OMEGAMON II for MVS as well as the RKM2OUTM log from EPILOG.