f- OpenVMS FAQ -&- page 8)b @5z

HP OpenVMS Systems Documentation

 q> $"b,
Content starts here"D

The OpenVMS Frequently Asked Questions (FAQ)


 l n  
PreviousContentsIndex

p

5.8 Why doesn't OpenVMS see the new memory I just added?



@When adding memory to an OpenVMS system, you should check for anexisting@definition of the PHYSICALPAGES (OpenVMS VAX) or PHYSICAL_MEMORYC(OpenVMS Alpha) parameter in the SYS$SYSTEM:MODPARAMS.DAT parameterEdatabase, use a text editor to reset the value in the file to the newBcorrect value as required, and then perform the following command:

 

"
-$ @SYS$UPDATE:AUTOGEN GETDATA REBOOT FEEDBACK




BThis AUTOGEN command will reset various system parameters based onCrecent system usage (FEEDBACK), and it will reset the value for theAPHYSICALPAGES parameter to the new value. It will also reboot theOpenVMS system.

BPHYSICALPAGES and PHYSICAL_MEMORY can also be used to deliberatelyElower the amount of memory available for use by OpenVMS. This abilityBcan be useful in a few specific circumstances, such as testing theEbehaviour of an application in a system environment with a particular*(lower) amount of system memory available.

EPHYSICALPAGES and PHYSICAL_MEMORY can be set to -1 (on OpenVMS Alpha)Gor (better and simpler) the entry can be removed from the MODPARAMS.DAT;file, to indicate that all available memory should be used.p

5.9 How do I change the text in a user's UIC identifier?



GThe text translations of the numeric User Identification Code (UIC) areEbased on identifiers present in the OpenVMS rightslist. DocumentationBon this area is included in the _Guide to OpenVMS System Security_manual.

ETo control the identifiers shown for a user's UIC, you use AUTHORIZE.?Each user has an associated group identifier, and an identifier=specific to the user. And each user should have a unique UIC.

FTo alter the text of a user or group identifier, use commands such as:

 

"
$ RUN SYS$SYSTEM:AUTHORIZE*UAF> rename/ident oldgroupid newgroupid)UAF> rename/ident olduserid  newuserid




BIf you should find yourself missing an identifier for a particularAuser, you can add one for the user's UIC using a command such as:

 

"
2UAF> add/ident/value=uic=[group,user] newuserid




FThe UIC user identifier text is assigned when the username is created,Band is the text of the username. The UIC group group identifier isEassigned when the first username is created in the UIC group, and theFtext is based on the account name specified for the first user createdGin the group. The value of this identifier is [groupnumber, 177777]. To;add a missing group identifier, use an asterisk as follows:

 

"
0UAF> add/ident/value=uic=[group,*] newgroupid




GYou may find cases where an identifier is missing from time to time, asGthere are cases where the creation of a UIC group name identifier mightGconflict with an existing username, or a user identifier might conflictBwith an existing group identifier. When these conflicts arise, theCAUTHORIZE utility will not create the conflicting group and/or user(identifier when the username is created.

EYou can can add and remove user-specified identifiers, but you should>avoid changing the numeric values associated with any existingGidentifiers. You should also avoid reusing UICs or identifiers when youCadd new users, as any existing identifiers that might be present onEobjects in the system from the old user will grant the same access to9the new user. Please see the security manual for details.h

5.10 What are the OpenVMS version upgrade paths?

P

5.10.1 OpenVMS Alpha Upgrade (or Update) Paths





/  
Note

FUpgrade path information here has occasionally been found to be wrong.GInformation here does not reflect cluster rolling upgrade requirements;see Section 5.10.4 for related rolling upgrade information; versionsGpermissible for rolling upgrades can be and often are more constrained.9When upgrade information here conflicts with the official@documentation, please assume that the information here is wrong.=Corrections and updates to this material are welcome.


 

"
From V1.0,    you can upgrade to V1.5.From V1.5, or V1.5-1H1,    you can upgrade to V6.1.
From V6.1,    you can upgrade to V6.2.From V6.1, or V6.2,    you can upgrade to V7.0.)From V6.1, V6.2, V6.2-1H(1,2,3), or V7.0,    you can upgrade to V7.1.
From V6.2,6    you can update to V6.2-1H1, V6.2-1H2, or V6.2-1H3.7From V6.2, V6.2-1H(1,2,3), V7.1, V7.1-1H(1,2), or V7.2,    to V7.2-1.From V6.2, ... or V7.2,    to V7.2-1H1, to 7.3..From V7.1, you can update to V7.1-1H(1,2), ...    to V7.2-1H1, to 7.3..From 7.2, 7.2-1, 7.2-1H1, 7.2-2, 7.3 or 7.3-1,    you can upgrade to V7.3-20From V7.3, V7.2-2, V7.2-1H1, V7.2-1, and V7.1-2,    you can upgrade to V7.3-1From V7.3-1,)    you can upgrade to V7.3-2 or to V8.2.From V7.3-1 or V7.3-2,    you can upgrade to V8.2.




