DIGITAL

NAME

acms_create_tpsystem − Creates an ACMSxp TPsystem

SYNOPSIS

 
acms_create_tpsystem

DESCRIPTION

The acms_create_tpsystem script creates a TPsystem and subordinate entities. 

The script displays a series of queries requiring you to enter configuration information and allowing you to confirm your responses.  If you do not confirm your responses, the script redisplays each query, using your previous response as the default. For each query, you can keep your previous response, or enter a new response. 
 
You need to supply some or all of the following configuration information:
 
  TPsystem name
  Default namespace profile
  TPsystem work directory
  CDB name
  Transaction log volume type and size
  DCE server principal name for TPsystem
  Key file directory for TPsystem
  TPsystem user name
  Create SFS server (yes), name of server principal for SFS server
  Create SFS server (no), SFS server name, SFS logical volume name
 
After you confirm your responses, the script performs the following functions:

       •Creates a DCE namespace directory, if one does not exist. 

       •Creates a directory for TPsystem work files, if one does not exist. 

       •Creates a configuration database (CDB) for the TPsystem and populates the database with the appropriate entries. 

       •Creates a namespace profile entry for the TPsystem, if one does not exist. 

       •Creates ACMSxp system servers, an Encina Tran log system server, and logs. 

       •Establishes the environment for the SFS server by either creating an  SFS server for the TPsystem to use or using an existing SFS server. 

       •Records information in the ACMSxp TPsystem registry on the system to ensure that TPsystem names are unique on a system and to facilitate starting, stopping, and deleting TPsystem instances. 

Setting Up Operating System Accounts

Accounts on the ACMSxp system provide the resources for ACMSxp software to run. Create an operating system account under which the TPsystem is to run. By default, when you create a TPsystem, the user name that you specify for the TPsystem determines the operating system account under which the TP controller process and subordinate system and application servers run. 

The ACMSxp software uses the TPsystem user name as the default server user name for servers that run under that TPsystem. Thus, when you create a server under the TPsystem and do not specify a server user name, the ACMSxp software derives the server user name from the default server user name for that TPsystem. 

At run time, the ACMSxp software starts a TPsystem by starting the TP controller process under the TPsystem user name. The TP controller then starts each subordinate server under the user name designated for that server. By default, therefore, all servers and the TP controller run under the same operating system account. Run each TPsystem under its own, dedicated operating system account. 

You can run the TPsystem and subordinate servers under different operating system accounts. If you log in to the system as root when you create the TPsystem and specify the user name of the TPsystem as root, you can use other operating system accounts in one of the following ways:

       •Create an operating system account under which all the subordinate servers can run.  When you create the TPsystem, specify a default server user name for the TPsystem that differs from root, the TPsystem user name. It is not recommended practice to run application servers under root.  The system and application servers can then run under an operating system account that you specify rather than under root. 

       •Create the required number of operating system accounts under which the application servers can run and an operating system account under which the system servers can run. 

-When you create the TPsystem, specify as the default server user name for the TPsystem the user name of the account that you created for the system servers.  The system servers can then run under the operating system account that you specify rather than under root. 

-When you create the application servers under this TPsystem, specify the user name attribute of the application servers with the names of the operating system accounts that you created.  Under a TPsystem that has a user name of root, the system administration software lets specify a user name for the application server that differs from the default server user name of the parent TPsystem.  Thus, you can have each of your application servers run under a unique, dedicated account. (You cannot change the user name of system servers. All system servers must run under the default user name for the TPsystem.) 

Encina SFS Server Options

To create and run a TPsystem, an Encina SFS server is necessary to manage ACMSxp resources, for example, the configuration database, and to act as the ACMSxp transaction manager for STDL applications.  The following choices are available:

       •A TPsystem can use a dedicated SFS server that ACMSxp software creates when you create the TPsystem. 

       •A TPsystem can use an existing SFS server, sharing it with other users on the system.  Each TPsystem should use a dedicated SFS server to make the best use of processing resources and disk storage and reduce the effects of any potential failures. Have the ACMSxp software create the dedicated SFS server for each TPsystem and ensure that the SFS server is used only with that TPsystem.

