œDECVAX-VMS€ üOpenVMS Alpha Galaxy GuideÕ*˜dE�VMS_ALPHA_GALAXY_GDOPENVMS-ALPHABASE-VMS-250136BOOKBROWSER ¿ Contents  Tablesð) B*÷VAX DOCUMENT V2.1 p•KX•Kgcugrap �•Kø•Kx•Khw_rest °•K˜•Kgui_2apè•K(ЕK À•Kneeds_chaptÈ•K0WHIDE°—Kˆ–KH–K0tsø•Kð¬K6ð ,gcu|1z1HP–K0@–K–K;]8200_ints_tabKinuetopih–KC–( –K 䈖Kneeds_chaptØ–K(À–K°–K8200_ints_tab ð–K—KØ–Kgui_16r(—KCreatø–K8200_ints_tabGaH0—K0 —KP–K;Å_8200_ints_tab ÚR/”“ gCONTENTSCONTENTS8 ˆ E\TitlePageTitle Page@ ˆE\ CopyrightPageCopyright Page 1 xE\PrefacePreface} w+::$K1¾OpenVMSGalaxyVersion7.2ReleaseNotes1 OpenVMS Galaxy Version 7.2 Release Notes w)> $K1.11&K InformationalMessageDuringBooting1.1 Informational Message During Booting ê ÐW{ $K1.27&K Permanent RestrictiononKFMSBandCIXCD7&£AdaptersinOpenVMSGalaxyConfigurations1.2 Permanent Restriction on KFMSB and CIXCD Adapters in OpenVMS Galaxy Configurations!Ü ÐQs $L1.3;&L CompatibilityofGalaxy Computing Environment+&¤and Non-GalaxyClusterMembers1.3 Compatibility of Galaxy Computing Environment and Non-Galaxy Cluster Members#ß ÐRu $L1.44&LPossibleProblem UpgradingFirmwareon4&¤ AlphaServer4100Systemsfor V7.2-EFT31.4 Possible Problem Upgrading Firmware on AlphaServer 4100 Systems for V7.2-EFT30¸ àC]H‡\PartIM IntroductiontotheGalaxySoftware ArchitecturežµonOpenVMSPart I Introduction to the Galaxy Software Architecture on OpenVMS6X w&&$K2¾OpenVMSGalaxyOverview2 OpenVMS Galaxy Overview7® À:\ $K2.19&KANew ComputingModelandaNewSoftware&¤ Architecture2.1 A New Computing Model and a New Software Architecture8� w0G $K2.2:&KTheGalaxySoftware ArchitectureonOpenVMS2.2 The Galaxy Software Architecture on OpenVMS;„ w+A $K2.34&KOpenVMSGalaxy ComponentsandConcepts2.3 OpenVMS Galaxy Components and Concepts=K l$@2.3.1²APMPConcepts2.3.1 APMP ConceptsHb \++$@2.3.2²AnotherPossiblePicture2.3.2 Another Possible PictureMd w0 $L2.4#&LOpenVMSGalaxyFeatures2.4 OpenVMS Galaxy FeaturesPd w0 $K2.5#&KOpenVMSGalaxyBenefits2.5 OpenVMS Galaxy BenefitsX~ w(> $K2.61&KOpenVMSGalaxyVersion1.0Features2.6 OpenVMS Galaxy Version 1.0 Featuresgd w ,,$K3¾OpenVMSGalaxyConfigurations3 OpenVMS Galaxy Configurationsis w"9 $K3.1,&KIsanOpenVMSGalaxyforYou?3.1 Is an OpenVMS Galaxy for You?jƒ l->>$@3.1.1²WhyaGalaxyisaGoodBusinessChoice3.1.1 Why a Galaxy is a Good Business Choicen› l8KK$A3.1.2²ThingstoConsiderIfYouWanttoCreateaGalaxy3.1.2 Things to Consider If You Want to Create a Galaxyqƒ w+@ $K3.23&KPossibleOpenVMSGalaxyConfigurations3.2 Possible OpenVMS Galaxy Configurationsxn l%11$A3.2.1²Shared-Nothing ComputingModel3.2.1 Shared-Nothing Computing Model~n l%11$@3.2.2²Shared-Partial ComputingModel3.2.2 Shared-Partial Computing Model�t l(44$@3.2.3²Shared-Everything ComputingModel3.2.3 Shared-Everything Computing Modelƒp w"6 $K3.3)&K ImportantCluster Information3.3 Important Cluster Information…l g 4 $L3.4'&LSCSIClusterConsiderations3.4 SCSI Cluster Considerations‡Ç ÐGh $K3.5;&KSecurityConsiderationsinanOpenVMSGalaxy &£ Computing Environment3.5 Security Considerations in an OpenVMS Galaxy Computing Environment‘Ì ÐHl $L3.6@&L ImportantInfoThatNeedstobeLocatedinthe&¤ AppropriateChapters3.6 Important Info That Needs to be Located in the Appropriate Chapters”Z l''$A3.6.1²NewSYSGEN parameter3.6.1 New SYSGEN parameter•U l$$$A3.6.2²System Auto-Action3.6.2 System Auto-Action™ l-::$@3.6.3²Changingconsole environment variables3.6.3 Changing console environment variablesœQ \""$@3.6.4² CONFIGUREGALAXY3.6.4 CONFIGURE GALAXY�s w'44$K4¾OpenVMSGalaxy Licensing Information4 OpenVMS Galaxy Licensing Informationž� w*? $L4.12&LOpenVMSGalaxy Licensing Requirements4.1 OpenVMS Galaxy Licensing Requirements s l'44$A4.1.1²OpenVMS OperatingSystemLicense4.1.1 OpenVMS Operating System License¤^ l))$A4.1.2²OpenVMSGalaxyLicense4.1.2 OpenVMS Galaxy License¦s l'44$@4.1.3²OpenVMSLayeredProductsLicense4.1.3 OpenVMS Layered Products License¨} w(= $K4.20&K ClusteringOpenVMSGalaxy Instances4.2 Clustering OpenVMS Galaxy Instancesªn l$22$@4.2.1² ClusteringinaGalaxySystem4.2.1 Clustering in a Galaxy System«x l)77$A4.2.2² ClusteringOutsideaGalaxySystem4.2.2 Clustering Outside a Galaxy System­W g) $L4.3&LLicense Databases4.3 License Databases¯ w(? $K4.42&KOpenVMSGalaxyLicensePAKsandLMF4.4 OpenVMS Galaxy License PAKs and LMF¶‘ w1H $K4.5;&KForMore InformationAboutOpenVMS Licensing4.5 For More Information About OpenVMS Licensing¾… ˆ/>>‡\PartIINCreatinganOpenVMSGalaxy EnvironmentPart II Creating an OpenVMS Galaxy EnvironmentÀ™ À4M?$K5¾CreatinganOpenVMSGalaxyonan AlphaServer ¤84005 Creating an OpenVMS Galaxy on an AlphaServer 8400ÁÈ ÐGi $K5.1<&KStep1:*Choosea Configurationand Determine &¤Hardware Requirements5.1 Step 1: Choose a Configuration and Determine Hardware Requirements‚ l.<<$@5.1.1²UsingtheOpenVMS ConfigurationUtility5.1.1 Using the OpenVMS Configuration UtilityÏw l)66$A5.1.2²OpenVMS GalculatorDisplayExample5.1.2 OpenVMS Galculator Display ExampleØu w#: $L5.2-&LStep2:&SetUpGalaxyHardware5.2 Step 2: Set Up Galaxy HardwareÙ™ l9HH$A5.2.1² InstallingtheKFE72-DAConsole SubsystemHardware5.2.1 Installing the KFE72-DA Console Subsystem HardwareÚa l++$A5.2.2²UsingaTerminalServer5.2.2 Using a Terminal Serverߘ l9GG$@5.2.3²Recommendationsfor ConfiguringConsole Subsystems5.2.3 Recommendations for Configuring Console Subsystemsà` l**$@5.2.4² InstallingEISADevices5.2.4 Installing EISA Devicesçq w!8 $L5.3+&LStep3:&CreateASystemDisk5.3 Step 3: Create A System Diskw.F $L5.49&LStep4:&InstallOpenVMSAlphaVersion7.25.4 Step 4: Install OpenVMS Alpha Version 7.2ð{ l+88$A5.4.1²OpenVMSGalaxy Licensing Information5.4.1 OpenVMS Galaxy Licensing Informationòp w!7 $K5.5*&KStep5:&UpgradetheFirmware5.5 Step 5: Upgrade the Firmwareóz w&< $K5.6/&KStep6:&Set Environment Variables5.6 Step 6: Set Environment Variablesû{ l+88$@5.6.1²Galaxy Environment VariablesExample5.6.1 Galaxy Environment Variables Example c l,,$A5.6.2²TableofUsefulIntegers5.6.2 Table of Useful Integers � w0H $L5.7;&LStep7:&Startthe SecondaryConsoleDevices5.7 Step 7: Start the Secondary Console Devices K \$A5.7.1²ConsoleHints5.7.1 Console Hintsw w$; $L5.8.&LStep8:&BoottheOpenVMSGalaxy5.8 Step 8: Boot the OpenVMS Galaxy™ À4M?$K6¾CreatinganOpenVMSGalaxyonan AlphaServer ¤82006 Creating an OpenVMS Galaxy on an AlphaServer 8200!È ÐGi $K6.1<&KStep1:*Choosea Configurationand Determine &¤Hardware Requirements6.1 Step 1: Choose a Configuration and Determine Hardware Requirements"k l#00$@6.1.1²UsingtheOpenVMS Galculator6.1.1 Using the OpenVMS Galculator&w l)66$@6.1.2²OpenVMS GalculatorDisplayExample6.1.2 OpenVMS Galculator Display Example/u w#: $L6.2-&LStep2:&SetUpGalaxyHardware6.2 Step 2: Set Up Galaxy Hardware0™ l9HH$A6.2.1² InstallingtheKFE72-DAConsole SubsystemHardware6.2.1 Installing the KFE72-DA Console Subsystem Hardware1a l++$A6.2.2²UsingaTerminalServer6.2.2 Using a Terminal Server6˜ l9GG$A6.2.3²Recommendationsfor ConfiguringConsole Subsystems6.2.3 Recommendations for Configuring Console Subsystems7` l**$@6.2.4² InstallingEISADevices6.2.4 Installing EISA Devices>q w!8 $K6.3+&KStep3:&CreateASystemDisk6.3 Step 3: Create A System DiskEŒ w.F $L6.49&LStep4:&InstallOpenVMSAlphaVersion7.26.4 Step 4: Install OpenVMS Alpha Version 7.2G{ l+88$A6.4.1²OpenVMSGalaxy Licensing Information6.4.1 OpenVMS Galaxy Licensing InformationIp w!7 $K6.5*&KStep5:&UpgradetheFirmware6.5 Step 5: Upgrade the FirmwareJz w&< $K6.6/&KStep6:&Set Environment Variables6.6 Step 6: Set Environment VariablesR{ l+88$@6.6.1²Galaxy Environment VariablesExample6.6.1 Galaxy Environment Variables ExampleaO l!!$@6.6.2²UsefulIntegers6.6.2 Useful Integersb� w0H $L6.7;&LStep7:&Startthe SecondaryConsoleDevices6.7 Step 7: Start the Secondary Console DevicesdK \$@6.7.1²ConsoleHints6.7.1 Console Hintspw w$; $K6.8.&KStep8:&BoottheOpenVMSGalaxy6.8 Step 8: Boot the OpenVMS Galaxyv¨ Ð;U?$L7¾CreatinganOpenVMSGalaxyonan AlphaServer ¤4100System7 Creating an OpenVMS Galaxy on an AlphaServer 4100 SystemyV g) $K7.1&KBeforeYouStart7.1 Before You StartzH g! $K7.2&K Procedures7.2 ProceduresŠ› Ð5N>$K8¾UsingaSingle-InstanceGalaxyonAnyAlpha ¤System8 Using a Single-Instance Galaxy on Any Alpha Systemªn ˆ$22‡\PartIIIMManagingAnOpenVMSGalaxyPart III Managing An OpenVMS Galaxyµs w'44$K9¾OpenVMSGalaxy ConfigurationUtility9 OpenVMS Galaxy Configuration Utility¶E g   $L9.1&LGCUTour9.1 GCU Tour¿{ l+88$A9.1.1²CreatingGalaxy ConfigurationModels9.1.1 Creating Galaxy Configuration ModelsÄF \$A9.1.2² Observation9.1.2 ObservationÊW l%%$@9.1.2.1ÉLayout Management9.1.2.1 Layout ManagementÐ` l**$@9.1.2.2ÉOpenVMSGalaxyCharts9.1.2.2 OpenVMS Galaxy ChartsÓF \$@9.1.3² Interaction9.1.3 InteractionÙˆ w,D $L9.27&LManaginganOpenVMSGalaxywiththeGCU9.2 Managing an OpenVMS Galaxy with the GCUÝ[ l''$A9.2.1² Independent Instances9.2.1 Independent Instancesâ\ l(($A9.2.2²RequiredPROXYAccess9.2.2 Required PROXY Accessål w 4 $K9.3'&KGalaxy ConfigurationModels9.3 Galaxy Configuration ModelsíI \$A9.3.1²ActiveModel9.3.1 Active ModelñM \  $@9.3.2²OfflineModels9.3.2 Offline Modelsò| l+99$@9.3.2.1ÉExample:&CreatinganOfflineModel9.3.2.1 Example: Creating an Offline Modelô_ w. $K9.4!&KUsingtheGCUCharts9.4 Using the GCU Chartsù’ l6DD$A9.4.1² ComponentIdentificationandDisplay Properties9.4.1 Component Identification and Display Propertiesüb l++$A9.4.2²Physical StructureChart9.4.2 Physical Structure ChartO \!!$A9.4.2.1ÉHardwareRoot9.4.2.1 Hardware RootW l%%$A9.4.2.2É OwnershipOverlay9.4.2.2 Ownership Overlay` l**$@9.4.3²Logical StructureChart9.4.3 Logical Structure ChartO \!!$@9.4.3.1ÉSoftwareRoot9.4.3.1 Software Root ] l(($A9.4.3.2É Unassigned Resources9.4.3.2 Unassigned Resources [ l''$A9.4.3.3É Community Resources9.4.3.3 Community ResourcesY \&&$A9.4.3.4ÉInstance Resources9.4.3.4 Instance Resources` l**$A9.4.4²Memory AssignmentChart9.4.4 Memory Assignment ChartW l%%$@9.4.4.1ÉConsole Fragments9.4.4.1 Console FragmentsW l%%$@9.4.4.2ÉPrivate Fragments9.4.4.2 Private Fragmentsd l ,,$A9.4.4.3ÉSharedMemory Fragments9.4.4.3 Shared Memory FragmentsZ l''$A9.4.5²CPU AssignmentChart9.4.5 CPU Assignment ChartK l$A9.4.5.1ÉPrimaryCPU9.4.5.1 Primary CPUQ l""$A9.4.5.2É SecondaryCPUs9.4.5.2 Secondary CPUst \'55$A9.4.5.3ÉFastPathand AffinitizedCPUs9.4.5.3 Fast Path and Affinitized CPUsG \$A9.4.5.4ÉLostCPUs9.4.5.4 Lost CPUsZ l''$@9.4.6²IOP AssignmentChart9.4.6 IOP Assignment Chart\ l(($@9.4.7²FailoverTargetChart9.4.7 Failover Target Chart!n w!5 $L9.5(&LViewing Component Parameters9.5 Viewing Component Parameters(n w!5 $L9.6(&L Executing ComponentCommands9.6 Executing Component Commands*U w( $K9.7&KCPU Reassignment9.7 CPU Reassignment+Q l""$A9.7.1²DCL Reassignment9.7.1 DCL Reassignment-n l%11$@9.7.2²GCU Drag-and-Drop Reassignment9.7.2 GCU Drag-and-Drop Reassignment1_ l))$@9.7.3² Intermodal Reassignment9.7.3 Intermodal Reassignment2Š l2@@$A9.7.4²Software ReassignmentUsingGalaxyServices9.7.4 Software Reassignment Using Galaxy Services8W l%%$A9.7.5² ReassignmentFaults9.7.5 Reassignment Faults:‹ w.E $K9.88&K MonitoringanOpenVMSGalaxywithDECamds9.8 Monitoring an OpenVMS Galaxy with DECamds<^ w- $K9.9 &KCreatinganInstance9.9 Creating an Instance@d w0$K9.10"&K DissolvinganInstance9.10 Dissolving an InstanceAm w 5$K9.11'&KShutdownandRebootCycles9.11 Shutdown and Reboot CyclesBq g"7$K9.12)&KOnlineversusOfflineModels9.12 Online versus Offline ModelsCx g$<$K9.13.&KWhat'sNewForTheGCUinEFT39.13 What's New For The GCU in EFT3FT \$$$A9.13.1ŒNewDCLcommands9.13.1 New DCL commandsG^ w-$L9.14&LGCUSystemMessages9.14 GCU System MessagesMC g$K10“DCLCommands10 DCL CommandsNO g%$K10.1&KCPUCommands10.1 CPU CommandsRR \""$@10.1.1ŒSTOP/CPU/MIGRATE10.1.1 STOP/CPU/MIGRATESC \$@10.1.2ŒSHOWCPU10.1.2 SHOW CPUZM g$$L10.2&LSHOWMEMORY10.2 SHOW MEMORY\h w2$L10.3$&LLexicalFunctionExample10.3 Lexical Function Example^> g $K10.4&KDUMP10.4 DUMPaD g $K10.5&KANALYZE10.5 ANALYZEmD g $K10.6&KINSTALL10.6 INSTALLx€ w-;;$K11“SharedMemoryCluster Interconnect(SMCI)11 Shared Memory Cluster Interconnect (SMCI)yj w3$P11.1%&P SYS$PBDRIVERPortDevices11.1 SYS$PBDRIVER Port Devicesz l,;;$A11.1.1ŒMultipleClustersinaSingleGalaxy11.1.1 Multiple Clusters in a Single Galaxy|} w(=$Q11.2/&QSYSGEN Parametersfor SYS$PBDRIVER11.2 SYSGEN Parameters for SYS$PBDRIVERF l$A11.2.1Œ SMCI_PORTS11.2.1 SMCI_PORTS€F l$A11.2.2Œ SMCI_FLAGS11.2.2 SMCI_FLAGS‚x w%;$K11.3-&KLANSharedMemoryDeviceDriver11.3 LAN Shared Memory Device Driver„r w&44$K12“OpenVMSGalaxyTipsand Techniques12 OpenVMS Galaxy Tips and Techniquesˆ” à2J:‡\PartIVN DevelopingProgramsForAnOpenVMSÔ´GalaxyPart IV Developing Programs For An OpenVMS Galaxy‰h w"..$K13“Locking Programming Interfaces13 Locking Programming InterfacesŠn w"4$Q13.1&&QSYS$CREATE_GALAXY_LOCK_TABLE13.1 SYS$CREATE_GALAXY_LOCK_TABLE�n w"4$Q13.2&&QSYS$DELETE_GALAXY_LOCK_TABLE13.2 SYS$DELETE_GALAXY_LOCK_TABLE•` w-$Q13.3&QSYS$RESET_GALAXY_LOCK13.3 SYS$RESET_GALAXY_LOCKšb w.$P13.4 &PSYS$CREATE_GALAXY_LOCK13.4 SYS$CREATE_GALAXY_LOCKŸb w.$P13.5 &PSYS$DELETE_GALAXY_LOCK13.5 SYS$DELETE_GALAXY_LOCK¤f w0$P13.6"&PSYS$GET_GALAXY_LOCK_INFO13.6 SYS$GET_GALAXY_LOCK_INFO©f w0$Q13.7"&QSYS$GET_GALAXY_LOCK_SIZE13.7 SYS$GET_GALAXY_LOCK_SIZE®d w/$Q13.8!&QSYS$ACQUIRE_GALAXY_LOCK13.8 SYS$ACQUIRE_GALAXY_LOCK³d w/$Q13.9!&QSYS$RELEASE_GALAXY_LOCK13.9 SYS$RELEASE_GALAXY_LOCK¾f w1$K13.10"&KLockingErrorMessages13.10 Locking Error MessagesÃu w(55$K14“SystemEvents Programming Interfaces14 System Events Programming InterfacesÄX w)$P14.1&P$SET_SYSTEM_EVENT14.1 $SET_SYSTEM_EVENTÅ\ w+$Q14.2&Q$CLEAR_SYSTEM_EVENT14.2 $CLEAR_SYSTEM_EVENTòu w(55$K15“SharedMemory Programming Interfaces15 Shared Memory Programming Interfaces^ w-$L15.1&LUsingSharedMemory15.1 Using Shared MemoryU w($L15.2&LSystemServices15.2 System ServicesU \$$$A15.2.1ŒEnhancedServices15.2.1 Enhanced Services l-::$A15.2.2ŒNewSectionFlagSEC$M_READ_ONLY_SHPT15.2.2 New Section Flag SEC$M_READ_ONLY_SHPTl w 4$K15.3&&K GalaxywideGlobalSections15.3 Galaxywide Global Sectionsw w)66$K16“CPU Management Programming Interfaces16 CPU Management Programming Interfaces1Z w*$Q16.1&QSYS$CPU_TRANSITION16.1 SYS$CPU_TRANSITION2V w($Q16.2&Q$CPU_TRANSITIONW16.2 $CPU_TRANSITIONWa‹ w3@@$K17“ Configuration Management Programming Interfaces17 Configuration Management Programming InterfacesfJ w"$Q17.1&Q SYS$GETSYI17.1 SYS$GETSYIha w++$K18“SystemDumpAnalyzer(SDA)18 System Dump Analyzer (SDA)o� w0G$K18.19&KSDACommand InterfaceChangesor Additions18.1 SDA Command Interface Changes or Additionsqg w!..$L19“OpenVMSGalaxyDeviceDrivers19 OpenVMS Galaxy Device Driverswk w4$L19.1&&LDirectDMAWindowChanges19.1 Direct DMA Window Changesx¢ À4V$K19.2:&KHowPCIDirectDMAWorksPriortoOpenVMS&¤V7.219.2 How PCI Direct DMA Works Prior to OpenVMS V7.2y¤ À5W$K19.3<&KHowPCIDirectDMAWorksinOpenVMSVersion &¤7.219.3 How PCI Direct DMA Works in OpenVMS Version 7.2{½ ÅBc$P19.47&P IOC$NODE_DATAChangestoSupportNon-zero&©DirectDMAWindows19.4 IOC$NODE_DATA Changes to Support Non-zero Direct DMA Windows} Ý+ “gTABLESTABLESL l=@5-1ÿUsefulIntegers5- 1 Useful Integers ` l**=@6-1ÿTableofUsefulIntegers6- 1 Table of Useful Integersc † *[Ú1 Oƒ 'O÷OpenVMSAlphaGalaxyGuide ! âOÅDecember3,1998SOkThisguide introducesCompaqGalaxySoftware ArchitectureconceptsRO¹and describeshowtocreate,manage,anduseanOpenVMSGalaxy!O computing environment.�ÚâsKO{Thelatestversionofthisguideisalways availableat:(OÉhttp://www.openvms.digital.com*tÚÞJ'OÅRevision/Update Information:#^ÅThisisanewmanual.uÚÞK%OÅ OperatingSystemVersion:&^ÅOpenVMSAlphaVersion7.2mÚÞCOÅSoftwareVersion:'^ÅOpenVMSGalaxyVersion1.0* * j Úâ@'O{CompaqComputer CorporationOÉHouston,Texas >  ú  ! ÊÐ  O• OÝJanuary1999IOxTHISDRAFTDOCUMENTISAWORKIN PROGRESS.ITCONTAINSBO» PRELIMINARY INFORMATIONTHATISSUBJECTTOCHANGE.]OVCompaqComputer Corporationbelievesthatthe informationinthisdocumentfO˜isaccurateasofitsissuedate;such informationissubjecttochangewithoutBOÚnotice.'Compaqisnot responsibleforanyerrors.[OuThisdocumentisprovided``ASIS''andwithoutanyexpressorimpliedUO¸ warranties,! including, without limitation, theimplied warrantiesorEOúmerchantabilityandfitnessfora particularpurpose.\O•CompaqComputer Corporationmakesnorepresentationsthattheuseofits^OØproductsinthemanner describedinthis publicationwillnotinfringeon`Oexistingorfuturepatentrights,nordothe descriptions containedinthiscO\ publicationimplythegrantingoflicensestomake,use,orsell equipmentor;OŸsoftwarein accordancewiththe description.aO: Possession,use,orcopyingofthesoftware describedinthis publicationisZO| authorizedonlypursuanttoavalidwrittenlicensefromCompaqoran"O¿ authorized sublicensor.`OZCompaqconductsitsbusinessinamannerthat conservesthe environmentandcOœprotectsthesafetyandhealthofits employees, customers,andthe community.IO7©CompaqComputer Corporation1999.'Allrights reserved.UOÒThe followingare trademarksofCompaqComputer Corporation:.Alpha,RO  Bookreader,DECnet,DIGITAL,LAT,OpenVMS, StorageWorks,VAX,VAX?OW  DOCUMENT, VAXcluster,VMS,andtheCompaqlogo.TOò The followingare third-party trademarks:. POSTSCRIPTare registered7O4  trademarksofAdobeSystems Incorporated.ROÏ Compaqisa registered trademarkofCompaqComputer Corporation.\Oj Motif,OSF,OSF/1, OSF/Motif,andOpenSoftware Foundationare registered@O­  trademarksoftheOpenSoftware Foundation,Inc.DOH WindowsNTisa trademarkof Microsoft Corporation.[Oã  MicrosoftandWindowsare registered trademarksof Microsoft Corporation.OO~ MEMORYCHANNELisa trademarkofEncoreComputer Corporation.VOOracle,Oracle7,andOracleRdbare registered trademarksofOracleO[ Corporation.\OöAllother trademarksand registered trademarksarethepropertyoftheirO8 respectiveholders.:ZK6512FO±TheOpenVMS documentationsetis availableonCD-ROM.* õ  çÚq½OàPrefaceJO§Thisguide describeshow customerscantake advantageofDOtheOpenVMSGalaxy capabilities availableinOpenVMSOXAlphaVersion7.2.Û ›±KOƒThe informationinthisdocumentappliestoOpenVMSAlphaJOÜsystemsonly;itdoesnotapplytoOpenVMSVAXsystems.O‚IntendedAudienceKÚ !HOAThisguideisintendedforsystem managers, applicationHOš programmers, technical consultants,datacenter managers,FOòandanyoneelsewhowantstolearnabouttheGalaxy.OKSoftware ArchitectureonOpenVMS.OñDocument Structure  vGOASpecifictopicsinclude:,basicOpenVMSGalaxy concepts,?Ošhardwareandsoftware requirements,! configurationIOò alternatives, installingand licensing information,systemHOK managementoptions,and available application programmingEO£ interfaces(APIs)for developingprogramsforOpenVMSOüGalaxysystems.~ÚCT2Oƒ Tobe supplied:'Chapter descriptions"O*HowtoUsethisBookhÚZ>>OA Tobe supplied:'Addaroadmapofthebook.ö! ýÌJOƒThisbook introducesOpenVMSGalaxyfeaturesandexplainsEOÜhowtousetheOpenVMSGalaxyfeatures availableinHO5OpenVMSAlphaVersion 7.2-EFT3.'Itincludes step-by-stepGO� proceduresfor configuring, managing,andusingOpenVMSOOæGalaxy technologyaswellasAPIsfor developingprogramstoCO>take advantageofthenewOpenVMSGalaxy features.OäRelated Documents>ÿ6KOAFor additional informationabouttheOpenSystemsSoftwareGOšGroup(OSSG)productsand services,accesstheOpenVMS>OòWorldWideWebsiteatthe followingaddress:(Ow http://www.openvms.digital.comOReader'sCommentsgÚZ==OACompaqwelcomesyourcommentsonthismanual.¦Úõ|BOƒPrintoredittheonlineformSYS$HELP:OPENVMSDOC_:OÜ COMMENTS.TXTandsendusyourcommentsby:–! ËlOãInternet$bãopenvmsdoc@zko.mts.dec.com O]FaxAb]603 884-0120, Attention:!OSSGDocumentation,ZKO3-bª4/U08O$Mail'b$CompaqComputer Corporation1bqOSSG DocumentationGroup, ZKO3-4/U08b¿110SpitBrookRd.!b Nashua,NH 03062-26983O²HowToOrder Additional DocumentationÀÚ7–JOAUsethe followingWorldWideWebaddresstoorderaddi- Oštionaldocumentation:,O "http://www.openvms.digital.com:81/ÃÚ›™JOƒIfyouneedhelpdecidingwhich documentationbestmeets:OÜyourneeds,call 800-DIGITAL(800-344-4825).O‚ ConventionsEÚZOAInthismanual:Áìñ— `Ð ·ÔÐ Instance=OÐreferstoacopyoftheOpenVMSAlphaoper-Ô(atingsystem. `¨ ·Ô¨ OpenVMSGalaxy ²¨andT¨ Galaxy €¨refertotheCompaq6ÔGalaxySoftware ArchitectureonOpenVMS. `€ ·Ô€ DECwindows ý€and¡€ DECwindowsMotif¿€referto4ÔØ DECwindowsMotifforOpenVMS software.mÚœCCOƒThe following conventionsareusedinthismanual:{! ×QOãCtrl/ ßã x&KãAsequencesuchasCtrl/ \ã x“ã indicatesthatyou?K0mustholddownthekeylabeledCtrlwhileyou?K~pressanotherkeyorapointingdevicebutton. O÷PF1 Û÷ x$K÷AsequencesuchasPF1 Y÷ x�÷ indicatesthatyou=KEmustfirstpressandreleasethekeylabeled;K’PF1andthenpressandreleaseanotherkey*Kàorapointingdevicebutton. Oæ OTbWReturn 3T Opæ;KZIn examples,akeynameenclosedinaboxAK§ indicatesthatyoupressakeyonthe keyboard.CKõ(Intext,akeynameisnotenclosedinabox.);KnIntheHTMLversionofthis document,this=K¼ conventionappearsas brackets,ratherthanaK box.jƒ...:KƒA horizontalellipsisinexamples indicates1KÑoneofthe followingpossibilities: \V ·0ÐV Additionaloptional argumentsina)У statementhavebeenomitted. \" ·2Ð"The precedingitemoritemscanbe)Ðprepeatedoneormoretimes. \ï ·5Ðï Additional parameters,values,orother(Ð= informationcanbeentered. Oî. O; . O‰ .=KîAverticalellipsis indicatestheomissionof:K; itemsfromacodeexampleorcommandfor-K� indicatethatyoumustenclosetheoptionsin8Kë  parenthesesifyouchoosemorethanone.Oe []6Ke Incommandformat descriptions,brackets9K² indicateoptional elements.$YoucanchooseKè  specificationorinthesyntaxofa substring8K6  specificationinan assignment statement.)O¯ [ | ]6K¯ Incommandformat descriptions,vertical=Ký bars separatingitemsinsidebracketsindicate=KJthatyouchooseone,none,ormorethanoneK˜oftheoptions.O{}9KIncommandformat descriptions,bracesin-=K_dicaterequired elements;youmustchooseone#K­oftheoptionslisted.O&boldtext>K&Thistextstyle representsthe introductionof  $ÚÁú4O 1.>OpenVMS(Galaxy'Version(7.2'ReleaseOrNotesGO÷ThischaptercontainsOpenVMSGalaxyreleasenotesforIOOOpenVMSVersion7.2and indicatesthecurrentstatusof'O¨Version7.2releasenotes. ‡  m ÚnC6OÐ1.1B InformationalMessageDuringBooting OU TBS Q ½!ÚÆ“cluster recognizethenewsecurityclassesas describedinthisO—releasenote.€%! œVVOƒThis situationappliesifallofthe following conditionsaremet:t&ê ñJ `Ð ·IÔÐIfyourOpenVMSGalaxyis configuredinaclusterwithÔ( non-Galaxysystems `¨ ·JÔ¨Ifthe non-GalaxyclusternodessharetheVMS$OBJECTS.DAT"Ôsecuritydatabasefile `€ ·GÔ€Ifyouuse galaxywideglobalsectionsinyourOpenVMSÔØGalaxyø'ÚNÎ=OƒOpenVMSVAXandAlphasystemsrunningOpenVMSNOÜVersion6.2orVersion7.1willcrashifthey encounteranCO5unknownsecurityclassintheVMS$OBJECTS.DATfile.Â(! W˜KOƒToallowVAXandAlphasystemsrunningolderversionsofKOÜOpenVMSto cooperatewithVersion7.2Galaxy instancesinDO5thesameOpenVMSCluster environment,a SECURITY.EXEOO�imageisprovidedforeachofthese versions.+ThefilesareEOælocatedontheOpenVMSAlphaVersion7.2-EFT3CDin*O> directory[VMS$COMMON.SYS$LDR]::)Ú6OãOpenVMSAlphaV6.2JSECURITY.EXE_ALPHA_V62 K0SECURITY.STB_ALPHA_V626OªOpenVMSAlphaV7.1JSECURITY.EXE_ALPHA_V71 K÷SECURITY.STB_ALPHA_V712OqOpenVMSVAXV6.2pSECURITY.EXE_VAX_V622OëOpenVMSVAXV7.1pSECURITY.EXE_VAX_V71m*ÚœCCOƒTousethenewfiles,youmustdothe following:+l ˜ð@OÅForeachOpenVMSAlphaVersion6.2systemdisk:QO# $& RENAME/LOG%&target_disk:[SYS*.SYS$LDR]SECURITY.EXE%SECURITY.EXE_OLDQO� $& RENAME/LOG%&target_disk:[SYS*.SYS$LDR]SECURITY.STB%SECURITY.STB_OLDPOö $&COPY%:distribution_CD:[VMS$COMMON.SYS$LDR]SECURITY.EXE_ALPHA_V62%-7t† -target_disk:[VMS$COMMON.SYS$LDR]SECURITY.EXE;POï $&COPY%:distribution_CD:[VMS$COMMON.SYS$LDR]SECURITY.STB_ALPHA_V62%-7t -target_disk:[VMS$COMMON.SYS$LDR]SECURITY.STB;,l ˜ð@OÅForeachOpenVMSAlphaVersion7.1systemdisk:QO# $& RENAME/LOG%&target_disk:[SYS*.SYS$LDR]SECURITY.EXE%SECURITY.EXE_OLDQO� $& RENAME/LOG%&target_disk:[SYS*.SYS$LDR]SECURITY.STB%SECURITY.STB_OLDPOö $&COPY%:distribution_CD:[VMS$COMMON.SYS$LDR]SECURITY.EXE_ALPHA_V71%-7t† -target_disk:[VMS$COMMON.SYS$LDR]SECURITY.EXE;POï $&COPY%:distribution_CD:[VMS$COMMON.SYS$LDR]SECURITY.STB_ALPHA_V71%-7t -target_disk:[VMS$COMMON.SYS$LDR]SECURITY.STB;>-l 5>OÅForeachOpenVMSVAXVersion6.2systemdisk:QO# $& RENAME/LOG%&target_disk:[SYS*.SYS$LDR]SECURITY.EXE%SECURITY.EXE_OLDNO� $&COPY%8distribution_CD:[VMS$COMMON.SYS$LDR]SECURITY.EXE_VAX_V62%-7t -target_disk:[VMS$COMMON.SYS$LDR]SECURITY.EXE;è.l �¾=OÅForeachOpenVMSVAXVersion7.1systemdiskQO# $& RENAME/LOG%&target_disk:[SYS*.SYS$LDR]SECURITY.EXE%SECURITY.EXE_OLDNO� $&COPY%8distribution_CD:[VMS$COMMON.SYS$LDR]SECURITY.EXE_VAX_V71%-7t -target_disk:[VMS$COMMON.SYS$LDR]SECURITY.EXE;LO·Beforeyoucreateany galaxywideglobal sections,youmustOOrebootallclustermemberssharingoneoftheupdatedsystemOhdisks.ž/ÚõtEOƒNotethattheOpenVMSVAXVersion7.2-EFT3 operating/OÜsystemalreadycontainsthisfix. <p0! wFFOÐ1.4BPossibleProblem UpgradingFirmwareon AlphaServer'ü(4100Systemsfor V7.2-EFT3MO­Ifyouareusingan AlphaServer4100systemtofieldtestIOOpenVMSGalaxyorVersion 7.2-EFT3,youshouldbeawareCO^ofapossibleproblemwith upgradingthe firmware.é1ÚN¿GOƒWhen upgradingfromanypre-V5.2firmwaretotheAS4_HOÜG52-59firmwarefile,thesystemmayhangoroutputa0O5dumpofthe"ActiveCallFrames".[2Úœ11OƒIfthishappens,dothe following:63 ™ '`Ð1.: Power-cyclethesystem.I`O2.:UpgradetoAlphaSystemsFirmwareUpdateVersion5.22Ô¨intheVersion7.2-EFT3CD-ROMkit.C`'3.:ThenupgradefromAlphaSystemsFirmwareUpdate'Ô€Version5.2to AS4_G52-59.õ4Ú…ËBÔbNotethatthe AS4_G52-59firmwarefileisinthe7Ô»OpenVMSGalaxyfirmwarekit (GALAXY_FIRM_>Ô072.KIT)ontheOpenVMSAlphaVersion7.2-EFT3ÔlCD-ROM2.C5 ¦POƒIfyouhaveany questionswiththis procedure,pleasegetinJOÜtouchwithyour V7.2-EFT3 engineeringdirectedfieldtestTO5sitecontact.'Theproblemwillbe correctedinthefinalrelease+O�ofOpenVMSAlphaVersion7.2. ¡‡6Úƒ]:OüPartI8 IntroductiontotheGalaxySoftware#vj ArchitectureonOpenVMS /7ñ[ë'O 2.2OpenVMS!Galaxy!OverviewIO‘OpenVMSAlphaVersion7.2 introducesamodelofcomput-JOêingthatallowsmultiple instancesofOpenVMStoexecute1OB cooperativelyinasingle computer. H8ñ�Û>OÐ2.1BANew ComputingModelandaNewSoftwareü( Architecture8O­ Adaptive partitionedmultiprocessing(APMP)”­isanewIOmodelof computinginwhichmultiple instancesofoper-JO^atingsystemsexecute cooperativelyinasingle computer.IO·WithAPMP, processors(andotherphysical resources)areMO partitionedinordertorunmultiple instancesof operatingOhsystems.�9öÿeFOƒAPMPisanotherformofmultiprocessor computinglikeEOÜ symmetricmultiprocessing(SMP)and massivelyparallelJO5 processing(MPP).Forexample,withtwo identicalcomput-LO�ers(thehardwareisthesame),onecouldrunasanSMPDOæsystemandtheothercouldrunasanAPMPsystem.š:ÚWp OƒThe(öƒ GalaxySoftware Architectureăisthe complemen-DOÜtary architecturethat leveragesAdaptive Partitioned=O5Multiprocessing (APMP)! capabilities.4The!GalaxyGO� Architectureprovidesthesoftware structureandopera-FOætion componentsthatfullyexploittheAPMP computingO>model. D*J /e; w;?OÐ2.2BTheGalaxySoftware ArchitectureonOpenVMSIOUCompaq'sfirstimplementationoftheAPMPmodelofcom-GO­putingistheGalaxySoftware ArchitectureonOpenVMS,JOwhichusesAPMPtoexecutemultiple instancesofOpenVMS"O^inasingle computer.°< †OƒSoftware logically߃ partitions)…ƒCPUs,memory,andI/OportsJOÜby assigningthemto individual instancesoftheOpenVMSIO5 operatingsystem.*This partitioning,whichasystemman-NO�agerdirects,isasoftware function;nohardware boundaries*Oæare required.(Each individual�æ instance!ýæhasthe resourcesitHO>needstoexecuteindependently.)AnOpenVMSGalaxyenvi-O—ronmentisî— adaptive6c—inthat resourcessuchasCPUscanbeIOï dynamically reassignedto different instancesofOpenVMS. Û3=Ú 9OÐ2.3BOpenVMSGalaxy ComponentsandConceptsCOUTo appreciatehowOpenVMSGalaxyusesAPMPtorunLO­multiple instancesofOpenVMSinasingle computer,itisAO importantto understandthisnew computingmodel.¬> õ‚IOƒTheGalaxySoftware ArchitectureonOpenVMSincludesthe9OÜ followinghardwareandsoftware components:“? ¹iOÅConsole O4Theö4 console8C4onanOpenVMSsystemis comprisedofanGO�attachedterminalandafirmwareprogramthatperformsJOåpower-up self-tests, initializes hardware, initiatessystemIO>booting,andperformsI/OservicesduringsystembootingIO–and shutdown.(Theconsoleprogramalsoprovidesrun-timeQOïservicestothe operatingsystemforconsoleterminalI/O,en-FOG vironmentvariable retrieval,NVRAM (nonvolatilerandomHO accessmemory)saving,andother miscellaneous services.Ë@ W¡HOƒInanOpenVMSGalaxy computing environment,theconsoleNOÜplaysacriticalrolein partitioninghardware resources.+ItGO5 maintainsthe permanent configurationinNVRAMandtheKO�running configurationinmemory.'TheconsoleprovideseachMOæinstanceoftheOpenVMS operatingsystemwithapointerto,O>therunning configurationdata.A ÖOÅSharedmemoryNO4Memoryis logically partitionedintoprivateandsharedsec-KO�tions.,Each operatingsysteminstancehasitsownprivatePOåmemory;thatis,nootherinstancemapsthosephysicalpages.JO>Someofthesharedmemoryis availablefor instancesofKO–OpenVMSto communicatewithoneanother,andtherestof@Oïthesharedmemoryis availablefor applications.9B ¦LOƒTheGalaxySoftware Architectureispreparedforanonuni-EOÜformmemoryaccess(NUMA) environmentand,ifneces-RO5sary,willprovidespecialservicesforsuchsystemstoachieve,O�maximum application performance.ªCû¦€OÅCPUsEO4InanOpenVMSGalaxy computing environment,CPUscan-O�be reassignedbetween instances.fD! W< OÅI/OLO4AnOpenVMSGalaxyhasahighlyscalableI/O subsystembe-JO�causethereare multiple,primaryCPUsinthe system-oneMOåforeach instance.(Also,OpenVMS currentlyhasfeaturesforLO> distributingsomeI/Oto secondaryCPUsinanSMPsystem.QE W' OÅ Independent instancesIO4OneormoreOpenVMS instancescanexecutewithoutshar-DO�ingany resourcesinanOpenVMSGalaxy.,AnOpenVMSEOåinstancethatdoesnotshare resourcesiscalledaneå indepen-O> dentinstance y>.ôF NÊLOƒAn independentinstanceofOpenVMSdoesnot participateinJOÜsharedmemoryuse.)Neitherthebase operatingsystemnor4O5its applicationsaccesssharedmemory.ÜGÚN²AOƒAn OpenVMS!Galaxy can consist solely of indepen-IOÜdent instances;suchasystemwouldresemble traditional(O5mainframe-style partitioning.ˆH ¯^OÐ2.3.1BAPMPConceptsGO4Architecturally,APMPisbasedonanSMPhardwarear-GOŒ chitecture.,ItassumesthatCPU,memory,andI/OhaveNOåfull connectivitywithinthemachineandthatthememoryisNO=cache coherent.*Each subsystemhasfullaccesstoallotherO– subsystems.–I! ÿlOƒAsshownin!ƒFigure2-1.̓diagram,APMPthenlooksattheQOÜ resourcesasiftheywereapie.&Thevarious resources(CPUs,EO5privatememory,sharedmemory,andI/O)arearrangedNO�as concentricbandswithinthepieinaspecific hierarchy..OæSharedmemoryisatthecenter.*I!F“OJˆK! ^LOŠAPMPsupportstheabilitytodividethepieintomultipleWOãslices,eachof disparatesize.'Eachslice, regardlessofsize,hasLO<accesstoallofsharedmemory.) Furthermore,becausesoft-QO”ware partitionsthepie,youcanvarythenumberandsizeofOíslices dynamically.!L °÷QOƒInsummary,eachsliceofthepieisaseparateandcompleteJOÜinstanceofthe operatingsystem.+EachinstancehassomeGO5amountof dedicatedprivatememory,anumberofCPUs,NO�andthe necessaryI/O.EachinstancecanseeallofsharedMOæmemory,whichiswherethe applicationdataresides.'SystemJO> resourcescanbe reassignedbetweenthe instancesofthe0O— operatingsystemwithout rebooting.ÞMÚ¥´+OÐ2.3.2BAnotherPossiblePictureIO4AnotherwaytolookattheAPMP computingmodelisto@OŒthinkabouthowthe resourcescouldbedivided.NÚ¦òJOƒTheoverallsenseofthediagramisthatthe proportionLOÜbywhichoneresourceisdividedbetween instancesistheJO5 proportionbywhicheachoftheother resourcesmustbeO�divided./OÖ � HOƒSomeboxeswouldhavevarying proportionsper instance.Ê PhysicalÊP Memory ÚP CPU ÄP I/OF¤˜ +------+%-%-&-%-%-& -+------+%-&-%-%-&-% -+------+¤à |à|�à |à|zà |à|ä( Instance%1J|JM1K|�( |à|z( |KI1K|¤p +______+�p |à|zp +______+¤¸ |à|\�¸ |à|T¸ /|à|¤ |à|%\� |à|/ /&|à|"äH Instance%2J|JM2K|K\�H |KC1J| H /K|à|¤� |à|p\�� |à|ä� /p|à|¤Ø +______+•\�Ø |à|¿Ø /–|à|!¤  |à|\–\à|à|à/»|à|#¤h |à|%\•\»|à|º/à|à|¤° |à|K\•\•|à|•/z° |à|¤ø |à|p\–\p|à|p/zø |KI2K|¤@ |à|•\•\K|à|J/z@ |à|¤ˆ |à|»\•\%|à|%/zˆ |à|¤Ð |à|à\– \+______+/zÐ |à|¤ |à|Ô \•|à|z |à|ä_ Instance%3J|JM3K|ú_ \p|à|z_ |à|¤§ |à|§ \K|KC2J|z§ |à|¤ï |à|Dï \%|à|zï |à|¤7 |à|-j7 \+______+%-&-%-%-&-% -+______+¤ |à|� |à|z |à|¤Ç |à|�Ç |à|zÇ |à|¤ |à|� |KC3J|z |KI3K|¤W |à|�W |à|zW |à|F¤Ÿ +------+%-%-&-%-%-& -+------+%-&-%-%-&-% -+------+¤ç |JShared&Memory  ç | ¤/ |  / |F¤w +------+%-%-&-%-%-& -+------+%-&-%-%-&-% -+------+ À£PÚÐy(OÐ2.4BOpenVMSGalaxyFeaturesEOUAn evolutioninOpenVMSfunctionality,OpenVMSGalaxyDO­ leveragesprovenOpenVMSCluster, symmetric multipro-NOcessing,and performance capabilitiestooffergreaterlevelsLO^of performance, scalability,and availabilitywith extremely.O·flexible operational capabilities.êQäþÀOÅ ClusteringJO4FifteenyearsofprovenOpenVMSCluster technologyfacil-HO�itates communicationamong clustered instanceswithinanOåOpenVMSGalaxy.­R ÿƒROƒAnOpenVMSClusterisasoftwareconcept.'Itisasetofco-1OÜ ordinatedOpenVMS operatingsystems,÷Ü onepercomputer UÜ,GO5 communicatingovervariouscommunicationsmediatocom-LO�binethe processingpowerandstoragecapacityofmultipleFOæ computersintoasingle,shared-everything environment.ßS WµLOƒAnOpenVMSGalaxyisalsoasoftwareconcept.(However,itCOÜisasetof coordinatedOpenVMS operatingsystems, Ü inasin-O5 glecomputer8 5, communicatingthroughsharedmemory.*AnLO�instanceofthe operatingsysteminanOpenVMSGalaxycanNOæbe clusteredwithother instanceswithintheGalaxyorwith(O> instancesinothersystems.T °äLOƒAnOpenVMSGalaxyisacompletesysteminandofitself.IOÜAlthoughanOpenVMSGalaxycanbeaddedtoanexistingRO5clusterasmultipleclusternodescanbeaddedtoday,thesin-IO�glesystemistheOpenVMSGalaxy architecturefocus.+AnIOæ applicationrunningtotallywithinanOpenVMSGalaxycanKO>take advantageof performance opportunitiesnotpresentin O— multisystem clusters.ÇU � OÅSMPHO4AnyinstanceinanOpenVMSGalaxycanbeanSMPcon-OO� figuration.*ThenumberofCPUsispartofthe definitionofLOåan instance.(BecauseaninstanceintheOpenVMSGalaxyisJO>acompleteOpenVMS operatingsystem,all applicationsbe-PO–havethesameastheywouldona traditional,single-instanceOï computer.ÕV! «OÅCPU reassignmentKO4ACPUcanbe dynamically reassignedfromoneinstancetoNO�anotherwhileall applicationsonboth instancescontinuetoKOårun.+ Reassignmentisrealizedbythreeseparate functions:MO> stopping, reassigning,andstartingtheCPUin question.*AsOO–resourceneedsof applicationschange,theCPUscanbereas-NOïsignedtothe appropriate instances.(Therearesomerestric-LOGtions;forexample,theprimaryCPUinaninstancecannotPO be reassigned,andaCPUcannot specificallybe designatedto&Oøhandlecertain interrupts.ãWÚ¹"OÅDynamicReconfigurationGO4Multiple instancesoftheOpenVMS operatingsystemal-IO�lowsystemmanagerstoreassign processingpowertotheIOå instanceswhose applicationsmostneedit..AsthatneedIO>variesovertime,socantheconfiguration.,OpenVMSal-KO–lowsdynamicreconfigurationwhileall instancesandtheir*Oï applicationscontinuetorun. ;!XÚ÷(OÐ2.5BOpenVMSGalaxyBenefitsEOUManyofthethebenefitsofOpenVMSGalaxytechnol-LO­ogyresultdirectlyfromrunningmultiple instancesofthe>OOpenVMS operatingsysteminasingle computer.àY! N¶JOƒWithseveral instancesofOpenVMSinmemoryatthesameHOÜtime,anOpenVMSGalaxy computing environmentgivesyou$O5quantum improvementsin:©Z H `Ð ·FÔÐCompatibility-Existing applicationsrunwithoutchanges. `O ·EÔOAvailability-Presents opportunitiestoupgradesoftware=Ô¨andexpandsystemcapacitywithoutdowntime. `' ·HÔ'Scalability-Offersscaling alternativesthatimproveper-8Ô€formanceofSMPandcluster environments. `ÿ ·@ÔÿAdaptability-Physical resourcescanbe dynamically<ÔW reassignedtomeetchangingworkloaddemands. `× ·>Ô×Costofownership-FewercomputersystemsreduceFÔ/system management requirements,floorspace,andmore.‰[Úõ_LOƒThe following descriptionsprovidemoredetailsabouttheseOÜ benefits.R\ W(OÅ CompatibilityLO4Existing single-system applicationswillrunwithoutchangesDO�on instancesinanOpenVMSGalaxy.,ExistingOpenVMSMOåCluster applicationswillalsorunwithoutchangesonclus-4O>tered instancesinanOpenVMSGalaxy.]! þõOÅ AvailabilityIO4AnOpenVMSGalaxysystemismore availablethanatra-HO� ditional,single-system-view,SMPsystembecausemultipleNOå instancesofthe operatingsystemcontrolhardware resources.â^! W¸HOƒOpenVMSGalaxyallowsyoutorun differentversionsofJOÜOpenVMS(Version7.2andlater)simultaneously.'Forexam-SO5ple,youcantestanewversionofthe operatingsystemoranOO� applicationinoneinstancewhile continuingtorunthecur-NOærentversiontheother instances.(Youcanthenupgradeyour6O>entiresystem,oneinstanceatatime.Ÿ_ ¯uOÅ ScalabilityGO4Systemmanagerscanassign resourcestomatchapplica-MO�tion requirementsasbusinessneedsgroworchange.&WhenaROåCPUisaddedtoaGalaxyconfiguration,itcanbeassignedtoKO>anyinstanceofOpenVMS.Thismeansthat applicationscan/O–realize100%ofaCPU'spower.0`Ú¦GOƒTypicalSMPscalingissuesdonotrestrictanOpenVMSAOÜGalaxy.2Systemmanagerscandefinethe number ofFO5OpenVMS instances,assignthenumberofCPUsineach8O� instance,andcontrolhowtheyareused.´a WŠHOƒ Additionally,atrial-and-errormethodof evaluatingre-LOÜsourcesisaviable strategy.*SystemmanagerscanreassignDO5CPUsamong instancesofOpenVMSuntilthemostef-MO�fective combinationof resourcesisfound.,All instancesofKOæOpenVMSandtheir applicationscontinuetorunwhileCPUsO>are reassigned.%b þûOÅ AdaptabilityHO4AnOpenVMSGalaxyishighly adaptablebecause computingOO� resourcescanbe dynamically reassignedtoother instancesofNOåthe operatingsystemwhileall applicationscontinuetorun.'cí°ýJOƒ ReassigningCPUsbest demonstratestheadaptive capabilityDOÜofanOpenVMSGalaxy computing environment.+Forex-HO5ample,ifasystemmanagerknowsthatresourcedemandsJO�changeatcertaintimes,thesystemmanagercanwriteaJOæcommand proceduretoreassignCPUstoother instancesofHO>OpenVMSandsubmittheprocduretoabatchqueue.+TheKO—samecouldbedonetomanagesystemloadcharacteristics.µdéW‹HOƒInanOpenVMSGalaxy environment,softwareisintotalIOÜcontrolof assigningand dynamically reassigninghardwareJO5 resources.)As additionalhardwareisaddedtoanOpenVMSNO�Galaxysystem, resourcescanbeaddedtoexisting instances;KOæornew instancescanbedefinedwithout affectingrunningO> applications.e `óOÅCostof ownershipHO4AnOpenVMSGalaxypresents opportunitiestoupgradeex-KO�isting computersandexpandtheir capacity,ortoreplaceIOåsomenumberof computers,whethertheyareclustermem-MO>bersor independentsystems,withasinglecomputerrunningLO–multiple instancesofthe operatingsystem.'Fewer computersJOïgreatlyreducessystem management requirementsaswellasOGfloorspace.úfõÐOÅ PerformanceEO4AnOpenVMSGalaxycanprovidehigh commercialappli-HO�cation performanceby eliminatingmanySMPandcluster-QOåscaling bottlenecks.)Also,the distributionof interruptsacrossLO> instancesprovidesmanyI/O configurationpossibilities;forNO–example,asystem'sI/Oworkloadcanbe partitionedsothatCOïcertainI/Otrafficisdoneonspecific instances. “ágÚÆ·6OÐ2.6BOpenVMSGalaxyVersion1.0FeaturesCOUWithOpenVMSAlphaVersion7.2,youcancreatean>O­OpenVMSGalaxy environmentthatallowsyouto:˜h Nn `Ð ·AÔÐRunthree instancesofOpenVMSonan AlphaServerÔ(8400 `¨ ·EÔ¨Runtwo instancesofOpenVMSonan AlphaServer8200 `' ·EÔ'Runtwo instancesofOpenVMSonan AlphaServer4100 `¦ ·,Ô¦ReassignCPUsbetween instances `& ·EÔ&Perform independentbootingandshutdownof instances `¥ ·?Ô¥Usesharedmemoryfor communicationbetweenin-Ôþstances `} ·EÔ}Cluster instanceswithinanOpenVMSGalaxyusingthe/ÔÕsharedmemorycluster interconnect `U ·7ÔUCluster instanceswith non-Galaxysystems `Ô ·AÔÔCreate applicationsusingOpenVMSGalaxyAPIsforCÔ-resource management,event notification,lockingforFÔ…synchronization,andsharedmemoryforglobalsections ` ·JÔUsetheGalaxy ConfigurationUtilitytoviewandcontrol+Ô]theOpenVMSGalaxy environment `Ü ·BÔÜRunasingle-instanceOpenVMSGalaxyonanyAlpha/Ô5systemfor application development qWiÚ%--O 3.2OpenVMS!Galaxy!Configurations D*€ D*‚ D*„ [ ]j! �31OÐ3.1BIsanOpenVMSGalaxyforYou?JOUFor companieslookingtoimprovetheirabilitytomanageIO­unpredictable, variable,orgrowingIT workloads,OpenVMSIOGalaxy technologyprovidesthemostflexiblewaytody-EO^ namically reconfigureandmanagesystem resources.,AnIO· integratedhardwareandsoftware solution,OpenVMSGalaxyMOallowssystemmanagerstoperformtaskssuchas reassigningKOh individualCPUsthroughasimpledraganddrop procedure.¤kÚõzEOƒAnOpenVMSGalaxy computing environmentisidealfor5OÜhigh-availability applications,suchas:òlÚæÈ `Ð ·ÔÐDatabaseservers `O ·*ÔO Transaction processingsystems `Ï ·ÔÏData Warehousing `N ·ÔNDataMining `Í ·ÔÍInternetserversþm °ÔJOƒ Also,pointoutsomeexamplesofwhenanOpenVMSGalaxyDOÜ isNOTtheanswer./Forexample:/singlestreamnon-JO5 threaded computation, situationswherethe individualCPUsOO� mustbe physicallyseparatetobenearother equipment,suchOOæ asforprocesscontrol.+Perhapsjustsaythatif traditionalMO> SMPwouldnotworkatallthenOpenVMSGalaxyisnottheO— answer.Ân ¥˜>OÐ3.1.1BWhyaGalaxyisaGoodBusinessChoiceGO4 Tobe supplied:'InfoaboutmixedversionsandrollingOŒ upgrades.èoÚN¾COƒAnOpenVMSGalaxy computing environmentisanatu-JOÜral evolutionforcurrentOpenVMSuserswithclustersor1O5multiplesparsely configuredsystemsµpúõ‹JOƒAnOpenVMSGalaxyis attractiveforgrowing organizationsAOÜwithvaryingworkloads-predictableor unpredictable§qÚM}KOÐ3.1.2BThingstoConsiderIfYouWanttoCreateaGalaxy2O4 Thissectionneedstobe developed.—rÚõmJOƒWhenyouplantocreateanOpenVMSGalaxy,youneedto#OÜconsiderthe following:RsÚé( `Ð ·ÔÐHaveenoughCPUs?TtÚû* `â ·ÔâHaveenoughmemory?JuÚ{  ÔbEnoughI/O adapters?avÚû7 `â ·,ÔâHowto configureI/O adapters?bwÚû8 `â ·-ÔâHowto configuresystemsdisks? ³  xÚð8OÐ3.2BPossibleOpenVMSGalaxyConfigurationsEOU TBS:Inthissection,giveanoverviewofthemod-?O­ elsof computing..Thendescribehowthemodels4O "transform"intoGalaxyconfigurations.Þy N´FOƒAnOpenVMSGalaxy computing environmentlets customersKOÜdecidehowmuch cooperationexistsbetween instancesina#O5singlecomputersystem.ÝzÚN³OƒInaƒ shared-nothing/“ƒ computingmodel,the instancesdoKOÜnotshareany resources; operationsareisolatedfromoneO5another.Â{ãõ˜OƒInaƒ shared-partial2jƒ computingmodel,the instancesshare?OÜsome resourcesand cooperateinalimitedway./|ã¦OƒInaƒ shared-everything+ƒmodel,the instances cooperateNOÜfullyandshareall available resources,tothepointwherePO5the operatingsystempresentsasinglecohesiveentitytotheO�network.š}ÚõpAOƒ Tobe supplied:,Expandthe descriptionsofthese/OÜ modelsinthe following sections.U~! V+1OÐ3.2.1BShared-Nothing ComputingModelMO4Inasharednothingconfiguration,the instancesofOpenVMSLOŒare completely independentofeachotherandare connectedMOåthroughexternalinterconnects,asthoughtheywereseparateO= computers.+! ¦KOƒWithAPMP,all availablememoryis allocatedintoprivateMOÜmemoryforeachinstanceofOpenVMS.EachinstancehasitsNO5ownsetofCPUsandan appropriateamountofI/O resourcesO�assignedtoit.[�Ú¼11O£3.2.2BShared-Partial ComputingModel^ƒÚ¼44O£3.2.3BShared-Everything ComputingModel # !X…Ú¼..O£3.3B ImportantCluster Information±†Úh‡ `Ð ·3ÔÐ EverythingshouldworkinInstance0 `O ·>ÔOSomethingsmightnotworkinnon-0 instances _ ! "¶‡ ÆŒ,OÐ3.4BSCSIClusterConsiderationsLOU PointtotheOpenVMSClusterSystemsbookfordevicenam-O­ inginfo.¥ˆÚ){IO·IfyouarecreatinganOpenVMSGalaxywithsharedSCSI2Obuses,youmustnotethe following:ð‰ÚNÆJOƒForOpenVMSto correctlygivetheSCSIdevicesthesameNOÜnameoneach instance,youwilllikelyneedtoutilizethe.O5 device-namingfeatureofOpenVMS.?Š NOƒForexample,assumethatyouhavethe followingadaptersonEOÜyoursystemwhenyouentertheSHOWCONFIGcommand:,Oa PKA0& (embedded%SCSI&for%CDROM)/O© PKB0& (UltraSCSI% controller%KZPxxx)'Oñ PKC0& (UltraSCSI% controller)*‹Ú»FOƒWhenyoumakethissystema two-instanceGalaxy,youOÜ ????????????Oa Instance%0'O© PKA0K (UltraSCSI& controller)O Instance%1,OZ PKA0K (embedded%SCSI%for%CDROM)'O¢ PKB0K (UltraSCSI& controller)œŒ! õrNOƒYoursharedSCSIwillbe connectedfromPKA0oninstance0$OÜtoPKB0oninstance1.)� ¦ÿJOƒIfyou initializethesystemwiththeLP_COUNT environm-UOÜnetvariablesetto0,youwillnotbeabletobootOpenVMSonEO5thesystemunlesstheSYSGEN parameter STARTUP_P1isO�settoMINIMUM.tŽÿÿJHOƒThisisbecause,withtheLP_COUNTvariablesetto0,GOÜyouwillnohavePKB connectedtoPKC,andtheSCSINO5 device-namingthatwassetupfor initializingwithmultipleNO� partitionsisnotcorrectfor initializingwiththeLP_COUNTOævariablesetto0.T�Ú¦*IOƒDuringthedevice configurationthatoccursduringboot,FOÜOpenVMSwillnoticethatPKA0andPKB0are connectedIO5 together.*OpenVMSexpectsthateachdevicehasthesameRO� allocationclassandnames,butinthiscase-theywillnot.�ü ‚ÚIOƒThedevicenamingwhichwassetupforthe2instanceQOÜGalaxywillnotfunction correctlysincetheconsolenamingof+O5the controllershas changed...RO¹ Also,%there%appears&to&be&a%problem%with&setting%SCSI%IDs%forQO SCSI&adapters&in&the%console.JThis%is% something%that%needs%toUOI be%done&for%SCSI&cluster.KIt% currently%appears%that&on&the%4100,WO‘ you%must%set%instance%1%to%SCSI&id&6%and&leave&instance&1%at%7.POÙ We%don't%yet% understand%this&behavior&with%the&console,&so&IRO! can't%provide&a%detailed%release%note&here%-%only&that%we%may$Oi need& something%for%FT3. _"!#¼‘ú)’@OÐ3.5BSecurityConsiderationsinanOpenVMSGalaxy ü( Computing Environment?O­OpenVMS Galaxy instances executingin a shared-EO everythingcluster environment, inwhichallsecurityKO^databasefilesaresharedbetweenall instances, automati-PO·callyprovidea consistentviewofallGalaxy-relatedsecurityO profiles.–’ ÿlSOƒIfyouchoosenottoshareallsecuritydatabasefilesthrough-SOÜoutallGalaxy instances,a consistentsecurityprofilecanonlyOO5beachieved manually.'Changestoanobject'ssecurityprofileMO�mustbefollowedbysimilarchangesonall instanceswhere*Oæthisobjectcanbe accessed.ó“ WÉPOƒBecauseoftheneedto propagatechanges manually,itisun-OOÜlikelythatsucha configurationwouldeverbecoveredbyaLO5USC2 evaluationorbysimilar evaluationsfromotherau-JO� thorities., Organizationsthatrequire operatingsystemstoOOæhavesecurity evaluationsshouldensurethatall instancesinEO>asingleOpenVMSGalaxybelongtothesamecluster. h # "$Ž”ÚAdEOÐ3.6B ImportantInfoThatNeedstobeLocatedintheü( AppropriateChapters€•ÚMV'OÐ3.6.1BNewSYSGEN parameter/O4The GLX_INST_TMOSYSGEN parameter:g–Úÿ=FOƒEachSHARINGmemberticksa heartbeatcellinsharedJOÜmemorywhichtheother instanceswatch.*Ifan instance'sEO5 heartbeatstopstickingfor GLX_INST_TMO milliseconds,NO�thatinstancewillbeassumedtobedeadandremovedasaOæsharingmember.— °ðIOƒIfforexample,youCTRL-PasharingmemberforlongerGOÜthat GLX_INST_TMO milliseconds,uponissuingaContinueGO5commandfromtheconsole,theinstancewill immediatlyHO�bugcheckwithaGLXEXIT bugcheck.)ThisisverysimilarOOætothebehaviorofanOpenVMSclusterthatwouldresultinaGO>CLUEXITbugcheckifaclustermemberwasinaCTRL-P;O—stateforlongerthan RECNXINTERVALseconds.ñ˜ NÇJOƒThesharingmembersallusethesamevalueof GLX_INST_OOÜTMO.Thevalueusedisthesmallestvalueofanynodethat.O5hasEVERbootedintotheGalaxy\™! V2$OÐ3.6.2BSystem Auto-ActionGO4Uponsystem power-up,ifthe AUTO_ACTIONconsoleenvi-NOŒronmentvariableissettoBOOTorRESTARTforinstance0,JOåthentheGALAXYcommandwill automaticallybeissuedand/O=instance0willattempttoboot.OšÚ¦%FOƒThesettingof AUTO_ACTIONintheconsole environmentOOÜ variablesfortheother instanceswilldictatetheirbehaviorHO5upontheissuingoftheGALAXYcomamnd(whetheritisHO�issued automaticallyorbytheuserfromthe console).ƒ›ÿÿYQOƒTosetupyoursystemforthisfeature,youmustsetthecon-COÜsole environmentvariable "AUTO_ACTION"to "RESTART"MO5or"BOOT"oneach instance,andbesuretospecifyappro-BO�priatevaluesforthe BOOT_OSFLAGSand BOOTDEF_DEV6Oæ environment variablesforeach instance.úœ Ð:OÐ3.6.3BChangingconsole environment variablesBO4Onceyouhave establishedtheinitialsetofLP_ ý?*>4environ-GOŒment variablesforOpenVMSGalaxy operationandbootedJOåyoursystem,changing environmentvariablevaluesrequiresMO=thatyoufirst re-initializethesystem,changethevalues,EO–and re-initializeagain..WrappingthechangesbetweenQOîINITsisrequiredtoproperly propagatethenewvaluestoallOG partitions. ÔÉ_UÌNote É_JÔQForthe4100,noINITisneededtostartbutyoumust8Ô©changethese variablesonboth instances. Ôô—¦�Ú¥|"OÐ3.6.4B CONFIGUREGALAXY>O4TheGCUcannow beinvokedviaDCL commands:OŒ CONFIGUREGALAXY. H$#%cžÚ´95O 4.2OpenVMS!Galaxy! Licensing! InformationCO‘TheOpenVMSGalaxySoftware ArchitectureonOpenVMSGOê(OpenVMSGalaxy)isasystem integratedproduct(SIP).JOBThatis,OpenVMSGalaxycodeis integratedand delivered0O›withtheOpenVMS operatingsystem.ËŸ W¡ OpenVMSVersion7.2CD-ROMs ò>. _ % $&¾ ÚÆ”7OÐ4.1BOpenVMSGalaxy Licensing RequirementsFOUThe followinglist summarizesOpenVMSGalaxy licensingO­ requirements:�¡! ps `Ð ·BÔÐOneOpenVMS OperatingSystemLicenseforaGalaxyÔ(system `¨ ·IÔ¨OneSMP ExtensionLicenseforeachCPUafterthefirst ÔCPU `€ ·FÔ€OneOpenVMSGalaxyLicenseforeachCPUinaGalaxyÔØsystem `W ·IÔWNochangestohowCompaqlayeredproductsare licensed:}¢ÚAS-YÐOnecapacitylicensepersystem&Y(Oneuserlicenseperuse†£Úõ\KOƒThe followingsectionsdescribethese requirementsinmoreOÜdetail.)¤ÿþÿ4OÐ4.1.1BOpenVMS OperatingSystemLicenseHO4Whenan AlphaServersystemis configuredasanOpenVMSJOŒGalaxysystem,therearenochangesinhowasystemis9OålicensedfortheOpenVMS operatingsystem.Ø¥ N®KOƒOneOpenVMSBaseLicenseisrequiredfortheGalaxysys-NOÜtem,plusoneSMP ExtensionLicenseforeachCPUaftertheO5firstCPU.ï¦ ¥Å)OÐ4.1.2BOpenVMSGalaxyLicenseMO4Inordertocreateandrunmultiple instances,oneOpenVMSOOŒGalaxyLicenseisrequiredforeachCPUinaGalaxysystem.¾§Þõ”LOƒLicenserightsforrunningasingle-instanceGalaxyonanyHOÜAlphasystemareprovidedbytheOpenVMSBaseLicense.&¨! þü4OÐ4.1.3BOpenVMSLayeredProductsLicenseHO4CompaqsoftwarelayeredproductsonOpenVMSGalaxycon-QOŒ figurationscontinuetousestandardlicensetypes:' Traditional,/Oå ConcurrentUse,andPersonalUse.© ¢é `Ð ·FÔÐOne TraditionalcapacityLicensewillcontinuetoli-JÔ(censethesystem, regardlessofthenumberof instances.LÔ�ThelicenseisbasedonthesystemclassofthehardwareÔÚsystem. `Y ·EÔY ConcurrentUseLicenseswillcontinuetolicenseone,Ô± concurrentuseoftheproduct. `1 ·JÔ1PersonalUseLicenseswillcontinuetolicenseonenamed Ô‰useronthesystem. Ü&%'ɪöП5OÐ4.2B ClusteringOpenVMSGalaxy InstancesDOU InstancesinanOpenVMSGalaxy computing environmentLO­canbe clusteredwithother instancesinasinglesystem,LOwith instancesinotherGalaxysystems,orwith non-GalaxyIO^systems..Eachtypeof clusteringhas different licensingEO· requirements,as describedinthe following sections.o«ÚVE2OÐ4.2.1B ClusteringinaGalaxySystemEO4InanOpenVMSGalaxy computing environment, instancesMOŒcanbe clusteredwithother instanceswithinaGalaxysys-FOåtem.+ Clustered instancesusethe shared-memorycluster;O= interconnectto communicatewitheachother.¿¬! õ•POƒThe licensingand functionalityfor clusteringwithinaGalaxyEOÜsystemisprovidedundertheOpenVMSGalaxyLicense.¨­ ¯~7OÐ4.2.2B ClusteringOutsideaGalaxySystemAO4 InstancesinanOpenVMSGalaxy computingenviron-IOŒmentcanbe clusteredwith instancesinanotherOpenVMSLOåGalaxysystemorwithclusternodesin non-Galaxysystems.PO= Instances clusteredoutsideofaGalaxysystemuse traditional!O–clusterinterconnects.#® ¦ùLOƒEachsystemthatis clusteredwithanothersystemmustbeIOÜlicensedforOpenVMSCluster Software.) ClusteringoutsideJO5theOpenVMSGalaxysystemisnotcoveredbytheOpenVMSO�GalaxyLicense. + '&(Ư М!OÐ4.3BLicense DatabasesGOUWhenanOpenVMSGalaxysystemis configuredwithmoreRO­thanone instance,alicensedatabasemustbesetupforeachMO independentinstanceorclusterof instances.(ThePAKsrep-KO^ resentingthelicensesontheOpenVMSGalaxy configurationJO·maybeloadedonmultiplelicense databases,asfollows:‡°úA] `Ð ·@ÔÐOpenVMSBase,SMP Extensions,andOpenVMSGalaxyÔ(Licenses ±Ü]vBÔbForfulluseoftheOpenVMSGalaxyfunctionality,<Ô»thePAKs representingyourOpenVMSBase,SMP?Ô Extensions,andOpenVMSGalaxyLicensesmustbeCÔlloadedoneachlicensedatabasewithintheOpenVMS(ÔÅGalaxyonasinglesystem. `D ·CÔDCompaqLayeredProduct TraditionalCapacityLicenses²Þ¬ÜGÔbThePAKs representingtheselicensescanbeloadedonFÔ»eachlicensedatabasewithintheOpenVMSGalaxyonaÔsinglesystem. `“ ·+Ô“Compaq ConcurrentUseLicenses·³ÚÔ�GÔbThePAKs representingtheselicensescanbeloadedonFÔ»thelicensedatabasewherethelicensewillbeused.'´ ýCÔbForPAKs representingmultiple concurrentuses(forFÔ»example,a50_uselicense)thePAKcanbeloadedonDÔmultiplelicense databaseswithintheOpenVMSGalaxyHÔlonasinglesystem.)However,thePAKmustbemodifiedMÔÅdownoneachlicensedatabasesothatthetotalnumberofPÔlicenseunitsdoesnotexceedthetotallicenseunitsontheÔvLicensePAK. `õ ·)ÔõCompaqPersonalUseLicenses@µÞ…GÔbThePAKs representingtheselicensescanbeloadedonFÔ»eachlicensedatabasewithintheOpenVMSGalaxyonaHÔsinglesystem;however,thenumberofactualusesmustAÔlnotexceedthelicensednumberofpersonaluses. " (')™¶Úno7OÐ4.4BOpenVMSGalaxyLicensePAKsandLMF8OUOpenVMSGalaxyPAKnamesareasfollows:"·Ú™ø `Ð ·:ÔÐOpenVMS OperatingSystemBasePAK:OPENVMS- Ô(ALPHA(baselicense) `¨ ·:Ô¨OpenVMS OperatingSystemUserPAK:OPENVMS-Ô ALPHA-USER `€ ·/Ô€OpenVMSGalaxyPAK:OPENVMS-GALAXYP¸Úÿ&@OƒOpenVMSGalaxy customersmusthaveatleastone>OÜ OPENVMS-ALPHAPAK,plusone additionalOPENVMS-IO5ALPHAPAKforeach additional processor(CPU)aftertheLO�firstCPU(whichisincludedintheBase OperatingSystemOæ License).P¹öÿ&5OƒThe OPENVMS-ALPHAandOPENVMS-ALPHA-USERJOÜPAKscannowbesharedbymultipleGalaxy instances.*ToIO5 implementthisintheLicense ManagementFacility(LMF),FO�includeallOpenVMSGalaxyinstancenamesinthePAKOæINCLUDElist.Gº JOƒForexample,supposethatacustomerhasasystemnamed?OÜANDA1AinanOpenVMSCluster.'The OPENVMS-ALPHALO5licensePAK currentlyhasanINCLUDElistonitthathasIO�SCSnodenameANDA1Ainit.+IfthatsystemischangedCOætoanOpenVMSGalaxyrunningthree instancesnamedANDA1A,ANDA2A,andANDA3A,the OPENVMS-ALPHAPO—licensePAKmustbemodifiedsothatall instancescanshare0OïtheNO_SHARE OPENVMS-ALPHAlicense.í»ÚÂÃ?OƒThecommandtomodifythe OPENVMS-ALPHAlicenseOÜPAKis:EOa $&LICENSE%MODIFY&$OPENVMS-ALPHA/AUTHORIZATION=blahblah%--O© #_$/INCLUDE=3D(ANDA1A,ANDA2A,ANDA3A)/¼ã¦JOƒSincethisexampleassumesthatANDA1AwasalreadyinaOOÜcluster,the authorizationnumberisrequiredtoidentifytheCO5onePAKofmany OPENVMS-ALPHAlicensePAKsinthe)O�licensedatabasefile(LDB).J½Úœ  Oƒ TBS-Modifydowninfo  )(*í¾ÚÆÃ@OÐ4.5BForMore InformationAboutOpenVMS LicensingAOUFor informationaboutusingtheOpenVMS LicensingBO­ Management Facility,refertothe followingbooks:™¿ Êo `Ð ·<ÔÐ OpenVMSAlphaUpgradeand InstallationManual,Ðcon-GÔ(tainsnotesand supplemental informationaboutlicenses%Ô�and licensing procedures. ` ·7Ô OpenVMSLicense ManagementUtilityManual…containsEÔY complete,detailed informationaboutOpenVMS licensingÔ± procedures. ‚*)+hÀ† >>OüPartII7CreatinganOpenVMSGalaxy Environment +*,üÁÚhÒ3O 5.@Creating(an(OpenVMS(Galaxy(on(anOr AlphaServer!8400HO÷Thischapter describeshowtocreateanOpenVMSGalaxyOÐ5.2.1B InstallingtheKFE72-DAConsole Subsystem<(HardwareJOŒTheKFE72-DAisthesetofEISA-busmodulesthatestab-LOålishesan additionalconsoleport.'OneKFE72-DAmoduleset2O=isrequiredper secondary partition.qÛÚœGGOƒTheKFE72-DAcontainsthreeEISAmodulesthatprovide:ïÜÚæÅ `Ð ·ÔÐTwoCOMports `O · ÔOAkeyboard interface `Ï ·ÔÏAmouse interface `N ·ÔNAsmallspeaker `Í ·ÔÍAnEthernetport.ÝñNçKOƒTheCOM-1portisusedfortheconsoleserialline.-ThePOÜEthernetportcanbeusedasanetwork connectionoritcanLO5be terminated.'Themouseandkeyboardportsarenotused.›Þ qJOƒTheKFE72-DAmustbepluggedintothebottomthreeEISAPOÜslots.(Forthe AlphaServer8400thisrequiresthatyouattachMO5ahosefromyourI/OporttoaDWLPBPCIcardcage.(TheSO�KFE72-DAmodulesetmustbe installedinslots0,1,and2ofLOæthecardcage.)TheKFE72'sSIO(a.k.a.(Bridge)moduleen-NO>ablestheEISAslotswhicharepartofthe combinationPCILO—/EISA backplane.'Theothertwomodulesknownasthe"DataQOïPortModule"and "Beeper97"goinslots1and2 respectively.Nß `$+OÐ5.2.2BUsingaTerminalServerMO4YoumaywanttobringyourconsolelinestogetherusingaKOŒterminalserver.)Forexample,usea DECserver200toallowLOå reverse-LATaccesstoeachconsoleoverthenetwork.'WhileNO=thisisnotstrictly required,itgreatly simplifiesOpenVMSIO–Galaxy configuration management.(Refertothe appropriateJOîproduct documentationfordetailsabout configuringaLAT4OGServerorotherterminal concentrator.¨à ¯~;OÐ5.2.3BRecommendationsfor ConfiguringConsole<( SubsystemsJOŒEach additionalconsolerequiresaseparateKFE72-DAsub-NOåsystem installedinaseparateDWLPBcardcagewithahoseKO= connectingittoaseparateI/OmoduleoftypeKFTIAorLO–KFTHA.IfyouareusingaKFTIA,itmustbeinslot8.åá N»OOƒ AdditionalKFTIAI/OmodulesmustbeinthenextlowerslotOOÜorslots,withKFTHAI/OmodulesinthenextlowerslotorO5slotsafterthat.³âÚõ‰KOƒYoucanuseany combinationofthesetwoI/Omodulesas>OÜlongasyoufollowthisslot assignmentrule.Íã N£FOƒThe AlphaServer8400supportsamaximumofthreeI/OLOÜmodules.( Attemptingto configuremorethanthreeisunsup-O5ported.šäúÿpIOƒWhen configuringaconsole subsystem,theI/Ohosecon-HOÜnectingtheI/O ProcessorandDWLPBcardcagemustbeIO5pluggedintothelowesthoseport.(NotjustthelowestØ5 avail-O� ablePô�hoseport,buttheabsolutefirsthoseport;theoneclosest(Oætothetopofthemodule.�åÚõeIOƒKFE72-DAmodulesmustoccupyslots0,1,and2oftheOÜDWLPBcardcage.æ NêLOƒTheconsoleseriallineis connectedwithanH8571-Jcon-ROÜnectoradapterthatplugsintotherighthandseriallineportLO5whenviewedfromtherearofthemachine.&ThisisCOM-1.NçñV$*OÐ5.2.4B InstallingEISADevicesNO4Plug-inEISAdevicescanonlybe configuredin partition0.OOŒAfter installingEISAdevices,theconsolewillissueames-MOåsage requestingthatyouruntheEISA ConfigurationUtilityO=(ECU).OèÚœ%%OƒRuntheECUasfollows:„é! YZ:`Ð1.:ShutdownallOpenVMSGalaxy instances.S`O2.:Besureyourfloppydiskdriveisproperly connectedtotheHÔ¨primary partitions hardware.( TypicallythedrivecanbeGÔcabledintothe ConnectorModule ("Beeper"partnumber)ÔY 54-25133-01)inPCIslot2.A`Ø3.:Insertthediskette containingtheECUimage.K`W4.:Issuethe followingcommandsfromtheprimaryconsole:%ùÜ P00>>>&SET% ARC_ENABLE&ONù$ P00>>>& INITIALIZEùl P00>>>&RUN%ECUN`ì5.:Followthe proceduresoutlinedbytheECUandexitwhenÔDdone.`Ã6.:P00>>>boot%`C7.:$@SYS$SYSTEM:SHUTDOWN*`Â8.:P00>>>SET ARC_ENABLEOFF `A9.:P00>>> INITIALIZE`Á10.P00>>>GALAXY+`@11.ReboottheOpenVMSGalaxyÍêÿW£JOƒTherearetwoversionsoftheECU,onethatrunsonaKOÜgraphicsterminalandanotherthatrunson charactercellPO5 terminals.)Bothversionsareonthe diskette,andtheconsoleFO� determineswhichonetorun.+ForOpenVMSGalaxysys-QOætems,theprimaryconsolewillalwaysbeaserialdevicewith'O>a charactercell terminal.ë± ÂïMOƒIftheECUisnotrun,OpenVMSwilldisplaythe followingOÜmessage:Fza %SYSTEM-I-NOCONFIGDATA,&IRQ% Configuration&data%for&EISAJ © slot%xxx&was%not%found,&please%run%the&ECU%and%reboot.­ì õƒTOƒIfyouignorethismessage,thesystemwillboot,buttheplug-/OÜinEISAdeviceswillbeignored.íè¦ñIOƒOnceyouhave configuredandsetuptheOpenVMSGalaxyLOÜhardwareas describedinintheprevious sections,performHO5the followingstepstoinstallandbootOpenVMSGalaxyO� instances. é.-/ÛîþƱ0OÐ5.3BStep3:'CreateASystemDiskBOUDecidewhethertouseasystemdiskperinstance RU or·UtouseaO­clustercommondiskôïÞNÊHOƒAnew SECURITY.EXEisrequiredforallclustermembersIOÜrunningaversionpriortoOpenVMSV7.2thatsharethe9O5sameVMS$OBJECTS.DATwithGalaxy instances. }/.0¾ðÚД>OÐ5.4BStep4:'InstallOpenVMSAlphaVersion7.2GOUNospecial installation proceduresarerequiredtorunDO­OpenVMSGalaxy software..Galaxy functionalityisin-MOcludedinthebase operatingsystemandcanbeenabledorHO^disabledusingtheconsolecommandandsystem parameter6O·values describedlaterinthischapter.õñÚNËHOƒFormore informationabout installingtheOpenVMSAlpha&OÜ operatingsystem,seethe&øÜ OpenVMSAlphaVersion7.2,O5 Upgradeand InstallationManual "5.†òÚM\8OÐ5.4.1BOpenVMSGalaxy Licensing Information O4SeeÞ4Section4.1.*òÞ÷|?  ˜2~ Ú‘ T'OãTable5-1:7UsefulIntegers Oþù Oh1 MegabytesKh0x100000Oá2 MegabytesKá0x200000O[4 MegabytesK[0x400000OÕ8 MegabytesKÕ0x800000OO16 MegabytesKO0x1000000OÈ32 MegabytesKÈ0x2000000OB64 MegabytesKB0x4000000O¼128 MegabytesK¼0x8000000O6256 MegabytesK60x10000000O¯448 MegabytesK¯0x1C000000O)512 MegabytesK)0x20000000O£1GigabyteK£0x40000000O2 GigabytesK0x80000000O—4 GigabytesK—0x100000000O8 GigabytesK0x200000000OŠ16 GigabytesKŠ0x400000000O 32 GigabytesK 0x800000000O~ 64 GigabytesK~ 0x1000000000O÷ 128 GigabytesK÷ 0x2000000000Oq 256 GigabytesKq 0x4000000000Oë 512 GigabytesKë 0x8000000000Oe 1TerabyteKe 0x10000000000 O‹ ù  ˆ 0/1Üóï)²/OÐ5.5BStep5:'UpgradetheFirmwareOƒNotethattheOpenVMSGalaxyfirmware(GALAXY_GOÜ FIRM_072.KIT)islocatedontheAlphaCD2forOpenVMSO5Version7.2.øÚÖ(OƒUsethe following commands:4O P00>>>%BOOT%-FLAGS%0,80%cd_device_name OP . O˜ . Oà .8O( Bootfile:%#[GALAXY_FIRM_072.KIT]AS8_G53_27.EXE Op . O¸ . O .xùÿ.NJOƒWhenthefirmwareupdatehas completed,youmustrebuildAOÜtheEEPROMformatoneach even-numbered processorO5moduleasfollows:O¹ P00>>>%SET&CPUJ0O P00>>>%BUILD%-EOk P00>>>%SET&CPUJ2O² P00>>>%BUILD%-E O . Od . O¬ .O P00>>>INITÅúÚõ›KOƒNotethataMOPbootableversionofthefirmwareupdate,-OÜ #[GALAXY_FIRM_072.KIT]AS8_G53_27.SYS#jÜ,isalsoontheCD. t103nû ”D4OÐ5.6BStep6:'Set Environment VariablesKOUWhenyouhaveupgradedthefirmwareonallofyourpro-IO­cessormodules,youcancreatetheGalaxy-specificenvi-KOronment variablesasshowninthe followingexample.)ThisNO^exampleassumesyouare configuringa2 instance,8CPU,1>>%create&-nv%lp_count j< 2.O„ P00>>>%create&-nv% lp_cpu_mask0»1/OÌ P00>>>%create&-nv% lp_cpu_mask1»fe/O P00>>>%create&-nv% lp_io_mask0à100.O\ P00>>>%create&-nv% lp_io_mask1à805O¤ P00>>>%create&-nv% lp_mem_size0»100000005Oì P00>>>%create&-nv% lp_mem_size1»10000000;O3 P00>>>%create&-nv%lp_shared_mem_sizeK20000000O{ P00>>>%initäü NºKOƒOnceyoucreatethese variables,youcanuseconsoleSETKOÜcommandsto manipulatethem.'These variablesneedonlybe$O5createdon processor0.šýÚõpJOƒThe following descriptionsgivedetailed informationabout&OÜeach environment variable.Èþ ¦žOÅLP_COUNTTO4Ifsettozero,thesystemwillboota traditionalSMPconfigu-8O�rationonly.&GalaxyconsolemodeisOFF.qÿ ÿGROƒIfsettoanon-zerovalue,theGalaxyfeatureswillbeused,POÜandtheGalaxy variableswillbe interpreted.(TheexactvalueGO5ofLP_COUNT representsthenumberofGalaxy partitionsNO�theconsoleshouldexpect.( Currently,thisnumbermustbe0Oæor2.õ WËMOƒNotethatifyouassign resourcesforthree partitionsandROÜsetthisvariabletotwo,the remaining resourceswillbeleftNO5 unassigned.' UnassignedCPUswillbeassignedto partition0.KO�Youmayalsocreatethe variablesforthemaximumnumberROæof partitionsaheadoftimeandsimplynotassign resourcestoAO>them(setthemtonon-zerovalues)untilneeded.éÚ¿(OÅ LP_CPU_MASK partitionnumberIO4Thisbit-mask determineswhichCPUsaretobe initiallyGO�assignedtothe specifiedGalaxy partitionnumber./TheHOå AlphaServer8400consolechoosesthefirst even-numberedGO>CPUasitsprimary..Keepthisinmindwhen assigningMO–the resources(inotherwords,donotassignonlyanodd-+OïnumberedCPUtoa partition).°Ú¦†'OÅ LP_IO_MASK partitionnumberLO4These variablesassignI/OmodulesbyslotnumbertoeachO� instance.ñÚèÇ `Ð ·8ÔÐ100 representstheI/Omoduleinslot8 `O ·7ÔO80 representstheI/Omoduleinslot7 `Ï ·7ÔÏ40 representstheI/Omoduleinslot6ƒÚõYJOƒThesearetheonlyvalid assignmentsforthe AlphaServerOÜ8400.â N¸OOƒYoucanassignmorethanoneI/Omoduletoaninstanceus-NOÜingthesemasks,buteachGalaxyinstancerequiresatleastO5oneI/Omodule.Ù ¯¯(OÅ LP_MEM_SIZE partitionnumberLO4These variablesallocateaspecificamountofprivatemem-TO�oryforthe specified instance.'Itis imperativethatyoucreateMOåthese variablesusingpropervaluesfortheamountofmem-JO>oryinyoursystemandthedesired assignmentsforeachO– instance.'Refertoä–Table5-1]–forcommonvalues.*äYa? wÚœMMOƒSeealsothesharedmemoryvariableonthe followingline.Ú§õOÅLP_SHARED_MEM_SIZEJO4Thisvariable allocatesmemoryforuseassharedmemory.O�Refertoˆ�Table5-1�forcommonvalues. Ôg]Tips gBÔ–Sharedmemorymustbeassignedin multiplesof8DÔï megabytesandallvaluesare expressedin hexadeci-ÔGmalbytes.EÔÁYoucandefineonlytheamountofsharedmemorytoCÔuse,andleavetheother lp_mem_size variablesun-FÔrdefined.+Thiswillcausetheconsoletoallocatethe?ÔËsharedmemoryfromthehighaddressspace,andBÔ#splitthe remainingmemoryequallyamongthenum-JÔ|berof partitions specifiedbythelp_count variable.(IfFÔÔyoualso explicitlyassignmemorytoaspecificpar-EÔ-titionusinga lp_mem_size variable,butleaveotherBÔ† partitionmemory assignments undefined,theconsoleBÔÞwillagainassignthememory fragmentsforsharedDÔ7memoryandany partitionswithexplicit assignments,CÔ�thensplitandassignthe remainingmemorytoany>Ôè remaining partitionsnothavingexplicitmemoryÔ@ assignments. Ô‹—*ˆPa? – ! Wl3OÅ bootdef_devand boot_osflags variablesRO4Youshouldsetthese variablesoneachofyourGalaxyconsolesKO�priortobootingtoensurethatAUTOGENreboots correctlyTOåwhenitneedstorebootthesystemafteraninitial installationHO>andafterasystemcrashoroperator requestedreboot.á Ú·8OÐ5.6.1BGalaxy Environment VariablesExampleO# P00>>>%SHOW%GALAXY*OŒ lp_count%21OÔ lp_shared_mem_size%20000000p(512&MB)+O lp_mem_size0%10000000%(256%MB)+Od lp_mem_size1%10000000%(256%MB)#O¬ lp_cpu_mask0%1%(CPU&0)'Oô lp_cpu_mask1%fe%(CPUs%1-7)6O< lp_io_mask0%100%(I/O%module%in%slot%8)5O„ lp_io_mask1%80%(I/O&module%in%slot&7)Oí P00>>í Ú¥Ã,OÐ5.6.2BTableofUsefulIntegersO4Table5-19Ï4listscommonvaluesforGalaxy environmentJOŒ variables.'Allvaluesare expressedin hexadecimalbytes.* O÷e?  0314÷  (Í@O£5.7BStep7:'Startthe SecondaryConsoleDevicesHO(IftheKFE72-DAwasever configuredfor Windows-NT,itRO€probablyexpectstofindthevideoboardandwillhangifoneMOÙisnotpresent.'Thisisacommon occurrencewhen configur-KO1inganOpenVMSGalaxy.'Aconsolecommandcanbeusedto5OŠsetthemodeof operationasfollows:&O P00>>>%SET&CONSOLE%SERIALþã‚ÔKO·WhenyouissuethiscommandtotheprimaryconsolepriorMOto initializingthe secondary consoles,thesettingwillbe>>%SHOW%NETWORK)OÔ P00>>>%SET& EWA0_MODE%TWISTED ÿUMOƒThefirstcommanddisplaysalistof availablenetworkde-HOÜvices.+Thesecondcommand establishesthedefaultmediaMO5typeforthe specifieddevice(EWA0inthis example).*ThisUO�shouldbedoneforallEthernetdevicespriorto initializingtheOæ secondary consoles.ÓïW©HOƒOnceyouhavesetyourconsolemodeandnetworkmediaPOÜtypes(ifused)youshould re-initializethesystemtoensurePO5thatthecurrentsettingsaresaved.(Ifyouhavealreadyde-OO�finedyourGalaxy partitions,youcan initializenow.*IfyouKOæhavenotdefinedyourGalaxy partitions,youshoulddefer'O>initializationuntillater.ƒÚ!YCOƒIfyouarereadyto initializethesystem,enter:O P00>>>%INITy! ÿOLOƒYoushouldseetheprimaryconsolerespondwithitsusualMOÜpower-up-self-test(POST)report.'ThiscouldtakeuptotwoNO5minutes.)IfyouhaveproperlydefinedtheGalaxy partitions,RO�onlytheI/Odevices associatedwiththeprimary partitionwillOæbevisible.³Úô‰@OƒToverifythat partitioninghas occurred,enter:O P00>>>%SHOW%DEVICE Oq orOÛ P00>>>%SHOW%NETWORK|Ú!R:OƒTo initializethe secondaryconsole,enter:O P00>>>%GALAXYÌÚê¢1OƒTheconsoledisplaysthe following:+O Partition%0:%Primary%CPU%=%0+OP Partition%1:%Primary%CPU%=%2GO˜ Partition%0:%Memory&Base%=% 000000000pSize&=% 010000000GOà Partition%1:%Memory&Base%=% 010000000pSize&=% 010000000@O( Shared%Memory&Base%=% 020000000pSize&=% 0100000000Op Galaxy% Configuration%Tree&=%12c000KO¸ starting%cpu%1%in%Galaxy%instance%1%at%address& 01000c001KO starting%cpu%2%in%Galaxy%instance%1%at%address& 01000c001KOH starting%cpu%3%in%Galaxy%instance%1%at%address& 01000c001KO� starting%cpu%4%in%Galaxy%instance%1%at%address& 01000c001KOØ starting%cpu%5%in%Galaxy%instance%1%at%address& 01000c001KO  starting%cpu%6%in%Galaxy%instance%1%at%address& 01000c001KOh starting%cpu%7%in%Galaxy%instance%1%at%address& 01000c001OÑ P00>>>ðñWÆ5OƒThiscommandmustbeenteredfromthe<ƒ primaryGalaxyOÜ consoleHDÜ.)IftheGalaxy partitionshavebeenproperlydefined,JO5andhardware resourceshavebeenproperly configured,youNO�shouldseetheprimaryconsolestartthe processorsassignedMOætoeach secondary partition.)Eachofthe secondaryconsoles:O>should initializewithinabouttwominutes.ñ! NÇSOƒIfoneormoreconsolesfailsto initialize,youshoulddouble-OOÜcheckyourhardware installation,Galaxy partition definitions,%O5andhardware assignments.%èþûOÐ5.7.1BConsoleHintsMO4Becausethe AlphaServer8400wasbuiltpriortotheGalaxyEOŒSoftware Architecture,OpenVMSGalaxyconsolefirmwareJOåandsystem operationsmustdealwithafew restrictions.½úõ“QOƒThe followinglistbriefly describessomethingsyoushouldbeBOÜawareofandsomethingsyoushouldavoiddoing:] û3 `Ð ·ÔÐDonotsettheÝÐ BOOT_RESET#2Ð environmentvariableto ¦Ð 1 ÆÐ.JÔ(Thiscauseseach secondaryconsoletoresetthebusbe-OÔ�forebooting,thus resettingall previouslybooted partitions.AÔÚRememberthatOpenVMSGalaxy partitionssharetheÔ2 hardware. `± ·HÔ±Bepatient.*Consoleinitialization,andsystem rebooting&Ô cantakeseveralminutes. `‰ ·@Ô‰ Donotattempttoabortafirmwareupdatepro-Ôâ cess!ÜçS²:ÔbThiscanleaveyoursystem seriouslyhung. `â ·4ÔâWhenupdatingconsole firmware,updateÀâ ALLCPUs pâatÔ:thesametime.ë ]ÁJÔbYoucannotruntwo differenttypesofCPUsortwodif-NÔ»ferentfirmware revisions.'Ifyoufailtoprovide consistentFÔfirmware revisions,thesystemwillhangon power-up. `“ ·Ô“Neverissuethe “ GALAXY%¡“commandfroma secondaryKÔëconsole.*Thiswill re-initializethesystem,andyouwill=ÔDneedtostartoverfromtheprimaryconsole. {435Úë3OÐ5.8BStep8:'BoottheOpenVMSGalaxyFOUWhenyouhave correctly installedtheGalaxyfirmwareOO­and configuredthe consoles,youcanboottheinitialGalaxy#O environmentasfollows:Þ ô´&OƒForeachGalaxy instance:PO P00>>>%B%-FL%0,1&DKA100%//%or%whatever%your&boot%device&is."Oq SYSBOOT>%SET%GALAXY&1OÛ SYSBOOT>%CONTINUEn ÚœDDOƒCongratulations!'YouhavecreatedanOpenVMSGalaxy. 546ü!ÚhÒ3O 6.@Creating(an(OpenVMS(Galaxy(on(anOr AlphaServer!8200HO÷Thischapter describeshowtocreateanOpenVMSGalaxyOÐ6.2.1B InstallingtheKFE72-DAConsole Subsystem<(HardwareJOŒTheKFE72-DAisthesetofEISA-busmodulesthatestab-LOålishesan additionalconsoleport.'OneKFE72-DAmoduleset2O=isrequiredper secondary partition.q2ÚœGGOƒTheKFE72-DAcontainsthreeEISAmodulesthatprovide:ï3ÚæÅ `Ð ·ÔÐTwoCOMports `O · ÔOAkeyboard interface `Ï ·ÔÏAmouse interface `N ·ÔNAsmallspeaker `Í ·ÔÍAnEthernetport.4ñNçKOƒTheCOM-1portisusedfortheconsoleserialline.-ThePOÜEthernetportcanbeusedasanetwork connectionoritcanLO5be terminated.'Themouseandkeyboardportsarenotused.œ5! rJOƒTheKFE72-DAmustbepluggedintothebottomthreeEISAPOÜslots.(Forthe AlphaServer8200thisrequiresthatyouattachLO5aHosefromyourIO ProcessortoaDWLPBPCIcardcage.QO�TheKFE72-DAmodulesetmustbe installedinslots0,1,andNOæ2ofthecardcage.)TheKFE72'sSIO(a.k.a.(Bridge)modulePO>enablestheEISAslotswhicharepartofthe combinationPCILO—/EISA backplane.'Theothertwomodulesknownasthe"DataQOïPortModule"and "Beeper97"goinslots1and2 respectively.N6 `$+OÐ6.2.2BUsingaTerminalServerMO4YoumaywanttobringyourconsolelinestogetherusingaKOŒterminalserver.)Forexample,usea DECserver200toallowLOå reverse-LATaccesstoeachconsoleoverthenetwork.'WhileNO=thisisnotstrictly required,itgreatly simplifiesOpenVMSIO–Galaxy configuration management.(Refertothe appropriateJOîproduct documentationfordetailsabout configuringaLAT4OGServerorotherterminal concentrator.ª7 ¯€;OÐ6.2.3BRecommendationsfor ConfiguringConsole<( SubsystemsJOŒEach additionalconsolerequiresaseparateKFE72-DAsub-NOåsystem installedinaseparateDWLPBcardcagewithahoseMO= connectingittoaseparateIO ProcessoroftypeKFTIAorLO–KFTHA.IfyouareusingaKFTIA,itmustbeinslot8.ã8ìN¹NOƒ AdditionalKFTIAI/OmodulemustbeinthenextlowerslotNOÜorslots,withKFTHAI/OmoduleinthenextlowerslotorO5slotsafterthat.½9Úõ“HOƒYoucanuseany combinationofthesetwoIO ProcessorKOÜmodulesaslongasyoufollowthisslot assignmentrule.Ì:ÚN¢EOƒThe AlphaServer8200supportsamaximumofthreeIOGOÜ Processors.. Attemptingto configuremorethanthreeisO5 unsupported.•; ÿkLOƒWhen configuringaconsole subsystem,theIOhoseconnect-LOÜingtheIO ProcessorandDWLPBcardcagemustbeplugged@O5intothelowesthoseport.)Notjustthelowest­5 available5hoseXO�port,buttheabsolutefirsthoseport;theoneclosesttothetopOæofthemodule.�<ÚõeIOƒKFE72-DAmodulesmustoccupyslots0,1,and2oftheOÜDWLPBcardcage.= NêLOƒTheconsoleseriallineis connectedwithanH8571-Jcon-ROÜnectoradapterthatplugsintotherighthandseriallineportLO5whenviewedfromtherearofthemachine.&ThisisCOM-1.N>ñV$*OÐ6.2.4B InstallingEISADevicesNO4Plug-inEISAdevicescanonlybe configuredin partition0.OOŒAfter installingEISAdevices,theconsolewillissueames-MOåsage requestingthatyouruntheEISA ConfigurationUtilityO=(ECU).O?Úœ%%OƒRuntheECUasfollows:‚@! YX:`Ð1.:ShutdownallOpenVMSGalaxy instances.S`O2.:Besureyourfloppydiskdriveisproperly connectedtotheHÔ¨primary partitions hardware.( TypicallythedrivecanbeGÔcabledintothe ConnectorModule ("Beeper"partnumber)ÔY 54-25133-01)inPCIslot2.A`Ø3.:Insertthediskette containingtheECUimage.K`W4.:Issuethe followingcommandsfromtheprimaryconsole:%ùÜ P00>>>&SET% ARC_ENABLE&ONù$ P00>>>& INITIALIZEùl P00>>>&RUNECUN`ì5.:Followthe proceduresoutlinedbytheECUandexitwhenÔDdone.`Ã6.:P00>>>boot%`C7.:$@SYS$SYSTEM:SHUTDOWN*`Â8.:P00>>>SET ARC_ENABLEOFF `A9.:P00>>> INITIALIZE`Á10.P00>>>GALAXY+`@11.ReboottheOpenVMSGalaxyÍAÿW£JOƒTherearetwoversionsoftheECU,onethatrunsonaKOÜgraphicsterminalandanotherthatrunson charactercellPO5 terminals.)Bothversionsareonthe diskette,andtheconsoleFO� determineswhichonetorun.+ForOpenVMSGalaxysys-QOætems,theprimaryconsolewillalwaysbeaserialdevicewith'O>a charactercell terminal.B± ÂïMOƒIftheECUisnotrun,OpenVMSwilldisplaythe followingOÜmessage:Fza %SYSTEM-I-NOCONFIGDATA,&IRQ% Configuration&data%for&EISAJ © slot%xxx&was%not%found,&please%run%the&ECU%and%reboot.­C õƒTOƒIfyouignorethismessage,thesystemwillboot,buttheplug-/OÜinEISAdeviceswillbeignored.Dè¦ñIOƒOnceyouhave configuredandsetuptheOpenVMSGalaxyLOÜhardwareas describedinintheprevious sections,performHO5the followingstepstoinstallandbootOpenVMSGalaxyO� instances. é879ÛEþƱ0OÐ6.3BStep3:'CreateASystemDiskBOUDecidewhethertouseasystemdiskperinstance RU or·UtouseaO­clustercommondiskôFÞNÊHOƒAnew SECURITY.EXEisrequiredforallclustermembersIOÜrunningaversionpriortoOpenVMSV7.2thatsharethe9O5sameVMS$OBJECTS.DATwithGalaxy instances. I98:¾GÚД>OÐ6.4BStep4:'InstallOpenVMSAlphaVersion7.2GOUNospecial installation proceduresarerequiredtorunDO­OpenVMSGalaxy software..Galaxy functionalityisin-MOcludedinthebase operatingsystemandcanbeenabledorHO^disabledusingtheconsolecommandandsystem parameter6O·values describedlaterinthischapter.õHÚNËHOƒFormore informationabout installingtheOpenVMSAlpha&OÜ operatingsystem,seethe&øÜ OpenVMSAlphaVersion7.2,O5 Upgradeand InstallationManual "5.|IÚMR8OÐ6.4.1BOpenVMSGalaxy Licensing InformationO4 SeeChapter4. £<‰cÚ‘ _2OãTable6-1:7TableofUsefulIntegers Oþù Oh1 MegabytesKh0x100000Oá2 MegabytesKá0x200000O[4 MegabytesK[0x400000OÕ8 MegabytesKÕ0x800000OO16 MegabytesKO0x1000000OÈ32 MegabytesKÈ0x2000000OB64 MegabytesKB0x4000000O¼128 MegabytesK¼0x8000000O6256 MegabytesK60x10000000O¯448 MegabytesK¯0x1C000000O)512 MegabytesK)0x20000000O£1GigabyteK£0x40000000O2 GigabytesK0x80000000O—4 GigabytesK—0x100000000O8 GigabytesK0x200000000OŠ16 GigabytesKŠ0x400000000O 32 GigabytesK 0x800000000O~ 64 GigabytesK~ 0x1000000000O÷ 128 GigabytesK÷ 0x2000000000Oq 256 GigabytesKq 0x4000000000Oë 512 GigabytesKë 0x8000000000Oe 1TerabyteKe 0x10000000000 O‹ ù  Š :9;ÜJï)²/OÐ6.5BStep5:'UpgradetheFirmwareOƒNotethattheOpenVMSGalaxyfirmware(GALAXY_GOÜ FIRM_072.KIT)islocatedontheAlphaCD2forOpenVMSO5Version7.2.OÚ×(OƒUsethe following commands:4O P00>>>%BOOT%-FLAGS%0,80%cd_device_name OP . O˜ . Oà .9O( Bootfile:%$[GALAXY_FIRM_072.KIT]AS8_G52-101.EXE Op . O¸ . O .xPÿ.NJOƒWhenthefirmwareupdatehas completed,youmustrebuildAOÜtheEEPROMformatoneach even-numbered processorO5moduleasfollows:O¹ P00>>>%SET&CPUJ0O P00>>>%BUILD%-EOk P00>>>%SET&CPUJ2O² P00>>>%BUILD%-E O . Od . O¬ .O P00>>>INITÆQÚõœKOƒNotethataMOPbootableversionofthefirmwareupdate,.OÜ $[GALAXY_FIRM_072.KIT]AS8_G52-101.SYS#�Ü,isalsoontheCD. M;:=nR ”D4OÐ6.6BStep6:'Set Environment VariablesKOUWhenyouhaveupgradedthefirmwareonallofyourpro-IO­cessormodules,youcancreatetheGalaxy-specificenvi-KOronment variablesasshowninthe followingexample.)ThisNO^exampleassumesyouare configuringa2 instance,8CPU,1>>%create&-nv%lp_count j< 2.O„ P00>>>%create&-nv% lp_cpu_mask0»1/OÌ P00>>>%create&-nv% lp_cpu_mask1»fe/O P00>>>%create&-nv% lp_io_mask0à100.O\ P00>>>%create&-nv% lp_io_mask1à805O¤ P00>>>%create&-nv% lp_mem_size0»100000005Oì P00>>>%create&-nv% lp_mem_size1»10000000;O3 P00>>>%create&-nv%lp_shared_mem_sizeK20000000O{ P00>>>%init÷SèNÍNOƒOncethese variableshavebeencreated,youcanuseconsoleFOÜSETcommandsto manipulatethem.*These variablesneed9O5onlybecreatedon processor0asshown.šTÚõpJOƒThe following descriptionsgivedetailed informationabout&OÜeach environment variable.ÈU ¦žOÅLP_COUNTTO4Ifsettozero,thesystemwillboota traditionalSMPconfigu-8O�rationonly.&GalaxyconsolemodeisOFF.yV ¦OROƒIfsettoanon-zerovalue,theGalaxyfeatureswillbeused,POÜandtheGalaxy variableswillbe interpreted.(Theexactvalue O5ofª5 lp_count>*5 representsthenumberofGalaxy partitionstheQO�consoleshouldexpect.' Currently,thisnumbermustbe0or2.¿WûW•MOƒNotethatifyouassign resourcesforthree partitionsandROÜsetthisvariabletotwo,the remaining resourceswillbeleftMO5 unassigned.(Youmayalsocreatethe variablesforthemax-IO�imumnumberof partitionsaheadoftimeandsimplynotOOæassign resourcestothem(setthemtonon-zerovalues)untilO>needed.éXÚ¿(OÅ LP_CPU_MASK partitionnumberIO4Thisbit-mask determineswhichCPUsaretobe initiallyGO�assignedtothe specifiedGalaxy partitionnumber./TheHOå AlphaServer8200consolechoosesthefirst even-numberedGO>CPUasitsprimary..Keepthisinmindwhen assigningMO–the resources(inotherwords,donotassignonlyanodd-+OïnumberedCPUtoa partition).²Y䦈'OÅ LP_IO_MASK partitionnumberNO4These variablesassignIO processorsbyslotnumbertoeachO� instance.ñZÚèÇ `Ð ·8ÔÐ100 representstheI/Omoduleinslot8 `O ·7ÔO80 representstheI/Omoduleinslot7 `Ï ·7ÔÏ40 representstheI/Omoduleinslot6ƒ[ÚõYJOƒThesearetheonlyvalid assignmentsforthe AlphaServerOÜ8200.â\ N¸OOƒYoucanassignmorethanoneI/Omoduletoaninstanceus-NOÜingthesemasks,buteachGalaxyinstancerequiresatleastO5oneI/Omodule.Ù] ¯¯(OÅ LP_MEM_SIZE partitionnumberLO4These variablesallocateaspecificamountofprivatemem-TO�oryforthe specified instance.'Itis imperativethatyoucreateMOåthese variablesusingpropervaluesfortheamountofmem-JO>oryinyoursystemandthedesired assignmentsforeachO– instance.'Refertoä–Table6-1]–forcommonvalues.*]äYa?cw^ÚœMMOƒSeealsothesharedmemoryvariableonthe followingline._Ú§õOÅLP_SHARED_MEM_SIZEJO4Thisvariable allocatesmemoryforuseassharedmemory.O�Refertoˆ�Table6-1�forcommonvalues. Ôg]Tips gBÔ–Sharedmemorymustbeassignedin multiplesof8DÔï megabytesandallvaluesare expressedin hexadeci-ÔGmalbytes.EÔÁYoucandefineonlytheamountofsharedmemorytoCÔuse,andleavetheother lp_mem_size variablesun-FÔrdefined.+Thiswillcausetheconsoletoallocatethe?ÔËsharedmemoryfromthehighaddressspace,andBÔ#splitthe remainingmemoryequallyamongthenum-JÔ|berof partitions specifiedbythelp_count variable.(IfFÔÔyoualso explicitlyassignmemorytoaspecificpar-EÔ-titionusinga lp_mem_size variable,butleaveotherBÔ† partitionmemory assignments undefined,theconsoleBÔÞwillagainassignthememory fragmentsforsharedDÔ7memoryandany partitionswithexplicit assignments,CÔ�thensplitandassignthe remainingmemorytoany>Ôè remaining partitionsnothavingexplicitmemoryÔ@ assignments. Ô‹—*_ˆPa?cŽ`! ¤dOÅ bootdef_devO boot_osflagsRO�Youshouldsetthese variablesoneachofyourGalaxyconsolesKOÚpriortobootingtoensurethatAUTOGENreboots correctlyTO3whenitneedstorebootthesystemafteraninitial installationHO‹andafterasystemcrashoroperator requestedreboot.æaÚ¼8OÐ6.6.1BGalaxy Environment VariablesExampleO# P00>>>%SHOW%GALAXY*OŒ lp_partitions&21OÔ lp_shared_mem_size%20000000p(512&MB)+O lp_mem_size0%10000000%(256%MB)+Od lp_mem_size1%10000000%(256%MB)#O¬ lp_cpu_mask0%1%(CPU&0)'Oô lp_cpu_mask1%fe%(CPUs%1-7)6O< lp_io_mask0%100%(I/O%module%in%slot%8)5O„ lp_io_mask1%80%(I/O&module%in%slot&7)Oí P00>>âbÚ¥¸!OÐ6.6.2BUsefulIntegersO4Table6-19Ï4listscommonvaluesforGalaxy environmentJOŒ variables.'Allvaluesare expressedin hexadecimalbytes.*bO÷e?c Ç=;>÷d (Í@O£6.7BStep7:'Startthe SecondaryConsoleDevicesHO(IftheKFE72-DAwasever configuredfor Windows-NT,itRO€probablyexpectstofindthevideoboardandwillhangifoneMOÙisnotpresent.'Thisisacommon occurrencewhen configur-KO1inganOpenVMSGalaxy.'Aconsolecommandcanbeusedto5OŠsetthemodeof operationasfollows:&O P00>>>%SET&CONSOLE%SERIALþeã‚ÔKO·WhenyouissuethiscommandtotheprimaryconsolepriorMOto initializingthe secondary consoles,thesettingwillbe>>%SHOW%NETWORK)OÔ P00>>>%SET& EWA0_MODE%TWISTEDg ÿUMOƒThefirstcommanddisplaysalistof availablenetworkde-HOÜvices.+Thesecondcommand establishesthedefaultmediaMO5typeforthe specifieddevice(EWA0inthis example).*ThisUO�shouldbedoneforallEthernetdevicespriorto initializingtheOæ secondary consoles.ÓhïW©HOƒOnceyouhavesetyourconsolemodeandnetworkmediaPOÜtypes(ifused)youshould re-initializethesystemtoensurePO5thatthecurrentsettingsaresaved.(Ifyouhavealreadyde-OO�finedyourGalaxy partitions,youcan initializenow.*IfyouKOæhavenotdefinedyourGalaxy partitions,youshoulddefer'O>initializationuntillater.ƒiÚ!YCOƒIfyouarereadyto initializethesystem,enter:O P00>>>%INITyj! ÿOLOƒYoushouldseetheprimaryconsolerespondwithitsusualMOÜpower-up-self-test(POST)report.'ThiscouldtakeuptotwoNO5minutes.)IfyouhaveproperlydefinedtheGalaxy partitions,RO�onlytheI/Odevices associatedwiththeprimary partitionwillOæbevisible.³kÚô‰@OƒToverifythat partitioninghas occurred,enter:O P00>>>%SHOW%DEVICE Oq orOÛ P00>>>%SHOW%NETWORK|lÚ!R:OƒTo initializethe secondaryconsole,enter:O P00>>>%GALAXYÌmÚê¢1OƒTheconsoledisplaysthe following:+O Partition%0:%Primary%CPU%=%0+OP Partition%1:%Primary%CPU%=%2GO˜ Partition%0:%Memory&Base%=% 000000000pSize&=% 010000000GOà Partition%1:%Memory&Base%=% 010000000pSize&=% 010000000@O( Shared%Memory&Base%=% 020000000pSize&=% 0100000000Op Galaxy% Configuration%Tree&=%12c000KO¸ starting%cpu%1%in%Galaxy%instance%1%at%address& 01000c001KO starting%cpu%2%in%Galaxy%instance%1%at%address& 01000c001KOH starting%cpu%3%in%Galaxy%instance%1%at%address& 01000c001KO� starting%cpu%4%in%Galaxy%instance%1%at%address& 01000c001KOØ starting%cpu%5%in%Galaxy%instance%1%at%address& 01000c001KO  starting%cpu%6%in%Galaxy%instance%1%at%address& 01000c001KOh starting%cpu%7%in%Galaxy%instance%1%at%address& 01000c001OÑ P00>>>ðnñWÆ5OƒThiscommandmustbeenteredfromthe<ƒ primaryGalaxyOÜ consoleHDÜ.)IftheGalaxy partitionshavebeenproperlydefined,JO5andhardware resourceshavebeenproperly configured,youNO�shouldseetheprimaryconsolestartthe processorsassignedMOætoeach secondary partition.)Eachofthe secondaryconsoles:O>should initializewithinabouttwominutes.ño! NÇSOƒIfoneormoreconsolesfailsto initialize,youshoulddouble-OOÜcheckyourhardware installation,Galaxy partition definitions,%O5andhardware assignments.%pèþûOÐ6.7.1BConsoleHintsMO4Becausethe AlphaServer8200wasbuiltpriortotheGalaxyEOŒSoftware Architecture,OpenVMSGalaxyconsolefirmwareJOåandsystem operationsmustdealwithafew restrictions.½qúõ“QOƒThe followinglistbriefly describessomethingsyoushouldbeBOÜawareofandsomethingsyoushouldavoiddoing:r #ó `Ð ·ÔÐDonotsettheÝÐ BOOT_RESET#2Ð environmentvariableto ¦Ð 1 ÆÐ.JÔ(Thiscauseseach secondaryconsoletoresetthebusbe-OÔ�forebooting,thus resettingall previouslybooted partitions.AÔÚRememberthatOpenVMSGalaxy partitionssharetheÔ2 hardware. `± ·,Ô±The AlphaServer8200detectsae± Ctrl/Pk±keysequenceon1Ô theprimaryconsoleusing hardware.×s H­)Ôb ThiswillgoawayforSSB:)bIfyouenterCtrl/PontheJÔ»primaryconsole,ALLconsoleswillhalt.*Ifyoudidnot<Ôintendtodothis,youcanusuallyissuea¥ CONTINUEBÔlcommandtogetthe operatingsystemrunningagainCÔÅ(yourchancesof successfully continuingdependsonGÔwhatisrunningonthesystemandhowlongyouhaveLÔvbeenhalted).(Youshouldbeableto independentlyissueaGÔÎ Control-Pkeysequencetoany secondaryinstancewith-FÔ'out impactinganyother instances.( Secondary Control-P>Ôkey sequencesarehandledbyconsole firmware. `ÿ ·JÔÿGivetheprocesstime.)Consoleinitialization,andsystem1ÔW rebootingcantakeseveralminutes. `Ö ·@ÔÖ Donotattempttoabortafirmwareupdatepro-Ô/ cess!ÜtçS²:ÔbThiscanleaveyoursystem seriouslyhung. `â ·4ÔâWhenupdatingconsole firmware,updateÀâ ALLCPUs pâatÔ:thesametime.ëu ]ÁJÔbYoucannotruntwo differenttypesofCPUsortwodif-NÔ»ferentfirmware revisions.'Ifyoufailtoprovide consistentFÔfirmware revisions,thesystemwillhangon power-up. `“ ·Ô“Neverissuethe “ GALAXY%¡“commandfroma secondaryKÔëconsole.*Thiswill re-initializethesystem,andyouwill=ÔDneedtostartoverfromtheprimaryconsole. {>=?vÚë3OÐ6.8BStep8:'BoottheOpenVMSGalaxyFOUWhenyouhave correctly installedtheGalaxyfirmwareOO­and configuredthe consoles,youcanboottheinitialGalaxy#O environmentasfollows:Þw ô´&OƒForeachGalaxy instance:PO P00>>>%B%-FL%0,1&DKA100%//%or%whatever%your&boot%device&is."Oq SYSBOOT>%SET%GALAXY&1OÛ SYSBOOT>%CONTINUEnxÚœDDOƒCongratulations!'YouhavecreatedanOpenVMSGalaxy. H?>@.y Á3O 7.@Creating(an(OpenVMS(Galaxy(on(an#Or AlphaServer!4100!SystemKO÷Thischapter describesthe requirementsand proceduresforGOOcreatinganOpenVMSGalaxy computing environmentonanO¨ AlphaServer4100. Ÿ@?A—zÚnm!OÐ7.1BBeforeYouStartLOUBesuretoreadtheReleaseNoteschapterinthisguide.á{ N·JOƒTocreateanOpenVMSGalaxyonan AlphaServer4100,youLOÜmustalsobefamiliarwiththe following configurationand!O5hardware requirements:±|Ú¦‡OÅ Two-instancemaximumHO4Youcanrunamaximumoftwo instancesofOpenVMSon O�an AlphaServer4100.Ã}覙OÅConsolefirmwareHO4Youmusthave AlphaServer4100consolefirmwareVersion6O� AS4_G52-59 (AvailableontheV7.2kit).Ê~Ú¦ OÅConsolecommands3O4Inadditiontotheconsolehintsin4Chapter5,²4youshouldbe$O�awareofthe following:*~÷nOÁåÁê `Ð ·CÔÐEnterconsolecommandsononeinstanceatatime. `O ·HÔODonotenterconsolecommandsatanotherconsoleuntilIÔ¨thecommandenteredatthefirstconsolehas completed.�€ ¯s"OÅ AlphaServer4100clockCO4An AlphaServer4100hasoneclock./ForanOpenVMSKO�Galaxy,thismeansthatyoucannotrunthetwo instancesHOåat differenttimes.,Also,theSETTIMEcommandaffectsQO>both instances.'Notethatthismaynotbecomeevidentuntila*O–numberofhourshavepassed.Æ�Ú¦œOÅConsoleportsBO4COM1(upper)istheconsoleportforinstance0.BO�COM2(lower)istheconsoleportforinstance1.ñ‚ÚNÇDOƒUnlikecreatinganOpenVMSGalaxyonan AlphaServerKOÜ8400,youdonotneed additionalhardwareforthesecond8O5console.'COM-2isusedforthispurpose.ƒÚWÛOÅCPUs9O4CPU0mustbetheprimaryforinstance0.9O�CPU1mustbetheprimaryforinstance1.HOåCPUs2and3areoptional secondaryCPUsthatcanbeO> migrated.%„ÚWûOÅI/OadaptersNO4ThefourlowerPCIslotsbelongtoIOD0,whichistheI/O$O�adapterforinstance0.NOåThefourupperPCIslotsbelongtoIOD1,whichistheI/O$O>adapterforinstance1.K… W!OÅStorage controllersOO4Youwillneedtwostorage controllers,suchasKZPSAs.'TheseQO�cangotoseparate StorageworksboxesortothesameboxforOOårunningasaSCSIcluster.(One controllereachgoesinIOD0O>andIOD1.ˆ ¦¡OÅNetworkcardsNO4Ifeachinstanceneedsnetworkaccess,anetworkcard(such;O�asaDE500)isrequiredforeach instance._‡Úœ55OƒOnecardeachgoesinIOD0andIOD1.fˆûW<OÅPhysicalmemoryHO4BecauseOpenVMSGalaxyonan AlphaServer4100doesnotEO�supportmemoryholes,physicalmemoryforanOpenVMSKOåGalaxy environmentmustbe contiguous.)ToachievethisonJO>an AlphaServer4100,oneofthe followingmustbetrue:8‰!  `Ð ·IÔÐAllmemorymodulesmustbethesamesize(forexample,Ô(1GB). `¨ ·OÔ¨Iftwosizesarepresent,onlyonemodulecanbeasmallerOÔsize.'Youmustputthelargermodulesintothelowerslots. -A"@B¹ŠÚÆ�OÐ7.2B ProceduresDOUTocreateanOpenVMSGalaxyonan AlphaServer41002O­system,performthe followingsteps:‹Ýóò=`Ð1.:UsetheSHOWCONFIGcommandtomakesureGÔ(thatthe AlphaServer4100youareusingtocreatean@Ô�OpenVMSGalaxy environmentmeetsthe requirementsÔÚ describedin’ÚSection7.1.*‹’�|?zŠŒÚ`DÔbAttheconsoleprompt,enterthe followingcommand:Ôç P00>>>show&config‹�† 3a>ÔbTheconsoledisplaysthe following information:Xùç Console%G52-59KOpenVMS%PALcode% V1.19-16,%Digital%UNIX&PALcode%V1.21-24ùP Module¤P Type»Rev•Nameù˜ System& Motherboard ¤˜ 0ô˜ 0000pmthrbrd0ùà MemoryK512%MB%EDO ¤à 0ôà 0000pmem0ù( MemoryK256%MB%EDO ¤( 0ô( 0000pmem1ùp CPU& (Uncached) ¤p 0ôp 0000pcpu0ù¸ CPU& (Uncached) ¤¸ 0ô¸ 0000pcpu1ù Bridge& (IOD0/IOD1)¤ 600à0021p iod0/iod1ùH PCI& Motherboard ¤H 8ôH 0000psaddle0ù� CPU& (Uncached) ¤� 0ô� 0000pcpu2ùØ CPU& (Uncached) ¤Ø 0ôØ 0001pcpu3ùA Bus&0Kiod0%(PCI0)ù‰ SlotpOption%Name¤‰ Type»Rev•NameùÑ 1àPCEB¤Ñ 4828086K0005ppceb0ù 4àDEC%KZPSA¤ 81011•0000ppks1ùa 5àDECchip%21040-AA¤a 21011•0023ptulip1FùÊ Bus&1Kpceb0&(EISA&Bridge% connected%to%iod0,%slot%1)ù SlotpOption%Name¤ Type»Rev•Nameù{ Bus&0Kiod1%(PCI1)ùà SlotpOption%Name¤Ã Type»Rev•Nameù  1àNCR%53C810¤  11000•0002pncr0ùS 2àDECchip%21040-AA¤S 21011•0024ptulip0ù› 3àDEC%KZPSA¤› 81011•0000ppks04`2.:InstallOpenVMSAlphaVersion7.2.€ŽúÞVGÔbNospecial installation proceduresarerequiredtorun?Ô»OpenVMSGalaxy software..Galaxy functionalityisGÔincludedinthebase operatingsystemandcanbeen-HÔlabledordisabledusingtheconsolecommandandsystemAÔÅ parametervalues describedlaterinthischapter.è�Ú,¾KÔbIfyour AlphaServer4100isnotpartofaSCSIcluster,DÔ»youmustinstallOpenVMSVersion7.2ontwosystem/Ô disks-onediskforeach instance.ß� ,µKÔbIfyour AlphaServer4100ispartofaSCSIclusterwithEÔ»acluster-commonsystemdisk,installOpenVMSVersion%Ô7.2ononesystemdisk.õ‘ÿµËAÔbFormore informationabout installingtheOpenVMS-Ô»Alpha operatingsystem,seethe!X» OpenVMSAlphaVersion0Ô 7.2Upgradeand InstallationGuide Ö.J`“3.:Toupgradethe firmware,copythefirmwarefileAS4_8Ôë G52-59.SYSto MOM$SYSTEMona MOP-enabledJÔDserverthatis accessibletothe AlphaServer4100.)Enter5Ôœthe followingcommandsontheconsole: ’Úß,Ôb NEEDTOADDTHECD PROCEDURE.7Ôç P00>>>%boot%-fl%0,0&ewa0%-fi& as4_g52-59Ô/ UPD>&update%srm*Ôw A`ö4.: Configuretheprimaryconsoleforinstance0.]“Ú{33ÔbCPU0istheprimaryforinstance0.ð”Ú,ÆEÔbCreatetheGalaxy environment variables.)Fordescrip-EÔ»tionsoftheGalaxy environment variablesandcommon'Ôvaluesforthem,refertoUChapter5.*”UÖlOÁ½•! ñ“GÔbThe followingexampleisforan AlphaServer4100withGÔ»threeCPUsand512MBofmemorydividedinto256MB Ô+192MB+64MB.+Ô˜ P00>>>%create&-nv% lp_cpu_mask0 _˜ 1+Ôà P00>>>%create&-nv% lp_cpu_mask1 _à 6*Ô( P00>>>%create&-nv% lp_io_mask0 _( 10*Ôp P00>>>%create&-nv% lp_io_mask1 _p 20+Ô¸ P00>>>%create&-nv% lp_mem_size0_¸ 10000000+Ô P00>>>%create&-nv% lp_mem_size1_ c000000'ÔH P00>>>%create&-nv%lp_count _H 2:Ô� P00>>>%create&-nv%lp_shared_mem_sizeK4000000(ÔØ P00>>>%set& auto_action&halt—–ÚÞmJÔbIfyouhavefourCPUsandyouwanttoassignallsec-EÔ»ondaryCPUstoinstance1,the lp_cpu_mask1variableÔwillbe Õ EA .IfyousplittheCPUsbetweenboth instances,HÔlCPU0mustbetheprimaryforinstance0,andCPU18ÔÅmustbetheprimaryCPUforinstance1.®—ÚÔ„ ÔbThezb mem_size4*b variablesdependonyour configuration1Ô»andhowyouwanttosplititup.Š˜ÚA`0YÐgalaxy_io_mask0mustbesetto100Y(galaxy_io_mask1mustbesetto20Ê™ * =ÔbYoumustsettheconsole environmentvariable�b AUTO_Ô» ACTION@C»toHALT.ThiswillensurethatthesystemdoesKÔnotbootandthatyouwillbeabletoentertheGalaxyÔlcommand.L`ë5.: InitializethesystemandstarttheGalaxyfirmwareby-ÔDenteringthe following commands:ÔÉ P00>>>%initÔ P00>>>%galaxy šÚÔvGÔbAfterthe self-test completes,theGalaxycommandwill/Ô»starttheconsoleoninstance1. ›ÚÞßJÔbThefirsttimethattheGalaxystarts,itmightdisplay2Ô»severalmessageslikethe following: Ô@ CPU0&would&not%joinCÔÅ IOD0&and%IOD1&did%not%pass%the%power-up% self-testîœõ,ÄEÔbThishappensbecausetherearetwosetsofenviron-$Ô»ment variables,andthe9» galaxy&N» variablesarenotpresent%Ô initiallyoninstance1.¨�ð6~IÔbNotethatwhentheI/ObusisdividedbetweenthetwoFÔ»Galaxy partitions,theportletterofadevicemightAÔchange.-Forexample,adisk designatedasDKC300IÔlwhenthe AlphaServer4100isasinglesystemcouldbe-KÔÅcomeDKA300whenitis configuredas partition0oftheÔOpenVMSGalaxy.÷ž! SÍNÔbItisbesttowaitfortheP01>>>promptonthe secondaryGÔ»consolebefore attemptingtoboottheprimaryconsole.8`:6.: Configuretheconsoleforinstance1.5Ÿúõ HÔbUsethesamecommandsfromstep2tocreatethesame)Ô»Galaxy environment variables./Ô@ P01>>>%create&-nv%galaxy_cpu_mask0 ô@ 1/Ôˆ P01>>>%create&-nv%galaxy_cpu_mask1 ôˆ 6.ÔÐ P01>>>%create&-nv%galaxy_io_mask0 ôÐ 10.Ô P01>>>%create&-nv%galaxy_io_mask1 ô 20/Ô_ P01>>>%create&-nv%galaxy_mem_size0ô_ 10000000/Ô§ P01>>>%create&-nv%galaxy_mem_size1ô§ c0000000Ôï P01>>>%create&-nv%galaxy_partitions ôï 2>Ô7 P01>>>%create&-nv%galaxy_shared_mem_sizeK4000000(Ô P01>>>%set& auto_action&haltN`ÿ7.: InitializethesystemandrestarttheGalaxyfirmwareby,ÔWenteringthe followingcommand:ÔÜ P00>>>%init* ì1DÔbWhentheconsoledisplaysthe following confirmationÔ»prompt,typeY:>Ô@ Do%you%REALLY&want%to%reset%the&Galaxy%(Y/N)O`¿8.: Configurethesystemroot,bootdevice,andotherrelatedÔ variables.d¡V Ê:CÔbThe followingexamplesettingsarefromanOpenVMSGÔ» Engineeringsystem.)Changethese variablestomeetthe,Ôneedsofyourown environment.)Ô˜ P00>>>%set& boot_osflags%12,0(Ôà P00>>>%set& bootdef_dev&dka0&Ô( P00>>>%set& boot_reset%off!_( !!!%must&be&OFF%!!!)Ôp P00>>>%set& ewa0_mode%twisted)ÔÙ P01>>>%set& boot_osflags%11,0*Ô! P01>>>%set& bootdef_dev&dkb200&Ôi P01>>>%set& boot_reset%off!_i !!!%must&be&OFF%!!!)Ô± P01>>>%set& ewa0_mode%twisted´¢! žŠPÔbIfyoubuildaSCSIcluster,makesuretosetupyourSCSI7Ô»adapterhostIDs correctly.&Forexample:&Ô@ P00>>>%set& pka0_host_idJ6&Ôˆ P00>>>%set& pkb0_host_idJ6'ÔÐ P00>>>%set& kzpsa_host_id%6&Ô9 P01>>>%set& pka0_host_idJ7'Ô� P01>>>%set& kzpsa_host_id%7-`9.:Bootinstance1asfollows:Ô… P01>>>%bootð£Ú±ÆKÔbOnceinstance1isbooted,logintothesystemaccount<Ô»andedittheSYS$SYSTEM:MODPARAMS.DATfileto-Ôincludethethe followingline:Ô˜ GALAXY=1�¤õfJÔbConfirmthatthelinesfortheSCSnodeandSCSsystemEÔ»IDarecorrect.*RunAUTOGENasfollowsto configureFÔinstance1asaGalaxymember,andleavethesystemÔlhalted:<Ôñ $&@SYS$UPDATE:AUTOGEN%GETDATA%SHUTDOWN%INITIAL.`p10.Bootinstance0asfollows:Ôõ P00>>>%bootû¥Ú±ÑKÔbOnceinstance0isbooted,logintothesystemaccount<Ô»andedittheSYS$SYSTEM:MODPARAMS.DATfileto(Ôincludethe followingline:"Ô˜ Add%the&line%GALAXY=1¦õÝïJÔbConfirmthatthelinesfortheSCSnodeandSCSsystemEÔ»IDarecorrect.*RunAUTOGENasfollowsto configureFÔinstance0asaGalaxymember,andleavethesystemÔlhalted:<Ôñ $&@SYS$UPDATE:AUTOGEN%GETDATA%SHUTDOWN%INITIALL`p11.PreparetheGalaxytocomeup automaticallyuponini-JÔÉ tializationorpowercycleofthesystem.)SettheAUTO_@Ô!ACTION environmentvariableonboth instancestoÔzRESTART.+Ôÿ P00>>>%set& auto_action&restart+Ôh P01>>>%set& auto_action&restartK`ç12. InitializetheGalaxyagainbyenteringthe following.Ô@commandsattheprimaryconsole:ÔÄ P00>>>%initǧÚY�DÔbWhentheconsoledisplaysthe following confirmationÔ»prompt,typeY:>Ô@ Do%you%REALLY&want%to%reset%the&Galaxy%(Y/N)ɨ ,ŸEÔbAlternatively,youcould power-cycleyoursystem,andIÔ»theGalaxywithboth instancesshould bootstrapautomat-Ôically.n©ÚœDDOƒCongratulations!'YouhavecreatedanOpenVMSGalaxy. úB AC�ª {s8O 8.:Using&a&Single-Instance&Galaxy%on&AnyOrAlpha!SystemHO÷WithOpenVMSAlphaVersion7.2,youcanrunasingle-GOOinstanceGalaxyonanyAlpha platform.-This capabilityKO¨allowsearlyadopterstoevaluateOpenVMSGalaxy features,GOandmost importantly,todevelopandtest Galaxy-awareLOY applicationswithout incurringtheexpenseofsettingupaJO± full-scaleGalaxy computing environmentonasystemcapa-LO bleofrunningmultiple instancesofOpenVMS(forexample,!Oban AlphaServer8400). «! °áNOƒAsingle-instanceGalaxyrunningonanyAlphasystemisnotLOÜan emulator.'ItisOpenVMSGalaxycodewithGalaxyinter-LO5facesand underlying operatingsystem functions.(AllGalaxyLO�APIsarepresentinasingle-instanceGalaxy(forexample,HOæresource management,sharedmemoryaccess,eventnotifi-KO>cation,lockingforsynchronization,andsharedmemoryforO—global sections).˜¬ anOOƒAny applicationrunonasingle-instanceGalaxywillexerciseNOÜtheexactsame operatingsystemcodeonamultipleinstanceMO5Galaxysystem.(Thisis accomplishedbycreatingtheconfig-@O�urationfileSYS$SYSTEM:GLX$GCT.BIN,whichOpenVMSGOæreadsintomemory.,OnaGalaxyplatform(forexample,LO> AlphaServer8400),theconsoleplaces configurationdatainHO—memoryforOpenVMStouse.)Oncethe configurationdataNOïisinmemory, regardlessofitsorigin,OpenVMSbootsasaOHGalaxy instance.«­Úõ�NOƒTousetheGalaxy ConfigurationUtilitytocreateasingle-3OÜinstanceGalaxyonanyAlphaSystem:¨®úõ~HOƒRuntheGCUontheOpenVMSAlphasystemonwhichyou6OÜwanttousethesingle-instanceGalaxy.ä¯ÚNºMOƒIftheGCUisrunona non-Galaxysystem,itwillpromptMOÜastowhetheryouwanttocreateasingle-instanceGalaxy.O5Clickon “5 OK.Á°! W—KOƒTheGCUnextpromptsfortheamountofmemorytodesig-QOÜnateassharedmemory.'EnteranyvaluethatisamultipleofPO58 megabytes.'Notethatyoumustspecifyatleast8 megabytesOO�ofsharedmemoryifyouwanttobootasaGalaxy instance.HOæThismeanstheminimumGalaxymemory requirementis72O> megabytes.•±úÿkMOƒWhentheGCUhas displayedtheconfiguration,itwillhaveIOÜalreadywrittenthefile GLX$GCT.BINtothecurrentdi-PO5rectory.(YoumayexittheGCUatthispoint.(IfyoumadeaQO�mistakeorwanttoaltertheconfiguration,youcanclosethe4Oæcurrentmodelandrepeattheprocess.e²Úœ;;OƒTorebootthesystemasaGalaxy instance:K³Q D!O`Õ1.:Copythe GLX$GCT.BINfiletoSYS$SYSROOT:[SYSEXE]GLX$GCT.BIN$`U2.:Shutdownthesystem.N`Ô3.:Rebootwithaconversationalbootcommand(i.e.'>>>B-Ô,FL0,1device)&`¬4.:SYSBOOT>SETGALAXY1 `+5.:SYSBOOT>CONTINUEc´Úœ99Oƒ Consoleoutputmessageistobe supplied. vCBD\µÚ22OüPartIII7ManagingAnOpenVMSGalaxy °D CEM¶ÿ´#5O 9.2OpenVMS!Galaxy! Configuration"UtilityGO‘TheGalaxy ConfigurationUtility(GCU)isa DECwindowsKOêMotif applicationthatallowssystemmanagersto configureKOBandmanagetheirGalaxysystemsfromasingle workstationO›window.\·Úœ22OƒUsingtheGCU,systemmanagerscan:T¸ l* `Ð ·6ÔÐDisplaytheactiveGalaxyconfiguration. `O ·8ÔOReassign resourcesamongGalaxy instances. `Ï ·3ÔÏViewresource-specificcharacteristics. `N ·CÔNShutdownorrebootoneormoreGalaxy instances. `Í ·0ÔÍInvoke additional managementtools. `L ·@ÔLEvaluaterun-time performanceandresourceusage. `Ì ·=ÔÌCreateandengageGalaxy configurationmodels. `K ·DÔKCreateasingle-instanceGalaxyonanyAlphasystem?Ô¤(forsoftware developmenton non-GalaxyhardwareÔü platforms). `{ ·3Ô{ViewtheonlineGalaxydocumentation. `û ·GÔû Determinehot-swapcharacteristicsofthecurrenthard-ÔSware platform.ιÚN¤COƒTheGCUresidesintheSYS$SYSTEM[SYSMGR] directoryMOÜalongwithasmallnumberoffiles containing configurationO5 knowledge.bºÚœ88OƒTheGCUconsistsofthe followingfiles:»ýàêOãSYS$SYSTEM:GCU.EXE ãGCU executableimageO]SYS$MANAGER:GCU.DAT]Optional DECwindowsªresourcefile O$SYS$MANAGER:GALAXY.GCR$Galaxy ConfigurationqRuleset9OëSYS$MANAGER:GCU$ACTIONS.COMåSystem management8 proceduresO² SYS$MANAGER: t² xxxÔ².GCM ² User-definedconfigu-rationmodels;OzSYS$HELP:GALAXY_GUIDE.DECW$BOOKPOnlinehelpinÇ Bookreaderformž¼! ÿtMOƒTheGCUis typicallyrunfromtheprimaryGalaxy instance.POÜIfthesystemdoesnotdirectlysupportgraphicsoutput,thenLO5the DECwindowsdisplaycanbesettoanexternalworksta-NO�tionorsuitably configuredPC.However,theGCU application=OæitselfmustalwaysrunontheGalaxysystem.W½! ˆ-MOƒWhentheGCUisstarted,itloadsanycustomizationsfoundKOÜinitsresourcefile (GCU.DAT);thenitloadstheGalaxyIO5 ConfigurationRuleset (GALAXY.GCR).Therulesetfilecon-JO�tains statementsthat determinethewaytheGCUdisplaysGOæthevarioussystem components,andincludesrulesthatMO>governthewaysinwhichuserscaninteractwiththecon-NO— figurationdisplay.+Usersdonot typicallyaltertherulesetQOïfileunlesstheyarewellversedinits structureoraredi-LOHrectedtodosobyaCompaqServices Engineer.+AftertheHO GCUdisplaybecomesvisible,theGCU determineswhetherIOùthesystemis currently configuredasanOpenVMSGalaxyNORorasasingle-instanceGalaxyonanyAlphasystem.)IftheQOªsystemis configuredasaGalaxy,theGCUdisplaystheactiveGOGalaxy configurationmodel.)Themain observationwindowLO[displaysa hierarchicalviewoftheGalaxy.,IfthesystemLO´hasnotyetbeen configuredasaGalaxy,theGCUpromptsPO youastowhetherornottocreateasingle-instanceGalaxy.KOeNotethattheGCUcancreateasingle-instanceGalaxyonFO¾anyAlphasystem,butmultiple-instanceOpenVMSGalaxyGO environmentsarecreatedbyusingconsolecommandsandLOofirmware functionsas described elsewhereinthis document.`¾ì¦6MOƒOncetheGalaxy configurationmodelis displayed,userscanOOÜeitherinteractwiththeactivemodelortakethemodeloffLO5lineanddefinespecificconfigurationsforlateruse.-TheNO� followingsectionsdiscussthese functionsingreaterdetail. dFEG<ÝÚ processor.)TheGCUisawareofthis requirement,andwillJO—attempttouseoneormorecommunicationspathstosendMOïthe reassignmentrequesttotheowner instance.)DCLisnotMOH inherentlyawareofthis requirement; therefore,ifyouuseMO DCLtoreassign resources,youwillneedtouseSYSMANorJOùa separately logged-interminaltoissuethecommandsonORtheowner instance.Õß W«FOƒTheGCUfavorsusingSYSMAN,andits underlyingSMI_MOÜServer processestoprovidecommandpathstotheotherin-HO5stancesintheGalaxy.+However,the SMI_ServerrequiresQO�thatthe instancesbeinaclustersothatthecommandenvi-HOæronmentfallswithinacommonsecuritydomain.)However,7O>Galaxy instancesmightnotbe clustered.³à W‰FOƒIfthesystemcannotprovideasuitablecommandpathJOÜforthe SMI_Servertouse,theGCUwillattempttouseEO5DECnet task-to-taskcommunications.+ThisrequiresthatNO�the participating instancesberunningDECnet,andthateachLOæ participatingGalaxyinstancehaveaproxysetupfortheO>SYSTEMaccount.ûáÚWÑPOƒItispossibleforaninstancetonotbe clustered,havenoKOÜproxyaccount established,andnothaveDECnet capability.IO5Theseare consideredisolatedinstancefroma managementIO� perspective.,Theonlywaytoreassign resourcesfromanSOæisolatedinstanceistobeloggedintoitsconsole.*(Formore7O> informationaboutisolated instances,seeû>Section9.2.1.)*áû¶?ââÚÙ'OÐ9.2.1B Independent InstancesIO4Youcan partitionaGalaxysystemsothatoneormoreFOŒ partitionsarebootedwithoutbecomingmembersoftheFOåGalaxysharing community.)Theseareknownasindepen-JO=dent instances.+Because independent instancesresideinaMO–Galaxy partition,theirpresenceis reflectedintheGalaxyFOî ConfigurationFile,andtheyarevisibletotheGCU.ÏãÚN¥KOƒThese independenttheycanstill participateinCPUreas-GOÜ signment.+TheycannotutilizesharedmemoryorrelatedO5 services.7ä! ° NOƒYoucancreatea partitionthathasnoEthernetdeviceandPOÜisnotamemberofaclusteroroftheGalaxysharingcom-(O5munity.)Theseareknownas~5 isolated instancesT5.)BecauseUO�theyresideinaGalaxy partition,theyarestillvisibletotheKOæGCUandyoucanreassignCPUstothem.'ToreassignCPUsPO>awayfromisolated instances,youmustlogintotheconsole&O—oftheisolated instance.kå `A(OÐ9.2.2BRequiredPROXYAccessHO4WhentheGCUneedstoexecutea managementaction,itIOŒalwaysattemptstousetheSYSMANutilityfirst.)SYSMANSOårequiresthattheinvolved instancesbeinthesamecluster.'IfSO=thisisnotthecase,theGCUwillnextattempttouseDECnetGO– task-to-taskcommunications.-Forthistowork,thein-LOîvolved instancesmusteachhaveanEthernetdevice,DECnetOOG capability,andsuitableproxyaccessonthetarget instance.Ìæ âKOƒForexample,considera two-instance configurationthatisMOÜnot clustered.)Ifinstance0wererunningtheGCUandtheOO5userattemptstoreassignaCPUfrominstance1toinstanceHO�0,theactual reassignmentcommandmustbeexecutedonTOæinstance1.'Todothis,theGCU'saction proceduresinthefile=O>SYS$MANAGER:GCU$ACTIONS.COMwillattempttoes-GO—tablishaDECnet task-to-task connectiontotheSYSTEMKOïaccountoninstance1.,Thisrequiresthatinstance1hasHOHgrantedproxyaccesstotheSYSTEMaccountofinstanceNO 0.(Usingthe established connection,theaction procedureonOOùinstance0willpassits parameterstothe equivalentactionPOR procedureoninstance1,whichnowtreatsthe operationasaOªlocal operation.ŽçÚÿdJOƒTheGCUaction proceduresassumethattheywillbeusedLOÜbythesystemmanager.*Thus,intheaction procedurefile8O5SYS$MANAGER:GCU$ACTIONS.COM,theSYSTEMac-KO�countisused..Tograntaccesstotheopposite instancesKOæSYSTEMaccount,theproxymustbesetuponinstance1.QèÚœ''OƒTo establishproxyaccess:Šé! ¢`D`Ð1.:Enterthe followingcommandsattheDCLprompt:%ÔU $&SET%DEFAULT& SYS$SYSTEMÔ� $&RUN% AUTHORIZEU`2.:Ifproxy processingisnotyetenabled,enableitbyentering#Ôuthe following commands:Ôù UAF>& CREATE/PROXY4ÔA UAF>&ADD%PROXY%instance::SYSTEM&SYSTEMÔ‰ UAF>&EXIT²ê! kˆOƒReplaceƒ instance<¾ƒwiththenameoftheinstancetowhichyouPOÜaregrantingaccess.(Performthesestepsforeachofthein-MO5stancesyouwanttomanagefromtheinstanceonwhichyouNO�runtheGCU.Forexample,inatypical two-instanceGalaxy,ROæifyouruntheGCUonlyoninstance0,thenyouneedtoaddOO>proxyaccessonlyoninstance1forinstance0.+Ifyouin-SO—tendtoruntheGCUoninstance1also,thenyouneedtoaddOOïproxyaccessoninstance0forinstance1.(Inthree-instanceMOHGalaxysystems,youmayneedtoaddproxyaccessforeachQO  combinationof instancesyouwanttocontrol.'Forthisreason,QOùagoodruleofthumbistoalwaysruntheGCUfrominstance OR0.‡ë/ ÿ]MOƒYouarenotrequiredtousetheSYSTEMaccount.'TochangeIOÜtheaccount,youneedtoeditSYS$MANAGER:GCU$ACTIONS.COMRO5oneachinvolved instance.'Locatethelinethat establishestheGO� task-to-task connection,andreplacetheSYSTEMaccount.Oænamewithoneofyour choosing.ÿì NÕHOƒNotethattheselectedaccountmusthaveOPER,SYSPRV,LOÜandCMKRNL privileges.'Youalsoneedtoaddthe necessaryAO5proxyaccesstoyour instancesforthisaccount. G FH¨íñ<~,OÐ9.3BGalaxy ConfigurationModelsJOUTheGCUisafully programmabledisplayengine.+ItusesOO­asetofrulestolearnthedesiredcharacteristicsandin-IO teractive behaviorsofthesystem components.+UsingthisEO^ specialized configuration knowledge,theGCU assemblesJO·modelsthat representthe relationshipsamongsystemcom-GOponents.,TheGCUobtains informationaboutthecurrentLOhsystem structurebyparsinga configuration structurebuiltLOÁbytheconsole firmware.*This structure,calledtheGalaxyHO ConfigurationFile,isstoredinmemoryandisupdatedEOrasneededbyfirmwareandbyOpenVMS executiverou-QOÊtinestoensurethatit accuratelyreflectsthecurrentsystem$O# configurationandstate.dî :GOƒTheGCUconvertsandextendsthebinaryrepresentationOOÜofthe configurationfileintoasimpleASCIIrepresentation,OO5whichitcanstoreinafileasanofflinemodel.+TheGCUOO�canlaterreloadanofflinemodelandalterthesystemcon-MOæ figurationtomatchthemodel.(WhetheryouareviewingtheRO>activemodeloranofflinemodel,youarealwaysfreetosaveMO—thecurrent configurationasanofflineGalaxy ConfigurationOïModel(.GCM)file.ÉïûaŸLOƒTomakeanofflinemodeldrivethecurrentsystemconfig-KOÜuration,themodelmustbeloadedandengaged.*ToengageKO5amodel,clicktheEngagebutton.+TheGCUwillscantheOO�current configurationfile,compareitagainstthemodel,andPOæcreatealistofany managementactionsthatarerequiredtoPO>engagethemodel.)TheGCUpresentsthislisttoyouforfi-MO—nal confirmation.)Ifyouapprove,theGCUwillexecutetheLOïactions,andthemodelwillbecomeengagedtoreflectthe5OHcurrentsystem configurationandstate.xð NGOƒWhenyou disengageamodel,theGCU immediatelymarksNOÜtheCPUsand instancesasoffline.)Youcanthenfreelyar-PO5rangethemodelhoweveryoulike,andeithersavethemodel,QO�orreengagethemodel.)Intypical practice,youarelikelytoOOæhaveasmallnumberofmodels,thathaveprovedtobeuse-LO>fulforyourbusiness operations.+ThesecanbeengagedbyMO—asystemmanagerorasuitably privilegeduser,orthrough0Oï automated proceduresorbatchjob.}ñ ÌSOÐ9.3.1BActiveModelNO4TheGCU maintainsasingleactivemodel.'Thismodelisal-HOŒwaysderivedfromthe in-memory configurationfile.*TheMOå configurationfilecanbefromaGalaxyconsoleorfromaGO= file-based,single-instanceGalaxyonanyAlphasystem.NO– Regardlessofitssource,console callbacksmaintainthein-ROîtegrityofthefile.(TheGCUutilizesGalaxyeventservicestoIOG determinewhena configurationchangehas occurred.'WhenMOŸachangeoccurs,theGCUparsesthe configurationfileandNOøupdatesitsactivemodeltoreflectthecurrentsystem.*TheWOQactivemodelisnotsavedtoafileunlessyouchoosetosaveitOO©asanofflinemodel.) Typically,theactivemodelbecomestheLObasisforcreating additionalmodels.)Whencreatingmodels,UOZitis generallybesttodosoonlinesothatyouaresureyour@O³offlinemodelscanengagewhentheyareneeded.qòÿVG OÐ9.3.2BOfflineModelsKO4TheGCUcanloadanynumberofofflineGalaxy configura-IOŒtionmodelsandfreelyswitchamongthem,assumingtheyJOåwerecreatedforthespecificsystem hardware.*ThemodelIO=representationisasimpleASCIIdata definitionformat.ÈóúažSOƒYoushouldneverneedtoeditamodelfileinitsASCIIform.LOÜTheGCUmodelsandrulesetadheretoasimple proprietaryCO5languageknownastheGalaxy ConfigurationLanguageMO�(GCL).Thislanguage continuestoevolveasneededtorep-LOæresentnewGalaxy innovations.+BewareofthisfactifyouRO>decidetoexplorethemodelandrulesetfiles directly.)IfyouKO— accidentallycorruptamodel,youcanalwaysgeneratean-OOïother.(Ifyoucorrupttheruleset,youmayneedtodownload7OHanotherfromtheOpenVMSGalaxywebsite.£ôÚBy9OÅ9.3.2.1CExample:!CreatinganOfflineModel@O)TocreateanofflineGalaxy configurationmodel:(õ! \þM`Ð1.:BootyourGalaxysystem,logintothesystemaccount,Ô(andruntheGCU.C`¨2.:Bydefault,theGCUdisplaystheactivemodel.N`'3.: DisengagetheactivemodelbyclickingtheEngagebuttonÔ€(it toggles).I`ÿ4.:Assumingyoursystemhasafew secondaryCPUs,dragMÔWanddropsomeoftheCPUstoa differentGalaxy instance.L`×5.:Savethemodelby selectingSaveModelfromtheModelHÔ/menu.(Givethemodelasuitablenamewitha.GCMex-PÔˆtension.&ItisusefultogivethemodelanamethatdenotesCÔàtheCPU assignments;forexample,suchasG1x7.GCMLÔ9forasysteminwhichinstance0has1CPUandinstanceJÔ’1has7CPUs,orG4x4.GCMforasystemwith4CPUonMÔêeachofitstwo instances.'Thisnamingschemeis optional,KÔCbutbesuretogivethefiletheproper.GCM extension.�ö ÔcKÔbYoucancreateandsaveasmany variationsofthemodelÔ»asyoulike.S÷Úœ))OƒToengageanofflinemodel:Rø *(`Ð1.:RuntheGCU.M`O2.:Bydefault,theGCUdisplaystheactivemodel.)Youcan9Ô¨closetheactivemodelorjustleaveit.N`'3.:Loadthedesiredmodelby selectingOpenModelfromtheÔ€Modelmenu.L`ÿ4.:LocateandselectthedesiredmodelandclickOK.TheKÔWmodelwillbeloadedand displayedinanoffline,disen-Ô°gagedstate.C`/5.:ClicktheEngagebuttontoreengagethemodel.G`¯6.:TheGCUwilldisplayany management operationsre-IÔquiredtoengagethemodel.,Ifyouapproveoftheac-FÔ`tions,clickOK.TheGCUwillperformthe managementIÔ¸actions,andthemodelwillbe displayedasactiveandÔengaged. ySH/GImùôãC&OÐ9.4BUsingtheGCUChartsEOUTheGalaxy ConfigurationFilecontainsa considerableGO­amountof configurationdataandcangrowquitelargeMOforcomplexGalaxyconfigurations.(IftheGCU displayedallMO^the informationithasaboutthesystem,thedisplaywouldHO·become unreasonablycomplex.,Toavoidthisproblem,theIOGCUprovidesGalaxycharts.-ChartsaresimplyasetofNOhmasksthatcontrolthe visibilityofthevarious components,IOÁdevices,andinterconnections.*Theentire componenthier-MOarchyispresent,butonlythe components specifiedbythePOrselectedchartarevisible.* Selectinga differentchartalters2OÊthe visibilityof componentsubsets.[ú! 1NOƒBydefault,theGCUprovidesfive preconfiguredcharts.'EachMOÜisdesignedtoshowaspecific component relationship.)SomeDO5GCUcommand operationscanbe performedonlywithinGO�specificcharts.-Forexample,youcannotreassignCPUsGOæfromwithinthePhysical Structurechart.-ThePhysicalJO> StructurechartdoesnotshowtheGalaxyinstancecompo-QO—nents,thusyouwouldhavenotargettodraganddropaCPUOOïon.'BecauseyoucanmodifythechartstheGCUdoesnotre-KOHstrictitsmenusandcommand operationstospecificchartNO  selections.'Insomecases,theGCUdisplaysan informationalAOùmessagetohelpyouselectan appropriatechart.rûÚœHHOƒFormore informationabout modifyingcharts,see?????.�ü ¸cDOÐ9.4.1B ComponentIdentificationandDisplay PropertiesOO4Each componenthasaunique identifier.)This identifierbeaKOŒsimple sequentialnumber,suchaswithCPUIDs,aphysi-ROåcal backplaneslotnumber,aswithI/O adapters,oraphysicalIO=address,aswithmemorydevices.+Each componenttypeisLO–alsoassignedashapeandcolorbytheGCU.Wherepossi-HOîble,theGCUfurther distinguisheseach componentusingEOG supplementary informationitgathersfromtherunningOŸsystem._ý ¦5NOƒThedisplay propertiesofeach componentareassignedwithinHOÜtheGalaxy ConfigurationRuleset(SYS$MANAGER:GALAXY.GCR).MO5Youshouldnoteditthisfile,exceptto customizecertainRO�display properties,suchaswindowcolorordisplaytextstyle.)þ! ¦ÿLOƒThetextthatgets displayedabouteach componentisalsoOOÜ customizable.'Each componenttypehasasetof statementsinNO5therulesetthat determineits appearance,datacontent,andO� interaction.ƒÿÚYSOƒOneusefulfeatureistheabilitytoselectwhichtextisdis-JOÜplayedineach componenttypeonthescreen.,ThedevicePO5 declarationintherulesetallowyoutospecifythetextandIO� parameters,whichmakeupthedisplaytext statement.*AMOæsubsetofthisdisplaytextis displayedwheneverthezoomTO>scalefactordoesnotallowthefulltexttobe displayed.)ThisGO—subsetisknownasthe mnemonic.+Themnemoniccanbe;Oïalteredtoincludeanytextand parameters.! }ð+OÐ9.4.2BPhysical StructureChartMO4ThePhysical Structurechart describesthephysicalhardwareMOŒinthesystem.)Thelarge rectangular componentatthetop,OOåorroot,ofthechart representsthephysicalsystemcabinetSO=itself.( Typically,belowtheroot,youwillfindphysicalcompo-RO–nentssuchasmodules,slots,arrays, adapters,andsoon.'TheKOîtypeof components presentedandthedepthofthecompo-OOGnent hierarchyisdirectly dependentonthelevelofsupportJOŸprovidedbytheconsolefirmwareforeachhardwareplat-KOøform.+Ifyouareviewingasingle-instanceGalaxyonanyOOQAlphasystem,thenonlyasmallsubsetof componentsmaybeMO© displayed.*Asageneralrule,theconsolefirmwarepresentsLO componentsonlydowntothelevelof configurabledevices,ROZ typicallytothe first-levelI/Oadapterorslightlybeyond.*ItPO³isnotagoaloftheGCUoroftheGalaxyconsolefirmwareRO tomapeverydevice,butratherthosethatareofinterestto,OdGalaxy configuration management. ÿNâPOƒThePhysical StructurechartisusefulforviewingtheentireOOÜ collectionof componentsinthesystem.)However,itdoesnotCO5displayanylogical partitioningofthe components.bÚœ88OƒInthePhysical Structurechartyoucan:Ã! Ó™ `Ð ·?ÔÐExaminethe parametersofanysystem component. `O ·KÔOPerformahot-swapinquiryto determinehowtoisolatea"Ô¨ componentforrepairs. `' ·GÔ'Applyan OptimizationOverlayto determinewhethertheFÔ€hardwareplatformhasspecific optimizationsthatwillCÔØensurethebest performance.+Forexample, multiple-CÔ1CPUmodulesmayrunbestifallCPUsresidingonAÔ‰acommonmoduleareassignedtothesameGalaxyÔâ instance. `a ·HÔaShutdownorreboottheGalaxyorspecificGalaxyin-Ôºstances.q! ]G!OÅ9.4.2.1CHardwareRootJO)Thetopmost componentinthePhysical StructurechartisIO�knownasthehardwareroot (HW_Root).'EveryGalaxysys-SOÚtemhasasinglehardwareroot.*ItisusefultothinkofthisRO3asthephysical floorplanofthemachine.(IfaphysicaldeviceSO‹hasnospecificlowerplaceinthe component hierarchy,itwillSOäappearasachildofthehardwareroot.&A componentthatisaPO<childcanbeassignedtootherdevicesinthe hierarchywhen@O•themachineis partitionedor logicallydefined. Ôz oTip ñzFÔžClickingtherootnodeofanychartwillperformanGÔ÷ auto-layout operationiftheAutoLayoutmodeisset. ÔA—G U%OÅ9.4.2.2C OwnershipOverlayBO)Choose OwnershipOverlayfromtheWindowsmenutoNO�displaytheinitialowner relationshipsforthevariouscom-MOÚponents.+These relationshipsindicatetheinstancethatwillLO3ownthe componentafterapowercycle.)OnceasystemhasIO‹beenbooted, migratable componentsmaychangeownersdy-ROä namically.(Inordertoaltertheinitial ownership,theconsole4O< environment variablesmustbechanged.¬Úõ‚EOƒThe ownership overlay has no effectonthe Physical=OÜ StructurechartortheFailoverTargetchart.vö¸L*OÐ9.4.3BLogical StructureChartGO4TheLogical StructurechartdisplaysGalaxy communitiesROŒand instancesandisthebest illustrationofthe relationshipsGOåwhichformtheGalaxy.,Belowthese componentsaretheIO=variousdevicesthey currentlyown.+ Ownershipisanim-LO–portant distinctionbetweentheLogical StructurechartandKOîPhysical Structurechart.+InaGalaxy, resourcesthatcanMOGbe partitionedor dynamically reconfiguredhavetwodistinctOŸ ``owners''.Ø W®MOƒTheowner describeswherethedevicewillturnupafteraLOÜsystemcoldboot.,Thisvalueis determinedbytheconsoleIO5firmwareduring bus-probing proceduresandthroughinter-IO� pretationoftheGalaxy environment variables.*TheownerOOævaluesarestoredinconsole nonvolatilememorysothatthey4O>canberestoredafterapowercycle.š ! ÿpIOƒThe current_owner describestheownerofadeviceataLOÜ particularmomentintime.*Forexample,aCPUisfreetoOO5reassignamong instances.'Asitdoes,its current_ownervaluePO�is modified,butitsownervalueremainswhateveritwassetO5select OwnershipOverlayfromtheWindowmenu.Õ ! ¬«!OÅ9.4.3.1CSoftwareRootIO)Thetopmost componentintheLogical StructurechartisKO�knownasthesoftwareroot (SW_Root).'EveryGalaxysystemUOÚhasasinglesoftwareroot.'IfaphysicaldevicehasnospecificSO3owner,itwillappearasachildofthesoftwareroot.)Acom-UO‹ponentthathasachildcanbeassignedtootherdevicesinthe@Oä hierarchywhenthemachineis logicallydefined. Ôez ohTip ñezFÔíClickingtherootnodeofanychartwillperformanHÔFautolayout operationiftheAutoLayoutmodeisset. Ô�—n ! LD(OÅ9.4.3.2C Unassigned ResourcesOO)Youcan configureGalaxy partitionswithout assigningallde-SO�vicestoa partition,oryoucandefinebutnot initializeoneKOÚormore partitions.+Ineithercase,somehardwaremaybe/O3 unassignedwhenthesystemboots.� ÚõeIOƒTheconsolefirmwarehandles unassigned resourcesintheOÜ followingmanner:±Úh‡ `Ð ·AÔÐ UnassignedCPUswillbeassignedto partition0. `O ·0ÔO Unassignedmemorywillbeignored.Ü N²LOƒDevicesthatremain unassignedafterthesystembootswillMOÜappearassignedtothesoftwareroot componentandmaynotO5be accessible./ ó'OÅ9.4.3.3C Community ResourcesNO) Resourcessuchassharedmemorycanbeaccessedbyallin-JO�stanceswithinasharing community.* Therefore,forsharedFOÚmemory,the communityitselfis consideredtheowner.ùÚóÏ&OÅ9.4.3.4CInstance ResourcesHO) Resourcesthatare currentlyor permanentlyownedbyaMO�specificinstanceare displayedaschildrenoftheinstanceOÚ component.ŽÚ¯d*OÐ9.4.4BMemory AssignmentChartHO4TheMemory Assignmentchart illustratesthe partitioningDOŒand assignmentofmemory fragmentsamongtheGalaxyGOå instances.,Thischartdisplaysbothhardware componentsIO=(arrays, controllers,andsoon)andsoftware componentsO–(memory fragments).ÿ°ÚEOƒCurrentGalaxyfirmwareand operatingsystemsoftwareHOÜdoesnotyetsupportdynamicreconfigurationofmemory.HO5Thus,theMemory AssignmentchartreflectsthewaytheJO�memoryaddressspacehasbeen partitionedbytheconsoleJOæamongtheGalaxy instances.*This informationcanbeuse-PO>fulfor debuggingsystem applicationsorforstudyingpossible!O— configurationchanges.� ®c%OÅ9.4.4.1CConsole FragmentsKO)Theconsolerequiresoneormoresmall fragmentsofmem-GO�ory.0 Typically,aconsole allocates approximately2MBHOÚofmemoryinthelowaddressrangeofeach partition.HO3Thisvariesbyhardwareplatformandfirmware revision.OO‹ Additionally,someconsolesallocateasmallfragmentinhighKOäaddressspaceforeach partitiontostorememorybitmaps.JO<Theconsolefirmwaremayneedtocreate additionalfrag-8O•mentstoenforcepropermemory alignment.º ¤�%OÅ9.4.4.2CPrivate FragmentsKO)EachGalaxyinstanceisrequiredtohaveatleast64MBLO�ofprivatememory (includestheconsole fragments)tobootLOÚOpenVMS.Thismemorymayconsistofasingle fragment,orLO3theconsolefirmwaremayneedtocreate additionalprivatereassigntheCPUbacktothecurrentowner..TheGCU9O— communicatesonlywiththeGalaxymembers.Jî¦ JOƒ RegardlessofwhetheraninstanceispartoftheGalaxyQOÜsharing communityorisan independentnode,itwillstillbeOO5presentintheGalaxy configurationfile; therefore,thusthe6O�GCUwillstillbeabletodisplayit.© ¯'OÐ9.4.6BIOP AssignmentChartKO4TheIOP Assignmentchartdisplaysthecurrent relationshipMOŒbetweenI/O processorsandtheGalaxy instances.)Notethat,MOå dependingonwhattypeofhardwareplatformisbeingused,LO=asingle-instanceGalaxyonanyAlphasystemmaynotshow'O–anyIOPsinthisdisplay.°  ÿ†POƒThe OwnershipOverlaycanbeshowninthischarttoseetheOOÜ nonvolatileowner(whichinstancethedevicewillbeassignedRO5toafterapowercycle),butuntilIOPreconfigurationissup-GO�portedbytheOpenVMSGalaxyimplementation,theownerNOæwillalwaysbethesameasthedefaultdisplay illustrates.h!ÚV>(OÐ9.4.7BFailoverTargetChartIO4TheFailoverTargetchartshowshoweach processorwillNOŒ automaticallyfailovertoother instancesintheeventofaNOåshutdownorfailure.+ Additionally,thischart illustratesthe1O=stateofeachCPUs autostartflag."úNõROƒForeach instance,asetoffailoverobjectsareshown,repre-SOÜsentingthefullsetof potentialCPUs.(Bydefault,nofailoverPO5 relationshipsare establishedandall autostartflagsareset.°#ãÿ†LOƒTo establish automaticfailoverofspecificCPUs,dragandQOÜdropthedesiredfailoverobjecttotheinstanceyouwanttheMO5 associatedCPUtotarget.,Tosetfailover relationshipsforMO�allCPUsownedbyan instance,draganddroptheinstanceOOæobjectontopoftheinstanceyouwanttheCPUstotarget.Í$! W£QOƒToclear individualfailovertargets,draganddropafailoverPOÜobjectbacktoitsowner instance.+Toclearallfailoverre-PO5 lationships, right-clickontheinstanceobjecttodisplaytheIO� Parameters&Commandsdialogbox,clickontheCommandsOOæbutton,clickthe``ClearALLfailover targets?'',buttonandO>thenclickOK.|% RLOƒBydefault,wheneverafailover operationoccurs,theCPUsNOÜwill automaticallystartoncetheyarriveinthetargetin-KO5stance.,Youcancontrolthis autostartfunctionusingtheFO� autostartcommandsfoundinthe Parameters&CommandsPOædialogboxforeachfailoverobject,oreachinstanceobject.PO>TheFailoverTargetchartdisplaysthestateofthe autostartTO—flagby displayingtheFailoverobjectsingreenif autostartis3Oïset,andredif autostartisclear.¶&ÚõŒNOƒPleasenotethe following restrictionsinthecurrentimple->OÜ mentationoffailoverand autostart management.5'   `Ð ·FÔÐThefailoverand autostartsettingsarenot preservedNÔ(acrosssystemboots.'Thus,youwillneedto reestablishtheJÔ�modelwheneverthesystemreboots.)Todothis,invokeaEÔÚ previouslysaved configurationmodel,eitherbymanu-IÔ2ally restoringthedesiredmodelorbyusingacommand-Ô‹ procedureduringsystemstartup. `  ·JÔ TheGCU currentlyisnotcapableof determiningtheau-KÔctostartandfailover relationshipsof instancesotherthanKÔ»theonetheGCUisrunningon,unlessthe instancesareÔ clustered. `“ ·BÔ“TheGCU currentlydoesnotrespondtochangesinHÔìfailoveror autostartstatethataremadefromanotherEÔD executingcopyoftheGCUorfromDCL commands.*IfPÔ�thisstateisaltered,theGCU refreshesitsdisplayonlyif>Ôõtheactivemodelisclosedandthen reopened. ’IHJ7(ô� -OÐ9.5BViewing Component ParametersKOUEach componenthasasetof parametersthatcanbedis-OO­playedand,insomecases,altered.)Todisplaya component'sJO parameters,positionthecursoronthedesired component,IO^clicktherightmousebutton,andselectthe ParametersKO·itemfromthepopupmenuentry.) Alternately,youcanse-MOlecta component,thenselectthe ParametersitemfromtheOh Componentsmenu.A)! °HOƒWhere parametersaresubjecttounit conversion,chang-ROÜingthedisplayunitwillupdatethedisplayandany currentlyJO5visible parameterdialogboxes.)Other parameters representIO�asnapshotofthesystem componentandarenotdynami-KOæcallyupdated.*Ifthese parameterschange,youmustclosePO>andthenreopenthe ParametersdialogboxtoseetheupdatedOO—values.'(This limitationwillbefixedinafuture version.) $JIK *! 2à-OÐ9.6B Executing ComponentCommandsHOUA component's ParametersdialogboxmayalsocontainaFO­commandpage.-Ifso,youcanaccessthecommandsbyROclickingontheCommandsbuttonatthetopofthedialogbox.OO^Mostofthecommandsareexecutedbyclickingontheirtog-PO·glebuttonsandthenclickingtheOKorApplybuttons.'OtherLOcommandsmayrequirethatyouenter information,orselectUOhvaluesfromalistoroptionmenu.'Notethatifyouselectsev-LOÁeral commands,theywillbeexecutedinatop-downorder.GOBesuretochoosecommand sequencesthatarelogical. ƒ LKMð<! <Æ=OÐ9.8B MonitoringanOpenVMSGalaxywithDECamdsDOUTheDECamds availabilitymanagersoftwareprovidesaKO­valuable real-timeviewoftheGalaxysystem.'DECamdscanKOmonitorallGalaxy instancesfromasingle workstationorIO^PCanywhereonthelocalareanetwork.)DECamdsutilizesDO·acustomOpenVMSdriver (RMDRIVER)that periodicallyPOgathers availabilitydatafromthesystem.'This informationisNOhreturnedtotheDECamdsclient applicationusinga low-levelKOÁEthernet protocol.(Theclient applicationprovidesnumerousOOviewsandgraphsofthesystem's availabilitycharacteristics.IOr Additionally,whenDECamdsdetectsoneofnumerousknownROÊ conditions,itnotifiestheuserandoffersasetof solutionsOO#(calledfixes)thatcanbeappliedtoresolvethe condition.Ø= Ü®AOƒEveryOpenVMSsystemcomeswiththeDECamdsDataHOÜ Collector (RMDRIVER) installed.,Toenablethe collector,IO5youmustexecuteitsstartup procedureinside SYSTARTUP_FO�VMS.COMormanuallyoneachGalaxyinstanceyouwantKOætomonitor.+Usethe followingcommandstostartthedataO> collector:7Oà $&@SYS$STARTUP:AMDS$STARTUP%STARTKor&STOP»> W‘IOƒPriorto startingthe collector,!youneedtospecify aIOÜgroupnameforyourGalaxy./Dosobyeditingthefile3O5#SYS$COMMON:[AMDS]AMDS$LOGICALS.COM.ThisOO�fileincludesa statementfor declaringagroupname.'ChooseHOæanyuniquename,makingsurethisfileoneachGalaxy5O>instancecontainsthesamegroupname.æ?! W¼HOƒWhenusingDECamds,OpenVMS EngineeringfindsitusefulIOÜtodisplaytheSystemOverviewwindow,theEventWindowDO5andaCPUSummarywindowforeachGalaxy instance.IO�Thereareanumberof additionalviewsyoucanmonitorKOæ dependingonyourspecific interests.*Formore information)O>aboutDECamds,refertothek> DECamdsUsersGuide ©>. õMLNÛ@ )±%OÐ9.9BCreatinganInstanceAOUThecurrentimplementationoftheGalaxySoftwareIO­ ArchitectureforOpenVMSrequiresthatyou predefinetheQOGalaxy instancesyouintendtouse.(YoucandothisbyusingMO^console environment variables.(Refertothe appropriatesec-PO·tionsofthisguideformoredetailsaboutGalaxy environmentO variables. NMOeAÚw;(OÐ9.10C DissolvinganInstancePOUTheonlywayto effectivelydissolveaGalaxyinstanceistoMO­shutitdown,reassignits resourcesusingconsoleenviron-NOment variables,and,if necessary,rebootany instancesthat(O^willacquirenew resources. ÆONP¬BøÐ‚-OÐ9.11CShutdownandRebootCyclesEOU ResourcessuchasCPUscanbe dynamically reassignedPO­oncetheinvolved instancesarebooted.(Toreassign staticallyKOassigned resources,suchasI/O processors,youmustshutLO^downandreboottheinvolved instancesafter executingthe)O· appropriateconsole commands.  POQßC! 2µ/OÐ9.12COnlineversusOfflineModelsKOUTheGCUallowsyoutodisplayandinteractwiththeac-QO­tive(online)orinactive (offline)Galaxy configurationmodels.JOWhenthe configurationdisplay representsamodeloftheMO^activesystem,theGCUdisplaysthestateoftheCPUsandNO· instancesusingcolorandtext.'Whenthe configurationmodelOOisengagedinthismanner,youcaninteractwiththeactiveEOhsystemusing drag-and-drop procedures.+Theformalde-OOÁ scriptionforthismodeof operationis interactingwiththe"Oengaged,onlinemodel.vD LHOƒGCUuserscanalsointeractwithanynumberofdisen-POÜgaged,oroffline,models.*OfflinemodelscanbesavedtoorPO5loadedfromfiles.(AnofflinemodelcanalsobederivedfromOO�theactiveonlinemodelbyclickingtheEngagebuttontobeOOæ disengagedwhentheactiveonlinemodelis displayed.'Inad-RO>ditiontothevisualstateoftheEngagebutton,theGCUalsoPO— indicatestheonlineversusofflinecharacteristicoftheCPUsJOïand instancesbyusingcolorandtext.*Any drag-and-dropQOHactionsdirectedatanofflinemodelare interpretedassimpleNO editing functions.)Theychangetheinternal structureofthe;Oùmodelbutdonotaffecttheactivesystem.¬E k‚IOƒWhenanofflinemodelisengaged,theGCUcomparestheSOÜ structureofthemodelwiththatoftheactivesystem.(IftheyTO5agree,theofflinemodelisengagedanditsnewonlinestateisQO� indicatedwithcolorandtext.)Iftheydonotagree,theGCUHOæ determineswhat managementactionswouldberequiredtoOO>altertheactivesystemtomatchtheproposedmodel.)AlistOO—ofthe resulting managementactionsis presentedtotheuserQOïandtheuserisaskedwhethertheywouldliketoexecutetheROHactionlist.(Iftheuser disapproves,themodelremainsofflineMO and disengaged.)Iftheuser approves,theGCUexecutestheLOù managementactionsandthe resultingmodelis displayedasORonlineandengaged. …QPR¥FÚn{4OÐ9.13CWhat'sNewForTheGCUinEFT3GOUThisinfoneedstobemovedtothecorrect location:nGÚMD$OÐ9.13.1CNewDCLcommands O4 SETCPU n/FAILOVER=y¨HÚõ~LOƒ Establishesinstance-specificfailover relationshipsforeach2OÜCPUinthe instances potentialset.àIøN¶GOƒWherenistheCPUnumber,acomma-separatedlistofGOÜCPUs,or/ALLandyistheinstancenumberorname. !Ü SETO5 CPU n/NOFAILOVER³JÚõ‰KOƒRemovesanyinstance-specificfailover relationshipfortheOÜ specifiedCPU/s.#µÜ SETCPUn/[NO]AUTOSTART’KÚõhMOƒSetsorclearstheinstance-specific autostartflagfortheOÜ specifiedCPU/s.‹LÚõaGOƒWherenistheCPUnumber,acomma-separatedlistofOÜCPUs,or/ALL. B4RQS(4M– RDþ3%OÐ9.14CGCUSystemMessages ÔR5*UMargie: 6R5GÔÚThesemessagesneedtobein alphabeticalorderbased4Ô2onthemessagenamegcu-x-MESSAGENAME. Ô}—AO< %GCU-E-SUBPROCHALT,& Subprocess%halted;%See%GCU.LOG.Vš¥ The%GCU%has&launched&a% user-defined& subprocess%which%has& terminatedPší with%error%status.JDetails%may%be%found%in%the&file%GCU.LOG.5OV %GCU-S-SUBPROCTERM,& Subprocess% terminatedWš¿ The%GCU%has&launched&a% user-defined& subprocess%which%has& terminated.3O( %GCU-I-SYNCMODE,& XSynchronize% activatedTš’ The%GCU%has&been%invoked%with& X-windows% synchronous%mode&enabled.JšÚ This%is%a% development%mode&which&is&not% generally%used.0OC %GCU-W-NOCPU,&Unable%to%locate%CPUXš¬ A% migration&action%was% initiated&which&involved&an&unknown%CPU.JThis[šô can%result%from%engaging%a&model&which&contains&invalid%CPU& identifiers$š< for%the%current%system.1O¥ %GCU-E-NORULESET,%Ruleset&not%found:Tš The%GCU%was&unable%to%locate%the&Galaxy% Configuration&Ruleset%inUšV SYS$MANAGER:GALAXY.GCR.KNew%versions%of%this%file&can%be% downloaded0šž from%the&OpenVMS%Galaxy&web%page.DO %GCU-E-NOMODEL,%Galaxy& configuration%model%not&found:Ušp The% specified%Galaxy& Configuration%Model%was&not%found.KCheck&your4š¸ command%line%model%file&specification./O! %GCU-W-XTOOLKIT,& X-Toolkit%Warning:Yš‹ The%GCU%has& intercepted&an& X-Toolkit%warning.JYou&may%or%may%not&beEšÓ able%to% continue,& depending%on%the%type%of%warning.EO< %GCU-S-ENGAGED,%New&Galaxy% configuration&model&engagedUš¥ The%GCU%has& successfully%engaged&a%new&Galaxy% Configuration&Model.NO %GCU-E-DISENGAGED,%Unable&to&engage%Galaxy% configuration%modelXšw The%GCU%has&failed%to%engage%a%new%Galaxy& Configuration%Model.KThis]š¿ can%happen%when%a& specified%model%is%invalid&for%the%current%system,&orZš when%other%system& activities%prevent%the% requested&resource& assignments.9Op %GCU-E-NODECW,% DECwindows&is&not% installed.TšÙ The%current&system%does&not%have&the%required% DECwindows&support.3OC %GCU-E-HELPERROR&Help% subsystem&error.Nš¬ The% DECwindows&Help%system& (Bookreader)% encountered%an%error.5O %GCU-E-TOPICERROR%Help&topic&not%found.Sš~ The% DECwindows&Help%system&could&not%locate%the& specified%topic.5Oç %GCU-E-INDEXERROR%Help&index&not%found.SšP The% DECwindows&Help%system&could&not%locate%the& specified%index.+Oº %GCU-E-UNKNOWN_COMPONENT:&{name}Uš# The%current&model&contains& reference%to%an%unknown& component.KThisUšk can%result%from%model%or%ruleset& corruption.KSearch%for&the%namedWš³ component%in%the%ruleset%SYS$MANAGER:GALAXY.GCR.JIf%it%is%not&found,Yšû download&a%new&one%from&the%OpenVMS&Galaxy%web%site.KIf&the%problemBšC persists,%delete%and&recreate&the% offending%model.@O¬ %GCU-I-UNASSIGNED_HW:%Found% unassigned% {component}"Tš The%GCU%has&detected&a%hardware% component&which&is&not% currentlyVš] assigned&to&any%Galaxy% instance.KThis&may%result%from% intentionallyPš¥ leaving% unassigned% resources.KNote&the%message&and%continue%orTší assign%the%hardware% component&from%the&primary%Galaxy&console%andš5 reboot.)Ož %GCU-E-UNKNOWN_KEYWORD:%{word}[š The%GCU%has&parsed%an%unknown&keyword%in%the&current%model%file.KThisPšO can%only&result%from&model&file%format& corruption.KDelete%and*š— recreate&the% offending%model.8O %GCU-E-NOPARAM:%Display%field%{field%name}Wši The%GCU%has&parsed%an% incomplete& component% statement%in%the&currentQš± model.JThis%can%only%result%from%model%file&format% corruption.7šù Delete%and%recreate%the& offending%model.@Ob %GCU-E-NOEDITFIELD:&No&editable&field&in&display.\šË The%GCU%has& attempted%to%edit&a% component& parameter%which%is% undefined.Vš This%can&only%result&from%model%file%format% corruption.KDelete%and*š[ recreate&the% offending%model.FOÄ %GCU-E-UNDEFTYPE,% Undefined% Parameter&Data%Type:%{type}]š. The%GCU%has&parsed%an%unknown&data%type%in%a&model& component% parameter.Tšv This%can&result%from&model&file%format& corruption%or% incompatibleZš¾ ruleset%for&the%current&model.JSearch&the%ruleset&SYS$MANAGER:GALAXY.GCRTš for%the% offending& datatype.JIf%not&found,%download%a&more%recentRšM ruleset%from%the%OpenVMS%Galaxy%web&site.KIf%found,%delete&and*š• recreate&the% offending%model.MOÿ %GCU-E-INVALIDMODEL,%Invalid&model& structure%in:%{model&file}Yšh The%GCU% attempted&to&load%an%invalid%model%file.JDelete&and%recreate š° the% offending%model.4O %GCU-F-TERMINATE& Unexpected% termination.=š‚ The%GCU% encountered%a%fatal% DECwindows&event.- %GCU-E-INTERNAL%Slot%{slot%detail}[š§- The%GCU%has& encountered&an&invalid%datatype%from%a& component% parameter.Yšï- This%can&result%from&ruleset%or%model% corruption.KDownload&a%new&oneZš7. from%the&OpenVMS%Galaxy&web%page.JIf%the&problem% persists,&delete%and*š. recreate&the% offending%model.#Oè. %GCU-F-PARSERR,%{detail}YšQ/ The%GCU% encountered%a%fatal%error%while%parsing&the%ruleset.JDownload=š™/ a%new&one%from&the%OpenVMS&Galaxy%web%page.=O0 %GCU-W-NOLOADFONT:%Unable&to&load%font:%{font}Wšl0 The%GCU%could%not&locate%the% specified&font%on%the&current%system.4š´0 A%default%font&will%be%used%instead.:O1 %GCU-W-NOCOLORCELL:&Unable%to%allocate%colorXš†1 The%GCU%is%unable&to&access%a&colormap&entry.JThis%can%result&from[šÎ1 a%system&with%limited%color%support&or&from%having&an& excessive%numberAš2 of& graphical% applications%open%at%the%same%time.Lt2 GCU-E-NOGALAXY,&This%system&is&not% configured&as&a%Galaxy.šè2 Description:O Q3 The%user&has%issued%the& CONFIGURE% GALAXY/ENGAGE&command%on%aE ™3 system%which%is%not% configured%for%Galaxy& operation.š4 User%Action:Q k4 Configure%your&system%for%Galaxy& operation%using%the% proceduresV ³4 described%in%the%OpenVMS%Galaxy%Guide.KIf%you%only%want&to&run%aJ û4 single-instance%Galaxy,&enter& CONFIGURE%GALAXY%without%theO C5 /ENGAGE% qualifier&and%follow%the& instructions%provided%by%the) ‹5 Galaxy% Configuration&Utility.FOô5 %GCU-E-ACTIONNOTALPHA%GCU&actions%require%OpenVMS&AlphaWš^6 A%GCU&user%has& attempted%to%invoke%a%Galaxy% configuration% operation'š¦6 on&an&OpenVMS%VAX&system.AO7 %GCU-I-ACTIONBEGIN%at%{time},%on% {instance}&{mode}Sšx7 This% informational%message& indicates%the%start%of%a% configurationRšÀ7 action%on%the% specified&Galaxy% instance.KNote%that%many&actionsSš8 require% collaboration%between&command% environments&on&two%separateXšP8 Galaxy% instances,&thus,&you%may% encounter&two%of%these% messages,%oneVš˜8 per%instance%involved%in%the% operation.JThe&mode%argument% indicates5šà8 which&instance&is&local&versus%remote.7OI9 %GCU-S-ACTIONENDKat%{time},&on& {nodename}Vš²9 This%is%the&normal% successful& completion%message% following%a%GalaxySšú9 configuration%action.JNote%that&many%actions%require& collaboration[šB: between%command% environments%on%two&separate&Galaxy% instances,&thus,&youZšŠ: may% encounter%two&of&these& messages,%one%per&instance&involved&in&thešÒ: operation.9O;; %GCU-S-ACTIONEND,%Exiting& GCU$ACTIONS&on&^YTš¤; Indicates%that&the%user&has%aborted&a%Galaxy& configuration%actionšì; using& Control-Y.GOU< %GCU-S-ACTIONEND,%Exiting& GCU$ACTIONS&on&error& {message}Tš¾< Indicates%that&a%Galaxy& configuration%action& terminated%with%error<š= status%as% indicated%by%the&message% argument.5Oo= %GCU-E-ACTIONUNKNOWN%no%action% specifiedTšÙ= Indicates%that&the%GCU$ACTIONS.COM% procedure&was%called% improperly.Wš!> It&is&possible&that%the&command% procedure&has%been& corrupted%or%is7ši> out%of%revision%for%the&current%system.COÒ> %GCU-E-ACTIONNOSIN%no%source&instance&name% specifiedTš;? Indicates%that&the%GCU$ACTIONS.COM% procedure&was%called% improperly.Wšƒ? It&is&possible&that%the&command% procedure&has%been& corrupted%or%is7šË? out%of%revision%for%the&current%system.FO4@ %GCU-E-ACTIONBAD&failed%to%execute&the%specfied%actionQš�@ Indicates%that&a%Galaxy& configuration%action&aborted%due&to&anRšå@ indeterminate%error% condition.JReview&related%screen&messages&andQš-A verify%that&the% necessary%proxy%accounts%have%been& established.PO–A %GCU-E-INSFPRIVS,% Insufficient% privileges%for% attempted& operationZšÿA An&underprivileged%user&has% attempted%to%perform%a&Galaxy% configurationXšGB action.K Typically,%these%actions%are% performed&from%within&the%systemKš�B managers&account.KOPER&and%SYSPRV% privileges%are% required.>OøB %GCU-E-NCF&network%connect%to% {instance}&failedYšbC An&error&has%occurred%trying%to%open%a&DECnet% task-to-task% connectionTšªC between%the&current%and& specified% instances.KReview%related%screenRšñC messages&and%verify%that%the% necessary&proxy&accounts&have%beenš9D established. SRT§NÞ}O 10.2DCL!CommandsGO‘The followingDCLCommandsareusefulformanaginganOêOpenVMSGalaxy:O ?è `Ð ·ÔÐSHOWMEMORY `O ·ÔOSTOP/CPU/MIGRATE `Ï ·ÔÏSHOWCPU `N ·CÔN CONFIGUREGalaxy(CheckedintoonlineDCLHelpforÔ¦EFT3) `& ·Ô&Lexical functionsÁPÚN—AOƒSeveralDCLcommandshavebeenenhancedwithnewEOÜ qualifiersforusewithsharedmemoryinanOpenVMSO5Galaxy:�QÚhW `Ð ·ÔÐDUMP `O ·3ÔOANALYZE(not supportedfor V7.2-EFT3) 2T SU‹RÚnaOÐ10.1CCPUCommandsDOUCPUsare assignable resourcesinanOpenVMSGalaxy.žSÚ¥t"OÐ10.1.1CSTOP/CPU/MIGRATE>O4 Addmore description..NeedtotalkmoreaboutOŒ migration.×T N­=OƒTheSTOP/CPU/MIGRATEcommandstopsandremovesQOÜthe specified secondary processor(s)fromtheactivesetinanO5OpenVMSSMPsystem.AUÚœOƒForexample:sVÚ!I OƒWhenauserenters:)O GLX1$%stop/cpu/migrate=GLX0K4ÖW– !¬LOƒThe followingmessageis displayedattheuser's terminal:`O %SYSTEM-I-CPUSTOPPING,&trying%to%stop&CPU%4&after&it&reaches% quiescent&state‹XÚ!a)OƒThesourceconsole displays:8O %SMP-I-STOPPED,%CPU&#04%has%been%stopped.eYÚ!;.OƒThe destinationconsole displays: O TBSêZÚþÀOÐ10.1.2CSHOWCPU?O4TheSHOWCPUcommanddisplays informationaboutOOŒthestatus,characteristics,and capabilitiesofthe specifiedOå processor(s).´[l ŠOƒForexample:O GLX0$%show&cpu0Oq GLX0,J AlphaServer%8400%Model%5/440TOÛ Multiprocessing%ENABLED.%Full%checking%synchronization%image%loaded.@OD Minimum&multiprocessing%revision%levels:&CPU%=&1O­ PRIMARY&CPU%=K00O Active%CPUs:à00%01#O Configured&CPUs:K00%016Oè Potential%CPUs:p00%01%03%04%05%06%07 ÆUTV¨\ Æ~OÐ10.2CSHOWMEMORYCOUTheSHOWMEMORYcommanddisplaystheusesofmem-O­orybythesystem.]á ÙÚOƒForexample:O CLSSIC$&SHOW%MEMORY@Zq System%Memory% Resources&on& 5-OCT-1999% 20:50:19.032OÛ Physical%Memory%Usage%(pages):»Total!OÛ FreeàIn%Use–Modified#¿# Main&Memory% (2048.00Mb)D# 262144O# 228183•31494à2467O­ GALAXY$&show%memory@Z System%Memory% Resources&on& 5-OCT-1999% 07:55:14.682O Physical%Memory%Usage%(pages):»Total!O FreeàIn%Use–Modified%¿Ç Private&Memory% (512.00Mb)jÇ 65536OÇ 56146à8875 Ï Ç 515%¿ Shared%Memory& (1024.00Mb)j 131072O 130344à728dOx Of%the%physical%pages%in%use,%6421&pages&are% permanently% allocated%to%OpenVMS. OÀ $ 7VUWT^Úé**OÐ10.3CLexicalFunctionExamplev_Ö |L8OÅLexicalFunctionExampleCommand Procedure"O# $&write& sys$output%""COk $&write& sys$output% "Instance&=%",f$getsyi("scsnode")KO³ $&write& sys$output% "Platform&=%",f$getsyi("galaxy_platform")POû $&write& sys$output%"Sharing%Member&=%",f$getsyi("galaxy_member")GOC $&write& sys$output%"Galaxy%ID%=&",f$getsyi("galaxy_id")MO‹ $&write& sys$output% "Community%ID%=&",f$getsyi("community_id")MOÓ $&write& sys$output% "Partition%ID%=&",f$getsyi("partition_id")"O $&write& sys$output%""Oc $&exitS`Úv)7OÅLexicalFunctionCommand ProcedureOutputO# COBRA2$&@shoglxO� Instance%=&COBRA2OÔ Platform%=&1O Sharing&Member%=&19Od Galaxy%ID%=% 376172626F6320202020202020202020O¬ Community%ID%=%0Oô Partition%ID%=%0O] COBRA2$ ¦W VXgaÚn=OÐ10.4CDUMP)OU New Qualifier:'/SHARED_MEMORYb! ¹ØPOƒIntheeventofsystemcrashes,itmaybe necessarytosavePOÜthecontentsofsomeorallofsharedmemoryinadditiontoRO5thememorythatislocaltothesystemthathascrashed.'ThisNO�willbedoneeitherbywritingsharedmemorytothesystemOOædumpfileusingenhancedsystemdumpcode,orasaseparate>O>stepusingtheDUMP/SHARED_MEMORYcommand.(ThisRO—canbedoneeitherafterthefailedsystemreboots,oratanyIOïtimefromanotherinstanceofOpenVMSinthesamecom->OHmunity.*DUMP/SHARED_MEMORYwritestoaseparate2O file,nottothesystemdumpfile.kc ÿAGOƒSharedmemoryincludedinasystemdumpfilewillbeAOÜanalyzedwiththeexistingANALYZE/CRASH_DUMPcom-GO5mand.)Sharedmemorydumped separatelywillbeanalyzed9O�usingthenewcommandANALYZE/SHARED_MEMORY9Oæ(whichisthetopicofaseparatenote).HdÚœOƒSyntax Description:…e õ[=OƒTheformatis:(DUMP/SHARED_MEMORY [region_name_OÜlist] [other_quals]Of °%JOƒwhere"region_name_list"isacomma-separatedlistoftheNOÜregionsofsharedmemorytobedumped,alogicalnamethat/O5 translatestosuchalist,or" 8@*0]5", indicatingthatallregionsinJO�sharedmemoryaretobedumped.+IfnoregionnamelistGOæisgiven,thedefaultisGLX$DUMP_RANGE,whichisex-VO>pectedtobealogicalnamethat translatestoalistofregionsinSDA,suchnumberscanincludeaperiodtoseparatethe6O—upper32bitsfromthelower32bits.&iŒ Ýü/Oƒ other_qualsincludethe following:Mt /ALL_MEMORY%All&shared%memory%is%to%be%dumped&as&a%single=¿P unit,% regardless&of&whether%it%is%part%of%a>¿˜ named%region.&If& /ALL_MEMORY&is& specified,%the3¿à region%name%list&must%not&be&given.HtI /COMPRESSED%The&dump%is%to%be%written%in%a& compressed@¿‘ format%(same% algorithm&as&used%in%system&dumps)Otú /OUTPUT="file"%The&dump%is%to%be%written%to%the%named%file,/¿B instead&of&the%default,%which%is:¿Š GLX$SHARED_MEMORY.DMP%in%the&current%default¿Ò directory.Pt; /SIZE="blocks"%The&size%of%dump%file&to&be&created% initially.A¿ƒ If%not%given,&a%size%is% calculated.%Either%way,?¿Ë the%file%is% truncated%to%the&number%of%blocks=¿ written&when%the&dump%is% complete.&/SIZE&can@¿[ only&be& specified%if%/OUTPUT&is&also% specified.1tÄ /PHYSICAL& Placeholder&at&this%time.KjÚœ!!Oƒ Qualifier description:ýk ¦ÓO>separatestepusingtheDUMP/SHARED_MEMORYcom-NO—mand(whichisthetopicofaseparatenote).+ThiscanbeOOïdoneeitherafterthefailedsystemreboots,oratanytimeIOHfromanotherinstanceofOpenVMSinthesame community.EO DUMP/SHARED_MEMORYwritestoaseparatefile,notto"Oùthesystemdumpfile.3o ¦ GOƒSharedmemoryincludedinasystemdumpfilewillbeAOÜanalyzedwiththeexistingANALYZE/CRASH_DUMPcom-GO5mand.)Sharedmemorydumped separatelywillbeanalyzed:O�usingthenewcommandANALYZE/SHARED_MEMORY.HpÚœOƒSyntax Description:hqðœ>>OƒTheformatis:'ANALYZE/SHARED_MEMORY "file_name"œrÚõrLOƒwhere "file_name"isthenameofthefilecreatedbythe&OÜDUMP/SHARED_MEMORYcommand.�s WsAOƒTheonlyexistingANALYZE qualifier(fromANALYZE:OÜ /CRASH_DUMP)thatmaybeusedwithANALYZEAO5/SHARED_MEMORYis /OVERRIDE.This qualifier,whichOO�is optional,allowslimitedaccesstothesharedmemorydumpMOæfilewhentryingto establishthecauseofa corruptedorO> incompletedump.KtÚœ!!Oƒ Qualifier description:luæÿBDOƒThe/SHARED_MEMORY qualifier indicatesthatasharedMOÜmemorydumpistobe analyzed.)TheSDAutilityisinvokedLO5toperformthe analysis,althoughitshouldbenotedthatMO�onlyalimitedsetofSDAcommandsarerelevanttosharedOæmemorydumps.vÚ„ÝOƒExample:9O $&ANALYZE/SHARED_MEMORY%GLX$SHARED_MEMORY.DMP6šq OpenVMS%(TM)%Alpha%system%dump%analyzer:š¹ ...analyzing%a&Galaxy%shared%memory&dump...O# shmSDA>&EXIT Ok $wÚ¦ÜEOƒThiscommandinvokesSDAtoanalyzethesharedmem->OÜorydumpfileGLX$SHARED_MEMORY.DMP.(NotethatGO5thisisthedefaultfilenamecreatedby DUMP/SHARED_O�MEMORY). ÒYXZ¸x ÆŽOÐ10.6CINSTALLNOUTheLISToptionnowreturnsthe galaxywidesectionsaswell)O­asstandardglobal sections. ¯ZY[•y …k4O 11.=Shared'Memory'Cluster' InterconnectOr(SMCI)IO÷TheSharedMemoryCluster Interconnect(SMCI)isanSCSFOOportforcommunicationsbetweenGalaxy instances.*WhenMO¨anOpenVMSinstanceisbootedasbothaGalaxyandasanGOOpenVMSCluster,theSharedMemoryCluster InterconnectLOYdriverwillbeloaded.*ThisSCSportdriverwillcommuni-MO±catetoothercluster instancesinthesameGalaxythroughHO sharedmemory.,This capabilityprovidesoneofthema-HObjor performancebenefitsoftheOpenVMSGalaxySoftwareJO» Architecture.*Theabilityto communicatetoanotherclus-FOteredinstancethroughsharedmemoryprovidesdramaticKOl performancebenefitsover traditionalclusterinterconnects. ñ [Z\•zèãk+OÐ11.1C SYS$PBDRIVERPortDevicesJOUWhenbootingasbothaGalaxyandasaclustermember,HO­ SYS$PBDRIVERwillbeloadedbydefault.,TheloadingofLOthisdriverwillcreateadevicePBAx,wherex representsOO^theGalaxy partitionId.*Asother instancesarebooted,theyKO·willalsocreatePBAxdevices.)TheSharedMemoryCIwillIOquicklydiscovertheother instancesandcreatecommuni-LOhcationschannelstotheother instances.+Unlike traditionalNOÁclusterinterconnects,anewdevicewillbecreatedtocom-NOmunicatetotheother instances.*ThisdevicewillalsohaveLOrthenamePBAx,wherex representstheGalaxy partitionIdKOÊfortheinstancewithwhichthisdeviceiscommunicating.${ì®úMOƒForexample,lookataGalaxy consistingoftwo instances:EOÜMILKYandWAY.MILKYisinstance0andWAYisin-IO5stance1.)WhennodeMILKYboots,itcreatesPBA0.)WhenNO�nodeWAYboots,itcreatesPBA1.)AsthetwonodesdiscoverIOæeachother,MILKYcreatesPBA1totalktoWAYandWAY-O>createsPBA0totalktoMILKY.à MILKY Dà WAY, PBA0:D, PBA1:!• PBA1:p <------->ºPBA0:Ü|! ²;OÐ11.1.1CMultipleClustersinaSingleGalaxyGO4 SYS$PBDRIVERcansupportmultipleclustersinthesameIOŒGalaxy.(Thisisdoneinthesamewaythat SYS$PEDRIVERLOåallowssupportformultipleclustersonthesameLAN.TheGO=clustergroupnumberandpasswordusedby SYS$PEDRIVERGO–arealsousedby SYS$PBDRIVERto distinguish differentLOîclustersinthesameGalaxy community.)IfyourGalaxyin-HOGstancesarealso clusteredwithotherOpenVMS instancesMOŸviatheLAN,theclustergroupnumberwouldbesetappro-DOøpriatelybyCLUSTER_CONFIG.To determinethecurrent!OQclustergroupnumber:OÕ $&MCR%SYMAN=O SYSMAN>& CONFIGURATION%SHOW%CLUSTER_AUTHORIZATION2Oe Node:%MILKYpCluster%group%number:%00O­ Multicast%address:%xx-xx-xx-xx-xx-xxOõ SYSMAN>'}á ýNOƒIfyouarenot clusteringoveraLANandyouwanttorunJOÜmultipleclustersinthesameGalaxy community,thenyouOO5mustsettheclustergroupnumber.'YoumustinsurethattheLO�groupnumberandpasswordissetthesameforallGalaxyFOæ instanceswhichyouwishtobeinthesamecluster.Ok $&MCR%SYSMAN[O² SYSMAN>& CONFIGURATION%SET&4CLUSTER_AUTHORIZATION/GROUP_NUMBER=222/PASSWORD=xxxxOú SYSMAN>~! °ñJOƒInmostcases,CLUSTER_CONFIGshoulddotherightthing.MOÜIfyourGalaxy instancesarealso clusteringovertheLAN,CO5CLUSTER_CONFIGwillaskforaclustergroupnumberPO�andtheGalaxy instanceswillutilizethosegroupnumbers.'IfLOæyouarenot clusteringoveraLAN,thegroupnumberwillPO>defaulttozero.)Thismeansthatall instancesintheGalaxy+O—willbeinthesamecluster. # \[][! w15OÐ11.2CSYSGEN Parametersfor SYS$PBDRIVERMOUInmostcases,thedefaultsettingsfor SYS$PBDRIVERshouldEO­be appropriate,howeverseveralSYSGEN parametersareDO provided.'TwoSYSGEN parameterscontrol SYS$PBDRIVER:&O^ SMCI_PORTSand SMCI_FLAGS.Œ€ ¸bOÐ11.2.1C SMCI_PORTSFO4The SMCI_PORTSSYSGEN parametercontrolsinitialload-GOŒingof SYS$PBDRIVER.This parameterisabitmasksuchROåthatthebits0through25each representa controllerletter.YO=Ifbit0isset,PBAxwillbeloaded.(Thisisthedefaultsetting.WO–Ifbit1isset,PBBxwillbeloaded,andsoonallthewayupNOîtobit25willcausePBZxtobeloaded.(ForOpenVMSAlphaIOGVersion7.2,we recommendleavingthis parameteratthe OŸdefaultvalueof1.‹�úaaKOƒLoading additionalportsallowsformultiplepathsbetweenHOÜGalaxy instances.*ForOpenVMSAlphaVersion7.2,havingJO5multiplecommunicationschannelsdoesnotprovideanyad-HO�vantagesbecause SYS$PBDRIVERwill initiallynotsupportKOæFastPath.*AfuturereleaseofOpenVMSwillprovideFastFO>Pathsupportfor SYS$PBDRIVER.WhenFastPathsupportKO—isenabled, instanceswithmultipleCPUscangetimprovedCOï throughputbyhavingmultiple communicationchannelsOHbetween instances.Ö‚! ¬OÐ11.2.2C SMCI_FLAGSCO4The SMCI_FLAGSSYSGEN parametercontrols operationalIOŒaspectsof SYS$PBDRIVER.Theonly currentlydefinedflagTOåisbit1.'ThiscontrolswhetherornottheportdevicesupportsHO=communicationswithitself.( SupportingSCScommunicationsXO–toitselfis primarilyusedfortest purposes.'Bydefault,thisbitLOîwillbeturnedoffandthussupportforSCS communicationLOGlocallyisdisabledwhichsavessystem resources.+Thispa-ROŸrameterisdynamicandbyturningthisbiton,anSCSvirtual&Oøcircuitshouldsoonform.Áƒ! 2— O•  OÝBitþMask¯ Description Oø  Ob0 ¨b0@b0=Donotcreatelocalcommunicationschannels8°(SYSGEN default).#LocalSCScommunications>ýare primarilyusedintest situationsandnot>Kneededfornormal operations.#Leavingthisbit=˜offsaves resourcesand overhead.%1=Create*ålocalcommunications channels. O_1 ¨_2>_0=Load SYS$PBDRIVERifbootingintobotha5­GalaxyandaCluster(SYSGEN Default).8ú1=Load SYS$PBDRIVERifbootingintoaHGalaxy. OÁ2 ¨Á4;Á0=Minimalconsoleoutput(SYSGENdefault)41=Fullconsoleoutput, SYS$PBDRIVER:\willdisplayconsolemessageswhencreating5ª communicationchannelsandtearingdown"÷ communication channels. O  §]\^ „ �ö3OÐ11.3CLANSharedMemoryDeviceDriver>OULocalAreaNetwork(LAN)communicationsbetweenJO­OpenVMSGalaxy instancesare supportedbyanewEthernetCOLANsharedmemorydriver.*ThisLANdrivercommuni-MO^catestoother instancesinthesameGalaxythroughsharedGO·memory.,Theabilityto communicatetoanotherinstanceHOthroughsharedmemoryprovides performancebenefitsoverOh traditionalLANs.á…ÿ·FOƒTheLANsharedmemorydriver, SYS$EBDRIVER,isloaded&OÜbythe followingcommand:Oa $mcr&sysman5O© io%conn&!eba/driver=sys$ebdriver/noadapterцöW§NOƒInafuturerelease,thisdevicedriverwillbeloadedau-HOÜ tomatically.+ForOpenVMSVersion7.2,inorderforLANNO5 protocolsto automaticallystartoverthisLANdevice(EBAn,IO�wherenistheunitnumber),the procedureforloadingMOæthisdrivershouldbeaddedtothe configuration procedure:"O> sys$manager:syconfig.com Ï>.»‡ W‘JOƒTheLANdriveremulatesanEthernetLANwithframefor-GOÜmatsthesameas Ethernet/IEEE802.3butwithmaximumHO5framesize increasedfrom1518to7360bytes.,TheLANJO�driverpresentsastandardOpenVMSQIOandVCI interfaceLOæto applications.*AllexistingQIOandVCILAN applications"O>shouldwork unchanged. ”^]_zˆÚªP5O 12.2OpenVMS!Galaxy"Tips"and! TechniquesO‘ TOBE SUPPLIED. ³_^`™‰; o:OüPartIV7 DevelopingProgramsForAnOpenVMS»jGalaxyQOChaptersinthispartdefine interfacesoftheGalaxySoftwareIO^ ArchitectureonOpenVMSthatare importantto developingNO« application programs.'Manyoftheconceptsare extensionsof=Oùthe traditionalsingle-instanceOpenVMSsystem. ñ`_aSŠ! ½)/O 13.2Locking! Programming! InterfacesTO‘OneofthemajorfeaturesoftheGalaxyplatformistheabilityMOêtoshare resourcesacrossmultiple instancesoftheoperat-OOBingsystem.)Aswithanyshared resource,theneedarisestoLO› synchronizeaccesstothat resource.)Theservices describedJOóinthischapterprovide primitivesuponwhichacoopera-MOLtiveschemecanbecreatedto synchronizeaccesstoshared'O¤ resourceswithinaGalaxy.>‹ö° OƒA¡ƒ galaxylock:zƒisa combinationofaspinlockandamu-MOÜtex.)While attemptingtoacquireanownedgalaxylock,theSO5threadwillspinforashortperiod.*Ifthelockdoesnotbe-SO�come availableduringthespin,thethreadwillputitselfintoOOæawaitstate.)Thisis differentfromSMP spinlocksinwhichSO>thesystemcrashesifthespintimesout,behaviorthatisnot$O— acceptableinagalaxy.îŒ WÄOOƒGiventhenatureofgalaxylocks,theywillreside somewhereGOÜinsharedmemory.+Thatsharedmemorycanbe allocatedQO5eitherbytheuserorbythegalaxylocking services.*IftheLO�user allocatesthememory,thelockingservicestrackonlySOæthelocationofthelocks.*Ifthelockingservicesallocatethe>O>memory,itismanagedonbehalfoftheuser.Ú� N°NOƒUnlikeother monitoringcodewhichisonlypartoftheMONQOÜversionof execlets,thegalaxylock monitoringcodeisalwaysO5loaded.~Ž! ÿTIOƒThereareseveralroutinesprovidedto manipulategalaxyMOÜlocks.+TheroutinesdonotprovideanythingbutthebasicsPO5whenitcomestolocking.*TheyarealittlericherthantheRO� spinlocksusedtosupportSMPbutfarlessthanwhatthelockOæmanager provides. , a`bö� 2Ì,OÐ13.1CSYS$CREATE_GALAXY_LOCK_TABLEJOUThisservice allocatesagalaxy locktable structure..ThisLO­ structureisusedtomaintain informationaboutthesharedLOmemorysection,whichthisservicealsocreates.+ThefirstRO^calleroftheservicewithaunique locktablenamecreatestheMO·section.( Additionalcallersmapit.(Thissharedmemorysec-SOtioncontainsasetofgalaxylocks.*AlllocksresidinginthePOhsectionareofthesamesize.+Oncethe locktableiscreated,AOÁtheSYS$CREATE_GALAXY_LOCKservicecanbeusedto;Ocreateandallocatealockfromthetable.˜�ÚWn8OƒTheflagsGLCKTBL$C_PROCESSand GLCKTBL$C_COÜSYSTEMspecifywhetherthesharedmemoryregionisHO5mappedintosystemspaceorprocessspace.-CreationofDO�processspacesectionsrequirestheSHMEM privilege.EOæCreationofsystemspacesectionsrequirestheSHMEM"O>andCMKRNL privileges.¢‘ÚõxEOƒ"sys$create_galaxy_lock_table(name,accmode, section_size,3OÜ section_type,prot, lock_size,handle) ’ fv O• O+ parameterbÝsizeb+(bytes)Átype+usage OF O°name b°8°inputbyvalue°addressofýthelocktableKname(ASCIZ)OÄaccmode bÄ4ÄinputbyvalueÄaccessmodeofthelocktableOŒsectionsize²8ŒinputbyvalueŒvirtualsizeofÙlocksectionOSsectiontype­4SinputbyvalueS glcktbl$c_ processorî glcktbl$c_;systemOµprot bµ4µinputbyvalueµ protectionap-pliedtolockPsectionOÊ lock_sizeø4ÊinputbyvalueÊsizeofthegalaxylocksinethesectionOÞhandle bÞ8ÞoutputbyrefÞlocktable,handle OG C“ÚœOƒReturnstatus:ÿ”ÚZÕÔÕ SS$_ACCVIOÔ. SS$_BADPARAMÔ† SS$_CREATEDÔß SS$_IVLOCKIDÔ7 SS$_NOPRIVÔ� SS$_NOSHMEMÔé SS$_NORMALCÔAAnystatusfromthesharedmemorysupportroutines bbac•ãî,OÐ13.2CSYS$DELETE_GALAXY_LOCK_TABLEMOUThisservicedeletesagalaxylocktable..IftherearenoOO­longeranymappersofthe locktablesection,whichthetable&O maintains,itisdeleted.Z–Úœ00Oƒsys$delete_galaxy_lock_table(handle)é—Ú7¿ O• O+ parameterbÝsizeb+(bytes)Átype+usage OF O°handle b°8°inputbyvalue°locktableýhandle O C˜ÚœOƒReturnstatus:ª™Ú©€ÔÕ SS$_BADPARAMÔ. SS$_IVLOCKIDÔ† SS$_IVLOCKTBLÔß SS$_NOPRIVÔ7 SS$_NOSHMEMÔ� SS$_NORMAL cbdŸšúÐu%OÐ13.3CSYS$RESET_GALAXY_LOCKUOUThisservicesetsagalaxylocktoastate consideredtobein-AO­validbytheSYS$ACQUIRE_GALAXY_LOCKservice.(ThisQOroutineisintendedtobeusedonlyonlockswhichresideinJO^sharedmemory allocatedbytheuserand initializedwithO·SYS$INIT_GALAXY_LOCK.O›Úœ%%Oƒsys$reset_lock(handle,va)DœÚþ O• O+ parameterbÝsizeb+(bytes)Átype+usage OF O°handle b°8°inputbyvalue°galaxylockýhandle Owva bw8winputbyrefwaddressofÄgalaxylock Oß C�ÚœOƒReturnstatus:‚žÚøXÔÕ SS$_BADLCKTBLÔ. SS$_IVLOCKIDÔ† SS$_LOCKINUSEÔß SS$_NORMAL �dce.Ÿ w&OÐ13.4CSYS$CREATE_GALAXY_LOCKOOUThisservices allocatesagalaxylockblockfroma locktable:O­createdwiththeSYS$CREATE_GALAXY_LOCK_TABLEHOservice.(ItthenusesSYS$INIT_GALAXY_LOCKto initialize O^it.� ÚõeGOƒ%sys$create_galaxy_lock(lcktbl_handle,name,timeout,size,OÜipl,rank,handle)„¡! fZ O• O+ parameterbÝsizeb+(bytes)Átype+usage OF O° lcktbl_handlen4°inputbyvalue°locktableýhandleOwname bw8winputbyrefwaddressof16ÄbyteASCIZnameofgalaxy_lockOÙtimeout bÙ4ÙinputbyvalueÙdefaultwait&timeout(10t microsecondÁunits)O;size b;4;inputbyvalue;sizeoflock Oµipl bµ4µinputbyvalueµIPLoflock(kernelmodePonly)OÊrank bÊ4ÊinputbyvalueÊrankoflock(notimple-emented)OÞhandle bÞ8ÞoutputbyrefÞhandleforthe,newlock OG C¢ÚœOƒReturnstatus:ÿ£Ú ÕÔÕ SS$_ACCVIOÔ. SS$_BADLCKTBLÔ† SS$_BADPARAMÔß SS$_CREATEDÔ7 SS$_IVLOCKIDÔ� SS$_IVLOCKTBLÔé SS$_INSFMEMÔA SS$_NOPRIVÔš SS$_NOSHMEMÔò SS$_NORMAL –edf;¤ð&OÐ13.5CSYS$DELETE_GALAXY_LOCKAOUThisservicesusesSYS$RESET_GALAXY_LOCKtoinval-OO­idatethegalaxylockandtodeleteit.*Thememoryforthe[Olockisnottrulydeleted,butisputonafreelistforlateruse.R¥Úœ((Oƒsys$delete_galaxy_lock(handle)ê¦Ú7À O• O+ parameterbÝsizeb+(bytes)Átype+usage OF O°handle b°8°inputbyvalue°galaxylockýhandle O C§ÚœOƒReturnstatus:¨ژÔÕ SS$_BADLCKTBLÔ. SS$_IVLOCKIDÔ† SS$_IVLOCKTBLÔß SS$_LOCKINUSEÔ7 SS$_NORMALÔ� SS$_NOPRIVÔé SS$_NOSHMEM !feg³©öƉ(OÐ13.6CSYS$GET_GALAXY_LOCK_INFOROUThisservicereturnsall "interesting"fieldsfromthe specifiedO­lock.‰ªÚõ_HOƒ sys$get_galaxy_lock_info(handle,name,timeout,size,ipl,OÜrank,flags)4«! 0  O• O+ parameterbÝsizeb+(bytes)Átype+usage OF O°handle b°8°inputbyvalue°galaxylockýhandleOwname bw8woutputbyrefwaddressof16ÄbyteASCIZnameofgalaxy_lockOÙtimeout bÙ4ÙoutputbyrefÙdefaultwait&timeoutO size b 4 outputbyref sizeoflockî structure Ohipl bh4houtputbyrefhIPLoflockOárank bá4áoutputbyrefárankoflockO[flags b[2[outputbyref[flagsfieldin©galaxylockö structure O C¬ÚœOƒReturnstatus:T­ÚG*ÔÕ SS$_IVLOCKIDÔ. SS$_NORMAL šgfhQ®øw'(OÐ13.7CSYS$GET_GALAXY_LOCK_SIZEIOUThisservicereturnstheminimumandmaximumsizeofaQO­galaxylock.(Ifalockiscreatedwiththemaximumsize,theMOlockingserviceswillrecordacquireandrelease informationO^inthelock.a¯Úœ77Oƒ"sys$get_galaxy_lock_size(min_size, max_size)M° þ# O• O+ parameterbÝsizeb+(bytes)Átype+usage OF O°min_sizeó4°outputbyref°MinimumsizeýofgalaxylockOwmax_sizeè4woutputbyrefwMaximumsizeÄofgalaxylock Oß C±ÚœOƒReturnstatus:>²ÚîÔÕ SS$_NORMAL C h gi½³ Г'OÐ13.8CSYS$ACQUIRE_GALAXY_LOCKSOUThisserviceisusedtoacquire ownershipofagalaxylock.(IfSO­thelockisfree,thecallerbecomestheownerandcontrolre-OOturns immediately.)Ifthelockisowned,basedontheinputSO^flagsandthetimeoutvalue,eitherthecallerwillwaitoran$O·errorwillbe returned.ÿ´ß°ÕMOƒThedefaultbehaviorwhenanattemptismadetoacquireaPOÜlockthatisowned,istospinfor10 microsecondsandthenPO5towait.-Ifawaittimeoutvaluewas specifiedinthecall,OO�itisused.- Otherwisethetimeoutvaluesetinthelockby6OæSYS$CREATE_GALAXY_LOCKorSYS$INIT_GALAXY_LO>LOCKwillbeused.)ThisbehaviorcanbechangedwiththeO—inputflags.šµ! õpMOƒIfjustGLOCK$C_NOSPINis specifiedandthelockisowned,#OÜnospinwillbedone.ç¶ W½EOƒIfjustGLOCK$C_NOWAITis specifiedandthelockisMOÜowned,thecallerwillonlyspinonthelock..Ifatime-WO5outvalueis specifiedinthecall,itisusedasthespintime.NO� Otherwise,thecallerwillspinfor10 microseconds.+IftheTOælockdoesnotbecome availableduringthespin,thelockisnot2O>acquiredand SS$_NOWAITis returned.û·úNÑIfGLOCK$C_NOBREAKis specified, SYS$ACQUIRE_BO— GALAXY_LOCKwillnotbreakthelock ownershipandOïreturns SS$_NOBREAK.e¹Úœ;;Oƒsys$acquire_galaxy_lock(handle,timeout,flags)*ºû»îIÑ O• O+ parameterbÝsizeb+(bytes)Átype+usage OF O°handle b°8°inputbyvalue°galaxylockýhandleOwtimeout bw4winputbyvaluewwaittime-Äout (overridesdefault)OŒflags bŒ4ŒinputbyvalueŒGLOCK$C_ÙNOWAIT&GLOCK$C_tNOSPINÁGLOCK$C_NOBREAK O* C¼ÚœOƒReturnstatus:î½Ú³ÄÔÕ SS$_BADPARAMÔ. SS$_BROKENÔ† SS$_IVLOCKIDÔß SS$_IVLOCKOPÔ7 SS$_IVLOCKTBLÔ�SS$_LOCK_TIMEOUTÔé SS$_NOBREAKÔA SS$_NOWAITÔš SS$_NORMAL 0ihj¾ï)ë'OÐ13.9CSYS$RELEASE_GALAXY_LOCKKOUThisservicereleases ownershipofagalaxylock.+BecauseLO­agalaxylockcanbeacquiredmultipletimesbythesameOOowner(nested ownership),thelockisnotreleaseduntiltheOO^ ownershipcountgoestozero.(Ifthelock ownershipiscom-OO·pletelyreleasedandthereareotherthreadswaitingforthe@Olock,theyarereleasedfromtheirwaitstates.S¿Úœ))Oƒsys$release_galaxy_lock(handle)êÀÚ7À O• O+ parameterbÝsizeb+(bytes)Átype+usage OF O°handle b°8°inputbyvalue°galaxylockýhandle O CÁÚœOƒReturnstatus:�ÂÚøWÔÕ SS$_IVLOCKIDÔ. SS$_IVLOCKOPÔ† SS$_IVLOCKTBLÔß SS$_NORMAL ^ jikD ö g )OÐ13.10CLockingErrorMessages.tD IVLOCKOP%E¿­ An%attempt&was%made&to&release%a%lock&that%is%not¿õ owned.E¿^ Check%that&all%calls%to%acquire&a%lock%are%matched%¿¦ by%calls%to%release&it.+t IVLOCKTBL&E¿y The%lock%table%handle%passed&to&the%locking&service6¿Á does&not% represent%a%valid%lock&table.F¿* Verify%that%the%lock%table%handle%being%used%is%theD¿r same&as&that%returned%by%SYS$CREATE_GALAXY_LOCK_TABLE)¿º or%SYS$INIT_GALAXY_LOCK_TABLE.=t# LOCKINUSE&I¿Œ An%attempt&was%made&to&delete%a&lock%which%is%in%useF¿Ô or%to% initialize&a%lock%which%is%already& initializedI¿= Verify%that%the%lock%handle%being%used%is%the%same%as8¿… that&returned&by&SYS$CREATE_GALAXY_LOCK%or¿Í SYS$INIT_GALAXY_LOCK.Nt6 LOCK_TIMEOUT&?¿Ÿ An%attempt&to&acquire%a%lock&did%not%complete'¿ç during%the&timeout%period.A¿P This&problem%could%be%caused&by&a%timeout%value>¿˜ that&is&too%small.%It%can&also%be%caused&by8¿à a&thread%holding&the%lock&for%too%long.7tJ BADLCKTBL&C¿³ The%list%of%locks%in%the% specified&lock%table%is¿û corrupt.8¿d Lock&tables%are%writable%from%the%accessA¿¬ mode&in&which&they%are&created.&Verify%that&the>¿ô application%is%not% overwriting%the&lock%table.Lz] NOBREAKKA¿Æ An%attempt&to&acquire%a%lock&failed%because&theB¿ lock& ownership%had%been%broken%and&GLOCK$C_NOBREAKE¿V was% specified&on&the%call&to&SYS$ACQUIRE_GALAXY_LOCK.E¿¿ Lock& ownership%being%broken%can&be&the%result%of%aA¿ process&or&system%failure&while&a%lock%is%held.?¿O Depending%on%how&the%lock&is&used,&this%couldC¿— mean&that%the&data%this%lock&protects&is&corrupt.Ft NOWAITKA¿i An%attempt&to&acquire%a%lock&failed%because&the9¿± lock&is& currently%owned%and%GLOCK$C_NOWAITD¿ù was% specified&on&the%call&to&SYS$ACQUIRE_GALAXY_LOCKC¿b The% application%must%either%retry%the& operation%or6¿ª wait&for%the%lock%to%become% available.Hz BROKENJ@Ï} An%attempt&to&acquire%a%lock& succeeded%but%theB¿Å previous%owner%of%the%lock%no%longer%existed%and&¿  its% ownership&was%broken.E¿v Lock& ownership%being%broken%can&be&the%result%of%aA¿¾ process&or&system%failure&while&a%lock%is%held.?¿ Depending%on%how&the%lock&is&used,&this%couldC¿N mean&that%the&data%this%lock&protects&is&corrupt. ÏkjlµÄ ‹6O 14.2System!Events! Programming" InterfacesNO‘ ApplicationscanregistertobenotifiedwhencertainsystemOOêeventsoccur;forexample,whenaninstancejoinsthegalaxyUOBorifaCPUjoinsa configureset.(Ifeventsare registered,anKO› applicationcandecidehowtorespondwhenthe registeredOóeventsoccur. Þ"l-kmgÅÚn=!OÐ14.1C$SET_SYSTEM_EVENTOUSetSystemEvent‘ÆÚõgGOƒ Establishesarequestfor notificationwhenanOpenVMS OÜsystemeventoccurs.;ÇÚœOƒFormat:…È õ[BOƒSYS$SET_SYSTEM_EVENT(event,astadr,astprm,acmode,OÜflags,handle)AÉÚœOƒC Prototype:ÊÚYóAOƒint sys$set_system_event (unsigned int event,"void OÜ( jè*C�Ü astadr)(_ _unknown_params),intastprm,unsignedint=O5acmode,unsignedintflags,struct _generic_64 ê@*)5handle;>ËÚœOƒ Arguments:9ÌÚœOƒ eventÐÍÚ·¦OãOpenVMSO0usage:bã event_codeOªtype:bªlongword (unsigned)O$access:b$readonlyOž mechanism:ŽbyvalueÎÚNçKOƒEventcode indicatingthetypeofsystemeventforwhich.OÜanASTistobe delivered.+The«Ü event ¢Üargumentisavalue?O5 indicatingwhichtypeofeventisof interest.©ÏÚõEOƒEacheventtypehasasymbolicname.+The $SYSEVTDEF:OÜmacrodefinesthe followingsymbolicnames.Ð p Ö O• OÝSymbolicNameÝ Description Oø ObSYSEVT$C_ADD_MEMBER bOneormoreOpenVMS!° instanceshavejoinedýtheOpenVMSGalaxyKsharing community.OÄSYSEVT$C_DEL_MEMBER ÄOneormoreOpenVMS instanceshaveleft_theOpenVMSGalaxy­sharing community.!O&SYSEVT$C_ADD_ACTIVE_CPU &Oneormoreproces-$tsorshavebecomeactiveÁwithinthisOpenVMS instance.#O‰ SYSEVT$C_DEL_ ACTIVE_CPU#‰Oneormore processors Öhavebecomeinactive$withinthisOpenVMSqinstance!OëSYSEVT$C_ADD_CONFIG_CPU ëOneormoreproces-$8sorshavebecomeactive†withinthisOpenVMSÓ instance.!OMSYSEVT$C_DEL_CONFIG_CPU#MOneormore processors ›havebecomeinactiveèwithinthisOpenVMS6  instance. OQ  :ÑÚœOƒ astadrüÒÚiÒOãOpenVMSusage:3ã ast_procedureO]type:3] procedurevalueOÖaccess:)3Öcallwithoutstack unwindingOP mechanism:+3Pby32-bitor64-bit reference«Óñõ�POƒ NotificationASTroutinetoreceivecontrolafterachangein1OÜOpenVMSsystem configurationoccurs.:ÔÚœOƒ astprmÂÕÚi˜OãOpenVMSusage:3ãuser_argO]type:3]quadwordOÖaccess:3ÖreadonlyOP mechanism:3Pbyvalue�ÖÚõWEOƒThequadwordAST parametertobepassedtotheASTOÜroutine.:×ÚœOƒ acmodeÓØÚi©OãOpenVMSusage:3ã access_modeO]type: 3]longword (unsigned)OÖaccess:3ÖreadonlyOP mechanism:3PbyvalueÞÙñN´LOƒAccessmodeatwhichthesystemeventASTistoexecute. OÜTheôÜ acmode flagþ>isnotset.jèÚœ@@OƒErrorswillbereturnedinthe followingcases:sé ÛI `Ð ·LÔÐIfquotasare exceeded,anerrorwillbe returned.+ItisIÔ( importanttonotethatthisroutinewillreturnaner-PÔ�rorandwillnotretryanattempttogetquotaifquotais-ÔÚ exhaustedonthefirstattempt. `Y ·HÔYSeethe ConditionValuesReturnedsectionfortypesof*Ô±errorsthatcanbe returned. `1 ·Ô1Ifthe¶1 astadr6î1argumentisomitted,andanewnotifi-EÔ‰cationobjectisbeingcreated, SS$_BADPARAMwillbeÔâ returned. `a ·ÔaIfthe¸a event5Ìaargumentis incorrectly specified,SS$_'ÔºBADPARAMwillbe returned. `9 ·KÔ9Iftheaccessmode parameterismore privilegedthantheMÔ’modeofthecaller,themodeofthecallerwillbeused. ` ·ÔIf specified,the handle'Gargumentmustbe writeableIÔifromthemodeofthecaller.) SS$_ACCVIOisreturnedif#ÔÂthisisnotthecase.HêÚœOƒRequired Privileges9ëÚœOƒNone.CìÚœOƒRequiredQuota:íÚœOƒASTLM.EîÚœOƒRelatedServicesGïÚœOƒ$CLEAR_SYSTEM_EVENTOðÚœ%%Oƒ ConditionValuesReturnedñ! ñOã SS$_NORMAL03ãTheservice completed successfully.O] SS$_ACCVIO63]Theservicecannotaccessthe locations23ª specifiedbyoneormore arguments.O$ SS$_BADPARAM43$Oneofmore argumentshasaninvalid3qvalue.Oë SS$_EXASTLM13ëTheprocessexceededitsquotafor38 outstandingASTs.O² SS$_INSFMEM23²Thesystemdynamicmemoryisinsuf-.3ficienttocompletetheservice. mlnkòÚnA#OÐ14.2C$CLEAR_SYSTEM_EVENTOUClearSystemEvent6ó ¦ NOƒClearEventdoesnotallowyoutospecifyahandleandanPOÜevent.'Youmustpassazeroasoneofthese parameters.'YouRO5caneitherclearbyhandleorrequestthatalleventsfortheO�userbecleared.®ôñõ„LOƒRemovesoneormore notificationrequests previouslyestab-8OÜlishedbyacalltoSYS$SET_SYSTEM_EVENT.;õÚœOƒFormat:göÚœ==OƒSYS$CLEAR_SYSTEM_EVENT [handle], [acmode],eventA÷ÚœOƒC Prototype:¹øÚõ�;Oƒintsys$clear_system_event(struct _generic_64 �*aƒhandle,8OÜunsignedintacmode,unsignedintevent);>ùÚœOƒ Arguments::úÚœOƒ handleÔûÚiªOãOpenVMSusage:3ã identifierO]type:3]quadword (unsigned)OÖaccess:3ÖreadonlyOP mechanism:3Pby referencetü ÿJFOƒIdentificationoftheASTrequesttobecleared.+Theœƒ han- OÜ dleIéÜargumentuniquely identifiestherequestandisreturnedAO5whenthe$SET_SYSTEM_EVENTserviceiscalled.,TheO� handle=‡�argumentmaybeomittedby specifyingazeroOæaddress.:ýÚœOƒ acmodeÓþÚi©OãOpenVMSusage:3ã access_modeO]type: 3]longword (unsigned)OÖaccess:3ÖreadonlyOP mechanism:3Pbyvalue/ÿ ¦EOƒAccessmodeofthesystemeventtobecleared.'The“ƒ acmodeHOÜargumentisalongword containingtheaccessmode.+TheNO5valueoftheaccessmodeis maximizedwiththeaccessmodeO�ofthecaller.9ÚœOƒ eventÐÚi¦OãOpenVMSusage:3ã event_codeO]type:3]longword (unsigned)OÖaccess:3ÖreadonlyOP mechanism:3PbyvalueýïNÓ OƒTheõƒ eventAëƒargumentisavalue indicatingthetypeofsys-DOÜtemeventtobecleared.)SYSEVT$C_ALL_EVENTSmaybe2O5 specifiedtoclearalleventtypes.?ÚœOƒ DescriptionóúNÉKOƒTheClearSystemEventserviceremovesoneormoreeventTOÜtypesor notificationobjects previously establishedbyacallto*O5the$SET_SYSTEM_EVENTservice.Dã¦3OƒAvalidrequest specifieseithertheVƒ handle�ƒforaspecificPOÜ notificationrequest,orisawildcardclearofall notifica-RO5tionobjectswhoseisaccessmodeisgreaterthanorequaltoO� acmode ©�.ðþNÆOƒIftheMƒ handle:„ƒargumentis specified,caller'saccessmodeUOÜmustbelessthanorequaltotheaccessmodeoftheobjecttoO5becleared.Ý! N³KOƒIfSYSEVT$C_ALL_EVENTSis specified,orthesetofeventsROÜenabledforthe object(s)becomesempty,the notificationobjectO5isdeleted.TÚœ**OƒRequiredAccessor Privileges8 ÚœOƒNoneC ÚœOƒRequiredQuota8 ÚœOƒNoneE ÚœOƒRelatedServicesE ÚœOƒ$SET_SYSTEM_EVENTOÚœ%%Oƒ ConditionValuesReturned*Á! Q—Oã SS$_NORMAL03ãTheservice completed successfully.O] SS$_ACCVIO53]Theservicecannotaccessthelocation%3ª specifiedbythehandle.O$ SS$_BADPARAM43$Oneofmore argumentshasaninvalid03qvalue,suchasaninvalidhandle.Oë SS$_NOSUCHOBJ03ëNorequestwasfoundthatmatches$38the descriptionsupplied énmoÏá ¥6O 15.2Shared!Memory" Programming! Interfaces O‘A) ‘ SharedMemoryGlobalSectionµ‘mapssomeamountOOêofmemorythatcanbeaccessedonall instancesinashar-sharedmemoryglobalsection.L ¦"EOƒIncontrasttomemoryresidentsectionstheReservedOOÜMemoryRegistryisnotusedtoallocatespacefor galaxywideHO5 sections.)SharedmemoryisnotusedfornormalOpenVMSFO�paging operationsand thereforeneednotbe reserved. 5poqJÚé  OÐ15.2CSystemServicesÿÚþÕ$OÐ15.2.1CEnhancedServicesJO4The followingsystemserviceshavebeenenhancedtorec-OŒognizethenew)�Œ sharedmemoryglobalsection•ŒflagOå SEC$M_SHMGS:¸ÚlŽ `Õ ·ÔÕSYS$CRMPSC_GDZRO_64 `U ·ÔUSYS$CREATE_GDZRO `Ô ·ÔÔ SYS$MGBLSC_64 `S ·ÔS SYS$DGBLSC±Úõ‡JOƒThe followingsystemserviceswereenhancedtoworkwith=OÜsharedmemorybutno interfaceswerechanged:àÚë¶ `Õ ·ÔÕ SYS$DELTVA `U ·ÔU SYS$DELTVA_64 `Ô ·ÔÔSYS$CREATE_BUFOBJ `S ·ÔSSYS$CREATE_BUFOBJ_64 `Ò ·ÔÒSYS$DELETE_BUFOBJb! `8:OÐ15.2.2CNewSectionFlagSEC$M_READ_ONLY_SHPTAO4ThenewsectionflagSEC$M_READ_ONLY_SHPTisrec->OŒognizedbytheSYS$CREATE_GDZROand SYS$CRMPSC_ROåGDZRO_64 services.'Whenthisbitisset,itdirectsthesystemPO=tocreatesharedpagetablesforthesectionthatallowonlyOO–readaccess.*Thisfeatureis particularlyusefulinanenvi-JOîronmentwhereamemoryresidentorGalaxysharedsectionDOGisusedbymanyreadersbutonlyasinglewriter.ã N¹JOƒWhenyoumapaGalaxysharedormemoryresidentsectionROÜthathasan associatedsharedpagetablesection,youhavetheO5 followingoptions:Dª ©' O• OxSharedpagetablesÝDesired +ac-xcess O“ 3ýREADONLY:ýREAD KAND ˜/ORåWRITE:O_nonecreated&3_Donotsetthe SEC$M_WRT&3­flaginthemaprequest.*3&Privatepagetableswillal--3twaysbeused,evenifyouare*3Á specifyingasharedpageta-+3bleregionintowhichtomap3\thesection._Setthe­SEC$M_ úWRTHflag•inthe ãmap 0re-~quest.÷PrivateEpage’tablesàwill-always {beÈused,evencifyou ±areþspeci-L fyinga™ sharedç page4 table‚ regionÏ into whichj tomap ¸ the sec-S tion.OÌ writeaccess&3Ì Donotsetthe SEC$M_WRT&3 flaginthemaprequest.%3” Ensurethatprivatepage*3á tableswillbeused.%Donot)3/specifyasharedpagetable+3|regionintowhichtomapthe,3Êsection.#Ifyoudo,theerror"3status SS$_IVSECFLGis3e returned.Ì Setthe SEC$M_ g WRTµ flaginthe Pmap �re-ëquest. eThe²sharedpageMtable›sectionèwillbe6used ƒforÐmap-pingkifyou¹spec-ifyaTshared¡pageïtable<regionŠinto×which%tomap rtheÀsec- tion.O‡readaccess&3‡Donotsetthe SEC$M_WRT+3Õflaginthemaprequest."The,3"sharedpagetablesectionwill)3pbeusedformappingifyou)3½specifyasharedpagetable+3 regionintowhichtomapthe3Xsection.‡SettheÕSEC$M_ "WRTpflag½inthe  map Xre-¥quest.óEnsure@thatŽprivateÛpage)tablesvwillbeÄused.Donot_spec-¬ifyaúsharedGpage•tableâregion0into}whichËtomap thefsec-³tion.IfyouNdotheœerroréstatus7 SS$_„ IVSECFLGÒ isre-!turned. O:!  ÔÂ!MBÅ!Notes Â!MHÔJ"SharedpagetablesforGalaxysharedsectionsarealso?Ô£" implementedasGalaxyshared sections.,Thisim-GÔû"pliesthattheyalloweitherreadaccessonlyonallDÔT#OpenVMS instances connectedtothissectionortheyJÔ¬#allow read/writeaccessonall instances.'Thesettingof8Ô$theSEC$M_READ_ONLY_SHPTflagas requestedOÔ]$bythefirstinstancetocreatethesectionisusedonallÔ¶$ instances.:Ô0%UsingtheSYS$CRMPSC_GDZRO_64servicealwaysAÔˆ%impliesthatthe SEC$M_WRTflagissetandthatHÔá%youwanttomapthesectionforwriting.'IfyouwantLÔ9&tousethisservicetocreateasectionwithsharedpageIÔ’&tablesforreadonlyaccess,youmustuseprivatepageCÔê&tablesandyoucannotspecifyasharedpagetable5ÔC'regionintowhichtomapthesection. Ô�'— 'qpr? �,OÐ15.3C GalaxywideGlobalSectionsIOUTheSHMEM privilegeisrequiredtocreateanobjectinNO­Galaxysharedmemory.'Therighttomaptoanexistingsec-MOtionis controlledthroughnormalaccesscontrol mechanisms.GO^SHMEMisnotneededtomapanexistingsection.,NoteBO·thattheVMS$MEM_RESIDENT_USER identifier,whichisNOneededtocreateanordinarymemoryresidentsectionisnot.Ohrequiredfor galaxywide sections.%! ¦ûGOƒCreatingandmapping galaxywidememorysectionsisac-LOÜ complishedthroughthesameservicesusedtocreatememoryLO5resident sections.*The followingservicesnow recognizetheO� SEC$M_SHMGSflag:Œ ÚøbÔÕSYS$CREATE_GDZROÔ.SYS$CRMPSC_GDZRO_64Ô† SYS$MGBLSC_64Ôß SYS$DGBLSCÍ!ÚN£4OƒSYS$CREATE_GDZROandSYS$CRMPSC_GDZRO_640OÜcanalsoreturnnewstatuscodes.#Ü Tobe supplied-more O5 detailsaboutthese:o"! QEOãSS$_INV_O0SHMEM)¿ãSharedmemoryisnotvalid.NOª SS$_INSFRPGS€ Insufficientfreesharedpagesorprivatepages.RO$ SS$_NOBREAK‹AGalaxylockisheldbyanothernodeandwasnot¿qbroken.Oë SS$_LOCK_O8TIMEOUT&¿ëAGalaxylocktimedout.ã#ÚN¹=Oƒ$INSTALL LIST/GLOBALand$SHOWMEMORYalso+OÜknowabout glaxywide sections.ÜÜ Tobe supplied-some2O5 additional documentationaboutthese.¬$! ÿ‚NOƒ Galaxywidesectionsareusingtheirownnamespace.'JustasPOÜyoucouldalwaysusethesamenametoidentifysystemglobalLO5sectionsandgroupglobalsectionsforvariousownerUICs,NO�youcannowalsohave galaxywidesystemglobalsectionsandJOæ galaxywidegroupglobalsectionsallwiththesamename.t%ÚœJJOƒ Galaxywidesectionsalsohavetheirownsecurityclasses:h&ÚA>ÔÐGLXSYS_GLOBAL_SECTIONÔ(GLXGRP_GLOBAL_SECTIONÒ'ìN¨HOƒThesesecurityclassesareusedwiththe$GET_SECURITY,>OÜ $SET_SECURITYsystem services,andtheSET/SHOW"O5SECURITYDCL commands:Á(ßõ—OOƒThesenewsecurityclassesareonlyvalidinaGalaxyenvi-HOÜronment.'Theyarenot recognizedona non-galaxynode.Ë)! õ¡ROƒYoucanonlyretrieveandaffectsecurity attributesofgalaxy-OOÜwideglobalsectionsiftheyexistonyoursharing instance.Š*\0`GOƒAuditmessagesfor galaxywidesectionslooklikethis:pO %%%%%%%%%KOPCOMK 20-MAR-1998% 10:44:43.71J%%%%%%%%%(from%node%GLX1&at& 20-MAR-1998& 10:44:43.85)5OP Message&from%user% AUDIT$SERVER%on%GLX1DO˜ Security%alarm% (SECURITY)&on&GLX1,&system%id:%19955Oà Auditable%event:à Object%creationO( Event% information:'( global%section&map%requestOp Event%time:"p 20-MAR-1998& 10:44:43.84O¸ PID:¸ 2040011AO Process&name: ANDYOH Username:H ANDYO� Process&owner:� [ANDY]OØ Terminal%name:Ø RTA1:O  Image%name:*  MILKY$DKA100:[ANDY]SHM_MAP.EXE;1Oh Object%class%name:h GLXGRP_GLOBAL_SECTIONO° Object%name:*° [47]WAY____D99DDB03_0$MY_SECTIONAOø Secondary%object&name:– O@ Access% requested:@ READ,WRITEOˆ Deaccess%key:ˆ 8450C610OÐ Status:FÐ %SYSTEM-S-CREATED,%file&or&section%did&not%exist;%hasO been&createdé+ñN¿JOƒNotethe"Objectname"record:+theobjectname displayedMOÜhereuniquely identifiesthesectionintheOpenVMSGalaxy.(O5Thefieldsareasfollows:h,ãØ>Oã[47]?Kã(onlyforgroupglobal sections) identifiesthe0K0UICgroupofthesectioncreator.OªWAY_ __ _D99DDB03_ O÷0$7KªAn identifierforthesharing community.Oq MY_SECTION=KqThenameofthesectionas specifiedbytheK¿user.x- ÿNQOƒTheusercanonlyspecifythesectionnameandclassforre-ROÜqueststosetorshowthesecurityprofile.(TheUICisalwaysKO5obtainedfromthecurrentprocessandthe communityiden-MO�tifierisobtainedfromthe communityinwhichtheprocessOæ executes.<. ¦QOƒTheoutputfora galaxywidesystemglobalsectiondiffersonlyQOÜinthefields"Objectclassname"and"Objectsname".(Theob-PO5jectnameforthistypeofsectiondoesnotincludeagroup O�identificationfield:Ž/ÚdOãObjectclassO0name:¿ãGLXSYS_GLOBAL_SECTION=OªObjectname:ÚWAY_ __ _D99DDB03_0$SYSTEM_SECTION Ô,$/ ImportantSecurityNotes Z,CÔ´Security attributesfora galaxywidememorysectionGÔ mustappear identicaltoaprocessnomatteronwhat&Ôeinstanceitis executing.GÔßThiscanbeachievedbyhavingall instancespartici-EÔ7patinginthissharing communityalso participatein?Ô�a "homogeneous"OpenVMSClusterwhereallnodes/Ôèsharethesecurityrelatedfiles:û0Ú«Ñ5YÐ SYSUAF.DAT, SYSUAFALT.DAT(systemautho-Y(rizationfile),Y�RIGHTSLIST.DAT(rights database).YÚVMS$OBJECTS.DAT(objects database)AÔ^In particular, automatic propagationof protectionBÔ·changestoa galaxywidesectionrequiresthatthe?Ôsamephysicalfile(VMS$OBJECTS.DAT)isusedby"Ôhallsharing instances.JÔâIfyour installationdoesnotsharethesefilesthrough-DÔ:outtheGalaxy,thecreatorofa galaxywidesharedHÔ“sectionmustensurethatthesectionhasthesamese-FÔìcurity attributesoneach instances.(ThismayrequireÔDmanual intervention. Ô�— «rqs‘1 ªg7O 16.2CPU! Management! Programming" Interfaces0O‘ Tobe supplied:'includeanintro. ¢4s/rt¤2ÚÐz"OÐ16.1CSYS$CPU_TRANSITIONGOUOnAlphasystems,changesthecurrent processingstateOO­ofaCPUinthe configuresetofthecurrentsystemoranBO unassignedCPUinanOpenVMSGalaxyconfiguration.EO^Thisservice completesasynchronously.,For synchronous;O· completion,usethe$CPU_TRANSITIONWservice.Õ3ÚN«IOƒThisserviceaccepts64-bit addresses., ParameterandbitGOÜ definitionsareresolvedin$CSTDEFinthe appropriateO5STARLETlibrary.´4Ú¦ŠOÅFormatO�node_id,flags,efn,iosb, astadr_64, astprm_64P5ÚM&OÅ ArgumentsO4 tran_codeÎ6Úi¤OãOpenVMSusage:3ãlongwordO]type:3]longword (unsigned)OÖaccess:3ÖreadonlyOP mechanism:3Pbyvalue 7 NáQOƒ Identifier specifyingthetypeofstatechangetobe initiated$OÜonthetargetCPU.The¾Ü tran_code#sÜargumentisalongword6O5 containingoneofthe followingvalues:Y8 Ê/ O• OÝSymbolicName3Ý Description Oø ObCST$K_CPU_STOP53bThetargetCPUistoberemovedfrom63°theactivesetandhaltedintoconsole53ýmode."Itremainsinthe configureset&3Kofthecurrent partition.EOÄCST$K_CPU_MIGRATEßThetargetCPUisremovedfromthe83 configuresetofthelocal partitionand;3_theconsoleis requestedtoaddittothe73­ configuresetofthe partition specified33úinnode_id.$IftheCPUis currently63Hintheactiveset,itis automatically23•broughttoconsolemodethroughthe*3ãCST$K_CPU_STOPfunctionfirst.O\CST$K_CPU_START33\ThetargetCPUis requestedtoexit83ªconsolemodeandjointheactivesetof23÷thecurrent partition.#TheCPUmust53Ealreadybepartofthe configureset.HO¿CST$K_CPU_FAILOVERÄTheCPUisassignedadefaulttarget/3  partitionwhereitwill automati-43Zcallymigrateonsystemfailure.#This53§ assignmentpersistsuntilitissuper-03õseded.$Toremovean assignmentor33B partitionname,thecurrent partition$3�IDshouldbe specified. O« :9ÚœOƒ cpu_idÎ:Úi¤OãOpenVMSusage:3ãlongwordO]type:3]longword (unsigned)OÖaccess:3ÖreadonlyOP mechanism:3Pbyvalue›;! qLOƒ IdentifieroftheCPUwhosestateistobe modified.'The*ƒ cpu_ OÜ idFºÜargumentisalongwordnumberinthe supportedrangeHO5of individualCPUsfrom0to SYI$_MAX_CPUS-1.)InaOO�Galaxy,thisCPUmustbeinthe configuresetofthelocalROæ partitionornotassignedtoanyother partitions.'ThesymbolicBO>values,CST$K_ANY_LOCAL_CPUcanbeusedincertainUO—typesof transitionstoallowthenext available processoroftheEOï appropriatetypebeusedinsteadofaspecificone.;<ÚœOƒ node_idÎ=Úi¤OãOpenVMSusage:3ãlongwordO]type:3]longword (unsigned)OÖaccess:3ÖreadonlyOP mechanism:3Pbyvalueþ>! WÔHOƒ IdentifierofthetargetGalaxy partitionin CST$K_CPU_6OÜASSIGN,CST$K_CPU_FAILOVER,or CST$K_CPU_#O5MIGRATE transition.,The.5 node_id •5argumentisalong-IO�word containinganumberinthe supportedrangeofIDsPOæprovidedbytheconsoleforthecurrenthardware platform.'If O>theÙ> nodename#£> parameteris specified,Û> node_id?>isignored.9?ÚœOƒ flagsÓ@Úi©OãOpenVMSusage:3ã longword_maskO]type:3]longword (unsigned)OÖaccess:3ÖreadonlyOP mechanism:3PbyvaluexAõÿNCOƒOptionsselectedfortheCPUstate transition.)Themƒ flags Cƒar-LOÜgumentisalongwordbitvectorwhereinabit correspondsMO5toanoption./Onlythebits specifiedbelowareused; theJO� remainderofthelongwordbitsarereservedandmustbe Oæ0. B Nã;OƒEachoption(bit)hasasymbolicname.(Theˆƒ flags]ƒargumentPOÜis constructedby performingalogicalOR operationusingthe7O5symbolicnamesofthe followingoptions:*C$D ú O• OÝSymbolicName3Ý Description Oø ObCST$V_CPU_DEFAULT_O° CAPABILITIES83bAtthe completionofthe transition,the73°CPU'suser capabilitiesaresetbackto83ýthedefaultsystemvalue.!Ifthisoption43Kisnot specified,modifiedusercapa-13˜bilitiesare maintainedacrossSTOP43åandSTART transitionsaslongasthe133CPUremainsinthelocal partition3€ configureset.OúCST$V_CPU_ALLOW_OHORPHANS43úThe transitionistobeallowedeven93Hthoughitwillleaveatleastonethread73•inthesystemunabletoexecuteonany$3ãCPUintheactiveset. Oþ 7EÚœ  Oƒ efnÏFÚi¥OãOpenVMSusage:3ã ef_numberO]type:3]longword (unsigned)OÖaccess:3ÖreadonlyOP mechanism:3PbyvalueBG ¦SOƒTheeventflagtobesetwhenthestate transitionattempthasOÜ completed.*The ”Ü efn45Üargumentisalongword specifyingtheQO5numberoftheeventflag;however,thisserviceonlyusestheO� low-orderbyte.ÓH N©DOƒWhenyouinvoke$CPU_TRANSITION,the specifiedeventSOÜflagiscleared;whenthe operationis complete,theeventflagO5isset.8IÚœOƒ iosbèJÚi¾OãOpenVMSusage:3ãio_status_areaO]type:3]IOSB structureOÖaccess:3ÖwriteonlyOP mechanism:+3Pby32-bitor64-bit referenceûK! WÑQOƒTheI/Ostatusareatoreceivethefinal completionstatusof*OÜthe transition operation.(TheqÜ iosb'1Üargumentisthe32-bitorQO564-bitvirtualaddressoftheI/Ostatusarea.*TheI/OstatusVO�area structureis32bytesinlength;its definitioncanbefoundGOæin$IOSBDEFin STARLET.MLBformacroandinthefile3O> IOSBDEF.HinSYS$STARLET_C.TLBforC.åL! N»GOƒWhenyoucall$CPU_TRANSITION,theI/OstatusareaisTOÜcleared.'Afterthe transition operationis complete,theblockis O5modifiedasfollows:àMý™¶ O• OÝSymbolicName3Ý Description Oø Ob iosb$w_status13bThefirstwordcontainsthecondi-63°tionvaluereturn, indicatingthefinal13ý completionstatusofthe operation.93wThefirstbitinthesecondwordofthe63ÄIOSBissetonlyifanerroroccurred13duringthe operation;the remaining3_bitsarezeroes. Oz =NÚœOƒ astadr_64üOÚiÒOãOpenVMSusage:3ã ast_procedureO]type:3] procedurevalueOÖaccess:)3Öcallwithoutstack unwindingOP mechanism:+3Pby32-bitor64-bit reference©P! ÿOOƒTheASTroutinetobeexecutedwhenthe requested transitionJOÜattempthas completed.)The astadr_64argumentisthe32-VO5bitor64-bitvirtualaddressofthisroutine.'IfyouspecifytheLO� astadr_64 argument,theASTroutineexecutesattheaccessDOæmodefromwhichthestate transitionwas requested.=QÚœOƒ astprm_64ÂRÚi˜OãOpenVMSusage:3ãuser_argO]type:3]quadwordOÖaccess:3ÖreadonlyOP mechanism:3Pbyvalue„SéõZKOƒThequadwordAST parametertobepassedtotheASTrou-OÜtine.*T¸UÚ¦ŽOÅ Description$O4Thestate transitionin‹4 tran_id)Ò4is requestedforthetargetO� cpu_id d�.mVÚœCCOƒACPU currentlyintheactivesetcan transition:ÁWöA— `Ð ·HÔÐTotheSTOPPEDstate;removedfromtheactivesetandDÔ(leftinthe configureset,haltedinconsolemode.eXÚœ;;OƒACPUinthe configuresetcan transition:±Y r‡ `Ð ·GÔÐTotheACTIVEstate;warmrebootedandafullmemberDÔ(oftheSMPactivesetonthe requesting partition. `¨ ·EÔ¨Toanother partitionthrough reassignmnet;thetargetJÔCPUisremovedfromthe configuresetandaddedtothe;ÔY configuresetofthe partition specifiedby“Y node_id øY.6Z! ¹ FOƒCPU state transitionis a two-phase operation intheIOÜOpenVMS schedulingmodel.+Thisservice initiatesthere-NO5questintheprocesscontextofthecallerandreturnsthePO�setupstatusintheservice conditionvalue.(Phase2proceedsOæasynchronously;the 0æ efn Ñæandqæ iosb&æ argumentscanbeusedtoPO>indicatethe completionofthe transitionthroughthestandardMO—waitsystem services.* Additional notificationofthecomple-EOïtioncanbemadethroughtheOpenVMSAST mechanisms*OHusingaroutine specifiedin2H astadr_64ÓHanda user-suppliedO  parameterinC  astprm_64 è .Á[Ú¦—OÅRequired PrivilegesCO4Thecaller musthavethe CMKRNL privilegeto call6O�SYS$CPU_TRANSITIONtomodifyCPUstates.E\ÚœOƒRelatedServicesD]ÚœOƒ$CPU_TRANSITIONWO^ÚÞ%%OÅ ConditionValuesReturnedÑ_! • §Oã SS$_NORMAL/3ãTheservice completed successfullyO] SS$_BADPARAM43]Oneofmore argumentshasaninvalid53ªvalueorthe specifiedCPUisnotin3÷the configurationOq SS$_ACCVIO63qTheservicecannotaccessthe locations13¿ specifiedbyoneormore argumentsO8 SS$_NOCMKRNL138CallerdoesnothaveCMKRNLprivi-/3†legeneededtocomplete operationO SS$_INSFARG,3Fewerthantherequirednumber03Mof argumentswere specifiedorno#3› operationwas specifiedCOSS$_TOO_MANY_ARGSÏMore argumentswere specifiedthan(3bareallowedbytheserviceOÜ SS$_INVCOMPID43ÜThetargetgNodeIDisnotvalidin3)this configurationO£ SS$_CPUNOTACT53£The specifiedCPUisnotpartofthe,3ðcurrent partitions'sactivesetOj SS$_NOSUCHCPU83jThe specifiedCPUdoesnotexistinthe/3¸currenthardwareconfiguration,or:3isnotinthe configuresetofthelocal3S partitionOÌ SS$_CPUSTARTD33ÌThe specifiedCPUisalreadyinthe;3 localactiveset,orisintheprocessof3g joiningitOá SS$_CPUSTOPPING*3á The specifiedCPUisalready.3/ STOPPEDorinthe processingof#3| leavingtheactiveset*` *tsu®a Є OÐ16.2C$CPU_TRANSITIONWNOUOnAlphasystems,changesthecurrent processingstateofaNO­CPUinthe configuresetoran unassignedCPUinaGalaxyMOconfiguration.(Thisservice completessynchronously;thatis,SO^itreturnstothecalleronlyafterthefinal completionstatus(O·ofthe operationisknown.'bÚ¦ýHOƒInallother respects,$CPU_TRANSITIONWis identicaltoDOÜ$CPU_TRANSITION.Forallother informationabouttheEO5$CPU_TRANSITIONWservice,refertothe descriptionof,O�$CPU_TRANSITIONinthismanual.^cÚœ44OƒThisserviceaccepts64-bit addresses.*d³eÚ¦‰OÅFormat;O4SYS$CPU_TRANSITIONWtran_id,cpu_id, nodename,>O�node_id,flags,efn,iosb, astadr_64, astprm_64 åutv¡fÜw5O 17.5 Configuration# Management# ProgrammingOr Interfaces.O÷ Tobe supplied:' Additionalinfo.*g ’vuw´hÚÆŠOÐ17.1C SYS$GETSYIAOUSYI$_GALAXY_PLATFORMreturns1ifyouarerunning/O­onaGalaxy platform,0ifnot.¤i! õzEOƒSYI$_GALAXY_MEMBERreturns1ifyouareamemberof5OÜaGalaxysharing community,0ifnot.fjÚœ<Y< /PFN=FREEvalidatePFNdbforeachpageintheY”freelistBYí/PFN=BADvalidatePFNdbforeachpageinthebadYElist=Yž /PFN=UNTESTEDvalidatePFNdbforeachpageinY÷theuntestedlist=YO/PFN=ALLvalidatePFNdbforeachpageintheY¨PMAP3Y /PFN=(x,y)tovalidatemultiplelistsWu -EÔbIf/PFNisgivenwithout/ALL,/IDENT,or /ADDRESS,CÔ»thenPFNlistsfromthelastSHM_CPPaccessedareÔ validated.L`“3.:AddedSHOWSHM_REG.DefaultisabriefdisplayofallEÔë SHM_REGs,withthe following parameteror qualifiers:‚vÚJX*YÐ/ALLdetaileddisplayofall.Y(/IDENT=ndetaileddisplayofone0Y� /ADDRESS=xdetaileddisplayofone*YÚnamedetaileddisplayofone:`Y4.:Added/GLXSYSand/GLXGRPtoSHOWGSD.D`Ø5.:AddedSHOWGMDBtodisplaythecontentsofthe(Ô1GMDBandallNODEBblocks. syxzYwÚ%//O 19.2OpenVMS!Galaxy"Device!Drivers Özy{¼x! 2’,OÐ19.1CDirectDMAWindowChangesMOUTherearechangesplannedfortheusageoftheDirectDMAGO­windowforPCIdriversstartinginOpenVMSAlpha7.2.LOThesechangeswererequiredtosupporttheGalaxySoftwareEO^ architectureonOpenVMSandmemoryholes.)ThechangeHO·involvesmovingtheDirectDMAwindowawayfromphysi-LOcalmemorylocation0.'ThisdocumentshouldprovideenoughKOh backgroundand informationforyoutoupdateyourdriver.LOÁNotethatthisdocumentdoesn'ttalkaboutbus addressableOpool(BAP). m{z|ky– »AFOÐ19.2CHowPCIDirectDMAWorksPriortoOpenVMSV7.2JOUOnallPCIbased machines,thedirectDMAwindowbeginsLO­at (usually)1GbinPCIspace,andcoversphysicalmemory'O beginningat0for1Gb:O‹ Memory: ”‹ PCITÓ __________-\š 0•|¤ |J\ $ | O | Tc |¤c |p\ $c | Oc | T« |¤« |•\ $« | O« | Tò |F¤ò |º\----------------%|------%|1Gb&(IOC$K_DIRECT_DMA_BASE)š: 1GbJ|-------%|-\ $: |O: |p\ T‚ |¤‚ |J\ $‚ |O‚ |–\ TÊ |¤Ê |p\ $Ê |"OÊ |àIOC$K_DIRECT_DMA_SIZE¿ .p|¤ |•\ $ |O |–/äZ .J|.¤Z |º\----------------%|_______|2Gb-1 ¢ .èz `¾MOƒ Typicallydriverscomparetheirbuffer addressesagainsttheMOÜlengthofthewindowreturnedbycalling ioc$node_datawithJO5theioc$k_direct_dma_sizefunctioncode.(ThisassumesthatNO�thewindowonthememorysidestartsatzero.(Anotherpop-FOæularmethodfor determiningwhethermap registersareJO> necessaryinvolveslookingatmmg$gl_maxpfn.)ThisisalsoKO—notlikelytowork correctlyinOpenVMSVersion 7.2-EFT3. Ô 9ÿForamuchbetterpictureand explanation a Ô Seethe9ï  WritingOpenVMSDeviceAlphaDriversinCÔùbook. ÔD— ‹|{}�{L :WGOÐ19.3CHowPCIDirectDMAWorksinOpenVMSVersion7.2LOUGalaxyandmemoryholeconsiderationsforceustopossibly?O­changethe placementoftheDirectDMAwindow.O2 Memory: ”2 PCI Tz | ¤z | T | ¤Â | T  | ¤  |#OR IOC$K_DIRECT_DMA_BASE_PA:Tš __________-\ Tâ |¤â |J\ $â | Oâ | T* |¤* |p\ $* | O* | Tr |¤r |•\ $r | Or | Tº |C¤º |º\----------------%|------%|1Gb&(IOC$K_DDMA_BASE_BA)T |-------%|-\ $ |O |p\ TJ |¤J |J\ $J |OJ |–\ T’ |¤’ |p\ $’ | O’ |àIOC$K_DDMA_WIN_SIZE TÚ |¤Ú |•\ $Ú |OÚ |–/ T! |.¤! |º\----------------%|_______|2Gb-1ð|! ¹ÆMOƒItisunknownfromthedrivers perspectivewhereinmemoryJOÜthebaseoftheDirectDMAwindowwillbe.+Simplycom-KO5paringabufferaddressagainstthelengthofthewindowTO�willnolongerbe sufficientto determineifabufferiswithinGOætheDirectDMAwindow.(Also, comparingagainstmmg$gl_SO>maxpfnwillnolonger guaranteethatallofpooliswithintheFO—window.+Thecorrectcelltocheckismmg$gl_max_node_NOïpfn.' Additionally, alignmentconcernsmayrequireanslightlyKOH differentoffsetbe incorporatedintophysicalbusaddressO  calculations. °}|o}! wE=OÐ19.4C IOC$NODE_DATAChangestoSupportNon-zero'(DirectDMAWindowsPO­To alleviatethisproblem,newfunctioncodeshavebeenaddedROtoioc$node_data.+HereisalistofallthecodesrelatingtoHO^directDMA,anda descriptionofwhatthedatameans.(~ óþOãIOC$K_DIRECT_DMA_O0BASE43ãThisisthebaseaddressonthePCI630side,orbusaddress.#Thereisasyn-13~onymforthisfunctioncodecalled3ËIOC$K_DDMA_BASE_BA.COEIOC$DIRECT_DMA_SIZE¯On non-Galaxy machines,thisre-03’turnsthesizeofthedirectDMA13àwindow(in megabytes).#Onasystem/3-wherethedirectDMAwindowdoes43{notstartatzero,thedatareturned.3Èiszero,implyingnodirectDMA3windowsexist.KO�IOC$K_DDMA_WIN_SIZE”Onallsystems(asofx6jh)thiswill43Ýalwaysreturnthesizeofthedirect'3+DMAwindow(in megabytes).O¤IOC$K_DIRECT_DMA_OòBASE_PA43¤Thisisthebasephysicaladdressin33òmemoryofthedirectDMAwindow.!It53?isprobablycloselyrelatedtommg$gl_/3� min_node_pfn,butmaybeslightly23Ú differentdueto alignment concerns.*Õ€öW«>OƒTheaddressreturnedwiththeIOC$K_DIRECT_DMA_LOÜBASE_PAcodeis necessarytocomputethe offset.(Thisusu-LO5allyusedtobethe1Gb differencebetweenthememoryPAQO�andthebus address).Theoffsetisdefinedasthesigneddif-KOæferencebetweenthebasebusaddressandthebasememory9O>address.'Thisisnownot necessarily1Gb.     !!!!!!!!!!"""##########$$%%%%%%%%%%&&&&&'''''''(((((((())*+,,,,,,,,,,,,,,,,,,,,,,,---------------------..///000000001111111111111111123333333333333333344456666666666666677777777777777777777788999::::::::;;;;;;;;;;;;;;;;;<==================>>>?@@@@@@@@@@@@@@@@AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAABBBBBBBBBBBCDDDDDDDDDEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEFFFFFFFFFFFFFFFFGGGGGGGGGGGGHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHIIJKKKKKKKKKKKKKKKKKLLLLMNOPPPQQQQQQQRSSSSTTTTTTTTTTUUVVVWWWWWWWWWWWWXXXXXXXXXXXYZ[[[[[\\\\\]]]]^_`````aaaaaabbbbbcccccdddddeeeeefffffggggghhhhhhhhhhhiiiiijklllllllllllllllllllllllllllllllllllllllllllllmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmnooooppppppppqqqqqqqqqqqqqqqqqqqrssssssssssssssssssssssssssssssssssssssssssssssstttttuuvvvvvvvwwxxxxxxyz{{||}}}} þ}PrefacePrefacePrefacePrefacePrefacePrefacePrefacePrefacePrefacePrefacePrefacePrefacePrefacePrefacePrefacePrefacePreface21. OpenVMS Galaxy Version 7.2 Release Notes/1.1 Informational Message During Booting]1.2 Permanent Restriction on KFMSB and CIXCD Adapters in OpenVMS Galaxy Configurations]1.2 Permanent Restriction on KFMSB and CIXCD Adapters in OpenVMS Galaxy ConfigurationsW1.3 Compatibility of Galaxy Computing Environment and Non-Galaxy Cluster MembersW1.3 Compatibility of Galaxy Computing Environment and Non-Galaxy Cluster MembersW1.3 Compatibility of Galaxy Computing Environment and Non-Galaxy Cluster MembersW1.3 Compatibility of Galaxy Computing Environment and Non-Galaxy Cluster MembersW1.3 Compatibility of Galaxy Computing Environment and Non-Galaxy Cluster MembersW1.3 Compatibility of Galaxy Computing Environment and Non-Galaxy Cluster MembersW1.3 Compatibility of Galaxy Computing Environment and Non-Galaxy Cluster MembersW1.3 Compatibility of Galaxy Computing Environment and Non-Galaxy Cluster MembersW1.3 Compatibility of Galaxy Computing Environment and Non-Galaxy Cluster MembersW1.3 Compatibility of Galaxy Computing Environment and Non-Galaxy Cluster MembersW1.3 Compatibility of Galaxy Computing Environment and Non-Galaxy Cluster MembersW1.3 Compatibility of Galaxy Computing Environment and Non-Galaxy Cluster MembersW1.3 Compatibility of Galaxy Computing Environment and Non-Galaxy Cluster MembersX1.4 Possible Problem Upgrading Firmware on AlphaServer 4100 Systems for V7.2-EFT3X1.4 Possible Problem Upgrading Firmware on AlphaServer 4100 Systems for V7.2-EFT3X1.4 Possible Problem Upgrading Firmware on AlphaServer 4100 Systems for V7.2-EFT3X1.4 Possible Problem Upgrading Firmware on AlphaServer 4100 Systems for V7.2-EFT3X1.4 Possible Problem Upgrading Firmware on AlphaServer 4100 Systems for V7.2-EFT3X1.4 Possible Problem Upgrading Firmware on AlphaServer 4100 Systems for V7.2-EFT3IPart I Introduction to the Galaxy Software Architecture on OpenVMS!2. OpenVMS Galaxy Overview@2.1 A New Computing Model and a New Software Architecture@2.1 A New Computing Model and a New Software Architecture@2.1 A New Computing Model and a New Software Architecture62.2 The Galaxy Software Architecture on OpenVMS62.2 The Galaxy Software Architecture on OpenVMS12.3 OpenVMS Galaxy Components and Concepts12.3 OpenVMS Galaxy Components and Concepts12.3 OpenVMS Galaxy Components and Concepts12.3 OpenVMS Galaxy Components and Concepts12.3 OpenVMS Galaxy Components and Concepts12.3 OpenVMS Galaxy Components and Concepts12.3 OpenVMS Galaxy Components and Concepts12.3 OpenVMS Galaxy Components and Concepts12.3 OpenVMS Galaxy Components and Concepts12.3 OpenVMS Galaxy Components and Concepts12.3 OpenVMS Galaxy Components and Concepts2.3.1 APMP Concepts2.3.1 APMP Concepts2.3.1 APMP Concepts2.3.1 APMP Concepts%2.3.2 Another Possible Picture%2.3.2 Another Possible Picture%2.3.2 Another Possible Picture"2.4 OpenVMS Galaxy Features"2.4 OpenVMS Galaxy Features"2.4 OpenVMS Galaxy Features"2.4 OpenVMS Galaxy Features"2.4 OpenVMS Galaxy Features"2.4 OpenVMS Galaxy Features"2.4 OpenVMS Galaxy Features"2.4 OpenVMS Galaxy Features"2.5 OpenVMS Galaxy Benefits"2.5 OpenVMS Galaxy Benefits"2.5 OpenVMS Galaxy Benefits"2.5 OpenVMS Galaxy Benefits"2.5 OpenVMS Galaxy Benefits"2.5 OpenVMS Galaxy Benefits"2.5 OpenVMS Galaxy Benefits"2.5 OpenVMS Galaxy Benefits"2.5 OpenVMS Galaxy Benefits"2.5 OpenVMS Galaxy Benefits"2.5 OpenVMS Galaxy Benefits"2.5 OpenVMS Galaxy Benefits"2.5 OpenVMS Galaxy Benefits"2.5 OpenVMS Galaxy Benefits"2.5 OpenVMS Galaxy Benefits.2.6 OpenVMS Galaxy Version 1.0 Features.2.6 OpenVMS Galaxy Version 1.0 Features'3. OpenVMS Galaxy Configurations(3.1 Is an OpenVMS Galaxy for You?(3.1 Is an OpenVMS Galaxy for You?(3.1 Is an OpenVMS Galaxy for You?(3.1 Is an OpenVMS Galaxy for You?33.1.1 Why a Galaxy is a Good Business Choice33.1.1 Why a Galaxy is a Good Business Choice33.1.1 Why a Galaxy is a Good Business Choice>3.1.2 Things to Consider If You Want to Create a Galaxy>3.1.2 Things to Consider If You Want to Create a Galaxy>3.1.2 Things to Consider If You Want to Create a Galaxy>3.1.2 Things to Consider If You Want to Create a Galaxy>3.1.2 Things to Consider If You Want to Create a Galaxy>3.1.2 Things to Consider If You Want to Create a Galaxy>3.1.2 Things to Consider If You Want to Create a Galaxy13.2 Possible OpenVMS Galaxy Configurations13.2 Possible OpenVMS Galaxy Configurations13.2 Possible OpenVMS Galaxy Configurations13.2 Possible OpenVMS Galaxy Configurations13.2 Possible OpenVMS Galaxy Configurations13.2 Possible OpenVMS Galaxy Configurations+3.2.1 Shared-Nothing Computing Model+3.2.1 Shared-Nothing Computing Model+3.2.2 Shared-Partial Computing Model.3.2.3 Shared-Everything Computing Model(3.3 Important Cluster Information(3.3 Important Cluster Information&3.4 SCSI Cluster Considerations&3.4 SCSI Cluster Considerations&3.4 SCSI Cluster Considerations&3.4 SCSI Cluster Considerations&3.4 SCSI Cluster Considerations&3.4 SCSI Cluster Considerations&3.4 SCSI Cluster Considerations&3.4 SCSI Cluster Considerations&3.4 SCSI Cluster Considerations&3.4 SCSI Cluster ConsiderationsM3.5 Security Considerations in an OpenVMS Galaxy Computing EnvironmentM3.5 Security Considerations in an OpenVMS Galaxy Computing EnvironmentM3.5 Security Considerations in an OpenVMS Galaxy Computing EnvironmentN3.6 Important Info That Needs to be Located in the Appropriate Chapters!3.6.1 New SYSGEN parameter!3.6.1 New SYSGEN parameter!3.6.1 New SYSGEN parameter!3.6.1 New SYSGEN parameter3.6.2 System Auto-Action3.6.2 System Auto-Action3.6.2 System Auto-Action33.6.3 Changing console environment variables3.6.4 CONFIGURE GALAXY.4. OpenVMS Galaxy Licensing Information.4. OpenVMS Galaxy Licensing Information04.1 OpenVMS Galaxy Licensing Requirements04.1 OpenVMS Galaxy Licensing Requirements04.1 OpenVMS Galaxy Licensing Requirements04.1 OpenVMS Galaxy Licensing Requirements-4.1.1 OpenVMS Operating System License-4.1.1 OpenVMS Operating System License#4.1.2 OpenVMS Galaxy License#4.1.2 OpenVMS Galaxy License-4.1.3 OpenVMS Layered Products License-4.1.3 OpenVMS Layered Products License.4.2 Clustering OpenVMS Galaxy Instances*4.2.1 Clustering in a Galaxy System*4.2.1 Clustering in a Galaxy System/4.2.2 Clustering Outside a Galaxy System/4.2.2 Clustering Outside a Galaxy System4.3 License Databases4.3 License Databases4.3 License Databases4.3 License Databases4.3 License Databases4.3 License Databases4.3 License Databases.4.4 OpenVMS Galaxy License PAKs and LMF.4.4 OpenVMS Galaxy License PAKs and LMF.4.4 OpenVMS Galaxy License PAKs and LMF.4.4 OpenVMS Galaxy License PAKs and LMF.4.4 OpenVMS Galaxy License PAKs and LMF.4.4 OpenVMS Galaxy License PAKs and LMF.4.4 OpenVMS Galaxy License PAKs and LMF.4.4 OpenVMS Galaxy License PAKs and LMF74.5 For More Information About OpenVMS Licensing74.5 For More Information About OpenVMS Licensing5Part II Creating an OpenVMS Galaxy Environment;5. Creating an OpenVMS Galaxy on an AlphaServer 8400M5.1 Step 1: Choose a Configuration and Determine Hardware RequirementsM5.1 Step 1: Choose a Configuration and Determine Hardware RequirementsM5.1 Step 1: Choose a Configuration and Determine Hardware RequirementsM5.1 Step 1: Choose a Configuration and Determine Hardware RequirementsM5.1 Step 1: Choose a Configuration and Determine Hardware RequirementsM5.1 Step 1: Choose a Configuration and Determine Hardware RequirementsM5.1 Step 1: Choose a Configuration and Determine Hardware RequirementsM5.1 Step 1: Choose a Configuration and Determine Hardware RequirementsM5.1 Step 1: Choose a Configuration and Determine Hardware RequirementsM5.1 Step 1: Choose a Configuration and Determine Hardware RequirementsM5.1 Step 1: Choose a Configuration and Determine Hardware RequirementsM5.1 Step 1: Choose a Configuration and Determine Hardware RequirementsM5.1 Step 1: Choose a Configuration and Determine Hardware Requirements45.1.1 Using the OpenVMS Configuration Utility45.1.1 Using the OpenVMS Configuration Utility45.1.1 Using the OpenVMS Configuration Utility45.1.1 Using the OpenVMS Configuration Utility45.1.1 Using the OpenVMS Configuration Utility45.1.1 Using the OpenVMS Configuration Utility45.1.1 Using the OpenVMS Configuration Utility45.1.1 Using the OpenVMS Configuration Utility45.1.1 Using the OpenVMS Configuration Utility/5.1.2 OpenVMS Galculator Display Example)5.2 Step 2: Set Up Galaxy Hardware?5.2.1 Installing the KFE72-DA Console Subsystem Hardware?5.2.1 Installing the KFE72-DA Console Subsystem Hardware?5.2.1 Installing the KFE72-DA Console Subsystem Hardware?5.2.1 Installing the KFE72-DA Console Subsystem Hardware?5.2.1 Installing the KFE72-DA Console Subsystem Hardware$5.2.2 Using a Terminal Server?5.2.3 Recommendations for Configuring Console Subsystems?5.2.3 Recommendations for Configuring Console Subsystems?5.2.3 Recommendations for Configuring Console Subsystems?5.2.3 Recommendations for Configuring Console Subsystems?5.2.3 Recommendations for Configuring Console Subsystems?5.2.3 Recommendations for Configuring Console Subsystems?5.2.3 Recommendations for Configuring Console Subsystems$5.2.4 Installing EISA Devices$5.2.4 Installing EISA Devices$5.2.4 Installing EISA Devices$5.2.4 Installing EISA Devices$5.2.4 Installing EISA Devices$5.2.4 Installing EISA Devices$5.2.4 Installing EISA Devices'5.3 Step 3: Create A System Disk'5.3 Step 3: Create A System Disk45.4 Step 4: Install OpenVMS Alpha Version 7.245.4 Step 4: Install OpenVMS Alpha Version 7.215.4.1 OpenVMS Galaxy Licensing Information'5.5 Step 5: Upgrade the Firmware'5.5 Step 5: Upgrade the Firmware'5.5 Step 5: Upgrade the Firmware'5.5 Step 5: Upgrade the Firmware'5.5 Step 5: Upgrade the Firmware'5.5 Step 5: Upgrade the Firmware'5.5 Step 5: Upgrade the Firmware'5.5 Step 5: Upgrade the Firmware,5.6 Step 6: Set Environment Variables,5.6 Step 6: Set Environment Variables,5.6 Step 6: Set Environment Variables,5.6 Step 6: Set Environment Variables,5.6 Step 6: Set Environment Variables,5.6 Step 6: Set Environment Variables,5.6 Step 6: Set Environment Variables,5.6 Step 6: Set Environment Variables,5.6 Step 6: Set Environment Variables,5.6 Step 6: Set Environment Variables,5.6 Step 6: Set Environment Variables,5.6 Step 6: Set Environment Variables,5.6 Step 6: Set Environment Variables,5.6 Step 6: Set Environment Variables,5.6 Step 6: Set Environment Variables15.6.1 Galaxy Environment Variables Example%5.6.2 Table of Useful Integers"Table 5- 1: Useful Integers65.7 Step 7: Start the Secondary Console Devices65.7 Step 7: Start the Secondary Console Devices65.7 Step 7: Start the Secondary Console Devices65.7 Step 7: Start the Secondary Console Devices65.7 Step 7: Start the Secondary Console Devices65.7 Step 7: Start the Secondary Console Devices65.7 Step 7: Start the Secondary Console Devices65.7 Step 7: Start the Secondary Console Devices65.7 Step 7: Start the Secondary Console Devices65.7 Step 7: Start the Secondary Console Devices65.7 Step 7: Start the Secondary Console Devices65.7 Step 7: Start the Secondary Console Devices5.7.1 Console Hints5.7.1 Console Hints5.7.1 Console Hints5.7.1 Console Hints5.7.1 Console Hints*5.8 Step 8: Boot the OpenVMS Galaxy*5.8 Step 8: Boot the OpenVMS Galaxy*5.8 Step 8: Boot the OpenVMS Galaxy;6. Creating an OpenVMS Galaxy on an AlphaServer 8200M6.1 Step 1: Choose a Configuration and Determine Hardware RequirementsM6.1 Step 1: Choose a Configuration and Determine Hardware RequirementsM6.1 Step 1: Choose a Configuration and Determine Hardware RequirementsM6.1 Step 1: Choose a Configuration and Determine Hardware Requirements)6.1.1 Using the OpenVMS Galculator)6.1.1 Using the OpenVMS Galculator)6.1.1 Using the OpenVMS Galculator)6.1.1 Using the OpenVMS Galculator)6.1.1 Using the OpenVMS Galculator)6.1.1 Using the OpenVMS Galculator)6.1.1 Using the OpenVMS Galculator)6.1.1 Using the OpenVMS Galculator)6.1.1 Using the OpenVMS Galculator/6.1.2 OpenVMS Galculator Display Example)6.2 Step 2: Set Up Galaxy Hardware?6.2.1 Installing the KFE72-DA Console Subsystem Hardware?6.2.1 Installing the KFE72-DA Console Subsystem Hardware?6.2.1 Installing the KFE72-DA Console Subsystem Hardware?6.2.1 Installing the KFE72-DA Console Subsystem Hardware?6.2.1 Installing the KFE72-DA Console Subsystem Hardware$6.2.2 Using a Terminal Server?6.2.3 Recommendations for Configuring Console Subsystems?6.2.3 Recommendations for Configuring Console Subsystems?6.2.3 Recommendations for Configuring Console Subsystems?6.2.3 Recommendations for Configuring Console Subsystems?6.2.3 Recommendations for Configuring Console Subsystems?6.2.3 Recommendations for Configuring Console Subsystems?6.2.3 Recommendations for Configuring Console Subsystems$6.2.4 Installing EISA Devices$6.2.4 Installing EISA Devices$6.2.4 Installing EISA Devices$6.2.4 Installing EISA Devices$6.2.4 Installing EISA Devices$6.2.4 Installing EISA Devices$6.2.4 Installing EISA Devices'6.3 Step 3: Create A System Disk'6.3 Step 3: Create A System Disk46.4 Step 4: Install OpenVMS Alpha Version 7.246.4 Step 4: Install OpenVMS Alpha Version 7.216.4.1 OpenVMS Galaxy Licensing Information'6.5 Step 5: Upgrade the Firmware'6.5 Step 5: Upgrade the Firmware'6.5 Step 5: Upgrade the Firmware'6.5 Step 5: Upgrade the Firmware'6.5 Step 5: Upgrade the Firmware'6.5 Step 5: Upgrade the Firmware'6.5 Step 5: Upgrade the Firmware'6.5 Step 5: Upgrade the Firmware,6.6 Step 6: Set Environment Variables,6.6 Step 6: Set Environment Variables,6.6 Step 6: Set Environment Variables,6.6 Step 6: Set Environment Variables,6.6 Step 6: Set Environment Variables,6.6 Step 6: Set Environment Variables,6.6 Step 6: Set Environment Variables,6.6 Step 6: Set Environment Variables,6.6 Step 6: Set Environment Variables,6.6 Step 6: Set Environment Variables,6.6 Step 6: Set Environment Variables,6.6 Step 6: Set Environment Variables,6.6 Step 6: Set Environment Variables,6.6 Step 6: Set Environment Variables,6.6 Step 6: Set Environment Variables16.6.1 Galaxy Environment Variables Example6.6.2 Useful Integers+Table 6- 1: Table of Useful Integers66.7 Step 7: Start the Secondary Console Devices66.7 Step 7: Start the Secondary Console Devices66.7 Step 7: Start the Secondary Console Devices66.7 Step 7: Start the Secondary Console Devices66.7 Step 7: Start the Secondary Console Devices66.7 Step 7: Start the Secondary Console Devices66.7 Step 7: Start the Secondary Console Devices66.7 Step 7: Start the Secondary Console Devices66.7 Step 7: Start the Secondary Console Devices66.7 Step 7: Start the Secondary Console Devices66.7 Step 7: Start the Secondary Console Devices66.7 Step 7: Start the Secondary Console Devices6.7.1 Console Hints6.7.1 Console Hints6.7.1 Console Hints6.7.1 Console Hints6.7.1 Console Hints6.7.1 Console Hints*6.8 Step 8: Boot the OpenVMS Galaxy*6.8 Step 8: Boot the OpenVMS Galaxy*6.8 Step 8: Boot the OpenVMS GalaxyB7. Creating an OpenVMS Galaxy on an AlphaServer 4100 System7.1 Before You Start7.1 Before You Start7.1 Before You Start7.1 Before You Start7.1 Before You Start7.1 Before You Start7.1 Before You Start7.1 Before You Start7.1 Before You Start7.1 Before You Start7.1 Before You Start7.1 Before You Start7.1 Before You Start7.1 Before You Start7.1 Before You Start7.1 Before You Start7.2 Procedures7.2 Procedures7.2 Procedures7.2 Procedures7.2 Procedures7.2 Procedures7.2 Procedures7.2 Procedures7.2 Procedures7.2 Procedures7.2 Procedures7.2 Procedures7.2 Procedures7.2 Procedures7.2 Procedures7.2 Procedures7.2 Procedures7.2 Procedures7.2 Procedures7.2 Procedures7.2 Procedures7.2 Procedures7.2 Procedures7.2 Procedures7.2 Procedures7.2 Procedures7.2 Procedures7.2 Procedures7.2 Procedures7.2 Procedures7.2 Procedures7.2 Procedures<8. Using a Single-Instance Galaxy on Any Alpha System<8. Using a Single-Instance Galaxy on Any Alpha System<8. Using a Single-Instance Galaxy on Any Alpha System<8. Using a Single-Instance Galaxy on Any Alpha System<8. Using a Single-Instance Galaxy on Any Alpha System<8. Using a Single-Instance Galaxy on Any Alpha System<8. Using a Single-Instance Galaxy on Any Alpha System<8. Using a Single-Instance Galaxy on Any Alpha System<8. Using a Single-Instance Galaxy on Any Alpha System<8. Using a Single-Instance Galaxy on Any Alpha System<8. Using a Single-Instance Galaxy on Any Alpha System*Part III Managing An OpenVMS Galaxy.9. OpenVMS Galaxy Configuration Utility.9. OpenVMS Galaxy Configuration Utility.9. OpenVMS Galaxy Configuration Utility.9. OpenVMS Galaxy Configuration Utility.9. OpenVMS Galaxy Configuration Utility.9. OpenVMS Galaxy Configuration Utility.9. OpenVMS Galaxy Configuration Utility.9. OpenVMS Galaxy Configuration Utility.9. OpenVMS Galaxy Configuration Utility9.1 GCU Tour9.1 GCU Tour9.1 GCU Tour9.1 GCU Tour9.1 GCU Tour19.1.1 Creating Galaxy Configuration Models19.1.1 Creating Galaxy Configuration Models19.1.1 Creating Galaxy Configuration Models19.1.1 Creating Galaxy Configuration Models19.1.1 Creating Galaxy Configuration Models19.1.1 Creating Galaxy Configuration Models9.1.2 Observation9.1.2 Observation9.1.2 Observation9.1.2 Observation9.1.2 Observation9.1.2 Observation 9.1.2.1 Layout Management 9.1.2.1 Layout Management 9.1.2.1 Layout Management$9.1.2.2 OpenVMS Galaxy Charts$9.1.2.2 OpenVMS Galaxy Charts$9.1.2.2 OpenVMS Galaxy Charts$9.1.2.2 OpenVMS Galaxy Charts$9.1.2.2 OpenVMS Galaxy Charts$9.1.2.2 OpenVMS Galaxy Charts9.1.3 Interaction9.1.3 Interaction9.1.3 Interaction9.1.3 Interaction29.2 Managing an OpenVMS Galaxy with the GCU29.2 Managing an OpenVMS Galaxy with the GCU29.2 Managing an OpenVMS Galaxy with the GCU29.2 Managing an OpenVMS Galaxy with the GCU29.2 Managing an OpenVMS Galaxy with the GCU"9.2.1 Independent Instances"9.2.1 Independent Instances"9.2.1 Independent Instances"9.2.2 Required PROXY Access"9.2.2 Required PROXY Access"9.2.2 Required PROXY Access"9.2.2 Required PROXY Access"9.2.2 Required PROXY Access"9.2.2 Required PROXY Access"9.2.2 Required PROXY Access"9.2.2 Required PROXY Access&9.3 Galaxy Configuration Models&9.3 Galaxy Configuration Models&9.3 Galaxy Configuration Models&9.3 Galaxy Configuration Models9.3.1 Active Model9.3.2 Offline Models9.3.2 Offline Models19.3.2.1 Example: Creating an Offline Model19.3.2.1 Example: Creating an Offline Model19.3.2.1 Example: Creating an Offline Model19.3.2.1 Example: Creating an Offline Model19.3.2.1 Example: Creating an Offline Model9.4 Using the GCU Charts9.4 Using the GCU Charts9.4 Using the GCU Charts<9.4.1 Component Identification and Display Properties<9.4.1 Component Identification and Display Properties<9.4.1 Component Identification and Display Properties<9.4.1 Component Identification and Display Properties%9.4.2 Physical Structure Chart%9.4.2 Physical Structure Chart%9.4.2 Physical Structure Chart%9.4.2 Physical Structure Chart9.4.2.1 Hardware Root 9.4.2.2 Ownership Overlay 9.4.2.2 Ownership Overlay$9.4.3 Logical Structure Chart$9.4.3 Logical Structure Chart$9.4.3 Logical Structure Chart$9.4.3 Logical Structure Chart9.4.3.1 Software Root#9.4.3.2 Unassigned Resources#9.4.3.2 Unassigned Resources#9.4.3.2 Unassigned Resources#9.4.3.2 Unassigned Resources"9.4.3.3 Community Resources!9.4.3.4 Instance Resources$9.4.4 Memory Assignment Chart$9.4.4 Memory Assignment Chart 9.4.4.1 Console Fragments 9.4.4.2 Private Fragments&9.4.4.3 Shared Memory Fragments!9.4.5 CPU Assignment Chart9.4.5.1 Primary CPU9.4.5.2 Secondary CPUs-9.4.5.3 Fast Path and Affinitized CPUs-9.4.5.3 Fast Path and Affinitized CPUs9.4.5.4 Lost CPUs9.4.5.4 Lost CPUs9.4.5.4 Lost CPUs!9.4.6 IOP Assignment Chart!9.4.6 IOP Assignment Chart"9.4.7 Failover Target Chart"9.4.7 Failover Target Chart"9.4.7 Failover Target Chart"9.4.7 Failover Target Chart"9.4.7 Failover Target Chart"9.4.7 Failover Target Chart"9.4.7 Failover Target Chart'9.5 Viewing Component Parameters'9.5 Viewing Component Parameters'9.6 Executing Component Commands9.7 CPU Reassignment9.7 CPU Reassignment9.7.1 DCL Reassignment9.7.1 DCL Reassignment9.7.1 DCL Reassignment9.7.1 DCL Reassignment+9.7.2 GCU Drag-and-Drop Reassignment$9.7.3 Intermodal Reassignment$9.7.3 Intermodal Reassignment$9.7.3 Intermodal Reassignment$9.7.3 Intermodal Reassignment$9.7.3 Intermodal Reassignment$9.7.3 Intermodal Reassignment89.7.4 Software Reassignment Using Galaxy Services89.7.4 Software Reassignment Using Galaxy Services 9.7.5 Reassignment Faults 9.7.5 Reassignment Faults49.8 Monitoring an OpenVMS Galaxy with DECamds49.8 Monitoring an OpenVMS Galaxy with DECamds49.8 Monitoring an OpenVMS Galaxy with DECamds49.8 Monitoring an OpenVMS Galaxy with DECamds9.9 Creating an Instance"9.10 Dissolving an Instance&9.11 Shutdown and Reboot Cycles(9.12 Online versus Offline Models(9.12 Online versus Offline Models(9.12 Online versus Offline Models*9.13 What's New For The GCU in EFT39.13.1 New DCL commands9.13.1 New DCL commands9.13.1 New DCL commands9.13.1 New DCL commands9.13.1 New DCL commands9.13.1 New DCL commands9.14 GCU System Messages10. DCL Commands10. DCL Commands10. DCL Commands10. DCL Commands10.1 CPU Commands10.1.1 STOP/CPU/MIGRATE10.1.1 STOP/CPU/MIGRATE10.1.1 STOP/CPU/MIGRATE10.1.1 STOP/CPU/MIGRATE10.1.1 STOP/CPU/MIGRATE10.1.1 STOP/CPU/MIGRATE10.1.1 STOP/CPU/MIGRATE10.1.2 SHOW CPU10.1.2 SHOW CPU10.2 SHOW MEMORY10.2 SHOW MEMORY$10.3 Lexical Function Example$10.3 Lexical Function Example$10.3 Lexical Function Example10.4 DUMP10.4 DUMP10.4 DUMP10.4 DUMP10.4 DUMP10.4 DUMP10.4 DUMP10.4 DUMP10.4 DUMP10.4 DUMP10.4 DUMP10.4 DUMP10.5 ANALYZE10.5 ANALYZE10.5 ANALYZE10.5 ANALYZE10.5 ANALYZE10.5 ANALYZE10.5 ANALYZE10.5 ANALYZE10.5 ANALYZE10.5 ANALYZE10.5 ANALYZE10.6 INSTALL411. Shared Memory Cluster Interconnect (SMCI)%11.1 SYS$PBDRIVER Port Devices%11.1 SYS$PBDRIVER Port Devices211.1.1 Multiple Clusters in a Single Galaxy211.1.1 Multiple Clusters in a Single Galaxy211.1.1 Multiple Clusters in a Single Galaxy.11.2 SYSGEN Parameters for SYS$PBDRIVER11.2.1 SMCI_PORTS11.2.1 SMCI_PORTS11.2.2 SMCI_FLAGS11.2.2 SMCI_FLAGS+11.3 LAN Shared Memory Device Driver+11.3 LAN Shared Memory Device Driver+11.3 LAN Shared Memory Device Driver+11.3 LAN Shared Memory Device Driver-12. OpenVMS Galaxy Tips and Techniques8Part IV Developing Programs For An OpenVMS Galaxy)13. Locking Programming Interfaces)13. Locking Programming Interfaces)13. Locking Programming Interfaces)13. Locking Programming Interfaces)13. Locking Programming Interfaces(13.1 SYS$CREATE_GALAXY_LOCK_TABLE(13.1 SYS$CREATE_GALAXY_LOCK_TABLE(13.1 SYS$CREATE_GALAXY_LOCK_TABLE(13.1 SYS$CREATE_GALAXY_LOCK_TABLE(13.1 SYS$CREATE_GALAXY_LOCK_TABLE(13.1 SYS$CREATE_GALAXY_LOCK_TABLE(13.2 SYS$DELETE_GALAXY_LOCK_TABLE(13.2 SYS$DELETE_GALAXY_LOCK_TABLE(13.2 SYS$DELETE_GALAXY_LOCK_TABLE(13.2 SYS$DELETE_GALAXY_LOCK_TABLE(13.2 SYS$DELETE_GALAXY_LOCK_TABLE!13.3 SYS$RESET_GALAXY_LOCK!13.3 SYS$RESET_GALAXY_LOCK!13.3 SYS$RESET_GALAXY_LOCK!13.3 SYS$RESET_GALAXY_LOCK!13.3 SYS$RESET_GALAXY_LOCK"13.4 SYS$CREATE_GALAXY_LOCK"13.4 SYS$CREATE_GALAXY_LOCK"13.4 SYS$CREATE_GALAXY_LOCK"13.4 SYS$CREATE_GALAXY_LOCK"13.4 SYS$CREATE_GALAXY_LOCK"13.5 SYS$DELETE_GALAXY_LOCK"13.5 SYS$DELETE_GALAXY_LOCK"13.5 SYS$DELETE_GALAXY_LOCK"13.5 SYS$DELETE_GALAXY_LOCK"13.5 SYS$DELETE_GALAXY_LOCK$13.6 SYS$GET_GALAXY_LOCK_INFO$13.6 SYS$GET_GALAXY_LOCK_INFO$13.6 SYS$GET_GALAXY_LOCK_INFO$13.6 SYS$GET_GALAXY_LOCK_INFO$13.6 SYS$GET_GALAXY_LOCK_INFO$13.7 SYS$GET_GALAXY_LOCK_SIZE$13.7 SYS$GET_GALAXY_LOCK_SIZE$13.7 SYS$GET_GALAXY_LOCK_SIZE$13.7 SYS$GET_GALAXY_LOCK_SIZE$13.7 SYS$GET_GALAXY_LOCK_SIZE#13.8 SYS$ACQUIRE_GALAXY_LOCK#13.8 SYS$ACQUIRE_GALAXY_LOCK#13.8 SYS$ACQUIRE_GALAXY_LOCK#13.8 SYS$ACQUIRE_GALAXY_LOCK#13.8 SYS$ACQUIRE_GALAXY_LOCK#13.8 SYS$ACQUIRE_GALAXY_LOCK#13.8 SYS$ACQUIRE_GALAXY_LOCK#13.8 SYS$ACQUIRE_GALAXY_LOCK#13.8 SYS$ACQUIRE_GALAXY_LOCK#13.8 SYS$ACQUIRE_GALAXY_LOCK#13.8 SYS$ACQUIRE_GALAXY_LOCK#13.9 SYS$RELEASE_GALAXY_LOCK#13.9 SYS$RELEASE_GALAXY_LOCK#13.9 SYS$RELEASE_GALAXY_LOCK#13.9 SYS$RELEASE_GALAXY_LOCK#13.9 SYS$RELEASE_GALAXY_LOCK#13.10 Locking Error Messages/14. System Events Programming Interfaces14.1 $SET_SYSTEM_EVENT14.1 $SET_SYSTEM_EVENT14.1 $SET_SYSTEM_EVENT14.1 $SET_SYSTEM_EVENT14.1 $SET_SYSTEM_EVENT14.1 $SET_SYSTEM_EVENT14.1 $SET_SYSTEM_EVENT14.1 $SET_SYSTEM_EVENT14.1 $SET_SYSTEM_EVENT14.1 $SET_SYSTEM_EVENT14.1 $SET_SYSTEM_EVENT14.1 $SET_SYSTEM_EVENT14.1 $SET_SYSTEM_EVENT14.1 $SET_SYSTEM_EVENT14.1 $SET_SYSTEM_EVENT14.1 $SET_SYSTEM_EVENT14.1 $SET_SYSTEM_EVENT14.1 $SET_SYSTEM_EVENT14.1 $SET_SYSTEM_EVENT14.1 $SET_SYSTEM_EVENT14.1 $SET_SYSTEM_EVENT14.1 $SET_SYSTEM_EVENT14.1 $SET_SYSTEM_EVENT14.1 $SET_SYSTEM_EVENT14.1 $SET_SYSTEM_EVENT14.1 $SET_SYSTEM_EVENT14.1 $SET_SYSTEM_EVENT14.1 $SET_SYSTEM_EVENT14.1 $SET_SYSTEM_EVENT14.1 $SET_SYSTEM_EVENT14.1 $SET_SYSTEM_EVENT14.1 $SET_SYSTEM_EVENT14.1 $SET_SYSTEM_EVENT14.1 $SET_SYSTEM_EVENT14.1 $SET_SYSTEM_EVENT14.1 $SET_SYSTEM_EVENT14.1 $SET_SYSTEM_EVENT14.1 $SET_SYSTEM_EVENT14.1 $SET_SYSTEM_EVENT14.1 $SET_SYSTEM_EVENT14.1 $SET_SYSTEM_EVENT14.1 $SET_SYSTEM_EVENT14.1 $SET_SYSTEM_EVENT14.1 $SET_SYSTEM_EVENT14.1 $SET_SYSTEM_EVENT14.2 $CLEAR_SYSTEM_EVENT14.2 $CLEAR_SYSTEM_EVENT14.2 $CLEAR_SYSTEM_EVENT14.2 $CLEAR_SYSTEM_EVENT14.2 $CLEAR_SYSTEM_EVENT14.2 $CLEAR_SYSTEM_EVENT14.2 $CLEAR_SYSTEM_EVENT14.2 $CLEAR_SYSTEM_EVENT14.2 $CLEAR_SYSTEM_EVENT14.2 $CLEAR_SYSTEM_EVENT14.2 $CLEAR_SYSTEM_EVENT14.2 $CLEAR_SYSTEM_EVENT14.2 $CLEAR_SYSTEM_EVENT14.2 $CLEAR_SYSTEM_EVENT14.2 $CLEAR_SYSTEM_EVENT14.2 $CLEAR_SYSTEM_EVENT14.2 $CLEAR_SYSTEM_EVENT14.2 $CLEAR_SYSTEM_EVENT14.2 $CLEAR_SYSTEM_EVENT14.2 $CLEAR_SYSTEM_EVENT14.2 $CLEAR_SYSTEM_EVENT14.2 $CLEAR_SYSTEM_EVENT14.2 $CLEAR_SYSTEM_EVENT14.2 $CLEAR_SYSTEM_EVENT14.2 $CLEAR_SYSTEM_EVENT14.2 $CLEAR_SYSTEM_EVENT14.2 $CLEAR_SYSTEM_EVENT14.2 $CLEAR_SYSTEM_EVENT14.2 $CLEAR_SYSTEM_EVENT14.2 $CLEAR_SYSTEM_EVENT14.2 $CLEAR_SYSTEM_EVENT/15. Shared Memory Programming Interfaces15.1 Using Shared Memory15.1 Using Shared Memory15.1 Using Shared Memory15.1 Using Shared Memory15.2 System Services15.2.1 Enhanced Services15.2.1 Enhanced Services15.2.1 Enhanced Services15.2.1 Enhanced Services315.2.2 New Section Flag SEC$M_READ_ONLY_SHPT315.2.2 New Section Flag SEC$M_READ_ONLY_SHPT315.2.2 New Section Flag SEC$M_READ_ONLY_SHPT&15.3 Galaxywide Global Sections&15.3 Galaxywide Global Sections&15.3 Galaxywide Global Sections&15.3 Galaxywide Global Sections&15.3 Galaxywide Global Sections&15.3 Galaxywide Global Sections&15.3 Galaxywide Global Sections&15.3 Galaxywide Global Sections&15.3 Galaxywide Global Sections&15.3 Galaxywide Global Sections&15.3 Galaxywide Global Sections&15.3 Galaxywide Global Sections&15.3 Galaxywide Global Sections&15.3 Galaxywide Global Sections&15.3 Galaxywide Global Sections&15.3 Galaxywide Global Sections&15.3 Galaxywide Global Sections&15.3 Galaxywide Global Sections&15.3 Galaxywide Global Sections016. CPU Management Programming Interfaces16.1 SYS$CPU_TRANSITION16.1 SYS$CPU_TRANSITION16.1 SYS$CPU_TRANSITION16.1 SYS$CPU_TRANSITION16.1 SYS$CPU_TRANSITION16.1 SYS$CPU_TRANSITION16.1 SYS$CPU_TRANSITION16.1 SYS$CPU_TRANSITION16.1 SYS$CPU_TRANSITION16.1 SYS$CPU_TRANSITION16.1 SYS$CPU_TRANSITION16.1 SYS$CPU_TRANSITION16.1 S¾f“ “ YS$CPU_TRANSITION16.1 SYS$CPU_TRANSITION16.1 SYS$CPU_TRANSITION16.1 SYS$CPU_TRANSITION16.1 SYS$CPU_TRANSITION16.1 SYS$CPU_TRANSITION16.1 SYS$CPU_TRANSITION16.1 SYS$CPU_TRANSITION16.1 SYS$CPU_TRANSITION16.1 SYS$CPU_TRANSITION16.1 SYS$CPU_TRANSITION16.1 SYS$CPU_TRANSITION16.1 SYS$CPU_TRANSITION16.1 SYS$CPU_TRANSITION16.1 SYS$CPU_TRANSITION16.1 SYS$CPU_TRANSITION16.1 SYS$CPU_TRANSITION16.1 SYS$CPU_TRANSITION16.1 SYS$CPU_TRANSITION16.1 SYS$CPU_TRANSITION16.1 SYS$CPU_TRANSITION16.1 SYS$CPU_TRANSITION16.1 SYS$CPU_TRANSITION16.1 SYS$CPU_TRANSITION16.1 SYS$CPU_TRANSITION16.1 SYS$CPU_TRANSITION16.1 SYS$CPU_TRANSITION16.1 SYS$CPU_TRANSITION16.1 SYS$CPU_TRANSITION16.1 SYS$CPU_TRANSITION16.1 SYS$CPU_TRANSITION16.1 SYS$CPU_TRANSITION16.1 SYS$CPU_TRANSITION16.1 SYS$CPU_TRANSITION16.1 SYS$CPU_TRANSITION16.2 $CPU_TRANSITIONW16.2 $CPU_TRANSITIONW16.2 $CPU_TRANSITIONW16.2 $CPU_TRANSITIONW16.2 $CPU_TRANSITIONW:17. Configuration Management Programming Interfaces:17. Configuration Management Programming Interfaces17.1 SYS$GETSYI17.1 SYS$GETSYI17.1 SYS$GETSYI17.1 SYS$GETSYI17.1 SYS$GETSYI17.1 SYS$GETSYI17.1 SYS$GETSYI%18. System Dump Analyzer (SDA)%18. System Dump Analyzer (SDA)618.1 SDA Command Interface Changes or Additions618.1 SDA Command Interface Changes or Additions618.1 SDA Command Interface Changes or Additions618.1 SDA Command Interface Changes or Additions618.1 SDA Command Interface Changes or Additions618.1 SDA Command Interface Changes or Additions(19. OpenVMS Galaxy Device Drivers%19.1 Direct DMA Window Changes:19.2 How PCI Direct DMA Works Prior to OpenVMS V7.2:19.2 How PCI Direct DMA Works Prior to OpenVMS V7.2;19.3 How PCI Direct DMA Works in OpenVMS Version 7.2;19.3 How PCI Direct DMA Works in OpenVMS Version 7.2H19.4 IOC$NODE_DATA Changes to Support Non-zero Direct DMA WindowsH19.4 IOC$NODE_DATA Changes to Support Non-zero Direct DMA WindowsH19.4 IOC$NODE_DATA Changes to Support Non-zero Direct DMA WindowsH19.4 IOC$NODE_DATA Changes to Support Non-zero Direct DMA Windows Rgalaxfront_2rnotes_chapt from_clair!perm_rest#ak_clust+ sysd, sysdd-sysddd. what0rb_11026over_part7galaxy_intro8 new;gsa_ovms=apmp_con? consA shmemC cpusD ioEindep_insHapmp_consJapmp_figMdiagramPxxxvvvQ cluU smpVspu_subWdyn_recXglx_bens\comp_su] avail_ scaleb adapte costf perfgeft3featsiconcepts_chaptjgsa_younwhy_galaxqcreatexconfigurations~ s_n€sn_fig� s_p‚sp_figƒ s_e„se_fig…clust_sat‡glx_scsi‘ak_security”find_a_home• new2™ new3œ new4�newcgconfigž sym_c lmfsym_1¤lmfsym_2¦lmfsym_3¨lmfsym_4ªlmfsym_5«lmfsym_6­lmfsym_7¯lmfsym_8¶lmfsym_9¾install_where_licenseÀcreat_partÁneeds_chaptÂconfigsÃconfig1Éconfigs2Ìconfigs3Ïhw_reqsØgalc_exÙset_upÚgnsym_3ßterm_sà thumbçeisa_devî sydð instò licó fwûgsym_9þgsym_10gsym_11gsym_12gsym_13gsym_14 gsym_15  ee ui_sect useful_ints_tab gsym_1gsym_2gsym_16!8200_needs_chapt"8200_configs#8200config1&8200hw_reqs/8200galc_ex08200set_up18200gnsym_368200term_s78200thumb>8200eisa_devE8200sydG8200instI8200licJ8200fwR8200gsym_9U8200gsym_10X8200gsym_11Y8200gsym_12]8200gsym_13_8200gsym_14`8200gsym_15a8200eeb8200ui_sectc8200_ints_tabd8200gsym_1p8200gsym_2v8200gsym_16yrawhidezhw_rest|ins_4100}4100_fw~ zz€ zz2�cp_4100ƒcpu_4100„ioa_cpu…ioc_4100†nwc_4100ˆmem_4100Š zz3ªbean_chaptµmanage_part¶ gcu¿ gui_5Ä gui_6Ê gui_8Ð gui_9Ógui_10Ùgui_11Ýgcu_new2â gui_2å gui_4ígui_12ñgui_13ògui_14ôgui_15ùgui_16ügui_17gui_18gui_19gui_23agui_24 gui_25 gui_26gui_27gui_28gui_29gui_30gui_31gui_32gui_33gui_34gui_35gui_36gui_37gui_iop!gui_failo(gui_38*gui_39+gui_40-gui_411gui_422gui_438gui_44:gui_46<gui_49@gui_50Agui_51Bgui_52Cgui_53Ffind_homeG new1Mgcu_mssgNsym_acRsym_adSsym_afZsym_ah\sym_aj^lex_dcl_lex_dcl1`lex_dcl2a d_stmanalyz_commxsym_amy smcizpbdriver|mult_clustsysgen_parms€ ports‚smci_flgs„lanshm_1ˆtech_tips‰develop_partŠlocking_api_chapt� sym_g• sym_hš sym_jŸ sym_k¤ sym_l© sym_m® sym_n³ sym_o¾ sym_pÃlck_mssgÄevents_api_chaptÅ sym_rò sym_sshared_mem_api sym_t sym_usym_uaandy_flagggw_sects1cpu_man_api2 sym_x4 frm15 frm2U frm3[ frm4^ frm5a sym_ye frm7fconfig_apihsym_abosym_arqnew_intwglx_drivsxdirect_dmaydma_today{pci_new} ioc é@-ADOBE-Helvetica-Bold-R-Normal--*-180-*-*-P-*-ISO8859-1@-ADOBE-Helvetica-Bold-R-Normal--*-120-*-*-P-*-ISO8859-1O-ADOBE-New Century Schoolbook-Medium-R-Normal--*-120-*-*-P-*-ISO8859-1M-ADOBE-New Century Schoolbook-Bold-R-Normal--*-120-*-*-P-*-ISO8859-1M-ADOBE-New Century Schoolbook-Bold-R-Normal--*-100-*-*-P-*-ISO8859-1O-ADOBE-New Century Schoolbook-Medium-R-Normal--*-100-*-*-P-*-ISO8859-1@-ADOBE-Helvetica-Bold-R-Normal--*-140-*-*-P-*-ISO8859-1O-ADOBE-New Century Schoolbook-Medium-R-Normal--*-140-*-*-P-*-ISO8859-1B-ADOBE-Helvetica-Medium-R-Normal--*-120-*-*-P-*-ISO8859-1M -ADOBE-New Century Schoolbook-Bold-R-Normal--*-140-*-*-P-*-ISO8859-1@ -ADOBE-Courier-Medium-R-Normal--*-120-*-*-M-*-ISO8859-1/ -ADOBE-Symbol-*-R-*--*-140-*-*-P-*-*-*O -ADOBE-New Century Schoolbook-Medium-I-Normal--*-120-*-*-P-*-ISO8859-1O -ADOBE-New Century Schoolbook-Medium-I-Normal--*-140-*-*-P-*-ISO8859-1 à,+-‹ÂÚAaAOÐ5.1BStep1:*Choosea Configurationand Determine ü(Hardware RequirementsŒÃÚMbJOÅQuickSummaryofan AlphaServer8400Galaxy ConfigurationO49slotsfor:�ÄÚšcÔÐI/OmodulesÔ(Memorymodules4Ô� Processormodules(2CPUspermodule)XÅÚœ..OƒConsolelineforeach partition:�ÆÚAc/ÔÐStandardUARTforfirst partition4Ô(KFE72-DAforeach additional partition:ÇÚœOƒ Rules:ÆÈÚšœ5ÔÐMusthaveanI/Omoduleper partition&Ô(Maximumof3I/OmodulesAÔ�MusthaveatleastoneCPUmoduleper partition}ÉÚMS#OÅExample Configuration10O42 partitions,8CPUs,12GBmemoryUÊÚé++ÔÐ9slots allocatedasfollows:œËÚ…rÔ»2I/Omodules0Ô4 Processormodules(2CPUseach))Ôl3Memorymodules(4GBeach)|ÌÚMR#OÅExample Configuration2/O43 partitions,8CPUs,8GBmemoryUÍÚé++ÔÐ9slots allocatedasfollows:œÎÚ…rÔ»3I/Omodules0Ô4 Processormodules(2CPUseach))Ôl2Memorymodules(4GBeach)sÏ VI&Update%KN7C*).t� MISCELLANEOUS%PARTS^tù In%addition%to%the&above&parts,%consider%the% following&parts&to&help%you6tA organize%and&manage%your&Galaxy%system.]tª 1)%A%Terminal-Server%(for%example,% DECserver200%or%900,%etc.)%to%organize\äò your%console&serial%lines.%Having& reverse-LAT&access%to%your&consoles&isä: helpful.It‚ 2)%An%Ethernet%HUB&to&manage%your&Ethernet& connections.atÊ 3)%A%suitable% workstation%for%using%the&OpenVMS%Galaxy& Configuration%Utility.Mt 4)%Refer%to%the&OpenVMS%Galaxy&Guide&for%more& information.š{ MEMORY%MODULES.tä 1%MS7CC-EA%(1GB)%Memory%Modules..tN 1%MS7CC-GA%(4GB)%Memory%Modules.*t· SYSTEM&CAPACITY&AS& SPECIFIED:Jt  1)%There%are&10& processors%of%which%8%can%be% migrated.Gth 2)%There%are&5%I/O&Hoses& available%for%PCI&and%XMI.Pt° 3)%There%are&57&possible&PCI%devices&if&all%hoses%are%used.1t 4)%There%are&2%KFTIA%I/O&modules.]äa Each%contains%2&Ethernet&Ports,%4&SCSI%Ports,&and%1&optional&FDDI%port.Hä© Remember%that%only&the%instance%owning%the&I/O%modules$äñ can&access%these%ports. ™657‹"ÚAaAOÐ6.1BStep1:*Choosea Configurationand Determine ü(Hardware Requirements¡#ÚMwJOÅQuickSummaryofan AlphaServer8200Galaxy Configuration-O4Onlyonepossibleconfiguration.v$ÚhL `Ð ·ÔÐTwo instancesonly `O ·ÔO5slotsfor:±%Úè‡ åÐ ·.YÐTwoCPUmodules(twoCPUseach) åO ·YOTwoI/Omodules åÏ ·YÏOnememorymoduleE&! V0OÐ6.1.1BUsingtheOpenVMS GalculatorJO4TheOpenVMS Galculatorisan applicationprogramyoucanQOŒuseto determinetheGalaxy configurationthatbestsuitsyour(Oåneeds.'Itis availableat:(O=http://www.openvms.digital.com÷'ÿNÍIOƒTocreateanOpenVMSGalaxyVersion7.2 computingenvi-JOÜronmentonan AlphaServer8200,the Galculatorstepsyou:O5throughthe followinghardware requirements:,(â@ `Ð ·EÔÐOneI/Omodule(I/OmoduleoftypeKFTIAorKFTHA)Ô(foreach partition `¨ ·;Ô¨AtleastoneCPUmoduleforeach partition `' ·CÔ'A dedicatedserialconsoleportforeach partitionÎ)Ú,¤BÔbThe AlphaServer8200providesabuilt-inUARTforLÔ»thefirstconsoleline.*Each additionalconsolerequiresaÔmoduleset.ä*õ,ºIÔbTheonlyhardwarerequiredforGalaxy operationthatisJÔ»notinthetypical AlphaServer8200 configurationisthe'ÔKFE72-DAconsole subsystem.+õ¬ÝFÔbTheKFE72-DAmodulesetisthesetofEISA-busmod-4Ô»ulesthat establishtheconsoleport. `: ·FÔ:AdisplaydevicefortheOpenVMSGalaxy ConfigurationÔ“Utility.@,! …CÔbCompaq recommendsanAlphaorVAX workstationrun-AÔ»ning DECwindowsoraWindowsNT workstationwithFÔan Xterminal emulator.(Formore informationaboutthe7ÔlOpenVMSGalaxy ConfigurationUtility,seelChapter9.*,/lO¶�-ÚõeHOƒOpenVMSV7.2 customersmightwanttousethe followingOÜoptional hardware:*.! ™ `Ð ·LÔÐPluginunits(PIU)forI/O expansionfromanI/OmoduleÔ((PCIorXMI) `¨ ·JÔ¨I/Oadaptersfornetwork,storage,or traditionalclusterÔ interconnects `€ ·Ô€ AdditionalCPUsè/ ¾6OÐ6.1.2BOpenVMS GalculatorDisplayExampleDO4The followingisasampledisplayfromtheOpenVMSOŒ Galculator:'O Compaq%Computer% Corporation0tz OpenVMS%Galaxy%System& Configuration&Update%KN7C*).t� MISCELLANEOUS%PARTS^tù In%addition%to%the&above&parts,%consider%the% following&parts&to&help%you6tA organize%and&manage%your&Galaxy%system.]tª 1)%A%Terminal-Server%(for%example,% DECserver200%or%900,%etc.)%to%organize\äò your%console&serial%lines.%Having& reverse-LAT&access%to%your&consoles&isä: helpful.It‚ 2)%An%Ethernet%HUB&to&manage%your&Ethernet& connections.atÊ 3)%A%suitable% workstation%for%using%the&OpenVMS%Galaxy& Configuration%Utility.Mt 4)%Refer%to%the&OpenVMS%Galaxy&Guide&for%more& information.š{ MEMORY%MODULES.tä 1%MS7CC-EA%(1GB)%Memory%Modules..tN 1%MS7CC-GA%(4GB)%Memory%Modules.*t· SYSTEM&CAPACITY&AS& SPECIFIED:Jt  1)%There%are&10& processors%of%which%8%can%be% migrated.Gth 2)%There%are&5%I/O&Hoses& available%for%PCI&and%XMI.Pt° 3)%There%are&57&possible&PCI%devices&if&all%hoses%are%used.0t 4)%There%are&2%KFTIA%I/O&module.]äa Each%contains%2&Ethernet&Ports,%4&SCSI%Ports,&and%1&optional&FDDI%port.Gä© Remember%that%only&the%instance%owning%the&I/O%module$äñ can&access%these%ports. Q4EDF�¿ÚnWOÐ9.1BGCUTour?OUTheGCUcanperformthreetypesof operations:+ÀÚ@ `Ð ·CÔÐCreateofGalaxy configurationmodelsorasingle-Ô(instanceGalaxy. `¨ ·?Ô¨ObserveactiveGalaxy performanceand resources. `' ·CÔ'InteractwithactiveGalaxyresourceconfigurations.RÁ! (GOƒMostGCU operationsare organizedaroundthemainob-HOÜ servationwindowandits hierarchicaldisplayofGalaxyLO5 components.'The observationwindowprovidesaportholeintoKO�averylargespace.*The observationwindowcanbepannedMOæandzoomedasneededtoobservepartortheentireGalaxyQO>configuration.'ThemaintoolbarcontainsasetofbuttonsthatGO—control workspacezoom operations.) WorkspacepanningisPOï controlledbythe horizontalandvertical scrollbars; workspaceLOHslidingisachievedbyholdingdownthemiddlemousebut-LO tondownasyoudragthe workspacearound.(This obviously5Oùassumesyouhavea three-buttonmouse.? KOƒThevariousGCU operationsareinvokedfrompulldownorIOÜpopupmenu functions.)General operationssuchasopeningLO5andclosingfiles,andinvokingexternaltools,areaccom-NO�plishedusingthemainmenubarentries.( OperationsspecificFOæto individualGalaxy componentsare accomplishedusingFO>popupmenusthatappearwheneveryouclicktherightJO—mousebuttonona component displayedinthe observationOïwindow.ÏÃßW¥HOƒInresponsetomany operations,theGCUdisplaysaddi-OOÜtionaldialogboxes containing information,forms,editors,orJO5prompts.*Errorand information responsesare displayedinPO�popupdialogboxesorinsidethestatusbaralongthebottomMOæofthewindow, dependingontheseverityoftheerrorand'O> importanceofthemessage.ðÄÿ¥Æ8OÐ9.1.1BCreatingGalaxy ConfigurationModelsLO4YoucanusetheGCUtocreateGalaxy configurationmodelsBOŒandasingle-instanceGalaxyonanyAlphasystem.CÅ KOƒWhenviewingtheactiveGalaxy configurationmodel,directKOÜ manipulationofdisplayobjects (components)mayaltertheHO5runningconfiguration.(Forexample,draggingaCPUcom-QO�ponentfromitscurrentlocationanddroppingitontopofaJOæ differentinstance componentwillinvokea managementac-MO>tion procedure,that reassignstheselectedCPUtothenewPO— instance.)Atcertaintimesthismaybea desirable operation;LOïhowever,inother situationsyoumightwantto reconfigureJOHyourGalaxyallatonceratherthan componentbycompo-NO nent.)To accomplishthis,youmustcreateanofflineGalaxyOù configurationmodel.öÆìNÌMOƒTocreateaGalaxy configurationmodel,wemuststartwithQOÜanexistingmodel, typicallytheactiveone,alteritinsome.O5manner,andsaveitinafile.nÇÚœDDOƒStartingfromtheactiveGalaxy ConfigurationModel:öÈ! zÌI`Ð1.:PresstheENGAGEbuttonsuchthatthemodelbecomesGÔ( DISENGAGED.Thebuttonshouldturnfromredtowhite,HÔ�andits appearanceshouldbepoppedoutward.'Whendis-FÔÚengaged,allCPU componentsinthedisplaywillturnLÔ2redasan indicationthattheyarenolongerengaged.(DoHÔ‹notpanic,theyhavenotbeen shutdown!)Themodelhas(Ôãsimplybeentaken off-line.L`c2.:AltertheCPU assignmentsbydragginganddroppingin-LÔ»dividualCPUsontopofthe instancesyouwishtoassignÔthemto.K`“3.:When finished,youcaneither re-engagethemodel,orMÔìsavethemodelinafileforlateruse.)Wheneveryoure-EÔDengageamodel, regardlessofwhetherthemodelwasLÔ�derivedfromtheactivemodelorfroma file-basedmodel,EÔõtheGCUwillcomparetheactivesystem configurationMÔNwiththe configurationproposedbythemodel.'ItwillthenCÔ¦provideasummaryof managementactionsthatwouldJÔÿneedtobe performedtoreassignthesystemtothenewLÔWmodel.)Iftheuserapprovesoftheactions,theGCUwillBÔ°commencewith executionoftherequired managementKÔ actionsandthe resultingmodelwillbe displayedasthe&Ôaactiveandengagedmodel.‰É! ÿ_QOƒThereasonforcreatingofflinemodelsistoallow significantMOÜ configurationchangestobe automated.'Forexample,youcanKO5createmodels representingthedesiredGalaxy configurationMO�at differenttimesandthenengagethemodels interactively)Oæby followingthis procedure.™Ê ¯oOÐ9.1.2B ObservationLO4TheGCUcandisplaythesingleactiveGalaxy configurationNOŒmodel,oranynumberofofflineGalaxy configurationmodels.NOåEachloadedmodelappearsasanitemintheModelmenuonMO=thetoolbar.*YoucanswitchbetweenmodelsbyclickingtheO–desiredmenuitem.(Ë ¦þ@OƒTheactivemodelisalwaysnamedGLX$ACTIVE.GCM.UOÜWhentheactivemodelisfirstloaded,afilebythisnamewillNO5existbrieflyasthesystem synchronizesthemodelwiththeO�system hardware.ÌúNòSOƒWhenamodelisvisible,youcanzoom,pan,orslidethedis-LOÜplayasneededtoviewGalaxy components.(UsethebuttonsSO5ontheleftsideofthetoolbartocontrolthezoom functions.RÍÚœ((OƒThezoom functionsinclude:§ÎÚ0}OãGalacticzoom:KãZoomtofittheentire component hierarchy$K0into observationwindow.OªZoom1:12KªZoomtothe componentnormalscale.O$Zoomtoregion:K$Zoomtoaselectedregionofthedisplay.OžZoomin$KžZoominby10percent.OZoomout%KZoomoutby10percent.$Ï ¦úNOƒPanningis accomplishedbyusingtheverticaland horizontalOOÜ scrollbars.)Slidingisdonebypressingandholdingthemid-MO5dlemousebuttonanddragging (sliding)thecursorandtheO�image.3Ð! ó %OÅ9.1.2.1CLayout ManagementHO)The AutomaticLayoutfeaturemanagesthe componentlay-SO�out.'Ifyoueverneedtorefreshthelayoutwhilein AutomaticIOÚLayoutmode,simplyselecttheroot (topmost) component.æÑ ¹¼MOƒToalterthecurrentlayout,selectManualLayoutfromtheEOÜWindowsmenu.+InManualLayoutMode,youcanfreelyJO5draganddrop componentshoweveryouliketogenerateaHO�pleasing structure.-Becauseeach componentisfreefromKOæ automaticlayout constraints,youmayneedtoinvestsomeNO>timein positioningeach component,possiblyoneachoftheQO—charts.'Tomakethingssimpler,youcanclickpresstherightIOïmousebuttononany componentandselectLayoutSubtreeQOHtoprovide automaticlayout assistancebelowthatpointintheO  hierarchy. Ò ¹ßMOƒWhenyouare satisfiedwiththelayout,youmustsavetheNOÜcurrentmodelinafiletoretainthemanuallayoutinfor-MO5mation.)Thecustomlayoutisusedwhenthemodelisopen.NO�NotethatifyouselectAutoLayoutmode,yourmanuallay-QOæoutwillbelostforthe in-memorymodel.*Also,inorderforLO>CPU componentstoreassigninavisually effectivemanner,KO—theymustperformsubtreelayout operationsbelowthein-ROïstancelevel.+Forthisreason,itisbesttolimitanymanualPOHlayout operationstotheinstanceand communitylevelsoftheO  component hierarchy.µÓ š‹*OÅ9.1.2.2COpenVMSGalaxyChartsPO)TheGCUprovidessixdistinctsubsetsofthemodel,knownasO�charts.NÔÚœ$$OƒThesixchartsinclude: ÕÚýâ O• OÝChartname3ÝShows Oø ObLogical Structure(3bDynamicresource assignmentsOÜPhysical Structure.3Ü Nonvolatilehardware relationshipsOVCPU Assignment03V SimplifiedviewofCPU assignmentsOÏMemory Assignment'3ÏMemory subsystem componentsOIIOP Assignment'3II/O processor relationshipsOÃFailoverTargets*3à Processorfailover assignments OÞ áÖíN·POƒThesechartsresultfromenablingor disablingthedisplayofNOÜvarious componenttypestoprovideviewsofsensiblesubsetsO5of components.ä× WºJOƒSpecificchartsmayoffer functionalitythatcanbepro-KOÜvidedonlyforthatcharttype.+Forexample, reassignmentKO5ofCPUsrequiresthattheinstance componentsbevisible.QO�Because instancesarenotvisibleinthePhysical StructureorIOæMemory Assignmentcharts,youcanreassignCPUsonlyin@O>theLogical StructureandCPU Assignmentcharts.|ØÚœR;OƒFormore informationaboutcharts,referto„ƒSection9.4.*Ø„F|?ù®Ù! ¸„OÐ9.1.3B InteractionHO4WhenviewingtheactiveGalaxy configurationmodel,youMOŒcaninteractdirectlywiththesystem components.'Forexam-QOåple,toreassignaCPUfromoneinstancetoanother,youcanJO=draganddropaCPUontothedesired instance.*TheGCUMO–willvalidatethe operationandexecuteanexternalcommandMOîactiontomakethe configurationchange.( InteractingwithaOOGmodelthatisnotengaged,issimplyadrawing operationonOOŸtheofflinemodel,andhasnoimpacttotherunningsystem.Ú! ¹ÝJOƒWhile interactingwithGalaxy components,theGCUappliesMOÜbuilt-inand user-definedrulesthatpreventmisconfigurationIO5andimproper managementactions.'Forexample,youcannotJO�reassignprimaryCPUs,andyoucannotreassignaCPUtoKOæany componentotherthanaGalaxy instance.(Eitheropera-QO>tionwouldresultinanerrormessageonthestatusbar,andRO—themodelwouldreturntoitsproperconfiguration.'Iftheat-POïtempted operationviolatesoneofthe configurationrules,theTOHerrormessage, displayedinredonthestatusbar,willdescribe!O therulethatfired.GÛõ¦NOƒYoucanviewdetailsforanyselected componentbyclickingLOÜtherightmousebuttonandeither selectingthe ParametersKO5itemfromthepopupmenuorby selecting Parametersfrom8O�the Componentsmenuonthemaintoolbar.ƒÜ YKOƒTheGCUcanshutdownorrebootoneormoreGalaxyin-KOÜstancesusingtheShutdownorRebootitemsontheGalaxyHO5menu.*Thevariousshutdownorreboot parameterscanbeNO�enteredintheShutdowndialogbox.*BesuretospecifytheDOæCLUSTER_SHUTDOWNoptiontofullyshutdown clusteredNO>Galaxy instances.(TheShutdowndialogboxallowsyoutose-OO—lectany combinationof instances,orall instances.(TheGCULOïis ``smart''enoughtoshutdownitsownerinstancelast. 'KJLT+! �* OÐ9.7BCPU ReassignmentEOUOpenVMSsupportsseveralmethodsofmanagingCPUre-LO­sources.*Theconsole establishesthedefaultownerinstanceLOforeachCPUusingtheconsole environment variables.(ThisOO^allowstheCPU resourcestobe statically assigned, providingWO·apreciseinitialconfiguration.'Intheeventofacoldboot(thatSOis,powercycleorinitialization),thisdefault configurationis4Ohrestoredfromconsole nonvolatileRAM.0, ¦GOƒOncea configurationhasbeenbooted,OpenVMSprovidesJOÜmoreelegantmeansof assigning resourcesforuserswithHO5CMKRNL(ChangeModetoKernel) privilege.'The following-O�sectionsdescribethesemethods.- *Ü"OÐ9.7.1BDCL ReassignmentFO4UserswithCMKRNL privilegecanperformCPU reassign-@OŒment operationsusingthe followingDCLcommand:4O $&STOP/CPU/MIGRATE=instance-or-idpcpu-idi.Ü ?JOƒTheusermustprovidethetargetinstancename (SCSNAME)QOÜornumericID(0,1,andsoon),andthenumericIDoftheIO5CPUbeing reassigned.)The followingexamplesshowafew#O�formsofthiscommand.FO $&STOP/CPU/MIGRATE=0J4à !Reassign%CPU%4%to%instance%0OOZ $&STOP/CPU/MIGRATE=1J3,4,5K !Reassign%CPUs&3,4,5&to&instance&1NO¢ $&STOP/CPU&7/MIGRATE=BIGBNGK !ReassignCPU%7&to&instance&BIGBNGUOê $&STOP/CPU/ALL/MIGRATE=0» !Reassign%all% secondary&CPUs%to%instance%0Ò/ a¨JOƒThesecommandscanbeinsertedintocommand procedures.JOÜForexample,youmightwanttomoveextraCPU resourcesPO5toaninstanceinastartup procedureofan applicationwithJO�known processing requirements.( Similarly,youmaywanttoMOæreassignCPUsawayfromaninstancethatisabouttoper-MO>formlengthy,I/O intensive operations(suchasbackups)soKO—thattheCPUsare availabletoother instances.+WhentheHOïjob completes,youmayreassignthemback.,OryoumayMOHreassignCPUsawayfromaninstancethatisshuttingdown.m0 CIOƒNotethatyoucanonlyreassign resourcesawayfromanIOÜ instance..ThisisthepushmodeldefinedbytheGalaxyIO5Software Architecture.)Thismodelprevents resourcesfromPO�being ``stolen''byother instancesthatmaynotbeawareofNOætheircurrentusage.'To effectivelymanagetheentireGalaxyQO>systemusingDCL,youmusteitherlogintoeachofthein-LO—volved instancesorusetheSYSMANutilitytoexecutethe-Oïcommandsontheowner instance.Ÿ1 ¸u1OÐ9.7.2BGCU Drag-and-Drop ReassignmentKO4TheGCUprovidesan interactivevisual interfaceforman-IOŒagingGalaxy resources.*UsingtheGCU,youcanreassignEOåCPUsbysimplydragginganddroppingthemamongin-NO=stances.) Additionally,theGCUallowsyoutodrawchartsofKO–variousconfigurations(knownas configurationmodels),andPOîsavethemasfiles.*Atanytime,youcanloadandengageaKOG configurationmodelandthesystemwillreassign resources7OŸasneededtoachievethedesiredmodel. 2Úà)OÐ9.7.3B Intermodal ReassignmentKO4BecauseoftheresourcepushmodeldefinedbytheGalaxyGOŒSoftware Architecture, resourcesmustbegivenawaybyLOåtheGalaxyinstancethat currentlyownsthem.*Forautil-MO=ityoruserto effectivelymanageresource assignmentinaIO–multiple-instanceGalaxyconfiguration,youmust establishCOîsomemeansof executingcommandsoneach instance.ÿ3ÞNÕJOƒOnesuchmeansistoopenawindoworterminalsessionLOÜoneachoftheGalaxy instancesandperformyourresource?O5 management operationsineachofthesewindows.o4 kEJOƒAnothermethodisusetheSYSMANutilityanditsunder-GOÜlying SMI-Serverto establishacommand environmentonNO5theowner instance.(Usingthismethod,afairlysimplecom-LO�mand procedurecanbewrittentoperformspecificresourceHOæ management operations.)Thismethodhassome limitations,PO>however.'Firts,itrequiresthattheinvolvedGalaxy instancesNO—mustbeinacluster.(Also,acommand procedurecannotef-HOï fectivelypassvariable parameterstoSYSMAN environmentJOHscripts,andyoucannotspecifyaremotesystempasswordJO withinaSYSMANscript.*Soitis cumbersometogenerateGOùageneral-purposecommand procedure interfacethatusesORSYSMAN.¦5 k|IOƒTheGCUdoes,infact,useSYSMANwhereverpossibletoIOÜ accomplishits managementactions.*WhenasystemisnotLO5 configuredtosupportSYSMAN,theGCUwillattempttouseDO�DECnet task-to-task comminationsamongproxyaccountsQOæasits management transport.'Ifthatapproachalsofails(thatPO>is,ifthesystemisnotrunningDECnetorifthe necessaryQO—proxyaccountsarenotsetup),theGCUwillnotbeabletoJOïmanageGalaxy instancesotherthantheoneonwhichtheJOHGCUis currentlyrunning.)Youcould certainlyrunmulti-RO plecopiesoftheGCUifyouchoose,oneperGalaxy instance.DOùHowever,youcanassumethatOpenVMSGalaxysystems>ORarelikelytobe clusteredortouseDECnet. 6 °öZOƒTheGCUs managementactionsarebasedintheSYS$MANAGER:GCU$ACTIONS.COMJOÜcommand procedure.)Youcanmodifythisfileto customizeMO5actionsforyourown environment.'Forexample,inaTCP/IPEO� environment,youmaychoosetouseREXECorsimilarHOæutilityforyour management transport,oryoumaywantMO>toincludesomeformof notificationorloggingwhenevera+O— managementactionis executed.7 ç?OƒTheGCU$ACTIONS.COMfileissomewhatunusualinGOÜthewayit operates.*WhenusingSYSMAN,the procedureGO5buildssmallSYSMANcommandscriptsin temporaryfilesDO�todealwithvariable parametersthatSYSMANCannotIOæhandle.)WhenSYSMANisnot available,the procedureat-MO>temptstoopenaDECnet task-to-task connectiontoaproxyMO—accountontheowner instance.,If successful,itusesthisIOï connectiontoshufflecommand parameterstothecopyofCOHGCU$ACTIONS.COMthatresidesontheowner instance.MO Theendresultis executionofthecommandlocallybytheOùowner instance.©8 ¸@OÐ9.7.4BSoftware ReassignmentUsingGalaxyServicesIO4Perhapsthebestmethodformanagingresource assignmentNOŒistousetheGalaxyAPIstowriteyourownresourceman-OOåagement routines.)Thisallowsyoutobaseyour decisionsforIO=resource managementonyourowncriteriaand applicationIO– environment.(Thesame push-model restriction describedinOîSection9.7.3Fîstillexists,however,soyourroutineswillneedtoMOGbeGalaxyaware,possiblyusingsharedmemoryto coordinateOŸtheir operations.*8O±·?2€9ÚõV@OƒFor informationaboutCPU reassignmentAPIs, seeOÜChapter16.*9OŸ—O1Û: ±%OÐ9.7.5B ReassignmentFaultsLO4CPU reassignmentcanfailorbeblocked,forseveralrea-HOŒsons.,BecausetheGCUburiesits managementactionsinMOåSYSMANorDCLscripts,itmaynotalwaysidentifyandre-JO=portthereasonsfora reassignmentfault.+TheGCUdoesJO–performcertaincheckspriortoallowing reassignmentac-OOîtionsinorder,forexample,topreventattemptstoreassignFOGtheprimaryCPU.Otherreasonsexistfor reassignmentOOŸfaultsthatcanonlybedetectedbythe operatingsystemorLOøconsole firmware.)Forexample,ifthe operatingsystemde-QOQtectsafault attemptingtoreassignaCPUthat currentlyhasOO©processaffinityorFastPathduties,aDCLmessagewillbeGO displayedonboththeconsoleandtheusers terminal.|; ÿRKOƒTheGalaxyAPIsfor reassignmentarecapableof reportingOOÜmostfaultstothecaller.)However,evenusingthe reassign-NO5ment services,theconsolemayrejecta reassignmentbecauseNO�ofhardwareplatform dependenciesnotreadilyvisibletotheOæ operatingsystem. üþþxRxZ f�‡ÃüRËPé.¼†1D> ÚR.ÜÝ6„õ G|>G¼‡HFQIš&QÂ<U¡U¤/UÖHXf/Z˜ÛX DivÀq8;|v“ q€R[ …°³€DÆD€ DŠf#ŠŒ_ �î_“Ph šºHœ_ ¡fܤD+ ©r" ­– ¯8‚¯¼Í<à¯Ô+½é½î}ˆ Æ’t¿n˜Ô0à:{á¸Ü™âÐ.ïéðìIôÞŠ ùjMò8£ºÇ„{HLŸî-5pú<lv<ä°éºQ4E–dUüdyS�”’�($'‘Nƒ –Ôõ—̘NÆ™ ž4… ¼B4º¼2¿LÆÁ7ÃN¦Íö¡ ÓšÒÓn¯Õ ñ Ü# ã:§æ䔿z³ç0ñì$, ñRbò¶ôÊ�øj–ú!ü&šþÂC 0:^ šÏlÞ"L)dé*P* /|59´'GÞ«GŒ¢4b0*d\ådD’fØÞg¸™ lTslÊÖn¢mq‹t °ü