|
|
 |
OpenVMS VAXQMAN04_061 VAX V6.1 Queue Manager ECO Summary
|
TITLE: OpenVMS VAXQMAN04_061 VAX V6.1 Queue Manager ECO Summary
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.
*OpenVMS] VAXQMAN04_061 VAX V6.1 Queue Manager ECO Summary
Copyright (c) Digital Equipment Corporation 1997, 1998. All rights reserved.
OP/SYS: DIGITAL OpenVMS VAX
COMPONENT: Queue Manager
Job Controller
SOURCE: Digital Equipment Corporation
ECO INFORMATION:
ECO Kit Name: VAXQMAN04_061
ECO Kits Superseded by This ECO Kit: VAXQMAN03_070 (For OpenVMS VAX
V6.1 *ONLY*)
VAXQMAN02_070
VAXQMAN01_070
VAXQMAN01_062
VAXQMAN03_061
VAXQMAN02_061
VAXQMAN01_061 (CSCPAT_1176)
VAXQMAN02_060
VAXQMAN01_060 (CSCPAT_1175)
VAXQMAN8_U2055
VAXQMAN07_U2055 (CSCPAT_1165)
VAXQMAN06_U2055
VAXQMAN05_U2055
VAXQMAN04_U2055
VAXQMAN03_U2055
QMAN$02_U2055
QMAN$01_U2055
ECO Kit Approximate Size: 630 Blocks
Kit Applies To: OpenVMS VAX V6.1
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 (patch) kit exists for the Queue Manager and Job Controller
on OpenVMS VAX V6.1. This kit addresses the following problems:
Problems addressed in VAXQMAN04_061 for OpenVMS VAX V6.1:
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 VAXQMAN03_070 for OpenVMS VAX V6.1:
o Being re-issued to keep Message Routines current with Library
RTL kit. There are no new fixes in this kit.
Problems addressed in VAXQMAN02_070 for OpenVMS VAX V6.1:
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 process 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 VAXQMAN01_070 for OpenVMS VAX V6.1:
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 VAX 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.
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 VAXQMAN03_061 for OpenVMS VAX V6.1:
o VAXQMAN02_061 and previous VAXQMAN ECO kits contained both QMAN
(queue manager, job controller) and PRTSMB (print symbiont) fixes.
This ECO kit, VAXQMAN03_061, contains only the QMAN fixes and
supersedes only that portion of the previous kits. The PRTSMB
fixes have been moved to a new kit, VAXPRTS01_061, which
supersedes the PRTSMB portion of the previous kits.
o The accounting data reported by the DCL command
'ACCOUNTING/SUMMARY/REPORT=PAGES' command is not always correct.
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. After this occurs, it is necessary
to recreate the queue manager to restart the queue system.
o QMAN security fix.
Problems addressed in VAXQMAN02_061 for OpenVMS VAX V6.1:
o If a 'START/QUEUE' DCL command is immediately followed by a
'STOP/QUEUE/RESET' DCL command, the symbiont may dump with a
BADLOGIC error in PSM$REPORT. The queues managed by the failing
symbiont are stopped and there is a loss of service.
o A print job may have 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. See the
following example:
$ 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 job controller process can crash due to access violations.
o The 'SHOW/QUEUE/FORM' DCL command does not terminate the
form/char name search correctly. This might cause the
QMAN$MASTER.DAT file to be locked for unnecessarily
long periods which causes queue system response to be
intermittently slow. This occurs particularly on systems
with many queues and forms. On large production systems,
the delays can 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.
Problems addressed in VAXQMAN01_061 for OpenVMS VAX V6.1
o If there are outstanding jobs during a failover of the Queue
Manager, the Job Controller may crash the system with the
system service NOMOREPROC error status.
o In OpenVMS VAX V5.4, a DCL 'SHOW QUEUE' command listed timed
jobs in /AFTER_TIME order. Beginning with OpenVMS VAX V5.5,
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 restores support for the
earlier 'SHOW QUEUE' order.
o When a symbiont sends a TASK_STATUS request other than
DEVICE_STATUS 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
Support has also been added for additional TASK_STATUS requests
besides DEVICE_STATUS when there is not an active job.
o Timed jobs of equal priority sometimes execute in submit
time order, not in release time (/AFTER_TIME) order. This
occurs when multiple jobs are pending execution.
o Issuing the PRINT/DELETE command for may files (several
thousand) may cause the Queue Manager to crash with an
Access Violation (ACCVIO) because data is not properly
copied from one address to another.
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 The file associated with a 'PRINT/DELETE' job is deleted
even if the print is unsuccessful.
o When $GETQUI with 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 DCL
'SHOW QUEUE/MANAGER' command is not deallocated after command
completion. If a user does a series of SHOW QUEUE/MANAGER
commands the job controller can crash with an insufficient
virtual memory error.
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.
|
Files on this server are as follows:
|
»vaxqman04_061.README
»vaxqman04_061.CHKSUM
»vaxqman04_061.CVRLET_TXT
»vaxqman04_061.a-dcx_vaxexe
|
