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]> 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]> 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:[email protected]] On >> Behalf Of Matt Hogstrom >> Sent: Thursday, December 19, 2024 8:11 AM >> To: [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]> 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] with the message: INFO IBM-MAIN
