    B     Read Before Installing Version 6.6A of DSM for OpenVMS VAX and	     Alpha        IS-DSMLC-VM   C     This document describes the distribution kits for the following 
     software:   .     o  Version 6.6A of DSM for OpenVMS VAX[TM]  0     o  Version 6.6A of DSM for OpenVMS Alpha[TM]  E     It also provides product information that supplements the DSM for      OpenVMS Release Notes.  (     This document has three attachments:  D     o  Attachment A, "Installing the DSM 6.6A kit," describes how to        install this MUP kit.  E     o  Attachment B, "Additional Product Information," provides prod- 3        uct information you need to know to use DSM.   D     o  Attachment C, "ECO Descriptions," is a list of problems fixed        in Version 6.6A.        Version Compatibility   D     Version 6.6A of DSM for OpenVMS is a maintenance update (MUP) toB     the most recent major release of DSM for OpenVMS, Version 6.6.F     Version 6.6A is compatible with DSM[TM] applications written underB     previous versions of DSM for OpenVMS[TM]. You need to be usingC     OpenVMS VAX Version 6.1, Version 6.2, or Version 7.0 to install E     and run Version 6.6A of DSM for OpenVMS VAX. You need to be using E     OpenVMS Alpha Version 6.1, Version 6.2, or Version 7.0 to install 2     and run Version 6.6A of DSM for OpenVMS Alpha.       Distribution  A     DSM is distributed by both InterSystems Corporation and Digi- D     tal Equipment Corporation. InterSystems distributes DSM softwareC     on the following media for both DSM for OpenVMS VAX and DSM for      OpenVMS Alpha:       o  9-track magnetic tape       o  TLZ06[TM]       o  TK50[TM] tape cartridge  A     Digital Equipment Corporation distributes DSM software on the      following media:       o  DSM for OpenVMS VAX:           -  9-track magnetic tape           -  TLZ06[TM]   !        -  TK50[TM] tape cartridge                          -  CD-ROM       o  DSM for OpenVMS Alpha:           -  CD-ROM  D     DSM supports the OpenVMS License Management Facility (LMF), thatD     allows licensed users access to DSM. If you are a first-time DSME     customer, the DSM distribution kit also includes a Product Autho- E     rization Key (PAK). The information contained in your PAK must be E     registered using LMF. For additional information, see the DSM In- D     stallation and Management Guide and the OpenVMS System Manager'sD     Manual. If you are upgrading from a previous release of DSM, see@     the DSM for OpenVMS Release Notes for information about LMF.       Installation Information  E     If you are installing DSM software for the first time, read Chap- C     ter 1 of the DSM for OpenVMS Installation and Management Guide. @     This chapter describes the installation procedure in detail.  A     If you are upgrading from a previous release of DSM, you must C     upgrade your existing configurations and volume sets. After you C     complete your software installation, the upgrade procedure will D     load Version 6.6A manager utilities and globals. You must recom-C     pile application routines, create new mapped routine files, and #     reinitialize the journal files.   A     A copy of the DSM for OpenVMS Release Notes is distributed in E     printed form and on line as a file with the DSM distribution kit. E     You can obtain a copy of these release notes when you install DSM D     by using the "OPTIONS N" parameter with the VMSINSTAL procedure.     For example:  9        $ @SYS$UPDATE:VMSINSTAL DSM <kit_device> OPTIONS N   C     If you are using CD-ROM media, you can obtain a copy of the re- E     lease notes using the CDMENU Utility. After installation, the DSM F     for OpenVMS Release Notes is available in SYS$HELP:DSM066.RELEASE_D     NOTES, and a copy of this cover letter and attachments is avail-3     able in the file SYS$HELP:DSM066A.COVER_LETTER.   -     Thank you for purchasing DSM for OpenVMS.        The DSM Product Group                       &                                      2                                 $      InterSystems Corporation. 1996                                                                                              &                                      3                       6     Attachment A - Installing the DSM Version 6.6A Kit  C     The following sections contain information about installing the      DSM kit.  %     Installing DSM for the First Time   E     If you are installing DSM software for the first time, read Chap- C     ter 1 of the DSM for OpenVMS Installation and Management Guide. @     That chapter describes the installation procedure in detail.  E     Take the following steps to install the DSM Version 6.6A MUP kit:        1. Back up your system.   C     2. Install the MUP kit. Run the SYS$UPDATE:VMSINSTAL procedure. F        On an OpenVMS VAX system, specify DSMVAXMUPA066A as the productF        name. On an OpenVMS Alpha system, specify DSMAXPMUPA066A as the        product name.  F     3. If you do not run the IVP during VMSINSTAL, install the DSM forE        OpenVMS images as shared using the SYS$STARTUP:DSM$INSTALL.COM         procedure.         Postinstallation Activities:  E     1. Use the SYS$MANAGER:DSM$INIT.COM procedure to create a DSM for -        OpenVMS environment manager's account.   E     2. Edit the OpenVMS system files to provide for automatic startup F        and shutdown of DSM for OpenVMS configurations when your system        is rebooted.   F     3. Log in to the DSM for OpenVMS environment manager's account and        run theD        SYS$MANAGER:DSM$CONFIGURE.COM procedure to initialize DSM for7        OpenVMS database volume sets and configurations.   ,     Upgrading From a Previous Version of DSM  D     If you are upgrading from a previous release of DSM you must up-D     grade your existing configurations and volume sets. Read the DSMC     for OpenVMS Release Notes in addition to the following informa- 	     tion.   F     Take the following steps to upgrade from a previous version of DSM$     to DSM for OpenVMS Version 6.6A:  <     1. Shut down all running DSM for OpenVMS configurations.       2. Back up your system.   C     3. Install the MUP kit. Run the SYS$UPDATE:VMSINSTAL procedure. F        On an OpenVMS VAX system, specify DSMVAXMUPA066A as the productF        name. On an OpenVMS Alpha system, specify DSMAXPMUPA066A as the        product name.  &                                      4                 F     4. If you do not run the IVP during VMSINSTAL, install the DSM forE        OpenVMS images as shared using the SYS$STARTUP:DSM$INSTALL.COM         procedure.         Postinstallation Activities:  C     1. Use the SYS$MANAGER:DSM$INIT.COM procedure from a privileged D        OpenVMS system account to upgrade DSM for OpenVMS manager ac-A        counts to DSM for OpenVMS Version 6.6A environment manager         accounts.  F     2. Log in to the DSM for OpenVMS environment manager's account andJ        run the SYS$MANAGER:DSM$UPGRADE.COM procedure. If you are upgradingC        from the previous major release to this MUP release (for ex- D        ample: if you are upgrading from Version 6.6 to Version 6.6A)C        or from one MUP release to the next (for example: if you are F        upgrading from Version 6.3C to 6.3D), you do not need to recom-&        pile your application routines.  D        If you are upgrading from any other major version of DSM (for@        example: if you are upgrading from Version 6.5 to Version;        6.6A), you must recompile your application routines.   C        DSM$UPGRADE optionally reinitializes before-image and after- A        image journal files and optionally upgrades mapped routine F        sets. You can also use ^BIJINIT, ^JRNINIT, and ^RMBLD to reini-E        tialize your journal files and rebuild your mapped routines at         a later time.  E     3. Edit the OpenVMS system files to provide for automatic startup F        and shutdown of DSM for OpenVMS configurations when your system        is rebooted.   E     4. If you are using DDP, reboot your OpenVMS system to reload the         DDP driver.  ,     5. Start up the upgraded configurations.       Alternate Root Installation   C     If you are installing DSM in an alternate root, read Appendix A B     of the DSM Installation and Management Guide. It describes the*     alternate root installation in detail.  =     Do the following to install the DSM Version 6.6A MUP kit:   $     1. Log in to the system account.  F     2. Shut down all running DSM configurations. In a VMScluster envi->        ronment, shut down configurations running on each node.  A     3. Extract the DSM$ALTROOT_INSTALL.COM procedure from the kit         saveset.   ;        On an OpenVMS VAX system, use the following command:   Y           $ BACKUP/LOG kit_device:DSMVAXMUPA066A.B/SAVE/SELECT=DSM$ALTROOT_INSTALL.COM; *   =        On an OpenVMS Alpha system, use the following command:   Y           $ BACKUP/LOG kit_device:DSMAXPMUPA066A.B/SAVE/SELECT=DSM$ALTROOT_INSTALL.COM; *   &                                      5                 A        Where kit_device is the distribution tape, CD-ROM, or disk (        where the DSM MUP kit is located.  E     4. Use the DSM$ALTROOT_INSTALL.COM procedure to create the alter- F        nate root directories and install the DSM software distribution        kit.   C     5. Use the DSM$ALTROOT.COM procedure to create and initialize a D        DSM environment manager's account for the new alternate root.  F     6. Use the DSM$ALTROOT.COM procedure to initialize the group logi-<        cal name search lists for all users within the GROUP.  R     7. Log in to the new manager account and use the SYS$MANAGER:DSM$CONFIGURE.COMC        procedure to create volume sets and to define new configura- 
        tions.   E     8. Edit system startup files to initialize alternate root instal-         lation on system reboot.                                                                           &                                      6                 1     Attachment B - Additional Product Information   D     The following sections contain additional information about doc-D     umentation and functionality that is not included in the DSM Re-     lease Notes.  '     Documentation Notes and Corrections   F     This section contains notes about and corrections to the DSM docu-     mentation set.  F     o  The DSM for OpenVMS Programmer's Guide left out the descriptionD        of the %SETUCI utility. The following is the missing descrip-        tion of this utility:          %SETUCI  D        Changes your default UCI and volume set. If you omit the flagA        argument, then DSM changes the UCI and volume set for both F        globals and routines. If you do not specify the volume set name)        (VOL), DSM uses the volume set S0.   B        You can control access to this external routine by enabling>        configuration access control using the ^CONFIG Utility.          Format:  -        SET X=$&ZLIB.%SETUCI(UCI,{VOL},{flag})              UCI    New UCI name $           VOL    New volume set name3           flag   G = change UCI and VOL for globals 4                  R = change UCI and VOL for routines  A     o  Chapter 9 of the DSM for OpenVMS Database Operations Guide F        contains a typographical error. Please replace every occurrenceE        of the word "rambles" in Chapter 9 with the word "re-enables."   $     Additional Technical Information  <     This section contains notes about DSM technical changes.  A     o  DSM for OpenVMS has implemented the following behavior for         handling year dates:   B        DSM will interpret that all year dates entered as two-digitE        numeric values refer to a year within the century in which the C        value is entered. For example, when you enter a year date of D        "99" before Dec 31, 1999 at 11:59:59, DSM will interpret thatB        year date as 1999. When you enter a year date of "99" afterE        Dec 31, 1999 at 11:59:59, DSM will interpret that year date as         2099.  D        The $HOROLOG special variable, however, will continue to keep!        the correct absolute date.   &                                      7                 F     o  A partial remedy for the BIJ file overflow issue (documented asD        ECO 5 in Attachment C) was included in Version 6.6 of DSM forD        OpenVMS. Version 6.6A of DSM for OpenVMS includes a more com-E        plete solution to the BIJ file overflow issue that was present (        in releases prior to Version 6.6.  @     o  To resolve the issue documented as ECO 6 in Attachment C,A        security auditing now allows users to disable auditing for B        non-journaled globals. To do so, run ^CONFIG and answer the        following prompts:   M           Modify security audit name definition [Y OR N] ?   <N>   Y <Return>            .            .            .   U           Disable security auditing for non-journaled globals [Y OR N] ?   Y <Return>   B     o  In an attempt to prevent DSM environment managers from dis-C        mounting a database set while that set is being dejournaled, E        Version 6.6 of DSM for OpenVMS inadvertently removed the abil- E        ity of running concurrent processes to dejournal separate vol- A        ume sets (as documented in ECO 7). This condition has been F        corrected in Version 6.6A. Dejournaling to separate volume sets'        can once again run concurrently.   B     o  For backwards compatibility, the $ZV special variable againF        reports the string "VAX DSM." (See ECO 15 in Attachment C for a*        description of the original issue.)                                                      &                                      8                 #     Attachment C - ECO Descriptions   +     The following table describes DSM ECOs.   G     ___________________________________________________________________ G     ECO____DSM_Problem_Description_____________________________________        DSM Version 6.6A-022  =     1      If a multiple-volume-set TP set is mounted in non- B            contiguous slots (for example: S2 and S4), the AIJ con-E            trol for the volume sets after the "gap" are not correctly 7            associated with the preceding TP volume set.   F     2      The recovery process can loop in HIB status in the event ofE            a cluster state transition due to another node going down, A            while the database set is dismounted. This only occurs D            when the database set has been dismounted from the masterD            node and the node attempting to perform a recovery is not#            capable of being master.   E     3      If you use a global reference with a $D value of 10 as the C            first argument of $GET and you supply a second argument, D            $GET always ignores the second argument and returns null.  2            >k ABC S ABC("TEST")="TEST" W $G(ABC,1)            15            >k ^ABC S ^ABC("TEST")="TEST" W $G(^ABC,1)   C     4      If you issue the following command with a reference to a E            volume set in a different DSM environment you get a DSM-E- F            NOSUCHVOLSET error, even though you can see the global withD            ^%G and $D (that is, the DDP connection to the volume set             is working properly).  &            W $ZS(^["UCI","VOL"]GLOBAL)  D     5      A possible BIJ FULL error may occur if a volume set has aD            large number of blocks allocated for globals. The routineB            used to search the global directory for top level dele-D            tions, creations, and modifications would perform before-B            image journaling on each of the blocks it scanned whileD            searching for the block that contained the global's data.D            DSM for OpenVMS Version 6.6 logs an error to DSMCRASH.LOG,            indicating the BIJ file overflow.  C     6      Security auditing cannot be turned off for non-journaled             globals.   @     7      Starting with DSM for OpenVMS Version 6.6, you can no8            longer run concurrent processes to dejournal.  C     8      If a "user open call" routine is defined, an inadvertent E            attempt to close a previously-closed journal file may hang             the process.   &                                      9               G     ___________________________________________________________________ G     ECO____DSM_Problem_Description_____________________________________   C     9      You may get a GDT allocation error because of corruption C            in free memory chain when smaller sized segments are al- E            located from an existing larger segment; for example: if a F            volume set containing x number of globals is dismounted andE            another volume set with x-n globals is mounted in the same             slot.  D     10     %ERRCHK fails to report a warning for using SET $FIND andB            SET $EXTRACT as described in the following extract from            help text:   Q                   The ^%ERRCHK Utility has been modified to detect occurrences of   M                   SET $EXTRACT and SET $FIND in your application. The utility   L                   prints a warning for each SET $EXTRACT occurrence when the  L                   /EXTENSION=SETFUNCTION command line qualifier is in force.  L                   However, it always prints a warning for each occurrence of                     SET $FIND.  F     11     Modifying the "ALTERNATE" field in the database description>            for mounting using an alternate name does not work.  F     12     A user can get an <UNDEF> when accessing the top level nodeF            of a global right after creating the global causes <UNDEF>.  @            JRNTEST4>K ^X S ^X(1)=0,^X=9,^Y(0)=9 S ^Y(0)=^Y(0)_^X  .            %DSM-E-UNDEF, undefined variable ^X  C     13     With a multi-volume transaction processing database set, D            you can experience a process hang when writing to the AIJE            file. The problem is caused when the TP monitor, DSM_JRNL, B            attempts to write to the AIJ for a non-base (any volumeB            set that is not first) TP volume set from the timer AST            routine.   F     14     DSM reports an erroneous DDP error message when dismounting            a database set.  6     15     The $ZV string no longer reports "VAX DSM."  D     16     If you try to display the current line of a % routine be-C            ing executed in a non "MGR" UCI, from any non "MGR" UCI, A            it fails with "(cannot display routine line -source is             unavailable)".   B     17     Under certain conditions, a process may go into a COM 0E            state while running ^%JOB on another process. For example, B            suppose ^%JOB is run for a process that defined a largeE            symbol by a process that has not defined a symbol table of F            the same size or larger. If the process running ^%JOB triesF            to load the symbol table of the first process, that process#            goes into a COM 0 state.   &                                     10               G     ___________________________________________________________________ G     ECO____DSM_Problem_Description_____________________________________   A     18     Under OpenVMS Alpha V6.2 only: The %BASEDIT Ecall sub- A            function 32 (convert lower to uppercase) does not work 3            correctly for certain German characters.   E     19     Errors occur in the ^CONTR utility in the following situa-             tions:   F            o  When using the wildcard as the last entry in a subscript               range list.   C            o  When an entry being inserted has more subscripts than %               the entry that follows.   F     20     If you try to display the current line of a % routine beingB            executed in a non "MGR" UCI, from any non "MGR" UCI, itF            fails with (cannot display routine line -source is unavail-8            able). Previous versions of DSM allowed this.  F     21     Modifying the volume-set label of an application volume setF            with ^LABEL changes that application volume set to a systemF            volume set. This can cause problems if the database set wasC            dismounted. Attempts to remount the database set will be D            unsuccessful. You must run DSM$VOLUPG on the database set            to remount it.   B     22     In prior versions of DSM, TP database sets could not beG     _______mounted_as_read-only._______________________________________                                                       &                                     11