Re: Converting *ENTRY & PLIST to free format

With these replies I am feeling better and better. Apparently it is not as elementary a problem as I thought it was.

I named the prototype and the procedure interface the same name as the program and did not include the ExtPgm() keyword. It seems to have worked just fine.

By the way, thank you for the careful and courteous replies. I appreciate that.



On 6/20/2013 2:23 PM, Brian Parkins wrote:

Converting *ENTRY & PLIST to free format.
Are there some simple examples, tutorials, and explanations on replacing
*ENTRY? I am having trouble understanding the process.

I found this on Brian May's site:
http://www.bmeyers.net/faqs/15-faqs/51-replacing-entry-plist-with-a-prototype

I fear the example on Brian MEYER'S website is not correct. The EXTPGM
keyword requires a parameter. Here are some simple examples that I have
tested:
============================================
// Module/program name is ENTRYPARM1
// Compiler warning - external program name not same as program name

D EntryPlist Pr ExtPgm('RUBBISH')
D 10A Const

D EntryPlist Pi
D String 10A Const
============================================
// Module/program name is ENTRYPARM2
// No compiler warnings

D EntryPlist Pr ExtPgm('ENTRYPARM2')
D 10A Const

D EntryPlist Pi
D String 10A Const
============================================
// Module/program name is ENTRYPARM3
// Source will NOT compile - keyword EXTPGM requires a parameter

D EntryParm3 Pr ExtPgm
D 10A Const

D EntryParm3 Pi
D String 10A Const
============================================

As Brian Meyer correctly states:

o The prototype for the main procedure must include the EXTPGM keyword.
o The procedure interface must be named (the same as the prototype).
o The prototype must precede the procedure interface.

Hope this helps.
Brian Parkins.