Working as designed it seems. From the V5R4 RPG Reference
"If a based field is defined within a subprocedure, then both the field
and the basing pointer are local. "
So it is most definitely implicitly defining your pointer locally in the
subprocedure.
As a work around, you should be able to base it on a pointer of a
different name and then set the address of the local pointer to the
address of the global.
Brian May
Project Lead
Management Information Systems
Garan, Incorporated
Starkville, Mississippi
"Elbert Cook" <elbert@xxxxxxxxxxxxxxx>
Sent by: rpg400-l-bounces@xxxxxxxxxxxx
03/24/2011 01:28 PM
Please respond to
RPG programming on the IBM i / System i <rpg400-l@xxxxxxxxxxxx>
To
"'RPG programming on the IBM i / System i'" <rpg400-l@xxxxxxxxxxxx>
cc
Subject
Local Variable or Bug
The program snippet below will display to the screen
Message 1
Message 1
Message 3
Remove or comment out the "C s 10a based(ptr_Msg)" and the
program
displays
Message 1
Message 2
Message 3
My best guess is based(ptr_Msg) is spawning a local ptr_Msg unique to
ProcedureX
Is this effect correct? Is this a bug in the RPG Compiler?
H DFTACTGRP(*NO) ACTGRP(*CALLER)
****************************************************
D ptr_Msg s *
D Msg s 10a based(ptr_Msg)
D Result s 3a
D Msg1 s 10a inz('Message 1')
D Msg2 s 10a inz('Message 2')
D Msg3 s 10a inz('Message 3')
**
D ProcedureX pr
/Free
ptr_Msg = %addr(Msg1);
Dsply Msg '' Result;
Procedurex();
ptr_Msg = %addr(Msg3);
Dsply Msg '' Result;
*inLR = *on;
/End-Free
****************************************************
P ProcedureX B
D PI
D****Remove or comment out the next line of code and the program will
work
D C s 10a based(ptr_Msg)
/Free
ptr_Msg = %addr(Msg2);
Dsply Msg '' Result;
Return;
/End-Free
P E
****************************************************
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact
[javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.