I regenerate my DR restore jobs at the end of the daily FDRABR DR back-up jobs. 
We use DFHSM for migration and application ack-and restore. When practicing the 
DR recovery, I need to restore DFHSM using the most recent CDS back-up.
So, this scenario is that I've just restored all CDS (and JRNL)  from the 
latest back-up. So, the version numder in the MCDS for the next backup is the 
one I used to restore. I'd like to reset that value before starting DFHSM with 
these restored CDSs. To me, this would be the least error prone path. I'd like 
it to be a step in the restore job. It seems that to do this, that step in the 
restore job needs to be DFHSM itself, with an abbreviated ARCCMDxx member that 
I'll need to also dynamically generate. In an temp PDS? So, now a three step 
DFHSM recovery job.

> -----Original Message-----
> From: IBM Mainframe Discussion List <IBM-MAIN@LISTSERV.UA.EDU> On
> Behalf Of Allan Staller
> Sent: Tuesday, February 05, 2019 5:18 AM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: Re: DFHSM FIXCDS before start-up?
> 
> Why would you want to do this?
> I presume you have the health-check recommended 4 backups (or more).
> If the current backup is 'N', the next backup would be taken to N+1.
> N will not be overwritten for 3 additional cycles. More than long enough to
> make a backup copy.
> 
> To answer your question about fixcds prior to startup, no.  What I have done
> is add the FIXCDS command to the end of ARCCMD* This will be executed
> before a CDS backup can occur.
> 
> You can also bring dfHSM up in emergency mode obtain the backup number
> and issue the FIXCDS command followed by SETSYS NOEMERGENCY.
> 
> HTH,
> 
> -----Original Message-----
> From: IBM Mainframe Discussion List <IBM-MAIN@LISTSERV.UA.EDU> On
> Behalf Of Gibney, Dave
> Sent: Monday, February 4, 2019 5:19 PM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: DFHSM FIXCDS before start-up?
> 
> I am refining our DR procedures. After I restore the DFHSM CDSs from the
> most recent back-up, I need to update so as to  not overwrite that back-up
> with the next occurrence of CDS backup. The fine manual says to use FIXCDS
> S MHCR PATCH(X'B1' nnnnnnn) to set the next back-up number.
> FIXCDS requires an active DFHSM. Is there a supported way to make this
> update BEFORE starting DFHSM on the recovered system?
> 
> I have thought of running DFHSM itself with a specifically tailored parm to
> come up, FIXCDS, and stop, but this seems overkill. I can also do it 
> "manually"
> during the steps documented for first IPL of recovered system, but this is
> more prone to error or omission.  S DFHSM is in my COMMNDxx parmlib
> member.
> 
> Dave Gibney
> Information Technology Services
> Washington State University
> 
> 
> ----------------------------------------------------------------------
> For IBM-MAIN subscribe / signoff / archive access instructions, send email to
> lists...@listserv.ua.edu with the message: INFO IBM-MAIN
> ::DISCLAIMER::
> ----------------------------------------------------------------------------------------------
> ----------------------------------------------------------------------------------------------
> ------------------------------------------------------------------------------------------
> The contents of this e-mail and any attachment(s) are confidential and
> intended for the named recipient(s) only. E-mail transmission is not
> guaranteed to be secure or error-free as information could be intercepted,
> corrupted, lost, destroyed, arrive late or incomplete, or may contain viruses
> in transmission. The e mail and its contents (with or without referred errors)
> shall therefore not attach any liability on the originator or HCL or its 
> affiliates.
> Views or opinions, if any, presented in this email are solely those of the
> author and may not necessarily reflect the views or opinions of HCL or its
> affiliates. Any form of reproduction, dissemination, copying, disclosure,
> modification, distribution and / or publication of this message without the
> prior written consent of authorized representative of HCL is strictly
> prohibited. If you have received this email in error please delete it and 
> notify
> the sender immediately. Before opening any email and/or attachments,
> please check them for viruses and other defects.
> ----------------------------------------------------------------------------------------------
> ----------------------------------------------------------------------------------------------
> ------------------------------------------------------------------------------------------
> 
> ----------------------------------------------------------------------
> For IBM-MAIN subscribe / signoff / archive access instructions, send email to
> lists...@listserv.ua.edu with the message: INFO IBM-MAIN

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

Reply via email to