OpenTP1 UAPs are available in the following types:

• UAPs used for communication in client/server mode
  
  • Service using program (SUP)
    This UAP is dedicated to a client. The SUP requires the basic OpenTP1 facility (TP1/Server Base or TP1/LiNK).
    
  • Service providing program (SPP)
    This UAP (server UAP) offers service upon request from a client UAP. The SPP requires the basic OpenTP1 facility (TP1/Server Base or TP1/LiNK).
    
• UAPs used for communication in message exchange mode
  
  • Message handling program (MHP)
    This UAP receives and processes messages sent through communication lines. An MHP process can request an SPP for service. The MHP requires the basic OpenTP1 facility and message exchange facility (TP1/Message Control).
    
• UAPs which initialize user files
  
  • UAP that handles offline work
    This UAP performs user-specified arbitrary processing. UAPs that handle offline work can use only OpenTP1 library functions for initially creating DAM files and accessing them in a batch environment.
    
• UAPs used with the OpenTP1 client facility (TP1/Client)
  
  • Client user program (CUP)
    This UAP is dedicated to a client. Programs which request SPPs for service using TP1/Client library functions from WSs or PCs are called by the generic name of CUP. The CUP requires the OpenTP1 client facility (TP1/Client/W or TP1/Client/P).
    For the CUP, see the manual OpenTP1 TP1/Client User's Guide TP1/Client/W, TP1/Client/P.
    You can use TP1/Client for Java to create Java applets and Java applications that request services from SPPs.
    You can use TP1/Client/J to create Java applets, Java applications, and Java servlets. For further information, see the manual OpenTP1 TP1/Client User's Guide TP1/Client/J.
    

Figure 1-5 shows client/server mode UAPs (SUP, SPP) and Figure 1-6 shows a message exchange mode UAP (MHP).

Figure 1-5 Outline of UAP roles and positions (client/server mode)

Figure 1-6 Outline of UAP roles and positions (message exchange mode)

Organization of this section

1.2.1 Using services UAP (SUP)

1.2.2 Providing services UAP (SPP)

1.2.3 Message handling UAP (MHP)

1.2.4 UAP that handles offline work