220 likes | 388 Views
ZMF – The Platform for the Future. ZMF Roadmap 2008/2009. Q4 08. Q1 09. Q2 09. Q4 09. 5.6.3. 6.1. 6.1.1. 6.2 (Hilo). Maintenance Release Patch release rollup Quick follow up to 6.1. Major Feature Release New I/A Compliance support Improved admin support Enhanced workflow
E N D
ZMF Roadmap 2008/2009 Q4 08 Q1 09 Q2 09 Q4 09 5.6.3 6.1 6.1.1 6.2 (Hilo) • Maintenance Release • Patch release rollup • Quick follow up to 6.1 • Major Feature Release • New I/A • Compliance support • Improved admin support • Enhanced workflow • Performance updates • Platform redesign • EGA: November 2008 • Maintenance Release • EOL release for 5.6.x • Patch release rollup • Last release of APS option • Major Feature Release • ELS • Java/C++/C • HFS Support • Usability / Other • EGA: Q4 2009
The Crystal Ball 250 billion lines of Cobol 4-5 billion lines of new Cobol every year 850,000 Cobol programmers worldwide 5% of Cobol programmers retire per year 1/4 of Cobol programmers will be retired in 5 years Dr. Dobb’s Oct. Issue They say “old soldiers never die, they just fade away” well “Old programs never die and never go away”
Shifting Trends Favor the Mainframe Again Continuous availability is more important in the web world Security and compliance are top of mind Server sprawl has drive up the cost of labor Cost of power is increasing TCO pressure drives consolidation to virtualized platforms Growing use of zLinux Network economics favor consolidation once again IDC believes Big Blue sold $1.6 billion in mainframes in Q2 of 2008, an increase of 31.7 percent
Z/OS the Platform for the Future Near Linear Scale - 900,000+ concurrent users “Mean Time Between Failure” Measured in decades and not months 1/4 network costs 1/25 floor space 1/20 energy requirement 1/5 the administration Highest average resources utilization - >70% vs < 15% Highest concurrent workloads 60% of all System z revenue is driven by new workloads Java, Linux, Database, SOA
ZMF the Platform for the Future Managing ALL software artifacts for the mainframe environment Mainframe centric solution Supporting enterprise applications Across all sites and systems Evolution not Revolution Support current application workloads Support new workloads Support hybrid applications Support new application and workloads Provide developer transparency While providing the same change governance that ZMF customers expect Impact Analysis Audit ZMF package lifecycle
ZMF: Platform for the Future John Skelton Principal Software Developer, SERENA
ZMF Hilo Overview Marching Orders From Marketing/Sales Integrate Extended Language Support (ELS) into ZMF ELS = JAVA, C++, C, ??? ZMF Process and Control remain intact Could we have it next Month?
ZMF Hilo Overview Development responds - we need to add the following big ticket items to make ELS viable: HFS support Language specific options User Interface / Client Updates More than a month
ZMF Hilo Overview Disclaimer Anything subject to change
ZMF Hilo Overview HFS Support Path Names up to 1024 characters Component Names up to 256 characters Path, Component Names are Case Sensitive Impact to almost every ZMF service
ZMF Hilo Overview HFS Support Baseline libraries are defined as HFS Lifecycle libraries must be defined consistently. Staging, Production, Promotion HFS tree treated as single ZMF LIBTYPE Components may include relative pathname
ZMF Hilo Overview HFS Support Baseline defined as /u/src/ /u/src/actions/foo.java /u/src/actions/bar.java /u/src/reports/foo.java /u/src/reports/bar.java Component name(s): actions/foo.java, actions/bar.java reports/foo.java, reports/bar.java
ZMF Hilo Overview HFS Support Package Master layout remains the same HFS names stored as tokens. Component Master moved to LDS from KSDS LDS access through 1 or more Dataspaces Variable length keys – we can support any length Access to PMAST/CMAST data available through XML Services and WebServices
ZMF Hilo Overview Language Specific Options - BUILD Build jobs may run under BPXBATCH Access to USS services Simply customize skeletons
ZMF Hilo Overview Language Specific Options – Impact Analysis No change to I/A for existing languages C/C++ use event side file created during the build process to generate I/A data. Special processing for JAVA - everything is dynamic. I/A Data stored in Dataspace (Holyrood)
ZMF Hilo Overview Language Specific Options – Audit JAVA – JAR processing
ZMF Hilo Overview ISPF User Interface changes Minimal changes to existing panels Panels permit zoom-in on long names ISPF KEYLIST and ZEXPAND
ZMF Hilo Overview UI changes – Eclipse JAVA Development on ISPF = COBOL development using punched cards. Eclipse is the standard for JAVA development
ZMF Hilo Overview UI changes – Eclipse plugin Move existing ZMF integration to Serena Explorer from RDZ Rework RDZ interface for existing users Workspace/Project integration Add project to workspace Synchronize with repository Checkout/Checkin etc… Rename the plugin
ZMF Hilo Overview Hilo Requirements z/OS 1.8 - ISPF File Tailoring – string functions