<CMN/ZMF Application Administration>

Mass update sequence numbers of like CPY library types

Summary: Create a basket of all like CPY library types (or a subset of them) for all application IDs (or a subset of them). Then use ASC's basket processing to assign a sequence number to each of the selected library types (in A.A.2). Read more »

Find the XML service to update the appl in use flag

Summary: How to search (or find) the XML service that is available for updating the "application in use" indicator. Read more »

Generate REXX with an XML to update the appl in use flag

Summary: Develop a REXX procedure using appropriate XML service(s) for updating the "application in use" indicator (e.g. in a batch job during ChangeMan ZMF housekeeping). Read more »

Basket processing applied to ASR report PCORPHN

Summary: Create a basket of orphan component promotion history records (using ASR's built-in report PCORPHN). Then use ASC's basket processing to remove all these orphan component promotion history entries. Read more »

Basket processing

Using XML services in ChangeMan ZMF (CMN/ZMF) is great. It has allowed many CMN/ZMF users to create all sorts of customizations and applications that interface with CMN/ZMF, all based on the XML services that are delivered with CMN/ZMF.However, many of these CMN/ZMF users also want to automate various tasks that are typically repeated for a “list” of: Read more »

Verify/alloc/delete of BAS- PROM- or PROD DSNs

Summary: Create a set of baskets for a single application (alternative: for all applications). Each basket contains all DSNs defined in application administration as production DSNs, baseline DSNs or promotion DSNs. Read more »

Solution Variables:

Verify/alloc/delete of BAS- PROM- or PROD DSNs - variables

The above screen (via Appl id within Target selection) shows that this solution can be used for just 1 application, or for all (dozens? hundreds?) applications in 1 shot.

Also note that this solution (via Site within Target selection) can be used to process "ALL" sites together, or to process just 1 site (e.g. a new promotion or production target added in various applications) and eventually to be repeated for a 2nd site.

To understand how the output of this solution looks like, and how to further process that output, checkout the various steps in the scenario below.

Recreate xNode DSNs for selected frozen pkgs

Summary: Submit a request to recreate the X-node DSNs for all frozen packages, optionally limited to only those packages that contain components of a specific library type. Read more »

Solution Variables:

Recreate xNode DSNs for selected FRZ pkgs - variables

Syndicate