9Some typical OpenVMS Alpha upgrade (or update) paths are:

 

"
?V1.0 -> V1.5 -> V6.1 -> (V6.2, V7.0, V7.1, V7.2, V7.3)8V1.5-1H1 -> V6.1 -> (V6.2, V7.0, V7.1, V7.2, V7.3)V6.2 -> V6.2-1H3V6.2 -> V7.2-1V6.2 -> V7.3V6.2-1H(1,2,3) -> V7.1V6.2-1H(1,2,3) -> V7.2-1)V6.2 through 7.1-1H2 inclusive -> V7.3V7.1 -> V7.1-2V7.1 -> V7.2-1V7.1-1H(1,2) -> V7.1-2V7.1-1H(1,2) -> V7.2-1V7.1-2 -> V7.3-1V7.2 -> V7.2-1H1V7.2 -> V7.3 -> V7.3-1V7.2-1 -> (V7.3, V7.3-1)#V7.2-2 -> (V7.3, V7.3-1, V7.3-2)V7.3 -> (V7.3-1, V7.3-2)V7.3-1 -> (V7.3-2, V8.2)V7.3-2 -> V8.2




BNote that OpenVMS Alpha V7.0 does not include support for hardware@and/or configurations first supported in OpenVMS Alpha V6.2-1H1,HV6.2-1H2, or V6.2-1H3; one must upgrade to OpenVMS Alpha V7.1, or later.

GOne cannot update directly to a V6.2-1Hx Limited Hardware Release (LHR)=from any release prior to the baseline V6.2 release. The sameFprohibition holds for performing updates directly to V7.1-1Hx from anyGrelease prior to V7.1---this is not supported, and does not produce theGexpected results. The LHR kits can, however, be directly booted and canBbe directly installed, without regard to any operating system that$might be present on the target disk.

EUsers of OpenVMS Alpha V7.1-1H1, V7.1-1H2, V7.2-1H1 or other hardwareEare encouraged to upgrade to the next available non-hardware-release,Fand should preferably upgrade to the current or to a supported OpenVMSAlpha release.

DOpenVMS Alpha updates for LHRs (through V7.1-1Hx) require the use of=VMSINSTAL for the update. These LHR releases use PCSI for theCinstallation, but not for the update. Non-LHR releases use PCSI forinstalls and upgrades.

@OpenVMS Alpha V7.1-2 and later use PCSI for LHRs and for OpenVMSDupgrades and for all OpenVMS ECO kit installations; V7.1-2 and laterFuse upgrades and not updates. VMSINSTAL OpenVMS ECO kits (updates) are<not used on OpenVMS Alpha V7.1-2 and later; prior to V7.1-2,7VMSINSTAL-based ECO (update) kits are used for OpenVMS.@

5.10.2 OpenVMS I64 Upgrade Paths





/  
Note

FUpgrade path information here has occasionally been found to be wrong.GInformation here does not reflect cluster rolling upgrade requirements;see Section 5.10.4 for related rolling upgrade information; versionsGpermissible for rolling upgrades can be and often are more constrained.9When upgrade information here conflicts with the official@documentation, please assume that the information here is wrong.=Corrections and updates to this material are welcome.


 

