Discussion:
DFHSM QUESTION
Add Reply
willie bunter
2017-07-26 14:25:34 UTC
Reply
Permalink
Raw Message
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 ***@listserv.ua.edu with the message: INFO IBM-MAIN
retired mainframer
2017-07-26 17:29:02 UTC
Reply
Permalink
Raw Message
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-----
Behalf Of willie bunter
Sent: Wednesday, July 26, 2017 7:27 AM
Subject: DFHSM QUESTION
Good Day,
I ran an AUDIT of the BCDS. I was 99% successfull of performing a clean up execept for
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 ***@listserv.ua.edu with the message: INFO IBM-MAIN
Brian Fraser
2017-07-27 01:31:52 UTC
Reply
Permalink
Raw Message
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 <
Post by retired mainframer
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-----
Behalf Of willie bunter
Sent: Wednesday, July 26, 2017 7:27 AM
Subject: DFHSM QUESTION
Good Day,
I ran an AUDIT of the BCDS. I was 99% successfull of performing a clean
up execept for
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,
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to ***@listserv.ua.edu with the message: INFO IBM-MAIN
willie bunter
2017-07-27 13:31:03 UTC
Reply
Permalink
Raw Message
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 <***@GMAIL.COM> wrote:

Subject: Re: DFHSM QUESTION
To: IBM-***@LISTSERV.UA.EDU
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 <
Post by retired mainframer
Please show the
complete AUDIT and BDELETE commands you are using.
Post by retired mainframer
Did you look up ERR40
in the "Error Codes and Diagnosis" section
(section
Post by retired mainframer
3 in my copy) of the
"Using the AUDIT Command" chapter (my chapter
67)?
Post by retired mainframer
The table (51) identifies several
possible causes and corrective actions.
BDELETE is the proper action for only one of the causes.
Post by retired mainframer
-----Original
Message-----
Post by retired mainframer
From: IBM Mainframe
Discussion List [mailto:IBM-***@LISTSERV.UA.EDU]
On
Post by retired mainframer
Behalf Of willie bunter
Sent: Wednesday, July 26, 2017 7:27
AM
Post by retired mainframer
Subject: DFHSM QUESTION
Good
Day,
Post by retired mainframer
I
ran an AUDIT of the BCDS.  I was 99% successfull of
performing a clean
Post by retired mainframer
up execept for
  ERR 40 DB2.ARCHLOG2.A0091613
HSMBACK.BACK.T592617.DB2.ARCHLOG2.I8257 MISSING
Post by retired mainframer
  FIXCDS B DUMMY.RECOVER.MCB
CREATE(X'00000014' X'0098257F')
Post by retired mainframer
  FIXCDS B DUMMY.RECOVER.MCB
PATCH(X'0000002E' BITS(1.1.....))
Post by retired mainframer
  FIXCDS B DUMMY.RECOVER.MCB
PATCH(X'00000030' X'000100010001')
Post by retired mainframer
  FIXCDS B DUMMY.RECOVER.MCB
EXPAND(X'00000040')
Post by retired mainframer
 
FIXCDS B DUMMY.RECOVER.MCB PATCH(X'00000050' +
X'404040404040404040404040404040404040404040404040404040404040
Post by retired mainframer
404040404040
404
Post by retired mainframer
  FIXCDS B DUMMY.RECOVER.MCB
PATCH(X'00000050'
HSMBACK.BACK.T592617.DB2.ARCHLOG
Post by retired mainframer
 
FIXCDS B DUMMY.RECOVER.MCB PATCH(X'00000082'
BITS(01000010))
Post by retired mainframer
  BDELETE
DUMMY.RECOVER.MCB
Post by retired mainframer
  FIXCDS B
DUMMY.RECOVER.MCB DELETE
Post by retired mainframer
END OF
-    ENHANCED AUDIT - LISTING -
Post by retired mainframer
I tried a HSEND BDELETE
'DB2.ARCHLOG2.A0091613' ALL .  The command which
Post by retired mainframer
I
ran in batch
was successful however when I ran another AUDIT the entry
Post by retired mainframer
appears.  I tried a
HSEND FIXCDS B DB2.ARCHLOG2.A0091613.  Again the
command was successful,
Post by retired mainframer
however
the AUDIT says otherwise.
----------------------------------------------------------------------
Post by retired mainframer
For IBM-MAIN subscribe / signoff / archive
access instructions,
with the message: INFO IBM-MAIN
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive
access instructions,
send email to ***@listserv.ua.edu
with the message: INFO IBM-MAIN


----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to ***@listserv.ua.edu with the message: INFO IBM-MAIN
Lizette Koehler
2017-07-27 14:21:37 UTC
Reply
Permalink
Raw Message
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-----
Behalf Of willie bunter
Sent: Thursday, July 27, 2017 6:32 AM
Subject: Re: DFHSM QUESTION
Brian,
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
--------------------------------------------
Subject: Re: DFHSM QUESTION
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 <
Post by retired mainframer
Please show the
complete AUDIT and BDELETE commands you are using.
Post by retired mainframer
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)?
Post by retired mainframer
The table (51) identifies several
possible causes and corrective actions.
BDELETE is the proper action for only one of the causes.
Post by retired mainframer
-----Original
Message-----
Post by retired mainframer
From: IBM Mainframe
bunter > > Sent: Wednesday, July 26, 2017 7:27 AM > > To: IBM-
Post by retired mainframer
I ran an AUDIT of the BCDS. I was 99% successfull of performing a
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
Post by retired mainframer
404040404040
404
Post by retired mainframer
FIXCDS B DUMMY.RECOVER.MCB
PATCH(X'00000050'
HSMBACK.BACK.T592617.DB2.ARCHLOG
FIXCDS B DUMMY.RECOVER.MCB PATCH(X'00000082'
BITS(01000010))
Post by retired mainframer
BDELETE
DUMMY.RECOVER.MCB
Post by retired mainframer
FIXCDS B
DUMMY.RECOVER.MCB DELETE
Post by retired mainframer
END OF
- ENHANCED AUDIT - LISTING -
Post by retired mainframer
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
Post by retired mainframer
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 ***@listserv.ua.edu with the message: INFO IBM-MAIN
willie bunter
2017-07-27 14:22:51 UTC
Reply
Permalink
Raw Message
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-***@Q.COM> wrote:

Subject: Re: DFHSM QUESTION
To: IBM-***@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-***@LISTSERV.UA.EDU]
On
Behalf Of willie bunter
Sent: Wednesday, July 26, 2017 7:27 AM
Subject: DFHSM QUESTION
Good Day,
I ran an AUDIT of
the BCDS.  I was 99% successfull of performing a clean up
execept for
  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 ***@listserv.ua.edu
with the message: INFO IBM-MAIN

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to ***@listserv.ua.edu with the message: INFO IBM-MAIN
Carmen Vitullo
2017-07-27 14:37:06 UTC
Reply
Permalink
Raw Message
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-***@LISTSERV.UA.EDU>
To: IBM-***@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-***@Q.COM> wrote:

Subject: Re: DFHSM QUESTION
To: IBM-***@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-***@LISTSERV.UA.EDU]
On
Behalf Of willie bunter
Sent: Wednesday, July 26, 2017 7:27 AM
Subject: DFHSM QUESTION
Good Day,
I ran an AUDIT of
the BCDS. I was 99% successfull of performing a clean up
execept for
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 ***@listserv.ua.edu
with the message: INFO IBM-MAIN

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


