Using OPS/REXX › Use the Precompiled OPS/REXX Programs › The OPSEXEC and OPSCOMP Libraries › Allocate the OPSEXEC DDname

Allocate the OPSEXEC DDname

When you invoke an OPS/REXX program, OPS/REXX first searches the OPSEXEC ddname for a precompiled version of it.

For this reason, the same data set that you allocated to the OPSCOMP ddname typically should also be the first data set in your OPSEXEC ddname concatenation.

If you are an OPSVIEW user, second in your OPSEXEC ddname concatenation should be the SYS1.OPS.CCLXOPEX data set. The SYS1.OPS.CCLXOPEX data set stores all previously compiled REXX programs for the OPSVIEW feature, and should be allocated to the OPSEXEC ddname of all OPSVIEW users for improved performance. In case you have customized any of these programs for use at your site, placing this CA-distributed data set second ensures that OPS/REXX finds your versions first.

The SYS1.OPS.CCLXOPEX data set has a block size of 8192. For performance reasons, you may want to re-block the SYS1.OPS.CCLXOPEX data set (the larger the block size, the better the performance). To do so, use the JCL in the OPEXRBLK member of the OPS.CCLXCNTL library.

To allocate the OPSEXEC ddname, use either the JCL or the TSO ALLOC command shown in the following examples.

Note: In these examples, the SYS1.OPS.CCLXOPEX data set appears second in the concatenation:

• JCL

  //OPSEXEC DD DISP=SHR,DSN=user.compile.library
  //        DD DISP=SHR,DSN=SYS1.OPS.CCLXOPEX
  

• TSO

  ALLOC FILE (OPSEXEC)
    DATASET('user.compile.library' 'SYS1.OPS.CCLXOPEX') SHR
  

In the examples, user.compile.library is the name of the data set where you store your OPS/REXX programs. Different user.compile.library data sets can be in use at different times.