Presentation is loading. Please wait.

Presentation is loading. Please wait.

HORIZONT 1 DSN/Change The Dataset Renaming System HORIZONT Software for Datacenters Garmischer Str. 8 D- 80339 München Tel ++49(0)89 / 540 162 - 0 www.horizont-it.com.

Similar presentations


Presentation on theme: "HORIZONT 1 DSN/Change The Dataset Renaming System HORIZONT Software for Datacenters Garmischer Str. 8 D- 80339 München Tel ++49(0)89 / 540 162 - 0 www.horizont-it.com."— Presentation transcript:

1 HORIZONT 1 DSN/Change The Dataset Renaming System HORIZONT Software for Datacenters Garmischer Str. 8 D München Tel ++49(0)89 / Introduction DSN/Change

2 HORIZONT 2 DSN/Change Table of Contents Renaming Datasets with DSN/Change Specify Production Environment Introduction Rename Financial Benefit Preparation

3 HORIZONT 3 DSN/Change Why renaming datasets? Normally production datasets are not renamed very often. But there are strong arguments to rename datasets from time to time: The number of files is steadily growing, but your naming conventions are too old and have to be adapted You‘ve been integrating other data centers and their naming conventions do not fit into your system.

4 HORIZONT 4 DSN/Change Rename Data Set Command ===> Data Set Name.. : P390A.DCH.V1R1M0.CLIST Volume Serial.. : ROSD01 Enter new name below: (The data set will be recataloged.) ISPF Library: Project.. _________ Group... _________ Type.... _________ Other Partitioned or Sequential Data Set: Data Set Name... 'P390A.DCH.V1R1M0.CLIST' __________________ How to do that? The rename of production datasets requires more than simple ISPF commands. You cannot do that with production files!

5 HORIZONT 5 DSN/Change Which actions are required? 1.Rename datasets Non-VSAM and VSAM files GDG IMS Tapes 2.Change all references pointing to datasets JCL PROCLIB SYSIN, e.g. IDCAMS RACF Profiles JCL variables (symbolic parameters) TWS variables To rename production datasets, following steps must be executed:

6 HORIZONT 6 DSN/Change Renaming datasets with DSN/Change DSN/Change renames datasets automatically. The whole process consists of three steps: 1.Specify production environment Libraries with references to datasets Rename rules JCL modification rules 2.Prepare rename DSN/Change generates new names 3.Physical rename DSN/Change renames datasets DSN/Change modifies references

7 HORIZONT 7 DSN/Change Step 1: Specify production environment Libraries with dataset names – JCLe.g. DSN=MY.OLDFILE – PROCLIBe.g. DSN=MY.&VAR – SYSIN cardse.g. DELETE MY.OLDFILE – REXXe.g. ALLOC “MY.FILE” Rename rules – Rule based (IF - ELSE logic) – Alternative: new names can be specified manually JCL modification rules (optional) – Remove, insert or replace DD parameters (VOLUME, BLKSIZE etc.) – Remove, insert or replace SMS parameters (STORCLASS etc.) First the user has to specify the production environment

8 HORIZONT 8 DSN/Change -- DSN/Change Row 1 of 4 Dataset Status P390A.HORIZONT.JOBLIB 12 S Not done P390A.OPC.JOBLIB 12 S Not done P390A.PROCLIB 12 S Not done USER.PROCLIB 12 S Not done P390A.DATA.SYSIN 12 S Not done How to specify libraries These libraries are scanned for references i Add a JCL library COMMAND ===> DS-Name P390A.PROD.CNTL Scan Intervall (hours) 12 The user specifies a new library The user specifies which libraries should be scanned for references to datasets.

9 HORIZONT 9 DSN/Change DSN/Change Dialog Production Libraries and Datasets DSN/Change Batch Programs DSN/Change Database How to scan libraries Joblib Proclib Clists DSN/Change Scan DSN1 DSN2 DSN3 DSN4 DSN5 -- DSN/Change Row 1 to 2 of JCL Modification Method | | => CSR | Short Description IMSLOG | | Long Description IMS - LOGDATASETS | - | | | JCL-Old Datasets | | Remove VOLUME Y Remove UNIT Y | | Change DSN in Comment Y | | JCL-New Datasets | | | - | Recalculate Space Y Add DATACLASS | | on base of Model 3390 Add STORCLASS SCIMSLOG | | Add RLSE Y Add MGMTCLASS | | Set DISP to CATLG Y | | Remove VOLUME Y Remove DATACLASS Y | | Remove Multivol N Remove STORCLASS N | | Remove Unit Y Remove MGMTCLASS Y | | Remove Label Y Remove Model-DCB Y | | Remove BLKSZ N Set BLKSIZE 1024 | | | User specifies all libraries where datasets are referenced: JOBLIB, PROCLIB, CLIST, SYSIN etc. 2. The libs are scanned for dataset names. The program scans modified or new members. It runs frequently, e.g. day by day. Libs XRef 3. internal references are created an maintained

