Purpose
Ends the current recovery unit and makes permanent any changes made to the database data during the current recovery unit.
Syntax
►►─── COMMIT ───┬────────┬───┬───────┬── . ───────────────────────────────────►◄ └─ TASK ─┘ └─ ALL ─┘
Parameters
COMMIT TASK writes a checkpoint to the CA IDMS/DB journal file and updates the subschema control block for all database, queue, and scratch records associated with run units that have been implicitly established for the issuing dialog. All record locks except those held on current records are released.
If TASK is not specified, only database records are the objects of the COMMIT command.
Releases all record locks, including those held on current records, and sets all currencies to null.
Note: The COMMIT command does not release long-term locks held on database records.
Usage
Definition
The COMMIT command is used to write a checkpoint to the CA IDMS/DB journal file and to release record locks held on database, queue, and scratch records. The checkpoints mark the beginning or end of specific database, queue, and scratch area activities within the issuing dialog. The release of record locks lessens the possibility of abnormal termination resulting from too many locks.
The CA ADS runtime system automatically writes a checkpoint to the CA IDMS/DB journal file at the beginning and end of a run unit. Additional checkpoints can be written to the journal file by using the COMMIT command.
Considerations
If autostatus is not in use, a dialog's error-status field indicates the outcome of a COMMIT command:
|
Status code |
Meaning |
|---|---|
|
0000 |
The request was executed successfully |
|
5031 |
The request is invalid, possibly due to a logic error in the process |
|
5096 |
Too many run units exist for the internal run-unit table |
|
5097 |
An invalid status was received from DBIO. Check the DC/UCF system log for details |
|
Copyright © 2014 CA.
All rights reserved.
|
|