| Explanation | The version directory is located according to the ""was.version.dir"" Java system property, or as ""<root>\properties\version"", where <root> is a directory from the ""was.install.root"" Java system property. The error indicates that ""was.install.root"" Java system property is not set, with the consequence that the version directory cannot be determined. |
| Action | Verify that the ""was.install.root"" Java system property is set. The Java system property must be set either through process configuration or as an option to a process that is launched from the command line. |
| Explanation | When loading product version information, this information is stored in files having specific extensions. The extensions determine the type of information stored in each file. Valid extensions are "".websphere"", "".component"", "".product"", "".ptf"", and "".extension"". An attempt was made to load a file containing version information where the extension of the file is not one of the valid extensions. |
| Action | This indicates an internal error. |
| Explanation | This informational message describes the options to the versionInfo utility program. The versionInfo utility program accepts optional keyword options, one which specifies the output format, one which specifies an output file, one which causes fixpacks to be displayed, one which causes fixpack detail to be displayed, one which causes ifixes to be displayed, one which causes ifix detail to be displayed, one which causes fixpacks and ifixes to be displayed (-maintenancePackages argument is deprecated), one which causes fixpack and ifix detail to be displayed (-maintenancePackageDetail argument is deprecated), one which is a no operation argument (-components argument is deprecated), one which is a no operation argument (-componentDetail argument is deprecated), and one which is used to display usage information. |
| Action | No user action is required. The usage information message is displayed upon request. |
| Explanation | The specified error occurred while writing out a version report to the specified file. |
| Action | Corrective action depends on the specifics of the error which occurred. In particular, make sure that the specified file is writable and that sufficient space is available for the report. |
| Explanation | The listed option requires an value. (Use ""-help"" or ""-usage"" to display usage information.) |
| Action | Specify a value for the listed option. |
| Explanation | The valid format values are ""text"" and ""html"". The value specified is not one of these values. (Use ""-help"" or ""-usage"" to display usage information.) |
| Action | Change the format value to one of the valid values, ""text"" or ""html"". |
| Explanation | The specified option is not valid. (Use ""-help"" or ""-usage"" to display usage information.) |
| Action | Change to use a valid option. |
| Explanation | The message describes the valid options to the versionInfo utility program. |
| Action | No user action is required. The usage information message is displayed upon request. |
| Explanation | An error occurred while writing out a version report to the specified file. A second error occurred while retrieving the text of the error. |
| Action | No user action is available. Retry the requested operation, or contact support for further assistance. |
| Explanation | This is a standard copyright statement. |
| Action | No user action is required. This is an informational message. |
| Explanation | This is a standard module description statement. |
| Action | No user action is required. This is an informational message. |
| Explanation | Refer to the nested exception details for further information. |
| Action | Refer to the nested exception details for further information. |
| Explanation | Refer to the nested exception details for further information. |
| Action | Refer to the nested exception details for further information. |
| Explanation | Refer to the nested exception details for further information. |
| Action | Refer to the nested exception details for further information. |
| Explanation | Refer to the nested exception details for further information. |
| Action | Refer to the nested exception details for further information. |
| Explanation | The logs directory is located according to the java system property ""was.version.log.dir"", or as the ""log"" directory of the version directory. Neither the ""was.version.log.dir"" property nor the version directory is set. |
| Action | Ensure that the version directory is set, or set the java system property ""was.version.log.dir"". |
| Explanation | The backups directory is located according to the java system property ""was.version.backup.dir"", or as the ""backup"" directory of the version directory. Neither the ""was.version.backup.dir"" property nor the version directory is set. |
| Action | Ensure that the version directory is set, or set the java system property ""was.version.backup.dir"". |
| Explanation | The DTD directory is located according to the java system property ""was.version.dtd.dir"", or as the ""dtd"" directory of the version directory. Neither the ""was.version.dtd.dir"" property nor the version directory is set. |
| Action | Ensure that the version directory is set, or set the java system property ""was.version.dtd.dir"". |
| Explanation | The errors, a list of which follows, occurred while parsing fix information. Refer to the listed errors for additional information. |
| Action | Refer to the listed errors for suggested user actions. |
| Explanation | The specified entity has structure which is not valid, as described by the specified error. However, the unrecoverable error disrupted the operation and the parsing continued. |
| Action | The specified file should be reviewed and, if possible, corrected. |
| Explanation | The warnings, a list of which follows, occurred while parsing product information. Refer to the listed warnings for additional information. |
| Action | Refer to the listed warnings for suggested user actions. |
| Explanation | The specified entity has structure which is not valid, as described by the specified warning. However, the unrecoverable error disrupted the operation and the parsing continued. |
| Action | The specified file should be reviewed and, if possible, corrected. |
| Explanation | The named file could not be removed. |
| Action | Ensure that the target file can be removed. |
| Explanation | The errors, a list of which follows, occurred while parsing maintenance package information. Refer to the listed errors for additional information. |
| Action | Refer to the listed errors for suggested user actions. |
| Explanation | The named file could not be saved. |
| Action | Ensure that the target file is writable, and that space is available for a new file. |
| Explanation | The named file could not be removed. |
| Action | Ensure that the target file can be removed. |
| Explanation | The version directory does not exist. |
| Action | Ensure that the specified directory is a valid product version directory. |
| Explanation | The version directory is not a directory. |
| Action | Ensure that the specified directory is a valid product version directory. |
| Explanation | The DTD directory does not exist. |
| Action | Ensure that the specified directory is a valid product DTD directory. |
| Explanation | The DTD directory is not a directory. |
| Action | Ensure that the specified directory is a valid product DTD directory. |
| Explanation | The log directory could not be created. |
| Action | Ensure that the specified directory is a valid product log directory. |
| Explanation | The log directory is not a directory. |
| Action | Ensure that the specified directory is a valid product log directory. |
| Explanation | The backup directory could not be created. |
| Action | Ensure that the specified directory is a valid product backup directory. |
| Explanation | The backup directory is not a directory. |
| Action | Ensure that the specified directory is a valid product backup directory. |
| Explanation | The product directory does not exist. |
| Action | Ensure that the product directory is a valid product directory. |
| Explanation | The product directory is not a directory. |
| Action | Ensure that the specified directory is a valid product directory. |
| Explanation | The specified document cannot be loaded |
| Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: https://ibm.biz/BdztgV WebSphere Application Server for z/OS Support page: https://ibm.biz/Bdqd4J . |
| Explanation | The exception caused the loading of the specified document to fail. |
| Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: https://ibm.biz/BdztgV WebSphere Application Server for z/OS Support page: https://ibm.biz/Bdqd4J . |
| Explanation | A root document element cannot be created. |
| Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: https://ibm.biz/BdztgV WebSphere Application Server for z/OS Support page: https://ibm.biz/Bdqd4J . |
| Explanation | An XML model object cannot be created. |
| Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: https://ibm.biz/BdztgV WebSphere Application Server for z/OS Support page: https://ibm.biz/Bdqd4J . |
| Explanation | This is an internal error. |
| Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: https://ibm.biz/BdztgV WebSphere Application Server for z/OS Support page: https://ibm.biz/Bdqd4J . |
| Explanation | The version information cannot be written to the specified file. |
| Action | Verify that you can write to the specified file and that sufficient space is available for the file. |
| Explanation | The noted DTD cannot be resolved while parsing product information. |
| Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: https://ibm.biz/BdztgV WebSphere Application Server for z/OS Support page: https://ibm.biz/Bdqd4J . |
| Explanation | The history directory is a subdirectory of the product directory. The Application Server cannot determine the history directory location. |
| Action | For more information, see the associated version error. |
| Explanation | The Application Server cannot load the history information from the history file. |
| Action | Verify that the Application Server can read the history file. Also, verify that the file uses the correct format. |
| Explanation | The Application Server cannot read the file. |
| Action | For more information, see the nested or associated error messages. |
| Explanation | The Application Server cannot create the history directory. |
| Action | For more information, see the nested or associated error messages. |
| Explanation | The Application Server cannot create backup files for the history files. |
| Action | For more information, see the nested or associated error messages. |
| Explanation | The Application Server cannot write the event history file. |
| Action | For more information, see the nested or associated error messages. |
| Explanation | This statement is a standard copyright statement. |
| Action | No action is required. |
| Explanation | This statement is a standard module description statement. |
| Action | No action is required. |
| Explanation | The listed argument requires a value. Use the -help or -usage argument to display the usage information. |
| Action | Specify a value for the listed argument. |
| Explanation | The valid format values are text and html. The specified value is not in a valid format. Use the -help or -usage argument to display the usage information. |
| Action | Change the format value to either text or html. |
| Explanation | The specified argument is not valid. Use the -help or -usage argument to display the usage information. |
| Action | Change the argument to a valid argument. |
| Explanation | This informational message describes the arguments for the historyInfo utility program. The historyInfo utility program accepts the following optional keyword arguments: \ An argument that specifies the output format \ An argument that specifies an output file \ An argument that displays the events that are associated with a specified offering only (-maintenancePackageId is deprecated) \ An argument that is deprecated \ An argument that displays usage information \ Use the -usage or -help argument to display additional information. |
| Action | No action is required. The usage information message displays upon request. |
| Explanation | The message describes the valid arguments to the historyInfo utility program. |
| Action | No action is required. The usage information message displays upon request. |
| Explanation | The Application Server cannot write the history report to the specified file. |
| Action | Verify that the Application Server can write to the specified file. Also verify that sufficient space is available for the report. |
| Explanation | The Application Server cannot write the history report to the specified file. When the Application Server attempted to retrieve the text of the second error, another exception occurred. |
| Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: https://ibm.biz/BdztgV WebSphere Application Server for z/OS Support page: https://ibm.biz/Bdqd4J . |
| Explanation | The Application Server cannot process the history information. |
| Action | For more information, see the nested or associated error messages. |
| Explanation | The Application Server cannot process the history information. |
| Action | For more information, see the nested or associated error messages. |
| Explanation | The Application Server cannot save the specified file. |
| Action | Verify that Application Server can write to the specified file. Also, verify that space is available for a new file. |
| Explanation | The Application Server cannot save the specified file. |
| Action | Verify that Application Server can write to the specified file. Also, verify that space is available for a new file. |
| Explanation | The Application Server cannot remove the specified file. |
| Action | Verify that the Application Server can remove the specified file. |
| Explanation | The component cannot find a record of an application for the specified fix. The product information might be corrupted or an internal error might have occurred. |
| Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: https://ibm.biz/BdztgV WebSphere Application Server for z/OS Support page: https://ibm.biz/Bdqd4J . |
| Explanation | The Application Server cannot remove the specified file. |
| Action | Verify that the Application Server can remove the target file. |
| Explanation | The Application Server cannot parse the maintenance package information and several errors occurred. |
| Action | For more information, see the nested or associated error messages. |
| Explanation | The Application Server cannot save the specified file. |
| Action | Verify that Application Server can write to the specified file. Also, verify that space is available for a new file. |
| Explanation | The Application Server cannot create or remove the specified file. |
| Action | Verify that Application Server can write to or remove the specified file. Also, verify that space is available for a new file if applicable. |
| Explanation | The component does not have a record of applying the specified maintenance package. The product information might be corrupted or an internal error might have occurred. |
| Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: https://ibm.biz/BdztgV WebSphere Application Server for z/OS Support page: https://ibm.biz/Bdqd4J . |
| Explanation | The Application Server cannot remove the specified file. |
| Action | Verify that the Application Server can remove the target file. |
| Explanation | The history information is stored in files that have specific file name extensions. The extension names determine the type of information that is stored in each file. Valid extension names are .ptfDriver, and .ptfApplied. An attempt has been made to load a file that contains version information. However, the file name extension is not one of the valid extension names. |
| Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: https://ibm.biz/BdztgV WebSphere Application Server for z/OS Support page: https://ibm.biz/Bdqd4J . |
| Explanation | he Application Server cannot read the file. |
| Action | For more information, see the nested or associated error messages. |