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 VMS731_SYS-V0300 Alpha V7.3-1 System ECO Summary
TITLE: OpenVMS VMS731_SYS-V0300 Alpha V7.3-1 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:       04-MAR-2003
Modification Date:  Not Applicable
Modification Type:  NEW KIT

Copyright (c) Compaq Computer Corporation 2002,2003.  All rights reserved.

OP/SYS:     OpenVMS Alpha

COMPONENT:  SYSTEM

SOURCE:     Compaq Computer Corporation

ECO INFORMATION:

     ECO Kit Name:  VMS731_SYS-V0300
                    DEC-AXPVMS-VMS731_SYS-V0300--4.PCSI
     ECO Kits Superseded by This ECO Kit: VMS731_SYS-V0200
     ECO Kit Approximate Size:  18880 Blocks
     Kit Applies To: OpenVMS Alpha V7.3-1
     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:

         None.

       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-1.  
This kit addresses the following problems:


PROBLEMS ADDRESSED IN VMS731_SYS-V0300 KIT


      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  After applying VMS731_SYS-V0200 patch kit, threaded processes
         calling LIB$SPAWN without specifying the flag of NOWAIT can
         hang in HIBernation state in supervisor mode.  The user AST
         queue (PCB$L_ASTQFL_U) will have the PCB$L_WAKE_ACB queued to
         it, waiting to be delivered, but blocked by the higher mode.

         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  An ANALYZE/PROCESS command can result in the following error:

            %SDA-W-EXCLDATA, data excluded from dump due to
            insufficient privilege


         Images Affected:[SYSLIB]IMGDMP.EXE
			 [SYSLIB]SDA$SHARE.EXE



      o  When analyzing a process dump produced using DCL "SET
         PROCESS/DUMP=NOW", the "DBG> SHOW CALLS" command gives no
         useful information.  Only system call frames are displayed.

         Images Affected:[SYSLIB]IMGDMP.EXE



      o  Using JAVA, an attempt to merge activate an image using a
         logical name, in a secondary kernel thread, access violates
         with a system service exception.  The exception is due to
         accessing a stale context pointer.  If that shareable image is
         then dynamically invoked with lib$find_image_symbol, using a
         logical that points to a second logical which points to the
         image (an extra level of indirection), then the process gets
         deleted, causing the bugcheck.

         Images Affected:[SYS$LDR]IMAGE_MANAGEMENT.EXE



      o  There is a problem with dump compression that can cause lost
         data.  This is seen most often when trying to COPY/DECOMPRESS
         the dump, but it is also possible to get incorrect data out of
         the dump during analysis.  In addition, SDA can get stuck in a
         CPU-bound loop trying to COPY/DECOMPRESS certain dumps.

         Images Affected:[SYSLIB]IMGDMP.EXE
			 [SYSLIB]SDA$SHARE.EXE
			 [SYS$LDR]EXCEPTION.EXE
			 [SYS$LDR]EXCEPTION_MON.EXE
			 [SYS$LDR]EXCEPTION.STB
			 [SYS$LDR]EXCEPTION_MON.STB


      o  The layout of the dump header changed between OpenVMS V7.3 and
         V7.3-1.  Now, a DUMPEMPTY error is given rather than an
         INCDUMPFORM error.  Because of this the new SDA will not
         recognize old dumps and vice-versa.

         Images Affected:[SYSLIB]SDA$SHARE.EXE



      o  SDA overruns its buffer for storing page headings.  This leads
         to ACCVIOs.  

	 Images Affected:[SYSLIB]SDA$SHARE.EXE


      o  SDA cannot traverse pool fragments spread across multiple RADs
         and does not always recognize VCRPs

         Images Affected:[SYSLIB]SDA$SHARE.EXE


      o  After installation of the VMS731_SYS-V0200 patch kit,
         uniprocessor systems experience numerous non-fatal INCONSTATE
         bugcheck errorlog entries.  Setting BUGCHECKFATAL to 1 to
         induce a crash indicates an INCONSTATE bugcheck at
         SYSDEVICE+0013A4.

         Crashdump Summary Information:
         ------------------------------
         Bugcheck Type:    INCONSTATE, Inconsistent I/O data base
         CPU Type:         AlphaServer 4100 5/300 2MB
         VMS Version:      V7.3-1
         Current Process:  NET$ACP
         Current Image:    DSA0:[SYS0.SYSCOMMON.][SYSEXE]NET$ACP.EXE;1
         Failing PC:       FFFFFFFF.801213A4  SYSDEVICE+013A4
         Failing PS:       00000000.00000B00
                                         ^ IPL = 11. .GT. 2
         Module:           SYSDEVICE (Link Date/Time:
                                     1-OCT-2002 16:16:21.09)
         Offset:           000013A4

         Note that the system only crashes if BUGCHECKFATAL is set.
         Otherwise, it will log non-fatal INCONSTATE bugcheck errorlog
         entries.

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



      o  When doing a SET PROCESS, if the process is not current, the
         null process's PTBR (Page Table Base Register) is used, which
         is -1.  This makes memory access very difficult in a full dump.

         Images Affected:[SYSLIB]SDA$SHARE.EXE


      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  An image dump does not save the ACBs (Asynchronous Control
         Block) associated with a kernel thread being dumped.

         Images Affected:[SYSLIB]IMGDMP.EXE



      o  SDA walks IMCBs (Image Control Blocks) and examines KFERES
         (Known File Entry section descriptor) structures connected to
         IMCBs when reading symbol files, symbolizing addresses, and
         executing the MAP or SHOW PROCESS/IMAGE[=ALL] commands.  If
         IMCBs and/or KFERESs are corrupt, SDA can fail in a myriad of
         ways, including a compute-bound loop.

         Images Affected:[SYSLIB]SDA$SHARE.EXE


      o  An SDA copy command can get stuck in a loop.  For Example:

         SYSTEM> mcr sda
         Enter name of dump file >
         %SDA-I-USEMASTER, accessing dump file via _$1$DGA6005:, 
         master member of shadow set _DSA18:

         OpenVMS (TM) Alpha system dump analyzer
         ...analyzing a compressed selective memory dump...

         Dump taken on 16-DEC-2002 15:41:58.44
         INVPTEFMT, Invalid page table entry format

         SDA> COPY $1$dga5011:[dump]INVPTEFMT_qtv18_16-dec.dmp
         Copy Status: copying block 35783 (of 2084576 total blocks)
         Copy Status: copying block 77566 (of 2084576 total blocks)
         Copy Status: copying block 129423 (of 2084576 total blocks)
         Copy Status: copying block 256423 (of 2084576 total blocks)
         Copy Status: copying block 429355 (of 2084576 total blocks)
         Copy Status: copying block 546703 (of 2084576 total blocks)
                              .
                              .
                              .


         Images Affected:[SYSLIB]SDA$SHARE.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-VMS731_SYS-V0200--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-1 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:

          o  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 occurrance of this problem is
             rare and can only occur if:

              -  A user program must use the asynchronous version of the
                 system call $BRKTHRU -- using the synchronous form,
                 $BRKTHRUW, prevents this)

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

              -  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  Mount verification can abort when a tape, mounted on a
         dual-path controller is dismounted.  For example:
 
         Mount a tape on a dual-path controller:

           SYSTEM>>> MOUNT/FOREIGN $2$MUA140:
           %MOUNT-I-MOUNTED, TEST mounted on _$2$MUA140: (MOUSE)
           SYSTEM>>> DISMOUNT $2$MUA140:

         The dismount will hang for TAPE_MVTIMEOUT seconds.  
         Show the device from another session:

         SYSTEM>>> SHOW DEVICE $2$MUA140:

           Device             Device      Error Volume Free   Trans Mnt
           Name               Status      Count Label  Blocks Count Cnt
           $2$MUA140: (MOUSE) MountVerify     0 TEST        0     1   0
                              mounted
                              dismount
                              cached alloc
                              foreign

         If TAPE_MVTIMEOUT expires the following message is received:

           %%%%%%  OPCOM  16-JAN-2003 12:12:14.87  %%%%%%
           Mount verification has aborted for device
           $2$MUA140: (MOUSE, CAT)

         Other symptoms are that the drive can not be mounted on another
         node using the secondary controller if mountverification has
         aborted.

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


