Willie, While I can't comment on what you need to do to actually fix the problem, I can comment on your confusion about the SDSP. The description in the storage mgmt manual (I have a slightly older revision of the book) for message 909 (you documented 908) says:
MSG 909 ERROR OPENING [DSN(datasetname) | SDSP FOR VOLUME(volser)] An error has been encountered during the OPENING of the data set indicated. The data set is on either the SDSP VOLUME indicated or the VOLUME indicated. So since your actual error is stating "error in opening DSN...", it is having trouble opening the dataset. No SDSP is involved. If the SDSP were there and involved, the error would state it was having trouble with the "SDSP for volume...". Since you can't find the actual dataset, I would interpret the MSG 909 as "DFHSM tried to open the DSN on this volume, but something is wrong so HSM threw an open error." Rex -----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of willie bunter Sent: Friday, August 15, 2014 8:35 AM To: [email protected] Subject: DFHSM QUESTION - UNABLE TO FIX MSG 909 - AUDIT Good Day All, AUDIT MEDIACONTROLS VOLUMES(MVSZ04) NOFIX. I received the following message : /* MSG 909 - ERROR IN OPENING DSN(DFHSM.HMIG.T182120.A4PROD.XPD2.A4226) VOLUME(MVSZ04) */ /* MSG 998 - AUDIT CONTINUING, COMMAND ACTIVITY LOG MAY CONTAIN ADDITIONAL INFORMATION */ I ran a FIXCDS A DFHSM.HMIG.T182120.A4PROD.XPD2.A4226 DISPLAY but HSM says that the file does not exist : ARC0195I TYPE A, KEY DFHSM.HMIG.T182120.A4PROD.XPD2.A4226, FIXCDS DISPLAY, ERROR I checked the error message in the manual DFSMShsm Storage Management SC35-0421-14 to perform the cleanup. According to IBM Speak all it says the following : MSG 908 ERROR CLOSING DSN(dsname) [VOLUME(volser) | SDSP FOR VOLUME(volser)]. Explanation: An error has been encountered during the closing of the data set dsname. The data set is on the volume volser. If my understanding of IBM Speak is correct the dsn shold be on the volume. However, I checked the volume via ISPF 3.4 but it is not there. Also, this volume is a NOSDSP contrary to the IBM explanation Could someone suggest what I should do to correct the error or it will mysteriously "go away"? Thanks. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN The information contained in this message is confidential, protected from disclosure and may be legally privileged. If the reader of this message is not the intended recipient or an employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any disclosure, distribution, copying, or any action taken or action omitted in reliance on it, is strictly prohibited and may be unlawful. If you have received this communication in error, please notify us immediately by replying to this message and destroy the material in its entirety, whether in electronic or hard copy format. Thank you. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
