Re: Costly PSDS

albartell wrote:

One last question.  Obviously the "costly to obtain" is relative to your
machine, but it would be better if I had something to relate it to.  For
instance, it is more costly to have a 65535 character variable vs. a 65535
VARYING character variable if you needed to %trim a lot on that variable.
That may not be apples to apples, but I am just trying to grasp what "costly
to obtain" means.  If it was costly as in "similar to having to start the
JVM for your job" I would definitely go another route.

I wouldn't worry about it.  It's nothing like starting the JVM; not even
close to the cost of opening a file.  Depending on the actual length of
the PSDS, the RPG runtime may have to call a couple or a few extra
functions during the *INIT phase of the cycle.

The first 80 bytes of the PSDS are filled up at compile time; some of
the later subfields are too.  But some of the subfields require calling
a function or two to get the information.  Say your PSDS is over 80
bytes long, it would have to figure out what library your program is
in.  If it's over 190 bytes long, it would have to fetch the job date. 
Over 343 bytes long, it has to figure out what module the procedure is
in.