HP OpenVMS Systems Documentation

Displays information about an identifier, such as its name, value, attributes, and holders, on the current SYS$OUTPUT device.

Format

SHOW/IDENTIFIER [id-name]

Parameter

id-name

Specifies an identifier name. The identifier name is a string of 1 to 31 alphanumeric characters. The name can contain underscores and dollar signs. It must contain at least one nonnumeric character. If you omit the identifier name, you must specify /USER or /VALUE.

Qualifiers

/BRIEF

Specifies a brief listing in which only the identifier name, value, and attributes are displayed. The default format is /BRIEF.

/FULL

Specifies a full listing in which the names of the identifier's holders are displayed along with the identifier's name, value, and attributes.

/USER=user-spec

Specifies one or more users whose identifiers are to be displayed. The user-spec can be a user name or a UIC. You can use the asterisk wildcard character (*) to specify multiple UICs or all user names. UICs must be in the form [*,*], [n,*], [*,n], or [n,n]. A wildcard user name specification (*) displays identifiers alphabetically by user name; a wildcard UIC specification ([*,*]) displays them numerically by UIC.

/VALUE=value-specifier

Specifies the value of the identifier to be listed. The following formats are valid for the value-specifier:

IDENTIFIER:n	An integer value in the range of 65,536 to 268,435,455. You can also specify the value in hexadecimal (precede the value with %X) or octal (precede the value with %O). To differentiate general identifiers from UIC identifiers, %X80000000 is added to the value you specify.
UIC:uic	A UIC value in the standard UIC format.

See also the screen control qualifiers listed under the SHOW command:

/EXACT

/HIGHLIGHT[=keyword]

/NOHIGHLIGHT (default)

/PAGE[=keyword]

/NOPAGE (default)

/SEARCH=string

/WRAP

/NOWRAP (default)

Description

The SHOW/IDENTIFIER command displays identifier names, values, attributes, and holders in various formats depending on the qualifiers specified. Two of these formats are illustrated in the following examples.

Examples

UAF> SHOW/IDENTIFIER/FULL INVENTORY
      

This command would produce output similar to the following example:

Name Value Attributes INVENTORY %X80010006 NORESOURCE NODYNAMIC Holder Attributes ANDERSON NORESOURCE NODYNAMIC BROWN NORESOURCE NODYNAMIC CRAMER NORESOURCE NODYNAMIC

UAF> SHOW/IDENTIFIER/USER=ANDERSON
      

This command displays the identifier associated with the user ANDERSON, as follows:

Name Value Attributes ANDERSON [000300,000015] NORESOURCE NODYNAMIC

The identifier is shown, along with its value and attributes. Note, however, that this is the same result you would produce had you specified ANDERSON's UIC with the following forms of the command:

UAF> SHOW/IDENTIFIER/USER=[300,015]

UAF> SHOW/IDENTIFIER/VALUE=UIC:[300,015]

SHOW/PROXY

Displays all authorized proxy access for the specified remote user.

Format

SHOW/PROXY node::remote-user

Parameters

node

Specifies the name of a network node in the network proxy authorization file. The asterisk wildcard character (*) is permitted in the node specification.

remote-user

Specifies the user name or UIC of a user on a remote node. The asterisk wildcard character (*) is permitted in the remote-user specification.

Qualifiers

/OLD

Directs AUTHORIZE to display information from NETPROXY.DAT rather than the default file NET$PROXY.DAT.

If someone modifies the proxy database on a cluster node that is running an OpenVMS system prior to Version 6.1, you can use the /OLD qualifier to display the contents of the old database, NETPROXY.DAT.

See also the screen control qualifiers listed under the SHOW command:

/EXACT

/HIGHLIGHT[=keyword]

/NOHIGHLIGHT (default)

/PAGE[=keyword]

/NOPAGE (default)

/SEARCH=string

/WRAP

/NOWRAP (default)

Description

The SHOW/PROXY command displays the first 255 characters of a node name although the command can handle a maximum of 1024 characters.

Examples

UAF> SHOW/PROXY SAMPLE::[200,100]

 Default proxies are flagged with an *

SAMPLE::[200,100]
     MARCO *                              PROXY2
     PROXY3
      

The command in this example displays all authorized proxy access for the user on node SAMPLE with a UIC of [200,100]. The default proxy account can be changed from MARCO to PROXY2 or PROXY3 with the MODIFY/PROXY command.

UAF> SHOW/PROXY *::*

 Default proxies are flagged with (D)

TAO:.TWA.RANCH::MARTINEZ
    MARTINEZ (D)                        SALES_READER

UAF> show/proxy/old *::*

 Default proxies are flagged with (D)

RANCH::MARTINEZ
    MARTINEZ (D)                        SALES_READER
      

The command in this example displays information about local authorized proxy access on a system running DECnet-Plus. The first command draws information from the file NET$PROXY.DAT. By including the /OLD qualifier on the SHOW/PROXY command, AUTHORIZE displays information from the file NETPROXY.DAT.

Displays the identifiers held by the specified identifiers or, if /USER is specified, all identifiers held by the specified users.

