BFGCM0001 - BFGCM9999

BFGCM0000E: The source configuration directory "<insert_0>" specified in the -config parameter cannot be located.
Severity: 20 : Error
Explanation: The source configuration directory specified by the -config parameter is either invalid or incorrect and cannot be located.
Response: Review the value given in the parameter and ensure it is present and correct.

BFGCM0001E: The source configuration directory "<insert_0>" specified in the -config parameter cannot be located.
Severity: 20 : Error
Explanation: The source configuration directory specified by the -config parameter is either invalid or incorrect and cannot be located.
Response: Review the value given in the parameter and ensure it is present and correct.

BFGCM0110E: The source configuration directory "<insert_0>" specified in the -config parameter cannot be located.
Severity: 20 : Error
Explanation: The source configuration directory specified by the -config parameter is either invalid or incorrect and cannot be located.
Response: Review the value given in the parameter and ensure it is present and correct.

BFGCM0002E: The source configuration directory "<insert_0>" specified in the -config parameter cannot be read.
Severity: 20 : Error
Explanation: The source configuration directory specified in the -config parameter although present cannot be read.
Response: Review the permission settings of the specified source configuration directory, and ensure that this command is executed with sufficient permissions to read the configuration.

BFGCM0003E: The source configuration directory "<insert_0>" specified in the -config parameter cannot be read.
Severity: 20 : Error
Explanation: The source configuration directory specified in the -config parameter although present cannot be read.
Response: Review the permission settings of the specified source configuration directory, and ensure that this command is executed with sufficient permissions to read the configuration.

BFGCM0111E: The source configuration directory "<insert_0>" specified in the -config parameter cannot be read.
Severity: 20 : Error
Explanation: The source configuration directory specified in the -config parameter although present cannot be read.
Response: Review the permission settings of the specified source configuration directory, and ensure that this command is executed with sufficient permissions to read the configuration.

BFGCM0004E: The source configuration directory "<insert_0>" specified in the -config parameter is the same as the IBM MQ Managed File Transfer configuration directory.
Severity: 20 : Error
Explanation: The source configuration directory parameter has specified the same configuration directory as the destination. The fteMigrateAgent tools does not support migration within the same configuration.
Response: Review the given source configuration directory and correct as necessary. The fteMigrateAgent tools does not support migration within the same configuration.

BFGCM0005E: The source configuration directory "<insert_0>" specified in the -config parameter is the same as the IBM MQ Managed File Transfer configuration directory.
Severity: 20 : Error
Explanation: The source configuration directory parameter has specified the same configuration directory as the destination. The fteMigrateLogger tools does not support migration within the same configuration.
Response: Review the given source configuration directory and correct as necessary. The fteMigrateLogger tools does not support migration within the same configuration.

BFGCM0112E: The source configuration directory "<insert_0>" specified in the -config parameter is the same as the IBM MQ Managed File Transfer configuration directory.
Severity: 20 : Error
Explanation: The source configuration directory parameter has specified the same configuration directory as the destination. The fteMigrateConfigurationOption tools does not support migration within the same configuration.
Response: Review the given source configuration directory and correct as necessary. The fteMigrateLogger tools does not support migration within the same configuration.

BFGCM0006E: The source configuration "<insert_0>" is missing the wmqfte.properties file which defines the default coordination. Use the -p parameter to specify the property set that the agent is a member of.
Severity: 20 : Error
Explanation: The required default property set file wmqfte.properties is missing from the source configuration. This is required to determine the default property set for use in this command.
Response: Repeat the command with the -p parameter to specify the required property set. Review recent changes to the source configuration and if necessary recover missing files from a backup.

BFGCM0007E: The source configuration "<insert_0>" is missing the wmqfte.properties file which defines the default coordination. Use the -p parameter to specify the property set that the logger is a member of.
Severity: 20 : Error
Explanation: The mandatory default property set file wmqfte.properties is missing from the source configuration. This is required to determine the default property set for use in this command.
Response: Repeat the command with the -p parameter to specify the required property set. Review recent changes to the source configuration and if necessary recover missing files from a backup.

BFGCM0113E: The source configuration "<insert_0>" is missing the wmqfte.properties file which defines the default coordination. Use the -p parameter to specify the property set that the logger is a member of.
Severity: 20 : Error
Explanation: The mandatory default property set file wmqfte.properties is missing from the source configuration. This is required to determine the default property set for use in this command.
Response: Repeat the command with the -p parameter to specify the required property set. Review recent changes to the source configuration and if necessary recover missing files from a backup.

BFGCM0008E: The wmqfte.properties file in the source configuration "<insert_0>" is present but cannot be read by fteMigrateAgent.
Severity: 20 : Error
Explanation: The required file wmqfte.properties which defines the default property set from fteMigrateAgent has been located, but cannot be read by this command.
Response: Review the permissions on the wmqfte.properties and ensure fteMigrateAgent has sufficient permission to read the file.

BFGCM0009E: The wmqfte.properties file in the source configuration "<insert_0>" is present but cannot be read by fteMigrateLogger
Severity: 20 : Error
Explanation: The required file wmqfte.properties which defines the default property set from fteMigrateLogger has been located, but cannot be read by this command.
Response: Review the permissions on the wmqfte.properties and ensure fteMigrateLogger has sufficient permission to read the file.

BFGCM0114E: The wmqfte.properties file in the source configuration "<insert_0>" is present but cannot be read by fteMigrateLogger
Severity: 20 : Error
Explanation: The required file wmqfte.properties which defines the default property set from fteMigrateConfigurationOptions has been located, but cannot be read by this command.
Response: Review the permissions on the wmqfte.properties and ensure fteMigrateLogger has sufficient permission to read the file.

BFGCM0010E: The wmqfte.properties file in the source configuration "<insert_0>" has been located, but could not be read due to <insert_1>.
Severity: 20 : Error
Explanation: An attempt to read the wmqfte.properties file in the source configuration failed with an IO exception. This property file is required to determine the default property set to use in the fteMigrateAgent command.
Response: Review the reported exception which may reflect on a hardware or network access problem or that the file is locked by another program.

BFGCM0011E: The wmqfte.properties file in the source configuration "<insert_0>" has been located, but could not be read due to <insert_1>.
Severity: 20 : Error
Explanation: An attempt to read the wmqfte.properties file in the source configuration failed with an IO exception. This property file is required to determine the default property set to use in the fteMigrateLogger command.
Response: Review the reported exception which may reflect on a hardware or network access problem or that the file is locked by another program.

BFGCM0115E: The wmqfte.properties file in the source configuration "<insert_0>" has been located, but could not be read due to <insert_1>.
Severity: 20 : Error
Explanation: An attempt to read the wmqfte.properties file in the source configuration failed with an IO exception. This property file is required to determine the default property set to use in the fteMigrateConfigurationOptions command.
Response: Review the reported exception which may reflect on a hardware or network access problem or that the file is locked by another program.

BFGCM0012E: The wmqfte.properties file in the source configuration "<insert_0>" is missing the required property "defaultProperties". Use the -p parameter to define a specific property set to use in this command.
Severity: 20 : Error
Explanation: The "defaultProperties" value is required to determine the default property set to use in the fteMigrateAgent command. This value is missing from the wmqfte.properties in the given source configuration.
Response: Review recent changes to the source configuration and recover as necessary from a backup. Alternatively, use the -p to define a specific property set to use in this command.

BFGCM0013E: The wmqfte.properties file in the source configuration "<insert_0>" is missing the required property "defaultProperties". Use the -p parameter to define a specific property set to use in this command.
Severity: 20 : Error
Explanation: The "defaultProperties" value is required to determine the default property set to use in the fteMigrateLogger command. This value is missing from the wmqfte.properties in the given source configuration.
Response: Review recent changes to the source configuration and recover as necessary from a backup. Alternatively, use the -p to define a specific property set to use in this command.

BFGCM0116E: The wmqfte.properties file in the source configuration "<insert_0>" is missing the required property "defaultProperties". Use the -p parameter to define a specific property set to use in this command.
Severity: 20 : Error
Explanation: The "defaultProperties" value is required to determine the default property set to use in the fteMigrateConfigurationOptions command. This value is missing from the wmqfte.properties in the given source configuration.
Response: Review recent changes to the source configuration and recover as necessary from a backup. Alternatively, use the -p to define a specific property set to use in this command.

BFGCM0014E: The property file "<insert_0>" as determined from the specified property set (-p) is missing.
Severity: 20 : Error
Explanation: The coordination.properties for the property set specified by the -p is missing. This is a required property set for the fteMigrateAgent to complete successfully.
Response: Review the given -p parameter. If correct review recent changes to the source configuration and recover from a backup if necessary.

BFGCM0015E: The property file "<insert_0>" as determined from the specified property set (-p) is missing.
Severity: 20 : Error
Explanation: The coordination.properties for the property set specified by the -p is missing. This is a required property set for the fteMigrateLogger to complete successfully.
Response: Review the given -p parameter. If correct review recent changes to the source configuration and recover from a backup if necessary.

