BFGIO0001 - BFGIO9999

BFGIO0001E: File "<insert_0>" does not exist.
Severity: 20 : Error
Explanation: The system was unable to find the file specified.
Response: Ensure that the file exists and that the file is accessible.

BFGIO0002E: File "<insert_0>" is not a normal file (it might be a directory).
Severity: 20 : Error
Explanation: The system was unable to find the file specified. A normal file is a file that is not a directory and meets other criteria depending on the system.
Response: Ensure that the file exists and that the file is accessible.

BFGIO0003E: Unable to open file "<insert_0>" for reading.
Severity: 20 : Error
Explanation: The system was unable to read the file specified.
Response: Ensure that the file's access permissions allow the file to be read.

BFGIO0006E: File "<insert_0>" already exists.
Severity: 20 : Error
Explanation: The system was unable to create the file specified because the file already exists.
Response: Remove the existing file or specify an alternative file name.

BFGIO0007E: Unable to create directory "<insert_0>" for new file "<insert_1>".
Severity: 20 : Error
Explanation: The system was unable to create the directory path specified.
Response: Ensure you have the correct access to create the specified path.

BFGIO0012E: Unable to create directory "<insert_0>" for file <insert_1> because a normal file already exists in its place.
Severity: 20 : Error
Explanation: The system was unable to create the directory required for the file because a normal file is already present. A normal file is a file that is not a directory and meets other criteria depending on the system.
Response: Remove the existing file or specify an alternative directory path.

BFGIO0014E: An internal error has occurred. Invalid type identifier ("<insert_0>") for FileChannelState recovery
Severity: 20 : Error
Explanation: This exception is unexpected. The cause is not immediately known.
Response: If the problem persists, see problem determination information in the product documentation.

BFGIO0015E: An internal error has occurred. Incompatible FileChannelState version ("<insert_0>")
Severity: 20 : Error
Explanation: This exception is unexpected. The cause is not immediately known.
Response: If the problem persists, see problem determination information in the product documentation.

BFGIO0016E: An internal error has occurred. Invalid state data (<insert_0>)
Severity: 20 : Error
Explanation: This exception is unexpected. The cause is not immediately known.
Response: If the problem persists, see problem determination information in the product documentation.

BFGIO0017E: An internal error has occurred. The channel is already open for the file <insert_0>
Severity: 20 : Error
Explanation: This exception is unexpected. The cause is not immediately known.
Response: If the problem persists, see problem determination information in the product documentation.

BFGIO0020E: An internal error has occurred. The buffer is invalid for channel (position must be 0 and buffer limit less than or equal to <insert_0>)
Severity: 20 : Error
Explanation: This exception is unexpected. The cause is not immediately known.
Response: If the problem persists, see problem determination information in the product documentation.

BFGIO0021E: The attributes for the destination data set (<insert_0>) are not compatible for the transfer. In particular the <insert_1> attribute for the transfer is <insert_2> but the data set''s value is <insert_3>.
Severity: 20 : Error
Explanation: There are a number of rules that determine whether or not a destination data set is compatible for a transfer. For example, the LRECL attribute for the destination data set must be greater or equal the transfer or source data set LRECL value. For a complete set of rules refer to the IBM MQ Managed File Transfer documentation.
Response: Select a compatible destination data set or remove any incompatible destination data set attribute overrides that are specified for the transfer.

BFGIO0022E: The destination data set <insert_0> is VSAM, but a non-VSAM data set is required.
Severity: 20 : Error
Explanation: It is not possible to transfer data between non-VSAM and VSAM data sets.
Response: Select a compatible source or destination data set or remove any incompatible destination data set attribute overrides that are specified for the transfer.

BFGIO0023E: Failed to allocate DDName for data set. Reason: <insert_0> [<insert_1>. DYNALLOC error reason code (S99ERROR) 0x<insert_2> and information reason code (S99INFO) 0x<insert_3>]. Allocate command used: "<insert_4>"
Severity: 20 : Error
Explanation: The allocation of the required data set for the transfer failed.
Response: The allocation failure reported can be diagnosed using the z/OS Information Center, section "z/OS UNIX", subsection "Using REXX and z/OS UNIX System Services", subsection "BPXWDYN", subsection "Return codes". You can find the z/OS Information Centers here: http://www.ibm.com/systems/z/os/zos/bkserv/ This information is also in publication SA22-7806 "Using REXX and z/OS UNIX System Services". Consider specifying a different destination data set or alternative data set attributes for a new destination data set, or correct the problem at the destination system.

BFGIO0024E: An internal error has occurred. Invalid size specified for <insert_0>. Size specified was <insert_1>, but the data set requires a record size of <insert_2>
Severity: 20 : Error
Explanation: This exception is unexpected. The cause is not immediately known.
Response: If the problem persists, see problem determination information in the product documentation.

BFGIO0025E: A fixed block data set (<insert_0>) was specified, but the BLKSIZE (<insert_1>) is not a multiple of the LRECL (<insert_2>)
Severity: 20 : Error
Explanation: BLKSIZE must be a multiple of the LRECL for a fixed block format record data set.
Response: Correct the specified data set attributes.

BFGIO0026E: An internal error has occurred. FileSlice (size: <insert_0>bytes) is too small for data set record, FileSlice must be <insert_1>bytes
Severity: 20 : Error
Explanation: This exception is unexpected. The cause is not immediately known.
Response: If the problem persists, see problem determination information in the product documentation.

BFGIO0027E: An internal error has occurred. FileSlice with position <insert_0> was expected, but received FileSlice is at position <insert_1>
Severity: 20 : Error
Explanation: This exception is unexpected. The cause is not immediately known.
Response: If the problem persists, see problem determination information in the product documentation.

BFGIO0028E: Data set <insert_0> was specified for a <insert_1> platform. Data sets are supported on z/OS only for a non-protocol bridge MQMFT agent.
Severity: 20 : Error
Explanation: Data sets are accessible from a standard agent running on z/OS only.
Response: Check the correct agent was specified or that you really intended to specify a data set for the transfer.

BFGIO0029E: An internal error has occurred. Unexpectedly reached the end of file (at position <insert_0>) while attempting to read slice <insert_1>.
Severity: 20 : Error
Explanation: This exception is unexpected. The cause is not immediately known.
Response: If the problem persists, see problem determination information in the product documentation.

BFGIO0030E: Cannot process file <insert_0> because the file contains a line length greater than the maximum supported of <insert_1>.
Severity: 20 : Error
Explanation: The text translation algorithm processes text files on a line by line basis. This requires that an entire line of text is present in memory before the line can be processed, hence a maximum line length is imposed.
Response: Check that the source file is correctly encoded and has the correct line ending characters for the platform. If the destination is a z/OS data set, ensure its LRECL/BLKSIZE setting is sufficient to support the maximum line length for the source.

BFGIO0031E: An internal error has occurred. File <insert_0> is already closed.
Severity: 20 : Error
Explanation: This exception is unexpected. The cause is not immediately known.
Response: If the problem persists, see problem determination information in the product documentation.

BFGIO0032E: An internal error has occurred. Insufficient data for checksum state (expected <insert_0> bytes, received <insert_1> bytes)
Severity: 20 : Error
Explanation: This exception is unexpected. The cause is not immediately known.
Response: If the problem persists, see problem determination information in the product documentation.

BFGIO0033E: There is an invalid checksum for file <insert_0> and recovery is not possible.
Severity: 20 : Error
Explanation: A transfer of the file failed part way through. During the recovery operation the system discovered the contents of the file had been changed.
Response: Resubmit the transfer request again, if required.

BFGIO0034E: An internal error has occurred. File <insert_0> is already closed.
Severity: 20 : Error
Explanation: This exception is unexpected. The cause is not immediately known.
Response: If the problem persists, see problem determination information in the product documentation.

BFGIO0035E: An internal error has occurred. The serialized state for GenericTextConverter is not valid.
Severity: 20 : Error
Explanation: This exception is unexpected. The cause is not immediately known.
Response: If the problem persists, see problem determination information in the product documentation.

BFGIO0036E: An internal error has occurred. The position <insert_0> for data set <insert_1> is not valid
Severity: 20 : Error
Explanation: This exception is unexpected. The cause is not immediately known.
Response: If the problem persists, see problem determination information in the product documentation.

BFGIO0037E: <insert_0> Attributes specified: <insert_1>
Severity: 20 : Error
Explanation: The allocation of the required data set for the destination of the transfer failed.
Response: Look up the reason code information and view the MVS system log on the destination host for a description of why the allocation failed. Consider specifying a different destination data set or alternative data set attributes for a new destination data set.

BFGIO0038E: An internal error has occurred. Unable to release lock for file <insert_0>
Severity: 20 : Error
Explanation: This exception is unexpected. The cause is not immediately known.
Response: If the problem persists, see problem determination information in the product documentation.

BFGIO0039E: A data set (<insert_0>) was specified, but the BLKSIZE (<insert_1>) is not a valid integer in the range <insert_2> - <insert_3>.
Severity: 20 : Error
Explanation: BLKSIZE must be an integer value in the correct range.
Response: Correct the specified BLKSIZE data set attribute.

BFGIO0040E: A data set (<insert_0>) was specified, but the LRECL (<insert_1>) is not a valid integer in the range <insert_2> - <insert_3>.
Severity: 20 : Error
Explanation: LRECL must be an integer value in the correct range.
Response: Correct the specified LRECL data set attribute.

BFGIO0041E: Unable to lock file "<insert_0>" for reading.
Severity: 20 : Error
Explanation: The system was unable to lock the file specified.
Response: Ensure that the file is not already locked.

BFGIO0042E: Unable to lock file "<insert_0>" for writing.
Severity: 20 : Error
Explanation: The system was unable to lock the file specified.
Response: Ensure that the file is not already locked.

BFGIO0043E: Unable to lock data set "<insert_0>" for reading.
Severity: 20 : Error
Explanation: The system was unable to lock the data set specified.
Response: Ensure that the data set is not already locked.

BFGIO0044E: Unable to lock data set "<insert_0>" for writing.
Severity: 20 : Error
Explanation: The system was unable to lock the data set specified.
Response: Ensure that the data set is not already locked.

BFGIO0045E: The specified data set name <insert_0> is not a valid data set name.
Severity: 20 : Error
Explanation: The specified data set is not a valid z/OS data set name.
Response: Specify a valid data set name.

BFGIO0046E: An internal error has occurred. The FTEFileIOWorker thread has failed to shut down in the specified interval of <insert_0> milliseconds.
Severity: 20 : Error
Explanation: This exception is unexpected. The cause is not immediately known.
Response: If the problem persists, see problem determination information in the product documentation.

BFGIO0047E: Unable to generate a unique temporary file from <insert_0> with suffix <insert_1>.
Severity: 20 : Error
Explanation: A temporary file cannot be created because either a file with the same name already exists or there is an access permission problem.
Response: Ensure that you have write access to the directory to contain the output file {0} and that you remove any existing files in that directory that end with {1}. If the problem persists and cannot be resolved, contact the IBM support center.

BFGIO0048E: An internal error has occurred. Insufficient data for path name state (expected <insert_0> bytes, received <insert_1> bytes).
Severity: 20 : Error
Explanation: This exception is unexpected. The cause is not immediately known.
Response: If the problem persists, see problem determination information in the product documentation.

BFGIO0049E: The rename of temporary file <insert_0> to <insert_1> failed.
Severity: 20 : Error
Explanation: Failed to rename a temporary file, used for the file transfer destination, to the required final name. The destination file might not be accessible.
Response: Manually attempt to rename the file, resolving any issues as required.

BFGIO0050E: Failed to remove temporary file <insert_0>.
Severity: 20 : Error
Explanation: The temporary file used during the transfer could not be deleted.
Response: Check that the temporary file still exists and attempt to delete the temporary file manually.

BFGIO0051E: Unable to generate a unique temporary data set or PDS member from <insert_0> with suffix <insert_1>.
Severity: 20 : Error
Explanation: A temporary data set or PDS member cannot be created because either a data set or PDS member with the same name already exists or there is an access permission problem.
Response: Ensure that there is sufficient permission to create data set or PDS member {1} and remove any existing data sets or PDS members with names that end with {1}. If the problem persists and cannot be resolved, contact the IBM support center.

