![[Digital logo]](../../IMAGES/DIGITAL-LOGO.GIF){kind=logo}
![[HR]](../../IMAGES/REDBAR.GIF)
Displays information about an identifier, such as its name, value, attributes, and holders, on the current SYS$OUTPUT device.
SHOW/IDENTIFIER [id-name]
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.
/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 are valid formats 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)
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
Name Value Attributes INVENTORY %X80010006 NORESOURCE NODYNAMIC Holder Attributes ANDERSON NORESOURCE NODYNAMIC BROWN NORESOURCE NODYNAMIC CRAMER NORESOURCE NODYNAMIC
UAF> SHOW/IDENTIFIER/USER=ANDERSON
Name Value Attributes ANDERSON [000300,000015] NORESOURCE NODYNAMIC
UAF> SHOW/IDENTIFIER/USER=[300,015]
UAF> SHOW/IDENTIFIER/VALUE=UIC:[300,015]
Displays all authorized proxy access for the specified remote user.
SHOW/PROXY node::remote-user
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.
/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)
The SHOW/PROXY command displays the first 255 characters of a node name although the command can handle a maximum of 1024 characters.
UAF> SHOW/PROXY SAMPLE::[200,100]
Default proxies are flagged with an *
SAMPLE::[200,100]
MARCO * PROXY2
PROXY3
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
Displays the identifiers held by the specified identifiers or, if /USER is specified, all identifiers held by the specified users.
SHOW/RIGHTS [id-name]
id-name
Specifies the name of the identifier associated with the user. If you omit the identifier name, you must specify the /USER 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)
Output displayed from the SHOW/RIGHTS command is identical to that written to RIGHTSLIST.LIS when you use the LIST/RIGHTS command.
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 NODYNAMICNote that the following formats of the command produce the same result:
SHOW/RIGHTS/USER=ANDERSONSHOW/RIGHTS/USER=[300,015]
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.
Digital 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, see Appendix J.
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 on 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, see 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.
Note
When making major configuration changes, do not use feedback. Specify nofeedback to assure the use of the initial AUTOGEN settings. See Table 6-4 for more information about nofeedback.
Digital recommends that you run AUTOGEN in the following circumstances:
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.
| ACP_DINDXCACHE | ACP_DIRCACHE | ACP_HDRCACHE |
| ACP_MAPCACHE | ACP_MULTIPLE | ACP_QUOCACHE |
| ACP_SWAPFLGS | ACP_SYSACC | BALSETCNT |
| BORROWLIM | CTLPAGES | DUMPSTYLE |
| ERLBUFFERPAGES¹ | EXPECTED_VOTES | FREEGOAL |
| FREELIM | GBLPAGES | GBLPAGFIL |
| GBLSECTIONS | ++GH_EXEC_CODE | ++GH_EXEC_DATA |
| ++GH_RES_CODE | ++GH_RES_DATA | GROWLIM |
| +INTSTKPAGES | LNMPHASHTBL² | LNMSHASHTBL |
| LOAD_SYS_IMAGES¹ | LOCKDIRWT | LOCKIDTBL |
| LONGWAIT¹ | MAXPROCESSCNT | MINWSCNT |
| MMG_CTLFLAGS | MPW_HILIMIT | MPW_IOLIMIT¹ |
| MPW_LOLIMIT | MPW_LOWAITLIMIT | MPW_THRESH¹ |
| MPW_WAITLIMIT | MPW_WRTCLUSTER | MSCP_BUFFER |
| MSCP_LOAD | ++MULTITHREAD | MVTIMEOUT¹ |
| NISCS_MAX_PKTSZ¹ | NISCS_PORT_SERV | NPAGEDYN |
| NPAGEVIR | PAGEDYN | PASTDGBUF |
| PFCDEFAULT | PFRATH¹ | PFRATL |
| ++PHYSICAL_MEMORY | +PHYSICALPAGES | PIOPAGES |
| PIXSCAN | PQL_DPGFLQUOTA² | PQL_DWSDEFAULT |
| PQL_DWSEXTENT | PQL_DWSQUOTA | PQL_MPGFLQUOTA² |
| PQL_MWSDEFAULT | PQL_MWSEXTENT | PQL_MWSQUOTA |
| PRCPOLINTERVAL¹ | PROCSECTCNT | QUANTUM¹ |
| RECNXINTERVAL¹ | RESHASHTBL | RMS_DFMBC |
| RMS_DFMBFIDX | RMS_DFMBFREL | RMS_DFMBFSDK |
| RMS_DFMBFSMT | RMS_DFMBFSUR | RMS_DFNBC |
| SCSBUFFCNT | SCSCONNCNT | SCSNODE |
| SCSRESPCNT | SHADOW_MAX_COPY | +SPTREQ |
| SWPOUTPGCNT² | SYSMWCNT | TMSCP_LOAD |
| VAXCLUSTER | +VBSS_ENABLE | ++VCC_FLAGS |
| ++VCC_MAXSIZE | VIRTUALPAGECNT | VOTES |
| WSDEC | WSINC¹ | WSMAX |
| ++ZERO_LIST_HI |
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 on 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 on 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.
| ACP_DINDXCACHE | ACP_DIRCACHE | ACP_EXTCACHE |
| ACP_FIDCACHE | ACP_HDRCACHE | ACP_MAPCACHE |
| ACP_QUOCACHE | GBLPAGES | GBLSECTIONS |
| ++GH_EXEC_CODE | ++GH_EXEC_DATA | ++GH_RES_CODE |
| ++GH_RES_DATA | ++GH_RSRVPGCNT | LNMSHASHTBL |
| LOCKIDTBL | MAXPROCESSCNT | MSCP_BUFFER |
| NPAGEDYN | PAGEDYN | RESHASHTBL |
| SCSBUFFCNT | SCSCONNCNT | SCSRESPCNT |
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.
| Phase | Description |
|---|---|
| SAVPARAMS | Saves dynamic feedback from the running system. |
| GETDATA | Collects all data to be used in AUTOGEN calculations. |
| GENPARAMS | Generates new system parameters; creates the installed image list. |
| TESTFILES | Displays the system page, swap, and dump file sizes calculated by AUTOGEN (cannot be used as a start phase). |
| GENFILES | Generates new system page, swap, and dump files if appropriate (cannot be used as a start phase). |
| SETPARAMS | Runs SYSMAN to set the new system parameters in the default parameter file, saves the original parameters, and generates a new parameter file, AUTOGEN.PAR. |
| SHUTDOWN | Prepares the system to await a manual reboot. |
| REBOOT | Automatically shuts down and reboots the system. |
| HELP | Displays help information to the screen. |
The following sections describe each phase in detail.
The SAVPARAMS phase records feedback in the file AGEN$FEEDBACK.DAT, which can be used in subsequent AUTOGEN phases. If you specify NOFEEDBACK as the execution-mode parameter, the information collected is not used.
The SAVPARAMS phase is valid as a start phase and end phase. SAVPARAMS requires the SYSPRV and CMKRNL privileges.
Note
You can specify the SAVE_FEEDBACK option during an interactive orderly shutdown with SYS$SYSTEM:SHUTDOWN.COM. Entering this option in response to the prompt "Shutdown options:" records feedback collected since the system was last booted. Using the SAVE_FEEDBACK option creates a new version of SYS$SYSTEM:AGEN$FEEDBACK.DAT. Run AUTOGEN from the GETDATA phase after the system reboots to use this new version of the feedback.
The GETDATA phase collects the following information required for AUTOGEN calculations and places it in the file PARAMS.DAT:
The GETDATA phase also attempts to configure devices on the system, by executing the following:
The GETDATA phase is valid as a start phase and an end phase. GETDATA requires the SYSPRV and CMKRNL privileges.
In the GENPARAMS phase, AUTOGEN calculates the parameter values based on data stored in PARAMS.DAT and produces SETPARAMS.DAT as output. AUTOGEN checks to see if feedback is included, and if so, uses it in the calculations unless the NOFEEDBACK execution mode was specified when AUTOGEN was invoked. Also during this phase, AUTOGEN generates the known image file list (VMSIMAGES.DAT).
The GENPARAMS phase is valid as a start phase and an end phase. GENPARAMS requires the SYSPRV and OPER privileges.
The TESTFILES phase displays system page, swap, and dump file sizes calculated by AUTOGEN. (This phase does not change the file sizes.)
File sizes for all currently installed primary and secondary page and swap files are displayed. The information is directed to SYS$OUTPUT and the AGEN$PARAMS.REPORT file by default.
Specify the TESTFILES phase to display AUTOGEN's file size calculations; to generate new sized files, specify the GENFILES phase. You cannot specify both of these phases when invoking AUTOGEN. Digital recommends you use TESTFILES to display the file size changes before actually generating new sized files on your system.
The TESTFILES phase is valid only as an end phase. TESTFILES requires the SYSPRV privilege.
The GENFILES phase generates the new page, swap, and dump files on the system. This phase changes the file sizes based on AUTOGEN's calculations.
The GENFILES phase does not modify a file if the calculated size change is within ten percent of the existing file size. The following files are affected: PAGEFILE.SYS, SWAPFILE.SYS, SYSDUMP.DMP, and all other currently installed page and swap files. For more information, see the chapter on managing page, swap and dump files in the OpenVMS System Manager's Manual.
GENFILES is valid only as an end phase. GENFILES requires the SYSPRV privilege.
The SETPARAMS phase uses as its input the SETPARAMS.DAT file created during the GENPARAMS phase. In this phase, AUTOGEN runs SYSMAN to update the system parameter values in the default parameter file.
On VAX systems, the default parameter file is SYS$SYSTEM:VAXVMSSYS.PAR. AUTOGEN saves the current system parameters in the file SYS$SYSTEM:VAXVMSSYS.OLD before updating these parameters in SYS$SYSTEM:VAXVMSSYS.PAR. The new values are also saved in SYS$SYSTEM:AUTOGEN.PAR.
On Alpha systems, SYS$SYSTEM:ALPHAVMSSYS.PAR is the default parameter file. AUTOGEN saves the current system parameters in the file SYS$SYSTEM:ALPHAVMSSYS.OLD before updating these parameters in SYS$SYSTEM:ALPHAVMSSYS.PAR. The new values are also saved in SYS$SYSTEM:AUTOGEN.PAR.
The SETPARAMS phase is valid as a start phase and an end phase. SETPARAMS requires the SYSPRV and OPER privileges.
SHUTDOWN shuts down the system and awaits a manual reboot. To use the new system parameter values generated in the SETPARAMS phase, specify either SHUTDOWN or REBOOT as the end phase. You can define the logical name AGEN$SHUTDOWN_TIME (using the DCL command DEFINE) to specify the number of minutes before shutdown occurs.
SHUTDOWN requires the SETPRV privilege.
REBOOT automatically shuts down and reboots the system, thus installing the new parameter values. To install the new system parameter values generated in the SETPARAMS phase, specify either SHUTDOWN or REBOOT as the end phase. You can define the logical name AGEN$SHUTDOWN_TIME (using the DCL command DEFINE) to specify the number of minutes before shutdown occurs.
REBOOT requires the SETPRV privilege.
HELP displays help information about AUTOGEN to the screen. The HELP phase is only valid as the start phase command line parameter. When you specify HELP for the start phase, the end phase and execution mode parameters are ignored.
Specify an execution mode when you invoke AUTOGEN to control how AUTOGEN uses feedback. Table 6-4 lists the execution-mode options.
| Option | Description |
|---|---|
| FEEDBACK | Specifies that AUTOGEN run in feedback mode, using dynamic feedback collected during the SAVPARAMS phase to make its calculations. |
| NOFEEDBACK | Specifies that AUTOGEN not use feedback in the calculations. The feedback from the SAVPARAMS phase is ignored. Use NOFEEDBACK mode for the initial system installation or upgrade. NOFEEDBACK supersedes the execution-mode option INITIAL, which was used in a previous version of the operating system. |
| CHECK_FEEDBACK | Specifies that AUTOGEN use feedback in its calculations as long as the feedback is valid. If feedback is suspect, AUTOGEN does not use feedback in the calculations, but continues through the specified end phase. |
| Blank | If you do not specify an execution mode, AUTOGEN uses feedback in the calculations by default. However, if AUTOGEN determines that the feedback might be suspect, it performs the calculations, issues the feedback report, and stops before modifying any parameters or system files, even if you specified an end phase of GENFILES, SETPARAMS, SHUTDOWN or REBOOT. |
Table 6-5 lists the files AUTOGEN uses during each phase.
| AUTOGEN Phase | Input Files¹ | Output Files¹ |
|---|---|---|
| SAVPARAMS | None | AGEN$FEEDBACK.DAT |
| GETDATA |
MODPARAMS.DAT
VMSPARAMS.DAT AGEN$FEEDBACK.DAT |
PARAMS.DAT |
| GENPARAMS | PARAMS.DAT |
SETPARAMS.DAT
VMSIMAGES.DAT AGEN$PARAMS.REPORT |
| TESTFILES | PARAMS.DAT | SYS$OUTPUT |
| GENFILES | PARAMS.DAT |
PAGEFILE.SYS
SWAPFILE.SYS (and secondary page and swap files) SYSDUMP.DMP AGEN$PARAMS.REPORT |
| SETPARAMS | SETPARAMS.DAT |
+VAXVMSSYS.PAR
++ALPHAVMSSYS.PAR AUTOGEN.PAR +VAXVMSSYS.OLD ++ALPHAVMSSYS.OLD |
| SHUTDOWN | None | None |
| REBOOT | None | None |
The AUTOGEN command procedure runs automatically when your system is installed or upgraded to set appropriate values for system parameters and sizes for system page, swap, and dump files.
Previous | Next | Contents | [Home] | [Comments] | [Ordering info] | [Help]
6048P011.HTM OSSG Documentation 26-NOV-1996 12:42:33.24Copyright © Digital Equipment Corporation 1996. All Rights Reserved.