×

Good News Everybody!

The new search engine is LIVE!

Please report any problems to david (at) midrange.com.




Did removing the plus signs fix it for you?

Remember that you can do math on a callp.  For example:
callp myproc(1+2: prefix + body + suffix)

Rob Berendt
-- 
"They that can give up essential liberty to obtain a little temporary 
safety deserve neither liberty nor safety." 
Benjamin Franklin 




"Reeve Fritchman" <reeve@xxxxxxxxxx>
Sent by: rpg400-l-bounces@xxxxxxxxxxxx
02/18/2003 08:50 AM
Please respond to RPG programming on the AS400 / iSeries
 
        To:     "'RPG programming on the AS400 / iSeries'" 
<rpg400-l@xxxxxxxxxxxx>
        cc: 
        Fax to: 
        Subject:        RE: RNF7421 errors


"+" signs aren't necessary...

-rf


> -----Original Message-----
> From: rpg400-l-bounces+reeve=ltl400.com@xxxxxxxxxxxx [mailto:rpg400-l-
> bounces+reeve=ltl400.com@xxxxxxxxxxxx] On Behalf Of Jeff Crosby
> Sent: Tuesday, February 18, 2003 8:05 AM
> To: RPG400-L@xxxxxxxxxxxx
> Subject: RNF7421 errors
> 
> I'm getting a new error that I've never seen before.  At the end of my
> compile I get the following errors:
> 
> *RNF7421 30   2198 175400  Operands are not compatible with the type of
> operator.
> *RNF7421 30   2211 176700  Operands are not compatible with the type of
> operator.
> *RNF7421 30   2212 176800  Operands are not compatible with the type of
> operator.
> 
> The statements referred to (2198, 2211, & 2212) are parms in a CallP
> that look like this (I remove some blank spaces to hopefully keep the
> lines from wrapping.  This is from the compile listing.):
> 
> 2197 C                   CallP              GetDtlCntDta(ITNBR:  +
> 2198 C                                     (error-->)    PIDATE: +
> 2199 C                                                   SLTNC:  +
> 2200 C                                                   SLTCS:  +
> 2201 C                                                   SLTUN:  +
> 2202 C                                                   SLTWT:  +
> 2203 C                                                   EXCNC:  +
> 2204 C                                                   EXCCS:  +
> 2205 C                                                   EXCUN:  +
> 2206 C                                                   EXCWT:  +
> 2207 C                                                   RCTNC:  +
> 2208 C                                                   RCTCS:  +
> 2209 C                                                   RCTUN:  +
> 2210 C                                                   RCTWT:  +
> 2211 C                                     (error-->)    ExcDsc: +
> 2212 C                                     (error-->)    RctDsc)
> 
> 
> The Fields PIDATE, ExcDsc, and RctDsc are those with errors.  Their D
> specs follow:
> 
> 139 D EXCDSC          S            225A
>    143 D PIDATE          S               D
DATFMT(*ISO)INZ(D'9999-12-31')
> 144 D RCTDSC          S            225A
> 
> 
> 
> The service program prototype that was copied in looks like this:
> 
> 580+D GetDtlCntDta    PR
> 581+D  ITNBR                         6A   Const
> 582+D  PIDATE                         D   Const
> 583+D   SCNTN                        3P 0
> 584+D   SCNTC                        5P 0
> 585+D   SCNTU                        3P 0
> 586+D   SCNTW                        7P 2
> 587+D   ECNTN                        3P 0
> 588+D   ECNTC                        5P 0
> 589+D   ECNTU                        3P 0
> 590+D   ECNTW                        7P 2
> 591+D   RCNTN                        3P 0
> 592+D   RCNTC                        5P 0
> 593+D   RCNTU                        3P 0
> 594+D   RCNTW                        7P 2
> 595+D   ExcDesc                    225A
> 596+D   RctDesc                    225A
> 
> I have another program that compiles successfully, but not this one.
> The error doesn't sound like a parm mismatch, it seems more like an
> incorrect compile option, but I don't see it.  I've tried it without the
> Const in there as well, with no luck.  Any suggestions?
> 
> Thanks.
> 
> --
> Jeff Crosby
> Dilgard Frozen Foods, Inc.
> P.O. Box 13369
> Ft. Wayne, IN 46868-3369
> 260-422-7531
> 
> The opinions expressed are my own and not necessarily
> the opinion of my company.  Unless I say so.
> 
> 
> 
> _______________________________________________
> This is the RPG programming on the AS400 / iSeries (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.



_______________________________________________
This is the RPG programming on the AS400 / iSeries (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.



As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2026 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.