The CMS EXEC &STACK control statement allows you to enter commands or operands as in-stream data before coding the CPEREPXA EXEC. It is another way to avoid having to recode parameters and control statements each time you run EREP.

Precede each operand by &STACK, one to each input record. CPEREPXA reads the operands in the order in which you have stacked them.

To invoke CPEREPXA from an EXEC using only EREP’s default values, code only a null &STACK statement in the EXEC.

&TRACE ERR
FILEDEF EREPPT PRINTER (NOCHANGE BLOCK 133 PERM
FILEDEF TOURIST TERMINAL (NOCHANGE BLOCK 133
FILEDEF DIRECTWK DISK EREP CMSUT1 &DISK?
FILEDEF ACCIN DISK HIST RECORDS A (RECFM VB
&STACK HIST
&STACK ACC=N
&STACK TABSIZE=500K
&STACK SYSEXN
&STACK ENDPARM
&STACK SHARE=(020402.0736,220402.0736)
&STACK SHARE=(020402.0735,220402.0735)
&STACK LIMIT 33XX,ALL=15
&STACK LIMIT 3420,HR1600=025(1),HW1600=010(15)
&STACK LIMIT 3420,VR1600=025(1),VW1600=010(15)
&STACK DASDID CPU=020402,CH=07,SCU=14,STR=0238
&STACK
EXEC CPEREPXA
&EXIT

In this example, the EREP controls are in line, to be read by CPEREPXA in the order they are listed. Note the null &STACK statement following the DASDID statement. Without it, CPEREPXA prompts the terminal user for more EREP control statements.

The report output produced by this example is sent to the printer, but the TOURIST output appears on the terminal screen.

See the user’s guide for your version of CMS for information about coding and using EXECs.