Note the description in the manual for DFHSM AUDIT AUDIT usually identifies a repair (and takes repair action when FIX is specified) for error messages (*ERR) 30, 35, 36, 40, 41, 42, 43, 44, and 46. AUDIT recommends an additional diagnostic step for error messages (*ERR) 17 if the backup tape involved is a volume written in single file format. If you want AUDIT to continue its attempt to identify a repair action, you must specify an additional AUDIT command using the recommended parameter. For other reported conditions, see Error codes (*ERR) and diagnosis for some troubleshooting hints.
It usually does the repair. Which tells me sometimes it cannot. If you need to remove these errors, you may need to open an SR with IBM HSM Level two for further assistance. It could be that in all of the commands that have been entered, something may have been broken links in the xCDS Datasets. And IBM should be able to help you. Anything the list provides may cause further issues in your xCDS datasets. Lizette > -----Original Message----- > From: IBM Mainframe Discussion List [mailto:[email protected]] On > Behalf Of willie bunter > Sent: Friday, July 28, 2017 9:34 AM > To: [email protected] > Subject: Re: DFHSM QUESTION > > Lizette, > > I have taken note of your suggestion and I will adhere to it. > I checked my command and it shows that all the contents of the command is as > follows as suggested by Brian: HSEND AUDIT DSCTL(BACKUP) FIX. > > I didn't have BDELETE or anyother parm in the command. I am not sure why HSM > is complaining that the command contained these parms. > > -------------------------------------------- > On Fri, 7/28/17, Lizette Koehler <[email protected]> wrote: > > Subject: Re: DFHSM QUESTION > To: [email protected] > Received: Friday, July 28, 2017, 10:01 AM > > Willie > > It would be helpful to include just on > pair of COMMAND and RESPONSE rather than all of your error > messages. Without the context of what command syntax you entered, it is > difficult to assist you. > > Next. > > For this message: > > ARC0085I (H)BDELETE REQUIRES ONE OF THE FOLLOWING MUTUALLY EXCLUSIVE > KEYWORDS: > ARC0085I (CONT.) ALL, VERSIONS, OR > DATE > > > > It appears that when you entered the > BDELETE command you did not include the subparm of ALL VERSIONS or DATE > > Please review this process and ensure > you are entering the command according to the DFHSM Admin Guide > > Lizette > > > > -----Original Message----- > > From: IBM Mainframe Discussion > List [mailto:[email protected]] > On > > Behalf Of willie bunter > > Sent: Friday, July 28, 2017 6:33 > AM > > To: [email protected] > > Subject: Re: DFHSM QUESTION > > > > 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'404040404040404040404040404040404040404040404040404040404040404040404040404 > > 0404040404040') > > /* 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. > > > > > > > > > ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
