The executable file of the created UAP is stored in the $DCDIR/aplib/ directory (where $DCDIR represents the OpenTP1 home directory).

The executable file of the UAP is registered with OpenTP1. An OpenTP1 UAP is called a user server because it offers services.

(a) UAP registration method

When registering a UAP with OpenTP1, set up the environment in which the UAP will run. The setting method is as follows:

• TP1/Server Base
  Set a UAP execution environment in the user service definition.
  
• TP1/LiNK
  Use the dcsysset -u command for UNIX or the Application Control icon for Windows.
  

(b) User server name

The UAP name (user server name) under OpenTP1 is as follows:

• TP1/Server Base
  File name of the user service definition
  
• TP1/LiNK
  When setting up a UAP execution environment, give any user server name associated with the executable file name.
  

Names given to programs created as UAPs are explained below.

• UAP executable file name
  This name is set in an option to the linkage command when the UAP object file is linked to the library.
  
• User server name
  This name is set when the UAP is registered with OpenTP1. It is specified as the argument to the dcsvstart command. It is 1 to 8 characters long.
  
• Service group name and service name
  These names are specified as arguments to functions which are used to request service through OpenTP1 remote procedure calls or communication via the XATMI interface. When the user server name is registered with OpenTP1, these names are also specified.
  Each UAP executable file is given a service group name.
  Each service function is given a service name which works as a function name.
  
• Application name
  After a message is received through TP1/Message Control, it is processed by the application identified by this name. MHP service functions are registered under application names given to them. The relationship between service names and application names is specified in the MCF application definition.