Entries are specified in the PLT as follows:

>>-DFHPLT--TYPE=ENTRY--,PROGRAM=(program-+--------------+-)----><
'-,program,...-'
- TYPE=ENTRY
- Indicates that one or more program names are to be listed in this table.
Note: As shown below, a TYPE=ENTRY macro is also needed to specify the PROGRAM=DFHDELIM
entry.
- PROGRAM=program
- Code
this with a program name of up to eight characters. Each program must either
have a definition in the CSD file or must be capable of being autoinstalled
(that is, the appropriate system initialization parameters must be specified
for program autoinstall). Undefined programs before the DFHDELIM statement
are system autoinstalled.
For PLTPI and PLTSD lists, only initial programs
should be named: other programs that are linked to by initial programs should
not be listed (but must be defined or be capable of being autoinstalled).
For programming information about restrictions on using PLT programs during
initialization, see the CICS® Customization
Guide.

>>-DFHPLT--TYPE=ENTRY--,PROGRAM=DFHDELIM-----------------------><
- PROGRAM=DFHDELIM
- Code this to delimit the programs to run in the first or second passes
of PLTPI or PLTSD. The DFHDELIM entry is not a program—it serves as a delimiter
only.
Note that:
- Programs listed before the PROGRAM=DFHDELIM entry in a PLTPI are
executed during the second stage of initialization. These are to enable
user exit programs needed during recovery. Define the user exit programs in
the CSD file, otherwise CICS may not be able to access them after CICS initialization
is complete, for example in EXEC CICS DISABLE commands. However, note that
the properties defined by RDO have no effect during the second stage of initialization.
- Programs listed after the PROGRAM=DFHDELIM entry in a PLTPI are executed
during the third stage of initialization. If these programs are used to enable
user exits, the user exit programs must also be defined in the CSD file or
must be capable of being autoinstalled.
- Programs listed before the PROGRAM=DFHDELIM entry in a PLTSD are executed
during the first quiesce stage of shutdown.
- Programs listed after the PROGRAM=DFHDELIM entry in a PLTSD are executed
during the second quiesce stage of shutdown.
Second stage initialization and second stage quiesce PLT programs do not
require program resource definitions. If they are not defined, they are system
autoinstalled (irrespective of the program autoinstall system initialization
parameters). This means that the autoinstall exit is not called to allow the
definition to be modified. The programs are defined with the following attributes:
LANGUAGE(ASSEMBLER) STATUS(ENABLED) CEDF(NO)
DATALOCATION(BELOW) EXECKEY(CICS)
EXECUTIONSET(FULLAPI)

As a result, system autoinstalled
programs have a default CONCURRENCY setting of QUASIRENT, and a default API
setting of CICSAPI.
- For those threadsafe PLT programs that
- are defined with the OPENAPI value for the API attribute, or
- are C or C++ programs compiled with the XPLINK compiler option
provide an appropriate resource definition, or alternatively, for Language
Environment conforming programs, use the CICSVAR runtime option to set the
appropriate CONCURRENCY and API values. See the CICS Application
Programming Guide.

Third stage initialization and first stage quiesce PLT programs can be
defined using program autoinstall, depending upon the program autoinstall
system initialization parameters. See Autoinstalling programs, map sets, and partition sets
for further information. If program autoinstall is not used, these programs
must have program resource definitions in the CSD file.