I tried out the BDELETE and as expected the record was not found.
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
Below is the HLIST:
ARC0138I NO BCDS INFORMATION FOUND FOR DATASET DB2.ARCHLOG2.A0091613
--------------------------------------------
On Thu, 7/27/17, Lizette Koehler <stars...@mindspring.com> wrote:
Subject: Re: DFHSM QUESTION
To: IBM-MAIN@LISTSERV.UA.EDU
Received: Thursday, July 27, 2017, 10:52 AM
At this point, just take one step
back.
You wanted to delete
a backup version from HSM.
The dataset is either DB2.ARCHLOG2.A0091613
or DB96.ARCHLOG2.B0000778
Issue an HLIST
DSN('DB96.ARCHLOG2.B0000778') BCDS or
HLIST DSN('DB2.ARCHLOG2.A0091613 ') BCDS
If you do not
see any backup datasets listed for these datasets, then you
have deleted the backup copies.
If you still see BCDS entries, then you may
need to do more BDELETE commands.
AUDIT is used to verify content in HSM.
However, it may create confusion with its results.
I rarely use AUDIT. If the
BDELETE works or there are no longer any BCDS entries, I
will not issue AUDIT commands.
If you could provide the
description of the problem you are trying to solve with
BDELETE and AUDIT, that will be helpful.
From what you have posted so far, the BDELETE
looks like it was successful at some point.
For further
analysis, issue the command BACKDS
'DB2.ARCHLOG2.A0091613'
Then do the HLIST
DSN('DB2.ARCHLOG2.A0091613') BCDS and see if you
get an entry
Next do the BDELETE command for
DB2.ARCHLOG2.A0091613
Repeat the HLIST command.
If there are
no entries in the BCDS for this dataset, that should show
the process in HSM is working.
Lizette
> -----Original
Message-----
> From: IBM Mainframe
Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU]
On
> Behalf Of willie bunter
>
Sent: Thursday, July 27, 2017 6:53 AM
>
To: IBM-MAIN@LISTSERV.UA.EDU
> 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-
> m...@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
