There is an API call not shown but is implicit in the LOADWorkmod API call, 
that is BINDWorkmod. The binder will call it if required during LOADWorkmod. 

The binder takes as input OBJ/XOBJ/GOFF format object modules, load modules, 
program objects and control statements. The binder provides a number of batch 
programs normally called via JCL EXEC PGM= (some of which are what the TSO 
LOAD|LOADGO are using). I say programs, but many I name here are 
aliases/alternate entry points of the same module.

The most used is called by the program named IEWBLINK | IEWL | LINKEDIT | HEWL 
(and a couple of other names). This does a SAVEWorkmod - converts a Workmod to 
Load Module or Program Object format and writes to a dataset or file - rather 
than do a LOADWorkmod.

Other interfaces are IEWBLOAD, IEWBLODI, IEWBLDGO which do use LOADWorkmod and 
respectively do bind+load, bind+load+Identify, bind+load+call (Go) using the 
binder.

There are still other batch interface programs which use the ancient linkage 
editor. HEWLKED is the analog of IEWL.
HEWLD, HEWLDI, HEWLDIA are the analogs to the other binder batch programs, the 
so-called "batch loader", they respectively do linkedit+load, 
linkedit+load+Identify, linkedit+load+Identify+attach using the ancient linkage 
editor.

I brought up the ancient linkage editor because the binder-based load programs 
like IEWBLOAD were created to provide compatible interfaces with what was 
available with the the ancient batch loader, so there would be no need for the 
ancient linkage editor. As such these binder-base programs have limitations - 
specifically the underlying LOADWorkmod API has limitations.

LOADWorkmod is doing only some of what the CSV loader can do. Most importantly 
It does not deal with multiple loadable classes in the same way as the loader. 
If there are multiple initial load text classes, they are brought into storage 
concatenated together. If there are deferred load classes, LOADworkmod will 
fail. Thus for example, most LE applications built with XPLINK or LP64 will not 
work using the batch binder programs program which use LOADWorkmod.  (Such 
program definitely cannot work if the ancient "batch loader" is used which 
knows nothing of those constructs).

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN

Reply via email to