The INCLUDE statements will work fine, though you have to have the corresponding DD statements in your JCL. There are alternatives --
- Code: Select all
//L.SYSIN DD DISP=SHR,DSN=data-set-name-of-object-for-program1
// DD DISP=SHR,DSN=data-set-name-of-object-for-program2
// DD *
more Binder control statements
You can also place the object decks into a PDS, possibly with alias names that conform to external entry names, and specify the PDS using
- Code: Select all
//L.SYSLIB DD DISP=SHR,DSN=name-of-PDS-library
A final possibility is to link the object decks into a PDS using the NCAL option so no external libraries are searched specifying member and alias names as for my second example, and then specify the PDS as a SYSLIB. In the long run you may find the SYSLIB idea more convenient than having a lot of DD statements, though if your ultimate goal is to prepare you system for external distribution for installation through SMP you'll find
- Code: Select all
INCLUDE ddname(member)
more convenient than using SYSLIB.