# hp Reliable Transaction Router
System Manager's Manual

Previous | Contents | Index

# START HTTP_SERVER

> The START HTTP_SERVER starts the HTTP server on the computer system where you wish to use web-based management functions.

## Format

> START HTTP_SERVER

Command Qualifiers | Defaults
--- | ---
/ACCESS=READ_ONLY | Write, edit
/[NO]USER_AUTHENTICATION | /USER-AUTHENTICATION

## Description

> The START HTTP_SERVER command allows you to start the HTTP server on the target computer system. This command must be issued before you can access the web-based management functions. It must be issued for each user of the management features.

## Qualifiers

> ### /ACCESS=READ_ONLY

> The servers can be started in read-only mode. If this qualifer is not specified, the default access is WRITE, EDIT.

> ### /USER_AUTHENTICATION (D)

> ### /NOUSER_AUTHENTICATION

> By default, the servers require HTTP clients to provide a user name and password which will be validated by the host computer operating system. Use /NOUSER_AUTHENTICATION to disable this feature and allow anonymous access.

# START RTR

> The START RTR command starts the RTR Application Control Process (ACP) on one or more nodes. The RTR CLI (Command Line Interface) must be running to execute this command.

## Format

> START RTR

Qualifiers valid on all RTR systems:

Command Qualifiers | Defaults
--- | ---
/CLUSTER | /NOCLUSTER
/NODE[=node-list] | /NODE=default-node
/OUTPUT[=filespec] | /OUTPUT=stdout
/PARTITION[partition-quantity] | /PARTITION=500
/RESERVE_MEMORY_SIZE=m-size | /RESERVE_MEMORY_SIZE=10

Qualifiers valid only on OpenVMS systems.

Command Qualifiers | Defaults
--- | ---
/ASTLM=AST-limit | Depends on /LINKS and /PROCESSES values
/BIOLM=io-buffered | Depends on /LINKS and /PROCESSES values
/BYTLM=buffer-limit | /BYTLM=1000000
/CPULM=time-limit | /CPULM=default-time-limit
/DIOLM=io-direct | /Depends on /LINKS and /PROCESSES values
/ENQLM=enqueue-limit | /ENQLM=2000
/FILLM=file-limit | Depends on /LINKS and /PROCESSES values
/JTQUOTA=job-table-quota | /JTQUOTA=5000
/LINKS=max-links | /LINKS=512
/PGFLQUOTA=pages quota | Depends on /LINKS and /PROCESSES values
/PRCLM=subprocess-limit | /PRCLM=10
/PRIORITY=priority | /PRIORITY=6
/PROCESSES=max-processes | /PROCESSES=64
/TQELM=queue-limit | /TQELM=2000
/WSDEFAULT=working-set | /WSDEFAULT=2000
/WSEXTENT=extent | /WSEXTENT=20000 pages
/WSQUOTA=max-working-set | /WSQUOTA=10000 pages

## Description

> The START RTR command starts the RTRACP on one or more nodes.

> When RTR is started on a node, a detached process called the RTRACP is created. This process performs transaction and communication activities for all users of RTR running on that node.

> The START RTR command must be issued before adding RTR facilities or starting application programs that use RTR.

> When running on OpenVMS systems, the quota qualifiers affect the way the RTRACP is created. The default values will suffice for many applications. The values for quota qualifiers take effect independently of SYSGEN settings. This means that RTR can be started with different quotas without rebooting the system. The quota qualifiers are similar to those specified with the DCL RUN /DETACHED command.

> If you use obsolete RTR Version 2 qualifiers with the START RTR command, a warning is issued. Qualifiers affected are `partitions` , `cache_pages` , and `relations` . Warnings are also generated if an OpenVMS qualifier is used on a non-OpenVMS platform.

## Qualifiers

> ### /ASTLM=AST-limit

> ### /ASTLM=(max-links + max-processes) x 2 + 10 = default AST-limit (D)

> This qualifier is relevant only on OpenVMS systems.

