This document describes how to specify which of a CV's dictionaries will be recognized by Visual DBA as a dictionary instance in its object model.
Release: All supported releases
Component: Visual DBA
During installation, the statements in vdb5v18x.sql (also located in *.CAGJSRC(VDB5V18X) on the mainframe configuration files) are used as input to an IDMSBCF batch job which must be run against all of the dictionaries that Visual DBA should include in its object model. One of the entities it creates is table procedure SYSCA.VDBA_DICTIONARY5. Each column in SYSCA.VDBA_DICTIONARY5 represents a dictionary that Visual DBA will recognize as a dictionary instance in the object model.
By default it is set to this:
CREATE TABLE PROCEDURE SYSCA.VDBA_DICTIONARY5 ( SYSTEM CHARACTER(1), APPLDICT CHARACTER(1), SYSDICT CHARACTER(1) ) EXTERNAL NAME VDBADICT DEFAULT DATABASE NULL USER MODE LOCAL WORK AREA 1024 ;
To change which dictionaries will be recognized by Visual DBA as a dictionary instance, then change this definition before running the script.
For example, if Visual DBA should also recognize PRODDICT as a dictionary instance, then change it to this:
CREATE TABLE PROCEDURE SYSCA.VDBA_DICTIONARY5 ( SYSTEM CHARACTER(1), APPLDICT CHARACTER(1), SYSDICT CHARACTER(1), PRODDICT CHARACTER(1) ) EXTERNAL NAME VDBADICT DEFAULT DATABASE NULL USER MODE LOCAL WORK AREA 1024 ;
Ideally this should be done before running the script. If the script has already been run, then manually change the table procedure in every dictionary in which it has been created by performing a DROP and (re-)CREATE of the table procedure.
For example:
DROP TABLE PROCEDURE SYSCA.VDBA_DICTIONARY5;CREATE TABLE PROCEDURE SYSCA.VDBA_DICTIONARY5 ( SYSTEM CHARACTER(1), APPLDICT CHARACTER(1), SYSDICT CHARACTER(1), PRODDICT CHARACTER(1) ) EXTERNAL NAME VDBADICT DEFAULT DATABASE NULL USER MODE LOCAL WORK AREA 1024 ;
Note: This table procedure must contain a column for the dictionary that is specified on the ODBC datasource that is used to connect to IDMS from Visual DBA. For example, the following datasource has Dictionary: APPLDICT, so SYSCA.VDBA_DICTIONARY5 must include a column called APPLDICT.
See Error popup "Parent Object does not exist" in IDMS Visual/DBA.