The SFS server uses two logical volumes, one for the SFS server log and one for SFS server data.  If you have the TPsystem use a dedicated SFS server, by default, the ACMSxp software places the logical volumes on the file system.  You have the following options with the SFS logical volumes that the ACMSxp software creates. 

       •Specify the size of a disk file for a logical volume. 

       •Have a logical volume use a dedicated device instead of a disk file. 

Before you create a TPsystem, determine the need for the following related environment variables. 

       •ENCINA_FLT_MAX_THREADS

       •ENCINA_FLT_INITIAL_THREADS

       •ACMS_ENCINA_LOGVOL

       •ACMS_ENCINA_DISKLOG

       •ACMS_ENCINA_DATVOL

       •ACMS_ENCINA_DISKDATA

       •ACMS_ENCINA_NOARCH

ENCINA_FLT_MAX_THREADS - Fast Local Transport Maximum Threads

This specifies the maximum threads that the SFS server creates to support its Fast Local Transport (FLT) interface. The default value is 120 threads. FLT is used between the SFS server and any SFS clients that are on the same system.  The following ACMSxp servers act as SFS clients:

       •Request queue server (acms_queue_svr)

       •Record queue server (acms_recqu_svr)

       •STDL processing servers that use the EXTFH interface

To determine the maximum number of threads that a TPsystem requires, use the following variables:

queue_svrNumber of simultaneous requests that the ACMSxp request queue server must handle. 

recqu_svrNumber of simultaneous enqueue and dequeue operations that the ACMSxp record queue server must handle for all record queues in the TPsystem. 

extfh_p_svrsNumber of STDL processing servers that use EXTFH services. 

Use the following formula to determine the value to set for the ENCINA_FLT_MAX_THREADS environment variable. 

({queue_svr ~∗~ 2} ~+~ recqu_svr ~+~ extfh_p_svrs)

If flt_threads is greater than 120 (the default value), set the ENCINA_FLT_MAX_THREADS environment variable to that integer value.  For example:

setenv ENCINA_FLT_MAX_THREADS 200

Set the value before you run the acms_create_tpsystem script, or, if your SFS server is not currently running, before you execute the acms_start_tpsystem script. 

If flt_threads is less than 120, do not set the environment variable. 
 

ENCINA_FLT_INITIAL_THREADS - Fast Local Transport Initial Threads

The ENCINA_FLT_INITIAL_THREADS environment variable specifies the initial number of threads that the SFS server creates in the Fast Local Transport (FLT) request thread pool when the TPsystem starts.  The default value is 1 thread.  During processing on the TPsystem, the SFS server creates more threads as they are needed until it reaches the maximum number of threads specified by the ENCINA_FLT_MAX_THREADS environment variable. 

If the TPsystem typically has requests queued when it starts, consider setting the ENCINA_FLT_INITIAL_THREADS environment variable so that one thread per queued request is available initially.  For example:

setenv ENCINA_FLT_INITIAL_THREADS 100

The number of initial threads must be less than the number set by the ENCINA_FLT_MAX_THREADS environment variable. If the number of initial threads is set too low, the SFS server generates a communications error for each request that it cannot handle when the TPsystem starts. Set the ENCINA_FLT_INITIAL_THREADS environment variable before you execute the acms_create_tpsystem script or, if your SFS server is not currently running, before you execute the acms_start_tpsystem script. 
 

ACMS_ENCINA_LOGVOL - Size of SFS Log Volume

 
The ACMS_ENCINA_LOGVOL environment variable controls the original size of the logical volume file for the SFS server log. If the ACMSxp software creates the SFS server when you create the TPsystem, it also creates the SFS log and SFS data logical volumes. The file for the SFS log logical volume is used by the SFS server for storing transaction coordination information. If this and the ACMS_ENCINA_DISKLOG environment variable are not set, the script creates the logical volume in the same partition as the TPsystem work directory with a size of eight megabytes. By default, the SFS logical volume is created with a name in the following format.