> Specifies the AST limit for the RTRACP.

> The value for `AST-limit` must include five for RTRACP mailbox reads and timer scheduling and a minimum of two per DECnet logical link maintained by RTR.

> For example, in a 20-node configuration, a router node needs an ASTLM of at least 45 ( 10 + (20 x 2) ).

> In systems where a lot of traffic is expected, defining additional ASTLM quota will enable lookahead I/O to be booked to channels without RTRACP being held up in a resource wait.

> The default value of `AST-limit` is automatically calculated, based on the value of /LINKS and /PROCESSES.

> ### /BIOLM=io-buffered

> ### /BIOLM=(max-links + max-processes) x 2 + 10 = default io-buffered (D)

> This qualifier is relevant only on OpenVMS systems.

> Specifies the maximum number of system-buffered I/O operations that the RTRACP can have outstanding at any one time.

> The default value of `io-buffered` is automatically calculated, based on /LINKS and /PROCESSES values.

> ### /BYTLM=buffer-limit

> ### /BYTLM=1000000 (D)

> This qualifier is relevant only on OpenVMS systems.

> Specifies the maximum amount of memory, in bytes, that the RTRACP can use for buffered I/O operations or temporary mailbox creation.

> This should be sufficiently large to account for lookahead DECnet traffic.

> The default for `buffer-limit` is 1000000 bytes.

> ### /CLUSTER

> ### /NOCLUSTER (D)

> Specifies that the command is executed on all the nodes in the cluster.

> If neither /NODE nor /CLUSTER is specified, the command is executed on the nodes specified by the latest SET ENVIRONMENT command. If no SET ENVIRONMENT command has been entered, the command is executed only on the node where the command was issued.

> Note In environments that do not support remote command capability, the /CLUSTER qualifier causes the relevant command to be executed on the local node only. See Section 1.4 for more information.

> ### /CPULM=time-limit

> ### /CPULM=default-time-limit (D)

> This qualifier is relevant only on OpenVMS systems.

> Specifies the maximum amount of CPU time (in delta time) allocated to the RTRACP. The unit of `time-limit` is 10 milliseconds. When the time expires, the RTRACP is deleted.

> The default value is established at system-generation time.

> A `time-limit` value of 0 indicates that CPU time is not restricted.

> ### /DIOLM=io-direct

> ### /DIOLM=(max-links + max-processes) x 2 + 10 = default io-direct (D)

> This qualifier is relevant only on OpenVMS systems.

> Specifies the maximum number of direct I/O operations that the RTRACP can have outstanding at any one time.

> If you do not specify a direct I/O quota, the default value established at system generation time is used.

> The default for `io-direct` is automatically calculated based on the values for /LINKS and /PROCESSES.

> ### /ENQLM=enqueue-limit

> ### /ENQLM=2000 (D)

> This qualifier is relevant only on OpenVMS systems.

> Specifies the maximum number of locks that the RTRACP can have outstanding at any one time.

> The default for `enqueue-limit` is 2000.

> ### /FILLM=file-limit

> ### /FILLM=(max-links + max-processes) + 10 = default file-limit (D)

> This qualifier is relevant only on OpenVMS systems.

> Specifies the maximum number of files that the RTRACP can have open at any one time.

> The default value of `file-limit` is automatically calculated, based on the values of /LINKS and /PROCESSES.

> ### /JTQUOTA=job-table-quota

> ### /JTQUOTA=5000 (D)

> This qualifier is relevant only on OpenVMS systems.

> Allows you to specify a quota for the job-wide logical name table for the RTRACP.

> The default for `job-table-quota` is 1024.

> ### /LINKS=max-links

> ### /LINKS=512 (D)

> This qualifier is relevant only on OpenVMS systems.

> Specifies the maximum number of nodes with which this node can communicate. The default for `max-links` is 512.

> ### /NODE[=node-list]

> ### /NODE=default-node (D)

> Specifies that the command is executed on all nodes specified in `node-list` . If `node-list` is omitted, the command is executed only on the node where the command was issued.

