HP OpenVMS Systems Documentation
Compaq ACMS for OpenVMS
You must register and load your ACMS license before you can install or use ACMS. This appendix explains how to register and load your license.
Section B.1 describes an ACMS License Product Authorization Key (PAK).
Section B.2 describes how to load and register your ACMS license using the command procedure VMSLICENSE.COM.
Section B.3 describes how to load and register your ACMS license using the LICENSE DCL commands.
For more information on OpenVMS licensing, see OpenVMS License Management Utility Manual, and the
DCL command HELP LICENSE.
B.1 Sample ACMS License PAK
The ACMS License PAK is a paper document that contains information about your ACMS license. When you register your ACMS license on your system, information from this document is loaded into the license database.
Each PAK has fourteen fields of information. Depending on your license agreement, some fields might contain data, while others might be blank.
Table B-1 lists all the fields on a PAK, along with typical data for an ACMS PAK.
|Field Name||Typical ACMS Information|
|PRODUCT NAME:||ACMS 1|
|NUMBER OF UNITS:||1200|
|PRODUCT RELEASE DATE:||(none)|
|KEY TERMINATION DATE:||(none)|
|ACTIVITY TABLE CODE:||(none)|
You can register and load your ACMS license using the OpenVMS command procedure VMSLICENSE.COM. To invoke this procedure, first log in to the system manager's account, SYSTEM, and then execute the following command:
The procedure displays a menu; press [Return] to choose the default menu item, registering a PAK. The procedure then asks if you have your PAK; press [Return] to choose the default answer, YES.
The procedure now asks you to supply the data for each field on your PAK. For each field, type in the data exactly as it appears on the PAK.
A PAK cannot have both a version and a product release date. If you provide version information, the procedure does not ask for a product release date.
When you have supplied all the PAK information, the procedure displays the information you provided, in the same form as it appears on the PAK, and asks if it is correct. If all the information is correct, press [Return] to choose the default answer, YES.
The procedure then registers the PAK in the license database, and asks if you want to load the license. Press [Return] to choose the default answer, YES.
The license must be registered and loaded on your system before you can install and use ACMS.
When you are finished, select menu item 99 to exit from the procedure.
B.3 Using LICENSE DCL Commands
You can register and load your ACMS license using the DCL commands LICENSE REGISTER and LICENSE LOAD. Log in to the system manager's account, SYSTEM, before executing these commands.
The LICENSE REGISTER command accepts parameters and qualifiers that correspond to the fields on your PAK. The general syntax for this command is:
LICENSE REGISTER product-name [/qualifiers]
Table B-2 lists all the fields on a PAK, along with their LICENSE LOAD parameters and qualifiers.
|Field Name||LICENSE REGISTER Qualifier|
|PRODUCT NAME:||(product-name parameter)|
|NUMBER OF UNITS:||/UNITS=number|
|PRODUCT RELEASE DATE:||/RELEASE_DATE=date|
|KEY TERMINATION DATE:||/TERMINATION_DATE=date|
|ACTIVITY TABLE CODE:||
For example, the following DCL commands register and load the PAK information supplied in Table B-1:
$ LICENSE REGISTER ACMS - _$ /ISSUER="DEC" - _$ /AUTHORIZATION=US-10-THM-0 - _$ /PRODUCER="DEC" - _$ /UNITS=1200 - _$ /VERSION=4.4 - _$ /AVAILABILITY=F - _$ /OPTION=MOD_UNITS - _$ /CHECKSUM=1-NTIN-DCIN-TCTA-NYMR $ LICENSE LOAD ACMS
The ACMS kit includes a save set that contains the files you can use to translate the contents of ACMS message files and help text to languages other than English. This section provides information on how to restore the save set from the kit.
All source files for the messages and help text are stored in a BACKUP save set in the kit. Restore this save set to a directory and modify it there. Follow these instructions to restore the save set:
$ MOUNT/OVERRIDE=ID $100$DUA31:
BACKUP/LOG kit-device:<kit-name>.I /SAVE disk:[directory]
The <kit-name> parameter denotes the software kit you are installing:
$ BACKUP/LOG DKA1:ACMSDEVA_044.I/SAVESET DISK1:[MESSAGES]
$ BACKUP/LOG $100$DUA31:[0,0]ACMSRTOA_044.I/SAVESET - _$ DISK1:[MESSAGES]*
If you want to use DECdtm services on a node, you must create a transaction log for that node. In an OpenVMS Cluster system, you must create a transaction log for each node in the cluster. This appendix describes the following:
For more information about DECdtm services and the commands described
in this appendix, see the OpenVMS documentation set.
D.1 Prerequisites for Creating a Transaction Log
Before you create a transaction log for a node, the following prerequisites must be met:
The size and location of transaction logs can affect the performance of your system. Before you create transaction logs, plan how big to make the logs, and where you are going to put them. Although you can later move a transaction log and change the size to improve performance, careful planning reduces the need for changes.
If the performance of your system is adversely affected by either the location or size of the logs, refer to the OpenVMS documentation for the following information:
These guidelines for determining the size of a transaction log are approximate. When planning transaction logs, overestimate, rather than underestimate, the size of the transaction log.
When you create transaction logs, you specify the size of the log in blocks. By default, the size of each transaction log is 4000 blocks. This default size gives acceptable performance on most systems.
If you know the rate of transactions and their duration, use the following algorithm to calculate the transaction log size:
size = 40 * rate * duration
In this algorithm:
For example, if the rate is 10 transactions per second and the duration is 12 seconds, the calculation is as follows:
size = 40 * 10 * 12 = 4800 blocks
In this example, the recommended size for the transaction log is 4800 blocks.
If you do not know the rate and duration of transactions, accept the
default value of 4000 blocks.
D.2.2 Determining the Location for Transaction Logs
When deciding where to put the transaction log for a node, consider the following factors:
You may have to choose which of these factors are most important. For example, if the node is a workstation, you may choose to give up speed for availability and reliability, by putting the transaction log on a shadowed HSC-based disk, instead of on a faster disk attached to the workstation.
If you have an OpenVMS Cluster, each node must have its own transaction log. To improve the performance of the transactions, distribute the logs among different disks on the system.
Ensure that the disk has sufficient contiguous space to hold the transaction log. A discontiguous transaction log results in poor transaction performance.
This section describes how to set up and create transaction logs. Before creating a transaction log, consider the recommendations for sizing and locating the log, as described in Section D.2. For an example of how to set up and create transaction logs for a three-node OpenVMS Cluster, refer to Section D.4.
To set up and create a transaction log:
DECdtm services uses the logical SYS$JOURNAL to locate transaction logs. For a single node, you must define SYS$JOURNAL to point to the directory that will contain the transaction log. In an OpenVMS Cluster, you define SYS$JOURNAL on each node as a search list that points to all the directories that will contain the transaction logs for the cluster. If you put transaction logs for all nodes in one directory, SYS$JOURNAL on each node points to that directory.
You must define SYS$JOURNAL in the system logical name table, in executive mode.
Remember to define SYS$JOURNAL in both the common and node-specific versions of the SYS$STARTUP:SYLOGICALS.COM command procedure.
To create a transaction log file, use the CREATE LOGFILE command of the Log Manager Control Program (LMCP) Utility:
$ RUN SYS$SYSTEM:LMCP LMCP> CREATE LOGFILE file-spec /SIZE=size LMCP> EXIT
In this example:
This section shows you how to set up and create transaction logs for a three-node OpenVMS Cluster system. In this example, cluster members and transaction log details are listed in Table D-1.
|Node Name||Location||Size (In Blocks)|
To set up and create the transaction logs for the three-node OpenVMS Cluster, follow these steps. Before starting, ensure that all three disks are mounted on all three nodes.
$ DEFINE /SYSTEM /EXECUTIVE SYS$JOURNAL - _$ DISK$USER1:[LOGFILES], - _$ DISK$USER3:[LOGFILES], - _$ DISK$LOG:[LOGFILES]
You can enter all of the commands to set up the cluster from one node, using the SYSMAN Utility.
$ RUN SYS$SYSTEM:LMCP LMCP> CREATE LOGFILE DISK$USER1:[LOGFILES]SYSTEM$ORANGE/SIZE=5000 LMCP> CREATE LOGFILE DISK$USER3:[LOGFILES]SYSTEM$RED LMCP> CREATE LOGFILE DISK$LOG:[LOGFILES]SYSTEM$GREEN/SIZE=6000 LMCP> EXIT