Hey List,
So I entered a PMR to report an issue where an implied subfield definition was appearing as Unknown(0) in the outline.
Example:
D ds_Cust DS Qualified Inz
D Data Dim( 999999 ) Ascend
D Cust# 6p 0 Overlay( Data: *next ) Inz
D Cycle 1a Overlay( Data: *next ) Inz
D DropCDRs n Overlay( Data: *next ) Inz
D TLRNRating n Overlay( Data: *next ) Inz
The outline gives the definition for Data as Unknown(0). But the compiler understands it.
I reported this because I would think that seeing Uknown(0) in your product would be bad. How often would I reference/use the definition of this kind of subfield? Rarely.
Well, I was told that this would require a RFE. I disagree because the software isn't supporting existing RPG coding techniques, but at this point I guess I just don't care that much about it. So, I figured I'd write the list to see if anyone would benefit from me arguing the point with IBM (or sighing and entering an RFE). Otherwise I'll just let it drop.
Thanks,
Kurt Anderson
Sr. Programmer/Analyst - Application Development, Service Delivery Platform
[cid:image002.jpg@01CD16F9.25D27630]
web: www.customcall.com<
http://www.customcall.com/> | email: kurt.anderson@xxxxxxxxxxxx<mailto:kurt.anderson@xxxxxxxxxxxx>
A Division of Enghouse Systems Ltd.<
http://www.enghouse.com/> (TSX:ESL)
As an Amazon Associate we earn from qualifying purchases.