BFGCM0117E: The property file "<insert_0>" as determined from the -configurationOptions parameter is missing.
Severity: 20 : Error
Explanation: The coordination.properties for the property set specified by the -p is missing. This is a required property set for the fteMigrateConfigurationOption to complete successfully.
Response: Review the given -p parameter. If correct review recent changes to the source configuration and recover from a backup if necessary.

BFGCM0016E: The property file "<insert_0>" as determined from the specified property set (-p) cannot be read.
Severity: 20 : Error
Explanation: The coordination.properties for the property set specified by the -p cannot be read, due to file access permissions. This is a required property set for the fteMigrateLogger to complete successfully.
Response: Review the file permissions and ensure the user has the correct permissions to access the file.

BFGCM0017E: The property file "<insert_0>" as determined from the specified property set (-p) cannot be read.
Severity: 20 : Error
Explanation: The coordination.properties for the property set specified by the -p cannot be read, due to file access permissions. This is a required property set for the fteMigrateLogger to complete successfully.
Response: Review the file permissions and ensure the user has the correct permissions to access the file.

BFGCM0118E: The property file "<insert_0>" as determined from the specified property set (-p) cannot be read.
Severity: 20 : Error
Explanation: The coordination.properties for the property set specified by the -p cannot be read, due to file access permissions. This is a required property set for the fteMigrateConfigurationOptions to complete successfully.
Response: Review the file permissions and ensure the user has the correct permissions to access the file.

BFGCM0018E: The property file "<insert_0>" as determined from the specified property set (-p) reported an exception whilst reading the contents. The reported exception is <insert_1>
Severity: 20 : Error
Explanation: An attempt to read the contents of a coordination.properties file failed with an exception. This may indicate a hardware or network problem, or that the file is locked by a different program.
Response: Review the contents of the reported exception and resolve as necessary.

BFGCM0019E: The property file "<insert_0>" as determined from the specified property set (-p) reported an exception whilst reading the contents. The reported exception is <insert_1>
Severity: 20 : Error
Explanation: An attempt to read the contents of a coordination.properties file failed with an exception. This may indicate a hardware or network problem, or that the file is locked by a different program.
Response: Review the contents of the reported exception and resolve as necessary.

BFGCM0119E: The property file "<insert_0>" as determined from the specified property set (-p) reported an exception whilst reading the contents. The reported exception is <insert_1>
Severity: 20 : Error
Explanation: An attempt to read the contents of a coordination.properties file failed with an exception. This may indicate a hardware or network problem, or that the file is locked by a different program.
Response: Review the contents of the reported exception and resolve as necessary.

BFGCM0020E: The property file "<insert_0>" as determined from the specified property set (-p) is missing.
Severity: 20 : Error
Explanation: The command.properties for the property set specified by the -p is missing. This is a required property set for the fteMigrateAgent to complete successfully.
Response: Review the specified -p parameter and if correct review recent changes to the source configuration and recover from a backup as necessary.

BFGCM0021E: The property file "<insert_0>" as determined from the specified property set (-p) is missing.
Severity: 20 : Error
Explanation: The command.properties for the property set specified by the -p is missing. This is a required property set for the fteMigrateLogger to complete successfully.
Response: Review the specified -p parameter and if correct review recent changes to the source configuration and recover from a backup as necessary.

BFGCM0120E: The property file "<insert_0>" as determined from the specified property set (-p) is missing.
Severity: 20 : Error
Explanation: The command.properties for the property set specified by the -p is missing. This is a required property set for the fteMigrateConfigurationOptions to complete successfully.
Response: Review the specified -p parameter and if correct review recent changes to the source configuration and recover from a backup as necessary.

BFGCM0022E: The property file "<insert_0>" as determined from the specified property set (-p) cannot be read.
Severity: 20 : Error
Explanation: The command.properties for the property set specified by the -p cannot be read, due to file access permissions. This is a required property set for the fteMigrateAgent to complete successfully.
Response: Review the file permissions and ensure the user has the correct permissions to access the file.

BFGCM0023E: The property file "<insert_0>" as determined from the specified property set (-p) cannot be read.
Severity: 20 : Error
Explanation: The command.properties for the property set specified by the -p cannot be read, due to file access permissions. This is a required property set for the fteMigrateLogger to complete successfully.
Response: Review the file permissions and ensure the user has the correct permissions to access the file.

BFGCM0121E: The property file "<insert_0>" as determined from the specified property set (-p) cannot be read.
Severity: 20 : Error
Explanation: The command.properties for the property set specified by the -p cannot be read, due to file access permissions. This is a required property set for the fteMigrateConfigurationOptions to complete successfully.
Response: Review the file permissions and ensure the user has the correct permissions to access the file.

BFGCM0024E: The property file "<insert_0>" as determined from the specified property set (-p) reported an exception whilst reading the contents. The reported exception is <insert_1>
Severity: 20 : Error
Explanation: An attempt to read the contents of a command.properties file failed with an exception. This may indicate a hardware or network problem, or that the file is locked by a different program.
Response: Review the contents of the reported exception and resolve as necessary.

BFGCM0025E: The property file "<insert_0>" as determined from the specified property set (-p) reported an exception whilst reading the contents. The reported exception is <insert_1>
Severity: 20 : Error
Explanation: An attempt to read the contents of a command.properties file failed with an exception. This may indicate a hardware or network problem, or that the file is locked by a different program.
Response: Review the contents of the reported exception and resolve as necessary.

BFGCM0122E: The property file "<insert_0>" as determined from the specified property set (-p) reported an exception whilst reading the contents. The reported exception is <insert_1>
Severity: 20 : Error
Explanation: An attempt to read the contents of a command.properties file failed with an exception. This may indicate a hardware or network problem, or that the file is locked by a different program.
Response: Review the contents of the reported exception and resolve as necessary.

BFGCM0026E: The required property file <insert_0> is missing from the IBM MQ Managed File Transfer configuration, although the property set is present.
Severity: 20 : Error
Explanation: The property set is present in the IBM MQ Managed File Transfer configuration. but the coordination.properties file is missing.
Response: Review the property set in the IBM MQ Managed File Transfer configuration and the result of recent commands executed, then recover from a backup as necessary.

BFGCM0027E: The required property file <insert_0> is missing from the IBM MQ Managed File Transfer configuration, although the property set is present.
Severity: 20 : Error
Explanation: The property set is present in the IBM MQ Managed File Transfer configuration. but the coordination.properties file is missing.
Response: Review the property set in the IBM MQ Managed File Transfer configuration and the result of recent commands executed, then recover from a backup as necessary.

BFGCM0123E: The required property file <insert_0> is missing from the IBM MQ Managed File Transfer configuration, although the property set is present.
Severity: 20 : Error
Explanation: The property set is present in the IBM MQ Managed File Transfer configuration. but the coordination.properties file is missing.
Response: Review the property set in the IBM MQ Managed File Transfer configuration and the result of recent commands executed, then recover from a backup as necessary.

BFGCM0028E: The required property file <insert_0> is present but cannot be read by fteMigrateAgent command from the IBM MQ Managed File Transfer configuration.
Severity: 20 : Error
Explanation: The fteMigrateAgent command does not have the correct permission to read the coordination.properties in the IBM MQ Managed File Transfer configuration.
Response: Review the permission on the named file and ensure the fteMigrateAgent command has sufficient permission to read the file.

BFGCM0029E: The required property file <insert_0> is present but cannot be read by fteMigrateLogger command from the IBM MQ Managed File Transfer configuration.
Severity: 20 : Error
Explanation: The fteMigrateLogger command does not have the correct permission to read the coordination.properties in the IBM MQ Managed File Transfer configuration.
Response: Review the permission on the named file and ensure the fteMigrateLogger command has sufficient permission to read the file.

BFGCM0124E: The required property file <insert_0> is present but cannot be read by fteMigrateConfigurationOptions command from the IBM MQ Managed File Transfer configuration.
Severity: 20 : Error
Explanation: The fteMigrateConfigurationOptions command does not have the correct permission to read the coordination.properties in the IBM MQ Managed File Transfer configuration.
Response: Review the permission on the named file and ensure the fteMigrateConfigurationOptions command has sufficient permission to read the file.

BFGCM0030E: Attempt to read file <insert_0> failed with exception <insert_1>
Severity: 20 : Error
Explanation: The fteMigrateAgent attempted to read coordination.properties from the IBM MQ Managed File Transfer configuration, but failed. This may indicate a hardware or network problem, or that the file is locked by a different program.
Response: Review the contents of the reported exception and resolve as necessary.

BFGCM0031E: Attempt to read file <insert_0> failed with exception <insert_1>
Severity: 20 : Error
Explanation: The fteMigrateLogger attempted to read coordination.properties from the IBM MQ Managed File Transfer configuration, but failed. This may indicate a hardware or network problem, or that the file is locked by a different program.
Response: Review the contents of the reported exception and resolve as necessary.

BFGCM0032E: The required property file <insert_0> is missing from the IBM MQ Managed File Transfer configuration, although the property set is present.
Severity: 20 : Error
Explanation: The property set is present in the IBM MQ Managed File Transfer configuration, but the command.properties file is missing.
Response: Review the property set in the IBM MQ Managed File Transfer configuration and the result of recent commands executed, then recover from a backup as necessary.

