Transcript DSN/Change - horizont

DSN/Change
The Dataset Renaming System
Introduction
HORIZONT
Software
HORIZONT for Datacenters1
Garmischer Str. 8
D- 80339 München
Tel ++49(0)89 / 540 162 - 0
www.horizont-it.com
DSN/Change
Table of Contents
Introduction
Renaming Datasets with DSN/Change
Specify Production Environment
Preparation
Rename
Financial Benefit
HORIZONT
2
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.
HORIZONT
3
DSN/Change
How to do that?
The rename of production datasets requires
more than simple ISPF commands.
Rename Data Set
Command ===>
Data Set Name . . : P390A.DCH.V1R1M0.CLIST
Volume Serial . . : ROSD01
Enter new name below: (The data set will be
recataloged.)
You cannot do
ISPF Library:
with production
Project . . _________
Group . . . _________
Type . . . . _________
Other Partitioned or Sequential Data Set:
Data Set Name . . . 'P390A.DCH.V1R1M0.CLIST'
__________________
HORIZONT
4
that
files!
DSN/Change
Which actions are required?
To rename production datasets, following steps must
be executed:
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
HORIZONT
5
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
HORIZONT
6
DSN/Change
Step 1: Specify production environment
First the user has to specify the production environment
• Libraries with dataset names
– JCL
– PROCLIB
– SYSIN cards
– REXX
e.g.
e.g.
e.g.
e.g.
DSN=MY.OLDFILE
DSN=MY.&VAR
DELETE MY.OLDFILE
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.)
HORIZONT
7
DSN/Change
How to specify libraries
The user specifies which libraries should be scanned
for references to datasets.
These
-- DSN/Change ---------------------------- Row 1 of 4
libraries are
Dataset
Status
P390A.HORIZONT.JOBLIB
12 S scanned
Not donefor
P390A.OPC.JOBLIB
12 S references
Not done
P390A.PROCLIB
12 S Not done
USER.PROCLIB
12 S Not done
i P390A.DATA.SYSIN
12 S Not done
Add a JCL library
COMMAND ===>
DS-Name P390A.PROD.CNTL
Scan Intervall (hours)
HORIZONT
8
12
The user
specifies a
new library
DSN/Change
1. User specifies all
libraries where
datasets are
referenced:
JOBLIB, PROCLIB,
CLIST, SYSIN etc.
How to scan libraries
-- DS N/Cha nge ----- ----- ----- ----- ---- ----- ----- ---- Row 1 to 2 of 2
.---- ----- ---- ----- --- J CL Mo dific atio n Met hod - ----- ----- ---- ----- -.
|
|
|
- |
|
|
|
|
|
|
- |
|
Sh ort D escr iptio n
Lo ng De scri ption
I MSLOG
I MS - LOGDA TASE TS
JC L-Old Dat asets ---- ----- ----- ---- ----- ----- ----- ----- --Rem ove VOLUM E
Y
Remo ve UN IT
Y
Ch ange DSN in Co mment Y
JCL-N ew D atase ts -- ----- ----- ---- ----- ----- ----- ----- ---- -
Recal cula te Sp ace
o n ba se of Mode l
Y
3 390
Add DATAC LASS
Add STORC LASS
SCIM SLOG
|
|
|
|
|
A dd R LSE
S et D ISP t o CAT LG
R emov e VOL UME
R emov e Mul tivol
R emov e Uni t
Y
Y
Y
N
Y
Re move DATAC LASS
Re move STORC LASS
Re move MGMTC LASS
Y
N
Y
|
|
|
R emov e Lab el
R emov e BLK SZ
Y
N
Re move Model -DCB
Se t BLK SIZE
Add MGMTC LASS
Y
1024
| => CSR
|
|
| -- ----|
|
|
|
|
|
| -- ----|
Joblib
|
|
|
|
|
|
|
|
.---- ----- ---- ----- ----- ----- ----- ---- ----- ----- ----- ----- ---- ----- -.
Joblib
Libs
DSN/Change Dialog
Proclib
DSN/Change
Scan
XRef
references are
created an
maintained
HORIZONT
DSN2
2. The libs are scanned
3. internal
DSN/Change
Database
Clists
for dataset names. The
program scans modified
or new members. It runs
frequently, e.g. day by
day.
DSN/Change Batch Programs
9
DSN5
DSN1
DSN3
DSN4
Production
Libraries and
Datasets
DSN/Change
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
Select “old” names
JCL Change Method IMSLOG
by condition
Set of Variables
Priority of Rule
1
Selective Condition (IF ...)
<DDNAME> IN <IEFRDER,IEFRDR2> & <O1,1,2> = PR
New DSN (THEN ...)
PRIMS.<O2>.<DDNAME>.<JOBNAME>
HORIZONT
10
Create “new”
names by rules
DSN/Change
How to define JCL modifications
DSN/Change additionally changes DD statements
automatically by using “JCL modification rules”.
-- DSN/Change ----------------------------------------Volume,Short Description IMSLOG
IMS - LOGDATASETS
Space, Long Description
etc. JCL-Old Datasets -------------------------------------Remove VOLUME
Y
Remove UNIT
Y
SMS
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
HORIZONT
11
DSN/Change
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
HORIZONT
12
DSN/Change
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.
HORIZONT
13
DSN/Change
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.CLU1
DSNCHG.CHECKED.CLU1
Only JCL-Change
DSNCHG.IVP.CLU2
“New“ Datasets
DSNCHG.IVP.GDG1
DSNCHG.CHECKED.GDG1
Only JCL-Change
DSNCHG.IVP.GDG2
DSNCHG.IVP.PAT1
DSNCHG.CHECKED.PAT1
Only JCL-Change
“Old“ Datasets
HORIZONT
14
DSN/Change
How rename rules are used
1. User selects
datasets to be
prepared
-- DS N/Cha nge ----- ----- ----- ----- ---- ----- ----- ---- Row 1 to 2 of 2
.---- ----- ---- ----- --- J CL Mo dific atio n Met hod - ----- ----- ---- ----- -.
|
|
|
- |
|
|
|
|
|
|
- |
|
Sh ort D escr iptio n
Lo ng De scri ption
I MSLOG
I MS - LOGDA TASE TS
JC L-Old Dat asets ---- ----- ----- ---- ----- ----- ----- ----- --Rem ove VOLUM E
Y
Remo ve UN IT
Y
Ch ange DSN in Co mment Y
JCL-N ew D atase ts -- ----- ----- ---- ----- ----- ----- ----- ---- -
Recal cula te Sp ace
o n ba se of Mode l
Y
3 390
Add DATAC LASS
Add STORC LASS
SCIM SLOG
|
|
|
|
|
A dd R LSE
S et D ISP t o CAT LG
R emov e VOL UME
R emov e Mul tivol
R emov e Uni t
Y
Y
Y
N
Y
Re move DATAC LASS
Re move STORC LASS
Re move MGMTC LASS
Y
N
Y
|
|
|
R emov e Lab el
R emov e BLK SZ
Y
N
Re move Model -DCB
Se t BLK SIZE
Add MGMTC LASS
Y
1024
| => CSR
|
|
| -- ----|
|
|
|
|
|
| -- ----|
Joblib
|
|
|
|
|
|
|
|
.---- ----- ---- ----- ----- ----- ----- ---- ----- ----- ----- ----- ---- ----- -.
Joblib
DSN/Change Dialog
Proclib
3. New names
XRef
Clists
are saved
2. DSN/Change compares the
Rules
selection part of each rule with
dataset names. If a rule applies, it is
used for creating new names.
DSN2
DSN1
DSN3
Physical datasets and references
are not changed at this time!
DSN/Change
Database
HORIZONT
DSN/Change Programs
15
DSN5
DSN4
Production
Libraries and
Datasets
DSN/Change
The integrated simulation
The TRY mode allows to display planned modifications
Change of VAB.SI01.GSC3600
Dataset
DVB.JOBLIB(GSC3600 )
Library member
referencing the
dataset
//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
“old“ DDstatement
Space
calculation
>new>//UL.UNLOAD DD DSN=INBCH.GSC.N360001(+1),
>new>//
DISP=(,CATLG,DELETE),
“new“ DD>new>//
SPACE=(624,(434,22),RLSE),AVGREC=K,
statement
>new>//
RECFM=VB,
>new>//
LRECL=23472
HORIZONT
16
DSN/Change
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
HORIZONT
17
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)
The whole process can be stopped at anytime by a “P-Command“. That
•guarantees
Continue
with the next dataset
that the program always ends in consistent status.
HORIZONT
18
DSN/Change
The final report
Finally a report displays all executed modifications.
D.ULTIMO.GIA1.G0024V00 recalled
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)
Renamed
“Old” DDstatement
Spacecalculation:(CYL,(2,1))
>new>
>new>
>new>
>new>
>new>
>new>
//DD2
//
//
//
//
//
DD DSN=A1PBAT.GI&GRUPPE..ULTIMO(+1),
DISP=(,CATLG,DELETE),
SPACE=(80,(17,9)),AVGREC=K,
UNIT=(,5),
RECFM=FB,
LRECL=80
D.ULTIMO.GIA1.G0024V00 migrated
HORIZONT
19
Space
calculation
“new“ DDstatement
Migrated again
DSN/Change
Summary: Financial Benefit
• The user costs 75.000 € per year
• Without DSN/Change: 40 files per day
• With DSN/Change: 200 files per ½ day
2.000.000 €
1.800.000 €
Costs without DSN/Change
1.600.000 €
Costs with DSN/Change
1.400.000 €
1.200.000 €
1.000.000 €
HORIZONT
800.000 €
Costs (in EUR, 1 EUR = 0,9 US$)
The Result:
600.000 €
400.000 €
200.000 €
0€
20.000
40.000
60.000
80.000
100.000
150.000
250.000
Datasets
20
DSN/Change
Do you have any further questions?
[email protected]
What is with
GDGs?
And
databases?
And the effort for
implementation?
HORIZONT
Another
started task?
21
DSN/Change
DSN/Change
The Dataset Renaming System
Many thanks for your
attention
HORIZONT
Software
HORIZONT for Datacenters22
Garmischer Str. 8
D- 80339 München
Tel ++49(0)89 / 540 162 - 0
www.horizont-it.com
DSN/Change