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

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

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

connection tools
» nameserver lookup
» traceroute
» ping


Find Support Information and Customer Communities for Presario.
Content starts here
HP Services Software Patches - alpqman04_070
 
NOTE:  An OpenVMS saveset or PCSI installation file is stored
       on the Internet in a self-expanding compressed file.
       The name of the compressed file will be kit_name-dcx_vaxexe
       for OpenVMS VAX or kit_name-dcx_axpexe for OpenVMS Alpha.
 
       Once the file is copied to your system, it can be expanded
       by typing RUN compressed_file.  The resultant file will
       be the OpenVMS saveset or PCSI installation file which
       can be used to install the ECO.
 

Copyright (c) Digital Equipment Corporation 1997, 1998.  All rights reserved.

                             SUPERSESSION NOTE

Until January 28, 1998 this kit contained fixes for OpenVMS Alpha V6.1,
V6.1-1H1, V6.1-1H2, V6.2, V6.2-1H1, V6.2-1H2, V6.2-1H3, and V7.0.  The
fixes for OpenVMS Alpha V6.1x have been moved to ALPQMAN04_061 and
the fixes for V6.2x have been moved to ALPQMAN02_062.  If you need the
fixes for those versions, please use the updated kits.

If you need fixes for OpenVMS Alpha V7.0, this kit, ALPQMAN04_070, is
still the functional kit.  Engineering is in the process of preparing 
a new ALPQMAN05_070 kit which will contain only the fixes for V7.0.

There are fixes for OpenVMS Apha V7.1 in ALPQMAN01_071.


PRODUCT:    DIGITAL OpenVMS Alpha

COMPONENT:  Queue Manager

SOURCE:     Digital Equipment Corporation

ECO INFORMATION:

     ECO Kit Name:  ALPQMAN04_070
     ECO Kits Superseded by This ECO Kit:  ALPQMAN03_070
                                           ALPQMAN02_070                      
                                           ALPQMAN01_070                      
                                           ALPQMAN01_062                      
                                           AXPQMAN03_061 (AXPQMAN)            
                                           AXPJOBC01_061 (CSCPAT_2087 V1.2)   
                                             This kit was never released.     
                                           AXPQMAN01_061 (CSCPAT_2087 V1.1)   
                                           AXPPRTS01_061 (CSCPAT_2087 V1.0)   

     ECO Kit Approximate Size:  4410 Blocks
                    Saveset A -  198 Blocks
                    Saveset B - 1404 Blocks
                    Saveset C - 1584 Blocks
                    Saveset D - 1224 Blocks

     Kit Applies To:  OpenVMS Alpha V6.1, V6.1-1H1, V6.1-1H2,                 
                                    V6.2, V6.2-1H1, V6.2-1H2, 6.2-1H3         
                                    V7.0                                      
     System/Cluster Reboot Necessary:  Yes

     Installation Rating:  3 - To be installed on all systems running
                               the listed versions of OpenVMS which
                               are experiencing the problems described.

     NOTE:  In order to receive the full fixes listed in this kit,
            the following remedial kits also need to be installed:

                 None


ECO KIT SUMMARY:

An ECO kit exists for Queue Manager OpenVMS Alpha V6.1 through V7.0.
This kit addresses the following problems:

Problems addressed in ALPQMAN04_070 for OpenVMS Alpha V6.1, V6.1-1H1,
  V6.1-1H2, V6.2, V6.2-1H1, V6.2-1H2, V6.2-1H3, and V7.0:

  o  Being re-issued to keep Message Routines current with Library
     RTL kit.  There are no new fixes in this kit.


Problems addressed in ALPQMAN03_070 for OpenVMS Alpha V6.1, V6.1-1H1,
  V6.1-1H2, V6.2, V6.2-1H1, V6.2-1H2, V6.2-1H3, and V7.0:

  o  The ALPQMAN02_070 remedial kit would not install on V6.1 and
     V6.2 OpenVMS Alpha hardware versions.  There are no additional
     problem fixes in this remedial kit.


Problems addressed in ALPQMAN02_070 for OpenVMS Alpha V6.1, V6.1-1H1,
  V6.1-1H2, V6.2, V6.2-1H1, V6.2-1H2, V6.2-1H3, and V7.0:

  o  Delete/Entry on a starting job fails to stop the job.  The job
     stays in an aborting state and processes to completion.

  o  When F$GETQUI is used at DCL to obtain queue manager information,
     certain combinations of items can hang the process.

  o  The queue manager stops after the following messages are
     issued in OPCOM:

       %%%%%%%%%%%  OPCOM   8-MAY-1996 14:52:17.83  %%%%%%%%%%%
       Message from user QUEUE_MANAGE on HULAW3
       %QMAN-W-LOWMEMORY, the queue manager process may require more
       virtual memory  than is currently available

       %%%%%%%%%%%  OPCOM   8-MAY-1996 14:53:07.20  %%%%%%%%%%%
       Message from user QUEUE_MANAGE on HULAW3
       %QMAN-F-ALLOCMEM, error allocating virtual memory

       %%%%%%%%%%%  OPCOM   8-MAY-1996 14:53:07.24  %%%%%%%%%%%
       Message from user QUEUE_MANAGE on HULAW3
       -LIB-F-INSVIRMEM, insufficient virtual memory

