RE: %ADDR() in a DS is not resolving to the correct value.

Thanks for the suggestion Mark.

Unless the rules for defining this pointer are different between *PGM and *SRVPGM, then it is defined correctly. This is based on the success of the *PGM version of the condition handler and the fact that it works just fine as a *SRVPGM when used in my tame test program.

Steve Needles

-----Original Message-----
From: RPG400-L [mailto:rpg400-l-bounces@xxxxxxxxxxxx] On Behalf Of mlazarus
Sent: Friday, May 13, 2016 12:52 PM
To: RPG programming on the IBM i (AS/400 and iSeries)
Subject: Re: %ADDR() in a DS is not resolving to the correct value.

Steve,

I haven't looked in the manual, but if I had to guess I would say that CONST on the CommArea parm should not be there.

-mark

On 5/13/2016 1:34 PM, Needles,Stephen J wrote:

OS version is 7.2.

I've a program that uses a registered condition handler that is a *SRVPGM.

There is a copybook that contains the data structures, prototypes and other variables that define the interaction between the failing program and the condition handler using IBM's CEEHDLR API.

Among the DS's is the PSDS and the Communication Area used for the condition handler. This was all developed according to IBM's examples many years ago.

The Communication Areas DS contains a pointer to the failing program's PSDS. It is defined as follows:

* Communication area *
*---------------------------------------------------------------
D CommArea DS NOOPT
D CA_pPsds * INZ(%ADDR(PGM_PSDS))

The DS to pass control to the registered handler includes the above DS:

* CEEHDLR Interface *
*------------------------------------------------------
D CEEHDLR PR
D pConHdlr * PROCPTR
D CommArea * CONST
D Feedback 12A OPTIONS(*OMIT)

The problems are that when the program is initialized, the pointer is supposed to have a value, it does not.

When the %addr() is obtained in the c-specs, it finds the correct address for the PSDS.

eval CA_pPsds = %ADDR(PGM_PSDS);

The impact is that as the condition handler accepts control from the failing program, the address is invalid and the condition handler cannot resolve the address, so it fails.

When the address is forced in the c-spec, all works as expected.

I don't think that the *SRVPGM angle has anything to do with the error as my tame test program works just fine.

Anyone got any ideas? Barbara? :)

Steve Needles

________________________________
This communication, including attachments, is confidential, may be subject to legal privileges, and is intended for the sole use of the addressee. Any use, duplication, disclosure or dissemination of this communication, other than by the addressee, is prohibited. If you have received this communication in error, please notify the sender immediately and delete or destroy this communication and all copies.

TRVDiscDefault::1201

--
This is the RPG programming on the IBM i (AS/400 and iSeries) (RPG400-L) mailing list To post a message email: RPG400-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives at http://archive.midrange.com/rpg400-l.

Please contact support@xxxxxxxxxxxx for any subscription related questions.