Reason:
During the dump of a SYS1.MANx file, the named history file failed to close properly. The dump will ABEND U3001.
Action:
Examine the system console for messages detailing the specifics of the problem. Run TAPEINIT on the system on which the error occurred. Rerun the dump.
Reason:
An attempt to catalog a history file was unsuccessful, due to the fact that the data set name of the history file was already cataloged to a different volume than the one that was just written.
Action:
Examine the catalog entry for the history file on the original volume indicated in the "volser-1" field of the message. If the catalog entry is in error, recatalog the history file to the volume indicated in the "volser-2" field of the message. Note that the history file has been written successfully; the only issue with the history file is that the file has not been cataloged properly.
Reason:
Catalog Services issued a return code other than zero when CA SMF Director tried to catalog a history file.
Action:
Examine the return code and determine if the data set has been cataloged. If necessary, you may recatalog the data set. Note that the history file has been written successfully, and that the only issue with the history file is that the file has not been cataloged properly.
| Copyright © 2011 CA. All rights reserved. | Tell Technical Publications how we can improve this information |