Re: Why wont prototyped (extpgm) call compile when using qualified DS fields as parms?

On 02-Dec-2015 13:16 -0600, JRusling wrote:

I have this -
d callNotesMaint pr extpgm('ORD140')
d Type 1
d Cust 6 0
d Line 4 0
d Doc 15

d uniq ds qualified
d Type 1
d Cust 6 0
d Line 4 0
d Doc 15

dzzzType s 1
dzzzCust s 6 0
dzzzLine s 4 0
dzzzDoc s 15

When I compile with zzz prefixed fields for pgm call the compile
works but when I compile with uniq. qualified DS fields for pgm call
the compile fails?

Works -
callNotesMaint(zzzType:zzzCust:zzzLine:zzzDoc);

Fails -
callNotesMaint(uniq.Type:uniq.Cust:uniq.Line:uniq.Doc);

Standalone default data typing is different than default data typing for a Data Structure (DS). IIRC, the prototype defaulted data type matches a standalone field; that would explain the difference. IMO, best to always explicitly specify the data type, so as to avoid allowing the RPG assigning a _default_ [and possibly undesired] data type.

Internal Data Type - Help

Choose from the following:

Blank

Leave the field blank for a character field, or a packed decimal
standalone field, or a zoned decimal field data structure
subfield. For zoned or packed data types, the decimal positions
field must be nonblank.

[...]