RE: Procedure to set global variable

You could have separate Set... and Get... procedures that are wrappers for this special procedure of yours to make it easy on the calling program. Although I'm not particularly fond of fusing what I believe to be two completely procedures into one (i.e. a SetGet... procedure).

-Kurt

-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx [mailto:rpg400-l-bounces@xxxxxxxxxxxx] On Behalf Of David FOXWELL
Sent: Tuesday, October 13, 2009 2:19 AM
To: RPG programming on the IBM i / System i
Subject: RE: Procedure to set global variable

-----Message d'origine-----
[mailto:rpg400-l-bounces@xxxxxxxxxxxx] De la part de Ken Sims

But another way is to make the SetTransactionCode procedure a
SetGet procedure. Make the transaction code parameter
*NOPASS. Add a return value for the transaction code.

When passed a transaction code, that value is saved and also returned.

When not passed a transaction code, the saved value is returned.

Then the transaction code can be saved in a STATIC variable
local to the SetGet procedure.

I've tried this out and I rather like it.

But how would you name this procedure?

If I do SetTransactionCode then GetTransActionCode, the program code is self-documenting. SetGetTransActionCode needs commenting. I called it InzTransActionCode.