> ### /OUTPUT[=filespec]

> ### /OUTPUT=stdout (D)

> Specifies that the resulting information is written to the file `filespec` . If /OUTPUT or `filespec` is omitted, the standard or default output is used.

> ### /PARTITION=partition-quantity

> ### /PARTITION=500 (D)

> Specifies the maximum number of partitions allowed. The maximum allowable number is 65536. Partition quantity is dynamically allocated to the current maximum, which helps to minimize the use of memory for the user who needs very few partitions. If the /PARTITION qualifier is not used, the default (500) is used.

> ### /PGFLQUOTA=pages

> ### /PGFLQUOTA=((max-links + max-processes) x 400) + 35000 + (reserve_memory_size x 2048) = default pages (D)

> This qualifier is relevant only on OpenVMS systems.

> Specifies the maximum number of pages allocated in the paging file for the RTRACP. The paging file quota is the amount of secondary storage available during execution of the RTRACP image and limits available virtual memory. Note that a shortage of virtual memory can cause transactions to fail.

> The default value of `pages` is automatically calculated, based on the values of /LINKS and /PROCESSES.

> ### /PRCLM=subprocess-limit

> ### /PRCLM=10 (D)

> This qualifier is relevant only on OpenVMS systems.

> Specifies the maximum number of subprocesses that the RTRACP can create.

> The default for `subprocess-limit` is 10.

> ### /PRIORITY=priority

> ### /PRIORITY=6 (D)

> This qualifier is relevant only on OpenVMS systems.

> Requires alter priority (ALTPRI) privilege to set the priority higher than your current process.

> Specifies the base priority at which the RTRACP executes.

> The priority value is a decimal number from 0 through 31, where 31 is the highest priority and 0 is the lowest. Normal priorities range from 0 through 15; real-time priorities range from 16 through 31.

> Higher priorities result in faster response, but lower priorities may be more CPU efficient and give a higher overall throughput.

> ### /PROCESSES=max-processes

> ### /PROCESSES=64 (D)

> This qualifier is relevant only on OpenVMS systems.

> Specifies the maximum number of processes that can use RTR on this node. The default is 64.

> ### /RESERVE_MEMORY_SIZE=memory-size

> ### /RESERVE_MEMORY_SIZE=10 (D)

> Specifies the amount of heap memory, in megabytes, reserved by the RTRACP at startup. This reserve memory is used when the RTRACP is critically low on heap memory, and serves as a buffer to keep the RTRACP from exiting immediately. A log entry, ACPLOWMEMORY, is written when the RTRACP is forced to use the reserve memory. Another log entry, ACPSUFMEMORY, is written after the RTRACP no longer needs to use the reserve memory.

> When the reserve memory is in use, all new and uncommitted transactions are subject to automatic rejection.

> The minimum value is 1MB, the maximum value is 500 MB, and the default value is 10MB.

> ### /TQELM=queue-limit

> ### /TQELM=2000 (D)

> This qualifier is relevant only on OpenVMS systems.

> Specifies the maximum number of timer queue entries that the RTRACP can have outstanding at any one time. This number includes timer requests and scheduled wakeup requests.

> The default for `queue-limit` is 2000.

> ### /WSDEFAULT=working-set

> ### /WSDEFAULT=2000 (D)

> This qualifier is relevant only on OpenVMS systems.

> Specifies the default working set size for the image running in the RTRACP.

> `working-set` cannot be greater than the working set quota (specified with the /WSQUOTA qualifier).

> The default for `working-set` is 2000.

> ### /WSEXTENT=extent

> ### /WSEXTENT=20000 pages (D)

> This qualifier is relevant only on OpenVMS systems.

> Specifies the maximum size in pages to which the image running in the RTRACP can increase its physical memory size.

> The default for `extent` is 20000 pages.

> ### /WSQUOTA=max-working-set

> ### /WSQUOTA=10000 pages (D)

