Hello I tried allocating the DFHSM BACKUP dataset tape but I don't see them over ISPF 3.4 after the job ran fine with 00.
May be my JCL needs a tweak and I just picked up from DFHSM starter 000003 //ALLOCBK EXEC PGM=IEFBR14 000004 //MCDSV1 DD DSN=DFHSM.MCDS.BACKUP.D0000001,DISP=(,CATLG),UNIT=DTAPE 000005 //MCDSV2 DD DSN=DFHSM.MCDS.BACKUP.D0000002,DISP=(,CATLG),UNIT=DTAPE 000006 //MCDSV3 DD DSN=DFHSM.MCDS.BACKUP.D0000003,DISP=(,CATLG),UNIT=DTAPE 000007 //MCDSV4 DD DSN=DFHSM.MCDS.BACKUP.D0000004,DISP=(,CATLG),UNIT=DTAPE Peter On Sun, 22 Dec 2024, 16:35 Bost, David Loyd, < 0000075740fe916a-dmarc-requ...@listserv.ua.edu> wrote: > If you have changed to tape and DSS with the above comments, I believe the > last node switches to .Dxxxxxx But it has been a long time since I > switched. Look in the DFHSM started task and you will see the names it > created. > > David l. Bost Jr. > HCL/Unum > (O) 803-731-5869 > (M) 803-587-4597 > ________________________________ > From: IBM Mainframe Discussion List <IBM-MAIN@LISTSERV.UA.EDU> on behalf > of Jake Anderson <00000655e880aa7d-dmarc-requ...@listserv.ua.edu> > Sent: Saturday, December 21, 2024 11:43:02 PM > To: IBM-MAIN@LISTSERV.UA.EDU <IBM-MAIN@LISTSERV.UA.EDU> > Subject: Re: DFHSM error > > Hello David Thanks. After relishing some space on this volume I can see > the BACKUP dataset are created successfully but I don't see those dataset > under ispf 3. 4. Are these DFHSM. BACKUP MCDS. Vxxzzx are temporary and > it's deleted at the end of > 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 > > Hello David > > Thanks. > > After relishing some space on this volume I can see the BACKUP dataset are > created successfully but I don't see those dataset under ispf 3.4. > > Are these DFHSM.BACKUP > MCDS.Vxxzzx are temporary and it's deleted at the end of the task? > > On Sun, 22 Dec 2024, 03:44 Bost, David Loyd, < > 0000075740fe916a-dmarc-requ...@listserv.ua.edu> wrote: > > > Items in DFHSM PARMLIB ARCCMDxx member: > > > > SETSYS CDSVERSIONBACKUP - > > (BACKUPCOPIES(10) - > > BACKUPDEVICECATEGORY(TAPE(PARALLEL)) - > > DATAMOVER(DSS)) > > > > Could be a few others you might need to change or modify in your > > environment. But the SETSYS parms in the ARCCMD member is what you need > to > > review. > > > > Below is the F DFHSM,Q SETSYS command lists for the CDS backup section in > > my environment. As you can see by the number > > we have been backing up the CDSs for a long time D0026350. > > > > ARC0375I CDSVERSIONBACKUP, MCDSBACKUPDSN=HSM.MCDS.BACKUP, > > ARC0375I (CONT.) BCDSBACKUPDSN=HSM.BCDS.BACKUP.DS1-.DS2, > > ARC0375I (CONT.) OCDSBACKUPDSN=HSM.OCDS.BACKUP, > > JRNLBACKUPDSN=HSM.JRNL.BACKUP > > ARC0376I BACKUPCOPIES=0010, BACKUPDEVICECATEGORY=TAPE UNITNAME=3490, > > DENSITY=*, > > ARC0376I (CONT.) RETPD=0007, PARALLEL, LATESTFINALQUALIFIER=D0026350, > > ARC0376I (CONT.) DATAMOVER=DSS > > > > Hope this helps you get there. > > > > From: IBM Mainframe Discussion List <IBM-MAIN@LISTSERV.UA.EDU> On Behalf > > Of Peter > > Sent: Saturday, December 21, 2024 1:38 PM > > To: IBM-MAIN@LISTSERV.UA.EDU > > Subject: Re: DFHSM error > > > > I would love to back this up to Virtual tape DLM8500. So what changes i > > need to do so that the HSM recognises the tape file for backup? On Fri, > 20 > > Dec 2024, 23: 59 Bost, David Loyd, < 0000075740fe916a-dmarc-request@ > > listserv. ua. edu> wrote: > > 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 > > > > I would love to back this up to Virtual tape DLM8500. > > > > > > > > So what changes i need to do so that the HSM recognises the tape file for > > > > backup? > > > > > > > > > > > > On Fri, 20 Dec 2024, 23:59 Bost, David Loyd, < > > > > 0000075740fe916a-dmarc-requ...@listserv.ua.edu<mailto: > > 0000075740fe916a-dmarc-requ...@listserv.ua.edu>> wrote: > > > > > > > > > Any reason you don’t have DFHSM CDSs backed up straight to VTL tape? It > > is > > > > > an option. > > > > > > > > > > From: IBM Mainframe Discussion List <IBM-MAIN@LISTSERV.UA.EDU<mailto: > > IBM-MAIN@LISTSERV.UA.EDU>> On Behalf > > > > > Of Dave Gibney > > > > > Sent: Friday, December 20, 2024 2:39 PM > > > > > To: IBM-MAIN@LISTSERV.UA.EDU<mailto:IBM-MAIN@LISTSERV.UA.EDU> > > > > > 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 <IBM-MAIN@LISTSERV.UA.EDU > <mailto: > > > > > IBM-MAIN@LISTSERV.UA.EDU<mailto:IBM-MAIN@LISTSERV.UA.EDU>>> On > > > > > > > > > > > Behalf Of Matthew Stitt > > > > > > > > > > > Sent: Friday, December 20, 2024 10:26 AM > > > > > > > > > > > To: IBM-MAIN@LISTSERV.UA.EDU<mailto:IBM-MAIN@LISTSERV.UA.EDU<mailto: > > IBM-MAIN@LISTSERV.UA.EDU%3cmailto:IBM-MAIN@LISTSERV.UA.EDU>> > > > > > > > > > > > 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 <dbajava...@gmail.com > > <mailto: > > > > > dbajava...@gmail.com<mailto:dbajava...@gmail.com>>> > > > > > > > > > > > wrote: > > > > > > > > > > > > > > > > > > > > > > >Hello Steve > > > > > > > > > > > > > > > > > > > > > > > >Do you have a sample JCL that you follow in enlarging ? > > > > > > > > > > > > > > > > > > > > > > > >On Thu, 19 Dec 2024, 23:29 Steve Beaver, < > > > > > > > > > > > >0000050e0c375a14-dmarc-requ...@listserv.ua.edu<mailto<mailto: > > 0000050e0c375a14-dmarc-requ...@listserv.ua.edu%3cmailto>: > > > > > 0000050e0c375a14-dmarc-requ...@listserv.ua.edu<mailto: > > 0000050e0c375a14-dmarc-requ...@listserv.ua.edu>>> 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- > > > > > > > > > > > m...@listserv.ua.edu<mailto:m...@listserv.ua.edu<mailto: > > m...@listserv.ua.edu%3cmailto:m...@listserv.ua.edu>>] > > > > > > > > > > > >> On Behalf Of Matt Hogstrom > > > > > > > > > > > >> Sent: Thursday, December 19, 2024 8:11 AM > > > > > > > > > > > >> To: IBM-MAIN@LISTSERV.UA.EDU<mailto:IBM-MAIN@LISTSERV.UA.EDU > > <mailto:IBM-MAIN@LISTSERV.UA.EDU%3cmailto: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<mailto<mailto: > > 000005e4a8a0a03d-dmarc-requ...@listserv.ua.edu%3cmailto>: > > > > > 000005e4a8a0a03d-dmarc-requ...@listserv.ua.edu<mailto: > > 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<mailto:lists...@listserv.ua.edu<mailto: > > lists...@listserv.ua.edu%3cmailto: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<mailto:lists...@listserv.ua.edu > > <mailto:lists...@listserv.ua.edu%3cmailto: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<mailto: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<mailto: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 > ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
