Skip to Content

[1.2-Westmalle]

Printer-friendly version

ChangeMan ZMF Application Administration - Getting started

This is an in-depth introduction to ChangeMan ZMF's application administration functions, which is also the foundation (and pre-req) for ChangeMan ZMF's global administration training classes.

READ MORE
Z-Course
Topics: 
  • Configuring a ChangeMan ZMF Application:
    • The ChangeMan ZMF Lifecycle (application parms).
    • The ChangeMan ZMF Library Structure:
      • Library types and baseline libraries.
      • Local and/or remote promotion or production sites.
      • Promotion and/or production libraries.
    • The ChangeMan ZMF Security Architecture.
      • Package approvals configuration.
      • Promotion authorizations configuration.
    • The ChangeMan ZMF Programming Languages and Compile Procedures.
    • Configuring logical DB2 subsystems.
  • Navigating the various ISPF panels in ChangeMan ZMF related to application administration.
Audience: 
  • ChangeMan ZMF Administrators involved in the customization, installation, configuration or optimization of ChangeMan ZMF.
  • ChangeMan ZMF Helpdesk operators assuming they are authorized / responsible also for performing application administration also.
  • Release managers who want to learn about how ChangeMan ZMF can help them implementing (and enforcing) their release management procedures.
  • IT Auditors who want to increase their understanding of ChangeMan ZMF's functions and processes.
  • Users such as Operations control, project leaders, development managers, .... interested in learning more about ChangeMan ZMF and its key concepts.
Duration (hours): 
8.00

ChangeMan ZMF Global Administration - Getting started

This is an in-depth introduction to ChangeMan ZMF's global administration functions.

Z-Course
Topics: 
  • Configuring ChangeMan ZMF subsystems:
    • The ChangeMan ZMF Lifecycle (global parms).
    • The ChangeMan ZMF Library Structure:
      • Library types.
      • Local and/or remote promotion or production sites.
    • The ChangeMan ZMF Security Architecture.
      • Global and application administration authorizations configuration.
      • Revert, backout and monitor authorizations configuration
    • The ChangeMan ZMF Programming Languages and Compile Procedures.
    • Configuring DB2 subsystems.
  • Navigating the various ISPF panels in ChangeMan ZMF related to global administration.
Audience: 
Duration (hours): 
8.00

Enable user defined edit macros in CMN/ZMF

Document what it takes to enable your own set of edit macros to be invoked when using edit in staging, together with some typical use-cases for it (i.e. to launch non-standard ISPF editor session, also called exotic editors).

READ MORE

Outdated LTPs, DSNs, entities, ... in appl admin

ChangeMan ZMF 's application administration facilities are yet another amazing, extremely powerful feature. It's flexibility is one of those things what makes it so much fun for a ChangeMan ZMF admin to be working in the ChangeMan ZMF sphere. You can add library types as much as you want, and extremely fast. Same for designing and implementing a library structure (DSNs related to promotion, baselines and production). Or connecting various ChangeMan ZMF functions (like approve, promote, etc) to selected entities in your security system. Etc, Etc. You can even automate many of those things with the XML services available in ChangeMan ZMF.

READ MORE

Missing package activity dates (invalid restarts)

Package activity dates are dates that are stored in ChangeMan ZMF's meta data (CMNPMAST), and which relate to events such as:

  • When did this package enter the status FRZ, DIS, INS, BAS, etc.
  • When did some target production site confirm that the package was distributed to that site, or installed in that site.

READ MORE

Outdated user options (or invalid user option values)

User options is one of those great ChangeMan ZMF features (in the product since the beginning), which typically allows any ChangeMan ZMF administrators to fine-tune any staging procedure (which is like a checkin of a source component that needs to be compiled by ChangeMan ZMF also). The actual procedures to compiling components (or variations of compilations) is typically something that differs from any ChangeMan ZMF customer to any other ChangeMan ZMF customers (everybody has their own unique needs and requirements).

READ MORE

Speed up package aging via a CMN/ZMF archive subsystem

The package aging parm is a number of days (set in global admin) that a package should be in BAS status (installed in production) before the meta data of that package (VSAM records stored in CMNPMAST) are allowed to be removed during ChangeMan ZMF housekeeping. The higher this number of days, the more people like IT auditors will like it (they are often the ones who are asking for such high number of days). While many countries have laws that force such data to be kept for (e.g.) 7 years, or even more ...

READ MORE

Missing, empty or forgotten staging libraries

Staging libraries are the data sets related to a change package in which ChangeMan ZMF stores its changed components. Together with the meta data of the package and the components in it (both stored in ChangeMan ZMF control files like CMNPMAST), they actually constitute the change package. And the ChangeMan ZMF started task (server running on the mainframe) will take care of managing all such staging libraries: they get created (by ChangeMan ZMF) whenever they are needed, and they get removed during housekeeping, after the package became INS/BAS.

Here are some issues about these staging libraries:

READ MORE

Empty packages

A change package is assumed to contain changed components and/or scratch requests (in 2 decades we have not ever found 1 ChangeMan ZMF customer that's using the rename function, so let's skip that one). Fine, but where do those empty (= no components + no scratch requests) packages come from?

READ MORE

Limbo packages with install date passed

Anybody knows this issue, which is about all non-BAS packages that have a planned installed date that's somewhere in the past. It's entered on the last panel to create a package, or updated via the U7 panel.

READ MORE
Syndicate content