Document revision date: 30 March 2001

## OpenVMS System Management Utilities Reference Manual

Previous | Contents | Index

1. Number of times known file entry has been accessed by this node since it swas installed.
2. First number indicates the current count of concurrent accesses of the known file. The second number indicates the highest count of concurrent accesses of the file since it was installed. This number appears only if the image is installed with the /OPEN qualifier.
3. Number of global sections created for the known file; appears only if the image is installed with the /SHARED qualifier.
4. Translation of the privilege mask; appears only if the image is installed with privileges.

#4
    INSTALL> LIST/GLOBAL

> The command in this example displays all global sections for shared images. Global sections created by INSTALL (prefix INS$) for a specific image are listed following the name of that image.

>                           System Global Sections (1)

>     DSA1000:<SYS2.SYSCOMMON.SYSLIB>SLS$USSSHR.EXE (2)
>      INS$86D9BFB0_003 (3)
>      (14000001) (4)
>            PRM SYS (5)
>        Pagcnt/Refcnt=1/1 (6)

>      INS$86D9BFB0_002    (14000001)          PRM SYS      Pagcnt/Refcnt=3/3
>      INS$86D9BFB0_001    (14000001)          PRM SYS      Pagcnt/Refcnt=1/1
>        .
>        .
>        .
>     RMS$87A63B00         (00000000) WRT DZRO TMP SYS      Pagcnt/Refcnt=74/74
>        .
>        .
>        .
>      671 Global Sections Used, 102138/22862  Global Pages Used/Unused (7)

> 1. Display of global sections in memory.
> 2. Name of the image for which the following global sections were created by INSTALL.
> 3. Name of global section. The prefix identifies the creator of the section; for example, INS means the global section was created by INSTALL. The number includes the address of the section.
> 4. Version number (in hexadecimal) of global section; for shareable images only, the high-order byte (01 in CRFSHR_003) contains major identification, and low-order bytes (0003E8 in CRFSHR_003) contain minor identification determined by the programmer at link time. For executable images, the number is a known unique value determined by the system.
> 5. Attributes of the global section:

>    DZRO | Global section is demand-zero.
>    GRP | Along with a group number indicates a groupwide section, which would be created by a program other than INSTALL.
>    PRM | Global section is permanent.
>    SYS | Global section is systemwide.
>    TMP | Indicates a temporary global section, which would be created by a program other than INSTALL.
>    WRT | Global section is writable.

> 6. Number of pages (VAX) or pagelets (Alpha) in the section and number of page table entries currently mapped to this global section. For a more detailed discussion of mapping global sections, refer to the OpenVMS Programming Concepts Manual.
> 7. Number of global sections created, number of global pages used, and number of global pages unused in local memory. Note that, because of arithmetic rounding, the number of global sections created will sometimes be greater than the SYSGEN parameter GBLSECTIONS. When the size of the system header is being computed, the values of the GBLSECTIONS and SYSMWCNT parameters are combined with the size of the fixed part of the process header. The result is rounded up to the next page boundary. This rounding process sometimes adds space to the global section table, depending on the values of the two SYSGEN parameters and the amount of system paging that preceded the running of INSTALL to create all of the global sections.

#5
    INSTALL> LIST/GLOBAL/FULL

> The command in this example displays a complete listing of global sections for shared images. The /FULL qualifier adds owner and protection codes to the display.

>       System Global Sections
>     NM_MAILSHR_003 (741A6919)           PRM SYS      Pagcnt/Refcnt=10/0
>     NM_MAILSHR_002 (741A6919)           PRM SYS      Pagcnt/Refcnt=1/0
>     NM_MAILSHR_001 (741A6919)           PRM SYS      Pagcnt/Refcnt=11/0
>                    Owner:       [1,4] (1)
>                    Protection:  S:RWED,O:RWED,G:RWED,W:RE (2)
>     .
>     .
>     .

> 1. UIC of the owner of the global section
> 2. Type of access allowed for the image

## PURGE

> Deletes all known file entries for images installed without the /NOPURGE qualifier.

