An insufficient number of arguments has been passed to the IBM MQ Managed File Transfer process controller.
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.
BFGPC0002W
Argument <insert_0> not specified, IBM MQ Managed File Transfer process controller log output is defaulting to the current working directory.
Severity
10 : Warning
Explanation
The IBM MQ Managed File Transfer process controller outputs event and trace log information to files in the specified log directory. When this directory has not been specified the current working directory is used.
Response
None.
BFGPC0003I
IBM MQ Managed File Transfer process controller started. Log files located at: <insert_0>.
Severity
0 : Information
Explanation
Indicates that the IBM MQ Managed File Transfer process controller has started.
Response
None.
BFGPC0004I
IBM MQ Managed File Transfer process controller ended with exit code <insert_0>.
Severity
0 : Information
Explanation
Indicates that the IBM MQ Managed File Transfer process controller has ended.
Response
None.
BFGPC0005E
The value supplied for the ''<insert_0>'' IBM MQ Managed File Transfer process controller option is outside the range of valid numerical values for this option. The range is from <insert_1> to <insert_2>.
Severity
20 : Error
Explanation
The value supplied for the specified option is outside the specified range of acceptable values. As a result, the IBM MQ Managed File Transfer process controller cannot be run.
Response
Restart the IBM MQ Managed File Transfer process controller with a valid value for this option. If IBM MQ Managed File Transfer process controller was not invoked directly then contact the IBM MQ Managed File Transfer product support team for assistance.
BFGPC0006E
The value supplied for the ''<insert_0>'' IBM MQ Managed File Transfer process controller command line option is not a valid numerical value.
Severity
20 : Error
Explanation
The value supplied for the specified IBM MQ Managed File Transfer process controller command line option is not a valid numerical value. As a result, the command cannot be issued.
Response
Restart the IBM MQ Managed File Transfer process controller with a numerical value for the specified option. If IBM MQ Managed File Transfer process controller was not invoked directly then contact the IBM MQ Managed File Transfer product support team for assistance.
BFGPC0007I
IBM MQ Managed File Transfer process controller with process identifier <insert_0> started <insert_1> with process identifier <insert_2>.
Severity
0 : Information
Explanation
Indicates that the IBM MQ Managed File Transfer process controller has started an application. The process identifiers for both the process controller and application are included in the message to help with their association.
Response
None.
BFGPC0008E
Another instance of the IBM MQ Managed File Transfer process controller is already running.
Severity
20 : Error
Explanation
Another instance of the IBM MQ Managed File Transfer process controller is already running. Only a single instance of any given IBM MQ Managed File Transfer process controller can run at one time. A second instance of the IBM MQ Managed File Transfer process controller has not been started.
Response
No action required.
BFGPC0009E
Failed to create directory <insert_0> for log files.
Severity
20 : Error
Explanation
The directory path could not be created because either a regular file with the same name already exists or the application has insufficient access rights to create the directory.
Response
Check that the specified log directory is correct and that there is sufficient authority for the application to create the directory. If the problem persists, contact the IBM MQ Managed File Transfer product support team for assistance.
BFGPC0010E
Message <insert_0> received after the listener for the IBM MQ Managed File Transfer process controller client had been shutdown.
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.
BFGPC0011E
Message <insert_0> received before the IBM MQ Managed File Transfer process controller''s associated application had been started.
Severity
20 : Error
Explanation
The message cannot be processed because the IBM MQ Managed File Transfer process controller's associated application has not been started yet.
Response
Retry the command. If the problem persists, contact the IBM MQ Managed File Transfer product support team for assistance.
BFGPC0012E
No Windows service name specified.
Severity
20 : Error
Explanation
The command requires a Windows service name to be specified.
Response
Run the command again specifying a Windows service name.
BFGPC0013E
The specified Windows service name is too long.
Severity
20 : Error
Explanation
The specified Windows service name is longer than the maximum permitted length of 256 characters.
Response
Run the command again specifying a Windows service name of less than or equal to 256 characters.
BFGPC0014E
The specified Windows service display name is too long.
Severity
20 : Error
Explanation
The specified Windows service display name is longer than the maximum permitted length of 256 characters.
Response
Run the command again specifying a Windows service display name of less than or equal to 256 characters.
BFGPC0015E
A call to the Windows GetModuleFileName function failed. Reason: <insert_0>
Severity
20 : Error
Explanation
The system was unable to obtain the module file name for the reason given.
Response
Check the reason for the failure and take action as appropriate. If the problem persists, contact the IBM MQ Managed File Transfer product support team for assistance.
BFGPC0016E
Failed to access the Windows service control manager. Reason: <insert_0>
Severity
20 : Error
Explanation
The Windows service cannot be installed because the Windows service control manager cannot be accessed.
Response
Check the reason for the failure and take action as appropriate. If the problem persists, contact the IBM MQ Managed File Transfer product support team for assistance.
BFGPC0017E
Failed to create Windows service named <insert_0>. Reason: <insert_1>
Severity
20 : Error
Explanation
The Windows service cannot be created for the reason given.
Response
Check the reason for the failure and take action as appropriate. If the problem persists, contact the IBM MQ Managed File Transfer product support team for assistance.
BFGPC0018W
Failed to set the description for Windows service named <insert_0>. Reason <insert_1>
Severity
10 : Warning
Explanation
The system could not set the description for the Windows service. The Windows service has been successfully installed, but the description has not been set.
Response
Check the reason for the failure and take action as appropriate. If the problem persists, contact the IBM MQ Managed File Transfer product support team for assistance.
BFGPC0019I
Installed Windows service <insert_0>.
Severity
0 : Information
Explanation
The Windows service has been successfully installed.
Response
No action.
BFGPC0020W
The stop was successful, but the application had to be forcibly shut down due to error: <insert_0>
Severity
10 : Warning
Explanation
The application has been forcibly shut down. Normally an application is requested to shut down in a controlled manner, but this was not possible due to the reason given. This in general should not cause any problems.
Response
No action. If the problem persists, contact the IBM MQ Managed File Transfer product support team for assistance.
BFGPC0021W
Use the default value of <insert_1> for property <insert_0> because the property has been defined in error. Reason: <insert_2>
Severity
10 : Warning
Explanation
The property was defined in the properties files but it was assigned a value that is invalid. Because of this a default value for the property is being used.
Response
Correct the value for the property in the properties file and restart.
BFGPC0022I
Process has ended with return code <insert_0>.
Severity
0 : Information
Explanation
The controlled process has ended due to a request for it to end.
Response
None.
BFGPC0023E
Process has ended with return code <insert_0>.
Severity
20 : Error
Explanation
The controlled process has ended with an error code indicating that it cannot be recovered. This type of error is typically due to a configuration error or fatal application startup error.
Response
Examine the log files for details of the problem and correct as necessary.
BFGPC0024W
Process has ended with return code <insert_0> and will be restarted to attempt to recover the problem.
Severity
10 : Warning
Explanation
The controlled process has ended with an error code indicating that it may be possible to recover. This type of error is typically due to an unexpected error during normal running operation.
Response
None. Normally this type of error can be tolerated, but if the problem persists, contact the IBM MQ Managed File Transfer product support team for assistance.
BFGPC0025E
Process has ended with return code <insert_0> after <insert_1> attempts to recover in <insert_2> seconds.
Severity
20 : Error
Explanation
The controlled process has ended again after a number of attempts to recover from the failure. This indicates a more serious type of error that needs to be investigated.
Response
If the problem persists, contact the IBM MQ Managed File Transfer product support team for assistance.
BFGPC0026W
Process has ended with return code <insert_0> after <insert_1> attempts to recover in <insert_2> seconds. The process will be restarted in <insert_3> seconds to attempt to recover the problem.
Severity
10 : Warning
Explanation
The controlled process has ended again after a number of attempts to recover from the failure. The process controller will restart the process again after a delay.
Response
If the problem persists, contact the IBM MQ Managed File Transfer product support team for assistance.
BFGPC0027W
Process has ended with return code <insert_0> and will be restarted to attempt to recover the problem.
Severity
10 : Warning
Explanation
The controlled process has ended with an error code indicating that it may be possible to recover. This type of error is typically due to an unexpected error during normal running operation.
Response
None, normally this type of error can be tolerated. But if the problem persists, contact the IBM MQ Managed File Transfer product support team for assistance.
BFGPC0028W
Process has ended with return code <insert_0> because the queue manager is unavailable. The process will be restarted when the queue manager becomes available.
Severity
10 : Warning
Explanation
The controlled process has ended because the queue manager is no longer available. When the queue manager becomes available again the process controller will restart the process.
Response
If the queue manager was deliberately stopped, then no action is required. Otherwise the queue manager should be investigated to discover the cause of the problem.
BFGPC0029W
The process controller was unable to connect to the application''s queue manager ''<insert_0>''. The MQ reason code returned is : <insert_1>. The process controller will try to connect to the queue manager again after <insert_2> seconds. The queue manager retry period is specified by the application property ''<insert_3>''
Severity
10 : Warning
Explanation
The process controller must be able to connect to the application's queue manager before the application is started. When unable to connect to the queue manager, the process controller will try to connect again after a period determined by the application's queue manager retry interval property.
Response
None
BFGPC0030W
The process controller was unable to connect to the application''s queue manager because the queue manager ''<insert_0>'' property has not been set in the application''s property file. The process controller will try to connect to the queue manager again after <insert_1> seconds. The queue manager retry period is specified by the application property ''<insert_2>''
Severity
10 : Warning
Explanation
The process controller must be able to connect to the application's queue manager before the application is started. When no queue manager property is defined the process controller will read the application's property file again after a period determined by the application's queue manager retry interval property.
Response
None
BFGPC0031E
An uncaught exception has been thrown and the process controller will be ended. The exception is: <insert_0>
Severity
20 : Error
Explanation
This exception is unexpected. The cause is not immediately known.
Response
If the problem persists, see problem determination information in the product documentation.
BFGPC0032E
The process controller has terminated unexpectedly.
Severity
20 : Error
Explanation
The process controller that is monitoring the application process has terminated unexpectedly. The application process will terminate.
Response
If the termination of the process controller was unexpected then contact the IBM MQ Managed File Transfer product support team for assistance.
BFGPC0033I
A client mode connection is required to queue manager ''<insert_0>''. The process controller will no longer wait for the queue manager.
Severity
0 : Information
Explanation
The process controller previously had problems while attempting to establish a bindings transport mode connection to the queue manager. The configuration properties have been changed and consequently a client mode connection to the queue manager is now required. The process controller does not attempt a client mode connection to the queue manager and will start the agent immediately. If the agent has problems establishing the client mode connection to the queue manager, the agent will report an error message to its output log file and retry at regular intervals.
Response
No action is required.
BFGPC0034I
The process controller has established a bindings transport mode connection to queue manager ''<insert_0>''. The application will be started.
Severity
0 : Information
Explanation
The process controller previously had problems while attempting to establish a bindings transport mode connection to the queue manager. A successful connection has now been established either because the queue manager is now available or because the configuration properties have been changed to specify a different queue manager that is available.
Response
No action is required.
BFGPC0035I
IBM MQ Managed File Transfer process controller ended due to its associated agent stopping in a controlled manner.
Severity
0 : Information
Explanation
Indicates that the IBM MQ Managed File Transfer process controller has ended as a result of its associated agent being stopped in a controlled manner.
Response
No action is required.
BFGPC0036E
IBM MQ Managed File Transfer process controller ended after the maximum number of agent restarts were attempted without success.
Severity
20 : Error
Explanation
Indicates that the IBM MQ Managed File Transfer process controller has made repeated attempts to restart its associated agent. The number of restarts attempted has reached the configured maximum number of attempts as defined by the maxRestartCount agent property. No further restarts will be attempted and the process controller will stop.
Response
Consult the agent and process controller logs to determine what is causing the failure.
BFGPC0037E
IBM MQ Managed File Transfer process controller ended due to a failure when starting the IPC service.
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.
BFGPC0038W
A problem occurred when the agent attempted to start its process controller at startup. The agent will continue without a process controller. Exception: <insert_0>, Return code: <insert_1>
Severity
10 : Warning
Explanation
The agent had a problem when trying to start its process controller during agent startup. The agent will continue to run without a process controller.
Response
Review the agent and process controller logs to determine the cause of the failure. One possible reason for the process controller failing to start is insufficient background slots being available for the new process to run in. If this appears to be the case we can either free up a slot to allow the process controller to run or set the useProcessController agent property to false to run without a process controller and stop these warnings.
BFGPC0039W
A problem occurred when the agent attempted to connect to its process controller at startup. The agent will continue without a process controller.
Severity
10 : Warning
Explanation
The agent had a problem when trying to connect to its process controller during agent startup. The agent will continue to run without a process controller.
Response
Review the agent and process controller logs to determine the cause of the failure. One possible reason for the process controller failing to start is insufficient background slots being available for the new process to run in. If this appears to be the case we can either free up a slot to allow the process controller to run or set the useProcessController agent property to false to run without a process controller and stop these warnings.
BFGPC0040I
An attempt to restart the agent background process has failed and will be tried again. Exception: <insert_0>, Return code: <insert_1>
Severity
0 : Information
Explanation
The process controller detected that the agent was not responsive and attempted a restart of the agent to resolve the problem. This restart failed so it will be tried again at a future time.
Response
No action is required.
BFGPC0041I
The agent background process was already stopped when an attempt was made to stop it after it became unresponsive. A restart will be attempted.
Severity
0 : Information
Explanation
The process controller detected that the agent was not responsive and attempted to stop it before attempting a restart. This stop failed as the agent background process was already stopped. The agent background process will be restarted.
Response
No action is required.
BFGPC0042I
An attempt to stop the agent background process after it became unresponsive has failed. Exception: <insert_0>, Return code: <insert_1>
Severity
0 : Information
Explanation
The process controller detected that the agent was not responsive and attempted to stop it before attempting a restart. This stop failed. The reason for the failure may be related to the reason the agent has become unresponsive. Restart processing will continue in an attempt to bring the agent back to normal operation.
Response
No action is required.
BFGPC0043I
The agent background process has become unresponsive so it will be stopped by the process controller.
Severity
0 : Information
Explanation
The agents process controller has detected that the agent has become unresponsive so it will attempt to stop the agent background process. This is the first step in restarting the agent background process in an attempt to return it back to normal operation.
Response
No action is required.
BFGPC0044I
The agent background process is being restarted by the process controller.
Severity
0 : Information
Explanation
After previously stopping the agent background process due to it becoming unresponsive, the process controller will now attempt to restart it. This should bring the agent back up and return it to normal operation.
Response
No action is required.
BFGPC0045E
The agent background process could not be found by the process controller. NAME=<insert_0> PARM=<insert_1>
Severity
20 : Error
Explanation
When the process controller attempted to stop or restart the agent background process it could not be found. This may be because the background process defined for the agent does not have matching parameters to those used by the process controller. The values being used by the process controller are supplied to allow the user to ensure the agent background process definition matches exactly.
Response
Redefine your agent background process to match the format being used by the process controller and restart the agent.
BFGPC0046E
IBM MQ Managed File Transfer process controller ended as it could not find its associated agent background process.
Severity
20 : Error
Explanation
The process controller cannot continue without access to the associated agent background process so it stops.
Response
Review previous messages to determine why the agent background process could not be found by the process controller.
BFGPC0047E
IBM MQ Managed File Transfer process controller is already running. An exclusive lock cannot be acquired on file: <insert_0>. This process controller instance cannot continue and will end.
Severity
20 : Error
Explanation
This process controller has detected that another instance of the process controller is running. Only one instance of a process controller can run at any one time, so this process controller will end. The mechanism used to detect that another instance of the process controller is running is an exclusive lock on the named file.
Response
No action is required.
BFGPC0048E
IBM MQ Managed File Transfer process controller cannot open file ''<insert_0>'' and will end. The file could not be opened because of: <insert_1>.
Severity
20 : Error
Explanation
The process controller could not open the specified file, for the specified reason. The process controllers must be able to access this file to start successfully. The process controller will now end.
Response
Use the information in the message to investigate why the process controller cannot open the specified file. If possible, resolve the problem and run the command to start the agent associated with the process controller again. If necessary, contact the IBM support center if you need further assistance to resolve this problem.
BFGPC0049I
IBM MQ Managed File Transfer process controller ended because the IBM 4690 system is not acting as a file server.
Severity
0 : Information
Explanation
The process controller cannot continue when the IBM 4690 system is not acting a file server.
Response
No action is required.
BFGPC0050E
The expected background process definition for this agent could not be found. The agent will be stopped. NAME=<insert_0> PARM=<insert_1>
Severity
20 : Error
Explanation
When an agent attempts to start it checks for the presence of the background process that is expected by the agent's process controller. The agent failed to find the expected background process so it does not start as continuing would mean that the process controller will fail if it attempts to restart the agent. This may be because the background process defined for the agent does not have parameters that match those used by the process controller. The parameter values being used by the process controller are supplied to allow the user to ensure the agent background process definition matches these parameter values.
Response
Redefine your agent background process to match the format being used by the process controller then restart the agent.
BFGPC0051I
The process controller was unable to establish a bindings mode connection to queue manager ''<insert_0>'' because of MQ reason code 2035 (not authorized). The application will be started and should be able to successfully connect to the queue manager if the appropriate authorization credentials have been configured.
Severity
0 : Information
Explanation
The process controller was unable to establish a bindings mode connection to the queue manager because additional authorization credential information was required. The process controller currently implements a basic check only for a queue manager connection, which does not include supplying authorization credential information. As a result the process controller starts the application, on the assumption that the queue manager will be available and the process controller will be able to connect to the queue manager successfully .
Response
No action is required.
BFGPC0052W
Process has ended with return code <insert_0> because the queue manager is unavailable. The process will be restarted when the queue manager becomes available.
Severity
10 : Warning
Explanation
The controlled process has ended because the queue manager is no longer available. When the queue manager becomes available again the process controller will restart the process.
Response
If the queue manager was deliberately stopped, then no action is required. Otherwise the queue manager should be investigated to discover the cause of the problem.
BFGPC0053E
Unable to obtain exclusive access on a process controller lock file. The error reported was: ''<insert_0>''. Check if another instance of the IBM MQ Managed File Transfer process controller is already running.
Severity
20 : Error
Explanation
Another instance of the IBM MQ Managed File Transfer process controller may already be running. Only a single instance of any given IBM MQ Managed File Transfer process controller can run at one time. A second instance of the IBM MQ Managed File Transfer process controller has not been started.
Response
No action required.
BFGPC9999E
<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.