![[Contents]](FIGURE/CONTENT.GIF)
OpenTP1 Version 7 System Definition
![[Index]](FIGURE/INDEX.GIF)
![[Back]](FIGURE/FRONT.GIF)
![[Next]](FIGURE/AFTER.GIF)
This section explains UAP-related OpenTP1 system definitions. System definitions are necessary only when the basic facility of the OpenTP1 is the TP1/Server Base. The explanation that follows is true when the TP1/Server Base is in use.
The system definitions required for UAPs are outlined below.
This definition determines the execution environment common to the OpenTP1 system. For example, the maximum response wait time of RPC is specified.
This definition determines the UAPs that are concurrently started when the OpenTP1 system is activated.
This definition determines the execution environment for UAP started as an online job. It is created for each UAP.
This definition specifies the defaults for the user service definition items that are omitted.
This definition determines the application name of UAP when the message exchange mode is used. The application name is defined so that MCF can recognize the UAP defined in the user service definition.
Table A-1 summarizes the OpenTP1 system definitions related to UAPs.
Table A-1 OpenTP1 system definitions related to UAPs
| Classification | System definition | ||||
|---|---|---|---|---|---|
| System common definition | User service configuration definition | User service definition | User service default definition | MCF application definition | |
| Unit for definition | Node | Service group | Node | One or more MCF communication processes | |
| Time of use | When SUP, SPP, or MHP is activated | When the system is normally activated | When SUP, SPP, or MHP is activated | When MHP is started | |
| Method for definition change (for set format#) | Change the definition, terminate OpenTP1 for the node of the old definition, then start OpenTP1 for the node with the new definition. | Change the definition, terminate the process of the old definition, then restart the UAP with the new definition. | |||
The files of OpenTP1 system definitions are created under $DCCONFPATH. Table A-2 lists the file names of OpenTP1 system definitions related to UAPs.
Table A-2 File names of OpenTP1 system definitions related to UAPs
| System definition related to UAPs | Definition file name (complete path name) |
|---|---|
| System common definition | $DCCONFPATH/betranrc |
| User service configuration definition | $DCCONFPATH/usrconf |
| User service definition | $DCCONFPATH/user server name specified in the user service configuration definition, or user server name specified by the server start command (dcsvstart) |
| User service default definition | $DCCONFPATH/usrrc |
| MCF application definition | $DCCONFPATH/optional name that is unique in the node |
The service of MHP is scheduled based on the application name (first eight characters of the first segment of the message received with MCF). In the system definitions, the service group name and service name of MHP specified in the user service definition need to be specified in the MCF application definition, so that the two definitions are correlated with each other. For the service group name and service name of application attribute definition in the MCF application definition, specify the names defined in the user service definition.
All Rights Reserved. Copyright (C) 2006, 2010, Hitachi, Ltd.