BS2000 systems
If the client program is running on a BS2000 system, BCMAP entries may be required, see also "Configuration using BCMAP entries (BS2000 systems)".
There are dependencies between the entries in the client program, in the upicfile and the UTM configuration. The following sections describe which parameters you must coordinate for partner configuration.
You can specifiy the information necessary for the transport system either using keywords directly in the upicfile or using function calls in the client program. If you do not use either of these options, the preset values will be used. The table below gives an overview of the preset values which can be modified in the side information file or in the program:
Property | Function | Keyword | Default value |
local application name | |||
T-SEL | Specify_Local_Tsel | T-SEL= | local application name |
T-TSEL format | Specify_Local_Tsel_Format | T-SEL-FORMAT= | T |
Port number | Specify_Local_Port | PORT= | 102 |
transport address | |||
T-SEL | Set_Partner_Tsel | T-SEL= | partner name |
T-TSEL format | Set_Partner_Tsel_Format | T-SEL-FORMAT= | T |
Port number | Set_Partner_Port | PORT= | 102 |
Internet address1 | Set_Partner_IP_Address | IP-ADDRESS= | Information from host |
Host name | Set_Partner_Host_Name | HOSTNAME= | Processor name |
Table 14: Properties of the address information
1The Internet address takes priority over the host name.
The following relationships exist between the entries in the client program or in the upicfile and the configuration of the UTM application.
Local application name
The local application name is specified in the calls Enable_UTM_UPIC and Disable_UTM_UPIC. A distinction is made between the following cases:
The local application name is entered in the
upicfile(identifier LN). The application name in this entry is transferred directly to the transport system.If the local application name is not entered in the
upicfile, it is transferred as the application name directly by UPIC to the transport system.
Partners on Unix, Linux or Windows systems or on BS2000 systems without a BCMAP entry
If the partner is a UTM application on a Unix, Linux or Windows system or a UTM application on a BS2000 system for which no BCMAP entries have been configured, the configuration must be coordinated as follows:
Both PTERM names must match. If there is no PTERM name configured for the client, there must be an LTERM pool via which the client can sign on.
Partners on BS2000 systems with a BCMAP entry
If the partner is a UTM application on BS2000 systems that uses BCMAP entries, the configurations must be harmonized as follows.
The T-selector of the local application must match the T-selector which is assigned to the client application in the server system.
Partner name
If the partner_LU_name ("Side information for standalone UTM applications") is specified in two parts (applicationname.processorname), UPIC transfers this name directly to the transport system.
Partners on Unix, Linux or Windows systems or on BS2000 systems without a BCMAP entry
If the partner is a UTM application on a Unix, Linux or a Windows system or a UTM application on a BS2000 system for which no BCMAP entries have been configured, the configurations must be harmonized as follows:
The applicationname which UPIC transfers to the transport system must match the BCAMAPPL name of the UTM application via which the connection to the client is made (in the diagram this is utmsampl). processorname must be entered in the TCP/IP name service as the name of the remote system.
Partners on BS2000 systems with a BCMAP entry
If the partner is a UTM application on a BS2000 system that uses BCMAP entries, the configurations must be harmonized as follows.
applicationname must match the T-selector of the BCMAP entry for the UTM application on the remote processor.