Customizing File Manager to use library management system libraries

File Manager provides the facility to allow you to access source code stored in either library management (LM) or source code management (SCM) systems.

The difference between library management systems and source code management systems is not well defined, but in general, SCM systems tend to provide software packaging, version management of packages, and build management in addition to the typical LM functions. LM systems tend to be simpler and focus on efficiently storing data (files) in a library and managing versions or levels of the individual files. An example of a library management system is CA-Panvalet. An example of a source code management system is SCLM.

In this chapter both LMs and SCMs are referred to as library management systems or LMSs.

There are two possible scenarios to accessing source code in LMSs:
  • The LMS is CA-Panvalet.
  • The LMS (not CA-Panvalet) provides a SUBSYS interface.

If you want to use File Manager to access COBOL copybooks, PL/I include books, or HLASM copybooks stored in LMS libraries, the customization tasks you must perform are different, depending on which of the above scenarios applies to your LMS. The possible customization tasks are listed in Summary of steps for customizing File Manager to use LMS libraries.

Table 1. Summary of steps for customizing File Manager to use LMS libraries
Step Description
__ 1 Determine if your LMS provides a SUBSYS interface.
__ 2 Set the LMS and LMSUBSYS options, as necessary. See LMS.
__ 3 Ensure that the correct release of Language Environment® is available to File Manager. See the third bullet point in Accessing source code in an LMS with SUBSYS interface.