PROBLEMS ADDRESSED IN VMS731_SYS-V0200 KIT


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

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



     o  The system can  crash  with  a  SSRVEXCEPT,  Unexpected  system
        service exception 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


         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  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.  For this problem to
        occur  there  has to be a lot of cluster-wide $GETJPI activity.
        A typical stack of the hung process looks like this:

         Process Stacks (on CPU 00)
         --------------------------
         Current Operating Stack (SUPERVISOR):
                00000000.7FFABD90 00000000.00000004
                00000000.7FFABD98 00000000.00000000
                00000000.7FFABDA0 00000000.00000001
                00000000.7FFABDA8 00000000.00000002
         SP =>  00000000.7FFABDB0 00000000.0000001D
                00000000.7FFABDB8 00000000.7FFABEA4
                00000000.7FFABDC0 FFFFFFFF.98D490D0 SYS$SYNCH
                00000000.7FFABDC8 00000000.00000000
                00000000.7FFABDD0 00000000.00000002
                00000000.7FFABDD8 00000000.0000001D
                00000000.7FFABDE0 00000000.7FFABEA4
                00000000.7FFABDE8 00000000.7FFABE18
                00000000.7FFABDF0 00000000.00000000
                00000000.7FFABDF8 FFFFFFFF.DF2A59A8 RMS+299A8
                00000000.7FFABE00 00000000.7AF21AE0
                00000000.7FFABE08 00000000.7FFABE10
                00000000.7FFABE10 FFFFFFFF.DF3042E0  RMS+882E0
                00000000.7FFABE18 00000000.80814501  DECW$XMLIBSHR12+8E501
                00000000.7FFABE20 00000000.00010001  RMS$_SUC
                00000000.7FFABE28 FFFFFFFF.DF2A6764  SYS$FLUSH_C+000A0
                00000000.7FFABE30 FFFFFFFF.DF304560  SYS$FLUSH
                00000000.7FFABE38 00000000.7FFABEE0
                00000000.7FFABE40 00000000.00000000
                00000000.7FFABE48 00000000.7FFABE50
                00000000.7FFABE50 FFFFFFFF.DF304560  SYS$FLUSH
                00000000.7FFABE58 00000000.7FFABE9C
                00000000.7FFABE60 00000003.0000001D
                00000000.7FFABE68 00000004.00018001  RMS$_STALL
                00000000.7FFABE70 00000000.7AF4FB64
                00000000.7FFABE78 00000000.00000000
                00000000.7FFABE80 00000000.7FFABEE0
                00000000.7FFABE88 00000000.7AF21AE0
                00000000.7FFABE90 00000000.0000000E
                00000000.7FFABE98 80814401.7FFAC4E2  DECW$XMLIBSHR12+8E401
                00000000.7FFABEA0 01000000.00000000  PTE$M_TYP0
                00000000.7FFABEA8 00000000.00000000
                00000000.7FFABEB0 00000000.00000000
                00000000.7FFABEB8 00000000.00000000
                00000000.7FFABEC0 00000000.00000000
                00000000.7FFABEC8 00000000.00000000
                00000000.7FFABED0 00000000.00000000
                00000000.7FFABED8 00000000.00000000
                00000000.7FFABEE0 00000000.7AF21AE0
                00000000.7FFABEE8 00000000.00000000
                00000000.7FFABEF0 00000000.03C2834A
                00000000.7FFABEF8 FFFFFFFF.800F6AD0  EXE$AST_RETURN
                00000000.7FFABF00 00000000.00000002
                00000000.7FFABF08 00000000.00040428  XZA_XPCCTRL_M_RESBSY+
                00000000.7FFABF10 00000000.0000FF80  DAP$K_CTLMENU_I+00070
                00000000.7FFABF18 00000000.00000000
                00000000.7FFABF20 00000000.00011480  V_SMP$BUGCHK_HALT_CPU
                00000000.7FFABF28 00000000.00040128  XZA_XPCCTRL_M_RESBSY+
                00000000.7FFABF30 FFFFFFFF.98D48940  EXEC_ASTDEL_C
                00000000.7FFABF38 00000000.7FFABF40
                00000000.7FFABF40 FFFFFFFF.98D48940  EXEC_ASTDEL_C
                00000000.7FFABF48 00000000.00000000
                00000000.7FFABF50 FFFF8000.00000000
                00000000.7FFABF58 FFFFFFFF.98D490D0  SYS$SYNCH
                00000000.7FFABF60 00000000.00040088  XZA_XPCCTRL_M_RESBSY+
                00000000.7FFABF68 00000000.7AE55330
                00000000.7FFABF70 00000000.00000001
                00000000.7FFABF78 40A03800.00000000
                00000000.7FFABF80 00000000.0000002B
                00000000.7FFABF88 40000000.00000000  IRP$M_FILE_FLUSH
                00000000.7FFABF90 00000000.00000000
                00000000.7FFABF98 00000000.00000000

       There are signs of SYS$FLUSH code on  the  stack,  as  well  as
       pieces  of AST delivery.  Most of the time, the flush occurs on
       a batch logfile, but other flush operations may suffer as well.

         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  A system that supports NUMA and  has  RAD_SUPPORT  enabled  can
        crash  with  bugcheck  code  INVEXCEPTN 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 
		  	 [SYS$LDR]SYS$VM.STB



     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.

        The DCL command $ SET VOLUME/REBUILD is an example of this,  as
        well   as   a   lookup   via   the   runtime  library  function
        LIB$FIND_IMAGE_SYMBOL.  For example:

         $ SHOW DEVICE $8$DUA10

         Device               Device         Error  Volume
         Name                 Status         Count  Label  

         $8$DUA10: (UTRAMP)   Mounted Alloc  0      TEST1 

         Free     Trans   Mnt
         Blocks   Count   Cnt

         2050506      1     1

         $ 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

         This happens if we get DDB's (Device Data Block)  organized  in
         this way:

         System: UTRAMP
         DDB:    DUA   UCB: 00000000 2P_UCB: 00000000 Alloclass:   0
         DDB:    DIA   UCB: 80DCEE40 2P_UCB: 00000000 Alloclass:   8
         DDB:    DUA   UCB: 80DCDD00 2P_UCB: 00000000 Alloclass:   8
         DDB:    MUA   UCB: 80E8E280 2P_UCB: 00000000 Alloclass:   0


         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  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
			 [SYS$LDR]SYSLDR_DYN.STB



     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  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
			 [SYS$LDR]SHELL8K.STB



     o  Nonpaged pool usage may increase over time due  to  a  leak  of
        process control blocks (PCB).  This leak only occurs under very
        specific circumstances which are not that common  and  it  only
        affects  NUMA platforms with RAD_SUPPORT enabled.  The platform
        has to be "sub-optimally" configured with RADs without  private
        memory.

         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 may crash with a INVTQEFMT bugcheck during an insert
        of a timer queue element (TQE).

         Crashdump Summary Information:
         ------------------------------
         Bugcheck Type:     INVTQEFMT, Invalid time queue entry
                            format
         Failing PC:        FFFFFFFF.8004AB60 EXE_STD$TIMEOUT_C+006A0
         Failing PS:        10000000.00000800
         Module:            SYSTEM_PRIMITIVES_MIN  (Link Date/Time:
                            18-JUL-2002 20:01:15.20)
         Offset:            00020B60

         Failing Instruction:
         EXE_STD$TIMEOUT_C+006A0:    BUGCHK

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


     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  In the following scenario, a  process  can  be  deleted,  as  a
        result of an EXEC mode system service exception.


         1.  Statically linked to a shareable image.

         2.  That   image   is    then    dynamically    invoked    with
             lib$find_image_symbol  using  a  logical  that  points to a
             second logical.

         3.  The second logical points to the image (an extra  level  of
             indirection)


         Images Affected:[SYS$LDR]IMAGE_MANAGEMENT.EXE



     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  Under certain conditions, a process waiting on a mutex may  not
        be  woken  up  when  the mutex is unlocked.  This can result in
        application performance issues.

         Images Affected:[SYS$LDR]SYSTEM_PRIMITVES.EXE
			 [SYS$LDR]SYSTEM_PRIMITVES.STB
			 [SYS$LDR]SYSTEM_PRIMITVES_MIN.EXE
			 [SYS$LDR]SYSTEM_PRIMITVES_MIN.STB



     o  Currently,  the  fairness  algorithm  only  applies  to  static
        spinlocks,  but  ignores dynamic spinlocks and portlocks.  This
        is becoming a serious performance issue now with more and  more
        dynamic spinlocks in use (XFC, TCPIP etc.).

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


     o  The system can crash with an INCONSTATE, Inconsistent I/O  data
        base bugcheck.

         Crashdump Summary Information
         -----------------------------
         Bugcheck Type:     INCONSTATE, Inconsistent I/O data base
         Failing PC:        FFFFFFFF.802F2224    SYS$VCC+0C224
         Failing PS:        28000000.00000804
         Module:            SYS$VCC    (Link Date/Time:
                            18-JUL-2002 20:09:40.91)
         Offset:            0000C224


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


     o  With TCPIP and LAN becoming fastpath capable, we will now  have
        fastpath  related  routines being called and passed in a cloned
        UCB.  The DCL command $ SET  DEVICE/PREFER=x  BG0  is  such  an
        example, as it intends to change the fastpath preferred CPU for
        the template device, but gets a channel assigned  to  a  cloned
        UCB.   Currently  it is hard to figure out, if a given UCB is a
        cloned  UCB  or  not.   This  leads  to  a   degradation.    in
        performance.

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


     o  Systems  with  heavy  mailbox  activity   experience   a   high
        contention  on  the  static MAILBOX spinlock, namely in routine
        EXE$CANCEL.  T his results in a performance degradation.

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


     o  Additional SMP performance improvements to cut  down  on  SCHED
        spinlock contention.

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


     o  A system can crash with an INVEXCEPTN,  Exception  while  above
        ASTDEL

         Crashdump Summary Information:
         ------------------------------
         Bugcheck Type:     INVEXCEPTN, Exception while above
                            ASTDEL
         Failing PC:        FFFFFFFF.800BAAFC SMP$ACQUIREL_C+0002C
         Failing PS:        38000000.00000801
         Module:            SYSTEM_SYNCHRONIZATION (Link Date/Time:
                            18-JUL-2002 20:07:57.50)
         Offset:            0002EAFC

         Failing Instruction:
         RMS+56630:      LDL             R26,#X0008(R6)


         Images Affected:[SYSLDR]LOCKING.EXE
			 [SYSLDR]LOCKING.STB



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

         Crashdump Summary Information:
         ------------------------------
         Bugcheck Type:     INVEXCEPTN, Exception while above ASTDEL
         Current Process:   NULL
         Current Image:     
         Failing PC:        FFFFFFFF.8058E630    RMS+56630
         Failing PS:        10000000.00000804
         Module:            RMS    (Link Date/Time:
                            18-JUL-2002 19:59:04.73)
         Offset:            00056630


         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  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
			 [SYS$LDR]PROCESS_MANAGEMENT_MON.STB



     o  Usnig JAVA, an attempt to  merge  activate  an  image  using  a
        logical name, in a secondary kernel thread, will access violate
        due to an access to a stale context pointer.  If the  shareable
        image  is dynamically invoked with lib$find_image_symbol, using
        a logical that points to a second logical, which points to  the
        image (an extra level of indirection), the process gets deleted
        (bug check with system service exception).

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


