The ISPF Software Configuration and Library Manager facility (SCLM) is a software configuration management (SCM) product that is included at no additional cost in base IBM z/OS®.
IBM Breeze for SCLM for z/OS, IBM SCLM Suite Administrator Toolkit, IBM SCLM Developer Toolkit, and IBM Enhanced Access Control for SCLM along with SCLM comprise the IBM z/OS SCLM family of products.
These products, when used together, provide a complete solution for centrally managing all your application development, including Java™, HTML, and traditional IBM S/390® application development.
SCLM is a feature of Interactive System Productivity Facility (ISPF), which is included with the z/OS operating system. If you are a z/OS user, then you already have SCLM.
A library manager and a configuration manager
As a library manager, SCLM:
As a configuration manager, SCLM knows how all the pieces of your application fit together. In SCLM, this is not limited to just standard source, object, and load modules. You can specify additional relationships in SCLM to associate your other data, such as test cases, publications, and JCL, with the application.
The SCLM build function translates your inputs into outputs. In SCLM, this is not limited to just compiling source code and linking object modules. You can use build to drive most any procedure that translates an input into an output.
On a promote, SCLM ensures that all your inputs and outputs are in synch. You no longer have to worry about one of your production load modules not matching the source in your production source libraries.
Change management and impact analysis
In SCLM, you can associate a change code with a member, and then build, promote, and report based on change code(s).
SCLM also provides a sample interface to IBM Tivoli® Information Management for z/OS. Tivoli Information Management is a problem and change management system that tracks problem and change records to completion.
When using this product with SCLM, you must enter a change code when modifying or creating a member. SCLM checks the Tivoli Information Management database to determine whether or not a problem or change record exists for that change code.
If not, then you cannot update or create the member. This interface can be extended to perform additional processing or to use additional points of interaction.
SCLM also provides impact analysis. Build and promote in report mode allow you to perform a what-if analysis of what may be impacted (for instance, which load modules need to be rebuilt for a specific copybook change) by a change before an actual build or promote is performed.
The Database Contents Utility allows you to produce customized reports of the contents of your SCLM controlled applications based on a number of different criteria.
The Architecture Report provides you with information on how all the pieces of your application are related. You can use IBM WebSphere® Studio Asset Analyzer for z/OS to perform additional and more granular impact analyses.
You can use WebSphere Studio Asset Analyzer to determine which programs and other elements are affected by changing the length of a specific data field within a program. For instance, what would the impact be if I were to make the zip code field ten characters rather than the current five?
SCLM and ISPF key functions
If you are currently using ISPF, then you already know how to use some of the key functions of SCLM.
SCLM view and browse functions are the same as its ISPF counterparts. The SCLM edit function is built on top of ISPF edit. It supports the ISPF edit macros and commands, language-sensitive editing, and the Edit Compare tool.
From a user's perspective, an SCLM edit is no different than an ISPF edit. All the SCLM processing to verify the group being used and to draw down and lock the member is transparent to the user.
An ISPF configuration table option determines whether or not a member can be accessed from outside of SCLM. Even if such access is allowed, SCLM is smart enough to know when the data has been changed and does not allow a build or promote until the member is either edited again from the SCLM editor or migrated back into SCLM using the Migration Utility.