Explanation
The logger event monitor determined
that an offload data set allocation, deletion, or HSM recall, or an
update to the LOGR couple data set for the offload activity results
have not been satisfied for the secondary monitoring interval. The
data set naming convention is included to aid in identifying other
potential messages that might be related to this offload activity.
The offload function involves reading log data from interim storage
and writing it to DASD log data sets. Writing data to DASD log data
sets involves DASD I/O and the potential need to allocate a new or
existing log data set, which might be on primary DASD or archived.
See Offload and Service Task Monitoring in z/OS MVS Setting Up a Sysplex for more information about system logger log stream offload monitoring activities.
- seconds
- is the number of seconds that the current offload has been delayed.
- logstream
- is the name of the log stream whose offload has been delayed.
- strname
- For a coupling facility log stream, the name of the structure
associated with the log stream.For a DASD-only based log stream, strname:
*NOT APPLICABLE*.
- request
- can be one of the following:
- ALLOCATING
- Allocating a new or existing log stream offload data set request.
- DELETING
- Deleting offload data sets that are no longer needed.
- RECALLING
- Recalling an existing log stream offload data set request.
- UPDATING
- Updating the LOGR CDS log stream record with offload control information.
- dsnhlq
- is the high level qualifier of the log stream data set name.
- dsnlsn
- is the log stream name qualifier portion of the log stream data set name.
- dsnllq
- is the low level qualifier of the log stream data
set name or <SEQ#>. If <SEQ#> is seen, this indicates that the
log stream is waiting for another log stream that is having a problem.
Check the log for an earlier IXG310I message for the name of the other
log stream.When UPDATING preceeds DSN=, the data set
name is replaced with LOGR CDS.
System action
System logger prompts the operator for action with message IXG312E, unless an AUTOFAIL response on a previous IXG312E condition in which case the system issues message IXG313I occurs.
Until this allocation completes, the system logger on this system may be unable to process many functions such as log stream connect requests, log stream disconnect requests and log stream deletion requests.
Operator response
- Check for outstanding WTOs or WTORs.
Check for any outstanding WTORs or WTOs that are awaiting action and 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 the offload DASD device or any device required to allocate/unallocate log data sets, such as the catalog device. If start pending conditions are found for any device, then 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 Logger. Resolve any recall requests for migrated log data sets.
If these steps do not resolve the condition, notify the system programmer.
System programmer response
See also message IXG312E documentation.
User response
None.
Programmer response
None.
Source
System logger (SCLOG)
Module
IXGL2MON, IXGXMSG
Routing code
2,10
Descriptor code
7,11