/work-dir/tpsystem-simplename_sfslogvol

where:

work-dirThe location you specify for the TPsystem work directory when you run the script

tpsystem-simplenameThe simple name you give for the TPsystem

If the default size of eight megabytes is insufficient for a TPsystem, set this environment variable before you execute the acms_create_tpsystem script. For example:

setenv ACMS_ENCINA_LOGVOL 64

The command sets the value so that the file created in this process is 64 megabytes. ACMS_ENCINA_LOGVOL must be set to an integer value.

ACMS_ENCINA_DISKLOG - Disk for SFS Log Volume

If the ACMS_ENCINA_LOGVOL environment variable is not set, the ACMS_ENCINA_DISKLOG environment variable can specify a raw disk on which the SFS software creates and accesses the logical volume for the SFS server log.  If this environment variable is not set, the acms_create_tpsystem script uses the value of ACMS_ENCINA_LOGVOL to create the logical volume in the same partition as the TPsystem work directory.  If the TPsystem you are creating is going to run at a high transaction rate, consider using a dedicated raw disk to hold the SFS log logical volume. Ensure that the dedicated disk is not mounted on any file system and is not used for swap space and that the user account under which the TPsystem is to run has read and write access to the disk partition. To place the logical volume on the dedicated storage, set the environment variable to the character interface of the device. For example:

setenv ACMS_ENCINA_DISKLOG /dev/rrz2c

The command sets the environment variable so that the logical volume is created on partition c of the rz2 device. This improves performance within the TPsystem by reducing I/O contention between CDB and TPsystem logging activities and transaction logging activities.

ACMS_ENCINA_DATVOL - Size of SFS Data Volume

The ACMS_ENCINA_DATVOL environment variable controls the original size of the logical volume file for the SFS data.  If the ACMSxp script creates the SFS server when you create the TPsystem, it also creates the SFS log and data logical volumes.  The data volume must have sufficient storage to hold the following items. 

       •CDB

       •Request queue database

       •Each record queue data base

       •Application files defined in a STDL group file specification, and

       •Recoverable send database

If this and the ACMS_ENCINA_DISKDATA environment variables are not set, the script creates the logical volume in the same partition as the TPsystem work directory with a size of eight megabytes.  By default, the SFS logical volume is created with a name in the following format. 

/work-dir/tpsystem-simplename_sfsdatavol

where:

work-dirLocation you specify for the TPsystem work directory when you run the script. 

tpsystem-simplenameSimple name of the TPsystem you supply in creating the TPsystem. 

If the default value of eight megabytes is insufficient for a TPsystem, set the environment variable before you execute the acms_create_tpsystem script. For example:

setenv ACMS_ENCINA_DATVOL 64

The command sets the environment variable value so that the file created in this process is 64 megabytes. ACMS_ENCINA_DATVOL must be set to an integer value. 

ACMS_ENCINA_DISKDATA - Disk for SFS Data Volume

If the ACMS_ENCINA_DATVOL environment variable is not set, the ACMS_ENCINA_DISKDATA environment variable specifies a raw disk on which the SFS software creates and accesses the logical volume for the SFS server data.  If this environment variable is not set, the acms_create_tpsystem script uses the value of ACMS_ENCINA_DATVOL to create the logical volume in the same partition as the TPsystem work directory. 

If the TPsystem you are creating is going to run task queuing or record queuing, consider using a dedicated raw disk to hold the logical volume. Ensure that the dedicated disk is not mounted on any file system and is not used for swap space and that the user account under which the TPsystem is to run has read and write access to the disk partition. 

To place the logical volume on the dedicated storage, set the environment variable to the character interface of the device.  For example:

setenv ACMS_ENCINA_DISKDATA /dev/rrz4a

The command sets the environment variable so that the logical volume is created on partition a of the rz4 device. This improves performance within the TPsystem by reducing I/O contention between CDB, transaction logging, and application group file activities and task queuing and record queuing activities.

ACMS_ENCINA_NOARCH - No Media Archiving

