7.2 Offload monitoring

< Day Day Up >

As part of z/OS 1.4 (or via APAR OW51854 on earlier releases), System Logger introduced function that allows installations to monitor offloads. If an offload appears to be taking too long or if it hangs, System Logger will issue message IXG312E. There are several actions you can take to attempt to determine what may be inhibiting an offload:

First of all, verify that there are no outstanding WTORs.
Determine if there are inhibitors to offload processing by issuing such commands as:
- D LOGGER,C,LSN=logstreamname
- D LOGGER,L,LSN=logstreamname
- D XCF,STRUCTURE,STRNAME=stucturename
- D GRS,C
Attempt to remedy any problems noted.
If the problem persists, respond or react to any Allocation, Catalog, or recall messages such as IEF861I, IEF863I, or IEF458D.
If the problem persists, respond to message IXG312E. This can be used to stop the offload processing for the log stream named in the message and allow it to run on another system, if possible. It may also allow other work to run on the system that was attempting the original offload.
If message IXG115A is displayed, reply to this message only after you have attempted to remedy any delayed offloads by responding to the related IXG312E messages. As a last resort, if you reply "TASK=END" to an IXG115A message, System Logger will terminate all the log stream connections in the structure named in the message on this system.

Review the complete description of messages IXG311I, IXG312E, IXG114I, and IXG115I in the z/OS MVS System Messages Volume 10 (IXC - IZP), SA22-7640-03 before responding to any of these messages.

Note that several messages could appear at the same time for different log stream for which offloading is taking place. It may be that only one log stream is actually having a problem, and the others are simply waiting for this log stream to finish its allocation processing. Usually, the log stream that is causing the delay is the first log stream to be reported on.

Another way to determine which log stream is actually causing the delay is to check in the message IXG312E to see if the data set name ends with an explicit sequence number, such as "A0000001". If this is the case, it usually means that this log stream is experiencing a problem. If the data set name ends with ".<SEQ#>", then it is more likely that this log stream is waiting for another log stream that is having a problem.

< Day Day Up >