Placing Enterprise COBOL modules in shared storage

All of the modules in Start of changeIGY.V6R2M0End of change.SIGYCOMP that are reentrant can be included in shared storage.

To include the modules in shared storage, you can:
  • Authorize the data set Start of changeIGY.V6R2M0End of change.SIGYCOMP
  • (Optional) Include Start of changeIGY.V6R2M0End of change.SIGYCOMP in the LNKLSTnn concatenation
  • Add compiler modules to LPA dynamically after the system is IPLed
Under z/OS®, you do not need to place Start of changeIGY.V6R2M0End of change.SIGYCOMP in the LNKLSTnn concatenation to be able to load program objects into the LPA. If you choose not to add it to the LNKLSTnn concatenation, you must make the modules that are not included in the LPA available to steps that compile Enterprise COBOL applications by doing one of these steps:
  • Copying the non-LPA modules to a data set that is in the LNKLSTnn concatenation
  • Copying the non-LPA modules to a data set that can be used as a STEPLIB or JOBLIB

Using the entire Start of changeIGY.V6R2M0End of change.SIGYCOMP data set as a STEPLIB or JOBLIB defeats the purpose of placing the modules in the LPA because modules are loaded from a STEPLIB or JOBLIB before the LPA is searched.

Modules that you copy into another data set are not serviced automatically by SMP/E in that data set. You must rerun your copy job after you apply service to Enterprise COBOL to make the updated modules available in the LNKLSTnn data set or in the STEPLIB.

For more information about including modules in the LPA, see these documents:
  • z/OS MVS™ Initialization and Tuning Guide
  • z/OS MVS Initialization and Tuning Reference

If you are placing compiler phases in shared storage, code the corresponding phase options with the value OUT when you run the sample job IGYWDOPT to change the compiler options defaults. For more information, see Changing the defaults for compiler options.