An internal error has occurred. Unable to create a pipe for Stdout.
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.
BFGNV0002E
An internal error has occurred. Unable to set handle information for Stdout.
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.
BFGNV0003E
An internal error has occurred. Unable to create a pipe for Stdin.
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.
BFGNV0004E
An internal error has occurred. Unable to set handle information for Stdin.
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.
BFGNV0005E
An internal error has occurred. Unable to create a pipe for Stderr.
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.
BFGNV0006E
An internal error has occurred. Unable to set handle information for Stderr.
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.
BFGNV0007E
An internal error has occurred. Error creating a process. The application name is: <insert_0> The command line parameters are: <insert_1> The last error code is: <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.
BFGNV0008E
An internal error has occurred. Error creating an event. The last error code is: <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.
BFGNV0009E
An internal error has occurred. Error setting an event. The last error code is: <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.
BFGNV0010E
An internal error has occurred. Error resetting an event. The last error code is: <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.
BFGNV0011E
An internal error has occurred. Error waiting on an event. The last error code is: <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.
BFGNV0012E
An internal error has occurred. Error waiting on an event. The return value is: <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.
BFGNV0013E
An internal error has occurred. Error creating a thread. The last error code is: <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.
BFGNV0014E
An internal error has occurred. Error terminating a thread. The last error code is: <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.
BFGNV0015E
An internal error has occurred. Error waiting on a thread. The last error code is: <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.
BFGNV0016E
An internal error has occurred. Error waiting on a thread. The return value is: <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.
BFGNV0017E
An internal error has occurred. Error getting a thread exit code. The last error code is: <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.
BFGNV0018I
The trace specification has changed to "<insert_0>".
Severity
0 : Information
Explanation
The trace specification has changed to the value specified in the message. This affects the amount of diagnostic information that is generated.
Response
No action required.
BFGNV0019E
Failed to change permissions for file <insert_0>. Reason: <insert_1>
Severity
20 : Error
Explanation
The system has failed to change the security permissions on a file.
Response
Check that the MQMFT application has the appropriate rights to change the security permissions on the identified file. If not, then either run the MQMFT application as a suitably privileged user, or change the ownership of the file such that the MQMFT is the owner, or grant system permissions to the MQMFT user such that the file permissions may be changed.
BFGNV0020E
chmod is not supported on Windows.
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.
BFGNV0021E
OpenProcessToken failed. 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.
BFGNV0022E
GetTokenInformation failed for file <insert_1>. 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.
BFGNV0023E
AllocateAndInitializeSid failed for file <insert_1>. 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.
BFGNV0024E
AllocateAndInitializeSid failed for file <insert_1>. 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.
BFGNV0025E
InitializeAcl failed for file <insert_1>. 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.
BFGNV0026E
AddAccessAllowedAce failed for file <insert_1>. 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.
BFGNV0027E
AddAccessAllowedAce failed for file <insert_1>. 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.
BFGNV0028E
AddAccessAllowedAce failed for file <insert_1>. 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.
BFGNV0029E
InitializeSecurityDescriptor failed for file <insert_1>. 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.
BFGNV0030E
SetSecurityDescriptorDacl failed for file <insert_1>. 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.
BFGNV0031E
SetFileSecurity failed for file <insert_1>. 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.
BFGNV0032E
An internal error has occurred. Error forking a process. The application name is: <insert_0> The error code 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.
BFGNV0033E
An internal error has occurred. Error calling execv in the child process. The application name is: <insert_0> The error code 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.
BFGNV0034E
An internal error has occurred. Error killing the child process. The process id is: <insert_0> The error code 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.
BFGNV0035E
An internal error has occurred. Error waiting for the child process. The process id is: <insert_0> The error code 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.
BFGNV0036E
An internal error has occurred. Error reading from a pipe. The error code is: <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.
BFGNV0037E
An internal error has occurred. Error initializing thread attributes. The error code is: <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.
BFGNV0038E
An internal error has occurred. Error creating a thread. The error code is: <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.
BFGNV0039E
An internal error has occurred. Error canceling a thread. The thread id is: <insert_0> The error code 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.
BFGNV0040E
An internal error has occurred. Error joining a thread. The thread id is: <insert_0> The error code 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.
BFGNV0041E
An internal error has occurred. Error locking a mutex. The error code is: <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.
BFGNV0042E
An internal error has occurred. Error unlocking a mutex. The error code is: <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.
BFGNV0043E
An internal error has occurred. Error waiting on a condition variable. The error code is: <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.
BFGNV0044E
An internal error has occurred. Error broadcasting to a condition variable. The error code is: <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.
BFGNV0045E
An internal error has occurred. Error creating a pipe for stdin. The error code is: <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.
BFGNV0046E
An internal error has occurred. Error creating a pipe for stdout. The error code is: <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.
BFGNV0047E
An internal error has occurred. Error creating a pipe for stderr. The error code is: <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.
BFGNV0048E
An internal error has occurred. Error creating mapping pipe for stdin. The error code is: <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.
BFGNV0049E
An internal error has occurred. Error creating mapping pipe for stdout. The error code is: <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.
BFGNV0050E
An internal error has occurred. Error creating mapping pipe for stderr. The error code is: <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.
BFGNV0051E
Failed to create directory <insert_0> for log files.
Severity
20 : Error
Explanation
The directory path could not be created because either a regular file with the same name already exists or the application has insufficient access rights to create the directory.
Response
Check that the specified log directory is correct and there is sufficient authority for the application to create it. If the problem persists then contact the IBM MQ Managed File Transfer product support team for assistance.
BFGNV0052E
The system is unable to output log messages to the event log file in directory <insert_0> (reason: <insert_1>). Event log messages will be output to the console.
Severity
20 : Error
Explanation
An error occurred whilst attempting to write a message to the event log file. The event log file or containing directory may be inaccessible or the event log file is being used exclusively by another application.
Response
Ensure the event log file and directory are accessible and not being used by another application.
BFGNV0053E
The system is unable to output trace messages to the trace file in directory <insert_0> (reason: <insert_1>). Trace output is disabled.
Severity
20 : Error
Explanation
An error occurred whilst attempting to write a message to the trace file. The trace file or containing directory may be inaccessible or the trace file is being used exclusively by another application.
Response
Ensure the trace file and directory are accessible and not being used by another application.
BFGNV0054E
Failed to open file <insert_0>. Reason: <insert_1>
Severity
20 : Error
Explanation
The required file could not be opened.
Response
Check the reason for the open failure and take action as appropriate. If the problem persists then contact the IBM MQ Managed File Transfer product support team for assistance.
BFGNV0055E
Unable to create files for log pattern <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.
BFGNV0056E
Failed to rename file <insert_0> to <insert_1>. Reason: <insert_2>
Severity
20 : Error
Explanation
The required file could not be renamed.
Response
Check the reason for the rename failure and take action as appropriate. If the problem persists then contact the IBM MQ Managed File Transfer product support team for assistance.
BFGNV0057E
Failed to lock file <insert_0>. Reason: <insert_1>
Severity
20 : Error
Explanation
The required file could not be locked.
Response
Check the reason for the lock failure and take action as appropriate. If the problem persists then contact the IBM MQ Managed File Transfer product support team for assistance.
BFGNV0058E
An internal error has occurred. Error initializing thread condition variable attributes. The error code is: <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.
BFGNV0059E
An internal error has occurred. Error initializing thread condition variable. The error code is: <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.
BFGNV0060E
An internal error has occurred. Error initializing thread mutex attributes. The error code is: <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.
BFGNV0061E
An internal error has occurred. Error initializing thread mutex. The error code is: <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.
BFGNV0062E
An internal error has occurred. The interprocess communications mechanism is not connected.
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.
BFGNV0063E
Failed to write interprocess communications message. Reason: <insert_0>
Severity
20 : Error
Explanation
An attempt to write an interprocess communications message failed.
Response
Retry the command. If the problem persists, contact the IBM MQ Managed File Transfer product support team for assistance.
BFGNV0064E
Failed to read interprocess communications message. Reason: <insert_0>
Severity
20 : Error
Explanation
An attempt to read an interprocess communications message failed.
Response
Retry the command. If the problem persists, contact the IBM MQ Managed File Transfer product support team for assistance.
BFGNV0065E
An internal error has occurred. The interprocess communications mechanism is already connected.
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.
BFGNV0066E
Failed to open named pipe <insert_0> for interprocess communications. Reason: <insert_1>
Severity
20 : Error
Explanation
For interprocess communication a Windows named pipe is used. This pipe could not be opened. This might be because the named pipe does not exist or the application does not have permission to open the named pipe.
Response
Examine the reason given for the failure and take action as appropriate. If the problem persists, contact the IBM MQ Managed File Transfer product support team for assistance.
BFGNV0067E
Failed to open named pipe <insert_0> within <insert_1> seconds for interprocess communications.
Severity
20 : Error
Explanation
For interprocess communication a Windows named pipe is used. This pipe could not be opened within a specific time period because it was already in use.
Response
Retry running the application. If the problem persists, contact the IBM MQ Managed File Transfer product support team for assistance.
BFGNV0068E
Failed to change pipe <insert_0> to message mode. 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.
BFGNV0069E
Java method <insert_0> not 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.
BFGNV0070E
The interprocess communications server received an exception from the Java environment.
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.
BFGNV0072E
OpenProcessToken failed. 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.
BFGNV0073E
GetTokenInformation failed. 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.
This exception is unexpected. The cause is not immediately known.
Response
If the problem persists, see problem determination information in the product documentation.
BFGNV0082E
SetFileSecurity failed. 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.
BFGNV0083E
The system is unable to write FFDC data to FFDC file <insert_0> (reason: <insert_1>). FFDC information will be written to the IBM MQ Managed File Transfer process controller event log.
Severity
20 : Error
Explanation
An error occurred while attempting to write to an FFDC file.
Response
No action required.
BFGNV0084E
An internal error has occurred. Product failure data was captured in 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.
BFGNV0085E
Failed to read a valid message for service <insert_0>. Reason: <insert_1>
Severity
20 : Error
Explanation
The IBM MQ Managed File Transfer interprocess communications server has had an error reading a valid message from the client. The reason might be that the client has sent an incorrectly-formatted message, or a system error has occurred.
Response
Examine the reason given for the failure and take action as appropriate. If the problem persists, contact the IBM MQ Managed File Transfer product support team for assistance.
BFGNV0086E
Failed to write message for service <insert_0>. Reason: <insert_1>
Severity
20 : Error
Explanation
The IBM MQ Managed File Transfer interprocess communications server has had an error writing a message to the client.
Response
Examine the reason given for the failure and take action as appropriate. If the problem persists, contact the IBM MQ Managed File Transfer product support team for assistance.
BFGNV0087E
Failed to create a named pipe for service <insert_0>. Reason: <insert_1>
Severity
20 : Error
Explanation
The IBM MQ Managed File Transfer interprocess communications server has had an error creating a named pipe.
Response
Examine the reason given for the failure and take action as appropriate. If the problem persists, contact the IBM MQ Managed File Transfer product support team for assistance.
BFGNV0088E
Failed to start client processing thread for service <insert_0>. Reason: <insert_1>
Severity
20 : Error
Explanation
The IBM MQ Managed File Transfer interprocess communications server has had an error starting a new thread to process client messages.
Response
Examine the reason given for the failure and take action as appropriate. If the problem persists, contact the IBM MQ Managed File Transfer product support team for assistance.
BFGNV0089E
Failed to accept client connection for service <insert_0>. Reason: <insert_1>
Severity
20 : Error
Explanation
The IBM MQ Managed File Transfer interprocess communications server has had an error trying to accept a connection from a client.
Response
Examine the reason given for the failure and take action as appropriate. If the problem persists, contact the IBM MQ Managed File Transfer product support team for assistance.
BFGNV0090E
Failed to accept client connection for service <insert_0> because the maximum number of connected clients has already been reached. The maximum number of connected clients allowed is: <insert_1>
Severity
20 : Error
Explanation
The IBM MQ Managed File Transfer interprocess communications server has rejected a connection request from a client because the maximum number of connected clients has already been reached.
Response
No action required. The client connection should be tried again later, after one of the connected clients disconnects.
BFGNV0091E
The data for the IBM MQ Managed File Transfer interprocess communications message is too short. Only received <insert_0> bytes.
Severity
20 : Error
Explanation
The IBM MQ Managed File Transfer interprocess communications message protocol requires a message of a minimum length. The length of passed data was too short. The problem is probably caused by an erroneous or corrupt message being sent. Normally the message will be ignored.
Response
If the problem persists, contact the IBM MQ Managed File Transfer product support team for assistance.
BFGNV0092E
The data for the IBM MQ Managed File Transfer interprocess communications message contains a bad eye catcher.
Severity
20 : Error
Explanation
The IBM MQ Managed File Transfer interprocess communications message protocol requires eye catcher data within the message. The message eye catcher data did not match the expected eye catcher data. The problem is probably caused by an erroneous or corrupt message being sent. Normally the message will be ignored.
Response
If the problem persists, contact the IBM MQ Managed File Transfer product support team for assistance.
BFGNV0093E
The data for the IBM MQ Managed File Transfer interprocess communications message is too short. Only received <insert_0> bytes, but should have received at least <insert_1> bytes.
Severity
20 : Error
Explanation
The IBM MQ Managed File Transfer interprocess communications message protocol requires a message of a minimum length. The length of passed data was too short. The problem is probably caused by an erroneous or corrupt message being sent. Normally the message will be ignored.
Response
If the problem persists, contact the IBM MQ Managed File Transfer product support team for assistance.
BFGNV0094E
The data for the IBM MQ Managed File Transfer interprocess communications message is too short. Only received <insert_0> bytes, but should have received at least <insert_1> bytes.
Severity
20 : Error
Explanation
The IBM MQ Managed File Transfer interprocess communications message protocol requires a message of a minimum length. The length of passed data was too short. The problem is probably caused by an erroneous or corrupt message being sent. Normally the message will be ignored.
Response
If the problem persists, contact the IBM MQ Managed File Transfer product support team for assistance.
BFGNV0095E
The text data for the IBM MQ Managed File Transfer interprocess communications message is too long. Received <insert_0> bytes, but expected <insert_1> bytes.
Severity
20 : Error
Explanation
The IBM MQ Managed File Transfer interprocess communications message protocol required a message with text of a certain length, but more data was received. The problem is probably caused by an erroneous or corrupt message being sent. Normally the message will be ignored.
Response
If the problem persists, contact the IBM MQ Managed File Transfer product support team for assistance.
BFGNV0096E
An internal error has occurred. The interprocess communications mechanism is already connected.
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.
BFGNV0097E
An internal error has occurred. The interprocess communications mechanism is not connected.
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.
BFGNV0098E
An internal error has occurred. The interprocess communications mechanism is already connected.
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.
BFGNV0099E
An internal error has occurred. The interprocess communications mechanism is not connected.
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.
BFGNV0100E
An internal error has occurred. The interprocess communications mechanism is not connected.
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.
BFGNV0101E
Failed to write interprocess communications message. Reason: <insert_0>
Severity
20 : Error
Explanation
An attempt to write an interprocess communications message failed.
Response
Retry the command. If the problem persists, contact the IBM MQ Managed File Transfer product support team for assistance.
BFGNV0102E
Failed trying to use existing socket file <insert_0>. Reason: <insert_1>
Severity
20 : Error
Explanation
An attempt to re-use an existing socket file has failed. This may be because another process has the socket file locked or because we don't have permission to delete the file.
Response
Retry the command. If the problem persists, contact the IBM MQ Managed File Transfer product support team for assistance.
BFGNV0103E
Failed to read message from socket. Reason: <insert_0>
Severity
20 : Error
Explanation
An attempt to read an interprocess communications message failed.
Response
Retry the command. If the problem persists, contact the IBM MQ Managed File Transfer product support team for assistance.
BFGNV0104E
Failed to start client processing thread for service <insert_0>. Reason: <insert_1>
Severity
20 : Error
Explanation
The IBM MQ Managed File Transfer interprocess communications server has had an error starting a new thread to process client messages.
Response
Examine the reason given for the failure and take action as appropriate. If the problem persists, contact the IBM MQ Managed File Transfer product support team for assistance.
BFGNV0105E
Failed to accept client connection for service <insert_0>. Reason: <insert_1>
Severity
20 : Error
Explanation
The IBM MQ Managed File Transfer interprocess communications server has had an error trying to accept a connection from a client.
Response
Examine the reason given for the failure and take action as appropriate. If the problem persists, contact the IBM MQ Managed File Transfer product support team for assistance.
BFGNV0106E
Failed to accept client connection for service <insert_0> because the maximum number of connected clients has already been reached. The maximum number of connected clients allowed is: <insert_1>
Severity
20 : Error
Explanation
The IBM MQ Managed File Transfer interprocess communications server has rejected a connection request from a client because the maximum number of connected clients has already been reached.
Response
No action required. The client connection should be tried again later, after one of the connected clients disconnects.
BFGNV0107E
Failed to write interprocess communications message. Reason: <insert_0>
Severity
20 : Error
Explanation
An attempt to write an interprocess communications message failed.
Response
Retry the command. If the problem persists, contact the IBM MQ Managed File Transfer product support team for assistance.
BFGNV0108E
Failed to make client connection for service <insert_0>. Reason: <insert_1>
Severity
20 : Error
Explanation
The IBM MQ Managed File Transfer interprocess communications client has had an error trying to make a connection to a server.
Response
Examine the reason given for the failure and take action as appropriate. If the problem persists, contact the IBM MQ Managed File Transfer product support team for assistance.
BFGNV0109E
An internal error has occurred. Error setting current working directory to <insert_0>. The error code 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.
BFGNV0110E
An internal error has occurred. Error setting environment variable <insert_0> to <insert_1>. Reason: <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.
BFGNV0111E
Failed to make client connection for service <insert_0>. Reason: <insert_1>
Severity
20 : Error
Explanation
The IBM MQ Managed File Transfer interprocess communications client has had an error trying to make a connection to a server.
Response
Examine the reason given for the failure and take action as appropriate. If the problem persists, contact the IBM MQ Managed File Transfer product support team for assistance.
BFGNV0112E
Failed to make client connection for service <insert_0> for the current user. This is probably because another user is currently using the service.
Severity
20 : Error
Explanation
The IBM MQ Managed File Transfer interprocess communications client has had an error trying to make a connection to a server. Another user may have started the service.
Response
Retry the command as the user who started the service. If the problem persists, contact the IBM MQ Managed File Transfer product support team for assistance.
BFGNV0114E
Failed to setup security attributes for the IBM MQ Managed File Transfer interprocess communications mechanism for service <insert_0>. Reason: <insert_1>
Severity
20 : Error
Explanation
The IBM MQ Managed File Transfer interprocess communications server has had an error setting up the security attributes, to secure the IBM MQ Managed File Transfer interprocess communications mechanism.
Response
Examine the reason given for the failure and take action as appropriate. If the problem persists, contact the IBM MQ Managed File Transfer product support team for assistance.
BFGNV0115E
The property named "<insert_0>" is not a string type property.
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.
BFGNV0116E
The property named "<insert_0>" is not an integer type property.
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.
BFGNV0117E
The property named "<insert_0>" is not a boolean type property.
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.
BFGNV0118E
The property named "<insert_0>" has an invalid numeric value of "<insert_1>"
Severity
20 : Error
Explanation
The named property must be a numeric value for the command to successfully complete.
Response
Review the associated property file and change the property so that is has a valid numeric value.
BFGNV0119E
The property named "<insert_0>" has a value of "<insert_1>", which is not in the range between "<insert_2>" and "<insert_3>".
Severity
20 : Error
Explanation
The named numeric property is present in the configuration, but has a value that is outside the valid range.
Response
Review the associated property file and change the value to one that is in the given ranges.
BFGNV0120E
The property named "<insert_0>" has an invalid boolean value of "<insert_1>"
Severity
20 : Error
Explanation
The named property has only two options and the one assigned is not a valid option.
Response
Review the associated property file and change the property to have a value of true or false, yes or no, or on or off.
BFGNV0121E
Failed to open file <insert_0>. Reason: <insert_1>
Severity
20 : Error
Explanation
The required file could not be opened.
Response
Check the reason for the open failure and take action as appropriate. If the problem persists then contact the IBM MQ Managed File Transfer product support team for assistance.
BFGNV0122E
Unable to open the property file with path <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.
BFGNV0123E
An empty property file path has been specified.
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.
BFGNV0124E
An internal error has occurred. The current thread is not the owner of the lock.
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.
BFGNV0125E
An internal error has occurred. The current thread is not the owner of the lock.
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.
BFGNV0126E
The system is unable to create or access the event log file in directory <insert_0> (reason: <insert_1>). Event log messages will be output to the console.
Severity
20 : Error
Explanation
An error occurred while attempting to create or access the event log file. The event log file or its containing directory might be inaccessible or the event log file is being used exclusively by another application.
Response
Ensure the event log file and directory are accessible and not being used by another application.
BFGNV0127E
The system is unable to create or access the trace file in directory <insert_0> (reason: <insert_1>). Trace output is disabled.
Severity
20 : Error
Explanation
An error occurred while attempting to create the trace file. The trace file or its containing directory might be inaccessible or the trace file is being used exclusively by another application.
Response
Ensure the trace file and directory are accessible and not being used by another application.
BFGNV0128E
Failed to lookup group <insert_0>. Reason: <insert_1>
Severity
20 : Error
Explanation
The identified group could not be accessed. For z/OS the likely cause of this error is an invalid group being specified by the BFG_GROUP_NAME environment variable.
Response
For z/OS correct the value of the BFG_GROUP_NAME environment variable to specify a valid group name. For distributed platforms, if the problem persists then contact the IBM MQ Managed File Transfer product support team for assistance.
BFGNV0129E
An internal error has occurred. OpenProcessToken method failed. 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.
BFGNV0130E
An internal error has occurred. OpenProcessToken method failed. 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.
BFGNV0131E
An internal error has occurred. GetTokenInformation method failed. 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.
BFGNV0132E
An internal error has occurred. LookupAccountSid method failed. 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.
BFGNV0133E
The file ''<insert_0>'' has read permission granted for ''other'' users.
Severity
20 : Error
Explanation
Configuration files should be appropriately secured. The specified file is currently configured to allow 'other' users to read the file.
Response
Change the permissions of the file to prevent 'other' users having read access to it.
BFGNV0134E
The file ''<insert_0>'' has write permission granted for ''other'' users.
Severity
20 : Error
Explanation
Configuration files should be appropriately secured. The specified file is currently configured to allow 'other' users to write to the file.
Response
Change the permissions of the file to prevent 'other' users having write access to it.
BFGNV0135E
The directory ''<insert_0>'' has write permission granted for ''other'' users.
Severity
20 : Error
Explanation
Configuration files should be appropriately secured. The specified directory is currently configured to allow 'other' users to write to it.
Response
Change the permissions of the directory to prevent 'other' users having write access to it.
BFGNV0136E
IBM MQ Managed File Transfer was unable to check that the product configuration file ''<insert_0>'' is appropriately secured.
Severity
20 : Error
Explanation
Configuration files should be appropriately secured. The permissions on the specified file could not be checked. This may be because we do not have permission to read the file.
Response
Ensure the specified configuration file is readable by the user running IBM MQ Managed File Transfer.
BFGNV0137E
IBM MQ Managed File Transfer was unable to check that the product configuration directory ''<insert_0>'' is appropriately secured.
Severity
20 : Error
Explanation
Configuration directories should be appropriately secured. The permissions on the specified directory could not be checked. This may be because we do not have permission to read the directory.
Response
Ensure the specified configuration directory is readable by the user running IBM MQ Managed File Transfer.
BFGNV0138E
GetFileSecurity failed for file <insert_1>. 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.
BFGNV0139E
GetFileSecurity failed for file <insert_1>. 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.
BFGNV0140E
GetFileSecurity succeeded with 0 length buffer 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.
BFGNV0141E
AllocateAndInitialzeSid failed for file <insert_1>. 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.
BFGNV0142E
AllocateAndInitialzeSid failed for file <insert_1>. 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.
BFGNV0143E
AllocateAndInitialzeSid failed for file <insert_1>. 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.
BFGNV0144E
GetSecrurityDescriptorDacl failed for file <insert_1>. 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.
BFGNV0145E
The ''<insert_0>'' group has access to the file ''<insert_1>''.
Severity
20 : Error
Explanation
The file must not allow the Everyone, Users, or Guests groups any access to the file.
Response
Modify the discretionary access control list on the file so that the group has no access.
BFGNV0146E
The file ''<insert_0>'' has no discretionary access control list so all users and groups have access.
Severity
20 : Error
Explanation
The file must not allow the Everyone, Users, or Guests groups any access to the file.
Response
Add a discretionary access control list to the file that specifies that the Everyone, Users, and Guests groups have no access.
BFGNV0147E
GetAce failed for file <insert_1>. 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.
BFGNV0148W
The system is unable to change the permissions of FFDC file <insert_0> (reason: <insert_1>).
Severity
10 : Warning
Explanation
An error occurred while attempting to set the file permissions for an FFDC file.
Response
No action required.
BFGNV0149E
An uncaught exception has been thrown and the thread will be ended. The exception is: <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.
BFGNV0150E
An internal error has occurred. Product failure data was captured\n<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.
BFGNV0151E
The process controller failed to load the IBM MQ library ''<insert_0>''. Reason: <insert_1>
Severity
20 : Error
Explanation
For a bindings connection to the IBM MQ Manager File Transfer agent or logger queue manager, IBM MQ Managed File Transfer must be installed with IBM MQ.
Response
Install IBM MQ and then start the agent or logger again. If the problem persists, contact the IBM MQ Managed File Transfer product support team for assistance.
BFGNV0152E
GetProcAddress failed getting the address for MQCONN. 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.
BFGNV0153E
GetProcAddress failed getting the address for MQDISC. 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.
BFGNV0154E
The product root passed to the WMQifaceImpl initialize() method is empty.
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.
BFGNV0156E
The address of the MQCONN function has not been initialized.
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.
BFGNV0157E
The address of the MQDISC function has not been initialized.
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.
BFGNV0158E
FreeLibrary failed. 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.
BFGNV0159E
Failed trying to bind to socket file. Reason: <insert_0>
Severity
20 : Error
Explanation
An attempt to bind to a socket file has failed.
Response
Retry the command. If the problem persists, contact the IBM MQ Managed File Transfer product support team for assistance.
BFGNV0161E
The process controller failed to load the IBM MQ library ''<insert_0>''. Reason: <insert_1>
Severity
20 : Error
Explanation
For a bindings connection to the IBM MQ Manager File Transfer agent or logger queue manager, IBM MQ Managed File Transfer must be installed with IBM MQ.
Response
Install IBM MQ and then start the agent or logger again. If the problem persists, contact the IBM MQ Managed File Transfer product support team for assistance.
BFGNV0162E
dlsym failed getting the address for MQCONN. 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.
BFGNV0163E
dlsym failed getting the address for MQDISC. 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.
BFGNV0164E
dlclose failed. 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.
BFGNV0165E
The product root passed to the WMQifaceImpl initialize() method is empty.
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.
BFGNV0166E
Failed to create directory path <insert_0>. Reason <insert_1>.
Severity
20 : Error
Explanation
The system was unable to create the specified directory path. This problem is most likely to be caused by an insufficient access problem to one of the sub-directories in the specified directory path.
Response
Examine the reason given for the failure and take appropriate action to resolve the problem. If the problem persists, contact the IBM MQ Managed File Transfer product support team for assistance.
BFGNV0167E
A null file path has been specified to check permissions on.
Severity
20 : Error
Explanation
A request was made to check the permissions on a null file path.
Response
Specify a valid file path.
BFGNV0168E
An internal error has occurred. Error setting stack size attribute. The error code is: <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.
BFGNV0169E
An internal error has occurred. An invalid JVM pointer was specified.
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.
BFGNV0170E
An internal error has occurred. Unable to attach the current thread to the JVM.
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.
BFGNV0171E
An internal error has occurred. The current thread is not the owner of the lock.
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.
BFGNV0172E
LookupAccountName failed for account <insert_1>. 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.
BFGNV0173E
WMQiface is not supported on z/OS.
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.
BFGNV0174E
Failed to check for special authority <insert_0>. Reason: <insert_1>
Severity
20 : Error
Explanation
The identified special authority could not be checked. For IBM i, this is likely to be a permission issue.
Response
For IBM i, call DSPMSGD for the preceding reason code to find out more information about why the command failed.
BFGNV0175W
The group ''<insert_0>'', specified by the agent property "adminGroup", does not exist.
Severity
10 : Warning
Explanation
The agent property "adminGroup" had been set to the name of a group that did not exist. As a result, only the user that started the agent can perform administrative tasks on that agent.
Response
Modify the agent property "adminGroup" to specify a valid group name.
BFGNV0176I
Members of the group ''<insert_0>'' are administrators for this agent.
Severity
0 : Information
Explanation
The agent has been configured to allow members of the group specified by the agent property "adminGroup" to perform administrative tasks for the agent.
Response
No action required.
BFGNV9999E
<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.