HP OpenVMS Systems Documentation

Displays the name of the current site-independent startup command procedure.

Format

SHOW/STARTUP

Parameters

None.

Qualifiers

None.

Example

SYSGEN>  SHOW/STARTUP
Startup command file = SYS$SYSTEM:STARTUP.COM
      

This command displays the name of the site-independent startup command procedure.

Modifies the Ctrl/C, Ctrl/O, Ctrl/Y, and Ctrl/Z echo strings on a systemwide basis.

Format

TERMINAL/ECHO

Parameters

None.

Qualifiers

None.

Description

Before entering the TERMINAL command, edit the file SYSGTTSTR.MSG in SYS$EXAMPLES. The file contains detailed instructions for the editing procedure.

When you enter the TERMINAL command after editing the file, the modifications you have specified are carried out.

Initializes the SYSGEN work area with system parameter values and the name of the site-independent startup command procedure, overwriting existing values. The initial values of the SYSGEN work area when the utility is invoked are the active values.

Specify the source for both the parameter values and the procedure name. They can be retrieved from a parameter file, the current system parameter file on disk, the active system in memory, or the default list.

Format

USE file-spec

Parameters

file-spec

The file specification of a system parameter file from which data is to be retrieved. You can use the SYSGEN command WRITE to create the parameter file. The default file type is .PAR.

In place of a file specification, you can specify one of the following keywords:

CURRENT

Specifies that source information is to be retrieved from the current system parameter file on disk.

On Alpha systems, the system parameter file is SYS$SYSTEM:ALPHAVMSSYS.PAR.

On Integrity servers, the system parameter file is SYS$SYSTEM:IA64VMSSYS.PAR.

ACTIVE

Specifies that source information is to be retrieved from the active system in memory.

DEFAULT

Specifies that source information is to be retrieved from the default list. The USE DEFAULT command initializes the SYSGEN work area with parameter values that are built into SYSGEN; these values allow the operating system to boot on any standard configuration.

To avoid starting all layered products on a system that is not tuned for them, possibly causing the system to hang, set the STARTUP_P1 system parameter as follows:

SYSGEN> SET STARTUP_P1 "MIN"

Qualifiers

None.

Examples

SYSGEN> USE SYS$SYSTEM:SPECIAL
      

This command uses the existing parameter file SYS$SYSTEM:SPECIAL.PAR.

SYSGEN> USE DEFAULT
 
 
SYSGEN> SET STARTUP_P1 "MIN"
      

The first command initializes the SYSGEN work area with default parameter values. The second command sets the STARTUP_P1 system parameter to "minimum."

Writes the system parameter values and the name of the site-independent startup command procedure from the SYSGEN work area to a parameter file, the current system parameter file on disk, or the active system in memory.

Format

WRITE file-spec

Parameters

file-spec

The file specification of a new parameter file to be created. The default file type is .PAR.

In place of a file specification, you can specify one of the following keywords:

CURRENT

Specifies that source information is to be written to the current system parameter file on disk.

On Alpha systems, the system parameter file is SYS$SYSTEM:ALPHAVMSSYS.PAR.

On Integrity servers, the system parameter file is SYS$SYSTEM:IA64VMSSYS.PAR.

Use of the WRITE CURRENT command requires the SYSPRV privilege.

ACTIVE

Specifies that source information is to be written to the active system in memory. (Only the dynamic parameter values are written to the active system.)

Use of the WRITE ACTIVE command requires the CMKRNL privilege.

Qualifiers

None.

Description

On VAX systems, the implementation of security auditing within SYSGEN has altered the reporting of modifications to the system parameter file VAXVMSSYS.PAR. System managers can receive notification of a change to the file by setting up an access control list (ACL) on the file to signal such an event, as in the following example:

$ SET SECURITY/ACL=(ALARM=SECURITY,ACCESS=WRITE+FAILURE+SUCCESS)- _$ SYS$SYSTEM:VAXVMSSYS.PAR

For more information about setting ACLs, see the OpenVMS User's Manual and the HP OpenVMS Guide to System Security.

On Alpha and Integrity servers, both the WRITE ACTIVE and WRITE CURRENT commands send a message to OPCOM and log the event.

Note Prior to Version 7.3-2, enabling SYSGEN audits or alarms did not provided audits or alarms with information about the parameters being modified. Beginning with Version 7.3-2, audits or alarms provide a list of the changed parameters along with their old and new values.

Examples

SYSGEN> WRITE SYS$SYSTEM:SPECIAL
      

This command creates a new parameter specification file, SYS$SYSTEM:SPECIAL.PAR.

SYSGEN> WRITE CURRENT
      

On Alpha systems, this command modifies the current system parameter file on disk, ALPHAVMSSYS.PAR.

On Integrity servers, this command modifies the current system parameter file on disk, IA64VMSSYS.PAR.

The System Management utility (SYSMAN) centralizes the management of nodes and cluster environments. Rather than logging in to individual nodes and repeating a set of management tasks, SYSMAN enables you to define your management environment to be a particular node, a group of nodes, or a cluster environment. With a management environment defined, you can perform system management tasks from your local node. SYSMAN executes these tasks on all nodes in the target environment.

