Explanation
The system logger Event Monitor is requesting that an action be specified for a task that is not responding in the system logger address space.
- MONITOR—Continue monitoring this delayed request.
- IGNORE—Stop monitoring this delayed request.
- FAIL—Fail the current request this task is processing.
- EXIT—Terminate system logger Service Task Monitoring.
See the system programmer Response for a more complete description of these actions.
- group
- is the name of the group to which the service task belongs (either PRODUCTION or TEST)
- taskname
- is the name of system logger service task that is not responding.
The task is either ALLOCATION, CONNECTION,
LOGSTREAM
MISC
or MIGRATED DATASET.
System action
Message IXG271I accompanies this message. System logger waits for the operator to specify an action, or for the request to complete resulting in message IXG272E being DOMed.
Operator response
Contact the system programmer. Then respond to the message.
System programmer response
Message IXG271I accompanies this message. Review IXG271I and its description before proceeding with a response.
This message can also be accompanied by messages IXG311I and IXG312E, which also indicates a possible delay related to a log stream data set request. Review these message descriptions as well. See "Offload and Service Task Monitoring" in z/OS MVS Setting Up a Sysplex for more information about the relationship and considerations for these action messages.
- MONITOR
- The system logger Event Monitor continues to Monitor the request
and takes no overt action. If the specific request has not made progress
after another interval, the system will issue another WTOR at that
time.
When you reply MONITOR, any subsequent IXG271I messages issued will show a delay duration. You can use the delay duration to determine if a new delay is being seen, or if the delay is ongoing, that is, the delay value is increasing.
- IGNORE
- The system logger Event Monitor stops Monitoring this request. It might be that there is no problem with this request, it is simply taking a long time, and this is acceptable to the installation, (e.g. HSM Recalls for data sets).
- FAIL
- The request will be interrupted on this system. This will most
likely cause the request to behave as if it failed (e.g. a data set
could not be allocated).
This can also allow other work to continue that was waiting for this system logger service task. Use this option only if you cannot determine why the request is not completed.
Replying FAIL might cause undesirable results, and is meant to keep the rest of the system logger applications running, at the expense of one hung application.
Take note of any other system logger error messages or messages from any exploiter of the affected log stream.
If you reply FAIL, system logger might cause other components such as Allocation to enter their Recovery, take dumps, or issue various messages.
- EXIT
- The system logger event monitor terminates ALL service task monitoring activity on this system. There will be no messages indicating system logger task processing being delayed, and there will be no mechanism available to quiesce (fail) any delayed system logger tasks. In this case, the system also issues Message IXG275I.This response will not affect offload monitoring. If system logger is ever stopped and restarted, the Task Monitor will be restarted as well.
If it appears there is a persistent problem inhibiting normal system logger operations, get a dump of system logger to obtain diagnostic information, and contact the IBM® support center. See Operator Command in IEADMCxx Parmlib Member and Getting a Dump of System Logger Information of z/OS MVS Diagnosis: Tools and Service Aids for more information about obtaining system logger dumps.
User response
None.
Programmer response
None.
Source
System logger (SCLOG)
Module
IXGL2MON
Routing code
2,10
Descriptor code
3