DFHLGxxxx messages

DFHLG0001
applid An abend (code aaa/bbbb) has occurred at offset X'offset' in module modname.
Explanation:

An abnormal end (abend) or program check has occurred in module modname. This implies that there may be an error in the CICS code. Alternatively, unexpected data has been input, or storage has been overwritten.

The code aaa/bbbb is a 3-digit hexadecimal MVS code (if applicable), followed by a 4-digit alphanumeric CICS code. The MVS code is a system completion code (for example, 0C1 or D37). If an MVS code is not applicable, this field is filled with three hyphens. The CICS code is an abend code or a number referring to a CICS message (for example, AKEA is a CICS abend code; 1310 refers to message DFHTS1310).

System action:

An exception entry is made in the trace table. A system dump is taken, unless you have specifically suppressed dumps in the dump table.

CICS continues unless you have specified in the dump table that CICS should terminate. If appropriate, an error return code is sent to the caller of this domain. In this case CICS could be terminated by the caller ( for example, the domain manager, DFHDMDM). A message is issued to this effect.

Message DFHME0116 is normally produced containing the symptom string for this problem.

User response:

Notify the system programmer. If CICS is still running, it is necessary to decide whether to terminate CICS.

Look up the MVS code, if there is one, in the relevant MVS codes manual.

Next, look up the CICS alphanumeric code. This tells you, for example, whether the error was a program check, an abend, or a runaway, and may give you some guidance concerning user response.

If module modname is not crucial to the running of your CICS system, you may decide to continue and bring CICS down at a convenient time to resolve the problem.

If you cannot continue without the full use of module modname you should bring CICS down in a controlled shutdown.

You need further assistance from IBM to resolve this problem. See CICS® Problem Determination Guide for guidance on how to proceed.

Destination:

Console

Modules:

DFHLGDM, DFHLGGL, DFHLGLD, DFHLGJN, DFHLGST DFHL2HS2, DFHL2HS3, DFHL2HS4, DFHL2HS5, DFHL2HS6, DFHL2HS7, DFHL2HS8, DFHL2HS9, DFHL2HSF, DFHL2HSG, DFHL2HSJ

XMEOUT Parameters: applid, aaa/bbbb, X'offset', modname

DFHLG0002
applid A severe error (code X'code') has occurred in module modname.
Explanation:

An error has been detected in module modname. The code X'code' is the exception trace point ID which uniquely identifies what the error is and where the error was detected.

System action:

An exception entry (code X'code' in the message) is made in the trace table. A system dump is taken, unless you have specifically suppressed dumps in the dump table.

CICS continues unless you have specified in the dump table that CICS should terminate. If appropriate, an error return code is sent to the caller of this domain. In this case, CICS could be terminated by the caller (for example, the domain manager, DFHDMDM). A message is issued to this effect.

Message DFHME0116 is normally produced containing the symptom string for this problem.

User response:

This indicates a possible error in CICS code. The severity of its impact depends on the importance of the function being executed at the time of the error.

CICS may not have been terminated. If the message occurs once and module modname is not crucial to the running of your CICS system, you may decide to continue and bring CICS down at a convenient time to resolve the problem.

If the message recurs or if you cannot continue without the full use of module modname, you should bring CICS down in a controlled shutdown.

You need further assistance from IBM to resolve this problem. See CICS Problem Determination Guide for guidance on how to proceed.

Destination:

Console

Modules:

DFHLGDM, DFHLGGL, DFHLGLD, DFHLGJN, DFHLGST

XMEOUT Parameters: applid, X'code',modname

DFHLG0004
applid A possible loop has been detected at offset X'offset' in module modname.
Explanation:

A CICS function is taking more time to process than CICS expects. A possible loop has been detected in module modname at offset X'offset'. This is the offset of the instruction which was executing at the time the error was detected.

System action:

An exception entry is made in the trace table. A system dump is taken, unless you have specifically suppressed dumps in the dump table.

CICS continues unless you have specified in the dump table that CICS should terminate. If appropriate, an error return code is sent to the caller of this domain. In this case CICS could be terminated by the caller (for example, the domain manager, DFHDMDM). A message is issued to this effect.

Message DFHME0116 is normally produced containing the symptom string for this problem.

User response:

Notify the system programmer. If CICS has not been terminated, it is necessary to decide whether the problem is serious enough to bring CICS down.

Since some CICS functions can use a lot of processor time, this message may have been caused by a long-running function. So there may not be an error here. Usually, CICS purges a CICS function which exceeds the runaway task time interval which you have specified in the SIT (this is the ICVR which is measured in milliseconds). This means that module modname in the message is terminated and CICS continues.

But if you have declared ICVR=0 in the SIT and you consider that module modname has gone into a loop, you have to terminate CICS in order to terminate the runaway function.

If CICS has terminated module modname, and you consider that it was not a runaway, you should increase the ICVR time interval in the SIT. You have to bring CICS down at a suitable time to do this permanently, but you can change the ICVR time interval temporarily online, using the CEMT transaction.

If raising the ICVR time does not solve the problem, you will need further assistance from IBM. See CICS Problem Determination Guide for guidance on how to proceed.

Destination:

Console

Modules:

DFHLGLB

XMEOUT Parameters: applid, X'offset', modname

DFHLG0101I
applid Log manager domain initialization has started.
Explanation:

This is an informational message indicating the start of log manager domain initialization.

System action:

Initialization continues.

User response:

None. You can suppress this message with the system initialization parameter, MSGLVL=0.

Destination:

Console

Modules:

DFHLGDM

XMEOUT Parameter: applid

DFHLG0102I
applid Log manager domain initialization has ended.
Explanation:

This is an informational message indicating the end of log manager domain initialization.

System action:

Initialization continues.

User response:

None. You can suppress this message with the system initialization parameter, MSGLVL=0.

Destination:

Console

Modules:

DFHLGDM

XMEOUT Parameter: applid

DFHLG0103I
applid System log (journalname) initialization has started.
Explanation:

This is an informational message indicating the start of system log initialization for the specified journal (either DFHLOG or DFHSHUNT).

System action:

Initialization continues.

User response:

None. You can suppress this message with the system initialization parameter, MSGLVL=0.

Destination:

Console

Modules:

DFHL2SLN

XMEOUT Parameters: applid, journalname

DFHLG0104I
applid System log (journalname) initialization has ended. Log stream logstreamname is connected to structure structurename.
Explanation:

This is an informational message indicating the end of system log initialization for the specified journal (either DFHLOG or DFHSHUNT).

Start of changeThe name shown as LOGSTREAMNAME(logstreamname) in the message is the name of the log stream associated with this journal. A value of '**************************' implies that it is a dummy log.End of change

Start of changeThe name shown as STRUCTNAME(structname) in the message is the structure name of the log stream associated with this journal. A value of '****************' implies that it has no related structure, which means that either the log stream is a dummy log or of type DASDONLY(YES).End of change

System action:

Initialization continues.

User response:

None. You can suppress this message with the system initialization parameter, MSGLVL=0.

Destination:

Console

Modules:

DFHL2SLN

XMEOUT Parameters: applid, journalname, logstreamname, structurename

DFHLG0191
subsys-name {CONVERTER | ALLOCATION} VERIFICATION HAS FAILED BECAUSE OF A {SEVERE ERROR | SYNTAX ERROR | MUTUAL EXCLUSION FAILURE}
Explanation:

A parse error was encountered while CICS was verifying the SUBSYS options of the application’s JCL DD statement.

The message includes the following inserts:

System action:

If the error was detected during MVS JCL conversion, the job is not executed because of the JCL error.

If the error was detected during MVS allocation processing, the allocation request is rejected.

User response:

Correct the SUBSYS= specification and resubmit the job.

Note:
This message cannot be changed with the message editing utility.
Destination:

Console and SYSPRINT

Modules:

DFHLGIPI, DFHLGIMS

DFHLG0192
ERROR IN MVS LOGGER MACRO macro_name FOR REQUEST request_type. MVS LOGGER CODES X'X'return-code'' X'X'reason-code''
Explanation:

The CICS subsystem exit made a call to the MVS logger to access a log. This message gives the return code and reason code for that operation. Usually this message is issued only when the return code indicates an error in the MVS logger macro.

The message includes the following inserts:

For further guidance, see the OS/390 MVS Programming: Assembler Services Reference.

System action:

The subsystem exit terminates the logstream read, and passes a return code back to the caller.

This message is followed by message DFHLG0193 which specifies the logstream. In some cases a dump is also produced.

User response:

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 CICS Problem Determination Guide for guidance on how to proceed.

Note:
This message cannot be changed with the message editing utility.
Destination:

Console

Modules:

DFHLGSSI, DFHLGIGT

DFHLG0193
log-stream-name
Explanation:

This message gives the logstream referred to in the preceding DFHLG0192 message.

System action:

See message DFHLG0192.

User response:

See message DFHLG0192.

Note:
This message cannot be changed with the message editing utility.
Destination:

Console

Modules:

DFHLGSSI, DFHLGIGT

DFHLG0194
ERROR DETECTED BY CICS SUBSYSTEM. error-description X'data1' X'data2' X'data3'
Explanation:

The CICS subsystem exit detected an unexpected error. The error is described by the error-description and optional hex data fields.

In some cases a dump is also produced.

System action:

The subsystem exit terminates the logstream read, and passes a return code back to the caller. If DELETE was specified as on option on the SUBSYS keyword then it will be ignored.

User response:

Use the error-description to identify the cause of the error. A possible cause is an invalid logstream or invalid entries within a valid logstream; the CICS logger and DFHJUP work only with CICS logstreams containing CICS records for the appropriate release.

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 CICS Problem Determination Guide for guidance on how to proceed.

