S".BITNET Postmaster's Guide for VAX/VMS Systemsp2ePOST_VMS  Contents   Examples  Figures  Tables  Index*d / EXAMPLESEXAMPLESw%:+=@5-1MemberentryfromBITEARNNODES5- 1 Member entry from BITEARN NODESpT{/=A5-2UPDATEjobtocreateanode(entryinBITEARNNODESfor$a standaloneVAXsystem5- 2 UPDATE job to create a node entry in BITEARN NODES for a standalone VAX system}UY,=A5-3UPDATEjobtocreatenode%entriesinBITEARNNODES&foratwo-node VAXcluster)system5- 3 UPDATE job to create node entries in BITEARN NODES for a two-node VAXcluster system~Ru%=@6-1Command procedureto) initializePMDFbatchqueues'ona two-member VAXcluster6- 1 Command procedure to initialize PMDF batch queues on a two-member VAXclusterW{,=@6-2Command proceduretostart(PMDFbatch executionqueues'ona two-member VAXcluster6- 2 Command procedure to start PMDF batch execution queues on a two-member VAXcluster/F0=@6-3PMDF configurationfileforaBITNETnode6- 3 PMDF configuration file for a BITNET node}'>0=A6-4PMDFaliasfileforaBITNETnode6- 4 PMDF alias file for a BITNET nodeUg+=@6-5UPDATEjobtoregistera(mailerandInternetaddress$inBITEARNNODESfora!) standaloneVAXsystem6- 5 UPDATE job to register a mailer and Internet address in BITEARN NODES for a standalone VAX system!Ul+=A6-6UPDATEjobtoregistera(mailerandInternetaddress$inBITEARNNODESfora&)two-node VAXclustersystem6- 6 UPDATE job to register a mailer and Internet address in BITEARN NODES for a two-node VAXcluster systemJl'=@6-7MailtoDOMAINS@BITNIC'toregisterthe Arnold.ComdomainwithBITNET6- 7 Mail to DOMAINS@BITNIC to register the Arnold.Com domain with BITNETE]+=@6-8MailtoDOMAINS@BITNICto&registerthe BostonCol.Edu(domainwithBITNICandthe)DDNNIC6- 8 Mail to DOMAINS@BITNIC to register the BostonCol.Edu domain with BITNIC and the DDN NIC c-FIGURESFIGURES2H,=A1-1 ArchitectureoftheBITNETmail application.1- 1 Architecture of the BITNET mail application.68Q0=@1-2SendingBITNETmailbydirect!useofNJE software.1- 2 Sending BITNET mail by direct use of NJE software.91I2=A2-1Stepstosetupan operationalBITNETnode.2- 1 Steps to set up an operational BITNET node.kk)=@5-1BITNETtopologyexample.+Largefilledcircles represent* PrincipalNodes.'Opencircles)) represent pseudonodesbearingvJnetclusternames.5- 1 BITNET topology example. Large filled circles represent Principal Nodes. Open circles represent pseudonodes bearing Jnet cluster names.;+TABLESTABLESLx =@1@Minimumandassumed*softwareversionsforDigital$VAXsystemsrunningVMS1 Minimum and assumed software versions for Digital VAX systems running VMS9P)=@3-1 Campus-widenetworkname'spaceexample:'BayCollege3- 1 Campus-wide network name space example: Bay College/F.=A5-1TCP/IPProducts supportedbyJnetTCPNJE5- 1 TCP/IP Products supported by Jnet TCP NJE@L/ CONTENTSCONTENTS8 E[TitlePageTitle Page@E\ CopyrightPageCopyright Page1xE\PrefacePreface Lg  $L1MailersonBITNET1 Mailers on BITNET)(@b'$K1.1Direct Transmissionof'& ElectronicMailbyNetwork&JobEntry1.1 Direct Transmission of Electronic Mail by Network Job Entry*Vw%%$K1.2BITNETMailConcepts1.2 BITNET Mail Concepts0p"6 $K1.3BITNET Technical& Requirements1.3 BITNET Technical Requirements=nw$22$K1.4Benefitsof InstallingaMailer1.4 Benefits of Installing a MailerH`l**$@1.4.1MailersEase Addressing1.4.1 Mailers Ease AddressingI1H.$A1.4.2MailersIsolateUsersFrompNetworkChanges1.4.2 Mailers Isolate Users From Network ChangesOm\$11$@1.4.3MailersProvideNew Functions1.4.3 Mailers Provide New FunctionsP~'?)$K2OverviewofSettingUpa BITNETNode2 Overview of Setting Up a BITNET NodeRBw$K2.1 Assumptions2.1 AssumptionsUt":,$K2.2StepstosetupaBITNET&node2.2 Steps to set up a BITNET nodeZp!7($K3PlanningSystemandUser Names3 Planning System and User Namesm+A)$L3.1Starting assumptionsfor&nameplanning3.1 Starting assumptions for name planningo-C+$K3.2Generalconsiderationsfor&networknames3.2 General considerations for network namess[g(($K3.3NamesforBITNEThosts3.3 Names for BITNET hostsx2I($L3.4 Suggested procedurefor!&planningsystemnames3.4 Suggested procedure for planning system namesz)?,$A3.4.1Summaryofnameplanningp procedure3.4.1 Summary of name planning procedure{~(>/$@3.4.2PlanSCSNODEand DECnet-VAXpnames3.4.2 Plan SCSNODE and DECnet-VAX names}l\#11$A3.4.3Plana VAXclusteraliasname3.4.3 Plan a VAXcluster alias nameT\$$$@3.4.4Plandomainnames3.4.4 Plan domain names.G0$@3.4.5RegisteradomainnamewithptheDDNNIC3.4.5 Register a domain name with the DDN NICN\!!$@3.4.6PlanNJEnames3.4.6 Plan NJE names+B3$@3.4.7Planreservedandgeneraluserpnames3.4.7 Plan reserved and general user namesd\ ,,$@3.4.7.1 POSTMASTERandPOSTMAST3.4.7.1 POSTMASTER and POSTMAST\\(($@3.4.7.2MAILERandSMTPUSER3.4.7.2 MAILER and SMTPUSER^\))$A3.4.7.3LISTSERVandNETSERV3.4.7.3 LISTSERV and NETSERV:\ $A3.4.7.4JOB3.4.7.4 JOBeg --$A3.4.7.5SYSTEM,ROOT,andMAINT3.4.7.5 SYSTEM, ROOT, and MAINTZg''$A3.4.7.6PMDFand PMDF_USER3.4.7.6 PMDF and PMDF_USERZ\''$A3.4.7.7Generalusernames3.4.7.7 General user namesZw''$L3.5Campusnetworkexample3.5 Campus network example1G)$K4 Installingand Configuring  NetworkingSoftware4 Installing and Configuring Networking Softwares#8)$K4.1 VMSINSTALand autoanswer&files4.1 VMSINSTAL and autoanswer filesZw''$L4.2ChangingSCSNODEnames4.2 Changing SCSNODE namesYw&&$K4.3 Configuring DECnet-VAX4.3 Configuring DECnet-VAXx&:&$K4.4 Configuring DECnet-VAX& Extensions4.4 Configuring DECnet-VAX ExtensionsSw##$K4.5 ConfiguringVMSmail4.5 Configuring VMSmail*?($K4.6TCP/IP installationand& configuration4.6 TCP/IP installation and configuration*@.$K5 Installingand ConfiguringNJE Software5 Installing and Configuring NJE SoftwareVw%%$L5.1PlanBITNETtopology5.1 Plan BITNET topology1H4$A5.1.1 Selectingsystemsto participatepinBITNET5.1.1 Selecting systems to participate in BITNETOl!!$A5.1.2 PrincipalNodes5.1.2 Principal Nodesll$00$A5.1.3Planningexternal connections5.1.3 Planning external connectionsrl'33$A5.1.4Planningintraorganizationlinks5.1.4 Planning intraorganization links]\(($@5.1.5 VAXcluster connections5.1.5 VAXcluster connections Ml  $@5.1.6Link protocols5.1.6 Link protocols `w**$K5.2InstallBITNET transports5.2 Install BITNET transportsjg"00$K5.3InstallJnetandlinkdrivers5.3 Install Jnet and link driversIw$L5.4 ConfigureJnet5.4 Configure Jnet(+@-$A5.4.1RunJnetautoconfigurationp procedure5.4.1 Run Jnet autoconfiguration procedure)fl!--$A5.4.2Manual configurationtasks5.4.2 Manual configuration tasks8y':$A5.4.2.1Edit#JAN_COMMON:[SYS]LOGIN.COM5.4.2.1 Edit JAN_COMMON:[SYS]LOGIN.COM;u%8$@5.4.2.2Test!SYS$MANAGER:SYLOGIN.COM5.4.2.2 Test SYS$MANAGER:SYLOGIN.COM<Cb$A5.4.2.3UseSYSMANSTARTUPinsteadof&SYS$MANAGER:SYSTARTUP_V5.COM5.4.2.3 Use SYSMAN STARTUP instead of SYS$MANAGER:SYSTARTUP_V5.COM=;P-$A5.4.2.4EditJAN_SYS:JANLINKS.JCP#andJAN_SYS:JANSTART.JCP5.4.2.4 Edit JAN_SYS:JANLINKS.JCP and JAN_SYS:JANSTART.JCP>cJ+$A5.4.2.5DeferthecreationofJAN_SYS:JANROUTES.JCPD{(;$@5.4.2.6 ConsolidateJAN_SYS:JANLOAD.COM5.4.2.6 Consolidate JAN_SYS:JANLOAD.COME/B$A5.4.2.7Edit+!JAN_COMMON:[SYS]JANSITECOMMON.COM5.4.2.7 Edit JAN_COMMON:[SYS]JANSITECOMMON.COMGql&33$@5.4.2.8Skip instructionsforLMD.COM5.4.2.8 Skip instructions for LMD.COMR4I$$A5.4.2.9Editandenable%JAN_COMMON:[SYS]JANTIDY.COM5.4.2.9 Edit and enable JAN_COMMON:[SYS]JANTIDY.COMSkl#00$@5.4.2.10Editlink parameterfiles5.4.2.10 Edit link parameter filesU3F$A5.4.2.11Edit.$SYS$COMMON:[SYSMGR]LAT$SYSTARTUP.COM5.4.2.11 Edit SYS$COMMON:[SYSMGR]LAT$SYSTARTUP.COMWWw&&$K5.5BringupBITNETlink5.5 Bring up BITNET linkYXg&&$K5.6InstallBITNETtables5.6 Install BITNET tables\Xw&&$K5.7RegisterBITNETnodes5.7 Register BITNET nodesagl!..$@5.7.1AbouttheUPDATE procedure5.7.1 About the UPDATE procedurecfl ..$A5.7.2WheretosendUPDATEjobs5.7.2 Where to send UPDATE jobskpl%33$A5.7.3Addinga Postmasterpeopletag5.7.3 Adding a Postmaster people tagoVl%%$@5.7.4 Registeringanode5.7.4 Registering a nodev]w))$K5.8Waitforroutingtables5.8 Wait for routing tablescl,,$A5.8.1Themonthlyupdatecycle5.8.1 The monthly update cyclebl++$@5.8.2 Monitoringtableupdates5.8.2 Monitoring table updatesdl ,,$A5.8.3 Installinginitialtables5.8.3 Installing initial tables-D,$K6 Installingand Registeringa BITNETMailer6 Installing and Registering a BITNET Mailerbg,,$K6.1Externalviewofamailer6.1 External view of a mailerEg$K6.2InstallPMDF6.2 Install PMDF-D+$@6.2.1 DetermineUICsforPMDFpSYSUAFentries6.2.1 Determine UICs for PMDF SYSUAF entries+C4$@6.2.2SelectalocationforthePMDFpfiles6.2.2 Select a location for the PMDF filesWl&&$A6.2.3SetupPMDFqueues6.2.3 Set up PMDF queuesK\$A6.2.4Run VMSINSTAL6.2.4 Run VMSINSTAL+A0$@6.2.5 ConfigurePMDFfor automaticpstartup6.2.5 Configure PMDF for automatic startup5M*$A6.2.6MakePMDFonlinebooks#p availableto Bookreader6.2.6 Make PMDF online books available to BookreaderIw$K6.3 ConfigurePMDF6.3 Configure PMDFX\&&$@6.3.1Obtainmailerfiles6.3.1 Obtain mailer filesfl!--$A6.3.2RunPMDFautoconfiguration6.3.2 Run PMDF autoconfigurationkl#00$A6.3.3EditPMDF configurationfile6.3.3 Edit PMDF configuration fileMl  $@6.3.4Run LONG_NAMES6.3.4 Run LONG_NAMES_\**$@6.3.5EditPMDFaliasesfile6.3.5 Edit PMDF aliases file[l''$A6.3.6Compile configuration6.3.6 Compile configurationpl&22$A6.3.6.1Compilemaximum configuration6.3.6.1 Compile maximum configurationrl'33$A6.3.6.2Installcompiled configuration6.3.6.2 Install compiled configurationI\$@6.3.7MoveLMD.COM6.3.7 Move LMD.COM~(>/$A6.3.8PMDF configurationstepstopavoid6.3.8 PMDF configuration steps to avoid*B'$L6.4StartupPMDFonall& VAXclusternodes6.4 Start up PMDF on all VAXcluster nodesbw++$K6.5UpdateBITNET registration6.5 Update BITNET registration~(>.$L6.6Registerdomaingatewaywith&BITNIC6.6 Register domain gateway with BITNIC[l(($@6.6.1TagsinDOMAINNAMES6.6.1 Tags in DOMAIN NAMES6N2$A6.6.2 RegisteringanInternetdomainpnamewithBITNIC6.6.2 Registering an Internet domain name with BITNIC@\2$@6.6.3 Registeringanewdomainname*pwithBITNICandtheDDNNIC6.6.3 Registering a new domain name with BITNIC and the DDN NIC .D/$L6.7 Subscribetorelevantnetwork& discussions6.7 Subscribe to relevant network discussions ml$11$@6.7.1 SubscribingtoLISTSERVlists6.7.1 Subscribing to LISTSERV lists*?*$A6.7.2 SubscribingtoInternetp discussions6.7.2 Subscribing to Internet discussionsz&<%$K7On-going Managementof BITNETNodes7 On-going Management of BITNET Nodes$(?0$K7.1 Initiallyandwhenaddingnew&users7.1 Initially and when adding new users&Zl''$A7.1.1 Assigningusernames7.1.1 Assigning user names'Kl$@7.1.2Usertraining7.1.2 User training(@w$K7.2 Constantly7.2 Constantly-<w $L7.3Weekdays7.3 Weekdays3\l(($A7.3.1ReviewJANTIDYoutput7.3.1 Review JANTIDY output4*A-$A7.3.2Disposeoffilessenttop POSTMASTER7.3.2 Dispose of files sent to POSTMASTER5a\++$A7.3.3Readmailto POSTMASTER7.3.3 Read mail to POSTMASTER6el --$A7.3.4CheckPMDFchannelqueues7.3.4 Check PMDF channel queues9al++$@7.3.5CheckPMDFbatchqueues7.3.5 Check PMDF batch queues;}(=($@7.3.6Readrelevantnetworkp discussions7.3.6 Read relevant network discussions<:w $L7.4Monthly7.4 Monthly=il"//$A7.4.1InstallJnetroutingtables7.4.1 Install Jnet routing tables>?\&&$A7.4.2Buildmailertables@cw,,$K7.5Whenchangingsystemclock7.5 When changing system clockA3J/$K7.6 Management activitieswithno&regularschedule7.6 Management activities with no regular scheduleD*@($A7.6.1UpdateJnetandPMDFpconfigurations7.6.1 Update Jnet and PMDF configurationsE0G'$A7.6.2Modifysoftwarewhen pSCSNODEnameschange7.6.2 Modify software when SCSNODE names changeF/G4$@7.6.3Adjustqueueswhen upgradingtopVMSV5.57.6.3 Adjust queues when upgrading to VMS V5.5Gll#11$A7.6.4RespondtomailfromNETSERV7.6.4 Respond to mail from NETSERVJ1J1$[AMAddinganInternet ConnectiontoaBITNETNodeA Adding an Internet Connection to a BITNET NodeQiw"//$LA.1 AssumptionsforthisappendixA.1 Assumptions for this appendixR-F/$KA.2Obtainanetworknumberfrom&theDDNNICA.2 Obtain a network number from the DDN NICT-D+$LA.3Review acceptableuseand&otherpoliciesA.3 Review acceptable use and other policiesV;U/$KA.4Joina consortiumorarrange&&for commercialIPserviceA.4 Join a consortium or arrange for commercial IP serviceYiw"//$KA.5Installaphysical connectionA.5 Install a physical connectionZ*@.$KA.6Installand configureTCP/IP&softwareA.6 Install and configure TCP/IP software[_w**$KA.7ArrangefornameserviceA.7 Arrange for name service]\w(($LA.8 ReconfigureyourMAILERA.8 Reconfigure your MAILER_Tw$$$KA.9UpdateDOMAINNAMESA.9 Update DOMAIN NAMES`\w(($KA.10bAdjustBITNETtopologyA.10 Adjust BITNET topologychg!//$KA.11bTrainusersonnewservicesA.11 Train users on new servicesejg"00$KA.12bSwitchtoInternetNewsfeedA.12 Switch to Internet News feedgg!..$\BM OperatingBITNETMailGatewaysB Operating BITNET Mail Gatewaysh*A0$KB.1Mailgatewaystodomainswith&mailersB.1 Mail gateways to domains with mailersj1H,$LB.2 Providingnameservicefor& connecteddomainsB.2 Providing name service for connected domainsq|'=,$KB.3 OperatinganINTERBITmail&gatewayB.3 Operating an INTERBIT mail gatewaytx%;*$KB.4MailgatewaystoMail-11&domainsB.4 Mail gateways to Mail-11 domainsvR##$\CN MigrationfromGmailC Migration from Gmail~/ EXAMPLESEXAMPLESw%:+=@5-1MemberentryfromBITEARNNODES5- 1 Member entry from BITEARN NODESpT{/=A5-2UPDATEjobtocreateanode(entryinBITEARNNODESfor$a standaloneVAXsystem5- 2 UPDATE job to create a node entry in BITEARN NODES for a standalone VAX system}UY,=A5-3UPDATEjobtocreatenode%entriesinBITEARNNODES&foratwo-node VAXcluster)system5- 3 UPDATE job to create node entries in BITEARN NODES for a two-node VAXcluster system~Ru%=@6-1Command procedureto) initializePMDFbatchqueues'ona two-member VAXcluster6- 1 Command procedure to initialize PMDF batch queues on a two-member VAXclusterW{,=@6-2Command proceduretostart(PMDFbatch executionqueues'ona two-member VAXcluster6- 2 Command procedure to start PMDF batch execution queues on a two-member VAXcluster/F0=@6-3PMDF configurationfileforaBITNETnode6- 3 PMDF configuration file for a BITNET node}'>0=A6-4PMDFaliasfileforaBITNETnode6- 4 PMDF alias file for a BITNET nodeUg+=@6-5UPDATEjobtoregistera(mailerandInternetaddress$inBITEARNNODESfora!) standaloneVAXsystem6- 5 UPDATE job to register a mailer and Internet address in BITEARN NODES for a standalone VAX system!Ul+=A6-6UPDATEjobtoregistera(mailerandInternetaddress$inBITEARNNODESfora&)two-node VAXclustersystem6- 6 UPDATE job to register a mailer and Internet address in BITEARN NODES for a two-node VAXcluster systemJl'=@6-7MailtoDOMAINS@BITNIC'toregisterthe Arnold.ComdomainwithBITNET6- 7 Mail to DOMAINS@BITNIC to register the Arnold.Com domain with BITNETE]+=@6-8MailtoDOMAINS@BITNICto&registerthe BostonCol.Edu(domainwithBITNICandthe)DDNNIC6- 8 Mail to DOMAINS@BITNIC to register the BostonCol.Edu domain with BITNIC and the DDN NIC -FIGURESFIGURES2H,=A1-1 ArchitectureoftheBITNETmail application.1- 1 Architecture of the BITNET mail application.68Q0=@1-2SendingBITNETmailbydirect!useofNJE software.1- 2 Sending BITNET mail by direct use of NJE software.91I2=A2-1Stepstosetupan operationalBITNETnode.2- 1 Steps to set up an operational BITNET node.kk)=@5-1BITNETtopologyexample.+Largefilledcircles represent* PrincipalNodes.'Opencircles)) represent pseudonodesbearingvJnetclusternames.5- 1 BITNET topology example. Large filled circles represent Principal Nodes. Open circles represent pseudonodes bearing Jnet cluster names.+TABLESTABLESLx =@1@Minimumandassumed*softwareversionsforDigital$VAXsystemsrunningVMS1 Minimum and assumed software versions for Digital VAX systems running VMS9P)=@3-1 Campus-widenetworkname'spaceexample:'BayCollege3- 1 Campus-wide network name space example: Bay College/F.=A5-1TCP/IPProducts supportedbyJnetTCPNJE5- 1 TCP/IP Products supported by Jnet TCP NJE@X|\* Copyright1992,3 CorporationforResearchand Educational Networking,CREN ~AllRights Reserved.nSD*OBITNET Postmaster'sGuideforO:VAX/VMSSystems OWrittenforCRENby:OStephenL.Arnold,Ph.D.,Arnold ConsultingO`April1992[OThisbook describesmailroutingand transport,andtheresponsibilitiesWO3ofthe Postmaster,foracomputersystemonBITNET.Thisbookalso[Oprovides instructions,specifictotheBITNET environment,on installing,TO configuring,andmanagingNJEandmailersoftwareanddatatablesPOforDigitalVAXcomputersystemsrunningVMS,Jnet,andPMDF,ROhto supplementthe documentationprovidedwith commercialsoftwareO products.rH'ORevision/Update Information:!^Thisisanewbook.U*O OperatingSystemandVersion:+^VAX/VMSVersionV5.0orlater,`OSoftware Versions:^JnetVersion3.5'^PMDFVersion4.0orlater  _ ! "5  O OO April1992aOThisdocumentwaswrittenbyStephenL.Arnold,Ph.D.,Arnold@Eisner.DECUS.OrgcO (Internet), Principal,Arnold Consulting,4138IroquoisDrive,Madison, Wisconsin9O? 53711-3701U.S.A.,undercontracttoCREN. O\O Copyright1992,3 CorporationforResearchand Educational Networking,CRENjO PermissionisgrantedbyCRENto reproduceand distributethismaterialinwholeormOinpart,without impositionoffeesorcharges,solongasthesourceis acknowledgedWO=andCREN's copyrightnoticeisincludedonthe reproduced materials.jOThe informationinthisdocumentissubjecttochangewithoutnoticeandshouldnotgObe construedasa commitmentbytheauthor,Arnold Consulting,orthe CorporationaO\forResearchand Educational Networking(CREN).Theauthor,Arnold Consulting,iOandCRENassumenoresponsibilityforanyerrorsthatmayappearinthis document.jO|Someofthesoftware describedinthisdocumentis furnishedunderlicensesandmayhObeused,copied,or disclosedonlyin accordancewiththetermsofsuch licenses.bOZTheauthorwould appreciatecommentsonthisdocumentsothatfutureeditionsdOmightbe improved.'By providingcommentsor correctionstoCRENortheauthor,dOyougiveyour permissionforthemtobeusedwithout restrictions.+Pleasesend]O!yourcommentstotheauthoratCRENDOC@BITNIC (BITNET),orcall+1(608)Oc 238-7835.VO  ALL-IN-1,DEC,DECnet, DECwindows, MicroVAX,ULTRIX,VAX, VAXcluster,`O  VAXstation,VMS,andVMSmailare trademarksofDigital Equipment Corporation.fOw BITNETandCRENare registeredservicemarksofthe CorporationforResearchand"O  Educational Networking.eOT  Application System/400,IBM,MVS,andVMare trademarksof InternationalBusiness O Machines Corporation.UO1 Joinerisa registered trademarkofJoiner Associates Incorporated.IO Jnetisa registered trademarkofJoiner Software,Inc.POg PMDFisa registered trademarkofInnosoftInternational,Inc.MOMotifisa trademarkoftheOpenSoftware Foundation,Inc.VOMultiNetisa trademarkofSRI InternationalandTGV, Incorporated.AO8Tekisa registered trademarkof Tektronix,Inc.SOUNIXisa registered trademarkofUNIXSystem Laboratories,Inc.OOnWINandWIN/TCPare trademarksofThe WollongongGroup,Inc.=O Ethernetisa trademarkofXerox Corporation.*[  A  OPrefaceMOThisPrefaceexplainsthe objectives,intended audience,andPO structureofthisbook, describesthesoftware environmentforMOXwhichthisbookis relevant,andexplainsthe topographicalO conventionsused.   ! )O ObjectivesOOUThisbookisdesignedtohelpgettheroutingand transportIOofBITNETmailupandrunningonaDigitalVAXsystemJOrunningVMSasquicklyandaseasilyas possible,whileJO^ complyingwithBITNET standardsformailers.*ItdoesnotUOdealwiththemailuser interface,exceptforaspectsspecifictoOBITNET.  BOThegeneralapproachistoprovideBITNET-specificJO instructionsforallthetasksrequiredatanewBITNETNO5siteintheorderthattheyare encountered.)For continuingIOBITNETsites,whereNetworkJobEntry(NJE)softwareisNOalready installedbutwithnomailer,thereadercaneasilyFO>reviewtheNJE configurationandcontinuewithmailer+O configurationand installation.  J   OIntendedaudienceNOUThisbookis addressedtothepersonorpersons responsibleJOfor installationandongoing managementofthe electronicKOmail applicationonaBITNETcomputersystem.'ThispersonO^iscalledthe^ Postmaster.^ throughoutthisbook.*(ThisbookMOalso discussesan electronicmailboxandusernamefortheO Postmaster,called POSTMASTER&C,inuppercaseletters,"Oh throughoutthisbook.)k AEOForlargesystems, PostmasterresponsibilitiescanbeCOsharedbyasystems programmer,anetworkmanager,OO5auserservices consultant,andthosewithotherjobtitles.KOForasmallsystem,asingle individualmayhaveallofOOtheseresponsibilitiesaswellasother, unrelatedroles.+ForFO>VAX/VMSsystems,the PostmasterisusuallythesystemHOmanager.,The PostmasterisassumedtobefamiliarwithBOVMS management proceduresandtheuseofVMSmail.y kOPOManyofthetasks describedhererequireaccessto privilegedCOsystem functionsand technical competencetomanageDO5thesystemandattached networks.0Othertasks,suchGOas respondingtoroutinerequestsfor informationfromNOnetworkusersand monitoringthesystemfortrouble,canbePO> delegatedtostaffwithordinary privilegesandless technicalLO expertise.+Youareurgedtodelegate Postmasterduties,asJO appropriatetoyoursystem environment,sothat importantLOHtasksare performedinatimelymannerwithout overloadingJOstaff.*BothlocalandremoteBITNETusersdependontheOO PostmastertocompletetherequiredtaskstoprovidereliableORmailservice. hHONoprior experiencewithBITNETisassumed.(ForBITNETFOlinksoverothernetworksandmailgatewaystootherDO5 networks,suchasSNA,DECnet,andTCP/IP networks,NOthereaderisassumedtobefamiliarwiththeconceptsandHOsoftwarerequiredtoinstallandmanagethose networks.sY /hOTable1:7MinimumandassumedsoftwareversionsforDigitalVAXsystemsrunningVMS O $OVendorandproductnameFMinimumversionFAssumedversion O )O DigitalVMS OperatingSystem V5.0 V5.5Oq Digital DECnet-VAXq V5.0q V5.5*O JoinerJnetstandardfeatures V3.5 V3.5-Oe JoinerJnetlinkdriveroptionse V1.1e V1.1O InnosoftPMDF V3.2 V4.0 O $nVO ConventionsAOUThe following conventionsareusedinthisbook.O% :%O Newterm8 Thistypefaceinthetext representsthe)0 introductionofanewterm.O Userinput8 In examples,boldfacetype indicatestext" thattheuserenters.Oq UPPERCASE0q Uppercaselettersinacommandor7 UPDATEjob representtextthatyouhave  toenterasshown.O lowercaseitalics8 Lowercaseitaliclettersinacommandor3 UPDATEjobindicatevariableinforma-"! tionthatyousupply.&N OTheReturn=keyisnotshowninsyntax statementsorin4O examples;however,youmustpresstheReturnkeyafter>O5enteringacommandor respondingtoaprompt.' V1OThisbook distinguishesbetweenthev installation _andO configuration=ofJnetandPMDF software.( InstallationisaPO5 standardizedprocess requiringlittleinputfromthe installer,LOandmovesthesoftwarefromthe distributionmediatoitsLOplaceinthefilesystem., ConfigurationisamorecomplexOO>task requiringcareful,individualizedplanningforeachsite,NOandresultsinthecreationofdatatablesthatenablethe)Osoftwaretodousefulwork.!( JO Distinctionsarealsomadebetween installationandpost-MO installation,andbetween configuration(orautoconfiguration)HO5andpost-configuration.+ InstallationandautoconfigurationCOare accomplishedbyrunningcommand proceduresthatIOpromptforinput;post-installationandpost-configurationNO>consistofmanualtasksthatarenoteasily automated,such>Oaseditingasystemstartupcommand procedure.1] M1FMailerswerefirst developedunderIBM'sVM operatingJ5system,andBITNETdatafilesarestill maintainedunderAVM.ThisbookreferstoBITEARNNODESandotherFsuchfilesusingVMfilenaming conventions.-VMfileE>identificationshavespacebetweenthefilenameandIthefiletype,whileVAX/VMSfilespecificationshaveaLperiod(.)+inthat position.,Forexample,whenacopyofIHBITEARNNODESisstoredonaVAXsystem,itiscalledBITEARN.NODES.Us6 HIIOFigure1-1:7 ArchitectureoftheBITNETmail application.U6i 0TKKY ? xx `    8  1 1 p `` `xx a??aa@0`~``bpP @%P QP@QPb@#P@@?P(RC@ P8B!`1B@ P(B"`)B@ Ps`S  P  P0 !jP   jP @R pdP@{ P@? P@ P@ P 8C@ P @ P  2P ? ?bP @ RJP  @ P@  @ P@!@ P!@ pP~x!@ PP!@ P @p!@ P80!@!`P` !@!Px|!@1#Px @T!@1#P` E!@# P !@'`P` 8B!@&`?P!@ ,@BjUP!@x , ! PJ!@ !0B"KP2 !@ 87:P<!@ P=(O !@ P!@` Pp!@@P` G6!A P`0!A0Pp!C0P?!G P!OBP !_pPg ! P(!P(&!P (!Pgj!Ps=!PS!PW !P!?P!_!@p!!@C !!@\C !!@ BC!!@^WC !!@ BC!1!?@`]U;C !} !@?C!VUP!!@VUjC !!!!@BC!!R!!@`uC!s9s!@C!!@WUUC!!@C!!@pU]]]C!!@ G!!@WUWUG! !@8" '0!!@pUWUuug5!!@D@' !!!0@XuUU]Ug5!!0@/ !!@UUU:o5!!|p3@r?/ !!3@^UUUuU o5!! 36@ B?`!8 3@UUUUUW<3U! 3@@/@! 36@VUUUU]k! 3@ !0p3@TUUUU]UU!@ @XUUUUWum_U @" t>  @XUUUUuU}_UW >@D@ ~`0@ ƙ`0@ > x00@ >B 0@ >B @ >B A@ >B@@ >B@@ |B80@@ |Bbx0ϟ@ |B@x0c@ |B(RC0c`@ |B8B!`1B08g`@ |B(B"`)B10f@ |Bs`S10@ |B30@ B30f@ B78g @ B6c0@ B6c@@ B<? @ B<?@ B!@ B8CA@ B@ B @ B @@ B @  @@  @@  10@ a0 10 a0 30  ax 30  ax 60 a 60@ a  <0@@ a <0@@ a  83 s  8? ?  0            @   @ @ @   @   @   @   @  @ @   @8μ ɸ |@PDO ?(|@pDa >@|@PD)I ~@`|@<i& | |@ |@ p|@ ` 8A A A@? 4A@ @A@  A@ A7@  A(%@ ?8A8#@  ?A(@J  ~A@ ~= A@J) 3A@= | A@ A@ A!@ @@ @@B @@ @@ ?@@ =@C ``<@B!p8AB!pAB!yAB!`o8AB!`ofAB!`fgAB!`fg`AB|!`f`A BT!`fg A BE!`faApB!AB8B!@8AB!0AB!8AB!0AxB!APB!|0@0D-B<!|@@D-B(O !| @lB!|@B!|`@B G6!|@B!p|@B!<|@@B! |@8@B !#|@@P1B !,| `@PL8B(!P| @PJ B(&!?``|@80B(!8|@Bj!}@B!~@B!B~@B!"}A@B!| @B! |@BB!|b@BB!|b@BB!|"@BB!|@BB!|@BbB!|@B@B!|`@B(RCB>!|@B8B!`1BBT*(!|@B(B"`)BBmX!80@Bs`SBX!x0@BBǹ9!x0c@BB! 0c@BB!08g@BB!10f@BB!@10@BB!|30@BB!|30f@BB! 78g@B8CB! 6c@BB!|6c@BBB!|<@BB! <@BB! @BB! @B!|@B!x|@B!@B!@B!@C!@@!10@@ 10@@ 30@@ 30@@ 60@@ 60@@ <0@@ <0@@ 83@@ 8?@>@ 0@(E*@ @(E@d @(E@J @@J @@J @0@8 @@ @@ @ @ @?@ @ -F|9 RROFigure1-2:7SendingBITNETmailbydirectuseofNJE software.E9i mEKKC??s s`?001Øa @ ØDZa?ư3?0303;l0 ?sl0@ |0 @b ?80 @@ ?80 @(RC @8B!`1B @@(B"`)B@s`S?@?@@?@ @|@T@E@@8Cw8B@ @@0@pp0@0<@ 0<<@ h0f(O @ Sp0f@@`p0~@.0 G6@( a``9@F@ @@@B @0@@b @<a (@A (&@B(@j@n@@@ `@`@0@?@ @?`G ? D D D!` Dq D 1D\ } DR VUP!DU# !!D? !R!D`~ s9sD  DXu` D! ? DV` D ` D@@ D`  DX`0 DF  !DU` D`@b  DXU_:` D@? DUWWkP?>G0xD?>A@\UWUիQ>C@>#@@Uu]]Q> ?@0  >\WUUUS > `" > T]UUwuS D@UUUUU S 9WUUU_ 8?U?UUUUUU:r _p? ? ?UUUUuWWk}@D?VUUUUUUTUUU]]mWU]xTUUUUUU_WU" Jx?XUUUUwu5WUW?D@$xD D >D  >€  >?xx | |~ |`  |> ʓ >#E >$ >(ÑM @@~0 @@| @ |  |  | |< x G |J) 8F @  @ ` `@ P@00 !P  !( !(  !$` !$` ! @ !"88 |!!EUc!&G6,F!`8ET,E!@|l!~@!~`@@!0@!| @!|@!|@@! @! @b!@! @g!!@!@!@!@@! @!B@ "@ @ @ @ @?@ @@@@@@@@@ @ @  ? ~  ? cx  c`  g  ;ff 8 H3ff8 8sffxf cff xfg c` cx f?f~gf     @ @ @ @ |@?|@ @ @|@|@ @ @ @|@x|@@@@@@@@@@@@@@*! KO1.1BDirect Transmissionof ElectronicMailbyNetworkJob(Entry&OOnacomputersystem(or%node#)onBITNET,themailKO applicationis supportedbya specializedsoftwaresystem,NO^calledamailer,which transfersmailamonglocalusersandOO applicationsandmailersonremotenodes.'Mailis transferred,Obetweenmailersusingfilesin'BatchSimpleMailTransferOhProtocol(BSMTP)).hformatandBITNET'sbuilt-inhNetworkOJobEntry(NJE)%filetransfer facilities.I+GOBeforemailerswere developed,acopyofeveryBITNETIOmailmessagewassentdirectlyfromthesendertoeachKO5 recipientasaseparateNJEfile.+ThisapproachhasmanyDOdisadvantages.'Someofthemost importantonesare:,! e `mHmOnlyusersand applicationswithdirectly reachableNJEH addressescanreceivemail.)This precludessendingmailGto addressesonothernetworks connectedtoBITNETbywmail gateways. `MSendingseparatecopiesofamessagetoevery addresseeisHOwastefulofnetwork bandwidth,central processorcycles,Canddiskspace.-Thisproblemis compoundedbytheGfactthatthereisno standardizedgroup communicationBY applicationonBITNETexceptthosebasedonmail. `!TheNJE envelope,!or tag$,!does not includethe>0 informationneededforadequateerror handling. `HWhennomailerispresenttoinsulateusersfrommailF transports,endusersmust explicitlyaddressmailto?a different networks,forexample, BITNETandtheF Internet..Mailersallowmailtobesenton differentA networks,simultaneouslyandtransparently,fromajsinglejuseragent bj. `JUsingNJEsoftwaredirectlyfor electronicmail increasesFBthe difficultyofadaptingtonewmail transportandFuser interface technologies.*ThiscausesproblemswhenG switchingfromother transportstoNJEandagainwhen6L switchingfromNJEtoother transports.-! WOOToavoidtheserious disadvantagesofdirectNJE transmissionHOofmail,theCRENBoardofTrusteesandits TechnicalCO5Advisory CommitteehavemandatedtheuseofmailerNOsoftwareforBITNETnodesthatsendorreceivemailthroughKOINTERBITmail gateways.&Therearethreereasonstoswitch)O>to mailer-basedBITNETmail:. D`m1.:AlmosteveryBITNETuserusestheINTERBITmailDgatewaysatleastonetime,sotheCRENTermsandI Conditionsof Membershipand Affiliationrequiresyoutowinstallamailer.K`2.:Therearemany technical advantagesandno significantOdisadvantages.M`3.:CRENhasworkedhardtomake installingamailereasy./NMOThe sponsorshipofthe developmentand distributionofthisIObookisonewayCRENis supportingthe installationofO5BITNETmailers.>! e M2F5Toobtainacopyofafilefrom LISTSERV,sendtheLISTSERVcommand! GETfilenamefiletypetotheNJEMaddressoftheserverasan interactivecommandorinthe9>bodyofan electronicmailmessage,where> filename>isthe+VMfilenameofthefile,and filetype#istheVMfiletypeofJthefile.*Forexample,togetthefileCRENTERMSfromBHtheLISTSERVserveronnodeBITNICbysendingan& interactivemessage,enter"T $SENDLISTSERV@BITNIC GETCRENTERMS8\.MostpublicBITNETfilesare availableFRfromtheLISTSERVserveronnodeBITNIC,operatedby4theBITNETNetwork InformationCenter.:YoumustsendLISTSERVcommandsfromnodesE[ registeredinBITEARNNODES,ortheserverwillnotVbeabletosendfilestoyou.(ToobtainafilebeforeyournodeJ is registered,askforthe assistanceoftheTECHREPorCe Postmasterofa registerednodeadjacenttoyours.0A  M3J5Thisfileisprovidedasa print-typefilewithFORTRANEcarriagecontrolofforms skipping, underscoring,andGbolding.-ForVMStoproperly recognizethese controls,I>RMS attributemustbe correctlyset.+ThesesettingscanLbechangedwithJoeMeadows'FILEutility, availableasa5VMS_SHARfilefromanyNETSERVserver.@HRequesttheFILEutilitybysendingthecommand GETMODATTCOM+toaNETSERVserver,suchas;NETSERV@BITNIC.Receivethecommand procedure>R MODATT.COMintoanempty directoryandrunitFtounpackthefiles./Followthe instructionsprovided7toinstalltheFILEutility, thenenter $FILEfilespec-[ #/ATTRIBUTES=(FORTRANCC,NOIMPLIEDCC)[toto0setthecorrectRMS attributesoni filespecvfortypingor  printing. =).O1.3BBITNET Technical RequirementsJOUEveryCRENmemberand affiliateisrequiredto implementGOCREN technical standards,andtomakeeveryeffortto=O implementCREN technicalrecommendations./TheseHO^ requirementsarepartoftheCRENTermsand ConditionsKOof Membershipand Affiliation, publishedasthefileCREN2OTERMS, availablefromLISTSERV@BITNIC  2 .*="/>?VOVItisoneofthe objectivesofthisbooktohelpyoumeetthese*OBITNET technical requirements:@! >F`m1.:EveryBITNETnodemustacceptmailforthelocal8 addresses POSTMASTERand POSTMAST,inanyG combinationofupperandlowercaseletters.,AllsuchJwmailmustbepromptly deliveredtoatrainedpersonwho?cansolvenetworkproblemsandanswer inquires.B`O2.:EveryBITNETnodethat exchangesmailwithan?INTERBITmailgatewaymusthavemailersoftwareF compliantwiththeBSMTPspecification,asdefinedin$YthefilesBSMTPLISTING < 3YandBSMTP ADDENDUM,= availablefromLISTSERV@BITNIC. Currently,PMDF and v MX7 aretheonlyBSMTP-compliantmailersfor@btheVAX/VMS environmentknowntome.+ (AdditionalF informationaboutMX,apublicdomainmailerbyMattNMadison,of Rensselaer Polytechnic Institute,isinthefile7lMXINFO, availablefromLISTSERV@BITNIC.)J`3.:OfficialINTERBITmailgatewaysmustrejectmailfromJDtheInternetthatis addressedtoBITNETsystemswithoutG registeredBSMTPmailers,andrejectmailfromsystemsJwithouta registeredmailerifthemailis addressedtoMInternet addresses.J`4.:OfficialINTERBITmailgatewaysmustrewrite addresses% correctly:*@"/AB G;a.:FQDNsmustnotbemodifiedwhengoingthroughthe/Ymailgatewayineither direction.+b.?NJE addressesoftheform3username@nodenamemustCYkbe convertedto domain-style addressesoftheform/Y%username%nodename.BITNET@gateway_fqdn(the``%-BYhack'' convention)onthewayfromBITNETtotheYu Internet,whereu gateway_fqdn"uisthefully-qualifiedAYdomainnameoftheINTERBITmailgatewayitself.4Mc.? Domain-style addressesoftheform/Y%username%nodename.BITNET@gateway_fqdnmust:Ybe! converted!to NJE addresses of the!formYVusername@nodename/VonthewayfromtheInternettoYBITNET.G.d.: Addresseswith``!'',inusernamemustbe rejected,=Ybecause the! precedence!of ``!''4and ``%'' in)Yabc!mno%xyz.BITNET@gateway_fqdnis undefined.CHOINTERBITmailgatewaysacceptNJEfilestaggedforthe>ONJEaddressSMTPUSER@INTERBITand interprettheJO5BSMTPcommandsinthefilestoforwardmailtoInternetFO addresses.)The requirementsforINTERBITmailgateways availablefromLISTSERV@BITNIC.OfficialINTERBITLOsitesarelistedinthefileBITNETGATES, availablefrom>OLISTSERV@BITNIC. Unofficialmail gateways,whichDOHincludealmosteveryBITNETsystemwithanInternetMO connection,shouldstrivetocomplywith requirements3and O4.DZUOStrictly speaking,ifusersatanodedonotrequiretheuseofGOINTERBIT gateways,CRENdoesnotrequirethatnodetoQO5runamailer.)However,itis practically impossibleforactiveIOBITNETuserstoavoidusingINTERBIT services.(Toavoid$OusingINTERBIT services:-E@ `mHmLocalusersmustneversendmailtoInternet addressesDovertheirBITNET connection(forexample,withtheCGMAILcommand procedure,byEdMiller,ofStanford'wLinear AcceleratorCenter). `GRemoteusersmustneverattempttoaddressyourlocal0OusersthroughanINTERBITgateway. `GUsersmustneverreplytooldmessagesthat traversed.'anyInternet/BITNETmailgateway.F! QO Installingamailerandnot registeringitisjustasbadasMOnot installingamaileratall.)TheINTERBITgatewayswillPO5notknowyouhaveamailer,sotheywillbounceyourusers'NOmail.)The performanceand usabilitybenefitsof installingaROmailerwillnotbe realized,forthesamereason:'remotenodesLO>willnotknowtheytheycantake advantageofthemailerO protocols.<GLOIn conclusion,thereisreallyno practical alternativetoLO correctly installingand registeringamailertomeetyourCO5organization's obligationsundertheCRENTermsand7O Conditionsof Membershipand Affiliation.1H 2O1.4BBenefitsof InstallingaMailerNOU Fortunately,thereareseveral substantial, immediatebenefitsPOofrunningamailerthatoffsettheextraexpenseandsystemO managementeffort. I! *O1.4.1BMailersEase AddressingIO4UsernameslongerthantheNJEmaximumeight charactersKOare correctlyhandledbymailers,since addressesarenotLOconfinedtothe eight-bytefieldsintheNJEtag.+Domain-EO=style hostnamescanalsobelonger,!and thus more?O meaningful,thaneight-characterNJEnodenames.3J  SOMailersallowtheuserofasingleaddressformat,suchasthe OIN%EformatusedbyPMDF,forBITNET NJE-style addresses,GO5BITNET domain-style addresses,andInternet domain-styleJO addresses.*Every correspondentcanbe addressedusingtheOOmostnaturalformofaddress,andthereplyfunctioncanbeNO>usedwithall messages.'Localusersneedneverbe concerned6Owithwhatnetworka correspondentuses.K GOMany BITNET-onlynodes(thatis,nodeswithnodirectGOInternet connection)nowsendallmailwithadomain-JO5stylereturnaddress,andthispracticeisbecomingmoreMO widespread.*Ifyournodedoesnothaveamailer,youmustAOusetheVMSmailSENDor FORWARD/EDITcommandstoRO>sendtoa differentaddressthanthereturnaddress,sincetheEOVMSmailREPLYcommandwon'twork.(The resultingmailHOmustgooverInternettoanINTERBITmailgatewayforNOHretransmissiontothefinal addressee,delayingthemailand3Owastingnetworkandsystem resources.2L GOAsan alternativeto respondingtoBITNET domain-styleMO addressesasiftheyareInternet addresses,eachusercanIO5keepapersonaltableofBITNETandInternet equivalentRO addresses(oryoucanmakeone availabletoallusersofyourHOsystem),andmanuallylookupeach domain-styleaddressMO>to determineifthesystemisonBITNETonlyanditsNJEDOaddress.'Mailersperformthisfunctionautomatically.MUEO Installing a mailer allowsInternet and other globalBOnetworkusers toaddress your users by a domain-CO5stylenameinsteadofthemoreawkward ``%-hack'',Ofor!example,$1Postmaster@host.domain.Eduinstead of0O&Postmaster%host.BITNET@CUNYVM.CUNY.Edu .N! WSOEvenifyoucouldtrainallyouruserswhentobegin addressesOwith Jnet% andSMTP%>:,andevenifyoucouldgetridofalltheMO5oldmailonthenetworkwithINTERBITreturn addresses,itLOmakesmuchmoresensetoinstallamailer.) CertainlyyourMOuserswillprefertousethecommonmail addressingscheme#O>thatamailerpermits.O k@O1.4.2BMailersIsolateUsersFromNetworkChangesLO4IfyoudropyourBITNET connection completely,youneedaQOmailerevenmore.'AmailerwillallowlocaluserstocontinueLOtousetheBITNET addressesstoredonyoursystemwithoutOO=change,inmailinglistsandinthereturn addressesofoldMOmail.'Whenamaileris installed, switchingfromaBITNET-FOonly connectiontoBITNETandInternet connectionsorJOGaan Internet-only connectionis transparenttothemailO application.[P! 1O1.4.3BMailersProvideNew FunctionsEO4PMDFaddsmany importantnew functionstoyourmailMOnetwork.)Itsupports forwardingtolists,afeatureremovedBOfromVMSmailatVMSVersion5.0.0Other additionalKO= functionsincludestore-and-forward reliabilityforVMSmail-QO to-VMSmaillinks,mail directoryservice,asimplefileserver,JOand optionally, facsimile capabilitiesforanymailuser.,Q ROMailerssendallthecopiesofamessageroutedtoonesystemJOorgatewayinasingleNJEfile.,This conservesnetworkLO5 resources,andtherebyimprovesthedeliveryspeedofmailOforallusers.\"tk JJOFigure2-1:7Stepstosetupan operationalBITNETnode.\ki; [KK@@@@@p@@ϫ@"l@`(@(@(@",@p+"@>@"@A@A@@@ @@ @@@@@@D@(@@P@@@@TT888'8A(A(^A(a#@!A@!fA@!A a!`A ^!````|ësxa$l$`<!(!(`'!( ~!$,$?`!+xf |A Ax $ (tI $ @/$I P DH A$$ D0B#px0A@@@@`  < ``  P п! P! @``  @``a@@@``!@!Q@!!J2@@ @`2@@@B @@P!J@@!2@@@@B@@@<@@@@@@@@@@@@@@@@^<:W@@aBHX#@@@B(P!@@@B(P!@@@B(P!@@aBBHX!@@@ ^ADA@A @@ A0@#F`@$H@$H@ADHA@`G> @@@2 P@R@@R@@Q@>@@@@@@@ @@@@`@@@@``@@@@|`@@>``<T8808```  `0P`f@ P@`  `P@ `8@@@`@`x@8@-`8@.@X9`'@ pX@A``#@AG( 4@AHH(!8fL @A'@п @A⟤P @A$ 6@AD#!D@A#D0~@0@P <@|@P$  A@@ AyxʞG@  AHR +E?|@> A'PBt*$PA@AA% A_L$_tx@A ~ A$@PD %@@A #!ADRD+EH|@A @ALxxʄG@A  @A A@AA!!?|x@>!@@@`@Ux>x@ A1 @!P TJ II@!P T?UI@`!P TJUI@AV "1@Ux "x@` @xp@@@8@@x@@@C?8@PA0@P`@ @@@ @@@@ 0@ @@@+{`@"!@ @A(``F (``I"!+@ ``@@>@@``@@^ţ8@#a%d @@(``0@@/`@@ @!a%$ @!^#`@P @bP@1@y@ @@@0@@`@@@@@@@H@X@ @A#@AG(` 4@AHH(!L @A'@п @A⟤P @A$ 6@AD#!D@A#D@@0H>@0 !HB@PD!DB@P$D!DBp$@DB>?8B$!@$IDBT""!@ HDA8""!@ H% A8 "!@C@80"!@ @H`" @ HB @$ H@ @#H @@@0@@`@@@@@@@ @@@ @ @H@@@@~ `@J#!` @@ J@@8@@J@@ J@p@K!!@@J!@@@@@x@C8@~@@@@@@@@@@^uϣë@@#a"d$l$$0@@@(( @@@/( @@@ (`@@!a"$$,$$@@@!^#+@@@@P@@@@@@@@@@@@@@@ @ @ @ @``@  @  0PP @@ @ @  ``@0  !}UnSO2.1B Assumptions9OUThisbookmakesthe following assumptions:V!  `mImYouwillconnectorhave connectedoneormoresystemsBtoBITNET.IfyoudonothaveorplanaBITNET0 connection,donotusethisbook. `FYouwilluseasfewnames(mail addresses)foryourOsystemas possible,tosimplifytheuseofnetworkmailfor2Oyourusersandtheircorrespondents. `4YouwilluseJnetandPMDF software. `MEMIfyouhavea VAXclustersystem,youwill configureEallthenodesofthe VAXclusterforBITNET(andifD applicable, Internet)mailbyrunningPMDFoneveryIWnode,eventhoughnotallofthenodesrunBITNET(orTCP/IP) software. `/C/YouwillinstallatleasttheminimumversionsofthesoftwareinTable1.%\ThisbookexplainsmajorF dependenciesonthe installedversionsofJnet,PMDF,9andVMS. `KYouwill establishadomainnameforyoursystems,whichOwillbeusedfor addressingmailbyallyourusersandany4icorrespondentsonBITNETand Internet. `GVMSmailwillbethemailuseragentforBITNETmail.JAThisbookwillnotattempttodescribetheuseofALL->IN-1,MM,PonyExpress,orotheruseragents.*VK ?rWHHOThe following variationsare accommodatedinthisbook:XR} `mGmYoursystemmayalreadybeonBITNET,oryoumaybe;addingyourBITNET connectionatthistime. `EEEYoursystemmaybeasingle, standaloneVAXsystem,Ca homogeneous VAXclustersystem,ora heterogeneousD VAXclustersystem.'(Thisbookexplainstheseterms.) `vAvIfyouhavea VAXclustersystem, youcaneitherE configureallyour VAXclusternodesasBITNETnodes,+'oronlyasubsetofthem(a' subclusterh'configuration). `EYoursystemmayalreadybeonaDECnetnetwork,orKyoucansetupaDECnet connectionatthesametimeasCWyourBITNET connection,oryoucanhavenoDECnet3 connectionandnoplanstoaddone. `/E/Yoursystemmayalreadybeon Internet,oryoucanJsetupanInternet connectionatthesametimeasyourEBITNET connection,oryoucanreservetheoptionof@9 connectingtotheInternetatsomefuturetime.YNJOOther combinationsofsoftwarecanbe configuredtomeetKOCREN requirements,butsuchconfigurationsareoutsidethe O5scopeofthisbook.x$#%o9O3.1BStarting assumptionsfornameplanningGOUThischapterassumesthatyour organizationhasjoinedOBITNETby:1pI f `m?m CompletingaCREN Applicationfor Membershipor AffiliateStatus `EFE Receivingapprovalfrom membershipor affiliationfrom(theCRENBoardofTrustees `*PayingitsCRENduesinvoice `A Appointing institutionalrepresentatives:.Memberor? AffiliateRepresentative, TechnicalRepresentative M(MTECHREP1M),and InformationRepresentative(rMINFOREP M)3q HOThe remainderofthischapterisdirected primarilytoHOtheTECHREP,whomIcall``you''inthischapter..TheBO5TECHREPis responsiblefor coordinatingtheBITNET7Onamesandtopologyforthe organization.;r DOBefore continuing,makesureyouhavereceivedyour=OTECHREP informationpacketfromBITNIC.BITNICPO5mailsthispacketinhardcopyformuponreceiptoftheforms@O appointingyouasTECHREPforyour organization.%$&s ;O3.2BGeneralconsiderationsfornetworknamesLOUOnceanamecomesintouseforasystem,user,orotherEOnetworkentity,thenamespreadsrapidlythroughtheGOinterconnectednetworksof computersandpeopleinthePO^formof directoryentries,return addresses,routes,andotherMOnetwork information.)Itishardtochangethis information,KOinboth computersandpeople,evenusingsuchdevicesasIOh forwarding addressesand electronic``changeof address''MOnotices.( Therefore,planningtheuseofnetworknamessavesPOtimeandeffortbecauseitreducesthefutureneedtochangeOrnames. t JONameplanningshouldbedoneforallsystemsunderyourLOadministrativecontrolatthesametime,soastohaveaOO5coherentnamesystemthatwillserveyouforthe foreseeableOfuture.,u DO Authority fornames should be clearly vestedinanJOorganization-wide authority appointedbytheorganization'sMO5chief executiveofficer,suchasthechairofacampusorIO corporatenetworkgroup.'Namesofsystems sometimeshaveMOorganizational connotations,andthename authorityforyourOO> organizationshouldhavetheclout, sensitivity,and expertiseBOtodealwithboth politicaland technicalissues.vhEOThenamesyouapproveshouldmeetasmanyofthese#O guidelinesas possible: w!   `mJmNameshouldserveonlyforidentification,andnotimplyE addressingorrouting.+The organization operatingtheIsystemisoftenausefulsourceforaname.+WithinanKw organization,itisoftenusefultogivesystemseasy-to-Dremembernamesfromaseriesthatisnot otherwiseB( meaningfultothe organization, suchasplanetor wildflowernames. `@Eachsystemcanhavemanytypesofnames,eachDY conformingto differentrules.-TrytomakeasmanyKofthesethesameaspossibletominimizethenumberofA nameswithwhichnetworkusersandmanagersmustbcope. `INamesshouldbeshortforeaseoftypingand remember-:ing. `INamesshouldbeglobally descriptive.+SinceyouwillbeG participatingininterconnectednetworksthatspanfiveEj continents,avoidnameslike``VAX1''and ``PHYSICS''Lthatgivenocluetotheownerorlocationofasystem. `B>BAvoid namesthat could be embarrassing to theK organizationor individuals.(Namesintendedtobe``cute''Lmayseemsillyorbe offensivetothosethatspeakother@L languagesorhave differentcultural backgrounds. `@Namesshouldnotmake referencetothesystem'sE$  manufactureror operatingsystem.'NetworknamesoftenF| outlivethehardwareandsoftware platformsforwhichE theywerefirst established,andbecome inappropriate8. whentheyarere-usedforanewsystem. ` F Thenameofthe organizationitself, ``Harvard'',forC example,shouldonlybegivento centrallymanagedH^ systems,suchastheprimary timesharingsystemforan% academiccomputercenter. `6 C6  Hierarchicalnamespaces,suchasthedomainnamesK usedforInternethosts,shouldbewideandshallow,notG deep.(AnamingsystembasedoncampusandhostwouldL? easiertosetupandrequirelesschangesovertimethanF onebasedoncampus,college, department, system-type, andhost."&%'x(O3.3BNamesforBITNEThostsLOUBITNEThosts,ornodes,haveatleasttwonames:)NJEandEOdomain.,(Thedomainnamewasformerly optional.,ThisMObookassumesyouwill establishandregisteradomainnameHO^andexchangemailwiththeInternet community.,Ifthis@O assumptionisnottrue,donotusethisbook.)Py &JOIn addition,VAXsystemsrunningVMSmayalsohaveJnetEOclusternames,SCSNODEnames,DECnetPhaseIVnames,EO5 DistributedNameServicenames,VAXP.S.I. addresses,CO VAXclusterDECnetaliases,UUCPnames,andsynonymsSOoraliasesforsomeofthese.(Insofaras possible,namesforaMO>systemshouldallbethesame,and VAXclusternamesshouldPOberelatedtothenamesofsystemsthatmakeuptheclusterOinanobviousway.'&(z wcAO3.4B Suggested procedureforplanningsystemnamesKOUWhenplanningyoursystemandusernames,seekhelpfromIOyourorganization'snetworknaming authority,orifyourNO organizationhaslittle experienceinthisarea,fromBITNIC@O^andother applicablenetwork informationcenters.('){z7O3.4.1BSummaryofnameplanning procedureMO4Ifyouare experiencedatplanningnetworknamesinglobalHO networks,usethe following checklisttomakesureyouHOhave consideredalltherelevantissuesinnamingyourJO=systems.+Ifyouhavenot previouslyreviewedyoursystemMOnamesusingthecriteriainthischapter,followthestep-0Oby-step instructions beginningwitheSection3.4.2,IanduseJOGthe following checklistafteryouhave completedallthe*O instructionsinthischapter.*{e?} | `-Z `/T /T `Z/mPlanSCSNODEand DECnet-VAXnames `Z `T T `Z=For VAXclusters,plana VAXclusteraliasname `,Z `.T .T `ZlPlandomainnames `Z `T T `Z0If necessary,registeryourdomain `*Z `,T ,T `ZkPlanNJEnames `Z `T T `Z3Planreservedandgeneralusernames.-/ :O3.4.7BPlanreservedandgeneralusernamesGO4ThereareusernamesthatareconventionallyusedforJOspecificpurposesonBITNETnodesandInternethosts.+IfPOyouaresettingupanewsystem,orifthesenamesarenotQO=yetinuseforanypurpose,youshouldtakestepstopreventHOthemfrombeingassignedtogeneralusersor otherwiseNOusedinwaysthatconflictwiththeir conventional purposes.HOGIftheseusernameshavebeenassignedfor conflictingHOuse,youshouldmakeeveryefforttoreclaimthemforIOtheir conventional purposes.+UsingthesenamesfortheirJOQ conventionalpurposesonlywillmakeiteasierforotherNOnetworkusersandmanagerstodealwithyoursysteminthe'Oglobalnetwork environment.A0/1  (O3.4.7.2CMAILERandSMTPUSERJO)Whenamaileris configuredonyoursystem,BITNETmailHOfilessenttothemaileraddressarehandledbyPMDF.O(SeeSection1.2:foran explanationofthemailer concept.)AO3MAILERisthe recommendedusernameformailers,PObecausethenameclearly indicatesthepurposeoftheaddress8Oandbecauseoflong historical precedent.*?0! BOYouwillforwardmailforMAILERtoPMDF'sBSMTPOO interpreteratthePMDFlevelwhenyouinstalland configureKO5PMDF.ThereisnoneedtocreateausernameofMAILERMOintheSYSUAF,butyoushouldverifythatnoMAILERentryLOexistsnow,andmodifyyouraccountcreation procedurestoGO>preventthenameMAILERfromeverbeingusedforanyOotherpurpose. JOToquicklydiscoveranymail incorrectlysenttoMAILER,>OforwardMAILER'sVMSmailto POSTMASTER.IfforFO5somereasonPMDFshouldbecomedisabled(forexample,EOby upgradingJnetand forgettingto reinstallPMDF'sDO replacementfortheJnetcommand procedure LMD.COM),EO>BSMTPmailfrom othermailerswillbesentto yourEO POSTMASTERaccountwheretheproblemwill immediately>Obecome apparent.+FromanaccountwiththeVMSSYSNAMOH privilege,enter:OMAIL>+/FORWARD& /USER=MAILER% POSTMASTERD KOSomesitesuseSMTPUSERforthemaileraddress.(TaketheHOsimple precautiontoreservetheSMTPUSERnameatyourKO5siteandforwardanymailtoittothe Postmasteralso.OMAIL>-/FORWARD&/USER=SMTPUSER& POSTMASTERY102)O3.4.7.3CLISTSERVandNETSERV?O)LISTSERVandNETSERVareBITNETserverprogramsHOwidely installedonIBMVMsystemsonBITNET.Versions@Oarenot currently availableforVAX/VMSsystems.nHONETSERVprovidesfileserver functionsforvariousdataBOandprogramfiles includingBITEARNNODES.NETSERVMO5 generatesand distributesthenewroutingtableseachmonthGOforthosenodesthathave requestedthatservicefromPOBITNIC.Italsoprovides directoryservicesforgeneralusers.X! .COYoushouldnotassigntheusernamesLISTSERVandKONETSERVtoordinaryusers,andyoushouldnotrunserverHO5softwareundertheseusernamesunlessthesoftwareisLO compatiblewiththeIBMVMversionsand interoperateswithOOtheVMversionsastruepeers.*(SuchsoftwareisnotlikelyOO>tobe availableforyears,ifever.)+ChooseothernamesforMOserversthatarenot completely compatiblepeersofIBMVM!OLISTSERVandNETSERV.5 JOVerifythatnoLISTSERVorNETSERVentryexistsinyourHOSYSUAFnow,andmodifyyouraccountcreation proceduresFO5topreventthenamesLISTSERVandNETSERVfrombeing3Ousedforanypurposeinthefuture.213q! LGO3.4.7.4CJOBPO)JOBisthe conventionalusernameforthebatchinputstreamBOonIBM mainframesrunningMVSandVAX/VMSsystemsROrunningJnet.(When installingJnet,youcanelecttosetupaMO3batchserver,andJOBisthe recommendedanddefaultname.8KOVerifythatnoJOBentryexistsinyourSYSUAFnow,andGOmodifyyouraccountcreation procedurestopreventtheLO5nameJOBfrombeingusedforanypurpose,otherthanthe0OJnetbatchserver,inthefuture. 324-O3.4.7.5CSYSTEM,ROOT,andMAINTCO)SYSTEMisthesystemmanagerusernameonVAX/VMSHOsystems,whichDigital recommends reservingforsoftwareKO installationsandsystembackup operations.)IBMandJoinerDO3 recommendthatSYSTEMbeusedinasimilarwayonHOIBM Application System/400systems,astheUserIDfor*Othesystem operator,QSYSOPR.e! ;>OOnIBM mainframesrunningVMorMVS,however,EOSYSTEMisreservedfor addressingthesystemdefaultNO5printerandpunchdevices;mailsenttothese addressesmayEObe discarded..Nodalmessagerecords(NMRs,orsimplyHO ``messages'')toSYSTEMaretreatedascommandstotheOO>NJEsoftwareonthesystem(RSCSorJES).Inthesameway,KOJnettreatstomessagestoSYSTEMasnetworkcommandstoCOJnet,andnotasmessagestothesystem operator.sIIOBecauseoftheseinconsistencies,takethese precautions:j `mImDonotsend messages,files,ormailtoSYSTEMonanyABITNETnodeunlessyouknowthe operatingsystemErunningonthenodeandtheeffectofyouraction. `GDonotsend messages,files,ormailfromtheSYSTEM>accountonyoursystemtootherBITNETnodes.! GORemoteBITNETusersmayattempttoreacha knowledge-TOableuserofyoursystemtoreportaproblemoraskaquestionKO5bywritingtothe conventionalsystemmanageraccountforEOvarious operatingsystems:(SYSTEM(for VAX/VMS),ROOTHO(forUNIX),orMAINT(forVM).ForwardmailfortheseKO>usernamestothe Postmasterforpromptand knowledgeable6O handling.*FromanaccountwiththeVMSgSYSNAMc privilege,Oenter:OtMAIL>+/tFORWARD& /USER=SYSTEM% POSTMASTEROMAIL>)/FORWARD& /USER=ROOT% POSTMASTEROMAIL>*/FORWARD& /USER=MAINT& POSTMASTER)DOVerifythatnoROOTorMAINTentryexistsinyourHOSYSUAFnow,andmodifyyouraccountcreation proceduresFO5topreventthenamesROOTandMAINTfrombeingused-Oforanypurposeinthefuture.435_'O3.4.7.6CPMDFand PMDF_USERLO)Duringthe installationofPMDF,youareaskedifaPMDFEOor PMDF_USERentryshouldbecreatedintheSYSUAF.GOPMDFisa nonprivilegeduserthatwillownmanyPMDFDO3filesandunderwhichcertainPMDFjobsrun.-PMDF_OOUSERisa privilegeduserrequiredforthe operationoftheFOPMDF-FAXoption.,DonotconfusetheseuserswiththeEO<mailerusername,MAILER.YoushouldnothavetheseNOentriesintheSYSUAFunlessyouhave installedtherelatedIO products./ ElectronicmailshouldneverbesenttotheseOF accounts.WnHOVerifythatnoPMDFor PMDF_USERentryexistsinyour>OSYSUAFunlesscreatedbythePMDForPMDF-FAXHO5product installation procedures,andmodifyyouraccountHOcreation procedurestopreventthenames beginningwithGO``PMDF''frombeingusedfornon-PMDFpurposesintheO>future.74 POTable3-1:7 Campus-widenetworknamespaceexample:"BayCollege O OFSystem"KFBITNETDECnetInternet Ob  O IBM mainframeBAYADM[ Adm.Bay.EduO$ VAXcluster%K$ BAYACAXBAYACAX Aca.Bay.EduO VAXservers'K BAYACBcBAYACBc B.Aca.Bay.Edu'K BAYACC]BAYACC^ C.Aca.Bay.EduO VAXstations" ELVISElvis.Aca.Bay.Edu$  BOPPER~Bopper.Aca.Bay.Edu$ EVERLYnEverly.Aca.Bay.Edu  ... [ ...Ox UNIXservers[x Popcorn.CS.Bay.Edu[ Pretzel.CS.Bay.EduOl UNIX workstations[l Cracker.CS.Bay.Edu[ Cookie.CS.Bay.Edu [_ ... O G 546j'O3.4.7.7CGeneralusernamesAO)BITNETplaces limitations onusernames.2AlthoughIOVAX/VMSsupportsusernamesofuptotwelve characters,JOandwhilePMDFandothermailerscanhandlelongeruserFO3names,onlyeight charactersare supportedforBITNET)Omessagesandfile transfers.| RMOTominimize confusionamongusersofyoursystemandtheirMOnetworkcorrespondents,andtomeetthe requirementsoftheMO5most restrictiveuseragentsoftwareusedonBITNET,followIOtheserecommendationsin assigningusernamestogeneral"Ousersofyoursystem:i? `m4mLimitusernamestoeight characters.uKJWIfyouareworkingwithanexistingsystemthatalreadyFhasuserswithlongerusernames,makesurenouserHnamehasthesamefirsteight charactersasanyotherGausername.*Reassignusernames,if necessary,tomeetthis constraint. `9J9 Constructusernamesofonlylettersanddecimaldigits,Iwiththefirst characteraletter.-Forexample,donot/includeIBMnational characters( $ , @ ,and #),spaces,$B underscores,orhyphens. `BDo notcreatea user namewith samefirst eightD charactersasthenameofanBITNETlink (adjacent>ssystem)orNJEserverrunninginyoursystem.O! %NWInthecaseofa conflict,theusermustusuallyyieldtoKalink,sincethelinktakesitsnamefromtheadjacentKsystem,and ordinarilyyouwillhavenocontroloverthe?anameassignedtoothersystemsinthenetwork. `EIfyourunALL-IN-1 IntegratedOfficeSystem,assignE9eachALL-IN-1userhisorherownVMSaccount,andJassigneachuseranALL-IN-1username identicaltohis#orherVMSusername.! !GWBlanks,used frequentlyinALL-IN-1usernames,cannotCbeusedinBITNET addresseswithcertain important<BITNET software, includingJnetand LISTSERV. 658O! %'O3.5BCampusnetworkexampleIOUBayCollegehasacentral timesharing VAXclusteroftwoEO timesharingsystemsandten workstationsforacademic=O computing,!an IBM mainframe for administrative=O^ computing,!twoUNIX servers and a dozenUNIXFO workstationsforcomputerscience.,TheIBMsystemandFOthe VAXcluster timesharingsystemsareonBITNET,theNOhVAXsystemsareonalocalDECnetnetwork,andallsystemsOareon Internet.uaKHOTheCollege Presidenthas designatedtheVice PresidentAOfor InformationandCommunicationsSystemsastheFO5 authorityforcampusnetworknames,whohas delegatedBOthe developmentofanamingschemeand day-to-dayKO assignmentofnamestothechairofthenetworkcouncil,GO>a committeehostedbytheacademiccomputercentertoHO coordinatecampus networks.*Thecouncilchair developed,KOandthecouncil approved,theschemeforsystemnamesinOHTable3-1.*O a? NOBayCollegeallowssystemadministratorstochoosetheirown7Oschemefor assigningusernames,except: `mJmnamesmustconsistofonly uppercaselettersanddigits,:andthefirst charactermustbealetter, `EGEnonamesonthesamesystemmayhavethesamefirst!eight characters,and `CordinaryusernamesmaynotbeMAILER,JOB,ROOT,9vSYSTEM,orMAINT,orbeginwith POSTMAST.maC@OThe POSTMASTERusernameanditseight-characterEO abbreviationPOSTMASTisusedoneverysystembyanIO5 electronicmail coordinator,who,onthelargersystems,GOchecksmailmanytimesaday.,MAILERisreservedforCOtheBITNETmail application,andROOT,SYSTEM,andMO>MAINTare(orare forwardedto)themailboxofthesystemEO programmerforeachsystem..JOBistheNJEnameofEOthebatch subsystemontheVMSsystemsandtheIBMOH mainframe.M8693# 6O 4.< Installing&and' Configuring' NetworkingOrSoftwareJOThischapterprovidesanoverviewofthe installationofBOO DECnet-VAXandTCP/IP software.-YoushouldinstallFODECnetandTCP/IPsoftwarebefore installingJnetandEOPMDF.BothJnetandPMDFcanuseDECnetandTCP/IPJOYnetwork services,andthe configurationofJnetandPMDFPOiseasierifthe underlying networkingsoftwareisalreadyinO place.98:{! Q0O4.1B VMSINSTALand autoanswerfilesDOUVAX/VMSsoftwarefromDigital,Joiner,and Innosoft,BOandVAX/VMSTCP/IPsoftwarefrommanyvendors,isIO installedwiththeDigital-supplied installation procedureO^ VMSINSTAL2O^,inthe directory SYS$UPDATE.WhenHO installing software,consideradoptingthe conventionof9O documentingyour installationbyusingtheu autoanswerIOhoptionof VMSINSTALandleavingthe generated autoanswer/Ofileinthe directory SYS$UPDATE.MOThe autoanswerfilecontainsallthe questionsaskedduringNOthe installationandyouranswers,andthecreationdateofMO5thefileshowswhenthe installationtookplace.) AutoanswerQOfilesarealsousefulin reinstallingaspecificversionofaKOsoftwareproduct,shouldthateverbecome necessary.)WhileKO>a product's installationdialoguecanbechangedfromoneQOversiontothenext,havingthedialoguefromthe installationOOofthepreviousversionofthesoftwarecanbehelpfulwhenLOH upgrading.)The installationsshowninthisbookassumeyou+Oare followingthis convention.4:9;X! .'O4.2BChangingSCSNODEnamesIOUIf necessary,changetheSCSNODEnametothenewvalueOyouplannedinSection3.4.2."}TochangetheSCSNODE>Onameandthe correspondingnumeric SCSSYSTEMID,?O^editthefileSYS$SYSTEM:MODPARAMS.DAT,thenrunBOSYS$UPDATE:AUTOGEN.COM,as explainedinSection6.1Oofthe0/ GuidetoSettingUpaVMSSystem$.'Itwillbe necessaryEOhtorebootyoursystemtomakethechange effective.*p?}KOOnasysteminactiveuse,changingtheSCSNODEnameisMOlikelytocauseproblemsinthe operationofmanysoftwareKO5 products.+Trytomakethechangebeforethe beginningofPOabusinessday, advertisewidelythattherewillbeasystemNOchange,andplantospendtheday reconfiguringsoftwareinSO>responsetoproblemreports.)HereisapartiallistofusesofOSCSNODE:V O ,  `mAmSCSNODEand SCSSYSTEMIDmustbesetinthefile3"SYS$SYSROOT:[SYSEXE]MODPARAMS.DAT.ThereDisaseparate MODPARAMSfileforeachsysteminaw VAXcluster. `CSCSNODEisusedbytheLicense ManagementFacilityEOtocontrolwhichsystemsmayloadsoftware licenses.BCheckthe/INCLUDEand/EXCLUDE qualifiersintheIlicensedatabaseforthechangedSCSNODE.Alicensefor0YVAX-VMSshouldalwaysbe affected. `7TheSYSMANSTARTUPdatabaseusesSCSNODEE0toenableordisabletherunningofstartupcommand procedures. `EJnetusesSCSNODEaspartofthenameoftherootRa directorytree(ortrees,ifyouuseasplitJnetdevice).)IfHJnetisalready installed,changethesenames manually,Bor reinstallJnetwith VMSINSTAL,tousethenewjSCSNODEname. `The DECnet-VAXexecutorname (nodename)ofyour?BsystemmustmatchtheSCSNODEname.*IfDECnet-@VAXisalready configured,changethe DECnet-VAX@executorname manually,or reconfigure DECnet-VAX:LwithSYS$MANAGER:NETCONFIG.COM,toresetthe8executornametomatchtheSCSNODEname. `$ D$ Ifyouarerunning VAXcluster Software,theSCSNODEK| nameisusedtoqualifythedevicenamesinyoursystem? configuration.-Forexample,iftheSCSNODEnameE. isBIOLAB,diskdeviceswillhavethenamesofthe> form BIOLAB$Ddcu.+ManysoftwareproductscreateD startupandothercommand proceduresat installationF7 timethatcontainthesedevicenames.)UsetheSEARCH? commandtosearchfortheoldSCSNODEnameinJ command proceduresinthe directoriesinthesearchlistCA  SYS$STARTUP,andeditthe procedurestochangethe devicenames. ` = DECnetnodenames,whichshouldmatchSCSNODE>q names,"are used!in the!startup procedures!for5  DECwindows(seeSYS$MANAGER:DECW$PRIVATE_L"APPS_SETUP.COM)andDSNlink(seeSYS$STARTUP:DSN$STARTUP.COM).5{Editthesefilestochangethenames. `FBatchqueuenamesareoften qualifiedbynodenames,LSandareoften initializedtorunor autostartonspecific?nodeswiththe/ONor /AUTOSTART_ON qualifiers.EExamineallqueues,createany necessarynewqueues,J\makeanychangesrequiredtoexistingqueues,anddelete(queueswithobsoletenames.2 LOWhenyouhaverebootedyoursystemandrunforaweekdayHOwithoutanyreportsofproblemscausedbychangingtheBO5SCSNODEname, youcanturnyour attentiontothe2O configurationof DECnet-VAX software.<;=2O4.4B Configuring DECnet-VAX ExtensionsCOU DECnet-VAX ExtensionsisoptionalsoftwarethatcanGObe installedwith DECnet-VAXV5.4orlatertoprovideOcertain,fOpenSystems Interconnect(OSI) functionsinLO^thecontextofaDECnetnetwork.,Asofthiswriting,theHOonlyreasontoinstall DECnet-VAX ExtensionstosupportCOBITNETorInternet networkingistosupportBITNETOOhlinksoverOSIsessionswith Digital'sOSI ApplicationKernelFO(OSAK)product.*The configurationofBITNETorTCP/IPNO applicationsoverOSInetworksisoutsidethescopeofthisOrbook.NGOIfyourequire DECnet-VAX Extensionsforyourconfigu-UOration,youcaninstallitnoworatanytimeinthefutureto/O5supportemergingOSI applications.M=<>= #O4.5B ConfiguringVMSmailJOUIfthissystemisamemberofa homogeneous VAXcluster,ROyoushouldsetthreeflagstocontrolthedeliveryofVMSmail.OIncludethecommand5O$&DEFINE/SYSTEM/EXEC%MAIL$SYSTEM_FLAGS%7j @BOinthecommand procedureSYS$MANAGER:SYLOGICALS.COM.NODefiningthislogicalnamebypassesDECnetformaildeliveryNO5withinthe VAXcluster, announcesthearrivalofmailonallJO VAXclusternodes,andincludesatimestampinnewmailOannouncements. WIOIfthissystemisnotpartofa homogeneous VAXclusterNObecauseitdoesnotshareaSYSUAForVMSmailprofilewithMO5anyothersystem,orbecausethesystemsinthe VAXclusterEOarenotallrunningPMDF,youmustset MAIL$SYSTEM_MOFLAGStoanevennumber(4or6is recommended)orleave(O>thelogicalname undefined.NOForfurther informationonthesettingsoftheseflags,seeOSection9inthe$ VMSMailUtilityManual 4.?>@ n9O 5.2 Installing!and" Configuring"NJE!SoftwareKOThischapterprovides suggestionsfortheBITNET transport0Olayerofyournetwork,whichusesBNetworkJobEntryOB(NJE)9IB protocols.2Thisbook provides supplementaryGO informationonrunningJnetintheBITNET environment,LOandisnotintendedtoreplaceJnetdocumentation.+IfyouKOLare unfamiliarwithJnet,readChapter1, Introductionto.ONetworkJobEntry(NJE),inthe  Jnet Manager'sGuide!.'ForMO additional background,seethe referencesinthePrefaceofOUthatbook.X@?A>%O5.1BPlanBITNETtopologyQOUInthissectionyouwillplanthetopologyofcomputersystem,O participatinginBITNET,callednodes,andthelogical+O connectionsamongthem,calledlinks .|A@BV]@O5.1.1B Selectingsystemsto participateinBITNETNO4ThefirstdecisioninplanningtheBITNETtopologyforyourKO organizationisto determinewhichsystemswillbeBITNETNOnodes.)SystemsthatrunNJEsoftwareandarelistedinthe6O=BITNETroutingtablesareBITNETnodes.! IOThereisnoseparatechargetoCRENmembersforaddingAOnodestoBITNET,andBITNETcommunicationswithinJO5an organizationareoftenoverexistingDECnetorTCP/IPMO networks,sothemaincostofadding additionalsystemstoEOBITNETmaybeJnetsoftware licenses.-In determiningNO>whethertoputaspecificsystemonBITNET,an organizationCOmustbalancethecostswiththeexpected benefits.awLOThebenefitsofBITNET,oranyothernetwork,arenetworkLOservicesreceivedbyusers., ElectronicmailisperhapstheFO5mostvaluableserviceBITNEToffers,butwhenmailersIOareused,mailcanbecarriedoverDECnet,TCP/IP,andFONJEnetworks transparentlytousers,soaddingdirectIO>BITNET connectivitydoesnotnormallyincrease electronicHOmailservicestoasystemrunningPMDFandalreadyonGOaDECnetnetworkorthe Internet..Theaddedvalueof2OHBITNETcomesfromnon-mail services.sIIOInadditionto electronicmail,BITNETservicesinclude:! 5 `m:mSender-initiated, password-freefiletransfer `. Interactivecommandsandmessages `llRemoteprinting `'Remotebatchjob execution `kKk Applicationsbuiltonthegenericservicesabove,suchasHgroup communicationand automaticfile distributionwithLISTSERV  NNO Additional informationabouttheseservicesis availablefromQOCRENandJoiner,andsomeoftheseservicesareusedinthisDO5bookfortheon-going managementofJnetandPMDF. FOAvoidputting single-usersystemsonBITNET.UsersofJO workstationsandpersonal computerscangetdirectaccessMO5toBITNETservicesbyusingterminal emulationtologintoJOa timesharingsystemorserverwiththeDECnetSETHOST>Ocommand,LATConnectcommand,orTCP/IPTELNETKO> application.(Bynotputting single-usersystemsonBITNET,GOyouwillconserveBITNET'slimitedaddressspace,saveNO resourcesoneveryBITNETnodebyreducingthesizeoftheNOHBITNETroutingtables,andfree resourcesonthe single-userHOsystemthatwouldbeconsumedbyrunningNJE software.qGGOThereareseveralcommon exceptionstothis guideline:! S `mCm VAXstationsusedasnetwork managementconsolescanJbenefitfromrunningNJEsoftwaresoastomoreclosely6monitorBITNETtrafficandlinkstatus. `A VAXstationsusedasBITNET wide-arearoutersmustJrunNJE software.'This arrangementisusedintheTexas.OHigher EducationNetwork,THEnet. `: VAXstationsthat aremembers of homogeneousG' VAXclusterscanbe configuredtorunJnetwithlittleB management overhead, atlittleornolicensecostF(becauseofJoiner's ClusterWidelicense pricing),andB0without increasingthesizeoftheBITNETroutingCtables.*(RunningJneton VAXclustermemberswithoutC registeringtheNJEnamesofthosesystemsintheL:BITNETtablesisbeyondthescopeofthisbook, however.)NIOIngeneral,putonly timesharingsystemsandserversonJOBITNET,andtrainusersinBITNET applicationstogetanumberofBITNETusersgrowstoacriticalmassonanotherLO timesharingsystem,thoseuserscancanbeaskedtoraiseIOthemoneyfor additionalJnet licenses.-The disadvantageQOHofthisapproachisthatusersmayneverseethebenefitsofJOnon-mailBITNET services,andsothe potentialofBITNETQOinthe organizationmayneverbe realized.(ThisisthereasonNORthatpublicand university librariesarenotfundedbyuserOfees.yGOEvenif significantBITNETusebuilds, usersofguestLOaccountsontheinitialBITNETnodemustnotifyalltheirDO5correspondents, includingserver applicationssuchasFO LISTSERV,thattheyhavemovedtoanewaddress.-AsO explainedinSection3.2,.thisisalong,manualprocess.*|?sO%FOIf,!foranyreason,!notallmembersof an otherwiseBO homogeneous VAXcluster participateinBITNET,usersIO5musttakecarewhentheylogintouseaBITNETnodeIOiftheyintendtoaccessnon-mailBITNET services.,ThisCO configurationisnot recommended,becausetheusualJO> motivationforsettingupa homogeneous VAXclusteristoMOprovidehigh availabilitywhile relievingusersfromconcern1Oaboutwhichmembertheyareusing.NOThisbookassumesthatyouwillrunJnetonallthenodesQOofa homogeneous VAXcluster.)Ifthisisnotthecase,installLO5Jnetasfora standaloneVAXsystem,installPMDFasforMOa VAXcluster,andtrainyouruserstoonlyattempttouseGOnon-mailBITNETservicesfromthe system(s)onBITNET.LD s UOFigure5-1:7BITNETtopologyexample."Largefilledcircles representB PrincipalNodes.%Opencircles represent pseudonodes(`bearingJnetclusternames.KOKKKkx?0` 00 p0`p@ ` @@@@@       /80  @1@1@a a  @   @@@8@@   `    ?   0 !#1`""F@ "$ $  "$? "$ $  "P$ $ "P"F@@`0"  #1``0"  1 < ?@`0`|oaC<D!"3B#!H!  !H! !H! !H! !"D!B#!C!<0@ @> `@B @B@B@"@~$ @$@D@D@„@~0@  `@%Wt&31!@ $!@@ $! @ $!@ $!@@&!„!@%!0@   `  AP  AP #!A $!b"  !$ "! !' ! @ !$@ $$3"  #.! 0@ `<|$`$  $>$`Ӈ@$a0@`$ A! @@@$B0A@@ $$@"@ $'"@ $ "$   ! B@$B a0`$ `@|$@ >@@a@   !@?_?( @@@@@ 0?_?$"`!@@ @2HB >2HB @RH$ @RH$  H %B9  H$ "` I$@IBP"JBQ "(J !$BHL @` > `<` @ A@ B@B@Ӈ@!ͣ/ @a0@"1c$" p@! @$!$BA@@$ ! BB@$D?  B@$D# B@$($@HB! @$(!$@H 2Aa0a$0!&@"0@ Js@$#"H@ D !H?!A D!A@D !ABH!A0! 0"   C>"g(d"&Ȁ$"$H $"$H "$H  "P$H  "P&Ȁ$0"  '&" $H>@@ @ @ H(    @H @HHx(@"0IH""HHH  HH AH!AH"  L" !xO>4 apb`!`"B@A@D""A@""@D"!"@D" !`"@@ ap!@`O>x @`0` |  @   @A -@xx @F `!@ 8@D a@@@@@H !@@    @H !@@  A@8@@H !@@  `!@@H !@" @D a@@B@ a0`@9@ ^/!@|x@   @ 8 @ @@ `  '8 D $ ( ? ?( ?$ ?D ? ? ?8B'"   ?x    @@@ @@@0`@@  1`@A QPA QPBPP?8D@H@ H E0 E BB @`0t^9xsF3g`!$DB!$DB!$DB!$DB!DDB!DBx BACj V@!O5.1.2B PrincipalNodesJO4ToconnectyourVAXor VAXclustersystemtotheBITNET,DOyouhavearrangedtomakeaBITNET connectionwithNOanother organizationandhaveagreedona transportprotocolCO=with technicalrepresentativesofthat organization. KOIfthesystemwhichyouare connectingorhave connectedEOtoBITNEThasa connectiontoanotherBITNETmemberPO5or affiliate,orisontheBITNETroutebetweentwoofyourHOorganization'ssystemswithsuch connections,thesystemOisa PrincipalNode1candmustmeetthe requirementsforEO> PrincipalNodesintheCRENTermsand ConditionsofKO Membershipand Affiliation.(ThefirstsystemonBITNETatSOamemberor affiliateisalwaysa PrincipalNode.(SeethefileOHCRENTERMS , 1-H, availablefromLISTSERV@BITNIC , 2H,forOmore information.*/1*"/>! WLO Designateeitheralarge, productionsystemora dedicatedNOroutingsystemas PrincipalNodeforyour organization.&YourLO5 PrincipalNodemustmeetthe requirementsfor availability,KOandyourlinkstootherCRENmembersand affiliatesmustMOmeetthe requirementsforBITNET bandwidth,thatarelistedO>inCRENTERMS._ k5EOIdeally,!your Principal Node should be availableforJO forwardingBITNETtrafficallthetime,andhavearound-HO5 the-clock supervisionby operatorswhocandiagnoseandKOrepairanyproblemswithBITNET connections.)Ifyoucan'tGOmeetthisrecommendation,andiftheTECHREPorotherCO>CRENrepresentativeoftheadjacentCRENmemberorKO affiliateistrustedand experienced,considergivingthatKO individuala privilegedguestaccount,enabledfordial-inLOHaccess,onyour PrincipalNode.*That individualcanbeanFO additionalresourcein resolvinganyBITNET forwardingNOproblemsthatappearwhenyour organizationisnotopenforOR business.CBE0O5.1.3BPlanningexternal connectionsNO4Ifyouhavenotyet determinedwhereyouwillconnectyourKO organizationtoBITNET,theconsiderationsinthissectionOmayhelp.O! %QOArrangetoconnectyour PrincipalNodeasclosetothecenterKOofBITNETas possible.)WiththeregionalizationofBITNET?O5overaTCP/IP backbone,theregionalBITNETIIe5core 05ofMOhubsitesarethe ``center''ofBITNET.EachofthesehubNOsites,twoperregion,are connectedtoeveryotherhubbyJO>BITNETlinksover high-speed(1.5 Mbits/secondorfaster)KOlinesoperatedbyNSFnetandregional affiliated mid-levelEOTCP/IP networks.,AsummaryoftheBITNETIIprojectIOHmaybefoundinthefileBITNET-2INFO, availablefromCOLISTSERV@BITNIC.Thatfile references additionalon-POlinefilesthatprovidefurther informationon protocols,coreMOR topology,andothertopics.* PersonalizedadviceonwheretoGOconnecttoBITNETcanbeobtainedby telephoneBITNICKOandaskingtospeaktoamemberofthe technicalstaff.X .GO Minimizingthenumberof forwardingnodesbetweenyourNO PrincipalNodeandthenearestBITNETIIcoresitehastwoQO5 advantages.(First,transittimeforNJEtrafficis proportionalOOtothenumberoflinksinthepathtothe destination,andFO minimizingthenumberoflinkstothecore minimizesJO>theaveragenumberoflinkstrafficfromyournodemustOO traverse,andsoimprovesthespeedofdeliveryoffilestoROandfromyournode.(Second,eachlinkisa potentialpointofJOHfailure,and minimizingthenumberoflinksbetweenyourLOsystemsandthecoremeansimprovedBITNET reliabilityfor2Oyourusersandtheircorrespondents. fIOIf possible,putalllinkstootherBITNETmembersandMO affiliatesonthe PrincipalNode.* Otherwise,anyothernodeJO5youuseforexternal connections,andanynodesinyourNO organizationthatcarrytrafficbetweenthem,mustalsomeet8Oallthe requirementsfor PrincipalNodes.#! OFigure5-1; illustratestheseplanningconsiderationsforKOexternallinks.,State Universityhasthreeexternallinks,OO5toaBITNETIIcorenodeandtwolocal colleges.*AllthreeROexternallinksaretotheState University's PrincipalNode,soHOthe resourcesofothercampussystemsarenotconsumedJO>inroutingtrafficbetweenthecollegesandtherestofOOBITNET.ItwouldbenefitthecollegestoconnectdirectlytoOOtheBITNETIIcorenode themselves,butinthis hypotheticalLOHexample,theycannotmakedirect connectionstotheBITNETAOIIcorebecauseofthecostof wide-arealinks.*OFO AOWhenplanningNJE linksover underlying networks,JO includingTCP/IP,DECnet,SNA,andOSI networks,considerJO<the structureofthe underlyingnetworkwhendecidingonKONJE topology.*Ingeneral,make connectionstoothernodesOthatare logically<close,wherelogicaldistanceismeasuredbyMOEthenumberofroutersandthespeedandcostof bandwidthMObetweenrouters.)Forexample,whenlookingfora ``nearby''OOBITNETIIcorenodeonthe Internet,followthetopologyofLOOyourfastestInternetlinksuntilyoureachtheBITNETIIOcore.' ECFI! j3O5.1.4BPlanningintraorganizationlinksMO4The principleof minimizingthenumberof forwardinglinks, Oorhops?v,betweennodesalsoapplieswhenplanningNJETOtopologywithinyour organization.'Ingeneral,itisbesttouseOO=astar topology,withyour Principalnodeasthehub.)ThereMOaretwomain exceptionstothisruleofthumb:+youshouldVO establishasecondhubontheothersideofaslowor unreliableMOGlink,andeachJnetclustersystemshouldbe configuredasKOasinglenode externallyandafullmesh internally.-SeeOSection5.1.5:$for suggestionsontheNJEtopologywithinOQ VAXclusters.*O?  OFigure5-1?also illustratestheplanningconsiderationsforHOinternallinks.-State Universityhastwo VAXclusters,aBO5 stand-aloneVAXsystem,andanIBM mainframe.-ForEOoptimal performance,eachshouldbe connectedtothePO PrincipleNode directly,butthatwouldbetoocostlybecauseKO>the mainframeandone VAXclusterareatasecondcampus,HO connectedtothemaincampusbyaslowlink.,TheIBMFO mainframeservesasa secondaryhubforthesuburbanFOHcampus,andanyfutureBITNETsystemsonthatcampus5Oshouldbe connectedtothat mainframe.*OFO ! UMOAswithexternal connections,considerthe structureofanyJO underlyingnetworkwhenplanningNJEtopologywithinyourJO5 organization.+AtState University,ifthetwo VAXclustersHOwere connectedbyaDECnetnetwork, VAXclusterBwouldOOhaveprobablybeenabetterchoiceasthehubnodefortheJO>SuburbanCampus.(ButsincethereisnoDECnet connectionHObetweenthe campuses,theIBM mainframewaschoosenasKOthehubbecauseithasgreater synchronousport capacity.iFEG  (O5.1.5B VAXcluster connectionsJO4Ina VAXclustersystem,youshouldlicenseandrunJnetHOsoftwareonall timesharingnodes, establishlinksover5ODECnetbetweeneverypairofnodes(afullmesh} topology),IO=andregisterallNJEnodesandaJnetclusternameinLOBITEARNnodes.(YouwillregistertheJnetclusternameinLOBITEARNNODESasanodethatis connectedtoeveryother,OGnodeintheJnetcluster.(ThevG pseudonodeGbearingtheJnetexternal connectionsisanothercommonconfiguration.&TheseMOadvancedconfigurationsareoutsidethescopeofthisbook,Ohowever.GFH2  ` O5.1.6BLink protocolsFO4JnetsupportslinkstoothersystemsusingmanylinkJO protocols,andthe protocolsusedon differentlinksareGO independent.1SelectaprotocolforeachlinkbasedonPO= compatibilitywithNJEsoftwareonthenodeattheotherendOofthelink(the|peernode/)and requirementsfor underlyingHO networks, specialized hardware,communicationslines,andOGJnet licenses.  a?ORunningNJEoverDECnetorTCP/IPnetworksand!Olocalareanetwork( +LAN,)hardwareprovidethehighestMO5 available performance,andshouldbeusedwhenever possible.GOOverwidearealinks,communicationslinecostsbecomeFOan overridingfactor,andsharingexisting connectionsFO>byrunningNJEoverexistingTCP/IP,DECnet,orlessGOcommonlySNAorOSInetworksis recommended.(Fornew,IO BITNET-only connections,linksoverBSClinesoftenhaveDOHthelowestinitialcostfor equipmentand software.+3OIngeneral,uselinksoverDECnet(LDNANJElinks)withinKOJnetclustersandinallothercaseswherean underlyingFO5DECnetnetworkis available.-ChooselinksoverTCP/IP O(jTCPNJE4links)whenmaking connectionsbetweenDOVAX/VMSandUNIXorIBMVMsystemsoveracampus-LO>widenetworkorwhen connectingtotherestofBITNETif2OanInternet connectionis available. FOIfyour organizationis currently connectedtoBITNETNObya dedicatedBSClineandtotheInternetbyaseparateMO5 connection,an attractiveoptionistoswitchyourexternalLO connectionfromtheBSClinktoaTCPNJElinkovertheQOInternetand terminatetheleaseonthe dedicatedBSClinetoLO>savemoney.'Thischangeshouldbe undertakenwithcaution,KO particularlyiffundingforyourInternet connectioncomesNOfromanotherentity.( TechnicalproblemscanalsocropupinPOHthefirstfewmonthsofusinganew connectionthatmakesa(OBSCbackuproute desirable.6!  HOWhenplanninglinks,workwiththe PostmasterorotherPO technicalstaffforthepeernodetoagreeontheNJEnamesTO5yoursystemswilluse,thelink protocols,andanylinkprotocol O parameters.' Examples:m! C `mLmIfmultistreamingis availableonbothsystems,youshouldFuseittoimprovetotal throughputand throughputofLsmallfiles,butyoumustagreeonhowmanystreamswillwbeused. `JThereareseveralBSClink protocols,andtheremustbe4O agreementonwhichonewillbeused. `KIfyouwilluseTCPNJE,youmustexchangeIP addresses?'ordomainnamesandTCPportnumberswiththe)managerofthepeersystem.&baudovertheline.( Unconditionedlinesareusually sufficientFOwithin metropolitanareas,butD1 conditioningmaybeNOrequiredforwidearealinks.) Full-duplexcircuitshavefour>OHwires,twoforsendingandtwofor receiving.! aDOV.29modemsare relatively expensiveandusematureHO technology.-Asecond alternativeisa DataphoneDigitalGO5Service(DDS) connection.,Insteadofmodems,DDSlinesJOuseless expensivedevicescalleddataserviceunitsandPOchannelserviceunits,mostoftencombinedintodevicescalledJO>DSU/CSUs.'Wheneverorderingleasedlines, determinebothQOinitialandmonthlycostsofbothanalogandDDSservicesandMO equipmentbeforemakinga decision,becauseeithertypecanMOHbemorecost-effective, dependingonthespecific situation.C QOForlinkswithinalocalcallingarea,athird alternativeisOV.32orV.32  bis3dial-upmodems.+Suchmodemsusetwo-JO5wiredial-upcircuitsandtheswitched telephonenetwork.KO Dedicatingaswitchedbusiness telephonelinetoaBITNETQOlinkmaybemuchless expensivethanaleasedline,andV.32KO>modemsaresoldinvolumetopersonalcomputerusers,so?Otheyaremuchless expensivethanV.29modems.! HOWhileJnetBSC/370hasnosoftwaresupportfordialingBOthesemodems,manymodemmodelscanbe configuredIO5to automaticallydialastorednumberwhenJnetsignalsBOthemodemthatitisreadyto communicate.0ModemNO configurationisusually accomplishedby attachingaterminalIO>tothemodemportandsending configurationcommandsto-Othemodemas asynchronousdata.! COWhen purchasinganytypeofmodemforBITNETuse,KObecertainthatafull complementof diagnostic features,IO5 including indicatorsandtesting functions,are provided.HOTestingand diagnosticfeaturesareveryusefulintheDOBITNET environment,buttheyareoftenomittedfromOO>modemsdesignedtobesoldintoprice-sensitivemarkets,such,Oastopersonalcomputerusers.E! IOTherearemany different synchronous interfaces availableAOfor the!members of the VAX family of computers.O5Consult the)5 Jnet System Support Addendum5for aFOcurrentlistof supported interfaces,andtheDigital  VAXwhich interfacesare supportedonyourVAXsystems.,IfKOrequiredforthe interfaceandVMSversionyouwilluse,FOobtainandinstall Digital'sWideAreaNetworkDevice2OHDrivers software.&Thenrefertothe"\H JnetBSC/370 Manager'sO GuideD4for informationon configuring synchronous interfaces&OforusebyJnetBSC/370.IHJF0O5.3BInstallJnetandlinkdriversMOUJnet installationisastraight-forwardprocessof unpackingPOfilesfromthe distributionsavesetsintotheJnet directoryOOtree.'YourprimarydecisioniswheretoputtheJnetfiles.! {pROToalloweasymovementofJnetfilesfromonedisktoanotherMOasyour configurationchanges,considerdefiningthelogical7O5namesMY_JNET_PERM_DEVICEand MY_JNET_TMP_?ODEVICEinSYS$MANAGER:SYLOGICALS.COM,asinthisOexample: Ok...GO$&!%Put&Jnet% permanent&files&on&DUA0:&and% transitory!O$&!%files%on%DUA4:.=OB$&-DEFINE/SYSTEM/EXEC/TRANS=(TERMINAL,CONCEALED)%-'zMY_JNET_PERM_DEVICE%$1$DUA0:=O$&-DEFINE/SYSTEM/EXEC/TRANS=(TERMINAL,CONCEALED)%-&zMY_JNET_TMP_DEVICE%$1$DUA4: Ob...FOThencreateaJnetstartup procedure,calledMY_JNET_KO STARTUP.COM,thatusesthenewlogicalnames,asinthisO5example:+O$&DEFINE/SYS/EXEC% JAN_DEVICE&-*z MY_JNET_PERM_DEVICE:[JNET_PERM.]+OI$&DEFINE/SYS/EXEC% JAN_TMPDEVICE(zMY_JNET_TMP_DEVICE:[JNET_TMP.]5O$&#@JAN_DEVICE:[JANCOMMON.SYS]JANSTART&'P1! `POIntheexampleabove,a different top-level directoryisusedQOforthe permanentand temporaryfiles,allowingyoutosetupUO5thisflexiblefile arrangementevenifallJnetfileswillbeonOOthesamediskdevice initially.(This directory arrangementis:O recommendedforallnewJnetinstallations. h_UkNote h_/Intheselogicalandfilenames, BMY_(oranotherstringGHofyour preference)shouldbeusedtoavoid conflictsFwithlogicalnamesusedbytheJnetsoftwareitself,#noworinthefuture. DW l-JOIfyoukeeptheJnetstartup procedureinthe directory?OSYS$COMMON:[SYS$STARTUP],youcanusetheSYSMANQO5utilitytostartJnetateachsystemreboot.'TodirectSYSMANNOtoexecutetheJnetstartup procedureinbatchmodeintheJOmainlayeredproductphaseoftheVMSstartup procedure,O>enter: O$SYSMAN%:==%$SYSMAN O $B SYSMAN%ADD%FILE%MY_JNET_STARTUP.COM& /PHASE=LPMAIN%- OS_$)S /MODE=BATCH%/PARAMETER=P1:COLD!  NOIf,atsomelatertime,youneedtomoveoneoftheJnetIO directorytreestoa differentdiskdevice, merelyshutJO5downJnetcold(as explainedinSection16.1.1.4ofthe O Jnet Manager'sGuide6g,editthelogicalname definitionsin>OSYS$MANAGER:SYLOGICALS.COM,manuallyredefinetheNO>twodevicelogicalnames,movethe directorytreeswiththe4OVMSBACKUPutility,andrestartJnet.N!$JOBefore beginningthe installation, determinewhetherthereJOisa POSTMASTERentryintheSYSUAF.YoumusttelltheKO5Jnet installation procedurewhethertheuserentryalreadyEOexistssothe procedurecancreateitif necessary.'" KOThe POSTMASTERentrycreatedbytheJnet installationhasKOsystem privileges.,Handlingfilesforotheror nonexistentLO5usersisa privileged function,soifyoualreadyhaveaDO POSTMASTERentryintheSYSUAFforanotherpurpose,LObutitdoesnothavesystem privileges,youwillhavetoIO> reconcileyouruseofthe POSTMASTERentrywithJnet's.HOIfyouwanttheJnet installation proceduretomakeaEOnew POSTMASTERentry,deletetheexistingentry,anyJOH POSTMASTERentryinthesystemrightslist database,andPOthelogin directoryandanyotherfiles belongingtotheoldO POSTMASTERuser.#aEOWhenyouhavepreparedthedevicelogicalnamesandBO determinedwhetheryouhavea POSTMASTERentryinFO5theSYSUAF,installJnetwith VMSINSTAL accordingtheO directionsinthe# Jnet InstallationGuide..IfyouwillbeMO configuringaJnetcluster,performthe installationonanyKO>fastorlightlyloadedVAXsystemthatwillbeamemberLOofthecluster.* Normally,youshouldchooseyour PrincipalLONode,orthesystemthatwillhavetheexternallinksto/OHsystemsoutsidetheJnetcluster.$! KOUnlessyouarerunningaVMSversionbeforeV5.0,answerOthatyoudo  notAwanttoinstalltheinstallthewholekit.'Then'O5installallthekitparts5 except-e5VMS``V4compatibility''.'(There7Oarecertain situations, explainedinthe Jnet InstallationO GuideH,inwhichyouwillskip installingotherkitparts.)l%BPOIfyouwillbe configuringaJnetcluster, reinstallJnetonNOeveryothersystemthatwillbeanodeinthecluster.,OnQO5thesecondand subsequentnodes,donotinstallthewholekitOagain,butinstall only'athe``node-specificroot''.)& OOWhenyouhave installedJnet'sstandard features,installanyMOoptionallinkdriverslicensedandrequiredforsystem.*YouQO5caninstalltheseonanysystemthatwillbepartofaJnetOcluster.'NKOWhenyouhave installedalltherequiredJnet components,JOcontinuewiththe configurationofJnet,as describedinO5Section5.4.*'O|?(JIKe(;O5.4B ConfigureJnetLOUJnet configurationistheprocessofcreatingor modifyingLOJnetstartupfilesto automaticallysetuptheproperNJEHOserversandlinksforyour organizationeachtimeJnet/O^isstarted./Chapters5-14ofthe ^ Jnet Manager'sGuideLOprovide instructionsfor configuringJnetthatwillnotbeHOrepeatedhere..The followingsectionsprovide additionalDOhrecommendationsforJnet configurationintheBITNETO environment.KLKM 8-O5.4.2BManual configurationtasks!O4Chapters7-14ofthe l4 Jnet Manager'sGuide4dealwith=O configurationtasksonacomponent-by-componentJObasis.,That organizationismostusefulwhen modifyingaJO= componentinyourJnetconfiguration,butcanbeawkwardNOfornewJnetsite,becauseitrequiresanumberofediting?Osessionsoneachofseveralcommand procedures.%9! EOAsan alternative, newsitesshouldconsiderworking(OthroughSection7.2ofthe  Jnet Manager'sGuide$,makingJO5allthechangesrequireineachfile(forexample,JAN_IOSYS:LOGIN.COM)beforegoingontothenextfile.*Youcan"OuseTable7-1ofthe ? Jnet Manager'sGuide nasachecklistofOO>possiblecustomizationsandcross-referenceto instructionsforOeachchange.:NDOSpecificrecommendationsforpostconfigurationfollow.EOTheserecommendations supplement,butdonotreplace,$O5the instructionsinthe |5 Jnet Manager'sGuide 5.MLN;B}2O5.4.2.1CEditJAN_COMMON:[SYS]LOGIN.COMKO)Changetheword ``network''to ``BITNET''inthemessage._NMOE<U0O5.4.2.2CTestSYS$MANAGER:SYLOGIN.COMAO)AftereditingtheJnetlogincommand procedure(a) JnetO Manager'sGuide@,Section7.3.1)andthisfile(Section7.3.2),MOtestthefiles carefullyfromanon-privilegedaccount.,AllKO3usersexecutethesecommand proceduresatlogintime,andNO incorrect protections,editingerrors,andsooncanpreventNOloginsbynon-privilegedusers.(Remembertotestbatchjobs,O<too.-Q@ 7FOTable5-1:7TCP/IPProducts supportedbyJnetTCPNJE O OFLinename&FTCP/IPVendorandProduct Ob  O CMU7 CarnegieMellon UniversityCMU-TEKIP/TCP O$ UCX)$ Digital VMS/ULTRIX ConnectionO FUSION+ NetworkResearchFUSIONTCP/IPO MNETV20 TGVMultiNetV2.0O MULTINET) TGVMultiNetV2.1andlater O  WIN   TWGWIN/TCPforVMS O1 CONP= 4O5.4.2.3CUseSYSMANSTARTUPinsteadof&gSYS$MANAGER:SYSTARTUP_V5.COM4OvIfyoufollowedtherecommendationinvSection5.3jvtocreateaJO site-specificJnetstartupfileinSYS$COMMON:[SYS$STARTUP]IO'andenterthefileintheSYSMANSTARTUP database,you?OdonothavetoeditSYS$MANAGER:SYSTARTUP_V5.COM O( j Jnet Manager'sGuide},Section7.3.3).*=9|? POR>! HO5.4.2.4CEditJAN_SYS:JANLINKS.JCPandJAN_SYS:JANSTART.JCPIO) Normally,thesefilesarecreatedbytheJnet automaticAO configurationcommand procedure,JANCONFIG.COM.ForFOmostconfigurations,therewillbeoneCREATEcommand@O3andseveral DEFINE/LINKcommandsin JANLINKS.JCP,>OandaSTARTcommandin JANSTART.JCPforevery;O DEFINE/LINKcommandin JANLINKS.JCP.YoucanKO<manuallyeditthesefilestochangelinkswithoutrunningKO JANCONFIG,however,andmanualeditingisrequiredtouseFOcertainfeaturesthatarenot supportedby JANCONFIG.? OTheline9nameforaTCPNJElink determineswhichKOTCP/IPproductJnetwillattempttousetomaketheTCPHO5NJE connection.*IfyouchangefromoneTCP/IPsoftwareJOproducttoanother,edit JANLINKS.JCPtochangethelineHOname,orexecute JANCONFIG.COMtocreateanewsetofPO>startupfiles.)ThelinenameisnormallytheonlyJnetsetupEO parameterthatmustbechangedwhen switchingTCP/IP"Osoftware products.(SeeTable5-1' forthelinenamekeywordJOH associatedwitheachTCP/IPsoftwareproduct supportedbyOJnetTCPNJEV1.1.*?a?@A ^OOBusyBITNETlinksshouldusefilequeuingbysize, explainedOinthe : Jnet Manager'sGuide2O,Section3.5.)SetupfilequeuingHO<bysizewhenyoudefinelinksbyediting JANLINKS.JCP.JOBITNETlinkscanbenefitfromusingsixsize categories,FOthemaximumnumber, distributedso approximatelyequalCOEnumbersoffilesare transmittedineach category.bB8OO Initially, establishatleastthree categories., CategoriesforROfilesupto100records,100to1000records,andlargerthanJO51000recordsare suggested.+Later,youcantunecategoryMO boundariesusingthesizedataJnetcollectsinlogfiles.PC &OIfyou implementmultistreaming$i,whichisalsorecom-NOmendedforbusylinks,youmustalso implementfilequeuingUO5bysizeanduseoneofthesizecategory boundariesasthesize+O thresholdfor``largefiles''.SRTXE! L.3O5.4.2.6C ConsolidateJAN_SYS:JANLOAD.COMBO) JANLOAD.COMisalsocreatedby JANCONFIG,anditsSOcontentsdependonthetypesoflinksinyourconfiguration.'ItQOisnormallyusedforsetup synchronous interfacesforusebyO3BSClinks.FEOIfyour configurationresultsinaJANLOAD procedureEO containingonlythe definitionoftheSYSGENsymbol,DO5youcanreplaceitbyanew,emptyJANLOADproce-HOdure.2IfmorethanonesysteminaJnetclusteruses?Othe same JANLOAD procedure,"you can reduce theEO>numberofstartup files bymovingonecopy toJAN_BO COMMON:[SYS]anddeletingthe remainingcopies..DoLOnotdeleteallthecopiesoftheemptyJANLOAD procedure,=OHorJAN_COMMON:[SYS]JANSTART.COM,themainsite-NO independentJnetstartupfile,willproduceanerrormessage3Owhenitattemptstorun JANLOAD.COM.T SUEGi:O5.4.2.7CEdit!JAN_COMMON:[SYS]JANSITECOMMON.COM?O)ForallBITNETnodes,editJANSITECOMMON.COMtoBOassignthevalue34toJAN_SYSTEM_FLAGS.ThishasNOtwoeffects..Settingbit5(adding32tothevalue)causesNO3Jnettolimit responsestonetworkcommandsto50linesofLOoutput,in compliancewithanEARNtraffic requirement.(IfROthisbitisnotset,Jnetcansend thousandsofhighpriorityAO<nodalmessagerecordsinresponsetothecommand<QUERYOSYSTEMROUTESA*,blockingfiletrafficontheaffectedlinks( JnetO Manager'sGuide;Section7.5.9).-Settingbit1(adding2toOOFthevalue)causesJnetto broadcastfilearrivalmessagesto,Oallmembersofa VAXcluster(  Jnet Manager'sGuideSectionIO8.2.4)..Thissettingdoesnoharmon standalonesystems%OP (single-node VAXclusters).iH k?HO BeginningwithVMSV5.5,the batch/print subsystemdoesPOnotrequirequeuestobe initializedeachtimethesystemisJO5 rebooted.,ForsystemsrunningJnetonVMSV5.5orlater@OanddefiningNJE symbionts, including JNET_JOBLOGKO(forbatch servers), initializequeuesmanuallyonlyonce,BO>usingcommandslikethoseprovidedascomments in=OJANSITECOMMON.COM.LeavethecommandsyouusedFOto initializethequeuesascommentsin JANSITECOMMONJOHtodocumentyourqueuesetup.+ToavoiderrorscausedbyDOrunningNJE symbiontswhenJnetisnotstarted,do  notOOdefinequeuesforNJE symbiontsas autostartqueueswiththe#OR /AUTOSTART_ON qualifier.INAORemovethecomment character(!)/fromtheSUBMITKOcommandtosubmittheJANTIDYjobtoabatchqueueeach"O5timeJnetisstarted.JNIOThe remainingrecommendationsinthissectionapplyonlyVOtoJnet clusters.(IfyouarenotsettingupaJnetcluster,skipO5aheadto5Section5.4.2.8.*J?RBK! GOJnet versionsbeforeV3.5didnotsupportmessages toGOtheJnetclustername,causingendless confusionaboutHO5NJEnodenames, especially regardingtheuseofremoteIOserverssuchas LISTSERV.Itwasso difficultforJnetEOclusteruserstomaintainLISTSERV subscriptionsthatJO>itisafrequentrecommendationtoneveruse interactiveHOcommandsto communicatewith LISTSERV,butinsteadsend"Oallcommandsbymail.]L! 3HO BeginningwithJnetV3.5, this precautionisnolongerMO necessary,becauseJnetclusterscanbesetuptousetheJO5Jnetclusternameforallinboundandoutbound messages,KOfiles,and electronicmail.(Formore information,seethe; Jnet-O Release Information,Version3.5+,Sections1.10and1.11.*If:O>youare configuringaJnetcluster,itis> strongly> recommendedBOthatyoutake advantageof cluster-wide messaging.MROIfyouhaveaJnetclusterbutarenotyetrunningJnetV3.5Oorlater,itis* strongly-b recommendedthatyouupgradetoOO5thelatestversionofJnettotake advantageof cluster-wideNO messaging.) Implementitby followingthe instructionsinthe O Jnet Manager'sGuide7g,Section8.2.2(fornewnodes)orthe3O> JnetRelease Information,Version3.5">,Section2.16.1(forKO upgradingnodes).*ThemasternodeforshouldbethenodeKOwithall(oratleastmost)oftheexternal connections.N aMOIfyouareformingaJnetclusterbyaddingasystemstoIOa stand-aloneJnetnode(forexample,changingfromtheAO5singlenodeACMEtotwonodes,ACME1andACME2,JOwithJnetclusternameACME),nomailaddressorserverOO subscriptionswillbeaffectedbythechange.+IfyouformaLO>Jnetclusterfromnodes previously operatingontheBITNETLOwithseparatenames(forexample,formingtheJnetclusterCOACMEoutofnodesACME1andACME2),somecareis6OHrequiredtochangeserversubscriptions.O HOTochangeaLISTSERV subscriptionfromaspecificnodeROnametoaJnetclustername,theusermustsignoffthelistRO5usingthespecificnodenameand resubscribetothelistusing-OtheJnetclustername.,Seethe% JnetRelease Information,O Version3.5.,Section1.11,foranexample.vPLKOItispossiblefortheTECHREPornodeADMINcontacttoHOchangeLISTSERV subscriptionsonbehalfofotherusers,PO5anditmaybepossibletouseLISTSERVjobstoobtainlistsSOof subscriberstoalllistsonaspecificnodeandchangethemNOtotheJnetclusternameinbulk,butthese techniquesareNO>beyondthescopeofthisbook.)Seetheonline documentationKO availablefromLISTSERVfor additional informationonList/OOwnercommandsandLISTSERVjobs.Q aROJnet'suseofthespecificnodenameortheJnetclusternameOOastheoriginoffiles,mail,andmessagesis controlledbyJO5logicalnames..BeforeV3.5,JnetusedaseparatelogicalEOnameforevery imagethat called theJnet shareableHOimage.. BeginningwithV3.5,theselogicalnamesareno?O>longer required.*Followthe instructionsinthe> JnetRelease$O Information,Version3.5$,Section2.17,orthe Jnet Manager'sO GuideN,Section8.2.3,to configureJnettousetheJnetcluster7OHnameforallfiles, messages,andmail.VUWfS! U<AO5.4.2.9CEditandenableJAN_COMMON:[SYS]JANTIDY.COMCO)Theuseof JANTIDY.COM,Jnet'snightlycleanupandKO monitoring procedure,is recommendedforallBITNETnodes.1OEditJANTIDYtodefinethesymbols  JANSYSTEM, JANMANAGER , O3and3 BATCHQUEUEh3.Setting3 JANMANAGER<3to POSTMASTERisAO recommended,tofunnelallBITNET managementmailIOthroughasingleaccountforeaseof forwardingtothe"O< responsible individual.{T QKOYoumaywishtodevelopa specializedversionofJANTIDYNO(witha differentname)torun frequently,asoftenassixNO5timesanhour,onbusyBITNETnodes.'SuchajobcancheckUOthatalllinksareup,queuesarenottoolong,andsoon,andEOsendmailto POSTMASTERoraREQUESTtothesystemJO>operatorifit discoversany problems..ThisisacommonDOpracticeonIBM mainframesonBITNET,wheresucha Oprogramiscalledalinemonitor . WVXU0O5.4.2.10BEditlink parameterfilesJO)Createlink parameterfilesinJAN_SYS:tospecifychar-IO acteristicsofspecificlinks.*RecommendationsforBITNETOnodesfollow:V  `mJmIfyouwillusebatchorprintserversoverwideareasK(ratherthanjustbetweenNJEhostsatyour institution),J configureeachservertosendmessagesasauserratherGwthanalink,sothatcommandrepliesfromtheserverAwon'tappeartobefromanunknownBITNETnode.(Specify(MSG=USER73(inthe parameterfileforthelink.-IfKserversare installed homogeneouslyacrossaJnetcluster,Myoucanstoreasinglecopyofthe parameterfileintheA2common directoryJAN_COMMON:[SYS].SeeSection9.4ofthe  Jnet Manager'sGuide'for additional information. ` C UseDECnetobjectnumbersratherthanobjectnamesCbforDNANJElinks.-Sucha configuration eliminatesFloginfailurenoticesfromDNANJEdaemons attemptingHtoconnectbeforeJnethasbeenstartedontheirpeerBlsystems, andcanimprovesecuritybyallowingtheKremovaloftheDECnetTASKobject.(SeeSection11.2.1of the ^ Jnet Manager'sGuide'for additional information. `Alwaysenablemultistreaming!vonbusyBITNETlinksIwhenbothpeerspermitit.-Forthebest utilizationofAM available bandwidth,! especiallyonTCPNJElinks,@ configuresevenstreams.1Forthemost responsiveK transmissionof electronicmailfiles,specify transmissionJW algorithmFwithafilesize thresholdlargerthanmostN electronicmailfiles.+Useaninitialsettingof1000linesD unlessyouhave determinedthesize distributionofKa files transmittedonthelink.-SeeSection11.5.1ofthe Jnet Manager'sGuide*  for additional informationonF multistreamingonDNANJElinks,orthe correspondingEj sectionsofthe documentationforBSCNJE,OSINJE,* SNANJE,andTCPNJElinks.XWY"W >O5.4.2.11BEdit$SYS$COMMON:[SYSMGR]LAT$SYSTARTUP.COMJO)Ifyouhavea VAXcluster configurationinwhichnotallJO VAXclustermembersareJnetclusternodes,andusersuse OLocalArea Transport ( LAT-)toconnecttothe VAXclusterNO3for timesharing services,consider establishingaLATserviceMOcalled ``BITNET'', availableonlyonBITNETnodes,towhich&OBITNETusersmayconnect.yXOJOSettingupsuchaservice,andtrainingBITNETuserstoLOconnecttoitwhentheywantBITNET services,willreduceIO5thenumberoftimesBITNETuserslogintoa VAXclusterLOmemberandtrytouseBITNET services,onlytofindthatKOtheymustlogoutandconnecttoanotherclustermember.MO>This situationoftenariseswhena VAXclusterincludesbothGO timesharingsystemsonBITNETand workstationsthatdo,OnotrunJnet,as suggestedinjSection5.1.1.*Xj?+YXZY &O5.5BBringupBITNETlinkNOUIfyouhaveagreedonlink protocols, parameters,andnamesFOwiththe Postmaster(orNJEnetworkmanager)ofyourLOpeernode,yourlinkshouldcomeuptotheConnectstateQO^assoonasbothsidesarestarted.*ForyourfirstattempttoSObringupthelink,itisusefultomake telephonecontactwithPOthe PostmasteroftheothernodeandstartbothendsoftheNOhlinkwhileyoumonitorthestateofthelinkwiththeJCPOcommandMONITOR/CONTINUOUS n.Z aROIfbothsidesgototheActivestatebutdonotconnect,youDOandtheother Postmastercan immediatelyreviewtheHO5configuration,testthe underlyingnetworklayers,tracePOtheBSCline,orinitiateothertroubleshooting procedures.)IfROeithersidedoesnotreachtheActivestate,youshouldreviewQO>the configurationofthatsideofthelink,andif necessary,LOcallJoinerorthevendorofthepeer'sNJEsoftwarefor-Osupport.+SeeChapter18ofthe  Jnet Manager'sGuide for@OHmore informationontroubleshootingBITNETlinks.\[2UOIfthelinkgoestotheConnectstate,testthelinkbysendingGO interactive messages./Ifthatworks,requesttheotherKO5 Postmastertosendyouacopyoftheroutingtablesfor4Othepeernode.'YouwillusetheminkSection5.6.*[kP{?\[Z\a&O5.7BRegisterBITNETnodesLOUYouarereadytoregisteraBITNETnodeifthe following)O prerequesiteshavebeenmet: b `m#mAllthe assumptionsinmSection3.1mare fulfilled. `: Connectiontoadjacentsiteis operational. `l3lInitialroutingtablesare installed.*b0|?oh \ []8c`.O5.7.1BAbouttheUPDATE procedureDO4AllthedataabouttheBITNETnetworkandallNJEEO cooperatingnetworksare maintainedinBITEARNNODES.POEachdatavalueis associatedwithorassignedtoaspecific O=tagK=(nottobeconfusedwiththetagofanNJEfile).+EachQOtagbeginswithacolon(:)*andendswithaperiod(.).+ThePO informationaftertheperiodisthevalue associatedwiththeOGtag. d! NJOToregisteraBITNETnode,theTECHREPsendsafileof.OupdatecommandsandtagstotheupdateservergatBITNIC?O5toaddorchange informationinBITEARNNODES.e DOYoushouldhavecopiesof``BITNETNode InformationIOUpdate Procedures''and ``RequiredInfo''.+PrintedcopiesJO5weresentaspartoftheTECHREPpacket.+TheyarealsoDO availableasthefilesUPDATEPROCEDURandREQUIREDGOINFO,fromLISTSERV@BITNIC.(Don'tusetheolder,now-AO>obsoleteREQUIREDINFO1.)-These documentsdescribeJOthe proceduresrequiredtoprepareandsubmitanon-lineLOrequesttoadd,delete,ormodifynodeandcertainmemberGOH information,andtheminimum informationrequiredina2Onodeentrytoregisteranewnode.Jf JOThisbookdoesnotattempttodiscusstheusageofall?Odefinedtags.2Thedefining documentfor BITEARN,O5NODEStagsisNEWTAGSDESCRIPT  35, availablefrom4OLISTSERV@BITNET. NEWTAGS DESCRIPT is aGO comprehensivedocumentthatisnormallymoreusefultoCO> developersofBITNETserversthanto TECHREPs,whoEOjustneedtoupdateBITEARNNODES,forwhichUPDATEAOPROCEDURandREQUIREDINFOarebetter references.*f"/Ahg>>OThestepsforanewmemberor affiliateare:h H`m1.:Receive notificationthataBITNICstaffmemberhas%createdthememberentryI`E2.:SendinitialupdatejobtoCONNECT@BITNICwithsteps to:i h9Yhadd Postmasterpeopletagtomemberentry #Yregister PrincipalNode?`f3.:Sendupdatejobsto UPDATE@BITNICtocreate remainingnodesojEEOThesestepsare explainedinthe following sections._}p Sstepsareshown.,Ifthe TECHREP'snodeis connectedtoJOthenetworkbutnotyet registered,sendtheUPDATEjobAOtoCONNECT@BITNIC.Ifthe TECHREP'snodeisbothIOH connectedand registeredinBITEARNNODES,sendthejob8Oto UPDATE@BITNICfor automatic processing.naEOYoushouldmakeeveryefforttosubmitUPDATEjobs,PO particularlythejobtoaddyourinitialnode,bythecutoffMO5dateforthefirstpossiblemonthlyupdatecycle.+ CurrentlyQOthecutoffdateisthe fifteenthdayofeachmonth, includingIOholidaysand weekends,forthe followingmonth'stables.DO>YouwillbeabletomanageyourBITNETnodesmuchLOmore effectivelyafterthe TECHREP'snodeis registeredinEOBITEARNNODESandtheTECHREPcanreceivefilesand/OH electronicmailoverthenetwork.1a} MOExample5-2:7UPDATEjobtocreateanodeentryinBITEARN02NODESfora standaloneVAXsystemOADD%NODE%ARNOLD 1 TO%MEMBER& MN_ARNOLD&O:NODEDESC.Arnold& Consulting%O  :FFORMAT.VD%ND%PU%PR%DD  2Og :MSGS.YES g3RO*&Topology& configuration% (connected%to%WISCMAC3%by%Ethernet%LAN)"O:LINKS1.WISCMAC3(V1,10M) 4O?:CONNECT.READY {?55O*&System%hardware/software% configuration,O:MACHINE.Digital& VAXstation%3100 6O :SYSTEM.VMSO_ :NETSOFT.Jnet@O*&Routing%table%generation/destination% information2O :ROUTTAB.JNET&(NETSERV,POSTMAST@ARNOLD) 7b~  WLOExample5-3:7UPDATEjobtocreatenodeentriesinBITEARN52NODESforatwo-node VAXclustersystemOcADD%NODE%DECUSA c1 cTO%MEMBER&MN_DECUS;O:NODEDESC.DECUS%U.S.%Chapter&Spring% Symposium%O :FFORMAT.VD%ND%PU%PR%DD 2RO:*&Topology& configuration% (connected%to%Georgia&Tech%by%T1%link)!O:LINKS1.GITVMA(V1,1.5M) 4O:CONNECT.19920501 55O*&System%hardware/software% configuration)OZ:MACHINE.Digital&VAX%9000-420 Z6O :SYSTEM.VMSO :NETSOFT.Jnet@O2*&Routing%table%generation/destination% information/Oz :ROUTTAB.JNET&(NETSERV,ARNOLD@DECUS) z7OADD%NODE%DECUSB 1 TO%MEMBER&MN_DECUS;O+:NODEDESC.DECUS%U.S.%Chapter&Spring% Symposium%Os :FFORMAT.VD%ND%PU%PR%DD s2KO*&Topology& configuration% (connected%to%DECUSA%by% Ethernet) O:LINKS1.DECUSA(V0,10M) 4OK:CONNECT.19920501 K55O*&System%hardware/software% configuration)O:MACHINE.Digital&VAX%6000-660 6O# :SYSTEM.VMSOk :NETSOFT.Jnet@O*&Routing%table%generation/destination% informationO :ROUTTAB.NONE V7OdADD%NODE%DECUS {d1dTO%MEMBER%MN_DECUS;O:NODEDESC.DECUS%U.S.%Chapter&Spring% Symposium%O :FFORMAT.VD%ND%PU%PR%DD 2KO< *&Topology& configuration% (VAXcluster%of%DECUSA&and%DECUSB)0O :LINKS1.DECUSA(P,999M)&DECUSB(P,999M)  4O :CONNECT.19920501  55O *&System%hardware/software% configuration&O\ :MACHINE.Digital& VAXcluster `\ 6O  :SYSTEM.VMSO  :NETSOFT.Jnet@O3 *&Routing%table%generation/destination% information/O{  :ROUTTAB.JNET&(NETSERV,ARNOLD@DECUS) { 7O MODIFY%NODE%DECUSA1O, :LINKS1.GITVMA(V1,1.5M)%DECUSB(V0,10M) , 4Ot :LINKS2.DECUS(P,999M) t 4O MODIFY%NODE%DECUSBO :LINKS2.DECUS(P,999M)  4 ^ ]`o3O5.7.3BAddinga PostmasterpeopletagDO4EachBITNETmember organizationhasasinglememberBOentryinBITEARNNODES,whichcontains informationEOaboutthememberasawhole, orcommontoallthe=O=member'snodes..TheTECHREPmaymodifymemberOentries.}Example5-1+xshowshowthenodeentryMN_FODECUSmightlookifDECUSbecameaBITNET affiliate.*o}YOpq LOYouwillneedtospecifya PostmasterforeverynodeyouDO register.+TheeasiestwaytodothisistoaddapeopletagKO<forthe PostmastertoyourmemberentrywhereitcanbeNO referencedineverynodeentry.,Ifthishasnotbeendone,=Oincludethe followingstepinanUPDATEjob:$OrMODIFY%MEMBER& membernameMO4:P_POSTMAST.POSTMASTER;POSTMAST@principalnodename;+n&nnn%nnn.nnnn:rOwhere:s! DuHO membernameisthenameassignedtoyourmembertagby?0 BITNICstafforas subsequentlyrenamedoneof=~ your authorizedmemberrepresentatives.!(Itis ~ notC thesameasthenameofyour organizationorany ofyournodes.)TO principalnodenameistheNJEnameofyour PrincipalNode(orits@ Jnetclustername,ifyour PrincipalNodeisa(- memberofaJnet cluster).O +nnnnO nnn.nnnnC isthe telephonecountrycode,cityorareacode,B andnumberofthepersonwho currentlyholdstheAB postmasterrole.#ThecountrycodefortheUnited? States,Canada,andthe Carribeanis1.%FollowA the punctuationexampleforthistagexactly;no!+ hyphensmaybeused.t! @OToadda postmastertagtotheDECUSentryinExample5-1,9OtheTECHREPwouldsubmitthisupdatejob:"OaMODIFY%MEMBER&MN_DECUSAO(:P_POSTMAST.Postmaster;POSTMAST@DECUS;+1&608%238.7835*tFOp^ui4HOAsyour organizationadds additionalsystemstoBITNET,GOyoumaywant different Postmastersfor differentkindsLO5ofsystems,forexample,oneforIBMsystemsandoneforGOVAX/VMSsystems.,Youcanthendefine additionalpeopleBOtags.+SeeUPDATEPROCEDURformore informationonO>peopletags. _UNote _BHEvenifyoudonotcreateapeopletagforthe: POSTMASTERmailboxandevenifyoudonot@registerthe POSTMASTERmailboxasan privilegedERADMINuseratthememberornodelevel,theremust<stillbea POSTMASTER(and POSTMAST)mailbox5oneveryBITNETnode,as explainedinmSection3.4.7.1. M*um? dce! g,O5.8.1BThemonthlyupdatecycleKO4After submittingUPDATEjobstoaddyourfirstnode,andCO optionally additionalnodes,toBITEARNNODES,waitKOforroutingtables includingyournodestobe distributedEO= throughoutthenetwork./TablesarenormallysenttheEOfirstfullweekendofeachmonth, and importanthubMOnodes generallyinstallthemwithinafewdays,soifyouNOGregisteryournodesjustbeforetheupdatecutoff (currentlySOthe fifteenthofeachmonth),tableswithroutesforyournodesTOwillbeshippedinasfewasthreeweeks.)IfyoujustmissanNOQupdatecutoff,however,itwilltakeuptoeightweeksforHOtables includingyournodestobeshipped.'Planahead! (OSinceyourfirstnodewill  not)beinthetableswhentheyGOareshippedunlessyouhavemadespecial arrangements,OO5theinitialattempttosendyouroutingtableswillprobablyDOfail.2As a serviceto newnodes, however,!anEARN>O participant, Hans-UlrichGiese, U001212@HEARNor8O>U001213@HNYKUN11.URC.KUN.NL,resendsroutingQOtablesfornewnodesabouttwoweeksaftertheinitialtablesKOareshipped.,Bythistime, intermediatenodeshavehadaROHchancetoinstalltheirtables,and successfuldeliveryismuchOmorelikely.S )GOUntiltableswithroutesforyournodesare generallyFO available, youcanimproveinitialnetworkservicebyAO5 arrangingforTECHREPsor PostmasterstomanuallyOOdefinearouteforyour PrincipalNodeat intermediatenodesEObetweenyournodeBITNIC,andbetweenyournodeandEO>yourregionalNETSERV.Contactthe responsiblepeoplePOafteryournodeis connectedbutbeforeitiswidelydefinedHOinNETSERV-generatedtables.(A telephonecalltoBITNICOOHcanhelp determineifthiswouldbe practicalandusefulinQOyourcase.'BythesecondupdatecycleafteryouregisteryourJOnodes,yourtablesshouldarrive uneventfullyeachmonth. edf! +O5.8.2B MonitoringtableupdatesLO4Youare dependenton Postmasters throughoutthenetworktoNOmanuallyinstalltheirroutingtableswhentheyarrive.'ManyLO Postmasterscanbedependedupontoperformthis importantGO=task promptly,butunfortunately,afew PostmastersdoLOnottakethisresponsibility seriously.+Thiscausesnetwork2O connectivityproblemsfornewnodes.= NOIftherearestillnodesbetweenyournodeandyourusers'FOcorrespondentsthathavenot installedtablesdefiningGO5arouteforyournodeamonthaftersuchtablesareMO generally available,youshouldfeel justifiedin contactingOOthe Postmasterofthenode,by electronicmailor telephone,SO>toinsistthatthenewtablesbe installed,asrequiredbytheIOCRENTermsand Conditionsof Membershipand Affiliation.! WKOAfteryounodehasbeen publishedinthetables,troubleLO receivingmailandfilesisprobablycausedby out-of-datePO5routingtablesonothernodes.'Rememberhowitfeels,becauseMOyearsfromnow, Postmastersofnewnodeswillbe depending Oon  youIStoupdateyourtablesinatimelyway,asdemandedbyO>theCRENterms.#! ROYoucanfindoutwhichnodesdonothaveyouintheirtablesRObysendingashortfiletoorthroughthem.'Thenodeadjacent/O5tothelastnodetosendyoua!5fileprogressmessage5istheLOcauseofthetrouble,ifthesystemrunsVMandRSCSorIOVMSandJnet.((IBMsystemsrunningMVSandJESdonotOO>sendmessageswhentheyforwardfilesonbehalfofaremoteOuser.)! YVOIfanoderunsVMorJnetandhasyournodeinitstables,you,OcanalsosendtheNJEcommand QUERYVERSyymm$tothenode.OO5Ifthenodehasarouteforthe pseudonode VERSyymm,itisOusingthe mm8thsetoftablesissuedintheyear19 yyY.*UnlessMOtherearespecialtableupdates(usuallymadetocorrectaO> problem),version>yymm8>tablesarethoseissuedatthe beginningOofthe 3mm}thmonth.gfhy! O=O 6.2 Installing!and" Registering!a!BITNET!MailerKOThischapterprovides suggestionsforthemailerlayerofJOyournetwork.&Thisbookprovides supplementary informationHOBonrunningPMDFintheBITNET environment,andisnot5OintendedtoreplacePMDFdocumentation.hgiew;,O6.1BExternalviewofamailerMOUTootherBITNETnodes,amailerisan applicationwithanGONJEaddressthatcansendandreceiveBSMTPmail.,ToMO correctlysetupamailer,youmustchooseanNJEaddress.O^forthemailerandinsurethat:<  `mDmPMDFusestheselectedaddressastheNJEenvelope (tag)returnaddress `EIEMailtotheselectedaddressisroutedtoPMDF'sBSMTP processor `LTheselectedaddressis registeredasthemailerforyour"vnodeinBITEARNNODES Y 1(v,andinturn,inXMAILERNAMES `MMMTheselectedaddressis registeredasthemailgatewayfor)yourdomaininDOMAINNAMES*,/1! Wbeyondthescopeofthisbook.NIOThe remainderofthischaptershowshowtoinstallandAO configurePMDFonaVAXor VAXclustersystemto8O5 consistentlymeetthesefour requirements.ihj )O6.2BInstallPMDFBOUPMDF installationisa straight-forward processofJO unpackingfilesfromthe distributionsavesetsintotheJOPMDF directorytree.)Yourprimary decisionsaretheUserKO^IdentificationCodes(UICs)ofanyrequiredPMDF accounts,OOthenameofthebatchqueue(s)PMDFwilluse,andwhereto OputthePMDFfiles.jik OSYS$MANAGER:SYLOGICALS.COM,manuallyredefinetheMO>devicelogicalname,movethe directorytreeswiththeVMSbatchqueuecalled>PMDF_aliasname >,where2> aliasname>isthe4ODECnetaliasnameofyour VAXcluster.! pDOTo initializePMDFbatchqueues,createthecommand7O procedure"SYS$COMMON:[SYS$STARTUP]PMDF_INIT_DO5 QUEUES.COM.ForVMS V5.0-V5.4,executethe procedureBOusingtheSYSMANSTARTUPfacility (recommended)orlater versions,runPMDF_INIT_QUEUES.COMonlyonce,IOthensaveittodocumenthowyou initializedyourPMDFKOqueues.'The batch/print subsystem introducedwithVMSV5.5NOHdoesnotrequirequeuestobe initializedaftereachsystemOboot.OExample6-17HshowsasamplePMDFqueueinitializationDO procedurefora VAXclusterwithtwomembersrunningO5PMDF.Do 5 not75startthe node-specificqueuesfromthisO procedure,anddo  nottusethe autostartfeature, introduced,OinVMSV5.5,forPMDFqueues.*OFO# ?OStart PMDF batch queues in a command procedure8O.SYS$COMMON:[SYS$STARTUP]PMDF_START_QUEUES.COM.HO<Executethe procedureusingtheSYSMANSTARTUPfacility:O (recommended)orSYS$STARTUP:SYSTARTUP_V5.COM.2 OExample 6-20Oshows a sample PMDF queue startupDO procedurefora VAXclusterwithtwomembersrunningNO5PMDF.Notethatthe node-specificqueuesarestartedasthe0Onodeonwhichtheyruncomesup.*OFO olp! O6.2.4BRun VMSINSTALLOWhenyouhavepreparedthedevicelogicalname, determinedBO_whetheryouhaveanyPMDFentriesintheSYSUAF,FOandsetupthePMDFbatchqueues,installPMDFwithJO VMSINSTAL accordingthe directionsinSection1.5ofthe6Oi PMDF InstallationGuide&ReleaseNotes1i,as supplemented2Obythe suggestionsinthissection.! OOIfyouwillbe installingPMDFona VAXcluster,performthePO installationonanyfastorlightlyloadedVAXsystemintheMOiclusterthatislicensedtorunPMDF.ThissectionassumesNOthatthis installationisthefirst installationofPMDFon1OyourVAXor VAXclustersystem.*The PMDF Installation"Or Guide&ReleaseNotes5rexplainsthe differencesbetweenanewMO installationandanupgrade installation.)ConsidersavinganFO# autoanswerfilein SYS$UPDATEas documentationofthe>O| installationchoicesyoumake,as suggestedin|Section4.1.*?|?{! QMOThePMDF installation procedureasksanumberof questions.?OThe procedure'spromptsandSection1.5ofthe PMDF0O5 InstallationGuide&ReleaseNotes"S5provide directionsforIO answeringthe questions.' RecommendedanswersforselectedO questionsfollow:  3 `mJmIfyoufollowedthe suggestiontocreatealogicalname$forthePMDFdeviceinFSection6.2.2,%enterMY_PMDF_D DEVICE:[PMDF]forthedeviceand directoryforPMDFwfiles. `BIfyouhavenoPMDFserverentryintheSYSUAF,AOallow VMSINSTALtocreateonenamedPMDF.AcceptFthedefaultnameandUICofferedbythe installation procedure. Securitycaution F Ifyou requestedan autoanswerfile,thepasswordofEbthePMDFaccountwillbewritteninthefile.+EditGthefileafterthe installationiscompletetodeleteEthe password,andpurgetheoriginalversionofthel autoanswerfile.  `9H9Specifythesamenumericoffsetfrom UniversalTimeasFyoudidfortheJnet configuration procedure(SectionO5.4). `iKiThesourcefilesareusefulonlyforapplyingpatches,aGprocesswhichrequiresaPascal compiler.(NormallyyouHshouldrequestthatthesourcefilesnotbe installed.*F?*:T|?(W@OWhen VMSINSTAL completes,ifyouaddedthePMDFIOcommandtotheDCLtablesandyouare installingonaOO5 VAXclustersystem, reinstalltheDCLtablesonallthenodesHOofthe VAXclusterusingSYSMAN.ThencontinuewiththeNOPMDFpost-installationsteps1and2inSection1.6ofthe6O> PMDF InstallationGuide&ReleaseNotes +>.? poq'! 9O6.2.5B ConfigurePMDFfor automaticstartupOO4Thissection supplementsthe instructionsforPost-installation,Ostep1inSection1.6ofthe&) PMDF InstallationGuide&O ReleaseNotes 4.! W~JOPMDF componentsandothersoftwaremustbestartedinaMOspecificordertoprevent mishandlingofmail.*YoucanuseCO5eithertheSYSMANSTARTUPfacility (recommended)orCOSYSTARTUP_V5.COMtostartPMDFandother networkingKOandmail software.)Software componentsmustbestartedinO>thisorder:c r?`m1.: Initialize PMDFqueues (VMS V5.0-V5.4 only):PMDF_INIT_QUEUES.COMG`E2.:InstallPMDFimagesanddefinePMDFlogicalnames:* PMDF_STARTUPcommand procedure.`3.:Start DECnet-VAX: STARTNET.COMN`4.:Startothernetwork software,forexample:'UCX$STARTUP.COM"orMULTINET_STARTUP.COM`t5.:Start DECwindows,`6.:StartJnet:'JNET_STARTUP.COMG`s7.:StartPMDFqueues(onlyneededonnodeswithPMDF)queues):'PMDF_START_QUEUES.COM9`K8.:SubmitperiodicPMDFjobs:2 PMDF_SUBMIT_JOBS.COMW a-?OInnosoft recommendsthatPMDF_STARTUP.COMberunCObeforeanynetworksarestarted.,Because DECnet-VAXDO5mustbestartedbefore DECwindows, STARTNET.COMmustDOberunfromSYSTARTUP_V5.COM.IfyouwillrunPMDFGOoverDECnet(eitherMAIL-11orSMTPoverDECnet),you@O>mustrun PMDF_STARTUPbefore STARTNET,andthus,LOfrom STARTUP_V5aswell.(Onlyifyouwillnotberunning?OPMDFoverDECnetcanyourun PMDF_STARTUPwithOHSYSMAN. 5OInitializationofPMDFbatchqueuesis onlyrequiredonLOVMSversionsbeforeV5.5.(IfyoufollowtherecommendationHO5tonotuse MAIL$BATCHandto initializequeuesfromaHOcommand procedure,youcanrunthe procedurebeforeorDOafter PMDF_STARTUP,butyoumustrunitbeforeanyKO>networksthatPMDFusesarestartedandbeforeusersare%Oallowedontothesystem.[rDOIfyouarenotusingPMDFoverDECnet,theSYSMANIOutilityis recommendedforstartingPMDFateachsystemFO5reboot.,TodirectSYSMANtoexecutethePMDFstartupHO proceduresinthecorrectorderduringtheVMSstartup:O procedure,enter,forallversionsofVMS: Ok$kSYSMAN%:==%$SYSMAN O$FSYSMAN%STARTUP&ADD%FILE&PMDF_STARTUP.COM%/PHASE=LPBEGIN O$FSYSMAN%STARTUP&ADD%FILE&PMDF_SUBMIT_JOBS.COM& /PHASE=END OB$GBSYSMAN%STARTUP&ADD%FILE&PMDF_START_QUEUES.COM% /PHASE=ENDf !5Oandenter,forVMSV5.0throughV5.4: O$JSYSMAN%STARTUP&ADD%FILE&PMDF_INIT_QUEUES.COM&/PHASE=LPBEGINq pr EO6.2.6BMakePMDFonlinebooks availableto Bookreader,O4Step2ofSection1.6ofthe&-4 PMDF InstallationGuide&O ReleaseNotes8IsuggeststhatyourunPMDF_ROOT:[EXE]PMDF_GODEFINE_BOOK.COMeachtimeyoustartupyoursystemtoQO=addthePMDFonlinelibrarytothelistof librariessearchedDObythe DECwindows Bookreader.,Becausethis procedureMOmustberunafter DECwindowsisstarted,itcannotberun;OGfromSYS$MANAGER:SYSTARTUP_V5.COM.UseoneofKOthesemethodstomakethePMDFonlinebooks availabletoO Bookreader:M r# `m5mCopythecommand procedure PMDF_DEFINE_ABOOK.COMtothe directorySYS$COMMON:[SYS$STARTUP],CandusetheSYSMANSTARTUPfacilitytorunitinwphaseLPMAIN. `6EditSYS$MANAGER:SYLOGICALS.COMtodefine?O DECW$BOOKinthesystemlogicalnametable..DoEnotdefineitinthe DECwindowslogicalnametable,Cbecausethe DECwindowsstartup proceduresrunafter?Y SYLOGICALS,andwould overwriteyour definition.D JW DECW$BOOKisasearchlistthathasonevalueforeachMonlinelibrary.'The followinglinesshowonewaytodefine> DECW$BOOKinSYLOGICALS.COMtomaketheonlineHa librariesforVMS,PMDF,andTGVMultiNet availableto Bookreader: >... $4$!%Online% documentation%for% BookreaderD$&DEFINE/SYSTEM/EXEC% DECW$BOOK%OLD_DEVICE:[DECW$BOOK],-^PMDF_ROOT:[DOC],-0&MULTINET_ROOT:[MULTINET.DOCUMENTATION] ...! WHOTheversionof Bookreadershippedwith DECwindowsMotifKO (DECwindowsVersion3)supportsthe expansionof librariesQO5inoutlineformbydouble-clickingonthelibrarynameintheKOlibrarywindow.'Unlessthe bookshelfforalibraryhasa5TITLE>Oline,thelibraryislistedonlyas ``Library  nO'',where  nisanO>integer.MOTocause Bookreadertodisplayan informativenameforthe(OPMDFonlinelibrary,enter: Oa$'aSET%DEFAULT&PMDF_ROOT:[DOC] O$-COPY%SYS$INPUT+PMDF.DECW$BOOKSHELFO_To:- #LIBRARY.DECW$BOOKSHELF;/CONCATENATE InstallationGuide&ReleaseNotes ,>.*|?s rt? `&O6.3.1BObtainmailerfilesLO4TogeneratePMDFtables,youmustobtain up-to-datecopiesyear,forexample,9202forthesecondupdatein1992.KOUnlessthereisanextraupdate,forexample,tocorrectKOanerror,thelasttwodigitsnormally correspondtotheKOHmonth.-Thefilename,type,andversionofyourcopyofCOtheFebruary1992DOMAINNAMESfilewouldthusbeODOMAIN.NAMES;9202.n>OTheuseofXMAILERNAMESandDOMAINNAMESisO describedin Section6.3.2.* ?=v# _HOExample6-3:7PMDF configurationfileforaBITNETnodeIOB!&PMDF.CNF&-%PMDF% configuration&file%for&the% two-member,O!& VAXcluster%system& Arnold.Com. O!:O!&Rewrite%rules%for&the%local% host/clusterOb!&Domain%namesO Arnold.Com$ $U@Arnold.ComOArnold1.Arnold.Com$ $U@Arnold.ComO:Arnold2.Arnold.Com$: $U@Arnold.ComO!&BITNET%namesO ARNOLD.BITNET$ $U@Arnold.ComO ARNOL1.BITNET$ $U@Arnold.ComOZ ARNOL2.BITNET$Z $U@Arnold.Com,O!&DECnet%and%short%form%namesOArnold$ $U@Arnold.ComO1ARNOL1$1 $U@Arnold.ComOyArnold1$y $U@Arnold.ComOARNOL2$ $U@Arnold.ComO Arnold2$  $U@Arnold.Com%OQ!&TCP/IP%domain%literalsO[192.135.80.1]$ $U@Arnold.ComO[192.135.80.2]$ $U@Arnold.ComO)[192.135.80.3]$) $U@Arnold.Com)Oq!&All%other%domain%literals O[]$$U%[$L]@MTCP-DAEMON O!>OI!&BITNET%rewrites%included%from&external&files O!'OO4Theautoconfiguration procedurewritesthe PMDF@O configurationfile,PMDF_ROOT:[TABLE]PMDF.CNF,thatJO recognizesmailfortheTCP/IPhostnameorBITNETnodeIO=nameaslocalmail.)Ona homogeneous VAXclustersystem,MOeachclustermemberandthe VAXclusteritselfcanbeknown Oby$mBITNET(NJE)nodename,'domain(TCP/IPhost)name,6 short-formaliasesforthenamesabove,"wDECnetnodename,and/domainliteralname(IP address).! SOTheusual intentionisto recognizemailtoanyofthesenamesNOaslocalmail.,UseaneditortoaddallthemissingnamesKO5toyourownnewPMDF configurationfile.*InsurethattheFOTCP/IPhostname,BITNETnodename(withandwithoutO.BITNETBT),andDECnetnodenameofeverysysteminyourFO> VAXclustermapstothedomainnameofthe VAXclusterOitself.?OExample6-3=DshowsthePMDF configurationfileforatwo-IOnode VAXclustersystemonbothBITNETandthe Internet.RO5Thefilehasbeenmanuallyeditedtoincludethefulllistof'Onames recognizedaslocal.*OFO,! JOCertaincharacteristicsofPMDF's operationare controlledOforeachdeliverychannel ,bychannelkeywordsintheBO<PMDF configurationfile./ BeginningwithV4.0,PMDF-Osupportsthe configurationofadefaultchannelN./TheSOdefaultchannelexistsonlytoallow modificationofthedefaultIOEchannel keywords.*(Thedefaultchannelisnot documentedOuntilPMDFV4.1.)-NDOBITNETnodesshouldnormallyhaveadefaultchannelOwithtwo keywords:2LOGGING RandSENDHEAD.(bSENDHEADiscalledO5 POSTHEADONLY')5 beginningwithPMDFV4.1.)7 IOTracing individualmailfiles, fortroubleshootingortoKOconfirm delivery,isan importantdutyofthe Postmaster.GO5TracingBITNETmailbetweenmailersrequiresthatmailIOfilesbeloggedatthemailerlayer.1Unfortunately, theFOautoconfiguration procedureshippedwithPMDF generates7O>configurationswithlogging disabled.+The6>LOGGINGX>channelJOkeywordontheDEFAULTenablesloggingforall channels.; JOWhenPMDF encountersa permanentdeliveryerror,ittrysROtoreturnthemessage,alongwitha notificationoftheerror,IO5tothesender.. Optionallyandbydefault,PMDFsendsaO copyCofthis nondeliverynoticetothe Postmaster.-PMDFKOalsosendsthenoticetothe Postmasterifit encountersEO>a permanent delivery error whiletrying tosend theKO nondeliverynoticetothesenderoftheoriginalmessage.! NOIfthe nondeliverynoticecontainsthetextoftheoriginalQOmessage(the default),theprivacyoftheoriginalmessagecanLO5be compromisedbycarelesshandlingbythe Postmaster.'TheOSENDHEAD (or POSTHEADONLY0)keywordhelpsthe Postmasterto1Omaintaintheprivacyofusermail.N,OThePMDF configurationfileinExample6-3showstheROadditionofadefaultchannelattheproperplace,justbeforeO5thelocalchannel.*FOzODonotspecifythe HEADEROMIT}ortheo HEADERBOTTOMJkeywordsMOonthedefaultchannel.*Theformermakesitvery difficultJO5todiagnosemailrouting problems..ThelatterforcestheNO Postmastertoscrollthroughtheuser'smessagetoreadthe)Omailheadersatthebottom. aMOUsersmayobjectto scrollingthroughmanymailheadersatJOthetopofeachmessage.)Userswho thoroughly understandPO5the disadvantagesof discardingmailheadersatlocaldeliveryFOcanusePMDF's integratedDELIVERfacilitytodiscardPOsomeorallheadersfromtheirownmailor otherwiseprocessMO>ituponarrival.-ThedetailsofsettingupsuchachannelPOareoutsidethescopeofthisbook,however.*SeeSection2.3Oofthe(7 PMDFSystem Manager'sGuidefor informationonOHDELIVER.yl A @OExample6-4:7PMDFaliasfileforaBITNETnode?OB!&ALIASES.&-%PMDF%aliases&file%for& Arnold.Com. O!5O!& Address(es)&for%the%local% Postmaster O!Obfield:$bsystemOmaint:$ postmasterOpmdf:$ postmasterO: pmdf_user:$: postmasterO postmaster:$arnoldO postmast:$ postmasterOroot:$ postmasterOZ smtpuser:$Z postmasterOsystem:$ postmaster O!#O1!&BITNET%gateway&alias Oy!Omailer:$mailer@bitnet-gateway O !%OQ!&Locally%useful&aliases O!O info-pmdf:&$info-pmdf@ymir.claremont.eduO)service:$)arnold,%maxwellOqsteve:$qarnold O!TO!&Aliases%for&long%names% generated&by&PMDF_ROOT:[EXE]LONG_NAMES.COM OI!O DSN$SERV:% DSN$SERVERO FARMINGT:% FARMINGTON O!  MAIL$SER:% MAIL$SERVER!Oi  MIRRO$SE:% MIRRO$SERVERO  NML$SERV:% NML$SERVER!O  SYSTEST_:% SYSTEST_CLIGOA  VPM$SERV:% VPM$SERVER#wux2` O6.3.4BRun LONG_NAMESIO4Ifthereare mailboxesonyoursystem (includingSYSUAFIOentriesand forwarding addressesintheVMSmailprofile)HOwithnameslongerthaneight characters,reviewSectionO=5.9.4ofthe(= PMDFSystem Manager'sGuide=andtaketheDOmost appropriateactionforyoursystem.+ (POSTMASTERJOissuchamailboxname,butitishandledbythePMDF(OGautoconfiguration procedure.) WJOInmostcaseswheretherearemailboxnames(otherthanLO POSTMASTER)longerthaneight characters,itisusefulandAO5harmlesstorunthe procedurePMDF_ROOT:[EXE]LONG_CO NAMES.COM.This procedurecreatesaliasesfornamesGOlongerthaneight characters,andwarnsyouaboutany?O> mailboxeswiththesamefirsteight characters.  BOAfteryourun LONG_NAMES,appendthenewaliases,:Oin thefilePMDF_ROOT:[TABLE]ALIASES.TMP,to9O5theend ofPMDF_ALIAS_FILE (normally PMDF_BOROOT:[TABLE]ALIASES.).-Dealwith conflictingmailboxHOnames,listedinthefilePMDF_ROOT:[TABLE]CONFLICTS.TMP,GO>bychangingtheuser'sloginname (recommended)orbyHOmanuallyaddinganaliasforthemailboxtothePMDF_O ALIAS_FILE.xwz *O6.3.5BEditPMDFaliasesfileKO4EditthePMDF_ALIAS_FILE (normallyPMDF_ROOT:[TABLE]ALIASES.)AOtoforwardmailfor additionalsystem-manager-likeKO mailboxestothe Postmaster,toaddthealiases generatedKO=by LONG_NAMES,andtoaddanylocallyusefulaliasesand5Omailinglists.'SeeSection3.3ofthe!> PMDFSystem Manager'sO Guide:4for background informationand instructions.N$OExample6-4O5to POSTMASTER,thenforwards POSTMASTERtotheGOpersonalusernameofthecurrent Postmaster,allowingMO Postmasterdutiestobeeasily reassigned.)TheexamplealsoHO>showsnicknamealiases(forlocalandremote mailboxes)UOandamailinglist,allowingmailtobelocallyfannedouttoa Onumberof mailboxes.*OFOB IOTherecanbeno duplicatesinALIASES.The autoconfigu-IOration procedurecreatesanaliasfor POSTMAST,asdoesAO< LONG_NAMES.Whenyouadd ALIASES.TMPto ALIASES.,EOdeletethealiasforPOSTMASTcreatedby LONG_NAMES.zx{! Vc'O6.3.6BCompile configurationPO4BecauseofthesizeofthemailertablesrequiredforBITNETOnodes,= alwaysPcompile0yourPMDF configurationtoimproveIO performance.)Compiledconfigurationsare describedinthe(O= PMDFSystem Manager'sGuide=,Section3.5.'{z|}! US2O6.3.6.1CCompilemaximum configuration@O)WhenyoucompilethePMDF configurationforthe) first?)time,QOandafteranymajorchangeinthesizeofyourmailertablesEO(forexample,uponjoiningBITNET),youmustcomputeQO3thesizesofinternalPMDFtablesandstorethesizesintheOPMDFeoptionsfile50.(Itis recommendedthatBITNETsitesROrepeatthisstep annually,totunethesizeofPMDFtablesto0O<theamountofdatatobestored.zPOTocreateanewoptionfilewiththecorrectsize parameters+Oforyourconfiguration,enter: Oa$.aPMDF%CNBUILD/NOIMAGE/MAXIMUM/OPTION! UO Additional informationonthisprocessisinSection3.5.2ofthe(O PMDFSystem Manager'sGuide .}|~0! `O6.3.7BMoveLMD.COMMO4InorderforPMDFtohandleallincomingBITNETmail,theJOLocalMailDeliverycommand procedureprovidedwithJnet,AOJAN_COMMON:[SYS]LMD.COM,mustbereplacedwithoneLO=oftheversions distributedwithPMDF.This importantstep4Ois describedinSection5.9.1ofthe! PMDFSystem Manager'sO GuideG,andmustberepeatedeverytimeyouupgradeeitherOGJnetorPMDF. DOUsethecorrectversionofLMD.COMfortheversionEOofJnet installedonyoursystem..ComparethePMDF-LO5suppliedversionwiththeJnetsuppliedversionandreviewNOalldiscrepancies.'TheremaybecustomizationsbythepersonSOwho installedJnet,andiftheyarestill required,thechangesKO>mustbemergedintotheversionofLMD.COMprovidedwithOPMDF.x! NJOAfteryouhavecopiedthecorrectversionofLMD.COMtoSOtheJnet directorytree,stopandrestarttheJnetlocaldaemonPO5(oneachclusternodeifyoursystemisamemberofaJnetO cluster).+The(A PMDFSystem Manager'sGuide incorrectlyMOcallsthis ``shuttingdownJnet'slocal servers''.,TheJnet,O> documentationreservestheterm>shutdown>forthestopping Oof  allJthelinkdaemonsonanode,notjustthelocaldaemon.5 UOExample6-5:7UPDATEjobtoregisteramailerandInternetaddress=2inBITEARNNODESfora standaloneVAXsystemOMODIFY%NODE%ARNOLDO :SERVERS1 1.MAILER -2t@ARNOLD 3(MAIL 4 , J5 ,,,P_POSTMAST 6 )O:INTERNET.Arnold.Com [7 -UOExample6-6:7UPDATEjobtoregisteramailerandInternetaddress:2inBITEARNNODESforatwo-node VAXcluster23systemOMODIFY%NODE%DECUSO :SERVERS1 1.MAILER -2t@DECUS u3(MAIL 4 , %5k ,,,P_POSTMAST r6 )$O;:INTERNET.Sympos.DECUS.Org ;;7OMODIFY%NODE%DECUSAO :SERVERS1 1.MAILER -2t@DECUS u3(MAIL 4 , %5k ,,,P_POSTMAST r6 )8O4:INTERNET.Sympos.DECUS.Org%A.Sympos.DECUS.Org 47OMODIFY%NODE%DECUSBO :SERVERS1 1.MAILER -2t@DECUS u3(MAIL 4 , %5k ,,,P_POSTMAST r6 )8O-:INTERNET.Sympos.DECUS.Org%B.Sympos.DECUS.Org -7 `POExample6-7:7MailtoDOMAINS@BITNICtoregisterthe Arnold.Com2domainwithBITNET%ODomain:Arnold% ConsultingOName:2Arnold% Consulting%Local%Area&Network!OGateway: MAILER@ARNOLD&OW Gatemaster:%POSTMAST@ARNOLDHO>--------------------------------------------------------------GO:NICK.Arnold.Com&:MAILER.MAILER@ARNOLD%BSMTP%3& :SERVED.NO8O/ :SITE.Arnold% Consulting%Local%Area&Network6Ow:GATEMAST.POSTMAST@ARNOLD&:INTERCONNECT.YESHO>-------------------------------------------------------------- eU ;(O6.6.1BTagsinDOMAINNAMESPO4ToregisteradomainwithBITNIC,yourmailtoDOMAINS@BITNIC)Omustspecifyvaluesforthe8:NICK , :MAILER %,Q:SERVED W,:SITE >,O :GATEMAST,andh :INTERCONNECT(htagsinDOMAINNAMES.ThisQO=sectionprovides clarificationofthe permittedvaluesoftheseKOtags.+This information supplementsthe descriptionsofthe0OtagsattheendofDOMAINGUIDE.  OThe:MAILER=tagshouldindicatethesameNJEaddressforOthemailerasthe :SERVERS1&AtagintheBITEARNNODESO5entry.((The5 :SERVERS10q5tagintheBITEARNNODESreplaced Othe:MAILER<taginBITEARNNODESin1991,andisstillO translatedtoam:MAILER#taginXMAILERNAMES.)lBOThevalueofthe :GATEMAST+)shouldbetheNJEaddressofIOthe Postmasterforthedomain./(Itisnot necessarytoMO5storetheInternetaddressofthe Postmaster;itisalwaysDO``Postmaster@''andthefully-qualifieddomainname.)IORegisterthePOSTMASTmailboxinsteadofthemailboxofMO>aspecificpersontomakeiteasiertodelegate PostmasterJOdutiestoa differentpersonby forwardingmailforthe-O POSTMASTERuseronyoursystem.sIDOTherehasbeenmuch discussionamongBITNETnetworkinthisdomainoverthe Internet,eitherunconditionally O(j:INTERCONNECT.YES<)oronlyifthesendingmailerandTCP/IP,OsoftwaresupportsMXrecords(:INTERCONNECT.MX !).*F}?# KO PostmastersofIBMnodesonbothBITNETandtheInternetAOandrunningVMandtheVMMailerV2shouldrunDO5JohnVoigt'sDOMAINEXECtotailortheirVMMailerMOconfigurationsiftheyprefertosendmailtodomainsthatEOhave InterconnectYESorMXoverthe Internet.+PMDFFO>doesthis automaticallyduringautoconfigurationunlessJOthedomainnameisincludedinthevalueofthesymbolO FORCE_BITNET.(Seethe(w PMDFSystem Manager'sGuide ,@OHSection5.8,forfurther informationonthetheH FORCE_BITNET,OFORCE_INTERNET, and8FORCE_INTERBIT] symbols.)NHOIfyour organizationprefersinboundmailtoarrivebyOBITNET,codel:INTERCONNECT.NO,,evenifallyourhostsare1O5directly connectedtothe Internet.! atNONotethatthis preferenceonlyappliestomail addressedtoHO domain-stylenames.)MailtoNJE addressesshouldalwaysIO5berouteddirectlyoverBITNETfromanotherBITNETnodeFOortoanINTERBITgatewayfromanInternethostandLOfinally deliveredbyBITNET.IfinboundroutingviaBITNETPO>isnotwhatyour organizationprefers,makesurealloutboundIOmailhasa domain-styleaddressreturnaddress,andaskFOuserstoinformtheircorrespondentsthat domain-style$OH addressingis preferred.p V   I, SOExample6-8:7MailtoDOMAINS@BITNICtoregisterthe BostonCol.Edu22domainwithBITNICandtheDDNNIC ODomain: BostonCol.EduOName:/Boston%College%Local%Area&Network OGateway: MAILER@BCVMS%OW Gatemaster:%POSTMAST@BCVMSHO>--------------------------------------------------------------JO:NICK.BOSTONCOL.EDU&:MAILER.MAILER@BCVMS&BSMTP&3% :SERVED.YES5O/ :SITE.Boston%College%Local%Area&Network4Ow:GATEMAST.POSTMAST@BCVMS%:INTERCONNECT.NOHO>--------------------------------------------------------------%O1.p Top-level%domain:Edu4OO2.pComplete&Domain%Name:J BostonCol.Edu3O3a.K Organization%name:Boston&College6O3b.K Organization%address:JBoston&College)d'Chestnut%Hill,%MAK02167KUSA/Oo4.pDate% operational:1%July&1992!Administrative%Contact(O 5a.KNIC%Handle%(if&known):3Oh5b.KName%(Last,&First):Jeff%JeffersO5c.K Organization:dBoston&CollegeO5d.KMail%Address:dNetwork%Servicesd@Computer%Center)dChestnut%Hill,%MAK02167KUSAO5e.KPhone&Number:d(617)%552-8507O5f.KNet%Mailbox:dJJeff@BostonCol.Edu' Technical%and&Zone%Contact8O6a.KNIC%Handle%(if&known):%John%McCarthy7O 6b.KName%(Last,&First)%:p(617)%552-4629OY 6c.K Organization:dY Boston&CollegeO 6d.KMail%Address:d Network%Servicesd Computer%Center)d1 Chestnut%Hill,%MAK02167KUSAOy 6e.KPhone&Number:dy (617)%552-8507O 6f.KNet%Mailbox:&d McCarthy@VMCMS.BostonCol.Edu* Primary&Server>O 7a.KPrimary%Server& Hostname:JHarvard.Harvard.Edu8O 7b.KPrimary%Server& Netaddress:K 128.103.1.17O# 7c.KPrimary%Server& Hardware:JMicroVAX%II9Ok 7d.KPrimary%Server& Software:J4.3&BSD%UNIX  Secondary%Server?O= 8a.K Secondary%Server% Hostname:KLilac.Berkeley.EduHO 8b.K Secondary%Server% Netaddress:K128.32.136.12,& 31.4.0.100O 8c.K Secondary%Server% Hardware:KVAX;O8d.K Secondary%Server% Software:K4.3%BSD&UNIXB~If%any% currently& registered%hosts%will%be%renamedBinto&the%new%domain,%please%specify%old% hostname,* netaddress,%and%new& hostname.Ow9.pNone7Please%describe%your% organization%brieflyKOI10.KBoston%College&is&an& institution&of&higher% education.Q  FO6.6.2B RegisteringanInternetdomainnamewithBITNICOO4Thissectionprovidesa partially hypotheticalexampleoftheLO registrationofaBITNETmailgatewaybyaCREN affiliateIOthatalreadyhas registeredadomainwiththeDDNNIC.IO=Foranexample involvingamemberthathasnotalready/O registeredwiththeDDNNIC,see/Section6.6.3ofthisbook.*/Y? e ;OOArnold Consulting anticipatesadirectInternet connection,soKOit registereditsdomainnamewiththeDDNNIC directly,MO5andarrangedfornameserviceforitsdomain,as described OinSection3.4.5.Example6-7,showsthecontentofthemailAOmessagethatmustbesenttoDOMAINS@BITNICfrom ARNOLD@ARNOLD(theTECHREPaddressforArnoldJO Consulting)toregisterthe company'sBITNETmailgateway&Otothedomain Arnold.Com.*P?*PO}OIn comparingYExample6-7 RtoExample6-8,noticetheseO differences:*YMO*MO @!  `mmThevalueofthe9m:SERVED Ymis mNO%mbecauseArnold ConsultingHhasarrangedfornameserviceitself.)BITNIC, Berkeley,IandHarvardwillnot automaticallyprovidethisservice. `ThevalueoftheC :INTERCONNECT Fis YES&becauseArnoldL Consultingwillbedirectly connectedtothe Internet,andFOnodesonboththeInternetandBITNETmaysendmail@tothedomainviatheInternetiftheyprefer. `'E'Items1-10areomittedbecause Arnold.ComisalreadyI registeredwiththeDDNNIC,andprovidedthe necessary3 informationtotheDDNNIC directly. TOToavoidthelossorreturnofmail,theexamplefilemustnotBObemailedtoDOMAINS@BITNICuntilArnold'sprimaryGO5and secondarynameserviceandInternet connectionareO functional.   JO6.6.3B RegisteringanewdomainnamewithBITNICandthe<(DDNNICOOThissectionprovidesa partially hypotheticalexampleoftheIO registrationofaBITNETmailgatewaybyaCRENmemberJO=thathasnot registeredadomainwiththeDDNNIC.ForOOanexample involvingan affiliatethathasalready registered#OwiththeDDNNIC,seeSection6.6.2ofthisbook.* ?  AOBoston College is a member of CREN, and has noNO immediateplanstoconnectitsVAXsystemstothe Internet.GO5 Nevertheless,toallow transparentmail addressingfromPOtheInternettousersoftheComputerCenter,thecollegeisIO registeringadomainnamewithBITNETandwiththeDDNO>NICthroughBITNIC.>Example6-8!>showsthecontentofFOthemailmessagethatmustbesenttoDOMAINS@BITNIC=OfromMCCARTHY@BCVMCMS(theTECHREPaddressforJOHBostonCollege)toregisterthedomain BostonCol.EduwithOBITNET.* O   ONoteinwExample6-80pthateventhoughBCVMSisaJnetEOcluster consistingofBCVAX1andBCVAX2,itisonlyHO5 necessarytoregisterthedomainonce.,BCVMS,theJnetOOclustername,isgivenastheNJEnodenameofthegatewayLOforthedomain,andallusersofBCVAX1,BCVAX2,andanyPO>futurenodesintheBCVMSclustercanreceivealltheremailIOthroughPMDFrunningoneitherclusternode.)Items1-10IOprovide informationrequiredbytheDDNNICtoregisterMOHthedomain,andwillbepassedfromBITNICthroughtothe=ODDNNICaspartofthe registrationprocess.* wFO   p1O6.7.1B SubscribingtoLISTSERVlistsFO4AfteryourBITNETlinkis operationalandyournodesBOhaveappearedinBITEARNNODES,youcan subscribeEOtoLISTSERVlistsbysendingmessagestotheserver6O=address(forexample,LISTSERV@nodename). = DonotNOsendadministrativemessagesormailtoalistaddress(forFOexample,LINKFAIL@nodename).'SuchmessagewillbesentJOGtohundredsor thousandsofotheruserswhomustdeleteMOthem,andwillnothavetheintendedadministrativeeffect.! 3DOTo subscribetoaLISTSERVlist, sendtheLISTSERV>Ocommand SUBSCRIBEto theserveraddress as anPO5 interactivemessage,inthebodyofmail,orasarecordinIOafile.*Forexample,to subscribetoLINKFAIL@BITNIC,IOentered: Ok$kSEND%LISTSERV@BITNICz(BITNIC)LISTSERV:2 SUBSCRIBE%LINKFAIL%Stephen&L.&Arnoldz(BITNIC)LISTSERV: *  *MACtrl/Z 5M * KOLISTSERV preservesthecaseofmyname;thecaseoftheBOcommanddoesn'tmatter.*LISTSERV determinesmyNJELO5addressfromthecommanditself,soit'snot necessarytoOenterit. POIfanyofthelinksontheBITNETpathtothenodehostingNOtheLISTSERVarenot connected,youwillreceiveamessage,O5forexample:=O%SEND-E-NOTCONNECT,&Link%WISCMAC3%not& connectedn DSOIfalinkisdown,youcanstillsendmailto subscribetoaLOlist.-Your subscriptionrequestwillbe deliveredwhentheMO5communicationslinkcomesbackup.'Intheexampleabove,IOentered: O$MAILO{MAIL>,/{"SEND/NOSELF/NOEDIT/NOCC/SUBJECT="" OTo:zIN%"LISTSERV@BITNIC"]O Enter%your&message%below.&Press&CTRL/Z%when& complete,%or%CTRL/C%to%quit:2OS SUBSCRIBE%LINKFAIL%Stephen%L.%Arnold `i  `kMvCtrl/Z jkM ` NKOIfthelistsareonthesameserver,youentermultipleHO subscriptionsbyentering additional interactivecommands6O5or additionallinesinamailmessage.yOOOAsaBITNET Postmaster,youshould subscribetotheselists:H!  `m@mLINKFAIL@BITNIC, annoucementsaboutnetwork,host,-andserverservice interruptions `EEEJNET-L@BITNIC,a discussiononJoiner'sJnetsoftware `<BITNEWS@BITNIC,newsaboutBITNETforgeneral$and management audiences `:TECHNEWS@BITNIC, technicalnewsaboutBITNET `;NODMGT-L@BITNIC,a discussionofroutingandKtmailertables, protocols,andothermattersofconcernto PostmastersWCO Institutionalrepresentatives, TECHREPs,andINFOREPsKOare automatically subscribedtolists maintainedbyBITNICPO5forpeopleservinginthoseroles.)TherearealsomanyotherKOLISTSERVlistsonamyriadof subjects,whicharebeyondEOthescopeofthisbook.-SeetheTECHREPorINFOREP>O> informationpacketstolearnmoreaboutthese. a@OWhenyou subscribetoaLISTSERVlist,!LISTSERVNO automaticallysendsyouawelcomenotethatexplainshowtoTO5setcertainlistoptionsandhowtosignoffthelist.*ConsiderPOsavingthesenotesinaspecialmailfoldertodocumentwhat/Oliststowhichyou've subscribed.%! OOTosignoffalist,sendtheSIGNOFFcommandtotheserverPOasamessageormail.'Forexample,tosignofftheLINKFAILO5list,Icanenter: O$2SEND%LISTSERV@BITNIC&SIGNOFF%LINKFAIL7O6.7.2B SubscribingtoInternet discussionsHO4AfteryourBITNETlinkis operational,yournodeshave?OappearedinBITEARNNODES,andyourdomainhasIOappearedinDOMAINNAMES,or,if applicable,afteryourJO=Internet connectionis operational,youcanjoinInternetOO discussiongroups.(Thisisnormallyamanualprocess,andisIO initiatedbymailingarequesttothelist coordinator.! WOOBy convention,thelist coordinatorofanInternet discussionWOcanbereachedonthesamenodeasthelistitself,atamailboxQO5namedbyadding ``-Request''tothenameofthelistmailbox.OOForexample,tojointhe discussionofTGV'sMultiNetTCP/IPDO software,Info-MultiNet@TGV.Com,sendyourrequestto(O>Info-MultiNet-Request@TGV.Com.NNOTosignoffofanInternet discussion,sendmailtothe-NORequestmailboxforthelist requestingthatyouberemovedPO5fromthelist.'Donotsendyourrequesttothelistitself.  EOIngeneral,BITNET-oriented discussionsarehostedbyIOLISTSERVservers,buttherearetwoInternet discussionsEO5thatyoushouldjoin:/forPMDFandforyourTCP/IPFO software, ifany.0TojointhePMDF discussion,Info-6OPMDF@Ymir.Claremont.Eduor IPMDF@YMIR(onKO>BITNET),sendyourrequesttoInfo-PMDF-Request@Innosoft.ComGOor RPMDF@YMIR, respectively.(NoticethatthePMDFlistNOdoesnotfollowthe conventionofhavingthe discussionandOOHrequest mailboxesonthesamenode.(Also,donotattempttoDOsendLISTSERVcommandsto RPMDF@YMIR.Notalllists2OonBITNETnodesareLISTSERVlists.h! >OOContactyourTCP/IPsoftwarevendortofindoutifthereisKOanetwork discussionontheproduct.*TheaddressforTGVBO5MultiNetisInfo-MultiNet-Request@TGV.Com.( WollongongBOWIN/TCPis discussedontheLISTSERVlistWINTCP- OL@UBVM.CC.Buffalo.Edu." OOIfyouuse Digital'sTCP/IPsoftwareandhave contractedforLOsoftwaresupport, Digital'sDSNlinksupportnetworkprovidesPO5this function.*Ifyoudonothavesoftwaresupport,youwillLOfind friendly, knowledgeableusersof Digital'sproductsonGO DECUServe,acomputer conferencingservice sponsoredbyMO>theUnitedStateschapteroftheDigital EquipmentComputerIOUsersSociety(DECUS), Digital'susergroup.*PMDF,Jnet,FO third-partyTCP/IP software,ANUNews,andmanyotherHOHproductsandprogramsofinteresttoBITNET PostmastersDOarealso discussedon DECUServe..For informationonJO DECUServe,dial1(800)521-8950withaVTterminalandHORmodem,orTelnettotheInternethostEisner.DECUS.Org,FOandloginwithusername INFORMATION(no password).;# AOBoth Info-PMDFand Info-Multinetare availableasMOnetworknewsgroups.+Ifanewsfeedis justifiedforyourRO5site,youmaywishtoconsider participatinginthe discussions1Ovianewsratherthanthroughmail.q-'`'O7.1.1B AssigningusernamesFO4Whenaddingnewusers,followtheusernamepolicies1Oyou developedwhileworkingthroughChapter3.hIfyouJOmustassignVMSusernameslongerthaneight characters,JO=checkfor conflicts,addaneight-characteraliastotheHOPMDFALIASES.file,and recompileandinstallthePMDFMO configuration(onall VAXclusternodesifyoursystemisaOG VAXcluster).*'OoOm  (`O7.1.2BUsertrainingIO4Your organizationmusthave proceduresfor orientingnewIOusersto computersand networks,tohelpthemlearnofHOpossible applicationsandtocomplywith acceptableuseHO= agreementsand applicablelaws.)TheliasonbetweenCRENNOandtheusersatyour organizationforthispurposeistheBOINFOREP.TheINFOREPpacketshouldcontainstarter%OG informationtohelpyou.)gFOInstructyourusersoncomputerandnetwork security,+Oandpropernetworkbehavior( netiquetteQ)./AnymailHO5usercanfindan immediateaudienceof50,000ormoreSOreadersofasinglelist,andcanbecomeasourceofprideor0O embarrassmenttoyour organization.>* JOExplainthatthenetworksdonot guaranteethe confiden-KOtialityofmailorotherdata,andremindthemtoavoidLO5 compromisingthesecurityoftheirVMSpasswordbysending3OitoverBITNETinaVMSbatchjob.+gJOThereareseveralguidestogood electronicmailmannersHO publishedinbookson networkingand circulatedmonthlyHO5ininternet discussions, including Info-VAX,theVAX/VMSQO discussion.(Oneormoreofthesewillprovideagoodstartingreachedat155Wilson Boulevard,Suite300, ArlingtonVAHO 22209-2405,(703) 875-8620,fax(703) 552-0241,orsend2OInternetmailtoEMA@MCImail.MCI.Com.m $-! O7.2B ConstantlyJOU OperatingaBITNETnodemakesyou responsibleforpromptSOandreliabledeliveryofnetworkdata,notonlytolocalusers,OObuttotheircorrespondentsandtootherswhosenetworkdataIO^mustbe transmittedthroughyoursystem.'TheCRENTermsJOand Conditionsof Membershipand AffiliationrequireyourMO organizationtomonitorthenetworkandrespondtoproblemsOh constantly.. NMOYoumuststrivetomakeyour PrincipalNodeandanyotherKOmajornodes availablearoundtheclock.+ Specifically,yourNO5nodesandthelinkstoadjacentsitesshouldalwaysbeup.!/ )OConsider developingasimplelinemonitor,aprogramLOwhich periodicallychecksforthecorrect configurationandOO5stateofyoursystemandnetworklinks.*IfyoudonothaveLO operatorsondutyatalltimes,youcanprogramthelineROmonitortocallapagerorasecuritydeskwhenit determinesLO>thatthenetworkisdown.+Formoreonline monitors,seeOSection5.4.2.9.*/OZ?S0oHOSomeofthethingsanoperatororlinemonitorshould'O periodicallycheckinclude:1! 5 `m3mArealllinksintheConnectstate? `RDolinkqueuecountsgobacktozeroafterafileisqueued? `lGlAredatalinkordeviceerrorcounters increasingtooquickly? `DGDIsthereenoughdiskspaceon importantdiskdevices? `LAretrafficcounters increasingattheusualrateforthetimeofday?Q2'LOInadditiontoNJE software, operatorsormonitorprogramsGOshouldcheckforfailuresinthe underlying networkingEO5software(forexample,TCP/IPor DECnet-VAX software)OOandif possible,monitorthe conditionofthesystemitself.4! ~(O7.3.1BReviewJANTIDYoutput@O4IfyouruntheJANTIDY management procedure,asO suggestedinSection5.4.2.9,.8youwillhavemaileachmorningJOfromtheJANTIDYrunoneachofyourVAXBITNETnodes.JO=Revieweachofthesemailmessagesforproblem symptoms,"Othendeletethemail.*4O?S^D5 j9O7.3.2BDisposeoffilessentto POSTMASTERCO4JANTIDY warns!you if there are any files for theIO POSTMASTERtoreceive.*MostoftheseweresenttouserLOnamesthatdonotexistonyoursystem.+ExaminethefileMO=tagdatawithJnet'sRECEIVEutility,eitherbyloggingin,Oas POSTMASTERorbyusingthe./USER=POSTMASTER qualifierJOfroma privilegedaccount.,Youmaybeableto determineNOGtheuserforwhomthefilewasintendedandsenditalongOwith RECEIVE's!FORWARD/ORIGINAL/NOKEEP9command.(Donot,TOhowever,reviewthefile contents.&Todosowouldbetoviolate!OQthesender'sprivacy.6! +O7.3.3BReadmailto POSTMASTERAO4As! Postmaster,"you should!read mail addressed toHO POSTMASTERorPOSTMASTasitarrives.'YoucandothisRObylogginginas POSTMASTER,butitiseasiertodelegatetheIO= Postmasterdutiesby forwarding POSTMASTER'smailtotheKOpersonalaccountofthe individual currentlyon PostmasterOduty.7! e@OPMDFandmostothermail softwarereturn entireJO undeliveredmailmessagesbacktothesenderor,iftheHO5sendercannotbereached,tothe Postmaster.+PMDFalso2Osends, optionallyandbydefault,a copy$ofbouncedmailtotheROlocal Postmaster.&ThisplacesaburdenofconfidentiallyontheMO> Postmaster.)UseyourbestefforttoavoidreadinganymoreLOofamailmessagethan necessarytodiagnoseanyproblemsDOandsendthemessageontotheproper destination.78  4OIfyoufollowedtherecommendationinSection6.3.3toset OtheSENDHEAD9 channelkeyword(inPMDFV4.0,renamedtoO5 POSTHEADONLYB*5inPMDFV4.1)asadefaultforall channels,itOOismucheasiertomaintaintheprivacyofmail,becausetheOOtextofatleastsome undeliverablemessagesisnotsentto(O>the Postmaster.*SettingtheA> HEADERBOTTOM>channelkeywordPOasthedefaultmakesprivacy especially difficultto maintain,PObecausethe PostmastermustscrollthroughtheentiretextofMOHreturnedmessagestogettotheheadersneededtodiagnoseOdelivery failures.*8F?b9! -O7.3.4BCheckPMDFchannelqueuesAO4CheckPMDFchannelqueuesdailywithPMDF'sQmanEOcommand procedure.*Exceptonverybusysystems,PMDFQOqueuesshouldusuallybeempty,orcontainmailthathasbeenTO=heldonlyashorttime.'IfmailbeginstobuildupormessagesPOare remainingonqueueformorethanahalfday, investigate/Othecauseofthedeliverydelay.G: $OUsedQmantocheckforheld messages./PMDFputs>OmessagesonholdifitfindsmorethanfortyReceivedlines,asKO5aloop-preventionmeasure.' OperatorscanalsoputmessagesOonhold manually.;V]+O7.3.5BCheckPMDFbatchqueuesIO4Eachday,checkthatthePMDFbatchqueuesaredefinedNOandstarted,thatthemessagebounceranddeliveryjobsareLOholdinguntiltheirnext regularly scheduledruntime,andOO=thatanyotherjobsare executingandsoonleavethequeue.}<S5O7.3.6BReadrelevantnetwork discussionsJO4Readthenetwork discussionandLISTSERVlists pertaining?OtoBITNET, includingJNET-L, Info-PMDF,TECHREP,?O TECHNEWS,BITNEWS, LINKFAIL,andrelevantTCP/IPEO=lists.1IfyouhavenetworknewsfeedsorVAXNotesIO conferencesonBITNET-relatedtopics,monitorthosedailyOOaswell.)Trytoanswer questionsaboutyoursiteforremoteQOGusersandaboutthenetworksforlocalusers,andtrytorun(Odownanyreported problems.V}>! VS/O7.4.1BInstallJnetroutingtablesPO4ReceiveJnetroutingtableswhentheyarriveatthe beginningLOofeachmonth.)Compareeachtabletothepreviousmonth'sSOtablestocheckfor corruption,changesinformat,orerrorsby5O=theserversin generatingyourtables.?W@OMovethetablesintoJAN_SPECIFIC:[SYS](orJAN_CO COMMON:[SYS]ifJnetclustermembersshareacopy)EO5whereJANTIDYwillinstallthemonitsnextmorningFOrun.0YoucanalsouseJANTIDYtoinstallnewtablesEO immediatelyby releasingthequeuedJANTIDYjobwithO>theDCLcommand>SET ENTRY/RELEASE >.@ &O7.4.2BBuildmailertables8O4WhenbothDOMAINNAMESandXMAILERNAMES'Ohavearrivedforamonth,"RECEIVEEthemintoPMDF_IO ROOT:[TABLE],inspectthemforcorrectformatanddamageAO=intransit,andruntheBITNET_DOMAINS_DRIVERandAOCOMPILE_INSTALL procedurestogenerateandinstall1Onewmailertables,as describedin0Section6.3.6.2. bTheDOG recommended procedure automaticallyrestartstheJnetQOlocalmaildeliveryprocesssothatthenewmailertablesare/O availabletorouteincomingmail.*@0?9XA .,O7.5BWhenchangingsystemclockPOUIfyouchangeyoursystemclocktoanewtimezone,becauseMOofthe observationofdaylighttime,forexample,youmustHOinformanysoftwarethatneedstoknowthetimezone.IO^Theseareusuallyproductsthatusewidearea networks,IOandincludePMDF,Jnet,MessageRouter,TCP/IP software,JOALL-IN-1andothermailuseragents,andMessageRouter.AOhSeethePMDFandJnet documentationfordetails.zB! PUOIfyouobservedaylighttimeinyourlocalityandifyourpolicyPOistochangethesystemclocktoconformtolocaltime,youOO5willhavetochangealloftheseproductstwiceayear.,AsJO alternatives,considerrunningyoursystemclockonlocalGOstandardtime(or UniversalTime)allyeararoundandGO>lettingusersmakethe necessarymental adjustment,orLOdevelopadaylighttimecommand procedurethatchangesall8Oyourtime-zone-sensitiveproductsatonce.MC#HOYoucanalso encourageyoursoftwarevendorstomodifyMOtheirproductstoacceptboththetimeandtimezonefromIO5anexternalsource, preferablytheInternetNetworkTimeEOProtocol(NTP)or Digital's DistributedTimeService.E Vk8O7.6.1BUpdateJnetandPMDFconfigurationsKO4UpdateyourPMDFand/orJnet configurationtoreflectanyNOchangesinyoursystemornetworkconfiguration.(IfyouuseLOacompiledconfiguration, recompileyour configurationafterNO=makinganychangetothePMDF configurationoraliasfiles.Fa?O7.6.2BModifysoftwarewhenSCSNODEnameschangeJO4If SCS/DECnetnodenameschange,reviewJnet directories,AOPMDF configurationfiles,PMDFqueuenames,queueIOinitializations,andthe definitionofJnet's JAN_MASTER_GO=NODElogicalname,aswellasanyother configuration@O parameter dependentonthe DECnet-VAXorSCSNODELOnameofyoursystem.+FindingallthethingsthatmustbeDOGchangedifyouchangeyourSCSNODEandDECnetnode7Onamesisbeyondthescopeofthebook.^G 4?O7.6.3BAdjustqueueswhen upgradingtoVMSV5.5JO4When upgradingtoVMSV5.5,editJAN_SYS:JANSITECOMMON.COMJOtocommentouttheinitializationofanyqueuesforNJEIO symbionts.+UnderVMSV5.5andlater versions,queuesdoNO=notneedtobe initializedeachtimethesystemisbooted.IOUnderVMSV5.5andlater,attemptsto initializequeues8OwhenstartingJnetresultinthemessageIOs%JBC-I-QUENOTMOD,% modifications&not%made&to&running%queueHzDOfor each queue (after the first attempt).3For moreO information,seeSection5.4.2.7.*H?GCI! 5OIfyoufollowedtherecommendationsinSection6.2.3tocreate9Othecommand procedureSYS$STARTUP:PMDF_INIT_CO5 QUEUES.COMto initializePMDFqueuesateachboot,IOyoumustdisablethiscommand procedureaswell.+Either=OcommentoutthelineinSYS$MANAGER:SYSTARTUP_KO>V5.COMthatstartsthe procedure,orremovethe procedureCOfromtheSYSMANSTARTUP database, dependingonhow(Oyou initiallysetupPMDF.*IF? J 1O7.6.4BRespondtomailfromNETSERVFO4Fora descriptionoftheNETSERVnetworkserver,seeOSection3.4.7.3.9vForfurther informationonNETSERV,obtainCOthefileNETSERVINFOfromLISTSERV@BITNIC,orthe?O=filesNETSERVREFCARDandNETSERVHELPFILEfrom4OthenearestNETSERVorNETSERV@BITNIC.*JOO?KWDONETSERVuses passwordstocontrolaccesstocertainMO privilegedserver functions,suchthefetchingof restrictedFO5files.0Althoughthese functionsarenotnormallyused Obynodeadministrators&(NADs)whose organizationsHOareservedbyBITNIC,NADsshouldkeeptrackoftheir:O>NETSERV passwordsincasetheyareneeded.WL->OWhenanew nodeis createdinBITEARN NODES,@ONETSERV automaticallyassignstheNADapasswordHO5andsendsthepasswordtotheNADby electronicmail.4O(NETSERV recognizesthepersononthe:USERADM_tagasthePOnode administrator(NAD).Ifthattagdoesnotexistituses O>the>:ADMIN=>tag.)+NADscanalsonominateother privilegedEONETSERVusers,whointurngettheir passwordsfromONETSERVbymail.-MFOIfyoureceiveaNETSERVpasswordbymail,savetheIOmessage,withthepasswordandtheserveraddress,withMO5your importantBITNETmailwhereyouwillbeabletofind'Oitayearormorelater.NNCONETSERV passwordsexpireafteracertainnumberofDOmonthsandmustbechanged.*TochangeyourNETSERV9O5passwordyoumustknowitscurrentvalue.O! ]FOIfyoureceivemailfromNETSERV requestingthatyouKOchangeyour password,getoutthemailfromNETSERVwithHO5yourNETSERVpasswordfromsafekeepinganduseittoROpickanewone accordingtothe instructionsthatcameinthe2Omail requestingthepasswordchange.P! aGOIfyoucannotrememberyourNETSERV password,youcan Orequestitfromthe controller#(thehumanmanager)ofJO5theNETSERVserverthatservicesyournode.*TofindoutGOtheaddressoftheNETSERV controllerofanyNETSERV,OsendaSQUERY CONTROLLER)commandtothatNETSERV.ToAO>findoutwhichNETSERVservesyournode,senda>QUERYOSERVICE>mcommandtoNETSERV@BITNIC,anditwillrespondIOwithvarious informationabouttheNETSERVservicearea,MOH includingthenodeoftheNETSERVthatservicesyournode.fLQ! A"=O A.!Adding!an"Internet" Connection"to!a"BITNETOrNode _UNote _C{Thisappendixisadraft,andserves primarilytoJprovideanoutlineformaterialforafutureeditionofC-thisbook.*Your experiencesandother contributionsCarewelcome.+TosubmitmaterialorideasforthisB appendix,followthe instructionsonthe copyright*6pagefor submitting comments. COThisappendix doesnot attempt toprovide completeROw instructionsfor connectingtothe Internet.'Instead,itfocusesMOonthosetasksrequiredofBITNETsitestomaintainBITNETJO(serviceswhileaddingthe complementaryInternet services.:R/OA.1C AssumptionsforthisappendixJOUThisappendixassumesthatyoursystemisonBITNETandTOrunsamailer,as describedinthefirstsevenchaptersofthisLO document.)In particular,Iassumethatyouhave registeredMO^adomainnameforyoursystem,eitherdirectlythroughthe4ODDNNICor indirectlythroughBITNIC.\S2ROIfyouhavenot completedthetasksinthemainpartofthisKObook,workthroughthebookfromthe beginning, followingLO5the instructionsfor implementinganInternet connectionasIOwellasaBITNET connection.'Donotusethis appendix.{T! >OA.2CObtainanetworknumberfromtheDDNNIC?OUCompletetheInternetnumber template, INTERNET-betterservedby commercialIPservice providers,unlesstheirNObusinessisstrictlyserving governmentandhigher education._X55OAlsoreviewpricesandother policies.F,Y wDOA.4CJoina consortiumorarrangefor commercialIP(serviceOOSelectthemost applicableserviceor consortiumandcompleteLOtheadministrativestepsthatare prerequisiteto obtainingO^service.hZ! w>/OA.5CInstallaphysical connectionHOUArrangefortelecommunicationslinesanddata communica-JOtions equipment.' Sometimesthese arrangementsaremadebyMOthe consortiumorservice provider.(Connectyourlocalarea0O^networktothe wide-area backbone.[wW8OA.6CInstalland configureTCP/IPsoftwareIOUObtainlicensesandmediaforTCP/IP software.+ AvailableHOsoftwarerangesfromrobustand full-featured commercialEOproductsto inexpensiveorfreesoftwareprovidedbyIO^ universitiesorbysystemvendorprogramsfor education.V\,,OInstallandtestthe software..C] *OA.7CArrangefornameserviceIOUWhenyouconnectyour organizationtothe Internet,youGOmustprovideprimarynameserviceforyourdomainandMOarrangeforanotherInternethosttoprovide secondarynameMO^service.'Thehost(s) providing secondarynameserviceshouldIObegeographicallyand logicallyremotefromyourprimaryJOnameserver.*Often secondarynameserviceisprovidedby2Ohyour consortiumorservice provider.^ WMOIfyou advertisemail exchanger(MX)recordstotheDomainGONameService(DNS),theyshouldbehigherpriorityMXJO5recordsthanthose advertisedforyourdomainbyHarvardNOand Berkeley,sothatmailfromotherInternetsitesstartsKOcomingtoyoudirectly immediatelyratherthancomingvia0O>INTERBITmailgatewaysandBITNET.V<_(OA.8C ReconfigureyourMAILERBOURerunthePMDFautoconfiguration proceduretotakeGO advantageofyourInternetlinkformail.-ComparetheEO automatically generated configurationwiththeBITNET-GO^only configurationyouhavebeenusing,andmakesureNOyou understandthereasonforallthe differences.(CopyanyMOneededcustomizationsfromtheold configurationtothenew:Ohone.'Testthenew configuration thoroughly.$`! $OA.9CUpdateDOMAINNAMESMOUWhenyournameserviceis operational,changethevalueof Othe:SERVED&taginDOMAINNAMESfrom iYES to JNO.ThiswillHOcauseBITNICtoremovethemail exchanger(MX)recordsKO^fromthenameserversatHarvardandBerkeleythatpoint3OyourmailtoINTERBITmail gateways.'a LOWhenyouaddanInternet connectiontoaBITNETnode,ifNOallthehostsinyourdomainarenowdirectly connectedtoLO5the Internet,orcanreceiveInternetmailviaMXrecordsIO(otherthanMXrecordsservedbyHarvardand Berkeley),2Oyoushouldchangethevalueofthe_ :INTERCONNECTataginO>DOMAINNAMESfrom >NO M>to >YES 5>or >MX >, respectively.*ThisHOwillallowotherdual-connectedBITNET-InternetsitestoPOroutemailtoyourdomainoverInternetiftheyprefer.(MailLOH addressedtoyourBITNETaddresswillcontinuetocomeinOviaBITNET.b NIORequestallchangestoDOMAINNAMESbysendingmailtoFODOMAINS@BITNIC.ExplainthereasonforthechangeandIO5requestthenewvaluesyouneedforanyaffectedtags. Dc(OA.10CAdjustBITNETtopologyLOUWhenyourInternet connectionisstable,consider switchingDOyourBITNETlinkfromBSCtoTCPNJE.RetainyourLOBSClineasabackupunlessthefundingofyourInternetNO^ connectionistotallyunderthecontrolofyour organizationNOandthelineitselfprovesreliableforseveralmonths.,YouKOwillbenefitfromhigher throughput, redundancy,andfewer/OhBITNEThopstomostothersites.dLOIfyouchoosetodropyourBSC connection,youwillalso5Orealizetelecommunicationscostsavings.ne/OA.11CTrainusersonnewservicesJOUUsersneedtobetrainedonthenewservices available,GO includingFTPandTELNET.ContinuetoprovidetrainingEOon complementaryservicesuniquetoBITNET, includingEO^ interactivecommandsand messages, LISTSERV,SENDandEORECEIVEforfile transfer,andremotebatchservice.f qJOIfyourmailerwasproperly configuredbeforeaddingtheNOInternet connection,theonlychangeendusersshouldnoticeQO5in electronicmailserviceisfasterdeliveryandthelostofPO``file progress''messagesforsome addressees.'Mailshouldno8OlongergothroughINTERBITmail gateways.O5g  0OA.12CSwitchtoInternetNewsfeedIOUIfyouhavebeen receivinganewsfeedoverBITNETorMOUUCP,considermovingthefeedtoTCP/IP protocolstotakeEO advantageofhigherspeedlinesandpath redundancy.j9OB.1CMailgatewaystodomainswithmailersKOUThissectioncoverstwocommon situations.*YoursystemorGO VAXclusterprovidesamailgatewaybetweenBITNETand:k ^A`m1.:otherVAXsystemsrunningPMDF,viaaDECnetnetwork,and/orL`E2.:otherhostsrunningSMTP,overalocalTCP/IPnetwork.9lMOInthesecond situation,IpresumethattheTCP/IPnetworkOOisnot connectedtothe Internet.)IftheTCP/IPsystemsareNO5 connectedtothe Internet,thenusethe instructionsinthe%Omainpartofthisbook.m WLOThegatewayfunctionrequiresamaileroneachsystemforNOwhichyoursystemwillacceptmail.,Inthefirstcase,theKO5mailerfunctionisprovidedbyPMDF;inthesecondcase,FOSMTP software,suchastheSMTPmailerprovidedwithOMultiNetorthe sendmail-  componentoftheUNIX operating3O>system,providesthemailer function.n MOAssignadomainnameinyourorganization'sdomaintoeach9OTCP/IPhostorDECnetnodetobeserved.o _KOUsingthe instructionsprovidedinthePMDFdocumentation,?O configureaSMTP-over-DECnetorSMTPchanneltoIO5connecttothe non-BITNETsystems.*AddrewriterulestoNOyourPMDF configurationfiletoroutemailreceivedbyyour>OsystemfromBITNETtothe appropriatechannel.pWIODonotattempttosetupNJEnodenamesforthenon-IOBITNETnodes.)Ifyoudo,remoteBITNETuserswillthenFO5expectthe non-BITNETsystemstosupportotherBITNETHO applications,suchas interactivemessagesandNJEfileJO transfer.+Allmailtothe non-BITNETnodesshouldgotoO>theirdomainnames.<q! <y@OB.2C Providingnameservicefor connecteddomainsHOUIfyoursystemwillbeadomainnameserver,considerKO providingnameserviceforany BITNET-only(thatis,non-GO Internet)nodes reachablethroughyour organization.,ToHO^providenameservicefor BITNET-onlynodes,yoursystemLOwill advertisemailexchange(MX)recordspointingtoyourCOorganization'sBITNET-InternetmailgatewaytootherEOhserversintheDomainNameSystem.*WhenyourdomainHOnameserverandyourorganization'sBITNET-InternetmailJOgatewayare operational,InternetusersanywherecansendMOrmailtodomain addressesofthe BITNET-onlynodesthatcanGObereachedthroughtheBITNET-InternetmailgatewayatO#your organization.r MOAnexamplemayservetoclarifythisconfiguration.(SupposeOOyour organizationisBayCollege,the hypothetical institutionO5 describedin5Section3.5,+5andthatAcme CorporationhasCO registeredthedomainAcme.Comfora VAXclusteron?OBITNET connectedtoyourBITNEThubBAYACB.IfEO>you configureaBITNET-InternetmailgatewayonyourHO VAXclusterBAYACA(alsocalled Aca.Bay.Edu)thatacceptsLOmailfortheAcme.ComdomainandprovidenameserviceforJOHtheAcme.Comdomain,anyInternetusercansendmailtoOAcmemailboxes.*r~?us! KIOForfurther informationon providingdomainnameserviceJOforotherdomains,seethe documentationforyourdomainNO5nameserversoftware(usuallypartofyourTCP/IP software).JOThe configurationofdomainnamesserversisoutsidethe Oscopeofthisbook.(t X5OB.3C OperatinganINTERBITmailgatewayJOUThe requirementsfor operationofanINTERBITgatewayonHOaVAXsystemrunningVMShavenotyetbeen clarified,EOasallofficialINTERBIThosts currentlyruntheVMGO^ operatingsystem.'TheCRENrulesforINTERBITgatewaysBOareinthefileINTERBIT STANDARD, availablefromAOLISTSERV@BITNIC. DiscussionofINTERBIT operationalPOhissuesoccursonaLISTSERVlistthatclosedto subscriptions2OfromtheBITNET communityatlarge.ubPOAnattemptwillbemadetocompetethissectioninafutureOedition.})INDEXINDEX!i  iAAKS9addingBITNETnodesadding BITNET nodesv3J88address rewriting,mail,byINTERBITmail-gatewaysaddress rewriting, mail, by INTERBIT mail gateways@1S  8AFDAFD:-S9aliasesaliases5S N8 duplicateduplicate7S 8ALIASES.ALIASES.<S 9aliasesfilealiases file3S 8ALL-IN-1ALL-IN-1V8S N8usernamesuser names<S 9analoglinesanalog lines4S 9ANUNewsANU NewsPS!!8 Application System/400Application System/400fS!--8ArizonaState UniversityexampleArizona State University exampleIS9Arnold,StephenL.Arnold, Stephen L.FS8Arnold ConsultingArnold ConsultingsS%%8Arnold ConsultingexampleArnold Consulting example|1S9ASU.EduASU.EdufS++8 autoansweroptionof VMSINSTALautoanswer option of VMSINSTALRS""8autoconfigurationfilesautoconfiguration filesWS%%9AUTOGENcommand procedureAUTOGEN command procedurecS''8 automaticfile distributionautomatic file distribution:BS8 automaticrepliesautomatic repliesMS  N9to POSTMASTER'smailto POSTMASTER's mailDS8 autostartqueuesautostart queues;S 8 availabilityavailability-!i  iBBDS9BACKUPutilityBACKUP utility >S8batch,remotebatch, remoteJS  8 batch/print subsystembatch/print subsystemLS  N9useofSCSNODEnameuse of SCSNODE name:S 8batchqueuebatch queue<S 8batchserverbatch servermS$119BatchSimpleMailTransferProtocolBatch Simple Mail Transfer Protocol*OS8BayCollegeexampleBay College examplekS"--8binary synchronouscommunicationsbinary synchronous communications jS 8BITEARNNODESBITEARN NODES0:c MS  N9monthlyupdatecyclemonthly update cycleDSN8update procedureupdate procedurec/S8BITNETBITNET ^S))N9accessbyterminal emulationaccess by terminal emulation<S N8addingnodesadding nodesv3S N8benefitsbenefitsSS##N9choosingBITNETsystemschoosing BITNET systemsDSN8 continuingcostscontinuing costs =SN8 disconnectiondisconnectionO>SN9initialcostsinitial costs 9S  N9initiallinkstartupY>SN8mailconceptsmail concepts0-SN8namesnamesxFSN9node registrationnode registrationa9S N8 performanceperformance SS##N8planningexternallinksplanning external linksSS##N9planninginternallinksplanning internal linksSS##N8planninglink protocolsplanning link protocols WS%%N8planning VAXclusterlinksplanning VAXcluster links BSN9 PrincipalNodesPrincipal Nodes@SN8routingtablesrouting tablesFSN8topologyplanningtopology planning3S N8 transportstransports;S 9 installationinstallation>S8BITNET-2INFOBITNET-2 INFO<S 8BITNETGATESBITNET GATESC2S 9BITNETIIBITNET II+SN8corecoreAS8BITNETIIcoreBITNET II coreIS9BITNETIIprotocolBITNET II protocolKS8BITNETmailgatewayBITNET mail gatewayUS$$8BITNETnode registrationBITNET node registrationJS9 BITNET_QUEUEsymbolBITNET_QUEUE symbolKS8BITNICBITNIC0;>bz+S8blanksblanks?SN9inusernamesin user names3S 8boldfaceboldface%7S 8 BookreaderBookreader-SN9setupsetupQS""8BostonCollegeexampleBoston College example -S  8BSCBSC 9S9BSMTPBSMTP*2:3S N8envelopeenvelope5@S8BSMTPADDENDUMBSMTP ADDENDUM@!i  iCCUM&&3CarnegieMellon UniversityCarnegie Mellon UniversityEMN3seeCMU-TEKIP/TCPsee CMU-TEK IP/TCP-S8channelchannel1SN9keywordkeywordaS**8 ClusterWidesoftware licensingClusterWide software licensingDS8CMU-TEKIP/TCPCMU-TEK IP/TCPANS  9 commands, interactivecommands, interactive3S 8commentscommentsPS!!8compiled configurationcompiled configuration]S((8compiledconfiguration,PMDFcompiled configuration, PMDF/S 9conceptsconcepts:S N8BITNETmailBITNET mail0;S 8 conferencingconferencing]S((9 CONFIG.COMcommand procedureCONFIG.COM command procedure=S8 configurationconfiguration'[S''9 CONFIGUREcommand procedureCONFIGURE command procedure]S((8 configuringnetworksoftwareconfiguring network software<S 8:CONNECTtag:CONNECT tag9S 9 conventionsconventions$5S 8 copyrightcopyright4J)8 CorporationforResearchand!- Educational NetworkingCorporation for Research and Educational Networking+S9CRENCRENGSN8BoardofTrusteesBoard of Trustees-+SN8duesduesp7S N9 membershipmembershipp?SN8recommendationrecommendationASN8representativesrepresentativesp?S N9 requirementsrequirements=]S((N8 TechnicalAdvisory CommitteeTechnical Advisory Committee-MS  N8termsand conditionsterms and conditions=<S 9CRENTERMSCREN TERMS=!i  jDDQS""8daily managementtasksdaily management tasks3WS%%8 DataphoneDigitalServiceDataphone Digital Service>S9daylighttimedaylight timeA4S 8DCLtablesDCL tables5S N8 replacingreplacing:S9DDNNICDDN NICBSN8documentserverdocument server+S8DECnetDECnet-SN9namesnamesy1SN8networknetworkX3S N8networksnetworks3S N8softwaresoftware]8S 9DECnetaliasDECnet alias-SN8namesnamesy<S8DECnetobjectsDECnet objectsHSN9forDNANJElinksfor DNA NJE linksV;S 8 DECnet-VAXDECnet-VAX=SN8 configurationconfiguration-SN9namesnames}3S N8softwaresoftware`1SN8startupstartupLS  N9useofSCSNODEnameuse of SCSNODE name3S N8versionsversionsRS  8 DECnet-VAX ExtensionsDECnet-VAX ExtensionsLS!!9 DECnet-VAX ExtentsionsDECnet-VAX Extentsions=SN8 configurationconfiguration-S8DECUSDECUS"5S 9 DECUServeDECUServe">S8DECUSexampleDECUS exampleocS##8DECUS SymposiumexampleDECUS Symposium example~;S""8 DECW$BOOKlogicalnameMS!!9DECW$PRIVATE_APPS_SETUPDECW$PRIVATE_APPS_SETUPFSN8command procedurecommand procedure3S 8 DECwindowsDECwindows1SN9startupstartupLS  N8useofSCSNODEnameuse of SCSNODE nameBS8defaultchanneldefault channelMS  9DefenseDataNetworkDefense Data Network3S 8 delegationdelegation7S N8 PostmasterPostmasterDS9DELIVERfacilityDELIVER facilityDS8DELIVERYutilityDELIVERY utility8S 8devicenamesdevice namesLS  N8useofSCSNODEnameuse of SCSNODE name>S9dial-uplinesdial-up lines1S8DigitalDigital cS))8Digital Equipment CorporationDigital Equipment Corporation!US$$9directmail transmissiondirect mail transmission*LS8 directoryservicesdirectory servicesP\S((8direct transmissionofmaildirect transmission of mail*7S 9 disclaimerdisclaimerPS""8DISKDUMPfileformatDISK DUMP file format:S 8diskquotasdisk quotas<S 9DISMAILflagDISMAIL flagUS$$8 DistributedNameServiceDistributed Name Service-SN8namesnamesy?S9DNANJElinksDNA NJE linksV)S  8DNSDNS=S8 documentationdocumentationLS9document conventionsdocument conventions$iS#..8 documentingsoftware installationsdocumenting software installations+S8domaindomain-SN9namesnames;S N8 registrationregistration[S''8domain applicationtemplatedomain application templateLS 9DOMAINGUIDEDOMAIN GUIDE>S 8domainnamedomain nameVg7S N8 registeredregistered;S N9 registrationregistration<S 8domainnamesdomain namesx\S 8DOMAINNAMESDOMAIN NAMES;@IS9domainnamesystemdomain name system@S8DO_CRDBsymbolDO_CRDB symbol1S8DSNlinkDSNlink"LS  N8useofSCSNODEnameuse of SCSNODE nameDS9DSNlinksoftwareDSNlink software~1S8DSU/CSUDSU/CSU!i  iEE+S8EARN0;JSN8traffic requirementtraffic requirementG[S''9 ElectronicMail AssociationElectronic Mail Association,)S  8EMAEMA,@S8ExcelanTCP/IPExcelan TCP/IP!i  iFF5S 9 facsimilefacsimileP)S  8faxfaxP<S 8:FFORMATtag:FFORMAT tag<S 9fileformatsfile formatsOS!!8fileprogressmessagefile progress messageNS!!8filequeuingbysizefile queuing by sizeA:S 9fileserverfile serverP>S8filetransferfile transfer<S 8FILEutilityFILE utilityAUS$$9FORTRANcarriagecontrolFORTRAN carriage controlA>S8 forwardingmailforwarding mail8S N8forMAILERfor MAILER6S N9forMAINTfor MAINT@SN8for POSTMASTERfor POSTMASTER4S N8forROOTfor ROOT<S N8forSMTPUSERfor SMTPUSER8S N9forSYSTEMfor SYSTEMVS%%8 forwardingmailtolistsforwarding mail to listsP+S8FQDNFQDN3MS9fullmeshtopologyfull mesh topology IS8FUSIONforVAX/VMSFUSION for VAX/VMSPS""8FUSIONTCP/IPforVMSFUSION TCP/IP for VMSA!i  iGG>S9 :GATEMASTtag:GATEMAST tagDS8GATEWAYSTANDARDGATEWAY STANDARDCHS8Giese, Hans-UlrichGiese, Hans-Ulrich1S9GMAILGMAILE~JS8group communicationgroup communication>S8guestaccountguest account@S9guestaccountsguest accounts!i  jHH/S9%-hack%-hackMaS((8 HEADERBOTTOMchannelkeywordHEADERBOTTOM channel keyword8YS&&8 HEADEROMITchannelkeywordHEADEROMIT channel keyword:S9headers,mailheaders, mail5S N8 excessiveexcessive>S8heldmessagesheld messages:TS##9 heterogeneous VAXclusterheterogeneous VAXclusterXPS!!8 homogeneous VAXclusterhomogeneous VAXclusterX7S N8 definitiondefinition+S9hopshops+S8hosthost8S 8hostaliashost alias7S 8 HostmasterHostmaster!i  iII)S  8IBMIBMSS##9IBMnational charactersIBM national characters+@/8Indiana Universityof Pennsylvania-exampleIndiana University of Pennsylvania example=S8 Info-MultiNetInfo-MultiNet#9S 9 Info-PMDFInfo-PMDF#1S8INFOREPINFOREPpZS''8initialNJEroutingtablesinitial NJE routing tables\eS((9InnosoftInternational,Inc.Innosoft International, Inc.;S 8 installationinstallation'[S''8 installingnetworksoftwareinstalling network softwareo"5"8INSTALL_COMPILEcommand- procedureINSTALL_COMPILE command procedureWS!!8INTERBITmailgatewayINTERBIT mail gateway7@QS""8INTERBITmailgatewaysINTERBIT mail gateways-FS9 :INTERCONNECTtag:INTERCONNECT tag3S 8 interfacesinterfaces9S N8 synchronoussynchronous?S 9InternetInternet,7;y%<.N8addinga connectiontoaBITNETnodeadding a connection to a BITNET nodeQ7S N8 connectionconnectionXYS&&9Internet discussiongroupsInternet discussion groups PS8Internet discussionsInternet discussions<FS8InternetProtocolInternet Protocol>S9 :INTERNETtag:INTERNET tag8S 8IPaddressIP address/S8italicitalic%1S8IUP.EduIUP.Edu!i  iJJ[S''9 JANCONFIGcommand procedureJANCONFIG command procedure)?S 8 JANLINKS.JCPJANLINKS.JCP4>5S 8 JANLOAD.COMJANLOAD.COMTS$$N9sharingina VAXclustersharing in a VAXclusterEAS8 JANROUTES.JCPJANROUTES.JCPD\cS ++8 JANSITECOMMONcommand procedureJANSITECOMMON command procedureG;S 9 JANSTART.JCPJANSTART.JCP>9S 8 JANTIDY.COMJANTIDY.COMI_S%%8JANTIDYcommand procedureJANTIDY command procedureS34_S))9JAN_SYSTEM_FLAGSlogicalnameJAN_SYSTEM_FLAGS logical nameG)S  8JESJES?S8JnetJnet5VESN9autoconfigurationautoconfiguration)GS8JnetclusternameJnet cluster name/>S8localserverslocal servers4<S 9networksizenetwork size.6S 8timezonetime zone0TS$$N8batchandprintserversbatch and print servers7ASN9 configurationconfiguration(t$8%N9device connectioncommand proceduredevice connection command procedureE=SN9 documentationdocumentation>SN8filelocationfile locationMS  N8initiallinkstartupinitial link startupYCS N9 installationinstallationb@S8on VAXclusterson VAXclusters%OS!!8optionallinkdriversoptional link drivers&WS%%N9link definition procedurelink definition procedure>MS  N8link parameterfileslink parameter filesUQS""N8linkstartup procedurelink startup procedure>`S**N9localmaildelivery procedurelocal mail delivery procedureRSS##N8logincommand procedurelogin command procedure;SS##N8nightlyclean procedurenightly clean procedureSESN8postconfigurationpostconfiguration8BSN9RECEIVEutilityRECEIVE utility5YS&&N8route definition procedureroute definition procedureD<SN8routingtablesrouting tables;S 9 installationinstallation>/S N8securitysecurity<S 8batchserverbatch server6z';(N8 site-specificcommonstartup proceduresite-specific common startup procedureG1SN8startupstartupFSN8startup procedurestartup procedureLS  N9useofSCSNODEnameuse of SCSNODE nameRS##N8useofTCP/IPsoftwareuse of TCP/IP software3S N8versionsversions<S 9JnetBSC/370Jnet BSC/3708S 8JnetclusterJnet cluster+SN8namename-SN9namesnamesy:S8JnetclustersJnet clusters3S N8messagesmessagesK8S 9JnetsectionJnet sectionUS$$N8globalpage requirementsglobal page requirements/AS 8JnetTCPNJEJnet TCP NJE?aS**9 JNET_STARTUPcommand procedureJNET_STARTUP command procedure-S  8JOBJOB[S!!8Joiner Software,Inc.Joiner Software, Inc.!i  iKK<S 9KnoxexampleKnox example!i  iLL)S  9LATLATWcS ++8 LAT$SYSTARTUPcommand procedureLAT$SYSTARTUP command procedureWOS!!8LATstartup procedureLAT startup procedureW@S9layeredproductslayered productsLS  N8useofSCSNODEnameuse of SCSNODE name1S8licenselicense[S''9License ManagementFacilityLicense Management Facility~9S  N9useofSCSNODEname@S 8linemonitorline monitorT/MS  8link parameterfileslink parameter filesU@S9link protocolslink protocols 8S 8links,NJElinks, NJE8S 8:LINKStag:LINKS tagcS 9LISTSERVLISTSERV=COe CSN8AFDADDcommandAFD ADD command>S N8GETcommandGET command>-SN9listslists<=SN8 subscriptionssubscriptions5S8LMD.COMLMD.COMWS%%9LMD.COMcommand procedureLMD.COM command procedureRMS  8LocalArea TransportLocal Area TransportWSS##8LOGGINGchannelkeywordLOGGING channel keywordBS8login directorylogin directory]S((9 LONG_NAMEScommand procedureLONG_NAMES command procedure!i  iMM<S 8:MACHINEtag:MACHINE tag>S8Madison,MattMadison, Matt@+S9mailmail US""8 MAIL$BATCHbatchqueueMAIL$BATCH batch queueaS**8MAIL$SYSTEM_FLAGSlogicalnameMAIL$SYSTEM_FLAGS logical nameOS!!9mail concepts,BITNETmail concepts, BITNET03S8mailermailer )3S N8benefitsbenefitsH7S N9 definitiondefinition2>SN8externalviewexternal view?S N8 installationinstallationg;S N9 registrationregistration/SN8tablestables:;S8MAILERMAILER<S 9mailerfilesmailer files>S8mailertablesmailer tables@:S 8:MAILERtag:MAILER tag8S 9mailgatewaymail gateway7S N8 definitiondefinition3>S8mailgatewaysmail gateways,5S N8 operatingoperatingh8S 9mailheadersmail headers5S N8 excessiveexcessive1S8MAINTMAINT7S 9 managementmanagement$:S 8masternodemaster nodeMNS  8maximum configurationmaximum configuration<S 9Meadows,JoeMeadows, JoeANS  8 messages, interactivemessages, interactive8S 8Miller,EdMiller, EdE'S  8MMMMV8S 9MODATTCOMMODATT COMA)S8modemmodem3S N8autodialautodial^S))N9 diagnosticandtestfeaturesdiagnostic and test features+SN8V.29V.29+SN8V.32V.32=S9 MODPARAMS.DATMODPARAMS.DATUS$$8monthly managementtasksmonthly management tasks=-S8MotifMotif6S 9:MSGStag:MSGS tag;S 8MultiNetMultiNetALSN8online documentationonline documentationq#6#8MULTINET_STARTUPcommand- procedureMULTINET_STARTUP command procedureGS8multistreamingmultistreamingCVQS  8MVS operatingsystemMVS operating system'S  9MXMX@2S8MXINFOMX INFO@!i  iNNGM2Novell,seeExcelanNovell, see Excelan)S  9NADNADK'S8namename<S N8JnetclusterJnet clusterLS9name authorityname authorityu>S8nameplanningname planning[)S8namesnames>SN9ALL-IN-1userALL-IN-1 user/SN8BITNETBITNETx3S 8planningplanning/SN9DECnetDECnety<S N8DECnetaliasDECnet aliasy7S N8 DECnet-VAXDECnet-VAX}QS""N9 difficultyinchangingdifficulty in changingsUS$$N8 DistributedNameServiceDistributed Name Servicey3SN8domaindomainxPS!!N9generalconsiderationsgeneral considerationss<S N8JnetclusterJnet clustery3S N8planningplanningm9S 9 assumptionsassumptionso5S 8 checklistchecklist{JS8 suggested proceduresuggested procedurez5SN9SCSNODESCSNODEy}/SN8useruserBSN8user, assigninguser, assigning'+SN8UUCPUUCPy7S N9 VAXclusterVAXclusteryDSN8 VAXclusteraliasVAXcluster alias8S N8VAXP.S.I.VAX P.S.I.y4S N9VMSuserVMS user/S8nameserver@S 9nameservicename service]JS8national charactersnational characters[S''8 NETCONFIGcommand procedureNETCONFIG command procedureKS9NETDATAfileformatNETDATA file format7S 8 netiquettenetiquette)1S8NETSERVNETSERV:S N9GETcommandGET commandA3S N8passwordpasswordJJS8network discussionsnetwork discussions OS9NetworkJobEntryNetwork Job Entry *<S8networknumbernetwork number3S N8assignedassigned@M2NetworkResearchNetwork ResearchUM''N3seeFUSIONTCP/IPforVMSsee FUSION TCP/IP for VMS/S8newsnews <DS8NEWTAGSDESCRIPTNEWTAGS DESCRIPTf6S 9:NICKtag:NICK tag1S  8NJENJE *-SN8linkslinks6S N9nodenamenode name-SN8nodesnodes-S  N8tagtag,IOS!!9NJEoutput limitationNJE output limitationG8S 8NJEsoftwareNJE software=SN8 configurationconfiguration;S N9 installationinstallationQS  8nodalmessagerecordnodal message recordG+S8nodenode*JS8nodeadministratorsnode administratorsK8S 9nodes,NJEnodes, NJE6S 8:NODEtag:NODE tag/S8NSFnetNSFnet!i  iOO7S 9 objectivesobjectives IS8officialhostnameofficial host nameWS%%8OpenSystems InterconnectOpen Systems InterconnectGS9optionfile,PMDFoption file, PMDFbS++8orderofsoftware installationorder of software installation)S  8OSIOSIQS""9OSI ApplicationKernelOSI Application Kernel3S 8overviewoverviewR!i  iPP\M**2Process Software,seeTCPwareProcess Software, see TCPware)S  9PAKPAKBS8PascalcompilerPascal compiler6S 8peernodepeer node 4S 9peopletagpeople tag@SN8for Postmasterfor PostmasterosS'448 permissionto reproduceand distributepermission to reproduce and distributeHS8personal computerspersonal computers@S8planningnamesplanning namesm5S N9 checklistchecklist{JSN8 suggested proceduresuggested procedurez;S8PMDFPMDF3<JV<S N9aliasesfilealiases file8S N8aliasfilealias fileESN8autoconfigurationautoconfigurationHS N9batchqueuesbatch queues3;DSN8channelqueueschannel queues39PS!!N8compiled configurationcompiled configuration1S9maximummaximum97 7SN8 configurationconfiguration-S8stepssteps=SN9 documentationdocumentation7S N8 ``don't''s``don't''s>SN8filelocationfile location;S N9 installationinstallationLSN8online documentationonline documentation:S N8optionfileoption fileGSN9periodbatchjobsperiod batch jobs<S N8sourcefilessource files1SN8startupstartup4S N9UICsforUICs forRS##N8useofTCP/IPsoftwareuse of TCP/IP software6S N8usernameuser nameHSN9 VAXclusterstartupVAXcluster startup3S N8versionsversions/S 8PMDF.CNFPMDF.CNF1SN8editingediting3S 9PMDF-FAXPMDF-FAXu#6#9PMDF_INIT_QUEUEScommand- procedurePMDF_INIT_QUEUES command procedureAS9PMDF_ROOT:[TABLE]PMDF_ROOT:[TABLE]jS#//N8defaultforPMDFautoconfigurationdefault for PMDF autoconfiguration{$7$9PMDF_START_QUEUEScommand- procedurePMDF_START_QUEUES command procedureq#6#8PMDF_SUBMIT_JOBScommand- procedurePMDF_SUBMIT_JOBS command procedure9S 8 PMDF_USERPMDF_USER<S 8PonyExpressPony ExpressVaS((9 POSTHEADONLYchannelkeywordPOSTHEADONLY channel keyword8;S 8POSTMASTPOSTMAST@7S 8 PostmasterPostmaster 7S N9 delegationdelegation8S N8peopletagpeople tagoCSN8responsibilitiesresponsibilities _S 9 POSTMASTERPOSTMASTER @u356BSN8 conflictinguseconflicting use"7S N8 privilegesprivileges"5S8POSTMASTSTANDARD1S8prefacepreface LS9 Princeton UniversityPrinceton University@S8 PrincipalNodePrincipal NodeBS8 PrincipalNodesPrincipal NodesGS9PRINTfileformatPRINT file formatDS8 printing,remoteprinting, remote9S8privacyprivacy,587S 9 privilegesprivilegesSS%%8Product AuthorizationKeyProduct Authorization Key7S N8 DECnet-VAXDECnet-VAX1SN9VAX-VMSVAX-VMS;S 8 pseudodomainpseudodomain7S 8 pseudonodepseudonode GS8PUNCHfileformatPUNCH file format!i  iQQQS""9Qmancommand procedureQman command procedure:1S8QSYSOPRQSYSOPRBS8QUERYcommandQUERY commandG^!i  iRR7S 9 registrationregistration>S N8BITNETnodeBITNET node0b:S N8domainnamedomain name3SN9mailermailer:g@S N8mailgatewaymail gateway;gCSN8ofBITNETnodesof BITNET nodesaaS**9 reinstallingsoftwareproductsreinstalling software products+A/8 rejection,mail,byINTERBITmail-gatewaysrejection, mail, by INTERBIT mail gateways@eS!,,8 Rensselaer Polytechnic InstituteRensselaer Polytechnic Institute@>S9REQUIREDINFOREQUIRED INFOe@S8REQUIREDINFO1REQUIRED INFO1eHS8 requirements,CRENrequirements, CREN=8S 9ReturnkeyReturn key&4S 8RFC1123RFC 11236S8RFC822RFC 82246S 9RiceMailRice Mail5/S8ROOTROOT@S8routingtablesrouting tables07S N8 installinginstalling\HSN9 installinginitialinstalling initialHSN8 monitoringupdatesmonitoring updates<S 8:ROUTTABtag:ROUTTAB tag/S9RSCSRSCS5!i  iSS1S8SCSNODESCSNODE1SN8namesnamesy}8S 9SCSNODEnameSCSNODE name3S N8changingchanging9S 8 SCSSYSTEMIDSCSSYSTEMID/S9security*YS$$8SENDHEADchannelkeywordSENDHEAD channel keyword8:S 8:SERVEDtag:SERVED tagOS!!9 short-formhostnamesshort-form host names`S**8SimpleMailTransferProtocolSimple Mail Transfer Protocol6S 8:SITEtag:SITE tagJS9 SKIP_XMAILERsymbolSKIP_XMAILER symbolGS8slowBITNETlinksslow BITNET links+S8SMTPSMTP7S 9SMTPUSERSMTPUSERYS&&8STARTNETcommand procedureSTARTNET command procedure>S8startopologystar topology [S%%9startup procedure,systemstartup procedure, system<=US$$8State UniversityexampleState University example;S 8 subclustersubclusterXiS((9 SYLOGICALScommand procedureSYLOGICALS command procedurePS!!8 synchronous interfacessynchronous interfaces_S))8 SYS$SYLOGINcommand procedureSYS$SYLOGIN command procedure<LS9 SYS$UPDATE directorySYS$UPDATE directory/S8SYSGENSYSGEN/S8SYSMANSYSMANDSN9STARTUPdatabaseSTARTUP database_S##8SYSMANSTARTUPfacilitySYSMAN STARTUP facilityHS8SYSNAM privilegeSYSNAM privilegeqS**9 SYSTARTUP_V5command procedureSYSTARTUP_V5 command procedure=7S8SYSTEMSYSTEM<S 8systemclocksystem clockASS 9SYSUAFSYSUAF!!i  iTT)S  9tagtagc)S  N8NJENJE,'S8tagstags<S N9DOMAINNAMESDOMAIN NAMES+S8TCP/IPTCP/IP6S N8hostnamehost name3S N9networksnetworks7S N8softwaresoftware7]PM$$3TCP/IPServicesforVMSTCP/IP Services for VMSSM%%N2see VMS/ULTRIX Connectionsee VMS/ULTRIX ConnectionBS9TCP/IPsoftwareTCP/IP software_S**N8 compatiblewithJnetTCPNJEcompatible with Jnet TCP NJEMS  N8 compatiblewithPMDFcompatible with PMDF=SN9 configurationconfigurationESN8forBITNETlinksfor BITNET linksGSN8forInternetmailfor Internet mail;S N9 installationinstallation;S8TCPNJElinksTCP NJE links6S N8linenameline name?ES9TCPNJEprotocolTCP NJE protocol1S9TCPwareTCPware1S8TECHREPTECHREPpHSN8 informationpacketinformation packetrDS9 TektronixTCP/IPTektronix TCP/IPDS8 terminology,newterminology, new%1S8testingtesting[2M 3TGV,Inc.TGV, Inc.8M N3seeMultiNetsee MultiNet:S 8timezonetime zoneA/S 8topologytopology)S  N9NJENJE 7S 8 trademarkstrademarks3S 8trainingtraining(AS9troubleshootingtroubleshootingZ!i  jUU)S  8UCXUCX_S))8 UCX$STARTUPcommand procedureUCX$STARTUP command procedure)S  9UICUIC'S8UICsUICs4S N8forPMDFfor PMDFSS##9 unreliableBITNETlinksunreliable BITNET links6S 8UPDATEjobsUPDATE jobs:S N8addressforaddress forkBS8UPDATEPROCEDURUPDATE PROCEDUReDS9update procedureupdate procedureckS#008update procedureforBITEARNNODESupdate procedure for BITEARN NODESc>S8updateserverupdate serverd3S 9upgradesupgradesE5S 8 uppercaseuppercase%@S 8useragentuser agent,5VUS$$9UserIdentificationCodeUser Identification CodeDS8user interfaceuser interface ,IS8usernameplanninguser name planning8S 9usernamesuser namesOS!!8usernames, assigninguser names, assigning''S8UUCPUUCP-SN9namesnamesy!i  jVV:S 8V.29modemsV.29 modems:S 8V.32modemsV.32 modemsDS9vacationprogramvacation program-S  8VAXVAX WS 8 VAXclusterVAXcluster<VW)SN9aliasalias-S8namesnamesGSN8common-environmentcommon-environment=S N8 homogeneoushomogeneousRS##N9JnetroutingtablesonJnet routing tables on`KSN8multiple-environmentmultiple-environment-SN8namesnamesy9S  N8useofSCSNODEnameOS!!9 VAXclusteraliasnameVAXcluster alias name9S 8 VAXclustersVAXclustersJJS8 VAXclusterSoftwareVAXcluster Software~4S 9VAXP.S.I.VAX P.S.I.-SN8namesnamesy5S 8 VAXstationsVAXstationsCSN9asBITNETnodesas BITNET nodes7S 8versionsversionsV?S8versions/BEGINversions/BEGIN;S 9 versions/ENDversions/END6S 8VMMailerVM MailerOS8VM operatingsystemVM operating systemSS##N9filenaming conventionsfile naming conventions1RS  8 VMS/ULTRIX ConnectionVMS/ULTRIX ConnectionAWS%%8VMS batch/print subsystemVMS batch/print subsystemHKS9VMSDUMPfileformatVMSDUMP file format9S 8 VMSINSTALVMSINSTAL#[S''8 VMSINSTALcommand procedureVMSINSTAL command procedure9S9VMSmailVMSmailKV=SN8 configurationconfiguration1SN8profileprofileaS  9VMS operatingsystemVMS operating system 3V~MSN8changeinV5.5change in V5.5HG=SN8 documentationdocumentation!WS%%N9system generationUtilitysystem generation UtilityYS&&N8system integratedproductssystem integrated productsSS##N8version4 compatibilityversion 4 compatibility$3S N9versionsversions!i  iWW-S9WHOISWHOISGS8WIN/TCPforVMSWIN/TCP for VMSAKM!!2 WollongongGroup,TheWollongong Group, TheHM  N3seeWIN/TCPforVMSsee WIN/TCP for VMS;S 8 workstationsworkstations!i  iXXZS8XMAILERNAMESXMAILER NAMES:@kVv,3OB.4CMailgatewaystoMail-11domainsBOUWhenPMDF exchangesmailwithVAXsystemsrunningKOonlyVMSmail,itmustusetheMail-11protocol(aDECnetQO application protocol).(Mail-11isaveryold protocol,andhasLO^manyproblemsthatmakeit unsuitablefor productionmail,NOsomeofwhicharelistedhere.) Therefore,only undertaketoNOsetupthis configurationifyoucannotgetmailersoftware3Oh installedontheremoteVAXsystems.>w QOThe principlereasontoattemptthis configurationissavetheLOcostofPMDF licenses.*AnotherreasonistoexchangemailDO5with non-VAX/VMSsystemsthathaveMail-11 software,3OsuchasDigitalPDP-11minicomputers.Ux! +VOHerearesomereasonstoavoidthis approach,ifatall possible. OTheremotesystem1cisthesystemrunningonlyMail-11FO5software(forexample,aVAXrunningVMSandVMSmail9ObutwithoutPMDF,MX,orTCP/IP sofware).Sy) `mEmUsersoftheremotesystemcannotuseIN%astheirHaddressprefix,as describedinthedocumentation.)They"mustuseIN:instead. `GUsersoftheremotesystemcannotusePMDF utilities,= SEND/FOREIGN,andotherPMDF features.-IntheCOfuture,thiswillpreventthemfromusingthenew@Internetstandard multi-mediamail, whichisnot! supportedbyMail-11. `=Mail-11systemshave six-characterDECnetnodeBnames,andcannotsupportdomainstylenames.,TheA0DECnetnodenamesmustbe distinguishedsomehowAfromBITNETnodenamesandTCP/IPrelative(also0called``shortform'')hostnames.sz IIOAMail-11mailgatewayisoften consideredforamixedFO interconnect VAXclusterwithmany satellites,toavoidEO5runningPMDFoneach satellite..Thereare additionalLOreasonsthatapplyonlytoMail-11toBITNETmailgatewas)Oservingasingle VAXcluster.L{ " `m>mTheMAIL$SYSTEM_FLAGSlogicalnamemustbesetGto0toindicatethe VAXclusteris hetergeneous;thatFforcesallmailbetweenclusermemberstogothroughIwDECnet.' (Normally,suchmailshouldbewrittenintotheK recipientsMAIL.MAIfilelocally,justlikemailwithina(singlemember.) `EMailrepliesonlyworkifthesendingnode(say, aE workstation)isonthenetwork,evenifthesending5Yuserisloggedintoanother satellite. `IAllPMDFbatchqueuesmustrunonbootnode(whichisO0alreadyasinglepointoffailureforclusterduetosingleCsystemdisk)insteadofrunningonanyidlenode. `KAll messagingjobsmustrunonthebootnode,andthereJawillbemanymoresuchjobs,becauseeverymailmessageNsentorreceivedona satellitewillrequireaDECnetjob.=|LOOnewaytoavoidtheproblemsofMail-11 transportwithinUOa VAXclusteristoprohibitmailonthe satellites.(All satelliteNO5usersmustuseSETHOSTor X-clientsonbootnodetosend$Oandreceivetheirmail.}NMOIfatall possible,avoidMail-11toBITNETmail gateways.KOIfyoumustusethistypeof configuation,refertothe PMDF"O5 System Manager'sGuide'5for additional information.( ~$O C.! Migration"from!Gmail _UNote _CThisappendixisadraft,andserves primarilytoJnprovideanoutlineformaterialforafutureeditionofCthisbook.*Your experiencesandother contributionsC arewelcome.+TosubmitmaterialorideasforthisBx appendix,followthe instructionsonthe copyright*pagefor submitting comments. IOGMAILshouldnolongerbeused.,ItsprimarypurposeisHOtosendmailtoINTERBITandothermail gateways.+TheHOjCRENTermsand Conditionsof Membershipand Affiliation@OrequirethatallCRENmembersthatuseINTERBITEOgatewaysmustinstallaBSMTP-compliantmailer.(GMAILAOtproducescorrect BSMTP-format messages,butcannotOacceptthem. YIOToremoveGMAILfromyoursystem,performthe followingOtasks: 0`m1.:Logintoa privilegedaccount.=`2.:FindthelocationoftheGMAIL directory: q$qSHOW%SYMBOL&GMAILO`3.:Notethe directory specificationinthesymbolvalue,and/Isetyourdefault directorythere.F`4.:CreateanewGMAILcommand procedureinthesameJ! directorythatprintsamessagetousers requestingthatEztheyuseVMSmailandPMDFinstead.(Hereisoneway&toentersuchamessage: W$WCREATE% GMAIL.COM$&TYPE% SYS$INPUTRGMAIL%has%been%removed.JPlease&send%all&mail%using%the&VMSmailR/Utility&(MAIL).KTo&send%to%Internet%and&BITNET% addresses,&enter"w addresses%of%the&form-i#IN%"username@host.subdomain.domain" and'iOIN%"USERNAME@nodename.BITNET"U respectively.KIf%you%have%any% questions,%please%contact%the%SystemManager.   M,Ctrl/Z M D J`5.:Youmayalsowanttouseyourregular proceduresto8announcethechangetoallsystemusers.O`6.:Nowdeletealltheotherfilesinthecurrent directory.J` 7.:Finally,send electronicmailtoauthorofGMAIL,EdA] Miller,GMAIL@SLACVX.BITNET,toaskhimtoremoveI yournamefromtheGMAILlistbecauseyouwillnotbeM usingtheprograminthefuture,andtogivehimawell-Fg deserved``Thankyou!'')formakingGMAIL availableto: the networking communitythroughtheyears.*   !!!!!!!!!!!!!!!!!"!##$$$$%%%%%&&'(())))))))))*****++++++++++,,,,,,,,,----.////////000011112233333344555555667666899::::;;;;<<====>>>>>>>>>>>>>>>>>?@AAAAAAAAAAAAAABBBBCCCCCDCEEEFFGGGGGGGHHHHHHHHIIIIIIIIIIIIIJKKKKKKKKKKKKKKKLLLMNOPPQPPPRSSTTTTTTTTTTTUVVWWXXYYYZZZZZ[[\\\\\\\\]]]]^_^^^^^```````ab````cdddeeeeefffghhhhijkkllllmllnooooopppppppqqqqqqqqrrrsssssssssstttttuuuuvuuuuuuuuwwwxxyxz{{{|||}}}~~~~~~ihPrefaceObjectivesObjectivesIntended audienceIntended audienceIntended audienceIntended audienceStructure of this bookStructure of this book4Software environment and associated documents4Software environment and associated documents4Software environment and associated documentsYTable 1: Minimum and assumed software versions for Digital VAX systems running VMS4Software environment and associated documents4Software environment and associated documents4Software environment and associated documents4Software environment and associated documents4Software environment and associated documents4Software environment and associated documents4Software environment and associated documents4Software environment and associated documents4Software environment and associated documents4Software environment and associated documents4Software environment and associated documents4Software environment and associated documents4Software environment and associated documents4Software environment and associated documentsConventionsConventionsConventionsConventionsConventions1. Mailers on BITNETF1.1 Direct Transmission of Electronic Mail by Network Job EntryF1.1 Direct Transmission of Electronic Mail by Network Job EntryF1.1 Direct Transmission of Electronic Mail by Network Job EntryF1.1 Direct Transmission of Electronic Mail by Network Job EntryF1.1 Direct Transmission of Electronic Mail by Network Job EntryF1.1 Direct Transmission of Electronic Mail by Network Job Entry1.2 BITNET Mail Concepts Note 11.2 BITNET Mail Concepts1.2 BITNET Mail Concepts1.2 BITNET Mail Concepts1.2 BITNET Mail Concepts@Figure 1- 1: Architecture of the BITNET mail application.1.2 BITNET Mail Concepts1.2 BITNET Mail ConceptsFFigure 1- 2: Sending BITNET mail by direct use of NJE software.1.2 BITNET Mail Concepts1.2 BITNET Mail Concepts1.2 BITNET Mail Concepts(1.3 BITNET Technical Requirements Note 2(1.3 BITNET Technical Requirements(1.3 BITNET Technical Requirements Note 3(1.3 BITNET Technical Requirements(1.3 BITNET Technical Requirements(1.3 BITNET Technical Requirements(1.3 BITNET Technical Requirements(1.3 BITNET Technical Requirements(1.3 BITNET Technical Requirements*1.4 Benefits of Installing a Mailer$1.4.1 Mailers Ease Addressing$1.4.1 Mailers Ease Addressing$1.4.1 Mailers Ease Addressing$1.4.1 Mailers Ease Addressing$1.4.1 Mailers Ease Addressing$1.4.1 Mailers Ease Addressing71.4.2 Mailers Isolate Users From Network Changes*1.4.3 Mailers Provide New Functions*1.4.3 Mailers Provide New Functions.2. Overview of Setting Up a BITNET Node.2. Overview of Setting Up a BITNET Node.2. Overview of Setting Up a BITNET Node2.1 Assumptions2.1 Assumptions2.1 Assumptions2.1 Assumptions2.1 Assumptions(2.2 Steps to set up a BITNET node(2.2 Steps to set up a BITNET node(2.2 Steps to set up a BITNET node(2.2 Steps to set up a BITNET node(2.2 Steps to set up a BITNET node(2.2 Steps to set up a BITNET node(2.2 Steps to set up a BITNET node(2.2 Steps to set up a BITNET node(2.2 Steps to set up a BITNET node(2.2 Steps to set up a BITNET node(2.2 Steps to set up a BITNET node(2.2 Steps to set up a BITNET node(2.2 Steps to set up a BITNET node(2.2 Steps to set up a BITNET node(2.2 Steps to set up a BITNET node(2.2 Steps to set up a BITNET node(2.2 Steps to set up a BITNET node?Figure 2- 1: Steps to set up an operational BITNET node.(2.2 Steps to set up a BITNET node(3. Planning System and User Names(3. Planning System and User Names13.1 Starting assumptions for name planning13.1 Starting assumptions for name planning13.1 Starting assumptions for name planning13.1 Starting assumptions for name planning33.2 General considerations for network names33.2 General considerations for network names33.2 General considerations for network names33.2 General considerations for network names33.2 General considerations for network names!3.3 Names for BITNET hosts!3.3 Names for BITNET hosts83.4 Suggested procedure for planning system names/3.4.1 Summary of name planning procedure/3.4.1 Summary of name planning procedure.3.4.2 Plan SCSNODE and DECnet-VAX names.3.4.2 Plan SCSNODE and DECnet-VAX names.3.4.2 Plan SCSNODE and DECnet-VAX names.3.4.2 Plan SCSNODE and DECnet-VAX names.3.4.2 Plan SCSNODE and DECnet-VAX names.3.4.2 Plan SCSNODE and DECnet-VAX names.3.4.2 Plan SCSNODE and DECnet-VAX names.3.4.2 Plan SCSNODE and DECnet-VAX names.3.4.2 Plan SCSNODE and DECnet-VAX names.3.4.2 Plan SCSNODE and DECnet-VAX names)3.4.3 Plan a VAXcluster alias name)3.4.3 Plan a VAXcluster alias name)3.4.3 Plan a VAXcluster alias name)3.4.3 Plan a VAXcluster alias name)3.4.3 Plan a VAXcluster alias name3.4.4 Plan domain names3.4.4 Plan domain names3.4.4 Plan domain names3.4.4 Plan domain names3.4.4 Plan domain names3.4.4 Plan domain names3.4.4 Plan domain names3.4.4 Plan domain names3.4.4 Plan domain names3.4.4 Plan domain names43.4.5 Register a domain name with the DDN NIC43.4.5 Register a domain name with the DDN NIC43.4.5 Register a domain name with the DDN NIC43.4.5 Register a domain name with the DDN NIC43.4.5 Register a domain name with the DDN NIC43.4.5 Register a domain name with the DDN NIC43.4.5 Register a domain name with the DDN NIC43.4.5 Register a domain name with the DDN NIC43.4.5 Register a domain name with the DDN NIC3.4.6 Plan NJE names3.4.6 Plan NJE names3.4.6 Plan NJE names3.4.6 Plan NJE names13.4.7 Plan reserved and general user names&3.4.7.1 POSTMASTER and POSTMAST&3.4.7.1 POSTMASTER and POSTMAST&3.4.7.1 POSTMASTER and POSTMAST&3.4.7.1 POSTMASTER and POSTMAST&3.4.7.1 POSTMASTER and POSTMAST&3.4.7.1 POSTMASTER and POSTMAST&3.4.7.1 POSTMASTER and POSTMAST&3.4.7.1 POSTMASTER and POSTMAST"3.4.7.2 MAILER and SMTPUSER"3.4.7.2 MAILER and SMTPUSER"3.4.7.2 MAILER and SMTPUSER"3.4.7.2 MAILER and SMTPUSER#3.4.7.3 LISTSERV and NETSERV#3.4.7.3 LISTSERV and NETSERV#3.4.7.3 LISTSERV and NETSERV#3.4.7.3 LISTSERV and NETSERV3.4.7.4 JOB3.4.7.4 JOB&3.4.7.5 SYSTEM, ROOT, and MAINT&3.4.7.5 SYSTEM, ROOT, and MAINT&3.4.7.5 SYSTEM, ROOT, and MAINT&3.4.7.5 SYSTEM, ROOT, and MAINT&3.4.7.5 SYSTEM, ROOT, and MAINT&3.4.7.5 SYSTEM, ROOT, and MAINT!3.4.7.6 PMDF and PMDF_USER!3.4.7.6 PMDF and PMDF_USER!3.4.7.7 General user names!3.4.7.7 General user names!3.4.7.7 General user names!3.4.7.7 General user names!3.4.7.7 General user names!3.4.7.7 General user names!3.5 Campus network example!3.5 Campus network exampleFTable 3- 1: Campus-wide network name space example: Bay College!3.5 Campus network example!3.5 Campus network example!3.5 Campus network example84. Installing and Configuring Networking Software)4.1 VMSINSTAL and autoanswer files)4.1 VMSINSTAL and autoanswer files!4.2 Changing SCSNODE names!4.2 Changing SCSNODE names!4.2 Changing SCSNODE names!4.2 Changing SCSNODE names!4.3 Configuring DECnet-VAX!4.3 Configuring DECnet-VAX!4.3 Configuring DECnet-VAX!4.3 Configuring DECnet-VAX,4.4 Configuring DECnet-VAX Extensions,4.4 Configuring DECnet-VAX Extensions4.5 Configuring VMSmail4.5 Configuring VMSmail4.5 Configuring VMSmail4.5 Configuring VMSmail04.6 TCP/IP installation and configuration04.6 TCP/IP installation and configuration04.6 TCP/IP installation and configuration04.6 TCP/IP installation and configuration04.6 TCP/IP installation and configuration04.6 TCP/IP installation and configuration04.6 TCP/IP installation and configuration04.6 TCP/IP installation and configuration04.6 TCP/IP installation and configuration04.6 TCP/IP installation and configuration04.6 TCP/IP installation and configuration04.6 TCP/IP installation and configuration04.6 TCP/IP installation and configuration04.6 TCP/IP installation and configuration04.6 TCP/IP installation and configuration04.6 TCP/IP installation and configuration04.6 TCP/IP installation and configuration15. Installing and Configuring NJE Software5.1 Plan BITNET topology75.1.1 Selecting systems to participate in BITNET75.1.1 Selecting systems to participate in BITNET75.1.1 Selecting systems to participate in BITNET75.1.1 Selecting systems to participate in BITNET75.1.1 Selecting systems to participate in BITNET75.1.1 Selecting systems to participate in BITNET75.1.1 Selecting systems to participate in BITNET75.1.1 Selecting systems to participate in BITNET75.1.1 Selecting systems to participate in BITNET75.1.1 Selecting systems to participate in BITNET75.1.1 Selecting systems to participate in BITNET75.1.1 Selecting systems to participate in BITNET75.1.1 Selecting systems to participate in BITNET75.1.1 Selecting systems to participate in BITNET5.1.2 Principal Nodes5.1.2 Principal Nodes5.1.2 Principal Nodes5.1.2 Principal Nodes*5.1.3 Planning external connections*5.1.3 Planning external connections*5.1.3 Planning external connections*5.1.3 Planning external connections*5.1.3 Planning external connectionsFigure 5- 1: BITNET topology example. Large filled circles represent Principal Nodes. Open circles represent pseudonodes bearing Jnet cluster names.*5.1.3 Planning external connections-5.1.4 Planning intraorganization links-5.1.4 Planning intraorganization links-5.1.4 Planning intraorganization links#5.1.5 VAXcluster connections#5.1.5 VAXcluster connections5.1.6 Link protocols5.1.6 Link protocols5.1.6 Link protocols5.1.6 Link protocols5.1.6 Link protocols5.1.6 Link protocols5.1.6 Link protocols$5.2 Install BITNET transports$5.2 Install BITNET transports$5.2 Install BITNET transports$5.2 Install BITNET transports$5.2 Install BITNET transports$5.2 Install BITNET transports$5.2 Install BITNET transports$5.2 Install BITNET transports(5.3 Install Jnet and link drivers(5.3 Install Jnet and link drivers(5.3 Install Jnet and link drivers(5.3 Install Jnet and link drivers(5.3 Install Jnet and link drivers(5.3 Install Jnet and link drivers(5.3 Install Jnet and link drivers(5.3 Install Jnet and link drivers(5.3 Install Jnet and link drivers(5.3 Install Jnet and link drivers(5.3 Install Jnet and link drivers(5.3 Install Jnet and link drivers(5.3 Install Jnet and link drivers5.4 Configure Jnet15.4.1 Run Jnet autoconfiguration procedure15.4.1 Run Jnet autoconfiguration procedure15.4.1 Run Jnet autoconfiguration procedure15.4.1 Run Jnet autoconfiguration procedure15.4.1 Run Jnet autoconfiguration procedure15.4.1 Run Jnet autoconfiguration procedure15.4.1 Run Jnet autoconfiguration procedure15.4.1 Run Jnet autoconfiguration procedure15.4.1 Run Jnet autoconfiguration procedure15.4.1 Run Jnet autoconfiguration procedure15.4.1 Run Jnet autoconfiguration procedure15.4.1 Run Jnet autoconfiguration procedure15.4.1 Run Jnet autoconfiguration procedure15.4.1 Run Jnet autoconfiguration procedure15.4.1 Run Jnet autoconfiguration procedure'5.4.2 Manual configuration tasks'5.4.2 Manual configuration tasks'5.4.2 Manual configuration tasks-5.4.2.1 Edit JAN_COMMON:[SYS]LOGIN.COM+5.4.2.2 Test SYS$MANAGER:SYLOGIN.COMI5.4.2.3 Use SYSMAN STARTUP instead of SYS$MANAGER:SYSTARTUP_V5.COMA5.4.2.4 Edit JAN_SYS:JANLINKS.JCP and JAN_SYS:JANSTART.JCPA5.4.2.4 Edit JAN_SYS:JANLINKS.JCP and JAN_SYS:JANSTART.JCP<Table 5- 1: TCP/IP Products supported by Jnet TCP NJEA5.4.2.4 Edit JAN_SYS:JANLINKS.JCP and JAN_SYS:JANSTART.JCPA5.4.2.4 Edit JAN_SYS:JANLINKS.JCP and JAN_SYS:JANSTART.JCPA5.4.2.4 Edit JAN_SYS:JANLINKS.JCP and JAN_SYS:JANSTART.JCP:5.4.2.5 Defer the creation of JAN_SYS:JANROUTES.JCP.5.4.2.6 Consolidate JAN_SYS:JANLOAD.COM.5.4.2.6 Consolidate JAN_SYS:JANLOAD.COM55.4.2.7 Edit JAN_COMMON:[SYS]JANSITECOMMON.COM55.4.2.7 Edit JAN_COMMON:[SYS]JANSITECOMMON.COM55.4.2.7 Edit JAN_COMMON:[SYS]JANSITECOMMON.COM55.4.2.7 Edit JAN_COMMON:[SYS]JANSITECOMMON.COM55.4.2.7 Edit JAN_COMMON:[SYS]JANSITECOMMON.COM55.4.2.7 Edit JAN_COMMON:[SYS]JANSITECOMMON.COM55.4.2.7 Edit JAN_COMMON:[SYS]JANSITECOMMON.COM55.4.2.7 Edit JAN_COMMON:[SYS]JANSITECOMMON.COM55.4.2.7 Edit JAN_COMMON:[SYS]JANSITECOMMON.COM55.4.2.7 Edit JAN_COMMON:[SYS]JANSITECOMMON.COM55.4.2.7 Edit JAN_COMMON:[SYS]JANSITECOMMON.COM,5.4.2.8 Skip instructions for LMD.COM:5.4.2.9 Edit and enable JAN_COMMON:[SYS]JANTIDY.COM:5.4.2.9 Edit and enable JAN_COMMON:[SYS]JANTIDY.COM)5.4.2.10 Edit link parameter files)5.4.2.10 Edit link parameter files95.4.2.11 Edit SYS$COMMON:[SYSMGR]LAT$SYSTARTUP.COM95.4.2.11 Edit SYS$COMMON:[SYSMGR]LAT$SYSTARTUP.COM5.5 Bring up BITNET link5.5 Bring up BITNET link5.5 Bring up BITNET link 5.6 Install BITNET tables 5.6 Install BITNET tables 5.6 Install BITNET tables 5.6 Install BITNET tables 5.6 Install BITNET tables 5.7 Register BITNET nodes 5.7 Register BITNET nodes'5.7.1 About the UPDATE procedure'5.7.1 About the UPDATE procedure'5.7.1 About the UPDATE procedure'5.7.1 About the UPDATE procedure'5.7.1 About the UPDATE procedure'5.7.1 About the UPDATE procedure'5.7.1 About the UPDATE procedure'5.7.1 About the UPDATE procedure&5.7.2 Where to send UPDATE jobs&5.7.2 Where to send UPDATE jobs&5.7.2 Where to send UPDATE jobs&5.7.2 Where to send UPDATE jobs+5.7.3 Adding a Postmaster people tag4Example 5- 1: Member entry from BITEARN NODES+5.7.3 Adding a Postmaster people tag+5.7.3 Adding a Postmaster people tag+5.7.3 Adding a Postmaster people tag+5.7.3 Adding a Postmaster people tag+5.7.3 Adding a Postmaster people tag5.7.4 Registering a node5.7.4 Registering a node5.7.4 Registering a node5.7.4 Registering a node5.7.4 Registering a node5.7.4 Registering a node5.7.4 Registering a nodecExample 5- 2: UPDATE job to create a node entry in BITEARN NODES for a standalone VAX systemhExample 5- 3: UPDATE job to create node entries in BITEARN NODES for a two-node VAXcluster system5.7.4 Registering a node5.7.4 Registering a node5.7.4 Registering a node5.7.4 Registering a node"5.8 Wait for routing tables%5.8.1 The monthly update cycle%5.8.1 The monthly update cycle%5.8.1 The monthly update cycle%5.8.2 Monitoring table updates%5.8.2 Monitoring table updates%5.8.2 Monitoring table updates%5.8.2 Monitoring table updates%5.8.2 Monitoring table updates&5.8.3 Installing initial tables&5.8.3 Installing initial tables&5.8.3 Installing initial tables46. Installing and Registering a BITNET Mailer$6.1 External view of a mailer$6.1 External view of a mailer$6.1 External view of a mailer$6.1 External view of a mailer6.2 Install PMDF36.2.1 Determine UICs for PMDF SYSUAF entries16.2.2 Select a location for the PMDF files16.2.2 Select a location for the PMDF files6.2.3 Set up PMDF queues6.2.3 Set up PMDF queues6.2.3 Set up PMDF queues6.2.3 Set up PMDF queuesaExample 6- 1: Command procedure to initialize PMDF batch queues on a two-member VAXcluster6.2.3 Set up PMDF queues6.2.3 Set up PMDF queuesfExample 6- 2: Command procedure to start PMDF batch execution queues on a two-member VAXcluster6.2.4 Run VMSINSTAL6.2.4 Run VMSINSTAL6.2.4 Run VMSINSTAL6.2.4 Run VMSINSTAL6.2.4 Run VMSINSTAL16.2.5 Configure PMDF for automatic startup16.2.5 Configure PMDF for automatic startup16.2.5 Configure PMDF for automatic startup16.2.5 Configure PMDF for automatic startup16.2.5 Configure PMDF for automatic startup16.2.5 Configure PMDF for automatic startup16.2.5 Configure PMDF for automatic startup;6.2.6 Make PMDF online books available to Bookreader;6.2.6 Make PMDF online books available to Bookreader;6.2.6 Make PMDF online books available to Bookreader;6.2.6 Make PMDF online books available to Bookreader;6.2.6 Make PMDF online books available to Bookreader;6.2.6 Make PMDF online books available to Bookreader;6.2.6 Make PMDF online books available to Bookreader;6.2.6 Make PMDF online books available to Bookreader6.3 Configure PMDF6.3 Configure PMDF6.3 Configure PMDF 6.3.1 Obtain mailer files 6.3.1 Obtain mailer files 6.3.1 Obtain mailer files 6.3.1 Obtain mailer files 6.3.1 Obtain mailer files 6.3.1 Obtain mailer files 6.3.1 Obtain mailer files 6.3.1 Obtain mailer files 6.3.1 Obtain mailer files 6.3.1 Obtain mailer files'6.3.2 Run PMDF autoconfiguration'6.3.2 Run PMDF autoconfiguration'6.3.2 Run PMDF autoconfiguration'6.3.2 Run PMDF autoconfiguration'6.3.2 Run PMDF autoconfiguration)6.3.3 Edit PMDF configuration file)6.3.3 Edit PMDF configuration file)6.3.3 Edit PMDF configuration file)6.3.3 Edit PMDF configuration file>Example 6- 3: PMDF configuration file for a BITNET node)6.3.3 Edit PMDF configuration file)6.3.3 Edit PMDF configuration file)6.3.3 Edit PMDF configuration file)6.3.3 Edit PMDF configuration file)6.3.3 Edit PMDF configuration file)6.3.3 Edit PMDF configuration file)6.3.3 Edit PMDF configuration file)6.3.3 Edit PMDF configuration file6.3.4 Run LONG_NAMES6.3.4 Run LONG_NAMES6.3.4 Run LONG_NAMES#6.3.5 Edit PMDF aliases file#6.3.5 Edit PMDF aliases file6Example 6- 4: PMDF alias file for a BITNET node#6.3.5 Edit PMDF aliases file"6.3.6 Compile configuration,6.3.6.1 Compile maximum configuration,6.3.6.1 Compile maximum configuration,6.3.6.1 Compile maximum configuration-6.3.6.2 Install compiled configuration-6.3.6.2 Install compiled configuration-6.3.6.2 Install compiled configuration6.3.7 Move LMD.COM6.3.7 Move LMD.COM6.3.7 Move LMD.COM.6.3.8 PMDF configuration steps to avoid.6.3.8 PMDF configuration steps to avoid.6.3.8 PMDF configuration steps to avoid.6.3.8 PMDF configuration steps to avoid.6.3.8 PMDF configuration steps to avoid.6.3.8 PMDF configuration steps to avoid06.4 Start up PMDF on all VAXcluster nodes06.4 Start up PMDF on all VAXcluster nodes%6.5 Update BITNET registration%6.5 Update BITNET registrationvExample 6- 5: UPDATE job to register a mailer and Internet address in BITEARN NODES for a standalone VAX system{Example 6- 6: UPDATE job to register a mailer and Internet address in BITEARN NODES for a two-node VAXcluster system%6.5 Update BITNET registration.6.6 Register domain gateway with BITNIC.6.6 Register domain gateway with BITNIC.6.6 Register domain gateway with BITNIC.6.6 Register domain gateway with BITNIC.6.6 Register domain gateway with BITNIC.6.6 Register domain gateway with BITNIC.6.6 Register domain gateway with BITNIC.6.6 Register domain gateway with BITNIC.6.6 Register domain gateway with BITNIC.6.6 Register domain gateway with BITNIC!6.6.1 Tags in DOMAIN NAMES!6.6.1 Tags in DOMAIN NAMES!6.6.1 Tags in DOMAIN NAMES!6.6.1 Tags in DOMAIN NAMES!6.6.1 Tags in DOMAIN NAMES!6.6.1 Tags in DOMAIN NAMES!6.6.1 Tags in DOMAIN NAMES!6.6.1 Tags in DOMAIN NAMES<6.6.2 Registering an Internet domain name with BITNIC<6.6.2 Registering an Internet domain name with BITNICYExample 6- 7: Mail to DOMAINS@BITNIC to register the Arnold.Com domain with BITNET<6.6.2 Registering an Internet domain name with BITNIC<6.6.2 Registering an Internet domain name with BITNIC<6.6.2 Registering an Internet domain name with BITNICF6.6.3 Registering a new domain name with BITNIC and the DDN NICF6.6.3 Registering a new domain name with BITNIC and the DDN NICF6.6.3 Registering a new domain name with BITNIC and the DDN NIClExample 6- 8: Mail to DOMAINS@BITNIC to register the BostonCol.Edu domain with BITNIC and the DDN NIC46.7 Subscribe to relevant network discussions46.7 Subscribe to relevant network discussions46.7 Subscribe to relevant network discussions46.7 Subscribe to relevant network discussions46.7 Subscribe to relevant network discussions*6.7.1 Subscribing to LISTSERV lists*6.7.1 Subscribing to LISTSERV lists*6.7.1 Subscribing to LISTSERV lists*6.7.1 Subscribing to LISTSERV lists*6.7.1 Subscribing to LISTSERV lists*6.7.1 Subscribing to LISTSERV lists*6.7.1 Subscribing to LISTSERV lists*6.7.1 Subscribing to LISTSERV lists*6.7.1 Subscribing to LISTSERV lists*6.7.1 Subscribing to LISTSERV lists*6.7.1 Subscribing to LISTSERV lists06.7.2 Subscribing to Internet discussions06.7.2 Subscribing to Internet discussions06.7.2 Subscribing to Internet discussions06.7.2 Subscribing to Internet discussions06.7.2 Subscribing to Internet discussions06.7.2 Subscribing to Internet discussions06.7.2 Subscribing to Internet discussions-7. On-going Management of BITNET Nodes-7. On-going Management of BITNET Nodes.7.1 Initially and when adding new users!7.1.1 Assigning user names7.1.2 User training7.1.2 User training7.1.2 User training7.1.2 User training7.1.2 User training7.2 Constantly7.2 Constantly7.2 Constantly7.2 Constantly7.2 Constantly7.2 Constantly7.3 Weekdays"7.3.1 Review JANTIDY output07.3.2 Dispose of files sent to POSTMASTER$7.3.3 Read mail to POSTMASTER$7.3.3 Read mail to POSTMASTER$7.3.3 Read mail to POSTMASTER&7.3.4 Check PMDF channel queues&7.3.4 Check PMDF channel queues$7.3.5 Check PMDF batch queues.7.3.6 Read relevant network discussions7.4 Monthly(7.4.1 Install Jnet routing tables(7.4.1 Install Jnet routing tables 7.4.2 Build mailer tables%7.5 When changing system clock%7.5 When changing system clock%7.5 When changing system clock97.6 Management activities with no regular schedule07.6.1 Update Jnet and PMDF configurations67.6.2 Modify software when SCSNODE names change57.6.3 Adjust queues when upgrading to VMS V5.557.6.3 Adjust queues when upgrading to VMS V5.557.6.3 Adjust queues when upgrading to VMS V5.5)7.6.4 Respond to mail from NETSERV)7.6.4 Respond to mail from NETSERV)7.6.4 Respond to mail from NETSERV)7.6.4 Respond to mail from NETSERV)7.6.4 Respond to mail from NETSERV)7.6.4 Respond to mail from NETSERV)7.6.4 Respond to mail from NETSERV8A. Adding an Internet Connection to a BITNET Node(A.1 Assumptions for this appendix(A.1 Assumptions for this appendix3A.2 Obtain a network number from the DDN NIC3A.2 Obtain a network number from the DDN NIC3A.3 Review acceptable use and other policies3A.3 Review acceptable use and other policies3A.3 Review acceptable use and other policiesAA.4 Join a consortium or arrange for commercial IP service(A.5 Install a physical connection0A.6 Install and configure TCP/IP software0A.6 Install and configure TCP/IP software#A.7 Arrange for name service#A.7 Arrange for name service"A.8 Reconfigure your MAILERA.9 Update DOMAIN NAMESA.9 Update DOMAIN NAMESA.9 Update DOMAIN NAMES"A.10 Adjust BITNET topology"A.10 Adjust BITNET topology'A.11 Train users on new services'A.11 Train users on new services(A.12 Switch to Internet News feed(B. Operating BITNET Mail Gateways(B. Operating BITNET Mail Gateways0B.1 Mail gateways to domains with mailers0B.1 Mail gateways to domains with mailers0B.1 Mail gateways to domains with mailers0B.1 Mail gateways to domains with mailers0B.1 Mail gateways to domains with mailers0B.1 Mail gateways to domains with mailers0B.1 Mail gateways to domains with mailers7B.2 Providing name service for connected domains7B.2 Providing name service for connected domains7B.2 Providing name service for connected domains-B.3 Operating an INTERBIT mail gateway-B.3 Operating an INTERBIT mail gateway+B.4 Mail gateways to Mail-11 domains+B.4 Mail gateways to Mail-11 domains+B.4 Mail gateways to Mail-11 domains+B.4 Mail gateways to Mail-11 domains+B.4 Mail gateways to Mail-11 domains+B.4 Mail gateways to Mail-11 domains+B.4 Mail gateways to Mail-11 domains+B.4 Mail gateways to Mail-11 domainsC. Migration from GmailC. Migration from GmailC. Migration from GmailC. Migration from Gmail &P12345678PREFACE_PREFACEPREFACE_OBJECTIVE_SEC11PREFACE_AUDIENCE_SEC131415PREFACE_STRUCTURE_SEC17PREFACE_DOCUMENT_SEC1920SOFTWARE_VERSION_TABLE2223242526272829303132333435PREFACE_CONVENTION_SEC37383940INTRO_CHAPINTRO_MAILER_NJE_SEC4344454647INTRO_MAILER_DEFIN_SEC_DECW_FN_1_150515253INTRO_MAIL_ARCH_FIGURE5556INTRO_MAIL_DIRECT_FIGURE585960INTRO_REQUIR_SEC_DECW_FN_2_26364_DECW_FN_3_3666768697071INTRO_BENEFIT_SECINTRO_BENEFIT_USE_SEC7475767778INTRO_BENEFIT_ISOLATE_SECINTRO_BENEFIT_FUNCT_SEC81OVERVIEW_CHAP8384OVER_ASSUMP_SEC86878889OVER_STEPS_SEC919293949596979899100101102103104105106OVERVIEW_STEPS_FIGURE108NAMES_CHAP110NAMES_ASSUMP_SEC112113114NAMES_GENERAL_SEC116117118119NAMES_BITNET_SEC121NAMES_PROCED_SECNAMES_PROCED_CHECKL_SEC124NAMES_PROCED_DECNET_SEC126127128129130131132133134NAMES_PROCED_CLUSTER_SEC136137138139NAMES_PROCED_DOMAIN_SEC141142143144145146147148149NAMES_PROCED_REGIST_SEC151152153154155156157158NAMES_PROCED_NJE_SEC160161162NAMES_PROCED_USER_SECNAMES_RESERVED_POSTMASTER_SEC165166167168169170171NAMES_RESERVED_MAILER_SEC173174175NAMES_RESERVED_LISTSERV_SEC177178179NAMES_RESERVED_JOB_SEC181NAMES_RESERVED_SYSTEM_SEC183184185186187NAMES_RESERVED_PMDF_SEC189NAMES_RESERVED_GENERAL_SEC191192193194195NAMES_EXAMPLE_SEC197NAMES_EXAMPLE_TABLE199200201NETWORKSW_CHAPNETWORKSW_AUTOANS_SEC204NETWORKSW_SCSNODE_SEC206207208NETWORKSW_DECNET_SEC210211212NETWORKSW_DVEXT_SEC214NETWORKSW_DECNET_VMSMAIL_SEC216217218NETWORKSW_TCPIP_SEC220221222223224225226227228229230231232233234235NJE_CHAPJNET_PLAN_SECJNET_PLAN_LICENSE_SEC239240241242243244245246247248249250251JNET_PLAN_PRINCIPAL_SEC253254255JNET_PLAN_EXTERNAL_SEC257258259260JNET_PLAN_FIGURE262JNET_PLAN_INTERNAL_SEC264265JNET_PLAN_CLUSTER_SEC267JNET_PLAN_PROTOCOLS_SEC269270271272273274JNET_TRANSPORT_SEC276277278279280281282JNET_INSTALL_SEC284285286287288289290291292293294295JNET_CONFIG_SECJNET_CONFIG_PROC_SEC298299300301302303304305306307308309310311JNET_CONFIG_MANUAL_SEC313314JNET_CONFIG_JANLOGIN_SECJNET_CONFIG_SYLOGIN_SECJNET_CONFIG_SYSMAN_SECJNET_CONFIG_JANJCP_SEC319TCPIP_PRODUCT_TABLE321322323JNET_CONFIG_JANROUTES_SECJNET_CONFIG_JANLOAD_SEC326JNET_CONFIG_JANSITECOMMON_SEC328329330331332333334335336337JNET_CONFIG_LMD_SECJNET_CONFIG_JANTIDY_SEC340JNET_CONFIG_PAR_SEC342JNET_CONFIG_LAT_SEC344BITNET_LINK_SEC346347BITNET_TABLE_SEC349350351352JNET_REGISTER_SEC354NODE_REGISTR_UPDATE_SEC356357358359360361362NODE_REGISTR_WHERE_SEC364365366NODE_REGISTR_POSTMAST_SECMEMBER_ENTRY_EXAMPLE369370371372373NODE_REGISTR_NODE_SEC375376377378379380ADD_NODE_EXAMPLEADD_CLUSTER_EXAMPLE383384385386JNET_WAIT_SECJNET_WAIT_SCHED_SEC389390JNET_WAIT_URGE_SEC392393394395JNET_WAIT_INSTALL_SEC397398MAILER_CHAPMAILER_EXTERNAL_SEC401402403MAILER_INSTALL_SECMAILER_INSTALL_UAF_SECMAILER_INSTALL_DISK_SEC407MAILER_INSTALL_QUEUES_SEC409410411MAILER_INSTALL_QUEUES_EXAMPLE413414MAILER_INSTALL_QUESTART_EXAMPLEMAILER_INSTALL_VMSINSTAL_SEC417418419420MAILER_INSTALL_STARTUP_SEC422423424425426427MAILER_INSTALL_DECWBOOK_SEC429430431432433434435MAILER_CONFIG_SEC437438MAILER_CONFIG_FILES_SEC440441442443444445446447448MAILER_CONFIG_AUTOCONFIG_SEC450451452453MAILER_CONFIG_EDIT_SEC455456457MAILER_CONFIG_EDIT_EXAMPLE459460461462463464465466MAILER_CUSTOM_LONGNAMES_SEC468469MAILER_CUSTOM_ALIASES_SEC471ALIASES_EXAMPLE473MAILER_COMPILE_SECMAILER_COMPILE_MAXIMUM_SEC476477MAILER_COMPILE_INSTALL_SEC479480MAILER_CONFIG_LMD_SEC482483MAILER_CONFIG_AVOID_SEC485486487488489MAILER_VAXCLUSTER_SEC491MAILER_SERVERS1_SEC493REG_MAILER_NODE_EXAMPLEREG_MAILER_CLUSTER_EXAMPLE496MAILER_GATEWAY_SEC498499500501502503504505506MAILER_GATEWAY_TAGS_SEC508509510511512513514MAILER_GATEWAY_INTERNET_SEC516MAILER_GATEWAY_INTERNET_EXAMPLE518519520MAILER_GATEWAY_BITONLY_SEC522523MAILER_GATEWAY_BITONLY_EXAMPLEMAILER_LISTSUBS_SEC526527528529MAILER_LISTSUBS_LISTSERV_SEC531532533534535536537538539540MAILER_LISTSUBS_INTERNET_SEC542543544545546547MANAGE_CHAP549MANAGE_INITIAL_SECMANAGE_INITIAL_USERNAME_SECMANAGE_INITIAL_TRAINING_SEC553554555556MANAGE_CONSTANT_SEC558559560561562MANAGE_WEEKDAY_SECMANAGE_WEEKDAY_JANTIDY_SECMANAGE_WEEKDAY_POSTFILE_SECMANAGE_WEEKDAY_POSTMAIL_SEC567568MANAGE_WEEKDAY_PMDFCHAN_SEC570MANAGE_WEEKDAY_PMDFBATCH_SECMANAGE_WEEKDAY_LISTS_SECMANAGE_MONTHLY_SECMANAGE_MONTHLY_JNET_SEC575MANAGE_MONTHLY_MAILER_SECMANAGE_CLOCK_SEC578579MANAGE_IRREG_SECMANAGE_IRREG_CONFIG_SECMANAGE_IRREG_SCSNODE_SECMANAGE_IRREG_VMS_SEC584585MANAGE_IRREG_NETSERV_SEC587588589590591592INTERNET_APPENDINTERNET_ASSUMP_SEC595INTERNET_IPADDR_SEC597INTERNET_USE_SEC599600INTERNET_SERVICE_SECINTERNET_PHYSICAL_SECINTERNET_SOFTWARE_SEC604INTERNET_NAMESERV_SEC606INTERNET_MAILER_SECINTERNET_DOMAIN_SEC609610INTERNET_BITNET_SEC612INTERNET_TRAIN_SEC614INTERNET_NEWS_SECGATEWAY_APPEND617GATEWAY_MAILONLY_SEC619620621622623624GATEWAY_NAME_SEC626627GATEWAY_INTERBIT_SEC629GATEWAY_MAIL11_SEC631632633634635636637GMAIL_APPEND639640641 B-ADOBE-Helvetica-Medium-R-Normal--*-120-*-*-P-*-ISO8859-1@-ADOBE-Helvetica-Bold-R-Normal--*-180-*-*-P-*-ISO8859-1@-ADOBE-Helvetica-Bold-R-Normal--*-120-*-*-P-*-ISO8859-1@-ADOBE-Helvetica-Bold-R-Normal--*-100-*-*-P-*-ISO8859-1B-ADOBE-Helvetica-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-1M-ADOBE-New Century Schoolbook-Bold-R-Normal--*-140-*-*-P-*-ISO8859-1/-ADOBE-Symbol-*-R-*--*-140-*-*-P-*-*-*O -ADOBE-New Century Schoolbook-Medium-R-Normal--*-120-*-*-P-*-ISO8859-1O -ADOBE-New Century Schoolbook-Medium-I-Normal--*-140-*-*-P-*-ISO8859-1M -ADOBE-New Century Schoolbook-Bold-R-Normal--*-120-*-*-P-*-ISO8859-1O -ADOBE-New Century Schoolbook-Medium-I-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-Courier-Medium-R-Normal--*-120-*-*-M-*-ISO8859-1>-ADOBE-Courier-Bold-R-Normal--*-120-*-*-M-*-ISO8859-1@-ADOBE-Courier-Medium-O-Normal--*-120-*-*-M-*-ISO8859-1  nk#O StructureofthisbookHOUThisbookincludessevenchaptersandthree appendices.    `m+mChapter1,MailersonBITNET,{m introducesrequiredE networkingconceptsandexplainsthe requirementsforEandbenefitsofrunningamaileronaBITNETnode. `BChapter2,OverviewofSettingUpaBITNETNode,Jprovidesanoverviewofthe installationand registration)Ostepscoveredinthisbook. `:Chapter3,PlanningSystemandUserNames,}suggestsG' guidelinesforchoosingnamesforcomputersystemsand%useraccountsonBITNET. `?Chapter4, Installingand Configuring NetworkingW Software,4=Wremindsyoutoinstall DECnet-VAXandCTCP/IPsoftwareifyoursystemwill participateinADECnetorTCP/IP networks,and highlightsaspectsDaofDECnetandTCP/IPconfigurationsthataffectNJE#and/ormailer software. `9C9Chapter5, Installingand ConfiguringNJE Software,A supplementsJnet documentationwithBITNET-specificI instructionsfor installingand configuringJnetsoftware?Band registeringsystemswiththeBITNETNetwork InformationCenter. `GChapter6, Installingand RegisteringaBITNETMailer,Csexplainshowtoinstalland configurePMDFintheDBITNETcontextandhowtoregisteramaileranda-$ domainnameforaBITNETnode. ` ? Chapter7,On-going ManagementofBITNETNodes,D listsBITNET PostmasterresponsibilitiesandprovidesAT  suggestionsfortheon-going managementofBITNET nodes. `, G, AppendixA,AddinganInternet ConnectiontoaBITNET Node,? suggestsstepstotakewhenaddinganInternetI  connectiontoasystemthat previouslywas connectedto6 BITNETonly. ` : AppendixB, OperatingBITNETMail Gateways, explainsH howto configureasystemtoactasaBITNET-Internet+f or BITNET-DECnetmailgateway. ` / AppendixC, MigrationfromGmail, provides supplemen-I>tary informationforsiteswhereGMAILisusedtosend(mailtoInternet addresses.*0|O)*acOR*OmnDWW*nO*O*f O$nQD<  < <  < *x Oh* O~Y! /;OSoftware environmentand associated documentsQOUThisbookassumesthatyouwillusespecificsoftwareproductsNOto implementBITNETanditsmail application,thatyouhavePOorwillinstallthelatestversionofeachprogram,andthatMO^youintendtoupgradeyoursoftwareasnewversionsbecomeOO available.-Forthisbooktobehelpful,youmustinstallatOleasttheminimumversion)xofeach recommendedsoftwareOhproduct.I AOWhenmaking referencestovendorsoftwareproductQOdocumentation,the referencesaretoaspecificversion,called O5the5assumedversion7z5,unlessanotherversionis specificallyLO referencedbyversionnumber.'YoushouldhavethecompleteKO documentationforthe installedversionofthe recommendedLO>productathandwhenworkingthroughthisbook,sincenotLOall informationinvendor documentationis duplicatedhere.NFOForDigitalVAXsystemsrunningVMS,theminimumandNOassumedversionsofrelevantsoftwareproductsarelistedinO5Table1.*O? ULOUnlessstated otherwise,theminimumandlaterversionsofOOsoftwareproducts discussedherefunctionin substantiallytheO<sameway./BOThe commercialmailersoftware recommendedhereis8OPMDF,fromInnosoftInternational,Inc.+(HInnosoft).*YouNO5willneedthe followingInnosoft publicationstoinstallandO configurePMDF: `m6m PMDF InstallationGuide&ReleaseNotesm,Version4.0 `( PMDFSystem Manager'sGuideW,Version4.0Q'BO Additional important informationonPMDF, includingHOsoftware corrections,isreleased regularlyonthePMDFIO5networkforum:) Info-PMDF. Instructionsfor subscribingto#O Info-PMDFaregiveninSection6.7.2ofthisbook.*P?uDOIfyouaremissinganyPMDFdocumentation,orneed1O additionalcopies,contact Innosoft:!A/m250WestFirstStreet,Suite240/ Claremont, California91711U.S.A.G Telephone:(+1(714) 624-7907, facsimile:(+1(714)621-w5319BITNET:III@YMIR)( Internet:'Service@Innosoft.Com; DOMostBITNETmembersitesmakeNJE connectionsamongBOVAXsystemsoverDECnet networks,andbetweenVAX=O5systemsandothertypesofBITNETnodesover5binary,O synchronouscommunications(BSC)linesorTCP/IPQO networks.'Youwillneedtorefertothe following publications(O>ofJoiner Software,Inc.+(>Joiner)>),toinstalland configureEOJoiner'sJnetNJEsoftwareandtherequiredoptions:g `m#m Jnet InstallationGuide m,Version3.4 ` Jnet Manager'sGuide,Version3.5 `ll JnetUser'sGuideMl,Version3.5 `) JnetBSC/370 Manager'sGuideL,Version1.0 `k*k JnetTCPNJE Manager'sGuideVk,Version1.0 MO Additional important informationonJnetanditsoptionsisKOfoundincoverletters,softwareproduct descriptions,andMO5releasenotes.'Releasenotesareshippedinmachine-readableMOformatonthe distributionmedia,andcanbeprintedusingOOthe instructionsinthecoverletters.*ThecoverlettersandKO>softwareproduct descriptionsareshippedwiththeproductOdocumentation.! QOIfyouaremissinganyoftherequiredJnetdocumentation,or5Oneed additionalcopies,contactJoiner:. m450ScienceDrive!PostOfficeBox56301Madison, Wisconsin 53705-0630U.S.A.Gw Telephone:(+1(608) 238-4454, facsimile:(+1(608)238-8986(BITNET: CSC@JOINER# Internet:'CSC@Joiner.Com!WHOThisbookassumesyouhaveaccesstotheVMSExtended@O Documentation Set,! published byDigital EquipmentO5 Corporation(05Digital0;5)onpaperandCompact Disk-Read-FOOnlyMemory (CD-ROM).ToobtainDigitaldocumentation,GO telephoneDigitalat1-(800)-DIGITALintheU.S.A.,orPO>contacttheDigital subsidiaryor distributorinyourcountry.)"GOForrecommendationsonwhichVMS publicationsaremostHOrelevanttothe installationand managementofNJEand=O5mailer software,refertothePrefaceofthes5 Jnet Manager'sO Guide .'# LOSeealsothe publicationlistsinthe recommendedsoftwareNOvendor documentationlistedherefor additional referencesonKO5 prerequisite products, protocols, historical background,andOothertopics.c) w!O 1.2Mailers!on!BITNETOOYoumayhavebeenaskedtoinstallandoperatea ``mailer''DOonyourcomputersystem./Thischapter describestheNOB transmissionofmailonBITNETwithouttheuseofamailer O(jdirect transmission |,Section1.1),tdefinesmailer and%Orelatedconcepts(Section1.2),#listsCREN requirements)OLfor electronicmail(Section.L1.3),'Landattemptstoprovidea6O rationaleforrunningamailer(Section1.4).*)^?**)?0*)~?=*)g{?H02%O1.2BBITNETMailConcepts OUToUregister9UaBITNETnodemeanstodescribeitina?OstandardformatinthedatafileBITEARNNODES  1 ,CO maintainedbytheBITNETNetwork InformationCenter O^(j^BITNIC8^)andtheEuropeanAcademicandResearchONetwork(EARN4)CentralOffice..VariousmethodsareFOusedtogenerateNJEroutingtablesbasedonBITEARNDOhNODESthatare ultimately installedoneveryBITNETJOsystem,enablingeachsystemto originateorforwardNJEKOdatatoanynodeonBITNETandits cooperating networks.*0d/1[21 OVAVmailer>V, asusedinthis document,issoftwarethatDO transmitsBITNETmailinBSMTPformattoNJEusersHO(humanusers, applications,and devices).+ Normally,mailKO`is transmittedbetweennodesbyNJEfiletransferbetweenLOmailersonthosenodes.(MailershaveNJE addresses(eight-CO character usernamesandeight-characternodenames),KOjandcanalsoexchangemailwithNJEusersbydirectNJE'O transmission,if necessary.D3 OOnBITNET,amailgateway.,asusedinthis document,isEOsoftwarethatsendsoracceptsBITNETmailinBSMTP2O5formatonbehalfof addresseeswith}5fully-qualified&O domain-stylenames(FQDNs)).'Some confusioncanresultKOfromthefactthatmailersandmailgatewaysareusuallyNO> implementedas differentaspectsofthe configurationoftheEOsame software,forexample,PMDFonVAX/VMSsystems. 4WLOAfully-qualified domain-stylenameisanameoftheform1O'mailbox_name@subdomain.subdomain.domain.)MyownInternetO5address,!5Arnold@Eisner.DECUS.Org%5,isanexample./ForaEOformal definitionofaFQDN,refertoSection6ofY RFC822:HO StandardfortheformatofARPAInternetTextMessages ,DO>shippedwithPMDFinthe documentation subdirectory.5 OOTheconceptsofmailersandmailgatewaysare illustratedinOFigure1-1.AThefigureshowsthecontentofamailmessage,LO5``BITNETmailis...'',createdbyauseratnodeCALTECH,GOwithmailheaders prependedbytheVMSmailuseragentGO(UA),wrappedinaBSMTPenvelopebythePMDFmailerHO> (Mailer),and transmittedovertheNJEnetworkbyJnetBO(NJE). IntermediatenodesNODE1andNODE2transmitJOtheNJEfiletoitsfinal destination,nodeRICEVM1..AtEOHRICEVM1,theNJEtagisremovedbyRSCS,theBSMTPIOenvelopeis interpretedand discardedbytheVMMailer,NOandtheRiceMailuseragentdeliversthecontentandmailMORheaderstothe addressee,usingtheaddressfromtheBSMTPO envelope.*5OO687 @ORICEVM1servesasamailgatewaybetweenBITNET!OandtheInternet(anWINTERBIT  gateway)./ Therefore,HO< RICEVM1'smailercouldfollow instructionsintheBSMTPPOenvelopetosendcopiesofthemessagetoInternet addresseesXOinsteadoforinadditionto deliveringittolocalusers.)ThisisOEshowninEFigure1-13]Ebythe connectionbetweenthemailer1OandTCP/IPsoftwarewithinRICEVM1.*7O68 WOContrastFigure1-1SwithFigure1-2,which illustratesMOBITNETmaildirectlyoverNJE.Withouttheuseofmailers,KO5CALTECHuserswouldhavetosendaseparatecopyoftheHOmessagetoevery addresseeatRICEVM1,andtherewouldSObenooptiontosendmailtoInternetusersusingtheInternet"O> connectionatRICEVM1.*8FO6*8FO9:  OTo%registeraBITNETmailer(meanstodescribeitinaDOstandardformatinBITEARNNODES.WhilemailersandJO<mailgateways installedaroundBITNETandits cooperatingNOnetworkscould theoreticallygeneratetheroutingtablestheyOuse,calledmailertables,,fromBITEARNNODES directly,LOEinpracticemostsitesgeneratemailertablesfromamuch=Osmallerfile,XMAILERNAMES.XMAILERNAMESisCO automaticallyderivedfromBITEARNNODESeachmonth#OOandmade availablefor'O automaticfile distribution O( OAFD O).!O(AFDis describedinESection6.3.1.) \MailertablesenableFOmailersandmailgatewaysrunningonBITNETnodestoJOYroutemailfiles(inBSMTPformat)toothermailersfor=Odeliveryto addresseesonspecificNJEnodes.*:Ej?w;! tM OTo$register amailgateway%means todescribeitinBOastandardformatinthedatafileDOMAINNAMES,AO5 maintainedbyBITNICforBITNET,EARN,andtheirBO cooperating networks.*DOMAINNAMESismuchsmaller?OthanBITEARNNODESorevenXMAILERNAMES.LikeGO>XMAILERNAMES,itisupdatedeachmonthand availableHOforAFD.DatainDOMAINNAMESisalso incorporatedinLOmailertables,toenablemailersandmailgatewaysrunningEOHonBITNETnodestosendmailfiles(againinBSMTPROformat)tomailgatewaysfordeliveryto addresseesatspecificMO domain-style addresses.(Someofthese addresseesareontheLORsameNJEnodeasthemailgateway,andmailis deliveredJOtothe addresseelocally.-Othersareonsystemsonnon-IONJE networks,andthenon-NJEnetwork(forexample,theVO[ Internet)isusedtodeliverthemailtoitsultimate destination.<! aKOThisbookexplainshowtoregisterPMDFtosimultaneouslyOOserveasamailertohandlemailforaBITNETnodebyitsLO5NJEnameandamailgatewaytohandlemailforaBITNETJOnodebyanyofitsdomainnames.+For VAXclusters,theseIO instructionsexplainhowtosentupPMDFtohandleallOO>thenodesofthecluster,both collectivelyand individually.OAppendixB@explainshowtosetupandregisterPMDFasaJOmailgatewaybetweenBITNETandanexternalnetworklikeOHthe Internet.*<OZOh ]R! 38O 2.2Overview!of!Setting"Up!a"BITNET!NodeIOYoushouldbeabletoworkstraightthroughthisbook,NOwhetheryouareanewBITNETsitestartingfromscratchorMOBa continuingsite reviewingyour configurationandaddingaOOmailer,whetheryouarealreadyontheInternetornot,andJOwhetheryourhave previously installedTCP/IPsoftwareorROLaredoingitatthistime.)(IfyouaddanInternet connectionOlater,seeAppendixA.)*RgOQSNKO Dependingonyour situation,youwillbeskippingcertainMO sections.,Sothatyourworkgoesasquicklyandeasilyas:O5 possible,skipaheadwhenaskedtodoso.VT! ,IOTherearemanywaysto accomplishsomeeffects.+IhaveHOfavoredmethodsthatgivethehighestlevelofnetworkKO5service,areeasiesttomodifyorextendasyournetworkHOevolves,!and,"if all else is equal,"that are somewhatMO standardizedby tradition.(I've consultedapanelofBITNETMO>expertsincomingtotheserecommendations,butwheretherePOisnoclear consensus,I'vemadethefinaldecisionbasedonOmyown experience.! #Z2O2.2BStepstosetupaBITNETnodeAOUWith these assumptionsinmind,!the planning andFOimplementationofyournetwork connectionsaredivided"Ointofourstepshere:V[,,`m1.:Plansystemandusernames\ [LWPlanningisrequiredforthenamesofsystems,users,andHothernetworkentitiesbecausethenamesareveryhardItochangeoncetheybecome established.(SystemanduserEanamesaretheprimaryelementsofyour configuration9thatarevisibletoremotenetworkusers.]~'WThisstepis describedin:WChapter3.B`2.:PlanandinstallDECnetand/orTCP/IPsoftware*]:lOm^zEWIfyouintendtoinstallDECnetorTCP/IP software,L installationofyourmailerwillbe considerably simplifiedEifyouinstallthe DECnet-VAXand/orTCP/IPsoftwareafirst._!?WIfDECnetand/orTCP/IPsoftwarewas previouslyI installedonyoursystem,you'llneedtoreviewhowit?is configuredinordertoinstallyourmailer.`! GWTheactual installationand configurationof DECnet-VAXIandTCP/IPsoftwareisoutsidethescopeofthisbook.a['WThisstepis describedin:WChapter4.`3.:BringupBITNET*a:lObzCWInthisstepyouplanyourBITNET connectionsandH services,installand configureJnet software,bringupDyourBITNETlinkswithadjacentnodes,andregister$ayournodeswithBITNIC.c +KWIfJnetsoftwarewas previously installedonyoursystem,Jyou'llneedtoreviewhowitis configuredinordertoIinstallyourmailer.+Youmayalsobeabletousesome"aofthe suggestionsinaChapter5$Mato streamlineyourJnetJ configurationand/orimprovethelevelofnetworkserviceyourusersenjoy.*c$mOd IWIfyourBITNETnodeisnew,youmayhavetowaitforGseveralweeksforyournodetobecomeknowntootherFsystemsonBITNET.YoumaybeabletocontinuewithJathe configurationofyourmailerifyouhaveanaccountGonanotherBITNETnode,ifyoursystemisalreadyonLthe Internet,orifthe PostmasterofanotherBITNETsite=kiswillingtohelpyouobtaincertainfiles.e !EWInstallJnetafterTCP/IPand/or DECnet-VAX software,LbecauseJnetisanetwork applicationthatcanbelayered-overTCP/IPorDECnet software.f 'WThisstepis describedin:WChapter5.O`4.:Installandregisteramailerandregisteradomainname*f:lOgIWInthisstepyouwillinstalland configurePMDFusingBthe informationaboutyournetwork connectionsyouI collectedintheprevioussteps.-YouwillalsoregisterDayoursystem'sdomainnamethroughBITNIC(ifitisCnotalready registered)andupdatetheBITNETnodeG registrationdatabasetoshowyoursystem'smailerandkdomainname.h!AWInstallPMDFafterNJE,TCP/IP,and/or DECnet-VAXI software,becausemailisanetwork applicationthatisElayeredoveroverNJE,TCP/IP,orDECnet transports.fip<'WThisstepis describedin:WChapter6.*i:lOj! iOFigure2-1Eshowsthesteps describedinthisbookin graphicalOform.*jOFOkl nOChapter7=provides informationonon-going managementofOyourBITNETnode.*lOMlO$ #!$m x0O 3.2Planning!System"and!User!NamesKOThischapterprovides suggestionsfornaming,or reviewingGOthenamesof,yourcomputersystemsandusersintheJOBBITNET environment.'IfthecomputersystemsareonotherMOnetworksaswell,theirnamesonthoseothernetworksmustOalsobe considered.#n KOThischapterdoesnotdealwithnetwork topology.)NetworkJOtopologymustbeplannedforeachnetworkinwhichyourMO5systems participate.'For suggestionsonBITNET topology,seeOSection5.1.*nOP|?)(*}6O3.4.2BPlanSCSNODEand DECnet-VAXnamesGO4OfallthenamesaVAXsystemcanhave,perhapstheGOmost difficulttochangeisthenameusedbySystems?OCommunications Services,!a componentofVMS.AnO=SCSNODEnameis&= required(P=,evenfor stand-aloneVAX*Osystems,ifthesystemuses:~ `mm VAXcluster Software, `%DSNlinkservice software, `l=lLicense ManagementFacilityV1.1orlater,or `VMSV5.5orlater.NCOThe DECnet-VAXnameofyoursystemmustmatchtheGOSCSNODEname,andothernamesareoftenbasedontheO5 DECnet-VAXname., DODisplaytheSCSNODEnamewiththeSystem GenerationOUtility (SYSGEN): Oa$asysgen%:==%$sysgen O$sysgen%show&scsnodeO Parameter%Name5CurrentDefaultMin.Max.UnitJDynamicO9--------------;9---------------------K-------p----J-------OSCSNODE/"BAYACBK""""""ZZZZ"&Ascii! aSOIfnoSCSNODEnameisdefined,orifoneisdefinedthatdoes&OnotmeetthecriteriainSection3.2,%Xtakethis opportunitytoEO5planabettername.+BecauseDECnetnamesmustmatchBOSCSNODEnames,andbecauseDECnetnamesareknownJO throughouttheDECnetnetworkandmustnotconflictwithFO>otherDECnetnames, coordinateanychangesinSCSNODELOnameswiththenetworkname authorityofyour organizationIOandthenamespace coordinatorforyourDECnetnetwork.*}?s{?OSCSNODEnamesmust besix orless alphanumeric currentlyusedbymailer software,however.(Ifyou establishIOaDECDNSnameforyoursystemor VAXcluster,considerOthecriteriain^Section3.2,0andif possible,usea systematicCOHmappingbetween six-characterDECnetnodenamesand ODECDNSnodenames.*^}?sNJOIfyoursystemdoesnot participateina VAXclusterandTOyoudono anticipatethatitwillinthefuture,skipaheadtoO5Section3.4.4.$:5 Otherwise,continuewith5Section3.4.3.*O?*? *)+ 1O3.4.3BPlana VAXclusteraliasnameKO4Ifyoursystem currently participatesina VAXcluster,orSOyouplanthatitwillinthenearfuture,youcangiveitan.O additionalDECnetname,calleda VAXclusteralias.(ThisisNO=toyour advantageiftwoormoresystemsprovideasimilarKO computing environmenttoagroupofusers,an arrangementOcalleda! homogeneous VAXcluster.-(Recentversions;OGoftheVMS documentationsetusethetermsGcommon-O environment randmultiple-environmentinsteadof+O homogeneousandheterogeneous.)' FOEverycharacteristicofthe computing environmentneedOOnotbe identicaltousea VAXclusteralias.+ForpurposesofMO5 electronicmail,a VAXclusteris homogeneousifthesystems@OshareacommonSystemUser AuthorizationFile(`SYSUAF ),JOVMSmailprofile,andbatchqueues.*In addition,youmustIO>setupmailersoftwarefora homogeneous VAXcluster,asO describedin Chapter6.* ZlO^ 4OO Likewise,allofthesystemsina VAXclusterneednotserveTOthesameusersfora VAXclusteraliastobeuseful.(IfnotallQO5thesystemsinaclusterare identical,youcanuseanaliasLOforapropersubsetofthe VAXcluster, sometimescalledaO subcluster>.,Consider establishinga VAXclusteraliasforMO>eachgroupoftwoormorenodesthatsharesaSYSUAFandGOVMSmailprofile.,However,the configurationofmultipleIO homogeneous subclustersonasingle VAXclusterisbeyondIOHthescopeofthisbook..Usethe VAXcluster instructionsMOinthisbookto configurea VAXclusteraliasforonlyone/O homogeneousclusteror subcluster.WMOIfyouintendtousea VAXclusteralias,considerderivingMOthenamesofthesystemsinthe VAXclusterfromthealiasPO5byaddinga modifyingletterordigit.*Forexample,theU.S.COChapterDECUS Symposium timesharing VAXclusternodesDOcouldbenamedDECUSA,DECUSB,andsoon,andthe0O> VAXclusteraliasescouldbeDECUS.NHOMakeanoteofthe VAXclusteraliasnameyouplantoMOuse.,Youwillsetormodifythe VAXclusteraliasname,if.O5 necessary,whenyouworkthrough[5Chapter4.*[lO+*,! $O3.4.4BPlandomainnamesLO4Domainnamesareusedtoidentifycomputersystems(calledOhostsJ)ontheInternetformany applications, includingmail,KOfile transfer,andremotelogin.)DomainnameshaveprovenRO=tobesousefulthattheyarenowwidelyusedformailamongNO non-Internetsystems.'ThisbookassumesthatyouwillfollowDOCRENrecommendationsto establishadomainnameforLOGyoursystemandtousethatdomainnametoidentifyyourJOsystemwhensendingmailtoInternet addressesandother"O domain-style addresses.! WGOTheprimary referencefortheuseofdomainnameson.OBITNETisthefileDOMAINGUIDE  1, availablefromO5LISTSERV@BITNIC D 28g5.'IfyoudonothaveacopyofDOMAINPOGUIDE,obtainacopyatthistime.'If necessary,asksomeoneNOatBITNICoratanotherBITNETnodetoprintapapercopy!O>andmailittoyou.*/1*D"/>R(IOOnlyone second-leveldomainmaybe registeredforeachGO organization.-Allsystemsinan organizationmusthaveEO5thesametop-and second-leveldomains(forexample,OBerkeley.Edu)./The 2DefenseDataNetwork ( DDN )&ONetwork InformationCenter ( NIC"),whichoverseestheHO> registrationofdomainnames world-wide, recommendsthatKO second-leveldomainnamesbelimitedtotwelve characters.d :OOHavingasingledomaincanbea significantissueforlargeIO organizationshavingmany computers,sinceitforcestheKO5chief executiveofficerofthe organization,whomaycarePOlittleforthesematters,todelegatethenamingof networkedQOsystemstoasingle authority.'Nomatterhow difficultitmayQO>beforyour organization,however,thisissuemustberesolvedIOinternaltoyour organizationbefore proceedingwiththeOplanningprocess!tJ"OUsingthecriteriainFSection3.2,choose:*FF|?s `mDma top-leveldomainanda second-level subdomainfor%yourentire organization, `EDE third-level subdomainsforeach VAXclusteraliasandF third-levelhostnameseachhostwithouta VAXclusteralias,and `vGv fourth-levelhostnamesforeach clusteredsystemthat$hasa VAXclusteralias.  HOThe third-level subdomainforeach VAXclusterorstand-GOalonesystemcanbethesameasthe VAXclusteraliasEO5orDECnetnodenameforthatsystem..A fourth-levelGO subdomaincanbetheDECnetnodenameofa clusteredLOsystemoramodifierto VAXclusteraliasto constructtheCO>DECnetnodename.*Forexample,theDECUS Symposium4O VAXcluster mentionedasanexamplein/Section3.4.3?Ocouldusethe domain-stylenameSympos.DECUS.OrgAOHfortheentire VAXcluster,andA.Sympos.DECUS.Org,HOB.Sympos.DECUS.Org,andsoonasthe domain-stylenames8Ofor individualnodesDECUSA,DECUSB,etc.*/Z?FOIfa VAXclusteror stand-alonesystemisathemainPO computingfacilityforan organization,itcoulduseonlytheFO5second-and top-levelnamesasits domain-stylename.EOForexample,themain computingfacilityforIndianaHO Universityof Pennsylvaniaisa VAXcluster.,TheclusterNO>bearsthe institution'stop-and second-leveldomainsasits'O domain-stylename:'IUP.Edu.g =DOYourorganization's lower-leveldomainnamesmustbeCO coordinatedbyyourownorganization'snetworknameRO5 authority.'Ifyouarenotthat authority,contactthe authorityMOtorequestthatthenamesyouhavechoosenbeassignedtoOyoursystem.x NHOMakeanoteofthe domain-stylenameyouplantouseKOforthissystem,andif applicable,the domain-stylenameOO5youplantouseforthe VAXclusteralias.*YouwillregisterEOthe second-leveldomainwhenyouworkthrougheitherOSection3.4.5 orSection6.6.3,,` dependingonthecircumstances,OO>andyouwillsetormodifythedomainnameforyoursystemIOand,if applicable,its VAXclusteralias,whenyouworkOthroughChapter4.*O?*? *lOW, +-J ?O3.4.5BRegisteradomainnamewiththeDDNNICEO4Yourorganization's second-leveldomainname(ormoreOsimply,your)domain1^)mustbe registeredwiththeDDNDONIC.Oneofthree situationsappliestoyourcase:! M`m1.:Ifyourdomainisalready registeredwiththeDDNNIC,>nofurtheractionis necessary.'Skipaheadto,Section3.4.6.J`E2.:Ifyoudonot anticipate connectingyour organizationLtothe Internet,atleastforthe foreseeablefuture,theCBITNICwillregisteryourdomainwiththeDDNNICFOonyourbehalf.-Detailed instructionsareprovidedin9DOMAINGUIDE.RegisteryourdomainthroughEBITNICwiththeDDNNICwhendirectedtodosoinYSection6.6.3.$YFornow,skipaheadto YSection3.4.6.S`3.:Ifyouare establishinganInternet connection,orintendtoK0dosointhenearfuture,youmustregisteryourdomainHdirectlywiththeDDNNICatthistime.* Referencesto9 instructionsareprovidedinthissection.*,?*? * ?! aROToregisteryourdomain,youwillneedaccesstoan electronicMOmailaccountthatcan communicatewiththeInternet(eitherJO5onanInternethostoronaBITNETnoderunningmailerEOsoftwarethatconformstoCREN technical requirementsJOfortheuseofINTERBITmail gateways).*AguestaccountIO>onthesystemtowhichyouwillbemakingyourBITNETJOlink,as suggestedintheTECHREP informationpacket,isTOideal.)ItisalsopossibletoregisteradomainwithonlypaperMOHcorrespondence,buttheprocessisslowerandmoreawkward. $MOSendanempty electronicmailmessagetoService@NIC.DDN.MilEOwiththesubjectline ``NETINFODOMAIN-TEMPLATE.TXT''.BO5TheDDNNICdocumentserverwillsendthedomainNO applicationtemplatetoyouby electronicmail.&Forexample:OMAIL>/SEND& NL:/NOEDIT OZTo:"zZIN%"SERVICE@NIC.DDN.MIL"OSubj:&zNETINFO%DOMAIN-TEMPLATE.TXTO MAIL>]EOYouwillalsofindacopyofDOMAIN-TEMPLATE.TXTinODOMAINGUIDE.B! NOReviewthetemplatefile.&For additional background material,FOreviewDOMAINGUIDEandtheRFCsthatit references.MO5Ifyoustillhave questions, telephonetheDDNNICatthe7O toll-freenumberlistedinthe template.T*@OTooperateadomain,youmustalsoarrangefor=nameOserviceDd.,AnameserverisanInternethostthatconvertsGO5FQDNstoInternetProtocol(IP)numeric addressesthatGOcanbeusedbyTCP/IP software.-YoumustarrangeforHOboth authoritative (primary)andbackup (secondary)nameEO>serversforyourowndomain..Usuallyan organizationOOoperatesaprimarynameserverononeofitsownhostsandJOrecruitsoneormore organizationstorun secondarynameMOHserversingeographicallyand logicallyremotepartsoftheHO Internet.- Additional informationonnameservicecanbe>OfoundintheRFCs referencedinDOMAINGUIDE. WROCollectallthe information requestedbythe template,edittheTOon-linecopyofthe template,andsenditby electronicmailtoEO5Hostmaster@NIC.DDN.Mil.(YoushouldreceivereturnmailJO acknowledgingthe registrationofyourdomain(orrarely,OO notifyingyouofaconflictwitha pre-existing registration)-O>withinabouttenbusinessdays.F MOAfteryouhavereceivedacknowledgmentofyour registration,KOyoucanusetheInternetWHOIS applicationtocheckthatMO5the registrationisintheDDNNIC'son-line database.*ForMOexample,ifyouarethe PostmasterforthedomainASU.Edu,OOtocheckyourdomain registrationdatafromanInternethost3O>runningVMSandTGV MultiNet,enter: O$whois&asu.edu/O Arizona&State& University% (ASU-DOM)STempe,%AZ Domain%Name:%ASU.EDU"%Administrative%Contact:H/m Cantrall,%ArthurK(AC85)K#icsadc%asuic.bitnet@CUNYVM.CUNY.EDUj...-,.D `!O3.4.6BPlanNJEnamesNO4WhiletheNJEnameofasystemneednothaveanyrelationNOtoitsothernames,itwillbeeasierforusersandtheirIOcorrespondentstoremembermail addressesiftheDECnet-HO=VAXandNJEnamesandthehostportionofthedomainQOnameofasystemareallthesame.) Likewise,ifasystemisLOpartofa VAXcluster,theDECnetaliasnameandtheJnet/OGclusternameshouldbethesame. WBONJE user and system names must be eight or lessO alphanumericorIBMnational characters,andthefirstIO5 charactermustbe alphabetic.-However,avoidtheuseof+OtheIBMnational characters( $ , @,and # ),astheyarenotFO permittedinotherkindsofnetworknames,andcause1O>problemswithsomeuser interfaces. GOForother suggestionsonplanningNJEnames,referto4OSection6.1,NJENodeNaming,inthe  Jnet Manager'sGuide .t! JSOMakeanoteoftheNJEnameyouplantouseforthissystem,ROandif applicable,theNJEnameyouplantousefortheJnet?O5cluster,onthe worksheetinChapter6ofthe5 Jnet Manager'sO GuideJ.'YouwillsetormodifytheNJEnameforyoursystemROand,if applicable,itsJnetclusternamealias,whenyouworkO>through>Section5.4,34>andyouwillregistertheNJEnames0OwithBITNETwhenyouworkthroughSection5.7.*~?(*Z|?a/ .0p F,O3.4.7.1C POSTMASTERandPOSTMASTJO)TheInternethaslongrequiredthatthereservedmailboxNO``Postmaster''be supportedoneveryhost,andthatmailtoFO Postmasterbe forwardedtothepersonwith managementNO3responsibilityforthemail applicationonthathostorforJOtheentiresystem(RFC822,Sections6.3and3.4.7;RFCHO1123,Section5.2.7).-In1991,CRENadoptedastandardKO<thatallBITNETnodesmust similarlysupporta PostmasterMOaddress,anditseight-character truncation, ``Postmast'',inQOany combinationofupperandlowercaseletters.(ForthefullHOFtextofthis standard,seethefilePOSTMAST STANDARD,+O availablefromLISTSERV@BITNIC.! NROInordertoserveitsintendedpurpose,the PostmasteruseronAOVAX/VMSBITNETnodes,called POSTMASTER(inupper'O5case)inthisbook,must:^4 `m)mBeabletoreceiveVMSmail.ReAWThelogin directoryfor POSTMASTERmustexistonEamountedand accessibledevice./Ifdiskquotasare?enabled, POSTMASTERmusthaveamplediskquota.BaTheSYSUAFflagDISMAILmustnotbesetforthe POSTMASTERentry. `979Notforwarditsmailtoanothersystem.yO@WMailfor POSTMASTERmaybe forwardedtoanotherFuseronthelocalsystemsothatmailto POSTMASTERFreceivesprompt attention,but forwardingtoaremoteJasystemcouldsubject Postmastermailtodeliveryfailures9duetofailureofthe underlyingnetwork.R<WIf POSTMASTER's mailis forwarded to anotherIlocaluser,itshouldbe forwarded consistentlyatboth@theVMSmailandPMDFlevels./Theusertowhich?a POSTMASTER'smailis forwardedmustbeableto9receiveVMSmail.'(Seethe precedingitem.) `9>9Neversend automaticrepliestoreceivedmail. ?WMany automaticprogramsontheglobal networks,H includingmailersandotherservers,senderrorreportsHtothe Postmastermailbox.+Topreventmailloops,theyIadependonthe Postmastertonotsend automaticreplies.A POSTMASTER,or,if POSTMASTER'smailis forwardedGtoanotherlocaluser,theuser receiving POSTMASTER'sFkmail,mustnotbean automaticserveroremployanyB automaticresponseor filtering programs, includingE ``vacation''programsandDELIVERscriptsthatreturntordeletemail.F KODuringthe installationof Jnet,!youwillbeaskedif a;O POSTMASTER user should be created.3The PMDFIO5autoconfiguration procedureasksthemailaddressoftheGO Postmaster.+Recommendationsfortheseoptionsaregiven OinSection5.3 GandSection6.3.+Fornow,plantoreservetheIO> POSTMASTERuserforthisspecialpurpose,and determine,LOif applicable,where POSTMASTER'smailistobe forwarded.*}?*}?0;:<u wK&O4.3B Configuring DECnet-VAX OU DECnet-VAXisaVMS%Usystem integratedproductU,thatROis,itisshippedand installedwiththeVMS operatingsystem.HONo installationis required..Youmust,however,havea5O^ DECnet-VAXlicensetousetheproduct.U+COToenabletheuseof DECnet-VAX software, registerHOthelicensebyenteringthe informationontheProductFO5 AuthorizationKey(PAK)intothelicense database, asO explainedinthe3 VMSLicense managementUtilityManual .g =GOForthemoststraight-forward DECnet-VAXconfigurations,JOyoucan configureyoursystemautomatically,as described'O5inSection3.3.2.2ofthe+5 Guideto DECnet-VAX Networking v5.MOIfyouwillhavea VAXclusteraliasnameforthissystem,KOmanuallydefineitusingthecommandsinStep9ofthatKO>section.(Usethenodenameand VAXclusteraliasnameyouOselectedinSection3.4.2 andFSection3.4.3ofthisbook.*Z?}*FZ?g=FOIfyouwillinstalland configure DECnet-VAXsoftwarePOonthissystem,doitbefore installingand configuringJnet,O5 describedin5Chapter5.35The installationand configurationofHO DECnet-VAXsoftwareisoutsidethescopeofthisbook.*lO>=?Xw.7O4.6BTCP/IP installationand configurationCOUYoumayrequireTCP/IPsoftwareonyoursystemtoJO participateintheInternetoraTCP/IPnetworkinternalGOtoyour organization.+ForBITNET,yourTCP/IPsoftware#O^mayhavetwo purposes: `m?mYoumaywanttomakeyouBITNETlinkoveran+Internet connection,usingtheBITNETII orJTCPNJEPprotocoltosaveonthecostofa dedicatedleasedlineforEwBITNET purposes.)This configurationrequiresthatyou>useTCP/IPsoftware supportedbyJnetTCP/NJE. `OBOYoumaywanttosend electronicmailtoInternetF addresseesdirectlyoveranInternet connection,using!theInternetstandard*SimpleMailTransferProtocolY(SMTP)=Y protocol.+This configurationrequiresthatyou5useTCP/IPsoftware supportedbyPMDF. JOByusingsoftwarethatis compatiblewithbothJnetTCPKONJEandPMDF,youcanuseyourTCP/IPsoftwareforbothHO5ofthesepurposessimultaneously,acommonandflexibleO arrangement.MOJnetTCPNJEV1.1,theversioncurrentwhenthisbookwasBO published,supportstheseTCP/IPsoftware products:5| `m7mCarnegieMellon UniversityCMU-TEKIP/TCP `ADigital VMS/ULTRIX Connection(alsoknownasUCX,CEandrenamedTCP/IPServicesforVMS beginningwithV2.0) `1NetworkResearchFUSIONforVAX/VMS `TGVMultiNet `3The WollongongGroupWIN/TCPforVMS+ KOConsultJoinerforthemostcurrent informationonTCP/IPLOproducts compatiblewithJnetTCPNJE, including applicableEO5 versions,supportrecommendationsand limitations,and%Ovendorcontact addresses.COPMDFV4.0, theversioncurrentwhenthisbookwasBO published,supportstheseTCP/IPsoftware products: `m7mCarnegieMellon UniversityCMU-TEKIP/TCP `)Digital VMS/ULTRIX Connection `l1lNetworkResearchFUSIONForVAX/VMS `!NovellExcelanTCP/IP `k$kProcessSoftwareTCPware ` TektronixTCP/IP `iiTGVMultiNet `3The WollongongGroupWIN/TCPforVMS# MOConsultInnosoftforthemostcurrent informationonTCP/IPBOproducts compatiblewithPMDF, including applicableEO5 versions,supportrecommendationsand limitations,and%Ovendorcontact addresses.! WLOSincemostTCP/IPnetworksare eventually connectedtotheMO Internet,youshouldinstallyourTCP/IPsoftwareinawayNO5thatallowsyoutotake advantageofanInternet connectionVOinthefuture,evenifyoudon'tplantoconnecttotheInternetGO immediately.-Toprepareforeventual connectiontothe!O> Internet,youshould:! Y `mHmApplyforanetworknumberandregisteradomainnamewiththeDDNNIC. `EMEInstallTCP/IPsoftwarethatconformstoallthe applicable9Internet standards,as documentedinRFCs. `?Useyourassignednetworknumberand registered@vdomainnameinthe configurationofyourhosts. `=Usefully-qualifieddomainnames(forexample,HMStat.Wisc.Edu)insteadof short-formnames(forexample,=Stat),andtrainyouruserstodothesame.! aHOIfyour organizationhasmorethanone departmentthatEO maintainsitsown computers(forexample,acomputerHO5science department,an engineeringschool,administrativeJOdata processing,andanacademiccomputercenter)butnoKOstrong traditionofcentralnetwork management,checkwithJO>eachsuch departmentto determinewhetherthat departmentLOhasalready registeredadomainnameforyour organizationIOorbeenassignedanetworknumberbytheDDNNIC.SeeOHSection3.4.47Hfor additional informationonthisstep.*O ?kGOWhetheryouhavealready installedTCP/IPsoftwarebutEOmustchangethe domain-stylenameyouareusing,orMO5are installingTCP/IPsoftwareforthefirsttime,settheIOhostnameofyoursystemtothenewvalueyouplanned OinSection3.4.42and registeredwiththeDDNNICinO>Section3.4.5.6G>Followthe instructionsforyourTCP/IPLOsoftwaretosetthehostnameofyoursystem.,IfanotherNOnamehasbeenwidelyusedontheInternetforyoursystem,LOHyoumaywantto configureyoursoftwareto advertisethat#Onameasasynonym,orhostalias)5,butbecertainthatyourIOsoftwareisusingyour registered,fully-qualifieddomain.ORnameasitsofficialhostname.*?*O?! WNOBecausetheInternetrulesrequireyoutohavea PostmasterJOmailbox,yourTCP/IPsoftwaremayrequireyoutospecifyJO5whatVMSuseristoreceivemail addressedtotheSMTPOO Postmastermailbox.'To facilitatethe delegationof PostmasterOOduties,specifythatsuchmailistobesentasVMSmailto&O>VMSusername POSTMASTER. `IOIfyoursystemisamemberofa homogeneous VAXclusterLOandyourTCP/IPsoftwarepermitsit, configurethedomain-MO5stylenameofthe VAXclusterastheofficialhostnameofLOyoursystem,and configureaspecific domain-stylenameas2Oahostaliasnameforyoursystem. KOIfyoursystemwillbeonbothBITNETandthe Internet,HOconsider operatinganINTERBITmailgateway.' InformationDO5onrunninganINTERBITmailgatewayisprovidedinOSectionB.3.*OP?t_5LOIfyouwillinstalland configureTCP/IPsoftwareonthisQOsystem,doitbefore installingand configuringJnet, described O5in5Chapter5.;T5The installationand configurationofTCP/IP additional important information.V-,,OSpecificrecommendationsfollow:_.5 `m*mNumberofNJEnetworknodes:V/ [,IWSpecifythatthereare4000nodesinyourNJEnetwork.BThisanswerwillcause JANCONFIGtorequestspaceIfor4050nodesintheJnetsection,allowingabout14%Bafreespace.-Theamplefreespacewill accommodateIfuture variationinthenumberofNJEnamesdefinedinEBITEARNNODESwithoutthe necessityofcheckingfreeKkspaceeachmonth.(The resultingJnetsectionwillrequire463globalpages. `BBNJEnames:0RmDWIfyoursystem participatesina VAXclustersystem,A JANCONFIGwillaskyouifyouwanttodefineaFJnetclustername..Inanyevent,itwillpromptyouHafortheNJEnameofyoursystem.(Enterthenamesyou! previouslyplannedinSection3.4.6. `99Timezone:*0|?1! BWUsenumericoffsetsfrom UniversalTime(UT,once?called GreenwichMeanTime,orGMT)insteadofC customaryUnitedStatestimezoneabbreviations,evenGathoughtheyare permittedbyRFCs822and1123.(YourJsystemswill participateinaglobalnetworkwherethereKisnostandardfortimezoneabbreviations,andwhereeven:kcommontimezone abbreviationsare ambiguous.R2 (HWNumerictimezone designationscanbe subtracteddirectlyHfromtheadjacentlocaltime displayedinmailheadersHtogetUTforeasy correlationofmessagetimes.+TheyEaare understood globally,andavoidthe appearanceofL ``Internetprovincialism'',theviewthattheUnitedStatesMisthecenteroftheglobalnetworksandtherestoftheGkworldissomehowless important.*Be sensitiveanduse+numerictimezoneabbreviations!13JWMany referencestodonotclearlystatewhetherpositiveKoffsetsfromUTareeastorwestoftheprime meridian.NPositiveoffsetsareeast,so,forexample,mostofwesternBaEuropeobserves+0100whenSummerTimeisnotinIeffect.,NegativeoffsetsarewestofUT,sotheUnited@StatesEasternTimeZoneobserves-0500whenon@kEasternStandardTimeand-0400whenonEasternDaylightTime.4 RMWEntertheoffsetusedbyyoursystemclock.'IfyouchangeGyoursystemclocktoobserveDaylightSavingsTimeorLSummerTimetwiceayear,youwilledittheJnetstartupDafileJAN_SYS:JANLINKS.JCPtoshowthechangedoffset1atthesametime,as explainedinSection7.5. `99Localservers:*4||?A5+DWYour organizationshould establishasecuritypolicyDonwhetherto configurebatchserveronBITNET,asCVMSbatchjobs submittedthroughJnet'sJOBserverGamustcontainVMS passwords,andtheconfidentialityofGBITNETfilesisnotassured.*NeversendingbatchjobsFoverBITNETtorunin privilegedaccountsunlessyou6! V hKYhtrusttheconfidentialityofthefileon forwardingnodesFYandknowthatyourjobwillnotbequeuedonthose6Ynodesformorethanafewmoments,or BYcanaccessthesystem interactivelytochangethe7Ypassword immediatelyafterthejobruns.7JW ConfigurebatchandprinterserversonlyonJnetclusterEnodeswithexternallinks,becausebatchandprinter@serversarenormallyusedonlybyremoteBITNETEausers,andnotbylocalVMSusers.-TheserverscanIqueuejobstobatchqueuesandprintersrunningonanyF VAXclusternode,evennodesnotrunningJnet,iftheHknodessharea batch/print subsystem.+(AllthenodesofDa VAXclusternormallysharea batch/print subsystem,Dandthis arrangementisrequired beginningwithVMS!tV5.5.)-Ifyouexpectt local*}tuserstosendfilestoyourFBITNETbatchandprintservers, configuretheserversL% homogeneouslyonallthenodesofaJnetclustersothatK~userscansendjobstoserversattheJnetclustername)fromanyJnetclusternode.{RPS7D BO5.4.2.5CDeferthecreationofJAN_SYS:JANROUTES.JCP7O)Deferthecreationoftheroutefile( X) Jnet Manager'sGuide p),ROSection7.4.3).+Thecreationoftheroutefileis discussedinOSection5.6.*DO|?\UTVR \3O5.4.2.8CSkip instructionsforLMD.COMIO)JnetversionsafterV3.3usethelogicalname JAN_SPOOLMOforthe directorytocontain transientfiles,whileearlier;OversionsusedJAN_SYS.Section7.6.2ofthe Jnet Manager'sO3 GuideB83asksyoutodefineasearchlistforJAN_SYSinAOJAN_SYS:LMD.COMsothatPMDForother alternativeOOmailhandlerscanfindinboundmailfiles.,ThisstepisnotKO< necessarywhenusingPMDFV4.0orlater versions,becauseCOthe replacementfilesLMD.COMandLMD.V35,suppliedKOwithPMDFV4.0,already incorporatethischange.*YouwillPOFreplaceJnet'sversionofLMD.COMwithoneofthesefilesasOyouworkthroughSection6.3.7.*Ra?ZY[\ <&O5.6BInstallBITNETtablesOOUNJEroutingrequireseverynodetohaveatableofalltheKOnodesinthenetwork.-Foryournodetofully participateOOinBITNET,youmustobtainalistofallthenodesintheNO^network,andyournodemustbeaddedtotheroutingtablesLOofeveryothernode.,Thissectionprovides suggestionsforOsettingup initial>routingtablesforyournodeorJnetcluster.LOhAfteryouhave registeredyournodeswiththeBITNIC,youAOwill automaticallyreceiveupdatedtablesmonthly.rSection5.7KOgives instructionson registeringyournodessothattheyLOrcanbeincludedintheroutingtables generatedfornodes#O throughoutthenetwork.Section5.8$} discusseshowtableson%O#othernodesareupdated.*\r|?a*\}?]! TOTocreateaninitialroutingtableforyourfirstoronlynode,NOyoumusteditalistofBITNETnodesintoafileofJnetBO5ControlProgram DEFINE/ROUTEcommandsandstoreitFOasJAN_SYS:JANROUTES.JCP.IfyourpeernodeisaVAXSOrunningJnet,thisisasimplematter.&UseyourfavoriteeditorQO>tomakethenameofyourpeernodetherouteforeverynodeHOinthenetwork.*Eachlineof JANROUTES.JCPmustbeofOtheform:OtDEFINETtlinknamet/ROUTE=(tpeername&!%optional%comment^aMO Normally,adjacentnodes(links)aredefinedina differentLOfilethan non-adjacentnodes (routes),soyoumustaddtoRO5yourroutingtablesroutesforallthenodesthatareadjacentOOtoyourpeernodebutnotadjacenttoyourownnode.)TheseLOnodesmaybelistedascommentsintheroutingtableyouCO>getfromyourpeer.+Ifnot,sendtheNJEcommand>QUERYOSYSTEMLINKSBtoyourpeerifitisaVAXorIBMVMsystem,TOor telephonethe Postmasterofthepeernode,togetalistofOHadjacentnodes._! mROFor additional informationonsettingupinitialroutingtables,&OseeSection7.4.3ofthe  Jnet Manager'sGuide.*InstallyourSO5initialtables manually,as describedinthatsection,andwatchKOformessagescausedby duplicateentries,typing mistakes,Oandothererrors.a` 7UOIfyouare configuringaJnetcluster,installtheinitialtablesMOforthenodewithyourfirst(oronly)external connectionIO5andstoreitinthe directoryJAN_SPECIFIC:[SYS].CreateMOasecondtable,routingeverynodeoutsideofyourclusterNOthroughthefirstnode,andstoreitinthe directoryJAN_AO> COMMON:[SYS].ThissingleroutingtablecanserveMOeverynodeinyourJnetclusterexceptnodeswithexternalJO connections.*(Ifyou configurea full-meshtopologyamongTOHthenodesofaJnetclusterandrequestroutingtablesforeachROnode,youwillfindthatthetablesfornodeswithoutexternalOlinksare identical .)/`^c>v! V%O5.7.4B RegisteringanodeHO4TheremustbeanodeentryinBITEARNNODESforeachRONJEnametobeintheroutingtables.'YoucreatenodeentriesDOinBITEARNNODESbysendingADDNODEjobstepstoO=UPDATE.ywONOThissection describes informationrequiredtocreateanodeGOentryforaVAXsystemrunningVMSandJnet.,AnodeLO5entrycontainsdataaboutaspecificnodeonthenetwork.DOOnlytheTECHREPorADMINatthememberlevelmay*Oaddnewnodesforamember.x! QOIfmorethanonepersonistohave authoritytocreatenodesMOandmakeotherchangestoyourmemberentry,createpeopleIO5tagsforeach authorizeduserand referenceeachpeopleOtaginthe:ADMIN=tag.)ThisisabettersecuritypracticethanOOhavinga privilegedaccountthatissharedbymorethanone%O>person.'Soentrieslike:GO:P_SARNOLD.Stephen%L.%Arnold;ARNOLD@DECUS;+1%608%238.7835EO :P_MGRACEFF.Mark&Graceffa;GRACEFFA@DECUS;+1&508%467.4526>OS:P_KMEANY;Kevin%Meany;MEANY@DECUS;+1%508&467.43460O:ADMIN.P_SARNOLD& P_MGRACEFF%P_KMEANYy iOarebetterthanLO:P_TECHREP.DECUS&BITNET%managers;TECHREP@DECUS;+1&608%238.7835OP:ADMIN.P_TECHREPzaFOwhereArnold, Graceffa,andMeanyhaveaccesstotheOTECHREPaccount.-{ HOWhilePOSTMASTshouldbe registeredasthecontactforKOproblemswithmailersoftwareonyoursystemas described O5in5Section6.5,2_5donot routinelyusethe POSTMASTERIOaccountformanagingyourBITNETsystem,becausecertainFO software, including LISTSERV,ignorescommandsinmailAO>from POSTMASTERorPOSTMASTtoavoidmailloops.GOInstead,use specific,personalaccountslistedinthe:ADMINMOtagfor managementtasks.( Nevertheless,itis permittedandCOH recommendedtoregister POSTMASTER(or POSTMAST)asROthecontactpointfor questionsand recipientsofroutingtableOupdates.*{?| ROAsampleupdatejobsteptocreateanentryfora stand-alone(OVAX/VMSsystemisshowninExample5-2.TheUPDATEMO5jobstepstocreatenodeentriesforatwo-node VAXcluster6OwithaJnetclusternameareshowninExample5-3.ROFeaturesofthejobstepsare explainedinthe followinglist.*|O}*|PO~!  t1;tUPDATEusesthenodename specifiedontheltADDNODEcommandtosetthe:NODE%tag.+Donotspecifythe:NODE %taginUPDATEjobs. 2LUsersatthisnode,andallnodesrunningrecentversions8ofJnet,canreceivefilesinVMSDUMP( VD),NETDATA V( VND9V),PUNCH( VPUAV),PRINT( VPR V),andDISKDUMP( "VDD mV).formats,inorderof preference. .39.ForJnetV3.5andlater versions,specifyu. :MSGS.YES.,oromit the`:MSGS>7tagsfrombothnodeandJnetclusterentries,% acceptingthedefaultof< :MSGS.YES".(ForJnetV3.4and=7earlier versions,itwas necessarytospecify7:MSGS.NO :7forI VAXclusterentries.(AllversionsofJnetsupportmessageEto VAXclustermembersand standaloneVAXsystems,soAalwaysspecifyA :MSGS.YESWAintheir entries.) 4 The|:LINKSntags(f:LINKS1through:LINKS99) specifiesEotherBITNETnodestowhichyournodehasadirectOq connection.)Ifalinkisnota9600baudleasedline,codeHthelinktypeandspeed immediatelyafterthenameinD# parenthesis..Formore informationonlink definition${ parametersrefertotheK{:LINKSJ{taginNEWTAGS DESCRIPT.!NWIfalinkisavirtuallinkbetweentheJnetclusternameIandoneoftheclustermembers,codethelinktypeas(P,999M)(a dedicated, veryfastlink).! MWIfanodehasmanylinks,youmaywanttoorganizetheseKbytype.+Forexample,youcanputalllinksexternalto your organizationon:LINKS1),all intraclusterlinksona:LINKS2Aa,allTCPNJElinkstoUNIXonyourcampusto:LINKS34,anda temporarylinkbyitselfon:LINKS4 . 95!9Specifythedate,in9yyyymmdd9format,inthe9:CONNECT"9tagto9showafuture connectiondate,orspecifyREADYytoindicateGanodeis operationalonthedatetheUPDATEjobisB submitted. 6Forthe:MACHINEItag,specifyeitherDigitalandtheBsystem marketingmodel,asshowninthe examples, sor8sDigital VAXcluster's,forJnetclusternames. 7 They:ROUTTAB@tag specifiesthetypeofroutingtablestobeGK generatedforthisnode,theirsource,andtheBITNET>addresstowhichtheyshouldbesent.(SpecifyAJNETtables,GthatNETSERVistogeneratethetables,andgivetheJT Postmaster'sNJEaddress(notthenameofapeopletag)Kasthe destination.'Donotputaspaceafterthecomma.! !*WFor VAXclusternodes,specifyW :ROUTTAB.NONEWforallentriesKexceptthe PrincipalNodeandtheJnetclustername.'YouAwillonlyreceivetworoutingtableseachmonth.c`d 2)O5.8BWaitforroutingtablesLOUWhenyouregisteryournodeswithBITNIC,as describedinOSection5.7,@ informationaboutyournodeswillbe distributedEO throughoutthenetworkinthenextupdatecycle.0AnBO^outlineoftheupdatecyclescheduleisgivenin^Section5.8.1.KO Suggestionsfor monitoringthe installationoftableswithLOroutestoyournode,andfor encouragingother Postmasters;Ohtoinstallthenewtables,areprovidedinhSection5.8.2.OO Instructionsforthe installationofyourowninitialmonthly!Otableupdatesarein&Section5.8.3.*Op}?a*!?*+?*&?feg ,O5.8.3B InstallinginitialtablesEO4Whenyoureceiveyourownroutingtables, theywillCOcomeasfile transfersto POSTMASTER(ifyouhave(Ofollowedthe suggestionsin-Section5.7)andbenamedO=nodenameAz= .NETINIT.Receiveeachroutingtableasthefile?OJAN_SPECIFIC:[SYS]JANROUTES.JCPonthe appropriateQOnode,excepttablesforJnetclusternames.'Suchtablesshould?OGbereceivedintoJAN_COMMON:[SYS]JANROUTES.JCPonTOanynodeoftheJnetcluster,tobesharedbyallJnetcluster6Onodesthatdonothaveexternallinks.*-?aW1OIfyoufollowedthe suggestionsinSection5.4.2.9,8thenewLOtableswillbe automatically installedbythenextnightlyGO5JANTIDYrun.(WhenyourreceivetheJANTIDYreporttheLO followingmorning,youcanpurgetheoldtables.*FormoreJO informationon installing subsequentmonthytableupdates, O>see>Section7.4.1.*F?S*?>P &MOConsiderusingRMSversionnumberstoidentifytheversionsBOof JANROUTES.JCPandotherfilesthatareupdatedEO5monthly.0Thesefileshaveinternal four-digitversionNOnumbers, consistingofthelasttwodigitsoftheyearandPOtwodigitsforupdateinthecurrentyear,forexample,9202NO>forsecondsetoftablesin1992.-UnlesstherearespecialLOtableupdates(usuallymadetocorrecta problem),versionOyymmAtablesarethoseissuedatthe beginningofthe mm thIOHmonth.-Thefilename,type,andversionofyournode'sMOsecondsetoftablesroutingtablesin1992wouldthusbeOJANROUTES.JCP;9202.rqs}nSO6.3B ConfigurePMDF5OUThissectionprovides instructionsfor:K6!:`m1.: Obtaininginitialmailertables(Section@m6.3.1)>`2.:RunningthePMDFautoconfiguration procedureE(SectionE6.3.2)>`3.:Manual steps to complete PMDF configuration(Section 6.3.3-Section6.3.7)*+0?*?*?*?5 LOThesection concludeswithalistofPMDF instructionstoO avoidG,eitherbecausetheyarehandledbyautoconfigurationFO5orbecausetheyarenot recommendedforBITNETnodesO(Section~6.3.8).*jP?!tsuVU-O6.3.2BRunPMDFautoconfiguration0O4Section3.2andChapter4ofthe#4 PMDF InstallationGuideO &ReleaseNotes;describeand illustratetheautoconfigurationJOofPMDF.Thissectionprovides additional suggestionsfor5O=PMDFautoconfigurationofBITNETnodes., >`m1.:If DECnet-VAXis availableonyoursystem,+mSETHOST/LOGItothesystemtobeautoconfigured.+ThelogprovidesaIvaluablerecordoftheautoconfigurationsession.*IfyouKwareautoconfiguringa VAXcluster,sethosttothefastestH availablesystem,asautoconfigurationiscomputationally( intensive!I`2.:Logintoafully privilegedaccountto autoconfigureEPMDF.Apersonalaccountis preferredtotheSYSTEMAYaccountforthispurpose..Digital recommendsthatBSYSTEMbeusedonlyforsoftware installationandB  standalonebackups,andtheuseofSYSTEMrendersGbuselessthe configurationfilecomments identifyingthe)userwhoranthe procedure.C`:3.:Setyourdefaultdeviceand directorytoPMDF_ ROOT:[TABLE].D`4.:Theautoconfiguration procedurechecksthevaluesEjofcertainDCLsymbolstoset configurationoptions.ASettingthesesymbolsis recommendedovereditingBtheautoconfiguration procedure,becausechangestoFttheautoconfiguration procedurewillbelostwhenyouDupgradePMDF.Youcaneithermakea permanentnoteH%onwhatsymbolsyouset,orifyousetmanysymbols,H~writeacommand proceduretosetthesymbolsandthen1runtheautoconfiguration procedure.fp<<WSettingthe followingsymbolsis recommended:! C  h'YhFor all BITNET nodes,#setBh SKIP_XMAILER "hto%Y"/nodename1/nodename2/.../"I,wherethenodename *sGYarealistofalltheNJEnamesforyoursystemor=Yq VAXclusterthatappearinXMAILERNAMES.ThisAYoptionavoids configuringthesenamestwice,onceDY#asaBITNETnodeandonceasthelocalnode.*ForCY{example,ifyoursystemisa standalonenodewith(YNJEnameKNOX,thenenter: YY$$Y SKIP_XMAILER&==&"/KNOX/" 'YForallBITNETnodes,set(DO_CRDB Hto 1.*ThisoptionEY0causesyour configurationtouseanindexedfiletoCYstorethelargeamountof configuration information(YrequiredforBITNET.Enter: Yf$fDO_CRDB%==%1  YFor VAXclusters,set^ BITNET_QUEUE :to PMDF_scsnode V,Y>whereU> PMDF_scsnode+1>isthenameofaPMDFbatchDYqueuethatrunsonlyonthe VAXclustermemberwithBYtheexternalBITNETlinks.+ThisoptioncausesallEYHbatchjobsthatsendmailonBITNETtorunontheDYnodewiththeexternallinks,whichavoidstheNJEBYtransferofmailfilesbetween VAXclustermembers.@YRForexample,iftheexternallinktotheDECUSnodeARNOLDwithdomainname Arnold.Com,enter Arnold.Com+cinresponsetothis question.K`_10.Nextyouareaskedforthenameofthemailboxthe/gatewayuses.(Acceptthedefault,MAILERx.ThepurposeofIthemailboxismuchmoreobviousfromthenameifyouAiuseMAILERthanifyouuse SMTPUSER,andMAILERGisthedefaultnameofthesendinguserforoutboundBSMTPmail.O`11.YouareaskedfortheofficiallocalhostnameinPartGFouroftheautoconfiguration dialogue.*IfyoursystemCJisa homogeneous VAXcluster,enterthe domain-styleJnameofthe VAXcluster,notthatoftheclustermember.LThisnamewillbethereturnaddressforallmailexcept/TthatsenttoBITNET destinations.M`12.Youarealsoaskedfortheaccounttowhichmailfor., Postmasteristobesent..EnterO, POSTMASTER@,andtheEofficialhostnameofthis homogeneous VAXclusterorCsystem.)Youcanlaterforward POSTMASTER'smailto+6anotheraccount,if necessary.D`13.In Part Five of the autoconfiguration dialogue,A you are asked to confirmor re-specify the fileDfspecifications ofthe files the procedurewill use.CThedefaultsare recommended,exceptforthefiles-PMDF_ROOT:[TABLE]GATEWAY.RULES and5p PMDF_ROOT:[TABLE]BGATEWAY.RULES.)TaketheLdefaultsforthesefilesifthereareVAXsystemsrunningF!PMDF,thatareonthesameDECnetorTCP/IPnetworkGyandnotonBITNETandnotinthesame VAXclusterasIyours,andthatwillroutemailtoBITNETthroughyour#* system.' Otherwiseenter Y* NL:!* forthesetwofiles.* ?*<%?; DOWhentheautoconfiguration procedure finishes,reviewOChapter5inthe( PMDFSystem Manager'sGuideO.+MuchEO5of thechapterexplains how tomanually setuptheJO configurationyouhavejustcreatedautomatically.*CertainLOmanualstepsarestill required,andare explainedintheO> following sections.>Section6.3.8)>providesmore informationon#Owhichstepsyoushould  not +do.*? |{}f! U<3O6.3.6.2CInstallcompiled configurationJO)IfyouuseacompiledPMDF configuration(asshouldallJOBITNETnodes),youmust recompileand reinstallthePMDFKO configurationeachtimeyouchangethePMDFconfiguration,UO3alias,oroptionsfile.(Sinceyoumustdothisatleastmonthly,>OwhentheDOMAINNAMESandXMAILERNAMESfilesNOareupdated,itspeedsyourworkandreducesthechanceofIO<errorsifyouuseacommand procedureforthesetasks.BOConsiderusingacommand procedurecalledCOMPILE_CO INSTALL.COM,whichcanbe convenientlykeptinthe=O5 directoryPMDF_ROOT:[TABLE].This procedurecanBObeusedwheneverPMDF.CNForALIASES.ischanged.FOFor incorporatingmonthlytableupdatesintothePMDFGO>configuration,callthis procedurefromanothercommand#O procedure, describedinSection7.4.*Z{?=L f"=OCOMPILE_INSTALLcompilesthePMDF configurationMOwiththeCNBUILDutility,setsthecorrectfile protectionsMO5onthecompiled configurationfile(an importantandeasilyNO forgottenstep),installsthecompiled configurationoneveryLOnodeofthe VAXclusterofwhichyoursystemisamember,LO>andpurgesthecompiled configurationfiletooneversion.LO(Ifyoursystemisnotamemberofa VAXclusterandyouJOdon't anticipatethatwillchange,youcaneasilymodifyIOHthe proceduretoworkslightlyfasteronasinglenodeFOby executingINSTALLcommandsdirectlyinsteadofvia,OSYSMAN.)The procedurefollows:O~$&PMDF%CNBUILD3O$&SET%PROTECTION=W:RE%PMDF_CONFIG_DATAO$&SYSMAN"OVSET%ENVIRONMENT/CLUSTER%OSET%PROFILE/PRIVILEGES=ALLJODO%IF%F$FILE_ATTRIBUTES%("PMDF_CONFIG_DATA","KNOWN")&THEN%-Ez.INSTALL%REPLACE%PMDF_CONFIG_DATA&/OPEN&/HEADER%/SHAREDQOvDO%IF%.NOT.%F$FILE_ATTRIBUTES%("PMDF_CONFIG_DATA","KNOWN")&THEN%-DzINSTALL%CREATE&PMDF_CONFIG_DATA%/OPEN%/HEADER%/SHARED%ODO%PMDF&RESTART%BN_SLAVE$OM$&PURGE&PMDF_CONFIG_DATAt~ } 6O6.3.8BPMDF configurationstepstoavoid>O4Manyofthe instructionsinChapter5ofthe4 PMDFSystemO Manager'sGuide6shouldbeskippedbecausethe procedureJOisnot recommendedorbecausethe automatic configurationJO=utilityhasmadetherequiredchangesautomatically.*ThisPOsectionprovidesalistof ``don't''stohelpthenewBITNETOO Postmasterskipoverthese instructions confidently.'AfteryouMOGhaveyourmailer configuredand operating successfully,feelMOfreetoreturntothesesectionsofthePMDF documentationBOtoincreaseyour understandingofhowPMDFworks.  p `mmDon't:maddaBITNETchanneltoyour configuration (( PMDFSystem Manager'sGuide%x,Section5.3and5.4).@Theautoconfigurationprocessdoesthisforyou. `Don't<setupanyoptionfilesforBITNETchannels (( PMDFSystem Manager'sGuide&t,Section5.5).)TaketheHOdefaultstosendclassN PUNCH-typefiles,expandtabsGtospaces,andhandlelonglines.-Thesedefaultswere,designed specificlyforBITNET. `Don't1definesystems accessibletoNJE( PMDFSystem Manager'sGuide3;,Section5.6).,Theautoconfiguration(0processdoesthisforyou. `Don't>setupachannelforall addressesendingin.BITNET (( PMDFSystem Manager'sGuide,Section5.6).DaTheautoconfigurationprocessdefineseach registeredDBITNETnodetoPMDF individually,andso eliminates0theneedforsuchachannel.1The PMDFSystemj Manager'sGuide7Tjliststhe disadvantagesof configuringa2channelforall addressesendingin.BITNET(a ``catch-all'' channel). `Don't9setupchannelsforeachBITNETnodeandgateway((5 PMDFSystem Manager'sGuide,Section5.7).@LTheautoconfigurationprocessdoesthisforyou. `Don't7defineJAN_BN_MASTER_FLAGSas1forJnet'$ V3.5andlaterversions((=$ PMDFSystem Manager'sGuide $ ,-| Section5.7).'Youalreadyhave:; $&DEFINE/EXEC/SYSTEM%JAN_DEFAULT_IMAGE_FLAGS%1 V  3in!JAN_COMMON:[SYS]JANSITECOMMON.COMif,you configuredaJnetcluster. `[[Don't7[writedirectlytoHenry Nussbacherabout# registeringadomain(( PMDFSystem Manager'sGuide ~,D Section5.8)..Thecorrectaddressand procedurefor1esettingupadomainiscoveredineSection6.6"eofthisbook. `Don't7editBITNET_DOMAINS.COM.Youmayneedto;=edittheversionofBITNET_DOMAINS_DRIVER.COM?createdby CONFIGUREtodefineadditionsymbols4fromthelistinSection5.8of the PMDFSystemG Manager'sGuide3XGtogettheoptimal configurationforDyoursystem./YoucanalsosetthesesymbolsbeforeBrunning CONFIGUREandtheywillbepassedthrough$PtoBITNET_DOMAINS_DRIVER. `Don't4runBITNET_DOMAINS.COM directly.*Always9(runitfromPMDF_ROOT:[EXE]CONFIGURE.COMor8BITNET_DOMAINS_DRIVER.COMtosetupsymbol4 definitionsthatcontrolcustomization. `XXDon't=Xfollowthe procedureinSection5.8.1oftheX PMDF" System Manager'sGuide*xtoregisteryourmailer.*The :MAILERC tag mentionedinthatsectionis obsolete.(Instead'bfollowthe instructionsinobSection6.6 btooperateasatrustedmailer. `: : Don't#: usetheBSMTPcommands: VERB n: and: TICK : (: PMDF" System Manager'sGuide-Z ,Section5.8.2).(MostgatewaysI return undeliverablemailwithan explanationofwhyitMD couldnotbe delivered,sothemessages resultingfromthe useof VERB l and  TICK are superfluous. `  Don't6 attempttousethe MULTIGATEkeyword( PMDF"t System Manager'sGuide*_t ,Section5.8.3)..Leavethis; complex configurationtasktoBITNET_DOMAINS,@% whichsetsupyourmailertableswith MULTIGATE~ automatically. `  Don't> simulatemaildeliverybyNJEtosystemsthat$V havenoNJEsoftware(()V PMDFSystem Manager'sGuide V ,C Section5.10).,Instead, establish domain-stylenamesEforthenon-NJEsystemsinthesamedomainasyour@_BITNETnode,and configurePMDFtoforwardmailHtothenodeoveranon-NJEnetworklink(forexample,<MAIL-11andDECnetorSMTPandTCP/IP).SeeiAppendixB$iforfurther information. `Don't,setupyourmailermanually( PMDFSystemA Manager'sGuide.:A,Section5.11.2).*BITNET_DOMAINS) automaticallyputsthelines+!&Rewrite%for&BITNET%gateways f!BITNET-GATEWAY$U@BITNET-GATEWAY*(|?*o%?*,Oh and%!&BITNET%gateway&channel P!, bit_gateway% nox_env_to&period%4BITNET-GATEWAY !b2inyourPMDF.CNFfileandthelinemailer:mailer@bitnet-gatewayM##inyourALIASES.file.g~ ! ):O6.4BStartupPMDFonall VAXclusternodesKOUAfterPMDFis installedand configured,startitrunning.KOFirststartall networking software,thenrunthecommand O procedureslistedinSection6.2.5+inthecorrectorder.)IfyouEO^are configuringa VAXclustersystem,run PMDF_STARTUPBOandPMDF_START_QUEUESoneachnodeofthecluster(OthatislicensedforPMDF.*? WJOWhenPMDFisstarted,testyour configurationbysendingQOmailtoeachofthenamesofthelocalsystemor VAXcluster,IO5andthrougheachtypeofchanneltoremotesystems.-IfJOyoufindany problems,reviewyour configurationandtheQOdocumentation.'Ifyourequirehelp,callInnosoftorsendmail5O>tothe INFO-PMDFmailinglist(Section%>6.7).*|? J Z 0+O6.5BUpdateBITNET registrationIOUWhenPMDFisfully operational,registeryourmailerby;OsendinganUPDATEjobtoBITNET.Includea :SERVERS1$Otag(whichreplacedthe:MAILER!taginBITEARNNODES8O^in1991)toregisteryourmailerandan^ :INTERNETr^tagtoGOinformLISTSERVofthe domain-stylehostnameofyourGOnode., (LISTSERVusesthis informationto determinetheGOhNJEaddressforusers accessingLISTSERVbymail.,SeeOSection6.6.1<for additional information.)'ThefileNEWTAGSODESCRIPT  3- , availablefromLISTSERV@BITNIC F 2i, describes(Orthesetagsinmoredetail.*O?*"/A*F"/>WNOAsampleupdatejobsteptoupdatetheentryforastand-/OaloneVAX/VMSsystemisshowninExample6-5. TheEO5UPDATEjobstepstoupdatenodeentriesforatwo-HOnode VAXclusterwithaJnetclusternameareshowninOExample6-6.@cFeaturesofthejobstepsare explainedintheO> followinglist.*O*OO!   t1 tThezt :SERVERS18ttagdefinesthenetworkservicesprovided)byserverssuchasmailers. L20LSpecifythe recommendedusername:BLMAILER"L.ThisistheI``nameofthemailboxtheBITNETgatewayuses''intheC terminologyofthePMDFautoconfiguration procedure.IVUseofothernamesisoutsidethescopeofthisbook. 3OSpecifytheNJEnameoftheJnetcluster,orifthemailerP.doesnotrunonacluster,thenodeitself.(SpecifytheNJENnameofanothernodeifthatnodeisthemailhandlerforLthisnode.+IncludethenodenameevenifitisthenodeL7definedbythisentry.'Codenospacesafterthe nodename. 4MAILM specifiesthatthisisamailserver,ormailer.'AtpressHtime,mailersaretheonly recognizedtypeofservers. 5MThereisnoneedtospecifythe argumentsomittedinthis;example.'Thedefaultsforthese arguments(PUNCHforthe@outputfileformat, ~@M'@fortheoutputclass,andA@BSMTP @forKthemessagetransfer protocol)arethecorrectvaluesfor5VAX/VMSsystemsrunningJnetandPMDF. p6LpSpecifythenameofthepeopletagofthe Postmaster.*If0youfollowedtherecommendationinSection5.7.3,specifyI!thepeopletagyouaddedtoyourmemberentryforthez postmasteruser,8z P_POSTMAST z. 7JSpecifytheTCP/IPhostnameofthenodeor VAXcluster.RR IfthisentryisforamemberofaJnetcluster,specifytheJ TCP/IPhostnameofthe VAXclusterhostalias,thenthe  individualmember.*?oTA! )6O6.6BRegisterdomaingatewaywithBITNICCOUToinformother networkedsystemsthatyourdomainGO (includinga domain-stylenamefora BITNET-onlynode)NOexistsandhowtoreachit,youmustregisteryourdomain.PO^InternethostsfindouthowtoreachyourdomainthroughtheOdomainnamesystem ( DNS)). ProvidingDNS information8Otootherhostsonthenetworkiscallednameservice .r! aH@OBITNETnodesfind outhow to reach your domainDOthrough entries!in local mailer tables.3These table>O5entriesare generatedfromDOMAINNAMES,whichEOis centrally maintainedbyBITNICand availablefrom@OLISTSERV@BITNIC.TheentriesinDOMAINNAMESareNO>madeupoftagsthathavethesamesyntaxasthetagsinBOBITEARNNODES.Thesetagsare describedinDOMAIN8OGUIDE,withupdatesandclarificationsinHSection6.6.1ofthisOHbook.*H?Z00OTherearetwopossible situations:m! CU`m1.:Ifyoursystemisorwillsoonbe connectedtothe Internet,Dyouhavealready registeredadomainnamewiththe@DDNNICandarrangedfornameserviceforyour$wdomain,as describedin&wSection3.4.5.$wSitesinthis situationDarrangefornameservice themselvesaspartoftheF(processof connectingtothe Internet,andneedonlyC establishanentryinDOMAINNAMES.AsamplemailLfiletoregisteradomainforasiteonbothBITNETand*2theInternetis describedin2Section6.6.2.R`2.:Ifyouhaveno immediateplanstoconnecttothe Internet,B CRENwillregisteryourdomainnamewiththeDDNGbNICforyouatthesametimeitisaddedtoDOMAIN=NAMES,andarrangeforHarvard UniversityandEthe UniversityofCalifornia-BerkeleytoprovidenameGlserviceforyourdomain.-Sitesinthis situationmustFprovide additional informationsothattheBITNICcanGregisteryourdomainnamewiththeDDNNIC.AsampleLvmailfiletoregisteradomainfora BITNET-onlysiteis describedinSection6.6.3.*&:?*?*? NKOIfyouhavenotreceivedacopyofDOMAINGUIDEintheIOTECHREPpacketoroverthenetwork,obtainacopyfromO5LISTSERVE@BITNIC.}SFOThe procedures describedinDOMAINGUIDEmaybeused Oby:y O `m.mMembersand affiliatesofBITNET `DMembersof CooperatingNetworksthatusetheBITNETAENetwork InformationCenter(BITNIC)astheBITNET! registration authority `BCountry coordinatorsofother Cooperating Networks,vsuchasEARNZ0JO Participantsin CooperatingNetworksthatdonotusetheLOservicesoftheBITNICshouldregisterwiththeirnationalKO5 registration authorityusingthe procedures establishedforOOtheircountry,whichareoutsideofthescopeofthisbook.@OToregisteradomainnamewith BITNET, and op-DO tionally,"with the DDN NIC, a file must be mailedBO5fromtheTECHREPaddressforyour organizationto?ODOMAINS@BITNIC.Onlysites registeredinBITEARN@ONODEShaveaTECHREP,soyour organizationmustAO>alreadyhaveamemberentryinBITEARNNODEStoLOusethis procedure.( Acceptingdomain registrationsfromtheGOTECHREPonlyprovidesan additionalcheckthatonlyaMOHsingledomainnameisever registeredforany organization.,OFor additional information,seeSection3.4.4.*c?NFOThissectionprovides supplementary informationtotheIO procedureinPart2ofDOMAINGUIDE(theversiondated7O5April1992)andtwo additional examples. wand directionsfor subscribingare discussedin>Section6.7.2.*?F tFOMostLISTSERVlistsandmanyInternet discussionsareKO gatewayedtonetworknews.(Newsusesaflooding algorithmRO5tosendallarticlestomostnewsservers,andismostusefulFOwhenmany differentusersononenode participateinGOa discussion./Newshasaseparateuser interfacefromLO> electronicmail,an advantageforusersthatwanttokeepKOurgentorpersonalmailseparatefromnetwork discussions.JO Investigate installingANU (AustralianNational University)HOHNewsand obtaininganewsfeedifyoufindthatmanyKO individualusersare participatinginLISTSERVorInternetIO discussionsthatarealso availableasnews..NewsfeedsGORcancomeoverBITNET,the Internet,andothernetworkIO transports.)Further informationonANUNewsis availablePOfromtheDECUSlibrary,andisoutsideofthescopeofthisO[book.J$  5O 7.2On-going! Management"of!BITNET!NodesEOCongratulations!)Youhave implementedBITNETforyourEO organization,completewithafully-functional,BSMTP-LOB compliantmailer,asrequiredbyCRENforallmembersandO affiliates.?% JOTokeepyoursoftwarerunning smoothly,providethebestLOBITNETservicesforyourusers,andremainagoodnetworkDO5citizen, certain maintenancetasksmustbe performedHOonaregularbasisorwhen circumstancesrequire.-ThisKOchapter summarizesthesetasks,andis organizedbytheirJO>required frequency:* initiallyandwhenyouaddnewusersO(Section7.1),4 constantly(Section7.2),dailyonweekdaysO(Section7.3),1monthly(Section7.4), YwhenchangingsystemOHclock(SectionRH7.5),6Hand irregularly,inresponsetocertainOchanges(Section7.6).*%jZ?&*%Z?-*%j}?3*%}?=*%; ?A*%c{?DC&! 7O7.1B InitiallyandwhenaddingnewusersBOUWhenyoufirstbringupaBITNET connection, andLOwheneveryouadduserstoyoursysteminthefuture,youKOhavetwo managementresponsibilities:(toassignusernamesO^(Section}^7.1.1)DV^andtotrainororientthenewusersintheuser$Oofthenetwork(Section7.1.2).*&j!?'*&z?(3 O7.3BWeekdaysOOUThetasksinthissectionshouldbedoneeachbusinessday:+OreviewJANTIDYoutput(Section7.3.1),&disposeoffilessenttoO POSTMASTER(Section7.3.2),$readmailto POSTMASTERO^(Section^7.3.3),0k^checkPMDFchannelqueues(Section^7.3.4),.OcheckPMDFbatchqueues(Sectionc7.3.5),Nandreadrelevant(Onetwork discussions(Sectiond7.3.6).`Consider automatingLOhasmanyofthesetasksaspossibleandmergingtheminto:OJANTIDYoranotherdailycommand procedure.*3p?4*3?5*3j!?6*3!?9*3Nz?;*3M?<I= O7.4BMonthlyROUThetasksinthissectionshouldbedonemonthly:'installJnet#Oroutingtables(Section7.4.1)*`andbuildmailertablesfromODOMAINNAMES  1'6andXMAILERNAMES(Section7.4.2).*=mp?>*=/1*=?@3qDGBO7.6B Management activitieswithnoregularscheduleJOUThetasksinthissectionmustbedonewhenevercircum-DOstanceswarrant:-updateJnetandPMDFconfigurationsO(Section7.6.1),7jmodifysoftware dependentontheSCSNODE@O^andDECnetnodenameswhentheychange(Section^7.6.2),HOadjustqueueconfigurationswhenfirst upgradingtoVMSOV5.5(Section87.6.3),/%andrespondtomailfromNETSERVOhservers(Sectionh7.6.4).*Dj?E*D!?F*D!?G*D+?JUh 4+/O B.! Operating!BITNET!Mail"Gateways _UNote _CThisappendixisadraft,andserves primarilytoJnprovideanoutlineformaterialforafutureeditionofCthisbook.*Your experiencesandother contributionsC arewelcome.+TosubmitmaterialorideasforthisBx appendix,followthe instructionsonthe copyright*pagefor submitting comments. 1OThePMDF configuration describedinChapter6FprovidesaHO ``gateway''betweenBITNETmailandthedomainnameofKOjyourownsystem.'Thisappendixis concernedwithgatewaysCOonyoursystemthatroutemailbetweenBITNETand otherOsystems.*h|mOXi .COThisappendix doesnot attempt toprovide completeLO instructionsfor operatingmailgatewaysforthirdparties.HO5Itattemptstoprovide frequentlyneeded informationonFO providingsuchgatewaysforanorganization'sownuseKOratherthanfortheglobal networking communityatlarge.NO>IfyouintendtoprovidesuchaservicebetweenBITNETand%Otheentire Internet,seeSectionB.3*:inafutureeditionofthisO appendix.*iZ?t ihB&Pj@0X34 Ld fc ;9[:8<0 l, rA sB~zcF(GUrt-F\6*0>1r [ (\ rx"| lXWfAY ^G N (Mx 40&V(jM+,X-|a@ fN;Ln' siv|}zTzK_Cd -{(<~| \>+lh  $ /R1&  t:,T* 4[? ?   ~  j!*=##&, :))' + t-jg/J/0|7 T3,AQ 2F<"p @vKpT"GJ6C[q\` ajm K|ef^h(lbnloMvpVrs 9NZ3vHwx{X f\:{XpF<0.`V$ nZOP<(kr(