The OpenTP1 administrator must create OpenTP1 system definition information and then the superuser catalogs OpenTP1 into the OS by using the OpenTP1 dcsetup command.

If the OpenTP1 home directory specified in the dcsetup command does not contain the directories and files required for executing OpenTP1, the command creates the directories, copies the files, and adds the resource managers required for executing OpenTP1 when the command catalogs OpenTP1 into the OS. When you execute the dcsetup command for the directory for which the necessary environment has already been created, OpenTP1 is only cataloged into the OS.

If you do not use multiOpenTP1, specify /BeTRAN as the OpenTP1 home directory. If you do this, the dcsetup command does not need to copy the necessary files when you catalog OpenTP1 into the OS for the first time. The /BeTRAN owner and group are changed to the ID for root when you install the program. If you want to execute the dcsetup command after you install OpenTP1, change the /BeTRAN owner and group to the ID of the OpenTP1 administrator.

When you use multiOpenTP1, create a new directory for OpenTP1, change the directory owner and group to the ID for the OpenTP1 administrator, and specify it in an argument of dcsetup. When you use multiOpenTP1, specify a directory other than the root partition so that the root partition is not adversely affected.

Note the following when you catalog OpenTP1 into the OS:

• As the OpenTP1 home directory, do not specify a directory on a remote file system or a directory that is symbolically linked. If you do, operation is not guaranteed.
• When you specify the OpenTP1 home directory in the dcsetup command, specify a directory that is specifically created for OpenTP1 or /BeTRAN. If you do not do this, the environment will be damaged.
• When you execute the dcsetup command, the owner and group of the directories in the OpenTP1 home directory (aplib, bin, conf, etc, examples, include, lib, spool, tmp) and the files in those directories are changed along with the owner and group of the OpenTP1 home directory.
  The owner and group are changed when a new directory, other than examples, is created.
  

If you want to delete OpenTP1 from the OS, terminate OpenTP1. After this operation, the superuser must use the dcsetup command for OpenTP1 for the deletion.

When you delete OpenTP1 from the OS, you need to select whether to delete the environment in the OpenTP1 home directory. If you want to delete the environment in the OpenTP1 home directory, processing differs as follows depending on the location of the OpenTP1 home directory:

When the OpenTP1 home directory is /BeTRAN

• The spool and tmp directories are deleted.
• RM connection information is deleted.
• The message object file is deleted.

When the OpenTP1 home directory is not /BeTRAN

• The bin, etc, include, lib, spool, and tmp directories are deleted.
• RM connection information is deleted.
• The message object file is deleted.

If OpenTP1 has already been deleted from the OS when you execute the dcsetup command, the dcsetup command deletes the environment in the OpenTP1 home directory.

If you do not delete the environment in the OpenTP1 home directory, you can execute the dcsetup command whenever necessary to catalog OpenTP1 into the OS. If you want to change the environment under the OpenTP1 home directory, use the dcsetup command to delete OpenTP1 from the OS and then execute dcsetup again to catalog OpenTP1 into the OS.