Download to read offline
Uploaded byNavita Sood
Sneak Peek into the New ChangeMan ZMF Release
The document provides updates on Serena Software's changeman ZMF 8.1.1, including new features and enhancements addressing over 200 change requests. It outlines support for IPv6, automatic restart management, private and public TLS configurations, as well as improvements in repository management. Additionally, it mentions the release timelines for various software versions and their operational functionalities.
More Related Content
Similar to Sneak Peek into the New ChangeMan ZMF Release
Sneak Peek into the New ChangeMan ZMF Release
- 1. 1 Copyright © SerenaSoftware 2016 Mainframe Virtual User Group – January 2016
- 2. 2 Move Fast WithoutBreaking Things HRLEs Highly Regulated Large Enterprises Speed without risk End-to-end Practitioner specific Collaboration enabled Enterprise scaled Supporting all Enterprise methodologies Enterprise technologies Enterprise platforms
- 3. 3 News, Events andAnnouncements Product Update ChangeMan ZMF 8.1.1 Preview Q&A Agenda
- 4. 4 Serenade – Serena’sBi-Annual Mainframe Newsletter • New format • Content resides on Serena Central • Contributions by • Partners • Customers • Product Team • Support • ProServ • Tech Tips • Industry Insights • Events • Published Jan 28th
- 5. 5 Serena at ShareSan Antonio Visit us at Booth #608 And Enter to Win a MiPosaur DevOps in the Enterprise
- 6. 6 Old Repositories • Can’tmodernize • Can’t control • Can’t integrate • Can’t maintain workforce RAMP Up Your Old Repositories RAMP Repository Automated Migration Process Free automated assessment of the current state of the repository Free analysis of assessment report with recommendations
- 7. 7 Copyright © SerenaSoftware 2016 Products Update Al Slovacek Vice President, Mainframe Products
- 8. 9 • Continues thetheme of 8.1 that GA’d October 2014 • Over 200 Change Request have been addressed. • ~75 Enhancement requests including • IPV6 Support • DB2 Native Stored Procedures • Support for IBM ARM (Automatic Restart Manager) • Additional XML service calls • Cmponent / List / Pkg • Calendar/Summary/Service • Second phase of HLLX exits • Additional HLLX exits • Minor refinements to HLLX based on feedback • ZMF4ECL support for the LPEX Editor ChangeMan ZMF 8.1.1 overview
- 9. 10 • Continued.. • ClientPack Support for IBM AT-TLS • Additional Sort options provided to ISPF panels • Application admin baseline panels CMNCBAS1, CMNCBAS2. • Application production libraries panel CMNCPRDL. • Application update across applications baseline panel CMNCBAS3. • Application update across applications production libraries panel CMNCPRD2. • Global library type selection list panel CMNGLTPL within application admin library types, promotion, baseline and production libraries. • Minor changes to CUA based on feedback • Dynamic support for SKIP(OFF/ON) toggle based on feedback requests • Planned GA date for V8.1.1 of ChangeMan ZMF and Client Pack 8.1.1 – March 18 2016 ChangeMan ZMF 8.1.1 overview
- 10. 11 • ~75 CRs/ 44 enhancements / defect backlog • Fall time change • UI consistency (V01-V10 variable support in Client Pack) • HLLX: Release area checkin • Stage or copy components from another package • SORT enhancements • GA TBD ChangeMan ZMF 8.1.2
- 11. 12 Special Interest Groups(SIGs) SERENA SOFTWARE INC. ZMF 8.2 ZMF and Adabas/Natural ZMF Upgrade ZMF Reporting ZMF Online Forms Manager ZMF User Defined Impact Analysis ZMF and Stored Procedures Comparex Mainframe SIGs Serena Central
- 12. 14 ChangeMan ZMF H1 CY15H2 CY15 H1 CY16 Legend Draft Proposed Construction Shipped CP 8.1 ZMF 8.1.1 CP 8.1.1 ZMF 7.1.3.03 CP 7.1.3.02 End of Development for ZMF 7.1.3 and 7.1.3.01 End of Development for Client Pack 7.1.3, 7.1.3.01 and 7.1.3.02 ZMF 8.1.0.01 CP 8.1.0.01 End of Support for ChangeMan ZMF v7 August 31, 2016 8.1.2 CP 8.1.2
- 13. 15 ChangeMan SSM andStarTool ChangeMan SSM 8.5.1 Improved RTCT for SYS1.PARMLIB Improved RTCT PROCLIB concatenation Improved serialization of tracking by multiple SSM tasks Automatic Restart Management Email notification extended to Global Capture Suppress dup entries from ‘Tracked Objects’ List ‘AUTODELTA’ to enable DELTA tracking for OI-tracked datasets z/OS 2.3 positioning Maintenance rollup Target GA 2016-02-26 FDM 7.8.0.03 Performance enhancements VSAM improvements DB2 improvements IMS improvements ~25 defects addressed Maintenance rollup Target GA 2016-02-26 DA 5.7.3 CICS TS 5.3 support COBOL 5.1 support Enhancements to DA-ZMF integration Maintenance rollup Target GA 2016-02-26
- 14. 16 ChangeMan SSM, Comparexand StarTool roadmap H1 CY15 H2 CY15 H1 CY16 Legend Draft Proposed Construction Shipped SSM 8.5 CPX 8.8 FDM 7.8.0.02 CPX 8.7.1.02 IOO 3.1.5.01 SSM 8.5.1 DA 5.7.3 FDM 7.8.0.03
- 15. 17 Copyright © SerenaSoftware 2016 ChangeMan ZMF 8.1.1 Preview ChangeMan ZMF R&D Team
- 16.
- 17. 19 • IPV6 providessupport for 128-bit IP addresses and 253-byte DNS names • External representation of 128-bit address requires up to 39 characters • SER#PARM is a registry of started tasks and their TCP/IP contact information; prior to 8.1.1: • Only provides 15 characters for either the IP address or the DNS name • Dataset format is F/80 (can not provide for a DNS name > 52 characters in length) • SER#PARM in 8.1.1 • New member format to cater for DNS names up to 52 characters • Automatic update to new member format when STC initializes • If DNS name > 52 characters warning message is issued and IP address is adopted • If DNS name > 52 characters is a requirement: • SER#PARM must be manually changed to RECFM=V,LRECL=281 • DNS name may be up to 253 bytes • BEWARE – if SER#PARM is changed to RECFM=V then all STCs MUST be running 8.1.1 SerNet 8.1.1 Implementation of support for TCP/IP V6
- 18. 20 • Old formatof SER#PARM members: * SMFI.SUBS APP DOT.TED.DEC.MAL PORT# TCPIPROC --Update-Time-Stamp— D001.SERU XCH 10.35.11.101 06414 2015/01/12 - 13:32:41 • New format of SER#PARM members: * SMFI S APP TCPIPROC PORT# ADDR D001 U XCH 06414 D001 • No other changes of any kind are required for IPV6 support SerNet 8.1.1 Implementation of support for TCP/IP V6
- 19. 21 • Automatic RestartManagement (ARM) is one of the z/OS Sysplex Services • ARM provides for the automatic restarting of registered elements. Two types of restart: • ‘Local’ – deals with a failing job • ‘Cross-system’ – deals with a failing LPAR • New SERSYSIN parameter of ARM=YES|NO (where ARM=NO is the default) • NB: ARM can be disabled by the z/OS sysprog so setting ARM=YES may not work SerNet 8.1.1 Support for ARM
- 20. 22 • Local restartsare simple • Cross-system restarts are not so simple. Serena recommends that you: • Identify which STCs you want to protect • Identify where each will be restarted in the case of an LPAR failure • Code an ARM policy specifying a TARGET_SYSTEM (single alternate LPAR) or TARGET_LIST (multiple alternates) • Ensure the ARM policy is active (SETXCF START command) • TEST ! • Some considerations for cross-system restarts: • Same JCL or START command will be used for the restart • All required datasets must be available on the restart LPAR • JES may be configured differently between LPARs so be careful with proclibs • System symbols used will be those of the failing LPAR, not the restart LPAR • Serena products will need to be licensed to run on the restart LPAR • TCP/IP definitions will need to be consistent SerNet 8.1.1 Support for ARM
- 21. 23 Demonstration of newHLL exits approve and revert www.serena.com John Hearn
- 22. 24 New HLL Exitsintroduced in 8.1.1. (prioritized by customer base) 1. 2 Build Component checkin, stage, build, recompile, relink 2. 3 Package Create Initial create of a package 3. 4 Package Update Subsequent update of package attributes 4. 5 File Tailoring Define customized ISPF variables for file tailoring 5. 6 Checkout Component Checkout from baseline/promotion 6. 7 Promote/Demote Promotion and demotion of components 7. 8 Audit Audit job submission and audit process 8. 9 Freeze Package freeze and selective unfreeze/refreeze 9. A Approve/Reject Package approve and reject 10.B Revert Package revert DemonstrationofnewHLLexitsapproveandrevert HLLX Approve/Reject
- 23. 25 One of therequests relating to the new Approve/Reject HLL exit was to present error (warning) messages to a user regarding potential errors in the package, but allow the user to ignore the warnings and continue, or cancel the approval and request that the problems are fixed beforehand. This demonstration shows a way of achieving this Using the new VPOOL facility available in the High Level exits to store the package number and referring to it before issuing the error message to see if this user has already attempted to approve the package beforehand. Once the message has been issued, store the new package number to signal that the warning message has been issued. HLLX Approve/Reject
- 24.
- 25. 27 • SSL –Secure Sockets Layer • Developed by Netscape ~ 1995 • TLS – Transport Layer Security • Developed ~ 1999 as an upgrade to SSL 3.0 • AT/TLS – Application Transparent / Transport Layer Security • Adds TLS support to z/OS applications • Works with communications manager ZMF TLS Support - Terms
- 26. 28 • ZMF supportfor TLS implemented via AT/TLS • No code changes to ZMF or Sernet • Support added to ZMF4ECL, ZDD, Web Services • Support added at TCP/IP Socket level ZMF TLS Support
- 27. 29 • Obtain Certificatesfrom Certificate Authority (CA) • Setup AT/TLS rules for ZMF • Configure Tomcat / Web Server • Configure ZMF4ECL • Configure ZDD ZMF TLS Support - Setup
- 28. 30 • AT/TLS ConfigurationAssistant (zOSMF in future) • Configure Policy Agent (PAGENT) • Configure SYSLOGD • AT/TLS Rule for Server • All connections TLS enabled for specified port range • Server Role • AT/TLS Rule for z/OS Clients • All connections targeting Server Port range TLS enabled. • Client Role AT/TLS Configuration for ZMF
- 29. 31 • Configure SecurePort – Default is 8443 • Points to keystore file with Certificate • Install Latest ZMF 8.1.1 Web Services Tomcat Configuration Updates
- 30. 32 • Install latestZMF4ECL version (8.1.1) • Update ZMF4ECL Server Definitions to use TLS ZMF4ECL Configuration
- 31. 33 • Install latestZDD version (8.1.1) • Update ZDD Server Definitions to use TLS ZDD Configuration
- 32. 34 • Full functionalityof LPEX / COBOL/ PL1 editors from Serena Explorer • No Checkout to personal • Feature enabled by default • All component types supported ZMF4ECL Smart Editor Support
- 33.
- 34. 36 • Administration • Generaltoken templates • CMNDB2DD HLL exit point • SQL process installation CMN21 • Demo • Data Studio ZMF package • DB2 Native-SQL SP versioning • Use of general token templates • Use of HLL exit • Automatic activation of new version • Replacement of prior version on demote Native-SQL stored procedures
- 35.
Editor's Notes
- #3 Who is Serena? Founded in 1980 500 employees $200m annual revenue About Serena Software Serena Software is the largest independent Application Lifecycle Management (ALM) vendor with more than 2,500 active enterprise customers. Highly regulated large enterprises (HRLEs) depend on Serena’s application development and deployment solutions every day to help them move fast without breaking things. Serena supports all enterprise methodologies (Agile to Waterfall to DevOps), technologies (Open Source to Proprietary) and platforms (Mainframe to Mobile) from one end of the SDLC to the other. Award winning support teams, legendary domain experts and exceptional and experienced practitioners engage with customers daily to speed software delivery, eliminate risk, enforce compliance and maximize productivity. Headquartered in Silicon Valley, Serena is a portfolio company of HGGC, a leading middle market private equity firm. More information is available on the company’s website at www.serena.com.
- #4 Ladies and Gentlemen: Welcome to Serena’s October Mainframe Virtual User Group. My name is Mark Levy, Product Marketing Director and I am the moderator for today’s online event, We have a great virtual user group program for you today. We are going to open up with some news and events. What Serena has been up to and what we are doing. I’m than going to hand it over the Al Slovacek, VP of Mainframe Products. Al is going to give you a product roadmap and than we have one of our ZMF experts, Tom Mavor presenting on the “Top 5 Practices of a Highly Successful ChangeMan ZMF Administrator” but first.
- #6 We are going to be at Share San Antonio in February.
- #13 SP Support for IBM Data Studio in developing Stored Procedures HLLX exit points Freeze Approve/Reject Revert Checkout
- #16 Service Enablement – ENH246810: A generalized product API - Peer to peer communication among SSM tasks - Communication to ChangeMan ZMF, Sernet and related tasks - Integration into SBM etc. - Eclipse This first version addresses the integration into SBM. When a change basket is successfully created, a ticket is opened. When the change basket is applied, the ticket status is first checked to see if it is in the appropriate state. The SBMXML command creates an object containing the information necessary to connect to the SBM server. The CR ticket id and table id (TS_ID) information is stored within the Change Basket header. Templating - ENH246811: This enhancement invokes during the IMPORT of change baskets. O.I. ENH77568, 109382 SMPE: ENH89566 GDG: ENH92441: support in fingerprint and change basket data sets for new and delete of GDG base dataset REPLACE: ENH196053: can replace existing modules during a RECOVER command of Change Tracking MRT: ENH197240: Supports FIND in addition to BLDL RTO/HSM: ENH199626 increases the accuracy of the event information by picking up the HMIGRATE, HRECALL, and HDELETE data set events when they happen, instead of relying on Global Capture or a CLOSE-driven capture.
- #19 One of the requests relating to the new Approve/Reject HLL exit was to present error (warning) messages to a user regarding potential errors in the package, but allow the user to ignore the warnings and continue, or cancel the approval and request that the problems are fixed beforehand. This demonstration shows 2 ways of achieving this – by using the new VPOOL facility in the approve HLLX, and by presenting the warning message in the revert reasons in the revert HLLX, and requiring the user to overtype the warning message to acknowledge before continuing.
- #24 One of the requests relating to the new Approve/Reject HLL exit was to present error (warning) messages to a user regarding potential errors in the package, but allow the user to ignore the warnings and continue, or cancel the approval and request that the problems are fixed beforehand. This demonstration shows 2 ways of achieving this – by using the new VPOOL facility in the approve HLLX, and by presenting the warning message in the revert reasons in the revert HLLX, and requiring the user to overtype the warning message to acknowledge before continuing.
- #27 One of the requests relating to the new Approve/Reject HLL exit was to present error (warning) messages to a user regarding potential errors in the package, but allow the user to ignore the warnings and continue, or cancel the approval and request that the problems are fixed beforehand. This demonstration shows 2 ways of achieving this – by using the new VPOOL facility in the approve HLLX, and by presenting the warning message in the revert reasons in the revert HLLX, and requiring the user to overtype the warning message to acknowledge before continuing.
- #36 One of the requests relating to the new Approve/Reject HLL exit was to present error (warning) messages to a user regarding potential errors in the package, but allow the user to ignore the warnings and continue, or cancel the approval and request that the problems are fixed beforehand. This demonstration shows 2 ways of achieving this – by using the new VPOOL facility in the approve HLLX, and by presenting the warning message in the revert reasons in the revert HLLX, and requiring the user to overtype the warning message to acknowledge before continuing.