Network Router User Manual

100 GINA V4.0 System Administrator Guide – September 2000
Generated files
For T-ORB applications and static T-ORB clients, this file is generated in the directory
assigned to the application; for dynamic clients the file is created in the directory of the host
on which the dynamic clients are configured.
The gina.config file must normally be copied to the directory where the application is
called. You can, however, choose a directory other than "." using the environment variable
GINACONFIG.
gina.dynamic
A file gina.dynamic is generated for each host for which dynamic T-ORB clients are con-
figured (statement DYNAMIC_CONNECT). This file contains information on the dynamic con-
nections and is used by DomsDynConnectHandler (see Dynamic Connection Handler on
page 197).
Configuration data for the transaction monitor
If the kdcdf.bat script was created with the runtime option config -r, it generates a file
KDCA and possibly other elements of KDCFILE. This data is configuration data for
open UTM. The kdcdf.bat script must be called in the directory where the KDCA file will
reside when the application is running. Before the call, ensure that the %PATH% variable
contains <install-dir>\bin (where <install-dir> is the GINA installation direc-
tory). MAX statements in the configuration description can be used to influence the files
other than KDCA which are generated [26]. If the file KDCA already exists when kdcf.bat
is called, it is backed up under the name old\KDCA (UNIX).
Start and administration scripts
The runtime variant of kdcdf.bat (created using config -r) generates scripts for start-
ing and administering a T-ORB application when called.
– utmstart.multi.bat
Start procedure for the application
– utmstart.single.bat
Start procedure for the debug variant of the application
– start
Start parameters for open UTM
– dtp.bat
Procedure for open UTM administration