This document describes how to specify the dictionaries in a given CV that Visual DBA can access.
During the installation, the statements in vdb5v18x.sql are used as input to an IDMSBCF batch job against all of the dictionaries that should be managed by Visual DBA.
One of the entities it creates is table procedure SYSCA.VDBA_DICTIONARY5.
Each column in SYSCA.VDBA_DICTIONARY5 represents a dictionary that Visual DBA can manage
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
;
If you want your Visual DBA installation to manage a different collection of dictionaries, then change this definition before running the script.
For example, if you also want Visual DBA to be able to access another dictionary called PRODDICT, 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 you have already run it, then manually change the table procedure in every dictionary in which you have created it 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.