BFGIO0052E: The source data BLKSIZE of <insert_1> is not compatible with the PDSE data set <insert_0>. BLKSIZE must be in the range <insert_2> - <insert_3>.
Severity: 20 : Error
Explanation: BLKSIZE must be an integer value in the correct range.
Response: Select a compatible destination data set or update any specified BLKSIZE attribute override to be compatible.

BFGIO0053E: The attributes for the destination data set <insert_0> are not compatible with the required attributes of the transfer. Maximum record data length supported by the destination data set is <insert_2>, but the transfer''s required record data length is <insert_1>.
Severity: 20 : Error
Explanation: Taking into account the data set BLKSIZE, LRECL and RECFM settings the maximum record data length supported by the destination data set is less than the maximum required record data length.
Response: Select a compatible destination data set or remove or update any incompatible destination data set attribute overrides specified for the transfer.

BFGIO0054E: The source data BLKSIZE of <insert_1> is not compatible with PDSE data set <insert_0>. BLKSIZE must be in the range <insert_2> - <insert_3>.
Severity: 20 : Error
Explanation: BLKSIZE must be an integer value in the correct range.
Response: Correct the specified BLKSIZE data set attribute.

BFGIO0055E: An internal error has occurred. Reblocking of destination data set <insert_0> is not supported. Reblocking is valid only for PDSE data sets.
Severity: 20 : Error
Explanation: This exception is unexpected. The cause is not immediately known.
Response: If the problem persists, see problem determination information in the product documentation.

BFGIO0056E: Attempt to read file "<insert_0>" has been denied. The file is located outside of the restricted transfer sandbox.
Severity: 20 : Error
Explanation: The system was unable to read the specified file as it is not within the restricted transfer sandbox. Please note that if the commandPath property has been defined, all of the commandPath directories will be excluded from the restricted sandbox by default.
Response: Ensure that the specified location is within the restricted sandbox. For further information, refer to the IBM MQ Managed File Transfer documentation.

BFGIO0057E: The attempt to write file "<insert_0>" has been denied. The file is located outside of the restricted transfer sandbox.
Severity: 20 : Error
Explanation: The system was unable to write to the specified file as it is not within the restricted transfer sandbox. Please note that if the commandPath property has been defined, all of the commandPath directories will be excluded from the restricted sandbox by default.
Response: Ensure that the specified location is within the restricted sandbox. For further information, refer to the IBM MQ Managed File Transfer documentation.

BFGIO0058E: The transfer source encoding <insert_0> is not legal or is for an unsupported character set.
Severity: 20 : Error
Explanation: The destination agent was unable to recognise the character set for the required source encoding. If the default source encoding is used then this error implies the destination agent's Java SDK is not compatible with the source agent's system.
Response: If a source encoding has been specified ensure it specifies a valid encoding as recognised by the destination agent's Java SDK. If the default source encoding is used and is expected to be compatible with the destination agent then ensure all maintenance has been applied. If the problem persists and cannot be resolved, contact the IBM support center.

BFGIO0059E: The transfer destination encoding <insert_0> is not legal as it is for an unsupported character set.
Severity: 20 : Error
Explanation: The destination agent was unable to recognise the character set for the required destination encoding.
Response: If a destination encoding has been specified ensure it specifies a valid encoding as recognised by the destination agent's Java SDK. If the problem persists and cannot be resolved, contact the IBM support center.

BFGIO0060E: Text data conversion has failed (reason: <insert_0>)
Severity: 20 : Error
Explanation: The text data conversion from source encoding to the destination encoding is not possible. Usually this error occurs because there is a character in the source file than cannot be mapped to the destination encoding.
Response: If the problem is due to an unmappable character consider defining the textReplacementCharacterSequence agent property. If the problem persists and cannot be resolved, contact the IBM support center.

BFGIO0061E: Unable to open file "<insert_0>" for writing.
Severity: 20 : Error
Explanation: The system was unable to write to the file specified.
Response: Ensure that the file's access permissions allow the file to be written.

BFGIO0062E: An internal error has occurred. setState for an open data set channel is not supported
Severity: 20 : Error
Explanation: This exception is unexpected. The cause is not immediately known.
Response: If the problem persists, see problem determination information in the product documentation.

BFGIO0063E: Failed to close data set <insert_0> due to error <insert_1>
Severity: 20 : Error
Explanation: The closing of a data set has failed due to a system error.
Response: Examine the system error to understand the cause and if appropriate attempt to resolve the problem. If the problem persists and cannot be resolved, contact the IBM support center.

BFGIO0064E: Writing is complete but unexpected additional records are present at the end of data set <insert_0> (<insert_1> extra records)
Severity: 20 : Error
Explanation: Writing to the data set was recovered after a transfer or MQMFT agent problem, but the source or destination data set content seems to have been changed (i.e. source data has been truncated or additional records added to the destination data set by another user).
Response: If an agent should fail ensure any files currently involved in a MQMFT transfer are not modified.

BFGIO0065E: An internal error has occurred. The source buffer contains a partial record. This is not supported for transfers between data sets
Severity: 20 : Error
Explanation: This exception is unexpected. The cause is not immediately known.
Response: If the problem persists, see problem determination information in the product documentation.

BFGIO0066E: An internal error has occurred. getState or close attempted with a partial incomplete block (<insert_0>) pending to be written to data set <insert_1>.
Severity: 20 : Error
Explanation: This exception is unexpected. The cause is not immediately known.
Response: If the problem persists, see problem determination information in the product documentation.

BFGIO0067E: An internal error has occurred. setState for an open file channel is not supported
Severity: 20 : Error
Explanation: This exception is unexpected. The cause is not immediately known.
Response: If the problem persists, see problem determination information in the product documentation.

BFGIO0068E: An internal error has occurred. The data set block is invalid (insufficient data or corrupt BDW/RDW)
Severity: 20 : Error
Explanation: This exception is unexpected. The cause is not immediately known.
Response: If the problem persists, see problem determination information in the product documentation.

BFGIO0069E: A write failed. The data set may be out of space
Severity: 20 : Error
Explanation: A system write operation failed to write to the data set. A common cause for this is the data set being full and could not be expanded to make space available.
Response: Either reallocate the data set to provide more space or choose an alternative destination data set. If necessary examine the additional system error message information to fully understand the issue.

BFGIO0070E: Failed to delete data set <insert_0>.
Severity: 20 : Error
Explanation: The destination data set created during a failed transfer could not be deleted.
Response: Check that the data set still exists and attempt to delete the data set manually.

BFGIO0071E: Transfer not possible as ''<insert_0>'' specifies a bad path, reason: ''<insert_1>''
Severity: 20 : Error
Explanation: The system has detected a problem with the specified file path and hence is unable to access the file.
Response: Either ignore the failed transfer (since the path is likely to be invalid) or specify an alternative source path.

BFGIO0072E: A transfer of a directory referenced by the symbolic link ''<insert_0>'' is not supported.
Severity: 20 : Error
Explanation: The system doesn't support transfer of symbolic linked directories, due to the potential for defining an infinite path.
Response: Either ignore the failed transfer of the symbolic linked directory or specify an alternative source path.

BFGIO0073E: Failed to free DDName for data set <insert_2>. Free command used: "<insert_0>" reason: <insert_1>. Look up DYNALLOC error reason code (S99ERROR) 0x<insert_3> and information reason code (S99INFO) 0x<insert_4> in the "z/OS MVS Authorized Assembler Services Guide" z/OS manual, section "Interpreting DYNALLOC Return Codes", to fully understand the error.
Severity: 20 : Error
Explanation: The free of the required data set for the transfer failed.
Response: Look up the reason code information and view the MVS system log on the host for a description of why the free failed. If the problem persists and cannot be resolved, contact the IBM support center.

BFGIO0074W: An internal error has occurred. The attributes for data set <insert_0> are not available, since the format-1 DSCB not available (data set could be on tape). Additional information: <insert_1>
Severity: 10 : Warning
Explanation: This exception is unexpected. The cause is not immediately known.
Response: If the problem persists, see problem determination information in the product documentation.

BFGIO0075E: The specified name <insert_0> does not specify a valid PDS member name.
Severity: 20 : Error
Explanation: The specified name does not conform to a valid PDS member name. See z/OS documentation for the required format. This error can be caused by specifying a destination PDS member name for a transfer where a PDS data set name is required (i.e. on the command line a PDS member name is specified for the -dp option).
Response: Specify a valid PDS or PDS member name as appropriate.

BFGIO0076E: The specified data set <insert_0> exists but is not a PDS or PDSE data set.
Severity: 20 : Error
Explanation: A PDS or PDSE data set was expected but the specified existing data set is not a PDS or PDSE data set. This error can be caused by specifying the destination PDS instead of the destination data set option (-dp instead of -ds on the command line) for a transfer.
Response: Review the transfer specification and check that a destination partitioned data set (-dp option on the command line) was not erroneously specified for the destination or the specified destination data set was incorrectly specified.

BFGIO0077E: Open failed.
Severity: 20 : Error
Explanation: A system operation failed to open the data set. Common causes for this are not having the required permission to access the data set or an out of space issue during a transfer recovery operation.
Response: Either change the data set access rights or choose an alternative data set. If necessary examine the additional system error message information to fully understand the issue.

BFGIO0078E: A file read failed due to a Java IOException with message text <insert_0>
Severity: 20 : Error
Explanation: A system operation failed to read the file.
Response: Check the text of the Java IOException for possible reasons for the error.

BFGIO0079E: A file write failed due to a Java IOException with message text <insert_0>
Severity: 20 : Error
Explanation: A system operation failed to write the file.
Response: Check the text of the Java IOException for possible reasons for the error.

BFGIO0080E: A file close failed due to a Java IOException with message text <insert_0>
Severity: 20 : Error
Explanation: A system operation failed to close the file.
Response: Check the text of the Java IOException for possible reasons for the error.

BFGIO0081E: A transfer of a file failed to complete due to a Java IOException with message text <insert_0>
Severity: 20 : Error
Explanation: A system operation failed.
Response: Check the text of the Java IOException for possible reasons for the error.

BFGIO0082E: A file open for read failed due to a Java IOException with message text <insert_0>
Severity: 20 : Error
Explanation: A system operation failed to open the file.
Response: Check the text of the Java IOException for possible reasons for the error.

BFGIO0083E: A file open for write failed due to a Java IOException with message text <insert_0>
Severity: 20 : Error
Explanation: A system operation failed to open the file.
Response: Check the text of the Java IOException for possible reasons for the error.

BFGIO0084E: Close failed.
Severity: 20 : Error
Explanation: A system operation failed to close the data set.
Response: Examine the additional system error message information to fully understand the issue.

BFGIO0085E: Read failed.
Severity: 20 : Error
Explanation: A system operation failed to read the data set.
Response: Examine the additional system error message information to fully understand the issue.

BFGIO0086E: Reopen failed.
Severity: 20 : Error
Explanation: A system operation failed to reopen the data set.
Response: Examine the additional system error message information to fully understand the issue.

BFGIO0087E: Access denied to PDS.
Severity: 20 : Error
Explanation: A system operation failed to access the PDS directory or one of its members.
Response: Examine the additional system error message information to fully understand the issue.

BFGIO0088E: Failed status file slice recieved by receiving agent, indicating there is a problem with the source file on the sending agent. File slice is: ''<insert_0>''
Severity: 20 : Error
Explanation: Received file slices with a failed status indicate that the source agent has detected an I/O error whilst opening or reading the source file for a transfer. The details of the failure should be reported by the sending agent and hence this message should not normally be seen.
Response: If the problem persists, see problem determination information in the product documentation.

BFGIO0089E: File channel is in the closed state for a received file slice, indicating there is a problem with the destination file. File slice is: ''<insert_0>''
Severity: 20 : Error
Explanation: A receiver channel for a file has had a problem (normally a write failure) and hence cannot process the file slice received from the source agent. The details of the original failure should be reported by the receiving agent and hence this message should not normally be seen.
Response: If the problem persists, see problem determination information in the product documentation.

BFGIO0090E: Receiver channel is null for a received file slice, indicating there is a problem with the destination file. File slice is: ''<insert_0>''
Severity: 20 : Error
Explanation: A receiver channel for a file has had a problem (i.e. could not be opened) and hence cannot process the file slice received from the source agent. The details of the original failure should be reported by the receiving agent and hence this message should not normally be seen.
Response: If the problem persists, see problem determination information in the product documentation.

