To each his own but wouldn't an Export/Import be more efficient. There's no additional file to define, no jcl to change or files to rename.
Besides the sample jcl is provided in sys1.samplib(ARCSTRST). HSMPRESS is located at the end of the member. -----Original Message----- From: Staller, Allan [mailto:[email protected]] Sent: Thursday, January 17, 2013 8:27 AM To: [email protected] Subject: Re: DFHSM CDS size versus multi-cluster Probably needs to be re-orged. Define a "new cluster" shut down HSM(all LPARS) and repro. You will probably be amazed at how small the re-orged dataset will be. That being said, my DFHSM CDS's are defined as VSAM extended format dataset in a "do nothing" SMS management class and storage group. Concurrent copy will greatly improve the speed of CDS backups. Works great. HTH, <snip> I'm running z/os V1.12 and I've got my BCDS filled with 85%. It's size is 6500 CYLS with no SEC space. VSAM characteristics are: SHROPTNS(3,3) RECOVERY UNIQUE NOERASE UNORDERED TEMP-EXP NOREUSE NONSPANNED INDEXED NOWRITECHK NOIMBED NOREPLICAT EXTENDED EXT-ADDR In a short time I'll have to create a new BCDS, so, in your opinion what's advisable to have (performance aspect, backup considerations?, etc)?? 1) a bigger BCDS or 2) multi cluster Note: - DFHSM cdss are shared among 3 lpars </snip> ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [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