BFGCM0033E: The required property file <insert_0> is missing from the IBM MQ Managed File Transfer configuration, although the property set is present.
Severity: 20 : Error
Explanation: The property set is present in the IBM MQ Managed File Transfer configuration, but the command.properties file is missing.
Response: Review the property set in the IBM MQ Managed File Transfer configuration and the result of recent commands executed, then recover from a backup as necessary.

BFGCM0125E: The required property file <insert_0> is missing from the IBM MQ Managed File Transfer configuration, although the property set is present.
Severity: 20 : Error
Explanation: The property set is present in the IBM MQ Managed File Transfer configuration, but the command.properties file is missing.
Response: Review the property set in the IBM MQ Managed File Transfer configuration and the result of recent commands executed, then recover from a backup as necessary.

BFGCM0034E: The required property file <insert_0> is present but cannot be read by fteMigrateAgent from the IBM MQ Managed File Transfer configuration.
Severity: 20 : Error
Explanation: The fteMigrateAgent command does not have the correct permission to read the command.properties in the IBM MQ Managed File Transfer configuration.
Response: Review the permission on the named file and ensure the fteMigrateAgent command has sufficient permission to read the file.

BFGCM0035E: The required property file <insert_0> is present but cannot be read by fteMigrateLogger from the IBM MQ Managed File Transfer configuration.
Severity: 20 : Error
Explanation: The fteMigrateLogger command does not have the correct permission to read the command.properties in the IBM MQ Managed File Transfer configuration.
Response: Review the permission on the named file and ensure the fteMigrateLogger command has sufficient permission to read the file.

BFGCM0126E: The required property file <insert_0> is present but cannot be read by fteMigrateConfigurationOptions from the IBM MQ Managed File Transfer configuration.
Severity: 20 : Error
Explanation: The fteMigrateConfigurationOptions command does not have the correct permission to read the command.properties in the IBM MQ Managed File Transfer configuration.
Response: Review the permission on the named file and ensure the fteMigrateConfigurationOptions command has sufficient permission to read the file.

BFGCM0036E: Attempt to read file <insert_0> failed with exception <insert_1>
Severity: 20 : Error
Explanation: The fteMigrateAgent attempted to read command.properties from the IBM MQ Managed File Transfer configuration, but failed. This may indicate a hardware or network problem, or that the file is locked by a different program.
Response: Review the contents of the reported exception and resolve as necessary.

BFGCM0037E: Attempt to read file <insert_0> failed with exception <insert_1>.
Severity: 20 : Error
Explanation: The fteMigrateLogger attempted to read command.properties from the IBM MQ Managed File Transfer configuration, but failed. This may indicate a hardware or network problem, or that the file is locked by a different program.
Response: Review the contents of the reported exception and resolve as necessary.

BFGCM0127E: Attempt to read file <insert_0> failed with exception <insert_1>.
Severity: 20 : Error
Explanation: The fteMigrateLogger attempted to read command.properties from the IBM MQ Managed File Transfer configuration, but failed. This may indicate a hardware or network problem, or that the file is locked by a different program.
Response: Review the contents of the reported exception and resolve as necessary.

BFGCM0038E: The required property file <insert_0> is missing from the given configuration to migrate, although the property set is present.
Severity: 20 : Error
Explanation: The property set is present in the given configuration. but the coordination.properties file is missing.
Response: Review the property set in the given configuration and the result of recent commands executed, then recover from a backup as necessary.

BFGCM0039E: The required property file <insert_0> is missing from the given configuration to migrate, although the property set is present.
Severity: 20 : Error
Explanation: The property set is present in the given configuration. but the coordination.properties file is missing.
Response: Review the property set in the given configuration and the result of recent commands executed, then recover from a backup as necessary.

BFGCM0128E: The required property file <insert_0> is missing from the given configuration to migrate, although the property set is present.
Severity: 20 : Error
Explanation: The property set is present in the given configuration. but the coordination.properties file is missing.
Response: Review the property set in the given configuration and the result of recent commands executed, then recover from a backup as necessary.

BFGCM0040E: The required property file <insert_0> is present but cannot be read by fteMigrateAgent from the IBM MQ Managed File Transfer configuration.
Severity: 20 : Error
Explanation: The fteMigrateAgent command does not have the correct permission to read the coordination.properties in the IBM MQ Managed File Transfer configuration.
Response: Review the permission on the named file and ensure the fteMigrateAgent command has sufficient permission to read the file.

BFGCM0041E: The required property file <insert_0> is present but cannot be read by fteMigrateLogger from the IBM MQ Managed File Transfer configuration.
Severity: 20 : Error
Explanation: The fteMigrateLogger command does not have the correct permission to read the coordination.properties in the IBM MQ Managed File Transfer configuration.
Response: Review the permission on the named file and ensure the fteMigrateLogger command has sufficient permission to read the file.

BFGCM0129E: The required property file <insert_0> is present but cannot be read by fteMigrateLogger from the IBM MQ Managed File Transfer configuration.
Severity: 20 : Error
Explanation: The fteMigrateConfigurationOptions command does not have the correct permission to read the coordination.properties in the IBM MQ Managed File Transfer configuration.
Response: Review the permission on the named file and ensure the fteMigrateConfigurationOptions command has sufficient permission to read the file.

BFGCM0042E: Attempt to read file <insert_0> failed with exception <insert_1>
Severity: 20 : Error
Explanation: The fteMigrateAgent attempted to read coordination.properties from the IBM MQ Managed File Transfer configuration, but failed. This may indicate a hardware or network problem, or that the file is locked by a different program.
Response: Review the contents of the reported exception and resolve as necessary.

BFGCM0043E: Attempt to read file <insert_0> failed with exception <insert_1>
Severity: 20 : Error
Explanation: The fteMigrateLogger attempted to read coordination.properties from the IBM MQ Managed File Transfer configuration, but failed. This may indicate a hardware or network problem, or that the file is locked by a different program.
Response: Review the contents of the reported exception and resolve as necessary.

BFGCM0130E: Attempt to read file <insert_0> failed with exception <insert_1>
Severity: 20 : Error
Explanation: The fteMigrateConfigurationOptions attempted to read coordination.properties from the IBM MQ Managed File Transfer configuration, but failed. This may indicate a hardware or network problem, or that the file is locked by a different program.
Response: Review the contents of the reported exception and resolve as necessary.

BFGCM0044E: The required property file <insert_0> is missing from the IBM MQ Managed File Transfer configuration, although the property set is present..
Severity: 20 : Error
Explanation: The property set is present in the IBM MQ Managed File Transfer configuration, but the coordination.properties file is missing.
Response: Review the property set in the IBM MQ Managed File Transfer configuration and the result of recent commands executed, then recover from a backup as necessary.

BFGCM0045E: The required property file <insert_0> is missing from the IBM MQ Managed File Transfer configuration, although the property set is present..
Severity: 20 : Error
Explanation: The property set is present in the IBM MQ Managed File Transfer configuration, but the command.properties file is missing.
Response: Review the property set in the IBM MQ Managed File Transfer configuration and the result of recent commands executed, then recover from a backup as necessary.

BFGCM0131E: The required property file <insert_0> is missing from the IBM MQ Managed File Transfer configuration, although the property set is present..
Severity: 20 : Error
Explanation: The property set is present in the IBM MQ Managed File Transfer configuration, but the command.properties file is missing.
Response: Review the property set in the IBM MQ Managed File Transfer configuration and the result of recent commands executed, then recover from a backup as necessary.

BFGCM0046E: The required property file <insert_0> is present but cannot be read by fteMigrateAgent from the IBM MQ Managed File Transfer configuration.
Severity: 20 : Error
Explanation: The fteMigrateAgent command does not have the correct permission to read the command.properties in the IBM MQ Managed File Transfer configuration.
Response: Review the permission on the named file and ensure the fteMigrateAgent command has sufficient permission to read the file.

BFGCM0047E: The required property file <insert_0> is present but cannot be read by fteMigrateLogger from the IBM MQ Managed File Transfer configuration.
Severity: 20 : Error
Explanation: The fteMigrateLogger command does not have the correct permission to read the command.properties in the IBM MQ Managed File Transfer configuration.
Response: Review the permission on the named file and ensure the fteMigrateLogger command has sufficient permission to read the file.

BFGCM0132E: The required property file <insert_0> is present but cannot be read by fteMigrateLogger from the IBM MQ Managed File Transfer configuration.
Severity: 20 : Error
Explanation: The fteMigrateConfigurationOptions command does not have the correct permission to read the command.properties in the IBM MQ Managed File Transfer configuration.
Response: Review the permission on the named file and ensure the fteMigrateConfigurationOptions command has sufficient permission to read the file.

BFGCM0048E: Attempt to read file <insert_0> failed with exception <insert_1>
Severity: 20 : Error
Explanation: The fteMigrateAgent attempted to read command.properties from the IBM MQ Managed File Transfer configuration, but failed. This may indicate a hardware or network problem, or that the file is locked by a different program.
Response: Review the contents of the reported exception and resolve as necessary.

BFGCM0049E: Attempt to read file <insert_0> failed with exception <insert_1>
Severity: 20 : Error
Explanation: The fteMigrateLogger attempted to read command.properties from the IBM MQ Managed File Transfer configuration, but failed. This may indicate a hardware or network problem, or that the file is locked by a different program.
Response: Review the contents of the reported exception and resolve as necessary.