BFGIO0091E: Source data contains a blank line for a machine print-control coded data set ''<insert_0>''. This is not permitted.
Severity: 20 : Error
Explanation: Empty records (blank lines) are not permitted for a machine print-control coded data set.
Response: Ensure the source does not contain any blank lines or specify a non-machine print-control coded data set for the transfer destination.

BFGIO0092E: Source data contains an empty record for an ASA or machine print-control coded data set ''<insert_0>''. This is not permitted.
Severity: 20 : Error
Explanation: Empty records are not permitted for an ASA or machine print-control coded data set.
Response: Ensure the source does not contain any empty records or specify a non-ASA or non-machine print-control coded data set for the transfer destination.

BFGIO0093E: The rename of PDS member <insert_0> to a temporary name failed. Reason: <insert_1>
Severity: 20 : Error
Explanation: Failed to rename member to a temporary PDS member name, used for the file transfer destination.
Response: Examine the PDS to ensure new member may be created and that temporary names of the form FTEhhhhh (where hhhhh is up to five hex digits) do not already exist.

BFGIO0094E: Failed to delete PDS member <insert_0>. Reason: <insert_1>
Severity: 20 : Error
Explanation: The destination PDS member created during a failed transfer could not be deleted.
Response: Check that the PDS member still exists and attempt to delete the member manually.

BFGIO0095E: A record format of <insert_1> was specified for data set <insert_0>, but the specified LRECL and BLKSIZE are not equal (BLKSIZE=<insert_2> LRECL=<insert_3>).
Severity: 20 : Error
Explanation: BLKSIZE and LRECL are required to be equal for a non-blocked fixed format data set.
Response: Correct the specified data set attributes.

BFGIO0096E: An incorrect record format of <insert_1> was specified for a partitioned data set <insert_0>
Severity: 20 : Error
Explanation: RECFM of FS or FBS is not supported with BPAM.
Response: Correct the specified data set attributes.

BFGIO0097E: No FTEFileFactoryHelpers available. MQMFT File I/O is not possible.
Severity: 20 : Error
Explanation: This exception is unexpected. The cause is not immediately known.
Response: If the problem persists, see problem determination information in the product documentation.

BFGIO0098E: File "<insert_0>" already exists.
Severity: 20 : Error
Explanation: The system was unable to create the file specified because the file already exists.
Response: Remove the existing file or specify an alternative file name.

BFGIO0099E: The rename of temporary file <insert_0> to <insert_1> failed.
Severity: 20 : Error
Explanation: Failed to rename a temporary file, used for the file transfer destination, to the required final name. The destination file might already exist or the destination file might not be accessible.
Response: Manually attempt to rename file {0} to {1} resolving any issues as required.

BFGIO0100E: Failed to remove temporary file <insert_0>.
Severity: 20 : Error
Explanation: The temporary file used during the transfer could not be deleted.
Response: Check that the temporary file still exists and attempt to delete the temporary file manually.

BFGIO0101E: Internal error: Not a Bridge File object. Class name <insert_0>
Severity: 20 : Error
Explanation: This exception is unexpected. The cause is not immediately known.
Response: If the problem persists, see problem determination information in the product documentation.

BFGIO0102E: Internal error: No session object present. Transfer Ref <insert_0>
Severity: 20 : Error
Explanation: This exception is unexpected. The cause is not immediately known.
Response: If the problem persists, see problem determination information in the product documentation.

BFGIO0103E: Internal error: BridgeFileImpl called with no file path. Transfer Ref <insert_0>
Severity: 20 : Error
Explanation: This exception is unexpected. The cause is not immediately known.
Response: If the problem persists, see problem determination information in the product documentation.

BFGIO0104E: Internal error: Bad initialisation of start checksum. Transfer Ref <insert_0>
Severity: 20 : Error
Explanation: This exception is unexpected. The cause is not immediately known.
Response: If the problem persists, see problem determination information in the product documentation.

BFGIO0105E: Transfer to destination file <insert_0> in transfer reference <insert_1> could not be completed after an agent recovery as the original source file has been changed and does not match with what has been written to the destination.
Severity: 20 : Error
Explanation: The destination agent has either performed an agent recovery or the transfer has been restarted following an environmental problem in the network. During recovering this transfer the destination agent has discovered that additional data was written to the destination file by the destination agent which was beyond the recorded position. While this is not an error, when attempting to continue the transfer after recovery the supplied data from the source does not match what was written. As a result the transfer of this file is marked as a failure.
Response: Resubmit the transfer request.

BFGIO0106E: File "<insert_0>" is not a normal file (it might be a directory).
Severity: 20 : Error
Explanation: The system was unable to find the file specified. A normal file is a file that is not a directory and meets other criteria depending on the system.
Response: Ensure that the file exists and that the file is accessible.

BFGIO0107E: Internal error: Closing a new file <insert_0> with exception: <insert_1>
Severity: 20 : Error
Explanation: This exception is unexpected. The cause is not immediately known.
Response: If the problem persists, see problem determination information in the product documentation.

BFGIO0108E: Lost connection to server while performing a <insert_0> action.
Severity: 20 : Error
Explanation: The protocol bridge after a number of retries has been unable to reconnect to the server.
Response: Review the health of the associated server and check the connection between this protocol bridge and the server

BFGIO0109E: An internal error has occurred, a file object passed to protocol bridge was not one generated by the protocol bridge. File object type was <insert_0>
Severity: 20 : Error
Explanation: This exception is unexpected. The cause is not immediately known.
Response: If the problem persists, see problem determination information in the product documentation.

BFGIO0110E: File "<insert_0>" does not exist.
Severity: 20 : Error
Explanation: The system was unable to find the file specified.
Response: Ensure that the file exists and that the file is accessible.

BFGIO0111E: An internal error has occurred. Attempt to open a second input stream from the server within the same session. Second file was <insert_0>
Severity: 20 : Error
Explanation: This exception is unexpected. The cause is not immediately known.
Response: If the problem persists, see problem determination information in the product documentation.

BFGIO0112E: An internal error has occurred. Attempt to open a input stream from the server when an output stream was already present within the same session. Second file was <insert_0>
Severity: 20 : Error
Explanation: This exception is unexpected. The cause is not immediately known.
Response: If the problem persists, see problem determination information in the product documentation.

BFGIO0113E: An internal error has occurred. Attempt to open a second output stream from the server in the same session. Second file was <insert_0>
Severity: 20 : Error
Explanation: This exception is unexpected. The cause is not immediately known.
Response: If the problem persists, see problem determination information in the product documentation.

BFGIO0114E: An internal error has occurred. Attempt to open an output stream from the server when an input stream was already present in the same session. Second file was <insert_0>
Severity: 20 : Error
Explanation: This exception is unexpected. The cause is not immediately known.
Response: If the problem persists, see problem determination information in the product documentation.

BFGIO0115E: An internal error has occurred. Attempted to read from an input stream when it was not open. File was <insert_0>
Severity: 20 : Error
Explanation: This exception is unexpected. The cause is not immediately known.
Response: If the problem persists, see problem determination information in the product documentation.

BFGIO0116E: An internal error has occurred with a invalid slice. Expected slice position: <insert_0> but received slice: <insert_1> Slice details: <insert_2>
Severity: 20 : Error
Explanation: This exception is unexpected. The cause is not immediately known.
Response: If the problem persists, see problem determination information in the product documentation.

BFGIO0117E: Internal error: Attempt to stream from an non-opened file. File: <insert_0>
Severity: 20 : Error
Explanation: This exception is unexpected. The cause is not immediately known.
Response: If the problem persists, see problem determination information in the product documentation.

BFGIO0118E: An internal error has occurred. Attempt to open a input stream from the server when an output stream was already present within the same session. Second file was <insert_0>
Severity: 20 : Error
Explanation: This exception is unexpected. The cause is not immediately known.
Response: If the problem persists, see problem determination information in the product documentation.

BFGIO0119E: An internal error has occurred. Attempt to open a output stream from the server when an input stream was already present in the saem session. Second file was <insert_0>
Severity: 20 : Error
Explanation: This exception is unexpected. The cause is not immediately known.
Response: If the problem persists, see problem determination information in the product documentation.

BFGIO0120E: Lost connection to server while performing a <insert_0> action.
Severity: 20 : Error
Explanation: The protocol bridge after a number of retries has been unable to reconnect to the server.
Response: Review the health of the associated server and check the connection between this protocol bridge and the server

BFGIO0121E: An internal error has occurred. Insufficient data for checksum state (expected <insert_0> bytes, received <insert_1> bytes)
Severity: 20 : Error
Explanation: This exception is unexpected. The cause is not immediately known.
Response: If the problem persists, see problem determination information in the product documentation.

BFGIO0122E: An internal error has occurred. A DataInputStream was expected but found <insert_0>
Severity: 20 : Error
Explanation: This exception is unexpected. The cause is not immediately known.
Response: If the problem persists, see problem determination information in the product documentation.

BFGIO0123E: An error was reported during an input stream operation. Reported exception was <insert_0>
Severity: 20 : Error
Explanation: The protocol bridge was reading data from its server when an error condition occurred. This could be a failure in the connection to the server.
Response: If this is a repeating occurrence investigate the connection and health of the server.

BFGIO0124E: An internal error has occurred. Insufficient data for checksum state (expected <insert_0> bytes, received <insert_1> bytes)
Severity: 20 : Error
Explanation: This exception is unexpected. The cause is not immediately known.
Response: If the problem persists, see problem determination information in the product documentation.

BFGIO0125E: File <insert_0> of transfer <insert_1> is already present on the protocol server, which has limited write configuration. The recovery of the transfer of this file cannot continue.
Severity: 20 : Error
Explanation: The protocol server has been configured for limited-write operation. The agent cannot append, overwrite, delete, or rename the file part that exists because of a previous incomplete transfer. The transfer cannot be recovered and has been marked as a failure.
Response: Review the contents of the file server and remove any existing destination files as necessary. Then resubmit a new transfer request.

BFGIO0126E: A previous error reported in this transfer has resulted in all files in this transfer being failed.
Severity: 20 : Error
Explanation: An earlier error report within the transfer had indicated a transfer wide error condition. This has resulted in all other file transfer attempts within the same transfer will be marked as failed.
Response: Review previous error message and act upon them.

BFGIO0127E: This agent will not transfer files specified using relative file paths: <insert_0>
Severity: 20 : Error
Explanation: The agent has been configured in such a way that it will not transfer files that have been specified using relative paths. The agent will only transfer files if they have been specified using an absolute path. The agent will not transfer the specified file.
Response: Resubmit the transfer request referencing files using absolute paths instead of relative paths for the file indicated in the message.

BFGIO0128E: Path ''<insert_0>'' could not be added to the sandbox as it is a relative path and the agent cannot determine the root directory to use when resolving relative paths to absolute paths.
Severity: 20 : Error
Explanation: The specified directory could not be added to the sandbox as it was specified as a relative path and the agent process cannot determine the root directory to use when resolving relative paths. The directory will be ignored.
Response: Specify the indicated directory using an absolute path. Restart the agent process.

BFGIO0129E: This agent will not transfer files specified using relative file paths: <insert_0>
Severity: 20 : Error
Explanation: The agent has been configured in such a way that it will not transfer files that have been specified using relative paths. The agent will only specify files if they have been specified using an absolute path. The agent will not transfer the specified file.
Response: Resubmit the transfer request referencing files using absolute paths instead of relative paths for the file indicated in the message.

BFGIO0131E: Unable to lock file "<insert_0>" for reading.
Severity: 20 : Error
Explanation: The system was unable to lock the specified source file due to another application already having the file open.
Response: Ensure the file is not in use and resubmit the transfer request.

BFGIO0132E: An internal error has occurred. Attempt to access a closed session by method <insert_0>.
Severity: 20 : Error
Explanation: This exception is unexpected. The cause is not immediately known.
Response: If the problem persists, see problem determination information in the product documentation.

BFGIO0133W: The maximum number of bridge sessions has been reached. Transfer <insert_0> cannot be processed at this time and will be re-queued.
Severity: 10 : Warning
Explanation: The configured maximum number of sessions the bridge agent is allowed to generated has been reached, so no additional sessions can be created. The transfer needs to be queued until such time there are free sessions.
Response: Review the protocolBridgeMaxSessions agent property. It should be in the order the sum of maxSourceTransfers and maxDestinationTransfers.

