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

Allocate the OPSCOMP DDname

The OPSCOMP ddname contains the output of the compile process. When you compile an OPS/REXX program using either the OICOMP or OXCOMP command, CA OPS/MVS saves the compiled version of the program as a member in the data set you have allocated to the OPSCOMP ddname. Because the OPSCOMP ddname is an output data set, it must be a single data set rather than a concatenation. This rule conforms to standard z/OS restrictions on output data sets.

To allocate the OPSCOMP data set, use either the JCL or the TSO ALLOC command shown here:

• JCL

  //OPSCOMP DD DISP=SHR,DSN=user.compile.library
  

• TSO

  ALLOC FILE (OPSCOMP) DATASET('user.compile.library') SHR
  

In the previous examples, user.compile.library is the name of the data set that is to store the output of the compile process. Different user.compile.library data sets can be in use at different times.

Follow these guidelines when allocating OPSCOMP:

• For additional flexibility, do not allocate OPSCOMP permanently.
• Allocate OPSCOMP to an output partitioned data set with a minimum block size of 4096 (at least 8192 is recommended) and a logical record length of 4096. You may want to reblock the data set for efficiency; the larger the block size, the better the performance. The OPEXRBLK member of the OPS.CCLXCNTL library contains JCL to reblock this data set or any compiled library.
• Place the data set you allocate to the OPSCOMP DDNAME first in your OPSEXEC concatenation (as described below).