BFGCM0133E: Attempt to read file <insert_0> failed with exception <insert_1>
Severity: 20 : Error
Explanation: The fteMigrateConfigurationOptions attempted to read command.properties from the IBM MQ Managed File Transfer configuration, but failed. This may indicate a hardware or network problem, or that the file is locked by a different program.
Response: Review the contents of the reported exception and resolve as necessary.

BFGCM0050E: The agent to be migrated is missing a properties file. It was expected to be located at "<insert_0>".
Severity: 20 : Error
Explanation: The named agent to be migrated is missing a required properties file. This file defines the agent and without it the command cannot successfully complete.
Response: Review the result of any recently executed commands and recover from a backup as necessary.

BFGCM0051E: The logger to be migrated is missing a properties file. It was expected to be located at "<insert_0>".
Severity: 20 : Error
Explanation: The logger to be migrated is missing a required properties file. This file defines the logger and without it the command cannot successfully complete.
Response: Review the result of any recently executed commands and recover from a backup as necessary.

BFGCM0134E: The logger to be migrated is missing a properties file. It was expected to be located at "<insert_0>".
Severity: 20 : Error
Explanation: The logger to be migrated is missing a required properties file. This file defines the logger and without it the command cannot successfully complete.
Response: Review the result of any recently executed commands and recover from a backup as necessary.

BFGCM0052E: This command is unable to read the agent.properties file of the agent to be migrated. The attempted to read was "<insert_0>"
Severity: 20 : Error
Explanation: The fteMigrateAgent command does not have the correct permission to read the agent.properties file of the agent to be migrated.
Response: Review the permission on the named file and ensure the fteMigrateAgent command has sufficient permission to read the file.

BFGCM0053E: This command is unable to read the logger.properties file of the logger to be migrated. The attempted to read was "<insert_0>"
Severity: 20 : Error
Explanation: The fteMigrateLogger command does not have the correct permission to read the logger.properties file of the logger to be migrated.
Response: Review the permission on the named file and ensure the fteMigrateLogger command has sufficient permission to read the file.

BFGCM0135E: This command is unable to read the logger.properties file of the logger to be migrated. The attempted to read was "<insert_0>"
Severity: 20 : Error
Explanation: The fteMigrateConfigurationOptions command does not have the correct permission to read the logger.properties file of the logger to be migrated.
Response: Review the permission on the named file and ensure the fteMigrateConfigurationOptions command has sufficient permission to read the file.

BFGCM0054E: Attempt to read file <insert_0> failed with exception <insert_1>.
Severity: 20 : Error
Explanation: The fteMigrateAgent command attempted to read agent.properties of the agent to be migrated, but failed. This may indicate a hardware or network problem, or that the file is locked by a different program.
Response: Review the contents of the reported exception and resolve as necessary.

BFGCM0055E: Attempt to read file <insert_0> failed with exception <insert_1>.
Severity: 20 : Error
Explanation: The fteMigrateLogger command attempted to read logger.properties of the logger to be migrated, but failed. This may indicate a hardware or network problem, or that the file is locked by a different program.
Response: Review the contents of the reported exception and resolve as necessary.

BFGCM0136E: Attempt to read file <insert_0> failed with exception <insert_1>.
Severity: 20 : Error
Explanation: The fteMigrateLogger command attempted to read logger.properties of the logger to be migrated, but failed. This may indicate a hardware or network problem, or that the file is locked by a different program.
Response: Review the contents of the reported exception and resolve as necessary.

BFGCM0056E: The agent to be migrated cannot be located in the source configuration. The expected location is "<insert_0>".
Severity: 20 : Error
Explanation: The named agent is expected to be located under the relevant property set. However, no directory could be located using the agent name.
Response: Review the agent parameter and correct as necessary.

BFGCM0057E: The logger to be migrated cannot be located in the source configuration. The expected location is "<insert_0>".
Severity: 20 : Error
Explanation: The named logger is expected to be located under the relevant property set. However, no directory could be located using the logger name.
Response: Review the logger parameter and correct as necessary.

BFGCM0137E: The logger to be migrated cannot be located in the source configuration. The expected location is "<insert_0>".
Severity: 20 : Error
Explanation: The named logger is expected to be located under the relevant property set. However, no directory could be located using the logger name.
Response: Review the logger parameter and correct as necessary.

BFGCM0058W: The properties of the agent to be migrated have one or more configuration errors. Review and correct these errors or use the -f (force) option to ignore these errors.
Severity: 10 : Warning
Explanation: This is confirming that there are one or more errors detected within the agent configuration to be migrated.
Response: Review errors reported about the configuration and correct as necessary or use the -f (force) parameter to ignore these errors.

BFGCM0059W: The properties of the logger to be migrated have one or more configuration errors. Review and correct these errors or use the -f (force) option to ignore these errors.
Severity: 10 : Warning
Explanation: This is confirming that there are one or more errors detected within the logger configuration to be migrated.
Response: Review errors reported about the configuration and correct as necessary or use the -f (force) parameter to ignore these errors.

BFGCM0138W: The properties of the logger to be migrated have one or more configuration errors. Review and correct these errors or use the -f (force) option to ignore these errors.
Severity: 10 : Warning
Explanation: This is confirming that there are one or more errors detected within the logger configuration to be migrated.
Response: Review errors reported about the configuration and correct as necessary or use the -f (force) parameter to ignore these errors.

BFGCM0060W: The agent "<insert_0>" to be migrated is already present in the IBM MQ Managed File Transfer configuration.
Severity: 10 : Warning
Explanation: Warning the named agent is already present in the IBM MQ Managed File Transfer configuration.
Response: Review configuration and use the -f (force) parameter to overwrite the agent configuration in IBM MQ Managed File Transfer.

BFGCM0061W: The logger "<insert_0>" to be migrated is already present in the IBM MQ Managed File Transfer configuration.
Severity: 10 : Warning
Explanation: Warning the named logger is already present in the IBM MQ Managed File Transfer configuration.
Response: Review configuration and use the -f (force) parameter to overwrite the logger configuration in IBM MQ Managed File Transfer.

BFGCM0139W: The logger "<insert_0>" to be migrated is already present in the IBM MQ Managed File Transfer configuration.
Severity: 10 : Warning
Explanation: Warning the named logger is already present in the IBM MQ Managed File Transfer configuration.
Response: Review configuration and use the -f (force) parameter to overwrite the logger configuration in IBM MQ Managed File Transfer.

BFGCM0062W: A directory path "<insert_0>" in the agent to be migrated has too many levels to be migrated.
Severity: 10 : Warning
Explanation: The named directory in the agent to be migrated has too many levels to be migrated which suggests that the structure may be incorrect.
Response: Review the named directory from the agent and recover from a backup as necessary.

BFGCM0063W: A directory path "<insert_0>" in the logger to be migrated has too many levels to be migrated.
Severity: 10 : Warning
Explanation: The named directory in the logger to be migrated has too many levels to be migrated which suggests that the structure may be incorrect.
Response: Review the named directory from the logger and recover from a backup as necessary.

BFGCM0140W: A directory path "<insert_0>" in the logger to be migrated has too many levels to be migrated.
Severity: 10 : Warning
Explanation: The named directory in the logger to be migrated has too many levels to be migrated which suggests that the structure may be incorrect.
Response: Review the named directory from the logger and recover from a backup as necessary.

BFGCM0064E: The source property set path "<insert_0>" is missing.
Severity: 20 : Error
Explanation: The property set is missing from the source configuration. This is required as it will contain the agent to be migrated.
Response: Review recent change to the source configuration and recover from a backup as necessary.

BFGCM0065E: The source property set path "<insert_0>" is missing.
Severity: 20 : Error
Explanation: The property set is missing from the source configuration. This is required as it will contain the logger to be migrated.
Response: Review recent change to the source configuration and recover from a backup as necessary.

BFGCM0141E: The source property set path "<insert_0>" is missing.
Severity: 20 : Error
Explanation: The property set is missing from the source configuration. This is required as it will contain the logger to be migrated.
Response: Review recent change to the source configuration and recover from a backup as necessary.

BFGCM0066E: The create MQSC script file cannot be located and was expected at "<insert_0>". The script is required for the migration to be completed.
Severity: 20 : Error
Explanation: The MQSC script to configure the agent queue manager is expected to be located in the agent home directory but is missing.
Response: Review recent changes to the agent home directory and recover from a backup as necessary.

BFGCM0067E: The create MQSC script file cannot be located and was expected at "<insert_0>". The script is required for the migration to be completed.
Severity: 20 : Error
Explanation: The MQSC script to configure the logger queue manager is expected to be located in the logger home directory but is missing.
Response: Review recent changes to the logger home directory and recover from a backup as necessary.

BFGCM0142E: The create MQSC script file cannot be located and was expected at "<insert_0>". The script is required for the migration to be completed.
Severity: 20 : Error
Explanation: The MQSC script to configure the logger queue manager is expected to be located in the logger home directory but is missing.
Response: Review recent changes to the logger home directory and recover from a backup as necessary.

