Ensure that the file exists and that the file is accessible.
BFGII0002E
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.
BFGII0003E
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.
BFGII0004E
The file "<insert_0>" has a file type that is not supported in file transfers in to or from the QSYS.LIB filesystem.
Severity
20 : Error
Explanation
The product currently only supports native save files in to or from the QSYS.LIB filesystem.
Response
Resubmit the request specifying the name of a valid save file in the QSYS.LIB filesystem.
BFGII0005E
A security exception was encountered while retrieving a file attribute for file "<insert_0>".
Severity
20 : Error
Explanation
The access permissions for the specified file do not permit querying the file's attributes.
Response
Ensure that the file's access permissions allow querying the file's attributes.
BFGII0006E
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.
BFGII0007E
An IO exception occurred while accessing file "<insert_0>".
Severity
20 : Error
Explanation
An IO operation on the specified file encountered an exception.
Response
Retry the request. If the problem persists contact IBM support.
BFGII0008E
Unable to create directory "<insert_0>" for new file "<insert_1>".
Severity
20 : Error
Explanation
The specified directory path could not be created.
Response
Ensure that the user profile the destination agent is running under has sufficient authority to create the directory specified in the file path and then retry the request
BFGII0009E
Unable to create library "<insert_0>" for save file "<insert_1>".
Severity
20 : Error
Explanation
The system was unable to create the library specified in the file path.
Response
Ensure that the user profile the destination agent is running under has sufficient authority to create the library specified in the file path and then retry the request
BFGII0010E
Unable to create library "<insert_0>" for new file "<insert_1>" due to an internal error.
Severity
20 : Error
Explanation
The system was unable to create the specified library.
Response
Retry the request. If the problem persists contact IBM support.
BFGII0011E
Unable to create save file "<insert_0>" due to error "<insert_1>".
Severity
20 : Error
Explanation
Cause of the problem could be the specification of an invalid library or file name in the file path.
Response
Ensure that a valid file path is specified. Refer to the IBM i Information center for rules relating to path names in the QSYS.LIB file system.
BFGII0012E
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.
BFGII0013E
An invalid library name "<insert_0>" was specified in the file path.
Severity
20 : Error
Explanation
The library name specified in the file path is not valid. Refer to the IBM i Information center for rules relating to path names in the QSYS.LIB file system.
Response
Resubmit your request providing a valid library name in the file path.
BFGII0014E
An internal error has occurred. The file path for the transfer file was received without any value.
Severity
20 : Error
Explanation
An initialization failure has occurred due to missing file path value for the transfer file.
Response
A fatal error has occurred in the product, contact the IBM Support center for assistance.
BFGII0015E
An invalid file path "<insert_0>" was specified for transferring a native IFS File on IBM i.
Severity
20 : Error
Explanation
The file path for a native IFS file on IBM i must start with /QSYS.LIB as the first component in the path.
Response
Ensure that the file path specified for the transfer of a native IFS file on IBM i starts with /QSYS.LIB as the first component in the path.
BFGII0016E
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.
BFGII0017E
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.
BFGII0018E
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.
BFGII0019E
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.
BFGII0020E
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.
BFGII0021E
Not authorized to access file "<insert_0>".
Severity
20 : Error
Explanation
An authorization error occurred while attempting to perform IO operations on the specified file.
Response
Ensure that the user profile that the agent is running under has sufficient authority to perform read or write operations to the specified file and the directory or library in which it exists.
BFGII0022E
An incorrect transfer mode was specified on the transfer request to transfer file "<insert_0>".
Severity
20 : Error
Explanation
Specified file can only be transferred using the binary transfer mode.
Response
Ensure that binary mode is specified and retry the request.
BFGII0023E
Path "<insert_0>" must end in a file name with a ".FILE" extension.
Severity
20 : Error
Explanation
The specified path does not contain a valid file name.
Response
Specify a path that ends in a file name with a ".FILE" extension and then retry your request.
BFGII0024E
File name "<insert_0>" must end with ".FILE".
Severity
20 : Error
Explanation
The specified name contains an invalid or unsupported extension.
Response
Specify a file name that ends with ".FILE" and then retry your request.
BFGII0025E
Library name "<insert_0>" must end in ".LIB".
Severity
20 : Error
Explanation
The specified library name contains an invalid extension.
Response
Specify a library name that ends with ".LIB" and then retry your request.
BFGII0026E
Destination file "<insert_0>" subtype incompatible with source file "<insert_1>" subtype.
Severity
20 : Error
Explanation
File subtype for source and destination files must be compatible.
Response
Either specify a different destination file name or move, delete or rename the destination file and then retry the request.
BFGII0027E
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.
BFGII0028E
An internal error has occurred. The subtype for the transfer file was received without any value.
Severity
20 : Error
Explanation
An initialization failure has occurred due to missing subtype value for the transfer file.
Response
A fatal error has occurred in the product, contact the IBM Support center for assistance.
BFGII0029E
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.
BFGII0031E
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.
BFGII0032E
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.
BFGII0033E
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.
BFGII0034E
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.
BFGII0035E
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.
BFGII0038E
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.
BFGII0041E
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.
BFGII0042E
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.
BFGII0046E
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.
BFGII0047E
Unable to generate a unique temporary file for "<insert_0>".
Severity
20 : Error
Explanation
An internal error occurred while attempting to generate a unique temporary file name.
Response
Retry the request. If the problem persists contact IBM support.
BFGII0048E
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.
BFGII0049E
The rename of temporary file "<insert_0>" to file "<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
None.
BFGII0050E
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 it manually.
BFGII0051E
An authorization error occurred while attempting to create file "<insert_0>".
Severity
20 : Error
Explanation
The user profile under which the destination agent is running does not have sufficient authority to create this path.
Response
Ensure that the user profile under which the destination agent is running has authority to create a file in this path. Then retry the request.
BFGII0052E
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 we 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.
BFGII0056E
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.
Response
Ensure that the specified location lies within the restricted sandbox.
BFGII0057E
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.
Response
Ensure that the specified location lies within the restricted sandbox.
BFGII0058E
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 can not be resolved, contact the IBM support center.
BFGII0059E
The transfer destination encoding "<insert_0>" is not legal is for an unsupported character set.
Severity
20 : Error
Explanation
The destination agent was unable to recognize 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 can not be resolved, contact the IBM support center.
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 can not 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 can not be resolved, contact the IBM support center.
BFGII0061E
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.
BFGII0063E
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 can not be resolved, contact the IBM support center.
BFGII0067E
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.
BFGII0068E
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.
BFGII0071E
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.
BFGII0078E
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.
BFGII0079E
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.
BFGII0080E
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.
BFGII0081E
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.
BFGII0082E
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.
BFGII0083E
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.
BFGII0088E
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.
BFGII0089E
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 can not 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.
BFGII0090E
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 can not 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.
BFGII0092E
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.
BFGII0093E
Message to file transfers are not supported for transfers to the QSYS.LIB filesystem.
Severity
20 : Error
Explanation
The product currently does not support transfers to a QSYS.LIB filesystem file from a queue.
Response
None.
BFGII0094E
File to message transfers are not supported for transfers from the QSYS.LIB filesystem.
Severity
20 : Error
Explanation
The product currently does not support transfers from a QSYS.LIB filesystem file to a queue.
Response
None.
BFGII0095E
File to message transfers are not supported for transfers from the QSYS.LIB filesystem.
Severity
20 : Error
Explanation
The product currently does not support transfers from a QSYS.LIB filesystem file to a queue.
Response
None.
BFGII0096E
Message to file transfers are not supported for transfers to the QSYS.LIB filesystem.
Severity
20 : Error
Explanation
The product currently does not support transfers to a QSYS.LIB filesystem file from a queue.
Response
None.
BFGII0097E
FTEFileFactoryHelper "<insert_0>" can not be found.
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.
BFGII0098E
Blocking locks not supported for IFS 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.
BFGII0099E
Unable to generate a unique temporary file for "<insert_0>" due to 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.
BFGII0100E
Unable to create physical file "<insert_0>" for new file member "<insert_1>".
Severity
20 : Error
Explanation
The specified physical file path could not be created.
Response
Ensure that the user profile the destination agent is running under has sufficient authority to create the directory specified in the file path and then retry the request.
BFGII0101E
The file <insert_0> contains fields which are binary only fields, but a text transfer was selected.
Severity
20 : Error
Explanation
The file being transfered contains fields which contain binary fields which cannot be converted during a text transfer.
Response
Try the transfer again in binary mode.
BFGII0102E
All CCSIDs for the fields in <insert_0> are not identical, which could result in invalid conversion
Severity
20 : Error
Explanation
The file being transfered contains fields with multiple CCSIDs. Because the text conversion is done on a whole file and not individual fields, this could result in invalid conversion.
Response
Try the transfer again in binary mode.
BFGII0103E
The rename of temporary file "<insert_0>" to "<insert_1>" failed because the destination file member is full.
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 rename operation received a CPA5305 message signifying that the destination file member is not large enough to hold the temporary file.
Response
Use the CHGPF CL command to increase the size of the destination file member to *NOMAX or to a large enough value to hold the source file and then try the request again.
BFGII9999E
"<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.