Converting DBOMP to CA IDMS/DB › Converting DBOMP Retrieval and Update Programs

Converting DBOMP Retrieval and Update Programs

The final task in conversion to CA IDMS/DB is converting DBOMP retrieval and update programs.

Steps for Converting Retrieval and Update Programs

Follow the eight steps presented below to convert DBOMP Assembler, PL/I, and COBOL load and maintenance programs to CA IDMS/DB. To obtain the proper record names and descriptions, set names, area names, and subschema names, consult the data dictionary reports produced by the IDMSRPTS utility (see the CA IDMS Utilities Guide).

1. Remove all program references to DBOMP file work areas and work area prefixes.
2. Provide a CA IDMS/DB Communications Block for the program (see the same step under Converting DBOMP Load and Maintenance Programs, in this chapter).
3. Allocate space in the CA IDMS/DB program variable storage for each CA IDMS/DB record type to be referenced in the converted program. The structure of each record type is described in the dictionary Subschema Record Description Listing, or SUBREC report.

   Note: For more information on SUBREC, see IDMSRPTS in the CA IDMS Utilities Guide.

4. Issue an @MODE macro (Assembler only).
5. BIND the subschema and all record types to be referenced in the program.
6. READY those database areas that will be accessed by the program; one READY statement can be issued for all areas, or each area can be READYed explicitly.
7. Convert each DBOMP command and accompanying process indicator to an equivalent DML command. Alter the program logic associated with the DBOMP command as necessary to conform with CA IDMS/DB programming requirements. Refer to the syntax shown under Converting DBOMP Load and Maintenance Programs for the CA IDMS/DB statements that are equivalent to DBOMP commands save process indicators.
8. Check the status code returned by CA IDMS/DB after every call to CA IDMS/DB (see the table under DBOMP Error Codes With CA IDMS/DB Equivalents).