JCL requirements for the Database Selection facility


The JCL requirements are the same as those for any DL/I batch program.

In the Unload function, the DBSF does not use the IMS region controller services. Several additional DD statements are required to provide selection information and define the output data sets. the following figure shows sample JCL.

       //SELECT   EXEC PGM=DFSRRC00,PARM='DLI,ULPDBSEL,psbname'
//STEPLIB  DD DISP=SHR,DSN=bmc.xxx.load
//         DD DISP=SHR,DSN=IMSVS.RESLIB
//DFSRESLB DD DISP=SHR,DSN=IMSVS.RESLIB
//IMS      DD DISP=SHR,DSN=IMSVS.PSBLIB
//         DD DISP=SHR,DSN=IMSVS.DBDLIB
//RECON1   DD DISP=SHR,DSN=your.recon1       <===for HALDB only; required
//RECON2   DD DISP=SHR,DSN=your.recon2       <===for HALDB only; required
//RECON3   DD DISP=SHR,DSN=your.recon3       <===for HALDB only; required
//DI21PART DD DISP=SHR,DSN=DI21PART
//DBSPRINT DD SYSOUT=*
//BMCMSG   DD SYSOUT=*
//DFSURGU1 DD DISP=(,PASS),DSN=user.unload,UNIT=SYSDA,SPACE=(TRK,(2,1))
//PLUSIN DD *
   DBSELECT BEGIN(100) END(199) SKIPFREQ(5)

The PSB specified in the PARM parameter of the EXEC statement must contain a PCB for the database being read. It must be the first DB PCB in the PSB, unless you specify a PCB with the PCB or PCBNAME keyword of the DBSELECT command. The PCB must reference a physical DBD; no logical DBDs are allowed. If the PCB does not define all segments in the database record, the DBSF unloads only the segments defined in the PCB. PROCOPT is not used.

Specify the database selection criteria through commands in the PLUSIN control statement data set. The DBSF does not access the PDX.



 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*