|
Hi Joe, Does the system completely lock up, or can you still issue commands from the console. The console job runs at priority 10 so should take precedence over all other user work. However, if a program is in a loop or something, the console can still be quite slow. If the console does not give you a response, then there are a number of possibilities. Ones I think of are: 1. A system job taking a lot of CPU. System jobs run at low priority - often priority 0. There may be a valid reason for this which would require further investigation, or it may be a problem that IBM need to solve. 2. A user job has been set to run at priority 10 or less and is in a tight loop. 3. A programmer or somebody has a changed job to a priority of 10 or less which then hogs the system, or has bug and starts into a tight loop. Usually, the console will respond, albeit very slowly. I would be tempted to use WRKACTJOB to try to find the culprit. You will probably need patience with the very long response times. Another question - When the system locks up, how long does the lock up last, does it eventually free itself? Syd Nicholson Joe Lewis wrote:
About 30 days ago for the first time, my little 170 just locked up. TCP and Twinax stopped working, no error code on the front panel, the power light was green, and the processor light was lit up solid. After talking with IBM (hours later), I had to manual power down. Once back up, there were no error listings in any of the logs or in Service Tools. Then 2 weeks later, it did it again. Then over this past weekend, again yesterday and now this morning. Hardware support thinks it's software. I am on hourly support with Software, and I don't want to spend the money just find out it's an IBM issue ($250 an hour is not in my budget). I upgrade to v5r1 ,with all the PTFs at the time, in February. Nothing new has been added since then. Other then ordering the latest CUM (which I did), I am stumped. Has anyone ran into this before? - Joe Lewis _______________________________________________ This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@midrange.com To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l or email: MIDRANGE-L-request@midrange.com 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 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.