"
	From V8.2    you can upgrade to V8.2-1




7Some typical OpenVMS I64 upgrade (or update) paths are:

 

"
V8.2 -> V8.2-1




FOpenVMS I64 V8.2 is the first production release. OpenVMS I64 V8.0 andFV8.1 were intended for early adopters of OpenVMS on Integrity servers,1and are not considered to be production releases.

DTo utilize OpenVMS I64 V8.2, you must perform a full installation ofBV8.2. No supported upgrade path to V8.2 is available from previousAreleases; there is no upgrade from OpenVMS I64 E8.2, nor from theearlier V8.1 or V8.0 releases.H

5.10.3 OpenVMS VAX Release Upgrade Paths





/  
Note

FUpgrade path information here has occasionally been found to be wrong.GInformation here does not reflect cluster rolling upgrade requirements;see Section 5.10.4 for related rolling upgrade information; versionsGpermissible for rolling upgrades can be and often are more constrained.9When upgrade information here conflicts with the official@documentation, please assume that the information here is wrong.=Corrections and updates to this material are welcome.


 

"
<From V5.0 through V5.4-3 inclusive, one can upgrade to V5.5.:From V5.5, V5.5-1, or V5.5-2HW, one can upgrade to V5.5-2.6From V5.5, V5.5-1, or V5.5-2, one can upgrade to V6.0.8From V5.5-2, V5.5-2H4, or V6.0, one can upgrade to V6.1.,From V6.0, or V6.1, one can upgrade to V6.2.,From V6.1, or V6.2, one can upgrade to V7.0.2From V6.1, V6.2, or V7.0, one can upgrade to V7.1.?From V6.1, one can upgrade to V7.3 (with VAXBACK ECO for V6.1).




+Some typical OpenVMS VAX upgrade paths are:

 

"
>V5.x -> V5.5 -> V6.0 -> V6.2 -> (V7.1, V7.2, V7.3)V5.5-2HW -> V5.5-2:V5.5-2, or V5.5-2H4 -> V6.1 -> (V6.2, V7.0, or V7.1)3V6.1 -> V6.1 with VAXBACK ECO -> (V7.2, V7.3)V6.2 -> V7.2V6.2 -> V7.3




GNote that OpenVMS VAX V6.0 does not include support for hardware and/orGconfigurations first added in OpenVMS VAX V5.5-2H4, one must upgrade toOpenVMS VAX V6.1.

FNote that OpenVMS VAX V5.5-2HW is a pre-release version of V5.5-2. Any9system running it should be upgraded to V5.5-2, or later.

FIf you attempt a direct upgrade from OpenVMS VAX V6.1 to V7.2 or laterEwithout having first applied the VAXBACK ECO kit to your V6.1 system,"you will receive an error message:

 

"
4%BACKUP-E-INVRECTYP, invalid record type in save set




Dand the upgrade will fail. Acquire and apply the VAXBACK ECO kit for>OpenVMS VAX V6.1. OpenVMS VAX V6.2 and later do not require an7application of an ECO for an upgrade to V7.2 and later.T

5.10.4 OpenVMS Cluster Rolling Upgrade Paths



CRolling Upgrades permit the OpenVMS Cluster and the applications toEremain available while individual systems are being upgraded to a newOpenVMS release.

/Rolling Upgrades require multiple system disks.

COpenVMS Cluster Rolling Upgrades for OpenVMS Alpha, OpenVMS I64 and@OpenVMS VAX may (will) have architecture-specific, or additionalCupgrade requirements or prerequisites, and have requirements around@which versions and architectures of OpenVMS can coexist within a*OpenVMS Cluster than what are listed here.

@For specific details on Rolling Upgrades, please see the OpenVMSCUpgrade and Installation Manual for the particular release, and theAOpenVMS Software Product Descriptions for OpenVMS and for OpenVMSCluster software:



Hfor further details on the Rolling Upgrade, and for support information.I

