Filter
Top Products
Starting and Setting Up RTR
2.7 RTR Privileges
The
rtrinfo
group is currently only used to allow applications to call
rtr_request_info( )
For other users, create the groups
rtroper
and
rtrinfo
Users who do not fall into the above categories, but are members of the
rtrinfo
group can only use RTR commands that display information (SHOW, MONITOR,
call rtr_request_info, etc.).
If the groups
rtroper
and
rtrinfo
are not defined, then all users automatically
belongs to them. This means that there is no system management required for
systems that do not need privilege checking.
Setting RTR Privileges on OpenVMS Systems
Create the Rights Identifiers RTR$OPERATOR and RTR$INFO if they do not
already exist on your system, and assign them to users as appropriate. The
RTR System Manager must have the RTR$OPERATOR identifier or the OPER
privilege.
Setting RTR Privileges on Windows NT Systems
Administrator privileges are needed for RtrOperator rights by the RTR System
Manager.
2.8 RTR ACP Virtual Memory Sizing
In addition to basic memory requirements of an unconfigured RTR ACP of
approximately 5.8 Mbytes, additional memory requirements may be required
according to the operating system environment that the RTR ACP process is
using.
Compaq strongly recommends that you allocate as much virtual memory as
possible. While there is no penalty for allocating more virtual memory than is
used, the result of allocating too little can be catastrophic.
2.8.1 OpenVMS Virtual Memory Sizing
On OpenVMS the following allowances for additional virtual memory should be
made:
• For each link add an additional 202 Kbytes
• For each facility an additional 13 Kbytes plus 80 bytes for each link in the
facility
• For each client or server application process an additional 190 Kbytes for the
first channel
• For each additional application channel an additional 1350 bytes
It is also necessary to prepare for the number of active transactions in the system.
Unless the client applications are programmed to initiate multiple concurrent
transactions this number will not exceed the total number of client channels in
the system. This should be verified with the application provider.
In addition it is necessary to determine the size of the transaction messages in
use:
1. For each front end:
• Add one Kbyte per active transaction
• Add 250 bytes per message per transaction
2–10 Starting and Setting Up RTR