Format

SHOW/RIGHTS [id-name]

Parameter

id-name

Specifies the name of the identifier associated with the user. If you omit the identifier name, you must specify the /USER qualifier.

Qualifier

/USER=user-spec

Specifies one or more users whose identifiers are to be listed. The user-spec can be a user name or a UIC. You can use the asterisk wildcard character (*) to specify multiple UICs or all user names. UICs must be in the form [*,*], [n,*], [*,n], or [n,n]. A wildcard user name specification (*) or wildcard UIC specification ([*,*]) displays all identifiers held by users. The wildcard user name specification displays holders' user names alphabetically; the wildcard UIC specification displays them in the numerical order of their UICs.

See also the screen control qualifiers listed under the SHOW command:

/EXACT

/HIGHLIGHT[=keyword]

/NOHIGHLIGHT (default)

/PAGE[=keyword]

/NOPAGE (default)

/SEARCH=string

/WRAP

/NOWRAP (default)

Description

Output displayed from the SHOW/RIGHTS command is identical to that written to RIGHTSLIST.LIS when you use the LIST/RIGHTS command.

Example

UAF> SHOW/RIGHTS ANDERSON
      

This command displays all identifiers held by the user ANDERSON. For example:

Name Value Attributes INVENTORY %X80010006 NORESOURCE NODYNAMIC PAYROLL %X80010022 NORESOURCE NODYNAMIC

Note that the following formats of the command produce the same result:

SHOW/RIGHTS/USER=ANDERSON

SHOW/RIGHTS/USER=[300,015]

6.1 AUTOGEN Description

In addition, you can use AUTOGEN to reset system parameter values, system file sizes, or both. The new values and file sizes take effect the next time the system is booted.

Compaq recommends that you run AUTOGEN on a weekly basis to adjust system parameters according to your system's work load. For a list and description of all system parameters, refer to

AUTOGEN executes in phases with each phase performing a separate task. You control which tasks AUTOGEN performs by specifying a start phase and an end phase when you invoke AUTOGEN. For more information about the AUTOGEN phases, see Section 6.4.

You can add commands to the file SYS$SYSTEM:MODPARAMS.DAT to control the system parameter values and file sizes that AUTOGEN sets. AUTOGEN uses the information in this file to determine final values for system parameters or page, swap or dump file sizes. For more information, refer to the chapter about managing system parameters in the OpenVMS System Manager's Manual.

AUTOGEN can improve system performance by using dynamic information, called feedback, gathered from the running system.

Compaq recommends that you run AUTOGEN in the following circumstances:

• During a new installation or upgrade.
• Whenever your work load changes significantly.
• When you add an optional (layered) software product. Certain layered products might require you to execute AUTOGEN to adjust parameter values and page and swap file sizes. (For information about using AUTOGEN to modify page and swap files, refer to the chapter on managing page, swap, and dump files in the OpenVMS System Manager's Manual.) Refer to specific product documentation for installation requirements.
• When you install images with the /SHARED attribute. The GBLSECTIONS and GBLPAGES parameters might need to be increased to accommodate additional use of global pages and global sections.
• During normal operation, as part of a batch-oriented command procedure that runs AUTOGEN on a regular basis and automatically sends a report to an appropriate Mail account. The recommended procedure is described in the chapter on managing system parameters in the OpenVMS System Manager's Manual.

After a new operating system installation or upgrade, examine the results of calculations that AUTOGEN made to determine whether AUTOGEN has set system parameter values that are appropriate for your workload requirements.

Table 6-1 lists the system parameters affected by AUTOGEN calculations. AUTOGEN calculations also affect the size of page, swap and dump files. Table 6-2 lists the system parameters affected by AUTOGEN feedback.

AUTOGEN feedback minimizes the necessity to modify parameter values or system file sizes. Feedback allows AUTOGEN to automatically size the operating system based on your actual work load. Sizing is the process of matching the allocation of system resources (memory and disk space) with the workload requirements of your site.

Feedback is information about how various resources are used by the system's work load. This information is continuously collected by the operating system executive. Because the system collects feedback when exception events occur, feedback collection does not affect system performance.

You control how AUTOGEN uses feedback by specifying an execution mode when you invoke AUTOGEN. When run in feedback mode, AUTOGEN analyzes this information and adjusts any related parameter values. For information about controlling AUTOGEN's use of feedback, see Section 6.5.

AUTOGEN collects feedback during the SAVPARAMS phase by executing the image SYS$SYSTEM:AGEN$FEEDBACK.EXE. AUTOGEN writes feedback information to the file SYS$SYSTEM:AGEN$FEEDBACK.DAT. This file is then read during the GETDATA phase. For more information about AUTOGEN phases, see Section 6.4.

Table 6-2 lists the system parameters affected by AUTOGEN feedback. Feedback also affects the size of page and swap files.

AUTOGEN executes in phases. You control which tasks AUTOGEN performs by specifying a start phase and an end phase when you invoke AUTOGEN. Table 6-3 lists the phases AUTOGEN can execute in order.

The following sections describe each phase in detail.