BFGIO0134E: An internal error has occurred. There are no available bridge sessions to process transfer <insert_0>.
Severity: 20 : Error
Explanation: This exception is unexpected. The cause is not immediately known.
Response: If the problem persists, see problem determination information in the product documentation.

BFGIO0135E: Unable to lock file "<insert_0>" for writing.
Severity: 20 : Error
Explanation: The system was unable to lock the specified destination file due to another application already having the file open.
Response: Ensure the file is not in use and resubmit the transfer request.

BFGIO0136E: The connection to the <insert_0> server at <insert_1> was lost while data was being written for a running transfer.
Severity: 20 : Error
Explanation: The protocol bridge was writing data to the server when an error condition occurred. This could be a failure in the connection to the server.
Response: If this is a repeating occurrence investigate the connection and health of the server.

BFGIO0138E: Transfer recovery of file ''<insert_0>'' has failed because <insert_1>.
Severity: 20 : Error
Explanation: Protocol bridge agent was attempting to recover an incomplete transferred file but has failed. The part written file is no longer recoverable.
Response: Review the supporting error message and investigate any potential problems it might be referencing on the file protocol server.

BFGIO0139E: Bad data buffer for variable blocked data set (length required: <insert_0>, buffer is: <insert_1>)
Severity: 20 : Error
Explanation: This exception is unexpected. The cause is not immediately known.
Response: If the problem persists, see problem determination information in the product documentation.

BFGIO0140E: Bad variable blocked record read from data set <insert_0> (maximum length expected: <insert_1>, actual length was: <insert_2>)
Severity: 20 : Error
Explanation: This exception is unexpected. The cause is not immediately known.
Response: If the problem persists, see problem determination information in the product documentation.

BFGIO0141E: The sandbox pattern <insert_0> contains a relative path, which cannot be resolved as the agent has not been configured with a transfer root.
Severity: 20 : Error
Explanation: The agent has not been configured with a transfer root. The agent cannot resolve the relative path specified in the named sandbox pattern. The agent is not able to use the sand-box configuration. If this problem occurs when the agent is starting then the agent process will end. If this problem occurs while the agent is running then updates to the sand-box configuration documet will be ignored until the problem is corrected.
Response: Either specify a transfer root in the agent's configuration or modify the sandbox configuration to specify absolute paths.

BFGIO0142E: The sandbox pattern <insert_0> contains a relative path, which cannot be resolved as the agent has not been configured with a transfer root.
Severity: 20 : Error
Explanation: The agent has not been configured with a transfer root. The agent cannot resolve the relative path specified in the named sandbox pattern. The agent is not able to use the sand-box configuration. If this problem occurs when the agent is starting then the agent process will end. If this problem occurs while the agent is running then updates to the sand-box configuration documet will be ignored until the problem is corrected.
Response: Either specify a transfer root in the agent's configuration or modify the sandbox configuration to specify absolute paths.

BFGIO0143E: A problem occurred while parsing the user sandbox document <insert_0>. Details of the problem are as follows: <insert_1>.
Severity: 20 : Error
Explanation: The user sandbox document could not be parsed for the specified reason. If this problem occurs when the agent is starting then the agent process will end. If this problem occurs while the agent is running then updates to the sand-box configuration documet will be ignored until the problem is corrected.
Response: Use the information in the message to resolve the problem with the sandbox document. The agent will periodically re-check the document and will update appropriately when the problem has been resovled.

BFGIO0144E: The sandbox user name pattern <insert_0>, specified in sandbox document <insert_1>, is not a valid regular expression. Details of the problem are as follows: <insert_2>.
Severity: 20 : Error
Explanation: The specified sandbox user name pattern is not a valid regular expression. If this problem occurs when the agent is starting then the agent process will end. If this problem occurs while the agent is running then updates to the sand-box configuration documet will be ignored until the problem is corrected.
Response: Use the information in the message to resolve the problem with the user name pattern. The agent will periodically re-check the document and will update appropriately when the problem has been resovled.

BFGIO0145E: The sandbox document file ''<insert_0>'' could not be read. Details of the problem are as follows: <insert_1>.
Severity: 20 : Error
Explanation: The file containing the specified sandbox document could not be read for the specified reason.
Response: Ensure that the sandbox document file is present and accessible to the agent process.

BFGIO0146E: A problem occured while reading the sandbox document file ''<insert_0>''. Details of the problem are as follows: <insert_1>.
Severity: 20 : Error
Explanation: The file containing the specified sandbox document could not be read for the specified reason.
Response: Use the information in the message to resolve the problem.

BFGIO0147E: A problem occurred while parsing the user sandbox document <insert_0>. Details of the problem are as follows: <insert_1>.
Severity: 20 : Error
Explanation: The user sandbox document could not be parsed for the specified reason. If this problem occurs when the agent is starting then the agent process will end. If this problem occurs while the agent is running then updates to the sand-box configuration documet will be ignored until the problem is corrected.
Response: Use the information in the message to resolve the problem with the sandbox document. The agent will periodically re-check the document and will update appropriately when the problem has been resovled.

BFGIO0148E: An internal error has occurred. Error creating the XML document builder.
Severity: 20 : Error
Explanation: This exception is unexpected. The cause is not immediately known.
Response: If the problem persists, see problem determination information in the product documentation.

BFGIO0149I: The agent sandbox configuration has been updated.
Severity: 0 : Information
Explanation: The agent has detected a change in the sandbox configuration document. The agent has reloaded the sandbox configuration document and will now operate based on the content of the new document.
Response: No user action is required.

BFGIO0150E: An internal error has occurred. Missing attributes for <insert_0>.
Severity: 20 : Error
Explanation: This exception is unexpected. The cause is not immediately known.
Response: If the problem persists, see problem determination information in the product documentation.

BFGIO0151E: The user sandbox XML document contains two default 'agent' elements.
Severity: 20 : Error
Explanation: The user sandbox XML document contains two default 'agent' elements ('agent' elements without a 'name' attribute). The document may contain at most one default 'agent' element. If this problem occurs when the agent is starting then the agent process will end. If this problem occurs while the agent is running then updates to the sandbox configuration document will be ignored until the problem is corrected.
Response: Alter the user sandbox XML document so that it contains at most one default 'agent' element. The agent will periodically re-check the document and will update appropriately when the problem has been resolved.

BFGIO0152E: The user sandbox XML document contains two ''agent'' elements with the same ''name'' attribute of ''<insert_0>''.
Severity: 20 : Error
Explanation: The user sandbox XML document has two 'agent' elements which have the same, specified, 'name' attribute. Each 'agent' element in the document that specifies a 'name' attribute must specify a different value for this attribute. If this problem occurs when the agent is starting then the agent process will end. If this problem occurs while the agent is running then updates to the sandbox configuration document will be ignored until the problem is corrected.
Response: Alter the user sandbox XML document so that all the 'agent' elements contained in the document specify different values for their 'name' attribute. The agent will periodically re-check the document and will update appropriately when the problem has been resolved.

BFGIO0153E: The user sandbox XML document does not contain an ''agent'' element that matches the name of this agent (''<insert_0>'').
Severity: 20 : Error
Explanation: The user sandbox XML document does not contain an 'agent' element with a 'name' attribute with a value that matches the name of this agent. The sandbox XML document must contain a matching 'agent' element to be valid. If this problem occurs when the agent is starting then the agent process will end. If this problem occurs while the agent is running then updates to the sandbox configuration document will be ignored until the problem is corrected.
Response: Alter the user sandbox XML document so that it contains an 'agent' element that has a 'name' attribute value matching the name of this agent. The agent will periodically re-check the document and will update appropriately when the problem has been resolved.

BFGIO0154E: Unable to perform a <insert_0> operation with the server.
Severity: 20 : Error
Explanation: The protocol bridge after a number of retries has been unable perform the operation although successful connection has been created.
Response: Review the health of the associated server and any information messages that server might be generating.

BFGIO0155E: Data set <insert_0> is a PDS or PDSE, and it is not permitted to be opened directly.
Severity: 20 : Error
Explanation: A PDS or PDSE data set has been requested to be opened. This is not supported. The error is likely due to a migrated PDS/PDSE being requeued for transfer.
Response: Retry the operation. If the problem persists then contact the IBM support center.

BFGIO0156E: An internal error has occurred. Attempted to read canonical path name of file and received exception <insert_0>
Severity: 20 : Error
Explanation: This exception is unexpected. The cause is not immediately known.
Response: If the problem persists, see problem determination information in the product documentation.

BFGIO0157E: Recovery of transfer file <insert_0> has been failed as the actual size of the file was <insert_2> which is less than the expected size of <insert_1>.
Severity: 20 : Error
Explanation: The agent was performing a recovery of a part transferred file, but the actual size of the part written file was less than record position before the failure occurred. The missing file data is nolonger available and the file has been marked as failed.
Response: Investigate whether the part written file has been changed between failure and attempted recovery, then perform the transfer request again.

BFGIO0158E: Recovery of transfer file <insert_0> has been interrupted as the connection to the protocol file server has been broken. The reported exception for the connection failure is <insert_1>
Severity: 20 : Error
Explanation: The agent was performing a recovery of a part transferred file, but the actual size of the part written file was less than the recorded position before the failure occurred. The missing file data is no longer available and the file has been marked as failed.
Response: Investigate the connection between the bridge agent and the protocol file server, then the health of the protocol file server. No further action is required to restart the transfer as this will be performed by the bridge agent.

BFGIO0159E: Line <insert_0> is too long for the output file. The maximum permitted line length is <insert_1>.
Severity: 20 : Error
Explanation: The source file for the text file transfer has a line of text that when encoded for the destination text file is too long. This typically occurs for over length lines when the destination file is a z/OS data set and a multi-byte codepage is defined for the destination encoding. MQMFT cannot support line wrapping of data when the destination encoding is multi-byte.
Response: Either select a destination data set with a larger LRECL (which determines the maximum line length), or update the source file such that over length lines are split as appropriate.

BFGIO0160E: Internal error: Attempt to write while transfer in recovery. File: <insert_0>
Severity: 20 : Error
Explanation: This exception is unexpected. The cause is not immediately known.
Response: If the problem persists, see problem determination information in the product documentation.

BFGIO0161E: Internal error: Attempt to read while transfer in recovery. File: <insert_0>
Severity: 20 : Error
Explanation: This exception is unexpected. The cause is not immediately known.
Response: If the problem persists, see problem determination information in the product documentation.

BFGIO0162E: While writing file <insert_0> to the protocol file server, the server reported the following exception <insert_1>
Severity: 20 : Error
Explanation: Writing to the protocol file server has been interrupted with a problem reported by the server.
Response: Evaluate the reported protocol file server exception and correct as necessary.

BFGIO0163E: While writing file <insert_0> to the protocol file server the communication with the server has been interrupted with exception <insert_1>
Severity: 20 : Error
Explanation: A communication problem has been detected while performing a write operation to the protocol file server. This may be a communication problem to the server or the server is no longer available.
Response: Investigate the health of the protocol file server. No further action is required as the transfer will have been queued for later recovery.

BFGIO0164E: An error was reported during an output stream operation. Reported exception was <insert_0>.
Severity: 20 : Error
Explanation: The protocol bridge was stream writing data from its server when an error condition occurred. This error condition relates to the file on the server and is not recoverable.
Response: Review the exception report by the server and correct as necessary.

BFGIO0165E: Unable to lock file "<insert_0>" for writing.
Severity: 20 : Error
Explanation: The system was unable to lock the specified destination file due to another application already having the file open.
Response: Ensure the file is not in use and resubmit the transfer request.

BFGIO0166E: The connection to the <insert_0> server at <insert_1> was lost while data was being read for a running transfer.
Severity: 20 : Error
Explanation: The protocol bridge was read data from the server when an error condition occurred. This could be a failure in the connection to the server.
Response: If this is a repeating occurrence investigate the connection and health of the server.