Note:
This message cannot be changed with the message editing utility.
Destination:

Console

Modules:

DFHLGSSI, DFHLGIGT

Start of change
DFHLG0195
LOG GAP WARNING UP TO BLOCKID X'data1'
Explanation:

The CICS subsystem exit made a call to the MVS logger to access a log stream using the IXGBRWSE macro but this received a return code of IXGRSNCODEWARNING (X'04') with a reason code of IxgRsnCodeWarningGap (X'0403'). The blockid is the id of the next readable data in the log stream.

System action:

The CICS subsystem exit continues to access the log. This message is followed by message DFHLG0196.

User response:

For further guidance on the IxgRsnCodeWarningGap reason code see the z/OS Assembler Services Reference. Use the blockid and the timestamp reported in DFHLG0196 to investigate further if required. The warning may be the result of known activity that has deleted log data from the log.

Note:
This message cannot be changed with the message editing utility.
Destination:

Console

Module(s):

DFHLGIGT

End of change
Start of change
DFHLG0196
STCK OF BLOCK AFTER GAP (TIME FORMAT): X'data1'
Explanation:

This message is issued in association with message DFHLG0195. It provides the timestamp from the block id header corresponding to the block read after the reported gap.

System action:

See message DFHLG0195.

User response:

See message DFHLG0195.

Note:
This message cannot be changed with the message editing utility.
Destination:

Console

Module(s):

DFHLGIGT

End of change
DFHLG0301
date time applid An error has been detected for log stream stream for journal name journalname. The journal status has been set to FAILED.
Explanation:

An error has been detected for log stream stream which is used by journal journalname.

System action:

An exception entry is made in the trace table.

CICS marks the journal as failed and ends the associated connection with the log stream. Applications which attempt to use the journal receive an IOERROR response and may terminate abnormally.

User response:

Notify the system programmer. If CICS is still running, it is necessary to decide whether to terminate CICS.

See the associated messages issued by CICS or the MVS system logger for more information and for guidance about appropriate recovery actions.

If journal journalname is not crucial to the running of your CICS system, you may decide to continue.

If the problem with the log stream can be resolved, use of the journal can be restored by issuing SET JOURNALNAME(journalname) ACTION(RESET) via the CEMT or EXEC CICS interfaces.

If you cannot continue without the full use of journal journalname you should bring CICS down in a controlled shutdown.

Destination:

CSMT

Modules:

DFHLGJN

XMEOUT Parameters: date, time,applid, stream, journalname

DFHLG0302
date time applid Journal name journalname has been installed. Journal type: {MVS | SMF |DUMMY}stream.
Explanation:

Journal name journalname has been installed and is available for use. The type of journal, and for type MVS only, the log stream name stream are also shown.

System action:

An event entry is made in the trace table.

User response:

None

Destination:

CRDI

Modules:

DFHLGJN

XMEOUT Parameters: date, time,applid, journalname, {1=MVS ,2=SMF, 3=DUMMY}, stream

DFHLG0303
date time applid An error has been detected while connecting to log stream stream for journal name journalname. The journal status has been set to FAILED.
Explanation:

An error has been detected connecting to log stream stream which is used by journal journalname.

System action:

An exception entry is made in the trace table.

CICS marks the journal as failed. Applications which attempt to use the journal receive an IOERROR response and may terminate abnormally.

User response:

Notify the system programmer.

See the associated messages issued by CICS or the MVS system logger for more information and for guidance about appropriate recovery actions.

If CICS is still running, it is necessary to decide whether to terminate CICS.

If journal journalname is not crucial to the running of your CICS system, you may decide to continue.

If the problem with the log stream can be resolved, use of the journal can be restored by issuing the CEMT SET JOURNALNAME(journalname) RESET or the EXEC CICS SET JOURNALNAME(journalname) RESET command.

If you cannot continue without the full use of journal journalname you should bring CICS down in a controlled shutdown.

Destination:

CSMT

Modules:

DFHLGJN

XMEOUT Parameters: date, time,applid, stream, journalname

DFHLG0304
date time applid An error has been detected writing the catalog entry for journal name journalname.
Explanation:

An error has been detected writing the global catalog entry for journal journalname.

System action:

An exception entry is made in the trace table.

The new journal entry is used for this CICS run but does not persist over a CICS restart

User response:

Notify the system programmer.

See the associated CICS messages for more information, and for guidance about appropriate recovery actions.

If you cannot continue without the full use of journal journalname, you should bring CICS down in a controlled shutdown.

Destination:

CSMT

Modules:

DFHLGJN

XMEOUT Parameters: date, time,applid, journalname

DFHLG0305
date time applid An error has been detected deleting the catalog entry for journal name journalname.
Explanation:

An error has been detected deleting the global catalog entry for journal journalname.

System action:

An exception entry is made in the trace table.

The old journal entry could not be discarded and may reappear after a CICS restart

User response:

Notify the system programmer.

See the associated CICS messages for more information and for guidance about appropriate recovery actions.

If you cannot continue without the full use of journal journalname, you should bring CICS down in a controlled shutdown.

Destination:

CSMT

Modules:

DFHLGJN

XMEOUT Parameters: date, time,applid, journalname

DFHLG0306
date time applid Journal name journalname has been discarded.
Explanation:

Journal name journalname has been discarded and is no longer available for use.

Future attempts to use the journal name will cause it to be reinstalled using the journal model definitions active at that time.

System action:

An event entry is made in the trace table.

User response:

None.

Destination:

CRDI

Modules:

DFHLGJN

XMEOUT Parameters: date, time,applid, journalname

DFHLG0401
date time applid Journal model resource journalmodel has been installed.
Explanation:

The journal model resource entry journalmodel has been installed and is available for use.

System action:

An event entry is made in the trace table.

User response:

None.

Destination:

CRDI

Modules:

DFHLGLD

XMEOUT Parameters: date, time,applid, journalmodel

DFHLG0402
date time applid An error has been detected writing the catalog entry for journal model journalmodel.
Explanation:

An error has been detected writing the global catalog entry for journal model journalmodel.

System action:

An exception entry is made in the trace table.

The new journal model entry is used for this CICS run but does not persist over a CICS restart

User response:

Notify the system programmer.

See the associated CICS messages for more information and for guidance about appropriate recovery actions.

If you cannot continue without the full use of journal model journalmodel you should bring CICS down in a controlled shutdown.

Destination:

CSMT

Modules:

DFHLGLD

XMEOUT Parameters: date, time,applid, journalmodel

DFHLG0403
date time applid An error has been detected deleting the catalog entry for journal model journalmodel.
Explanation:

The deletion of the global catalog entry for journal model journalmodel has failed.

System action:

An exception entry is made in the trace table.

The old journal model entry could not be deleted and may reappear after a CICS restart

User response:

Notify the system programmer.

See the associated CICS messages for more information and for guidance about appropriate recovery actions.

If you cannot continue without the full use of journal model journalmodel you should bring CICS down in controlled shutdown.

Destination:

CSMT

Modules:

DFHLGJN

XMEOUT Parameters: date, time,applid, journalmodel

DFHLG0404
date time applid Journal model resource journalmodel1 has been replaced by journalmodel2.
Explanation:

A journal model resource entry has been replaced because journal model journalmodel2 has the same journal name template as journalmodel1.

System action:

An event entry is made in the trace table.

User response:

None.

Destination:

CRDI

Modules:

DFHLGLD

XMEOUT Parameters: date, time,applid, journalmodel1, journalmodel2

DFHLG0405
date time applid Journal model journalmodel has been discarded.
Explanation:

Journal model journalmodel has been discarded and is no longer available for use.

System action:

An event entry is made in the trace table.

User response:

None.

Destination:

CRDI

Modules:

DFHLGLD

XMEOUT Parameters: date, time,applid, journalmodel

DFHLG0501
date time applid Log stream definition for stream suppressed by XLGSTRM user exit.
Explanation:

MVS log stream stream does not exist but could not be defined because the XLGSTRM user exit suppressed automatic installation.

System action:

An exception entry is made in the trace table.

CICS cannot define or connect to the log stream. Applications attempting to use the stream receive an error response and may terminate abnormally.

User response:

Notify the system programmer. If CICS is still running, it is necessary to decide whether to terminate CICS.

Define the log stream directly to the MVS system logger.

If stream stream is not crucial to the running of your CICS system, you may decide to continue.

If the problem with the log stream can be resolved, use of an associated journal can be restored by issuing SET JOURNALNAME(journalname) ACTION(RESET) via the CEMT or EXEC CICS interfaces. If the log stream is a data set forward recovery log or autojournal, reopen the associated data sets.

If you cannot continue without the full use of log stream stream, you should bring CICS down in a controlled shutdown.

Destination:

Console and Transient Data Queue CRDI

Modules:

DFHLGST

XMEOUT Parameters: date, time,applid, stream

DFHLG0502
date time applid Log stream stream defined to MVS using model stream model.
Explanation:

MVS log stream stream did not exist and has been successfully defined to the MVS system logger using the attributes of model log stream model.

System action:

An event entry is made in the trace table.

CICS connects and uses the newly defined log stream.

User response:

None.

Destination:

CRDI

Modules:

DFHLGST

XMEOUT Parameters: date, time,applid, stream, model

DFHLG0503
date time applid Log stream stream, using model stream model, not defined to MVS for reason X'rc'/X'reason'.
Explanation:

MVS log stream stream does not exist and could not be defined to the MVS system logger using the attributes of model log stream model for reason X'rc'/X'reason'.

