To expand a bit Steps to reorg (a process I have used in the past). I also have modified the IBM Start Set for HSM found in SYS1.SAMPLIB for this purpose.
1) Shutdown HSM 2) Backup (DFDSS Dump) HSM datasets 3) Rename all current CDS datasets to .OLD 4) Allocate new xCDS datasets (using SYS1.SAMPLIB HSM starter set) 5) VSAM REPRO old to new (include any additional validations here) 6) Start HSM backup on one system and validate 7) Start remaining HSMs as needed The IBM Sample started in SYS1.SAMPLIB is a good version of reorging HSM xCDS datasets. Also pay attention when IBM changes the record sizes in the xCDS datasets. They do that occasionally. JCL from 10 years ago may not be the same as today. Lizette > -----Original Message----- > From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On > Behalf Of R.S. > Sent: Wednesday, March 29, 2017 8:22 AM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: Re: REORGANIZING HSM CDS > > In short words, there is no black magic here, it is regular VSAM KSDS cluster, > so any method to reorganize it is OK. > I don't like your job because of irrational CONDs and disputable LISTCATs (why > ?) > > In general: > 1. Check your clusters using LISTCAT and/or EXAMINE if you want, but > definitely review the output before next step or just skip this step. > 2. Do a backup, of course "manual backup", do not use HSM. It can be REPRO, > EXPORT, or dss DUMP/COPY RENAMEU or whatever. > 2.1 Make sure, your backup is valid. You are allowed to do another backup, > using other method. You are not allowed to proceed if you are unsure about > backup... > 3. Delete CDS (and recreate it) and copy data from the backup to new empty > dataset. > 4. Have a beer... > > BTW: it is good idea to review CDS parameters, especially space allocation. > BTW2: For the step 2 I would consider REPRO OFILE(OUT) with //OUT DD > DISP=(,CATLG),LIKE=INPUT.FILE > > HTH > > -- > Radoslaw Skorupka > Lodz, Poland > > > > > > > > W dniu 2017-03-29 o 16:43, John Dawes pisze: > > G'Day, > > > > I am setting up a reorg job to reorganise the MCDS/BCDS/OCDS because they > have reached the threshold of 95%. > > I checked the doc IBM z/OS DFSMShsm Primer for an example. I noticed that > in the IMPORT step it is using parm IEMPTY: > > IMPORT IDS(?UID.EXPORT.MCDS) ODS(?UID.MCDS) IEMPTY because the cluster is > being redefined. Would it be a problem if I was not deleting the cluster and > performed the IMPORT using the IEMPTY parm? > > I have run a test with the IEMPTY parm and without and they both work. My > question is do I need to use the IEMPTY parm? > > I read in the doc z/OS V1R9.0 DFSMShsm Storage Administration Guide that the > IMPORT function redefines a VSAM data set by using a copy of the catalog > information saved in the EXPORT copy of the data set > > > > Here is my jcl: > > //STEP1 EXEC PGM=IDCAMS,COND=(0,NE) > > //SYSPRINT DD SYSOUT=* > > //SYSIN DD * > > LISTC ENT(SYS2.MCDS) ALL > > /* > > //STEP2 EXEC PGM=IEFBR14,COND=(0,NE) > > //MCDS DD DSNAME=SYS2.MCDS.BKUP,UNIT=SYSALLDA, > > // DISP=(,CATLG,DELETE),SPACE=(CYL,(250,200)) > > /* > > //STEP3 EXEC PGM=IDCAMS,COND=(0,NE,STEP4) > > //SYSPRINT DD SYSOUT=* > > //SYSIN DD * > > EXPORT SYS2.MCDS ODS(SYS2.MCDS.BKUP) TEMPORARY > > /* > > //STEP4 EXEC PGM=IDCAMS,COND=(0,NE) > > //SYSPRINT DD SYSOUT=* > > //SYSIN DD * > > IMPORT IDS(SYS2.MCDS.BKUP) ODS(SYS2.MCDS) IEMPTY > > /* > > //STEP5 EXEC PGM=IDCAMS,COND=(0,NE) > > //SYSPRINT DD SYSOUT=* > > //SYSIN DD * > > LISTC ENT(SYS2.MCDS) ALL > > /* > > > > ---------------------------------------------------------------------- > > For IBM-MAIN subscribe / signoff / archive access instructions, > > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN > > > > > > ====================================================================== > > > -- > Treść tej wiadomości może zawierać informacje prawnie chronione Banku > przeznaczone wyłącznie do użytku służbowego adresata. Odbiorcą może być > jedynie jej adresat z wyłączeniem dostępu osób trzecich. Jeżeli nie jesteś > adresatem niniejszej wiadomości lub pracownikiem upoważnionym do jej > przekazania adresatowi, informujemy, że jej rozpowszechnianie, kopiowanie, > rozprowadzanie lub inne działanie o podobnym charakterze jest prawnie > zabronione i może być karalne. Jeżeli otrzymałeś tę wiadomość omyłkowo, > prosimy niezwłocznie zawiadomić nadawcę wysyłając odpowiedź oraz trwale usunąć > tę wiadomość włączając w to wszelkie jej kopie wydrukowane lub zapisane na > dysku. > > This e-mail may contain legally privileged information of the Bank and > is intended solely for business use of the addressee. This e-mail may only be > received by the addressee and may not be disclosed to any third parties. If > you are not the intended addressee of this e-mail or the employee authorized > to forward it to the addressee, be advised that any dissemination, copying, > distribution or any other similar activity is legally prohibited and may be > punishable. If you received this e-mail by mistake please advise the sender > immediately by using the reply facility in your e-mail software and delete > permanently this e-mail including any copies of it either printed or saved to > hard drive. > > mBank S.A. z siedzibą w Warszawie, ul. Senatorska 18, 00-950 Warszawa, > www.mBank.pl, e-mail: kont...@mbank.plsąd Rejonowy dla m. st. Warszawy XII > Wydział Gospodarczy Krajowego Rejestru Sądowego, nr rejestru przedsiębiorców > KRS 0000025237, NIP: 526-021-50-88. Według stanu na dzień 01.01.2016 r. > kapitał zakładowy mBanku S.A. (w całości wpłacony) wynosi 168.955.696 złotych. > > > ---------------------------------------------------------------------- > 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
