This presentation includes:
- ZMF 7.1.3 First Impressions
- New, competitive migration utility
- Looking at what’s hot for 7.2
- Share in Boston and xChange in Miami Beach
- Important changes at Serena
2. Four things to take note of
2
First impressions
Migration utility
Looking forward
SHARE and xChange
Dave Jackson
Steve Downes
Al Slovacek
Al Slovacek
Steve Downes
Kevin Parker
4. ChangeMan ZMF 7.1.3
4
Eclipse
Windows 8 support
Large volume (EAV) support
Allow scheduled promotion requests
Improved filtering
ZDDOPTS
Further align with ZDD client
Support for RACF groups
zDD
Windows 8 support
Large Volume (EAV) Support
Simplify Installer
Allow scheduled promotion requests
ZDDOPTS support for RACF groups
7.1.3
Continue defect backlog burndown
Large Volume (EAV) Support
ERO Web Services
DNS name support
Activity Logfile parms
#varlist updates
6. History
• Panvalet and Librarian came into being as the most reliable source
repositories of their time in the 1960s
• Volatility of legacy production code has been a barrier to conversion
off of Pan/Lib
• Yet CA customers continue to pay significant maintenance costs and
derive little or no value (little or no product enhancements, no
currency support, no support for modern workloads, Java, zFS, etc.)
• An actual Librarian message recently seen at a global financial
services client:
6
SUMMARY OF MESSAGES
FINAL INPUT STATEMENT WAS NOT —END. MAKE SURE THAT LAST
PART OF DECK WAS NOT DROPPED.
A —END statement did not follow the data. Make sure that
the control stream is complete.
7. How Serena can help
• PREVIOUSLY
• Conversion off of Pan/Lib involved extraction to PDS/PDSEs then manual
migration into ZMF
• NEW
• Serena Professional Services armed with a new utility to execute
rapid, accurate and complete conversions from Panvalet or Librarian to
ChangeMan ZMF
• Complete conversion of Pan/Lib components including:
• Versioning
• Component History
• Baselines (including full generations, or stacked reverse delta)
• Selective conversion, filtering, XML generation
• Support for multiple input sources
• Intelligent language determination
• Orphan, duplicate, missing component, junk determination
7
8. Migration Approach – CMNPNLBC
(Phase 1)
• Pass 1 – for discovery
• Read only
• Detection
• Duplicates,
• Missing,
• Orphans
• Language identification
• Source, Copy detection
• Comprehensive Filtering
• Conformance score
• Report post process
• Iterative
8
10. CMNPNLBC
• Pass 1 – post processing
• Read only
• Duplicate elimination
• Orphan elimination
• Find missing components
• Inspect bad conform
scores
• Iterate
• Report edit process
10
11. CMNPNLBC
(Phase 2)
• Copy members to PDS(E)
• Copies the identified
members
• Convert Lib stats to
ISPF stats
• 9 & 10 char names stored
as SRD
• Options:
• Post process report
• Synonym conversion
• Generate versions
• Generate XML
• User customization
11
12. CMNPNLBC
(Phase 3)
• Pass 3 – Ensure nothing is
left behind
• Post operative detection
after
• Full life cycle
• Members secured in
Baseline Libraries
• Component History
captured
• Archive Levels preserved
• Analyzes members in both
systems
• Shows components left behind
• ZMF Packages audited for completeness
• Safeguard against duplication
12
13. Customer Experience
Major Global Financial Organization
• 10 Librarian
• 14 Panvalet
• Utility enhanced for multiple library input
• Cross library duplicate detection
• A previously manually converted application (approximately 400
person-hours)
• Complete lifecycle
• Component History preserved.
• Member statistics carried over.
13
14. Customer Experiences
Education services provider
• Very Fast
• Numeric member names
• Non-national special characters in member names
• Source and Copybooks sometimes in segregated libraries, sometimes
in shared libraries
• Panvalet positions 9-10 not always used
• Librarian Archive levels not used
• Multiple repositories by application release
• Y2K issues with Librarian
14
16. ChangeMan ZMF 7.2 - Themes
Modernization Time-to-Value
Usability and
Standards
High Availability
16
17. Themes
• Time To Value
• Pre/Post Exits
• Exits can be coded in REXX and/or
any LE-supported language
• Centralize customizations for ease
of upgrade
• Expose customizations to Client
Pack
• Application mass
copy/clone/update support
• Clone all application configuration
data to another new/existing app
• Mass update of a single
application parameter across all or
many applications.
• High Availability
• Build on 7.1.3 (support for DNS
over IP address)
• Failover (Automated Restart
Management)
• Modernization
• Expose ERO Web Services
• Extend RD&T support
• Usability and Standards
• Consistency across UI
• JCL standards
• Consistent use of Sort and PF
keys
17
18. ZMF+Release Management Touchpoints
18
System
Test
Acceptance
Test
Mainframe
Unix / Linux
Windows
Pre Prod
ProductionConfigurable steps (environments) toward
production + Process
VaultDelivery
Subversion
Dimensions
ZMF
(as Release Vault)
3rd Party Build & Test Tools
Build & Test Management
Baseline
-N
Checkout
Baseline
Ripple
Baseline
-2
Baseline
-1
Baseline
0
Reverse
Baseline
Ripple
Install
Promotion
Level 10 Promotion
Level 15
Development
Systems
Integration
Promotion
Level 20 Promotion
Level 25
Development
Systems
Integration
Promotion
Level 80
Production
Integration
Promotion
SERENA SOFTWARE INC.18
20. HLLX Overview
Rationale
• Key item requested by customers
• Currently, customers modify ISPF Panels – inaccessible to ClientPack
• Multiple clients (ISPF, Eclipse and ZDD) demand a common method of
invoking business logic
• Remove need for repetitive rework of user customizations
• Simplify the upgrade process – improve time to value
• Enable consistent and seamless approach across all clients
• No structural changes to API across releases
• Protected to ensure future compatibility and upgradability
20
21. HLLX Overview
How it works (part 1)
• Isolate customer written LE/REXX code from ZMF stc
• VSCR and protection from error/abend
• Separate HLL exit processing address space
• Started/Shut down automatically by ZMF stc
• ZMF user subtask – HLL A/S exit processing subtask
• Initiation/Termination to bracket logical group of exit calls
• HLL A/S subtask initiates LE enclave and/or REXX environment as
required.
• All ‘expected’ functions available from exit program
• File I/O
• ZMF services
• CAF-DB2
• Call external routines
21
22. HLLX Overview
How it works (part 2)
• Published, non-volatile API for each exit point
• New fields/variables added to end of list
• Initially arranged amongst specific UI panel flows/functions
• Package Create – ENH209028 (currently in sandbox)
• Build – ENH210231
• Approval – ENH208969
• Install – ENH210233
• Future exit points added as requested
• Need to validate each for performance implications
• Note: NOT a replacement for existing assembler exits
• These remain unchanged
• Many of the assembler exits have critical performance requirements
22
23. HLLX Detail
Admin
• Exit module details maintained in ZMF admin
• User chosen name for exit program/exec
• Active/Inactive
• LE/REXX
• Two definitions per exit point
• Standard – applies to all
• Debug – applies only to listed userids
• Definitions stored in pmast
• Service call to allow clients to decide, up-front, which HLL exits (if any)
are to be invoked.
23
24. HLLX Detail
Testing/Diagnosis
• Refresh of exit modules
• Disconnect/Reconnect client to pick up exit program/exec changes
• ZMF Modify command to display active exits in SERPRINT
• ZMF Trace class to show data passed to/from each HLL exit point
• Includes timestamp for monitoring delays in customer code.
24
29. xChange www.serena.com/xchange
Miami Beach, September 16th to 18th, 2013
29
• Single ticket $1,895
• 5-Pack $8,500 (only $1,700 each)
• Special pricing for international
• 70 breakout sessions
• 14 dedicated to mainframe
• Answer zone!
• Executive meetings!
• Networking and more
30. Keep in touch
sales@serena.com/support@serena.com/info@serena.com
30
Kevin Parker
Mainframe Product Officer
+1-650-481-3494
kparker@serena.com
Al Slovacek
Senior Director Mainframe Products
+1-818-712-4135
aslovacek@serena.com
Robert “Bob” Aloisio
Vice President Mainframe Sales
+1-516-922-3757
raloisio@serena.com
Jeff Jones
Senior Manager Customer Support
+1-817-684-0707
jjones@serena.com
Greg Hughes
President and CEO
+1-650-481-3418
ghughes@serena.com
NEXT EVENTS
SHARE August 11th
xChange September 16th
Fall VUG October 15th
Notes de l'éditeur
ZMF4ECl 7.1.2 Comments – 1/21/2012John Skelton is going to provide a deep dive into this solution tomorrow.Any code page supported by z/OSNew query package, very powerful in EclipseMulti-select packages and components…BIG USABILITY GAINSA lot of work providing “like” functionality with the ISPF client7.1.2.01 – 06/08/2012We added the eclipse installer. The great thing about the eclipse installer is that it’s a “pull” model..making deployment within the enterprise a lot easier.Better usabilityAnd cusomtizations7.1.2.02 – 09/20/2012RDZ 8.5 supportImproved RDZ integration –Enable RDZ Smart Editing with ZMF apps - Integrating ZMF Syslib concatenation configuration with RDZ propertiesJohn Skelton is going to provide a deep dive into this solution tomorrow.
Serena has always provided support for Pan/Lib but now takes things a step further to provide a robust way to convert off with confidence. Librarian and Panvalet are vintage library management products that address the problem of holding large repositories of editable source code in proprietary monolithic library structuresLibrarianApplied Data Research – Princeton NJ 1959PanvaletPansophic Systems – Chicago IL 1969Both Acquired by Computer AssociatesInsignificant product enhancement in 20 years2000 active PAN/LIB licenses world wide
Execution JCL for typical Pass #1.This should be run several times until duplicates are eliminated, orphan fragments of code are removed and anomalies resolved.Sample report shows component relationships. Copybooks are distinguished from genuine source.
Edit Macro can convert –INC or ++INCLUDE to COPY (not necessary as CMNWRITE is capable of parsing past this) The ISPF dialog is an interactive interface allowing full edit facility.The Edit macro fully automates ++INCLUDES and –INC to language specific COPY or equivalent.(Example here is a Librarian file)
Post processing is mostly investigative; you will not succeed in reaching baseline unless all missing components are available for audit. Duplicates are best eliminated; we do not want duplicate components in baselines. Orphans are fragments of code that were copied and abandoned. Language conformance is a guidance for a decision made by the customer.This report can be passed to second phase for processing, but should be run enough times to get things clean.
Pass #2This is the real work horse. It also produces the same report but copies the identified members and stows them into their respective library types. While doing so, it optionally changes the mechanics of inclusion from ++INCLUDE or -INC to COPY. When the naming structure of included pieces is determined in advance, there should not be any instances of ++INCLUDE ABC10000D7 because we can only support eight characters. If older versions of source and copy are determined by characters 9 and 10 of member name, they are consolidated into the stacked reverse delta. If SRD has been specified, those deltas are calculated and stowed for as many levels back as specified. Meta data is captured and stowed into the PDS(E) directory such as userID, date/time stamp, number of records and some semblance of version.mod.The SRC and CPY are seperated and extracted to PDS libraries.The PDS are staged into ChangeMan development libraries.Optionally, they can be processed via CMNBAHST
Pass #3After a complete cycle, the original library is scanned once more.Components in the base library are marked off the list,and any components that are missing are reported.This is post-operative.When components have been confidently secured in ChangeMan base libraries and component history and archive levels preserved, the report detects components that have may been left behind. Applications will have been segregated, and broken into different libraries based on language type. Members copied to the wrong library because of nonconformance are corrected in the first life cycle before reaching the base library. All ChangeMan packages are audited for completeness.
About 500 Cyl/ secondAs ZMF uses IBM interfaces (PDS, PDSE etc.) we are bound by their naming conventions, customers must resolve illegal member namesDefault behavior is to use positions 9-10 as version numbers
Customers were asked to list the top “3” things Serena has to improve on. ----- Meeting Notes (9/22/11 07:49) -----UpgradeUsabilityReportingAdministratorDoc
true DELTA versions of shipped componentsMake SSV datasets more manageableAllow aging of closed complex and super packages
ERO: Point Product, Mainframe Centric, Release Centric (fixed lifecycle), Requires DB2, Inter-Package Dependencies within a release, ZMF OnlyRM: Enterprise Product, Process-Centric, Customizable Workflows, Spans Platforms, Orchestrates ZMF Via Web Services, Platform/Product Agnostic, Web Interface