Author: Susan McClure <smcclure AT IS.RICE DOT EDU>
Date: Tue, 6 Feb 1996 09:09:44 -0600
Well IBM- any ideas on how to trace/trap/debug this problem?? Looks like we have all been (mistakenly) keeping quiet, assuming it was "just us and our environment" ADSM in MVS hoped it would the 3172
Author: Jeffrey Mathers <matherj AT ROCKVAX.ROCKEFELLER DOT EDU>
Date: Tue, 6 Feb 1996 10:29:46 +0100
Susan, I would like to encourage you to open a problem number, if you have not done so. IBM's responsiveness to problems will increase dramatically when problem numbers are opened. It's a major pain
Author: Mary Vollmer <Mary_Vollmer AT MGIC DOT COM>
Date: Tue, 6 Feb 1996 10:19:31 EDT
Since many of us have the same problem, suggestions on areas to check, modify, etc. and WHAT IS CONTRIBUTING TO/CAUSING THE TIMEOUTS would be very helpful. I agree that Susan should open a problem to
Author: Helmut Richter <Helmut.Richter AT LRZ-MUENCHEN DOT DE>
Date: Tue, 6 Feb 1996 17:11:16 +0100
As the problem seems to be common to many customers, it might be a good idea to collect on this mailing list all the problem numbers that address this one problem. This will help the support to close
We are pretty well convinced that this problem is a symptom of the CPU constraint on the server (it runs on only one processor of our 3090-600E) and that the problem has nothing at all to do with our