Optimize ChangeMan ZMF with regular weeding

Keeping ChangeMan ZMF environments
in perfect shape
www: http://www.abitmore-scm.com/
twitter: @AbitMORE_SCM
speaker: Pierre.Vriens @ abitmore-scm.com

Copyright © 2012 AbitMORE ® 2 Keeping ChangeMan ZMF environments in perfect shape
Abstract
From the perspective of a Serena partner,
you will hear about the typical issues
showing up in mostly any ChangeMan ZMF environment
after it has been operational for a number of years.
At the end of the session, it should be clear that
ChangeMan ZMF is like a garden,
you need to weed it occasionally (ideally even daily) …
using the correct tools & customizations to do so.

Agenda
1. About AbitMORE SCM
2. A tour in the ZMF garden
3. Weeding the ZMF garden
4. Keeping the ZMF garden healthy
5. The fruit of your labor
6. Where to go from here
7. Questions?

About AbitMORE SCM
Company profile
 Founded in 2000, based in Belgium
 CMN/ZMF experience:
 First CMN/ZMF exposure in 1989 (teacher: John Allen; SERENA=+/- 10 people)
 Over 150 man-years, in 3 continents
 SERENA XML certified since 2004 (prereq for YELLOW srvcs)
 Customers such as (incomplete list …)
 Europe : KBC, Dexia, Euroclear, Credit Suisse, …
 USA : Prudential , Conway CNF, …
 …
 Participations in CMN/ZMF events
 Attendee of all SERENA global conferences (since 1991)
 Legacy sponsor of SERENA global conferences since 2005
 Legacy co-organizer of the CMN/ZMF Benelux user groups
 Regional CMN/ZMF user groups
 Regional CMN/ZMF XML workshops
 Contact info
 Corporate website: http://www.abitmore.eu
 SCM specific: http://www.abitmore-scm.com (web) @AbitMORE_SCM (twitter)
 CMN/ZMF specific: http://dr.chgman.com (web) @Dr_Chgman (twitter)
 eMail: info@abitmore-scm.com

About AbitMORE SCM
Products and services
 Provider of onsite CMN/ZMF services
 CMN/ZMF implementation and upgrade services (consulting)
 CMN/ZMF training services
 CMN/ZMF helpdesk outsourcing services (ITIL based)
 Provider of CMN/ZMF product options
 AbitMORE SCM Reporting - On demand CMN/ZMF reporting
 AbitMORE SCM Commander - XML based workbench for CMN/ZMF
 AbitMORE SCM For IDMS/ADSO - Manage ADSO with CMN/ZMF
 Provider of CMN/ZMF expertise in the cloud, via http://Dr.Chgman.com
 Z-Factory - Z-Issues, Z-Clues, Z-Files
 Z-Wiki - Z-Recipes, Z-Deficiencies, Z-Redbook, Z-Practices
 Z-Consults - Z-Support, Z-Audit, Z-Tuning, Z-Assist, Z-Coach, Z-Act
 Z-University - User training, admin training, XML training

About AbitMORE SCM
Timeline for ZMF (1/2)
 1990: Get started with Change Man 3.2.1b as SERENA’s BeNeLux rep
 1991: Support for dynamically called routines in ZMF
 1992: ChangeMan ESF option (= beat DDT’s “can’t do it”)
 1993: Support for Adabas / Natural in CMN/ZMF
 1994: CMNEX* exits for ZMF’s audit (= audit-à-la-carte by Mr. Audit)
 1995: AbitMORE SCM for IDMS/ADSO (= ZMF’s alternative to NDVR/DB)
 1996: CMN/ZMF’s technical support challenger (it has to perfect)
 1997: Implement ChangeMan ESF option around the world (+ 10 sites)
 1998: AbitMORE SCM goes private (= Senior SERENA consultant for ZMF)
 1999: Launch/sponsoring of CMN/ZMF BeNeLux user group (2nd Wed Dec)
 2000: Manage DB2 table data contents with CMN/ZMF
 2001: Support for Cool:Gen in CMN/ZMF
 2002: APS interface replacing SER’s APS option

