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!).
And by combining this reduction of that aging parm with the creation of a ChangeMan ZMF archive subsystem (creation and maintenance of such archive system is supported by AbitMORE SCM Reporting also) those 4.500 packages would still be available for online queries and/or reporting (which IT auditors like a lot ...).
Report ID:
PKGS2AGE
Report 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).
