An abnormal end (abend) or program check has occurred in module modname. This implies that there may be an error in CICS code. Alternatively, unexpected data has been input, or storage has been overwritten.
The code aaa/bbbb is a three 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; TS1310 refers to message DFHTS1310).
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.
Message DFHME0116 is normally produced containing the symptom string for this problem.
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 OS/390 MVS System Codes manual. Then look up the CICS alphanumeric code. This tells you, for example, whether the error is 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 to run and bring CICS down at a convenient time to resolve the problem.
If you cannot run 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.
Console
DFHCQCQ, DFHCQSY
XMEOUT Parameters: applid, aaa/bbbb, X'offset', modname
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. For further information about CICS exception trace entries, refer to the CICS Problem Determination Guide.
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.
The severity of this error 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 to run and bring CICS down at a convenient time to resolve the problem.
If the message recurs or if you cannot run 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.
Console
DFHCQCQ, DFHCQSY
XMEOUT Parameters: applid, X'code',modname
Console queue initialization has started.
System initialization continues.
None. The message can be suppressed with the system initialization parameter MSGLVL=0.
Console
DFHCQCQ
XMEOUT Parameter: applid
Console queue initialization has completed successfully.
System initialization continues.
None. The message can be suppressed with the system initialization parameter MSGLVL=0.
Console
DFHCQSY
XMEOUT Parameter: applid
Console queue initialization has failed.
Provided there are no subsequent serious errors which prevent further initialization of CICS, CICS issues one of two messages depending on what other errors, if any, have occurred during initialization.
If DFHSI1521 is issued, CICS initialization is terminated. If DFHSI1522 is issued, decide if CICS initialization is to be continued in degraded mode or to be terminated.
Check previous console messages, one of which should explain why console queue initialization has failed.
Console
DFHCQSY
XMEOUT Parameter: applid
CICS sets a limit of 255, the MVS maximum, on the number of modify commands that can be queued at any time for the CICS server.
CICS also sets an internal limit of 254 on the number of modifiy commands that can be queued at any time to invoke transactions, for example CEMT.
If this internal limit is reached CICS will reject further modify commands unless these invoke transaction CEKL.
System initialization continues.
None. The message can be suppressed with the system initialization parameter MSGLVL=0.
Console
DFHCQSY
XMEOUT Parameter: applid
CICS will not accept any modify commands from MVS.
System termination continues.
None. The message can be suppressed with the system initialization parameter MSGLVL=0.
Console
DFHCQSY
XMEOUT Parameter: applid
CICS can not accept the modify command as 254 modify commands to invoke transactions are currently queued.
CICS rejects the modify command.
The severity of this error depends on how many terminal definitions are being autoinstalled in your CICS system at the time you entered the modify command.
If the message recurs when you reenter the modify command you can use the CEKL INQUIRE and SET commands to identify the user tasks in your system and which, if any, should be removed from your system.
Console
DFHCQSY
CICS supports CEKL INQUIRE and CEKL SET commands.
CICS continues normally.
You can use the CEKL INQUIRE and CEKL SET commands from a console device.
Console
DFHCQSY
XMEOUT Parameter: applid
CICS supports only CEKL INQUIRE commands.
CICS continues normally.
Support for kill in CICS Transaction Server for z/OS 2.2 is being shipped in two PTFs which can be applied independently of each other.
You must apply both PTFs if you want to use the CEKL SET command.
If support for kill is not crucial to the running of your CICS system, you may decide to continue to run and bring CICS down at a convenient time to install the second PTF.
Console
DFHCQSY
XMEOUT Parameter: applid
The CEKL command has been rejected.
The INQUIRE or SET keyword is expected; neither has been specified.
The system continues normally.
Check the syntax of the CEKL command.
Console
DFHCQSY
The CEKL command has been rejected.
A keyword is expected but has not been specified.
The system continues normally.
Check the syntax of the CEKL command.
Console
DFHCQSY
The CEKL command has been rejected.
The input beginning input is too long; for example a transaction class name that is longer than 9 bytes.
The system continues normally.
Check the syntax of the CEKL command.
Console
DFHCQSY
The CEKL command has been rejected.
Keyword keyword has been specified more than once.
The system continues normally.
Check the syntax of the CEKL command.
Console
DFHCQSY
The CEKL command has been rejected.
invkwd is not a valid keyword.
The system continues normally.
Check the syntax of the CEKL command.
Console
DFHCQSY
The CEKL command has been rejected.
Keywords can be abbreviated provided that the abbreviated keyword is unique; for example TRANSID and TRANCLASS can be abbreviated to TRANS and TRANC respectively but not to TRAN.
The system continues normally.
Check the syntax of the CEKL command.
Console
DFHCQSY
The CEKL command has been rejected.
A non-numeric keyword value has been specified where a numeric value is expected; for example TASK(12345) is valid, TASK(abcde) is invalid.
The system continues normally.
Check the syntax of the CEKL command.
Console
DFHCQSY
The CEKL command has been rejected.
A keyword value has been specified which lies outside the range of values supported for the keyword; for example task numbers must be in the range 1-99999.
The system continues normally.
Check the syntax of the CEKL command.
Console
DFHCQSY
The CEKL command has been rejected.
A left paranthesis, '(', or a right paranthesis, ')' is expected but has not been specified.
The system continues normally.
Check the syntax of the CEKL command.
Console
DFHCQSY
The CEKL INQUIRE command has been rejected.
The TASK keyword is expected but has not been specified.
The system continues normally.
Check the syntax of the CEKL command.
Console
DFHCQSY
The CEKL INQUIRE command has been rejected.
A keyword is expected but has not been specified.
The system continues normally.
Check the syntax of the CEKL command.
Console
DFHCQSY
The CEKL INQUIRE command has been rejected.
Conflicting keywords have been specified.
The system continues normally.
Check the syntax of the CEKL command.
Console
DFHCQSY
The CEKL SET command has been rejected.
The TASK keyword is expected but has not been specified.
The system continues normally.
Check the syntax of the CEKL command.
Console
DFHCQSY
The CEKL SET command has been rejected.
A keyword is expected but has not been specified.
The system continues normally.
Check the syntax of the CEKL command.
Console
DFHCQSY
The CEKL SET command has been rejected.
The TASK keyword must be qualified by taskno.
The system continues normally.
Check the syntax of the CEKL command.
Console
DFHCQSY
The CEKL SET command has been rejected.
A keyword, PURGE or FORCEPURGE or KILL, is expected but has not been specified.
The system continues normally.
Check the syntax of the CEKL command.
Console
DFHCQSY
The CEKL SET command has been rejected.
Conflicting keywords have been specified.
The system continues normally.
Check the syntax of the CEKL command.
Console
DFHCQSY
Task number taskno has not been found.
The system continues normally.
Check the value that you specified fortaskno.
If this is correct then the task has been removed from the system.
Console
DFHCQSY
Task number taskno has been found.
CICS displays information about task taskno on the console and job log.
Console
DFHCQSY
CICS has not found any tasks that match the options specified on the CEKL INQUIRE command.
The system continues normally.
Check the options specified on the CEKL command. For example specify a lower value for the SUSPENDED option.
Console
DFHCQSY
notasks tasks have been found matching the options specified on the CEKL INQUIRE command.
CICS displays information about these tasks on the console and job log.
You should use the information to determine, which task, if any, should be removed from your system.
If the list of tasks is too long you may decide to invoke the CEKL INQUIRE command again specifying a different set of options.
Console
DFHCQSY
The request to remove task number taskno from the system has been rejected.
The task can not be found.
The system continues normally.
Check the value that you specified fortaskno.
If this is correct then the task has been removed from the system.
Console
DFHCQSY
The request to remove task taskno from the system has been deferred as it has not yet been attached to the to the dispatcher; the task either belongs to a transaction class that is at its MAXACTIVE limit or the system is at its MXT limit.
CICS will purge the task when it has been attached to the dispatcher.
None.
Console
DFHCQSY
A request has been passed to the dispatcher to purge task number taskno.
CICS continues normally.
The CEKL INQUIRE TASK(taskno) command can be used to display the progress of the request.
Console
DFHCQSY
The request to purge number taskno has been ignored.
A previous request was passed to the dispatcher to purge the task.
CICS continues normally.
None.
Console
DFHCQSY
The request to purge number taskno has been ignored.
A previous request was passed to the dispatcher to forcepurge the task.
CICS continues normally.
None.
Console
DFHCQSY
The request to kill purge number taskno has been ignored.
A previous request was passed to the dispatcher to kill the task.
CICS continues normally.
None.
Console
DFHCQSY
A request has been passed to the dispatcher to forcepurge task number taskno.
CICS continues normally.
The CEKL INQUIRE TASK(taskno) command can be used to display the progress of the request.
Console
DFHCQSY
The request to kill forcepurge number taskno has been ignored.
A previous request was passed to the dispatcher to forcepurge the task.
CICS continues normally.
None.
Console
DFHCQSY
The request to forcepurge number taskno has been ignored.
A previous request was passed to the dispatcher to kill the task.
CICS continues normally.
None.
Console
DFHCQSY
A request has been passed to the dispatcher to kill task number taskno.
CICS continues normally.
The CEKL INQUIRE TASK(taskno) command can be used to display the progress of the request.
Console
DFHCQSY
The request to kill task number taskno has been ignored.
A previous request was passed to the dispatcher to kill the task.
CICS continues normally.
The CEKL INQUIRE TASK(taskno) command can be used to display the progress of the request.
Console
DFHCQSY
The request to purge system task number taskno from the system has been rejected.
The system continues normally.
None.
Console
DFHCQSY
The request to forcepurge system task number taskno from the system has been rejected.
The system continues normally.
None.
Console
DFHCQSY
The request to kill system task number taskno from the system has been rejected.
The system continues normally.
None.
Console
DFHCQSY
The request to purge task number taskno from the system has been rejected. The transaction definition specifies SPURGE(NO).
The system continues normally.
Retry the request to remove the task from the system specifying either the FORCEPURGE or the KILL option.
Console
DFHCQSY
The request to forcepurge task number taskno has been rejected.
A request to remove the task from the system has been made and deferred as it has not yet been attached to the dispatcher; the task either belongs to a transaction class that is at its MAXACTIVE limit or the system is at its MXT limit.
CICS will purge the task when it has been attached to the dispatcher.
If the task can not be attached to the dispatcher because the system is under stress then
Console
DFHCQSY
The request to kill task number taskno has been rejected.
A request to remove the task from the system has been made and deferred as it has not yet been attached to the dispatcher; the task either belongs to a transaction class that is at its MAXACTIVE limit or the system is at its MXT limit.
CICS will purge the task when it has been attached to the dispatcher.
If the task can not be attached to the dispatcher because the system is under stress then
Console
DFHCQSY