This subsection explains how to set up multiOpenTP1.

• Setting up
  Use the dcsetupml command to set up all multiOpenTP1 environments. To set up a multiOpenTP1, you specify an identifier in the command argument. This identifier is used for registry, service, and event viewer registrations. The identifier is expressed as 1 to 4 single-byte alphanumeric characters.
  For details about the dcsetupml command, see dcsetupml (sets up a multiOpenTP1 or cancels setup of a multiOpenTP1) in Chapter 7. Operation Commands.
  You can set up a maximum of three multiOpenTP1s. If you set up more than three multiOpenTP1s, operation is not guaranteed.
  
• Registering the service
  The identifier for a multiOpenTP1 specified in the dcsetupml command during setup is added to the end of the service name. For example, if the identifier is M001, the service name is registered as OpenTP1_M001. In this case, OpenTP1_M001 - OpenTP1 for Windows is displayed as the title at the OpenTP1 console.
  
• Message output to the Event Viewer
  When messages are output to the Event Viewer in a multiOpenTP1 environment, the identifier specified in the dcsetupml command during setup is added at the end to obtain the source name (in the same manner as with the service name). For example, if the identifier is M001, the source name is OpenTP1_M001. This source name identifies the OpenTP1 that issued the message.
  

To set up the multiOpenTP1 environment again:

1. Make file backups in all the multiOpenTP1 environments.
   You must back up the following files:
   
   • System service information definition file (%DCDIR%\lib\sysconf\mcfu*)
   • System service common information definition file (%DCDIR%\lib\sysconf\mcf)
   • Communication service executable program (%DCDIR%\lib\servers\mcfu*)
   • Files under the multiOpenTP1 environment setup folder that have been changed and added by the user
2. Use the dcsetupml -d command to delete all multiOpenTP1 environments.
3. Install the replacement programs.
4. Use the dcsetupml command to set up all multiOpenTP1 environments.
5. In all multiOpenTP1 environments that have been set up, copy the backup files that were created in step 1 to overwrite the existing files.
6. If different resource managers^# are to be linked to the installed environments, execute the trnlnkrm command for each environment.
   

   #

   Such resource managers as TP1/Message Control, TP1/FS/Direct Access, TP1/FS/Table Access, HiRDB, and Oracle.