Re: What good is ILE?

[Michael Ryan <michaelrtr@xxxxxxxxx>]

Not quite what I meant Vern...I meant that one could take all the
procedures (through service programs and modules) and have one binding
directory in your H spec. That would satisfy the need to have access to all
the procedures on the system. It would be unwieldy IMO, but it's doable.
And yes, you're right - you can have multiple BNDDIR entries in your H
specs.


On Mon, Feb 4, 2013 at 10:45 AM, Vernon Hamberg <vhamberg@xxxxxxxxxxxxxxx>wrote:

> Hi Michael
>
> I may have misunderstood your comment - did you mean to say that we can
> put only one binding directory in the H-spec? I think it is actually a
> list - in fact, I seem to remember having more than one in code at a
> former employer.
>
> So it is already possible to list multiple binding directories within
> the source.
>
> And this kind of thing can be done with /copy or /include
>
> Vern
>
> On 2/4/2013 9:33 AM, Michael Ryan wrote:
> > That could be done with one line in an H spec, right? Specify a binding
> > directory with all the service programs and/or modules. I think it would
> be
> > better to have multiple binding directories, but it's possible.
> >
> >
> > On Mon, Feb 4, 2013 at 10:20 AM, Steve Richter <stephenrichter@xxxxxxxxx
> > wrote:
> >
> > > On Sun, Feb 3, 2013 at 8:17 PM, w 4038 <window4038@xxxxxxxx> wrote:
> > > > What good is ILE??
> > > >
> > > > Before ILE, if you needed to call program B from program A, a simple
> CALL
> > > > statement did the job.
> > > > All you had to worry about was the library list and it was up to you to
> > > > pass parameters correctly.
> > > >
> > > > Then IBM introduced ILE.
> > > > Now you can worry about, Activation Groups,Binding Directories, Binder
> > > > Language, subprocedures, service programs, Static Binding, Dynamic
> > > Binding,
> > > > Bind by Reference and some I can't recall right now.
> > > I agree with the complaint about the complexity of ILE.  The compiler
> > > and OS should be able to abstract a lot of the complexity away. Should
> > > not need procedure prototypes and binding source. Even binding
> > > directories and the listing of service programs to bind to at create
> > > time. Some sort of a system maintained directory of all the procedures
> > > in all the service programs in a library could serve as the basis of a
> > > way the system would find a procedure at run time.
> > >
> > > -Steve
> > > --
> > > This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
> list
> > > To post a message email: MIDRANGE-L@xxxxxxxxxxxx
> > > To subscribe, unsubscribe, or change list options,
> > > visit: http://lists.midrange.com/mailman/listinfo/midrange-l
> > > or email: MIDRANGE-L-request@xxxxxxxxxxxx
> > > Before posting, please take a moment to review the archives
> > > at http://archive.midrange.com/midrange-l.
>
> --
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
> To post a message email: MIDRANGE-L@xxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/mailman/listinfo/midrange-l
> or email: MIDRANGE-L-request@xxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/midrange-l.