Explanation
The logger event monitor determines that a system logger service task is not responding while attempting an allocation, deletion, HSM recall, or HSM deletion for a log stream data set. Delays in system logger service tasks can impact not only the specific log stream, but also other log streams on the system or in the sysplex.
- group
- is the name of the group that the service task belongs to (either PRODUCTION or TEST)
- taskname
- is the name of the system logger service task that is not responding.
The task is either ALLOCATION, CONNECTION,
LOGSTREAM
MISC
or MIGRATED DATASET - seconds
- is the number of seconds that the task has not responded.
- logstream
- is the log stream name.
- staging
- is the word STAGING or null.
- dsname
- is the log stream data set name.
- diag
- is the internal Diagnostic Data where the hexadecimal ranges below
followed by the decimal values indicate the type of activity that
system logger is waiting on to complete:
- X'01'-X'0A' (1-10) Dynamic Allocation/Unallocation
- X'0B'-X'14' (11-20) Serialization/Latching
- X'15'-X'1E' (21-30) Catalog Accesses
- X'1F'-X'32' (31-50) Media Manager OPEN/CONNECT
- X'33'-X'46' (51-70) Media Manager CLOSE/DISCONNECT
- X'47'-X'50' (71-80) Media Manager I/O Accesses
- X'51'-X'5A' (81-90) Migrated Data Set Recall
- X'5B'-X'64' (91-100) Migrated Data Set Delete
System action
System logger will prompt the operator for action with message IXG272E. If the operator makes no response, the data set request might still finish normally. If this occurs, system logger will issue a DOM for both IXG271I and IXG272E messages and continues processing. Until the data set request completes, system logger on this system might not be able to process many functions such as log stream connect, disconnect, deletion requests, offloads, or browses.
When the taskname is MIGRATED DATASET, the resource information for the log stream and data set identifies the oldest recall request outstanding for that group. Note that the PRODUCTION group can have up to 24 recall requests waiting for DFSMShsm to respond, and the TEST group can have up to 8 recalls. If any of the waiting recalls complete, system logger will issue a DOM for both IXG271I and IXG272E messages and continue processing. Message IXG281I may also be issued indicating system logger has data set recall requests pending.
Operator response
- Check for outstanding WTOs or WTORs.
Check for any outstanding WTORs or WTOs that are awaiting action that might be preventing system logger from being able to allocate a log data set.
- Check for start pendings.
Check for any start pending conditions against either the DASD device or any devices required to allocate or unallocate log data sets, such as the catalog device and any device for which a new log data set could be allocated. If start pending conditions are found for any of these devices, resolve the condition.
- Check for resource contention.
Issue the DISPLAY GRS,C command to display resource contention. If there is resource contention that is preventing system logger from allocating log data sets, then resolve the contention.
- Check for recall of migrated log data sets.
Issue the DISPLAY LOGGER,STATUS,RECALLS command to display all the outstanding data set recalls requested by system logger, and consider using the SETLOGR FORCE,NORECALL command to cause system logger to stop waiting for a particular data set to be recalled.
Resolve any recall requests for migrated log data sets.
If none of the above steps resolves the problem, notify the system programmer.
System programmer response
See also message IXG272E documentation.
User response
None.
Programmer response
None.
Source
System logger (SCLOG)
Module
IXGL2MON
Routing code
2,10
Descriptor code
7,11