BFGIO0167E: Unable to generate a unique temporary data set or PDS member name from <insert_0> with suffix <insert_1>.
Severity: 20 : Error
Explanation: A temporary unique data set or PDS member name cannot be created because either a data set or PDS member with the same name already exists or there is an access permission problem.
Response: Ensure that there is sufficient permission to create the data set or PDS member and remove any existing data sets or PDS members with names that end with the required suffix. If the problem persists and cannot be resolved, contact the IBM support center.

BFGIO0168E: Internal error: File line separator is null
Severity: 20 : Error
Explanation: This exception is unexpected. The cause is not immediately known.
Response: If the problem persists, see problem determination information in the product documentation.

BFGIO0169E: The data for data set <insert_0> is corrupt.
Severity: 20 : Error
Explanation: The data read from the data set seems to be corrupt, in that the BDW or RDW has an invalid value.
Response: Validate the data set on the system. If it seems ok, then retry the request. If the problem persists and cannot be resolved, contact the IBM support center.

BFGIO0170E: Opening a queue for reading failed due to a Java IOException or WMQApiException with message text <insert_0>
Severity: 20 : Error
Explanation: A system operation failed to open the queue.
Response: Check the text of the Java IOException or WMQApiException for possible reasons for the error.

BFGIO0171E: Opening a queue for writing failed due to a Java IOException or WMQApiException with message text <insert_0>
Severity: 20 : Error
Explanation: A system operation failed to open the queue.
Response: Check the text of the Java IOException or WMQApiException for possible reasons for the error.

BFGIO0172E: An internal error has occurred. The channel is already open for the queue <insert_0>
Severity: 20 : Error
Explanation: This exception is unexpected. The cause is not immediately known.
Response: If the problem persists, see problem determination information in the product documentation.

BFGIO0173E: A queue close failed due to a WMQApiException with message text <insert_0>
Severity: 20 : Error
Explanation: A system operation failed to close the queue.
Response: Check the text of the WMQApiException for possible reasons for the error.

BFGIO0174E: An internal error has occurred. setState for an open queue channel is not supported
Severity: 20 : Error
Explanation: This exception is unexpected. The cause is not immediately known.
Response: If the problem persists, see problem determination information in the product documentation.

BFGIO0175E: An internal error has occurred. Queue <insert_0> is already closed.
Severity: 20 : Error
Explanation: This exception is unexpected. The cause is not immediately known.
Response: If the problem persists, see problem determination information in the product documentation.

BFGIO0176E: An internal error has occurred. Queue <insert_0> is already closed.
Severity: 20 : Error
Explanation: This exception is unexpected. The cause is not immediately known.
Response: If the problem persists, see problem determination information in the product documentation.

BFGIO0177E: A queue read failed due to a WMQApiException with message text <insert_0>
Severity: 20 : Error
Explanation: A system operation failed to read the queue.
Response: Check the text of the WMQApiException for possible reasons for the error.

BFGIO0178E: A queue write failed due to a WMQApiException with message text <insert_0>
Severity: 20 : Error
Explanation: A system operation failed to write to the queue.
Response: Check the text of the WMQApiException for possible reasons for the error.

BFGIO0179E: An internal error has occurred. Queue <insert_0> is already closed.
Severity: 20 : Error
Explanation: This exception is unexpected. The cause is not immediately known.
Response: If the problem persists, see problem determination information in the product documentation.

BFGIO0180E: The delimiter ''<insert_0>'' is not valid for a binary transfer.
Severity: 20 : Error
Explanation: The delimiter specified on the file to message transfer request is not valid. For details of valid syntax for a delimiter see the IBM MQ Managed File Transfer documentation.
Response: Correct the delimiter value and submit the transfer request again.

BFGIO0181E: The delimiter ''<insert_0>'' does not represent a valid length.
Severity: 20 : Error
Explanation: The delimiter specified on the file to message transfer request does not represent a valid length. For details of valid syntax for a delimiter see the IBM MQ Managed File Transfer documentation.
Response: Correct the delimiter value and submit the transfer request again.

BFGIO0182E: Flush failed.
Severity: 20 : Error
Explanation: A system operation failed to flush data to the data set.
Response: Examine the additional system error message information to fully understand the issue.

BFGIO0183E: An internal error has occurred. Insufficient data for checksum state (expected <insert_0> bytes, received <insert_1> bytes)
Severity: 20 : Error
Explanation: This exception is unexpected. The cause is not immediately known.
Response: If the problem persists, see problem determination information in the product documentation.

BFGIO0184E: An internal error has occurred. Insufficient data for queue name state (expected <insert_0> bytes, received <insert_1> bytes)
Severity: 20 : Error
Explanation: This exception is unexpected. The cause is not immediately known.
Response: If the problem persists, see problem determination information in the product documentation.

BFGIO0185E: An internal error has occurred. Insufficient data for groupId state (expected <insert_0> bytes, received <insert_1> bytes)
Severity: 20 : Error
Explanation: This exception is unexpected. The cause is not immediately known.
Response: If the problem persists, see problem determination information in the product documentation.

BFGIO0186E: An internal error has occurred. Insufficient data for queue manager name state (expected <insert_0> bytes, received <insert_1> bytes)
Severity: 20 : Error
Explanation: This exception is unexpected. The cause is not immediately known.
Response: If the problem persists, see problem determination information in the product documentation.

BFGIO0187E: An internal error has occurred. Queue <insert_0> is already closed.
Severity: 20 : Error
Explanation: This exception is unexpected. The cause is not immediately known.
Response: If the problem persists, see problem determination information in the product documentation.

BFGIO0188E: The length <insert_0> specified by the delimiter is too short for character set ''<insert_1>'' that has a maximum character size of <insert_2> bytes.
Severity: 20 : Error
Explanation: The length specified by a delimiter must be a minimum of 2 times the maximum character size of the destination character set.
Response: Correct the delimiter value and submit the transfer request again.

BFGIO0189E: Unable to convert the character set ''<insert_0>'' to a coded character set ID.
Severity: 20 : Error
Explanation: When performing a text transfer to a queue the character set must be converted to a coded character set ID that is recognised by IBM MQ.
Response: Change the character set and submit the transfer again.

BFGIO0190E: The delimiter ''<insert_0>'' does not represent a binary hexadecimal delimiter.
Severity: 20 : Error
Explanation: The delimiter specified on the file to message transfer request does not represent a binary hexadecimal delimiter. For details of valid syntax for a delimiter see the IBM MQ Managed File Transfer documentation.
Response: Correct the delimiter value and submit the transfer request again.

BFGIO0191E: An internal error has occurred. Queue <insert_0> is already closed.
Severity: 20 : Error
Explanation: This exception is unexpected. The cause is not immediately known.
Response: If the problem persists, see problem determination information in the product documentation.

BFGIO0192E: The regular expression compilation of the text delimiter with value ''<insert_0>'' failed (reason: <insert_1>)
Severity: 20 : Error
Explanation: The text delimiter value must be a valid regular expression.
Response: Correct the delimiter value and submit the transfer request again.

BFGIO0193E: The delimiter ''<insert_0>'' does not represent a valid text delimiter.
Severity: 20 : Error
Explanation: The delimiter specified on the file to message transfer request does not represent a text regular expression delimiter. For details of valid syntax for a delimiter see the IBM MQ Managed File Transfer documentation.
Response: Correct the delimiter value and submit the transfer request again.

BFGIO0194E: An internal error has occurred. The delimiter regular expression has not been set.
Severity: 20 : Error
Explanation: This exception is unexpected. The cause is not immediately known.
Response: If the problem persists, see problem determination information in the product documentation.

BFGIO0195E: An internal error has occurred. The text writer is not the DelimitedTextWriter.
Severity: 20 : Error
Explanation: This exception is unexpected. The cause is not immediately known.
Response: If the problem persists, see problem determination information in the product documentation.

BFGIO0196E: The delimiter ''<insert_0>'' has matched data of length <insert_1> which exceeds the maximum allowed of <insert_2>. The text matched by the delimiter is : ''<insert_3>''.
Severity: 20 : Error
Explanation: The length of data matched by the delimiter has exceeded the maximum allowed length, which is controlled by the agent property maxDelimiterMatchLength.
Response: Correct the delimiter value or increase the value of the maxDelimiterMatchLength property. Then submit the transfer again.

BFGIO0197E: An attempt to write to a queue was rejected by the destination agent. The agent must have <insert_0>=true set in the agent.properties file to support transferring to a queue.
Severity: 20 : Error
Explanation: An agent does not support file to message transfers by default. This function must be enabled.
Response: Enable the specified property and restart the agent before trying the transfer again.

BFGIO0198E: An attempt to read from a queue was rejected by the source agent. The agent must have <insert_0>=true set in the agent.properties file to support transferring from a queue.
Severity: 20 : Error
Explanation: An agent does not support message to file transfers by default. This function must be enabled.
Response: Enable the specified property and restart the agent before trying the transfer again.

BFGIO0199E: The delimiter ''<insert_0>'' is not valid for a text transfer.
Severity: 20 : Error
Explanation: The delimiter specified on the file to message transfer request is not valid. For details of valid syntax for a delimiter see the IBM MQ Managed File Transfer documentation.
Response: Correct the delimiter value and submit the transfer request again.

BFGIO0200E: The WebSpehere MQ queue ''<insert_0>'' on queue manager ''<insert_1>'' is not on the source agent''s queue manager.
Severity: 20 : Error
Explanation: When reading messages from an input queue the queue must reside on the source agent's queue manager.
Response: Update the transfer request to refer to a queue on the source agent's queue manager. Submit the transfer request again.

BFGIO0201E: An internal error has occurred. The channel is already open for the queue <insert_0>
Severity: 20 : Error
Explanation: This exception is unexpected. The cause is not immediately known.
Response: If the problem persists, see problem determination information in the product documentation.

BFGIO0202E: An internal error has occurred. Queue <insert_0> is already closed.
Severity: 20 : Error
Explanation: This exception is unexpected. The cause is not immediately known.
Response: If the problem persists, see problem determination information in the product documentation.

BFGIO0203E: An internal error has occurred. Queue <insert_0> is already closed.
Severity: 20 : Error
Explanation: This exception is unexpected. The cause is not immediately known.
Response: If the problem persists, see problem determination information in the product documentation.

BFGIO0204E: The text delimiter ''<insert_0>'' could not be encoded because the source encoding ''<insert_1>'' is not supported.
Severity: 20 : Error
Explanation: When performing a text transfer, use a supported source encoding.
Response: Ensure you are using a supported source encoding and resubmit the transfer request.

BFGIO0205E: The message data length <insert_0> being written to the output queue ''<insert_1>'' is greater than the maximum allowed <insert_2>.
Severity: 20 : Error
Explanation: The length of the data being written must not exceed the maximum specified by the agent property maxInputOutputMessageLength. For more information see the IBM MQ Managed File Transfer documentation.
Response: Ensure that the length of data being written does not exceed maxInputOutputMessageLength and submit the transfer request again.

BFGIO0206E: The message data length <insert_0> being read from the input queue ''<insert_1>'' is greater than the maximum allowed <insert_2>.
Severity: 20 : Error
Explanation: The length of the data being read must not exceed the maximum specified by the agent property maxInputOutputMessageLength. For more information see the IBM MQ Managed File Transfer documentation.
Response: Ensure that the length of data being read does not exceed maxInputOutputMessageLength and submit the transfer request again.

BFGIO0207E: The parsing of the text delimiter ''<insert_0>'' failed. Reason: ''<insert_1>''
Severity: 20 : Error
Explanation: The text delimiter has an invalid format. For more information see the IBM MQ Managed File Transfer documentation.
Response: Modify the text delimiter and submit the transfer again.

BFGIO0208E: The source queue attribute ''<insert_0>'' has a value of ''<insert_1>'' which is not valid.
Severity: 20 : Error
Explanation: The source queue attribute specified on the file to message transfer request is not valid. For details of valid syntax for this attribute see the IBM MQ Managed File Transfer documentation.
Response: Correct the attribute value and submit the transfer request again.

BFGIO0209E: The source queue attribute ''<insert_0>'' has a value of ''<insert_1>'' which is larger than the maximum permitted (<insert_2>).
Severity: 20 : Error
Explanation: The source queue attribute specified on the file to message transfer request has too large a value. For details of the permitted size for this attribute see the IBM MQ Managed File Transfer documentation.
Response: Correct the attribute value and submit the transfer request again.