BFGCM0068E: The create MQSC script file bas been located and "<insert_0>", but this command is unable to read it.
Severity: 20 : Error
Explanation: The name file is present in the home directory of the agent to be migrated, but fteMigrateAgent cannot read its contents.
Response: Review the permissions on the named file and ensure the fteMigrateAgent command has the correct permissions to read the contents.

BFGCM0069E: The create MQSC script file bas been located and "<insert_0>", but this command is unable to read it.
Severity: 20 : Error
Explanation: The name file is present in the home directory of the logger to be migrated, but fteMigrateLogger cannot read its contents.
Response: Review the permissions on the named file and ensure the fteMigrateLogger command has the correct permissions to read the contents.

BFGCM0143E: The create MQSC script file bas been located and "<insert_0>", but this command is unable to read it.
Severity: 20 : Error
Explanation: The name file is present in the home directory of the logger to be migrated, but fteMigrateLogger cannot read its contents.
Response: Review the permissions on the named file and ensure the fteMigrateConfigurationOptions command has the correct permissions to read the contents

BFGCM0070E: The delete MQSC script file cannot be located and was expected at "<insert_0>". The script is required for the migration to be completed.
Severity: 20 : Error
Explanation: The MQSC script to unconfigure the agent queue manager is expected to be located in the agent home directory but is missing.
Response: Review recent changes to the agent home directory and recover from a backup as necessary.

BFGCM0071E: The delete MQSC script file cannot be located and was expected at "<insert_0>". The script is required for the migration to be completed.
Severity: 20 : Error
Explanation: The MQSC script to unconfigure the logger queue manager is expected to be located in the logger home directory but is missing.
Response: Review recent changes to the logger home directory and recover from a backup as necessary.

BFGCM0072E: The delete MQSC script file bas been located and "<insert_0>", but this command is unable to read it.
Severity: 20 : Error
Explanation: The named file is present in the home directory of the agent to be migrated, but fteMigrateAgent cannot read its contents.
Response: Review the permissions on the named file and ensure the fteMigrateAgent command has the correct permissions to read the contents.

BFGCM0073E: The delete MQSC script file bas been located and "<insert_0>", but this command is unable to read it.
Severity: 20 : Error
Explanation: The named file is present in the home directory of the logger to be migrated, but fteMigrateLogger cannot read its contents.
Response: Review the permissions on The named file and ensure the fteMigrateLogger command has the correct permissions to read the contents.

BFGCM0074W: The Connect:Direct property file "<insert_0>" could not be located and is required to migrate this agent.
Severity: 10 : Warning
Explanation: The agent to be migrated has been configured as a Connect:Direct bridge and the required named configuration could not be located.
Response: Review recent changes to the agent configuration and correct as necessary.

BFGCM0076E: The Connect:Direct property file "<insert_0>" although present could not be read by fteMigrateAgent. It is required to migrate this agent.
Severity: 20 : Error
Explanation: The agent to be migrated has been configured as a Connect:Direct bridge and the required named configuration could not read. To successfully perform the migration the named file also needs to be migrated.
Response: Review the permissions on the named file and ensure the fteMigrateAgent has the correct permission to access the file.

BFGCM0078W: The Protocol Bridge property file "<insert_0>" could not be located and is required to migrate this agent.
Severity: 10 : Warning
Explanation: The agent to be migrated has been configured as a protocol bridge and the required named configuration could not be located.
Response: Review recent changes to the agent configuration and correct as necessary.

BFGCM0080E: The protocol bridge property file "<insert_0>" although present could not be read by fteMigrateAgent. It is required to migrate this agent.
Severity: 20 : Error
Explanation: The agent to be migrated has been configured as a protocol bridge and the required named configuration could not be read. To successfully complete the migration the named file also needs to be migrated.
Response: Review the permissions on the named file and ensure the fteMigrateAgent has the correct permission to access the file.

BFGCM0082W: The sand box property file of the agent to be migrated cannot be located. It was expected to be at "<insert_0>"
Severity: 10 : Warning
Explanation: The user sand box for the named agent cannot be located and is required to complete the migration.
Response: Review recent changes to the configuration and recover from a backup as necessary.

BFGCM0084E: The sand box property file of the agent to be migrated has been located at "<insert_0>", but cannot be read by this command.
Severity: 20 : Error
Explanation: The fteMigrateAgent command cannot read the sand box property file of the agent to be migrated. This is a required part of the migration and therefore the command cannot complete successfully.
Response: Review the permissions of the named file and ensure the fteMigrateAgent command has the correct permissions to read the file.

BFGCM0086W: The "exit" directory of the agent to be migrated is missing, it was expected to be located at "<insert_0>"
Severity: 10 : Warning
Explanation: Each agent has an optional exit directory, it is missing for this agent.
Response: Review whether the directory should be present and if not use the -f (force) parameter to ignore this condition.

BFGCM0088E: The agent to be migrated has an existing directory at "<insert_0>", but this command cannot read the contents.
Severity: 20 : Error
Explanation: The exit directory for the agent to be migrated cannot be read by the fteMigrateAgent but is required for the migration to be successfully completed.
Response: Review the permissions of the exit directory and ensure the fteMigrateAgent command has the correct permissions to read the contents.

BFGCM0090E: The agent "<insert_0>" to be migrated is running. The agent must be stopped before migration can take place.
Severity: 20 : Error
Explanation: The agent lock file is present and locked by an existing running agent. The migration cannot be successfully completed if one or more files are in use by an existing agent.
Response: Issue an fteStopAgent command for the agent to be migrated and ensure it has successfully stopped before retrying this command.

BFGCM0091E: The logger "<insert_0>" to be migrated is running. The logger must be stopped before migration can take place.
Severity: 20 : Error
Explanation: The logger lock file is present and locked by an existing running logger. The migration cannot be successfully completed if one or more files are in use by an existing logger.
Response: Issue an fteStopLogger commend for the logger to be migrated and ensure it has successfully stopped before retrying this command.

BFGCM0092W: The property set of the agent to be migrated is already present in IBM MQ Managed File Transfer configuration and is different from the one located in the source configuration.\n Review differences and use the -f (force) parameter to ignore source property set differences. The differences in the coordination.properties are: <insert_0>
Severity: 10 : Warning
Explanation: The coordination.properties of the property set is present in both the source configuration as specified in the -config parameter and in the IBM MQ Managed File Transfer configuration. These two files have different values.
Response: If the value is correct in the IBM MQ Managed File Transfer configuration use the -f (force) parameter to ignore these differences.

BFGCM0093W: The property set of the logger to be migrated is already present in IBM MQ Managed File Transfer configuration and is different from the one located in the source configuration.\n Review differences and use the -f (force) parameter to ignore source property set differences. The differences in the coordination.properties are: <insert_0>
Severity: 10 : Warning
Explanation: The coordination.properties of the property set is present in both the source configuration as specified in the -config parameter and in the IBM MQ Managed File Transfer configuration. These two files have different values.
Response: If the value is correct in the IBM MQ Managed File Transfer configuration use the -f (force) parameter to ignore these differences.

BFGCM0144W: The property set of the configuration options to be migrated is already present in IBM MQ Managed File Transfer configuration and is different from the one located in the source configuration. Review differences and use the -f (force) parameter to ignore source property set differences. The differences in the coordination.properties are: <insert_0>
Severity: 10 : Warning
Explanation: The coordination.properties of the property set is present in both the source configuration as specified in the -config parameter and in the IBM MQ Managed File Transfer configuration. These two files have different values.
Response: If the value is correct in the IBM MQ Managed File Transfer configuration use the -f (force) parameter to ignore these differences.

BFGCM0094W: The property set of the command options to be migrated is already present in IBM MQ Managed File Transfer configuration and is different from the one located in the source configuration.\nReview differences and use the -f (force) parameter to ignore source property set differences. The differences in the command.properties are: <insert_0>
Severity: 10 : Warning
Explanation: The command.properties of the property set is present in both the source configuration as specified in the -config parameter and in the IBM MQ Managed File Transfer configuration. These two files have different values.
Response: If the value is correct in the IBM MQ Managed File Transfer configuration use the -f (force) parameter to ignore these differences.

BFGCM0095W: The property set of the logger to be migrated is already present in IBM MQ Managed File Transfer configuration and is different from the one located in the source configuration.\n Review differences and use the -f (force) parameter to ignore source property set differences. The differences in the command.properties are: <insert_0>
Severity: 10 : Warning
Explanation: The command.properties of the property set is present in both the source configuration as specified in the -config parameter and in the IBM MQ Managed File Transfer configuration. These two files have different values.
Response: If the value is correct in the IBM MQ Managed File Transfer configuration use the -f (force) parameter to ignore these differences.

BFGCM0098E: Internal error: no source coordination value has been defined.
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.

BFGCM0099E: Internal error: no source coordination value has been defined.
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.

BFGCM0145E: Internal error: no source coordination value has been defined.
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.

BFGCM0100E: User must be an IBM MQ Managed File Transfer administrator to run this command.
Severity: 20 : Error
Explanation: The command could not successfully complete because the user requires IBM MQ Managed File Transfer administrator rights.
Response: User needs to be an IBM MQ Managed File Transfer administrator to execute this command.

