Defining link-edit processed components

Standard linkage editors produce load modules as output. To define software components with load module outputs from standard linkage editors, use Linkedit Control (LEC) architecture members. LEC architecture members contain all the information necessary to produce a complete load module. Use the LEC architecture member to identify the following information:

The load module name and the type in which you want it saved
The linkage editor listing name and the type in which you want it saved
All object and other load modules the load module is to contain
Linkedit control statements and linkage editor options.

LEC architecture members must have at least one LINK, INCL, INCLD, or SINC statement and one LOAD statement.

Linkedit Control (LEC) architecture members can be constructed by referencing any combination of source members, CC architecture members, generic architecture members or LEC architecture members. Inputs to LEC architecture members are identified in the same way that inputs to CC architecture members are identified. The one difference is that by default LEC architecture members include object and load modules generated by the OBJ and LOAD statements in the input stream to the linkage editor. SINC statements can be used in LEC architecture members to identify object modules or load modules which are generated outside of the project. If SINC statements are being used to include load modules, the input ddname for the build translator must specify KEYREF=INCL. One additional statement can be used in LEC architecture members to identify an input to the linkage editor. That statement is the LINK statement. It identifies an output in the project that does not need to be rebuilt before being included in the input stream.

SCLM verifies that the inputs to the LEC architecture member are up-to-date before link-editing the inputs. SCLM will rebuild any inputs that are outputs of building other members in the project when those outputs are out-of-date. The inputs specified on LINK statements are an exception. These inputs will not be rebuilt.

You can override default linkage editor options by using the PARM statement. Use the statement as many times as necessary to specify all options you want. SCLM uses the standard S/370 linkage editor as defined by the LE370 language definition unless an LKED statement is used to override the default. See LKED within Statement uses for more information.

You can specify in the LEC that SCLM pass linkage edit control statements directly to the linkage editor by using the CMD statement. Insert the control statements along with the object and load modules by careful positioning in the LEC architecture member.

The CMD statement can be used to include object modules and load modules that are in data sets outside of the project. The language definition for the linkage editor must include a ddname referencing the data set containing the members to include.

SCLM generates linkage editor listings to temporary listing data sets so that you can view them online during the build. You can save these listings to members in the database by using the optional LMAP architecture member statement. If you do not specify the LMAP statement, the online linkage editor listings are not saved. You might choose to discard the listings because of disk space limitations. Another option is to compress the listings. The ISPF sample library ISP.SISPSAMP contains two sample members, FLM03ASM and FLM03LMC, that demonstrate how to compress SCLM listings using the PACK option on the LMCOPY service. Comments explaining how to use these members are included in the code.

You cannot use the SETSSI linkage editor command in an LEC architecture member. If SCLM finds a CMD SETSSI statement in an LEC architecture member during a build, the build function overrides the statement with its own SETSSI command.