Updated: 24-SEP-2003 (Use your browsers' Reload button to ensure you're viewing the most recent version)
ALPQMAN04_061 Alpha V6.1 - V6.1-1H2 Queue Manager ECO Summary
Copyright (c) Digital Equipment Corporation 1997, 1998. All rights reserved.
PRODUCT: DIGITAL OpenVMS Alpha
COMPONENT: Queue Manager
Job Controller
SOURCE: Digital Equipment Corporation
ECO INFORMATION:
ECO Kit Name: ALPQMAN04_061
ECO Kits Superseded by This ECO Kit: ALPQMAN04_070 (For OpenVMS Alpha
V6.1 *ONLY*)
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: 1602 Blocks
Kit Applies To: OpenVMS Alpha V6.1, V6.1-1H1, V6.1-1H2
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 V6.1-1H2.
This kit addresses the following problems:
Problems addressed in ALPQMAN04_061:
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 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.
Problems addressed in ALPQMAN04_070 for OpenVMS Alpha V6.1, V6.1-1H1,
V6.1-1H2:
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:
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:
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_62 for OpenVMS Alpha V6.1,
V6.1-1H1, and V6.1-1H2:
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.
RELATED ARTICLES:
Detailed articles describing the problems listed above may exist in
the OPENVMS database. To view these articles, open the appropriate
product database and perform a query using either of the following
search strings: 'ALPQMAN04_061' or 'ALPQMAN."
ECO KIT ORDERING INSTRUCTIONS:
If after an evaluation you wish to obtain this kit, request it
electronically using the appropriate Advanced Electronic Services
(AES) Service Tool. If you are not familiar with how to request
kits electronically, open the DIA, WIS or DSNLINK database and
review the article entitled:
[AES] How To Electronically Request ECO Kits Using Service Tools
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,
the entire cluster should be rebooted.
==========================================================================
| Table of Kit Image Information |
+----------------------------+----------+-----------------+--------------+
| | Overall | Image File | Image Link |
| Image Name | Checksum | Identification | Date/Time |
+----------------------------+----------+-----------------+--------------+
| JBC$JOB_CONTROL.EXE | D291B56F | X-20A1 | 6-AUG-1997 |
| | | 17:54:23.65 |
+----------------------------+----------+-----------------+--------------+
| MESSAGE_ROUTINES.EXE | A84AAECB | X-3 | 10-OCT-1997 |
| | | 10:35:23.69 |
+----------------------------+----------+-----------------+--------------+
| QMAN$QUEUE_MANAGER.EXE | FA042ECA | X-3 | 13-AUG-1996 |
| | | 12:19:46.66 |
+----------------------------+----------+-----------------+--------------+
|
