Re: Defining, or using, dates on a command definition

rob@dekko.com wrote:
> This is a multipart message in MIME format.
> --
> [ Picked text/plain from multipart/alternative ]
> I have an RPGLE program with the following:
>      FDIRLOCAL01IP   E           K DISK
>      ...
>      D DIRSUMPRT       PI      *entry PLIST
>      D DATE1pm                             LIKE(RUNDATE) CONST
> OPTIONS(*NOPASS)
>      D DATE2pm                             LIKE(RUNDATE) CONST
> OPTIONS(*NOPASS)
>
> From the command definition:
> CMD        PROMPT('Compare summarized directories')
> PARM       KWD(FIRSTDATE) TYPE(*DATE) CHOICE(DATE) +
>              PROMPT('First date')
> PARM       KWD(NEXTDATE) TYPE(*DATE) CHOICE(DATE) +
>              PROMPT('Next date')
>
> From the command line:
> DIRSUMPRT FIRSTDATE('07152002') NEXTDATE('07172002')
 > ...

The F1 help text for the CMD PARM statement indicates that a *DATE
value is always passed to the command processing program as a
character string in CYYMMDD format.  Since date variables in your
RPG program cannot be defined with DATFMT(*CYMD0), it would appear
that you must define your parameters as 7A in your RPG program.  If
you want to deal with the values in date variables, you then need to
convert to date type using built-in %DATE(PARM:*CYMD0).

Hans