Siemens V 4.0 User Manual

Page of 244
GINA V4.0 System Administrator Guide – September 2000
101
Generated files
Dr
uc
k v
om 24. 01.2001 17:00.37
 torb-k
on
6.6.3
Generated files for BS2000/OSD hosts
6.6.3.1
Development option
The development variant of the command procedure
KDCDF
generates assembler source
files for the following program parts:
GinaRoot
OwnMsgs
The script
KDCDF
automatically calls a file assembly routine and writes the objects created
to an LMS library as the LLM elements
 GINART
and
 OWNMSGS
. The LMS library has the
name
TP_application_name.LIB
. From there they must be linked to the T-ORB applica-
tion. A different library name to the TP application name can be selected via a call param-
eter of the
 KDCDF
script.
The name of the Resource Manager manufacturer from the
 RMXA
statement is incorpo-
rated into the
 GinaRoot
source. If this statement is modified,
 GinaRoot
must be regen-
erated and the application must be linked once more.
❍ ❍ ●
6.6.3.2
Runtime option
gina.config
A file
 GINA.CONFIG
.TP_application_name
is generated for each T-ORB application
(
TA_APPLICATION
) and static T-ORB/client application (
APPLICATION
). It acts as a direc-
tory for addressable applications. Among other things, the file also contains intervals for an
application-specific timer and for controlling events.
Configuration data for the transaction monitor
If the
kdcdf
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
openUTM. The
kdcdf
script must be called in the directory where the
KDCA
file will reside when the appli-
cation is running.
MAX
statements in the configuration description can be used to influence
which files other than
 KDCA
are generated [27].
KDCA
must also exist as a DMS file under BS2000/OSD. To avoid naming conflicts, the file
name is prefixed with the string
GINA
and the TP application name from the configuration
description, i.e.
 GINA.
TP_application_name.KDCA.
If the file
 KDCA
already exists when
 kdcf
is called, it is backed up under the name
old/KDCA
(UNIX) or
 old\KDCA
(WindowsNT) or
OLD.GINA.
TP_application_name.KDCA
(BS2000/OSD).