Keep DEDB database online

while restructuring it
Jiří Vandas
CA Technologies

Date of presentation (01/11/2016)

Session <HD>
Agenda

• DEDB internal structure description

– Internal structure, mapping to DBD
• Which attributes can be changed
• Prerequisites
– DBRC registration, shadow datasets & image copies
– Staging ACBLIB
• DBFUDA00
– Utility control statements
– Limitations
 DEDB Alter
• Utility included with IMS installation
• Allows to change DEDB Fast Path database layout and
parameters while remaining database online and
available for applications
• Runs as a standard Fast Path IFP utility
Database Description for DEDB
DBD NAME=DEALT,ACCESS=DEDB,RMNAME=(DBFHDC20,2)
*
AREA1 AREA DD1=DEALTDD1,SIZE=1024,UOW=(50,10),ROOT=(100,30)
AREA2 AREA DD1=DEALTDD2,SIZE=1024,UOW=(50,10),ROOT=(100,30)
*
SEGM NAME=SEGROOT,BYTES=300,PARENT=0

RMNAME
Randomizer name and flag for two stage randomizer capability
SIZE
Control Interval (CI) size of VSAM dataset
UOW (Unit Of Work)
Number of CIs per one UOW
Subset of Cis dedicated to Dependent overflow part
ROOT
Number of UOWs in both Root addressable and Independent overflow part
Number of UOWs in Independent overflow part
Structure of DEDB area
Root addressable part Independent overflow Sequential dependent data

UOW
CI CI

CI CI CI
CI
Base part
CI CI
CI CI
CI CI
CI CI
CI CI
CI CI
CI CI
CI CI
Dependent
overflow CI CI
CI CI
part
CI CI
What you can change in IMS v13
DBD NAME=DEALT,ACCESS=DEDB,RMNAME=(DBFHDC20,2)
*
AREA1 AREA DD1=DEALTDD1,SIZE=1024,UOW=(50,10),ROOT=(100,30)
AREA2 AREA DD1=DEALTDD2,SIZE=1024,UOW=(50,10),ROOT=(100,30)
AREA3 AREA DD1=DEALTDD3,SIZE=1024,UOW=(50,10),ROOT=(100,30)
*
*
SEGM NAME=SEGROOT,BYTES=300,PARENT=0

• Physical DEDB area attributes like Control Interval size, sizes of various
parts and overflows
• Randomizer name for the entire DEDB database
What you can change in IMS v14
DBD NAME=DEALT,ACCESS=DEDB,RMNAME=(DBFHDC20,2)
*
AREA1 AREA DD1=DEALTDD1,SIZE=1024,UOW=(50,10),ROOT=(100,30)
AREA2 AREA DD1=DEALTDD2,SIZE=1024,UOW=(50,10),ROOT=(100,30)
AREA3 AREA DD1=DEALTDD3,SIZE=1024,UOW=(50,10),ROOT=(100,30)
AREAxx add new area definition here…
*
SEGM NAME=SEGROOT,BYTES=300,PARENT=0,
COMPRTN=(IMEXPRES,DATA,INIT)

• Physical DEDB area attributes like Control Interval size, sizes of various
parts and overflows
• Randomizer name for the entire DEDB database
• Add one or more DEDB areas
• Add segment edit/compression routine. The change or removal is not
allowed.
The process in the nutshell

One time settings actions

• Create staging ACB library
• Update GENMAX to accommodate additional shadow image copies
• Allocate & register shadow area data set to DBRC

For every execution

• Prepare and generate new ACB member
• Reallocate shadow area data sets and initialize them using
DBFUMIN0
• Allocate and register new shadow image copy for area
• Execute DBFUDA00 utility
New options in PROCLIB(DFSDFxxx)

• All new options are located in section

<SECTION=FASTPATH>
• ACBSHR
– Specifies whether ACB library is shared among IMS systems.
Possible options are Yes or No. It allows to automatically share
new ACB across IMS plex.
• ALTERGRP
– The Name of DEDB Alter data-sharing group. It must be
specified for each data sharing IMS system, which wants to
participate in DEDB ALTER process.
• ALTERHLQ
– High level qualifier for temporary data sets.
IMS staging ACBLIB

• Contains the new version on generated DBDs with

structural changes
• Different from ACBLIBA and ACBLIBB libraries
• Can be shared/reused with the one for HALDB ALTER
• The new library must be allocated by IMS under the
ACBLIB DD:

• Can be hardcoded in IMS Control Region in JCL:

//IMSACB DD DISP=SHR,DSN=IDI.IMSJ.ACBLIB
– When running ACBGEN, you are not able to get exclusive
access unless shutting down IMS region
IMS staging ACBLIB

• Dynamically allocate by IMS from DFSMDA member

• Compile and link-edit. The output must be placed in IMSACB named

load module, which needs to be in IMS control region STEPLIB
concatenation
Recon requirements

• Upgrade Recon MINVER at least to 13.1

– Sufficient level for using both IMS v13 or IMS v14 features
– IMS regions themselves must be on proper release v13 or v14
• All data sharing systems must be upgraded to the same release

• DEDB database and all areas must be registered in

DBRC
– When using Multiple area data sets database is already
registered
– Use INIT.DB, INIT.DBDS and INIT.ADS
Shadow data sets

• Need to additionally allocate Shadow database data set

– IDCAMS allocations according to the new DBD changes

