2 options
Merging systems into a sysplex / [Frank Kyne ... et al.].
- Format:
- Book
- Series:
- IBM redbooks.
- IBM redbooks
- Language:
- English
- Subjects (All):
- System design.
- Parallel processing (Electronic computers).
- IBM computers--Programming.
- IBM computers.
- Physical Description:
- xvi, 412 p. : ill.
- Edition:
- 1st ed.
- Place of Publication:
- [United States] : IBM, International Technical Support Organization, 2002.
- Language Note:
- English
- Contents:
- Front cover
- Contents
- Notices
- Trademarks
- Preface
- The team that wrote this redbook
- Comments welcome
- Chapter 1. Introduction
- 1.1 Why this book was produced
- 1.2 Starting and ending points
- 1.2.1 BronzePlex
- 1.2.2 GoldPlex
- 1.2.3 PlatinumPlex
- 1.3 Structure of each chapter
- 1.3.1 Are multiple subplexes supported or desirable
- 1.3.2 Considerations checklist
- 1.3.3 Implementation methodology
- 1.3.4 Tools and documentation
- 1.4 Terminology and assumptions
- 1.4.1 'Plexes
- 1.5 "Gotchas"
- 1.5.1 Duplicate data set names
- 1.5.2 Duplicate volsers
- 1.5.3 TCP/IP
- 1.5.4 System Logger
- 1.5.5 Sysplex HFS sharing
- 1.5.6 Legal implications
- 1.6 Updates to this document
- Chapter 2. Sysplex infrastructure considerations
- 2.1 One or more XCF subplexes
- 2.2 CDS considerations
- 2.2.1 MAXSYSTEM CDS parameter
- 2.2.2 General CDS guidelines
- 2.3 Cross-System Coupling Facility
- 2.3.1 Considerations for merging XCFs
- 2.4 Coupling Facility Resource Management
- 2.4.1 Considerations for merging CFRM
- 2.5 Sysplex Failure Management
- 2.5.1 Considerations for merging SFM
- 2.6 Automatic Restart Manager
- 2.6.1 Considerations for merging ARM
- 2.7 Tools and documentation
- Chapter 3. System Logger considerations
- 3.1 One or more LOGRplexes
- 3.2 Considerations for merging System Loggers
- 3.2.1 System Logger fundamentals
- 3.2.2 Considerations for different target environments
- 3.2.3 Considerations for the merge
- 3.3 Methodology for merging System Loggers
- 3.4 Tools and documentation
- Chapter 4. WLM considerations
- 4.1 One or more WLMplexes
- 4.1.1 Compatibility mode considerations
- 4.1.2 Configuration options
- 4.2 Merging WLMplexes
- 4.3 Considerations for merging WLMplexes
- 4.4 Methodology for merging WLMplexes
- 4.5 Tools and documentation
- 4.5.1 Tools.
- 4.5.2 Documentation
- Chapter 5. GRS considerations
- 5.1 One or more GRSplexes
- 5.1.1 Star complex
- 5.1.2 Ring complex
- 5.1.3 Target environments
- 5.1.4 Why convert to a Star complex
- 5.2 Considerations for merging GRSplexes
- 5.3 Methodology for merging GRSplexes
- 5.3.1 Merging into a Star complex
- 5.3.2 Merging into a Ring complex (sysplex matches complex)
- 5.3.3 Merging into a Ring complex (mixed GRS complex)
- 5.4 Tools and documentation
- 5.4.1 Tools
- 5.4.2 Documentation
- Chapter 6. SMF considerations
- 6.1 Managing your SMF data
- 6.2 Considerations when merging systems into a sysplex
- 6.3 Tools and documentation
- 6.3.1 Tools
- 6.3.2 Documentation
- Chapter 7. JES2 considerations
- 7.1 JES2 configurations
- 7.2 Methodology for merging JESplexes
- 7.3 Moving to a multi-JESplex environment
- 7.4 Moving to a single JES2plex environment
- 7.4.1 SDSF considerations
- 7.5 Tools and documentation
- Chapter 8. Shared HFS considerations
- 8.1 One or more HFSplexes
- 8.2 Considerations for merging HFSplexes
- 8.3 Methodology for merging HFSplexes
- 8.4 Tools and documentation
- 8.4.1 Tools
- 8.4.2 Documentation
- Chapter 9. Language Environment considerations
- 9.1 Language Environment
- 9.2 LE considerations when merging systems into a sysplex
- 9.3 Compatibility
- 9.3.1 Upward compatibility
- 9.3.2 Downward compatibility
- 9.4 LE run-time options
- 9.4.1 Displaying the run-time values in batch
- 9.4.2 Obtaining the run-time values in CICS
- 9.5 Tools and documentation
- 9.5.1 Tools
- 9.5.2 Documentation
- Chapter 10. System data set considerations
- 10.1 Introduction
- 10.2 System symbols
- 10.3 Sharing sysres
- 10.3.1 Considerations for merging sysres'
- 10.3.2 Methodology for moving to a shared sysres
- 10.4 Sharing Master Catalogs
- 10.4.1 Considerations for merging Master Catalogs.
- 10.4.2 Methodology for merging Master Catalogs
- 10.5 Sharing Parmlib
- 10.5.1 MSTJCLxx Parmlib member
- 10.5.2 COMMNDxx Parmlib member
- 10.5.3 Merging Parmlibs
- 10.6 Proclibs and TSO-related files
- 10.6.1 Merging Proclibs and TSO-related files
- 10.7 Tools and documentation
- 10.7.1 Tools
- 10.7.2 Documentation
- Chapter 11. VTAM considerations
- 11.1 Overview of scope
- 11.1.1 VTAM's job
- 11.1.2 Subarea networking
- 11.1.3 APPN networking
- 11.1.4 How VTAM uses XCF
- 11.1.5 VTAM Generic Resources
- 11.1.6 MultiNode Persistent Sessions
- 11.2 One or more VTAMplexes
- 11.3 Considerations for merging VTAMplexes
- 11.4 Documentation
- Chapter 12. TCP/IP considerations
- 12.1 One or more TCPplexes
- 12.1.1 Target environments
- 12.2 TCP/IP in a sysplex
- 12.2.1 DYNAMICXCF
- 12.2.2 Routing in a sysplex
- 12.2.3 Dynamic VIPA
- 12.2.4 DNS/WLM - Connection Optimization
- 12.2.5 External IP workload balancing
- 12.2.6 Sysplex Distributor
- 12.2.7 TCPplex prerequisites
- 12.3 Considerations for merging TCPplexes
- 12.4 Tools and documentation
- Chapter 13. RACF considerations
- 13.1 One or more RACFplexes
- 13.2 Considerations for merging RACFplexes
- 13.3 Methodology for merging RACFplexes
- 13.3.1 Before you start
- 13.3.2 RACF exits
- 13.3.3 Synchronize RACF options
- 13.3.4 Synchronize the Class Descriptor Table (ICHRRCDE)
- 13.3.5 Synchronize the router table (ICHRFR01)
- 13.3.6 Global Access Checking Facility
- 13.3.7 RACF database merge
- 13.3.8 Things not handled by DBSYNC
- 13.3.9 Password synchronization
- 13.3.10 Cutover
- 13.3.11 Summary
- 13.4 Tools and documentation
- 13.4.1 Tools
- 13.4.2 Documentation
- Chapter 14. SMS considerations
- 14.1 One or more SMSplexes
- 14.2 Considerations for merging SMSplexes
- 14.3 Methodology for merging SMSplexes
- 14.4 Tools and documentation.
- Chapter 15. DFSMShsm considerations
- 15.1 One or more HSMplexes
- 15.2 Considerations for merging HSMplexes
- 15.3 Methodology for merging HSMplexes
- 15.3.1 Merging the CDS
- 15.3.2 Backout
- 15.4 Tools and documentation
- Chapter 16. DFSMSrmm considerations
- 16.1 One or more RMMplexes
- 16.2 Considerations for merging RMMplexes
- 16.3 Methodology for merging RMMplexes
- 16.3.1 Merging the CDSs
- 16.3.2 Backout
- 16.4 Tools and documentation
- 16.4.1 Tools
- 16.4.2 Documentation
- Chapter 17. OPC considerations
- 17.1 One or more OPCplexes
- 17.2 Considerations for merging OPCplexes
- 17.2.1 General notes about the merge project
- 17.3 Methodology for merging OPCplexes
- 17.3.1 Merging OPC system-related definitions
- 17.3.2 Merging the OPC databases
- 17.4 Tools and documentation
- 17.4.1 Tools
- 17.4.2 Documentation
- Chapter 18. System Automation for OS/390 considerations
- 18.1 One or more SA/390 environments
- 18.2 Checklist of considerations for merging SA/390
- 18.3 Tools and documentation
- 18.3.1 Tools
- 18.3.2 Documents and References
- 18.3.3 Group forums
- Chapter 19. Operations considerations
- 19.1 One or more HMCplexes
- 19.1.1 Considerations for merging HMCplexes
- 19.1.2 Security
- 19.1.3 Optical and I/O error analysis
- 19.1.4 Remote access
- 19.1.5 Methodology for merging HMCplexes
- 19.2 Consoles
- 19.2.1 EMCS security
- 19.2.2 Systems Network Architecture (SNA) MCS
- 19.2.3 Console recommendations
- 19.2.4 Considerations for merging consoles
- 19.2.5 Console philosophy
- 19.3 General operations procedures
- 19.3.1 IPL procedures
- 19.3.2 Sysplex Failure Management and Automatic Restart Manager
- 19.3.3 Operational Efficiency
- 19.3.4 JES2 Multi-Access Spool
- 19.3.5 WLM-Managed Initiators
- 19.3.6 Automatic Tape Switching (ATS Star)
- 19.3.7 Shared sysres.
- 19.3.8 Useful Commands
- 19.3.9 Housekeeping
- 19.4 Tools and documentation
- 19.4.1 Tools
- 19.4.2 Documentation
- Chapter 20. Hardware configuration considerations
- 20.1 Introduction
- 20.2 Assumptions
- 20.3 Considerations when merging systems into a sysplex
- 20.4 Single or multiple production IODFs
- 20.4.1 How many master IODFs
- 20.4.2 How many cloned IODFs
- 20.5 HCD and I/O Operations
- 20.5.1 HCD and I/O Operations relationship
- 20.6 Activating a new I/O configuration
- 20.6.1 Performing the dynamic I/O reconfiguration
- 20.6.2 Dynamic I/O reconfiguration with more than one sysplex
- 20.6.3 CONFIGxx Parmlib member
- 20.7 IOCDS management
- 20.8 Duplicate device numbers
- 20.9 NIP console requirements
- 20.10 Eligible Device Table and esoterics
- 20.11 Single or multiple OS Configs
- 20.12 ESCON logical paths
- 20.12.1 DASD control unit considerations
- 20.12.2 Tape control unit considerations
- 20.12.3 Non-IBM hardware
- 20.12.4 Switch (ESCON/FICON) port considerations
- 20.13 CF connectivity
- 20.14 FICON/ESCON CTCs
- 20.14.1 ESCON CTC
- 20.14.2 FICON CTC
- 20.14.3 Differences between ESCON and FICON CTC
- 20.15 Sysplex Timer
- 20.15.1 LPAR Sysplex ETR support
- 20.15.2 Parmlib
- 20.16 Console connectivity
- 20.17 Hardware Management Console (HMC) connectivity
- 20.18 Tools and Documentation
- 20.18.1 Tools
- 20.18.2 Documentation
- Chapter 21. System exits and usermod considerations
- 21.1 Overview
- 21.2 Definitions
- 21.3 Simplicity
- 21.4 Reviewing system modifications
- 21.5 Supporting system modifications
- 21.5.1 Documentation
- 21.5.2 Tracking
- 21.6 Documentation
- 21.7 Useful exits and usermods
- 21.7.1 Duplicate TSO logons in a JES2 MAS
- 21.7.2 ISPF Exit 16: Log, List, and Temporary Data Set Allocation Exit
- 21.7.3 PDF Data Set Name Change Exit
- 21.7.4 JES2 Exit 4.
- Chapter 22. Maintenance considerations.
- Notes:
- "December 2002."
- "SG24-6818-00."
- OCLC:
- 560313623
The Penn Libraries is committed to describing library materials using current, accurate, and responsible language. If you discover outdated or inaccurate language, please fill out this feedback form to report it and suggest alternative language.