|
|
|
Reason:
The checkpoint file was incorrectly identified on a MIMINIT CHKPTDSN statement in the startup procedure, or this checkpoint file was moved or deleted.
Action:
Examine the MIMINIT CHKPTDSN statements to verify that the correct data set name prefix was specified. If not, then correct the entry. Also, check system catalog information to see if the checkpoint file is on the correct DASD device.
| Copyright © 2011 CA. All rights reserved. | Tell Technical Publications how we can improve this information |