This section describes the OpenTP1 client facility (TP1/Client) used by a client WS or PC for requesting services from a server system configured using OpenTP1.

For details about TP1/Client/W and TP1/Client/P, see the manual OpenTP1 TP1/Client User's Guide TP1/Client/W, TP1/Client/P. For details about TP1/Client/J, see the manual OpenTP1 TP1/Client User's Guide TP1/Client/J.

• TP1/Client communications
  TP1/Client can perform the following:
  
  • Remote procedure calls of TP1/Client
    A UAP of TP1/Client (CUP), a Java applet, a Java application, or a Java servlet can request a service from an SPP of OpenTP1. When you use TP1/Client/W or TP1/Client/P, you can start a transaction from a CUP and request a service from an SPP.
    
  • Message transmission using the TCP/IP protocol (supported by TP1/Client/W and TP1/Client/P)
    Messages can be sent and received between a CUP and an MHP of OpenTP1.
    
  • Communication with XDM/DCCM3
    TP1/Client can communicate with old systems such as XDM using the same method used for issuing remote procedure calls from a CUP, a Java applet, a Java application, or a Java servlet to OpenTP1.
    
• Preparing to request a service from TP1/Client to OpenTP1
  When TP1/Client requests a service of OpenTP1, the facility to determine whether or not to accept the request is known as the User Authentication facility.
  Whether or not the service request is accepted can be set by registering log-in names and passwords for TP1/Client or CUP in the /etc/passwd directory of OpenTP1.
  The use of the User Authentication facility varies depending on the products.
  
  • For TP1/Client/W and TP1/Client/P for Windows, call the start and end that indicate a function (dc_clt_cltin_s() and dc_clt_cltout_s() functions) while coding CUP.
  • For TP1/Client/P for MS-DOS, executes the TP1/Client commands (CLTIN and CLTOUT commands) and manages the start and end of the User Authentication facility.
  The above preparations are not required when you use TP1/Client/J.
  

Organization of this section

3.5.1 Remote procedure calls of TP1/Client

3.5.2 MCF message exchange using the TCP/IP protocol

3.5.3 Communication with XDM/DCCM3