Rational Developer for System z
Enterprise PL/I for z/OS, Version 3.8, Programming Guide

Requesting a checkpoint record

Defining the checkpoint data set

Each time you want a checkpoint record to be written, you must invoke, from your PL/I program, the built-in subroutine PLICKPT.

Read syntax diagramSkip visual syntax diagram>>-CALL--PLICKPT------------------------------------------------>
 
>--+--------------------------------------------------------+--><
   '-(--ddname--+--------------------------------------+--)-'
                '-,--check-id--+---------------------+-'
                               '-,--org--+---------+-'
                                         '-,--code-'
 

The four arguments are all optional. If you do not use an argument, you need not specify it unless you specify another argument that follows it in the given order. In this case, you must specify the unused argument as a null string (''). The following paragraphs describe the arguments.

ddname
is a character string constant or variable specifying the name of the DD statement defining the data set that is to be used for checkpoint records. If you omit this argument, the system will use the default ddname SYSCHK.
check-id
is a character string constant or variable specifying the name that you want to assign to the checkpoint record so that you can identify it later. If you omit this argument, the system will supply a unique identification and print it at the operator’s console.
org
is a character string constant or variable with the attributes CHARACTER(2) whose value indicates, in operating system terms, the organization of the checkpoint data set. PS indicates sequential (that is, CONSECUTIVE) organization; PO represents partitioned organization. If you omit this argument, PS is assumed.
code
is a variable with the attributes FIXED BINARY (31), which can receive a return code from PLICKPT. The return code has the following values:
0
A checkpoint has been successfully taken.
4
A restart has been successfully made.
8
A checkpoint has not been taken. The PLICKPT statement should be checked.
12
A checkpoint has not been taken. Check for a missing DD statement, a hardware error, or insufficient space in the data set. A checkpoint will fail if taken while a DISPLAY statement with the REPLY option is still incomplete.
16
A checkpoint has been taken, but ENQ macro calls are outstanding and will not be restored on restart. This situation will not normally arise for a PL/I program.

Terms of use | Feedback

This information center is powered by Eclipse technology. (http://www.eclipse.org)