Problems addressed in ALPQMAN01_070 for OpenVMS Alpha V6.1, V6.1-1H1,
  V6.1-1H2, V6.2, V6.2-1H1, V6.2-1H2, V7.0:

  o  LATSYM symbiont processes run with less than the maximum
     number of queues assigned.

NOTE:  According to OpenVMS Engineering, the fixes discussed 
       below have been included in OpenVMS Alpha V7.0.
       There are some fixes that have been included in previous
       versions of OpenVMS and those versions are specified in
       text following the problem descriptions.

Problems addressed in ALPQMAN01_062 for OpenVMS Alpha V6.2:

  o  Queue System Response is sporadically slow.  This reduction
     in performance occurs most frequently on systems with many
     queues and forms.  On large production systems, the delays
     may become severe if the problem occurs during queue journal
     file checkpointing.  The Queue Manager may crash with a
     BADLOGIC error in the WILD_MASTER_NAME routine.

  o  An extra line feed occurs on the top of printouts for FORTRAN
     Carriage control files that contain a zero-length first record.

  o  The log files created via the 'SUBMIT/NOPRINT' command executed
     from within SYSTARTUP_VMS.COM are placed in the SYS$SYSTEM directory
     instead of the SYS$MANAGER directory as expected.  This is not
     consistent with the behavior of SYSTARTUP_VMS.COM on all previous
     versions of the operating system.

  o  The SYS$COMMON:[SYSEXE]SYS$QUEUE_MANAGER.QMAN$JOURNAL queueing
     system journal file extends to approximately 41,000 blocks
     after the upgrade from OpenVMS Alpha V6.1 to OpenVMS Alpha V6.2.

  o  With OpenVMS Alpha V6.2, a 'SUBMIT' command using a wildcard
     character fails to create a batch job.  This is a change in
     behavior from OpenVMS V6.1.

Problems addressed in ALPQMAN01_62 for OpenVMS Alpha V6.1,
  V6.1-1H1, V6.1-1H2, V6.2:

  o  Over time, the number of symbiont processes running on the
     system increases.

  o  When image accounting is enabled, the ASTCNT for a batch job
     grows from its initial setting, and the batch job subsequently
     fails with the following messages:

       RMS-F-BUG, Fatal RMS Condition, process deleted.
         R0  =  1C (EXQUOTA)
         R2 = FFFFFFF8 (CANTDOAST)

      Each time an image is activated and terminated in a batch
      process, the AST quota of the process is incremented by 1.


