Collecting A Trace Using The ACS Client

From the Edit menu, select Preferences and set the 'Logging level:' to FINEST as shown in Fig. 2

Click 'Local Settings' and press Clear in the 'Logs directory' section as shown in Fig. 3 to ensure that we are getting logs for the problem we are tracing. If there are 0 objects in the Logs directory (as shown in Fig. 3), then the Clear button is unavailable, move to the next step.

Press the OK button in the Preferences window to close it.

Restart the ACS client.

Re-create the problem.

After the problem is re-created, go back to the Preferences window and turn the logging level back to OFF.

Select 'Package Service Logs' from the Tools menu. Upon completion, a message like the one in Fig. 4 displays showing the location of the collection that was created. You can press the 'Open Target Directory' to get easy access to the compressed file containing all the service logs.

Upload compressed file to IBM Support by using www.ecurep.ibm.com or www.ibm.com/mysupport

Tracing on IBM i

To trace ACS running on the IBM i itself it you should first determine if the ACS client is on the current PTF level.  The current PTF for each version of IBM i is documented in this technote:  IBM i Access - Client Solutions 5733XJ1

Next, ensure that the user profile that is running ACS has a home directory.  Use the DSPUSRPRF command to determine what the home directory value is for the user profile and the WRKLNK command to verify that it exists and the profile owns it and is authorized to create new objects within it.  The trace output is created in the home directory of the user.

In order to start and stop tracing you must call the log plugin for ACS with either a java command or RUNJVA.  For example, start a trace, run a data transfer and then stop the trace I could combine all three commands into on CL command:

QSH CMD('java -jar /QIBM/ProdData/Access/ACS/Base/acsbundle.jar /plugin=log /level=finest;java -jar /QIBM/ProdData/Access/ACS/Base/acsbundle.jar /plugin=cldownload /system=localhost /hostfile=qiws/qcustcdt /clientfile=/tmp/qcustcdt.xlsx /colheadings=1 /usecollabels;java -jar /QIBM/ProdData/Access/ACS/Base/acsbundle.jar /plugin=log /level=off;')

Or you can use the JAVA or RUNJVA command and execute the command sequentially:

JAVA CLASS('/QIBM/ProdData/Access/ACS/Base/acsbundle.jar') PARM('/plugin=log' '/level=finest')
JAVA CLASS('/QIBM/ProdData/Access/ACS/Base/acsbundle.jar') PARM('/plugin=cldownload' '/system=localhost' '/hostfile=QIWS/QCUSTCDT' '/clientfile=/tmp/custdata.xlsx' '/colheadings=1' '/usecollabels')
JAVA CLASS('/QIBM/ProdData/Access/ACS/Base/acsbundle.jar') PARM('/plugin=log' '/level=off')

If the home directory for the user is /home/joeuser, then the traces will reside in the path /home/joeuser/IBM/iAccessClient/Logs and any dumps that might get created are in the path /home/joeuser/IBM/iAccessClient/Dumps.  Download all of the files from these two paths and upload them to support by using  www.ecurep.ibm.com or www.ibm.com/mysupport