z/OS: System Setup Guide
- What we need to know to understand this book
- Conventions used in this book
- Summary of changes
- Changes for this edition (SC34-6583-00)
- Customizing your queue managers
- Preparing for customization
- Installable features
- Libraries that exist after installation
- Customizing your queue managers
- Before you start
- Identify the national language support libraries
- Customization summary
- Task 1: Identify the z/OS system parameters
- Task 2: APF authorize the WebSphere MQ load libraries
- Task 3: Update the z/OS link list and LPA
- Early code
- Other code
- Task 4: Update the z/OS program properties table
- Task 5: Define the WebSphere MQ subsystem to z/OS
- Updating the subsystem name table
- Defining command prefix strings
- CPFs in a sysplex environment
- Task 6: Create procedures for the WebSphere MQ queue manager
- Task 7: Create procedures for the channel initiator
- Task 8: Define the WebSphere MQ subsystem to a z/OS WLM service class
- Task 9: Set up the DB2 environment
- Task 10: Set up the Coupling Facility
- Task 11: Implement your ESM security controls
- Task 12: Update SYS1.PARMLIB members
- Task 13: Customize the initialization input data sets
- Initialization data set formats
- Using the CSQINP1 sample
- Using the CSQINP2 samples
- Using the CSQINPX sample
- Task 14: Create the bootstrap and log data sets
- Task 15: Define your page sets
- Task 16: Add the WebSphere MQ entries to the DB2 data-sharing group
- Task 17: Tailor your system parameter module
- Creating your own system parameter module
- Fine tuning a system parameter module
- Altering system parameters
- Using CSQ6SYSP
- Using CSQ6LOGP
- Using CSQ6ARVP
- Task 18: Tailor the channel initiator parameters
- Task 19: Set up Batch, TSO, and RRS adapters
- Task 20: Set up the operations and control panels
- Set up the libraries
- Updating the ISPF menu
- Updating the function keys and command settings
- Task 21: Include the WebSphere MQ dump formatting member
- Task 22: Suppress information messages
- Migrating from a previous version
- Migrating to V6
- Migrating from V5.3.1 and V5.3
- Migrating from earlier unsupported releases of MQSeries
- Migrating from V5.3.1 and V5.3
- Software levels
- Libraries
- Migrating queue-sharing groups to V6
- Set up a new queue-sharing group
- CF structures
- Channel initiators
- Commands
- Initialization input data sets CSQINP1 and CSQINP2
- DB2 plan names
- Clustering
- CICS
- JMS resources
- Changing to full function WebSphere MQ
- Reverting to previous versions
- Coexistence with earlier versions of WebSphere MQ
- Multiple queue manager versions in a queue-sharing group
- Multiple queue manager versions in z/OS
- Operations and control panels
- Application stubs
- Testing your queue manager
- Running the basic installation verification program
- Overview of the CSQ4IVP1 application
- Preparing to run CSQ4IVP1
- Running CSQ4IVP1
- Checking the results of CSQ4IVP1
- Testing for queue-sharing groups
- Preparing to run CSQ4IVP1 for a queue-sharing group
- Running CSQ4IVP1 for a queue-sharing group
- Checking the results of CSQ4IVP1 for a queue-sharing group
- Testing for distributed queuing
- Overview of CSQ4IVPX job
- Preparing to run CSQ4IVPX
- Running CSQ4IVPX
- Checking the results of CSQ4IVPX
- Testing for C, C++, COBOL, PL/I, and CICS
- Customizing for CICS
- Set up the CICS adapter
- Resource definition
- Updating the CSD
- Starting a connection automatically during CICS initialization
- System definition
- SNAP dumps
- Completing the connection from CICS
- Controlling CICS application connections
- Customizing the CICS adapter
- Writing a PLTPI program to start the connection
- The API-crossing exit
- Customizing the CICS bridge
- Set up CICS
- Set up WebSphere MQ
- Security
- Controlling CICS bridge throughput
- Customizing for IMS
- Set up the IMS adapter
- Defining WebSphere MQ to IMS
- Placing the subsystem member entry in IMS.PROCLIB
- Specifying the SSM EXEC parameter
- Preloading the IMS adapter
- Defining WebSphere MQ queue managers to the IMS adapter
- Parameters
- Using the CSQQDEFX macro
- Set up the IMS trigger monitor
- Customizing the IMS bridge
- Monitoring performance and resource usage
- Introduction to monitoring
- Getting snapshots of WebSphere MQ
- Using DISPLAY commands
- Using CICS adapter statistics
- Using WebSphere MQ trace
- Starting WebSphere MQ trace
- Controlling WebSphere MQ trace
- Effect of trace on WebSphere MQ performance
- Using WebSphere MQ online monitoring
- Using WebSphere MQ events
- Using System Management Facility
- Allocating additional SMF buffers
- Reporting data in SMF
- Using other products with WebSphere MQ
- Using Resource Measurement Facility
- Using Performance Reporter for OS/390
- Using the CICS monitoring facility
- Investigating performance problems
- Investigating the overall system
- Investigating individual tasks
- Interpreting WebSphere MQ performance statistics
- Layout of an SMF type 115 record
- The SMF header
- Self-defining sections
- Examples of SMF statistics records
- Processing type 115 SMF records
- Storage manager data records
- Log manager data records
- Message manager data records
- Data manager data records
- Buffer manager data records
- Managing your buffer pools
- Lock manager data records
- DB2 manager data records
- Coupling Facility manager data records
- Interpreting WebSphere MQ accounting data
- Layout of an SMF type 116 record
- The SMF header
- Self-defining sections
- Processing type 116 SMF records
- Common WebSphere MQ SMF header
- Thread cross reference data
- Message manager data records
- Records containing zero CPU time
- Sample subtype zero accounting record
- Thread-level and queue-level data records
- Meaning of the channel names
- Sample subtype 1 and subtype 2 records
- Set up security
- Using RACF classes and profiles
- Using RACF security classes
- RACF profiles
- Switch profiles
- Switches and classes
- How switches work
- Profiles to control subsystem security
- Profiles to control queue-sharing group or queue manager level security
- Resource level checks
- An example of defining switches
- Profiles used to control access to WebSphere MQ resources
- Profiles for connection security
- Connection security profiles for batch connections
- Connection security profiles for CICS connections
- Connection security profiles for IMS connections
- Connection security profiles for the channel initiator
- Profiles for queue security
- Considerations for alias queues
- Using alias queues to distinguish between MQGET and MQPUT requests
- Considerations for model queues
- Close options on permanent dynamic queues
- Security and remote queues
- Dead-letter queue security
- System queue security
- API-resource security access quick reference
- Profiles for processes
- Profiles for namelists
- Profiles for alternate user security
- Profiles for context security
- Profiles for command security
- Profiles for command resource security
- Command resource security checking for alias queues
- Command resource security checking for remote queues
- Using the RESLEVEL security profile
- The RESLEVEL profile
- RESLEVEL and batch connections
- RESLEVEL and system functions
- RESLEVEL and CICS connections
- User IDs checked
- Completion codes
- How RESLEVEL can affect the checks made
- RESLEVEL and IMS connections
- Completion codes
- How RESLEVEL can affect the checks made
- RESLEVEL and channel initiator connections
- Completion codes
- How RESLEVEL can affect the checks made
- RESLEVEL and intra-group queuing
- RESLEVEL and the user IDs checked
- User IDs for security checking
- User IDs for connection security
- User IDs for command security and command resource security
- User IDs for resource security (MQOPEN and MQPUT1)
- User IDs checked for batch connections
- User IDs checked for CICS connections
- User IDs checked for IMS connections
- User IDs used by the channel initiator
- User IDs used by the intra-group queuing agent
- Blank user IDs and UACC levels
- WebSphere MQ security management
- User ID reverification
- User ID timeouts
- Refreshing queue manager security
- Refreshing SSL security
- Displaying security status
- Security installation tasks
- Set up WebSphere MQ data set security
- Set up WebSphere MQ resource security
- Configuring your system to use the Secure Sockets Layer (SSL)
- Auditing considerations
- Auditing RESLEVEL
- Statistics
- Customizing security
- Security problem determination
- Violation messages
- What to do if access is allowed or disallowed incorrectly
- Security considerations for distributed queuing
- The channel initiator
- Cluster support
- Security considerations for using WebSphere MQ with CICS
- Controlling the security of CICS transactions supplied by WebSphere MQ
- CICS adapter user IDs
- User ID checking for WebSphere MQ resources during PLTPI and PLTSD
- Terminal user IDs
- Automating starting of CKTI
- Propagating the CKTI user ID to other CICS transactions
- Security considerations for the CICS bridge
- Authority
- Security considerations for using WebSphere MQ with IMS
- Using the OPERCMDS class
- Security considerations for the IMS bridge
- Connecting to IMS
- Application access control
- Security checking on IMS
- Security checking done by the bridge
- Using RACF passtickets in the IMS header
- Example security scenarios
- The two queue managers scenario
- Security switch settings
- WebSphere MQ object definitions
- User IDs used in scenario
- Security profiles and accesses required
- The queue-sharing group scenario
- Security switch settings
- WebSphere MQ object definitions
- User IDs used in scenario
- Security profiles and accesses required
- WebSphere MQ security implementation checklist
- Appendixes
- Appendix A. Migrating from an unsupported release of MQSeries
- Additional steps when migrating from V5.2
- System parameters
- Queue-sharing groups
- CF structures
- Context profiles
- Channel initiator
- Objects
- Libraries
- CICS message table names
- DEFINE MAXSMSGS command
- Additional steps when migrating from V2.1
- Additional steps when migrating from V1.2
- Coexistence of WebSphere MQ V5.3.1 and earlier versions
- Multiple queue manager versions in a queue-sharing group
- Multiple queue manager versions in z/OS
- Operations and control panels
- Application stubs
- Appendix B. Upgrading and applying service to TCP/IP, Language Environment, or z/OS Callable Services
- Running a REPORT CALLLIBS job
- Running a LINK CALLLIBS job
- Appendix C. Using OTMA exits in IMS
- Exit names
- Specifying the destination resolution user exit name
- Naming convention for IMS destination
- A sample scenario
- The pre-routing exit DFSYPRX0
- The destination resolution user exit
- Appendix D. Notices
- Trademarks
- Figures
- Tables
- Index