The Transparency Environment › DBOMP Routines Supported

DBOMP Routines Supported

The transparency provides the logic for limited maintenance of the Run Activity Control Number (RACN). If you want to retain RACN logic in bridged programs, modify RACN processing within each program to accommodate the limited support provided by the transparency.

Note: The transparency does not acknowledge low-level code logic or chain count logic. The presence of low-level code or chain count fields in a DBOMP file does not necessitate program modification. These fields are ignored.

The transparency supports RACN logic as follows:

• RACN processing is maintained for only one DBOMP file
• OPEN processing causes the transparency to return to the calling DBOMP program the file control record for the file for which RACN has been specified
• CLOS processing causes the transparency to MODIFY the file control record, thereby returning it to the database

Once the file control record has been made available to the program, the transparency ignores it until a CLOS process indicator is issued. All RACN logic is executed independently of the transparency so the contents of the file control record can be manipulated by the executing program as you wish. When the transparency encounters a CLOS process indicator, it modifies the file control record, whether or not the DBOMP program has updated that record.

You are responsible for storing (in the CA IDMS/DB database) one occurrence of the record for which RACN processing is specified. The database key for this record must be initialized to binary zeros.