Running Mainframe Utilities

The mainframe utilities consist of load modules and sample JCL. Some utilities also include REXX execs so that you can run the utilities interactively. The REXX execs, load modules, and sample JCL shipped with EngageOne™ Enrichment are in the following data sets:

  • hlq.STREAMW.EXEC
  • hlq.STREAMW.LOAD
  • hlq.STREAMW.JCL

where hlq is the high-level qualifier in which you installed EngageOne™ Enrichment.

Mainframe utilities run in either batch mode or interactive mode, depending upon the utility.

Running Utilities in Batch Mode

Batch mode indicates that the utility is run using JCL. Batch utilities are generally used as a step in your production JCL to prepare a print stream for EngageOne™ Enrichment processing. PDRCCA2M, PDRCCM2A, and PDRXCME are generally run in batch mode.

To run a utility in batch mode, customize the job card as well as the STEPLIB and data set names in the sample JCL shipped with the utility and submit it. Each sample JCL contains comments that describe what you need to customize.

Running Utilities in Interactive Mode

Interactive mode indicates that the utility is run from TSO. PDRCMETA, PDRLNADD, and PDRLNSUB are generally run in this mode. Interactive utilities are usually run ad hoc, during the analysis and setup of an EngageOne™ Enrichment project.

To run a utility interactively, change the loadmod variable in the REXX exec shipped with the utility so that it points to the data set in which EngageOne™ Enrichment is installed, and then run the exec. Each REXX exec contains comments that describe what you need to customize.

Note: The C run-time library must be in your TSO LOADLIB concatenation for you to run any C programs interactively. Consult your system administrator if you have any problems.

In order for TSO to locate the REXX utilities without your specifying the entire data set name, you must allocate the SYSEXEC DD to the data set. So, if your EngageOne™ Enrichment high-level qualifier (HLQ) is hlq, the REXX exec data set would be hlq.STREAMW.EXEC. For example, you can invoke the PDRCMETA exec with the fully qualified name:

hlq.STREAMW.EXEC(PDRCMETA) metacodefile

or you can allocate hlq.STREAMW.EXEC as SYSEXEC and then invoke PDRCMETA directly, as follows: 

ALLOC FI(SYSEXEC) DA('hlq.STREAMW.EXEC') SHR
PDRCMETA metacodefile

In this case, you would not have to reallocate the file for future references during the current TSO/ISPF session. For example: 

PDRCMETA metacodefile2
Note: If you use these utilities often, you may want to put the SYSEXEC allocation into your TSO log-on CLIST. Ask your system administrator if you do not know how to do this yourself.