X'rc' is the return code from the IXGINVNT macro and X'reason' is the reason code returned by the IXGINVNT macro. These are described in the OS/390 MVS Programming: Assembler Services Reference and in the IXGCON macro.

System action:

An event entry is made in the trace table. The trace entry contains additional diagnostic information from the system logger answer area (IXGANSAA).

CICS cannot define or connect to the log stream so applications which attempt to use the stream receive an error response and may terminate abnormally.

Message DFHME0116 is normally produced containing the symptom string for this problem.

User response:

Notify the system programmer. If CICS is still running, it is necessary to decide whether to terminate CICS.

If stream stream is not crucial to the running of your CICS system, you may decide to continue.

You can define the log stream directly to the MVS system logger using the MVS log stream definition utility (IXCMIAPU).

If the problem with the log stream can be resolved, use of an associated journal can be restored by issuing SET JOURNALNAME(journalname) ACTION(RESET) via the CEMT or EXEC CICS interfaces. If the log stream is a data set forward recovery log or autojournal, the associated data sets should be reopened.

If you cannot continue without the full use of log stream stream you should bring CICS down in a controlled shutdown. You need further assistance from IBM to resolve this problem. See CICS Problem Determination Guide for guidance on how to proceed.

Destination:

Console and Transient Data Queue CSMT

Modules:

DFHLGST

XMEOUT Parameters: date, time,applid, stream, model, X'rc', X'reason'

DFHLG0504
date time applid Log stream stream using model stream model not defined to MVS due to insufficient authority.
Explanation:

MVS log stream stream does not exist and could not be defined to the MVS system logger using the attributes of model log stream model because of insufficient authority.

To define a log stream CICS requires the following authority:

System action:

An event entry is made in the trace table.

CICS cannot define or connect to the log stream so applications which attempt to use the stream receive an error response and may terminate abnormally.

User response:

Notify the system programmer. If CICS is still running, it is necessary to decide whether to terminate CICS.

If stream stream is not crucial to the running of your CICS system, you may decide to continue.

You can define the log stream directly to the MVS system logger using the MVS log stream definition utility (IXCMIAPU).

If the problem with the log stream can be resolved, use of an associated journal can be restored by issuing SET JOURNALNAME(journalname) ACTION(RESET) via the CEMT or EXEC CICS interfaces. If the log stream is a data set forward recovery log or autojournal, reopen the associated data sets.

If you cannot continue without the full use of log stream stream you should bring CICS down in a controlled shutdown.

Destination:

Console and Transient Data Queue CSMT

Modules:

DFHLGST

XMEOUT Parameters: date, time,applid, stream, model

DFHLG0505
date time applid Log stream stream using model stream model not defined to MVS because of an invalid HLQ parameter.
Explanation:

MVS log stream stream does not exist and could not be defined to the MVS system logger using the attributes of model log stream model because of an invalid high level qualifier (HLQ) parameter.

The HLQ parameter specifies the high level qualifier to be used for log stream data sets.

System action:

An event entry is made in the trace table.

CICS cannot define or connect to the log stream. Applications which attempt to use the stream receive an error response and may terminate abnormally.

User response:

Notify the system programmer. If CICS is still running, it is necessary to decide whether to terminate CICS.

If stream stream is not crucial to the running of your CICS system, you may decide to continue.

Correct the HLQ parameter in the model logger definition or the XLGSTRM exit, or both.

You can define the log stream directly to the MVS system logger using the MVS log stream definition utility (IXCMIAPU).

If the problem with the log stream can be resolved, use of an associated journal can be restored by issuing SET JOURNALNAME(journalname) ACTION(RESET) via the CEMT or EXEC CICS interfaces. If the log stream is a data set forward recovery log or autojournal, the associated data sets should be reopened.

If you cannot continue without the full use of log stream stream, you should bring CICS down in a controlled shutdown.

Destination:

Console and Transient Data Queue CSMT

Modules:

DFHLGST

XMEOUT Parameters: date, time,applid, stream, model

DFHLG0506
date time applid Log stream stream using model stream model not defined to MVS because of insufficient LOGR couple data set space.
Explanation:

MVS log stream stream does not exist and could not be defined to the MVS system logger using the attributes of model log stream model because of insufficient space in the MVS system logger’s LOGR couple data set.

System action:

An event entry is made in the trace table.

CICS cannot define or connect to the log stream. Applications which attempt to use the stream receive an error response and may terminate abnormally.

User response:

Notify the system programmer. If CICS is still running, it is necessary to decide whether to terminate CICS.

If stream stream is not crucial to the running of your CICS system, you may decide to continue.

Redefine the MVS system logger’s LOGR couple data set to contain space for this log stream and for future requirements.

You can define the log stream directly to the MVS system logger using the MVS log stream definition utility (IXCMIAPU).

If the problem with the log stream can be resolved, use of an associated journal can be restored by issuing SET JOURNALNAME(journalname) ACTION(RESET) via the CEMT or EXEC CICS interfaces. If the log stream is a data set forward recovery log or autojournal, the associated data sets should be reopened.

If you cannot continue without the full use of log stream stream, you should bring CICS down in a controlled shutdown.

Destination:

Console and Transient Data Queue CSMT

Modules:

DFHLGST

XMEOUT Parameters: date, time,applid, stream, model

DFHLG0507
date time applid Log stream stream using model stream model not defined to MVS. Maximum number of streams reached.
Explanation:

MVS log stream stream does not exist and could not be defined to the MVS system logger using the attributes of model log stream model because the maximum number of log streams for the coupling facility structure has been reached.

The maximum number of streams per structure is specified in the LOGSNUM parameter when defining a structure to the MVS system logger.

System action:

An event entry is made in the trace table.

CICS cannot define or connect to the log stream so applications which attempt to use the stream receive an error response and may terminate abnormally.

User response:

Notify the system programmer. If CICS is still running, it is necessary to decide whether to terminate CICS.

If stream stream is not crucial to the running of your CICS system, you may decide to continue.

Change the STRUCTNAME parameter in the model logger definition or the XLGSTRM exit to point to a structure that has room for more streams or delete unneeded streams from the current structure.

You can define the log stream directly to the MVS system logger using the MVS log stream definition utility (IXCMIAPU).

If the problem with the log stream can be resolved, you can restore the use of an associated journal by issuing SET JOURNALNAME(journalname) ACTION(RESET) via the CEMT or EXEC CICS interfaces. If the log stream is a data set forward recovery log or autojournal, reopen the associated data sets.

If you cannot continue without the full use of log stream stream, you should bring CICS down in a controlled shutdown.

Destination:

Console and Transient Data Queue CSMT

Modules:

DFHLGST

XMEOUT Parameters: date, time,applid, stream, model

DFHLG0508
date time applid Log stream stream not defined to MVS because model stream model does not exist.
Explanation:

MVS log stream stream could not be defined to the MVS system logger because the model log stream model does not exist.

System action:

An event entry is made in the trace table.

CICS cannot define or connect to the log stream. Applications which attempt to use the stream receive an error response and may terminate abnormally.

User response:

Notify the system programmer. If CICS is still running, it is necessary to decide whether to terminate CICS.

If stream stream is not crucial to the running of your CICS system, you may decide to continue.

You can define the log stream directly to the MVS system logger using the MVS log stream definition utility (IXCMIAPU). or you can define the model log stream to the MVS logger if there are likely to be more log streams to be defined using the same model.

If the problem with the log stream can be resolved, you can restore the use of an associated journal by issuing SET JOURNALNAME(journalname) ACTION(RESET) via the CEMT or EXEC CICS interfaces. If the log stream is a data set forward recovery log or autojournal, reopen the associated data sets.

If you cannot continue without the full use of log stream stream you should bring CICS down in a controlled shutdown.

Destination:

Console and Transient Data Queue CSMT

Modules:

DFHLGST

XMEOUT Parameters: date, time,applid, stream, model

DFHLG0509
date time applid Log stream stream using model stream model not defined to MVS because of an invalid structure name.
Explanation:

MVS log stream stream does not exist and could not be defined to the MVS system logger using the attributes of model log stream model because of an invalid coupling facility structure name.

System action:

An event entry is made in the trace table.

CICS cannot define or connect to the log stream so applications which attempt to use the stream receive an error response and may terminate abnormally.

User response:

Notify the system programmer. If CICS is still running, it is necessary to decide whether to terminate CICS.

If stream stream is not crucial to the running of your CICS system, you may decide to continue.

Correct the STRUCTNAME parameter in the model logger definition or the XLGSTRM exit, or both.

You can define the log stream directly to the MVS system logger using the MVS log stream definition utility (IXCMIAPU).

If the problem with the log stream can be resolved, you can restore the use of an associated journal by issuing SET JOURNALNAME(journalname) ACTION(RESET) via the CEMT or EXEC CICS interfaces. If the log stream is a data set forward recovery log or autojournal, reopen the associated data sets.

If you cannot continue without the full use of log stream stream you should bring CICS down in a controlled shutdown.

Destination:

Console and Transient Data Queue CSMT

Modules:

DFHLGST

XMEOUT Parameters: date, time,applid, stream, model

DFHLG0510
date time applid Log stream stream using model stream model not defined to MVS because of an invalid stream name.
Explanation:

MVS log stream stream does not exist and could not be defined to the MVS system logger using the attributes of model log stream model because stream is an invalid stream name.

System action:

An event entry is made in the trace table.

CICS cannot define or connect to the log stream so applications which attempt to use the stream receive an error response and may terminate abnormally.

User response:

Notify the system programmer. If CICS is still running, it is necessary to decide whether to terminate CICS.

If stream stream is not crucial to the running of your CICS system, you may decide to continue.

