× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



did you run that over all of the spooled files in the OUTQ??? if so that's
the problem....

Print sequence (PRTSEQ) - Help

cause the position of the file on the output queue to
change.

*NEXT
The attributes of the file (or files) are changed so
that they are moved to the top of the output queue.
If PRTSEQ(*NEXT) is specified when the SELECT
parameter is specified, files with selection values
are moved ahead of the files that do not meet the
requirements. Two files that are both moved may

the system is juggling all the spooled files to place them all to be
printed first in the outq...

Thanks,
Tommy Holden



"Frances Denoncourt" <Frances.Denoncourt@xxxxxxxxxxxxxx>
Sent by: midrange-l-bounces@xxxxxxxxxxxx
01/02/2008 01:32 PM
Please respond to
Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>


To
<midrange-l@xxxxxxxxxxxx>
cc

Subject
RE: PRTSEQ(*next) causes Necessary Resource not Available






Maybe I posted this too close to the holidays, but I was hoping someone
had an idea what was happening.
This is the original post. We are at V5R2M0
Thanks.


I think this entry caused a problem with an outq or controller or
something.

WRKOUTQ TRSPRT23 to display spooled files.
Took option 2 to change and entered this sequence:
outq(trsprt04) save(*yes) prtseq(*next)


I have not had a problem with this before, but it caused my session to
lock up - killed it after 20 minutes or so and went home. I did not end
the job properly knowing I was going home and the signon would be
available the next day after it got over it. That was Friday night.
An overnight job that had several OVRPRTF to TRSPRT04 failed because it
could not allocate the queue.

I thought it was 'fixed' this morning and used the exact same sequence
again and locked up the works again. This time I ended the job properly
and we seem to be in business - except for the job that blew up and should
have posted tons of stuff.

Any ideas about that command sequence??
Thanks

Fran Denoncourt
Sr. Programmer/Analyst
Pinal County Treasurer's Office
Florence, AZ 85232
(520) 866-6404

Receipt of this message does not grant you permission to send me
Unsolicited Commercial Email



As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.