Problem | The history directory is a subdirectory of the product directory. See the explanation for the error that occurred when determining the product directory for more information. |
User response | Follow the instructions that appear with the version error. |
Problem | History information could not be loaded from the history file {0}. Particular details are according to the error that occurred. |
User response | Verify that the history file is readable, and has a correct format. |
Problem | Refer to the nested exception details for further information. |
User response | Refer to the nested exception details for further information. |
Problem | Refer to the nested exception details for further information. |
User response | Refer to the nested exception details for further information. |
Problem | Refer to the nested exception details for further information. |
User response | Refer to the nested exception details for further information. |
Problem | Refer to the nested exception details for further information. |
User response | Refer to the nested exception details for further information. |
Problem | This is a standard copyright statement. |
User response | No action is required. |
Problem | This is a standard module description statement. |
User response | No action is required. |
Problem | The listed argument requires a value. (Use ''-help'' or ''-usage'' to display usage information.) |
User response | Specify a value for the listed argument. |
Problem | 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. |
User response | Change the format value to one of the valid values, ''text'' or ''html''. |
Problem | The specified argument is not valid. Use ''-help'' or ''-usage'' to display usage information. |
User response | Change the argument to a valid argument. |
Problem | This informational message describes the arguments to the historyInfo utility program. The historyInfo utility program accepts five optional keyword arguments: one that specifies the output format; one that specifies an output file; one that displays only those events associated with a specified maintenance package; one that displays only those events associated with a specified component; and one that is used to display usage information. Use ''-usage'' or ''-help'' to display additional information. |
User response | No action is required. The usage information message displays upon request. |
Problem | The message describes the valid arguments to the versionInfo utility program. |
User response | No action is required. The usage information message displays upon request. |
Problem | Corrective action depends on the specifics of the error that occurred. The specified error occurred while writing the history report to the specified file. |
User response | Verify that the specified file is writable and that sufficient space is available for the report. |
Problem | An error occurred while writing out a history report to the specified file. A second error occurred while retrieving the text of the error. |
User response | Retry the requested operation, or contact IBM WebSphere Application Server Support. Web page at http://www-3.ibm.com/software/webservers/appserv/support.html |
Problem | Refer to the nested exception details for further information. |
User response | Refer to the nested exception details for further information. |
Problem | Refer to the nested exception details for further information. |
User response | Refer to the nested exception details for further information. |
Problem | The named file could not be saved. |
User response | Verify that the target file is writable, and that space is available for a new file. |
Problem | The named file could not be saved. |
User response | Verify that the target file is writable, and that space is available for a new file. |
Problem | The named file could not be removed. |
User response | Verify that the target file can be removed. |
Problem | The component has no record of an application of the specified fix. The product information might be corrupt, or an internal error might have occurred. |
User response | Contact IBM WebSphere Application Server Support. Web page at http://www-3.ibm.com/software/webservers/appserv/support.html |
Problem | The named file could not be removed. |
User response | Verify that the target file can be removed. |
Problem | The errors, a list of which follows, occurred while parsing maintenance package information. |
User response | Refer to the listed errors for suggested user actions. |
Problem | The named file could not be saved. |
User response | Verify that the target file is writable, and that space is available for a new file. |
Problem | The named file could not be removed. |
User response | Verify that the target file can be removed. |
Problem | The component has no record of an application of the specified maintenance package. The product information might be corrupt, or an internal error might have occurred. |
User response | Contact IBM WebSphere Application Server Support. Web page at http://www-3.ibm.com/software/webservers/appserv/support.html |
Problem | The named file could not be removed. |
User response | Verify that the target file can be removed. |
Problem | History information is stored in files having specific extensions. The extensions determine the type of information stored in each file. Valid extensions are .ptfDriver, and .ptfApplied. An attempt was made to load a file containing version information where the extension of the file is not one of the valid extensions. |
User response | This error indicates an internal problem. |
Problem | Refer to the nested exception details for further information. |
User response | Refer to the nested exception details for further information. |