Pre-Con Ed: Introduction to CA Datacom Key Concepts and Facilities Part II

World®
’16
Introduction to CA Datacom
Key Concepts and Facilities - Part II
Dale Russell
Director Software Engineering and Product Owner
CA Technologies
MAINFRAME AND WORKLOAD AUTOMATION
MFX68EB

2 © 2016 CA. ALL RIGHTS RESERVED.@CAWORLD #CAWORLD
Abstract
This is a multi-part session targeted towards the new CA
Datacom DBA or systems programmer. The session covers the
key concepts and facilities for implementing and managing the
CA Datacom environment.Director Software
Engineering and
Product Owner
CA Technologies
Dale Russell

Module 5: DBUTLTY

Agenda
DEFINE THE PURPOSE OF DBUTLTY
PERFORM IMPORTANT DBUTLTY TASKS
GENERATE DBUTLTY REPORTS
1
2
3

DBUTLTY
§ What we’ll talk about
– What DBUTLTY is
– Review of major functions
– Master List (DBMSTLST)

DBUTLTY
§ Batch program
§ Performs all utility functions for databases and system areas
§ Keyword driven, not positional
§ Statements can be executed individually or in groups
§ CA Datacom/DB messages and return codes are issued for any
failure/error
What is it?

DBUTLTY
§ Standard condition codes are generated for each DBUTLTY step
§ Statements are echoed along with results
§ STATUS command available through console – monitors
progress of long-running functions
What is it?

Major Functions
§ System area maintenance
§ CXX Database definition maintenance
§ Multi-User Control
§ Data handling

Major Functions
§ Reporting
§ Recovery
§ Accounting
§ Error handling
§ Resource measurement and monitoring
Continued

System Area Maintenance
§ INIT
– AREA=CXX,CXXNAME=name,DATACOM=DB/AD
– AREA=LXX,BLKSIZE=32760,VARIABLE=YES/NO,TSN=nnnnnnnnn
– AREA=FXX,BLKSIZE=32760,TASKS=1-9999
§ RESET
– AREA=CXX,DBID=nnnn,REPLY=NO/YES
– AREA=LXX (only to be used on very rare or special occasions!!!!!)

System Area Maintenance
§ BACKUP
– AREA=CXX,DDNAME=outdd
– AREA=CXX,DDNAME=outdd,DBID=nnnn
§ LOAD
– AREA=CXX,DDNAME=indd
– AREA=CXX,DDNAME=indd,DBID=nnnn,NEWDBID=nnnn
– AREA=CXX,DDNAME=indd,DBID=nnnn
Continued

CXX Database Definition Maintenance
§ CXXMAINT
– OPTION=ALTER,CBSUSE=YES/NO,DBID=nnnn,KEYNAME=keynm,
TABLE=ttt
– OPTION=ALTER,DSN=new.dataset.name,DBID=nnnn,AREA=aaa
– OPTION=ALTER,DSOP=0-5,DBID=nnnn,AREA=aaa
§ The following were performed by the Version 14.0 upgrade
– OPTION=ALTER,OPTION2=Y_DATAFS
– OPTION=ALTER,OPTION2=Y_DATAHU
– OPTION=ALTER,OPTION2=Y_AREAEV
– OPTION=ALTER,CXXENQ=SYSPLEX

§ CXXMAINT DDPROD,DDNAME=ddcfbld.output.dataset,
NEWDBID=nnnn
Note: Use may be restricted to DATA-DICT and DDD-DATABASE in future
versions, so it is strongly recommended that its use for any other
database be discontinued. The DDUPDATE CATALOG, DDOL CATALOG or
DDCFBLD -CXX CATALOG should be used instead.
Continued

§ CXXMAINT OPTION=DELETE,DBID=nnnn,TABLE=ttt
§ CXXMAINT OPTION=PURGE,DBID=nnnn
§ LINK DBID=nnnn
§ REMOVE AREA=IXX,DBID=nnnn,KEYID=nnn
Continued

Multi-User Control
§ ACCESS
– STATUS=OFF/READ/UTLTY/MAINT/NOMAINT/WRITE,
– USERS=FAIL/WAIT/IGNORE,DBID=nnnn,AREA=aaa
§ COMM
– OPTION=CLOSE,DBID=nnnn,AREA=aaa,IGN68=YES/NO
– OPTION=REQABORT,REQSEQNO=nnnnnnn,IGN68=YES/NO

Multi-User Control
§ COMM
– OPTION=ALTER,RCERROR=eeeii,BUFFERS=YES/NO,MASTERL=YES/NO
– OPTION=ALTER,DUMPS=type,JOBNAME=jobname,TERMID=terminal
§ type EXAMPLES: ARRAY/GLOBALA/PLAN/LUW/TASK/URT
– OPTION=ALTER,TRACE=class,JOBNAME=jobname,TERMID=terminal
§ class EXAMPLES: TRACEERR/TRACERAT/TRACEPLAN
– See DBUTLTY Reference Guide for complete list
Continued

Multi-User Control
§ COMM OPTION=
– EOJ, EOJOFF, EOJKEEP, EOJFREE
– CLRPXX
– NEWRXX
– SNAP, SNAPCSA, SNAPSVC
– STATS
– STATUS
– SYSTEMDBID_DELETE
Continued

Multi-User Control
§ COMM OPTION=CONSOLE,OPTION2=‘console/console-like
command’
– ‘COVERED_ADD 237,A01,1G,F,75’
– ‘COVERED_DELETE 237,A01’
– ‘DYNAMIC_EXTEND 1440,XYZ,300,CYL’
– ‘NEWCOPY module-name’
– ‘QUIESCE OFF/TXN/REQ’
– ‘VIRTUAL_ADD 101,A25,200M’
§ FLEXPOOL
– OPTION=ADD/DELETE,AREA=DATA/DATA2/DXX/IXX,NUMBER=nnnn
Continued

Data Handling
§ Initializing index and data areas
§ Loading data areas
§ Extracting information from data areas
§ Reorganizing large data areas
§ Maintaining index and/or data areas

Data Handling
§ INIT
– AREA=IXX,DBID=nnnn,VERIFY=NO/YES,MULTUSE=NO/YES,BLKSIZE=nnn
nn,OLDEP=YES/NO
– AREA=aaa,DBID=nnnn,MULTUSE=NO/YES,VERIFY=NO/YES
– IXXAREA=***,DBID=nnnn,VERIFY=NO/YES,MULTUSE=NO/YES,
– BLKSIZE=nnnnn,OLDEP=YES/NO
– IXXAREA=Inn,DBID=nnnn,VERIFY=NO/YES,MULTUSE=NO/YES,
– BLKSIZE=nnnnn,OLDEP=YES/NO
– NOTE: If a DD statement is present in the JCL, the data set name on the
DD statement will replace the data set name in the CXX
Continued

Data Handling
Blocks formatted to CA Datacom/DB requirements
First block updates with control information
INIT diagram

Data Handling
§ LOAD (database level)
– DBID=nnnn,DDNAME=indd,FORMAT=backup/none,
– SORT=nnnnnnn,OPTIMIZE=NO/YES,KBYTES=nnn,
– INDEX=YES/NO,CLUSTER=SPARSE/DENSE,
– LOADID=NO/YES,LOADDUPS=NO/YES,REMAP=fffttt,
– OPTION1=NOF/’(I)’/’(U)’,RESETRCE=YES/NO,
– SLACK=nnnn,SORTWK=0-99,STATS=YES/NO
– NOTE: ‘INIT AREA=IXX’ REQUIRED AHEAD OF FULL DATABASE LOADS
Continued

Data Handling
§ LOAD (area level)
– DBID=nnnn,AREA=aaa,TABLE=ttt,DDNAME=indd,
– FORMAT=backup/extract/var/none,SORT=nnnnnnn,
– OPTIMIZE=NO/YES,KBYTES=nnn,INDEX=YES/NO,
– URI=YES/NO,CLUSTER=SPARSE/DENSE,
– LOADID=NO/YES,LOADDUPS=NO/YES,REMAP=fffttt,
– OPTION1=NOF/’(I)’/’(U)’,RESETRCE=YES/NO,
– SLACK=nnnn,SORTWK=0-99,STATS=YES/NO,
– MISMATCH=IGNORE
Continued

Data Handling
§ MASSADD
– DBID=nnnn,DDNAME=indd,TABLE=aaa,MULTUSE=NO/YES,
STARTAFT=nnnnnnn
§ REPLACE
– DBID=nnnn,TABLE=ttt,DDNAME=indd,MULTUSE=NO/YES,
SORT=nnnnnnn,LOADPTN=SKIP/FAIL,SLACK=nnnn
Continued

Data Handling
LOAD diagram

Data Handling
§ RETIX (database level)
– DBID=nnnn,SORT=nnnnnnn,OPTIMIZE=NO/YES,
OPTION1=NOF/’(I)’/’(U)’,VERIFY=NO/YES,SORTWK=nn
§ RETIX (area level)
– DBID=nnnn,AREA=aaa,SORT=nnnnnnn,OPTIMIZE=NO/YES,
OPTION1=NOF/’(I)’/’(U)’,VERIFY=NO/YES,SORTWK=nn,
MULTUSE=NO/YES,MINIMAL=NO/YES
Continued

