 


















                     DECset________________________________________
                     Release Notes for CMS Server Version 1.2a

                     November 1997

                     These release notes for the DIGITAL CMS Client for
                     Windows Version 1.2a Server for DIGITAL OpenVMS
                     VAX and DIGITAL OpenVMS Alpha contain general
                     information.


                     Operating System and Version: OpenVMS VAX, Versions
                                                  6.0 - 7.1
                                                  OpenVMS Alpha,
                                                  Versions 6.1 - 7.1

                     Software Version:            DECset for OpenVMS,
                                                  Version 12.1 - 12.2
                                                  or DIGITAL CMS for
                                                  OpenVMS Systems,
                                                  Version 3.8 - 3.9

                     Software Version:            Server for CMS Client
                                                  for Windows Version
                                                  1.2a




                     Digital Equipment Corporation
                     Maynard, Massachusetts
 






              __________________________________________________________
        November 1997

              While DIGITAL or EDS believes the information included in
              this publication is correct as of the date of publication,
              it is subject to change without notice.

              Possession, use, or copying of the software described in
              this publication is authorized only pursuant to a valid
              written license from DIGITAL, an authorized sublicensor,
              or the identified licensor.

              Digital Equipment Corporation or EDS makes no represen-
              tations that the interconnection of its products in the
              manner described in this publication will not infringe
              existing or future patent rights, nor do the descriptions
              contained in this document imply the granting of licenses
              to make, use, or sell equipment or software in accordance
              with the description.

              © Digital Equipment Corporation 1995, 1997. All rights
              reserved.

              © Electronic Data Systems Limited 1995, 1997.

              The following are trademarks of Digital Equipment
              Corporation: DEC C, DECdocument, DECnet, DECset,
              DECwindows, DIGITAL, OpenVMS, VAX, VAX DOCUMENT and the
              DIGITAL logo.

              All other trademarks and registered trademarks are the
              property of their respective holders.

              This document was prepared using VAX DOCUMENT, Version
              2.1.
 













     ________________________________________________________________

                                                             Contents


     Preface..................................................      v


     1  General Information

         1.1  Introduction....................................    1-1
         1.2  Features........................................    1-1
         1.3  Requirements....................................    1-1
         1.4  New Features....................................    1-2

     2  After the Installation

         2.1  For DECnet......................................    2-1
         2.2  For TCP/IP......................................    2-2

     3  Troubleshooting

     4  Problems Fixed


     5  Restrictions

     6  Reporting Problems and Suggestions











                                                                  iii
 






        Tables

           1       Conventions ..................................     vi










































        iv
 











        ________________________________________________________________

                                                                 Preface



              These release notes characterize the Version 1.2a release
              of the DIGITAL CMS Client for Windows Server for OpenVMS
              systems.

        Intended Audience

              These release notes are intended for any user or system
              manager who needs information on the CMS Client for
              Windows Server.

        Document Structure

              These release notes are organized as follows:

              o  Chapter 1 contains general information about this
                 release and the server's software requirements.

              o  Chapter 2 contains important post installation steps.

              o  Chapter 3 provides additional information on trou-
                 bleshooting connection problems.

              o  Chapter 4 describes all problems resolved by the
                 current release.

              o  Chapter 5 describes all known restrictions.

              o  Chapter 6 describes how to report problems.






                                                                       v
 






        Associated Documents

              For more information on CMS and CMS Client for Windows,
              refer to the following documents

              o  Guide to DEC Code Management Systems for OpenVMS
                 Systems

              o  CMS Client for Windows User's Guide

        Sending DIGITAL Your Comments

              We welcome your comments on these release notes or on any
              other pieces of documentation. See Chapter 6 for details
              on how to contact DIGITAL with your comments.

        Conventions

              Table 1 lists the conventions used in these notes.

              Table_1_Conventions_______________________________________

              Convention__________Description___________________________

              $                   A dollar sign ($) represents the
                                  OpenVMS DCL system prompt.

              Ctrl/x              The key combination Ctrl/x indicates
                                  that you must hold down the key
                                  labeled Ctrl while you press another
                                  key, for example, Ctrl/Y or Ctrl/Z or
                                  a pointing device button.

              boldface text       Boldface text represents the
                                  introduction of a new term.

              monospace boldface  Boldface monospace text represents
              text                user input in interactive examples.

              italic text         Italic text represents book titles,
                                  parameters, arguments, and information
                                  that can vary in system messages (for
                                  example, Internal error number).

                                                (continued on next page)

        vi
 






              Table_1_(Cont.)_Conventions_______________________________

              Convention__________Description___________________________

              UPPERCASE           Uppercase indicates the name of
                                  a command, routine, the name of a
                                  file, the name of a file protection
                                  code, or the abbreviation of a system
                                  privilege.

              lowercase           Lowercase in examples indicates that
                                  you are to substitute a word or value
              ____________________of_your_choice._______________________
































                                                                     vii
 









                                                                       1
        ________________________________________________________________

                                                     General Information



              The information in these release notes pertain to DIGITAL
              CMS Client for Windows Server Version 1.2a.

        1.1 Introduction

              DIGITAL CMS Client for Windows Server Version 1.2a is a
              maintenance release.

        1.2 Features

              CMS Client for Windows Server Version 1.2a is compatible
              with both CMS Client V1.2 and V1.2a.

                ________________________Note  ________________________

                Note that the distribution media for the server
                contains both VAX and Alpha kits. If installing onto
                a VAX system, use the CMSSRV012a.* savesets from
                the distribution media. If installing onto an Alpha
                system, use the CMSSRV012a_AXP.* savesets from the
                distribution media.

                The server that is provided with the CMSSRV V1.2 kit
                must be installed in order for the CMS Client V1.2
                to work properly. CMS Client V1.2 will not work with
                any other version of the server.

                _____________________________________________________

        1.3 Requirements

              The CMS Server supports both DECset and the TCP/IP
              connections.

              For DECnet:

              o  PATHWORKS for OpenVMS VAX Version 5.0 or higher OR

                                                 General Information 1-1
 






              o  DIGITAL PATHWORKS for OpenVMS Alpha Version 5.0 or
                 higher

              For TCP/IP

              o  DIGITAL TCP/IP services for OpenVMS (UCX) Version 3.3
                 or Version 4.1 OR

              o  PathWay [TM] for OpenVMS Version 2.5.1 (Attachmate
                 Corporation) OR

              o  Cisco MultiNet [R] for OpenVMS Version 4.0 (Cisco
                 Systems [R], Inc.) OR

              o  TCPware [R] for OpenVMS Version 5.1 (Process Software
                 Corporation)

        1.4 New Features

              The following enhancements were added to the CMS Server
              V1.2:

              o  The server may be built for a different TCP/IP
                 transport.

                 Server command files and objects are optionally
                 provided to allow support for a different TCP/IP
                 transport without reinstalling the product.

              o  The transport may be changed after the CMS server has
                 been installed.

                 An option has been added to the installation of the CMS
                 server to retain build files after the installation.

                 If build files have been retained and the transport
                 method should change after the CMS server has been
                 installed, the build files may be used to build a
                 server appropriate for the new transport method.

                 If build files have not been retained and the transport
                 method should change after the CMS server has been
                 installed, the CMS server must be reinstalled to build
                 a server appropriate for the new transport method.

                 1. To build a server for UCX or TCPware, follow the
                    steps below:

        1-2 General Information
 






                    $ @SYS$COMMON:[SYSLIB.CMSSRV]BUILD_UCX_SERVER
                    $ COPY SYS$COMMON:[SYSLIB.CMSSRV]PCSA$CMS_SERVER.EXE -
                    _$ SYS$COMMON:[SYSEXE]
                    $ COPY SYS$COMMON:[SYSLIB.CMSSRV]PCSA$CMS_SERVER.COM -
                    _$ SYS$COMMON:[SYSEXE].

                 2. To build a server for MultiNet, follow the steps
                    below:

                    $ @SYS$COMMON:[SYSLIB.CMSSRV]BUILD_MULTI_SERVER
                    $ COPY SYS$COMMON:[SYSLIB.CMSSRV]PCSA$CMS_SERVER.EXE -
                    _$ SYS$COMMON:[SYSEXE]
                    $ COPY SYS$COMMON:[SYSLIB.CMSSRV]PCSA$CMS_SERVER.COM -
                    _$ SYS$COMMON:[SYSEXE]

                 3. To build a server for Pathway, perform the
                    following:

                    $ @SYS$COMMON:[SYSLIB.CMSSRV]BUILD_PWAY_SERVER
                    $ COPY SYS$COMMON:[SYSLIB.CMSSRV]PCSA$CMS_SERVER.EXE -
                    _$ SYS$COMMON:[SYSEXE]
                    $ COPY SYS$COMMON:[SYSLIB.CMSSRV]PCSA$CMS_SERVER_PWAY.COM -
                    _$ SYS$COMMON:[SYSEXE]PCSA$CMS_SERVER.COM

                    Note that the command file is renamed during the
                    copy operation.



















                                                 General Information 1-3
 









                                                                       2
        ________________________________________________________________

                                                  After the Installation





        2.1 For DECnet

              Create a DECnet object for the server on the OpenVMS
              system (in both the volatile and permanent databases).

              To create a DECnet Phase IV object, from a privileged
              account enter the following commands:

              $ MCR NCP SET OBJECT PCSA$CMS_SERVER -
              _$ NUM 0 FILE SYS$COMMON:[SYSEXE]PCSA$CMS_SERVER.COM

              $ MCR NCP DEFINE OBJECT PCSA$CMS_SERVER -
              _$ NUM 0 FILE SYS$COMMON:[SYSEXE]PCSA$CMS_SERVER.COM

              Use the following DCL command to check if the object
              exists:

              $ MCR NCP SHOW OBJECT PCSA$CMS_SERVER

              To create a DECnet Phase V object, from a privileged
              account enter the following commands:

              $ MCR NCL CREATE NODE 0 SESSION CONTROL APPLICATION -
              _$ PCSA$CMS_SERVER

              $ MCR NCL SET NODE 0 SESSION CONTROL APPLICATION -
              _$ PCSA$CMS_SERVER ADDRESS={NAME=PCSA$CMS_SERVER}, -
              _$ IMAGE NAME=SYS$COMMON:[SYSEXE]PCSA$CMS_SERVER.COM

              Use the following DCL command to check if the object
              exists:

              $ MCR NCL SHOW NODE 0 SESSION CONTROL APPLICATION -
              _$ PCSA$CMS_SERVER

                                              After the Installation 2-1
 






        2.2 For TCP/IP

              For TCP/IP connections to work properly, the remote
              execute service must be enabled on OpenVMS. This service
              is called REXEC or EXEC for most TCP/IP networks (service
              port 512). If this service is not enabled, users will
              be unable to connect to the CMS Server on OpenVMS. For
              example, if you have DIGITAL TCP/IP services for OpenVMS
              (UCX) enter the following command to check if REXEC is
              enabled:

              $ UCX SHOW SERVICE REXEC

              You will receive the reply ENABLED if it is running. If it
              is not running, you can start the REXEC service with the
              following command:

              $ UCX ENABLE SERVICE REXEC

              Also, several TCP/IP networks allow limits to be set
              on the number of REXEC services that can be running at
              any given time. The limit must be set high enough, based
              on the user count, to allow successful connections (for
              example if the limit is set to 5 and a 6th person tries to
              connect, that connection will fail).

              Increasing the REXEC services limit requires SYSPRV
              privilege:

              $ UCX DISABLE SERVICE REXEC
              $ UCX SET SERVICE/LIMIT=n REXEC
              $ UCX ENABLE SERVICE REXEC

              Where "n" represents the number of services.











        2-2 After the Installation
 









                                                                       3
        ________________________________________________________________

                                                         Troubleshooting



              If in attempting to set a session an error occurs, the
              cause of the error is usually an invalid password, invalid
              username, wrong protection settings on the server files,
              or the server not being installed.

              See CMS Client for Windows User's Guide and the CMS Client
              ReadMe.Txt file for more hints on troubleshooting.




























                                                     Troubleshooting 3-1
 









                                                                       4
        ________________________________________________________________

                                                          Problems Fixed



              The following bugs were fixed and restrictions removed in
              the CMS Server V1.2a:

              o  CMS Client hangs when fetching large files on certain
                 systems running UCX.

                 This problem is now fixed.




























                                                      Problems Fixed 4-1
 









                                                                       5
        ________________________________________________________________

                                                            Restrictions



              The following restrictions apply to the CMS Server V1.2a:

              o  The server is incompatible with CMS Client for Windows
                 V1.0 and V1.1.































                                                        Restrictions 5-1
 









                                                                       6
        ________________________________________________________________

                                      Reporting Problems and Suggestions



              Depending on the nature of the request or problem,
              customers can call DIGITAL provided their software
              contract and warranty entitles them to telephone support.

              Review the SPD and Warranty Addendum for an explanation of
              warranty.

              If a problem is encountered during the warranty period,
              customers can report the problem using DSNlink. In the
              United States, customers can call the DIGITAL Customer
              Support Center at 1-800-354-9000.

              In addition, DIGITAL provides access to Web Information
              and Support (WIS), an Internet-based electronic services
              application that allows customers to submit electronic
              service requests, access databases, download patch kits,
              transfer files from DIGITAL, and connect to global notes
              conferences via the World Wide Web.

              Dial-In Access (DIA) users can access WIS by:

              1. Opening http://www.service.digital.com/wis.

              2. Choosing a country code.

              3. Entering DIA Access ID and password.

              WIS and DIA use the same underlying account and directory
              on the DIGITAL Customer Support Center host system.

              Customers can register for DIA and receive a WIS account
              by contacting their Customer Support Center or local
              DIGITAL representative.

              This method can also be used to make requests for
              additional features or modifications to existing features.

                                  Reporting Problems and Suggestions 6-1
 






              When submitting a request, please include the following
              information:

              1. CMS Client version number and type of OpenVMS operating
                 system.

              2. Problem summary.

              3. Stack dumps or error logs (if applicable).

              4. Files in machine-readable media: magnetic tape
                 (preferred), floppy diskette, or tape cassette.

































        6-2 Reporting Problems and Suggestions
