Extracting repository data

DLIAXTRC is a utility that extracts data from the repositories and produces a file in the same format as the PDX Extract utility, DBUXRPT1.

Although the extract file is in the same format, the data content differs slightly because the EXTRACT keyword controls the extract file format. You may run the extract utility as often as you want. The data in the repositories is not affected by running an extract.

Member #MXAEXT in your sample library contains JCL to extract data from the repositories. The following figure shows required JCL.

//DLIAXTRC EXEC PGM=DLIAXTRC
//STEPLIB   DD  DISP=SHR,DSN=your.BMC.LOAD
//RECON1    DD  DISP=SHR,DSN=your.RECON1 
//CPCLOG    DDSYSOUT=* 
//PDXOUT    DDDISP=(,CATLG),DSN=DLIAXTRC.PDXOUT, 
//                DCB=(LRECL=320,BLKSIZE=nnnn,RECFM=VB), 
//                UNIT=SYSDA,SPACE=(CYL,(100,100)) 
//PLUSIN    DD  *

The following table lists DD statements that can be used to extract data.

Database extraction batch utility JCL statements

Statement

Description

STEPLIB

(optional) Specify the data set name of the BMC load library where DLIAXTRC resides.

CPCLOG

(optional) Specify where to store messages regarding the success or failure of the job.

RECON1

Specify the RECON1 data set that corresponds to the IMS environment from which you want to extract data.

PDXOUT

Specify the output extract data set. This is a VB data set with a logical record length up to 320. The block size may be any value greater than 324.

PLUSIN

Specify input control cards.

The following figure shows a sample control card.

Extracting repository data control card sample

PDXTRACT FUNC(function) +
         DBD(dbdname) +
         DBGROUP(dbgroup) +
         EXTRACT(PDXCOMP) + or
                (EXPANDED) +
         DATE(LAST) or
                (YYMMDD(from,to))

The following table lists keywords that are used to control extraction processing.

Database extraction batch utility keywords

Keyword

Description

PDXTRACT

Specify the command verb.

FUNC

Identify the type of data to extract. The following values are valid:

  • RELOAD

  • LOAD

  • UNLOAD

  • PTRCHK

  • SECINDEX

  • DBSCAN

  • SPACE

  • VOLUME

DBD

(optional) Specify the DBD from which to extract data. If this keyword is omitted, data is extracted for all DBDs.

DBGROUP

(optional) Specify the database group for which to extract data. If this keyword is omitted, data is extracted for all DBDs.

DATE

(optional) Specify the dates for which data is extracted. The following formats are valid:

  • LAST—extract data from the last occurrence of the data type that is requested

  • YYMMDD(from,to)—extract data within the date range that is specified

    The date is specified in Gregorian format. The to field is optional.

EXTRACT

(optional) Specify the file format of the extracted data file. The following values are valid:

  • PDXCOMP— produces an extract file in the same format as data from a PDX. HALDB and PDF data is not broken down at the partition level.

  • EXPANDED—produces HALDB and PDF data at a partition level, as well as other fields and records that are only available from the repositories. The resulting extract file has the partition name as part of the key of every record. All other fields are shifted 8 bytes to the right.

If this keyword is omitted, the extracted data file is in the PDXCOMP format.

The PDXOUT data set contains data that has been extracted from the repositories. There is no SYSOUT type of output.

If HALDB and PDF data is not extracted, the extract file is in the same format as an extract file from a PDX. Record layouts for this data are in sample library member DBUCOBEX or DBUSTATS. Data content during extraction from a repository is different, compared to extraction from a PDX.

The following table lists data content differences.

Extracting repository data differences

Record type

Difference

All types

Position 1

There are fewer record types in the repository. All types of load data are record type RS. All types of unload data are record type US. All types of pointer checker data are record type KS. All types of secondary index data are record type XB.

Position 3

The IMS ID is blank. The IMS ID is not stored in the repository.

13, 14, 16, 21, 25, 51

Not produced

The data in these records is not stored in the repository.

20

FSE fields starting in position 163 are blank. This data is not stored in the repository.

22

Fields SYNCHN12, SYNCHN13, SYNCHN14, and SYNCHN15 are blank.

30

FSE fields starting in position 125 are blank. This data is not stored in the repository.

41

Fields THLASTXT, THCISPLT, THCASPLT, THSPUSED, THUSEDXT, and KEYRANGE are blank.

42

Fields BLKSDATA and BLKSFSPC are blank.

43, 44

Record types 43 and 44 exist only for the latest record type 42.

55

Field NBREXCP is blank.

Note

If EXTRACT (EXPANDED) is used, all data is shifted to the right 8 bytes and the partition name is inserted in the key of each record immediately following the DBD name.

Was this page helpful? Yes No Submitting... Thank you

Comments