An internal error has occurred. A request has been made to create an invalid resource. Resource reference 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.
BFGDM0002E
An internal error has occurred. Invalid units of <insert_0> found in file size comparison.
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.
BFGDM0003E
An internal error has occurred. A request has been made to create an invalid task. Task reference 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.
BFGDM0004E
An internal messaging problem prevented the monitor task from completing successfully. The IBM MQ completion code was <insert_0>, and the reason code was <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.
BFGDM0005E
An internal messaging problem prevented the monitor task from completing successfully. The IBM MQ completion code was <insert_0>, and the reason code was <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.
BFGDM0006E
An internal error has occurred. A request has been made to create an invalid matcher. Matcher reference 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.
BFGDM0009E
Cannot locate the agent and associated queue manager from the task XML.
Severity
20 : Error
Explanation
Both the 'agent' and 'QMgr' attributes must be present on the 'sourceAgent' element in the task XML.
Response
Delete the monitor. Modify the task XML so both the 'agent' and 'QMgr' attributes are present on the 'sourceAgent' element. Submit the monitor again.
BFGDM0010E
An internal error has occurred. An xpath error has occurred during processing a XML task script. Error reported 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.
BFGDM0012E
Monitor <insert_0> is not present and could not be stopped
Severity
20 : Error
Explanation
The requested monitor could not be located within the agent. Therefore the monitor was not stopped.
Response
Run the fteListMonitors command to validate the monitor name given.
BFGDM0013E
The monitor XML definition has parsing errors.
Severity
20 : Error
Explanation
The given monitor definition does not match the monitor XML schema. The monitor creation has been rejected.
Response
Review the associated error messages and correct the monitor XML definition.
BFGDM0014E
An internal error has occurred. A parsing exception occurred while processing a monitor definition. 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.
BFGDM0015E
An internal error has occurred. SAX exception occurred while processing a monitor definition. 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.
BFGDM0016E
An internal error has occurred. An IO exception occurred while processing a monitor definition. 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.
BFGDM0017E
The new monitor definition for monitor <insert_0> is already loaded.
Severity
20 : Error
Explanation
Attempt was made to create a monitor definition with the same name as an existing monitor.
Response
A monitor definition must be deleted before it can be created.
BFGDM0018I
A request to delete monitor <insert_0> has been submitted.
Severity
0 : Information
Explanation
A request to delete a named monitor has been successful sent tothe owning agent.
Response
No action is required.
BFGDM0019E
An internal error has occurred. No resources have been defined for monitor <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.
BFGDM0020E
An internal error has occurred. More than one resources have been defined for monitor <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.
BFGDM0021E
An internal error has occurred. No triggers have been defined for monitor <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.
BFGDM0022E
An internal error has occurred. No tasks have been defined for monitor <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.
BFGDM0023E
An internal error has occurred. Too many tasks have been defined for monitor <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.
BFGDM0024I
Monitor <insert_0> successfully submitted a transfer request reference <insert_1>.
Severity
0 : Information
Explanation
The resource monitor has generated a transfer request and been successfully submitted to the named agent.
Response
No action is required
BFGDM0025E
An internal error has occurred. monitor <insert_0> task execution completed with state <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.
BFGDM0026E
An internal error has occurred. monitor <insert_0> task execution failed. Exception: <insert_1>
Severity
20 : Error
Explanation
This exception is unexpected. The cause is not immediately known.
Response
If the problem persists, see problem determination information in the product documentation.
BFGDM0027E
An internal error has occurred. Regenerating the transfer request XML failed with 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.
BFGDM0028E
An internal error has occurred. Regenerating the transfer request XML failed with 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.
BFGDM0029E
An internal error has occurred. Regenerating the transfer request XML failed with 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.
BFGDM0030E
An internal error has occurred. Unable to handle matcher 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.
BFGDM0031E
Attempted to start an undefined monitor. Monitor name was <insert_0>.
Severity
20 : Error
Explanation
A request was received to start a monitor which is not present or defined.
Response
Check the name of the monitor and its existing, then reissue request.
BFGDM0032I
Monitor <insert_0> has been started.
Severity
0 : Information
Explanation
A request to start a monitor was received and been successfully executed.
Response
No action required.
BFGDM0033E
An internal error has occurred. A persistable object could not be serialised. Reference <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.
BFGDM0034E
An internal error has occurred. A URL decoding error 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.
BFGDM0035E
An internal error has occurred. A corrupt persisted object has been encountered. Eye catcher 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.
BFGDM0036E
An internal error has occurred. There are insufficient data bytes to create string of <insert_0> bytes.
Severity
20 : Error
Explanation
This exception is unexpected. The cause is not immediately known.
Response
If the problem persists, see problem determination information in the product documentation.
BFGDM0038E
An internal error has occurred. There are insufficient data bytes from message <insert_0> with expected length of <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.
BFGDM0039E
An internal error has occurred. Could not read schedule message. 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.
BFGDM0040E
An internal error has occurred. It was not possible to store the configuration message. 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.
BFGDM0041E
An internal error has occurred. It was not possible to store the matcher data message. 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.
BFGDM0042E
An internal error has occurred. It was not possible to store the schedule message. 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.
BFGDM0043E
An internal error has occurred. It was not possible to remove a configuration message from the store. 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.
BFGDM0044E
An internal error has occurred. It was not possible to remove a matcher data message from the store. 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.
BFGDM0045E
An internal error has occurred. It was not possible to access WMQ Queue FTEEVENT. 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.
BFGDM0047E
An internal error has occurred. Parsing an internal XML generated a SAX error. 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.
BFGDM0048E
An internal error has occurred. Parsing an internal XML generated a IO error. 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.
BFGDM0049E
An internal error has occurred. Parsing an internal XML generated a parser configuration error. 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.
BFGDM0050E
An internal error has occurred. Parsing an internal XML generated a parser configuration error. 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.
BFGDM0051E
An internal error has occurred. Unknown top level persistent object. Eye catcher was <insert_0>.
Severity
20 : Error
Explanation
This exception is unexpected. The cause is not immediately known.
Response
If the problem persists, see problem determination information in the product documentation.
BFGDM0052E
An internal error has occurred. There is a missing top level persistent object. Reference name <insert_0>.
Severity
20 : Error
Explanation
This exception is unexpected. The cause is not immediately known.
Response
If the problem persists, see problem determination information in the product documentation.
BFGDM0053E
An internal error has occurred. Resource monitor recovery fail with a WMQ failure. 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.
BFGDM0054E
An internal error has occurred. A resource monitor recovery failed with a WMQ warning. 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.
BFGDM0055E
An internal error has occurred. A resource monitor recovery failed with a WMQ JMQI Failure. 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.
BFGDM0056E
A monitor task could not complete as variable <insert_0> had value <insert_1> which only had <insert_2> token(s). However the variable expression requires <insert_3> token(s).
Severity
20 : Error
Explanation
The given task XML script had a variable replacement expression which is required to subdivide the given value into a number of tokens. The subdivided tokens was not sufficient to meet the requirements of the expression. As a result the task was not completed.
Response
Review the associated task XML script against the actual values being passed to it.
BFGDM0057E
A monitor task could not complete as a variable substitution <insert_0> specified a range of tokens in a mixed direction.
Severity
20 : Error
Explanation
The given task XML script has a variable substitution with token ranges with mixed direction. The tokens must either both positive for reading left to right or both negative for reading right to left.
Response
Review the task XML script and check that the token directions are not mixed.
BFGDM0058E
A monitor task could not complete as a variable substitution <insert_0> specified a range of tokens in a reversed order.
Severity
20 : Error
Explanation
The given task XML script has a variable substitution with token ranges. The token ranges have the start token after the end token which is not valid.
Response
Review the task XML script and check that the token directions are in the correct order. For reading left to right the start token has to be less than or equals to the end token. The same applies for reading right to left.
BFGDM0059E
An internal error has occurred. A monitor task could not complete as a nameless variable substitution was given. Reference <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.
BFGDM0060E
A monitor task could not complete as a variable substitution <insert_0> was not present.
Severity
20 : Error
Explanation
The requested variable substitution has failed as the requested variable is not present.
Response
Review the task XML script and the variables request. Check that the variables are one of known names.
BFGDM0061E
An internal error has occurred. An unknown persistable object has been detected. Eye catcher was <insert_0>.
Severity
20 : Error
Explanation
This exception is unexpected. The cause is not immediately known.
Response
If the problem persists, see problem determination information in the product documentation.
BFGDM0062E
An internal error has occurred. An attempt has been made to use the monitor persistent store before it was initialised.
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.
BFGDM0065E
An internal error has occurred. IBM MQ reported an JMQI error 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.
BFGDM0066E
An internal error has occurred. IBM MQ reported an error 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.
BFGDM0067W
An internal error has occurred. IBM MQ reported an warning of <insert_0>.
Severity
10 : Warning
Explanation
This exception is unexpected. The cause is not immediately known.
Response
If the problem persists, see problem determination information in the product documentation.
BFGDM0068E
An internal error has occurred. IBM MQ reported an sync point error 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.
BFGDM0069I
Monitor <insert_0> has been stopped.
Severity
0 : Information
Explanation
A request to stop a monitor was been received and successfully executed.
Response
No action required.
BFGDM0070E
An internal error has occurred. Monitor has a WMQ Sync. point problem. 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.
BFGDM0071E
The monitor definition has more than one resource or trigger condition defined.
Severity
20 : Error
Explanation
The supplied monitor definition has been rejected as it contains more than one resource or trigger condition defined.
Response
Review the supplied monitor definition XML and ensure that a maximum of one resource or trigger condition has been defined and then resubmit.
BFGDM0072E
The source agent "<insert_0>" of the transfer is different to the resource monitor agent "<insert_1>".
Severity
20 : Error
Explanation
Any transfer task started by a resource monitor must use the resource monitor agent as the transfer source agent.
Response
Review the supplied monitor definition XML and ensure the source agent matches the resource monitor agent.
BFGDM0073E
The task XML generated by a monitor user exit has failed to parse with the following exception : <insert_0>
Severity
20 : Error
Explanation
A monitor user exit has modified the XML script for a monitor task to be executed and the updated script has failed to parse.
Response
Review the additional information in the monitor transfer log message for details of the user exits that were run and the script that was generated. Make any required changes to the monitor exits, rebuild them and place the .jar file in the appropriate user exits directory. Then restart the MQMFT agent.
BFGDM0074E
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.
BFGDM0075E
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.
BFGDM0076E
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.
BFGDM0077E
Resource monitor has a satisfied trigger, but was cancelled by a user exit.
Severity
20 : Error
Explanation
The resource monitor has found a satisfactory trigger match but was prevented from performing the task action by a user exit cancelling this trigger.
Response
No action required
BFGDM0078E
Root directory of <insert_1> for monitor <insert_0> is not available.
Severity
20 : Error
Explanation
The resource monitor was not able to scan for trigger matches as the root directory for the resource is not available.
Response
Review the root directory for the monitors resource and check to see if it is present and accessible by the resource monitor.
BFGDM0079E
An internal error has occurred. IBM MQ reported an error 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.
BFGDM0080W
An internal error has occurred. IBM MQ reported a warning of <insert_0>.
Severity
10 : Warning
Explanation
This exception is unexpected. The cause is not immediately known.
Response
If the problem persists, see problem determination information in the product documentation.
BFGDM0081E
An internal error has occurred. An unsupported internal message has been 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.
BFGDM0082E
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.
BFGDM0083E
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.
BFGDM0084E
The resource monitor generated a transfer request which has an invalid recipient. The recipient agent of <insert_0> with queue manger of <insert_1> has reported reason code of <insert_2>
Severity
20 : Error
Explanation
The resource monitor attempted to submit a transfer request, but delivery could not be completed for the given reason code.
Response
Check that recipient agent and assoicated queue manager names are correct.
BFGDM0085E
The queue manager "<insert_1>" of the source agent "<insert_0>" for the transfer must be the same as the queue manager for the resource monitor "<insert_2>"
Severity
20 : Error
Explanation
Any transfer task started by a resource monitor must use the same resource monitor queue manager as the transfer source queue manager.
Response
Review the supplied monitor definition XML and ensure the source queue manger matches the resource monitor queue manager.
BFGDM0086E
User (<insert_0>) has requested the creation of a resource monitor 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 create resource monitors.
Response
Determine if the specified user should be able to create resource monitors. If the user should be able to carry out this action, 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 create resource monitors inform the specified user that they are not authorized to perform the action and should stop trying to create resource monitors.
BFGDM0087E
User (<insert_0>) has requested the deletion of a resource monitor 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 resource monitor. The resource monitor has not been deleted.
Response
Determine if the specified user should be able to delete resource monitors. If the user should be able to carry out this action, 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 delete resource monitors inform the specified user that they are not authorized to perform the action and should stop trying to delete resource monitors.
BFGDM0088E
User (<insert_0>) has requested the deletion of a resource monitor 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 resource monitor. The resource monitor has not been deleted.
Response
Determine if the specified user should be able to delete resource monitors. If the user should be able to carry out this action, 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 delete resource monitors inform the specified user that they are not authorized to perform the action and should stop trying to delete resource monitors.
BFGDM0089W
An attempt was made to load resource monitor <insert_0> on an agent that does not support resource monitoring. The resource monitor has not been loaded.
Severity
10 : Warning
Explanation
Resource monitors are not supported on protocol bridge or Web Gateway MQMFT agents.
Response
No user action is required. However the monitor should be deleted to prevent this warning from being produced in the future.
BFGDM0090E
An attempt was made to create resource monitor <insert_0> on an agent that does not support resource monitoring. The resource monitor has not been created.
Severity
20 : Error
Explanation
Resource monitors are not supported on protocol bridge or Web Gateway MQMFT agents.
Response
Create the resource monitor on an agent that supports resource monitors, such as a standard MQMFT agent.
BFGDM0091E
An attempt was made to create resource monitor <insert_0> but an I/O problem occurred - <insert_1>
Severity
20 : Error
Explanation
An I/O Exception occurred while attempting to create a resource monitor.
Response
Examine the reason for the I/O Exception and take the necessary corrective action. It maybe the case that the specified directory or files for monitoring are invalid or not accessible.
BFGDM0092E
Monitor resource <insert_0> has been asked to scan a denied path of <insert_1>
Severity
20 : Error
Explanation
The resource directory being monitored will not scan directories which have been listed as denied access.
Response
Review agent properties 'sandBoxRoot' and 'commandPath' and ensure they are not on the resource path of any monitors.
BFGDM0093E
An attempt to start monitor <insert_0> has failed.
Severity
20 : Error
Explanation
A request to start a monitor could not be completed as an error condition was detected during the startup of the monitor.
Response
Review the associated error message and correct as necessary.
BFGDM0094E
The monitor <insert_0> has failed because the monitor resource queue <insert_1> is in use.
Severity
20 : Error
Explanation
The monitor resource queue is already open with options that are not compatible with the IBM MQ Managed File Transfer agent opening the queue for input shared access.
Response
Ensure that other applications open the resource queue with compatible open options.
BFGDM0095E
The monitor <insert_0> has failed because the monitor resource queue <insert_1> does not exist.
Severity
20 : Error
Explanation
The monitor resource queue does not exist on the monitor queue manager.
Response
Ensure that the resource queue has been specified correctly and exists on the monitor queue manager.
BFGDM0096E
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.
BFGDM0097E
An internal error has occurred. The xpath expression is invalid (reason: <insert_0>)
Severity
20 : Error
Explanation
This exception is unexpected. The cause is not immediately known.
Response
If the problem persists, see problem determination information in the product documentation.
BFGDM0098E
''<insert_0>'' is not a valid regular expression.
Severity
20 : Error
Explanation
The regular expression pattern, specifies as part of a request to create a resource monitor, is not a valid regular expression.
Response
Correct the pattern so that it is a valid regular expression and resubmit the request to create the resource monitor.
BFGDM0099E
No transfer item specified in the monitor XML for a monitor with a batch size greater than one.
Severity
20 : Error
Explanation
A resource monitor has been created that specified a batch size greater than one but does not contain a transfer item in the monitor XML. To submit multiple resource triggers in a single resource monitor action, the associated monitor XML must contain at least one transfer item definition.
Response
Correct the monitor definition by specifying a maximum batch size of one or using a monitor XML that contains at least one transfer item.
BFGDM0100E
The number of times that the monitor task has been re-tried for groupId: ''<insert_0>'' on queue: ''<insert_1>'' has exceeded the value specified by the agent property monitorGroupRetryLimit.
Severity
20 : Error
Explanation
The monitor has triggered on a complete group of messages on the queue but the backout count on the first message has exceeded the value of the monitorGroupRetryLimit. This indicates that there have already been several unsuccessful attempts to transfer this group of messages. The task will not be executed again.
Response
Check the transfer log for reason for the transfer tasks failing and correct the problem. Stop and restart the IBM MQ Managed File Transfer agent.
BFGDM0101E
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.
BFGDM0102E
An attempt to start monitor <insert_0> has failed. The reason is: <insert_1>
Severity
20 : Error
Explanation
A request to start a monitor could not be completed as an error condition was detected during the startup of the monitor.
Response
Review the error message and correct as necessary.
BFGDM0103E
The new monitor definition for monitor <insert_0> could not be updated. Caused by <insert_1>.
Severity
20 : Error
Explanation
An attempt was made to update an existing monitor definition with a new set of configuration details.
Response
BFGDM0104E
Queue operations have not been enabled by the monitor agent. The queue monitor has not been started.
Severity
20 : Error
Explanation
The agent property enableQueueInputOutput must be set to "true" for queue monitors to be started.
Response
Set the agent property enableQueueInputOutput to "true" in the agent.properties file. Then restart the monitor agent.
BFGDM0105W
The number of trigger failures for monitor <insert_0> has exceeded the maximum threshold. Further reporting has been disabled.
Severity
10 : Warning
Explanation
The maximum number of trigger failure publications as defined by the 'monitorSilenceOnTriggerFailure' agent property has been exceeded.
Response
Check the previously-published trigger failure messages for the reason for the failures and make any appropriate changes.
BFGDM0106W
The number of monitor FFDCs for monitor <insert_0> has exceeded the maximum threshold. The monitor has been stopped.
Severity
10 : Warning
Explanation
The maximum number of monitor FFDC publications as defined by the 'monitorStopOnInternalFailure' agent property has been exceeded.
Response
Contact the IBM support center for further assistance.
BFGDM0107W
The number of tasks generated by monitor <insert_0> during a polling interval has exceeded twice the value of the maxSourceTransfers agent property and the agent property monitorMaxResourcesInPoll is set to its default value of -1.
Severity
10 : Warning
Explanation
The number of tasks generated by this monitor may be sufficient to overload the agent. The number of tasks generated can be limited by setting the monitorMaxResourcesInPoll agent property to a positive integer value. Currently it is set to -1 which means that the number of tasks that can be generated is unlimited.
Response
For guidance on setting the monitorMaxResourcesInPoll agent property, and other properties and parameters related to resource monitors, refer to the product documentation online at: http://publib.boulder.ibm.com/infocenter/wmqfte/v7r0/.
BFGDM0108E
The monitor <insert_0> has failed because of an IBM MQ exception while accessing resource queue <insert_1>. The exception message is <insert_2>.
Severity
20 : Error
Explanation
The monitor failed with the exception indicated while trying to monitor the specified resource queue. This is most likely caused by a configuration problem.
Response
Check the exception message to determine the cause of the error.
BFGDM0109E
An expected JMQI exception occurred when analysing the command queue''s properties on Queue manager <insert_0>. Exception was: <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.
BFGDM0110W
No resource monitor can start as the agent command queue does not have Set Identity Context enabled.
Severity
10 : Warning
Explanation
For a resource monitor to generate transfer requests it must be able to set the identity context on for the requests it generates. The command queue configuration is not authorized for Set Identity Context.
Response
Enable set identity context on the agent's command queue and restart the agent before any resource monitors are created.
BFGDM0111E
The agent cannot be started as the resource monitor does not have authorization to enable Set Identity Context on the agent command queue.
Severity
20 : Error
Explanation
For a resource monitor to generate transfer requests it must be able to set the identity context on for the requests it generates. The command queue configuration is not authorised for Set Identity Context.
Response
Enable Set Identity Context on the agent command queue before restarting the agent.
BFGDM0112W
Last reported failure for <insert_0> for reason <insert_1>
Severity
10 : Warning
Explanation
The resource monitor has failed to trigger correctly following either a user or an environmental problem. This was the last report for this condition and further reports will be suppressed.
Response
Review the reported condition, investigate and correct as necessary. If the monitor is stopped then restart it.
BFGDM0113W
Trigger failure for <insert_0> for reason <insert_1>
Severity
10 : Warning
Explanation
The resource monitor has failed to trigger correctly following either a user or an environmental problem.
Response
Review the reported exception, investigate and correct as necessary. The monitor is still running but may terminate if the problem persists.
BFGDM0114E
Internal error: attempted to read triggered file path from metadata but is not present for monitor ''<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.
BFGDM0115E
Monitor ''<insert_0>'' attempted to read the contents of triggered file ''<insert_1>'' but failed due to ''<insert_2>''.
Severity
20 : Error
Explanation
A resource monitor configured for trigger content detected a new file but was unable to read is contents. The contents of the file have been ignored and the monitor will not re-trigger until the file has been updated.
Response
Review the named trigger file and ensure the associated agent for this resource monitor has permission and can read its contains.
BFGDM0116E
Monitor ''<insert_0>'' configured for trigger content with regular expression ''<insert_4>'' attempted to parse file ''<insert_1>'' but failed on line ''<insert_2>'' with contents ''<insert_3>''
Severity
20 : Error
Explanation
A resource monitor configured for trigger content failed to parse an entry in a triggered file. The contents of the file have been ignored and the monitor will not re-trigger until the file has been updated.
Response
Review the content parsing regular expression and the contents of the named triggered file and correct either before retrying.
BFGDM0117E
Monitor ''<insert_0>'' configured for trigger content with regular expression ''<insert_4>'' parse file ''<insert_1>'' has detected the incorrect number of capture groups of ''<insert_5>'' on line ''<insert_2>'' with contents ''<insert_3>''
Severity
20 : Error
Explanation
A resource monitor configured for trigger content has a regular expression that has returned the incorrect number of capture groups (expected number is 1 or 2). The contents of the file have been ignore and the monitor will not re-trigger until the file has been updated.
Response
Review the content parsing regular expression for the monitor and correct so that the expression it will only return 1 or 2 capture groups before retrying.
BFGDM0118E
Internal error: Monitor ''<insert_0>'' with type ''<insert_1>''has been configured for trigger content which is not supported.
Severity
20 : Error
Explanation
This exception is unexpected. The cause is not immediately known.
Response
If the problem persists, see problem determination information in the product documentation.
BFGDM0119E
Internal error: Could not determine the monitor type of monitor ''<insert_0>'' as it has no associated resource class.
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.
BFGDM0120E
Internal error: Could not determine the monitor type of monitor ''<insert_0>'' with resource class ''<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.
BFGDM0121W
The number of trigger failures for monitor <insert_0> has exceeded the maximum threshold. The monitor has been stopped.
Severity
10 : Warning
Explanation
The maximum number of trigger failure publications as defined by the 'monitorSilenceOnTriggerFailure' agent property has been exceeded. To prevent further reporting the monitor has been stopped.
Response
Check the previously-published trigger failure messages for the reason for the failures and make any appropriate changes before restarting the monitor.
BFGDM9999E
<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.