Rich Hart wrote:
>  RE:  The post by James Lampert.  I was not aware that the AS/400 supported 
> PL/I

Unfortunately, it apparently doesn't any more. At V2, it was a licensed
product; at V3, it was a PRPQ; at V4, it was long gone.

It was never a particularly good subset. As I recall, list-directed
(sort of like C stdin/stdout) and data-directed (sort of like a really
good implementation of FORTRAN's NAMELIST) I/O wasn't there, and the
terminal support was particularly lousy.

But what was there worked, and worked fairly well. We had (I think) the
V3R2 version for a short time, while still on a beta test version of the
operating system, and (as I said) I used it to implement an enhanced
version of the front-end in the back of the V2R3 API manual. But since
the "TGTRLS" support in MI only came in around V5, I wasn't able to do
much with it. Nor would I have any reason to do so, since the last thing
I'd want to do with a commercial product is to have the MI programs in
it limited to some arbitrary minimum release: the minimum release level
limits C and RPG programs are enough of a pain in the <equus asinius> as
it is.

But as I said, QPRCRTPG front-ends aren't rocket science. As long as you
get the basic principles of ANY example in ANY language, you should be
able to write one in whatever language is most convenient for you.

Now if only I knew how to attach my CRTMIPGM command to the "14" option
in PDM . . .

-- 
James H. H. Lampert
Professional Dilettante
http://www.hb.quik.com/jamesl
http://members.hostedscripts.com/antispam.html
http://www.thehungersite.com

Help America's Passenger Trains. http://www.saveamtrak.org

Read My Lips: No More Atrocities!


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-2022 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.