Brian, I tried your suggestion unfortunately it didn't get rid of the ERR 40. Here is the message that was sent to my terminal:
ARC0085I (H)BDELETE REQUIRES ONE OF THE FOLLOWING MUTUALLY EXCLUSIVE KEYWORDS: ARC0085I (CONT.) ALL, VERSIONS, OR DATE ARC0085I (H)BDELETE REQUIRES ONE OF THE FOLLOWING MUTUALLY EXCLUSIVE KEYWORDS: ARC0085I (CONT.) ALL, VERSIONS, OR DATE ARC0085I (H)BDELETE REQUIRES ONE OF THE FOLLOWING MUTUALLY EXCLUSIVE KEYWORDS: ARC0085I (CONT.) ALL, VERSIONS, OR DATE ARC0085I (H)BDELETE REQUIRES ONE OF THE FOLLOWING MUTUALLY EXCLUSIVE KEYWORDS: ARC0085I (CONT.) ALL, VERSIONS, OR DATE ARC0085I (H)BDELETE REQUIRES ONE OF THE FOLLOWING MUTUALLY EXCLUSIVE KEYWORDS: ARC0085I (CONT.) ALL, VERSIONS, OR DATE ARC0085I (H)BDELETE REQUIRES ONE OF THE FOLLOWING MUTUALLY EXCLUSIVE KEYWORDS: ARC0085I (CONT.) ALL, VERSIONS, OR DATE ARC0085I (H)BDELETE REQUIRES ONE OF THE FOLLOWING MUTUALLY EXCLUSIVE KEYWORDS: ARC0085I (CONT.) ALL, VERSIONS, OR DATE ARC0085I (H)BDELETE REQUIRES ONE OF THE FOLLOWING MUTUALLY EXCLUSIVE KEYWORDS: ARC0085I (CONT.) ALL, VERSIONS, OR DATE ARC0085I (H)BDELETE REQUIRES ONE OF THE FOLLOWING MUTUALLY EXCLUSIVE KEYWORDS: ARC0085I (CONT.) ALL, VERSIONS, OR DATE Below is a sample of the output. /* 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'4040404040404040404040404040404040404040404040404040404040404040404040404040404040404040') /* FIXCDS B DUMMY.RECOVER.MCB PATCH(X'00000050' HSMBACK.BACK.T592617.DB2.ARCHLOG2.I8257) /* FIXCDS B DUMMY.RECOVER.MCB PATCH(X'00000082' BITS(01000010)) /* BDELETE DUMMY.RECOVER.MCB /* MSG 914 - ERROR ON BDELETE COMMAND /* MSG 998 - AUDIT CONTINUING, SEE COMMAND ACTIVITY LOG /* FIXCDS B DUMMY.RECOVER.MCB DELETE - END OF - ENHANCED AUDIT - LISTING - -------------------------------------------- On Thu, 7/27/17, Brian Fraser <[email protected]> wrote: Subject: Re: DFHSM QUESTION To: [email protected] Received: Thursday, July 27, 2017, 9:18 PM HSEND AUDIT DSCTL(BACKUP) FIX ODS('dsn.for.output.listing') is what you should run. On Fri, Jul 28, 2017 at 2:56 AM, Horne, Patti <[email protected]> wrote: > You ran the fix on the BDELETE not the AUDIT. > > > > > -----Original Message----- > From: IBM Mainframe Discussion List [mailto:[email protected]] On > Behalf Of willie bunter > Sent: Thursday, July 27, 2017 11:23 AM > To: [email protected] > Subject: Re: DFHSM QUESTION > > I ran the FIX and the following messages were received : > > ARC0085I (H)BDELETE REQUIRES ONE OF THE FOLLOWING MUTUALLY EXCLUSIVE > KEYWORDS: > ARC0085I (CONT.) ALL, VERSIONS, OR DATE > ARC0085I (H)BDELETE REQUIRES ONE OF THE FOLLOWING MUTUALLY EXCLUSIVE > KEYWORDS: > ARC0085I (CONT.) ALL, VERSIONS, OR DATE > ARC0085I (H)BDELETE REQUIRES ONE OF THE FOLLOWING MUTUALLY EXCLUSIVE > KEYWORDS: > ARC0085I (CONT.) ALL, VERSIONS, OR DATE > ARC0085I (H)BDELETE REQUIRES ONE OF THE FOLLOWING MUTUALLY EXCLUSIVE > KEYWORDS: > ARC0085I (CONT.) ALL, VERSIONS, OR DATE > ARC0085I (H)BDELETE REQUIRES ONE OF THE FOLLOWING MUTUALLY EXCLUSIVE > KEYWORDS: > ARC0085I (CONT.) ALL, VERSIONS, OR DATE > ARC0085I (H)BDELETE REQUIRES ONE OF THE FOLLOWING MUTUALLY EXCLUSIVE > KEYWORDS: > ARC0085I (CONT.) ALL, VERSIONS, OR DATE > ARC0085I (H)BDELETE REQUIRES ONE OF THE FOLLOWING MUTUALLY EXCLUSIVE > KEYWORDS: > ARC0085I (CONT.) ALL, VERSIONS, OR DATE > ARC0085I (H)BDELETE REQUIRES ONE OF THE FOLLOWING MUTUALLY EXCLUSIVE > KEYWORDS: > ARC0085I (CONT.) ALL, VERSIONS, OR DATE > > Below is my command > HSEND AUDIT DATASETCONTROLS(BACKUP) FIX - > ODS(SYS2.AUDIT.DATASET.CONTROLS.BCDS.FIX.#2) > -------------------------------------------- > On Thu, 7/27/17, Horne, Patti <[email protected]> wrote: > > Subject: Re: DFHSM QUESTION > To: [email protected] > Received: Thursday, July 27, 2017, 11:42 AM > > Try using FIX on your audit to > see if it cleans up the error. > > > > -----Original > Message----- > From: IBM Mainframe Discussion > List [mailto:[email protected]] > On Behalf Of willie bunter > Sent: Thursday, > July 27, 2017 10:36 AM > To: [email protected] > Subject: Re: DFHSM QUESTION > > Lizette, > > > The reason why I think that it is a problem because after I run the > AUDIT using NOFIX the output shows the dsn (*err 40). I do not see this > for other LPARS. > My > understanding is that if any errors appear a clean up is needed to be > initiated. In this case only ERR 40 appears. > -------------------------------------------- > > On Thu, 7/27/17, Lizette > Koehler <[email protected]> > wrote: > > Subject: Re: DFHSM > QUESTION > To: [email protected] > Received: Thursday, July 27, 2017, 10:22 AM > > That does not seem to be a > failure. > > It > just states the > record you tried to delete > no longer exists in HSM. Once the record is deleted, it cannot be > deleted again. > > > Why do you think this is a > failure? > > The message > > ARC0195I is all you need to focus on. The ARC1001 or ARC1615I just > states the command could not do any work. > > > > > Lizette > > > > > > -----Original Message----- > > From: > IBM > Mainframe Discussion List [mailto:[email protected]] On > > Behalf Of willie bunter > Sent: Thursday, July 27, 2017 6:32 AM > To: > [email protected] > Subject: Re: DFHSM QUESTION > > Brian, > > > I tried that out however it didn't work (record not found). Below is > the > output: > > > > ARC0195I TYPE B, > KEY > DB2.ARCHLOG2.A0091613, FIXCDS DELETE, > ERROR=RECORD NOT > ARC0195I (CONT.) FOUND > ARC1001I FIXCDS B > DB2.ARCHLOG2.A0091613 DELETE COMMAND FAILED, RC=0015, > ARC1001I > (CONT.) REAS=0000 > ARC1615I FIXCDS COMMAND REJECTED > > > -------------------------------------------- > > On Wed, 7/26/17, Brian Fraser <[email protected]> > wrote: > > > > > Subject: > Re: DFHSM QUESTION > > To: [email protected] > > Received: Wednesday, July 26, 2017, > 9:23 PM > > If you just want to get rid of > the backup, then you > can do the following. > > > > HSEND FIXCDS B > > > DB2.ARCHLOG2.A0091613 > *DELETE* > > > > > Regards > > Brian > > > > > On Thu, Jul 27, > 2017 at 1:30 > > AM, > retired mainframer > < > > > [email protected]> > > wrote: > > > > > Please show the > > > complete AUDIT and BDELETE commands you are using. > > > > > > > Did you look up ERR40 > > in the > "Error Codes and > Diagnosis" > section (section > 3 in my copy) of the > "Using the AUDIT Command" > chapter > (my chapter 67)? > > > The > table (51) identifies several > > > > possible causes and corrective > actions. > > > > > > BDELETE is > the proper action for > only one of the causes. > > > > > > > > > -----Original > > Message----- > > > > From: IBM Mainframe > > Discussion List [mailto:[email protected]] On > > Behalf Of > willie > bunter > > > Sent: Wednesday, July 26, 2017 7:27 AM > > To: > IBM- > [email protected] > > > Subject: DFHSM QUESTION > > > > > 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'404040404040404040404040404040404040404040404040404040404040 > > > 404040404040 > > > > > > > > > 404 > > > > > > 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. > > > > > > > > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, send > email to [email protected] with the message: INFO IBM-MAIN > > ---------------------------------------------------------------------- > 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 proprietary and/or confidential. > If you are not the intended recipient, please: > (i) delete the message and all copies; (ii) do not disclose, distribute > or use the message in any manner; and (iii) notify the sender immediately. > In addition, please be aware that any message addressed to our domain is > subject to archiving and review by persons other than the intended > recipient. Thank you. > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, send > email to [email protected] with the message: INFO IBM-MAIN > > > ---------------------------------------------------------------------- > 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 proprietary and/or > confidential. If you are not the intended recipient, please: (i) delete the > message and all copies; (ii) do not disclose, distribute or use the message > in any manner; and (iii) notify the sender immediately. In addition, please > be aware that any message addressed to our domain is subject to archiving > and review by persons other than the intended recipient. Thank you. > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to [email protected] with the message: INFO IBM-MAIN > ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