Problems addressed in AXPQMAN03_061:

  o  The unreleased AXPJOBC01_061 kit contained both QMAN and
     PRTSMB ECOs.  It superseded both AXPQMAN01_061 and
     AXPPRTS01_061.  This kit, AXPQMAN03_061, only replaces the
     the QMAN fixes from that combined kit.  The print symbiont
     and SMBSRVSHR fixes have been moved to the AXPPRTS02_061
     ECO kit.

  o  The queue name field is blank for batch accounting records
     on OpenVMS Alpha V6.1 systems after the application of
     AXPQMAN01_061.

  o  The accounting data reported by the DCL 'ACCOUNTING/SUMMARY/REPORT=PAGES'
     command is sometimes incorrect.  The incorrect data is reported
     after jobs are reprinted and occurs because the number of pages
     printed is accumulated in each separate accounting record
     instead of being overwritten.  For example:

         Print Seq     Acctng Record     ACCOUNTING/SUMMARY/REPORT=PAGES
          number              Pages Printed     Output
          ---------     --------------    -------------------------------
              1            3                       3
              2            6                       9
              3            9                      18

          The actual number of  pages printed by the user is nine but the
          summary accounting reports eighteen pages.

  o  At startup, the queue manager may dump with a BADLOGIC error
     in the WILD_MASTER_NAME routine ((PC 0000C67E on V6.1).  It
     is then necessary to recreate the queue manager to restart
     the queue system.

  o  QMAN Security fix.


Problems addressed in AXPJOBC01_061:

  o  The queue name field is blank for batch accounting records
     on OpenVMS Alpha V6.1 systems after the application of
     AXPQMAN01_061.


Problems addressed in AXPQMAN01_061:

  o  An extra line feed occurs on the top of printouts for FORTRAN
     Carriage control files that contain a zero-length first record.

  o  Queue System Response is sporadically slow.  This reduction
     in performance occurs most frequently on systems with many
     queues and forms.  On large production systems, the delays
     may become severe if the problem occurs during queue journal
     file checkpointing.  The Queue Manager may crash with a
     BADLOGIC error in the WILD_MASTER_NAME routine.

  o  The job controller process can crash due to access violations.

  o  A print job may go into a status of "pending" due to a stock type
     mismatch, even though the stock of the form on the print job
     matches the stock of the form mounted on the queue.  Following
     is an example of this error:

          $ SHOW QUEUE/FULL/ALL 332_m_1

          Terminal queue 332_M_1, idle, on UHAD6::LTA151:, mounted form
          DEFAULT/BASE_PRIORITY=3 /CHAR=(9) /DEFAULT=(FORM=DEFAULT)
          /NOENABLE_GENERIC/LIBRARY=UH_HPLASERJET Lowercase
          /OWNER=[VMS,SYSTEM]/PROCESSOR=LATSYM/PROTECTION=(S:M,O:D,G:M,W:RS)
          /SCHEDULE=(NOSIZE)/SEPARATE=(RESET=(RESET))

          Entry  Jobname     Username     Blocks  Status
          -----  -------     --------     ------  ------
          10960  TEST        SPARKS            1  Pending (stock type mismatch)
                 Submitted 23-JUN-1994 10:27 /FORM=DEFAULT/PRIORITY=100
                 File: _DSA0:[UHCOMMON.SHARON]TEST.TXT;2
          10962  TEST        SPARKS            1  Pending (stock type mismatch)
                 Submitted 23-JUN-1994 10:27 /FORM=NOMARGIN (stock=DEFAULT)
                 /PRIORITY=100
                 File: _DSA0:[UHCOMMON.SHARON]TEST.TXT;2

  o  The symbiont can dump with a BADLOGIC error in PSM$REPORT if a
     'STOP/QUEUE/RESET' is immediately followed by a 'START/QUEUE'
     command.  The queues managed by the failing symbiont are
     stopped and there is a loss of service.

  o  A 'SET QUEUE/ENTRY' DCL command for a non-existant queue causes
     the following error message to be displayed twice:

          %JBC-E-NOSUCHQUE, no such queue

  o  When the '$GETQUI' system service using the DISPLAY_JOB function
     and the THIS_JOB flag is called from a non-batch process, a
     JOBQUEDIS error is returned even when the queue manager is running.
     This problem also occurs when a process is spawned from a batch
     process.

  o  Memory that is allocated for storing output values for a
     'SHOW QUEUE/MANAGER' command is not deallocated after command
     completion.  If a user does a series of 'SHOW  QUEUE/MANAGER'
     commands the job controller may crash with an insufficient
     virtual memory error.

  o  Timed jobs are listed by priority, then by /AFTER_TIME.  Jobs
     with the same /AFTER_TIME are listed in entry number order,
     not in submit time order.  This fix causes a 'SHOW  QUEUE'
     command to list timed jobs in /AFTER_TIME order.


  o  Timed jobs of equal priority sometimes execute in submit order,
     not in the release time (/AFTER_TIME) order.  This happens when
     multiple jobs are pending execution.  In the example provided
     below, users expect the jobs to run in 1,3,2 order, not in the
     1,2,3 order.  The fix contained in this kit corrects the
     execution order.

          Time 12:00

            Entry  Jobname         Username         Status
            -----  -------         --------         ------
                1  LOGIN           SWEENEY          Executing
                3  LOGIN           SWEENEY          Holding until 12:30
                2  LOGIN           SWEENEY          Holding until 13:00

          Time 12:31

            Entry  Jobname         Username         Status
            -----  -------         --------         ------
                1  LOGIN           SWEENEY          Executing
                3  LOGIN           SWEENEY          Pending
                2  LOGIN           SWEENEY          Holding until 13:00

          Time 13:01

            Entry  Jobname         Username         Status
            -----  -------         --------         ------
                1  LOGIN           SWEENEY          Executing
                2  LOGIN           SWEENEY          Pending
                3  LOGIN           SWEENEY          Pending

          Entry number one finishes:

            Entry  Jobname         Username         Status
            -----  -------         --------         ------

            2  LOGIN           SWEENEY          Executing
            3  LOGIN           SWEENEY          Pending

  o  When the /DELETE qualifier is specified in the 'PRINT' command,
     the printed file is marked for deletion.  At job completion,the
     completion status is not checked before deleting the job.  There-
     fore, the file is deleted even if the print was unsuccessful.

  o  When a symbiont sends a TASK_STATUS request to the Queue
     Manager, and no job is active, then the request is rejected
     with the following message:

          Message from user QUEUE_MANAGE on ARDAS1

          %QMAN-I-INVSMBMSG, invalid data in message from symbiont
           on queue TEST is being ignored

  o  During a failover of the Queue Manager, if there are outstanding
     jobs, it is possible to get the system service error NOMOREPROC
     status.

  o  With latest print symbiont, All-In-1 users may experience a
     blank page between each job

  o  Issuing the 'PRINT/DELETE' command for many files (several
     thousand) causes the queue manager to crash with an ACCVIO.


INSTALLATION NOTES:

In order for the corrections in this kit to take effect, the system
must be rebooted.  If the system is a member of a VMScluster,
Files on this server are as follows:
»alpqman04_070.README
»alpqman04_070.CHKSUM
»alpqman04_070.CVRLET_TXT
»alpqman04_070.a-dcx_axpexe
»alpqman04_070.b-dcx_axpexe
»alpqman04_070.c-dcx_axpexe
»alpqman04_070.d-dcx_axpexe
privacy statement using this site means you accept its terms