Data Handling
RETIX diagram

Data Handling
§ EXTEND
– DBID=nnnn,AREA=aaa,MULTUSE=NO/YES
– DBID=nnnn,AREA=IXX,MULTUSE=NO/YES
– DBID=nnnn,IXXAREA=aaa,MULTUSE=NO/YES
Continued

Data Handling
§ BACKUP
– DBID=nnnn,SEQ=native/physical,DDNAME=outdd,RECID=NO/YES,
CMPRS=NO/YES,EXCLUDE=ttt,INCLUDE=ttt
– DBID=nnnn,AREA=aaa,SEQ=NATIVE,DDNAME=outdd,RECID=NO/YES,
CMPRS=YES/NO,MULTUSE=NO/YES,FIRSTKEY=key-value,
LASTKEY=key-value,EXCLUDE=ttt,INCLUDE=ttt
– DBID=nnnn,AREA=aaa,SEQ=PHYSICAL,DDNAME=outdd,RECID=NO/YES,
CMPRS=YES/NO,MULTUSE=NO/YES,FIRSTKEY=key-value,
LASTKEY=key-value,UPDATE=NO/YES,EXCLUDE=ttt,INCLUDE=ttt
Continued

Data Handling
§ EXTRACT
– DBID=nnnn,AREA=aaa,TABLE=ttt,SEQ=NATIVE,DDNAME=outdd,
MULTUSE=NO/YES,SLACK=nnn,SEQBUFS=0-256,BLKSIZE=nnnnn
– DBID=nnnn,AREA=aaa,TABLE=ttt,SEQ=PHYSICAL,DDNAME=outdd,
UPDATE=NO/YES,SLACK=nnn,SEQBUFS=0-256,BLKSIZE=nnnnn
§ LOAD
– OPTION=MOVER,DBID=nnn,AREA=aaa
§ UNLOCK
– OPTION=MOVER,DBID=nnn,AREA=aaa
Continued

Data Handling
§ EXTBKUP
– FILEOUT DDNAME=outdd,TABLE=ttt
– EXTBKUP DDNAME=indd
– NOTE: Both functions must be present in the same DBUTLTY execution
Continued

Data Handling
§ Examples
– BACKUP DBID=001,DDNAME=DB001BK,SEQ=NATIVE
– BACKUP DBID=001,DDNAME=DB001BK,SEQ=PHYSICAL,RECID=YES
– BACKUP DBID=001,DDNAME=DB001BK,SEQ=PHY,EXCLUDE=PMF
– BACKUP DBID=001,DDNAME=DB001BK,SEQ=PHY,INCLUDE=PAY,
MULTUSE=YES,CMPRS=NO
Continued

Data Handling
§ Examples (contd)
– EXTRACT DBID=2009,DDNAME=EXTOUT,SEQ=NATIVE,AREA=AR2,
TABLE=MNT
– EXTRACT DBID=001,DDNAME=PMFOUT,SEQ=PHY,AREA=PMF,
TABLE=PMF,MULTUSE=YES
– FILEOUT DDNAME=PMFOUT,TABLE=PMF
– EXTBKUP DDNAME=DB001BK
Continued

Data Handling
BACKUP diagram

Data Handling
§ DEFRAG
– DBID=nnnn
– DBID=nnnn,KEYID=kkk,PERCENT=nn,FIRSTKEY=key-value,
LASTKEY=key-value
§ VERINDEX
– DBID=nnnn,OPTION=DATAINDEX/INDEXDATA,TABLE=ttt,
KEYNAME=ALL/keynm
§ OLREORG
– DBID=nnnn,TABLE=ttt,REFGROUP=0-100,NUMBER=nnnnn,
– FIRSTKEY=key-value,LASTKEY=key-value
Continued

Data Handling
§ REORG
– OPTION2=BACKUPONLY,AREA=aaa,DBID=nnnn,INNUM=n,
DDNAME=outdd,MULTUSE=NO/YES,CYCLE=n,SEQBUFS=0-256
– OPTION2=LOADONLY,AREA=aaa,DBID=nnnn,INNUM=n,
DDNAME=outdd,MULTUSE=NO/YES,FORMAT=BACKUP/EXTRACT,
TABLE=ttt,KBYTES=nnn,CYCLE=n,SEQBUFS=0256,SLACK=nnn,
RESETRCE=NO/YES
– OPTION2=BACKUPLOAD,AREA=aaa,DBID=nnnn,INNUM=n,
DDNAME=outdd,MULTUSE=NO/YES,FORMAT=BACKUP/EXTRACT,
TABLE=ttt,KBYTES=nnn,CYCLE=n,SEQBUFS=0-256,SLACK=nnn,
RESETRCE=NO/YES
Continued

Reporting
– AREA=CXX ,TYPE=(A,B,I)
– AREA=IXX,TYPE=(A,B,D,E, or G) (MUF must be up)
– AREA=LXX
– AREA=RXX
– AREA=PXX
– DEVICE=3390
– MEMORY=(MVS,CF or DS)
– TYPE=H (history report, MUF must be up)
– TYPE=DATANE (MUF must be up)
– TYPE=U (debugging report)

Reporting
§ Report types
– TYPE=A (space utilization)
– TYPE=B (key, element, field information suppressed)
– TYPE=I (catalog impact, MUF must be up)
§ Report scope reduced by using ‘DBID=‘ keyword
– AREA=CXX,DBID=001
– AREA=CXX,DBID=101,DBID=109,DBID=123,DBID=75
– AREA=CXX,DBID=2-15
REPORT AREA=CXX

Reporting – CXX (contd)
DATA AREA SPACE UTILIZATION REPORT
AREA DATA TOTAL TOTAL TOTAL USED PERCENT PARTIALLY AREA REUSE
NAME BASE TRACKS RECORDS BLOCKS BLOCKS FULL MAX EMPTY BLKS OPTION
CXX 100 N/A 1,200 631 52 52 N/A N/A
IXX 1 11 N/A 132 15 11 11 N/A N/A
DEM 1 5 17 165 12 7 7 10 CLUSTERING
PAY 1 15 200 495 13 2 2 0 NO RECLAMATION
PMF 1 20 200 660 17 2 2 0 NO RECLAMATION
IXX 2 300 N/A 3,600 942 26 26 N/A N/A
DD1 2 2,700 19,209 2,400 1,114 3 3 0 RANDOM
TYPE=A Report

DATA BASE INFORMATION
DBCRBAS REQUIREMENTS FOR THIS BASE - 1,840
DBCRKEL REQUIREMENTS FOR THIS BASE - 1,624
NUMBER OF AREAS IN THIS BASE - 3
NUMBER OF TABLES IN THIS BASE - 6
NUMBER OF KEYS IN THIS BASE - 11
NUMBER OF ELEMENTS IN THIS BASE - 21
LAST OPENED - DATE--7/11/2012, TIME-09.25.26
LAST RESTARTED - DATE--7/09/2012, TIME-13.55.06
LAST MAINTAINED - DATE--4/09/2012, TIME-14.03.56
TYPE=B Report – Page 1

REPLICATED BASE - NO BASE FORMAT - 2
PARTITIONED BASE - NO
UPDATE USERS - 0
READ ONLY USERS - 0
OCCURRENCE - HUMAN-RESOURCE P001
SQL SECURITY - NO
TYPE=B Report – Page 1 continued

INDEX INFORMATION - IXX
DEVICE TYPE - 3390 DYNAMIC EXTEND - NO
BLOCK LENGTH - 4,096 DYN.EXT.TRACKS - 0
LEVELS - 1 OLDEP - YES
BLOCKS/TRACK - 12 CXXMAINT LINK - YES
BLOCKS IN USE - 15
BLOCKS UNUSED - 117
TOTAL BLOCKS - 132
TOTAL TRACKS - 11
PERCENT FULL - 11
DATA SET NAME - DCMLV2.DB12.IXX001 INDEX DTF/DDNAME - IXX001
VOLUMES - DCMSP1

TABLE NAME - PNC AREA NAME - DEM
OCCURRENCE - DEMO-DEM-PNC P001 OCCURRENCE - DEMO-DEM P001
TABLE ID - 6 AREA SQLNAME - DEMO_DEM
RECORD LENGTH - 14 / 26 BLOCK LENGTH - 1,024 SLACK - 0
RECORDS IN TABLE - 5 OVERFLOWS IN AREA - 0
LENGTH OF KEY/ELEMENTS - 176 BLOCKS IN USE - 12
NUMBER OF KEYS - 1 BLOCKS UNUSED - 153
NUMBER OF ELEMENTS - 3 TOTAL BLOCKS - 165 CXXMAINT LINK - YES
CHANGE MASTER KEY - NO TOTAL TRACKS - 5 DYNAMIC EXTEND - YES
DUPLICATE MASTER KEY - NO PERCENT FULL - 7 DYN.EXT.TRACKS - 0

