RE: Parm identification routine...

[Gene_Gaunt/ReviewWorks@xxxxxxxxxxxxxxx]

Steve's DSPPARM program can rout out hidden exit points like the one that
OPM RPG/400 calls when compiling a device type of  ^^^^ (four uppercase
6's) in an F-spec columns 40-43 like the following.

     FINPUT   IF  F      80            ^^^^
     IINPUT   NS  01
     C                     READ INPUT                    LR

Do you think this code makes the compiler return fatal error QRG2013, "The
Device-Type entry is not PRINTER, DISK, WORKSTN, SPECIAL, or SEQ" ?  No,
this code makes the compiler fail with MCH3401, "Cannot resolve to object
CARDFILE.  Type and Subtype X'0201' Authority X'0000' ".

Okay, lets rename Steve's program into CARDFILE in our library list.  Now
compile the OPM RPG/400 again and the compiler fails with CPF6301,
"Intermediate representation of program (IRP) contains 11 errors."

My point here is entertainment (not a bug report, jeez guys) but maybe
another MI400er knows the history of this fossil CARDFILE.


+---
| This is the MI Programmers Mailing List!
| To submit a new message, send your mail to MI400@midrange.com.
| To subscribe to this list send email to MI400-SUB@midrange.com.
| To unsubscribe from this list send email to MI400-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: dr2@cssas400.com
+---