Jump to page titleUNITED STATES
hp.com home products and services support and drivers solutions how to buy
» contact hp


more options
 
hp.com home
End of Jump to page title
HP Services software patches
Jump to content


» software & drivers
» ask Compaq
» reference library
» forums & communities
» support tools
» warranty information
» contact support
» parts
» give us feedback

associated links
» what's new
» contract access
» browse patch tree
» search patch tree
» join mailing list

patches by topic
» DOS
» OpenVMS
» Security
» Tru64 Unix
» Ultrix 32
» Windows
» Windows NT

connection tools
» nameserver lookup
» traceroute
» ping


Find Support Information and Customer Communities for Presario.
Content starts here
OpenVMS VMS73_SYS-V0600 Alpha V7.3 System ECO Summary
TITLE: OpenVMS VMS73_SYS-V0600 Alpha V7.3 System ECO Summary
 
NOTE:  An OpenVMS saveset or PCSI installation file is stored
       on the Internet in a self-expanding compressed file.
 
       For OpenVMS savesets, the name of the compressed saveset
       file will be kit_name.a-dcx_vaxexe for OpenVMS VAX or
       kit_name.a-dcx_axpexe for OpenVMS Alpha. Once the OpenVMS
       saveset is copied to your system, expand the compressed
       saveset by typing RUN kitname.dcx_vaxexe or kitname.dcx_alpexe.
 
       For PCSI files, once the PCSI file is copied to your system,
       rename the PCSI file to kitname.pcsi-dcx_axpexe or
       kitname.pcsi-dcx_vaxexe, then it can be expanded by typing
       RUN kitname.pcsi-dcx_axpexe or kitname.pcsi-dcx_vaxexe.  The
       resultant file will be the PCSI installation file which can be
       used to install the ECO.
 

New Kit Date:       16-JUN-2003
Modification Date:  Not Applicable
Modification Type:  NEW KIT

 
Copyright (c) Hewlett-Packard Company 2002,2003.  All rights reserved.

OP/SYS:     OpenVMS Alpha

COMPONENT:  SYSTEM

SOURCE:     Hewlett-Packard Company

ECO INFORMATION:

     ECO Kit Name:  VMS73_SYS-V0600
                    DEC-AXPVMS-VMS73_SYS-V0600--4.PCSI
     ECO Kits Superseded by This ECO Kit: VMS73_SYS-V0500  
     ECO Kit Approximate Size:  20368 Blocks
     Kit Applies To: OpenVMS Alpha V7.3
     System/Cluster Reboot Necessary:  Yes
     Rolling Re-boot Supported:  Yes
     Installation Rating:  INSTALL_1
                            1 - To be installed by all customers.

     Kit Dependencies:

       The following remedial kit(s), or later, must be installed BEFORE
       installation of this , or any required kit:

         VMS73_UPDATE-V0100 

       In order to receive all the corrections listed in this
       kit, the following remedial kits, or later, should also be installed:

         None 


ECO KIT SUMMARY:

An ECO kit exists for System components on OpenVMS Alpha V7.3.  
This kit addresses the following problems:


KNOWN ISSUES IN THE VMS73_SYS-V0600 KIT:

     o  After installing the VMS73_SYS-V0600 ECO kit, when SDA is used
        (e.g.  an ANAL/SYS command) you will see the following
        warning:

        $ANAL/SYS
        OpenVMS (TM) Alpha system analyzer

        %SDA-W-SDALINKMISM, link time of SYS$BASE_IMAGE built
        into SDA$SHARE (2-MAY-2003 11:27) does not match link
        time of image in system (12-MAY-2003 15:50)
        SDA>

        This warning is a notification only.  It does not affect the
        functionality of the kit, the images in the kit, the system or
        SDA.  It can be ignored completely.  This warning will be
        corrected in the next V7.3-1 SYS ECO kit.