----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to ***@listserv.ua.edu with the message: INFO IBM-MAIN
Lizette Koehler
2017-07-27 14:51:25 UTC
Reply
Permalink
Raw Message
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-----
Behalf Of willie bunter
Sent: Thursday, July 27, 2017 6:53 AM
Subject: Re: DFHSM QUESTION
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?
--------------------------------------------
Subject: Re: DFHSM QUESTION
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
willie bunter > Sent: Wednesday, July 26, 2017 7:27 AM > To: IBM-
an AUDIT of the BCDS. I was 99% successfull of performing a clean up
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 ***@listserv.ua.edu with the message: INFO IBM-MAIN
willie bunter
2017-07-27 15:35:14 UTC
Reply
Permalink
Raw Message
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 <***@MINDSPRING.COM> wrote:

Subject: Re: DFHSM QUESTION
To: IBM-***@LISTSERV.UA.EDU
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:IBM-***@LISTSERV.UA.EDU]
On
Behalf Of willie bunter
Sent: Thursday, July 27, 2017 6:32 AM
Subject: Re: DFHSM QUESTION
Brian,
I tried that out
however it didn't work (record not found).  Below is
the
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
--------------------------------------------
Re: DFHSM QUESTION
  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
<
  > 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
On  > > Behalf Of willie
bunter  > > Sent: Wednesday, July 26, 2017 7:27 
AM  > > To: IBM-
Subject: DFHSM QUESTION  > >  > >
Good  Day,  > >

ran an AUDIT of the BCDS.  I was 99% successfull of 
performing a
clean  > up execept
  > >  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 ***@listserv.ua.edu
with the message: INFO IBM-MAIN

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to ***@listserv.ua.edu with the message: INFO IBM-MAIN
Horne, Patti
2017-07-27 15:41:53 UTC
Reply
Permalink
Raw Message
Try using FIX on your audit to see if it cleans up the error.



-----Original Message-----
From: IBM Mainframe Discussion List [mailto:IBM-***@LISTSERV.UA.EDU] On Behalf Of willie bunter
Sent: Thursday, July 27, 2017 10:36 AM
To: IBM-***@LISTSERV.UA.EDU
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 <***@MINDSPRING.COM> wrote:

Subject: Re: DFHSM QUESTION
To: IBM-***@LISTSERV.UA.EDU
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
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 >
--------------------------------------------
Re: DFHSM QUESTION
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
<
Post by retired mainframer
Please show the
complete AUDIT and BDELETE commands you are using.
Post by retired mainframer
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)?
Post by retired mainframer
The
table (51) identifies several
possible causes and corrective actions.
BDELETE is
the proper action for only one of the causes.
-----Original
Message-----
Post by retired mainframer
From: IBM Mainframe
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
Post by retired mainframer
404040404040
404
Post by retired mainframer
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
Post by retired mainframer
FIXCDS B
DUMMY.RECOVER.MCB DELETE
Post by retired mainframer
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 ***@listserv.ua.edu with the message: INFO IBM-MAIN

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions, send email to ***@listserv.ua.edu 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 ***@listserv.ua.edu with the message: INFO IBM-MAIN
willie bunter
2017-07-27 15:57:07 UTC
Reply
Permalink
Raw Message
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 <***@MINDSPRING.COM> wrote:

Subject: Re: DFHSM QUESTION
To: IBM-***@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-***@LISTSERV.UA.EDU]
On
Behalf Of willie bunter
Sent: Thursday, July 27, 2017 6:53 AM
Subject: Re: DFHSM QUESTION
Here are the
  HSEND FIXCDS B
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?
--------------------------------------------
Re: DFHSM QUESTION
  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-***@LISTSERV.UA.EDU] 
On  > Behalf Of
willie bunter 
IBM-
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
  >  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 ***@listserv.ua.edu
with the message: INFO IBM-MAIN

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to ***@listserv.ua.edu with the message: INFO IBM-MAIN
Lizette Koehler
2017-07-27 16:05:25 UTC
Reply
Permalink
Raw Message
So is everything is correct now?

Or do you have more questions.

Otherwise I think your issues are resolved.

