Mark:

One useful alternative to the standalone dump utility is the VMDUMP
command. It produces a core image dump as a spool file that can be
loaded onto disk using the CMS DUMPLOAD command and examined using
the Dump Viewing Facility and (soon) the VM Dump Tool. While there's
no Linux-specific support in the dump readers, developing some would
not be a huge effort (they both provide macro facilities and control
block mapping functions).

Two of the best advantages of VMDUMP are (1) it's always available, and
(2) one command (VMDUMP 0-END) gets the information you need in almost
all situations.

Romney

On Sat, 13 Jul 2002 11:47:09 -0400 Post, Mark K said:
>Rob,
>
>I can't help too much with the VM-specific stuff, but I would recommend that
>you investigate the Linux/390 2.4 standalone dump utility.  If this ever
>happens again, and they're going to force the machine off and re-boot it,
>they should use the SAD to get some diagnostic information before doing
>that.  In the past, we've had to do things such as tell operations "if you
>don't have any diagnostic data for us, we're not accepting any problems
>records," to get the message across.
>
>Mark Post
>
>-----Original Message-----
>From: Rob Schwartz [mailto:[EMAIL PROTECTED]]
>Sent: Friday, July 12, 2002 4:58 PM
>To: [EMAIL PROTECTED]
>Subject: System "Hang"
>
>
>We are running SUSE 7.2 in an IFL with z/VM 4.1.  On this machine we are
>running UDBEE 7.2.    Early this morning the machine hung up.   I have very
>little information to go on.   Here is what I have.
>
>/var/log/messages
>After 01:13 there were no new messages.   The last message  showed an REXEC
>session starting.   This REXEC is started from an OS/390 machine and has
>worked fine for weeks.
>
>Telnet connections would time-out.
>
>I do NOT know if the VM user was consuming CPU or doing I/O.
>
>The machine was recycled and now the REXEC-started procedure works.
>
>I instructed the people involved with this on how to do an INDICATE USER
>command to gather some VM-perspective information.   Are there any logs
>other than /var/log/messages that could be helpful?    Is there something
>that I could turn on to further trace activity on the system?
>
>Regards,
>Rob

Reply via email to