ROBAR-SV communicates with ROBAR-CL via CMX (see “CMX Communication Manager” [12, 13]). You will find further details on the installation and configuration of CMX in the manual “CMX Communication Manager” [12] and in the hardware description of the ROBAR server.
Systems support must therefore set up the following:
the data for the connection to the remote partner
Local application name which is addressed by the remote partner
(the local name can also be generated automatically by ROBAR, see section "Add a new partner")
So that ROBAR can set up connections, requisite names must be entered in the Transport Name Service (TNS). A name for the local system and a name for the remote system must be entered for each connection. For the remote system, only the fifth name part is used.
The ROBAR-SV Manager offers user-friendly functions to configure and manage partner systems and local names, see section "Managing the partner configuration (CMX) of the ROBAR server".
Local and global name
A local and global name must be defined in the Transport Service directory (TS directory) for each remote system.
The global name is used as a keyword and allows remote applications to be accessed via a TCP/IP connection. It must be unique within the ROBAR server. The global name describes the TCP/IP connection and creates a link to the address and name or port of the remote application (depending on the connection type).
The local name is the name of the local application whose task it is to communicate with the remote application. Like the global name, the local name must also be unique within the ROBAR server.
Both a global (TNS partner name in the gen_hosts section) and a local name (local in the gen_hosts section) must be defined in the interface-specific ROBAR-SV configuration file for each remote system with which a communication link is to be established. The global names for the remote systems are freely selectable but must be specified in uppercase letters and comprise exactly 8 characters (e.g. ROB1WAN1).
Example
Determine the communication with the BS2000 systems (only the part affected by the communication is described):
# Global definitions gen_global_info ... archive_serial_number=1 ... end_global_info # Host definitions gen_hosts * definition of GLOBAL names (partner=) and LOCAL names (local=) * via RFC1006 (ISO protocol on TCP/IP network) EVARFC partner=RORFCEVA local=robrfc1 end_hosts ...
The global names defined in the TS directory describe the TCP/IP connection. Name and IP address of the ROBAR server must be known in the (remote) BS2000 system (BCAM component).
RORFCEVA\
TA RFC1006 193.210.194.170 PORT 102 T'ROBAR1DC'
robrfc1\
TSEL RFC1006 T'ROBRFC1'
You can output a TNS directory to a file using the following command: tnsxcom -D <file>. You can edit the <file> file (e.g. using vi), for instance to make a new BS2000 system known.
Enter the following command to update the TNS directory (root authorization required): tnsxcom -u <file>.