RE: v6r1 strobjcvn

Rob--

The reason the "File Qxxxx ... in use" message is issued is because there are no unused spool file members available (for a new document), and the system has to add a member to one of the Q* files. It needs an exclusive lock to do so.

One solution is to set the system value that cleans out unused spool file members so it keeps them around at least 45 days. In our case, that keeps them through a month end (which is usually the high point of spool file activity).

Once that is set, if you clear out old joblogs &c you'll have a few (!) unused spool file members.

--Paul E Musselman
PaulMmn@xxxxxxxxxxxxxxxxxxxx




At 8:24 AM -0500 11/26/08, rob@xxxxxxxxx wrote:

As noted earlier, you're right. You do NOT want too many of these running
at once. The spooling system on the i can't handle it. The following is
from just one of the hundreds of jobs that I had abnormally terminate
during a *NOMAX of a thousand or some STROBJCVN jobs. (Which goes to show
you that I think IBM has no comprehension of APIs and is trying to output
to a spool file and convert that to a disk file member.)

STROBJCVN LIB(GDIHQ)

Lock operation for object Q04079N008 not satisfied.
File Q04079N008 in library QSPL in use.
Member not added. Errors occurred.
Lock operation for object Q04079N008 not satisfied.
File Q04079N008 in library QSPL in use.
Member not added. Errors occurred.
Lock operation for object Q04079N008 not satisfied.
File Q04079N008 in library QSPL in use.
Member not added. Errors occurred.
Lock operation for object Q04079N008 not satisfied.
File Q04079N008 in library QSPL in use.
Member not added. Errors occurred.
Lock operation for object Q04079N008 not satisfied.
...

Rob Berendt