1C5

Explanation
An error occurred during System Logger processing.
The accompanying reason codes identify either an internal recoverable
Logger error or an external error code as follows: Code
Explanation
00000804
An IXGBRWSE or IXGDELET request failed because the block identifier
could not be found in the log stream.System Action: The
request is not honored and a return code 8, reason code 00000804 (or
corresponding missing data reason code) is returned to the caller.
System
Programmer Response:Ensure that the value in the request references
an existing portion of the log stream.
You can run the utility
IXCMIAPU with LIST LOGSTREAM (logstream-name) DETAIL(YES) to help
you determine if the requested blockid is in a valid range, and it
is not in a loss of data range.
 If the blockid is valid, search
problem reporting databases for a fix for the problem. If no fix exists,
contact the IBM® Support Center.
Provide the dump and LOGREC entries associated with this ABEND.

0000085F
Control percolated to the service requester's task due to an abend
during system logger processing. Retry was not possible. System
Programmer Response:  Request the service again.  If the problem
persists, search problem reporting databases for a fix for the problem.
If no fix exists, contact the IBM Support
Center.

00010001
Logger encountered an error that would have resulted in overwriting
log data on DASD. System Action: System Logger ends the
task.
 System Programmer Response: If the operation
in question fails, refer to message IXG269I for diagnostic procedures.
Search problem reporting databases for a fix for the problem. If no
fix exists, contact the IBM Support
Center
 and provide the diagnostic information.
00010008
Logger is unable to interpret the contents of an offload data
set. System Action: The request to read the data set fails.
Logger will issue message IXG063I to attempt to identify the log stream,
and it will request a dump. Logger may have also issued message IXG269I
to identify the data set in error. Browse (IXGBRWSE) requests to a
log stream that encounters this error might result in warning or error
gap conditions.
 System Programmer Response: Search problem
reporting databases for a fix for the problem. If no fix exists, contact
the IBM Support Center.

00010009
Logger is attempting to read from or write to an offload data
set, but a Media Manager access method error was encountered. System
Action: Logger will issue message IXG063I to attempt to identify
the log stream and it will request a dump.  For offload processing,
if Logger can recover from the error, it will close the current data
set, allocate a new one, and continue with the offload.  If Logger
cannot recover, it will issue message IXG301I and the offload will
fail.  Browse (IXGBRWSE) requests to the log streams that encounter
this error might result in warning or error gap conditions.
 System
Programmer Response:  If the operation in question fails, search
problem reporting databases for a fix for the problem. If no fix exists,
contact the IBM Support Center
and provide the diagnostic information.

00030006
An abend occurred after system logger called an application's
complete exit. Either the complete exit abended and percolated to
system logger recovery, or the address of the complete exit specified
on the COMPLETEEXIT parameter of the IXGCONN request for the log stream
was incorrect. System Action: System logger ends the task
that owned the connection to the log stream in order to end the connection.
 System
Programmer Response:Ensure that the complete exit address specified
on the IXGCONN request was correct and that the address does not change.
System logger requires that the caller's complete exit remain loaded
in storage at the address specified on IXGCONN until the application
receives control after successfully disconnecting from the log stream.
Then, if necessary, restart the application.
 If the problem
persists, search problem reporting databases for a fix for the problem.
If no fix exists, contact the IBM Support
Center.  Provide the dump and logrec entries associated with this
abend.

00030009
System logger was unable to complete an offload during log stream
recovery. The operator response to message IXG115A caused system logger
to abnormally terminate the structure connect task. System Action: System
logger ends the task that owned the connection to the log stream and
the structure for which the offload was processing.
 System
Programmer Response:Restart any applications that use the log
stream identified in message IXG114A.
 If the problem persists,
search problem reporting databases for a fix for the problem. If no
fix exists, contact the IBM Support
Center. Provide the dump and logrec entries associated with this abend.

00040003
System Logger has detected that the timestamp of the last block
written for the current logstream is well in the future.  It is likely
that this log stream was used in testing environment, and
an attempt has been made to reuse the log stream once testing
was complete and the clock has been set back to the present or
appropriate date/time. This type of Logger ABEND condition
has been known to occur during the following types of testing situations:during Y2K testing.
during reverse migration from a Mixed-CTN to an ETR-only network
on z/OS® images on the CPC for
which the ETR ports are enabled. A Coordinated Timing Network (CTN)
is a collection of servers and Coupling Facilities that are time synchronized
to a time value called Coordinated Server Time. A Mixed-Coordinated
Timing Network (Mixed-CTN) requires a Sysplex Timer, and allows for both
an External Time Reference (ETR) network and a Server Time Protocol
(STP). Depending on how long the stratum 2 server resides in STP-timing
mode, the TOD clock may drift enough for Logger to detect that a system
on an ETR-timing CPC might be less advanced than one on the STP-Timing
CPC. This might be encountered on any image on the STP-timing server
if they are actively writing log blocks to a CF structure based log
stream.
System Action: If the log stream had been newly
connected on a system after the clock (time) adjustment, then the
system has previously issued message IXG218A, warning of this condition.
 Once the issue is encountered, no IXGWRITE requests for
this log stream can be completed until the date/time becomes current
(as indicated in Message IXG218A).  Until the appropriate date
and time are reached, Logger will reject IXGWRITE requests with a
return code X'0C'.  A dump will be requested to provide diagnostic
information.
 System Programmer Response: The most likely
cause of this problem is that the clock value for the sysplex has
been adjusted backwards in time, and that this log stream was written
to while the clock was adjusted forward. If the time difference
from the clock adjustment or wait time indicated in message IXG218A
is unacceptable, it will be necessary to disconnect from the log stream,
delete it, redefine it, and reconnect.

Any other reason codes indicate that an internal
error has occurred.

System action
The system will have issued message IXG063I
in an attempt to identify the log stream (and CF structure) resources
Logger was operating on at the time of the ABEND. The system
writes a dump and records the error in logrec.
For the reason
codes listed above, use the system actions specifically listed.

System programmer response
Try disconnecting a log stream and
connecting again. If the problem persists, search problem reporting
databases for a fix for the problem. If no fix exists, contact the IBM Support Center.  Provide the
dump and logrec entries associated with this abend.
For the
reason codes listed above, use the system programmers response specifically
listed.

Source
System Logger