RE: %Int

Hi Aaron,

> That would put make it so zeros would be put into myInt if it was
> _entirely_ blanks.  The way %Int works right now is more purist that the
> RPG cares to have it's bif's, IMO.

FWIW, I agree.  %int() as it stands is too "purist."

Right now, every time I want to use %int() or %dec() I have to do
something like this:

    monitor;
       peSup.DockNo = %int(peSup.DockNo);
    on-error;
       peSup.DockNo = 0;
       util_rmvmsg('RNX0105');
    endmon;

The util_rmvmsg() subprocedure then goes and removes the message from the
job log.  (At first, I didn't think to remove the messages from the job
log... but then I started having problems with jobs ending abnormally
because there was no space in the job log!)

It would be a really useful enhancement if they changed %int(), %dec(),
etc so that you could do something like this:

     myVar = %int(SomeString: -1);
or
     myVar = %dec(SomeString: 15: 5: -1);

So that if the assignment succeeds, the integer equivalent of "SomeString"
is stored in myVar, and if it fails, the value -1 is stored in myVar.
Preferably without all the hassle of having to remove the messages from
the job log.

That would be a really nice enhancement.