I understand that the record doesn't exist.  However my question is how do I 
perform the clean up of the ERR 40 records?
--------------------------------------------
On Thu, 7/27/17, Carmen Vitullo <cvitu...@hughes.net> wrote:

 Subject: Re: DFHSM QUESTION
 To: IBM-MAIN@LISTSERV.UA.EDU
 Received: Thursday, July 27, 2017, 10:38 AM
 
 I think it's time to list the
 contents of the BCDS, I don't have HSM so I can't
 provide the correct command, 
 
 
 HSEND LIST LEVEL(DB96) BCDS or
 (BACKUPCONTROLDATASET) OUTDATASET(xxx.yyy.xxx) ?? 
 
 but I tent to agree with
 Lizette, the record in the BCDS does not exist 
 
 
     *
 RECORD NOT FOUND—The indicated record was not found; you
 could not delete or update it. 
 
 
 Carmen ----- Original Message
 -----
 
 From: "willie
 bunter" <0000001409bd2345-dmarc-requ...@listserv.ua.edu>
 
 To: IBM-MAIN@LISTSERV.UA.EDU
 
 Sent: Thursday, July 27, 2017 8:52:37 AM
 
 Subject: Re: DFHSM QUESTION 
 
 Here are the commands I tried
 : 
 HSEND FIXCDS B DB96.ARCHLOG2.B0000778
 (message received) : 
 
 ARC0195I TYPE B, KEY DB96.ARCHLOG2.B0000778,
 FIXCDS DISPLAY, ERROR=RECORD NOT 
 ARC0195I
 (CONT.) FOUND 
 ARC1001I FIXCDS B
 DB96.ARCHLOG2.B0000778 COMMAND FAILED, RC=0015, REAS=0000
 
 ARC1615I FIXCDS COMMAND REJECTED 
 
 HSEND BDELETE
 'DB2.ARCHLOG2.A0091613' ALL 
 No
 error message received. 
 
 I
 looked at the ERR 40 in the doc. It describes my problem
 however it is not clear what I should do. In this case the B
 record does not exist or missing. 
 for
 example it says "If the backup version (C) record
 references a data set (B) record that does not exist, then a
 new (B) record is created and the version added". Not
 usre ...then a new(B) record is created and the version
 added. 
 
 I do not understand
 this. Any suggestions? 
 --------------------------------------------
 
 On Wed, 7/26/17, retired mainframer <retired-mainfra...@q.com>
 wrote: 
 
 Subject: Re: DFHSM
 QUESTION 
 To: IBM-MAIN@LISTSERV.UA.EDU
 
 Received: Wednesday, July 26, 2017, 1:30 PM
 
 
 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:IBM-MAIN@LISTSERV.UA.EDU]
 
 On 
 > Behalf Of willie
 bunter 
 > Sent: Wednesday, July 26, 2017
 7:27 AM 
 > To: IBM-MAIN@LISTSERV.UA.EDU
 
 > 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'404040404040404040404040404040404040404040404040404040404040404040404040
 
 > 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 lists...@listserv.ua.edu
 
 with the message: INFO IBM-MAIN 
 
 ----------------------------------------------------------------------
 
 For IBM-MAIN subscribe / signoff / archive
 access instructions, 
 send email to lists...@listserv.ua.edu
 with the message: INFO IBM-MAIN 
 
 
 ----------------------------------------------------------------------
 For IBM-MAIN subscribe / signoff / archive
 access instructions,
 send email to lists...@listserv.ua.edu
 with the message: INFO IBM-MAIN

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Reply via email to