The transparency supports most Total DML statements that access and update the database. Almost all Total DML statements supported by the transparency translate directly to corresponding CA IDMS DML statements. The Total DML statements described in the following table are translated to CA IDMS, but with some variations in function. The variations are explained in the table.
Note: Total DML recovery and logging functions are not converted to CA IDMS/DB. CA IDMS/DB provides recovery utilities and journaling options that adequately replace these Total DML functions.
|
For this Total DML statement |
CA IDMS TOTAL Transparency does the following: |
|---|---|
|
CNTRL (purge) |
Ignores the command |
|
COMIT |
Issues a COMMIT ALL |
|
ENDLG |
Issues a COMMIT |
|
FREEX |
Issues a COMMIT ALL |
|
QMARK |
Issues a COMMIT |
|
QUIET |
Issues a COMMIT |
|
SINON and OPENX
|
After the runtime system processes a Total SINON or OPENX command, it will not reissue the CA IDMS/DB BIND/READY sequence. When a SINON command is issued, the runtime interface performs the following actions:
|
|
CLOSX and SINOF
|
Issues a FINISH statement FINISH releases all database areas (and therefore all database records) from program control. If a SINOF command is preceded by a CLOSX command, the runtime interface does not issue a FINISH in response to the SINOF command. |
|
RQLOC (batch)
|
Accepts a key value from the Total application and returns a suitable DBKEY value. Note that for RQLOC, the module IDMSCALC is required. If IDMSCALC is not link edited to ETOTBINT, it is loaded the first time the RQLOC function is invoked. |
|
Copyright © 2013 CA.
All rights reserved.
|
|