Re: Procedure with varying parm

> Procedure 1 returns a variable length field and
> procedure 2 receives a variable length field.
> Procedure 2 is getting memory garbage in its
> input parm.  Any ideas?

That's the way it works.  P1 initialises 51 bytes of storage and P2 is
reading 1024 bytes of storage (which have only the first 51 bytes set
to a known value.)  The answer is to make P2 only use the number of
bytes that P1 sets.  You can look into %len, operational descriptors,
and passing another parameter indicating the size of P1's variable and
see what works best for your situation.
  --buck