Guess I waited too long, Chuck. Our V5R1 machine has three options under
the MSD Manager. The first one (Work with current main storage dump (MSD)
residue) only says "Main storage dump not present." The second one (Work
with copies of main storage dumps) brings up an empty list. The third one
(Work with copy options) wants to make copies and re-IPL; I don't think so.
.-) The Service Action Log is empty.

Though it is good to know that I'm not the only one who can bring a system
to its knees so innocently. I thought I had done it again this morning.
This time I used WRKLNK and pressed the Pass Down key. The inhibited
indicator came on - and stayed on longer than I would have expected (okay, I
panicked after 10-15 seconds). Dodged a bullet there.

Jerry C. Adams
IBM i Programmer/Analyst
Ears too big. -Hollywood casting director after Clark Gable's first screen
test
--
A&K Wholesale
Murfreesboro, TN
615-867-5070


-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of CRPence
Sent: Monday, April 23, 2012 12:02 PM
To: midrange-l@xxxxxxxxxxxx
Subject: Re: System Hung

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
"normal" levels.

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
time.

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

Regards, Chuck
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe,
or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a
moment to review the archives at http://archive.midrange.com/midrange-l.


This thread ...

Replies:

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

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 [javascript protected email address].