A dynamic PCE table

Figure 1 illustrates an alternative method of defining the installation table in Figure 1 through use of a dynamic table.

Figure 1. Example of a Dynamic PCE Table

MYPCETAB $PCETAB TABLE=DYNAMIC
SCTYPCET $PCETAB NAME=SCTY,
               DESC='SECURITY'                                         X
               DCTTAB=*-*,                                             X
               MODULE=HASPXJ00,                                        X
               ENTRYPT=UCTMSCTY,                                       X
               CHAIN=UCTSYPCE,                                         X
               COUNTS=UCTSYNUM,                                        X
               MACRO=$SCYWORK,                                         X
               WORKLEN=SCYLEN,                                         X
               GEN=INIT,                                               X
               DISPTCH=WARM,                                           X
               PCEFLGS=0,                                              X
               FSS=NO,                                                 X
               PCEID=(0,UPCESCTY)
         $PCETAB TABLE=END

To create the installation PCE table illustrated in Figure 1 or Figure 1, you need to code the following operands on the $PCETAB macro:

Operand	Description
NAME=SCTY	The name of the PCE
DESC=SECURITY	The description of the processor. The word ‘PROCESSOR’ is appended to the end of the value specified on the DESC operand.
DCTTAB=-	An indicator that there was no DCT table and that the processor is not associated with a device
MODULE=HASPXJ00	The name of the module to contain the processor code
ENTRYPT=UCTMSCTY	The field to hold the entry point address. The $UCT field UCTMSCTY holds the address of the routine USCTPCE
CHAIN=UCTSYPCE	The name of the $UCT field to hold the pointer to the first security PCE
COUNTS=UCTSYNUM	Where the $PCEDYN service routine is to find out how many PCEs of this type it can create and to keep track of how many it has created.
MACRO=$SCYWORK	The PCE's own variable extension area The $SCYWORK macro maps this extension area.
WORKLEN=SCYLEN	The length of the variable extension area. SCYLEN is an equate in the $SCYWORK macro.
GEN=INIT	The indicator to generate the processor during initialization.
DISPTCH=WARM	The indicator that the processor should receive control after warm start processing. This assumes that the security processor is not be needed during warm start processing.
PCEFLGS=0	The indicator that the PCE has no special requirements. The PCEFLGS operand specifies the initial value the PCE PCEFLAGS field contains after it is created by $PCEDYN. If the initial state of the processor should be that it: Should be traced, specify PCETRACE. Should be marked as permanently exempt from non-dispatchability, specify PCEDSPXP. If the processor should never be marked non-dispatchable, then set this value. Should be marked as temporarily exempt from non-dispatchability, specify PCEDSPXT. This value would be specified if some processing must be completed by this processor that would fail if the processor was marked non-dispatchable. Cannot wait in the case of an I/O error, then specify PCENWIOP.
FSS=NO	The indicator that the processor should not run in FSS mode.
PCEID=(0,UPCESCTY)	The indicator that this is a processor that is not associated with a device. The identifier of the processor is 255. Installation-specified identifiers should start at 255 and decrease. JES2 processors start at 1 and increase. Code an equate in the $UCT named UPCESCTY and set it to 255. The PCEID operand specifies the type and identifier of the processor as follows: Processor Type Meaning 0 Non-device processor PCELCLID Local special PCE identifier PCERJEID Remote special PCE identifier PCENJEID Network special PCE id, indicates NJE or XFE JT/JR/ST/SR PCEINRID Initial special PCE identifier PCEPRSID Printer special PCE identifier PCEPUSID Punch special PCE identifier PCEXFRID XFR special PCE identifier