Dealing with the problem
Dealing with program abends
Batch abends
CICS transaction abends
IMS transaction abends
Dealing with waits and loops
Distinguishing between waits and loops
Waits
Loops
Symptoms of waits and loops
Dealing with waits
Is a batch or TSO program waiting?
Is a CICS transaction waiting?
Is DB2 waiting?
Is RRS active?
Is WebSphere MQ for z/OS waiting?
Dealing with loops
Is a batch application looping?
Is a batch job producing a large amount of output?
Does a CICS region show a lot of CPU activity?
Does an IMS region show a lot of CPU activity?
Is the queue manager showing a lot of CPU activity?
Is a queue, page set, or Coupling Facility structure filling up unexpectedly?
Are a task, and WebSphere MQ for z/OS, showing a lot of CPU activity?
Dealing with performance problems
z/OS system considerations
WebSphere MQ for z/OS considerations
Log buffer pools
Buffer pool size
Distribution of data sets on available DASD
Distribution of queues on page sets
Distribution of queues on Coupling Facility structures
Limitation of concurrent threads
Using the WebSphere MQ trace for administration
CICS constraints
Application design considerations
Effect of message length
Effect of message persistence
Searching for a particular message
Queues that contain messages of different lengths
Frequency of syncpoints
Advantages of the MQPUT1 call
Dealing with incorrect output
Messages do not appear when expected
Problems with missing messages when using distributed queuing
Problems with getting messages when using message grouping
Finding messages sent to a cluster queue
Finding messages sent to the WebSphere MQ-IMS bridge
Messages contain unexpected or corrupted information
Notices
|
Downloads
|
Library
|
Support
|
Feedback
csq4p02