The Communications component has been successfully initialized.
CICSPlex® SM initialization continues.
None.
EYULOG
EYU0CIIN
The Communications component has been terminated.
CICSPlex SM termination continues.
None.
EYULOG
EYU0CITM, EYU1CITM
The specified subcomponent of the Communications component is being initialized, where:
Initialization of the subcomponent continues.
None.
EYULOG
EYU0CIIN, EYU1CIIN
During CMAS initialization, the data repository was scanned for CMAS-to-CMAS link
records, but none were found. This either means that no links have been defined
to CICSPlex SM (through the CMTCMDEF or CMTPMDEF views), or that the data repository has
been reinitialized since links were defined.
To ensure that the CICS® DFHCSD file coincides with the data repository, the specified CSD communications group, which contains the link definitions for the CMAS, is being deleted, where:
CICSPlex SM attempts to delete the communications group. This message is followed by another message that indicates whether the group could be deleted: EYUCI0005I indicates the group was deleted; EYUCI0006E indicates it was not.
None.
Console, job log, EYULOG
EYU0CSSR
This message follows message EYUCI0004I to indicate that the specified CSD communications group was successfully deleted, where:
Initialization of the Communications component continues.
None.
EYULOG
EYU0CSSR
This message follows message EYUCI0004I to indicate that the specified CSD communications group could not be deleted, where:
Any CMAS-to-CMAS links defined
to CICSPlex SM are not established. In the case of a CEDA failure, message EYUXS0003E
is issued with details about the failure.
Depending on the reason for the failure, do one of the following:
Console, job log, EYULOG
EYU0CSSR
During initialization of the Communications component, the definitions in the specified communications group are being installed. All CICS definitions for CMAS-to-CMAS links reside in a communications group in the DFHCSD file, where:
CICSPlex SM attempts to install the group. This message is followed by another message that indicates whether the group could be installed: EYUCI0008I indicates the group was installed; EYUCI0008E or EYUCI0014W indicates it was not.
None.
EYULOG
EYU0CSSR
This message follows message EYUCI0007I to indicate that the specified CSD communications group was successfully installed, where:
Initialization of the Communications component continues.
None.
EYULOG
EYU0CSSR
This message follows message EYUCI0007I to indicate that the specified CSD communications group could not be installed, where:
Any CMAS-to-CMAS links defined
to CICSPlex SM are not established. In the case of a CEDA failure, message EYUXS0003E
is issued with details about the failure.
Depending on the reason for the failure, do one of the following:
Console, job log, EYULOG
EYU0CSSR
During CMAS initialization, the data repository is scanned for CMAS-to-CMAS link
records. Appropriate CONNECTION, SESSION, and PARTNER resources are dynamically
created in the running CMAS, where:
CICSPlex SM attempts to create the required resources and to update the connection list. This message is followed by another message that indicates whether or not the list could be updated. EYUCI0011I indicates that the list was updated; EYUCI0012E indicates that it was not.
None.
EYULOG
EYU0CSSR
This message follows message EYUCI0010I to indicate that a link to the specified CICS system was successfully defined and installed, where:
Initialization of the Communications component continues.
None.
EYULOG
EYU0CSSR
This message follows message EYUCI0010I to indicate that a link to the specified CICS system could not be defined and installed, where:
The impact on system processing depends on the reason for the failure:
Console, job log, EYULOG
EYU0CSSR
The CMAS that is being initialized was not started with a system initialization table (system initialization table)
parameter of START=COLD. The link definitions in the specified communications
group are not installed; CICS restores all link definitions from the DFHRSD
file. Any recent changes or additions to the CICSPlex SM CMAS-to-CMAS link
definitions (made using the CMTCMDEF or CMTPMDEF views) are not available
to the CMAS, where:
The CMAS uses whatever link definitions existed in the DFHRSD file at the time of its last shutdown. If either the CICSPlex SM data repository or the DFHCSD file was restored from backup or reinitialized since the last CMAS execution, the link definitions may not be up to date.
To make use of the latest link definitions, stop the CMAS and then restart it with a system initialization table parameter of START=COLD.
EYULOG
EYU0CSSR
This message follows message EYUCI0007I to indicate that the specified communications group could not be installed because it could not be found in the DFHCSD file. This problem could occur for one of two reasons:
Where:
If the DFHCSD file was restored from backup or reinitialized, this message is followed by one or more EYUCI0010I messages as CICSPlex SM attempts to synchronize the file with its data repository.
Otherwise, no CMAS-to-CMAS connections
are established.
None.
Console, job log, EYULOG
EYU0CSSR
During initialization of the Communications component, an error has been detected while trying to set the priority of the CICSPlex SM supplied transaction COIR.
MAS initialization continues. However, evaluation definitions (EVALDEFs) that run in this MAS operate as if the CICSPlex SM system parameter COIRTASKPRI=0 is set. This means the MAS long-running task COIE is used for all EVALDEFs, even if the Separate Task field is set to Yes.
Check that transaction COIR is installed in the MAS. Once COIR has been installed, the MAS agent will need to be restarted to pick up the change.
Console, job log
EYU0CIIN
During initialization of the Communications component, an error has been detected while trying to set the priority of theCICSPlex SM supplied transaction COHT.
MAS initialization continues. However, it will not be possible to obtain data for completed tasks (HTASK resource table) because the MAS COHT transaction is not available.
Check that transaction COHT is installed in the MAS. Once COHT has been installed, the MAS agent will need to be restarted to pick up the change.
Console, job log
EYU0CIIN
One or more subcomponents of the Communications component could not be initialized.
CICSPlex SM initialization terminates abnormally. A user trace record is written to the CICS trace data set.
Examine the exception trace records, and any messages issued before this one, to determine the cause of the problem.
Console, job log, EYULOG
EYU0CIIN
One or more subcomponents of the Communications component could not be properly terminated. Some resources may remain allocated.
CICSPlex SM termination continues. A user trace record is written to the CICS trace data set.
Examine the exception trace records and, any messages issued before this one, to determine the cause of the problem.
Console, job log, EYULOG
EYU0CITM