This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.
--
[ Picked text/plain from multipart/alternative ]
Hi all,
 
I have a funny thing happening at a client where all of a sudden
printers/outqs are getting an error anytime that a response needs to be
performed on the printer (G, H, etc).  There error is:
 
40    12/04/01   09:04:49   QSPWAIT        QSYS        018F    
QCMD        
  Message . . . . :   An error occurred during a mutex operation.  The
return
    code is
3459.                                                           
 
This is coming out of:
                                               
 From program . . . . . . . . . :   QSPDSPFM   
   From library . . . . . . . . :     QSYS     
   Instruction  . . . . . . . . :     060A     
                                                
 To program . . . . . . . . . . :   QSPDSPQ    
   To library . . . . . . . . . :     QSYS     
   Instruction  . . . . . . . . :     0402     
                                               
 
Environment:
 
Just loaded 5.1 with CUM over the weekend (yes that is kind of peculiar)
but is worked OK yesterday.
 
Ending the QSPL subsystem makes the problem go away, but it returns as
soon as a writer is started and requires a response of some kind.  (We
are powering down the system now to see if we can get it cleaned up - I
hate to do that!).
 
We can not use a WRKWTR command - it hangs with an object lock (on the
above error).
Any ideas? 
 
Thanks
 
John Bussert
Swift Technologies, Inc.
www.swiftorder.com
847-289-8339
847-289-8939 (fax)
jbussert@swiftorder.com
 
 


As an Amazon Associate we earn from qualifying purchases.

This thread ...


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

This mailing list archive is Copyright 1997-2022 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.