The ACMS_ENCINA_NOARCH environment variable specifies that no media archiving be done on the SFS log logical volume within the TPsystem you are creating. The default is that the ACMSxp software enables media archiving and creates the following archive directory when you create the TPsystem. 

/work-dir/tpsystem-simplename_logarchdir

where:

work-dirLocation you select for the TPsystem work directory

tpsystem-simplenameSimple name of the TPsystem

By default, all logical volumes are archived. 

Because media archiving is needed only in a production environment, save archiving overhead during development by defining this environment variable. For example:

setenv ACMS_ENCINA_NOARCH ""

This command defines the environment variable to omit media archiving on the SFS log logical volume. The value is not checked. The SFS log archive directory is not created when you create the TPsystem.

To enable media archiving, use the following command:

tkadmin enable mediaarchiving

Steps to Follow

To create a TPsystem, perform the following steps:

     1.Log in to the system on which the TPsystem and application servers are to run.  You have the following choices. 

oIf the TPsystem that you are creating is going to run under root, log in to the operating system under root.  To create and start TPsystems that run under root, your process must be logged in to DCE as the machine principal.  When you log in to the operating system as root, your process automatically runs under the DCE machine principal.  The principal name is in the following format:

hosts/<machine-name>/self

oIf TPsystem that you are creating is not going to run under root, log in to the operating system using an appropriate account created for this purpose.  The account needs access to the TPsystem registry file and sufficient system resources and privileges.  The registry file acms_tpsystems.dat is stored in a version-specific product directory under /var/opt. 

     2.Obtain the required DCE authentication and permissions.  If you are logged into the system under root, do not log in to DCE under another principal. You are automatically running as the machine principal.  If you are not logged in to the system under root, perform a dce_login using a principal that has been given the necessary DCE permissions that a system manager requires.  (Logging in to DCE forks a no-login process and establishes your forked process as a DCE principal.)  Use the cell_admin account to obtain authenticated access to the DCE namespace. 

oEnsure that you have DCE permissions to create a namespace directory if one does not exist for the TPsystem. For examples of setting DCE permissions, refer to section on DCE procedures for the IVP in the ACMSxp for DIGITAL UNIX Installation Guide.  If a namespace directory for the TPsystem does not exist, the script attempts to create one. Creating a namespace directory requires the following permissions:

∗ir permissions (insert and read) on the parent directory

∗w permission (write) on the namespace clearinghouse

If you use an established namespace directory, these permissions are not necessary.  For example, if the default namespace directory that ACMSxp uses (/.:/acmsxp) is already set up, use that directory. 

oSet up the following required DCE security objects for the TPsystem:

∗Server principal and account

∗Key file directory

∗Key file for the TPsystem server principal

 

oYou need the following when you request the acms_create_tpsystem script to create a dedicated SFS server for each TPsystem:

∗A separate DCE server principal for each SFS server

∗A DCE account for each SFS server principal in the DCE registry

∗A file system directory to store the key files of the server principals under which the SFS servers are to run. 

∗Operating system accounts under which the SFS servers run must have read and write access to the key files of the SFS server principals

The software checks these requirements when you create the TPsystem.

 

     3.If you are using a dedicated disk partition to store a SFS logical volume, ensure that:

oThe dedicated device is not mounted on any file system. 

oThe partition is not used for swap space. 

oThe operating system account under which the TPsystem is to run has read and write access to the disk partition. 

     4.Ensure that the ACMSxp software environment is set up.  Run the acms_set_version script to define environment variables and point to the correct executables.  Check that Encina, DIGITAL DCE, and other dependent software are installed and configured correctly. See Section 18.4 of the Developing and Managing Applications for further details. 
 

Invoking the Script

 
Run the acms_create_tpsystem script found in the ACMSxp system directory to which the environment variable ACMS_SYS_DIR points.  For example:

csh> acms_create_tpsystem
ACMSxp V3.1 for DIGITAL UNIX
  .
  .
  .

Invoke the script directly. Do not use source or . to invoke it because the script might exit the shell.
 

