From mboxrd@z Thu Jan  1 00:00:00 1970
X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00,FREEMAIL_FROM
	autolearn=ham autolearn_force=no version=3.4.4
X-Google-Language: ENGLISH,ASCII-7-bit
X-Google-Thread: 103376,e6a2e4a4c0d7d8a6
X-Google-Attributes: gid103376,public
X-Google-Thread: 101deb,3488d9e5d292649f
X-Google-Attributes: gid101deb,public
X-Google-ArrivalTime: 2003-02-22 05:14:10 PST
Path: 
 archiver1.google.com!news1.google.com!newsfeed.stanford.edu!logbridge.uoregon.edu!snoopy.risq.qc.ca!nf3.bellglobal.com!cyclone.mw.ipsvc.net!news.mw.ipsvc.net!cyclone.kc.rr.com!news-west.rr.com!cyclone.nyroc.rr.com!cyclone-out.nyroc.rr.com!twister.nyroc.rr.com.POSTED!53ab2750!not-for-mail
Message-ID: <3E574C46.2F195258@yahoo.com>
From: Peter Flass <peter_flass@yahoo.com>
X-Mailer: Mozilla 4.75 [en] (Win98; U)
X-Accept-Language: en
MIME-Version: 1.0
Newsgroups: comp.lang.pl1,comp.lang.ada
Subject: IEFBR14, was Re: status of PL/I as a viable language
References: <f2rb5v8020kkvq6tsf0uqg91pfbk9errs7@4ax.com>
 <E65DA1BAEE8B3C52.29B16126289D882E.5EB549036373C4E5@lp.airnews.net>
 <b366jv$j2r$1@sparta.btinternet.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Date: Sat, 22 Feb 2003 13:04:06 GMT
NNTP-Posting-Host: 24.194.50.82
X-Complaints-To: abuse@rr.com
X-Trace: twister.nyroc.rr.com 1045919046 24.194.50.82 (Sat,
 22 Feb 2003 08:04:06 EST)
NNTP-Posting-Date: Sat, 22 Feb 2003 08:04:06 EST
Organization: Road Runner
Xref: archiver1.google.com comp.lang.pl1:4420 comp.lang.ada:34418
Date: 2003-02-22T13:04:06+00:00
List-Id: <comp.lang.ada>

Pointless Harlows wrote:
> 
> "John R. Strohm" <strohm@airmail.net> wrote in message
> > Actually, it IS possible to create perfect code.
> 
> You may recall the perfect IBM mainframe utility routine IEFBR14 ;-)
> 
> However, I did hear it said once that even the first version of IEFBR14 had
> a fault in that it didnt return a zero return code.
> Can anyone actually confirm that?

I've head the same thing, and at one point I believe someone posted the
PTF number for the fix.  This should still be readable in the load
module, since (AFAIK) IEFBR14 hasn't been rewritten since release 1.0 of
OS/360.