RE: System Date Problem

LPAR is out, because of the cost to do it.

        Isn't the date format part of the locale?  In other words, by
specifying a different locale in the user profile, he'd get the correct
format without needing the DCR, wouldn't he?  Doesn't matter much since he's
using QDATE instead of the job date, so changing the format of the job date
doesn't help.
Changing the user profile looks promising. 

Sorry, I meant UDATE.  We have a lot of old RPG code that we are not going
to convert to RPGLE {ain't broke...don't fix}.

Thanks.  It looks like it is going to be a lot of work & testing.

\Vincent

 -----Original Message-----
From:   Bob Cozzi [mailto:cozzi@xxxxxxxxx] 
Sent:   October 7, 2004 3:32 PM
To:     'RPG programming on the AS400 / iSeries'
Subject:        RE: System Date Problem

You can:
1) Change the job using CHGJOB and specify the desired date format.
2) Change your CL so that in addition to the date, you retrieve the job's
date format and then act accordingly.
3) Already have code that is date-format independent (you should be here
anyway.)
4) Explain exactly what you mean by RPG IV programs use "QDATE"?.  QDATE is
a system value, whereas RPG IV uses true date fields, or the old fashion
*DATE/UDATE fields (which should be avoided). 

-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx [mailto:rpg400-l-bounces@xxxxxxxxxxxx]
On Behalf Of Forbes, Vincent
Sent: Thursday, October 07, 2004 2:12 PM
To: 'RPG programming on the AS400 / iSeries'
Subject: System Date Problem

We are going to merge 2 development boxes into one & upon looking at the
system values, we found that one group has the system value QDATFMT "Date
format" set to MDY & the other has it set to YMD.

Is there a simple way {without changing all programs} to get around this?
In other word, when one application's RPG {LE} program uses QDATE, it gets
it in MDY format while the other application get it in YMD format.

Vincent Forbes
CIBC