About AbitMORE SCM
Timeline for ZMF (2/2)
 2003: ERO-lite (= ERO alternative to INS 150,000 cmps in < 2 h window)
 2004: AbitMORE SCM Reporting (= reports & charts for ChangeMan ZMF)
 2005: AbitMORE SCM Helpdesk for CMN/ZMF (= calls -70% in 6 months)
 2006: AbitMORE SCM Commander (= push ChangeMan ZMF’s XML limits)
 2007: Exclusive platinum sponsor SERENA’s global conference (Chicago)
 2008: Manage DDLs via integration with prods from BMC, IBM etc
 2009: XML boot camp for CMN/ZMF - 2 to 5 days intensive XML training
 2010: Dr.Chgman.com (Z-Factory, Z-Wiki, Z-Consults, …)
 2011: RED xml srvcs in AbitMORE SCM Commander, approved by SERENA
 2012: XML Support in AbitMORE SCM Reporting, incl. CMN/ZMF 7.1.x
 …
 Coming up next: complement the SERENA Dashboard for CMN/ZMF

A tour in the ZMF garden:
Back to ZMF basics (since at least 3.2.1b)
 About a change package:
1. Has a planned install date that should be in the future
2. Contains package components and/or scratch reqs or renames
3. Use checkout to start a new version of a component
4. Package status goes from DEV, to FRZ, … to BAS …
5. In case of failed INS jobs: just restart from the failed jobstep
6. Use BAK to recover from production failures (due to poor testing)
7. Housekeeping removes BAS pkgs (pkg aging, e.g. 500 days)
8. Change packages contain historical info (IT auditor reports)
 About CMN/ZMF managed libraries:
1. STG libs are allocated by CMN/ZMF whenever they are (first) needed
2. Housekeeping removes all STG libs (e.g. 7 days after BAS)
3. Baseline 0 is a copy of production libs
4. Promotion libraries are cleaned up at BAS-time
 About customization facilities:
1. User options for like SRCs (to Keep-It-Super-Simple you only need 20 bytes …)
2. Appl admin flexibility (LTPs, DSNs, entities, etc)
 So far some commonly known theory (= CMN/ZMF 101) …

Issues in nearly any CMN/ZMF environment
 Many CMN/ZMF customer have > 90% of these issues:
1. Limbo packages with install date passed
2. Some packages remain in DEV for year (or forever …)
3. Non-BAS packages hanging around (from people who quit)
4. Empty packages
5. Dead checkouts and dead stage requests (= performed long time ago)
6. Missing stg libs (defer bit), empty stg libs or forgotten (housekeeping) stg libs
7. Small package aging parms conflicts with reporting needs
8. Outdated user options (or invalid user option values)
9. BAS pkgs with missing pkg activity dates (invalid restarts)
10. Outdated appl admin entries (LTPs, DSNs, entities, etc)
… (this list is not just incomplete, but far from complete!)
 Who ‘thinks to have’ less then 100% of these issues? … 90%? 80%? …
 The longer you use CMN/ZMF, the more these issues grow …
 … Unless you treat CMN/ZMF like your garden, i.e.: you weed it
occasionally … ideally even daily …

CMN/ZMF health indicators (1/2)
1. Nr of pkgs (=size of package master, e.g. 50,000+ pkgs)
2. Nr of cmps (=size of component master, eg: 1.3M entries)
3. Nr of staging libraries (empty, obsolete or disappeared)
4. Nr of pkgs in status NE DEV, FRZ, BAS
5. Response times for Q.P of all pkgs (like 30 mins)
6. Promotes / installs fail due to x37 abends or missing DSNs
7. Package aging parms (60 days is enough … trust us!)
8. Resources consumption (MIPs) to create xNode DSNs
9. Nr + complexity of custom skls, pnls, rexx, rpts, …
10. Time it takes to upgrade to a (major) CMN/ZMF release
11. …