Lizette
-----Original Message-----
Behalf Of willie bunter
Sent: Thursday, July 27, 2017 8:58 AM
Subject: Re: DFHSM QUESTION
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
ARC0138I NO BCDS INFORMATION FOUND FOR DATASET DB2.ARCHLOG2.A0091613
--------------------------------------------
Subject: Re: DFHSM QUESTION
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
bunter >
Sent: Thursday, July 27, 2017 6:53 AM
Subject: Re: DFHSM QUESTION
Here are the
HSEND FIXCDS B
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?
--------------------------------------------
Re: DFHSM QUESTION
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
IBM-
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
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 ***@listserv.ua.edu with the message: INFO IBM-MAIN
willie bunter
2017-07-27 16:22:21 UTC
Reply
Permalink
Raw Message
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 <***@FISGLOBAL.COM> wrote:

Subject: Re: DFHSM QUESTION
To: IBM-***@LISTSERV.UA.EDU
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:IBM-***@LISTSERV.UA.EDU]
On Behalf Of willie bunter
Sent: Thursday,
July 27, 2017 10:36 AM
To: IBM-***@LISTSERV.UA.EDU
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 <***@MINDSPRING.COM>
wrote:

Subject: Re: DFHSM
QUESTION
To: IBM-***@LISTSERV.UA.EDU
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-----
IBM
Mainframe Discussion List [mailto:IBM-***@LISTSERV.UA.EDU] 
On  > Behalf Of willie bunter  > Sent: Thursday,
Subject: Re: DFHSM QUESTION  >  > Brian, 
  > I tried that out  however it didn't work
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  >

--------------------------------------------
Re: DFHSM QUESTION
  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
<
  > 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
On  > > Behalf Of willie  >  bunter  > >
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
  > >  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 ***@listserv.ua.edu 
with the message: INFO IBM-MAIN

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive
access instructions, send email to ***@listserv.ua.edu
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 ***@listserv.ua.edu
with the message: INFO IBM-MAIN


----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to ***@listserv.ua.edu with the message: INFO IBM-MAIN
Horne, Patti
2017-07-27 18:55:06 UTC
Reply
Permalink
Raw Message
You ran the fix on the BDELETE not the AUDIT.




-----Original Message-----
From: IBM Mainframe Discussion List [mailto:IBM-***@LISTSERV.UA.EDU] On Behalf Of willie bunter
Sent: Thursday, July 27, 2017 11:23 AM
To: IBM-***@LISTSERV.UA.EDU
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 <***@FISGLOBAL.COM> wrote:

Subject: Re: DFHSM QUESTION
To: IBM-***@LISTSERV.UA.EDU
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:IBM-***@LISTSERV.UA.EDU]
On Behalf Of willie bunter
Sent: Thursday,
July 27, 2017 10:36 AM
To: IBM-***@LISTSERV.UA.EDU
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 <***@MINDSPRING.COM>
wrote:

Subject: Re: DFHSM
QUESTION
To: IBM-***@LISTSERV.UA.EDU
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-----
IBM
Post by willie bunter
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 >

--------------------------------------------
Re: DFHSM QUESTION
Post by willie bunter
Received: Wednesday, July 26, 2017,
9:23 PM > > If you just want to get rid of > the backup, then you can do the following.
Post by willie bunter
HSEND FIXCDS B
DB2.ARCHLOG2.A0091613
*DELETE*
Regards
Post by willie bunter
Brian
On Thu, Jul 27,
2017 at 1:30
Post by willie bunter
AM,
retired mainframer
<
Post by willie bunter
Post by retired mainframer
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)?
Post by willie bunter
Post by retired mainframer
The
table (51) identifies several
possible causes and corrective
actions.
Post by willie bunter
BDELETE is
the proper action for
only one of the causes.
-----Original
Post by willie bunter
Message-----
Post by retired mainframer
From: IBM Mainframe
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
Post by willie bunter
Post by retired mainframer
ERR 40
DB2.ARCHLOG2.A0091613
HSMBACK.BACK.T592617.DB2.ARCHLOG2.I8257

