SMPCSI

To do this, you use JCL statements instead of dynamic allocation to define the CSI data sets containing the zones required for processing. For each CSI data set, you need to provide two DD statements:

• The first DD statement is used by SMP/E to enqueue on the data set (to protect it from simultaneous updates) and to trigger batch LSR. This DD statement uses the DDNAME parameter to point to the second DD statement.
• The second DD statement is used by batch LSR to open the CSI data set.

Both DD statements must specify the same DSN value. The following example shows how this can be done:

//SMPCSI    DD DSN=dataset1.CSI,DISP=SHR,
//          SUBSYS=(BLSR,'DDNAME=MYSMPCSI',
//          'HBUFND=value','HBUFNI=value')
//MYSMPCSI  DD  DSN=dataset1.CSI,DISP=SHR
//*
//tgtzone   DD  DSN=dataset2.CSI,DISP=SHR,
//          SUBSYS=(BLSR,'DDNAME=MYTGT1',
//          'HBUFND=value','HBUFNI=value')
//MYTGT1    DD  DSN=dataset2.CSI,DISP=SHR

In this example, note that:

• If the target zone and global zone exist in the same CSI, dataset1 and dataset2 refer to the same data set.
• HBUFND and HBUFNI are used instead of BUFND and BUFNI to indicate the use of hiperspace in expanded storage (if available).
• tgtzone is the name of the target zone specified on the SET BDY command to be processed.
• The DSN parameter must be specified on all DD statements to ensure internal enqueue protection.