RE: dates as parms

Barbara,
That could very well be the issue, but it was with *JOBRUN. I seem to
recall it being related to using UDATE (to move it into a date field)
and relying on *JOBRUN to be the format of UDATE. But UDATE is in the
format of DATFMT(*JOB), therefore
*JOBRUN     MOVE  UDATE    myDate
Would not work in a job where the job date format is different. I
believe this is where I was coming from...  Today, the work around would
simply be using TIME or *JOB to initialize a date field instead of using
UDATE to do it.
Thanks.
Bob Cozzi
cozzi@rpgiv.com
Visit the new on-line iSeries Forums at: http://www.rpgiv.com/forum

> -----Original Message-----
> From: rpg400-l-admin@midrange.com [mailto:rpg400-l-admin@midrange.com]
On
> Behalf Of bmorris@ca.ibm.com
> Sent: Monday, August 20, 2001 12:58 PM
> To: rpg400-l@midrange.com
> Subject: RE: dates as parms
>
>
> >From: "Bob Cozzi \(RPGIV\)" <cozzi@rpgiv.com>
> >Date: Wed, 15 Aug 2001 18:04:52 -0500
> >
> >Isn't *JOBRUN the job date format for the job that compiles the RPG
> >program, not the job running the RPG program... at least it used to
work
> >like that (we never liked it working that way so if it's changed,
it's a
> >good thing).
>
> Bob, *JOBRUN is the date format at runtime.  It always worked like
that.
>
> Maybe you're thinking of DATFMT(*JOB) in DDS which is still, as far as
> I know, the date format at compile-time of the file.
>
> Barbara Morris
>
> _______________________________________________
> This is the RPG programming on the AS400 / iSeries (RPG400-L) mailing
list
> To post a message email: RPG400-L@midrange.com
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/cgi-bin/listinfo/rpg400-l
> or email: RPG400-L-request@midrange.com