Re: Problem with dates while converting RPGIII to IV

I (we) didn't know that one (*Datetime, I mean). I've already gone too
far to be able to use it, which is a shame as it would have saved so
much time. At least most of the fields have been properly fixed. We
had a standard where we were obliged to use the P with a MOVEL, so I
ended up with a lot of MOVEL(P) to date fields which wouldn't compile.
I changed those to EVAL. But there are still some moves in there.

Thanks, anyway.

2012/9/12 Barbara Morris <bmorris@xxxxxxxxxx>:

On 2012/9/11 10:26 AM, Michael Schutte wrote:

Couldn't you put in the HSPECS
H CvtOpt(*DATETIME)
to resolve this issue.

If all you are doing is converting from RPGIII to RPGIV, this should work.

That seems like a good idea for the first step in the conversion. Then
Dave can gradually work through the source members that still have
CVTOPT(*DATETIME) and fix them so they handle those fields as true dates.

I guess the danger is that once it's working that way, it will be
considered "not broken" and they will never get changed to use true dates.
--
This is the RPG programming on the IBM i / System i (RPG400-L) mailing list
To post a message email: RPG400-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/rpg400-l.