PROBLEMS ADDRESSED IN VMS73_SYS-V0600 KIT:

     o  A system can hang or crash with an INVEXCEPTN bugcheck.  The
        symptoms of this problem can take several different forms,
        including exception bugchecks and forced crashes of hung
        systems.  Crashes have occurred at PC =
        PROCESS_MANAGEMENT+0AAF8 = SCH$ONE_SEC_C+00258 in module
        [SYS]RSE and at PC = LOCKING+0ADE0 = LCK$QUEUEWAIT_C+00050 in
        module [SYS]SYSENQDEQ.

        Crashdump Summary Information:
        ------------------------------
        Bugcheck Type:     OPERCRASH, Operator forced system crash
        Current Process:   NULL
        Current Image:     
        Failing PC:        FFFFFFFF.8013813C    SCH$CLASS_IDLE_C+000BC
        Failing PS:        00000000.00000003
        Module:            PROCESS_MANAGEMENT    (Link Date/Time:
                           28-MAR-2002 14:21:36.47)
        Offset:            0003213C

        Failing Instruction:
        SCH$CLASS_IDLE_C+000BC:         CMPLE           R2,#X3F,R7

        Crashdump Summary Information:
        ------------------------------
        Bugcheck Type:     OPERCRASH, Operator forced system crash
        Current Process:   NULL
        Current Image:     

        Failing PC:        FFFFFFFF.92637FC8
        Failing PS:        00000000.00001504
        Module:            
        Offset:            00000000

        Failing Instruction:
        FFFFFFFF.92637FC8:      BR       R31,#XFFFF9F

        Images Affected: [SYS$LDR]PROCESS_MANAGEMENT.EXE

                         [SYS$LDR]PROCESS_MANAGEMENT.STB

                         [SYS$LDR]PROCESS_MANAGEMENT_MON.EXE

                         [SYS$LDR]PROCESS_MANAGEMENT_MON.STB



     o  When creating many resource domain IDs via
        $SET_RESOURCE_DOMAIN with RSDM$_JOIN_DOMAIN, subsequent calls
        to end that association with RSDM$_LEAVE could result in the
        error SS$_RSDMNOTFOU (resource domain not found) on some IDs.

        Images Affected: [SYS$LDR]LOCKING.EXE




     o  Several multi-threaded servers have experienced a condition
        where the reference counts of various persona structures have
        fallen out of sync.  The security subsystem triggers an
        INVSECURESTATE system crash when this condition is detected by
        the sanity checks.

        Crashdump Summary Information:
        ------------------------------
        Bugcheck Type:     INVSECURESTATE, Invalid state detected
                           by SECURITY subsystem
        Current Process:   TNT_SERVER
        Current Image:     $1$DUA0:[SYS3.SYSCOMMON.][SYSEXE]
                           TNT$SERVER.EXE
        Failing PC:        FFFFFFFF.801A8E94
                           NSA$ASSUME_PERSONA_C+00064
        Failing PS:        10000000.00000000
        Module:            SECURITY
                           (Link Date/Time: 13-SEP-2000 06:39:51.16)
        Offset:            00006E94

        Images Affected: [SYS$LDR]SECURITY.EXE
                         [SYS$LDR]SECURITY_MON.EXE


     o  After installing the DEC-AXPVMS-VMS73_SYS-V0500--4.PSCI ECO
        kit, process hangs could occur when using SMTP mail.  When
        sending a mail message via SMTP, the mail is delivered but the
        process handling SMTP mail delivery hangs on creating the mail
        notification.  The mail delivery notification is never sent
        and any subsequent SMTP mail accumulates, unsent, in the
        queue.  The process hangs occur because BRKTHR tries to
        allocate memory from P1 space.  If it is unsuccessful, it
        tries to allocate from P0 space.  This is when the hangs
        occur.

        This kit removes the code fix for V7.3 that caused this
        problem to occur.  This fix was originally done to solve the
        following problem.  Since this fix is being removed, this
        problem could re-occur:

        -  The system can crash with a SSRVEXCEPT bugcheck when an
           image exits before the $BRKTHRU has been delivered to some
           of its targets.  Note that occurrence of this problem is
           rare and can only occur if:
 
             1.  A user program must use the asynchronous version of
                  the system call $BRKTHRU -- using the synchronous
                  form, $BRKTHRUW, prevents this)

              2.  The P1 allocation area sized by the SYSGEN parameter
                  CTLPAGES must be exhausted

              3.  The program must then exit before the $BRKTHRU call
                  has finished sending messages to all the appropriate
                  terminals.


        Note that the third issue cannot happen if the synchronous
        form of the $BRKTHRU call, $BRKTHRUW, is used.

        Crash Dump Summary:
        -------------------
        Bugcheck Type:     SSRVEXCEPT, Unexpected system
                           service exception
        Current Process:   SDNCC_MBX_MAIN
        Current Image:
        Failing PC:        FFFFFFFF.98B56AAC    IO_ROUTINES+46AAC
        Failing PS:        00000000.00000000
        Module:            IO_ROUTINES (Link Date/Time:
                           17-MAR-2001 03:30:01.24)
        Offset:            00046AAC

        Signal Array:            64-bit Signal Array:
        Arg Count    = 00000005  Arg Count   =          00000005
        Condition    = 0000000C  Condition   = 00000000.0000000C
        Argument #2  = 00000000  Argument #2 = 00000000.00000000
        Argument #3  = 006C41D0  Argument #3 = 00000000.006C41D0
        Argument #4  = 98B56AAC  Argument #4 = FFFFFFFF.98B56AAC
        Argument #5  = 00000000  Argument #5 = 00000000.00000000

        Failing Instruction:
        IO_ROUTINES+46AAC:      LDL     R6,(R7)

          Images Affected: [SYS$LDR]IO_ROUTINES.EXE
                           [SYS$LDR]IO_ROUTINES.STB
                           [SYS$LDR]IO_ROUTINES_MON.EXE
                           [SYS$LDR]IO_ROUTINES_MON.STB


     o  Recent changes to handle segmented data capturing from remote
        processes failed to detect possible data overrun conditions.
        If a buffer of insufficient size is passed to the service, the
        resulting overrun could result in NPP corruption.  Customer's
        experiencing a crash due to the data overrun would see
        corruption in NNP as the cause.  Programs that pass data
        buffers too small to contain the data items request,
        JPI$_RIGHTLIST items in particular, can trigger this crash.

        Images Affected: [SYS$LDR]PROCESS_MANAGEMENT.EXE
                         [SYS$LDR]PROCESS_MANAGEMENT.STB
                         [SYS$LDR]PROCESS_MANAGEMENT_MON.EXE
                         [SYS$LDR]PROCESS_MANAGEMENT_MON.STB



     o  The system can crash with an INVEXCEPTN, Exception while above
        ASTDEL bugcheck at FIND_CVCB_C+0001C.

        Crashdump Summary Information:
        ------------------------------
        Bugcheck Type:     INVEXCEPTN, Exception while above ASTDEL
        Current Process:   NULL
        Current Image:     
        Failing PC:        FFFFFFFF.8022939C    FIND_CVCB_C+0001C
        Failing PS:        20000000.00000804
        Module:            SYS$VCC    (Link Date/Time:
                           5-AUG-2001 01:16:26.26)
        Offset:            0000539C

        Stack Pointers:
        KSP = FFFFFFFF.C5FE9BE8  ESP = FFFFFFFF.C5FEB000
        SSP = FFFFFFFF.C5FD5000  USP = FFFFFFFF.C5FD5000

        Images Affected: [SYS$LDR]SYS$VCC.EXE
                         [SSY$LDR]SYS$VCC_MON.EXE


     O  Under rare circumstances the nonpaged pool expansion code
        could try to allocate additional physical memory for pool
        expansion without proper synchronization (ie, without the MMG
        spinlock).  This results in lost synchronization to the PFN
        data base that in turn could lead to a PFNREFNZRO bugcheck.

        Crashdump Summary Information:
        ------------------------------
        Bugcheck Type:     PFNREFNZRO, PFN reference
                           count nonzero
        Current Process:   BATCH_515
        Current Image:     $1$DGA20:[SQR4_3_4.ORA.BIN]SQR.EXE;6
        Failing PC:        FFFFFFFF.8006A82C MMG$INS_PFNH_C+0014C
        Failing PS:        18000000.00000203
        Module:            SYSTEM_PRIMITIVES_MIN (Link Date/Time:
                           4-NOV-2002 16:37:10.53)
        Offset:            0004282C

        Stack Pointers:
        KSP = 00000000.7FFA1AD8   ESP = 00000000.7FFA6000
        SSP = 00000000.7FFAC100   USP = 00000000.7A8FDE50

        Images Affected: [SYS$LDR]SYSTEM_PRIMITIVES.EXE
                         [SYS$LDR]SYSTEM_PRIMITIVES.STB
                         [SYS$LDR]SYSTEM_PRIMITIVES_MIN.EXE
                         [SYS$LDR]SYSTEM_PRIMITIVES_MIN.STB

     O  An image without UIC based protection access to a QUEUE
        object, but which is installed with the OPER privilege, will
        not be able to manipulate the QUEUE object as allowed when
        holding the OPER privilege.  This can result in a
        "%JBC-E-NOPRIV, insufficient privilege or queue protection
        violation" error message.

        Images Affected: [SYS$LDR]MESSAGE_ROUTINES.EXE


     O  On IO to a fibre channel disk, there are two SIO entries made
        in the IOPERFORM buffers for each IO request.  Normally we
        would expect to see SRQ (start request), SIO (start IO), EIO
        (end IO, and ERQ (end request).  What we are seeing SRQ, SIO,
        SIO, EIO, and ERQ.

        Images Affected: [SYS$LDR]IO_ROUTINES.EXE
                         [SYS$LDR]IO_ROUTINES.STB
                         [SYS$LDR]IO_ROUTINES_MON.EXE
                         [SYS$LDR]IO_ROUTINES_MON.STB


     O  Converting an integer to IEEE S floating with software
        completion produces a denormal (i.e.  very small) result value
        for very large integer values.  These denormal values cannot
        be represented exactly in the available mantissa bits.  The
        following C program demonstrates the problem :

        $ type test.c
        #include 

        main() {
            const float f1 = (float) 0x7fffffff;
            const float f2 = (float) 2147483647;
            const float f3 = (float) 2147483647.0;
            printf("f1 = %f\n", f1);
            printf("f2 = %f\n", f2);
            printf("f3 = %f\n", f3);
            return 0;
        }
        $ cc /float=ieee /ieee=denorm test
        $ link test
        $ run test
        f1 = 0.000000
        f2 = 0.000000
        f3 = 2147483648.000000
        $

        Note that any code using floating point constants to hold the
        float numbers, that is suffering from this bug, needs to be
        recompiled and relinked after the applying the new image.

        Images Affected: [SYS$LDR]EXCEPTION.EXE
                         [SYS$LDR]EXCEPTION_MON.EXE


     O  Callers to IO_PERFORM that have not provided an astprm when
        they completed IO_SETUP can cause the system to crash.  The
        timing of this problem is such that it has only happened when
        XFC is being used.  The crash typically occurs in
        CACHE$RESUME, in XFC, when a FASTIO IRP is one which XFC has
        already dismissed.

        Crashdump Summary Information
        -----------------------------
        Bugcheck Type:     ASSERTFAIL, System ASSERT failure detected
        Current Process:   ORA_PRSPC3267
        Current Image:     $1$DGA2:[ORACLE.V734.RDBMS]SRV.EXE
        Failing PC:        FFFFFFFF.802DE6B0    CACHE$RESUME_C+00AC0
        Failing PS:        10000000.00000804
        Module:            SYS$XFCACHE    (Link Date/Time:
                           15-JUL-2002 16:07:47.11)
        Offset:            000246B0

        Stack Pointers:
        KSP = 00000000.7FFA1E90   ESP = 00000000.7FFA6000
        SSP = 00000000.7FFAC100   USP = 00000000.7AF19DC0

        Images Affected: [SYS$LDR]IO_ROUTINES.EXE
                         [SYS$LDR]IO_ROUTINES_MON.EXE


     O  In the case where a fibre channel switch is disabled and the
        votes from a fibre channel quorum disk are required to
        maintain quorum, fibre channel disks may not all failover, and
        may hang.

        Images Affected: [SYS$LDR]IO_ROUTINES.EXE
                         [SYS$LDR]IO_ROUTINES_MON.EXE


     O  The system can crash when HSM is running in the system.  The
        crash indicates that DIOCNT is larger than DIOLMT.

        Images Affected: [SYS$LDR]IO_ROUTINES.EXE
                         [SYS$LDR]IO_ROUTINES_MON.EXE



PROBLEMS ADDRESSED IN VMS73_SYS-V0500 KIT:


  o  On  a  multi-processor  machine,  in  a  small  cluster,  when
     creating or updating a clusterwide logical name, a process may
     hang in RWSCS state.

          Images Affected: [SYS$LDR]SYS$CLUSTER.EXE


  o  The  system  can  crash  with   a   BADDALRQSZ   bugcheck   in
     EXE$DEANONPGDSIZ_C.   In  some, but not all cases, the current
     process is CLUSTER_SERVER.  In cases where the current process
     is  not  CLUSTER_SERVER,  the  stack  will  have  addresses in
     EXE$CSP_BRDCST and EXE$ALLOC_CSD.

          Images Affected:[SYS$LDR]SYS$CLUSTER.EXE


  o  F$GETSYI('RAD_MAX_RADS',node) fails  to  get  the  information
     from   the  specified  node.   Instead,  the  command  returns
     information from the current node the command is executing on.

     Note that with OpenVMS versions  before  V7.3-1,  RAD_MAX_RADS
     will return 1 if there is no RAD support, and will return 8 no
     matter how many QBBs are physically present.  This  limitation
     was  documented  in  the  V7.2-1H1R  New  Features and Release
     Notes, June 2000, section 3.5.6.1.

          Images Affected:[SYS$LDR]SYSGETSYI.EXE


  o  The system can crash with a FILCNTNONZ bugcheck.

          CrashDump Summary
          -----------------
          Bugcheck Type:     FILCNTNONZ, Open file count nonzero
                             after process rundown
          Current Image:     
          Failing PC:        FFFFFFFF.D269A360
                             PROCESS_MANAGEMENT+3C360
          Failing PS:        18000000.00000000
          Module:            PROCESS_MANAGEMENT (Link Date/Time:
                             18-OCT-2000 07:01:30.44)
          Offset:            0003C360


          Images Affected:[SYS$LDR]IO_ROUTINES.EXE
		          [SYS$LDR]IO_ROUTINES_MON.EXE
           		  [SYS$LDR]SYS$CLUSTER.EXE

	  CLD(s):CFS.84385

  o  The system can crash with a CWLNMERR bugcheck.  The failing PC
     is in the LOGICAL_NAMES executive image.

          Images Affected:[SYS$LDR]LOGICAL_NAMES.EXE
           		  [SYS$LDR]LOGICAL_NAMES.STB


  o  A program using C signals can be aborted  with  the  condition
     code set to the C signal value.

          Images Affected:[SYS$LDR]EXCEPTION.EXE
           		  [SYS$LDR]EXCEPTION_MON.EXE


  o  The system can crash with  an  SSRVEXCEPT,  Unexpected  system
     bugcheck at EXE$IO_PERFORM_C+00650

          Crashdump Summary Information:
          ------------------------------
          Bugcheck Type:    SSRVEXCEPT, Unexpected system
                            service exception
          Current Process:  ORA_P10111B1238
          Current Image:    $1$DGA92:[A_ORACLE.ORACLEV7336.RDBMS]SRV.EXE
          Failing PC:       FFFFFFFF.800CBEB0
                            EXE$IO_PERFORM_C+00650
          Failing PS:       30000000.00000203
          Module:           IO_ROUTINES (Link Date/Time:
                            5-NOV-2001 11:49:25.01)
          Offset:           00017EB0

          Failing Instruction:
          EXE$IO_PERFORM_C+00650: LDQ  R18,#X0108(R18)\


          Images Affected:[SYS$LDR]IO_ROUTINES.EXE
           		  [SYS$LDR]IO_ROUTINES_MON.EXE



  o  An SSREXCEPT bugcheck in MMG_STD$IOLOCK_BUF if it  must  fault
     in the affected page.

     Section  2.2.1  of  the  OpenVMS  Alpha  Guide  to   Upgrading
     Privileged  Code Applications describes how device drivers can
     lock  down  multiple  I/O  buffers  using   IRPEs   with   the
     EXE_STD$READLOCK,    WRITELOCK,    or   MODIFYLOCK   routines.
     Unfortunately, when an IRPE  was  passed  in  and  the  buffer
     required  a  page  fault this code used the IRP$PS_FDT_CONTEXT
     offset on the IRPE, which is only valid on an IRP.

     The correction for this problem is to delay  the  use  of  the
     IRP$PS_FDT_CONTEXT  cell  until after the original IRP pointer
     has been restored by a call to the error call back routine.

          Images Affected:[SYS$LDR]IO_ROUTINES.EXE
	           	  [SYS$LDR]IO_ROUTINES_MON.EXE
           		  [SYS$LDR]IO_ROUTINES.STB
           		  [SYS$LDR]IO_ROUTINES_MON.STB



  o  If there is a lot of cluster-wide $GETJPI activity, a  process
     may   hang  waiting  for  the  completion  of  an  RMS  $FLUSH
     operation.  The I/O  request  resulting  from  this  may  wait
     forever because the IOSB is not filled in.

          Images Affected:[SYS$LDR]PROCESS_MANAGEMENT.EXE
           		  [SYS$LDR]PROCESS_MANAGEMENT_MON.EXE



  o  A system that supports NUMA and has RAD_SUPPORT  enabled,  can
     crash  with  an  INVEXCEPTN  bugcheck  when the swapper is the
     current  process.   The   failing   PC   is   at   or   around
     MMG$WRTMFYPAG_C+006E4.

          Images Affected:[SYS$LDR]SYS$VM.EXE


  o  If a "space" pattern string is  combined  with  an  NEQ  match
     qualifier,  the  expected results of all processes will not be
     returned.

          Images Affected:[SYS$LDR]PROCESS_MANAGEMENT.EXE
           		  [SYS$LDR]PROCESS_MANAGEMENT.STB
           		  [SYS$LDR]PROCESS_MANAGEMENT_MON.EXE
           		  [SYS$LDR]PROCESS_MANAGEMENT_MON.STB


  o  Under some circumstances lookup of a device may fail.  If  the
     system doing the lookup has a zero allocation class specified,
     and attempts to  access  an  MSCP-served  disk  by  using  the
     NODE$DUA form, the access may fail because the device will not
     be found.

     This can be seen  in  the  following  SET  VOLUME/REBUILD  DCL
     example  (SHOW  DEVICE  fields  have  been  edited  for  space
     reasons).

          $ SHOW DEVICE $8$DUA10

          Device               Device           Error    Volume
          Name                 Status           Count    Label
          $8$DUA10: (UTRAMP)   Mounted alloc        0    TEST1

          $ WRITE SYS$OUTPUT F$GETDVI("$8$DUA10:","EXISTS")
            TRUE
          $
          $ WRITE SYS$OUTPUT F$GETDVI("$8$DUA10:","ROOTDEVNAM")
            _UTRAMP$DUA10:
          $
          $ WRITE SYS$OUTPUT F$GETDVI("$8$DUA10:","DEVNAM")
            _UTRAMP$DUA10:
          $
          $ WRITE SYS$OUTPUT F$GETDVI("_utramp$dua10:","EXISTS")
            FALSE
          $
          $ SET VOLUME/REBUILD $8$DUA10:
            %SET-E-NOTSET, error modifying _UTRAMP$DUA10:
            -RMS-F-DEV, error in device name or inappropriate
            device type for operation
            %SET-E-NOTSET, error modifying _UTRAMP$DUA10:
            -SYSTEM-W-NOSUCHDEV, no such device available

          A    lookup    via    the     runtime     library     function
          LIB$FIND_IMAGE_SYMBOL will also show the problem.


          Images Affected:[SYS$LDR]IO_ROUTINES.EXE
          		  [SYS$LDR]IO_ROUTINES_MON.EXE


  o  PWRK$STREAMSOS_V7.EXE is a big  file,  about  1760  blocks  in
     size.    If   this  file  has  become  very  fragmented  after
     installation then Advanced server  startup  may  fail  with  a
     SS$_BADPARAM  error.   This can occur if PWRK$STREAMSOS_V7.EXE
     is heavily fragmented  and  has  multiple  file  headers  (the
     following example has been modified for space reasons):

          $ @sys$startup:pwrk$startup
          The file server will use DECnet, TCP/IP.
          Advanced Server mail notification will use DECnet.
          %SYSTEM-F-BADPARAM, bad parameter value
          %TRACE-F-TRACEBACK, symbolic stack dump follows

          image    module     routine       line
          PWRK$LOADSTREAMS_V7 LOAD  main    7822

                 rel PC           abs PC
            000000000000213C 000000000003213C

          image    module     routine       line
          PWRK$LOADSTREAMS_V7 LOAD  __main  0

                 rel PC           abs PC
            0000000000000070 0000000000030070

          image    module     routine       line
                                            0
                 rel PC           abs PC

            FFFFFFFF802653B4 FFFFFFFF802653B4


          Images Affected:[SYS$LDR]SYSLDR_DYN.EXE



  o  The system can crash with a SSRVEXCEPT bugcheck when an  image
     exits  before  the  $BRKTHRU has been delivered to some of its
     targets.

          Crash Dump Summary:
          -------------------
          Bugcheck Type:     SSRVEXCEPT, Unexpected system
                             service exception
          Current Process:   SDNCC_MBX_MAIN
          Current Image:
          Failing PC:        FFFFFFFF.98B56AAC    IO_ROUTINES+46AAC
          Failing PS:        00000000.00000000
          Module:            IO_ROUTINES (Link Date/Time:
                             17-MAR-2001 03:30:01.24)
          Offset:            00046AAC

          Signal Array:            64-bit Signal Array:
          Arg Count    = 00000005  Arg Count   =          00000005
          Condition    = 0000000C  Condition   = 00000000.0000000C
          Argument #2  = 00000000  Argument #2 = 00000000.00000000
          Argument #3  = 006C41D0  Argument #3 = 00000000.006C41D0
          Argument #4  = 98B56AAC  Argument #4 = FFFFFFFF.98B56AAC
          Argument #5  = 00000000  Argument #5 = 00000000.00000000

          Failing Instruction:
          IO_ROUTINES+46AAC:      LDL     R6,(R7)


          Images Affected:[SYS$LDR]IO_ROUTINES.EXE
           		  [SYS$LDR]IO_ROUTINES.STB
           		  [SYS$LDR]IO_ROUTINES_MON.EXE
           		  [SYS$LDR]IO_ROUTINES_MON.STB



  o  Entering an empty path into a SET DEVICE/SWITCH/PATH  command,
     such as:

                 SET DEVICE/SWITCH/PATH =""

          will cause the system  to  bugcheck.   The  SET_DEVICE  system
          service  used  with  a  zero  path  length will also cause the
          system to crash.

          Crashdump Summary Information:
          ------------------------------
          Bugcheck Type:     INVEXCEPTN, Exception while above ASTDEL
          Current Process:   SYSTEM
          Current Image:     $1$DGA100:[SYS7.SYSCOMMON.]
                             [SYSEXE]SET.EXE
          Failing PC:        FFFFFFFF.803A7050
                             MPDEV$MANUAL_SWITCH_C+00290
          Failing PS:        10000000.00000803
          Module:            MULTIPATH (Link Date/Time:
                             18-JUN-2002 08:04:33.18)
          Offset:            00001050

          Stack Pointers:
          KSP = 00000000.7FFA1BA8   ESP = 00000000.7FFA6000
          SSP = 00000000.7FFAC100   USP = 00000000.7AE9B5B0

          Failing Instruction:
          MPDEV$MANUAL_SWITCH_C+00290: LDL R17,#X0010(R6)


          Images Affected:[SYS$LDR]MULTIPATH.EXE
           		  [SYS$LDR]MULTIPATH.STB
		          [SYS$LDR]MULTIPATH_MON.EXE
		          [SYS$LDR]MULTIPATH_MON.STB



  o  If a process uses $GETJPI to  request  rightslist  information
     about  itself  then  the  information  appears  to be correct.
     However, if another process uses  $GETJPI  to  get  rightslist
     information  about  that  same  process  then  the information
     returned is incorrect.

          Images Affected:[SYS$LDR]PROCESS_MANAGEMENT.EXE
		          [SYS$LDR]PROCESS_MANAGEMENT.STB
		          [SYS$LDR]PROCESS_MANAGEMENT_MON.EXE
		          [SYS$LDR]PROCESS_MANAGEMENT_MON.STB



 o  Lock manager and nonpaged pool usage may  increase  over  time
    due  to  a  memory  leak  of lock blocks (LKB) and AST control
    blocks (ACB64).  This lock manager leak only occurs under very
    specific   circumstances  which  are  not  that  common.   The
    specific circumstances are the $DEQ of a  process  based  lock
    with a pending completion AST that has not yet been delivered.

          Images Affected:[SYS$LDR]LOCKING.EXE
		          [SYS$LDR]LOCKING.STB



  o  A call to SYS$GETSYI to return system rights will only  return
     the  first  right  in  the  rightslist, regardless of how many
     rights are in the list.

          Images Affected:[SYS$LDR]SYSGETSYI.EXE


  o  Use of SPAWN or DCL PIPE commands result in  the  increase  of
     the  process'  PAGFILCNT  (JIB$L_PGFLCNT).   The more SPAWN or
     PIPE activity, the higher the PAGFILCNT grows.

          Images Affected:[SYS$LDR]SHELL8K.EXE



  o  If a global section follows a process section  in  process  P0
     space  with the same section index value, the system can crash
     with a WSLXVANMAT bugcheck during image rundown.

     Crash Information:
     ------------------
     Bugcheck Type: WSLXVANMAT, Working set list entry
                    does not match VA
     Failing PC:    FFFFFFFF.8016FEF0    SYS$VM+25EF0
     R1  =  00000000.00000000


          Images Affected:[SYS$LDR]SYS$VM.EXE
		          [SYS$LDR]SYS$VM.STB



  o  Multiprocessors making heavy use of RMS global  buffers  could
     encounter  a  variety of system crashes related to a corrupted
     system buffer object list, PCB$Q_BUFOBJ_LIST off of the system
     PCB  (process control block).  These could include things such
     as:

           o  SSRVEXCEPTN at MMG_STD$INSERT_BOD_C+2C

           o  INVEXCEPTN at EXE$DELETE_BUFOBJ_C+1C0

           o  Nonpaged pool corruption involving BOD sized  packets  and
              lists

           o  CPUSPINWAIT due to pool corruption with TQE list

           o  Global Buffered File access getting SYS-F-IVLOCKID errors


          Images Affected:[SYS$LDR]SYS$VM.EXE
		          [SYS$LDR]SYS$VM.STB


  o  When the lock manager is unable to obtain physical  memory  to
     allocate  an  RSB,  the  error  path to return an insufficient
     memory error may result in a system crash.

          Crashdump Summary Information:
          ------------------------------
          Bugcheck Type:     INVEXCEPTN, Exception while
                             above ASTDEL
          Failing PC:        FFFFFFFF.80184888
                             RSDM_OSR_PREPROCESS_C+00658                   
          Failing PS:        18000000.00000804
          Module:            LOCKING  (Link Date/Time:
                             28-MAR-2002 09:11:25.76)
          Offset:            00004888

          Failing Instruction:
          RSDM_OSR_PREPROCESS_C+00658: LDL R23,#X00C0(R5)


          Images Affected:[SYS$LDR]LOCKING.EXE
		          [SYS$LDR]LOCKING.STB



  o  A process can exit with the status SYS$_UNWIND (920).  If this
     is  a  detached  process, this error status can be seen in the
     accounting report by executing the command:

             $ account /since=time/before=time

     where time is the time  the  detached  process  exited.   This
     problem  can  affect Oracle 9i RAC LMS processes such that the
     Oracle instance crashes with the error ORA-00484.

          Images Affected:[SYS$LDR]EXCEPTION.EXE
		          [SYS$LDR]EXCEPTION.STB
		          [SYS$LDR]EXCEPTION_MON.EXE
		          [SYS$LDR]EXCEPTION_MON.STB

  o  The symptoms of this problem can take several different forms,
     including  exception  bugchecks  and  forced  crashes  of hung
     systems.     Crashes     have     occurred     at     PC     =
     PROCESS_MANAGEMENT+0AAF8   =   SCH$ONE_SEC_C+00258  in  module
     [SYS]RSE and at PC = LOCKING+0ADE0 = LCK$QUEUEWAIT_C+00050  in
     module [SYS]SYSENQDEQ.

          Crashdump Summary Information:
          ------------------------------
          Bugcheck Type:     OPERCRASH, Operator forced system crash
          Current Process:   NULL
          Current Image:     
          Failing PC:        FFFFFFFF.8013813C    SCH$CLASS_IDLE_C+000BC
          Failing PS:        00000000.00000003
          Module:            PROCESS_MANAGEMENT    (Link Date/Time: 28-MAR-2002
          14:21:36.4
          7)
          Offset:            0003213C

          Failing Instruction:
          SCH$CLASS_IDLE_C+000BC:         CMPLE           R2,#X3F,R7


          Crashdump Summary Information:
          ------------------------------
          Bugcheck Type:     OPERCRASH, Operator forced system crash
          Current Process:   NULL
          Current Image:     
          Failing PC:        FFFFFFFF.92637FC8
          Failing PS:        00000000.00001504
          Module:            
          Offset:            00000000

          Failing Instruction:
          FFFFFFFF.92637FC8:      BR       R31,#XFFFF9F


          Images Affected:[SYS$LDR]PROCESS_MANAGEMENT.EXE
        		  [SYS$LDR]PROCESS_MANAGEMENT.STB
	           	  [SYS$LDR]PROCESS_MANAGEMENT_MON.EXE



PROBLEMS ADDRESSED IN VMS73_SYS-V0400 KIT:

  o  V7.3 nodes do not correctly handle Quorum Disks.   The  issues
     can  result in either CLUEXIT bugchecks or numerous connection
     manager console messages:

       %CNXMAN, Proposing modification of quorum or quorum disk
       membership

     Any cluster with a quorum disk and V7.3  nodes  requires  this
     fix.

          Images Affected:  [SYS$LDR]SYS$CLUSTER.EXE


  o  SDA can ACCVIO when the SHOW LOCK/POOL command is issued.

        SDA> SHOW LOCK/POOL/SUMMARY
        %SYSTEM-F-ACCVIO, access violation, reason mask=00, virtual
        address=0000000000678472, PC=0000000000144070, PS=0000001B

          Images Affected:  [SYSLIB]SDA$SHARE.EXE


  o  Doing I/O on a multipath device, when the current  path  is  a
     secondary,  results  in  an increase in the UCB$L_OPCNT in the
     primary as  well  as  the  current  path  UCB.   Although  the
     UCB$L_OPCNT in the secondary grows faster than in the primary,
     the UCB$L_OPCNT in the primary should not be changing (except,
     at  most  by  once  per  second  for  polling.) This is easily
     observed when doing a DIR/SIZE on the system disk.

     A number of customers and third-parties rely on these counters
     to  be  accurate  in  their  performance and capacity planning
     tools.

          Images Affected:  SYS$LDR]IO_ROUTINES.EXE
                            SYS$LDR]IO_ROUTINES_MON.EXE
                            SYS$LDR]IO_ROUTINES.STB
                            SYS$LDR]IO_ROUTINES_MON.STB


  o  The Lock Manager can deliver a  blocking  AST  to  the  system
     owned  locks  incorrectly.  The window of opportunity for this
     to occur is very small, but if it  happens,  the  system  will
     often crash with an Invalid exception error.

     Crashdump Summary Information:
     ------------------------------
     Bugcheck Type:     SSRVEXCEPT, Unexpected system service
                        exception
     Failing PC:        FFFFFFFF.802059E8    XQP$FCBSTALE_C
     Failing PS:        00000000.00000000
     Module:            F11BXQP
                        (Link Date/Time: 17-MAR-2001 03:16:47.08)
     Offset:            0000D9E8

          Images Affected:  [SYS$LDR]LOCKING.EXE


  o  During installation of an OpenVMS ECO kit, the  names  of  the
     installed         images         are         written        to
     SYS$COMMON:[SYSUPD]VMS$REMEDIAL_OLD_FILES.TXT.    These   file
     names  should  be written with _OLD appended to the end of the
     filename along with the name of the kit.  The  VMS73_SYS-V0300
     ECO kit did not do this editing correctly.

     When upgrading from  V7.3  to  a  later  version  of  OpenVMS,
     operating  system  files  from the previous version of OpenVMS
     are deleted.  The  above  file  name  errors  will  cause  old
     operating  system  files  to  be  left on the system after the
     upgrade.  In addition, users will see  multiple  instances  of
     the following installation warning message during the upgrade:

       [SYSUPD]VMS$REMEDIAL_OLD_FILES.TXT
       %UPGRADE-W-NOTOLD2, does not have "_OLD" at end
       %UPGRADE-W-NOTOLD2, file not deleted

     This      change      corrects      the      filenames      in
     [SYSUPD]VMS$REMEDIAL_OLD_FILES.TXT.

          Images Affected: [SYSUPD]VMS$REMEDIAL_OLD_FILES.TXT

