Could not load properties file ''<insert_0>'' due to exception: <insert_1>
Severity
20 : Error
Explanation
The specified properties file could not be loaded because of the specified exception.
Response
Use the exception information from the message to diagnose the problem. Resolve the problem if possible, otherwise contact the IBM Support Center for further assistance.
BFGPR0008W
Audit publication is disabled.
Severity
10 : Warning
Explanation
No audit message will be published because the coordination queue manager has not been specified.
Response
Correctly specify the coordination queue manager.
BFGPR0009E
An empty expression was used as the success return code for a command invocation.
Severity
20 : Error
Explanation
An empty expression has been specified for use when evaluating the return code for a command invocation. It is not valid to specify an empty expression for the expression used to evaluate a command invocation.
Response
Correct the place where the expression has been specified so that a non-empty expression is specified.
BFGPR0010E
The success return code expression ''<insert_0>'', is malformed as it ends with a logical operator.
Severity
20 : Error
Explanation
A malformed expression has been specified for use when evaluating the return code for a command invocation. The expression is malformed because it ends with either the '|' or '&' logical operators which are intended to join expressions.
Response
Correct the place where the expression has been specified so that a well-formed expression is specified.
BFGPR0011E
The success return code expression ''<insert_0>'' is malformed as it contains the symbol ''<insert_1>'' where either the logical operators ''|'' or ''&'' are expected.
Severity
20 : Error
Explanation
A malformed expression has been specified for use when evaluating the return code for a command invocation. The expression is malformed because the specified symbol was encountered where either the '|' or '&' logical operators were expected.
Response
Correct the place where the expression has been specified so that a well-formed expression is specified.
BFGPR0012E
The success return code expression ''<insert_0>'' is malformed as it contains the symbol ''<insert_1>'' where a numeric value is expected.
Severity
20 : Error
Explanation
A malformed expression has been specified for use when evaluating the return code for a command invocation. The expression is malformed because the specified symbol was encountered where a numeric value was expected.
Response
Correct the place where the expression has been specified so that a well-formed expression is specified.
BFGPR0013E
The success return code expression ''<insert_0>'' is malformed as it contains the symbol ''<insert_1>'' where a comparison operator of ''!'', ''<'' or ''>'' is expected.
Severity
20 : Error
Explanation
A malformed expression has been specified for use when evaluating the return code for a command invocation. The expression is malformed because the specified symbol was encountered where a comparison operator was expected.
Response
Correct the place where the expression has been specified so that a well-formed expression is specified.
BFGPR0014E
The country and language format of <insert_0> is not valid.
Severity
20 : Error
Explanation
The given country and language parameter could not be validated against the expected format. The expected format is cc-ll, where cc is the two letter country code and ll is the two letter language code.
Response
Review the given parameter and correct the format as necessary.
BFGPR0015E
The language code of <insert_0> does not match any of the know values.
Severity
20 : Error
Explanation
The language element of the given country and language parameter does not match any of the know values and has been rejected.
Response
Review the given parameter and correct the language element as necessary.
BFGPR0016E
The country code of <insert_0> does not match any of the know values.
Severity
20 : Error
Explanation
The country element of the given country and language parameter does not match any of the know values and has been rejected.
Response
Review the given parameter and correct the country element as necessary.
BFGPR0017E
The given property value for ''<insert_0>'' is not valid as it contains control characters. This usually occurs if the backslash character has not been escaped.
Severity
20 : Error
Explanation
When inputting property values that contain a backslash character (e.g., a Windows path name), these values must be escaped to ensure they are passed through as expected.
Response
Replace all occurrences of the backslash '\\' with a double-backslash '\\\\' in the referenced property value.
BFGPR0018E
An incomplete transfer template has been detected in either the Id or name 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.
BFGPR0019E
An invalid transfer template has been detected and the parser has reported <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.
BFGPR0020E
Internal error has occurred and a <insert_0> exception has been reported with description <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.
BFGPR0021E
Internal error has occurred with an unsupported encoding.
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.
BFGPR0022E
The command received MQI reason code <insert_0> when connecting to coordination queue ''<insert_1>''. The requested action cannot be completed.
Severity
20 : Error
Explanation
The command cannot access transfer template information because the command cannot establish a binding mode connection to the specified queue manager because of the specified MQI reason code. The requested action cannot be completed.
Response
Consult the IBM MQ product documentation to determine the cause of the problem. Resolve the problem.
BFGPR0023E
The command received MQI reason code <insert_0> when connecting to coordination queue ''<insert_1>'' on host <insert_2>, port <insert_3> using channel <insert_4>. The requested action cannot be completed.
Severity
20 : Error
Explanation
The command cannot access transfer template information because the command cannot establish a client mode connection to the specified queue manager because of the specified MQI reason code. The requested action cannot be completed.
Response
Consult the IBM MQ product documentation to determine the cause of the problem. Resolve the problem.
BFGPR0024E
Internal error has occurred with a report JMQI exception of <insert_0> caused by <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.
BFGPR0025E
Internal error has occurred with a report JMQI exception of <insert_0>.
Severity
20 : Error
Explanation
This exception is unexpected. The cause is not immediately known.
Response
If the problem persists, see problem determination information in the product documentation.
BFGPR0026E
MQ returned reason code <insert_0> when attempting to read the <insert_2> topic string from queue <insert_1> on queue manager <insert_3>.
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.
BFGPR0027E
MQ returned reason code <insert_0> when attempting to delete template name <insert_1> with Id <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.
BFGPR0028E
Internal error has occurred. Xpath reported exception <insert_1> when processing <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.
BFGPR0029E
Internal error has occurred. Xpath reported exception <insert_1> when processing <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.
BFGPR0030E
The trace request has the following XML errors: <insert_0>.
Severity
20 : Error
Explanation
A request to change trace settings has been received. However it contains XML syntax errors and could not be processed.
Response
Review the XML request and correct as necessary. If this was generated by a supplied command then contact the IBM Support Center for further assistance.
BFGPR0031E
The XML trace request contains mixed triggers. The -disableOnAnyFFDC parameter cannot be combined with the -disableOnFFDC parameter.
Severity
20 : Error
Explanation
A request for changing trace settings has been received, but contains mixed FFDC triggers. It contains requests to disable on both any FFDC and a specific FFDC. This is ambiguous and the request could not be completed.
Response
Review the XML request and correct as necessary. If this was generated by a supplied command then contact the IBM Support Center for further assistance.
BFGPR0032E
An internal error has occurred. Xpath reported exception <insert_0>.
Severity
20 : Error
Explanation
This exception is unexpected. The cause is not immediately known.
Response
If the problem persists, see problem determination information in the product documentation.
BFGPR0033E
Log capture could not be enabled due to the following exception: <insert_0>
Severity
20 : Error
Explanation
Log capturing has been configured to be enabled but was not initialized due to an exception. Log capturing has been disabled.
Response
Review the exception and take any necessary action before restarting the agent.
BFGPR0034E
The tag filter for log capturing has the following syntax errors: <insert_0>.
Severity
20 : Error
Explanation
The supplied tag filter for log capture contains a syntax error and cannot be used for filtering the log capture. Log capture will be enabled but filtering will not be used.
Response
Review the syntax errors and correct the regular expression as necessary before restarting the agent.
BFGPR0035E
Internal error. The capture log file name of <insert_0> is missing the ''%d'' sequence for substituting the index value.
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.
BFGPR0036E
Failed to write capture log information to <insert_0> due to the following exception: <insert_1>
Severity
20 : Error
Explanation
Writing to the capture log file has failed due to a problem with the storage device. Capture logging has been disabled.
Response
Check that the directory that the capture logs are written to has the correct permissions for the agent to write to the directory, and that there is sufficient file space. Make any necessary changes and restart the agent.
BFGPR0037E
Failed to delete capture log file <insert_0>
Severity
20 : Error
Explanation
An attempt to delete the oldest capture log file has failed. Capture logging has been disabled.
Response
Check that the agent has permission to delete this file and then restart the agent.
BFGPR0038E
Failed to rename capture log file <insert_0> to <insert_1>
Severity
20 : Error
Explanation
An attempt to rename the capture log file has failed. Capture logging has been disabled.
Response
Check that the agent has permission to rename these files and then restart the agent.
BFGPR0039E
The capture log directory of <insert_0> does not exist or the agent does not have permission to write files to the directory.
Severity
20 : Error
Explanation
The agent is unable to access the specified directory, either because the directory does not exist or because the agent does not have permission to write to the directory. Capture logging has been disabled.
Response
Check that the directory does exist and the agent has write permission for the directory. Restart the agent.
BFGPR0040E
Failed to write capture log information to <insert_0> due to the exception <insert_1>
Severity
20 : Error
Explanation
Writing to the capture log file has failed due to a problem with the storage device. Capture logging has been disabled.
Response
Check that the directory that the capture logs are written to has the correct permissions for the agent to write to the directory, and that there is sufficient file space. Make any necessary changes and restart the agent.
BFGPR0041W
Use default value of ''<insert_1>'' for property ''<insert_0>''. The specified value ''<insert_2>'' is invalid. The value must be an integer in the range <insert_3> to <insert_4>.
Severity
10 : Warning
Explanation
An invalid value was specified for an integer property. The system will use the default value.
Response
Update the property definition to specify a valid value.
BFGPR0042W
Invalid logCapture property value: ''<insert_0>''. Valid values are ''true'' or ''false''.
Severity
10 : Warning
Explanation
The value specified for the logCapture property is not valid. Valid values are 'true' and 'false'. The default value of 'false' will be used.
The value specified for the logCaptureFileSize property is not valid. The value must be a positive integer that specifies a size in megabytes. The default value for the logCaptureFileSize property (10 MB) will be used.
Response
Correct the value of the logCaptureFileSize property.
The value specified for the logCaptureFiles property is not valid. The value must be a positive integer that specifies the maximum number of log capture files to generate. The default value for the logCaptureFiles property (10) will be used.
Response
Correct the value of the logCaptureFiles property.
BFGPR0045E
A problem has occurred while parsing the <insert_0> XML file. The internal MQMFT data has not been updated. The details of the error are: <insert_1>
Severity
20 : Error
Explanation
A SAX parsing error has been encountered while parsing an XML file.
Response
Correct the XML file to resolve the problem.
BFGPR0046E
A problem has occurred while attempting to open the <insert_0> XML file. The internal MQMFT data has not been updated. The details of the error are: <insert_1>
Severity
20 : Error
Explanation
The XML file cannot be opened.
Response
Check that the XML file is in the correct location and accessible by the agent.
BFGPR0047E
A problem has occurred while attempting to read the <insert_0> XML file. The internal MQMFT data has not been updated. The details of the error are: <insert_1>
Severity
20 : Error
Explanation
The XML file cannot be read.
Response
Check that the XML file is accessible by the agent.
BFGPR0048E
A problem has occurred while attempting to read the <insert_0> XML file. The internal MQMFT data has not been updated. The details of the error are: <insert_1>
Severity
20 : Error
Explanation
A SAX error has been encountered while accessing an XML file.
Response
Take appropriate action based on the exception.
BFGPR0049E
An internal error has occurred while creating the XML document builder for the <insert_0> XML file. The internal MQMFT data has not been updated. The details of the error are: <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.
BFGPR0050E
An invalid regular expression has been found in the <insert_0> XML file. The internal MQMFT data has not been updated. The details of the error are: <insert_1>
Severity
20 : Error
Explanation
When loading an XML file that contains regular expression fields, the contents are validated to ensure they specify a syntactically correct regular expression.
Response
Correct the regular expression fields that are in error in the XML file to resolve the problem.
BFGPR0051E
An invalid data value has been found in the <insert_0> XML file. The internal MQMFT data has not been updated. The details of the error are: <insert_1>
Severity
20 : Error
Explanation
When loading an XML file the contents are validated to ensure that all data is valid. See the explanation associated with the error for further information.
Response
Correct the values that are in error in the XML file to resolve the problem.
BFGPR0052E
XML file <insert_0> does not exist. The internal MQMFT data has not been updated.
Severity
20 : Error
Explanation
The XML file cannot be found.
Response
Create the XML file with the correct path and file name.
BFGPR0053I
The <insert_0> file has been updated.
Severity
0 : Information
Explanation
The agent has detected a change in the XML configuration document. The agent has reloaded the XML configuration document and will now operate based on the content of the new document.
Response
No user action is required.
BFGPR0054E
The program specification ''<insert_0>'' does not define the command to be run.
Severity
20 : Error
Explanation
A program specification must contain the name of the command to be called.
Response
Check the syntax of the program specification and correct as required. If necessary refer to the product documentation to determine the correct syntax for the command. Then reissue the command.
BFGPR0055E
Ant script property parameter ''<insert_1>'' is invalid within the program specification ''<insert_0>''.
Severity
20 : Error
Explanation
An Ant script property parameter must be in the form: =, where is 1 or more characters, and is 0 or more characters.
Response
Check the syntax of the program specification and correct as required. If necessary refer to the product documentation to determine the correct syntax for the command. Then reissue the command.
BFGPR0056E
The program specification ''<insert_0>'' defines one or more arguments for a <insert_1> command type. This command type does not support arguments.
Severity
20 : Error
Explanation
Command arguments are not supported for certain command types (such as JCL scripts).
Response
Check the syntax of the program specification and correct as required. If necessary refer to the product documentation to determine the correct syntax for the command. Then reissue the command.
BFGPR0057E
The program specification ''<insert_0>'' is invalid.
Severity
20 : Error
Explanation
A program specification is syntactically incorrect and cannot be parsed.
Response
Check the syntax of the program specification and correct as required. If necessary refer to the product documentation to determine the correct syntax for the command. Then reissue the command.
BFGPR0058E
Internal error during initialization of XPath components. The error 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.
BFGPR0059E
Internal error during parsing of XPath components. The error 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.
BFGPR0060E
A parsing configuration error was reported while parsing an XML message. The error 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.
BFGPR0061E
A SAX error was reported while parsing an XML message. The error 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.
BFGPR0062E
An IO error was reported while parsing an XML message. The error 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.
BFGPR0063E
Schema errors have been detected in the imported XML message. See associated reported data for details.
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.
BFGPR0064E
An environment variable used in a configuration property could not be found. Variable name: <insert_0>
Severity
20 : Error
Explanation
An environment variable included as part of a configuration property could not be found when an attempt was made to replace the variable with its value.
Response
Check that the supplied environment variable has been defined on the system and can be found by the process that reported this error. When the required variable is available, restart the process.
BFGPR0065E
The specified credentials file could not be found. File path: <insert_0>
Severity
20 : Error
Explanation
When an attempt was made to open a credentials file, no file was found to open.
Response
Check that the file exists in the specified location and retry the operation.
BFGPR0066E
An error occurred when initializing the parser used to process credentials files. Reported error: <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.
BFGPR0067E
An error occurred when processing the contents of a credentials file. File path <insert_0>. Reported error: <insert_1>
Severity
20 : Error
Explanation
An exception was thrown when the supplied credentials file was processed. This is most likely because of a problem with the format of the file.
Response
Determine the problem from the error information included. Check that the supplied credentials file conforms to the MQMFTCredentials.xsd schema definition and retry the operation.
BFGPR0068E
An error occurred when obfuscating the contents of a credentials file. File path <insert_0>. Reported error: <insert_1>
Severity
20 : Error
Explanation
An unexpected error occurred when processing the contents of the supplied credentials file during obfuscation.
Response
Determine the problem from the error information included. Check the contents of the supplied credentials file for errors and run the command again.
BFGPR0069E
The type of a credentials file could not be determined during obfuscation. File path <insert_0>.
Severity
20 : Error
Explanation
The contents of the supplied credentials file do not match the format for any of the credentials file types supported.
Response
Check the contents of the supplied credentials file for errors and run the command again.
BFGPR0070E
An exception occurred during initialization of encoders used during obfuscation. Reported error: <insert_0>
Severity
20 : Error
Explanation
Response
BFGPR0071E
An exception occurred when encoding a value in a credentials file. Reported error: <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.
BFGPR0072E
An exception occurred when decoding a value in a credentials file. Reported error: <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.
BFGPR0073E
The backup file ''<insert_0>'' created during obfuscation could not be deleted.
Severity
20 : Error
Explanation
The temporary backup file created during the running of the fteObfuscate command could not be deleted when the command successfully completed. This might be because of an intermittent I/O problem on the system. Because the command completed successfully, the file is no longer required so can be safely deleted.
Response
Manually delete the supplied backup file.
BFGPR0074E
The security permissions defined for credentials file ''<insert_0>'' do not meet the minimum requirements for a file of this type. Reported problem: <insert_1>
Severity
20 : Error
Explanation
For security purposes credentials files have restrictions placed on the access rights that users have to the file. A credentials file must not have system-wide read, write, or delete permissions set. For more information on credentials files and the restrictions placed on them, consult the product documentation.
Response
Modify the security permissions of the specified credentials file and run the command again.
BFGPR0075E
A problem occurred accessing the data in credentials file ''<insert_0>''. Reported problem: <insert_1>
Severity
20 : Error
Explanation
There has been an error accessing the data in the supplied credentials file. The included problem message will provide more specific details about the problem.
Response
Take the necessary steps to fix the reported problem and run the command again.
BFGPR0076W
The given command specification ''<insert_0>'' contains a '':'' character, but has been interpreted as an executable task because no recognizable type was found.
Severity
10 : Warning
Explanation
Because no recognizable type was found in the call specification, the executable type has been assumed. However, a colon (:) character appeared within the command specification which may indicate a typing error in the original command.
Response
Either add a prefix to the call specification with the 'executable:' type indicator or correct the typing error if a different type was intended.
BFGPR0077W
The value ''<insert_0>'' of the commandMessagePriority property is invalid. The command IBM MQ message priority has been set to the default value of -1 (MQPRI_PRIORITY_AS_Q_DEF).
Severity
10 : Warning
Explanation
The value of the commandMessagePriority property must be an integer between -1 and 9.
Response
Set a valid value for the commandMessagePriority property.
BFGPR0079E
An unexpected error occurred when processing substitution file: ''<insert_0>''. 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.
BFGPR0080E
A problem occurred when parsing substitution file: ''<insert_0>''. Exception: <insert_1>
Severity
20 : Error
Explanation
When the specified susbtitution.xml was parsed, the file did not conform to the schema defined in the Substitution.xsd file, which means that the XML file cannot be processed. Therefore, it is not possible to correctly perform the expected substitution on the supplied agent's configuration.
Response
Ensure that the format of the supplied substitution.xml file conforms to the schema defined in the Substitution.xsd schema file.
BFGPR0081E
The low attribute value of ''<insert_0>'' was found to be greater than the high attribute value of ''<insert_1>'' in substitution file ''<insert_2>''.
Severity
20 : Error
Explanation
The value of the low attribute of a storeNumber element in the specified substitution.xml file was found to be greater than the value of the high attribute. As this combination cannot ever match against a valid store number it is not allowed.
Response
Change the values of the low and high attributes of the storeNumber element in the substitution.xml file.
BFGPR0082E
The priority value of <insert_0> supplied on a program call request is outside the supported range of 1 - 9.
Severity
20 : Error
Explanation
The command priority must fall within the range of 1 - 9.
Response
Correct the program call specification so that the priority falls within the accepted range and run the command again.
BFGPR0083E
The status message of ''<insert_0>'' supplied on a program call request is longer (<insert_1> characters) than the maximum of 46 characters supported by the 4690 OS.
Severity
20 : Error
Explanation
The 4690 OS limits the maximum length of the status message to no more than 46 characters.
Response
Reduce the length of the status message and run the command again.
BFGPR0084E
Failed to create file ''<insert_0>''. Reason: <insert_1>
Severity
20 : Error
Explanation
The identified file could not be created for the reason given.
Response
Complete the necessary steps to fix the reported problem and run the command again.
BFGPR0086W
The value ''<insert_0>'' for the <insert_1> agent property is invalid.
Severity
10 : Warning
Explanation
The value of the given property must be an integer within the accepted range.
Response
Refer to the documentation to determine the range of accepted values and set the property appropriately.
BFGPR0087W
The metadata parameter ''<insert_0>'' is incomplete near the metadata ''<insert_1>''.
Severity
10 : Warning
Explanation
An attempt to parse the metadata values from a given command has failed because the value is ambiguous or incorrect between parameters.
Response
Review all the metadata values and check that they are complete and any required escape characters have been included.
BFGPR0088W
The metadata parameter ''<insert_0>'' is incomplete following the metadata ''<insert_1>''.
Severity
10 : Warning
Explanation
An attempt to parse the metadata values from a given command has failed because the values are ambiguous or incorrect at the end of the parameters.
Response
Review all the metadata values and check that they are complete and any required escape characters have been included.
BFGPR0089E
The given trigger content capture of ''<insert_0>'' is not recognized.
Severity
20 : Error
Explanation
The value given for the trigger content capture (-tcc) does not match "srcDest" or "destSrc". As a result the monitor cannot be created.
Response
Review the trigger content capture value and change to the correct value before trying the command again.
BFGPR0090E
The trigger content regular expression of ''<insert_0>'' has the following reported errors ''<insert_1>''.
Severity
20 : Error
Explanation
The trigger content regular expression has one or more syntax errors. As a result the monitor cannot be created.
Response
Review the error message and correct the regular expression as necessary before trying the command again.
BFGPR0091E
A create monitor XML request has a content reference where the trigger content capture group order of ''<insert_0>'' is not recognized.
Severity
20 : Error
Explanation
An error has been detected while examining a create monitor XML request. The trigger content capture order attribute has an invalid value.
Response
Locate where the create monitor XML request was created and review the settings for the trigger content before retrying.
BFGPR0092E
Internal error: Attempt to parse a content XML sequence failed 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.
BFGPR0093E
Internal error: Attempt to compile a content Xpath component failed 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.
BFGPR0094E
Internal error: Attempted to invoke method <insert_1> with <insert_0> in the IO component has failed with <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.
BFGPR0095E
Internal error: An internal secure item has an invalid number format. Hexadecimal values are expected.
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.
BFGPR0096E
The password associated with file <insert_0> has an incorrect format. Hexadecimal values are expected.
Severity
20 : Error
Explanation
The password specified in the credentials file for the named store has an invalid value. Only hexadecimal values are expected.
Response
Review the password in the credential file and ensure it is the correct value, then restart the agent.
BFGPR0097E
The password associated with file <insert_0> has an incorrect format. Cipher block length is incorrect.
Severity
20 : Error
Explanation
The password specified in the credentials file for the named store has an invalid value. The password used is a block cipher and its total length is not a multiple of its block size.
Response
Review the password in the credential file and ensure it is the correct value and size, then restart the agent.
BFGPR0098E
The password associated with file <insert_0> has an incorrect format. Incorrect padding has been applied.
Severity
20 : Error
Explanation
The password specified in the credentials file for the named store has an invalid value. The padding for the password has an incorrect number of bytes.
Response
Review the password in the credential file and ensure it is the correct value and padding, then restart the agent.
BFGPR0099E
The truststore file ''<insert_0>'' does not exist.
Severity
20 : Error
Explanation
The truststore file must exist.
Response
Check that the truststore file path is correct and that the file exists.
BFGPR0100E
The keystore file ''<insert_0>'' does not exist.
Severity
20 : Error
Explanation
The keystore file must exist.
Response
Check that the keystore file path is correct and that the file exists.
BFGPR0101E
The security permissions defined for keystore file ''<insert_0>'' do not meet the minimum requirements for a file of this type. Reported problem: <insert_1>
Severity
20 : Error
Explanation
For security purposes, truststore files have restrictions placed on the access rights that users have to the file. A keystore file must not have system-wide read, write, or delete permissions set. For more information on keystore files and the restrictions placed on them, consult the product documentation.
Response
Modify the security permissions of the specified keystore file and run the command again.
BFGPR0102E
The security permissions defined for truststore file ''<insert_0>'' do not meet the minimum requirements for a file of this type. Reported problem: <insert_1>
Severity
20 : Error
Explanation
For security purposes, truststore files have restrictions placed on the access rights that users have to the file. A truststore file must not have system-wide read, write, or delete permissions set. For more information on truststore files and the restrictions placed on them, consult the product documentation.
Response
Modify the security permissions of the specified truststore file and run the command again.
BFGPR0103E
Invalid metadata XML format was found while parsing metadata element <insert_0> in XML message.
Severity
20 : Error
Explanation
A corrupt XML message has been discovered in one of the MFT internal queues. The XML message is no longer usable and will be ignored.
Response
Review the current activities to how the corruption occurred. If necessary use the fteCleanAgent command to clear the relevant MFT queue.
BFGPR0104E
"Internal build error: Build Product version of <insert_0> is not known in ProductVersion."
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.
BFGPR0105E
"Internal build error: request to perform a z/OS PDS action of method <insert_0> is not supported."
Severity
20 : Error
Explanation
This exception is unexpected. The cause is not immediately known.
Response
If the problem persists, see problem determination information in the product documentation.
BFGPR0106E
Internal build error: an attempt to generate an unsupported z/OS PDS action has occurred. The USS file name value 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.
BFGPR0107E
Unable to create a new temporary file with a file name based on format: <insert_0>, because there are already files present with this name.
Severity
20 : Error
Explanation
All files with a name based on the specified file name format already exist. Hence it is not possible to create a new file with name based on the file name format.
Response
If possible, delete all files with names of the identified format and run the command again. If the problem persists, contact the IBM Support Center for further assistance.
BFGPR0108E
Internal error: The system attempted to obtain the PDSE library name from PDSE member name ''<insert_0>'', but the library name was not 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.
BFGPR0109E
Internal error: The system attempted to obtain the parent directory name from file name ''<insert_0>'', but the directory name was not 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.
BFGPR0110E
The specified ARM element type ''<insert_0>'' is invalid.
Severity
20 : Error
Explanation
ARM element types can only be 1 to 8 characters long, contain only characters A to Z, 0 to 9, dollar ($), hash (#), at (@), and cannot start with characters 0 to 9. Note that element types that start with A through I, or SYS, are reserved for use by IBM.
Response
Correct the specified ARM element type property (armELEMTYPE), and submit the required job again.
BFGPR0111E
The specified ARM element name ''<insert_0>'' is invalid.
Severity
20 : Error
Explanation
ARM element names can only be 1 to 16 characters long, contain only characters A to Z, 0 to 9, dollar ($), hash (#), at (@), underscore (_), and cannot start with characters 0 to 9. Note that element names that start with A through I, or SYS, are reserved for use by IBM.
Response
Correct the specified ARM element name property (armELEMENT), and submit the required job again.
BFGPR0112E
Already registered with ARM.
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.
BFGPR0113W
Successfully registered with ARM for ELEMTYPE: <insert_0>, ELEMENT: <insert_1>. Service was restarted (reason code: <insert_2>)
Severity
10 : Warning
Explanation
The service has successfully registered with ARM after a restart.
Response
None.
BFGPR0114E
Registering with ARM for ELEMTYPE: <insert_0>, ELEMENT: <insert_1> failed with return code: <insert_2> and reason code: <insert_3>
Severity
20 : Error
Explanation
The service failed to register with ARM for the reason given.
Response
Look up the return code and reason code in the MVS Programming Sysplex Services Reference, in the IXCARM section, to understand the reason for the error. Correct the problem and submit the job again.
BFGPR0115I
Successfully registered with ARM for ELEMTYPE: <insert_0>, ELEMENT: <insert_1>
Severity
0 : Information
Explanation
The service has successfully registered with ARM. Note that the service will wait for any predecessors configured in the ARM policy, such as a queue manager, before continuing with startup.
Response
No action required.
BFGPR0116E
Not registered with ARM.
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.
BFGPR0117W
Wait for predecessor for ELEMTYPE: <insert_0>, ELEMENT: <insert_1> returned warning reason code: <insert_2>
Severity
10 : Warning
Explanation
The wait for a predecessor, defined in the ARM policy, returned with a warning.
Response
Look up the reason code in the MVS Programming Sysplex Services Reference, in the IXCARM section, to understand the reason for the warning.
BFGPR0118E
Wait for predecessor for ELEMTYPE: <insert_0>, ELEMENT: <insert_1> failed with return code: <insert_2> and reason code: <insert_3>
Severity
20 : Error
Explanation
The wait for a predecessor, defined in the ARM policy, failed for the reason given.
Response
Look up the return code and reason code in the MVS Programming Sysplex Services Reference, in the IXCARM section, to understand the reason for the error. If required, correct the problem and restart the job.
BFGPR0119E
Already declared the ready state to ARM.
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.
BFGPR0120W
Indicating ready to ARM for ELEMTYPE: <insert_0>, ELEMENT: <insert_1> returned warning reason code: <insert_2>
Severity
10 : Warning
Explanation
The indication of the ready state to ARM returned with a warning.
Response
Look up the reason code in the MVS Programming Sysplex Services Reference, in the IXCARM section, to understand the reason for the warning.
BFGPR0121E
Indicating ready to ARM for ELEMTYPE: <insert_0>, ELEMENT: <insert_1> failed with return code: <insert_2> and reason code: <insert_3>
Severity
20 : Error
Explanation
The indication of the ready state to ARM failed for the reason given.
Response
Look up the return code and reason code in the MVS Programming Sysplex Services Reference, in the IXCARM section, to understand the reason for the error. If required, correct the problem and restart the job.
BFGPR0122W
Deregistering from ARM for ELEMTYPE: <insert_0>, ELEMENT: <insert_1> returned warning reason code: <insert_2>
Severity
10 : Warning
Explanation
Deregistering from ARM returned with a warning.
Response
Look up the reason code in the MVS Programming Sysplex Services Reference, in the IXCARM section, to understand the reason for the warning.
BFGPR0123E
Deregistering from ARM for ELEMTYPE: <insert_0>, ELEMENT: <insert_1> failed with return code: <insert_2> and reason code: <insert_3>
Severity
20 : Error
Explanation
Deregistering from ARM failed for the reason given.
Response
Look up the return code and reason code in the MVS Programming Sysplex Services Reference, in the IXCARM section, to understand the reason for the error. If required, correct the problem.
BFGPR0124I
Successfully deregistered from ARM.
Severity
0 : Information
Explanation
The service has successfully deregistered from ARM.
Response
No action required.
BFGPR0125E
The program is not registered with ARM.
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.
BFGPR0126E
Internal error: The credential user ID/password facilities have not been initialized before first use. Attempted to read user ID/password for queue manager <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.
BFGPR0127W
No credentials file has been specified to connect to IBM MQ. Therefore, the assumption is that IBM MQ authentication has been disabled.
Severity
10 : Warning
Explanation
For IBM MQ V8, the default mode is that connection authentication is enabled, unless upgraded. MFT is required to supply authentication credentials. However, this agent's credentials are missing or have not been defined. As a result the agent will assume that IBM MQ connection authentication has been disabled.
Response
Review the product documentation regarding MFT supplying credentials for MQ authentication.
BFGPR0128E
Internal error: An Xpath exception occurred while handling the MQ credentials. Reason: <insert_0>
Severity
20 : Error
Explanation
This exception is unexpected. The cause is not immediately known.
Response
If the problem persists, see problem determination information in the product documentation.
BFGPR0129E
Internal error: An Xpath exception occurred while generating the objects for MQ credentials. Reason: <insert_0>
Severity
20 : Error
Explanation
This exception is unexpected. The cause is not immediately known.
Response
If the problem persists, see problem determination information in the product documentation.
BFGPR0130E
Internal error: Unable to obfuscate the user ID and password. Reason: <insert_0>
Severity
20 : Error
Explanation
This exception is unexpected. The cause is not immediately known.
Response
If the problem persists, see problem determination information in the product documentation.
BFGPR0131E
Internal error: Unable to obfuscate the user ID and password. Reason: <insert_0>
Severity
20 : Error
Explanation
This exception is unexpected. The cause is not immediately known.
Response
If the problem persists, see problem determination information in the product documentation.
BFGPR0132E
An internal error has occurred. An Xpath exception has been detected. The exception is <insert_0>
Severity
20 : Error
Explanation
This exception is unexpected. The cause is not immediately known.
Response
If the problem persists, see problem determination information in the product documentation.
BFGPR0133E
An attempt to connect to queue manager <insert_0> has been rejected because of invalid authentication details. If this queue manager has authentication enabled, user ID and password details must be supplied.
Severity
20 : Error
Explanation
The attempted connection to the queue manager has failed with an MQRC 2035. This indicates the connection has been rejected because of invalid authentication details and the command cannot be completed.
Response
Check the required authentication for connection to this queue manager before attempting this command again. Refer to the IBM MQ product documentation for more information on this subject.
BFGPR0134E
The credentials file path <insert_0> cannot be a relative path.
Severity
20 : Error
Explanation
The defined path to the credentials file is not complete because the path does not reference the file from root.
Response
Review the credentials file property and supply its full absolute path before trying again.
BFGPR0135W
The value for property ''<insert_0>'' has been altered from ''<insert_1>'' to ''<insert_2>'' because it contained invalid characters for XML conversion.
Severity
10 : Warning
Explanation
The value for this property needed to be XML 1.0 encoded, and contained characters which are not valid in XML 1.0. These characters were therefore removed to allow XML encoding.
Response
Refer to the XML 1.0 specification to determine the acceptable range of characters which can be used, then alter within the MFT configuration file the property stated in the message above to avoid the need for incompatible characters.
BFGPR0136E
Internal error: ''<insert_0>'' is not valid for productId.
Severity
20 : Error
Explanation
An internal error has occurred attempting while attempting to register for SCRT usage recording.
Response
If the problem persists, see problem determination information in the product documentation.
BFGPR0137I
Product usage data recording started for product ''<insert_0>'', product id ''<insert_1>''.
Severity
0 : Information
Explanation
IBM MQ usage recording will be for product ''{0}''.
Response
No user action required.
BFGPR0138W
Product usage data already being recorded for product ''<insert_0>'', product id ''<insert_1>''.
Severity
10 : Warning
Explanation
The product attempted to start product usage data recording for product ''{0}'', but it was already started. This may not be a problem.
Response
No user action required if there are no other issues with usage data recording.
BFGPR0139E
Internal error: Product usage data cannot be recorded for product ''<insert_0>'', product id ''<insert_1>'' because the limit on product registrations has been reached for the address space.
Severity
20 : Error
Explanation
The product attempted to start product usage data recording for product ''{0}'', product id ''{1}'', which failed.
Response
CMSG002
BFGPR0140I
Product usage data is not being recording for product ''<insert_0>'', product id ''<insert_1>''.
Severity
0 : Information
Explanation
IBM MQ usage recording will not be collected for product ''{0}''. Thismay be because usage recording is not active on the system.
Response
No user action required.
BFGPR9999E
<insert_0>
Severity
20 : Error
Explanation
If this message does not give enough information, check the accompanying error messages for further information.
Response
For further information on resolving this error, see the problem determination information on the product Web site.