IEH was for system utilities; IEF, application or dataset oriented. It was 
IEFBR14, which was used mainly for preallocating datasets for a job. It, 
unfortunately, had a bug that made it difficult to use in a large job that had 
general checks for return codes - it didn't zero R15 before doing the BR R14, 
so its return code was always its entry point. I know that this defect was 
APARd as early as O/S 360 Release 15. It was not fixed until much later, 
Release 21.1 IIRC. We had our own version for all of the years that I supported 
O/S 360.


Regards,
Richard Schuh


> -----Original Message-----
> From: VM/ESA and z/VM Discussions [mailto:[EMAIL PROTECTED]
> Behalf Of Anne & Lynn Wheeler
> Sent: Sunday, October 09, 2005 8:10 AM
> To: VMESA-L@LISTSERV.UARK.EDU
> Subject: Re: IEH/IEB/... names?
> 
> 
> [EMAIL PROTECTED] wrote:
> > Perhaps you know the answer:
> > long ago I used IBM mainframes.
> > Utilities started with IEH, IEB, etc.
> > What were the rules for those prefixes?
> >
> > I remember IEHLIST (list files) and IEBGENER (file copy).
> > Wasn't IEHBR14 the null program so the JCL's DD side-effects
> > could occur (such as file creation or deletion)?
> >
>

Reply via email to