For the ERR03, I've used the following;
HSEND DELETE 'AOSYS.OPS.GLBLVAR.BKUPS.NWKC.G0068V00'
This is some documentation I picked up along the way for the ERR20:
THE ERR 20 MESSAGES INDICATE THERE IS A MCD RECORD BUT THE
CORRESPONDING MCV RECORD IS NOT FOUND. TO CLEAN THIS UP, YOU WILL DO
THE FOLLOWING:
ISSUE THE
FIXCDS D DSN DISPLAY
AT OFFSET X'9C', IT SHOULD SHOW YOU THE ALIAS NAME OF THE DATASET.
(ALIAS.DSN AS BELOW).
(MY NOTE: THIS IS THE 'DFHSM.HMIG.T281204.??????.????.J7156' NAME
THEN ISSUE:
FIXCDS A ALIAS.DSN DELETE
FIXCDS D DSN DELETE
THESE COMMANDS WILL TAKE CARE OF THE MCD AND MCA RECORDS.
YOU WILL ALSO NEED TO DELETE THE CATALOG ENTRY IF IT EXISTS.
IDCAMS DELETE DSNAME NOSCR SHOULD BE USED.
I wouldn't be afraid to follow these steps again for these errors, but all
the usual disclaimer stuff goes here.
ddk
Good Day Readers,
I am having a problem to find the record type of some dsns which do not
exist in the ICFCAT however they are in uncataloged status in HSM. I
stumbled upon 25 dsns while running AUDIT against the MCDS & BCDS.
Here is an example.
ERR 03 HESD.MAILRETN.WRKLIST.G0041V00 NOT CATALOGED, HAS MIGRATION COPY
EHSM.HMIG.T531718.HESD.MAILRETN.J0313
ERR 20 HESD.MAILRETN.WRKLIST.G0041V00 ON HSM005 BUT NO V RECORD
* ERR 20 CLAXMS.PUNCH.CARD2 ON HSM004, BUT NO V RECORD
* ERR 20 CLSGDM.SYSOUT2.DATA ON HSM004, BUT NO V RECORD
Please note that the volsers HSM004 & HSM005 do not exist.
I would like to delete these records but I am unable to do so because I do
not know the record type because FIXCDS needs the record type.
Thanks.
**********************************************************************
This e-mail message and all attachments transmitted with it may contain legally
privileged and/or confidential information intended solely for the use of the
addressee(s). If the reader of this message is not the intended recipient, you
are hereby notified that any reading, dissemination, distribution, copying,
forwarding or other use of this message or its attachments is strictly
prohibited. If you have received this message in error, please notify the
sender immediately and delete this message and all copies and backups thereof.
Thank you.
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
