RE: program data structure pointer error

I threw this data structure into a test program, had it reference the parms field, and did not get a run-time error. I'm at v5r4. Which has me agreeing with Rob that a PMR may be required. Or - there's something else within the program that's contributing to the error situation. The fact that the job log shows a pointer error three times with a following recursion error makes me think there's something else at work here.

-Kurt

-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx [mailto:rpg400-l-bounces@xxxxxxxxxxxx] On Behalf Of rob@xxxxxxxxx
Sent: Thursday, October 22, 2009 8:00 AM
To: RPG programming on the IBM i / System i
Subject: Re: program data structure pointer error

It strikes me as a bit silly to have keyword parameters (like *PARMS) and
still require them to be in the proper order. In the reference *PARMS
goes from 37-39 and is a 3,0 zoned decimal.

Job user goes 254-263. You may wish to deprecate the use of this. See
the "Current user profile name" in columns 358-367. There are profile
handle api's used to switch between profiles. Most commonly noticed by
client/server type jobs that run under the user profile QUSER or some such
thing but the job logs may show "Now servicing user profile ROB". These
profile handle api's are published and are being used by others. But do
what you want though.

I use a standard /COPY for my PSDS.

I would open up a pmr with IBM on this. If order is important then it
should be a compile time error - not a run time error.

Rob Berendt