IBM 51 manual COPCOM269E The switch endpoint mode VALUE0 is not valid

Facility to determine the problem. To activate logging, set the TraceFileName variable in the Tivoli Enterprise Console configuration file.

COPCOM264E The system cannot generate the Tivoli Enterprise Console (TEC) event because no event class name was specified.

Explanation: The Send TEC Event Java plug-in uses the Tivoli Enterprise Console TECAgent code base to send TEC events to the Tivoli Enterprise Console (TEC) server. All TEC events sent by the Send TEC Event Java plug-in must conform to the Tivoli Enterprise Console standard. The TEC event class name that was provided to the system does not conform to the standard.

Operator response: Verify that the name of the event class contains only alphanumeric characters, and verify that it does not contain any white space. Refer to the Tivoli Enterprise Console product manual for more information.

COPCOM265E The system cannot find the switch endpoint VALUE_0.

Explanation: No additional information is available for this message.

COPCOM266E The system cannot find the switch or the endstation endpoint VALUE_0.

Explanation: No additional information is available for this message.

COPCOM267E The switch endpoint VALUE_0 is not in trunking mode.

Explanation: No additional information is available for this message.

COPCOM268E The switch endpoint VALUE_0 is not connected to a peer endpoint.

Explanation: No additional information is available for this message.

COPCOM269E The switch endpoint mode VALUE_0 is not valid.

Explanation: No additional information is available for this message.

COPCOM270E The switch endpoint encapsulation VALUE_0 is not valid.

Explanation: No additional information is available for this message.

COPCOM271E The system cannot find the VALUE_0

DcmObjectSoftwareStack.

Explanation: No additional information is available for this message.

COPCOM272E The system cannot find the discovery-association: VALUE_0.

Explanation: While it imported discovery information from an XML file, the system searched the data center model for the discovery-association that the system expects to associate or update. However, the system did not find the discovery-association.

Operator response: Verify that the discovery-association exists and that it is spelled correctly.

COPCOM273E The system cannot find the config-drift: VALUE_0.

Explanation: While it imported discovery information from an XML file, the system searched the data center model for the config-drift entity that the system expects to associate or update. However, the system did not find the config-drift entity.

Operator response: Verify that the config-drift entity exists and that it is spelled correctly.

COPCOM274E The system cannot find the discoverable: VALUE_0.

Explanation: While it imported discovery information from an XML file, the system searched the data center model for the discoverable entity that the system expects to associate or update. However, the system did not find the discoverable entity.

Operator response: Verify that the discoverable entity exists and that it is spelled correctly.

COPCOM275E The system cannot find the discovery-execution: VALUE_0.

Explanation: While it imported discovery information from an XML file, the system searched the data center model for the discovery-execution entity that the system expects to associate or update. However, the system did not find the discovery-execution entity.

Operator response: Verify that the discovery-execution entity exists for the ID.

COPCOM277E Fibre channel port number VALUE_0 is out of range in the fibre channel switch VALUE_1.

Explanation: No additional information is available for this message.

Chapter 10. Tivoli Intelligent Orchestrator messages 109