Skip to Content


Printer-friendly version

Mass recall migrated data sets

Sometimes you need to recall a (huge number of) libraries, which fit a certain DSN pattern.

You're lucky if these DSNs (by accident) are just any of these:


Show user options and V0x-variables in CMN/ZMF jobs

Failures in user initiated jobs (like checkout, stage, audit, promote, ...) may be caused by special (or missing) values for so called &V0x variables and/or user options. Typical failures are:

  • invalid (or simply missing) values for DSN=... in a staging job.
  • entire jobsteps that are missing (because of some skeleton variable that has an unexpected value, or just no value at all).


Check availability of all CMN/ZMF started tasks

Periodically, typically at the beginning of business hours, you should do an (automatic) verification that all your started tasks are "up", and this across all Z/OS images where at least 1 ChangeMan ZMF STC runs.

A variation of this is verifying that each of these STCs have been started with the correct options (to avoid other problems such at package installation time), to mention a few:

  • The jobname of the STC.
  • The type of ChangeMan ZMF subsystem (D-, P-, DP- or ALL-site).
  • The name of the (remote) site that the STC corresponds to.
  • ...


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.


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:


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.


Add restart instructions in Xnode jobs

Add restart instructions in Xnode jobs

A possible solution to eliminate these difficulties is to add restart instructions in all appropriate Xnode members, so that these instructions are available in any job listing of any Xnode job that may have to be restarted.


Add restart instructions in Xnode jobs

In case of a failed installation of a change package, the failing job (typically the CMN10, CMN20, CMN21 or CMN30 job) needs to be restarted, after the reason for the failure has been addressed. Such restart typically needs to be initiated by operations control people (and quite a lot during non-business hours). To actually perform such restart, these people often encounter quite some difficulties that need to be addressed somehow:


Verify VSAM datasets as 1st step of STC proc

According to the ChangeMan ZMF manuals you should always shutdown the started task with the modify command to “orderly shutdown”, which then also ensures the correct closing of the VSAM files.

However, there are a few occasions where this simply does not happen, like:

Syndicate content