10 HORIZONT 10 DSN/Change How to define rename rules -- DSN/Change Short Description CHANGE IMS-LOGDATASETS DS-Change Method JCLONLY JCL Change Method IMSLOG Set of Variables Priority of Rule 1 Selective Condition (IF...) IN & = PR New DSN (THEN...) PRIMS... Select “old” names by condition Create “new” names by rules DSN/Change uses conditions and rules to create new names automatically by using “rename rules”.

11 HORIZONT 11 DSN/Change -- DSN/Change Short Description IMSLOG Long Description IMS - LOGDATASETS JCL-Old Datasets Remove VOLUME Y Remove UNIT Y JCL-New Datasets Recalculate Space Y Add DATACLASS on base of Model 3390 Add STORCLASS SCIMSLOG Add RLSE Y Add MGMTCLASS Remove VOLUME Y Remove DATACLASS Y Remove Multivol N Remove STORCLASS N Remove Unit Y Remove MGMTCLASS Y Remove Label Y Remove Model-DCB Y Remove BLKSZ N Set BLKSIZE 1024 How to define JCL modifications SMS Volume, Space, etc. DSN/Change additionally changes DD statements automatically by using “JCL modification rules”.

12 HORIZONT 12 DSN/Change Step 2: Preparation (1) DSN/Change generates new dataset names DSN/Change verifies names (clashes, syntax) DSN/Change analyses variables (&var) DSN/Change analyses RACF Profiles DSN/Change starts mass recall actions DSN/Change generates IMS change jobs DSN/Change defines new GDG physically After the user has defined and libraries and rules, DSN/Change prepares the physical migration.

13 HORIZONT 13 DSN/Change Step 2: Preparation (2) All actions can be simulated (TRY mode) All actions are audited All actions are reversible Physical objects like datasets or JCL are not changed at this time, all modifications are “prepared” internally. Again: The physical objects are changed later. This parting into “preparation” and “physical rename” increases productivity drastically.

14 HORIZONT 14 DSN/Change -- DSN/Change Row 3 of 15 Top: S(hort) L(ong) MAXROW -Set max displ rows RACF ON/OFF SETx - Set Sel Char CAT-Catalogue Line: N-Next Step P-previous Step H-History X-eXclude J-JCL Xref F-force RACF C-Connections =-Repeat Dsname Old Dsname New Status DSNCHG.IVP.AIX2 DSNCHG.IVP.CLU1 DSNCHG.CHECKED.CLU1 Only JCL-Change DSNCHG.IVP.CLU2 DSNCHG.IVP.GDG1 DSNCHG.CHECKED.GDG1 Only JCL-Change DSNCHG.IVP.GDG2 DSNCHG.IVP.PAT1 DSNCHG.CHECKED.PAT1 Only JCL-Change How to “prepare” datasets Commands The preparation is controlled by a dialog program. Here the user initiates all actions step by step. “Old“ Datasets “New“ Datasets

15 HORIZONT 15 DSN/Change DSN/Change Dialog Production Libraries and Datasets DSN/Change Programs DSN/Change Database How rename rules are used Joblib Proclib Clists DSN1 DSN2 DSN3 DSN4 DSN5 -- DSN/Change Row 1 to 2 of JCL Modification Method | | => CSR | Short Description IMSLOG | | Long Description IMS - LOGDATASETS | - | | | JCL-Old Datasets | | Remove VOLUME Y Remove UNIT Y | | Change DSN in Comment Y | | JCL-New Datasets | | | - | Recalculate Space Y Add DATACLASS | | on base of Model 3390 Add STORCLASS SCIMSLOG | | Add RLSE Y Add MGMTCLASS | | Set DISP to CATLG Y | | Remove VOLUME Y Remove DATACLASS Y | | Remove Multivol N Remove STORCLASS N | | Remove Unit Y Remove MGMTCLASS Y | | Remove Label Y Remove Model-DCB Y | | Remove BLKSZ N Set BLKSIZE 1024 | | | User selects datasets to be prepared XRef 3. New names are saved Rules 2. DSN/Change compares the selection part of each rule with dataset names. If a rule applies, it is used for creating new names. Physical datasets and references are not changed at this time!