Log Files Used

The script sets up the ACMS_LOG_FILE environment variable to write to the default TPsystem log file in the TPsystem work directory.  Any errors in verifying the DCE principal are written to this log file. 
 

Software Prompts and Responses

Some prompts have ACMSxp-supplied default responses displayed within square brackets ([ ]) or within left and right parentheses ().  Respond to the queries in one of the following ways:

       •If the prompt has an ACMSxp-supplied default response, press <Return> to accept the default.  If the prompt has no default, pressing <Return> displays help text. 

       •To respond to a prompt, enter the text and press <Return.> Use the format of the default response shown in the prompt as a guideline for your response.  and your answer overrides any ACMSxp-supplied default.  The software checks the validity of some responses and proceeds to the next prompt. 

       •Type a question mark (?) and press <Return> to display some explanatory help text and redisplay the prompt. 

       •If the software finds an invalid response, it prints a warning message and redisplays the prompt. Use operating system command recall and editing features to fix your invalid response and reenter it. 
 

Full Namespace Name of the TPsystem

 
The default response is the default ACMSxp namespace directory /.:/acmsxp and a simple name of tpsys1. To override the default, specify a full DCE namespace name in cell-relative (or local) format.  For example:

/.:/acmsxp/avertz_hq

This name specifies the TPsystem avertz_hq in the ACMSxp default namespace directory /.:/acmsxp.  The name must meet these conditions:

oThe full name must be unique in the cell. 

oThe simple name (in this example, avertz_hq) must be unique on the system and not exceed 16 characters.  If the namespace directory does not exist (either the ACMSxp default one or the one you specify), the software runs a DCEdce utility to create the directory. This requires that the principal under which the software runs must have DCE permission to create a namespace directory. If the namespace directory already exists, the principal must have DCE permissions to create entries in the namespace directory. It is good practice to use DCE groups to provide the requisite permissions.
 

Full Namespace Name of the Default TPsystem Profile

 
Specify the full namespace name of the profile to be used by this TPsystem. The default response is the namespace directory that you specified for the TPsystem and a default simple name in the following format:

tpsystem-simplename_profile

If the profile does not exist, the software creates it. TPsystems can share profiles. 
 

Path for TPsystem Work Directory

 
Specify an absolute path for the location to store TPsystem information, for example, the default log file. The default location is either the translation of the shell environment variable ACMS_WORK_DIR or, if ACMS_WORK_DIR is not defined, a subdirectory of ACMSxp root directory having the simple name of your TPsystem. If the directory does not exist, the software creates it. The software defines a shell environment variable ACMS_WORK_DIR that points to the TPsystem work directory. If you run the software again to create another TPsystem, the default path is the translation of the shell environment variable.
 

Simple Name for the Configuration Database (CDB)

 
Specify the simple name of the configuration database for this TPsystem. The format for the default CDB name is:

tpsystem-simplename_cdb

The CDB is created in the  SFS data volume. 
 

Transaction Log Volume Storage Method

 
ACMSxp software logs information about its transactions in a transaction log. The response can be:
 

FileLog is stored in the same file system partition as the TPsystem work directory with the following name.  tpsystem-simplename_txnlog

The software next asks for the size to create the ACMSxp transaction log file. 
 

Size for the Transaction Log File (in megabytes)

 
Specify the number of megabytes of storage for the ACMSxp transaction log. The default is 16 megabytes. Ensure that there is enough free space to hold the ACMSxp transaction information. 32 megabytes should be adequate for most applications unless transactions tend to be longlived.
 

Name of DCE Server Principal Under Which TPsystem Is to Run

 
Give the name of the DCE server principal that you create for the TPsystem. The software checks whether the principal is valid. If the principal is not valid, the software displays another prompt asking whether you want to reenter the principal name. If you press <Return> as the response, the script exits and you must create the server principal and its DCE account to proceed beyond this point.  If you run the TPsystem under root, the process runs under the machine principal. 
 