BFGIO0210E: An internal error has occurred. Insufficient data for messageId state (expected <insert_0> bytes, received <insert_1> bytes)
Severity: 20 : Error
Explanation: This exception is unexpected. The cause is not immediately known.
Response: If the problem persists, see problem determination information in the product documentation.

BFGIO0211E: The value of the destination agent''s textReplacementCharacterSequence property is too long for the transfer. The current length is <insert_0> character(s). The maximum supported length for the transfer is <insert_1> character(s).
Severity: 20 : Error
Explanation: The textReplacementCharacterSequence property that has been specified for the transfer's destination agent contains too many characters for the current transfer. The maximum length of the value of the textReplacementCharacterSequence agent property is equal to the maximum number of characters per byte for a transfer's source encoding setting.
Response: Change the value of the textReplacementCharacterSequence agent property so that it contains the same number of characters as, or fewer characters than, the number that is supported by the source encoding for each transfer. Typically, setting the textReplacementCharacterSequence agent property to a single character is acceptable for all source encoding settings. When the textReplacementCharacterSequence agent property has been changed, restart the MQMFT agent. Then try the transfer again.

BFGIO0212E: The transfer from queue ''<insert_0>'' failed due to user result code <insert_1>. The following supplementary information was provided: ''<insert_2>''
Severity: 20 : Error
Explanation: The transfer failed because the provider of the messages added a non-zero user result code to the last message in the group of messages that was being transferred.
Response: Take appropriate action based on the user result code and any supplementary information provided.

BFGIO0213E: The parsing of an RFH2 header on a message from queue ''<insert_0>'' failed (reason: <insert_1>)
Severity: 20 : Error
Explanation: The format or code page specified for the RFH2 header on the message is invalid.
Response: Correct the problem and put the messages on the queue again. Then submit the transfer again.

BFGIO0214E: An internal error has occurred. The xpath expression is invalid (reason: <insert_0>)
Severity: 20 : Error
Explanation: This exception is unexpected. The cause is not immediately known.
Response: If the problem persists, see problem determination information in the product documentation.

BFGIO0215E: An attempt to read from queue "<insert_0>" by user "<insert_1>" has been denied.
Severity: 20 : Error
Explanation: The agent was unable to read from the specified queue as it is not within the restricted transfer sandbox for the user who requested this operation.
Response: Update the restricted sandbox configuration, as appropriate, to ensure this user has the necessary permissions to read from the given queue.

BFGIO0216E: An attempt to write to queue "<insert_0>" by user "<insert_1>" has been denied.
Severity: 20 : Error
Explanation: The agent was unable to write to the specified queue as it is not within the restricted transfer sandbox for the user who requested his operation.
Response: Update the restricted sandbox configuration, as appropriate, to ensure this user has the necessary permissions to write to the given queue.

BFGIO0217E: An attempt to read from the system queue "<insert_0>" by user "<insert_1>" has been denied.
Severity: 20 : Error
Explanation: The agent was unable to read from the specified queue as the agent is not permitted to read from any queues with a 'SYSTEM.' prefix.
Response: Reissue the command, choosing a queue without a 'SYSTEM.' prefix as the source.

BFGIO0218E: An attempt to write to the system queue "<insert_0>" by user "<insert_1>" has been denied.
Severity: 20 : Error
Explanation: The agent was unable to write to the specified queue as the agent is not permitted to write to any queues with a 'SYSTEM.' prefix.
Response: Reissue the command, choosing a queue without a 'SYSTEM.' prefix as the destination.

BFGIO0219E: This agent is configured with a multi-instance queue manager client connection and cannot be used for message to file transfers of IBM MQ message groups.
Severity: 20 : Error
Explanation: An agent configured with a multi-instance queue manager client connection is incompatible with IBM MQ message grouping.
Response: Either configure the agent with a single-instance queue manager or reissue the command without including the option to request message grouping.

BFGIO0220E: This agent is configured with a multi-instance queue manager client connection and cannot be used for file to message transfers.
Severity: 20 : Error
Explanation: An agent configured with a multi-instance queue manager client connection cannot be used for transfers to a destination queue.
Response: Either configure the agent with a single-instance queue manager or reissue the command specifying a different destination type.

BFGIO0221E: File <insert_0> is already locked by another channel on the same thread.
Severity: 20 : Error
Explanation: An attempt to lock the file has be rejected because another channel has already locked the file for the same thread.
Response: None.

BFGIO0222E: The source delimiter type of ''<insert_0>'' is not compatible with a transfer type of ''<insert_1>''
Severity: 20 : Error
Explanation: The source delimiter type must match the transfer type.
Response: Modify the source delimiter type or the transfer type. Then submit the transfer request again.

BFGIO0223E: The destination delimiter type of ''<insert_0>'' is not compatible with a transfer type of ''<insert_1>''
Severity: 20 : Error
Explanation: The destination delimiter type must match the transfer type.
Response: Modify the destination delimiter type or the transfer type. Then submit the transfer request again.

BFGIO0224E: Failed to allocate DDName for data set. Reason: <insert_0> [<insert_1>]. Allocate command used: "<insert_2>"
Severity: 20 : Error
Explanation: The allocation of the required data set for the transfer failed due to an invalid parameter list.
Response: Examine the data set attributes specified for the transfer request to ensure they are correct. If the problem persists and cannot be resolved, contact the IBM support center.

BFGIO0225E: Failed to allocate DDName for data set. Reason: <insert_0> [<insert_1>. Invalid parameter: <insert_2>]. Allocate command used: "<insert_3>"
Severity: 20 : Error
Explanation: The allocation of the required data set for the transfer failed due to an invalid parameter.
Response: Examine the data set attributes specified for the transfer request to ensure they are correct. If the problem persists and cannot be resolved, contact the IBM support center.

BFGIO0226E: Failed to allocate DDName for data set. Reason: <insert_0> [<insert_1>. Message processing error. IEFDB476 return code <insert_2>]. Allocate command used: "<insert_3>"
Severity: 20 : Error
Explanation: The allocation of the required data set for the transfer failed due to a message processing error.
Response: Retry the transfer. If the problem persists and cannot be resolved, contact the IBM support center.

BFGIO0227E: Failed to allocate DDName for data set. Reason: <insert_0> [<insert_1>. Unexpected return code]. Allocate command used: "<insert_2>"
Severity: 20 : Error
Explanation: This exception is unexpected. The cause is not immediately known.
Response: If the problem persists, see problem determination information in the product documentation.

BFGIO0332E: The default Connect:Direct bridge credential exit has has found a 'user' element with an empty or non-existent 'name' attribute in the credential mapping XML file. This element has been ignored.
Severity: 20 : Error
Explanation: It is mandatory for a 'user' element to have a 'name' attribute with a non-empty pattern as a value.
Response: Update the credential mapping XML file so that all 'user' elements have a 'name' attribute with a valid value.

BFGIO0336I: A connection to the Connect:Direct node <insert_0> has been established.
Severity: 0 : Information
Explanation: The Connect:Direct bridge agent has successfully connected to its associated Connect:Direct node after a previous connection failure.
Response: None.

BFGIO0337E: A connection to the Connect:Direct node <insert_0> has failed. The error reported from Connect:Direct is: ''<insert_1>''. Transfers will attempt recovery every <insert_2> seconds.
Severity: 20 : Error
Explanation: The Connect:Direct bridge agent cannot transfer files because it cannot connect to its Connect:Direct node. The agent will keep trying to recover transfers at the specified interval. When the problem is corrected the agent will be able to transfer files again.
Response: Examine the error reported from Connect:Direct and consult the Connect:Direct product documentation to determine the cause of the problem. Resolve the problem. If the problem persists contact the IBM support center for assistance.

BFGIO0338E: An attempt to connect to the Connect:Direct node <insert_0> has failed. The error reported from Connect:Direct is: ''<insert_1>''. Transfers will attempt recovery every <insert_2> seconds.
Severity: 20 : Error
Explanation: The Connect:Direct bridge agent cannot transfer files because a connection to its Connect:Direct node cannot be established. The agent will keep trying to recover transfers at the specified interval. When the problem is corrected the agent will be able to transfer files again.
Response: Examine the error reported from Connect:Direct and consult the Connect:Direct product documentation to determine the cause of the problem. Resolve the problem. If the problem persists contact the IBM support center for assistance.

BFGIO0339E: The IBM MQ User ID ''<insert_0>'' is not valid for use with the Connect:Direct bridge agent and the transfer has been failed.
Severity: 20 : Error
Explanation: The IBM MQ User ID supplied with the transfer request has not been validated by the credential package. As a result no credentials are available for connecting to the Connect:Direct node and the transfer request has been failed.
Response: Review the ConnectDirectCredentials.xml configuration to ensure the given IBM MQ User ID has been configured. If the default credential package is not being used then refer to the documentation of the credential package being used.

BFGIO0340E: The transfer item ''<insert_0>'' is a queue. Queues are not supported by a protocol bridge agent.
Severity: 20 : Error
Explanation: A protocol bridge agent is dedicated to reading and writing to the associated FTP/SFTP server.
Response: Submit the transfer again specifying an agent that is not a protocol bridge agent.

BFGIO0341E: The rename of temporary file <insert_0> to <insert_1> failed because the temporary file does not exist.
Severity: 20 : Error
Explanation: The temporary file is missing even though the transfer completed successfully. Another process might have deleted the file.
Response: Check whether any other processes are running that could be deleting the temporary file. Under normal conditions this error should never be seen. If the problem persists contact the IBM support center for assistance.

BFGIO0342E: The rename of temporary file <insert_0> to <insert_1> failed because the destination file is in use.
Severity: 20 : Error
Explanation: Failed to rename a temporary file, used for the file transfer destination, to the required final name. This is because the destination file already exists and is in use by another process.
Response: Manually attempt to rename the file, resolving any issues as required.

BFGIO0343E: The rename of temporary file <insert_0> to <insert_1> failed because the destination file already exists.
Severity: 20 : Error
Explanation: Failed to rename a temporary file, used for the file transfer destination, to the required final name. This is because the destination file already exists and it could not be overwritten.
Response: Manually attempt to rename the file, resolving any issues as required.

BFGIO0344E: The FTP site ''MSGI'' command to the IBM Sterling File Gateway FTP server failed (reason: <insert_0>)
Severity: 20 : Error
Explanation: The command to retrieve the IBM Sterling File Gateway message ID and document ID failed. The file has transferred successfully but the transfer will not be correlated with IBM Sterling File Gateway.
Response: Investigate the reason for the failure and make any necessary corrections for future transfers.

BFGIO0345E: The FTP site ''MSGI'' command to the IBM Sterling File Gateway FTP server returned the failure reply code: (<insert_0>)
Severity: 20 : Error
Explanation: The command to retrieve the IBM Sterling File Gateway message ID and document ID failed. The file has transferred successfully but the transfer will not be correlated with IBM Sterling File Gateway.
Response: Investigate the reason for the failure and make any necessary corrections for future transfers.

BFGIO0346E: The reply ''<insert_0>'' returned by FTP site ''MSGI'' command to the IBM Sterling File Gateway FTP server is invalid.
Severity: 20 : Error
Explanation: The command to retrieve the IBM Sterling File Gateway message ID and document ID has returned invalid values. The file has transferred successfully but the transfer will not be correlated with IBM Sterling File Gateway.
Response: Investigate the reason for the invalid values and make any necessary corrections for future transfers.

BFGIO0347E: The message ID ''<insert_0>'' returned by FTP site ''MSGI'' command to the IBM Sterling File Gateway FTP server is not a valid Long value.
Severity: 20 : Error
Explanation: The command to retrieve the IBM Sterling File Gateway message ID and document ID has returned an invalid value for the message ID. The file has transferred successfully but the transfer will not be correlated with IBM Sterling File Gateway.
Response: Investigate the reason for the invalid value and make any necessary corrections for future transfers.

BFGIO0348E: The call to obtain the FTP session for the site ''MSGI'' command to the IBM Sterling File Gateway FTP server failed (reason: <insert_0>)
Severity: 20 : Error
Explanation: The command to retrieve the IBM Sterling File Gateway message ID and document ID has not been executed. The file has transferred successfully but the transfer will not be correlated with IBM Sterling File Gateway.
Response: Investigate the reason for the failure and make any necessary corrections for future transfers.

