Available aXes and O/S logging facilities
Posted: 13 Feb 2017, 14:33
Often checking the job logs of aXes server jobs can reveal information about a problem. And all IBM i (OS/400) servers maintain a history log called QHST which can often contain messages in the event of operating system issues. The following sections contain information about each logging facility.
Checking aXes Server Job Logs
Does this facility need to be installed separately?
No
How you turn it on / start it?
It is always on.
How you turn it off / stop it?
It cannot be turned off.
Are there performance ramification in using it?
No
How is it typically used to isolate problems?
Use the WRKSBSJOB AXES command to display all Axes server jobs active in the AXES subsystem.
Use option 5 - Work With, then option 10 - Display job log, if active, on job queue, or pending. On the resulting Display Job Log screen, use F10=Display detailed messages and then scroll through all the message displayed.
Checking IBM i (OS/400) history logs
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.
Checking aXes Server Job Logs
Does this facility need to be installed separately?
No
How you turn it on / start it?
It is always on.
How you turn it off / stop it?
It cannot be turned off.
Are there performance ramification in using it?
No
How is it typically used to isolate problems?
Use the WRKSBSJOB AXES command to display all Axes server jobs active in the AXES subsystem.
Use option 5 - Work With, then option 10 - Display job log, if active, on job queue, or pending. On the resulting Display Job Log screen, use F10=Display detailed messages and then scroll through all the message displayed.
Checking IBM i (OS/400) history logs
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.