Managing a system with SYSMAN is similar to the traditional management of an individual system because SYSMAN uses many of the same software tools. It can process most DCL commands, such as MOUNT, DEFINE, INITIALIZE, SET, and SHOW. It can also execute many OpenVMS system management utilities and command procedures, such as AUTHORIZE, AUTOGEN, and INSTALL.

SYSMAN also contains system management tools that let you perform the following tasks:

• Set disk quotas using DISKQUOTA commands.
• Load and unload licenses using LICENSE commands.
• Associate a terminal or port with a user name using the automatic login facility (ALF) commands.
• Modify or display System Generation utility (SYSGEN) parameters using PARAMETERS commands.
• Build site-specific startup procedures using STARTUP commands, which display or modify startup components of the OpenVMS operating system, site-specific programs, and layered products.
• Modify or display OpenVMS Cluster parameters using CONFIGURATION commands.
• Load system services using SYS_LOADABLE commands, which add and remove executive loaded images from the set of images loaded at boot time.
• Create and modify scheduling classes, which allow you to limit the amount of CPU time alloted to users on a system.
• Shut down systems using the SHUTDOWN NODE command.
• On Alpha and Integrity servers, detect all previously undiscovered tapes and media changers.
• On Alpha and Integrity servers, connect devices, load device drivers, and display configuration information using I/O commands.
• On Alpha and Integrity servers, set the priority of processes so that they are dumped early during a selective dump.

Instead of having to type lengthy command lines, SYSMAN enables you to define keys to execute SYSMAN commands. For example, you can define a key to execute a SET ENVIRONMENT command as follows:

SYSMAN> DEFINE/KEY/TERMINATE
_Key name: KP0
_Translation: "SET ENVIRONMENT/NODE=(NODE21,NODE22,NODE23)"

Once the key is defined, you can press keypad 0, and SYSMAN executes the SET ENVIRONMENT command. Note that key definitions are lost each time that you exit from SYSMAN, unless you define them in the SYSMAN initialization file. (See Section 24.1.2 for more information about executing commands from an initialization file.)

24.1.2 Executing Commands from an Initialization File

You can create an initialization file that SYSMAN will use each time you invoke the utility. In the SYSMAN initialization file, you can perform tasks such as defining keys and setting the SYSMAN environment.

The default file specification for the SYSMAN initialization file is SYS$LOGIN:SYSMANINI.INI. If you want your SYSMAN initialization file to have a different file specification, you must define the logical name SYSMANINI to point to the location of the file.

The following example is a sample initialization file in which several keys are defined:

$ TYPE SYSMANINI.INI
DEFINE/KEY/TERMINATE KP0 "SET ENVIRONMENT/CLUSTER/NODE=(NODE21,NODE22,NODE23,NODE24)"
DEFINE/KEY/TERMINATE KP1 "CONFIGURATION SHOW TIME"
DEFINE/KEY/TERMINATE KP2 "SHOW PROFILE" 
   .
   .
   .

The System Management utility (SYSMAN) centralizes system management, enabling you to manage nodes or clusters from one location.

Format

RUN SYS$SYSTEM:SYSMAN

Parameters

None.

Description

To invoke SYSMAN, enter the following command at the DCL prompt:

$ RUN SYS$SYSTEM:SYSMAN

SYSMAN displays the following prompt at which you can enter SYSMAN commands using the standard rules of DCL syntax:

SYSMAN>

To exit from SYSMAN and return to the DCL command level, enter the EXIT command at the SYSMAN> prompt or press Ctrl/Z.

Note SYSMAN has the following restrictions: You must have the OPER privilege on the local node and authorization for the OPER or SETPRV privilege on any remote nodes in the management environment. You must also have the privileges required by individual commands, as each command in this chapter describes. To determine which privileges are required for DCL commands or for system management utilities, see the HP OpenVMS DCL Dictionary or the appropriate utility reference part of this manual. You cannot run SYSMAN from a batch job in any environment that requires a password. Some DCL commands, such as SHOW SYSTEM/CLUSTER, SET CLUSTER/QUORUM, MOUNT/CLUSTER, and some forms of the REPLY command, operate clusterwide by design. These commands should not be run using SYSMAN, unless the environment has been set to a single node. Similarly, operations on clusterwide logical names and tables operate clusterwide by design. If a SYSMAN user running with more than 125 total rights attempts to issue a SYSMAN command to a remote node within a cluster, the following error message is displayed: SMI-E-RIGHTSLIM, Rights limit exceeded. Note that this rights limitation includes a minimum of three identifiers that are granted during login when the process rights list is created: A UIC identifier A system identifier Depending upon the environment in which the process is operating, at least one environmental identifier Users who want to run SYSMAN must have either one of the following items: A separate account with no more than 125 rights Enough identifiers removed from their current account so that the total number of rights falls within the appropriate range

This section describes the SYSMAN commands and demonstrates their use. Table 24-1 summarizes each command.