DSNChange

1
DSN/Change
The Dataset Renaming System
Product Presentation
HORIZONT Software for Datacenters
Garmischer Str. 8 D- 80339 München Tel 49(0)89
/ 540 162 0www.horizont-it.com
2
Table of Contents
Introduction
Renaming Datasets with DSN/Change
Specify Production Environment
Preparation
Rename
Financial Benefit
3
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
• Youve been integrating other data centers and
  their naming conventions do not fit into your
  system.

4
How to do that?
The rename of production datasets requires more
than simple ISPF commands.
Rename Data Set
Command gt

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'
__________________
You cannot do that with production files!
5
Which actions are required?
To rename production datasets, following steps
must be executed

• Rename datasets
• Non-VSAM and VSAM files
• GDG
• IMS
• Tapes
• Change all references pointing to datasets
• JCL
• PROCLIB
• SYSIN, e.g. IDCAMS
• RACF Profiles
• JCL variables (symbolic parameters)
• TWS variables

6
Renaming datasets with DSN/Change
DSN/Change renames datasets automatically. The
whole process consists of three steps

• Specify production environment
• Libraries with references to datasets
• Rename rules
• JCL modification rules
• Prepare rename
• DSN/Change generates new names
• Physical rename
• DSN/Change renames datasets
• DSN/Change modifies references

7
Step 1 Specify production environment
First the user has to specify the production
environment

• Libraries with dataset names
• JCL e.g. DSNMY.OLDFILE
• PROCLIB e.g. DSNMY.VAR
• SYSIN cards e.g. DELETE MY.OLDFILE
• REXX e.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.)

8
How to specify libraries
The user specifies which libraries should be
scanned for references to datasets.
-- 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
These libraries are scanned for references
i
Add a JCL library COMMAND gt
DS-Name P390A.PROD.CNTL Scan Intervall
(hours) 12
The user specifies a new library
9
How to scan libraries
1. User specifies all libraries where datasets
are referenced JOBLIB, PROCLIB, CLIST, SYSIN
etc.
DSN/Change Dialog
Production Libraries and Datasets
DSN/Change Database
Libs
DSN/Change Batch Programs
DSN/Change Scan
XRef
2. The libs are scanned for dataset names. The
program scans modified or new members. It runs
frequently, e.g. day by day.
3. internal references are created an maintained
10
How to define rename rules
DSN/Change uses conditions and rules to create
new names automatically by using 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 ...) ltDDNAMEgt IN
ltIEFRDER,IEFRDR2gt ltO1,1,2gt PR New DSN (THEN
...) PRIMS.ltO2gt.ltDDNAMEgt.ltJOBNAMEgt
Select old names by condition
Create new names by rules
11
How to define JCL modifications
DSN/Change additionally changes DD statements
automatically by using JCL modification rules.
-- 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
Volume, Space, etc.
SMS
12
Step 2 Preparation (1)
After the user has defined and libraries and
rules, DSN/Change prepares the physical migration.

• 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

13
Step 2 Preparation (2)
Physical objects like datasets or JCL are not
changed at this time, all modifications are
prepared internally.

• All actions can be simulated (TRY mode)
• All actions are audited
• All actions are reversible

Again The physical objects are changed later.
This parting into preparation and physical
rename increases productivity drastically.
14
How to prepare datasets
The preparation is controlled by a dialog
program. Here the user initiates all actions step
by step.
Commands
-- 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.CL
U1 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
New Datasets
Old Datasets
15
How rename rules are used
1. User selects datasets to be prepared
DSN/Change Dialog
Production Libraries and Datasets
DSN/Change Database

XRef
3. New names are saved
DSN/Change Programs
2. DSN/Change compares the selection part of each
rule with dataset names. If a rule applies, it
is used for creating new names.
Rules
Physical datasets and references are not changed
at this time!
16
The integrated simulation
The TRY mode allows to display planned
modifications
Library member referencing the dataset
Change of VAB.SI01.GSC3600 DVB.JOBLIB(GSC3600 )
//UL.UNLOAD DD DSNVAB.SI01.GSC3600(1),//
DISP(,CATLG,DELETE), // UNITPROD,SPACE(CYL
,(400,20),RLSE), // DCB(V.GDG,RECFMVB,LRECL
23472,BLKSIZE23476) Space calculation(CYL,(40
0,20),RLSE) LRECL from DS 624 DCB VG.GDG
mergedgtnewgt//UL.UNLOAD DD DSNINBCH.GSC.N360001(
1), gtnewgt//
DISP(,CATLG,DELETE), gtnewgt//
SPACE(624,(434,22),RLSE),AVGRECK,
gtnewgt// RECFMVB,
gtnewgt// LRECL23472
Dataset
old DD- statement
Space calculation
new DD-statement
17
Step 3 Rename (1)
After the preparation is done, all physical
objects are changed by a batch program. The whole
sequence is carried out dataset by dataset.

• 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

18
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
The final report
Finally a report displays all executed
modifications.
Recalled
D.ULTIMO.GIA1.G0024V00 recalledD.ULTIMO.GIA1.G00
24V00 renamed to A1PBAT.GIA1.ULTIMO.G0024V00 //DD
2 DD DSND.ULTIMO.GIGRUPPE(1),//
DISP(,CATLG,DELETE), // DCB(MODEL,RECFMFB
,LRECL80,BLKSIZE23440),
// SPACE(CYL,(2,1)),UNIT(SYSDA,5)
Spacecalculation(CYL,(2,1)
) gtnewgt //DD2 DD DSNA1PBAT.GIGRUPPE..ULTIMO(
1), gtnewgt // DISP(,CATLG,DELETE)
, gtnewgt //
SPACE(80,(17,9)),AVGRECK,gtnewgt //
UNIT(,5), gtnewgt //
RECFMFB, gtnewgt //
LRECL80 D.ULTIMO.GIA1.G0024V00 migrated
Renamed
Old DD-statement
Space calculation
new DD-statement
Migrated again
20
Summary Financial Benefit

• The user costs 75.000 per year
• Without DSN/Change 40 files per day
• With DSN/Change 200 files per ½ day

The Result
21
Do you have any further questions?
Info_at_Horizont-it.com
What is with GDGs?
And databases?
Another started task?
And the effort for implementation?
22
DSN/Change
The Dataset Renaming System
Thank you very much for your attention
HORIZONT Software for Datacenters
Garmischer Str. 8 D- 80339 München Tel 49(0)89
/ 540 162 0www.horizont-it.com