Re: using a defined constant to dimension an array

- and while we're at it: INZ( %ADDR( whatever )) has the same problem of not
being properly initialized on subsequent calls to a subprocedure...

Best regards,
Carsten

----- Original Message -----
From: <owner-rpg400-l@midrange.com>
To: <RPG400-L@midrange.com>
Sent: Wednesday, July 04, 2001 8:18 AM
Subject: Re: using a defined constant to dimension an array




?
Barbara wrote:
>By the way, INZ(*SYS) (but not INZ(*JOB)) is allowed in subprocedures
>starting in V4R4.

Yeah, but it's broke!  (Well certainly for TIME and TIMESTAMP and I assume
DATE too).  I raised APAR SA92403 for this problem.  The issue is that a
TIME or TIMESTAMP (and probably DATE) data structure subfield initialised
to *SYS defined in a subprocedure is not reinitialised on subsequent calls
to the procedure.  (Since INZ(*SYS) and INZ(*JOB) arrived in VRM370, not
supporting them in procedures until VRM440 seems a silly oversight.  And
why can't I use INZ(*JOB) in a procedure?)



+---
| This is the RPG/400 Mailing List!
| To submit a new message, send your mail to RPG400-L@midrange.com.
| To subscribe to this list send email to RPG400-L-SUB@midrange.com.
| To unsubscribe from this list send email to RPG400-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---