DEC CIT Applications Interface for VMS Installation Order Number: AA-KX59D-TE This document contains instructions for installing DEC Computer Integrated Telephony (CIT) Applications Interface Software for VMS on VAX/VMS systems. It also explains how to read the online release notes before or after installing the product. Revision/Update Information: This manual supersedes the VAX CIT Applications Interface Software Installation Guide Version 2.0 (Order Number AA-KX59C-TE). Operating System and Version: VAX/VMS Version 5.0 or later. Software Version: DEC CIT Applications Interface for VMS Version 2.1. digital equipment corporation maynard, massachusetts ii 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 ©1988, 1989, 1991 by Digital Equipment Corporation All Rights Reserved. Printed in the UK. __________ The READER'S COMMENTS form on the last page of this document requests the user's critical evaluation to assist in preparing future documentation. The following are trademarks of Digital Equipment Corporation: DDCMP Packetnet UNIBUS DEC PDP VAX DECnet Q-bus VAXcluster DECrouter Q22-bus VMS DECUS RSTS VT DECvoice RSX MASSBUS ULTRIX MicroVAX ULTRIX-32 DIGITAL This document was prepared using VAX DOCUMENT, Version 1.2 __________________________________________________________ 1 INTRODUCTION TO INSTALLING THE KIT The DEC CIT product set consists of two separately installable software products: o DEC CIT Applications Interface for VMS software, which is installed on client nodes in a DEC CIT network. o DEC CIT Server for VMS software (CITSR), which is installed on the server node of a DEC CIT network. Note that if you want to run applications on the server node, you have to install the DEC CIT Applications Interface for VMS software on the server node as well as installing the DEC CIT Server for VMS software. This manual describes how to install DEC CIT Applications Interface for VMS software. For instructions on installing DEC CIT Server for VMS software, see the DEC CIT Server for VMS Installation manual. This manual is intended for system managers who understand the general installation procedures on VAX/VMS systems. Keep this document with your distribution kit. You will need to refer to it again if you receive any maintenance updates, or if you need to reinstall DEC CIT Applications Interface for VMS software for any other reason. Release Notes This document does not contain release information; instead, release notes are provided online. You can read the release notes before you install DEC CIT Applications Interface for VMS software, and at any time after the product is installed. 1 To read the release notes, follow the installation procedure up to step 4. At that step, you can choose to display or to print the release notes, or both. You can then choose whether to continue with the installation procedure. For information on reporting problems with DEC CIT Applications Interface for VMS software, see Section 5.3. __________________________________________________________ 2 PREPARING TO INSTALL DEC CIT APPLICATIONS INTERFACE SOFTWARE The following sections describe the checks and actions required before you install the DEC CIT Applications Interface for VMS software. _____________________________ 2.1 Contents of the Installation Kit The Bill of Materials (BOM) specifies the number and contents of your media. Check the contents of your kit against the list in the Bill of Materials. If your kit is damaged, or if you find that parts of it are missing, call your Digital representative. Table 1 shows details of the media on which the DEC CIT Applications Interface for VMS software may be delivered. 2 ________________________________________________________________ Table 1 Media Details _______________________________________________________ Media______________Quantity__Label_____________________ TK50 cartridge 1 DEC CIT Appl Infc 1600 bpi magnetic 1 DEC CIT Appl Infc tape CDROM 1 VMS Consolidated Software ______________________________________Distribution______________ Note that the TK50 cartridge can be read from both a TK50 and a TK70 tape drive. _____________________________ 2.2 Hardware Requirements DEC CIT Applications Interface for VMS software must be installed on a VAX/VMS system that is connected to at least one DEC CIT server node through DECnet. _____________________________ 2.3 Software Requirements DEC CIT Applications Interface for VMS Version 2.1 requires VAX/VMS Version 5.0 or later. The VMS operating system comes with a variety of support options, or classes. Classes include such features as networking and RMS journaling. To use DEC CIT Applications Interface for VMS, your system should be running a version of VMS that includes the following classes: o VMS Required Saveset o Network Support 3 o Programming Support For a complete list of the required classes, see the Software Support Addendum (SSA), which comes with the Software Product Description (SPD) 29.92.xx. _____________________________ 2.4 Installation Procedure Requirements This section describes the preparations you need to make before installing the kit. _____________________________ 2.4.1 Basic Requirements The installation takes up to 30 minutes, depending on the type of media and the configuration of your system. For example, installation takes about 10 minutes from a TK50 cartridge on a MicroVAX II. To ensure the installation runs smoothly: o Back up the system disk before starting the installation procedure. o Check that sufficient disk space is available. DEC CIT Applications Interface for VMS software requires 1200 free blocks during the installation process, and 850 blocks after the installation. o Either install DEC CIT Applications Interface for VMS software from the system manager's account with your default device and directory set to SYS$UPDATE, or ensure that you can enable the following VMS privileges: CMKRNL EXQUOTA NETMBX SYSNAM SYSPRV TMPMBX 4 For more information on VMS privileges, see the Guide to Setting Up a VMS System. For a summary of VMS privileges, see the VMS DCL Concepts Manual. _____________________________ 2.4.2 Support of License Management Facility (LMF) The DEC CIT Applications Interface for VMS software supports the VMS License Management Facility (LMF) for installation on VMS V5.0 and later systems. If you need to register DEC CIT Applications Interface for VMS software through the LMF, the kit includes a Product Authorization Key (PAK) containing the information you need for registration. To find out whether a license is already registered on your system, enter the following: $ LICENSE LIST CIT Now press . If you do not have the PAK registered, the system displays only general LMF information. To register your PAK, use the SYS$UPDATE:VMSLICENSE.COM command procedure. For more information on this command procedure and the LMF, refer to VMS License Management Utility Reference Manual. The installation procedure for DEC CIT Applications Interface for VMS software asks if you have an authorization key registered and loaded. You can install the kit without authorization, but you will not be able to run the kit or the Installation Verification Procedure (IVP). 5 _____________________________ 2.4.3 Information Required During Installation The installation procedure creates a startup command procedure (SYS$STARTUP:CIT$STARTUP.COM) for the DEC CIT Applications Interface software. To create this file, the installation procedure prompts you for details of each CIT server node and each PBX and/or DECvoice module connected to a CIT server. For each CIT server, the installation procedure prompts you for: 1 The node name of the CIT server 2 The logical identifier for each PBX and/or each DECvoice module connected to the server The logical identifier is a name that identifies the PBX and communications device, or the DECvoice module, to the server software. Each logical identifier is defined by the system manager of the server node when the server software is installed or configured. You must specify the same logical identifier for each PBX and/or DECvoice module that the system manager of the server node has defined. Note that if a large number of DECvoice modules are installed on a CIT server, it may take less time to edit the startup file for the applications interface than to provide information during the installation procedure. By editing SYS$STARTUP:CIT$STARTUP.COM, you can specify details of the DECvoice modules in the startup file instead of supplying all the logical identifiers at the installation prompts. To define the DECvoice modules in this way, complete the following procedure: 1 Follow the installation procedure and specify the logical identifier for one DECvoice module. (If you 6 require support for PBX functions, supply all the information that is required for PBX support.) Do not select automatic startup. 2 When the installation is complete, edit SYS$STARTUP:CIT$STARTUP.COM to include the logical identifiers for the other DECvoice modules installed on the server. For example, if you specified the logical identifier CIT_VOXA during installation for a DECvoice module installed on the server node CITVAX, you must copy and edit the following line in SYS$STARTUP:CIT$STARTUP.COM: $ DEFINE/SYSTEM/EXECUTIVE CIT_VOXA CITVAX To define the DECvoice module VXB0, for example, you must add the following line to SYS$STARTUP:CIT$STARTUP.COM: $ DEFINE/SYSTEM/EXECUTIVE CIT_VOXB CITVAX 3 When you have included the logical identifiers for all the DECvoice modules installed on the server, start up the client software (see Section 4.1) and run the IVP (see Section 4.3). _____________________________ 2.4.4 Starting and Testing the Kit During the installation procedure, you are also asked whether you want to start up the CIT software automatically after installation. If you select automatic startup, the installation procedure runs the startup file SYS$STARTUP:CIT$STARTUP.COM, as soon as installation is complete. If you do not want to select automatic startup, you have to run the startup file sometime after the installation. See Section 4.1 for details on starting the CIT software. 7 If you choose automatic startup, the installation procedure also asks you whether you want to run the Installation Verification Procedure (IVP). This tests the installation by checking the DECnet connection to each CIT server node that you specify, and by communicating with each PBX and/or with each DECvoice module. To run the IVP: o There must be a DECnet link between the client and the server nodes. o The DEC CIT Server software must be installed and running. o The CIT server must be connected to a PBX and/or at least one DECvoice module. The system manager on the server should have demonstrated that the connection is working by running the IVP for the server software. If you do not want to run the IVP as part of the installation procedure, you can run a separate IVP after the installation. This procedure tests the link to each PBX and/or each DECvoice module that you specify. See Section 4.3. __________________________________________________________ 3 INSTALLING DEC CIT APPLICATIONS INTERFACE SOFTWARE The following sections describe the VMSINSTAL command procedure and give a step-by-step guide to the DEC CIT Applications Interface for VMS software installation procedure. VMSINSTAL.COM resides in SYS$UPDATE. 8 _____________________________ 3.1 Using VMSINSTAL The VMSINSTAL command line has the following format: $ @VMSINSTAL CIT source OPTIONS N CIT The release or maintenance update of DEC CIT Applications Interface for VMS software. source The name of the device from which you are installing the DEC CIT Applications Interface for VMS software. The device name is in the form ddcu: where dd is the device code, c is the controller, and u is the unit number. OPTIONS N Set the OPTIONS N parameter if you want VMSINSTAL to prompt you to display or print the release notes. If you enter only @VMSINSTAL as the command line, VMSINSTAL prompts you for the first two parameters, but it does not prompt for OPTIONS N. Digital recommends that you enter the command line, including the OPTIONS N parameter, so that you can read the release notes during installation. Even if you do not set the OPTIONS N parameter, the release notes are automatically copied to the file SYS$HELP:CIT021.RELEASE_NOTES. _____________________________ 3.2 Installation Procedure The rest of this section describes the installation procedure. You can get help by entering a question mark (?) in response to any of the questions asked during the installation procedure. 9 These installation instructions use MUA0: as an example of the source device from which you install the DEC CIT Applications Interface for VMS software. To cancel the installation procedure at any time, press . VMSINSTAL then deletes all files it has created up to that point and exits. If you want to retry the installation procedure after pressing , you must proceed from step 2. Step 1: Log in to the system manager's account and set your default device and directory to SYS$UPDATE. Username: SYSTEM Password: $ SET DEFAULT SYS$UPDATE Step 2: Invoke VMSINSTAL. $ @VMSINSTAL CIT MUA0: OPTIONS N VAX/VMS Software Product Installation Procedure V5.n-n It is dd-mmm-yyyy at hh:mm. Enter a question mark (?) at any time for help. %VMSINSTAL_W_DECNET, Your DECnet network is up and running. If you want to run the IVP, your DECnet network must be up and running. * Do you want to continue anyway [NO]? * Are you satisfied with the backup of your system disk [YES]? 10 Step 3: Insert the installation volume. Insert the tape into the drive. VMSINSTAL automatically mounts the volume for you. Please mount the first volume of the set on MUA0:. * Are you ready? %MOUNTED-I-MOUNTED, CIT mounted on CITVAX$MUA0: The following products will be processed: CIT V2.1 Beginning installation of CIT V2.1 at hh:mm %VMSINSTAL-I-RESTORE, Restoring product saveset A... Step 4: Select a release notes option. This step applies only if you specified OPTIONS N in step 2. Release Notes Options: 1. Display release notes 2. Print release notes 3. Both 1 and 2 4. Copy release notes to SYS$HELP 5. Do not display, print or copy release notes * Select option [2]: If you select option 1, VMSINSTAL displays the release notes immediately on your screen. You can terminate the display at any time by entering . If you select option 2, VMSINSTAL prompts you for a queue name. * Queue name [SYS$PRINT]: 11 You can enter a queue name, or send the file to the default output print device. If you select option 3, VMSINSTAL displays the release notes immediately on your screen and then prompts you for a queue name. If you select option 4, VMSINSTAL copies the release notes to SYS$HELP. VMSINSTAL then prompts you with the following: Do you want to continue the installation [NO]? %VMSINSTAL-I-RELMOVED, the product release notes have been successfully moved to SYS$HELP. Step 5: Verify licensing. CIT Software Installation Procedure. %VMSINSTAL-I-RESTORE, Restoring product saveset B ... Product: CIT Producer: DEC Version: 2.1 Release Date: 21-DEC-1990 Does this product have an authorization key registered and loaded? If you have not registered and loaded the PAK for this kit, the installation will continue but you will not be able to run the software or the IVP during or after the installation. See Section 2.4.2. Step 6: Select installation options. * Do you want to startup CIT automatically after installation? [YES]? 12 Select automatic startup if you want the installation procedure to start the CIT client software for you. * Do you want to run the IVP after installation [YES]? You are prompted to run the IVP only if you chose automatic startup. If you choose not to have the IVP run automatically, refer to Section 4.3 for instructions on how to run the IVP. CIT$STARTUP.COM will now be created for you. This procedure creates the CIT startup file, CIT$STARTUP.COM which brings up and configures your CIT client node. It requires the CIT server node name(s) and the logical identifier for each PBX connected to and/or each DECvoice module installed on the server node(s) Provide the values in response to the following questions. You are given the opportunity to re-enter mistyped values. * Enter the name of the CIT server node: server * Enter the logical identifier for the PBX or DECvoice module: logical_identifier CIT server node name : server CIT server logical identifier : logical_identifier * Is this information correct? [YES]? Specify the name of the CIT server node and the logical identifier for the PBX or DECvoice module to which the server is connected. You must specify the same logical identifier that the system manager of the CIT server node has defined for that PBX or module. The identifier and server node name are then included in the startup file SYS$STARTUP:CIT$STARTUP.COM. 13 If you specify a wrong server node name or logical identifier, the Installation Verification Procedure will fail. For example, if you specify a logical identifier for a PBX or DECvoice module that is not the same as the identifier defined by the system manager of the CIT server node, the IVP fails. To correct these names in the startup file, you must edit the file SYS$STARTUP:CIT$STARTUP.COM when installation is complete, or reinstall the DEC CIT Applications Interface for VMS software. See Section 4.2 for details of how to change CIT$STARTUP.COM. * Do you want to specify another logical identifier [YES]? If there is more than one PBX and/or DECvoice module connected to the same CIT server node, you are prompted for the server node name again and the logical identifier for that PBX and/or DECvoice module. See the example installation in Section 6. * Do you want to specify another CIT server [NO]? If you specify that there is another CIT server node, the procedure prompts you for the server node name and the logical identifier for each PBX and/or each DECvoice module connected to that server. Your CIT applications interface startup profile has been configured in CIT$STARTUP.COM. %VMSINSTAL-I-SYSDIR, This product creates system disk directory VMI$ROOT:[SYSTEST.CIT]. You have answered all the questions necessary for the installation to be completed. The installation will now run unattended %VMSINSTAL-I-MOVEFILES, Files will now be moved to their target directories... 14 The procedure copies the files before running the IVP. Table 2 in Section 4.6 shows all the files that are created by the installation procedure, and the directories to which they are moved. Step 7: Verify successful installation. If you chose to run the IVP (see step 6), VMSINSTAL now calls the IVP to verify that the DEC CIT Applications Interface for VMS software has been installed successfully. Starting the CIT V2.1 Installation Verification Procedure Logical Identifier = logical_identifier Calling the CIT$ASSIGN routine The CIT$ASSIGN routine has now made a successful DECnet connection to the CIT server that is defined by the specified logical identifier. A communications link has been established between the CIT client and the CIT server. The CIT Client has also successfully communicated with the PBX or the DECvoice module that is defined by the logical identifier. The CIT IVP has completed successfully The IVP checks that DEC CIT Applications Interface for VMS software has installed successfully by making a DECnet connection to each CIT server that you specify during the installation procedure. It then communicates with each PBX and/or each DECvoice module that you specify during the installation procedure. If the IVP cannot communicate with a PBX or DECvoice module, it returns an error message. For information on the IVP error messages, see Section 5.2. 15 CIT V2.1 Installation Verification Procedure completed at hh:mm Installation of CIT V2.1 completed at hh:mm VMSINSTAL procedure done at hh:mm $ LOGOUT SYSTEM logged out at dd-mmm-yyyy hh:mm:ss.ss Note that during the installation procedure, VMSINSTAL deletes or changes entries in the process symbol tables. Therefore, if you are going to continue using the system manager's account, and want to restore those symbols, log out and log in again. __________________________________________________________ 4 AFTER THE INSTALLATION The following sections describe the actions to take when installation is complete, and include a table showing files that are created during installation. _____________________________ 4.1 Starting the DEC CIT Applications Interface Software The installation procedure creates a startup file (SYS$STARTUP:CIT$STARTUP.COM), which starts the DEC CIT Applications Interface software. The CIT$STARTUP.COM file defines each CIT server node name that you specified during installation. It also defines the logical identifier for each PBX and/or DECvoice module connected to a CIT server that you specified. If you did not specify automatic startup during the installation procedure, run SYS$STARTUP:CIT$STARTUP.COM to define the appropriate names and start the software. If you are starting a new version of the DEC CIT Applications Interface for VMS software for the first time, you should then run the IVP (see Section 4.3). 16 If you want the DEC CIT Applications Interface for VMS software to restart whenever the system restarts, include the following command line in the site-specific startup command file (SYSTARTUP_V5.COM): @SYS$STARTUP:CIT$STARTUP Note that the instructions to start DECnet must be included in the system startup file, before the call to CIT$STARTUP. Note that if you have installed on a VAXcluster and have not rebooted the cluster, to enable the CIT software on other nodes within the cluster you have to load the CIT license on each node. _____________________________ 4.2 Changing CIT$STARTUP.COM This section applies only if, at any time after installing the DEC CIT Applications Interface for VMS software, you have to change a server node name or a logical identifier in the DEC CIT Applications Interface for VMS software startup file. The installation procedure prompts you to specify a server node name and a logical identifier for each PBX and/or each DECvoice module connected to the CIT server node(s). It includes these names in the DEC CIT Applications Interface for VMS software startup file SYS$STARTUP:CIT$STARTUP.COM. If you specify an invalid name or logical identifier during installation, or if a name changes at any time after installation, you must change the name defined in the startup file. To do this, you edit the file SYS$STARTUP:CIT$STARTUP.COM. 17 For example, if you specify the logical identifier CIT_ VOXA for a DECvoice module and it does not match the identifier defined at the server, you must change the identifier defined in the startup file. To do this, you edit the following line in SYS$STARTUP:CIT$STARTUP.COM: $ DEFINE/SYSTEM/EXECUTIVE CIT_VOXA CITVAX where CITVAX is the name of the server node. The new values are defined when you next run CIT$STARTUP.COM to start the CIT client software. _____________________________ 4.3 Run the IVP If you did not run the IVP automatically after installation, run it now to check that the DEC CIT Applications Interface for VMS software is installed correctly. Enter the following command: $ @SYS$TEST:CIT$IVP The procedure asks you if you have started the CIT software: * Have you started CIT? [Yes] : The DEC CIT Server software must be running before you run the IVP. The procedure then asks you if you want to run a complete IVP which checks the connection to each PBX and DECvoice module: * Do you want to run the IVP based on your CIT configuration? [YES] : If you answer Yes, the procedure checks that data is being transferred to each PBX and each DECvoice module connected to the CIT server. 18 If you answer No, the procedure prompts you for a logical identifier: * Enter the logical identifier for the PBX or DECvoice module: Specify the logical identifier for a PBX or DECvoice module. The IVP then tests that data is being transferred to that PBX or DECvoice module only: Logical Identifier = logical_identifier Calling the CIT$ASSIGN routine The CIT$ASSIGN routine has now made a successful DECnet connection to the CIT server that is defined by the specified logical identifier. A communications link has been established between the CIT client and the CIT server. The IVP checks that data is being transferred between the CIT client node and the CIT server node. It then checks that the client can communicate with the PBX or DECvoice module connected to the server: The CIT client has also successfully communicated with the PBX or the DECvoice module defined by the logical identifier. The CIT IVP has completed successfully. The procedure then prompts: * Do you want to run another IVP? [No] : If you want to run another IVP, you are prompted to specify the logical identifier for another PBX or DECvoice module. The IVP then tests that data is transferred to that PBX or DECvoice module. 19 If you do not want to run another IVP, the procedure is completed and the DCL ($) prompt is displayed: CIT V2.1 Installation Verification Procedure completed at hh:mm $ If the IVP fails, it does not necessarily mean that you have failed to install the DEC CIT Applications Interface for VMS software. See Section 5.2. _____________________________ 4.4 Read the Release Notes If you did not follow the recommendation to read the release notes during installation (see Section 3.2), read them now. When installation is complete, you can read the release notes by displaying or printing the file SYS$HELP:CIT021.RELEASE_NOTES. These release notes may contain important information about the DEC CIT Applications Interface software. _____________________________ 4.5 Back Up the System Disk When you have installed DEC CIT Applications Interface for VMS software successfully, back up the system disk. _____________________________ 4.6 Files Created During Installation Table 2 shows all the files that are created by the installation procedure, and the directories to which they are moved. 20 ________________________________________________________________ Table 2 Files Created During Installation _______________________________________________________ File_Name__________________Directory___________________ CIT$IVP.EXE SYS$COMMON:[SYS$TEST.CIT] CIT$TEST.EXE SYS$COMMON:[SYS$TEST.CIT] CIT021.RELEASE_NOTES SYS$HELP CIT$TEST.HLB SYS$HELP CIT$CLIENT_SHR.EXE SYS$LIBRARY CIT$DEFINITIONS.FOR SYS$LIBRARY CIT$DEFINITIONS.H SYS$LIBRARY CIT$DEFINITIONS.MLB SYS$LIBRARY CIT$DEFINITIONS.PAS SYS$LIBRARY CIT$DEFINITIONS.PEN SYS$LIBRARY CIT$DEFINITIONS.L32 SYS$LIBRARY CIT$DEFINITIONS.R32 SYS$LIBRARY CIT$STARTUP.COM SYS$STARTUP 21 ________________________________________________________________ Table 2 (Cont.) Files Created During Installation _______________________________________________________ File_Name__________________Directory___________________ _________CIT$IVP.COM________________SYS$TEST____________________ __________________________________________________________ 5 ERROR CONDITIONS The following sections give advice on what to do if you have problems that cause the installation procedure to fail or that cause the IVP to return error messages. They also give advice on what to do if you have problems following successful installation. _____________________________ 5.1 Errors During the Installation Procedure If the installation procedure fails, the following message is displayed: CIT V2.1 Installation failed. An error during installation can be caused by the use of an incorrect version of the VAX/VMS operating system, or if system quotas or resources are inadequate. For descriptions of the error messages generated by these conditions, see the VMS System Messages and Recovery Procedures. If installation fails and you solve the problem, you must repeat the installation procedure from step 2. 22 _____________________________ 5.2 Errors During the IVP If the IVP fails, the procedure returns an error message and a brief explanation. For example: The CIT$ASSIGN routine returned a %CIT-E-NOLOGID error. This indicates that the CIT logical identifier has not been defined or is incorrect. The CIT IVP has failed. Failure of the IVP does not necessarily mean that you have failed to install the DEC CIT Applications Interface for VMS software. The IVP can fail for one of the following reasons: o The DEC CIT Server for VMS software is not installed and running on the server node. o You specify an invalid server node name or logical identifier in step 6 of the installation procedure. This means that the startup file SYS$STARTUP:CIT$STARTUP.COM includes the invalid name or identifier. If this is the cause of the IVP failure, you must change the name or logical identifier by editing the CIT$STARTUP.COM file (see Section 4.2). When you have edited CIT$STARTUP.COM, rerun the startup file so that the new name or identifier is defined. o The DEC CIT Applications Interface for VMS software is not registered through the License Management Facility. See Section 2.4.2. o You specify a wrong logical identifier or nonexistent logical identifier when you run the IVP. If the logical identifier does not match a defined identifier at the specified server node, the IVP fails. If you specify a logical identifier that is not defined during the client or server software installation procedures, the IVP fails. 23 o A CIT server node has not been configured as part of a DECnet network. This means that the client does not recognize that CIT server node. If the IVP is successful but an error message is displayed, there is a problem with communication between the server and the PBX or DECvoice module. If, for example, the server cannot communicate with a PBX, CIT may return the following message: The CIT$ASSIGN routine has now made a successful DECnet connection to the CIT server that is defined by the specified logical identifier. A communications link has been established between the CIT client and the CIT server. %CIT-E-TIMEOUT, operation timed out However, the CIT$ASSIGN routine returned the above error. It indicates that the CIT client has not been able to communicate with the PBX or the DECvoice module defined by the logical identifier. The CIT IVP has completed successfully. Refer to the Troubleshooting section in the DEC CIT Server for VMS System Management manual for more information. When you have corrected the condition causing the error, rerun the IVP following the instructions in Section 4.3. _____________________________ 5.3 Determining and Reporting Problems If an error occurs while you are using DEC CIT Applications Interface for VMS software and you believe that the error is caused by a problem with CIT software, take one of the following actions: 24 o If you are within the warranty period or if you have a Software Support Contract that gives you telephone support, contact Digital's Customer Support Center or submit a Software Performance Report (SPR). o If you have a Self-Maintenance Software Contract, submit a Software Performance Report (SPR). If you find an error in the DEC CIT Applications Interface for VMS software documentation, fill out and submit the Reader's Comments form at the back of the document in which the error was found. Specify the problem, the relevant section, and the page number. 25 __________________________________________________________ 6 EXAMPLE INSTALLATION This section contains an example installation of DEC CIT Applications Interface for VMS software. ________________________________________________________________ Example 1 Example Log File for Client Installation ________________________________________________________________ $ @VMSINSTAL CIT MUA0: OPTIONS N VAX/VMS Software Product Installation Procedure V5.2-1 It is 29-OCT-1990 at 16:50. Enter a question mark (?) at any time for help. * Are you satisfied with the backup of your system disk [YES]? Y Please mount the first volume of the set on MUA0:. * Are you ready? Y %MOUNT-I-MOUNTED, CIT mounted on CITVAX$MUA0: The following products will be processed: CIT V2.1 Beginning installation of CIT V2.1 at 16:53 %VMSINSTAL-I-RESTORE, Restoring product saveset 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]: 4 * Do you want to continue the installation [NO]? Y %VMSINSTAL-I-RELMOVED , The product's release notes have been successfully moved to SYS$HELP. ________________________________________________________________ Example 1 Cont'd on next page 26 ________________________________________________________________ Example 1 (Cont.) Example Log File for Client Installation ________________________________________________________________ CIT Software Installation Procedure. %VMSINSTAL-I-RESTORE, Restoring product saveset B ... Product: CIT Producer: DEC Version: 2.1 Release Date: 21-DEC-1990 * Does this product have an authorization key registered and loaded? Y * Do you want to startup CIT automatically after installation [YES]? Y * Do you want to run the IVP immediately after installation [YES]? Y CIT$STARTUP.COM will now be created for you. This procedure creates the CIT startup file, CIT$STARTUP.COM which brings up and configures your CIT client node. It requires the CIT server node name(s) and the logical identifier for each PBX connected to and/or each DECvoice module installed on the server node(s). Provide the values in response to the following questions. You are given the opportunity to re-enter mistyped values. * Enter the name of the CIT server node: CITVAX * Enter the logical identifier for PBX or DECvoice module: CIT_PBX CIT Server nodename : CITVAX CIT Server logical identifier : CIT_PBX * Is this information correct? [YES]? Y * Do you want to specify another Logical identifier [YES]? Y ________________________________________________________________ Example 1 Cont'd on next page 27 ________________________________________________________________ Example 1 (Cont.) Example Log File for Client Installation ________________________________________________________________ * Enter the logical identifier for PBX or DECvoice module: VOX_A CIT Server nodename : CITVAX CIT Server logical identifier : VOX_A * Is this information correct? [YES]? Y * Do you want to specify another Logical identifier [YES]? N * Do you want to specify another CIT server [NO]? N Your CIT applications interface startup profile has been configured in CIT$STARTUP.COM. %VMSINSTAL-I-SYSDIR, This product creates system disk directory VMI$ROOT:[SYSTEST.CIT]. You have answered all the questions necessary for the installation to be completed. The installation will now run unattended. %VMSINSTAL-I-MOVEFILES, Files will now be moved to their target directories... Starting the CIT V2.1 Installation Verification Procedure Logical Identifier = CIT_PBX Calling the CIT$ASSIGN routine The CIT$ASSIGN routine has now made a successful DECnet connection to the CIT server that is defined by the specified logical identifier. A communications link has been established between the CIT client and the CIT server. The CIT client has also successfully communicated with the PBX or the DECvoice module defined by the logical identifier. The CIT IVP has completed successfully. ________________________________________________________________ Example 1 Cont'd on next page 28 ________________________________________________________________ Example 1 (Cont.) Example Log File for Client Installation ________________________________________________________________ Logical Identifier = VOX_A Calling the CIT$ASSIGN routine The CIT$ASSIGN routine has now made a successful DECnet connection to the CIT server that is defined by the specified logical identifier. A communications link has been established between the CIT client and the CIT server. The CIT client has also successfully communicated with the PBX or the DECvoice module defined by the logical identifier. The CIT IVP has completed successfully. CIT V2.1 Installation Verification Procedure completed at 17:01 Installation of CIT V2.1 completed at 17:01 VMSINSTAL procedure done at 17:01 $_______________________________________________________________ 29