|
HP OpenVMS Systems Documentation |
|
HP OpenVMS System Management Utilities Reference Manual
10.5.5 /TERSE ExampleThe following modifications are made to the standard report when you use the /TERSE qualifier:
The example that follows shows the results of using the /TERSE qualifier with the /FULL qualifier. You can also use /TERSE with standard reports of any detail level to output event information in terse format.
Chapter 11
|
$ INSTALL |
The utility responds with the following prompt:
INSTALL> |
You can then perform INSTALL operations by entering the appropriate INSTALL commands.
To exit from the Install utility, enter the EXIT command at the INSTALL> prompt or press Ctrl/Z. Either method returns control to the DCL command level.
Alternatively, you can enter a single INSTALL command on the same line as the command that invokes the utility, for example:
$ INSTALL LIST/FULL SYS$SYSTEM:LOGINOUT |
This section describes the /TRANSLATE qualifier and provides examples
of its use.
/TRANSLATE
The /TRANSLATE qualifier forces INSTALL to attempt a logical name translation of a file that you specify.
Note
Before you use the /TRANSLATE qualifier, you must invoke INSTALL as a foreign command:
$ INSTALL = "$INSTALL"
/TRANSLATE
Within OpenVMS, when you specify a file name without a device, directory, or file type, OpenVMS usually attempts a logical name translation of the file name before it applies device, directory, or file type defaults. However, if you specify a device, directory, or file type, OpenVMS does not attempt a logical name translation.Using the /TRANSLATE qualifier forces INSTALL to attempt a logical name translation even if a device, directory, or file type is specified.
| #1 |
|---|
DEFINE FILE1 FILE1_EV6
$ INSTALL = "$INSTALL"
$ INSTALL
INSTALL> ADD SYS$SHARE:FILE1.EXE ! SYS$SHARE:FILE1 is added as a
known image
|
The first command in this example defines FILE1 as a logical name with an equivalence name of FILE1_EV6. However, because a device (SYS$SHARE:) and file type (.EXE) are supplied, INSTALL treats FILE1 as part of a file specification rather than as a logical name.
| #2 |
|---|
DEFINE FILE1 FILE1_EV6
$ INSTALL = "$INSTALL"
$ INSTALL/TRANSLATE
INSTALL> ADD SYS$SHARE:FILE1.EXE ! SYS$SHARE:FILE1_EV6 is added as
a known image
|
The first command in this example defines FILE1 as a logical name with an equivalence name of FILE1_EV6. Because /TRANSLATE is specified, INSTALL treats FILE1 as a logical name even though a device (SYS$SHARE:) and file type (.EXE) are supplied.
This section describes and provides examples of the INSTALL commands. The following table summarizes the INSTALL command functions:
| Command | Function |
|---|---|
| ADD | Synonym for the CREATE command |
| CREATE | Installs the specified image as a known image |
| DELETE | Synonym for the REMOVE command |
| EXIT | Exits from INSTALL |
| HELP | Describes how to use INSTALL |
| LIST | Displays a description of each specified known image, global sections, and the addresses of known image data structures |
| PURGE | Deletes all known images installed without the /NOPURGE qualifier |
| REMOVE | Deletes a known image |
| REPLACE | Associates a known image with the latest version of the image file or modifies the attributes of an installed image |
Installs the specified image file as a known image. The ADD command is a synonym for the CREATE command.Requires the CMKRNL privilege. Also requires the SYSGBL privilege to create system global sections and the PRMGBL privilege to create permanent global sections.
Installs the specified image file as a known image. The CREATE command is a synonym for the ADD command.Requires the CMKRNL privilege. Also requires the SYSGBL privilege to create system global sections and the PRMGBL privilege to create permanent global sections.
CREATE file-spec
file-spec
Names the file specification of an image to be installed as a known image. The file specification must name an existing executable or shareable image, which must have been linked with the /NOTRACEBACK qualifier. If you omit the device and directory specification, the default SYS$SYSTEM is used. The default file type is .EXE.The highest existing version of the file is used by default. However, you can specify another version of the file as the known version of the image. Even if other versions of the file exist, the version that you specify will be the version that satisfies all known file lookups for the image.
/ACCOUNTING
/NOACCOUNTING (default)
Enables image-level accounting for the specified image even if image accounting is disabled (by using the DCL command SET ACCOUNTING/DISABLE=IMAGE). When image accounting is enabled on the local node, it logs all images, and the /NOACCOUNTING qualifier has no effect./ARB_SUPPORT=keyword
On Alpha and I64 systems, overrides the system parameter ARB_SUPPORT for this installed image.The following table shows the keywords you can use with the /ARB_SUPPORT qualifier:
Keyword Behavior None The obsolete kernel data cells are not maintained by the system. Fields are initialized to zero or set to invalid pointers at process creation. Clear The obsolete kernel data cells are cleared or set to invalid pointers when the code would have set up values for backward compatibility. Read-only The obsolete cells are updated with corresponding security information stored in the current Persona Security Block (PSB) when a $PERSONA_ASSUME is issued. Full (default) Data is moved from the obsolete cells to the currently active PSB on any security-based operation. For more information about obsolete kernel cells, refer to the ARB_SUPPORT system parameter in an appendix to this manual or in online help.
/AUTHPRIVILEGES[=(priv-name[,...])]
/NOAUTHPRIVILEGES
Installs the file as a known image installed with the authorized privileges specified.Usage Notes
- If a privileged image is not located on the system volume, the image is implicitly installed /OPEN.
- The set of privileges for a privileged image can be empty. You must, however, list each privilege every time you define or redefine privileges.
- The /AUTHPRIVILEGES qualifier applies only to executable images.
- You cannot specify this qualifier for an executable image linked with the /TRACEBACK qualifier.
- You cannot assign privilege names with the /NOAUTHPRIVILEGES qualifier.
You can specify one or more of the privilege names described in detail in an appendix to the HP OpenVMS Guide to System Security. (ALL is the default.)
/EXECUTE_ONLY
/NOEXECUTE_ONLY (default)
The /EXECUTE_ONLY qualifier is meaningful only to main programs. It allows the image to activate shareable images to which the user has execute access but no read access. All shareable images referenced by the program must be installed, and OpenVMS RMS uses trusted logical names (those created for use in executive or kernel mode).You cannot specify this qualifier for an executable image linked with the /TRACEBACK qualifier.
/HEADER_RESIDENT
/NOHEADER_RESIDENT
Installs the file as a known image with a permanently resident header (native mode images only). An image installed header resident is implicitly installed open./LOG
/NOLOG (default)
Lists the newly created known file entry along with any associated global sections created by the installation./OPEN
/NOOPEN
Installs the file as a permanently open known image./PRIVILEGED[=(priv-name[,...])]
/NOPRIVILEGED
Installs the file as a known image with active privileges specified. If a privileged image is not located on the system volume, the image is implicitly installed /OPEN.Usage Notes
- The set of privileges for a privileged image can be empty.
- You must list each privilege every time you define or redefine privileges.
- The /PRIVILEGED qualifier applies only to executable images.
- You cannot specify this qualifier for an executable image linked with the /TRACEBACK qualifier.
- You cannot assign privilege names with the /NOPRIVILEGED qualifier.
Installing Shareable Images
Installing an image with privileges declares that the image is trusted to maintain system integrity and security properly. To maintain that trust, any routine called by the privileged image must also be trusted. For this reason, any shareable images activated for use by a privileged image must be installed. Only trusted logical names (names defined in executive and kernel mode) can be used in locating shareable images to be used by a privileged image.
Interaction of /PRIVILEGED and /AUTHPRIVILEGES
When you create a new entry, the privileges you assign are also assigned for Authorized Privileges if you do not assign specific authorized privileges with the /AUTHPRIVILEGED qualifier.
When you replace an image, any privileges assigned with the /PRIVILEGED qualifier are not repeated as Authorized Privileges. Also, if you use the REPLACE command with the /NOAUTHPRIVILEGES qualifier, the Authorized Privileges become the same as the Default Privileges (set using the /PRIVILEGED qualifier).
You can specify one or more of the privilege names described in detail in an appendix to the HP OpenVMS Guide to System Security. (ALL is the default.)
For examples of how to use CREATE commands with /PRIVILEGES qualifiers, see the Examples section at the end of this command.
/PROTECTED
/NOPROTECTED (default)
Installs the file as a known image that is protected from user-mode and supervisor-mode write access. You can write into the image only from executive or kernel mode. The /PROTECTED qualifier together with the /SHARE qualifier are used to implement user-written services, which become privileged shareable images./PURGE (default)
/NOPURGE
Specifies that the image can be removed by a purge operation; if you specify /NOPURGE, you can remove the image only by a remove operation./RESIDENT[=([NO]CODE,[NO]DATA)]
On Alpha and I64 systems, causes image code sections or read-only data sections to be placed in the granularity hint regions and compresses other image sections, which remain located in process space. If you do not specify the /RESIDENT qualifier, neither code nor data is installed resident. If you specify the /RESIDENT qualifier without keyword arguments, code is installed resident, and data is not installed resident.The image must be linked using the /SECTION_BINDING=(CODE,DATA) qualifier. An image installed with resident code or data is implicitly installed header resident and shared.
/SHARED[=[NO]ADDRESS_DATA]
/NOSHARED
Installs the file as a shared known image and creates global sections for the image sections that can be shared. An image installed shared is implicitly installed open.When you use the ADDRESS_DATA keyword with the /SHARED qualifier, P1 space addresses are assigned for shareable images. With the assigned addresses, the Install utility can determine the content of an address data section when the image is installed rather than when it is activated, reducing CPU and I/O time. A global section is created to allow shared access to address data image sections.
/SIGNAL
/NOSIGNAL
Installs the file as an image capable of accepting signals (or exceptions) from other processes. This allows privileged images to be signaled./WRITABLE=[GALAXY[=IDENT]]
/NOWRITABLE
Installs the file as a writable known image when you also specify the /SHARED qualifier. The /WRITABLE qualifier applies only to images with image sections that are shareable and writable. The /WRITABLE qualifier is automatically negated if the /NOSHARED qualifier is specified.You can use the GALAXY keyword with the /WRITABLE qualifier to place write shared image sections in Galaxy global sections. You can also use the IDENT keyword with GALAXY to include the image ident in the name of the Galaxy global section, so that multiple versions of an image can be used simultaneously in a Galaxy system.
| #1 |
|---|
INSTALL> CREATE/OPEN/SHARED WRKD$:[MAIN]STATSHR
|
The command in this example installs the image file STATSHR as a permanently open shared known image.
| #2 |
|---|
INSTALL> CREATE/OPEN/PRIVILEGED=(GROUP,GRPNAM) GRPCOMM
|
The command in this example installs the image file GRPCOMM as a permanently open known image with the privileges GROUP and GRPNAM.
Any process running GRPCOMM receives the GROUP and GRPNAM privileges for the duration of the execution of GRPCOMM. The full name of GRPCOMM is assumed to be SYS$SYSTEM:GRPCOMM.EXE.
| #3 |
|---|
INSTALL> CREATE/LOG GRPCOMM
|
The command in this example installs the image file GRPCOMM as a known image and then displays the newly created known file entry.
| #4 |
|---|
INSTALL> CREATE/SHARED=ADDRESS_DATA WRKD$:[MAIN]INFOSHR
|
The command in this example installs the INFOSHR file as a shared known image and creates shared global sections for code sections and read-only data sections. Because the command includes the ADDRESS_DATA keyword, address data is also created as a shared global section.
| #5 |
|---|
INSTALL> CREATE STATSHR/PRIV
|
The command in this example creates the STATSHR image with all privileges.
| #6 |
|---|
INSTALL> CREATE STATSHR/PRIV=(OPER,SYSPRV)
|
The command in this example creates the STATSHR image with the OPER and SYSPRV privileges.
| #7 |
|---|
INSTALL> CREATE STATSHR/PRIV=NOALL
|
The command in this example creates the STATSHR image with an empty set of privileges.
| #8 |
|---|
INSTALL> CREATE STATSHR/NOPRIV
|
The command in this example creates the STATSHR image explicitly with no privileges.
| Previous | Next | Contents | Index |