- Integrated Systems
- About Us
- Integrated Systems
- About Us
05-03-2010 11:23 AM
VMS v7.2-2, AS800 512MB, uptime 328 01:25:12
"Suddenly" this morning, I'm receiving the above message regarding the queue manager. It is month-end, but I don't think it's any busier a month-end than others, job wise.
Thus far I have reduced the journal file size (DIAG 7) from 2M blocks to ~6K, added a pagefile and restarted some processes to make use of it.
Is there anything else I can do to help it right now? I'm waiting for a quiet time to restart the queue manager with a larger value for page file quota.
ES47's with gobs of memory are patiently waiting on the sidelines so no need to suggest I upgrade, we are progressing at glacial speeds in that direction.
Solved! Go to Solution.
05-03-2010 11:44 AM
Clustered or non-clustered environment? Shared system disk or separate system disks?
I'm thinking along the lines of fixing the queue manager on each different node in turn.
However, I don't have access to verify everything at this instant.
- Bob Gezelter, http://www.rlgsc.com
05-03-2010 11:47 AM
I suspect you'll be restarting the queue manager.
Presuming it's not some other system-level leak.
And if I were suggesting an upgrade, memory would be a factor, but I'd also be looking at OpenVMS Alpha V8.3 or at OpenVMS I64 V8.3-1H1.
I'd recommend getting away from those long up-times, too; that's an inviting strategy on the surface, but one tends to leave your servers down-revision on patches. My preference is shorter up-times and preferably with some redundancies of servers, and with clustering or fail-over. Planning for failures and for upgrades, in other words, rather than trying to avoid that. (There's often no prize for long up-times, and there can be costs.)
Barring key applications that are locked into Alpha, I'd be moving to OpenVMS I64, too.
05-03-2010 01:19 PM
Our company will be changing hands "soon", we'll see what the new owners think of VMS.
05-03-2010 02:03 PM
Have you checked for accumulating queue entries? Maybe a queue with /RETAIN?
I run a job daily to look for retained jobs, or jobs with procedures that don't match the most recent file.
05-03-2010 03:12 PM
05-03-2010 07:23 PM
Looks like QMAN is not getting enough virtual memory to perform its work.
What is the JOB_LIMIT of the queue. JOB_LIMIT would indicate number of jobs
in the queue that execute in parallel.
Also, how many jobs in the queue do actually execute in parallel?
>> restart the queue manager with a larger value for page file quota.
Yes. This would give the queue manager some more virtual memory to work with.
05-03-2010 07:27 PM
Looks like fix is available for this problem.
From the kits VMS732_QMAN-V0100 and VMS82A_QMAN-V010
Systems which have a very large physical memory (more
then 10GB) and a large PAGEFILE.SYS sometimes produce the
following QMAN error messages.
%QMAN-W-LOWMEMORY, the queue manager process may require
more virtual memory than is currently available.
%QMAN-F-ALLOCMEM, error allocating virtual memory
-LIB-F-INSVIRMEM, insufficient virtual memory
%JBC-E-QMANDEL, unexpected queue manager process termination
05-03-2010 08:09 PM
>> VMS v7.2-2, AS800 512MB, uptime 328 01:25:12
Current version of VMS is V7.2-2.
You have to upgrage VMS to V73-2 or onwards in order to be able
to instal the QMAN patches which has fix related to "QMAN-W-LOWMEMORY"