I am not sure how to fix this situation. I would need to poke at it a bit myself and perhaps try to figure how it occurred. Perhaps AUDIT MEDIACONTROLS VOLUME(migvol). If it was mine, I would hope it wasn't important and that I could make every effort to whack gone. If it was important, I would likely open a PMR (SR nowdays). If I couldn't successfully whack it, then that would also require IBM help and a SR/PMR
> -----Original Message----- > From: Willie Bunter [mailto:[email protected]] > Sent: Friday, August 08, 2014 9:34 AM > To: Gibney, Dave > Subject: Re: DFHSM QUESTION - FINDING HSM RECORD TYPE. > > Dave, > > The manual doesn't give a solutio for err 140: > > AUDIT may recommend an additional diagnostic step for error messages > (*ERR) > 140 and 148. If you want AUDIT to continue its attempt to identify a repair > action, you must specify an additional AUDIT command using the > recommended parameter > > *ERR 140 migvol - cdddsn HAS NO ALIAS RECORD For migration volume > migvol, no MCDS alias entry (A) record exists for one of the following > conditions: > v Data set name userdsn in the VTOC > has the form of a > DFSMShsm-generated migration > copy name. > v Data set name cdddsn, in what > appears to be a common data set > descriptor (CDD) record, indicates a > migration copy. (The catalog entry > for cdddsn indicates volume serial > MIGRAT; an MCDS data set (D) > record for cdddsn refers to an alias > (A) record for the migration copy.) > > In the Audit Repair Action it says the following An alias (A) record is > created, > referring to this migration copy. > * > I am not sure how I should go about creating the (A) record. Would you > suggest how I could go about it? > > Thanks. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