BFGIO0349E: The call to obtain the FTP session for the site 'MSGI' command to the IBM Sterling File Gateway FTP server returned null.
Severity: 20 : Error
Explanation: The command to retrieve the IBM Sterling File Gateway message ID and document ID has not been executed. The file has transferred successfully but the transfer will not be correlated with IBM Sterling File Gateway.
Response: Investigate the reason for the failure and make any necessary corrections for future transfers.

BFGIO0350E: File "<insert_0>" already exists.
Severity: 20 : Error
Explanation: The system was unable to create the file specified because the file already exists.
Response: Remove the existing file or specify an alternative file name.

BFGIO0351E: File "<insert_0>" is not a normal file (it might be a directory).
Severity: 20 : Error
Explanation: The system was unable to find the file specified. A normal file is a file that is not a directory and meets other criteria depending on the system.
Response: Ensure that the file exists and that the file is accessible.

BFGIO0352E: Attempt to read file "<insert_0>" by user "<insert_1>" has been denied.
Severity: 20 : Error
Explanation: The system was unable to read the specified file because the user has been denied access.
Response: Ensure that the specified location is correct. Check the user access policies for the installed I/O user exits for the agent.

BFGIO0353E: The attempt to write file "<insert_0>" by user "<insert_1>" has been denied.
Severity: 20 : Error
Explanation: The system was unable to write to the specified file because the user has been denied access.
Response: Ensure that the specified location is correct. Check the user access policies for the installed I/O user exits for the agent.

BFGIO0354E: Unable to create path for resource "<insert_0>". Reason: <insert_1>
Severity: 20 : Error
Explanation: The system was unable to create the path specified because the underlying I/O user exit threw an exception.
Response: Examine the reason given by the underlying I/O user exit, and correct as appropriate.

BFGIO0355E: The I/O exit for class ''<insert_0>'' failed to initialize. The agent will be stopped.
Severity: 20 : Error
Explanation: It is mandatory for all of the configured I/O exits to be successfully initialized for an agent to start.
Response: Investigate the cause of the exception and correct the source code for the specified class as appropriate. Recompile the class and replace the existing user exit routine with the new version. Restart the agent.

BFGIO0356E: The getPath method for class ''<insert_1>'', for I/O exit ''<insert_0>'', has returned a string that is longer in length than its getName method. The getPath method returned: ''<insert_2>'', The getName method returned: ''<insert_3>''.
Severity: 20 : Error
Explanation: The getPath method for an IOExitPath implementation is expected to return the full path for the resource. The getName method for an IOExitPath implementation is expected to return the name part of the path for the resource. Hence, the string returned from the getPath method should be greater or equal to the string returned from the getName method.
Response: Investigate the cause of the exception and correct the source code for the specified class as appropriate. Recompile the class and replace the existing user exit routine with the new version. Restart the agent.

BFGIO0357E: The IOExit.newPath method for I/O exit ''<insert_0>'', has returned an unsupported IOExitPath instance ''<insert_1>''.
Severity: 20 : Error
Explanation: The IOExit.newPath method is required to return a IOExitResourcePath or IOExitWildcardPath instance.
Response: Investigate the cause of the exception and correct the source code for the specified class as appropriate. Recompile the class and replace the existing user exit routine with the new version. Restart the agent.

BFGIO0358E: The delimiter ''<insert_0>'' is not valid for a binary transfer.
Severity: 20 : Error
Explanation: The delimiter specified on the transfer request is not valid for a binary transfer. For details of valid syntax for a delimiter, see the IBM MQ Managed File Transfer documentation.
Response: Correct the delimiter value and submit the transfer request again.

BFGIO0359E: The source record delimiter is not appropriate for a transfer to a record-oriented destination.
Severity: 20 : Error
Explanation: A source record delimiter has been specified for a transfer to a record-oriented destination (such as a z/OS data set). Source record delimiters are not valid for transfers to record-oriented destinations.
Response: Resubmit the transfer either without specifying the source record delimiter or to a destination that is not record oriented.

BFGIO0360E: A value of 'true' has been specified for the 'keepTrailingSpaces' attribute for a non-text mode transfer.
Severity: 20 : Error
Explanation: The source 'keepTrailingSpaces' attribute is only allowed to be set to 'true' for text mode transfers.
Response: Resubmit the transfer either without specifying the 'keepTrailingSpaces' attribute or specify that the transfer is in text mode.

BFGIO0361E: A value of 'true' has been specified for the 'keepTrailingSpaces' attribute for a non-fixed length format source data set or the source data set format cannot be determined.
Severity: 20 : Error
Explanation: The source 'keepTrailingSpaces' attribute is only allowed to be set to 'true' for fixed-length-format source data sets.
Response: Resubmit the transfer either without specifying the 'keepTrailingSpaces' attribute or specify a source that is a fixed-length-format data set.

BFGIO0362E: A value of 'true' has been specified for the 'keepTrailingSpaces' attribute for a source that is not a data set.
Severity: 20 : Error
Explanation: The source 'keepTrailingSpaces' attribute is only allowed to be set to 'true' for fixed-length-format data sets.
Response: Resubmit the transfer either without specifying the 'keepTrailingSpaces' attribute or specify a source that is a fixed-length-format data set.

BFGIO0363E: Delimiters are not supported for text transfers.
Severity: 20 : Error
Explanation: Delimiters are supported for binary transfers only.
Response: Remove the delimiter value and submit the transfer request again.

BFGIO0364E: The record length for the source file is too long for the destination file. Source file''s record length is <insert_0>. Destination file''s record length is <insert_1>.
Severity: 20 : Error
Explanation: A transfer between two record-oriented files can be successful only if the source file's record length is less than or equal to the destination file's record length.
Response: Check that the source and destination files specified for the transfer are correct. If required, submit the transfer request again and correct the source and destination file as required.

BFGIO0365E: An internal error has occurred. The specified path (<insert_0>) for a record channel is not record oriented.
Severity: 20 : Error
Explanation: This exception is unexpected. The cause is not immediately known.
Response: If the problem persists, see problem determination information in the product documentation.

BFGIO0366E: The source record delimiter is not appropriate for a transfer from a source that is not record oriented.
Severity: 20 : Error
Explanation: A source record delimiter has been specified for a transfer from a source that is not record oriented. Source record delimiters are valid only for transfers from record-oriented sources.
Response: Resubmit the transfer either without specifying the source record delimiter or specify from a source that is record oriented.

BFGIO0367E: The data set "<insert_0>" does not exist.
Severity: 20 : Error
Explanation: The system was unable to find the data set specified.
Response: Ensure that the data set exists and that the data set is accessible.

BFGIO0368E: The size of file <insert_0> is <insert_2> bytes, but it was expected to be <insert_1> bytes. Recovery is not possible.
Severity: 20 : Error
Explanation: A transfer of the file failed part way through. During the recovery operation the system discovered the contents of the file had been changed. This could be because of a problem with an installed I/O user exit reporting the wrong size for the file.
Response: Resubmit the transfer request again, if required. If the problem persists, ensure the problem is not because of an installed I/O user exit reporting the wrong size for the file. If the problem persists and cannot be resolved, contact the IBM support center.

BFGIO0369E: Cannot pad fixed-format record to length <insert_0> because the padding byte sequence of length <insert_1> will not fit exactly for the record.
Severity: 20 : Error
Explanation: Text transfers to fixed-format record-oriented paths will write each text line as a separate record, padded with space characters to the maximum record length. For multibyte character sets this means that the required padding length for each line must be a multiple of the number of bytes that represent a single space character. Otherwise a partial space character will be written at the end of the record.
Response: Change the destination of the transfer to a non-fixed-format record-oriented path and resubmit the transfer request again. If the destination must be a fixed-format record-oriented path, consider first performing the text transfer to a non-fixed-format record-oriented destination, then binary transfer the destination to the required fixed-format record-oriented path (binary transfers pad records with 0x00 bytes).

BFGIO0370E: While processing path ''<insert_3>'', the I/O user exit failed because the <insert_2> method implemented by class <insert_0> threw an exception. The exception is: <insert_1>
Severity: 20 : Error
Explanation: The exit routine class, named in the message, threw the specified exception during the processing of the specified task. It is not valid for user exit routines to throw exceptions and this caused the specified task to be canceled.
Response: Investigate the cause of the exception and correct the source code for the specified class as appropriate. Recompile the class and replace the existing user exit routine with the new version. Restart the agent.

BFGIO0371E: The agent cannot continue because while processing path ''<insert_3>'', the <insert_2> method implemented by class <insert_0> threw an exception. The exception is: <insert_1>
Severity: 20 : Error
Explanation: The exit routine class, named in the message, threw the specified exception during the processing of a transfer. It is not valid for user exit routines to throw exceptions. The agent cannot continue and will end.
Response: Investigate the cause of the exception and correct the source code for the specified class as appropriate. Recompile the class and replace the existing user exit routine with the new version. Restart the agent. If you cannot resolve the problem, contact the IBM support center for further assistance.

BFGIO0372E: While processing path ''<insert_3>'', the I/O user exit <insert_1> method implemented by class <insert_0> returned a <insert_2> instance, which does not implement the required <insert_3> interface.
Severity: 20 : Error
Explanation: The exit routine class, named in the message, returned an object of the incorrect type during the processing of the specified task. This caused the specified task to be canceled.
Response: Investigate the cause of the problem and correct the source code for the specified class as appropriate. Recompile the class and replace the existing user exit routine with the new version. Restart the agent.

BFGIO0373E: The command <insert_0> cannot be run in a thread-safe manner because the background command runner thread has been shut down.
Severity: 20 : Error
Explanation: This exception is unexpected. The cause is not immediately known.
Response: If the problem persists, see problem determination information in the product documentation.

BFGIO0374E: While processing path ''<insert_1>'', the I/O user exit write(ByteBuffer) method implemented by class <insert_0> returned a value of <insert_2>. The write method was passed a buffer with <insert_3> bytes of data to be written, but after the write method returned there are still <insert_4> bytes to be written.
Severity: 20 : Error
Explanation: The write method for the exit routine class, named in the message, indicated that data could not be written to the resource and hence the transfer has been failed.
Response: Resubmit the transfer request, if required. If the problem persists, ensure the problem is not a fault with an installed I/O user exit's IOExitChannel.write(ByteBuffer) method implementation. If the problem persists and cannot be resolved, contact the IBM support center.

BFGIO0375E: The generated GDG data set name "<insert_0>" is longer than the 44 bytes allowed.
Severity: 20 : Error
Explanation: To produce an absolute GDG data set name, MQMFT must add 9 characters to the supplied base name. Adding those characters has exceeded the allowed character limit and caused an error.
Response: Reduce the length of the base data set name to less than 35 characters.

BFGIO0376E: While processing path ''<insert_2>'', the I/O user exit <insert_1> method implemented by class <insert_0> returned a com.ibm.wmqfte.exitroutine.api.IOExitRecordChannel instance. The I/O user exit class instance is not record oriented.
Severity: 20 : Error
Explanation: The I/O user exit method returned a com.ibm.wmqfte.exitroutine.api.IOExitRecordChannel instance for a resource path that does not implement the com.ibm.wmqfte.exitroutine.api.IOExitRecordResourcePath interface. This is not permitted. The I/O user exit method should have returned a com.ibm.wmqfte.exitroutine.api.IOExitChannel instance.
Response: Ensure that the I/O user exit implementation is corrected as appropriate.

BFGIO0377E: The record length of <insert_1> for file ''<insert_0>'' is invalid. The record length must be an integer value greater than zero and less than <insert_2>
Severity: 20 : Error
Explanation: An invalid record length has been requested for a record-oriented file. The record length must be an integer value greater than zero and less than the configured maximum, as specified by the MQMFT agent property ioMaxRecordLength.
Response: If one of the agents for the transfer has an I/O user exit installed, ensure that the I/O user exit implementation for instance method com.ibm.wmqfte.exitroutine.api.IOExitRecordResourcePath.getRdcordLength() is returning a value greater than zero and less than the configured maximum. If appropriate, set the ioMaxRecordLength MQMFT agent property to increase the maximum record length that can be supported by the agent. If the problem persists and cannot be resolved, contact the IBM support center.