• Register data set into DBRC for particular area

INIT.ADS DBD(DEALT) AREA(DEALTDD1) -
ADDN(DEALTDB1) -
ADSN(IDI.VANJI01.DEALTDT1) -
SHADOW

• Both ADDN and ADSN names must be unique within DBRC

• For Multiple area data sets you must allocate the same number of
shadow data sets (max. 6) unless you want to change them
– Allocate one resp. multiple if you want to disable resp. enable MADS
Shadow data sets

• Pre-allocate Shadow database image copy

– IDCAMS allocations according to the new DBD changes

• Register image copy into DBRC for particular area

INIT.ADS DBD(DEALT) AREA(DEALTDD1) -
ADDN(DEALTDC1) -
ADSN(IDI.VANJI01D.IC3.DEALT.DEALTDT1) -
SHADOW IC

• Increase CHANGE.DBDS GENMAX value to accommodate new

image copy taken during execution
Shadow data sets

• To check registration use LIST.DBDS

• Problems:
After running DEDB ALTER these data sets will be swapped and
the shadow data set becomes active  you always need to refer to
DBRC for active data set names, which makes difficult to have
areas allocated in JCL directly.
Initialize shadow area / data set

• Make sure to ACBGEN the modified DBD and PSBs

• Initialize shadow data set by standard DBFUMIN0 utility
– Needs to run with Recon data sets
– ACBLIB points to staging ACB library
– Specify area and SHADOW argument: default is active data set !
Initialize shadow area / data set

• Problem: Omit shadow data set and image copy allocations in JCL
DFS3725I AREA=DEALTDD1 JCL DD STATEMENT DOES NOT
EXIST
– Bit more complicated to have a prepared (automatic) job already
because data set names for area are changing/switching

• Problem: Reallocate shadow data set according to new DBD

changes
DFS2509I DEFINED CI SIZE IN CATALOG NOT
CONSISTENT WITH DBD SIZE PARM
– To fix follow/copy DBDGEN recommended VSAM define cluster
parameters
Initialize shadow area / data set

• Problem: Reallocate shadow data set according to new DBD

changes
DFS4620E DEDB ALTER VALIDATION ERROR: SHADOW AREA
SDEP PART IS LESS FOR ALTERAREA FUNCTION
– Applicable only when using Sequential Dependent Segments
– Message from DEDB ALTER utility, but needs to be fixed in this
step
– The new SDEP part can not be smaller than existing SDEP part
– New primary allocation = new RA + new IOVF + old SDEP
• New RA and IOVF size: calculate from new DBD
• Old SDEP size: calculate from old DBD or check /DISPLAY AREA output or
pointer checker tool
Run DEDB Alter utility DBFUDA00

• Running in IFP region

• Available functions:
– ALTERAREA area_name
– ADDAREA
– REPLRAND
Optional control statements

• TIMEOUT, RETRY, RETRYWAIT

– Applicable since IMS v13
– Allows utility to suspend applications in the end of the process to
synchronize shadow area data set with active area and commit
structural changes of DEDB
– Defines the length of timeout for looking of quite point for a
switch (default 15 seconds)
– If the process fails, how many times it should be repeated (with
how long pause in between)
Optional control statements

• PHYSICAL option for ALTERAREA

– Applicable in IMS v14
– Applicable only when Sequential dependent segments are used
– ADJNO: Does not adjust the SDEP logical begin to the first
SDEP CI of the SDEP part in the shadow area data set.
PHYSICAL ADJNO is the default.
– ADJYES: Adjusts the SDEP logical begin to the first SDEP CI of
the SDEP part in the shadow area data set, dissolves the
wraparound state of the SDEP part, and reduces the size of the
SDEP segments processed. The cycle count is reset to 1 for the
SDEP logical begin.
Optional control statements

• UNKEYSEG option for ALTERAREA

– Applicable since IMS v13
– NONE: If any un-keyed segments are defined in the DEDB
definition, the utility will terminate.
– ISRTFILA: The DEDB Alter utility is allowed to run if un-keyed
segments are inserted with FIRST or LAST rule. Detection of any
other update leads to utility termination.
– ALL: The utility is allowed to run and processes updates that
involve un-keyed segments, but various rules applies.
Limitations…

• IMS v13 limitation

– DEDB database areas with sequential dependent (SDEP)
segments that are defined cannot be altered.
• IMS v13 and IMS v14 limitations
– Databases in Virtual Storage Option (VSO) mode or Shared
Virtual Storage Option (SVSO) mode are not directly supported.
 You have to unload them back to DASD using /VUNLOAD
command before the execution.
– Only one area per DEDB can be altered at the same time
• But multiple instances of utility can run concurrently on different DEDBs
Two stage randomizer limitation

• To use all DEDB Alter features, real two stage

randomizer is necessary
– Randomizer must always based on the key assign the root segment into
the same area regardless number of areas or current sizes of overflow
parts etc.
– Typically such randomizer must be table-driven
• IBM IMS provided randomizer DBFHDC20 and
DBFHDC24
– Is not real two stage randomizer
– But still key will not move between areas even if the total number of
RAPs in the DEDB area changes.
– Usable only for ALTERAREA to change the ROOT or UOW parameters
for any particular areas in the DBD.
– Impossible to use when doing ADDAREA !
Session feedback

• Please submit your feedback at

http://conferences.gse.org.uk/2016/feedback/HD

• Session is HD