> This qualifier is relevant only on OpenVMS systems.

> Specifies the maximum size in pages to which the image being executed in the RTRACP process can increase its working set size.

> The default for `max-working-set` is 10000 pages.

### Related commands

- SHOW RTR
- STOP RTR

##

### Examples

> See Chapter 2, Starting and Setting Up RTR, for examples of how to use the START RTR command.

# STOP HTTP_SERVER

> The STOP HTTP_SERVER stops the HTTP server.

## Format

> STOP HTTP_SERVER

## Description

> The STOP HTTP_SERVER command stops the HTTP server. This command must be issued for each user of the web-based management features.

# STOP RTR

> The STOP RTR command stops RTR on one or more nodes.

## Format

> STOP RTR

Command Qualifiers | Defaults
--- | ---
/ABORT | /NOABORT
/CLUSTER | /NOCLUSTER
/NODE[=node-list] | /NODE=default-node
/OUTPUT[=filespec] | /OUTPUT=stdout

## Description

> The STOP RTR command stops RTR in an orderly manner.

> Alternatively, RTR can be stopped in an abrupt manner (/ABORT), and any applications using RTR are forced to exit.

## Qualifiers

> ### /ABORT

> Specifying /ABORT causes RTR to stop, regardless of the state of any RTR user applications. Applications using RTR are forced to exit.

> Note This qualifier supersedes the /NOCONFIRM of earlier versions of RTR.

> ### /CLUSTER

> ### /NOCLUSTER (D)

> Specifies that the command is executed on all the nodes in the cluster.

> If neither /NODE nor /CLUSTER is specified, the command is executed on the nodes specified by the latest SET ENVIRONMENT command. If no SET ENVIRONMENT command has been entered, the command is executed only on the node where the command was issued.

> Note In environments that do not support remote command capability, the /CLUSTER qualifier causes the relevant command to be executed on the local node only. See Section 1.4 for more information.

> ### /NODE[=node-list]

> ### /NODE=default-node (D)

> Specifies that the command is executed on all nodes specified in `node-list` . If `node-list` is omitted, the command is executed only on the node where the command was issued.

> ### /OUTPUT[=filespec]

> ### /OUTPUT=stdout (D)

> Specifies that the resulting information is written to the file `filespec` . If /OUTPUT or `filespec` is omitted, the standard or default output is used.

### Related commands

- SHOW RTR
- START RTR

##

### Examples

> See Chapter 2, Starting and Setting Up RTR, for examples of how to use the STOP RTR command.

# TRIM FACILITY

> The TRIM FACILITY command removes nodes or roles (or both) from an existing facility definition.

## Format

> TRIM FACILITY [facility_name]

Command Qualifiers | Defaults
--- | ---
/BACKEND=backend-list | /NOBACKEND
/CLUSTER | /NOCLUSTER
/FRONTEND=frontend-list | /NOFRONTEND
/NODE[=node-list] | /NODE=default-node
/OUTPUT[=filespec] | /OUTPUT=stdout
/ROUTER=router-list | /NOROUTER

## Description

> The TRIM FACILITY command removes nodes or roles (or both) from an RTR facility definition. A node can be removed from a facility or a role can be removed from a node. For example, a node having both router and frontend roles can be trimmed to have only a router role. When a role is trimmed from a facility definition, quorum is recalculated. This may cause a backend to lose quorum briefly.

> A TRIM FACILITY command causing the removal of all roles is equivalent to a DELETE FACILITY command.

> A frontend role can be removed from a node with the router role as long as there is at least one other frontend defined.

> A backend role can be removed from a node with the router role as long as at least one other backend is defined. A command to remove a backend role should be executed on all router nodes to avoid problems with inconsistent facility definitions.

> If a router role is removed, the node from which it is removed will discard its knowledge of other backends and frontends in the facility. If the router role is again added to the node (using EXTEND FACILITY), this information must be specified again.

