From: Bruce Harvey (BruceH@ROUTESCAPE.COM)
Date: Fri Nov 22 2002 - 09:40:08 EST
Excluding the underlying program possible error messages, you can research
the following yourself:
Look through /bin/mksysb for lines such as,
"`${dspmsg} -s $MSGSET $MSGCAT 4 '0512-007 %s: Abnormal program
termination.' $NAME`"
look through the files for the definitions of dspmsg (/usr/bin/dspmsg),
MSGGET, MSGCAT, etc., then display the message yourself (dspmsg simply
displays catalog messages). Then, you can check out 'backup' and other
command messages.
---------------------------------------
Bruce T. Harvey, Special Projects Developer
bruceh@routescape.com, www.routescape.com
Insight Distribution Systems --- Hunt Valley, MD
-----Original Message-----
From: CHANDRASHEKAR, MANI [mailto:MANI_CHANDRASHEKAR@FLEET.COM]
Sent: Friday, November 22, 2002 9:14 AM
To: aix-l@Princeton.EDU
Subject: [aix-l] mksysb error message documentation
All,
Iam documenting some information regarding mksysb on the
company's homepage, so that it would be helpful for the on-call person to
troubleshoot issues with mksysb. It would be helpful if you could let me
know what would be the error messages when mksysb fails (eg: due to a bad
tape, bad tape drive etc...). I run the mksysb on the standalones and on the
sp nodes and it is run through cron.
Thanks..
shekar
This archive was generated by hypermail 2.1.7 : Wed Apr 09 2008 - 22:16:22 EDT