RECOVER - YES DEVICE TYPE - 3390
LOGGING - YES BLOCKS/TRACK - 33
PIPELINE - YES DSOP MODE - BASIC
DB COMPRESSION - NO TABLE LOADED - YES, DATE--7/09/2012, TIME-14.01.53
USER COMPRESSION - NO INDEX LOADED - YES
CLUSTER KEY ID - 0 DATADICTIONARY BASE - 2
CLUSTER KEY LENGTH - 3 DATA BASE ID CHANGE - NO
DEFINITION POSTED VIA - LOAD FROM BACKUP
AUTHID - SYSUSR SQL-INTENT - Y
TABLE SQLNAME - DEMO_DEM_PNC UNIQUE ROW IDENTIFIERS (URI) - 17
TYPE=B Report – Page 3 continued

IMPACT REPORT
BASE AREA TABLE ID DISPOSITION
1 DEM PNC 006 LOADED
PNM 005 LOADED
POH 003 LOADED
POL 004 LOADED
PAY PAY 001 LOADED
PMF PMF 002 LOADED
TYPE=I Report

Reporting – IXX
REPORT
AREA=IXX,DBID=n,TYPE=A (table name sequence)
AREA=IXX,DBID=n,TYPE=B (keyid sequence)
AREA=IXX,DBID=n,TYPE=D,KEYID=nnn (dump of DXX)
AREA=IXX,DBID=n,TYPE=E,KEYID=nnn (dump of IXX)
AREA=IXX,DBID=n,TYPE=G (unique key value count)
AREA=IXXAREA,……… (multi-dataset index reports)
Reminder: MUF must be up
Types

Reporting – IXX
INDEX POPULATION REPORT - BY TABLE
TABLE KEY ID KEY NAME RECORDS COMMENTS
PAY 001 EMPNO 200
PMF 001 EMPNO 200
002 STZIP 200
PNC 016 PNDAT 5
PNM 015 PN 3
POH 011 POLI 5
012 VENDR 5
013 POHTV 5
014 LATE 2
REPORT AREA=IXX,TYPE=A Report

