EYUCInnnn messages

EYUCI0001I
Communications initialization complete
Explanation:

The Communications component has been successfully initialized.

System action:

CICSPlex® SM initialization continues.

User response:

None.

Destination:

EYULOG

Module:

EYU0CIIN

EYUCI0002I
Communications termination complete
Explanation:

The Communications component has been terminated.

System action:

CICSPlex SM termination continues.

User response:

None.

Destination:

EYULOG

Module:

EYU0CITM, EYU1CITM

EYUCI0003I
subcompid initialization has started
Explanation:

The specified subcomponent of the Communications component is being initialized, where:

subcompid
Identifies the subcomponent as one of the following:
  • Timing services
  • Transport services
  • Link set services
  • Protocol services
  • Connection services
  • Access services
System action:

Initialization of the subcomponent continues.

User response:

None.

Destination:

EYULOG

Module:

EYU0CIIN, EYU1CIIN

EYUCI0004I
Data Repository does not contain Link Definitions, Communications Group grpname is being deleted.
Explanation:

Start of changeDuring 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.End of change

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:

grpname
Is the name of the communications group in the form EYUCxxxx, where xxxx is the four-character CICS system ID of the CMAS.
System action:

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.

User response:

None.

Destination:

Console, job log, EYULOG

Module:

EYU0CSSR

EYUCI0005I
Delete of Communications Group grpname successful.
Explanation:

This message follows message EYUCI0004I to indicate that the specified CSD communications group was successfully deleted, where:

grpname
Is the name of the communications group in the form EYUCxxxx, where xxxx is the four-character CICS system ID of the CMAS.
System action:

Initialization of the Communications component continues.

User response:

None.

Destination:

EYULOG

Module:

EYU0CSSR

EYUCI0006E
Delete of Communications Group grpname failed, reason
Explanation:

This message follows message EYUCI0004I to indicate that the specified CSD communications group could not be deleted, where:

grpname
Is the name of the communications group in the form EYUCxxxx, where xxxx is the four-character CICS system ID of the CMAS.
reason
Identifies the reason for the failure as one of the following:
CSD in use
The DFHCSD file was in use by another user or transaction for more than two minutes. Deleting a group requires update access to the DFHCSD file.
CEDA Failure
A nonzero return code was received from the CEDA interface, which is used to delete a group from the DFHCSD file.
System action:

Start of changeAny 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.End of change

User response:

Depending on the reason for the failure, do one of the following:

Destination:

Console, job log, EYULOG

Module:

EYU0CSSR

EYUCI0007I
Install of Communications Group grpname started.
Explanation:

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:

grpname
Is the name of the communications group in the form EYUCxxxx, where xxxx is the four-character CICS system ID of the CMAS.
System action:

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.

User response:

None.

Destination:

EYULOG

Module:

EYU0CSSR

EYUCI0008I
Install of Communications Group grpname successful.
Explanation:

This message follows message EYUCI0007I to indicate that the specified CSD communications group was successfully installed, where:

grpname
Is the name of the communications group in the form EYUCxxxx, where xxxx is the four-character CICS system ID of the CMAS.
System action:

Initialization of the Communications component continues.

User response:

None.

Destination:

EYULOG

Module:

EYU0CSSR

EYUCI0009E
Install of Communications Group grpname failed, reason
Explanation:

This message follows message EYUCI0007I to indicate that the specified CSD communications group could not be installed, where:

grpname
Is the name of the communications group in the form EYUCxxxx, where xxxx is the four-character CICS system ID of the CMAS.
reason
Identifies the reason for the failure as one of the following:
CSD in use
The DFHCSD file was in use by another user or transaction for more than two minutes. Installing a group requires update access to the DFHCSD file.
CEDA Failure
A nonzero return code was received from the CEDA interface, which is used to install a group from the DFHCSD file.
System action:

Start of changeAny 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.End of change

User response:

Depending on the reason for the failure, do one of the following:

Destination:

Console, job log, EYULOG

Module:

EYU0CSSR

EYUCI0010I
Start of changeCommunications link to addspace sysname is being added to the Connection List.End of change
Start of change
Explanation:

Start of changeDuring 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:

addspace
Identifies the type of address space being linked to as either a CMAS or a MAS.
sysname
Is the name of the CMAS or MAS being linked to.
End of changeEnd of change
Start of change
System action:

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.

End of change
User response:

None.

