RE: subprocedure questions

[Dan <dbcerpg@xxxxxxxxx>]

I'm going to give that a try.

Question:  In your PI (Procedure Interface), you use LIKE(MyDS), but
the data structure below defines MyDS2.  Was that intentional?  Or
would you just as soon use MyDS2?  Does the subprocedure "see" all the
variables in the main module?

TIA, Dan

--- "Haas, Matt" <Matt.Haas@thomsonlearning.com> wrote:
> Dan,
>
> There's two way's to do this, the first is to remove the 'VALUE' from
> Z_ACGAMT and Z_AMTERR which passes the variable by reference instead
> of by value so you can modify it in your subprocedure. Passing by
> value (which is what you do when you add VALUE to a parameter
> definition) is similar to declaring a constant in that you can't
> change it in the subprocedure.
>
> A better way would be to create a data structure for these two values
> and return the data structure just like you would when dealing with
> API's. This makes the program much easier to maintain if you need to
> return another field in the future. To do this, you'd do something
> like this:
>
> DMyDS             DS
> D Z_ACGAMT                       8S 2
> D Z_AMTERR                      30A
>
>
> D CVTA2N          PR                  LIKE(MyDS)
> D   ACGAMT                      10A   VALUE
>
> C               eval     MyDS = CVTA2N(ACGAMT)
>
> P CVTA2N          B
> D CVTA2N          PI                  LIKE(MyDS)
> D   ACGAMT                      10A   VALUE
>
> DMyDS2            DS
> D   X_ACGAMT                     8S 2
> D   X_AMTERR                    30A
> <snip>
> C    .........  EVAL      X_ACGAMT = N_ACGAMT
> C    .........  RETURN    MyDS2
> P                 E
>
> Matt

__________________________________________________
Do you Yahoo!?
U2 on LAUNCH - Exclusive greatest hits videos
http://launch.yahoo.com/u2