Document revision date: 19 July 1999 | |
Previous | Contents | Index |
On a running Alpha system, frees reserved memory. This command does not affect the contents of the Reserved Memory Registry data file; it affects only the memory with the running system. You can also use RESERVED_MEMORY FREE qualifiers to free a block of contiguous page frame numbers (PFNs).For information about the Reserved Memory Registry, refer to the OpenVMS Alpha Guide to 64-Bit Addressing and VLM Features.
RESERVED_MEMORY FREE gs_name
gs_name
Name of the memory-resident global section associated with this reserved memory. You must specify a name.
/GLOBAL_SECTION (default)
/NOGLOBAL_SECTION
/NOGLOBAL_SECTION indicates that the memory qualifier is for a privileged application instead of a group or system global section. (/GLOBAL_SECTION indicates that the memory qualifier is for a group or system global section.) You cannot use /NOGLOBAL_SECTION with the qualifiers /GROUP, /SYSGBL, or /PAGE_TABLES.AUTOGEN processes the Reserved Memory Registry File in its GETDATA phase. The size of all entries is taken into account when calculating system parameters that depend on the available amount of physical memory.
The reservation size is also used to calculate the initial size of the global page table unless the entry was specified as /NOGLOBAL_SECTION.
/GROUP=n
You must specify /GROUP if the memory-resident global section is a group global section. Do not specify /GROUP if the memory-resident global section is a system global section. The value n is the UIC group number (in octal) associated with the memory-resident being freed.You cannot use the /GROUP qualifier with either /SYSGBL or /NOGLOBAL_SECTION qualifiers.
/SYSGBL
Indicates that a reservation is for a system global, memory-resident section.You cannot combine this qualifier with the /GROUP or /NOGLOBAL_SECTION qualifier. This qualifier is the default unless you specify /GROUP or /NOGLOBAL_SECTION.
If contiguous, aligned physical pages were not pre-allocated during system initialization for this global section, the served memory is simply added to the systems fluid page count. Otherwise, the physical pages are deallocated only the system's free or zeroed page list. The system's fluid page count is adjusted to include the deallocated pages.If page tables are also reserved for the named memory-resident global section, the reserved memory for the shared page tables is also freed.
If the named memory-resident global section is using the reserved memory, the amount of reserved memory not currently in use is freed. The system displays an informational message that indicates if the named global section is using some portion of the reserved memory.
SYSMAN> RESERVED_MEMORY FREE DFW$GS_2 %SMI-S-RMRFREPAG, pages successfully freed from reservation SYSMAN> RESERVED_MEMORY SHOW %SYSMAN-I-OUTPUT, command execution on node PIPERI
|
In this example, the first command frees reserved memory in DFW$GS_2. The second command displays reserved memory in the running system for DFW$GS_3 and DFW$GS_1, but not for DFW$GS_2, which has no reserved memory.
On Alpha systems, allows you to modify an existing entry in the Reserved Memory Registry data file.
RESERVED_MEMORY MODIFY gs_name
gs_name
Name of the memory-resident global section associated with the entry being removed. You must specify a name.
/ALLOCATE
/NOALLOCATE (default)
Allocates contiguous, aligned pages during the next reboot of the system as specified on the command line. (The default is taken from the existing Reserved Memory Registry entry.) The allocated memory is deducted from the system's fluid pagecount, and the creation of the memory-resident global section results in the use of the allocate option. The physical alignment of the pages is based on the maximum granularity hint factor that can be used to map the pages depending on the size of the reserved memory.Possible granularity hint factors are 512 pages (or 4 MB) and 64 pages (or 512 KB). Therefore, assuming an 8-KB system page size, reserved memory is physically aligned as follows:
- size >= 4 MB: physically aligned on a 4-MB boundary
- size < 4 MB: physically aligned on a 512-KB boundary
/NOALLOCATE implies /NOZERO. (/ZERO is incompatible with /NOALLOCATE.) If you specify /NOALLOCATE, or do not specify /ALLOCATE, the reserved memory is not allocated during the next reboot of the system. The reserved memory is deducted only from the system's fluid page count, and the creation of the memory-resident global section results in the use of the fault option.
/GLOBAL_SECTION (default)
/NOGLOBAL_SECTION
/NOGLOBAL_SECTION indicates that the memory qualifier is for a privileged application instead of a group or system global section. (/GLOBAL_SECTION indicates that the memory qualifier is for a group or system global section.) You cannot use /NOGLOBAL_SECTION with the qualifiers /GROUP, /SYSGBL, or /PAGE_TABLES.AUTOGEN processes the Reserved Memory Registry File in its GETDATA phase. The size of all entries is taken into account when calculating system parameters that depend on the available amount of physical memory.
The reservation size is also used to calculate the initial size of the global page table unless the entry was specified as /NOGLOBAL_SECTION.
/GROUP=n
Establishes that the reserved memory is for a group global section. The value n specifies the UIC group number (in octal) of the process that creates the group global section. Only processes within the creator's UIC group number are allowed access to the global section. For example, if a process with the UIC of [6,100] is the creator of the group global section, the group number for the /GROUP qualifier is 6.You cannot use the /GROUP qualifier with either /SYSGBL or /NOGLOBAL_SECTION qualifiers.
/PAGE_TABLES (default)
/NOPAGE_TABLES
Reserves additional memory for shared page tables system as specified on the command line. (The default is taken from the existing Memory Registry.) When the memory-resident global section is created, shared page tables are created for the global section. If you do not specify /ALLOCATE (or if you specify /NOALLOCATE), the additional reserved memory is deducted only from the system's fluid page count. If you specify /ALLOCATE, additional contiguous, during the next reboot of the system, aligned pages are allocated for the shared page table, and the additional reserved memory is deducted from the system's fluid page count.If you do not specify /PAGE_TABLES, or if you specify /NOPAGE_TABLES, additional memory is not reserved for shared page tables. When the memory-resident global section is created, shared page tables are not created for the global section.
You cannot specify /PAGE_TABLES if the reservation has the attribute /NOGLOBAL_SECTION.
/SIZE=[size of reserved memory, unit: MB]
Specifies the number of megabytes to be deducted from the system's fluid page count for this memory-resident global section when the VMS$RESERVED_MEMORY.DATA data file is read during system initialization. The default value for /SIZE is taken from the existing Reserved Memory Registry./SYSGBL
Indicates that a reservation is for a system global memory resident section.You cannot combine this qualifier with the /GROUP or /NOGLOBAL_SECTION qualifier. This qualifier is the default unless you specify /GROUP or /NOGLOBAL_SECTION.
/ZERO
/NOZERO (default)
/ZERO implies /ALLOCATE. If you specify /ZERO, pre-allocated pages are zeroed during system initialization. Zeroed pages are required for memory-resident global sections; however, the pages do not need to be zeroed during system initialization. The default value is taken from existing Reserved Memory Registry entry./NOALLOCATE implies /NOZERO because /ZERO is incompatible with /NOALLOCATE. If you do not specify /ZERO, or if you specify /NOZERO, pre-allocated pages are not zeroed during system initialization. Instead, these pages are zeroed when the global section is created.
The Reserved Memory Registry entry to be modified is identified by the combination of the following items:
- gs_name
- /[NO]GLOBAL_SECTION
- /GROUP=n
- /SYSGBL
The values of these qualifiers are the same as for the RESERVED_MEMORY ADD command.
SYSMAN> RESERVED_MEMORY MODIFY X234567890123456789012345678901/SIZ=2/ZERO $ TYPE SYS$SYSTEM:VMS$RESERVED_MEMORY.DATA
|
The command in this example modifies an entry to reserve 2 MB of memory and to allocate and zero this memory at boot time.
On Alpha systems, removes a reserved memory entry from the Reserved Memory Registry data file. The command does not affect memory within the memory allocation for running systems. You can also use RESERVED_MEMORY REMOVE qualifiers to remove a block of contiguous page frame numbers (PFNs) from the Reserved Memory Registry data file.For information about the Reserved Memory Registry, refer to the OpenVMS Alpha Guide to 64-Bit Addressing and VLM Features.
RESERVED_MEMORY REMOVE gs_name
gs_name
Name of the memory-resident global section associated with the entry being removed. You must specify a name.If page tables are reserved for the named memory-resident global section, the additional reserved memory is also removed.
/GLOBAL_SECTION (default)
/NOGLOBAL_SECTION
/NOGLOBAL_SECTION indicates that the memory qualifier is for a privileged application instead of a group or system global section. (/GLOBAL_SECTION indicates that the memory qualifier is for a group or system global section.) You cannot use /NOGLOBAL_SECTION with the qualifiers /GROUP, /SYSGBL, or /PAGE_TABLES.AUTOGEN processes the Reserved Memory Registry data file in its GETDATA phase. The size of all entries is taken into account when calculating system parameters that depend on the available amount of physical memory.
The reservation size is also used to calculate the initial size of the global page table unless the entry was specified as /NOGLOBAL_SECTION.
/GROUP=n
You must specify /GROUP if the memory-resident global section is a group global section. Do not specify /GROUP if the memory-resident global section is a system global section. The value n is the UIC group number (in octal) associated with the memory-resident section being removed. You cannot use the /GROUP qualifier with either /SYSGBL or /NOGLOBAL_SECTION parameters./SYSGBL
Indicates that a reservation is for a system global memory resident section.You cannot combine this qualifier with the /GROUP or /NOGLOBAL_SECTION qualifier. This qualifier is the default unless you specify /GROUP or /NOGLOBAL_SECTION.
SYSMAN> RESERVED_MEMORY ADD DFW$GS1/SIZE=1 SYSMAN> RESERVED_MEMORY REMOVE DFW$GS1 |
The first command in this example adds DFW$GS1; the second command removes it.
On Alpha systems, displays the memory reservations on the running system. The display includes how much of the reserved memory is currently in use by the named global section. It also includes how much memory is reserved and currently in use for page tables, if any, and the blocks of contiguous page frame numbers (PFNs) reserved.For information about Reserved Memory Registry, refer to OpenVMS Alpha Guide to 64-Bit Addressing and VLM Features.
RESERVED_MEMORY SHOW gs_name
gs_name
Name of the memory-resident global section associated with the entry being displayed within the running system. If you do not specify gs_system, the system displays the reserved memory for all registered global sections.
/GLOBAL_SECTION (default)
/NOGLOBAL_SECTION
/NOGLOBAL_SECTION indicates that the memory qualifier is for a privileged application instead of a group or system global section. (/GLOBAL_SECTION indicates that the memory qualifier is for a group or system global section.) You cannot use /NOGLOBAL_SECTION with the qualifiers /GROUP, /SYSGBL, or /PAGE_TABLES.AUTOGEN processes the Reserved Memory Registry data file in its GETDATA phase. The size of all entries is taken into account when calculating system parameters that depend on the available amount of physical memory.
The reservation size is also used to calculate the initial size of the global page table unless the entry was specified as /NOGLOBAL_SECTION.
/GROUP=n
You must specify /GROUP if the memory-resident global section is a group global section. Do not specify /GROUP if the memory-resident global section is a system global section. The value n is the UIC group number (in octal) associated with the memory-resident section being displayed. You can use the /GROUP qualifier only if you specify gs_name. You cannot use the /GROUP qualifier with either /SYSGBL or /NOGLOBAL_SECTION parameters./SYSGBL
Indicates that a reservation is for a system global memory resident section.You cannot combine this qualifier with the /GROUP or /NOGLOBAL_SECTION qualifier. This qualifier is the default unless you specify /GROUP or /NOGLOBAL_SECTION.
SYSMAN> RESERVED_MEMORY SHOW %SYSMAN-I-OUTPUT, command execution on node PIPER Name Pages In Use Group PTs Alloced Zeroed DFW$GS_3 384 0 SYSGBL No No No DFW$GS_2 256 0 SYSGBL No Yes Yes DFW$GS_1 128 0 00000100 No No No DFW$GS_3 1 0 SYSGBL Yes No No DFW$GS_2 1 0 SYSGBL Yes Yes No |
The command in this example displays the memory reservations on a running system.
Defines the nodes or cluster to which subsequent commands apply.Requires OPER or SETPRV privilege on all nodes in the target environment.
SET ENVIRONMENT
None.
/CLUSTER
Specifies that all subsequent commands apply to all nodes in the cluster. By default, the management environment is the local cluster. Specify a nonlocal cluster by naming one cluster member with the /NODE qualifier./NODE=(node1,node2,...)
Specifies that SYSMAN execute subsequent commands on the given DECnet nodes. If accompanied by the /CLUSTER qualifier, the environment becomes the cluster where the given DECnet node is a member. A node name can be a system name, cluster alias, or logical name. However, before you can use logical names to define the command environment, you must set up the logical name table SYSMAN$NODE_TABLE. For more information about defining the SYSMAN logical name table, refer to the OpenVMS System Manager's Manual./USERNAME=username
Specifies that this user name should be used for access control purposes on another node. You can use this qualifier only in conjunction with the /CLUSTER or /NODE qualifiers. SYSMAN uses the current user name if none is supplied. SYSMAN prompts for a password whenever you specify a new user name.
Note
The account specified must have only a primary password. Accounts with secondary passwords are not supported.
The SET ENVIRONMENT command defines the target nodes or cluster for subsequent commands. When invoked, the system management environment is the local node where you are running SYSMAN. You can change the environment to any other nodes in the cluster, the entire cluster, or any nodes or cluster available through DECnet.Designate an OpenVMS Cluster environment with the /CLUSTER qualifier. When specifying a nonlocal cluster, also include the /NODE qualifier to identify the cluster.
If your environment consists of VAX and Alpha nodes, see the DO command for information about creating logicals to manage each platform as an environment.
You can display the current environment with the command SHOW ENVIRONMENT. To adjust privileges and defaults for the current environment, use the SET PROFILE command.
An environment exists until you exit from SYSMAN or establish another command context with the SET ENVIRONMENT command.
#1 |
---|
SYSMAN> SET ENVIRONMENT/CLUSTER %SYSMAN-I-ENV, Current command environment: Clusterwide on local cluster Username ALEXIS will be used on nonlocal nodes |
This command defines the command environment as the local cluster. SYSMAN confirms the new environment.
#2 |
---|
SYSMAN> SET ENVIRONMENT/NODE=NODE21/CLUSTER Remote Password: %SYSMAN-I-ENV, Current command environment: Clusterwide on remote node NODE21 Username ALEXIS will be used on nonlocal nodes |
This command establishes a management environment on the cluster where NODE21 is a member. SYSMAN prompts for a password because it is a nonlocal environment.
#3 |
---|
SYSMAN> SET ENVIRONMENT/NODE=(NODE21,NODE22,NODE23) %SYSMAN-I-ENV, Current command environment: Individual nodes: NODE21,NODE22,NODE23 Username ALEXIS will be used on nonlocal nodes |
This command defines the management environment to be three individual nodes.
#4 |
---|
$ CREATE/NAME_TABLE/PARENT=LNM$SYSTEM_DIRECTORY - _$ SYSMAN$NODE_TABLE $ DEFINE LAVCS SYS1,SYS2,SYS3,SYS4/TABLE=SYSMAN$NODE_TABLE $ RUN SYS$SYSTEM:SYSMAN SYSMAN> SET ENVIRONMENT/NODE=(LAVCS) %SYSMAN-I-ENV, Current command environment: Individual nodes: SYS1,SYS2,SYS3,SYS4 Username ALEXIS will be used on nonlocal nodes |
The commands in this example set up the logical name table SYSMAN$NODE_TABLE, define a logical name (LAVCS), and use the logical name to define the command environment.
Temporarily modifies a user's current privileges and default device and directory.
SET PROFILE
None.
/DEFAULT=device:[directory]
Specifies the default disk device and directory name that the system should use in this environment to locate and catalog files./PRIVILEGES=(priv1,priv2...)
Specifies the privileges to add to the current privileges. Any enhanced privileges must be authorized./VERIFY
/NOVERIFY (default)
Specifies whether you want DCL verification (both procedure and image) for future DO commands.
The SET PROFILE command modifies process attributes for the current management environment. After considering the privilege requirements of commands that you intend to use in an environment, you can add or delete current privileges, if they are authorized. You can also set a new default device and directory, as well as use the SET PROFILE/[NO]VERIFY command to control DCL command verification in SYSMAN. Other attributes of your process remain constant. The profile is in effect until you change it, reset the environment, or exit from SYSMAN. The OpenVMS System Manager's Manual discusses profile changes in more detail.
#1 |
---|
SYSMAN> SET PROFILE/DEFAULT=WORK1:[ALEXIS] |
This command changes the default device and directory in the user account to directory ALEXIS on device WORK1.
#2 |
---|
SYSMAN> SET PROFILE/PRIVILEGES=(SYSPRV,CMKRNL)/VERIFY |
This command makes the authorized privileges, SYSPRV and CMKRNL, part of the current privileges, and turns on DCL verification. The privileges remain in effect until the environment changes, you enter another SET PROFILE command, or you exit.
Previous | Next | Contents | Index |
privacy and legal statement | ||
6048PRO_070.HTML |