|Built-in Solutions|

Printer-friendly version PDF version

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.

The set of baskets created are:

Solution ID: 
ASCZ0202
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.

Scenario: 

Step 01: List the baskets created by ASCZ0202

Verify/alloc/delete of BAS- PROM- or PROD DSNs - List the baskets created by ASCZ0202

Step 02: View the baskets content (1/2)

Verify/alloc/delete of BAS- PROM- or PROD DSNs - View the baskets content (1/2)
This is a perfect illustration of how "real" baskets look like (= CSV-kind of files).

The various data included in each record, is what gets created by using a Process option (within Execution options) with value 1 (Allocate), because all these data are required as input tags for the XML service to actually allocate these DSNs (shown in step 04 below).

By using value 1 (Info) or 3 (Delete), each record will only contain the mvslib value, because only a DSN is required as input tag for the XML service to either report about the DSN info (with data similar to ISPF option 3.2) or to actually delete these DSNs.

Step 02: View the baskets content (2/2)

Verify/alloc/delete of BAS- PROM- or PROD DSNs - View the baskets content (1/2)

Step 03: Launch the baskets

Verify/alloc/delete of BAS- PROM- or PROD DSNs - Launch the baskets

Step 04: Select XML

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

Above is an illustration of how ASC helps an XML newbee to take advantage of the extreme power of XML services. I.e. ASC "guides" you to picking (= finding !) the appropriate XML service (in this case DSS/SERVICE/ALLOCATE), and gives you all sorts of extra XML execution features (step 05, part 2/2 below) to get the job done.

Step 05: Execute XML (1/2)

Verify/alloc/delete of BAS- PROM- or PROD DSNs -  Execute XML (1/2)

Step 05: Execute XML (2/2)

Verify/alloc/delete of BAS- PROM- or PROD DSNs -  Execute XML (2/2)
So in this specific scenario the basket processing will trigger about 100 to 200 XML requests for each application, 1 for each record in each of the 3 basket DSNs in this scenario. Do the math if you'd have hundreds of applications (and then think of how long it would take to achieve the same result if you have to do this without using XML services ... hours, days or weeks?).

What is even (Abit)MORE: executing all these XML services can be done without "disturbing" the CMN/ZMF STC too much. This because of the input basket options shown above: turning on the options Split in units, Nr req/unit and Next unit after will facilitate a kind of work load balancing to actually execute all those services. That will avoid that regular ZMF users would experience bad response times from the CMN/ZMF started task while all those XML services are being processed (like compile jobs or promotion jobs that would take extremely long ...). Because of this, the scenario above can be executed also during CMN/ZMF primetime hours (instead of during none business hours at night or during weekends).

AbM SCM Solutions:

Synchronize DEV staging library list with catalog

Summary: Verify and correct discrepancies between the zOS catalog and the staging DSNs registered in CMNPMAST as allocated.

To better illustrate this discrepancy, consider this example: using CMN/ZMF’s function “query package”, and then asking for “development staging libraries”, you get a list with, say, 14 entries of staging DSNs that, according to CMN/ZMF, have been allocated already (defer = N).

Solution ID: 
ASCZ0103
Solution Variables: 

Synchronize development staging library list with the catalog - variables

Scenario: 

 

AbM SCM Solutions:
ASC Category:

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.

Limiting the scope of all package to be processed by library type is possible for library types displayed within the package content (S2) or displayed via a source-to-load relationship.

Solution ID: 
ASCZ0051
Solution Variables: 

Recreate xNode DSNs for selected FRZ pkgs - variables

Scenario: 

 

AbM SCM Solutions:

Change the creator Id of a package

Summary: Change the creator ID of a change package to another userid, something that is typically done for none-BAS packages created by somebody who left the company.

Solution ID: 
ASCZ0011
Solution Variables: 

Change the creator Id of a package - variables

AbM SCM Solutions:
ASC Category:

Update install date for all expired packages (limbo)

Summary: Mass update the planned install date of all change package with “install date passed” to the new (future) install date.

Solution ID: 
ASCZ0301
Solution Variables: 

Update install date for all expired packages (limbo) - variables

Scenario: 

 

AbM SCM Solutions:

AbitMORE SCM Commander - Solutions

AbitMORE SCM Commander’s solution center is a set of ISPF dialogs (ASC solutions) to perform various CMN/ZMF tasks, and this via all sorts of XML services that are executed from within those dialogs. These XML services are hidden within the ASC solutions (and/or the batchjob that may get submitted to complete a request), so that the users of these solutions do not have to know anything about using XML services.

AbM SCM Solutions:
Subscribe to |Built-in Solutions|