Messages that are generated because the VTAM SYNAD and LERAD exits have been entered are followed by VTAM RETURN CODE xxyy where xx is the VTAM recovery action return code and yy is the VTAM specific error return code, each obtained from fields of the RPL.
Messages that are generated because system or user sense data has been received, are followed by SENSE RECEIVED xxyy zzzz where xx is the VTAM system sense information byte, yy is the VTAM system sense modifier byte, and zzzz represents 2 bytes of user sense information.
Values for xx, yy, and zzzz are hexadecimal. The VTAM system sense information byte, xx, can have the following values:
For the meaning of yy, see the SNA Formats manual.
The sense insert is not included in DFHZCxxxx messages when no meaningful feedback is available.
The instance field on some DFHZCxxxx messages is for IBM internal use only.
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).
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.
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 OS/390 MVS System Codes manual.
Next, look up the CICS abend 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 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.
For further information about code, 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.
Console
DFHZGBM, DFHZGCA, DFHZGCC, DFHZGCN, DFHZGDA, DFHZGPC, DFHZGRP, DFHZGSL, DFHZGUB
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.
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.
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 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
DFHZGCA, DFHZGCC, DFHZGCN, DFHZGDA, DFHZGPC, DFHZGRP, DFHZGSL, DFHZGUB
XMEOUT Parameters: applid, X'code',modname
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.
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 A message will be issued to this effect. Message DFHME0116 is normally produced containing the symptom string for this problem.
Inform the system programmer.
Try increasing the size of the DSA or EDSA. See the CICS System Definition Guide or the CICS Performance Guide for more information on CICS storage.
Console
DFHTCRP, DFHZGRP
XMEOUT Parameters: applid, X'code',modname
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.
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.
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.
Console
XMEOUT Parameters: applid, X'offset', modname
A predatory takeover is occurring. This means that a job is initializing which has the same applid as the CICS system. This initiates a takeover of the network. As a normal part of this process, VTAM drives the TPEND exit.
All requests on VTAM sessions are abnormally terminated and the sessions closed. The VTAM ACB is then opened by the application which is using the same APPLID as the CICS region. The new system recovers any persisting sessions.
If this takeover of the network was unintentional, you can prevent it happening in future by using RACF to protect the APPLID. Refer to the VTAM application security section in the VTAM Network Implementation Guide, SC31-6434 for details of how to do this.
Console and Transient Data Queue CSNE
DFHZNCA
XMEOUT Parameters: date, time,applid
A node initialization block (NIB) has been passed to CICS by VTAM during a persistent sessions restart. An attempt was made by CICS to match the NIB to a session TCTTE. The reason code explains the cause of the mismatch.
The attempt to match a persisting session with a TCTTE has failed. The session is unbound. CICS ignores this session and continues with the next session if there is one.
The production of this message means that there is no suitable global catalog record to match the NIB which VTAM has passed in. This implies that the wrong global catalog is being used for this initialization of CICS, or that the catalog records are corrupted. Ensure that the global catalog being used is correct.
CSNE
DFHZGPC
XMEOUT Parameters: date, time,applid, sessid, X'n'
During persistent sessions restart VTAM has returned more node initialization blocks (NIBs) than the current CNOS session limit values require. This is probably because a CNOS from a high session limit to a lower session limit was in progress when CICS failed.
The process NIB function is terminated. The session is unbound. CICS ignores this session and continues with the next session if there is one.
This situation has no effect on the restored CICS. The last catalogued CNOS values are restored.
None.
CSNE
DFHZGPC
XMEOUT Parameters: date, time,applid, sysid, modename
An error has occurred during persistent sessions restart. VTAM passed a NIB to CICS containing the named modename, but CICS was unable to locate the corresponding TCTME.
The attempt to match the NIB to a TCTTE is terminated. The session is unbound.
A system dump is produced.
The CNOS values not related to this modegroup are restored, but the named modegroup cannot be recovered.
You need further assistance from IBM to resolve this problem. See CICS Problem Determination Guide for guidance on how to proceed.
CSNE
DFHZGPC
XMEOUT Parameters: date, time,applid, sysid, modename
CICS is initializing with a cold or initial start, but some VTAM sessions have persisted from a previous CICS with a nonzero PSDI value.
CICS has attempted to terminate all persisting sessions. The message inserts are as follows:
If there are no earlier messages, it is possible that the count obtained from the VTAM INQUIRE counts macro, indicating the number of active sessions, was not equal to the number of sessions that VTAM held persisting. This is not a problem.
CICS continues.
None.
Console
DFHZGRP
XMEOUT Parameters: applid, icount,spcount, stcount
CICS is initializing with a WARM start, but some VTAM sessions unexpectedly persisted from a previous CICS with a nonzero PSDI value.
CICS has attempted to terminate all persisting sessions. The message inserts are as follows:
If there are no earlier messages, it is possible that the count obtained from the VTAM INQUIRE counts macro, indicating the number of active sessions, was not equal to the number of sessions that VTAM held persisting. This is not a problem.
CICS continues.
Examine the JOBLOG from the previous run to determine why sessions persisted despite a WARM shut down.
Console
DFHZGRP
XMEOUT Parameters: applid, icount,spcount, stcount
CICS is initializing with an EMERGENCY start, but XRF = YES has been specified and some VTAM sessions persisted unexpectedly from a previous CICS with a nonzero PSDI value.
CICS has attempted to close all persisting sessions. The message inserts are as follows:
If there are no earlier messages, it is possible that the count obtained from the VTAM INQUIRE counts macro, indicating the number of active sessions, was not equal to the number of sessions that VTAM held persisting. This is not a problem.
CICS continues.
You should not mix XRF and persistent sessions. If you wish to use XRF, do a cold or initial start.
Console
DFHZGRP
XMEOUT Parameters: applid, icount,spcount, stcount
The VTAM ACB has been opened while CICS is running, however some VTAM sessions persisted either from a previous CICS with a nonzero PSDI value, or when the VTAM ACB was closed.
Persisting sessions have been terminated. The message inserts are as follows:
If there are no earlier messages, it is possible that the count obtained from the VTAM INQUIRE counts macro, indicating the number of active sessions, was not equal to the number of sessions that VTAM held persisting. This is not a problem.
CICS continues.
None.
Console
DFHZGRP
XMEOUT Parameters: applid, icount,spcount, stcount
CICS was initializing with an EMERGENCY start and some VTAM sessions persisted from a previous CICS with a nonzero PSDI value.
Each of the persisting sessions has been restored or terminated. The message inserts are as follows:
CICS continues.
None.
Console
DFHZGRP
XMEOUT Parameters: applid, icount,spcount, stcount, socount, secount
CICS was initializing with an EMERGENCY start and some VTAM sessions persisted from a previous CICS with a nonzero PSDI value.
However, the session with a NETNAME of netname is terminated for one of the following reasons as indicated by the instance in the message. An AP exception trace entry is made for each instance as follows.
An AP exception trace with a point ID as above is issued. The session is terminated and CICS continues.
The exception trace point identifies where the message was issued and determines the action to take.
CSNE
DFHZGRP
XMEOUT Parameters: date, time,applid, netname, sense, instance, {1=DFHZGRP, 2=DFHZGRP, 3=DFHZGRP}
CICS was initializing with an EMERGENCY start but no VTAM sessions persisted from a previous CICS run. Possible reasons are:
CICS continues.
None.
Console
DFHZGRP
XMEOUT Parameter: applid
The VTAM ACB has been opened and CICS is processing VTAM persisting sessions, however the ACB was closed, or is being closed by operator action before all the sessions could be restored or terminated.
CICS continues to close the VTAM ACB and then runs without VTAM support.
Determine why the operator closed the ACB and either continue without VTAM, dynamically open the ACB, or shut CICS down normally and restart it.
X'code' is the AP exception trace entry that determines which VTAM macro diagnosed the ACB as being closed and where it was issued.
Console
DFHZGRP DFHZGUB
XMEOUT Parameters: applid, X'code',module
CICS is processing VTAM persisting sessions. However it has issued a VTAM macro and has waited for 8 minutes for the response.
If this occurs during start up, CICS terminates. If this occurs during dynamic open, the VTAM ACB is closed and CICS continues without VTAM.
A dump is taken for this message in both cases.
You can restart CICS again immediately, or wait for the persistent sessions to time out and then restart CICS.
If this problem recurs you need to find out why VTAM is not responding to the INQUIRE or OPNDST macro (if the message is issued by DFHZGRP), or the CLSDST or TERMSESS macro (if the message is issued by DFHZGUB).
You can determine which macro is not responding by examining the TCP section of the dump and looking at the RPLs in the PS POOL labeled PS_RPL. The first RPL is for use by INQUIRE or OPNDST, the next 10 by CLSDST or TERMSESS.
Console
DFHZGRP, DFHZGUB
XMEOUT Parameters: applid, module
CICS is processing VTAM persistent sessions during an EMERGENCY restart but VTAM returned a RTNCD,FDB2 of rc,fd in response to the OPNDST OPTCD=RESTORE macro.
An AP exception trace entry, X'code', is made.
A system dump is taken on the first occurrence of this problem unless dumps have been specifically suppressed in the dump table.
CICS attempts to terminate all the sessions in the NIBLIST instead of restoring them.
Use the dump taken on the first occurrence of this problem or the exception trace entry and the VTAM programming manual to determine the meaning of the RTNCD,FDB2 and the actions necessary to correct it.
Console
DFHZGRP
XMEOUT Parameters: applid, X'rc',X'fd', X'code'
CICS is processing VTAM persistent sessions but VTAM returned a RTNCD,FDB2 of rc,fd in response to the INQUIRE OPTCD=PERSESS macro.
An AP exception trace entry, X'code', is made.
A system dump is taken unless dumps have been specifically suppressed in the dump table.
If this occurs during initialization, CICS terminates.
If this occurs during a dynamic open of the ACB, CICS closes the ACB and continues to run without VTAM.
The sessions persist until the PSDI value times out or until VTAM operator commands are issued to terminate the sessions.
Use the dump or the exception trace entry and the VTAM programming manual to determine the meaning of the RTNCD,FDB2 and the actions necessary to correct it.
If the problem occurs during initialization, try to correct the error and then retry the start up, or wait until the PSDI value time expires and restart CICS.
If the problem occurs when the ACB was opened dynamically, you can repeat the command to open the VTAM ACB, or wait until the PSDI time expires and then repeat it.
Console
DFHZGRP
XMEOUT Parameters: applid, X'rc',X'fd', X'code'
CICS is processing VTAM persistent sessions and has issued an OPNDST OPTCD=RESTORE against a NIBLIST. However, the NIB identified by netname and a session or termid of termid failed to open successfully. This is probably because the session was terminated by the VTAM operator after INQUIRE OPTCD=PERSESS was issued.
CICS continues.
Reopen the session in the normal way.
CSNE
DFHZGRP
XMEOUT Parameters: date, time,applid, netname, termid
CICS is processing VTAM persistent sessions but VTAM returned a RTNCD,FDB2 of rc,fd in response to a subsequent INQUIRE OPTCD=PERSESS macro.
An AP exception trace entry, X'code', is made.
A system dump is taken unless you have specifically suppressed dumps in the dump table.
CICS continues with a partial network. Some of the sessions are usable, others are not until the PSDI value times out or the VTAM operator terminates the sessions that failed.
Use the dump or the exception trace entry and the VTAM programming manual to determine the meaning of the RTNCD,FDB2 and the actions necessary to correct it.
If enough of the network is available, wait until the PSDI value expires or use VTAM operator commands to terminate the sessions.
If the network is unusable, either close and reopen the VTAM ACB, or restart CICS.
Console
DFHZGRP
XMEOUT Parameters: applid, X'rc',X'fd', X'code'
CICS was initializing when an attempt to process VTAM persistent session failed. The reasons are given in earlier messages.
CICS terminates.
Examine earlier messages and exception trace entries to determine the reason for failure.
Console
DFHSII1
XMEOUT Parameter: applid
The VTAM ACB has been opened while CICS is running, and some VTAM sessions persisted after VTAM abended.
Each of the persisting sessions has been restored or terminated. The message inserts are as follows:
CICS continues.
None.
Console
DFHZGRP
XMEOUT Parameters: applid, icount,spcount, stcount, socount, secount
The PSDI value is nonzero. This specifies that VTAM sessions are to persist across CICS failures. However, this release of VTAM does not support persistent sessions.
CICS sets the PSDI value to 0 and continues without persistent session support.
ACF/VTAM Release 3 Version 4 Modification 1 or higher must be used in order to take advantage of CICS persistent session support.
To prevent this message being issued when using an earlier release of VTAM, set the PSDINT system initialization parameter to zero, and when using the EXEC CICS SET VTAM command, either omit, or specify a value of zero for the PSDINTERVAL operand.
Console
DFHZSLS
XMEOUT Parameter: applid
The PSDI value is nonzero. This specifies that VTAM sessions are to persist across CICS failures. However, DFHTCTxx was assembled against a release of VTAM that cannot support persistent sessions.
CICS sets the PSDI value to 0 and continues without persistent session support.
Reassemble the TCT against ACF/VTAM Release 3 Version 4 Modification 1 or higher in order to take advantage of CICS persistent session support.
To prevent this message being issued when using an earlier release of VTAM, set the PSDINT system initialization parameter to zero, and when using the EXEC CICS SET VTAM command, either omit, or specify a value of zero for the PSDINTERVAL operand.
Console
DFHZSLS
XMEOUT Parameter: applid
CICS was opening the VTAM ACB, setting the PSDI value from an operator command or doing a WARM shut down. It attempted to issue the VTAM command SETLOGON OPTCD=PERSIST or OPTCD=NPERSIST. However, VTAM returned a RTNCD,FDB2 of rc,fd.
An AP exception trace entry, code, is made.
A system dump is taken unless you have specifically suppressed dumps in the dump table.
If the ACB was being opened, no VTAM sessions persist and the PSDI value is set to 0.
If just the PSDI value was being changed, either by the operator or during termination, the value is unchanged, both to CICS and to VTAM.
If this occurs during a VTAM shut down and some sessions are not closed, sessions may exist on VTAM start-up and are terminated then.
Use the dump taken or the exception trace entry code and the VTAM programming manual to determine the meaning of the RTNCD,FDB2 and the actions necessary to correct it.
Console
DFHZGSL
XMEOUT Parameters: applid, X'rc',X'fd', X'code'
CICS has received an attach FMH5 for a synclevel 2 conversation from a partner with netname netname before exchange lognames processing is complete.
A Deallocate(Abend) with sense code 08640001 is issued for the conversation.
No further APPC synclevel 2 conversations can be started by the partner until exchange lognames has completed. Use CEMT to inquire on the status of the connection in order to determine whether exchange lognames has completed (see the CICS Supplied Transactions for more information).
CSNE
DFHZGDA
XMEOUT Parameters: date, time,applid, sysid, termid, netname, sense, instance, {1=DFHZGDA}
The APPC session termid with netname persisted during a CICS persistent sessions restart. The partner initiated a new synclevel 2 conversation before Exchange Lognames processing had completed. CICS attempted to issue a Deallocate(Abend) for the conversation. The Deallocate(Abend) could not be completed for the reason indicated by the instance in the message as follows.
For the meaning of the sense data, see DFHZCxxxx messages.
The state of the session after the persistent sessions restart cannot be determined, and the session is deactivated in order to reset the states The sessions are reactivated.
If the session is not successfully reactivated, check the CSNE log for messages indicating why the new BIND failed. The session may have been set out of service by the VTAM operator.
CSNE
DFHZGDA
XMEOUT Parameters: date, time,applid, netname, termid, sense, instance, {1=DFHZGDA, 2=DFHZGDA}
CICS has restored the VTAM persistent session for terminal termid following a persistent sessions restart.
The equivalent message for APPC sessions is DFHZC0156.
If recovery notification is specified for this terminal, the recovery message is sent to the terminal, or the transaction requested to run at recovery notification time is started.
If required, code an NEP to override the recovery notification option originally specified in the TYPETERM definition for this session. See the CICS Resource Definition Guide and the CICS Customization Guide for more information.
CSNE
DFHZXRC
XMEOUT Parameters: date, time,applid, termid, sense, instance, {1=DFHZXRC}
An error has prevented the recovery of an APPC conversation which persisted across an emergency restart.
The session with a termid of termid is terminated. The reason and the corresponding AP exception trace entry are indicated by the instance in the message;
An AP exception trace with a point ID as above is issued. The session is terminated and CICS continues.
If recovery failed due to insufficient storage, try increasing the DSA or EDSA size limits (see the CICS Customization Guide). If any of the other instances occur, you will need further assistance from IBM. See CICS Problem Determination Guide for guidance on how to proceed.
CSNE
DFHZGDA
XMEOUT Parameters: date, time,applid, sysid, termid, sense, instance, {1=DFHZGDA, 2=DFHZGDA, 3=DFHZGDA, 4=DFHZGDA, 5=DFHZGDA}
As part of session recovery following a persistent session restart CICS issued a VTAM SEND or RECEIVE. The VTAM request failed leaving the session in an unknown state.
For the meaning of the sense data, see DFHZCxxxx messages.
The session is terminated.
To determine the cause of the problem, see the associated DFHZCnnnn message in the CSNE log. This message gives further diagnostic information on the failing VTAM request.
CSNE
DFHZGDA
XMEOUT Parameters: date, time,applid, sysid, termid, sense, instance, {1=DFHZGDA, 2=DFHZGDA}
During a persistent sessions restart, CICS has been notified of the failure of a session initiation request issued during the previous instance of CICS.
For the meaning of the sense data, see DFHZCxxxx messages.
Processing continues.
None
CSNE
DFHZNSP
XMEOUT Parameters: date, time,applid, termid, sense, instance, {1=DFHZNSP}
The VTAM session for terminal termid persisted during a CICS persistent sessions restart, but an error occurred while processing the session state data returned by VTAM. The reason is indicated by the instance in the message as follows.
For the meaning of the sense data, see DFHZCxxxx messages.
The state of the session after the persistent sessions restart cannot be determined, and the session is terminated in order to reset the states. Non-APPC sessions are restarted.
If the session is not successfully restarted, check the CSNE log for messages indicating why the new BIND failed. The session may have been set out of service by the VTAM operator.
CSNE
DFHZXRC
XMEOUT Parameters: date, time,applid, termid, sense, instance, {1=DFHZXRC, 2=DFHZXRC, 3=DFHZXRC, 4=DFHZXRC, 5=DFHZXRC, 6=DFHZXRC, 7=DFHZXRC, 8=DFHZXRC, 9=DFHZXRC, 10=DFHZXRC, 11=DFHZXRC, 12=DFHZXRC, 13=DFHZXRC}
Transaction transid was started invalidly. transid should only be ATTACHed by CICS. It should not be started by keying in through the terminal or by a START from a user program.
transid will terminate.
None
CSNE
DFHZSGN, DFHZPCT, DFHZRTP
XMEOUT Parameters:
date,
time,
applid,
transid,
transid
CICS attempted to sign on a user following a persistent sessions restart. The user domain replied with one of the following return codes:
An AP exception trace with point ID FB9B is issued.
The terminal is available but the user is not signed on to it. The terminal has the attributes of the default user.
Note the return code and take the necessary action. Look for messages output earlier by the ESM or the security domain. If no reason can be
CSNE
DFHZSGN
XMEOUT Parameters: date, time,applid, termid, termid, rc
The restart timer program DFHZRTP has failed in an attempt to write a timer record to the catalog. If no timer records are written to the catalog terminals will not be signed on again after a Persistent Sessions restart.
An exception trace is output.
Investigate the cause of the error. There may be a problem with the global catalog. Look for other messages confirming this.
CSNE
DFHZRTP
XMEOUT Parameters:
date,
time,
applid
A timed start or cancellation of the restart timer program DFHZRTP failed. This means that no timer records will be written to the global catalog and terminals will be timed out if a Persistent Sessions restart occurs.
CICS initialization continues. In the event of a Persistent Sessions restart terminals will not be signed on.
Look for earlier messages and trace entries output by the timer domain which may indicate the reason for the failure. The most likely reason is that CICS is short on storage.
CSNE
DFHTCRP, DFHZPCT
XMEOUT Parameters:
date,
time,
applid
An AP exception trace with a point ID is issued. The state of the session
after the restart cannot be determined, and the session is terminated in order
to reset the states. The session is restarted. A system dump is produced
for all instances except 04.
If the session is not successfully restarted, check the CSNE log for messages indicating why the new BIND failed. The session may have been set out of service by the VTAM operator.
CSNE
DFHZXPS
XMEOUT Parameters: date, time,applid, sysid, termid, sense, instance, {1=DFHZXPS, 2=DFHZXPS, 3=DFHZXPS, 4=DFHZXPS, 5=DFHZXPS, 6=DFHZXPS, 7=DFHZXPS, 8=DFHZXPS, 9=DFHZXPS, 10=DFHZXPS, 11=DFHZXPS, 12=DFHZXPS, 13=DFHZXPS, 14=DFHZXPS, 15=DFHZXPS, 16=DFHZXPS, 17=DFHZXPS, 18=DFHZXPS, 19=DFHZXPS, 20=DFHZXPS, 21=DFHZXPS, 22=DFHZXPS, 23=DFHZXPS, 24=DFHZXPS, 25=DFHZXPS, 26=DFHZXPS, 27=DFHZXPS, 28=DFHZXPS, 29=DFHZXPS, 30=DFHZXPS, 31=DFHZXPS, 32=DFHZXPS, 33=DFHZXPS, 34=DFHZXPS, 35=DFHZXPS, 36=DFHZXPS, 37=DFHZXPS, 38=DFHZXPS, 39=DFHZXPS, 40=DFHZXPS, 41=DFHZXPS, 42=DFHZXPS, 43=DFHZXPS, 44=DFHZXPS, 45=DFHZXPS, 46=DFHZXPS, 47=DFHZXPS, 48=DFHZXPS, 49=DFHZXPS, 50=DFHZXPS, 51=DFHZXPS, 52=DFHZXPS, 53=DFHZXPS, 54=DFHZXPS, 55=DFHZXPS, 56=DFHZXPS, 57=DFHZXPS, 58=DFHZXPS, 59=DFHZXPS, 60=DFHZXPS, 61=DFHZXPS, 62=DFHZXPS, 63=DFHZXPS, 64=DFHZXPS, 65=DFHZXPS}
CICS has restored the VTAM APPC persisting session for sysid termid following a persistent sessions restart.
The equivalent message for non-APPC sessions is DFHZC0146. Note that the RECOVNOTIFY option that applies to message DFHZC0146 is not applicable to APPC sessions.
Processing continues.
None.
CSNE
DFHZXPS
XMEOUT Parameters: date, time,applid, sysid, termid, sense, instance, {1=DFHZXPS, 2=DFHZXPS}
CICS was unable to restore the APPC persisting session for sysid termid following a persistent sessions restart. There are three possible reasons for this:
The TCTTE and TIOA are output for information only.
The session is unbound and rebound.
None.
CSNE
DFHZXPS
XMEOUT Parameters:
date,
time,
applid,
sysid,
termid,
sense,
instance,
{1=DFHZXPS}
CICS was attempting to write signon data for termid to the global catalog so that the signon status could be recovered after a persistent sessions restart, but the catalog write failed.
An exception trace is output. Loss of the data may mean that termid will not be signed on or off correctly after a persistent sessions restart.
Investigate the cause of the error. Look for earlier messages and trace entries from the catalog domain indicating the cause of the error, for example the catalog may be full.
CSNE
DFHZSGN, DFHZPCT, DFHSNTU
XMEOUT Parameters:
date,
time,
applid,
termid
CICS has made two attempts to implement the change number of sessions (CNOS) command for the modename modename on the APPC connection sysid. The command was not successful because of other activity on the modegroup. This only happens on modegroups which are very busy. The state of one or more of the sessions has changed during the processing of the CNOS request.
The CNOS command results from a connection acquire, a connection release, or a request for a specific modename on this system or the connected system. If the connected system is not CICS, commands specific to that system may have been used.
The modegroup is left in the state reached after the second attempt to implement the changes.
Use the CEMT INQUIRE MODENAME command to determine the current state of the modegroup. The command may show the modegroup as you expect for successful CNOS completion. This is because the command only shows data for available and active sessions. CICS may have had problems with CNOS values for loser sessions, which would not be apparent by using CEMT. If the values are not as required, re-issue the original command.
CSNE
DFHZGCA
XMEOUT Parameters: date, time,applid, tranid, modename, netname, sysid
CICS has encountered an error while attempting to execute a change number of sessions (CNOS) command for the modename modename on the APPC connection sysid. The failure code X'code' is one of the following:
CICS makes an exception trace with ID AP xxxx; where xxxx is the code in the message. CICS takes a system dump for all failure codes except X'FBA2', X'FBA3', X'FBA6', X'FBAF', X'FBB1', and X'FBB9'. CICS continues without completing the request. The task does not abend. Message DFHME0116 is normally produced containing the symptom string for this problem.
This depends on the error code as follows:
CSNE
DFHZGCN
XMEOUT Parameters: date, time,applid, tranid, modename, netname, sysid, X'code'
The change number of sessions (CNOS) transaction program DFHZLS1 could not complete successfully. The error code X'code' is one of the following:
This may have occurred because a number of CLS1 tasks were started before shutdown was issued but are held up because CICS was at MAXTASK. During shutdown the VTAM ACB was closed and this task was then started.
CICS produces an exception trace, and except for in the case of an invalid start, a system dump is taken. The task terminates. Message DFHME0116 is normally produced containing the symptom string for this problem.
This depends on the error code as follows:
CSNE
DFHZLS1
XMEOUT Parameters: date, time,applid, tranid, sysid, X'code', X'subcode'
CICS successfully signed on a user at termid termid following a persistent sessions restart.
CICS continues.
None.
CSNE
DFHZSGN
XMEOUT Parameters:
date,
time,
applid,
termid,
termid
CICS attempted to sign on a user following a persistent sessions restart. The user could not be signed on because the RSTSIGNTIME value in the SIT had expired.
CICS continues.
The user is forced to sign on again.
CSNE
DFHZSGN
XMEOUT Parameters:
date,
time,
applid,
termid,
termid
CICS signed off a user at termid termid following a multinode persistent sessions restart.
CICS continues.
None.
CSNE
DFHZSGN
XMEOUT Parameters:
date,
time,
applid,
termid,
termid
CICS attempted to sign off a user at termid termid because of a signon timeout following a multinode persistent sessions restart. An exception or disaster response was received from the signon program DFHSNTU with one of the following reason codes:
An AP exception trace with point ID FB9D is issued.
Reason codes 002, 003, 019 and 028 indicate a problem with the ESM or the security domain. The remaining reason codes may indicate an internal error in CICS. Look for messages output earlier by the ESM or the security domain. If security was active when the problem occurred and there was no problem with the ESM or the security domain contact your IBM support center.
CSNE
DFHZSGN
XMEOUT Parameters:
date,
time,
applid,
termid,
termid,
rc1,
rc2
CICS has registered as a VTAM generic resource in the group grname.
CICS continues. It is now possible to log on using the generic resource name.
None.
Console
DFHZGSL
XMEOUT Parameters: applid, grname
CICS failed to register as a VTAM generic resource in the group grname.
VTAM returned a RTNCD,FDB2 of rc,fd in response to the SETLOGON OPTCD=GNAMEADD macro.
An AP exception trace entry is output with trace point FB8E.
CICS continues without generic resource support.
Use the VTAM programming manual to determine the meaning of the RTNCD,FDB2 and the actions necessary to correct the problem.
When the problem has been corrected a further attempt may be made to register CICS as a generic resource by closing and reopening the VTAM ACB.
Console
DFHZGSL
XMEOUT Parameters: applid, grname,X'rc', X'fd'
CICS has deregistered from VTAM generic resource group grname.
None. CICS will not reregister to the generic resource until the VTAM ACB has been closed and opened again.
None.
Console
DFHZGSL
XMEOUT Parameters: applid, grname
CICS failed to deregister from VTAM generic resource group grname.
VTAM returned a RTNCD,FDB2 of rc,fd in response to the SETLOGON OPTCD=GNAMEDEL macro.
This may be due to a hardware failure in another part of the sysplex or to corruption of the TCT prefix causing CICS to attempt to deregister with the wrong name.
An AP exception trace entry is output with a trace point of X'FB8E'.
Use the VTAM Programming Manual to determine the meaning of the register 15 and register 0 values output by VTAM. If the problem is not caused by use of the wrong version of VTAM, you will need further assistance from IBM. See CICS Problem Determination Guide for guidance on how to proceed.
Console
DFHZGLS
XMEOUT Parameters: applid, grname,X'rc', X'fd'
A call to a VTAM macro to initialize the node initialization block (NIB) before registering or deregistering as a VTAM generic resource has failed.
A possible explanation is that the wrong level of VTAM is being used.
The values of register 15 and register 0 returned by VTAM are output.
An exception trace is output with trace point X'FBED'.
If registration was about to be attempted, CICS continues without generic resource support.
If deregistration was about to be attempted, ACB shutdown continues. VTAM removes CICS as a member for the generic resource name when the ACB is closed.
Use the VTAM Programming Manual to determine the meaning of the register 15 and register 0 values output by VTAM. If the problem is not caused by use of the wrong version of VTAM, you will need further assistance from IBM. See CICS Problem Determination Guide for guidance on how to proceed.
Console
DFHZGLS
XMEOUT Parameters: applid, r15,r0
A value was specified for the GRNAME system initialization parameter. This indicates that CICS is to register as a VTAM generic resource. However, either DFHTCTxx was assembled against a release of VTAM that cannot support generic resource registration, or CICS is running on a VTAM earlier than release 4 version 2.
CICS sets the generic resource name to blanks and continues without attempting generic resource registration.
If you are running with ACF/VTAM Release 4 Version 2 or higher, reassemble the TCT against this level of VTAM in order to take advantage of CICS support for generic resource registration.
To prevent this message being issued when using an earlier release of VTAM, do not specify a value for the GRNAME system initialization parameter.
Console
DFHZSLS
XMEOUT Parameter: applid
An attempt was made to end an affinity between this CICS, which is a member of generic resource grname, and a remote LU with netid netid and netname netname by means of a SET CONNECTION ENDAFFINITY or PERFORM ENDAFFINITY command. The attempt has failed because a problem with VTAM prevented the VTAM CHANGE OPTCD=ENDAFFINITY macro from being issued.
VTAM has issued the return code-feedback (RTNCD,FDB2) X'rc',X'fd' in response to the CHANGE OPTCD=ENDAFFINITY macro.
R15 r15 is the register 15 value returned by VTAM.
Processing continues. VTAM has made no attempt to end the affinity.
See the VTAM programming manual for the meaning of the RTNCD,FDB2 and for guidance on correcting the problem.
When the problem has been corrected retry the command.
CSNE
DFHZGCH
XMEOUT Parameters: date, time,applid, grname, netid, netname, X'rc', X'fd', X'r15'
A generic resource member has established an APPC synclevel 2, APPC limited resource, or LU6.1 connection with another LU. For connections of these types VTAM creates affinities which are owned by CICS and have to be ended by the CICS operator using the SET CONNECTION ENDAFFINITY or PERFORM ENDAFFINITY command. The message is output whenever the connection is acquired but the affinity is not recreated for each acquire unless it has been ended in the meantime.
Processing continues.
None, but note that the affinity has to be ended before the partner LU can establish a connection with another generic resource member.
The affinity may be ended automatically by the connection quiesce transaction when the connection is released. However, it is not done if the system crashes or is shut down 'immediate' whilst the connection is still acquired.
CSNE
DFHZNAC
XMEOUT Parameters: date, time,applid, sysid, grname, netid, netname
An attempt was made to end an affinity between this CICS, which is a member of generic resource grname, and a remote LU with netid netid and netname netname using a SET CONNECTION ENDAFFINITY or PERFORM ENDAFFINITY command. The request has been rejected by VTAM.
VTAM has issued the return code-feedback (RTNCD,FDB2) X'rc',X'fd' in response to the CHANGE OPTCD=ENDAFFINITY macro.
Processing continues.
See the VTAM programming manual for the meaning of the RTNCD,FDB2 code and for guidance on correcting the problem.
When the problem has been corrected, retry the command if appropriate.
CSNE
DFHZGCH
XMEOUT Parameters: date, time,applid, grname, netid, netname, X'rc', X'fd'
A connection sysid from netname netname to generic resource grname has been established.
The message is issued once for each connection acquire.
Processing continues.
None.
CSNE
DFHZNAC
XMEOUT Parameters: date, time,applid, sysid, netname, grname, membername
VTAM has responded positively to an attempt to end an affinity with remote LU netid netid, netname netname. The affinity was ended implicitly by the connection quiesce transaction when the connection was released or explicitly by a SET CONNECTION ENDAFFINITY or PERFORM ENDAFFINITY command.
Processing continues. The remote LU can now establish a connection with a different generic resource member.
None.
CSNE
DFHZGCH
XMEOUT Parameters: date, time,applid, grname, netid, netname
An unsuccessful attempt was made to end an affinity between this CICS, which is a member of generic resource grname, and a remote LU with netid netid and netname netname using a SET CONNECTION ENDAFFINITY or PERFORM ENDAFFINITY command. VTAM has issued return code-feedback (RTNCD,FDB2) of X'14',X'88' in response to the CHANGE OPTCD=ENDAFFINITY macro indicating that no such affinity exists.
Processing continues.
Ensure that the values input to the SET CONNECTION ENDAFFINITY or PERFORM ENDAFFINITY command are correct.
CSNE
DFHZGCH
XMEOUT Parameters: date, time,applid, grname, netid, netname
CICS has attempted to determine the network qualified netname of logical unit luname. The attempt has failed because a problem with VTAM prevented the VTAM INQUIRE OPTCD=NQN macro from being issued.
VTAM has issued the return code-feedback (RTNCD,FDB2) X'rc',X'fd' in response to the INQUIRE OPTCD=NQN macro.
R15 r15 is the register 15 value returned by VTAM.
The CICS component which requires the network qualified netname of the logical unit determines whether any further action is called for.
See the VTAM Programming manual for the meaning of the RTNCD,FDB2 and for guidance on correcting the problem.
CSNE
DFHZGIN
XMEOUT Parameters: date, time,applid, luname, X'rc', X'fd', X'r15'
CICS has attempted to determine the network qualified name of logical unit luname. The request has been rejected by VTAM.
VTAM has issued the return code-feedback (RTNCD,FDB2) X'rc',X'fd' in response to the INQUIRE OPTCD=NQN macro.
The CICS component which requires the network qualified name of the logical unit decides whether further action is called for.
See the VTAM Programming manual for the meaning of the RTNCD,FDB2 code and for guidance on correcting the problem.
CSNE
DFHZGIN
XMEOUT Parameters: date, time,applid, luname, X'rc', X'fd'
CICS has attempted to determine the member of a generic resource set grname to which logical unit netid.luname is logged on. The attempt has failed because a problem with VTAM prevented the VTAM INQUIRE OPTCD=SESSNAME macro from being issued.
VTAM has issued the return code-feedback (RTNCD,FDB2) X'rc',X'fd' in response to the INQUIRE OPTCD=NQN macro.
R15 r15 is the register 15 value returned by VTAM.
The CICS component which needs to know where the logical unit is logged on determines whether any further action is called for.
See the VTAM Programming manual for the meaning of the RTNCD,FDB2 and for guidance on correcting the problem.
CSNE
DFHZGIN
XMEOUT Parameters: date, time,applid, grname, netid, luname, X'rc', X'fd', X'r15'
CICS has attempted to determine the member of generic resource set to which grname logical unit netid.luname is logged on. The request has been rejected by VTAM.
VTAM has issued the return code-feedback (RTNCD,FDB2) X'rc',X'fd' in response to the INQUIRE OPTCD=SESSNAME macro.
The CICS component which requires the member name decides whether further action is called for.
See the VTAM Programming manual for the meaning of the RTNCD,FDB2 code and for guidance on correcting the problem.
CSNE
DFHZGIN
XMEOUT Parameters: date, time,applid, grname, netid, luname, X'rc', X'fd'
Node nodeid attempted to log on to CICS but the logon is invalid.
The nodeid in the message always starts with the netname of the node attempting to connect to CICS. For some instances of the message resulting from an APPC log on, the modename of the session is concatenated to the netname with a dot separator. Since a string consisting of eight blanks is the default modename, this can lead to idiosyncratic formatting of the message.
If the message is issued by DFHZATA, CICS has failed in its attempt to autoinstall the terminal or connection.
The instance instance is one of the following:
The acquire of the connection continues.
Use the instance number to determine why the netname already exists:
Since this problem should not occur under normal circumstances, you may need further assistance from IBM.
CSNE
DFHZOPN, DFHZOPN
XMEOUT Parameters: date, time,applid, sysid, grname, netname, sense, instance, {1=DFHZOPN, 2=DFHZOPN}
CICS has failed to reset connection sysid after an affinity was ended successfully. A lock was held by task taskid, transaction tranid.
Processing continues but the state of the connection is undetermined. The lock on the connection should be released when task taskid ends.
If appropriate, use the information in the message to find out why there was a lock on the connection. If the connection is left in a state where it cannot be acquired, delete and reinstall it.
CSNE
DFHZGCH
XMEOUT Parameters:
date,
time,
applid,
sysid,
grname,
applid,
taskid,
tranid
This message is sent to a terminal when the associated VTAM session is successfully recovered following a persistent sessions restart of CICS.
This is the default message issued by CICS if RECOVNOTIFY(MESSAGE) is specified on the TYPETERM for a device (see the CICS Resource Definition Guide ), or in the node error program (see the CICS Customization Guide). If RECOVNOTIFY(MESSAGE) is used, it is recommended that the CICS supplied sample mapset DFHXMSG be tailored to meet the installation recovery requirements.
Processing continues.
Sign on if required, and take any recovery actions required.
Terminal End User
DFHZNAC
The COVR transaction has attempted an EXEC CICS SET VTAM OPEN, but the operation failed with the return code retcode from the OPEN ACB.
CICS continues. The COVR transaction retries the operation every 5 seconds. This message is reissued every minute until the operation succeeds, or until 10 minutes has passed, in which case message DFHZC0201 is issued.
Investigate the reason for VTAM being unavailable. See the VTAM Programming manual for an explanation of the ACB return code.
Console
DFHZCOVR
XMEOUT Parameters: applid, X'retcode'
The COVR transaction has repeatedly attempted an EXEC CICS SET VTAM OPEN, but the operations have failed. The OPEN ACB has issued the return code retcode.
CICS continues. The COVR transaction terminates and the SET VTAM OPEN is not retried.
Investigate the reason for VTAM being unavailable. See the VTAM Programming manual for an explanation of the ACB return code.
Console
DFHZCOVR
XMEOUT Parameters: applid, X'retcode'
Recovery manager was invoked during resynchronization of an LU6.1 session, but gave an unexpected response. This is due to an internal logic error.
A system dump is taken unless dumps have been specifically suppressed in the dump table.
You need further assistance from IBM to resolve this problem. See CICS Problem Determination Guide for guidance on how to proceed.
CSNE
DFHZNAC
XMEOUT Parameters: date, time,applid, termid, sysid
A SEND response issued on a receive-any RPL failed, or was not accepted by VTAM.
For the meaning of the sense data, see DFHZCxxxx messages.
If a task is attached, it is abnormally terminated with a transaction dump. Message DFHME0116 is normally produced containing the symptom string for this problem.
A subsequent message in the log indicates the reasons for the failure. Refer to this message for further information and guidance.
CSNE
DFHZRAC
XMEOUT Parameters: date, time,applid, termid, tranid, sense, instance, {1=DFHZRAC, 2=DFHZRAC}
CICS has issued a VTAM SEND macro to send a response but no notification has been received that the response has completed. Until this SEND operation completes, one of the limited number of receive-any RPLs remains unusable (the number of receive-any RPLs is defined by the RAPOOL system initialization parameter).
This is a serious condition. If all the receive-any RPLs become unusable in this way, CICS is unable to accept any new requests from VTAM. Similarly, a reduction in the number of available receive-any RPLs can adversely affect terminal performance and transaction throughput.
Additionally, while the RPL is hanging, a normal CICS shutdown might be unable to complete.
The CID is the 32-bit VTAM communication identifier which was assigned when the session was established.
CICS continues to monitor for the SEND operation to complete. Until this happens, CICS reissues this message at approximately three minute intervals.
This problem is usually caused by a failure in the network which stops the SEND completing. Check the session and the associated logical unit to ensure that there is no error condition which stops VTAM completing the SEND request.
Console
DFHZRAC
XMEOUT Parameters: applid, termid,netname, X'cid', instance, {1=DFHZRAC}
Resynchronization of an LU6.1 session with a remote system has failed to complete for one of the following reasons:
CSNE
DFHZRSY, DFHZSCX, DFHZSEX
XMEOUT Parameters: date, time,applid, termid, sysid
CICS has received data on a pipeline session which is larger than the initial I/O area allocated for the receive any RPL. The size of the receive any input area (RAIA) is specified on the RAMAX system initialization parameter.
CICS ends the session which sent the data and marks it out of service. CICS will also attempt to abnormally terminate any running transactions which were initiated from this session.
Increase the value of the RAMAX system initialization parameter so that it is at least equal to the largest RUSIZE (from the CINIT) specified for a pipeline session.
CSNE
DFHZRAC
XMEOUT Parameters:
date,
time,
applid,
termid,
tranid,
instance,
{1=DFHZRAC}
All the CICS Receive Any RPLs have been posted but the TCTTE for each one is waiting for a response from a VTAM terminal or session. All the Receive Any RPLs have been stalled for 10 dispatches of the TCP task (CSTP). This message is produced for each session that is in this situation. A VTAM session has not responded to a command such as BID or SHUTD sent by CICS. This is typically caused by a protocol error.
CICS is NOT running with system initialization parameter RAPOOL=(n,n,FORCE) so CICS VTAM activity is held up until one of the commands completes.
Issue the VTAM command V NET,INACT,ID=netname,I for one or more of the sessions indicated by netname, to try and free a Receive Any RPL. Note - if the sessions are LU6.2 then the above command will inactivate the partner APPLID to VTAM.
Investigate why the CICS terminal control commands that have caused the stall have not completed. If this is due to a protocol error from the partner or device, attempt to get the protocol error corrected.
Consider increasing the number of Receive Any RPLs specified in the RAPOOL System Initialization parameter. For instance, if you were using the old default of 2, increase this to the new default of 50.
If you still get this message after changing the RAPOOL value consider running CICS with system initialization parameter RAPOOL=(n,n,FORCE), which attempts to issue CLSDST for all the offending sessions or terminals and to re-issue the Receive Any RPLs.
Console
DFHZRAC
XMEOUT Parameters: applid, netname
CICS has received data on a pipeline session that violates the pipeline protocol. An LUSTAT SENSE 08310000 'Device Powered Off' was received from the device requesting a definite response, but only EXC responses are allowed.
CICS ends the session that sent the data and marks it out of service. CICS also attempts to abnormally terminate any running transactions initiated from this session.
Determine why the pool pipeline terminal is violating the protocol.
CSNE
DFHZRAC
XMEOUT Parameters: date, time,applid, termid, tranid, instance, {1=DFHZRAC}
The XZIQUE global user exit program has been invoked by CICS because
of a potential problem with the connection. The global user exit has used
return code UERCAKLL indicating that throughput on the connection is abnormally
low and some exceptional action is required. The poor performance of the connection
can be caused by:
The condition may be intermittent. Message DFHZC2301 may follow indicating
that the connection has recovered.
This message may also occur when the XZIQUE global user exit
is disabled but the connection has been at the QUEUELIMIT for MAXQTIME where
both parameters are specified in the connection definition.
CICS cancels all transactions which have outstanding queued requests to use the connection.
Investigate the cause of the poor performance of the connection. Check the availability and condition of the connected system.
Console
DFHZISP
XMEOUT Parameters: applid, sysid
Message DFHZC2300 has been issued for this connection. The connection has now recovered and is operating normally.
Processing continues.
None
Console
DFHZISP
XMEOUT Parameters: applid, sysid
CICS issues the SETLOGON START command after a successful OPEN VTAM ACB. The SETLOGON START command is rejected in the following cases:
If the error occurs during CICS initialization, CICS abnormally terminates with a U2302 abend and a system dump.
If the error occurs as a result of a CEMT or EXEC CICS SET VTAM OPEN, CICS terminates the task abnormally with abend code ATC2 and a transaction dump, and the VTAM ACB is closed.
The VTAM return code can be found in RTNCD-FDBK2 in the first RPL in the RA pool addressed from TCTVRVRA in the system dump or the transaction dump.
Use the VTAM Programming manual, (SC23-0115-3), to determine the cause of the error and the actions necessary to correct it.
After correcting the error, either reinitialize CICS (for abend U2302) or follow the suggestions documented for abend ATC2.
Console
DFHZSLS
XMEOUT Parameter: applid
While trying to acquire receive-any I/O areas, the SETLOGON START VTAM command found that storage was not available.
CICS terminates with a dump. An exception entry code is made in the trace table.
A system dump is taken unless dumps have been specifically suppressed in the dump table.
Message DFHZC0133 is issued.
Reduce the size of the RAMAX value in the system initialization table (SIT).
For further information, see the CICS Performance Guide.
Console
DFHZGRP
XMEOUT Parameters: applid, X'code'
This message is issued when the ACB has been opened either during initialization or dynamic open. DFHZGRP was initiating the VTAM RECEIVE-ANY's but VTAM was short on storage or the VTAM HALT QUICK command was issued.
An exception entry code is made in the trace table.
A system dump is taken unless you have specifically suppressed dumps in the dump table.
If the error occurs during CICS initialization, CICS issues message DFHZC0133 and terminates.
If the error occurs as a result of a CEMT or EXEC CICS SET VTAM OPEN, CICS closes the VTAM ACB.
The VTAM return code can be found in RTNCD-FDBK2 in the RPL, which is either in the exception trace entry code, or in the RA pool addressed from TCTVRVRA in the system dump.
Use the VTAM Programming manual, (SC31-6436), to determine the cause of the error and the actions necessary to correct it.
After correcting the error, either reinitialize CICS or reopen the VTAM ACB.
Console
DFHZGRP
XMEOUT Parameters: applid, X'code'
Either CICS or VTAM is being terminated, or a dynamic close of the VTAM ACB has been requested.
All CICS-VTAM sessions are closed and the ACB is closed. If termination is not orderly, active transactions are abnormally terminated.
When VTAM is active, communication may be resumed by using the master terminal operator command CEMT SET VTAM OPEN.
Console
DFHZSHU
XMEOUT Parameter: applid
An RPL request has completed without a TCTTE token, for other than a VTAM storage shortage.
CICS performs a FORCECLOSE of the ACB.
CICS may produce this message twice as both module DFHZRAC and module DFHZSYX may detect the condition.
When VTAM has been restarted, issue a CEMT SET VTAM OPEN.
Console
DFHZRAC, DFHZSYX
The TCP task wait has failed.
The TCP dispatcher module, DFHZDSP, has received an unexpected
response, with response code X'xx' and reason code X'yy'
from the DSSR WAIT_OLDW call.
CICS abends with abend U1800 and a system dump is produced.
Determine the cause of the TCP task wait failure. Investigate the dump in conjunction with any other accompanying error messages or exception trace entries which may have been issued by dispatcher domain.
Console
DFHZDSP
XMEOUT Parameters: applid, X'xx',X'yy'
The XZIQUE global user exit program has been invoked by CICS because of a potential problem with the connection. The global user exit has used return code UERCAKLM indicating that throughput on the connection is abnormally low and some exceptional action is required. The poor performance of the connection can be caused by:
The condition may be intermittent. Message DFHZC2310 may follow indicating that the mode group has recovered.
CICS cancels all transactions which have outstanding queued requests to use this mode group.
Investigate the cause of the poor performance of the mode group. Check the availability and condition of the connected system.
Console
DFHZISP
XMEOUT Parameters: applid, sysid,modename
Message DFHZC2309 has been issued for this mode group. The mode group has now recovered and is operating normally.
Processing continues.
None
Console
DFHZISP
XMEOUT Parameters: applid, sysid,modename
This is the CICS default good morning message for VTAM LUs. It is displayed unless an alternative GMTEXT has been specified as a system initialization parameter, or the typeterm definition logon message (LOGONMSG) has been set to NO.
Processing continues.
None.
Terminal End User
DFHSIT
CICS and VTAM have been disconnected. This may be because:
SET VTAM {CLOSED|IMMCLOSE|FORCECLOSE}
The VTAM ACB is closed.
If VTAM has not terminated, connection with VTAM can be reestablished by using master terminal operator commands.
Console
DFHZSHU
XMEOUT Parameter: applid
While opening the VTAM ACB, CICS found that no installed program definition exists for the autoinstall user-program progname specified in the SIT.
Other processing continues.
If you want to use autoinstall, produce an installed program definition for the autoinstall user-program progname specified in the SIT.
Console
DFHSIJ1, DFHZOPA
XMEOUT Parameters: applid, progname, modname
The VTAM ACB CLOSE request failed.
CICS continues as if the ACB is closed. (It is not really closed.)
Refer to the VTAM Programming manual for an explanation of the return and error codes.
The return code xx is the VTAM return code in Register 15. The error code yy is the ACB error flag ‘ACBERFLG’.
Console
DFHZSHU
XMEOUT Parameters: applid, xx,yy
A DFHTC CTYPE=LOCATE macro has returned an error indication while shutting down VTAM. This implies that the TCTTE chain has been corrupted, possibly by an overlay of the table manager control blocks.
CICS is abnormally terminated with a system dump.
Investigate the dump to determine the cause of the problem.
Console
DFHZSHU
CICS' attempt to shut down the network has not been completed within the time period allowed. This time period, the terminal control shutdown wait threshold, is specified by the TCSWAIT system initialization parameter.
In the message, mm is the value of TCSWAIT, and sesslist is the VTAM network names of the first 10 (if there are that many) hung VTAM terminals.
CICS issues this message to both the CSNE transient data queue and the operating system console. This message is issued to the operating system console with an MVS write to operator (WTO) message descriptor code of 2. This means that the message is held by the operating system (that is, it does not roll off the screen) until the operator deletes it. For each hung VTAM session, message DFHZC2351 is also issued. DFHZC2351 gives further details of the session and is issued only to the CSNE transient data queue. CICS may attempt a FORCECLOSE on the session (see message DFHZC2351 for further details) but otherwise CICS terminal control shutdown continues as normal.
This message, DFHZC2350, is not processed by DFHZNAC (node abnormal condition program), so the condition cannot be intercepted by the installation’s DFHZNEP (node error program). Note however that DFHZC2351 is processed by DFHZNAC and may be intercepted by the installation’s DFHZNEP.
Note the message, then delete it from the operating system console using the MVS CONTROL E (or K E) system command. See message DFHZC2351 for further guidance.
Console and Transient Data Queue CSNE
DFHZSHU
XMEOUT Parameters: date, time,applid, mm, sesslist, instance, {1=DFHZSHU}
CICS' attempt to shut down the network has not been completed within the time period allowed. The time period, the terminal control shutdown wait threshold, is specified by the TCSWAIT system initialization parameter. This message is issued for each VTAM terminal that is still active (not shut down) after the time period has expired.
In the message termid and netname are respectively, the CICS terminal identifier, and the VTAM network name of the hung terminal. One of the following is also included in the message to indicate the reason for the hang:
CICS may attempt a FORCECLOSE on the session but otherwise CICS terminal control shutdown continues normally. Whether CICS attempts a FORCECLOSE depends upon:
If either of the following conditions is true:
CICS terminal control issues a VTAM CLSDST and sends an SNA UNBIND command. If neither of the conditions is true, no special action is taken.
The first 10 terminals (if there are that many) reported by this message are also included in message DFHZC2350.
Check the state of the terminal. Check whether the associated DFHZC3437 message includes CLSDST. If DFHZC3437 does not include CLSDST, or it does but the CLSDST still fails to complete, take appropriate action outside of CICS to shut down the terminal.
If after a reasonable interval, terminal control shutdown still fails to complete (message DFHZC2316 is not displayed), take one of the following actions:
Warning: Do not perform one of these actions unless there are no other suitable actions to take.
The reason why the terminal does not shutdown is more likely to be a problem with the terminal device or the network, than with CICS.
If messages DFHZC2350, DFHZC2351, and DFHZC2352 are issued too early or too late in the shutdown process, take appropriate steps to change the TCSWAIT system initialization parameter on future runs of CICS. Once CICS has initialized, TCSWAIT cannot be changed.
CSNE
DFHZSHU
XMEOUT Parameters: date, time,applid, termid, netname, {1=01 Request in progress, 2=02 Task still active, 3=03 Waiting for SHUTC, 4=04 Waiting for BIS,5=05 Waiting for UNBIND, 6=06 Waiting for RTR, 7=07 BID in progress, 8=08 Other TC work pending,99=99 Undetermined}, sense, instance, {1=DFHZSHU}
CICS' attempt to shut down the network has not been completed within the time period allowed. The time period, the terminal control shutdown wait threshold, is specified by the TCSWAIT system initialization parameter. This message is issued for the first VTAM intersystem parallel session in each connection ( LU Type 6.1 and LU Type 6.2, but not LU Type 6.2 single-session APPC terminals) that is still active (not shut down) after the time period has expired.
In the message sysid and netname are respectively, the CICS system identifier and the VTAM network name.
If the TCSACTN=FORCE system initialization parameter has been
specified CICS will attempt to force close the CICS VTAM ACB, provided that
CNOS close processing has completed for LU Type 6.2 parallel session connections,
otherwise CICS terminal control shutdown continues as normal. This message
is not processed by DFHZNAC (node abnormal condition program), so the condition
cannot be intercepted by the installation’s DFHZNEP (node error program).
Parallel connections reported by this message are not included in message
DFHZC2350.
If the TCSACTN=FORCE system initialization parameter has not
been specified, or has been specified but the VTAM ACB still does not close,
check the state of the connection. Take appropriate action outside of this
CICS system to shut down the connection.
If messages DFHZC2350, DFHZC2351, and DFHZC2352 are issued too early or too late in the shutdown process, take appropriate steps to change the TCSWAIT system initialization parameter on future runs of CICS. Once CICS has initialized TCSWAIT cannot be changed.
Console and Transient Data Queue CSNE
DFHZSHU
XMEOUT Parameters: date, time,applid, sysid, netname, instance, {1=DFHZSHU}
CICS received an unexpected error code from VTAM.
For the meaning of the sense data, see DFHZCxxxx messages.
CICS terminates the session. If a task is attached, it is abnormally terminated with a transaction dump.
Message DFHME0116 is normally produced containing the symptom string for this problem.
Use the symptom string, and if necessary the transaction dump, to determine the source of the error.
CSNE
DFHZSYX
XMEOUT Parameters: date, time,applid, termid, tranid, sense, instance, {1=DFHZSYX, 2=DFHZSYX, 3=DFHZSYX, 4=DFHZSYX, 5=DFHZSYX, 6=DFHZSYX, 7=DFHZSYX, 8=DFHZSYX, 9=DFHZSYX, 10=DFHZSYX}
CICS attempted to request VTAM services using a request parameter list (RPL) that is currently active.
For the meaning of the sense data, see DFHZCxxxx messages.
CICS terminates the session. If a task is attached, it is abnormally terminated with a transaction dump.
Message DFHME0116 is normally produced containing the symptom string for this problem.
Use the symptom string, and if necessary, the transaction dump to determine the source of the error.
CSNE
DFHZRVS, DFHZSDA, DFHZSDR, DFHZSDS, DFHZSES, DFHZSDL, DFHZRVL, DFHZSKR
XMEOUT Parameters: date, time,applid, termid, tranid, sense, instance, {1=DFHZRVS, 2=DFHZSDA, 3=DFHZSDL, 4=DFHZSDS, 5=DFHZSES, 6=DFHZSKR, 7=DFHZRVL, 8=DFHZSDR, 9=DFHZRVL, 10=DFHZRVL, 11=DFHZRVL, 12=DFHZSDL}
VTAM has indicated that a synchronous receive issued by DFHZRAS during receive-any slow-down processing did not complete successfully. This indicates a serious mismatch between CICS's view of the state of the session and that of VTAM.
For the meaning of the sense data, see DFHZCxxxx messages.
The request is ignored. CICS prints the associated session TCTTE on the CSNE transient data destination. The RPL returned by VTAM is included in exception trace entry AP FCA2.
Determine from the RPL in the exception trace why VTAM raised the error.
CSNE
DFHZRAS
XMEOUT Parameters: date, time,applid, termid, tranid, netname, sense, instance, {1=DFHZRAS}
An attempt to establish a session has failed. This could be because a physical path to the device could not be found, because the device does not exist or has been defined incorrectly, or because the device has rejected the bind.
For the meaning of the sense data, see DFHZCxxxx messages.
If this is an LU62 or LU61 session and the partner LU has sent sense bytes of X'0835oooo' and oooo is the offset of the NETNAME in the BIND, this indicates that the partner LU was unable to find a suitable session.
If the sense bytes are X'08010000', this may mean that the partner LU has failed to autoinstall a connection.
If the VTAM RETURN CODE FEEDBACK is X'1018' then Generic Resourc is in use but the coupling facility is unavailable.
Instance 1 with sense code '0805' - If this system (TOR2) is a member of a generic resource (GR) and the partner (AOR) is not and an affinity already exists between another member (TOR1) of the same generic resource (GR) and the AOR then this indicates that it is not valid to acquire this connection. This message is normally accompanied by DFHZC2411 instance 36 for the equivalent sessions in the AOR. The DFHZC2411 message is saying that the AOR cannot find a connection defined with the real name of TOR2. The AOR connection is defined with the Generic Resource name of the TOR.
Because communication cannot be established with a node, a VTAM CLSDST macro is issued to release any control blocks previously built, and the node could be placed out of service.
Use the VTAM sense code given in the message to determine the cause of failure. If appropriate, ensure that the node name was included in the network control program/virtual storage (NCP/VS) generation deck and investigate for a possible bad communication line.
If the sense bytes were X'0835oooo' (where oooo is the offset of the NETNAME in the BIND), the partner LU has been unable to find a suitable session. If the partner LU is CICS, look in the partner LU's log for DFHZC2411 and previous messages for the same session. This should give some indication as to why no session could be found.
If LU62 autoinstall is in use and the sense bytes were X'08010000' look in the partner LU's log for message DFHZC2411 and message DFHZC69xx which should indicate the reason for failure to autoinstall a connection.
If the VTAM RETURN CODE FEEDBACK is X'1018': the logon can be retried once the coupling facility becomes available.
Instance 1 sense X'0805' - Determine if TOR2 was started intentionally with a different APPLID and the same Generic Resource name and if not, correct the problem. If it was and you need a connection between these two systems then you need to end the affinity between AOR and TOR1. The affinity can be ended by:
However, if the AOR is within the same sysplex as the TOR you should be using MRO connections rather than APPC - you then get no problems with affinities.
If the AOR is outside the sysplex and the connection is acquired from the TOR then you need to use a HUB as described in 'Using a HUB' in the CICS Intercommunication Guide to prevent two TORs from attempting to connect to one AOR using the generic resource name.
Alternatively you can change the AOR connection to address TOR2 by its real name as opposed to its generic resource name and always acquire the connection from the AOR. This implies that you must not use AUTOCONNECT in the TOR connection.
You should release the connection as soon as possible.
CSNE
DFHZSYX
XMEOUT Parameters: date, time,applid, termid, tranid, sense, instance, {1=DFHZSYX, 2=DFHZSYX}
VTAM detected an error in a request. The request was either incomplete or not executable.
For the meaning of the sense data, see DFHZCxxxx messages.
CICS breaks communication with the node (CLSDST), abnormally terminates any attached task, places the node out of service and produces a transaction dump.
Message DFHME0116 is normally produced containing the symptom string for this problem.
Ensure that all application programs running concurrently have proper addressability, thereby avoiding alteration of CICS control blocks such as the TCTTE or the RPL. If this message occurs during normal system execution, you will need further assistance from IBM. See CICS Problem Determination Guide for guidance on how to proceed.
This message may also occur if VTAM is terminating. Under these conditions it is not a serious problem, and usually no response is necessary.
CSNE
DFHZLEX
XMEOUT Parameters: date, time,applid, termid, tranid, sense, instance, {1=DFHZLEX, 2=DFHZLEX, 3=DFHZLEX, 4=DFHZLEX, 5=DFHZLEX, 6=DFHZLEX}
The node was not activated, or was deactivated by the network operator, or a generic resource affinity already exists with another system in the same generic resource.
Instance 6 - If the partner is a member of a generic resource (TOR2) and this system (AOR) is not and an affinity already exists between the AOR and another member of the same generic resource (TOR1) because TOR1 crashed, then VTAM has indicated that you cannot acquire this connection.
For the meaning of the sense data, see DFHZCxxxx messages.
All outstanding SEND and RECEIVE requests are purged. If a task is attached, it is abnormally terminated with a transaction dump. A VTAM CLSDST macro is issued to halt communication with the node, and internal LOGONs are prevented.
If this message is issued during takeover, the acquire is retried at intervals of 1, 2, 4 and 8 minutes after the first attempt. This allows time for sessions which require manual intervention before the acquire can succeed.
Use the VTAM VARY command to activate the node before using it in the network. Alternatively, for ISC with IMS, enable IMS for LOGONs.
It is possible that the node in question has previously been used as a generic APPLID (or in VTAM terms - a USERVAR). Use the VTAM operator command DISPLAY USERVAR to see if this is the case. If it is, you can use MODIFY USERVAR,OPTION=DELETE,ID=node to delete the USERVAR.
Instance 6 - Determine if TOR2 was started intentionally with a different APPLID and the same GR name and if not, correct the problem. If it was and you need a connection between these two systems then you need to end the affinity between the AOR and TOR1. The affinity can be ended by:
However, if the AOR is within the same sysplex as the TOR you should be using MRO connections rather than APPC - you then get no problems with affinities.
If the AOR is outside the sysplex and the connection is acquired from the TOR then you need to use a HUB as described in 'Using a HUB' in the CICS Intercommunication Guide to prevent two TORs from attempting to connect to one AOR using the generic resource name.
Alternatively you can change the AOR connection to address TOR2 by its real name as opposed to its generic resource name and always acquire the connection from the AOR. This implies that you must not use AUTOCONNECT in the TOR2 connection.
CSNE
DFHZSYX, DFHZSIX, DFHZSIM
XMEOUT Parameters: date, time,applid, termid, tranid, netname, sense, instance, {1=DFHZSIM, 2=DFHZSIM, 3=DFHZSIM, 4=DFHZSIM, 5=DFHZSIM, 6=DFHZSYX, 7=DFHZSYX, 8=DFHZSYX, 9=DFHZSIX, 10=DFHZSYX, 11=DFHZSYX}
The logical unit (LU) has requested termination of the session.
For the meaning of the sense data, see DFHZCxxxx messages.
The VTAM CLSDST macro is issued to stop communications with the node. If a task is attached, it is abnormally terminated with a transaction dump.
None.
CSNE
DFHZSYX
XMEOUT Parameters: date, time,applid, termid, tranid, sense, instance, {1=DFHZSYX}
Network Control Program/Virtual Storage (NCP/VS) was either shut down by the network operator or was abnormally terminated. Alternatively, there could have been a channel failure.
For the meaning of the sense data, see DFHZCxxxx messages.
Since communication with the logical unit was broken, the VTAM CLSDST macro instruction is issued to release control blocks previously built by VTAM. If a task is attached, it is abnormally terminated with a transaction dump.
Use the supplied dump to check for a possible NCP/VS or channel problem.
CSNE
DFHZSYX
XMEOUT Parameters: date, time,applid, termid, tranid, sense, instance, {1=DFHZSYX, 2=DFHZSYX}
VTAM encountered an error during its own processing.
For the meaning of the sense data, see DFHZCxxxx messages.
If a task is attached, it is abnormally terminated with a transaction dump. The node is placed out of service.
Message DFHME0116 is normally produced containing the symptom string for this problem.
Use the sense data to determine the nature of the error.
CSNE
DFHZSYX
XMEOUT Parameters: date, time,applid, termid, tranid, sense, instance, {1=DFHZSYX, 2=DFHZSYX, 3=DFHZSYX, 4=DFHZSYX}
VTAM successfully reestablished communication with a node. The reason for entering the LOSTERM exit is given by xx, which has one of the following values:
For the meaning of the sense data, see DFHZCxxxx messages.
CICS reestablishes communication and places the node in service.
None.
CSNE
DFHZLTX
XMEOUT Parameters: date, time,applid, termid, tranid, X'xx', sense, instance, {1=DFHZLTX, 2=DFHZLTX}
Communication with a node was interrupted and cannot be reestablished by VTAM. The reason for entering the LOSTERM exit is given by the error code X'xx'.
For the meaning of the sense data, see DFHZCxxxx messages.
The VTAM CLSDST macro is issued to release any control blocks previously built for the node. If a task is attached, it is abnormally terminated with a transaction dump.
See the appropriate VTAM Programming manual for an explanation of the error code.
CSNE
DFHZLTX
XMEOUT Parameters: date, time,applid, termid, tranid, X'xx', sense, instance, {1=DFHZLTX, 2=DFHZLTX, 3=DFHZLTX, 4=DFHZLTX}
Node nodeid attempted to log on to CICS but the logon is invalid.
The nodeid in the message will always start with the ‘netname’ of the node attempting to connect to CICS. For some instances of the message resulting from an LU6.2 log on, the modename of the session will be concatenated to the ‘netname’ with a dot separator. Since a string consisting of eight blanks is the default modename, this can lead to idiosyncratic formatting of the message.
If the message is issued by DFHZATA, CICS has failed in its attempt to autoinstall the terminal or connection.
The instance instance is one of the following:
If both CICS systems are registered as different generic resources, the LU61 connections must be defined with each other’s generic resource netnames; they cannot communicate by member name. In this case CICS looked for the generic resource netname and was unable to find it.
Change the partner’s connection definition for this system to use a NETNAME of this system’s generic resource name.
Change the partner’s connection definition for this system to use a NETNAME of this system’s generic resource name.
Change the partner’s connection definition for this system to use a NETNAME of this system’s member name.
Change the partner’s connection definition for this system to use a NETNAME of this system’s member name.
This instance also indicates
that you should not acquire this connection if the partner is
a member of a generic resource, and this system is not, and an affinity already
exists between this system and another member of the same generic resource.
See message DFHZC2403, which is issued for the partner's equivalent sessions,
for how you correct the situation.
This can be caused by a VTAM LU definition
with a duplicate netname. At session initiation time VTAM cannot detect that
there may be two Independant Logical Units (ILUs) with the same netname.
This can lead to CICS being requested to bind more sessions than specified
in the mode group.
For the meaning of the sense data, see DFHZCxxxx messages.
If ???????? is displayed in the second half of the nodeid field, the BIND may contain a SESSION QUALIFIER or MODENAME with an invalid length.
The logon is rejected. If the reject is from DFHZSCX via the dummy TCTTE, an attempt is made to print the failing BIND and sense code with which it was rejected as part of the message.
Use the instance number to determine why the attempted logon has been rejected and take the appropriate action.
CSNE
DFHZLGX, DFHZSCX, DFHZATA, DFHZBLX
XMEOUT Parameters: date, time,applid, termid, tranid, nodeid, sense, instance, {1=DFHZSCX, 2=DFHZBLX, 3=DFHZBLX, 4=DFHZBLX, 5=DFHZBLX, 6=DFHZBLX, 7=DFHZATA, 8=DFHZLGX, 9=DFHZLGX, 10=DFHZLGX, 11=DFHZSCX, 12=RESERVE, 13=DFHZLGX, 14=DFHZLGX, 15=DFHZLGX, 16=DFHZLGX, 17=DFHZLGX, 18=DFHZLGX, 19=DFHZLGX, 20=DFHZLGX, 21=DFHTFP, 22=DFHZLGX, 23=DFHZSCX, 24=DFHZLGX, 25=DFHZLGX, 26=DFHZSCX, 27=DFHZLGX, 28=DFHZBLX, 29=DFHZBLX, 30=DFHZBLX, 31=DFHZBLX, 32=DFHZBLX, 33=DFHZBLX, 34=DFHZBLX, 35=DFHZBLX, 36=DFHZBLX, 37=DFHZBLX, 38=DFHZLGX, 39=DFHZBLX, 40=DFHZSCX,41=DFHZBLX}
A receive-any request to VTAM failed. VTAM was terminated.
For the meaning of the sense data, see DFHZCxxxx messages.
The VTAM RPL control block is logged to the CSMT log for visual inspection.
Message DFHME0116 is normally produced containing the symptom string for this problem.
Determine the reason why the receive-any failed. First, check to see if the VTAM RPL has been altered. If it has been altered, check to see if the alterations could have caused any problems. Correct any obvious errors. It may be useful to refer to the VTAM Programming manual, (SC23-0115), during problem determination.
CSNE
DFHZRAC
XMEOUT Parameters: date, time,applid, termid, tranid, sense, instance, {1=DFHZRAC, 2=DFHZRAC}
A CLSDST request for the node identified by nodeid failed. VTAM may not have sufficient space to respond to the request.
For the meaning of the sense data, see DFHZCxxxx messages.
No further communication with the node is initiated.
Inspect the CSNE, CSMT and CSTL logs for indication of a VTAM storage problem or error message. Also check for any messages indicating an I/O problem.
CSNE
DFHTFP, DFHZATA, DFHZLGX
XMEOUT Parameters: date, time,applid, termid, tranid, nodeid, sense, instance, {1=DFHZATA, 2=DFHZLGX, 3=DFHTFP}
Temporary VTAM storage problem. VTAM is currently short of storage.
For the meaning of the sense data, see DFHZCxxxx messages.
The failing VTAM request is retried until VTAM is able to accept it.
Increase the VTAM working buffer storage if this condition recurs and causes undue problems.
CSNE
DFHZSYX
XMEOUT Parameters: date, time,applid, termid, tranid, sense, instance, {1=DFHZSYX}
A node error condition has occurred on node nodeid.
For the meaning of the sense data, see DFHZCxxxx messages.
CICS places the node out of service.
Use the sense data to determine the nature of the error.
CSNE
DFHZNAC
XMEOUT Parameters: date, time,applid, termid, tranid, netname, sense, instance, {1=DFHZNAC}
A VTAM HALT command was entered by the network operator while a SIMLOGON or OPNDST request was in progress. The instance number indicates what type of halt was requested:
For the meaning of the sense data, see DFHZCxxxx messages.
The VTAM network is quiesced to prevent further requests and the node is placed out of service.
None.
CSNE
DFHZSYX
XMEOUT Parameters: date, time,applid, termid, tranid, sense, instance, {1=DFHZSYX, 2=DFHZSYX}
Either CICS has not opened its VTAM ACB or VTAM has halted.
For the meaning of the sense data, see DFHZCxxxx messages.
The VTAM network is quiesced to prevent further requests and a dump is produced.
If VTAM was not halted by the network operator, use the supplied dump to determine the problem.
CSNE
DFHZSYX, DFHZCLS, DFHZCLX, DFHZOPN, DFHZOPX, DFHZRAC, DFHZRLP, DFHZRST, DFHZRVL, DFHZRVS, DFHZRVX, DFHZSDL, DFHZSDR, DFHZSDS, DFHZSES, DFHZSIM, DFHZSIX, DFHZSKR, DFHZSLX, DFHZTAX, DFHZSDA
XMEOUT Parameters: date, time,applid, termid, tranid, sense, instance, {1=DFHZOPX, 2=DFHZCLS, 3=DFHZOPN, 4=DFHZRLP, 5=DFHZRST, 6=DFHZRVS, 7=DFHZRVX, 8=DFHZSDA, 9=DFHZSDL, 10=DFHZSDS, 11=DFHZSES, 12=DFHZSIM, 13=DFHZSKR, 14=DFHZSLX, 15=DFHZRAC, 16=DFHZCLX, 17=DFHZRVL, 18=DFHZSDR, 19=DFHZSIX, 20=DFHZTAX, 21=DFHZOPX, 22=DFHZSYX}
An unknown command was detected in the VTAM request parameter list (RPL) by the CICS SESSIONC exit routine. The RPL address could be invalid or the RPL could have been altered.
For the meaning of the sense data, see DFHZCxxxx messages.
All outstanding send and receive requests are purged. If a task is attached, it is abnormally terminated with a transaction dump.
Message DFHME0116 is normally produced containing the symptom string for this problem.
A CLSDST is issued to halt communication with the node, and the node is placed out of service.
First, check if the VTAM RPL has an invalid address. If the address is valid, check to see if the RPL has been altered. If it has been altered, check to see if the alterations could have caused any problems. Correct any obvious errors. It may be useful to refer to the VTAM Programming manual, (SC23-0115), while carrying out problem determination.
CSNE
DFHZSEX
XMEOUT Parameters: date, time,applid, termid, tranid, sense, instance, {1=DFHZSEX, 2=DFHZSEX}
An unknown command was detected in the request parameter list (RPL) by the send-data-flow synchronous exit routine. The RPL address could be invalid or the RPL could have been altered.
For the meaning of the sense data, see DFHZCxxxx messages.
All outstanding send and receive requests are purged. If a task is attached, it is abnormally terminated with a transaction dump.
Message DFHME0116 is normally produced containing the symptom string for this problem.
A VTAM CLSDST macro is issued to halt communication with the node, and the node is placed out of service.
In the first instance, check if the VTAM RPL has an invalid address. If the address is valid, check to see if the RPL has been altered. If it has been altered, check to see if the alterations could have caused any problems. Correct any obvious errors. It may be useful to refer to the VTAM Programming manual, (SC23-0115-3), while carrying out problem determination.
CSNE
DFHZSSX, DFHZSLX, DFHZRAC
XMEOUT Parameters: date, time,applid, termid, tranid, sense, instance, {1=DFHZSSX, 2=DFHZSLX, 3=DFHZRAC, 4=DFHZRAC, 5=DFHZRAC, 6=DFHZRAC, 7=DFHZRAC, 8=DFHZRAC}
An unknown command was detected in the request parameter list (RPL) by the send-data-flow asynchronous exit routine. The RPL address could be invalid or the RPL could have been altered.
For the meaning of the sense data, see DFHZCxxxx messages.
All outstanding send and receive requests are purged. If a task is attached, it is abnormally terminated with a transaction dump.
Message DFHME0116 is normally produced containing the symptom string for this problem.
A VTAM CLSDST macro is issued to halt communication with the node, and the node is placed out of service.
In the first instance, check if the VTAM RPL has an invalid address. If the address is valid, check to see if the RPL has been altered. If it has been altered, check to see if the alterations could have caused any problems. Correct any obvious errors. It may be useful to refer to the VTAM Programming manual, (SC23-0115), while carrying out problem determination.
CSNE
DFHZSAX
XMEOUT Parameters: date, time,applid, termid, tranid, sense, instance, {1=DFHZSAX}
An unknown command or request was detected, or the RPL contains logical unit (LU) status.
For the meaning of the sense data, see DFHZCxxxx messages.
If an invalid command or request was detected, all outstanding send and receive requests are purged. If a task is attached, it is abnormally terminated with a transaction dump. A VTAM CLSDST macro is issued to halt communication with the node.
For ISC sessions, this error may be caused by specifying incompatible session types at each node. (For example, SESSIONTYPE=SEND in one node and SESSIONTYPE=FASTRECV in the other node.)
If the RPL contains logical unit (LU) status, one of the following messages is issued: DFHZC2461, DFHZC2462, DFHZC2464, DFHZC2465, or DFHZC2466.
Message DFHME0116 is normally produced containing the symptom string for this problem.
An invalid command or request indicates inconsistencies or errors in the definitions of the named terminals/sessions in CICS, VTAM or the connected system for LU6 sessions. Ensure that these definitions are consistent and correct for the device or session characteristics.
CSNE
DFHZRAC, DFHZRVX, DFHZRLP
XMEOUT Parameters: date, time,applid, termid, tranid, sense, instance, {1=DFHZRLP, 2=DFHZRLP, 3=DFHZRVX, 4=DFHZRVX, 5=DFHZRAC, 6=DFHZRAC, 7=DFHZRAC, 8=DFHZRAC, 9=DFHZRAC}
During terminal processing, CICS detected an invalid internal state in DFHZCP.
Instance 1 of the message could be caused by a loss of data following a persistent sessions restart in a partner system. In this case, no logic error has occurred because any updates are backed out. This normally follows an AZCD for the same session and the message DFHZC0144 for the partner session.
For the meaning of the sense data, see DFHZCxxxx messages.
All outstanding send and receive requests are purged, and the task is abnormally terminated with a transaction dump. The node is placed out of service and the TCTTE, RPL, and action flags are logged to the CSMT destination for debugging purposes.
Message DFHME0116 is normally produced containing the symptom string for this problem.
Ensure that the application programs running concurrently do not alter the TCTTE. If the TCTTE is not being altered, use the dump to locate the source of the error.
It may be useful to examine the debugging data printed on the CSMT log for clues about what possibly went wrong.
CSNE
DFHZARL, DFHZDET, DFHZERH, DFHZEV1, DFHZEV2, DFHZOPN, DFHZRAC, DFHZRVS, DFHZSDS, DFHZSIM, DFHZSKR, DFHZSLX, DFHZNAC, DFHZSSX
XMEOUT Parameters: date, time,applid, termid, tranid, sense, instance, {1=DFHZDET, 2=DFHZSIM, 3=DFHZSIM, 4=DFHZERH, 5=DFHZERH, 6=DFHZERH, 7=DFHZERH, 8=DFHZERH, 9=DFHZERH, 10=DFHZERH, 11=DFHZERH, 12=DFHZERH, 13=DFHZERH, 14=DFHZNAC, 15=DFHZERH, 16=DFHZERH, 17=DFHZERH, 18=DFHZERH, 19=DFHZSDS, 20=DFHZEV1, 21=DFHZEV1, 22=DFHZOPN, 23=DFHZOPN, 24=DFHZRVS, 25=DFHZRVS, 26=DFHZSKR, 27=DFHZSSX, 28=DFHZSLX, 29=DFHZSLX, 30=DFHZRAC, 31=DFHZRAC, 32=DFHZRAC, 33=DFHZRAC, 34=DFHZRAC, 35=DFHZRAC, 36=DFHZRAC, 37=DFHZRAC, 38=DFHZRAC, 39=DFHZARL, 40=DFHZARL, 41=DFHZEV2, 42=DFHZEV2, 43=DFHZRAC, 44=DFHZRAC, 45=DFHZOPN}
A request to send data synchronously was incomplete. Possible reasons are as follows:
For the meaning of the sense data, see DFHZCxxxx messages.
All outstanding send and receive requests are purged. If a task is attached, it is abnormally terminated with a transaction dump. Communication with the node is terminated by issuing the VTAM CLSDST macro instruction.
For reasons 1 to 3 listed above, ensure that application programs running concurrently do not alter the TCTTE.
If you suspect a logic error (2), check that the VTAM RPL has not been corrupted. If you still cannot resolve the problem, you will need further assistance from IBM. See CICS Problem Determination Guide for guidance on how to proceed.
CSNE
DFHZSDS
XMEOUT Parameters: date, time,applid, termid, tranid, sense, instance, {1=DFHZSDS}
A SESSIONC request is incomplete or invalid. Possible reasons are as follows:
For the meaning of the sense data, see DFHZCxxxx messages.
All outstanding send and receive requests are purged. If a task is attached, it is abnormally terminated with a transaction dump.
Message DFHME0116 is normally produced containing the symptom string for this problem.
Communication with the node is terminated by issuing the VTAM CLSDST macro instruction.
Ensure that application programs running concurrently do not alter the TCTTE.
If the TCTTE is not altered, check for conditions 2 or 3.
CSNE
DFHZSES
XMEOUT Parameters: date, time,applid, termid, tranid, sense, instance, {1=DFHZSES, 2=DFHZSES, 3=RESERVE}
A request to send data asynchronously was incomplete or invalid. This condition can be caused by the TCTTE being altered.
For the meaning of the sense data, see DFHZCxxxx messages.
All outstanding send and receive requests are purged. If a task is attached, it is abnormally terminated with a transaction dump.
Message DFHME0116 is normally produced containing the symptom string for this problem.
Communication with the node is terminated by issuing the VTAM CLSDST macro instruction.
Check the TCTTE. Ensure that application programs running concurrently do not alter the TCTTE.
CSNE
DFHZSDA
XMEOUT Parameters: date, time,applid, termid, tranid, sense, instance, {1=DFHZSDA, 2=DFHZSDA}
Input was received from a node identified either as output-only or as permanently out of service.
For the meaning of the sense data, see DFHZCxxxx messages.
All outstanding send and receive requests are purged. If a task is attached, it is abnormally terminated with a transaction dump.
Change the terminal entry in the TCT to indicate that the node is not an output-only device. If the node is out of service, the master terminal operator should place the node back into service.
CSNE
DFHZATT
XMEOUT Parameters: date, time,applid, termid, tranid, sense, instance, {1=DFHZATT, 2=DFHZATT, 3=DFHZATT}
Network Control Program/Virtual Storage (NCP/VS) has been restarted after failing during an OPNDST.
For the meaning of the sense data, see DFHZCxxxx messages.
The OPNDST request is reissued.
None.
CSNE
DFHZSYX
XMEOUT Parameters: date, time,applid, termid, tranid, sense, instance, {1=DFHZSYX}
A send-synchronous request was issued without indicating that either a command or data was to be sent.
For the meaning of the sense data, see DFHZCxxxx messages.
All outstanding send and receive requests are purged. If a task is attached, it is abnormally terminated with a transaction dump.
Message DFHME0116 is normally produced containing the symptom string for this problem.
Check the VTAM RPL for obvious errors. Ensure that application programs running concurrently do not alter the TCTTE. If the TCTTE is not being altered, use the symptom string, and if necessary, the dump to determine the source of the error.
CSNE
DFHZSDS
XMEOUT Parameters: date, time,applid, termid, tranid, sense, instance, {1=DFHZSDS}
An invalid RESETSR request was made in the VTAM macro issued by CICS. The invalid request can be because an RTYPE was not specified or was incorrectly specified, or the TCTTE was altered.
For the meaning of the sense data, see DFHZCxxxx messages.
All outstanding receive requests are purged. If a task is attached, it is abnormally terminated with a transaction dump.
Message DFHME0116 is normally produced containing the symptom string for this problem.
Check the VTAM RPL for obvious errors. Ensure that application programs running concurrently do not alter the TCTTE. If the TCTTE is not being altered, use the symptom string, and if necessary the dump, to determine the source of the error.
CSNE
DFHZRST
XMEOUT Parameters: date, time,applid, termid, tranid, sense, instance, {1=DFHZRST, 2=DFHZRST, 3=DFHZRST}
A send-response request was invalid. Either the request did not specify the response level (DR1 or DR2), or the TCTTE was altered.
For the meaning of the sense data, see DFHZCxxxx messages.
All outstanding send requests are purged. If a task is attached, it is abnormally terminated with a transaction dump and the node is placed out of service.
Check the VTAM RPL for obvious errors. Ensure that application programs running concurrently do not alter the TCTTE. If the TCTTE is not being altered, use the dump to determine the source of the error.
CSNE
DFHZSDR
XMEOUT Parameters: date, time,applid, termid, tranid, sense, instance, {1=DFHZSDR}
CICS requested VTAM to perform a close destination for a node currently "owned" by CICS.
For the meaning of the sense data, see DFHZCxxxx messages.
If the CICS ACB is open, all outstanding requests are purged
and the task is abnormally terminated with a transaction dump if a task is
attached.
If the CICS ACB is open, use the dump to determine the source of the error. Check that the TCTTE is valid.
CSNE
DFHZSYX
XMEOUT Parameters: date, time,applid, termid, tranid, sense, instance, {1=DFHZSYX}
CICS has received an exception response.
For the meaning of the sense data, see DFHZCxxxx messages.
Another CICS message is issued in conjunction with this message.
Perform the action specified for the associated CICS message.
CSNE
DFHZRAC, DFHZRVX, DFHZSSX
XMEOUT Parameters: date, time,applid, termid, tranid, sense, instance, {1=DFHZRVX, 2=DFHZRVX, 3=DFHZRVX, 4=DFHZRVX, 5=DFHZRVX, 6=DFHZRVX, 7=DFHZRVX, 8=DFHZSSX, 9=DFHZSSX, 10=DFHZSSX, 11=DFHZSSX, 12=DFHZRAC, 13=DFHZRAC, 14=DFHZRAC, 15=DFHZRAC, 16=DFHZRAC, 17=DFHZRAC, 18=DFHZRAC, 19=DFHZRAC, 20=DFHZRAC, 21=DFHZRAC, 22=DFHZRAC, 23=DFHZRAC}
Node nodeid attempted to log on to CICS. The logon has failed because autoinstall is disabled. Possible reasons are:
The logon is rejected.
Ensure that the value for the AIQMAX system initialization parameter is greater than zero. If an autoinstall user program has been specified for system initialization parameter AIEXIT, check that the program name has been defined to CICS. See the CICS System Definition Guide for further information about autoinstall parameters.
If the system is short on storage, see the associated messages for further guidance.
CSNE
DFHZLGX, DFHZSCX, DFHZBLX
XMEOUT Parameters: date, time,applid, termid, tranid, nodeid, sense, instance, {1=DFHZLGX, 2=DFHZLGX, 3=DFHZBLX, 4=DFHZBLX}
A DFHTC TYPE=COPY request has been issued to a 3270 compatibility mode logical unit. The request is invalid because the 3270 COPY command is not supported by a 3270 compatibility mode logical unit.
For the meaning of the sense data, see DFHZCxxxx messages.
The task abends.
Change the application program to avoid issuing a COPY request.
CSNE
DFHZARQ
XMEOUT Parameters: date, time,applid, termid, tranid, sense, instance, {1=DFHZARQ}
CICS issued a receive-specific request VTAM without specifying a request parameter list (RPL). This condition could result from one of the following reasons:
For the meaning of the sense data, see DFHZCxxxx messages.
All outstanding receive requests are purged. If a task is attached, it is abnormally terminated with a transaction dump. A CLSDST macro is issued to terminate communication with the node.
Use the dump to determine whether the TCTTE was altered by an application program. If it was, correct the error. If the TCTTE has not been altered, check for potential RPL problems.
CSNE
DFHZRVS
XMEOUT Parameters: date, time,applid, termid, tranid, sense, instance, {1=DFHZRVS}
The TIOA was missing while a receive-specific request was being processed. This condition could result from the TIOA being freed or TCTTEDA being altered.
For the meaning of the sense data, see DFHZCxxxx messages.
All outstanding receive requests are purged. If a task is attached, it is abnormally terminated with a transaction dump.
Use the dump to determine if the TCTTE was altered by an application program.
CSNE
DFHZRVS, DFHZRVX
XMEOUT Parameters: date, time,applid, termid, tranid, sense, instance, {1=DFHZRVS, 2=DFHZRVX, 3=DFHZRVS}
An output request was issued to a VTAM terminal that is defined as an input-only device. Either the TCTTETS was altered or a task that was attached issued a send request.
For the meaning of the sense data, see DFHZCxxxx messages.
All outstanding send requests are purged. If a task is attached, it is abnormally terminated with a transaction dump. The terminal status remains unchanged.
Either ensure that the node is defined correctly in the TCTTE, or prevent the task from issuing an output request to the node.
CSNE
DFHZSDS
XMEOUT Parameters: date, time,applid, termid, tranid, sense, instance, {1=DFHZSDS}
An input request was issued to a VTAM terminal that is identified as an output-only device. Either the TCTTETS was altered or a task was attached that issued a read request.
For the meaning of the sense data, see DFHZCxxxx messages.
All outstanding receive requests are purged. If a task is attached, it is abnormally terminated with a transaction dump. The terminal status remains unchanged.
Either change the definition of the terminal in the TCTTE, or prevent the task from issuing input requests to the node.
CSNE
DFHZRVS, DFHZSDS
XMEOUT Parameters: date, time,applid, termid, tranid, sense, instance, {1=DFHZRVS, 2=DFHZSDS}
An invalid resume request was received. The CICS activate-scan function detected a resume request in a TCTTE, but the TCTTE was not part of any transaction.
For the meaning of the sense data, see DFHZCxxxx messages.
The TCTTE is printed and logged to the CSNE destination for debugging purposes.
Message DFHME0116 is normally produced containing the symptom string for this problem.
Use the symptom string to determine the cause of the problem. Check the TCTTE data printed and logged to the CSNE destination for obvious alterations and errors.
CSNE
DFHZACT
XMEOUT Parameters: date, time,applid, termid, tranid, sense, instance, {1=DFHZACT}
A VTAM logical unit has requested CICS to quiesce all I/O activity with that node.
For the meaning of the sense data, see DFHZCxxxx messages.
All data transmission to the node is halted until CICS receives a release-quiesce indicator.
None.
CSNE
DFHZASX
XMEOUT Parameters: date, time,applid, termid, tranid, sense, instance, {1=DFHZASX}
CICS received a release-quiesce indicator from a VTAM logical unit that had previously quiesced CICS.
For the meaning of the sense data, see DFHZCxxxx messages.
Data transmission to the node is resumed by CICS.
None.
CSNE
DFHZASX
XMEOUT Parameters: date, time,applid, termid, tranid, sense, instance, {1=DFHZASX}
An exception response was received when a definite response protocol was requested.
For the meaning of the sense data, see DFHZCxxxx messages.
CICS issues a second message in conjunction with this message that explains the reason for the exception response.
Perform the action specified for the second CICS message received.
CSNE
DFHZRVX
XMEOUT Parameters: date, time,applid, termid, tranid, sense, instance, {1=DFHZRVX, 2=DFHZRVX}
CICS received a request from an application program, when its node was either not in session or queued to be CLSDSTed.
For the meaning of the sense data, see DFHZCxxxx messages.
All outstanding requests are ignored. If a task is attached, it is abnormally terminated with a transaction dump.
None.
CSNE
DFHZSDS, DFHZRVL, DFHZRVS, DFHZSDL, DFHZSHU
XMEOUT Parameters: date, time,applid, termid, tranid, sense, instance, {1=DFHZRVS, 2=DFHZSDL, 3=DFHZSDS, 4=DFHZSDS, 5=DFHZSDS, 6=DFHZSHU, 7=DFHZSHU, 8=DFHZRVL, 9=DFHZSHU}
A CICS application program violated bracket protocol. It is possible that the application program issued an I/O request following a write (last) request.
For the meaning of the sense data, see DFHZCxxxx messages.
All outstanding send and receive requests are purged. If a task is attached, it is abnormally terminated with a transaction dump.
Correct the application program.
CSNE
DFHZRVS, DFHZSDS
XMEOUT Parameters: date, time,applid, termid, tranid, sense, instance, {1=DFHZRVS, 2=DFHZSDS}
The TIOA was not large enough to hold all the output data. The application program either set up the TIOA incorrectly or it overran the TIOA.
For the meaning of the sense data, see DFHZCxxxx messages.
All outstanding send requests are purged. If a task is attached, it is abnormally terminated with a transaction dump.
Correct the application program to acquire a larger TIOA.
CSNE
DFHZSDS
XMEOUT Parameters: date, time,applid, termid, tranid, sense, instance, {1=DFHZSDS, 2=DFHZSDS}
An invalid response was received for a bid request. A normal response was received in response to a bid indicator while the transaction was in bracket state. The controller application program is in error.
For the meaning of the sense data, see DFHZCxxxx messages.
All outstanding requests are purged. If a task is attached, it is abnormally terminated with a transaction dump. Communication with the node is terminated by issuing a VTAM CLSDST macro instruction, and the node is placed out of service.
Correct the controller application program to return an exception response to a bid indicator when in the bracket state, followed by a ready-to-receive indicator when ready to honor the bid.
CSNE
DFHZRAC, DFHZRVX, DFHZSSX
XMEOUT Parameters: date, time,applid, termid, tranid, sense, instance, {1=DFHZRVX, 2=DFHZSSX, 3=DFHZRAC}
A domain call failed and the response could not be handled by module modname because of a previous failure. The domain concerned should have issued a message to the console which gives further information about the failure.
For the meaning of the sense data, see DFHZCxxxx messages.
All outstanding send and receive requests for terminal termid are purged. If a task is attached, it is abnormally terminated with a transaction dump. Terminal termid is placed out of service and the TCTTE is logged to the CSNE destination.
Refer to the message issued by the domain that is in error. It indicates the source of the original error.
CSNE
DFHZRAC, DFHZRVS, DFHZSDA, DFHZOPN, DFHZFRE, DFHZRLP, DFHZACT, DFHZGET
XMEOUT Parameters: date, time,applid, termid, tranid, sense, instance, {1=DFHZOPN, 2=DFHZRVS, 3=DFHZSDA, 4=DFHZRAC, 5=DFHZRAC, 6=DFHZOPN, 7=DFHZOPN, 8=DFHZFRE, 9=DFHZRLP, 10=DFHZACT, 11=DFHZGET, 12=DFHZGET, 13=DFHZOPN}
An invalid response was requested. An application program transmitted data to CICS without requesting a response from CICS.
For the meaning of the sense data, see DFHZCxxxx messages.
All outstanding receive requests are purged. If a task is attached, it is abnormally terminated with a transaction dump. Communication with the node is terminated by issuing a VTAM CLSDST macro, and the node is placed out of service.
Correct the application program.
CSNE
DFHZRAC, DFHZRVX
XMEOUT Parameters: date, time,applid, termid, tranid, sense, instance, {1=DFHZRVX, 2=DFHZRAC, 3=DFHZRAC}
The application program either sent a begin-bracket indicator while the transaction was in bracket state, or sent an end-bracket indicator.
For the meaning of the sense data, see DFHZCxxxx messages.
If a task is attached, it is abnormally terminated with a transaction dump. Communication with the node is terminated by issuing the VTAM CLSDST macro, and the node is placed out of service.
Correct the application program.
CSNE
DFHZRAC, DFHZRVX
XMEOUT Parameters: date, time,applid, termid, tranid, sense, instance, {1=DFHZRVX, 2=DFHZRVX, 3=DFHZRAC, 4=DFHZRAC}
An automatic task initiation (ATI) request was issued without an ATI pending for that terminal.
For the meaning of the sense data, see DFHZCxxxx messages.
CICS will satisfy the BB pending condition by sending a standalone BB-EB.
If ATI is time-initiated, increase the timer value.
CSNE
DFHZRAC, DFHZRVX, DFHZSSX
XMEOUT Parameters: date, time,applid, termid, tranid, sense, instance, {1=DFHZRVX, 2=DFHZRVX, 3=DFHZRVX, 4=DFHZSSX, 5=DFHZSSX, 6=DFHZSSX, 7=DFHZRAC, 8=DFHZRAC, 9=DFHZRAC}
A request was outstanding when clear was issued. A receive-specific request was pending when a clear indicator was issued. A clear indicator is sent when any of the following occurs:
For the meaning of the sense data, see DFHZCxxxx messages.
All outstanding requests are purged. If a task is attached, it is abnormally terminated with a transaction dump.
None.
CSNE
DFHZSYX
XMEOUT Parameters: date, time,applid, termid, tranid, sense, instance, {1=DFHZSYX}
CICS received an invalid command (VTAM indicator). The CICS session-control input exit-routine (SCIP) encountered an indicator other than request-recovery. This routine should be scheduled only when a request-recovery indicator is received from the controller application program.
For the meaning of the sense data, see DFHZCxxxx messages.
If a task is attached, it is abnormally terminated with a transaction dump. The session is terminated and the node is placed out of service.
Check the VTAM RPL for obvious errors. Use the dump to help determine the source of the problem.
CSNE
DFHZSCX
XMEOUT Parameters: date, time,applid, termid, tranid, sense, instance, {1=DFHZSCX}
A request for recovery was received. The secondary logical unit requested message resynchronization by sending a request-recovery indicator, but a message sequence number is inconsistent with the sequence number maintained by the 3601 application program.
For the meaning of the sense data, see DFHZCxxxx messages.
All outstanding send and receive requests are purged. If a task is attached, it is abnormally terminated with a transaction dump. Message resynchronization is then initiated by CICS.
None.
CSNE
DFHZSCX
XMEOUT Parameters: date, time,applid, termid, tranid, sense, instance, {1=DFHZSCX}
An exception response was returned on a POST=RESP chain-data send. CICS normally does not send chained data using POST=RESP.
For the meaning of the sense data, see DFHZCxxxx messages.
All outstanding send and receive requests are purged. If a task is attached, it is abnormally terminated with a transaction dump.
Message DFHME0116 is normally produced containing the symptom string for this problem.
Use the symptom string, and if necessary the transaction dump, to determine the source of the error.
CSNE
DFHZSYX
XMEOUT Parameters: date, time,applid, termid, tranid, sense, instance, {1=DFHZSYX}
An attempt to attach a task to a logical unit (LU) was made, despite the task being in continue-any (CA) mode. However, terminal termid already had a task attached to it.
For the meaning of the sense data, see DFHZCxxxx messages.
The task that is already attached to terminal termid is abnormally terminated with a transaction dump.
Message DFHME0116 is normally produced containing the symptom string for this problem. Communication with the node is terminated by issuing the VTAM CLSDST macro. CICS then reestablishes communication with the node by issuing the SIMLOGON macro.
Use the symptom string, and if necessary the dump, to determine the source of the error. Try to determine why there was an attempt to attach a task to terminal termid while it already had a task attached to it.
CSNE
DFHZATT
XMEOUT Parameters: date, time,applid, termid, tranid, sense, instance, {1=DFHZATT}
CICS received an exception response to a command (VTAM indicator) that it sent to a logical unit.
For the meaning of the sense data, see DFHZCxxxx messages.
In conjunction with this message, CICS issues a second message that explains the reason for the exception response.
Perform the action specified in the second CICS message received.
CSNE
DFHZSYX, DFHZSSX
XMEOUT Parameters: date, time,applid, termid, tranid, sense, instance, {1=DFHZSYX, 2=DFHZSYX, 3=DFHZSYX, 4=DFHZRAC}
A node encountered consecutive errors. That is, the node abnormal condition program, NACP, encountered a second error while processing the first error.
For the meaning of the sense data, see DFHZCxxxx messages.
If a task is attached, it is abnormally terminated with a transaction dump. Communication with the node is terminated by issuing a VTAM CLSDST macro. The first error is accompanied by an error message.
Use the dump to determine the source of the errors. Refer to the error message produced by the first problem and to any VTAM messages that may have been issued.
CSNE
DFHZRAC, DFHZSYX, DFHZEMW
XMEOUT Parameters: date, time,applid, termid, tranid, sense, instance, {1=DFHZEMW, 2=DFHZSYX, 3=DFHZSYX, 4=DFHZRAC, 5=DFHZRAC}
CICS received an exception response to a send for which an exception response was requested.
For the meaning of the sense data, see DFHZCxxxx messages.
In conjunction with this message, CICS issues a second message that explains the reason for the exception response.
Perform the action specified in the second CICS message received.
CSNE
DFHZRAC, DFHZRVX
XMEOUT Parameters: date, time,applid, termid, tranid, sense, instance, {1=DFHZRVX, 2=DFHZRVX, 3=DFHZRVX, 4=DFHZRVX, 5=DFHZRAC, 6=DFHZRAC, 7=DFHZRAC, 8=DFHZRAC, 9=DFHZRAC, 10=DFHZRAC, 11=DFHZRAC, 12=DFHZRAC}
TCTTEDA was not loaded before issuing a DFHTC TYPE=WRITE, or it was inadvertently cleared.
For the meaning of the sense data, see DFHZCxxxx messages.
If a task is attached, it is abnormally terminated with a transaction dump. The send is purged.
Ensure that TCTTEDA is loaded with the TIOA address before issuing the write.
CSNE
DFHZSDS
XMEOUT Parameters: date, time,applid, termid, tranid, sense, instance, {1=DFHZSDS, 2=DFHZSDS}
Sense codes not supported by CICS were received from the logical unit.
For the meaning of the sense data, see DFHZCxxxx messages.
All outstanding send and receive requests are purged. If a task is attached, it is abnormally terminated with a transaction dump. Communication with the node is terminated by issuing a VTAM CLSDST macro, and the node is placed out of service.
The user’s node error program (DFHZNEP) can process the sense codes.
CSNE
DFHZNAC
XMEOUT Parameters: date, time,applid, termid, tranid, sense, instance, {1=DFHZNAC}
Operator action is requested for a physical component of terminal termid before a request can be completed.
For the meaning of the sense data, see DFHZCxxxx messages.
The request is retried, unless the device is one that sends a logical unit status message after intervention is required. In the latter case, the relevant system action is taken.
Correct the problem with the device.
CSNE
DFHZNAC
XMEOUT Parameters: date, time,applid, termid, tranid, sense, instance, {1=DFHZNAC}
The secondary logical unit and CICS both sent a begin-bracket indicator concurrently.
For the meaning of the sense data, see DFHZCxxxx messages.
All outstanding send and receive requests are purged. If a task is attached, it is abnormally terminated with a transaction dump. Communication with the node is terminated by issuing the VTAM CLSDST macro.
Correct the controller application program so that it cannot send a begin-bracket indicator.
CSNE
DFHZNAC
XMEOUT Parameters: date, time,applid, termid, tranid, sense, instance, {1=DFHZNAC}
Node nodeid tried to connect to CICS. CICS rejected the request because it was deleting the terminal definition for termid.
For the meaning of the sense data, see DFHZCxxxx messages.
CICS continues with the resource alteration, or for instance 3 of the message, the autoinstall delete transaction, CATD, is restarted.
When the resource alteration is complete, retry the connection or logon request.
CSNE
DFHZSCX, DFHZBLX, DFHZLGX
XMEOUT Parameters: date, time,applid, termid, tranid, nodeid, sense, instance, {1=DFHZBLX, 2=DFHZBLX, 3=DFHZLGX}
The secondary logical unit asked CICS to terminate transmission of further data in the current chain.
For the meaning of the sense data, see DFHZCxxxx messages.
All outstanding send and receive requests are purged. If a task is attached, it is abnormally terminated with a transaction dump. A cancel indicator is issued to the logical unit permitting discard of the data in the current chain.
Use the supplied dump to determine why the logical unit requested the chain to be discarded.
For the meaning of the sense data, refer to the explanatory paragraph in message DFHZC2461.
CSNE
DFHZNAC
XMEOUT Parameters: date, time,applid, termid, tranid, sense, instance, {1=DFHZNAC}
The subsystem controller application program has insufficient resources to handle the request. For instance, in the case of 3601, the 3601 diskette might be full, or the data segment in the 3601 might not be large enough to handle the data set.
For the meaning of the sense data, see DFHZCxxxx messages.
The subsystem is temporarily suspended.
Determine why the controller application program encountered this condition. For the meaning of the sense data, refer to the explanatory paragraph in message DFHZC2461.
CSNE
DFHZNAC
XMEOUT Parameters: date, time,applid, termid, tranid, sense, instance, {1=DFHZNAC}
The controller application program cannot transmit a message to terminal termid. Either a data check occurred, or the node is not available.
For the meaning of the sense data, see DFHZCxxxx messages.
All outstanding send and receive requests are purged. If a task is attached, it is abnormally terminated with a transaction dump. Terminal status remains unchanged.
Use the supplied dump to determine why the application program could not execute the request.
For the meaning of the sense data, refer to the explanatory paragraph in message DFHZC2461.
CSNE
DFHZNAC
XMEOUT Parameters: date, time,applid, termid, tranid, sense, instance, {1=DFHZNAC}
CICS issued a VTAM request containing a communications identifier (CID) which VTAM did not recognize. This may be due to the TCTECID field having been altered. Alternatively, it may mean that the session is in the process of being closed down by VTAM and that CICS has tried to use it before the process was complete.
For the meaning of the sense data, see DFHZCxxxx messages.
All outstanding send and receive requests are purged. If a
task is attached, it is abnormally terminated with a transaction dump. If
the losterm exit was driven with return code X'0C', X'10', or X'14', CICS
issues a CLSDST to VTAM.
Ensure that application programs running concurrently do not alter the TCTECID field in the TCTTE. Also check that the session is still active; that is, that the system being communicated with is still functioning.
CSNE
DFHZLEX
XMEOUT Parameters: date, time,applid, termid, tranid, sense, instance, {1=DFHZLEX}
Either the node has not been activated by VARY ACTIVATE or CICS issued a VTAM request containing an invalid symbolic node name where:
For the meaning of the sense data, see DFHZCxxxx messages.
All outstanding send and receive requests are purged. If a task is attached, it is abnormally terminated with a transaction dump. The node is placed out of service.
Either issue VARY ACTIVATE for the node, or ensure that application programs running concurrently do not alter the NIB name. Names specified during VTAM definition must agree with those in the TCT.
CSNE
DFHZLEX
XMEOUT Parameters: date, time,applid, termid, tranid, netname, sense, instance, {1=DFHZLEX}
An exception response (negative response) was sent by the secondary logical unit.
For the meaning of the sense data, see DFHZCxxxx messages.
For a non-3270 device, an exception response is returned to the node, along with the sense codes supplied by VTAM in the request parameter list (RPL) for the inbound message. For a 3270 device, the exception request contains 3270 sense/status.
Analyze the sense codes in DFHZNEP.
CSNE
DFHZSYX
XMEOUT Parameters: date, time,applid, termid, tranid, sense, instance, {1=DFHZSYX, 2=DFHZSYX}
One of the following has occurred:
For the meaning of the sense data, see DFHZCxxxx messages.
In the first two cases, CICS honors the command. In all cases, all outstanding send and receive requests are purged, and if a task is attached, it is abnormally terminated with a transaction dump. Communication with the node is terminated by issuing a VTAM CLSDST macro.
None.
CSNE
DFHZASX
XMEOUT Parameters: date, time,applid, termid, tranid, sense, instance, {1=DFHZASX}
The function management header (FMH) length was greater than that of the data received from the logical unit.
For the meaning of the sense data, see DFHZCxxxx messages.
All data received is purged. If a task is attached, it is abnormally terminated with a transaction dump.
Correct the application program in the logical unit.
CSNE
DFHZRAC, DFHZATT
XMEOUT Parameters: date, time,applid, termid, tranid, sense, instance, {1=DFHZATT, 2=DFHZATT, 3=DFHZATT, 4=DFHZATT, 5=DFHZATT, 6=DFHZRAC}
The receive request for the remainder of data in excess of the input area for the receive-any module was not accepted by VTAM.
For the meaning of the sense data, see DFHZCxxxx messages.
All associated data is purged.
A subsequent message follows in the log, indicating reasons for the request failing. Refer to this message for further information and guidance.
CSNE
DFHZRAC
XMEOUT Parameters: date, time,applid, termid, tranid, sense, instance, {1=DFHZRAC, 2=DFHZRAC}
The application program has attempted to send more data than the generated maximum allowable length.
For the meaning of the sense data, see DFHZCxxxx messages.
All send requests are purged. If a task is attached, it is abnormally terminated with a transaction dump.
Correct the application program so that it is sensitive to the maximum allowable length of data that can be sent to the terminal (such as checking the device type), providing the terminal does not support outbound chaining of data (such as a pipeline session).
Note: The generated maximum allowable length is specified in the TCTTE.
CSNE
DFHZSDS
XMEOUT Parameters: date, time,applid, termid, tranid, sense, instance, {1=DFHZSDS, 2=DFHZSDS}
The logical unit (LU) has terminated all processing connected with one of its components.
For the meaning of the sense data, see DFHZCxxxx messages.
All send and receive requests are purged. If a task is attached, it is abnormally terminated with a transaction dump.
Correct the problem with the LU component and bring it back online. Possible causes of the problem include the following:
CSNE
DFHZNAC
XMEOUT Parameters: date, time,applid, termid, tranid, sense, instance, {1=DFHZNAC}
A component of the logical unit (LU) is no longer available.
For the meaning of the sense data, see DFHZCxxxx messages.
All send and receive requests are purged. If a task is attached, it is abnormally terminated with a transaction dump.
Correct the problem with the LU component and bring it back online. Possible causes of the problem include the following.
CSNE
DFHZNAC
XMEOUT Parameters: date, time,applid, termid, tranid, sense, instance, {1=DFHZNAC}
The logical unit (LU) does not support chaining of data from the host.
For the meaning of the sense data, see DFHZCxxxx messages.
All send requests are purged. If a task is attached, it is abnormally terminated with a transaction dump.
Ensure that the maximum amount of data being transmitted to the LU does not exceed the length specified in the buffer parameter of the DFHTCT macro instruction.
Note: The buffer parameter value can be increased only to the maximum acceptable limit of the LU.
CSNE
DFHZNAC
XMEOUT Parameters: date, time,applid, termid, tranid, sense, instance, {1=DFHZNAC}
The function management header (FMH) transmitted to the logical unit (LU) had no counterpart on the translate table.
For the meaning of the sense data, see DFHZCxxxx messages.
All send and receive requests are purged. If the batch data interchange program is not being used, the transaction is abnormally terminated with a transaction dump. The first part of the TIOA, containing the FMH, is written to the CSNE log.
Correct the application program so that the LU has a counterpart on the translate table.
CSNE
DFHZNAC
XMEOUT Parameters: date, time,applid, termid, tranid, sense, instance, {1=DFHZNAC}
The response unit (RU) received by the logical unit (LU) contains a request that this device does not support.
For the meaning of the sense data, see DFHZCxxxx messages.
All send and receive requests are purged. If a task is attached, it is abnormally terminated with a transaction dump.
Ensure that the terminal control table (TCT) generation specifications for the device are valid as well as able to accommodate the application requests. (For example, a read-only device being defined as transceive, yet having a bid sent to it.)
CSNE
DFHZNAC
XMEOUT Parameters: date, time,applid, termid, tranid, sense, instance, {1=DFHZNAC}
The logical unit (LU) has indicated, via sense codes contained in an exception response or an LU status message, that it requires the data to be retransmitted.
For the meaning of the sense data, see DFHZCxxxx messages.
Retransmission of data will be attempted only in the case of protected tasks (message integrity). If the exception response containing the retry sense codes is received for an unprotected task while in chain processing, a cancel command will be sent to the LU and the task will be resumed. If CICS is not in chain processing, the transaction will be resumed.
If message retransmission is necessary for the LU, ensure that the retry sense codes are imbedded in the exception response. Also ensure that the host transaction is defined as a protected task (message integrity).
CSNE
DFHZNAC
XMEOUT Parameters: date, time,applid, termid, tranid, sense, instance, {1=DFHZNAC}
The response unit (RU) received by the logical unit (LU) was either not translatable or had an invalid length.
For the meaning of the sense data, see DFHZCxxxx messages.
All send and receive requests are purged. If a task is attached, it is abnormally terminated with a transaction dump.
Retrying the request a number of times by use of the node error program (NEP) mechanism may be necessary. This is because this type of error may stem from a bad communication line. If this fails, check for possible invalid or inappropriate terminal specifications at terminal control table (TCT) generation time.
CSNE
DFHZNAC
XMEOUT Parameters: date, time,applid, termid, tranid, sense, instance, {1=DFHZNAC}
Terminal termid was defined in the terminal control table (TCT) as running in pipeline session mode. However, the BRACKET operand in that definition was either omitted or was specified as BRACKET=YES. Bracket protocol is not enforced on a pipeline session terminal.
For the meaning of the sense data, see DFHZCxxxx messages.
All send and receive requests are purged and the session is terminated. If a task is attached, it is abnormally terminated with a transaction dump.
Correct the TCT entry by inserting the BRACKET=NO operand.
CSNE
DFHZNAC
XMEOUT Parameters: date, time,applid, termid, tranid, sense, instance, {1=DFHZATT}
Normal data flow has been interrupted.
For the meaning of the sense data, see DFHZCxxxx messages.
Processing continues.
Retry the WRITE.
CSNE
DFHZNAC
XMEOUT Parameters: date, time,applid, termid, tranid, sense, instance, {1=DFHZNAC}
An application request could not be satisfied because the required component was not available.
For the meaning of the sense data, see DFHZCxxxx messages.
If a task is attached, it is abnormally terminated with a transaction dump. All outstanding send and receive requests are purged.
Message DFHME0116 is normally produced containing the symptom string for this problem.
Check the terminal environment, or use the symptom string, and if necessary the dump, to determine the cause of the error.
CSNE
DFHZNAC
XMEOUT Parameters: date, time,applid, termid, tranid, sense, instance, {1=DFHZNAC}
A CANCEL indicator was received while a task was active.
For the meaning of the sense data, see DFHZCxxxx messages.
If a task is attached, it is abnormally terminated with a transaction dump. All outstanding send and receive requests purged.
None.
CSNE
DFHZRVX
XMEOUT Parameters: date, time,applid, termid, tranid, sense, instance, {1=DFHZRVX}
A CANCEL indicator was received while no task was active.
For the meaning of the sense data, see DFHZCxxxx messages.
Processing continues.
None.
CSNE
DFHZRAC
XMEOUT Parameters: date, time,applid, termid, tranid, sense, instance, {1=DFHZRAC}
A connection request was rejected. CICS is temporarily unable to carry out the connection request. The TCTTE for node nodeid indicated that the session could not be established. returncode gives the reason, as follows:
For the meaning of the sense data, see DFHZCxxxx messages.
The connection request is rejected.
Retry the connection request when the node becomes available. See the CICS Customization Guide for more information on the CLSDST macro and for an explanation of abnormal node conditions.
CSNE
DFHZLGX, DFHZSCX, DFHZBLX
XMEOUT Parameters: date, time,applid, termid, tranid, nodeid, returncode, sense, instance, {1=DFHZSCX, 2=DFHZSCX, 3=DFHZSCX,4=DFHZSCX, 5=DFHZSCX, 6=DFHZSCX,7=DFHZBLX, 8=DFHZBLX, 9=DFHZLGX,10=DFHZLGX, 11=DFHZLGX, 12=DFHZLGX,13=DFHZLGX, 14=DFHZLGX, 15=DFHZLGX,16=DFHZLGX}
A connection request was rejected because the CICS terminal recovery program was still executing.
For the meaning of the sense data, see DFHZCxxxx messages.
The connection request is rejected.
Retry the connection request. Message DFHRU2800 is produced when the recovery program has completed processing.
CSNE
DFHZLGX, DFHZSCX, DFHZBLX
XMEOUT Parameters: date, time,applid, termid, tranid, nodeid, sense, instance, {1=DFHZLGX, 2=DFHZSCX, 3=DFHZBLX}
The terminal control table terminal entry (TCTTE) of the device from which the information is to be copied ("from" device) did not specify the COPY feature. Alternatively, the "from" device:
For the meaning of the sense data, see DFHZCxxxx messages.
If a task is attached, it is abnormally terminated with a transaction dump.
Ensure that the application program is aware of the device configuration. Furthermore, ensure that the "from" device is defined in the TCT as a 3270 device AND is connected to CICS.
CSNE
DFHZARQ
XMEOUT Parameters: date, time,applid, termid, tranid, sense, instance, {1=DFHZARQ, 2=DFHZARQ, 3=DFHZARQ}
On a request for TOLTEP, a receive request completes in error.
For the meaning of the sense data, see DFHZCxxxx messages.
If a transaction is currently attached, it is abnormally terminated. The terminal is disconnected from CICS by a VTAM CLSDST macro, and is queued for logon to CICS when TOLTEP has finished.
None.
CSNE
DFHZSYX
XMEOUT Parameters: date, time,applid, termid, tranid, sense, instance, {1=DFHZSYX}
This message is sent to the CSNE message log when an INTERVENTION REQUIRED condition is detected on a 3270 printer. This condition could occur for any of the reasons listed below.
For the meaning of the sense data, see DFHZCxxxx messages.
No action is performed except printing of the RPL and the TCTTE.
Check that the terminal control table (TCT) is properly defined and that the transaction requests proper printer operations. If this is correct, check that the printer itself is in proper working order.
CSNE
DFHZNAC
XMEOUT Parameters: date, time,applid, termid, tranid, sense, instance, {1=DFHZNAC}
This message occurs when an INTERVENTION REQUIRED condition arises on the 3270 Information Display System.
For the meaning of the sense data, see DFHZCxxxx messages.
No action is performed.
Correct the intervention condition.
CSNE
DFHZNAC
XMEOUT Parameters: date, time,applid, termid, tranid, sense, instance, {1=DFHZNAC}
An error status message sense was received from a 3270 Information Display System. An INTERVENTION REQUIRED condition causes an "intervention required" message to be output instead of this message.
If a task is attached, it is abnormally terminated with a transaction dump. If bad data, sent by Basic Mapping Support (BMS), causes an operation check, the bad data is purged.
Analyze the error status codes to determine the proper course of action required to correct the unit error or program error.
For non-SNA 3270 devices, the sense code is 0000 xxxx, where xxxx is sense data returned by the control unit to which the 3270 device is attached. Datastream errors are rejected with an Operation Check, and commands with a Command Reject. Details of error status codes are given in the IBM 3270 Information Display System 3274 Control Unit Description and Programmer’s Guide.
CSNE
DFHZNAC
XMEOUT Parameters: date, time,applid, termid, tranid, sense, instance, {1=DFHZNAC}
DFHZNAC has performed an interval control PUT to a 3270 printer on behalf of a DFHZC2497 "unavailable printer" condition. The printer is:
For the meaning of the sense data, see DFHZCxxxx messages.
Other processing continues.
Determine why the printer is unavailable. If the terminal is out of service, put it back into service. If the terminal has an intervention situation, determine what this situation is and correct it. If the terminal does not have a RECEIVE or TRANSCEIVE status, place it into RECEIVE or TRANSCEIVE status.
CSNE
DFHZNAC
XMEOUT Parameters: date, time,applid, termid, tranid, sense, instance, {1=DFHZNAC}
DFHZNAC has attempted to perform a DFHIC TYPE=PUT macro as the result of a DFHZC2497 "unavailable printer" condition and has failed. This message is written to the CSNE log.
For the meaning of the sense data, see DFHZCxxxx messages.
DFHZNEP is recalled by DFHZNAC to allow for further processing.
Ensure that:
CSNE
DFHZNAC
XMEOUT Parameters: date, time,applid, termid, tranid, {1= , 2= IOERROR, 3= TRNIDER, 4=TRMIDER, 5= INVREQ}, sense, instance, {1=DFHZNAC}
A print function was requested on a 3270 display device. Neither the PRINTTO or the ALTPRT printer was available to receive the information.
For the meaning of the sense data, see DFHZCxxxx messages.
If no NEP action is specified, the print request is halted.
A possible solution is to route the data available at TCTTEDA in the provided terminal entry to a transient data queue that causes automatic task initiation later to a printer. This would be done in DFHZNEP. For more information, see the CICS Customization Guide.
CSNE
DFHZARQ
XMEOUT Parameters: date, time,applid, termid, tranid, sense, instance, {1=DFHZARQ}
A 3270 print request has failed because transaction CSPP could not be initiated. Either transaction CSPP is not an installed transaction definition, or the message to be printed cannot be written to temporary storage.
For the meaning of the sense data, see DFHZCxxxx messages.
Processing continues.
Check that transaction CSPP is an installed transaction definition and that you have sufficient temporary storage to accommodate the data to be printed.
CSNE
DFHZARQ
XMEOUT Parameters: date, time,applid, termid, tranid, sense, instance, {1=DFHZARQ}
The user has entered an invalid entry, the entry is rejected, and the request is backed out.
Terminal Control backs out the request and issues this message with the error information contained in msgtext.
Read the error information that is contained in msgtext and reenter the request.
XMEOUT Parameters: date, time,applid, msgtext
A CCIN transaction has been run from a CICS client. The codepage which the CICS client has requested is not supported.
netname is the VTAM netname of the CICS client.
CICS cannot perform the translations required to support the CICS client with the requested character set and codepage. CICS continues but uses a default codepage instead of the supplied one. For details of the default codepage, see the CICS Family: Communicating from CICS on System/390® manual.
The request to install the CICS client continues, but uses the default codepage. A response code of EXCEPTION and a reason code of INVALIDCODEPAGE is sent to the client.
See the CICS Family: Communicating from CICS on System/390 manual for a list of the client codepage values which are supported. It may be necessary to reconfigure the client locale.
CSCC
DFHZCN2
XMEOUT Parameters: date, time,applid, netname, codepage
A CCIN transaction has been run from a CICS client. The capabilities which have been received are not valid. The CICS client has specified that it supports features which no CICS client is supposed to support. The CICS client is violating the CICS client communications architecture.
netname is the VTAM netname of the CICS client.
Exception trace point AP301A is written.
The request to install the CICS client is rejected. A response code of DISASTER and a reason code of INVALIDREQUEST is sent to the client.
You need further assistance from IBM to resolve this problem. See CICS Problem Determination Guide for guidance on how to proceed.
CSCC
DFHZCN2
XMEOUT Parameters: date, time,applid, netname
A CCIN transaction has been run from a CICS client. One of the parameters which must be supplied is the codepage which the CICS client intends to use. This parameter is missing.
netname is the VTAM netname of the CICS client.
Exception trace point AP301B is written.
The request to install the CICS client is rejected. A response code of DISASTER and a reason code of INVALIDREQUEST is sent to the client.
You need further assistance from IBM to resolve this problem. See CICS Problem Determination Guide for guidance on how to proceed.
CSCC
DFHZCN1
XMEOUT Parameters: date, time,applid, netname
A CTIN install request has been received from a CICS client as a result of a CICS_EpiAddTerminal function or terminal emulator operation.
CICS was checking the codepage specified by the CICS client and the codepage specified by the virtual terminal. However one of the following occurred:
CICS cannot perform the translations required to support the CICS client with the requested codepage.
netname is the VTAM netname of the CICS client.
Exception trace point AP3035 is written.
A response code of ERROR and a reason code of INSTALLCANCELLED is sent to the client. The virtual terminal is NOT installed.
The request to install the virtual terminal continues and the invalid codepage is replaced by a default as specified in the CICS Family: Communicating from CICS on System/390 manual.
A response code of EXCEPTION and a reason code of INVALIDCODEPAGE is sent to the client.
A response code of ERROR and a reason code of INSTALLCANCELLED is sent to the client. The virtual terminal is NOT installed.
See the CICS Family: Communicating from CICS on System/390 manual and check the list of the client codepage values then reconfigure the workstation locale or correct the virtual terminal TYPETERM definition.
The exception trace point AP3035 contains the CICS client codepage and the virtual terminal CGCSGID values.
CSCC
DFHZCT1
XMEOUT Parameters: date, time,applid, termid, netname, {1=n.a., 2=n.a., 3=n.a., 4=combination of client and virtual terminal codepage., 5=client codepage., 6=virtual terminal codepage.}
A CTIN install request has been received from a CICS client as a result of a CICS_EpiAddTerminal function or terminal emulator operation. However the CICS client whose VTAM netname is netname already has 512 virtual terminals.
termid is the name that would have been given to the new virtual terminal. If the CICS client did not supply the name it is blank.
The request to install the virtual terminal is rejected. A response code of DISASTER and a reason code of INVALIDREQUEST is sent to the client.
Check why the CICS client has sent so many CTIN installs without corresponding CTIN uninstall functions.
To correct the problem the CICS client must send a CTIN uninstall for each virtual terminal that needs to be deleted.
CSCC
DFHZCT1
XMEOUT Parameters: date, time,applid, termid, netname
A CTIN install request has been received from a CICS client as a result of a CICS_EpiAddTerminal function or terminal emulator operation. However there was no previous CCIN install request for the CICS client with the VTAM netname of netname. CCIN must always run before CTIN.
This may have been caused by a CICS restart.
netname is the VTAM netname of the CICS client.
If the request was to install a virtual terminal then it is rejected with a response code of CTIN_ERROR and a reason code of CTIN_CCIN_INACTIVE.
The CICS client must carry out CCIN uninstall/install before the next CTIN install.
CSCC
DFHZCT1
XMEOUT Parameters: date, time,applid, netname
A CTIN install request has been received from a CICS client as a result of a CICS_EpiAddTerminal function or terminal emulator operation. However CICS was unable to find the model modelid which was specified in the CICS_EpiAddTerminal DEVTYPE parameter or terminal emulator ModelId parameter.
netname is the VTAM netname of the CICS client.
The request to install the virtual terminal is rejected. A response code of ERROR and a reason code of UNKNOWNMODEL is sent to the client.
Either correct the DevType in the CICS_EpiAddTerminal function or terminal emulator parameter or install a model of this name using RDO to define the autoinstall model with the RDO TERMINAL and TYPETERM definitions.
CSCC
DFHZCT1
XMEOUT Parameters: date, time,applid, termid, netname, modelid
A CTIN install request has been received from a CICS client as as a result of a CICS_EpiAddTerminal function or terminal emulator operation. The parameter list did not supply a NetName indicating that CICS should supply the name. However there are only 46,656 possible names available and they are all currently in use.
netname is the VTAM netname of the CICS client.
The request to install the virtual terminal is rejected. A response code of ERROR and a reason code of INSTALLCANCELLED is sent to the client.
As CICS clients issue CTIN uninstalls for autoinstalled virtual terminals these termids will be freed.
It is possible that some of the CICS clients were switched off leaving autoinstalled virtual terminals around. When these are switched back on again they should issue CCIN install which will free the virtual terminals if they are not in use.
DISCARD can be used to delete a virtual terminal - but this should be done with discretion.
If the SIT VTPREFIX coincides with the first character of the termid allocated to a normal autoinstall terminal by the autoinstall URM (default DFHZATDX), there may be some names reserved because the autoinstall terminal existed when CTIN install tried to use the same name. Avoid doing this if possible because the only way to free these names is to restart CICS.
CSCC
DFHZCT1
XMEOUT Parameters: date, time,applid, netname
A CTIN install request has been received from a CICS client as a result of a CICS_EpiAddTerminal function or terminal emulator operation. As part of the installation process the CITS transaction is called to create a virtual terminal termid. However CICS was unable to attach the CITS transaction.
netname is the VTAM netname of the CICS client.
Exception trace point AP3025 is written.
The request to install the virtual terminal is rejected. A response code of ERROR and a reason code of INSTALLCANCELLED is sent to the client.
Check that the CITS transaction and the DFHZATS program are defined correctly as specified in the DFHSPI IBM supplied group and are installed.
CSCC
DFHZCT1
XMEOUT Parameters: date, time,applid, termid, netname
A CTIN install request has been received from a CICS client as a result
of a CICS_EpiAddTerminal function or terminal emulator operation. The NetName parameter termid starts or ends with a
character
that conflicts with CICS standards.
netname is the VTAM netname of the CICS client.
The request to install the virtual terminal is rejected. A response
code of DISASTER and a reason code of INVALIDTERMID is sent to the client.
Change the NetName to start or end with a different character.
It can start with any character that is valid for a normal terminal name except
for <,> or -. It cannot end with an -.
If the NetName was specified
correctly, check the input to the CTIN transaction.
CSCC
DFHZCT1
XMEOUT Parameters: date, time,applid, termid, netname
A CTIN install request has been received from a CICS client as a result of a CICS_EpiAddTerminal function or terminal emulator operation. As part of the installation process the CITS transaction is called to create virtual terminal termid. However the CTIN transaction has waited for two minutes for the CITS transaction to run.
netname is the VTAM netname of the CICS client.
Exception trace point AP3027 is written.
The request to install the virtual terminal is rejected. A response code of ERROR and a reason code of INSTALLCANCELLED is sent to the client.
Investigate why the CITS transaction was unable to start or was hanging.
You may need to increase MAXTASK or the CITS TRANCLASS allocation.
CSCC
DFHZCT1
XMEOUT Parameters: date, time,applid, termid, netname
A CTIN uninstall request has been received from a CICS client as a result of a CICS_EpiDelTerminal function or terminal emulator operation. As part of the delete process the CDTS transaction is called to delete virtual terminal termid. However CICS was unable to attach the CDTS transaction.
netname is the VTAM netname of the CICS client.
Exception trace point AP3028 is written. The attempt to delete the virtual terminal is rejected.
Check to see if the CDTS transaction and the DFHZATS program are defined correctly as specified in IBM supplied group DFHSPI and that they are installed.
CSCC
DFHZCT1
XMEOUT Parameters: date, time,applid, termid, netname
A CTIN uninstall request has been received from a CICS client as a result of a CICS_EpiDelTerminal function or terminal emulator operation. As part of the installation process the CDTS transaction is called to delete virtual terminal termid. However the CTIN transaction has waited for the CDTS transaction for two minutes and so ends with this message.
netname is the VTAM netname of the CICS client.
Exception trace point AP3029 is written. The CDTS attempt to delete the virtual terminal continues and will occur when the CDTS transaction starts or is 'unsuspended'.
Check to see why the CDTS transaction was unable to start or was hanging.
You may need to increase MAXTASK or the CDTS TRANCLASS allocation.
CSCC
DFHZCT1
XMEOUT Parameters: date, time,applid, termid, netname
A CTIN install request has been received from a CICS client as a result of a CICS_EpiAddTerminal function or terminal emulator operation. However the virtual terminal termid is in use, that is the surrogate TCTTE indicates that a transaction is still running against this terminal.
netname is the VTAM netname of the CICS client.
Exception trace point AP302E is written.
The request to install the virtual terminal is rejected. A response code of ERROR and a reason code of ALREADYINSTALLED is sent to the client.
Investigate why a transaction is still running for the virtual terminal.
CSCC
DFHZCT1
XMEOUT Parameters: date, time,applid, termid, netname
A CTIN install request has been received from a CICS client as a result of a CICS_EpiAddTerminal function or terminal emulator operation. CTIN specified that a pre defined virtual terminal termid should be used, but CICS cannot find it and no ModelId was provided (DevType) so an autoinstall was not attempted.
netname is the VTAM netname of the CICS client.
The request to install the virtual terminal is rejected. A response code of ERROR and a reason code of UNKNOWNTERMINAL is sent to the client.
Ensure that there is an installed predefined terminal for termid that has a remote system parameter (REMOTESYSTem) specifying the name of this CICS clients connection and that the VTAM NETNAMEs match. Then install the definition with the correct parameters.
CSCC
DFHZCT1
XMEOUT Parameters: date, time,applid, termid, netname
A CTIN request has been received from a CICS client with a VTAM netname of netname. However the function specified was not INSTALL or UNINSTALL.
Exception trace point AP3034 is written. The CTIN transaction abnormally terminates with abend code AZAI.
Determine where the request originated. Ensure that the input has not been corrupted. You may need further assistance from IBM. See CICS Problem Determination Guide for guidance on how to proceed.
CSCC
DFHZCT1
XMEOUT Parameters: date, time,applid, netname
A CTIN install request has been received from a CICS client as a result of a CICS_EpiAddTerminal function or terminal emulator operation. CTIN specified that a virtual terminal termid should be autoinstalled. However another resource was installed with the same name after the CTIN transaction had ensured that the name was free.
netname is the VTAM netname of the CICS client.
Exception trace point AP3026 is written.
The request to install the virtual terminal is rejected. A response code of ERROR and a reason code of ALREADYINSTALLED is sent to the client.
Investigate where the duplicate resource came from. It is possible that the terminal/APPC autoinstall URM created the name dynamically. If NetName was specified in the CTIN parameters, ensure that the CICS client names do not conflict with existing CICS terminal or connection names. If NetName was not specified, examine the SIT VTPREFIX override to check that the URM does not create names starting with the VTPREFIX character.
CSCC
DFHZCT1
XMEOUT Parameters: date, time,applid, termid, netname
A CTIN install request has been received from a CICS client as a result of a CICS_EpiAddTerminal function or terminal emulator operation. CTIN supplied a NetName termid but CICS found a resource with the same name which is either an existing virtual terminal for this client, an existing virtual terminal for another client or another CICS terminal or connection resource.
netname is the VTAM netname of the CICS client.
The request to install the virtual terminal is rejected. A response code of ERROR and a reason code of ALREADYINSTALLED is sent to the client.
Investigate where the duplicate resource came from. It is possible that the terminal/APPC autoinstall URM created the name dynamically and that the CICS client used a name that clashes with the URM.
It is also possible that a client created the virtual terminal and then tried to reuse it without an intervening uninstall, via CCIN or CTIN.
CSCC
DFHZCT1
XMEOUT Parameters: date, time,applid, termid, netname
A CTIN install request has been received from a CICS client as a result of a CICS_EpiAddTerminal function or terminal emulator operation. CTIN specified that the virtual terminal termid should be autoinstalled. However, the virtual terminal was already installed.
netname is the VTAM netname of the CICS client.
The request to install the virtual terminal is rejected. A response code of ERROR and a reason code of ALREADYINSTALLED is sent to the client.
The CICS client should issue CTIN uninstall before any attempt to issue another CTIN install for the same NetName.
CSCC
DFHZCT1
XMEOUT Parameters: date, time,applid, termid, netname
A CTIN install request has been received from a CICS client as a result of a CICS_EpiAddTerminal function or terminal emulator operation. CTIN specified that the virtual terminal termid should be autoinstalled. However, the name specified is already in use by another CICS resource.
netname is the VTAM netname of the CICS client.
The request to install the virtual terminal is rejected. A response code of ERROR and a reason code of ALREADYINSTALLED is sent to the client.
Investigate where the duplicate resource came from. It is possible that the terminal/APPC autoinstall URM created the name dynamically.
If NetName was specified on the CTIN install ensure that NetName does not conflict with other CICS resources.
If NetName was not specified, examine the SIT VTPREFIX override to check that the URM does not create names starting with the VTPREFIX character.
CSCC
DFHZCT1
XMEOUT Parameters: date, time,applid, termid, netname
A CTIN install request has been received from a CICS client as a result of a CICS_EpiAddTerminal function or terminal emulator operation. CICS attempted to autoinstall the virtual terminal termid. However, the CITS task which was attached to install the virtual terminal, abended.
If this ABEND was an AZVE, this is because a resource already exists with that name. However, this only occurs if the duplicate resource was added after this CTIN transaction started and checked for any duplicate.
netname is the VTAM netname of the CICS client.
Exception trace point AP3030 is written.
The request to install the virtual terminal is rejected. A response code of ERROR and a reason code of INSTALLCANCELLED is sent to the client.
Investigate where the duplicate resource came from. It is possible that the terminal/APPC autoinstall URM created the name dynamically.
If NetName was specified on the CTIN install, ensure that the names do not conflict.
If NetName was not specified, examine the SIT VTPREFIX override to check that the URM does not create names starting with the VTPREFIX character.
For any other abend, see the description of the abend code for further guidance.
CSCC
DFHZCT1
XMEOUT Parameters: date, time,applid, termid, netname
A CTIN uninstall request has been received from a CICS client as a result of a CICS_EpiDelTerminal function or terminal emulator operation. However, the surrogate TCTTE attached to the virtual terminal is still in use and cannot be deleted.
netname is the VTAM netname of the CICS client.
Exception trace point AP302F is written. The attempt to delete the virtual terminal is rejected.
Either wait for the transaction to finish or PURGE the transaction. Once the transaction has ended the virtual terminal will be deleted when the client issues CCIN install or uninstall.
CSCC
DFHZCT1
XMEOUT Parameters: date, time,applid, termid, netname
A CTIN uninstall request has been received from a CICS client as a result of a CICS_EpiDelTerminal function or terminal emulator operation. However the virtual terminal termid does not exist as a remote terminal for this CICS client.
netname is the VTAM netname of the CICS client.
The attempt to delete the virtual terminal is rejected.
Determine why a CICS client requested that a non existent virtual terminal be deleted.
If the CTIN uninstall was issued correctly and the virtual terminal should exist, examine the CICS log for message DFHZC5966 and for DFHZC32xx messages referring to this terminal.
CSCC
DFHZCT1
XMEOUT Parameters: date, time,applid, termid, netname
A CTIN uninstall request has been received from a CICS client as a result of a CICS_EpiDelTerminal function or terminal emulator operation. However the NetName parameter, defining which virtual terminal is to be deleted, is missing.
netname is the VTAM netname of the CICS client.
Exception trace point AP3037 is written - data 2 contains the data received. The attempt to delete the virtual terminal is rejected.
Examine the input to CTIN. You may need further assistance from IBM. See CICS Problem Determination Guide for guidance on how to proceed.
CSCC
DFHZCT1
XMEOUT Parameters: date, time,applid, netname
A CTIN install request has been received from a CICS client as a result of a CICS_EpiAddTerminal function or terminal emulator operation. CICS is attempting to extract the details from the virtual terminal that has just been created and return them back to the CICS client. However the attempt to extract the details in the form of a builder parameter set (BPS) failed.
netname is the VTAM netname of the CICS client.
Exception trace point AP3031 is written.
The request to install the virtual terminal is rejected. A response code of ERROR and a reason code of INSTALLCANCELLED is sent to the client.
You need further assistance from IBM to resolve this problem. See CICS Problem Determination Guide for guidance on how to proceed.
CSCC
DFHZCT1
XMEOUT Parameters: date, time,applid, termid, netname
A CTIN install request has been received from a CICS client as a result of a CICS_EpiAddTerminal function or terminal emulator operation. However the data received was longer than expected. netname is the VTAM netname of the CICS client.
Exception trace point AP302D is written - data 2 contains the length that was received. The CTIN transaction abnormally terminates with abend code AZAI.
Examine the data sent to CICS from the CICS client. You may need to contact IBM for assistance. See CICS Problem Determination Guide for guidance on how to proceed.
CSCC
DFHZCT1
XMEOUT Parameters: date, time,applid, netname
A CTIN install request has been received from a CICS client as a result of a CICS_EpiAddTerminal function or terminal emulator operation. However the header contains an invalid group. netname is the VTAM netname of the CICS client.
Exception trace point AP3024 is written - data 2 contains the data received. The CTIN transaction abnormally terminates with abend code AZAI.
Examine the data sent to CICS from the CICS client. You may need to contact IBM for assistance. See CICS Problem Determination Guide for guidance on how to proceed.
CSCC
DFHZCT1
XMEOUT Parameters: date, time,applid, netname
A CTIN install request has been received from a CICS client as a result of a CICS_EpiAddTerminal function or terminal emulator operation. CICS attempted to parse this data but found a discrepancy between the number of parameters, the length of the parameters and the length of the data received. netname is the VTAM netname of the CICS client.
Exception trace point AP3033 is written - data 2 contains the data received. The CTIN transaction abnormally terminates with abend code AZAI.
Examine the data sent to CICS from the CICS client. You may need further assistance from IBM. See CICS Problem Determination Guide for guidance on how to proceed.
CSCC
DFHZCT1
XMEOUT Parameters: date, time,applid, netname
A CTIN request has been received on a conversation which is not at synchronization level 0 or 1. netname is the VTAM netname of the CICS client.
Exception trace point AP302B is written. The CTIN transaction abnormally terminates with abend code AZAI.
Ensure that the CICS client converses at sync level 0 or 1.
CSCC
DFHZCT1
XMEOUT Parameters: date, time,applid, netname
A CTIN install request has been received from a CICS client as a result of a CICS_EpiAddTerminal function or terminal emulator operation. However there is an invalid version number in the header. netname is the VTAM netname of the CICS client.
Exception trace point AP3036 is written - data 2 contains the data received. The CTIN transaction abnormally terminates with abend code AZAI.
Since the version used in the CICS client must match with the version used by the server, one or the other is at the wrong level and should be changed. You may need further assistance from IBM. See CICS Problem Determination Guide for guidance on how to proceed.
CSCC
DFHZCT1
XMEOUT Parameters: date, time,applid, netname
A CCIN request has been received on a conversation which is not at synchronization level 0 or 1. netname is the VTAM netname of the CICS client.
Exception trace point AP3003 is written. The CCIN transaction abnormally terminates with abend code AZAF.
Ensure that the CICS client converses at sync level 0 or 1.
CSCC
DFHZCN1
XMEOUT Parameters: date, time,applid, netname
A CCIN install request has been received from a CICS client. However the data received was longer than expected. netname is the VTAM netname of the CICS client.
Exception trace point AP3004 is written - data 2 contains the length that was received. The CCIN transaction abnormally terminates with abend code AZAF.
Examine the data sent to CICS from the CICS client. You may need further assistance from IBM. See CICS Problem Determination Guide for guidance on how to proceed.
CSCC
DFHZCN1
XMEOUT Parameters: date, time,applid, netname
A CCIN request has been received from a CICS client. However there is an invalid group in the header. netname is the VTAM netname of the CICS client.
Exception trace point AP3002 is written - data 2 contains the data received. The CCIN transaction abnormally terminates with abend code AZAF.
Examine the data sent to CICS from the CICS client.
CSCC
DFHZCN1
XMEOUT Parameters: date, time,applid, netname
A CCIN install request has been received from a CICS client. However the header contains an invalid version value. netname is the VTAM netname of the CICS client.
Either the CICS client is setting up the CCIN header incorrectly or a new version of the CICS client software is being used which is not supported on CICS Transaction Server for z/OS®, Version 3 Release 1.
Exception trace point AP300B is written - data 2 contains the data received. The CCIN transaction abnormally terminates with abend code AZAF.
Since the version used in the CICS client must match with the version used by the server, one or the other is at the wrong level and should be changed. You may need further assistance from IBM. See CICS Problem Determination Guide for guidance on how to proceed.
CSCC
DFHZCN1
XMEOUT Parameters: date, time,applid, netname
A CCIN request has been received from a CICS client. However there is an invalid function in the header. netname is the VTAM netname of the CICS client.
Exception trace point AP3002 is written - data 2 contains the data received. The CCIN transaction abnormally terminates with abend code AZAF.
Investigate why the CICS client has sent an unknown function call to CCIN. You may need further assistance from IBM. See CICS Problem Determination Guide for guidance on how to proceed.
CSCC
DFHZCN1
XMEOUT Parameters: date, time,applid, netname
A CCIN transaction has been run from a CICS client. One of the parameters which must be supplied is the CAPABILITIES parameter which specifies the capabilities the CICS client can support. This parameter is missing.
netname is the VTAM netname of the CICS client.
The request to install a CICS client is rejected. A response code of DISASTER and a reason code of INVALIDREQUEST is sent to the client.
You need further assistance from IBM to resolve this problem. See CICS Problem Determination Guide for guidance on how to proceed.
CSCC
DFHZCN1
XMEOUT Parameters: date, time,applid, netname
A CCIN request has been received from a CICS client. As part of the processing, the CDTS transaction was called to delete virtual terminal termid. However CICS was unable to attach the CDTS transaction.
netname is the VTAM netname of the CICS client.
The attempt to delete the virtual terminal fails. If this is a CCIN install request, the install continues.
Ensure that the CDTS transaction and the DFHZATS program are defined correctly as specified in IBM supplied group DFHSPI and that they are installed.
CSCC
DFHZCN2
XMEOUT Parameters: date, time,applid, termid, netname
A CCIN request has been received from a CICS client. As part of the processing, the CDTS transaction is called to delete virtual terminal termid. However the CCIN transaction has waited for the CDTS transaction for two minutes and has timed out.
netname is the VTAM netname of the CICS client.
The CDTS attempt to delete the virtual terminal continues and occurs when the CDTS transaction starts or is 'unsuspended'.
If this is a CCIN install request, the install continues.
Check to see why the CDTS transaction was unable to start or was hanging.
You may need to increase MAXTASK or the CITS TRANCLASS allocation.
CSCC
DFHZCN2
XMEOUT Parameters: date, time,applid, termid, netname
A CCIN request has been received from a CICS client. There should not be any virtual terminals installed, however, one or more were located. The surrogate TCTTE attached to the virtual terminal is still in use and cannot be deleted. If this was caused by an immediate shut down of the client the transaction abend might not have completed before CICS attempted to delete the client.
netname is the VTAM netname of the CICS client.
Exception trace point AP301C is written. The attempt to delete the virtual terminal is rejected.
If this is a CCIN install request, the install continues.
Determine why the virtual terminal was installed when CCIN was run.
Either wait for the transaction to finish or PURGE the transaction. Once the transaction completes the virtual terminal will be deleted at the next CCIN install/uninstall.
CSCC
DFHZCN2
XMEOUT Parameters: date, time,applid, termid, netname
A CCIN install request has been received from a CICS client. CICS attempted to parse this data but found a discrepancy between the number of parameters, the length of the parameters, and the length of the data received. netname is the VTAM netname of the CICS client.
Exception trace point AP300E is written - data 2 contains the data received. The CCIN transaction abnormally terminates with abend code AZAF.
Examine the data sent to CICS from the CICS client. You may need further assistance from IBM. See CICS Problem Determination Guide for guidance on how to proceed.
CSCC
DFHZCN1
XMEOUT Parameters: date, time,applid, netname
If chain assembly (BUILDCHAIN) has been specified in the TCTTE, the chain being assembled does not fit into the IOAREALEN for a maximum chain (IOAREALEN Value 2). The remaining space in the IOAREALEN for a maximum chain is smaller than the maximum RECEIVESIZE.
If chain assembly (BUILDCHAIN) has been specified in the TCTTE, but maximum chain value equals zero, either the maximum chain value has been set incorrectly at build time or the value has been overwritten.
For the meaning of the sense data, see DFHZCxxxx messages.
If a task is attached, it is abnormally terminated with a transaction dump.
Ensure that the maximum chain size, generated in CEDA TYPETERM with IOAREALEN (value 2) keyword, is large enough for the maximum chain expected.
CSNE
DFHZRVS, DFHZRVX, DFHZRAC
XMEOUT Parameters: date, time,applid, termid, tranid, sense, instance, {1=DFHZRVS, 2=DFHZRVS, 3=DFHZRVS, 4=DFHZRVS, 5=DFHZRVS, 6=DFHZRVX, 7=DFHZRAC, 8=DFHZRAC}
A resource of the logical unit (LU) is now available. It had previously been temporarily unavailable or had required intervention.
For the meaning of the sense data, see DFHZCxxxx messages.
Any outstanding read or write operation is retried.
None.
CSNE
DFHZNAC
XMEOUT Parameters: date, time,applid, termid, tranid, sense, instance, {1=DFHZNAC}
A DFHTC TYPE=READ request is being processed, although the previously issued DFHTC TYPE=WRITE request did not complete a chain.
For the meaning of the sense data, see DFHZCxxxx messages.
All outstanding receive requests are purged. If a task is attached, it is abnormally terminated with a transaction dump.
Correct the application program.
CSNE
DFHZRVS
XMEOUT Parameters: date, time,applid, termid, tranid, sense, instance, {1=DFHZRVS}
The logical unit detected a failure of CICS to enforce bracket rules.
For the meaning of the sense data, see DFHZCxxxx messages.
All outstanding send and receive requests are purged. If a task is attached, it is abnormally terminated with a transaction dump. The session is terminated.
Message DFHME0116 is normally produced containing the symptom string for this problem.
Use the symptom string, a VTAM trace, and if necessary the dump, to determine the source of the problem.
CSNE
DFHZNAC
XMEOUT Parameters: date, time,applid, termid, tranid, sense, instance, {1=DFHZNAC}
The request/response unit (RU) received by the logical unit (LU) contains a control function with invalid parameters.
For the meaning of the sense data, see DFHZCxxxx messages.
All send and receive requests are purged. If a task is attached, it is abnormally terminated with a transaction dump. A portion of the TIOA is put to the CSNE log.
Correct the application program.
CSNE
DFHZNAC
XMEOUT Parameters: date, time,applid, termid, tranid, sense, instance, {1=DFHZNAC}
A request for input (for example, a READBUF command) sent to a logical unit (LU) type 2 (3270 compatibility mode logical unit) must carry the SNA change direction indicator. The LU has received such a request, but the indicator is not set.
Since the setting of the change direction indicator is controlled by terminal control, this message indicates that an internal logic error may have occurred. The error is not necessarily in terminal control, but may be in the logical unit or some other element of the network.
For the meaning of the sense data, see DFHZCxxxx messages.
The task and the VTAM session for the logical unit are abnormally terminated.
Message DFHME0116 is normally produced containing the symptom string for this problem.
Identify the request that caused the error, and locate the element of the network responsible.
CSNE
DFHZNAC
XMEOUT Parameters: date, time,applid, termid, tranid, sense, instance, {1=DFHZNAC}
The contents of data for screen presentation by a logical unit has been altered. This is usually due to operator action. For example, the TEST/NORMAL key may have been used or the 3270 SYS REQ key may have been pressed.
It may also have been caused by factors other than operator action, for example, 3270 regeneration buffer failure.
For the meaning of the sense data, see DFHZCxxxx messages.
Any outstanding requests are canceled. If a task is attached, it is abnormally terminated with a transaction dump.
Determine reason for failure at the remote terminal.
CSNE
DFHZNAC
XMEOUT Parameters: date, time,applid, termid, tranid, sense, instance, {1=DFHZNAC}
CICS received a negative response to a command for which a negative response would not normally be expected.
For the meaning of the sense data, see DFHZCxxxx messages.
All outstanding send and receive requests are purged. If a task is attached, it is abnormally terminated with a transaction dump. The node is placed out of service and the TCTTE, RPL, and action flags are logged to CSNE.
Message DFHME0116 is normally produced containing the symptom string for this problem.
Ensure that the application programs running concurrently do not alter the TCTTE. Check that the SNA flows on the session are valid and that the logical unit is not violating SNA protocols.
CSNE
DFHZRAC
XMEOUT Parameters: date, time,applid, termid, tranid, sense, instance, {1=DFHZRAC}
Input (other than a logical unit status message) was received after a request was rejected with a system sense code indicating a possibly rectifiable error condition at the terminal node: for example, Intervention Required. The subsequent LU status message indicates that the error situation has now been corrected, or that the request is permanently not executable.
For the meaning of the sense data, see DFHZCxxxx messages.
If a task is attached, it is abnormally terminated with a transaction dump.
Conform to SNA protocol by ensuring that the next transmission is an LUSTATUS message with a system sense for either Resource Available (0001) or Function Not Executable (081C).
CSNE
DFHZRVX
XMEOUT Parameters: date, time,applid, termid, tranid, sense, instance, {1=DFHZRVX, 2=DFHZRVX, 3=DFHZRVX}
A terminal resource required to complete a request is temporarily unavailable.
For the meaning of the sense data, see DFHZCxxxx messages.
The request is retried unless the device is one that sends an LUSTATUS message after receiving a "resource temporarily unavailable" notification.
If "resource temporarily unavailable" notification is received, an associated VTAM message is usually issued.
Refer to the associated VTAM message, if applicable, and follow the guidance provided.
CSNE
DFHZNAC
XMEOUT Parameters: date, time,applid, termid, tranid, sense, instance, {1=DFHZNAC}
Operator action is requested for the secondary resource of a logical unit (LU). However, no such resource is immediately available. In the case of a 3270-compatible LU, this message means that the printer most likely to be available for a PRINT request has an Intervention Required status.
For the meaning of the sense data, see DFHZCxxxx messages.
The system waits for a logical unit status message and, when this is received, takes appropriate system action.
Correct the problem that relates to the device.
CSNE
DFHZNAC
XMEOUT Parameters: date, time,applid, termid, tranid, sense, instance, {1=DFHZNAC}
The logical unit has rejected a request because its resources are busy (for example, it is communicating with the system services control point (SSCP)), and thus is unable to process the request.
For the meaning of the sense data, see DFHZCxxxx messages.
The system waits for a logical unit status message and then takes appropriate action.
None.
CSNE
DFHZNAC
XMEOUT Parameters: date, time,applid, termid, tranid, sense, instance, {1=DFHZNAC}
The secondary resource of a logical unit is permanently unavailable to complete a request. For a 3270-compatible LU, this means that a printer was not available for a PRINT request.
For the meaning of the sense data, see DFHZCxxxx messages.
All outstanding send and receive requests are purged. If a task is attached, it is abnormally terminated with a transaction dump.
Determine the reason why the resource is not available at the remote terminal.
CSNE
DFHZNAC
XMEOUT Parameters: date, time,applid, termid, tranid, sense, instance, {1=DFHZNAC}
A receive request has been rejected by the logical unit because it has no data to send for one of the following reasons:
For the meaning of the sense data, see DFHZCxxxx messages.
The receive request is halted. If a task is attached, it is abnormally terminated with a transaction dump.
Verify that the request was issued to the correct device and that the device is capable of data transmission.
CSNE
DFHZNAC
XMEOUT Parameters: date, time,applid, termid, tranid, sense, instance, {1=DFHZNAC}
The requested logon was to be rejected, but the attempt to send a negative response was rejected by VTAM.
For the meaning of the sense data, see DFHZCxxxx messages.
No further attempts are made to communicate with the invalid node.
Inspect the CSNE, CSMT and CSTL logs for an indication of a VTAM storage problem or error message. Determine whether the node was invalid. If it was valid, update the CICS TCT for that node.
CSNE
DFHZNAC
XMEOUT Parameters: date, time,applid, termid, tranid, nodeid, sense, instance, {1=DFHZSCX}
A request for a sync point to be taken was ignored. COMMIT or ABORT has not been issued.
For the meaning of the sense data, see DFHZCxxxx messages.
If a task is attached, it is abnormally terminated with a transaction dump.
To determine the cause of the problem, inspect the CSNE, CSMT and CSTL logs for further diagnostic information. Also inspect transaction tranid.
CSNE
DFHZSDR
XMEOUT Parameters: date, time,applid, termid, tranid, sense, instance, {1=DFHZSDR}
A logon request was rejected because the TCTTE for the ISC session had been generated with an incompatible SESSIONTYPE.
For the meaning of the sense data, see DFHZCxxxx messages.
The request is rejected.
Change the TCTTE generation to specify a secondary logical unit at one end of the connection, and a primary logical unit at the other end.
A primary logical unit should have SESSIONTYPE=SEND or SESSIONTYPE=FASTSEND, and a secondary logical unit should have SESSIONTYPE=RECEIVE or SESSIONTYPE=FASTRECV.
CSNE
DFHZSCX, DFHZLGX, DFHZBLX
XMEOUT Parameters: date, time,applid, termid, tranid, netname, sense, instance, {1=DFHZSCX, 2=DFHZBLX, 3=DFHZLGX}
A connection request was rejected because the characteristics specified for the connecting system were unacceptable.
Possible reasons for the rejection are:
For the meaning of the sense data, see DFHZCxxxx messages.
The request is rejected. The bind parameter is printed on the CSNE log.
Determine whether the connecting system has specified its characteristics correctly. If it has not, correct the requesting system.
CSNE
DFHZSCX
XMEOUT Parameters: date, time,applid, termid, tranid, netname, sense, instance, {1=RESERVE, 2=DFHZBLX, 3=DFHZSCX, 4=DFHZSCX, 5=DFHZBLX, 6=DFHZBLX, 7=DFHZSCX, 8=DFHZBLX, 9=DFHZBLX, 10=DFHZBLX, 11=DFHZBLX, 12=DFHZBLX, 13=DFHZBLX, 14=DFHZBLX, 15=DFHZBLX, 16=DFHZBLX, 17=DFHZBLX, 18=DFHZBLX, 19=DFHZSCX, 20=DFHZBLX, 21=DFHZBLX, 22=DFHZBLX, 23=DFHZBLX, 24=DFHZBLX, 25=DFHZBLX, 26=DFHZBLX, 27=DFHZBLX, 28=DFHZBLX, 29=DFHZSCX, 30=DFHZBLX, 31=DFHZBLX, 32=DFHZBLX, 33=DFHZBLX, 34=DFHZBLX, 35=DFHZBLX, 36=DFHZBLX, 37=DFHZBLX, 38=DFHZBLX, 39=DFHZBLX, 40=DFHZBLX, 41=DFHZBLX}
A logon request was rejected because the TCTTE is out of service.
For the meaning of the sense data, see DFHZCxxxx messages.
The request is rejected.
Place the terminal in service by using the master terminal program and reissuing the connection request.
CSNE
DFHZSCX, DFHZOPN, DFHZBLX
XMEOUT Parameters: date, time,applid, termid, tranid, netname, sense, instance, {1=DFHZOPN, 2=DFHZBLX, 3=DFHZBLX}
A shutdown request was received for the system. An orderly termination procedure has begun.
For the meaning of the sense data, see DFHZCxxxx messages.
Orderly termination of the session is started. Access to the remote system is stopped after the current transaction has finished.
None.
CSNE
DFHZASX
XMEOUT Parameters: date, time,applid, termid, tranid, netname, sense, instance, {1=DFHZASX}
An error occurred while trying to connect the two systems. The request was terminated before a session had been established.
For the meaning of the sense data, see DFHZCxxxx messages.
The request is terminated.
Determine the cause of the problem by inspecting the VTAM logs. If the problem is due to a shortage of storage or another temporary error, reissue the request when the system is less heavily loaded.
CSNE
DFHZNSP
XMEOUT Parameters: date, time,applid, termid, tranid, sense, instance, {1=DFHZNSP, 2=DFHZNSP}
CICS has received a negative response (VTAM sense code 0826). The receiver does not support the function requested by the sender.
For the meaning of the sense data, see DFHZCxxxx messages.
All outstanding SENDs and RECEIVEs are purged. If a task is attached, it is abnormally terminated with a transaction dump.
Investigate the reason for issuing a request for a function that the receiver does not support.
CSNE
DFHZNAC
XMEOUT Parameters: date, time,applid, termid, tranid, sense, instance, {1=DFHZNAC}
Communication with a node was interrupted during a session because a session outage was detected, or because a VTAM VARY INACT command was issued.
Error messages produced for the same session after this message may be caused by the session failure and may not be the reason for it. If this is the case, they can be ignored.
For the meaning of the sense data, see DFHZCxxxx messages.
The session is canceled. The session may be recovered later by VTAM. See also messages DFHZC2409 and DFHZC2410.
Check if the failure was caused by an operator-issued VTAM VARY INACT. If this is not the case, use the sense data and any associated messages to investigate the reason for the failure.
CSNE
DFHZNSP
XMEOUT Parameters: date, time,applid, termid, tranid, sense, instance, {1=DFHZNSP, 2=DFHZNSP, 3=DFHZNSP}
During intersystem connection, no matching TCTTE could be found.
For the meaning of the sense data, see DFHZCxxxx messages.
The request is terminated.
Ensure that the name of the requested TCTTE is correctly specified in the requesting system.
CSNE
DFHZNAC
XMEOUT Parameters: date, time,applid, termid, tranid, sense, instance, {1=DFHZNAC}
During intersystem connection, either one or more parameters contained in the bind area of the request were invalid, or were not supported.
For the meaning of the sense data, see DFHZCxxxx messages.
The request is terminated.
Determine which parameters in the bind area are incorrect, and correct them.
CSNE
DFHZNAC
XMEOUT Parameters: date, time,applid, termid, tranid, sense, instance, {1=DFHZNAC}
CICS did not go through a resynchronization process that was expected to occur by the other LU.
For the meaning of the sense data, see DFHZCxxxx messages.
Processing continues.
Check whether this resynchronization mismatch is acceptable.
CSNE
DFHZRSY, DFHZSYX
XMEOUT Parameters: date, time,applid, termid, tranid, sense, instance, {1=DFHZRSY, 2=DFHZRSY, 3=DFHZRSY, 4=DFHZRSY, 5=DFHZSYX}
The transaction is communicating with a logical unit (LU) type LU6.1 or LU6.2.
The logical unit sent an FMH7 which may carry error log data. If error log data is included, then the text is inserted in this message.
For the meaning of the sense data, see DFHZCxxxx messages.
The action taken depends upon the sense code.
If the receiving transaction is designed to handle this situation, no action is necessary. However, if this is not the case, use the sense code and any error log data to determine why the connected logical unit sent the FMH7.
If the connected LU is another CICS system, the error log data is a CICS message.
If the connected LU is not a CICS system, see that product’s documentation for details of error log data. Some products permit the user to define the contents of error log data.
CSNE
DFHZRVX, DFHZRAC, DFHZERH
XMEOUT Parameters: date, time,applid, termid, tranid, xxxxxxxx, {1= Error log data is : , 2=No error log data received. , 3=No error log data available. }, xxxxxxxx, sense, instance, {1=DFHZRVX, 2=DFHZRAC, 3=DFHZRAC, 4=DFHZERH}
One side of the intersystem link (secondary) received an unbind command without normal termination protocol being observed. This means an abnormal termination of the session was performed, possibly caused by the other side of the intersystem link abnormally terminating.
For the meaning of the sense data, see DFHZCxxxx messages.
The session is terminated.
Determine the cause of the termination by using CICS Trace and the diagnostic information available on the CSNE log. Try to reestablish the session.
CSNE
DFHZSCX
XMEOUT Parameters: date, time,applid, termid, tranid, sense, instance, {1=DFHZSCX, 2=DFHZSCX, 3=DFHZSCX, 4=DFHZSCX, 5=DFHZSCX, 6=DFHZSCX, 7=DFHZSCX, 8=DFHZSCX, 9=DFHZSCX, 10=DFHZSCX}
VTAM can no longer transmit to a device because there is no access path to that device. This usually occurs because the device or 3270 has been powered off.
For the meaning of the sense data, see DFHZCxxxx messages.
All outstanding send and receive requests are purged. If a task is attached, it is abnormally terminated with a transaction dump. Communication with the node is terminated by issuing a VTAM CLSDST macro, and the node is placed out of service. The session is terminated.
Determine the cause of the termination. Try to reestablish the session.
CSNE
DFHZNAC
XMEOUT Parameters: date, time,applid, termid, tranid, sense, instance, {1=DFHZNAC}
A sense code has been received specifying that an unauthorized request was made to the remote node. The request was rejected.
For the meaning of the sense data, see DFHZCxxxx messages.
The session is terminated.
Determine why the end user is not authorized to perform the request.
CSNE
DFHZNAC
XMEOUT Parameters: date, time,applid, termid, tranid, sense, instance, {1=DFHZNAC}
After an error has been processed by DFHZNAC, certain actions may be taken to correct the error. This message indicates the actions that were set. The actions taken can differ from the actions set, depending on the type and state of the node at the time of the error.
The user action depends on what action has been taken by the system. This is indicated by action in the message text.
CSNE
DFHZNAC
XMEOUT Parameters: date, time,applid, termid, tranid, netname, action, instance, {1=DFHZNAC}
A request has been rejected by the logical unit because the associated device has been powered off. This message may be caused by operator action. For example, the TEST/NORMAL key may have been used.
For the meaning of the sense data, see DFHZCxxxx messages.
The system waits for a logical unit status message and, when the message has been received, takes appropriate system action.
Correct the problem that relates to the device.
For the meaning of the sense codes, refer to the explanatory paragraph in message DFHZC2461.
CSNE
DFHZNAC
XMEOUT Parameters: date, time,applid, termid, tranid, sense, instance, {1=DFHZNAC}
A negative response has been received to the START DATA TRAFFIC (SDT) command.
For the meaning of the sense data, see DFHZCxxxx messages.
Processing continues.
None.
CSNE
DFHZNAC
XMEOUT Parameters: date, time,applid, termid, tranid, sense, instance, {1=DFHZNAC}
DFHZEMW was attempting to write a message to another node, but was unable to do so because the session was in "between bracket" status.
In this state, it is not possible to send the message in the normal way. The session was in free status, probably because the application program had issued a SEND command with the LAST option.
For the meaning of the sense data, see DFHZCxxxx messages.
Processing continues.
Check to see why the other node sent its request EXCEPTION response mode. Change the response mode to DEFINITE if error messages are to be sent.
CSNE
DFHZEMW
XMEOUT Parameters: date, time,applid, termid, tranid, sense, instance, {1=DFHZEMW, 2=DFHZEMW}
A request for an orderly close of VTAM sessions and subsequent close of CICS VTAM ACB has been received. The request may have been initiated by the CICS master terminal command or by the VTAM network closing down.
For the meaning of the sense data, see DFHZCxxxx messages.
All nodes are quiesced and each session is closed as it becomes inactive. When all sessions have been closed, the ACB is closed.
None.
CSNE
DFHZSHU
XMEOUT Parameters: date, time,applid, sense, instance, {1=DFHZSHU}
A request for an immediate close of all VTAM sessions and subsequent close of CICS VTAM ACB has been received. The request may have been initiated by the CICS master terminal command or by the VTAM network closing down.
This message is also issued if V NET,ID=...,INACT is issued by the VTAM operator.
For the meaning of the sense data, see DFHZCxxxx messages.
All requests on a VTAM session are abnormally terminated and the session is closed. The VTAM ACB is then closed.
If V NET,ID=...,INACT was issued by the VTAM operator, VTAM waits for all sessions to be closed before informing CICS. In this case there are no sessions to be abnormally terminated. This message may be issued twice, once by DFHZTPX and once by DFHZSHU. The messages will have different instance numbers.
None.
CSNE
DFHZSHU, DFHZTPX
XMEOUT Parameters: date, time,applid, sense, instance, {1=DFHZSHU, 2=RESERVE, 3=RESERVE,4=DFHZTPX, 5=DFHZSHU}
VTAM has been cancelled or force closed by the CICS/VTAM operator.
For the meaning of the sense data, see DFHZCxxxx messages.
CICS will close its ACB. All transactions running on VTAM sessions are abnormally terminated.
None.
CSNE
DFHZSHU, DFHZTPX, DFHZSYX
XMEOUT Parameters: date, time,applid, sense, instance, {1=DFHZSHU, 3=DFHZSYX, 4=DFHZTPX,5=DFHZSHU}
CICS has detected that more than 32k of data has been transmitted
while receiving data from terminal "termid".
For the meaning of the sense data, see DFHZCxxxx messages.
CICS terminates the session and places the terminal out of service. If a task is attached, it is abnormally terminated with a transaction dump.
Message DFHME0116 is normally produced containing the symptom string for this problem.
To determine the cause of this error,
CSNE
DFHZRVS, DFHZRAC
XMEOUT Parameters: date, time,applid, termid, tranid, sense, instance, {1=DFHZRVS, 2=DFHZRAC}
CICS has received a state error negative response (VTAM sense code 20yy).
For the meaning of the sense data, see DFHZCxxxx messages.
All outstanding send and receive requests are purged. If a task is attached, it is abnormally terminated with a transaction dump. Communication with the node is terminated by issuing a VTAM CLSDST macro, and the node is placed out of service.
Determine the reason for the error before restarting the session.
CSNE
DFHZNAC
XMEOUT Parameters: date, time,applid, termid, tranid, sense, instance, {1=DFHZNAC}
CICS has received a request error negative response (VTAM sense code 10yy) for which it does not recognize the minor code yy.
For the meaning of the sense data, see DFHZCxxxx messages.
All outstanding send and receive requests are purged. If a task is attached, it is abnormally terminated with a transaction dump. Communication with the node is terminated by issuing a VTAM CLSDST macro, and the node is placed out of service.
Determine the reason for the error.
CSNE
DFHZNAC
XMEOUT Parameters: date, time,applid, termid, tranid, sense, instance, {1=DFHZNAC}
CICS has received a request reject negative response (VTAM sense code 08yy) for which it does not recognize the minor code yy.
For the meaning of the sense data, see DFHZCxxxx messages.
All outstanding send and receive requests are purged. If a task is attached, it is abnormally terminated with a transaction dump. Communication with the node is terminated by issuing a VTAM CLSDST macro, and the node is placed out of service.
Determine the reason for the error.
CSNE
DFHZNAC
XMEOUT Parameters: date, time,applid, termid, tranid, sense, instance, {1=DFHZNAC}
CICS has received a negative response to a request to access a resource because it was not authorized. If it was an OPNDST (BIND) request, CICS did not send the authorization sequence expected by a logical unit. CICS does not support the security feature in the bind.
For the meaning of the sense data, see DFHZCxxxx messages.
The logical unit is placed out of service and the session is closed.
CICS does not support the security feature in the bind. Modify the authorization parameters in the remote logical unit so that it does not require authorization to initiate a session.
CSNE
DFHZNAC
XMEOUT Parameters: date, time,applid, termid, tranid, sense, instance, {1=DFHZNAC}
CICS has received a status message from a logical unit indicating that the terminal is now attended.
Note that this is the default mode of operation.
For the meaning of the sense data, see DFHZCxxxx messages.
The mode of operation bit TCTEMOPU is reset in the TCTTE.
For logical units that can operate in unattended mode, the application programmer should test the mode of operation before starting a conversational sequence with the terminal operator. If the bit is on, no operator action can be expected.
For command level, use the EXEC CICS ASSIGN UNATTEND (data area) command to obtain the value of TCTEMOPU.
CSNE
DFHZNAC
XMEOUT Parameters: date, time,applid, termid, tranid, sense, instance, {1=DFHZNAC}
CICS has received a status message from a logical unit indicating that the terminal is no longer attended.
For the meaning of the sense data, see DFHZCxxxx messages.
The mode of operation bit TCTEMOPU is set in the TCTTE.
For logical units that can operate in unattended mode, the application programmer should test the mode of operation before starting a conversational sequence with the terminal operator. If the bit is on, no operator action can be expected.
For command level, use the EXEC CICS ASSIGN UNATTEND (data area) command to obtain the value of TCTEMOPU.
CSNE
DFHZNAC
XMEOUT Parameters: date, time,applid, termid, tranid, sense, instance, {1=DFHZNAC}
Following the issue of a READ command to a logical unit, or the completion of a transaction associated with the logical unit, CICS has received a status message from the logical unit indicating that it currently has no data to send.
For the meaning of the sense data, see DFHZCxxxx messages.
If a data interchange (DFHDI) receive request is outstanding, it will complete with DSSTAT condition and a response code X'15'.
If no task is active and no work is outstanding for the terminal, the soft CLSDEST action flag is set and DFHZNEP is called. Unless it is reset by DFHZNEP, the session is terminated.
Ensure that no more receive requests are issued to the terminal.
CSNE
DFHZNAC
XMEOUT Parameters: date, time,applid, termid, tranid, sense, instance, {1=DFHZNAC}
CICS has received a SIGNAL command from a logical unit. The SIGNAL codes received with the SIGNAL command are made available to the DFHZNEP user program.
If a task is active, the SIGNAL condition is raised on return to the application program. This message is produced only when SIGNAL codes are passed to the node abnormal condition program (DFHZNAC). CICS does this for Type 4 logical units only.
For the meaning of the sense data, see DFHZCxxxx messages.
If the SIGNAL code is 0001 0000 (request change direction), any further output request will cause the IGREQCD condition to be raised. All SIGNAL codes will cause the SIGNAL condition to be raised.
For logical units for which CICS enforces SIGNAL request change direction, if the code is 0001 0000, issue a receive request or terminate transaction tranid.
If the code is NOT 0001 0000, terminate transaction tranid and refer to the VTAM Programming manual for further guidance.
CSNE
DFHZASX
XMEOUT Parameters: date, time,applid, termid, tranid, xxxx, sense, instance, {1=DFHZASX, 2=DFHZASX}
CICS has received a request header (RH) usage error negative response for which it does not recognize the minor code yy.
For the meaning of the sense data, see DFHZCxxxx messages.
All outstanding send and receive requests are purged. If a task is attached, it is abnormally terminated with a transaction dump. Communication with the node is terminated by issuing a VTAM CLSDST macro, and the node is placed out of service.
None.
CSNE
DFHZNAC
XMEOUT Parameters: date, time,applid, termid, tranid, sense, instance, {1=DFHZNAC}
A remote secondary’s response to a negotiable bind contained unacceptable parameters.
For the meaning of the sense data, see DFHZCxxxx messages.
Session initialization fails. The sent and received bind parameters are printed on the CSNE log.
Look at the parameters printed on the CSNE log. Ensure that the remote system has correctly specified its characteristics. If there is an invalid format, change it to LEN PSQ LEN SSQ.
CSNE
DFHZOPX
XMEOUT Parameters: date, time,applid, termid, tranid, netname, sense, instance, {1=DFHZOPX, 2=DFHZOPX, 3=DFHZOPX, 4=DFHZOPX, 5=DFHZOPX, 6=DFHZOPX, 7=DFHZOPX, 8=DFHZOPX, 9=DFHZOPX, 10=DFHZOPX, 11=DFHZOPX, 12=DFHZOPX, 13=DFHZOPX, 14=DFHZOPX, 15=DFHZOPX, 16=DFHZOPX, 17=DFHZOPX, 18=DFHZOPX, 19=DFHZOPX, 20=DFHZOPX, 21=DFHZOPX, 22=DFHZOPX, 23=DFHZOPX, 24=DFHZOPX, 25=DFHZOPX, 26=DFHZOPX, 27=DFHZOPX, 28=DFHZOPX, 29=DFHZOPX, 30=DFHZOPX, 31=DFHZOPX, 32=DFHZOPX, 33=DFHZOPX, 34=DFHZOPX, 35=DFHZOPX, 36=DFHZOPX, 37=DFHZOPX, 38=DFHZOPX, 39=DFHZOPX, 40=DFHZOPX, 41=DFHZOPX, 42=DFHZOPX, 43=DFHZOPX, 44=DFHZOPX, 45=DFHZOPX}
A remote secondary’s response to a negotiable bind contained an invalid session qualifier pair in the user data field. Either it had an invalid format, or the primary SQ had been altered.
For the meaning of the sense data, see DFHZCxxxx messages.
Session initialization fails. The sent and received bind images are printed on the CSNE log.
Correct the error in the remote system. If there is an invalid format, change it to LEN PSQ LEN SSQ.
CSNE
DFHZOPX
XMEOUT Parameters: date, time,applid, termid, tranid, netname, sense, instance, {1=DFHZOPX, 2=DFHZOPX, 3=DFHZOPX}
An outboard format has been referenced, but no outboard formats are loaded on this logical unit.
Transaction tranid is abnormally terminated with a transaction dump.
Load the necessary outboard formats.
CSNE
DFHZNAC
XMEOUT Parameters: date, time,applid, termid, tranid, sense, instance, {1=DFHZNAC}
An outboard format has been referenced, but the requested format is not loaded on this logical unit.
For the meaning of the sense data, see DFHZCxxxx messages.
Transaction tranid is abnormally terminated with a transaction dump.
Load the requested outboard format.
CSNE
DFHZNAC
XMEOUT Parameters: date, time,applid, termid, tranid, sense, instance, {1=DFHZNAC}
An outbound format group has been referenced, but that format group is not loaded on this logical unit.
For the meaning of the sense data, see DFHZCxxxx messages.
Transaction tranid is abnormally terminated with a transaction dump.
Load the required format group.
CSNE
DFHZNAC
XMEOUT Parameters: date, time,applid, termid, tranid, sense, instance, {1=DFHZNAC}
The data stream sent to the device contains control data for functions that the device does not support.
For the meaning of the sense data, see DFHZCxxxx messages.
Transaction tranid is abnormally terminated.
Either ensure that transaction tranid is not run against the terminal, or change the terminal to one that supports the data stream.
CSNE
DFHZNAC
XMEOUT Parameters: date, time,applid, termid, tranid, sense, instance, {1=DFHZNAC}
The Referenced Logical Character Set Identifier (LCID) specified in the define alternate character set is not known.
For the meaning of the sense data, see DFHZCxxxx messages.
Transaction tranid is abnormally terminated with a transaction dump.
Ensure that the character set referenced by the LCID is loaded.
CSNE
DFHZNAC
XMEOUT Parameters: date, time,applid, termid, tranid, sense, instance, {1=DFHZNAC}
CICS has successfully issued or received a bind to the node netname.
For the meaning of the sense data, see DFHZCxxxx messages.
Processing continues.
None.
CSNE
DFHZOPX, DFHZEV1, DFHZEV2
XMEOUT Parameters: date, time,applid, termid, tranid, netname, sense, instance, {1=DFHZOPX, 2=DFHZOPX, 3=DFHZEV1, 4=DFHZEV2}
A session with node netname has been closed.
For the meaning of the sense data, see DFHZCxxxx messages.
Processing continues.
None.
CSNE
DFHZCLS
XMEOUT Parameters: date, time,applid, termid, tranid, netname, sense, instance, {1=DFHZCLS, 2=DFHZCLS}
The master terminal operator issued a CEMT or CSMT command to open the VTAM ACB.
For the meaning of the sense data, see DFHZCxxxx messages.
Processing continues.
This depends on the return code:
CSNE
DFHZOPA
XMEOUT Parameters: date, time,applid, X'rc', time, sense, instance, {1=DFHZOPA}
The master terminal operator issued a CEMT command to release the logical unit (LU).
For the meaning of the sense data, see DFHZCxxxx messages.
The LU is closed. Any task associated with the LU is terminated either abnormally (if the master terminal operator so desired) or normally.
None.
CSNE
DFHZSTU
XMEOUT Parameters: date, time,applid, termid, tranid, netname, sense, instance, {1=DFHZSTU}
CICS received a positive response in one of the following circumstances:
For the meaning of the sense data, see DFHZCxxxx messages.
All outstanding send and receive requests are purged. If a task is attached, it is abnormally terminated with a transaction dump. The node is placed out of service and the TCTTE, RPL, and action flags are logged to CSNE.
Ensure that the application programs running concurrently do not alter the TCTTE. Check that the SNA flows on the session are valid and that the logical unit is not violating SNA protocols.
CSNE
DFHZRVX, DFHZRAC, DFHZRLP
XMEOUT Parameters: date, time,applid, termid, tranid, sense, instance, {1=DFHZRLP, 2=DFHZRVX, 3=DFHZRVX, 4=DFHZRVX, 5=DFHZRVX, 6=DFHZRAC, 7=DFHZRAC, 8=DFHZRAC, 9=DFHZRAC, 10=DFHZRAC, 11=DFHZRAC, 12=DFHZRAC}
A CICS master terminal command was used to put terminal termid out of service while session startup was taking place.
For the meaning of the sense data, see DFHZCxxxx messages.
The session is terminated and the TCTTE for terminal termid is left out of service.
To establish the session for use, the master terminal operator should issue the command CEMT SET TER (XXXX) INS ACQ. This puts the terminal back in service, and start up the session for use.
CSNE
DFHZSEX, DFHZSKR
XMEOUT Parameters: date, time,applid, termid, tranid, sense, instance, {1=DFHZSEX, 2=DFHZSKR}
The PS buffer resource required by load PS is not available.
For the meaning of the sense data, see DFHZCxxxx messages.
If a task is attached, it is abnormally terminated with a transaction dump.
Look at the CSNE log. A second message with a sense received code of 084C should have been issued. Refer to this message in the VTAM Programming manual for full details.
CSNE
DFHZNAC
XMEOUT Parameters: date, time,applid, termid, tranid, sense, instance, {1=DFHZNAC}
An SNA clear command was received by the node. The other end of the session was unable to handle the current requests for some reason, and purged any outstanding messages on the session.
For the meaning of the sense data, see DFHZCxxxx messages.
The session is canceled immediately, and any transaction executing on that session is also abnormally terminated and a transaction dump is produced.
Check the other end of the session to determine why the clear command was sent. It may be due to a lack of buffers in the VTAM region attached to the other session.
CSNE
DFHZSCX
XMEOUT Parameters: date, time,applid, termid, tranid, sense, instance, {1=DFHZSCX}
The secondary LU is being passed to a new application program via CLSDST(PASS).
For the meaning of the sense data, see DFHZCxxxx messages.
If a task is attached, it is abnormally terminated with a transaction dump.
None.
CSNE
DFHZSCX
XMEOUT Parameters: date, time,applid, termid, tranid, sense, instance, {1=DFHZSCX}
An LU session has failed because an UNBIND command has been received.
Possible reasons are:
For the meaning of the sense data, see DFHZCxxxx messages.
If a task is attached, it is abnormally terminated with a transaction dump.
Use the symptom string, a VTAM trace, and the dump, if available, to determine the source of the UNBIND before attempting to reestablish the session.
CSNE
DFHZSCX
XMEOUT Parameters: date, time,applid, termid, tranid, {1=restart/takeover. LU does not support ACTLU(ERP).,2=route extension to cluster failed., 3=LU abend, discontact, DACTPU or ANS. }, sense,instance, {1=DFHZSCX, 2=DFHZSCX, 3=DFHZSCX, 4=DFHZSCX}
The session has been broken because the virtual route it was using has failed.
For the meaning of the sense data, see DFHZCxxxx messages.
If a task is attached, it is abnormally terminated with a transaction dump. For APPC sessions, CICS attempts to reestablish the failing session.
None.
CSNE
DFHZSCX
XMEOUT Parameters: date, time,applid, termid, tranid, sense, instance, {1=DFHZSCX}
Device end was received from a non-SNA VTAM supported 3270
For the meaning of the sense data, see DFHZCxxxx messages.
The good morning message is displayed, unless the terminal is associated with an active task.
None.
CSNE
DFHZSYX
XMEOUT Parameters: date, time,applid, termid, tranid, sense, instance, {1=DFHZSYX}
The session has had to be deactivated because of a forced deactivation of the virtual route being used.
For the meaning of the sense data, see DFHZCxxxx messages.
If a task is attached, it is abnormally terminated with a transaction dump. Afterwards CICS attempts to reestablish the session.
Determine the cause of the session failure and attempt to reestablish the session.
CSNE
DFHZSCX
XMEOUT Parameters: date, time,applid, termid, tranid, sense, instance, {1=DFHZSCX}
The session has had to be deactivated because of an abnormal termination of an LU.
For the meaning of the sense data, see DFHZCxxxx messages.
If a task is attached, it is abnormally terminated with a transaction dump. Session reinitiation is not attempted.
None.
CSNE
DFHZSCX
XMEOUT Parameters: date, time,applid, termid, tranid, sense, instance, {1=DFHZSCX}
The session has had to be deactivated because of an abnormal termination of an LU; recovery of the session may be possible.
For the meaning of the sense data, see DFHZCxxxx messages.
If a task is attached, it is abnormally terminated with a transaction dump. CICS attempts to reinitiate the session.
None.
CSNE
DFHZSCX
XMEOUT Parameters: date, time,applid, termid, tranid, sense, instance, {1=DFHZSCX}
The sending LU has reset its half-session before receiving a response from CICS; recovery of the session may be possible.
For the meaning of the sense data, see DFHZCxxxx messages.
If a task is attached, it is abnormally terminated with a transaction dump. CICS attempts to reinitiate the session.
None.
CSNE
DFHZSCX
XMEOUT Parameters: date, time,applid, termid, tranid, sense, instance, {1=DFHZSCX}
The logical unit in session with CICS has detected a session failure, and has unbound the session with CICS.
For the meaning of the sense data, see DFHZCxxxx messages.
The session is terminated, and the transaction using it is abnormally terminated or informed by return code.
Determine the reason for the session failure by using Trace. Check the CSNE log for a second error message associated with DFHZC3479. This message should be located immediately after DFHZC3479.
Refer to the sense code shown in the associated message.
CSNE
DFHZSCX
XMEOUT Parameters: date, time,applid, termid, tranid, sense, instance, {1=DFHZSCX, 2=DFHZSCX}
A session initiation has been attempted to an APPC system or terminal. The session cannot be established because the CICS ISC nucleus modules are required.
For the meaning of the sense data, see DFHZCxxxx messages.
The session initiation request is rejected.
If APPC connections are to be used, ensure that ISC=NO is not used for CICS initialization.
CSNE
DFHZSCX, DFHZLGX, DFHZSIM
XMEOUT Parameters: date, time,applid, termid, tranid, sense, instance, {1=DFHZSIM, 2=DFHZBLX, 3=DFHZLGX}
CICS has received zero length data from a device defined in the TCT as a 3270 terminal. This violates the protocol for 3270 devices.
For the meaning of the sense data, see DFHZCxxxx messages.
CICS cancels the session and any transactions attached to the terminal.
Determine why zero length data was received from a device purporting to be a 3270 terminal, and correct the error.
The most likely reasons are an incorrect TCT definition for the terminal, or incorrect programming of a terminal that is simulating 3270 protocols.
CSNE
DFHZRAC, DFHZRVX
XMEOUT Parameters: date, time,applid, termid, tranid, sense, instance, {1=DFHZRVX, 2=DFHZRAC}
A node nodeid, unknown to CICS, attempted to logon. CICS could not obtain sufficient storage to complete autoinstall processing.
For the meaning of the sense data, see DFHZCxxxx messages.
CICS rejects the logon request.
Retry the logon.
CSNE
DFHZLGX, DFHZSCX, DFHZBLX
XMEOUT Parameters: date, time,applid, tranid, nodeid, sense, instance, {1=DFHZLGX, 2=DFHZLGX, 3=DFHZBLX, 4=DFHZSCX}
By successful execution of an ISSUE PASS command, a VTAM logical unit whose network name is netname has been passed to the VTAM application whose VTAM APPLID (netname) is applid.
For the meaning of the sense data, see DFHZCxxxx messages.
CICS processing continues.
None.
CSNE
DFHZNSP
XMEOUT Parameters: date, time,applid, netname, applid, sense, instance, {1=DFHZNSP}
In executing an ISSUE PASS command, CICS attempted to pass control of a VTAM logical unit whose network name is netname, to a system whose VTAM APPLID is applid. VTAM has notified CICS of an error at applid.
For the meaning of the sense data, see DFHZCxxxx messages.
CICS saves the status byte xx and reason byte yy passed by VTAM in the Notify Request Unit. CICS processing continues.
The reason for the error can be determined by investigating the status byte xx and reason byte yy given in the message. These bytes are documented in the NSEXIT routine section of VTAM Programming (SC23-0115).
CSNE
DFHZNSP
XMEOUT Parameters: date, time,applid, netname, applid, xx, yy, sense, instance, {1=DFHZNSP}
In executing an ISSUE PASS command, CICS attempted to pass control of a VTAM logical unit whose network name is netname, to a system whose VTAM APPLID is applid. VTAM has notified CICS that applid is currently not available.
For the meaning of the sense data, see DFHZCxxxx messages.
Processing continues.
None.
CSNE
DFHZSYX
XMEOUT Parameters: date, time,applid, netname, applid, sense, instance, {1=DFHZSYX, 2=DFHZSYX}
In executing an ISSUE PASS command, CICS attempted to pass control of a VTAM logical unit whose network name is netname. VTAM has notified CICS that CICS is not authorized to use this function.
For the meaning of the sense data, see DFHZCxxxx messages.
CICS continues.
CICS may or may not be able to display the applid it was being passed. If CICS can display this applid, it appears in the text of this message.
To use the ISSUE PASS command, you must code AUTH=PASS on the VTAM definition of the CICS APPL, then reactivate the APPL.
CSNE
DFHZLEX
XMEOUT Parameters: date, time,applid, netname, nodeid, sense, instance, {1=DFHZLEX, 2=DFHZLEX}
A simlogon request to an ISC system was rejected because the netname was not known. CICS has now issued the INQUIRE OPTCD=USERVAR command in order to determine if netname had been defined as a user variable. That INQUIRE command has been rejected because the user variable does not exist in the USERVAR table. This may be because the USERVAR is either not known or invalid, or the MODIFY USERVAR command has not been issued to define the user variable.
For the meaning of the sense data, see DFHZCxxxx messages.
CLSDST is issued to reset the session.
Determine if the netname has been defined correctly to CICS. If the netname is to be used as a user variable then determine why the MODIFY USERVAR command has not been issued to set it.
CSNE
DFHZSIX
XMEOUT Parameters: date, time,applid, netname, sense, instance, {1=DFHZSIX}
CICS has attempted to acquire a session to the logical unit (LU), but VTAM has rejected the request because the LU is inhibited for sessions.
The partner LU could be inhibited because it has issued the VTAM macro SETLOGON OPTCD=QUIESCE.
For the meaning of the sense data, see DFHZCxxxx messages.
The request is rejected and the session is set into NOINTLOG state to prevent further requests being issued.
After the partner LU has enabled itself, it can initiate the session request to CICS. Alternatively, the CICS master terminal operator could reset the NOINTLOG state and allow CICS to initiate the session request.
CSNE
DFHZSYX
XMEOUT Parameters: date, time,applid, netname, sense, instance, {1=DFHZSYX}
In executing an ISSUE PASS command, CICS attempted to pass control of the named VTAM logical unit to a system identified as node nodeid. VTAM has notified CICS that this request has failed.
This may occur if the LUNAME specified is a generic resource name and this CICS is the only system registered under this name. You are effectively passing the terminal to yourself.
However, if there is more than one CICS registered under the generic resource name, the terminal should pass successfully to another member (chosen by VTAM) in the same resource.
For the meaning of the sense data, see DFHZCxxxx messages.
A VTAM CLSDST macro is issued to halt communication with the node.
Ensure that the node nodeid is defined and active to VTAM.
CSNE
DFHZSYX, DFHZLEX, DFHZCLX
XMEOUT Parameters: date, time,applid, netname, nodeid, sense, instance, {1=DFHZLEX, 2=DFHZSYX, 3=DFHZCLX}
The active CICS system has attempted to OPNDST the session as "XRF capable", but has been refused because the Network Control Program (NCP) has insufficient space to hold the control blocks for a future backup session from the alternate CICS system.
For the meaning of the sense data, see DFHZCxxxx messages.
CICS performs a SIMLOGON, but does not deem the session to be "XRF capable". CICS therefore treats the terminal as class 2.
No immediate action is necessary. You may need to increase the number of buffers in the NCP.
CSNE
DFHZLEX
XMEOUT Parameters: date, time,applid, netname, sense, instance, {1=DFHZLEX}
DFHZLGX has been driven for SIMLOGON with a token that is no longer a valid TCTTE address.
For the meaning of the sense data, see DFHZCxxxx messages.
An unexpected condition has occurred during SIMLOGON. CICS will continue processing normally.
None.
CSNE
DFHZLGX
XMEOUT Parameters: date, time,applid, tranid, nodeid, sense, instance, {1=DFHZLGX}
A print function was requested on a 3270 information display system. However, the print function was unable to find an eligible printer because the function does not support the device type.
For the meaning of the sense data, see DFHZCxxxx messages.
If no other action is specified in the Network Error Program (NEP). the print request is halted. CICS processing continues.
Check that the printers specified for the information display system are valid. Valid devices are 3270P and LUTYPE3.
CSNE
DFHZARQ
XMEOUT Parameters: date, time,applid, termid, tranid, sense, instance, {1=DFHZARQ}
The request unit (RU) received by the secondary logical unit (LU) contains a request which terminal termid cannot handle.
For the meaning of the sense data, see DFHZCxxxx messages.
All send and receive requests are purged and transaction tranid is abnormally terminated with a dump.
Check that the TYPETERM specifications for terminal termid are valid. This error could occur if, for example, QUERY was sent to a nonqueriable 3270 defined with QUERY=COLD|ALL.
CSNE
DFHZSYX
XMEOUT Parameters: date, time,applid, termid, tranid, sense, instance, {1=DFHZNAC}
A terminal with netname netname has logged on before a NOTIFY request was received for an outstanding CLSDST PASS with CLSDST=NOTIFY.
For the meaning of the sense data, see DFHZCxxxx messages.
CICS processing continues. Any subsequent NOTIFY requests for the terminal identified will be ignored.
It is recommended that any user processing for CLSDST PASS messages incorporates this message.
CSNE
DFHZLGX
XMEOUT Parameters: date, time,applid, netname, sense, instance, {1=DFHZLGX}
Terminal termid has been found to be in error by terminal control.
As terminal termid had no task attached to it at the time of the error, DFHZNAC was unable to cause a transaction abend with a transaction dump.
The TWAODNTA flag in the DFHZNAC-DFHZNEP commarea is set ON and DFHZNAC produces a system dump for terminal termid instead.
An exception trace entry is made in the trace table at trace point FC73.
A system dump is produced unless you have specifically suppressed dumps in the dump table.
To determine the nature of the problem that caused the dump to be taken, refer to the CSNE log. There should be an associated CICS message which will provide further information.
For more information about TWAODNTA, refer to the CICS Customization Guide.
CSNE
DFHZNAC
XMEOUT Parameters: date, time,applid, termid, instance, {1=DFHZNAC}
While processing an error for a VTAM terminal, CICS attempted to link to user-replaceable module DFHZNEP. The link failed.
See message DFHZC3437 for the default action or actions taken.
The default action or actions set by DFHZNAC are taken.
The reason for the failure is specified in the message. Possible solutions are:
CSNE
DFHZNAC
XMEOUT Parameters: date, time,applid, {1=module DFHZNEP is not AMODE 31., 2=module DFHZNEP could not be loaded., 3=module DFHZNEP could not be autoinstalled., 4=of an unexpected error.}, instance, {1=DFHZNAC}
While processing an error for a VTAM terminal, user-replaceable module DFHZNEP was linked and the program abended with abend code abcode. See message DFHZC3437 for the default action or actions that are taken.
Control is passed back to the calling module, DFHZNAC. DFHZNAC reinstates the default actions set before DFHZNEP was called. The actions are then taken.
Refer to abend code abcode for details of the original error. Follow the user response given in the abend code to solve the problem.
CSNE
DFHZNAC
XMEOUT Parameters: date, time,applid, abcode, instance, {1=DFHZNAC}
An error has been detected by module modname. The OS GETMAIN request by this module has failed with return code X'return_code', and as a result, the diagnostic information relating to the original error has not been saved and cannot be processed by DFHZNAC.
The only information available for diagnosis of the error is message_number which is the number of the message that would have been issued had the OS GETMAIN request not failed.
For the meaning of the sense data, see DFHZCxxxx messages.
Processing continues normally.
Refer to message message_number for further guidance.
Refer to the MVS System Programming Library: Macro Reference for the meaning of the OS GETMAIN return code.
CSNE
DFHZATA, DFHZLGX, DFHZRAC, DFHZSCX, DFHZSHU, DFHZTPX, DFHZLEX, DFHZSYX
XMEOUT Parameters: date, time,applid, modname, X'return_code',message_number, sense, instance,{1=DFHZLEX, 2=DFHZSHU, 3=DFHZSCX, 4=DFHZSCX, 5=DFHZSYX, 6=DFHZSYX, 7=DFHZTPX, 8=DFHZRAC, 9=DFHZRAC, 10=DFHZATA, 11=DFHZLGX, 12=DFHZLGX}
A CHANGE-NUMBER-OF-SESSIONS command has been sent or received. The inserts are identified as follows:
If the "values amended" option is displayed, the values of the n1 (maximum session count) and n2 (maximum source contention winner sessions) have been renegotiated by the target system.
If the "race detected" option is displayed, the CNOS command could not be implemented because the modename modename was already locked for a CNOS command from the other system.
If a modename of ALL is produced, it has been set internally by
CICS and all of the modegroups for this connection will be affected
by the CNOS command.
If the "CNOS failed" option is displayed, the CNOS
command could not be implemented because the modename lock
was still held on the remote system when a second CNOS
command was sent by this CICS, as the CNOS race winner,
following a previous CNOS race condition.
The negotiated values are applied.
None.
CSNE
DFHZGCN
XMEOUT Parameters: date, time,applid, termid, tranid, {1=sent to, 2=received from}, netname, sysid, modename, n1,n2, {1=race detected, 2=successful, 3=values amended, 4=modename not recognized, 5=modename closed, 6=CNOS failed}, instance, {1=DFHZGCN}
This message follows message DFHZC4900 when the maximum session count (n1) and the maximum source contention winner sessions (n2) have been renegotiated.
If a modename of ALL is produced, it has been set internally by
CICS and all of the modegroups for this connection will be affected
by the CNOS command.
The negotiated values are applied.
None.
CSNE
DFHZGCN
XMEOUT Parameters: date, time,applid, termid, tranid, netname, sysid, modename, n1,n2, instance, {1=DFHZGCN}
A request to attach a task has been received across an APPC link. However, there is an error in the function management header (FMH) length or in the length of one of the subfields. As a result, CICS is unable to determine which task to attach.
For the meaning of the sense data, see DFHZCxxxx messages.
The task is abnormally terminated with a dump.
The remote APPC system is sending an invalid attach header (FMH type 5). Use the supplied dump to determine the error and investigate the cause at the remote system.
CSNE
DFHZATT
XMEOUT Parameters: date, time,applid, termid, tranid, sense, instance, {1=DFHZATT, 2=DFHZATT, 3=DFHZATT, 4=DFHZATT, 5=DFHZATT, 6=DFHZATT, 7=DFHZATT}
A request to attach a task has been received across an APPC link. However, no APPC attach header has been found at the start of the input data stream.
For the meaning of the sense data, see DFHZCxxxx messages.
The task is abnormally terminated with a dump.
The remote APPC system is failing to send a valid attach header (FMH type 5). Use the supplied dump to determine the error and investigate the cause at the remote system.
CSNE
DFHZATT, DFHZRAC
XMEOUT Parameters: date, time,applid, termid, tranid, sense, instance, {1=DFHZATT, 2=DFHZATT, 3=DFHZRAC}
The bracket finite state machine (FSM) has reported an error in the use of APPC bracket protocols.
For the meaning of the sense data, see DFHZCxxxx messages.
The task is abnormally terminated with a dump.
Message DFHME0116 is normally produced containing the symptom string for this problem.
If this message occurs after a persistent sessions restart, look for associated messages for more guidance. The problem might be temporary.
If this message occurs during normal system execution, you will need further assistance from IBM. See CICS Problem Determination Guide for guidance on how to proceed.
CSNE
DFHZRAC, DFHZRLP, DFHZSDL, DFHZSLX
XMEOUT Parameters: date, time,applid, termid, tranid, sense, instance, {1=DFHZRLP, 2=DFHZRLP, 3=DFHZRLP, 4=DFHZRLP, 5=DFHZSDL, 6=DFHZSDL, 7=DFHZSLX, 8=DFHZSLX, 9=DFHZSLX, 10=DFHZSLX, 11=DFHZSLX, 12=DFHZSLX, 13=DFHZRAC, 14=DFHZRAC, 15=DFHZRAC}
The chain finite state machine (FSM) has reported an error in the use of APPC chaining protocols.
For the meaning of the sense data, see DFHZCxxxx messages.
The task is abnormally terminated with a dump.
Message DFHME0116 is normally produced containing the symptom string for this problem.
If this message occurs after a persistent sessions restart, look for associated messages for more guidance. The problem might be temporary.
If this message occurs during normal system execution, investigate any transactions running on the session at the time of failure because the error can be caused by using both the LAST and WAIT options on an EXEC CICS SEND command in an APPC DTP application. This combination of parameters is not recommended. See the CICS Distributed Transaction Programming Guide for more information. If this is not the cause of the problem, you will need further assistance from IBM. See CICS Problem Determination Guide for guidance on how to proceed.
CSNE
DFHZRAC, DFHZRLP, DFHZSDL, DFHZSLX, DFHZERH, DFHZDET
XMEOUT Parameters: date, time,applid, termid, tranid, sense, instance, {1=DFHZRLP, 2=DFHZRLP, 3=DFHZRLP, 4=DFHZRLP, 5=DFHZRLP, 6=DFHZRLP, 7=DFHZRLP, 8=DFHZDET, 9=DFHZERH, 10=DFHZSDL, 11=DFHZSDL, 12=DFHZSLX, 13=DFHZSLX, 14=DFHZSLX, 15=DFHZSLX, 16=DFHZSLX, 17=DFHZSLX, 18=DFHZSLX, 19=DFHZSLX, 20=DFHZSLX, 21=DFHZSLX, 22=DFHZRAC, 23=DFHZRAC, 24=DFHZRAC, 25=DFHZRAC, 26=DFHZRAC, 27=DFHZRAC, 28=DFHZRAC}
The contention finite state machine (FSM) has reported an error in the use of APPC contention protocols.
For the meaning of the sense data, see DFHZCxxxx messages.
The task is abnormally terminated with a dump.
Message DFHME0116 is normally produced containing the symptom string for this problem.
If this message occurs after a persistent sessions restart,
look for associated messages for more guidance. The problem
might be temporary.
If this message occurs during normal system execution, you will need further assistance from IBM. See CICS Problem Determination Guide for guidance on how to proceed.
CSNE
DFHZRAC, DFHZRLP, DFHZDET, DFHZCLS
DFHZCC
XMEOUT Parameters: date, time,applid, termid, tranid, sense, instance, {1=DFHZDET, 2=DFHZRAC, 3=DFHZRAC, 4=DFHZRAC, 5=DFHZRAC, 6=DFHZRAC, 7=DFHZRAC,
8=DFHZRAC, 9=DFHZRAC, 10=DFHZRAC, 11=DFHZRLP, 12=DFHZRAC, 13=DFHZRAC, 14=DFHZRAC, 15=DFHZRAC, 16=DFHZRAC, 17=DFHZCLS}
DFHZSDL was entered, but no valid request was passed to it.
For the meaning of the sense data, see DFHZCxxxx messages.
The task is abnormally terminated with a dump.
Message DFHME0116 is normally produced containing the symptom string for this problem.
You need further assistance from IBM to resolve this problem. See CICS Problem Determination Guide for guidance on how to proceed.
CSNE
DFHZSDL
XMEOUT Parameters: date, time,applid, termid, tranid, sense, instance, {1=DFHZSDL, 2=DFHZSDL, 3=DFHZSDL, 4=DFHZSDL, 5=DFHZSDL}
DFHZRVL was entered, but no valid request was passed.
For the meaning of the sense data, see DFHZCxxxx messages.
The task is abnormally terminated with a dump.
Message DFHME0116 is normally produced containing the symptom string for this problem.
You need further assistance from IBM to resolve this problem. See CICS Problem Determination Guide for guidance on how to proceed.
CSNE
DFHZRVL
XMEOUT Parameters: date, time,applid, termid, tranid, sense, instance, {1=DFHZRVL}
The receive buffer passed to DFHRVL is too small to accommodate a maximum size request unit.
For the meaning of the sense data, see DFHZCxxxx messages.
The task will be abnormally terminated with a dump.
Message DFHME0116 is normally produced containing the symptom string for this problem.
You need further assistance from IBM to resolve this problem. See CICS Problem Determination Guide for guidance on how to proceed.
CSNE
DFHZRVL
XMEOUT Parameters: date, time,applid, termid, tranid, sense, instance, {1=DFHZRVL, 2=DFHZRVL, 3=DFHZRVL, 4=DFHZRVL}
A non-process-level exception response has been received.
For the meaning of the sense data, see DFHZCxxxx messages.
The task is abnormally terminated with a dump.
Incorrect flows have been received on an APPC session. The CICS trace gives further details of the flow. Try to recreate the error by running a VTAM trace TYPE=IO/BUF to obtain complete details of the line flow.
CSNE
DFHZRLP
XMEOUT Parameters: date, time,applid, termid, tranid, sense, instance, {1=DFHZRLP}
BID with data received, but not OIC.
For the meaning of the sense data, see DFHZCxxxx messages.
The task is abnormally terminated.
Incorrect flows have been received on an APPC session. The CICS trace gives further details of the flow. It may help to run a VTAM trace TYPE=IO/BUF and repeat the error to obtain complete details of the line flow.
CSNE
DFHZRAC, DFHZRLP
XMEOUT Parameters: date, time,applid, termid, tranid, sense, instance, {1=DFHZRLP, 2=DFHZRAC, 3=DFHZRAC}
A BID with data was received in an invalid state for rejection.
For the meaning of the sense data, see DFHZCxxxx messages.
The task is abnormally terminated.
Incorrect flows have been received on an APPC session. The CICS trace gives further details of the flow. It may help to run a VTAM trace TYPE=IO/BUF and repeat the error to obtain complete details of the line flow.
CSNE
DFHZRLP
XMEOUT Parameters: date, time,applid, termid, tranid, sense, instance, {1=DFHZRLP, 2=DFHZRLP, 3=DFHZRLP, 4=DFHZRLP}
The record length received exceeds the buffer length.
For the meaning of the sense data, see DFHZCxxxx messages.
The task is abnormally terminated.
Incorrect flows have been received on an APPC session. The CICS trace gives further details of the flow. It may help to run a VTAM trace TYPE=IO/BUF and repeat the error to obtain complete details of the line flow.
CSNE
DFHZRLP
XMEOUT Parameters: date, time,applid, termid, tranid, sense, instance, {1=DFHZRLP}
An end chain was received with invalid DFC indicators.
For the meaning of the sense data, see DFHZCxxxx messages.
The task is abnormally terminated.
Incorrect flows have been received on an APPC session. The CICS trace gives further details of the flow. It may help to run a VTAM trace TYPE=IO/BUF and repeat the error to obtain complete details of the line flow.
CSNE
DFHZRLP
XMEOUT Parameters: date, time,applid, termid, tranid, sense, instance, {1=DFHZRLP}
A response, sent to acknowledge successful receipt of data, was rejected by VTAM.
For the meaning of the sense data, see DFHZCxxxx messages.
The task is abnormally terminated with a dump.
Message DFHME0116 is normally produced containing the symptom string for this problem.
You need further assistance from IBM to resolve this problem. See CICS Problem Determination Guide for guidance on how to proceed.
CSNE
DFHZRLP
XMEOUT Parameters: date, time,applid, termid, tranid, sense, instance, {1=DFHZRLP}
Bracket initiation stopped (BIS) received with invalid DFC flags.
For the meaning of the sense data, see DFHZCxxxx messages.
The task is abnormally terminated.
Incorrect flows have been received on an APPC session. The CICS trace will give further details of the flow. It may help to run a VTAM trace TYPE=IO/BUF and repeat the error to obtain complete details of the line flow.
CSNE
DFHZRLP
XMEOUT Parameters: date, time,applid, termid, tranid, sense, instance, {1=DFHZRLP, 2=DFHZRLP}
An unexpected response was received that was either a positive response to data of a previous bracket, or a response to a command that cannot be accepted when the logical unit is in "continue specific" mode.
For the meaning of the sense data, see DFHZCxxxx messages.
The task is abnormally terminated.
Incorrect flows have been received on a APPC session. The CICS trace will give further details of the flow. It may help to run a VTAM trace TYPE=IO/BUF and repeat the error to obtain complete details of the line flow.
CSNE
DFHZRLP
XMEOUT Parameters: date, time,applid, termid, tranid, sense, instance, {1=DFHZRLP, 2=DFHZRLP, 3=DFHZRLP, 4=DFHZRLP, 5=DFHZRLP}
An indicator other than CD, CEB, RQD2, or error response has been received.
For the meaning of the sense data, see DFHZCxxxx messages.
The task is abnormally terminated with a dump.
Message DFHME0116 is normally produced containing the symptom string for this problem.
You need further assistance from IBM to resolve this problem. See CICS Problem Determination Guide for guidance on how to proceed.
CSNE
DFHZARL, DFHZARER, DFHZARL
XMEOUT Parameters: date, time,applid, termid, tranid, sense, instance, {1=DFHZARL, 2=DFHZARL, 3=DFHZARL, 4=DFHZARL, 5=DFHZARER}
Data received from the remote system or terminal is not in correct generalized data stream (GDS) format.
For the meaning of the sense data, see DFHZCxxxx messages.
The task is abnormally terminated with a dump.
Message DFHME0116 is normally produced containing the symptom string for this problem.
You need further assistance from IBM to resolve this problem. See CICS Problem Determination Guide for guidance on how to proceed.
CSNE
DFHZARL, DFHZARER, DFHZERH
XMEOUT Parameters: date, time,applid, termid, tranid, sense, instance, {1=DFHZERH, 2=DFHZERH, 3=DFHZERH, 4=DFHZERH, 5=DFHZERH, 6=DFHZERH, 7=DFHZARL, 8=DFHZARL, 9=DFHZARL, 10=DFHZARER, 11=DFHZARER, 12=DFHZARER}
An error situation has been detected during the operation of the LU services manager transaction program (DFHLUP).
Registers 15 and 0 are set to indicate the nature of the error as shown below:
Register 15 = X'0' Task invalidly started ...
Register 0 = X'3' ... via a perm transid.
Register 0 = X'4' ... by a TD trigger.
Register 0 = X'5' ... without data.
Register 0 = >X'6' ... or is out of range of
a valid start code for this
service
Register 15 = X'4' Call code did not match a
supported function (1-5).
Register 0 = call code
Register 15 = X'8' Invalid parameters passed
for this function.
Register 0 = keyword #
Register 15 = X'0C' Function-specific checks
failed for this keyword.
Register 0 = keyword #
Register 15 = X'10' No input data supplied.
Register 0 = ¬0 The IC_GET for the TS START
data failed.
Register 0 = X'0' The LUTYPE6.2 RECEIVE
returned data
length=0.
Register 15 = X'14' The GDS-ID is not for XLN.
Register 0 = GDS-ID
The task is allowed to complete but the required function is not executed.
Message DFHME0116 is normally produced containing the symptom string for this problem.
If one of the errors mentioned above has occurred, try to discover the reason for the failure. If you fail in this, you will need further assistance from IBM. See CICS Problem Determination Guide for guidance on how to proceed.
CSNE
DFHLUP
XMEOUT Parameters: date, time,applid, sysid, X'xxxxx', X'yyyyy'
The connected logical unit has sent Bracket Initiation Stopped (BIS) and can accept no more work.
For the meaning of the sense data, see DFHZCxxxx messages.
If a conversation was active, it is treated as though rollback had occurred on it for full syncpoint (syncpoint level 2), or as session failure for confirm-level syncpoint (syncpoint level 1).
If there was no conversation, it is treated as a BID failure (as for 0813 sense code).
None.
CSNE
DFHZRAC, DFHZGDA, DFHZERH
XMEOUT Parameters: date, time,applid, termid, tranid, sense, instance, {1=DFHZRAC, 2=DFHZGDA, 3=DFHZERH}
Transaction tranid, engaged in an SNA session with a CICS system, issued a command that was inconsistent with the transaction’s current state in the conversation.
The conversation terminates and CICS sends this message to the connected logical unit at the nonfailing end of the conversation.
The application in system sysid abnormally terminates with an abend.
Correct the application program. To find the command in error, use the state diagrams in the CICS Intercommunication Guide.
CSMT
DFHZARL
XMEOUT Parameters: date, time,applid, termid, tranid, sysid
Bind-time security data sent to CICS by its partner LU is missing or invalid. CICS’s password for the partner LU system differs from the partner’s password for CICS. This can be caused by an attempt to sign on to CICS by an unauthorized user.
For the meaning of the sense data, see DFHZCxxxx messages.
The bind is rejected.
Check that an unauthorized user has not tried to log on to CICS. Ensure that the unsuccessful connection is correctly defined to CICS (using RDO or the DFHTCT macro) and to its partner LU system. Ensure that the security requirements are equal at both partners, that is, both have security off, or both have security on. A mismatch is one cause of this message.
CSNE
DFHZSCX, DFHZOPX, DFHZBLX
XMEOUT Parameters: date, time,applid, termid, tranid, sense, instance, {1=DFHZOPX, 2=DFHZBLX, 3=DFHZBLX, 4=DFHZBLX, 5=DFHZBLX, 6=DFHZOPX, 7=DFHZOPX, 8=DFHZOPX, 9=DFHZOPX, 10=DFHZSCX}
This message can be issued for any of the reasons listed below.
For the meaning of the sense data, see DFHZCxxxx messages.
CICS rejects the bind.
CICS does NOT allow subsequent binds to specify different security requirements from the first bind. It will not support persistent verification on input either.
Where applicable, alter your applications to meet these requirements.
CSNE
DFHZOPX, DFHZOPN
XMEOUT Parameters: date, time,applid, termid, tranid, sense, instance, {1=DFHZOPX, 2=DFHZOPN, 3=DFHZOPN, 4=DFHZOPX}
CICS detected an error while verifying an encrypted bind security password.
For the meaning of the sense data, see DFHZCxxxx messages.
CICS rejects the bind.
Investigate the CSNE and CSMT logs.
Find out whether an unauthorized user tried to log on to CICS, or whether an authorized user entered his password incorrectly.
CSNE
DFHZEV1, DFHZEV2
XMEOUT Parameters: date, time,applid, termid, tranid, sense, instance, {1=DFHZEV1, 2=DFHZEV2, 3=DFHZEV1}
CICS received a bind with bind security without an FMH12.
For the meaning of the sense data, see DFHZCxxxx messages.
CICS rejects the bind.
Message DFHME0116 is normally produced containing the symptom string for this problem.
This is an error either in CICS or in SNA. Keep the CSNE and CSMT logs. You need further assistance from IBM to resolve this problem. See CICS Problem Determination Guide for guidance on how to proceed.
CSNE
DFHZRAC
XMEOUT Parameters: date, time,applid, termid, tranid, sense, instance, {1=DFHZRAC, 2=DFHZRAC, 3=DFHZRAC, 4=DFHZRAC}
CICS required a TIOA work area for bind security validation, but the GETMAIN failed because insufficient storage was available.
CICS rejects the bind.
Consider increasing the size of the CICS region or reducing the number of concurrent CICS tasks (MXT parameter in the system initialization table).
CSNE
DFHZEV1
XMEOUT Parameters: date, time,applid, termid, tranid, sense, instance, {1=DFHZEV1}
CICS has detected an error while validating the BIND supplied by VTAM for a CICS typeterm definition defined with LOGMODE=0 or LOGMODE=logmode.
The response code indicates:
The reason code for a response of X'04' is as follows:
The reason code for a response of X'08' or X'0C' is as follows:
Reason Invalid Explanation
Hex byte
1 3 Should be hex 02, 03, 04 or 07
2-8 4|5|6|7 Invalid for this FM profile
9 2 Should be hex 00, 02, 03, 04,
07, 13 or 14
0A,0D,10 1 Invalid for LUTYPE 1,2 or 3 -
must be hex 01
0B 4|5|6|7 Invalid for LUTYPE 1
0C 22 Invalid for LUTYPE 1
0E 4|5|6|7 Invalid for LUTYPE 2
0F 24 Invalid for LUTYPE 2 should be
hex 00, 01, 02, 03, 7E, or 7F
11 4|5|6|7 Invalid for LUTYPE 3
12 24 Invalid for LUTYPE 3 should be
hex 00, 01, 02, 03, 7E, or 7F
13 16 Invalid for LUTYPE 6.2
14 23 Invalid for LUTYPE 6.2
15-18 24 Invalid for LUTYPE 6.2
19 15 Should be hex 00 or 02
1A 14 Should be hex 00, 01, 02, 03,
06
1B and User Data The reason code matches the
over byte position in the BIND for
the error detected. These can
be:
- Session ID length
unsupported - should
be 3 to 11
- PLU/SLU name length
unsupported - should
be 2 to 19
- PLU/SLU defined twice
- Length invalid
- Session qualifier pairs have
inconsistent lengths.
CICS rejects the logon request. The BIND being validated is printed with this message.
Use the response and reason codes and the printed BIND, together with the VTAM definition of the BIND for the relevant LOGMODE to determine the reason for the rejection.
Either change the logmode or use a different one that matches CICS requirements.
CSMT
DFHZOPN
XMEOUT Parameters: date, time,applid, termid, tranid, logmode, X'response', X'reason', instance, {1=DFHZOPN}
A READ timeout has occurred on the SNA link. SNA unbinds the session and CICS returns control to the application program. This allows the program to override the system action (for example, the program could free the APPC session).
For the meaning of the sense data, see DFHZCxxxx messages.
CICS abends the task abnormally with a dump.
This is probably a network problem caused by a high level of network traffic. To avoid this problem, increase the Read Timeout (RTIMOUT) to a sufficiently high value to compensate for the level of network traffic. Alternatively, this problem may have arisen simply because the partner application failed to respond due to a programming error. If this is the case, correct the partner application and retry the request.
CSNE
DFHZARL, DFHZARER.
XMEOUT Parameters: date, time,applid, termid, tranid, sense, instance, {1=DFHZARL, 2=DFHZARL, 3=DFHZARER}
Either a MODENAME passed to VTAM during an attempt to bind an APPC session is not known to VTAM, or the logmode name of a VTAM 3270-type terminal is not valid.
For the meaning of the sense data, see DFHZCxxxx messages.
CICS places the session permanently out of service and for APPC, the mode entry is flagged unusable.
Either redefine the sessions using a MODENAME that is known to VTAM, or add the MODENAME to the VTAM LOGMODE table. Alternatively, if the logmode name specified for a VTAM terminal is invalid, redefine the terminal entry using the correct name.
CSNE
DFHZLEX
XMEOUT Parameters: date, time,applid, termid, tranid, sense, instance, {1=DFHZLEX}
A request to attach a task has been received across an APPC link. However, there is an error in the conversation type field. It must be TYPE=MAPPED or TYPE=UNMAPPED.
For the meaning of the sense data, see DFHZCxxxx messages.
The task is abended and a dump is produced. The session is unbound.
The remote APPC system sends an invalid attach header (FMH Type 5). Use the supplied dump to determine the error and investigate the cause at the remote system.
CSNE
DFH62XM
XMEOUT Parameters: date, time,applid, termid, tranid, sense, instance, {1=DFH62XM}
A request to attach a task has been received across an APPC link. However, there is an error in the DBA field.
For the meaning of the sense data, see DFHZCxxxx messages.
The task abends and a dump is produced. The session is unbound.
The remote APPC system sends an invalid attach header (FMH Type 5). Use the supplied dump to determine the error and investigate the cause at the remote system.
CSNE
DFH62XM
XMEOUT Parameters: date, time,applid, termid, tranid, sense, instance, {1=DFH62XM}
A request to attach a task has been received across an APPC link. However, the synchronization level requested is invalid.
For the meaning of the sense data, see DFHZCxxxx messages.
The task abends and a dump is produced.
The remote APPC system sends an invalid attach header (FMH Type 5). Use the supplied dump to determine the error and investigate the cause at the remote system.
Check the sync level in the ATTACH header against that in the BIND.
CSNE
DFH62XM
XMEOUT Parameters: date, time,applid, termid, tranid, sense, instance, {1=DFH62XM}
A request to attach a task has been received across an APPC link and either the unit of work ID is invalid, or no UOWID was received when the sync point level required it.
For the meaning of the sense data, see DFHZCxxxx messages.
The task abends and a dump is produced. The session is unbound.
The remote APPC system sends an invalid attach header (FMH Type 5). Use the supplied dump to determine the error and investigate the cause at the remote system.
CSNE
DFH62XM
XMEOUT Parameters: date, time,applid, termid, tranid, sense, instance, {1=DFH62XM, 2=DFH62XM, 3=DFH62XM, 4=DFH62XM, 5=DFH62XM, 6=DFH62XM}
A request to attach a task has been received across an APPC link. However, there is an error in the FMH length or in the length of one of the sub-fields. This results in CICS being unable to determine which task to attach.
The instance instance is one of the following:
For the meaning of the sense data, see DFHZCxxxx messages.
The task abends and a dump is produced.
The remote APPC system sends an invalid attach header (FMH Type 5). Use the supplied dump to determine the error and investigate the cause at the remote system.
CSNE
DFH62XM
XMEOUT Parameters: date, time,applid, termid, tranid, sense, instance, {1=DFH62XM, 2=DFH62XM}
A security authorization facility (SAF) request to extract APPC bind-time security information from the external security manager (ESM) has been rejected with return code RF=X'rf'. and RO=X'r0'.
This is due either to the ESM being inactive or to the appropriate APPC profile not being defined to the ESM.
For the meaning of the sense data, see DFHZCxxxx messages.
CICS rejects the bind.
Refer to the ESM manuals appropriate to your system to obtain information about the meanings of any return codes which may have been produced by the ESM.
If you are using RACF as your security manager, refer to the RACXTRT macro guidance documented in the System Programming Library RACF manual for the meaning of the return codes.
If the appropriate APPC profile had not been defined to the ESM, define the profile, perform a CICS security rebuild and then attempt to reestablish the APPC connection.
CSNE
DFHZEV1, DFHZEV2, DFHZOPN
XMEOUT Parameters: date, time,applid, X'rf', X'r0', sense, instance, {1=DFHZOPN, 2=DFHZOPN, 3=DFHZOPN, 4=DFHZOPN, 5=DFHZOPN, 6=DFHZOPN, 7=DFHZOPN, 8=DFHZOPN, 9=DFHZEV1, 10=DFHZEV1, 11=DFHZEV1, 12=DFHZEV1, 13=DFHZEV2, 14=DFHZEV2, 15=DFHZEV2, 16=DFHZEV2}
The external security manager (ESM) was attempting to process a security authorization facility (SAF) request. Processing has failed with return code RF=X'rf' and reason code R0=X'r0'.
For the meaning of the sense data, see DFHZCxxxx messages.
CICS rejects the bind.
Refer to the ESM manuals appropriate to your system to obtain information about the meanings of any return codes or reason codes produced by the ESM.
If you are using RACF as your security manager, refer to the RACXTRT macro guidance documented in the System Programming Library RACF manual for the meaning of the return code and the reason code.
CSNE
DFHZEV1, DFHZEV2, DFHZOPN
XMEOUT Parameters: date, time,applid, X'rf', X'r0', sense, instance, {1=DFHZOPN, 2=DFHZOPN, 3=DFHZEV1, 4=DFHZEV2}
A request to extract APPC bind-time security information has failed with return code RF=X'rf' and reason code R0=X'r0'. The profile information which was requested had not been previously defined to the external security manager (ESM).
For the meaning of the sense data, see DFHZCxxxx messages.
CICS rejects the bind.
Check the profiles defined to the ESM. Create the missing APPC profile entry.
Refer to the ESM manuals appropriate to your system to obtain information about the meanings of any return codes or reason codes produced by the ESM.
If you are using RACF as your security manager, refer to the RACXTRT macro guidance documented in the System Programming Library RACF manual for the meaning of the return code and the reason code.
CSNE
DFHZEV1, DFHZEV2, DFHZOPN
XMEOUT Parameters: date, time,applid, X'rf', X'r0', sense, instance, {1=DFHZOPN, 2=DFHZOPN, 3=DFHZEV1, 4=DFHZEV2}
APPC bind-time validation has failed. No session key has been found in the requested APPC profile information. When bind-time security has been defined between two logical units (LUs), a valid session key must have been defined for the encryption process. A null session key (that is, when no key is defined) is regarded as an error.
For the meaning of the sense data, see DFHZCxxxx messages.
CICS rejects the bind.
Check the profiles defined to the external security manager (ESM). Create a valid session key for the appropriate APPC profile entry. DO NOT use the NOSESSKEY ESM option for XAPPC security profiles when using RACF.
Refer to the ESM manuals appropriate to your system to obtain information about the meanings of any return and reason codes which produced by the ESM.
If you are using RACF as your security manager, refer to the RACXTRT macro guidance documented in the System Programming Library RACF manual for the meaning of the return code and the reason code.
CSNE
DFHZEV1, DFHZEV2, DFHZOPN
XMEOUT Parameters: date, time,applid, sense, instance, {1=DFHZOPN, 2=DFHZOPN, 3=DFHZEV1,4=DFHZEV2}
The external security manager (ESM) has requested profile information during bind-time validation but the requested profile is locked. When a profile is locked no sessions can be established.
For the meaning of the sense data, see DFHZCxxxx messages.
CICS rejects the bind.
Check the profiles defined to the ESM. The system administrator may have locked the profile. Request that the profile be unlocked. Try once more when the profile has been unlocked.
If you are using RACF as your security manager, refer to the RACXTRT macro guidance documented in the System Programming Library RACF manual for further information.
CSNE
DFHZEV1, DFHZEV2, DFHZOPN
XMEOUT Parameters: date, time,applid, sense, instance, {1=DFHZOPN, 2=DFHZOPN, 3=DFHZEV1,4=DFHZEV2}
The external security manager (ESM) has requested profile information during bind-time validation but the requested profile has expired.
For the meaning of the sense data, see DFHZCxxxx messages.
CICS rejects the bind.
Check the profiles defined to the ESM. The system administrator needs to update the required profile. Request that the profile be updated. Try once more when the profile has been updated.
If you are using RACF as your security manager, refer to the RACXTRT macro guidance documented in the System Programming Library RACF manual for further information.
CSNE
DFHZEV1, DFHZEV2, DFHZOPN
XMEOUT Parameters: date, time,applid, sense, instance, {1=DFHZOPN, 2=DFHZOPN, 3=DFHZEV1,4=DFHZEV2}
The finite state machine (FSM), for the APPC alternate RPL (RPL 'B'), has detected an error in the use of the RPL.
For the meaning of the sense data, see DFHZCxxxx messages.
The task is abnormally terminated with abend code ATNI and a dump is produced.
If this message occurs when VTAM is terminating, it is not a serious problem and usually no response is necessary.
If this message occurs during normal system execution, you will need further assistance from IBM. See CICS Problem Determination Guide for guidance on how to proceed.
CSNE
DFHZSDL
XMEOUT Parameters: date, time,applid, termid, tranid, sense, instance, {1=DFHZSDL}
CICS has detected an error while validating the bind security specification. LOCAL security has been specified, but the bind contains data that indicates NON LOCAL security.
For the meaning of the sense data, see DFHZCxxxx messages.
CICS rejects the bind.
Ensure that the correct data is sent in the bind for the required type of security.
CSMT
DFHZSCX, DFHZOPX, DFHZBLX
XMEOUT Parameters: date, time,applid, termid, tranid, sense, instance, {1=DFHZBLX, 2=DFHZBLX, 3=DFHZOPX, 4=DFHZOPX}
A task was purged or forcepurged while it was suspended, waiting for an ISC request to complete.
For the meaning of the sense data, see DFHZCxxxx messages.
An unbind is requested for the session against which the ISC request was waiting and the task is abended A FORCEPURGE command causes the task to be abended irrespective of the state of the session. Other VTAM error messages may result from this action.
Investigate the reasons the task was purged or forcepurged because it may have been the result of an application error. In addition, the partner task in the connected CICS system will have session failure notification returned on the next ISC request after the session has been unbound. Check that the partner task has handled the situation.
CSNE
DFHZARER
XMEOUT Parameters: date, time,applid, termid, tranid, sense, instance, {1=DFHZARER}
A request to attach a task has been received across an APPC link. However there is an error in the FMH attach parameters. An attach parameter is present that is not authorized by the bind security indicators.
The instance data can take the following values:
The task abends and a dump is produced and the session is unbound. An exception trace point (number 1737) for component TF is issued, tracing the invalid attach header (FMH type 5).
Investigate the cause of the error which is in the remote system. Use the FMH5 in the exception trace to determine why the remote system sent an invalid attach request.
CSNE
DFH62XM
XMEOUT Parameters: date, time,applid, termid, tranid, sense, instance, {1=DFH62XM, 2=DFH62XM, 3=DFH62XM}
A request to attach a task has been received over an APPC link. However the FMH5 attach parameters do not conform to the APPC protocol.
The instance data can take the following values:
The attach request is rejected and the session is unbound. An exception trace point (number 1737) for component TF is issued tracing the invalid attach header (FMH type 5).
Investigate the cause of the error which is in the remote system. Use the FMH5 in the exception trace, to determine why the remote system sent an invalid attach request.
If the remote system has an earlier release of CICS or CICS on another platform and the sense value given is 5 then you may need to set USEDFLTUSER. See 'Attach Time Security and the USEDFLTUSER option' in chapter 12 of the CICS RACF® Security Guide.
CSNE
DFH62XM, DFHZGXA
XMEOUT Parameters: date, time,applid, termid, tranid, sense, instance, {1=DFH62XM, 2=DFH62XM, 3=DFH62XM, 4=DFH62XM, 5=DFH62XM, 6=DFH62XM, 7=DFH62XM,
8=DFH62XM, 9=DFH62XM}
An error has been detected during the execution of transaction CLS3. The error code indicates the nature of the error:
Depending upon the nature of the event that gave rise to the message, the transaction continues execution, terminates normally, or terminates abnormally. The message text indicates which action is being taken.
This depends upon the error code:
CSNE
DFHCLS3
XMEOUT Parameters: date, time,applid, {1= unknown, 2= inbound, 3= outbound}, {1= request., 2=Persistent Verify Signoff request., 3=Persistent Verify Timeout request.}, tranid,{1= continuing., 2= terminating.,3= terminating abnormally.}, X'xxxxx',yyyy
All the CICS Receive Any RPLs have been posted but the TCTTE for each one is waiting for a response from a VTAM terminal or session. All the Receive Any RPLs have been stalled for 10 dispatches of the TCP task (CSTP). This message is produced for each session that is in this situation. A VTAM session has not responded to a command such as BID or SHUTD sent by CICS. This is typically caused by a protocol error.
CICS is running with system initialization parameter RAPOOL=(n,n,FORCE) causing CICS to issue a VTAM CLSDST against the session, which causes the TCTTE's RPL to be completed and the session to be unbound.
The default NEP action is CLSDST, which causes CICS to clean up the TCTTE after the pending command has been terminated.
The Receive Any data received is discarded and the RA RPL is reissued.
Investigate the reason why the command has not completed. The TCTTE RPL is printed with the message.
It is important to look at any earlier DFHZC4949 messages because of the asynchronous nature of DFHZNAC. If the CLSDST has not completed, the RPL printed will be active and will show the RPL that can not complete. If the CLSDST has completed when DFHZNAC runs, the RPL printed will have a RTNCD/FDB2 of X'0C0B' but RPLREQ still shows what command would not complete.
If the CLSDST return code rc is non 0, the CLSDST macro has failed in DFHZRAC and the session remains hung. You may be able to free the session by using VTAM command V NET,INACT,ID=netname,I. You can find the reason for the CLSDST failure by looking at the RPL in the AP FC90 trace point for the CLSDST.
CSNE
DFHZRAC
XMEOUT Parameters:
date,
time,
applid,
termid,
tranid,
netname,
{1=data lost. ,
2=response lost. ,
3=command lost. },
X'rc',
sense,
instance,
{1=DFHZRAC,
2=DFHZRAC,
3=DFHZRAC}
An error has been detected while attempting to attach the outbound transaction for the Connection Quiesce Protocol (CQPO) on an APPC session.
The release of the connection continues, but the Connection Quiesce Protocol will take place only if the partner system successfully initiates it.
Determine why transaction CQPO failed to attach. If you have installed the correct definition for the transaction, you should never see this message, and you may need to contact your IBM Support Center for assistance.
If the partner system did not initiate the Connection Quiesce Protocol, you may need to determine if there are units of work awaiting resync, or VTAM affinities to be ended before you can INITIAL start either of the connected systems.
CSNE
DFHZCLS
XMEOUT Parameters:
date,
time,
applid,
termid,
sysid,
instance,
{1=DFHZCLS}
An error has been detected during the execution of transaction tranid. The error code indicates the nature of the error:
Depending upon the nature of the event that gave rise to the message, the transaction continues execution, terminates normally, or terminates abnormally. The message text indicates which action is being taken.
This depends upon the error code:
In other cases, contact your IBM Support Center.
CSNE
DFHCLS5
XMEOUT Parameters:
date,
time,
applid,
{1= unknown,
2= inbound,
3= outbound},
tranid,
{1=continuing.,
2= terminating.,
3=terminating abnormally.},
X'
xxxxx',
yyyy
CICS has received definitions from remote system sysid, but cannot find a connection named cccc.
CICS continues.
If you want these definitions to be accepted, install the necessary connection using CEDA, and retransmit the definitions from the remote system.
CSMT
DFHBSTZ1, DFHBSTZ2
XMEOUT Parameters: date, time,applid, sysid, cccc
When installing resource resource, CICS module xxxx could not get storage for the extent specified by the value of yyyy.
CICS continues.
If possible, increase the size of your CICS address space. Otherwise, consider reducing the number of resources used in one CICS run.
CSMT
DFHBSMIR, DFHBSMPP, DFHBSM62,
DFHBSS, DFHBSSZM, DFHBSTS,
DFHBSTB, DFHBSTB3, DFHBSTC, DFHBSTZ,
DFHBSTZB, DFHBSTZO, DFHBSTZR, DFHBSTZV,
DFHBSTZ1, DFHBSTZ2,
DFHBSZZS
XMEOUT Parameters:
date,
time,
applid,
resource,
xxxx,
yyyy
CICS cannot delete terminal termid because a BMS paging session is still active for the terminal.
CICS continues.
Sign on to terminal termid and purge the pages.
CSMT
DFHBSTB
XMEOUT Parameters: date, time,applid, termid
CICS cannot delete the terminal termid, because the CICS batch data attach function (DIP) is still active for this terminal.
CICS continues. A system dump is taken with dumpcode ZC5903. Message DFHME0116 is normally produced containing the symptom string for this problem.
You need further assistance from IBM to resolve this problem. See CICS Problem Determination Guide for guidance on how to proceed.
CSMT
DFHBSTD
XMEOUT Parameters: date, time,applid, termid
CICS cannot delete the terminal termid because an EDF session is still active for this terminal.
CICS continues.
Deactivate EDF for the terminal, and reinstall the group.
CSMT
DFHBSTE
XMEOUT Parameters: date, time,applid, termid
CICS cannot delete terminal termid because the command level interface is still active for this terminal.
CICS continues. A system dump is taken with dumpcode ZC5905. Message DFHME0116 is normally produced containing the symptom string for this problem.
You need further assistance from IBM to resolve this problem. See CICS Problem Determination Guide for guidance on how to proceed.
CSMT
DFHBSTH
XMEOUT Parameters: date, time,applid, termid
A name of hexadecimal zeros has been used for a TERMINAL or CONNECTION definition.
This is a reserved value. CICS has failed to install the terminal or connection.
xxxx is the reserved value converted to printable hexadecimal. The error has probably been made using autoinstall.
CICS continues.
Correct the definition to use a valid name and reinstall the group.
CSMT
DFHBSS, DFHBSTZ, DFHBSTZ1, DFHBSTZ2 DFHBSMPP
XMEOUT Parameters: date, time,applid, xxxx
During the deletion of connection cccc, the connection was found to have shipped remote terminals. The deletion of one or more of these shipped remote terminals has failed.
CICS continues.
See message DFHZC5915 for further information.
Use CEMT to release the connection and put it OUT OF SERVICE, then retry the install of the connection.
CSMT
DFHBSSZ
XMEOUT Parameters: date, time,applid, cccc
CICS cannot install terminal termid. DFHXSMN gave the return code retcode.
CICS continues.
Check the value of the return code retcode in the CICS Customization Guide.
CSMT
DFHBSTS
XMEOUT Parameters: date, time,applid, termid, retcode
When installing resource resource, the CICS module DFHBSSZR made a call to an IR service irp_function which failed due to the specified return code,
CICS continues. The MRO connection resource is not installed.
For an explanation of the return code, see DFHIRSDS in the CICS Data Areas manual.
Also see the user response section of message DFHIR3780. This gives a list of reasons why starting IRC can fail. However, some of the reasons are now also applicable when adding an IRC connection when IRC is OPEN. For instance a return code of E8 is issued if you add an IRC connection when cross memory is requested on the new connection but is not being used on any existing connection and when the CICS DB2 attachment has been initialized.
CSMT
DFHBSSZR
XMEOUT Parameters: date, time,applid, resource, irp_function,Return_code
CICS could not find the connection cccc associated with resource resource.
CICS continues.
Install connection cccc.
CSMT
DFHBSMIR
XMEOUT Parameters: date, time,applid, resource, cccc
The terminal termid and the connection cccc are mutually incompatible.
CICS continues.
Modify your definition of termid or cccc.
CSMT
DFHBSTZ, DFHBSTZ2
XMEOUT Parameters: date, time,applid, termid, cccc
CICS cannot delete node id. The message explains the reason for the failure.
The TMP table entry is identified by tabname. The key used in the table has a value key. The module that issued the message is identified by modname and the instance of the message in that module by inst.
The resource is not deleted. If the entry was locked, CICS issues one or more message DFHZC5980.
Choose the action which corresponds to the reason identified in the message:
CSMT
DFHBSS, DFHBSSZ, DFHBSTZ, DFHBSTZ1, DFHBSTZ2, DFHBSTZV, DFHBSTZS, DFHBSTZZ
XMEOUT Parameters: date, time,applid, id, {1=A table entry is locked., 2=A table entry was not found., 3=There was a logic error.}, tabname, key, modname, inst
CICS has failed to delete terminal termid because it is already marked as pending deletion.
It is likely that a CEDA user is installing this terminal.
CICS continues.
Check if a CEDA user is installing the terminal.
CSMT
DFHBSMIR, DFHBSMPP, DFHBSS, DFHBSTZ
XMEOUT Parameters: date, time,applid, termid
CICS cannot delete node id The reason is identified in the message.
The module issuing the message is identified as modname.
CICS continues and does not delete the node.
Before retrying the deletion or replacement, perform the action which corresponds to the reason given in the message.
CSMT
DFHBSMIR, DFHBSTZ, DFHBSTZP
XMEOUT Parameters:
date,
time,
applid,
id,
{1=The node is still in service.,
2=The system entry is still in service.,
3=The node has a task attached.},
modname
CICS cannot delete resource termid because DFHZCP activity is pending for this terminal. The resource could be a session belonging to a connection or a terminal TCTTE.
CICS continues.
Use exception trace point AP FCDE to determine what sort of activity is pending.
If this indicates that the VTAM CLSDST command is in progress, VTAM could be trying to contact a nonexistent or unavailable resource (indicated by NETNAME in the CEDA definition for the resource). In this case, wait for a few minutes and retry the reinstall or discard. If you have access to the JOBLOG, message DFHZC3462 for the resource in question indicates that the CLSDST has finished.
If the resource is a terminal, put the terminal briefly into service and then take it out of service again, using the CEMT transaction.
CSMT
DFHBSTZA
XMEOUT Parameters:
date,
time,
applid,
termid
CICS cannot delete terminal termid because the error message writer is still active for this terminal.
CICS continues.
Put the terminal briefly into service and then take it out of service again, using the CEMT transaction.
CSMT
DFHBSTZE
XMEOUT Parameters: date, time,applid, termid
The MVS console consname has outstanding activity that prevents its deletion.
CICS continues.
After replying to any outstanding replies requested of this console, put the console briefly into service and then take it out of service again, using the CEMT transaction.
CSMT
DFHBSTZO
XMEOUT Parameters: date, time,applid, termid, consname
CICS cannot delete terminal termid because of an error in disconnecting remote terminals.
CICS continues. A system dump is taken with dumpcode ZC5919. Message DFHME0116 is normally produced containing the symptom string for this problem.
You need further assistance from IBM to resolve this problem. See CICS Problem Determination Guide for guidance on how to proceed.
CSMT
DFHBSSZ
XMEOUT Parameters: date, time,applid, termid
This CICS system failed to install terminal termid. No terminals can be accepted yet because the system does not have a local system entry. There was probably a failure during CICS initialization.
CICS continues. A system dump is taken with dumpcode ZC5920. Message DFHME0116 is normally produced containing the symptom string for this problem.
You need further assistance from IBM to resolve this problem. See CICS Problem Determination Guide for guidance on how to proceed.
CSMT
DFHBSTZ
XMEOUT Parameters:
date,
time,
applid,
termid
CICS failed to install terminal termid because CICS was initialized without VTAM support.
CICS continues processing.
To use VTAM, shut down CICS and restart with the system initialization parameter VTAM=YES, a TCT assembled with ACCESSMETHOD=VTAM, and appropriate RDO terminal definitions.
CSMT
DFHBSZZV
XMEOUT Parameters: date, time,applid, termid
CICS failed to install terminal termid because the bind-image was invalid.
CICS continues. A system dump is taken with dumpcode ZC5923. Message DFHME0116 is normally produced containing the symptom string for this problem.
You need further assistance from IBM to resolve this problem. See CICS Problem Determination Guide for guidance on how to proceed.
CSMT
DFHBSZZV
XMEOUT Parameters: date, time,applid, termid
CICS failed to install terminal termid because the TCTTE contained no node information block (NIB) descriptor.
CICS continues. A system dump is taken with dumpcode ZC5924. Message DFHME0116 is normally produced containing the symptom string for this problem.
You need further assistance from IBM to resolve this problem. See CICS Problem Determination Guide for guidance on how to proceed.
CSMT
DFHBSZZV
XMEOUT Parameters: date, time,applid, termid
CICS did not delete connection cccc because the AID-chains for the remote system cccc are not empty.
CICS continues.
Using the CEMT transaction, put the connection into service to allow the outstanding AIDs to be processed. Then take the connection out of service to allow deletion.
CSMT
DFHBSSA
XMEOUT Parameters: date, time,applid, cccc
CICS did not install the connection cccc because DFHZCP received no DATASTREAM operand.
CICS continues. A system dump is taken with dumpcode ZC5926. Message DFHME0116 is normally produced containing the symptom string for this problem.
You need further assistance from IBM to resolve this problem. See CICS Problem Determination Guide for guidance on how to proceed.
CSMT
DFHBSSZ6
XMEOUT Parameters: date, time,applid, cccc
CICS did not install the connection cccc because DFHZCP did not receive a RECORDFORMAT operand.
CICS continues. A system dump is taken with dumpcode ZC5927. Message DFHME0116 is normally produced containing the symptom string for this problem.
You need further assistance from IBM to resolve this problem. See CICS Problem Determination Guide for guidance on how to proceed.
CSMT
DFHBSSZ6
XMEOUT Parameters: date, time,applid, cccc
When remote connection sysid was being deleted, it was still in use by number of sessions.
The resource is not deleted. CICS continues.
Wait until access to this remote connection has quiesced and then retry the deletion.
CSMT
DFHBSTZ2
XMEOUT Parameters: date, time,applid, sysid, number
CICS did not install a SESSIONS definition using MODENAME modename because it would have exceeded the maximum number of permitted sessions.
The maximum number of sessions depends on whether the PTF shipped
for APAR PQ27823 is installed. The basic limit is 46656 and the names
are in the range -AAA to -999. The APAR doubles this limit to 93312
giving an additional range of AAA- to 999-.
CICS continues.
Either wait for the system to become less busy, or delete some APPC sessions.
The system programmer should consider increasing the number of
CICS TORs.
CSMT
DFHBSM61
XMEOUT Parameters: date, time,applid, modename
CICS did not install a SESSIONS definition using MODENAME modename because of an unknown name cccc in the CONNECTION parameter.
CICS continues.
Install connection cccc.
CSMT
DFHBSM62
XMEOUT Parameters: date, time,applid, modename, cccc
CICS did not install a SESSIONS definition using MODENAME modename because the CONNECTION is not valid in this context.
CICS continues.
Modify your definition of remote system cccc.
CSMT
DFHBSM62
XMEOUT Parameters: date, time,applid, modename, cccc
CICS did not install a SESSIONS definition using MODENAME modename because the single-session CONNECTION cccc is already in use.
CICS continues.
Modify the definition of cccc.
CSMT
DFHBSM61, DFHBSM62
XMEOUT Parameters: date, time,applid, modename, cccc
CICS has not installed a SESSIONS definition with MODENAME modename because the connection cccc already has an active MODEGROUP, xxxx.
CICS continues.
Put the connection briefly into service and then take it out of service again, using the CEMT transaction.
CSMT
DFHBSM62
XMEOUT Parameters: date, time,applid, modename, cccc, xxxx
CICS has not deleted a SESSIONS definition with MODENAME modename because the definition is already pending deletion.
CICS continues.
Check if a CEDA user was installing the SESSIONS definition.
CSMT
DFHBSM62
XMEOUT Parameters: date, time,applid, modename
CICS is unable to delete a SESSIONS definition with MODENAME modename because of one or more errors reported in previous messages.
CICS continues.
Refer to any preceding messages for further information and guidance. Correct the reported errors.
CSMT
DFHBSM61
XMEOUT Parameters: date, time,applid, modename
CICS is unable to install a session or modegroup as the session-name or modegroup-name name is duplicated. The duplicate might be another connection, session, modegroup or terminal. However it might also be the local connection which has the name specified by SYSIDNT in the system initialization table.
CICS continues processing, but the session or modegroup is not installed.
Change the duplicated session-name or modegroup-name.
CSMT
DFHBSMIR, DFHBSM62
XMEOUT Parameters: date, time,applid, name, sysid
You have tried to replace the error console, CERR. CICS does not allow this.
CICS continues with original error console.
Note this restriction.
CSMT
DFHZCQDL
XMEOUT Parameters: date, time,applid, termid
CICS was unable to install terminal termid because the console consname has posted an ECB.
Processing continues.
Put the terminal briefly into service and then take it out of service again, using the CEMT transaction.
CSMT
DFHBSTZO
XMEOUT Parameters: date, time,applid, termid, consname
CICS cannot install the definition of node nodeid because an addition to a TMP table failed. CICS was trying to add the key key to the table tablename.
The return code from TMP is given in return. If the return code is 4, the entry was a duplicate. It is possible that another entry was added at the same time as this entry and used the same key. If this is not the case, CICS has suffered a logic error. The module that issued the message is indicated by modname.
CICS does not install the definition.
If the entry was not overlapped by another definition which conflicted with its key, or if the return code is not 4, you will need assistance from IBM to resolve the problem. See CICS Problem Determination Guide for guidance on how to proceed.
CSMT
DFHBSS, DFHBSTZ, DFHBSTZS, DFHBSTZZ, DFHBSTZ1, DFHBSTZ2
XMEOUT Parameters:
date,
time,
applid,
nodeid,
key,
tablename,
X'
return',
modname
CICS cannot delete the connection conname because it is an MRO connection and interregion communication (IRC) is open.
The connection is not deleted.
Close the IRC definition and retry the Delete or Replace.
CSMT
DFHBSS
XMEOUT Parameters: date, time,applid, conname
CICS cannot install definition of type called id because it would make a loop of connection definitions. The connection type may be an indirect connection or a remote connection. Indirect connections point to other connections with the INDSYS field, and remote connections point to other connections with the REMOTESYSTEM field. The module that issued the message is identified by modname.
CICS does not install the definition.
Determine the source of the loop either in the already installed definitions or in this definition, and change it before attempting to reinstall this definition.
CSMT
DFHBSSZI, DFHBSTZ2
XMEOUT Parameters: date, time,applid, type, id, modname
CICS has not deleted the SESSIONS definition, ssss, because the CONNECTION is still defined to IRC.
CICS continues.
Issue a CEMT SET IRC CLOSED command.
CSMT
DFHBSTZR
XMEOUT Parameters: date, time,applid, ssss, cccc
CICS has not installed the SESSIONS definition, ssss, because the CONNECTION is already defined to IRC.
CICS continues.
Issue a CEMT SET IRC CLOSED command.
CSMT
DFHBSTZR
XMEOUT Parameters: date, time,applid, ssss, cccc
CICS has not installed the SESSIONS definition, ssss, because the CONNECTION name is not specified.
CICS continues. A system dump is taken with dumpcode ZC5947. Message DFHME0116 is normally produced containing the symptom string for this problem.
You need further assistance from IBM to resolve this problem. See CICS Problem Determination Guide for guidance on how to proceed.
CSMT
DFHBSMIR, DFHBSTZR
XMEOUT Parameters: date, time,applid, ssss
CICS has not installed the SESSIONS definition, ssss, because the CONNECTION specified is not suitable for IRC.
CICS continues.
Modify your definition of cccc.
CSMT
DFHBSTZR
XMEOUT Parameters: date, time,applid, ssss, cccc
CICS has not installed the SESSIONS definition, ssss, because the CONNECTION specified does not support the required type of session. If you are replacing a connection of the same name but of a different type and the install fails for some other reason then this message may occur.
CICS continues.
Modify your definition of cccc.
CSMT
DFHBSMIR, DFHBSTZS, DFHBSTZR
XMEOUT Parameters: date, time,applid, ssss, cccc
CICS has not installed the CONSOLE definition termid because the console ID, consname, already exists.
CICS continues without installing the terminal.
Use the CEDA transaction to define a different console ID and reinstall the terminal.
CSMT
DFHBSTZO
XMEOUT Parameters:
date,
time,
applid,
termid,
consname
CICS has not deleted the CONNECTION definition, ssss, because it cannot delete one or more sessions. A preceding message or messages should explain this failure.
CICS continues.
Refer to the preceding message for further information and guidance.
CSMT
DFHBSSZR, DFHBSSZ6
XMEOUT Parameters: date, time,applid, ssss
CICS cannot delete terminal termid because of its current state.
CICS continues.
Use the CEMT transaction to set terminal termid released and out of service.
CSMT
DFHBSTZV
XMEOUT Parameters: date, time,applid, termid
An object being installed did not have a bind-image.
CICS continues. A system dump is taken with dumpcode ZC5953. Message DFHME0116 is normally produced containing the symptom string for this problem.
You need further assistance from IBM to resolve this problem. See CICS Problem Determination Guide for guidance on how to proceed.
CSMT
DFHBSM62
XMEOUT Parameters: date, time,applid
CICS has failed to install resource resource. Previous message(s) should give the reason for the failure.
CICS continues.
Refer to any preceding messages for further information and guidance.
CSMT
DFHBSTZC
XMEOUT Parameters: date, time,applid, resource
The APPC SESSIONS object being installed is invalid because architected user-data IDs greater than X'02' occur in bind.
CICS does not install the object. A system dump is taken with dumpcode ZC5957. Message DFHME0116 is normally produced containing the symptom string for this problem. You need further assistance from IBM to resolve this problem. See CICS Problem Determination Guide for guidance on how to proceed.
CSMT
DFHBSM62
XMEOUT Parameters: date, time,applid, xx
A terminal or a connection was defined with the same name as the local system entry during the last run of CICS. This is not allowed as the local system entry cannot be replaced.
During cold or initial start of the current run of CICS, CICS attempted to install the group which included the invalid definition. CICS then issued this message.
CICS continues, but this terminal or connection is not installed.
Use the CEDA transaction to correct the terminal or connection name and install the group.
CSMT
DFHBSSZL
XMEOUT Parameters: date, time,applid, xxxx
CICS cannot delete a surrogate TCT entry.
CICS continues. A system dump is taken with dumpcode ZC5961. Message DFHME0116 is normally produced containing the symptom string for this problem.
You need further assistance from IBM to resolve this problem. See CICS Problem Determination Guide for guidance on how to proceed.
CSMT
DFHBSTZ1, DFHBSTZ2
XMEOUT Parameters: date, time,applid, xxxx
CICS has failed to install resource resource because the MODENAME parameter is missing.
CICS continues.
Supply the missing parameter.
CSMT
DFHBSTZS
XMEOUT Parameters: date, time,applid, resource
An autoinstall has been attempted with terminal termid that has a VTAM RECEIVESIZE greater than the corresponding TYPETERM RECEIVESIZE|SENDSIZE.
CICS continues. The autoinstall is rejected.
Increase the TYPETERM RECEIVESIZE or the TYPETERM SENDSIZE, OR decrease the RECEIVESIZEs in the VTAM LOGMODE table.
CSMT
DFHBSZZV
XMEOUT Parameters: date, time,applid, operation, xxxx, termid, yyyy
CICS has failed to install SESSIONS ssss because the length of the BINDPASSWORD exceeds the limit of 8.
CICS continues. A system dump is taken with dumpcode ZC5964. Message DFHME0116 is normally produced containing the symptom string for this problem.
You need further assistance from IBM to resolve this problem. See CICS Problem Determination Guide for guidance on how to proceed.
CSMT
DFHBSSZS
XMEOUT Parameters: date, time,applid, ssss
CICS failed in an attempt to install or delete POOL definition poolid. A terminal termid in the pool was being deleted at the same time as the pool was being installed or deleted. This probably due to changing the terminal from a pooled terminal to a non-pooled terminal, or changing the pool name for a terminal in the same group. CICS cannot continue to modify the pool until the change to the terminal has completed.
CICS continues.
Once the deletion or modification of the terminal has succeeded, retry the installation.
CADL
DFHBSMPP
XMEOUT Parameters: date, time,applid, poolid, termid
CICS is starting to install, delete or restore resource. The resource may be either a terminal, a connection, a modegroup, a session, or a pool_entry. Other messages are issued after this one if this installation, deletion or restoration fails.
CICS continues.
None.
CADL
DFHBSTZ, DFHBSMPP, DFHBSM62, DFHBSS, DFHBSMIR
XMEOUT Parameters: date, time,applid, {1=INSTALL, 2=DELETE,3=RESTORE}, resource, termid,modname
CICS has failed to install a SESSIONS definition using MODENAME modename. Previous message(s) should give the reason for the failure.
CICS continues.
Refer to the preceding message for further information and guidance.
CSMT
DFHBSM61
XMEOUT Parameters: date, time,applid, modename
CICS has failed to install a CONNECTION definition for MODEGROUP modename. Previous message(s) should give the reason for the failure.
CICS continues.
Refer to any preceding messages for further information and guidance.
CSMT
DFHBSSZP
XMEOUT Parameters: date, time,applid, modename
CICS has failed to replace a CONNECTION definition for MODEGROUP modename. Previous message(s) should give the reason for the failure.
CICS continues.
Refer to any preceding messages for further information and guidance.
CSMT
DFHBSSZS
XMEOUT Parameters: date, time,applid, modename
CICS failed to delete resource resource because of an unexpected signon state during the destroy operation.
CICS continues. A system dump is taken with dumpcode ZC5971. Message DFHME0116 is normally produced containing the symptom string for this problem.
You need further assistance from IBM to resolve this problem. See CICS Problem Determination Guide for guidance on how to proceed.
CSMT
DFHBSTS
XMEOUT Parameters: date, time,applid, resource
CICS failed to delete a TERMINAL or SESSIONS resource resource because a terminal or session is still signed on.
CICS continues.
Run the signoff transaction CESF and retry.
CSMT
DFHBSTS
XMEOUT Parameters: date, time,applid, resource
CICS failed to delete a SESSIONS definition ssss because the maximum session-count was reached for MODENAME modename.
CICS continues.
Delete some sessions in modename, or redefine modename with a higher maximum session-count.
CSMT
DFHBSTZS
XMEOUT Parameters: date, time,applid, ssss, modename
CICS failed to delete a POOL pppp. Previous messages(s) should explain the cause of this failure.
CICS continues.
Refer to any previous messages for further guidance and information.
CSMT
DFHBSMPP
XMEOUT Parameters: date, time,applid, pppp
CICS failed to install the POOL definition pppp because the required POOLID parameter was missing. This is a CICS logic error (probably in DFHTRZPP).
CICS continues. A system dump is taken with dumpcode ZC5975. Message DFHME0116 is normally produced containing the symptom string for this problem.
You need further assistance from IBM to resolve this problem. See CICS Problem Determination Guide for guidance on how to proceed.
CSMT
DFHBSMPP, DFHBSTZP
XMEOUT Parameters: date, time,applid, pppp
CICS failed to install a POOL definition because the required POOLCNT parameter was missing. This is a CICS logic error (probably in DFHTRZPP).
CICS continues. A system dump is taken with dumpcode ZC5976. Message DFHME0116 is normally produced containing the symptom string for this problem.
You need further assistance from IBM to resolve this problem. See CICS Problem Determination Guide for guidance on how to proceed.
CSMT
DFHBSMPP
XMEOUT Parameters: date, time,applid
CICS failed to install a POOL definition, because of a failure in building pool entries. Previous messages should explain the cause of this failure.
CICS continues.
Refer to any previous messages for further information and guidance.
CSMT
DFHBSMPP
XMEOUT Parameters: date, time,applid
CICS failed in an attempt to install or delete a POOL definition. Previous messages should explain the cause of this failure.
CICS continues.
Refer to previous messages for further information and guidance.
CSMT
DFHBSMPP, DFHBSTZP
XMEOUT Parameters:
date,
time,
applid,
pppp
CICS has failed to delete pool pppp because the pool still has an active session for terminal termid.
CICS continues.
Put the terminal out of service (using the CEMT transaction) and retry.
CSMT
DFHBSTZP
XMEOUT Parameters: date, time,applid, pppp, termid
The resource resource is in use. taskid is the task number, and tranid is the transaction ID.
CICS continues.
Wait for the termination of task taskid, and retry the operation.
CSMT
DFHBSS, DFHBSSZ, DFHBSTZ, DFHBSTZ1, DFHBSTZ2, DFHBSTZS, DFHBSTZZ,
DFHBST2V
XMEOUT Parameters:
date,
time,
applid,
resource,
taskid,
tranid
CICS has failed to install a resource because POOL pppp does not exist. Previous messages should explain the cause of this failure.
CICS continues.
Refer to the previous messages for further information and guidance.
CSMT
DFHBSTZP
XMEOUT Parameters: date, time,applid, pppp
CICS has failed to delete POOL pppp because the pool still has an entry in use for terminal termid.
CICS continues.
Put the terminal out of service (using the CEMT transaction) and retry.
CSMT
DFHBSMPP
XMEOUT Parameters: date, time,applid, pppp, termid
CICS failed to install resource resource either because it already exists, or for reasons explained in previous messages.
Possible causes are:
CICS continues.
Refer to previous messages for further information and guidance.
If no previous messages were issued, check your terminal identifiers.
CSMT
DFHBSS, DFHBSTZ,
DFHBSTZ1, DFHBSTZ2
XMEOUT Parameters:
date,
time,
applid,
resource
The installation or deletion of the communications resource, resname1 of resource type restype1 has failed. This resource refers to a system entry, sysname, which is being updated by another task. The other task is identified by taskname and taskid. The resource type restype1 can be terminal, remote terminal, connection, remote connection, or indirect connection. The message is issued by module modname.
CICS continues but reverses the effects of the installation or deletion.
Wait until the other task has completed then retry the action.
CSMT
DFHBSTZ, DFHBSTZ1, DFHBSTZ2, DFHBSSZI
XMEOUT Parameters: date, time,applid, restype1, resname1, taskname, taskid, sysname, modname
CICS has failed to install resource resource. Previous message(s) should give the reason for the failure.
CICS continues.
Refer to previous messages for further information and guidance.
CSMT
DFHBSTZC
XMEOUT Parameters: date, time,applid, resource
Either the warm keypoint program (DFHWKP), or the query transaction (DFHQRY), made an invalid request which could not be implemented.
CICS continues. A system dump is taken with dumpcode ZC5986. Message DFHME0116 is normally produced containing the symptom string for this problem.
You need further assistance from IBM to resolve this problem. See CICS Problem Determination Guide for guidance on how to proceed.
CSMT
DFHZCQCH
XMEOUT Parameters: date, time,applid
The installation or deletion of communications resource resname1 of resource type restype1 has failed. Table builder services cannot complete the change because another task is updating a definition which uses the resource resname2 of resource type restype2. The other task is identified by taskid and taskname. Restype2 can be a termid, netname, a unique network-qualified ID, or a pipeline terminal pool_name Restype1 can be a terminal, a session, a remote terminal, a connection, a remote connection, or a pipeline terminal. The message was issued by module modname.
CICS continues but reverses this install or delete.
Wait until the other task has completed and then retry the action.
CSMT
DFHBSS, DFHBSTZ, DFHBSTZS, DFHBSTZV, DFHBSTZZ, DFHBSTZ1, DFHBSTZ2, DFHBSMPP, DFHBSTZP
XMEOUT Parameters: date, time,applid, restype1, resname1, taskname, taskid, restype2, resname2, modname
CICS failed to install resource resource because CICS was initialized without VTAM support.
CICS continues.
If you want to install VTAM resources urgently, shut down CICS, and restart it with the system initialization parameter ACCESSMETHOD=VTAM, and appropriate TCT or RDO terminal definitions.
CSMT
DFHBSSZS, DFHBSSZ6, DFHBSTZV
XMEOUT Parameters: date, time,applid, resource
CICS failed to delete resource resource because a remote delete in system cccc failed.
Previous messages should explain the cause of this failure.
CICS continues.
Refer to the previous message for further information and guidance.
CSMT
DFHBSTZ1, DFHBSTZ2
XMEOUT Parameters: date, time,applid, resource, cccc
CICS rejected an INSTALL or DELETE request because it does not recognize the request code.
CICS continues. A system dump is taken with dumpcode ZC5990. Message DFHME0116 is normally produced containing the symptom string for this problem.
You need further assistance from IBM to resolve this problem. See CICS Problem Determination Guide for guidance on how to proceed.
CSMT
DFHZCQ00
XMEOUT Parameters: date, time,applid
CICS rejected a VALIDATE BIND request because no BIND was supplied.
CICS continues. A system dump is taken with dumpcode ZC5991. Message DFHME0116 is normally produced containing the symptom string for this problem.
You need further assistance from IBM to resolve this problem. See CICS Problem Determination Guide for guidance on how to proceed.
CSMT
DFHZCQ00
XMEOUT Parameters: date, time,applid
CICS rejected RESTORE request because the resource types table (DFHZCQRT) in DFHZCQ is incompatible with the recovery record from the log or CICS catalog.
CICS continues. A system dump is taken with dumpcode ZC5992. Message DFHME0116 is normally produced containing the symptom string for this problem.
CICS is unable to warm start correctly. You should therefore shut CICS down and perform a cold or initial start.
CSMT
DFHZCQRS
XMEOUT Parameters: date, time,applid
CICS rejected a RESTORE request because the resource types table (DFHZCQRT) in DFHZCQ is incompatible with the recovery record from the log or CICS catalog.
CICS continues. A system dump is taken with dumpcode ZC5993. Message DFHME0116 is normally produced containing the symptom string for this problem.
You need further assistance from IBM to resolve this problem. See CICS Problem Determination Guide for guidance on how to proceed.
CSMT
DFHZCQRS
XMEOUT Parameters: date, time,applid
CICS rejected a RESTORE request because no recovery record was passed.
CICS continues. A system dump is taken with dumpcode ZC5994. Message DFHME0116 is normally produced containing the symptom string for this problem.
You need further assistance from IBM to resolve this problem. See CICS Problem Determination Guide for guidance on how to proceed.
CSMT
DFHZCQRS
XMEOUT Parameters: date, time,applid
CICS failed to install a resource with resource type code (RTC) xxxx and subtype yyyy (from the Builder Parameter Set) because a resource with type code xxxx, sub-type yyyy, and the associated BIND-image, is not a builder resource type. The RTC and subtype are defined in module DFHZCQRT.
This is a CICS logic error (probably in DFHTRZxP).
CICS continues. A system dump is taken with dumpcode ZC5995. Message DFHME0116 is normally produced containing the symptom string for this problem.
You need further assistance from IBM to resolve this problem. See CICS Problem Determination Guide for guidance on how to proceed.
CSMT
DFHZCQIS
XMEOUT Parameters: date, time,applid, xxxx, yyyy
CICS has rejected an INSTALL request because the resource type code in the request is zero.
CICS continues. A system dump is taken with dumpcode ZC5996. Message DFHME0116 is normally produced containing the symptom string for this problem.
You need further assistance from IBM to resolve this problem. See CICS Problem Determination Guide for guidance on how to proceed.
CSMT
DFHZCQIS
XMEOUT Parameters: date, time,applid
CICS has rejected an INQUIRE request because no TCT entry was passed.
CICS continues. A system dump is taken with dumpcode ZC5997. Message DFHME0116 is normally produced containing the symptom string for this problem.
You need further assistance from IBM to resolve this problem. See CICS Problem Determination Guide for guidance on how to proceed.
CSMT
DFHZCQIQ
XMEOUT Parameters: date, time,applid
CICS rejected a DELETE request because the entry passed is of a type that cannot be deleted, for example, a non-VTAM terminal.
CICS continues.
The failing delete/replace was necessitated by an INSTALL request. Correct the resource type in that request.
CSMT
DFHZCQCH, DFHZCQDL
XMEOUT Parameters: date, time,applid
If DFHZCQCH issues this message, CICS has rejected a CATALOG request because the required entry parameter was not passed.
If DFHZCQDL issues this message, CICS has rejected a DELETE request because the required entry parameter was not passed.
CICS continues. A system dump is taken with dumpcode ZC5999. Message DFHME0116 is normally produced containing the symptom string for this problem.
You need further assistance from IBM to resolve this problem. See CICS Problem Determination Guide for guidance on how to proceed.
CSMT
DFHZCQCH, DFHZCQDL
XMEOUT Parameters: date, time,applid
While executing a request, CICS table builder services detected a severe error. The error is identified by the error code code and the module modname.
CICS rejects the request and takes a dump. CICS writes an exception trace record identified by code, then issues message DFHZC6208 either to the user of the CEDA transaction, or if the request did not originate from CEDA, to the CSMT transient data queue
This failure indicates either an error in CICS, or a storage overlay. You need further assistance from IBM to resolve this problem. See CICS Problem Determination Guide for guidance on how to proceed.
Console
DFHTBSB, DFHTBSD, DFHTBSBP, DFHTBSDP, DFHTBSL, DFHTBSLP, DFHTBSS
XMEOUT Parameters: applid, modname,X'code'
While executing a request, CICS table builder services has detected that the pattern pattern cites a builder that is not declared with DFHBSHDR(ENTRY). pattern is the name of the pattern as coded in the DFHBSPTE macro.
CICS rejects the request. A system dump is taken with dumpcode ZC6202. Message DFHME0116 is normally produced containing the symptom string for this problem.
You need further assistance from IBM to resolve this problem. See CICS Problem Determination Guide for guidance on how to proceed.
CSMT
DFHTBSB, DFHTBSL, DFHTBSQ, DFHTBSR
XMEOUT Parameters: date, time,applid, pattern
While executing a request, CICS table builder services has detected that the subpattern pattern cites a builder that is not declared with DFHBSHDR(ENTRY). pattern is the name of the subpattern as coded in the DFHBSPTE macro.
CICS rejects the request. A system dump is taken with dumpcode ZC6204. Message DFHME0116 is normally produced containing the symptom string for this problem.
You need further assistance from IBM to resolve this problem. See CICS Problem Determination Guide for guidance on how to proceed.
CSMT
DFHTBSBP, DFHTBSDP
XMEOUT Parameters: date, time,applid, pattern
While executing a request, CICS table builder services has detected that the subpattern pattern is invalidly defined. pattern is the name of the subpattern as coded in the DFHBSPTE macro.
CICS rejects the request. A system dump is taken with dumpcode ZC6205. Message DFHME0116 is normally produced containing the symptom string for this problem.
You need further assistance from IBM to resolve this problem. See CICS Problem Determination Guide for guidance on how to proceed.
CSMT
DFHTBSBP, DFHTBSDP
XMEOUT Parameters: date, time,applid, pattern
While executing a DESTROY request, CICS table builder services has detected that the pattern pattern is not valid for a DESTROY request. pattern is the name of the pattern as coded in the DFHBSPTE macro.
CICS rejects the request. A system dump is taken with dumpcode ZC6206. Message DFHME0116 is normally produced containing the symptom string for this problem.
You need further assistance from IBM to resolve this problem. See CICS Problem Determination Guide for guidance on how to proceed.
CSMT
DFHTBSD
XMEOUT Parameters: date, time,applid, pattern
While executing a request, CICS table builder services has detected that builder cited in the pattern pattern has returned an invalid CC key on MAKEKEY. pattern is the name of the pattern as coded in the DFHBSPTE macro.
CICS rejects the request. A system dump is taken with dumpcode ZC6207. Message DFHME0116 is normally produced containing the symptom string for this problem.
You need further assistance from IBM to resolve this problem. See CICS Problem Determination Guide for guidance on how to proceed.
CSMT
DFHTBSBP, DFHTBSDP, DFHTBSL
XMEOUT Parameters: date, time,applid, pattern
While executing a request, CICS table builder services detected a severe error. The error is identified by the error code code and the module modname.
CICS rejects the request. It has already issued message DFHZC6201, written an exception trace record identified by code, and taken a dump.
This failure indicates either an error in CICS, or a storage overlay. You need further assistance from IBM to resolve this problem. See CICS Problem Determination Guide for guidance on how to proceed.
CSMT
DFHTBSB, DFHTBSD, DFHTBSBP, DFHTBSDP, DFHTBSL, DFHTBSLP, DFHTBSS
XMEOUT Parameters: date, time,applid, modname, X'code'
While executing a request, CICS table builder services has detected that the code, xxxx, for a catalog request is invalid.
CICS rejects the request. A system dump is taken with dumpcode ZC6209. Message DFHME0116 is normally produced containing the symptom string for this problem.
You need further assistance from IBM to resolve this problem. See CICS Problem Determination Guide for guidance on how to proceed.
CSMT
DFHTBSL
XMEOUT Parameters: date, time,applid, xxxx
While executing a BUILD, a DESTROY or a RESTORE request, CICS table builder services could not obtain storage for a control block. The control block could be a RRAB, a RABN, an action_block, a recovery record, or a recovery segment. The error code code identifies the element that could not be obtained by the module modname.
CICS rejects the request. It has already written an exception trace record identified by code.
This failure may be a symptom of a expanded dynamic storage area (EDSA) that is too small. If so, you can solve the problem by increasing the size of your CICS region. For guidance on estimating the size of the DSA and the CICS region, see the CICS System Definition Guide and the CICS Performance Guide. You can identify which control block that could not be obtained by formatting the exception trace record.
The failure may also be caused by an error in another transaction, for example, a looping program with an EXEC CICS GETMAIN within the loop.
CSMT
DFHTBSB, DFHTBSD, DFHTBSL, DFHTBSBP, DFHTBSDP, DFHTBSLP, DFHTBSS
XMEOUT Parameters: date, time,applid, X'code', modname
While executing a request during a warm or emergency start, CICS Table Builder Services has detected that the CC record is not compatible with the pattern it names. xxx is the builder ID.
CICS rejects the request.
The CC record was probably written by an earlier level of CICS. That is, you have applied one or more PTF maintenance fixes to the system since the CC record was written. Assuming this is the case, you must either:
CSMT
DFHTBSR, DFHTBSRP
XMEOUT Parameters: date, time,applid, xxx
While processing a RESTORE request, CICS Table Builder Services detected an error reported in a previous message. key is the catalog key for the abandoned record, or, if the key is unknown to CICS, key is the single character ?.
See the previously issued message for the cause of the problem, and follow the recommended user action.
CSMT
DFHTBSR
XMEOUT Parameters: date, time,applid, key
While processing a CATALOG request, CICS Table Builder Services could not obtain recovery record storage.
CICS rejects the request.
This failure may be a symptom of a dynamic storage area (DSA) that is too small. If so, you can solve the problem by increasing the size of your CICS region. For advice on estimating the size of the DSA and the CICS region, see the CICS System Definition Guide and the CICS Performance Guide.
The failure may also be caused by an error in another transaction, for example, a looping program with an EXEC CICS GETMAIN within the loop.
CSMT
DFHTBSLP
XMEOUT Parameters: date, time,applid
The RDO definition for a resource of type restype1 named resname1 could not be installed because of an error. This causes the installable set of RDO definitions associated with restype2 named resname2 to be backed out.
The resource type of the definition that failed restype1 can be connection, session, modegroup, pool, or pooled terminal. The resource type of the associated definition restype2 can be connection, or a pool_name for pipeline terminals.
CICS backs out the installation of the set of associated RDO definitions and continues without them.
Correct the reason for the failure of the definition, identified by previous DFHZXnnnn messages, and then retry the install.
CSMT
DFHTBSB
XMEOUT Parameters: date, time,applid, restype1, resname1, restype2, resname2
A resource tttt was being installed but was found to have the same network name netname as resource rrrr.
The resource is not installed, CICS continues.
If you want the definitions to be installed, use CEDA to correct the network name and reinstall the definition.
CSMT
DFHBSTZV
XMEOUT Parameters: date, time,applid, tttt, netname, rrrr
A connection cccc was being installed but was found to have the same network name netname as resource rrrr.
The resource is not installed, CICS continues.
You cannot have an APPC connection with the same network name as another APPC connection or an LU6.1 connection. That is, you cannot have more than one APPC connection between two systems and an APPC connection cannot be installed with an LU6.1 connection between two systems.
Neither APPC or LU6.1 network names can be the same as a terminal's network name.
Also you cannot have an IRC (or XM) connection with the same network name as another IRC (or XM) connection. However, an IRC network name can be the same as any VTAM network name (APPC or LU61 connection or terminal).
If you want the definitions to be installed, use CEDA to correct the network name and then reinstall the definition.
If you need to replace a connection with a different network name, it must have the same connection name as the one you are replacing.
CSMT
DFHBSS
XMEOUT Parameters: date, time,applid, cccc, netname, rrrr
A resource tttt was being installed but was found to have a duplicate network name netname.
This message occurs:
The resource is not installed; CICS continues.
If you want the definitions to be installed, use CEDA to correct the network name and then reinstall the definition.
CSMT
DFHBSTZV
XMEOUT Parameters: date, time,applid, tttt, netname
CICS has issued a logoff transaction to the remote terminal termid but this terminal cannot be deleted because it is in use by another transaction.
The remote terminal can be reused. CICS continues.
This situation usually occurs because the remote CICS is under stress. Consider allocating more resources. For example, you might need to allocate more storage.
CSMT
DFHBSTZ
XMEOUT Parameters: date, time,applid, termid
A connection cccc specifying protocol(exci) and conntype(generic) was being installed but an existing EXCI generic connection rrrr was found.
The resource is not installed. CICS continues.
There can be only one EXCI generic connection installed in a CICS system. Determine which EXCI generic connection definition is required and remove the duplicate definition.
If you need to replace the EXCI generic connection definition, it must have the same connection name as the one you are replacing.
CSMT
DFHBSS
XMEOUT Parameters: date, time,applid, cccc, rrrr
A connection cccc was being installed but the netname netname is the same as the generic resource name for this CICS (as defined in the SIT GRNAME parameter).
Communication within a SYSPLEX (intra-plex) must be done using member names.
The resource is not installed, CICS continues.
If this connection is for communication within a sysplex, use CEDA to change the NETNAME to the member name of the connection with which you wish to communicate.
If this is for communication between two sysplexes, change the NETNAME to the generic resource name of the partner sysplex.
CSMT
DFHBSS
XMEOUT Parameters: date, time,applid, cccc, netname
During an emergency or warm restart CICS tried to restore connection cccc. However its netname netname is the same as the generic resource name for this CICS (as defined in the GRNAME system initialization parameter).
This is probably because the GRNAME specified in the SIT has been changed. It should only be changed at INITIAL start time.
Processing continues. The resource is not installed.
If this connection is for communication within a sysplex, use CEDA to change the NETNAME to the member name of the connection with which you wish to communicate.
If this is for communication between two sysplexes, change the NETNAME to the generic resource name of the partner sysplex.
If you need to change the GRNAME parameter, remember to do so only during an INITIAL start.
CSMT
DFHBSS
XMEOUT Parameters: date, time,applid, cccc, netname
User userid was attempting to install terminal tttt but the userid does not have sufficient authority. This is because the terminal has preset authority (the definition for terminal tttt specifies a userid value.) Installing a resource with preset security requires special authorization.
Resource security violation messages are logged to the CSCS transient data queue and to the system console. The resource is not installed. CICS continues.
In order to install this resource, do one of the following:
CSMT
DFHBSTS
XMEOUT Parameters: date, time,applid, userid, tttt
A resource tttt was being installed but was found to have an invalid LDCLIST ldclist.
The resource is not installed, CICS continues.
If you want the definition to be installed, use the DFHTCT TYPE=LDCLIST macro to define the listname.
CSMT
DFHBSTBL
XMEOUT Parameters: date, time,applid, tttt, ldclist
A connection tttt was being installed but a non-VTAM terminal with the same name already exists.
The resource is not installed; CICS continues.
Change the name of the connection and reinstall.
CSMT
DFHBSS
XMEOUT Parameters: date, time,applid, tttt
A terminal tttt was being installed but a non-VTAM terminal with the same name already exists.
The resource is not installed; CICS continues.
Change the name of the terminal and reinstall.
CSMT
DFHBSTZ
XMEOUT Parameters: date, time,applid, tttt
CICS has not installed a mode group modename because the maximum number of sessions specified was 0. The CEDA SESSION MAXIMUM parameter cannot be set to 0, so this was possibly caused by a storage overwrite, or by an invalid builder parameter set being shipped into CICS.
The install fails, but CICS continues.
Find the offending builder parameter set and set ZC_MAXSESS_1 to a minimum value of 1.
CSMT
DFHBSM61
XMEOUT Parameters:
date,
time,
applid,
modename
A connection tttt was being installed but a session with the same name already exists.
The resource is not installed; CICS continues.
Change the name of the connection and reinstall.
CSMT
DFHBSS
XMEOUT Parameters: date, time,applid, tttt
CICS has found terminal input output areas (TIOAs) chained to a TCTTE during deletion of a terminal. This is a CICS logic error.
A system dump is taken, the TCTTE is deleted and CICS continues. Message DFHME0116 is normally produced containing the symptom string for this problem.
You need further assistance from IBM to resolve this problem. See CICS Problem Determination Guide for guidance on how to proceed.
It would aid IBM support if you used the system dump to determine why TIOAs are still chained to the TCTTEs. The TIOAs are normally freemained before deletion.
Answers to the following questions would also be helpful:
CADL
DFHBST
XMEOUT Parameters: date, time,applid, termid, modname
CICS has previously detected a loop or abend. Module bymodule called module inmodule which looped or abended.
CICS issues message DFHZC0001 if an abend is detected or DFHZC0004 if a loop is detected. The install or delete being performed is backed out. CICS continues. Message DFHME0116 is normally produced containing the symptom string for this problem.
See the associated message for more guidance.
CADL
DFHBSM61
DFHBSTZS, DFHBSTZR
XMEOUT Parameters:
date,
time,
applid,
inmodule,
bymodule
A connection was being installed but the APPC or MRO session name BITMAP which is used to create a session name, was corrupt. The corrupt BITMAP has been rebuilt.
The APPC session name BITMAP is always used for an APPC session, however the MRO session name BITMAP is only used if the session name is prefixed with ‘<’ or ‘>’.
A dump is taken with dumpcode ZC6350. Trace point ID AP X'FB05' is produced. The install continues. CICS continues.
Use the dump provided to determine the cause of the storage overwrite. See the CICS Problem Determination Guide for guidance on dealing with storage problems.
CSMT
DFHZGBM
XMEOUT Parameters: date, time,applid, type
A ZCP install has failed. This would normally result in a message being issued. However, the GETMAIN attempting to obtain storage from the CDSA for use as a message area has failed. This means that there is no more free storage available in the CDSA.
The message which should have reported the ZCP install failure cannot be issued. Subsequent messages also cannot be issued while there is no free storage available in the CDSA. However, subsequent messages can be issued if storage becomes available on subsequent GETMAIN attempts.
Message DFHME0116 is normally produced containing the symptom string for this problem.
Use trace to determine the source of the problem. Trace point AP FCDD, the TBSM entry, gives the message number which should have been issued and the message insert data. Refer to the description of this message for further guidance.
CSMT
DFHBSTS, DFHBSTZO, DFHZATA2
XMEOUT Parameters:
date,
time,
applid
The resource could not be installed or signed on with preset userid userid because the userid is not known to the external security manager (ESM).
CICS continues.
Correct the userid, or contact your security administrator to have the unknown userid added to your ESM. Then either reinstall the resource definition, or attempt to send a command to CICS via this console.
CSMT
DFHBSTS, DFHBSTZO
XMEOUT Parameters:
date,
time,
applid,
{1=Install,
2=Signon},
{1=netname ,
2=console ,
3=terminal },
portname,
userid
The resource could not be installed or signed on with preset userid userid because the userid has been revoked by the external security manager (ESM).
CICS continues.
Contact your security administrator, who can reauthorize the revoked userid by issuing the ALTUSER RESUME function. Then reinstall the resource definition or try another command from the affected console.
CSMT
DFHBSTS, DFHBSTZO
XMEOUT Parameters:
date,
time,
applid,
{1=Install,
2=Signon},
{1=netname ,
2=console ,
3=terminal },
portname,
userid
The resource could not be installed or signed on with preset userid userid because the access of that userid to the group containing it has been revoked by the external security manager (ESM).
CICS continues.
Contact your security administrator who can restore the access of the preset userid to its group by issuing the CONNECT RESUME function. Then reinstall the resource definition or try another command from the console.
CSMT
DFHBSTS, DFHBSTZO
XMEOUT Parameters:
date,
time,
applid,
{1=Install,
2=Signon},
{1=netname ,
2=console ,
3=terminal },
portname,
userid
The resource could not be installed or signed on with preset userid userid because of unexpected return codes from the external security manager (ESM).
CICS continues. Either message DFHSN1401 or DFHSN1801 is issued.
See the accompanying message for further guidance. Reinstall the resource definition or try another command from the console when you have corrected the problem.
CSMT
DFHBSTS, DFHBSTZO
XMEOUT Parameters:
date,
time,
applid,
{1=Install,
2=Signon},
{1=netname ,
2=console ,
3=terminal },
portname,
userid
The resource could not be installed or signed on with preset userid userid because the external security manager (ESM) is no longer active.
CICS continues.
Contact your security administrator to restart the ESM. Reinstall the resource definition or try the command from a console again when the ESM is active again.
CSMT
DFHBSTS, DFHBSTZO
XMEOUT Parameters:
date,
time,
applid,
{1=Install,
2=Signon},
{1=netname ,
2=console ,
3=terminal },
portname,
userid
The resource could not be installed or signed on with a preset userid because the preset userid is not authorized to use application applid.
CICS continues.
Contact your security administrator who can authorize the preset userid to access the application applid by issuing the PERMIT function for the APPL resource class. Then reinstall the resource definition or try the command again from the console.
CSMT
DFHBSTS, DFHBSTZO
XMEOUT Parameters:
date,
time,
applid,
{1=Install,
2=Signon},
{1=netname ,
2=console ,
3=terminal },
portname,
userid
The resource could not be installed or signed on with preset userid userid because the security label associated with the userid in the external security manager (ESM) does not have the necessary authority.
CICS continues.
Contact your security administrator to assign a new security label to the preset userid. Then reinstall the resource definition or try the command from the console again.
CSMT
DFHBSTS, DFHBSTZO
XMEOUT Parameters:
date,
time,
applid,
{1=Install,
2=Signon},
{1=netname ,
2=console ,
3=terminal },
termid,
userid
The resource could not be installed or signed on with preset userid userid because the external security manager (ESM) has been placed in a "tranquil" state and is not allowing new users to be added to the system.
CICS continues.
Contact your security administrator to establish when the ESM will be fully available again. When it is, reinstall the resource definition or try the command from the console again.
CSMT
DFHBSTS, DFHBSTZO
XMEOUT Parameters:
date,
time,
applid,
{1=Install,
2=Signon},
{1=netname ,
2=console ,
3= terminal },
portname,
userid
The resource could not be installed or signed on because the national language langcode specified in the resource definition is not recognized.
CICS continues.
Change the national language on the resource definition to a valid value and reinstall the resource definition.
CSMT
DFHBSTS, DFHBSTZO, DFHZSGN
XMEOUT Parameters:
date,
time,
applid,
{1=Install,
2=Signon},
{1=netname ,
2=console ,
3=terminal },
portname,
langcode
The resource could not be installed or signed on because the national language langcode specified in the resource definition is not supported in this run of CICS.
CICS continues.
Change the national language in the resource definition to one that has been initialized. Then reinstall the resource definition.
CSMT
DFHBSTS, DFHBSTZO, DFHZSGN
XMEOUT Parameters:
date,
time,
applid,
{1=Install,
2=Signon},
{1=netname ,
2=console ,
3=terminal },
portname,
langcode
The resource could not be installed or signed on with preset userid userid because the specified userid is not authorized to use that resource.
CICS continues. Either message DFHSN1401 or DFHSN1801 is issued.
See the accompanying message for further guidance. Reinstall the resource definition or retry the command from the console when you have corrected the problem.
CSMT
DFHBSTS, DFHBSTZO
XMEOUT Parameters:
date,
time,
applid,
{1=Install,
2=Signon},
{1=netname ,
2=console ,
3=terminal },
portname,
userid
A connection cccc was being installed but the netname netname is the same as the member name of a generic resource connection grcon which is already in use.
The resource is not installed. CICS continues.
If the NETNAME is incorrect, use CEDA to change it. Alternatively if you wish to communicate with the generic resource member by its member name, discard the generic resource connection after ending the VTAM affinity and try again.
CSMT
DFHBSS
XMEOUT Parameters: date, time,applid, cccc, netname, grcon
The node specified has been switched to this system following an XRF takeover.
For the meaning of the sense data, see DFHZCxxxx messages.
Processing continues.
None.
CSNE
DFHZXRC
XMEOUT Parameters: date, time,applid, termid, tranid, netname, sense, instance, {1=DFHZXRC, 2=DFHZXRC, 3=DFHZXRC, 4=DFHZXRC, 5=DFHZXRC}
The terminal has been switched to this CICS system following an XRF takeover, but an error was encountered processing the response data.
For the meaning of the sense data, see DFHZCxxxx messages.
The state of the session at takeover is uncertain and the session is unbound in order to reset the states. The session is simlogged on, and proceeds as a normal emergency restart.
Proceed as for a normal emergency restart.
CSNE
DFHZXRC
XMEOUT Parameters: date, time,applid, termid, tranid, sense, instance, {1=DFHZXRC, 2=DFHZXRC, 3=DFHZXRC, 4=DFHZXRC, 5=DFHZXRC, 6=DFHZXRC, 7=DFHZXRC, 8=DFHZXRC, 9=DFHZXRC, 10=DFHZXRC, 11=DFHZXRC}
Node netname has successfully issued an OPNDST OPTCD=BACKUP command to the connected LU.
For the meaning of the sense data, see DFHZCxxxx messages.
Processing continues.
None.
CSNE
DFHZOPX
XMEOUT Parameters: date, time,applid, termid, tranid, netname, sense, instance, {1=DFHZOPX, 2=DFHZOPX}
The backup system has received a "hierarchical reset" UNBIND on the backup session to the named terminal. This implies that the active session has ended normally.
For the meaning of the sense data, see DFHZCxxxx messages.
CLSDST the backup session.
None.
CSNE
DFHZSCX
XMEOUT Parameters: date, time,applid, termid, tranid, netname, sense, instance, {1=DFHZSCX}
Before the OPNDST is issued, the backup system has abandoned the attempt to establish a backup session for one of the following reasons:
For the meaning of the sense data, see DFHZCxxxx messages.
If this system takes over, the autoconnect process attempts to acquire a session. In this case, it probably takes longer for the session to become available for use.
Do not attempt a backup session.
Rectify error, or downgrade the recovery option specified for this terminal.
CSNE
DFHZOPN
XMEOUT Parameters: date, time,applid, termid, tranid, netname, sense, instance, {1=DFHZOPN, 2=DFHZOPN, 3=DFHZOPN}
The VTAM ACB has been opened, and the function level of the terminal control program (ZCP) and VTAM has been examined. It has been determined that XRF terminal functions cannot be supported in this execution of CICS.
This can be because one of the DFHZCx modules, or the TCT, was assembled against a version of VTAM earlier than 3.1, or because the level of VTAM that has just been opened is pre-3.1.
For the meaning of the sense data, see DFHZCxxxx messages.
Processing continues. Processing continues, but no VTAM XRF functions can be supported.
If VTAM XRF functions are required, check the assembly of each of the DFHZCx modules and the TCT.
If a pre-3.1 release of VTAM was used in the assembly process, then a warning MNOTE will have been issued.
The relevant modules should then be reassembled against the correct level of VTAM.
If the assembly of all modules is correct, then the VTAM used in this execution is at a pre-3.1 level.
Console
DFHZSEX,DFHZSLS
XMEOUT Parameters: applid, sense,instance, {1=DFHZSEX, 2=DFHZSLS}
The TPEND exit has been driven because VTAM has been shutdown. This is an XRF Alternate system and it cannot continue without VTAM.
For the meaning of the sense data, see DFHZCxxxx messages.
The system is abnormally terminated.
Determine why and how VTAM was shutdown.
Console
DFHZTPX
XMEOUT Parameters: applid, sense,instance, {1=DFHZTPX}
The bind passed for AUTOINSTALL of a resource has shown an error in the bind image check call. The fixed part of the BIND is printed (this is the part on which the validation code operates -- see the SNA Network Protocol Formats for details of the BIND RU). The internal return code X'code' identifies the location within the module that invalidated the BIND.
CICS continues but the session is not installed. The request is rejected and message DFHZC2411 is issued. The terminal is not usable until a VTAM LOGOFF command is issued.
Investigate the fixed part of the BIND data to determine the reason for the rejection. The internal return code gives more information that can be used by IBM to help you to determine the cause of the problem. See CICS Problem Determination Guide for guidance on how to proceed.
CADL
DFHZATA
XMEOUT Parameters: date, time,applid, netname, X'response'
An attempt was made to autoinstall either a VTAM device or a console; however, there are no appropriate autoinstall models defined.
CICS processing continues, but the autoinstall logon attempt is rejected.
Use CEDA to define autoinstall model(s). For further information, refer to the CICS Resource Definition Guide.
CADL
DFHZATA, DFHZATA2
XMEOUT Parameters:
date,
time,
applid,
{1=terminal,
2=console}
The connection or terminal or console build process failed.
The reason is given in
a following DFHZC59xx, DFHZC62xx or DFHZC63xx message referring
to the same resid.
These messages are followed by message DFHZC6942.
Processing continues.
Refer to following messages for further information.
CADL
DFHZATA, DFHZATA2
XMEOUT Parameters: date, time,applid, resource, resid, {1=netname, 2=consolename}, id,model
Transaction CATA was autoinstalling a terminal or console, id, when the task abended with abend abend. If the resource being autoinstalled was a terminal, then the issuing module was DFHZATA. Otherwise, the issuing module was DFHZATA2 if the resource was a console. The id can be either a netname or a consolename.
CICS continues but the resource is not installed.
Retry the logon attempt. If the abend indicates a TIMEOUT and this occurs frequently, increase the CATA DTIMOUT value. If you do not want the CATA transaction to time out, remove the DTIMOUT parameter from the CATA DEFINE TRANSACTION command. However, if you do this, and if the system is short on storage, a large number of CATA transactions running at the some time with no other transactions present could cause a deadlock.
CADL
DFHZATA, DFHZATA2
XMEOUT Parameters:
date,
time,
applid,
{1=netname,
2=consolename},
id,
abend
Transaction CATD, program DFHZATD was deleting an autoinstalled resource resid, when the task abended with abend abend.
CICS continues. If the resource still exists, it is reused next time the same TERMID or SYSID is used.
See the description of abend abend for further guidance.
If the abend indicates a TIMEOUT and this occurs frequently, increase the CATD DTIMOUT value. If you do not want the CATD transaction to time out, remove the DTIMOUT parameter from the CATD DEFINE TRANSACTION command. However, a large number of CATD tasks running at the same time with no purgeable tasks present could cause a deadlock if the system is also short on storage.
CADL
DFHZATD
XMEOUT Parameters: date, time,applid, resource, resid, {1=netname, 2=consolename}, id,abend
One of the functions of DFHZATS (transaction CITS, CDTS, CMTS or CFTS) has abended with abend abend.
CICS continues.
For CITS (remote install), if the remote terminal (skeleton) was actually built, CICS might use it.
For CDTS (remote delete), If the remote terminal (skeleton) has not been deleted, it might be reused.
For CMTS (remote mass delete), terminals which have not been deleted by CMTS might be deleted at a later stage.
For CFTS (remote mass flag), terminals which have been flagged for deletion might be deleted at a later stage. If any terminals have not been flagged, attempts might be made to reuse them. This can have unpredictable results.
See the description of abend abend for further guidance.
The most likely reason for this message is a timeout of CITS or CDTS. In the case of CITS, reissue your transaction if necessary.
If the TIMEOUTs occur frequently, consider increasing the CITS or CDTS DTIMOUT values. If you do not want the transactions to time out, remove the DTIMOUT parameter from the CITS or CDTS DEFINE TRANSACTION command. However, a large number of CITS tasks running at the same time with no purgeable tasks present could cause a deadlock if the system is also short on storage.
Note that CFTS and CMTS do not have a DTIMOUT parameter and should not be given one because they only run once after a warm or emergency restart and should not be allowed to time out.
CADL
DFHZATS
XMEOUT Parameters: date, time,applid, termid, tranid, abend
CICS has started to autoinstall a terminal or a connection. This message shows the netname by which CICS will know the device and network qualified name netid.realnet showing the origin of the resource.
CICS continues.
None. This message is for information only.
CADL
DFHZATA
XMEOUT Parameters:
date,
time,
applid,
netname,
netid,
realnet
CICS is autoinstalling a terminal. This message shows the netname by which CICS will know the device and the TN3270 IP address, port number and host name (if present).
CICS continues.
None. This message is for information only.
CADL
DFHZATA
XMEOUT Parameters:
date,
time,
applid,
netname,
tnaddr
An INSTALL for the remote terminal termid has failed. The reason for the failure is specified in associated DFHZC59xx and DFHZC62xx messages.
DFHZATS terminates abnormally with a CICS transaction dump.
See the associated messages for further guidance.
CADL
DFHZATS
XMEOUT Parameters: date, time,applid, termid
A DELETE for remote terminal termid has failed. Possible causes are that the terminal has already been deleted or that it is in use by another task.
If this message is repeated a number of times, there could be a more serious problem.
If the message is associated with message DFHZC6912, CICS continues normally. If message DFHZC6912 is not issued, DFHZATS is abnormally terminated with a transaction dump.
If the message is associated with message DFHZC6912, no action is necessary. If DFHZC6912 is not issued, see the associated DFHZC59xx, DFHZC62xx and DFHZC63xx messages for the reason for the DELETE failure.
CADL
DFHZATS
XMEOUT Parameters: date, time,applid, termid
This message is issued during a mass delete of remote terminals following a warm or emergency restart. A terminal which had been flagged for deletion could not be deleted. The most likely explanation is that the terminal has already been deleted by another task.
An associated DFHZC6911 message gives the identity of the terminal. This might be associated with one or more DFHZC59xx and DFHZC62xx messages giving the reason for the failure.
Processing continues normally.
See the associated messages for further information.
CADL
DFHZATS
XMEOUT Parameters: date, time,applid
A remote DELETE has been attempted for a terminal which has already been deleted by another task.
Processing continues normally.
None.
CADL
DFHZATS
XMEOUT Parameters: date, time,applid, termid
The TCTTE build process failed due to the failure of an internal function call.
The terminal autoinstall process fails. CICS processing continues.
Retry the logon attempt.
CADL
DFHZATA, DFHZATA2
XMEOUT Parameters: date, time,applid, termid, {1=netname,2=consolename}, id, X'retcode'
An unexpected response (INVALID, DISASTER or EXCEPTION) has been received on a call by DFHZATS to function SIGNOFF_TERMINAL_USER during sign-off processing for a remote terminal session running under CRTE.
The terminal sign-off process fails to complete and the terminal user remains signed on. CICS processing continues.
See the related message produced by the domain that detected the original error.
CADL
DFHZATS
XMEOUT Parameters:
date,
time,
applid,
termid,
X'
SNUS_RESPONSE
'
An autoinstall attempt to install APPC NETNAME netname has failed. The autoinstall program call to the autoinstall control program failed with return code x.
The return codes are mapped from the program manager LINK_URM response and reason. More precise reasons for failure can be obtained from trace point PG 0A02.
CICS continues.
The appropriate response depends on the return code as follows:
CADL
DFHZGAI
XMEOUT Parameters: date, time,applid, netname, x
An APPC connection not known to CICS has attempted to connect to CICS. However, the autoinstall control program has given a nonzero return code indicating that the install cannot go ahead.
If you do not support APPC autoinstall, the autoinstall control program (DFHZATDX is the default name) automatically returns a nonzero return code to disallow this function.
The exception trace entry code shows the parameter list for the autoinstall control program. The session is terminated. CICS continues.
The failure code X'code' is as follows:
If APPC autoinstall is supported, examine the autoinstall control program to determine why it has not set the return code to allow the install.
CADL
DFHZGAI
XMEOUT Parameters: date, time,applid, netname, X'code'
An APPC connection not known to CICS has attempted to connect to CICS. However, the autoinstall control program has returned an invalid parameter, or a parameter that has led to an invalid template being used.
The exception trace entry code shows the parameter list for the autoinstall control program. The session is terminated. CICS continues.
The failure code X'code' is one of the following:
For parallel sessions, the SNASVCMG modegroup is missing. The install for the template may have failed - check for any CADL messages mentioning the template name. The template connection may have been corrupted. Try and re-install the template.
For single sessions, the user modegroup name does not match. Change the autoinstall control program to supply the correct template name or use CEDA to reinstall the template correctly.
CADL
DFHZGAI
XMEOUT Parameters: date, time,applid, netname, X'code'
CICS has received a BIND from an unknown APPC node. The autoinstall process was initiated, but an invalid bind parameter has been detected. The parameter in error is indicated by the failure code X'code' which is one of the following:
The exception trace entry with trace point ID 'AP xxxx' (where xxxx is X'code') shows the bind that was received. The session is terminated. CICS continues.
Change the definitions on the connecting LU so that the bind parameters are acceptable to CICS.
CADL
DFHZGAI
XMEOUT Parameters: date, time,applid, netname, X'code'
CICS has successfully installed resource restype resid, with id id, using model or template model. The restype can be TERMINAL or CONNECTION or CONSOLE depending on whether a terminal, an APPC connection, or a console has just been autoinstalled.
CICS continues.
None.
CADL
DFHZATA, DFHZATA2
XMEOUT Parameters:
date,
time,
applid,
restype,
resid,
{1=netname,
2=consolename},
id,
model
The VTAM MTS control vector contained a model name modelname not defined to CICS.
CICS continues. This message is informational.
There are four possible ways of correcting this problem:
CADL
DFHZATA
XMEOUT Parameters: date, time,applid, netname, modelname
An autoinstall attempt occurred using the modelname printed. The MODEL BIND (from the CICS model definition) did not match with the incoming bind in CINIT. The MISMATCH_BITS show which bind bits did not match.
CICS continues.
There are four possible ways of correcting this problem:
CADL
DFHZATA
XMEOUT Parameters: date, time,applid, netname, modelname
CICS verification checks on the format of the control vectors in the CINIT have failed.
offset indicates the first point of failure. This is either a length field greater than 128, or a length field which would cause CICS to overrun the end of a CINIT vector or subvector.
This is either due to incorrect format of the CINIT RU (and therefore probably a VTAM logic error), or due to incorrect parsing of the CINIT RU by DFHZATD, which is a CICS logic error.
CICS continues. The logon request is rejected.
Inspect the format of the CINIT RU as captured by the autoinstall program for all rejected logon requests. The first point of failure may be at offset or before it since CICS verification checks are permissive.
If the format is incorrect, the origin of the invalid CINIT should be tracked and the problem resolved there.
If the format is correct, this is a CICS logic error. In this case you will need further assistance from IBM. See CICS Problem Determination Guide for guidance on how to proceed.
CADL
DFHZATA
XMEOUT Parameters: date, time,applid, netname, nn, offset
An AUTOINSTALL attempt to install resource resid has failed.
CICS continues.
For the cause of the failure, look for a previous message containing the same resid.
CADL
DFHZATA, DFHZATA2
XMEOUT Parameters: date, time,applid, resource, resid
An AUTOINSTALL attempt to delete resource resid has failed.
CICS continues.
For the cause of the failure, look for a previous message containing the same resid.
CADL
DFHZATD
XMEOUT Parameters: date, time,applid, resource, resid, {1=netname, 2=consolename}, id
An autoinstall attempt to install terminal id has failed.
The autoinstall program call to the user exit program failed with
return code x.
The id is either a netname or a consolename.
CICS continues.
Possible causes of the problem and an indication of how to solve them are given in the following list of return code meanings:
CADL
DFHZATA, DFHZATA2
XMEOUT Parameters: date, time,applid, {1=netname, 2=consolename}, id, x
An autoinstall attempt to install resource id has failed.
The issuing module, either DFHZATA or DFHZATA2,
called the user exit program for DELETE but the user exit
failed for reasons given in return code x.
If the resource being installed was a terminal, the issuing
module was DFHZATA. Otherwise, if a console was being installed,
DFHZATA2 was the issuing module.
CICS continues.
Possible causes of the problem and an indication of how to solve them are given in the following list of return code meanings:
CADL
DFHZATA, DFHZATA2
XMEOUT Parameters: date, time,applid, {1=netname, 2=consolename}, id, x
CICS has deleted the autoinstalled resource resid. The call to the delete user exit program failed for reasons given in return code x.
CICS continues.
Possible causes of the problem and an indication of how to solve them are given in the following list of return code meanings:
CADL
DFHZATD
XMEOUT Parameters: date, time,applid, resource, resid, {1=netname, 2=consolename}, id,x
CICS was attempting to delete an autoinstalled APPC connection sysid but the attempt failed because CICS was unable to initiate the CATD transaction. The specific circumstances depend on the module:
The connection is left in a released state. CICS continues.
Ensure that the definitions for transaction CATD and program DFHZATD are correct. If you still wish to delete this connection, use CEMT DISCARD CONNECTION or EXEC CICS DISCARD CONNECTION.
CADL
DFHZATR, DFHZCLS, DFHZGCH
XMEOUT Parameters: date, time,applid, sysid, netname, module
An autoinstall attempt to install terminal termid has failed. The autoinstall program call to the user exit program failed with return code x.
CICS continues.
Possible causes of the problem and an indication of how to solve them are as follows:
CADL
DFHZATS
XMEOUT Parameters: date, time,applid, termid, x
An autoinstall attempt to install terminal termid has failed. The autoinstall program call to the user exit program failed with return code x.
CICS continues.
Possible causes of the problem and an indication of how to solve them are as follows:
CADL
DFHZATMD
XMEOUT Parameters: date, time,applid, termid, x
The RESOURCE, PRINTER, or ALTPRINTER ID
supplied by the AUTOINSTALL exit program is invalid.
The return code n can be one of the following:
CICS continues but does not install the object.
Change the AUTOINSTALL exit program to create IDs that contain only valid characters. These are specified in the CICS Resource Definition Guide.
CADL
DFHZATA, DFHZATA2
XMEOUT Parameters: date, time,applid, {1=netname, 2=consolename}, id, X'termid', {1=RESOURCE, 2=PRINTER, 3=ALTPRINTER}, n
CICS has successfully deleted the autoinstalled resource
restype resid.
The restype can be a terminal, an APPC connection,
or a console.
CICS continues.
None.
CADL
DFHZATD
XMEOUT Parameters: date, time,applid, restype, resid, {1=netname, 2=consolename}, id
An autoinstall attempt has failed for lack of an exact match.
netname is the netname of the LU which failed to logon,
model is the name of the model that gave the best failure (that is, the one that had the fewest bits different from the BIND image supplied by VTAM).
The following associated information is also written to CADL:
CICS continues.
For further information, refer to the CICS Customization Guide.
More on the meaning of the various bits in a bind image may be found in ACF/VTAM Programming manual, (SC27-0611).
Details of the preparation of VTAM logmode table entries are given in ACF/VTAM Customization manual, (SC27-0613).
CADL
DFHZATA
XMEOUT Parameters: date, time,applid, netname, model