DFHAPxxxx messages

DFHAP0001
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 CICS code.

Alternatively:

The code aaa is, if applicable, a 3-digit hexadecimal MVS system completion code (for example, 0C1 or D37). If an MVS code is not applicable, this field is filled with three hyphens. The 4-digit code bbbb, which follows aaa, is a user abend code produced either by CICS or by another product on the user’s system.

If X'offset' contains the value X'FFFF', then module modname was in control at the time of the abend, but the program status word (PSW) was not addressing this module.

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.

Either this is a critical error and CICS is terminated, even if you have specified in the dump table that CICS should not terminate.

Or CICS will continue unless you have specified in the dump table that CICS should terminate. Message DFHME0116 is normally produced containing the symptom string for this problem.

User response:

Notify the system programmer.

Look up the MVS code aaa, if there is one, in the relevant MVS codes manual which is detailed in the book list in the front of this manual.

If the modname insert contains the value ????, then CICS was unable to determine which module has abnormally terminated. In this case, examine the system dump to determine which area of code has caused the program check.

The user should examine other messages to determine what the module which issued this message was doing at the time the abend occurred. From these messages they can deduce which product has produced the abend code bbbb. If bbbb is identified as a CICS code, it may be either alphameric or numeric.

If the user abend code is from another product (for example, IMS), refer to the appropriate messages and codes manual to determine the cause of the abend.

The entries in the appropriate manuals will give the user guidance regarding the nature of the error, and may also give some guidance concerning the appropriate user response.

Note:
The program check may have occurred in a user program. If this is the case, the program check is usually followed by an ASRA or an ASRB transaction abend and a transaction dump.

If you want to suppress system dumps that precede ASRA and ASRB abends, you must specify this on an entry in the dump table, using either CEMT or an EXEC CICS command. Further guidance on suppressing system dumps can be found in the CICS® System Definition Guide.

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

Destination:

Console

Modules:

Start of changeDFHABAB, DFHAFMT, DFHAPDM, DFHAPDN, DFHAPEX, DFHAPIQ, DFHAPJC, DFHAPNT, DFHAPSM, DFHAPST, DFHAPSI, DFHAPXM, DFHAPXME, DFHDKMR, DFHEDFE, DFHEISR, DFHICXM, DFHMRXM, DFHSAIQ, DFHSIPLT, DFHSRP, DFHSTDT, DFHSTFC, DFHSTLK, DFHSTLS, DFHSTSZ, DFHSTTD, DFHSTTM, DFHSTTR, DFHSTTS, DFHSUEX, DFHTDXM, DFHTMP, DFHTSUT, DFH62XMEnd of change

Start of changeXMEOUT Parameters: applid, aaa/bbbb, X'offset', modnameEnd of change

DFHAP0002
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 is made in the trace table (X'code' in the message). A system dump is taken, unless you have specifically suppressed dumps in the dump table.

If this message is issued from DFHAPEX or DFHSUEX, and the exit point is XDUREQ, then a system dump is not taken in order to prevent recursive dumping.

Either this is a critical error and CICS is terminated, even if you have specified in the dump table that CICS should not terminate.

Or CICS will continue unless you have specified in the dump table that CICS should terminate. Message DFHME0116 is normally produced containing the symptom string for this problem.

User response:

Notify the system administrator. This failure indicates a serious error in CICS. If you have not requested termination in the dump table, you may want to terminate CICS. For further information about CICS exception trace entries, see the CICS Problem Determination Guide.

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

Destination:

Console

Modules:

DFHABAB, DFHAFMT, DFHAPDM, DFHAPDN, DFHAPEX, DFHAPJC, DFHAPLI, DFHAPLJ, DFHAPSI, DFHAPSIP, DFHAPSM, DFHAPST, DFHAPTI, DFHAPTIM, DFHAPTIX, DFHAPXM, DFHAPXME, DFHDKMR, DFHERM, DFHEISR, DFHICXM, DFHPCPG, DFHSIPLT, Start of changeDFHSTDT, DFHSTFC, DFHSTJC, DFHSTLK DFHSTLS, DFHSTSZ, DFHSTTD, DFHSTTM, DFHSTTR, DFHSTTS, DFHSUEX, DFHSUZX, DFHTMP, DFHTDXM, DFHVEH, DFHXCPA, DFHXSWM, DFHZCUTEnd of change

Start of changeXMEOUT Parameters: applid, X'code',modnameEnd of change

DFHAP0003
applid Insufficient storage (code X'code') in module modname.
Explanation:

A CICS GETMAIN was issued by module modname, but there was insufficient storage available to satisfy the request.

The code X'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 (code X'code' in the message). A system dump is taken, unless you have specifically suppressed dumps in the dump table. CICS will continue 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 will be issued to this effect. Message DFHME0116 is normally produced containing the symptom string for this problem.

User response:

Inform the system programmer.