BFGIO0378E: While processing path ''<insert_2>'', the I/O user exit failed because the <insert_1> method implemented by class <insert_0> returned a null value.
Severity: 20 : Error
Explanation: The exit routine class, named in the message, returned a null value during the processing of the specified task. It is not valid for user exit routines to return a null value for the called method and this caused the specified task to be canceled.
Response: Investigate the cause of the problem and correct the source code for the specified class as appropriate. Recompile the class and replace the existing user exit routine with the new version. Restart the agent.

BFGIO0379E: The record length of <insert_1> for file ''<insert_0>'' is too large for transfer. The theoretical maximum record length that can be supported by MQMFT is <insert_2>.
Severity: 20 : Error
Explanation: The record length for a source record-oriented file is too large for a transfer between the agents. MQMFT agents transfer file data as a sequence of transfer chunks and a whole record of a record-oriented file must be able to be contained within a single transfer chunk. It is only possible to configure MQMFT agents for a maximum transfer chunk size of 2147483647, which results in the theoretical maximum record length identified in the message.
Response: None.

BFGIO0380E: The record length of <insert_1> for file ''<insert_0>'' is too large for transfer. The maximum record length that can be supported by the transfer is <insert_2>. Set the MQMFT agent property agentChunkSize to a value of at least <insert_3> for both the source and destination agents to support the transfer of the file.
Severity: 20 : Error
Explanation: The record length for a source record-oriented file is too large for a transfer between the agents. MQMFT agents transfer file data as a sequence of transfer chunks and a whole record of a record-oriented file must be able to be contained within a single transfer chunk.
Response: Increase the chunk size for the source and destination agents for the transfer by setting MQMFT agent property agentChunkSize to a minimum of the size specified in the message. Restart the source and destination agents and submit the transfer request again.

BFGIO0381E: While processing path ''<insert_4>'',\nthe I/O user exit method <insert_3> implemented by class <insert_0>\nthrew a <insert_1>. The exception message is: <insert_2>
Severity: 20 : Error
Explanation: The exit routine class threw an exception during the processing of the specified task. This is an expected exception but has caused the specified task to be canceled.
Response: Investigate the cause of the exception and resubmit the task if required.

BFGIO0382E: A wildcard cannot be specified as a transfer's destination file path.
Severity: 20 : Error
Explanation: A destination file path was specified that contains wildcard characters. This is not supported by IBM MQ Managed File Transfer.
Response: Correct the destination file path so that it does not contain wildcard characters. Wildcard characters are as determined by the destination file system, so you should check that the specified destination file path is targeted at the correct file system. If the problem persists and cannot be resolved, contact the IBM support center.

BFGIO0383E: The security permissions defined for credentials file ''<insert_0>'' do not meet the minimum requirements for a file of this type. Reported problem: <insert_1>
Severity: 20 : Error
Explanation: For security purposes credentials files have restrictions placed on the access rights that users have to the file. A credentials file must not have system-wide read, write, or delete permissions set. For more information on credentials files and the restrictions placed on them, consult the product documentation.
Response: Modify the security permissions of the specified credentials file and run the command again.

BFGIO0384E: The transfer source encoding <insert_0> is not valid or is for an unsupported character set.
Severity: 20 : Error
Explanation: The destination agent was unable to recognize the character set for the required source encoding. If the default source encoding is used, this error implies that the destination agent's Java SDK is not compatible with the source agent's system.
Response: If a source encoding has been specified, ensure this source encoding is a valid encoding as recognized by the destination agent's Java SDK. If the default source encoding is used and is expected to be compatible with the destination agent, ensure all maintenance has been applied. If the problem persists and cannot be resolved, contact the IBM support center.

BFGIO0385W: The directory path ''<insert_0>'' specified in the commandPath property is not a directory. The agent will continue but some commands might not run.
Severity: 10 : Warning
Explanation: If you set the commandPath property in the agent.properties file, the agent checks at startup that each path is a valid directory on the file system. If a path is invalid, commands that are specified as part of a transfer might not run.
Response: To prevent this warning, remove the invalid path from the commandPath property in the agent.properties file.

BFGIO0386W: The data set path ''<insert_0>'' specified in the commandPath property is not a valid data set specification. The agent will continue but some commands might not run.
Severity: 10 : Warning
Explanation: If you set the commandPath property in the agent.properties file, the agent checks at startup that each data set path is valid. If a path is invalid, commands that are specified as part of a transfer might not run.
Response: To prevent this warning, remove the invalid path from the commandPath property in the agent.properties file.

BFGIO0387W: One of the directory paths specified in the commandPath property is not an executable path for the current user. The agent will continue but some commands might not run correctly.
Severity: 10 : Warning
Explanation: If you set the commandPath property in the agent.properties file, the agent checks at startup that the user running the agent has permission to run commands on each of the paths specified.
Response: To prevent this warning, remove the invalid path from the commandPath property in the agent.properties file.

BFGIO0388E: The attribute with name ''<insert_0>'' is not supported by the 4690 OS agent.
Severity: 20 : Error
Explanation: All attributes in the transfer request must be supported by the 4690 OS agent.
Response: Remove the attribute from the transfer request. Then submit the the transfer request again. For a list of the supported attribute names, refer to the IBM MQ Managed File Transfer documentation.

BFGIO0389E: The value ''<insert_0>'' of the DIST attribute is invalid.
Severity: 20 : Error
Explanation: The value of the DIST attribute must be valid.
Response: Modify the DIST attribute in the transfer request to have a valid value. Then submit the the transfer request again. For a list of the supported values, refer to the IBM MQ Managed File Transfer documentation.

BFGIO0390E: The DIST attribute has no value.
Severity: 20 : Error
Explanation: The DIST attribute must have a valid value.
Response: Modify the DIST attribute in the transfer request to have a valid value. Then submit the the transfer request again. For a list of the supported values, refer to the IBM MQ Managed File Transfer documentation.

BFGIO0391E: An error occurred while setting the distribution type ''<insert_1>'' on the file ''<insert_0>''. The reason is: <insert_2>
Severity: 20 : Error
Explanation: An exception was given while setting the distribution type on the file.
Response: Check that the drive that the file is being written on supports distribution types and that the distribution type value is valid. Modify the transfer request as appropriate. Then submit the transfer request again. For further information, refer to the IBM MQ Managed File Transfer documentation.

BFGIO0392E: Destination file attributes have been specified for ''<insert_0>''. Destination File attributes are not supported for this destination.
Severity: 20 : Error
Explanation: Destination file attributes are not supported for this destination.
Response: Remove the destination file attributes from the transfer request. Then submit the transfer again. For further information, refer to the IBM MQ Managed File Transfer documentation.

BFGIO0393E: An error occurred while creating the temporary file in directory ''<insert_0>''. The reason is: <insert_1>
Severity: 20 : Error
Explanation: An exception was given while creating a temporary file.
Response: Review the reason for the error and take appropriate action. Then submit the transfer request again.

BFGIO0394E: An error occurred while opening the file ''<insert_0>'' for write. The reason is: <insert_1>
Severity: 20 : Error
Explanation: An exception was given while opening a file for write.
Response: Review the reason for the error and take appropriate action. Then submit the transfer request again.

BFGIO0395E: An error occurred while opening the file ''<insert_0>'' for read. The reason is: <insert_1>
Severity: 20 : Error
Explanation: An exception was given while opening a file for read.
Response: Review the reason for the error and take appropriate action. Then submit the transfer request again.

BFGIO0396E: An error occurred while getting the canonical path for the file ''<insert_0>''. The reason is: <insert_1>
Severity: 20 : Error
Explanation: An exception was given while getting the canonical path for a file.
Response: Review the reason for the error and take appropriate action. Then submit the transfer request again.

BFGIO0397E: An error occurred while renaming the file ''<insert_0>'' to ''<insert_1>''.
Severity: 20 : Error
Explanation: An error occurred while renaming a file.
Response: Check that the destination file path is valid and take appropriate action. Then submit the transfer request again.

BFGIO0398E: An error occurred while deleting the file ''<insert_0>''.
Severity: 20 : Error
Explanation: An error occurred while deleting a file.
Response: Check that the file exists and is not open. Take appropriate action. Then submit the transfer request again.

BFGIO0399E: An error occurred while creating the file ''<insert_0>''. The reason is: <insert_1>
Severity: 20 : Error
Explanation: An exception was given while creating a file.
Response: Review the reason for the error and take appropriate action. Then submit the transfer request again.

BFGIO0400E: The size information for file ''<insert_0>'' is unavailable.
Severity: 20 : Error
Explanation: This exception is unexpected. The cause is not immediately known.
Response: If the problem persists, see problem determination information in the product documentation.

BFGIO0401E: A relative path was used when no value has been set for the transferRoot agent property.
Severity: 20 : Error
Explanation: When transferring to or from a 4690 agent, relative paths for files cannot be used unless a value has been specified for the transferRoot agent property.
Response: If you want to use a relative path in a transfer, set a value for the transferRoot property in the 4690 agent's agent.properties file.

BFGIO0402E: A queue open failed due to a WMQApiException with message text <insert_0>
Severity: 20 : Error
Explanation: A system operation failed to open the queue.
Response: Check the text of the WMQApiException for possible reasons for the error.

BFGIO0403E: No delimiterType attribute has been specified for the element for the delimiter <insert_0>.
Severity: 20 : Error
Explanation: A delimiterType attribute with a value of "size", "binary" or "text" must be specified if a delimiter attribute is specified on the element.
Response: Add a delimiterType attribute to the element of the transfer request and submit the transfer request again.

BFGIO0404E: The value ''<insert_0>'' of the delimiterType attribute specified on the element is invalid.
Severity: 20 : Error
Explanation: The valid values for the delimiterType attribute on the element are as follows: "size", "binary" or "text".
Response: Specify a valid value for the delimiterType attribute on the element of the transfer request and submit the transfer request again.

BFGIO0405E: A queue write failed due to a JmqiException with message text <insert_0>
Severity: 20 : Error
Explanation: A system operation failed to write to the queue.
Response: Check the text of the JmqiException for possible reasons for the error.

BFGIO0406E: The file ''<insert_0>'' could not be read because: <insert_1>.
Severity: 20 : Error
Explanation: The named file could not be opened for reading for the specified reason.
Response: Ensure that the file is present and accessible to the agent process.

BFGIO0407E: The dataset ''<insert_0>'' could not be read because: <insert_1>.
Severity: 20 : Error
Explanation: The named data set could not be opened for reading for the specified reason.
Response: Ensure that the data set is present and accessible to the agent process.

BFGIO0408E: Data set ''<insert_0>'' with RECFM(<insert_1>), LRECL(<insert_2>), and BLKSIZE(<insert_3>) is not supported, because LRECL is greater than BLKSIZE.
Severity: 20 : Error
Explanation: A data set with LRECL greater than BLKSIZE cannot be read and therefore is not support by MQMFT for file transfer.
Response: Specify a data set with attributes that specify LRECL less than or equal to the BLKSIZE.

BFGIO0409E: The rename of temporary file <insert_0> to <insert_1> failed. The file has not been deleted.
Severity: 20 : Error
Explanation: Failed to rename a temporary file, which is used for the file transfer destination, to the required final name. The destination file might not be accessible. The file has been retained ensuring that data has not been lost (but data may have been duplicated).
Response: Manually attempt to rename the file, resolving any issues as required.

BFGIO0410E: The protocol server name has not been specified, and no default protocol server has been defined for the protocol bridge.
Severity: 20 : Error
Explanation: The protocol bridge agent received a managed transfer request that did not specify a protocol server name, and no default protocol server was defined in the agent's ProtocolBridgeProperties.xml file.
Response: Either resubmit the transfer with a valid protocol server specified or reconfigure the protocol bridge agent to define a default protocol server.

BFGIO0411E: Access denied to file "<insert_0>".
Severity: 20 : Error
Explanation: A system operation failed to access the specified file.
Response: Ensure that the file exists and that the file is accessible.

BFGIO0414E: No messages exist on queue "<insert_0>".
Severity: 20 : Error
Explanation: The source agent was unable to find any messages on the specified queue.
Response: Ensure that a message exists on the queue.

BFGIO9999E: <insert_0>
Severity: 20 : Error
Explanation: If this message does not give enough information, check the accompanying error messages for further information.
Response: For further information on resolving this error, see the problem determination information on the product Web site.