RE: ChgJob

[CWilt@xxxxxxxxxxxx]

Scott,

I agree it does nothing as shown.

However, what if instead of
RtvJobA  Date(&Date)
ChgJob   Date(&Date)

The following was used:
RtvSysVal  SysVal(QDATE)  RtnVar(&Date)
ChgJob   Date(&Date)

Would this ensure that the job date matches the system date?  

Maybe the co-worker is remembering the method/reason backwards.

Just a thought.

Charles Wilt
iSeries Systems Administrator / Developer
Mitsubishi Electric Automotive America
ph: 513-573-4343
fax: 513-398-1121
 

> -----Original Message-----
> From: Scott Klement [mailto:midrange-l@xxxxxxxxxxxxxxxx]
> Sent: Thursday, November 18, 2004 12:12 PM
> To: Midrange Systems Technical Discussion
> Subject: Re: ChgJob
> 
> 
> Hi Tim,
> 
> >     RtvJobA  Date(&Date)
> >     ChgJob   Date(&Date)
> 
> You're correct, this does absolutely nothing except waste CPU cycles.
> 
> > He insisted it was absolutely necessary if I wanted 'UDATE' 
> to reflect
> > the job date, rather than the system date. I ran a couple 
> of tests and
> > got the same expected results with or without the ChgJob statement.
> > (UDATE reflected the job date)
> 
> Your co-worker is mistaken.  UDATE is always the job date. 
> It's never the
> system date.  (The same is true for *DATE. as well as INZ(*JOB))
> 
> If you want the system date instead, you have to use the TIME 
> op-code, or
> the %date() BIF, the %timestamp() BIF or INZ(*SYS).
> 
> What RPG really needs is another 13 or 14 ways to retrieve 
> the date. :)
> 
> --
> This is the Midrange Systems Technical Discussion 
> (MIDRANGE-L) mailing list
> To post a message email: MIDRANGE-L@xxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/mailman/listinfo/midrange-l
> or email: MIDRANGE-L-request@xxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/midrange-l.
>