PLT programs for the second quiesce stage

Programs that are to execute during the second quiesce stage of CICS® shutdown are specified in the second half of the PLT (after the DFHDELIM statement).

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(ANY)  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. Alternatively, for Language Environment® conforming programs, use the CICSVAR runtime option to set the appropriate CONCURRENCY and API values. See Defining runtime options for Language Environment.

During the second quiesce stage, no new tasks can start, and no terminals are available. Because of this, second phase PLT programs must not cause other tasks to be started, and they cannot communicate with terminals. Further, second phase PLT programs must not cause any resource security checking or DB2® calls to be performed. A PLT program cannot be a Java program that runs in a JVM server.

If a transaction abend occurs while the PLTSD program is running, CICS remains in a permanent wait state. To avoid this happening, ensure that your PLTSD program handles all abend conditions.

The second quiesce stage is complete when all of the second phase PLT programs have been executed.

You cannot use Debug Tool to debug a PLT program during the second queisce stage.