z/OS: System Admin. Guide
- z/OS: System Admin. Guide
- Figures
- Tables
- About this book
- Who this book is for
- What we need to know to understand this book
- Conventions used in this book
- Syntax diagrams
- How to read railroad diagrams
- How to read dotted decimal diagrams
- Summary of changes
- Changes for this edition (SC34-6585-00)
- Operating WebSphere MQ for z/OS
- Operating WebSphere MQ for z/OS
- Issuing commands
- Issuing commands from a z/OS console or its equivalent
- Issuing commands from the utility program CSQUTIL
- Introducing the operations and control panels
- Invoking the operations and control panels
- Rules for the operations and control panels
- Objects and actions
- Object dispositions
- Choosing a queue manager
- Using the function keys
- Using the command line
- Using the operations and control panels
- Defining objects
- Defining a local queue
- When your local queue definition is complete
- Defining other types of objects
- Working with object definitions
- Altering an object definition
- Displaying an object definition
- Delete an object
- Working with namelists
- Starting and stopping a queue manager
- Before you start WebSphere MQ
- Starting a queue manager
- Start options
- Starting after an abnormal termination
- User messages on start-up
- Stopping a queue manager
- Stop messages
- Writing programs to administer WebSphere MQ
- Understanding how it all works
- Before you begin
- Preparing queues for administration programs
- Defining the system-command input queue
- Defining a reply-to queue
- Opening the system-command input queue
- Opening a reply-to queue
- Using the command server
- Identifying the queue manager that processes your commands
- Starting the command server
- Sending commands to the command server
- Putting messages on the system-command input queue
- Retrieving replies to your commands
- Waiting for a reply
- The reply message descriptor
- Interpreting the replies
- Using the DISPLAY commands
- Examples of commands and their replies
- Messages from a DEFINE command
- Messages from a DELETE command
- Messages from DISPLAY commands
- Messages from commands with CMDSCOPE
- Messages from commands that generate commands with CMDSCOPE
- If you do not receive a reply
- Passing commands using MGCRE
- WebSphere MQ and CICS
- Operating the CICS adapter
- Invoking the adapter's control functions
- From the CICS adapter control panels
- From the CICS command line
- From CICS application programs
- Accessing the CICS adapter control panels
- Starting a connection
- Starting a connection from the CICS adapter control panels
- Starting a connection from the CICS command line
- Starting a connection from a CICS application program
- Stopping a connection
- Stopping a connection from the CICS adapter control panels
- Stopping a connection from the CICS command line
- Stopping a connection from a CICS application program
- Modifying a connection
- Modifying a connection from the CICS adapter control panels
- Modifying a connection from the CICS command line
- Modifying a connection from a CICS application program
- Displaying details of connections and CICS tasks
- Displaying details of a connection from the CICS adapter control panels
- Starting an instance of the task initiator CKTI
- Starting CKTI from the CICS adapter control panels
- Starting CKTI from the CICS command line
- Starting CKTI from a CICS application program
- Starting CKTI automatically
- Stopping an instance of CKTI
- Stopping an instance of CKTI from the CICS adapter control panels
- Stopping an instance of CKTI from the command line
- Stopping an instance of CKTI from an application program
- Displaying the current instances of CKTI
- Displaying the current instances of CKTI from the CICS adapter control panels
- Displaying CICS task information
- Displaying CICS tasks from the CICS adapter control panels
- Displaying connection status and in-flight tasks
- Purging tasks that are using the CICS adapter
- Shutting down a connection between WebSphere MQ and the CICS adapter
- Orderly shutdown
- Forced shutdown
- Operating the CICS bridge
- Starting the CICS bridge
- Shutting down the CICS bridge
- WebSphere MQ and IMS
- Operating the IMS adapter
- Controlling IMS connections
- Connecting from the IMS control region
- Initializing the adapter and connecting to the queue manager
- Thread attachment
- Displaying in-doubt units of recovery
- Recovering in-doubt units of recovery
- Resolving residual recovery entries
- Controlling IMS dependent region connections
- Connecting from dependent regions
- Region error options
- Monitoring the activity on connections
- Disconnecting from dependent regions
- Disconnecting from IMS
- Controlling the IMS trigger monitor
- Starting CSQQTRMN
- Stopping CSQQTRMN
- Controlling the IMS bridge
- Starting and stopping the IMS bridge
- Controlling IMS connections
- Controlling bridge queues
- Resynchronizing the IMS bridge
- Considerations for Commit mode 1 transactions
- Delete messages from IMS
- Delete Tpipes
- Managing WebSphere MQ resources
- Managing the logs
- Archiving logs with the ARCHIVE LOG command
- Restarting the log archive process after a failure
- Controlling archiving and logging
- Printing log records
- Recovering logs
- Discarding archive log data sets
- Automatic archive log data set deletion
- Manually deleting archive log data sets
- The impact of log shunting
- Managing the BSDS
- Finding out what the BSDS contains
- Time stamps in the BSDS
- Active log data set status
- Changing the BSDS
- Changes for active logs
- Changes for archive logs
- Recovering the BSDS
- Managing page sets
- How to add a page set to a queue manager
- What to do when one of your page sets becomes full
- How to balance loads on page sets
- Moving a non-shared queue
- How to expand a page set
- Defining a page set to be larger than 4GB
- Altering a page set to allow automatic expansion
- Moving messages to a new, larger page set
- How to reduce a page set
- How to reintroduce a page set
- How to back up and recover page sets
- Creating a point of recovery for non-shared resources
- Recovering page sets
- How to delete page sets
- How to back up and restore queues using CSQUTIL
- Managing buffer pools
- How to change the number of buffers in a buffer pool
- How to delete a buffer pool
- Managing queue-sharing groups and shared queues
- Managing queue-sharing groups
- Adding a queue-sharing group to the DB2 tables
- Adding a queue manager to a queue-sharing group
- Removing a queue manager from a queue-sharing group
- Removing a queue-sharing group from the DB2 tables
- Validating the consistency of DB2 definitions
- Managing shared queues
- Recovering shared queues
- Moving shared queues
- Migrating non-shared queues to shared queues
- Suspending a connection to DB2
- Managing group objects
- Managing the Coupling Facility
- Adding a Coupling Facility structure
- Removing a Coupling Facility structure
- Recovery and restart
- Restarting WebSphere MQ
- Restarting after a normal shutdown
- Restarting after an abnormal termination
- Restarting if you have lost your page sets
- Restarting if you have lost your log data sets
- Restarting if you have lost your CF structures
- Recovering a single queue manager at an alternative site
- Fast copy techniques
- Recovering a queue-sharing group
- CF structure media recovery
- Backing up the queue-sharing group at the prime site
- Recovering a queue-sharing group at the alternative site
- Reinitializing a queue manager
- Reinitializing a queue manager that is not in a queue-sharing group
- Reinitializing queue managers in a queue-sharing group
- Using the z/OS Automatic Restart Manager (ARM)
- What is the ARM?
- ARM couple data sets
- ARM policies
- Defining an ARM policy
- Activating an ARM policy
- Using ARM in a WebSphere MQ network
- Restarting on a different z/OS image with LU 6.2
- Restarting on a different z/OS image with TCP/IP
- Recovering units of work manually
- Displaying connections and threads
- Active units of work
- Unresolved units of work
- Recovering CICS units of recovery manually
- What happens when the CICS adapter restarts
- How to resolve CICS units of recovery manually
- Recovering IMS units of recovery manually
- What happens when the IMS adapter restarts
- How to resolve IMS units of recovery manually
- Recovering RRS units of recovery manually
- Recovering units of recovery on another queue manager in the queue-sharing group
- Example recovery scenarios
- Shared queue problems
- Queue is both private and shared
- Active log problems
- Dual logging is lost
- Active log stopped
- One or both copies of the active log data set are damaged
- Write I/O errors on an active log data set
- I/O errors occur while reading the active log
- Active log is becoming full
- Active log is full
- Archive log problems
- Allocation problems
- Off-load task terminated abnormally
- Insufficient DASD space to complete off-load processing
- Read I/O errors on the archive data set while WebSphere MQ is restarting
- BSDS problems
- Error occurs while opening the BSDS
- Log content does not agree with the BSDS information
- Both copies of the BSDS are damaged
- Unequal time stamps
- Out of synchronization
- I/O error
- Page set problems
- Page set I/O errors
- Page set full
- Coupling Facility and DB2 problems
- Storage medium full
- A DB2 system fails
- A DB2 data-sharing group fails
- DB2 and the Coupling Facility fail
- Problems with long-running units of work
- Old unit of work found during restart
- IMS-related problems
- IMS cannot connect to WebSphere MQ
- IMS application problem
- IMS is not operational
- Hardware problems
- Using the WebSphere MQ utilities
- WebSphere MQ utility program (CSQUTIL)
- Invoking the WebSphere MQ utility program
- PARM parameters
- Which PARM parameters do we need?
- Return codes
- Monitoring the progress of the WebSphere MQ utility program
- Formatting page sets (FORMAT)
- Keywords and parameters
- Example
- Usage notes
- Page set information (PAGEINFO)
- Keywords and parameters
- Example
- Usage notes
- Expanding a page set (COPYPAGE)
- Keywords and parameters
- Example
- Usage notes
- Copying a page set and resetting the log (RESETPAGE)
- Using the RESETPAGE function
- Keywords and parameters
- Example
- Usage notes
- Issuing commands to WebSphere MQ (COMMAND)
- Keywords and parameters
- Examples
- Issuing commands
- Making a list of DEFINE commands
- Making a list of ALTER commands
- Making a client channel definition file
- Usage notes
- Producing a list of WebSphere MQ define commands (SDEFS)
- Keywords and parameters
- Examples
- Usage notes
- Copying queues into a data set while the queue manager is running (COPY)
- Keywords and parameters
- Example
- Usage notes
- Syncpoints
- Copying queues into a data set while the queue manager is not running (SCOPY)
- Keywords and parameters
- Example
- Usage notes
- Emptying a queue of all messages (EMPTY)
- Keywords and parameters
- Example
- Usage notes
- Restoring messages from a data set to a queue (LOAD)
- Keywords and parameters
- Example
- Usage notes
- Migrating a channel initiator parameter module (XPARM)
- Keywords and parameters
- Example
- The change log inventory utility (CSQJU003)
- Invoking the CSQJU003 utility
- Data definition (DD) statements
- Multiple statement operation
- Adding information about a data set to the BSDS (NEWLOG)
- Keywords and parameters
- Delete information about a data set from the BSDS (DELETE)
- Keywords and parameters
- Supplying a password for archive log data sets (ARCHIVE)
- Keywords and parameters
- Controlling the next restart (CRESTART)
- Keywords and parameters
- Set checkpoint records (CHECKPT)
- Keywords and parameters
- Updating the highest written log RBA (HIGHRBA)
- Keywords and parameters
- The print log map utility (CSQJU004)
- Invoking the CSQJU004 utility
- Data definition statements
- The log print utility (CSQ1LOGP)
- Invoking the CSQ1LOGP utility
- Input control parameters
- Usage notes
- The EXTRACT function
- Processing EXTRACT data
- Example 1. Counting the number of bytes put to each queue
- Output
- Detail report
- Record layouts for the output data sets
- The queue-sharing group utility (CSQ5PQSG)
- Invoking the queue-sharing group utility
- Data definition statements
- Keywords and parameters
- Example
- The active log preformat utility (CSQJUFMT)
- Invoking the CSQJUFMT utility
- The dead-letter queue handler utility (CSQUDLQH)
- Invoking the DLQ handler
- Data definition statements
- Sample JCL
- The DLQ handler rules table
- Control data
- Rules (patterns and actions)
- The pattern-matching keywords
- The action keywords
- Rules table conventions
- Processing the rules table
- Ensuring that all DLQ messages are processed
- An example DLQ handler rules table
- Appendixes
- Appendix A. User messages on start-up
- Appendix B. Notices
- Programming interface information
- Trademarks
- Index