How to interpret the scenarios
The scenarios in this section show how to use each of the Fast Path Offline Suite primary commands.
Each scenario presents JCL and an associated control statement that combines a primary command with other elements of the Fast Path Offline Suite command language to achieve a defined set of desired results. Each line of the JCL and control statement begins with a two-digit line number. Immediately following the JCL and control statement, a table provides textual descriptions of each line in the scenario. The following example shows how each scenario is presented and described.
JCL and control statement
The following figure shows an example of JCL control statement.
02 //STEPLIB DD DISP=SHR,DSN=BMC.PFP.LOAD
03 // DD DISP=SHR,DSN=IMSVS.RESLIB
04 // DD DISP=SHR,DSN=IMSVS.DFSMDA
05 //IMSACB DD DISP=SHR,DSN=IMSVS.ACBLIB
06 //PFPSAMP1 DD DISP=SHR,DSN=BMCPFP.PFPSAMP.PFPSAMP1
07 //PFPSAMP2 DD DISP=SHR,DSN=BMCPFP.PFPSAMP.PFPSAMP2
08 //PFPSAMP3 DD DISP=SHR,DSN=BMCPFP.PFPSAMP.PFPSAMP3
09 //PFPSYSIN DD *
10 REORGANIZE DBD=dbdname,POINTER_VALIDATION=FULL
11 REPORT REPORT_HEADING='ANALYSIS DURING REORG'
12 IC DSNAME='PFP.ICOPY.&DBD.&AREA(+1)',
13 UNIT=TAPE,DISP=(NEW,CATLG)
/*
Descriptive text
The following table describes the JCL text.
Line no. | Comments |
|---|---|
01-04 | EXEC and STEPLIB statements for Fast Path/EP offline execution |
05 | The IMSACB DD statement is used for database processing. |
06-08 | Define area data sets. |
09 | DD statement for Fast Path/EP control cards. |
10 | All areas of the DBD are reorganized (IAREA=ALL is default). Full (cross-reference) pointer validation is performed on all areas. |
11 | A report of the analysis is created with the specified heading. |
12-13 | An image copy is taken with a user-specified data set name. Standard storage and disposition parameters for image copy are specified. |
Sample library JCL
The Fast Path/EP sample library contains sample JCL for each scenario that is presented in this appendix.
Member $$PFPIDX contains a reference list of the scenario members.
Segment hierarchy for sample DEDB
The scenarios in this appendix are based on processes that are performed on the PFPSAMP sample DEDB, which contains three areas.
The following figure shows a hierarchy diagram of the segments that are defined in the DBD for each area in the PFPSAMP database.
DBD for sample DEDB
The following figure provides the DBD that defines the PFPSAMP sample DEDB.
AREA DD1=PFPSAMP1,DEVICE=3380,SIZE=(4096), X
ROOT=(300,100),UOW=(30,5)
AREA DD1=PFPSAMP2,DEVICE=3380,SIZE=(4096), X
ROOT=(300,100),UOW=(30,5)
AREA DD1=PFPSAMP3,DEVICE=3380,SIZE=(4096), X
ROOT=(300,100),UOW=(30,5)
SEGM NAME=SEGA,BYTES=(485,18), X
PARENT=0,COMPRTN=(DPIFPRTN,DATA,INIT)
FIELD NAME=(SEGAKEY,SEQ,U),BYTES=13,START=3,TYPE=C
FIELD NAME=FLD01,BYTES=9,START=7,TYPE=C
FIELD NAME=FLD02,BYTES=12,START=41,TYPE=C
SEGM NAME=SDEP,BYTES=(400,25), X
COMPRTN=(DPIFPRTN,DATA,INIT), X
PARENT=SEGA,TYPE=SEQ
SEGM NAME=SEGB,BYTES=(60,13), X
COMPRTN=(DPIFPRTN,DATA,INIT), X
PARENT=SEGA,TYPE=DIR
FIELD NAME=(SEGBKEY,SEQ,U),BYTES=8,START=3,TYPE=C
FIELD NAME=FLD05,BYTES=4,START=11,TYPE=C
SEGM NAME=SEGC,BYTES=(50,13), X
PARENT=SEGB,TYPE=DIR
FIELD NAME=(SEGCKEY,SEQ,U),BYTES=8,START=3,TYPE=C
SEGM NAME=SEGD,BYTES=(55,13), X
COMPRTN=(DPIFPRTN,DATA,INIT), X
PARENT=SEGB,TYPE=DIR
FIELD NAME=(SEGDKEY,SEQ,U),BYTES=8,START=3,TYPE=C
SEGM NAME=SEGE,BYTES=(150,13), X
COMPRTN=(DPIFPRTN,DATA,INIT), X
PARENT=SEGA,TYPE=DIR
FIELD NAME=(SEGEKEY,SEQ,U),BYTES=8,START=3,TYPE=C
SEGM NAME=SEGF,BYTES=(90,14), X
COMPRTN=(DPIFPRTN,DATA,INIT), X
PARENT=SEGE,TYPE=DIR
FIELD NAME=(SEGFKEY,SEQ,U),BYTES=9,START=3,TYPE=C
SEGM NAME=SEGG,BYTES=(40,7), X
COMPRTN=(DPIFPRTN,DATA,INIT), X
PARENT=SEGA,TYPE=DIR
FIELD NAME=(SEGGKEY,SEQ,U),BYTES=2,START=3,TYPE=C
DBDGEN
FINISH
END
Related topic