5.10.5 OpenVMS VAX Manual Organization



DThe documentation for older releases of OpenVMS VAX was comprised ofDvarious platform-specific manuals, manuals that include instructionsCthat are specific to installing and upgrading on the particular VAX-Eplatform. These older manuals can be useful for learning platform- oriCconsole-specific operations or requirements for the particular (anduolder) VAX platform.

rCThere is far less console command syntax, and console storage mediadFvariability, among the more recent Alpha and Integrity processors. The>newer platform operator and management interfaces are far more%consistent across the platform lines./U

5.10.6 OpenVMS Product Version and Support Information

f

a.For information on Prior Version Support (PVS)and Mature Product SupportC(including information on support end dates for OpenVMS and various>Elayered products), please see the support resources link available at=Dthe main OpenVMS website or the services links available at the mainservices website:

n

e<And see the following links, with the caveat that the direct3"/hps" links shown here may become stale:a

a

lAFor information on the supported and required versions of layeredGproducts, and the minimum required layered product versions for variouse@configurations, please see the Software Rollout Report (SWROLL), available at:

x

>qFor additional related information, see Section 2.6.1. 

e<For information on the release history of OpenVMS, including?information on the code names of various releases and the majora features:i

D

OEAdditional release history information, as well as a variety of otherA6trivia, is available in the VAX 20th anniversary book:

S

5.10.7 OpenVMS Alpha and I64 Upgrade Terminology

o

yAOpenVMS Alpha and OpenVMS I64 use the POLYCENTER Software ProductwGInstall Utility, occasionly refered to as SPIU and rather more commonly Gknown as PCSI. PCSI is a component of the OpenVMS operating system, andr<is available on OpenVMS VAX, OpenVMS Alpha, and OpenVMS I64.

FThe following terms apply to OpenVMS Alpha and to OpenVMS I64 Upgradesand Installations using PCSI: 

  • UPDATE:aFTypically used for Limited Hardware Releases (LHR) releases. PerformedBvia VMSINSTAL. Applies only to the OpenVMS release that the LHR isBbased on, or to an intermediate LHR. (eg: V7.1-1H2 applies only toFV7.1-1H1 and to V7.1, not to any other releases.) LHRs within a seriesEare cumulative, containing all files and features of previous LHRs in Dthe same series.
    VMSINSTAL-based Updates and VMSINSTAL-based ECOEkits are not generally used to upgrade OpenVMS on releases of OpenVMS >Alpha V7.1-2 and later, nor are thse used on OpenVMS I64; onlyFPCSI-based Upgrades and Installs are used. VMSINSTAL remains availableDfor other uses and other products; for upgrades and installations of#products other than OpenVMS itself.
  • UPGRADE:CPerformed via PCSI. Upgrades can typically be applied directly to aoGrelease-specific range of earlier OpenVMS releases. The product releaselFdocumentation specifies the prior OpenVMS releases; if your release isGnot one of the specified releases, you will have to perform one or moreDadditional upgrades (through intermediate OpenVMS releases) to reach!one of the prerequisite releases.m
  • INSTALL:DPerformed via PCSI. With an installation, no existing version of theGoperating system is assumed present, nor are any files from any copy of ?the operating system might be present preserved, and the entire Dcontents of the target disk are destroyed via a disk initialization.I
  • PRESERVE: Performed via PCSI. Otherwise similar to an installation,hG this option skips the disk reinitialization. User files on the targetrG disk are preserved. Any existing operating system files on the target  disk are clobbered.l
  • LHR:FLimited Hardware Release. LHRs are specific to and are targeted at newFhardware configurations, and are not shipped to customers with supportBcontracts. At least one LHR kit must be specifically acquired whenDpurchasing new hardware, new hardware that is not (yet) supported byAany mainline (non-LHR) release. LHRs have an "H" in thegBOpenVMS version string, indicating a "Hardware" release.?
    You will not generally want to continue using an LHR once aeEsubsequent OpenVMS release is available; you will want to upgrade offc%the LHR at your earliest convenience.i
i