> Requires the CMKRNL privilege. Also requires the SYSGBL privilege to create system global sections and the PRMGBL privilege to create permanent global sections.

### Format

> PURGE

### Parameters

> None.

### Description

> The PURGE command deletes all known file entries for images installed without the /NOPURGE qualifier.

> If a process is accessing global sections when the PURGE command is entered, the global sections are deleted only after the operation initiated by the process completes. However, once the command is entered, no additional processes can access the global sections because they are marked for deletion.

### Example

    INSTALL> PURGE

> The command in this example deletes all images except those installed with the /NOPURGE qualifier. The image files remain unaffected. Writable global sections are written back to disk upon their removal as known images.

## REMOVE

> Deletes a known image. The REMOVE command is identical to the DELETE command.

> Requires the CMKRNL privilege. Also requires the SYSGBL privilege to create system global sections and the PRMGBL privilege to create permanent global sections.

### Format

> REMOVE file-spec

### Parameter

> #### file-spec

> Names the file specification of a known image.

### Description

> The REMOVE command deletes an entry from the known file list. The image's entry on the known file list and any global sections created for the image are deleted. The image file remains unaffected. Writable global sections are written back to disk upon their removal as known images.

> If a process is accessing global sections when the REMOVE command is entered, the global sections are deleted only after the operation initiated by the process completes. However, once the command is entered, no additional processes can access the global sections because they are marked for deletion.

### Example

    INSTALL> REMOVE GRPCOMM

> The command in this example deletes the entry for the known image GRPCOMM from the known image file list.

## REPLACE

> Replaces a known image entry with another version of the image, or with modified attributes. The REPLACE command is a synonym for the DELETE command.

> Requires the CMKRNL privilege. Also requires the SYSGBL privilege to create system global sections and the PRMGBL privilege to create permanent global sections.

### Format

> REPLACE file-spec

### Parameter

> #### file-spec

> Names the file specification of an image installed as a known image.

### Description

> The REPLACE command updates a known file to the latest, or to a specified version found in the specified directory, or in another directory if the file-spec parameter uses a search list.

> You can use the REPLACE command to modify the attributes of currently installed images. Either specify new qualifiers, or change the value of qualifiers used when installing the image with the CREATE (or ADD) command. If you specify no qualifiers, the new image retains the same attributes as the old one. If the REPLACE command modifies neither the installed image file nor its attributes, the REPLACE command allows continued sharing of global sections.

> If a process is accessing global sections when the REPLACE command is entered, the global sections are deleted only after the operation initiated by the process completes. However, once the command is entered, no additional processes can access the global sections because they are marked for deletion.

### Qualifiers

> #### /ACCOUNTING

> #### /NOACCOUNTING (default)

> Enables image-level accounting for selected images even if image accounting is disabled on the local node (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 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.

> Interaction of /PRIVILEGED and /AUTHPRIVILEGES Qualifiers

> 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).

> For a complete listing of privileges, see the 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 installed with the working 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 /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.

> For a complete listing of privileges, see the OpenVMS Guide to System Security. (ALL is the default.)

> #### /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 delete or remove operation.

> #### /RESIDENT[=([NO]CODE,[NO]DATA)]

> On Alpha 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.

> #### /WRITABLE

> #### /NOWRITABLE

> Installs the file as a writable known image as long as you also specify the /SHARED qualifier. The /WRITABLE qualifier only applies to images with image sections that are shareable and writable. The /WRITABLE qualifier is automatically negated if the /NOSHARED qualifier is specified.

### Example

    INSTALL> REPLACE GRPCOMM /ACCOUNTING/NOOPEN

> The command in this example replaces the known image GRPCOMM with the latest version of the image, while enabling image accounting and removing the OPEN attribute from this version.

> The full name of the file specification is assumed to be SYS$SYSTEM:GRPCOMM.EXE.

## Chapter 12
LAN Control Program (LANCP) Utility

## 12.1 LANCP Description

The LAN Control Program (LANCP) utility allows you to configure and control the LAN software on OpenVMS systems. You can use LANCP to:

- Obtain LAN device counters, revision, and configuration information
- Change the operational parameters of LAN devices on the system
- Maintain the LAN permanent and volatile device and node databases
- Control the LANACP LAN Server process (including Maintenance Operations Protocol (MOP) downline load server related functions)
- Initiate MOP console carrier and MOP trigger boot operations

## 12.2 LANCP Usage Summary

> You can use the LANCP utility to:
> - Set LAN parameters to customize your LAN environment.
> - Display LAN settings and counters.
> - Provide MOP downline load support for devices such as terminal servers, x-terminals, and LAN-based printers, and for booting satellites in an OpenVMS Cluster environment. This provides an alternative to the traditional method of using DECnet software.

### Format

> LANCP [command]

### Parameter

> #### command

> Specifies a LANCP command. This parameter is optional. If no command is specified, the utility displays its prompt and waits for command input.

Usage Summary To invoke LANCP, enter the following command at the DCL command prompt:

    $ RUN SYS$SYSTEM:LANCP

The LANCP utility responds by displaying the LANCP> prompt, at which you can enter any LANCP command described in this chapter.

You can also invoke LANCP by using the MCR command or by defining LANCP as a foreign command.

To use the MCR command, at the DCL command prompt, enter:

    $ MCR LANCP

To define LANCP as a foreign command, either at the DCL prompt or in a startup or login command file, enter:

    $ LANCP :== $SYS$SYSTEM:LANCP

Then you can enter the LANCP command at the DCL prompt to invoke the utility and enter LANCP commands.

When you enter the LANCP or MCR LANCP command:

- Without specifying any command qualifiers, the LANCP utility displays the LANCP> prompt, at which you can enter commands.
- With command qualifiers, the LANCP utility terminates after it executes the command and returns you to the DCL command prompt.

Note Some LANCP commands require special privileges.

To exit from the LANCP utility, enter the EXIT command at the LANCP> prompt or press Ctrl/Z.

For information about the LANCP utility, enter the HELP command at the LANCP> prompt.

## 12.3 LANCP Commands

This section describes and provides examples of the LANCP commands. The following table summarizes the LANCP commands.

Command | Function
--- | ---
@ (Execute Procedure) | Executes a command procedure.
CLEAR DLL | Clears MOP downline load counters for all nodes and devices.
CLEAR DEVICE | Deletes a device from the LAN volatile device database.
CLEAR MOPDLL | Same as the CLEAR DLL command.
CLEAR NODE | Deletes a node from the LAN volatile node database.
CONNECT NODE | Connects to a LAN device, such as a terminal server, that implements a management interface using the MOP console carrier protocol.
CONVERT DEVICE_DATABASE | Converts the device database to the format required by the current version of LANCP.
CONVERT NODE_DATABASE | Converts the node database to the format required by the current version of LANCP.
DEFINE DEVICE | Enters a device into the LAN permanent device database or modifies an existing entry.
DEFINE NODE | Enters a node into the LAN permanent node database or modifies an existing entry.
EXIT | Stops execution of LANCP and returns control to the DCL command level.
HELP | Provides online help information about the LANCP utility.
LIST DEVICE | Displays information in the LAN permanent device database.
LIST NODE | Displays information in the LAN permanent node database.
PURGE DEVICE | Deletes a device from the LAN permanent device database.
PURGE NODE | Deletes a node from the LAN permanent node database.
SET ACP | Modifies the operation of the LANACP LAN Server process.
SET DEVICE | Enters a device into the LAN volatile device database or modifies an existing entry and sets device parameters.
SET NODE | Enters a node into the LAN volatile node database or modifies an existing entry.
SHOW CONFIGURATION | Displays a list of LAN devices on the system.
SHOW DEVICE | Displays information in the LAN volatile device database and displays device data.
SHOW DLL | Displays the current state of MOP downline load services.
SHOW LOG | Displays recent downline load activity.
SHOW MOPDLL | Same as the SHOW DLL command.
SHOW NODE | Displays information in the LAN volatile node database.
SPAWN | Creates a subprocess of the current process.
TRIGGER NODE | Issues a request to reboot to a remote node.

Previous | Next | Contents | Index

| privacy and legal statement |
6048PRO_029.HTML