Correct the JOURNALMODEL definition used to create the stream name and DISCARD any JOURNAL definitions which refer to the stream name or, if the stream is a VSAM forward recovery log stream, correct the stream name in the VSAM data set‘s catalog entry.

If the problem with the log stream can be resolved, you can restore the use of an associated journal by issuing SET JOURNALNAME(journalname) ACTION(RESET) via the CEMT or EXEC CICS interfaces. If the log stream is a data set forward recovery log or autojournal, reopen the associated data sets.

If you cannot continue without the full use of log stream stream you should bring CICS down in a controlled shutdown.

Destination:

Console and Transient Data Queue CSMT

Modules:

DFHLGST

XMEOUT Parameters: date, time,applid, stream, model

DFHLG0511
date time applid Log stream stream using model stream model not defined to MVS because STRUCTNAME parameter missing in model.
Explanation:

MVS log stream stream does not exist and could not be defined to the MVS system logger using the attributes of model log stream model because the model log stream definition does not contain the required STRUCTNAME parameter.

System action:

An event entry is made in the trace table.

CICS cannot define or connect to the log stream. Applications which attempt to use the stream receive an error response and may terminate abnormally.

User response:

Notify the system programmer. If CICS is still running, it is necessary to decide whether to terminate CICS.

If stream stream is not crucial to the running of your CICS system, you may decide to continue.

Redefine the model log stream in the MVS system logger’s LOGR couple data set using the IXCMIAPU utility ensuring the model stream definition contains the STRUCTNAME(structure_name) parameter to indicate which coupling facility structure is to be used for the log stream. Alternatively you can use the CICS exit, XLGSTRM, to supply the structure name to the MVS system logger.

You can define the log stream directly to the MVS system logger using the MVS log stream definition utility (IXCMIAPU).

If the problem with the log stream can be resolved, use of an associated journal can be restored by issuing SET JOURNALNAME(journalname) ACTION(RESET) via the CEMT or EXEC CICS interfaces. If the log stream is a data set forward recovery log or autojournal, the associated data sets should be reopened.

If you cannot continue without the full use of log stream stream, you should bring CICS down in a controlled shutdown.

Destination:

Console and Transient Data Queue CSMT

Modules:

DFHLGST

XMEOUT Parameters: date, time,applid, stream, model

DFHLG0512
date time applid Log stream stream cannot be used as both a system log and a general log.
Explanation:

MVS log stream stream cannot be used as both a system log and as a general log.

It is likely that a JOURNALMODEL resource definition has resulted in the same log stream name for a user journal as for the system log journal names (DFHLOG and DFHSHUNT).

Alternatively a system log stream name may have been specified in the ICF catalog as the forward recovery log stream for a VSAM data set.

System action:

CICS cannot connect to the log stream. Applications which attempt to use the stream receive an error response and may terminate abnormally.

User response:

Notify the system programmer. If CICS is still running, it is necessary to decide whether to terminate CICS.

If stream stream is not crucial to the running of your CICS system, you may decide to continue.

Review and correct your installed Journalmodels to ensure that the the same log stream is not used for system logs (DFHLOG and DFHSHUNT) as for other journals. Use the CEMT DISCARD JOURNALNAME() command to remove any journals that have been installed with the incorrect stream name.

Note:
If you change the Journalmodel definitions which apply to DFHLOG and DFHSHUNT, you will need to perform an initial start.

If the ICF catalog specifies the wrong stream name, use the IDCAMS ALTER command to correct it.

Destination:

CSMT

Modules:

DFHLGST

XMEOUT Parameters: date, time,applid, stream

DFHLG0513
date time applid Log stream stream has failed and new connections cannot be accepted.
Explanation:

MVS log stream stream has been marked as failed by a previous error. The stream cannot be used again until all current users of the stream have disconnected and the problem that caused the failure has been resolved.

System action:

CICS cannot connect to the log stream. Applications which attempt to use the stream receive an error response and may terminate abnormally.

CICS continues with attempting to quiesce usage of the log stream and will disconnect from the log stream.

User response:

Notify the system programmer. If CICS is still running, it is necessary to decide whether to terminate CICS.

If stream stream is not crucial to the running of your CICS system, you may decide to continue.

CICS should automatically quiesce usage of the log stream but if CEMT INQUIRE STREAM(stream) shows continued use of the log stream, you should investigate whether there are any long running transactions that are preventing the closure of files which use the log stream as a forward recovery log or autojournal.

If the problem with the log stream can be resolved, use of an associated journal can be restored by issuing the command SET JOURNALNAME(journalname) ACTION(RESET) via the CEMT or EXEC CICS interfaces. If the log stream is a data set forward recovery log or autojournal, the associated data sets should be reopened.

If you cannot continue without the full use of log stream stream, you should bring CICS down in a controlled shutdown.

Destination:

CSMT

Modules:

DFHLGST

XMEOUT Parameters: date, time,applid, stream

DFHLG0514
date time applid Log stream stream is in use by another CICS system.
Explanation:

MVS log stream stream is in use by another CICS region.

General log streams can be shared between CICS regions but each CICS region must have unique system log streams.

One of the following may have occurred:

System action:

CICS cannot connect to the log stream. Applications which attempt to use the stream receive an error response and may terminate abnormally.

User response:

Notify the system programmer. If CICS is still running, it is necessary to decide whether to terminate CICS.

If stream stream is not crucial to the running of your CICS system, you may decide to continue.

Use the MVS console command DISPLAY GRS,RES=(DFHSTRM,stream) to find which other CICS region or regions are using the log stream,

