The document provides an overview of how to run an implementation project using ZD&T. It describes preparing by identifying requirements, installing a pilot baseline system, configuring the system, integrating host data, applications and configurations, pilot testing, and then designing a long-term system including developing processes and tools.
Short Story: Unveiling the Reasoning Abilities of Large Language Models by Ke...
ZD&T Survival Kit
1. z108251 ZD&T Survival Kit
Michael Erichsen
Xact Consulting A/S
Enterprise Modernization Specialist
2019 IBM Systems Technical University
20 – 24 May | Berlin, Germany
51. Which Challenges have we
met?
z108251 ZD&T Survival Kit
IBM Systems Technical University
20 – 24 May | Berlin, Germany
52. 2019 IBM Systems Technical University
Challenges: IBM-supplied ZD&T System is ready to run, but…
— The effort to adapt it to your environment is a big effort
• The organizational effort is much bigger than the technical effort!
— Customize the ZD&T z/OS system to your environment
— Identify, isolate, extract, copy and integrate applications, data and configurations from the Big Iron
to ZD&T
— Establish maintenance and operations and prepare for future system upgrades
53. 2019 IBM Systems Technical University
Challenges: Application Dependencies on System and Subsystem Names
— Remove dependencies before copying to ZD&T?
— Rename while copying?
— Rename ZD&T default subsystem names?
• This would be a recurring activity for each new version of ADCD
54. 2019 IBM Systems Technical University
Challenges: Data and Application upgrade Strategy
Development
— Deciding how to interact with existing SCM
and ALM systems
▪ Versioning
▪ Build
▪ Promotion
55. 2019 IBM Systems Technical University
Challenges: Data and Application upgrade Strategy
Development
— Deciding how to interact with existing SCM
and ALM systems
▪ Versioning
▪ Build
▪ Promotion
Test
— Identifying a consistent set of test data
from the big iron
▪ Don't move everything
▪ If your SCM is in a mess, then don't rely on
this project to clean it up for you
— Extracting these data to a separate pool
▪ Initial, and recurring
— Agree with operations/service provider on
access to those data
▪ Picking the best tools
— Agree with 3rd party vendors on porting
data unload/reload tools to ZD&T
▪ Licenses?
56. 2019 IBM Systems Technical University
Challenges: System Upgrade Strategy
— In sync with Big Iron?
— In sync with IBM deliveries of ADCD (Pre-packaged z/OS system)?
— Adding SMP/E work for selected subsystems?
— Swapping ADCD packages impacts DB2 and RACF
• Unload DB2 catalog and table spaces before swap using DB2ADM
• Reload after swap
• Unload RACF definitions and authorizations before swap using a REXX EXEC
• Reload after swap
57. 2019 IBM Systems Technical University
Challenges: Security
— General principle
• Agility and flexibility requires more freedom than the Big Iron
— Suggested implementation
• Data and application copied to ZD&T must be cleansed before copying
• Separate RACF system and definitions on ZD&T
• Do not copy the Big Iron RACF database
— Data
• Anonymize and/or filter data
— Applications
• Confidential code
— Handle situations where team A must not see code or data from team B
— Difficult to agree with Big Iron staff on processes and tools for copying to ZD&T and for promoting
changes from ZD&T
58. How to survive the Journey
z108251 ZD&T Survival Kit
IBM Systems Technical University
20 – 24 May | Berlin, Germany