z/OS: Concepts and Planning
- Introduction
- What is a message?
- What is a queue?
- What is a WebSphere MQ object?
- What is a queue manager?
- The queue manager subsystem
- Shared queues
- Page sets and buffer pools
- Logging
- Tailoring the queue manager environment
- Recovery and restart
- Security
- Availability
- Manipulating objects
- Monitoring and statistics
- Application environments
- What is a channel initiator?
- Queue manager clusters
- WebSphere MQ for z/OS concepts
- Shared queues and queue-sharing groups
- What is a shared queue?
- Any queue manager can access messages
- Queue definition shared by all queue managers
- What is a queue-sharing group?
- Where are shared queue messages held?
- The Coupling Facility
- The CF structure object
- Backup and recovery
- Advantages of using shared queues
- High availability
- Distributed queuing and queue-sharing groups
- Shared channels
- Intra-group queuing
- Clusters and queue-sharing groups
- Where to find more information
- Storage management
- Page sets
- Storage classes
- How storage classes work
- Buffers and buffer pools
- Where to find more information
- Logging
- What logs are
- Archiving
- Dual logging
- Log shunting
- Log data
- Unit-of-recovery log records
- Checkpoint records
- Page set control records
- CF structure backup records
- How the log is structured
- Physical and logical log records
- How the logs are written
- When the active log is written
- Dynamically adding log data sets
- When the archive log is written
- WebSphere MQ and SMS
- What the bootstrap data set is for
- Archive log data sets and BSDS copies
- Where to find more information
- Defining your system
- Set system parameters
- Defining system objects
- System default objects
- System command objects
- System administration objects
- Channel queues
- Cluster queues
- Queue-sharing group queues
- Storage classes
- Dead-letter queue
- Default transmission queue
- Pending data queue
- Tuning your queue manager
- Syncpoints
- Expired messages
- Sample definitions supplied with WebSphere MQ
- The CSQINP1 samples
- CSQ4INSG system object sample
- CSQ4INSS system object sample
- CSQ4INSX system object sample
- CSQ4INSJ system JMS object sample
- CSQ4INSR object sample
- CSQ4INYD object sample
- CSQ4INYC object sample
- CSQ4INYG object sample
- CSQ4INYS/CSQ4NQR object samples
- CSQ4DISP display sample
- CSQ4INPX sample
- CSQ4IVPQ and CSQ4IVPG samples
- Where to find more information
- Recovery and restart
- How changes are made to data
- Units of recovery
- Backing out work
- How consistency is maintained
- Consistency with CICS or IMS
- How consistency is maintained after an abnormal termination
- What happens during termination
- Normal termination
- Abnormal termination
- What happens during restart and recovery
- Understanding the log range required for recovery
- Determining which application has a long running unit of work
- Rebuilding queue indexes
- How in-doubt units of recovery are resolved
- How in-doubt units of recovery are resolved from CICS
- How in-doubt units of recovery are resolved from IMS
- How in-doubt units of recovery are resolved from RRS
- Shared queue recovery
- Transactional recovery
- Peer recovery
- Shared queue definitions
- Logging
- Coupling Facility failure
- Where to find more information
- Security
- Why we need to protect WebSphere MQ resources
- If you do nothing
- Security controls and options
- Subsystem security
- Queue manager or queue-sharing group level checking
- Controlling the number of user IDs checked
- Resources we can protect
- Connection security
- API-resource security
- Command security
- Command resource security
- Channel security
- Secure Sockets Layer (SSL)
- Where to find more information
- Availability
- Sysplex considerations
- Shared queues
- Shared channels
- WebSphere MQ network availability
- Using the z/OS Automatic Restart Manager (ARM)
- Using the z/OS Extended Recovery Facility (XRF)
- Where to find more information
- Commands
- Issuing commands
- Private and global definitions
- Directing commands to different queue managers
- Command summary
- Initialization commands
- The WebSphere MQ for z/OS utilities
- The CSQUTIL utility
- The data conversion exit utility
- The change log inventory utility
- The print log map utility
- The log print utility
- The queue-sharing group utility
- The active log preformat utility
- The dead-letter queue handler utility
- Where to find more information
- Monitoring and statistics
- Online monitoring
- WebSphere MQ trace
- Events
- Where to find more information
- WebSphere MQ and other products
- WebSphere MQ and CICS
- The CICS adapter
- Control functions
- MQI support
- Adapter components
- Alert monitor
- Auto-reconnect
- Task initiator
- Multitasking
- The API-crossing exit
- CICS adapter conventions
- The CICS bridge
- When to use the CICS bridge
- Running CICS DPL programs
- Running CICS 3270 transactions
- Where to find more information
- WebSphere MQ and IMS
- The IMS adapter
- Using the adapter
- System administration and operation with IMS
- The IMS trigger monitor
- The IMS bridge
- What is OTMA?
- Submitting IMS transactions from WebSphere MQ
- Where to find more information
- WebSphere MQ and z/OS Batch and TSO
- Introduction to the Batch adapters
- The Batch/TSO adapter
- The RRS adapter
- Where to find more information
- WebSphere MQ and WebSphere Application Server
- Connection between WebSphere Application Server and a queue manager
- Using WebSphere MQ functions from JMS applications
- Planning your WebSphere MQ environment
- Planning your storage and performance requirements
- Address space storage
- Common storage
- Queue manager private region storage usage
- Channel initiator private region storage usage
- Data storage
- Library storage
- System LX usage
- z/OS performance options for WebSphere MQ
- Determining z/OS workload management importance and velocity goals
- Where to find more information
- Planning your page sets and buffer pools
- Planning your page sets
- Page set usage
- Number of page sets
- Size of page sets
- Calculating the size of your page sets
- Page set zero
- Page sets 01 to 99
- Enabling dynamic page set expansion
- Defining your buffer pools
- Planning your Coupling Facility and DB2 environment
- Defining Coupling Facility resources
- Planning your structures
- Planning the size of your structures
- Mapping shared queues to structures
- Planning your DB2 environment
- DB2 storage
- Planning your logging environment
- Planning your logs
- Log data set definitions
- Logs and archive storage
- Planning your archive storage
- Should your archive logs reside on tape or DASD?
- Planning for backup and recovery
- Recovery procedures
- Tips for backup and recovery
- Periodically take backup copies
- Do not discard archive logs you might need
- Do not change the DDname to page set association
- Recovering page sets
- How often should a page set be backed up?
- Recovering CF structures
- Achieving specific recovery targets
- Periodic review of backup frequency
- Backup and recovery with DFHSM
- Recovery and CICS
- Recovery and IMS
- Preparing for recovery on an alternative site
- Example of queue manager backup activity
- Planning to install WebSphere MQ
- WebSphere MQ Prerequisites
- Hardware requirements
- Software requirements
- Additional requirements for some features
- Non-IBM products
- Clients
- Delivery
- Making WebSphere MQ available
- Installing WebSphere MQ for z/OS
- National language support
- Communications protocol and distributed queuing
- Naming conventions
- Using command prefix strings
- Customizing WebSphere MQ and its adapters
- Using queue-sharing groups
- Verifying your installation of WebSphere MQ for z/OS
- What's changed in WebSphere MQ v6
- What's new in WebSphere MQ for z/OS
- Security
- Page sets and buffer pools
- Dynamically add log data sets to an active queue manager
- Display connection information (DISPLAY CONN command)
- Commands
- Queue sharing group improvements
- Improved cluster workload management
- Improvements to SSL support
- Integrated accounting and statistics data formatter
- Online monitoring
- Channels
- Channel initiator
- CICS bridge improvements
- Software prerequisites
- Removed features
- Migration from previous versions
- Migration from V5.3.1
- Additional steps related to migration from V5.3
- Migration from earlier versions
- Migration to full function WebSphere MQ
- Reverting to a previous version
- Coexistence with earlier versions of WebSphere MQ
- Appendixes
- Appendix A. Macros intended for customer use
- General-use programming interface macros
- Product-sensitive programming interface macros
- Appendix B. Measured usage license charges with WebSphere MQ for z/OS
- Appendix C. Notices
- Trademarks
- Index