Hi Edmund,
Thank you for your reply. I just opened a case.
Kinde regards,
Martijn van Breden
lead software architect
________________________________
Van: WDSCI-L <wdsci-l-bounces@xxxxxxxxxxxxxxxxxx> namens Edmund Reinhardt <edmund.reinhardt@xxxxxxxxxx>
Verzonden: vrijdag 13 oktober 2023 16:05
Aan: WDSCI-L@xxxxxxxxxxxxxxxxxx <wdsci-l@xxxxxxxxxxxxxxxxxx>
Onderwerp: [WDSCI-L] FW: Debugger in RDi error (9.6 and 9.8)
CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe.
Hi Martijn,
Please open a case with IBM, our debug expert says this looks like a host debug problem and our support agents should be able to help you.
From: Morris Kwan <mkwan@xxxxxxxxxx>
Date: Friday, October 13, 2023 at 9:59 AM
To: Edmund Reinhardt <edmund.reinhardt@xxxxxxxxxx>
Subject: RE: [EXTERNAL] [WDSCI-L] Debugger in RDi error (9.6 and 9.8)
Hi, Edmund
This looks like a host debug problem. We probably need to ask the customer to run through a few diagnostic steps. Please ask him to open an escalation and L2 support will assist him in getting the diagnostic information we need.
Thanks,
Morris Guan
IBM i Debugger Development
IBM Toronto Lab
From: Edmund Reinhardt <edmund.reinhardt@xxxxxxxxxx>
Sent: Friday, October 13, 2023 8:37 AM
To: Morris Kwan <mkwan@xxxxxxxxxx>
Subject: FW: [EXTERNAL] [WDSCI-L] Debugger in RDi error (9.6 and 9.8)
Not sure if you have any insight
From: WDSCI-L <wdsci-l-bounces@xxxxxxxxxxxxxxxxxx<mailto:wdsci-l-bounces@xxxxxxxxxxxxxxxxxx>> on behalf of Martijn van Breden <m.vanbreden@xxxxxxxxxxxxxxxxxxxxxxxxxx<mailto:m.vanbreden@xxxxxxxxxxxxxxxxxxxxxxxxxx>>
Date: Friday, October 13, 2023 at 5:48 AM
To: midrange-WDSC WDSC message board (wdsci-l@xxxxxxxxxxxxxxxxxx<mailto:wdsci-l@xxxxxxxxxxxxxxxxxx>) <wdsci-l@xxxxxxxxxxxxxxxxxx<mailto:wdsci-l@xxxxxxxxxxxxxxxxxx>>
Subject: [EXTERNAL] [WDSCI-L] Debugger in RDi error (9.6 and 9.8)
Hi
I have a pretty simple SQLRPGLE program that reads a JSON file from IFS with IFS_READ_UTF8 and then parses the header and lines from that file with JSON_TABLE.
While debugging I run into the following:
Everytime I start debugging or refresh the SEP the debugger terminates when I first hit the JSON_TABLE function with this message:
Platform: IBM i *UNKNOWN* Connection: PTHS02:3825 Error: (998) CRRDG3002E Connection with the debug engine was lost.
The program call (from 5250) ends normally and there's nothing weird popping up in my joblog. From the messages in the joblog it even appears that the program ran flawless into an end.
If I call the program a second time I can run through all the statements in the debugger just fine. If I refresh the SEP, it breaks.
I took me quite some time to find out that this was a debugger problem and not a programming problem, so I was wondering if anyone has run into something similar or has a solution to prevent this from happening
TIA
Kind regards, Met vriendelijke groet,
Martijn van Breden
lead software architect
--
This is the Rational Developer for IBM i (WDSCI-L) mailing list
To post a message email: WDSCI-L@xxxxxxxxxxxxxxxxxx<mailto:WDSCI-L@xxxxxxxxxxxxxxxxxx>
To subscribe, unsubscribe, or change list options,
visit:
https://lists.midrange.com/mailman/listinfo/wdsci-l
or email: WDSCI-L-request@xxxxxxxxxxxxxxxxxx<mailto:WDSCI-L-request@xxxxxxxxxxxxxxxxxx>
Before posting, please take a moment to review the archives
at
https://archive.midrange.com/wdsci-l .
--
This is the Rational Developer for IBM i (WDSCI-L) mailing list
To post a message email: WDSCI-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit:
https://lists.midrange.com/mailman/listinfo/wdsci-l
or email: WDSCI-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at
https://archive.midrange.com/wdsci-l.
midrange.com