Reporting – IXX
00000001
000000 C3C161C4 C1E3C1C3 D6D461C4 C261C9E7 E7F0F0F0 F0F14040 40404040 40404040 *CA/DATACOM/DB/IXX00001 *
000020 00-SAME-
000040 00000000 A00E0C01 10000001 00000000 00000000 00000000 00000000 00000000 *...............................................*
000060 00000000 00000084 0000000F 00000000 00000000 00000000 00000000 00000000 *.......d......................................*
000080 00000000 00000000 00000000 00000000 00000000 00000000 C4C2F1F1 C3E7E740 *...............................DB11CXX *
00000002
000000 FF010000 00000000 00000000 0F6F0000 000D002C 003E004D 005C000D 00000000 *.............?.........(.*..................*
000020 00000000 00000000 00000000 00060000 00030001 F0F0F1F5 02000000 00040002 *....................0015...................*
000040 00000005 00020101 00000006 0B000200 00000700 0C010100 0000080D 00020000 *...............................................*
000060 0009000E 01010000 000A0F01 01000000 0B100002 0000000C 038F0002 0000000D *...............................................*
REPORT AREA=IXX,KEYID=nnn,TYPE=D and E Report

Reporting – IXX
INDEX POPULATION REPORT - BY TABLE
TOTAL UNIQUE
TABLE KEY ID KEY NAME RECORDS RECORDS DATE/TIME
PAY 001 EMPNO 200 10/07/2014,14.40.28
200
PMF 001 EMPNO 200 10/07/2014,14.40.29
200
002 STZIP 200 10/07/2014,14.40.29
6
8
REPORT AREA=IXX,TYPE=G Report

Reporting – LXX
LOG FILE (LXX) OUTPUT
LOG FILE OPEN - YES
LOG FILE SPILLING - NO
LOG FILE SPILL PENDING - NO
MASTER LIST RCV OPTION - NEVER
LOG FILE HIGHEST TRANSACTION SEQUENCE NUMBER - 00001BE3
CYCLE START DATE - /00/0000
CYCLE START TIME - .00.00
REPORT AREA=LXX Report

Reporting – LXX
FIRST BLOCK USED THIS CYCLE - 00021A00
CURRENT LOG BLOCK - 00007B01
PHYSICAL BLOCKS USED THIS CYCLE - 184
RESTART FORWARD SCAN BLOCK - 00007B00
LOG PENDING PARAMETER - 100
LOG FILE BLOCK SIZE - 27,998
PHYSICAL BLOCK SIZE - 27,998
PHYSICAL BLOCKS PER LOGICAL BLOCK - 1
LOG VARIABLE - NO
REPORT AREA=LXX Report continued

Reporting – RXX
AREA=RXX,LOGPRINT=SUMMARY/DETAIL/DETAILX
AREA=RXX,TSNPRINT=SUMMARY/DETAIL/DETAILX
Filter keywords:
BLOCK= DBID=nnnn JOBNAME=
OPTION2= RANGEDT= RANGETSN=
RECORDS= RUNUNIT= STARTAFT=
TABLE= TSNPRINT= URINUM=
REPORT AREA=RXX Report

Reporting – RXX
REQUEST SUMMARY REPORT
COMMAND TABLE DBID AREA OCCURRENCES PERCENT
CLOSE 44 0.0
LOGDW 21 0.0
MOVERO EVT 161 EVT 7,030 32.1
ADDIT C01 781 A01 175 0.3
DELET C01 781 A01 72 0.1
UPDAT C01 781 A01 100 0.2
ADDIT C02 781 A01 8,625 16.8
DELET C02 781 A01 5,351 10.4
MOVERU C02 781 A01 3 0.0
UPDAT C02 781 A01 27 0.0
REPORT AREA=RXX,LOGPRINT=SUMMARY

Reporting – RXX continued
LOGPRINT DETAIL REPORT
CMD TBL DBID URI BLOCK L# TSN JOB NAME R-UNIT MP USER ID AREA MONITOR INFO INPUT RECORD FPR LXX
DATE TIME CLOCK SEC.USER MOVE TO LRID PREV LRSN LBSN TASK STATUS RECL DATA
DELET C02 781 000050ED 0000280C 00 00001BD3 DBAJDEL 31,365 CATBPPR A01 1
09/24/2012 08.59.08 CA38271D7674D525 JOHAL01 00000000 00000201 0002575A 00000923 00000258 1 B 0138 6C7C
DELET C02 781 000050EE 0000280C 00 00001BD3 DBAJDEL 31,365 CATBPPR A01 2
09/24/2012 08.59.08 CA38271D7677B925 JOHAL01 00000000 00000202 00000201 00000924 00000258 1 B 0138 6C7C
DELET C02 781 000050EF 0000280C 00 00001BD3 DBAJDEL 31,365 CATBPPR A01 3
09/24/2012 08.59.08 CA38271D76799025 JOHAL01 00000000 00000203 00000202 00000925 00000258 1 B 0138 6C7C
REPORT AREA=RXX,LOGPRINT=DETAIL

Reporting – RXX continued
LOGPRINT DETAILX REPORT
CMD TBL DBID URI BLOCK L# TSN JOB NAME R-UNIT MP USER ID AREA MONITOR INFO INPUT RECORD FPR LXX
DATE TIME CLOCK SEC.USER MOVE TO LRID PREV LRSN LBSN TASK STATUS RECL DATA
DELET C02 781 000050ED 0000280C 00 00001BD3 DBAJDEL 31,365 CATBPPR A01 1
09/24/2012 08.59.08 CA38271D7674D525 JOHAL01 00000000 00000201 0002575A 00000923 00000258 1 B 016C7C
492000 00000138 CA38271D 7674D525 00000000 000000C4 00010001 010C0002 57000000 *.........N........D............*
492020 02570000 00000000 05700000 02011800 00000924 12085908 00050E65 00000000 *...............................*
492040 C4C5D3C5 E3C3F0F2 C1F0F100 00000054 030D0066 000050ED 00000000 00000000 *DELETC02A01....................*
492060 00D1D6C8 C1D3F0F1 4003C3C1 E3C2D7D7 D9400000 00000000 00000000 00000000 *.JOHAL01 .CATBPPR .............*
492080 00000000 C4C2C1D1 C4C5D340 0002575A 40404000 00000000 0000D3D6 C3C1D340 *....DBAJDEL ...! ......LOCAL *
4920A0 40400400 20730000 00001BD3 00001BD3 00000923 00023D00 0000280C 00000257 * .........L...L...............*
4920C0 00000258 00000000 00000000 00000000 00600066 00001BD2 000050ED C3F0F240 *................-.....K....C02 *
REPORT AREA=RXX,LOGPRINT=DETAIL

Reporting – PXX
– Strongly recommend MUF startup option SYSOUT
– If SYSOUT used, only data in PXX is MUF EOJ report
– If MUF startup option PXXSTAT EOJPRT used, EOJ report is also written
to a SYSOUT data set
– PXX SUMMARY data also in DST tables while MUF up
– DBUTLTY AUTOINFO SYPRINT also contains this information
REPORT AREA=PXX
JOBSTAT=SUMMARY/DETAIL/DETAILX
SYSSTAT=SUMMARY/DETAIL/DETAILX
DUMPS=FULL/REQUEST/TRACE,RTNCODE=nnn

Reporting – Memory
MEMORY=MVS Report
OPERATING SYSTEM z/OS V1.13 PROCESSOR 2817 SYSTEM CA31
CA DATACOM/DB SUBSYSTEM IS PRESENT
COMMON MEMORY USAGE (NOT SVC OR MUF SPECIFIC)
ADDRESS SIZE TEXT
00C5CD64 36 SSCT 'DB ' AND SMALL ANCHOR
3A5FB000 384 DBNSDBNB LARGE ANCHOR
3A260000 2082 DBESPPR 12 CROSS MEMORY
00C39000 632 DBSSVPR 12 SUBSYSTEM
MUF NAME STATUS REL JOB NAME JOB ID CXX NAME SVC COMMON31 ENBL-MDHMS COMMENTS
AAACMU11 DISABLED UNKN. 231 0 COMMON24=192
BOL41MUF ENABLED 12 MSMMUF JOB36409 CAMSM 239 10176 1031104757 DS=00044MUF
BOL50MUF DISABLED 12 MSMMUF JOB47671 CAMSM 239 10176 DS=00028MUF
REPORT MEMORY=MVS/DS/CF

Reporting – Data Native Efficienty (DATANE)
DBID=nnnn,TABLE=ttt,RECORDS=nnnnn
Report Part 1:
Base: 161**************************************************************************** Directory: DB11CXX
TBL AREA KEY CMP USER COMPRESSION RECLN RECORDS BLKSIZE TRACKS TOT BLKS INUSE BLKS PART BLKS
EVT EVT EVTK N 513 103,528 7,476 2,500 17,500 12,515 5,706
SCAN MAX ROWS/BLOCK 14 #ROWS READ 98,593
REPORT TYPE=DATANE

Reporting – DATANE continued
Report Part 2:
*------- BLOCK -------* PBC 1429 MRB *-MAX ROW/BLK EFFICIENCY RATES WITH BUFFERS -*
GROUP ROWS BLOCKS MAX MIN AVG BLOCK EFF 2 4 8 12 16 20 24 28 32 48 64 96 128 256
READ W/DATA ROWS ROWS ROWS CHANGES % % % % % % % % % % % % % % %
1 20,000 4,288 14 1 5 13,365 11 13 14 15 16 17 19 21
2 20,000 4,216 14 1 5 16,714 9 17 18 19 20 21 22 23 24
3 20,000 4,110 14 1 5 14,265 10 17 18 19 20 21 22 23 24 25 26
4 20,000 2,783 14 1 7 7,217 20 33 34 36 37 38 39 42 44 45 46 47
5 20,000 2,578 14 1 8 6,067 24 37 38 41 42 43 46 48 49 51
6 3,528 411 14 1 9 789 32 54 57 60 61 62
____________________________________________________________________________________________
FULL TABLE
MRB 103,528 10,821 14 1 10 58,417 13 20 21 22 23 24 26 27 28 29 30
AMRB 103,528 10,821 14 1 10 58,417 19 30 31 33 34 35 38 39 41 42 44
REPORT TYPE=DATANE,DBID=nnnn,TABLE=ttt,RECORDS=nnnnn

Reporting – DATANE continued
Report Part 3:
*------- BLOCK -------* PBC 1429 MRB *-MAX ROW/BLK EFFICIENCY RATES WITH BUFFERS -*
GROUP ROWS BLOCKS MAX MIN AVG BLOCK EFF 2 4 8 12 16 20 24 28 32 48 64 96 128 256
READ W/DATA ROWS ROWS ROWS CHANGES % % % % % % % % % % % % % % %
1 20,000 1,429 14 8 14 1,429 100
2 20,000 1,430 14 2 14 1,429 100
3 20,000 1,429 14 10 14 1,428 100
4 20,000 1,430 14 4 14 1,429 100
5 20,000 1,429 14 10 14 1,428 100
6 3,528 253 14 2 14 252 100
____________________________________________________________________________________________
FULL TABLE
MRB 103,528 7,395 14 12 14 7,395 100
AMRB 103,528 7,395 14 12 14 7,395 100
REPORT TYPE=DATANE,DBID=nnnn,TABLE=ttt,RECORDS=nnnnn

Reporting – Dataset Identity
DATA SET IDENTITY INFORMATION DEVICE INIT DATE TIME CXX NAME
DIRECTORY CXX R12 LEVEL 01 DB 3390 20120921 103605 DB11CXX
000000 C3C160C4 C1E3C1C3 D6D461C4 C261C3E7 E7404040 40404040 40404040 40404040 *CA-DATACOM/DB/CXX *
000020 C4C2F1F1 C3E7E740 0005121C 110C0000 0002000F 00000000 00000000 0010C4C2 *DB11CXX ......................DB*
000040 0E0C1000 00000000 00000000 00000000 C4C2C1D1 C3E7E7D3 00000000 20120921 *................DBAJCXXL........*
000060 10360540 40404040 00000000 00000000 00000000 00000000 00000000 00000000 *... ........................*
000080 00000000 00000000 00000000 00000000 C4C2C1D1 F0F0F1D9 00000000 12103110 *................DBAJ001R........*
0000A0 41122040 40404040 00000000 00000000 0004B000 00027800 00000000 00000000 *... ........................*
0000C0 00000000 01000000 00000000 00000000 F8D48F77 EB5B1BD6 138F94A1 FC2F4143 *................8M...$.O..m.....*
0000E0 0AE10E9B F6CE4FD8 421B101C 00000000 00000000 00000000 00000000 00000000 *....6..Q........................*
000100 00-SAME-
000EE0 00000000 00000000 00000000 00000000 00000000 00000000 00000302 00017F02 *..............................".*
000F00 00027502 00027602 0001EB02 00027702 00000000 00000000 00000000 00000000 *................................*
000F20 00-SAME-
REPORT TYPE=U,DDNAME=indd

Recovery
§ SPILL
– MUF startup option LOGRCV NO only
– JCL must contain an RXX DD statement
§ SPILLOPT
– SPILL=MIN/MAX,HISTORY=NO/YES-FAIL/YES-RC0/YES-RC4
§ RXXFIX
– CYCLE=cccccccccc,DBID=nnnn,HISTORY=NO/YES-FAIL/YES-RC0/YES-RC4

Recovery
§ RECBASE
– DBID=nnnn,TABLE=ttt
§ RECJOB
– JOBNAME=job-name,NODE=n,ORIGRUNU=rununit,DATE=mmddyy,
STIME=hhmmss,ETIME=hhmmss
§ RECOVERY
– Forward or Backward
– One or more RECBASE and or RECJOB function must precede
RECOVERY function
Continued

Recovery
§ RECOVERY OPTION=FORWARD,
MISMATCH=FAIL/IGNORE,INDEX=YES/NO,NUMBER=0-9999,
UPDATE=YES/NO,MULTUSE=NO/YES,DBID=nnnn,AREA=aaa,
REPORT=ALL/ERRORS,RECID=NO/YES,FORCE=NO/YES,
RANGEDT=ccyymmddhhmmssccyymmddhhmmss
Continued

Recovery
§ RECOVERY OPTION=BACKWARD,
MISMATCH=FAIL/IGNORE,INDEX=YES/NO,NUMBER=0-9999,
SORT=nnnnnnn,OPTION1=NOF/’(I)’/’(U)’,SORTWK=0-99,
TASKID=nnnnn,REPORT=ALL/ERRORS,TERMID=tttt,UNIT=sysda,
TSN=nnnnnnn,FORCE=NO/YES,
RANGEDT=ccyymmddhhmmssccyymmddhhmmss
Continued

Accounting
§ ACCT OPTION=EDIT
– DATABASE=dd-entity-occ-name,DDOVER=version,STATUS=status
– TABLE=dd-entity-occ-name,DDOVER=version,STATUS=status
§ ACCT OPTION=CATALOG
– DATABASE=dd-entity-occ-name,DBID=4

Accounting
§ ACCT OPTION=OPEN
– TABLE=ALL/Ann
§ ACCT OPTION=CLOSE
– TABLE=ALL/Ann
§ ACCT OPTION=SPILL
– TABLE=ALL/Ann
Continued

Error Handling
§ SET OPTION1=
– ON-ERROR-CONTINUE
– ON-ERROR-STOP
– ON-ERROR-ABEND
– ON-ERROR-RCn
– ON-ERROR-REMOVE
– SNAPALL
– SNAPERR
§ May be entered in any order
§ Each subsequent SET supersedes/replaces previous

Resource Measurement and Monitoring
§ AUTOCOLLECT OPTION=SNAPSHOT
– MUFNAME=muf-name,DBID=1019/nnnn
§ AUTOCOLLECT OPTION=DELTACRE
– OPTION=DELTACRE,DBID=1020/nnnn
§ AUTOSTATUS MUFNAME=muf-name
– DBID=1018/nnnn,REPEATS=3/0-64800,OUTTAG=cccccccccccccccc,
SNAPEXCL=DURATION0/HEADER/NOTACTIVE/REPCONNECT/WARNMSG

Resource Measurement and Monitoring
§ AUTOINFO DDNAME=outdd,DELIMIT=;
– Creates both a SYSOUT report and a data set
– Contains MUF configuration information
– Contains MUF resource usage snapshot
– Run after MUF has been up for an extended period
– Helps CA Support understanding an environment’s configuration
and usage
Continued

Miscellaneous Functions
§ DBTEST
§ EDIT
§ SECURITY OPTION=RESET,USER=xxx

DBMSTLST
§ Assembled and linked during installation
§ Tailored as needed
§ Limited number of parameters

DBMSTLST Parameters
§ CXXNO
§ IXXNO
DXXNO
§ DATANO
§ DATALN
§ SMFRTY (z/OS)

Module Summary
§ Explain the purpose of DBUTLTY
§ Perform important DBUTLTY tasks
§ Generate DBUTILTY reports

Module 6: Routine Operations

Agenda
NAME THE MAJOR ROUTINE OPERATIONAL TASKS
IDENTIFY AREAS TO BACK UP
1
2

Routine Operations Considerations
§ Initiating the Multi-User Facility (MUF)
§ Displaying the MUF status
§ Stopping the MUF
§ Backups
§ Restores/Reorganizations

Initiating the Multi-User Facility
§ Job or Started Task
§ MUF Startup job typically has two steps
– DBMUFPR
– DBUTLTY REPORT AREA=PXX
§ DBUTLTY step not needed if MUF Startup Options SYSOUT
and PXXSTATS EOJPRT are present

Displaying MUF Status
§ MUF console commands
§ DBUTLTY COMM commands
§ Dynamic System Tables
§ CA SYSVIEW Performance Management (z/OS)

MUF Console Commands
§ Issue z/OS ‘/f’ (MODIFY) command
§ STATUS
– Displays status of MUF, task threads, active jobs
DB01311I - STATUS
DB01327I - MULTI-USER AVAILABLE, TASKS - ATTACHED----12, AVAILABLE----24
11/01/12 11:31:02
DB01328I - TIME I/O JOBNAME R-UNIT TASK CMD-DBID-TBL SEQ STATUS
ID TSN
DB01330I - DDDQC12 59680 1 NOT ACTIVE 12
§ STATS all/dbid/dbid-dbid
– Writes MUF in-memory database statistics to the CXX

MUF Console Commands
§ REQABORT
– Cancels a specific MUF request by request number
§ TSN_ABORT
– Cancels a specific MUF request by transaction sequence number
§ TASK_ABORT
– Cancels a specific MUF request by task number
§ Other commands available
Continued

DBUTLTY COMM Commands
§ Same functionality as console commands
§ Execute in batch as part of DBUTLTY
§ Output goes to SYSPRINT
§ COMM OPTION=CONSOLE,OPTION2=‘console command’

Dynamic System Tables
§ Tables exist as virtual SQL views
§ Table information extracted from CA Datacom/DB memory
§ Tables only accessible via SQL SELECTs or CA SYSVIEW
Performance Management display panels
§ Full MUF, CXX, PXX, LXX, SQL status information available
§ Some are updateable
§ Beginning in Version 14.0, SQL Web Connect facility available
for non-SQL licensed sites

CA SYSVIEW Performance Management (z/OS)
§ Provides an integrated interface for monitoring MUF
§ Commands can be issued from online or batch (TSO)
§ Retrieves information from CA Datacom/DB Dynamic System
Tables
§ Uses standard API for compatibility with future releases of CA
Datacom

Stopping the Multi-User Facility
Issue a z/OS “/f“ (MODIFY)
EOJ - Request Multi-User normal EOJ
– Waits for existing tasks to complete
– No new tasks can start
EOJOFF – Reverses EOJ request
Same functions in batch DBUTLTY

Backups
§ CXX
§ DD/DDD
§ LXX/FXX
§ VLS files
§ Index areas
§ Data areas

Backups
CXX
– Backup nightly
– Critical data set
– Use DBUTLTY or DASD utility
DD/DDD
– Backup in conjunction with CXX
LXX/FXX
– Spill to RXX using DBUTLTY
– Can be backed up using DASD utility, but synchronization issues could
be difficult so not recommended

Backups
§ VLS files
– Datadictionary
§ DDMAP, DDOL2
– IPC
§ ADRPNL, ADRLIB, ADROUT
– Ideal
§ IDLSRC, IDLOBJ, IDLPNL, IDDAT, IDDVW
§ With IDEAL backup VLS, DD, DDD together
§ Critical for online processing
Continued

Backups
§ IXX areas
– One (or optionally more) per database ID
– No DBUTLTY backup function
– Can use DASD utility to back up
– DBUTLTY RETIX recreates IXX from DATA area by table or base
– DBUTLTY LOAD always rebuilds IXX
Continued

Backups
§ Data areas
– Backup as needed using DBUTLTY or DASD utility
– DBUTLTY BACKUP
§ PHYSICAL creates image copy
– Primary type of backup used in recovering data areas
§ NATIVE primary type of backup used for reorganization
§ Use REORG for large data areas
– DBUTLTY EXTRACT produces "flat" file of all data records
– DASD utility can be used, special considerations - can’t restore to
devices of different track sizes
Continued

Restores/Reorganizations
§ CXX
§ DD/DDD
§ LXX/FXX
§ VLS files
§ Index areas
§ Data areas

Restores/Reorganizations
§ CXX
– Restore only if needed
– DBUTLTY can restore either entire CXX or a selected database
– DASD utility restores entire data set
– Synchronization with DD and DDD required
§ DD/DDD
– Restore in conjunction with CXX
§ LXX/FXX
– No DBUTLTY function, only restored by DASD utility
– Not usually done (possibly used for disaster recovery)
Continued

Module Summary
§ Name the major routine operational tasks
§ Identify areas to back up

Module 7: Logging and Recovery

Agenda
EXPLAIN LOGGING
EXPLAIN PIPELINING
DESCRIBE FORWARD AND BACKWARD RECOVERY
HOW TO ACTIVATE LOGGING, RECOVERY AND PIPELINING
1
2
3
4

Logging and Recovery Facilities
§ Logging
§ Transaction backout
§ Pipeline
§ Spilling the Log (LXX)
§ Forced checkpoint
§ Forced SPILL
§ Restart
§ Recovery

Logging
§ Logs both online and batch transactions
§ Optional by table
§ Users may also log their own records
§ User checkpointing

Implementing Logging Facility
§ Logging during installation
– Small Log Area (LXX)
– No recovery capability
§ Production system requirements
– Log Area of sufficient size
– Recovery capability

Implementing Logging Facility
§ Implementation steps
– Allocate and initialize LXX
§ Log block size 16K or greater
§ Minimum of 103 logical blocks
§ Variable logging strongly recommended and requires 32,760 block size
– Allocate and initialize FXX
§ Must be same block size as LXX
§ Allocation dependent on tasks
– Review related Multi-User startup options (discussed later in detail)
Continued

Log Record
§ Control information
§ Pre-update record images
§ Transaction image

Requests That Generate Log Blocks
§ ADDIT
§ UPDAT
§ DELET
§ LOGIT and LOGDW
§ DEQUE – internal command issued by CA Datacom CICS
Services at the end of a task, performs same function as
COMIT
Continued

Log-Related Startup Options
§ LOGPEND
§ LOGOPTION
§ LOGPOOL
§ LOGRCV
§ LOGSPILL

Implementing Transaction Backout
§ Define logging attributes for desired tables
§ Code TXNUNDO in programs’ User Requirements Table
§ Ensure Log Area size is adequate

Transaction Backout Processing
§ Invoked by any one of the following:
– CA Datacom/DB after a program abend
§ When TXNUNDO is coded in the URT
– Application program issuing a ROLBK command
– Restarting MUF after a system abend when transaction backout tasks
were active at the time of the abend

Impact on Exclusive Control
§ Without Transaction Backout
– Read with update intent
– Obtain primary exclusive control
– Update completes
– Primary exclusive control is dropped

Impact on Secondary Exclusive Control
§ With Transaction Backout
– Secondary exclusive control is dropped when:
§ Task completes
§ Or, COMIT is issued by program

Logging and Pipeline
§ System Level – LOGPEND startup option
– maximum number of blocks with pipeline pending transactions
LOGPEND 2000
§ Task Level – URT WRITE= parameter
§ NO - Deferred write - Pipeline active
§ YES - Immediate write - Pipeline Inactive
§ Task Level NO overrides Table Level Y
§ Task Level YES does not override Table Level N
§ Table Level – PIPELINE-OPTION=Y/N
– Datadictionary table entity occurrence attribute

Conditions Causing Writes
§ Data and Index Area writes occur when:
– Buffer containing pipelined records required for reuse
– User Requirements Table closes upon a job completion
– Log block containing record of update transaction has exceeded
LOGPEND= value
– Index Area block splits because of maintenance
– Spill of associated log records occurs
– DBUTLTY LOCK/UNLOCK COMBINATION
– DBUTLTY ACCESS status change

Conditions Causing Writes
§ Log Area writes occur when:
– Associated Index or data area block is written
– Log block in memory becomes full
– DEQUE, ROLBK, COMIT (if requested), or forced checkpoint occurs
Continued

Spilling (or Archiving) the Log
§ LXX blocks are copied to the RXX data set(s)
§ Only committed updates are spilled
§ Only contiguous spillable blocks are spilled
§ When the LXX is full, forced checkpoint or forced
spill may occur

Active Spilling
§ MUF automatically spills
§ LOGRCV=YES
§ Requires dedicated tape device
§ Not allowed if MUFPLEX startup option present

Active Spilling
Continued

Inactive Spilling
§ Spill occurs in a separate region
§ MUF startup option LOGRCV=NO
§ DBUTLTY function SPILL
§ DBUTLTY function SPILLOPT SPILL=(MIN or MAX)

Active Spilling
Continued

Never Spill
§ Nothing is written to RXX
§ MUF startup option LOGRCV=NEVER
§ Good for test systems
§ Allows RESTART and transaction backout up to LXX capacity
§ Make sure LXX is large enough to handle the largest amount
of work between COMITs (or be prepared to restore)
§ Recovery is not possible

Never Spill
Continued

Log Spill Options
§ LOGSPILL 35,100,20,30,20
§ LOGSPILL(a) – begin console message percent
§ LOGSPILL(b) – early forced checkpoint percent
§ LOGSPILL(c) – begin SPILL percent (LOGRCV=YES)
§ LOGSPILL(d) – % of log full to move last request to FXX
§ LOGSPILL(e) – % of log full to move active requests to FXX

Logging Performance Considerations
§ LXX usually most accessed data set
§ Larger LXX block sizes will reduce I/O
§ Strongly recommend variable LXX
§ INIT AREA=LXX,BLKSIZE=32760,VARIABLE=YES
§ Entire database must be disabled for forward recovery
§ LOGPEND may impact RESTART runtime

RXX Messages
§ DB00308I LOG AREA IS 50% FULL,150 BLOCKS SPILLABLE
– Occurs in inactive logging only
– Can occur only once per spill
– Batch SPILL expected at this point
– Based upon LOGSPILL(a)

RXX Messages
§ DB00309I LOG AREA IS 50% FULL,JOB xxxxxxxx
PREVENTING SPILL
– Based upon LOGSPILL(a)
– Spill not currently possible
Continued

RXX Messages
§ DB00310I LOG SPILL 3-1,BLOCKS 2-96,TIMES 050103070000-
050103100811
– After each spill
– Information about what was spilled
Continued

RXX Messages
§ DB00311I LOG AREA IS 60% FULL,SPILLING BLOCK 50,OUT OF
200
– If no spill, message repeats every additional 5% full up to 90%
– If no spill, message repeats every additional 1% full after 90%
– ‘Out of’ value grows until spill started
– Block shows as 'none' until spill started
– ‘Block’ replaced by ‘Track’ if variable logging used
Continued

Forced Checkpoint
§ When LXX fills, MUF updates wait for a spill
§ Active logical units of work cannot be spilled
§ If a spill is executed, MUF will checkpoint all active LUWs that
are preventing a spill
§ Secondary exclusive control locks are released for
checkpointed records
§ FXX contains logging related information that has been forced
from the LXX

Forced Checkpoint
§ Setting MUF Startup parameter LOGSPLL(b) with a value less
than 100% could allow a forced spill before LXX is full
§ If transaction backout requested for a task:
– Undo all updates still on LXX
– Post message requesting BACKWARD recovery be executed for task
nnnnnn (RXXROLLBACK=YES)
– When recovery completes, record locks are released
Continued

Forced SPILL
§ MUF Startup parameter
– RXXROLLBACK=YES (default)
§ When LXX fills, MUF updates wait for spill
§ Active logical units of work cannot be spilled
§ If a SPILL is executed, MUF will spill all active LUWs without
doing a checkpoint
§ Secondary exclusive control locks remain

RESTART (at Startup)
§ Rolls forward incomplete requests
§ Back out incomplete logical units of work
§ Databases not involved in backout are immediately available
§ Resets LXX

RECOVERY Utility
§ Recovery from RXX only
§ Forward and backward recovery available
§ Restore of backup required for forward recovery
§ Multiple options to select extent of recovery
– RECBASE DBID=,TABLE=
– RECJOB JOBNAME=,DATE=,STIME=,ETIME=
– RECOVERY OPTION=(FORWARD/BACKWARD),RANGEDT=,FORCE=

Backups for Recovery
§ DBUTLTY backups, PHYSICAL with RECID=YES only
§ DASD tool backups are OK
– If backup done with database closed
§ Can restore index dataset also
§ or run DBUTLTY INIT and RETIX once all data restored
– If backup done with database active
§ Must do DBUTLTY INIT and RETIX after restore
§ Frequent backups minimize forward recovery time

Procedure for Forward Recovery
§ Close database to all processing
§ Spill LXX records to RXX
§ DASD tool restore of DBUTLTY LOAD most recent backups
prior to recovery point
§ Locate all applicable RXX files
§ Run recovery
§ Review output

Procedure for Backward Recovery
§ Recommended, but not required:
– Close database to all processing
– Backup existing database
§ Spill LXX records to RXX
§ Locate all applicable RXX files
§ Run backward recovery
§ Review output

INDEX=NO
§ LOAD and RECOVERY option
§ IXX is not updated during the LOAD or the RECOVERY
§ May improve RECOVERY time
§ Requires RETIX after RECOVERY

Module Summary
§ Explain Logging
§ Explain Pipelining
§ Describe Forward and Backward Recovery
§ How to activate Logging, Recovery and Pipelining

Module 8: Batch and Online Program
Access

Agenda
NAME AND EXPLAIN THE THREE BATCH PROGRAM ACCESS METHODS
DESCRIBE THE ROLE OF THE URT
CREATE A DYNAMIC BATCH URT
CREATE AN ONLINE URT
CREATE A STATIC BATCH URT
1
2
3
4
5

Batch Program Access
§ 3 Application Program Interfaces (APIs)
– Each API is suited to a range of applications
– Each API's functionality overlaps with the other APIs
– You can be successful with whichever one you use
– You may even choose to use all three

Which One Should I Use?
§ RAAT (Record At A Time)
– Commands based on retrieval/update of a specific row by a specific key
value
§ SAAT (Set At A Time)
– Commands based on retrieval/update of a specific set of rows within
one table where a specific key path can usually be found
§ SQL (Structured Query Language)
– Commands based on retrieval/update of sets of rows involving multiple
tables with complex selection criteria where specific key paths may not
be available

Navigational Program Access
§ Call Level Programming
§ RAAT
§ SAAT
§ URTs

Call Level Programming
§ RAAT
– CALL 'DBNTRY' USING user-info, request-area, work-area, element-list
§ SAAT
– CALL 'DBNTRY' USING user-info, request-area, work-area, element-list,
request-qualification-area
§ Return code fields
– Return-code
– Internal-return-code

Navigational Program Access: RAAT
§ Record-at-a-time access
§ ALL access by key
§ Requires use of a URT
§ Languages supported
– COBOL, Assembler, PL/I, C

Types of RAAT Requests
§ Index only
§ Record retrieval
§ Record retrieval for update
– Primary exclusive control
§ Update/Delete
– Secondary exclusive control

Types of RAAT Requests (contd.)
– LOCKG – locate index entry equal to or greater than key value
– REDKG – Read data row equal to or greater than key value
– RDUKG – Read and lock data row equal to or greater than key value
– REDNX – Read row with next equal or higher key value
– ADDIT – Add a row
– UPDAT – Update a row (must be locked using RDUxx command first)
– DELET – Delete a row (must be locked using RDUxx command first)
– COMIT – Commit/checkpoint all adds, updates or deletes to this point
– OPEN – Open a table for access
– CLOSE – Close a table (serves as a COMIT if maintenance performed)
– GSETL/GETIT – Batch sequential read ahead
RAAT Command Examples

Types of RAAT Requests
§ Read for update (RDUxx) commands
– Primary exclusive control per row read
§ Sequential/Physical "read ahead with update“ (GSETL/GETIT)
– Primary exclusive control per row returned
§ Insert, update and delete commands
– Secondary exclusive control until COMIT or CLOSE
Continued

Navigational Program Access: SAAT
– Set-at-a-time access
– Chooses key(s) to use
– May build a temporary index
– Access limited to one table (no joins)
– Processes sets of records for retrieval
– Record(s) can be updated/deleted
– Will issue RAAT commands for retrieval when possible
– Languages supported
– COBOL, Assembler, PL/I, C, invoked internally by CA Ideal and
CA Dataquery for CA Datacom
Compound Boolean Selection

Navigational Program Access: SAAT
§ SAAT comprised of 6 commands
§ Normal set commands
– SELFR (Select first record)
– SELNR (Select next record)
– SELPR (Release set)
§ Special commands
– SELCN (Continue set record selection)
– SELSM (Select same record)
– SELST (Stop set record selection)
Continued

Navigational Program Access: URTs
§ User Requirements Table (URT)
§ Required for all program access
– RAAT
– SAAT
– SQL
§ Default URT for SQL access

§ Specifies CA Datacom/DB resources for program execution
– Tables program may access
– Tables program may update
– Sequential processing buffers
– Transaction backout requirements
– Processing priority within MUF
Continued

§ STATIC URTs require all 4 macros in one assembly
– DBURINF (one instance)
– DBURSTR (one instance)
– DBURTBL (one per table)
– DBUREND (one instance)
Continued

§ DYNAMIC URTs require two separate assemblies
– MUF Interface component
§ DBURINF (one instance)
§ DBUREND (one instance)
– Database table component
§ DBURSTR (one instance)
§ DBURTBL (one per table)
§ DBUREND (one instance)
Continued

DBURINF Parameters
§ URTABLE=
– Determines type of URT
§ URTABLE=ASM (Static URT)
§ URTABLE=LOAD (Dynamic URT)
§ LOADNAM= Dynamic URT table component load module
name
§ LOADPRM= Dynamic URT table component EXEC parameter
value
§ OPEN= Database tables to be opened by USER or DB

DBURINF Parameters
§ MUFS=
– Yes/No to multiple MUFs
§ MUFSMSG=
– 1-999 issue DB00505I for every RC
– 0 no message
§ RRS=
– Yes/No invoke Resource Recovery Services
§ USRNTRY=
– User program entry point where URT returns control
Continued

DBURINF Parameters
§ BACKSPT=
– Support for CA Datacom/DB entry points used in prior releases
§ DBMODS=
– Rent/Norent
§ LE=
– Language environment
Continued

DBURSTR Parameters
§ AUTHID=
– For SQL programs, provides system default override
§ DB00101=
– Started message, yes or no
§ CBSIO=
– SELFR command I/O interrupt limit
§ TXUNDO=
– Maintenance transaction backout in effect for all tables, yes or no
§ CSECT=
– Allows linking of multiple URTs as single load module

DBURSTR Parameters
§ JOBSTAT=
– Multi-User to save job statistics, yes or no
§ OPTMIZE=
– Close job without writing PXX statistics, yes or no
§ MULTUSE=
– Multi-User mode (default) or Single User mode, yes or no
§ WRITE=
– Immediately write maintenance transactions to disk, yes or no
– YES disables the MUF pipeline feature
Continued

DBURSTR Parameters
§ PRTY=
– Priority level within Multi-User
§ NO522=
– Allow 522 timeouts, yes or no
§ SIDNAME=
– Used for multiple MUF access (Multi-MUF feature)
§ TIMEMIN=
– Exclusive control wait time in minutes
§ TIMESEC=
– Exclusive control wait time in seconds
Continued

DBURTBL Parameters
§ TBLNAM=
– 3-character Datacom table name or characters ‘BASE’
§ UPDATE=
– Maintenance allowed by application(s) using this URT, yes or no
§ SYNONYM=
– Same Datacom table name used in more than one databases, yes or no
§ TABLES=
– Number of tables to open when TABNAME=BASE (1-999)
§ DBID=
– Database ID where table resides

DBURTBL Parameters
§ DBIDMUF=
– DBID as known to MUF
§ DBIDUSER=
– DBID as known to application program
§ AUTODXC=
– Automatically drop exclusive control, yes or no
§ BYPOPEN=
– Bypassed open and close processing for table named in the TBLNAM=
parameter, yes or no
Continued

DBURTBL Parameters
§ GETBLK=
– Buffer size to be used for GETIT and GETPS commands
§ GBMAXR=
– Maximum number rows allowed in the blocked GETIT/GETPS buffer
§ SEQBUFS=
– # MUF data buffers to reserve for blocked GETIT/GETPS processing
§ ELMCHG=
– Allow request area element list value changes between GETIT cmds
§ READAHD=
– Index scanning or physical block scanning to be done, yes or no
Continued

DBURTBL Parameters
§ DBFLSUB=
– User Requirements Table associated with a program using DBFLSUB,
yes or no
§ AREANAM=
– 3-character Datacom area name to be loaded using the DBFLSUB
subroutine
Continued

DBUREND Parameters
§ DBSQL=
– Application associated with this URT using SQL, yes or no
§ USRINFO=
– Up to 16 bytes of user info (descriptive text only)
§ AMODE=
– ANY, 24, 31, or NONE
§ RMODE=
– ANY, 24, 31, or NONE

Static Batch URTs
§ All URT macros must be present in assembly
§ DBURINF
§ DBURSTR
§ DBUREND
§ Assembled URT component linked with user program

Static Batch Macro Coding

Dynamic Batch URTs
§ Requires two assemblies
– MUF interface component
§ DBURINF
§ DBUREND
– Database table component
§ DBURSTR
§ DBUREND
§ MUF interface component linked with user program
§ Database table component loaded at program run time

Dynamic Batch Macro Coding
URT TITLE ‘DBSURT--MULTI-USER/SINGLE DB’
Interface DBURINF X
Macro URTABLE=LOAD X
LE=YES, X
LOADPRM=DBURT, X
OPEN=DB, X
BACKSPT=NO, X
COBOL=YES
End DBUREND X
Macro USRINFO=CA-INS-URT
END
Interface DBURINF X
Macro URTABLE=LOAD X
LE=YES, X
LOADNAME=DBURT031, X
OPEN=DB, X
BACKSPT=NO, X
COBOL=YES
End DBUREND X
END

Dynamic Batch Macro Coding (contd)
Table DBURSTR X
Start ABEND=YES X
Macro MULTUSE=YES, X
PRTY=7, X
TXNUNDO=YES
Entry DBURTBL X
Macro READAHD=PHYSICAL, X
DBID=31, X
ELMCHG=NO, X
GETBLK=8192, X
SEQBUFS=24, X
TBLNAM=CAR, X
UPDATE=NO
Entry DBURTBL X
READAHD=INDEX, X
DBID=31, X
ELMCHG=NO, X
GETBLK=8192, X
SEQBUFS=24, X
TBLNAM=INS, X
UPDATE=YES
End DBUREND X
END

Online Program Access
§ Same RAAT/SAAT support as batch except:
– GSETL/GETIT and GSETP/GETPS not allowed
– Programs linked with DBCSRPR or DBCSVPR instead of a URT module
§ CA Datacom/CICS Services uses URT pool to access a MUF
– URT module names have same prefix with different numeric suffixes
– URTs searched in numeric suffix order
– URT opens done by CA Datacom/CICS Services
– URT opens can be automatically done at CICS startup time
– URT closes and opens can be done manually after CICS startup

Online Program Access
§ Same return codes as batch
§ Some additional return codes for CICS
Continued

Online Macro Coding
URT TITLE ‘DBURT031’
Table DBURSTR X
Start ABEND=YES X
Macro MULTUSE=YES, X
PRTY=7, X
TXNUNDO=YES
Entry DBURTBL X
Macro READAHD=PHYSICAL, X
DBID=31, X
ELMCHG=NO, X
GETBLK=8192, X
SEQBUFS=24, X
TBLNAM=CAR, X
UPDATE=NO
Entry DBURTBL X
READAHD=INDEX, X
DBID=31, X
ELMCHG=NO, X
GETBLK=8192, X
SEQBUFS=24, X
TBLNAM=INS, X
UPDATE=YES
End DBUREND X
Macro USRINFO=ONLINE-URT
END

Online SQL Access
§ Same command support as batch
§ Programs are linked with DBCSRPR or DBCSVPR
§ Uses a single URT (usually DBURT020)
§ Same SQL return codes as batch

Module Summary
§ Name and explain the three batch program access methods
§ Describe the role of the URT
§ Create both batch and online URTs

Module 9: Problem Determination

Agenda
LIST INFORMATION NECESSARY BEFORE CALLING CA SUPPORT
IDENTIFY PROBLEM SEVERITY
MONITOR YOUR ISSUE
1
2
3

Problem Determination
§ Prepare for CA Support call
§ Place support call
§ Work support call
§ Complete support call

Prepare for CA Support Call
§ Have manuals available
§ Know your product's:
– Release
– CA RS level most recently applied
– Additional PTFs that are applied
§ Know your operating environment
– Operating system release
– CICS release

§ Documentation
– SVC or S dump
– PXX Report or Masterlist Dump(s)
– Console Log
– MUF JES Log
– Error messages
– Memory DS (for dataspace)
– DBUTLTY AUTOINFO output
Continued

§ Problem history:
– How often does it occur?
– Can the problem be recreated?
– What has changed?
§ Software
§ Application
§ Data
§ Transaction volume
Continued

Place the Support Call
§ Have your site ID ready
§ Have all documentation ready
§ Use CA Support Online (CSO) at http://support.ca.com or call
CA Support at 800-225-5224
– Open case - retain number
– Describe problem and what documentation is available

Place the Support Call
§ Establish problem priority
– Priority 1 Production system down or major business impact
– Priority 2 Major component down
– Priority 3 Minor problem
– Priority 4 Information/question
Continued

Work the Support Call
§ CA Support will:
– Enter all information provided if called
– If opened online, must call to upgrade to severity 1 if needed
– Level 1 will scan existing solutions, problems and cases to try and
match your scenario
– Provide applicable solutions or will transfer issue to Level 2
§ Sustaining Engineering (Level 2) will:
– Review the available documentation
– Possibly request additional information
– Provide a resolution for the problem

Complete the Support Call
§ Update the contact or call customer technician
– Confirm the resolution to the problem
– Ask the technician to close the issue

Module Summary
§ List information necessary before calling CA Support
§ Identify problem severity
§ Monitor your issue

Module 10: CA Datacom CICS Services

Agenda
DESCRIBE THE PURPOSE OF CA DATACOM CICS SERVICES
RECOGNIZE PRODUCT COMPONENTS
RECOGNIZE ENVIRONMENTAL CONSIDERATIONS
1
2
3

CA Datacom CICS Services

Product Components

Transactions
§ DBOC, DBEC, DBUT, DBUG should be secured
§ DBOC supports master operators
§ DBRC is an internal transaction

Modules

Modules
§ DBEC/DBEX with SYSID
– Or CRTE each DBOC command
Continued

URT Pool

Environmental Considerations
§ Uses COMMAND level CICS calls
§ Supports CICS Releases:
– 3.2 and later for z/OS (DBC Version 15.0)

Module Summary
§ Describe the purpose of CA Datacom CICS Services
§ Recognize the product components
– Transactions
– Modules
– URTs
§ Recognize environmental considerations

Module 11: Monitoring Online URTs

Agenda
ISSUE URT LEVEL COMMANDS
ISSUE TABLE LEVEL COMMANDS
UPDATE TABLE LEVEL VALUES
UPDATE URT LEVEL VALUES
ISSUE MUF LEVEL COMMANDS
1
2
3
4
5

Display URTs and Tables

INQuiry Commands
§ DBIC INQ=????.???.????
– ? or ?? or ??? or ???? on 1st and 3rd parameters
– First series is URT number
– Second series is Table name
– Third series is Database ID
§ DBIC INQ=type,status,when
– Type STD,DYN or SQL
– Status OPENED, CLOSED, FAIL
– When AUTO, DEFER, PLT

INQuiry Commands
§ DBEC I, level(????),limiter,SYSID(aaaa)
– Level is URT or TBL
– ???? represents URT number
– Limiter is type, status, when, condition
§ Type DYN or SQL
§ Status CLOSE, CLOSING, OPEN, UNOPENED
§ When AUTO, DEFER, PLT
§ Condition NOPPT
– SYSID is CICS region
§ Default is local
§ ‘*’ means all CICS Services attached to MUF
Continued

URT Inquiry: Example 1

Display URT Parameters Using DBEC/DBEX
§ DBEX I,URT(001?)
CA-DATACOM CICS SERVICES APPLID = A06ICDQD
DBEC I,URT(01?)
A SYS URT TYP STATUS WHEN REL CBSIO PRTY UNDO MIN SEC CONDITIONS
*LOC 0010 STD OPEN AUTO 81 000000 07 YES 000 000 ACTIVE=000 RESRVD=000
*LOC 0011 NO PPT ENTRY FOR URT
*LOC 0014 STD OPEN PLT 81 000000 07 YES 000 000 ACTIVE=000 RESRVD=000
*LOC 0016 STD OPEN PLT 80 000000 07 YES 000 000 ACTIVE=000 RESRVD=000
*LOC 0018 NO LOAD MODULE
*LOC 0019 NO LOAD MODULE

§ DBEX I,URT(001?)
DBEC I,TBL(10)
SYS URT TYP STATUS TABLE DBID UPD BYP SYN AUT DBIDM SIDNAME MUF
*LOC 0010 STD UNOPENED ACT 00010 YES NO YES YES DBSIDPR 01
CUS 00010 YES NO YES YES
DTL 00010 YES NO YES YES
ORD 00010 YES NO YES YES
ITM 00010 YES NO YES YES
NUM 00010 YES NO YES YES
RCP 00010 YES NO YES YES
SAL 00010 YES NO YES YES
SHP 00010 YES NO YES YES

Unique Commands
§ Available in DBOC/DBIC
– DBIC INQ=????.PAY
– DBIC INQ=????.???.0001
– DBIC INQ=FAIL
– DBIC INQ=PTF
§ Available in DBEC/DBEX
– DBEX I,URT(????),CLOSING
– DBEX I,URT(????),UNOPENED
– DBEX I,URT(????),NOPPT

Display PTFs Using DBOC/DBIC
§ DBIC I,PTF

Controlling Access to URT Pool

Control Access to URTs
§ DBUTLTY ACCESS=NOMAINT
– URTs do not need to be closed
§ DBOC command=????
– Open, Close, Auto, Defer, Restart
§ DBEC I,URT(????),SYSID(aaaa)
– Use action codes, O, C, A, D, R, N
§ DBEC P,action,URT(????),SYSID(aaaa)
– Open, Close, Auto, Defer, Restart

Modify DBURSTR Parameters
– Close URT
– Modify parameter
§ CBSIO, PRTY, TIMEMIN/TIMESEC, TXNUNDO
– Open URT

Display, Update a URT Using DBEC

Modify Tables in URT
§ DBOC Disable/Enable=nnnn.tbl
– Close URT
– Issue DBOC DISABLE=nnnn.tbl
– Open URT
– Close URT, Select URT
– Modify parameter
§ Autodxc, Synonym, Update, Bypass
– Open URT

Replace URT
§ DBOC method
– DBOC CLOSE=nnnn
– DBOC DELETE=nnnn
– CEMT S PROG(DBURTnnnn) NEWCOPY
– DBOC OPEN=nnnn
§ DBEC method
– DBEC P,CLOSE,URT(nnnn),SYSID(aaaa)
– DBEC P,NEWCOPY,URT(nnnn),SYSID(aaaa)
– DBEC P,OPEN,URT(nnnn),SYSID(aaaa)
Code, Assemble and Link URT

Changing Prefix of URTs

DBOC Demonstration
§ Disable Table by Closing URT and then disabling table
– DBOC CLOSE=0001
– DBOC DISABLE=0001.PAYT,0001.PMF
§ Open the URT containing the disabled tables
– DBOC OPEN=0001
– URT is now available for use
– PAY and PMF tables cannot be accessed at this time, but any other
tables specified in this URT are available for use
Step 1

DBOC Demonstration
§ Different variations can be used with this command
– DBOC CLOSE=0001,0003
– DBOC CLOSE=?? (closes URTs 00-99)
– DBOC CLOSE=1? (closes URTs 10-19)
– DBOC CLOSE=???? (closes URTs 000-999)
§ Variations also valid for OPEN and RESTART commands
Step 1 Continued

DBOC Demonstration
§ Different variations can be used with ENABLE and DISABLE
commands
– DBOC DISABLE-?.AAA
§ Disables all tables named AAA in URTs 0-9
– DBOC DISABLE=1.A??
§ Disables all tables that begin with the letter “A” in URT 1
Step 1 Continued

DBOC Demonstration
§ Enable the tables closed in step 1
– DBOC CLOSE=0001
– DBOC ENABLE=0001.PAY,0001.PMF
– DBOC OPEN=0001
Step 2

Module Summary
§ Issue URT level commands
§ Issue Table level commands
§ Update URT level values
§ Update Table level values
§ Issue MUF level commands

Module 12: Wrap-Up

How Did We Do?
§ What topic was most useful to you?
§ Are there topics you wanted covered that were not?
§ How would you improve this course for future attendees?

@CAWORLD #CAWORLD © 2016 CA. All RIGHTS RESERVED.219 @CAWORLD #CAWORLD
Mainframe and Workload Automation
For more information on Mainframe and Workload Automation,
please visit: http://cainc.to/9GQ2JI

Must See Demos
Demo Name
Services Y
Theater # location
Demo Name
Solution Y
Theater # location
Demo Name
Product X
Theater # location
Demo Name
Product X
Theater # location

Recommended Sessions
SESSION # TITLE DATE/TIME
MFX92S Strategy and Vision for CA Datacom and CA Ideal 11/16/2016 at 12:45 pm
MFX93S What’s new in CA Datacom 11/16/2016 at 1:45 pm
MFX94S Reducing TCO with Datacom Compression (Presspack) 11/16/2016 at 3:00 pm
MFX95SA Modernizing the CA Datacom data – SQL Access Part I 11/16/2016 at 3:45 pm
MFX95SB Modernizing the CA Datacom data – SQL Access Part II 11/16/2016 at 4:30 pm
MFX96S CA Datacom/AD Installation/Upgrade and Maintenance 11/17/2016 at 12:45 pm
MFX97S
CA Datacom/AD Report Utilization, and
information gather for Support
11/17/2016 at 1:45 pm
MFX98S
Using Sysview to monitor and measure your CA Datacom
environment – AD and DB
11/17/2016 at 3:00 pm
MFX99S Birds of a Feather/Stump the Techie! 11/17/2016 at 3:45 pm

Must See Demos
Demo Name
Services Y
Theater # location
Demo Name
Solution Y
Theater # location
Demo Name
Product X
Theater # location
Demo Name
Product X
Theater # location

Questions?

Thank you.
Stay connected at communities.ca.com

© 2016 CA. All rights reserved. All trademarks referenced herein belong to their respective companies.
The content provided in this CA World 2016 presentation is intended for informational purposes only and does not form any type of
warranty. The information provided by a CA partner and/or CA customer has not been reviewed for accuracy by CA.
For Informational Purposes Only
Terms of this Presentation

Pre-Con Ed: Introduction to CA Datacom Key Concepts and Facilities Part II

More Related Content

What's hot (20)

Viewers also liked (19)

Similar to Pre-Con Ed: Introduction to CA Datacom Key Concepts and Facilities Part II (20)

More from CA Technologies (20)

Recently uploaded (20)

Pre-Con Ed: Introduction to CA Datacom Key Concepts and Facilities Part II