BFGCM0101E: User must be an IBM MQ Managed File Transfer administrator to run this command.
Severity: 20 : Error
Explanation: The command could not successfully complete because the user requires IBM MQ Managed File Transfer administrator rights.
Response: User needs to be an IBM MQ Managed File Transfer administrator to execute this command.

BFGCM0146E: User must be an IBM MQ Managed File Transfer administrator to run this command.
Severity: 20 : Error
Explanation: The command could not successfully complete because the user requires IBM MQ Managed File Transfer administrator rights.
Response: User needs to be an IBM MQ Managed File Transfer administrator to execute this command.

BFGCM0102E: Internal error: cannot locate the "dspmqver" command to discover MQ configuration. Product exception 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.

BFGCM0103E: Internal error: cannot locate the "dspmqver" command to discover MQ configuration. Product exception 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.

BFGCM0147E: Internal error: cannot locate the "dspmqver" command to discover MQ configuration. Product exception 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.

BFGCM0104E: The coordination MQSC script file cannot be located and was expected at "<insert_0>". The script is required for the migration to be completed.
Severity: 20 : Error
Explanation: The MQSC script to configure the coordination queue manager is expected to be located in the coordination directory but is missing.
Response: Review recent changes to the coordination directory and recover from a backup as necessary.

BFGCM0105E: The coordination MQSC script file cannot be located and was expected at "<insert_0>". The script is required for the migration to be completed.
Severity: 20 : Error
Explanation: The MQSC script to configure the coordination queue manager is expected to be located in the coordination directory but is missing.
Response: Review recent changes to the coordination directory and recover from a backup as necessary.

BFGCM0148E: The coordination MQSC script file cannot be located and was expected at "<insert_0>". The script is required for the migration to be completed.
Severity: 20 : Error
Explanation: The MQSC script to configure the coordination queue manager is expected to be located in the coordination directory but is missing.
Response: Review recent changes to the coordination directory and recover from a backup as necessary.

BFGCM0106E: An attempt to access the IBM MQ Managed File Transfer configuration at "<insert_0>" has failed. This may be because the command does not have sufficient authority to read the configuration or that the configuration has been removed.
Severity: 20 : Error
Explanation: The fteMigrateAgent command was not able to access the IBM MQ Managed File Transfer configuration and as a result could not complete the migration.
Response: Check that the given configuration path exists and that this command has the correct authority to access the path and then run the migration command again.

BFGCM0107E: An attempt to access the IBM MQ Managed File Transfer configuration at "<insert_0>" has failed. This may be because the command does not have sufficient authority to read the configuration or that the configuration has been removed.
Severity: 20 : Error
Explanation: The fteMigrateLogger command was not able to access the IBM MQ Managed File Transfer configuration and as a result could not complete the migration.
Response: Check that the given configuration path exists and that this command has the correct authority to access the path and then run the migration command again.

BFGCM0149E: An attempt to access the IBM MQ Managed File Transfer configuration at "<insert_0>" has failed. This might be because the command does not have sufficient authority to read the configuration or that the configuration has been removed.
Severity: 20 : Error
Explanation: The fteMigrateConfigurationOptions command was not able to access the IBM MQ Managed File Transfer configuration and as a result could not complete the migration.
Response: Check that the given configuration path exists and that this command has the correct authority to access the path and then run the migration command again.

BFGCM0108W: The property <insert_1> from property file <insert_0> has a file path that refers to the original configuration.
Severity: 10 : Warning
Explanation: The migration command discovered a property with a file path that refers to the original configuration location.
Response: Move the file referenced by the property outside the original configuration and change the property to match the new location. Then try the migration again. Alternatively, if the migration command is run with the (-f) force parameter, ensure the named file is relocated before the original configuration is removed.

BFGCM0109W: The property <insert_1> from property file <insert_0> has a file path that refers to the original configuration. This file path will not be migrated.
Severity: 10 : Warning
Explanation: The migration command discovered a property with a file path that refers to the original configuration location. The migration command will not migrate this path or its contents.
Response: Move the file referenced by the property and change the property to match its new location before the original configuration is removed.

BFGCM0150W: The property <insert_1> from property file <insert_0> has a file path that refers to the original configuration. This file path will not be migrated.
Severity: 10 : Warning
Explanation: The migration command discovered a property with a file path that refers to the original configuration location. The migration command will not migrate this path or its contents.
Response: Move the file referenced by the property and change the property to match its new location before the original configuration is removed.

BFGCM0151W: The property <insert_0> has a value of <insert_1> which is a relative file path. This value will not be migrated.
Severity: 10 : Warning
Explanation: The fteMigrateAgent command has a property value which is a relative file path. The value will not be migrated.
Response: Review the named property and change its value to a full absolute file path.

BFGCM0152W: The property <insert_0> has a value of <insert_1> which is a relative file path. This value will not be migrated.
Severity: 10 : Warning
Explanation: The fteMigrateLogger command has a property value which is a relative file path. The value will not be migrated.
Response: Review the named property and change its value to a full absolute file path.

BFGCM0153W: The property <insert_0> has a value of <insert_1> which is a relative file path. This value will not be migrated.
Severity: 10 : Warning
Explanation: The fteMigrateConfigurationOptions command has a property value which is a relative file path. The value will not be migrated.
Response: Review the named property and change its value to a full absolute file path.

BFGCM0154W: Windows service properties have been detected in <insert_0>. The fteMigrateAgent command will not migrate the windows service configuration.
Severity: 10 : Warning
Explanation: The fteMigrateAgent command has detected a windows service property in the named file. This will not be migrated as part of the command.
Response: Refer to the IBM MQ product documentation for migrating of the windows service configuration.

BFGCM0155W: Windows service properties have been detected in <insert_0>. The fteMigrateLogger command will not migrate the windows service configuration.
Severity: 10 : Warning
Explanation: The fteMigrateLogger command has detected a windows service property in the named file. This will not be migrated as part of the command.
Response: Refer to the IBM MQ product documentation for migrating of the windows service configuration.

BFGCM0156W: Windows service properties have been detected in <insert_0>. The fteMigrateConfigurationOptions command will not migrate the windows service configuration.
Severity: 10 : Warning
Explanation: The fteMigrateConfigurationOptions command has detected a windows service property in the named file. This will not be migrated as part of the command.
Response: Refer to the IBM MQ product documentation for migrating of the windows service configuration.

BFGCM0157E: An attempt to migrate property set <insert_0> has failed because the coordination.properties is present but is missing mandatory properties to complete the migration.
Severity: 20 : Error
Explanation: The fteMigrateAgent command could not perform the requested migration as the coordination information in the source configuration is not complete. The coordination.properties is missing the "coordinationQMgr" property and therefore cannot generate the necessary scripts
Response: Review the named coordination and ensure it is a valid property set to migrate. Where necessary update the coordination.properties so that the "coordinationQMgr" property is present.

BFGCM0158E: An attempt to migrate property set <insert_0> has failed because the coordination.properties is present but is missing mandatory properties to complete the migration.
Severity: 20 : Error
Explanation: The fteMigrateLogger command could not perform the requested migration as the coordination information in the source configuration is not complete. The coordination.properties is missing the "coordinationQMgr" property and therefore cannot generate the necessary scripts
Response: Review the named coordination and ensure it is a valid property set to migrate. Where necessary update the coordination.properties so that the "coordinationQMgr" property is present.

BFGCM0159E: An attempt to migrate property set <insert_0> has failed because the coordination.properties is present but is missing mandatory properties to complete the migration.
Severity: 20 : Error
Explanation: The fteMigrateConfigurationOptions command could not perform the requested migration as the coordination information in the source configuration is not complete. The coordination.properties is missing the "coordinationQMgr" property and therefore cannot generate the necessary scripts
Response: Review the named coordination and ensure it is a valid property set to migrate. Where necessary update the coordination.properties so that the "coordinationQMgr" property is present.

BFGCM0200E: Internal error - no coordination directory has been defined.
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.

BFGCM0201E: Internal error - no coordination has been defined when requested to compare.
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.

BFGCM0203E: The following names will not be included in the migration as these are not valid agent names, <insert_0>.
Severity: 20 : Error
Explanation: The fteMigrateAgent command has a wild card value for the -agentName parameter and a number of entries in the agent directory match the parameter are not valid agent names. These names are not included in the migration.
Response: Review the excluded names and correct and reexecute the fteMigrateAgent for these names.

BFGCM0204E: Internal error - Attempt to copy file <insert_0> to <insert_1> has failed with file not found.
Severity: 20 : Error
Explanation: This exception is unexpected. The cause is not immediately known.
Response: If the problem persists, see problem determination information in the product documentation.

BFGCM0205E: Internal error - Attempt to copy file <insert_0> to <insert_1> has failed with OP Exception <insert_2>
Severity: 20 : Error
Explanation: This exception is unexpected. The cause is not immediately known.
Response: If the problem persists, see problem determination information in the product documentation.

BFGCM0206E: Internal error - Attempt to read NLS message <insert_0> for unsupported end point type <insert_1>
Severity: 20 : Error
Explanation: CMSG0001.
Response: If the problem persists, see problem determination information in the product documentation.

BFGCM0207E: Internal error - Attempt to migrate agent <insert_0> when its configuration contains error.
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.

