How to trace a Gen 8.6 GUI C client CALL EXTERNAL error (function TIRXCWS)
search cancel

How to trace a Gen 8.6 GUI C client CALL EXTERNAL error (function TIRXCWS)

book

Article ID: 281305

calendar_today

Updated On:

Products

Gen

Issue/Introduction

Is it possible to trace the cause of Gen 8.6 GUI C client CALL EXTERNAL error:
TIRM149E: Error occurred in CA Gen supplied function: TIRXCWS 

Resolution

CALL EXTERNAL does not use a Gen cooperative flow like calling the EJB Web Service does using commcfg.ini file WS protocol, so enabling "CMIDEBUG ON" in that file will not create a trace file in directory "%USERPROFILE%\AppData\Local\CA\Gen 8.6\logs\client".
The CALL EXTERNAL command uses curl (cURL) to execute the http call and it is possible to get trace data by setting Windows environment variable CMIDEBUG to the value -1 which also turns on the Verbose option in curl.
set CMIDEBUG=-1
For example setting CMIDEBUG can be done in a command prompt and then run the client from there or alternatively create a command file to set it and also run the client from that same command file.

After executing the CALL EXTERNAL a trace file named trace-<CLIENT-LOAD-MODULE-NAME>-nnnnnn.out should be created in directory "%USERPROFILE%\AppData\Local\CA\Gen 8.6\logs\client".

Additional Information

Powered by Wolken Software