> To have a consistent facility definition across the nodes of the facility (avoiding problems with attaining quorum), the command to remove a router role must be executed on all relevant nodes. This means executing the command on the node losing the router role, plus all backend and frontend nodes which know about this router.

> As with CREATE or MODIFY FACILITY, superfluous nodes or roles can be specified. That is, you can specify backend nodes on a node which only has a frontend role, and frontend nodes can be specified on a node which only has a backend role. This permits a single RTR management command to be issued on many nodes, and each node only accepts those parts of the command which are relevant to it.

> When using this command, the facility being extended may lose quorum until the affected nodes agree upon the new facility definition. During this time, server applications will not be presented with any new transactions.

> RTR MONITOR QUORUM displays a monitor picture which allows the quorum negotiations to be observed. You can use this after using a TRIM FACILITY command; once quorum has again been attained, the participating nodes return to the quorate state.

> For example, in a three-node facility called `facnam` , the nodes `FE` and `NFE` have only frontend roles, and node `FETRBE` has frontend, router and backend roles. This facility could have been created as follows:

>         % RTR
>         RTR> SET ENVIRONMENT /NODE=(FE,FETRBE,NFE)
>         RTR> CREATE FACILITY facnam /FRONTEND=(NFE,FE,FETRBE) -
>             /ROUTER=FETRBE -
>             /BACKEND=FETRBE

> The frontend node `NFE` can be removed from the facility as follows:

>         % RTR
>         RTR> SET ENVIRONMENT /NODE=(FETRBE,NFE)
>         RTR> TRIM FACILITY facnam /FRONTEND=NFE

## Parameters

> ### facility_name

> Specifies the name of the facility to be trimmed.

> The default value for `facility_name` is `RTR$DEFAULT_FACILITY` .

## Qualifiers

> ### /BACKEND=backend-list

> ### /NOBACKEND (D)

> Specifies the names of the nodes where backend roles for this facility are removed.

> `backend-list` is a list of `backend-nodes` separated by commas. If there is more than one `backend-node` , `backend-list` must be enclosed in parentheses.

> `backend-node` is either the name of a node or `@filespec` , where `filespec` specifies a text file containing a `backend-list` on each line.

> ### /CLUSTER

> ### /NOCLUSTER (D)

> Specifies that the command is executed on all the nodes in the cluster.

> If neither /NODE nor /CLUSTER is specified, the command is executed on the nodes specified by the latest SET ENVIRONMENT command. If no SET ENVIRONMENT command has been entered, the command is executed only on the node where the command was issued.

> Note In environments that do not support remote command capability, the /CLUSTER qualifier causes the relevant command to be executed on the local node only. See Section 1.4 for more information.

> ### /FRONTEND=frontend-list

> ### /NOFRONTEND (D)

> Specifies the names of nodes where the frontend role is removed for this facility. `frontend-list` is a list of `frontend-nodes` separated by commas. If there is more than one `frontend-node` , `frontend-list` must be enclosed in parentheses.

> `frontend-node` is either the name of a node or `@filespec` , where `filespec` specifies a text file containing a `frontend-list` on each line.

> ### /NODE[=node-list]

> ### /NODE=default-node (D)

> Specifies that the command is executed on all nodes specified in `node-list` . If `node-list` is omitted, the command is executed only on the node where the command was issued.

> ### /OUTPUT[=filespec]

> ### /OUTPUT=stdout (D)

> Specifies that the resulting information is written to the file `filespec` . If /OUTPUT or `filespec` is omitted, the standard or default output is used.

> ### /ROUTER=router-list

> ### /NOROUTER (D)

> Specifies the names of the nodes where the router role is removed for this facility.

> `router-list` is a list of `router-nodes` separated by commas. If there is more than one `router-node` , `router-list` must be enclosed in parentheses.

> `router-node` is either the name of a node or `@filespec` , where `filespec` specifies a text file containing a `router-list` on each line.

### Related commands

- SHOW FACILITY
- DELETE FACILITY
- CREATE FACILITY
- EXTEND FACILITY

Previous | Next | Contents | Index