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
OpenVMS ALPQMAN02_071 Alpha V7.1 Que Manager/Job Controller ECO Summary
TITLE: OpenVMS ALPQMAN02_071 Alpha V7.1 Que Manager/Job Controller ECO Summary
 
Modification Date:  01-FEB-99
Modification Type:  Updated Kit:  Supersedes ALPQMAN01_071

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) Compaq Computer Corporation 1998, 1999.  All rights reserved.

OP/SYS:     DIGITAL OpenVMS Alpha

COMPONENT:  Queue Manager
            Job Controller

SOURCE:     Compaq Computer Corporation

ECO INFORMATION:

     ECO Kit Name:  ALPQMAN02_071
     ECO Kits Superseded by This ECO Kit:  ALPQMAN01_071
     ECO Kit Approximate Size:  1386 Blocks
     Kit Applies To:  OpenVMS Alpha V7.1, V7.1-1H1, V7.1-1H2
     System/Cluster Reboot Necessary:  Yes
     Rolling Reboot Supported:  Yes
     Installation Rating:  INSTALL_3
                           3 - To be installed on all systems running
                               the listed versions of OpenVMS which
                               are experiencing the problems described.

     Kit Dependencies:

       The following remedial kit(s) must be installed BEFORE
       installation of this kit:

         None 

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

         None 


ECO KIT SUMMARY:

An ECO kit exists for Queue Manager and Job Controller on OpenVMS
Alpha V7.1 through V7.1-1H2. This kit addresses the following problems:

Problems Addressed in the ALPQMAN02_071 kit:

  o  When booting in a new node or when starting up the Queue
     Manager, cluster nodes appeared to hang.  The job controller
     continually produced dump files at SYS$SYSTEM:JBC$JOB_CONTROL.DMP.   
     Also, the error reported in the dump file was "feature incompatible 
     with previous system version."

 o  Submitting a job to a batch queue, set up with a default
    protection, generated a CONTROL access audit alarm, even
    though the user did not request control access.  As a result,
    OPERATOR.LOG was flooded with security audit messages.  For
    example, doing $ SET AUDIT/CLASS=QUEUE/ALARM/ENA=ACCESS=FAIL:

          $ SUBMIT X.COM/QUE=TEST/NOLOG/NOTIFY

          %%%%%%%%%%%  OPCOM   3-MAR-1998 12:08:20.38  %%%%%%%%%%%

          Message from user AUDIT$SERVER on CHEN
          Security alarm (SECURITY) on CHEN, system id: 65422
          Auditable event:          Object access
          Event time:                3-MAR-1998 12:08:20.38
          PID:                      000000DF
          Source PID:               000000CE
          Username:                 USER
          Process owner:            [LASTNAMEO,FIRSTNAMEO]
          Object class name:        QUEUE
          Object name:              TEST
          Object owner:             [SYSTEM]
          Object protection:        SYSTEM:M, OWNER:D, GROUP:R, WORLD:S
          Access requested:         CONTROL
          Status:                   %SYSTEM-F-NOPRIV, insufficient 
                                     privilege or
                                     object protection violation

          Job X (queue TEST, entry 4) started on TEST
          $

          Job X (queue TEST, entry 4) completed

  o  Two spool problems occurred:

     1.  Files copied to a spooled device were not deleted from the
         spool area when its corresponding entry was deleted from
         the queue.

     2.  Prior to OpenVMS V6.2, a spooled batch queue could run
         without a problem, even if the command procedure was
         broken.  However, on OpenVMS V6.2 and OpenVMS V7.1, a
         broken command procedure passed to a spooled batch queue
         would result in lost files.

  o  An error can occur when the Default Form reference count is
     incremented in two similar circumstances:

     1.  The error can occur while batch queues are being created.

     2.  It can also occur when generic queues are initialized.

     Changing the stock on the DEFAULT form can result in an error,
     even when there are no references (jobs, queues, ...) to the
     DEFAULT form.  The following error was observed:

       $DEFINE/FORM /STOCK=NEW_STOCK DEFAULT 0
       %JBC-E-STKNOTCHANGE, the stock associated with a form

     NOTE:

       If a customer uses multiple Queue Managers on a system, ALL
       Queue Managers must be running in order for a form update to
       occur.  If all Queue Managers are not running, the
       STKNOTCHANGE error will occur.


Problems Addressed in the ALPQMAN01_071 kit:

  o  BATCH/PRINT problems corrected:

     +  The DCL command SHOW QUEUE/MANAGER would hang on some
        nodes.  The job controller process would hang in the LEF
        state.

     +  After queue manager failover from VAX to Alpha, the job
        controller process (on Alpha) hangs in LEF causing the
        queues on the Alpha system to remain in a starting state.
        The queues remain there until the job controller is
        stopped and restarted.  Also, the SHOW  QUEUE/MANAGER
        command hangs.

  o  When SJC$_DELETE_FILE_ALWAYS deletes a print job created
     through PATHWORKS, the spool file is not always deleted.
     It deletes only when the job is in execution state.

  o  When booting in a new node or failing over the queue manager,
     the cluster appears to hang.  The job controller continually
     produces dump files at SYS$SYSTEM:JBC$JOB_CONTROL.DMP.  The
     error reported in the dump is "feature incompatible with
     previous system version".

  o  DCPS-F-STREAMUSE and queue become stuck in starting errors:

     +  Occasional flagging of a DCPS-F-STREAMUSE error while
        starting DCPS queues.

     +  Print Queues (either LAT, DQS or DCPS) may hang stuck in a
        starting state.


INSTALLATION NOTES:

The images in this kit will not take effect until the system is
rebooted.

If you have other nodes in your OpenVMS cluster, they must also be
rebooted in order to make use of the new image.  If it is not
possible or convenient to reboot the entire cluster at this time, a
rolling re-boot may be performed.
Files on this server are as follows:
»alpqman02_071.README
»alpqman02_071.CHKSUM
»alpqman02_071.CVRLET_TXT
»alpqman02_071.a-dcx_axpexe
privacy statement using this site means you accept its terms