PROBLEMS ADDRESSED IN VMS73_SYS-V0300 KIT:

  o  The following command should change the path to the disk:

     $SET DEVICE/SWITCH/PATH=   

     Sometimes it does not.

          Images Affected:  [SYS$LDR]MULTIPATH.EXE
                            [SYS$LDR]MULTIPATH.STB


  o  A system can hang with many processes in MUTEX wait state.

          Images Affected:  [SYS$LDR]IO_ROUTINES.EXE
                            [SYS$LDR]IO_ROUTINES_MON.EXE
                            [SYS$LDR]IO_ROUTINES.STB
                            [SYS$LDR]IO_ROUTINES_MON.STB


  o  On Alphaserver GS-series machines running OpenVMS V7.3,  after
     several  console  messages  indicating pool expansion failure,
     the system may hang, or crash with  CPUSPINWAIT  or  CPUSANITY
     bugchecks.

          Images Affected:  [SYS$LDR]SYSTEM_PRIMITIVES.EXE
                            [SYS$LDR]SYSTEM_PRIMITIVES_MON.STB
                            [SYS$LDR]SYSTEM_PRIMITIVES.EXE
                            [SYS$LDR]SYSTEM_PRIMITIVES_MON.STB

  o  The F$PID lexical function in DCL does not  work  as  expected
     when  the  user running the procedure does not have sufficient
     privilege to examine other processes.  The result may be  that
     process  selection  in  combination with F$CONTEXT returns the
     wrong PID.

          Images Affected:  [SYS$LDR]PROCESS_MANAGEMENT.EXE
                            [SYS$LDR]PROCESS_MANAGEMENT_MON.EXE
                            [SYS$LDR]PROCESS_MANAGEMENT.STB
                            [SYS$LDR]PROCESS_MANAGEMENT_MON.STB


  o  The system can crash with an INVEXCEPTN, Exception while above
     ASTDEL bugcheck:

     Crashdump Summary Information:
     ------------------------------
     Bugcheck Type:     INVEXCEPTN, Exception while above ASTDEL
     Current Process:   SWAPPER
     Current Image:     
     Failing PC:        FFFFFFFF.80115E0C
                        SCH$REPORT_EVENT_C+0082C
     Failing PS:        10000000.00000800
     Module:            PROCESS_MANAGEMENT
                        (Link Date/Time:  6-JUN-2001 17:31:27.58)
     Offset:            00009E0C

          Images Affected:  [SYS$LDR]PROCESS_MANAGEMENT.EXE
                            [SYS$LDR]PROCESS_MANAGEMENT_MON.EXE
                            [SYS$LDR]PROCESS_MANAGEMENT.STB
                            [SYS$LDR]PROCESS_MANAGEMENT_MON.STB


  o  MOUNT and Mount Verification sanity checks have  been  relaxed
     to correct the following issues:

       o  A MOUNT/NOWRITE command on a disk on one cluster will  now
          work  correctly  even if the disk is mounted with a /WRITE
          qualifier on another cluster  in  the  SAN  (Storage  Area
          Network).  Previously, depending on the order in which the
          mounts were executed, the mount would fail with the  error
          message:

          DIFVOLMNT - different volume already mounted on this
                      device.

          Images Affected:  [SYS$LDR]IO_ROUTINES.EXE
                            [SYS$LDR]IO_ROUTINES_MON.EXE
                            [SYS$LDR]IO_ROUTINES.STB
                            [SYS$LDR]IO_ROUTINES_MON.STB


  o  Queue  and  other   clusterwide   operations   fail   with   a
     SS$_BADPARAM  bugcheck  when  a  COE-baselevel  node is in the
     cluster.

          Images Affected:  [SYSLIB]SECURESHR.EXE
                            [SYSLIB]SECURESHRP.EXE


  o  When  called  from  exec  mode,  ACCVIOs  are  returned   from
     SYS$PERSONA_CREATE.

          Images Affected:  [SYSLIB]SECURESHR.EXE
                            [SYSLIB]SECURESHRP.EXE


  o  A  SSRVEXCEPT  system  crash  can  occur  when   a   call   to
     $PERSONA_CREATE  is  made  for  an  account  with a [0,0] UIC.
     (Though it is possible to create such an account, the  account
     is invalid on VMS systems).

     Crashdump Summary Information:
     ------------------------------
     Bugcheck Type:     SSRVEXCEPT, Unexpected system service
                        exception
     Current Process:   BUILDER
     Failing PC:        FFFFFFFF.801CB968    NSA$REFERENCE_RIGHTS_CHAIN_C+00008
     Failing PS:        10000000.00000201
     Module:            SECURITY    (Link Date/Time:
                        5-AUG-2001 01:12:10.86)
     Offset:            0000B968

          Images Affected:  [SYS$LDR]SECURITY.EXE
                            [SYS$LDR]SECURITY_MON.EXE


  o  On a system that contains a CPU numbered 31, CPU #31 can run a
     thread  even  if  that thread has specified, either by setting
     required capabilities or hard affinity, that it  must  run  on
     another  CPU.   Thus,  some  functions  which  must run on the
     primary CPU may occasionally be run on CPU  #31.   There  need
     not actually be 31 CPUs.  This bug can cause problems with CPU
     power down/up of any CPU, with  CPU  assignment  between  soft
     partitions, or garbled or missing console output.

          Images Affected:  [SYS$LDR]PROCESS_MANAGEMENT.EXE
                            [SYS$LDR]PROCESS_MANAGEMENT_MON.EXE
                            [SYS$LDR]PROCESS_MANAGEMENT.STB
                            [SYS$LDR]PROCESS_MANAGEMENT_MON.STB

  o  If a packet is requested from nonpaged  pool  that  is  larger
     than  nonpaged  pool's  maximum  allowed  size  (NPAGVIR), the
     request fails.  However, nonpaged pool expands to its  maximum
     size, even though the request can not be satisfied.

          Images Affected:  [SYS$LDR]SYSTEM_PRIMITIVES.EXE
                            [SYS$LDR]SYSTEM_PRIMITIVES_MIN.EXE
                            [SYS$LDR]SYSTEM_PRIMITIVES.STB
                            [SYS$LDR]SYSTEM_PRIMITIVES_MIN.STB


  o  A system may have one of  the  following  problems  caused  by
     possible  corruption  of  the process scheduling queues and/or
     the SCH$GQ_PFWQ queue:

       o  Processes stuck in CUR  but  on  the  PFW  queue  and  not
          executing

       o  Processes stuck in PFW on the PFW queue and not executing

       o  The  PFW  queue  merged  in  with  a  COM  queue,  usually
          resulting in an INCON_SCHED or a CPUSPINWAIT bugcheck.

       o  An INVEXCEPTN at SCH$QEND_C+38 trying to access  the  cell
          CTL$GL_REPORT_USER_FAULTS.

          Images Affected:  [SYS$LDR]SYS$VM.EXE


  o  In an OpenVMS mixed version  clustered  environment,  a  fatal
     invalid identifier format (%SYSTEM-F-IVIDENT) error can result
     in versions of  OpenVMS  that  are  not  OpenVMS  COE  (Common
     Operating Environment) compliant.

     This can occur  on  non-COE  compliant  OpenVMS  systems  when
     attempting to display the rights identifiers of a process that
     is  granted  a  valid  GID  COE  identifier.   The   following
     commands,  lexicals,  (and  respective system services), cause
     the %SYSTEM-F-IVIDENT system message to be  displayed  instead
     of the text translation of this COE GID IDENTIFIER:

       1.  F$GETJPI("PID_xxx","PROCESS_RIGHTS")

       2.  F$GETJPI("PID_xxx","RIGHTSLIST")

       3.  $ SHOW PROCESS/ALL

       4.  $ SHOW PROCESS/RIGHTS

          Images Affected: [SYS$LDR]SECURITY.EXE
                           [SYS$LDR]SECURITY_MON.EXE
                           [SYS$LDR]SECURITY.STB
                           [SYS$LDR]SECURITY_MON.STB


  o  A system can fail to boot with the following error:

         %INIT_IO_DB-F-LOAD_SH_ERROR, Error Loading shadowing
         driver SYS$SHDRIVER.EXE, error = 0x00000870

          Images Affected:  [SYS$LDR]EXEC_INIT.EXE
                            [SYS$LDR]EXEC_INIT.STB


  o  The sys$crmpsc_gdzro_64() returns a numeric  value  indicating
     that memory is reserved when it is not.

          Images Affected:  [SYS$LDR]SYSTEM_PRIMITIVES.EXE
                            [SYS$LDR]SYSTEM_PRIMITIVES_MIN.EXE
                            [SYS$LDR]SYSTEM_PRIMITIVES.STB
                            [SYS$LDR]SYSTEM_PRIMITIVES_MIN.STB
                            [SYS$LDR]SYS$VM.EXE


  o  If a RADCHECK is done  on  a  system  running  the  DECwindows
     Display  Server  (or possibly other images that memory map I/O
     space or other pages that do not appear in the  PFN  database)
     the  system  will  crash  with  an invalid exception bugcheck.
     Analysis will show the exception is an ACCVIO in image SYS$VM,
     image MMG$RADCHECK_PROCESS.

          Images Affected:  [SYS$LDR]SYS$VM.EXE

  o  A system can crash with a REFCNTNEG, PFN  reference  count  is
     negative  bugcheck.   The PFN database element being mapped is
     pointed to by R15, so, the SDA command:

           FORMAT @^QR15/TYPE=PFN

     can be used to examine the value in the  PFN$W_BO_REFC  field.
     If it is greater than or equal to 8000, 32768 decimal, this is
     the cause of the bugcheck.

     Crashdump Summary Information:
     ------------------------------
     Bugcheck Type:     REFCNTNEG, PFN reference count is negative
     Current Process:   ORA_CLUS_DBWR
     Current Image:     DSA2:[ORACLE.CODE_V7344.RDBMS]SRV.EXE
     Failing PC:        FFFFFFFF.801131C8
                        MMG_STD$DELBUFOBJPAGES_C+00678
     Failing PS:        04000000.00000800
     Module:            SYS$VM
                        (Link Date/Time: 29-DEC-1999 04:29:36.63)
     Offset:            000251C8

          Images Affected:  [SYS$LDR]SYS$VM.EXE


  o  On NUMA systems, at the end of the system startup, unused PFNs
     are  released for the exec data huge page region, and then the
     exec  code  and  resident  code  region  will  be  replicated.
     Customers  having  their own drivers, which can be reloaded on
     the  fly,  need  to  clear  the  RELEASE_PFNS   bit   in   the
     LOAD_SYS_IMAGES  SYSGEN  parameter to avoid releasing PFNs for
     the exec data region.  Otherwise the driver reload fails  with
     an error.

     This change stops release of PFNs for the  exec  data  region.
     This  allows  customers to reload drivers on the fly and still
     get the benefit of system code replication.           

          Images Affected:  [SYS$LDR]SYSLDR_DYN.EXE

  o  Connection to an Oracle server can fail:

         ORACLE error---
         ORA-01034: ORACLE not available
         ORA-27123: unable to attach to shared memory segment
         %SYSTEM-E-SECREFOVF, too many section refer
         %SYSTEM-W-UNWIND, unwind currently in progress
         %TRACE-W-TRACEBACK, symbolic stack dump follows
         %SYSTEM-W-UNWIND, unwind currently in progress

          Images Affected:  [SYS$LDR]SYS$VM.EXE
                            [SYS$LDR]IMAGE_MANAGEMENT.EXE
                            [SYS$LDR]IMAGE_MANAGEMENT.STB
                            [SYS$LDR]SYSTEM_PRIMITIVES.EXE
                            [SYS$LDR]SYSTEM_PRIMITIVES_MIN.EXE
                            [SYS$LDR]SYSTEM_PRIMITIVES.STB
                            [SYS$LDR]SYSTEM_PRIMITIVES_MIN.STB
                            [SYSEXE]INSTALL.EXE
                            [SYSLIB]IMGDMP.EXE
                            [SYSLIB]SDA$SHARE.EXE


  o  A call to $GETJPI to  return  information  about  the  calling
     process  could return a SS$_NOPRIV status if that call is made
     while a persona representing a security profile  that  differs
     from the natural persona (Persona_ID 1) is active.

          Images Affected:  [SYS$LDR]PROCESS_MANAGEMENT.EXE
                            [SYS$LDR]PROCESS_MANAGEMENT_MON.EXE
                            [SYS$LDR]PROCESS_MANAGEMENT.STB
                            [SYS$LDR]PROCESS_MANAGEMENT_MON.STB


  o  Under the following circumstances:

       o  The system is a GS80, GS160, or GS320.

       o  The SYSGEN parameter RAD_SUPPORT has bit 2  set,  enabling
          system space replication.

       o  The SYSGEN parameter GH_RSRVPGCNT is  set  to  a  non-zero
          value.

     The  system  can  crash  with  an   INVEXCEPTN   bugcheck   at
     LDR_STD$DEALLOC_S2_VA_C+006C4.

          Images Affected:  [SYS$LDR]SYSTEM_PRIMITIVES.EXE
                            [SYS$LDR]SYSTEM_PRIMITIVES_MIN.EXE
                            [SYS$LDR]SYSTEM_PRIMITIVES.STB
                            [SYS$LDR]SYSTEM_PRIMITIVES_MIN.STB


  o  Applications that make a call to the  $SNDOPR  system  service
     can  get  a SS$_MBFULL return status.  For example, Oracle/Rdb
     applications can fail with the following error:

             %COSI-F-UNEXPERR, unexpected system error
             -SYSTEM-W-MBFULL, mailbox is full

          Images Affected:  [SYS$LDR]SYSTEM_PRIMITIVES.EXE
                            [SYS$LDR]SYSTEM_PRIMITIVES_MIN.EXE
                            [SYS$LDR]SYSTEM_PRIMITIVES.STB
                            [SYS$LDR]SYSTEM_PRIMITIVES_MIN.STB


  o  It is possible to sometimes  get  an  INVEXCEPTN  bugcheck  at
     SCH$QEND_C+001E0 during quantum end processing.

     Crashdump Summary Information:
     ------------------------------
     Bugcheck Type:    INVEXCEPTN, Exception while
                       above ASTDEL
     Current Process:
     Current Image:    
     Failing PC:       FFFFFFFF.800CFB50  SCH$QEND_C+001E0
     Failing PS:       10000000.00000804
     Module:           PROCESS_MANAGEMENT (Link Date/Time:
                       23-JAN-2001 08:37:04.46)
    Offset:            00007B50

          Images Affected: [SYS$LDR]PROCESS_MANAGEMENT.EXE
                           [SYS$LDR]PROCESS_MANAGEMENT_MON.EXE
                           [SYS$LDR]PROCESS_MANAGEMENT.STB
                           [SYS$LDR]PROCESS_MANAGEMENT_MON.STB


  o  If PERFMON interrupts are not turned off for PCTR0, PCTR1  and
     PCTR2  during  BUGCHECK,  and on any STOP/CPU, severe hangs in
     the console can occur.  It could take a power cycle  to  clear
     the situation.

          Images Affected:  [SYS$LDR]EXCEPTION.EXE
                            [SYS$LDR]EXCEPTION.EXE
                            [SYS$LDR]EXCEPTION_MON.EXE
                            [SYS$LDR]EXCEPTION_MON.STB
                            [SYS$LDR]SYSTEM_SYNCHRONIZATION.EXE
                            [SYS$LDR]SYSTEM_SYNCHRONIZATION_UNI.EXE
                            [SYS$LDR]SYSTEM_SYNCHRONIZATION_MIN.EXE
                            [SYS$LDR]SYSTEM_SYNCHRONIZATION.STB
                            [SYS$LDR]SYSTEM_SYNCHRONIZATION_UNI.STB
                            [SYS$LDR]SYSTEM_SYNCHRONIZATION_MIN.STB

  o  When using the SYS$WAKE system service, if a PID  or  username
     for  a  process  on a remote node is specified, a SS$_IVLOGNAM
     error will be returned.

          Images Affected:  [SYS$LDR]SYS$CLUSTER.EXE
                            [SYS$LDR]PROCESS_MANAGEMENT.EXE
                            [SYS$LDR]PROCESS_MANAGEMENT_MON.EXE
                            [SYS$LDR]PROCESS_MANAGEMENT.STB
                            [SYS$LDR]PROCESS_MANAGEMENT_MON.STB


  o  The  system  can  crash  with  a  INVSECURESTATE  bugcheck  at
     NSA$DEREFERENCE_RIGHTS_CHAIN_C+0008C

     Crashdump Summary Information
     -----------------------------

     Bugcheck Type:     INVSECURESTATE, Invalid state detected by
                        SECURITY subsystem
     Current Process:   YERTLE$SRV73
     Current Image:     DSA20:[SYS0.SYSCOMMON.]
                        [SYSEXE]OAFC$SERVER.EXE
     Failing PC:        FFFFFFFF.8019798C
                        NSA$DEREFERENCE_RIGHTS_CHAIN_C+0008C
     Failing PS:        30000000.00000203
     Module:            SECURITY_MON (Link Date/Time:
                        17-OCT-2001 01:01:12.57)
     Offset:            0000B98C

          Images Affected:  [SYS$LDR]SECURITY.EXE
                            [SYS$LDR]SECURITY_MON.EXE
                            [SYS$LDR]SECURITY.STB
                            [SYS$LDR]SECURITY_MON.STB


  o  The system can crash  with  a  KRNLSTAKNV,  Kernel  stack  not
     valid, bugcheck"

     Crashdump Summary Information:
     ------------------------------
     Bugcheck Type:     KRNLSTAKNV, Kernel stack not valid
     Current Process:
     Current Image:     
     Failing PC:        FFFFFFFF.800243A8
                        SMP$BUGCHK_HALT_CPU_C+001F8
     Failing PS:        00000000.00001F00
     Module:            SYS$CPU_ROUTINES_2208 (Link Date/Time:
                        17-MAR-2001 03:15:26.81)
     Offset:            000163A8

          Images Affected:  [SYS$LDR]PROCESS_MANAGEMENT.EXE
                            [SYS$LDR]PROCESS_MANAGEMENT_MON.EXE
                            [SYS$LDR]PROCESS_MANAGEMENT.STB
                            [SYS$LDR]PROCESS_MANAGEMENT_MON.STB



