Upgrading to IMS V12 from IMS V10_Best Practices and Lessons Learned - IMS UG Phoenix 12-2013
Upcoming SlideShare
Loading in...5
×
 

Like this? Share it with your network

Share

Upgrading to IMS V12 from IMS V10_Best Practices and Lessons Learned - IMS UG Phoenix 12-2013

on

  • 869 views

 

Statistics

Views

Total Views
869
Views on SlideShare
869
Embed Views
0

Actions

Likes
0
Downloads
16
Comments
0

0 Embeds 0

No embeds

Accessibility

Categories

Upload Details

Uploaded via as Adobe PDF

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

Upgrading to IMS V12 from IMS V10_Best Practices and Lessons Learned - IMS UG Phoenix 12-2013 Presentation Transcript

  • 1. Upgrading to IMS V12 from IMS V10 Best practices and lessons learned Session Number IMS-1012A Jeff M. Sullivan Senior Systems Programmer State of Arizona JeffCaveCreek@gmail.com © 2013 IBM Corporation Dennis Eichelberger IT Specialist zSeries Software IMS ATS deichel@us.ibm.com
  • 2. Trademarks and disclaimers Any opinions, findings, conclusions or recommendations presented in this material are strictly those of the speaker and do not necessarily reflect the views of the Arizona Strategic Enterprise Technology (ASET), Arizona Department of Administration (ADOA) or the State of Arizona. The following are trademarks of the International Business Machines Corporation in the United States, other countries, or both. Not all common law marks used by IBM are listed on this page. Failure of a mark to appear does not mean that IBM does not use the mark nor does it mean that the product is not actively marketed or is not significant within its relevant market. Those trademarks followed by ® are registered trademarks of IBM in the United States; all others are trademarks or common law marks of IBM in the United States. For a complete list of IBM Trademarks, see www.ibm.com/legal/copytrade.shtml: *, AS/400®, e business(logo)®, DBE, ESCO, eServer, FICON, IBM®, IBM (logo)®, iSeries®, MVS, OS/390®, pSeries®, RS/6000®, S/30, VM/ESA®, VSE/ESA, WebSphere®, xSeries®, z/OS®, zSeries®, z/VM®, System i, System i5, System p, System p5, System x, System z, System z9®, BladeCenter® The following are trademarks or registered trademarks of other companies. Adobe, the Adobe logo, PostScript, and the PostScript logo are either registered trademarks or trademarks of Adobe Systems Incorporated in the United States, and/or other countries. Cell Broadband Engine is a trademark of Sony Computer Entertainment, Inc. in the United States, other countries, or both and is used under license therefrom. Java and all Java-based trademarks are trademarks of Sun Microsystems, Inc. in the United States, other countries, or both. Microsoft, Windows, Windows NT, and the Windows logo are trademarks of Microsoft Corporation in the United States, other countries, or both. Intel, Intel logo, Intel Inside, Intel Inside logo, Intel Centrino, Intel Centrino logo, Celeron, Intel Xeon, Intel SpeedStep, Itanium, and Pentium are trademarks or registered trademarks of Intel Corporation or its subsidiaries in the United States and other countries. UNIX is a registered trademark of The Open Group in the United States and other countries. Linux is a registered trademark of Linus Torvalds in the United States, other countries, or both. ITIL is a registered trademark, and a registered community trademark of the Office of Government Commerce, and is registered in the U.S. Patent and Trademark Office. IT Infrastructure Library is a registered trademark of the Central Computer and Telecommunications Agency, which is now part of the Office of Government Commerce. * All other products may be trademarks or registered trademarks of their respective companies. Notes: Performance is in Internal Throughput Rate (ITR) ratio based on measurements and projections using standard IBM benchmarks in a controlled environment. The actual throughput that any user will experience will vary depending upon considerations such as the amount of multiprogramming in the user's job stream, the I/O configuration, the storage configuration, and the workload processed. Therefore, no assurance can be given that an individual user will achieve throughput improvements equivalent to the performance ratios stated here. IBM hardware products are manufactured from new parts, or new and serviceable used parts. Regardless, our warranty terms apply. All customer examples cited or described in this presentation are presented as illustrations of the manner in which some customers have used IBM products and the results they may have achieved. Actual environmental costs and performance characteristics will vary depending on individual customer configurations and conditions. This publication was produced in the United States. IBM may not offer the products, services or features discussed in this document in other countries, and the information may be subject to change without notice. Consult your local IBM business contact for information on the product or services available in your area. All statements regarding IBM's future direction and intent are subject to change or withdrawal without notice, and represent goals and objectives only. Information about non-IBM products is obtained from the manufacturers of those products or their published announcements. IBM has not tested those products and cannot confirm the performance, compatibility, or any other claims related to non-IBM products. Questions on the capabilities of non-IBM products should be addressed to the suppliers of those products. Prices subject to change without notice. Contact your IBM representative or Business Partner for the most current pricing in your geography. 2
  • 3. j1 THIS PAGE LEFT INTENTIONALLY BLANK 3
  • 4. Slide 3 j1 jmspsullivan, 7/30/2013
  • 5. Presentation topics IMS V12 Your environment Before starting the upgrade Pulling down the software The issues we experienced 4
  • 6. IMS V12 Your environment Before starting the upgrade Pulling down the software The issues we experienced 5
  • 7. Your environment - political Make sure every one is on-board − Communicate to everyone − Pull in you IMS DBAs to help − Motivate end users 6
  • 8. Your environment - technical SVCNO SMP/E setup Name standard 7
  • 9. SVCNO 8
  • 10. SVCNO IMS Nucleus SVCNO 9
  • 11. SVCNO DBRC SVCNO 10
  • 12. SVCNO 11
  • 13. LPA library is APF-authorized 12
  • 14. SMP/E - Build a zone for each IMS subsystem 13
  • 15. SMP/E - Build a zone for each IMS subsystem 14
  • 16. SMP/E - Build a zone for each IMS subsystem 15
  • 17. SMP/E - Build a zone for each IMS subsystem Use ZONEEXPORT to get list of datasets Use ZONECOPY to clone the target/distribution Use ZONEEDIT to mass-edit the cloned zone Do not forget to clone those datasets, too!! SA22-7771 SMP/E Commands manual 16
  • 18. SMP/E and IMS – How we did it DDDEF in each target Define for all SDFS* SDXR (IRLM) optional 17
  • 19. SMP/E and IMS – How we did it 18
  • 20. Name standard 19
  • 21. Name standard 20
  • 22. IMS V12 Your environment Before starting the upgrade Pulling down the software The issues we experienced 21
  • 23. Before starting the upgrade Find someone who has done this before IMS SYSGEN Check “what’s new” Review current new features Find any “special” exits and validate they are required 22
  • 24. Short story #1 If skipping a release, make sure all release information is checked!
  • 25. Short story #2 Surprise! We used an IMS reserved word as a database name!
  • 26. Find an IMS mentor and gather knowledge Consider services with knowledge transfer Area IMS user groups (or a DB2 user group if no IMS) Informational PMR Search out your site IBM IMS liaison IBM technical sales people Conferences − IOD − SHARE − IMPACT 25
  • 27. IMS SYSGEN Definitions of databases, transactions, application PSBs, VTAM and non-VTAM devices Dynamic resource definition (DRD) IMS resource definition (IMSRSC) repository 26
  • 28. IMS V12 Your environment Before starting the upgrade Pulling down the software The issues we experienced 27
  • 29. Pulling in the software - Shopz CBPDO No SMP/E environment ServerPac Complete buildup Website: https://www14.software.ibm.com/webapp/ShopzSeries/ShopzSeries.jsp 28
  • 30. Pulling in the software 1 year to get it all installed Consider the RSU maintenance Carefully consider SMP/E ACCEPT 29
  • 31. IMS V12 Your environment Before starting the upgrade Pulling down the software The issues we experienced 30
  • 32. Lessons learned Have a good script Minimal replacement Installation verification program Critical items as documented by Landmines in you SDFSRESL Locking, the IRLM and DMB Know thy toolset Open systems − IBM − Exits and business partners − IMS manual “What’s New” − IMS Connect − Redbooks specific to the IMS release − Common services layer − Open database manager CICS exit 31
  • 33. Conversion script Pre-conversion work − Create and populate .NEW − Stage 1 and 2 − Fix landmines − Verify .NEW versus current Stop IMS + CSL Tooling Landmines − User exits − Sparse routines − Compression routines 32
  • 34. Conversion script ACB Gen Upgrade RECON Start CSL IMS Startup /S <IMS ctl regn>,AUTO=N /r ##,/NRE CHKPT 0 FORMAT ALL. FULL Image Copy RECON flags validated Run an online change if DB/DC Check tooling functionality Critical path IMS DC or CICS transactions 33
  • 35. Minimal replacement Cookie-cutter script − No new libraries − Address spaces do not change Three main PDSs replaced − DFSRESL − MODBLKS − OBJDSET May need to copy randomizing, sparsing, and user-specific routines from .OLD to .NEW Tooling 34
  • 36. The meaning of IVP To a DB2 systems programmer… 35
  • 37. The meaning of IVP To an IMS systems programmer… 36
  • 38. Determine what’s new This will take time Critical items as documented by − − IMS manual “Release Planning” Redbooks specific to the IMS release
  • 39. The IMS catalog and repository New to IMS V12 Why should we care? One person’s opinion Next steps
  • 40. CICS Exit Copied from OLD SDFSRESL to NEW Make sure you can find the source (just in case) Located in INSTALIB(IV3E308J)
  • 41. Non-IMS load modules in SDFSRESL Normal − Compression routines − Randomizers − Secondary index sparse routines Leftovers − Application programs − AOI routines − pre-Columbian art Clean installs are nice
  • 42. Locking, the IRLM, and the DMB
  • 43. Locking, the IRLM, and the DMB
  • 44. Locking, the IRLM, and the DMB
  • 45. Locking, the IRLM, and the DMB
  • 46. Locking, the IRLM, and the DMB
  • 47. Know thy toolset Find all IMS tools being used Compatibility vs Fully-Compliant Combine SMP/E if… − Same vendor used with same DBMS − Usage dictates it should be with IMS SMP/E
  • 48. Only replace things that need replacing…to summarize V10 to V11 to V12 no address space changes Three datasets − DFSRESL − MODBLKS − OBJDSET Critical items − RECON update − Log compatibility PTF − Open Systems (know who is attaching to your IMS subsystem or IMS group − Bring in your customers and partners − Watch for any user exits − Mind the deprecation list
  • 49. QUESTIONS 48
  • 50. IMS has a Catalog: Did you get the memo? Session Number IMS-1013A Jeff M. Sullivan Senior Systems Programmer State of Arizona JeffCaveCreek@gmail.com © 2013 IBM Corporation Nancy G. Stein IT Specialist zSeries Software IMS ATS ngstein@us.ibm.com
  • 51. THIS PAGE LEFT INTENTIONALLY BLANK 50
  • 52. Presentation topics IMS inevitability Technical details Examples Considerations 51
  • 53. It was inevitable Outsourcing Those #%&*@!* servers The monolithic machinery It needs to be pretty Sign of the times Business analytics Decades of IMS data
  • 54. Specifically, what does it mean Decreased skills in the community Paradigm that IMS represents only green-screen The mainframe reinvention − Java service class in WLM − WLM enclave processing − Business analytics with Cognos − DB2 with Netezza – Smart analytics optimizer − zLinux IBM supporting 2 very similar database products
  • 55. The implications to IMS IMS skills are very hard to find Mainframe reinvention Many people know SQL
  • 56. What does it do for me? Tooling Shared knowledge base (if supporting DB2) Simplification
  • 57. Presentation topics IMS inevitability Technical details Examples Considerations 56
  • 58. Presentation topics IMS inevitability Technical details Examples Considerations 57
  • 59. Example – catalog deployment
  • 60. Example – catalog populate
  • 61. Example – DFSDDLT0
  • 62. Example – DFSDDLT0 Refer to database administration manual, chapter 8, “Format of records in the IMS catalog database”
  • 63. Address spaces required
  • 64. Control cards
  • 65. Redbook on IMS connectivity http://www.redbooks.ibm.com/Redbooks.nsf/RedpieceAbstracts/sg248174.html?Open
  • 66. It works correctly when…
  • 67. Connecting to IMS Connect with IMS Explorer
  • 68. IMS Explorer
  • 69. IMS Explorer connectivity
  • 70. Connecting to IMS Connect with IMS Explorer
  • 71. IMS Catalog Benefits • Trusted, online source for IMS metadata • Direct access to IMS metadata in the catalog • Leveraged by the Universal Database Drivers • No need for “local” Java metadata classes 70
  • 72. IMS Catalog Benefits • IMS Catalog • Contains information about IMS program resources, database resources, and relevant application metadata • New ACBGEN Used to auto-populate the catalog • • The IMS Catalog: The Next Step in Simplification and Enterprise Integration http://www-01.ibm.com/software/sw-events/teleconference/D108305C25358T22.html • IMS Enterprise Suite Explorer for Development • Generates DBD/PSB source used to populate the catalog • Enables IMS metadata discovery • IMS Enterprise Suite Explorer: The new face of IMS http://www-01.ibm.com/software/sw-events/teleconference/T929253D59548D24.html 71
  • 73. Presentation topics IMS inevitability Technical details Examples Considerations 72
  • 74. Things to be considered Make sure every one is on-board − Communicate to staff − Pull in you IMS DBAs to help Process changes for rolling in new DBDs and PSBs Management of COPYLIB changes Access to objects - Tooling makes administration easy Auditing changes such as SOx or ISO Changes made without visibility
  • 75. QUESTIONS 74