The Global Database Information Container (GDIC) is a dynamic-link library to gather and supply database connection information for CA Gen generated GUI applications. It implements a shared cache of connection profile entries, or nodes, that GUI applications access for connection information.
The file iefgdic.ini stores information for these nodes. The information includes the following keyword sets:
|
Keyword |
Value |
|---|---|
|
Database |
Database to access. dbname stores this database name. Database is the key to use in the iefgdic.ini lookup. |
|
Trancode |
Transaction code in a load module to connect from. |
|
LoadModule |
Specific load module to connect from. |
|
Server |
Database server name. Required for connection. (ODBC only) |
|
SQLid |
Database connection identifier. Required for connection. |
|
SQLpassword |
Database connection password. Required for connection. |
There are one or more keyword sets in the [RDBMS] section, where RDBMS is a supported GUI RDBMS: Oracle, DB/2 or ODBC. Each keyword in the keyword set is appended with an incremental value to help identify each keyword set.
Example:
[MaxDatabases] Max=100 [ORACLE] DatabaseCount=2 Database1=ABLK05 Trancode1= LoadModule1= Server1= SQLid1=ptauto SQLPassword1=ptauto Database2=ora102 Trancode2= LoadModule2= Server2= SQLid2=ptauto SQLPassword2= [DB2/2] DatabaseCount=1 Database1=ABLK05 Trancode1= LoadModule1= Server1= SQLid1=ptauto SQLPassword1=ptauto [ODBC] DatabaseCount=1 Database1=ABLK05 Trancode1= LoadModule1= Server1=ABLK05 SQLid1=ptauto SQLPassword1=ptauto
In this example, MaxDatabases has value of 100, indicating this file can hold up to 100 keyword sets. There are three (3) RDBMS sections: Oracle, DB/2 and ODBC. The Oracle section has two (2) keyword sets, and DB/2 and ODBC only have one (1), identified by DatabaseCount.
The iefgdic.ini file stores the database connection information and can be in multiple locations. The system searches for the file in this order:
If the system fails to locate the iefgdic.ini file using this search order, it creates it in the %USERPROFILE%\AppData\Local\CA\Gen xx\cfg\client directory.
If a database DLL requires connection information, it calls a GDIC function to get the information from the iefgdic.ini file for the calling DLL. The GDIC displays an input window, pre-populating as many fields as possible, and allows the user to fill in the blanks or overwrite the pre-populated fields. If all the required fields are extracted from the iefgdic.ini file, the GDIC bypasses the input window. If you look back at the previous example, the first keyword set for each RDBMS has all the required fields, allowing the GDIC to bypass the input window for the specified database.
|
Copyright © 2013 CA.
All rights reserved.
|
|