× 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.



Help desk managers reply about the Basic assistance level:

"He!!, most of our users aren't capable of using *BASIC assistance level. 
*INTERMEDIATE will make their eyes roll up in the back of their heads."


I guess I'll open the DCR.


Rob Berendt
-- 
Group Dekko Services, LLC
Dept 01.073
PO Box 2000
Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com





Neil Palmer/DPS <neilp@xxxxxxxxxxx> 
Sent by: midrange-l-bounces@xxxxxxxxxxxx
05/16/2005 12:48 PM
Please respond to
Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>


To
Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
cc

Subject
Re: WRKSPLF and Basic Assistance Level






Exactly.  Poor programming on IBM's part.  I hate that flimsy "WAD" 
excuse.  As far as I'm concerned, I don't care whether it's a "bug" 
according to IBM, or "Working as designed, but whoever designed it 
obviously made an error in the design, so the fact it's working to a lousy 

design shouldn't be the customers concern, IBM shoudl just fix it".

PS - for 99% of the displays, *BASIC assistance level sucks anyway.  There 

are 1 or 2 places where it is useful.

...Neil




rob@xxxxxxxxx 
Sent by: midrange-l-bounces@xxxxxxxxxxxx
2005/05/16 12:23



To
midrange-l@xxxxxxxxxxxx
cc

Subject
WRKSPLF and Basic Assistance Level






Our help desk manager had an issue.

Had a document on P01A14 on hold.
Held out queue P01A14.
With assistance level for wrksplf set to Basic, I took option "6" to 
release spool file.
Got a message saying out queue is held and to use option 10.
Took option 10 and things just hung up - for about 20 minutes and 
eventually it worked.

I reported this to IBM.  They were able to duplicate it.  Their response 
was:

The developer has taken a look into this issue and explains what is 
going on in the CPS discussion.  The core of it is that, when you are at
basic assistance level and you use the options to release a held spooled
file and then release the held output queue, the system ends up doing a 
WRKSPLF *ALL, rather than just having to look at spooled files in a 
single output queue.  If there are a lot of spooled files on the system,
this can take a long time.  After this has been done once, the pages are
in memory already so the WRKSPLF *ALL takes a much shorter period of 
time to complete.  This is working as designed.  To avoid having to wait
a long time, it is recommended to either use an assistance level of 
*INTERMED or avoid holding output queues.


To me, this sounds like some bad use of the spool files api's.  What do 
you think?


Rob Berendt
-- 
Group Dekko Services, LLC
Dept 01.073
PO Box 2000
Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com




-- 
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing 
list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.



As an Amazon Associate we earn from qualifying purchases.

This thread ...

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.