FUNCTIONALITY ADDRESSED IN VMS731_SYS-V0100

     o  This kit  supports  OpenVMS  Alpha  Version  7.3-1  and  Alpha
        systems  running Alpha Firmware Version 6.3.  Install this kit
        if you plan to use  CPU  migration.   In  addition,  this  kit
        introduces Hot Add and extended Hot Swap features with OpenVMS
        Version 7.3-1.

        After kit installation, information  describing  this  support
        can be found in the following files:

          o  [SYSHLP]V63_FIRMWARE_SUPPORT.PDF

          o  [SYSHLP]V63_FIRMWARE_SUPPORT.TXT


        To access these files before the kit is installed, execute the
        following commands:

          PRODUCT EXTRACT FILE VMS731_SYS/SELECT=V63_FIRMWARE_SUPPORT.PDF
          PRODUCT EXTRACT FILE VMS731_SYS/SELECT=V63_FIRMWARE_SUPPORT.TXT

INSTALLATION NOTES:

This kit requires a system reboot.  Compaq 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 VMS731_SYS /SOURCE=[location of Kit]

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

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=V3.0


           -  De-assign the logicals assigned

        For  example,  a  sample   command   file   to   install   the
        VMS731_SYS-V0300 kit would be:

          $
          $ DEFINE/SYS NO_ASK$BACKUP TRUE
          $ DEFINE/SYS NO_ASK$REBOOT TRUE
          $!
          $ PROD INSTALL VMS731_SYS/PROD=DEC/BASE=AXPVMS/VER=V3.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-vms731_sys-v0300--4.README
»dec-axpvms-vms731_sys-v0300--4.CHKSUM
»dec-axpvms-vms731_sys-v0300--4.pcsi-dcx_axpexe
privacy statement using this site means you accept its terms