So, the idea of running DFHSM with a a limited ARCCMDxx as part of the CDS 
restore job is not viable!
Message ARC0009I DFSMSHSM STARTUP ATTEMPT FAILED, NOT A STARTED TASK happens

So, I guess I have no choice but to document it as a task to be performed post 
1st IPL of the recovered system 

And, I guess the errors
ARC0747E UNABLE TO CATALOG DATA SET 753                             
ARC0747E (CONT.) HSM.MCDS.BACKUP.D0013495 DURING CDS BACKUP, RC=0008
ARC0747E UNABLE TO CATALOG DATA SET 754                             
ARC0747E (CONT.) HSM.BCDS.BACKUP.D0013495 DURING CDS BACKUP, RC=0008
ARC0747E UNABLE TO CATALOG DATA SET 755                             
ARC0747E (CONT.) HSM.OCDS.BACKUP.D0013495 DURING CDS BACKUP, RC=0008
ARC0747E UNABLE TO CATALOG DATA SET 756                             
ARC0747E (CONT.) HSM.JRNL.BACKUP.D0013495 DURING CDS BACKUP, RC=0008
ARC0748I LAST SUCCESSFUL CDS BACKUP-SET QUALIFIER IS 757            
ARC0748I (CONT.) D0013495                                           
ARC0741I CDS BACKUP ENDING AT 02:31:39 ON 2019/01/31, 758           
ARC0741I (CONT.) STATUS=UNSUCCESSFUL                                

Which only happen the first CDS backup cycle are not the end of the world. :) 
Just untidy....

> >
> > If you don't want to run a special ARCCMDxx and you don't want to
> > issue the FIXCDS command manually, what other approach did you have in
> mind?
> >
> > > -----Original Message-----
> > > From: IBM Mainframe Discussion List <IBM-MAIN@LISTSERV.UA.EDU> On
> > > Behalf Of Gibney, Dave
> > > Sent: Monday, February 04, 2019 3: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
> >
> > ----------------------------------------------------------------------
> > For IBM-MAIN subscribe / signoff / archive access instructions, send
> > email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
> 
> ----------------------------------------------------------------------
> For IBM-MAIN subscribe / signoff / archive access instructions, send email to
> lists...@listserv.ua.edu with the message: INFO IBM-MAIN

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

Reply via email to