CMN/ZMF health indicators (2/2)
11. Amount of CMN/ZMF helpdesk calls
12. Nr of A.A. errors (A.A.2 vs A.A.B, outdated adm parms, …)
13. BAS/PROM/PROD DSNs that are obsolete or not allocated
14. Amount of empty baselines (= ‘model appl’ overkill)
15. Nr of orphan comps in prom libs
16. SEQ nr of highest pkg (e.g. 46,000)
17. Availability and status of experimental CMN/ZMF envir(s)
18. CMN/ZMF customizations are all managed by CMN-on-CMN
19. Security setup (resource classes, submit with STC auth, …)
20. Partial XML setup (XMLSPACE, MAPDATA, SERPARMS, …)
… (this list is not just incomplete, but far from complete!)

Weeding the ZMF garden:
Measuring the size of a CMN/ZMF instance
Notes:
1. Age = Nr of years CMN/ZMF is in use (operational mode)
2. Primary pkgs = Pkgs in operational CMN/ZMF’s DP-site (not yet aged pkgs)
3. Archived pkgs = Pkgs aged in the primary CMN/ZMF + restored in an additional
CMN/ZMF STC for reporting / query purposes only
Description Notes Cust 01
(Small)
Cust 16
(Medium)
Cust 04
(Large)
Cust 03
(Huge)
Customer age (1) 10 10 14 12
Nr of all primary pkgs (2) 244 8,433 596 4,219
Nr of all archived pkgs (3) 1,578 0 18,223 70,976
Nr of pkg aging days 60 365 60 60
Nr of appls 110 5 77 807
Nr of DFZ pkgs 231 1,477 544 3,518
All comps in all DFZ pkgs - 11,976 40,027 298,925

Find obsolete DFZ data and obsolete promo history
(Medium)
Cust 04
(Large)
Cust 03
(Huge)
Expired INS dates Plnd INS date < &today 816 952 495
Dead packages > 1 year ago 603 448 1,368
Dead checkouts > 6 months ago 32 23 2,698
Dead stage requests > 1 year ago 3,006 29,634 101,150
Orphan CMP promo hist Promo nickname=VM* 1 2,235 -
Empty packages No cmps + no scratches 260 71 345

Get your DEV users on track again
Description Notes/remarks Cust 16
(Medium)
Cust 04
(Large)
Cust 03
(Huge)
CMPs no CKO from BAS Hash at CKO = 00…00 8,007 6,797 12,801
Pkg CMPs without updates Hash(stg) = hash(bas0) 590 8,218 13,907
Del from STG + no DMT 1 2,218 -
Never promoted FRZ pkgs Tested? 10 5 75
Pln pkgs CRE+BAS same day Unplanned ??? 765 5 57

Get your INS-ed packages on track again
(Medium)
Cust 04
(Large)
Cust 03
(Huge)
No DIS/INS/BAS Ack Ack date missing 0/1/0 1/1/1 0/0/0
BAK pkgs waiting REV Pkgs with BAK date 21 0 0
Audit PRD reverts 25 0 0
Pkgs archive candidates BAS date < today – 60 d 4,714 1 2

Report on what’s happening in your ChangeMan ZMF environments
Use AbitMORE SCM Reporting (ASR) to:
1. Create and maintain an online archive
subsystem - for ChangeMan ZMF reporting
and/or online ChangeMan ZMF queries.
2. Create and maintain a ChangeMan ZMF history
environment - for ZMF reporting only, no
online ChangeMan ZMF queries.
3. Create and maintain a ChangeMan ZMF
warehouse - daily cache of your primary
ChangeMan ZMF environments.
4. Produce consolidated ChangeMan ZMF reports
- from multiple ChangeMan ZMF environments
such as a primary ChangeMan ZMF subsys
combined with a ChangeMan ZMF archive
and/or ChangeMan ZMF history environment.
5. Remove all sorts of obsolete ChangeMan ZMF
customizations (e.g. during ZMF upgrades …).
Use ASR if you don’t know XML,
or you don’t like XML, or XML
can’t do the job, or XML is too
slow or too resource consuming.

Keeping the ZMF garden healthy:
Package maintenance
 Proactive (= prevent issues):
 Prevent expired packages showing up in limbo:
• via daily nagging eMails (= quick-win).
• update INS date during housekeeping.
 Delete empty packages that are not created today.
 Hunt for dead packages.
 Remove orphan package data.
 Preload recently “used” comps during housekeeping (CMN 7.1.x only).
 Audit / (batch) freeze validations, e.g.: creation date <= today-1 year.
 Maintain a CMN/ZMF archive subsystem (+ pkg aging parm = 60 d).
 …
 Reactive (= resolve issues):
 Update package creator IDs for disappeared creators.
 Complete missing package activity dates for DIS, INS, BAS.
 Monitor the BAK packages to be reverted.
 Maintain a watch list of packages with a BAS date + not in status BAS.
 …

Component maintenance
 Remove dead checkout requests.
 Hunt for components staged long time ago.
 Disallow empty DBRMs (during stage).
 Complete like-SRC scratch requests with ILODs in D/A packages
(during batch freeze).
 Check component names during stage from DEVLIBs (S1).
 Implement component ownership:
• Create an initial component history record for all comps (not only like SRC).
• Move components between CMN/ZMF applications (in any CMN/ZMF lib).
• Enforce component ownership (= allow CKO or STG only to pkgs of the SAME
applid, unless some security entity check is OK).
 …
 Reduce the amount of component history entries with up to 50 % by
removing obsolete component history.
 During CMN 7.1 upgrade: recreate component history entries in CMN
7.1.x for components with more then 24 entries in pre CMN 7.1.x.
 …

Libraries maintenance
 Remove empty staging libraries + synchronize the defer bit again.
 Recreate xNode DSNs (F5) after A.A.P updates for selected LTPs, but
only for pkgs that contain the updated LTP.
 Automatic verify / allocate / delete of BAS/PROM/PROD DSNs.
 Force CMN/ZMF usage to mass update comps in DFZ pkgs, baselines
and prodlibs (= disallow mass conversions without using CMN/ZMF).
 …
 Synchronize the defer bit of STGLIBs that disappeared.
 Remove orphan stglib components (Synch12)
 Hunt for obsolete staging libraries, such as:
• Staging libraries forgotten by standard housekeeping (e.g. an xNode DSN for
a site removed from the U7 panel after BAK).
• Add ‘STGLIB aging’-variations (shadow stglibs, work DSNs, )….
• Real world case:
 Q: Which of these 16,000 STGLIBs that are all MIGRATED are still needed?
 A: 8,000 of them can be safely deleted (the corresponding pkg no longer exists) …
and here are another 12,000 stglibs (not migrated) that can be safely delete also …
 …

Appl admin maintenance
 Quick-win: Create/update CMN100 rpts during housekeeping (for all
appls), store SYSTSPRT (= rpt) in a shared DSN (mbrname = appl ID)
and run SUPERC to search for shared DSN (to safely delete any BASx,
SHAD, PROM, PROD, TEMP, BKUP libs).
 Get ready for agile CMN/ZMF administration (performing all sorts of
(mass) admin updates): use basket processing features.
 Maintain an experimental CMN/ZMF subsys: export A.A entries from
operational CMN/ZMF subsys + import them in experimental subsys.
 …
 Reset the “appl in use” indicator during housekeeping: use XML search
facilities (to find the XML that can do this) and use code generation
features (to generate the REXX to run the XML).
 Hunt for empty baseline libraries and remove what is appropriate from
appl admin (= stop defining model applications to “copy forward”).
 …

Use XML to automate ChangeMan ZMF maintenance
Use AbitMORE SCM Commander
(ASC) to:
1. mass update outdated package data.
2. remove orphan/obsolete data (pkg,
cmp, admin) using basket processing.
3. create an in-depth audit trail of all
updates performed via XML … and
optionally perform a rollback of them!
4. research available XML services
(=explore the XML universe).
5. facilitate upgrading XML based
customizations to new ZMF releases.
6. automatically generate REXX code for
any XML service (e.g. rewrite ZMF’s
ISPF client in (only) 10 workdays).
7. enable export / import of A.A. data
between 2 appls, ZMF systems (e.g.
enable CMN-on-CMN for ChangeMan
ZMF admin updates).
8. manage all BAS/PROM/PROD DSNs.
9. add 0.5 to 1.0 FTE to a ZMF team.
10.perform agile ChangeMan ZMF
administration and customization.
Use ASC if you’re not an
XML expert (yet), or want
to automate all sorts of
CMN/ZMF tasks or want to
push the XML limits

