BFGCR0001 - BFGCR9999
- BFGCR0001E
- An internal error has occurred.
- Severity
- 20 : Error
- Explanation
- This exception is unexpected. The cause is not immediately known.
- Response
- This exception is unexpected. The cause is not immediately known.
- BFGCR0002I
- Execution of command ''<insert_0>'' has been ended by a cancel transfer request.
- Severity
- 0 : Information
- Explanation
- The specified command ended because it was cancelled by a cancel transfer request.
- Response
- No action is required.
- BFGCR0003E
- A request has been made for the agent to call the command ''<insert_0>''. The agent''s command path ''<insert_1>'' does not define a path to this command. Only commands whose path is on the agent''s command path can be run.
- Severity
- 20 : Error
- Explanation
- The agent will only run commands whose path is defined by the agent's commandPath property. The specified command cannot be located on the command path of the agent and hence the command will not be run.
- Response
- Check that a valid command name was specified when the transfer request was issued. Ensure that the command is available on the command path of the agent. Update the agent's commandPath property to contain the full path to the required command. For more information, refer to the IBM MQ information in IBM Documentation.
- BFGCR0004E
- Execution of command ''<insert_0>'' has ended because it output more data than the maximum permitted amount of <insert_1> bytes.
- Severity
- 20 : Error
- Explanation
- The specified command ended because it output more data than the agent is configured to permit a command to output.
- Response
- Modify the command being executed so that the amount of data it outputs is within the maximum permitted by the agent. Alternatively, configure the agent to permit a larger amount of command generated output.
- BFGCR0005E
- A request has been made for the agent to call the JCL script ''<insert_0>''. The agent''s command path ''<insert_1>'' does not define a path to this JCL script. Only JCL scripts whose path is on the agent''s command path can be run.
- Severity
- 20 : Error
- Explanation
- The agent will only run JCL scripts whose path is defined by the agent's commandPath property. The specified JCL script cannot be located on the command path of the agent and hence the JCL script will not be run.
- Response
- Check that a valid JCL script name was specified when the transfer request was issued. Ensure that the JCL script is available on the command path of the agent. Update the agent's commandPath property to contain the full path to the required JCL script, when defined in USS space, or a prefix that matches the first part of the JCL script data set name. For more information, refer to the IBM MQ information in IBM Documentation.
- BFGCR0006E
- Cannot read JCL script ''<insert_0>'' due to <insert_1>
- Severity
- 20 : Error
- Explanation
- The specified JCL script exists but can not be read. The command will not be run.
- Response
- Check that the JCL script is accessible when the transfer request was issued.
- BFGCR0007E
- Failed to submit job for JCL script ''<insert_0>''. Return code is <insert_1>. JobName is ''<insert_2>'', JobId is ''<insert_3>''
- Severity
- 20 : Error
- Explanation
- The system failed to submit a job for the JCL script. The jobName or jobId is missing. The JCL script is most likely invalid or does not specify a job. The script will not be run.
- Response
- Check the system event log for more information.
- BFGCR0008E
- Invalid job for JCL script ''<insert_0>'' - job card not found.
- Severity
- 20 : Error
- Explanation
- The system failed to submit a job for the JCL script. The command will not be run.
- Response
- Check the system event log for more information.
- BFGCR0009E
- Invalid job for JCL script ''<insert_0>'' - submit() did not return a job id
- Severity
- 20 : Error
- Explanation
- The system failed to submit a job for the JCL script. The command will not be run.
- Response
- Check the system event log for more information.
- BFGCR0010E
- An internal error has occurred. Java executable cannot be found at: <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.
- BFGCR0011E
- The specified Ant script ''<insert_0>'' is not present in the command path ''<insert_1>'' of the agent.
- Severity
- 20 : Error
- Explanation
- The specified Ant script cannot be located on the command path of the agent. The Ant script will not be run.
- Response
- Check that a valid script name was specified when the transfer request was issued. Ensure that the script is available on the command path of the agent.
- BFGCR0012E
- A request has been made for the agent to call the command ''<insert_0>''. The agent''s commandPath property is not defined or empty. No commands can be run until their path is added to the agent''s commandPath.
- Severity
- 20 : Error
- Explanation
- The agent will only run commands whose path is defined by the agent's commandPath property. With this being empty no commands can be run by the agent.
- Response
- Update the agent properties to include a commandPath, containing the full path to the required commands. For more information, refer to the IBM MQ information in IBM Documentation.
- BFGCR0013E
- A request has been made for the agent to call the JCL script ''<insert_0>''. The agent''s commandPath property is not defined or empty. No JCL scripts can be run until their path is added to the agent''s commandPath.
- Severity
- 20 : Error
- Explanation
- The agent will only run JCL scripts whose path is defined by the agent's commandPath property. With this being empty no JCL scripts can be run by the agent.
- Response
- Update the agent properties to include a commandPath, containing the full path to the required JCL script, when defined in USS space, or a prefix that matches the first part of the JCL script data set name. For more information, refer to the IBM MQ information in IBM Documentation.
- BFGCR0014E
- A request has been made for the agent to call the command or script ''<insert_0>''. The agent''s commandPath property only defines a path to a symbolic link for this command or script (first path found is: ''<insert_1>''). Only commands or scripts whose path is on the agent''s command path and are not a symbolic link can be run.
- Severity
- 20 : Error
- Explanation
- The agent will not run commands or scripts whose only reference on the agent's command path is a symbolic link.
- Response
- Check that a valid command or script name was specified when the transfer request was issued. Ensure the command or script is available on the command path of the agent and is not a symbolic link. Update the agent's commandPath property to contain the full path to the required command or script. For more information, refer to the IBM MQ information in IBM Documentation.
- BFGCR0015E
- Execution of command ''<insert_0>'' has been ended by a request to immediately shut down this agent.
- Severity
- 20 : Error
- Explanation
- The specified command ended because an operator requested to immediately shut down this agent.
- Response
- The command will be started again when the agent is restarted.
- BFGCR0016E
- Program calls are not supported on Connect:Direct bridge agents.
- Severity
- 20 : Error
- Explanation
- Connect:Direct bridge agents do not support program calls or transfers containing pre-source calls, pre-destination calls, post-source calls, or post-destination calls.
- Response
- Remove the program calls from the transfer request and try the transfer again.
- BFGCR0017E
- Ant program calls are not supported on Connect:Direct bridge agents.
- Severity
- 20 : Error
- Explanation
- Connect:Direct bridge agents do not support program calls or transfers containing pre-source calls, pre-destination calls, post-source calls, or post-destination calls.
- Response
- Remove the program calls from the transfer request and try the transfer again.
- BFGCR0018E
- JCL program calls are not supported on Connect:Direct bridge agents.
- Severity
- 20 : Error
- Explanation
- Connect:Direct bridge agents do not support program calls or transfers containing pre-source calls, pre-destination calls, post-source calls, or post-destination calls.
- Response
- Remove the program calls from the transfer request and try the transfer again.
- BFGCR0019E
- JCL scripts supported only for agents running on z/OS.
- Severity
- 20 : Error
- Explanation
- JCL scripts are a feature for the z/OS platform and cannot be run from other platforms.
- Response
- Remove the program calls from the transfer request and try the transfer again.
- BFGCR0020E
- Ant scripts are not supported for agents running on 4690.
- Severity
- 20 : Error
- Explanation
- Ant is not supported on the 4690 platform.
- Response
- Remove the program calls from the transfer request and try the transfer again.
- BFGCR0021E
- Command ''<insert_0>'' is invalid because it specifies multiple commands or redirects standard input or output.
- Severity
- 20 : Error
- Explanation
- Only a single command may be specified without redirecting standard input or output.
- Response
- Check that the command is specified correctly, any required exclamation point (!), greater than (>), or less than (<) characters must be prefixed with a double quotation (") character. Then retry the transfer.
- BFGCR0022E
- 4690 background application calls supported only for agents running on the 4690 platform.
- Severity
- 20 : Error
- Explanation
- 4690 background application calls are a feature for the 4690 platform and cannot be run from other platforms.
- Response
- Remove the program calls from the transfer request and retry the transfer.
- BFGCR0023E
- Failed to start background application for command ''<insert_0>''. return Code: <insert_1>. Reason: <insert_2>
- Severity
- 20 : Error
- Explanation
- The background application could not be started for the reason given.
- Response
- Examine the reason given for the failure and take the necessary action to resolve the problem. Then retry the transfer.
- BFGCR0024E
- Failed to start background application for command ''<insert_0>''. Reason: The command name is too long. The maximum permitted command name length is <insert_1> characters.
- Severity
- 20 : Error
- Explanation
- The background application could not be started because the command name was too long.
- Response
- Check that the command name is correct. Try moving the command to a different directory, with a shorter path. Note that the agent commandPath property will need to be updated to reference any new path, and the agent restarted. Then retry the transfer.
- BFGCR0025E
- Failed to start background application for command ''<insert_0>'' with parameters ''<insert_1>''. Reason: The total length of the command parameters is too long. The maximum permitted length is <insert_2> characters.
- Severity
- 20 : Error
- Explanation
- The background application could not be started because the total length of the command parameters is too long. The total length of the parameters is calculated as the length of a text string comprising of all the parameters with a single space character between each parameter.
- Response
- Check that the specified parameters are correct and try to reduce the length. Then retry the transfer.
- BFGCR9999E
- <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.