MISSING > > FIXCDS B
DUMMY.RECOVER.MCB
CREATE(X'00000014'

X'0098257F') > > FIXCDS B
Post by willie bunter
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
Post by willie bunter
Post by retired mainframer
404040404040
404
FIXCDS B DUMMY.RECOVER.MCB
PATCH(X'00000050'
HSMBACK.BACK.T592617.DB2.ARCHLOG
Post by willie bunter
FIXCDS B
DUMMY.RECOVER.MCB

PATCH(X'00000082'
BITS(01000010))
BDELETE
DUMMY.RECOVER.MCB
Post by willie bunter
Post by retired mainframer
FIXCDS
B
Post by willie bunter
DUMMY.RECOVER.MCB DELETE
Post by retired mainframer
END OF
- ENHANCED AUDIT - LISTING -
Post by willie bunter
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 ***@listserv.ua.edu with the message: INFO IBM-MAIN

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions, send email to ***@listserv.ua.edu 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 ***@listserv.ua.edu with the message: INFO IBM-MAIN


----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions, send email to ***@listserv.ua.edu 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 ***@listserv.ua.edu with the message: INFO IBM-MAIN
Brian Fraser
2017-07-28 01:27:38 UTC
Reply
Permalink
Raw Message
HSEND AUDIT DSCTL(BACKUP) FIX ODS('dsn.for.output.listing')
is what you should run.
Post by Horne, Patti
You ran the fix on the BDELETE not the AUDIT.
-----Original Message-----
Behalf Of willie bunter
Sent: Thursday, July 27, 2017 11:23 AM
Subject: Re: DFHSM QUESTION
ARC0085I (CONT.) ALL, VERSIONS, OR DATE
ARC0085I (CONT.) ALL, VERSIONS, OR DATE
ARC0085I (CONT.) ALL, VERSIONS, OR DATE
ARC0085I (CONT.) ALL, VERSIONS, OR DATE
ARC0085I (CONT.) ALL, VERSIONS, OR DATE
ARC0085I (CONT.) ALL, VERSIONS, OR DATE
ARC0085I (CONT.) ALL, VERSIONS, OR DATE
ARC0085I (CONT.) ALL, VERSIONS, OR DATE
Below is my command
HSEND AUDIT DATASETCONTROLS(BACKUP) FIX -
ODS(SYS2.AUDIT.DATASET.CONTROLS.BCDS.FIX.#2)
--------------------------------------------
Subject: Re: DFHSM QUESTION
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
On Behalf Of willie bunter
Sent: Thursday,
July 27, 2017 10:36 AM
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
Subject: Re: DFHSM
QUESTION
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-----
IBM
I tried that out however it didn't work (record not found). Below is
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 >
--------------------------------------------
Re: DFHSM QUESTION
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
<
Post by retired mainframer
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)?
Post by retired mainframer
The
table (51) identifies several
possible causes and corrective
actions.
BDELETE is
the proper action for
only one of the causes.
-----Original
Message-----
Post by retired mainframer
From: IBM Mainframe
willie > bunter > >
Post by retired mainframer
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
Post by retired mainframer
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
Post by retired mainframer
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
Post by retired mainframer
FIXCDS
B
DUMMY.RECOVER.MCB DELETE
Post by retired mainframer
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
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions, send
information contained in this message is proprietary and/or confidential.
(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
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions, send email
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,
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to ***@listserv.ua.edu with the message: INFO IBM-MAIN
willie bunter
2017-07-27 16:24:18 UTC
Reply
Permalink
Raw Message
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 <***@HUGHES.NET> wrote:

Subject: Re: DFHSM QUESTION
To: IBM-***@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-***@LISTSERV.UA.EDU>

To: IBM-***@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-***@Q.COM>
wrote:

Subject: Re: DFHSM
QUESTION
To: IBM-***@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-***@LISTSERV.UA.EDU]

On
Behalf Of willie
bunter
Sent: Wednesday, July 26, 2017
7:27 AM
Subject: DFHSM QUESTION
Good Day,
I ran an AUDIT of
the BCDS. I was 99% successfull of
performing a clean up
execept for
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 ***@listserv.ua.edu

with the message: INFO IBM-MAIN

----------------------------------------------------------------------

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


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

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to ***@listserv.ua.edu with the message: INFO IBM-MAIN
willie bunter
2017-07-28 01:29:02 UTC
Reply
Permalink
Raw Message
Should I ignore the ERR 40 when I run the AUDIT report?

--------------------------------------------
On Thu, 7/27/17, Lizette Koehler <***@MINDSPRING.COM> wrote:

Subject: Re: DFHSM QUESTION
To: IBM-***@LISTSERV.UA.EDU
Received: Thursday, July 27, 2017, 12:06 PM

So is everything is correct
now?

Or do you have more
questions.

Otherwise I
think your issues are resolved.

Lizette
-----Original Message-----
From: IBM
Mainframe Discussion List [mailto:IBM-***@LISTSERV.UA.EDU]
On
Behalf Of willie bunter
Sent: Thursday, July 27, 2017 8:58 AM
Subject: Re: DFHSM QUESTION
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
ARC0138I NO BCDS INFORMATION FOUND FOR DATASET
DB2.ARCHLOG2.A0091613
--------------------------------------------
Re: DFHSM QUESTION
  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
On  > Behalf Of willie
bunter 
  Sent: Thursday, July 27, 2017
6:53 AM
  >
 
  > Subject: Re: DFHSM QUESTION
  >
  > Here
are the
  >  HSEND FIXCDS B
  DB96.ARCHLOG2.B0000778 (message
  >
  > 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
  >
 
Re: DFHSM QUESTION
  >  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-***@LISTSERV.UA.EDU] 
On  > Behalf Of
willie
bunter  > Sent: Wednesday, July 26, 2017 7:27 AM  >
  IBM-
  >
  > 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
 
  >  >  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 ***@listserv.ua.edu
with the message: INFO IBM-MAIN


----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to ***@listserv.ua.edu with the message: INFO IBM-MAIN
Brian Fraser
2017-07-28 02:40:37 UTC
Reply
Permalink
Raw Message
If you run the audit command with the FIX parameter, then it should delete
any orphaned C records without a matching B record.

Brian

On Fri, Jul 28, 2017 at 12:11 AM, willie bunter <
Post by willie bunter
Should I ignore the ERR 40 when I run the AUDIT report?
--------------------------------------------
Subject: Re: DFHSM QUESTION
Received: Thursday, July 27, 2017, 12:06 PM
So is everything is correct
now?
Or do you have more
questions.
Otherwise I
think your issues are resolved.
Lizette
-----Original Message-----
From: IBM
On
Behalf Of willie bunter
Sent: Thursday, July 27, 2017 8:58 AM
Subject: Re: DFHSM QUESTION
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
ARC0138I NO BCDS INFORMATION FOUND FOR DATASET
DB2.ARCHLOG2.A0091613
--------------------------------------------
Re: DFHSM QUESTION
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
On > Behalf Of willie
bunter
Sent: Thursday, July 27, 2017
6:53 AM
Subject: Re: DFHSM QUESTION
Here
are the
HSEND FIXCDS B
DB96.ARCHLOG2.B0000778 (message
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
Re: DFHSM QUESTION
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
On > Behalf Of
willie
bunter > Sent: Wednesday, July 26, 2017 7:27 AM >
IBM-
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
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,
with the message: INFO IBM-MAIN
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to ***@listserv.ua.edu with the message: INFO IBM-MAIN
willie bunter
2017-07-28 11:27:18 UTC
Reply
Permalink
Raw Message
Brian,

I did that but it didn't clear the ERR 40 records (see below for an example of the message). Thanks for the suggestion however.

/* 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
/* 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 <***@GMAIL.COM> wrote:

Subject: Re: DFHSM QUESTION
To: IBM-***@LISTSERV.UA.EDU
Received: Thursday, July 27, 2017, 10:31 PM

If you run the audit command with
the FIX parameter, then it should delete
any
orphaned C records without a matching B record.

Brian

On Fri, Jul 28, 2017 at 12:11 AM, willie bunter
<
Post by willie bunter
Should I ignore
the ERR 40 when I run the AUDIT report?
--------------------------------------------
Re: DFHSM QUESTION
Post by willie bunter
  Received: Thursday, July 27, 2017, 12:06
PM
Post by willie bunter
  So is
everything is correct
Post by willie bunter
  now?
  Or do you have
more
Post by willie bunter
  questions.
  Otherwise I
  think your issues are resolved.
  Lizette
  >
 
-----Original Message-----
IBM
Post by willie bunter
  Mainframe Discussion List
  On
  > Behalf Of
willie bunter
Post by willie bunter
  > Sent: Thursday,
July 27, 2017 8:58 AM
Post by willie bunter
  > Subject: Re: DFHSM QUESTION
  >
  > I tried
out the
Post by willie bunter
  BDELETE and as expected the
record was not found.
Post by willie bunter
  >
  > ARC0195I TYPE B, KEY
  DB2.ARCHLOG2.A0091613, FIXCDS DELETE,
ERROR=RECORD NOT
Post by willie bunter
  > ARC0195I
(CONT.) FOUND
Post by willie bunter
  > ARC1001I FIXCDS B
DB2.ARCHLOG2.A0091613
Post by willie bunter
  DELETE COMMAND
FAILED, RC=0015,
Post by willie bunter
  >
  ARC1001I (CONT.) REAS=0000
  > ARC1615I
 
FIXCDS COMMAND REJECTED
Post by willie bunter
  >
  >
  ARC0138I NO
BCDS INFORMATION FOUND FOR DATASET
Post by willie bunter
 
DB2.ARCHLOG2.A0091613
Post by willie bunter
  >
 
--------------------------------------------
Post by willie bunter
  > On Thu, 7/27/17, Lizette Koehler
  >
 
Re: DFHSM QUESTION
Post by willie bunter
  >  Received: Thursday, July 27,
2017, 10:52
Post by willie bunter
  AM
 
  >  At this
  point, just take one step
  >  back.
 
  >  You wanted to
  delete
  >  a
backup version from HSM.
Post by willie bunter
  >
  >  The dataset is
  either DB2.ARCHLOG2.A0091613  or
  DB96.ARCHLOG2.B0000778
  >
  >  Issue
an HLIST
Post by willie bunter
  >
 
DSN('DB96.ARCHLOG2.B0000778') BCDS    or 
HLIST
Post by willie bunter
 
DSN('DB2.ARCHLOG2.A0091613
Post by willie bunter
  >
')
Post by willie bunter
  BCDS
 
  >
 
  If you do not
  >  see
  any backup datasets listed for these
datasets, then you
Post by willie bunter
  have deleted
  > the backup copies.
  >
  >  If
you still see
Post by willie bunter
  BCDS entries, then you
may  need to do more BDELETE
Post by willie bunter
  >
commands.
Post by willie bunter
  >
 
  AUDIT is used to verify content in
  HSM.  However, it may create
confusion
Post by willie bunter
  >
 
with its results.
Post by willie bunter
  >
  >  I rarely use AUDIT.  If the
  >  BDELETE works or there are no
longer any
Post by willie bunter
  BCDS entries, I  will not
issue
Post by willie bunter
  > AUDIT
  commands.
  >
  >
  >  If
you could provide the
Post by willie bunter
  > 
description of the problem you are
Post by willie bunter
 
trying to solve with  BDELETE and AUDIT,
Post by willie bunter
  > that will be helpful.
  >
  >  From what you have posted so
far,
Post by willie bunter
  the BDELETE  looks like it was
successful
Post by willie bunter
  > at some point.
  >
  >
  >  For further
  >  analysis, issue the command
    BACKDS 
'DB2.ARCHLOG2.A0091613'
Post by willie bunter
 
  >  Then do the
  HLIST
  >
  DSN('DB2.ARCHLOG2.A0091613')
BCDS  and see if
Post by willie bunter
  you  get an
entry
Post by willie bunter
  >
 
  >  Next do the
  BDELETE command for
  >
 
DB2.ARCHLOG2.A0091613
Post by willie bunter
  >
  >
  > 
Repeat the HLIST
Post by willie bunter
  command.
  >
  >
  >  If there are
  >  no
  entries
in the BCDS for this dataset, that should show  the
Post by willie bunter
  process in
  >
HSM is working.
Post by willie bunter
  >
  >
  > 
Lizette
Post by willie bunter
  >
 
  >  >
  -----Original
 
  Message-----
IBM Mainframe
Post by willie bunter
  >  Discussion List
  On  > Behalf Of willie
  > bunter
 
  >  Sent: Thursday, July 27,
2017
Post by willie bunter
  6:53 AM
 
  >
  >
  >  > Subject: Re: DFHSM
QUESTION
Post by willie bunter
  >  >
  >  > Here
 
are the
Post by willie bunter
  >  >  HSEND FIXCDS B
  >  DB96.ARCHLOG2.B0000778
(message
Post by willie bunter
  >  >
 
  > ARC0195I TYPE B, KEY
 
  DB96.ARCHLOG2.B0000778, FIXCDS DISPLAY,
  ERROR=RECORD NOT  > ARC0195I
(CONT.)
Post by willie bunter
  > FOUND  > ARC1001I
FIXCDS B
Post by willie bunter
  DB96.ARCHLOG2.B0000778 
COMMAND FAILED, RC=0015,
Post by willie bunter
  >
REAS=0000  >  ARC1615I FIXCDS COMMAND
Post by willie bunter
  REJECTED  >  > HSEND 
BDELETE
Post by willie bunter
  >
 
'DB2.ARCHLOG2.A0091613' ALL No error message
Post by willie bunter
  received.
  > 
  >
  >
I
Post by willie bunter
  >  looked at the ERR 40  in
the
Post by willie bunter
  doc.  It describes my problem 
however it is  >
Post by willie bunter
  > not clear
what I should  do.  In this
Post by willie bunter
  case
the B record does not exist or  >
Post by willie bunter
 
missing.
  >  > for
  example
  >  it
says "If the backup
Post by willie bunter
  version (C)
record references a  data set  > (B)
Post by willie bunter
  > record that does not  exist, then
a new
Post by willie bunter
  (B) record is created and the 
  >
 
version added".  Not  usre ...then  a new(B)
record
Post by willie bunter
  is created and the
  > version  >
  added.
  > 
  >
  >
I do not understand this.  Any
Post by willie bunter
 
  suggestions?
  >  >
 
 
--------------------------------------------
Post by willie bunter
  >  > On Wed, 7/26/17, retired
mainframer
Post by willie bunter
 
  >
  >
  Re: DFHSM
QUESTION
Post by willie bunter
  >  >  Received: Wednesday, July
26,
Post by willie bunter
  2017, 1:30  PM  >  > 
Please show  the
Post by willie bunter
  > complete
AUDIT  >  and BDELETE
Post by willie bunter
  commands
you are using.
Post by willie bunter
  >  >
  >  >  Did you look up ERR40 in
the
Post by willie bunter
  "Error
  >  Codes  and
  Diagnosis" section (section 3 
in my copy) of
  the  "Using
the
Post by willie bunter
  > AUDIT
 
Command" chapter (my chapter  67)?  The  >
table
Post by willie bunter
  (51) identifies
  > several possible
  causes and  corrective  >
actions.  BDELETE is the
Post by willie bunter
  proper
  > action for only  one of the
  causes.
  > 
  >
 
  >
  >  > 
-----Original
Post by willie bunter
  Message-----
  >  >  > From: IBM
  >  >
 
  Mainframe
  Discussion List
  On  > Behalf Of
  > > willie
 
bunter  > Sent: Wednesday, July 26, 2017 7:27 AM 
Post by willie bunter
 
  IBM-
  >  >
  >  > Subject: DFHSM QUESTION 
  > Good Day,  >  > I
ran  > an AUDIT of
Post by willie bunter
  the
  > BCDS.  I was 99% successfull of
  performing a clean up  > execept
for  > the
Post by willie bunter
  > following type
  >
  >  >  >  ERR 40
  >  DB2.ARCHLOG2.A0091613
  >  >  >
  >
 
HSMBACK.BACK.T592617.DB2.ARCHLOG2.I8257
Post by willie bunter
  >  >  MISSING
  >
  > 
  >  FIXCDS B
  DUMMY.RECOVER.MCB
 
  >
  > 
CREATE(X'00000014'
Post by willie bunter
 
X'0098257F')
Post by willie bunter
  >  > 
  FIXCDS B DUMMY.RECOVER.MCB
  >  >
 
PATCH(X'0000002E'
Post by willie bunter
  >
  BITS(1.1.....))
 
  >  >  FIXCDS
  B
  >  DUMMY.RECOVER.MCB
  >  >
 
  PATCH(X'00000030'
X'000100010001')
Post by willie bunter
  > 
  >  FIXCDS B
 
DUMMY.RECOVER.MCB
Post by willie bunter
  >  >
  EXPAND(X'00000040')
  >  >
 
  FIXCDS B
  >  >
  >  DUMMY.RECOVER.MCB
  PATCH(X'00000050' +
  >  >
 
  >  >  >
  >  >
 
 
X'404040404040404040404040404040404040404040404040404040404040
Post by willie bunter
404040404040
  > 
  > 404
  >
  >  >
 
  FIXCDS B
  >  > 
DUMMY.RECOVER.MCB
Post by willie bunter
  > 
PATCH(X'00000050'
Post by willie bunter
  > 
  >
  >
  HSMBACK.BACK.T592617.DB2.ARCHLOG
  >
  >
  >  >  FIXCDS B
  DUMMY.RECOVER.MCB
 
  >
  > 
PATCH(X'00000082'
Post by willie bunter
 
BITS(01000010))
Post by willie bunter
  >  >  > 
BDELETE
Post by willie bunter
  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
Post by willie bunter
  which  I  > ran in batch  >
was
Post by willie bunter
  > successful  however when I
ran another
Post by willie bunter
  AUDIT the entry
appears.  I  tried  >
Post by willie bunter
  > a 
HSEND FIXCDS B
 
DB2.ARCHLOG2.A0091613.  Again the command was  >
Post by willie bunter
  > successful,  > however the
AUDIT
Post by willie bunter
  says  otherwise.
  >  >
 
 
----------------------------------------------------------------------
Post by willie bunter
  For IBM-MAIN subscribe / signoff /
archive
Post by willie bunter
  access instructions,
  with the message: INFO IBM-MAIN
----------------------------------------------------------------------
Post by willie bunter
For IBM-MAIN subscribe / signoff / archive
access instructions,
with the message: INFO IBM-MAIN
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive
access instructions,
send email to ***@listserv.ua.edu
with the message: INFO IBM-MAIN


----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to ***@listserv.ua.edu with the message: INFO IBM-MAIN
willie bunter
2017-07-28 13:32:04 UTC
Reply
Permalink
Raw Message
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 <***@GMAIL.COM> wrote:

Subject: Re: DFHSM QUESTION
To: IBM-***@LISTSERV.UA.EDU
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
<***@fisglobal.com>
wrote:
You ran the fix on the BDELETE not the AUDIT.
-----Original Message-----
From: IBM
Mainframe Discussion List [mailto:IBM-***@LISTSERV.UA.EDU]
On
Behalf Of willie bunter
Sent: Thursday, July 27, 2017 11:23 AM
Subject: Re: DFHSM QUESTION
I ran the FIX and the
ARC0085I (H)BDELETE REQUIRES ONE OF THE
FOLLOWING MUTUALLY EXCLUSIVE
ARC0085I (CONT.) ALL,
VERSIONS, OR DATE
ARC0085I (H)BDELETE
REQUIRES ONE OF THE FOLLOWING MUTUALLY EXCLUSIVE
ARC0085I
(CONT.) ALL, VERSIONS, OR DATE
ARC0085I
(H)BDELETE REQUIRES ONE OF THE FOLLOWING MUTUALLY
EXCLUSIVE
ARC0085I (CONT.) ALL, VERSIONS, OR DATE
ARC0085I (H)BDELETE REQUIRES ONE OF THE
FOLLOWING MUTUALLY EXCLUSIVE
ARC0085I (CONT.) ALL,
VERSIONS, OR DATE
ARC0085I (H)BDELETE
REQUIRES ONE OF THE FOLLOWING MUTUALLY EXCLUSIVE
ARC0085I
(CONT.) ALL, VERSIONS, OR DATE
ARC0085I
(H)BDELETE REQUIRES ONE OF THE FOLLOWING MUTUALLY
EXCLUSIVE
ARC0085I (CONT.) ALL, VERSIONS, OR DATE
ARC0085I (H)BDELETE REQUIRES ONE OF THE
FOLLOWING MUTUALLY EXCLUSIVE
ARC0085I (CONT.) ALL,
VERSIONS, OR DATE
ARC0085I (H)BDELETE
REQUIRES ONE OF THE FOLLOWING MUTUALLY EXCLUSIVE
ARC0085I
(CONT.) ALL, VERSIONS, OR DATE
Below is my command
 
  HSEND AUDIT DATASETCONTROLS(BACKUP) FIX -
         
ODS(SYS2.AUDIT.DATASET.CONTROLS.BCDS.FIX.#2)
--------------------------------------------
Re: DFHSM QUESTION
  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
  On Behalf Of willie bunter
  Sent: Thursday,
 
July 27, 2017 10:36 AM
  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
  Subject: Re: DFHSM
  QUESTION
  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-----
 
IBM
  Mainframe Discussion List
[mailto:IBM-***@LISTSERV.UA.EDU] 
On  >
Behalf Of willie bunter 
Subject: Re: DFHSM QUESTION  >  > Brian, 
I tried that out  however it
didn't work  (record not found).  Below is
 
  > 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
  >
  Re: DFHSM QUESTION
  >  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
  <
 
  >  > 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
On  > > Behalf Of
willie 
  bunter  > >
  > > 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
 
  >  > >  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 ***@listserv.ua.edu 
with the message: INFO IBM-MAIN
 
----------------------------------------------------------------------
  For IBM-MAIN subscribe / signoff /
archive  access instructions, send
email to ***@listserv.ua.edu 
with the message: INFO IBM-MAIN  The
information contained in this message is proprietary
and/or  confidential.
If you are not
  (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 ***@listserv.ua.edu 
with the message: INFO IBM-MAIN
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive
access instructions, send email
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,
with the message: INFO IBM-MAIN
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive
access instructions,
send email to ***@listserv.ua.edu
with the message: INFO IBM-MAIN


----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to ***@listserv.ua.edu with the message: INFO IBM-MAIN
Lizette Koehler
2017-07-28 13:59:45 UTC
Reply
Permalink
Raw Message
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-----
Behalf Of willie bunter
Sent: Friday, July 28, 2017 6:33 AM
Subject: Re: DFHSM QUESTION
Brian,
I tried your suggestion unfortunately it didn't get rid of the ERR 40. Here
ARC0085I (CONT.) ALL, VERSIONS, OR DATE
ARC0085I (CONT.) ALL, VERSIONS, OR DATE
ARC0085I (CONT.) ALL, VERSIONS, OR DATE
ARC0085I (CONT.) ALL, VERSIONS, OR DATE
ARC0085I (CONT.) ALL, VERSIONS, OR DATE
ARC0085I (CONT.) ALL, VERSIONS, OR DATE
ARC0085I (CONT.) ALL, VERSIONS, OR DATE
ARC0085I (CONT.) ALL, VERSIONS, OR DATE
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 -
--------------------------------------------
Subject: Re: DFHSM QUESTION
Received: Thursday, July 27, 2017, 9:18 PM
HSEND AUDIT DSCTL(BACKUP) FIX
ODS('dsn.for.output.listing')
is
what you should run.
You ran the fix on the BDELETE not the AUDIT.
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to ***@listserv.ua.edu with the message: INFO IBM-MAIN
willie bunter
2017-07-28 16:32:33 UTC
Reply
Permalink
Raw Message
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 <***@MINDSPRING.COM> wrote:

Subject: Re: DFHSM QUESTION
To: IBM-***@LISTSERV.UA.EDU
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:IBM-***@LISTSERV.UA.EDU]
On
Behalf Of willie bunter
Sent: Friday, July 28, 2017 6:33
AM
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
ARC0085I (H)BDELETE REQUIRES ONE
OF THE FOLLOWING MUTUALLY EXCLUSIVE
ARC0085I (CONT.) ALL, VERSIONS, OR
DATE
ARC0085I (H)BDELETE REQUIRES ONE
OF THE FOLLOWING MUTUALLY EXCLUSIVE
ARC0085I (CONT.) ALL, VERSIONS, OR
DATE
ARC0085I (H)BDELETE REQUIRES ONE
OF THE FOLLOWING MUTUALLY EXCLUSIVE
ARC0085I (CONT.) ALL, VERSIONS, OR
DATE
ARC0085I (H)BDELETE REQUIRES ONE
OF THE FOLLOWING MUTUALLY EXCLUSIVE
ARC0085I (CONT.) ALL, VERSIONS, OR
DATE
ARC0085I (H)BDELETE REQUIRES ONE
OF THE FOLLOWING MUTUALLY EXCLUSIVE
ARC0085I (CONT.) ALL, VERSIONS, OR
DATE
ARC0085I (H)BDELETE REQUIRES ONE
OF THE FOLLOWING MUTUALLY EXCLUSIVE
ARC0085I (CONT.) ALL, VERSIONS, OR
DATE
ARC0085I (H)BDELETE REQUIRES ONE
OF THE FOLLOWING MUTUALLY EXCLUSIVE
ARC0085I (CONT.) ALL, VERSIONS, OR
DATE
ARC0085I (H)BDELETE REQUIRES ONE
OF THE FOLLOWING MUTUALLY EXCLUSIVE
ARC0085I (CONT.) ALL, VERSIONS, OR
DATE
ARC0085I (H)BDELETE REQUIRES ONE
OF THE FOLLOWING MUTUALLY EXCLUSIVE
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
  Subject: Re: DFHSM QUESTION
  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
  >
  You ran the fix on the
BDELETE not the AUDIT.
  >
  >
  >
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff /
archive access instructions,
send email to ***@listserv.ua.edu
with the message: INFO IBM-MAIN

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to ***@listserv.ua.edu with the message: INFO IBM-MAIN
Gibney, Dave
2017-07-28 16:58:32 UTC
Reply
Permalink
Raw Message
Stop/Start DFHSM and end the confusion is to which command is getting which response by starting fresh.
The reissue the AUDIT with the FIX option. If the error is still there, show both the command and the output
-----Original Message-----
On Behalf Of willie bunter
Sent: Friday, July 28, 2017 9:34 AM
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.
--------------------------------------------
Subject: Re: DFHSM QUESTION
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.
ARC0085I (H)BDELETE REQUIRES ONE OF THE FOLLOWING MUTUALLY
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
On
Behalf Of willie bunter
Sent: Friday, July 28, 2017 6:33
AM
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
ARC0085I (H)BDELETE REQUIRES ONE
OF THE FOLLOWING MUTUALLY EXCLUSIVE
ARC0085I (CONT.) ALL, VERSIONS, OR
DATE
ARC0085I (H)BDELETE REQUIRES ONE
OF THE FOLLOWING MUTUALLY EXCLUSIVE
ARC0085I (CONT.) ALL, VERSIONS, OR
DATE
ARC0085I (H)BDELETE REQUIRES ONE
OF THE FOLLOWING MUTUALLY EXCLUSIVE
ARC0085I (CONT.) ALL, VERSIONS, OR
DATE
ARC0085I (H)BDELETE REQUIRES ONE
OF THE FOLLOWING MUTUALLY EXCLUSIVE
ARC0085I (CONT.) ALL, VERSIONS, OR
DATE
ARC0085I (H)BDELETE REQUIRES ONE
OF THE FOLLOWING MUTUALLY EXCLUSIVE
ARC0085I (CONT.) ALL, VERSIONS, OR
DATE
ARC0085I (H)BDELETE REQUIRES ONE
OF THE FOLLOWING MUTUALLY EXCLUSIVE
ARC0085I (CONT.) ALL, VERSIONS, OR
DATE
ARC0085I (H)BDELETE REQUIRES ONE
OF THE FOLLOWING MUTUALLY EXCLUSIVE
ARC0085I (CONT.) ALL, VERSIONS, OR
DATE
ARC0085I (H)BDELETE REQUIRES ONE
OF THE FOLLOWING MUTUALLY EXCLUSIVE
ARC0085I (CONT.) ALL, VERSIONS, OR
DATE
ARC0085I (H)BDELETE REQUIRES ONE
OF THE FOLLOWING MUTUALLY EXCLUSIVE
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'40404040404040404040404040404040404040404040404040404040404040404
0404040404
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
  Subject: Re: DFHSM QUESTION
  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
  >
  You ran the fix on the
BDELETE not the AUDIT.
  >
  >
  >
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff /
archive access instructions,
with the message: INFO IBM-MAIN
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions, send email to
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to ***@listserv.ua.edu with the message: INFO IBM-MAIN
Lizette Koehler
2017-07-28 17:08:32 UTC
Reply
Permalink
Raw Message
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-----
Behalf Of willie bunter
Sent: Friday, July 28, 2017 9:34 AM
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.
--------------------------------------------
Subject: Re: DFHSM QUESTION
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.
ARC0085I (H)BDELETE REQUIRES ONE OF THE FOLLOWING MUTUALLY EXCLUSIVE
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
On
Behalf Of willie bunter
Sent: Friday, July 28, 2017 6:33
AM
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
ARC0085I (H)BDELETE REQUIRES ONE
OF THE FOLLOWING MUTUALLY EXCLUSIVE
ARC0085I (CONT.) ALL, VERSIONS, OR
DATE
ARC0085I (H)BDELETE REQUIRES ONE
OF THE FOLLOWING MUTUALLY EXCLUSIVE
ARC0085I (CONT.) ALL, VERSIONS, OR
DATE
ARC0085I (H)BDELETE REQUIRES ONE
OF THE FOLLOWING MUTUALLY EXCLUSIVE
ARC0085I (CONT.) ALL, VERSIONS, OR
DATE
ARC0085I (H)BDELETE REQUIRES ONE
OF THE FOLLOWING MUTUALLY EXCLUSIVE
ARC0085I (CONT.) ALL, VERSIONS, OR
DATE
ARC0085I (H)BDELETE REQUIRES ONE
OF THE FOLLOWING MUTUALLY EXCLUSIVE
ARC0085I (CONT.) ALL, VERSIONS, OR
DATE
ARC0085I (H)BDELETE REQUIRES ONE
OF THE FOLLOWING MUTUALLY EXCLUSIVE
ARC0085I (CONT.) ALL, VERSIONS, OR
DATE
ARC0085I (H)BDELETE REQUIRES ONE
OF THE FOLLOWING MUTUALLY EXCLUSIVE
ARC0085I (CONT.) ALL, VERSIONS, OR
DATE
ARC0085I (H)BDELETE REQUIRES ONE
OF THE FOLLOWING MUTUALLY EXCLUSIVE
ARC0085I (CONT.) ALL, VERSIONS, OR
DATE
ARC0085I (H)BDELETE REQUIRES ONE
OF THE FOLLOWING MUTUALLY EXCLUSIVE
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
Subject: Re: DFHSM QUESTION
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
You ran the fix on the
BDELETE not the AUDIT.
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to ***@listserv.ua.edu with the message: INFO IBM-MAIN
Loading...