SSU_for_OpenVMS_Systems_______________________ Installation and User's Guide Order Number: AA-JB84D-TE This document describes how to install and use the SSU for OpenVMS Systems on OpenVMS VAX and OpenVMS AXP systems. Revision/Update Information: This manual replaces Session Support Utility Installation and User's Guide (Order Number AA- JB84C-TE). Operating System and Version: OpenVMS VAX Versions 5.5 and 6.0 OpenVMS AXP Versions 1.0 to 1.5 Software Version: SSU Version 2.0 for OpenVMS Systems Digital Equipment Corporation Maynard, Massachusetts __________________________________________________________ November 1993 Digital Equipment Corporation makes no representations that the use of its products in the manner described in this publication will not infringe on existing or future patent rights, nor do the descriptions contained in this publication imply the granting of licenses to make, use, or sell equipment or software in accordance with the description. Possession, use, or copying of the software described in this publication is authorized only pursuant to a valid written license from Digital or an authorized sublicensor. © Digital Equipment Corporation 1993. All Rights Reserved. Printed in U.S.A. The postpaid Reader's Comments forms at the end of this document request your critical evaluation to assist in preparing future documentation. The following are trademarks of Digital Equipment Corporation: Alpha AXP, AXP, OpenVMS, SSU, VAX, VAXcluster, VMScluster, VT330, VT340, VT420, and the DIGITAL logo. This document is available on CD-ROM. S2411 This document was prepared using VAX DOCUMENT Version 2.1. ________________________________________________________________ Contents About This Guide......................................... v 1 Preparing for Installation What You Need to Know.............................. 1-1 Do This Before You Install......................... 1-2 Inspect the Distribution Kit....................... 1-2 Log In to Privileged Account....................... 1-3 Access Online Release Notes........................ 1-3 Determine Disk Space............................... 1-3 Register Your License.............................. 1-4 Back Up Your System Disk........................... 1-4 2 Installing the Software Responding to VMSINSTAL Prompts.................... 2-1 Aborting the VMSINSTAL Procedure................... 2-1 Installation Procedure............................. 2-2 3 After Installing the Software Running the Installation Verification Procedure Separately......................................... 3-1 After Installation in VMScluster Environments...... 3-1 Deleting Files and Commands from Previous Versions........................................... 3-2 iii 4 Using SSU Software Setting Up the Environment......................... 4-1 Getting Online Help................................ 4-3 How to Use SSU Sessions............................ 4-3 5 Troubleshooting Recovering from Error Conditions................... 5-1 Attempting Use in Nonsession Environments.......... 5-1 Starting a New Session with a Session Running...... 5-2 Opening a Second Session Without a Session Running............................................ 5-2 Recovering Sessions After Terminal Power Loss...... 5-3 Reporting Problems and Getting Help................ 5-3 A Sample Installations B Files Installed on Your System Index Examples A-1 Sample Installation on an OpenVMS VAX System................................... A-1 A-2 Sample Installation on an OpenVMS AXP System................................... A-4 Tables 1-1 SSU Installation Requirements............ 1-1 1-2 Disk Space Requirements.................. 1-3 4-1 How to Set Up the VT420 Video Terminal to Use SSU Sessions......................... 4-2 4-2 Steps to Use SSU Sessions................ 4-4 iv ________________________________________________________________ About This Guide This guide provides step-by-step instructions for installing and using the SSU[TM] for OpenVMS Systems software on OpenVMS[TM] VAX[TM] and OpenVMS AXP[TM] systems. SSU software lets you log in to and maintain multiple independent sessions on a single terminal line on an OpenVMS system. SSU software is for use with Digital's VT330[TM], VT340[TM], and VT420[TM] video terminals. SSU software communicates with the single-line, multiple- session firmware in the terminal. For more information on your video terminal, see the terminal's documentation. Audience This guide is for system managers, operators with system privileges, and users of the SSU software. You should have a working knowledge of the OpenVMS operating system. System managers should read this manual before beginning installation. Structure This guide has the following sections: __________________________________________________________ Chapter_____Decribes______________________________________ Chapter 1 How to prepare for installing the SSU software on an OpenVMS system. Chapter 2 How to install the SSU software on an OpenVMS system. v __________________________________________________________ Chapter_____Decribes______________________________________ Chapter 3 Procedures you perform after installing the software. Chapter 4 How to set up your environment and use the SSU software. Chapter 5 Possible problems encountered when using the SSU software and recovery procedures. Appendix A Sample installations of the SSU software on OpenVMS systems. Appendix B Files added to your system by the installation ____________of_the_SSU_software.__________________________ Associated Documents The following documents may be useful during installation: o OpenVMS Developer's Guide to VMSINSTAL o OpenVMS License Management Utility Manual o OpenVMS System Manager's Manual o OpenVMS System Manager's Utilities Reference Manual o OpenVMS Upgrade and Installation Manual o Installing and Using the VT330/VT340 Video Terminal o Installing and Using the VT420 Video Terminal Conventions The following conventions are used in this document: __________________________________________________________ Convention_______Meaning__________________________________ UPPERCASE Uppercase characters indicate DCL commands, qualifiers, and parameters. italics Italic characters in command formats indicate that you are to substitute a word or value of your choice. vi __________________________________________________________ Convention_______Meaning__________________________________ bold For online display, bold type is used in examples and command formats to show the characters that you should enter. red In the printed book, red ink is used in examples to show the commands you should enter. setup settings This type in text indicates terminal _________________setup_feature_and_field_settings.________ vii 1 ________________________________________________________________ Preparing for Installation This chapter describes what you need to know and what you need to do before installing the SSU software on an OpenVMS system. Chapter 2 describes the installation procedure. What You Need to Know Table 1-1 provides information that you need to know before you install the SSU software. Table_1-1_SSU_Installation_Requirements___________________ For_._._._____SSU_requires_._._.__________________________ Software o OpenVMS VAX Operating System, Version 5.5 or 6.0 or OpenVMS AXP Operating System, Versions 1.0 to 1.5 o OpenVMS tailoring classes: - OpenVMS Required Saveset - Secure User's Environment Hardware o Any VAX or Alpha AXP[TM] processor Refer to the SSU Software Product Description (SPD)/System Support Addendum (SSA) for a complete list of supported hardware. (continued on next page) Preparing for Installation 1-1 Table_1-1_(Cont.)_SSU_Installation_Requirements___________ For_._._._____SSU_requires_._._.__________________________ Privileges System manager privileges License Product Authorization Key (PAK) License Free disk Minimum of 500 blocks space Refer to Determine Disk Space for in- formation on disk space during and after installation. Time About 15 minutes, depending on your type of media and your system configuration Documentation This manual and the OpenVMS Upgrade and Installation Manual VMScluster[TM]Installing SSU on only one node in a installation__VMScluster_system_with_a_common_disk._______ Do This Before You Install Do the following before installing the SSU software kit. Inspect the Distribution Kit For OpenVMS AXP systems, o SSU software is distributed on a layered product compact disc (CD-ROM). o SSU documentation is provided on the software layered products documentation CD-ROM. (Hardcopy documentation can be ordered separately.) For OpenVMS VAX systems, the SSU for OpenVMS Systems Distribution Kit contains: o Bill of materials (BOM) and indented bills report (BIL) o Distribution media containing the software o Documentation: - Software Product Description (SPD) and the System Support Addendum (SSA) - SSU for OpenVMS Systems Cover Letter 1-2 Preparing for Installation - SSU for OpenVMS Systems Installation and User's Guide - Software Performance Report (SPR) The distribution media contains the SSU software kit, which consists of the save set SSUnnn.A, where nnn represents the version number of the software. For example, the number 020 stands for Version 2.0. See Appendix B for files added to your system by the installation. This kit conforms to the standards specified in the OpenVMS Developer's Guide to VMSINSTAL. Log In to Privileged Account Log in to the system manager account, SYSTEM. This account provides the privileges necessary to register your Product Authorization Key (PAK) and install the SSU software. Access Online Release Notes The SSU product provides online release notes. You should review the release notes because they describe new features and differences among multiple versions of SSU, as well as changes in the installation procedure. For information on how to access the release notes, see Chapter 2. Determine Disk Space SSU requirements for free disk storage space are different during installation and after installation. Table 1-2 summarizes the storage requirements. Table_1-2_Disk_Space_Requirements_________________________ Blocks During Blocks After Installation_____Installation_____________________________ 500______________250______________________________________ To determine the number of free disk blocks on the current system disk, enter the following command at the DCL prompt: Preparing for Installation 1-3 $ SHOW DEVICE SYS$SYSDEVICE If you need to create free disk space, refer to the OpenVMS Upgrade and Installation Manual. Register Your License The SSU product supports the License Management Facility (LMF) provided by OpenVMS systems, and requires that you register a Product Authorization Key (PAK) before installing and using the product. The License PAK is shipped with the kit if you ordered a license and media together; otherwise, it is shipped separately to a location specified by your license order. Use the LMF utility to register and load the information from your License PAK in your system's license database. To register the license PAK, first log in to the system manager account, SYSTEM, then enter: $ @SYS$UPDATE:VMSLICENSE.COM ________________________Note ________________________ Add information carefully. The utility may return a checksum error message if you omit or incorrectly enter any license data. Check characters typed on each line, not just the checksum string. _____________________________________________________ For complete information on using the LMF utility, see the OpenVMS License Management Utility Manual. Back Up Your System Disk At the beginning of the installation, the installation utility asks if you have backed up your system disk. Digital recommends that you do a system disk backup before installing any software. Use the backup procedures that are established at your site. For details on performing a system disk backup, see the section on the Backup Utility in the OpenVMS System Management documentation subkit. 1-4 Preparing for Installation 2 ________________________________________________________________ Installing the Software This chapter describes how to install the SSU software on an OpenVMS system using the VMSINSTAL installation procedure. (Refer to the OpenVMS Upgrade and Installation Manual for more information on the VMSINSTAL procedure.) After you install SSU software successfully, inform system users who have VT330, VT340, and VT420 terminals that it is available. For logs of sample installations, see Appendix A. Responding to VMSINSTAL Prompts The VMSINSTAL procedure asks a series of questions to which you must provide answers. Default responses appear in square brackets ([]) at the end of some questions and prompts. Press the Return key to accept a default response. Otherwise, enter YES (Y), NO (N), or a question mark (?) for help. Aborting the VMSINSTAL Procedure To abort the installation procedure, press Ctrl/Y. The installation procedure deletes all files it has created up to that point and exits. If you want to retry the installation procedure after you press Ctrl/Y, you must invoke VMSINSTAL again, as shown in the section titled Installation Procedure. Installing the Software 2-1 Installation Procedure Before you start the installation, read Chapter 1 and this section about the installation procedure. To install the SSU software on an OpenVMS system, follow these steps. Step 1. Log in to the system manager account. The system manager account has the necessary privileges to run VMSINSTAL. 2-2 Installing the Software Step 2. Invoke VMSINSTAL. To invoke the VMSINSTAL procedure, enter: $ @SYS$UPDATE:VMSINSTAL SSUnnn device-id OPTIONS option_list You can supply the following information in the command line: SSUnnn Is the save-set name of the product you are installing. This name contains the product's utility name, version number, and update number. device- Identifies the device where the distribution id volumes are mounted. OPTIONS Must be included if you specify any options for the installation. option_ Is a list of installation options. For example, list including N in the option_list, allows you to select a release notes option during the installation procedure. For example, to install Version 2.0 of the SSU software with the release notes option: o On an OpenVMS VAX system on device MUA0:, enter: $ @SYS$UPDATE:VMSINSTAL SSU020 MUA0: OPTIONS N o On an OpenVMS AXP system on device DKA200:[000000], enter: $ @SYS$UPDATE:VMSINSTAL SSU020 DKA200:[000000] OPTIONS N SSU020 Indicates SSU Version 2.0. The 020 corresponds to 2.0. MUA0: Indicates the tape drive (device) for an OpenVMS VAX installation. Enter the name of the actual device you plan to use. DKA200:[0000Indicates the disc drive (device) for an OpenVMS AXP installation. Enter the name of the actual device you plan to use. Installing the Software 2-3 OPTIONS N Generates a copy of the release notes. You must specify OPTIONS N to print the release notes, display them, or both. The release notes are always copied to SYS$HELP. The VMSINSTAL procedure responds with the following messages. o For OpenVMS VAX systems: VAX/VMS Software Product Installation Procedure V5.5-2 It is 1-OCT-1993 at 14:07 Enter a question mark (?) at any time for help. o For OpenVMS AXP systems: OpenVMS Alpha Software Product Installation Procedure V1.5 It is 1-OCT-1993 at 14:07 Enter a question mark (?) at any time for help. Step 3. Confirm system backup. VMSINSTAL then asks if you are satisfied with your system backup. * Are you satisfied with the backup of your system disk [YES]? If you are satisfied with your backup, press the Return key. Otherwise, enter NO and press the Return key to end the installation. After you back up your system disk, you can restart the installation. Step 4. Mount the media. o For OpenVMS VAX systems: You are asked to mount the first volume. Mount the distribution volume of the utility on the device you entered when you invoked the VMSINSTAL procedure, for example, MUA0: Enter YES and press the Return key when ready. Please mount the first volume of the set on MUA0: * Are you ready? YES 2-4 Installing the Software VMSINSTAL displays a message that the media is mounted on the specified device (here, MUA0:). %MOUNT-I-MOUNTED, SSU mounted on _MUA0: o For OpenVMS AXP systems: If you are installing from CD-ROM, you are not asked to mount the media. o For all OpenVMS systems: If you did not indicate the device where the distribu- tion volumes are mounted when you invoked the VMSINSTAL procedure, you are asked: * Where will the distribution volumes be mounted: Enter the name of the device where you loaded the media that contains the SSU software. After the questions on mounting the media, the installa- tion of the software begins. The following products will be processed: SSU V2.0 Beginning installation of SSU V2.0 at 14:08 %VMSINSTAL-I-RESTORE, Restoring product save set A... The procedure checks whether there is enough disk space to install the SSU software, then ensures that you are running the correct version of the OpenVMS VAX or AXP operating system. If either test fails, the installation procedure issues an error message and exits. Otherwise, the procedure processes the files on the distribution media. Step 5. Select a release notes option. If you specified OPTIONS N when you started the installa- tion, you are presented with release notes options. Release notes included with this kit are always copied to SYS$HELP. Release Notes Options: Installing the Software 2-5 1. Display release notes 2. Print release notes 3. Both 1 and 2 4. None of the above * Select option [3]: 3 Digital recommends that you read the release notes before installing the SSU software. If you enter 1 or 3, VMSINSTAL displays the release notes at your terminal. If you enter 2 or 3, VMSINSTAL prompts you for a print queue for printing the release notes, as follows: * Queue name [SYS$PRINT]: Job SSU020 (queue SYS$PRINT, entry 1745) started on LPA0 After you have answered the questions regarding the release notes, this message is displayed: * Do you want to continue the installation [NO]? Enter YES or NO as appropriate. If you enter YES and press the Return key, the procedure continues with this message: (%VMSINSTAL-I-RELMOVED, The product's release notes have been successfully moved to SYS$HELP 2-6 Installing the Software Step 6. Respond to license registration queries. The installation procedure displays license information about your product and asks if have registered and loaded your License PAK. (Your License PAK lists the release date DD-MMM-YYYY.) Product: SSU Producer: DEC Version: 2.0 Release Date: DD-MMM-YYYY *Does this product have an authorization key registered and loaded? If you answer YES and you have registered a License PAK for the SSU product, the installation and verification procedures run to completion. If you answer NO, VMSINSTAL displays a message that tells you to register your License PAK and exits. Register and load your License PAK (see the section Register Your License) and restart the installation. Step 7. Specify whether to purge old files. The procedure asks if you want to purge files: During this installation, new files will be provided to replace existing versions. You may purge these older versions to save disk space, or keep them if you feel they may be of use. Purging is recommended. * Do you want to purge files replaced by this installation [YES]? If you press the Return key, the procedure deletes older versions of files provided by this kit, replacing them with new files. If you enter NO and press the Return key, the old files remain. In either case, the help library is always updated and purged. Step 8. Specify whether to run the IVP during installa- tion. The procedure asks if you want to run the Installation Verification Procedure (IVP): Most products provide an Installation Verification Procedure (IVP) which verifies the completeness and accuracy of the installation. You may wish to run the IVP immediately after installation. * Do you want to run the IVP after the installation [YES]? Installing the Software 2-7 Digital recommends that you run the IVP after the installation. 2-8 Installing the Software Step 9. Read installation progress messages. VMSINSTAL displays the following message as it copies files to their destination directories: %VMSINSTAL-I-MOVEFILES, Files will now be moved to their target directories ... Step 10. Observe IVP messages. If you answered YES in step 8, the Installation Verification Procedure (IVP) runs. ******************************************************************************* Beginning Installation Verification Procedure for SSU V2.0 SSU V2.0 successfully installed Installation Verification Procedure SSU V2.0 completed ******************************************************************************** Step 11. Observe ending of the installation. After installation is complete, these messages appear: Installation of SSU V2.0 complete at 14:14. VMSINSTAL procedure done at 14:14 $ These messages indicate the successful installation and verification (if chosen) of the the SSU product. If VMSINSTAL reports a failure, review the installation prerequisites. Installing the Software 2-9 3 ________________________________________________________________ After Installing the Software This chapter contains information on procedures that you perform after installing the SSU software. Topics include: o Running the Installation Verification Procedure (IVP) separately o VMScluster considerations o Deleting files from previous versions Running the Installation Verification Procedure Separately You usually run the IVP during the installation process (see Chapter 2). You can also run the IVP separately to check the integrity of installed files when system problems have occurred. To run the IVP separately, enter the following command: $ @SYS$TEST:SSU$IVP The IVP runs and displays output like the following: ******************************************************************************* Beginning Installation Verification Procedure for SSU V2.0 SSU V2.0 successfully installed Installation Verification Procedure SSU V2.0 completed ******************************************************************************** $ After Installation in VMScluster Environments After you install the SSU software on the common system disk, SSU sessions are available for anyone using a multisession terminal in the VMScluster system. After Installing the Software 3-1 Deleting Files and Commands from Previous Versions ________________________Note ________________________ Read this section if you are upgrading from a previous version of SSU software. If you are installing the software for the first time this section does not apply to you. _____________________________________________________ Previous versions of the SSU software required a startup procedure; SSU Version 2.0 software does not. Before using the Version 2.0 software, edit the system startup file (SYSTARTUP_V5.COM) and remove the following command line: $ @SYS$MANAGER:SSU$STARTUP.COM Some files from previous versions of the software are not deleted even if you answered "YES" to the purge question during the installation. You may want to delete these files manually. o If you are upgrading from SSU Version 1.3 software, you can delete: - SYS$MANAGER:SSU$STARTUP.COM - SYS$COMMON:[SYSEXE]TDDRIVER.EXE These files are not required by Version 2.0 of the SSU software. o If you are upgrading from a version of SSU software before Version 1.3, you can delete: - SYS$MANAGER:SSU$STARTUP.COM - SYS$COMMON:[SYSEXE]TDDRIVER_FOR_VMSV*.EXE - SYS$COMMON:[SYSEXE]SSU_FOR_VMSV*.EXE These files are not required by Version 2.0 of the SSU software. SSU_FOR_VMSV*.EXE is replaced by SSU.EXE. 3-2 After Installing the Software 4 ________________________________________________________________ Using SSU Software You can use the SSU software on OpenVMS systems on single- line, multiple-session terminals, such as the VT330, VT340, or VT420 video terminals. This chapter explains how to set up the environment for the SSU software and how to use the software to enable multiple sessions on a terminal line. Topics include: o Setting up your environment o Getting online help o Using multiple sessions See Chapter 5 for problems you may encounter and recovery information. Setting Up the Environment SSU software provides multiple sessions in environments that support the Terminal Device Session Management Protocol (TDSMP) and use XON/XOFF flow controls. o TDSMP allows the terminal to responds to session- switching and flow control commands. o XON/XOFF flow controls allow the terminal to tell the host and the host to tell the terminal when they can and cannot accept more data. For information on TDSMP support and on enabling XON/XOFF flow controls in the terminal, refer to the documentation for your video terminal or terminal emulator. Using SSU Software 4-1 In addition, your terminal must be set up for multiple sessions to use the SSU software. Setup requirements and procedures vary from one model of video terminal to another. To set up the VT420 video terminal for multiple sessions, you use two features in the Global Set-Up screen: Terminal comm ports Comm port selection ________________________Note ________________________ Refer to the user guide for your video terminal for specific information about setting up your environment to use SSU sessions. _____________________________________________________ Table 4-1 explains how you can check that the VT420 video terminal is set up for multiple sessions and how to change set-up features to support the SSU software. Table 4-1 How to Set Up the VT420 Video Terminal to Use __________SSU_Sessions____________________________________ Step___Action_____________________________________________ 1 Press the F3 (Set-Up) key. The terminal displays the Set-Up Directory screen with the cursor in the Global field. 2 Press the Enter key to display the Global Set-Up screen. 3 Check the setting of the second field on the second line. SSU sessions require the Sessions on Comm1 setting. If the setting is not correct: a. Use the arrow keys to move the cursor to the field. b. Press the Enter key until the Sessions on Comm1 setting is displayed. (continued on next page) 4-2 Using SSU Software Table 4-1 (Cont.) How to Set Up the VT420 Video Terminal __________________to_Use_SSU_Sessions_____________________ Step___Action_____________________________________________ 4 Check the setting of the first field on the third line. If this field does not contain a Comm port selection setting, this step does not apply to your terminal. Go to step 5. If this field contains a Comm port selection setting (like the Worldwide Model of the VT420 video terminal), the setting should match the connector you are using: Comm1=RS-232 setting for the 25-pin, RS-232 connector Comm1=DEC-423 setting for the 6-pin, DEC-423 connector If the setting is not correct, use the arrow keys to move the cursor to the field and press the Enter key until the correct setting is displayed. __5____Press_the_F3_key_to_leave_set-up.__________________ You are ready to start an SSU session. Refer to the Installing and Using the VT420 Video Terminal for more information about the VT420 video terminal environment. Getting Online Help For an explanation of the command you use to invoke the SSU software, options to modify session behavior, and examples, enter: $ HELP SSU How to Use SSU Sessions This section provides information on how to use the SSU software to manage multiple sessions on a single terminal line. Table 4-2 summarizes the steps that you use. Using SSU Software 4-3 Table_4-2_Steps_to_Use_SSU_Sessions_______________________ Step___Action_____________________________________________ 1 Log in to your system. 2 Invoke the SSU software. 3 Create additional sessions. 4 Move between sessions. __5____End_sessions.______________________________________ This section provides more detail about each step. 1. Log in to your system. This provides the host process or job in which you run SSU sessions. On OpenVMS systems, the login procedure most likely requires that you enter a username and password: Username: Sampson Password: $ Your password is not seen. 2. Invoke the SSU software. To invoke the SSU software, enter: $ MCR SSU SSU software: o Automatically logs you in to the first session. o Requires that you log in manually to all additional sessions. o Tells the terminal to disable multiple sessions after you close all sessions. o After you close all sessions, or after you disable sessions from terminal setup, logs out from the initial host process from which you invoked the SSU software. 4-4 Using SSU Software ________________________Note ________________________ The command format described in this manual assumes that the system manager installed the SSU software in a directory pointed to by the SYS$SYSTEM logical name. If the SSU software is not in such a directory, you need to include the device:[directory] name when you start an SSU session: $ MCR device:[directory]SSU _____________________________________________________ After an SSU initiated session is open: o Anything that you type is sent to the host system, except for special keys to which the terminal responds (such as the setup key or the switch session key). o Data from the the host system is displayed on the screen if the session is visible. 3. Create additional sessions. Press the switch session key on your terminal. On the VT420 video terminal, the switch session key is F4. The terminal starts a new session. On the VT420, the following is displayed in the status line at the bottom of the terminal: Service Name = ______________________________________ After you enter an optional name and press the Return key or press the Return key, the VT420 terminal reponds with Session opened and tells the SSU software to open a session. Press the Return key and log in to the session as you normally do. On OpenVMS systems, the login procedure most likely requires that you enter a username and password: Username: Sampson Password: $ Using SSU Software 4-5 Your password is not seen. 4-6 Using SSU Software 4. Move between sessions. Press the switch session key on your terminal. On the VT420 terminal, F4 is the switch session key. VT420 terminals display the number of the session at the bottom left of the screen. On the VT420 terminal, pressing the Ctrl key and the F4 key together divides the screen into two windows. You can then view two SSU sessions on the same screen. Pressing Ctrl/F4 lets you toggle between a split screen and a full screen. 5. End sessions. Log out from each SSU session the way you normally log out from sessions. The host system displays a message like: $ LOGOUT USERNAME logged out at 3-SEP-1993 15:48:15.35 If another session is active, the SSU software displays a message that indicates this, and tells you to press the Session key. [ *** Other SSU session(s) active -- press SESSION key to resume *** ] After you log out from all sessions, sessions are disabled and the SSU software exits and logs out your initial host process. SSU Version 2.0 finished. Thank you. Using SSU Software 4-7 5 ________________________________________________________________ Troubleshooting This chapter describes problems that you may encounter and suggests recovery procedures. Topics include: o Recovering from error conditions o Reporting problems and getting help Recovering from Error Conditions This sections lists conditions that can cause errors when you run SSU sessions. Attempting Use in Nonsession Environments SSU software requires an environment that supports multiple sessions. Therefore, you can expect an error if you use SSU sessions in the following ways: o On a nonsession terminal. Check the documentation for your terminal. If your terminal does not support sessions, you cannot use SSU software. o As a batch job. SSU sessions require terminal lines. Batch jobs do not support multiple sessions. o On a terminal that supports sessions, but sessions have not been enabled. Enter the Set-Up Directory and enable sessions. See the section Setting Up the Environment and the documentation for your video terminal. Troubleshooting 5-1 If you attempt to run SSU sessions in these environments, SSU software displays the following characters on the screen: !@AJ!@AJ!@AJ These characters represent commands sent to the terminal to start multiple sessions. After a few seconds, the SSU software stops sending requests and the system prompt returns. Make sure that your terminal is set-up to use multiple sessions and start the SSU software again. Starting a New Session with a Session Running If you attempt to start an SSU session on a terminal where SSU sessions are already running, the terminal displays messages like: $ MCR SSU !@AJ!@AJ!@AJ!@AJ SSU finished. Thank you. $ This creates no problems for the SSU sessions that are running. Resume using your current sessions. Opening a Second Session Without a Session Running If you attempt to open a second session (press the F4 (Session) key) before starting an SSU session, the terminal displays messages like: $ !@AB!@AB !@AB NODE::USERNAME 11:31:51 (DCL) CPU=00:00:02.98 PF=766 IO=210 MEM=543 $ !@AB!@AB!@AB If your terminal is connected to the host through a LAT line, the following LAT messages may be displayed: Local -nnn- No other session(s) active Local -nnn- NODE session 1 resumed In addition, the following message is displayed in the status line at the bottom of the VT420 screen: Sessions not enabled - No Session Management response from host 5-2 Troubleshooting Press the Return key to return the system prompt. To start a session, see Chapter 4. Recovering Sessions After Terminal Power Loss On occasion, your terminal loses power while you are using multiple sessions with the SSU software. When power is returned, you can do the following to recover your SSU sessions: o Press the F3 key to enter the Set-Up Directory. o Use the arrow keys to move the cursor to the Enable Sessions field. o Press the F3 key again to leave setup. Your SSU sessions are returned, unless the system also lost power. Reporting Problems and Getting Help If you followed the suggestions in the troubleshooting section and you still have a problem using SSU sessions, report it to Digital. Depending on the nature of the problem and the type of support you have, you can take one of the following actions: o Call Digital if your software contract or warranty agreement entitles you to telephone support. o Determine whether the problem is a result of defective media. If so, contact your Digital service represen- tative for a replacement copy. If the requirements for installation have been met, and the media is not defective, then submit a Software Performance Report (SPR). o Fill out and submit a Reader's Comments form if the problem has to do with the documentation. There are Reader's Comments forms at the back of each manual. Use the form from the manual in which you found the error. Include the section and page number of the problem. Troubleshooting 5-3 Review the SSU for OpenVMS Systems Software Product Description (SPD) and Warranty Addendum for an explanation of the warranty. If you encounter a problem during the warranty period, report the problem as described or follow alternate instructions provided by Digital for reporting SPD nonconformance problems. 5-4 Troubleshooting A ________________________________________________________________ Sample Installations Example A-1 is a sample installation of the SSU software on an OpenVMS VAX system with selection of the release notes option. Example A-2 is a sample installation of the SSU software on an OpenVMS AXP system with selection of the release notes option. Example A-1 Sample Installation on an OpenVMS VAX System $ @SYS$UPDATE:VMSINSTAL SSU020 MUA0: OPTIONS N VAX/VMS Software Product Installation Procedure V5.5-2 It is 27-SEP-1993 at 16:06. 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 MUA0: * Are you ready?) Y %MOUNT-I-MOUNTED, SSU mounted on _MUA0: The following products will be processed: SSU V2.0 Beginning installation of SSU V2.0 at 16:06 %VMSINSTAL-I-RESTORE, Restoring product save set A... (continued on next page) Sample Installations A-1 Example A-1 (Cont.) Sample Installation on an OpenVMS VAX System Release notes included with this kit are always copied to SYS$HELP. Release Notes Options: 1. Display release notes 2. Print release notes 3. Both 1 and 2 4. None of the above * Select option [3]: 2 * Queue name [SYS$PRINT]: Job SSU020 (queue SYS$PRINT, entry 107) started on LPA0 * Do you want to continue the installation [NO]? Y %VMSINSTAL-I-RELMOVED, The product's release notes have been successfully moved to SYS$HELP During this installation, new files will be provided to replace existing versions. You may purge these older versions to save disk space, or keep them if you feel they may be of use. Purging is recommended. * Do you want to purge files replaced by this installation [YES]? Most products provide an Installation Verification Procedure (IVP) which verifies the completeness and accuracy of the installation. You may wish to run the IVP immediately after installation. * Do you want to run the IVP after the installation [YES]? Product: SSU Producer: DEC Version: 2.0 Release Date: * Does this product have an authorization key registered and loaded? YES (continued on next page) A-2 Sample Installations Example A-1 (Cont.) Sample Installation on an OpenVMS VAX System %VMSINSTAL-I-MOVEFILES, Files will now be moved to their target directories ... ******************************************************************************** Beginning Installation Verification Procedure for SSU V2.0 SSU V2.0 successfully installed Installation Verification Procedure SSU V2.0 completed ******************************************************************************** Installation of SSU V2.0 completed at 16:07 VMSINSTAL procedure done at 16:07 $ Sample Installations A-3 Example A-2 Sample Installation on an OpenVMS AXP System $ @SYS$UPDATE:VMSINSTAL SSU020 DKA200:[000000] OPTIONS N OpenVMS AXP Software Product Installation Procedure V1.5 It is 27-SEP-1993 at 16:27. Enter a question mark (?) at any time for help. * Are you satisfied with the backup of your system disk [YES]? The following products will be processed: SSU V2.0 Beginning installation of SSU V2.0 at 16:27 %VMSINSTAL-I-RESTORE, Restoring product save set A... Release notes included with this kit are always copied to SYS$HELP. Release Notes Options: 1. Display release notes 2. Print release notes 3. Both 1 and 2 4. None of the above * Select option [3]:) 2 * Queue name [SYS$PRINT]: Job SSU020 (queue SYS$PRINT, entry 107) started on LPA0 * Do you want to continue the installation [NO]? Y %VMSINSTAL-I-RELMOVED, The product's release notes have been successfully moved to SYS$HELP During this installation, new files will be provided to replace existing versions. You may purge these older versions to save disk space, or keep them if you feel they may be of use. Purging is recommended. * Do you want to purge files replaced by this installation [YES]? Most products provide an Installation Verification Procedure (IVP) which verifies the completeness and accuracy of the installation. You may wish to run the IVP immediately after installation. * Do you want to run the IVP after the installation [YES]? (continued on next page) A-4 Sample Installations Example A-2 (Cont.) Sample Installation on an OpenVMS AXP System Product: SSU Producer: DEC Version: 2.0 Release Date: * Does this product have an authorization key registered and loaded? Y %VMSINSTAL-I-MOVEFILES, Files will now be moved to their target directories... ******************************************************************************** Beginning Installation Verification Procedure for SSU V2.0 SSU V2.0 successfully installed Installation Verification Procedure SSU V2.0 completed ******************************************************************************** Installation of SSU V2.0 completed at 16:27 Adding history entry in VMI$ROOT:[SYSUPD]VMSINSTAL.HISTORY Creating installation data file: VMI$ROOT:[SYSUPD]SSU020.VMI_DATA VMSINSTAL procedure done at 16:28 $ Sample Installations A-5 B ________________________________________________________________ Files Installed on Your System The SSU software installation procedure installs the following files on your system: __________________________________________________________ File_Name________Directory___Description__________________ SSU.EXE SYS$SYSTEM: Executable file SSU.HLP SYS$HELP: Help file SSU020.RELEASE_ SYS$HELP: Release notes NOTES SSU$IVP.COM SYS$TEST: Installation Verification _____________________________Procedure_(IVP)______________ Files Installed on Your System B-1 ________________________________________________________________ Index A__________________________ G__________________________ Additional sessions, Global Set-Up opening, 4-5 VT420 terminal comm port selection, C__________________________ 4-2 Command to start SSU terminal comm ports, software, 4-4 4-2 Creating another session, 4-5 H__________________________ Help D__________________________ on VMSINSTAL questions, Diagnosing problems, 5-1 2-1 Disabling sessions, 4-7 online, command for, 4-3 Disk space requirements, 1-2 I__________________________ Distribution kit Installation OpenVMS AXP systems, 1-2 aborting, 2-1 OpenVMS VAX systems, 1-2 disk space requirements, 1-2 E__________________________ files added during, B-1 Enabling sessions, 4-4 hardware requirements, Error conditions, 5-1 1-1 Exiting sessions, 4-7 help for, 2-1 on a VMScluster system, F__________________________ 1-2 Files OpenVMS tailoring classes added during installation for, 1-1 , B-1 preparing for, 1-1 privileges for, 1-1 Index-1 Installation (cont'd) Product Authorization Key software requirements, (PAK), 1-2, 1-4 1-1 SSU procedure, 2-2 R__________________________ system requirements, 1-1 Recovery time required for, 1-2 from error conditions, Installation Verification 5-1 Procedure (IVP) from terminal power loss, during the installation, 5-3 2-7 Release notes running separately, 3-1 accessing, 1-3 generating, 2-4 L__________________________ Reporting problems, 5-3 License Management Facility (LMF), 1-4 S__________________________ Logging out of sessions, Sample installation 4-7 OpenVMS AXP systems, A-4 OpenVMS VAX systems, A-1 M__________________________ Sessions Moving betweeen sessions, disabling, 4-7 4-7 enabling, 4-4 exiting, 4-7 O moving between, 4-7 ___________________________ opening another, 4-5 Online help, 4-3 starting, 4-4 Opening another session, switching, 4-7 4-5 Setup for SSU software, OpenVMS tailoring classes, 4-1 1-1 Split screen, on VT420 terminal, 4-7 P__________________________ Starting an SSU session, Postinstallation 4-4 deleting files from Switching sessions, 4-7 previous versions, System requirements, 1-1 3-2 T removing SSU startup ___________________________ command file, 3-2 Terminal Device Session running IVP separately, Management Protocol 3-1 (TDSMP), 4-1 Privileges, 1-1 Troubleshooting, 5-1 Problems, recovery, 5-1 Index-2 responding to questions, U__________________________ 2-1 Using SSU sessions, 4-3 VT420 terminal steps to, 4-4 multiple sessions on, 4-2 ___________________________ W__________________________ VMScluster system Windows, creating two on installing SSU on, 1-2 VT420 screen, 4-7 using SSU software, 3-1 VMSINSTAL procedure X__________________________ invoking, 2-2 XON/XOFF flow controls, 4-1 Index-3