Review and correct your installed Journalmodels to ensure that the the same log stream is not used for system logs (DFHLOG and DFHSHUNT as for other journals. Use the command CEMT DISCARD JOURNALNAME() to remove any journals that have been installed with the incorrect stream name.

Note:
If you change the Journalmodel definitions which apply to DFHLOG and DFHSHUNT, you will need to perform an initial start.

If the ICF catalog specifies the wrong stream name, use the IDCAMS ALTER command to correct it.

Destination:

Console and Transient Data Queue CSMT

Modules:

DFHLGST

XMEOUT Parameters: date, time,applid, stream

DFHLG0730
applid A severe error (code X'code') has occurred while opening the system log (journalname). CICS will be terminated.
Explanation:

The CICS log manager has detected a severe error while opening the primary or secondary system log. The nature of the error is indicated by a previous CICS message. The code code is the exception trace point ID which uniquely identifies the place where the error was detected.

System action:

An exception entry is made in the trace table. A system dump is taken and CICS is terminated immediately. CICS cannot tolerate a failure of this nature for the system log.

Message DFHME0116 is normally produced containing the symptom string for this problem.

User response:

Using the previous message as a guide, correct the problem and restart CICS, ensuring that the appropriate SIT START parameter is specified in order to maintain data integrity.

If the error condition persists, you will need assistance from IBM. See CICS Problem Determination Guide for guidance on how to proceed.

Destination:

Console

Modules:

DFHL2SLN

XMEOUT Parameters: applid, X'code',journalname

DFHLG0731
applid A failure has occurred while opening the system log (journalname). CICS will be terminated.
Explanation:

The CICS log manager has detected a failure while opening the primary or secondary system log. The nature of the failure is indicated by a previous CICS message.

System action:

An exception entry is made in the trace table, and CICS is terminated immediately. CICS cannot tolerate a failure of this nature for the system log.

User response:

Using the previous message as a guide, correct the problem and restart CICS, ensuring that the appropriate SIT START parameter is specified in order to maintain data integrity.

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 CICS Problem Determination Guide for guidance on how to proceed.

Destination:

Console

Modules:

DFHL2SLN

XMEOUT Parameters: applid, journalname

DFHLG0733
applid A log stream type of SMF has been requested for the system log (journalname). This is not allowed.
Explanation:

A log stream type of SMF has been specified on the JOURNALMODEL definition for either the primary or secondary system log. JOURNALMODEL definitions for the system log must have a log stream type of either MVS or DUMMY.

System action:

An exception entry is made in the trace table and CICS is terminated. CICS can not operate with an SMF system log.

User response:

Change the JOURNALMODEL definition so that a log stream type of either MVS or DUMMY is specified.

Destination:

Console

Modules:

DFHL2SLN

XMEOUT Parameters: applid, journalname

DFHLG0734
applid A severe error (code X'code') has occurred while accessing the CICS system log. CICS will be terminated.
Explanation:

The CICS log manager has detected a severe error while writing to or reading from the primary or secondary system log. The nature of the error is indicated by a previous CICS message. The code code is the exception trace point ID which uniquely identifies the place where the error was detected.

System action:

An exception entry is made in the trace table . A system dump is taken and CICS is terminated immediately. CICS cannot tolerate a failure of this nature for the system log.

Message DFHME0116 is normally produced containing the symptom string for this problem.

User response:

Using the previous message as a guide, correct the problem and restart CICS, specifying the SIT START parameter as AUTO.

If the error condition persists, you will need assistance from IBM. See CICS Problem Determination Guide for guidance on how to proceed.

Destination:

Console

Modules:

DFHL2SLE

XMEOUT Parameters: applid, X'code'

DFHLG0735
applid A failure has occurred while {writing to | reading from} the system log (journalname). Access to the system log has been lost. CICS will be terminated.
Explanation:

The CICS log manager has detected a failure while writing to or reading from the system log. The nature of the failure is indicated by a previous CICS message, and implies that data on the log has not been lost.

System action:

An exception entry is made in the trace table, and CICS is terminated immediately. CICS cannot tolerate a failure of this nature for the system log.

User response:

Using the previous message as a guide, correct the problem and restart CICS, ensuring that the appropriate SIT START parameter is specified in order to maintain data integrity.

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 CICS Problem Determination Guide for guidance on how to proceed.

Destination:

Console

Modules:

DFHL2SLE

XMEOUT Parameters: applid, {1=writing to, 2=reading from}, journalname

Start of changeDFHLG0736End of change
Start of changeapplid A failure has occurred while reading from the system log (journalname). The requested data could not be found. CICS will be quiesced allowing some tasks to complete. Further work requires an initial start.End of change
Start of change
Explanation:

The CICS log manager is unable to locate previously hardened data when reading from the system log during the dynamic backout of a task. This implies that data on the system log has been lost. The integrity of the system log is therefore suspect.

End of change
Start of change
System action:

No more blocks are written to the system log. CICS is quiesced via a normal shutdown to let as many tasks complete as possible. Any tasks that enter dynamic backout from this point onwards are suspended. If the next CICS start is not an initial start, CICS will terminate before allowing user processing to begin because system log data may have been lost.

End of change
User response:

Start of changeTransactions that failed to complete before shutdown will need to be recovered by other means before starting CICS again.End of change

Start of changeYou may need assistance from IBM. See CICS Problem Determination Guide for guidance on how to proceed.End of change

Destination:

Console

Modules:

DFHL2SLE

XMEOUT Parameters: applid, journalname

DFHLG0737
applid A failure has occurred while writing to the system log (journalname). A log record was longer than the maximum block size for the MVS log stream. CICS will be terminated.
Explanation:

The CICS log manager has detected a failure while writing to the system log. An attempt was made to write a log record longer than the maximum block size allowed for the MVS log stream. The size mismatch is indicated by a previous DFHLG0742 message written to the CSMT TD destination.

System action:

An exception entry is made in the trace table, and CICS is terminated immediately. CICS cannot tolerate a failure of this nature for the system log.

User response:

Using the DFHLG0742 message as a guide, define a larger block size for the MVS log stream structure that the system log will use. Then restart CICS, ensuring that the appropriate SIT START parameter is specified in order to maintain data integrity.

Destination:

Console

Modules:

DFHL2SLE

XMEOUT Parameters: applid, journalname

Start of changeDFHLG0738End of change
Start of changeapplid A failure has occurred while reading the system log (journalname). The requested data could not be found. CICS will be terminated. Further work requires an initial start.End of change
Start of change
Explanation:

The CICS log manager is unable to locate previously hardened data when reading from the system log during a restart of CICS. This implies that data on the system log has been lost. The integrity of the system log is therefore suspect.

End of change
Start of change
System action:

No blocks are written to the system log. CICS restart is abandoned. If the next CICS start is not an initial start, CICS will terminate before allowing user processing to begin because system log data may have been lost.

End of change
User response:

Start of changeIncomplete transactions will need to be recovered by other means before starting CICS again.End of change

Start of changeYou may need assistance from IBM. See CICS Problem Determination Guide for guidance on how to proceed.End of change

Destination:

Console

Modules:

DFHL2SLE

XMEOUT Parameters: applid, journalname

DFHLG0739
applid An attempt to start transaction CSQC to perform a normal shutdown of CICS has failed. Perform a normal shutdown of CICS manually.
Explanation:

The CICS log manager attempted to start transaction CSQC to quiesce CICS via a normal shutdown but the attempt was unsuccessful. CICS was being quiesced because the integrity of the system log is suspect.

System action:

An exception entry is made in the trace table, and a system dump is taken. CICS continues processing but any tasks that enter dynamic backout are suspended indefinitely and remain inflight.

User response:

Issue CEMT PERFORM SHUTDOWN to quiesce CICS via a normal shutdown. This lets as many transactions complete as possible. Refer to the explanations for messages DFHLG0736 and DFHLG0740.

Also attempt to establish why transaction CSQC failed to start, and correct the problem. If the error condition persists, you will need assistance from IBM. See CICS Problem Determination Guide for guidance on how to proceed.

Destination:

Console

Modules:

DFHL2SLE

XMEOUT Parameter: applid

DFHLG0740
applid While writing data to the system log (journalname), a lost data warning was received. CICS will be quiesced without logging, allowing tasks to complete. Further work requires an initial start.
Explanation:

The CICS log manager received a lost data warning when writing to the system log. This means that one or more blocks of previously hardened data have been lost from the system log. The integrity of the system log is therefore suspect.

System action:

Start of changeNo more blocks are written to the system log. CICS is quiesced via a normal shutdown to let as many tasks complete as possible. Any tasks that enter dynamic backout from this point onwards are suspended. If the next CICS start is not an initial start CICS will terminate before allowing user processing to begin because system log data may have been lost.End of change

Start of change
User response:

Transactions that failed to complete before shutdown will need to be recovered by other means before starting CICS again.

You may need assistance from IBM. See CICS Problem Determination Guide for guidance on how to proceed.

End of change
Destination:

Console

Modules:

DFHL2SLE

XMEOUT Parameters: applid, journalname

DFHLG0741
applid A failure to read data from the system log during dynamic backout has caused task tasknum to be suspended indefinitely. Tranid tranid, termid termid.
Explanation:

Task tasknum with tranid tranid running at termid termid has been suspended indefinitely. Data required during dynamic backout could not be located on the system log. This message is preceded by message DFHLG0736.

System action:

The task is suspended. CICS in the process of quiescing via a normal shutdown.

User response:

Refer to the message explanation for message DFHLG0736.

Destination:

Console

Modules:

DFHL2SLE

XMEOUT Parameters: applid, tasknum,tranid, termid

DFHLG0742
date time applid Log record too long for block. Record size rsize bytes. Block size bsize bytes. {MVS log stream | SMF journal name}.
Explanation:

The CICS log manager has detected an attempt to write a log record to an MVS logger log stream or SMF journal where the log record is too long to fit in the maximum block size allowed.

The message indicates the size of the log record and the maximum size of a block for that log stream. The size of the log record includes a CICS record header (up to 200 bytes for system log, 56 bytes otherwise) and any user prefix data. There must also be enough room in the block for a CICS block header (158 bytes for SMF, 52 bytes for system log, 40 bytes otherwise).

System action:

An exception entry is made in the trace table. If the log stream is part of the CICS system log and the log record was not written by a user application or exit program then CICS is terminated. Otherwise an exception is passed back to the caller.

User response:

First establish whether a log record of the indicated size is expected. If the log record was written by a user application or exit program using EXEC CICS WRITE JOURNALNAME or DFHJCJCX WRITE_JOURNAL_DATA, the program could be in error.

If the log record is correct, you should increase the block size for an MVS logger log stream by defining a larger block size for the structure that the log stream will use. For an SMF journal, the block size is fixed at 32756 bytes and cannot be changed.

Destination:

CSMT

Modules:

DFHL2LB, DFHL2WF, DFHL2CHM

XMEOUT Parameters: date, time,applid, rsize, bsize, {1=MVS log stream, 2=SMF journalname}

DFHLG0743
date time applid Tail of log stream lsn deleted at block id X'blockid'.
Explanation:

The CICS log manager has trimmed the tail of MVS logger log stream lsn. All records that occurred before (older) the specified MVS logger block id blockid have been deleted.

This occurs during activity keypoint processing when CICS decides it no longer needs records beyond a certain age on a CICS system log log stream.

System action:

CICS continues processing.

User response:

None.

Destination:

CSMT

Modules:

DFHL2CHE

XMEOUT Parameters: date, time,applid, lsn, X'blockid'

DFHLG0744
date time applid All records in log stream lsn have been deleted.
Explanation:

The CICS log manager has deleted all records from MVS logger log stream lsn.

Start of changeThis occurs either at CICS startup when the start type is initial, or during activity keypoint processing, when CICS decides it no longer needs any of the records currently on a CICS system log log stream.End of change

System action:

CICS continues processing.

User response:

None.

Destination:

CSMT

Modules:

DFHL2CC, DFHL2CHE

XMEOUT Parameters: date, time,applid, lsn

Start of changeDFHLG0745IEnd of change
Start of changeapplid System log full scan has started.End of change
Start of change
Explanation:

The CICS log manager has started the full scan of the system log during startup.

This is a progress message.

End of change
Start of change
System action:

CICS continues processing.

End of change
Start of change
User response:

None. The message can be suppressed with the SIT parameter MSGLVL=0.

End of change
Start of change
Destination:

Console

End of change
Modules:

Start of changeDFHL2CHAEnd of change

Start of changeXMEOUT Parameter:End of changeStart of change End of changeStart of changeapplidEnd of change

Start of changeDFHLG0746End of change
Start of changedate time applid System log scan trim record found. Primary logstream block id X'pblock', secondary logstream block id X'sblock'.End of change
Start of change
Explanation:

The CICS log manager has encountered a trim record during the scan of the system log stream during startup. The primary logstream trim record block id is pblock, the secondary logstream trim record block id is sblock.

This is an informational message.

End of change
Start of change
System action:

CICS continues processing.

End of change
Start of change
User response:

None.

End of change
Start of change
Destination:

CSMT

End of change
Modules:

Start of changeDFHL2CHNEnd of change

Start of changeXMEOUT Parameters:End of changeStart of change End of changeStart of changedate, End of changeStart of changetime,End of changeStart of changeapplid, End of changeStart of changeX'End of changeStart of changepblock', End of changeStart of changeX'End of changeStart of changesblockEnd of changeStart of change'End of change

Start of changeDFHLG0747IEnd of change
Start of changeapplid System log scan continuing, count records processed.End of change
Start of change
Explanation:

The CICS log manager has processed count records during the scan of the system logstream at a CICS restart.

The message is produced every 'n' records - where 'n' is half of AKPFREQ or 500, which ever is the greatest.

This is a progress message.

End of change
Start of change
System action:

CICS continues processing.

End of change
Start of change
User response:

None. The message can be suppressed with the SIT parameter MSGLVL=0.

End of change
Start of change
Destination:

Console

End of change
Modules:

Start of changeDFHL2CHN DFHL2CH4End of change

Start of changeXMEOUT Parameters:End of changeStart of change End of changeStart of changeapplid, End of changeStart of changecountEnd of change

Start of changeDFHLG0748IEnd of change
Start of changeapplid System log selective scan has started.End of change
Start of change
Explanation:

The CICS log manager has started the selective scan of the system log during startup.

This is a progress message.

End of change
Start of change
System action:

CICS continues processing.

End of change
Start of change
User response:

None. The message can be suppressed with the SIT parameter MSGLVL=0.

End of change
Start of change
Destination:

Console

End of change
Modules:

Start of changeDFHL2CHHEnd of change

Start of changeXMEOUT Parameter:End of changeStart of change End of changeStart of changeapplidEnd of change

Start of changeDFHLG0749IEnd of change
Start of changeapplid System log scan has completed.End of change
Start of change
Explanation:

The CICS log manager has finished the scan of the system log stream during startup.

This is a progress message.

End of change
Start of change
System action:

CICS continues processing.

End of change
Start of change
User response:

None. The message can be suppressed with the SIT parameter MSGLVL=0.

End of change
Start of change
Destination:

Console

End of change
Modules:

Start of changeDFHL2CHLEnd of change

Start of changeXMEOUT Parameter:End of changeStart of change End of changeStart of changeapplidEnd of change

DFHLG0750
applid Transaction CSQC has failed to perform a normal shutdown of CICS. Perform a normal shutdown of CICS manually.
Explanation:

Transaction CSQC has failed to quiesce CICS via a normal shutdown because an error was detected. CICS was being quiesced because the integrity of the system log is suspect.

System action:

A system dump is taken. CICS continues processing but any tasks that enter dynamic backout are suspended indefinitely and remain inflight.

User response:

Issue CEMT PERFORM SHUTDOWN to quiesce CICS via a normal shutdown. This lets as many transactions complete as possible. Refer to the explanations for messages DFHLG0736 and DFHLG0740.

Attempt to establish why transaction CSQC failed to quiesce CICS, and correct the problem. If the error condition persists, you will need assistance from IBM. See CICS Problem Determination Guide for guidance on how to proceed.

Destination:

Console

Modules:

DFHLGQC

XMEOUT Parameter: applid

DFHLG0760
date time applid Log stream lsn not trimmed by keypoint processing. Number of keypoints since last trim occurred: trimnum. History point held by transaction: transid, task number: trannum.
Explanation:

The CICS log manager has been unable to trim the tail of MVS logger log stream lsn, during an activity keypoint.

CICS will attempt to trim the system log log streams during activity keypoint processing, to delete redundant data from the oldest end of the log stream (the tail).

Note that this message is only issued if the primary system log stream (DFHLOG) fails to be trimmed during a keypoint operation. It is not issued if a trim does not occur for the secondary system log stream (DFHSHUNT). This is since a trim of the primary system log stream is considerably more likely to occur per keypoint, and hence failures to trim the primary system log stream should be recognized, and investigated if required.

System action:

CICS continues processing.

User response:

This is an informational message, but should be treated as a warning of a potential problem if the number of keypoints that have been unable to trim the primary system log stream continues to increase. Occasional keypoints that fail to trim DFHLOG are not unexpected events. However, if the message is issued by a number of sequential keypoints then this warrants further investigation.

The keypoint operation was unable to trim the tail of DFHLOG because the oldest log records on the log stream belong to a Unit Of Work (UOW) that is still required. This may be a validly long-running UOW; alternatively, it may be part of a long-running task executing an application that generates log records but does not issue syncpoint requests regularly enough.

This may be a transient phenomenon due to an atypical long-running UOW. Review the number of keypoints that have been unable to trim the log. Check what message CICS issues for log stream lsn at the next activity keypoint. Message DFHLG0743 indicates the log stream is now successfully trimmed. Another DFHLG0760 message indicates a long-running UOW still exists on the system. If the log stream still cannot be trimmed, use the CEMT INQUIRE UOW command to review the oldest UOWs on the system.

The transaction identifier and the task number of the task whose UOW relates to the oldest data on DFHLOG are also provided in the DFHLG0760 message. The CEMT INQUIRE TASK command may be used to review them.

It is also worthwhile reviewing how often CICS is performing activity keypoints (as defined by the AKPFREQ system definition parameter).

Destination:

CSMT

Modules:

DFHL2CHE

XMEOUT Parameters: date, time,applid, lsn, trimnum, transid, trannum

DFHLG0770
applid A severe error has occurred while writing to the SMF log, which was accessed via journal jname. SMF response X'resp'.
Explanation:

The CICS log manager has detected a severe error while writing to the SMF log. This is accessed via journal jname. SMF returns the response byte X'resp'.

System action:

An exception entry is made in the trace table, a system dump is taken and an exception is returned to the caller.

User response:

Using the SMF response byte, diagnose and correct 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 CICS Problem Determination Guide for guidance on how to proceed.

Destination:

Console

Modules:

DFHL2LB

XMEOUT Parameters: applid, jname,X'resp'

DFHLG0771
date time applid A temporary error condition occurred during MVS logger operation {IXGCONN | IXGWRITE | IXGBRWSE | IXGDELET | IXGQUERY }{CONNECT | DISCONNECT | | START | READCURSOR | READBLOCK | END | ALL | RANGE} for log stream lsn. MVS logger codes: X'ret', X'rsn'.
Explanation:

The CICS log manager made a call to the MVS logger to access a log, which returned a temporary error condition. The MVS logger operation that returned the error condition is identified in the message. The return and reason codes shown are those returned by the MVS logger.

For further guidance, see the OS/390 MVS Programming: Assembler Services Reference.

Start of change
System action:

The log manager automatically retries the operation while the temporary error condition persists. This message is issued every thirty seconds following the first/previous issue.

End of change
User response:

None. This is a temporary condition.

Destination:

CSMT

Modules:

DFHL2HS2, DFHL2HS3, DFHL2HS4, DFHL2HS5, DFHL2HS6, DFHL2HS7, DFHL2HS8, DFHL2HS9, DFHL2HSF, DFHL2HSG, DFHL2HSJ

XMEOUT Parameters: date, time,applid, {1=IXGCONN , 2=IXGWRITE, 3=IXGBRWSE , 4=IXGDELET , 5=IXGQUERY }, {1=CONNECT, 2=DISCONNECT, 3= ,4=START, 5=READCURSOR, 6=READBLOCK,7=END, 8=ALL, 9=RANGE}, lsn, X'ret', X'rsn'

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. Start of changeThis 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.End of change

Start of changeIf 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.End of change

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. Start of changeA restart of the MVS logger implicitly disconnects all connections to it.End of change

For further guidance, see the OS/390 MVS Programming: Assembler Services Reference.

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 is normally produced containing the symptom string for this problem.

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 CICS Problem Determination Guide for guidance on how to proceed.

Destination:

Console

Modules:

DFHL2HS2, DFHL2HS3, DFHL2HS4, DFHL2HS5, DFHL2HS6, DFHL2HS7, DFHL2HS8, DFHL2HS9, DFHL2HSF, DFHL2HSG, DFHL2HSJ, DFHL2HB

XMEOUT Parameters: applid, {1=IXGCONN , 2=IXGWRITE, 3=IXGBRWSE , 4=IXGDELET , 5=IXGQUERY }, {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', {1=YES,2=NO}, {1=YES, 2=NO}, structname, X'retpd', {1=YES,2=NO}

DFHLG0773
applid A severe error (code X'code') has occurred while accessing ({IXGCONN | IXGWRITE |IXGBRWSE | IXGDELET }{CONNECT | DISCONNECT | | START |READCURSOR | READBLOCK | END |ALL | RANGE}) the log stream lsn.
Explanation:

The CICS log manager has detected a severe error while attempting to access a log. The code X'code' is the exception trace point ID which uniquely identifies where the error was detected. This message is preceded by DFHLG0001, and usually followed by other messages.

System action:

An exception entry is made in the trace table. A system dump will have been taken by DFHLG0001. The log manager returns a disaster condition to the caller. If the log is the CICS system log, a forward recovery log or autojournal log, another message is issued. Otherwise a disaster condition is returned to the application program.

Message DFHME0116 is normally produced containing the symptom string for this problem.

User response:

Refer to other messages following this message for more information and guidance.

If the error condition persists, you will need assistance from IBM. See CICS Problem Determination Guide for guidance on how to proceed.

Destination:

Console

Modules:

DFHL2HS2, DFHL2HS3, DFHL2HS4, DFHL2HS5, DFHL2HS6, DFHL2HS7, DFHL2HS8, DFHL2HS9, DFHL2HSF, DFHL2HSG, DFHL2HSJ

XMEOUT Parameters: applid, X'code',{1=IXGCONN , 2=IXGWRITE, 3=IXGBRWSE , 4=IXGDELET }, {1=CONNECT, 2=DISCONNECT, 3= , 4=START, 5=READCURSOR, 6=READBLOCK, 7=END, 8=ALL, 9=RANGE}, lsn

DFHLG0774
applid The MVS logger has returned an alert during operation {IXGCONN CONNECT | IXGWRITE }for logstream lsn. The log stream data set directory is full. MVS logger codes: X'ret' X'rsn'.
Explanation:

The CICS log manager has detected a warning while attempting to access a log stream. The log stream's data set directory is full.

For further guidance, see the OS/390 MVS Programming: Assembler Services Reference.

System action:

An exception entry is made in the trace table.

CICS continues normal operation until the current data set of the log stream becomes full. When this happens message DFHLG0772 is issued.

User response:

You should delete data from the log stream tail before the current data set fills up. You may wish to take a copy of the data before deleting it. Alternatively you could use a new log stream, but this may be too disruptive.

Destination:

Console

Modules:

DFHL2HS2, DFHL2HSF

XMEOUT Parameters: applid, {1=IXGCONN CONNECT, 2=IXGWRITE }, lsn,X'ret', X'rsn'

DFHLG0775
applid The MVS logger has returned an alert during operation {IXGCONN CONNECT | IXGWRITE }for log stream lsn. The log stream writer offload task is failing. MVS logger codes: X'ret' X'rsn'.
Explanation:

The CICS log manager has detected a warning while attempting to access a log stream. The writer offload task for the log stream is failing.

For further guidance, see the OS/390 MVS Programming: Assembler Services Reference.

System action:

An exception entry is made in the trace table.

CICS can continue normal operation until the log stream's structure becomes full. When this happens DFHLG0772 is issued.

User response:

You should investigate and fix the failing log stream writer offload task, which is part of the MVS logger, before the log stream structure in the coupling facility fills up.

Destination:

Console

Modules:

DFHL2HS2, DFHL2HSF

XMEOUT Parameters: applid, {1=IXGCONN CONNECT, 2=IXGWRITE }, lsn,X'ret', X'rsn'

DFHLG0776
applid The MVS logger has returned an alert during operation IXGWRITE for log stream lsn. The log stream staging data set has failed. MVS logger codes: X'ret' X'rsn'.
Explanation:

The CICS log manager has detected an alert while attempting to access a log stream. The log stream staging data set has failed.

For further guidance, see the OS/390 MVS Programming: Assembler Services Reference.

System action:

An exception entry is made in the trace table.

CICS continues normal operation, but the data written to the log stream structure is not being duplexed. Consequently, if the structure (or coupling facility) fails, the data cannot be recovered.

User response:

You are recommended to shutdown CICS as soon as possible. You should investigate and fix the failing log stream, without losing the data.

If the failing log stream is the CICS system log and CICS was shutdown immediately, you should emergency restart CICS in order to recover the inflight transactions.

Destination:

Console

Modules:

DFHL2HSF

XMEOUT Parameters: applid, lsn,X'ret', X'rsn'

DFHLG0777
applid A temporary error condition occurred during MVS logger operation {IXGCONN | IXGWRITE |IXGBRWSE | IXGDELET | IXGQUERY }{CONNECT | DISCONNECT | | START | READCURSOR | READBLOCK | END | ALL | RANGE} for log stream lsn. MVS logger codes: X'ret', X'rsn'.
Explanation:

The CICS log manager made a call to the MVS logger to access a log, which returned a temporary error condition. The MVS logger operation that returned the error condition is identified in the message. The return and reason codes shown are those returned by the MVS logger.

For further guidance, see the OS/390 MVS Programming: Assembler Services Reference.

System action:

The log manager automatically retries the operation every three seconds while the temporary error condition persists. This message is issued every ten retries following the first/previous issue.

User response:

None. This is a temporary condition.

Destination:

Console

Modules:

DFHL2HS2, DFHL2HS3, DFHL2HS4, DFHL2HS5, DFHL2HS6, DFHL2HS7, DFHL2HS8, DFHL2HS9, DFHL2HSF, DFHL2HSG, DFHL2HSJ

XMEOUT Parameters: applid, {1=IXGCONN , 2=IXGWRITE, 3=IXGBRWSE , 4=IXGDELET , 5=IXGQUERY }, {1=CONNECT, 2=DISCONNECT, 3= , 4=START, 5=READCURSOR, 6=READBLOCK, 7=END, 8=ALL, 9=RANGE}, lsn, X'ret', X'rsn'

DFHLG0778
applid The MVS logger has returned an error during operation IXGCONN CONNECT for log stream lsn. CICS does not have authority to perform this operation. MVS logger codes: X'ret' X'rsn'.
Explanation:

The CICS log manager has detected an error while attempting to access a log stream. CICS region userid has not been defined to the MVS logger with the authority to perform this operation.

For further guidance, see the OS/390 MVS Programming: Assembler Services Reference.

System action:

An exception entry is made in the trace table.

The log manager returns an exception condition to the caller. If the log is the CICS system log, a forward recovery log or an autojournal log, another message is issued. Otherwise an exception condition is returned to the application program.

User response:

Refer to any messages issued subsequently for guidance. Use the MVS logger return and reason codes to further diagnose the problem.

Ensure that the CICS region userid has authority to access the log stream. For further guidance, see the CICS RACF® Security Guide.

Destination:

Console

Modules:

DFHL2HS2

XMEOUT Parameters: applid, lsn,X'ret', X'rsn'

DFHLG0779
applid The MVS logger has returned an error during operation IXGCONN CONNECT for log stream lsn. The log stream is being deleted by another program. MVS logger codes: X'ret' X'rsn'.
Explanation:

The CICS log manager has detected an error while attempting to access a log stream. The log stream is being deleted by a request from another program and CICS cannot connect to it until this program has finished.

For further guidance, see the OS/390 MVS Programming: Assembler Services Reference.

System action:

An exception entry is made in the trace table.

The log manager returns an exception condition to the caller. If the log stream is the CICS system log, a forward recovery log or an autojournal log, another message is issued. Otherwise an exception condition is returned to the application program.

User response:

Refer to any messages issued subsequently for guidance. Use the MVS logger return and reason codes to further diagnose the problem.

You will need to understand why another program was deleting the log stream. Either prevent such a conflict from occurring in the future, or allocate a different log stream to CICS.

Destination:

Console

Modules:

DFHL2HS2

XMEOUT Parameters: applid, lsn,X'ret', X'rsn'

Start of changeDFHLG0780End of change
Start of changeapplid The MVS logger has returned an error during operation IXGCONN CONNECT for log stream lsn. Some data previously written to this log stream has been lost. MVS logger codes: X'ret' X'rsn'.End of change
Start of change
Explanation:

The CICS log manager has detected an error while attempting to access a log stream. Some of the data written to this log stream has been permanently lost.

This message is issued only if the log stream is a general log (not a CICS system log).

For further guidance, see the OS/390 MVS Programming: Assembler Services Reference.

End of change
Start of change
System action:

An exception entry is made in the trace table.

The log manager returns an exception condition to the caller.

End of change
Start of change
User response:

This log stream is a general log, therefore it must be deleted and redefined before it can be used by CICS again.

If the log stream is used as a forward recovery log, take a fresh backup of all data sets that use this log stream as soon as possible.

If the log stream is used as a user journal, the associated journal needs to be reenabled before it can be used again. To do this, issue the command

SET JOURNALNAME(...) RESET

Use the MVS logger return and reason codes to further diagnose the problem.

End of change
Start of change
Destination:

Console

End of change
Modules:

Start of changeDFHL2HS2End of change

Start of changeXMEOUT Parameters:End of changeStart of change End of changeStart of changeapplid, End of changeStart of changelsn,End of changeStart of changeX'End of changeStart of changeret', End of changeStart of changeX'End of changeStart of changersnEnd of changeStart of change'End of change

DFHLG0781
applid The MVS logger has returned an error during operation IXGCONN CONNECT for log stream lsn. The maximum number of log stream connections that the MVS logger can support has been reached. MVS logger codes: X'ret' X'rsn'.
Explanation:

The CICS log manager has detected an error while attempting to access a log stream. The maximum number of log stream connections that the MVS logger can support has been reached.

For further guidance, see the OS/390 MVS Programming: Assembler Services Reference.

System action:

An exception entry is made in the trace table.

The log manager returns an exception condition to the caller. If the log is the CICS system log, a forward recovery log or an autojournal log, another message is issued. Otherwise an exception condition is returned to the application program.

User response:

Refer to any messages issued subsequently for guidance. Use the MVS logger return and reason codes to further diagnose the problem.

It may be possible to retry this transaction later when other work has completed and the number of concurrent transactions has reduced. Otherwise you should investigate your usage of log streams within the sysplex with a view to reducing the number of log streams that need to be connected concurrently.

Destination:

Console

Modules:

DFHL2HS2

XMEOUT Parameters: applid, lsn,X'ret', X'rsn'

DFHLG0782
applid The MVS logger has returned an error during operation {IXGCONN CONNECT | IXGWRITE} for log stream lsn. The MVS logger does not have authority to access the log stream structure. MVS logger codes: X'ret' X'rsn'.
Explanation:

The CICS log manager has detected an error while attempting to access a log stream. The MVS logger does not have the authority to access the log stream structure.

For further guidance, see the OS/390 MVS Programming: Assembler Services Reference.

System action:

An exception entry is made in the trace table.

The log manager returns an exception condition to the caller. If the log is the CICS system log, a forward recovery log or an autojournal log, another message is issued. Otherwise an exception condition is returned to the application program.

User response:

Refer to any messages issued subsequently for guidance. Use the MVS logger return and reason codes to further diagnose the problem.

Ensure that the MVS logger address space has authority to access the log stream structure.

Destination:

Console

Modules:

DFHL2HS2, DFHL2HSF

XMEOUT Parameters: applid, {1=IXGCONN CONNECT, 2=IXGWRITE}, lsn,X'ret', X'rsn'

DFHLG0783
applid The MVS logger has returned an error during operation IXGCONN CONNECT for logstream lsn. CICS attempted to connect to a log stream model, which is not possible. MVS logger codes: X'ret' X'rsn'.
Explanation:

The CICS log manager has detected an error while attempting to access a log stream. CICS attempted to connect to a log stream model, which is not possible.

For further guidance, see the OS/390 MVS Programming: Assembler Services Reference.

System action:

An exception entry is made in the trace table.

The log manager returns an exception condition to the caller. If the log is the CICS system log, a forward recovery log or an autojournal log, another message is issued. Otherwise an exception condition is returned to the application program.

User response:

Refer to any messages issued subsequently for guidance. Use the MVS logger return and reason codes to further diagnose the problem.

It is possible that a user journal definition has been defined with the wrong log stream name or that the log stream has been defined incorrectly to have the MODEL(YES) attribute. See the CICS System Definition Guide for guidance on defining user journals.

Destination:

Console

Modules:

DFHL2HS2

XMEOUT Parameters: applid, lsn,X'ret', X'rsn'

Start of changeDFHLG0784End of change
Start of changeapplid The MVS logger has returned an error during operation IXGCONN CONNECT for log stream lsn. You cannot connect to a DASDONLY log stream that is already connected to another MVS image. MVS logger codes: X'ret' X'rsn'.End of change
Start of change
Explanation:

The CICS log manager has detected an error while attempting to access a log stream. The MVS logger rejected the connect request because the log stream is of type DASDONLY and is already connected to another MVS image.

For further guidance, see the OS/390 MVS Programming: Assembler Services Reference.

End of change
Start of change
System action:

An exception entry is made in the trace table.

The log manager returns an exception condition to the caller. If the log is the CICS system log, a forward recovery log or an autojournal log, another message is issued. Otherwise an exception condition is returned to the application program.

End of change
Start of change
User response:

Refer to any messages issued subsequently for guidance. Use the MVS logger return and reason codes to further diagnose the problem.

Log streams of type DASDONLY were designed to work within the scope of a single MVS image only (although the MVS image itself can still be part of a sysplex).

The possibilities are;-

End of change
Start of change
Destination:

Console

End of change
Modules:

Start of changeDFHL2HS2End of change

Start of changeXMEOUT Parameters:End of changeStart of change End of changeStart of changeapplid, End of changeStart of changelsn,End of changeStart of changeX'End of changeStart of changeret', End of changeStart of changeX'End of changeStart of changersnEnd of changeStart of change'End of change

Start of changeDFHLG0785End of change
Start of changeapplid The MVS logger has returned an error during operation IXGCONN CONNECT for log stream lsn. This is a DASDONLY log stream, which is not supported by the current system release level. MVS logger codes: X'ret' X'rsn'.End of change
Start of change
Explanation:

The CICS log manager has detected an error while attempting to access a log stream. The MVS logger rejected the connect request because the log stream is of type DASDONLY and is not supported by the current system release level.

For further guidance, see the OS/390 MVS Programming: Assembler Services Reference.

End of change
Start of change
System action:

An exception entry is made in the trace table.

The log manager returns an exception condition to the caller. If the log is the CICS system log, a forward recovery log or an autojournal log, another message is issued. Otherwise an exception condition is returned to the application program.

End of change
Start of change
User response:

Refer to any messages issued subsequently for guidance. Use the MVS logger return and reason codes to further diagnose the problem.

Log streams of type DASDONLY are supported by system release level OS/390 2.4 or later.

The possibilities are;-

End of change
Start of change
Destination:

Console

End of change
Modules:

Start of changeDFHL2HS2End of change

Start of changeXMEOUT Parameters:End of changeStart of change End of changeStart of changeapplid, End of changeStart of changelsn,End of changeStart of changeX'End of changeStart of changeret', End of changeStart of changeX'End of changeStart of changersnEnd of changeStart of change'End of change

DFHLG0786
applid The MVS logger has returned an error during operation IXGCONN CONNECT for log stream lsn. The MVS logger failed to find a suitable coupling facility for the log stream structure. MVS logger codes: X'ret' X'rsn'.
Explanation:

The CICS log manager has detected an error while attempting to access a log stream. The MVS logger failed to find a suitable coupling facility for the log stream structure.

For further guidance, see the OS/390 MVS Programming: Assembler Services Reference.

System action:

An exception entry is made in the trace table.

The log manager returns an exception condition to the caller. If the log is the CICS system log, a forward recovery log or an autojournal log, another message is issued. Otherwise an exception condition is returned to the application program.

User response:

Refer to any messages issued subsequently for guidance. Use the MVS logger return and reason codes to further diagnose the problem.

You should investigate your usage of the coupling facility resource within the sysplex.

Destination:

Console

Modules:

DFHL2HS2

XMEOUT Parameters: applid, lsn,X'ret', X'rsn'

Start of changeDFHLG0787End of change
Start of changeapplid CICS is attempting to read a blockid that does not belong to the current chain. Read blockid: X'blkid1'; Chain History Point: X'blkid2'.End of change
Start of change
Explanation:

The requested blockid is a lower relative number than the Chain History Point blockid, which means the CICS log manager has requested a block which was written earlier than the current logical start of the chain. This indicates an internal logic error within CICS.

The blockid of the requested block, and the blockid representing the Chain History Point for the log block chain in question, are shown in the message.

End of change
Start of change
System action:

An exception entry is made in the trace table and a system dump is taken, and the CICS log manager returns an exception condition.

If the failure occurred while CICS was reading from the system log, message DFHLG0736 will follow, and a quiesce of CICS will be initiated.

End of change
Start of change
User response:

The logstream should be printed before CICS is restarted, using the DFHJUP utility. For guidance in using this, refer to the CICS Operations and Utilities Guide.

Note:
If the failure occurred for the CICS system log, print both the primary and secondary CICS system log logstreams before restarting CICS.

Refer to any messages issued subsequently for further guidance.

If the error condition persists, you will need assistance from IBM. See CICS Problem Determination Guide for guidance on how to proceed.

End of change
Start of change
Destination:

Console

End of change
Modules:

Start of changeDFHL2BLCEnd of change

Start of changeXMEOUT Parameters:End of changeStart of change End of changeStart of changeapplid, End of changeStart of changeX'blkid1', End of changeStart of changeX'End of changeStart of changeblkid2End of changeStart of change'End of change

Start of changeDFHLG0788End of change
Start of changeapplid The System Log journals DFHLOG and DFHSHUNT have been defined on the same MVS logstream (logstream). This is invalid. CICS will terminate.End of change
Start of change
Explanation:

When connecting to the DFHLOG and DFHSHUNT journals, the CICS Logger Domain has detected that both journals are defined on the same MVS logstream. This is invalid.

End of change
Start of change
System action:

An exception entry is made in the trace table. A system dump is taken and CICS is terminated immediately. CICS cannot tolerate a failure of this nature for the system log.

End of change
Start of change
User response:

Correct the JOURNALMODEL definitions used to define the DFHLOG and DFHSHUNT journals and restart the system.

End of change
Start of change
Destination:

Console

End of change
Modules:

Start of changeDFHL2SLEEnd of change

Start of changeXMEOUT Parameters:End of changeStart of change End of changeStart of changeapplid, End of changeStart of changelogstreamEnd of change

Start of change
DFHLG0789
DATE TIME APPLID DELETION OF LOGSTREAM "LSN" DATA WAS SUPPRESSED BY THE LOGGER RESOURCE MANAGER INTERFACE. MVS LOGGER CODES: X'RET' X'RSN' .
Explanation:

When the CICS log manager issued an IXGDELET request to delete data from the logstream, the logger resource manager interface suppressed the delete operation.

System action:

An exception entry is written in the trace table.

User response:

This may be expected behaviour. Check the status and settings of the logger resource manager interface, in relation to the meaning of the reason code from the IXGDELET request.

Destination:

CSMT

Modules:

DFHL2CHE, DFHL2CC

XMEOUT Parameters: date, time, applid, lsn, X'ret', X'rsn'

End of change
DFHLG0800
applid The MVS logger failed to locate a blockid requested by the CICS log manager. Missing blockid: X'blkid1'; Chain History Point: X'blkid2'.
Explanation:

The MVS logger has returned an IxgRsnCodeNoBlock (00000804) Reason Code to the CICS log manager. This means that the log block requested by CICS could not be located by the MVS logger.

The blockid of the requested block, and the blockid representing the Chain History Point for the log block chain in question, are shown.

System action:

This is an informational message to provide the blockid of the missing block, and the blockid of the Chain History Point for the chain which should contain the requested block.

This message will have been preceded by message DFHLG0772. An exception trace was written and a system dump taken.

If the failure occurred while CICS was reading from the system log message DFHLG0736 will follow, and a quiesce of CICS will be initiated.

User response:

Compare the requested blockid with the Chain History Point blockid. If the requested blockid is equal to, or a higher relative number than, the Chain History Point, the blockid represents a log block which CICS is still validly interested in and which should be available from the MVS logger.

If the requested blockid is a lower relative number than the Chain History Point blockid, then the CICS log manager has requested a block which was written earlier than the current logical start of the chain. This indicates an internal logic error within CICS.

The logstream should be printed before CICS is restarted, using the DFHJUP utility. For guidance in using this, refer to the CICS Operations and Utilities Guide. Note if the failure occurred for the CICS system log then print both the primary and secondary CICS system log logstreams before restarting CICS.

Refer to any messages issued subsequently for further guidance.

If the error condition persists, you will need assistance from IBM. See CICS Problem Determination Guide for guidance on how to proceed.

Destination:

Console

Modules:

DFHL2BLC

XMEOUT Parameters: applid, X'blkid1', X'blkid2'

[[ Contents Previous Page | Next Page Index ]]