|CMN/ZMF Performance Tuning|

Printer-friendly version PDF version

Remove dead checkout requests

Summary: Create a basket of dead checkout requests (using ASR's built-in report DEADCKOS). Then use ASC's basket processing to delete all such components from their packages.

Scenario: 

Step 01: Create a basket with all dead checkout requests (using DEADCKOS)
Remove dead checkout requests - output (XML basket)
Step 02: Launch a basket - Required input tags for CMPONENT/PKG_COMP/DELETE
Launch a basket - Check required input tags for CMPONENT/PKG_COMP/DELETE
Step 03: Launch a basket - Edit the basket header
Launch a basket - Edit the basket header
Step 04: Launch a basket - Filter the basket
Launch a basket - Filter the basket
Step 05: Launch a basket - Select a basket compliant XML
Launch a basket - Select a basket compliant XML
Step 06: Execute the basket - Request tags
Execute the basket - Request tags

Step 07: Execute the basket – Execution options
Execute the basket – Execution options

Subject:
AbM SCM Solutions:
Taxonomy upgrade extras:

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.

Scenario: 

Step 01: Create a basket with orphan component promotion history (using PCORPHN)
Orphan component promotion history - output (XML basket)
Step 02: Launch a basket - Filter the basket
Launch a basket - Filter the basket
Step 03: Launch a basket - Select a basket compliant XML
Launch a basket - Select a basket compliant XML
Step 04: Execute the basket - Request tags
Execute the basket - Request tags

Step 05: Execute the basket – Execution options
Execute the basket – Execution options

Subject:
AbM SCM Solutions:

BAS packages waiting to be aged

Summary: List all BAS packages baselined before a given date.

Here is a real world use case of this report: a customer with about 8.500 change packages and with the package aging parm (in A.A.1) set to 365 days wanted to find out (simulate) what the effect would be of reducing this aging parm to 60 days (only!). The simulation showed that it would allow for aging over 4.500 change packages (that's more then 50 % of the total number of packages!).

Report ID: 
PKGS2AGE
Report Specs: 

Pkgs not aged yet / pkg archive candidates - specs

Report Variables: 

The available report variable #RPTV_TIME_FRAME allows for some interesting report variations:

  • Using a value that matches the package aging parm (defined in A.A.1), it will create a list of all BAS packages that should have been aged already by ChangeMan ZMF housekeeping (but for some reason they were not aged yet).
  • Using a value that is smaller then the package aging parm (defined in A.A.1), it will create a list of all BAS packages that would be aged during the next ChangeMan ZMF housekeeping cycle (so it can be used to simulate the effect of changing value of the package aging parm).
AbM SCM Solutions:

Components deleted from STG without demote

Summary: List all components deleted from staging without a prior demote from one or more promotion levels.

Report ID: 
PCDLNODM
Report Specs: 

Components deleted from staging without demote - specs

Report Variables: 

Components deleted from staging without demote - report variables
Specifying values for report variables can be done using the edit vars feature, for which two options exist:

  • option P will bring up an ISPF pop-up panel (as illustrated above). Using this option, the values entered can be validated using any of the available ISPF panel validation techniques (even ISPF panel exists should that be required), which adds another dimension to the power of report variables.
  • option I will invoke the standard ISPF editor. Checkout orphan component promotion history for an illustration of this option.
Report Output: 

Components deleted from staging without demote - output (XML basket)

AbM SCM Solutions:

Staged components without updates

Summary: List all staged components checked out before, but without any updates as compared to the baseline.

Here is the clue for creating such report (the selection criteria):

Report ID: 
CMPNOCHG
Report Specs: 

Staged component without updates - specs

Report Variables: 

Because of the nature of this report, it doesn't have/require any report variables.

AbM SCM Solutions:

Empty Packages

Summary: List all DEV packages created in the past, without any package components.

Report ID: 
PKGEMPTY
Report Specs: 

Empty packages - specs

Report Variables: 

Because of the nature of this report, it doesn't have/require any report variables.

Report Output: 

Empty packages - output (Chart)

AbM SCM Solutions:

Orphan component promotion history

Summary: List all component promotion history for all DFZ packages, related to an obsoleted promotion level.

Report ID: 
PCORPHN
Report Specs: 

Orphan component promotion history - specs

Report Variables: 

Orphan component promotion history - report variables
Specifying values for report variables can be done using the edit vars feature, for which two options exist:

  • option P will bring up an ISPF pop-up panel. Checkout components deleted from STG without demote for an illustration of this option.
  • option I will invoke the standard ISPF editor (as illustrated above). Using this option, the specification of values can be done using any REXX compliant assign statement, which adds another dimension to the power of report variables.
Report Output: 

Orphan component promotion history - output (XML basket)

AbM SCM Solutions:

All stage requests not moving anymore

Summary: List all staged components in all non-BAS packages, that were last changed long time ago.

Report ID: 
DEADSTGS
Report Specs: 

All stage requests that don’t move anymore - specs

Report Variables: 

All stage requests that don’t move anymore - report variables
The available report variable #RPTV_TIME_FRAME allows for specifying the desired cut-off date.

Report Output: 

All stage requests that don’t move anymore - output (XML basket)

AbM SCM Solutions:

All checkout requests not moving anymore

Summary: List all components in CHECKOUT status, checked out before a given date.

A typical reason for creating such report (and recreating it periodically) is to actually delete such components from staging, as illustrated in remove dead checkout requests. Here are some reasons for doing so:

Report ID: 
DEADCKOS
Report Specs: 

All checkout requests that don’t move anymore - specs

Report Variables: 

All checkout requests that don’t move anymore - report variables
The available report variable #RPTV_TIME_FRAME allows for specifying the desired cut-off date.

Report Output: 

All checkout requests that don’t move anymore - output (XML basket)

AbM SCM Solutions:

Non-BAS pkgs not moving anymore

Summary: List all non-BAS packages without any recent package status changes.

Report ID: 
DEADPKGS
Report Specs: 

All non-BAS pkgs that don't move anymore - specs

Report Variables: 

All non-BAS pkgs that don't move anymore - report variables
The available report variable #RPTV_TIME_FRAME allows for specifying the desired cut-off date.

Report Output: 

All non-BAS pkgs that don't move anymore - output (XML basket)

AbM SCM Solutions:

Pages

Subscribe to |CMN/ZMF Performance Tuning|