nyFor minimum OpenVMS versions for various platforms, see Section 2.12.e~

5.11 Why do I have a negative number in the pagefile reservable pages?



sDSeeing a negative number in the reservable pages portion of the SHOW=MEMORY/FULL command can be normal and expected, and is (even)/Edocumented behaviour. A pagefile with a negative number of reservableMGpages is overcommitted, which is generally goodness assuming that everylFprocess with reserved pages does not try to occupy all of the reserved pagefile space at the same time.

nETo understand how the pagefile reservation process works, think aboutaDhow a traditional bank operates when accepting customer deposits andGmaking loans. It's the same idea with the pagefile space. There is lesslDmoney in the bank vault than the total deposits, because much of theAmoney has been loaned out to other customers of the bank. And thenDbehaviour parallels that of the pagefile down to the problems that aD"run on the bank" can cause for banking customers. (Though<there is no deposit insurance available for pagefile users.)

EIf all of the running applications try to use the reserved space, therCsystem manager will need to enlarge the pagefile or add one or more additional pagefules.o

DTo determine if the pagefile is excessively overcommitted, watch for="double overcommitment"---when the reservable space Gapproaches the negatation of the available total space---and watch that@the total amount of free space available in the pagefile remainsCadequate. If either of these situations arises, additional pagefiletstorage is required.

-FAdditional pagefile information: Additional pagefiles can typically beDcreated and connected on a running OpenVMS system. New processes and@new applications will tend to use the new pagefile, and existingBapplications can be restarted to migrate out of the more congestedCpagefiles. Pagefiles are generally named PAGEFILE.SYS, and multipleaFpagefiles are generally configured on separate disk spindles to spreadDthe paging I/O load across the available disk storage. When multipleDpagefiles are present on recent OpenVMS versions, each pagefile fileCshould be configured to be approximately the same total size as thelother pagefiles.

>GFor additional information on pagefile operations and related commands,6Csee the system management and performance management manuals in theVOpenVMS documentation set.

HEWith OpenVMS V7.3 and later, the displays have been changed and these6&negative values are no longer visible.x

5.12 Do I have to update layered products when updating OpenVMS?



;DThe Software Public Rollout Reports for OpenVMS list the current andCfuture availability of HP software products shipping on the OpenVMSGSoftware Products Library kits (CDROM consolidations) for OpenVMS AlphalCand/or OpenVMS VAX. Specifically, the required minimum versions for product support are listed.n

BComprehensive Public Rollout Information, listing previous productGversions as well as currently shipping versions, has been compiled intoeEa separate set of reports. The product information is grouped to showiOperating System support.e

eGYou may or may not be able to use older versions of local applications,mGthird-party products, and various HP OpenVMS layered products with more Crecent versions of OpenVMS. User-mode code is expected to be upward Ecompatible. Code executing in a privileged processor mode---typically Ceither executive or kernel mode---may or may not be compatible withAmore recent OpenVMS versions.H

hEThese Software Rollout (SWROLL) Reports are updated regularly. Pleaseasee:

1

efFor related information, see Section 2.6.1.h

5.13 How do I change the volume label of a disk?



SDDismount the disk, and mount it privately. If the disk is mounted byDmore than one node in an OpenVMS Cluster, dismount it from all otherBnodes. If this disk is an OpenVMS system disk, shut down all other+nodes that are bootstrapped from this disk.O

=Issue the SET VOLUME/LABEL command, specifying the new label.>

aDOn OpenVMS V6.0 and later, issue the following PCSI command to resetDthe label information stored within the PCSI database to reflect thenew disk volume label:

> 
a
"
*$ PRODUCT REGISTER VOLUME old-label device

n


mDLocate any references in the system startup (typically including theAdisk MOUNT commands) and any DISK$label references in applicationn/files, and change the references appropriately.f

FIf this is a system disk (for the host or for a satellite), also checkGthe DECnet MOP or LANCP boot database, as well as any references to the$disk created by CLUSTER_CONFIG*.COM.

