RE: Procedure to set global variable

[David FOXWELL <David.FOXWELL@xxxxxxxxx>]

 Thanks, Larry.

> -----Message d'origine-----
> [mailto:rpg400-l-bounces@xxxxxxxxxxxx] De la part de Larry Ducie

> If you feel the transaction code does NOT form part of the 
> state of the module then please don't create a GetSetInitView 
> procedure to manage it as a local static variable. You could 

I do feel that this is the case.

> consider using ANOTHER module. You would store the variable 
> as a global variable in that module and provide various 
> procedures to Get/Set/Init/View the value held there. The 
> variable is now only viewable by your procedures designed to 
> work with it. You could go further and place ALL transaction 
> code related variables and accessor/mutator procedures in 
> this module. Further still, you could wrap it in a service 
> program and call it TRANSCODE. That way you have an object 
> that represents the transaction code, all of its associated 
> attributes, and all of its functions.
>
> Got to be better than using local static variables and 
> horribly disfigured procedures for this.

However, I don't know if I appreciate the advantage of a separate module over a static variable. 
Adding a module is a lot more difficult for me, as we only bind by copy. I know we shouldn't but we're working on that. Adding a call to a procedure in another module here will mean recompiling the whole kit and kaboodle.