- CWYFF0001E: A function name is not specified.
- Explanation: None of the valid function names (CREATE, APPEND, OVERWRITE, RETRIEVE, LIST, EXISTS and DELETE) have been specified in the Interaction specification.
- User Action: Ensure that a valid function name is specified in the InteractionSpec.
- CWYFF0002E: The specified function name is not supported.
- Explanation: None of the valid function names (CREATE, APPEND, OVERWRITE, RETRIEVE, LIST, EXISTS and DELETE) have been specified in the Interaction specification.
- User Action: Ensure that a valid function name is specified in the InteractionSpec.
- CWYFF0003E: The file to which data had to be appended does not exist.
- Explanation: For the APPEND operation, the file to which data has to be appended should already exist in the file system.
- User Action: Ensure that the file to which the data has to be appended exists in the file system.
- CWYFF0004E: The file to be created already exists.
- Explanation: For the CREATE operation, the file that has to be created should not already exist in the file system.
- User Action: Ensure that the file to be created does not already exist in the file system.
- CWYFF0005E: The file from which the content needs to be retrieved does not exist.
- Explanation: For the RETRIEVE operation, the file from which the content needs to be retrieved should already exist in the file system.
- User Action: Ensure that the file from which the content needs to be retrieved is present in the file system.
- CWYFF0006E: The file whose content has to be overwritten does not exist.
- Explanation: For the OVERWRITE operation, the file whose content needs to be overwritten should already exist in the file system.
- User Action: Ensure that the file whose content has to be overwritten exists in the file system.
- CWYFF0007E: The file to be deleted does not exist.
- Explanation: For the DELETE operation, the file that needs to be deleted should already exist in the file system.
- User Action: Ensure that the file to be deleted exists in the file system.
- CWYFF0008E: The directory whose content needs to be listed does not exist.
- Explanation: For LIST operation, the directory whose content needs to be listed must already exist in the file system.
- User Action: Ensure that the directory whose content needs to be listed exists in the file system.
- CWYFF0009E: The specified directory path is not valid.
- Explanation: The specified directory path might not exist in file system or might contain invalid characters.
- User Action: Specify a valid directory path.
- CWYFF0010E: The specified directory does not have read permission.
- Explanation: For the operation to succeed, the specified directory should have read permission.
- User Action: Ensure that the specified directory has read permission.
- CWYFF0011E: The specified file name is not valid.
- Explanation: The specified file name might contain characters that are not valid for a file name.
- User Action: Specify a valid file name.
- CWYFF0012F: The specified EventFileMask is not valid.
- Explanation: The EventFileMask contains invalid characters. The EventFileMask only matches text based on wildcard (*) matching.
- User Action: Specify a valid EventFileMask.
- CWYFF0013F: The specified value for PollPeriod is invalid.
- Explanation: The PollPeriod value(in milliseconds) should have a non-negative integer value.
- User Action: Specify a valid PollPeriod value.
- CWYFF0014F: The specified value for PollQuantity invalid.
- Explanation: The PollQuantity should have a positive integer value.
- User Action: Specify a valid PollQuantity.
- CWYFF0015F: The EDTDriverName is not specified.
- Explanation: A valid EDTDriver name must be specified for the inbound event processing to function.
- User Action: Specify a valid value for EDTDriverName.
- CWYFF0016F: The EDTDatabaseName is not specified.
- Explanation: For inbound event processing to fuction, a valid EDTDatabaseName name must be specified.
- User Action: Specify a valid value for EDTDatabaseName.
- CWYFF0017F: The EDTUserName is not specified.
- Explanation: For inbound event processing to fuction, a valid EDTUserName name must be specified.
- User Action: Specify a valid EDTUserName value.
- CWYFF0018F: The EDTUserPassword is not specified.
- Explanation: For inbound event processing to fuction, a valid EDTUserPassword name must be specified.
- User Action: Specify a valid EDTUserPassword value.
- CWYFF0019F: The FFEventTableName is not specified.
- Explanation: For inbound event processing to fuction, a valid FFEventTableName name must be specified.
- User Action: Specify a valid FFEventTableName value.
- CWYFF0020F: Could not connect to the database with the given parameters.
- Explanation: For inbound event processing to fuction, the specified database parameters must be valid and the database needs to be active.
- User Action: Ensure that the database parameters are correct and that the database is active.
- CWYFF0021F: The adapter could not execute the SQL statement.
- Explanation: The adapter could not execute the SQL statement. The database needs to be active for the inbound event processing to function.
- User Action: Ensure that the database is active.
- CWYFF0022F: The specified SortEventFiles is not valid.
- Explanation: The valid values for SortEventFiles are Filename, Timestamp and BLANK.
- User Action: Specify a valid SortEventFiles value.
- CWYFF0023W: Unable to close database connection.
- Explanation: An error occurred while closing the database connection. The database needs to be active for the inbound event processing to function.
- User Action: Ensure that the database is active.
- CWYFF0024F: The specified EventDirectory is invalid.
- Explanation: The specified EventDirectory might either contain invalid characters or not exist in the file system.
- User Action: Specify a valid EventDirectory.
- CWYFF0025F: The specified ArchiveDirectory is invalid.
- Explanation: The specified ArchiveDirectory might either contain invalid characters or not exist in the file system.
- User Action: Specify a valid ArchiveDirectory.
- CWYFF0026F: The specified EventDirectory does not have read or write or both the permissions.
- Explanation: For the adapter to perform its inbound functions properly, the EventDirectory should have both the read and write permissions.
- User Action: Ensure that the specified EventDirectory has both read and write permissions.
- CWYFF0027F: The specified ArchiveDirectory does not have write permission.
- Explanation: For the adapter to perform its inbound functions properly, the ArchiveDirectory should have write permission.
- User Action: Ensure that the specified ArchiveDirectory has write permission.
- CWYFF0028E: The specified directory does not have write permission.
- Explanation: The specified directory should have write permission for the operation to succeed.
- User Action: Ensure that the specified directory has write permission.
- CWYFF0029E: The specified file does not have read permission.
- Explanation: The specified file must have read permission for this operation to succeed.
- User Action: Ensure that the specified file has read permission.
- CWYFF0030E: The specified file does not have write permission.
- Explanation: The specified file must have write permission for this operation to succeed.
- User Action: Ensure that the specified file has write permission.
- CWYFF0031E: The delete operation has failed.
- Explanation: The file to be deleted might be locked by another program.
- User Action: Ensure that the file being deleted is not being used by another program.
- CWYFF0032F: The specified FileChunkSize is invalid.
- Explanation: The FileChunkSize should have a positive integer value when FileSplitThreshold is non-negative.
- User Action: Specify a valid FileChunkSize value.
- CWYFF0033F: The specified FileSplitThreshold is invalid.
- Explanation: The FileSplitThreshold should be either -1, zero, or a positive integral value.
- User Action: Specify a valid FileSplitThreshold value.
- CWYFF0034E: The specified output record is invalid.
- Explanation: The output record passed as an argument to the execute method of the Interaction should not be null and should have a valid data structure.
- User Action: Specify a valid output record argument.
- CWYFF0035E: The specified input record specified is invalid.
- Explanation: The input record passed as an argument to the execute method of the Interaction should not be null and should have a valid data structure.
- User Action: Specify a valid input record argument.
- CWYFF0036E: The input record does not contain the input bytes required for this operation.
- Explanation: The CREATE, APPEND and OVERWRITE operations require input bytes as an argument.
- User Action: Pass the input bytes as an argument inside the input record for this operation.
- CWYFF0037E: The specified InteractionSpec is invalid.
- Explanation: The InteractionSpec passed as an argument to the execute method of the Interaction is either null or is an invalid instance.
- User Action: Specify a valid InteractionSpec argument.
- CWYFF0038F: The FFDatabaseName is not specified.
- Explanation: A valid FFDatabaseName name must be specified for the inbound event processing to function.
- User Action: Specify a valid FFDatabaseName value.
- CWYFF0041E: An error occurred while instantiating the file object.
- Explanation: Either the file does not exist or it is locked
- User Action: The file path and name is incorrect. Ensure that the path is valid and that the file exists in the specified path.
- CWYFF0042E: An error occurred while retrieving the business object content.
- Explanation: Check the content of the event file.
- User Action: The event file might be empty.
- CWYFF0043E: An error occurred while fetching the total number of business objects in the file.
- Explanation: The total number of business objects could not be obtained due to invalid event file or delimiter.
- User Action: Verify that the event file and delimiter are correct.
- CWYFF0044E: EndBODelimiter is set to an invalid value.
- Explanation: Delimiter is set to an unsupported format.
- User Action: Set a valid value for the EndBODelimiter.
- CWYFF0045E: The specified delimiter does not exist in the event file.
- Explanation: A delimiter value could not be found in the event file. Ensure that the specified delimiter exists in the event file.
- User Action: Configure a delimiter that exists in the event file.
- CWYFF0046E: The file exists in the specified location, but is not accessible.
- Explanation: File might be locked by an external application or might not have sufficient access permissions.
- User Action: Ensure that the file has the required permissions and no external application has a lock on the file.
- CWYFF0047E: The configured encoding is not supported.
- Explanation: The encoding specified may not be a valid value.
- User Action: Specify a valid encoding.
- CWYFF0061E: An error occurred while copying the file {0} to {1}.
- Explanation: An error occurred while copying the file from one directory to the other.
- User Action: Ensure that the file is available for copying.
- CWYFF0062E: An error occurred while renaming the file from {0} to {1}.
- Explanation: Check if the files are locked by an external process.
- User Action: Ensure that the file is not locked by an external process.
- CWYFF0063E: An error occurred while deleting the file {0}.
- Explanation: The file could not be deleted through the program; The file might be locked.
- User Action: Ensure that the file is not locked by an external process.
- CWYFF0064E: An error occurred while validating the Delivery Type, which should take a value of either ORDERED or UNORDERED. The value given for the delivery type is {0}
- Explanation: The delivery type should be either ORDERED or UNORDERED. This value determines the order in which the events will be published, either one at a time (ORDERED) or all at once (UNORDERED).
- User Action: Ensure that the delivery type is correct and that it takes a valid value.
- CWYFF0065I: Setting SplittingFunctionClassName to com.ibm.j2ca.utils.filesplit.SplitBySize
- Explanation: If SplittingFunctionClassName of the ActivationSpec is not set, then SplittingFunctionClassName is set to 'com.ibm.j2ca.utils.filesplit.SplitBySize' by default.
- User Action: No action is required.
- CWYFF0066E: An error occurred while validating SplittingFunctionClassName. It is not valid. The given value is {0}.
- Explanation: The SplittingFunctionClassName cannot be validated. A fully qualified class name must be used to split the file.
- User Action: Ensure that the SplittingFunctionClassName is a valid value. It should be a fully qualified class name.
- CWYFF0067E: An error occurred while validating the SplitCriteria. It is not valid for the selected SplittingFunctionClassName: {0}. SplitCriteria is {1}
- Explanation: The SplitCriteria value could not be validated. A valid value based on the SplittingFunctionClassName is required.
- User Action: Ensure that the SplitCriteria has a valid value and try again.
- CWYFF0068I: SplitCriteria is being set to 0 (no chunking of event file) because the SplitCriteria value provided is not valid for the specified SplittingFunctionClassName(com.ibm.j2ca.utils.filesplit.SplitBySize).
- Explanation: If the value for SplittingFunctionClassName is com.ibm.j2ca.utils.filesplit.SplitBySize, and SplitCriteria is not a valid number, then SplitCriteria is set to 0.
- User Action: No action is required.
- CWYFF0069E: The value set for FileContentEncoding property {0} is not supported.
- Explanation: The value specified for the FileContentEncoding property is not supported.
- User Action: Use a valid encoding supported by Java and try again.
- CWYFF0070E: An error occurred while retrieving the business object content as a byte[] from the event file present in EventDirectory for the event ID {0}.
- Explanation: An error occurred while retrieving the business object content from the event file when the file was parsed based on the SplitCriteria.
- User Action: This is a runtime error. Ensure that the file exists in the EventDirectory and try again. If you still receive an error message, the file might be corrupt.
- CWYFF0071E: An error occurred while archiving. The delivery type is {0}, the event file name: {1} , the current business object: {2} , the total business objects: {3} , the current business object status: {4}.
- Explanation: An error occurred while archiving each business object in the event file.
- User Action: Ensure that the event file exists in the EventDirectory and that it is not corrupt.
- CWYFF0072I: The DefaultObjectName value is being set to {0}.
- Explanation: If a value for DefaultObjectName or EventContentType is not set, the DefaultObjectName is set to the fully qualified namespace of FlatFileBG.
- User Action: No action is required.
- CWYFF0073E: An error occurred while validating the DefaultObjectName value, because it is invalid. DefaultObjectName = {0}
- Explanation: An instance of a business object with the specified DefaultObjectName value could not be created.
- User Action: Ensure that the DefaultObjectName is correct and that the required XSDs are available in the deployed application.
- CWYFF0074E: An error occurred while validating the BONamespace value because it is invalid. BONamespace = {0}
- Explanation: The BONamespace could not be validated.
- User Action: Ensure that the BONamespace value is correct, and try again.
- CWYFF1001I: Starting adapter.
- Explanation: Starting adapter.
- User Action: No action required.
- CWYFF1002F: An exception was caught: '{0}'
- Explanation: The EMD has encountered a severe error and cannot continue.
- User Action: See the exception message for more information.
- CWYFF1003W: An exception was caught: '{0}'
- Explanation: The EMD has encountered an error and cannot complete the current action.
- User Action: See the exception message for more information.
- CWYFF1004S: A wrong adapterTypeID {0} was encountered.
- Explanation: A wrong adapterTypeID was encountered.The EMD expects the type to be FlatFile Resource Adapter.Please ensure that the adapterTypeID is correct for the emd.
- User Action: Verify that the right adapterTypeID is being passed to the emd.
- CWYFF1005S: Failed to create Configuration properties for Import Configuration.Reason {0}
- Explanation: Unable to create Configuration properties for Import Configuration.
- User Action: Check the logs and take necessary steps to resolve the problem.
- CWYFF1006S: Failed to construct Metadata tree.Reason {0}
- Explanation: Failed to construct Metadata tree.
- User Action: Check the logs and take necessary steps to resolve the problem.
- CWYFF1007S: Failed to create Unified Properties.Reason {0}
- Explanation: Failed to retrieve top level objects.
- User Action: Check the logs and take necessary steps to resolve the problem.
- CWYFF1008S: Failed to create ActivationSpec Properties.Reason {0}
- Explanation: Failed to create ActivationSpec Properties.
- User Action: Check the logs and take necessary steps to resolve the problem.
- CWYFF1009S: Failed to create Resource Adapter Properties.Reason {0}
- Explanation: Failed to create Resource Adapter Properties.
- User Action: Check the logs and take necessary steps to resolve the problem.
- CWYFF1010S: Failed to create Inbound Connection Configuration.Reason {0}
- Explanation: Failed to create Inbound Connection Configuration.
- User Action: Check the logs and take necessary steps to resolve the problem.
- CWYFF1011S: Failed to create Outbound Connection Configuration.Reason {0}
- Explanation: Failed to create Outbound Connection Configuration.
- User Action: Check the logs and take necessary steps to resolve the problem.
- CWYFF9000E\: Bidi Transformation Error: An error occurred while creating the bidi context for the \'{0}\' property.
- Explanation: Bidi Transformation Error: The bidi context for the property cannot be created.
- User Action: Check the log and trace files, and correct any error indicated in the files.
- CWYFF9001E\: Bidi Transformation Error: An error occurred while transforming the business object \'{0}\'.
- Explanation: Bidi Transformation Error: A business object cannot be transformed.
- User Action: Check the log and trace files, and correct any error indicated in the files.
- CWYFF9002E\: Bidi Transformation Error: An error occurred while transforming the metadata property \'{0}\' for the business object.
- Explanation: Bidi Transformation Error: A metadata property for the business object cannot be transformed.
- User Action: Check the log and trace files, and correct any error indicated in the files.
- CWYFF9003E\: Bidi Transformation Error: An error occurred while transforming metadata property for attribute \'{0}\' for business object.
- Explanation: Bidi Transformation Error: A metadata property for an attribute of the business object cannot be transformed.
- User Action: Check the log and trace files, and correct any error indicated in the files.
- CWYFF9004E\: Bidi Transformation Error: An error occurred while transforming the metadata configuration property \'{0}\'.
- Explanation: Bidi Transformation Error: A metadata configuration property cannot be transformed.
- User Action: Check the log and trace files, and correct any error indicated in the files.
- CWYFF9005E\: Bidi Validation Error: An error occurred while validating bidi properties for metadata configuration property.
- Explanation: Bidi Validation Error: A bidi property for the metadata configuration property cannot be validated.
- User Action: Check the log and trace files, and correct any error indicated in the files.