BFGCM0208E: Cannot merge user <insert_2> into <insert_0>/<insert_1> because the user is already present but has different values.
Severity: 20 : Error
Explanation: Attempt to merge two ProtocolBridgeCredential.xml files cannot be completed because there is a user element present in both files, but the elements have different values.
Response: Review the two user elements and correct the version in the file to be merged.

BFGCM0209E: Internal error - Unable to generate a XML test from document because <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.

BFGCM0210E: Internal error - Unable to generate a XML test from document because <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.

BFGCM0211E: Internal error - attempt to create <insert_0> failed with a file not found 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.

BFGCM0212E: Internal error - attempt to create <insert_0> failed because of an unknown UTF-8 code page. Report exception is <insert_1>
Severity: 20 : Error
Explanation: This exception is unexpected. The cause is not immediately known.
Response: If the problem persists, see problem determination information in the product documentation.

BFGCM0213E: Internal error - attempt to create <insert_0> failed with the following 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.

BFGCM0214E: Internal error - attempt to use a document before it is loaded. File: <insert_0>
Severity: 20 : Error
Explanation: This exception is unexpected. The cause is not immediately known.
Response: If the problem persists, see problem determination information in the product documentation.

BFGCM0215E: Could not open the ProtocolBridgeCredentials.xml file at <insert_0>.
Severity: 20 : Error
Explanation: A ProtocolBridgeCredentials.xml file was expected at the given location but could not be read.
Response: Check that the correct path has been given and that the user has read permission for the file.

BFGCM0216E: Could not open the ProtocolBridgeCredentials.xml file at <insert_0>
Severity: 20 : Error
Explanation: Attempt to read a ProtocolBridgeCredential.xml has failed with a read error although the file was found.
Response: Check that the ProtocolBridgeCredentials.xml file can be read and is complete.

BFGCM0217E: Parsing error: <insert_0>
Severity: 20 : Error
Explanation: The attempt to load and analyze the given name xml file has failed because the file has parsing errors.
Response: Review the parsing error and correct the relevant file.

BFGCM0218E: Internal error - attempt to parse <insert_0> failed with 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.

BFGCM0219E: Internal error - the following exception was encountered during initialization <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.

BFGCM0220E: Internal error - attempt to evaluate <insert_0> failed with 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.

BFGCM0221E: Internal error - attempt to evaluate <insert_0> failed with 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.

BFGCM0222E: Internal error - attempt to evaluate <insert_0> failed with 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.

BFGCM0223E: Internal error - attempt to compile <insert_0> failed with 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.

BFGCM0224E: Internal error - attempt to evaluate <insert_0> failed with 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.

BFGCM0225E: Attempt to rename existing file <insert_0> to <insert_1> has failed.
Severity: 20 : Error
Explanation: The original master copy of the ProtocolBridgeCredentials.xml could not be renamed to a backup file name. As a result the command cannot continue.
Response: Check that the user has full read and write permissions in the directory where the file is held.

BFGCM0226E: Following XML parsing errors have been detected in <insert_0>. <insert_1>
Severity: 20 : Error
Explanation: While attempting to load an XML document a number of parsing errors had been detected, which prevents the command from continuing.
Response: Review and correct the XML parsing errors.

BFGCM0227E: Internal error - attempt to compile <insert_0> failed with 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.

BFGCM0228E: Internal error - attempt to evaluate <insert_0> failed with 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.

BFGCM0229E: Internal error - attempt to evaluate <insert_0> failed with 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.

BFGCM0230E: Internal error - destination file path of <insert_0> already has a file present.
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.

BFGCM0231E: Attempted to migrate agent <insert_0> failed as its properties indicates its a protocol bridge agent, but either the ProtocolBridgeServer property is missing from the agent.properties or the ProtocolBridgeProperties.xml is not present.
Severity: 20 : Error
Explanation: The migration of the agent could not be completed as it is indicated to be a ProtocolBridge agent. However a mandatory protocol bridge properties are missing from the agent.properties or ProtocolBridgeProperties.xml is missing.
Response: Add the missing protocol bridge properties to the agent.properties or investigate if there should have been a ProtocolBridgeProperties.xml file and why this user does not have access.

BFGCM0232E: Attempted to create ProtocolBridgeProperties.xml failed has protocol bridge type <insert_1> is not known for agent <insert_0>.
Severity: 20 : Error
Explanation: The fteMigrateAgent command attempt to generated a ProtocolBridgeProperties.xml from the agent properties, but failed as the protocol bridge type is not known.
Response: Review the agent.properties for the named agent and either remove the "protocolServerName" if the agent is not protocol bridge or correct the "protocolServerType" to one of the known values.

BFGCM0233E: Attempted to create ProtocolBridgeProperties.xml for agent <insert_0> failed has as the mandatory property <insert_1> for the protocol bridge type is not present in the agent properties.
Severity: 20 : Error
Explanation: The fteMigrateAgent command attempt to generated a ProtocolBridgeProperties.xml from the agent properties, but failed as a mandatory property is not present.
Response: Review the agent.properties for the named agent and add the missing mandatory property.

BFGCM0234E: Attempt to migrate agent properties has failed as the property <insert_0> is present but the associated <insert_1> property is missing.
Severity: 20 : Error
Explanation: The fteAgentMigrate could not be complete as there was a missing property. The password property for the associated trust store could not be found and is required to complete the migration.
Response: Review the agent.properties and any recent changes and either remove the trust store property and appending it password property.

BFGCM0235E: Attempted to access <insert_0> has failed as the user does not have file permission to read and write to this file.
Severity: 20 : Error
Explanation: The MQMFTCredentials.xml specified in the command could not be accessed or the directory path to it was not accessible.
Response: Ensure the correct credential path has been given and that the user was read and write access to that file or directory.

BFGCM0236E: Attempted to add secure property <insert_0> to the <insert_1> has failed as the property of <insert_2> already exists, but has different password values.
Severity: 20 : Error
Explanation: The migrate command attempted to create secure values within the MQMFCredential.xml file but could not as the path already existed, but has different values.
Response: Review the original values in the agent.properties of the agent to migrate and correct as necessary.

BFGCM0237E: The file ''<insert_0>'' already exists. Run the command again specifying the -f parameter to force file to be overwritten.
Severity: 20 : Error
Explanation: The file ''{0}'' exists, and you are trying to overwrite the file.
Response: If you want to overwrite the file, specify the '-f' parameter on the command line.

BFGCM0238I: Direct the following MQSC definitions for agent ''<insert_0>'' to queue manager ''<insert_1>''.
Severity: 0 : Information
Explanation: Direct the following MQSC definitions for the specified agent to the specified queue manager.
Response: Direct the following MQSC definitions for the specified agent to the specified queue manager.

BFGCM0239I: A file has been created containing the MQSC definitions to define the agent <insert_0>. The file can be found here: ''<insert_1>''.
Severity: 0 : Information
Explanation: Use the MQSC definitions to configure the agent queues if we have not already done so.
Response: Use the MQSC definitions as input to runmqsc, if available. Alternatively, on z/OS, the commands can be used as input to CSQUTIL. Refer to the topic "Installing > Installing on z/OS > After we have installed on z/OS" in the product documentation for an example of how to do this. The product documentation is available online at: http://publib.boulder.ibm.com/infocenter/wmqfte/v7r0/.

BFGCM0240E: Attempted to generate MQ Script in file <insert_0>, but failed with exception <insert_1>
Severity: 20 : Error
Explanation: The migrate command attempted to generate a MQSC script file, but failed with a file system error message.
Response: Review the error message and ensure that the user has the correct permission to perform write operations to the file.

BFGCM0241I: A file has been created containing the MQSC definitions to delete the agent <insert_0>. The file can be found here: ''<insert_1>''.
Severity: 0 : Information
Explanation: A file has been created containing the MQSC definitions to delete your agent.
Response: Use the MQSC definitions as input to runmqsc, if available. Alternatively, on z/OS, the commands can be used as input to CSQUTIL. Refer to the topic "Installing > Installing on z/OS > After we have installed on z/OS" in the product documentation for an example of how to do this. The product documentation is available online at: http://publib.boulder.ibm.com/infocenter/wmqfte/v7r0/.

BFGCM0242I: Direct the following MQSC definitions for your coordination queue manager ''<insert_0>'' to an MQSC session if we have not already done so.
Severity: 0 : Information
Explanation: Use the MQSC definitions to configure the coordination queue manager for MQMFT if we have not already done so.
Response: Use the MQSC definitions as input to runmqsc, if available. Alternatively, on z/OS, use the commands as input to CSQUTIL. Refer to the topic "Installing > Installing on z/OS > After we have installed on z/OS" in the product documentation for an example of how to do this. The product documentation is available online at: http://publib.boulder.ibm.com/infocenter/wmqfte/v7r0/.

BFGCM0243I: A file has been created that contains the MQSC definitions for your coordination queue manager. The file can be found here: ''<insert_0>''.
Severity: 0 : Information
Explanation: Use the MQSC definitions to configure the coordination queue manager for MQMFT if we have not already done so.
Response: Use the MQSC definitions as input to runmqsc, if available. Alternatively, on z/OS, use the commands as input to CSQUTIL. Refer to the topic "Installing > Installing on z/OS > After we have installed on z/OS" in the product documentation for an example of how to do this. The product documentation is available online at: http://publib.boulder.ibm.com/infocenter/wmqfte/v7r0/.

