RE: Compile error - why?

[Rich Duzenbury <rduz@xxxxxxxxxxxxxxxxxxx>]

Uh, yeah, I kind of gathered.  I'm trying to figure out why (Hans?) such a
restriction is in place.  It seems a bit silly.  Kind of like not being
able to level break (cycle) on a binary field.

I did find out that after V4R5 it gets easier, as the %char bif can
supposedly take an additional parameter for the conversion format.

At 05:30 AM 10/4/02, you wrote:
> VARRYING is not allowed with this date conversion.
> it should be fixed length character variable...
>
> Be ignorant than urban insane
> Smile :-) from your Heart
>
> > -----Original Message-----
> > From: Rich Duzenbury [SMTP:rduz@westernmidrange.com]
> > Sent: Friday, October 04, 2002 2:51 AM
> > To:   rpg400-l@midrange.com
> > Subject:      Compile error - why?
> >
> > Hi,
> >
> > I'm getting a compile error on this.  What is that rationale for not
> > allowing one to move from a date field into a VARYING alpha field?  This
> > machine is on V4R5, btw.  Now it looks like I'll have to declare a
> > non-varying field to accept the data, and then do an extra move or eval to
> > get the data over into $tagval.
> >
> > D work_date       S               D
> > D $tagval         s            512    VARYING
> > C     *usa          movel     work_date     $tagval
> >
> > *RNF7560 30      1 Variable-length field is not allowed with this
> > operation.
> >
> > Curious.