In order to successfully analyze Hogan calls, you need to supply information about the Hogan configuration extracted from the Hogan system. This is done using external configuration files. The following table describes the necessary files:
| HOGAN CDMF EXTRACT FILE | Artifact Type | Data Record Contents | Name |
|---|---|---|---|
| BNS.CIS.ACTS | Activities | Activity type (e.g. LINK)
Program definition ID |
CDMFACTS |
| BNS.CIS.PGMS | Program Definitions | Program source name
Program load name Data Groups Used Activities Authorized |
CDMFPGMS |
| BNS.CIS.DGS | Data groups | Copybook name | CDMFDGS |
| BNS.CIS.MAPS | Maps | Map name
IMS tran code |
CDMFMAPS |
| BNS.CIS.TXNS | Transaction definitions | Transaction code
PSB name Activities executed |
CDMFTXNS |
| BNS.CIS.HDBS | Hierarchical DB definitions | Database name
Segment names Segment data group IDs |
CDMFHDBS |
| BNS.CIS.SDBS | Sequential file definitions | File ID
File description File type (I/O) DD name |
CDMFSDBS |
| BNS.CIS.X200 | Non-Hogan PGM interface definitions | Non-Hogan program
LINK activity ID Non-Hogan PGM load name |
CDMFX200 |
The configuration filename required by Enterprise Analyzer is of the form BNS.CIS.XXXX => CDMFXXXX.hogan. For example, BNS.CIS.PGMS must be named CDMFPGMS.hogan for it to be processed by the EA utility.
Specify the location of the configuration files in . An example location is: C:\samplecode\hoganconfig.
The expected format of the Hogan configuration files is described in the next topics.