On z/VM 3.1 Q PRT ALL shows open spool files. I don't remember when that was
added (sometime in VM/ESA I think) but it was a lot of help diagnosing spool
filling problems. Now VM doesn't crash when the spool gets full. It stops users
that are adding to the spool.
[EMAIL PROTECTED] wrote:
Also, open spool files will not show up in CP QUERY <XXX> ALL. You will
only see closed spool files. We had a problem some years ago (HPO 5 on
a 4381, which will give you a time frame) of spool filling up and the
system crashing every Monday night at 10 pm. But nothing showed up in
spool. We came to the conclusion that we had a user with an open spool
file that was filling up the system, crashing it (HPO would crash when
the spool filled up), re-ipling and wiping out the open spool file, so
we never did see what was causing the problem. We purchased CA's
VMSPOOL, which can let you look at open spool files, and quickly found a
user had a fortran program that ran every Monday night, but had errors
in it. The printed report put out the errors in an endless loop and by
the time spool filled up had 2,500,000 records in just this one file.
VMSPOOL is the only tool I know of that lets you look at open spool
files and is worth its weight in diamonds for this one feature alone.
--
Stephen Frazier
Information Technology Unit
Oklahoma Department of Corrections
3400 Martin Luther King
Oklahoma City, Ok, 73111-4298
Tel.: (405) 425-2549
Fax: (405) 425-2554
Pager: (405) 690-1828
email: stevef%doc.state.ok.us
