Table pairs coding example

This coding example implements an installation security processor. It is made up of a JES2 initialization Exit 0 and a user extension module named HASPXJ00 which contains the installation security processor, the installation security subtask, and the installation PCE, DTE, trace, work selection, and $SCAN tables. The example includes sample mapping macros $SCYWORK, $SCDWORK, and $UCT, and the macro $USERCB which invokes the mapping macros.

Note: This code is provided as an example of installation extensions to JES2. The code is not Type 1 supported code of IBM®. It is not APARable.

The examples are inter-related to show how the tables can be used together. This is not required. That is, it is not necessary to code a PCE table (create your own processor) and code a DTE table (create your own subtask). In fact, it may make no sense for certain applications to design interrelated tables. This example was contrived to show what can be done, not necessarily what should be done.

There are six pieces required for the example used here.

HASPXJ00 - Installation extension code and tables that are required to create an installation security processor, security subtask, trace id, work selection criteria on the offload sysout transmitter work selection list, and an additional operand on the offload sysout transmitter.
$UCT - contains required fields for table generation
$SCDWORK - subtask DTE extension to hold fields specific to a security subtask
$SCYWORK - processor PCE extension to hold fields specific to a security processor
$USERCBS - control block that actually generates the above macros. This control block is known by $MODULE and is the way to get $MODULE to generate installation control blocks.
HASPXIT0 - Exit 0 module that contains EXIT0. This exit initializes the $MCT with the addresses of the installation tables located in HASPXJ00.