____________________________________________________ DSNlink for OpenVMS Installation Guide Order Number: AA-PJMNB-TE This document describes how to install DSNlink for OpenVMS. Revision/Update Information: This document supersedes all previous versions. Operating System and Version: VMS Version 5.2 or higher OpenVMS AXP Version 1.0 or greater Software Version: DSNlink V1.2 for OpenVMS. ________________________________________________________________ December 21, 1992 The information in this document is subject to change without notice and should not be construed as a commitment by Digital Equipment Corporation. Digital Equipment Corporation assumes no responsibility for any errors that may appear in this document. The software described in this document is furnished under a license and may be used or copied only in accordance with the terms of such license. No responsibility is assumed for the use or reliability of software on equipment that is not supplied by Digital Equipment Corporation or its affiliated companies. Restricted Rights: Use, duplication, or disclosure by the U.S. Government is subject to restrictions as set forth in subparagraph (c) (1) (ii) of the Rights in Technical Data and Computer Software clause at DFARS 252.227-7013. Copyright © Digital Equipment Corporation 1992 Printed in U.S.A. All Rights Reserved. The following are trademarks of Digital Equipment Corporation: AXP, DEC, DECnet, DECserver, DECsystem, DECUS, DECwriter, DIBOL, Digital, IAS, MASSBUS, Packetnet, PDP, PDT, RSTS, RSX, UNIBUS, VAX, VAX BASIC, VAX DATATRIEVE, VAX DOCUMENT, VMScluster, VAXstation, VMS, VT, VT100, VT200, VTX, and the DIGITAL logo. Third Party Trademarks: Hayes Smartmodem 2400 is a trademark of Hayes Microcomputer Products, Inc. This document was prepared using VAX DOCUMENT, Version 2.0. _________________________________________________________________ Contents Preface................................................... vii 1 Preparing to Install DSNlink for OpenVMS 1.1 Authorization Letter ............................ 1-1 1.1.1 Product Authorization Key (PAK) Not Required .. 1-1 1.2 Electronic Kit Distribution ..................... 1-1 1.3 Is DECnet Needed?................................ 1-2 1.4 Order of Installation............................ 1-2 1.5 DSNlink Customization for Your System............ 1-2 1.5.1 Modem Transport Overview ...................... 1-3 1.5.2 X.25 Transport Overview ....................... 1-4 1.5.3 DECnet Transport Overview ..................... 1-6 1.6 Installation May Add Disk Quota Entry............ 1-6 1.7 Disk Space Requirements ......................... 1-7 1.8 System Parameters................................ 1-7 1.8.1 Setting SCSNODE ............................... 1-8 1.8.2 Setting the SCSSYSTEMID Parameter ............. 1-9 1.8.3 Other System Parameters ....................... 1-10 1.9 User Account Parameters.......................... 1-11 1.10 DSN$SERVER Default UIC........................... 1-13 1.11 Preinstallation Information for Modem Transport.. 1-13 1.11.1 Parameters on DECservers ...................... 1-13 1.11.2 Telephone Line and Modem Setup ................ 1-16 1.11.3 Telephone Line Verification ................... 1-16 1.11.4 Modem Verification ........................... 1-17 1.11.5 Setting the Serial Port Interface Speed ...... 1-19 1.12 VMScluster Installation Requirements............. 1-19 1.13 Read the Release Notes........................... 1-20 1.14 Preinstallation Checklist........................ 1-21 1.15 Choose An Installation Example................... 1-22 iii 2 Modem Transport Installation 2.1 Installation Overview............................ 2-1 2.2 How to Abort an Installation..................... 2-1 2.3 Installing DSNlink on a DCN Using the Modem Transport........................................ 2-2 2.4 Installing DSNlink on a DAN...................... 2-12 3 X.25 and DECnet Transport Installation 3.1 Installation Overview............................ 3-1 3.2 How to Abort an Installation..................... 3-2 3.3 Installing DSNlink Using the X.25 or DECnet Transport........................................ 3-2 4 After Installing DSNlink 4.1 Changing the DSNlink Transport................... 4-1 4.2 VMScluster Installation.......................... 4-1 4.2.1 Start up DSNlink on DANs in the VMScluster .... 4-1 4.2.2 Replace DCLTABLES.EXE ......................... 4-1 4.3 The Site-Specific Startup File................... 4-2 4.4 Special Mail Logical Names....................... 4-3 A Modem Troubleshooting A.1 List of Modems................................... A-1 A.2 Modem Prefix String.............................. A-2 A.3 Echo and Dial Modem Commands..................... A-3 A.4 Conditions for Using a Hayes Compatible Modem.... A-4 A.4.1 How to Get DSNlink Working with a Hayes Compatible Modem............................... A-5 A.5 Types of Possible DSNlink Modem Problems......... A-8 A.5.1 No Dial Tone Error on Modem ................... A-8 A.5.2 SYSTEM-F-HANGUP ............................... A-8 A.5.3 DSN-E-MODEM_ERR ............................... A-9 A.5.4 Modem Does Not Respond ........................ A-10 iv B Modem Scripts B.1 Overview......................................... B-1 B.2 Default Modem Scripts............................ B-2 B.2.1 Scripts for Digital Modems .................... B-2 B.2.2 Scripts for Hayes Modems ...................... B-4 B.3 Alternate Modem Scripts.......................... B-6 B.3.1 How to Use the Alternate Hayes Compatible Modem Setup Scripts.................................. B-6 B.3.2 Hayes Alternate Modem Setup Script C .......... B-8 B.3.3 Hayes Alternate Modem Setup Script D .......... B-9 B.3.4 Hayes Alternate Modem Setup Script E .......... B-10 B.3.5 How to Set Up DF196 or DF296 Modems at Lower Baud Rates..................................... B-11 Index Examples B-1 DF242 Modem Setup Script Example .............. B-2 B-2 DF196 and DF296 Modem Setup Script Example .... B-3 B-3 Modem Dialer Script Example for the DF124+, DF242, DF196, and DF296 Modems................. B-3 B-4 Hayes Modem Setup Script Example .............. B-4 B-5 Hayes Modem Dialer Script Example ............. B-6 B-6 Alternate Hayes File-DSN$HAYES_SETUP_C.DIALER.................. B-8 B-7 Alternate Hayes File-DSN$HAYES_SETUP_D.DIALER.................. B-10 B-8 Alternate Hayes File-DSN$HAYES_SETUP_E.DIALER.................. B-10 Tables 1 Manual Conventions ............................ vii 1-1 Disk Space Requirements ....................... 1-7 1-2 System Parameters Required .................... 1-10 1-3 User Account Settings ......................... 1-11 1-4 DECserver Parameters .......................... 1-14 1-5 Modem Wakeup Sequences and Responses .......... 1-18 v A-1 Modem Enable Echo Sequences and Responses ..... A-3 A-2 Modem Dialing Sequences and Responses ......... A-4 vi _________________________________________________________________ Preface This document describes how to install the DSNlink for OpenVMS software. It assumes general familiarity with system management tasks performed on VMS systems. Conventions Used in This Document This document uses the conventions listed in Table 1. Table_1_Manual_Conventions_________________________________ Convention__Description____________________________________ DSN Uppercase words and letters used in examples indicate that you type the word or letter exactly as shown. DSNlink Abbreviated product name used for convenience to refer to DSNlink for OpenVMS. filename Lowercase words or letters set in italics indicate that you substitute a word or value of your choice. bold Indicates user input. [ ] Brackets indicate that the enclosed item is optional. . . . A horizontal ellipsis indicates that you can repeat the preceding items one or more times. (continued on next page) vii Table_1_(Cont.)_Manual_Conventions_________________________ Convention__Description____________________________________ $ DSN ITS A vertical ellipsis in an example indicates . that not all lines are shown. . . The symbol indicates that you should press the Return key. The symbol indicates that you should hold down the key labeled Ctrl and then press ____________another_key_indicated_by_x.____________________ viii 1 _________________________________________________________________ Preparing to Install DSNlink for OpenVMS Complete the following steps before you install DSNlink on your computer system. 1. Read this chapter. 2. Make sure your system meets the criteria described in the Preinstallation Checklist in Section 1.14. 3. Choose an installation script example in Section 1.15. 1.1 Authorization Letter All DSNlink sites must have an authorization letter from Digital. This letter contains information that is required during DSNlink installation. If you are using a previous version of DSNlink, your original authorization letter is also valid for this release, DSNlink V1.2 for OpenVMS. If this is the first installation of DSNlink at your site, your authorization letter will be sent separately. 1.1.1 Product Authorization Key (PAK) Not Required You do not need to have a Product Authorization Key (PAK) to install DSNlink. 1.2 Electronic Kit Distribution If you are already using DSNlink you can obtain any new DSNlink installation kit via your existing DSNlink system. This is known as electronic kit distribution (EKD) and is described in DSNlink for OpenVMS User's Guide. Preparing to Install DSNlink for OpenVMS 1-1 Preparing to Install DSNlink for OpenVMS 1.3 Is DECnet Needed? 1.3 Is DECnet Needed? Prior to installing DSNlink, you may need to have DECnet running on your systems. If any of the following conditions are true, you will need DECnet: o You plan to have any DANs. o You wish to use DSN VTX. o You wish to allow Digital support specialists to remotely log into your system when you authorize it. o You are an internal Digital Customer and wish to use the DECnet transport. 1.4 Order of Installation If you are planning to install DSNlink on more than one node it is important to follow this order of installation: 1. Install DSNlink on your DCN first. 2. Then install DSNlink on your DANs. All DANs must be at the same version level of the DSNlink software as the DCN. If you attempt to use DSNlink from a DAN that is running a different version of DSNlink software, the following message is displayed on the DAN: DSN-F-BADRESP, invalid response from DSNlink control software 1.5 DSNlink Customization for Your System DSNlink can be tailored to your system requirements by assigning your own values to the DSNlink logical names. You accomplish this by creating your own site-specific startup file. Install DSNlink before creating your site- specific startup file. Instructions for creating this file are provided in Section 4.3. If you are upgrading from an earlier version of DSNlink you have an existing startup file named DSN$STARTUP.COM (in either SYS$STARTUP or SYS$MANAGER directories). This existing file may contain customizations for your system. Digital recommends that you proceed with this installation. Your old startup file will be preserved and renamed to SYS$STARTUP:DSN$STARTUP.OLD. 1-2 Preparing to Install DSNlink for OpenVMS Preparing to Install DSNlink for OpenVMS 1.5 DSNlink Customization for Your System The logical names that were defined in your old startup file are automatically used to create your new startup file during installation. 1.5.1 Modem Transport Overview If you are not using the Modem transport you do not need to read this section. DCN Description One OpenVMS system in the network must be designated as the DCN. The DCN is the node to which the DSNlink modem is connected, either directly or using a terminal server. The DSN$NETWORK process executes on the DCN. To determine which system will be the DCN, you should first decide which system is to be connected to the DSNlink Communications Device. The DSNlink Communications Device is the asynchronous terminal port or terminal server port that will be connected to the DSNlink modem. If the DSNlink Communications Device is connected to an asynchronous device other than a terminal server, the DCN is the system to which that device is attached. If the DSNlink Communications Device is on a terminal server, any OpenVMS system in the Local Area Network (LAN) that has access to the terminal server can be the DCN. DAN Description You can install DSNlink on any other OpenVMS systems in the VMScluster or DECnet network. These systems can communicate with the DSNlink Host system using a single DCN. These other systems are called DANs. Electronic Address Your DSNlink electronic address is the telephone number, including the area code, of the phone line connected to the DSNlink modem. The DSNlink Host system uses this electronic address to connect to your system. More detail on the Modem transport and a sample installation are provided in Chapter 2. Preparing to Install DSNlink for OpenVMS 1-3 Preparing to Install DSNlink for OpenVMS 1.5 DSNlink Customization for Your System 1.5.2 X.25 Transport Overview If you are not using the X.25 transport you do not need to read this section. Your system must satisfy the following conditions to use the X.25 transport with DSNlink: o Either VAX P.S.I. software or the VAX P.S.I. Access software must be installed and running on all nodes that will use DSNlink. This must be done prior to installing DSNlink. o X.25 connections must be functional from all nodes that will use DSNlink, and these connections must use one of the public X.25 PSDNs. o One node must be designated as the DCN. VAX P.S.I. and VAX P.S.I. Access Software Either the VAX P.S.I. software or the VAX P.S.I. Access software must be installed and running on your system prior to installing DSNlink. DSNlink requires that the software be at the following version levels: o VAX P.S.I.-Version 4.2 or higher o VAX P.S.I. Access-Version 4.2 or higher Either a VAX P.S.I. Multihost node or a VAX P.S.I. Access node may be used, as long as X.25 data can go to and from your DSNlink node and the DSNlink Host system. Public X.25 PSDNs Prior to installing DSNlink, you must be connected to one of the public X.25 PSDNs. You should know the Data Terminal Emulator (DTE) number of your system, including the subaddress, if any. Each use of a DSNlink application, whether incoming or outgoing, uses one X.25 channel. Make sure that you have obtained a sufficient channel range from your X.25 service provider to meet your anticipated concurrent usage needs. Digital recommends that you have at least four channels. This would support two users simultaneously working with incoming applications as well as two users working with outgoing applications. 1-4 Preparing to Install DSNlink for OpenVMS Preparing to Install DSNlink for OpenVMS 1.5 DSNlink Customization for Your System DSNlink application clients select their appropriate application server with the use of X.25 user data. Because of this, you may notice several new DECnet objects and X.25-SERVER destinations on your system. These objects specify the DSN$SERVER account for their process creations. The DSNlink startup procedure will automatically create and maintain these objects and destinations for you. If you ever suspect that any of these objects or destinations are invalid, simply purge any of them from the permanent database and restart DSNlink. The startup procedure will reset the DSN$SERVER password to match and recreate the appropriate objects and destinations. For more information on the DECnet objects created during DSNlink installation, see the appendices at the end of the DSNlink for OpenVMS Manager's Guide. DCN Description The DCN is the node designated as the contact for all incoming connections from Digital. This node also distributes any information destined for the DANs. DAN Description The DAN is any node that is running DSNlink software and is not a DCN. Electronic Address Your electronic address is used by the DSNlink Host system to connect to your DSNlink system. This electronic address is based on your DTE number and may contain up to four character fields, depending on your system. These character fields are: o The "X" character to mark the X.25 electronic address. This is required. o The network name plus the percent "%" character. This is optional. o Your DTE number. This is required. o The period "." character plus your subaddress. This is optional. These character fields are concatenated to form your electronic address as follows: X[network_name%]dte_number[.subaddress] Preparing to Install DSNlink for OpenVMS 1-5 Preparing to Install DSNlink for OpenVMS 1.5 DSNlink Customization for Your System Here are some examples of X.25 electronic addresses: o If your DTE address is 100055512123 then your electronic address is X100055512123. o If your DTE address is 21635165, your subaddress is 99, and your network name is TELENET then your electronic address is XTELENET%21635165.99. More detail on the X.25 transport and a sample installation are provided in Chapter 3. 1.5.3 DECnet Transport Overview If you are not using the DECnet transport you do not need to read this section. If you are a Digital internal site and DECnet is to be used as your DSNlink transport, then you must designate one of your nodes as the DCN, meet the criteria described in this chapter, and install DSNlink as described in Section 3.3. If your node resides in a hidden area, it must be on the same extended LAN as the DSNlink Host system node. Electronic Address Your electronic address is used by the DSNlink Host system to connect to your DSNlink system. This electronic address is your node name preceded by the letter D as shown: Dnode_name For example, if your node is KELSON, your electronic address is DKELSON. More detail on the DECnet transport and a sample installation are provided in Chapter 3. 1.6 Installation May Add Disk Quota Entry If any of the DSNlink working directories reside on disks where disk quotas are active, the DSNlink installation adds a disk quota entry for the DSN$SERVER account. The permanent disk quota is 20,000 blocks. The overdraft disk quota is 100 blocks. 1-6 Preparing to Install DSNlink for OpenVMS Preparing to Install DSNlink for OpenVMS 1.7 Disk Space Requirements 1.7 Disk Space Requirements Please consider the following disk space requirements before installing DSNlink. Table_1-1_Disk_Space_Requirements__________________________ ____________VAX___________________AXP______________________ During in- 6,000 blocks (3,072K 18,000 blocks (9,216K stallation bytes) bytes) After in- 2,600 blocks (1,330K 7,800 blocks (3,990K stallation__bytes)________________bytes)___________________ These counts refer to the disk space required on the system disk. The sizes are approximate; actual sizes may vary depending on the system environment, configuration, and software options selected. 1.8 System Parameters Even though DECnet is not required (see Section 1.3), two DECnet-related system parameters, SCSNODE and SCSSYSTEMID, must be set before DSNlink can be installed. Follow the instructions in Sections 1.8.1 and 1.8.2 for setting these parameters. Several system parameters are discussed in the upcoming sections. If any of the these system parameters are changed, you must update SYS$SYSTEM:MODPARAMS.DAT to include these changed values so the modifications do not disappear the next time AUTOGEN is run. Refer to the Guide to Setting Up a OpenVMS System for a discussion of AUTOGEN. All of the system parameters discussed in the upcoming sections are nondynamic, except for MAXBUF. This means the system must be rebooted if the current values of any of these nondynamic parameters are modified. However, it is permissible to make all changes required at one time so you only have to reboot the system once. Preparing to Install DSNlink for OpenVMS 1-7 Preparing to Install DSNlink for OpenVMS 1.8 System Parameters 1.8.1 Setting SCSNODE Please consider the following pointers when setting the SCSNODE system parameter: o If DECnet is running, the SCSNODE parameter must be set to the same value as the DECnet node name. You can determine the value of the DECnet node name using the commands in following example. $ RUN SYS$SYSTEM:NCP NCP>SHOW EXECUTOR Node Volatile Summary as of 13-NOV-1992 14:19:47 Executor node = 2.117 (MYNODE) State = on Identification = DECnet-VAX Vn.n-n, VMS Vn.n-n Active links = 2 o If DECnet is not running, SCSNODE must still be set, but it can be any value. While SCSNODE will already be set on systems in a VMScluster, it is likely that it will not be set on a standalone OpenVMS system. For DSNlink to function, even on a standalone OpenVMS system, this parameter must be set to the DECnet node name of that system. o Enter the following SYSGEN utility commands to change the value of SCSNODE: $ RUN SYS$SYSTEM:SYSGEN SYSGEN> USE CURRENT SYSGEN> SHOW SCSNODE Parameter Name Current Default Minimum Maximum Unit Dynamic -------------- ------- ------- ------- ------- ---- ------- SCSNODE "JANET " " " " " "ZZZZ" Ascii SYSGEN> SET SCSNODE "MYNODE" SYSGEN> WRITE CURRENT SYSGEN> EXIT o If the system parameter SCSNODE is changed, it is often necessary to create a new system queue file, JBCSYSQUE.DAT. If JBCSYSQUE.DAT is not changed, batch and print queue jobs can fail with "remote node unknown or unreachable" errors. 1-8 Preparing to Install DSNlink for OpenVMS Preparing to Install DSNlink for OpenVMS 1.8 System Parameters To rebuild the queue file, enter the following commands: $ STOP/QUEUE/MANAGER $ START/QUEUE/MANAGER/NEW_VERSION After entering the previous commands, reboot the system. Any jobs that were in queues at the time the START/QUEUE /MANAGER/NEW_VERSION command was entered are deleted and will need to be requeued. o If DECnet is not running at the time of the DSNlink installation, but at a later date you decide to activate DECnet on that system, SCSNODE must be set to the DECnet node name on that system. The system should then be rebooted. 1.8.2 Setting the SCSSYSTEMID Parameter The SCSSYSTEMID parameter specifies the low-order 32 bits of the 48-bit system identification number. Beginning with OpenVMS Version 5.5 software, SCSSYSTEMID must be set to some value regardless of whether or not DECnet is running. The SCSSYSTEMID parameter is the unique identifier of each system and is calculated as follows: (DECnet area number * 1024) + DECnet-VAX node number For example, if the DECnet address is 2.211, then SCSSYSTEMID should be set to (2 * 1024) + 211, which is equal to 2259. SCSSYSTEMID is then be set to this value using the following commands: $ RUN SYS$SYSTEM:SYSGEN SYSGEN> USE CURRENT SYSGEN> SHOW SCSSYSTEMID Parameter Name Current Default Minimum Maximum Unit Dynamic -------------- ------- ------- ------- ------- ---- ------- SCSSYSTEMID 0 0 -1 -1 Pure-number SYSGEN> SET SCSSYSTEMID 2259 SYSGEN> WRITE CURRENT SYSGEN> EXIT Preparing to Install DSNlink for OpenVMS 1-9 Preparing to Install DSNlink for OpenVMS 1.8 System Parameters 1.8.3 Other System Parameters Before installing DSNlink, you must be sure that certain system parameters are set correctly. Table 1-2 lists the minimum required values for installing and running DSNlink. Table_1-2_System_Parameters_Required_______________________ F$GETSYI SYSGEN_Parameter______Minimum_Value_________Parameter______ GBLPAGES VAX: 1890 free FREE_GBLPAGES AXP: 4900 free GBLSECTIONS VAX: 25 free FREE_GBLSECTS AXP: 25 free MAXBUF 1200 MAXBUF SCSNODE See Section 1.8.1 SCSNODE SCSSYSTEMID___________See_Section_1.8.2_____SCSSYSTEMID____ A command similar to the following may be used to view the current system parameters using the F$GETSYI DCL lexical: $ WRITE SYS$OUTPUT F$GETSYI("parameter") Replace parameter with the parameter name shown in Table 1-2. 1-10 Preparing to Install DSNlink for OpenVMS Preparing to Install DSNlink for OpenVMS 1.8 System Parameters If any changes need to be made to match the parameters listed in Table 1-2, use the SYSGEN utility to make these changes. For example: $ WRITE SYS$OUTPUT F$GETSYI("FREE_GBLPAGES") 134 $ RUN SYS$SYSTEM:SYSGEN SYSGEN> SHOW GBLPAGES Parameter Name Current Default Minimum Maximum Unit Dynamic -------------- ------- ------- ------- ------- ---- ------- GBLPAGES 10000 10000 512 -1 Pages SYSGEN> USE CURRENT SYSGEN> SET GBLPAGES 10066 SYSGEN> WRITE CURRENT SYSGEN> EXIT The previous example shows setting the minimum number of free global pages. 1.9 User Account Parameters Any user account that uses DSNlink applications must have the minimum parameter settings listed in Table 1-3. This includes the MAIL$SERVER account on your DSNlink nodes. Table_1-3_User_Account_Settings____________________________ Minimum Value Parameter_______________________________/Setting___________ DISUSER flag NODISUSER+ DISMAIL flag NODISMAIL+ CAPTIVE flag NOCAPTIVE BYTLM 16000 PGFLQUOTA 10000 BIOLM 15 DIOLM 15 TQELM 10 +Parameter_value_is_required_for_DSNlink_Copy_or_DSNlink___ Mail only. (continued on next page) Preparing to Install DSNlink for OpenVMS 1-11 Preparing to Install DSNlink for OpenVMS 1.9 User Account Parameters Table_1-3_(Cont.)_User_Account_Settings____________________ Minimum Value Parameter_______________________________/Setting___________ ENQLM 30 FILLM 20 CLI DCL+ Authorized Privileges TMPMBX and NETMBX Access Restrictions None for BATCH access+ +Parameter_value_is_required_for_DSNlink_Copy_or_DSNlink___ Mail only. ___________________________________________________________ The user flags and parameters listed in Table 1-3 can be set using the OpenVMS Authorize utility. See the OpenVMS Authorize Utility Manual for more information. 1-12 Preparing to Install DSNlink for OpenVMS Preparing to Install DSNlink for OpenVMS 1.10 DSN$SERVER Default UIC 1.10 DSN$SERVER Default UIC By default, DSNlink uses UIC [376,200] for the exclusive use of the DSNlink network server account DSN$SERVER. You can choose a different UIC during installation-unless the DSN$SERVER account already exists. In this case the UIC is left unchanged and the the following informational message is displayed: %DSNLINK-I-ACCEXISTS, Using existing DSN$SERVER account 1.11 Preinstallation Information for Modem Transport This section contains information that is only applicable if you are using the Modem transport. If you are using the X.25 or DECnet transport, go to Section 1.12. 1.11.1 Parameters on DECservers DSNlink supports terminal server ports as the DSNlink Communications Device. Thus, DSNlink supports the following DECservers: o DECserver 200/MC running Version 3.1 or higher software o DECserver 500 with a CXY08 linecard running Version 2.0 or higher software o DECserver 550 with a CXY08 linecard running Version 2.0 or higher software o DECserver 700/MC running Version 1.0 or higher software To find out what the current settings for the terminal server port are, log into the DECserver, enable privileges, and enter the LIST PORT n command (where n is the terminal server port number where the DSNlink modem is to be attached): Recommended DECserver Parameters Local> LIST PORT n Port n: Character Size: 8 Input Speed: 2400 Flow Control: XON Output Speed: 2400 Parity: None Modem Control: Enabled Preparing to Install DSNlink for OpenVMS 1-13 Preparing to Install DSNlink for OpenVMS 1.11 Preinstallation Information for Modem Transport Access: Remote Local Switch: None Backwards Switch: None Name: DSN$MODEM_PORT Break: Local Session Limit: 1 Forwards Switch: None Type: Soft Preferred Service None Authorized Groups: 0 (Current) Groups: 0 Enabled Characteristics: Dialup, DTRwait, Input Flow Control, Output Flow Control, Remote Modification The suggested settings on the DECserver port are listed in Table 1-4. Table_1-4_DECserver_Parameters_____________________________ Parameter_______________________________Value______________ Access Remote Alternate Speed None Authorized Groups xx + Autobaud Disabled Autoconnect Disabled Autoprompt Disabled Backward Switch None Break Disabled Broadcast Disabled Character Size 8 Dedicated Service None Dialup Enabled +The_group_number_specified_must_be_offered_by_the_DCN.____ See the OpenVMS LAT Control Program (LATCP) Manual for more information on running LATCP. Refer to the appropriate DECserver manuals for more information on groups and authorized groups. (continued on next page) 1-14 Preparing to Install DSNlink for OpenVMS Preparing to Install DSNlink for OpenVMS 1.11 Preinstallation Information for Modem Transport Table_1-4_(Cont.)_DECserver_Parameters_____________________ Parameter_______________________________Value______________ DSRlogout Disabled DTRwait Enabled Flow Control XON Forward Switch None Inactivity Logout Disabled Interrupts Disabled Limited View Disabled Local Switch None Loss Notification Disabled Message Codes Disabled Modem Control Enabled Multisessions Disabled Name DSN$MODEM_PORT[1] On-demand Loading Disabled Parity None Preferred Service None Queuing Disabled Remote Modification Enabled Ring Disabled Security Disabled Session Limit 1 Signal Check Disabled Speed 2400, 4800, Or 9600[2] Type Softcopy Verification Disabled [1]This_is_the_recommended_name,_although_any_port_name_is_ valid. [2]This must match the serial port interface speed of the modem. ___________________________________________________________ Preparing to Install DSNlink for OpenVMS 1-15 Preparing to Install DSNlink for OpenVMS 1.11 Preinstallation Information for Modem Transport To change settings on the DECserver, log into the DECserver and change the incorrect settings with the following commands: Local> SET PRIVILEGE Password> Local> DEFINE PORT n parameter value key Note that the Password> entry is not echoed. After making the necessary changes, log the port out of the DECserver to set the values: Local> LOGOUT PORT n 1.11.2 Telephone Line and Modem Setup When using the modem transport, verify that the DSNlink modem and telephone line are operational before installing DSNlink on the DCN. Refer to the instruction book that comes with the modem for information on connecting the modem. 1.11.3 Telephone Line Verification You need to know the telephone number of the phone line connected to the modem. Make certain that the telephone number is correct by connecting a telephone to the telephone set jack at the rear of the modem and then dialing the telephone number of the modem from another telephone line. If the telephone that is connected to the modem rings, then you have dialed the correct number. Record this number for later use during the installation. In the U.S. the DSNlink software dials a toll-free 800 number to communicate with the DSNlink Host system. At some sites, long distance service is not available to all phone lines. To make sure that the phone line is capable of reaching the 800 service, you should test the line by dialing an 800 number from a telephone attached to the modem line. Note if you have to dial any numbers to access the 800 service. These number(s) are called the modem prefix string and during installation, you will be prompted for this string. 1-16 Preparing to Install DSNlink for OpenVMS Preparing to Install DSNlink for OpenVMS 1.11 Preinstallation Information for Modem Transport 1.11.4 Modem Verification If your modem is not on a terminal server, skip this section. Preparing for Your Modem Test If the DSNlink Communications Device is an LTA device (that is, a terminal server port), you will need to map the LTA device to a server port to perform the following modem test. This is accomplished by entering the following commands: $ RUN SYS$SYSTEM:LATCP LCP> CREATE PORT LTAnnnn: LCP> SET PORT LTAnnnn:/NODE=server_name/PORT=port_name LCP> The value of nnnn must be an unused LAT device number. Server_name is the name of the DECserver and port_name is a port on that DECserver. If the DECserver port is set according to the specifications in Section 1.11.1, port_ name should have a value of DSN$MODEM_PORT. Enter the following command at the DCL prompt to determine which LAT numbers are currently in use on the system: $ SHOW DEVICES LTA Modem Test Procedure After the modem is connected and powered on, verify that your modem and computer can communicate by entering the following commands, where ddcu is the name of your communications device: $ SET TERMINAL/PERMANENT/TYPE_AHEAD/HANGUP/SPEED=2400/MODEM ddcu: 1 $ SET HOST/DTE ddcu: 2 %REM-I-TOEXIT, connection established, type ^\ to exit 3 . . . %REM-S-END, control returned to node _MYNODE:: 1 If the DSNlink Communications Device is an LTA device, the /MODEM qualifier has no effect and can be omitted. Preparing to Install DSNlink for OpenVMS 1-17 Preparing to Install DSNlink for OpenVMS 1.11 Preinstallation Information for Modem Transport 2 Entering a SET HOST/DTE command to a LAT device is not supported by Digital, but should function adequately for this test. 3 Enter a modem wakeup sequence appropriate to the modem being used. See Table 1-5 for a list of DSNlink modems and responses. The modem should respond with the appropriate message from Table 1-5. If it does not, enter the wakeup sequence as shown in Table 1-5 several more times. If the modem still does not respond, recheck all connections and make sure that the modem is powered on. The modem is correctly connected to the system if the modem responds with the appropriate message. Table_1-5_Modem_Wakeup_Sequences_and_Responses_____________ Modem_Type_________________Wakeup_Sequence__Modem_Response_ Digital DF124+ Ready Digital DF196 Ready Digital DF242 Ready Digital DF296 Ready Hayes Smartmodem 2400 AT OK or 0 (Model_231AA)______________________________________________ Refer to the appendixes for detailed information on modem commands, modem scripts, and modem troubleshooting. 1-18 Preparing to Install DSNlink for OpenVMS Preparing to Install DSNlink for OpenVMS 1.11 Preinstallation Information for Modem Transport 1.11.5 Setting the Serial Port Interface Speed If you are using the Modem transport with a Hayes-style modem, during DSNlink installation you are asked for the modem serial interface port speed. This is the speed at which a modem communicates with the local computer system or terminal server. This speed may be at a different baud rate than the modem uses to communicate across the telephone line. Digital recommends setting this speed to the maximum baud rate. 1.12 VMScluster Installation Requirements The following requirements apply to DSNlink installations on VMSclusters: o If your VMScluster contains the DCN you must install DSNlink on that node. o Install DSNlink only once on a VMScluster. o Both the system authorization file and the network object database must either reside on a common VMScluster node or on each individual node. The filenames are: o System authorization file SYS$COMMON:[SYSEXE]SYSUAF.DAT o Network object database SYS$COMMON:[SYSEXE]NETOBJECT.DAT Do not install DSNlink if one of these is in common and the other is in a node-specific area. o All nodes in the VMScluster must share the queue manager file (SYS$COMMON:[SYSEXE]JBCSYSQUE.DAT or SYS$COMMON:[SYSEXE]SYS$QUEUE_MANAGER.QMAN$QUEUES) o All nodes in the VMScluster must share a single system disk. After installing DSNlink on one node of a VMScluster, the DCL tables on other DSNlink nodes in the same VMScluster will need to be updated. Refer to Section 4.2 for instructions on how to do this. Preparing to Install DSNlink for OpenVMS 1-19 Preparing to Install DSNlink for OpenVMS 1.13 Read the Release Notes 1.13 Read the Release Notes You will find it helpful to read the release notes before installing DSNlink. For your convenience, a copy of the release notes is included with the installation software. You can choose to view them from your terminal, send them to a printer, or both. The following example shows how to send the release notes to a printer. $ SET DEFAULT SYS$UPDATE $ @VMSINSTAL DSNLINK012 mtcu: OPTIONS N VAX/VMS Software Product Installation Procedure V5.5-1 . . . %VMSINSTAL-I-RESTORE, Restoring product save set A ... Release notes included with this kit are always copied to SYS$HELP. Additional Release Notes Options: 1. Display release notes 2. Print release notes 3. Both 1 and 2 4. None of the above * Select option [2]: * Queue name [SYS$PRINT]: Job DSNLINK (queue SYS$PRINT, entry 875) started on LPS40$DSNLPS * Do you want to continue the installation [NO]?1 %VMSINSTAL-I-RELMOVED, Product's release notes have been moved to SYS$HELP.2 VMSINSTAL procedure done at 09:59 1 It is recommended that you read the release notes and review the installation examples provided in Chapter 2 before installing DSNlink. 2 The file name is DSNLINK.RELEASE_NOTES. 1-20 Preparing to Install DSNlink for OpenVMS Preparing to Install DSNlink for OpenVMS 1.14 Preinstallation Checklist 1.14 Preinstallation Checklist Please complete this checklist before installing DSNlink. 1. Read Chapter 1. 2. Have the DSNlink authorization letter available during the installation. The information contained in this letter will be required. If you are installing this software on a computer system that is already running DSNlink, your previously assigned authorization code remains valid. 3. The queue manager must be running, or be started with the following command (see the OpenVMS System Management manuals for more information): $ START/QUEUE/MANAGER 4. Decide which of the following transports you plan to use (refer to Section 1.6): o A modem using the telephone system o An X.25 link o DECnet (available to Digital internal sites only) 5. Have a modem and make sure it works (see Section 1.11). 6. If you are using the X.25 transport, then either the VAX P.S.I. software or the VAX P.S.I. Access software must be installed and running on your system prior to installing DSNlink (refer to Section 1.5.2). 7. If you are an internal Digital Customer and are using DECnet as the transport, make sure that the DSNlink Host system node name is known to your DECnet database (refer to Section 1.5.3). 8. Designate which node will be your DCN and which node(s) are to be DANs, and allow sufficient time to install or upgrade DSNlink on all these nodes. 9. Make sure you have enough disk space available (refer to Section 1.7). 10. Set the system parameters (see Section 1.8). Preparing to Install DSNlink for OpenVMS 1-21 Preparing to Install DSNlink for OpenVMS 1.14 Preinstallation Checklist 11. Make sure that the user accounts are properly set up (refer to Section 1.9). 12. Determine if you need DECnet running on your system(s) (refer to Section 1.3). 1.15 Choose An Installation Example Chapter 2 and Chapter 3 contain examples of DSNlink installations. Examine the following list and select the example installation that is best for your situation. o Installing with modem transport on a DCN-Use the example in Section 2.3 o Installing with modem transport on a DAN-Use the example in Section 2.4 o Installing with X.25 transport on a DAN or DCN-Use the example in Section 3.3 o Installing with DECnet transport on a DAN or DCN-Use the example in Section 3.3 1-22 Preparing to Install DSNlink for OpenVMS 2 _________________________________________________________________ Modem Transport Installation Two installation examples are presented in this chapter. They are: o Installing with modem transport on a DCN o Installing with modem transport on a DAN Please make sure you have completed these steps before continuing with this chapter: 1. Read Chapter 1. 2. Verified that your system meets all of the criteria in the Preinstallation checklist (see Section 1.14). 3. Chosen an installation script (see Section 1.15). 2.1 Installation Overview DSNlink is installed using the VMSINSTAL command procedure. The installation example is shown as it is displayed at your terminal. Explanations for the example are provided at the end of each example installation. Default responses appear in square brackets ([]) You may notice slight variations in naming conventions if you are installing on an AXP system. Any variations that affect your response to the installation are noted in the explanatory text. The AXP installation kit name used in Step 2 is DSNLINK_AXP012. 2.2 How to Abort an Installation To abort an installation procedure at any time, enter . The installation procedure deletes all files it has created up to that point and exits. To retry the installation procedure after entering , start over at Step 2 in the installation procedure. Modem Transport Installation 2-1 Modem Transport Installation 2.3 Installing DSNlink on a DCN Using the Modem Transport 2.3 Installing DSNlink on a DCN Using the Modem Transport Use this example if you chose the following installation in Section 1.15: o Installing with modem transport on a DCN Example Installation Username: SYSTEM Password: $ ALLOCATE mtcu: 1 %DCL-I-ALLOC, mtcu: allocated $ SET DEFAULT SYS$UPDATE $ @VMSINSTAL DSNLINK012 mtcu: 2 VAX VMS Software Product Installation Procedure Vn.n It is dd-mmm-yyyy at hh:mm. Enter a question mark (?) at any time for help. * Are you satisfied with the backup of your system disk [YES]? Please mount the first volume of the set on mtcu: *Are you ready? YES The following products will be processed: DSNlink V1.2 Beginning installation of DSNlink V1.2 at hh:mm %VMSINSTAL-I-RESTORE, Restoring product save set A ... %VMSINSTAL-I- RELMOVED, Product's release notes have been moved to SYS$HELP. © Digital Equipment Corporation, 1989, 1992. All Rights Reserved. * Do you want to purge files replaced by this installation [YES]? 3 DSNlink allows you to use an X.25 link, a modem using the telephone system, or DECnet as a transport. Please indicate what transport type you will be using to connect to Digital. Answer Modem, X.25, or DECnet. * Which DSNlink transport will you use to connect to Digital [Modem]: 4 2-2 Modem Transport Installation Modem Transport Installation 2.3 Installing DSNlink on a DCN Using the Modem Transport The answers to the following questions can be found in the authorization letter which you should have received. Please be sure to enter the values correctly. Incorrectly entered values will cause DSNlink to be non-operational. * Enter your Digital Access Number : nnnnnnn 5 * Enter your Access Number Authorization Code : xxxx-xxxx-xxxx-xxxx DSNlink has been designed so that a single asynchronous terminal interface connected to a modem and phone line can serve as the communication path for all DSNlink applications for a single system, a VAXcluster, or DECnet network, when using the MODEM transport. This installation has determined that your connections to Digital are via the MODEM transport. The VMS system which is physically connected to the asynchronous terminal port used by DSNlink is termed the DSNlink Communications Node. Other nodes in a VAXcluster or DECnet network which communicate with Digital through the DSNlink Communications Node are termed DSNlink Applications Nodes. The minimum DSNlink configuration is a single DSNlink Communications Node. You must now indicate whether you are performing this installation on your DSNlink Communications Node, or on one of your DSNlink Applications Nodes. By default, the installation will assume that you are performing this installation on your DSNlink Communications Node. * Is node MYNODE your DSNlink Communications Node [YES]? 6 You have indicated that you are executing this installation procedure on your DSNlink Communications Node. DSNlink requires exclusive access to an asynchronous terminal port connected to a modem. This terminal port is termed the DSNlink Communications Device. You must now enter the full VAX VMS device name, including the colon, for this device. If the modem is connected to a terminal server port, enter the name of a LAT device (such as LTA9500) that you wish to use. The DSNlink startup procedure will create this device if it does not exist. The DSNlink startup procedure will set this line to "No Typeahead" to prevent any dial-in users from logging in on this line. * Enter the device name of the DSNlink Communications Device : LTA9500 7 * Enter the name of the terminal server for LTA9500 : DSRVR1 * Enter the name of the port on DSRVR1 for LTA9500 : DSN$MODEM_PORT Indicate the type of modem to be used on LTA9500: Modem Transport Installation 2-3 Modem Transport Installation 2.3 Installing DSNlink on a DCN Using the Modem Transport 1 Digital DF242 or DF124+ 2 Digital DF196 or DF296 3 Hayes or Hayes Compatible * Enter the number of the modem type [1]: 3 8 Many modems have the ability to communicate with your local computer system or terminal server at a different baud rate than they use to communicate across the telephone line. This is called the serial port interface speed. This speed is often set to the highest baud rate that your modem can use to communicate with a remote modem. Valid speeds are 2400, 4800, or 9600 baud. * What is the serial port interface speed for LTA9500: 2400 9 A site- specific modem prefix string is sent to the modem connected to the DSNlink Communications Device. The first character in this string represents the type of phone service that you use with your modem. Enter the letter T if you have tone dial service or P if you have pulse dial service. The second character in this string usually represents the initial number required by your phone service for outgoing calls. Other prefix string formats are explained in the Installation Guide. EXAMPLE 1: You have a tone dial service and your modem is connected to PBX equipment that requires an 8 precede outgoing calls. You would enter T8. EXAMPLE 2: You are in the U.S. and your modem is connected to a standard business or a residential phone line. The number 1 must precede outgoing long- distance calls, including 800 number calls. In this case enter T1 if you have a tone dial service, or P1 if you have a pulse dial service. Please note that if you are in the U.S. your system dials an 800 number when communicating with Digital. If your access to 800 service is on a different line than your regular long distance service, your modem prefix string will need to reflect this. * Enter the prefix string to be used with the modem [T1]: 10 To ensure that the DSNlink network runs with the proper quotas and privileges, this installation procedure will create an account for the DSNlink network server and network objects. The name of the account is DSN$SERVER. It is set for batch and network access and has TMPMBX and NETMBX privileges. 2-4 Modem Transport Installation Modem Transport Installation 2.3 Installing DSNlink on a DCN Using the Modem Transport A random password will be set on this account when DSNlink starts up. * UIC for the DSN$SERVER account [376,200]: 11 * Enter the device for the DSN$SERVER account [SYS$COMMON:]: 12 Unsolicited informational DSNlink Mail messages may be sent from Digital to your site. These messages fall into several categories, which are each identified by a logical name that you can modify by creating a DSNlink site- specific startup file. This installation procedure will define these logical names as shown below: 13 DSN$MAIL_CC_RECIPIENT = %NONE% DSN$MAIL_FLASH_RECIPIENT = SYSTEM DSN$MAIL_INFORMATION_RECIPIENT = %NONE% DSN$MAIL_MARKETING_RECIPIENT = %NONE% DSN$MAIL_SURVEY_RECIPIENT = %NONE% You may disable receipt of any of these catagories of information by defining the logical equivalence name to be %NONE%. %DSNLINK012-I-MAIL_ LOGICALS, The logicals will be defined in DSN$STARTUP.COM DSNlink Mail and DSNlink File Copy queue jobs for execution in batch. By default, the DSN$STARTUP procedure will create and start a separate batch queue called DSN$BATCH for this purpose. If you wish to execute the DSNlink batch jobs in an already existing batch queue, the system logical name DSN$BATCH will be defined to use this batch queue, rather than create a separate queue. * Enter the name of the DSNlink batch queue [DSN$BATCH]: 14 All installation questions have been answered. The rest of the installation will proceed automatically and may take up to 15 minutes, depending on your system type. %VMSINSTAL-I-SYSDIR, This product creates system disk directory SYS$COMMON:[DSN]. %VMSINSTAL-I-SYSDIR, This product creates system disk directory SYS$COMMON:[DSN.WORK]. %VMSINSTAL-I-SYSDIR, This product creates system disk directory SYS$COMMON:[DSN.LOGS]. %DSNLINK012-I-CREACC, Creating account DSN$SERVER %VMSINSTAL-I- ACCOUNT, This installation creates an ACCOUNT named DSN$SERVER. %UAF-I-ADDMSG, user record successfully added %UAF-I-RDBADDMSGU, identifier DSN$SERVER value: [000376,000200] added to rights data base Modem Transport Installation 2-5 Modem Transport Installation 2.3 Installing DSNlink on a DCN Using the Modem Transport %DSNLINK012-I-MODACC, Modifying account DSN$SERVER 6 times %VMSINSTAL-I- ACCOUNT, This installation updates an ACCOUNT named DSN$SERVER. %UAF-I-MDFYMSG, user record(s) updated %VMSINSTAL-I- ACCOUNT, This installation updates an ACCOUNT named DSN$SERVER. %UAF-I-MDFYMSG, user record(s) updated %VMSINSTAL-I- ACCOUNT, This installation updates an ACCOUNT named DSN$SERVER. %UAF-I-MDFYMSG, user record(s) updated %VMSINSTAL-I- ACCOUNT, This installation updates an ACCOUNT named DSN$SERVER. %UAF-I-MDFYMSG, user record(s) updated %VMSINSTAL-I- ACCOUNT, This installation updates an ACCOUNT named DSN$SERVER. %UAF-I-MDFYMSG, user record(s) updated %VMSINSTAL-I- ACCOUNT, This installation updates an ACCOUNT named DSN$SERVER. %UAF-I-MDFYMSG, user record(s) updated A new DSN$STARTUP.COM command procedure that reflects the parameters you have specified during this installation will now be created in SYS$STARTUP. If you wish to change any of these installation parameters, you can create a DSNlink site- specific startup file. 15 If you wish to have DSNlink started each time your system startup procedure executes, please ensure that your site specific startup file SYS$MANAGER:SYSTARTUP_ V5.COM includes the following line after the queue manager and DECnet (if installed) are started: $ @SYS$STARTUP:DSN$STARTUP.COM Or, you can add an entry to SYSMAN STARTUP to invoke DSNlink. Make sure that you execute SYS$STARTUP:DSN$STARTUP.COM on all other nodes in this VAXcluster once the DSNlink installation completes. %DSNLINK012-I-CRESTRTUP, creating your DSNlink startup file... %DSNLINK012-I-FILEPREP, preparing DSNlink files and images... %DSNLINK012-I- STARTUP, DSN$STARTUP.COM will be executed after files are moved %VMSINSTAL-I- 2-6 Modem Transport Installation Modem Transport Installation 2.3 Installing DSNlink on a DCN Using the Modem Transport MOVEFILES, Files will now be moved to their target directories... Beginning DSNlink startup on node MYNODE %UAF-I-MDFYMSG, user record(s) updated %JBC-I-QUENOTMOD, modifications not made to running queue %RUN-S-PROC_ID, identification of created process is 0000143E Waiting for DSN$NETWORK process to start... Waiting for DSN$NETWORK process to start... DSNlink startup completed on node MYNODE DSNlink Installation Verification Procedure ------------------------------------------- To verify that DSNlink has been successfully installed, and to register you as an DSNlink user with Digital, the DSNlink Registration Application will now be executed. You will be asked for *your* electronic address, which will permit Digital to send information back to your system. The electronic address you use depends upon the transport mechanism you will use to connect with Digital. If the registration process fails due to a modem error or other problem connecting to Digital, it is not necessary to reinstall DSNlink. Remedy the problem and execute the registration application again. Should your electronic address change in the future, you must execute the Registration Application again. See the DSNlink Manager's Guide for information on how this is done. Press RETURN to continue... You are using the Modem Transport. Your electronic address should be your modem's telephone number, including the area or region code. In the USA, use the format (000)000-0000 to enter your modem's number. DSNlink V1.2 for OpenVMS VAX Copyright (c) 1989, 1992 by Digital Equipment Corporation Digital Equipment Corporation Proprietary Service Tool All Rights Reserved DSNlink V1.2 for OpenVMS VAX Registration 16 Establishing connection to DSNlink Host - please wait... Your registered electronic address is currently: Enter your new electronic address or press RETURN: (617)555-3280 17 Your new registered electronic address is: (617)555-3280 Modem Transport Installation 2-7 Modem Transport Installation 2.3 Installing DSNlink on a DCN Using the Modem Transport Installation of DSNLINK012 V1.2 completed at hh:mm VMSINSTAL procedure done at hh:mm 1 Allocate the device that contains the distribution media. You do not need to do this if you are installing DSNlink from disk. 2 Invoke the VMSINSTAL utility. DSNLINK012 is the name of the software product to be installed and mtcu: is the device that was previously allocated. If you are installing on an AXP system the software product name that you enter is DSNLINK_AXP012. 3 Digital recommends that files replaced by this installation be purged. 4 DSNlink allows you to use an X.25 link, a modem using the telephone system, or DECnet as a transport. This installation example presumes modem was specified as the type of transport. If you plan to use either X.25 or DECnet as the transport type, see the installation example in Section 3.3. 5 The Access Number and Authorization Code can be found in the authorization letter that was shipped separately from the DSNlink distribution. If you are installing this software on a computer system that is already running DSNlink, your previously assigned authorization code remains valid. 6 The installation asks you if DSNlink is currently being installed on the DCN. If your response to this question is YES, then proceed to the next step. If your answer is NO, please use the example installation in Section 2.4. 7 After indicating that this installation is being performed on the DCN, you are prompted for the device name of the DSNlink Communications Device. Refer to the Hardware and Software Requirements shipped with the DSNlink distribution for a list of supported devices. 8 Enter the number corresponding to the type of modem you are using. In this case, a Hayes or Hayes compatible modem is specified. Refer to the appendixes for detailed information on the DSNlink modems, including modem commands, modem scripts, and modem troubleshooting. 2-8 Modem Transport Installation Modem Transport Installation 2.3 Installing DSNlink on a DCN Using the Modem Transport 9 If you selected a Hayes-style modem in the previous prompt, you are asked for the modem serial interface port speed. This is the speed at which a modem communicates with the local computer system or terminal server. This speed may be at a different baud rate than the modem uses to communicate across the telephone line. Digital recommends setting this speed to the maximum baud rate. 10 It is important that the prefix string of the modem (if used) matches the characteristics of the phone system. Otherwise, the system cannot establish contact with the DSNlink Host system. See Section A.2. 11 By default, DSNlink uses UIC [376,200] for the exclusive use of the DSNlink network server account DSN$SERVER. You can choose a different UIC during installation- unless the DSN$SERVER account already exists. In this case the UIC is left unchanged and the the following informational message is displayed: %DSNLINK-I-ACCEXISTS, Using existing DSN$SERVER account 12 Although SYS$COMMON is the default location for the DSN$SERVER account, you can choose to locate this account wherever there is sufficient disk space. Note that this prompt is not displayed if the DSN$SERVER account already exists. Instead, the default DSN$SERVER device and directory is used. 13 This is a list of the DSNlink Mail logical names that define where different Digital Communiques are currently to be sent. You can disable receiving a particular category of information by defining the appropriate logical name in SYS$STARTUP:DSN$SYSTARTUP.COM to be %NONE%. The following list describes the type of information that each logical name pertains to: o DSN$MAIL_FLASH_RECIPIENT defines the mail address(es) that receives time critical information sent from the DSNlink Host system. o DSN$MAIL_INFORMATION_RECIPIENT defines the mail address(es) that receives other classes of information that do not directly relate to marketing information or Flash Mail. Modem Transport Installation 2-9 Modem Transport Installation 2.3 Installing DSNlink on a DCN Using the Modem Transport o DSN$MAIL_MARKETING_RECIPIENT defines the mail address(es) that receives messages about new products and services, as well as update information about existing products and services. o DSN$MAIL_SURVEY_RECIPIENT defines the mail address(es) that receives surveys from Digital concerning service and product quality. o DSN$MAIL_CC_RECIPIENT defines the mail address(es) that receives a courtesy copy of any mail sent from the DSNlink Host system to your users. See the DSNlink for OpenVMS Manager's Guide for a description of how the SYSTEM and the DSN$MAIL_DELIVER_ FAILURE_RECIPIENT logical names are used to ensure DSNlink Mail delivery. 14 Digital recommends accepting the default to this prompt. If an existing queue is used for DSN$BATCH, make sure that the batch queue specified executes on the DCN. 15 For more information on creating a DSNlink site-specific startup file, refer to Section 4.3. 16 Invoking the DSNlink Registration application acts as the Installation Verification Procedure (IVP) during the DSNlink installation. Note that the IVP command procedure SYS$TEST:DSN$IVP.COM can also be invoked independently after installation to test the integrity of the DSNlink software. If the DSNlink modem has not been installed, or has been installed incorrectly, the attempted connection to the DSNlink Host system fails. This does not mean that the installation has failed. The DSNlink modem can be installed (see Section 1.11.2) or an improper modem installation can be diagnosed and corrected (see the appendices). After the DSNlink modem has been properly installed, you can manually register the system. To manually register DSNlink, refer to the DSNlink for OpenVMS Manager's Guide. 2-10 Modem Transport Installation Modem Transport Installation 2.3 Installing DSNlink on a DCN Using the Modem Transport 17 This phone number is used by the DSNlink Host system to contact your DCN. ________________________ Note ________________________ When the DSNlink Host system attempts to send any data, it dials the telephone number that you provided. Ensure this telephone number is correct; otherwise, the DSNlink Host system cannot make contact with your system. If you make a mistake in entering this phone number, the DSNlink Registration application must be executed again, as described in the DSNlink for OpenVMS Manager's Guide. ______________________________________________________ Modem Transport Installation 2-11 Modem Transport Installation 2.4 Installing DSNlink on a DAN 2.4 Installing DSNlink on a DAN Use this example if you chose the following installation in Section 1.15: o Installing with modem transport on a DAN The AXP installation kit name used in Step 3 is DSNLINK_ AXP012. Example Installation Username: SYSTEM Password: $ ALLOCATE mtcu: 1 %DCL-I-ALLOC, mtcu: allocated $ SET DEFAULT SYS$UPDATE $ @VMSINSTAL DSNLINK012 mtcu: 2 VAX VMS Software Product Installation Procedure Vn.n It is dd-mmm-yyyy at hh:mm. Enter a question mark (?) at any time for help. * Are you satisfied with the backup of your system disk [YES]? Please mount the first volume of the set on mtcu: *Are you ready? YES The following products will be processed: DSNlink V1.2 Beginning installation of DSNlink V1.2 at hh:mm %VMSINSTAL-I-RESTORE, Restoring product save set A ... %VMSINSTAL-I- RELMOVED, Product's release notes have been moved to SYS$HELP. © Digital Equipment Corporation, 1989, 1992. All Rights Reserved. * Do you want to purge files replaced by this installation [YES]? 3 DSNlink allows you to use an X.25 link, a modem using the telephone system, or DECnet as a transport. Please indicate what transport type you will be using to connect to Digital. Answer Modem, X.25, or DECnet. * Which DSNlink transport will you use to connect to Digital [Modem]: 4 2-12 Modem Transport Installation Modem Transport Installation 2.4 Installing DSNlink on a DAN The answers to the following questions can be found in the authorization letter which you should have received. Please be sure to enter the values correctly. Incorrectly entered values will cause DSNlink to be non-operational. * Enter your Digital Access Number : nnnnnnn 5 * Enter your Access Number Authorization Code : xxxx-xxxx-xxxx-xxxx DSNlink has been designed so that a single asynchronous terminal interface connected to a modem and phone line can serve as the communication path for all DSNlink applications for a single system, a VAXcluster, or DECnet network, when using the MODEM transport. This installation has determined that your connections to Digital are via the MODEM transport. The VAX OpenVMS system which is physically connected to the asynchronous terminal port used by DSNlink is termed the DSNlink Communications Node. Other nodes in a VAXcluster or DECnet network which communicate with Digital through the DSNlink Communications Node are termed DSNlink Applications Nodes. The minimum DSNlink configuration is a single DSNlink Communications Node. You must now indicate whether you are performing this installation on your DSNlink Communications Node, or on one of your DSNlink Applications Nodes. By default, the installation will assume that you are performing this installation on your DSNlink Communications Node. * Is node JANET your DSNlink Communications Node [YES]?NO 6 You have indicated that you are executing this installation procedure on one of your DSNlink Application Nodes. You will now be asked to enter the DECnet node name of the system in your VAXcluster or DECnet network which will be your DSNlink Communications Node. * Enter the nodename of your DSNlink Communications Node: MYNODE 7 To ensure that the DSNlink DECnet application client can run with the proper quotas and privileges, this installation procedure will create an account named DSN$SERVER. It is set for batch and network access and has TMPMBX and NETMBX privileges. A random password will be set on this account when DSNlink starts up. * UIC for the DSN$SERVER account [376,200]: 8 * Enter the device for the DSN$SERVER account [SYS$COMMON:]: 9 Modem Transport Installation 2-13 Modem Transport Installation 2.4 Installing DSNlink on a DAN DSNlink Mail and DSNlink File Copy queue jobs for execution in batch. By default, the DSN$STARTUP procedure will create and start a separate batch queue called DSN$BATCH for this purpose. If you wish to execute the DSNlink batch jobs in an already existing batch queue, the system logical name DSN$BATCH will be defined to use this batch queue, rather than create a separate queue. * Enter the name of the DSNlink batch queue [DSN$BATCH]: 10 All installation questions have been answered. The rest of the installation will proceed automatically and may take up to 15 minutes, depending on your system type. %VMSINSTAL-I-SYSDIR, This product creates system disk directory SYS$COMMON:[DSN]. %VMSINSTAL-I-SYSDIR, This product creates system disk directory SYS$COMMON:[DSN.LOGS]. %DSNLINK012-I-CREACC, Creating account DSN$SERVER %VMSINSTAL-I- ACCOUNT, This installation creates an ACCOUNT named DSN$SERVER. %UAF-I-ADDMSG, user record successfully added %UAF-I-RDBADDMSGU, identifier DSN$SERVER value: [000376,000200] added to rights data base %DSNLINK012-I-MODACC, Modifying account DSN$SERVER 6 times %VMSINSTAL-I- ACCOUNT, This installation updates an ACCOUNT named DSN$SERVER. %UAF-I-MDFYMSG, user record(s) updated %VMSINSTAL-I- ACCOUNT, This installation updates an ACCOUNT named DSN$SERVER. %UAF-I-MDFYMSG, user record(s) updated %VMSINSTAL-I- ACCOUNT, This installation updates an ACCOUNT named DSN$SERVER. %UAF-I-MDFYMSG, user record(s) updated %VMSINSTAL-I- ACCOUNT, This installation updates an ACCOUNT named DSN$SERVER. %UAF-I-MDFYMSG, user record(s) updated %VMSINSTAL-I- ACCOUNT, This installation updates an ACCOUNT named DSN$SERVER. %UAF-I-MDFYMSG, user record(s) updated %VMSINSTAL-I- ACCOUNT, This installation updates an ACCOUNT named DSN$SERVER. %UAF-I-MDFYMSG, user record(s) updated 2-14 Modem Transport Installation Modem Transport Installation 2.4 Installing DSNlink on a DAN A new DSN$STARTUP.COM command procedure that reflects the parameters you have specified during this installation will now be created in SYS$STARTUP. If you wish to change any of these installation parameters, you can create a DSNlink site- specific startup file. 11 If you wish to have DSNlink started each time your system startup procedure executes, please ensure that your site specific startup file SYS$MANAGER:SYSTARTUP_ V5.COM includes the following line after the queue manager and DECnet (if installed) are started: $ @SYS$STARTUP:DSN$STARTUP.COM Or, you can add an entry to SYSMAN STARTUP to invoke DSNlink. Make sure that you execute SYS$STARTUP:DSN$STARTUP.COM on all other nodes in this VAXcluster once the DSNlink installation completes. %DSNLINK012-I-CRESTRTUP, creating your DSNlink startup file... %DSNLINK012-I-FILEPREP, preparing DSNlink files and images... %DSNLINK012-I- STARTUP, DSN$STARTUP.COM will be executed after files are moved %VMSINSTAL-I- MOVEFILES, Files will now be moved to their target directories... Beginning DSNlink Startup on node JANET %UAF-I-MDFYMSG, user record(s) updated DSNlink startup completed on node JANET DSNlink Installation Verification Procedure ------------------------------------------- To verify that DSNlink has been successfully installed, and to register you as an DSNlink user with Digital, the DSNlink Registration Application will now be executed. You will be asked for *your* electronic address, which will permit Digital to send information back to your system. The electronic address you use depends upon the transport mechanism you will use to connect with Digital. If the registration process fails due to a modem error or other problem connecting to Digital, it is not necessary to reinstall DSNlink. Remedy the problem and execute the registration application again. Modem Transport Installation 2-15 Modem Transport Installation 2.4 Installing DSNlink on a DAN Should your electronic address change in the future, you must execute the Registration Application again. See the DSNlink Manager's Guide for information on how this is done. Press RETURN to continue... You are using the Modem Transport. Your electronic address should be your modem's telephone number, including the area or region code. In the USA, use the format (000)000-0000 to enter your modem's number. DSNlink V1.2 for OpenVMS VAX Copyright (c) 1989, 1992 by Digital Equipment Corporation Digital Equipment Corporation Proprietary Service Tool All Rights Reserved DSNlink V1.2 for OpenVMS VAX Registration 12 Establishing connection to DSNlink Host - please wait... Your registered electronic address is currently: (617)555-3280 13 Enter your new electronic address or press RETURN: 14 Electronic address not changed Installation of DSNLINK012 V1.2 completed at hh:mm VMSINSTAL procedure done at hh:mm 2-16 Modem Transport Installation Modem Transport Installation 2.4 Installing DSNlink on a DAN 1 Allocate the device that contains the distribution media. You do not need to do this if you are installing DSNlink from disk. 2 Invoke the VMSINSTAL utility. DSNLINK012 is the name of the software product to be installed and mtcu: is the device that was previously allocated. If you are installing on an AXP system the product name that you enter is DSNLINK_AXP012. 3 Digital recommends that files replaced by this installation be purged. 4 DSNlink allows you to use an X.25 link, a modem using the telephone system, or DECnet as a transport. This installation example presumes modem was specified as the type of transport. If you plan to use either X.25 or DECnet as the transport type, see the installation example in Section 3.3. 5 The Access Number and Authorization Code can be found in the authorization letter that was shipped separately from the DSNlink distribution. If you are installing this software on a computer system that is already running DSNlink, your previously assigned authorization code remains valid. 6 The installation asks you if DSNlink is currently being installed on the DCN. If your response to this question is NO, then proceed to the next step. If your answer is YES, please use the example installation in Section 2.3. 7 Since you are installing DSNlink on a DAN, you are prompted for the node name of the DCN. It is not necessary to enter colons as a part of the response to this question. 8 By default, DSNlink uses UIC [376,200] for the exclusive use of the DSNlink network server account DSN$SERVER. You can choose a different UIC during installation- unless the DSN$SERVER account already exists. In this case the UIC is left unchanged and the the following informational message is displayed: %DSNLINK-I-ACCEXISTS, Using existing DSN$SERVER account Modem Transport Installation 2-17 Modem Transport Installation 2.4 Installing DSNlink on a DAN 9 Although SYS$COMMON is the default location for the DSN$SERVER account, you can choose to locate this account wherever there is sufficient disk space. Note that this prompt is not displayed if the DSN$SERVER account already exists. Instead, the default DSN$SERVER device and directory is used. 10 Digital recommends accepting the default to this prompt. If an existing queue is used for DSN$BATCH, make sure that the batch queue specified executes on the DCN. 11 For more information on creating a DSNlink site-specific startup file, refer to Section 4.3. 12 Invoking the DSNlink Registration application acts as the Installation Verification Procedure (IVP) during the DSNlink installation. Note that the IVP command procedure SYS$TEST:DSN$IVP.COM can also be invoked independently after installation to test the integrity of the DSNlink software. 13 This phone number is used by the DSNlink Host system to contact your DCN. 14 Digital recommends that you enter so that the default value is used. ________________________ Note ________________________ When the DSNlink Host system attempts to send any data, it dials the telephone number that you provided. Ensure this telephone number is correct; otherwise, the DSNlink Host system cannot make contact with your system. If you make a mistake in entering this phone number, the DSNlink Registration application must be executed again, as described in the DSNlink for OpenVMS Manager's Guide. ______________________________________________________ 2-18 Modem Transport Installation 3 _________________________________________________________________ X.25 and DECnet Transport Installation One installation example (see Section 3.3) is presented in this chapter. It represents the following two installation types: o Installing with X.25 transport on a DAN or DCN o Installing with DECnet transport on a DAN or DCN Please make sure you have completed these steps before continuing with this chapter: 1. Read Chapter 1. 2. Verified that your system meets all of the criteria in the Preinstallation checklist (see Section 1.14). 3. Chosen an installation script (see Section 1.15). 3.1 Installation Overview DSNlink is installed using the VMSINSTAL command procedure. The installation example is shown as it is displayed at your terminal. Explanations for the example are provided at the end of each example installation. Default responses appear in square brackets ([]) You may notice slight variations in naming conventions if you are installing on an AXP system. Any variations that affect your response to the installation are noted in the explanatory text. The AXP installation kit name used in Step 2 is DSNLINK_AXP012. X.25 and DECnet Transport Installation 3-1 X.25 and DECnet Transport Installation 3.2 How to Abort an Installation 3.2 How to Abort an Installation To abort an installation procedure at any time, enter . The installation procedure deletes all files it has created up to that point and exits. To retry the installation procedure after entering , start over at Step 2 in the installation procedure. 3.3 Installing DSNlink Using the X.25 or DECnet Transport Example Installation Username: SYSTEM Password: $ ALLOCATE mtcu: 1 %DCL-I-ALLOC, mtcu: allocated $ SET DEFAULT SYS$UPDATE $ @VMSINSTAL DSNLINK012 mtcu: 2 VAX VMS Software Product Installation Procedure Vn.n It is dd-mmm-yyyy at hh:mm. Enter a question mark (?) at any time for help. * Are you satisfied with the backup of your system disk [YES]? Please mount the first volume of the set on mtcu: *Are you ready? YES The following products will be processed: DSNlink V1.2 Beginning installation of DSNlink V1.2 at hh:mm %VMSINSTAL-I-RESTORE, Restoring product save set A ... %VMSINSTAL-I- RELMOVED, Product's release notes have been moved to SYS$HELP. © Digital Equipment Corporation, 1989, 1992. All Rights Reserved. * Do you want to purge files replaced by this installation [YES]? 3 DSNlink allows you to use an X.25 link, a modem using the telephone system, or DECnet as a transport. Please indicate what transport type you will be using to connect to Digital. Answer Modem, X.25, or DECnet. * Which DSNlink transport will you use to connect to Digital [Modem]: X.25 4 3-2 X.25 and DECnet Transport Installation X.25 and DECnet Transport Installation 3.3 Installing DSNlink Using the X.25 or DECnet Transport The answers to the following questions can be found in the authorization letter which you should have received. Please be sure to enter the values correctly. Incorrectly entered values will cause DSNlink to be non-operational. * Enter your Digital Access Number : nnnnnnn 5 * Enter your Access Number Authorization Code : xxxx-xxxx-xxxx-xxxx To ensure that the DSNlink network runs with the proper quotas and privileges, this installation procedure will create an account for the DSNlink network server and network objects. The name of the account is DSN$SERVER. It is set for batch and network access and has TMPMBX and NETMBX privileges. A random password will be set on this account when DSNlink starts up. * UIC for the DSN$SERVER account [376,200]: 6 * Enter the device for the DSN$SERVER account [SYS$COMMON:]: 7 Unsolicited informational DSNlink Mail messages may be sent from Digital to your site. These messages fall into several categories, which are each identified by a logical name that you can modify by creating a DSNlink site- specific startup file. This installation procedure will define these logical names as shown below: 8 DSN$MAIL_CC_RECIPIENT = %NONE% DSN$MAIL_FLASH_RECIPIENT = SYSTEM DSN$MAIL_INFORMATION_RECIPIENT = %NONE% DSN$MAIL_MARKETING_RECIPIENT = %NONE% DSN$MAIL_SURVEY_RECIPIENT = %NONE% You may disable receipt of any of these catagories of information by defining the logical equivalence name to be %NONE%. %DSNLINK012-I-MAIL_ LOGICALS, The logicals will be defined in DSN$STARTUP.COM DSNlink Mail and DSNlink File Copy queue jobs for execution in batch. By default, the DSN$STARTUP procedure will create and start a separate batch queue called DSN$BATCH for this purpose. If you wish to execute the DSNlink batch jobs in an already existing batch queue, the system logical name DSN$BATCH will be defined to use this batch queue, rather than create a separate queue. * Enter the name of the DSNlink batch queue [DSN$BATCH]: 9 X.25 and DECnet Transport Installation 3-3 X.25 and DECnet Transport Installation 3.3 Installing DSNlink Using the X.25 or DECnet Transport All installation questions have been answered. The rest of the installation will proceed automatically and may take up to 15 minutes, depending on your system type. %VMSINSTAL-I-SYSDIR, This product creates system disk directory SYS$COMMON:[DSN]. %VMSINSTAL-I-SYSDIR, This product creates system disk directory SYS$COMMON:[DSN.WORK]. %VMSINSTAL-I-SYSDIR, This product creates system disk directory SYS$COMMON:[DSN.LOGS]. %DSNLINK012-I-CREACC, Creating account DSN$SERVER %VMSINSTAL-I- ACCOUNT, This installation creates an ACCOUNT named DSN$SERVER. %UAF-I-ADDMSG, user record successfully added %UAF-I-RDBADDMSGU, identifier DSN$SERVER value: [000376,000200] added to rights data base %DSNLINK012-I-MODACC, Modifying account DSN$SERVER 6 times %VMSINSTAL-I- ACCOUNT, This installation updates an ACCOUNT named DSN$SERVER. %UAF-I-MDFYMSG, user record(s) updated %VMSINSTAL-I- ACCOUNT, This installation updates an ACCOUNT named DSN$SERVER. %UAF-I-MDFYMSG, user record(s) updated %VMSINSTAL-I- ACCOUNT, This installation updates an ACCOUNT named DSN$SERVER. %UAF-I-MDFYMSG, user record(s) updated %VMSINSTAL-I- ACCOUNT, This installation updates an ACCOUNT named DSN$SERVER. %UAF-I-MDFYMSG, user record(s) updated %VMSINSTAL-I- ACCOUNT, This installation updates an ACCOUNT named DSN$SERVER. %UAF-I-MDFYMSG, user record(s) updated %VMSINSTAL-I- ACCOUNT, This installation updates an ACCOUNT named DSN$SERVER. %UAF-I-MDFYMSG, user record(s) updated A new DSN$STARTUP.COM command procedure that reflects the parameters you have specified during this installation will now be created in SYS$STARTUP. If you wish to change any of these installation parameters, you can create DSNlink site- specific startup file. 10 If you wish to have DSNlink started each time your system startup procedure executes, please ensure that your site specific startup file SYS$MANAGER:SYSTARTUP_ V5.COM includes the following line after the queue manager and DECnet (if installed) are started: 3-4 X.25 and DECnet Transport Installation X.25 and DECnet Transport Installation 3.3 Installing DSNlink Using the X.25 or DECnet Transport $ @SYS$STARTUP:DSN$STARTUP.COM Or, you can add an entry to SYSMAN STARTUP to invoke DSNlink. Make sure that you execute SYS$STARTUP:DSN$STARTUP.COM on all other nodes in this VAXcluster once the DSNlink installation completes. %DSNLINK012-I-CRESTRTUP, creating your DSNlink startup file... %DSNLINK012-I-FILEPREP, preparing DSNlink files and images... %DSNLINK012-I- STARTUP, DSN$STARTUP.COM will be executed after files are moved %VMSINSTAL-I- MOVEFILES, Files will now be moved to their target directories... Beginning DSNlink startup on node MYNODE %UAF-I-MDFYMSG, user record(s) updated DSNlink startup completed on node MYNODE DSNlink Installation Verification Procedure ------------------------------------------- To verify that DSNlink has been successfully installed, and to register you as an DSNlink user with Digital, the DSNlink Registration Application will now be executed. You will be asked for *your* electronic address, which will permit Digital to send information back to your system. The electronic address you use depends upon the transport mechanism you will use to connect with Digital. If the registration process fails due to a modem error or other problem connecting to Digital, it is not necessary to reinstall DSNlink. Remedy the problem and execute the registration application again. Should your electronic address change in the future, you must execute the Registration Application again. See the DSNlink Manager's Guide for information on how this is done. Press RETURN to continue... You are using the X.25 transport. Your electronic address should 11 be of the form "X"+dte_ number. For example, if the DTE address is 100055512123, the electronic address is "X100055512123" (without the quotation marks). Specify a subaddress with the period (.); for example, "X100055512123.99"; and if necessary, a network name with the percent sign (%), for example "XTELENET%21635165.99". X.25 and DECnet Transport Installation 3-5 X.25 and DECnet Transport Installation 3.3 Installing DSNlink Using the X.25 or DECnet Transport DSNlink V1.2 for OpenVMS VAX Copyright (c) 1989, 1992 by Digital Equipment Corporation Digital Equipment Corporation Proprietary Service Tool All Rights Reserved DSNlink V1.2 for OpenVMS VAX Registration 12 Establishing connection to DSNlink Host - please wait... Your registered electronic address is currently: Enter your new electronic address or press RETURN: X100071959200.15 13 Your new registered electronic address is: X100071959200.15 Installation of DSNLINK012 V1.2 completed at hh:mm VMSINSTAL procedure done at hh:mm 1 Allocate the device that contains the distribution media. You do not need to do this if you are installing DSNlink from disk. 2 Invoke the VMSINSTAL utility. DSNLINK012 is the name of the software product to be installed and mtcu: is the device that was previously allocated. If you are installing on an AXP system the name that you enter is DSNLINK_AXP012. 3 Digital recommends that files replaced by this installation be purged. 4 DSNlink allows you to use an X.25 link, a modem using the telephone system, or DECnet as a transport. 5 The Access Number and Authorization Code can be found in the authorization letter that was shipped separately from the DSNlink distribution. If you are installing this software on a computer system that is already running DSNlink, your previously assigned authorization code remains valid. 6 By default, DSNlink uses UIC [376,200] for the exclusive use of the DSNlink network server account DSN$SERVER. You can choose a different UIC during installation- unless the DSN$SERVER account already exists. In this case the UIC is left unchanged and the the following informational message is displayed: %DSNLINK-I-ACCEXISTS, Using existing DSN$SERVER account 3-6 X.25 and DECnet Transport Installation X.25 and DECnet Transport Installation 3.3 Installing DSNlink Using the X.25 or DECnet Transport 7 Although SYS$COMMON is the default location for the DSN$SERVER account, you can choose to locate this account wherever there is sufficient disk space. Note that this question is not asked if the DSN$SERVER account already exists. Instead, the default DSN$SERVER device and directory is used. 8 This is a list of the DSNlink Mail logicals that define where different Digital Communiques are currently to be sent. You can disable receiving a particular category of information by defining the appropriate logical name in SYS$STARTUP:DSN$SYSTARTUP.COM to be %NONE%. The following list describes the type of information that each logical name pertains to: o DSN$MAIL_FLASH_RECIPIENT defines mail address(es) that receive time critical information sent from the DSNlink Host system. o DSN$MAIL_INFORMATION_RECIPIENT defines mail address(es) that receive other classes of information that do not directly relate to marketing information or Flash Mail. o DSN$MAIL_MARKETING_RECIPIENT defines mail address(es) that receive messages about new products and services, as well as update information about existing products and services. o DSN$MAIL_SURVEY_RECIPIENT defines mail address(es) that receive surveys from Digital concerning service and product quality. o DSN$MAIL_CC_RECIPIENT defines mail address(es) that receive a courtesy copy of any mail sent from the DSNlink Host system to your users. In addition, see the DSNlink for OpenVMS Manager's Guide for a description of how the SYSTEM and the DSN$MAIL_ DELIVER_FAILURE_RECIPIENT logical names are used to ensure DSNlink Mail delivery. 9 Digital recommends accepting the default to this question. If an existing queue is used for DSN$BATCH, make sure that the batch queue specified executes on the DCN. X.25 and DECnet Transport Installation 3-7 X.25 and DECnet Transport Installation 3.3 Installing DSNlink Using the X.25 or DECnet Transport 10 For more information on creating a DSNlink site-specific startup file, refer to Section 4.3. 11 Note that if you specified DECnet as the transport, the following explanatory text is displayed: You are using the DECnet transport. Your electronic address should be of the form "D"+node_name. For example, if your node is KOLSEN, the electronic address is DKOLSEN. 12 Invoking the DSNlink Registration application acts as the Installation Verification Procedure (IVP) during the DSNlink installation. Note that the IVP command procedure SYS$TEST:DSN$IVP.COM can also be invoked independently after installation to test the integrity of the DSNlink software. 13 This electronic address is used by the DSNlink Host system to contact the DCN. If an incorrect electronic address is entered here, the DSNlink Host system cannot connect to your DCN when the Digital Customer Support Center (CSC) has information for you. The format of this electronic address depends on whether you have specified X.25 or DECnet as the type of transport: o For the X.25 format, the electronic address is based on your DTE number and may contain up to four character fields, depending on your system. These character fields are: o The "X" character to mark the X.25 electronic address. This is required. o The network name plus the percent "%" character. This is optional. o Your DTE number. This is required. o The period "." character plus your subaddress. This is optional. These character fields are concatenated to form your electronic address as follows: X[network_name%]dte_number[.subaddress] Here are some examples of X.25 electronic addresses: 3-8 X.25 and DECnet Transport Installation X.25 and DECnet Transport Installation 3.3 Installing DSNlink Using the X.25 or DECnet Transport o If your DTE address is 100055512123 then your electronic address is X100055512123. o If your DTE address is 21635165, your subaddress is 99, and your network name is TELENET then your electronic address is XTELENET%21635165.99. o For DECnet, the electronic address is your node name preceded by the letter D as shown: Dnode_name For example, if KELSON is the name of your node, your complete DECnet electronic address for DSNlink is DKELSON. ________________________ Note ________________________ When the DSNlink Host system attempts to connect to your system, it uses the electronic address that you provide. Make sure that this electronic address is correct; otherwise, the DSNlink Host system cannot make contact with your system. If you make a mistake in entering this electronic address, execute the DSNlink Registration application as described in the DSNlink for OpenVMS Manager's Guide. ______________________________________________________ X.25 and DECnet Transport Installation 3-9 4 _________________________________________________________________ After Installing DSNlink This chapter contains information on how to fine tune DSNlink for your system. 4.1 Changing the DSNlink Transport If you wish to change the DSNlink transport you must reinstall DSNlink. 4.2 VMScluster Installation Follow the procedures in this section if you installed DSNlink on a VMScluster. 4.2.1 Start up DSNlink on DANs in the VMScluster If you installed DSNlink on a DCN in a VMScluster, make sure that the DSNlink startup command file is executed on each DAN in that VMScluster. To run the startup command file, enter the following command from the DCL prompt: $ @SYS$STARTUP:DSN$STARTUP.COM It is recommended that you start DSNlink from the SYSTEM account. 4.2.2 Replace DCLTABLES.EXE If you have installed DSNlink on a DCN or DAN that is part of a VMScluster, replace DCLTABLES.EXE (which contains the CLI tables) on the other nodes of that VMScluster that are DANs. To replace DCLTABLES.EXE, complete the following procedure: 1. Log in to a node on the VMScluster. After Installing DSNlink 4-1 After Installing DSNlink 4.2 VMScluster Installation 2. Run the SYSMAN utility: $ RUN SYS$SYSTEM:SYSMAN SYSMAN> SET ENVIRONMENT/CLUSTER SYSMAN> SET PROFILE/PRIVILEGE=ALL SYSMAN> DO INSTALL REPLACE SYS$SHARE:DCLTABLES . . . SYSMAN> EXIT Any users who are logged in to the VMScluster during this procedure must log out and log back in again to use the new CLI tables. 4.3 The Site-Specific Startup File Digital recommends that you create a site-specific startup file if you run DSNlink with nondefault logical name definitions. This site-specific startup file preserves your logical name definitions if you reinstall DSNlink. Description This file contains DSNlink logical name definitions that you define for your own system. This file is called DSN$SYSTARTUP.COM and resides in the SYS$MANAGER directory. The site-specific startup file is executed by the DSNlink startup file. The definitions in the site-specific file supercede the default DSNlink logical definitions. Creating a Site-Specific Startup File A file template is provided in the DSNlink software kit to assist you in creating your own site-specific startup file. This file is named DSN$SYSTARTUP.TEMPLATE and is located in the SYS$MANAGER directory. All of the DSNlink logical definitions that can be customized are described in the DSNlink for OpenVMS Manager's Guide appendixes as well as within this template file. Edit the template file so that it contains the logical name definitions that you use at your site. Then rename the template file to DSN$SYSTARTUP.COM and leave it in the SYS$MANAGER directory. 4-2 After Installing DSNlink After Installing DSNlink 4.3 The Site-Specific Startup File Command File Execution The site-specific startup file is executed when the DSNlink startup file, DSN$STARTUP.COM, is executed. To run the startup command file, enter the following command from the DCL prompt: $ @SYS$STARTUP:DSN$STARTUP.COM It is recommended that you start DSNlink from the SYSTEM account. 4.4 Special Mail Logical Names Digital offers you an ongoing information service using DSNlink Mail. You are sent timely news messages about existing products, new products, and product updates. These messages are divided into several topical categories. You decide which, if any message category that you want to receive. You also choose who receives these messages on your DSNlink system. The following list of logical names define the recipient list for the Digital Communiques, courtesy copies, and failed mail. Define these logical names by creating a site- specific startup file as described in Section 4.3. o DSN$MAIL_CC_RECIPIENT o DNS$MAIL_DELIVER_FAILURE_RECIPIENT o DSN$MAIL_FLASH_RECIPIENT o DSN$MAIL_INFORMATION_RECIPIENT o DSN$MAIL_MARKETING_RECIPIENT o DSN$MAIL_SURVEY_RECIPIENT o DSN$NETWORK_FAILURE_DISTRIBUTION Refer to the DSNlink for OpenVMS Manager's Guide for more information. After Installing DSNlink 4-3 A _________________________________________________________________ Modem Troubleshooting This chapter provides: o A list of the modems that can be used by DSNlink. o A summary of various modem commands. o A procedure for using a Hayes compatible modem. o A description of some possible DSNlink modem problems, and instructions on how to resolve them. A.1 List of Modems Digital recommends the following modems for use with DSNlink: o 2400-baud modems: - Digital DF124-CA, Rev. 1.20 or greater - Digital DF124-CM, Rev. 1.20 or greater - Digital DF242-CA, Rev. 1.50 or greater - Hayes Smartmodem 2400 (Model 231AA) o 9600-baud modems: - Digital DF296-DA, Rev. 1.22 or greater - Digital DF196-DM, Rev. 1.22 or greater The modem setup files provided in the DSNlink installation kit correctly configure these modems for use with the DSNlink software. Modem Troubleshooting A-1 Modem Troubleshooting A.2 Modem Prefix String A.2 Modem Prefix String A site-specific modem prefix string is sent to the modem connected to the DSNlink Communications Device. The first character in this string represents the type of phone service that you use with your modem. Enter the letter T if you have tone dial service or P if you have pulse dial service. The second character in this string usually represents the initial number required by your phone service for outgoing calls. Some general guidelines for prefix strings for Digital modems follow: o Use T1 for a standard U.S. residential or business line. o Use Tn1 for local PBX, where n is the number pressed to get to long distance service. This number is typically 8 or 9. Keep in mind that the DCN dials a toll free 800 number, and in some cases, this makes a difference in the prefix string. o Use Tn=1 for local PBX when there is a delay in the secondary dial tone. The equal sign (=) instructs the modem to wait for another dial tone before proceeding with the remainder of the dial string. Here are some specific examples: o You have a tone dial service, your modem is connected to PBX equipment, and the number 8 must precede outgoing calls. You would enter T8. o You are in the U.S. and your modem is connected to a standard business or a residential phone line. The number 1 must precede outgoing long-distance calls, including 800 number calls. In this case enter T1 if you have a tone dial service, or P1 if you have a pulse dial service. Please note that if you are in the U.S. your system dials an 800 number when communicating with Digital. If your access to 800 service is on a different line than your regular long distance service, your modem prefix string must reflect this. A-2 Modem Troubleshooting Modem Troubleshooting A.3 Echo and Dial Modem Commands A.3 Echo and Dial Modem Commands When modem echo is enabled the commands you type to the modem are displayed on your terminal. If modem echo is disabled the commands are not displayed. During a modem troubleshooting session, you may need to send commands directly to the modem to cause the modem echo to be enabled or to initiate a dialing sequence. Table A-1 shows the command that causes modem echo to be enabled and Table A-2 shows the command that causes the modem to initiate a dialing sequence. Table_A-1_Modem_Enable_Echo_Sequences_and_Responses________ Modem Modem_Type___________Enable_Echo_Sequence_________Response_ Digital DF124+ SET P2:1 Ready Digital DF196 SET P2:1 Ready Digital DF242 SET P2:1 Ready Digital DF296 SET P2:1 Ready Hayes Smartmodem ATE1 OK or 0 2400_(Model_231AA)_________________________________________ Modem Troubleshooting A-3 Modem Troubleshooting A.3 Echo and Dial Modem Commands Table_A-2_Modem_Dialing_Sequences_and_Responses____________ Modem Modem_Type___________Dialing_Sequence_____________Response_ Digital DF124+ DIAL (prefix)[1]nnnnnnnnnnn[2Dialing Digital DF196 DIAL (prefix)[1]nnnnnnnnnnn[2Dialing Digital DF242 DIAL (prefix)[1]nnnnnnnnnnn[2Dialing Digital DF296 DIAL (prefix)[1]nnnnnnnnnnn[2Dialing Hayes Smartmodem ATD(prefix)[1]nnnnnnnnnnn[2] the modem should respond with either an OK or a 0. Modem Troubleshooting A-5 Modem Troubleshooting A.4 Conditions for Using a Hayes Compatible Modem 3. If you receive a "dataset hangup" error message about 30 seconds after entering the SET HOST/DTE command, it may be because your modem is holding DSR high. If this occurs, complete these additional steps: a. Connect a terminal directly to the modem and enter the following command to the modem: AT&S1&W b. Connect the modem back up to the DSNlink communications device, and then try entering the following command again: $ SET HOST/DTE DSN$COMMUNICATIONS_DEVICE 4. Decide which commands are needed to set up your modem to meet the conditions described in Section A.4. The commands issued by the standard Hayes setup script are documented in Section B.2.2; try those commands as a starting point. If those are not successful, then look at the alternate modem setup commands documented in Section B.3. The user's manual for your modem is also often helpful in determining how the command set for your modem differs from standard Hayes AT commands. Enter the appropriate commands to your modem from either a terminal connected to the modem, or after entering the SET HOST/DTE command to the DSNlink Communications Device, as previously described. 5. To prevent DSNlink from issuing any commands to your modem when starting up, complete the following procedure: 1. Edit the SYS$STARTUP:DSN$STARTUP.COM file and comment out the following line of code: $! DS DSN$DIALER_SETUP SYS$SYSTEM:DSN$HAYES_SETUP_B 2. If you have previously executed DSN$STARTUP.COM, you also need to de-assign that logical by entering the following command: $ DEASSIGN/SYSTEM/EXEC DSN$DIALER_SETUP By not defining this logical, you prevent the default modem setup from being used when DSNlink starts up. A-6 Modem Troubleshooting Modem Troubleshooting A.4 Conditions for Using a Hayes Compatible Modem 6. Start up DSNlink by entering the following command: $ @SYS$STARTUP:DSN$STARTUP.COM 7. Test the success of your startup by entering one of the following DSNlink commands: $ DSN REGISTER $ DSN ITS $ DSN LOOPBACK/COUNT=100 a. If you are able to successfully connect to the DSNlink Host system, then your modem is now appropriately configured for use by DSNlink. b. If you are unsuccessful in connecting, and are in the U.S., call your Digital CSC at (800) 354-9000 for further assistance. 8. After you have determined the appropriate setup commands for your modem, you can either leave the DSN$DIALER_ SETUP logical commented out (in which case you will have to manually re-configure the modem if it loses its parameter settings for any reason). If you are in the U.S. you can contact the Digital CSC and ask to have a modem setup file built that includes the appropriate commands. The .DIALER files are binary files, not ASCII text. You cannot just edit one of the supplied .DIALER files to enter the commands needed for your modem. Digital does not guarantee the operation of DSNlink with .DIALER files that have been modified in any way. 9. Please send mail to DSN%DSNLINK with the information on the make and model of modem that you have, and which setup files (or manually typed commands) were used. There is an article in the DSNlink database (accessible via DSNlink ITS) listing the types of modems that Digital customers have reported successfully using with DSNlink. Modem Troubleshooting A-7 Modem Troubleshooting A.5 Types of Possible DSNlink Modem Problems A.5 Types of Possible DSNlink Modem Problems The upcoming sections describe some of the problems that you may encounter while using a modem with DSNlink: o No Dial Tone Error on Modem o SYSTEM-F-HANGUP o DSN-E-MODEM_ERR o Modem Does Not Respond A.5.1 No Dial Tone Error on Modem When testing a Digital modem as shown below, an error that can be encountered is "NO DIAL TONE": $ SET TERMINAL/PERMANENT/TYPE_AHEAD/SPEED=2400/MODEM - DSN$COMMUNICATIONS_DEVICE $ SET HOST/DTE DSN$COMMUNICATIONS_DEVICE %REM-I-TOEXIT, connection established, type ^\ to exit Ready DIAL T9=18005559876 NO DIAL TONE This error usually indicates that the phone line is not connected to the phone line jack on the modem. Check to make sure that this connection is secure, or that the phone line is not connected to the telephone set jack. The telephone set jack is for use with an optional telephone. A.5.2 SYSTEM-F-HANGUP There are two types of "SYSTEM-F-HANGUP" errors. The first is caused when there is no power to the modem. The second is caused when the terminal server port is improperly mapped. SYSTEM-F-HANGUP When Attempting to Make a DSNlink Connection If there is no power to the modem, any attempt to establish a DSNlink connection produces a "SYSTEM-F-HANGUP, data set hang-up" error. The following is an example of how such an error might occur: A-8 Modem Troubleshooting Modem Troubleshooting A.5 Types of Possible DSNlink Modem Problems $ DSN ITS DSNlink V1.2 for OpenVMS VAX Copyright (c) 1989, 1992 by Digital Equipment Corporation Digital Equipment Corporation Proprietary Service Tool All Rights Reserved DSNlink V1.2 for OpenVMS VAX Interactive Text Search Establishing connection to DSNlink host - please wait... %DSN-F-TERMINATE, DSNlink link has been terminated -SYSTEM-F-HANGUP, data set hang-up Make sure that the power adapter is properly installed and that the power indicator light on the modem is on. At this point, you should shut down and then restart DSNlink to properly configure the modem. Be careful not to confuse the "SYSTEM-F-HANGUP" error with the "DSN-F-HANGUP hangup condition detected" error. DSN- F-HANGUP indicates that the line was disconnected and does not normally indicate a lack of power to the modem. SYSTEM-F-HANGUP When Attempting to Use SET HOST/DTE A "SYSTEM-F-HANGUP" error can also occur when attempting to test a DSNlink modem using the DCL command SET HOST/DTE to a terminal server port. After you enter the SET HOST/DTE command and then enter a character, the "SYSTEM-F-HANGUP" error occurs if the server port is improperly mapped. If this error is encountered on a SET HOST/DTE to a terminal server port, recheck the port configuration. Refer to Section 1.11.1 and Section 1.11.2 for more information. A.5.3 DSN-E-MODEM_ERR You might encounter the following error when attempting to make a connection with the DSNlink Host system: Modem Troubleshooting A-9 Modem Troubleshooting A.5 Types of Possible DSNlink Modem Problems $ DSN ITS DSNlink V1.2 for OpenVMS AXP (TM) Copyright (c) 1989, 1992 by Digital Equipment Corporation Digital Equipment Corporation Proprietary Service Tool All Rights Reserved DSNlink V1.2 for OpenVMS AXP Interactive Text Search Establishing connection to DSNlink host - please wait... %DSN-F-TERMINATE, DSNlink link has been terminated -DSN-E-MODEM_ERR, modem error This error may indicate that the phone line is not connected to the phone line jack on the modem. Check to ensure this connection is secure or that the phone line is not connected to the telephone set jack. The telephone set jack is for use with an optional telephone. A.5.4 Modem Does Not Respond For security reasons, DSNlink leaves the DSNlink Communications Device in a /NOTYPE_AHEAD state when not being used. When a request for communication is made, DSNlink changes to a /TYPE_AHEAD state for the duration of the communication. With /TYPE_AHEAD disabled, the modem cannot be used. This prevents logins on the line when DSNlink is not running. Since DSNlink does a SET TERMINAL/PERMANENT/NOTYPE_AHEAD whenever DSNlink is stopped for any reason (including normal shutdown), the DSNlink Communications Device is then left in a /NOTYPE_AHEAD state. Thus, the modem appears to be dead if attempts are made to use it for some other purpose when DSNlink is not running. To change this enter the following commands to the DSNlink Communications Device: $ SET TERMINAL/PERMANENT/TYPE_AHEAD DSN$COMMUNICATIONS_DEVICE $ SET HOST/DTE DSN$COMMUNICATIONS_DEVICE Another possible cause of the modem appearing to be dead is that it is not powered on. If this is the case, you should shutdown DSNlink, power on the modem, and then restart DSNlink. It is important to restart DSNlink so the modem parameters are properly set. A-10 Modem Troubleshooting B _________________________________________________________________ Modem Scripts In most cases the modem dialer and setup scripts that are selected during DSNlink installation are sufficient. A small percentage of DSNlink users may need to perform some additional tasks. This appendix provides some guidelines for modem troubleshooting. Please only use this information while working with a Digital specialist. B.1 Overview This appendix is divided into two sections: o Default-Description of modem scripts that may be selected during DSNlink installation o Alternate Hayes-Description of alternate Hayes-style modem scripts o Alternate Digital-Description of alternate Digital modem scripts Modem Command Usage Each DSNlink modem can have two sets of commands or responses as follows: o The first set is the modem setup script invoked only once during DSNlink startup. o The second set is the dialer script used to perform the actual modem dialing. Within the examples in this appendix, the character strings sent and returned are shown exactly as issued and expected. The following conventions are used in these examples. o The circumflex (^) character has two possible meanings. If the character string following the ^ character is uppercase, then interpret the ^ as a control character. Modem Scripts B-1 Modem Scripts B.1 Overview For example, ^B is a Ctrl/B. If the character string following the ^ character is lowercase, then interpret the ^ literally. For example, ^b is literally the circumflex character (^) followed by a lowercase letter b. o The following common control characters are shown differently to improve readability: o is a carriage return. o is a line feed. o The string denotes the modem prefix string. The modem prefix string is typically either the letter T or the letter P, followed by a zero or more digits; for example, T1 or T91. See Section A.2 for an explanation and examples of modem prefix strings. B.2 Default Modem Scripts During DSNlink installation you must choose from a list of supported modems. Your selection determines the modem setup and dialer script used by DSNlink. This section describes the modem setup scripts and the dialer scripts for these modems. o Digital DF124+ modem o Digital DF242 modem o Digital DF196 modem o Digital DF296 modem o Hayes modem B.2.1 Scripts for Digital Modems Example B-1 shows the modem setup script for both the Digital DF124+ and the DF242 modems. This script is contained in the DSN$DF242_SETUP.DIALER file. Example B-1 DF242 Modem Setup Script Example (continued on next page) B-2 Modem Scripts Modem Scripts B.2 Default Modem Scripts Example B-1 (Cont.) DF242 Modem Setup Script Example Sent to Modem Response Purpose ------------- -------- ------- ^B Ready Get attention of modem ^As p/ope 2,0,0,0,0, 0,0,0,0,0,0,0,1,1,1 r Set operational params ^As p/com 4,1,1,0,0, 0,2,0 r Set communication params ^As p/dis 1,1,1,1 r Set disconnect processing ^As p/err 0,0,0,0,0,0 r Set error handling ^As p/sbu 0,1,1,1 r Set speed buffering disabled ^Aw r Write to Memory Example B-2 shows the modem setup script for both the Digital DF196 and the DF296 modems. This script is contained in the DSN$DF196_SETUP_9600.DIALER file. Example B-2 DF196 and DF296 Modem Setup Script Example Sent to Modem Response Purpose ------------- -------- ------- ^B Ready Get attention of modem ^ADEFAULT P/ALL r Set to factory defaults ^ASET P/OPE 6,0, ,,,,,,,,,0,,1,,,,0 r Set operational parameters ^ASET P4:0/COM r Set communication parameters ^ASET P/ERR ,,,,,,,0 r Set error handling ^ASET P/SBU ,,0 r Set speed buffering parameters ^AWRITE P/ALL r Write to memory Example B-3 shows the dialer script to be used for the Digital DF124+, DF242, DF196, and DF296 modems, as well as any other DIGITAL Modem Command Language (DMCL) modems. The contents of Example B-3 are contained in the file named DSN$DMCL.DIALER. Example B-3 Modem Dialer Script Example for the DF124+, DF242, DF196, and DF296 Modems (continued on next page) Modem Scripts B-3 Modem Scripts B.2 Default Modem Scripts Example B-3 (Cont.) Modem Dialer Script Example for the DF124+, DF242, DF196, and DF296 Modems Sent to Modem Response Purpose ------------- -------- ------- ^B Ready Get attention of modem ^AD 8003323765 d Dialing... Wait up to 60 seconds n No Answer b Busy e Modem error t No dial tone a:96 Attached, 9600 a:48 Attached, 4800 a:24 Attached, 2400 a:12 Attached, 1200 a:30 Attached, 300 B.2.2 Scripts for Hayes Modems This section shows both the standard modem setup script and the dialer script for the Hayes modem. Example B-4 shows the standard modem setup script for a Hayes modem. This script is contained in the DSN$HAYES_ SETUP_B.DIALER file. Example B-4 Hayes Modem Setup Script Example (continued on next page) B-4 Modem Scripts Modem Scripts B.2 Default Modem Scripts Example B-4 (Cont.) Hayes Modem Setup Script Example Sent to Modem Response Purpose ------------- -------- ------- AT OK Is the modem alive? 0 Alternate response allowed +++ OK If no response from above 0 Alternate response allowed ATE0 Turn off echo ATQ0 Turn on results codes ATV0 Use numeric codes ATM0 Turn off speaker AT&D2 Hangup when DTR is dropped ATS0=1 Answer on first ring ATS2=128 Ignore escape sequence AT&W Write parameters to memory AT&C0&S1&W Hold CD high; raise DSR on successful connection Example B-5 shows the dialer script for a Hayes modem. This dialer script is contained in the DSN$HAYES_B.DIALER file. The former name of this DSN$HAYES_B.DIALER file was DSN$HAYES_SIMPLE.DIALER. Modem Scripts B-5 Modem Scripts B.2 Default Modem Scripts Example B-5 Hayes Modem Dialer Script Example Sent to Modem Response Purpose ------------- -------- ------- AT OK Check if modem's alive 0 Alternate response allowed +++ OK If no response from above 0 Alternate response allowed ATD8003323765 Dials modem 1 Connected 3 No answer 4 Modem error 5 Connected 6 No dialtone 7 Busy 8 No answer Only the first digit of the response code is examined. So if a 10, 12, 14, etc., is returned when the modem connects, that response is interpreted as a successful connection. B.3 Alternate Modem Scripts This section describes the alternate modem setup scripts supplied by the DSNlink installation. These script files are as follows: o DSN$HAYES_SETUP_C.DIALER o DSN$HAYES_SETUP_D.DIALER o DSN$HAYES_SETUP_E.DIALER o DSN$DF196_SETUP_2400.DIALER o DSN$DF196_SETUP_4800.DIALER B.3.1 How to Use the Alternate Hayes Compatible Modem Setup Scripts If you want to use a Hayes compatible modem you must make sure that during the DSNlink installation you selected the Hayes compatible modem option. You can determine the installed modem script by entering the following: $ SHOW LOGICAL DSN$DIALER_SETUP "DSN$DIALER_SETUP" = "SYS$SYSTEM:DSN$HAYES_SETUP_x" (LNM$SYSTEM_TABLE) B-6 Modem Scripts Modem Scripts B.3 Alternate Modem Scripts If this logical is defined as anything other than DSN$HAYES_SETUP_n, where n is C, D, or E, then reinstall DSNlink and select the option for the Hayes compatible modem. For each of the Hayes modem setup scripts presented, DSNlink still uses the default dialer script file named DSN$HAYES_B.DIALER, described in Example B-5. Modem Scripts B-7 Modem Scripts B.3 Alternate Modem Scripts To use any one of these alternate Hayes compatible modem setup scripts, complete the following procedure: 1. Choose from the Hayes alternate modem setup scripts described in Section B.3.2-Section B.3.4. 2. Edit DSN$STARTUP.COM, and change the definition of the DSN$DIALER_SETUP logical to be one of following file names: o DSN$HAYES_SETUP_C.DIALER o DSN$HAYES_SETUP_D.DIALER o DSN$HAYES_SETUP_E.DIALER 3. Stop DSNlink by entering the following command: $ DSN SHUTDOWN 4. Restart DSNlink by executing DSN$STARTUP.COM, as follows: $ @SYS$STARTUP:DSN$STARTUP.COM B.3.2 Hayes Alternate Modem Setup Script C Example B-6 shows version C of the alternate modem setup script for a Hayes Modem. This script is contained in the DSN$HAYES_SETUP_C.DIALER file. The only difference between this file and the default DSN$HAYES_SETUP_B.DIALER file shown in Example B-4 is that the &C0 command has been replaced by an &C1 command. Example B-6 Alternate Hayes File-DSN$HAYES_SETUP_C.DIALER (continued on next page) B-8 Modem Scripts Modem Scripts B.3 Alternate Modem Scripts Example B-6 (Cont.) Alternate Hayes File-DSN$HAYES_SETUP_C.DIALER Sent to Modem Response Purpose ------------- -------- ------- AT OK Is the modem alive? 0 Alternate response allowed +++ OK If no response from above 0 Alternate response allowed ATE0 Turn off echo ATQ0 Turn on results codes ATV0 Use numeric codes ATM0 Turn off speaker AT&D2 Hangup when DTR is dropped ATS0=1 Answer on first ring ATS2=128 Ignore escape sequence AT&W Write parameters to memory AT&C1&S1&W Raise DSR and CD on successful connection B.3.3 Hayes Alternate Modem Setup Script D Example B-7 shows version D of the alternate modem setup script D for a Hayes Modem. This script is contained in the DSN$HAYES_SETUP_D.DIALER file. The only difference between this file and the DSN$HAYES_ SETUP_E.DIALER shown in Example B-8 is that the &C1 has been added. Modem Scripts B-9 Modem Scripts B.3 Alternate Modem Scripts Example B-7 Alternate Hayes File-DSN$HAYES_SETUP_D.DIALER Sent to Modem Response Purpose ------------- -------- ------- ATZ OK Software reset 0 Alternate response allowed +++ OK If no response from above 0 Alternate response allowed AT&F&W OK Set to factory defaults ATE0 Turn off echo ATV0 Use numeric codes ATM0 Turn off speaker AT&D2 Hangup when DTR is dropped ATS0=1 Answer on first ring ATS2=128 Ignore escape sequence AT&W Write parameters to memory AT&C1&S1&W Raise DSR and CD on successful connection B.3.4 Hayes Alternate Modem Setup Script E Example B-8 shows version E of the alternate modem setup Script E for a Hayes Modem. This script is contained in the DSN$HAYES_SETUP_E.DIALER file. The former name of this DSN$HAYES_SETUP_E.DIALER file was DSN$HAYES_SETUP_BTSZ.DIALER. Example B-8 Alternate Hayes File-DSN$HAYES_SETUP_E.DIALER (continued on next page) B-10 Modem Scripts Modem Scripts B.3 Alternate Modem Scripts Example B-8 (Cont.) Alternate Hayes File-DSN$HAYES_SETUP_E.DIALER Sent to Modem Response Purpose ------------- -------- ------- ATZ OK Software reset 0 Alternate response allowed +++ OK If no response from above 0 Alternate response allowed AT&F&W OK Reset to factory defaults ATE0 Turn off echo ATV0 Use numeric codes ATM0 Turn off speaker AT&D2 Hangup when DTR is dropped ATS0=1 Answer on first ring ATS2=128 Ignore escape sequence AT&W Write parameters to memory AT&S1&W Raise DSR on successful connection B.3.5 How to Set Up DF196 or DF296 Modems at Lower Baud Rates This section shows how to set up Digital DF196 and DF296 modems at a lower baud rate of either 4800 or 2400 baud. The ability to communicate across the telephone line at 9600 baud with the DSNlink Host system is dependent on the quality of the end-to-end phone connection from your site to Digital. If you have a Digital DF196 or DF296 modem and have repeated problems either connecting or staying connected to the DSNlink Host system, you may want to try communicating at 4800 or 2400 baud instead. Modem Scripts B-11 Modem Scripts B.3 Alternate Modem Scripts Alternative modem setup files are provided for this purpose. To set your modem to communicate at a lower speed, complete the following procedure: 1. Edit and locate the following line of code in SYS$STARTUP:DSN$STARTUP.COM: $ ds dsn$dialer_setup sys$system:dsn$df196_setup_9600 2. Replace this line of code with one of the following, depending on the desired baud rate: o For 4800 baud: $ ds dsn$dialer_setup sys$system:DSN$DF196_SETUP_4800 o For 2400 baud: $ ds dsn$dialer_setup sys$system:DSN$DF196_SETUP_2400 Do not change the definition of the DSN$MODEM_SERIAL_ PORT_SPEED logical from 9600. The modem still needs to communicate at 9600 baud over the serial port connection to your computer. These alternate modem setup scripts only change the baud rate that the modem uses to communicate across the telephone line. 3. Stop DSNlink by entering the following command: $ DSN SHUTDOWN 4. Restart DSNlink by executing DSN$STARTUP.COM, as follows: $ @SYS$STARTUP:DSN$STARTUP.COM The contents of the DSN$DF196_SETUP_2400.DIALER and the DSN$DF196_SETUP_4800.DIALER files are exactly the same as the default DSN$DF196_SETUP_9600.DIALER file with the following exceptions: o The first operational parameter is 6 in the 9600 baud file. o The first operational parameter is 2 in the 2400 baud file. o The first operational parameter is 4 in the 4800 baud file. B-12 Modem Scripts _________________________________________________________________ Index D Installing and registering _______________________________ DSNlink (cont'd) DECservers, setting parameters DECserver parameters, setting for DSNlink installation, , 1-13 to 1-16 1-13 to 1-16 modems Disk space required, 1-7 setup, 1-16 to 1-19 DSN$SYSTARTUP.COM, 4-2 troubleshooting, A-3 to DSNlink Applications Node A-10 (DAN) - Modem Transport Modem transport overview, 1-3 installing DSNlink on, 2-12 performing the installation to 2-18 on a DAN - Modem Transport DSNlink Communications Node , 2-12 to 2-18 (DCN) - Modem Transport on a DCN - Modem Transport installing DSNlink on, 2-2 to , 2-2 to 2-11 2-11 on a DCN - X.25 or DECnet DSNlink Communications Node Transport, 3-2 to 3-9 (DCN) - X.25 or DECnet on VMSclusters, 4-1 Transport overview, 2-1, 3-1 installing DSNlink on, 3-2 to preinstallation checklist, 3-9 1-21 setting system parameters I______________________________ other parameters, 1-10 to Installing and registering 1-11 DSNlink overview, 1-7 DECnet transport overview, SCSNODE, 1-8 to 1-9 1-6 SCSSYSTEMID, 1-9 Index-1 Installing and registering See Installing and DSNlink registering DSNlink setting system parameters (cont'd) S______________________________ user account parameters, SCSNODE, setting for DSNlink 1-11 to 1-12 installation, 1-8 to 1-9 X.25 transport overview, 1-4 SCSSYSTEMID, setting for Installing DSNlink DSNlink installation, 1-9 PAK not required, 1-1 site-specific startup file, 4-2 M______________________________ Modems U______________________________ User accounts setting for DSNlink installation, 1-11 to 1-12 V______________________________ VMSclusters installing DSNlink on, 4-1 Index-2