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
--------------------------------------------------------------------------------
This electronic mail (including any attachments) may contain information that
is privileged, confidential, and/or otherwise protected from disclosure to
anyone other than its intended recipient(s). Any dissemination or use of this
electronic email or its contents (including any attachments) by persons other
than the intended recipient(s) is strictly prohibited. If you have received
this message in error, please notify us immediately by reply email so that we
may correct our internal records. Please then delete the original message
(including any attachments) in its entirety. Thank you
-----Original Message-----
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf
Of Matt Hogstrom
Sent: Thursday, December 19, 2024 8:11 AM
To: IBM-MAIN@LISTSERV.UA.EDU
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
> <000005e4a8a0a03d-dmarc-requ...@listserv.ua.edu> 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 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