Path for TPsystem Key File Directory

 
Supply an absolute path for the directory that contains the key file for the TPsystem server principal. There is no default. The software ensures that the directory exists and that the key file resides in the directory with the same name as the TPsystem server principal. If an error occurs, the software displays a message reporting the problem and another prompt asking whether you want to reenter the specification. If you press <Return> as the response, the software exits. Fix the problem to proceed beyond this point. 
 

Name of Operating System User Account for the TPsystem

 
Give the name of the DIGITAL UNIX account (except the root account) under which the TPsystem is to run.  The default is the operating system account under which the acms_create_tpsystem script is running. If you choose the default, the software checks whether that account has proper access to the key file for the TPsystem server principal and warns you if it does not.  If the user name for the TPsystem is not root, this name becomes the default server username attribute of the TPsystem.  The software displays the prompt concerning creating the SFS server.  If the user name for the TPsystem is root, you must run as root.  The software asks for the default server username for this TPsystem.  For example:

Default server username [root]:

The prompt shows that ACMSxp default for the default server user name (the operating system user name under which servers in the TPsystem run) is root.  DIGITAL recommends that you not run application servers under root.  To change the default, specify the name of the DIGITAL UNIX account different from root under which all servers in the TPsystem run by default. This user name becomes the value for the TPsystem default server username attribute. 
 

SFS Server Usage

 
Specify one of these responses for the action indicated:

yCreate a dedicated SFS server for the TPsystem to use

nDo not create a SFS server but use an existing SFS server and existing SFS logical volumes for the SFS log and data

To create and run a TPsystem, an SFS server is necessary.  A TPsystem can use a dedicated SFS server that ACMSxp software creates when you create the TPsystem. Or the TPsystem can use an existing SFS server, sharing it with other users on the system. 

The script asks whether you want the ACMSxp software to create an SFS server.  DIGITAL recommends that each TPsystem use a dedicated SFS server to make the best use of processing resources and disk storage and reduce the effects of any potential failures. 

If you respond y, the software not only creates an SFS server for the TPsystem to use, but checks the following environment variables for configuration information that you specify. 
 
  ENCINA_FLT_MAX_THREADS
  ENCINA_FLT_INITIAL_THREADS
  ACMS_ENCINA_LOGVOL
  ACMS_ENCINA_DISKLOG
  ACMS_ENCINA_DATVOL
  ACMS_ENCINA_DISKDATA
  ACMS_ENCINA_NOARCH
 
The ACMSxp software also runs the server automatically, and configures the TPsystem so that the SFS server starts when the TPsystem starts.

If you respond n, the software asks for the full namespace name of an existing SFS server and a logical volume name.  For example:

Enter the SFS server name (include /.:/) []: /.:/acmsxp/encina/sfs/svr
Please enter the SFS Logical Volume Name [sfslvol]:

The server must be running on the system on which you are creating the TPsystem and must be responding to incoming RPC calls. 
 

Name of the DCE Server Principal Under Which SFS Server Runs

 
If you answer y to create an SFS server, the software asks for the SFS server principal. Specify the name of the DCE server principal that you create for this SFS server.  The format for the default server principal name is:

tpsystem-server-principal-name_sfs

Specify a different SFS server principal for each SFS server. The SFS server principal should not be shared by SFS servers.
 

Response Summary

 
After you respond to the last prompt, the software summarizes your responses and lets you confirm them. For example:

Is this ok (y|n) [n]?

If you are satisfied with your responses, confirm them by typing y and pressing <Return> to have the script create the TPsystem.  If you want to change any response, press the <Return> key. The software recycles through the prompts, redisplaying each prompt, using your previous response as the default and allowing you to change the response, as follows:

       •Pressing <Return> retains your response and advances to the next prompt. 

       •Typing in a new response and pressing <Return> changes the response and advances to the next prompt. 

       •Typing a question mark (?) and pressing <Return> displays some explanatory help text and redisplays the prompt.  After the software redisplays all the prompts, it again summarizes the responses you indicated and lets you again confirm them. The software recycles through the prompts and retains your responses until you confirm the responses.
 

