umschlag Druck vom 24. 01.2001 17:00.14 GINA V4.
Comments Suggestions Corrections The User Documentation Department would like to know your opinion on this manual. Your feedback helps us to optimize our documentation to suit your individual needs. Fax forms for sending us your comments are included at the back of the manual. Order number of this manual: GINA V4.
titel Druck vom 24. 01.2001 17:00.15 GINA V4.
Copyright and Trademarks GINA is a registered trademark of Siemens Business Services GmbH & Co OHG. SINIX® Copyright © Siemens Nixdorf Informationssysteme AG 1990. SINIX is the UNIX® System derivative of Siemens Nixdorf Informationssysteme AG. Reliant® is a registered trademark of Pyramid Technology Corporation. UNIX is a registered trademark in the United States and other countries, licensed exlusively through X/Open Company Limited. Base: OSF/Motif™, Copyright © Open Software Foundation, Inc.
Introduction Changes since Version 3 Installation and deinstallation Creating GINA applications Configuring the Persistency Service Configuring T-ORB for openUTM Configuring T-ORB for BEA TUXEDO Operating GINA applications Glossary Abbreviations Continued
Related publications Index
verwivz.doc Druck vom 24. 01.2001 17:00.16 Contents 1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1 2 2.1 2.2 Changes since Version 3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Interface cancelations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Revisions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 5 7 3 3.1 3.2 3.2.1 3.2.2 3.2.3 3.3 3.3.1 3.3.2 3.3.3 3.3.4 3.3.5 3.4 3.4.1 3.4.2 3.4.3 3.
5.2 5.2.1 5.2.2 5.2.3 Customizing the database layout . . The pfx file . . . . . . . . . . . . . The tbl file . . . . . . . . . . . . . . Further options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33 34 35 40 6 6.1 6.2 6.2.1 6.2.2 6.2.3 6.3 6.4 6.5 6.6 6.6.1 6.6.1.1 6.6.1.2 6.6.2 6.6.2.1 6.6.2.2 6.6.3 6.6.3.1 6.6.3.2 6.6.4 6.7 6.
verwivz.doc Druck vom 24. 01.2001 17:00.17 7.6 7.6.1 7.6.2 7.6.3 7.7 7.7.1 7.7.2 7.7.3 7.7.4 7.7.5 Generated files . . . . . . . . . . . . . . Generated files for UNIX hosts . . . . . . Generated files for WindowsNT hosts . . Example . . . . . . . . . . . . . . . . . BEA TUXEDO domains . . . . . . . . . . Statements . . . . . . . . . . . . . . . . Syntax . . . . . . . . . . . . . . . . . . Example of a configuration file with domains Generated files . . . . . . . . . . . . . . Special points . . . . . . .
GINA V4.
einleit Druck vom 24. 01.2001 17:00.18 1 Introduction GINA (General Interface for Network Applications) provides a framework for the implementation and operation of object-oriented, transaction-oriented client/server applications. The GINA-API is an object-oriented solution for the mixed, distributed applications which are encountered everywhere in modern business life.
Structure of this manual Chapter 1 describes the structure and contents of this manual as well as other documentation on GINA. Chapter 2 contains a listing of the essential changes since the last version of this manual as well as a brief description of each. Chapter 3 Installation and deinstallation describes the installation of GINA, including prerequisites. Chapter 4 Creating GINA applications describes the necessary steps in creating GINA applications. Chapters 5 ...
einleit Druck vom 24. 01.2001 17:00.18 GINA Developer Manual GINA Developer Manual This manual is intended for developers of GINA applications. It provides a detailed description of GINA concepts and gives practical instructions and assistance for use.You should read this manual first as it describes the theory and principles on which GINA is based. Application developers should be familiar with the fundamentals of the object-oriented paradigm; knowledge of C++ is essential.
Notational conventions used in this manual This character draws your attention to special features or points of interest; you will also find useful or secondary information there. ❍❍● Particular attention must be paid to the information indicated by this symbol. ❍❍● Terms that are explained in the text are highlighted in bold. Program code, messages, keywords or class names are indicated by typewriter text. Italic typewriter text indicates variables for parameters that you must enter.
aender Druck vom 24. 01.2001 17:00.19 2 Changes since Version 3 2.1 Interface cancelations The interfaces listed in the following section were changed in Version 4.0 of GINA. This version contains the new variant. Each section indicates the GINA version as of which the relevant interface or its old variant is no longer supported. G_Exception eliminated In earlier versions, GINA used the exception handling simulation of the Generic++ class library [11] on some platforms.
Interface cancelations Changing the names of the iterator methods max/min to maxValue/minValue The methods max and min in the iterator classes PMibs::MibsFilterIt, PMibs::MibsSeqIt, and VIEWITERATOR(P) were renamed maxValue and minValue respectively in Version 3.0 of GINA in order to prevent conflicts with the max and min macros defined in some environments. The old API containing the method names max and min was supported as a transitional aid.
aender Druck vom 24. 01.2001 17:00.19 Revisions 2.2 Revisions Replacement of idlgen by idlgen1 The idlgen1 generates two definitions from an interface definition (x.idl) specified in CORBA-IDL (Revision 2.2): x.hi which defines the data members to be encoded and decoded and x.hd which defines the methods to be exported. The interim format x.hi serves as input for the MIO generator miogen2. The interim format x.hd serves as input for the T-ORB generator dogen2. GINA V4.
Revisions 8 GINA V4.
install Druck vom 24. 01.2001 17:00.19 3 Installation and deinstallation This chapter describes how to install and deinstall GINA. Some of the technical information given here is for the purposes of example only, e.g. it may vary partially depending on the details of the operating system.
Requirements 3.1 Requirements The following third-party products are required to implement the GINA components. Please note that the products listed may be based on other products, which must then likewise be installed. Up-to-date information on the products required can be found in the Release Notice included in the delivery. ❍❍● ● Generic++ V2.5 [11] GINA requires the class library Generic++ V2.5, which is contained in the GINA scope of supply and is installed under the name libsupport2. ● openUTM V5.
install Druck vom 24. 01.2001 17:00.20 Scope of supply and structure of GINA 3.2 Scope of supply and structure of GINA This section describes the delivery packages and the general delivery structure of GINA Version 4.0. 3.2.1 Delivery package GINA V4.0 is supplied as a full-feature version (UNIX, NT) and as a partial version (WindowsNT only).
Scope of supply and structure of GINA 3.2.2 Licensing of GINA The tool FLEXlm from the company GLOBEtrotter is used to license GINA. Both the generators and the GINA runtime system are protected by licenses. Before GINA can be used, the GINA Competence Center must generate the licenses for the machine you require (processor ID) and convey them to you. If you require an evaluation license, refer to the Release Notice for a template which you must return completed to the GINA Competence Center.
install Druck vom 24. 01.2001 17:00.20 Scope of supply and structure of GINA Structure of the license file The license file has the following structure: Keyword License DaemonVersion Valid N License code Processor ID Licensename Example FEATURE GinaDEV ginad 1.
Scope of supply and structure of GINA 3.2.
install Druck vom 24. 01.2001 17:00.21 Installation 3.3 Installation The installation procedures depend on the system base. The variants described here are examples only. You must always perform installation and deinstallation in accordance with the description of your system base or the information in the Release Notice. ❍❍● GINA is shipped as a package which is created using a system-specific packet assembly procedure (package under UNIX, setup under NT). The full-feature version of GINA V4.
Installation 3.3.1 UNIX (Solaris, SINIX) Start the installation under UNIX using the command pkgadd. The installation directory in which GINA is to be installed may not exist before the pkgadd command is called. ❍❍● 1. Log in as root. 2. Set up a new user group tmns. 3. Set up a new user gina. 4. Create a new directory e.g. /opt/gina for GINA: mkdir -p /opt/gina chmod 775 /opt/gina chown gina:tmns /opt/gina 5a.
install Druck vom 24. 01.2001 17:00.21 Installation 5b. The following steps are required if the GINA package is stored on the delivery CD in compressed format: ◊ Copy the GINA package from the CD to an intermediate directory cp /.gz ◊ Unpack the file in the intermediate directory using gunzip.
Installation 3.3.3 Windows NT Installation of the full-feature or partial version (RT version) under Windows NT is performed using the setup command, the installation tool is included in the GINA package on the delivery CD. 1. Log in as administrator. 2. Create a new directory for GINA. 3.
install Druck vom 24. 01.2001 17:00.22 Installation Example for csh – Solaris, SINIX setenv LD_LIBRARY_PATH /lib:$LD_LIBRARY_PATH – HP-UX setenv SHLIB_PATH /lib:$LD_LIBRARY_PATH On Windows NT all information necessary to the operation of the PS browser is entered during installation by the setup routine. That is, the environment variable GINADIR points to the file , <%GINADIR%\bin> is added to the PATH variable.
Installation 3.3.4 BS2000 The following steps are required when installing under BS2000: 1. Log in to BS2000/OSD under the name $GINA 2. Read in the tape using ARCHIVE, IMPORT ..., DEVICE=TAPE-C4 The following DVS files are created under the $GINA account: GINA.PAX pax archive containing the POSIX files of the transfer LIBxxx libraries of the GINA runtime system in PLAM format 3. Copy GINA.
install Druck vom 24. 01.2001 17:00.22 Installation 3.3.5 Environment variables Certain environment variables must be set when implementing the various components of GINA. Depending on the components implemented, these variables are: Using the T-ORB on basis of openUTM UTMPATH This environment variable contains the path of the installed openUTM environment. UPICPATH This environment variable contains the name of the directory with the upicfile file.
Installation Implementation of the Persistency Service INFORMIXDIR This environment variable contains the name of the directory for the installed INFORMIX environment. The environment variable PATH must contain an $INFORMIXDIR/bin entry. INFORMIXSERVER This environment variable identifies the current instance of the database server processed by the application database.
install Druck vom 24. 01.2001 17:00.23 Deinstallation 3.4 Deinstallation The installation procedures used depend on the system base; the variants described below are examples only. Installation and deinstallation should, therfore, always be carried out as described for your system base or in accordance with the information contained in the Release Notice. ❍ ❍ ● System-specific commands are used to deinstall GINA. 3.4.1 UNIX (Solaris, SINIX) 1. Log in as root. 2.
Deinstallation 3.4.3 Windows NT Deinstallation of GINA under Windows NT, Windows95 and Windows98 is performed by selecting the Software icon (Start > Settings > System Controls). Then select GINA, and start the graphical deinstallation interface. The necessary information is queried in the dialog box. The GINA package is then deinstalled, and the subdirectories and files are deleted. 24 GINA V4.
install Druck vom 24. 01.2001 17:00.23 Availability, restrictions 3.5 Availability, restrictions This section provides information on platform-related restrictions, the availability of the GINA components as well as libraries which are missing. UNIX with CFront compilers The GINA component PS/client is not available on UNIX systems with CFront compilers (e.g. HP-UX). WindowsNT ● The configuration generator for T-ORB with the graphical interface (WinConfig) is not available. ● INFORMIX V9.
Availability, restrictions ● Configuration file The configuration file (the file that reads the config) must contain the line OPERATING_SYSTEM("OS_WINNT") for both WindowsNT and Windows95. ● Environment variable The COMPUTERNAME environment variable is automatically set on WindowsNT, it must be set by the user on Windows95. BS2000/OSD The PS/client (client part) as well as the direct database system connection are not available in the runtime system of T-ORB/client under BS2000/OSD.
inbtrieb Druck vom 24. 01.2001 17:00.23 4 Creating GINA applications GINA applications comprise a range of modules which must be linked as a program before execution time, at the latest. Since GINA represents a framework which offers different functionality in different variants, special activities must be carried out to create an application, depending on its specific type. Further details are provided in the following sections. 4.
Environment Type 6 GINA applications associated with a Persistency Service/client application These use T-ORB and the Persistency Service of GINA jointly. Type 7 Dynamic client without a PS/client component Type 8 Dynamic Persistency Service/client applications Application of the type 5 as a dynamic client with a PS/client component. Depending on the type of your application, you may have to specify different libraries when linking. 4.
inbtrieb Druck vom 24. 01.2001 17:00.24 The generators 4.3 The generators The generators of GINA can be found in the bin directory of the GINA installation (see section 3.2 on page 11).
Makefiles 4.4 Makefiles Software development for larger systems, in particular, is much easier to handle with the UNIX program make. The Developer Manual [13] contains a detailed example of a possible makefile configuration. 30 GINA V4.
per-konf Druck vom 24. 01.2001 17:00.24 5 Configuring the Persistency Service When examining the configuration of the Persistency Service, it is generally a good idea to consult the documentation relating to the underlying database management system. All explanations in this chapter relate to the database management system INFORMIX on the UNIX platform. The environment can be different for other database management systems or on other operating systems. 5.
Setting up the database To enable these aims to be achieved, knowledge is required on datasets and their dynamics (static, low frequency of change, high rate of change), as well as the access behavior to the data (navigating, value-based). This information is supplied to the Persistency Service generator as customizing[14] input in an optimization process.
per-konf Druck vom 24. 01.2001 17:00.24 Customizing the database layout 5.2 Customizing the database layout GINA offers you the option of customizing the database layout and the access privileges. One aspect of this relates to the assignment of names of database tables for persistent classes, whereby the default is that the class names of the specialist models are also used to designate the database tables.
Customizing the database layout 5.2.1 The pfx file The description file that is called using the -r option, the so-called pfx file, handles the specification of class-wide attribute names. The attribute names used for the mapping to the database consist of the following components: classPrefix_attributCounter_extension classPrefix is the part of the field name that is common to all fields in a class. Neither does inheritance change it, i.e. it has the same value in the subclass as in the superclass.
per-konf Druck vom 24. 01.2001 17:00.25 Customizing the database layout 5.2.
Customizing the database layout name Name of the table to which the specialist model classes are to be mapped. The default value is the class name. Optional entry resource Entry to identify a dbspace in which the tables are to be stored. Such a dbspace is a storage area which is based on the physical storage media. Additional storage instructions are entered using the “fr definition lines” and result in the fragmentation of the table.
per-konf Druck vom 24. 01.2001 17:00.25 Customizing the database layout 2. Fragmentation of a database table A fragmentation line contains the following fields: fr | ident | resource | A number of definition lines of this type are permitted per class, at least two resources must be defined for the purpose of fragmenting. Note that a partitioning of storage space which is taken into account during the fragmentation can also be specified in the t definition line.
Customizing the database layout 4. Versioning of the database A version line contains the following entries: v | indent| Only one version line is permitted per database. ident Version of the database schema (string with a maximum of 30 characters) Mandatory entry Example v | 1.0 | 5. Access privileges for tables and identical views A privilege line contains the following entries: s | ident | name | resource | A number of definition lines of this type are permitted per class.
per-konf Druck vom 24. 01.2001 17:00.26 Customizing the database layout Example s | myClassname | hubert | INSERT | If a user is assigned the DELETE privilege, he/she also needs the SELECT privilege for the purpose of internal consistency checks. ❍❍● GINA V4.
Customizing the database layout 5.2.3 Further options The mgendb tool can also be used to influence the configuration of the database. In addition to specifications concerning the default database user and NLS/GLS specifications, the -d option can be used to determine a dbspace in which the database tables to be created are to be set up. The mgendb supports the following options: -d dbspace The named dbspace of the database instance is used as the default storage area of the database to be generated.
per-konf Druck vom 24. 01.2001 17:00.26 Customizing the database layout Note ltype must be a valid locale on the database server platform. If mgendb is called in another operating system environment, errors can occur since ltype is not recognized as a valid locale identifier. Therefore mgendb should be called on the same platform as the one on which the database server is running. -u userName A default database user can be entered if this option is specified.
Customizing the database layout 42 GINA V4.
torb-kon Druck vom 24. 01.2001 17:00.26 6 Configuring T-ORB for openUTM This chapter describes how to configure communication between GINA applications. The configuration does not require any modifications to the source program. However, it cannot take place while the application is running; rather it must be performed before the application starts. The configuration of T-ORB is based on the configuration of openUTM [29] and openUTMClient [31].
Overview transmitted by both sides. The controlling application simply has priority over the passive application. From a performance point of view, the controlling application should be the one which generally (or more frequently) opens the communication. The definition of the type and number of all connections between the applications is equivalent to the definition of the communication structure for the entire system.
torb-kon Druck vom 24. 01.2001 17:00.26 Overview The communication structure of a system can be depicted by a graph with nodes and edges. The nodes correspond to the applications, while the edges represent the communication channels. The first three blocks in the diagram define the nodes of the graph with respect to the specific system, host or application; the last block describes the edges of the graph.
Configuration language 6.2 Configuration language The configuration generator config reads a text file which describes the configuration of the entire system in a T-ORB-specific language. This file contains the necessary information on the network protocol, the transaction monitor, T-ORB, and the specialist application. The elements of the language include keywords, literals, separators and comments. Blanks, tabs, line feeds, form feeds and white spaces are ignored.
torb-kon Druck vom 24. 01.2001 17:00.27 Configuration language The ADDRESS statement describes how the GINA application is to be addressed by the foreign openUTM application. It has the following parameters: – – local name of the GINA application (LETTER) name of the local transaction code (LETTER) APPLICATION The APPLICATION statement describes a client which is connected via T-ORB/Client. It comprises the following components: – OsId of the application (NUMBER, 1 ...
Configuration language ASYN_PRIORITY The ASYN_PRIORITY statement defines the priority classes for the processing of asynchronous requests (see also the description of the PRIORITIES keyword).
torb-kon Druck vom 24. 01.2001 17:00.27 Configuration language RELATIVE attribute: Relative priority Free processes will be assigned to higher priority classes more often than lower priority classes provided that there are pending or interrupted requests for these higher priority classes. If there are requests present for all classes, a free process will be assigned to TAC class 9 twice as often as to TAC class 10, and twice as often to TAC class 10 as to TAC class 11, etc.
Configuration language CYCLIC attribute A so-called administration order is created for each cyclical timed request (DomsClient::cyclicOrder). This administration order makes sure that the cyclical timed request is executed in the selected timeframe. The CYCLIC attribute can be used to determine the priority class in which these administration orders are to run. CYCLIC can only be specified for one priority class.
torb-kon Druck vom 24. 01.2001 17:00.28 Configuration language The CANCEL statement on system level applies to all hosts if there is no CANCEL statement in the HOST statement. The CANCEL statement on host level applies accordingly to all TA applications if there is no CANCEL statement in the TA_APPLICATION statement. CHECK The CHECK statement of the EVENTCONTROL block defines the interval after which an event on a client is overdue, i.e.
Configuration language CYCLICORDER The CYCLICORDER statement defines the maximum number of cyclical tasks permitted per TA_APPLICATION. The default value is CYCLICORDER(10). The CYCLICORDER statement on system level applies to all hosts if there is no CYCLICORDER statement in the HOST statement. The CYCLICORDER statement on host level applies accordingly to all TA applications if there is no CYCLICORDER statement in the TA_APPLICATION statement.
torb-kon Druck vom 24. 01.2001 17:00.28 Configuration language EVENTCONTROL The EVENTCONTROL statement comprises the following components: – – – CYCLE CHECK CANCEL Each component is optional. Example EVENTCONTROL { CYCLE ( 0, 0, 20, 0 ) CHECK ( 0, 2, 0, 0 ) CANCEL ( 3, 0, 0, 0 ) } FOREIGN_APPLICATION The FOREIGN_APPLICATION statement describes a foreign openUTM application. It comprises the following components: – – – – OsId of the application (NUMBER, 1 ...
Configuration language FOREIGN_SESSION The FOREIGN_SESSION statement describes connections between a GINA application and a foreign openUTM application. It comprises the following components: – – – – session type (LETTER); the generator currently supports LU6.1 mapping (optional MAP_SYSTEM parameter) MAP= controls ASCII/EBCDIC conversion when exchanging unformatted messages with other applications.
torb-kon Druck vom 24. 01.2001 17:00.28 Configuration language IMPORT The IMPORT statements on the system level apply to all hosts, if there is no IMPORT statement with the same file name in the HOST statement. The IMPORT statements on the host level apply accordingly to all applications, if there is no IMPORT statement with the same parameters in the application.
Configuration language The following number of keys must be defined for each application: – 1 key each for CACHESHMKEY, IPCSHMKEY and KAASHMKEY – (6 + n + m)/10 semaphore keys for SEMKEY n = maximum number of work processes m = maximum number of communication partners connected simultaneously When calculated, the value must be rounded off to a whole number. MAX The MAX statement allows you to customize TP applications.
torb-kon Druck vom 24. 01.2001 17:00.29 Configuration language NET_ACCESS The NET_ACCESS statement describes the manner in which the application is linked to the network. The NET_ACCESS statements on system level apply to all hosts if there is no NET_ACCESS statement with the same name in the HOST statement. The NET_ACCESS statements on host level apply accordingly to all applications.
Configuration language PORTADDRESSES The PORTADDRESSES statement contains the port numbers for the TNSX entries. The statement has the following parameters: – – first port number last port number See the CMX documentation [7] for information on value ranges. The difference between the start address and end address must be large enough for each BCAMAPPL entry on the host to have its own port number.
torb-kon Druck vom 24. 01.2001 17:00.
Configuration language The attribute SYNC_WAIT specifies whether synchronous calls (callAndWait, addToChain and execChainAndWait) are permitted in this TAC class. This attribute can only be assigned to one of the three TAC classes. The PRIORITY statement may only be used once on system, host or TA application level. The PRIORITY statement on the system level applies to all hosts, if there is no PRIORITY statement in the HOST statement.
torb-kon Druck vom 24. 01.2001 17:00.30 Configuration language RMXA The RMXA statement describes a Resource Manager. The RMXA statements on system level apply to all hosts if there is no RMXA statement of the same name in the HOST statement. The RMXA statements on host level apply accordingly to all applications.
Configuration language The SCHEDULE statement can be used to assign functions, instance methods, class methods or all methods of a class to a specific priority. Classes, class methods, instance methods and functions that are not explicitly assigned to a specific category using the SCHEDULE statement will be automatically assigned to the second highest priority class.
torb-kon Druck vom 24. 01.2001 17:00.30 Configuration language SESSIONPOINT The SESSIONPOINT statement specifies the number of connections that can be controlled by an application.
Configuration language START_RM The START_RM statements on system level apply to all hosts if there is no START_RM statement with the same manufacturer name in the HOST statement. The START_RM statements on host level apply accordingly to all applications. The optional START_RM statement has the following parameters: – – manufacturer name of the database Openstring OS If the keyword APPLICATION is written instead of the Openstring parameter, the TA_application name is used as the Openstring.
torb-kon Druck vom 24. 01.2001 17:00.31 Configuration language The SYNC_PRIORITY statement can be used to define up to seven classes (PRIO1 through PRIO7). As part of this process, PRIO1 is mapped to TAC class 2, PRIO2 to TAC class 3 etc. of openUTM. TAC class 2 has the second highest priority, TAC class 8 the lowest. TAC class 1 with the highest priority is reserved for the T-ORB.
Configuration language PGWT attribute If a priority class is assigned requests that need to execute callAndWait and execChainAndWait calls, the class must have the appropriate authorization. The PGWT attribute can be used to grant this authorization to the priority class. PGWT can be specified for each priority class. Further information on the RELATIVE, ABSOLUTE and EQUAL attributes as well as on the free_sync parameter can be found in the openUTM documentation V5.
torb-kon Druck vom 24. 01.2001 17:00.31 Configuration language This statement acts as a wildcard so that a GINA-SESSION between a T-ORB application without the flag RESERVE and a T-ORB application with the flag RESERVE can be defined (see SESSION). A T-ORB application can then be generated from this session in the event of a revision generation. The normal syntax of this statement must then be used. OsId and LayerId may not then be changed.
Configuration language 6.2.2 Lexical structure This section describes how the configuration generator combines the contents of the configuration file into symbols (like the keywords) for syntax analysis. The description is in the notation used by the UNIX command lex. %{ %} letter DGS letter_or_digit [a-zA-Z_] [0-9]+ [a-zA-Z_0-9] %% [ \t\n\v\r\f]+ \/\/.*\n \{ \} \( \) \, \= {DGS} ; ; {return(BBOPEN);} {return(BBCLOSE);} {return(SBOPEN);} {return(SBCLOSE);} {return(COMMA);} {return(EQUAL);} {yylval.
torb-kon Druck vom 24. 01.2001 17:00.31 Configuration language 6.2.3 Syntax This section describes the syntax of the configuration language in the notation used by the UNIX command yacc.
Configuration language %token %token %token %token %token %token %token %token %token %token %token %token %token %token %token %token %token %token %token %token %token %token %token %token %token %token %token %token %token %token %token %token %token %token %token %token %token %token %token %token %token %token %token %token 70 IN_CONVERTER KEY_VECTOR MAX_STMT MPOOL NET_ACCESS OPERATING_SYSTEM OUT_CONVERTER PORTADDRESSES PRIO PRIORITIES PRIORITY REPOSITORY REREADTIME RMXA SCHEDULE SESSION SESSIONPOINT
torb-kon Druck vom 24. 01.2001 17:00.
Configuration language s_statement : statement | foreign_app_number | dynamic_connect ; org_statement : start_value | repository | operating_system ; start_value : START_VALUE SBOPEN NUMBER SBCLOSE ; repository : REPOSITORY SBOPEN LETTER SBCLOSE ; foreign_app_number : foreig_app_number_header BBOPEN address_list BBCLOSE ; foreign_app_number_header : FOREIGN_APPLICATION_NUMBER SBOPEN NUMBER SBCLOSE ; address_list : address_elm | address_list address_elm ; address_elm : ADDRESS SBOPEN NUMBER COMMA
torb-kon Druck vom 24. 01.2001 17:00.
Configuration language check_rest : cancel | /* empty */ ; cycle : CYCLE SBOPEN NUMBER COMMA NUMBER COMMA NUMBER COMMA NUMBER SBCLOSE ; check : CHECK SBOPEN NUMBER COMMA NUMBER COMMA NUMBER COMMA NUMBER SBCLOSE ; cancel : CANCEL NUMBER NUMBER NUMBER NUMBER ; net_access : NET_ACCESS SBOPEN LETTER COMMA LETTER SBCLOSE | NET_ACCESS SBOPEN LETTER SBCLOSE | NET_ACCESS SBOPEN NUMBER SBCLOSE ; area : AREA SBOPEN LETTER area_parameter_list_opt SBCLOSE ; SBOPEN COMMA COMMA COMMA SBCLOSE area_parameter_
torb-kon Druck vom 24. 01.2001 17:00.
Configuration language prio_rest : SBCLOSE | COMMA PGWT SBCLOSE ; asyn_priority : ASYN_PRIORITY SBOPEN r_a_e SBCLOSE BBOPEN aprio_list BBCLOSE ; aprio_list : i aprio_element | aprio_list aprio_element ; aprio_element : PRIO SBOPEN NUMBER aprio_rest ; aprio_rest : SBCLOSE | COMMA tecp_list SBCLOSE ; tecp_list : tecp_element | tecp_list COMMA tecp_element ; tecp_element : | | | ; p_schedule : SCHEDULE BBOPEN p_schedule_list BBCLOSE ; TIMER EVENT CYCLIC PGWT p_schedule_list: p_schedule_elemen
torb-kon Druck vom 24. 01.2001 17:00.
Configuration language rereadtime : REREADTIME SBOPEN NUMBER SBCLOSE ; schedule : SCHEDULE BBOPEN schedule_list BBCLOSE ; schedule_list : schedule_element | schedule_list schedule_element ; schedule_element : CLASS SBOPEN NUMBER | CLASSMETHOD SBOPEN NUMBER SBCLOSE | INSTMETHOD SBOPEN NUMBER SBCLOSE | FUNCTION SBOPEN NUMBER ; COMMA prio SBCLOSE COMMA NUMBER COMMA prio COMMA NUMBER COMMA prio COMMA prio SBCLOSE prio : LOW | MEDIUM | HIGH ; ta_attrib : /* empty */ | BBOPEN ta_appl_statement_list_op
torb-kon Druck vom 24. 01.2001 17:00.
Configuration language foreign_appl_statement_list : foreign_appl_statement | foreign_appl_statement_list foreign_appl_statement ; foreign_appl_statement : authentication | bcamppl_statement ; 80 rm : RMXA SBOPEN LETTER COMMA LETTER SBCLOSE ; admin : ADMIN SBOPEN LETTER COMMA LETTER SBCLOSE ; max : MAX SBOPEN LETTER COMMA LETTER SBCLOSE | max_header max_list_opt SBCLOSE ; max_header : MAX SBOPEN LETTER EQUAL LETTER ; max_list_opt : /* empty *? | COMMA max_list ; max_list : max_element | max_li
torb-kon Druck vom 24. 01.2001 17:00.
Configuration language vector_rest : internet address_opt | address internet_opt ; internet : INTERNETADDRESS SBOPEN INADDRESS SBCLOSE ; ; internet_opt : /* empty */ | internet ; vector_opt : /* empty */ | vector ; host_statements : /* empty */ | operating_system host_statement_list_opt | host_statement_list ; host_statement_list_opt : /* empty */ | host_statement_list ; host_statement_list : host_statement | host_statement_list host_statement ; host_statement : statement | dynamic_connect_host ; d
torb-kon Druck vom 24. 01.2001 17:00.
Configuration language 84 non_ta_appl : nonta_appl_remote | nonta_appl_1 ; ta_appl_best : TA_APPLICATION SBOPEN LETTER COMMA NUMBER COMMA NUMBER COMMA LETTER COMMA BEST_BCAMAPPL SBCLOSE ; ta_appl_max : TA_APPLICATION SBOPEN LETTER COMMA NUMBER COMMA NUMBER COMMA LETTER SBCLOSE ; ta_appl_2 : TA_APPLICATION SBOPEN NUMBER COMMA NUMBER COMMA RESERVE SBCLOSE ; nonta_appl_1 : APPLICATION SBOPEN NUMBER COMMA NUMBER COMMA LETTER SBCLOSE | APPLICATION SBOPEN NUMBER COMMA NUMBER COMMA GINA V4.
torb-kon Druck vom 24. 01.2001 17:00.
Configuration language NUMBER NUMBER NUMBER LETTER COMMA COMMA COMMA /* foreign application number */ COMMA LETTER SBCLOSE ; vector : KEYVECTOR SBOPEN NUMBER COMMA NUMBER SBCLOSE ; address : PORTADDRESSES SBOPEN NUMBER COMMA NUMBER SBCLOSE ; multi_link_opt : multi_link | /* empty */ ; multi_link : link | multi_link link ; link : sessblock | connect ; connect : CONNECT SBOPEN NUMBER COMMA NUMBER COMMA NUMBER COMMA NUMBER SBCLOSE ; sessblock : session_header BBOPEN sesspoint sesspoint BBCLOSE |
torb-kon Druck vom 24. 01.2001 17:00.
Revision generation 6.3 Revision generation The purpose of the revision generation is as follows: when the configuration is revised, the generation for the applications not affected by the revision remain the same. Prerequisites The use of a repository is an absolute must for this revision generation (see the statement REPOSITORY on page 60). The repository must be created when generating the previous version or updated to the new status.
torb-kon Druck vom 24. 01.2001 17:00.35 Revision generation Performing the revision generation The user must perform the following steps when revising the configuration so that no user data is lost from an application: – Adapt the configuration file The modifications to the configuration, e.g. new hosts, new applications and connections must be defined in the input file of the configuration generator config.
Sample configuration file 6.4 Sample configuration file This section illustrates the syntactic structure using a sample configuration. SYSTEM { // // system-wide MAX statements. // MAX("TASKS","7") MAX("ASYNTASKS","4") MAX("PGPOOL","(200,80,96)") MAX("RECBUF","(32,4096)") MAX("TASKS-IN-PGWT","3") RMXA("INFORMIX","C") ADMIN("upicadm","valentin") ADMIN("admin","4711") START_RM("INFORMIX",APPLICATION) // // first operating system of the system. // in this example the hostname is // used as symbolic name.
torb-kon Druck vom 24. 01.2001 17:00.35 Sample configuration file // // available port addresses. // PORTADDRESSES(10111,10126) // // host wide MAX statements. // MAX("LSSBS","200") MAX("TASKS","6") // // first application of first operating system. // a1 is the utm known application name. // buslay is the user friendly name. // the third parameter is optional for BCAMAPPL // optimization.
Sample configuration file // // first session of the system between application a2 // of kotw002 // and a1 of kotw005. // a2 controls 3 connections // a1 controls 1 connection // SESSION("LU6.1") { SESSIONPOINT(1,1, 3) SESSIONPOINT(1,2, 1) } SESSION("LU6.1") { SESSIONPOINT(1,1, 1) SESSIONPOINT(1,3, 2) } SESSION("LU6.1") { SESSIONPOINT(1,2, 3) SESSIONPOINT(1,3, 2) } SESSION("LU6.
torb-kon Druck vom 24. 01.2001 17:00.35 Sample configuration file // // client2 of kotw005 is configured remote because // of remote server 1,1 // CONNECT(1,1, 1,6) CONNECT(1,6, 1,3) // // client3 of kotw005 is configured remote because // of REMOTE statement in the client3 definition // CONNECT(1,7, 1,3) } GINA V4.
Call and options 6.5 Call and options The configuration generator config is called as follows: config [-a] [-d] [-k nohinfo] [-m] [-r] [-u] [-v] [-V] configfile -a The all option contains the -d and -r options that are described below. If no option is set in the call, -a is assumed, i.e. all of the files are generated. -d If the development option is set, the configuration generator creates files required in the application development process (see below for a description of the individual files).
torb-kon Druck vom 24. 01.2001 17:00.36 Generated files 6.6 Generated files The configuration generator config analyzes a description file and generates from it resource files and configuration scripts for the runtime environment of the distributed system. Some of the generated files are host-specific and some are application-specific. config creates a directory tree in the current directory. The basic structure of this tree is illustrated in Figure 2 below.
Generated files The call options specified for the configuration generator result in different variants of the script being generated. These different variants generate different files: – If kdcdf was generated using the config -d development option, it generates source files for program parts which are needed to link the T-ORB application to the transaction monitor.
torb-kon Druck vom 24. 01.2001 17:00.36 Generated files 6.6.1 Generated files for UNIX hosts 6.6.1.1 Development option The development variant of the C shell script kdcdf generates the following C source files: – GinaRoot.c – OwnMsgs.c This files must be compiled using a C compiler and linked to the T-ORB application (see the GINA Developer Manual [13], chapter Compiling and linking). The name of the Resource Manager manufacturer from the RMXA statement is incorporated into the GinaRoot source.
Generated files 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 configured (statement DYNAMIC_CONNECT). This file contains information on the dynamic connections and is used by DomsDynConnectHandler (see Dynamic Connection Handler on page 197).
torb-kon Druck vom 24. 01.2001 17:00.36 Generated files 6.6.2 Generated files for WindowsNT hosts 6.6.2.1 Development option The development variant of the batch processing file kdcdf.bat generates the following C source files: – GinaRoot.c – OwnMsgs.c This files must be compiled using a C compiler and linked to the T-ORB application (see the GINA Developer Manual [13], chapter Compiling and linking).
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.
torb-kon Druck vom 24. 01.2001 17:00.37 Generated files 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.
Generated files Start and administration scripts The runtime variant of the procedure KDCDF (created using config -r) creates an ENTER file with the name START.TP_application_name when called. This file is used to start a T-ORB application. It must be copied as a DMS file to the host on which the application is to run. 6.6.4 Example The file structure illustrated in Figure 3 is an example of the structure created for the sample configuration file on page 90.
torb-kon Druck vom 24. 01.2001 17:00.38 Creating a configuration file using WinConfig 6.7 Creating a configuration file using WinConfig The configuration file described in the preceding sections contains all the necessary information on the desired system structure and can be created either with an editor or using the WinConfig graphical user interface. The WinConfig graphical user interface is only available on UNIX platforms and only for openUTM.
Creating a configuration file using WinConfig The configuration file created using WinConfig is the input for the GINA configuration generator config. The configuration generator creates the files required for configuring the entire system based on the information provided in the configuration file (see section 6.5 on page 94). This chapter explains the steps for working with the WinConfig graphical user interface. The description requires knowledge of the configuration language specified in section 6.
torb-kon Druck vom 24. 01.2001 17:00.38 Creating a configuration file using WinConfig 6.7.
Creating a configuration file using WinConfig Host edit window For information on editing the hosts in a configuration (physical view), see section 6.7.2.1 on page 110. Application edit window For information on editing the applications (TA applications, non-TA applications and foreign applications), as well as their sessions, connections, and foreign sessions (logical view), see section 6.7.2.2 on page 112.
torb-kon Druck vom 24. 01.2001 17:00.39 Creating a configuration file using WinConfig There are a total of six connections, two sessions, and a foreign session in this configuration example: Connections The non-transaction-monitored applications B.adm, K.adm and HB.adm are connected locally with the transaction-monitored applications B.big, K.big or HB.big respectively. The non-transaction-monitored application order is connected with each of the three transaction-monitored applications.
Creating a configuration file using WinConfig Figure 5 WinConfig: main window with open dialog boxes With few exceptions, all WinConfig dialog windows are based on the same model: the lefthand column in the window shows the parameter names, and the right-hand column shows the input fields with the relevant values. Parameter input is terminated by clicking with the left mouse button on OK, Delete or Cancel. The dialog window is closed. 108 GINA V4.
torb-kon Creating a configuration file using WinConfig Druck vom 24. 01.2001 17:00.40 Figure 6 shows the WinConfig main window with a graphical representation of the configuration file from section 6.4 on page 90. The individual application icons were positioned manually, see also the File>Open menu item on page 121. Figure 6 WinConfig: main window with the loaded configuration file from section 6.
Creating a configuration file using WinConfig 6.7.2.1 Host edit window Each host in a configuration is represented in the host edit window by a host icon. A label underneath the icon shows the name of the host. Each new host is generated using the pop-up menu of the right mouse button. However, newly generated hosts do not yet have a label underneath the icon showing the host’s name. WinConfig arranges all host icons one below the other in the host edit window.
torb-kon Druck vom 24. 01.2001 17:00.41 Creating a configuration file using WinConfig Parameter name Value Default Statement First Port First port number for the TNSX entries 10000 PORTADDRESSES Last Port 10000 Last port number for the TNSX entries This parameter value is calculated automatically by WinConfig. The calculation is explained in section 6.2 on page 46. WinConfig only uses the new value if it is larger than the old value.
Creating a configuration file using WinConfig 6.7.2.2 Application edit window a) Editing non-TA application parameters Each non-TA application in a configuration is represented in the application edit window by an icon. The name of the non-TA application is displayed within the icon. The position of an icon within the edit window can be changed by clicking once on the relevant icon using the middle mouse button. The icon tracks the movement of the mouse until you once again press the middle mouse button.
torb-kon Druck vom 24. 01.2001 17:00.
Creating a configuration file using WinConfig Each new TA application is generated using the pop-up menu of the right mouse button. The new TA application is represented by an icon that is positioned at the current mouse position within the application edit window. Newly generated TA applications do not yet have a name within the icon. The parameters can be edited by clicking on the TA application icon with the left mouse button.
torb-kon Druck vom 24. 01.2001 17:00.43 Creating a configuration file using WinConfig The simplest way of entering the host name is to perform a drag-and-drop operation on the host label: ◊ Click on the label of a host icon with the middle mouse button and drag the label into the Hostname input field by holding down the mouse key. The buttons in the dialog window execute the following actions: OK The entered parameter values are confirmed. Delete The corresponding TA application is deleted, i.e.
Creating a configuration file using WinConfig The following table describes the dialog window entries; the “Statement” column specifies the corresponding statement that is generated by WinConfig when saving to a configuration file.
torb-kon Druck vom 24. 01.2001 17:00.43 Creating a configuration file using WinConfig d) Editing sessions A session between two TA applications is represented graphically by a connecting line between the two icons. A session between two TA applications is generated by clicking once on the two relevant icons with the left mouse button. The session parameters can be edited by clicking on the connecting line with the left mouse button.
Creating a configuration file using WinConfig e) Editing connections A connection between a TA application and a non-TA application is represented graphically by a connecting line between the two icons. A connection between a TA application and a non-TA application is generated by clicking once on the two relevant icons with the left mouse button. A connection can be editing by clicking on the connecting line with the left mouse button.
torb-kon Creating a configuration file using WinConfig Druck vom 24. 01.2001 17:00.44 The following table describes the dialog window entries; the “Statement” column specifies the corresponding statement that is generated by WinConfig when saving to a configuration file. Parameter name Value Default Statement Protocol Name of the protocol used LU6.
Creating a configuration file using WinConfig The buttons in the dialog window execute the following actions: 6.7.2.3 OK The entered parameter values are confirmed. Delete The corresponding foreign session is deleted, i.e. the line between the two icons in the application edit window disappears. Cancel The entered parameter values are discarded again. WinConfig menu bar The menu bar contains the File, System, Hosts, TA-Apps, Non-TA-Apps, Links and Moves menus.
torb-kon Druck vom 24. 01.2001 17:00.46 Creating a configuration file using WinConfig File menu New All customizing settings are assigned defaults which means that parameter input for the hosts, non-TA applications, TA applications, foreign applications, sessions, connections and foreign sessions is sufficient to configure a system. The default values can be queried and changed via the System menu item in the individual customizing menus. Open... Loads a configuration file.
Creating a configuration file using WinConfig Config>Generate all Calls the GINA configuration generator config with the option -a. Config>Generate runtime Calls the GINA configuration generator config with the option -r. Config>Generate development Calls the GINA configuration generator config with the option -d. If the configuration includes BS2000 hosts, config (when calling the menu items Config>Generate all, Config>Generate runtime, Config>Generate development) is also called with the option -m.
torb-kon Druck vom 24. 01.2001 17:00.46 Creating a configuration file using WinConfig System menu This menu can be used to modify the customizing settings for the system. Init System... This menu entry permits the input of system-specific data for START_VALUE, REPOSITORY and OPERATING_SYSTEM statements.
Creating a configuration file using WinConfig Foreign-TA-App-Numbers... This menu item is used to input FOREIGN_APPLICATION_NUMBER statements. A FOREIGN_APPLICATION_NUMBER statement summarizes a list containing ADDRESS statements. This list is referenced by a number (see section 6.2 on page 46). The following list window is displayed when this menu item is called: Figure 15 Dialog window: Foreign-TA-App-Numbers The list window displays the current FOREIGN_APPLICATION_NUMBER settings.
torb-kon Druck vom 24. 01.2001 17:00.47 Creating a configuration file using WinConfig Input field 4: TransactionsType of the application Input field 5: optional, ConverterId of the application ◊ Click on Add Statement with the left mouse button. Terminate the input of FOREIGN_APPLICATION_NUMBER statements with OK or Cancel. The dialog window closes. The buttons execute the following actions: OK The entered FOREIGN_APPLICATION_NUMBER statements are confirmed.
Creating a configuration file using WinConfig MaxState... Customizes the MAX statements for the system. The following list window is displayed when this menu item is called: Figure 16 Dialog window: MAX system The list window always displays the current MAX settings for the system. Figure 15 shows the default settings. The statements displayed in the list window are transferred to a configuration file when they are saved.
torb-kon Druck vom 24. 01.2001 17:00.47 Creating a configuration file using WinConfig Admin... Customizes the ADMIN statement for the system. The following list window is displayed when this menu item is called: Figure 17 Dialog window: Admin system The list window always displays the current ADMIN settings for the system. Figure 17 shows the default setting. The statements displayed in the list window are transferred to a configuration file when they are saved.
Creating a configuration file using WinConfig Start... The Start menu item permits the customizing of the START and START_RM statements. A dialog window with five input fields is displayed when this menu item is activated: Figure 18 Dialog window: Start system The following table describes the dialog window entries; the “Statement” column specifies the corresponding statement that is generated by WinConfig when saving to a configuration file.
torb-kon Druck vom 24. 01.2001 17:00.48 Creating a configuration file using WinConfig Rmxa... Customizes the RMXA statements. A dialog window with two input fields is displayed when this menu item is activated: Figure 19 Dialog window: RMXA system The following table describes the dialog window entries; the “Statement” column specifies the corresponding statement that is generated by WinConfig when saving to a configuration file.
Creating a configuration file using WinConfig Timer... Customizes the statements for CYCLICTIME, CYCLICORDER, CYCLE, CHECK and CANCEL. The following dialog window is displayed when this menu item is called: Figure 20 Dialog window: Timer system The following table describes the dialog window entries; the “Statement” column specifies the corresponding statement that is generated by WinConfig when saving to a configuration file.
torb-kon Druck vom 24. 01.2001 17:00.49 Creating a configuration file using WinConfig Netaccess... Customizes the NETACCESS statement. The following dialog window is opened when this menu item is called: Figure 21 Dialog window: Netaccess system The following table describes the dialog window entries; the “Statement” column specifies the corresponding statement that is generated by WinConfig when saving to a configuration file.
Creating a configuration file using WinConfig Priority... The menu item is used to customize the PRIORITY statement in line with TAC class control. The following dialog window is displayed when this menu item is called: Figure 22 Dialog window: Priority-System The following table describes the dialog window entries; the “Statement” column specifies the corresponding statement that is generated by WinConfig when saving to a configuration file.
torb-kon Druck vom 24. 01.2001 17:00.49 Creating a configuration file using WinConfig The buttons in the dialog window execute the following actions: OK The entered parameter values are confirmed. If the three parameter values for High, Medium, Low are equal to 0, WinConfig does not generate a PRIORITY statement. WinConfig outputs an error message if there is at least one parameter value equal to 0 and at least one parameter value not equal to 0. Delete All parameter values are deleted.
Creating a configuration file using WinConfig Schedule... This menu item permits the input of entries for the SCHEDULE statement. The SCHEDULE statement is used to explicitly assign the specialist classes, class methods, instance methods and functions to the TAC classes with the priorities HIGH, MEDIUM and LOW (see section 6.2 on page 46).
torb-kon Druck vom 24. 01.2001 17:00.50 Creating a configuration file using WinConfig Input field 4 ◊ Allows you to enter one of the keywords LOW, MEDIUM or HIGH (to define the TAC class). Click on Add Statement with the left mouse button. The buttons execute the following actions: OK The entered entries for the SCHEDULE statement are confirmed. Cancel The modified entries for the SCHEDULE statement are discarded again. GINA V4.
Creating a configuration file using WinConfig Import... This menu item allows you to customize the IMPORT statement. The following list window is displayed when this menu item is called: Figure 24 Dialog window: IMPORT-System The list window always displays the current IMPORT statements for the system. There are no default settings. The statements displayed in the list window are transferred to a configuration file when they are saved.
torb-kon Druck vom 24. 01.2001 17:00.50 Creating a configuration file using WinConfig Area... This menu item allows you to customize the AREA statement. The following list window is displayed when this menu item is called: Figure 25 Dialog window: AREA-System The list window always displays the current AREA statements for the system. There are no default settings. The statements displayed in the list window are transferred to a configuration file when they are saved.
Creating a configuration file using WinConfig The following table describes the dialog window entries; the “Statement” column specifies the corresponding statement that is generated by WinConfig when saving to a configuration file. Parameter name Value Default Statement Access Mode of access to the additional data area. Possible values: DIRECT INDIRECT Selected via a pull-down menu. (This parameter only exists for OS_UNIX or OS_WINNT.
torb-kon Druck vom 24. 01.2001 17:00.51 Creating a configuration file using WinConfig The buttons in the list window execute the following actions: OK The entered AREA statements are confirmed. Cancel The modified AREA statements are discarded again. Mpool... This menu item allows you to customize the Mpool statement. This statement is only of relevance for BS2000 hosts.
Creating a configuration file using WinConfig Figure 28 Dialog window: MPOOL-Param The following table describes the dialog window entries; the “Statement” column specifies the corresponding statement that is generated by WinConfig when saving to a configuration file. Parameter name Value Default Statement Access Defines the access authorization. Possible values: DIRECT INDIRECT Selected via a pull-down menu. - MPOOL Lib Identifies the object module library when switching programs using KDCLOAD.
torb-kon Druck vom 24. 01.2001 17:00.52 Creating a configuration file using WinConfig The buttons in the list window execute the following actions: OK The entered MPOOL statements are confirmed. Cancel The modified MPOOL statements are discarded again. Dyn_Connect This menu item supports the definition of connections which are to be used by nontransaction-monitored dynamic clients for communication with transaction-monitored T-ORB applications (see section 6.2 on page 46).
Creating a configuration file using WinConfig ● Inserting an entry ◊ Insert the entries for the DYNAMIC_CONNECT statement in the two input fields beneath the display area. The meaning of the two input fields is as follows: ◊ Input field 1 Application name of the TA_APPLICATION for which connections are to be generated. Input field 2 Number of connections. Click on Add Statement with the left mouse button.
torb-kon Druck vom 24. 01.2001 17:00.52 Creating a configuration file using WinConfig Dyn_Connect>not_inherit_for_hosts... This menu item allows you to input the hosts which are not to inherit the DYNAMIC_CONNECT statement from the system. The following list window is displayed when this menu item is called: Figure 30 Dialog window: Hosts (not inherit DYNAMIC_CONNECT) The list window always displays all hosts which are not to inherit the DYNAMIC_CONNECT statement from the system, i.e.
Creating a configuration file using WinConfig Hosts menu This menu allows you to modify the customizing settings for the hosts. MaxState... This menu item allows you to customize MAX statements for all hosts whose icons are open. The MAX statements are input in the same way as for the menu item System>MaxState.... There are no default values. Admin... This menu item allows you to customize ADMIN statements for all hosts whose icons are open.
torb-kon Druck vom 24. 01.2001 17:00.53 Creating a configuration file using WinConfig Priority... This menu item allows you to customize the PRIORITY statement for all hosts whose icons are open. The statements are input in the same way as for the menu item System>Priority.... Default values are the same as for System. Schedule... This menu item allows you to customize the SCHEDULE statement for all hosts whose icons are open. The entries are input in the same way as for the menu item System>Schedule....
Creating a configuration file using WinConfig TA-Apps menu This menu allows you to modify the customizing settings for the TA applications. MaxState... This menu item allows you to customize MAX statements for all TA applications whose icons are open. The MAX statements are input in the same way as for the menu item System>MaxState.... There are no default values. Admin... This menu item allows you to customize ADMIN statements for all TA applications whose icons are open.
torb-kon Druck vom 24. 01.2001 17:00.53 Creating a configuration file using WinConfig Priority... This menu item allows you to customize the PRIORITY statement for all TA applications whose icons are open. The statements are input in the same way as for the menu item System>Priority.... Default values are the same as for System. Schedule... This menu item allows you to customize the SCHEDULE statement for all TA applications whose icons are open.
Creating a configuration file using WinConfig Bcamappl... This menu item allows you to customize the BCAMAPPL statement. When this menu item is called, the following list window is displayed for each TA application whose icon is open: Figure 31 Dialog window: BCAMAPPL The list window displays the current BCAMAPPL parameters for a specific TA application. There are no default settings. The BCAMAPPL parameters displayed in the list window are transferred to a configuration file when they are saved.
torb-kon Druck vom 24. 01.2001 17:00.54 Creating a configuration file using WinConfig Non-TA-Apps menu This menu permits the input of a UserId and Password for non-TA applications. Admin... The optional input of a UserId and Password is enabled in the non-TA application window for all non-TA applications whose icons are open. Foreign-Apps menu This menu can be used to modify the customizing settings for the foreign applications. Bcamappl...
Creating a configuration file using WinConfig Multi Link This menu item contains the two submenus Create Some and Erase Some. These two submenus can be used to generate or delete groups of sessions, connections and foreign sessions in a targeted manner.
torb-kon Druck vom 24. 01.2001 17:00.55 Creating a configuration file using WinConfig The buttons in the dialog window execute the following actions: OK Generates all of the sessions/connections/foreign sessions between applications that were specified by the pattern entered. Delete Deletes the values entered by the user. Cancel Closes the dialog window.
Creating a configuration file using WinConfig Moves menu This menu allows the user to change the layout of the configuration file displayed in the WinConfig main window. Move Param Among other things, the Moves menu permits a group of applications to be shifted using the Right, Left, Up, Down menu items and the cursor keys. The Move Param... menu item is used to define which applications belong to a group.
torb-kon Druck vom 24. 01.2001 17:00.55 Creating a configuration file using WinConfig 6.7.3 Mouse key assignments and mouse actions This section summarizes once again all of the mouse actions used by WinConfig and their effect. The most important mouse actions have already been explained in the preceding sections.
Creating a configuration file using WinConfig 154 Physical mouse key Position of the mouse cursor Mouse action Effect Right mouse button Pop-up menu for generating a new host, a new TA, non-TA or foreign application or for autoscrolling Drag to the menu item New Host, New TAApp, New NonTA-App, New Foreign-App or Autoscroll Depending on the menu selected, a new host, TA, non-TA or foreign application will be generated or autoscrolling activated GINA V4.
torbkontux Druck vom 24. 01.2001 17:00.56 7 Configuring T-ORB for BEA TUXEDO This chapter describes how to configure communication between GINA applications. The configuration does not require any modifications to the source program. However, it cannot take place while the application is running; rather it must be performed before the application starts. The configuration of T-ORB is based on the configuration of BEA TUXEDO. Knowledge of the respective manuals will therefore aid comprehension.
Overview Figure 35 is a symbolic representation of the hierarchies in the definition of the system. It is not drawn to scale to reflect the scope of the individual sub-descriptions. System-wide settings Parameters valid throughout the system Participating host: H1, H2, etc. Host-specific parameters R1 R2 etc. Applications in R1, R2 etc. Application-specific parameters A1 Figure 35 A2 etc.
torbkontux Druck vom 24. 01.2001 17:00.57 Overview – for the MASTER host a configuration file ubbconfig for the BEA TUXEDO transaction monitor and the shell scripts crbincf and crtlogs. – for each host a shell script crdevqu for setting up the “Queue Device”, “Queue Space” and “Queues” and for generating the database transaction manager. The configuration can be performed on a central computer for the entire system.
Configuration language 7.2 Configuration language The configuration generator config-tux reads a text file which describes the configuration of the entire system in a T-ORB-specific language. This file contains the necessary information on the transaction monitor, the T-ORB, and the specialist application. The elements of the language include keywords, literals, separators and comments. Blanks, tabs, line feeds, form feeds and white spaces are ignored.
torbkontux Druck vom 24. 01.2001 17:00.57 Configuration language Example CM_APPLICATION ( "CM1",-330, 1, "CM1" ) { ... } CM_PREFIX The CM_PREFIX statement defines a unique character string for each host which is used as a prefix when generating the parts resulting from conversational mode applications. The CM_PREFIX statement is mandatory if conversational mode applications are to be assigned to the host. The string may not exceed 5 characters and must start with a letter.
Configuration language Example HOST ( "Host2" ) { INTERNETADDRESS ( 127.0.0.2 ) KEYVECTOR ( 5005, 5040 ) PORTADDRESSES ( 2000, 2100 ) ... } INTERNETADDRESS The INTERNETADRESS statement is used to specify the current Internet address of the host. or the relative domain name of the domain name system.
torbkontux Druck vom 24. 01.2001 17:00.57 Configuration language The statement names APPDIR (78), ENVDIR, GINACONFIGDIR, TLOGDEVICE (64), TUXCONFIG (64), TUXDIR (78) and QUEUEFILE (78) must be defined indirectly or directly for all server machines. The numbers in brackets indicate the maximum number of characters permitted in the parameter value. The statement names ENVFILE, LDBAL, LMID, MASTER, MODEL, OPTIONS and TYPE may not be specified as these statements are generated automatically.
Configuration language OPENINFO The optional statement OPENINFO defines the Resource Manager. The parameters contain the following information: – – – the name of the database manufacturer the keyword APPLICATION or a string The current application name is used if APPLICATION is specified. the optional parameter TMS_NAME The default values is "TMS_INFX72". The OPENINFO statement at system level applies to all hosts unless the HOST statement contains an OPENINFO statement.
torbkontux Druck vom 24. 01.2001 17:00.58 Configuration language The repository supports generation for a modified configuration. If an application is removed, the same identifiers are used in the ubbconfig file for the remaining applications. The REPOSITORY statement is optional. If this statement is not specified, no memory is used in the generation.
Configuration language Example TA_APPLICATION ( "OS1", 1, 1, "OS1" ) { ... } USE_CM_APPLICATIONS The optional statement USE_CM_APPLICATIONS on the current machine (HOST) copies the conversational mode applications from the system level on this machine. Example 164 USE_CM_APPLICATIONS ( 50, 55 ) GINA V4.
torbkontux Druck vom 24. 01.2001 17:00.58 Configuration language 7.2.2 Lexical structure This section describes how the configuration generator combines the contents of the configuration file into symbols (like the keywords) for syntax analysis. The description is in the notation used by the UNIX command lex. %{ %} letter DGS letter_or_digit [a-zA-Z_] [0-9]+ [a-zA-Z_0-9] %% [ \t\n\v\r\f]+ \/\/.
Configuration language 7.2.3 Syntax This section describes the syntax of the configuration language in the notation used by the UNIX command yacc.
torbkontux Druck vom 24. 01.2001 17:00.
Configuration language s_statement : statement | conv_mode_appls ; org_statement : start_value | repository | operating_system ; start_value : START_VALUE SBOPEN NUMBER SBCLOSE ; repository : REPOSITORY SBOPEN LETTER SBCLOSE ; operating_system : OPERATING_SYSTEM SBOPEN LETTER SBCLOSE ; statement : max | openinfo ; conv_mode_appls: conv_mode_appl_header conv_mode_appls_body ; conv_mode_appls_header : CM_APPLICATIONS SBOPEN NUMBER SBCLOSE ; conv_mode_appls_body : BBOPEN cm_appl_list BBCLOSE ; 168
torbkontux Druck vom 24. 01.2001 17:00.
Configuration language 170 openinfo : OPENINFO SBOPEN LETTER COMMA LETTER SBCLOSE | OPENINFO SBOPEN LETTER COMMA APPLICATION SBCLOSE | OPENINFO SBOPEN LETTER COMMA LETTER COMMA LETTER SBCLOSE | OPENINFO SBOPEN LETTER COMMA APPLICATION COMMA LETTER SBCLOSE ; max : max_header max_list_opt SBCLOSE ; max_header : MAX_STMT SBOPEN LETTER EQUAL LETTER ; max_list_opt : /* empty */ | COMMA max_list ; max_list : max_element | max_list COMMA max_element ; max_element : LETTER EQUAL LETTER ; multi_host :
torbkontux Druck vom 24. 01.2001 17:00.
Configuration language host_statements_opt : /* empty */ | operating_system host_statement_list_opt | host_statement_list ; host_statement_list_opt : /* empty */ | host_statement_list ; host_statement_list : host_statement | host_statement_list host_statement ; host_statement : statement | cm_prefix | use_cm_applications ; cm_prefix : CM_PREFIX SBOPEN LETTER SBCLOSE : use_cm_applications : USE_CM_APPLICATIONS SBOPEN number_list SBCLOSE ; number_list : NUMBER | number_list COMMA NUMBER ; multi_applica
torbkontux Druck vom 24. 01.2001 17:00.59 Configuration language applicat : ta_appl ta_attrib | non_ta_appl | cm_appl cm_attrib ; /* server */ /* client */ /* conv.
Revision generation 7.3 Revision generation The purpose of the revision generation is as follows: when the configuration is revised, the generation for the applications not affected by the revision remain the same. Prerequisites The use of a repository is an absolute must for this revision generation (see the statement REPOSITORY on page 162). The repository must be created when generating the previous version or updated to the new status.
torbkontux Druck vom 24. 01.2001 17:01.00 Sample configuration file 7.4 Sample configuration file This section illustrates the syntactic structure using a sample configuration. SYSTEM { // // system-wide MAX statements.
Sample configuration file // // first application of first operating system. // a1 is the utm known application name. // buslay is the user friendly name. // TA_APPLICATION("a1",1,1,"buslay") { } TA_APPLICATION("a2",1,2,"servlay") } HOST("kotw005") { INTERNETADDRESS(192.200.94.4) KEYVECTOR(5000,5015) PORTADDRESSES(10114,10135) TA_APPLICATION("a1",1,3,"nwlay") TA_APPLICATION("a2",1,4,"nellay") APPLICATION(1,5,"client1") APPLICATION(1,6,"client2") APPLICATION(1,7,"client3") } } 176 GINA V4.
torbkontux Druck vom 24. 01.2001 17:01.00 Call and options 7.5 Call and options The configuration generator config-tux is called as follows: config-tux [-s] [-u] [-v] [-V] configfile -s The -s option outputs the addressing and name server data in a compact format. -u The -u option outputs the call syntax. -v With the verbose option, generator messages are output to stdout. -V If -V is specified, only the version message is output to stdout and execution of the program is terminated.
Generated files 7.6 Generated files The configuration generator config-tux analyzes a description file and generates from it resource files and configuration scripts for the runtime environment of the distributed system. Some of the generated files are host-specific and some are application-specific. config-tux creates a directory tree in the current directory. The basic structure of this tree is illustrated in Figure 36. There is a subdirectory for each host under the root system.
torbkontux Druck vom 24. 01.2001 17:01.00 Generated files – The BEA TUXEDO daemon process tlisten must be started on all server hosts. – The scripts must be executed in the order crbincf (MASTER), crdevqu (MASTER and then on all server hosts) and crtlogs (MASTER). Make sure that each one executes correctly. 7.6.1 Generated files for UNIX hosts readme The readme file is generated in the system directory.
Generated files ubbconfig The ubbconfig configuration file is generated in the directory assigned to the MASTER host. It contains configuration data for the BEA TUXEDO transaction monitor. crbincf.sh The script crbincf.sh calls the BEA TUXEDO utility routine tmloadcf and should only be executed on the MASTER host. crdevqu.sh The script crdevqu.sh is called with one parameter. The values which the parameter can assume are -y or -d or -q or -t, where -y contains the values -d, -q and -t.
torbkontux Druck vom 24. 01.2001 17:01.01 Generated files 7.6.2 Generated files for WindowsNT hosts readme The readme file is generated in the system directory. This file contains a list of the server host names with the related port numbers of the BEA TUXEDO system processes tlisten and WSL. gina.config ● Generation without the -s option A file gina.config is generated for each T-ORB application (TA_APPLICATION) and T-ORB/client application (APPLICATION).
Generated files crbincf.cmd The script crbincf.cmd calls the BEA TUXEDO utility routine tmloadcf and should only be executed on the MASTER host. crdevqu.cmd The script crdevqu.cmd calls the BEA TUXEDO utility routines tmadmin (function crdl), qmadmin (functions crdl, qspacecreate and qcreate) and buildtms. The script must be executed on all server hosts, first on the MASTER host, then on the other server hosts. The files needed for queues and transaction logs are generated during execution of the scripts.
torbkontux Druck vom 24. 01.2001 17:01.01 Generated files Directory crtlogs kotw002 ubbconfig buslay buslay.evf Figure 37 crbincf crdevqu kotw005 crdevqu servlay nwlay servlay.evf gina.config readme system Text file nwlay.evf gina.config client1 nellay client2 client3 nellay.evf gina.config gina.config gina.config File structure for the example of generation without the -s option Directory readme system Text file gina.config crdevqu crtlogs kotw002 kotw005 gina.
BEA TUXEDO domains 7.7 BEA TUXEDO domains A BEA TUXEDO domain refers to an administrative unit, a BEA TUXEDO application, which is independent of other BEA TUXEDO applications. These independent domains can, however, communicate with each other using gateways, i. e. services which offer and export a domain can be imported into another domain and then called.
torbkontux Druck vom 24. 01.2001 17:01.01 BEA TUXEDO domains 7.7.1 Statements DOMAIN The DOMAIN statement defines the name of the domain and describes its configuration. – domain name, max. 30 characters – domain-specific customizing statements (MAX, OPENINFO) – description of the host Example DOMAIN ( "Domain1" ) { START_VLAUE( MAX ... HOST ("Host1",MASTER) { ... } ... } EXPORT The keyword EXPORT attributes a TA_APPLICATION (...,EXPORT). This application will then be exported by the domain.
BEA TUXEDO domains 7.7.
torbkontux Druck vom 24. 01.2001 17:01.02 BEA TUXEDO domains after_domain_statement_list : after_domain_statement | after_domain_statement_list after_domain_statement ; after_domain_statement : statement | operating_system ; import : IMPORT SBOPEN import_list SBCLOSE ; import_list : import_element | import_list COMMA import_element ; import_element : | | | ; SBOPEN NUMBER COMMA NUMBER SBCLOSE HOST = LETTER UFN = LETTER LETTER /* user friendly name */ GINA V4.
BEA TUXEDO domains 7.7.
torbkontux Druck vom 24. 01.2001 17:01.
BEA TUXEDO domains 7.7.4 Generated files dmconfig The configuration file dmconfig is generated in the directory assigned to the MASTER host. This file contains configuration data for the BEA TUXEDO domain. The scripts crbincf.sh and crbincf.cmd call the BEA TUXEDO utility routine dmloadcf. Figure 39 illustrates the file structure for the sample configuration file on page 188. Directory File system readme dom_nt gina.config M19041pp gina.evf gina.config m61930pp gina.evf crbincf.cmd crtlogs.
torbkontux Druck vom 24. 01.2001 17:01.03 BEA TUXEDO domains 7.7.5 Special points CM_APPLICATIONS The CM_APPLICATIONS statement defines a list of conversational mode applications at domain level. MAX The MAX statement with the name BDMCONFIG (64) must be defined for the MASTER host. The BDMCONFIG environment variable is used by BEA TUXEDO to locate the file BDMCONFIG (binary).
BEA TUXEDO domains 192 GINA V4.
sys-adm Druck vom 24. 01.2001 17:01.03 8 Operating GINA applications This chapter provides an introduction to the runtime administration of configured GINA applications. 8.1 Communication administration 8.1.1 Communication structure of a server application Communication in GINA is based on the openUTM transaction monitor. Its functionality with respect to transaction-monitored message interchange and restart is thus inherited in the event of error.
DB administration 8.2 DB administration The database system INFORMIX Dynamic Server 2000 Version 9.2 is used for data storage within the Persistency Service. This results in a range of tasks for DB administration which can be completed with the aid of appropriate utilities. As already described, the transaction monitor and the database are synchronized by the XA protocol. It must be ensured that this link is supported in the current installation.
sys-adm Druck vom 24. 01.2001 17:01.04 DB administration Should a recovery procedure be required, manual interception to diagnose the error on the one hand and rectify it on the other (replace the faulty component) is generally necessary. Only then can the data recovery be performed from the backup archives using the appropriate programs (onarchive). This process can take a long time, during which the database can only be partially used or not at all.
Starting and stopping GINA applications 8.3 Starting and stopping GINA applications 8.3.1 Environment variables Please note that certain environment variables must be set so that GINA applications can run. These variables are explained in section 3.3.5 on page 21. 8.3.2 Transaction-monitored applications A GINA application which is based on the T-ORB service is made available by a start process.
sys-adm Druck vom 24. 01.2001 17:01.
Starting and stopping GINA applications Event Handler and Dynamic Connection Handler under WindowsNT The DomsEventHandler and the DomsDynConnectHandler are installed under WindowsNT as services which are automatically started when the system starts. The port number must be entered as described above in the file: C:\WINNT\system32\drivers\etc\Services Make sure that the lines end with an end of line character. Dynamic T-ORB/clients Dynamic clients need the files gina.
sys-adm Druck vom 24. 01.2001 17:01.04 Administering GINA applications 8.4 Administering GINA applications 8.4.1 TP monitor While an application is active, the administrator can decide to query information on the status and load or to interrupt the sequence. He/she uses the dtp script that is also created by the configuration generator to perform these activities.
Administering GINA applications 8.4.3 Monitoring alarms The delivery of an alarm to a non-transaction-monitored application is broken up into two parts. The partner is first informed of the event “Message n exists” via the auxiliary process EventHandler, and then the message is collected. The termination of the non-transaction-monitored partner or the EventHandler, for example as a result of a power failure, can result in alarms being lost during delivery.
sys-adm Druck vom 24. 01.2001 17:01.05 Administering GINA applications 8.4.4 Cyclical tasks The number of cyclical tasks that a transaction-monitored application can place at one time is limited. It is defined by the CYCLICORDER(n) parameter of the T-ORB generator config when the configuration is being created. For each transaction-monitored application, the T-ORB generator config generates the gina.config file, in which the number of cyclical tasks (cf. Figure 42) is stored.
Administering GINA applications 202 GINA V4.
fachwort Druck vom 24. 01.2001 17:01.05 Glossary action point A number of remote subcalls can be started in the T-ORB procedure “action point”. Given that the →server process is subsequently released, an action point is always a potential →end of transaction, a potential →monitoring and restart point. The results of all subcalls are evaluated by the Continuation of the action point. The continuation is a parallel callback which is only started when all the results have been received.
Glossary callback A procedure is called when an event occurs in an event-monitored environment (e.g. in an X application). This procedure is called a callback function, or simply only callback. class method A class method is a method which is used on the class, rather than on an object. In C++ we also talk about static methods. client In a client/server system, a client makes requests/calls to a →server. It requests a →service from the server. A client can also be the server of a client.
fachwort Druck vom 24. 01.2001 17:01.05 Glossary data link point A data link point is an →end of a transaction using commit. Transaction-monitored changes become visible and permanent outside the transaction at a data link point (see ACID property of →transactions). data reference A data reference DREF(P) is a special →global reference. It cannot be dereferenced. A data reference can however be used as an object, a data member, an argument or a result.
Glossary general reference A general reference GREF(P) is a →global reference. The →smart pointer GREF(P) can refer to a local →persistent object or a stub object. A method call is handled accordingly using either a local or a →remote call. global interface The global interface of a class is the subset of the methods of the class which can also be called →remotely. global reference A global reference is used in GINA to address an object, which is (possibly) remote.
fachwort Druck vom 24. 01.2001 17:01.05 Glossary job receiver see →server join We talk about a join when two or more database tables (i.e. persistent classes) are linked for a database query. lazy evaluation Lazy evaluation is when an expression can only ever be evaluated to the extent that is required, as dictated by its use. In connection with Persistency Service, the procedures used to access persistent objects follow a lazy evaluation strategy.
Glossary persistent A persistent object, unlike a →transient object, has a life span which does not depend on a process. In contrast to this, the life span of a transient object is limited by the life span of its process. polymorphy In object-oriented languages, a derived class inherits the interface of its base class(es). Polymorphy is when an object of the derived class can be used instead of an object of a base class. In C++ we use C++ references and C++ pointers here.
fachwort Druck vom 24. 01.2001 17:01.06 Glossary remote reference A remote reference RREF(P) is a special global reference. The →smart pointer always refers to a stub object. Given this, a method call using a remote reference is always handled using a →remote call. Remote references occur on the client side in strict client/server hierarchies. request Request is a synonym for call.
Glossary service A →server provides services. Services are generally provided in rpc-like interfaces in an API. Services are thus called. T-ORB provides an object-oriented API. Functions, class methods and instance methods can be called remotely (with transaction monitoring). →Stubs relieve the application of the task of dealing with communication details.
fachwort Druck vom 24. 01.2001 17:01.06 Glossary T-ORB The Transaction-monitored Object Request Broker allows local objects to send messages to remote objects with transaction monitoring. This means that not only the (persistent) states of the object, but also the messages undergo transaction monitoring. The sender does not have to worry about communication details.
Glossary two-phase commit refers to a transaction manager protocol, which ensures that all the changes in the resources are made atomically in a →distributed transaction operation, and that all the changes in all the resources are reversed if an error occurs in one resource. value-based access Access on a database using a search criterion. XA protocol The →transaction monitor and the →resource manager are connected over the standard X/Open XA interface.
abkuerzg Druck vom 24. 01.2001 17:01.06 Abbreviations ACID Atomicity, Consistency, Isolation, Durability ANS American National Standard ANSI American National Standards Institute API Application Programming Interface ASN.
Abbreviations 214 DB DataBase DBMS DataBase Management System DCE Distributed Computing Environment DCN Data Communication Network DER Distinguished Encoding Rules DOMS Distributed Object Management Service GINA General Interface for Network Applications GUI Graphical User Interface IC Information Conversion IDL Interface Definition Language IIOP Internet InterORB Protocol IRONMAN Integrated Regionalized Object-oriented Network MANagement System ISO International organization for
abkuerzg Druck vom 24. 01.2001 17:01.
Abbreviations 216 TNSX Transport Name Server SINIX T-ORB Transaction-monitored Object Request Broker TP Transaction Processing TTP Trail Termination Point UPIC Universal Programming Interface for Communication UTM Universal Transaction Monitor WAN Wide Area Network WS Work Station XA defines an Application Interface for Distributed Transaction Processing XDR eXternal Data Representation XMP X/Open Management Protocols Application Interface XOM X/Open OSI Abstract Data Manipulation
literat Druck vom 24. 01.2001 17:01.07 Related publications Contact your local Siemens Nixdorf office to order manuals whose order numbers begin with a U. Information relating to version and order numbers is only valid for the period in which this manual is published. Please ask for information on the latest editions. ❍❍● [1] BEA TUXEDO Reference Manual Release 6.3, BEA Systems Inc., April 1997 Part No. 801-001010-002 [2] BEA TUXEDO Administration Guide Release 6.3, BEA Systems Inc., April 1997 Part No.
Related publications 218 [7] CMX V5.1 Communications Manager in UNIX Operation and Administration Fujitsu Siemens Computers GmbH U6519-J-Z145-4-76 http://www.fujitsu-siemens.com/servers/man/man_de/utm_man/outm_50.htm [8] The Common Object Request Broker: Architecture and Specification Revision 2.2, February 1998 Object Management Group, Framingham, USA http://www.omg.org [9] CPI-C/LU6.2 (SINIX, BS2000, MS-DOS) Reference Manual Siemens Nixdorf Informationssysteme AG, November 1992, 446 p.
literat Druck vom 24. 01.2001 17:01.07 Related publications [15] IDL C++ Language Mapping Specification, September 1994, 135 p. OMG Document No. 94-9-14 [16] Informix Guide to SQL Syntax IDS.2000, V9.2, December 1999 Part No.: 000-6527 CD: Informix Answers Online, Product Documentation, Version 3.2 [17] INFORMIX-ESQL/C Programmer's Manual Client SDK 2.30, Version 9.21 April 1999 Part No.: 000-5424 CD: Informix Answers Online, Product Documentation, Version 3.
Related publications 220 [23] LU6.2-OSI-TP-GATE (SINIX) V1.0 Gateway between LU6.2 and OSI-TP Product Manual Siemens Nixdorf Informationssysteme AG, August 1993, 68 p. U21141-J-Z815-1-7600 [24] The Object Database Standard: ODMG-93, Release 1.1 Morgan Kaufmann Publishers, 1994 [25] openUTM V5.0 Concepts and Functions Fujitsu Siemens Computers GmbH U20683-J-Z135-3-76 http://www.fujitsu-siemens.com/servers/man/man_de/utm_man/outm_50.htm [26] openUTM V5.
literat Druck vom 24. 01.2001 17:01.08 Related publications [31] openUTM-Client V5.0 (UNIX, WindowsNT) for the UPIC Carrier System Fujitsu Siemens Computers GmbH U25770-J-Z135-2-76 http://www.fujitsu-siemens.com/servers/man/man_de/utm_man/outm_50 GINA V4.
Related publications 222 GINA V4.
verwsix.doc Druck vom 24. 01.2001 17:01.
DomsDynConnectHandler 197 DomsEventHandler 196 DPUTLIMIT1 56 DPUTLIMIT2 56 dtp 98, 199 dtp.
verwsix.doc Druck vom 24. 01.2001 17:01.09 min 6 miogen1 29 miogen2 29 MPOOL 56 N name 5 National Language Support 40 NB 56 NIS 197 NLS 40 noansi 5 nohinfo 5 O ODMG-OQL 5 OPENINFO 162 openUTM 10 openUTM client 10 operating system resources 43, 155, 184 OPERATING_SYSTEM 162 OQL 5 OwnMsgs.
tnsxcom 97 tnsxdel 97, 99 tnsxdel.tns 99 tnsxin 97 tnsxin.tns 99 T-ORB, generator 29 TP monitor 10 transfer of data 32 TRMSGLTH 56 TUXCONFIG 21 TUXDIR 21 type 7, 8 197 types of application 27 user default 41 public 41 user_friendly_name 179, 181 UTM 10 UTMPATH 21, 28 utmstart.multi 98, 196 utmstart.multi.bat 100 utmstart.single 98 utmstart.single.
kritik Druck vom 24. 01.2001 17:01.11 Siemens Business Services GmbH & Co OHG SBS MPM CPI 81730 Munich Germany Fax: (089) 636-48 303 Internet: gina.service@mch20.sbs.de Submitted by Comments on GINA V4.0 System Administrator Guide ✁ GINA V4.
kritik Druck vom 24. 01.2001 17:01.11 Siemens Business Services GmbH & Co OHG SBS MPM CPI 81730 Munich Germany Fax: (089) 636-48 303 Internet: gina.service@mch20.sbs.de Submitted by Comments on GINA V4.0 System Administrator Guide ✁ GINA V4.
Herausgegeben von / Published by Siemens Business Services GmbH & Co OHG D-81730 München Printed in Germany Bestell-Nr./ Order No. GINA V4.
