I would suggest if you are running in batch, you may see successful. But I would check the DFHSM Started task for error messages.
That you still see the entry seems to indicate that it was not successful. Please check the syntax of your BDELETE Command. https://www.ibm.com/support/knowledgecenter/SSLTBW_2.1.0/com.ibm.zos.v2r1.arcf000/s4118.htm I suggest you do the following HLIST DSN(your dataset name) BCDS See if you have more than one GEN for the backup. Next review the HSM Command manual for BDELETE and make sure you are entering the command correctly. Lastly, provide all commands and message (full details, mask company proprietary data) There are some functions that will return a OK to a command, but it does not mean that command was successful Lizette > -----Original Message----- > From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On > Behalf Of willie bunter > Sent: Wednesday, July 26, 2017 7:30 AM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: Re: DFHSM QUESTION - REPOST > > I am reposting my question because some info was truncated. > > I ran an AUDIT of the BCDS. I was 99% successfull of performing a clean up > execept for the following type dsns: > ERR 40 DB2.ARCHLOG2.A0091613 HSMBACK.BACK.T592617.DB2.ARCHLOG2.I8257 MISSING > B RECORD > FIXCDS B DUMMY.RECOVER.MCB CREATE(X'00000014' X'0098257F') > FIXCDS B DUMMY.RECOVER.MCB PATCH(X'0000002E' BITS(1.1.....)) > FIXCDS B DUMMY.RECOVER.MCB PATCH(X'00000030' X'000100010001') > FIXCDS B DUMMY.RECOVER.MCB EXPAND(X'00000040') > FIXCDS B DUMMY.RECOVER.MCB PATCH(X'00000050' + > > X'404040404040404040404040404040404040404040404040404040404040404040404040404 > FIXCDS B DUMMY.RECOVER.MCB PATCH(X'00000050' > HSMBACK.BACK.T592617.DB2.ARCHLOG > FIXCDS B DUMMY.RECOVER.MCB PATCH(X'00000082' BITS(01000010)) > BDELETE DUMMY.RECOVER.MCB > FIXCDS B DUMMY.RECOVER.MCB DELETE > END OF - ENHANCED AUDIT - LISTING - > > I tried a HSEND BDELETE 'DB2.ARCHLOG2.A0091613' ALL . The command which I > ran in batch was successful however when I ran another AUDIT the entry > appears. I tried a HSEND FIXCDS B DB2.ARCHLOG2.A0091613. Again the command > was successful, however the AUDIT says otherwise. > > Anything else I could try? > > -------------------------------------------- > On Wed, 7/26/17, willie bunter <0000001409bd2345-dmarc- > requ...@listserv.ua.edu> wrote: > > Subject: DFHSM QUESTION > To: IBM-MAIN@LISTSERV.UA.EDU > Received: Wednesday, July 26, 2017, 10:26 AM > > Good Day, > > I ran an AUDIT of the BCDS. I was > 99% successfull of performing a clean up execept for the following type > dsns: > ERR 40 DB2.ARCHLOG2.A0091613 > HSMBACK.BACK.T592617.DB2.ARCHLOG2.I8257 MISSING > FIXCDS B DUMMY.RECOVER.MCB > CREATE(X'00000014' X'0098257F') > > FIXCDS B DUMMY.RECOVER.MCB > PATCH(X'0000002E' BITS(1.1.....)) > > FIXCDS B DUMMY.RECOVER.MCB > PATCH(X'00000030' X'000100010001') > > FIXCDS B DUMMY.RECOVER.MCB > EXPAND(X'00000040') > > > FIXCDS B DUMMY.RECOVER.MCB > PATCH(X'00000050' + > > > > > X'404040404040404040404040404040404040404040404040404040404040404040404040404 > FIXCDS B DUMMY.RECOVER.MCB > PATCH(X'00000050' HSMBACK.BACK.T592617.DB2.ARCHLOG > FIXCDS B DUMMY.RECOVER.MCB > PATCH(X'00000082' BITS(01000010)) > > BDELETE DUMMY.RECOVER.MCB > > > > FIXCDS B DUMMY.RECOVER.MCB > DELETE > > > END OF - ENHANCED AUDIT - > LISTING - > > > > I tried a HSEND BDELETE > 'DB2.ARCHLOG2.A0091613' ALL . The command which I ran in batch was > successful however when I ran another AUDIT the entry appears. I tried a > HSEND FIXCDS B DB2.ARCHLOG2.A0091613. Again the command was successful, > however the AUDIT says otherwise. > > Anything else I could try? ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
