On 23 Apr 2012 05:31, Jerry C. Adams wrote:
I still have no idea what caused the system to hang up. I checked on
it this weekend a couple of times and this morning it is running at
The MSD produced during the Dxxx SRCs and the Vlogs would have
details. I seem to recall there are some tools [I forget what they are
called; service tool macros?] that could be invoked in SST\DST to
identify things like which job\task was using the CPU when the system
crashed [in hard-loop cases, that will generally be the job making the
system appear to "hang"]. Even knowing very little about the Main
Storage Dump, I recall the tooling for just viewing the MSD would enable
some great discoveries very easily; the thing I recall reviewing first,
always was the "task list".
The only thing that I know was going on was that I pressed F1 on an
error message from a test and then F10 to look at previous messages.
Could be coincidence, but no one else admitted doing anything at the
I have had way more than my share of similar coincidences; everyone
including myself convinced nothing they did gave origin. Though some
were eventually determined to be a direct effect of what I had done...
found out by seeing the system crash again after coming back up, and me
having repeated the same sequence of events. Once or twice I recall,
for seemingly as innocuous work as compared to the F1=Help\F10=Detailed :-Q
This mailing list archive is Copyright 1997-2019 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