DFHLG0772 applid An error has occurred during MVS logger operation {IXGCONN | IXGWRITE | IXGBRWSE | IXGDELET | IXGQUERY } {CONNECT | DISCONNECT | | START | READCURSOR | READBLOCK | END | ALL | RANGE | CHECKCONNSTATUS(YES)} for log stream lsn. MVS logger codes: X'ret', X'rsn'. Log stream attributes: SYSTEMLOG({YES | NO}), DASDONLY({YES | NO}), STRUCTNAME(structname), RETPD(X'retpd'), AUTODELETE({YES | NO}).
Explanation
The CICS log manager made a call to the MVS logger to access a log, which returned an error condition. The MVS logger operation that returned the error condition is identified in the message, and the return and reason codes shown are those returned by the MVS logger. This is followed by some of the attributes which define the log stream. A structure name of ****************" indicates that no structure is being used by this log stream.
If the error occurred during a log stream connection, these attributes may not have been updated to the correct values for the log stream and should be ignored. These attributes are only valid following a successful connection.
This message may be followed by other CICS messages, especially if the log stream is part of the CICS system log.
This situation can occur when CICS calls the MVS logger using an obsolete log stream connection token, when the MVS logger has been restarted following either a crash or a user request. A restart of the MVS logger implicitly disconnects all connections to it.
For further guidance, see the z/OS MVS Programming: Assembler Services Reference ABE-HSP.
Note: a reason code of x'0000085D' means an IxgRsnCodeWowError has been returned from the z/OS Logger. The coupling facility structure space allocated for this log stream is full or the staging data set space is full. Attempts to offload the interim storage data to DASD failed because of severe errors. No further write requests can be processed until the offload error condition is cleared.
System action
An exception entry is made in the trace table, and in some circumstances, a system dump is taken.
The log manager returns an exception condition.
Message DFHME0116, which contains the symptom string for this problem, is produced.
User response
If the MVS logger was recently restarted, AUTO start CICS. Otherwise use the MVS logger return and reason codes to diagnose the problem. If you cannot resolve the problem or the problem recurs, there may be a more severe error. In this case, you will need assistance from IBM. See IBM problem support for guidance on how to proceed.
Check the log for message IXG301I to determine the cause of the error. For general logstreams, you will most likely need to increase the size of the staging data set and then restart your CICS region or delete records from your general log streams.
Module
XMEOUT parameters/Message inserts
- applid
- Value chosen from the following options:
1=IXGCONN , 2=IXGWRITE, 3=IXGBRWSE , 4=IXGDELET , 5=IXGQUERY - Value chosen from the following options:
1=CONNECT, 2=DISCONNECT, 3= , 4=START, 5=READCURSOR, 6=READBLOCK, 7=END, 8=ALL, 9=RANGE, 10=CHECKCONNSTATUS(YES) - lsn
- X'ret'
- X'rsn'
- Value chosen from the following options:
1=YES, 2=NO - Value chosen from the following options:
1=YES, 2=NO - structname
- X'retpd'
- Value chosen from the following options:
1=YES, 2=NO
Destination
Console