Using Transparency for DBOMP

The CA IDMS DBOMP Transparency facilitates conversion from DBOMP or its Z/OS equivalent, CFMS, to CA IDMS/DB. By simulating the DBOMP environment, the transparency allows you to run existing DBOMP application programs after the DBOMP files have been converted to CA IDMS/DB database files. This allows for a gradual conversion from DBOMP to CA IDMS/DB.
idms
The CA IDMS DBOMP Transparency facilitates conversion from DBOMP or its Z/OS equivalent, CFMS, to CA IDMS/DB. By simulating the DBOMP environment, the transparency allows you to run existing DBOMP application programs after the DBOMP files have been converted to CA IDMS/DB database files. This allows for a gradual conversion from DBOMP to CA IDMS/DB.
Minimal User Involvement
The CA IDMS DBOMP Transparency is usually transparent to the DBOMP retrieval and update programs that it bridges, requiring little or no program alteration and usually no reassembly.
Conversion Tool
To aid you in converting DBOMP load and maintenance programs, the transparency package includes a prototype CA IDMS/DB bill-of-materials application program. This program shows the logic required to add records to and delete records from a CA IDMS/DB database.
System Requirements
The transparency requires no operating system facilities other than those necessary for CA IDMS/DB.
Two of the CA IDMS DBOMP Transparency modules, IMBSBRDG and IMBSTAB, require 5Kb memory in addition to that needed for standard CA IDMS/DB processing. Disk storage and all other memory requirements are the same as for CA IDMS/DB. The transparency operates under the CA IDMS/DB central version or in local mode.
This section is intended for:
    • Database administrators who are converting DBOMP databases to CA IDMS/DB databases
    • Application programmers who are using existing DBOMP application programs to access CA IDMS/DB databases