BMPOPEN

The first call to BMPOPEN causes IMBSBRDG to open the entire CA IDMS/DB database and prepare it for processing: BINDs are issued for the run unit and all record types described in the subschema, and database areas are READYed. The transparency returns the file control record for the file for which RACN has been specified in IMBSTAB. Subsequent calls to BMPOPEN are ignored once the database has been opened.

BMPCLOSE

The first call to BMPCLOSE causes IMBSBRDG to close all areas in the CA IDMS/DB database by issuing a FINISH command. Subsequent calls to BMPCLOSE are ignored once the database has been closed. If any command other than BMPCLOSE is issued after the first BMPCLOSE, the transparency automatically reopens the CA IDMS/DB database and processes the command; a subsequent BMPCLOSE causes the transparency to close the database again.

BMPCALL

The work area prefix for the named file is passed to IMBSBRDG, which interprets the process indicator contained in the work area prefix and performs the requested function. For information on process indicators that are supported by the transparency, see Chapter 3, "The Transparency Environment".

BMPGET

IMBSBRDG retrieves the first record in the named file and returns it to the work area. Subsequent calls to BMPGET using the same file cause IMBSBRDG to retrieve records in logical sequential order from that point if the record type is indexed, or in physical sequential order from that point if the record type is not indexed. When an end-of-file condition is detected, control passes to the routine specified for the file in the BMPEOF command (discussed below).

BMPEOF

IMBSBRDG handles BMPEOF in the same manner as does DBOMP, but obtains the necessary file information from the module generated by the DBOMP CB$BM macro. A call to BMPEOF must specify the end-of-file routines in the same sequence as the corresponding files are entered in the IMBSCOBL macro.

BMPSTKY

IMBSBRDG retrieves a record by the key specified in the work area prefix for the named file and returns the record to the work area. The currency for the file is set at the retrieved record. Subsequent BMPGET commands for the file retrieve records in logical sequential order from that point if the record type is indexed, or in physical sequential order from that point if the record type is not indexed. Note that the transparency's support of logical sequential processing assumes the use of indexing.

BMPSTDA

IMBSBRDG retrieves a record by the disk address specified in the work area prefix for the named file and returns the record to the work area. The currency for the file is set at the retrieved record. Subsequent BMPGET commands for the file retrieve records in logical sequential order from that point if the record type is indexed, or in physical sequential order from that point if the record type is not indexed. Note that the transparency's support of logical sequential processing assumes the use of indexing.

BMPPUT

IMBSBRDG writes back to the CA IDMS/DB database the last record retrieved by a BMPGET command. Chain address fields (pointers) are not updated or written back to the database.

CHASE

The transparency supports this command unconditionally. Programs that request only the CHASE function need not be modified before interfacing with the bridge, and should be linked with the CB$CH macro as indicated in IBM DBOMP documentation.

BMPOFFAD

The transparency does not support this command. If a call to BMPOFFAD is encountered by the bridge, no action takes place and control returns to the calling program.

BMPFO

The transparency does not support this command. If a BMPFO statement is encountered, an unresolved external reference results in the link edit map.

BMPRACN

The transparency does not support this command. If a BMPRACN command is encountered, no action takes place and control returns to the calling program. The transparency's maintenance of RACN in COBOL programs is the same as for Assembler programs.