INSTALLATION NOTES:

This kit requires a system reboot.  HP strongly recommends that a
reboot is performed immediately after kit installation to avoid
system instability

If you have other nodes in your OpenVMS cluster, they must also be
rebooted in order to make use of the new image(s).  If it is not
possible or convenient to reboot the entire cluster at this time, a
rolling re-boot may be performed.


INSTALLATION INSTRUCTIONS:

Install this kit with the POLYCENTER Software installation utility
by logging into the SYSTEM account, and typing the following at the
DCL prompt:

  PRODUCT INSTALL VMS73_SYS /SOURCE=[location of Kit]

The kit location may be a tape drive, CD, or a disk directory that
contains the kit.

Additional help on installing PCSI kits can be found by typing
  HELP PRODUCT INSTALL at the system prompt

SPECIAL INSTALLATION INSTRUCTIONS:

  o  Scripting of Answers to Installation Questions

     During installation, this kit will ask and require user
     response to several questions.  If you wish to automate the
     installation of this kit and avoid having to provide responses
     to these questions, you must create a DCL command procedure
     that includes the following definitions and commands:

           -  $ DEFINE/SYS NO_ASK$BACKUP TRUE

           -  $ DEFINE/SYS NO_ASK$REBOOT TRUE

           -  Add the following qualifiers to the PRODUCT INSTALL
              command and add that command to the DCL procedure.

                /PROD=DEC/BASE=AXPVMS/VER=V6.0


           -  De-assign the logicals assigned

          For example, a sample command file to install the
          VMS73_SYS-V0600 kit would be:

          $
          $ DEFINE/SYS NO_ASK$BACKUP TRUE
          $ DEFINE/SYS NO_ASK$REBOOT TRUE
          $!
          $ PROD INSTALL VMS73_SYS/PROD=DEC/BASE=AXPVMS/VER=V6.0
          $!
          $ DEASSIGN/SYS NO_ASK$BACKUP
          $ DEASSIGN/SYS NO_ASK$REBOOT
          $!
          $ exit

All trademarks are the property of their respective owners.
 
Files on this server are as follows:
»dec-axpvms-vms73_sys-v0600--4.README
»dec-axpvms-vms73_sys-v0600--4.CHKSUM
»dec-axpvms-vms73_sys-v0600--4.pcsi-dcx_axpexe
privacy statement using this site means you accept its terms