An internal error has occurred. An attempt to reconfigure a command queue package when not in Unit Test mode occurred.
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.
BFGCH0002E
The agent queue manager was omitted from the agent.properties file. The agent process will now end.
Severity
20 : Error
Explanation
The agent must have its associated queue manager named in the properties file otherwise it cannot start
Response
Review the properties file of the agent and ensure that the queue manager information is correct.
BFGCH0003E
An internal error has occurred. This receiving agent has received an internal file transfer request with no files 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.
BFGCH0004E
An internal error has occurred. This receiving agent has received an internal file transfer request with no files 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.
BFGCH0005E
A problem occurred when registering a file transfer request.
Severity
20 : Error
Explanation
A file transfer request had been received by this agent, but the agent was unable to register the request.
Response
Examine the associated problem report linked with this report for further details.
BFGCH0006E
A problem occurred when registering an internal file transfer request.
Severity
20 : Error
Explanation
An internal message has been received by this agent, but the agent was unable to register the request.
Response
Examine the associated problem report linked with this report for further details.
BFGCH0007E
An internal error has occurred. 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.
BFGCH0008E
An internal error has occurred. A problem occurred when registering an internal shutdown message with the state store.
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.
BFGCH0009E
An internal error has occurred. The agent''s internal message handler has received a message of an unknown type. Message "<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.
BFGCH0010E
An internal error has occurred. This receiving agent has received an internal file transfer request with no files 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.
BFGCH0011E
The originating user's host name is missing from the file transfer XML request
Severity
20 : Error
Explanation
A file transfer request has been received by this agent but the XML request is missing the necessary originating user identification.
Response
Validate the generation of the file transfer request to ensure the request complies with the XML schema.
BFGCH0012E
An internal error has occurred.
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.
BFGCH0013E
The originating user's ID is missing from the file transfer XML request
Severity
20 : Error
Explanation
A file transfer request has been received by this agent but the XML request is missing the necessary originating user identification.
Response
Validate the generation of the file transfer request to ensure the request complies with the XML schema.
BFGCH0014E
The destination agent name is missing from the file transfer XML request
Severity
20 : Error
Explanation
A file transfer request has been received by this agent. However, the XML request is missing the necessary destination agent name.
Response
Validate the generation of the file transfer request to ensure the request complies with the XML schema.
BFGCH0015E
The destination queue manager name is missing from the file transfer XML request
Severity
20 : Error
Explanation
A file transfer request has been received by this agent. However, the XML request is missing the necessary destination queue manager name associated with the destination agent.
Response
Validate the generation of the file transfer request to ensure the request complies with the XML schema.
BFGCH0016I
A request to shut down this agent has been received.
Severity
0 : Information
Explanation
An external shutdown request has been received and this agent is now waiting for the current transfer to complete.
Response
No action is required.
BFGCH0017E
The scheduler is not available.
Severity
20 : Error
Explanation
The scheduler is not available for processing new actions.
Response
Examine previous error messages to determine why the scheduler is offline.
BFGCH0018I
An internal error has occurred. The command message has been discarded because ''<insert_0>''.
Severity
0 : Information
Explanation
The agent's command handler has been unable to process a message and that message has now been discarded.
Response
If the problem persists, see problem determination information in the product documentation.
BFGCH0019E
An internal error has occurred. The schedule has failed to initialize due 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.
BFGCH0020E
An internal error has occurred. The command queue interaction with the queue manager has with failed with an exception.
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.
BFGCH0021E
An internal error has occurred. An attempt to publish an audit message resulted in the following 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.
BFGCH0022E
An internal error has occurred. The command queue interaction with the queue manager has with failed with an exception.
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.
BFGCH0023E
An internal error has occurred. The command queue interaction with the queue manager has with failed with an exception.
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.
BFGCH0024E
An internal error has occurred. An internal message has not been successfully parsed.
Severity
20 : Error
Explanation
This agent has received an internal request that does not match expected message formats.
Response
If the problem persists, see problem determination information in the product documentation.
BFGCH0025E
An internal error has occurred. An unsupported internal message has beem received. Message = "<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.
BFGCH0026E
An internal error has occurred. Received an internal XML message of an unknown format.
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.
BFGCH0027I
An internal error has occurred. The command message has been discarded because ''<insert_0>''.
Severity
0 : Information
Explanation
The command handler of the agent has been unable to process a message and that message has now been discarded.
Response
If the problem persists, see problem determination information in the product documentation.
BFGCH0028E
An internal error has occurred. A internal problem relating to the decoding of an XML message has occurred.
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.
BFGCH0029E
The XML schema checker reports the following problem: ''<insert_0>''
Severity
20 : Error
Explanation
A file transfer request received by this agent has failed the XML schema check.
Response
Validate the generation of the file transfer request to ensure the request complies with the XML schema.
BFGCH0030E
An internal error has occurred. An unsupported encoding schema has been detected.
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.
BFGCH0031E
An internal error has occurred. An unsupported encoding schema has been detected.
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.
BFGCH0032E
An internal error has occurred. An unsupported encoding schema has been detected.
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.
BFGCH0033E
An internal error has occurred. The command queue interaction with the queue manager has with failed with an exception.
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.
BFGCH0034E
An internal error has occurred. An attempt to reconfigure a command queue package when not in Unit Test mode occurred.
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.
BFGCH0035E
An internal error has occurred. An attempt to reconfigure a command queue package when not in Unit Test mode occurred.
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.
BFGCH0036E
An internal error has occurred. An attempt to reconfigure a command queue package when not in Unit Test mode occurred.
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.
BFGCH0037E
An internal error has occurred when reading the metadata for the XML message.
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.
BFGCH0038E
An internal error has occurred when analyzing the trigger check of <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.
BFGCH0039E
An internal error has occurred when creating an audit object.
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.
BFGCH0040E
The XML parser has detected the following error within an XML message ''<insert_0>''.
Severity
20 : Error
Explanation
A received XML message has failed to match the defined schema.
Response
Review the XML message and correct as necessary to match the schema.
BFGCH0041E
The XML parser has detected the following unrecoverable error within an XML message ''<insert_0>''.
Severity
20 : Error
Explanation
A received XML message has failed to match the defined schema with an unrecoverable error.
Response
Review the XML message and correct as necessary to match the schema.
BFGCH0042E
The XML parser has detected the following warning within an XML message ''<insert_0>''.
Severity
20 : Error
Explanation
A received XML message has failed to match the defined schema and has reported a warning.
Response
Review the XML message and correct as necessary to match the schema.
BFGCH0043E
An internal error has occurred while attempting to read the XML message.
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.
BFGCH0044E
An internal error has occurred while attempting to configure the parser.
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.
BFGCH0045E
An internal error has occurred related to the formatting of an XML message.
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.
BFGCH0046E
Either the source or destination file has not been specified.
Severity
20 : Error
Explanation
Both the source and destination file must be specified.
Response
Submit the transfer request again with both a source and destination file specified.
BFGCH0047E
The agent has received a reason code of ''<insert_0>'' from the MQI. The agent cannot continue processing and will now end.
Severity
20 : Error
Explanation
The agent has received the specified MQI reason code. The agent cannot continue processing after receiving this reason code from the MQI. The agent process will end.
Response
Consult the IBM MQ product documentation to determine the cause of the problem. Resolve the problem. Contact the IBM support center if you need further assistance.
BFGCH0048E
An internal error has occurred. 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.
BFGCH0049E
An internal error has occurred. 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.
BFGCH0050E
The agent has detected an error condition that prevents the agent from continuing. The error message is: <insert_0>
Severity
20 : Error
Explanation
The agent has received the specified error. The agent cannot continue processing after receiving this error. The agent process will end.
Response
Use the information in the error message to determine the cause of the problem. Resolve the problem. Contact the IBM support center if you need further assistance.
BFGCH0051E
The agent has received an MQI reason code of ''<insert_0>''. The agent cannot continue processing and will now end.
Severity
20 : Error
Explanation
The agent has received the specified MQI reason code. The agent cannot continue processing after receiving this reason code from the MQI. The agent process will end.
Response
Refer to the IBM MQ product documentation to determine the cause of the reason code. Resolve the problem. Contact the IBM support center if you need further assistance.
BFGCH0052E
An internal error has occurred. 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.
BFGCH0053E
The agent has detected an error condition that prevents the agent from continuing. The error message is: <insert_0>
Severity
20 : Error
Explanation
The agent has received the specified error. The agent cannot continue processing after receiving this error. The agent process will end.
Response
Use the information in the error message to determine the cause of the problem. Resolve the problem. Contact the IBM support center if you need further assistance.
BFGCH0054E
An internal error has occurred. 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.
BFGCH0055E
An internal error has occurred. 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.
BFGCH0056E
An internal error has occurred, with an incomplete Trigger definition with <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.
BFGCH0057E
An internal error has occurred while generating an trigger with the type <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.
BFGCH0058E
An internal error has occurred. A request to stop this agent has failed due to an invalid stop mode of <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.
BFGCH0059I
A request to immediately shut down this agent has been received.
Severity
0 : Information
Explanation
An external shutdown request has been received and this agent is performing an immediate shutdown.
Response
No action is required.
BFGCH0060E
An internal error has occurred. A second invalid set of metadata has been found in the file transfer XML request.
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.
BFGCH0061E
An internal error has occurred. The priority value of <insert_0> in file transfer XML request is invalid.
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.
BFGCH0062E
An internal error has occurred. The transfer id ''<insert_0>'' has an invalid format.
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.
BFGCH0063E
A problem occurred when registering an internal forget message with the state store.
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.
BFGCH0064W
A trigger definition <insert_0> was not successful and the file transfer will not proceed.
Severity
10 : Warning
Explanation
The file transfer request submitted included one or more trigger options. One of the triggers was not successful and the file transfer will not proceed.
Response
No action is required
BFGCH0065E
A submitted file transfer request with message identifier <insert_0> is malformed.
Severity
20 : Error
Explanation
A request submitted to this agent is malformed and cannot be evaluated. The request will not proceed.
Response
Review the action that generated this request and retry.
BFGCH0066E
An internal error has occurred. An exception has been reported by the State Store. 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.
BFGCH0068E
An internal error has occurred. An unsupported encoding schema has been detected.
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.
BFGCH0069W
A transfer log message has failed publication. Details of the failure are as follows : Agent Name : ''<insert_0>'' Transfer Id : ''<insert_1>'' Message Type : ''<insert_2>'' Topic Name : ''<insert_3>'' MQ Reason Code : ''<insert_4>'' MQ Error Code : ''<insert_5>''
Severity
10 : Warning
Explanation
A transfer log message has failed publication on the coordination queue manager.
Response
Consult the IBM MQ product documentation to interpret the MQ Reason and Error codes.Check the MQMFT IBM MQ configuration for the reason for the publication failure.
BFGCH0070W
GETs have been inhibited for the agent's command queue.
Severity
10 : Warning
Explanation
GETs have been inhibited for the agent's command queue. The agent will retry every 30 seconds until GETs are enabled for the agent's command queue. When GETs are enabled the agent will resume operation.
Response
Enable GETs for the agent's command queue. Please refer to the IBM MQ documentation for details.
BFGCH0071I
GETs have been re-enabled for the agent's command queue.
Severity
0 : Information
Explanation
GETs have been re-enabled for the agent's command queue. The agent has resumed normal operation.
Response
No user action is required.
BFGCH0072E
An internal error has occurred. Unknown monitor request.
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.
BFGCH0073W
Resource monitor message has been discarded because ''<insert_0>''.
Severity
10 : Warning
Explanation
The agent's resource monitor has been unable to process a message and that message has now been discarded.
Response
If the problem persists, see problem determination information in the product documentation.
BFGCH0074E
An unexpected value of ''<insert_0>'' was supplied as the value for the ''type'' attribute of the command element, inside a transfer request message.
Severity
20 : Error
Explanation
The XML in a transfer request message is not valid because the specified value was supplied as the value of the 'type' attribute. Valid values are 'executable', 'antscript' or 'jcl'. The transfer request message will not be processed and a log message containing the malformed message will be published to the coordination queue manager.
Response
Determine the source of the transfer request message. If the transfer request message was created by a user written application, correct the application so that it generates a valid XML transfer request message. If the transfer request message was generated by part of the IBM MQ Managed File Transfer product, contact IBM service for further assistance.
BFGCH0075E
An unexpected 'property' element was found as a child element of a 'command' element which specifies a 'type' attribute of 'executable' in the XML content of a transfer request message.
Severity
20 : Error
Explanation
It is not valid to specify a 'property' element as the child of a 'command' element with a 'type' attribute of 'executable' in the XML content of a transfer request message. The transfer request message will not be processed and a log message containing the malformed message will be published.
Response
Determine the source of the transfer request message. If the transfer request message was created by a user written application, correct the application so that it generates a valid XML transfer request message. If the transfer request message was generated by part of the IBM MQ Managed File Transfer product, contact IBM service for further assistance.
BFGCH0076E
An unexpected 'target' element was found as a child element of a 'command' element which specifies a 'type' attribute of 'executable' in the XML content of a transfer request message.
Severity
20 : Error
Explanation
It is not valid to specify a 'target' element as the child of a 'command' element with a 'type' attribute of 'executable' in the XML content of a transfer request message. The transfer request message will not be processed and a log message containing the malformed message will be published.
Response
Determine the source of the transfer request message. If the transfer request message was created by a user written application, correct the application so that it generates a valid XML transfer request message. If the transfer request message was generated by part of the IBM MQ Managed File Transfer product, contact IBM service for further assistance.
BFGCH0077E
An unexpected 'argument' element was found as a child element of a 'command' element which specifies a 'type' attribute of 'antscript' in the XML content of a transfer request message.
Severity
20 : Error
Explanation
It is not valid to specify a 'argument' element as the child of a 'command' element with a 'type' attribute of 'antscript' in the XML content of a transfer request message. The transfer request message will not be processed and a log message containing the malformed message will be published.
Response
Determine the source of the transfer request message. If the transfer request message was created by a user written application, correct the application so that it generates a valid XML transfer request message. If the transfer request message was generated by part of the IBM MQ Managed File Transfer product, contact IBM service for further assistance.
BFGCH0078E
An unexpected 'property' element was found as a child element of a 'command' element which specifies a 'type' attribute of 'jcl' in the XML content of a transfer request message.
Severity
20 : Error
Explanation
It is not valid to specify a 'property' element as the child of a 'command' element with a 'type' attribute of 'jcl' in the XML content of a transfer request message. The transfer request message will not be processed and a log message containing the malformed message will be published.
Response
Determine the source of the transfer request message. If the transfer request message was created by a user written application, correct the application so that it generates a valid XML transfer request message. If the transfer request message was generated by part of the IBM MQ Managed File Transfer product, contact IBM service for further assistance.
BFGCH0079E
An unexpected 'target' element was found as a child element of a 'command' element which specifies a 'type' attribute of 'jcl' in the XML content of a transfer request message.
Severity
20 : Error
Explanation
It is not valid to specify a 'target' element as the child of a 'command' element with a 'type' attribute of 'jcl' in the XML content of a transfer request message. The transfer request message will not be processed and a log message containing the malformed message will be published.
Response
Determine the source of the transfer request message. If the transfer request message was created by a user written application, correct the application so that it generates a valid XML transfer request message. If the transfer request message was generated by part of the IBM MQ Managed File Transfer product, contact IBM service for further assistance.
BFGCH0080E
An unexpected 'argument' element was found as a child element of a 'command' element which specifies a 'type' attribute of 'jcl' in the XML content of a transfer request message.
Severity
20 : Error
Explanation
It is not valid to specify a 'argument' element as the child of a 'command' element with a 'type' attribute of 'jcl' in the XML content of a transfer request message. The transfer request message will not be processed and a log message containing the malformed message will be published.
Response
Determine the source of the transfer request message. If the transfer request message was created by a user written application, correct the application so that it generates a valid XML transfer request message. If the transfer request message was generated by part of the IBM MQ Managed File Transfer product, contact IBM service for further assistance.
BFGCH0081E
Invalid trace request change to <insert_0> has not been completed.
Severity
20 : Error
Explanation
A request to change trace level has been received by the agent. However the request trace level is unknown and the request cannot be completed.
Response
Review the request trace level and reissue the request.
BFGCH0082E
An internal error has occurred. File IO system did not return the required attributes for filename <insert_0> and type <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.
BFGCH0083E
The user (<insert_0>) does not have the authority (<insert_1>) required to shut down agent ''<insert_2>''.
Severity
20 : Error
Explanation
The specified user requested the specified agent to shut down. The agent did not shut down because the specified user does not have the specified authority, which is required in order to successfully request that the agent shuts down.
Response
Determine if the specified user should be able to shut down the specified agent. If the user should be able to shut down the agent then consult the IBM MQ Managed File Transfer documentation to determine how to grant the specified authority to the specified user. If the user should not be able to shut down the agent then inform the specified user that they are not authorised to perform the action and should stop trying to shut down the specified agent.
BFGCH0084E
The user (<insert_0>) does not have the authority (<insert_1>) required to enable diagnostic trace for agent ''<insert_2>''.
Severity
20 : Error
Explanation
The specified user requested the specified agent to enable diagnostic trace. The agent did not enable diagnostic trace because the specified user does not have the specified authority, which is required in order to successfully request that the agent enables diagnostic trace.
Response
Determine if the specified user should be able to enable diagnostic trace for the specified agent. If the user should be able to enable diagnostic trace for the agent then consult the IBM MQ Managed File Transfer documentation to determine how to grant the specified authority to the specified user. If the user should not be able to enable diagnostic trace for the agent then inform the specified user that they are not authorised to perform the action and should stop trying to enable diagnostic trace for the specified agent.
BFGCH0085E
Agent ''<insert_0>'' and agent ''<insert_1>'' have different levels of authority checking.
Severity
20 : Error
Explanation
A file transfer between the two specified agents could not take place because the agents have been configured with different levels of authority checking. For files to be transferred between agents, both agents must be configured to use the same level of authority checking.
Response
Configure the specified agents so that their 'authorityChecking' properties have the same value. Restart the agents so that the changes take effect. Retry the transfer.
BFGCH0086E
The user (<insert_0>) associated with the source agent (<insert_1>) does not have the authority (<insert_2>) required to transfer files to agent (<insert_3>).
Severity
20 : Error
Explanation
The specified source agent does not have authority to transfer files to the specified destination agent.
Response
Determine if the specified agent should be able to transfer files to the specified agent. If the agent should be able to carry out this action then consult the IBM MQ Managed File Transfer documentation to determine how to grant the specified authority to the specified agent.
BFGCH0087E
The user (<insert_0>) requesting a transfer of files to agent (<insert_1>) does not have the required authority (<insert_2>) to perform this operation.
Severity
20 : Error
Explanation
The specified user does not have authority to transfer files to the specified destination agent.
Response
Determine if the specified user should be able to transfer files to the specified agent. If the user should be able to carry out this action then consult the IBM MQ Managed File Transfer documentation to determine how to grant the specified authority to the specified agent. If the user should not be able to transfer files to the specified agent then inform the specified user that they are not authorized to perform the action and should stop trying to perform the transfer operation.
BFGCH0088E
The user (<insert_0>) requesting a transfer of files from agent (<insert_1>) does not have the required authority (<insert_2>) to perform this operation.
Severity
20 : Error
Explanation
The specified user does not have authority to transfer files from the specified source agent.
Response
Determine if the specified user should be able to transfer files from the specified agent. If the user should be able to carry out this action then consult the IBM MQ Managed File Transfer documentation to determine how to grant the specified authority to the specified agent. If the user should not be able to transfer files from the specified agent then inform the specified user that they are not authorized to perform the action and should stop trying to perform the transfer operation.
BFGCH0089E
User (<insert_0>) has requested the creation of a scheduled transfer but does not have the required authority (<insert_1>) to perform this operation.
Severity
20 : Error
Explanation
The specified user does not have authority to schedule transfers.
Response
Determine if the specified user should be able to schedule transfers. If the user should be able to carry out this action then consult the IBM MQ Managed File Transfer documentation to determine how to grant the specified authority to the specified user. If the user should not be able to schedule transfers then inform the specified user that they are not authorized to perform the action and should stop trying to schedule transfers.
BFGCH0090E
User (<insert_0>) has requested the deletion of a scheduled transfer that belongs to user (<insert_1>) but does not have the required authority (<insert_2>) to perform this operation.
Severity
20 : Error
Explanation
The specified user does not have authority to delete the schedule transfers. The scheduled transfer has not been deleted.
Response
Determine if the specified user should be able to delete scheduled transfers. If the user should be able to carry out this action then consult the IBM MQ Managed File Transfer documentation to determine how to grant the specified authority to the specified user. If the user should not be able to delete scheduled transfers then inform the specified user that they are not authorized to perform the action and should stop trying to delete scheduled transfers.
BFGCH0091E
User (<insert_0>) has requested the deletion of a scheduled transfer but does not have either the (<insert_1>) or (<insert_2>) authorities required to perform this operation.
Severity
20 : Error
Explanation
The specified user does not have authority to delete the schedule transfers. The scheduled transfer has not been deleted.
Response
Determine if the specified user should be able to delete scheduled transfers. If the user should be able to carry out this action then consult the IBM MQ Managed File Transfer documentation to determine how to grant the specified authority to the specified user. If the user should not be able to delete scheduled transfers then inform the specified user that they are not authorized to perform the action and should stop trying to delete scheduled transfers.
BFGCH0092E
The transfer request has a trigger specified and the source agent is configured as a protocol bridge agent. The transfer request has not been executed.
Severity
20 : Error
Explanation
It is not supported for transfer requests to specify a trigger when the source agent is configured as a protocol bridge agent.
Response
Resubmit the transfer request without the trigger specified. Alternatively resubmit the request to a source agent that is not configured as protocol bridge agent.
BFGCH0093E
The transfer with ID ''<insert_0>'' has failed. The agent has received a reason code of ''<insert_1>'' from IBM MQ when sending a negative response message to source queue ''<insert_2>'' on Queue Manager ''<insert_3>''
Severity
20 : Error
Explanation
The agent has received the specified MQI reason code. This agent is unable to send the negative response message to the source agent.
Response
Consult the IBM MQ product documentation to determine the cause of the reason code. Resolve the problem. Contact the IBM support center if you need further assistance. The transfer on the source agent will remain in a waiting state. To remove the transfer it will be necessary to manually cancel the transfer
BFGCH0094W
Trial version agent ''<insert_1>'' has rejected transfer request from production version agent ''<insert_0>''
Severity
10 : Warning
Explanation
A trial version agent has received a file transfer request from a production agent. This is not supported and the request has been refused.
Response
Review the configuration and where necessary upgrade trail version agents to production agents.
BFGCH0095W
Production version agent ''<insert_0>'' has rejected transfer request from trial version agent ''<insert_2>''
Severity
10 : Warning
Explanation
A production version agent has received a file transfer request from a trial agent. This is not supported and the request has been refused.
Response
Review the configuration and where necessary upgrade trial version agents to production agents.
BFGCH0096E
An internal error has been detected. 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.
BFGCH0097E
A request to transfer a file to a destination file space cannot be completed as the named destination agent is not configured to have a file space.
Severity
20 : Error
Explanation
An attempt to transfer files to a file space has failed as the destination agent has not been configured for file space usage.
Response
Review the transfer request and check that the destination agent is correct. If the destination agent is not configured to write a file to a file space, consult the IBM MQ Managed File Transfer documentation to determine how to configure the agent to use a file space."
BFGCH0098E
An internal error has occurred. The Loading of XML Schemas 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.
BFGCH0099E
The agent cannot interpret the content of a message that is encoded using character set identifier ''<insert_0>''.
Severity
20 : Error
Explanation
The agent cannot interpret the content of a message encoded with the specified character set identifier because the character set identifier is not supported by the agent. The message will not be processed. The character set identifier associated with a message is set by the program that produces the message. The character set identifier can also be changed by IBM MQ, for example by routing the message using IBM MQ channels that perform data conversion.
Response
Determine the reason that the Coded Character Set Identifier field of IBM MQ Message Descriptor has been set to the specified value. Resolve this issue to ensure that the Coded Character Set Identifier is not changed or is only changed to a value that is supported by the agent. If required, refer to the IBM MQ Managed File Transfer product documentation to determine the character sets that an agent process supports.
BFGCH0100E
The agent cannot interpret the content of a message that is encoded using character set identifier ''<insert_0>''.
Severity
20 : Error
Explanation
The agent cannot interpret the content of a message encoded with the specified character set identifier because the character set identifier is not supported by the agent. The message will not be processed. The character set identifier associated with a message is set by the program that produces the message. The character set identifier can also be changed by IBM MQ, for example by routing the message using IBM MQ channels that perform data conversion.
Response
Determine the reason that the Coded Character Set Identifier field of IBM MQ Message Descriptor has been set to the specified value. Resolve this issue to ensure that the Coded Character Set Identifier is not changed or is only changed to a value that is supported by the agent. If required, refer to the IBM MQ Managed File Transfer product documentation to determine the character sets that an agent process supports.
BFGCH0101E
Both the source and destination of the transfer are IBM MQ queues.
Severity
20 : Error
Explanation
Either the source or destination of a transfer may be an IBM MQ queue but not both.
Response
Modify the transfer request so either the source or destination is not a IBM MQ queue. Then submit the transfer again.
BFGCH0102E
The transfer request specifies Web Gateway agent ''<insert_0>'' as the source agent. Web Gateway agents cannot be the source agent for a transfer.
Severity
20 : Error
Explanation
It is not supported for transfer requests to specify a Web Gateway agent as the source agent.
Response
Resubmit the request to a source agent that is not configured as a Web Gateway agent.
BFGCH0103E
The transfer request specifies Web Gateway agent ''<insert_0>'' as the destination agent. Web Gateway agents can be the destination agent only for a transfer to a file space.
Severity
20 : Error
Explanation
It is not supported for transfer requests to specify a Web Gateway agent as the destination agent when the destination is not a file space.
Response
Resubmit the request to a destination agent that is not configured as a Web Gateway agent.
BFGCH0104E
This agent has received a request for a different agent with name <insert_0> associated with queue manager <insert_1>.
Severity
20 : Error
Explanation
This agent has received a request to perform a transfer belonging to another agent. The transfer cannot be performed and the request is discarded.
Response
Locate where the original transfer was generated and ensure the correct values have been assigned. If the queue manager name is blank or null this might indicate that a Web Gateway servlet has sent a transfer request to this agent, which is not configured as a Web Gateway agent.
BFGCH0105E
This agent with name <insert_0> and queue manager <insert_1> has received a request for a different agent with name <insert_2> and queue manager <insert_3>.
Severity
20 : Error
Explanation
This agent has received a request to perform a transfer belonging to another agent. The transfer cannot be performed and the request is discarded.
Response
Locate where the original transfer was generated and ensure the correct values have been assigned.
BFGCH0106E
Pre-source calls are not supported on Connect:Direct bridge agents.
Severity
20 : Error
Explanation
Connect:Direct bridge agents do not support transfers that contain pre-source calls.
Response
Remove the pre-source call from the transfer definition an try the transfer again.
BFGCH0107E
Post-source calls are not supported on Connect:Direct bridge agents.
Severity
20 : Error
Explanation
Connect:Direct bridge agents do not support transfers that contain post-source calls.
Response
Remove the post-source call from the transfer definition an try the transfer again.
BFGCH0108E
Pre-destination calls are not supported on Connect:Direct bridge agents.
Severity
20 : Error
Explanation
Connect:Direct bridge agents do not support transfers that contain pre-destination calls.
Response
Remove the pre-destination call from the transfer definition an try the transfer again.
BFGCH0109E
Post-destination calls are not supported on Connect:Direct bridge agents.
Severity
20 : Error
Explanation
Connect:Direct bridge agents do not support transfers that contain post-destination calls.
Response
Remove the post-destination call from the transfer definition an try the transfer again.
BFGCH0110E
Program calls are not supported on Connect:Direct bridge agents.
Severity
20 : Error
Explanation
Connect:Direct bridge agents do not support program call requests.
Response
Submit the program call request to an agent that is not configured as a Connect:Direct bridge.
BFGCH0111E
Wildcards in source file specifications are not supported for transfers from a Connect:Direct node.
Severity
20 : Error
Explanation
Connect:Direct bridge agents do not support wildcard characters in the source specification for transfers from Connect:Direct nodes.
Response
Remove the wildcard from the transfer request and submit the transfer again.
BFGCH0112E
Transfers from a Connect:Direct node to a Connect:Direct node are not supported.
Severity
20 : Error
Explanation
Connect:Direct bridge agents do not support transfers in which both the source and destination files are located on a Connect:Direct node.
Response
Change the source or the destination of the transfer to be a regular MQMFT agent and submit the transfer again.
BFGCH0113E
The XML trace request contains mixed triggers. The -disableOnAnyFFDC parameter cannot be combined with the -disableOnFFDC parameter.
Severity
20 : Error
Explanation
A request for changing trace settings has been received, but contains mixed FFDC triggers. It contains requests to disable on both any FFDC and a specific FFDC. This is ambiguous and the request could not be completed.
Response
Review the XML request and correct as necessary. If this was generated by a supplied command then contact the IBM Support Center for further assistance.
BFGCH0114E
Ant calls are not supported on agents running on 4690 OS.
Severity
20 : Error
Explanation
Agents running on 4690 OS do not support transfers that contain calls to Ant scripts.
Response
Remove the Ant call from the transfer definition and attempt the transfer again.
BFGCH0115E
An unexpected 'property' element was found as a child element of a 'command' element which specifies a 'type' attribute of '4690background' in the XML content of a transfer request message.
Severity
20 : Error
Explanation
It is not valid to specify a 'property' element as the child of a 'command' element with a 'type' attribute of '4690background' in the XML content of a transfer request message. The transfer request message will not be processed and a log message containing the malformed message will be published.
Response
Determine the source of the transfer request message. If the transfer request message was created by a user written application, correct the application so that it generates a valid XML transfer request message. If the transfer request message was generated by part of the IBM MQ Managed File Transfer product, contact IBM service for further assistance.
BFGCH0116E
An unexpected 'target' element was found as a child element of a 'command' element which specifies a 'type' attribute of '4690background' in the XML content of a transfer request message.
Severity
20 : Error
Explanation
It is not valid to specify a 'target' element as the child of a 'command' element with a 'type' attribute of '4690background' in the XML content of a transfer request message. The transfer request message will not be processed and a log message containing the malformed message will be published.
Response
Determine the source of the transfer request message. If the transfer request message was created by a user written application, correct the application so that it generates a valid XML transfer request message. If the transfer request message was generated by part of the IBM MQ Managed File Transfer product, contact IBM service for further assistance.
BFGCH0117E
An unexpected 'argument' element was found as a child element of a 'command' element which specifies a 'type' attribute of '4690background' in the XML content of a transfer request message.
Severity
20 : Error
Explanation
It is not valid to specify a 'argument' element as the child of a 'command' element with a 'type' attribute of '4690background' in the XML content of a transfer request message. The transfer request message will not be processed and a log message containing the malformed message will be published.
Response
Determine the source of the transfer request message. If the transfer request message was created by a user written application, correct the application so that it generates a valid XML transfer request message. If the transfer request message was generated by part of the IBM MQ Managed File Transfer product, contact IBM service for further assistance.
BFGCH0118E
Attribute ''<insert_1>'' is not valid for command type ''<insert_0>''.
Severity
20 : Error
Explanation
It is not valid to specify the attribute for the command type.
Response
Determine the source of the transfer request message. If the transfer request message was created by a user written application, correct the application so that it generates a valid XML transfer request message. If the transfer request message was generated by part of the IBM MQ Managed File Transfer product, contact IBM service for further assistance.
BFGCH0120E
An invalid component name, ''<insert_0>'' specified.
Severity
20 : Error
Explanation
A request to enable or disable logging for a component has been received by the agent. However the requested component name is unknown and the request cannot be completed.
Response
Review the component name and reissue the request.
BFGCH0121E
An invalid operation type, ''<insert_0>'' was specified.
Severity
20 : Error
Explanation
A request to enable or disable logging for a component has been received by the agent. However the requested operation type is unknown and the request cannot be completed.
Response
Review the operation type and reissue the request.
BFGCH0122E
Attempt to read file path(s): ''<insert_0>'' has been denied. The file path(s) are located outside of the restricted transfer sandbox.
Severity
20 : Error
Explanation
The system was unable to process the managed transfer request as the transfer specification was not within the restricted transfer sandbox.
Response
Ensure that the transfer specification refers to locations within the restricted sandbox.
BFGCH9999E
<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.