Any reason you don’t have DFHSM CDSs backed up straight to VTL tape? It is an option.
From: IBM Mainframe Discussion List <[email protected]> On Behalf Of Dave Gibney Sent: Friday, December 20, 2024 2:39 PM To: [email protected] Subject: Re: DFHSM error When I had a system, I had the HSM CDS backup datasets pre-allocated (4 each) on non-SMS volumes with sufficient space. DFHSM then rotated between them. This is the way the DFHSM starter set (there is sample JCL) originally set things up. BCD's ZjQcmQRYFpfptBannerStart This Message Is From an External Sender Do not click links or open attachments unless you recognize the sender and know the content is safe. ZjQcmQRYFpfptBannerEnd When I had a system, I had the HSM CDS backup datasets pre-allocated (4 each) on non-SMS volumes with sufficient space. DFHSM then rotated between them. This is the way the DFHSM starter set (there is sample JCL) originally set things up. BCD's can grow significantly, especially if EXPIREBV is not run on a regular basis. My daily DFHSM maintenance job included three EXPIREBV commands. I also had it issue a few of the QUERY commands so that I usually didn't get surprised by these back-up space failures. > -----Original Message----- > From: IBM Mainframe Discussion List > <[email protected]<mailto:[email protected]>> On > Behalf Of Matthew Stitt > Sent: Friday, December 20, 2024 10:26 AM > To: [email protected]<mailto:[email protected]> > Subject: Re: DFHSM error > > I used a simple copy to a larger dataset. > > Bring HSM down. Rename the backup xCDS datasets. > > Define a new xCDS (larger). Copy (REPRO) to the new xCDS. Rename the xCDS > (old, new). Bring HSM back up. > > The backup copies HSM creates should have the new xCDS size. > > Matthew > > On Fri, 20 Dec 2024 15:37:32 +0400, Peter > <[email protected]<mailto:[email protected]>> > wrote: > > >Hello Steve > > > >Do you have a sample JCL that you follow in enlarging ? > > > >On Thu, 19 Dec 2024, 23:29 Steve Beaver, < > >[email protected]<mailto:[email protected]>> > > wrote: > > > >> Well you have 2 options > >> > >> INIT a new VOLUME with a much larger VTOC and copy over the > >> VOLUME and don’t > >> Forget the VVDS and copy the OLD to the New > >> > >> Dump the Volume using DSS, then RE-INIT the VOLUME with a > >> much larger VTOC and don't > >> Forget the VCVDS and restore the VOLUME > >> > >> > >> > >> > >> > >> > >> --------------------------------------------------------------------- > >> ----------- > >> -----Original Message----- > >> From: IBM Mainframe Discussion List [mailto:IBM- > [email protected]<mailto:[email protected]>] > >> On Behalf Of Matt Hogstrom > >> Sent: Thursday, December 19, 2024 8:11 AM > >> To: [email protected]<mailto:[email protected]> > >> Subject: Re: DFHSM error > >> > >> Does the VTOC have sufficient space for a new extent? > >> > >> -- > >> Matt Hogstrom > >> > >> “To achieve great things two things are needed: a plan, and not quite > >> enough time.” > >> - Leonard Bernstein > >> > >> > On Dec 19, 2024, at 09:04, Peter < > >> [email protected]<mailto:[email protected]>> > >> wrote: > >> > > >> >> DFHSM.MCDS.BACKUP.V0013037 > >> >> > >> >> *ARC0744E MCDS COULD NOT BE BACKED UP, RC=0013, 035 > >> >> > >> >> ARC0744E (CONT.) REAS=B37. MIGRATION, BACKUP, FRBACKUP, DUMP, > AND > >> > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, send email to > [email protected]<mailto:[email protected]> with the message: > INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected]<mailto:[email protected]> with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
