PreviousNext
Help > EASYCOM Server > EASYCOM behavior > TroubleShooting > How to diagnose errors
How to diagnose errors

 In case of connectivity errors, there are several ways to search:

         in the EASYCOMD job history. To see it, do WRKACTJOB, then option 5 on EASYCOMD, then option 10 (job’s history), and type F10. Type F1 on the suspicious messages to get more information.

         In the EACMSGQ messages. To see it, enter DSPMSG EASYCOM/EACMSGQ.

         In the QSYSOPR messages. To see it enter DSPMSG QSYSOPR. Unexpected, failures or licensing messages will appear here.

         In the QEZJOBLOG OutQ. A spool file is generated in this outq if Easycom failed to start properly (error -4 on the client), or if the easycom job unexpectedly stops.

To see the spool file, do the following commands:

o    WRKOUTQ OUTQ(QEZJOBLOG)

o    Type F18 (to go at the end), and then F11.

o    There should be a line with the station name, with the corresponding user, date and time.

Type 5 on then entry to display the spool. It contains information, warning and error messages of the job.

         In the LOGFILE file, LOGFILE member in the EASYCOM library. This file will contain all TCP/IP failures, with OS/400 errors codes. To see that file, use: DSPPFM EASYCOM/LOGFILE MBR(LOGFILE)

This file can be downloaded using FTP or Easycom configuration client on Windows.

 

In case of errors during processing, an Easycom logfile can be useful. It can be setup using CFGEAC or Easycom configuration. The contents of this file can help to understand what is performed on the server, see parameters, additional error messages, …

The Easycom job history can also help a lot. To see it, use WRKACTJOB, option 5, then 10 and type F10.

If the Easycom job stops too quickly to see a job history, use JOBLOG(*YES) in CFGEAC command to setup EASYCOM to always have a spool generated in QEZJOBLOG (see above to consult it).

 

If the Easycom job aborts unexpectedly there should be a spool file in QEZJOBLOG (see above).

 

If the EASYCOM or the EASYCOMD job fails in a loop, try to see what is involved in the call stack. It is available by using WRKACTJOB, then option 5, then option 11.

 

 

In case of licensing errors, do DSPMSG QSYSOPR if the information provided on the client is not sufficient.