Description

1.2.5.2.2 Description

CHKP (Symbolic) can be used for recovery purposes. It commits all changes made by the program and, if your application program abends, establishes the point at which the program can be restarted. In addition, the symbolic CHKP call can:

Work with the extended restart (XRST) call to restart your program if your program ends.
Enables you to save as many as seven data areas in your program, which are restored when your program is restarted.

In Tuxedo ART for IMS, the simulated CHKP (Symbolic) is used to:

Commit the changes already made by using tpcommit(), which is the same as basic CHKP.
Retrieve the next message which is the same as basic CHKP.
Accept at most 7 data areas and save it with the check pint ID.
Record current retrieval position of all related GSAM DB.

Note:
If ART BMP server was restarted after user used symbolic CHKP to store data area, but before user uses XRST to restart program, the stored data area by symbolic CHKP will not be restored by XRST.
CHKP record will be saved in record log file named “programname.psbname.log”. An environment variable ART_IMSLOGDIR is used to specify the directory where the record log files are located. If environment variable ART_IMSLOGDIR is not set, its default value is $APPDIR/IMSLOGDIR.

For MP mode, if you want to share the record log file among machines, the ART_IMSLOGDIR should point to NFS directory which machines in the Tuxedo domain could access. The CHKP record is always appended to the record log file by Symbolic CHKP and the saved record will not be deleted at any time except the user empty the record log file manually. Duplicate CHKP records are be appended to the CHKP record file.

The status code of all related GSAM/DB PCB is blank after the CHKP (symbolic) call.

Parent topic: CHKP (Symbolic)