wDIf Compaq Analyze is in use, check the system startup procedures forGthe Compaq Analyze tool. Certain versions of Compaq Analyze will recordn:specific disk volume labels within the startup procedures.

VRemount the disk appropriately.-a

5.14 How can I set up a shared directory?

p

tGTo set up a shared directory---where all files created in the directory>Gare accessible to the members of specified group of users---you can use2/an access control list (ACL) and an identifier.0

8CThe following also shows how to set up a resource identifier, which@further allows the disk resources to be charged to the specifiedEidentifier rather than each individual user. (If you don't want this,oGthen omit the attributes option on the identifier creation and omit ther'entry added in the disk quota database.r

h.Add an identifier using the AUTHORIZE utility:

" 
p
"
1ADD/IDENTIFER/ATTRIBUTES=RESOURCE groupidentifier

r


r 
m
"
)GRANT/IDENTIFIER groupidentifier usernameh

t


eAIf disk quotas are in use, add an entry via SYSMAN for each disk:i

e 
n
"
DISKQUOTA ADD groupidentifier -t)  /PERMQUOTA=pq/OVERDRAFT=od/DEVICE=ddcu:e

c


FSet the shared directory to have an ACL similar to the following usingEthe SET SECURITY (V6.0 and later) or SET ACL (versions prior to V6.0)>command:

= 
<
"
&(DEFAULT_PROTECTION,S:RWED,O:RWED,G,W)-(IDENTIFIER=groupidentifier,OPTIONS=DEFAULT,-.#  ACCESS=READ+WRITE+EXECUTE+DELETE) (IDENTIFIER=groupidentifier, -#  ACCESS=READ+WRITE+EXECUTE+DELETE)r)(CREATOR,ACCESS=READ+WRITE+ACCESS+DELETE)

2


?If there are files already resident in the directory, set theirmDprotections similarly. (The OPTIONS=DEFAULT, DEFAULT_PROTECTION, and#CREATOR ACEs apply to directories.)c

VAThe default protection mask is used to establish the default filetAprotection mask, this mask does not prevent the users holding theeAspecified groupidentifier from accessing the file(s), as they can.Caccess the file via the explicit identifier granting access that is2present in the ACL.1

VEFor further information, see the OpenVMS Guide to System SecurityVCManual, specifically the sections on ACLs and identifiers, anddresource identifiers. r

s


 i Sl n  b
PreviousNextContentsIndex

 

#b6l D :FILELIST.XML;BEAVIS DISK$WEB3 .2CB(y筗KK/ M):MASTER03_IMAGE002.GIF;BEAVIS DISK$WEB3 .2CB(y筗LL/ =J3.GIF;BEAVIS DISK$WEB3 .2CB(y筗MM/ =J4.GIF;BEAVIS DISK$WEB3 .2CB(y筗NN/ =J5.GIF;BEAVIS DISK$WEB3 .2CB(y筗2CB(y筗 A/NP; QG ; c.HTDOCS.PRESENTATIONS.CETS2001.CETS2001-1884_VMSIPF_FILES'MASTER03_IMAGE006.GIF;BEAVIS DISK$WEB3 .2CB(y筗; =J7.GIF;BEAVIS DISK$WEB3 .2CB(y筗; =J8.GIF;BEAVIS DISK$WEB3 .2CB(y筗; =J9.GIF;BEAVIS DISK$WEB3 .2CB(y筗; >I10.GIF;BEAVIS DISK$WEB3 .2CB(y筗; =J1.GIF;BEAVIS DISK$WEB3 .2CB(y筗; =J2.GIF;BEAVIS DISK$WEB3 .2CB(y筗; =J3.GIF;BEAVIS DISK$WEB3 .2CB(y筗 ; =J4.GIF;BEAVIS DISK$WEB3 .2CB(y筗 ; =J5.GIF;BEAVIS DISK$WEB3 .2CB(y筗 ; =J6.GIF;BEAVIS DISK$WEB3 .2CB(y筗 ; =J7.GIF;BEAVIS DISK$WEB3 .2CB(y筗 ; =J8.GIF;BEAVIS DISK$WEB3 .2CB(y筗