CWYIS0001E: The adapter cannot find the object at the path to the library on the IBM i operating system; the path is {0} and the object type to discover is {1}.
Explanation: The adapter could not find the object at the specified path for one of the following reasons: either the path to the library is invalid or the object type is not available at the specified path.
User Action: Type a valid path to the library on the IBM i operating system.
CWYIS0002E: The adapter could not construct a metadata tree due to the following error: {0}.
Explanation: The adapter cannot create a metadata tree for one of the following reasons: either the path to the library on the i operating system is invalid or the selected object type is not available at the specified path.
User Action: Ensure that the path to the library is correct and that the value for the object type is correct.
CWYIS0003E: The adapter could not get child components for the metadata object. The reason might be due to the following exception: {0}.
Explanation: There are no objects available at the following library path: {1}
User Action: Ensure that valid objects are available at the specified library path.
CWYIS0004E: The adapter could not create selection properties.
Explanation: Selection properties could not be created due to the following error: {0}.
User Action: Check the adapter logs and search for exceptions originating from the ISeriesMetadataSelection class.
CWYIS0005E: The adapter could not populate the metadata object.
Explanation: The metadata object could not be populated due to the following error: {0}.
User Action: Check the adapter logs and search for exceptions originating from the ISeriesDataQueueMetadataObject class or the ISeriesKeyedDataQueueMetadataObject class.
CWYIS0006E: The adapter could not create unified properties.
Explanation: The unified property group could not be created due to the following error: {0}.
User Action: Check the adapter logs and search for exceptions originating from the ISeriesOutboundConnectionConfiguration class.
CWYIS0007E: The adapter could not create an outbound connection configuration.
Explanation: The adapter cannot create an outbound connection configuration due to the following error: {0}.
User Action: Check the adapter logs and search for exceptions originating from the ISeriesOutboundConnectionType class.
CWYIS0008E: The adapter could not create resource adapter properties.
Explanation: Resource adapter properties could not be created due to the following error: {0}.
User Action: Check the adapter logs and search for exceptions originating from the ISeriesOutboundConnectionType class.
CWYIS0009E: The adapter could not create managed connection properties.
Explanation: Managed connection properties could not be created due to the following error: {0}.
User Action: Check the adapter logs and search for exceptions originating from the ISeriesOutboundConnectionConfiguration class.
CWYIS2011E: The adapter could not establish a connection with the enterprise information system (EIS).
Explanation: The EIS instance might be down or the specified managed connection property values might be incorrect.
User Action: If the EIS is down, restart it, and confirm that the specified managed connection property values username, password and hostname are correct.
CWYIS2012E: The adapter does not understand the function name that was passed {0}. It appears to be invalid.
Explanation: Either the function name is null or it is invalid.
User Action: Refer to the documentation for supported operations and resend the request with the appropriate function name.
CWYIS2013E: The adapter does not understand the path of the object that was passed {0}. It appears to be invalid.
Explanation: Either the path of the object is invalid or it is null.
User Action: Refer to the user documentation and set the path of the object appropriately.
CWYIS2014E: The adapter does not understand the object type value that was passed {0}.
Explanation: The adapter either does not support the type of object being passed in, or the type of object is invalid.
User Action: Refer to the documentation regarding supported objects types and resend the request with the appropriate object type.
CWYIS5012E: IBM i program cannot be executed.
Explanation: The adapter could not execute the IBM i program because the metadata for the attribute {1} of type {2} is null or could not be retrieved.
User Action: Use Proper XML Schema Definition for invoking the IBM i program.
CWYIS5013E: IBM i program cannot be executed.
Explanation: The adapter could not execute the IBM i program because the value of metadata item {3} or {4} for the attribute {1} of type {2} is null or improper.
User Action: Use Proper XML Schema Definition for invoking the IBM i program.
CWYIS5014E: IBM i program execution failed on the enterprise information system (EIS).
Explanation: IBM i program execution failed due to reasons or events relevant at the EIS Level.
User Action: Refer to the exception traces and the explanation section for more details.
CWYIS5020E: The input parameter {1} is null or empty.
Explanation: The input parameter {1} is null or empty.
User Action: Enter a proper value for input parameter {1}.
CWYIS6012E: The data queue is empty and did not return a message after the Read operation.
Explanation: The adapter could not retrieve a message from data queue because it does not contain any messages.
User Action: Either populate the data queue with the correct messages or connect to a different data queue.
CWYIS6013E: A 'null' or empty message cannot be written to a data queue. Adapter failed while trying to write data onto a data queue {0} on path {1}
Explanation: The adapter cannot write a 'null' or empty message to a data queue. The message should be a valid string or bytes.
User Action: Send a valid message, such as a string with a finite length.
CWYIS6014E: An exception occurred while writing a message to the keyed data queue {3}. The key of the message is {2}.
Explanation: The following error occurred while writing a message: {0} The return code sent by the i5/OS operating system is {1}.
User Action: Refer to the exception traces and the explanation section for more details.
CWYIS6015E: An exception occurred while reading a message from the keyed data queue {3}. The key of the message is {2}.
Explanation: The following error occurred while writing a message: {0} The return code sent by the i5/OS operating system is {1}.
User Action: Refer to the exception traces and the explanation section for more details.
CWYIS6016E: An exception occurred while writing a message to the data queue {2}.
Explanation: The following error occurred while writing a message: {0} The return code sent by the i5/OS operating system is {1}.
User Action: Refer to the exception traces and the explanation section for more details.
CWYIS6017E: An exception occurred while reading a message from the data queue {2}.
Explanation: The following error occurred while writing a message: {0}. The return code sent by the i5/OS operating system is {1}.
User Action: Refer to the exception traces and the explanation section for more details.
CWYIS6018E: A message with 'null' key value cannot be written to a data queue. Adapter failed while trying to write data onto a data queue {0} on path {1}
Explanation: The adapter cannot write a message onto a data queue with 'null' as key value. The message should have a valid key of type string or bytes.
User Action: Send a message with valid key value like a string with a finite length.
CWYIS6019E: An exception occurred while reading a message from the data queue {0}.
Explanation: The adapter cannot read a message from data queue with 'null' as key value. Message key should be of valid type string or bytes to read from a data queue.
User Action: Refer to the exception traces and the explanation section for more details.
CWYIS6020E: The operation cannot be performed because the object path {0} does not match the specified object type, {1}, function name, {2}, or both.
Explanation: For the operation to be successful, the object path, object type, and function name must be valid. If the object path ends with an extension of .DTAQ or .dtaq, the object type must be either DataQueue or KeyedDataQueue, and the operation name should be either PUTQUEUE or GETQUEUE. If the object path ends with an extension of .PGM or .pgm, the object type should be RPG/SRVPGM , and the function name should be CALLPGM.
User Action: Ensure that the specified object type, function name, or both is valid for the object path.
CWYIS6021W: The {0} key does not exist on the specified keyed data queue {1}.
Explanation: For the GETQUEUE operation to be successful, a key must exist and have at least one corresponding message.
User Action: Ensure that the key exists and that it contains at least one message.