After updating to the Integration REST agent (IG REST) from the RA REST solution agent, a PREP_PROCESS_REPORT that looks for a delimiter involving a colon no longer works.
For example, the following works on a RA REST agent job:
:set &hnd0# = prep_process_report(,,REP,'*"status"*:*','COL=DELIMITER,DELIMITER=@":@')
:process &hnd0#
: set &status_info# = get_process_line(&hnd0#,2)
: p &status_info#
:endprocess
:close_process &hnd0#where the report, like in a {client_number}/system/health might show:
2026-03-02 23:53:40 Start response pattern
2026-03-02 23:53:40 {
2026-03-02 23:53:40 "status": "UP",
2026-03-02 23:53:40 "pwp": {
2026-03-02 23:53:40 "status": "UP",
2026-03-02 23:53:40 "instancesRunning": 1
2026-03-02 23:53:40 },
...The script above will show in the report as:
2026-03-03 00:09:48 - U00020408 "UP",
With the IG_REST agent, nothing will return
In some cases, if there is string manipulation with str_cut() either in the same job or in a downstream job in the workflow, the following error may show up:
Runtime error in object 'OBJECT_NAME', line '00008'. The start column for the sub-string statement ('002') is not within the string (length '0001").
Agent type: Integration REST 24.x
The output between the RA REST agent jobs and IG REST agent jobs has changed
This behavior is by design.
IG REST jobs now include a space character between the element and value (in the example earlier, status and UP):
2026-03-02 23:58:50 {
2026-03-02 23:58:50 "status" : "UP",
2026-03-02 23:58:50 "pwp" : {
2026-03-02 23:58:50 "status" : "UP",
2026-03-02 23:58:50 "instancesRunning" : 1
2026-03-02 23:58:50 },
...To resolve this, the delimiter must be updated to account for the space between the double quote, ", and the colon, :
:set &hnd0# = prep_process_report(,,REP,'*"status"*:*','COL=DELIMITER,DELIMITER=@" :@')
:process &hnd0#
: set &status_info# = get_process_line(&hnd0#,2)
: p &status_info#
:endprocess
:close_process &hnd0#