BFGCM0244E: Cannot merge user <insert_2> into <insert_0>/<insert_1> because the user is already present but has different values.
Severity: 20 : Error
Explanation: Attempt to merge two ConnectDirectCredential.xml files cannot be completed because there is a user element present in both files, but the elements have different values.
Response: Review the two user elements and correct the version in the file to be merged.

BFGCM0245E: Internal error - the following exception was encountered during initialization <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.

BFGCM0246E: Internal error - the following exception was encountered during initialization <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.

BFGCM0247E: Internal error - destination file path of <insert_0> already has a file present.
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.

BFGCM0248E: XML file <insert_0> has parsing error: <insert_1>
Severity: 20 : Error
Explanation: The attempt to load and analyze the given name xml file has failed because the file has parsing errors.
Response: Review the parsing error and correct the relevant file.

BFGCM0249E: Internal error - attempt to parse <insert_0> failed with 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.

BFGCM0250E: Attempt to migrate logger properties has failed as the property <insert_0> is present but the associated <insert_1> property is missing.
Severity: 20 : Error
Explanation: The fteLoggerMigrate could not complete as there was a missing property. The database password property associated with the database user property could not be found and is required to complete the migration.
Response: Review the databaselogger.properties and any recent changes and either remove the database user property or add a database password property.

BFGCM0251E: Attempted to add secure property <insert_0> to the <insert_1> has failed as the property name of <insert_2> already exists, but has different password values.
Severity: 20 : Error
Explanation: The migrate command attempted to create secure values within the MQMFCredential.xml file but could not as the name already existed, but has different values.
Response: Review the original values in the agent.properties of the agent to migrate and correct as necessary.

BFGCM0252E: Agent migration could not be completed because <insert_0>
Severity: 20 : Error
Explanation: Attempt to migrate an agent could not be complete for the given reason.
Response: Review the given reason and correct as necessary.

BFGCM0253E: Logger migration could not be completed because <insert_0>
Severity: 20 : Error
Explanation: Attempt to migrate an logger could not be complete for the given reason..
Response: Review the given reason and correct as necessary.

BFGCM0254E: Configuration migration could not be completed because <insert_0>
Severity: 20 : Error
Explanation: Attempt to migrate an configuration could not be complete for the given reason.
Response: Review the given reason and correct as necessary.

BFGCM0255E: An entry for ''<insert_0>'' and ''<insert_2>'' already exists in credentials file ''<insert_1>'' but has different values for the credentials. As a result this command cannot complete successfully.
Severity: 20 : Error
Explanation: The command has requested that a new credential entry is added to the named credentials file. However, the entry already exists and has different credential values. As a result the command cannot complete successfully.
Response: Review whether the credentials need to be updated and if necessary use the (-f) force parameter to replace the existing credentials.

BFGCM0256E: An entry for ''<insert_0>'' already exists in credentials file ''<insert_1>'' but has different values for the credentials. As a result this command cannot complete successfully.
Severity: 20 : Error
Explanation: The command has requested that a new credential entry is added to the named credentials file. However, the entry already exists and has different credential values. As a result the command cannot complete successfully.
Response: Review whether the credentials need to be updated and if necessary use the (-f) force parameter to replace the existing credentials.

BFGCM0257I: The credentials information has been successfully added to the existing credentials file ''<insert_0>''.
Severity: 0 : Information
Explanation: An information message that indicates that the credentials details have been successfully added to the existing named credentials file.
Response: No action required

BFGCM0258I: A new credentials file ''<insert_0>'' has been created and the details have been successfully added. The permissions and ownership may need to be reviewed to ensure the correct users have access.
Severity: 0 : Information
Explanation: An information message that indicates that the credentials details have been successfully added to the new named credentials file. The permissions and ownership of the new credentials will have been set to the user performing the command. If other users require access then the ownership and permissions will need to be reviewed.
Response: Review the ownership and permissions to ensure the relevant users have access.

BFGCM0259E: Internal error: The required parameter ''<insert_0>'' for addCredentials() is missing.
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.

BFGCM0260I: The credentials file ''<insert_0>'' has not been updated because the given credentials are already present.
Severity: 0 : Information
Explanation: An information message that indicates that the credentials file already has matching credentials details and the file does not need to be updated.
Response: No action required.

BFGCM0261E: Attempt to access <insert_0> has failed because the directory or PDSE does not exist.
Severity: 20 : Error
Explanation: The MQMFTCredentials.xml file specified in the command does not exist and the parent location also does not exist.
Response: Ensure that the correct credential path has been specified and that the directory or PDSE exists.

BFGCM0262E: Attempt to access <insert_0> has failed because the user does not have file permission to read and write to the parent location.
Severity: 20 : Error
Explanation: The MQMFTCredentials.xml file specified in the command could not be accessed because the parent location is not accessible.
Response: Ensure that the correct credential path has been specified and that the user has read and write access to that file, directory, or PDSE.

BFGCM0263E: The credential file path <insert_0> must be an absolute path.
Severity: 20 : Error
Explanation: The given credential file path is not complete and relevant to the current users directory. This argument must be given as an absolute file path.
Response: Review the argument and change the credentials path to be an absolute file path.

BFGCM0264E: The credentials file <insert_0> cannot be accessed.
Severity: 20 : Error
Explanation: The credentials file in the given data set member cannot be accessed. This can occur for the following reasons: 1. The data set or member does not exist. 2. The user ID that started the agent or logger does not have read/write access to the data set. 3. The data set has not been allocated with the correct attributes.
Response: Following are the possible actions: 1. Ensure that a valid data set and member name has been specified. 2. Review the messages on the job log to see which security profile is being used to deny access. Use this to give the user ID access to the data set. 3. Use a PDSE with the correct attributes as described in the Knowledge Center.

BFGCM0265E: File ''<insert_0>'' for Connect:Direct bridge agent ''<insert_1>'' cannot be migrated because the -credentialPath option has not been specified.
Severity: 20 : Error
Explanation: A Connect:Direct bridge agent has credentials that need to be migrated. All credentials files for MQMFT are required to be located at a path specified by the -credentialPath option. But the -credentialPath option was not specified.
Response: Rerun the command with the -credentialPath option specifying a valid path.

BFGCM0266E: File ''<insert_1>'' for protocol bridge agent ''<insert_0>'' cannot be migrated because the -credentialPath option has not been specified.
Severity: 20 : Error
Explanation: A protocol bridge agent has a credentials XML file and properties XML file which has references to the credentials, these need to be migrated. All credentials files for MQMFT are required to be located at a path specified by the -credentialPath option. This could not be completed as a valid -credentialPath option was not specified.
Response: Rerun the command with the -credentialPath option specifying a valid path.

BFGCM0267E: File ''<insert_1>'' and ''<insert_2>'' for protocol bridge agent ''<insert_0>'' cannot be migrated because the -credentialPath option has not been specified.
Severity: 20 : Error
Explanation: A protocol bridge agent has a credentials XML file and a properties XML file which has references to the credentials, these need to be migrated. All credentials files for MQMFT are required to be located at a path specified by the -credentialPath option. This could not be competed as a valid -credentialPath option was not specified.
Response: Rerun the command with the -credentialPath option specifying a valid path.

BFGCM0268W: File ''<insert_1>'' for protocol bridge agent ''<insert_0>'' will not be migrated as the -credentialPath option has not been specified.
Severity: 10 : Warning
Explanation: A protocol bridge agent has a credentials XML file and a properties XML file which has references to the credentials, these need to be migrated. All credentials files for MQMFT are required to be located at a path specified by the -credentialPath option. However the migration will continue as the (-f) force option is present even though a valid -credentialPath option has not specified. The migration will not include the credential and/or properties XML files.
Response: Review the -credentialPath option unless it was the expected result.

BFGCM0269W: File ''<insert_1>'' and ''<insert_2>'' for protocol bridge agent ''<insert_0>'' will not be migrated as the -credentialPath option has not been specified.
Severity: 10 : Warning
Explanation: A protocol bridge agent has a credentials XML file and a properties XML file which has references to the credentials, these need to be migrated. All credentials files for MQMFT are required to be located at a path specified by the -credentialPath option. However the migration will continue as the (-f) force option is present even though a valid -credentialPath option has not specified. The migration will not include the credential and/or properties XML files.
Response: Review the -credentialPath option unless it was the expected result.

BFGCM0270E: The migrate program attempted to decode a value from the credentials but failed because ''<insert_0>''
Severity: 20 : Error
Explanation: The migrate operation detected an error when attempting to compare the new credential values with the existing values which had been obfuscated.
Response: Review the reported error and act on its recommendations.

BFGCM0271E: The migrate program attempted to decode a value from the credentials but failed because ''<insert_0>''
Severity: 20 : Error
Explanation: The migrate operation detected an error when attempting to compare the new credential values with the existing values which had been obfuscated.
Response: Review the reported error and act on its recommendations.

BFGCM9999E: <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, refer to the problem determination information on the product Website.