Checking IBM i (OS/400) history logs
All IBM i (OS/400) servers maintain a history log called QHST. In sites with suspect communication links, QHST will often record TCP/IP level drop outs and recoveries. If an aXes system is exhibiting intermittent or random issues then the root problem may be traceable to TCP/IP level communications issues. In such situations you need to rectify these basic TCP/IP level issues before aXes will function reliably. For example, people using a wireless link or with a loose or failing LAN connection may experience problems, as will people whose network routers play up or are re-booted.
| Does it have to be installed separately? If yes, where do you get it from? | No |
|---|---|
| How you turn it on / start it? | It is always turned on. |
| How you turn it off / stop it? | It is always turned on. |
| Are there performance ramification in using it? | No |
| How is it typically used to isolate problems? | Use the OS/400 command DSPLOG and scroll to messages issued around the time of the aXes issue. Look for any messages related to communication errors. |
| What sort of information might you be asked to send to aXes support? | Screen prints of the DSPLOG command showing messages issued at or around the time of the aXes issue. |