Skip to content

Implementation Checklist

The following checklist is a high-level overview of the steps to implement ChangeMan ZMF. Some of the items have been covered in more detail earlier in this chapter. Since every site is different, and every implementation needs to be tailored for your specific needs, this checklist is only a suggestion of the steps you may wish to take.

Most implementations are done one application at a time. The first application may be a real application in your shop, or a test application set up to become familiar with ChangeMan ZMF.

  1. Form an Implementation Team. This team usually consists of security personnel, application leads, application programmers, systems programmers, operations analysts, managers, et cetera. These are the people that can make and carry out the decisions necessary to implement ChangeMan ZMF.

  2. Form an Application Test Team. This team should consist of someone who could perform program tests where required and someone that is extremely familiar with your existing change control process and/or compile and link edit procedures. Additionally, someone that is familiar with ISPF skeletons would be a large plus but this process could be learned if required. Your security administrator must be on alert as changes are needed periodically during the initial phases of implementation.

  3. Conduct an implementation planning session with appropriate staff to determine how ChangeMan ZMF will help control the current environment and what the flow of the entire process should be.

  4. Identify ALL libraries that will be managed by ChangeMan ZMF for the application.

  5. Locate ALL compile/link edit procedures that will be required for integration into ChangeMan ZMF for the application. If current procedures are in skeleton format, all skeletons must be expanded and all symbolic variables must be resolved. This means that you have to review all the options for the compile/link edit procedures.

  6. Identify ALL language types that will be required for integration into ChangeMan ZMF for the application (for instance, ASM, COBOL, Db2, CICS). If multiple versions of a language are required, that must also be noted. Each of these languages must have compile/link edit procedures that have been identified above.

  7. Ensure the installation security package has been altered properly as outlined in the security portion of the ChangeMan ZMF documentation. This must include the set up of required ChangeMan ZMF entity names, association of the appropriate userids to those entity names, and set up of the proper dataset access rules for the ID associated with the subsystem.

  8. Have two TSO IDs available for use in ChangeMan ZMF.

    • The first ID must have the following privileges:

      • All five ChangeMan ZMF entity privileges

      • External authority for update of custom skeleton library

    • The second ID is a standard TSO ID with no additional authority to ChangeMan ZMF. This ID only has access to a specific application, and it must not have any administrative capabilities. It is used for testing/debugging the system. Remember to grant this ID access to data sets and batch jobs as outlined earlier in this chapter.

  9. The subsystem should be brought up, security resource rules established and set up for a test application, and the global and application administrative parameters should be defined with permissive rules. These initial administrative decisions may be made more restrictive later as you become more familiar with the product. Finish setting up the test application by defining libraries, languages, procedures, et cetera. (These processes are detailed in Setting Up Global Administration Setting Up Application Administration.)

  10. If you are using the Db2 Option, the installation procedures for Db2 should be followed, ensuring that the ID associated with the subsystem has SYSADM OR BIND/ ADD authority for all Db2 programs. For more information on the Db2 option see the ChangeMan ZMF Db2 Option Getting Started Guide.

  11. Identify all ChangeMan ZMF exits that will assist in the enforcement of shop standards for customization, if required. (See the ChangeMan ZMF Customization Guide.)

  12. Have test programs for each of the above language types so that the STAGE process may be completely tested. The resultant size (length) of the linked component is a good indicator of the ChangeMan ZMF process producing an equivalent load component to the one currently in production. In other words, the load components should be the same size if the skeletons invoked the same compile/link edit procedures. Running a parallel test of those components is a final test.

When the above tasks have been completed, you are ready to move through a phased implementation of ChangeMan ZMF. Many of the above tasks must be performed for each new application that is moved under ChangeMan ZMF control, for example, identifying the libraries necessary. Other tasks, such as setting up the subsystem security rules, are one time only items and do not need to be performed again.