How to: |
If you encounter a server problem, you can run a set of traces that will help you assess the problem, and, if necessary, communicate it to Customer Support Services for further troubleshooting. This topic describes trace options and provides instruction for creating the traces.
There are two types of traces you can run to troubleshoot a problem:
Under normal conditions, most applications are run in a server context. However, if you run your trace in a non-server context (that is, if you run a non-server trace), you can produce the necessary diagnostic information while significantly reducing the amount of material that needs to be reviewed. Running a non-server trace also rules out server communications as a cause of your problem.
If you prefer to use native IBM i commands, a number of CMD/CL programs are created during installation in the server administrator comment library and can be used to start traces, turn traces off, and perform edastart -savediag functions. The commands are, respectively, ITRCON, ITRCOFF, and ISAVEDIA. To use them (instead of using edastart under QSH), enter the required command and press F4 for prompted mode, then edit parameters, as needed, and press Enter. For related information, see CL and CMD Programs.
To generate a server trace:
edastart -traceon
You must preface edastart with the appropriate path, or place the directory in your system PATH variable.
edastart -savediag
For information about sending the diagnostic information to Customer Support Services, see Information You Should Have and Customer Support.
To generate a non-server trace:
edastart –savediag
You must preface edastart with the appropriate path, or place the directory in your system PATH variable.
For information about sending the diagnostic information to Customer Support Services, see Information You Should Have and Customer Support.
iWay Software |