Profound Logic Forums

Hello,

We are getting this error a few times a day.
I am certain they are being generated from some Genie screens that have some dynamic grids.
When the error shows up, only a few Genie Screens are being run.
For the life of me I can not recreate the error.
Can someone help me trace down what is causing this?

The call to RPGSPINIT ended in error (C G D F).
RPG procedure PUI0009102 in program PROFOUNDUI/PUI0009102
at statement 999 called program or procedure RPGSPINIT, which ended in
error. If the name is *N, the call was a bound call by procedure pointer.

It does not seem to be causing any problems unless users are not reporting them.

Thanks.

I'd start by getting a detailed job log with all the 2nd-level text, etc.

You'll want to use this to determine why RPGspInit is crashing. Right now we know almost nothing -- just that RPGspInit is crashing, no information as to why. A detailed job log would provide a lot more information.

I am being plagued with these errors the more users use Profound.
Here is a joblog from when I could capture this error.

Job 692481/QTMHHTTP/PROFOUNDUI started on 03/16/20 at 14:46:30 in subsystem QHTTPSVR in QHTTPSVR.
Job entered system on 03/16/20 at 14:46:30.
This is a CGI job for IBM HTTP Server instance PROFOUNDUI.
The requested heap space operation is invalid.
The pointer parameter passed to free or realloc is not valid.
Pointer not set for location referenced.Function check. MCH3601 unmonitored by RPGSPSP at statement 0000000025, instruction X'0000'.
The call to RPGSPINIT ended in error (C G D F).

I am trying to trace down why this is happening, but can not consistently re-create this error
These are genie screens with two dynamic grids kicking out these errors.
Any help with how to go about tracking this down would be greatly appreciated

I'd suggest opening a support ticket.

Hello Doug,

Any update on this by chance? We got this error a few hours ago and I'm currently trying to track down the user to see if I can recreate it. Also, we are Not using Genie, we are using Rich Display, but the error is the same...

Thanks,
Paul Kenosky