Destination:

EYULOG

Module:

EYU0CSSR

EYUCI0011I
Communications link to addspace sysname successful.
Explanation:

This message follows message EYUCI0010I to indicate that a link to the specified CICS system was successfully defined and installed, where:

addspace
Identifies the type of address space that was linked to as either a CMAS or a MAS.
sysname
Is the name of the CMAS or MAS that was linked to.
System action:

Initialization of the Communications component continues.

User response:

None.

Destination:

EYULOG

Module:

EYU0CSSR

EYUCI0012E
Communications link to addspace sysname failed, reason
Explanation:

This message follows message EYUCI0010I to indicate that a link to the specified CICS system could not be defined and installed, where:

addspace
Identifies the type of address space as either a CMAS or a MAS.
sysname
Is the name of the CMAS or MAS.
reason
Identifies the reason for the failure as one of the following:
CSD in use
The DFHCSD file was in use by another user or transaction for more than two minutes. Updating a group requires update access to the DFHCSD file.
Start of changeSYSID used in another linkEnd of change
Start of changeThis CMAS already has a connection to a CMAS or MAS with the same namEnd of change
Start of changeAPPLID used in another linkEnd of change
Start of changeThis CMAS already has a connection to a CMAS or MAS with the same VTAM® APPLID.End of change
Start of changeCREATE FailureEnd of change
Start of change An abnormal response was received while dynamically creating resources.End of change
System action:

The impact on system processing depends on the reason for the failure:

CSD in use
The definition is not processed.
Start of changeSYSID used in another linkEnd of change
Start of changeThe definition is not processed.End of change
Start of changeAPPLID used in another linkEnd of change
Start of changeThe definition is not processed.End of change
Start of changeCREATE FailureEnd of change
Start of changeIf creation of CONNECTION or SESSION definitions failed, the incomplete set will be discarded.If creation of related PARTNER definitions failed, the connection is NOT discarded.End of change
User response:

Destination:

Console, job log, EYULOG

Module:

EYU0CSSR

EYUCI0013I
Install of Communications Group grpname is bypassed, CICS was not started COLD.
Explanation:

Start of changeThe 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:

grpname
Is the name of the communications group in the form EYUCxxxx, where xxxx is the four-character CICS system ID of the CMAS.
End of change
System action:

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.

User response:

To make use of the latest link definitions, stop the CMAS and then restart it with a system initialization table parameter of START=COLD.

Note:
CMASs should always be initialized with a system initialization table parameter of START=COLD.
Destination:

EYULOG

Module:

EYU0CSSR

EYUCI0014W
Install of Communications Group grpname failed, Group not in DFHCSD.
Explanation:

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:

grpname
Is the name of the communications group in the form EYUCxxxx, where xxxx is the four-character CICS system ID of the CMAS.
System action:

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.

Start of changeOtherwise, no CMAS-to-CMAS connections are established.End of change

User response:

None.

Destination:

Console, job log, EYULOG

Module:

EYU0CSSR

EYUCI0015W
Transaction COIR not available
Explanation:

During initialization of the Communications component, an error has been detected while trying to set the priority of the CICSPlex SM supplied transaction COIR.

System action:

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.

User response:

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.

Destination:

Console, job log

Module:

EYU0CIIN

Start of change
EYUCI0016W
Transaction COHT not available
Explanation:

During initialization of the Communications component, an error has been detected while trying to set the priority of theCICSPlex SM supplied transaction COHT.

System action:

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.

User response:

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.

Destination:

Console, job log

Module:

EYU0CIIN

End of change
EYUCI0101E
Communications initialization failed
Explanation:

One or more subcomponents of the Communications component could not be initialized.

System action:

CICSPlex SM initialization terminates abnormally. A user trace record is written to the CICS trace data set.

User response:

Examine the exception trace records, and any messages issued before this one, to determine the cause of the problem.

Destination:

Console, job log, EYULOG

Module:

EYU0CIIN

EYUCI0102W
Communications termination failed
Explanation:

One or more subcomponents of the Communications component could not be properly terminated. Some resources may remain allocated.

System action:

CICSPlex SM termination continues. A user trace record is written to the CICS trace data set.

User response:

Examine the exception trace records and, any messages issued before this one, to determine the cause of the problem.

Destination:

Console, job log, EYULOG

Module:

EYU0CITM

[[ Contents Previous Page | Next Page Index ]]