skip book previous and next navigation links
go up to top of book: HP OpenVMS Alpha Partitioning and Galaxy Guide HP OpenVMS Alpha Partitioning and Galaxy Guide
go to beginning of chapter: Galaxy and NUMA Commands and Lexicals Galaxy and NUMA Commands and Lexicals
go to previous page: Galaxy-Related DCL Lexical Functions Galaxy-Related DCL Lexical Functions
go to next page: Communicating With Shared MemoryCommunicating With Shared Memory
end of book navigation links

DCL Command Examples  



The DCL commands and lexical functions in this section are useful for managing an OpenVMS Galaxy. They are described with examples in the following order:

These commands are described in the following sections.

CPU Commands  

CPUs are assignable resources in an OpenVMS Galaxy. You can assign CPUs using either the Physical Structure chart (see Physical Structure Chart ) or the STOP/CPU/MIGRATE command ( STOP/CPU/MIGRATE).

STOP/CPU/MIGRATE  

The STOP/CPU/MIGRATE command transfers ownership of the CPU from the current instance to another soft partition.

For example, enter:

$ STOP/CPU/MIGRATE=GLXSYS  4
In this example, GLXSYS can be an instance name or a partition ID value. No operating system is required to be running at the target.

The following message is displayed at the terminal:

%SYSTEM-I-CPUSTOPPING, trying to stop CPU 4 after it reaches quiescent 
state
The source console displays:
%SMP-I-STOPPED, CPU #04 has been stopped.
The destination console displays:
%SMP-I-SECMSG, CPU #04 message:   P04>>>START
%SMP-I-CPUTRN, CPU #04 has joined the active set.

SHOW CPU  

The SHOW CPU command displays information about the status, characteristics, and capabilities of the specified processors. For example:

$ show cpu
 
System: GLXSYS, Compaq AlphaServer GS320 6/731
 
CPU ownership sets:
   Active               0-31
   Configure            0-31
 
CPU state sets:
   Potential            0-31
   Autostart            0-31
   Powered Down         None
   Failover             None
 
$ show cpu/system
 
System: GLXSYS, Compaq AlphaServer GS320 6/731
 
  SMP execlet   = 2 : Enabled : Full checking.
  Config tree   = Version 6
  Primary CPU   = 0
  HWRPB CPUs    = 32
  Page Size     = 8192
  Revision Code =
  Serial Number = BUDATEST
  Default CPU Capabilities:
        System: QUORUM RUN
  Default Process Capabilities:
        System: QUORUM RUN
 
CPU ownership sets:
   Active               0-31
   Configure            0-31
 
CPU state sets:
   Potential            0-31
   Autostart            0-31
   Powered Down         None
   Failover             None

SET CPU  

The SET CPU command changes the user capabilities associated with the specified CPUs.

In the following commands, n represents the CPU number, a comma-separated list of CPUs, or the /ALL qualifier.

SHOW MEMORY  

The SHOW MEMORY command displays the uses of memory by the system. For example:

$ SHOW MEMORY/PHYSICAL
 
            System Memory Resources on 5-OCT-2001 20:50:19.03
 
Physical Memory Usage (pages):     Total        Free      In Use    Modified
   Main Memory (2048.00Mb)        262144        228183    31494      2467
Of the physical pages in use, 11556 pages are permanently allocated to OpenVMS.
 
$ SHOW MEMORY/PHYSICAL
 
              System Memory Resources on 5-OCT-2001 07:55:14.68
 
Physical Memory Usage (pages):     Total        Free      In Use    Modified
   Private Memory (512.00Mb)       65536        56146      8875         515
   Shared Memory (1024.00Mb)       131072       130344      728
 
Of the physical pages in use, 6421 pages are permanently allocated to OpenVMS.
$

Lexical Function Example  

A lexical function is a function that returns information about character strings and attributes of the current process. The following command procedure uses the F$GETSYI lexical function to create a command procedure to show you the attributes of a Galaxy system:

