• Subject: QSERVER subsystem problems
  • From: Matthias Oertli <oertlim@xxxxxxxxxxxxxxxx>
  • Date: Tue, 30 Mar 1999 16:43:20 +0000
  • Organization: Habba doo daa...

I've had a curious problem: The QSERVER subsystem was ended
(ENDSBS QSERVER OPTION(*IMMED)) and most jobs within it
ended. But one job (QPWFSERVSD) didn't end, instead it
grabbed 80% of the CPU and just sat there at status END.
Hence the QSERVER subsystem also didn't end it just sat
there at status END.
A short while after this a backup kicked in. Because it
didn't get much CPU it didn't get anything done. Therefore
it was ended (*CTRLD). But now, it too didn't end, it just
sat there at status END consuming a few tenth of CPU
IBM support recommended shutting down tcpip and see if that
allows jobs to end. It didn't. QSERVER didn't accept any end
requests. Then they recommended PWRDWNSYS which was done.
This timed out. (though SRC B900BF10 was avoided by
specifying TIMOUTOPT(*CONTINUE)). The machine then IPL'd
normally and all seems well. IBM recommended a RCLSTG asap
which I will do.

But... I would like to know what really went on. What went
wrong and what can I do to avoid this problem in the future.
Joblogs et al aren't helping. No indication of a problem
anywhere that I can see. Btw: I'm on v4r3 cum 9054.

Any insight would be appreciated.

Matthias Oertli   oertlim@s054.aone.net.au
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com

This thread ...


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

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