The fruits of your labor
 Amazing ChangeMan ZMF response times.
 Less obsolete / orphan ChangeMan ZMF data.
 Release management that flies.
 Happy IT auditors.
 Reduced backup time.
 Reduced IT resources (DASD, MIPs, ...).
 CMNPMAST that fits on a single volume (easily).
 Reduced number of ChangeMan ZMF helpdesk requests.
 Simplified ChangeMan ZMF release upgrades.
 ... Lean ZMF!

Where to go from here
 Option 1: Re-invent the wheel by:
 Learning / using SERXMLxC (x=B,R,C,A)
 Developing solutions / customizations yourself, or
 Hiring a CMN/ZMF consultant (from AbitMORE, from SERENA, from …)
 And … keep upgrading everything with any new ZMF release
 Option 2: Be patient (=wait for a future CMN/ZMF release), like:
 Last ‘action’ (instead of last ‘change’) on various ISPF panels (+/-1992)
 Skeleton CMN$$PRM redesign (+/-1994)
 Pgm=CMNAUDRC, Audit-à-la-carte aka CMNEX02* (+/- 1996)
 XML service PACKAGE AUDIT - since 5.5, not yet in 5.3 (+/- 2004)
 Scheduled promote (+/- 2008)
 Option 3: AbitMORE SCM solutions for CMN/ZMF (= ASR or ASC)
 Option 4: Get solutions and/or services from Dr.Chgman.com:
 Sign up at dr.chgman.com for:
• a (free of charge) membership (optionally combined with a support subscription) or
• a monthly, quarterly or yearly (subscription fee based) subscription (includes support)
 Available licenses (varies by solution):
• Freeware/shareware software license
• Professional software license (includes traditional M&E and support)
• Creative Commons license

 Website: http://www. abitmore-scm.com/
 eMail: info@abitmore-scm.com
Questions?
So you want a custom
report or chart about your
CMN/ZMF data?
… We can help you do that!
So you want to learn
about CMN/ZMF? …
Let us teach you!
XML in CMN/ZMF is great, but hard
to get started! … Let us help you,
and add a lot of extra features to it!
Have an issue using CMN/ZMF?
… How can we help you?
So you’re stuck or missing
something in CMN/ZMF? …
Pretty sure we have the
solution for you!

Bottom line
The key to our success ...
is our speed and flexibility ...
with which we can deliver quality and know-how ...

Fine print
 Copyrights
 Copyright, (c) 2012 by AbitMORE ® bvba . All rights reserved.
 No part of this presentation may be reproduced, stored in a retrieval system, or
transmitted in any form or by any means - electronic, mechanical, photocopying,
recording or otherwise - without the written permission of AbitMORE ® bvba
 Trademarks
 AbitMORE ® is a registered trademark of AbitMORE ® bvba
 All other products and company names are used for identification purpose only,
and may be trademarks of their respective owners.
 Disclaimers
 AbitMORE ® bvba makes no representations or warranties with respect to the
material in this document, and no express or implied warranties for product use
are included by use of it.
 Material herein is intended as reference matter only. AbitMORE ® bvba reserves
the right to amend and revise it at its discretion.

Please Evaluate This Session
1. Scan or go to surveymonkey.com/s/x12
2. Select session:
[6 – 4] Keeping ChangeMan ZMF Environments in Tip
Top Shape
3. Complete the survey
27
Every survey is an entry in
our Google Nexus 7 giveaway

Optimize ChangeMan ZMF with regular weeding

Recommandé

Recommandé

Contenu connexe

Tendances

Tendances (12)

Similaire à Optimize ChangeMan ZMF with regular weeding

Similaire à Optimize ChangeMan ZMF with regular weeding (20)

Dernier

Dernier (20)

Optimize ChangeMan ZMF with regular weeding