16 HORIZONT 16 DSN/Change The integrated simulation The TRY mode allows to display planned modifications Change of VAB.SI01.GSC3600 DVB.JOBLIB(GSC3600 ) //UL.UNLOAD DD DSN=VAB.SI01.GSC3600(+1), // DISP=(,CATLG,DELETE), // UNIT=PROD,SPACE=(CYL,(400,20),RLSE), // DCB=(V.GDG,RECFM=VB,LRECL=23472,BLKSIZE=23476) Space calculation:(CYL,(400,20),RLSE) LRECL from DS 624 DCB VG.GDG merged >new>//UL.UNLOAD DD DSN=INBCH.GSC.N360001(+1), >new>// DISP=(,CATLG,DELETE), >new>// SPACE=(624,(434,22),RLSE),AVGREC=K, >new>// RECFM=VB, >new>// LRECL=23472 Dataset Library member referencing the dataset “old“ DD- statement Space calculation “new“ DD- statement

17 HORIZONT 17 DSN/Change Step 3: Rename (1) Lock the dataset (ENQUEUE) Rename the dataset (PS, PO, VSAM, Tape) – GDG keeps absolute numbers – VSAM and components are renamed – TAPE files require CA-1 and last 17 chars unchanged – Old names are kept if an error occurs, e.g. “dataset in use” – “Unrenamable” datasets are copied, e.g. VSAM files to other catalogs After the preparation is done, all physical objects are changed by a batch program. The whole sequence is carried out dataset by dataset.

18 HORIZONT 18 DSN/Change Step 3: Rename (2) Change JCL – JCL is changed after the successful rename (or copy) – Symbolic parameters are changed after successful rename (or copy) – JCL libraries are compressed (if necessary) Rename IMS databases – Lock Database (DBRC NOAUTH) – Rename database – DYNALLOCs are changed – DBRCs are changed (CHANGE.DBDS) – Unlock Database (DBRC AUTH) Unlock the dataset (DEQUEUE) Continue with the next dataset The whole process can be stopped at anytime by a “P-Command“. That guarantees that the program always ends in consistent status.

19 HORIZONT 19 DSN/Change The final report D.ULTIMO.GIA1.G0024V00 recalled D.ULTIMO.GIA1.G0024V00 renamed to A1PBAT.GIA1.ULTIMO.G0024V00 //DD2 DD DSN=D.ULTIMO.GI&GRUPPE(+1), // DISP=(,CATLG,DELETE), // DCB=(MODEL,RECFM=FB,LRECL=80,BLKSIZE=23440), // SPACE=(CYL,(2,1)),UNIT=(SYSDA,5) Spacecalculation:(CYL,(2,1)) >new> //DD2 DD DSN=A1PBAT.GI&GRUPPE..ULTIMO(+1), >new> // DISP=(,CATLG,DELETE), >new> // SPACE=(80,(17,9)),AVGREC=K, >new> // UNIT=(,5), >new> // RECFM=FB, >new> // LRECL=80 D.ULTIMO.GIA1.G0024V00 migrated Recalled Renamed Space calculation “new“ DD- statement “Old” DD- statement Migrated again Finally a report displays all executed modifications.

20 HORIZONT 20 DSN/Change Summary: Financial Benefit The user costs € per year Without DSN/Change: 40 files per day With DSN/Change: 200 files per ½ day The Result:

21 HORIZONT 21 DSN/Change Do you have any further questions? What is with GDGs? And databases? Another started task? And the effort for implementation?

22 HORIZONT 22 DSN/Change Many thanks for your attention HORIZONT Software for Datacenters Garmischer Str. 8 D München Tel ++49(0)89 / The Dataset Renaming System DSN/Change


Download ppt "HORIZONT 1 DSN/Change The Dataset Renaming System HORIZONT Software for Datacenters Garmischer Str. 8 D- 80339 München Tel ++49(0)89 / 540 162 - 0 www.horizont-it.com."

Similar presentations


Ads by Google