Try increasing the size of the DSA or EDSA. See the CICS System Definition Guide or the CICS Customization Guide for further information on controlling CICS storage.

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

Destination:

Console

Modules:

DFHAPDM, DFHAPSIP

XMEOUT Parameters: applid, X'code',modname

DFHAP0004
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.

If this message is issued from DFHAPEX or DFHSUEX, and the exit point is XDUREQ, then a system dump is not taken in order to prevent recursive dumping.

Either this is a critical error and CICS is terminated, even if you have specified in the dump table that CICS should not terminate.

Or CICS will continue unless you have specified in the dump table that CICS should terminate. 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 will be 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 will purge 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 the module modname will be terminated and CICS will continue.

But if you have declared ICVR=0 in the SIT and you consider that module modname has gone into a loop, you will 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 will 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 need further assistance from IBM to resolve this problem. See CICS Problem Determination Guide for guidance on how to proceed.

Destination:

Console

Modules:

DFHAFMT, DFHAPDM, DFHAPDN, DFHAPEX, DFHAPIQ, DFHAPJC, DFHAPSM, DFHAPST, DFHAPSI, DFHAPXM, DFHAPXME, DFHDKMR, DFHEDFE, DFHEISR, Start of changeDFHICXM, DFHSAIQ, DFHSIPLT, DFHSTDT, DFHSTFC, DFHSTJC, DFHSTLK, DFHSTLS, DFHSTSZ, DFHSTTD, DFHSTTM, DFHSTTR, DFHSTTS, DFHSUEX, DFHTDXM, DFHTSUTEnd of change

Start of changeXMEOUT Parameters: applid, X'offset', modnameEnd of change

DFHAP0005
applid A hardware error has occurred (module modname, code X'code'). MVS Store Clock found inoperative.
Explanation:

A hardware error has occurred during the running of module module. The MVS store clock facility is the timing mechanism for the operating system.

The code X'code' is the exception trace point ID which uniquely identifies the place where the error was detected.

System action:

An exception entry (code 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.

This is a critical error and CICS is terminated, even if you have specified in the dump table that CICS should not terminate.

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

User response:

Investigate the MVS store clock to determine whether it is working properly. If this is the cause, you should take the appropriate action to have it repaired or replaced.

In the unlikely event that this is not a hardware problem, you need further assistance from IBM. See CICS Problem Determination Guide for guidance on how to proceed.

Destination:

Console

Modules:

DFHZCUT

XMEOUT Parameters: applid, modname,X'code'

DFHAP0100
applid Suffixed module modname cannot be loaded. Enter new suffix, 'YES'(unsuffixed), 'NONE'(dummy), or 'CANCEL'
Explanation:

During AP domain initialization, a suffixed CICS module or table could not be loaded.

System action:

The AP domain initialization routines wait for the operator to:

User response:

Determine whether the suffix is correct. If it is not, enter one of the replies listed in the System Action.

If you enter ‘CANCEL’, correct the error by adding the module to the appropriate library and then restart CICS.

Destination:

Console

Modules:

DFHSIB1

XMEOUT Parameters: applid, modname

DFHAP0101
applid Suffixed module modname cannot be loaded.
Explanation:

During AP domain initialization, a suffixed CICS module or table could not be loaded. This message is issued for all suffixable modules which cannot be located after CANCEL has been specified in response to a preceding DFHAP0100 message.

System action:

The AP domain initialization continues until the end of the nucleus load process. CICS is then abnormally terminated with a dump.

User response:

Determine whether the suffix is correct. If it is not, either correct the SIT or name the correct suffix via an override for the next initialization of CICS. Otherwise correct the error by adding the module to the appropriate library.

Destination:

Console

Modules:

DFHSIB1

XMEOUT Parameters: applid, modname

Start of changeDFHAP0360End of change
Start of changedate time applid An attempt to establish security for userid userid has failed. SAF codes are (X'safresp',X'safreas'). ESM codes are (X'esmresp',X'esmreas').End of change
Start of change
Explanation:

An attempt was made to establish security for userid userid but it was rejected by the external security manager (ESM). Check that the userid has been defined correctly.

End of change
Start of change
System action:

Security has not been established for the userid. The attempt to start the transaction has failed.

End of change
Start of change
User response:

The response and reason codes (safresp and safreas) returned by the system authorization facility (SAF), and the response and reason codes (esmresp and esmreas) returned by the external security manager (ESM) are those issued by the RACROUTE REQUEST=VERIFY or RACROUTE REQUEST=EXTRACT macros. These return codes are described in the Start of changeOS/390 MVS Programming: Authorized Assembler Services GuideEnd of changeStart of change,End of change and in External Security Interface (RACROUTE) Macro Reference for MVS and VM (SC28-1366). See these manuals for an explanation of the codes.

There may be further messages produced by CICS or the external security manager (ESM) which provide more information.

End of change
Start of change
Destination:

CSCS

End of change
Modules:

Start of changeDFHICXM DFHIEXMEnd 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 changeuserid, End of changeStart of changeX'End of changeStart of changesafresp', End of changeStart of changeX'safreas', End of changeStart of changeX'End of changeStart of changeesmresp', End of changeStart of changeX'End of changeStart of changeesmreasEnd of changeStart of change'End of change

DFHAP0501
date time applid Program progname has issued an ADDRESS CSA command that is no longer supported.
Explanation:

The program progname has attempted to address the CSA. This function is no longer supported. The address returned is now fetch protected. Any attempt to reference this address results in an abend.

System action:

CICS continues.

User response:

Remove this command from the application program. Translate and compile. Remove any references to the address that was previously returned.

Destination:

CMIG

Modules:

DFHEEI

XMEOUT Parameters: date, time,applid, progname

DFHAP0601
applid Force purge of transaction id tranid transaction number trannum has been deferred because the transaction is executing post commit syncpoint processing.
Explanation:

CICS has received a request to force purge a transaction. The target of the force purge request is part way through processing the second phase of a two phase syncpoint. If the purge was accepted at this time, the target transaction would be abended and this would cause CICS to fail with a U0408 abend. There is no way of purging the target transaction while it is in this state. Transactions should only remain in this state for a short period of time. A subsequent attempt to force purge the transaction may preempt the deferred abend issued by the system when this condition was detected. This would result in the transaction being purged from the system faster than if the deferred purge is left to take effect.

System action:

CICS defers the purge until the target transaction is no longer protected against purge.

User response:

Retry the purge after a short interval if the target transaction has not ended.

Note:
Do not attempt to reroute this message to a transient data queue.
Destination:

Console

Modules:

DFHAPXME

XMEOUT Parameters: applid, tranid,trannum

DFHAP0602
applid Force purge of transaction id tranid transaction number trannum has been deferred because the transaction is executing transaction backout.
Explanation:

CICS has received a request to force purge a transaction. The target of the force purge request is part way through transaction backout processing (either as a result of an earlier transaction abend, or a syncpoint rollback request). If the purge was accepted at this time, the target transaction would be abended and this would cause CICS to fail with a U0405 abend. There is no way of purging the target transaction while it is in this state. Transactions should only remain in this state for a short period of time. A subsequent attempt to force purge the transaction may preempt the deferred abend issued by the system when this condition was detected. This would result in the transaction being purged from the system faster than if the deferred purge is left to take effect.

System action:

CICS defers the purge until the target transaction is no longer protected against purge.

User response:

Retry the purge after a short interval if the target transaction has not ended.

Note:
Do not attempt to reroute this message to a transient data queue.
Destination:

Console

Modules:

DFHAPXME

XMEOUT Parameters: applid, tranid,trannum

DFHAP0603
applid Forcepurge of transaction ID tranid, transaction number trannum, recovery token X'rtoken' has been deferred because the transaction is waiting for a DLI request in DBCTL to complete.
Explanation:

CICS has received a request to forcepurge a transaction. The target of the forcepurge request is waiting in DBCTL (or an IMS DC system which CICS thinks is a DBCTL) for the DLI request to complete. If the forcepurge was accepted at this time, the IMS system would fail with a U113 abend. The target transaction cannot be purged while it is in this state. Transactions should only remain in this state for a short time, unless the transaction is requesting some data or resource held by some other task in DBCTL. The recovery token may be used to identify which DBCTL thread corresponds to your task. (Issue /DIS CCTL ALL against the relevant DBCTL). One of the other active threads probably holds the resource you are waiting for. A subsequent attempt to forcepurge the transaction may preempt the deferred abend issued by the system when this condition was detected. This would result in the transaction being purged from the system faster than if the deferred purge is left to take effect.

System action:

CICS defers the forcepurge until the target transaction is no longer protected against purge.

User response:

Retry the forcepurge after a short interval if the target transaction has not ended. If the purge is still deferred, you will not be able to purge this transaction until the resource it is waiting for is released.

Note:
Do not attempt to reroute this message to a transient data queue.
Destination:

Console

Modules:

DFHAPXME

XMEOUT Parameters: applid, tranid,trannum, X'rtoken'

Start of changeDFHAP0604End of change
Start of changeapplid Forcepurge of transaction ID tranid, transaction number trannum, recovery token X'rtoken' has been deferred because the transaction is on a CICS-DB 2 ready queue waiting for a thread or TCB to become available.End of change
Start of change
Explanation:

CICS has received a request to forcepurge a transaction. The target of the forcepurge request is queued on a CICS-DB2 ready queue awaiting a DB2 thread or TCB to become available. The target transaction cannot be purged while it is in this state.

If the CEMT INQUIRE TASK panel shows the task with an htype value of 'CDB2TCB', this means the task is awaiting a CICS-DB2 subtask TCB to become available, meaning that the DB2CONN defined TCBLIMIT has been reached.

If the CEMT INQUIRE TASK panel shows the task with an htype value of 'CDB2CONN', this means the task is awaiting a CICS-DB2 connection to become available with which to associate with the CICS open tcb to be used for the request. This indicates that the DB2CONN defined TCBLIMIT has been reached which limits the number of open TCBs that can be used for DB2.

If the htype value is 'CDB2RDYQ',this means the task is awaiting a CICS-DB2 thread to become available, and Hvalue identifies the pool, or the particular DB2ENTRY against which it is queued.

Transactions should remain in these states only for a short time.

End of change
Start of change
System action:

CICS defers the forcepurge until the target transaction is no longer protected against purge.

End of change
Start of change
User response:

If the task is queued awaiting a CICS-DB2 subtask TCB, you can increase the value of TCBLIMIT in the DB2CONN. If the transaction is awaiting a CICS-DB2 thread, you can increase the THREADLIMIT value in the DB2ENTRY, or in the DB2CONN for the pool.

Note:
Do not attempt to reroute this message to a transient data queue.
End of change
Start of change
Destination:

Console

End of change
Modules:

Start of changeDFHAPXMEEnd of change

Start of changeXMEOUT Parameters:End of changeStart of change End of changeStart of changeapplid, End of changeStart of changetranid,End of changeStart of changetrannum, End of changeStart of changeX'End of changeStart of changertokenEnd of changeStart of change'End of change

DFHAP0701
applid An abend (code abcode) has occurred in exit program progname at exit point xxxxxxxx.
Explanation:

An abnormal end (abend) or program check has occurred in the program progname. This implies that there is an error in the error program, that unexpected data has been input, or storage has been overwritten.

The code is a three digit hexadecimal MVS code (if applicable), followed by a four 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:

CICS makes an exception entry in the trace table and returns a zero return code to the exit point. CICS also produces a system dump unless:

Either CICS continues unless you have specified in the dump table that CICS should terminate.

Or This is a critical error and CICS is terminated, even if you have specified in the dump table that CICS should not terminate. If this is the case, a zero return code is returned to the CICS management module.

User response:

There might be a logic error in the user exit program progname. DISABLE the exit program from all exit points, by using the EXITALL operand in the EXEC CICS DISABLE, and correct the error.

For programming information about coding user exit programs see the CICS Customization Guide.

Destination:

Console

Modules:

DFHSUEX, DFHUEH

XMEOUT Parameters: applid, abcode,progname, xxxxxxxx

DFHAP0704
applid A possible loop has been detected in exit program progname at exit point xxxxxxxx.
Explanation:

The exit program progname was in control and the transaction has consumed more CPU time than has been specified in the ICVR. There is probably a loop.

System action:

CICS returns a zero return code to the exit point. CICS also produces a system dump unless

User response:

There is a probable logic error in the user exit program progname. DISABLE the exit program from all exit points by using the EXITALL operand in the EXEC CICS DISABLE, and correct the error.

Refer to the CICS Customization Guide for further information about coding user exit programs.

If you think there is no loop, you can increase the runaway task time interval in the ICVR by using CEMT. This is explained in the CICS Supplied Transactions manual.

Destination:

Console

Modules:

DFHSUEX, DFHUEH

XMEOUT Parameters: applid, progname, xxxxxxxx

DFHAP0705 W
date time applid The enable of task related user exit program progname has caused CICS to force TASKDATALOC(BELOW) for all transactions.
Explanation:

Task-related user exit program progname has been enabled with options TASKSTART and LINKEDITMODE, and progname has been linkedited AMODE 24. This ensures that it is always invoked in amode 24. An amode 24 task-related user exit program can only be invoked if the calling transaction is defined with TASKDATALOC(BELOW).

By enabling the AMODE 24 task-related user exit for task start, the user has forced CICS to force all subsequent transactions to run with TASKDATALOC(BELOW).

System action:

CICS continues, but for the remainder of the CICS run, CICS insists that all transactions run with TASKDATALOC(BELOW).

User response:

To avoid all transactions having to run with TASKDATALOC(BELOW), modify the task-related user exit so that it is capable of running AMODE(31) when invoked for task start.

Ideally the task-related user exit should be modified so that it always runs AMODE 31 for whoever is the caller. In this case the exit program can be linkedited with the AMODE 31 attribute, and enabled with the LINKEDITMODE option. This ensures CICS always invokes it in AMODE 31.

Alternatively the task-related user exit could be modified so it is capable of being invoked in either amode. In this case the exit should be enabled without the LINKEDITMODE option. This means the exit will be invoked in the amode of its caller. For CICS calls such as task start, this will always be AMODE 31, but it does allow the exit to be invoked AMODE 24 for calls from an amode 24 application if this is desired.

See the CICS Resource Definition Guide. for more information on the TASKDATALOC option.

See the CICS Customization Guide for programming information on the LINKEDITMODE option when enabling task-related user exits.

Destination:

Console and Transient Data Queue CSMT

Modules:

DFHUEM

XMEOUT Parameters: date, time,applid, progname

DFHAP0706
applid A probable loop has been detected in task related user exit program progname.
Explanation:

The task related user exit program progname was in control and the transaction has consumed more CPU time than has been specified in the ICVR. There is probably a loop.

System action:

CICS produces a system dump unless you have specifically suppressed dumps in the dump table.

User response:

There is a probable logic error in the task related user exit program progname. DISABLE the exit program and correct the error.

Refer to the CICS Customization Guide for programming information about task-related user exit programs.

If there is no loop, you can avoid this problem by increasing the runaway task time interval in the ICVR using CEMT. This is explained in the CICS Supplied Transactions.

Destination:

Console

Modules:

DFHERM

XMEOUT Parameters: applid, progname

DFHAP0707
applid An abend (code abcode) has occurred in task related user exit program progname.
Explanation:

An abnormal end (abend) or program check has occurred in the task related user exit program progname. This implies that there is an error in the exit program, that unexpected data has been input, or storage has been overwritten.

The code is a three digit hexadecimal MVS code (if applicable), followed by a four digit alphanumeric CICS code. The MVS code is a system completion code (for example, X'0C1' or X'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:

Start of changeCICS makes an exception entry in the trace table. A system dump is produced if requested via an entry in the dump table.End of change

CICS continues unless you have specified in the dump table that CICS should terminate.

User response:

There might be a logic error in the task related user exit program progname. DISABLE the task related user exit program and correct the error.

For programming information about coding task related user exit programs see the CICS Customization Guide.

Destination:

Console

Modules:

DFHERM

XMEOUT Parameters: applid, abcode,progname

Start of changeDFHAP0801IEnd of change
Start of changeapplid z/OS Conversion Services are not available.End of change
Start of change
Explanation:

Character conversion is not possible using z/OS conversion services because these services are not enabled.

End of change
Start of change
System action:

CICS continues.

End of change
Start of change
User response:

None. You can suppress this message with the system initialization parameter, MSGLVL=0. If z/OS conversion services are to be used by CICS then they must be enabled by following the steps in the z/OS Support for Unicode manual.

End of change
Start of change
Destination:

Console

End of change
Modules:

Start of changeDFHCCNVGEnd of change

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

Start of changeDFHAP0802End of change
Start of changeapplid Data conversion using CCSID ccsid1 and CCSID ccsid2 is not supported by this system.End of change
Start of change
Explanation:

CICS has received a request to convert some character data from one CCSID encoding to another. This CCSID combination is not currently supported by the region.

End of change
Start of change
System action:

The conversion process fails and no data is converted

End of change
Start of change
User response:

If z/OS conversion services are being used then add this CCSID combination to the conversion image and retry the request.

Note:
Do not attempt to reroute this message to a transient data queue.
End of change
Start of change
Destination:

Console

End of change
Modules:

Start of changeDFHCCNVGEnd of change

Start of changeXMEOUT Parameters:End of changeStart of change End of changeStart of changeapplid, End of changeStart of changeccsid1,End of changeStart of changeccsid2End of change

Start of changeDFHAP0900End of change
Start of changeapplid MQ support for CICS Web Services is not available.End of change
Start of change
Explanation:

An attempt has been made to use Websphere MQ as the transport for CICS Web Services, but the Websphere MQ stub CSQCSTUB could not be loaded during CICS Initialisation. The Websphere MQ library SCSQLOAD needs to be included in the DFHRPL concatenation to permit use of Websphere MQ as a transport for CICS Web Services

End of change
Start of change
System action:

The attempt to use Websphere MQ as a transport for CICS Web Services has been rejected. Any further such attempts will also be rejected, and this message will be produced again.

End of change
Start of change
User response:

The Websphere MQ library SCSQLOAD must be included in the DFHRPL concatenation to allow use of Websphere MQ as a transport for CICS Web Services. This is in addition to the other Websphere MQ libraries needed for MQ support in CICS.

End of change
Start of change
Destination:

Console

End of change
Modules:

Start of changeDFHPITQ1, DFHPILSQEnd of change

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

DFHAP1006
applid Resource definition recovery has failed with code X'code' in module modname.
Explanation:

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

System action:

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

This is a critical error and CICS is terminated even if you have specified in the dump table that CICS should not terminate.

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

User response:

Notify the system programmer. This failure indicates a serious error in CICS. For further information about CICS exception trace entries, see the CICS Diagnosis Reference.

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

Destination:

Console

Modules:

DFHAPRDR, DFHTCRP

XMEOUT Parameters: applid, X'code',modname

DFHAP1007
applid A GETMAIN has failed for a resource definition control block code X'code' in module modname.
Explanation:

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

System action:

An exception entry is made in the trace table (X'code' in the message). 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. Message DFHME0116 is normally produced containing the symptom string for this problem.

User response:

Notify the system administrator. This failure may indicate that you need to increase the size limits of the EDSAs. EDSA storage limits are specified by the EDSALIM system initialization parameter. See the CICS System Definition Guide for more guidance on EDSALIM. For further information about CICS exception trace entries, see the CICS Diagnosis Reference.

Destination:

Console

Modules:

DFHAPRDR

XMEOUT Parameters: applid, X'code',modname

DFHAP1200
applid A CICS request to the Language Environment has failed. Reason code rc.
Explanation:

CICS has attempted to communicate with AD/Cycle Language Environment, but due to an error, the function requested by CICS could not be performed.

System action:

If the error occurs during system initialization, then the initialization continues but without support for the Language Environment. If the error occurs in a user application program, then the transaction is abnormally terminated.

User response:

For an explanation of the Language Environment return code rc, refer to the Language Environment Debugging Guide and Runtime Messages manual.

If the error occurs during system initialization, check that the Language Environment modules and the modules required for the languages supported by that environment have been correctly installed. In particular ensure that:

Destination:

Console

Modules:

DFHAPLI

XMEOUT Parameters: applid, rc

DFHAP1203I
applid Language Environment is being initialized.
Explanation:

This is an informatory message indicating that CICS is initializing support for the Language Environment.

System action:

System initialization continues.

User response:

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

Destination:

Console

Modules:

DFHAPLI

XMEOUT Parameter: applid

Start of changeDFHAP1206End of change
Start of changeapplid CEECCICS module not found.End of change
Start of change
Explanation:

This is an informatory message indicating that CICS is unable to locate the Language Environment CEECCICS module either via the BLDL mechanism or in the LPA, and consequently CICS cannot call Language Environment to initialize.

End of change
Start of change
System action:

System initialization continues. However it will not be possible to execute application programs written in a high level language.

End of change
Start of change
User response:

If you wish to execute programs written in a high level language, you must ensure that the CEECCICS module, which is distributed in the Language Environment SCEERUN library, can be located either via STEPLIB or in the LPA.

End of change
Start of change
Destination:

Console

End of change
Modules:

Start of changeDFHAPLIEnd of change

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

Start of changeDFHAP1207End of change
Start of changeapplid CEEPIPI module not found.End of change
Start of change
Explanation:

This is an informatory message indicating that CICS is unable to locate the Language Environment CEEPIPI module either via the BLDL mechanism or in the LPA.

End of change
Start of change
System action:

System initialization continues. However it will not be possible for CICS to establish the pre-initialized environment required by CICS to support the JVM and sockets.

End of change
Start of change
User response:

If you need this CICS system to support the JVM and sockets, you must ensure that the CEEPIPI module, which is distributed in the Language Environment SCEERUN library, can be located either via STEPLIB or in the LPA. Also ensure that the Language Environment SCEERUN2 library is included in STEPLIB or LPA.

End of change
Start of change
Destination:

Console

End of change
Modules:

Start of changeDFHAPLIEnd of change

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

Start of changeDFHAP1208End of change
Start of changeapplid Language Environment cannot support the Cobol language.End of change
Start of change
Explanation:

This is an informatory message indicating that Language Environment has initialized successfully but is unable to execute programs written in the Cobol language.

End of change
Start of change
System action:

System initialization continues. However it will not be possible for CICS to run applications written in Cobol.

End of change
Start of change
User response:

If you need this CICS system to support the Cobol language you should search the joblog for any messages issued by Language Environment. One possible reason is that the CEEEV005 program, which is the Language Environment interface module to the Cobol runtime, has not been defined in the CICS System Definition (CSD) file. Refer to the Language Environment for OS/390 Customization for further guidance.

End of change
Start of change
Destination:

Console

End of change
Modules:

Start of changeDFHAPLIEnd of change

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

Start of changeDFHAP1209End of change
Start of changeapplid Language Environment cannot support the C/C++ languages.End of change
Start of change
Explanation:

This is an informatory message indicating that Language Environment has initialized successfully but is unable to execute programs written in the C and C++ languages.

End of change
Start of change
System action:

System initialization continues. However it will not be possible for CICS to run applications written in C or C++.

End of change
Start of change
User response:

If you need this CICS system to support the C and C++ languages you should search the joblog for any messages issued by Language Environment. One possible reason is that the CEEEV003 program, which is the Language Environment interface module to the C runtime, has not been defined in the CICS System Definition (CSD) file. Refer to the Language Environment for OS/390 Customization for further guidance.

End of change
Start of change
Destination:

Console

End of change
Modules:

Start of changeDFHAPLIEnd of change

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

Start of changeDFHAP1210End of change
Start of changeapplid Language Environment cannot support the PL/I language.End of change
Start of change
Explanation:

This is an informatory message indicating that Language Environment has initialized successfully but is unable to execute programs written in the PL/I language.

End of change
Start of change
System action:

System initialization continues. However it will not be possible for CICS to run applications written in PL/I.

End of change
Start of change
User response:

If you need this CICS system to support the PL/I language you should search the joblog for any messages issued by Language Environment. One possible reason is that the CEEEV010 program, which is the Language Environment interface module to the PL/I runtime, has not been defined in the CICS System Definition (CSD) file. Refer to the Language Environment for OS/390 Customization for further guidance.

End of change
Start of change
Destination:

Console

End of change
Modules:

Start of changeDFHAPLIEnd of change

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

Start of changeDFHAP1211IEnd of change
Start of changeapplid Language Environment initialization completed.End of change
Start of change
Explanation:

This is an informatory message indicating that Language Environment initialization has completed.

End of change
Start of change
System action:

System initialization continues.

End of change
Start of change
User response:

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

End of change
Start of change
Destination:

Console

End of change
Modules:

Start of changeDFHAPLIEnd of change

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

DFHAP1212
date time applid The program program_name was defined as language1 but CICS has redefined it as language2.
Explanation:

You have defined program program_name as language1. During validation CICS determined that language1 is not a valid language for program_name and has redefined the program with language2.

CICS is able to determine the program language automatically. It is therefore not necessary for users to pass the language of a program to CICS via an autoinstall exit.

System action:

Processing continues.

User response:

None. This message is issued for information only.

Destination:

CSTL

Modules:

DFHAPLI

XMEOUT Parameters: date, time,applid, program_name, language1,language2

DFHAP1213
applid An unexpected error has occurred during the LOAD of the modname module with system completion code compcode and reason code reason .
Explanation:

Either an error was detected when CICS tried to load one of the required language interface modules, or the region size you have defined for CICS is too small.

During the language initialization phase of CICS startup, an unexpected error has occurred while CICS was initializing the necessary support. Possibly CICS has determined that there is insufficient storage to enable run-time language support to be correctly installed. Application program execution is likely to be severely restricted if CICS continues.

System action:

CICS initialization continues.

User response:

You should examine the console log for any error messages which may have been issued by the operating system immediately preceding this CICS message. If no operating system messages were issued, it is likely that there is insufficient storage for CICS to continue and you should restart CICS with a larger region size.

Destination:

Console

Modules:

DFHAPLI

XMEOUT Parameters: applid, modname,compcode, reason

Start of changeDFHAP1214End of change
Start of changeapplid Language Environment global ENVAR option defined with invalid CICS program options.End of change
Start of change
Explanation:

An error has been detected in the Language Environment global runtime ENVAR option. The ENVAR string contains a substring in the form 'CICSVAR=xx....xx', but 'xx....xx' is an invalid or unsupported program option. At this level of CICS, the only valid options are 'OPENAPI', 'THREADSAFE' or 'QUASIRENT'.

End of change
Start of change
System action:

The incorrect ENVAR substring is ignored.

End of change
Start of change
User response:

Refer to the CICS System Definition Guide for information on how to define program options in the ENVAR string.

End of change
Start of change
Destination:

Console

End of change
Modules:

Start of changeDFHAPLIEnd of change

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

Start of changeDFHAP1215End of change
Start of changeapplid Invalid CICS program options found in ENVAR string in program pgmname.End of change
Start of change
Explanation:

The application program contains user-defined Language Environment runtime options, and an error has been detected in the specification of the ENVAR option. The ENVAR string contains a substring in the form 'CICSVAR=xx....xx', but 'xx....xx' is an unsupported or invalid program option. At this level of CICS, the only supported options are 'OPENAPI', 'THREADSAFE' or 'QUASIRENT'.

End of change
Start of change
System action:

The incorrect ENVAR substring is ignored.

End of change
Start of change
User response:

Refer to the CICS System Definition Guide for information on how to define program options in the ENVAR string.

End of change
Start of change
Destination:

Console

End of change
Modules:

Start of changeDFHAPLIEnd of change

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

Start of changeDFHAP1217End of change
Start of changedate time applid Attempt to fetch user replaceable module DFHJVMAT has failed.End of change
Start of change
Explanation:

The CICS JVM interface issued a fetch to load user replaceable module DFHJVMAT. The native C fetch request failed.

End of change
Start of change
System action:

The CICS transaction is abended with abend code AJM9.

End of change
Start of change
User response:

Ensure that C program DFHJVMAT is present in a dataset in the CICS STEPLIB concatenation. Examine messages output by language environment to determine why the fetch request failed.

End of change
Start of change
Destination:

CSMT

End of change
Modules:

Start of changeDFHAPLJEnd 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 changeapplidEnd of change

Start of changeDFHAP1218End of change
Start of changedate time applid CEEPIPI function pipifn failed with return code r15rc.End of change
Start of change
Explanation:

CICS XPLINK called CEEPIPI with one of the following function codes:

1  = init_main to initialize a new PIPI execution
               environment
2  = call_main to invoke the main program in the
               PIPI environment
5  = term      to terminate a PIPI execution
               environment
6  = add_entry to add an entry to the PIPI PreInit
               Table
11 = delete_entry to delete an entry from the PIPI
                  PreInit Table

A non-zero return code from CEEPIPI indicates that the function failed.

End of change
Start of change
System action:

Language Environment may have written diagnostic information to the CESE destination. CICS abends the transaction with an abend code of ALX1, ALX2, ALX3, ALX4 or ALX5 depending upon the reason for the call to CEEPIPI.

End of change
Start of change
User response:

Look at SYSOUT or the CESE destination for LE messages. Look in Language Environment Programmers Guide (SC28-1939) for the CEEPIPI function and the explanation of the return code which is in Register 15.

End of change
Start of change
Destination:

CSMT

End of change
Modules:

Start of changeDFHAPLXEnd 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 changepipifn, End of changeStart of changer15rcEnd of change

Start of changeDFHAP1226End of change
Start of changedate time applid Program program is defined as EXECKEY(USER) but transaction transaction as TASKDATAKEY(CICS): these attributes are incompatible.End of change
Start of change
Explanation:

An attempt has been made to run a program defined as EXECKEY(USER) as part of a transaction defined as TASKDATAKEY(CICS). These attributes are incompatible. This incompatibility could occur as a result of the program definition being autoinstalled. See the CICS Customization Guide and the CICS Resource Definition Guide for more information about program autoinstall.

End of change
Start of change
System action:

The transaction will be abnormally terminated with abend code AEZD.

End of change
Start of change
User response:

Redefine and install a new definition either for the transaction with TASKDATAKEY(USER), or for the program with EXECKEY(CICS).

If this message occurs when running a CICS transaction, a possible cause is that you are not using the CICS-supplied definition for the program. If you are using your own copies of CICS-supplied program definitions, they must be defined as EXECKEY(CICS).

End of change
Start of change
Destination:

CSMT

End of change
Modules:

Start of changeDFHAPLIEnd 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 changeprogram, End of changeStart of changetransactionEnd of change

Start of changeDFHAP1300End of change
Start of changedate time applid The JVM at address X'jvm_anchor' on thread X'thread_anchor' has encountered an error (reason code: X'reason_code') and has requested further diagnostic data from CICS. More information may be found in the stderr file: stderr.End of change
Start of change
Explanation:

An error condition was detected by one of the JVMs in the JVMPool. The JVM invoked CICS services to capture a system dump. The JVM may recover, and continue processing, or may terminate. The JVM may write further data to the current stderr file indicated in the message.

End of change
Start of change
System action:

A system dump is taken. For critical errors in the JVM, the JVM is terminated. If a CICS program was in control at the time of the failure, the program is abended. If the failure occurred during task termination, the current transaction is rolled back. Processing continues by recreating the JVM or using other JVMs in the JVMPool.

End of change
Start of change
User response:

Examine the system dump using the JVM formatting utility. Use the address (jvm_anchor) shown in the message to identify the JVM. Optionally, use the address (thread_anchor) shown in the message to identify the thread in the JVM. The failure may be due to a JVM internal error, or to a component loaded by the JVM as a Native method or plug-in. The reason code given (reason_code) may be a signal handle or other code defined by the JVM. Use the information generated by the JVM in the stderr file to assist in the diagnosis of the problem.

End of change
Start of change
Destination:

CSMT

End of change
Modules:

Start of changeLIBDFHAPJVMT.SOEnd 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 changejvm_anchor', End of changeStart of changeX'thread_anchor', End of changeStart of changeX'End of changeStart of changereason_code', End of changeStart of changestderrEnd of change

Start of change
Start of changeDFHAP1301End of change
Start of changedate time applid Language Environment has detected a corruption of its control blocks. Transaction tranid currently executing.End of change
Explanation:

Language Environment has issued a return code 8 indicating its control blocks are corrupted.

Start of change
System action:

The transaction abnormally ends with abend code 0C3.

End of change
Start of change
User response:

Investigate the cause of the corruption of the Language Environment control blocks.

End of change
Start of change
Destination:

Console

End of change
Modules:

Start of changeDFHAPLIEnd of change

Start of changeXMEOUT Parameters:End of changeStart of changedate, End of changeStart of changetime,End of changeStart of changeapplid, End of changeStart of changetranidEnd of change

End of change
DFHAP1500
applid The CICS time-of-day is no longer synchronized with the system time-of-day.
Explanation:

The CICS time-of-day differs from the system time-of-day by more than 30 minutes.

System action:

CICS continues. However, as SIT parameter AUTORESETTIME is set to NO, a CEMT PERFORM RESET is needed to synchronize the CICS time-of-day with the system time-of-day.

User response:

Use the CEMT PERFORM RESET (or EXEC CICS PERFORM RESETTIME) command to ensure that CICS immediately resynchronizes its local time with that of the MVS TOD clock. This will ensure that the correct local time is used by all CICS functions, including the API.

Destination:

Console

Modules:

DFHAPTIM

XMEOUT Parameter: applid

[[ Contents Previous Page | Next Page Index ]]