| Author |
Message
|
| pfarrel |
 Posted: Thu Oct 07, 2004 10:51 am Post subject: Problem Solving on AIX |
 |
|
Centurion
Joined: 16 Mar 2004
Posts: 120
Location: Kansas City
|
I am used to running MQ and WBIMB on a mainframe, and on Windows. We are now starting to use these products on AIX. Debugging problems appears to be MUCH harder, and it is quite an eye-opener.
All I seem to have on AIX is a set of line commands. I use the cd ( changedirectory ) and cat ( list a file ) a lot, to look at such things as error logs ( you have to cd to /var/mqm/qmgrs/qmname/errors, it's quite a mouthful ). I don't seem to be able to find the error messages that went to SYSMSG on the mainframe, and to the event log on windows. I feel like I don't have the right tools, or any tools for that matter.
Is there a better way to do this on the AIX platform ?What do more experienced AIX users of Websphere products do ? |
|
| Back to top |
|
 |
| csmith28 |
| Posted: Thu Oct 07, 2004 11:01 am Post subject: |
|
|
Grand Master
Joined: 15 Jul 2003
Posts: 1196
Location: Arizona
|
On AIX the system events go to an error report that can be accesse by typing:
MQSeries System errors are in /var/mqm/errors These are MQSeries system events. Also if a seriouse problem occurs a file will be generated in this direcory with a .FDC file extension.
The event and errors recorded in /var/mqm/qmgrs/QMGRNAME/errors are specific to the QManager who's subdirectory you are in.
If you are not real confortable with Unix Commands you can always use WMQExplorer to manage your AIX MQManager. That may put you back in more familiar territory but WMQExplorer does have it's limitations.
Personally I prefer managing my MQManagers from Unix Command line but I have been doing this for almost 10 years. I would be helpless as fish in a Privot Bush on the MainFrame, Tandem or AS/400.
Oh and I am not aware of any Unix equivalent of the SYSMSG.
Good luck. You have come to the right place for guidance. 
_________________
Yes, I am an agent of Satan but my duties are largely ceremonial.
Last edited by csmith28 on Thu Oct 07, 2004 3:16 pm; edited 1 time in total |
|
| Back to top |
|
|
| vennela |
| Posted: Thu Oct 07, 2004 11:55 am Post subject: |
|
|
Jedi Knight
Joined: 11 Aug 2002
Posts: 4055
Location: Hyderabad, India
|
Well AFAIK
will only report events when an FDC is cut. Other than that I haven't seen error being reported there.
However, /var/adm/syslog is the directory to look for system errors (like WBIMB errors).
Instead of cat use more to view the file. Also use man to get the usage of a unix command. |
|
| Back to top |
|
|
| csmith28 |
| Posted: Thu Oct 07, 2004 12:13 pm Post subject: |
|
|
Grand Master
Joined: 15 Jul 2003
Posts: 1196
Location: Arizona
|
I've never found much use for the syslog.
errpt records filsystem problems, core file creations, operating system problems, hardware failures etc. etc.
_________________
Yes, I am an agent of Satan but my duties are largely ceremonial. |
|
| Back to top |
|
|
| vennela |
| Posted: Thu Oct 07, 2004 12:42 pm Post subject: |
|
|
Jedi Knight
Joined: 11 Aug 2002
Posts: 4055
Location: Hyderabad, India
|
I am talking about AIX
I think that file is configurable. Maybe our Sys Admins made it /var/adm/syslog so that we always have the same file to look at no matter whether it is HP-UX or Solaris or AIX.
Look at your /etc/syslog.conf and see what the file is for system logging.
I thought if you do
| Code: |
| /usr/lib/errdemon -l |
it will tell you what the file is
For me it listed a file and that is not readable. |
|
| Back to top |
|
|
| csmith28 |
| Posted: Thu Oct 07, 2004 1:31 pm Post subject: |
|
|
Grand Master
Joined: 15 Jul 2003
Posts: 1196
Location: Arizona
|
| vennela wrote: |
I am talking about AIX
I think that file is configurable. Maybe our Sys Admins made it /var/adm/syslog so that we always have the same file to look at no matter whether it is HP-UX or Solaris or AIX.
Look at your /etc/syslog.conf and see what the file is for system logging.
I thought if you do
| Code: |
| /usr/lib/errdemon -l |
it will tell you what the file is
For me it listed a file and that is not readable. |
Yeah, apparently there is no company standard for the syslog here where I work. Why am I not surprised. I found it on some servers and the not on others. I am not sure what they record in your syslogs but mine look pretty useless for troubleshooting anything. Most of the entries are related to people loging on, typing in an invalid password, lots of entries about su being used. A few "FFST created in" entries.
I was thinking of /var/adm/message in Solaris but I don't work with SUN Servers much anymore. Now there's a useful file.
_________________
Yes, I am an agent of Satan but my duties are largely ceremonial. |
|
| Back to top |
|
|
|
|