Lexical Function Example Command Procedure

$ create shoglx.com
$ write sys$output ""$ write sys$output "Instance = ",f$getsyi("scsnode")
$ write sys$output "Platform = ",f$getsyi("galaxy_platform")
$ write sys$output "Sharing Member = ",f$getsyi("galaxy_member")
$ write sys$output "Galaxy ID = ",f$getsyi("galaxy_id")
$ write sys$output "Community ID = ",f$getsyi("community_id")
$ write sys$output "Partition ID = ",f$getsyi("partition_id")
$ write sys$output ""$ exit
$ ^Z

Lexical Function Command Procedure Output

$ @SHOGLX
 
Instance = COBRA2
Platform = 1
Sharing Member = 1
Galaxy ID = 5F5F30584C47018011D3CC8580F40383
Community ID = 0
Partition ID = 0
 
$

INSTALL LIST  

The INSTALL LIST command now returns all of the Galaxy sections as well as standard global sections.

INSTALL ADD/WRITABLE  

The INSTALL ADD/WRITABLE command now supports Galaxy sections as well as standard global sections. INSTALL ADD/WRITABLE=GALAXY installs the specified file as a writable known image in a Galaxy global section.

CONFIGURE GALAXY  

The CONFIGURE GALAXY command invokes the Galaxy Configuration Utility (GCU) to monitor, display, and interact with an OpenVMS Galaxy system. The GCU requires DECwindows Motif Version 1.2-4 or higher and OpenVMS Alpha Version 7.2 or higher.

The optional model parameter specifies the location and name of a Galaxy Configuration Model to load and display. If no model is provided and the system is running as an OpenVMS Galaxy, the current active configuration is displayed.

If the system is not running as an OpenVMS Galaxy, the GCU will assist the user in creating a single-instance OpenVMS Galaxy system.

OpenVMS Galaxy Configuration Models are created using either the Galaxy Configuration Utility (GCU) or the Graphical Configuration Manager (GCM). See the GCU or GCM online help for more information.

Format:

CONFIGURE GALAXY [model.GCM]

Parameter:

GALAXY [model.GCM]
Specifies the location and name of a Galaxy configuration model to load and display.

If no model is provided and the system is running as an OpenVMS Galaxy, the current active configuration is displayed.

Qualifiers:

/ENGAGE

Causes the GCU to engage (load, validate, and activate) the specified OpenVMS Galaxy Configuration Model without displaying the graphical user interface. After validation, the specified model becomes the active system configuration.

This qualifier allows system managers to restore the OpenVMS Galaxy system to a known configuration, regardless of what dynamic resource reassignments may have occurred since the system was booted. This command can be embedded in DCL command procedures to automate configuration operations.

/VIEW

When used in conjunction with /ENGAGE and a model parameter, causes the GCU to load, validate, activate, and display the specified configuration model.

Examples:

$ CONFIGURE GALAXY
Displays the GCU's graphical user interface. If the system is currently configured as an OpenVMS Galaxy, the active system configuration is displayed.
$ CONFIGURE GALAXY model.GCM
Displays the GCU's graphical user interface. The specified OpenVMS Galaxy Configuration Model is loaded and displayed, but does not become the active configuration until the user chooses to engage it.
$ CONFIGURE GALAXY/ENGAGE model.GCM
Invokes the GCU command-line interface to engage the specified OpenVMS Galaxy Configuration Model without displaying the GCU's graphical user interface.
$ CONFIGURE GALAXY/ENGAGE/VIEW model.GCM
Invokes the GCU command-line interface to engage the specified OpenVMS Galaxy Configuration Model and display the GCU's graphical user interface.
go to previous page: Galaxy-Related DCL Lexical Functions Galaxy-Related DCL Lexical Functions
go to next page: Communicating With Shared MemoryCommunicating With Shared Memory