DECVAX-VMS OpenVMS Alpha Galaxy Guide*dEVMS_ALPHA_GALAXY_GDOPENVMS-ALPHABASE-VMS-250136BOOKBROWSER  Contents  Tables) B*VAX DOCUMENT V2.1 pKXKgcugrap KKxKhw_rest KKgui_2apK(ЕK Kneeds_chaptȕK0WHIDEKKHK0tsKK6 ,gcu|1z1HPK0@KK;]8200_ints_tabKinuetopihKC(K Kneeds_chaptؖK(KK8200_ints_tab KKؖKgui_16r(KCreatK8200_ints_tabGaH0K0 KPK;_8200_ints_tab R/ gCONTENTSCONTENTS8 E\TitlePageTitle Page@E\ CopyrightPageCopyright Page 1xE\PrefacePreface}w+::$K1OpenVMSGalaxyVersion7.2ReleaseNotes1 OpenVMS Galaxy Version 7.2 Release Notesw)> $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-EFT30C]H\PartIM IntroductiontotheGalaxySoftware ArchitectureonOpenVMSPart I Introduction to the Galaxy Software Architecture on OpenVMS6Xw&&$K2OpenVMSGalaxyOverview2 OpenVMS Galaxy Overview7:\ $K2.19&KANew ComputingModelandaNewSoftware& Architecture2.1 A New Computing Model and a New Software Architecture8w0G $K2.2:&KTheGalaxySoftware ArchitectureonOpenVMS2.2 The Galaxy Software Architecture on OpenVMS;w+A $K2.34&KOpenVMSGalaxy ComponentsandConcepts2.3 OpenVMS Galaxy Components and Concepts=Kl$@2.3.1APMPConcepts2.3.1 APMP ConceptsHb\++$@2.3.2AnotherPossiblePicture2.3.2 Another Possible PictureMdw0 $L2.4#&LOpenVMSGalaxyFeatures2.4 OpenVMS Galaxy FeaturesPdw0 $K2.5#&KOpenVMSGalaxyBenefits2.5 OpenVMS Galaxy BenefitsX~w(> $K2.61&KOpenVMSGalaxyVersion1.0Features2.6 OpenVMS Galaxy Version 1.0 Featuresgdw ,,$K3OpenVMSGalaxyConfigurations3 OpenVMS Galaxy Configurationsisw"9 $K3.1,&KIsanOpenVMSGalaxyforYou?3.1 Is an OpenVMS Galaxy for You?jl->>$@3.1.1WhyaGalaxyisaGoodBusinessChoice3.1.1 Why a Galaxy is a Good Business Choicenl8KK$A3.1.2ThingstoConsiderIfYouWanttoCreateaGalaxy3.1.2 Things to Consider If You Want to Create a Galaxyqw+@ $K3.23&KPossibleOpenVMSGalaxyConfigurations3.2 Possible OpenVMS Galaxy Configurationsxnl%11$A3.2.1Shared-Nothing ComputingModel3.2.1 Shared-Nothing Computing Model~nl%11$@3.2.2Shared-Partial ComputingModel3.2.2 Shared-Partial Computing Modeltl(44$@3.2.3Shared-Everything ComputingModel3.2.3 Shared-Everything Computing Modelpw"6 $K3.3)&K ImportantCluster Information3.3 Important Cluster Informationlg 4 $L3.4'&LSCSIClusterConsiderations3.4 SCSI Cluster ConsiderationsGh $K3.5;&KSecurityConsiderationsinanOpenVMSGalaxy & Computing Environment3.5 Security Considerations in an OpenVMS Galaxy Computing EnvironmentHl $L3.6@&L ImportantInfoThatNeedstobeLocatedinthe& AppropriateChapters3.6 Important Info That Needs to be Located in the Appropriate ChaptersZl''$A3.6.1NewSYSGEN parameter3.6.1 New SYSGEN parameterUl$$$A3.6.2System Auto-Action3.6.2 System Auto-Actionl-::$@3.6.3Changingconsole environment variables3.6.3 Changing console environment variablesQ\""$@3.6.4 CONFIGUREGALAXY3.6.4 CONFIGURE GALAXYsw'44$K4OpenVMSGalaxy Licensing Information4 OpenVMS Galaxy Licensing Informationw*? $L4.12&LOpenVMSGalaxy Licensing Requirements4.1 OpenVMS Galaxy Licensing Requirementssl'44$A4.1.1OpenVMS OperatingSystemLicense4.1.1 OpenVMS Operating System License^l))$A4.1.2OpenVMSGalaxyLicense4.1.2 OpenVMS Galaxy Licensesl'44$@4.1.3OpenVMSLayeredProductsLicense4.1.3 OpenVMS Layered Products License}w(= $K4.20&K ClusteringOpenVMSGalaxy Instances4.2 Clustering OpenVMS Galaxy Instancesnl$22$@4.2.1 ClusteringinaGalaxySystem4.2.1 Clustering in a Galaxy Systemxl)77$A4.2.2 ClusteringOutsideaGalaxySystem4.2.2 Clustering Outside a Galaxy SystemWg) $L4.3&LLicense Databases4.3 License Databasesw(? $K4.42&KOpenVMSGalaxyLicensePAKsandLMF4.4 OpenVMS Galaxy License PAKs and LMFw1H $K4.5;&KForMore InformationAboutOpenVMS Licensing4.5 For More Information About OpenVMS Licensing/>>\PartIINCreatinganOpenVMSGalaxy EnvironmentPart II Creating an OpenVMS Galaxy Environment4M?$K5CreatinganOpenVMSGalaxyonan AlphaServer 84005 Creating an OpenVMS Galaxy on an AlphaServer 8400Gi $K5.1<&KStep1:*Choosea Configurationand Determine &Hardware Requirements5.1 Step 1: Choose a Configuration and Determine Hardware Requirementsl.<<$@5.1.1UsingtheOpenVMS ConfigurationUtility5.1.1 Using the OpenVMS Configuration Utilitywl)66$A5.1.2OpenVMS GalculatorDisplayExample5.1.2 OpenVMS Galculator Display Exampleuw#: $L5.2-&LStep2:&SetUpGalaxyHardware5.2 Step 2: Set Up Galaxy Hardwarel9HH$A5.2.1 InstallingtheKFE72-DAConsole SubsystemHardware5.2.1 Installing the KFE72-DA Console Subsystem Hardwareal++$A5.2.2UsingaTerminalServer5.2.2 Using a Terminal Serverl9GG$@5.2.3Recommendationsfor ConfiguringConsole Subsystems5.2.3 Recommendations for Configuring Console Subsystems`l**$@5.2.4 InstallingEISADevices5.2.4 Installing EISA Devicesqw!8 $L5.3+&LStep3:&CreateASystemDisk5.3 Step 3: Create A System Diskw.F $L5.49&LStep4:&InstallOpenVMSAlphaVersion7.25.4 Step 4: Install OpenVMS Alpha Version 7.2{l+88$A5.4.1OpenVMSGalaxy Licensing Information5.4.1 OpenVMS Galaxy Licensing Informationpw!7 $K5.5*&KStep5:&UpgradetheFirmware5.5 Step 5: Upgrade the Firmwarezw&< $K5.6/&KStep6:&Set Environment Variables5.6 Step 6: Set Environment Variables{l+88$@5.6.1Galaxy Environment VariablesExample5.6.1 Galaxy Environment Variables Example cl,,$A5.6.2TableofUsefulIntegers5.6.2 Table of Useful Integers w0H $L5.7;&LStep7:&Startthe SecondaryConsoleDevices5.7 Step 7: Start the Secondary Console Devices K\$A5.7.1ConsoleHints5.7.1 Console Hintsww$; $L5.8.&LStep8:&BoottheOpenVMSGalaxy5.8 Step 8: Boot the OpenVMS Galaxy4M?$K6CreatinganOpenVMSGalaxyonan 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"kl#00$@6.1.1UsingtheOpenVMS Galculator6.1.1 Using the OpenVMS Galculator&wl)66$@6.1.2OpenVMS GalculatorDisplayExample6.1.2 OpenVMS Galculator Display Example/uw#: $L6.2-&LStep2:&SetUpGalaxyHardware6.2 Step 2: Set Up Galaxy Hardware0l9HH$A6.2.1 InstallingtheKFE72-DAConsole SubsystemHardware6.2.1 Installing the KFE72-DA Console Subsystem Hardware1al++$A6.2.2UsingaTerminalServer6.2.2 Using a Terminal Server6l9GG$A6.2.3Recommendationsfor ConfiguringConsole Subsystems6.2.3 Recommendations for Configuring Console Subsystems7`l**$@6.2.4 InstallingEISADevices6.2.4 Installing EISA Devices>qw!8 $K6.3+&KStep3:&CreateASystemDisk6.3 Step 3: Create A System DiskEw.F $L6.49&LStep4:&InstallOpenVMSAlphaVersion7.26.4 Step 4: Install OpenVMS Alpha Version 7.2G{l+88$A6.4.1OpenVMSGalaxy Licensing Information6.4.1 OpenVMS Galaxy Licensing InformationIpw!7 $K6.5*&KStep5:&UpgradetheFirmware6.5 Step 5: Upgrade the FirmwareJzw&< $K6.6/&KStep6:&Set Environment Variables6.6 Step 6: Set Environment VariablesR{l+88$@6.6.1Galaxy Environment VariablesExample6.6.1 Galaxy Environment Variables ExampleaOl!!$@6.6.2UsefulIntegers6.6.2 Useful Integersbw0H $L6.7;&LStep7:&Startthe SecondaryConsoleDevices6.7 Step 7: Start the Secondary Console DevicesdK\$@6.7.1ConsoleHints6.7.1 Console Hintspww$; $K6.8.&KStep8:&BoottheOpenVMSGalaxy6.8 Step 8: Boot the OpenVMS Galaxyv;U?$L7CreatinganOpenVMSGalaxyonan AlphaServer 4100System7 Creating an OpenVMS Galaxy on an AlphaServer 4100 SystemyVg) $K7.1&KBeforeYouStart7.1 Before You StartzHg! $K7.2&K Procedures7.2 Procedures5N>$K8UsingaSingle-InstanceGalaxyonAnyAlpha System8 Using a Single-Instance Galaxy on Any Alpha Systemn$22\PartIIIMManagingAnOpenVMSGalaxyPart III Managing An OpenVMS Galaxysw'44$K9OpenVMSGalaxy ConfigurationUtility9 OpenVMS Galaxy Configuration UtilityEg   $L9.1&LGCUTour9.1 GCU Tour{l+88$A9.1.1CreatingGalaxy ConfigurationModels9.1.1 Creating Galaxy Configuration ModelsF\$A9.1.2 Observation9.1.2 ObservationWl%%$@9.1.2.1Layout Management9.1.2.1 Layout Management`l**$@9.1.2.2OpenVMSGalaxyCharts9.1.2.2 OpenVMS Galaxy ChartsF\$@9.1.3 Interaction9.1.3 Interactionw,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.2RequiredPROXYAccess9.2.2 Required PROXY Accesslw 4 $K9.3'&KGalaxy ConfigurationModels9.3 Galaxy Configuration ModelsI\$A9.3.1ActiveModel9.3.1 Active ModelM\  $@9.3.2OfflineModels9.3.2 Offline Models|l+99$@9.3.2.1Example:&CreatinganOfflineModel9.3.2.1 Example: Creating an Offline Model_w. $K9.4!&KUsingtheGCUCharts9.4 Using the GCU Chartsl6DD$A9.4.1 ComponentIdentificationandDisplay Properties9.4.1 Component Identification and Display Propertiesbl++$A9.4.2Physical StructureChart9.4.2 Physical Structure ChartO\!!$A9.4.2.1HardwareRoot9.4.2.1 Hardware RootWl%%$A9.4.2.2 OwnershipOverlay9.4.2.2 Ownership Overlay`l**$@9.4.3Logical StructureChart9.4.3 Logical Structure ChartO\!!$@9.4.3.1SoftwareRoot9.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.4Instance Resources9.4.3.4 Instance Resources`l**$A9.4.4Memory AssignmentChart9.4.4 Memory Assignment ChartWl%%$@9.4.4.1Console Fragments9.4.4.1 Console FragmentsWl%%$@9.4.4.2Private Fragments9.4.4.2 Private Fragmentsdl ,,$A9.4.4.3SharedMemory Fragments9.4.4.3 Shared Memory FragmentsZl''$A9.4.5CPU AssignmentChart9.4.5 CPU Assignment ChartKl$A9.4.5.1PrimaryCPU9.4.5.1 Primary CPUQl""$A9.4.5.2 SecondaryCPUs9.4.5.2 Secondary CPUst\'55$A9.4.5.3FastPathand AffinitizedCPUs9.4.5.3 Fast Path and Affinitized CPUsG\$A9.4.5.4LostCPUs9.4.5.4 Lost CPUsZl''$@9.4.6IOP AssignmentChart9.4.6 IOP Assignment Chart\l(($@9.4.7FailoverTargetChart9.4.7 Failover Target Chart!nw!5 $L9.5(&LViewing Component Parameters9.5 Viewing Component Parameters(nw!5 $L9.6(&L Executing ComponentCommands9.6 Executing Component Commands*Uw( $K9.7&KCPU Reassignment9.7 CPU Reassignment+Ql""$A9.7.1DCL Reassignment9.7.1 DCL Reassignment-nl%11$@9.7.2GCU Drag-and-Drop Reassignment9.7.2 GCU Drag-and-Drop Reassignment1_l))$@9.7.3 Intermodal Reassignment9.7.3 Intermodal Reassignment2l2@@$A9.7.4Software ReassignmentUsingGalaxyServices9.7.4 Software Reassignment Using Galaxy Services8Wl%%$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@dw0$K9.10"&K DissolvinganInstance9.10 Dissolving an InstanceAmw 5$K9.11'&KShutdownandRebootCycles9.11 Shutdown and Reboot CyclesBqg"7$K9.12)&KOnlineversusOfflineModels9.12 Online versus Offline ModelsCxg$<$K9.13.&KWhat'sNewForTheGCUinEFT39.13 What's New For The GCU in EFT3FT\$$$A9.13.1NewDCLcommands9.13.1 New DCL commandsG^w-$L9.14&LGCUSystemMessages9.14 GCU System MessagesMCg$K10DCLCommands10 DCL CommandsNOg%$K10.1&KCPUCommands10.1 CPU CommandsRR\""$@10.1.1STOP/CPU/MIGRATE10.1.1 STOP/CPU/MIGRATESC\$@10.1.2SHOWCPU10.1.2 SHOW CPUZMg$$L10.2&LSHOWMEMORY10.2 SHOW MEMORY\hw2$L10.3$&LLexicalFunctionExample10.3 Lexical Function Example^>g $K10.4&KDUMP10.4 DUMPaDg $K10.5&KANALYZE10.5 ANALYZEmDg $K10.6&KINSTALL10.6 INSTALLxw-;;$K11SharedMemoryCluster Interconnect(SMCI)11 Shared Memory Cluster Interconnect (SMCI)yjw3$P11.1%&P SYS$PBDRIVERPortDevices11.1 SYS$PBDRIVER Port Deviceszl,;;$A11.1.1MultipleClustersinaSingleGalaxy11.1.1 Multiple Clusters in a Single Galaxy|}w(=$Q11.2/&QSYSGEN Parametersfor SYS$PBDRIVER11.2 SYSGEN Parameters for SYS$PBDRIVERFl$A11.2.1 SMCI_PORTS11.2.1 SMCI_PORTSFl$A11.2.2 SMCI_FLAGS11.2.2 SMCI_FLAGSxw%;$K11.3-&KLANSharedMemoryDeviceDriver11.3 LAN Shared Memory Device Driverrw&44$K12OpenVMSGalaxyTipsand Techniques12 OpenVMS Galaxy Tips and Techniques2J:\PartIVN DevelopingProgramsForAnOpenVMSGalaxyPart IV Developing Programs For An OpenVMS Galaxyhw"..$K13Locking Programming Interfaces13 Locking Programming Interfacesnw"4$Q13.1&&QSYS$CREATE_GALAXY_LOCK_TABLE13.1 SYS$CREATE_GALAXY_LOCK_TABLEnw"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_LOCKbw.$P13.4 &PSYS$CREATE_GALAXY_LOCK13.4 SYS$CREATE_GALAXY_LOCKbw.$P13.5 &PSYS$DELETE_GALAXY_LOCK13.5 SYS$DELETE_GALAXY_LOCKfw0$P13.6"&PSYS$GET_GALAXY_LOCK_INFO13.6 SYS$GET_GALAXY_LOCK_INFOfw0$Q13.7"&QSYS$GET_GALAXY_LOCK_SIZE13.7 SYS$GET_GALAXY_LOCK_SIZEdw/$Q13.8!&QSYS$ACQUIRE_GALAXY_LOCK13.8 SYS$ACQUIRE_GALAXY_LOCKdw/$Q13.9!&QSYS$RELEASE_GALAXY_LOCK13.9 SYS$RELEASE_GALAXY_LOCKfw1$K13.10"&KLockingErrorMessages13.10 Locking Error Messagesuw(55$K14SystemEvents Programming Interfaces14 System Events Programming InterfacesXw)$P14.1&P$SET_SYSTEM_EVENT14.1 $SET_SYSTEM_EVENT\w+$Q14.2&Q$CLEAR_SYSTEM_EVENT14.2 $CLEAR_SYSTEM_EVENTuw(55$K15SharedMemory Programming Interfaces15 Shared Memory Programming Interfaces^w-$L15.1&LUsingSharedMemory15.1 Using Shared MemoryUw($L15.2&LSystemServices15.2 System ServicesU\$$$A15.2.1EnhancedServices15.2.1 Enhanced Servicesl-::$A15.2.2NewSectionFlagSEC$M_READ_ONLY_SHPT15.2.2 New Section Flag SEC$M_READ_ONLY_SHPTlw 4$K15.3&&K GalaxywideGlobalSections15.3 Galaxywide Global Sectionsww)66$K16CPU Management Programming Interfaces16 CPU Management Programming Interfaces1Zw*$Q16.1&QSYS$CPU_TRANSITION16.1 SYS$CPU_TRANSITION2Vw($Q16.2&Q$CPU_TRANSITIONW16.2 $CPU_TRANSITIONWaw3@@$K17 Configuration Management Programming Interfaces17 Configuration Management Programming InterfacesfJw"$Q17.1&Q SYS$GETSYI17.1 SYS$GETSYIhaw++$K18SystemDumpAnalyzer(SDA)18 System Dump Analyzer (SDA)ow0G$K18.19&KSDACommand InterfaceChangesor Additions18.1 SDA Command Interface Changes or Additionsqgw!..$L19OpenVMSGalaxyDeviceDrivers19 OpenVMS Galaxy Device Driverswkw4$L19.1&&LDirectDMAWindowChanges19.1 Direct DMA Window Changesx4V$K19.2:&KHowPCIDirectDMAWorksPriortoOpenVMS&V7.219.2 How PCI Direct DMA Works Prior to OpenVMS V7.2y5W$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} +gTABLESTABLESLl=@5-1UsefulIntegers5- 1 Useful Integers `l**=@6-1TableofUsefulIntegers6- 1 Table of Useful Integersc  *[1 O'OOpenVMSAlphaGalaxyGuide ! ODecember3,1998SOkThisguide introducesCompaqGalaxySoftware ArchitectureconceptsROand describeshowtocreate,manage,anduseanOpenVMSGalaxy!O computing environment.sKO{Thelatestversionofthisguideisalways availableat:(Ohttp://www.openvms.digital.com*tJ'ORevision/Update Information:#^Thisisanewmanual.uK%O OperatingSystemVersion:&^OpenVMSAlphaVersion7.2mCOSoftwareVersion:'^OpenVMSGalaxyVersion1.0* * j @'O{CompaqComputer CorporationOHouston,Texas >    !   OOJanuary1999IOxTHISDRAFTDOCUMENTISAWORKIN PROGRESS.ITCONTAINSBO PRELIMINARY INFORMATIONTHATISSUBJECTTOCHANGE.]OVCompaqComputer Corporationbelievesthatthe informationinthisdocumentfOisaccurateasofitsissuedate;such informationissubjecttochangewithoutBOnotice.'Compaqisnot responsibleforanyerrors.[OuThisdocumentisprovided``ASIS''andwithoutanyexpressorimpliedUO warranties,! including, without limitation, theimplied warrantiesorEOmerchantabilityandfitnessfora particularpurpose.\OCompaqComputer Corporationmakesnorepresentationsthattheuseofits^Oproductsinthemanner describedinthis publicationwillnotinfringeon`Oexistingorfuturepatentrights,nordothe descriptions containedinthiscO\ publicationimplythegrantingoflicensestomake,use,orsell equipmentor;Osoftwarein accordancewiththe description.aO: Possession,use,orcopyingofthesoftware describedinthis publicationisZO| authorizedonlypursuanttoavalidwrittenlicensefromCompaqoran"O authorized sublicensor.`OZCompaqconductsitsbusinessinamannerthat conservesthe environmentandcOprotectsthesafetyandhealthofits employees, customers,andthe community.IO7CompaqComputer Corporation1999.'Allrights reserved.UOThe 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.\OAllother trademarksand registered trademarksarethepropertyoftheirO8 respectiveholders.:ZK6512FOTheOpenVMS documentationsetis availableonCD-ROM.*   qOPrefaceJOThisguide describeshow customerscantake advantageofDOtheOpenVMSGalaxy capabilities availableinOpenVMSOXAlphaVersion7.2. KOThe informationinthisdocumentappliestoOpenVMSAlphaJOsystemsonly;itdoesnotapplytoOpenVMSVAXsystems.OIntendedAudienceK !HOAThisguideisintendedforsystem managers, applicationHO programmers, technical consultants,datacenter managers,FOandanyoneelsewhowantstolearnabouttheGalaxy.OKSoftware ArchitectureonOpenVMS.ODocument Structure vGOASpecifictopicsinclude:,basicOpenVMSGalaxy concepts,?Ohardwareandsoftware requirements,! configurationIO alternatives, installingand licensing information,systemHOK managementoptions,and available application programmingEO interfaces(APIs)for developingprogramsforOpenVMSOGalaxysystems.~CT2O Tobe supplied:'Chapter descriptions"O*HowtoUsethisBookhZ>>OA Tobe supplied:'Addaroadmapofthebook.! JOThisbook introducesOpenVMSGalaxyfeaturesandexplainsEOhowtousetheOpenVMSGalaxyfeatures availableinHO5OpenVMSAlphaVersion 7.2-EFT3.'Itincludes step-by-stepGO proceduresfor configuring, managing,andusingOpenVMSOOGalaxy technologyaswellasAPIsfor developingprogramstoCO>take advantageofthenewOpenVMSGalaxy features.ORelated Documents>6KOAFor additional informationabouttheOpenSystemsSoftwareGOGroup(OSSG)productsand services,accesstheOpenVMS>OWorldWideWebsiteatthe followingaddress:(Ow http://www.openvms.digital.comOReader'sCommentsgZ==OACompaqwelcomesyourcommentsonthismanual.|BOPrintoredittheonlineformSYS$HELP:OPENVMSDOC_:O COMMENTS.TXTandsendusyourcommentsby:! lOInternet$bopenvmsdoc@zko.mts.dec.com O]FaxAb]603 884-0120, Attention:!OSSGDocumentation,ZKO3-b4/U08O$Mail'b$CompaqComputer Corporation1bqOSSG DocumentationGroup, ZKO3-4/U08b110SpitBrookRd.!b Nashua,NH 03062-26983OHowToOrder Additional Documentation7JOAUsethe followingWorldWideWebaddresstoorderaddi- Otionaldocumentation:,O "http://www.openvms.digital.com:81/JOIfyouneedhelpdecidingwhich documentationbestmeets:Oyourneeds,call 800-DIGITAL(800-344-4825).O ConventionsEZOAInthismanual: `  Instance=OreferstoacopyoftheOpenVMSAlphaoper-(atingsystem. `  OpenVMSGalaxy andT Galaxy refertotheCompaq6GalaxySoftware ArchitectureonOpenVMS. `  DECwindows and DECwindowsMotifreferto4 DECwindowsMotifforOpenVMS software.mCCOThe following conventionsareusedinthismanual:{! QOCtrl/ x&KAsequencesuchasCtrl/ \ x indicatesthatyou?K0mustholddownthekeylabeledCtrlwhileyou?K~pressanotherkeyorapointingdevicebutton. OPF1  x$KAsequencesuchasPF1 Y x indicatesthatyou=KEmustfirstpressandreleasethekeylabeled;KPF1andthenpressandreleaseanotherkey*Korapointingdevicebutton. O OTbWReturn 3T Op;KZIn examples,akeynameenclosedinaboxAK indicatesthatyoupressakeyonthe keyboard.CK(Intext,akeynameisnotenclosedinabox.);KnIntheHTMLversionofthis document,this=K conventionappearsas brackets,ratherthanaK box.j...:KA horizontalellipsisinexamples indicates1Koneofthe followingpossibilities: \V 0V Additionaloptional argumentsina) statementhavebeenomitted. \" 2"The precedingitemoritemscanbe)prepeatedoneormoretimes. \ 5 Additional parameters,values,orother(= informationcanbeentered. O. O; . O .=KAverticalellipsis 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,ormorethanoneKoftheoptions.O{}9KIncommandformat descriptions,bracesin-=K_dicaterequired elements;youmustchooseone#Koftheoptionslisted.O&boldtext>K&Thistextstyle representsthe introductionof  $4O 1.>OpenVMS(Galaxy'Version(7.2'ReleaseOrNotesGOThischaptercontainsOpenVMSGalaxyreleasenotesforIOOOpenVMSVersion7.2and indicatesthecurrentstatusof'OVersion7.2releasenotes.   m nC6O1.1B InformationalMessageDuringBooting OU TBS Q !cluster recognizethenewsecurityclassesas describedinthisOreleasenote.%! VVOThis situationappliesifallofthe following conditionsaremet:t& J ` IIfyourOpenVMSGalaxyis configuredinaclusterwith( non-Galaxysystems ` JIfthe non-GalaxyclusternodessharetheVMS$OBJECTS.DAT"securitydatabasefile ` GIfyouuse galaxywideglobalsectionsinyourOpenVMSGalaxy'N=OOpenVMSVAXandAlphasystemsrunningOpenVMSNOVersion6.2orVersion7.1willcrashifthey encounteranCO5unknownsecurityclassintheVMS$OBJECTS.DATfile.(! WKOToallowVAXandAlphasystemsrunningolderversionsofKOOpenVMSto cooperatewithVersion7.2Galaxy instancesinDO5thesameOpenVMSCluster environment,a SECURITY.EXEOOimageisprovidedforeachofthese versions.+ThefilesareEOlocatedontheOpenVMSAlphaVersion7.2-EFT3CDin*O> directory[VMS$COMMON.SYS$LDR]::)6OOpenVMSAlphaV6.2JSECURITY.EXE_ALPHA_V62 K0SECURITY.STB_ALPHA_V626OOpenVMSAlphaV7.1JSECURITY.EXE_ALPHA_V71 KSECURITY.STB_ALPHA_V712OqOpenVMSVAXV6.2pSECURITY.EXE_VAX_V622OOpenVMSVAXV7.1pSECURITY.EXE_VAX_V71m*CCOTousethenewfiles,youmustdothe following:+l @OForeachOpenVMSAlphaVersion6.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 @OForeachOpenVMSAlphaVersion7.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>OForeachOpenVMSVAXVersion6.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 =OForeachOpenVMSVAXVersion7.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;LOBeforeyoucreateany galaxywideglobal sections,youmustOOrebootallclustermemberssharingoneoftheupdatedsystemOhdisks./tEONotethattheOpenVMSVAXVersion7.2-EFT3 operating/Osystemalreadycontainsthisfix. <p0! wFFO1.4BPossibleProblem UpgradingFirmwareon AlphaServer'(4100Systemsfor V7.2-EFT3MOIfyouareusingan AlphaServer4100systemtofieldtestIOOpenVMSGalaxyorVersion 7.2-EFT3,youshouldbeawareCO^ofapossibleproblemwith upgradingthe firmware.1NGOWhen upgradingfromanypre-V5.2firmwaretotheAS4_HOG52-59firmwarefile,thesystemmayhangoroutputa0O5dumpofthe"ActiveCallFrames".[211OIfthishappens,dothe following:63  '`1.: Power-cyclethesystem.I`O2.:UpgradetoAlphaSystemsFirmwareUpdateVersion5.22intheVersion7.2-EFT3CD-ROMkit.C`'3.:ThenupgradefromAlphaSystemsFirmwareUpdate'Version5.2to AS4_G52-59.4BbNotethatthe AS4_G52-59firmwarefileisinthe7OpenVMSGalaxyfirmwarekit (GALAXY_FIRM_>072.KIT)ontheOpenVMSAlphaVersion7.2-EFT3lCD-ROM2.C5 POIfyouhaveany questionswiththis procedure,pleasegetinJOtouchwithyour V7.2-EFT3 engineeringdirectedfieldtestTO5sitecontact.'Theproblemwillbe correctedinthefinalrelease+OofOpenVMSAlphaVersion7.2. 6]:OPartI8 IntroductiontotheGalaxySoftware#vj ArchitectureonOpenVMS /7['O 2.2OpenVMS!Galaxy!OverviewIOOpenVMSAlphaVersion7.2 introducesamodelofcomput-JOingthatallowsmultiple instancesofOpenVMStoexecute1OB cooperativelyinasingle computer. H8>O2.1BANew ComputingModelandaNewSoftware( Architecture8O Adaptive partitionedmultiprocessing(APMP)isanewIOmodelof computinginwhichmultiple instancesofoper-JO^atingsystemsexecute cooperativelyinasingle computer.IOWithAPMP, processors(andotherphysical resources)areMO partitionedinordertorunmultiple instancesof operatingOhsystems.9eFOAPMPisanotherformofmultiprocessor computinglikeEO symmetricmultiprocessing(SMP)and massivelyparallelJO5 processing(MPP).Forexample,withtwo identicalcomput-LOers(thehardwareisthesame),onecouldrunasanSMPDOsystemandtheothercouldrunasanAPMPsystem.:Wp OThe( GalaxySoftware Architectureisthe complemen-DOtary architecturethat leveragesAdaptive Partitioned=O5Multiprocessing (APMP)! capabilities.4The!GalaxyGO Architectureprovidesthesoftware structureandopera-FOtion componentsthatfullyexploittheAPMP computingO>model. D*J /e; w;?O2.2BTheGalaxySoftware ArchitectureonOpenVMSIOUCompaq'sfirstimplementationoftheAPMPmodelofcom-GOputingistheGalaxySoftware ArchitectureonOpenVMS,JOwhichusesAPMPtoexecutemultiple instancesofOpenVMS"O^inasingle computer.< OSoftware logically partitions)CPUs,memory,andI/OportsJOby assigningthemto individual instancesoftheOpenVMSIO5 operatingsystem.*This partitioning,whichasystemman-NOagerdirects,isasoftware function;nohardware boundaries*Oare required.(Each individual instance!hasthe resourcesitHO>needstoexecuteindependently.)AnOpenVMSGalaxyenvi-Oronmentis adaptive6cinthat resourcessuchasCPUscanbeIO dynamically reassignedto different instancesofOpenVMS. 3= 9O2.3BOpenVMSGalaxy ComponentsandConceptsCOUTo appreciatehowOpenVMSGalaxyusesAPMPtorunLOmultiple instancesofOpenVMSinasingle computer,itisAO importantto understandthisnew computingmodel.> IOTheGalaxySoftware ArchitectureonOpenVMSincludesthe9O followinghardwareandsoftware components:? iOConsole O4The4 console8C4onanOpenVMSsystemis comprisedofanGOattachedterminalandafirmwareprogramthatperformsJOpower-up self-tests, initializes hardware, initiatessystemIO>booting,andperformsI/OservicesduringsystembootingIOand shutdown.(Theconsoleprogramalsoprovidesrun-timeQOservicestothe operatingsystemforconsoleterminalI/O,en-FOG vironmentvariable retrieval,NVRAM (nonvolatilerandomHOaccessmemory)saving,andother miscellaneous services.@ WHOInanOpenVMSGalaxy computing environment,theconsoleNOplaysacriticalrolein partitioninghardware resources.+ItGO5 maintainsthe permanent configurationinNVRAMandtheKOrunning configurationinmemory.'TheconsoleprovideseachMOinstanceoftheOpenVMS operatingsystemwithapointerto,O>therunning configurationdata.A OSharedmemoryNO4Memoryis logically partitionedintoprivateandsharedsec-KOtions.,Each operatingsysteminstancehasitsownprivatePOmemory;thatis,nootherinstancemapsthosephysicalpages.JO>Someofthesharedmemoryis availablefor instancesofKOOpenVMSto communicatewithoneanother,andtherestof@Othesharedmemoryis availablefor applications.9B LOTheGalaxySoftware Architectureispreparedforanonuni-EOformmemoryaccess(NUMA) environmentand,ifneces-RO5sary,willprovidespecialservicesforsuchsystemstoachieve,Omaximum application performance.COCPUsEO4InanOpenVMSGalaxy computing environment,CPUscan-Obe reassignedbetween instances.fD! W< OI/OLO4AnOpenVMSGalaxyhasahighlyscalableI/O subsystembe-JOcausethereare multiple,primaryCPUsinthe system-oneMOforeach instance.(Also,OpenVMS currentlyhasfeaturesforLO> distributingsomeI/Oto secondaryCPUsinanSMPsystem.QE W' O Independent instancesIO4OneormoreOpenVMS instancescanexecutewithoutshar-DOingany resourcesinanOpenVMSGalaxy.,AnOpenVMSEOinstancethatdoesnotshare resourcesiscalledane indepen-O> dentinstance y>.F NLOAn independentinstanceofOpenVMSdoesnot participateinJOsharedmemoryuse.)Neitherthebase operatingsystemnor4O5its applicationsaccesssharedmemory.GNAOAn OpenVMS!Galaxy can consist solely of indepen-IOdent instances;suchasystemwouldresemble traditional(O5mainframe-style partitioning.H ^O2.3.1BAPMPConceptsGO4Architecturally,APMPisbasedonanSMPhardwarear-GO chitecture.,ItassumesthatCPU,memory,andI/OhaveNOfull connectivitywithinthemachineandthatthememoryisNO=cache coherent.*Each subsystemhasfullaccesstoallotherO subsystems.I! lOAsshownin!Figure2-1.diagram,APMPthenlooksattheQO resourcesasiftheywereapie.&Thevarious resources(CPUs,EO5privatememory,sharedmemory,andI/O)arearrangedNOas concentricbandswithinthepieinaspecific hierarchy..OSharedmemoryisatthecenter.*I!FOJK! ^LOAPMPsupportstheabilitytodividethepieintomultipleWOslices,eachof disparatesize.'Eachslice, regardlessofsize,hasLO<accesstoallofsharedmemory.) Furthermore,becausesoft-QOware partitionsthepie,youcanvarythenumberandsizeofOslices dynamically.!L QOInsummary,eachsliceofthepieisaseparateandcompleteJOinstanceofthe operatingsystem.+EachinstancehassomeGO5amountof dedicatedprivatememory,anumberofCPUs,NOandthe necessaryI/O.EachinstancecanseeallofsharedMOmemory,whichiswherethe applicationdataresides.'SystemJO> resourcescanbe reassignedbetweenthe instancesofthe0O operatingsystemwithout rebooting.M+O2.3.2BAnotherPossiblePictureIO4AnotherwaytolookattheAPMP computingmodelisto@Othinkabouthowthe resourcescouldbedivided.NJOTheoverallsenseofthediagramisthatthe proportionLObywhichoneresourceisdividedbetween instancesistheJO5 proportionbywhicheachoftheother resourcesmustbeOdivided./O HOSomeboxeswouldhavevarying proportionsper instance. PhysicalP 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   | / |  / |Fw +------+%-%-&-%-%-& -+------+%-&-%-%-&-% -+------+ Py(O2.4BOpenVMSGalaxyFeaturesEOUAn evolutioninOpenVMSfunctionality,OpenVMSGalaxyDO leveragesprovenOpenVMSCluster, symmetric multipro-NOcessing,and performance capabilitiestooffergreaterlevelsLO^of performance, scalability,and availabilitywith extremely.Oflexible operational capabilities.QO ClusteringJO4FifteenyearsofprovenOpenVMSCluster technologyfacil-HOitates communicationamong clustered instanceswithinanOOpenVMSGalaxy.R ROAnOpenVMSClusterisasoftwareconcept.'Itisasetofco-1O ordinatedOpenVMS operatingsystems, onepercomputer U,GO5 communicatingovervariouscommunicationsmediatocom-LObinethe processingpowerandstoragecapacityofmultipleFO computersintoasingle,shared-everything environment.S WLOAnOpenVMSGalaxyisalsoasoftwareconcept.(However,itCOisasetof coordinatedOpenVMS operatingsystems, inasin-O5 glecomputer8 5, communicatingthroughsharedmemory.*AnLOinstanceofthe operatingsysteminanOpenVMSGalaxycanNObe clusteredwithother instanceswithintheGalaxyorwith(O> instancesinothersystems.T LOAnOpenVMSGalaxyisacompletesysteminandofitself.IOAlthoughanOpenVMSGalaxycanbeaddedtoanexistingRO5clusterasmultipleclusternodescanbeaddedtoday,thesin-IOglesystemistheOpenVMSGalaxy architecturefocus.+AnIO applicationrunningtotallywithinanOpenVMSGalaxycanKO>take advantageof performance opportunitiesnotpresentin O multisystem clusters.U  OSMPHO4AnyinstanceinanOpenVMSGalaxycanbeanSMPcon-OO figuration.*ThenumberofCPUsispartofthe definitionofLOan instance.(BecauseaninstanceintheOpenVMSGalaxyisJO>acompleteOpenVMS operatingsystem,all applicationsbe-POhavethesameastheywouldona traditional,single-instanceO computer.V! OCPU reassignmentKO4ACPUcanbe dynamically reassignedfromoneinstancetoNOanotherwhileall applicationsonboth instancescontinuetoKOrun.+ Reassignmentisrealizedbythreeseparate functions:MO> stopping, reassigning,andstartingtheCPUin question.*AsOOresourceneedsof applicationschange,theCPUscanbereas-NOsignedtothe appropriate instances.(Therearesomerestric-LOGtions;forexample,theprimaryCPUinaninstancecannotPObe reassigned,andaCPUcannot specificallybe designatedto&Ohandlecertain interrupts.W"ODynamicReconfigurationGO4Multiple instancesoftheOpenVMS operatingsystemal-IOlowsystemmanagerstoreassign processingpowertotheIO instanceswhose applicationsmostneedit..AsthatneedIO>variesovertime,socantheconfiguration.,OpenVMSal-KOlowsdynamicreconfigurationwhileall instancesandtheir*O applicationscontinuetorun. ;!X(O2.5BOpenVMSGalaxyBenefitsEOUManyofthethebenefitsofOpenVMSGalaxytechnol-LOogyresultdirectlyfromrunningmultiple instancesofthe>OOpenVMS operatingsysteminasingle computer.Y! NJOWithseveral instancesofOpenVMSinmemoryatthesameHOtime,anOpenVMSGalaxy computing environmentgivesyou$O5quantum improvementsin:Z H ` FCompatibility-Existing applicationsrunwithoutchanges. `O EOAvailability-Presents opportunitiestoupgradesoftware=andexpandsystemcapacitywithoutdowntime. `' H'Scalability-Offersscaling alternativesthatimproveper-8formanceofSMPandcluster environments. ` @Adaptability-Physical resourcescanbe dynamically<W reassignedtomeetchangingworkloaddemands. ` >Costofownership-FewercomputersystemsreduceF/system management requirements,floorspace,andmore.[_LOThe following descriptionsprovidemoredetailsabouttheseO benefits.R\ W(O CompatibilityLO4Existing single-system applicationswillrunwithoutchangesDOon instancesinanOpenVMSGalaxy.,ExistingOpenVMSMOCluster applicationswillalsorunwithoutchangesonclus-4O>tered instancesinanOpenVMSGalaxy.]! O AvailabilityIO4AnOpenVMSGalaxysystemismore availablethanatra-HO ditional,single-system-view,SMPsystembecausemultipleNO instancesofthe operatingsystemcontrolhardware resources.^! WHOOpenVMSGalaxyallowsyoutorun differentversionsofJOOpenVMS(Version7.2andlater)simultaneously.'Forexam-SO5ple,youcantestanewversionofthe operatingsystemoranOO applicationinoneinstancewhile continuingtorunthecur-NOrentversiontheother instances.(Youcanthenupgradeyour6O>entiresystem,oneinstanceatatime._ uO ScalabilityGO4Systemmanagerscanassign resourcestomatchapplica-MOtion requirementsasbusinessneedsgroworchange.&WhenaROCPUisaddedtoaGalaxyconfiguration,itcanbeassignedtoKO>anyinstanceofOpenVMS.Thismeansthat applicationscan/Orealize100%ofaCPU'spower.0`GOTypicalSMPscalingissuesdonotrestrictanOpenVMSAOGalaxy.2Systemmanagerscandefinethe number ofFO5OpenVMS instances,assignthenumberofCPUsineach8O instance,andcontrolhowtheyareused.a WHO Additionally,atrial-and-errormethodof evaluatingre-LOsourcesisaviable strategy.*SystemmanagerscanreassignDO5CPUsamong instancesofOpenVMSuntilthemostef-MOfective combinationof resourcesisfound.,All instancesofKOOpenVMSandtheir applicationscontinuetorunwhileCPUsO>are reassigned.%b O AdaptabilityHO4AnOpenVMSGalaxyishighly adaptablebecause computingOO resourcescanbe dynamically reassignedtoother instancesofNOthe operatingsystemwhileall applicationscontinuetorun.'cJO ReassigningCPUsbest demonstratestheadaptive capabilityDOofanOpenVMSGalaxy computing environment.+Forex-HO5ample,ifasystemmanagerknowsthatresourcedemandsJOchangeatcertaintimes,thesystemmanagercanwriteaJOcommand proceduretoreassignCPUstoother instancesofHO>OpenVMSandsubmittheprocduretoabatchqueue.+TheKOsamecouldbedonetomanagesystemloadcharacteristics.dWHOInanOpenVMSGalaxy environment,softwareisintotalIOcontrolof assigningand dynamically reassigninghardwareJO5 resources.)As additionalhardwareisaddedtoanOpenVMSNOGalaxysystem, resourcescanbeaddedtoexisting instances;KOornew instancescanbedefinedwithout affectingrunningO> applications.e `OCostof ownershipHO4AnOpenVMSGalaxypresents opportunitiestoupgradeex-KOisting computersandexpandtheir capacity,ortoreplaceIOsomenumberof computers,whethertheyareclustermem-MO>bersor independentsystems,withasinglecomputerrunningLOmultiple instancesofthe operatingsystem.'Fewer computersJOgreatlyreducessystem management requirementsaswellasOGfloorspace.fO PerformanceEO4AnOpenVMSGalaxycanprovidehigh commercialappli-HOcation performanceby eliminatingmanySMPandcluster-QOscaling bottlenecks.)Also,the distributionof interruptsacrossLO> instancesprovidesmanyI/O configurationpossibilities;forNOexample,asystem'sI/Oworkloadcanbe partitionedsothatCOcertainI/Otrafficisdoneonspecific instances. g6O2.6BOpenVMSGalaxyVersion1.0FeaturesCOUWithOpenVMSAlphaVersion7.2,youcancreatean>OOpenVMSGalaxy environmentthatallowsyouto:h Nn ` ARunthree instancesofOpenVMSonan AlphaServer(8400 ` ERuntwo instancesofOpenVMSonan AlphaServer8200 `' E'Runtwo instancesofOpenVMSonan AlphaServer4100 ` ,ReassignCPUsbetween instances `& E&Perform independentbootingandshutdownof instances ` ?Usesharedmemoryfor communicationbetweenin-stances `} E}Cluster instanceswithinanOpenVMSGalaxyusingthe/sharedmemorycluster interconnect `U 7UCluster instanceswith non-Galaxysystems ` ACreate applicationsusingOpenVMSGalaxyAPIsforC-resource management,event notification,lockingforFsynchronization,andsharedmemoryforglobalsections ` JUsetheGalaxy ConfigurationUtilitytoviewandcontrol+]theOpenVMSGalaxy environment ` BRunasingle-instanceOpenVMSGalaxyonanyAlpha/5systemfor application development qWi%--O 3.2OpenVMS!Galaxy!Configurations D* D* D* [ ]j! 31O3.1BIsanOpenVMSGalaxyforYou?JOUFor companieslookingtoimprovetheirabilitytomanageIOunpredictable, variable,orgrowingIT workloads,OpenVMSIOGalaxy technologyprovidesthemostflexiblewaytody-EO^ namically reconfigureandmanagesystem resources.,AnIO integratedhardwareandsoftware solution,OpenVMSGalaxyMOallowssystemmanagerstoperformtaskssuchas reassigningKOh individualCPUsthroughasimpledraganddrop procedure.kzEOAnOpenVMSGalaxy computing environmentisidealfor5Ohigh-availability applications,suchas:l ` Databaseservers `O *O Transaction processingsystems ` Data Warehousing `N NDataMining ` Internetserversm JO Also,pointoutsomeexamplesofwhenanOpenVMSGalaxyDO isNOTtheanswer./Forexample:/singlestreamnon-JO5 threaded computation, situationswherethe individualCPUsOO mustbe physicallyseparatetobenearother equipment,suchOO asforprocesscontrol.+Perhapsjustsaythatif traditionalMO> SMPwouldnotworkatallthenOpenVMSGalaxyisnottheO answer.n >O3.1.1BWhyaGalaxyisaGoodBusinessChoiceGO4 Tobe supplied:'InfoaboutmixedversionsandrollingO upgrades.oNCOAnOpenVMSGalaxy computing environmentisanatu-JOral evolutionforcurrentOpenVMSuserswithclustersor1O5multiplesparsely configuredsystemspJOAnOpenVMSGalaxyis attractiveforgrowing organizationsAOwithvaryingworkloads-predictableor unpredictableqM}KO3.1.2BThingstoConsiderIfYouWanttoCreateaGalaxy2O4 Thissectionneedstobe developed.rmJOWhenyouplantocreateanOpenVMSGalaxy,youneedto#Oconsiderthe following:Rs( ` HaveenoughCPUs?Tt* ` Haveenoughmemory?Ju{  bEnoughI/O adapters?av7 ` ,Howto configureI/O adapters?bw8 ` -Howto configuresystemsdisks?   x8O3.2BPossibleOpenVMSGalaxyConfigurationsEOU TBS:Inthissection,giveanoverviewofthemod-?O elsof computing..Thendescribehowthemodels4O "transform"intoGalaxyconfigurations.y NFOAnOpenVMSGalaxy computing environmentlets customersKOdecidehowmuch cooperationexistsbetween instancesina#O5singlecomputersystem.zNOIna shared-nothing/ computingmodel,the instancesdoKOnotshareany resources; operationsareisolatedfromoneO5another.{OIna shared-partial2j computingmodel,the instancesshare?Osome resourcesand cooperateinalimitedway./|OIna shared-everything+model,the instances cooperateNOfullyandshareall available resources,tothepointwherePO5the operatingsystempresentsasinglecohesiveentitytotheOnetwork.}pAO Tobe supplied:,Expandthe descriptionsofthese/O modelsinthe following sections.U~! V+1O3.2.1BShared-Nothing ComputingModelMO4Inasharednothingconfiguration,the instancesofOpenVMSLOare completely independentofeachotherandare connectedMOthroughexternalinterconnects,asthoughtheywereseparateO= computers.+! KOWithAPMP,all availablememoryis allocatedintoprivateMOmemoryforeachinstanceofOpenVMS.EachinstancehasitsNO5ownsetofCPUsandan appropriateamountofI/O resourcesOassignedtoit.[11O3.2.2BShared-Partial ComputingModel^44O3.2.3BShared-Everything ComputingModel # !X..O3.3B ImportantCluster Informationh ` 3 EverythingshouldworkinInstance0 `O >OSomethingsmightnotworkinnon-0 instances _ ! " ,O3.4BSCSIClusterConsiderationsLOU PointtotheOpenVMSClusterSystemsbookfordevicenam-O inginfo.){IOIfyouarecreatinganOpenVMSGalaxywithsharedSCSI2Obuses,youmustnotethe following:NJOForOpenVMSto correctlygivetheSCSIdevicesthesameNOnameoneach instance,youwilllikelyneedtoutilizethe.O5 device-namingfeatureofOpenVMS.? NOForexample,assumethatyouhavethe followingadaptersonEOyoursystemwhenyouentertheSHOWCONFIGcommand:,Oa PKA0& (embedded%SCSI&for%CDROM)/O PKB0& (UltraSCSI% controller%KZPxxx)'O PKC0& (UltraSCSI% controller)*FOWhenyoumakethissystema two-instanceGalaxy,youO ????????????Oa Instance%0'O PKA0K (UltraSCSI& controller)O Instance%1,OZ PKA0K (embedded%SCSI%for%CDROM)'O PKB0K (UltraSCSI& controller)! rNOYoursharedSCSIwillbe connectedfromPKA0oninstance0$OtoPKB0oninstance1.) JOIfyou initializethesystemwiththeLP_COUNT environm-UOnetvariablesetto0,youwillnotbeabletobootOpenVMSonEO5thesystemunlesstheSYSGEN parameter STARTUP_P1isOsettoMINIMUM.tJHOThisisbecause,withtheLP_COUNTvariablesetto0,GOyouwillnohavePKB connectedtoPKC,andtheSCSINO5 device-namingthatwassetupfor initializingwithmultipleNO partitionsisnotcorrectfor initializingwiththeLP_COUNTOvariablesetto0.T*IODuringthedevice configurationthatoccursduringboot,FOOpenVMSwillnoticethatPKA0andPKB0are connectedIO5 together.*OpenVMSexpectsthateachdevicehasthesameRO allocationclassandnames,butinthiscase-theywillnot. IOThedevicenamingwhichwassetupforthe2instanceQOGalaxywillnotfunction 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. _"!#)@O3.5BSecurityConsiderationsinanOpenVMSGalaxy ( Computing Environment?OOpenVMS Galaxy instances executingin a shared-EO everythingcluster environment, inwhichallsecurityKO^databasefilesaresharedbetweenall instances, automati-POcallyprovidea consistentviewofallGalaxy-relatedsecurityO profiles. lSOIfyouchoosenottoshareallsecuritydatabasefilesthrough-SOoutallGalaxy instances,a consistentsecurityprofilecanonlyOO5beachieved manually.'Changestoanobject'ssecurityprofileMOmustbefollowedbysimilarchangesonall instanceswhere*Othisobjectcanbe accessed. WPOBecauseoftheneedto propagatechanges manually,itisun-OOlikelythatsucha configurationwouldeverbecoveredbyaLO5USC2 evaluationorbysimilar evaluationsfromotherau-JO thorities., Organizationsthatrequire operatingsystemstoOOhavesecurity evaluationsshouldensurethatall instancesinEO>asingleOpenVMSGalaxybelongtothesamecluster. h # "$AdEO3.6B ImportantInfoThatNeedstobeLocatedinthe( AppropriateChaptersMV'O3.6.1BNewSYSGEN parameter/O4The GLX_INST_TMOSYSGEN parameter:g=FOEachSHARINGmemberticksa heartbeatcellinsharedJOmemorywhichtheother instanceswatch.*Ifan instance'sEO5 heartbeatstopstickingfor GLX_INST_TMO milliseconds,NOthatinstancewillbeassumedtobedeadandremovedasaOsharingmember. IOIfforexample,youCTRL-PasharingmemberforlongerGOthat GLX_INST_TMO milliseconds,uponissuingaContinueGO5commandfromtheconsole,theinstancewill immediatlyHObugcheckwithaGLXEXIT bugcheck.)ThisisverysimilarOOtothebehaviorofanOpenVMSclusterthatwouldresultinaGO>CLUEXITbugcheckifaclustermemberwasinaCTRL-P;Ostateforlongerthan RECNXINTERVALseconds. NJOThesharingmembersallusethesamevalueof GLX_INST_OOTMO.Thevalueusedisthesmallestvalueofanynodethat.O5hasEVERbootedintotheGalaxy\! V2$O3.6.2BSystem Auto-ActionGO4Uponsystem power-up,ifthe AUTO_ACTIONconsoleenvi-NOronmentvariableissettoBOOTorRESTARTforinstance0,JOthentheGALAXYcommandwill automaticallybeissuedand/O=instance0willattempttoboot.O%FOThesettingof AUTO_ACTIONintheconsole environmentOO variablesfortheother instanceswilldictatetheirbehaviorHO5upontheissuingoftheGALAXYcomamnd(whetheritisHOissued automaticallyorbytheuserfromthe console).YQOTosetupyoursystemforthisfeature,youmustsetthecon-COsole environmentvariable "AUTO_ACTION"to "RESTART"MO5or"BOOT"oneach instance,andbesuretospecifyappro-BOpriatevaluesforthe BOOT_OSFLAGSand BOOTDEF_DEV6O environment variablesforeach instance. :O3.6.3BChangingconsole environment variablesBO4Onceyouhave establishedtheinitialsetofLP_ ?*>4environ-GOment variablesforOpenVMSGalaxy operationandbootedJOyoursystem,changing environmentvariablevaluesrequiresMO=thatyoufirst re-initializethesystem,changethevalues,EOand re-initializeagain..WrappingthechangesbetweenQOINITsisrequiredtoproperly propagatethenewvaluestoallOG partitions. _UNote _JQForthe4100,noINITisneededtostartbutyoumust8changethese variablesonboth instances. |"O3.6.4B CONFIGUREGALAXY>O4TheGCUcannow beinvokedviaDCL commands:O CONFIGUREGALAXY. H$#%c95O 4.2OpenVMS!Galaxy! Licensing! InformationCOTheOpenVMSGalaxySoftware ArchitectureonOpenVMSGO(OpenVMSGalaxy)isasystem integratedproduct(SIP).JOBThatis,OpenVMSGalaxycodeis integratedand delivered0OwiththeOpenVMS operatingsystem. W OpenVMSVersion7.2CD-ROMs >. _ % $&7O4.1BOpenVMSGalaxy Licensing RequirementsFOUThe followinglist summarizesOpenVMSGalaxy licensingO requirements:! ps ` BOneOpenVMS OperatingSystemLicenseforaGalaxy(system ` IOneSMP ExtensionLicenseforeachCPUafterthefirst CPU ` FOneOpenVMSGalaxyLicenseforeachCPUinaGalaxysystem `W IWNochangestohowCompaqlayeredproductsare licensed:}AS-YOnecapacitylicensepersystem&Y(Oneuserlicenseperuse\KOThe followingsectionsdescribethese requirementsinmoreOdetail.)4O4.1.1BOpenVMS OperatingSystemLicenseHO4Whenan AlphaServersystemis configuredasanOpenVMSJOGalaxysystem,therearenochangesinhowasystemis9OlicensedfortheOpenVMS operatingsystem. NKOOneOpenVMSBaseLicenseisrequiredfortheGalaxysys-NOtem,plusoneSMP ExtensionLicenseforeachCPUaftertheO5firstCPU. )O4.1.2BOpenVMSGalaxyLicenseMO4Inordertocreateandrunmultiple instances,oneOpenVMSOOGalaxyLicenseisrequiredforeachCPUinaGalaxysystem.LOLicenserightsforrunningasingle-instanceGalaxyonanyHOAlphasystemareprovidedbytheOpenVMSBaseLicense.&! 4O4.1.3BOpenVMSLayeredProductsLicenseHO4CompaqsoftwarelayeredproductsonOpenVMSGalaxycon-QO figurationscontinuetousestandardlicensetypes:' Traditional,/O ConcurrentUse,andPersonalUse.  ` FOne TraditionalcapacityLicensewillcontinuetoli-J(censethesystem, regardlessofthenumberof instances.LThelicenseisbasedonthesystemclassofthehardwaresystem. `Y EY ConcurrentUseLicenseswillcontinuetolicenseone, concurrentuseoftheproduct. `1 J1PersonalUseLicenseswillcontinuetolicenseonenamed useronthesystem. &%'5O4.2B ClusteringOpenVMSGalaxy InstancesDOU InstancesinanOpenVMSGalaxy computing environmentLOcanbe clusteredwithother instancesinasinglesystem,LOwith instancesinotherGalaxysystems,orwith non-GalaxyIO^systems..Eachtypeof clusteringhas different licensingEO requirements,as describedinthe following sections.oVE2O4.2.1B ClusteringinaGalaxySystemEO4InanOpenVMSGalaxy computing environment, instancesMOcanbe clusteredwithother instanceswithinaGalaxysys-FOtem.+ Clustered instancesusethe shared-memorycluster;O= interconnectto communicatewitheachother.! POThe licensingand functionalityfor clusteringwithinaGalaxyEOsystemisprovidedundertheOpenVMSGalaxyLicense. ~7O4.2.2B ClusteringOutsideaGalaxySystemAO4 InstancesinanOpenVMSGalaxy computingenviron-IOmentcanbe clusteredwith instancesinanotherOpenVMSLOGalaxysystemorwithclusternodesin non-Galaxysystems.PO= Instances clusteredoutsideofaGalaxysystemuse traditional!Oclusterinterconnects.# LOEachsystemthatis clusteredwithanothersystemmustbeIOlicensedforOpenVMSCluster Software.) ClusteringoutsideJO5theOpenVMSGalaxysystemisnotcoveredbytheOpenVMSOGalaxyLicense. + '&( !O4.3BLicense DatabasesGOUWhenanOpenVMSGalaxysystemis configuredwithmoreROthanone instance,alicensedatabasemustbesetupforeachMO independentinstanceorclusterof instances.(ThePAKsrep-KO^ resentingthelicensesontheOpenVMSGalaxy configurationJOmaybeloadedonmultiplelicense databases,asfollows:A] ` @OpenVMSBase,SMP Extensions,andOpenVMSGalaxy(Licenses]vBbForfulluseoftheOpenVMSGalaxyfunctionality,<thePAKs representingyourOpenVMSBase,SMP? Extensions,andOpenVMSGalaxyLicensesmustbeClloadedoneachlicensedatabasewithintheOpenVMS(Galaxyonasinglesystem. `D CDCompaqLayeredProduct TraditionalCapacityLicensesGbThePAKs representingtheselicensescanbeloadedonFeachlicensedatabasewithintheOpenVMSGalaxyonasinglesystem. ` +Compaq ConcurrentUseLicensesGbThePAKs representingtheselicensescanbeloadedonFthelicensedatabasewherethelicensewillbeused.' CbForPAKs representingmultiple concurrentuses(forFexample,a50_uselicense)thePAKcanbeloadedonDmultiplelicense databaseswithintheOpenVMSGalaxyHlonasinglesystem.)However,thePAKmustbemodifiedMdownoneachlicensedatabasesothatthetotalnumberofPlicenseunitsdoesnotexceedthetotallicenseunitsonthevLicensePAK. ` )CompaqPersonalUseLicenses@GbThePAKs representingtheselicensescanbeloadedonFeachlicensedatabasewithintheOpenVMSGalaxyonaHsinglesystem;however,thenumberofactualusesmustAlnotexceedthelicensednumberofpersonaluses. " (')no7O4.4BOpenVMSGalaxyLicensePAKsandLMF8OUOpenVMSGalaxyPAKnamesareasfollows:" ` :OpenVMS OperatingSystemBasePAK:OPENVMS- (ALPHA(baselicense) ` :OpenVMS OperatingSystemUserPAK:OPENVMS- ALPHA-USER ` /OpenVMSGalaxyPAK:OPENVMS-GALAXYP&@OOpenVMSGalaxy customersmusthaveatleastone>O OPENVMS-ALPHAPAK,plusone additionalOPENVMS-IO5ALPHAPAKforeach additional processor(CPU)aftertheLOfirstCPU(whichisincludedintheBase OperatingSystemO License).P&5OThe OPENVMS-ALPHAandOPENVMS-ALPHA-USERJOPAKscannowbesharedbymultipleGalaxy instances.*ToIO5 implementthisintheLicense ManagementFacility(LMF),FOincludeallOpenVMSGalaxyinstancenamesinthePAKOINCLUDElist.G JOForexample,supposethatacustomerhasasystemnamed?OANDA1AinanOpenVMSCluster.'The OPENVMS-ALPHALO5licensePAK currentlyhasanINCLUDElistonitthathasIOSCSnodenameANDA1Ainit.+IfthatsystemischangedCOtoanOpenVMSGalaxyrunningthree instancesnamedANDA1A,ANDA2A,andANDA3A,the OPENVMS-ALPHAPOlicensePAKmustbemodifiedsothatall instancescanshare0OtheNO_SHARE OPENVMS-ALPHAlicense.?OThecommandtomodifythe OPENVMS-ALPHAlicenseOPAKis:EOa $&LICENSE%MODIFY&$OPENVMS-ALPHA/AUTHORIZATION=blahblah%--O #_$/INCLUDE=3D(ANDA1A,ANDA2A,ANDA3A)/JOSincethisexampleassumesthatANDA1AwasalreadyinaOOcluster,the authorizationnumberisrequiredtoidentifytheCO5onePAKofmany OPENVMS-ALPHAlicensePAKsinthe)Olicensedatabasefile(LDB).J  O TBS-Modifydowninfo )(*@O4.5BForMore InformationAboutOpenVMS LicensingAOUFor informationaboutusingtheOpenVMS LicensingBO Management Facility,refertothe followingbooks: o ` < OpenVMSAlphaUpgradeand InstallationManual,con-G(tainsnotesand supplemental informationaboutlicenses%and licensing procedures. ` 7 OpenVMSLicense ManagementUtilityManualcontainsEY complete,detailed informationaboutOpenVMS licensing procedures. *)+h >>OPartII7CreatinganOpenVMSGalaxy Environment +*,h3O 5.@Creating(an(OpenVMS(Galaxy(on(anOr AlphaServer!8400HOThischapter describeshowtocreateanOpenVMSGalaxyO5.2.1B InstallingtheKFE72-DAConsole Subsystem<(HardwareJOTheKFE72-DAisthesetofEISA-busmodulesthatestab-LOlishesan additionalconsoleport.'OneKFE72-DAmoduleset2O=isrequiredper secondary partition.qGGOTheKFE72-DAcontainsthreeEISAmodulesthatprovide: ` TwoCOMports `O  OAkeyboard interface ` Amouse interface `N NAsmallspeaker ` AnEthernetport.NKOTheCOM-1portisusedfortheconsoleserialline.-ThePOEthernetportcanbeusedasanetwork connectionoritcanLO5be terminated.'Themouseandkeyboardportsarenotused. qJOTheKFE72-DAmustbepluggedintothebottomthreeEISAPOslots.(Forthe AlphaServer8400thisrequiresthatyouattachMO5ahosefromyourI/OporttoaDWLPBPCIcardcage.(TheSOKFE72-DAmodulesetmustbe installedinslots0,1,and2ofLOthecardcage.)TheKFE72'sSIO(a.k.a.(Bridge)moduleen-NO>ablestheEISAslotswhicharepartofthe combinationPCILO/EISA backplane.'Theothertwomodulesknownasthe"DataQOPortModule"and "Beeper97"goinslots1and2 respectively.N `$+O5.2.2BUsingaTerminalServerMO4YoumaywanttobringyourconsolelinestogetherusingaKOterminalserver.)Forexample,usea DECserver200toallowLO reverse-LATaccesstoeachconsoleoverthenetwork.'WhileNO=thisisnotstrictly required,itgreatly simplifiesOpenVMSIOGalaxy configuration management.(Refertothe appropriateJOproduct documentationfordetailsabout configuringaLAT4OGServerorotherterminal concentrator. ~;O5.2.3BRecommendationsfor ConfiguringConsole<( SubsystemsJOEach additionalconsolerequiresaseparateKFE72-DAsub-NOsystem installedinaseparateDWLPBcardcagewithahoseKO= connectingittoaseparateI/OmoduleoftypeKFTIAorLOKFTHA.IfyouareusingaKFTIA,itmustbeinslot8. NOO AdditionalKFTIAI/OmodulesmustbeinthenextlowerslotOOorslots,withKFTHAI/OmodulesinthenextlowerslotorO5slotsafterthat.KOYoucanuseany combinationofthesetwoI/Omodulesas>Olongasyoufollowthisslot assignmentrule. NFOThe AlphaServer8400supportsamaximumofthreeI/OLOmodules.( Attemptingto configuremorethanthreeisunsup-O5ported.pIOWhen configuringaconsole subsystem,theI/Ohosecon-HOnectingtheI/O ProcessorandDWLPBcardcagemustbeIO5pluggedintothelowesthoseport.(Notjustthelowest5 avail-O ablePhoseport,buttheabsolutefirsthoseport;theoneclosest(Otothetopofthemodule.eIOKFE72-DAmodulesmustoccupyslots0,1,and2oftheODWLPBcardcage. NLOTheconsoleseriallineis connectedwithanH8571-Jcon-ROnectoradapterthatplugsintotherighthandseriallineportLO5whenviewedfromtherearofthemachine.&ThisisCOM-1.NV$*O5.2.4B InstallingEISADevicesNO4Plug-inEISAdevicescanonlybe configuredin partition0.OOAfter installingEISAdevices,theconsolewillissueames-MOsage requestingthatyouruntheEISA ConfigurationUtilityO=(ECU).O%%ORuntheECUasfollows:! YZ:`1.:ShutdownallOpenVMSGalaxy instances.S`O2.:Besureyourfloppydiskdriveisproperly connectedtotheHprimary partitions hardware.( TypicallythedrivecanbeGcabledintothe ConnectorModule ("Beeper"partnumber)Y 54-25133-01)inPCIslot2.A`3.:Insertthediskette containingtheECUimage.K`W4.:Issuethe followingcommandsfromtheprimaryconsole:% P00>>>&SET% ARC_ENABLE&ON$ P00>>>& INITIALIZEl P00>>>&RUN%ECUN`5.:Followthe proceduresoutlinedbytheECUandexitwhenDdone.`6.:P00>>>boot%`C7.:$@SYS$SYSTEM:SHUTDOWN*`8.:P00>>>SET ARC_ENABLEOFF `A9.:P00>>> INITIALIZE`10.P00>>>GALAXY+`@11.ReboottheOpenVMSGalaxyWJOTherearetwoversionsoftheECU,onethatrunsonaKOgraphicsterminalandanotherthatrunson charactercellPO5 terminals.)Bothversionsareonthe diskette,andtheconsoleFO determineswhichonetorun.+ForOpenVMSGalaxysys-QOtems,theprimaryconsolewillalwaysbeaserialdevicewith'O>a charactercell terminal. MOIftheECUisnotrun,OpenVMSwilldisplaythe followingOmessage:Fza %SYSTEM-I-NOCONFIGDATA,&IRQ% Configuration&data%for&EISAJ  slot%xxx&was%not%found,&please%run%the&ECU%and%reboot. TOIfyouignorethismessage,thesystemwillboot,buttheplug-/OinEISAdeviceswillbeignored.IOOnceyouhave configuredandsetuptheOpenVMSGalaxyLOhardwareas describedinintheprevious sections,performHO5the followingstepstoinstallandbootOpenVMSGalaxyO instances. .-/0O5.3BStep3:'CreateASystemDiskBOUDecidewhethertouseasystemdiskperinstance RU orUtouseaOclustercommondiskNHOAnew SECURITY.EXEisrequiredforallclustermembersIOrunningaversionpriortoOpenVMSV7.2thatsharethe9O5sameVMS$OBJECTS.DATwithGalaxy instances. }/.0>O5.4BStep4:'InstallOpenVMSAlphaVersion7.2GOUNospecial installation proceduresarerequiredtorunDOOpenVMSGalaxy software..Galaxy functionalityisin-MOcludedinthebase operatingsystemandcanbeenabledorHO^disabledusingtheconsolecommandandsystem parameter6Ovalues describedlaterinthischapter.NHOFormore informationabout installingtheOpenVMSAlpha&O operatingsystem,seethe& OpenVMSAlphaVersion7.2,O5 Upgradeand InstallationManual "5.M\8O5.4.1BOpenVMSGalaxy Licensing Information O4See4Section4.1.*|? 2~  T'OTable5-1:7UsefulIntegers O Oh1 MegabytesKh0x100000O2 MegabytesK0x200000O[4 MegabytesK[0x400000O8 MegabytesK0x800000OO16 MegabytesKO0x1000000O32 MegabytesK0x2000000OB64 MegabytesKB0x4000000O128 MegabytesK0x8000000O6256 MegabytesK60x10000000O448 MegabytesK0x1C000000O)512 MegabytesK)0x20000000O1GigabyteK0x40000000O2 GigabytesK0x80000000O4 GigabytesK0x100000000O8 GigabytesK0x200000000O16 GigabytesK0x400000000O 32 GigabytesK 0x800000000O~ 64 GigabytesK~ 0x1000000000O 128 GigabytesK 0x2000000000Oq 256 GigabytesKq 0x4000000000O 512 GigabytesK 0x8000000000Oe 1TerabyteKe 0x10000000000 O   0/1)/O5.5BStep5:'UpgradetheFirmwareONotethattheOpenVMSGalaxyfirmware(GALAXY_GO FIRM_072.KIT)islocatedontheAlphaCD2forOpenVMSO5Version7.2.(OUsethe 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.NJOWhenthefirmwareupdatehas completed,youmustrebuildAOtheEEPROMformatoneach even-numbered processorO5moduleasfollows:O P00>>>%SET&CPUJ0O P00>>>%BUILD%-EOk P00>>>%SET&CPUJ2O P00>>>%BUILD%-E O . Od . O .O P00>>>INITKONotethataMOPbootableversionofthefirmwareupdate,-O #[GALAXY_FIRM_072.KIT]AS8_G53_27.SYS#j,isalsoontheCD. t103n D4O5.6BStep6:'Set Environment VariablesKOUWhenyouhaveupgradedthefirmwareonallofyourpro-IOcessormodules,youcancreatetheGalaxy-specificenvi-KOronment variablesasshowninthe followingexample.)ThisNO^exampleassumesyouare configuringa2 instance,8CPU,1>>%create&-nv%lp_count j< 2.O P00>>>%create&-nv% lp_cpu_mask01/O P00>>>%create&-nv% lp_cpu_mask1fe/O P00>>>%create&-nv% lp_io_mask0100.O\ P00>>>%create&-nv% lp_io_mask1805O P00>>>%create&-nv% lp_mem_size0100000005O P00>>>%create&-nv% lp_mem_size110000000;O3 P00>>>%create&-nv%lp_shared_mem_sizeK20000000O{ P00>>>%init NKOOnceyoucreatethese variables,youcanuseconsoleSETKOcommandsto manipulatethem.'These variablesneedonlybe$O5createdon processor0.pJOThe following descriptionsgivedetailed informationabout&Oeach environment variable. OLP_COUNTTO4Ifsettozero,thesystemwillboota traditionalSMPconfigu-8Orationonly.&GalaxyconsolemodeisOFF.q GROIfsettoanon-zerovalue,theGalaxyfeatureswillbeused,POandtheGalaxy variableswillbe interpreted.(TheexactvalueGO5ofLP_COUNT representsthenumberofGalaxy partitionsNOtheconsoleshouldexpect.( Currently,thisnumbermustbe0Oor2. WMONotethatifyouassign resourcesforthree partitionsandROsetthisvariabletotwo,the remaining resourceswillbeleftNO5 unassigned.' UnassignedCPUswillbeassignedto partition0.KOYoumayalsocreatethe variablesforthemaximumnumberROof partitionsaheadoftimeandsimplynotassign resourcestoAO>them(setthemtonon-zerovalues)untilneeded.(O LP_CPU_MASK partitionnumberIO4Thisbit-mask determineswhichCPUsaretobe initiallyGOassignedtothe specifiedGalaxy partitionnumber./TheHO AlphaServer8400consolechoosesthefirst even-numberedGO>CPUasitsprimary..Keepthisinmindwhen assigningMOthe resources(inotherwords,donotassignonlyanodd-+OnumberedCPUtoa partition).'O LP_IO_MASK partitionnumberLO4These variablesassignI/OmodulesbyslotnumbertoeachO instance. ` 8100 representstheI/Omoduleinslot8 `O 7O80 representstheI/Omoduleinslot7 ` 740 representstheI/Omoduleinslot6YJOThesearetheonlyvalid assignmentsforthe AlphaServerO8400. NOOYoucanassignmorethanoneI/Omoduletoaninstanceus-NOingthesemasks,buteachGalaxyinstancerequiresatleastO5oneI/Omodule. (O LP_MEM_SIZE partitionnumberLO4These variablesallocateaspecificamountofprivatemem-TOoryforthe specified instance.'Itis imperativethatyoucreateMOthese variablesusingpropervaluesfortheamountofmem-JO>oryinyoursystemandthedesired assignmentsforeachO instance.'RefertoTable5-1]forcommonvalues.*Ya? wMMOSeealsothesharedmemoryvariableonthe followingline.OLP_SHARED_MEM_SIZEJO4Thisvariable allocatesmemoryforuseassharedmemory.ORefertoTable5-1forcommonvalues. g]Tips gBSharedmemorymustbeassignedin multiplesof8D megabytesandallvaluesare expressedin hexadeci-Gmalbytes.EYoucandefineonlytheamountofsharedmemorytoCuse,andleavetheother lp_mem_size variablesun-Frdefined.+Thiswillcausetheconsoletoallocatethe?sharedmemoryfromthehighaddressspace,andB#splitthe remainingmemoryequallyamongthenum-J|berof partitions specifiedbythelp_count variable.(IfFyoualso explicitlyassignmemorytoaspecificpar-E-titionusinga lp_mem_size variable,butleaveotherB partitionmemory assignments undefined,theconsoleBwillagainassignthememory fragmentsforsharedD7memoryandany partitionswithexplicit assignments,Cthensplitandassignthe remainingmemorytoany> remaining partitionsnothavingexplicitmemory@ assignments. *Pa?  ! Wl3O bootdef_devand boot_osflags variablesRO4Youshouldsetthese variablesoneachofyourGalaxyconsolesKOpriortobootingtoensurethatAUTOGENreboots correctlyTOwhenitneedstorebootthesystemafteraninitial installationHO>andafterasystemcrashoroperator requestedreboot. 8O5.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>> ,O5.6.2BTableofUsefulIntegersO4Table5-194listscommonvaluesforGalaxy environmentJO variables.'Allvaluesare expressedin hexadecimalbytes.* Oe?  0314  (@O5.7BStep7:'Startthe SecondaryConsoleDevicesHO(IftheKFE72-DAwasever configuredfor Windows-NT,itROprobablyexpectstofindthevideoboardandwillhangifoneMOisnotpresent.'Thisisacommon occurrencewhen configur-KO1inganOpenVMSGalaxy.'Aconsolecommandcanbeusedto5Osetthemodeof operationasfollows:&O P00>>>%SET&CONSOLE%SERIALKOWhenyouissuethiscommandtotheprimaryconsolepriorMOto initializingthe secondary consoles,thesettingwillbe>>%SHOW%NETWORK)O P00>>>%SET& EWA0_MODE%TWISTED UMOThefirstcommanddisplaysalistof availablenetworkde-HOvices.+Thesecondcommand establishesthedefaultmediaMO5typeforthe specifieddevice(EWA0inthis example).*ThisUOshouldbedoneforallEthernetdevicespriorto initializingtheO secondary consoles.WHOOnceyouhavesetyourconsolemodeandnetworkmediaPOtypes(ifused)youshould re-initializethesystemtoensurePO5thatthecurrentsettingsaresaved.(Ifyouhavealreadyde-OOfinedyourGalaxy partitions,youcan initializenow.*IfyouKOhavenotdefinedyourGalaxy partitions,youshoulddefer'O>initializationuntillater.!YCOIfyouarereadyto initializethesystem,enter:O P00>>>%INITy! OLOYoushouldseetheprimaryconsolerespondwithitsusualMOpower-up-self-test(POST)report.'ThiscouldtakeuptotwoNO5minutes.)IfyouhaveproperlydefinedtheGalaxy partitions,ROonlytheI/Odevices associatedwiththeprimary partitionwillObevisible.@OToverifythat partitioninghas occurred,enter:O P00>>>%SHOW%DEVICE Oq orO P00>>>%SHOW%NETWORK|!R:OTo initializethe secondaryconsole,enter:O P00>>>%GALAXY1OTheconsoledisplaysthe 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>>>W5OThiscommandmustbeenteredfromthe< primaryGalaxyO consoleHD.)IftheGalaxy partitionshavebeenproperlydefined,JO5andhardware resourceshavebeenproperly configured,youNOshouldseetheprimaryconsolestartthe processorsassignedMOtoeach secondary partition.)Eachofthe secondaryconsoles:O>should initializewithinabouttwominutes.! NSOIfoneormoreconsolesfailsto initialize,youshoulddouble-OOcheckyourhardware installation,Galaxy partition definitions,%O5andhardware assignments.%O5.7.1BConsoleHintsMO4Becausethe AlphaServer8400wasbuiltpriortotheGalaxyEOSoftware Architecture,OpenVMSGalaxyconsolefirmwareJOandsystem operationsmustdealwithafew restrictions.QOThe followinglistbriefly describessomethingsyoushouldbeBOawareofandsomethingsyoushouldavoiddoing:] 3 ` Donotsetthe BOOT_RESET#2 environmentvariableto  1 .J(Thiscauseseach secondaryconsoletoresetthebusbe-Oforebooting,thus resettingall previouslybooted partitions.ARememberthatOpenVMSGalaxy partitionssharethe2 hardware. ` HBepatient.*Consoleinitialization,andsystem rebooting& cantakeseveralminutes. ` @ Donotattempttoabortafirmwareupdatepro- cess!S:bThiscanleaveyoursystem seriouslyhung. ` 4Whenupdatingconsole firmware,update ALLCPUs pat:thesametime. ]JbYoucannotruntwo differenttypesofCPUsortwodif-Nferentfirmware revisions.'Ifyoufailtoprovide consistentFfirmware revisions,thesystemwillhangon power-up. ` Neverissuethe  GALAXY%commandfroma secondaryKconsole.*Thiswill re-initializethesystem,andyouwill=Dneedtostartoverfromtheprimaryconsole. {4353O5.8BStep8:'BoottheOpenVMSGalaxyFOUWhenyouhave correctly installedtheGalaxyfirmwareOOand configuredthe consoles,youcanboottheinitialGalaxy#O environmentasfollows: &OForeachGalaxy instance:PO P00>>>%B%-FL%0,1&DKA100%//%or%whatever%your&boot%device&is."Oq SYSBOOT>%SET%GALAXY&1O SYSBOOT>%CONTINUEn DDOCongratulations!'YouhavecreatedanOpenVMSGalaxy. 546!h3O 6.@Creating(an(OpenVMS(Galaxy(on(anOr AlphaServer!8200HOThischapter describeshowtocreateanOpenVMSGalaxyO6.2.1B InstallingtheKFE72-DAConsole Subsystem<(HardwareJOTheKFE72-DAisthesetofEISA-busmodulesthatestab-LOlishesan additionalconsoleport.'OneKFE72-DAmoduleset2O=isrequiredper secondary partition.q2GGOTheKFE72-DAcontainsthreeEISAmodulesthatprovide:3 ` TwoCOMports `O  OAkeyboard interface ` Amouse interface `N NAsmallspeaker ` AnEthernetport.4NKOTheCOM-1portisusedfortheconsoleserialline.-ThePOEthernetportcanbeusedasanetwork connectionoritcanLO5be terminated.'Themouseandkeyboardportsarenotused.5! rJOTheKFE72-DAmustbepluggedintothebottomthreeEISAPOslots.(Forthe AlphaServer8200thisrequiresthatyouattachLO5aHosefromyourIO ProcessortoaDWLPBPCIcardcage.QOTheKFE72-DAmodulesetmustbe installedinslots0,1,andNO2ofthecardcage.)TheKFE72'sSIO(a.k.a.(Bridge)modulePO>enablestheEISAslotswhicharepartofthe combinationPCILO/EISA backplane.'Theothertwomodulesknownasthe"DataQOPortModule"and "Beeper97"goinslots1and2 respectively.N6 `$+O6.2.2BUsingaTerminalServerMO4YoumaywanttobringyourconsolelinestogetherusingaKOterminalserver.)Forexample,usea DECserver200toallowLO reverse-LATaccesstoeachconsoleoverthenetwork.'WhileNO=thisisnotstrictly required,itgreatly simplifiesOpenVMSIOGalaxy configuration management.(Refertothe appropriateJOproduct documentationfordetailsabout configuringaLAT4OGServerorotherterminal concentrator.7 ;O6.2.3BRecommendationsfor ConfiguringConsole<( SubsystemsJOEach additionalconsolerequiresaseparateKFE72-DAsub-NOsystem installedinaseparateDWLPBcardcagewithahoseMO= connectingittoaseparateIO ProcessoroftypeKFTIAorLOKFTHA.IfyouareusingaKFTIA,itmustbeinslot8.8NNO AdditionalKFTIAI/OmodulemustbeinthenextlowerslotNOorslots,withKFTHAI/OmoduleinthenextlowerslotorO5slotsafterthat.9HOYoucanuseany combinationofthesetwoIO ProcessorKOmodulesaslongasyoufollowthisslot assignmentrule.:NEOThe AlphaServer8200supportsamaximumofthreeIOGO Processors.. Attemptingto configuremorethanthreeisO5 unsupported.; kLOWhen configuringaconsole subsystem,theIOhoseconnect-LOingtheIO ProcessorandDWLPBcardcagemustbeplugged@O5intothelowesthoseport.)Notjustthelowest5 available5hoseXOport,buttheabsolutefirsthoseport;theoneclosesttothetopOofthemodule.<eIOKFE72-DAmodulesmustoccupyslots0,1,and2oftheODWLPBcardcage.= NLOTheconsoleseriallineis connectedwithanH8571-Jcon-ROnectoradapterthatplugsintotherighthandseriallineportLO5whenviewedfromtherearofthemachine.&ThisisCOM-1.N>V$*O6.2.4B InstallingEISADevicesNO4Plug-inEISAdevicescanonlybe configuredin partition0.OOAfter installingEISAdevices,theconsolewillissueames-MOsage requestingthatyouruntheEISA ConfigurationUtilityO=(ECU).O?%%ORuntheECUasfollows:@! YX:`1.:ShutdownallOpenVMSGalaxy instances.S`O2.:Besureyourfloppydiskdriveisproperly connectedtotheHprimary partitions hardware.( TypicallythedrivecanbeGcabledintothe ConnectorModule ("Beeper"partnumber)Y 54-25133-01)inPCIslot2.A`3.:Insertthediskette containingtheECUimage.K`W4.:Issuethe followingcommandsfromtheprimaryconsole:% P00>>>&SET% ARC_ENABLE&ON$ P00>>>& INITIALIZEl P00>>>&RUNECUN`5.:Followthe proceduresoutlinedbytheECUandexitwhenDdone.`6.:P00>>>boot%`C7.:$@SYS$SYSTEM:SHUTDOWN*`8.:P00>>>SET ARC_ENABLEOFF `A9.:P00>>> INITIALIZE`10.P00>>>GALAXY+`@11.ReboottheOpenVMSGalaxyAWJOTherearetwoversionsoftheECU,onethatrunsonaKOgraphicsterminalandanotherthatrunson charactercellPO5 terminals.)Bothversionsareonthe diskette,andtheconsoleFO determineswhichonetorun.+ForOpenVMSGalaxysys-QOtems,theprimaryconsolewillalwaysbeaserialdevicewith'O>a charactercell terminal.B MOIftheECUisnotrun,OpenVMSwilldisplaythe followingOmessage:Fza %SYSTEM-I-NOCONFIGDATA,&IRQ% Configuration&data%for&EISAJ  slot%xxx&was%not%found,&please%run%the&ECU%and%reboot.C TOIfyouignorethismessage,thesystemwillboot,buttheplug-/OinEISAdeviceswillbeignored.DIOOnceyouhave configuredandsetuptheOpenVMSGalaxyLOhardwareas describedinintheprevious sections,performHO5the followingstepstoinstallandbootOpenVMSGalaxyO instances. 879E0O6.3BStep3:'CreateASystemDiskBOUDecidewhethertouseasystemdiskperinstance RU orUtouseaOclustercommondiskFNHOAnew SECURITY.EXEisrequiredforallclustermembersIOrunningaversionpriortoOpenVMSV7.2thatsharethe9O5sameVMS$OBJECTS.DATwithGalaxy instances. I98:G>O6.4BStep4:'InstallOpenVMSAlphaVersion7.2GOUNospecial installation proceduresarerequiredtorunDOOpenVMSGalaxy software..Galaxy functionalityisin-MOcludedinthebase operatingsystemandcanbeenabledorHO^disabledusingtheconsolecommandandsystem parameter6Ovalues describedlaterinthischapter.HNHOFormore informationabout installingtheOpenVMSAlpha&O operatingsystem,seethe& OpenVMSAlphaVersion7.2,O5 Upgradeand InstallationManual "5.|IMR8O6.4.1BOpenVMSGalaxy Licensing InformationO4 SeeChapter4. <c _2OTable6-1:7TableofUsefulIntegers O Oh1 MegabytesKh0x100000O2 MegabytesK0x200000O[4 MegabytesK[0x400000O8 MegabytesK0x800000OO16 MegabytesKO0x1000000O32 MegabytesK0x2000000OB64 MegabytesKB0x4000000O128 MegabytesK0x8000000O6256 MegabytesK60x10000000O448 MegabytesK0x1C000000O)512 MegabytesK)0x20000000O1GigabyteK0x40000000O2 GigabytesK0x80000000O4 GigabytesK0x100000000O8 GigabytesK0x200000000O16 GigabytesK0x400000000O 32 GigabytesK 0x800000000O~ 64 GigabytesK~ 0x1000000000O 128 GigabytesK 0x2000000000Oq 256 GigabytesKq 0x4000000000O 512 GigabytesK 0x8000000000Oe 1TerabyteKe 0x10000000000 O   :9;J)/O6.5BStep5:'UpgradetheFirmwareONotethattheOpenVMSGalaxyfirmware(GALAXY_GO FIRM_072.KIT)islocatedontheAlphaCD2forOpenVMSO5Version7.2.O(OUsethe 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.NJOWhenthefirmwareupdatehas completed,youmustrebuildAOtheEEPROMformatoneach even-numbered processorO5moduleasfollows:O P00>>>%SET&CPUJ0O P00>>>%BUILD%-EOk P00>>>%SET&CPUJ2O P00>>>%BUILD%-E O . Od . O .O P00>>>INITQKONotethataMOPbootableversionofthefirmwareupdate,.O $[GALAXY_FIRM_072.KIT]AS8_G52-101.SYS#,isalsoontheCD. M;:=nR D4O6.6BStep6:'Set Environment VariablesKOUWhenyouhaveupgradedthefirmwareonallofyourpro-IOcessormodules,youcancreatetheGalaxy-specificenvi-KOronment variablesasshowninthe followingexample.)ThisNO^exampleassumesyouare configuringa2 instance,8CPU,1>>%create&-nv%lp_count j< 2.O P00>>>%create&-nv% lp_cpu_mask01/O P00>>>%create&-nv% lp_cpu_mask1fe/O P00>>>%create&-nv% lp_io_mask0100.O\ P00>>>%create&-nv% lp_io_mask1805O P00>>>%create&-nv% lp_mem_size0100000005O P00>>>%create&-nv% lp_mem_size110000000;O3 P00>>>%create&-nv%lp_shared_mem_sizeK20000000O{ P00>>>%initSNNOOncethese variableshavebeencreated,youcanuseconsoleFOSETcommandsto manipulatethem.*These variablesneed9O5onlybecreatedon processor0asshown.TpJOThe following descriptionsgivedetailed informationabout&Oeach environment variable.U OLP_COUNTTO4Ifsettozero,thesystemwillboota traditionalSMPconfigu-8Orationonly.&GalaxyconsolemodeisOFF.yV OROIfsettoanon-zerovalue,theGalaxyfeatureswillbeused,POandtheGalaxy variableswillbe interpreted.(Theexactvalue O5of5 lp_count>*5 representsthenumberofGalaxy partitionstheQOconsoleshouldexpect.' Currently,thisnumbermustbe0or2.WWMONotethatifyouassign resourcesforthree partitionsandROsetthisvariabletotwo,the remaining resourceswillbeleftMO5 unassigned.(Youmayalsocreatethe variablesforthemax-IOimumnumberof partitionsaheadoftimeandsimplynotOOassign resourcestothem(setthemtonon-zerovalues)untilO>needed.X(O LP_CPU_MASK partitionnumberIO4Thisbit-mask determineswhichCPUsaretobe initiallyGOassignedtothe specifiedGalaxy partitionnumber./TheHO AlphaServer8200consolechoosesthefirst even-numberedGO>CPUasitsprimary..Keepthisinmindwhen assigningMOthe resources(inotherwords,donotassignonlyanodd-+OnumberedCPUtoa partition).Y'O LP_IO_MASK partitionnumberNO4These variablesassignIO processorsbyslotnumbertoeachO instance.Z ` 8100 representstheI/Omoduleinslot8 `O 7O80 representstheI/Omoduleinslot7 ` 740 representstheI/Omoduleinslot6[YJOThesearetheonlyvalid assignmentsforthe AlphaServerO8200.\ NOOYoucanassignmorethanoneI/Omoduletoaninstanceus-NOingthesemasks,buteachGalaxyinstancerequiresatleastO5oneI/Omodule.] (O LP_MEM_SIZE partitionnumberLO4These variablesallocateaspecificamountofprivatemem-TOoryforthe specified instance.'Itis imperativethatyoucreateMOthese variablesusingpropervaluesfortheamountofmem-JO>oryinyoursystemandthedesired assignmentsforeachO instance.'RefertoTable6-1]forcommonvalues.*]Ya?cw^MMOSeealsothesharedmemoryvariableonthe followingline._OLP_SHARED_MEM_SIZEJO4Thisvariable allocatesmemoryforuseassharedmemory.ORefertoTable6-1forcommonvalues. g]Tips gBSharedmemorymustbeassignedin multiplesof8D megabytesandallvaluesare expressedin hexadeci-Gmalbytes.EYoucandefineonlytheamountofsharedmemorytoCuse,andleavetheother lp_mem_size variablesun-Frdefined.+Thiswillcausetheconsoletoallocatethe?sharedmemoryfromthehighaddressspace,andB#splitthe remainingmemoryequallyamongthenum-J|berof partitions specifiedbythelp_count variable.(IfFyoualso explicitlyassignmemorytoaspecificpar-E-titionusinga lp_mem_size variable,butleaveotherB partitionmemory assignments undefined,theconsoleBwillagainassignthememory fragmentsforsharedD7memoryandany partitionswithexplicit assignments,Cthensplitandassignthe remainingmemorytoany> remaining partitionsnothavingexplicitmemory@ assignments. *_Pa?c`! dO bootdef_devO boot_osflagsROYoushouldsetthese variablesoneachofyourGalaxyconsolesKOpriortobootingtoensurethatAUTOGENreboots correctlyTO3whenitneedstorebootthesystemafteraninitial installationHOandafterasystemcrashoroperator requestedreboot.a8O6.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!O6.6.2BUsefulIntegersO4Table6-194listscommonvaluesforGalaxy environmentJO variables.'Allvaluesare expressedin hexadecimalbytes.*bOe?c =;>d (@O6.7BStep7:'Startthe SecondaryConsoleDevicesHO(IftheKFE72-DAwasever configuredfor Windows-NT,itROprobablyexpectstofindthevideoboardandwillhangifoneMOisnotpresent.'Thisisacommon occurrencewhen configur-KO1inganOpenVMSGalaxy.'Aconsolecommandcanbeusedto5Osetthemodeof operationasfollows:&O P00>>>%SET&CONSOLE%SERIALeKOWhenyouissuethiscommandtotheprimaryconsolepriorMOto initializingthe secondary consoles,thesettingwillbe>>%SHOW%NETWORK)O P00>>>%SET& EWA0_MODE%TWISTEDg UMOThefirstcommanddisplaysalistof availablenetworkde-HOvices.+Thesecondcommand establishesthedefaultmediaMO5typeforthe specifieddevice(EWA0inthis example).*ThisUOshouldbedoneforallEthernetdevicespriorto initializingtheO secondary consoles.hWHOOnceyouhavesetyourconsolemodeandnetworkmediaPOtypes(ifused)youshould re-initializethesystemtoensurePO5thatthecurrentsettingsaresaved.(Ifyouhavealreadyde-OOfinedyourGalaxy partitions,youcan initializenow.*IfyouKOhavenotdefinedyourGalaxy partitions,youshoulddefer'O>initializationuntillater.i!YCOIfyouarereadyto initializethesystem,enter:O P00>>>%INITyj! OLOYoushouldseetheprimaryconsolerespondwithitsusualMOpower-up-self-test(POST)report.'ThiscouldtakeuptotwoNO5minutes.)IfyouhaveproperlydefinedtheGalaxy partitions,ROonlytheI/Odevices associatedwiththeprimary partitionwillObevisible.k@OToverifythat partitioninghas occurred,enter:O P00>>>%SHOW%DEVICE Oq orO P00>>>%SHOW%NETWORK|l!R:OTo initializethe secondaryconsole,enter:O P00>>>%GALAXYm1OTheconsoledisplaysthe 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>>>nW5OThiscommandmustbeenteredfromthe< primaryGalaxyO consoleHD.)IftheGalaxy partitionshavebeenproperlydefined,JO5andhardware resourceshavebeenproperly configured,youNOshouldseetheprimaryconsolestartthe processorsassignedMOtoeach secondary partition.)Eachofthe secondaryconsoles:O>should initializewithinabouttwominutes.o! NSOIfoneormoreconsolesfailsto initialize,youshoulddouble-OOcheckyourhardware installation,Galaxy partition definitions,%O5andhardware assignments.%pO6.7.1BConsoleHintsMO4Becausethe AlphaServer8200wasbuiltpriortotheGalaxyEOSoftware Architecture,OpenVMSGalaxyconsolefirmwareJOandsystem operationsmustdealwithafew restrictions.qQOThe followinglistbriefly describessomethingsyoushouldbeBOawareofandsomethingsyoushouldavoiddoing:r # ` Donotsetthe BOOT_RESET#2 environmentvariableto  1 .J(Thiscauseseach secondaryconsoletoresetthebusbe-Oforebooting,thus resettingall previouslybooted partitions.ARememberthatOpenVMSGalaxy partitionssharethe2 hardware. ` ,The AlphaServer8200detectsae Ctrl/Pkkeysequenceon1 theprimaryconsoleusing hardware.s H)b ThiswillgoawayforSSB:)bIfyouenterCtrl/PontheJprimaryconsole,ALLconsoleswillhalt.*Ifyoudidnot<intendtodothis,youcanusuallyissuea CONTINUEBlcommandtogetthe operatingsystemrunningagainC(yourchancesof successfully continuingdependsonGwhatisrunningonthesystemandhowlongyouhaveLvbeenhalted).(Youshouldbeableto independentlyissueaG Control-Pkeysequencetoany secondaryinstancewith-F'out impactinganyother instances.( Secondary Control-P>key sequencesarehandledbyconsole firmware. ` JGivetheprocesstime.)Consoleinitialization,andsystem1W rebootingcantakeseveralminutes. ` @ Donotattempttoabortafirmwareupdatepro-/ cess!tS:bThiscanleaveyoursystem seriouslyhung. ` 4Whenupdatingconsole firmware,update ALLCPUs pat:thesametime.u ]JbYoucannotruntwo differenttypesofCPUsortwodif-Nferentfirmware revisions.'Ifyoufailtoprovide consistentFfirmware revisions,thesystemwillhangon power-up. ` Neverissuethe  GALAXY%commandfroma secondaryKconsole.*Thiswill re-initializethesystem,andyouwill=Dneedtostartoverfromtheprimaryconsole. {>=?v3O6.8BStep8:'BoottheOpenVMSGalaxyFOUWhenyouhave correctly installedtheGalaxyfirmwareOOand configuredthe consoles,youcanboottheinitialGalaxy#O environmentasfollows:w &OForeachGalaxy instance:PO P00>>>%B%-FL%0,1&DKA100%//%or%whatever%your&boot%device&is."Oq SYSBOOT>%SET%GALAXY&1O SYSBOOT>%CONTINUEnxDDOCongratulations!'YouhavecreatedanOpenVMSGalaxy. H?>@.y 3O 7.@Creating(an(OpenVMS(Galaxy(on(an#Or AlphaServer!4100!SystemKOThischapter describesthe requirementsand proceduresforGOOcreatinganOpenVMSGalaxy computing environmentonanO AlphaServer4100. @?Aznm!O7.1BBeforeYouStartLOUBesuretoreadtheReleaseNoteschapterinthisguide.{ NJOTocreateanOpenVMSGalaxyonan AlphaServer4100,youLOmustalsobefamiliarwiththe following configurationand!O5hardware requirements:|O Two-instancemaximumHO4Youcanrunamaximumoftwo instancesofOpenVMSon Oan AlphaServer4100.}OConsolefirmwareHO4Youmusthave AlphaServer4100consolefirmwareVersion6O AS4_G52-59 (AvailableontheV7.2kit).~OConsolecommands3O4Inadditiontotheconsolehintsin4Chapter5,4youshouldbe$Oawareofthe following:*~nO ` CEnterconsolecommandsononeinstanceatatime. `O HODonotenterconsolecommandsatanotherconsoleuntilIthecommandenteredatthefirstconsolehas completed. s"O AlphaServer4100clockCO4An AlphaServer4100hasoneclock./ForanOpenVMSKOGalaxy,thismeansthatyoucannotrunthetwo instancesHOat differenttimes.,Also,theSETTIMEcommandaffectsQO>both instances.'Notethatthismaynotbecomeevidentuntila*Onumberofhourshavepassed.OConsoleportsBO4COM1(upper)istheconsoleportforinstance0.BOCOM2(lower)istheconsoleportforinstance1.NDOUnlikecreatinganOpenVMSGalaxyonan AlphaServerKO8400,youdonotneed additionalhardwareforthesecond8O5console.'COM-2isusedforthispurpose.WOCPUs9O4CPU0mustbetheprimaryforinstance0.9OCPU1mustbetheprimaryforinstance1.HOCPUs2and3areoptional secondaryCPUsthatcanbeO> migrated.%WOI/OadaptersNO4ThefourlowerPCIslotsbelongtoIOD0,whichistheI/O$Oadapterforinstance0.NOThefourupperPCIslotsbelongtoIOD1,whichistheI/O$O>adapterforinstance1.K W!OStorage controllersOO4Youwillneedtwostorage controllers,suchasKZPSAs.'TheseQOcangotoseparate StorageworksboxesortothesameboxforOOrunningasaSCSIcluster.(One controllereachgoesinIOD0O>andIOD1. ONetworkcardsNO4Ifeachinstanceneedsnetworkaccess,anetworkcard(such;OasaDE500)isrequiredforeach instance._55OOnecardeachgoesinIOD0andIOD1.fW<OPhysicalmemoryHO4BecauseOpenVMSGalaxyonan AlphaServer4100doesnotEOsupportmemoryholes,physicalmemoryforanOpenVMSKOGalaxy environmentmustbe contiguous.)ToachievethisonJO>an AlphaServer4100,oneofthe followingmustbetrue:8!  ` IAllmemorymodulesmustbethesamesize(forexample,(1GB). ` OIftwosizesarepresent,onlyonemodulecanbeasmallerOsize.'Youmustputthelargermodulesintothelowerslots. -A"@BO7.2B ProceduresDOUTocreateanOpenVMSGalaxyonan AlphaServer41002Osystem,performthe followingsteps:=`1.:UsetheSHOWCONFIGcommandtomakesureG(thatthe AlphaServer4100youareusingtocreatean@OpenVMSGalaxy environmentmeetsthe requirements describedinSection7.1.*|?z`DbAttheconsoleprompt,enterthe followingcommand: P00>>>show&config 3a>bTheconsoledisplaysthe following information:X Console%G52-59KOpenVMS%PALcode% V1.19-16,%Digital%UNIX&PALcode%V1.21-24P ModuleP TypeRevName System& Motherboard  0 0000pmthrbrd0 MemoryK512%MB%EDO  0 0000pmem0( MemoryK256%MB%EDO ( 0( 0000pmem1p CPU& (Uncached) p 0p 0000pcpu0 CPU& (Uncached)  0 0000pcpu1 Bridge& (IOD0/IOD1) 6000021p iod0/iod1H PCI& Motherboard H 8H 0000psaddle0 CPU& (Uncached)  0 0000pcpu2 CPU& (Uncached)  0 0001pcpu3A Bus&0Kiod0%(PCI0) SlotpOption%Name TypeRevName 1PCEB 4828086K0005ppceb0 4DEC%KZPSA 810110000ppks1a 5DECchip%21040-AAa 210110023ptulip1F Bus&1Kpceb0&(EISA&Bridge% connected%to%iod0,%slot%1) SlotpOption%Name TypeRevName{ Bus&0Kiod1%(PCI1) SlotpOption%Name TypeRevName  1NCR%53C810  110000002pncr0S 2DECchip%21040-AAS 210110024ptulip0 3DEC%KZPSA 810110000ppks04`2.:InstallOpenVMSAlphaVersion7.2.VGbNospecial installation proceduresarerequiredtorun?OpenVMSGalaxy software..Galaxy functionalityisGincludedinthebase operatingsystemandcanbeen-HlabledordisabledusingtheconsolecommandandsystemA parametervalues describedlaterinthischapter.,KbIfyour AlphaServer4100isnotpartofaSCSIcluster,DyoumustinstallOpenVMSVersion7.2ontwosystem/ disks-onediskforeach instance. ,KbIfyour AlphaServer4100ispartofaSCSIclusterwithEacluster-commonsystemdisk,installOpenVMSVersion%7.2ononesystemdisk.AbFormore informationabout installingtheOpenVMS-Alpha operatingsystem,seethe!X OpenVMSAlphaVersion0 7.2Upgradeand InstallationGuide .J`3.:Toupgradethe firmware,copythefirmwarefileAS4_8 G52-59.SYSto MOM$SYSTEMona MOP-enabledJDserverthatis accessibletothe AlphaServer4100.)Enter5the followingcommandsontheconsole: ,b NEEDTOADDTHECD PROCEDURE.7 P00>>>%boot%-fl%0,0&ewa0%-fi& as4_g52-59/ UPD>&update%srm*w A`4.: Configuretheprimaryconsoleforinstance0.]{33bCPU0istheprimaryforinstance0.,EbCreatetheGalaxy environment variables.)Fordescrip-EtionsoftheGalaxy environment variablesandcommon'valuesforthem,refertoUChapter5.*UlO! GbThe followingexampleisforan AlphaServer4100withGthreeCPUsand512MBofmemorydividedinto256MB +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&haltmJbIfyouhavefourCPUsandyouwanttoassignallsec-EondaryCPUstoinstance1,the lp_cpu_mask1variablewillbe  EA .IfyousplittheCPUsbetweenboth instances,HlCPU0mustbetheprimaryforinstance0,andCPU18mustbetheprimaryCPUforinstance1. bThezb mem_size4*b variablesdependonyour configuration1andhowyouwanttosplititup.A`0Ygalaxy_io_mask0mustbesetto100Y(galaxy_io_mask1mustbesetto20 *=bYoumustsettheconsole environmentvariableb AUTO_ ACTION@CtoHALT.ThiswillensurethatthesystemdoesKnotbootandthatyouwillbeabletoentertheGalaxylcommand.L`5.: InitializethesystemandstarttheGalaxyfirmwareby-Denteringthe following commands: P00>>>%init P00>>>%galaxyvGbAfterthe self-test completes,theGalaxycommandwill/starttheconsoleoninstance1. JbThefirsttimethattheGalaxystarts,itmightdisplay2severalmessageslikethe following: @ CPU0&would&not%joinC IOD0&and%IOD1&did%not%pass%the%power-up% self-test,EbThishappensbecausetherearetwosetsofenviron-$ment variables,andthe9 galaxy&N variablesarenotpresent% initiallyoninstance1.6~IbNotethatwhentheI/ObusisdividedbetweenthetwoFGalaxy partitions,theportletterofadevicemightAchange.-Forexample,adisk designatedasDKC300Ilwhenthe AlphaServer4100isasinglesystemcouldbe-KcomeDKA300whenitis configuredas partition0oftheOpenVMSGalaxy.! SNbItisbesttowaitfortheP01>>>promptonthe secondaryGconsolebefore attemptingtoboottheprimaryconsole.8`:6.: Configuretheconsoleforinstance1.5 HbUsethesamecommandsfromstep2tocreatethesame)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*1DbWhentheconsoledisplaysthe following confirmationprompt,typeY:>@ Do%you%REALLY&want%to%reset%the&Galaxy%(Y/N)O`8.: Configurethesystemroot,bootdevice,andotherrelated variables.dV :CbThe 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! PbIfyoubuildaSCSIcluster,makesuretosetupyourSCSI7adapterhostIDs 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>>>%bootKbOnceinstance1isbooted,logintothesystemaccount<andedittheSYS$SYSTEM:MODPARAMS.DATfileto-includethethe followingline: GALAXY=1fJbConfirmthatthelinesfortheSCSnodeandSCSsystemEIDarecorrect.*RunAUTOGENasfollowsto configureFinstance1asaGalaxymember,andleavethesystemlhalted:< $&@SYS$UPDATE:AUTOGEN%GETDATA%SHUTDOWN%INITIAL.`p10.Bootinstance0asfollows: P00>>>%bootKbOnceinstance0isbooted,logintothesystemaccount<andedittheSYS$SYSTEM:MODPARAMS.DATfileto(includethe followingline:" Add%the&line%GALAXY=1JbConfirmthatthelinesfortheSCSnodeandSCSsystemEIDarecorrect.*RunAUTOGENasfollowsto configureFinstance0asaGalaxymember,andleavethesystemlhalted:< $&@SYS$UPDATE:AUTOGEN%GETDATA%SHUTDOWN%INITIALL`p11.PreparetheGalaxytocomeup automaticallyuponini-J tializationorpowercycleofthesystem.)SettheAUTO_@!ACTION environmentvariableonboth instancestozRESTART.+ P00>>>%set& auto_action&restart+h P01>>>%set& auto_action&restartK`12. InitializetheGalaxyagainbyenteringthe following.@commandsattheprimaryconsole: P00>>>%initYDbWhentheconsoledisplaysthe following confirmationprompt,typeY:>@ Do%you%REALLY&want%to%reset%the&Galaxy%(Y/N) ,EbAlternatively,youcould power-cycleyoursystem,andItheGalaxywithboth instancesshould bootstrapautomat-ically.nDDOCongratulations!'YouhavecreatedanOpenVMSGalaxy. B AC {s8O 8.:Using&a&Single-Instance&Galaxy%on&AnyOrAlpha!SystemHOWithOpenVMSAlphaVersion7.2,youcanrunasingle-GOOinstanceGalaxyonanyAlpha platform.-This capabilityKOallowsearlyadopterstoevaluateOpenVMSGalaxy features,GOandmost importantly,todevelopandtest Galaxy-awareLOY applicationswithout incurringtheexpenseofsettingupaJO full-scaleGalaxy computing environmentonasystemcapa-LO bleofrunningmultiple instancesofOpenVMS(forexample,!Oban AlphaServer8400). ! NOAsingle-instanceGalaxyrunningonanyAlphasystemisnotLOan emulator.'ItisOpenVMSGalaxycodewithGalaxyinter-LO5facesand underlying operatingsystem functions.(AllGalaxyLOAPIsarepresentinasingle-instanceGalaxy(forexample,HOresource management,sharedmemoryaccess,eventnotifi-KO>cation,lockingforsynchronization,andsharedmemoryforOglobal sections). anOOAny applicationrunonasingle-instanceGalaxywillexerciseNOtheexactsame operatingsystemcodeonamultipleinstanceMO5Galaxysystem.(Thisis accomplishedbycreatingtheconfig-@OurationfileSYS$SYSTEM:GLX$GCT.BIN,whichOpenVMSGOreadsintomemory.,OnaGalaxyplatform(forexample,LO> AlphaServer8400),theconsoleplaces configurationdatainHOmemoryforOpenVMStouse.)Oncethe configurationdataNOisinmemory, regardlessofitsorigin,OpenVMSbootsasaOHGalaxy instance.NOTousetheGalaxy ConfigurationUtilitytocreateasingle-3OinstanceGalaxyonanyAlphaSystem:~HORuntheGCUontheOpenVMSAlphasystemonwhichyou6Owanttousethesingle-instanceGalaxy.NMOIftheGCUisrunona non-Galaxysystem,itwillpromptMOastowhetheryouwanttocreateasingle-instanceGalaxy.O5Clickon 5 OK.! WKOTheGCUnextpromptsfortheamountofmemorytodesig-QOnateassharedmemory.'EnteranyvaluethatisamultipleofPO58 megabytes.'Notethatyoumustspecifyatleast8 megabytesOOofsharedmemoryifyouwanttobootasaGalaxy instance.HOThismeanstheminimumGalaxymemory requirementis72O> megabytes.kMOWhentheGCUhas displayedtheconfiguration,itwillhaveIOalreadywrittenthefile GLX$GCT.BINtothecurrentdi-PO5rectory.(YoumayexittheGCUatthispoint.(IfyoumadeaQOmistakeorwanttoaltertheconfiguration,youcanclosethe4Ocurrentmodelandrepeattheprocess.e;;OTorebootthesystemasaGalaxy instance:KQ 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>CONTINUEc99O Consoleoutputmessageistobe supplied. vCBD\22OPartIII7ManagingAnOpenVMSGalaxy D CEM#5O 9.2OpenVMS!Galaxy! Configuration"UtilityGOTheGalaxy ConfigurationUtility(GCU)isa DECwindowsKOMotif applicationthatallowssystemmanagersto configureKOBandmanagetheirGalaxysystemsfromasingle workstationOwindow.\22OUsingtheGCU,systemmanagerscan:T l* ` 6DisplaytheactiveGalaxyconfiguration. `O 8OReassign resourcesamongGalaxy instances. ` 3Viewresource-specificcharacteristics. `N CNShutdownorrebootoneormoreGalaxy instances. ` 0Invoke additional managementtools. `L @LEvaluaterun-time performanceandresourceusage. ` =CreateandengageGalaxy configurationmodels. `K DKCreateasingle-instanceGalaxyonanyAlphasystem?(forsoftware developmenton non-Galaxyhardware platforms). `{ 3{ViewtheonlineGalaxydocumentation. ` G Determinehot-swapcharacteristicsofthecurrenthard-Sware platform.NCOTheGCUresidesintheSYS$SYSTEM[SYSMGR] directoryMOalongwithasmallnumberoffiles containing configurationO5 knowledge.b88OTheGCUconsistsofthe followingfiles:OSYS$SYSTEM:GCU.EXE GCU executableimageO]SYS$MANAGER:GCU.DAT]Optional DECwindowsresourcefile O$SYS$MANAGER:GALAXY.GCR$Galaxy ConfigurationqRuleset9OSYS$MANAGER:GCU$ACTIONS.COMSystem management8 proceduresO SYS$MANAGER: t xxx.GCM  User-definedconfigu-rationmodels;OzSYS$HELP:GALAXY_GUIDE.DECW$BOOKPOnlinehelpin Bookreaderform! tMOTheGCUis typicallyrunfromtheprimaryGalaxy instance.POIfthesystemdoesnotdirectlysupportgraphicsoutput,thenLO5the DECwindowsdisplaycanbesettoanexternalworksta-NOtionorsuitably configuredPC.However,theGCU application=OitselfmustalwaysrunontheGalaxysystem.W! -MOWhentheGCUisstarted,itloadsanycustomizationsfoundKOinitsresourcefile (GCU.DAT);thenitloadstheGalaxyIO5 ConfigurationRuleset (GALAXY.GCR).Therulesetfilecon-JOtains statementsthat determinethewaytheGCUdisplaysGOthevarioussystem components,andincludesrulesthatMO>governthewaysinwhichuserscaninteractwiththecon-NO figurationdisplay.+Usersdonot typicallyaltertherulesetQOfileunlesstheyarewellversedinits structureoraredi-LOHrectedtodosobyaCompaqServices Engineer.+AftertheHOGCUdisplaybecomesvisible,theGCU determineswhetherIOthesystemis currently configuredasanOpenVMSGalaxyNORorasasingle-instanceGalaxyonanyAlphasystem.)IftheQOsystemis configuredasaGalaxy,theGCUdisplaystheactiveGOGalaxy configurationmodel.)Themain observationwindowLO[displaysa hierarchicalviewoftheGalaxy.,IfthesystemLOhasnotyetbeen configuredasaGalaxy,theGCUpromptsPO youastowhetherornottocreateasingle-instanceGalaxy.KOeNotethattheGCUcancreateasingle-instanceGalaxyonFOanyAlphasystem,butmultiple-instanceOpenVMSGalaxyGO environmentsarecreatedbyusingconsolecommandsandLOofirmware functionsas described elsewhereinthis document.`6MOOncetheGalaxy configurationmodelis displayed,userscanOOeitherinteractwiththeactivemodelortakethemodeloffLO5lineanddefinespecificconfigurationsforlateruse.-TheNO followingsectionsdiscussthese functionsingreaterdetail. dFEG< processor.)TheGCUisawareofthis requirement,andwillJOattempttouseoneormorecommunicationspathstosendMOthe reassignmentrequesttotheowner instance.)DCLisnotMOH inherentlyawareofthis requirement; therefore,ifyouuseMODCLtoreassign resources,youwillneedtouseSYSMANorJOa separately logged-interminaltoissuethecommandsonORtheowner instance. WFOTheGCUfavorsusingSYSMAN,andits underlyingSMI_MOServer processestoprovidecommandpathstotheotherin-HO5stancesintheGalaxy.+However,the SMI_ServerrequiresQOthatthe instancesbeinaclustersothatthecommandenvi-HOronmentfallswithinacommonsecuritydomain.)However,7O>Galaxy instancesmightnotbe clustered. WFOIfthesystemcannotprovideasuitablecommandpathJOforthe SMI_Servertouse,theGCUwillattempttouseEO5DECnet task-to-taskcommunications.+ThisrequiresthatNOthe participating instancesberunningDECnet,andthateachLO participatingGalaxyinstancehaveaproxysetupfortheO>SYSTEMaccount.WPOItispossibleforaninstancetonotbe clustered,havenoKOproxyaccount established,andnothaveDECnet capability.IO5Theseare consideredisolatedinstancefroma managementIO perspective.,Theonlywaytoreassign resourcesfromanSOisolatedinstanceistobeloggedintoitsconsole.*(Formore7O> informationaboutisolated instances,see>Section9.2.1.)*?'O9.2.1B Independent InstancesIO4Youcan partitionaGalaxysystemsothatoneormoreFO partitionsarebootedwithoutbecomingmembersoftheFOGalaxysharing community.)Theseareknownasindepen-JO=dent instances.+Because independent instancesresideinaMOGalaxy partition,theirpresenceis reflectedintheGalaxyFO ConfigurationFile,andtheyarevisibletotheGCU.NKOThese independenttheycanstill participateinCPUreas-GO signment.+TheycannotutilizesharedmemoryorrelatedO5 services.7!  NOYoucancreatea partitionthathasnoEthernetdeviceandPOisnotamemberofaclusteroroftheGalaxysharingcom-(O5munity.)Theseareknownas~5 isolated instancesT5.)BecauseUOtheyresideinaGalaxy partition,theyarestillvisibletotheKOGCUandyoucanreassignCPUstothem.'ToreassignCPUsPO>awayfromisolated instances,youmustlogintotheconsole&Ooftheisolated instance.k `A(O9.2.2BRequiredPROXYAccessHO4WhentheGCUneedstoexecutea managementaction,itIOalwaysattemptstousetheSYSMANutilityfirst.)SYSMANSOrequiresthattheinvolved instancesbeinthesamecluster.'IfSO=thisisnotthecase,theGCUwillnextattempttouseDECnetGO task-to-taskcommunications.-Forthistowork,thein-LOvolved instancesmusteachhaveanEthernetdevice,DECnetOOG capability,andsuitableproxyaccessonthetarget instance. KOForexample,considera two-instance configurationthatisMOnot clustered.)Ifinstance0wererunningtheGCUandtheOO5userattemptstoreassignaCPUfrominstance1toinstanceHO0,theactual reassignmentcommandmustbeexecutedonTOinstance1.'Todothis,theGCU'saction proceduresinthefile=O>SYS$MANAGER:GCU$ACTIONS.COMwillattempttoes-GOtablishaDECnet task-to-task connectiontotheSYSTEMKOaccountoninstance1.,Thisrequiresthatinstance1hasHOHgrantedproxyaccesstotheSYSTEMaccountofinstanceNO0.(Usingthe established connection,theaction procedureonOOinstance0willpassits parameterstothe equivalentactionPOR procedureoninstance1,whichnowtreatsthe operationasaOlocal operation.dJOTheGCUaction proceduresassumethattheywillbeusedLObythesystemmanager.*Thus,intheaction procedurefile8O5SYS$MANAGER:GCU$ACTIONS.COM,theSYSTEMac-KOcountisused..Tograntaccesstotheopposite instancesKOSYSTEMaccount,theproxymustbesetuponinstance1.Q''OTo establishproxyaccess:! `D`1.:Enterthe followingcommandsattheDCLprompt:%U $&SET%DEFAULT& SYS$SYSTEM $&RUN% AUTHORIZEU`2.:Ifproxy processingisnotyetenabled,enableitbyentering#uthe following commands: UAF>& CREATE/PROXY4A UAF>&ADD%PROXY%instance::SYSTEM&SYSTEM UAF>&EXIT! kOReplace instance<withthenameoftheinstancetowhichyouPOaregrantingaccess.(Performthesestepsforeachofthein-MO5stancesyouwanttomanagefromtheinstanceonwhichyouNOruntheGCU.Forexample,inatypical two-instanceGalaxy,ROifyouruntheGCUonlyoninstance0,thenyouneedtoaddOO>proxyaccessonlyoninstance1forinstance0.+Ifyouin-SOtendtoruntheGCUoninstance1also,thenyouneedtoaddOOproxyaccessoninstance0forinstance1.(Inthree-instanceMOHGalaxysystems,youmayneedtoaddproxyaccessforeachQO combinationof instancesyouwanttocontrol.'Forthisreason,QOagoodruleofthumbistoalwaysruntheGCUfrominstance OR0./ ]MOYouarenotrequiredtousetheSYSTEMaccount.'TochangeIOtheaccount,youneedtoeditSYS$MANAGER:GCU$ACTIONS.COMRO5oneachinvolved instance.'Locatethelinethat establishestheGO task-to-task connection,andreplacetheSYSTEMaccount.Onamewithoneofyour choosing. NHONotethattheselectedaccountmusthaveOPER,SYSPRV,LOandCMKRNL privileges.'Youalsoneedtoaddthe necessaryAO5proxyaccesstoyour instancesforthisaccount. G FH<~,O9.3BGalaxy ConfigurationModelsJOUTheGCUisafully programmabledisplayengine.+ItusesOOasetofrulestolearnthedesiredcharacteristicsandin-IO teractive behaviorsofthesystem components.+UsingthisEO^ specialized configuration knowledge,theGCU assemblesJOmodelsthat representthe relationshipsamongsystemcom-GOponents.,TheGCUobtains informationaboutthecurrentLOhsystem structurebyparsinga configuration structurebuiltLObytheconsole firmware.*This structure,calledtheGalaxyHO ConfigurationFile,isstoredinmemoryandisupdatedEOrasneededbyfirmwareandbyOpenVMS executiverou-QOtinestoensurethatit accuratelyreflectsthecurrentsystem$O# configurationandstate.d :GOTheGCUconvertsandextendsthebinaryrepresentationOOofthe configurationfileintoasimpleASCIIrepresentation,OO5whichitcanstoreinafileasanofflinemodel.+TheGCUOOcanlaterreloadanofflinemodelandalterthesystemcon-MO figurationtomatchthemodel.(WhetheryouareviewingtheRO>activemodeloranofflinemodel,youarealwaysfreetosaveMOthecurrent configurationasanofflineGalaxy ConfigurationOModel(.GCM)file.aLOTomakeanofflinemodeldrivethecurrentsystemconfig-KOuration,themodelmustbeloadedandengaged.*ToengageKO5amodel,clicktheEngagebutton.+TheGCUwillscantheOOcurrent configurationfile,compareitagainstthemodel,andPOcreatealistofany managementactionsthatarerequiredtoPO>engagethemodel.)TheGCUpresentsthislisttoyouforfi-MOnal confirmation.)Ifyouapprove,theGCUwillexecutetheLOactions,andthemodelwillbecomeengagedtoreflectthe5OHcurrentsystem configurationandstate.x NGOWhenyou disengageamodel,theGCU immediatelymarksNOtheCPUsand instancesasoffline.)Youcanthenfreelyar-PO5rangethemodelhoweveryoulike,andeithersavethemodel,QOorreengagethemodel.)Intypical practice,youarelikelytoOOhaveasmallnumberofmodels,thathaveprovedtobeuse-LO>fulforyourbusiness operations.+ThesecanbeengagedbyMOasystemmanagerorasuitably privilegeduser,orthrough0O automated proceduresorbatchjob.} SO9.3.1BActiveModelNO4TheGCU maintainsasingleactivemodel.'Thismodelisal-HOwaysderivedfromthe in-memory configurationfile.*TheMO configurationfilecanbefromaGalaxyconsoleorfromaGO= file-based,single-instanceGalaxyonanyAlphasystem.NO Regardlessofitssource,console callbacksmaintainthein-ROtegrityofthefile.(TheGCUutilizesGalaxyeventservicestoIOG determinewhena configurationchangehas occurred.'WhenMOachangeoccurs,theGCUparsesthe configurationfileandNOupdatesitsactivemodeltoreflectthecurrentsystem.*TheWOQactivemodelisnotsavedtoafileunlessyouchoosetosaveitOOasanofflinemodel.) Typically,theactivemodelbecomestheLObasisforcreating additionalmodels.)Whencreatingmodels,UOZitis generallybesttodosoonlinesothatyouaresureyour@Oofflinemodelscanengagewhentheyareneeded.qVG O9.3.2BOfflineModelsKO4TheGCUcanloadanynumberofofflineGalaxy configura-IOtionmodelsandfreelyswitchamongthem,assumingtheyJOwerecreatedforthespecificsystem hardware.*ThemodelIO=representationisasimpleASCIIdata definitionformat.aSOYoushouldneverneedtoeditamodelfileinitsASCIIform.LOTheGCUmodelsandrulesetadheretoasimple proprietaryCO5languageknownastheGalaxy ConfigurationLanguageMO(GCL).Thislanguage continuestoevolveasneededtorep-LOresentnewGalaxy innovations.+BewareofthisfactifyouRO>decidetoexplorethemodelandrulesetfiles directly.)IfyouKO accidentallycorruptamodel,youcanalwaysgeneratean-OOother.(Ifyoucorrupttheruleset,youmayneedtodownload7OHanotherfromtheOpenVMSGalaxywebsite.By9O9.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,dragMWanddropsomeoftheCPUstoa differentGalaxy instance.L`5.:Savethemodelby selectingSaveModelfromtheModelH/menu.(Givethemodelasuitablenamewitha.GCMex-Ptension.&ItisusefultogivethemodelanamethatdenotesCtheCPU assignments;forexample,suchasG1x7.GCML9forasysteminwhichinstance0has1CPUandinstanceJ1has7CPUs,orG4x4.GCMforasystemwith4CPUonMeachofitstwo instances.'Thisnamingschemeis optional,KCbutbesuretogivethefiletheproper.GCM extension. cKbYoucancreateandsaveasmany variationsofthemodelasyoulike.S))OToengageanofflinemodel:R *(`1.:RuntheGCU.M`O2.:Bydefault,theGCUdisplaystheactivemodel.)Youcan9closetheactivemodelorjustleaveit.N`'3.:Loadthedesiredmodelby selectingOpenModelfromtheModelmenu.L`4.:LocateandselectthedesiredmodelandclickOK.TheKWmodelwillbeloadedand displayedinanoffline,disen-gagedstate.C`/5.:ClicktheEngagebuttontoreengagethemodel.G`6.:TheGCUwilldisplayany management operationsre-Iquiredtoengagethemodel.,Ifyouapproveoftheac-F`tions,clickOK.TheGCUwillperformthe managementIactions,andthemodelwillbe displayedasactiveandengaged. ySH/GImC&O9.4BUsingtheGCUChartsEOUTheGalaxy ConfigurationFilecontainsa considerableGOamountof configurationdataandcangrowquitelargeMOforcomplexGalaxyconfigurations.(IftheGCU displayedallMO^the informationithasaboutthesystem,thedisplaywouldHObecome unreasonablycomplex.,Toavoidthisproblem,theIOGCUprovidesGalaxycharts.-ChartsaresimplyasetofNOhmasksthatcontrolthe visibilityofthevarious components,IOdevices,andinterconnections.*Theentire componenthier-MOarchyispresent,butonlythe components specifiedbythePOrselectedchartarevisible.* Selectinga differentchartalters2Othe visibilityof componentsubsets.[! 1NOBydefault,theGCUprovidesfive preconfiguredcharts.'EachMOisdesignedtoshowaspecific component relationship.)SomeDO5GCUcommand operationscanbe performedonlywithinGOspecificcharts.-Forexample,youcannotreassignCPUsGOfromwithinthePhysical Structurechart.-ThePhysicalJO> StructurechartdoesnotshowtheGalaxyinstancecompo-QOnents,thusyouwouldhavenotargettodraganddropaCPUOOon.'BecauseyoucanmodifythechartstheGCUdoesnotre-KOHstrictitsmenusandcommand operationstospecificchartNO selections.'Insomecases,theGCUdisplaysan informationalAOmessagetohelpyouselectan appropriatechart.rHHOFormore informationabout modifyingcharts,see?????. cDO9.4.1B ComponentIdentificationandDisplay PropertiesOO4Each componenthasaunique identifier.)This identifierbeaKOsimple sequentialnumber,suchaswithCPUIDs,aphysi-ROcal backplaneslotnumber,aswithI/O adapters,oraphysicalIO=address,aswithmemorydevices.+Each componenttypeisLOalsoassignedashapeandcolorbytheGCU.Wherepossi-HOble,theGCUfurther distinguisheseach componentusingEOG supplementary informationitgathersfromtherunningOsystem._ 5NOThedisplay propertiesofeach componentareassignedwithinHOtheGalaxy ConfigurationRuleset(SYS$MANAGER:GALAXY.GCR).MO5Youshouldnoteditthisfile,exceptto customizecertainROdisplay properties,suchaswindowcolorordisplaytextstyle.)! LOThetextthatgets displayedabouteach componentisalsoOO customizable.'Each componenttypehasasetof statementsinNO5therulesetthat determineits appearance,datacontent,andO interaction.YSOOneusefulfeatureistheabilitytoselectwhichtextisdis-JOplayedineach componenttypeonthescreen.,ThedevicePO5 declarationintherulesetallowyoutospecifythetextandIO parameters,whichmakeupthedisplaytext statement.*AMOsubsetofthisdisplaytextis displayedwheneverthezoomTO>scalefactordoesnotallowthefulltexttobe displayed.)ThisGOsubsetisknownasthe mnemonic.+Themnemoniccanbe;Oalteredtoincludeanytextand parameters.! }+O9.4.2BPhysical StructureChartMO4ThePhysical Structurechart describesthephysicalhardwareMOinthesystem.)Thelarge rectangular componentatthetop,OOorroot,ofthechart representsthephysicalsystemcabinetSO=itself.( Typically,belowtheroot,youwillfindphysicalcompo-ROnentssuchasmodules,slots,arrays, adapters,andsoon.'TheKOtypeof components presentedandthedepthofthecompo-OOGnent hierarchyisdirectly dependentonthelevelofsupportJOprovidedbytheconsolefirmwareforeachhardwareplat-KOform.+Ifyouareviewingasingle-instanceGalaxyonanyOOQAlphasystem,thenonlyasmallsubsetof componentsmaybeMO displayed.*Asageneralrule,theconsolefirmwarepresentsLO componentsonlydowntothelevelof configurabledevices,ROZ typicallytothe first-levelI/Oadapterorslightlybeyond.*ItPOisnotagoaloftheGCUoroftheGalaxyconsolefirmwareRO tomapeverydevice,butratherthosethatareofinterestto,OdGalaxy configuration management. NPOThePhysical StructurechartisusefulforviewingtheentireOO collectionof componentsinthesystem.)However,itdoesnotCO5displayanylogical partitioningofthe components.b88OInthePhysical Structurechartyoucan:!  ` ?Examinethe parametersofanysystem component. `O KOPerformahot-swapinquiryto determinehowtoisolatea" componentforrepairs. `' G'Applyan OptimizationOverlayto determinewhethertheFhardwareplatformhasspecific optimizationsthatwillCensurethebest performance.+Forexample, multiple-C1CPUmodulesmayrunbestifallCPUsresidingonAacommonmoduleareassignedtothesameGalaxy instance. `a HaShutdownorreboottheGalaxyorspecificGalaxyin-stances.q! ]G!O9.4.2.1CHardwareRootJO)Thetopmost componentinthePhysical StructurechartisIOknownasthehardwareroot (HW_Root).'EveryGalaxysys-SOtemhasasinglehardwareroot.*ItisusefultothinkofthisRO3asthephysical floorplanofthemachine.(IfaphysicaldeviceSOhasnospecificlowerplaceinthe component hierarchy,itwillSOappearasachildofthehardwareroot.&A componentthatisaPO<childcanbeassignedtootherdevicesinthe hierarchywhen@Othemachineis partitionedor logicallydefined. z oTip zFClickingtherootnodeofanychartwillperformanG auto-layout operationiftheAutoLayoutmodeisset. AG U%O9.4.2.2C OwnershipOverlayBO)Choose OwnershipOverlayfromtheWindowsmenutoNOdisplaytheinitialowner relationshipsforthevariouscom-MOponents.+These relationshipsindicatetheinstancethatwillLO3ownthe componentafterapowercycle.)OnceasystemhasIObeenbooted, migratable componentsmaychangeownersdy-RO namically.(Inordertoaltertheinitial ownership,theconsole4O< environment variablesmustbechanged.EOThe ownership overlay has no effectonthe Physical=O StructurechartortheFailoverTargetchart.vL*O9.4.3BLogical StructureChartGO4TheLogical StructurechartdisplaysGalaxy communitiesROand instancesandisthebest illustrationofthe relationshipsGOwhichformtheGalaxy.,Belowthese componentsaretheIO=variousdevicesthey currentlyown.+ Ownershipisanim-LOportant distinctionbetweentheLogical StructurechartandKOPhysical Structurechart.+InaGalaxy, resourcesthatcanMOGbe partitionedor dynamically reconfiguredhavetwodistinctO ``owners''. WMOTheowner describeswherethedevicewillturnupafteraLOsystemcoldboot.,Thisvalueis determinedbytheconsoleIO5firmwareduring bus-probing proceduresandthroughinter-IO pretationoftheGalaxy environment variables.*TheownerOOvaluesarestoredinconsole nonvolatilememorysothatthey4O>canberestoredafterapowercycle. ! pIOThe current_owner describestheownerofadeviceataLO particularmomentintime.*Forexample,aCPUisfreetoOO5reassignamong instances.'Asitdoes,its current_ownervaluePOis modified,butitsownervalueremainswhateveritwassetO5select OwnershipOverlayfromtheWindowmenu. ! !O9.4.3.1CSoftwareRootIO)Thetopmost componentintheLogical StructurechartisKOknownasthesoftwareroot (SW_Root).'EveryGalaxysystemUOhasasinglesoftwareroot.'IfaphysicaldevicehasnospecificSO3owner,itwillappearasachildofthesoftwareroot.)Acom-UOponentthathasachildcanbeassignedtootherdevicesinthe@O hierarchywhenthemachineis logicallydefined. ez ohTip ezFClickingtherootnodeofanychartwillperformanHFautolayout operationiftheAutoLayoutmodeisset. n ! LD(O9.4.3.2C Unassigned ResourcesOO)Youcan configureGalaxy partitionswithout assigningallde-SOvicestoa partition,oryoucandefinebutnot initializeoneKOormore partitions.+Ineithercase,somehardwaremaybe/O3 unassignedwhenthesystemboots. eIOTheconsolefirmwarehandles unassigned resourcesintheO followingmanner:h ` A UnassignedCPUswillbeassignedto partition0. `O 0O Unassignedmemorywillbeignored. NLODevicesthatremain unassignedafterthesystembootswillMOappearassignedtothesoftwareroot componentandmaynotO5be accessible./ 'O9.4.3.3C Community ResourcesNO) Resourcessuchassharedmemorycanbeaccessedbyallin-JOstanceswithinasharing community.* Therefore,forsharedFOmemory,the communityitselfis consideredtheowner.&O9.4.3.4CInstance ResourcesHO) Resourcesthatare currentlyor permanentlyownedbyaMOspecificinstanceare displayedaschildrenoftheinstanceO component.d*O9.4.4BMemory AssignmentChartHO4TheMemory Assignmentchart illustratesthe partitioningDOand assignmentofmemory fragmentsamongtheGalaxyGO instances.,Thischartdisplaysbothhardware componentsIO=(arrays, controllers,andsoon)andsoftware componentsO(memory fragments).EOCurrentGalaxyfirmwareand operatingsystemsoftwareHOdoesnotyetsupportdynamicreconfigurationofmemory.HO5Thus,theMemory AssignmentchartreflectsthewaytheJOmemoryaddressspacehasbeen partitionedbytheconsoleJOamongtheGalaxy instances.*This informationcanbeuse-PO>fulfor debuggingsystem applicationsorforstudyingpossible!O configurationchanges. c%O9.4.4.1CConsole FragmentsKO)Theconsolerequiresoneormoresmall fragmentsofmem-GOory.0 Typically,aconsole allocates approximately2MBHOofmemoryinthelowaddressrangeofeach partition.HO3Thisvariesbyhardwareplatformandfirmware revision.OO Additionally,someconsolesallocateasmallfragmentinhighKOaddressspaceforeach partitiontostorememorybitmaps.JO<Theconsolefirmwaremayneedtocreate additionalfrag-8Omentstoenforcepropermemory alignment. %O9.4.4.2CPrivate FragmentsKO)EachGalaxyinstanceisrequiredtohaveatleast64MBLOofprivatememory (includestheconsole fragments)tobootLOOpenVMS.Thismemorymayconsistofasingle fragment,orLO3theconsolefirmwaremayneedtocreate additionalprivatereassigntheCPUbacktothecurrentowner..TheGCU9O communicatesonlywiththeGalaxymembers.J JO RegardlessofwhetheraninstanceispartoftheGalaxyQOsharing communityorisan independentnode,itwillstillbeOO5presentintheGalaxy configurationfile; therefore,thusthe6OGCUwillstillbeabletodisplayit. 'O9.4.6BIOP AssignmentChartKO4TheIOP Assignmentchartdisplaysthecurrent relationshipMObetweenI/O processorsandtheGalaxy instances.)Notethat,MO dependingonwhattypeofhardwareplatformisbeingused,LO=asingle-instanceGalaxyonanyAlphasystemmaynotshow'OanyIOPsinthisdisplay.  POThe OwnershipOverlaycanbeshowninthischarttoseetheOO nonvolatileowner(whichinstancethedevicewillbeassignedRO5toafterapowercycle),butuntilIOPreconfigurationissup-GOportedbytheOpenVMSGalaxyimplementation,theownerNOwillalwaysbethesameasthedefaultdisplay illustrates.h!V>(O9.4.7BFailoverTargetChartIO4TheFailoverTargetchartshowshoweach processorwillNO automaticallyfailovertoother instancesintheeventofaNOshutdownorfailure.+ Additionally,thischart illustratesthe1O=stateofeachCPUs autostartflag."NROForeach instance,asetoffailoverobjectsareshown,repre-SOsentingthefullsetof potentialCPUs.(Bydefault,nofailoverPO5 relationshipsare establishedandall autostartflagsareset.#LOTo establish automaticfailoverofspecificCPUs,dragandQOdropthedesiredfailoverobjecttotheinstanceyouwanttheMO5 associatedCPUtotarget.,Tosetfailover relationshipsforMOallCPUsownedbyan instance,draganddroptheinstanceOOobjectontopoftheinstanceyouwanttheCPUstotarget.$! WQOToclear individualfailovertargets,draganddropafailoverPOobjectbacktoitsowner instance.+Toclearallfailoverre-PO5 lationships, right-clickontheinstanceobjecttodisplaytheIO Parameters&Commandsdialogbox,clickontheCommandsOObutton,clickthe``ClearALLfailover targets?'',buttonandO>thenclickOK.|% RLOBydefault,wheneverafailover operationoccurs,theCPUsNOwill automaticallystartoncetheyarriveinthetargetin-KO5stance.,Youcancontrolthis autostartfunctionusingtheFO autostartcommandsfoundinthe Parameters&CommandsPOdialogboxforeachfailoverobject,oreachinstanceobject.PO>TheFailoverTargetchartdisplaysthestateofthe autostartTOflagby displayingtheFailoverobjectsingreenif autostartis3Oset,andredif autostartisclear.&NOPleasenotethe following restrictionsinthecurrentimple->O mentationoffailoverand autostart management.5'   ` FThefailoverand autostartsettingsarenot preservedN(acrosssystemboots.'Thus,youwillneedto reestablishtheJmodelwheneverthesystemreboots.)Todothis,invokeaE previouslysaved configurationmodel,eitherbymanu-I2ally restoringthedesiredmodelorbyusingacommand- procedureduringsystemstartup. `  J TheGCU currentlyisnotcapableof determiningtheau-Kctostartandfailover relationshipsof instancesotherthanKtheonetheGCUisrunningon,unlessthe instancesare clustered. ` BTheGCU currentlydoesnotrespondtochangesinHfailoveror autostartstatethataremadefromanotherED executingcopyoftheGCUorfromDCL commands.*IfPthisstateisaltered,theGCU refreshesitsdisplayonlyif>theactivemodelisclosedandthen reopened. IHJ7( -O9.5BViewing Component ParametersKOUEach componenthasasetof parametersthatcanbedis-OOplayedand,insomecases,altered.)Todisplaya component'sJO parameters,positionthecursoronthedesired component,IO^clicktherightmousebutton,andselectthe ParametersKOitemfromthepopupmenuentry.) Alternately,youcanse-MOlecta component,thenselectthe ParametersitemfromtheOh Componentsmenu.A)! HOWhere parametersaresubjecttounit conversion,chang-ROingthedisplayunitwillupdatethedisplayandany currentlyJO5visible parameterdialogboxes.)Other parameters representIOasnapshotofthesystem componentandarenotdynami-KOcallyupdated.*Ifthese parameterschange,youmustclosePO>andthenreopenthe ParametersdialogboxtoseetheupdatedOOvalues.'(This limitationwillbefixedinafuture version.) $JIK *! 2-O9.6B Executing ComponentCommandsHOUA component's ParametersdialogboxmayalsocontainaFOcommandpage.-Ifso,youcanaccessthecommandsbyROclickingontheCommandsbuttonatthetopofthedialogbox.OO^Mostofthecommandsareexecutedbyclickingontheirtog-POglebuttonsandthenclickingtheOKorApplybuttons.'OtherLOcommandsmayrequirethatyouenter information,orselectUOhvaluesfromalistoroptionmenu.'Notethatifyouselectsev-LOeral commands,theywillbeexecutedinatop-downorder.GOBesuretochoosecommand sequencesthatarelogical.  LKM<! <=O9.8B MonitoringanOpenVMSGalaxywithDECamdsDOUTheDECamds availabilitymanagersoftwareprovidesaKOvaluable real-timeviewoftheGalaxysystem.'DECamdscanKOmonitorallGalaxy instancesfromasingle workstationorIO^PCanywhereonthelocalareanetwork.)DECamdsutilizesDOacustomOpenVMSdriver (RMDRIVER)that periodicallyPOgathers availabilitydatafromthesystem.'This informationisNOhreturnedtotheDECamdsclient applicationusinga low-levelKOEthernet protocol.(Theclient applicationprovidesnumerousOOviewsandgraphsofthesystem's availabilitycharacteristics.IOr Additionally,whenDECamdsdetectsoneofnumerousknownRO conditions,itnotifiestheuserandoffersasetof solutionsOO#(calledfixes)thatcanbeappliedtoresolvethe condition.= AOEveryOpenVMSsystemcomeswiththeDECamdsDataHO Collector (RMDRIVER) installed.,Toenablethe collector,IO5youmustexecuteitsstartup procedureinside SYSTARTUP_FOVMS.COMormanuallyoneachGalaxyinstanceyouwantKOtomonitor.+Usethe followingcommandstostartthedataO> collector:7O $&@SYS$STARTUP:AMDS$STARTUP%STARTKor&STOP> WIOPriorto startingthe collector,!youneedtospecify aIOgroupnameforyourGalaxy./Dosobyeditingthefile3O5#SYS$COMMON:[AMDS]AMDS$LOGICALS.COM.ThisOOfileincludesa statementfor declaringagroupname.'ChooseHOanyuniquename,makingsurethisfileoneachGalaxy5O>instancecontainsthesamegroupname.?! WHOWhenusingDECamds,OpenVMS EngineeringfindsitusefulIOtodisplaytheSystemOverviewwindow,theEventWindowDO5andaCPUSummarywindowforeachGalaxy instance.IOThereareanumberof additionalviewsyoucanmonitorKO dependingonyourspecific interests.*Formore information)O>aboutDECamds,refertothek> DECamdsUsersGuide >. MLN@ )%O9.9BCreatinganInstanceAOUThecurrentimplementationoftheGalaxySoftwareIO ArchitectureforOpenVMSrequiresthatyou predefinetheQOGalaxy instancesyouintendtouse.(YoucandothisbyusingMO^console environment variables.(Refertothe appropriatesec-POtionsofthisguideformoredetailsaboutGalaxy environmentO variables. NMOeAw;(O9.10C DissolvinganInstancePOUTheonlywayto effectivelydissolveaGalaxyinstanceistoMOshutitdown,reassignits resourcesusingconsoleenviron-NOment variables,and,if necessary,rebootany instancesthat(O^willacquirenew resources. ONPB-O9.11CShutdownandRebootCyclesEOU ResourcessuchasCPUscanbe dynamically reassignedPOoncetheinvolved instancesarebooted.(Toreassign staticallyKOassigned resources,suchasI/O processors,youmustshutLO^downandreboottheinvolved instancesafter executingthe)O appropriateconsole commands.  POQC! 2/O9.12COnlineversusOfflineModelsKOUTheGCUallowsyoutodisplayandinteractwiththeac-QOtive(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 LHOGCUuserscanalsointeractwithanynumberofdisen-POgaged,oroffline,models.*OfflinemodelscanbesavedtoorPO5loadedfromfiles.(AnofflinemodelcanalsobederivedfromOOtheactiveonlinemodelbyclickingtheEngagebuttontobeOO disengagedwhentheactiveonlinemodelis displayed.'Inad-RO>ditiontothevisualstateoftheEngagebutton,theGCUalsoPO indicatestheonlineversusofflinecharacteristicoftheCPUsJOand instancesbyusingcolorandtext.*Any drag-and-dropQOHactionsdirectedatanofflinemodelare interpretedassimpleNOediting functions.)Theychangetheinternal structureofthe;Omodelbutdonotaffecttheactivesystem.E kIOWhenanofflinemodelisengaged,theGCUcomparestheSO structureofthemodelwiththatoftheactivesystem.(IftheyTO5agree,theofflinemodelisengagedanditsnewonlinestateisQO indicatedwithcolorandtext.)Iftheydonotagree,theGCUHO determineswhat managementactionswouldberequiredtoOO>altertheactivesystemtomatchtheproposedmodel.)AlistOOofthe resulting managementactionsis presentedtotheuserQOandtheuserisaskedwhethertheywouldliketoexecutetheROHactionlist.(Iftheuser disapproves,themodelremainsofflineMOand disengaged.)Iftheuser approves,theGCUexecutestheLO managementactionsandthe resultingmodelis displayedasORonlineandengaged. QPRFn{4O9.13CWhat'sNewForTheGCUinEFT3GOUThisinfoneedstobemovedtothecorrect location:nGMD$O9.13.1CNewDCLcommands O4 SETCPU n/FAILOVER=yH~LO Establishesinstance-specificfailover relationshipsforeach2OCPUinthe instances potentialset.INGOWherenistheCPUnumber,acomma-separatedlistofGOCPUs,or/ALLandyistheinstancenumberorname. ! SETO5 CPU n/NOFAILOVERJKORemovesanyinstance-specificfailover relationshipfortheO specifiedCPU/s.# SETCPUn/[NO]AUTOSTARTKhMOSetsorclearstheinstance-specific autostartflagfortheO specifiedCPU/s.LaGOWherenistheCPUnumber,acomma-separatedlistofOCPUs,or/ALL. B4RQS(4M RD3%O9.14CGCUSystemMessages R5*UMargie: 6R5GThesemessagesneedtobein alphabeticalorderbased42onthemessagenamegcu-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%inUV 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:Up 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%modelXw 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.SP 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.KThisUk 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%problemBC 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%and5 reboot.)O %GCU-E-UNKNOWN_KEYWORD:%{word}[ The%GCU%has&parsed%an%unknown&keyword%in%the&current%model%file.KThisPO can%only&result%from&model&file%format& corruption.KDelete%and* recreate&the% offending%model.8O %GCU-E-NOPARAM:%Display%field%{field%name}Wi 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.Tv 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%recentRM 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}Yh 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&oneZ7. from%the&OpenVMS%Galaxy&web%page.JIf%the&problem% persists,&delete%and*. recreate&the% offending%model.#O. %GCU-F-PARSERR,%{detail}YQ/ 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}Wl0 The%GCU%could%not&locate%the% specified&font%on%the&current%system.40 A%default%font&will%be%used%instead.:O1 %GCU-W-NOCOLORCELL:&Unable%to%allocate%colorX1 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%numberA2 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.FO5 %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}Sx7 This% informational%message& indicates%the%start%of%a% configurationR7 action%on%the% specified&Galaxy% instance.KNote%that%many&actionsS8 require% collaboration%between&command% environments&on&two%separateXP8 Galaxy% instances,&thus,&you%may% encounter&two%of%these% messages,%oneV8 per%instance%involved%in%the% operation.JThe&mode%argument% indicates58 which&instance&is&local&versus%remote.7OI9 %GCU-S-ACTIONENDKat%{time},&on& {nodename}V9 This%is%the&normal% successful& completion%message% following%a%GalaxyS9 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%is7i> 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.POA %GCU-E-INSFPRIVS,% Insufficient% privileges%for% attempted& operationZA An&underprivileged%user&has% attempted%to%perform%a&Galaxy% configurationXGB action.K Typically,%these%actions%are% performed&from%within&the%systemKB managers&account.KOPER&and%SYSPRV% privileges%are% required.>OB %GCU-E-NCF&network%connect%to% {instance}&failedYbC An&error&has%occurred%trying%to%open%a&DECnet% task-to-task% connectionTC between%the&current%and& specified% instances.KReview%related%screenRC messages&and%verify%that%the% necessary&proxy&accounts&have%been9D established. SRTN}O 10.2DCL!CommandsGOThe followingDCLCommandsareusefulformanaginganOOpenVMSGalaxy:O ? ` SHOWMEMORY `O OSTOP/CPU/MIGRATE ` SHOWCPU `N CN CONFIGUREGalaxy(CheckedintoonlineDCLHelpforEFT3) `& &Lexical functionsPNAOSeveralDCLcommandshavebeenenhancedwithnewEO qualifiersforusewithsharedmemoryinanOpenVMSO5Galaxy:QhW ` DUMP `O 3OANALYZE(not supportedfor V7.2-EFT3) 2T SURnaO10.1CCPUCommandsDOUCPUsare assignable resourcesinanOpenVMSGalaxy.St"O10.1.1CSTOP/CPU/MIGRATE>O4 Addmore description..NeedtotalkmoreaboutO migration.T N=OTheSTOP/CPU/MIGRATEcommandstopsandremovesQOthe specified secondary processor(s)fromtheactivesetinanO5OpenVMSSMPsystem.AUOForexample:sV!I OWhenauserenters:)O GLX1$%stop/cpu/migrate=GLX0K4W !LOThe followingmessageis displayedattheuser's terminal:`O %SYSTEM-I-CPUSTOPPING,&trying%to%stop&CPU%4&after&it&reaches% quiescent&stateX!a)OThesourceconsole displays:8O %SMP-I-STOPPED,%CPU&#04%has%been%stopped.eY!;.OThe destinationconsole displays: O TBSZO10.1.2CSHOWCPU?O4TheSHOWCPUcommanddisplays informationaboutOOthestatus,characteristics,and capabilitiesofthe specifiedO processor(s).[l OForexample: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\ ~O10.2CSHOWMEMORYCOUTheSHOWMEMORYcommanddisplaystheusesofmem-Oorybythesystem.] OForexample:O CLSSIC$&SHOW%MEMORY@Zq System%Memory% Resources&on& 5-OCT-1999% 20:50:19.032O Physical%Memory%Usage%(pages):Total!O FreeIn%UseModified## Main&Memory% (2048.00Mb)D# 262144O# 228183314942467O GALAXY$&show%memory@Z System%Memory% Resources&on& 5-OCT-1999% 07:55:14.682O Physical%Memory%Usage%(pages):Total!O FreeIn%UseModified% Private&Memory% (512.00Mb)j 65536O 561468875  515% Shared%Memory& (1024.00Mb)j 131072O 130344728dOx Of%the%physical%pages%in%use,%6421&pages&are% permanently% allocated%to%OpenVMS. O $ 7VUWT^**O10.3CLexicalFunctionExamplev_ |L8OLexicalFunctionExampleCommand 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)7OLexicalFunctionCommand ProcedureOutputO# COBRA2$&@shoglxO Instance%=&COBRA2O Platform%=&1O Sharing&Member%=&19Od Galaxy%ID%=% 376172626F6320202020202020202020O Community%ID%=%0O Partition%ID%=%0O] COBRA2$ W VXgan=O10.4CDUMP)OU New Qualifier:'/SHARED_MEMORYb! POIntheeventofsystemcrashes,itmaybe necessarytosavePOthecontentsofsomeorallofsharedmemoryinadditiontoRO5thememorythatislocaltothesystemthathascrashed.'ThisNOwillbedoneeitherbywritingsharedmemorytothesystemOOdumpfileusingenhancedsystemdumpcode,orasaseparate>O>stepusingtheDUMP/SHARED_MEMORYcommand.(ThisROcanbedoneeitherafterthefailedsystemreboots,oratanyIOtimefromanotherinstanceofOpenVMSinthesamecom->OHmunity.*DUMP/SHARED_MEMORYwritestoaseparate2Ofile,nottothesystemdumpfile.kc AGOSharedmemoryincludedinasystemdumpfilewillbeAOanalyzedwiththeexistingANALYZE/CRASH_DUMPcom-GO5mand.)Sharedmemorydumped separatelywillbeanalyzed9OusingthenewcommandANALYZE/SHARED_MEMORY9O(whichisthetopicofaseparatenote).HdOSyntax Description:e [=OTheformatis:(DUMP/SHARED_MEMORY [region_name_Olist] [other_quals]Of %JOwhere"region_name_list"isacomma-separatedlistoftheNOregionsofsharedmemorytobedumped,alogicalnamethat/O5 translatestosuchalist,or" 8@*0]5", indicatingthatallregionsinJOsharedmemoryaretobedumped.+IfnoregionnamelistGOisgiven,thedefaultisGLX$DUMP_RANGE,whichisex-VO>pectedtobealogicalnamethat translatestoalistofregionsinSDA,suchnumberscanincludeaperiodtoseparatethe6Oupper32bitsfromthelower32bits.&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-NOmand(whichisthetopicofaseparatenote).+ThiscanbeOOdoneeitherafterthefailedsystemreboots,oratanytimeIOHfromanotherinstanceofOpenVMSinthesame community.EODUMP/SHARED_MEMORYwritestoaseparatefile,notto"Othesystemdumpfile.3o  GOSharedmemoryincludedinasystemdumpfilewillbeAOanalyzedwiththeexistingANALYZE/CRASH_DUMPcom-GO5mand.)Sharedmemorydumped separatelywillbeanalyzed:OusingthenewcommandANALYZE/SHARED_MEMORY.HpOSyntax Description:hq>>OTheformatis:'ANALYZE/SHARED_MEMORY "file_name"rrLOwhere "file_name"isthenameofthefilecreatedbythe&ODUMP/SHARED_MEMORYcommand.s WsAOTheonlyexistingANALYZE qualifier(fromANALYZE:O /CRASH_DUMP)thatmaybeusedwithANALYZEAO5/SHARED_MEMORYis /OVERRIDE.This qualifier,whichOOis optional,allowslimitedaccesstothesharedmemorydumpMOfilewhentryingto establishthecauseofa corruptedorO> incompletedump.Kt!!O Qualifier description:luBDOThe/SHARED_MEMORY qualifier indicatesthatasharedMOmemorydumpistobe analyzed.)TheSDAutilityisinvokedLO5toperformthe analysis,althoughitshouldbenotedthatMOonlyalimitedsetofSDAcommandsarerelevanttosharedOmemorydumps.vOExample:9O $&ANALYZE/SHARED_MEMORY%GLX$SHARED_MEMORY.DMP6q OpenVMS%(TM)%Alpha%system%dump%analyzer: ...analyzing%a&Galaxy%shared%memory&dump...O# shmSDA>&EXIT Ok $wEOThiscommandinvokesSDAtoanalyzethesharedmem->OorydumpfileGLX$SHARED_MEMORY.DMP.(NotethatGO5thisisthedefaultfilenamecreatedby DUMP/SHARED_OMEMORY). YXZx O10.6CINSTALLNOUTheLISToptionnowreturnsthe galaxywidesectionsaswell)Oasstandardglobal sections. ZY[y k4O 11.=Shared'Memory'Cluster' InterconnectOr(SMCI)IOTheSharedMemoryCluster Interconnect(SMCI)isanSCSFOOportforcommunicationsbetweenGalaxy instances.*WhenMOanOpenVMSinstanceisbootedasbothaGalaxyandasanGOOpenVMSCluster,theSharedMemoryCluster InterconnectLOYdriverwillbeloaded.*ThisSCSportdriverwillcommuni-MOcatetoothercluster instancesinthesameGalaxythroughHO sharedmemory.,This capabilityprovidesoneofthema-HObjor performancebenefitsoftheOpenVMSGalaxySoftwareJO Architecture.*Theabilityto communicatetoanotherclus-FOteredinstancethroughsharedmemoryprovidesdramaticKOl performancebenefitsover traditionalclusterinterconnects.  [Z\zk+O11.1C SYS$PBDRIVERPortDevicesJOUWhenbootingasbothaGalaxyandasaclustermember,HO SYS$PBDRIVERwillbeloadedbydefault.,TheloadingofLOthisdriverwillcreateadevicePBAx,wherex representsOO^theGalaxy partitionId.*Asother instancesarebooted,theyKOwillalsocreatePBAxdevices.)TheSharedMemoryCIwillIOquicklydiscovertheother instancesandcreatecommuni-LOhcationschannelstotheother instances.+Unlike traditionalNOclusterinterconnects,anewdevicewillbecreatedtocom-NOmunicatetotheother instances.*ThisdevicewillalsohaveLOrthenamePBAx,wherex representstheGalaxy partitionIdKOfortheinstancewithwhichthisdeviceiscommunicating.${MOForexample,lookataGalaxy consistingoftwo instances:EOMILKYandWAY.MILKYisinstance0andWAYisin-IO5stance1.)WhennodeMILKYboots,itcreatesPBA0.)WhenNOnodeWAYboots,itcreatesPBA1.)AsthetwonodesdiscoverIOeachother,MILKYcreatesPBA1totalktoWAYandWAY-O>createsPBA0totalktoMILKY. MILKY D WAY, PBA0:D, PBA1:! PBA1:p <------->PBA0:|! ;O11.1.1CMultipleClustersinaSingleGalaxyGO4 SYS$PBDRIVERcansupportmultipleclustersinthesameIOGalaxy.(Thisisdoneinthesamewaythat SYS$PEDRIVERLOallowssupportformultipleclustersonthesameLAN.TheGO=clustergroupnumberandpasswordusedby SYS$PEDRIVERGOarealsousedby SYS$PBDRIVERto distinguish differentLOclustersinthesameGalaxy community.)IfyourGalaxyin-HOGstancesarealso clusteredwithotherOpenVMS instancesMOviatheLAN,theclustergroupnumberwouldbesetappro-DOpriatelybyCLUSTER_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>'} NOIfyouarenot clusteringoveraLANandyouwanttorunJOmultipleclustersinthesameGalaxy community,thenyouOO5mustsettheclustergroupnumber.'YoumustinsurethattheLOgroupnumberandpasswordissetthesameforallGalaxyFO instanceswhichyouwishtobeinthesamecluster.Ok $&MCR%SYSMAN[O SYSMAN>& CONFIGURATION%SET&4CLUSTER_AUTHORIZATION/GROUP_NUMBER=222/PASSWORD=xxxxO SYSMAN>~! JOInmostcases,CLUSTER_CONFIGshoulddotherightthing.MOIfyourGalaxy instancesarealso clusteringovertheLAN,CO5CLUSTER_CONFIGwillaskforaclustergroupnumberPOandtheGalaxy instanceswillutilizethosegroupnumbers.'IfLOyouarenot clusteringoveraLAN,thegroupnumberwillPO>defaulttozero.)Thismeansthatall instancesintheGalaxy+Owillbeinthesamecluster. # \[][! w15O11.2CSYSGEN Parametersfor SYS$PBDRIVERMOUInmostcases,thedefaultsettingsfor SYS$PBDRIVERshouldEObe appropriate,howeverseveralSYSGEN parametersareDO provided.'TwoSYSGEN parameterscontrol SYS$PBDRIVER:&O^ SMCI_PORTSand SMCI_FLAGS. bO11.2.1C SMCI_PORTSFO4The SMCI_PORTSSYSGEN parametercontrolsinitialload-GOingof SYS$PBDRIVER.This parameterisabitmasksuchROthatthebits0through25each representa controllerletter.YO=Ifbit0isset,PBAxwillbeloaded.(Thisisthedefaultsetting.WOIfbit1isset,PBBxwillbeloaded,andsoonallthewayupNOtobit25willcausePBZxtobeloaded.(ForOpenVMSAlphaIOGVersion7.2,we recommendleavingthis parameteratthe Odefaultvalueof1.aaKOLoading additionalportsallowsformultiplepathsbetweenHOGalaxy instances.*ForOpenVMSAlphaVersion7.2,havingJO5multiplecommunicationschannelsdoesnotprovideanyad-HOvantagesbecause SYS$PBDRIVERwill initiallynotsupportKOFastPath.*AfuturereleaseofOpenVMSwillprovideFastFO>Pathsupportfor SYS$PBDRIVER.WhenFastPathsupportKOisenabled, instanceswithmultipleCPUscangetimprovedCO throughputbyhavingmultiple communicationchannelsOHbetween instances.! O11.2.2C SMCI_FLAGSCO4The SMCI_FLAGSSYSGEN parametercontrols operationalIOaspectsof SYS$PBDRIVER.Theonly currentlydefinedflagTOisbit1.'ThiscontrolswhetherornottheportdevicesupportsHO=communicationswithitself.( SupportingSCScommunicationsXOtoitselfis primarilyusedfortest purposes.'Bydefault,thisbitLOwillbeturnedoffandthussupportforSCS communicationLOGlocallyisdisabledwhichsavessystem resources.+Thispa-ROrameterisdynamicandbyturningthisbiton,anSCSvirtual&Ocircuitshouldsoonform.! 2 O OBitMask 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$PBDRIVERifbootingintobotha5GalaxyandaCluster(SYSGEN Default).81=Load SYS$PBDRIVERifbootingintoaHGalaxy. O2 4;0=Minimalconsoleoutput(SYSGENdefault)41=Fullconsoleoutput, SYS$PBDRIVER:\willdisplayconsolemessageswhencreating5 communicationchannelsandtearingdown" communication channels. O ]\^  3O11.3CLANSharedMemoryDeviceDriver>OULocalAreaNetwork(LAN)communicationsbetweenJOOpenVMSGalaxy instancesare supportedbyanewEthernetCOLANsharedmemorydriver.*ThisLANdrivercommuni-MO^catestoother instancesinthesameGalaxythroughsharedGOmemory.,Theabilityto communicatetoanotherinstanceHOthroughsharedmemoryprovides performancebenefitsoverOh traditionalLANs.FOTheLANsharedmemorydriver, SYS$EBDRIVER,isloaded&Obythe followingcommand:Oa $mcr&sysman5O io%conn&!eba/driver=sys$ebdriver/noadapterWNOInafuturerelease,thisdevicedriverwillbeloadedau-HO tomatically.+ForOpenVMSVersion7.2,inorderforLANNO5 protocolsto automaticallystartoverthisLANdevice(EBAn,IOwherenistheunitnumber),the procedureforloadingMOthisdrivershouldbeaddedtothe configuration procedure:"O> sys$manager:syconfig.com >. WJOTheLANdriveremulatesanEthernetLANwithframefor-GOmatsthesameas Ethernet/IEEE802.3butwithmaximumHO5framesize increasedfrom1518to7360bytes.,TheLANJOdriverpresentsastandardOpenVMSQIOandVCI interfaceLOto applications.*AllexistingQIOandVCILAN applications"O>shouldwork unchanged. ^]_zP5O 12.2OpenVMS!Galaxy"Tips"and! TechniquesO TOBE SUPPLIED. _^`; o:OPartIV7 DevelopingProgramsForAnOpenVMSjGalaxyQOChaptersinthispartdefine interfacesoftheGalaxySoftwareIO^ ArchitectureonOpenVMSthatare importantto developingNO application programs.'Manyoftheconceptsare extensionsof=Othe traditionalsingle-instanceOpenVMSsystem. `_aS! )/O 13.2Locking! Programming! InterfacesTOOneofthemajorfeaturesoftheGalaxyplatformistheabilityMOtoshare resourcesacrossmultiple instancesoftheoperat-OOBingsystem.)Aswithanyshared resource,theneedarisestoLO synchronizeaccesstothat resource.)Theservices describedJOinthischapterprovide primitivesuponwhichacoopera-MOLtiveschemecanbecreatedto synchronizeaccesstoshared'O resourceswithinaGalaxy.> OA galaxylock:zisa combinationofaspinlockandamu-MOtex.)While attemptingtoacquireanownedgalaxylock,theSO5threadwillspinforashortperiod.*Ifthelockdoesnotbe-SOcome availableduringthespin,thethreadwillputitselfintoOOawaitstate.)Thisis differentfromSMP spinlocksinwhichSO>thesystemcrashesifthespintimesout,behaviorthatisnot$O acceptableinagalaxy. WOOGiventhenatureofgalaxylocks,theywillreside somewhereGOinsharedmemory.+Thatsharedmemorycanbe allocatedQO5eitherbytheuserorbythegalaxylocking services.*IftheLOuser allocatesthememory,thelockingservicestrackonlySOthelocationofthelocks.*Ifthelockingservicesallocatethe>O>memory,itismanagedonbehalfoftheuser. NNOUnlikeother monitoringcodewhichisonlypartoftheMONQOversionof execlets,thegalaxylock monitoringcodeisalwaysO5loaded.~! TIOThereareseveralroutinesprovidedto manipulategalaxyMOlocks.+TheroutinesdonotprovideanythingbutthebasicsPO5whenitcomestolocking.*TheyarealittlericherthantheRO spinlocksusedtosupportSMPbutfarlessthanwhatthelockOmanager provides. , a`b 2,O13.1CSYS$CREATE_GALAXY_LOCK_TABLEJOUThisservice allocatesagalaxy locktable structure..ThisLO structureisusedtomaintain informationaboutthesharedLOmemorysection,whichthisservicealsocreates.+ThefirstRO^calleroftheservicewithaunique locktablenamecreatestheMOsection.( Additionalcallersmapit.(Thissharedmemorysec-SOtioncontainsasetofgalaxylocks.*AlllocksresidinginthePOhsectionareofthesamesize.+Oncethe locktableiscreated,AOtheSYS$CREATE_GALAXY_LOCKservicecanbeusedto;Ocreateandallocatealockfromthetable.Wn8OTheflagsGLCKTBL$C_PROCESSand GLCKTBL$C_COSYSTEMspecifywhetherthesharedmemoryregionisHO5mappedintosystemspaceorprocessspace.-CreationofDOprocessspacesectionsrequirestheSHMEM privilege.EOCreationofsystemspacesectionsrequirestheSHMEM"O>andCMKRNL privileges.xEO"sys$create_galaxy_lock_table(name,accmode, section_size,3O section_type,prot, lock_size,handle) fv OO+ parameterbsizeb+(bytes)type+usage OFOname b8inputbyvalueaddressofthelocktableKname(ASCIZ)Oaccmode b4inputbyvalueaccessmodeofthelocktableOsectionsize8inputbyvaluevirtualsizeoflocksectionOSsectiontype4SinputbyvalueS glcktbl$c_processor glcktbl$c_;systemOprot b4inputbyvalue protectionap-pliedtolockPsectionO lock_size4inputbyvaluesizeofthegalaxylocksinethesectionOhandle b8outputbyreflocktable,handle OGCOReturnstatus:Z SS$_ACCVIO. SS$_BADPARAM SS$_CREATED SS$_IVLOCKID7 SS$_NOPRIV SS$_NOSHMEM SS$_NORMALCAAnystatusfromthesharedmemorysupportroutines bbac,O13.2CSYS$DELETE_GALAXY_LOCK_TABLEMOUThisservicedeletesagalaxylocktable..IftherearenoOOlongeranymappersofthe locktablesection,whichthetable&O maintains,itisdeleted.Z00Osys$delete_galaxy_lock_table(handle)7 OO+ parameterbsizeb+(bytes)type+usage OFOhandle b8inputbyvaluelocktablehandle OCOReturnstatus: SS$_BADPARAM. SS$_IVLOCKID SS$_IVLOCKTBL SS$_NOPRIV7 SS$_NOSHMEM SS$_NORMAL cbdu%O13.3CSYS$RESET_GALAXY_LOCKUOUThisservicesetsagalaxylocktoastate consideredtobein-AOvalidbytheSYS$ACQUIRE_GALAXY_LOCKservice.(ThisQOroutineisintendedtobeusedonlyonlockswhichresideinJO^sharedmemory allocatedbytheuserand initializedwithOSYS$INIT_GALAXY_LOCK.O%%Osys$reset_lock(handle,va)D OO+ parameterbsizeb+(bytes)type+usage OFOhandle b8inputbyvaluegalaxylockhandle Owva bw8winputbyrefwaddressofgalaxylock OCOReturnstatus:X SS$_BADLCKTBL. SS$_IVLOCKID SS$_LOCKINUSE SS$_NORMAL dce. w&O13.4CSYS$CREATE_GALAXY_LOCKOOUThisservices allocatesagalaxylockblockfroma locktable:OcreatedwiththeSYS$CREATE_GALAXY_LOCK_TABLEHOservice.(ItthenusesSYS$INIT_GALAXY_LOCKto initialize O^it.eGO%sys$create_galaxy_lock(lcktbl_handle,name,timeout,size,Oipl,rank,handle)! fZ OO+ parameterbsizeb+(bytes)type+usage OFO lcktbl_handlen4inputbyvaluelocktablehandleOwname bw8winputbyrefwaddressof16byteASCIZnameofgalaxy_lockOtimeout b4inputbyvaluedefaultwait&timeout(10t microsecondunits)O;size b;4;inputbyvalue;sizeoflock Oipl b4inputbyvalueIPLoflock(kernelmodePonly)Orank b4inputbyvaluerankoflock(notimple-emented)Ohandle b8outputbyrefhandleforthe,newlock OGCOReturnstatus:  SS$_ACCVIO. SS$_BADLCKTBL SS$_BADPARAM SS$_CREATED7 SS$_IVLOCKID SS$_IVLOCKTBL SS$_INSFMEMA SS$_NOPRIV SS$_NOSHMEM SS$_NORMAL edf;&O13.5CSYS$DELETE_GALAXY_LOCKAOUThisservicesusesSYS$RESET_GALAXY_LOCKtoinval-OOidatethegalaxylockandtodeleteit.*Thememoryforthe[Olockisnottrulydeleted,butisputonafreelistforlateruse.R((Osys$delete_galaxy_lock(handle)7 OO+ parameterbsizeb+(bytes)type+usage OFOhandle b8inputbyvaluegalaxylockhandle OCOReturnstatus: SS$_BADLCKTBL. SS$_IVLOCKID SS$_IVLOCKTBL SS$_LOCKINUSE7 SS$_NORMAL SS$_NOPRIV SS$_NOSHMEM !feg(O13.6CSYS$GET_GALAXY_LOCK_INFOROUThisservicereturnsall "interesting"fieldsfromthe specifiedOlock._HO sys$get_galaxy_lock_info(handle,name,timeout,size,ipl,Orank,flags)4! 0  OO+ parameterbsizeb+(bytes)type+usage OFOhandle b8inputbyvaluegalaxylockhandleOwname bw8woutputbyrefwaddressof16byteASCIZnameofgalaxy_lockOtimeout b4outputbyrefdefaultwait&timeoutOsize b4outputbyrefsizeoflock structure Ohipl bh4houtputbyrefhIPLoflockOrank b4outputbyrefrankoflockO[flags b[2[outputbyref[flagsfieldingalaxylock structure OCOReturnstatus:TG* SS$_IVLOCKID. SS$_NORMAL gfhQw'(O13.7CSYS$GET_GALAXY_LOCK_SIZEIOUThisservicereturnstheminimumandmaximumsizeofaQOgalaxylock.(Ifalockiscreatedwiththemaximumsize,theMOlockingserviceswillrecordacquireandrelease informationO^inthelock.a77O"sys$get_galaxy_lock_size(min_size, max_size)M # OO+ parameterbsizeb+(bytes)type+usage OFOmin_size4outputbyrefMinimumsizeofgalaxylockOwmax_size4woutputbyrefwMaximumsizeofgalaxylock OCOReturnstatus:> SS$_NORMAL C h gi 'O13.8CSYS$ACQUIRE_GALAXY_LOCKSOUThisserviceisusedtoacquire ownershipofagalaxylock.(IfSOthelockisfree,thecallerbecomestheownerandcontrolre-OOturns immediately.)Ifthelockisowned,basedontheinputSO^flagsandthetimeoutvalue,eitherthecallerwillwaitoran$Oerrorwillbe returned.MOThedefaultbehaviorwhenanattemptismadetoacquireaPOlockthatisowned,istospinfor10 microsecondsandthenPO5towait.-Ifawaittimeoutvaluewas specifiedinthecall,OOitisused.- Otherwisethetimeoutvaluesetinthelockby6OSYS$CREATE_GALAXY_LOCKorSYS$INIT_GALAXY_LO>LOCKwillbeused.)ThisbehaviorcanbechangedwiththeOinputflags.! pMOIfjustGLOCK$C_NOSPINis specifiedandthelockisowned,#Onospinwillbedone. WEOIfjustGLOCK$C_NOWAITis specifiedandthelockisMOowned,thecallerwillonlyspinonthelock..Ifatime-WO5outvalueis specifiedinthecall,itisusedasthespintime.NO Otherwise,thecallerwillspinfor10 microseconds.+IftheTOlockdoesnotbecome availableduringthespin,thelockisnot2O>acquiredand SS$_NOWAITis returned.NIfGLOCK$C_NOBREAKis specified, SYS$ACQUIRE_BO GALAXY_LOCKwillnotbreakthelock ownershipandOreturns SS$_NOBREAK.e;;Osys$acquire_galaxy_lock(handle,timeout,flags)*I OO+ parameterbsizeb+(bytes)type+usage OFOhandle b8inputbyvaluegalaxylockhandleOwtimeout bw4winputbyvaluewwaittime-out (overridesdefault)Oflags b4inputbyvalueGLOCK$C_NOWAIT&GLOCK$C_tNOSPINGLOCK$C_NOBREAK O*COReturnstatus: SS$_BADPARAM. SS$_BROKEN SS$_IVLOCKID SS$_IVLOCKOP7 SS$_IVLOCKTBLSS$_LOCK_TIMEOUT SS$_NOBREAKA SS$_NOWAIT SS$_NORMAL 0ihj)'O13.9CSYS$RELEASE_GALAXY_LOCKKOUThisservicereleases ownershipofagalaxylock.+BecauseLOagalaxylockcanbeacquiredmultipletimesbythesameOOowner(nested ownership),thelockisnotreleaseduntiltheOO^ ownershipcountgoestozero.(Ifthelock ownershipiscom-OOpletelyreleasedandthereareotherthreadswaitingforthe@Olock,theyarereleasedfromtheirwaitstates.S))Osys$release_galaxy_lock(handle)7 OO+ parameterbsizeb+(bytes)type+usage OFOhandle b8inputbyvaluegalaxylockhandle OCOReturnstatus:W SS$_IVLOCKID. SS$_IVLOCKOP SS$_IVLOCKTBL SS$_NORMAL ^ jikD  g )O13.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&Ey 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%theDr 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.AP 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.8d 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_NOBREAKEV 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 NOWAITKAi 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_LOCKCb 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.Ev 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%couldCN mean&that%the&data%this%lock&protects&is&corrupt. kjl 6O 14.2System!Events! Programming" InterfacesNO ApplicationscanregistertobenotifiedwhencertainsystemOOeventsoccur;forexample,whenaninstancejoinsthegalaxyUOBorifaCPUjoinsa configureset.(Ifeventsare registered,anKO applicationcandecidehowtorespondwhenthe registeredOeventsoccur. "l-kmgn=!O14.1C$SET_SYSTEM_EVENTOUSetSystemEventgGO Establishesarequestfor notificationwhenanOpenVMS Osystemeventoccurs.;OFormat: [BOSYS$SET_SYSTEM_EVENT(event,astadr,astprm,acmode,Oflags,handle)AOC Prototype:YAOint sys$set_system_event (unsigned int event,"void O( j*C astadr)(_ _unknown_params),intastprm,unsignedint=O5acmode,unsignedintflags,struct _generic_64 @*)5handle;>O Arguments:9O eventOOpenVMSO0usage:b event_codeOtype:blongword (unsigned)O$access:b$readonlyO mechanism:byvalueNKOEventcode indicatingthetypeofsystemeventforwhich.OanASTistobe delivered.+The event argumentisavalue?O5 indicatingwhichtypeofeventisof interest.EOEacheventtypehasasymbolicname.+The $SYSEVTDEF:Omacrodefinesthe followingsymbolicnames. p  OOSymbolicName Description OObSYSEVT$C_ADD_MEMBER bOneormoreOpenVMS! instanceshavejoinedtheOpenVMSGalaxyKsharing community.OSYSEVT$C_DEL_MEMBER OneormoreOpenVMS instanceshaveleft_theOpenVMSGalaxysharing community.!O&SYSEVT$C_ADD_ACTIVE_CPU &Oneormoreproces-$tsorshavebecomeactivewithinthisOpenVMS instance.#O SYSEVT$C_DEL_ ACTIVE_CPU#Oneormore processors havebecomeinactive$withinthisOpenVMSqinstance!OSYSEVT$C_ADD_CONFIG_CPU Oneormoreproces-$8sorshavebecomeactivewithinthisOpenVMS instance.!OMSYSEVT$C_DEL_CONFIG_CPU#MOneormore processors havebecomeinactivewithinthisOpenVMS6  instance. OQ :O astadriOOpenVMSusage:3 ast_procedureO]type:3] procedurevalueOaccess:)3callwithoutstack unwindingOP mechanism:+3Pby32-bitor64-bit referencePO NotificationASTroutinetoreceivecontrolafterachangein1OOpenVMSsystem configurationoccurs.:O astprmiOOpenVMSusage:3user_argO]type:3]quadwordOaccess:3readonlyOP mechanism:3PbyvalueWEOThequadwordAST parametertobepassedtotheASTOroutine.:O acmodeiOOpenVMSusage:3 access_modeO]type: 3]longword (unsigned)Oaccess:3readonlyOP mechanism:3PbyvalueNLOAccessmodeatwhichthesystemeventASTistoexecute. OThe acmode flag>isnotset.j@@OErrorswillbereturnedinthe followingcases:s I ` LIfquotasare exceeded,anerrorwillbe returned.+ItisI( importanttonotethatthisroutinewillreturnaner-Prorandwillnotretryanattempttogetquotaifquotais- exhaustedonthefirstattempt. `Y HYSeethe ConditionValuesReturnedsectionfortypesof*errorsthatcanbe returned. `1 1Ifthe1 astadr61argumentisomitted,andanewnotifi-Ecationobjectisbeingcreated, SS$_BADPARAMwillbe returned. `a aIfthea event5aargumentis incorrectly specified,SS$_'BADPARAMwillbe returned. `9 K9Iftheaccessmode parameterismore privilegedthantheMmodeofthecaller,themodeofthecallerwillbeused. ` If specified,the handle'Gargumentmustbe writeableIifromthemodeofthecaller.) SS$_ACCVIOisreturnedif#thisisnotthecase.HORequired Privileges9ONone.CORequiredQuota:OASTLM.EORelatedServicesGO$CLEAR_SYSTEM_EVENTO%%O ConditionValuesReturned! O SS$_NORMAL03Theservice completed successfully.O] SS$_ACCVIO63]Theservicecannotaccessthe locations23 specifiedbyoneormore arguments.O$ SS$_BADPARAM43$Oneofmore argumentshasaninvalid3qvalue.O SS$_EXASTLM13Theprocessexceededitsquotafor38 outstandingASTs.O SS$_INSFMEM23Thesystemdynamicmemoryisinsuf-.3ficienttocompletetheservice. mlnknA#O14.2C$CLEAR_SYSTEM_EVENTOUClearSystemEvent6  NOClearEventdoesnotallowyoutospecifyahandleandanPOevent.'Youmustpassazeroasoneofthese parameters.'YouRO5caneitherclearbyhandleorrequestthatalleventsfortheOuserbecleared.LORemovesoneormore notificationrequests previouslyestab-8OlishedbyacalltoSYS$SET_SYSTEM_EVENT.;OFormat:g==OSYS$CLEAR_SYSTEM_EVENT [handle], [acmode],eventAOC Prototype:;Ointsys$clear_system_event(struct _generic_64 *ahandle,8Ounsignedintacmode,unsignedintevent);>O Arguments::O handleiOOpenVMSusage:3 identifierO]type:3]quadword (unsigned)Oaccess:3readonlyOP mechanism:3Pby referencet JFOIdentificationoftheASTrequesttobecleared.+The han- O dleIargumentuniquely identifiestherequestandisreturnedAO5whenthe$SET_SYSTEM_EVENTserviceiscalled.,TheO handle=argumentmaybeomittedby specifyingazeroOaddress.:O acmodeiOOpenVMSusage:3 access_modeO]type: 3]longword (unsigned)Oaccess:3readonlyOP mechanism:3Pbyvalue/ EOAccessmodeofthesystemeventtobecleared.'The acmodeHOargumentisalongword containingtheaccessmode.+TheNO5valueoftheaccessmodeis maximizedwiththeaccessmodeOofthecaller.9O eventiOOpenVMSusage:3 event_codeO]type:3]longword (unsigned)Oaccess:3readonlyOP mechanism:3PbyvalueN OThe eventAargumentisavalue indicatingthetypeofsys-DOtemeventtobecleared.)SYSEVT$C_ALL_EVENTSmaybe2O5 specifiedtoclearalleventtypes.?O DescriptionNKOTheClearSystemEventserviceremovesoneormoreeventTOtypesor notificationobjects previously establishedbyacallto*O5the$SET_SYSTEM_EVENTservice.D3OAvalidrequest specifieseithertheV handleforaspecificPO notificationrequest,orisawildcardclearofall notifica-RO5tionobjectswhoseisaccessmodeisgreaterthanorequaltoO acmode .NOIftheM handle:argumentis specified,caller'saccessmodeUOmustbelessthanorequaltotheaccessmodeoftheobjecttoO5becleared.! NKOIfSYSEVT$C_ALL_EVENTSis specified,orthesetofeventsROenabledforthe object(s)becomesempty,the notificationobjectO5isdeleted.T**ORequiredAccessor Privileges8 ONoneC ORequiredQuota8 ONoneE ORelatedServicesE O$SET_SYSTEM_EVENTO%%O ConditionValuesReturned*! QO SS$_NORMAL03Theservice completed successfully.O] SS$_ACCVIO53]Theservicecannotaccessthelocation%3 specifiedbythehandle.O$ SS$_BADPARAM43$Oneofmore argumentshasaninvalid03qvalue,suchasaninvalidhandle.O SS$_NOSUCHOBJ03Norequestwasfoundthatmatches$38the descriptionsupplied nmo 6O 15.2Shared!Memory" Programming! Interfaces OA) SharedMemoryGlobalSectionmapssomeamountOOofmemorythatcanbeaccessedonall instancesinashar-sharedmemoryglobalsection.L "EOIncontrasttomemoryresidentsectionstheReservedOOMemoryRegistryisnotusedtoallocatespacefor galaxywideHO5 sections.)SharedmemoryisnotusedfornormalOpenVMSFOpaging operationsand thereforeneednotbe reserved. 5poqJ  O15.2CSystemServices$O15.2.1CEnhancedServicesJO4The followingsystemserviceshavebeenenhancedtorec-Oognizethenew) sharedmemoryglobalsectionflagO SEC$M_SHMGS:l ` SYS$CRMPSC_GDZRO_64 `U USYS$CREATE_GDZRO `  SYS$MGBLSC_64 `S S SYS$DGBLSCJOThe followingsystemserviceswereenhancedtoworkwith=Osharedmemorybutno interfaceswerechanged: `  SYS$DELTVA `U U SYS$DELTVA_64 ` SYS$CREATE_BUFOBJ `S SSYS$CREATE_BUFOBJ_64 ` SYS$DELETE_BUFOBJb! `8:O15.2.2CNewSectionFlagSEC$M_READ_ONLY_SHPTAO4ThenewsectionflagSEC$M_READ_ONLY_SHPTisrec->OognizedbytheSYS$CREATE_GDZROand SYS$CRMPSC_ROGDZRO_64 services.'Whenthisbitisset,itdirectsthesystemPO=tocreatesharedpagetablesforthesectionthatallowonlyOOreadaccess.*Thisfeatureis particularlyusefulinanenvi-JOronmentwhereamemoryresidentorGalaxysharedsectionDOGisusedbymanyreadersbutonlyasinglewriter. NJOWhenyoumapaGalaxysharedormemoryresidentsectionROthathasan associatedsharedpagetablesection,youhavetheO5 followingoptions:D ' OOxSharedpagetablesDesired +ac-xcess O3READONLY:READ KAND /ORWRITE:O_nonecreated&3_Donotsetthe SEC$M_WRT&3flaginthemaprequest.*3&Privatepagetableswillal--3twaysbeused,evenifyouare*3 specifyingasharedpageta-+3bleregionintowhichtomap3\thesection._SettheSEC$M_ WRTHflaginthe map 0re-~quest.PrivateEpagetableswill-always {beused,evencifyou arespeci-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,3section.#Ifyoudo,theerror"3status SS$_IVSECFLGis3e returned. Setthe SEC$M_ g WRT flaginthe Pmap re-quest. eThesharedpageMtablesectionwillbe6used formap-pingkifyouspec-ifyaTsharedpagetable<regionintowhich%tomap rthesec- tion.Oreadaccess&3Donotsetthe SEC$M_WRT+3flaginthemaprequest."The,3"sharedpagetablesectionwill)3pbeusedformappingifyou)3specifyasharedpagetable+3 regionintowhichtomapthe3Xsection.SettheSEC$M_ "WRTpflaginthe  map Xre-quest.Ensure@thatprivatepage)tablesvwillbeused.Donot_spec-ifyasharedGpagetableregion0into}whichtomap thefsec-tion.IfyouNdotheerrorstatus7 SS$_ IVSECFLG isre-!turned. O:! !MB!Notes !MHJ"SharedpagetablesforGalaxysharedsectionsarealso?" implementedasGalaxyshared sections.,Thisim-G"pliesthattheyalloweitherreadaccessonlyonallDT#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.'IfyouwantL9&tousethisservicetocreateasectionwithsharedpageI&tablesforreadonlyaccess,youmustuseprivatepageC&tablesandyoucannotspecifyasharedpagetable5C'regionintowhichtomapthesection. ' 'qpr? ,O15.3C GalaxywideGlobalSectionsIOUTheSHMEM privilegeisrequiredtocreateanobjectinNOGalaxysharedmemory.'Therighttomaptoanexistingsec-MOtionis controlledthroughnormalaccesscontrol mechanisms.GO^SHMEMisnotneededtomapanexistingsection.,NoteBOthattheVMS$MEM_RESIDENT_USER identifier,whichisNOneededtocreateanordinarymemoryresidentsectionisnot.Ohrequiredfor galaxywide sections.%! GOCreatingandmapping galaxywidememorysectionsisac-LO complishedthroughthesameservicesusedtocreatememoryLO5resident sections.*The followingservicesnow recognizetheO SEC$M_SHMGSflag: bSYS$CREATE_GDZRO.SYS$CRMPSC_GDZRO_64 SYS$MGBLSC_64 SYS$DGBLSC!N4OSYS$CREATE_GDZROandSYS$CRMPSC_GDZRO_640Ocanalsoreturnnewstatuscodes.# Tobe supplied-more O5 detailsaboutthese:o"! QEOSS$_INV_O0SHMEM)Sharedmemoryisnotvalid.NO SS$_INSFRPGS Insufficientfreesharedpagesorprivatepages.RO$ SS$_NOBREAKAGalaxylockisheldbyanothernodeandwasnotqbroken.O SS$_LOCK_O8TIMEOUT&AGalaxylocktimedout.#N=O$INSTALL LIST/GLOBALand$SHOWMEMORYalso+Oknowabout glaxywide sections. Tobe supplied-some2O5 additional documentationaboutthese.$! NO Galaxywidesectionsareusingtheirownnamespace.'JustasPOyoucouldalwaysusethesamenametoidentifysystemglobalLO5sectionsandgroupglobalsectionsforvariousownerUICs,NOyoucannowalsohave galaxywidesystemglobalsectionsandJO galaxywidegroupglobalsectionsallwiththesamename.t%JJO Galaxywidesectionsalsohavetheirownsecurityclasses:h&A>GLXSYS_GLOBAL_SECTION(GLXGRP_GLOBAL_SECTION'NHOThesesecurityclassesareusedwiththe$GET_SECURITY,>O $SET_SECURITYsystem services,andtheSET/SHOW"O5SECURITYDCL commands:(OOThesenewsecurityclassesareonlyvalidinaGalaxyenvi-HOronment.'Theyarenot recognizedona non-galaxynode.)! ROYoucanonlyretrieveandaffectsecurity attributesofgalaxy-OOwideglobalsectionsiftheyexistonyoursharing instance.*\0`GOAuditmessagesfor 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+NJONotethe"Objectname"record:+theobjectname displayedMOhereuniquely identifiesthesectionintheOpenVMSGalaxy.(O5Thefieldsareasfollows:h,>O[47]?K(onlyforgroupglobal sections) identifiesthe0K0UICgroupofthesectioncreator.OWAY_ __ _D99DDB03_ O0$7KAn identifierforthesharing community.Oq MY_SECTION=KqThenameofthesectionas specifiedbytheKuser.x- NQOTheusercanonlyspecifythesectionnameandclassforre-ROqueststosetorshowthesecurityprofile.(TheUICisalwaysKO5obtainedfromthecurrentprocessandthe communityiden-MOtifierisobtainedfromthe communityinwhichtheprocessO executes.<. QOTheoutputfora galaxywidesystemglobalsectiondiffersonlyQOinthefields"Objectclassname"and"Objectsname".(Theob-PO5jectnameforthistypeofsectiondoesnotincludeagroup Oidentificationfield:/dOObjectclassO0name:GLXSYS_GLOBAL_SECTION=OObjectname:WAY_ __ _D99DDB03_0$SYSTEM_SECTION ,$/ ImportantSecurityNotes Z,CSecurity attributesfora galaxywidememorysectionG mustappear identicaltoaprocessnomatteronwhat&einstanceitis executing.GThiscanbeachievedbyhavingall instancespartici-E7patinginthissharing communityalso participatein?a "homogeneous"OpenVMSClusterwhereallnodes/sharethesecurityrelatedfiles:05Y SYSUAF.DAT, SYSUAFALT.DAT(systemautho-Y(rizationfile),YRIGHTSLIST.DAT(rights database).YVMS$OBJECTS.DAT(objects database)A^In particular, automatic propagationof protectionBchangestoa galaxywidesectionrequiresthatthe?samephysicalfile(VMS$OBJECTS.DAT)isusedby"hallsharing instances.JIfyour installationdoesnotsharethesefilesthrough-D:outtheGalaxy,thecreatorofa galaxywidesharedHsectionmustensurethatthesectionhasthesamese-Fcurity attributesoneach instances.(ThismayrequireDmanual intervention.  rqs1 g7O 16.2CPU! Management! Programming" Interfaces0O Tobe supplied:'includeanintro. 4s/rt2z"O16.1CSYS$CPU_TRANSITIONGOUOnAlphasystems,changesthecurrent processingstateOOofaCPUinthe configuresetofthecurrentsystemoranBO unassignedCPUinanOpenVMSGalaxyconfiguration.EO^Thisservice completesasynchronously.,For synchronous;O completion,usethe$CPU_TRANSITIONWservice.3NIOThisserviceaccepts64-bit addresses., ParameterandbitGO definitionsareresolvedin$CSTDEFinthe appropriateO5STARLETlibrary.4OFormatOnode_id,flags,efn,iosb, astadr_64, astprm_64P5M&O ArgumentsO4 tran_code6iOOpenVMSusage:3longwordO]type:3]longword (unsigned)Oaccess:3readonlyOP mechanism:3Pbyvalue 7 NQO Identifier specifyingthetypeofstatechangetobe initiated$OonthetargetCPU.The tran_code#sargumentisalongword6O5 containingoneofthe followingvalues:Y8 / OOSymbolicName3 Description OObCST$K_CPU_STOP53bThetargetCPUistoberemovedfrom63theactivesetandhaltedintoconsole53mode."Itremainsinthe configureset&3Kofthecurrent partition.EOCST$K_CPU_MIGRATEThetargetCPUisremovedfromthe83 configuresetofthelocal partitionand;3_theconsoleis requestedtoaddittothe73 configuresetofthe partition specified33innode_id.$IftheCPUis currently63Hintheactiveset,itis automatically23broughttoconsolemodethroughthe*3CST$K_CPU_STOPfunctionfirst.O\CST$K_CPU_START33\ThetargetCPUis requestedtoexit83consolemodeandjointheactivesetof23thecurrent partition.#TheCPUmust53Ealreadybepartofthe configureset.HOCST$K_CPU_FAILOVERTheCPUisassignedadefaulttarget/3  partitionwhereitwill automati-43Zcallymigrateonsystemfailure.#This53 assignmentpersistsuntilitissuper-03seded.$Toremovean assignmentor33B partitionname,thecurrent partition$3IDshouldbe specified. O:9O cpu_id:iOOpenVMSusage:3longwordO]type:3]longword (unsigned)Oaccess:3readonlyOP mechanism:3Pbyvalue;! qLO IdentifieroftheCPUwhosestateistobe modified.'The* cpu_ O idFargumentisalongwordnumberinthe supportedrangeHO5of individualCPUsfrom0to SYI$_MAX_CPUS-1.)InaOOGalaxy,thisCPUmustbeinthe configuresetofthelocalRO partitionornotassignedtoanyother partitions.'ThesymbolicBO>values,CST$K_ANY_LOCAL_CPUcanbeusedincertainUOtypesof transitionstoallowthenext available processoroftheEO appropriatetypebeusedinsteadofaspecificone.;<O node_id=iOOpenVMSusage:3longwordO]type:3]longword (unsigned)Oaccess:3readonlyOP mechanism:3Pbyvalue>! WHO IdentifierofthetargetGalaxy partitionin CST$K_CPU_6OASSIGN,CST$K_CPU_FAILOVER,or CST$K_CPU_#O5MIGRATE transition.,The.5 node_id 5argumentisalong-IOword containinganumberinthe supportedrangeofIDsPOprovidedbytheconsoleforthecurrenthardware platform.'If O>the> nodename#> parameteris specified,> node_id?>isignored.9?O flags@iOOpenVMSusage:3 longword_maskO]type:3]longword (unsigned)Oaccess:3readonlyOP mechanism:3PbyvaluexANCOOptionsselectedfortheCPUstate transition.)Them flags Car-LOgumentisalongwordbitvectorwhereinabit correspondsMO5toanoption./Onlythebits specifiedbelowareused; theJO remainderofthelongwordbitsarereservedandmustbe O0. B N;OEachoption(bit)hasasymbolicname.(The flags]argumentPOis constructedby performingalogicalOR operationusingthe7O5symbolicnamesofthe followingoptions:*C$D  OOSymbolicName3 Description OObCST$V_CPU_DEFAULT_O CAPABILITIES83bAtthe completionofthe transition,the73CPU'suser capabilitiesaresetbackto83thedefaultsystemvalue.!Ifthisoption43Kisnot specified,modifiedusercapa-13bilitiesare maintainedacrossSTOP43andSTART transitionsaslongasthe133CPUremainsinthelocal partition3 configureset.OCST$V_CPU_ALLOW_OHORPHANS43The transitionistobeallowedeven93Hthoughitwillleaveatleastonethread73inthesystemunabletoexecuteonany$3CPUintheactiveset. O7E  O efnFiOOpenVMSusage:3 ef_numberO]type:3]longword (unsigned)Oaccess:3readonlyOP mechanism:3PbyvalueBG SOTheeventflagtobesetwhenthestate transitionattempthasO completed.*The  efn45argumentisalongword specifyingtheQO5numberoftheeventflag;however,thisserviceonlyusestheO low-orderbyte.H NDOWhenyouinvoke$CPU_TRANSITION,the specifiedeventSOflagiscleared;whenthe operationis complete,theeventflagO5isset.8IO iosbJiOOpenVMSusage:3io_status_areaO]type:3]IOSB structureOaccess:3writeonlyOP mechanism:+3Pby32-bitor64-bit referenceK! WQOTheI/Ostatusareatoreceivethefinal completionstatusof*Othe transition operation.(Theq iosb'1argumentisthe32-bitorQO564-bitvirtualaddressoftheI/Ostatusarea.*TheI/OstatusVOarea structureis32bytesinlength;its definitioncanbefoundGOin$IOSBDEFin STARLET.MLBformacroandinthefile3O> IOSBDEF.HinSYS$STARLET_C.TLBforC.L! NGOWhenyoucall$CPU_TRANSITION,theI/OstatusareaisTOcleared.'Afterthe transition operationis complete,theblockis O5modifiedasfollows:M OOSymbolicName3 Description OOb iosb$w_status13bThefirstwordcontainsthecondi-63tionvaluereturn, indicatingthefinal13 completionstatusofthe operation.93wThefirstbitinthesecondwordofthe63IOSBissetonlyifanerroroccurred13duringthe operation;the remaining3_bitsarezeroes. Oz=NO astadr_64OiOOpenVMSusage:3 ast_procedureO]type:3] procedurevalueOaccess:)3callwithoutstack unwindingOP mechanism:+3Pby32-bitor64-bit referenceP! OOTheASTroutinetobeexecutedwhenthe requested transitionJOattempthas completed.)The astadr_64argumentisthe32-VO5bitor64-bitvirtualaddressofthisroutine.'IfyouspecifytheLO astadr_64 argument,theASTroutineexecutesattheaccessDOmodefromwhichthestate transitionwas requested.=QO astprm_64RiOOpenVMSusage:3user_argO]type:3]quadwordOaccess:3readonlyOP mechanism:3PbyvalueSZKOThequadwordAST parametertobepassedtotheASTrou-Otine.*TUO Description$O4Thestate transitionin4 tran_id)4is requestedforthetargetO cpu_id d.mVCCOACPU currentlyintheactivesetcan transition:WA ` HTotheSTOPPEDstate;removedfromtheactivesetandD(leftinthe configureset,haltedinconsolemode.eX;;OACPUinthe configuresetcan transition:Y r ` GTotheACTIVEstate;warmrebootedandafullmemberD(oftheSMPactivesetonthe requesting partition. ` EToanother partitionthrough reassignmnet;thetargetJCPUisremovedfromthe configuresetandaddedtothe;Y configuresetofthe partition specifiedbyY node_id Y.6Z!  FOCPU state transitionis a two-phase operation intheIOOpenVMS schedulingmodel.+Thisservice initiatesthere-NO5questintheprocesscontextofthecallerandreturnsthePOsetupstatusintheservice conditionvalue.(Phase2proceedsOasynchronously;the 0 efn andq iosb& argumentscanbeusedtoPO>indicatethe completionofthe transitionthroughthestandardMOwaitsystem services.* Additional notificationofthecomple-EOtioncanbemadethroughtheOpenVMSAST mechanisms*OHusingaroutine specifiedin2H astadr_64Handa user-suppliedO parameterinC astprm_64 .[ORequired PrivilegesCO4Thecaller musthavethe CMKRNL privilegeto call6OSYS$CPU_TRANSITIONtomodifyCPUstates.E\ORelatedServicesD]O$CPU_TRANSITIONWO^%%O ConditionValuesReturned_! O SS$_NORMAL/3Theservice completed successfullyO] SS$_BADPARAM43]Oneofmore argumentshasaninvalid53valueorthe specifiedCPUisnotin3the configurationOq SS$_ACCVIO63qTheservicecannotaccessthe locations13 specifiedbyoneormore argumentsO8 SS$_NOCMKRNL138CallerdoesnothaveCMKRNLprivi-/3legeneededtocomplete operationO SS$_INSFARG,3Fewerthantherequirednumber03Mof argumentswere specifiedorno#3 operationwas specifiedCOSS$_TOO_MANY_ARGSMore argumentswere specifiedthan(3bareallowedbytheserviceO SS$_INVCOMPID43ThetargetgNodeIDisnotvalidin3)this configurationO SS$_CPUNOTACT53The specifiedCPUisnotpartofthe,3current partitions'sactivesetOj SS$_NOSUCHCPU83jThe specifiedCPUdoesnotexistinthe/3currenthardwareconfiguration,or:3isnotinthe configuresetofthelocal3S partitionO SS$_CPUSTARTD33The specifiedCPUisalreadyinthe;3 localactiveset,orisintheprocessof3g joiningitO SS$_CPUSTOPPING*3 The specifiedCPUisalready.3/ STOPPEDorinthe processingof#3| leavingtheactiveset*` *tsua  O16.2C$CPU_TRANSITIONWNOUOnAlphasystems,changesthecurrent processingstateofaNOCPUinthe configuresetoran unassignedCPUinaGalaxyMOconfiguration.(Thisservice completessynchronously;thatis,SO^itreturnstothecalleronlyafterthefinal completionstatus(Oofthe operationisknown.'bHOInallother respects,$CPU_TRANSITIONWis identicaltoDO$CPU_TRANSITION.Forallother informationabouttheEO5$CPU_TRANSITIONWservice,refertothe descriptionof,O$CPU_TRANSITIONinthismanual.^c44OThisserviceaccepts64-bit addresses.*deOFormat;O4SYS$CPU_TRANSITIONWtran_id,cpu_id, nodename,>Onode_id,flags,efn,iosb, astadr_64, astprm_64 utvfw5O 17.5 Configuration# Management# ProgrammingOr Interfaces.O Tobe supplied:' Additionalinfo.*g vuwhO17.1C SYS$GETSYIAOUSYI$_GALAXY_PLATFORMreturns1ifyouarerunning/OonaGalaxy platform,0ifnot.i! zEOSYI$_GALAXY_MEMBERreturns1ifyouareamemberof5OaGalaxysharing community,0ifnot.fj<Y< /PFN=FREEvalidatePFNdbforeachpageintheYfreelistBY/PFN=BADvalidatePFNdbforeachpageinthebadYElist=Y /PFN=UNTESTEDvalidatePFNdbforeachpageinYtheuntestedlist=YO/PFN=ALLvalidatePFNdbforeachpageintheYPMAP3Y /PFN=(x,y)tovalidatemultiplelistsWu -EbIf/PFNisgivenwithout/ALL,/IDENT,or /ADDRESS,CthenPFNlistsfromthelastSHM_CPPaccessedare validated.L`3.:AddedSHOWSHM_REG.DefaultisabriefdisplayofallE SHM_REGs,withthe following parameteror qualifiers:vJX*Y/ALLdetaileddisplayofall.Y(/IDENT=ndetaileddisplayofone0Y /ADDRESS=xdetaileddisplayofone*Ynamedetaileddisplayofone:`Y4.:Added/GLXSYSand/GLXGRPtoSHOWGSD.D`5.:AddedSHOWGMDBtodisplaythecontentsofthe(1GMDBandallNODEBblocks. syxzYw%//O 19.2OpenVMS!Galaxy"Device!Drivers zy{x! 2,O19.1CDirectDMAWindowChangesMOUTherearechangesplannedfortheusageoftheDirectDMAGOwindowforPCIdriversstartinginOpenVMSAlpha7.2.LOThesechangeswererequiredtosupporttheGalaxySoftwareEO^ architectureonOpenVMSandmemoryholes.)ThechangeHOinvolvesmovingtheDirectDMAwindowawayfromphysi-LOcalmemorylocation0.'ThisdocumentshouldprovideenoughKOh backgroundand informationforyoutoupdateyourdriver.LONotethatthisdocumentdoesn'ttalkaboutbus addressableOpool(BAP). m{z|ky AFO19.2CHowPCIDirectDMAWorksPriortoOpenVMSV7.2JOUOnallPCIbased machines,thedirectDMAwindowbeginsLOat (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 addressesagainsttheMOlengthofthewindowreturnedbycalling ioc$node_datawithJO5theioc$k_direct_dma_sizefunctioncode.(ThisassumesthatNOthewindowonthememorysidestartsatzero.(Anotherpop-FOularmethodfor determiningwhethermap registersareJO> necessaryinvolveslookingatmmg$gl_maxpfn.)ThisisalsoKOnotlikelytowork correctlyinOpenVMSVersion 7.2-EFT3.  9Foramuchbetterpictureand explanation a Seethe9 WritingOpenVMSDeviceAlphaDriversinCbook. D |{}{L :WGO19.3CHowPCIDirectDMAWorksinOpenVMSVersion7.2LOUGalaxyandmemoryholeconsiderationsforceustopossibly?Ochangethe 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|! MOItisunknownfromthedrivers perspectivewhereinmemoryJOthebaseoftheDirectDMAwindowwillbe.+Simplycom-KO5paringabufferaddressagainstthelengthofthewindowTOwillnolongerbe sufficientto determineifabufferiswithinGOtheDirectDMAwindow.(Also, comparingagainstmmg$gl_SO>maxpfnwillnolonger guaranteethatallofpooliswithintheFOwindow.+Thecorrectcelltocheckismmg$gl_max_node_NOpfn.' Additionally, alignmentconcernsmayrequireanslightlyKOH differentoffsetbe incorporatedintophysicalbusaddressO calculations. }|o}! wE=O19.4C IOC$NODE_DATAChangestoSupportNon-zero'(DirectDMAWindowsPOTo alleviatethisproblem,newfunctioncodeshavebeenaddedROtoioc$node_data.+HereisalistofallthecodesrelatingtoHO^directDMA,anda descriptionofwhatthedatameans.(~ OIOC$K_DIRECT_DMA_O0BASE43ThisisthebaseaddressonthePCI630side,orbusaddress.#Thereisasyn-13~onymforthisfunctioncodecalled3IOC$K_DDMA_BASE_BA.COEIOC$DIRECT_DMA_SIZEOn non-Galaxy machines,thisre-03turnsthesizeofthedirectDMA13window(in megabytes).#Onasystem/3-wherethedirectDMAwindowdoes43{notstartatzero,thedatareturned.3iszero,implyingnodirectDMA3windowsexist.KOIOC$K_DDMA_WIN_SIZEOnallsystems(asofx6jh)thiswill43alwaysreturnthesizeofthedirect'3+DMAwindow(in megabytes).OIOC$K_DIRECT_DMA_OBASE_PA43Thisisthebasephysicaladdressin33memoryofthedirectDMAwindow.!It53?isprobablycloselyrelatedtommg$gl_/3 min_node_pfn,butmaybeslightly23 differentdueto alignment concerns.*W>OTheaddressreturnedwiththeIOC$K_DIRECT_DMA_LOBASE_PAcodeis necessarytocomputethe offset.(Thisusu-LO5allyusedtobethe1Gb differencebetweenthememoryPAQOandthebus address).Theoffsetisdefinedasthesigneddif-KOferencebetweenthebasebusaddressandthebasememory9O>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 Sf 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_nsn_fig s_psp_fig s_ese_figclust_satglx_scsiak_securityfind_a_home new2 new3 new4newcgconfig sym_clmfsym_1lmfsym_2lmfsym_3lmfsym_4lmfsym_5lmfsym_6lmfsym_7lmfsym_8lmfsym_9install_where_licensecreat_partneeds_chaptconfigsconfig1configs2configs3hw_reqsgalc_exset_upgnsym_3term_s thumbeisa_dev syd inst lic fwgsym_9gsym_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 zz2cp_4100cpu_4100ioa_cpuioc_4100nwc_4100mem_4100 zz3bean_chaptmanage_part gcu gui_5 gui_6 gui_8 gui_9gui_10gui_11gcu_new2 gui_2 gui_4gui_12gui_13gui_14gui_15gui_16gui_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 portssmci_flgslanshm_1tech_tipsdevelop_partlocking_api_chapt sym_g sym_h sym_j sym_k sym_l sym_m sym_n sym_o sym_plck_mssgevents_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 ,+-AaAO5.1BStep1:*Choosea Configurationand Determine (Hardware RequirementsMbJOQuickSummaryofan AlphaServer8400Galaxy ConfigurationO49slotsfor:cI/Omodules(Memorymodules4 Processormodules(2CPUspermodule)X..OConsolelineforeach partition:Ac/StandardUARTforfirst partition4(KFE72-DAforeach additional partition:O Rules:5MusthaveanI/Omoduleper partition&(Maximumof3I/OmodulesAMusthaveatleastoneCPUmoduleper partition}MS#OExample Configuration10O42 partitions,8CPUs,12GBmemoryU++9slots allocatedasfollows:r2I/Omodules04 Processormodules(2CPUseach))l3Memorymodules(4GBeach)|MR#OExample Configuration2/O43 partitions,8CPUs,8GBmemoryU++9slots allocatedasfollows:r3I/Omodules04 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"AaAO6.1BStep1:*Choosea Configurationand Determine (Hardware Requirements#MwJOQuickSummaryofan AlphaServer8200Galaxy Configuration-O4Onlyonepossibleconfiguration.v$hL ` Two instancesonly `O O5slotsfor:% .YTwoCPUmodules(twoCPUseach) O YOTwoI/Omodules  YOnememorymoduleE&! V0O6.1.1BUsingtheOpenVMS GalculatorJO4TheOpenVMS Galculatorisan applicationprogramyoucanQOuseto determinetheGalaxy configurationthatbestsuitsyour(Oneeds.'Itis availableat:(O=http://www.openvms.digital.com'NIOTocreateanOpenVMSGalaxyVersion7.2 computingenvi-JOronmentonan AlphaServer8200,the Galculatorstepsyou:O5throughthe followinghardware requirements:,(@ ` EOneI/Omodule(I/OmoduleoftypeKFTIAorKFTHA)(foreach partition ` ;AtleastoneCPUmoduleforeach partition `' C'A dedicatedserialconsoleportforeach partition),BbThe AlphaServer8200providesabuilt-inUARTforLthefirstconsoleline.*Each additionalconsolerequiresamoduleset.*,IbTheonlyhardwarerequiredforGalaxy operationthatisJnotinthetypical AlphaServer8200 configurationisthe'KFE72-DAconsole subsystem.+FbTheKFE72-DAmodulesetisthesetofEISA-busmod-4ulesthat establishtheconsoleport. `: F:AdisplaydevicefortheOpenVMSGalaxy ConfigurationUtility.@,! CbCompaq recommendsanAlphaorVAX workstationrun-Aning DECwindowsoraWindowsNT workstationwithFan Xterminal emulator.(Formore informationaboutthe7lOpenVMSGalaxy ConfigurationUtility,seelChapter9.*,/lO-eHOOpenVMSV7.2 customersmightwanttousethe followingOoptional hardware:*.!  ` LPluginunits(PIU)forI/O expansionfromanI/Omodule((PCIorXMI) ` JI/Oadaptersfornetwork,storage,or traditionalcluster interconnects `  AdditionalCPUs/ 6O6.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. Q4EDFnWO9.1BGCUTour?OUTheGCUcanperformthreetypesof operations:+@ ` CCreateofGalaxy configurationmodelsorasingle-(instanceGalaxy. ` ?ObserveactiveGalaxy performanceand resources. `' C'InteractwithactiveGalaxyresourceconfigurations.R! (GOMostGCU operationsare organizedaroundthemainob-HO servationwindowandits hierarchicaldisplayofGalaxyLO5 components.'The observationwindowprovidesaportholeintoKOaverylargespace.*The observationwindowcanbepannedMOandzoomedasneededtoobservepartortheentireGalaxyQO>configuration.'ThemaintoolbarcontainsasetofbuttonsthatGOcontrol workspacezoom operations.) WorkspacepanningisPO controlledbythe horizontalandvertical scrollbars; workspaceLOHslidingisachievedbyholdingdownthemiddlemousebut-LOtondownasyoudragthe workspacearound.(This obviously5Oassumesyouhavea three-buttonmouse.? KOThevariousGCU operationsareinvokedfrompulldownorIOpopupmenu functions.)General operationssuchasopeningLO5andclosingfiles,andinvokingexternaltools,areaccom-NOplishedusingthemainmenubarentries.( OperationsspecificFOto individualGalaxy componentsare accomplishedusingFO>popupmenusthatappearwheneveryouclicktherightJOmousebuttonona component displayedinthe observationOwindow.WHOInresponsetomany operations,theGCUdisplaysaddi-OOtionaldialogboxes containing information,forms,editors,orJO5prompts.*Errorand information responsesare displayedinPOpopupdialogboxesorinsidethestatusbaralongthebottomMOofthewindow, dependingontheseverityoftheerrorand'O> importanceofthemessage.8O9.1.1BCreatingGalaxy ConfigurationModelsLO4YoucanusetheGCUtocreateGalaxy configurationmodelsBOandasingle-instanceGalaxyonanyAlphasystem.C KOWhenviewingtheactiveGalaxy configurationmodel,directKO manipulationofdisplayobjects (components)mayaltertheHO5runningconfiguration.(Forexample,draggingaCPUcom-QOponentfromitscurrentlocationanddroppingitontopofaJO differentinstance componentwillinvokea managementac-MO>tion procedure,that reassignstheselectedCPUtothenewPO instance.)Atcertaintimesthismaybea desirable operation;LOhowever,inother situationsyoumightwantto reconfigureJOHyourGalaxyallatonceratherthan componentbycompo-NOnent.)To accomplishthis,youmustcreateanofflineGalaxyO configurationmodel.NMOTocreateaGalaxy configurationmodel,wemuststartwithQOanexistingmodel, typicallytheactiveone,alteritinsome.O5manner,andsaveitinafile.nDDOStartingfromtheactiveGalaxy ConfigurationModel:! zI`1.:PresstheENGAGEbuttonsuchthatthemodelbecomesG( DISENGAGED.Thebuttonshouldturnfromredtowhite,Handits appearanceshouldbepoppedoutward.'Whendis-Fengaged,allCPU componentsinthedisplaywillturnL2redasan indicationthattheyarenolongerengaged.(DoHnotpanic,theyhavenotbeen shutdown!)Themodelhas(simplybeentaken off-line.L`c2.:AltertheCPU assignmentsbydragginganddroppingin-LdividualCPUsontopofthe instancesyouwishtoassignthemto.K`3.:When finished,youcaneither re-engagethemodel,orMsavethemodelinafileforlateruse.)Wheneveryoure-EDengageamodel, regardlessofwhetherthemodelwasLderivedfromtheactivemodelorfroma file-basedmodel,EtheGCUwillcomparetheactivesystem configurationMNwiththe configurationproposedbythemodel.'ItwillthenCprovideasummaryof managementactionsthatwouldJneedtobe performedtoreassignthesystemtothenewLWmodel.)Iftheuserapprovesoftheactions,theGCUwillBcommencewith executionoftherequired managementK actionsandthe resultingmodelwillbe displayedasthe&aactiveandengagedmodel.! _QOThereasonforcreatingofflinemodelsistoallow significantMO configurationchangestobe automated.'Forexample,youcanKO5createmodels representingthedesiredGalaxy configurationMOat differenttimesandthenengagethemodels interactively)Oby followingthis procedure. oO9.1.2B ObservationLO4TheGCUcandisplaythesingleactiveGalaxy configurationNOmodel,oranynumberofofflineGalaxy configurationmodels.NOEachloadedmodelappearsasanitemintheModelmenuonMO=thetoolbar.*YoucanswitchbetweenmodelsbyclickingtheOdesiredmenuitem.( @OTheactivemodelisalwaysnamedGLX$ACTIVE.GCM.UOWhentheactivemodelisfirstloaded,afilebythisnamewillNO5existbrieflyasthesystem synchronizesthemodelwiththeOsystem hardware.NSOWhenamodelisvisible,youcanzoom,pan,orslidethedis-LOplayasneededtoviewGalaxy components.(UsethebuttonsSO5ontheleftsideofthetoolbartocontrolthezoom functions.R((OThezoom functionsinclude:0}OGalacticzoom:KZoomtofittheentire component hierarchy$K0into observationwindow.OZoom1:12KZoomtothe componentnormalscale.O$Zoomtoregion:K$Zoomtoaselectedregionofthedisplay.OZoomin$KZoominby10percent.OZoomout%KZoomoutby10percent.$ NOPanningis accomplishedbyusingtheverticaland horizontalOO scrollbars.)Slidingisdonebypressingandholdingthemid-MO5dlemousebuttonanddragging (sliding)thecursorandtheOimage.3!  %O9.1.2.1CLayout ManagementHO)The AutomaticLayoutfeaturemanagesthe componentlay-SOout.'Ifyoueverneedtorefreshthelayoutwhilein AutomaticIOLayoutmode,simplyselecttheroot (topmost) component. MOToalterthecurrentlayout,selectManualLayoutfromtheEOWindowsmenu.+InManualLayoutMode,youcanfreelyJO5draganddrop componentshoweveryouliketogenerateaHOpleasing structure.-Becauseeach componentisfreefromKO automaticlayout constraints,youmayneedtoinvestsomeNO>timein positioningeach component,possiblyoneachoftheQOcharts.'Tomakethingssimpler,youcanclickpresstherightIOmousebuttononany componentandselectLayoutSubtreeQOHtoprovide automaticlayout assistancebelowthatpointintheO hierarchy.  MOWhenyouare satisfiedwiththelayout,youmustsavetheNOcurrentmodelinafiletoretainthemanuallayoutinfor-MO5mation.)Thecustomlayoutisusedwhenthemodelisopen.NONotethatifyouselectAutoLayoutmode,yourmanuallay-QOoutwillbelostforthe in-memorymodel.*Also,inorderforLO>CPU componentstoreassigninavisually effectivemanner,KOtheymustperformsubtreelayout operationsbelowthein-ROstancelevel.+Forthisreason,itisbesttolimitanymanualPOHlayout operationstotheinstanceand communitylevelsoftheO component hierarchy. *O9.1.2.2COpenVMSGalaxyChartsPO)TheGCUprovidessixdistinctsubsetsofthemodel,knownasOcharts.N$$OThesixchartsinclude:  OOChartname3Shows OObLogical Structure(3bDynamicresource assignmentsOPhysical Structure.3 Nonvolatilehardware relationshipsOVCPU Assignment03V SimplifiedviewofCPU assignmentsOMemory Assignment'3Memory subsystem componentsOIIOP Assignment'3II/O processor relationshipsOFailoverTargets*3 Processorfailover assignments ONPOThesechartsresultfromenablingor disablingthedisplayofNOvarious componenttypestoprovideviewsofsensiblesubsetsO5of components. WJOSpecificchartsmayoffer functionalitythatcanbepro-KOvidedonlyforthatcharttype.+Forexample, reassignmentKO5ofCPUsrequiresthattheinstance componentsbevisible.QOBecause instancesarenotvisibleinthePhysical StructureorIOMemory Assignmentcharts,youcanreassignCPUsonlyin@O>theLogical StructureandCPU Assignmentcharts.|R;OFormore informationaboutcharts,refertoSection9.4.*F|?! O9.1.3B InteractionHO4WhenviewingtheactiveGalaxy configurationmodel,youMOcaninteractdirectlywiththesystem components.'Forexam-QOple,toreassignaCPUfromoneinstancetoanother,youcanJO=draganddropaCPUontothedesired instance.*TheGCUMOwillvalidatethe operationandexecuteanexternalcommandMOactiontomakethe configurationchange.( InteractingwithaOOGmodelthatisnotengaged,issimplyadrawing operationonOOtheofflinemodel,andhasnoimpacttotherunningsystem.! JOWhile interactingwithGalaxy components,theGCUappliesMObuilt-inand user-definedrulesthatpreventmisconfigurationIO5andimproper managementactions.'Forexample,youcannotJOreassignprimaryCPUs,andyoucannotreassignaCPUtoKOany componentotherthanaGalaxy instance.(Eitheropera-QO>tionwouldresultinanerrormessageonthestatusbar,andROthemodelwouldreturntoitsproperconfiguration.'Iftheat-POtempted operationviolatesoneofthe configurationrules,theTOHerrormessage, displayedinredonthestatusbar,willdescribe!Otherulethatfired.GNOYoucanviewdetailsforanyselected componentbyclickingLOtherightmousebuttonandeither selectingthe ParametersKO5itemfromthepopupmenuorby selecting Parametersfrom8Othe Componentsmenuonthemaintoolbar. YKOTheGCUcanshutdownorrebootoneormoreGalaxyin-KOstancesusingtheShutdownorRebootitemsontheGalaxyHO5menu.*Thevariousshutdownorreboot parameterscanbeNOenteredintheShutdowndialogbox.*BesuretospecifytheDOCLUSTER_SHUTDOWNoptiontofullyshutdown clusteredNO>Galaxy instances.(TheShutdowndialogboxallowsyoutose-OOlectany combinationof instances,orall instances.(TheGCULOis ``smart''enoughtoshutdownitsownerinstancelast. 'KJLT+! * O9.7BCPU ReassignmentEOUOpenVMSsupportsseveralmethodsofmanagingCPUre-LOsources.*Theconsole establishesthedefaultownerinstanceLOforeachCPUusingtheconsole environment variables.(ThisOO^allowstheCPU resourcestobe statically assigned, providingWOapreciseinitialconfiguration.'Intheeventofacoldboot(thatSOis,powercycleorinitialization),thisdefault configurationis4Ohrestoredfromconsole nonvolatileRAM.0, GOOncea configurationhasbeenbooted,OpenVMSprovidesJOmoreelegantmeansof assigning resourcesforuserswithHO5CMKRNL(ChangeModetoKernel) privilege.'The following-Osectionsdescribethesemethods.- *"O9.7.1BDCL ReassignmentFO4UserswithCMKRNL privilegecanperformCPU reassign-@Oment operationsusingthe followingDCLcommand:4O $&STOP/CPU/MIGRATE=instance-or-idpcpu-idi. ?JOTheusermustprovidethetargetinstancename (SCSNAME)QOornumericID(0,1,andsoon),andthenumericIDoftheIO5CPUbeing reassigned.)The followingexamplesshowafew#Oformsofthiscommand.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/ aJOThesecommandscanbeinsertedintocommand procedures.JOForexample,youmightwanttomoveextraCPU resourcesPO5toaninstanceinastartup procedureofan applicationwithJOknown processing requirements.( Similarly,youmaywanttoMOreassignCPUsawayfromaninstancethatisabouttoper-MO>formlengthy,I/O intensive operations(suchasbackups)soKOthattheCPUsare availabletoother instances.+WhentheHOjob completes,youmayreassignthemback.,OryoumayMOHreassignCPUsawayfromaninstancethatisshuttingdown.m0 CIONotethatyoucanonlyreassign resourcesawayfromanIO instance..ThisisthepushmodeldefinedbytheGalaxyIO5Software Architecture.)Thismodelprevents resourcesfromPObeing ``stolen''byother instancesthatmaynotbeawareofNOtheircurrentusage.'To effectivelymanagetheentireGalaxyQO>systemusingDCL,youmusteitherlogintoeachofthein-LOvolved instancesorusetheSYSMANutilitytoexecutethe-Ocommandsontheowner instance.1 u1O9.7.2BGCU Drag-and-Drop ReassignmentKO4TheGCUprovidesan interactivevisual interfaceforman-IOagingGalaxy resources.*UsingtheGCU,youcanreassignEOCPUsbysimplydragginganddroppingthemamongin-NO=stances.) Additionally,theGCUallowsyoutodrawchartsofKOvariousconfigurations(knownas configurationmodels),andPOsavethemasfiles.*Atanytime,youcanloadandengageaKOG configurationmodelandthesystemwillreassign resources7Oasneededtoachievethedesiredmodel. 2)O9.7.3B Intermodal ReassignmentKO4BecauseoftheresourcepushmodeldefinedbytheGalaxyGOSoftware Architecture, resourcesmustbegivenawaybyLOtheGalaxyinstancethat currentlyownsthem.*Forautil-MO=ityoruserto effectivelymanageresource assignmentinaIOmultiple-instanceGalaxyconfiguration,youmust establishCOsomemeansof executingcommandsoneach instance.3NJOOnesuchmeansistoopenawindoworterminalsessionLOoneachoftheGalaxy instancesandperformyourresource?O5 management operationsineachofthesewindows.o4 kEJOAnothermethodisusetheSYSMANutilityanditsunder-GOlying SMI-Serverto establishacommand environmentonNO5theowner instance.(Usingthismethod,afairlysimplecom-LOmand procedurecanbewrittentoperformspecificresourceHO management operations.)Thismethodhassome limitations,PO>however.'Firts,itrequiresthattheinvolvedGalaxy instancesNOmustbeinacluster.(Also,acommand procedurecannotef-HO fectivelypassvariable parameterstoSYSMAN environmentJOHscripts,andyoucannotspecifyaremotesystempasswordJOwithinaSYSMANscript.*Soitis cumbersometogenerateGOageneral-purposecommand procedure interfacethatusesORSYSMAN.5 k|IOTheGCUdoes,infact,useSYSMANwhereverpossibletoIO accomplishits managementactions.*WhenasystemisnotLO5 configuredtosupportSYSMAN,theGCUwillattempttouseDODECnet task-to-task comminationsamongproxyaccountsQOasits management transport.'Ifthatapproachalsofails(thatPO>is,ifthesystemisnotrunningDECnetorifthe necessaryQOproxyaccountsarenotsetup),theGCUwillnotbeabletoJOmanageGalaxy instancesotherthantheoneonwhichtheJOHGCUis currentlyrunning.)Youcould certainlyrunmulti-ROplecopiesoftheGCUifyouchoose,oneperGalaxy instance.DOHowever,youcanassumethatOpenVMSGalaxysystems>ORarelikelytobe clusteredortouseDECnet. 6 ZOTheGCUs managementactionsarebasedintheSYS$MANAGER:GCU$ACTIONS.COMJOcommand procedure.)Youcanmodifythisfileto customizeMO5actionsforyourown environment.'Forexample,inaTCP/IPEO environment,youmaychoosetouseREXECorsimilarHOutilityforyour management transport,oryoumaywantMO>toincludesomeformof notificationorloggingwhenevera+O managementactionis executed.7 ?OTheGCU$ACTIONS.COMfileissomewhatunusualinGOthewayit operates.*WhenusingSYSMAN,the procedureGO5buildssmallSYSMANcommandscriptsin temporaryfilesDOtodealwithvariable parametersthatSYSMANCannotIOhandle.)WhenSYSMANisnot available,the procedureat-MO>temptstoopenaDECnet task-to-task connectiontoaproxyMOaccountontheowner instance.,If successful,itusesthisIO connectiontoshufflecommand parameterstothecopyofCOHGCU$ACTIONS.COMthatresidesontheowner instance.MOTheendresultis executionofthecommandlocallybytheOowner instance.8 @O9.7.4BSoftware ReassignmentUsingGalaxyServicesIO4Perhapsthebestmethodformanagingresource assignmentNOistousetheGalaxyAPIstowriteyourownresourceman-OOagement routines.)Thisallowsyoutobaseyour decisionsforIO=resource managementonyourowncriteriaand applicationIO environment.(Thesame push-model restriction describedinOSection9.7.3Fstillexists,however,soyourroutineswillneedtoMOGbeGalaxyaware,possiblyusingsharedmemoryto coordinateOtheir operations.*8O?29V@OFor informationaboutCPU reassignmentAPIs, seeOChapter16.*9OO1: %O9.7.5B ReassignmentFaultsLO4CPU reassignmentcanfailorbeblocked,forseveralrea-HOsons.,BecausetheGCUburiesits managementactionsinMOSYSMANorDCLscripts,itmaynotalwaysidentifyandre-JO=portthereasonsfora reassignmentfault.+TheGCUdoesJOperformcertaincheckspriortoallowing reassignmentac-OOtionsinorder,forexample,topreventattemptstoreassignFOGtheprimaryCPU.Otherreasonsexistfor reassignmentOOfaultsthatcanonlybedetectedbythe operatingsystemorLOconsole firmware.)Forexample,ifthe operatingsystemde-QOQtectsafault attemptingtoreassignaCPUthat currentlyhasOOprocessaffinityorFastPathduties,aDCLmessagewillbeGO displayedonboththeconsoleandtheusers terminal.|; RKOTheGalaxyAPIsfor reassignmentarecapableof reportingOOmostfaultstothecaller.)However,evenusingthe reassign-NO5ment services,theconsolemayrejecta reassignmentbecauseNOofhardwareplatform dependenciesnotreadilyvisibletotheO operatingsystem. xRxZ fRP.1D> R.6 G|>GHFQI&Q<UU/UHXf/ZX Divq8;|v qR[ DD Df#_ _Ph H_ fD+ r" 8<+} tn0:{.I jM8{HL-5p<lv<Q4EdUdyS($'N N 4B42L7N n  # :z0$, Rbj!&C 0:^ l"L)d*P* /|59'GG4b0*d\dDfg lTslnmqt