LINKLIST definitions in PROGxx

LINKLIST definitions for Developer for z/OS® can be grouped in three categories:
  • Developer for z/OS load libraries that are needed for Developer for z/OS functions. These definitions are described in this section.
  • Requisite load libraries that are needed for Developer for z/OS functions. These definitions are described in Requisite LINKLIST and LPA definitions.
  • Developer for z/OS load libraries that are needed by other products. These definitions are described in LINKLIST definitions for other products.
Table 1. Match load modules to functions. This table describes the functions of load modules and the load libraries where they are located.
Load library Load modules Usage STEPLIB
FEL.SFELLMOD IRZ* and IIRZ* Diagnostic IRZ messages for Enterprise Service Tools CICS®, IMS, or MVS batch
FEL.SFELLOAD AZU* and IAZU* xUnit support for Enterprise COBOL and PL/I (Deprecated) zee.env or MVS batch
CRA* Common Access Repository Manager (CARMA) CRASUB* or crastart*.conf
ELAX* ELAXF* remote build procedures

(error feedback and include preprocessor)

 ELAXF* procedures
FEJB* CICS bidirectional language support CICS
FEL.SFELLPA CRA* Common Access Repository Manager (CARMA) CRASRV.properties

In order for the listed Developer for z/OS services to work, all modules documented in Table 1 that are related to the service must be made available either through STEPLIB or LINKLST (or LPA). Note that the SFELLMOD library is not used by Developer for z/OS itself, but by code generated by Developer for z/OS. See the STEPLIB column in Table 1 if you choose to use STEPLIB to learn where the STEPLIB (or DFHRPL for CICS) definition must be made. However, you should be aware of the following things:

  • Using STEPLIB in z/OS UNIX has a negative performance impact.
  • If one STEPLIB library is APF-authorized, then all must be authorized. Libraries lose their APF authorization when they are mixed with non-authorized libraries in STEPLIB.
  • Libraries added to the STEPLIB DD in a JCL are not propagated to the z/OS UNIX processes started by the JCL.

LINKLIST data sets are defined in SYS1.PARMLIB(PROGxx), if your site followed IBM® recommendations. Define PROG=xx in the IEASYSxx parmlib member to specify which PROGxx parmlib member should be used during IPL.

The required definitions will look like the following, where listname is the name of the LINKLIST set that will be activated, and volser is the volume on which the data set resides if it is not cataloged in the master catalog:
  • LNKLST ADD NAME(listname) DSNAME(FEL.SFELLMOD) VOLUME(volser)
  • LNKLST ADD NAME(listname) DSNAME(FEL.SFELLOAD)
LINKLIST definitions can be created dynamically (until the next IPL) with the following actions:
  1. Create a new PARMLIB member named PROGxx, for example PROGLL.
  2. Place the following commands in your new PROGxx member, where volser is the volume on which the data set resides if it is not cataloged in the master catalog:
    • LNKLST DEFINE,NAME=LLTMP,COPYFROM=CURRENT
    • LNKLST ADD NAME=LLTMP,DSN=FEL.SFELLMOD,VOL=volser
    • LNKLST ADD NAME=LLTMP,DSN=FEL.SFELLOAD
    • LNKLST ACTIVATE,NAME=LLTMP
  3. Activate the new definitions by issuing the SET PROG=xx console command, where xx matches the last 2 characters of your new PROGxx member name.