Table Procedure Examples, Design, and Use › Specify a DBName for Table Procedures

Specify a DBName for Table Procedures

When CA IDMS accesses database records via SQL statements, as is the case for table procedures, the DBNAME value specified in your signon profile has no affect on which database is used. Instead, the DICTNAME value identified in a system DCUF statement or ODBC CONNECT statement identifies the SQL catalog that contains the information needed to locate the target database.

A generated table procedure contains a BIND RUN-UNIT statement that does not include a DBNAME parameter because it assumes that the SQL catalog points to the correct DBNAME. In some cases, this assumption means that the CA IDMS accesses the wrong target database or no database at all (IDMS error status 1491).

If you find that CA IDMS is accessing the wrong target database or no database for a specific table procedure, then:

• Map to the correct subschema in the DBTABLE statement, as described in the CA IDMS Database Administration Guide.
• Include a DBNAME in the BIND RUN-UNIT statement in the generated COBOL table procedure using either a hard-coded DBNAME or a GETPROF call to the IDMSIN01 subroutine to return the current DBNAME.