Running a TPsystem from the root Account

 
If you plan to run a TPsystem under root, softlink ACMSxp and application message catalogs into DCE directories.  To do the softlink, log in as root and use the ln -s command. For example:

# ln -s /usr/opt/ACMSXPV301/msg/en_US.ISO8859-1/∗ \
_# /usr/lib/nls/msg/en_US.ISO8859-1
# ln -s /usr/opt/ACMSXPV301/msg/C \
_# /usr/lib/nls/msg

This restriction exists to ensure system security.
 

EXAMPLE

The following example shows invoking the script, answering the queries,  and confirming the responses.  First set the version.  From csh:

% source /user1/ACMSXPV031/bin/acms_set_version.csh
ACMSxp V3.1 for DIGITAL UNIX
Copyright (c) 1993, 1997 by Digital Equipment Corporation. All rights reserved.
Using ACMSxp in /user1/ACMSXPV031/bin
%

From sh, ksh:

$ . /user1/ACMSXPV031/bin/acms_set_version.sh
ACMSxp V3.1 for DIGITAL UNIX
Copyright (c) 1993, 1997 by Digital Equipment Corporation. All rights reserved.
Using ACMSxp in /user1/ACMSXPV031/bin
$

Then, start the script (same for all shells):

% acms_create_tpsystem
ACMSxp V3.1 for DIGITAL UNIX
Creating registry /var/opt/ACMSXP301/acms_tpsystems.dat
 TPsystem name [/.:/acmsxp/tpsys1]: /.:/acmsxp/avertz_hq
Default namespace profile [/.:/acmsxp/avertz_hq_profile]:
TPsystem work directory (absolute path) [/usr/users/acmsxp031/avertz_hq]:
Configuration database [avertz_hq_cdb]:
Use file or raw disk for txn log volume? [file|disk] (file):
Size of log file (in megabytes)? [16]: 32
TPsystem Principal Name []: avertz_hq_server
TPsystem key file directory (absolute path) []: /usr/users/avertz
TPsystem username []: avertz_hq_server
Create SFS Server ? [y|n] (n): y
SFS Principal Name [avertz_hq_server_sfs]: avertz_hq_sfssvr
 Creating TPsystem with:
 TPsystem name:                 /.:/acmsxp/avertz_hq
 default namespace profile:     /.:/acmsxp/avertz_hq_profile
 work directory:                /usr/users/acmsxp031/avertz_hq
 configuration database:        avertz_hq_cdb
 transaction log file:          /usr/users/acmsxp031/avertz_hq_txnlog
 transaction log file size:     32
 principal name:                avertz_hq_server
 TPsystem key file directory:   /usr/users/avertz
 username:                      avertz_hq_server
 default server username:       avertz_hq_server
 Create New SFS Server:         Yes
 SFS Principal Name:            avertz_hq_sfssvr
 SFS Server Name:               /.:/acmsxp/avertz_hq_sfssvr
 SFS Logical Volume Name:       avertz_hq_sfsdatavol
 Is this ok [y|n] (n)?

When you confirm the responses, the script does the work, displaying status messages as it proceeds.  For example:

Is this ok [y|n] (n)? y
Creating namespace directory /.:/acmsxp
Deleting old acmstxnlog file
Creating the CDB, please wait...
Creating TPsystem /.:/acmsxp/avertz_hq...
 TPsystem successfully created

The successfully created message means that the TPsystem and related software are created. 

Use the following software to perform further operations on the TPsystem:

       •acms_start_tpsystem script starts the TPsystem and performs a warm start of the dedicated SFS server

       •acmsadmin utility stops TPsystems, creates servers, and manages TPsystems and subordinate entities

       •acms_delete_tpsystem script destroys a TPsystem that is not needed but does not delete a running SFS server

RELATED INFORMATION

Commands: acms(1), acmsadmin(1), acmslog(1), gwlog(1), stdl(1)

Scripts: acms_delete_tpsystem(1), acms_set_version(1), acms_start_tpsystem(1)

acmsxp_introduction(1)