Re: Setting breakpoints in HTTPAPI callbacks

When in doubt write to a debug file.

Regards,
Richard Schoen
Web: http://www.richardschoen.net
Email: richard@xxxxxxxxxxxxxxxxx
----------------------------------------------------------------------

message: 1
date: Thu, 30 Jul 2020 09:12:55 -0500
from: Joe Pluta <joepluta@xxxxxxxxxxxxxxxxx>
subject: [WEB400] Setting breakpoints in HTTPAPI callbacks

Cross-posted to RPG400 and WEB400 lists.

A colleague is using Scott Klement's HTTPAPI routines and is running into an issue.? They have the following code:

?????? rc = http_url_post_xml( URL
???????????????????????? : %addr(SOAP) + 2 ???????????????????????? : %len(SOAP) ???????????????????????? : *null ???????????????????????? : %paddr(Incoming) ???????????????????????? : %addr(call_status) ???????????????????????? : HTTP_TIMEOUT ???????????????????????? : HTTP_USERAGENT ???????????????????????? : 'text/xml'
???????????????????????? : %trim(WSWSUR));

The program runs in a never-ending batch job.? They execute STRSRVJOB on the job and STRDBG on the program, and then set a breakpoint on the first line of the "Incoming" procedure.? It looks like the procedure is being executed because it writes to a file and records are indeed being written, but the breakpoint is never hit.

Before we dig a lot deeper or start using bigger debug hammers, is this an issue anyone else has seen?? I was wondering if perhaps there are multi-threading concerns with the HTTP APIs that might complicate service jobs.

Thanks as always!