Re: Pointer Error

On 1/13/2012 1:38 PM, Jon Paris wrote:

I wonder how it does work then? I can't see how/why the situation is
any different to the Service Program scenario. The SrvPgm problem
arrises because there's nothing to tell the caller that it needs to
reinitialize the proc ptrs because the original copy has gone away.
So what causes the OPM program to re-resolve the pgm pointer? If it
doesn't need to re-resolve then why is there a problem with srvpgms?
It just seems that if it breaks in one scenario it should break in
both.

I assume it's because the individual links to bound procedures in service programs use completely different mechanism than system pointers. Static-bound calls within the same module or program must use something totally different from resolved pointers, and I think that dynamic-bound calls to procedures in service programs probably use something very similar to static-bound calls, just with a bit more work done during runtime binding.

RPG handles resolving to the library and program for program calls. The system handles resolving to bound procedures, so I have no idea how they do it.

I don't think the OPM program does re-resolve the pgm pointer. I think the original pointer is still valid, and that it is simply a system pointer to a program in a library, nothing to do with the activation group.

-- Barbara