DFHZCxxxx messages

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:

xx
meaning
X'00'
User sense data only (see zzzz)
X'08'
Request reject
X'10'
Request error
X'20'
State error
X'40'
Request header (RH) usage error
X'80'
Path error

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.

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

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

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

System action:

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

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

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

User response:

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

Look up the MVS code, if there is one, in the 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.

Destination:

Console

Modules:

DFHZGBM, DFHZGCA, DFHZGCC, DFHZGCN, DFHZGDA, DFHZGPC, DFHZGRP, DFHZGSL, DFHZGUB

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

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

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

System action:

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

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

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

User response:

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

CICS may not have been terminated. If the message occurs once and module modname is not crucial to the running of your CICS system, you may decide to continue 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.

Destination:

Console

Modules:

DFHZGCA, DFHZGCC, DFHZGCN, DFHZGDA, DFHZGPC, DFHZGRP, DFHZGSL, DFHZGUB

XMEOUT Parameters: applid, X'code',modname

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

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

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

System action:

An exception entry is made in the trace table (code X'code' in the message). A system dump is taken, unless you have specifically suppressed dumps in the dump table. CICS will continue unless you have specified in the dump table that CICS should terminate.

If appropriate, an error return code is sent to the caller of this domain. In this case, CICS could be terminated by the caller A message will be issued to this effect. Message DFHME0116 is normally produced containing the symptom string for this problem.

User response:

Inform the system programmer.

Try increasing the size of the DSA or EDSA. See the CICS System Definition Guide or the CICS Performance Guide for more information on CICS storage.

Destination:

Console

Modules:

DFHTCRP, DFHZGRP

XMEOUT Parameters: applid, X'code',modname

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

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

System action:

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

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

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

User response:

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

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

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

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

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

Destination:

Console

Modules:

XMEOUT Parameters: applid, X'offset', modname

DFHZC0101I
date time applid A predatory takeover has forced VTAM to allow another application to open the ACB which CICS was using.
Explanation:

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.

System action:

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.

User response:

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.

Destination:

Console and Transient Data Queue CSNE

Modules:

DFHZNCA

XMEOUT Parameters: date, time,applid

DFHZC0110
date time applid The LU6.2 NIB and the TCTTE/BIND data for session sessid did not match during a persistent sessions restart. Reason code X'n'.
Explanation:

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.

Reason
Explanation
1
Single/parallel session indication did not match.
2
LU type did not match.
3
LU type and single/parallel session did not match.
System action:

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.

User response:

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.

Destination:

CSNE

Modules:

DFHZGPC

XMEOUT Parameters: date, time,applid, sessid, X'n'

DFHZC0111
date time applid No session TCTTE is available to match sysid sysid for modename modename because VTAM has returned more NIBs than the CNOS session limit values require.
Explanation:

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.

System action:

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.

User response:

None.

Destination:

CSNE

Modules:

DFHZGPC

XMEOUT Parameters: date, time,applid, sysid, modename

DFHZC0112
date time applid No TCTME was found for sysid sysid modename modename during a persistent sessions restart.
Explanation:

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.

System action:

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.

User response:

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

Destination:

CSNE

Modules:

DFHZGPC

XMEOUT Parameters: date, time,applid, sysid, modename

DFHZC0120I
applid VTAM sessions persisted for a cold or initial start. Sessions terminated. Inquire issued icount, sessions persisting spcount, sessions terminated stcount.
Explanation:

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:

System action:

CICS continues.

User response:

None.

Destination:

Console

Modules:

DFHZGRP

XMEOUT Parameters: applid, icount,spcount, stcount

DFHZC0121I
applid VTAM sessions persisted for a WARM start. Sessions terminated. Inquires issued icount, sessions persisting spcount, sessions terminated stcount.
Explanation:

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:

System action:

CICS continues.

User response:

Examine the JOBLOG from the previous run to determine why sessions persisted despite a WARM shut down.

Destination:

Console

Modules:

DFHZGRP

XMEOUT Parameters: applid, icount,spcount, stcount

DFHZC0122I
applid VTAM sessions persisted for an EMERGENCY, XRF=YES start. Sessions terminated. Inquires issued icount, sessions persisting spcount, sessions terminated stcount.
Explanation:

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:

System action:

CICS continues.

User response:

You should not mix XRF and persistent sessions. If you wish to use XRF, do a cold or initial start.

Destination:

Console

Modules:

DFHZGRP

XMEOUT Parameters: applid, icount,spcount, stcount

DFHZC0123I
applid VTAM sessions persisted when OPEN VTAM ACB issued. Sessions terminated. Inquires issued icount, sessions persisting spcount, sessions terminated stcount.
Explanation:

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:

System action:

CICS continues.

User response:

None.

Destination:

Console

Modules:

DFHZGRP

XMEOUT Parameters: applid, icount,spcount, stcount

DFHZC0124I
applid VTAM sessions persisted for an EMERGENCY start. Inquires issued icount, sessions persisting spcount, sessions terminated stcount, sessions OPNDSTed socount, sessions in error secount.
Explanation:

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:

System action:

CICS continues.

User response:

None.

Destination:

Console

Modules:

DFHZGRP

XMEOUT Parameters: applid, icount,spcount, stcount, socount, secount

DFHZC0125
date time applid netname persistent session will be terminated. sense ((instance) Module name: {DFHZGRP})
Explanation:

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.

Instance
Point ID and Explanation
1
X'FB21' There is not enough storage to recover an APPC session.
2
X'FB22' There is not enough storage to recover a terminal session.
3
X'FB25' The NIB and the TCTTE with the same NETNAME were not of the same LU TYPE.
System action:

An AP exception trace with a point ID as above is issued. The session is terminated and CICS continues.

User response:

The exception trace point identifies where the message was issued and determines the action to take.

Destination:

CSNE

Modules:

DFHZGRP

XMEOUT Parameters: date, time,applid, netname, sense, instance, {1=DFHZGRP, 2=DFHZGRP, 3=DFHZGRP}

DFHZC0126I
applid No VTAM sessions persisted for an EMERGENCY restart.
Explanation:

CICS was initializing with an EMERGENCY start but no VTAM sessions persisted from a previous CICS run. Possible reasons are:

System action:

CICS continues.

User response:

None.

Destination:

Console

Modules:

DFHZGRP

XMEOUT Parameter: applid

DFHZC0127
applid Cannot reestablish persisting sessions - VTAM ACB is closed. Code: X'code'. Module name: module
Explanation:

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.

System action:

CICS continues to close the VTAM ACB and then runs without VTAM support.

User response:

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.

Destination:

Console

Modules:

DFHZGRP DFHZGUB

XMEOUT Parameters: applid, X'code',module

DFHZC0128
applid Cannot reestablish persisting sessions - VTAM not responding. Module name: module
Explanation:

CICS is processing VTAM persisting sessions. However it has issued a VTAM macro and has waited for 8 minutes for the response.

System action:

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.

User response:

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.

Destination:

Console

Modules:

DFHZGRP, DFHZGUB

XMEOUT Parameters: applid, module

DFHZC0129
applid VTAM OPNDST RESTORE failed. All sessions in the NIBLIST will be terminated instead. RTNCD,FDB2: X'rc',X'fd'. Code: X'code'
Explanation:

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.

System action:

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.

User response:

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.

Destination:

Console

Modules:

DFHZGRP

XMEOUT Parameters: applid, X'rc',X'fd', X'code'

DFHZC0130
applid VTAM INQUIRE PERSESS failed. Cannot restore any persisting sessions. RTNCD,FDB2: X'rc',X'fd'. Code: X'code'
Explanation:

CICS is processing VTAM persistent sessions but VTAM returned a RTNCD,FDB2 of rc,fd in response to the INQUIRE OPTCD=PERSESS macro.

System action:

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.

User response:

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.

Destination:

Console

Modules:

DFHZGRP

XMEOUT Parameters: applid, X'rc',X'fd', X'code'

DFHZC0131
date time applid netname termid VTAM OPNDST RESTORE failed.
Explanation:

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.

System action:

CICS continues.

User response:

Reopen the session in the normal way.

Destination:

CSNE

Modules:

DFHZGRP

XMEOUT Parameters: date, time,applid, netname, termid

DFHZC0132
applid VTAM INQUIRE PERSESS failed. Cannot restore some persisting sessions. Network only partially restored. RTNCD,FDB2: X'rc',X'fd'. Code: X'code'
Explanation:

CICS is processing VTAM persistent sessions but VTAM returned a RTNCD,FDB2 of rc,fd in response to a subsequent INQUIRE OPTCD=PERSESS macro.

System action:

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.

User response:

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.

Destination:

Console

Modules:

DFHZGRP

XMEOUT Parameters: applid, X'rc',X'fd', X'code'

DFHZC0133A
applid Persistent session recovery failed.
Explanation:

CICS was initializing when an attempt to process VTAM persistent session failed. The reasons are given in earlier messages.

System action:

CICS terminates.

User response:

Examine earlier messages and exception trace entries to determine the reason for failure.

Destination:

Console

Modules:

DFHSII1

XMEOUT Parameter: applid

DFHZC0134I
applid VTAM sessions persisted when OPEN ACB issued. Inquires issued icount, sessions persisting spcount, sessions terminated stcount, sessions OPNDSTed socount, sessions in error secount.
Explanation:

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:

System action:

CICS continues.

User response:

None.

Destination:

Console

Modules:

DFHZGRP

XMEOUT Parameters: applid, icount,spcount, stcount, socount, secount

DFHZC0136
applid PSDI value indicated persistence but the run time VTAM does not support persistent sessions.
Explanation:

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.

System action:

CICS sets the PSDI value to 0 and continues without persistent session support.

User response:

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.

Destination:

Console

Modules:

DFHZSLS

XMEOUT Parameter: applid

DFHZC0137
applid PSDI value indicated persistence but the TCT assemble time VTAM does not support persistent sessions.
Explanation:

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.

System action:

CICS sets the PSDI value to 0 and continues without persistent session support.

User response:

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.

Destination:

Console

Modules:

DFHZSLS

XMEOUT Parameter: applid

DFHZC0140
applid SETLOGON PERSIST failed. RTNCD,FDB2: X'rc',X'fd'. Code: X'code'
Explanation:

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.

System action:

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.

User response:

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.

Destination:

Console

Modules:

DFHZGSL

XMEOUT Parameters: applid, X'rc',X'fd', X'code'

DFHZC0144
date time applid sysid termid Synclevel 2 conversation started by netname before completion of exchange lognames. sense ((instance) Module name: {DFHZGDA})
Explanation:

CICS has received an attach FMH5 for a synclevel 2 conversation from a partner with netname netname before exchange lognames processing is complete.

System action:

A Deallocate(Abend) with sense code 08640001 is issued for the conversation.

User response:

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

Destination:

CSNE

Modules:

DFHZGDA

XMEOUT Parameters: date, time,applid, sysid, termid, netname, sense, instance, {1=DFHZGDA}

DFHZC0145
date time applid netname termid Synclevel 2 APPC conversation started before Exchange Lognames completed. Error occurred executing Deallocate(Abend). sense ((instance) Module name: {DFHZGDA})
Explanation:

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.

Instance
Explanation
01
DFHZGDA called with chain Finite State Machine in unexpected state.
02
DFHZGDA called with bracket Finite State Machine in unexpected state

For the meaning of the sense data, see DFHZCxxxx messages.

System action:

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.

User response:

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.

Destination:

CSNE

Modules:

DFHZGDA

XMEOUT Parameters: date, time,applid, netname, termid, sense, instance, {1=DFHZGDA, 2=DFHZGDA}

DFHZC0146
date time applid VTAM session for termid successfully recovered following a persistent sessions restart sense ((instance) Module name: {DFHZXRC})
Explanation:

CICS has restored the VTAM persistent session for terminal termid following a persistent sessions restart.

The equivalent message for APPC sessions is DFHZC0156.

System action:

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.

User response:

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.

Destination:

CSNE

Modules:

DFHZXRC

XMEOUT Parameters: date, time,applid, termid, sense, instance, {1=DFHZXRC}

DFHZC0147
date time applid sysid termid Error occurred recovering persisting session. sense ((instance) Module name: {DFHZGDA})
Explanation:

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;

Instance
Point ID and explanation
1
X'FB79' SEND not executed due to invalid bracket state.
2
X'FB7B' Insufficient storage for session recovery.
3
X'FB76' Recovery status byte TCTE_PRSS contains an unexpected value.
4
X'FB7A' RECEIVE not executed due to invalid bracket state.
5
X'FB78' Unexpected sense received during persistent sessions recovery.
System action:

An AP exception trace with a point ID as above is issued. The session is terminated and CICS continues.

User response:

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.

Destination:

CSNE

Modules:

DFHZGDA

XMEOUT Parameters: date, time,applid, sysid, termid, sense, instance, {1=DFHZGDA, 2=DFHZGDA, 3=DFHZGDA, 4=DFHZGDA, 5=DFHZGDA}

DFHZC0148
date time applid sysid termid VTAM send or receive failed during persistent sessions recovery. sense ((instance) Module name: {DFHZGDA})
Explanation:

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.

System action:

The session is terminated.

User response:

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.

Destination:

CSNE

Modules:

DFHZGDA

XMEOUT Parameters: date, time,applid, sysid, termid, sense, instance, {1=DFHZGDA, 2=DFHZGDA}

DFHZC0149
date time applid termid Connection failure occurred during a persistent sessions restart sense ((instance) Module name: {DFHZNSP})
Explanation:

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.

System action:

Processing continues.

User response:

None

Destination:

CSNE

Modules:

DFHZNSP

XMEOUT Parameters: date, time,applid, termid, sense, instance, {1=DFHZNSP}

DFHZC0150
date time applid termid Error processing the session state data returned after a persistent sessions restart. sense ((instance) Module name: {DFHZXRC})
Explanation:

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.

Instance
Explanation
01
DFHZXRC called with an invalid request.
02
TCTTEDA contains null characters instead of the expected address.
03
Reserved
04
The vector key of the data passed by VTAM is not correct.
05
The length of the vector_29 data is too short.
06
Unidentified cleanup action detected.
07
Unidentified recovery option detected.
08
Invalid cleanup action for RECOVOPTION(NONE).
09
Invalid cleanup action for RECOVOPTION(MESSAGE).
10
Invalid cleanup action for RECOVOPTION(TRANSACTION).
11
Reserved.
12
DFHZXRC has been driven to process an LU6 session.
13
Neither XRF nor persistent sessions recovery is in progress DFHZXRC has been called in error.

For the meaning of the sense data, see DFHZCxxxx messages.

System action:

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.

User response:

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.

Destination:

CSNE

Modules:

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}

Start of changeDFHZC0151End of change
Start of changedate time applid Transaction transid was started invalidly. transid will terminate.End of change
Start of change
Explanation:

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.

End of change
Start of change
System action:

transid will terminate.

End of change
Start of change
User response:

None

End of change
Start of change
Destination:

CSNE

End of change
Modules:

Start of changeDFHZSGN, DFHZPCT, DFHZRTPEnd of change

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

DFHZC0152
date time applid termid Signon of user at termid termid failed following a persistent sessions restart. Return code rc was received from the user domain.
Explanation:

CICS attempted to sign on a user following a persistent sessions restart. The user domain replied with one of the following return codes:

Return code
Explanation
005
The user is already signed on.
006
The userid is not authorized for this terminal.
008
The user's access to the specific group has been revoked.
009
The security label associated with the userid in the ESM does not have the necessary authority.
010
The userid was not contained in the group specified.
011
The userid has been revoked.
012
The userid is not known to the ESM.
015
SEC=NO was specified in the SIT.
016
The ESM is not responding.
017
The ESM is not responding.
018
The ESM returned a response which was not recognized by the CICS security domain.
27
The user domain returned a disaster response.
System action:

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.

User response:

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

Destination:

CSNE

Modules:

DFHZSGN

XMEOUT Parameters: date, time,applid, termid, termid, rc

Start of changeDFHZC0153End of change
Start of changedate time applid A catalog write failed in the restart timer program.End of change
Start of change
Explanation:

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.

End of change
Start of change
System action:

An exception trace is output.

End of change
Start of change
User response:

Investigate the cause of the error. There may be a problem with the global catalog. Look for other messages confirming this.

End of change
Start of change
Destination:

CSNE

End of change
Modules:

Start of changeDFHZRTPEnd of change

Start of changeXMEOUT Parameters:End of changeStart of change End of changeStart of changedate, End of changeStart of changetime,End of changeStart of changeapplidEnd of change

Start of changeDFHZC0154End of change
Start of changedate time applid Timed start or cancellation of the restart timer program failed.End of change
Start of change
Explanation:

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.

End of change
Start of change
System action:

CICS initialization continues. In the event of a Persistent Sessions restart terminals will not be signed on.

End of change
Start of change
User response:

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.

End of change
Start of change
Destination:

CSNE

End of change
Modules:

Start of changeDFHTCRP, DFHZPCTEnd of change

Start of changeXMEOUT Parameters:End of changeStart of change End of changeStart of changedate, End of changeStart of changetime,End of changeStart of changeapplidEnd of change

DFHZC0155
date time applid sysid termid Error occurred during processing of session state data returned after restart of persisting session. sense ((instance) Module name: {DFHZXPS})
Explanation:

System action:

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

User response:

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.

Destination:

CSNE

Modules:

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}

DFHZC0156
date time applid sysid VTAM APPC session termid successfully recovered following a persistent sessions restart. sense ((instance) Module name: {DFHZXPS})
Explanation:

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.

System action:

Processing continues.

User response:

None.

Destination:

CSNE

Modules:

DFHZXPS

XMEOUT Parameters: date, time,applid, sysid, termid, sense, instance, {1=DFHZXPS, 2=DFHZXPS}

Start of changeDFHZC0157End of change
Start of changedate time applid sysid VTAM APPC session termid could not be recovered following a persistent sessions restart. The session will be unbound.sense ((instance) Module name: {DFHZXPS})End of change
Start of change
Explanation:

CICS was unable to restore the APPC persisting session for sysid termid following a persistent sessions restart. There are three possible reasons for this:

  1. The BIND processing was incomplete when CICS failed.
  2. Resynchronization was in progress for the session when CICS failed.
  3. The recovery data returned by VTAM for the session was capable of more than one interpretation.

The TCTTE and TIOA are output for information only.

End of change
Start of change
System action:

The session is unbound and rebound.

End of change
Start of change
User response:

None.

End of change
Start of change
Destination:

CSNE

End of change
Modules:

Start of changeDFHZXPSEnd of change

Start of changeXMEOUT Parameters:End of changeStart of change End of changeStart of changedate, End of changeStart of changetime,End of changeStart of changeapplid, End of changeStart of changesysid, End of changeStart of changetermid, End of changeStart of changesense, End of changeStart of changeinstance, End of changeStart of change{1=DFHZXPS}End of change

Start of changeDFHZC0158End of change
Start of changedate time applid Persistent sessions signon data for terminal termid could not be written to the catalog.End of change
Start of change
Explanation:

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.

End of change
Start of change
System action:

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.

End of change
Start of change
User response:

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.

End of change
Start of change
Destination:

CSNE

End of change
Modules:

Start of changeDFHZSGN, DFHZPCT, DFHSNTUEnd of change

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

DFHZC0160
date time applid tranid CNOS changes for modename modename to node netname connection sysid are incomplete.
Explanation:

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.

System action:

The modegroup is left in the state reached after the second attempt to implement the changes.

User response:

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.

Destination:

CSNE

Modules:

DFHZGCA

XMEOUT Parameters: date, time,applid, tranid, modename, netname, sysid

DFHZC0161
date time applid tranid CNOS command for modename modename to node netname connection sysid has failed with code X'code'.
Explanation:

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:

X'FBA2'
The request to create a lock manager lock for modename failed.
X'FBA3'
CICS could not allocate a session for the CNOS negotiation conversation.
X'FBA6'
The request to obtain a lock manager lock for modename failed.
X'FBAA'
modename was not found or has been defined with one of the reserved names SNASVCMG or CPSVCMG.
X'FBAB'
sysid is known, but not as a connection.
X'FBAC'
The specified connection sysid has no modegroups. This is probably caused by a storage overwrite.
X'FBAD'
The first modegroup on the specified connection sysid has no sessions. This is probably caused by a storage overwrite.
X'FBAF'
The receive command for the CNOS reply failed.
X'FBB1'
The send command for the CNOS command or CNOS reply failed.
X'FBB2'
The session for the single-session connection could not be found. This is probably caused by a storage overwrite.
X'FBB3'
sysid is not a known connection name.
X'FBB4'
The connection is defined to CICS as not supporting CNOS. This is probably caused by a storage overwrite.
X'FBB9'
CICS sent a CNOS command for a specific modename but the partner system returned a CNOS reply indicating all modegroups. This is a protocol violation.
System action:

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.

User response:

This depends on the error code as follows:

X'FBA2'
Follow the guidance given for the lock manager console message that precedes this.
X'FBA3'
If all the sessions are busy, make one available and retry.
X'FBA6'
Follow the guidance given for the lock manager message that precedes this.
X'FBAA'
Reissue the request with the correct modename.
X'FBAB'
Reissue the request with the correct connection name.
X'FBAC'
See the CICS Problem Determination Guide for further guidance on storage problems.
X'FBAD'
Same as for X'FBAC'.
X'FBAF'
The connected system, or the link to it, has failed. Determine the reason for this from any other messages produced.
X'FBB1'
Same as for X'FBAF'.
X'FBB2'
Same as for X'FBAC'.
X'FBB3'
Reissue the request with the correct connection name.
X'FBB4'
Same as for X'FBAC'.
X'FBB9'
Investigate why the connected system is not following the APPC protocols.
Destination:

CSNE

Modules:

DFHZGCN

XMEOUT Parameters: date, time,applid, tranid, modename, netname, sysid, X'code'

Start of change
DFHZC0162
date time applid tranid CNOS transaction for connection sysid has failed with code X'code' subcode X'subcode'.
Explanation:

The change number of sessions (CNOS) transaction program DFHZLS1 could not complete successfully. The error code X'code' is one of the following:

X'FB92'
The transaction was not started as an IC request with data or by an attach flow from a connected system. The insert subcode is the start code from XMIQ_START_CODE.
X'FB93'
The transaction was started with data, but no data was found.
X'FB94'
The transaction was started with data, but the data was not in the form of the correct parameter list.
X'FB95'
The transaction was started with the correct format parameter list, but the function code was invalid.
X'FB96'
The transaction was started by an attach from a connected system but there was no CNOS data.
X'FB97'
The transaction was started by an attach from a connected system but the associated data was not a CNOS command.
X'FB9E'
The transaction was started but CICS is shutting down and the VTAM ACB is closed.

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.

System action:

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.

User response:

This depends on the error code as follows:

X'FB92'
The transaction was probably started by entering the transaction ID at a terminal. This is not allowed.
X'FB93'
Analyze the dump to determine why IC could not find the data.
X'FB94'
Analyze the dump to determine what the data was.
X'FB95'
Analyze the dump to determine what the data was.
X'FB96'
Analyze the dump to determine why no data was available.
X'FB97'
Analyze the dump to determine why the correct data was not sent with the attach.
X'FB9E'
No action to take.
Destination:

CSNE

Modules:

DFHZLS1

XMEOUT Parameters: date, time,applid, tranid, sysid, X'code', X'subcode'

End of change
Start of changeDFHZC0163End of change
Start of changedate time applid termid User signed on successfully at termid termid following a persistent sessions restart.End of change
Start of change
Explanation:

CICS successfully signed on a user at termid termid following a persistent sessions restart.

End of change
Start of change
System action:

CICS continues.

End of change
Start of change
User response:

None.

End of change
Start of change
Destination:

CSNE

End of change
Modules:

Start of changeDFHZSGNEnd of change

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

Start of changeDFHZC0164End of change
Start of changedate time applid termid Terminal termid was timed out by CICS following a persistent sessions restart.End of change
Start of change
Explanation:

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.

End of change
Start of change
System action:

CICS continues.

End of change
Start of change
User response:

The user is forced to sign on again.

End of change
Start of change
Destination:

CSNE

End of change
Modules:

Start of changeDFHZSGNEnd of change

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

Start of changeDFHZC0165End of change
Start of changedate time applid termid Termid termid was timed out after a multinode persistent sessions restart. The terminal has been signed off.End of change
Start of change
Explanation:

CICS signed off a user at termid termid following a multinode persistent sessions restart.

End of change
Start of change
System action:

CICS continues.

End of change
Start of change
User response:

None.

End of change
Start of change
Destination:

CSNE

End of change
Modules:

Start of changeDFHZSGNEnd of change

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

Start of changeDFHZC0167End of change
Start of changedate time applid termid An attempt to sign off a user at termid termid failed following a multinode persistent sessions restart. Response code rc1 and reason code rc2 were received.End of change
Start of change
Explanation:

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:

Reason code
Explanation
002
There is no active ESM.
003
The ESM is not responding.
010
The terminal type is invalid for this operation.
017
The terminal has preset security.
019
Security is not active for this CICS.
022
The terminal is a surrogate terminal.
028
The ESM returned a response which was not recognized by the CICS security domain.
038
The signon program went into recovery following an ABEND.
048
The signon program detected a loop and went into recovery.
052
The signon program received a bad response from transaction manager.
End of change
Start of change
System action:

An AP exception trace with point ID FB9D is issued.

End of change
Start of change
User response:

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.

End of change
Start of change
Destination:

CSNE

End of change
Modules:

Start of changeDFHZSGNEnd of change

Start of changeXMEOUT Parameters:End of changeStart of change End of changeStart of changedate, End of changeStart of changetime,End of changeStart of changeapplid, End of changeStart of changetermid, End of changeStart of changetermid, End of changeStart of changerc1, End of changeStart of changerc2End of change

Start of change
DFHZC0170I
applid CICS registered successfully to VTAM generic resource name grname.
Explanation:

CICS has registered as a VTAM generic resource in the group grname.

System action:

CICS continues. It is now possible to log on using the generic resource name.

User response:

None.

Destination:

Console

Modules:

DFHZGSL

XMEOUT Parameters: applid, grname

End of change
Start of change
DFHZC0171
applid CICS registration as a VTAM generic resource in the group grname failed. VTAM return code: X'rc'. FDB2: X'fd'.
Explanation:

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.

System action:

An AP exception trace entry is output with trace point FB8E.

CICS continues without generic resource support.

User response:

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.

Destination:

Console

Modules:

DFHZGSL

XMEOUT Parameters: applid, grname,X'rc', X'fd'

End of change
Start of change
DFHZC0172I
applid CICS deregistered successfully from VTAM generic resource name grname.
Explanation:

CICS has deregistered from VTAM generic resource group grname.

System action:

None. CICS will not reregister to the generic resource until the VTAM ACB has been closed and opened again.

User response:

None.

Destination:

Console

Modules:

DFHZGSL

XMEOUT Parameters: applid, grname

End of change
Start of change
DFHZC0173
applid CICS deregistration from VTAM generic resource name grname failed. VTAM return code: X'rc'. FDB2: X'fd'.
Explanation:

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.

System action:

An AP exception trace entry is output with a trace point of X'FB8E'.

User response:

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.

Destination:

Console

Modules:

DFHZGLS

XMEOUT Parameters: applid, grname,X'rc', X'fd'

End of change
Start of change
DFHZC0174
applid Control block initialization has failed. Generic resource registration or deregistration will not be attempted. Return codes r15,r0.
Explanation:

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.

System action:

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.

User response:

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.

Destination:

Console

Modules:

DFHZGLS

XMEOUT Parameters: applid, r15,r0

End of change
Start of change
DFHZC0175
applid A value was specified for GRNAME but the assemble time or run time VTAM does not support generic resource registration.
Explanation:

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.

System action:

CICS sets the generic resource name to blanks and continues without attempting generic resource registration.

User response:

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.

Destination:

Console

Modules:

DFHZSLS

XMEOUT Parameter: applid

End of change
Start of change
DFHZC0176
date time applid VTAM was unable to execute a CHANGE OPTCD=ENDAFFIN macro to end an affinity between this application, which is a member of generic resource grname, and a remote LU with netid netid netname netname. VTAM return code: X'rc', FDB2: X'fd', R15: X'r15'.
Explanation:

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.

System action:

Processing continues. VTAM has made no attempt to end the affinity.

User response:

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.

Destination:

CSNE

Modules:

DFHZGCH

XMEOUT Parameters: date, time,applid, grname, netid, netname, X'rc', X'fd', X'r15'

End of change
Start of change
DFHZC0177
date time applid Connection sysid has created an affinity between this application, which is a member of generic resource grname, and a remote LU with netid netid netname netname.
Explanation:

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.

System action:

Processing continues.

User response:

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.

Destination:

CSNE

Modules:

DFHZNAC

XMEOUT Parameters: date, time,applid, sysid, grname, netid, netname

End of change
Start of change
DFHZC0178
date time applid An attempt to end an affinity between this application, which is a member of generic resource grname, and a remote LU with netid netid netname netname was rejected by VTAM. VTAM return code: X'rc'. FDB2: X'fd'.
Explanation:

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.

System action:

Processing continues.

User response:

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.

Destination:

CSNE

Modules:

DFHZGCH

XMEOUT Parameters: date, time,applid, grname, netid, netname, X'rc', X'fd'

End of change
Start of change
DFHZC0179 I
date time applid Connection sysid netname netname is a link to generic resource grname member membername.
Explanation:

A connection sysid from netname netname to generic resource grname has been established.

The message is issued once for each connection acquire.

System action:

Processing continues.

User response:

None.

Destination:

CSNE

Modules:

DFHZNAC

XMEOUT Parameters: date, time,applid, sysid, netname, grname, membername

End of change
Start of change
DFHZC0180
date time applid An affinity between this application, which is a member of generic resource grname, and a remote LU with netid netid netname netname has ended successfully.
Explanation:

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.

System action:

Processing continues. The remote LU can now establish a connection with a different generic resource member.

User response:

None.

Destination:

CSNE

Modules:

DFHZGCH

XMEOUT Parameters: date, time,applid, grname, netid, netname

End of change
Start of change
DFHZC0181
date time applid No affinity exists between this application, which is a member of generic resource grname, and a remote LU with netid netid netname netname. VTAM return code: X'14', FDB2: X'88'.
Explanation:

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.

System action:

Processing continues.

User response:

Ensure that the values input to the SET CONNECTION ENDAFFINITY or PERFORM ENDAFFINITY command are correct.

Destination:

CSNE

Modules:

DFHZGCH

XMEOUT Parameters: date, time,applid, grname, netid, netname

End of change
Start of change
DFHZC0182
date time applid VTAM was unable to execute an INQUIRE OPTCD=NQN macro to determine the network qualified netname of logical unit luname. VTAM return code: X'rc', FDB2: X'fd', R15: X'r15'.
Explanation:

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.

System action:

The CICS component which requires the network qualified netname of the logical unit determines whether any further action is called for.

User response:

See the VTAM Programming manual for the meaning of the RTNCD,FDB2 and for guidance on correcting the problem.

Destination:

CSNE

Modules:

DFHZGIN

XMEOUT Parameters: date, time,applid, luname, X'rc', X'fd', X'r15'

End of change
Start of change
DFHZC0183
date time applid An attempt to determine the network qualified name of logical unit luname was rejected by VTAM. VTAM return code: X'rc'. FDB2: X'fd'.
Explanation:

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.

System action:

The CICS component which requires the network qualified name of the logical unit decides whether further action is called for.

User response:

See the VTAM Programming manual for the meaning of the RTNCD,FDB2 code and for guidance on correcting the problem.

Destination:

CSNE

Modules:

DFHZGIN

XMEOUT Parameters: date, time,applid, luname, X'rc', X'fd'

End of change
Start of change
DFHZC0184
date time applid VTAM was unable to execute an INQUIRE OPTCD=SESSNAME macro to determine the member of generic resource set grname to which logical unit netid.luname is logged on. VTAM return code: X'rc', FDB2: X'fd', R15: X'r15'.
Explanation:

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.

System action:

The CICS component which needs to know where the logical unit is logged on determines whether any further action is called for.

User response:

See the VTAM Programming manual for the meaning of the RTNCD,FDB2 and for guidance on correcting the problem.

Destination:

CSNE

Modules:

DFHZGIN

XMEOUT Parameters: date, time,applid, grname, netid, luname, X'rc', X'fd', X'r15'

End of change
Start of change
DFHZC0185
date time applid An attempt to determine the member of generic resource set grname to which logical unit netid.luname is logged on was rejected by VTAM. VTAM return code: X'rc'. FDB2: X'fd'.
Explanation:

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.

System action:

The CICS component which requires the member name decides whether further action is called for.

User response:

See the VTAM Programming manual for the meaning of the RTNCD,FDB2 code and for guidance on correcting the problem.

Destination:

CSNE

Modules:

DFHZGIN

XMEOUT Parameters: date, time,applid, grname, netid, luname, X'rc', X'fd'

End of changeStart of change
DFHZC0186
date time applid Connection sysid which is a member of generic resource grname has a duplicate remote LU netname netname. sense ((instance) Module name: {DFHZOPN})
Explanation:

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:

1
During the acquire process for a secondary session CICS attempted to add the membername of the partner to a table but this name already exists for a different generic resource connection.
2
During the acquire process for a secondary session CICS attempted to add the membername of the partner to a table but this name has just been used as the netname of a terminal by an install occurring at the same time as the install of this connection.
System action:

The acquire of the connection continues.

User response:

Use the instance number to determine why the netname already exists:

1
Use the CEMT INQUIRE CONNECTION API to see which generic resource has the same membername.

Since this problem should not occur under normal circumstances, you may need further assistance from IBM.

2
Investigate why the LU name of the partner is the same as the LU name of a terminal and remove one of the definitions.
Destination:

CSNE

Modules:

DFHZOPN, DFHZOPN

XMEOUT Parameters: date, time,applid, sysid, grname, netname, sense, instance, {1=DFHZOPN, 2=DFHZOPN}

End of change
Start of changeDFHZC0187End of change
Start of changedate time applid Reset of connection sysid failed following the ending of an affinity between this a pplication and a remote LU with generic resource name grname member name applid. The connection was locked by task taskid, transaction tranid.End of change
Start of change
Explanation:

CICS has failed to reset connection sysid after an affinity was ended successfully. A lock was held by task taskid, transaction tranid.

End of change
Start of change
System action:

Processing continues but the state of the connection is undetermined. The lock on the connection should be released when task taskid ends.

End of change
Start of change
User response:

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.

End of change
Start of change
Destination:

CSNE

End of change
Modules:

Start of changeDFHZGCHEnd of change

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

DFHZC0199
CICS has recovered after a system failure. Execute recovery procedures. { Already signed on. | Please sign on.}
Explanation:

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.

System action:

Processing continues.

User response:

Sign on if required, and take any recovery actions required.

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

Terminal End User

Modules:

DFHZNAC

DFHZC0200
applid An attempt by the COVR transaction to OPEN VTAM has failed with return code X'retcode'; CICS will retry.
Explanation:

The COVR transaction has attempted an EXEC CICS SET VTAM OPEN, but the operation failed with the return code retcode from the OPEN ACB.

System action:

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.

User response:

Investigate the reason for VTAM being unavailable. See the VTAM Programming manual for an explanation of the ACB return code.

Destination:

Console

Modules:

DFHZCOVR

XMEOUT Parameters: applid, X'retcode'

DFHZC0201
applid An attempt by the COVR transaction to OPEN VTAM has failed with return code X'retcode'; the COVR transaction will terminate.
Explanation:

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.

System action:

CICS continues. The COVR transaction terminates and the SET VTAM OPEN is not retried.

User response:

Investigate the reason for VTAM being unavailable. See the VTAM Programming manual for an explanation of the ACB return code.

Destination:

Console

Modules:

DFHZCOVR

XMEOUT Parameters: applid, X'retcode'

DFHZC2109 E
date time applid Unexpected response from Recovery Manager following resynchronization of LU6.1 session termid with remote system sysid.
Explanation:

Recovery manager was invoked during resynchronization of an LU6.1 session, but gave an unexpected response. This is due to an internal logic error.

System action:

A system dump is taken unless dumps have been specifically suppressed in the dump table.

User response:

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

Destination:

CSNE

Modules:

DFHZNAC

XMEOUT Parameters: date, time,applid, termid, sysid

DFHZC2114 E
date time applid termid tranid A SEND response failed during receive-any processing. sense ((instance) Module name: {DFHZRAC})
Explanation:

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.

System action:

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.

User response:

A subsequent message in the log indicates the reasons for the failure. Refer to this message for further information and guidance.

Destination:

CSNE

Modules:

DFHZRAC

XMEOUT Parameters: date, time,applid, termid, tranid, sense, instance, {1=DFHZRAC, 2=DFHZRAC}

DFHZC2115
applid termid Potential CICS hang detected following a SEND to node netname, CID X'cid'. Investigation is required. ((instance) Module name: {DFHZRAC})
Explanation:

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.

System action:

CICS continues to monitor for the SEND operation to complete. Until this happens, CICS reissues this message at approximately three minute intervals.

User response:

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.

Destination:

Console

Modules:

DFHZRAC

XMEOUT Parameters: applid, termid,netname, X'cid', instance, {1=DFHZRAC}

DFHZC2116 E
date time applid Resynchronization of LU6.1 session termid with remote system sysid failed.
Explanation:

Resynchronization of an LU6.1 session with a remote system has failed to complete for one of the following reasons:

  1. There is an apparent inconsistency between the sequence numbers in the two systems
  2. There was a protocol error during the exchange of the sequence numbers
  3. Neither system requested resynchronization, but there was a shunted unit of work associated with the session.
System action:

  1. A system dump is taken unless dumps have been specifically suppressed in the dump table.
  2. The TCTTE for the session on which the error occurred is printed. The local system’s sequence numbers, and the numbers or responses received from the remote system can be found in the TCTTE.
  3. The failure of resynchronization is reported to recovery manager. Recovery manager issues diagnostics relating to any unit of work affected by the failure.
User response:

  1. Determine whether changes to data in the local and remote system are synchronized. Diagnostics issued by recovery manager will help you to do this. If necessary, take action to resynchronize the data.
  2. Determine why the resynchronization failure happened. You will normally need assistance from IBM to do this. See CICS Problem Determination Guide for guidance on how to proceed.
Destination:

CSNE

Modules:

DFHZRSY, DFHZSCX, DFHZSEX

XMEOUT Parameters: date, time,applid, termid, sysid

Start of changeDFHZC2117 EEnd of change
Start of changedate time applid termid tranid Data received on pipeline session exceeds RAIA size. ((instance) Module name: {DFHZRAC})End of change
Start of change
Explanation:

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.

End of change
Start of change
System action:

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.

End of change
Start of change
User response:

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.

End of change
Start of change
Destination:

CSNE

End of change
Modules:

Start of changeDFHZRACEnd of change

Start of changeXMEOUT Parameters:End of changeStart of change End of changeStart of changedate, End of changeStart of changetime,End of changeStart of changeapplid, End of changeStart of changetermid, End of changeStart of changetranid, End of changeStart of changeinstance, End of changeStart of change{1=DFHZRAC}End of change

DFHZC2118
applid Receive Any stall for netname netname.
Explanation:

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.

System action:

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.

User response:

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.

Destination:

Console

Modules:

DFHZRAC

XMEOUT Parameters: applid, netname

DFHZC2119 E
date time applid termid tranid LUSTAT received on pipeline session incorrectly requests a definite response. ((instance) Module name: {DFHZRAC})
Explanation:

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.

System action:

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.

User response:

Determine why the pool pipeline terminal is violating the protocol.

Destination:

CSNE

Modules:

DFHZRAC

XMEOUT Parameters: date, time,applid, termid, tranid, instance, {1=DFHZRAC}

Start of changeDFHZC2300End of change
Start of changeapplid Recovery action requested for connection sysid.End of change
Explanation:

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

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

System action:

CICS cancels all transactions which have outstanding queued requests to use the connection.

User response:

Investigate the cause of the poor performance of the connection. Check the availability and condition of the connected system.

Destination:

Console

Modules:

DFHZISP

XMEOUT Parameters: applid, sysid

DFHZC2301I
applid Connection sysid operating normally following recovery action.
Explanation:

Message DFHZC2300 has been issued for this connection. The connection has now recovered and is operating normally.

System action:

Processing continues.

User response:

None

Destination:

Console

Modules:

DFHZISP

XMEOUT Parameters: applid, sysid

DFHZC2302
applid SETLOGON start command rejected
Explanation:

CICS issues the SETLOGON START command after a successful OPEN VTAM ACB. The SETLOGON START command is rejected in the following cases:

System action:

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.

User response:

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.

Destination:

Console

Modules:

DFHZSLS

XMEOUT Parameter: applid

DFHZC2303
applid No storage available when initiating RECEIVE-ANY's. Code: X'code'
Explanation:

While trying to acquire receive-any I/O areas, the SETLOGON START VTAM command found that storage was not available.

System action:

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.

User response:

Reduce the size of the RAMAX value in the system initialization table (SIT).

For further information, see the CICS Performance Guide.

Destination:

Console

Modules:

DFHZGRP

XMEOUT Parameters: applid, X'code'

DFHZC2304
applid RECEIVE-ANY command rejected. Code: X'code'
Explanation:

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.

System action:

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.

User response:

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.

Destination:

Console

Modules:

DFHZGRP

XMEOUT Parameters: applid, X'code'

DFHZC2305I
applid Termination of VTAM sessions beginning
Explanation:

Either CICS or VTAM is being terminated, or a dynamic close of the VTAM ACB has been requested.

System action:

All CICS-VTAM sessions are closed and the ACB is closed. If termination is not orderly, active transactions are abnormally terminated.

User response:

When VTAM is active, communication may be resumed by using the master terminal operator command CEMT SET VTAM OPEN.

Destination:

Console

Modules:

DFHZSHU

XMEOUT Parameter: applid

DFHZC2307
applid CICS VTAM ABNORMALLY QUIESCING (modname).
Explanation:

An RPL request has completed without a TCTTE token, for other than a VTAM storage shortage.

System action:

CICS performs a FORCECLOSE of the ACB.

CICS may produce this message twice as both module DFHZRAC and module DFHZSYX may detect the condition.

User response:

When VTAM has been restarted, issue a CEMT SET VTAM OPEN.

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

Console

Modules:

DFHZRAC, DFHZSYX

DFHZC2308
applid TCP Task WAIT failed. Unexpected response from DSSR WAIT_OLDW call (RESPONSE X'xx', REASON X'yy').
Explanation:

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.

System action:

CICS abends with abend U1800 and a system dump is produced.

User response:

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.

Destination:

Console

Modules:

DFHZDSP

XMEOUT Parameters: applid, X'xx',X'yy'

DFHZC2309
applid Recovery action requested for connection sysid using mode group modename.
Explanation:

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.

System action:

CICS cancels all transactions which have outstanding queued requests to use this mode group.

User response:

Investigate the cause of the poor performance of the mode group. Check the availability and condition of the connected system.

Destination:

Console

Modules:

DFHZISP

XMEOUT Parameters: applid, sysid,modename

DFHZC2310I
applid Connection sysid using mode group modename operating normally following recovery action.
Explanation:

Message DFHZC2309 has been issued for this mode group. The mode group has now recovered and is operating normally.

System action:

Processing continues.

User response:

None

Destination:

Console

Modules:

DFHZISP

XMEOUT Parameters: applid, sysid,modename

DFHZC2312
*** WELCOME TO CICS ***
Explanation:

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.

System action:

Processing continues.

User response:

None.

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

Terminal End User

Modules:

DFHSIT

DFHZC2316
applid VTAM ACB is closed
Explanation:

CICS and VTAM have been disconnected. This may be because:

System action:

The VTAM ACB is closed.

User response:

If VTAM has not terminated, connection with VTAM can be reestablished by using master terminal operator commands.

Destination:

Console

Modules:

DFHZSHU

XMEOUT Parameter: applid

DFHZC2318
applid The autoinstall user program progname is not enabled. Module modname.
Explanation:

While opening the VTAM ACB, CICS found that no installed program definition exists for the autoinstall user-program progname specified in the SIT.

System action:

Other processing continues.

User response:

If you want to use autoinstall, produce an installed program definition for the autoinstall user-program progname specified in the SIT.

Destination:

Console

Modules:

DFHSIJ1, DFHZOPA

XMEOUT Parameters: applid, progname, modname

DFHZC2319
applid Unable to close VTAM ACB RC=xx error code=yy
Explanation:

The VTAM ACB CLOSE request failed.

System action:

CICS continues as if the ACB is closed. (It is not really closed.)

User response:

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

Destination:

Console

Modules:

DFHZSHU

XMEOUT Parameters: applid, xx,yy

DFHZC2320
CORRUPTED TCTTE ADDRESS FOUND DURING SHUTDOWN.
Explanation:

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.

System action:

CICS is abnormally terminated with a system dump.

User response:

Investigate the dump to determine the cause of the problem.

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

Console

Modules:

DFHZSHU

DFHZC2350A
date time applid CICS Terminal Control shutdown threshold (mm minutes) exceeded. Sessions still active: sesslist ((instance) Module name: {DFHZSHU})
Explanation:

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.

System action:

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.

User response:

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.

Destination:

Console and Transient Data Queue CSNE

Modules:

DFHZSHU

XMEOUT Parameters: date, time,applid, mm, sesslist, instance, {1=DFHZSHU}

DFHZC2351
date time applid termid netname Session still active after TC shutdown threshold expired. Reason: {01 Request in progress | 02 Task still active |03 Waiting for SHUTC | 04 Waiting for BIS |05 Waiting for UNBIND | 06 Waiting for RTR |07 BID in progress | 08 Other TC work pending | 99 Undetermined} sense ((instance) Module name: {DFHZSHU})
Explanation:

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:

01
Request in progress
02
Task still active
03
Waiting for SHUTC
04
Waiting for BIS
05
Waiting for UNBIND
06
Waiting for RTR
07
BID in progress
08
Other TC work pending
99
Undetermined
System action:

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.

Note:
CLSDST is not guaranteed to work in all circumstances.

The first 10 terminals (if there are that many) reported by this message are also included in message DFHZC2350.

User response:

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.

Destination:

CSNE

Modules:

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}

DFHZC2352
date time applid sysid netname Intersystem parallel connection still active after TC shutdown threshold expired. ((instance) Module {DFHZSHU})).
Explanation:

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.

System action:

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

User response:

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

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.

Destination:

Console and Transient Data Queue CSNE

Modules:

DFHZSHU

XMEOUT Parameters: date, time,applid, sysid, netname, instance, {1=DFHZSHU}

DFHZC2400 E
date time applid termid tranid Error not supported. sense ((instance) Module name: {DFHZSYX})
Explanation:

CICS received an unexpected error code from VTAM.

For the meaning of the sense data, see DFHZCxxxx messages.

System action:

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.

User response:

Use the symptom string, and if necessary the transaction dump, to determine the source of the error.

Destination:

CSNE

Modules:

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}

DFHZC2401 E
date time applid termid tranid RPL Active. sense ((instance) Module name: {DFHZRVL | DFHZRVS | DFHZSDA | DFHZSDL | DFHZSDR | DFHZSDS | DFHZSES | DFHZSKR})
Explanation:

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.

System action:

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.

User response:

Use the symptom string, and if necessary, the transaction dump to determine the source of the error.

Destination:

CSNE

Modules:

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}

DFHZC2402 I
date time applid termid tranid netname VTAM has returned error on synchronous receive. sense ((instance) Module name: {DFHZRAS})
Explanation:

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.

System action:

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.

User response:

Determine from the RPL in the exception trace why VTAM raised the error.

Destination:

CSNE

Modules:

DFHZRAS

XMEOUT Parameters: date, time,applid, termid, tranid, netname, sense, instance, {1=DFHZRAS}

DFHZC2403 E
date time applid termid tranid Bind failure. sense ((instance) Module name: {DFHZSYX})
Explanation:

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.

System action:

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.

User response:

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:

  1. Bring up TOR1, acquire the connection and release it or
  2. bring up TOR1 and use ENDAFFIN via CEMT or EXEC CICS or
  3. use a batch program described in 'Writing a batch program to end affinities' in the CICS Intercommunication Guide.

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.

Destination:

CSNE

Modules:

DFHZSYX

XMEOUT Parameters: date, time,applid, termid, tranid, sense, instance, {1=DFHZSYX, 2=DFHZSYX}

DFHZC2404 E
date time applid termid tranid VTAM Detected Logic Error. sense ((instance) Module name: {DFHZLEX})
Explanation:

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.

System action:

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.

User response:

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.

Destination:

CSNE

Modules:

DFHZLEX

XMEOUT Parameters: date, time,applid, termid, tranid, sense, instance, {1=DFHZLEX, 2=DFHZLEX, 3=DFHZLEX, 4=DFHZLEX, 5=DFHZLEX, 6=DFHZLEX}

DFHZC2405 E
date time applid termid tranid Node netname not activated. sense ((instance) Module name: {DFHZSIM | DFHZSIX | DFHZSYX})
Explanation:

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.

System action:

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.

User response:

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:

  1. Bring up TOR1, acquire the connection and release it cleanly or
  2. Bring up TOR1 and use ENDAFFIN via CEMT or EXEC CICS or
  3. Use a batch program described in 'Writing a batch program to end affinities' in the CICS Intercommunication Guide.

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.

Destination:

CSNE

Modules:

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}

DFHZC2406 E
date time applid termid tranid Terminate self command received. sense ((instance) Module name: {DFHZSYX})
Explanation:

The logical unit (LU) has requested termination of the session.

For the meaning of the sense data, see DFHZCxxxx messages.

System action:

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.

User response:

None.

Destination:

CSNE

Modules:

DFHZSYX

XMEOUT Parameters: date, time,applid, termid, tranid, sense, instance, {1=DFHZSYX}

DFHZC2407 E
date time applid termid tranid Permanent channel failure. sense ((instance) Module name: {DFHZSYX})
Explanation:

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.

System action:

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.

User response:

Use the supplied dump to check for a possible NCP/VS or channel problem.

Destination:

CSNE

Modules:

DFHZSYX

XMEOUT Parameters: date, time,applid, termid, tranid, sense, instance, {1=DFHZSYX, 2=DFHZSYX}

DFHZC2408 E
date time applid termid tranid Apparent VTAM Error. sense ((instance) Module name: {DFHZSYX})
Explanation:

VTAM encountered an error during its own processing.

For the meaning of the sense data, see DFHZCxxxx messages.

System action:

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.

User response:

Use the sense data to determine the nature of the error.

Destination:

CSNE

Modules:

DFHZSYX

XMEOUT Parameters: date, time,applid, termid, tranid, sense, instance, {1=DFHZSYX, 2=DFHZSYX, 3=DFHZSYX, 4=DFHZSYX}

DFHZC2409 I
date time applid termid tranid VTAM Recovered Node. LOSTERM Error Code X'xx'. sense ((instance) Module name: {DFHZLTX})
Explanation:

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:

Value
Meaning
0
Dial-disconnect on dial-in.
4
Dial-disconnect on dial-out.
0C
Deactivate immediate.
14
Unconditional terminate self.
1C
Segmenting error.
20
Conditional terminate self.
24
BUFLIM value exceeded.

For the meaning of the sense data, see DFHZCxxxx messages.

System action:

CICS reestablishes communication and places the node in service.

User response:

None.

Destination:

CSNE

Modules:

DFHZLTX

XMEOUT Parameters: date, time,applid, termid, tranid, X'xx', sense, instance, {1=DFHZLTX, 2=DFHZLTX}

DFHZC2410 E
date time applid termid tranid Node Unrecoverable. VTAM LOSTERM Error Code X'xx'. sense ((instance) Module name: {DFHZLTX})
Explanation:

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.

System action:

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.

User response:

See the appropriate VTAM Programming manual for an explanation of the error code.

Destination:

CSNE

Modules:

DFHZLTX

XMEOUT Parameters: date, time,applid, termid, tranid, X'xx', sense, instance, {1=DFHZLTX, 2=DFHZLTX, 3=DFHZLTX, 4=DFHZLTX}

DFHZC2411 E
date time applid termid tranid nodeid attempted invalid logon. sense ((instance) Module name: {DFHTFP | DFHZATA | DFHZBLX | DFHZLGX | DFHZSCX | RESERVE})
Explanation:

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:

1
For LU6.1 no suitable TCTTE can be found, or no session TCTTE exists This could occur for one of the following reasons:
  1. The bind did not contain a modename.
  2. There is an RDO definition for a member name connection in a generic resource communicating with another generic resource over an LU6.1 link.
2
No PLUNAME has been found in the LU6.2 bind processed by CICS.
3
An attempt to autoinstall a member name connection in a generic resource system has failed because the bind was not for a SNA service manager.
4
Autoinstall is not allowed because the system is terminating.
5
Autoinstall is not allowed because the VTAM ACB is closing.
6
Start of changeISC support is not present because ISC=NO specified in the SIT.End of change
7
Used by DFHZATA for several reasons, for example BIND bad and user exit bad.
8
The TCTTE address restored and the address found by NIBSEARCH do not agree.
9
The system is terminating.
10
VTAM is terminating.
11
RESERVED.
12
RESERVED.
13
No address is present in the RPL.
14
LU6.1 cannot autoinstall.

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.

15
ISC support is not present.
16
A CINIT arrived for an APPC parallel session. This is not supported All input for an APPC parallel session should be via a BIND. Also, no connection exists with this NETNAME.
17
Session is not bound.
18
Not used.
19
LU is not enabled. Typically it is an XRF alternate CICS.
20
A second CINIT with the same netname has arrived.
21
Logon rejected due to CATA abend.
22
A CINIT initiated by SIMLOGON occurred for an APPC paralled session. A matching connection exists, but it is being deleted. This should not occur because either the delete should have been cancelled (if it had been scheduled but not started) or the SIMLOGON should have been queued until the delete was attempted and fails because there is SIMLOGON activity.
23
A BIND was received for an LU6.1 connection. This CICS is registered as a generic resource but the partner addressed CICS by its MEMBER name instead of its generic resource name.

Change the partner’s connection definition for this system to use a NETNAME of this system’s generic resource name.

24
Not used.
25
A CINIT was received for an LU6.1 connection. This CICS is registered as a generic resource but the partner addressed CICS by its MEMBER name instead of its generic resource name.

Change the partner’s connection definition for this system to use a NETNAME of this system’s generic resource name.

26
A BIND was received for an LU6.1 connection. This CICS is registered as the same generic resource as the partner. However, the partner addressed CICS by the generic resource name instead of the member name which it should use for intra-plex communication.

Change the partner’s connection definition for this system to use a NETNAME of this system’s member name.

27
A CINIT was received for an LU6.1 connection. This CICS is registered as the same generic resource as the partner. However, the partner addressed CICS by the generic resource name rather than the member name which it should use for intra-plex communication.

Change the partner’s connection definition for this system to use a NETNAME of this system’s member name.

28
Start of changeAn LU62 bind was received for the netname specified. CICS has found a connection with the relevant netname but the connection was not defined as APPC.End of change
29
A system entry for the connection indicated by the bind has been found but none of its sessions are usable.
30
No modename field UDSS02 was found in the bind.
31
Examination of the session tctte has indicated it to be out of service, a non-SNA service manager session and to have the associated connection released.
32
An attempt to autoinstall a GR name or XRF connection has failed because the bind was not for a SNA service manager.
33
This bind is a SNA service manager request for an existing partner.
34
There is a problem with the user data supplied in the bind. Specifically one of the following.
  • There is no user data.
  • The user data supplied is too short.
  • The user data is not architected.
35
A delete is pending for the connection found. This delete is for a non-transient terminal definition and has been requested explicitly.
36
For a non-generic resource request, examination of the bind has indicated that it is not for a SNA service manager.

This instance also indicates that you should not acquire this connection Start of changeif 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.End of change

37
The current session count has exceeded the maximum session count indicated in the mode group entry.

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

38
An attempt to acquire a generic resource connection failed because there is a member name connection defined for the generic resource member to which VTAM has chosen to route it.
Start of change39End of change
Start of changeThis CICS has deregistered from a generic resource but a remote partner is attempting to bind an APPC session using a generic resource name. This indicates that VTAM affinities have not been ended on both sides.End of change
Start of change40End of change
Start of changeThis CICS has deregistered from a generic resource but a remote partner is attempting to bind an LU6.1 session using a generic resource name. This indicates that VTAM affinities have not been ended on both sides.End of change
Start of change41End of change
Start of changeA bind has been received for an APPC SNA Service Manager session while the connection is in the process of being released. As the maximum number of SNASVCMG sessions has already been set to zero, acceptance of this bind would leave the connection in a Freeing state and is therefore rejected. Retry the Acquire of the connection when all the user sessions have been CLSDST and the connection is released.End of change

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.

System action:

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.

User response:

Use the instance number to determine why the attempted logon has been rejected and take the appropriate action.

Destination:

CSNE

Modules:

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,Start of change41=DFHZBLX}End of change

DFHZC2412 E
date time applid termid tranid Receive any request failed. sense ((instance) Module name: {DFHZRAC})
Explanation:

A receive-any request to VTAM failed. VTAM was terminated.

For the meaning of the sense data, see DFHZCxxxx messages.

System action:

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.

User response:

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.

Destination:

CSNE

Modules:

DFHZRAC

XMEOUT Parameters: date, time,applid, termid, tranid, sense, instance, {1=DFHZRAC, 2=DFHZRAC}

DFHZC2413 E
date time applid termid tranid nodeid CLSDST failed. sense ((instance) Module name: {DFHTFP | DFHZATA | DFHZLGX})
Explanation:

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.

System action:

No further communication with the node is initiated.

User response:

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.

Destination:

CSNE

Modules:

DFHTFP, DFHZATA, DFHZLGX

XMEOUT Parameters: date, time,applid, termid, tranid, nodeid, sense, instance, {1=DFHZATA, 2=DFHZLGX, 3=DFHTFP}

DFHZC2414 E
date time applid termid tranid Temporary VTAM Storage Problem. sense ((instance) Module name: {DFHZSYX})
Explanation:

Temporary VTAM storage problem. VTAM is currently short of storage.

For the meaning of the sense data, see DFHZCxxxx messages.

System action:

The failing VTAM request is retried until VTAM is able to accept it.

User response:

Increase the VTAM working buffer storage if this condition recurs and causes undue problems.

Destination:

CSNE

Modules:

DFHZSYX

XMEOUT Parameters: date, time,applid, termid, tranid, sense, instance, {1=DFHZSYX}

DFHZC2415 E
date time applid termid tranid Node netname out of service. sense ((instance) Module name: {DFHZNAC})
Explanation:

A node error condition has occurred on node nodeid.

For the meaning of the sense data, see DFHZCxxxx messages.

System action:

CICS places the node out of service.

User response:

Use the sense data to determine the nature of the error.

Destination:

CSNE

Modules:

DFHZNAC

XMEOUT Parameters: date, time,applid, termid, tranid, netname, sense, instance, {1=DFHZNAC}

DFHZC2416 E
date time applid termid tranid VTAM is halting. sense ((instance) Module name: {DFHZSYX})
Explanation:

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:

1
Orderly shutdown
2
Quick shutdown.

For the meaning of the sense data, see DFHZCxxxx messages.

System action:

The VTAM network is quiesced to prevent further requests and the node is placed out of service.

User response:

None.

Destination:

CSNE

Modules:

DFHZSYX

XMEOUT Parameters: date, time,applid, termid, tranid, sense, instance, {1=DFHZSYX, 2=DFHZSYX}

DFHZC2417 E
date time applid termid tranid VTAM Inactive to TCB. sense ((instance) Module name: {DFHZCLS | DFHZCLX | DFHZOPN | DFHZOPX | DFHZRAC | DFHZRLP | DFHZRST | DFHZRVL | DFHZRVS | DFHZRVX | DFHZSDA | DFHZSDL | DFHZSDR | DFHZSDS | DFHZSES | DFHZSIM | DFHZSIX | DFHZSKR | DFHZSLX | DFHZSYX | DFHZTAX})
Explanation:

Either CICS has not opened its VTAM ACB or VTAM has halted.

For the meaning of the sense data, see DFHZCxxxx messages.

System action:

The VTAM network is quiesced to prevent further requests and a dump is produced.

User response:

If VTAM was not halted by the network operator, use the supplied dump to determine the problem.

Destination:

CSNE

Modules:

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}

DFHZC2418 E
date time applid termid tranid Unknown command in RPL. sense ((instance) Module name: {DFHZSEX})
Explanation:

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.

System action:

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.

User response:

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.

Destination:

CSNE

Modules:

DFHZSEX

XMEOUT Parameters: date, time,applid, termid, tranid, sense, instance, {1=DFHZSEX, 2=DFHZSEX}

DFHZC2419 E
date time applid termid tranid Unknown command in RPL. sense ((instance) Module name: {DFHZRAC | DFHZSLX | DFHZSSX})
Explanation:

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.

System action:

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.

User response:

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.

Destination:

CSNE

Modules:

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}

DFHZC2420 E
date time applid termid tranid Unknown command in RPL. sense ((instance) Module name: {DFHZSAX})
Explanation:

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.

System action:

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.

User response:

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.

Destination:

CSNE

Modules:

DFHZSAX

XMEOUT Parameters: date, time,applid, termid, tranid, sense, instance, {1=DFHZSAX}

DFHZC2421 E
date time applid termid tranid Unsupported command received. sense ((instance) Module name: {DFHZRAC | DFHZRLP | DFHZRVX})
Explanation:

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.

System action:

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.

User response:

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.

Destination:

CSNE

Modules:

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}

DFHZC2422 E
date time applid termid tranid ZCP Logic Error. sense ((instance) Module name: {DFHZARL | DFHZDET | DFHZERH | DFHZEV1 | DFHZEV2 | DFHZNAC | DFHZOPN | DFHZRAC | DFHZRVS | DFHZSDS | DFHZSIM | DFHZSKR | DFHZSLX | DFHZSSX})
Explanation:

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.

System action:

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.

User response:

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.

Destination:

CSNE

Modules:

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}

DFHZC2423 E
date time applid termid tranid Attempted to send unsupported command. sense ((instance) Module name: {DFHZSDS})
Explanation:

A request to send data synchronously was incomplete. Possible reasons are as follows:

  1. The TCTTE was altered.
  2. A logic error was encountered.
  3. The TCTTE was inadvertently placed on the send-synchronous queue.

For the meaning of the sense data, see DFHZCxxxx messages.

System action:

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.

User response:

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.

Destination:

CSNE

Modules:

DFHZSDS

XMEOUT Parameters: date, time,applid, termid, tranid, sense, instance, {1=DFHZSDS}

DFHZC2424 E
date time applid termid tranid SESSIONC command request invalid. sense ((instance) Module name: {DFHZSES | RESERVE})
Explanation:

A SESSIONC request is incomplete or invalid. Possible reasons are as follows:

  1. The TCTTE was altered.
  2. The command request bits are incomplete. DFHZSES checks TCTEISDT for a Start Data Traffic (SDT) command, TCTEISTS for a Set and Test Sequence Number (STSN) command, and TCTEICLR for a CLEAR command. If it does not find any of these, DFHZSES causes the message to be issued.
  3. The wrong request was queued to SESSIONC.

For the meaning of the sense data, see DFHZCxxxx messages.

System action:

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.

User response:

Ensure that application programs running concurrently do not alter the TCTTE.

If the TCTTE is not altered, check for conditions 2 or 3.

Destination:

CSNE

Modules:

DFHZSES

XMEOUT Parameters: date, time,applid, termid, tranid, sense, instance, {1=DFHZSES, 2=DFHZSES, 3=RESERVE}

DFHZC2425 E
date time applid termid tranid ASYNC command request invalid. sense ((instance) Module name: {DFHZSDA})
Explanation:

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.

System action:

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.

User response:

Check the TCTTE. Ensure that application programs running concurrently do not alter the TCTTE.

Destination:

CSNE

Modules:

DFHZSDA

XMEOUT Parameters: date, time,applid, termid, tranid, sense, instance, {1=DFHZSDA, 2=DFHZSDA}

DFHZC2426 E
date time applid termid tranid Node Status Error. Node is out of service or receive only. sense ((instance) Module name: {DFHZATT})
Explanation:

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.

System action:

All outstanding send and receive requests are purged. If a task is attached, it is abnormally terminated with a transaction dump.

User response:

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.

Destination:

CSNE

Modules:

DFHZATT

XMEOUT Parameters: date, time,applid, termid, tranid, sense, instance, {1=DFHZATT, 2=DFHZATT, 3=DFHZATT}

DFHZC2427 I
date time applid termid tranid NCP Restarted. sense ((instance) Module name: {DFHZSYX})
Explanation:

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.

System action:

The OPNDST request is reissued.

User response:

None.

Destination:

CSNE

Modules:

DFHZSYX

XMEOUT Parameters: date, time,applid, termid, tranid, sense, instance, {1=DFHZSYX}

DFHZC2428 E
date time applid termid tranid Send DFSYN request incomplete. sense ((instance) Module name: {DFHZSDS})
Explanation:

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.

System action:

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.

User response:

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.

Destination:

CSNE

Modules:

DFHZSDS

XMEOUT Parameters: date, time,applid, termid, tranid, sense, instance, {1=DFHZSDS}

DFHZC2429 E
date time applid termid tranid RESETSR request invalid RTYPE. sense ((instance) Module name: {DFHZRST})
Explanation:

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.

System action:

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.

User response:

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.

Destination:

CSNE

Modules:

DFHZRST

XMEOUT Parameters: date, time,applid, termid, tranid, sense, instance, {1=DFHZRST, 2=DFHZRST, 3=DFHZRST}

DFHZC2430 E
date time applid termid tranid Send response command request invalid. sense ((instance) Module name: {DFHZSDR})
Explanation:

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.

System action:

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.

User response:

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.

Destination:

CSNE

Modules:

DFHZSDR

XMEOUT Parameters: date, time,applid, termid, tranid, sense, instance, {1=DFHZSDR}

DFHZC2431 E
date time applid termid tranid Request to a released node. sense ((instance) Module name: {DFHZSYX})
Explanation:

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.

System action:

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

User response:

If the CICS ACB is open, use the dump to determine the source of the error. Check that the TCTTE is valid.

Destination:

CSNE

Modules:

DFHZSYX

XMEOUT Parameters: date, time,applid, termid, tranid, sense, instance, {1=DFHZSYX}

DFHZC2432 E
date time applid termid tranid Exception response received. sense ((instance) Module name: {DFHZRAC | DFHZRVX | DFHZSSX})
Explanation:

CICS has received an exception response.

For the meaning of the sense data, see DFHZCxxxx messages.

System action:

Another CICS message is issued in conjunction with this message.

User response:

Perform the action specified for the associated CICS message.

Destination:

CSNE

Modules:

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}

DFHZC2433 E
date time applid termid tranid nodeid Logon has failed because autoinstall is disabled. sense ((instance) Module name: {DFHZBLX | DFHZLGX})
Explanation:

Node nodeid attempted to log on to CICS. The logon has failed because autoinstall is disabled. Possible reasons are:

System action:

The logon is rejected.

User response:

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.

Destination:

CSNE

Modules:

DFHZLGX, DFHZSCX, DFHZBLX

XMEOUT Parameters: date, time,applid, termid, tranid, nodeid, sense, instance, {1=DFHZLGX, 2=DFHZLGX, 3=DFHZBLX, 4=DFHZBLX}

DFHZC2434 E
date time applid termid tranid Invalid copy request - Copy not supported. sense ((instance) Module name: {DFHZARQ})
Explanation:

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.

System action:

The task abends.

User response:

Change the application program to avoid issuing a COPY request.

Destination:

CSNE

Modules:

DFHZARQ

XMEOUT Parameters: date, time,applid, termid, tranid, sense, instance, {1=DFHZARQ}

DFHZC2435 E
date time applid termid tranid RPL missing. sense ((instance) Module name: {DFHZRVS})
Explanation:

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.

System action:

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.

User response:

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.

Destination:

CSNE

Modules:

DFHZRVS

XMEOUT Parameters: date, time,applid, termid, tranid, sense, instance, {1=DFHZRVS}

DFHZC2436 E
date time applid termid tranid TIOA missing. sense ((instance) Module name: {DFHZRVS | DFHZRVX})
Explanation:

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.

System action:

All outstanding receive requests are purged. If a task is attached, it is abnormally terminated with a transaction dump.

User response:

Use the dump to determine if the TCTTE was altered by an application program.

Destination:

CSNE

Modules:

DFHZRVS, DFHZRVX

XMEOUT Parameters: date, time,applid, termid, tranid, sense, instance, {1=DFHZRVS, 2=DFHZRVX, 3=DFHZRVS}

DFHZC2437 E
date time applid termid tranid Invalid WRITE request to an input only device. sense ((instance) Module name: {DFHZSDS})
Explanation:

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.

System action:

All outstanding send requests are purged. If a task is attached, it is abnormally terminated with a transaction dump. The terminal status remains unchanged.

User response:

Either ensure that the node is defined correctly in the TCTTE, or prevent the task from issuing an output request to the node.

Destination:

CSNE

Modules:

DFHZSDS

XMEOUT Parameters: date, time,applid, termid, tranid, sense, instance, {1=DFHZSDS}

DFHZC2438 E
date time applid termid tranid Invalid READ request to an output only device. sense ((instance) Module name: {DFHZRVS | DFHZSDS})
Explanation:

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.

System action:

All outstanding receive requests are purged. If a task is attached, it is abnormally terminated with a transaction dump. The terminal status remains unchanged.

User response:

Either change the definition of the terminal in the TCTTE, or prevent the task from issuing input requests to the node.

Destination:

CSNE

Modules:

DFHZRVS, DFHZSDS

XMEOUT Parameters: date, time,applid, termid, tranid, sense, instance, {1=DFHZRVS, 2=DFHZSDS}

DFHZC2439 E
date time applid termid tranid Invalid RESUME request. sense ((instance) Module name: {DFHZACT})
Explanation:

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.

System action:

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.

User response:

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.

Destination:

CSNE

Modules:

DFHZACT

XMEOUT Parameters: date, time,applid, termid, tranid, sense, instance, {1=DFHZACT}

DFHZC2440 I
date time applid termid tranid CICS quiesced by node. sense ((instance) Module name: {DFHZASX})
Explanation:

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.

System action:

All data transmission to the node is halted until CICS receives a release-quiesce indicator.

User response:

None.

Destination:

CSNE

Modules:

DFHZASX

XMEOUT Parameters: date, time,applid, termid, tranid, sense, instance, {1=DFHZASX}

DFHZC2441 I
date time applid termid tranid CICS released by node. sense ((instance) Module name: {DFHZASX})
Explanation:

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.

System action:

Data transmission to the node is resumed by CICS.

User response:

None.

Destination:

CSNE

Modules:

DFHZASX

XMEOUT Parameters: date, time,applid, termid, tranid, sense, instance, {1=DFHZASX}

DFHZC2442 E
date time applid termid tranid Exception response received to a definite response send. sense ((instance) Module name: {DFHZRVX})
Explanation:

An exception response was received when a definite response protocol was requested.

For the meaning of the sense data, see DFHZCxxxx messages.

System action:

CICS issues a second message in conjunction with this message that explains the reason for the exception response.

User response:

Perform the action specified for the second CICS message received.

Destination:

CSNE

Modules:

DFHZRVX

XMEOUT Parameters: date, time,applid, termid, tranid, sense, instance, {1=DFHZRVX, 2=DFHZRVX}

DFHZC2443 E
date time applid termid tranid Request outstanding when node released. sense ((instance) Module name: {DFHZRVL | DFHZRVS | DFHZSDL | DFHZSDS | DFHZSHU})
Explanation:

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.

System action:

All outstanding requests are ignored. If a task is attached, it is abnormally terminated with a transaction dump.

User response:

None.

Destination:

CSNE

Modules:

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}

DFHZC2444 E
date time applid termid tranid CICS bracket state error. sense ((instance) Module name: {DFHZRVS | DFHZSDS})
Explanation:

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.

System action:

All outstanding send and receive requests are purged. If a task is attached, it is abnormally terminated with a transaction dump.

User response:

Correct the application program.

Destination:

CSNE

Modules:

DFHZRVS, DFHZSDS

XMEOUT Parameters: date, time,applid, termid, tranid, sense, instance, {1=DFHZRVS, 2=DFHZSDS}

DFHZC2445 E
date time applid termid tranid Output area exceeded. sense ((instance) Module name: {DFHZSDS})
Explanation:

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.

System action:

All outstanding send requests are purged. If a task is attached, it is abnormally terminated with a transaction dump.

User response:

Correct the application program to acquire a larger TIOA.

Destination:

CSNE

Modules:

DFHZSDS

XMEOUT Parameters: date, time,applid, termid, tranid, sense, instance, {1=DFHZSDS, 2=DFHZSDS}

DFHZC2446 E
date time applid termid tranid Invalid response to a bid. sense ((instance) Module name: {DFHZRAC | DFHZRVX | DFHZSSX})
Explanation:

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.

System action:

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.

User response:

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.

Destination:

CSNE

Modules:

DFHZRAC, DFHZRVX, DFHZSSX

XMEOUT Parameters: date, time,applid, termid, tranid, sense, instance, {1=DFHZRVX, 2=DFHZSSX, 3=DFHZRAC}

DFHZC2447 E
date time applid termid tranid A severe error has occurred as a result of a previous failure. sense ((instance) Module name: {DFHZACT | DFHZFRE | DFHZGET | DFHZOPN | DFHZRAC | DFHZRLP | DFHZRVS | DFHZSDA})
Explanation:

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.

System action:

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.

User response:

Refer to the message issued by the domain that is in error. It indicates the source of the original error.

Destination:

CSNE

Modules:

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}

DFHZC2448 E
date time applid termid tranid Invalid response requested. sense ((instance) Module name: {DFHZRAC | DFHZRVX})
Explanation:

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.

System action:

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.

User response:

Correct the application program.

Destination:

CSNE

Modules:

DFHZRAC, DFHZRVX

XMEOUT Parameters: date, time,applid, termid, tranid, sense, instance, {1=DFHZRVX, 2=DFHZRAC, 3=DFHZRAC}

DFHZC2449 E
date time applid termid tranid Bracket Error. sense ((instance) Module name: {DFHZRAC | DFHZRVX})
Explanation:

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.

System action:

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.

User response:

Correct the application program.

Destination:

CSNE

Modules:

DFHZRAC, DFHZRVX

XMEOUT Parameters: date, time,applid, termid, tranid, sense, instance, {1=DFHZRVX, 2=DFHZRVX, 3=DFHZRAC, 4=DFHZRAC}

DFHZC2450 E
date time applid termid tranid Bid issued but ATI cancelled. sense ((instance) Module name: {DFHZRAC | DFHZRVX | DFHZSSX})
Explanation:

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.

System action:

CICS will satisfy the BB pending condition by sending a standalone BB-EB.

User response:

If ATI is time-initiated, increase the timer value.

Destination:

CSNE

Modules:

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}

DFHZC2451 E
date time applid termid tranid Outstanding request when clear was issued. sense ((instance) Module name: {DFHZSYX})
Explanation:

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.

System action:

All outstanding requests are purged. If a task is attached, it is abnormally terminated with a transaction dump.

User response:

None.

Destination:

CSNE

Modules:

DFHZSYX

XMEOUT Parameters: date, time,applid, termid, tranid, sense, instance, {1=DFHZSYX}

DFHZC2452 E
date time applid termid tranid Invalid command received. sense ((instance) Module name: {DFHZSCX})
Explanation:

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.

System action:

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.

User response:

Check the VTAM RPL for obvious errors. Use the dump to help determine the source of the problem.

Destination:

CSNE

Modules:

DFHZSCX

XMEOUT Parameters: date, time,applid, termid, tranid, sense, instance, {1=DFHZSCX}

DFHZC2453 E
date time applid termid tranid Request recovery received. sense ((instance) Module name: {DFHZSCX})
Explanation:

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.

System action:

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.

User response:

None.

Destination:

CSNE

Modules:

DFHZSCX

XMEOUT Parameters: date, time,applid, termid, tranid, sense, instance, {1=DFHZSCX}

DFHZC2454 E
date time applid termid tranid Exception in chain. sense ((instance) Module name: {DFHZSYX})
Explanation:

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.

System action:

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.

User response:

Use the symptom string, and if necessary the transaction dump, to determine the source of the error.

Destination:

CSNE

Modules:

DFHZSYX

XMEOUT Parameters: date, time,applid, termid, tranid, sense, instance, {1=DFHZSYX}

DFHZC2455 E
date time applid termid tranid In CA mode - Task attached. sense ((instance) Module name: {DFHZATT})
Explanation:

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.

System action:

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.

User response:

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.

Destination:

CSNE

Modules:

DFHZATT

XMEOUT Parameters: date, time,applid, termid, tranid, sense, instance, {1=DFHZATT}

DFHZC2456 E
date time applid termid tranid Exception response received to a command. sense ((instance) Module name: {DFHZRAC | DFHZSYX})
Explanation:

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.

System action:

In conjunction with this message, CICS issues a second message that explains the reason for the exception response.

User response:

Perform the action specified in the second CICS message received.

Destination:

CSNE

Modules:

DFHZSYX, DFHZSSX

XMEOUT Parameters: date, time,applid, termid, tranid, sense, instance, {1=DFHZSYX, 2=DFHZSYX, 3=DFHZSYX, 4=DFHZRAC}

DFHZC2457 E
date time applid termid tranid Multiple Errors Encountered. sense ((instance) Module name: {DFHZEMW | DFHZRAC | DFHZSYX})
Explanation:

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.

System action:

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.

User response:

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.

Destination:

CSNE

Modules:

DFHZRAC, DFHZSYX, DFHZEMW

XMEOUT Parameters: date, time,applid, termid, tranid, sense, instance, {1=DFHZEMW, 2=DFHZSYX, 3=DFHZSYX, 4=DFHZRAC, 5=DFHZRAC}

DFHZC2458 E
date time applid termid tranid Exception response received to an exception response send. sense ((instance) Module name: {DFHZRAC | DFHZRVX})
Explanation:

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.

System action:

In conjunction with this message, CICS issues a second message that explains the reason for the exception response.

User response:

Perform the action specified in the second CICS message received.

Destination:

CSNE

Modules:

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}

DFHZC2459 E
date time applid termid tranid No TIOA available for send. sense ((instance) Module name: {DFHZSDS})
Explanation:

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.

System action:

If a task is attached, it is abnormally terminated with a transaction dump. The send is purged.

User response:

Ensure that TCTTEDA is loaded with the TIOA address before issuing the write.

Destination:

CSNE

Modules:

DFHZSDS

XMEOUT Parameters: date, time,applid, termid, tranid, sense, instance, {1=DFHZSDS, 2=DFHZSDS}

DFHZC2460 E
date time applid termid tranid Sense receive not supported. sense ((instance) Module name: {DFHZNAC})
Explanation:

Sense codes not supported by CICS were received from the logical unit.

For the meaning of the sense data, see DFHZCxxxx messages.

System action:

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.

User response:

The user’s node error program (DFHZNEP) can process the sense codes.

Destination:

CSNE

Modules:

DFHZNAC

XMEOUT Parameters: date, time,applid, termid, tranid, sense, instance, {1=DFHZNAC}

DFHZC2461 E
date time applid termid tranid Intervention required. sense ((instance) Module name: {DFHZNAC})
Explanation:

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.

System action:

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.

User response:

Correct the problem with the device.

Destination:

CSNE

Modules:

DFHZNAC

XMEOUT Parameters: date, time,applid, termid, tranid, sense, instance, {1=DFHZNAC}

DFHZC2462 E
date time applid termid tranid Bracket Error. sense ((instance) Module name: {DFHZNAC})
Explanation:

The secondary logical unit and CICS both sent a begin-bracket indicator concurrently.

For the meaning of the sense data, see DFHZCxxxx messages.

System action:

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.

User response:

Correct the controller application program so that it cannot send a begin-bracket indicator.

Destination:

CSNE

Modules:

DFHZNAC

XMEOUT Parameters: date, time,applid, termid, tranid, sense, instance, {1=DFHZNAC}

DFHZC2463 E
date time applid termid tranid Node nodeid resource pending deletion, connection request rejected. sense ((instance) Module name: {DFHZBLX | DFHZLGX})
Explanation:

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.

System action:

CICS continues with the resource alteration, or for instance 3 of the message, the autoinstall delete transaction, CATD, is restarted.

User response:

When the resource alteration is complete, retry the connection or logon request.

Destination:

CSNE

Modules:

DFHZSCX, DFHZBLX, DFHZLGX

XMEOUT Parameters: date, time,applid, termid, tranid, nodeid, sense, instance, {1=DFHZBLX, 2=DFHZBLX, 3=DFHZLGX}

DFHZC2464 E
date time applid termid tranid Terminate chain. sense ((instance) Module name: {DFHZNAC})
Explanation:

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.

System action:

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.

User response:

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.

Destination:

CSNE

Modules:

DFHZNAC

XMEOUT Parameters: date, time,applid, termid, tranid, sense, instance, {1=DFHZNAC}

DFHZC2465 E
date time applid termid tranid Insufficient resources. sense ((instance) Module name: {DFHZNAC})
Explanation:

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.

System action:

The subsystem is temporarily suspended.

User response:

Determine why the controller application program encountered this condition. For the meaning of the sense data, refer to the explanatory paragraph in message DFHZC2461.

Destination:

CSNE

Modules:

DFHZNAC

XMEOUT Parameters: date, time,applid, termid, tranid, sense, instance, {1=DFHZNAC}

DFHZC2466 E
date time applid termid tranid Function not executable. sense ((instance) Module name: {DFHZNAC})
Explanation:

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.

System action:

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.

User response:

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.

Destination:

CSNE

Modules:

DFHZNAC

XMEOUT Parameters: date, time,applid, termid, tranid, sense, instance, {1=DFHZNAC}

DFHZC2467 E
date time applid termid tranid Invalid communications ID (CID) detected. sense ((instance) Module name: {DFHZLEX})
Explanation:

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.

System action:

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

User response:

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.

Destination:

CSNE

Modules:

DFHZLEX

XMEOUT Parameters: date, time,applid, termid, tranid, sense, instance, {1=DFHZLEX}

DFHZC2468 E
date time applid termid tranid Name netname unknown or vary activate required. sense ((instance) Module name: {DFHZLEX})
Explanation:

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.

System action:

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.

User response:

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.

Destination:

CSNE

Modules:

DFHZLEX

XMEOUT Parameters: date, time,applid, termid, tranid, netname, sense, instance, {1=DFHZLEX}

DFHZC2469 E
date time applid termid tranid Exception response received. sense ((instance) Module name: {DFHZSYX})
Explanation:

An exception response (negative response) was sent by the secondary logical unit.

For the meaning of the sense data, see DFHZCxxxx messages.

System action:

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.

User response:

Analyze the sense codes in DFHZNEP.

Destination:

CSNE

Modules:

DFHZSYX

XMEOUT Parameters: date, time,applid, termid, tranid, sense, instance, {1=DFHZSYX, 2=DFHZSYX}

DFHZC2470 E
date time applid termid tranid Task active at Shutdown. sense ((instance) Module name: {DFHZASX})
Explanation:

One of the following has occurred:

For the meaning of the sense data, see DFHZCxxxx messages.

System action:

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.

User response:

None.

Destination:

CSNE

Modules:

DFHZASX

XMEOUT Parameters: date, time,applid, termid, tranid, sense, instance, {1=DFHZASX}

DFHZC2471 E
date time applid termid tranid FMH length error. sense ((instance) Module name: {DFHZATT | DFHZRAC})
Explanation:

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.

System action:

All data received is purged. If a task is attached, it is abnormally terminated with a transaction dump.

User response:

Correct the application program in the logical unit.

Note:
The first 16 bytes of the I/O area in error are put to the CSNE log data set to aid in error determination.
Destination:

CSNE

Modules:

DFHZRAC, DFHZATT

XMEOUT Parameters: date, time,applid, termid, tranid, sense, instance, {1=DFHZATT, 2=DFHZATT, 3=DFHZATT, 4=DFHZATT, 5=DFHZATT, 6=DFHZRAC}

DFHZC2472 E
date time applid termid tranid Unable to retrieve overlength data. sense ((instance) Module name: {DFHZRAC})
Explanation:

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.

System action:

All associated data is purged.

User response:

A subsequent message follows in the log, indicating reasons for the request failing. Refer to this message for further information and guidance.

Destination:

CSNE

Modules:

DFHZRAC

XMEOUT Parameters: date, time,applid, termid, tranid, sense, instance, {1=DFHZRAC, 2=DFHZRAC}

DFHZC2473 E
date time applid termid tranid Outbound chaining not supported. sense ((instance) Module name: {DFHZSDS})
Explanation:

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.

System action:

All send requests are purged. If a task is attached, it is abnormally terminated with a transaction dump.

User response:

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.

Destination:

CSNE

Modules:

DFHZSDS

XMEOUT Parameters: date, time,applid, termid, tranid, sense, instance, {1=DFHZSDS, 2=DFHZSDS}

DFHZC2475 E
date time applid termid tranid Function cancelled by LU device. sense ((instance) Module name: {DFHZNAC})
Explanation:

The logical unit (LU) has terminated all processing connected with one of its components.

For the meaning of the sense data, see DFHZCxxxx messages.

System action:

All send and receive requests are purged. If a task is attached, it is abnormally terminated with a transaction dump.

User response:

Correct the problem with the LU component and bring it back online. Possible causes of the problem include the following:

Destination:

CSNE

Modules:

DFHZNAC

XMEOUT Parameters: date, time,applid, termid, tranid, sense, instance, {1=DFHZNAC}

DFHZC2476 E
date time applid termid tranid Resource unavailable. sense ((instance) Module name: {DFHZNAC})
Explanation:

A component of the logical unit (LU) is no longer available.

For the meaning of the sense data, see DFHZCxxxx messages.

System action:

All send and receive requests are purged. If a task is attached, it is abnormally terminated with a transaction dump.

User response:

Correct the problem with the LU component and bring it back online. Possible causes of the problem include the following.

Destination:

CSNE

Modules:

DFHZNAC

XMEOUT Parameters: date, time,applid, termid, tranid, sense, instance, {1=DFHZNAC}

DFHZC2477 E
date time applid termid tranid Chaining not supported. sense ((instance) Module name: {DFHZNAC})
Explanation:

The logical unit (LU) does not support chaining of data from the host.

For the meaning of the sense data, see DFHZCxxxx messages.

System action:

All send requests are purged. If a task is attached, it is abnormally terminated with a transaction dump.

User response:

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.

Destination:

CSNE

Modules:

DFHZNAC

XMEOUT Parameters: date, time,applid, termid, tranid, sense, instance, {1=DFHZNAC}

DFHZC2478 E
date time applid termid tranid Invalid FMH. sense ((instance) Module name: {DFHZNAC})
Explanation:

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.

System action:

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.

User response:

Correct the application program so that the LU has a counterpart on the translate table.

Destination:

CSNE

Modules:

DFHZNAC

XMEOUT Parameters: date, time,applid, termid, tranid, sense, instance, {1=DFHZNAC}

DFHZC2479 E
date time applid termid tranid Function not supported. sense ((instance) Module name: {DFHZNAC})
Explanation:

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.

System action:

All send and receive requests are purged. If a task is attached, it is abnormally terminated with a transaction dump.

User response:

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

Destination:

CSNE

Modules:

DFHZNAC

XMEOUT Parameters: date, time,applid, termid, tranid, sense, instance, {1=DFHZNAC}

DFHZC2480 E
date time applid termid tranid Retry requested. sense ((instance) Module name: {DFHZNAC})
Explanation:

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.

System action:

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.

User response:

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

Destination:

CSNE

Modules:

DFHZNAC

XMEOUT Parameters: date, time,applid, termid, tranid, sense, instance, {1=DFHZNAC}

DFHZC2481 E
date time applid termid tranid RU Error. sense ((instance) Module name: {DFHZNAC})
Explanation:

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.

System action:

All send and receive requests are purged. If a task is attached, it is abnormally terminated with a transaction dump.

User response:

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.

Destination:

CSNE

Modules:

DFHZNAC

XMEOUT Parameters: date, time,applid, termid, tranid, sense, instance, {1=DFHZNAC}

DFHZC2482 E
date time applid termid tranid Pipeline session bracket error. sense ((instance) Module name: {DFHZATT})
Explanation:

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.

System action:

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.

User response:

Correct the TCT entry by inserting the BRACKET=NO operand.

Destination:

CSNE

Modules:

DFHZNAC

XMEOUT Parameters: date, time,applid, termid, tranid, sense, instance, {1=DFHZATT}

DFHZC2483 E
date time applid termid tranid Receiver in transmit mode. sense ((instance) Module name: {DFHZNAC})
Explanation:

Normal data flow has been interrupted.

For the meaning of the sense data, see DFHZCxxxx messages.

System action:

Processing continues.

User response:

Retry the WRITE.

Destination:

CSNE

Modules:

DFHZNAC

XMEOUT Parameters: date, time,applid, termid, tranid, sense, instance, {1=DFHZNAC}

DFHZC2484 E
date time applid termid tranid Component not available. sense ((instance) Module name: {DFHZNAC})
Explanation:

An application request could not be satisfied because the required component was not available.

For the meaning of the sense data, see DFHZCxxxx messages.

System action:

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.

User response:

Check the terminal environment, or use the symptom string, and if necessary the dump, to determine the cause of the error.

Destination:

CSNE

Modules:

DFHZNAC

XMEOUT Parameters: date, time,applid, termid, tranid, sense, instance, {1=DFHZNAC}

DFHZC2485 E
date time applid termid tranid Cancel received in 'CS'-mode. sense ((instance) Module name: {DFHZRVX})
Explanation:

A CANCEL indicator was received while a task was active.

For the meaning of the sense data, see DFHZCxxxx messages.

System action:

If a task is attached, it is abnormally terminated with a transaction dump. All outstanding send and receive requests purged.

User response:

None.

Destination:

CSNE

Modules:

DFHZRVX

XMEOUT Parameters: date, time,applid, termid, tranid, sense, instance, {1=DFHZRVX}

DFHZC2486 E
date time applid termid tranid Cancel received in 'CA'-mode. sense ((instance) Module name: {DFHZRAC})
Explanation:

A CANCEL indicator was received while no task was active.

For the meaning of the sense data, see DFHZCxxxx messages.

System action:

Processing continues.

User response:

None.

Destination:

CSNE

Modules:

DFHZRAC

XMEOUT Parameters: date, time,applid, termid, tranid, sense, instance, {1=DFHZRAC}

DFHZC2487 E
date time applid termid tranid nodeid Session connection failed. Node unavailability return code returncode. sense ((instance) Module name: {DFHZBLX | DFHZLGX | DFHZSCX})
Explanation:

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:

  1. The CLSDST macro has been scheduled for this node
  2. The node is in an abnormal condition
  3. The node has an error condition raised against it
  4. The node is already in use
  5. CICS is terminating
  6. VTAM is terminating.

For the meaning of the sense data, see DFHZCxxxx messages.

System action:

The connection request is rejected.

User response:

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.

Destination:

CSNE

Modules:

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}

DFHZC2488 E
date time applid termid tranid nodeid logon request rejected as terminal recovery is in progress. sense ((instance) Module name: {DFHZBLX | DFHZLGX | DFHZSCX})
Explanation:

A connection request was rejected because the CICS terminal recovery program was still executing.

For the meaning of the sense data, see DFHZCxxxx messages.

System action:

The connection request is rejected.

User response:

Retry the connection request. Message DFHRU2800 is produced when the recovery program has completed processing.

Destination:

CSNE

Modules:

DFHZLGX, DFHZSCX, DFHZBLX

XMEOUT Parameters: date, time,applid, termid, tranid, nodeid, sense, instance, {1=DFHZLGX, 2=DFHZSCX, 3=DFHZBLX}

DFHZC2489 E
date time applid termid tranid 3270 - Invalid copy request. sense ((instance) Module name: {DFHZARQ})
Explanation:

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.

System action:

If a task is attached, it is abnormally terminated with a transaction dump.

User response:

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.

Destination:

CSNE

Modules:

DFHZARQ

XMEOUT Parameters: date, time,applid, termid, tranid, sense, instance, {1=DFHZARQ, 2=DFHZARQ, 3=DFHZARQ}

DFHZC2490 E
date time applid termid tranid Request for TOLTEP. sense ((instance) Module name: {DFHZSYX})
Explanation:

On a request for TOLTEP, a receive request completes in error.

For the meaning of the sense data, see DFHZCxxxx messages.

System action:

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.

User response:

None.

Destination:

CSNE

Modules:

DFHZSYX

XMEOUT Parameters: date, time,applid, termid, tranid, sense, instance, {1=DFHZSYX}

DFHZC2492 E
date time applid termid tranid Intervention required on 3270 printer. sense ((instance) Module name: {DFHZNAC})
Explanation:

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.

System action:

No action is performed except printing of the RPL and the TCTTE.

User response:

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.

Destination:

CSNE

Modules:

DFHZNAC

XMEOUT Parameters: date, time,applid, termid, tranid, sense, instance, {1=DFHZNAC}

DFHZC2493 E
date time applid termid tranid Intervention required on 3270 device. sense ((instance) Module name: {DFHZNAC})
Explanation:

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.

System action:

No action is performed.

User response:

Correct the intervention condition.

Destination:

CSNE

Modules:

DFHZNAC

XMEOUT Parameters: date, time,applid, termid, tranid, sense, instance, {1=DFHZNAC}

DFHZC2494 E
date time applid termid tranid Error status sense received from 3270. ((instance) Module name: {DFHZNAC})
Explanation:

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.

System action:

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.

User response:

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.

Destination:

CSNE

Modules:

DFHZNAC

XMEOUT Parameters: date, time,applid, termid, tranid, sense, instance, {1=DFHZNAC}

DFHZC2495 E
date time applid termid tranid Printer Outserv/int reqd/ineligible. Req queued. sense ((instance) Module name: {DFHZNAC})
Explanation:

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.

System action:

Other processing continues.

User response:

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.

Destination:

CSNE

Modules:

DFHZNAC

XMEOUT Parameters: date, time,applid, termid, tranid, sense, instance, {1=DFHZNAC}

DFHZC2496 E
date time applid termid tranid IC put to printer failed{ | IOERROR | TRNIDER | TRMIDER | INVREQ}. sense ((instance) Module name: {DFHZNAC})
Explanation:

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.

System action:

DFHZNEP is recalled by DFHZNAC to allow for further processing.

User response:

Ensure that:

Destination:

CSNE

Modules:

DFHZNAC

XMEOUT Parameters: date, time,applid, termid, tranid, {1= , 2= IOERROR, 3= TRNIDER, 4=TRMIDER, 5= INVREQ}, sense, instance, {1=DFHZNAC}

DFHZC2497 E
date time applid termid tranid Unavailable printer. sense ((instance) Module name: {DFHZARQ})
Explanation:

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.

System action:

If no NEP action is specified, the print request is halted.

User response:

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.

Destination:

CSNE

Modules:

DFHZARQ

XMEOUT Parameters: date, time,applid, termid, tranid, sense, instance, {1=DFHZARQ}

DFHZC2498 E
date time applid termid tranid IC put to printer failed. sense ((instance) Module name: {DFHZARQ})
Explanation:

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.

System action:

Processing continues.

User response:

Check that transaction CSPP is an installed transaction definition and that you have sufficient temporary storage to accommodate the data to be printed.

Destination:

CSNE

Modules:

DFHZARQ

XMEOUT Parameters: date, time,applid, termid, tranid, sense, instance, {1=DFHZARQ}

DFHZC2499
date time applid The following message was destined for a read only terminal. The text is 'msgtext'
Explanation:

The user has entered an invalid entry, the entry is rejected, and the request is backed out.

System action:

Terminal Control backs out the request and issues this message with the error information contained in msgtext.

User response:

Read the error information that is contained in msgtext and reenter the request.

XMEOUT Parameters: date, time,applid, msgtext

DFHZC3202 E
date time applid Transaction CCIN - VTAM netname netname. The value codepage in the codepage parameter is not supported.
Explanation:

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.

System action:

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.

User response:

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.

Destination:

CSCC

Modules:

DFHZCN2

XMEOUT Parameters: date, time,applid, netname, codepage

DFHZC3203 E
date time applid Transaction CCIN - VTAM netname netname. The capabilities parameter is not valid.
Explanation:

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.

System action:

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.

User response:

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

Destination:

CSCC

Modules:

DFHZCN2

XMEOUT Parameters: date, time,applid, netname

DFHZC3204 E
date time applid Transaction CCIN - VTAM netname netname. The codepage parameter has not been specified.
Explanation:

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.

System action:

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.

User response:

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

Destination:

CSCC

Modules:

DFHZCN1

XMEOUT Parameters: date, time,applid, netname

DFHZC3205 E
date time applid Transaction CTIN - virtual terminal termid VTAM netname netname. CICS cannot support the {n.a. | n.a. | n.a. | combination of client and virtual terminal codepage. | client codepage. | virtual terminal codepage.}
Explanation:

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:

1 - 3
n.a. - not applicable and should not occur.
4
unsupported combination of CICS client and virtual terminal codepage. indicates that the two codepages above are known about but CICS does not support data conversion between the CICS client codepage and the virtual terminal codepage.
5
unsupported CICS client codepage indicates that CICS is unable to support the codepage supplied by the CICS client in the CCIN or CTIN transaction.
6
unsupported virtual terminal codepage indicates that the CGCSGID parameter defining the virtual terminal codepage is not supported for CICS data conversion. If the virtual terminal was autoinstalled, CGCSGID was specified in the autoinstall model requested by the CICS client. If the virtual terminal was defined, CGCSGID was defined in the TYPETERM named by the virtual terminal definition.

CICS cannot perform the translations required to support the CICS client with the requested codepage.

netname is the VTAM netname of the CICS client.

System action:

Exception trace point AP3035 is written.

4
unsupported combination of CICS client and virtual terminal codepage.

A response code of ERROR and a reason code of INSTALLCANCELLED is sent to the client. The virtual terminal is NOT installed.

5
unsupported CICS client codepage.

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.

6
unsupported virtual terminal codepage.

A response code of ERROR and a reason code of INSTALLCANCELLED is sent to the client. The virtual terminal is NOT installed.

User response:

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.

Destination:

CSCC

Modules:

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

DFHZC3206 E
date time applid Transaction CTIN - virtual terminal termid VTAM netname netname. The client's terminal install limit has been exceeded.
Explanation:

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.

System action:

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.

User response:

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.

Destination:

CSCC

Modules:

DFHZCT1

XMEOUT Parameters: date, time,applid, termid, netname

DFHZC3207 E
date time applid Transaction CTIN - VTAM netname netname. The request has failed because CCIN has not been run.
Explanation:

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.

System action:

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.

User response:

The CICS client must carry out CCIN uninstall/install before the next CTIN install.

Destination:

CSCC

Modules:

DFHZCT1

XMEOUT Parameters: date, time,applid, netname

DFHZC3208 E
date time applid Transaction CTIN - virtual terminal termid VTAM netname netname. Model modelid cannot be found.
Explanation:

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.

System action:

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.

User response:

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.

Destination:

CSCC

Modules:

DFHZCT1

XMEOUT Parameters: date, time,applid, termid, netname, modelid

DFHZC3209 E
date time applid Transaction CTIN - VTAM netname netname. CICS cannot supply a terminal name because all available names are in use.
Explanation:

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.

System action:

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.

User response:

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.

Destination:

CSCC

Modules:

DFHZCT1

XMEOUT Parameters: date, time,applid, netname

DFHZC3210 E
date time applid Transaction CTIN - virtual terminal termid VTAM netname netname. CICS cannot attach the CITS transaction.
Explanation:

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.

System action:

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.

User response:

Check that the CITS transaction and the DFHZATS program are defined correctly as specified in the DFHSPI IBM supplied group and are installed.

Destination:

CSCC

Modules:

DFHZCT1

XMEOUT Parameters: date, time,applid, termid, netname

DFHZC3211 E
date time applid Transaction CTIN - virtual terminal termid VTAM netname netname. The NetName parameter starts with an invalid character.
Explanation:

A CTIN install request has been received from a CICS client as a result of a CICS_EpiAddTerminal function or terminal emulator operation. Start of changeThe NetName parameter termid starts or ends with aEnd of change character that conflicts with CICS standards.

netname is the VTAM netname of the CICS client.

System action:

Start of changeThe request to install the virtual terminal is rejected. A response code of DISASTER and a reason code of INVALIDTERMID is sent to the client.End of change

User response:

Change the NetName to Start of changestart 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 -.End of change If the NetName was specified correctly, check the input to the CTIN transaction.

Destination:

CSCC

Modules:

DFHZCT1

XMEOUT Parameters: date, time,applid, termid, netname

DFHZC3212 E
date time applid Transaction CTIN - virtual terminal termid VTAM netname netname. The transaction has timed out waiting for CITS to run.
Explanation:

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.

System action:

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.

User response:

Investigate why the CITS transaction was unable to start or was hanging.

You may need to increase MAXTASK or the CITS TRANCLASS allocation.

Destination:

CSCC

Modules:

DFHZCT1

XMEOUT Parameters: date, time,applid, termid, netname

DFHZC3213 E
date time applid Transaction CTIN - virtual terminal termid VTAM netname netname. CICS cannot attach the CDTS transaction.
Explanation:

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.

System action:

Exception trace point AP3028 is written. The attempt to delete the virtual terminal is rejected.

User response:

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.

Destination:

CSCC

Modules:

DFHZCT1

XMEOUT Parameters: date, time,applid, termid, netname

DFHZC3214 E
date time applid Transaction CTIN - virtual terminal termid VTAM netname netname. The CTIN transaction has timed out waiting for CDTS to run.
Explanation:

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.

System action:

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

User response:

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.

Destination:

CSCC

Modules:

DFHZCT1

XMEOUT Parameters: date, time,applid, termid, netname

DFHZC3215 E
date time applid Transaction CTIN - virtual terminal termid VTAM netname netname. The terminal is in use by another transaction.
Explanation:

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.

System action:

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.

User response:

Investigate why a transaction is still running for the virtual terminal.

Destination:

CSCC

Modules:

DFHZCT1

XMEOUT Parameters: date, time,applid, termid, netname

DFHZC3216 E
date time applid Transaction CTIN - virtual terminal termid VTAM netname netname. CICS cannot find the terminal.
Explanation:

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.

System action:

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.

User response:

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.

Destination:

CSCC

Modules:

DFHZCT1

XMEOUT Parameters: date, time,applid, termid, netname

DFHZC3217 E
date time applid Transaction CTIN - VTAM netname netname. The specified function is not valid.
Explanation:

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.

System action:

Exception trace point AP3034 is written. The CTIN transaction abnormally terminates with abend code AZAI.

User response:

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.

Destination:

CSCC

Modules:

DFHZCT1

XMEOUT Parameters: date, time,applid, netname

DFHZC3218 E
date time applid Transaction CTIN - virtual terminal termid VTAM netname netname. A resource with the same name as the terminal is already installed.
Explanation:

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.

System action:

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.

User response:

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.

Destination:

CSCC

Modules:

DFHZCT1

XMEOUT Parameters: date, time,applid, termid, netname

DFHZC3219 E
date time applid Transaction CTIN - virtual terminal termid VTAM netname netname. The terminal is already in use.
Explanation:

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.

System action:

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.

User response:

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.

Destination:

CSCC

Modules:

DFHZCT1

XMEOUT Parameters: date, time,applid, termid, netname

DFHZC3220 E
date time applid Transaction CTIN - virtual terminal termid VTAM netname netname. The terminal has already been installed.
Explanation:

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.

System action:

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.

User response:

The CICS client should issue CTIN uninstall before any attempt to issue another CTIN install for the same NetName.

Destination:

CSCC

Modules:

DFHZCT1

XMEOUT Parameters: date, time,applid, termid, netname

DFHZC3221 E
date time applid Transaction CTIN - virtual terminal termid VTAM netname netname. The name specified is already in use by another CICS resource.
Explanation:

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.

System action:

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.

User response:

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.

Destination:

CSCC

Modules:

DFHZCT1

XMEOUT Parameters: date, time,applid, termid, netname

DFHZC3222 E
date time applid Transaction CTIN - virtual terminal termid VTAM netname netname. The CITS task has terminated abnormally.
Explanation:

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.

System action:

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.

User response:

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.

Destination:

CSCC

Modules:

DFHZCT1

XMEOUT Parameters: date, time,applid, termid, netname

DFHZC3223 E
date time applid Transaction CTIN - virtual terminal termid VTAM netname netname. The surrogate TCTTE is in use and cannot be deleted.
Explanation:

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.

System action:

Exception trace point AP302F is written. The attempt to delete the virtual terminal is rejected.

User response:

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.

Destination:

CSCC

Modules:

DFHZCT1

XMEOUT Parameters: date, time,applid, termid, netname

DFHZC3224 E
date time applid Transaction CTIN - virtual terminal termid VTAM netname netname. The terminal specified for deletion cannot be found.
Explanation:

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.

System action:

The attempt to delete the virtual terminal is rejected.

User response:

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.

Destination:

CSCC

Modules:

DFHZCT1

XMEOUT Parameters: date, time,applid, termid, netname

DFHZC3225 E
date time applid Transaction CTIN - VTAM netname netname. The terminal cannot be deleted because the NetName parameter is missing.
Explanation:

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.

System action:

Exception trace point AP3037 is written - data 2 contains the data received. The attempt to delete the virtual terminal is rejected.

User response:

Examine the input to CTIN. You may need further assistance from IBM. See CICS Problem Determination Guide for guidance on how to proceed.

Destination:

CSCC

Modules:

DFHZCT1

XMEOUT Parameters: date, time,applid, netname

DFHZC3226 E
date time applid Transaction CTIN - virtual terminal termid VTAM netname netname. CICS cannot access the builder parameter set.
Explanation:

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.

System action:

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.

User response:

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

Destination:

CSCC

Modules:

DFHZCT1

XMEOUT Parameters: date, time,applid, termid, netname

DFHZC3227 E
date time applid Transaction CTIN - VTAM netname netname. The client data is longer than expected.
Explanation:

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.

System action:

Exception trace point AP302D is written - data 2 contains the length that was received. The CTIN transaction abnormally terminates with abend code AZAI.

User response:

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.

Destination:

CSCC

Modules:

DFHZCT1

XMEOUT Parameters: date, time,applid, netname

DFHZC3228 E
date time applid Transaction CTIN - VTAM netname netname. The client header data contains an invalid group.
Explanation:

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.

System action:

Exception trace point AP3024 is written - data 2 contains the data received. The CTIN transaction abnormally terminates with abend code AZAI.

User response:

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.

Destination:

CSCC

Modules:

DFHZCT1

XMEOUT Parameters: date, time,applid, netname

DFHZC3229 E
date time applid Transaction CTIN - VTAM netname netname. CICS has received invalid data from the client.
Explanation:

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.

System action:

Exception trace point AP3033 is written - data 2 contains the data received. The CTIN transaction abnormally terminates with abend code AZAI.

User response:

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.

Destination:

CSCC

Modules:

DFHZCT1

XMEOUT Parameters: date, time,applid, netname

DFHZC3230 E
date time applid Transaction CTIN - VTAM netname netname. CICS has received a client request on an unsupported sync level.
Explanation:

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.

System action:

Exception trace point AP302B is written. The CTIN transaction abnormally terminates with abend code AZAI.

User response:

Ensure that the CICS client converses at sync level 0 or 1.

Destination:

CSCC

Modules:

DFHZCT1

XMEOUT Parameters: date, time,applid, netname

DFHZC3231 E
date time applid Transaction CTIN - VTAM netname netname. The client header data contains an invalid version number.
Explanation:

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.

System action:

Exception trace point AP3036 is written - data 2 contains the data received. The CTIN transaction abnormally terminates with abend code AZAI.

User response:

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.

Destination:

CSCC

Modules:

DFHZCT1

XMEOUT Parameters: date, time,applid, netname

DFHZC3240 E
date time applid Transaction CCIN - VTAM netname netname. CICS has received a client request on an unsupported sync level.
Explanation:

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.

System action:

Exception trace point AP3003 is written. The CCIN transaction abnormally terminates with abend code AZAF.

User response:

Ensure that the CICS client converses at sync level 0 or 1.

Destination:

CSCC

Modules:

DFHZCN1

XMEOUT Parameters: date, time,applid, netname

DFHZC3241 E
date time applid Transaction CCIN - VTAM netname netname. The client data is longer than expected.
Explanation:

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.

System action:

Exception trace point AP3004 is written - data 2 contains the length that was received. The CCIN transaction abnormally terminates with abend code AZAF.

User response:

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.

Destination:

CSCC

Modules:

DFHZCN1

XMEOUT Parameters: date, time,applid, netname

DFHZC3242 E
date time applid Transaction CCIN - VTAM netname netname. The client header data contains an invalid group.
Explanation:

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.

System action:

Exception trace point AP3002 is written - data 2 contains the data received. The CCIN transaction abnormally terminates with abend code AZAF.

User response:

Examine the data sent to CICS from the CICS client.

Destination:

CSCC

Modules:

DFHZCN1

XMEOUT Parameters: date, time,applid, netname

DFHZC3243 E
date time applid Transaction CCIN - VTAM netname netname. The client header data contains an invalid version number.
Explanation:

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.

System action:

Exception trace point AP300B is written - data 2 contains the data received. The CCIN transaction abnormally terminates with abend code AZAF.

User response:

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.

Destination:

CSCC

Modules:

DFHZCN1

XMEOUT Parameters: date, time,applid, netname

DFHZC3244 E
date time applid Transaction CCIN - VTAM netname netname. The client header data contains an invalid function.
Explanation:

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.

System action:

Exception trace point AP3002 is written - data 2 contains the data received. The CCIN transaction abnormally terminates with abend code AZAF.

User response:

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.

Destination:

CSCC

Modules:

DFHZCN1

XMEOUT Parameters: date, time,applid, netname

DFHZC3245 E
date time applid Transaction CCIN - VTAM netname netname. The capabilities parameter has not been specified.
Explanation:

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.

System action:

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.

User response:

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

Destination:

CSCC

Modules:

DFHZCN1

XMEOUT Parameters: date, time,applid, netname

DFHZC3246
date time applid Transaction CCIN - virtual terminal termid VTAM netname netname. CICS cannot attach the CDTS transaction.
Explanation:

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.

System action:

The attempt to delete the virtual terminal fails. If this is a CCIN install request, the install continues.

User response:

Ensure that the CDTS transaction and the DFHZATS program are defined correctly as specified in IBM supplied group DFHSPI and that they are installed.

Destination:

CSCC

Modules:

DFHZCN2

XMEOUT Parameters: date, time,applid, termid, netname

DFHZC3247
date time applid Transaction CCIN - virtual terminal termid VTAM netname netname. The CCIN transaction has timed out waiting for CDTS to run.
Explanation:

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.

System action:

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.

User response:

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.

Destination:

CSCC

Modules:

DFHZCN2

XMEOUT Parameters: date, time,applid, termid, netname

DFHZC3248 E
date time applid Transaction CCIN - virtual terminal termid VTAM netname netname. The surrogate TCTTE is in use and cannot be deleted.
Explanation:

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.

System action:

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.

User response:

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.

Destination:

CSCC

Modules:

DFHZCN2

XMEOUT Parameters: date, time,applid, termid, netname

DFHZC3249 E
date time applid Transaction CCIN - VTAM netname netname. CICS has received invalid data from the client.
Explanation:

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.

System action:

Exception trace point AP300E is written - data 2 contains the data received. The CCIN transaction abnormally terminates with abend code AZAF.

User response:

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.

Destination:

CSCC

Modules:

DFHZCN1

XMEOUT Parameters: date, time,applid, netname

DFHZC3400 E
date time applid termid tranid Chain exceeds max chain size. sense ((instance) Module name: {DFHZRAC | DFHZRVS | DFHZRVX})
Explanation:

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.

System action:

If a task is attached, it is abnormally terminated with a transaction dump.

User response:

Ensure that the maximum chain size, generated in CEDA TYPETERM with IOAREALEN (value 2) keyword, is large enough for the maximum chain expected.

Destination:

CSNE

Modules:

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}

DFHZC3401 I
date time applid termid tranid Resource now available. sense ((instance) Module name: {DFHZNAC})
Explanation:

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.

System action:

Any outstanding read or write operation is retried.

User response:

None.

Destination:

CSNE

Modules:

DFHZNAC

XMEOUT Parameters: date, time,applid, termid, tranid, sense, instance, {1=DFHZNAC}

DFHZC3402 E
date time applid termid tranid Invalid READ with outbound chain control. sense ((instance) Module name: {DFHZRVS})
Explanation:

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.

System action:

All outstanding receive requests are purged. If a task is attached, it is abnormally terminated with a transaction dump.

User response:

Correct the application program.

Destination:

CSNE

Modules:

DFHZRVS

XMEOUT Parameters: date, time,applid, termid, tranid, sense, instance, {1=DFHZRVS}

DFHZC3405 E
date time applid termid tranid Catastrophic bracket error. sense ((instance) Module name: {DFHZNAC})
Explanation:

The logical unit detected a failure of CICS to enforce bracket rules.

For the meaning of the sense data, see DFHZCxxxx messages.

System action:

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.

User response:

Use the symptom string, a VTAM trace, and if necessary the dump, to determine the source of the problem.

Destination:

CSNE

Modules:

DFHZNAC

XMEOUT Parameters: date, time,applid, termid, tranid, sense, instance, {1=DFHZNAC}

DFHZC3406 E
date time applid termid tranid Parameter error. sense ((instance) Module name: {DFHZNAC})
Explanation:

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.

System action:

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.

User response:

Correct the application program.

Destination:

CSNE

Modules:

DFHZNAC

XMEOUT Parameters: date, time,applid, termid, tranid, sense, instance, {1=DFHZNAC}

DFHZC3407 E
date time applid termid tranid READ command does not carry change direction indicator. sense ((instance) Module name: {DFHZNAC})
Explanation:

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.

System action:

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.

User response:

Identify the request that caused the error, and locate the element of the network responsible.

Destination:

CSNE

Modules:

DFHZNAC

XMEOUT Parameters: date, time,applid, termid, tranid, sense, instance, {1=DFHZNAC}

DFHZC3408 E
date time applid termid tranid Presentation space integrity lost. sense ((instance) Module name: {DFHZNAC})
Explanation:

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.

System action:

Any outstanding requests are canceled. If a task is attached, it is abnormally terminated with a transaction dump.

User response:

Determine reason for failure at the remote terminal.

Destination:

CSNE

Modules:

DFHZNAC

XMEOUT Parameters: date, time,applid, termid, tranid, sense, instance, {1=DFHZNAC}

DFHZC3409 E
date time applid termid tranid Unexpected negative response received. sense ((instance) Module name: {DFHZRAC})
Explanation:

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.

System action:

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.

User response:

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.

Destination:

CSNE

Modules:

DFHZRAC

XMEOUT Parameters: date, time,applid, termid, tranid, sense, instance, {1=DFHZRAC}

DFHZC3410 E
date time applid termid tranid Invalid input when LU status expected. sense ((instance) Module name: {DFHZRVX})
Explanation:

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.

System action:

If a task is attached, it is abnormally terminated with a transaction dump.

User response:

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

Destination:

CSNE

Modules:

DFHZRVX

XMEOUT Parameters: date, time,applid, termid, tranid, sense, instance, {1=DFHZRVX, 2=DFHZRVX, 3=DFHZRVX}

DFHZC3411 E
date time applid termid tranid Resource temporarily unavailable. sense ((instance) Module name: {DFHZNAC})
Explanation:

A terminal resource required to complete a request is temporarily unavailable.

For the meaning of the sense data, see DFHZCxxxx messages.

System action:

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.

User response:

Refer to the associated VTAM message, if applicable, and follow the guidance provided.

Destination:

CSNE

Modules:

DFHZNAC

XMEOUT Parameters: date, time,applid, termid, tranid, sense, instance, {1=DFHZNAC}

DFHZC3412 E
date time applid termid tranid Intervention required on secondary resource. sense ((instance) Module name: {DFHZNAC})
Explanation:

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.

System action:

The system waits for a logical unit status message and, when this is received, takes appropriate system action.

User response:

Correct the problem that relates to the device.

Destination:

CSNE

Modules:

DFHZNAC

XMEOUT Parameters: date, time,applid, termid, tranid, sense, instance, {1=DFHZNAC}

DFHZC3413 E
date time applid termid tranid Logical Unit busy. sense ((instance) Module name: {DFHZNAC})
Explanation:

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.

System action:

The system waits for a logical unit status message and then takes appropriate action.

User response:

None.

Destination:

CSNE

Modules:

DFHZNAC

XMEOUT Parameters: date, time,applid, termid, tranid, sense, instance, {1=DFHZNAC}

DFHZC3414 E
date time applid termid tranid Request not executable. Secondary resource unavailable. sense ((instance) Module name: {DFHZNAC})
Explanation:

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.

System action:

All outstanding send and receive requests are purged. If a task is attached, it is abnormally terminated with a transaction dump.

User response:

Determine the reason why the resource is not available at the remote terminal.

Destination:

CSNE

Modules:

DFHZNAC

XMEOUT Parameters: date, time,applid, termid, tranid, sense, instance, {1=DFHZNAC}

DFHZC3415 E
date time applid termid tranid No data available. sense ((instance) Module name: {DFHZNAC})
Explanation:

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.

System action:

The receive request is halted. If a task is attached, it is abnormally terminated with a transaction dump.

User response:

Verify that the request was issued to the correct device and that the device is capable of data transmission.

Destination:

CSNE

Modules:

DFHZNAC

XMEOUT Parameters: date, time,applid, termid, tranid, sense, instance, {1=DFHZNAC}

DFHZC3416 E
date time applid termid tranid Session failure. A connection request for an invalid node nodeid could not be terminated. sense ((instance) Module name: {DFHZSCX})
Explanation:

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.

System action:

No further attempts are made to communicate with the invalid node.

User response:

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.

Destination:

CSNE

Modules:

DFHZNAC

XMEOUT Parameters: date, time,applid, termid, tranid, nodeid, sense, instance, {1=DFHZSCX}

DFHZC3417 E
date time applid termid tranid Session processing error. A request for synchronization has been ignored. sense ((instance) Module name: {DFHZSDR})
Explanation:

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.

System action:

If a task is attached, it is abnormally terminated with a transaction dump.

User response:

To determine the cause of the problem, inspect the CSNE, CSMT and CSTL logs for further diagnostic information. Also inspect transaction tranid.

Destination:

CSNE

Modules:

DFHZSDR

XMEOUT Parameters: date, time,applid, termid, tranid, sense, instance, {1=DFHZSDR}

DFHZC3418 E
date time applid termid tranid System generation error. The netname logon request was rejected. sense ((instance) Module name: {DFHZBLX | DFHZLGX | DFHZSCX})
Explanation:

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.

System action:

The request is rejected.

User response:

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.

Destination:

CSNE

Modules:

DFHZSCX, DFHZLGX, DFHZBLX

XMEOUT Parameters: date, time,applid, termid, tranid, netname, sense, instance, {1=DFHZSCX, 2=DFHZBLX, 3=DFHZLGX}

DFHZC3419 E
date time applid termid tranid Session failure. The bind parameter for node netname is unacceptable. sense ((instance) Module name: {DFHZBLX | DFHZSCX | RESERVE})
Explanation:

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.

System action:

The request is rejected. The bind parameter is printed on the CSNE log.

User response:

Determine whether the connecting system has specified its characteristics correctly. If it has not, correct the requesting system.

Destination:

CSNE

Modules:

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}

DFHZC3420 E
date time applid termid tranid Session connection error. Node netname is out of service. sense ((instance) Module name: {DFHZBLX | DFHZOPN})
Explanation:

A logon request was rejected because the TCTTE is out of service.

For the meaning of the sense data, see DFHZCxxxx messages.

System action:

The request is rejected.

User response:

Place the terminal in service by using the master terminal program and reissuing the connection request.

Destination:

CSNE

Modules:

DFHZSCX, DFHZOPN, DFHZBLX

XMEOUT Parameters: date, time,applid, termid, tranid, netname, sense, instance, {1=DFHZOPN, 2=DFHZBLX, 3=DFHZBLX}

DFHZC3421 E
date time applid termid tranid Session shutdown request received. Node netname is receiving orderly shutdown. sense ((instance) Module name: {DFHZASX})
Explanation:

A shutdown request was received for the system. An orderly termination procedure has begun.

For the meaning of the sense data, see DFHZCxxxx messages.

System action:

Orderly termination of the session is started. Access to the remote system is stopped after the current transaction has finished.

User response:

None.

Destination:

CSNE

Modules:

DFHZASX

XMEOUT Parameters: date, time,applid, termid, tranid, netname, sense, instance, {1=DFHZASX}

DFHZC3422 E
date time applid termid tranid Connection failure. Request rejected before a session could be started. sense ((instance) Module name: {DFHZNSP})
Explanation:

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.

System action:

The request is terminated.

User response:

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.

Destination:

CSNE

Modules:

DFHZNSP

XMEOUT Parameters: date, time,applid, termid, tranid, sense, instance, {1=DFHZNSP, 2=DFHZNSP}

DFHZC3423I
date time applid termid tranid FM function not supported. A function requested in an FMD RU is not supported by the receiver. sense ((instance) Module Name: {DFHZNAC})
Explanation:

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.

System action:

All outstanding SENDs and RECEIVEs are purged. If a task is attached, it is abnormally terminated with a transaction dump.

User response:

Investigate the reason for issuing a request for a function that the receiver does not support.

Destination:

CSNE

Modules:

DFHZNAC

XMEOUT Parameters: date, time,applid, termid, tranid, sense, instance, {1=DFHZNAC}

DFHZC3424 E
date time applid termid tranid Session failure. Session terminated immediately. sense ((instance) Module name: {DFHZNSP})
Explanation:

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.

System action:

The session is canceled. The session may be recovered later by VTAM. See also messages DFHZC2409 and DFHZC2410.

User response:

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.

Destination:

CSNE

Modules:

DFHZNSP

XMEOUT Parameters: date, time,applid, termid, tranid, sense, instance, {1=DFHZNSP, 2=DFHZNSP, 3=DFHZNSP}

DFHZC3426 E
date time applid termid tranid Resource unknown. sense ((instance) Module name: {DFHZNAC})
Explanation:

During intersystem connection, no matching TCTTE could be found.

For the meaning of the sense data, see DFHZCxxxx messages.

System action:

The request is terminated.

User response:

Ensure that the name of the requested TCTTE is correctly specified in the requesting system.

Destination:

CSNE

Modules:

DFHZNAC

XMEOUT Parameters: date, time,applid, termid, tranid, sense, instance, {1=DFHZNAC}

DFHZC3427 E
date time applid termid tranid Invalid parameter in bind area. sense ((instance) Module name: {DFHZNAC})
Explanation:

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.

System action:

The request is terminated.

User response:

Determine which parameters in the bind area are incorrect, and correct them.

Destination:

CSNE

Modules:

DFHZNAC

XMEOUT Parameters: date, time,applid, termid, tranid, sense, instance, {1=DFHZNAC}

DFHZC3429 E
date time applid termid tranid Resynch error - CICS did not resynchronize, other logical unit was expecting resynch. sense ((instance) Module name: {DFHZRSY | DFHZSYX})
Explanation:

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.

System action:

Processing continues.

User response:

Check whether this resynchronization mismatch is acceptable.

Destination:

CSNE

Modules:

DFHZRSY, DFHZSYX

XMEOUT Parameters: date, time,applid, termid, tranid, sense, instance, {1=DFHZRSY, 2=DFHZRSY, 3=DFHZRSY, 4=DFHZRSY, 5=DFHZSYX}

DFHZC3433 E
date time applid termid tranid FMH7 was received on ISC session. Sense code is : xxxxxxxx{Error log data is : | No error log data received. | No error log data available. }xxxxxxxx sense ((instance) Module name: {DFHZERH | DFHZRAC | DFHZRVX})
Explanation:

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.

System action:

The action taken depends upon the sense code.

User response:

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.

Destination:

CSNE

Modules:

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}

DFHZC3434 E
date time applid termid tranid Unbind received while session still active. sense ((instance) Module name: {DFHZSCX})
Explanation:

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.

System action:

The session is terminated.

User response:

Determine the cause of the termination by using CICS Trace and the diagnostic information available on the CSNE log. Try to reestablish the session.

Destination:

CSNE

Modules:

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}

DFHZC3435 E
date time applid termid tranid Path error detected. Device cannot be contacted. sense ((instance) Module name: {DFHZNAC})
Explanation:

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.

System action:

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.

User response:

Determine the cause of the termination. Try to reestablish the session.

Destination:

CSNE

Modules:

DFHZNAC

XMEOUT Parameters: date, time,applid, termid, tranid, sense, instance, {1=DFHZNAC}

DFHZC3436 E
date time applid termid tranid End user not authorized. sense ((instance) Module name: {DFHZNAC})
Explanation:

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.

System action:

The session is terminated.

User response:

Determine why the end user is not authorized to perform the request.

Destination:

CSNE

Modules:

DFHZNAC

XMEOUT Parameters: date, time,applid, termid, tranid, sense, instance, {1=DFHZNAC}

DFHZC3437 I
date time applid termid tranid Node netname action taken: action ((instance) Module name: {DFHZNAC})
Explanation:

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.

System action:

Action
Effect
ABRECV
Cancel receive.
ABSEND
Cancel send.
ABTASK
Abend task
CLSDST
Close session.
GMM
Send good morning message.
OUTSRV
Place session out of service.
CREATE
Allow ATI to acquire the session if required.
NOCREATE
Do not allow ATI to acquire the session.
NEG RESP
Send an exception response.
SIMLOGON
Generate SIMLOGON request for the session.
CNTASK
Cancel the task.
SYSDUMP
Take a system dump.
PURGEBMS
Purge any BMS pages.
User response:

The user action depends on what action has been taken by the system. This is indicated by action in the message text.

Destination:

CSNE

Modules:

DFHZNAC

XMEOUT Parameters: date, time,applid, termid, tranid, netname, action, instance, {1=DFHZNAC}

DFHZC3438 E
date time applid termid tranid Device powered off. sense ((instance) Module name: {DFHZNAC})
Explanation:

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.

System action:

The system waits for a logical unit status message and, when the message has been received, takes appropriate system action.

User response:

Correct the problem that relates to the device.

For the meaning of the sense codes, refer to the explanatory paragraph in message DFHZC2461.

Destination:

CSNE

Modules:

DFHZNAC

XMEOUT Parameters: date, time,applid, termid, tranid, sense, instance, {1=DFHZNAC}

DFHZC3439 E
date time applid termid tranid Negative response received to SDT. sense ((instance) Module name: {DFHZNAC})
Explanation:

A negative response has been received to the START DATA TRAFFIC (SDT) command.

For the meaning of the sense data, see DFHZCxxxx messages.

System action:

Processing continues.

User response:

None.

Destination:

CSNE

Modules:

DFHZNAC

XMEOUT Parameters: date, time,applid, termid, tranid, sense, instance, {1=DFHZNAC}

DFHZC3440 E
date time applid termid tranid Unable to send error message - session in free status. sense ((instance) Module name: {DFHZEMW})
Explanation:

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.

System action:

Processing continues.

User response:

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.

Destination:

CSNE

Modules:

DFHZEMW

XMEOUT Parameters: date, time,applid, termid, tranid, sense, instance, {1=DFHZEMW, 2=DFHZEMW}

DFHZC3441 I
date time applid Orderly termination of VTAM sessions requested. sense ((instance) Module name: {DFHZSHU})
Explanation:

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.

System action:

All nodes are quiesced and each session is closed as it becomes inactive. When all sessions have been closed, the ACB is closed.

User response:

None.

Destination:

CSNE

Modules:

DFHZSHU

XMEOUT Parameters: date, time,applid, sense, instance, {1=DFHZSHU}

DFHZC3442 I
date time applid Immediate termination of VTAM sessions requested. sense ((instance) Module name: {DFHZSHU | DFHZTPX | RESERVE})
Explanation:

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.

System action:

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.

User response:

None.

Destination:

CSNE

Modules:

DFHZSHU, DFHZTPX

XMEOUT Parameters: date, time,applid, sense, instance, {1=DFHZSHU, 2=RESERVE, 3=RESERVE,4=DFHZTPX, 5=DFHZSHU}

DFHZC3443 I
date time applid VTAM has been cancelled or the ACB has been forceclosed. VTAM sessions terminated.sense ((instance) Module name: {DFHZSHU | DFHZSYX | DFHZTPX})
Explanation:

VTAM has been cancelled or force closed by the CICS/VTAM operator.

For the meaning of the sense data, see DFHZCxxxx messages.

System action:

CICS will close its ACB. All transactions running on VTAM sessions are abnormally terminated.

User response:

None.

Destination:

CSNE

Modules:

DFHZSHU, DFHZTPX, DFHZSYX

XMEOUT Parameters: date, time,applid, sense, instance, {1=DFHZSHU, 3=DFHZSYX, 4=DFHZTPX,5=DFHZSHU}

DFHZC3444 E
date time applid termid tranid Unexpected condition detected during RECEIVE processing. sense ((instance) Module name: {DFHZRAC | DFHZRVS})
Explanation:

Start of changeCICS has detected that more than 32k of data has been transmitted while receiving data from terminal "termid".End of change

For the meaning of the sense data, see DFHZCxxxx messages.

System action:

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.

User response:

To determine the cause of this error,

Destination:

CSNE

Modules:

Start of changeDFHZRVS, DFHZRACEnd of change

Start of changeXMEOUT Parameters: date, time,applid, termid, tranid, sense, instance, {1=DFHZRVS, 2=DFHZRAC}End of change

DFHZC3445 E
date time applid termid tranid State error. sense ((instance) Module name: {DFHZNAC})
Explanation:

CICS has received a state error negative response (VTAM sense code 20yy).

For the meaning of the sense data, see DFHZCxxxx messages.

System action:

System action:

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.

User response:

Determine the reason for the error before restarting the session.

Destination:

CSNE

Modules:

DFHZNAC

XMEOUT Parameters: date, time,applid, termid, tranid, sense, instance, {1=DFHZNAC}

DFHZC3446 E
date time applid termid tranid Request error. sense ((instance) Module name: {DFHZNAC})
Explanation:

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.

System action:

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.

User response:

Determine the reason for the error.

Destination:

CSNE

Modules:

DFHZNAC

XMEOUT Parameters: date, time,applid, termid, tranid, sense, instance, {1=DFHZNAC}

DFHZC3447 E
date time applid termid tranid Request reject error. sense ((instance) Module name: {DFHZNAC})
Explanation:

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.

System action:

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.

User response:

Determine the reason for the error.

Destination:

CSNE

Modules:

DFHZNAC

XMEOUT Parameters: date, time,applid, termid, tranid, sense, instance, {1=DFHZNAC}

DFHZC3448 E
date time applid termid tranid Security identification error. sense ((instance) Module name: {DFHZNAC})
Explanation:

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.

System action:

The logical unit is placed out of service and the session is closed.

User response:

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.

Destination:

CSNE

Modules:

DFHZNAC

XMEOUT Parameters: date, time,applid, termid, tranid, sense, instance, {1=DFHZNAC}

DFHZC3449 I
date time applid termid tranid Leaving unattended mode. sense ((instance) Module name: {DFHZNAC})
Explanation:

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.

System action:

The mode of operation bit TCTEMOPU is reset in the TCTTE.

User response:

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.

Destination:

CSNE

Modules:

DFHZNAC

XMEOUT Parameters: date, time,applid, termid, tranid, sense, instance, {1=DFHZNAC}

DFHZC3450 I
date time applid termid tranid Entering unattended mode. sense ((instance) Module name: {DFHZNAC})
Explanation:

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.

System action:

The mode of operation bit TCTEMOPU is set in the TCTTE.

User response:

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.

Destination:

CSNE

Modules:

DFHZNAC

XMEOUT Parameters: date, time,applid, termid, tranid, sense, instance, {1=DFHZNAC}

DFHZC3451 I
date time applid termid tranid Currently no data to send. sense ((instance) Module name: {DFHZNAC})
Explanation:

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.

System action:

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.

User response:

Ensure that no more receive requests are issued to the terminal.

Destination:

CSNE

Modules:

DFHZNAC

XMEOUT Parameters: date, time,applid, termid, tranid, sense, instance, {1=DFHZNAC}

DFHZC3452 E
date time applid termid tranid Signal received - Code xxxx. sense ((instance) Module name: {DFHZASX})
Explanation:

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.

System action:

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.

User response:

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.

Destination:

CSNE

Modules:

DFHZASX

XMEOUT Parameters: date, time,applid, termid, tranid, xxxx, sense, instance, {1=DFHZASX, 2=DFHZASX}

DFHZC3453 E
date time applid termid tranid RH usage error. sense ((instance) Module name: {DFHZNAC})
Explanation:

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.

System action:

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.

User response:

None.

Destination:

CSNE

Modules:

DFHZNAC

XMEOUT Parameters: date, time,applid, termid, tranid, sense, instance, {1=DFHZNAC}

DFHZC3454 E
date time applid termid tranid Session initiation failure. Bind response from node netname is unacceptable. sense ((instance) Module name: {DFHZOPX})
Explanation:

A remote secondary’s response to a negotiable bind contained unacceptable parameters.

For the meaning of the sense data, see DFHZCxxxx messages.

System action:

Session initialization fails. The sent and received bind parameters are printed on the CSNE log.

User response:

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.

Destination:

CSNE

Modules:

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}

DFHZC3455 E
date time applid termid tranid Session initiation failure. Bind response from node netname contains an invalid session qualifier pair. sense ((instance) Module name: {DFHZOPX})
Explanation:

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.

System action:

Session initialization fails. The sent and received bind images are printed on the CSNE log.

User response:

Correct the error in the remote system. If there is an invalid format, change it to LEN PSQ LEN SSQ.

Destination:

CSNE

Modules:

DFHZOPX

XMEOUT Parameters: date, time,applid, termid, tranid, netname, sense, instance, {1=DFHZOPX, 2=DFHZOPX, 3=DFHZOPX}

DFHZC3456 E
date time applid termid tranid No outboard formats loaded. sense ((instance) Module name: {DFHZNAC})
Explanation:

An outboard format has been referenced, but no outboard formats are loaded on this logical unit.

System action:

Transaction tranid is abnormally terminated with a transaction dump.

User response:

Load the necessary outboard formats.

Destination:

CSNE

Modules:

DFHZNAC

XMEOUT Parameters: date, time,applid, termid, tranid, sense, instance, {1=DFHZNAC}

DFHZC3457 E
date time applid termid tranid Requested outboard format not loaded. sense ((instance) Module name: {DFHZNAC})
Explanation:

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.

System action:

Transaction tranid is abnormally terminated with a transaction dump.

User response:

Load the requested outboard format.

Destination:

CSNE

Modules:

DFHZNAC

XMEOUT Parameters: date, time,applid, termid, tranid, sense, instance, {1=DFHZNAC}

DFHZC3458 E
date time applid termid tranid Requested format group not loaded. sense ((instance) Module name: {DFHZNAC})
Explanation:

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.

System action:

Transaction tranid is abnormally terminated with a transaction dump.

User response:

Load the required format group.

Destination:

CSNE

Modules:

DFHZNAC

XMEOUT Parameters: date, time,applid, termid, tranid, sense, instance, {1=DFHZNAC}

DFHZC3459 E
date time applid termid tranid Unsupported data stream. sense ((instance) Module name: {DFHZNAC})
Explanation:

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.

System action:

Transaction tranid is abnormally terminated.

User response:

Either ensure that transaction tranid is not run against the terminal, or change the terminal to one that supports the data stream.

Destination:

CSNE

Modules:

DFHZNAC

XMEOUT Parameters: date, time,applid, termid, tranid, sense, instance, {1=DFHZNAC}

DFHZC3460 E
date time applid termid tranid Requested character set not present. sense ((instance) Module name: {DFHZNAC})
Explanation:

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.

System action:

Transaction tranid is abnormally terminated with a transaction dump.

User response:

Ensure that the character set referenced by the LCID is loaded.

Destination:

CSNE

Modules:

DFHZNAC

XMEOUT Parameters: date, time,applid, termid, tranid, sense, instance, {1=DFHZNAC}

DFHZC3461 I
date time applid termid tranid Node netname session started. sense ((instance) Module name: {DFHZEV1 | DFHZEV2 | DFHZOPX})
Explanation:

CICS has successfully issued or received a bind to the node netname.

For the meaning of the sense data, see DFHZCxxxx messages.

System action:

Processing continues.

User response:

None.

Destination:

CSNE

Modules:

DFHZOPX, DFHZEV1, DFHZEV2

XMEOUT Parameters: date, time,applid, termid, tranid, netname, sense, instance, {1=DFHZOPX, 2=DFHZOPX, 3=DFHZEV1, 4=DFHZEV2}

DFHZC3462 I
date time applid termid tranid Node netname session terminated. sense ((instance) Module name: {DFHZCLS})
Explanation:

A session with node netname has been closed.

For the meaning of the sense data, see DFHZCxxxx messages.

System action:

Processing continues.

User response:

None.

Destination:

CSNE

Modules:

DFHZCLS

XMEOUT Parameters: date, time,applid, termid, tranid, netname, sense, instance, {1=DFHZCLS, 2=DFHZCLS}

DFHZC3463 I
date time applid VTAM ACB opened. VTAM Return Code = X'rc'. Time = time sense ((instance) Module name: {DFHZOPA})
Explanation:

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.

System action:

Processing continues.

User response:

Start of changeThis depends on the return code:End of change

Destination:

CSNE

Modules:

DFHZOPA

XMEOUT Parameters: date, time,applid, X'rc', time, sense, instance, {1=DFHZOPA}

DFHZC3464 I
date time applid termid tranid Node netname released by MT Operator/LU Services Manager. sense ((instance) Module name: {DFHZSTU})
Explanation:

The master terminal operator issued a CEMT command to release the logical unit (LU).

For the meaning of the sense data, see DFHZCxxxx messages.

System action:

The LU is closed. Any task associated with the LU is terminated either abnormally (if the master terminal operator so desired) or normally.

User response:

None.

Destination:

CSNE

Modules:

DFHZSTU

XMEOUT Parameters: date, time,applid, termid, tranid, netname, sense, instance, {1=DFHZSTU}

DFHZC3465 E
date time applid termid tranid Unexpected response received. sense ((instance) Module name: {DFHZRAC | DFHZRLP | DFHZRVX})
Explanation:

CICS received a positive response in one of the following circumstances:

For the meaning of the sense data, see DFHZCxxxx messages.

System action:

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.

User response:

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.

Destination:

CSNE

Modules:

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}

DFHZC3466 E
date time applid termid tranid Out of session during session start up .sense ((instance) Module name: {DFHZSEX | DFHZSKR})
Explanation:

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.

System action:

The session is terminated and the TCTTE for terminal termid is left out of service.

User response:

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.

Destination:

CSNE

Modules:

DFHZSEX, DFHZSKR

XMEOUT Parameters: date, time,applid, termid, tranid, sense, instance, {1=DFHZSEX, 2=DFHZSKR}

DFHZC3467 E
date time applid termid tranid Permanent insufficient resource. sense ((instance) Module name: {DFHZNAC})
Explanation:

The PS buffer resource required by load PS is not available.

For the meaning of the sense data, see DFHZCxxxx messages.

System action:

If a task is attached, it is abnormally terminated with a transaction dump.

User response:

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.

Destination:

CSNE

Modules:

DFHZNAC

XMEOUT Parameters: date, time,applid, termid, tranid, sense, instance, {1=DFHZNAC}

DFHZC3468 E
date time applid termid tranid CLEAR command received. sense ((instance) Module name: {DFHZSCX})
Explanation:

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.

System action:

The session is canceled immediately, and any transaction executing on that session is also abnormally terminated and a transaction dump is produced.

User response:

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.

Destination:

CSNE

Modules:

DFHZSCX

XMEOUT Parameters: date, time,applid, termid, tranid, sense, instance, {1=DFHZSCX}

DFHZC3469 E
date time applid termid tranid Session re-establishment being awaited. sense ((instance) Module name: {DFHZSCX})
Explanation:

The secondary LU is being passed to a new application program via CLSDST(PASS).

For the meaning of the sense data, see DFHZCxxxx messages.

System action:

If a task is attached, it is abnormally terminated with a transaction dump.

User response:

None.

Destination:

CSNE

Modules:

DFHZSCX

XMEOUT Parameters: date, time,applid, termid, tranid, sense, instance, {1=DFHZSCX}

DFHZC3470 E
date time applid termid tranid LU session failure caused by: {restart/takeover. LU does not support ACTLU(ERP). | route extension to cluster failed. | LU abend, discontact, DACTPU or ANS. }sense ((instance) Module name: {DFHZSCX})
Explanation:

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.

System action:

If a task is attached, it is abnormally terminated with a transaction dump.

User response:

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.

Destination:

CSNE

Modules:

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}

DFHZC3471 E
date time applid termid tranid Virtual route inoperative. sense ((instance) Module name: {DFHZSCX})
Explanation:

The session has been broken because the virtual route it was using has failed.

For the meaning of the sense data, see DFHZCxxxx messages.

System action:

If a task is attached, it is abnormally terminated with a transaction dump. For APPC sessions, CICS attempts to reestablish the failing session.

User response:

None.

Destination:

CSNE

Modules:

DFHZSCX

XMEOUT Parameters: date, time,applid, termid, tranid, sense, instance, {1=DFHZSCX}

DFHZC3472 E
date time applid termid tranid Device end received. sense ((instance) Module name: {DFHZSYX})
Explanation:

Device end was received from a non-SNA VTAM supported 3270

For the meaning of the sense data, see DFHZCxxxx messages.

System action:

The good morning message is displayed, unless the terminal is associated with an active task.

User response:

None.

Destination:

CSNE

Modules:

DFHZSYX

XMEOUT Parameters: date, time,applid, termid, tranid, sense, instance, {1=DFHZSYX}

DFHZC3474 E
date time applid termid tranid Virtual route deactivated. sense ((instance) Module name: {DFHZSCX})
Explanation:

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.

System action:

If a task is attached, it is abnormally terminated with a transaction dump. Afterwards CICS attempts to reestablish the session.

User response:

Determine the cause of the session failure and attempt to reestablish the session.

Destination:

CSNE

Modules:

DFHZSCX

XMEOUT Parameters: date, time,applid, termid, tranid, sense, instance, {1=DFHZSCX}

DFHZC3475 E
date time applid termid tranid Unrecoverable LU failure. sense ((instance) Module name: {DFHZSCX})
Explanation:

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.

System action:

If a task is attached, it is abnormally terminated with a transaction dump. Session reinitiation is not attempted.

User response:

None.

Destination:

CSNE

Modules:

DFHZSCX

XMEOUT Parameters: date, time,applid, termid, tranid, sense, instance, {1=DFHZSCX}

DFHZC3476 E
date time applid termid tranid Recoverable LU failure. sense ((instance) Module name: {DFHZSCX})
Explanation:

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.

System action:

If a task is attached, it is abnormally terminated with a transaction dump. CICS attempts to reinitiate the session.

User response:

None.

Destination:

CSNE

Modules:

DFHZSCX

XMEOUT Parameters: date, time,applid, termid, tranid, sense, instance, {1=DFHZSCX}

DFHZC3477 E
date time applid termid tranid Cleanup received. sense ((instance) Module name: {DFHZSCX})
Explanation:

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.

System action:

If a task is attached, it is abnormally terminated with a transaction dump. CICS attempts to reinitiate the session.

User response:

None.

Destination:

CSNE

Modules:

DFHZSCX

XMEOUT Parameters: date, time,applid, termid, tranid, sense, instance, {1=DFHZSCX}

DFHZC3479 E
date time applid termid tranid Unbind received after session failure detected. sense ((instance) Module name: {DFHZSCX})
Explanation:

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.

System action:

The session is terminated, and the transaction using it is abnormally terminated or informed by return code.

User response:

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.

Destination:

CSNE

Modules:

DFHZSCX

XMEOUT Parameters: date, time,applid, termid, tranid, sense, instance, {1=DFHZSCX, 2=DFHZSCX}

DFHZC3480 E
date time applid termid tranid Session could not be started due to insufficient CICS nucleus function - ISC not loaded. sense ((instance) Module name: {DFHZBLX | DFHZLGX | DFHZSIM})
Explanation:

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.

System action:

The session initiation request is rejected.

User response:

If APPC connections are to be used, ensure that ISC=NO is not used for CICS initialization.

Destination:

CSNE

Modules:

DFHZSCX, DFHZLGX, DFHZSIM

XMEOUT Parameters: date, time,applid, termid, tranid, sense, instance, {1=DFHZSIM, 2=DFHZBLX, 3=DFHZLGX}

DFHZC3481 E
date time applid termid tranid 3270 Data Stream protocol error. sense ((instance) Module name: {DFHZRAC | DFHZRVX})
Explanation:

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.

System action:

CICS cancels the session and any transactions attached to the terminal.

User response:

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.

Destination:

CSNE

Modules:

DFHZRAC, DFHZRVX

XMEOUT Parameters: date, time,applid, termid, tranid, sense, instance, {1=DFHZRVX, 2=DFHZRAC}

DFHZC3482 E
date time applid tranid Logon from node nodeid rejected. Insufficient storage for autoinstall request. sense ((instance) Module name: {DFHZBLX | DFHZLGX | DFHZSCX})
Explanation:

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.

System action:

CICS rejects the logon request.

User response:

Retry the logon.

Destination:

CSNE

Modules:

DFHZLGX, DFHZSCX, DFHZBLX

XMEOUT Parameters: date, time,applid, tranid, nodeid, sense, instance, {1=DFHZLGX, 2=DFHZLGX, 3=DFHZBLX, 4=DFHZSCX}

DFHZC3484 I
date time applid netname is now connected to applid. sense ((instance) Module name: {DFHZNSP})
Explanation:

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.

System action:

CICS processing continues.

User response:

None.

Destination:

CSNE

Modules:

DFHZNSP

XMEOUT Parameters: date, time,applid, netname, applid, sense, instance, {1=DFHZNSP}

DFHZC3485 E
date time applid netname A CLSDST Pass Procedure error occurred at applid. Status byte xx Reason byte yy.sense ((instance) Module name: {DFHZNSP})
Explanation:

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.

System action:

CICS saves the status byte xx and reason byte yy passed by VTAM in the Notify Request Unit. CICS processing continues.

User response:

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

Destination:

CSNE

Modules:

DFHZNSP

XMEOUT Parameters: date, time,applid, netname, applid, xx, yy, sense, instance, {1=DFHZNSP}

DFHZC3486 E
date time applid netname The named LU cannot be connected for sessions at applid. sense ((instance) Module name: {DFHZSYX})
Explanation:

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.

System action:

Processing continues.

User response:

None.

Destination:

CSNE

Modules:

DFHZSYX

XMEOUT Parameters: date, time,applid, netname, applid, sense, instance, {1=DFHZSYX, 2=DFHZSYX}

DFHZC3487 E
date time applid netname Unable to PASS to node nodeid. CLSDST PASS is not authorized. sense ((instance) Module name: {DFHZLEX})
Explanation:

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.

System action:

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.

User response:

To use the ISSUE PASS command, you must code AUTH=PASS on the VTAM definition of the CICS APPL, then reactivate the APPL.

Destination:

CSNE

Modules:

DFHZLEX

XMEOUT Parameters: date, time,applid, netname, nodeid, sense, instance, {1=DFHZLEX, 2=DFHZLEX}

DFHZC3488 E
date time applid netname ISC session connection failure. sense ((instance) Module name: {DFHZSIX})
Explanation:

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.

System action:

CLSDST is issued to reset the session.

User response:

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.

Destination:

CSNE

Modules:

DFHZSIX

XMEOUT Parameters: date, time,applid, netname, sense, instance, {1=DFHZSIX}

DFHZC3489 E
date time applid netname The LU is inhibited for sessions. sense ((instance) Module name: {DFHZSYX})
Explanation:

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.

System action:

The request is rejected and the session is set into NOINTLOG state to prevent further requests being issued.

User response:

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.

Destination:

CSNE

Modules:

DFHZSYX

XMEOUT Parameters: date, time,applid, netname, sense, instance, {1=DFHZSYX}

DFHZC3490 E
date time applid netname Unable to pass to node nodeid. sense ((instance) Module name: {DFHZCLX | DFHZLEX | DFHZSYX})
Explanation:

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.

System action:

A VTAM CLSDST macro is issued to halt communication with the node.

User response:

Ensure that the node nodeid is defined and active to VTAM.

Destination:

CSNE

Modules:

DFHZSYX, DFHZLEX, DFHZCLX

XMEOUT Parameters: date, time,applid, netname, nodeid, sense, instance, {1=DFHZLEX, 2=DFHZSYX, 3=DFHZCLX}

DFHZC3491 E
date time applid netname Unable to make session XRF capable. sense ((instance) Module name: {DFHZLEX})
Explanation:

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.

System action:

CICS performs a SIMLOGON, but does not deem the session to be "XRF capable". CICS therefore treats the terminal as class 2.

User response:

No immediate action is necessary. You may need to increase the number of buffers in the NCP.

Destination:

CSNE

Modules:

DFHZLEX

XMEOUT Parameters: date, time,applid, netname, sense, instance, {1=DFHZLEX}

DFHZC3492 E
date time applid tranid Logon for node nodeid contained invalid NIBUSER token. sense ((instance) Module name: {DFHZLGX})
Explanation:

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.

System action:

An unexpected condition has occurred during SIMLOGON. CICS will continue processing normally.

User response:

None.

Destination:

CSNE

Modules:

DFHZLGX

XMEOUT Parameters: date, time,applid, tranid, nodeid, sense, instance, {1=DFHZLGX}

DFHZC3493 E
date time applid termid tranid Invalid device type for a print request. sense ((instance) Module name : {DFHZARQ})
Explanation:

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.

System action:

If no other action is specified in the Network Error Program (NEP). the print request is halted. CICS processing continues.

User response:

Check that the printers specified for the information display system are valid. Valid devices are 3270P and LUTYPE3.

Destination:

CSNE

Modules:

DFHZARQ

XMEOUT Parameters: date, time,applid, termid, tranid, sense, instance, {1=DFHZARQ}

DFHZC3494 E
date time applid termid tranid Request error sense ((instance) Module name : {DFHZNAC})
Explanation:

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.

System action:

All send and receive requests are purged and transaction tranid is abnormally terminated with a dump.

User response:

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.

Destination:

CSNE

Modules:

DFHZSYX

XMEOUT Parameters: date, time,applid, termid, tranid, sense, instance, {1=DFHZNAC}

DFHZC3495 E
date time applid Logon occurred for terminal with netname netname before Notify received sense ((instance) Module name : {DFHZLGX})
Explanation:

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.

System action:

CICS processing continues. Any subsequent NOTIFY requests for the terminal identified will be ignored.

User response:

It is recommended that any user processing for CLSDST PASS messages incorporates this message.

Destination:

CSNE

Modules:

DFHZLGX

XMEOUT Parameters: date, time,applid, netname, sense, instance, {1=DFHZLGX}

DFHZC3496 E
date time applid System dump has been taken for terminal termid ((instance) Module name: {DFHZNAC})
Explanation:

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.

System action:

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.

User response:

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.

Destination:

CSNE

Modules:

DFHZNAC

XMEOUT Parameters: date, time,applid, termid, instance, {1=DFHZNAC}

DFHZC3497 E
date time applid Link to module DFHZNEP from DFHZNAC failed because {module DFHZNEP is not AMODE 31. |module DFHZNEP could not be loaded. | module DFHZNEP could not be autoinstalled. | of an unexpected error.} ((instance) Module name: {DFHZNAC})
Explanation:

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.

System action:

The default action or actions set by DFHZNAC are taken.

User response:

The reason for the failure is specified in the message. Possible solutions are:

Destination:

CSNE

Modules:

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}

DFHZC3498 E
date time applid Abend abcode has occurred in module DFHZNEP. ((instance) Module name: {DFHZNAC})
Explanation:

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.

System action:

Control is passed back to the calling module, DFHZNAC. DFHZNAC reinstates the default actions set before DFHZNEP was called. The actions are then taken.

User response:

Refer to abend code abcode for details of the original error. Follow the user response given in the abend code to solve the problem.

Destination:

CSNE

Modules:

DFHZNAC

XMEOUT Parameters: date, time,applid, abcode, instance, {1=DFHZNAC}

DFHZC3499 E
date time applid OS Getmain failure in module DFHmodname with return code X'return_code' while attempting to process message DFHZCmessage_number. sense ((instance) Module name: {DFHZATA | DFHZLEX | DFHZLGX | DFHZRAC | DFHZSCX | DFHZSHU | DFHZSYX | DFHZTPX})
Explanation:

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.

System action:

Processing continues normally.

User response:

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.

Destination:

CSNE

Modules:

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}

DFHZC4900 I
date time applid termid tranid CNOS {sent to | received from} Node netname System sysid Modename modename, Max = n1, Win=n2, {race detected | successful | values amended | modename not recognized | modename closed | CNOS failed}. ((instance) Module name: {DFHZGCN})
Explanation:

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.

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

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

System action:

The negotiated values are applied.

User response:

None.

Destination:

CSNE

Modules:

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}

DFHZC4901 I
date time applid termid tranid Node netname System sysid Modename modename, Negotiated values: Max=n1, Win=n2. ((instance) Module name: {DFHZGCN})
Explanation:

This message follows message DFHZC4900 when the maximum session count (n1) and the maximum source contention winner sessions (n2) have been renegotiated.

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

System action:

The negotiated values are applied.

User response:

None.

Destination:

CSNE

Modules:

DFHZGCN

XMEOUT Parameters: date, time,applid, termid, tranid, netname, sysid, modename, n1,n2, instance, {1=DFHZGCN}

DFHZC4902 E
date time applid termid tranid Attach FMH or subfield length error. sense ((instance) Module name: {DFHZATT})
Explanation:

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.

System action:

The task is abnormally terminated with a dump.

User response:

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.

Destination:

CSNE

Modules:

DFHZATT

XMEOUT Parameters: date, time,applid, termid, tranid, sense, instance, {1=DFHZATT, 2=DFHZATT, 3=DFHZATT, 4=DFHZATT, 5=DFHZATT, 6=DFHZATT, 7=DFHZATT}

DFHZC4903 E
date time applid termid tranid Attach FMH not found. sense ((instance) Module name: {DFHZATT | DFHZRAC})
Explanation:

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.

System action:

The task is abnormally terminated with a dump.

User response:

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.

Destination:

CSNE

Modules:

DFHZATT, DFHZRAC

XMEOUT Parameters: date, time,applid, termid, tranid, sense, instance, {1=DFHZATT, 2=DFHZATT, 3=DFHZRAC}

DFHZC4904 E
date time applid termid tranid Bracket FSM error. sense ((instance) Module name: {DFHZRAC | DFHZRLP | DFHZSDL | DFHZSLX})
Explanation:

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.

System action:

The task is abnormally terminated with a dump.

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

User response:

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.

Destination:

CSNE

Modules:

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}

DFHZC4905 E
date time applid termid tranid Chain FSM error. sense ((instance) Module name: {DFHZDET | DFHZERH | DFHZRAC | DFHZRLP | DFHZSDL | DFHZSLX})
Explanation:

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.

System action:

The task is abnormally terminated with a dump.

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

User response:

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.

Destination:

CSNE

Modules:

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}

DFHZC4906 E
date time applid termid tranid Contention FSM error. sense ((instance) Module name: {DFHZCLS | DFHZDET | DFHZRAC | DFHZRLP})
Explanation:

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.

System action:

The task is abnormally terminated with a dump.

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

User response:

Start of changeIf this message occurs after a persistent sessions restart, look for associated messages for more guidance. The problem might be temporary.End of change

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.

Destination:

CSNE

Modules:

Start of changeDFHZRAC, DFHZRLP, DFHZDET, DFHZCLS DFHZCCEnd of change

Start of changeXMEOUT 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}End of change

DFHZC4907 E
date time applid termid tranid Invalid request to send data routine. sense ((instance) Module name: {DFHZSDL})
Explanation:

DFHZSDL was entered, but no valid request was passed to it.

For the meaning of the sense data, see DFHZCxxxx messages.

System action:

The task is abnormally terminated with a dump.

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

User response:

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

Destination:

CSNE

Modules:

DFHZSDL

XMEOUT Parameters: date, time,applid, termid, tranid, sense, instance, {1=DFHZSDL, 2=DFHZSDL, 3=DFHZSDL, 4=DFHZSDL, 5=DFHZSDL}

DFHZC4909 E
date time applid termid tranid Invalid request to receive data routine. sense ((instance) Module name: {DFHZRVL})
Explanation:

DFHZRVL was entered, but no valid request was passed.

For the meaning of the sense data, see DFHZCxxxx messages.

System action:

The task is abnormally terminated with a dump.

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

User response:

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

Destination:

CSNE

Modules:

DFHZRVL

XMEOUT Parameters: date, time,applid, termid, tranid, sense, instance, {1=DFHZRVL}

DFHZC4910 E
date time applid termid tranid Receive buffer too small. sense ((instance) Module name: {DFHZRVL})
Explanation:

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.

System action:

The task will be abnormally terminated with a dump.

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

User response:

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

Destination:

CSNE

Modules:

DFHZRVL

XMEOUT Parameters: date, time,applid, termid, tranid, sense, instance, {1=DFHZRVL, 2=DFHZRVL, 3=DFHZRVL, 4=DFHZRVL}

DFHZC4911 E
date time applid termid tranid LU6.2 exception response received. sense ((instance) Module name: {DFHZRLP})
Explanation:

A non-process-level exception response has been received.

For the meaning of the sense data, see DFHZCxxxx messages.

System action:

The task is abnormally terminated with a dump.

User response:

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.

Destination:

CSNE

Modules:

DFHZRLP

XMEOUT Parameters: date, time,applid, termid, tranid, sense, instance, {1=DFHZRLP}

DFHZC4912 E
date time applid termid tranid BID received with invalid DFC indicators. sense ((instance) Module name: {DFHZRAC | DFHZRLP})
Explanation:

BID with data received, but not OIC.

For the meaning of the sense data, see DFHZCxxxx messages.

System action:

The task is abnormally terminated.

User response:

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.

Destination:

CSNE

Modules:

DFHZRAC, DFHZRLP

XMEOUT Parameters: date, time,applid, termid, tranid, sense, instance, {1=DFHZRLP, 2=DFHZRAC, 3=DFHZRAC}

DFHZC4913 E
date time applid termid tranid BID with data received with invalid DFC indicators. sense ((instance) Module name: {DFHZRLP})
Explanation:

A BID with data was received in an invalid state for rejection.

For the meaning of the sense data, see DFHZCxxxx messages.

System action:

The task is abnormally terminated.

User response:

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.

Destination:

CSNE

Modules:

DFHZRLP

XMEOUT Parameters: date, time,applid, termid, tranid, sense, instance, {1=DFHZRLP, 2=DFHZRLP, 3=DFHZRLP, 4=DFHZRLP}

DFHZC4914 E
date time applid termid tranid Data length exceed max RU size. sense ((instance) Module name: {DFHZRLP})
Explanation:

The record length received exceeds the buffer length.

For the meaning of the sense data, see DFHZCxxxx messages.

System action:

The task is abnormally terminated.

User response:

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.

Destination:

CSNE

Modules:

DFHZRLP

XMEOUT Parameters: date, time,applid, termid, tranid, sense, instance, {1=DFHZRLP}

DFHZC4915 E
date time applid termid tranid EOC received with invalid DFC indicators. sense ((instance) Module name: {DFHZRLP})
Explanation:

An end chain was received with invalid DFC indicators.

For the meaning of the sense data, see DFHZCxxxx messages.

System action:

The task is abnormally terminated.

User response:

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.

Destination:

CSNE

Modules:

DFHZRLP

XMEOUT Parameters: date, time,applid, termid, tranid, sense, instance, {1=DFHZRLP}

DFHZC4916 E
date time applid termid tranid Send response failed. sense ((instance) Module name: {DFHZRLP})
Explanation:

A response, sent to acknowledge successful receipt of data, was rejected by VTAM.

For the meaning of the sense data, see DFHZCxxxx messages.

System action:

The task is abnormally terminated with a dump.

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

User response:

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

Destination:

CSNE

Modules:

DFHZRLP

XMEOUT Parameters: date, time,applid, termid, tranid, sense, instance, {1=DFHZRLP}

DFHZC4917 E
date time applid termid tranid BIS received with invalid DFC indicators. sense ((instance) Module name: {DFHZRLP})
Explanation:

Bracket initiation stopped (BIS) received with invalid DFC flags.

For the meaning of the sense data, see DFHZCxxxx messages.

System action:

The task is abnormally terminated.

User response:

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.

Destination:

CSNE

Modules:

DFHZRLP

XMEOUT Parameters: date, time,applid, termid, tranid, sense, instance, {1=DFHZRLP, 2=DFHZRLP}

DFHZC4918 E
date time applid termid tranid Unexpected response received. sense ((instance) Module name: {DFHZRLP})
Explanation:

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.

System action:

The task is abnormally terminated.

User response:

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.

Destination:

CSNE

Modules:

DFHZRLP

XMEOUT Parameters: date, time,applid, termid, tranid, sense, instance, {1=DFHZRLP, 2=DFHZRLP, 3=DFHZRLP, 4=DFHZRLP, 5=DFHZRLP}

DFHZC4919 E
date time applid termid tranid Invalid indicators received. sense ((instance) Module name: {DFHZARER | DFHZARL})
Explanation:

An indicator other than CD, CEB, RQD2, or error response has been received.

For the meaning of the sense data, see DFHZCxxxx messages.

System action:

The task is abnormally terminated with a dump.

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

User response:

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

Destination:

CSNE

Modules:

DFHZARL, DFHZARER, DFHZARL

XMEOUT Parameters: date, time,applid, termid, tranid, sense, instance, {1=DFHZARL, 2=DFHZARL, 3=DFHZARL, 4=DFHZARL, 5=DFHZARER}

DFHZC4920 E
date time applid termid tranid Invalid data received. sense ((instance) Module name: {DFHZARER | DFHZARL | DFHZERH})
Explanation:

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.

System action:

The task is abnormally terminated with a dump.

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

User response:

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

Destination:

CSNE

Modules:

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}

DFHZC4921 E
date time applid sysid LU services manager failure. R15 =X'xxxxx' R0 =X'yyyyy'
Explanation:

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
System action:

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.

User response:

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.

Destination:

CSNE

Modules:

DFHLUP

XMEOUT Parameters: date, time,applid, sysid, X'xxxxx', X'yyyyy'

DFHZC4922 E
date time applid termid tranid Single session shutdown with DRAIN=CLOSE. sense ((instance) Module name: {DFHZERH | DFHZGDA | DFHZRAC})
Explanation:

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.

System action:

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

User response:

None.

Destination:

CSNE

Modules:

DFHZRAC, DFHZGDA, DFHZERH

XMEOUT Parameters: date, time,applid, termid, tranid, sense, instance, {1=DFHZRAC, 2=DFHZGDA, 3=DFHZERH}

DFHZC4923 I
date time applid termid tranid Conversation abnormally terminated by transaction end in system sysid
Explanation:

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.

System action:

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.

User response:

Correct the application program. To find the command in error, use the state diagrams in the CICS Intercommunication Guide.

Destination:

CSMT

Modules:

DFHZARL

XMEOUT Parameters: date, time,applid, termid, tranid, sysid

DFHZC4924 E
date time applid termid tranid Bind security password missing or invalid. sense ((instance) Module name: {DFHZBLX | DFHZOPX | DFHZSCX})
Explanation:

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.

System action:

The bind is rejected.

User response:

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.

Destination:

CSNE

Modules:

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}

DFHZC4925 E
date time applid termid tranid Inconsistent attach security required. sense ((instance) Module name: {DFHZOPN | DFHZOPX})
Explanation:

This message can be issued for any of the reasons listed below.

  1. CICS has received a bind request specifying attach time security requirements different from those specified in the first bind.
  2. CICS has received a bind requesting persistent verification.
  3. CICS has received a bind which does not include an SNA functional management header (FMH12).

For the meaning of the sense data, see DFHZCxxxx messages.

System action:

CICS rejects the bind.

User response:

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.

Destination:

CSNE

Modules:

DFHZOPX, DFHZOPN

XMEOUT Parameters: date, time,applid, termid, tranid, sense, instance, {1=DFHZOPX, 2=DFHZOPN, 3=DFHZOPN, 4=DFHZOPX}

DFHZC4926 E
date time applid termid tranid Bind security encryption error. sense ((instance) Module name: {DFHZEV1 | DFHZEV2})
Explanation:

CICS detected an error while verifying an encrypted bind security password.

For the meaning of the sense data, see DFHZCxxxx messages.

System action:

CICS rejects the bind.

User response:

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.

Destination:

CSNE

Modules:

DFHZEV1, DFHZEV2

XMEOUT Parameters: date, time,applid, termid, tranid, sense, instance, {1=DFHZEV1, 2=DFHZEV2, 3=DFHZEV1}

DFHZC4927 E
date time applid termid tranid Bind FMH response error. sense ((instance) Module name: {DFHZRAC})
Explanation:

CICS received a bind with bind security without an FMH12.

For the meaning of the sense data, see DFHZCxxxx messages.

System action:

CICS rejects the bind.

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

User response:

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.

Destination:

CSNE

Modules:

DFHZRAC

XMEOUT Parameters: date, time,applid, termid, tranid, sense, instance, {1=DFHZRAC, 2=DFHZRAC, 3=DFHZRAC, 4=DFHZRAC}

DFHZC4928 E
date time applid termid tranid Bind security GETMAIN of a TIOA failed. sense ((instance) Module name: {DFHZEV1})
Explanation:

CICS required a TIOA work area for bind security validation, but the GETMAIN failed because insufficient storage was available.

System action:

CICS rejects the bind.

User response:

Consider increasing the size of the CICS region or reducing the number of concurrent CICS tasks (MXT parameter in the system initialization table).

Destination:

CSNE

Modules:

DFHZEV1

XMEOUT Parameters: date, time,applid, termid, tranid, sense, instance, {1=DFHZEV1}

DFHZC4929
date time applid termid tranid Invalid or unsupported BIND for logmode logmode. Response X'response', Reason X'reason' ((instance) Module: {DFHZOPN})
Explanation:

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:

X'04'
The BIND supplied does not match the TCTTE - detected by DFHZBANS.
X'08'
The BIND supplied is unsupported - detected by DFHZBANV.
X'0C'
The BIND supplied is invalid - detected by DFHZBANV.

The reason code for a response of X'04' is as follows:

X'1B'
Unsupported TCTTE type or not VTAM
X'1C'
No NIB descriptor chained from TCTTE
X'1D'
No BMS extension chained from TCTTE
X'1E'
Same as for reason code X'1D'
X'1F'
LU6.2 BIND, but TCTTE does not match.

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.
System action:

CICS rejects the logon request. The BIND being validated is printed with this message.

User response:

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.

Destination:

CSMT

Modules:

DFHZOPN

XMEOUT Parameters: date, time,applid, termid, tranid, logmode, X'response', X'reason', instance, {1=DFHZOPN}

DFHZC4930 E
date time applid termid tranid Session unbound following read timeout. sense ((instance) Module name: {DFHZARER | DFHZARL})
Explanation:

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.

System action:

CICS abends the task abnormally with a dump.

User response:

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.

Destination:

CSNE

Modules:

DFHZARL, DFHZARER.

XMEOUT Parameters: date, time,applid, termid, tranid, sense, instance, {1=DFHZARL, 2=DFHZARL, 3=DFHZARER}

DFHZC4931 E
date time applid termid tranid VTAM detected bad logmode name. sense ((instance) Module name: {DFHZLEX})
Explanation:

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.

System action:

CICS places the session permanently out of service and for APPC, the mode entry is flagged unusable.

User response:

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.

Destination:

CSNE

Modules:

DFHZLEX

XMEOUT Parameters: date, time,applid, termid, tranid, sense, instance, {1=DFHZLEX}

DFHZC4932 E
date time applid termid tranid Invalid conversation type requested. sense ((instance) Module name: {DFH62XM})
Explanation:

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.

System action:

The task is abended and a dump is produced. The session is unbound.

User response:

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.

Destination:

CSNE

Modules:

Start of changeDFH62XMEnd of change

Start of changeXMEOUT Parameters: date, time,applid, termid, tranid, sense, instance, {1=DFH62XM}End of change

DFHZC4933 E
date time applid termid tranid Invalid DBA requested. sense ((instance) Module name: {DFH62XM})
Explanation:

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.

System action:

The task abends and a dump is produced. The session is unbound.

User response:

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.

Destination:

CSNE

Modules:

Start of changeDFH62XMEnd of change

Start of changeXMEOUT Parameters: date, time,applid, termid, tranid, sense, instance, {1=DFH62XM}End of change

DFHZC4934 E
date time applid termid tranid Invalid syncpoint level requested. sense ((instance) Module name: {DFH62XM})
Explanation:

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.

System action:

The task abends and a dump is produced.

User response:

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.

Destination:

CSNE

Modules:

Start of changeDFH62XMEnd of change

Start of changeXMEOUT Parameters: date, time,applid, termid, tranid, sense, instance, {1=DFH62XM}End of change

DFHZC4935 E
date time applid termid tranid Invalid UOWID supplied. sense ((instance) Module name: {DFH62XM})
Explanation:

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.

System action:

The task abends and a dump is produced. The session is unbound.

User response:

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.

Destination:

CSNE

Modules:

Start of changeDFH62XMEnd of change

Start of changeXMEOUT Parameters: date, time,applid, termid, tranid, sense, instance, {1=DFH62XM, 2=DFH62XM, 3=DFH62XM, 4=DFH62XM, 5=DFH62XM, 6=DFH62XM}End of change

DFHZC4936 E
date time applid termid tranid Attach FMH or subfield length error. sense ((instance) Module name: {DFH62XM})
Explanation:

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:

1
The FMH Length is not equal to the length of the fixed length portion + the length of all the sub fields.
2
The Conversation Correlator length within the FMH is greater than 8.

For the meaning of the sense data, see DFHZCxxxx messages.

System action:

The task abends and a dump is produced.

User response:

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.

Destination:

CSNE

Modules:

Start of changeDFH62XMEnd of change

Start of changeXMEOUT Parameters: date, time,applid, termid, tranid, sense, instance, {1=DFH62XM, 2=DFH62XM}End of change

DFHZC4937 E
date time applid SAF request for LU6.2 bind has been rejected. Return Codes from the Security Manager are: RF= X'rf' and R0= X'r0' sense ((instance) Module name: {DFHZEV1 | DFHZEV2 | DFHZOPN})
Explanation:

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.

System action:

CICS rejects the bind.

User response:

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.

Destination:

CSNE

Modules:

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}

DFHZC4938 E
date time applid SAF request for LU6.2 bind has failed with ESM return code RF= X'rf' and reason code R0= X'r0' sense ((instance) Module name: {DFHZEV1 | DFHZEV2 | DFHZOPN})
Explanation:

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.

System action:

CICS rejects the bind.

User response:

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.

Destination:

CSNE

Modules:

DFHZEV1, DFHZEV2, DFHZOPN

XMEOUT Parameters: date, time,applid, X'rf', X'r0', sense, instance, {1=DFHZOPN, 2=DFHZOPN, 3=DFHZEV1, 4=DFHZEV2}

DFHZC4939 E
date time applid Extraction of LU6.2 security data has failed with ESM returncode RF= X'rf' and reason code R0= X'r0' sense ((instance) Module name: {DFHZEV1 | DFHZEV2 | DFHZOPN})
Explanation:

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.

System action:

CICS rejects the bind.

User response:

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.

Destination:

CSNE

Modules:

DFHZEV1, DFHZEV2, DFHZOPN

XMEOUT Parameters: date, time,applid, X'rf', X'r0', sense, instance, {1=DFHZOPN, 2=DFHZOPN, 3=DFHZEV1, 4=DFHZEV2}

DFHZC4940 E
date time applid Bind time failure. No session key found in LU6.2 profile. sense ((instance) Module name: {DFHZEV1 | DFHZEV2 | DFHZOPN})
Explanation:

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.

System action:

CICS rejects the bind.

User response:

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.

Destination:

CSNE

Modules:

DFHZEV1, DFHZEV2, DFHZOPN

XMEOUT Parameters: date, time,applid, sense, instance, {1=DFHZOPN, 2=DFHZOPN, 3=DFHZEV1,4=DFHZEV2}

DFHZC4941 E
date time applid Bind time failure. LU6.2 profile locked. sense ((instance) Module name: {DFHZEV1 | DFHZEV2 | DFHZOPN})
Explanation:

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.

System action:

CICS rejects the bind.

User response:

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.

Destination:

CSNE

Modules:

DFHZEV1, DFHZEV2, DFHZOPN

XMEOUT Parameters: date, time,applid, sense, instance, {1=DFHZOPN, 2=DFHZOPN, 3=DFHZEV1,4=DFHZEV2}

DFHZC4942 E
date time applid Bind time failure. Expired LU6.2 profile found. sense ((instance) Module name: {DFHZEV1 | DFHZEV2 | DFHZOPN})
Explanation:

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.

System action:

CICS rejects the bind.

User response:

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.

Destination:

CSNE

Modules:

DFHZEV1, DFHZEV2, DFHZOPN

XMEOUT Parameters: date, time,applid, sense, instance, {1=DFHZOPN, 2=DFHZOPN, 3=DFHZEV1,4=DFHZEV2}

DFHZC4943 E
date time applid termid tranid RPL B FSM error. sense ((instance) Module name: {DFHZSDL})
Explanation:

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.

System action:

The task is abnormally terminated with abend code ATNI and a dump is produced.

User response:

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.

Destination:

CSNE

Modules:

DFHZSDL

XMEOUT Parameters: date, time,applid, termid, tranid, sense, instance, {1=DFHZSDL}

DFHZC4944
date time applid termid tranid Protocol Violation detected within bind security indicators. sense ((instance) MODULE NAME: {DFHZBLX | DFHZOPX})
Explanation:

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.

System action:

CICS rejects the bind.

User response:

Ensure that the correct data is sent in the bind for the required type of security.

Destination:

CSMT

Modules:

DFHZSCX, DFHZOPX, DFHZBLX

XMEOUT Parameters: date, time,applid, termid, tranid, sense, instance, {1=DFHZBLX, 2=DFHZBLX, 3=DFHZOPX, 4=DFHZOPX}

DFHZC4945 E
date time applid termid tranid Session unbind request due to the forcepurge of a task. sense ((instance) Module name: {DFHZARER})
Explanation:

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.

System action:

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.

User response:

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.

Destination:

CSNE

Modules:

DFHZARER

XMEOUT Parameters: date, time,applid, termid, tranid, sense, instance, {1=DFHZARER}

DFHZC4946 E
date time applid termid tranid Invalid attach parameter was received. sense ((instance) Module name: {DFH62XM})
Explanation:

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:

instance
Meaning
1
The bind security indicators show that the connection is defined as ATTACHSEC(LOCAL) indicating that this LU does not accept any security parameters in an attach from the partner LU. One or more of the following security parameters has been found: Userid, Password, Profile, AV, PV1 and PV2.
2
An already-verified (AV) indicator has been received in an attach from the partner LU, but the bind security indicators show that this LU does not support the receipt of the AV indicator.
3
A persistent verification signon (PV2) indicator, or a persistent verification signed-on (PV1) indicator, has been received in an attach from the partner LU, but the bind security indicators show that this LU does not support the receipt of the PV indicators.
System action:

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

User response:

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.

Destination:

CSNE

Modules:

Start of changeDFH62XMEnd of change

Start of changeXMEOUT Parameters: date, time,applid, termid, tranid, sense, instance, {1=DFH62XM, 2=DFH62XM, 3=DFH62XM}End of change

DFHZC4947 E
date time applid termid tranid Attach time security check has failed. Security not valid. sense ((instance) Module name: {DFH62XM})
Explanation:

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:

instance
Meaning
1
Unrecognized access security subfield
2
Multiple userid access security subfields present
3
Multiple profile access security subfields present
4
Multiple password access security subfields present
5
Userid required in FMH but not received
6
PV1 and PV2 security indicators both present in FMH5
7
Password received when AV indicator set
8
Password received when PV1 indicator set
9
Password required for PV2 but not received.
System action:

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

User response:

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.

Destination:

CSNE

Modules:

Start of changeDFH62XM, DFHZGXAEnd of change

Start of changeXMEOUT 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}End of change

DFHZC4948 E
date time applid An error has been detected when processing an{ unknown | inbound | outbound}{ request. | Persistent Verify Signoff request. | Persistent Verify Timeout request.} Transaction tranid is{ continuing. | terminating. | terminating abnormally.} Error code: X'xxxxx' Connection: yyyy
Explanation:

An error has been detected during the execution of transaction CLS3. The error code indicates the nature of the error:

X'01'
Transaction CLS3 issued an unsuccessful communications request on an APPC session.
X'02'
Transaction CLS3 was started by a START command with data, but the format of the data was incorrect.
X'04'
Transaction CLS3 is attempting to send a signoff request to a remote system, but the connection to the remote system is not an APPC connection.
X'06'
Transaction CLS3 was not started by terminal input, nor by a START command.
X'09'
Transaction CLS3 was started by a START command with data, but the data could not be retrieved.
X'0A'
Transaction CLS3 is attempting to send a signoff request to a remote system, but there is no connection to the remote system.
X'0B'
Transaction CLS3 unsuccessfully attempted to allocate an APPC session to a remote system.
System action:

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.

User response:

This depends upon the error code:

X'01'
Determine why the communications request on the APPC session failed. Possible reasons are:
  • There has been a session failure.
  • The connected transaction has abended.
This error produces an exception trace, which helps to determine the cause of the problem.
X'02'
Ensure that transaction CLS3 was started by CICS-supplied code, and not by application code. If it was started by CICS-supplied code, contact your IBM Support Center.
X'04'
Check the connection definition for the remote system. It should be an APPC connection.
X'06'
Ensure that transaction CLS3 was started by CICS-supplied code, and not by application code. If it was started by CICS-supplied code, contact your IBM Support Center.
X'09'
Determine why the data could not be retrieved. If you are unable to do so, contact your IBM Support Center
X'0A'
Ensure that the connection has been correctly defined
X'0B'
Ensure that the connection is acquired and in service
Destination:

CSNE

Modules:

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

Start of changeDFHZC4949 EEnd of change
Start of changedate time applid termid tranid netname Receive Any stall - {data lost. | response lost. | command lost. }CLSDST return code X'rc' sense ((instance) Module name: {DFHZRAC})End of change
Start of change
Explanation:

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.

End of change
Start of change
System action:

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.

End of change
Start of change
User response:

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.

End of change
Start of change
Destination:

CSNE

End of change
Modules:

Start of changeDFHZRACEnd of change

Start of changeXMEOUT Parameters:End of changeStart of change End of changeStart of changedate, End of changeStart of changetime,End of changeStart of changeapplid, End of changeStart of changetermid, End of changeStart of changetranid, End of changeStart of changenetname, End of changeStart of change{1=data lost. , End of changeStart of change2=response lost. , End of changeStart of change3=command lost. }, End of changeStart of changeX'rc', End of change Start of changesense, End of changeStart of changeinstance, End of changeStart of change{1=DFHZRAC, End of changeStart of change2=DFHZRAC, End of changeStart of change3=DFHZRAC}End of change

Start of changeDFHZC4950 EEnd of change
Start of changedate time applid An error has occurred when attempting to attach the outbound Connection Quiesce Protocol transaction CQPO on session termid. Release of connection sysid is continuing. ((instance) Module name: {DFHZCLS})End of change
Start of change
Explanation:

An error has been detected while attempting to attach the outbound transaction for the Connection Quiesce Protocol (CQPO) on an APPC session.

End of change
Start of change
System action:

The release of the connection continues, but the Connection Quiesce Protocol will take place only if the partner system successfully initiates it.

End of change
Start of change
User response:

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.

End of change
Start of change
Destination:

CSNE

End of change
Modules:

Start of changeDFHZCLSEnd of change

Start of changeXMEOUT Parameters:End of changeStart of change End of changeStart of changedate, End of changeStart of changetime,End of changeStart of changeapplid, End of changeStart of changetermid, End of changeStart of changesysid, End of changeStart of changeinstance, End of changeStart of change{1=DFHZCLS}End of change

Start of changeDFHZC4951 EEnd of change
Start of changedate time applid An error has been detected when processing an{ unknown | inbound | outbound} Connection Quiesce Protocol request. Transaction tranid is{ continuing. | terminating. | terminating abnormally.} Error code: X'xxxxx' Connection: yyyyEnd of change
Start of change
Explanation:

An error has been detected during the execution of transaction tranid. The error code indicates the nature of the error:

X'01'
Transaction tranid was not started by terminal input, nor by an internal CICS command.
X'02'
Transaction tranid was started by an inbound FMH5, but the TPN was not the correct value for the Connection Quiesce Protocol.
X'03'
Transaction tranid issued an unsuccessful communications request on an APPC session.
X'04'
Transaction tranid has been attached by an inbound FMH5. The format of the data received from the remote system did not comply with the architecture for the Connection Quiesce Protocol.
X'05'
Transaction tranid has received an unexpected response from the Recovery Manager.
X'06'
Transaction tranid has been attached by an internal CICS command and has sent a Connection Quiesce Protocol request to the remote system. The format of the reply received from the remote system did not comply with the architecture for the Protocol.
X'07'
Transaction tranid was started, but its principal facility is not a terminal or session.
End of change
Start of change
System action:

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.

End of change
Start of change
User response:

This depends upon the error code:

X'01, 02, 07'
Ensure that transaction tranid was started by CICS-supplied code, and not by application code. If it was started by CICS-supplied code, contact your IBM Support Center.
X'03'
Determine why the communications request on the APPC session failed. Possible reasons are:
  • There has been a session failure.
  • The connected transaction has abended.
This error produces an exception trace, which helps to determine the cause of the problem.

In other cases, contact your IBM Support Center.

End of change
Start of change
Destination:

CSNE

End of change
Modules:

Start of changeDFHCLS5End of change

Start of changeXMEOUT Parameters:End of changeStart of change End of changeStart of changedate, End of changeStart of changetime,End of changeStart of changeapplid, End of changeStart of change{1= unknown, End of changeStart of change2= inbound,End of change Start of change3= outbound}, End of changeStart of changetranid, End of changeStart of change{1=continuing., End of changeStart of change2= terminating., End of changeStart of change3=terminating abnormally.}, End of changeStart of changeX'End of changeStart of changexxxxx', End of change Start of changeyyyyEnd of change

DFHZC5900 E
date time applid System sysid has shipped definitions but connection cccc is not known to this system.
Explanation:

CICS has received definitions from remote system sysid, but cannot find a connection named cccc.

System action:

CICS continues.

User response:

If you want these definitions to be accepted, install the necessary connection using CEDA, and retransmit the definitions from the remote system.

Destination:

CSMT

Modules:

DFHBSTZ1, DFHBSTZ2

XMEOUT Parameters: date, time,applid, sysid, cccc

DFHZC5901 E
date time applid Install for resource failed. xxxx could not obtain yyyy storage
Explanation:

When installing resource resource, CICS module xxxx could not get storage for the extent specified by the value of yyyy.

System action:

CICS continues.

User response:

If possible, increase the size of your CICS address space. Otherwise, consider reducing the number of resources used in one CICS run.

Start of change
Destination:

CSMT

End of change
Modules:

Start of changeDFHBSMIR, DFHBSMPP, DFHBSM62, DFHBSS, DFHBSSZM, DFHBSTS, DFHBSTB, DFHBSTB3, DFHBSTC, DFHBSTZ, DFHBSTZB, DFHBSTZO, DFHBSTZR, DFHBSTZV, DFHBSTZ1, DFHBSTZ2, DFHBSZZSEnd of change

Start of changeXMEOUT Parameters:End of changeStart of change End of changeStart of changedate, End of changeStart of changetime,End of changeStart of changeapplid, End of changeStart of changeresource, End of changeStart of changexxxx, End of changeStart of changeyyyyEnd of change

DFHZC5902 E
date time applid Deletion of terminal termid failed. BMS Paging session still active
Explanation:

CICS cannot delete terminal termid because a BMS paging session is still active for the terminal.

System action:

CICS continues.

User response:

Sign on to terminal termid and purge the pages.

Destination:

CSMT

Modules:

DFHBSTB

XMEOUT Parameters: date, time,applid, termid

DFHZC5903 E
date time applid Deletion of terminal termid failed. CICS logic error
Explanation:

CICS cannot delete the terminal termid, because the CICS batch data attach function (DIP) is still active for this terminal.

System action:

CICS continues. A system dump is taken with dumpcode ZC5903. Message DFHME0116 is normally produced containing the symptom string for this problem.

User response:

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

Destination:

CSMT

Modules:

DFHBSTD

XMEOUT Parameters: date, time,applid, termid

DFHZC5904 E
date time applid Deletion of terminal termid failed. CEDF is still active
Explanation:

CICS cannot delete the terminal termid because an EDF session is still active for this terminal.

System action:

CICS continues.

User response:

Deactivate EDF for the terminal, and reinstall the group.

Destination:

CSMT

Modules:

DFHBSTE

XMEOUT Parameters: date, time,applid, termid

DFHZC5905 E
date time applid Deletion of terminal termid failed. CICS logic error
Explanation:

CICS cannot delete terminal termid because the command level interface is still active for this terminal.

System action:

CICS continues. A system dump is taken with dumpcode ZC5905. Message DFHME0116 is normally produced containing the symptom string for this problem.

User response:

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

Destination:

CSMT

Modules:

DFHBSTH

XMEOUT Parameters: date, time,applid, termid

DFHZC5906 E
date time applid Install failed because 'xxxx' is not a permitted value for a terminal or connection name
Explanation:

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.

System action:

CICS continues.

User response:

Correct the definition to use a valid name and reinstall the group.

Destination:

CSMT

Modules:

DFHBSS, DFHBSTZ, DFHBSTZ1, DFHBSTZ2 DFHBSMPP

XMEOUT Parameters: date, time,applid, xxxx

DFHZC5907 E
date time applid Deletion of remote shipped terminal failed for connection cccc.
Explanation:

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.

System action:

CICS continues.

User response:

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.

Destination:

CSMT

Modules:

DFHBSSZ

XMEOUT Parameters: date, time,applid, cccc

DFHZC5908 E
date time applid Install for terminal termid failed. The security manager gave return code retcode
Explanation:

CICS cannot install terminal termid. DFHXSMN gave the return code retcode.

System action:

CICS continues.

User response:

Check the value of the return code retcode in the CICS Customization Guide.

Destination:

CSMT

Modules:

DFHBSTS

XMEOUT Parameters: date, time,applid, termid, retcode

DFHZC5909 E
date time applid Install of resource resource failed. Call to DFHIRP irp_function Return_code did not succeed, See DFHIRSDS for return code.
Explanation:

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,

System action:

CICS continues. The MRO connection resource is not installed.

User response:

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.

Destination:

CSMT

Modules:

DFHBSSZR

XMEOUT Parameters: date, time,applid, resource, irp_function,Return_code

DFHZC5911 E
date time applid Install for resource resource failed. Connection cccc not found
Explanation:

CICS could not find the connection cccc associated with resource resource.

System action:

CICS continues.

User response:

Install connection cccc.

Destination:

CSMT

Modules:

DFHBSMIR

XMEOUT Parameters: date, time,applid, resource, cccc

DFHZC5912 E
date time applid Install for terminal termid failed. It is incompatible with connection cccc
Explanation:

The terminal termid and the connection cccc are mutually incompatible.

System action:

CICS continues.

User response:

Modify your definition of termid or cccc.

Destination:

CSMT

Modules:

DFHBSTZ, DFHBSTZ2

XMEOUT Parameters: date, time,applid, termid, cccc

DFHZC5913 E
date time applid Deletion of node id failed. {A table entry is locked. | A table entry was not found. | There was a logic error.} Table=tabname Key(key) Module(modname) Instance=inst.
Explanation:

CICS cannot delete node id. The message explains the reason for the failure.

  1. One of its TMP table entries is locked by other tasks.
  2. A TMP table entry could not be found, possibly because the node was already deleted by another task.
  3. There was a CICS logic error. A DFHTM0002 error message may have been issued as well.

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.

System action:

The resource is not deleted. If the entry was locked, CICS issues one or more message DFHZC5980.

User response:

Choose the action which corresponds to the reason identified in the message:

  1. See message DFHZC5980 for further information and guidance.
  2. If the node is deleted, no action is needed. If the node exists, determine whether it was replaced while this request was running. If the entry exists and has not been replaced, you will need assistance from IBM. See CICS Problem Determination Guide for guidance on how to proceed.
  3. You need further assistance from IBM to resolve this problem. See CICS Problem Determination Guide for guidance on how to proceed.
Destination:

CSMT

Modules:

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

DFHZC5914 E
date time applid Deletion of terminal termid found another deletion of it in progress
Explanation:

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.

System action:

CICS continues.

User response:

Check if a CEDA user is installing the terminal.

Destination:

CSMT

Modules:

DFHBSMIR, DFHBSMPP, DFHBSS, DFHBSTZ

XMEOUT Parameters: date, time,applid, termid

DFHZC5915 E
date time applid Deletion of node id failed. {The node is still in service. | The system entry is still in service. | The node has a task attached.} Module(modname).
Explanation:

CICS cannot delete node id The reason is identified in the message.

  1. The terminal or session is still in service.
  2. The system entry of this session is still in service.
  3. A task is still attached to this terminal or session.

The module issuing the message is identified as modname.

System action:

CICS continues and does not delete the node.

User response:

Before retrying the deletion or replacement, perform the action which corresponds to the reason given in the message.

  1. Set the node OUT OF SERVICE
  2. Set the system entry OUT OF SERVICE.
  3. Wait for activity to cease for this node.
Start of change
Destination:

CSMT

End of change
Modules:

Start of changeDFHBSMIR, DFHBSTZ, DFHBSTZPEnd of change

Start of changeXMEOUT Parameters:End of changeStart of change End of changeStart of changedate, End of changeStart of changetime,End of changeStart of changeapplid, End of changeStart of changeid, End of changeStart of change{1=The node is still in service., End of changeStart of change2=The system entry is still in service., End of changeStart of change3=The node has a task attached.}, End of changeStart of changemodnameEnd of change

Start of changeDFHZC5916 EEnd of change
Start of changedate time applid Deletion of terminal termid failed. It has pending DFHZCP activityEnd of change
Start of change
Explanation:

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.

End of change
Start of change
System action:

CICS continues.

End of change
Start of change
User response:

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.

End of change
Start of change
Destination:

CSMT

End of change
Modules:

Start of changeDFHBSTZAEnd of change

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

DFHZC5917 E
date time applid Deletion of terminal termid failed. Error message writer still active
Explanation:

CICS cannot delete terminal termid because the error message writer is still active for this terminal.

System action:

CICS continues.

User response:

Put the terminal briefly into service and then take it out of service again, using the CEMT transaction.

Destination:

CSMT

Modules:

DFHBSTZE

XMEOUT Parameters: date, time,applid, termid

DFHZC5918 E
date time applid Deletion of terminal termid Console consname failed. It has pending DFHZCP activity.
Explanation:

The MVS console consname has outstanding activity that prevents its deletion.

System action:

CICS continues.

User response:

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.

Destination:

CSMT

Modules:

DFHBSTZO

XMEOUT Parameters: date, time,applid, termid, consname

DFHZC5919 E
date time applid Deletion of terminal termid failed. CICS logic error
Explanation:

CICS cannot delete terminal termid because of an error in disconnecting remote terminals.

System action:

CICS continues. A system dump is taken with dumpcode ZC5919. Message DFHME0116 is normally produced containing the symptom string for this problem.

User response:

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

Destination:

CSMT

Modules:

DFHBSSZ

XMEOUT Parameters: date, time,applid, termid

DFHZC5920 E
date time applid Install of terminal termid failed. CICS logic error
Explanation:

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.

System action:

CICS continues. A system dump is taken with dumpcode ZC5920. Message DFHME0116 is normally produced containing the symptom string for this problem.

User response:

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

Start of change
Destination:

CSMT

End of change
Modules:

Start of changeDFHBSTZEnd of change

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

DFHZC5921 E
date time applid Install of terminal termid failed. VTAM support not loaded.
Explanation:

CICS failed to install terminal termid because CICS was initialized without VTAM support.

System action:

CICS continues processing.

User response:

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.

Destination:

CSMT

Modules:

DFHBSZZV

XMEOUT Parameters: date, time,applid, termid

DFHZC5923 E
date time applid Install for terminal termid failed. CICS logic error
Explanation:

CICS failed to install terminal termid because the bind-image was invalid.

System action:

CICS continues. A system dump is taken with dumpcode ZC5923. Message DFHME0116 is normally produced containing the symptom string for this problem.

User response:

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

Destination:

CSMT

Modules:

DFHBSZZV

XMEOUT Parameters: date, time,applid, termid

DFHZC5924 E
date time applid Install for terminal termid failed. CICS logic error
Explanation:

CICS failed to install terminal termid because the TCTTE contained no node information block (NIB) descriptor.

System action:

CICS continues. A system dump is taken with dumpcode ZC5924. Message DFHME0116 is normally produced containing the symptom string for this problem.

User response:

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

Destination:

CSMT

Modules:

DFHBSZZV

XMEOUT Parameters: date, time,applid, termid

DFHZC5925 E
date time applid Deletion of connection cccc failed. Its AID-Chains are not empty
Explanation:

CICS did not delete connection cccc because the AID-chains for the remote system cccc are not empty.

System action:

CICS continues.

User response:

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.

Destination:

CSMT

Modules:

DFHBSSA

XMEOUT Parameters: date, time,applid, cccc

DFHZC5926 E
date time applid Install for connection cccc failed. CICS logic error
Explanation:

CICS did not install the connection cccc because DFHZCP received no DATASTREAM operand.

System action:

CICS continues. A system dump is taken with dumpcode ZC5926. Message DFHME0116 is normally produced containing the symptom string for this problem.

User response:

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

Destination:

CSMT

Modules:

DFHBSSZ6

XMEOUT Parameters: date, time,applid, cccc

DFHZC5927 E
date time applid Install for connection cccc failed. CICS logic error
Explanation:

CICS did not install the connection cccc because DFHZCP did not receive a RECORDFORMAT operand.

System action:

CICS continues. A system dump is taken with dumpcode ZC5927. Message DFHME0116 is normally produced containing the symptom string for this problem.

User response:

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

Destination:

CSMT

Modules:

DFHBSSZ6

XMEOUT Parameters: date, time,applid, cccc

DFHZC5930 E
date time applid Remote connection (sysid) could not be deleted because it was in use by number sessions.
Explanation:

When remote connection sysid was being deleted, it was still in use by number of sessions.

System action:

The resource is not deleted. CICS continues.

User response:

Wait until access to this remote connection has quiesced and then retry the deletion.

Destination:

CSMT

Modules:

DFHBSTZ2

XMEOUT Parameters: date, time,applid, sysid, number

DFHZC5931 E
date time applid Install for modename modename failed. Maximum number of APPC sessions would have been exceeded
Explanation:

CICS did not install a SESSIONS definition using MODENAME modename because it would have exceeded the maximum number of permitted sessions.

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

System action:

CICS continues.

User response:

Either wait for the system to become less busy, or delete some APPC sessions.

Start of changeThe system programmer should consider increasing the number of CICS TORs.End of change

Destination:

CSMT

Modules:

DFHBSM61

XMEOUT Parameters: date, time,applid, modename

DFHZC5932 E
date time applid Install for modename modename failed. Connection cccc not found
Explanation:

CICS did not install a SESSIONS definition using MODENAME modename because of an unknown name cccc in the CONNECTION parameter.

System action:

CICS continues.

User response:

Install connection cccc.

Destination:

CSMT

Modules:

DFHBSM62

XMEOUT Parameters: date, time,applid, modename, cccc

DFHZC5933 E
date time applid Install for modename modename failed. Connection cccc is not valid here
Explanation:

CICS did not install a SESSIONS definition using MODENAME modename because the CONNECTION is not valid in this context.

System action:

CICS continues.

User response:

Modify your definition of remote system cccc.

Destination:

CSMT

Modules:

DFHBSM62

XMEOUT Parameters: date, time,applid, modename, cccc

DFHZC5934 E
date time applid Install for modename modename failed. Single-session connection cccc is already in use.
Explanation:

CICS did not install a SESSIONS definition using MODENAME modename because the single-session CONNECTION cccc is already in use.

System action:

CICS continues.

User response:

Modify the definition of cccc.

Destination:

CSMT

Modules:

DFHBSM61, DFHBSM62

XMEOUT Parameters: date, time,applid, modename, cccc

DFHZC5936 E
date time applid Install for modename modename failed. Connection cccc has active modegroup xxxx
Explanation:

CICS has not installed a SESSIONS definition with MODENAME modename because the connection cccc already has an active MODEGROUP, xxxx.

System action:

CICS continues.

User response:

Put the connection briefly into service and then take it out of service again, using the CEMT transaction.

Destination:

CSMT

Modules:

DFHBSM62

XMEOUT Parameters: date, time,applid, modename, cccc, xxxx

DFHZC5937 I
date time applid Deletion of modename modename found another deletion of it in progress
Explanation:

CICS has not deleted a SESSIONS definition with MODENAME modename because the definition is already pending deletion.

System action:

CICS continues.

User response:

Check if a CEDA user was installing the SESSIONS definition.

Destination:

CSMT

Modules:

DFHBSM62

XMEOUT Parameters: date, time,applid, modename

DFHZC5938 E
date time applid Deletion of modename modename failed. Unable to delete session(s)
Explanation:

CICS is unable to delete a SESSIONS definition with MODENAME modename because of one or more errors reported in previous messages.

System action:

CICS continues.

User response:

Refer to any preceding messages for further information and guidance. Correct the reported errors.

Destination:

CSMT

Modules:

DFHBSM61

XMEOUT Parameters: date, time,applid, modename

DFHZC5939 E
date time applid Install for name failed. Duplicate session- or modegroup-name for connection sysid
Explanation:

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.

System action:

CICS continues processing, but the session or modegroup is not installed.

User response:

Change the duplicated session-name or modegroup-name.

Destination:

CSMT

Modules:

DFHBSMIR, DFHBSM62

XMEOUT Parameters: date, time,applid, name, sysid

DFHZC5940 E
date time applid Install for terminal termid failed. Error console cannot be deleted
Explanation:

You have tried to replace the error console, CERR. CICS does not allow this.

System action:

CICS continues with original error console.

User response:

Note this restriction.

Destination:

CSMT

Modules:

DFHZCQDL

XMEOUT Parameters: date, time,applid, termid

DFHZC5941 E
date time applid Install for terminal termid failed. Console consname has a conversation outstanding
Explanation:

CICS was unable to install terminal termid because the console consname has posted an ECB.

System action:

Processing continues.

User response:

Put the terminal briefly into service and then take it out of service again, using the CEMT transaction.

Destination:

CSMT

Modules:

DFHBSTZO

XMEOUT Parameters: date, time,applid, termid, consname

DFHZC5942 E
date time applid Node nodeid was not installed. The addition of key key to table tablename failed. RC=X'return'. Module(modname).
Explanation:

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.

System action:

CICS does not install the definition.

User response:

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.

Start of change
Destination:

CSMT

End of change
Modules:

Start of changeDFHBSS, DFHBSTZ, DFHBSTZS, DFHBSTZZ, DFHBSTZ1, DFHBSTZ2End of change

Start of changeXMEOUT Parameters:End of changeStart of change End of changeStart of changedate, End of changeStart of changetime,End of changeStart of changeapplid, End of changeStart of changenodeid, End of changeStart of changekey, End of changeStart of changetablename, End of changeStart of changeX'End of changeStart of changereturn', End of changeStart of changemodnameEnd of change

DFHZC5943 E
date time applid MRO connection conname could not be deleted because IRC is open.
Explanation:

CICS cannot delete the connection conname because it is an MRO connection and interregion communication (IRC) is open.

System action:

The connection is not deleted.

User response:

Close the IRC definition and retry the Delete or Replace.

Destination:

CSMT

Modules:

DFHBSS

XMEOUT Parameters: date, time,applid, conname

DFHZC5944 E
date time applid Install for type(id) has failed. It would make a loop of connection definitions. Module(modname).
Explanation:

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.

System action:

CICS does not install the definition.

User response:

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.

Destination:

CSMT

Modules:

DFHBSSZI, DFHBSTZ2

XMEOUT Parameters: date, time,applid, type, id, modname

DFHZC5945 E
date time applid Deletion of sessions ssss failed. Connection cccc is defined to IRC
Explanation:

CICS has not deleted the SESSIONS definition, ssss, because the CONNECTION is still defined to IRC.

System action:

CICS continues.

User response:

Issue a CEMT SET IRC CLOSED command.

Destination:

CSMT

Modules:

DFHBSTZR

XMEOUT Parameters: date, time,applid, ssss, cccc

DFHZC5946 E
date time applid Install for sessions ssss failed. Connection cccc is defined to IRC
Explanation:

CICS has not installed the SESSIONS definition, ssss, because the CONNECTION is already defined to IRC.

System action:

CICS continues.

User response:

Issue a CEMT SET IRC CLOSED command.

Destination:

CSMT

Modules:

DFHBSTZR

XMEOUT Parameters: date, time,applid, ssss, cccc

DFHZC5947 E
date time applid Install for sessions ssss failed. CICS logic error
Explanation:

CICS has not installed the SESSIONS definition, ssss, because the CONNECTION name is not specified.

System action:

CICS continues. A system dump is taken with dumpcode ZC5947. Message DFHME0116 is normally produced containing the symptom string for this problem.

User response:

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

Destination:

CSMT

Modules:

DFHBSMIR, DFHBSTZR

XMEOUT Parameters: date, time,applid, ssss

DFHZC5948 E
date time applid Install for sessions ssss failed. Connection cccc is not suitable for IRC
Explanation:

CICS has not installed the SESSIONS definition, ssss, because the CONNECTION specified is not suitable for IRC.

System action:

CICS continues.

User response:

Modify your definition of cccc.

Destination:

CSMT

Modules:

DFHBSTZR

XMEOUT Parameters: date, time,applid, ssss, cccc

DFHZC5949 E
date time applid Install for sessions ssss failed. It is incompatible with connection cccc
Explanation:

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.

System action:

CICS continues.

User response:

Modify your definition of cccc.

Destination:

CSMT

Modules:

DFHBSMIR, DFHBSTZS, DFHBSTZR

XMEOUT Parameters: date, time,applid, ssss, cccc

DFHZC5950 E
date time applid Install for terminal termid failed. Console consname already exists
Explanation:

CICS has not installed the CONSOLE definition termid because the console ID, consname, already exists.

System action:

CICS continues without installing the terminal.

User response:

Use the CEDA transaction to define a different console ID and reinstall the terminal.

Start of change
Destination:

CSMT

End of change
Modules:

Start of changeDFHBSTZOEnd of change

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

DFHZC5951 E
date time applid Deletion of connection ssss failed. Unable to delete sessions
Explanation:

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.

System action:

CICS continues.

User response:

Refer to the preceding message for further information and guidance.

Destination:

CSMT

Modules:

DFHBSSZR, DFHBSSZ6

XMEOUT Parameters: date, time,applid, ssss

DFHZC5952 E
date time applid Deletion of terminal termid failed. It needs to be SET RELEASED
Explanation:

CICS cannot delete terminal termid because of its current state.

System action:

CICS continues.

User response:

Use the CEMT transaction to set terminal termid released and out of service.

Destination:

CSMT

Modules:

DFHBSTZV

XMEOUT Parameters: date, time,applid, termid

DFHZC5953 E
date time applid CICS logic error
Explanation:

An object being installed did not have a bind-image.

System action:

CICS continues. A system dump is taken with dumpcode ZC5953. Message DFHME0116 is normally produced containing the symptom string for this problem.

User response:

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

Destination:

CSMT

Modules:

DFHBSM62

XMEOUT Parameters: date, time,applid

DFHZC5954 E
date time applid Install for resource resource failed. Unable to install sessions component
Explanation:

CICS has failed to install resource resource. Previous message(s) should give the reason for the failure.

System action:

CICS continues.

User response:

Refer to any preceding messages for further information and guidance.

Destination:

CSMT

Modules:

DFHBSTZC

XMEOUT Parameters: date, time,applid, resource

DFHZC5957 E
date time applid Arch. User-Data ID X'xx occurs in bind. CICS logic error
Explanation:

The APPC SESSIONS object being installed is invalid because architected user-data IDs greater than X'02' occur in bind.

System action:

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.

User response:

Destination:

CSMT

Modules:

DFHBSM62

XMEOUT Parameters: date, time,applid, xx

DFHZC5958 E
date time applid Install failed for xxxx. This is the name of the local system which must not be replaced.
Explanation:

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.

System action:

CICS continues, but this terminal or connection is not installed.

User response:

Use the CEDA transaction to correct the terminal or connection name and install the group.

Destination:

CSMT

Modules:

DFHBSSZL

XMEOUT Parameters: date, time,applid, xxxx

DFHZC5961 E
date time applid Deletion of surrogate xxxx failed. CICS logic error
Explanation:

CICS cannot delete a surrogate TCT entry.

System action:

CICS continues. A system dump is taken with dumpcode ZC5961. Message DFHME0116 is normally produced containing the symptom string for this problem.

User response:

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

Destination:

CSMT

Modules:

DFHBSTZ1, DFHBSTZ2

XMEOUT Parameters: date, time,applid, xxxx

DFHZC5962 E
date time applid Install for resource resource failed. Modename parameter not found
Explanation:

CICS has failed to install resource resource because the MODENAME parameter is missing.

System action:

CICS continues.

User response:

Supply the missing parameter.

Destination:

CSMT

Modules:

DFHBSTZS

XMEOUT Parameters: date, time,applid, resource

DFHZC5963 E
date time applid operation RUSIZE xxxx from terminal termid was greater than TYPETERM RUSIZE yyyy.
Explanation:

An autoinstall has been attempted with terminal termid that has a VTAM RECEIVESIZE greater than the corresponding TYPETERM RECEIVESIZE|SENDSIZE.

System action:

CICS continues. The autoinstall is rejected.

User response:

Increase the TYPETERM RECEIVESIZE or the TYPETERM SENDSIZE, OR decrease the RECEIVESIZEs in the VTAM LOGMODE table.

Destination:

CSMT

Modules:

DFHBSZZV

XMEOUT Parameters: date, time,applid, operation, xxxx, termid, yyyy

DFHZC5964 E
date time applid Install for sessions ssss failed. CICS logic error.
Explanation:

CICS has failed to install SESSIONS ssss because the length of the BINDPASSWORD exceeds the limit of 8.

System action:

CICS continues. A system dump is taken with dumpcode ZC5964. Message DFHME0116 is normally produced containing the symptom string for this problem.

User response:

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

Destination:

CSMT

Modules:

DFHBSSZS

XMEOUT Parameters: date, time,applid, ssss

DFHZC5965
date time applid Pool delete for pool poolid failed. Terminal termid was being replaced at the same time.
Explanation:

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.

System action:

CICS continues.

User response:

Once the deletion or modification of the terminal has succeeded, retry the installation.

Destination:

CADL

Modules:

DFHBSMPP

XMEOUT Parameters: date, time,applid, poolid, termid

DFHZC5966 I
date time applid {INSTALL | DELETE | RESTORE} started for resource (termid) (Module name: modname).
Explanation:

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.

System action:

CICS continues.

User response:

None.

Destination:

CADL

Modules:

DFHBSTZ, DFHBSMPP, DFHBSM62, DFHBSS, DFHBSMIR

XMEOUT Parameters: date, time,applid, {1=INSTALL, 2=DELETE,3=RESTORE}, resource, termid,modname

DFHZC5967 E
date time applid Install for modename modename failed. Unable to install sessions
Explanation:

CICS has failed to install a SESSIONS definition using MODENAME modename. Previous message(s) should give the reason for the failure.

System action:

CICS continues.

User response:

Refer to the preceding message for further information and guidance.

Destination:

CSMT

Modules:

DFHBSM61

XMEOUT Parameters: date, time,applid, modename

DFHZC5968 E
date time applid Unable to install LU Services Manager for modename modename
Explanation:

CICS has failed to install a CONNECTION definition for MODEGROUP modename. Previous message(s) should give the reason for the failure.

System action:

CICS continues.

User response:

Refer to any preceding messages for further information and guidance.

Destination:

CSMT

Modules:

DFHBSSZP

XMEOUT Parameters: date, time,applid, modename

DFHZC5969 E
date time applid Deletion of dependent modename(s) failed for connection modename
Explanation:

CICS has failed to replace a CONNECTION definition for MODEGROUP modename. Previous message(s) should give the reason for the failure.

System action:

CICS continues.

User response:

Refer to any preceding messages for further information and guidance.

Destination:

CSMT

Modules:

DFHBSSZS

XMEOUT Parameters: date, time,applid, modename

DFHZC5971 E
date time applid Delete of resource resource failed. CICS logic error
Explanation:

CICS failed to delete resource resource because of an unexpected signon state during the destroy operation.

System action:

CICS continues. A system dump is taken with dumpcode ZC5971. Message DFHME0116 is normally produced containing the symptom string for this problem.

User response:

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

Destination:

CSMT

Modules:

DFHBSTS

XMEOUT Parameters: date, time,applid, resource

DFHZC5972 E
date time applid Delete of resource resource failed. It is still signed on
Explanation:

CICS failed to delete a TERMINAL or SESSIONS resource resource because a terminal or session is still signed on.

System action:

CICS continues.

User response:

Run the signoff transaction CESF and retry.

Destination:

CSMT

Modules:

DFHBSTS

XMEOUT Parameters: date, time,applid, resource

DFHZC5973 E
date time applid Install for sessions ssss failed. Max session-count reached for modename modename
Explanation:

CICS failed to delete a SESSIONS definition ssss because the maximum session-count was reached for MODENAME modename.

System action:

CICS continues.

User response:

Delete some sessions in modename, or redefine modename with a higher maximum session-count.

Destination:

CSMT

Modules:

DFHBSTZS

XMEOUT Parameters: date, time,applid, ssss, modename

DFHZC5974 E
date time applid Deletion of pool pppp failed. Unable to delete pool entries
Explanation:

CICS failed to delete a POOL pppp. Previous messages(s) should explain the cause of this failure.

System action:

CICS continues.

User response:

Refer to any previous messages for further guidance and information.

Destination:

CSMT

Modules:

DFHBSMPP

XMEOUT Parameters: date, time,applid, pppp

DFHZC5975 E
date time applid Install for resource pppp failed. CICS logic error
Explanation:

CICS failed to install the POOL definition pppp because the required POOLID parameter was missing. This is a CICS logic error (probably in DFHTRZPP).

System action:

CICS continues. A system dump is taken with dumpcode ZC5975. Message DFHME0116 is normally produced containing the symptom string for this problem.

User response:

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

Destination:

CSMT

Modules:

DFHBSMPP, DFHBSTZP

XMEOUT Parameters: date, time,applid, pppp

DFHZC5976 E
date time applid CICS logic error
Explanation:

CICS failed to install a POOL definition because the required POOLCNT parameter was missing. This is a CICS logic error (probably in DFHTRZPP).

System action:

CICS continues. A system dump is taken with dumpcode ZC5976. Message DFHME0116 is normally produced containing the symptom string for this problem.

User response:

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

Destination:

CSMT

Modules:

DFHBSMPP

XMEOUT Parameters: date, time,applid

DFHZC5977 E
date time applid Failure building pool entries
Explanation:

CICS failed to install a POOL definition, because of a failure in building pool entries. Previous messages should explain the cause of this failure.

System action:

CICS continues.

User response:

Refer to any previous messages for further information and guidance.

Destination:

CSMT

Modules:

DFHBSMPP

XMEOUT Parameters: date, time,applid

DFHZC5978 E
date time applid Unable to replace pool pppp
Explanation:

CICS failed in an attempt to install or delete a POOL definition. Previous messages should explain the cause of this failure.

System action:

CICS continues.

User response:

Refer to previous messages for further information and guidance.

Start of change
Destination:

CSMT

End of change
Modules:

Start of changeDFHBSMPP, DFHBSTZPEnd of change

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

DFHZC5979 E
date time applid Deletion of pool pppp failed. It still has session termid
Explanation:

CICS has failed to delete pool pppp because the pool still has an active session for terminal termid.

System action:

CICS continues.

User response:

Put the terminal out of service (using the CEMT transaction) and retry.

Destination:

CSMT

Modules:

DFHBSTZP

XMEOUT Parameters: date, time,applid, pppp, termid

DFHZC5980 E
date time applid Resource resource is in use by task taskid Transaction tranid
Explanation:

The resource resource is in use. taskid is the task number, and tranid is the transaction ID.

System action:

CICS continues.

User response:

Wait for the termination of task taskid, and retry the operation.

Start of change
Destination:

CSMT

End of change
Modules:

Start of changeDFHBSS, DFHBSSZ, DFHBSTZ, DFHBSTZ1, DFHBSTZ2, DFHBSTZS, DFHBSTZZ, DFHBST2VEnd of change

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

DFHZC5981 E
date time applid Pool pppp not found
Explanation:

CICS has failed to install a resource because POOL pppp does not exist. Previous messages should explain the cause of this failure.

System action:

CICS continues.

User response:

Refer to the previous messages for further information and guidance.

Destination:

CSMT

Modules:

DFHBSTZP

XMEOUT Parameters: date, time,applid, pppp

DFHZC5982 E
date time applid Deletion of pool pppp failed. Pool entry is in use for termid
Explanation:

CICS has failed to delete POOL pppp because the pool still has an entry in use for terminal termid.

System action:

CICS continues.

User response:

Put the terminal out of service (using the CEMT transaction) and retry.

Destination:

CSMT

Modules:

DFHBSMPP

XMEOUT Parameters: date, time,applid, pppp, termid

DFHZC5983 E
date time applid Unable to replace resource
Explanation:

CICS failed to install resource resource either because it already exists, or for reasons explained in previous messages.

Possible causes are:

System action:

CICS continues.

User response:

Refer to previous messages for further information and guidance.

If no previous messages were issued, check your terminal identifiers.

Start of change
Destination:

CSMT

End of change
Modules:

Start of changeDFHBSS, DFHBSTZ, DFHBSTZ1, DFHBSTZ2End of change

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

DFHZC5984 E
date time applid The installation or deletion of restype1 resname1 has failed. Task taskname taskid is updating related system definition sysname. Module modname.
Explanation:

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.

System action:

CICS continues but reverses the effects of the installation or deletion.

User response:

Wait until the other task has completed then retry the action.

Destination:

CSMT

Modules:

DFHBSTZ, DFHBSTZ1, DFHBSTZ2, DFHBSSZI

XMEOUT Parameters: date, time,applid, restype1, resname1, taskname, taskid, sysname, modname

DFHZC5985 E
date time applid Install for resource resource failed. Unable to install connection component
Explanation:

CICS has failed to install resource resource. Previous message(s) should give the reason for the failure.

System action:

CICS continues.

User response:

Refer to previous messages for further information and guidance.

Destination:

CSMT

Modules:

DFHBSTZC

XMEOUT Parameters: date, time,applid, resource

DFHZC5986 E
date time applid CICS logic error
Explanation:

Either the warm keypoint program (DFHWKP), or the query transaction (DFHQRY), made an invalid request which could not be implemented.

System action:

CICS continues. A system dump is taken with dumpcode ZC5986. Message DFHME0116 is normally produced containing the symptom string for this problem.

User response:

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

Destination:

CSMT

Modules:

DFHZCQCH

XMEOUT Parameters: date, time,applid

DFHZC5987 E
date time applid The install or delete of restype1 resname1 has failed. Task taskname taskid is changing a definition which uses the restype2 resname2. Module modname .
Explanation:

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.

System action:

CICS continues but reverses this install or delete.

User response:

Wait until the other task has completed and then retry the action.

Destination:

CSMT

Modules:

DFHBSS, DFHBSTZ, DFHBSTZS, DFHBSTZV, DFHBSTZZ, DFHBSTZ1, DFHBSTZ2, DFHBSMPP, DFHBSTZP

XMEOUT Parameters: date, time,applid, restype1, resname1, taskname, taskid, restype2, resname2, modname

DFHZC5988 E
date time applid Install for resource resource failed. VTAM support not generated
Explanation:

CICS failed to install resource resource because CICS was initialized without VTAM support.

System action:

CICS continues.

User response:

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.

Destination:

CSMT

Modules:

DFHBSSZS, DFHBSSZ6, DFHBSTZV

XMEOUT Parameters: date, time,applid, resource

DFHZC5989 E
date time applid Deletion of resource resource failed. Remote deletion in connection cccc failed
Explanation:

CICS failed to delete resource resource because a remote delete in system cccc failed.

Previous messages should explain the cause of this failure.

System action:

CICS continues.

User response:

Refer to the previous message for further information and guidance.

Destination:

CSMT

Modules:

DFHBSTZ1, DFHBSTZ2

XMEOUT Parameters: date, time,applid, resource, cccc

DFHZC5990 E
date time applid CICS logic error
Explanation:

CICS rejected an INSTALL or DELETE request because it does not recognize the request code.

System action:

CICS continues. A system dump is taken with dumpcode ZC5990. Message DFHME0116 is normally produced containing the symptom string for this problem.

User response:

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

Destination:

CSMT

Modules:

DFHZCQ00

XMEOUT Parameters: date, time,applid

DFHZC5991 E
date time applid CICS logic error
Explanation:

CICS rejected a VALIDATE BIND request because no BIND was supplied.

System action:

CICS continues. A system dump is taken with dumpcode ZC5991. Message DFHME0116 is normally produced containing the symptom string for this problem.

User response:

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

Destination:

CSMT

Modules:

DFHZCQ00

XMEOUT Parameters: date, time,applid

DFHZC5992 E
date time applid Resource Types Table does not support recovery record
Explanation:

CICS rejected RESTORE request because the resource types table (DFHZCQRT) in DFHZCQ is incompatible with the recovery record from the log or CICS catalog.

System action:

CICS continues. A system dump is taken with dumpcode ZC5992. Message DFHME0116 is normally produced containing the symptom string for this problem.

User response:

CICS is unable to warm start correctly. You should therefore shut CICS down and perform a cold or initial start.

Destination:

CSMT

Modules:

DFHZCQRS

XMEOUT Parameters: date, time,applid

DFHZC5993 E
date time applid CICS logic error
Explanation:

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.

System action:

CICS continues. A system dump is taken with dumpcode ZC5993. Message DFHME0116 is normally produced containing the symptom string for this problem.

User response:

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

Destination:

CSMT

Modules:

DFHZCQRS

XMEOUT Parameters: date, time,applid

DFHZC5994 E
date time applid CICS logic error
Explanation:

CICS rejected a RESTORE request because no recovery record was passed.

System action:

CICS continues. A system dump is taken with dumpcode ZC5994. Message DFHME0116 is normally produced containing the symptom string for this problem.

User response:

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

Destination:

CSMT

Modules:

DFHZCQRS

XMEOUT Parameters: date, time,applid

DFHZC5995 E
date time applid CICS logic error. Resource Type Code xxxx Subtype yyyy not recognized with associated bind image
Explanation:

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

System action:

CICS continues. A system dump is taken with dumpcode ZC5995. Message DFHME0116 is normally produced containing the symptom string for this problem.

User response:

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

Destination:

CSMT

Modules:

DFHZCQIS

XMEOUT Parameters: date, time,applid, xxxx, yyyy

DFHZC5996 E
date time applid CICS logic error
Explanation:

CICS has rejected an INSTALL request because the resource type code in the request is zero.

System action:

CICS continues. A system dump is taken with dumpcode ZC5996. Message DFHME0116 is normally produced containing the symptom string for this problem.

User response:

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

Destination:

CSMT

Modules:

DFHZCQIS

XMEOUT Parameters: date, time,applid

DFHZC5997 E
date time applid CICS logic error
Explanation:

CICS has rejected an INQUIRE request because no TCT entry was passed.

System action:

CICS continues. A system dump is taken with dumpcode ZC5997. Message DFHME0116 is normally produced containing the symptom string for this problem.

User response:

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

Destination:

CSMT

Modules:

DFHZCQIQ

XMEOUT Parameters: date, time,applid

DFHZC5998 E
date time applid Install specified a resource that cannot be replaced
Explanation:

CICS rejected a DELETE request because the entry passed is of a type that cannot be deleted, for example, a non-VTAM terminal.

System action:

CICS continues.

User response:

The failing delete/replace was necessitated by an INSTALL request. Correct the resource type in that request.

Destination:

CSMT

Modules:

DFHZCQCH, DFHZCQDL

XMEOUT Parameters: date, time,applid

DFHZC5999 E
date time applid CICS logic error.
Explanation:

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.

System action:

CICS continues. A system dump is taken with dumpcode ZC5999. Message DFHME0116 is normally produced containing the symptom string for this problem.

User response:

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

Destination:

CSMT

Modules:

DFHZCQCH, DFHZCQDL

XMEOUT Parameters: date, time,applid

DFHZC6201 E
applid CICS table builder services has detected a severe error in module modname code X'code'.
Explanation:

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.

System action:

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

User response:

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.

Destination:

Console

Modules:

DFHTBSB, DFHTBSD, DFHTBSBP, DFHTBSDP, DFHTBSL, DFHTBSLP, DFHTBSS

XMEOUT Parameters: applid, modname,X'code'

DFHZC6202 E
date time applid Pattern pattern not valid for builder
Explanation:

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.

System action:

CICS rejects the request. A system dump is taken with dumpcode ZC6202. Message DFHME0116 is normally produced containing the symptom string for this problem.

User response:

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

Destination:

CSMT

Modules:

DFHTBSB, DFHTBSL, DFHTBSQ, DFHTBSR

XMEOUT Parameters: date, time,applid, pattern

DFHZC6204 E
date time applid Illegal subpattern definition pattern
Explanation:

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.

System action:

CICS rejects the request. A system dump is taken with dumpcode ZC6204. Message DFHME0116 is normally produced containing the symptom string for this problem.

User response:

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

Destination:

CSMT

Modules:

DFHTBSBP, DFHTBSDP

XMEOUT Parameters: date, time,applid, pattern

DFHZC6205 E
date time applid Illegal subpattern definition pattern
Explanation:

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.

System action:

CICS rejects the request. A system dump is taken with dumpcode ZC6205. Message DFHME0116 is normally produced containing the symptom string for this problem.

User response:

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

Destination:

CSMT

Modules:

DFHTBSBP, DFHTBSDP

XMEOUT Parameters: date, time,applid, pattern

DFHZC6206 E
date time applid Pattern pattern not valid for destroy
Explanation:

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.

System action:

CICS rejects the request. A system dump is taken with dumpcode ZC6206. Message DFHME0116 is normally produced containing the symptom string for this problem.

User response:

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

Destination:

CSMT

Modules:

DFHTBSD

XMEOUT Parameters: date, time,applid, pattern

DFHZC6207 E
date time applid Catalog key too long or zero. Pattern pattern
Explanation:

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.

System action:

CICS rejects the request. A system dump is taken with dumpcode ZC6207. Message DFHME0116 is normally produced containing the symptom string for this problem.

User response:

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

Destination:

CSMT

Modules:

DFHTBSBP, DFHTBSDP, DFHTBSL

XMEOUT Parameters: date, time,applid, pattern

DFHZC6208 E
date time applid CICS table builder services has detected a severe error in module modname, code(X'code'.
Explanation:

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.

System action:

CICS rejects the request. It has already issued message DFHZC6201, written an exception trace record identified by code, and taken a dump.

User response:

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.

Destination:

CSMT

Modules:

DFHTBSB, DFHTBSD, DFHTBSBP, DFHTBSDP, DFHTBSL, DFHTBSLP, DFHTBSS

XMEOUT Parameters: date, time,applid, modname, X'code'

DFHZC6209 E
date time applid Invalid ZC catalog request code xxxx
Explanation:

While executing a request, CICS table builder services has detected that the code, xxxx, for a catalog request is invalid.

System action:

CICS rejects the request. A system dump is taken with dumpcode ZC6209. Message DFHME0116 is normally produced containing the symptom string for this problem.

User response:

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

Destination:

CSMT

Modules:

DFHTBSL

XMEOUT Parameters: date, time,applid, xxxx

DFHZC6210 E
date time applid Table builder could not obtain storage for control block code X'code', module modname.
Explanation:

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.

System action:

CICS rejects the request. It has already written an exception trace record identified by code.

User response:

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.

Destination:

CSMT

Modules:

DFHTBSB, DFHTBSD, DFHTBSL, DFHTBSBP, DFHTBSDP, DFHTBSLP, DFHTBSS

XMEOUT Parameters: date, time,applid, X'code', modname

DFHZC6212 E
date time applid Level mismatch with catalog record. DFHBS xxx
Explanation:

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.

System action:

CICS rejects the request.

User response:

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:

Destination:

CSMT

Modules:

DFHTBSR, DFHTBSRP

XMEOUT Parameters: date, time,applid, xxx

DFHZC6213 E
date time applid Recovery record abandoned. Key is key
Explanation:

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

System action:

See the previously issued message for the cause of the problem, and follow the recommended user action.

Destination:

CSMT

Modules:

DFHTBSR

XMEOUT Parameters: date, time,applid, key

DFHZC6214 E
date time applid Unable to obtain recovery record storage
Explanation:

While processing a CATALOG request, CICS Table Builder Services could not obtain recovery record storage.

System action:

CICS rejects the request.

User response:

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.

Destination:

CSMT

Modules:

DFHTBSLP

XMEOUT Parameters: date, time,applid

DFHZC6216 E
date time applid Install for restype1 (resname1) failed and caused the backout of the whole set of RDO resources for restype2 (resname2).
Explanation:

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.

System action:

CICS backs out the installation of the set of associated RDO definitions and continues without them.

User response:

Correct the reason for the failure of the definition, identified by previous DFHZXnnnn messages, and then retry the install.

Destination:

CSMT

Modules:

DFHTBSB

XMEOUT Parameters: date, time,applid, restype1, resname1, restype2, resname2

DFHZC6301 E
date time applid Install for tttt failed. Duplicate netname netname for resource rrrr found.
Explanation:

A resource tttt was being installed but was found to have the same network name netname as resource rrrr.

System action:

The resource is not installed, CICS continues.

User response:

If you want the definitions to be installed, use CEDA to correct the network name and reinstall the definition.

Destination:

CSMT

Modules:

DFHBSTZV

XMEOUT Parameters: date, time,applid, tttt, netname, rrrr

DFHZC6302 E
date time applid Install for connection cccc failed. Duplicate netname netname for resource rrrr found.
Explanation:

A connection cccc was being installed but was found to have the same network name netname as resource rrrr.

System action:

The resource is not installed, CICS continues.

User response:

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.

Destination:

CSMT

Modules:

DFHBSS

XMEOUT Parameters: date, time,applid, cccc, netname, rrrr

DFHZC6303 E
date time applid Install for tttt failed. Duplicate netname netname found.
Explanation:

A resource tttt was being installed but was found to have a duplicate network name netname.

This message occurs:

System action:

The resource is not installed; CICS continues.

User response:

If you want the definitions to be installed, use CEDA to correct the network name and then reinstall the definition.

Destination:

CSMT

Modules:

DFHBSTZV

XMEOUT Parameters: date, time,applid, tttt, netname

DFHZC6304 W
date time applid Deletion of remote terminal termid failed because it is in use by another transaction.
Explanation:

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.

System action:

The remote terminal can be reused. CICS continues.

User response:

This situation usually occurs because the remote CICS is under stress. Consider allocating more resources. For example, you might need to allocate more storage.

Destination:

CSMT

Modules:

DFHBSTZ

XMEOUT Parameters: date, time,applid, termid

DFHZC6305 E
date time applid Install for EXCI generic connection cccc failed. Duplicate EXCI generic connection rrrr found.
Explanation:

A connection cccc specifying protocol(exci) and conntype(generic) was being installed but an existing EXCI generic connection rrrr was found.

System action:

The resource is not installed. CICS continues.

User response:

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.

Destination:

CSMT

Modules:

DFHBSS

XMEOUT Parameters: date, time,applid, cccc, rrrr

DFHZC6307 E
date time applid Install for connection cccc failed. Netname netname is the same as the generic resource name.
Explanation:

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.

System action:

The resource is not installed, CICS continues.

User response:

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.

Destination:

CSMT

Modules:

DFHBSS

XMEOUT Parameters: date, time,applid, cccc, netname

DFHZC6308 E
date time applid Restore for connection cccc failed. Netname netname is the same as the generic resource name.
Explanation:

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.

System action:

Processing continues. The resource is not installed.

User response:

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.

Destination:

CSMT

Modules:

DFHBSS

XMEOUT Parameters: date, time,applid, cccc, netname

DFHZC6315 E
date time applid User userid is not authorized to install terminal tttt with preset security.
Explanation:

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.

System action:

Resource security violation messages are logged to the CSCS transient data queue and to the system console. The resource is not installed. CICS continues.

User response:

In order to install this resource, do one of the following:

Destination:

CSMT

Modules:

DFHBSTS

XMEOUT Parameters: date, time,applid, userid, tttt

DFHZC6330 E
date time applid Install for tttt failed. LDCLIST parameter ldclist not found.
Explanation:

A resource tttt was being installed but was found to have an invalid LDCLIST ldclist.

System action:

The resource is not installed, CICS continues.

User response:

If you want the definition to be installed, use the DFHTCT TYPE=LDCLIST macro to define the listname.

Destination:

CSMT

Modules:

DFHBSTBL

XMEOUT Parameters: date, time,applid, tttt, ldclist

DFHZC6331 E
date time applid Install for connection tttt failed. Non-VTAM terminal with same name already exists.
Explanation:

A connection tttt was being installed but a non-VTAM terminal with the same name already exists.

System action:

The resource is not installed; CICS continues.

User response:

Change the name of the connection and reinstall.

Destination:

CSMT

Modules:

DFHBSS

XMEOUT Parameters: date, time,applid, tttt

DFHZC6332 E
date time applid Install for terminal tttt failed. Non-VTAM terminal with same name already exists.
Explanation:

A terminal tttt was being installed but a non-VTAM terminal with the same name already exists.

System action:

The resource is not installed; CICS continues.

User response:

Change the name of the terminal and reinstall.

Destination:

CSMT

Modules:

DFHBSTZ

XMEOUT Parameters: date, time,applid, tttt

DFHZC6333 E
date time applid INSTALL for modename modename failed. Zero sessions specified
Explanation:

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.

System action:

The install fails, but CICS continues.

User response:

Find the offending builder parameter set and set ZC_MAXSESS_1 to a minimum value of 1.

Start of change
Destination:

CSMT

End of change
Modules:

Start of changeDFHBSM61End of change

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

DFHZC6334 E
date time applid Install for connection tttt failed. A session with the same name already exists.
Explanation:

A connection tttt was being installed but a session with the same name already exists.

System action:

The resource is not installed; CICS continues.

User response:

Change the name of the connection and reinstall.

Destination:

CSMT

Modules:

DFHBSS

XMEOUT Parameters: date, time,applid, tttt

DFHZC6340 E
date time applid CICS has detected an error in delete processing for termid. Module name: modname.
Explanation:

CICS has found terminal input output areas (TIOAs) chained to a TCTTE during deletion of a terminal. This is a CICS logic error.

System action:

A system dump is taken, the TCTTE is deleted and CICS continues. Message DFHME0116 is normally produced containing the symptom string for this problem.

User response:

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:

Destination:

CADL

Modules:

DFHBST

XMEOUT Parameters: date, time,applid, termid, modname

DFHZC6341 E
date time applid Loop or ABEND has been detected in inmodule by module bymodule.
Explanation:

CICS has previously detected a loop or abend. Module bymodule called module inmodule which looped or abended.

System action:

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.

User response:

See the associated message for more guidance.

Start of change
Destination:

CADL

End of change
Modules:

Start of changeDFHBSM61 DFHBSTZS, DFHBSTZREnd of change

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

DFHZC6350 I
date time applid The type session name BITMAP was corrupt and has been rebuilt. Error code: AP FB05.
Explanation:

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 ‘>’.

System action:

A dump is taken with dumpcode ZC6350. Trace point ID AP X'FB05' is produced. The install continues. CICS continues.

User response:

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.

Destination:

CSMT

Modules:

DFHZGBM

XMEOUT Parameters: date, time,applid, type

Start of changeDFHZC6360 WEnd of change
Start of changedate time applid A GETMAIN failed to obtain storage for a message set.End of change
Start of change
Explanation:

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.

End of change
Start of change
System action:

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.

End of change
Start of change
User response:

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.

End of change
Start of change
Destination:

CSMT

End of change
Modules:

Start of changeDFHBSTS, DFHBSTZO, DFHZATA2End of change

Start of changeXMEOUT Parameters:End of changeStart of change End of changeStart of changedate, End of changeStart of changetime,End of changeStart of changeapplidEnd of change

Start of changeDFHZC6361 EEnd of change
Start of changedate time applid {Install | Signon} for {netname | console |terminal }portname with userid userid failed because the preset userid is invalid.End of change
Start of change
Explanation:

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

End of change
Start of change
System action:

CICS continues.

End of change
Start of change
User response:

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.

End of change
Start of change
Destination:

CSMT

End of change
Modules:

Start of changeDFHBSTS, DFHBSTZOEnd of change

Start of changeXMEOUT Parameters:End of changeStart of change End of changeStart of changedate, End of changeStart of changetime,End of changeStart of changeapplid, End of changeStart of change{1=Install, End of changeStart of change2=Signon}, End of changeStart of change{1=netname , End of changeStart of change2=console , End of changeStart of change3=terminal }, End of changeStart of changeportname, End of changeStart of changeuseridEnd of change

Start of changeDFHZC6362 EEnd of change
Start of changedate time applid {Install | Signon} for {netname | console |terminal }portname with userid userid failed because the preset userid has been revoked.End of change
Start of change
Explanation:

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

End of change
Start of change
System action:

CICS continues.

End of change
Start of change
User response:

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.

End of change
Start of change
Destination:

CSMT

End of change
Modules:

Start of changeDFHBSTS, DFHBSTZOEnd of change

Start of changeXMEOUT Parameters:End of changeStart of change End of changeStart of changedate, End of changeStart of changetime,End of changeStart of changeapplid, End of changeStart of change{1=Install, End of changeStart of change2=Signon}, End of changeStart of change{1=netname , End of changeStart of change2=console , End of changeStart of change3=terminal }, End of changeStart of changeportname, End of changeStart of changeuseridEnd of change

Start of changeDFHZC6363 EEnd of change
Start of changedate time applid {Install | Signon} for {netname | console |terminal }portname with userid userid failed because the preset userid's group access has been revoked.End of change
Start of change
Explanation:

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

End of change
Start of change
System action:

CICS continues.

End of change
Start of change
User response:

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.

End of change
Start of change
Destination:

CSMT

End of change
Modules:

Start of changeDFHBSTS, DFHBSTZOEnd of change

Start of changeXMEOUT Parameters:End of changeStart of change End of changeStart of changedate, End of changeStart of changetime,End of changeStart of changeapplid, End of changeStart of change{1=Install, End of changeStart of change2=Signon}, End of changeStart of change{1=netname , End of changeStart of change2=console , End of changeStart of change3=terminal }, End of changeStart of changeportname, End of changeStart of changeuseridEnd of change

Start of changeDFHZC6364 EEnd of change
Start of changedate time applid {Install | Signon} for {netname | console |terminal }portname with userid userid failed because the external security manager returned an unrecognized response.End of change
Start of change
Explanation:

The resource could not be installed or signed on with preset userid userid because of unexpected return codes from the external security manager (ESM).

End of change
Start of change
System action:

CICS continues. Either message DFHSN1401 or DFHSN1801 is issued.

End of change
Start of change
User response:

See the accompanying message for further guidance. Reinstall the resource definition or try another command from the console when you have corrected the problem.

End of change
Start of change
Destination:

CSMT

End of change
Modules:

Start of changeDFHBSTS, DFHBSTZOEnd of change

Start of changeXMEOUT Parameters:End of changeStart of change End of changeStart of changedate, End of changeStart of changetime,End of changeStart of changeapplid, End of changeStart of change{1=Install, End of changeStart of change2=Signon}, End of changeStart of change{1=netname , End of changeStart of change2=console , End of changeStart of change3=terminal }, End of changeStart of changeportname, End of changeStart of changeuseridEnd of change

Start of changeDFHZC6365 EEnd of change
Start of changedate time applid {Install | Signon} for {netname | console |terminal }portname with userid userid failed because the external security manager is inactive.End of change
Start of change
Explanation:

The resource could not be installed or signed on with preset userid userid because the external security manager (ESM) is no longer active.

End of change
Start of change
System action:

CICS continues.

End of change
Start of change
User response:

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.

End of change
Start of change
Destination:

CSMT

End of change
Modules:

Start of changeDFHBSTS, DFHBSTZOEnd of change

Start of changeXMEOUT Parameters:End of changeStart of change End of changeStart of changedate, End of changeStart of changetime,End of changeStart of changeapplid, End of changeStart of change{1=Install, End of changeStart of change2=Signon}, End of changeStart of change{1=netname , End of changeStart of change2=console , End of changeStart of change3=terminal }, End of changeStart of changeportname, End of changeStart of changeuseridEnd of change

Start of changeDFHZC6366 EEnd of change
Start of changedate time applid {Install | Signon} for {netname | console |terminal }portname with userid userid failed because the userid is not authorized to access this CICS system.End of change
Start of change
Explanation:

The resource could not be installed or signed on with a preset userid because the preset userid is not authorized to use application applid.

End of change
Start of change
System action:

CICS continues.

End of change
Start of change
User response:

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.

End of change
Start of change
Destination:

CSMT

End of change
Modules:

Start of changeDFHBSTS, DFHBSTZOEnd of change

Start of changeXMEOUT Parameters:End of changeStart of change End of changeStart of changedate, End of changeStart of changetime,End of changeStart of changeapplid, End of changeStart of change{1=Install, End of changeStart of change2=Signon}, End of changeStart of change{1=netname , End of changeStart of change2=console , End of changeStart of change3=terminal }, End of changeStart of changeportname, End of changeStart of changeuseridEnd of change

Start of changeDFHZC6367 EEnd of change
Start of changedate time applid {Install | Signon} for {netname | console |terminal }termid with userid userid failed because the SECLABEL check failed.End of change
Start of change
Explanation:

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.

End of change
Start of change
System action:

CICS continues.

End of change
Start of change
User response:

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.

End of change
Start of change
Destination:

CSMT

End of change
Modules:

Start of changeDFHBSTS, DFHBSTZOEnd of change

Start of changeXMEOUT Parameters:End of changeStart of change End of changeStart of changedate, End of changeStart of changetime,End of changeStart of changeapplid, End of changeStart of change{1=Install, End of changeStart of change2=Signon}, End of changeStart of change{1=netname , End of changeStart of change2=console , End of changeStart of change3=terminal }, End of changeStart of changetermid, End of changeStart of changeuseridEnd of change

Start of changeDFHZC6368 EEnd of change
Start of changedate time applid {Install | Signon} for {netname | console | terminal }portname with userid userid failed because the external security manager is quiesced.End of change
Start of change
Explanation:

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.

End of change
Start of change
System action:

CICS continues.

End of change
Start of change
User response:

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.

End of change
Start of change
Destination:

CSMT

End of change
Modules:

Start of changeDFHBSTS, DFHBSTZOEnd of change

Start of changeXMEOUT Parameters:End of changeStart of change End of changeStart of changedate, End of changeStart of changetime,End of changeStart of changeapplid, End of changeStart of change{1=Install, End of changeStart of change2=Signon}, End of changeStart of change{1=netname , End of changeStart of change2=console , End of changeStart of change3= terminal }, End of changeStart of changeportname, End of change Start of changeuseridEnd of change

Start of changeDFHZC6369 EEnd of change
Start of changedate time applid {Install | Signon} for {netname | console |terminal }portname failed because national language langcode is invalid.End of change
Start of change
Explanation:

The resource could not be installed or signed on because the national language langcode specified in the resource definition is not recognized.

End of change
Start of change
System action:

CICS continues.

End of change
Start of change
User response:

Change the national language on the resource definition to a valid value and reinstall the resource definition.

End of change
Start of change
Destination:

CSMT

End of change
Modules:

Start of changeDFHBSTS, DFHBSTZO, DFHZSGNEnd of change

Start of changeXMEOUT Parameters:End of changeStart of change End of changeStart of changedate, End of changeStart of changetime,End of changeStart of changeapplid, End of changeStart of change{1=Install, End of changeStart of change2=Signon}, End of changeStart of change{1=netname , End of changeStart of change2=console , End of changeStart of change3=terminal }, End of changeStart of changeportname, End of change Start of changelangcodeEnd of change

Start of changeDFHZC6370 EEnd of change
Start of changedate time applid {Install | Signon} for {netname | console |terminal }portname failed because national language langcode is unavailable.End of change
Start of change
Explanation:

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.

End of change
Start of change
System action:

CICS continues.

End of change
Start of change
User response:

Change the national language in the resource definition to one that has been initialized. Then reinstall the resource definition.

End of change
Start of change
Destination:

CSMT

End of change
Modules:

Start of changeDFHBSTS, DFHBSTZO, DFHZSGNEnd of change

Start of changeXMEOUT Parameters:End of changeStart of change End of changeStart of changedate, End of changeStart of changetime,End of changeStart of changeapplid, End of changeStart of change{1=Install, End of changeStart of change2=Signon}, End of changeStart of change{1=netname , End of changeStart of change2=console , End of changeStart of change3=terminal }, End of changeStart of changeportname, End of change Start of changelangcodeEnd of change

Start of changeDFHZC6371 EEnd of change
Start of changedate time applid {Install | Signon} for {netname | console |terminal }portname with userid userid failed because the userid is not authorized to use this p ortname.End of change
Start of change
Explanation:

The resource could not be installed or signed on with preset userid userid because the specified userid is not authorized to use that resource.

End of change
Start of change
System action:

CICS continues. Either message DFHSN1401 or DFHSN1801 is issued.

End of change
Start of change
User response:

See the accompanying message for further guidance. Reinstall the resource definition or retry the command from the console when you have corrected the problem.

End of change
Start of change
Destination:

CSMT

End of change
Modules:

Start of changeDFHBSTS, DFHBSTZOEnd of change

Start of changeXMEOUT Parameters:End of changeStart of change End of changeStart of changedate, End of changeStart of changetime,End of changeStart of changeapplid, End of changeStart of change{1=Install, End of changeStart of change2=Signon}, End of changeStart of change{1=netname , End of changeStart of change2=console , End of changeStart of change3=terminal }, End of changeStart of changeportname, End of changeStart of changeuseridEnd of change

DFHZC6380 E
date time applid Install for connection cccc failed. Netname netname is the same as the member name of a generic resource connection grcon which is already in use.
Explanation:

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.

System action:

The resource is not installed. CICS continues.

User response:

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.

Destination:

CSMT

Modules:

DFHBSS

XMEOUT Parameters: date, time,applid, cccc, netname, grcon

DFHZC6590 I
date time applid termid tranid Node netname conversation restarted. sense ((instance) Module name: {DFHZXRC})
Explanation:

The node specified has been switched to this system following an XRF takeover.

For the meaning of the sense data, see DFHZCxxxx messages.

System action:

Processing continues.

User response:

None.

Destination:

CSNE

Modules:

DFHZXRC

XMEOUT Parameters: date, time,applid, termid, tranid, netname, sense, instance, {1=DFHZXRC, 2=DFHZXRC, 3=DFHZXRC, 4=DFHZXRC, 5=DFHZXRC}

DFHZC6591 E
date time applid termid tranid Error processing XRF switch command. sense ((instance) Module name: {DFHZXRC})
Explanation:

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.

System action:

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.

User response:

Proceed as for a normal emergency restart.

Destination:

CSNE

Modules:

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}

DFHZC6593 I
date time applid termid tranid Node netname backup session started. sense ((instance) Module name: {DFHZOPX})
Explanation:

Node netname has successfully issued an OPNDST OPTCD=BACKUP command to the connected LU.

For the meaning of the sense data, see DFHZCxxxx messages.

System action:

Processing continues.

User response:

None.

Destination:

CSNE

Modules:

DFHZOPX

XMEOUT Parameters: date, time,applid, termid, tranid, netname, sense, instance, {1=DFHZOPX, 2=DFHZOPX}

DFHZC6594 I
date time applid termid tranid Node netname backup session reset - active session ended. sense ((instance) Module name: {DFHZSCX})
Explanation:

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.

System action:

CLSDST the backup session.

User response:

None.

Destination:

CSNE

Modules:

DFHZSCX

XMEOUT Parameters: date, time,applid, termid, tranid, netname, sense, instance, {1=DFHZSCX}

DFHZC6595 I
date time applid termid tranid Node netname backup session not attempted. sense ((instance) Module name: {DFHZOPN})
Explanation:

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.

System action:

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.

User response:

Do not attempt a backup session.

Rectify error, or downgrade the recovery option specified for this terminal.

Destination:

CSNE

Modules:

DFHZOPN

XMEOUT Parameters: date, time,applid, termid, tranid, netname, sense, instance, {1=DFHZOPN, 2=DFHZOPN, 3=DFHZOPN}

DFHZC6596
applid CICS terminal control program cannot support XRF functions. sense ((instance) Module name: {DFHZSEX | DFHZSLS})
Explanation:

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.

System action:

Processing continues. Processing continues, but no VTAM XRF functions can be supported.

User response:

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.

Destination:

Console

Modules:

DFHZSEX,DFHZSLS

XMEOUT Parameters: applid, sense,instance, {1=DFHZSEX, 2=DFHZSLS}

DFHZC6598
applid VTAM Shutdown in XRF Alternate system. CICS will abend. sense ((instance) Module name: {DFHZTPX})
Explanation:

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.

System action:

The system is abnormally terminated.

User response:

Determine why and how VTAM was shutdown.

Destination:

Console

Modules:

DFHZTPX

XMEOUT Parameters: applid, sense,instance, {1=DFHZTPX}

DFHZC6901 W
date time applid Autoinstall BIND for NETNAME netname is invalid. Internal RC(X'response').
Explanation:

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.

System action:

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.

User response:

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.

Destination:

CADL

Modules:

DFHZATA

XMEOUT Parameters: date, time,applid, netname, X'response'

Start of changeDFHZC6902 EEnd of change
Start of changedate time applid Autoinstall failed because no {terminal | console} models are defined.End of change
Start of change
Explanation:

An attempt was made to autoinstall either a VTAM device or a console; however, there are no appropriate autoinstall models defined.

End of change
Start of change
System action:

CICS processing continues, but the autoinstall logon attempt is rejected.

End of change
Start of change
User response:

Use CEDA to define autoinstall model(s). For further information, refer to the CICS Resource Definition Guide.

End of change
Start of change
Destination:

CADL

End of change
Modules:

Start of changeDFHZATA, DFHZATA2End of change

Start of changeXMEOUT Parameters:End of changeStart of change End of changeStart of changedate, End of changeStart of changetime,End of changeStart of changeapplid, End of changeStart of change{1=terminal, End of changeStart of change2=console}End of change

DFHZC6903 W
date time applid Autoinstall for resource resid, {netname | consolename} id using model model failed.
Explanation:

Start of changeThe connection or terminal or console build process failed.End of change The reason is given in a following DFHZC59xx, DFHZC62xx or DFHZC63xx message referring to the same resid. These messages are followed by message DFHZC6942.

System action:

Processing continues.

User response:

Refer to following messages for further information.

Destination:

CADL

Modules:

Start of changeDFHZATA, DFHZATA2End of change

Start of changeXMEOUT Parameters: date, time,applid, resource, resid, {1=netname, 2=consolename}, id,modelEnd of change

Start of changeDFHZC6904 WEnd of change
Start of changedate time applid Autoinstall for {netname | consolename} id failed. CATA task abended (abend abend).End of change
Start of change
Explanation:

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.

End of change
Start of change
System action:

CICS continues but the resource is not installed.

End of change
Start of change
User response:

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.

End of change
Start of change
Destination:

CADL

End of change
Modules:

Start of changeDFHZATA, DFHZATA2End of change

Start of changeXMEOUT Parameters:End of changeStart of change End of changeStart of changedate, End of changeStart of changetime,End of changeStart of changeapplid, End of changeStart of change{1=netname, End of changeStart of change2=consolename}, End of changeStart of changeid, End of changeStart of changeabendEnd of change

DFHZC6905 W
date time applid Autoinstall delete for resource resid, {netname | consolename} id failed. CATD task abended (abend abend).
Explanation:

Transaction CATD, program DFHZATD was deleting an autoinstalled resource resid, when the task abended with abend abend.

System action:

CICS continues. If the resource still exists, it is reused next time the same TERMID or SYSID is used.

User response:

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.

Destination:

CADL

Modules:

DFHZATD

XMEOUT Parameters: date, time,applid, resource, resid, {1=netname, 2=consolename}, id,abend

DFHZC6906
date time applid Install or delete of remote terminal termid failed. tranid task abended (abend abend).
Explanation:

One of the functions of DFHZATS (transaction CITS, CDTS, CMTS or CFTS) has abended with abend abend.

System action:

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.

User response:

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.

Destination:

CADL

Modules:

DFHZATS

XMEOUT Parameters: date, time,applid, termid, tranid, abend

Start of changeDFHZC6907 IEnd of change
Start of changedate time applid Autoinstall starting for netname netname. Network qualified name is netid.realnet.End of change
Start of change
Explanation:

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.

End of change
Start of change
System action:

CICS continues.

End of change
Start of change
User response:

None. This message is for information only.

End of change
Start of change
Destination:

CADL

End of change
Modules:

Start of changeDFHZATAEnd of change

Start of changeXMEOUT Parameters:End of changeStart of change End of changeStart of changedate, End of changeStart of changetime,End of changeStart of changeapplid, End of changeStart of changenetname, End of changeStart of changenetid, End of changeStart of changerealnetEnd of change

Start of changeDFHZC6908 IEnd of change
Start of changedate time applid Autoinstall in progress for netname netname. TN3270 IP address is tnaddr.End of change
Start of change
Explanation:

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

End of change
Start of change
System action:

CICS continues.

End of change
Start of change
User response:

None. This message is for information only.

End of change
Start of change
Destination:

CADL

End of change
Modules:

Start of changeDFHZATAEnd of change

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

DFHZC6910 W
date time applid Install for remote terminal termid failed.
Explanation:

An INSTALL for the remote terminal termid has failed. The reason for the failure is specified in associated DFHZC59xx and DFHZC62xx messages.

System action:

DFHZATS terminates abnormally with a CICS transaction dump.

User response:

See the associated messages for further guidance.

Destination:

CADL

Modules:

DFHZATS

XMEOUT Parameters: date, time,applid, termid

DFHZC6911 W
date time applid Delete for remote terminal termid failed.
Explanation:

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.

System action:

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.

User response:

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.

Destination:

CADL

Modules:

DFHZATS

XMEOUT Parameters: date, time,applid, termid

DFHZC6912 I
date time applid Unable to delete remote terminal.
Explanation:

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.

System action:

Processing continues normally.

User response:

See the associated messages for further information.

Destination:

CADL

Modules:

DFHZATS

XMEOUT Parameters: date, time,applid

DFHZC6913 I
date time applid Remote delete of terminal termid failed. Terminal not found.
Explanation:

A remote DELETE has been attempted for a terminal which has already been deleted by another task.

System action:

Processing continues normally.

User response:

None.

Destination:

CADL

Modules:

DFHZATS

XMEOUT Parameters: date, time,applid, termid

DFHZC6914 E
date time applid Autoinstall for resource termid, {netname | consolename} id failed. Bad Return Code (RC = X'retcode' ) from an internal function call.
Explanation:

The TCTTE build process failed due to the failure of an internal function call.

System action:

The terminal autoinstall process fails. CICS processing continues.

User response:

Retry the logon attempt.

Destination:

CADL

Modules:

Start of changeDFHZATA, DFHZATA2End of change

Start of changeXMEOUT Parameters: date, time,applid, termid, {1=netname,2=consolename}, id, X'retcode'End of change

Start of changeDFHZC6915 EEnd of change
Start of changedate time applid Unable to sign off remote terminal termid. Bad Return Code (RC = X'SNUS_RESPONSE' ) from signon domain call.End of change
Start of change
Explanation:

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.

End of change
Start of change
System action:

The terminal sign-off process fails to complete and the terminal user remains signed on. CICS processing continues.

End of change
Start of change
User response:

See the related message produced by the domain that detected the original error.

End of change
Start of change
Destination:

CADL

End of change
Modules:

Start of changeDFHZATSEnd of change

Start of changeXMEOUT Parameters:End of changeStart of change End of changeStart of changedate, End of changeStart of changetime,End of changeStart of changeapplid, End of changeStart of changetermid, End of changeStart of changeX'End of changeStart of changeSNUS_RESPONSEEnd of changeStart of change'End of change

DFHZC6920 E
date time applid APPC autoinstall for NETNAME netname failed. RC x
Explanation:

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.

System action:

CICS continues.

User response:

The appropriate response depends on the return code as follows:

1
The user exit program should be linked with AMODE(31). Ensure that the user exit is linked to the correct AMODE.
2
The user exit program has no PPT entry. Ensure that the PPT entry for the user exit program exists and is valid.
3
The user exit program could not be loaded. Ensure that the user exit program is contained in one of the data sets concatenated in the DFHRPL DD statement and has the correct name.
4
The user exit program has abended. This is a possible error within the user exit program. Check for any abend codes that may have been issued.
5
Loading of the user exit program failed for some other reason. Check the DFHPGLU exit trace entry (PG 0A02) to see why the program manager was unable to load the program.
Destination:

CADL

Modules:

DFHZGAI

XMEOUT Parameters: date, time,applid, netname, x

DFHZC6921 W
date time applid Autoinstall for NETNAME netname has been disallowed by the autoinstall control program. Code X'code'
Explanation:

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.

System action:

The exception trace entry code shows the parameter list for the autoinstall control program. The session is terminated. CICS continues.

User response:

The failure code X'code' is as follows:

X'FA07'
If APPC autoinstall is not supported, use the netname to determine which device is attempting autoinstall.

If APPC autoinstall is supported, examine the autoinstall control program to determine why it has not set the return code to allow the install.

Destination:

CADL

Modules:

DFHZGAI

XMEOUT Parameters: date, time,applid, netname, X'code'

DFHZC6922 E
date time applid Parameter list error during autoinstall for NETNAME netname. Code X'code'
Explanation:

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.

System action:

The exception trace entry code shows the parameter list for the autoinstall control program. The session is terminated. CICS continues.

User response:

The failure code X'code' is one of the following:

X'FA08'
No netname or sysid was supplied for the template. Change the autoinstall control program to supply either the netname or the sysid.
X'FA09'
The sysid for the new connection has invalid characters. It can only contain A-Z a-z 0-9 and £#@ (where £ is X'5B') Redefine the connection name in the autoinstall control program.
X'FA0A'
The sysid for the new connection already exists. Change the autoinstall control program to supply a unique name.
X'FA0B'
CICS is unable to locate the supplied template netname. Change the autoinstall control program to supply the correct template name, or use CEDA to install the template connection.
X'FA0C'
CICS is unable to locate the supplied template sysid. Change the autoinstall control program to supply the correct template sysid or use CEDA to install the template connection.
X'FA0D'
The template is not an APPC connection. Change the autoinstall control program to supply the correct template name, or use CEDA to reinstall the template correctly.
X'FA0E'
The bind indicates that a parallel session connection is required. The template is a single session connection. Change the autoinstall control program to supply the correct template name, or use CEDA to reinstall the template correctly.
X'FA0F'
The bind indicates that a single session connection is required. The template is a parallel session connection. Change the autoinstall control program to supply the correct template name or use CEDA to reinstall the template correctly.
X'FA10'
The modename in the bind does not match the modename in the connection.

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.

X'FA11'
The program that attempted to INQUIRE on the template has detected an error in the template and is unable to create a BPS with which to install the new connection. This problem may be caused by a failure in the initial install of the template. Check the console and CADL log to determine whether the template installed correctly. Also, use CEMT to ensure that the CONNECTION is correct.
X'FA12'
The program that attempted to INQUIRE on a user modegroup for the named template has detected an error in the template and is unable to create a BPS with which to install a user modegroup. This problem may be caused by a failure in the initial install of the template. Check the console and CADL log to determine whether the template installed correctly. Also use CEMT to ensure that the MODEGROUP is correct.
X'FA13'
The template connection has no user modegroup. This problem may be caused by a failure in the initial install of the template. Check the console and the CADL log to determine whether the template installed correctly. Also, use CEMT to ensure that the MODEGROUP is correct.
X'FA14'
The template connection is out of service so this install cannot continue. If the install should have been allowed to continue, put the relevant template connection INSERVICE using CEMT.
X'FA15'
The incoming bind user data does not have a PLUNAME Network Name subfield (id 04). This is required and should have been supplied by the PLU.
X'FA16'
The incoming bind user data does not have a MODENAME Network Name subfield (id 02). This is required and should have been supplied by the PLU.
Destination:

CADL

Modules:

DFHZGAI

XMEOUT Parameters: date, time,applid, netname, X'code'

DFHZC6923 E
date time applid Unacceptable bind parameter during autoinstall for NETNAME netname. Code X'code'
Explanation:

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:

X'FA18'
There was no session instance ID field in the bind user data.
X'FA19'
There was no primary logical unit (PLU) name in the bind user data.
X'FA1A'
The PLU name in the bind user data is the same as the LU name of this CICS.
X'FA1B'
Security information (an encryption seed) was expected, but not present, in the bind user data.
X'FA1C'
Security information (an encryption seed) was found in the bind user data but its length was too high for it to be valid.
X'FA1D'
Security information (an encryption seed) was found in the bind user data when none was expected.
X'FA1E'
The received bind indicated that it was not negotiable. This is not acceptable for an APPC connection.
X'FA1F'
The received bind specified a primary RU size of zero.
X'FA20'
The received bind specified a secondary RU size of zero.
X'FA21'
The received bind contained inconsistent access security indicators.
X'FA22'
Two security information fields (seed and nonce field) were found in the received BIND where only one was expected.
X'FA23'
The received BIND contained a nonce field with an incorrect length.
X'FA24'
The received BIND did not contain a nonce field.
X'FA25'
The received BINDs security mechanisms field length was smaller than the minimum defined by the Architecture.
X'FA26'
The received BINDs security mechanisms field contained an invalid length for the mechanism identifier field.
System action:

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.

User response:

Change the definitions on the connecting LU so that the bind parameters are acceptable to CICS.

Destination:

CADL

Modules:

DFHZGAI

XMEOUT Parameters: date, time,applid, netname, X'code'

Start of changeDFHZC6935 IEnd of change
Start of changedate time applid Autoinstall for restype resid with {netname | consolename} id using model or template model successful.End of change
Start of change
Explanation:

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.

End of change
Start of change
System action:

CICS continues.

End of change
Start of change
User response:

None.

End of change
Start of change
Destination:

CADL

End of change
Modules:

Start of changeDFHZATA, DFHZATA2End of change

Start of changeXMEOUT Parameters:End of changeStart of change End of changeStart of changedate, End of changeStart of changetime,End of changeStart of changeapplid, End of changeStart of changerestype, End of changeStart of changeresid, End of changeStart of change{1=netname, End of changeStart of change2=consolename}, End of changeStart of changeid,End of changeStart of changemodelEnd of change

DFHZC6936 I
date time applid Autoinstall for NETNAME netname, model modelname in MTS control vector not known to CICS.
Explanation:

The VTAM MTS control vector contained a model name modelname not defined to CICS.

System action:

CICS continues. This message is informational.

User response:

There are four possible ways of correcting this problem:

Destination:

CADL

Modules:

DFHZATA

XMEOUT Parameters: date, time,applid, netname, modelname

DFHZC6937 I
date time applid Autoinstall for NETNAME netname, MTS model modelname and bind image mismatch.
Explanation:

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.

System action:

CICS continues.

User response:

There are four possible ways of correcting this problem:

Destination:

CADL

Modules:

DFHZATA

XMEOUT Parameters: date, time,applid, netname, modelname

DFHZC6939 W
date time applid Autoinstall for NETNAME netname, Invalid length nn found in cinit control vector at offset offset
Explanation:

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.

System action:

CICS continues. The logon request is rejected.

User response:

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.

Destination:

CADL

Modules:

DFHZATA

XMEOUT Parameters: date, time,applid, netname, nn, offset

DFHZC6942 W
date time applid Autoinstall for resource resid failed.
Explanation:

An AUTOINSTALL attempt to install resource resid has failed.

System action:

CICS continues.

User response:

For the cause of the failure, look for a previous message containing the same resid.

Destination:

CADL

Modules:

Start of changeDFHZATA, DFHZATA2End of change

Start of changeXMEOUT Parameters: date, time,applid, resource, residEnd of change

DFHZC6943 W
date time applid Autoinstall delete for resource resid, {netname | consolename} id failed.
Explanation:

An AUTOINSTALL attempt to delete resource resid has failed.

System action:

CICS continues.

User response:

For the cause of the failure, look for a previous message containing the same resid.

Destination:

CADL

Modules:

DFHZATD

XMEOUT Parameters: date, time,applid, resource, resid, {1=netname, 2=consolename}, id

DFHZC6944 W
date time applid Autoinstall for {netname | consolename} id failed. RC x
Explanation:

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

System action:

CICS continues.

User response:

Possible causes of the problem and an indication of how to solve them are given in the following list of return code meanings:

Return code
Meaning and solution
1
The user exit program should be linked with AMODE(31). Ensure that the user exit is linked to the correct AMODE.
2
The user exit program has no PPT entry. Ensure that the PPT entry for the user exit program exists and is valid.
3
The user exit program could not be loaded. Ensure that the user exit program is contained in one of the data sets concatenated in the DFHRPL DD statement and has the correct name.
4
The user exit program has abended. This is a possible error within the user exit program. Check for any abend codes that may have been issued.
Destination:

CADL

Modules:

Start of changeDFHZATA, DFHZATA2End of change

Start of changeXMEOUT Parameters: date, time,applid, {1=netname, 2=consolename}, id, xEnd of change

DFHZC6945 W
date time applid Autoinstall delete for {netname | consolename} id failed. RC x
Explanation:

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

System action:

CICS continues.

User response:

Possible causes of the problem and an indication of how to solve them are given in the following list of return code meanings:

Return code
Meaning and solution
1
The user exit program should be linked with AMODE(31). Ensure that the user exit is linked to the correct AMODE.
2
The user exit program has no PPT entry. Ensure that the PPT entry for the user exit program exists and is valid.
3
The user exit program could not be loaded. Ensure that the user exit program is contained in one of the data sets concatenated in the DFHRPL DD statement and has the correct name.
4
The user exit program has abended. This is a possible error within the user exit program. Check for any abend codes that may have been issued.
Destination:

CADL

Modules:

Start of changeDFHZATA, DFHZATA2End of change

Start of changeXMEOUT Parameters: date, time,applid, {1=netname, 2=consolename}, id, xEnd of change

DFHZC6946 W
date time applid Delete user exit for autoinstalled resource resid, {netname | consolename} id failed. RC x.
Explanation:

CICS has deleted the autoinstalled resource resid. The call to the delete user exit program failed for reasons given in return code x.

System action:

CICS continues.

User response:

Possible causes of the problem and an indication of how to solve them are given in the following list of return code meanings:

Return code
Meaning and solution
1
The user exit program should be linked with AMODE(31). Ensure that the user exit is linked to the correct AMODE.
2
The user exit program has no PPT entry. Ensure that the PPT entry for the user exit program exists and is valid.
3
The user exit program could not be loaded. Ensure that the user exit program is contained in one of the data sets concatenated in the DFHRPL DD statement and has the correct name.
4
The user exit program has abended. This is a possible error within the user exit program. Check for any abend codes that may have been issued.
Destination:

CADL

Modules:

DFHZATD

XMEOUT Parameters: date, time,applid, resource, resid, {1=netname, 2=consolename}, id,x

DFHZC6948 W
date time applid Delete for connection sysid, NETNAME netname failed due to CATD initiation failure. Module module.
Explanation:

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:

Start of changeDFHZATREnd of change
Start of changeAfter a CICS restart transaction, DFHZATR was driven to delete autoinstalled connections but CATD failed to initiate.End of change
DFHZCLS
Connection sysid was released and DFHZCLS was attempting to initiate the CATD transaction to delete the connection but CATD failed to initiate.
Start of changeDFHZGCHEnd of change
Start of changeAn attempt was made to delete sysid after a successful CHANGE ENDAFFIN request; however, CATD failed to initiate.End of change
System action:

The connection is left in a released state. CICS continues.

User response:

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.

Destination:

CADL

Modules:

DFHZATR, DFHZCLS, DFHZGCH

XMEOUT Parameters: date, time,applid, sysid, netname, module

DFHZC6950 W
date time applid Autoinstall for terminal termid failed with RC x.
Explanation:

An autoinstall attempt to install terminal termid has failed. The autoinstall program call to the user exit program failed with return code x.

System action:

CICS continues.

User response:

Possible causes of the problem and an indication of how to solve them are as follows:

Return code
Meaning and solution
1
The user exit program is not linked with AMODE(31). Ensure that the user exit is linked to the correct AMODE.
2
The user exit program has no PPT entry. Ensure that the PPT entry for the user exit program exists and is valid.
3
The user exit program could not be loaded. Ensure that the user exit program is contained in one of the data sets concatenated in the DFHRPL DD statement and has the correct name.
4
The user exit program has abended. This is a possible error within the user exit program. Check for any abend codes that may have been issued.
Destination:

CADL

Modules:

DFHZATS

XMEOUT Parameters: date, time,applid, termid, x

DFHZC6951 W
date time applid Autoinstall for terminal termid failed with RC x.
Explanation:

An autoinstall attempt to install terminal termid has failed. The autoinstall program call to the user exit program failed with return code x.

System action:

CICS continues.

User response:

Possible causes of the problem and an indication of how to solve them are as follows:

Return code
Meaning and solution
1
The user exit program is not linked with AMODE(31). Ensure that the user exit is linked to the correct AMODE.
2
The user exit program has no PPT entry. Ensure that the PPT entry for the user exit program exists and is valid.
3
The user exit program could not be loaded. Ensure that the user exit program is contained in one of the data sets concatenated in the DFHRPL DD statement and has the correct name.
4
The user exit program has abended. This is a possible error within the user exit program. Check for any abend codes that may have been issued.
Destination:

CADL

Modules:

DFHZATMD

XMEOUT Parameters: date, time,applid, termid, x

DFHZC6958 W
date time applid Autoinstall for {netname | consolename} id, resource X'termid' failed. {RESOURCE | PRINTER | ALTPRINTER} ID is invalid. RC=n.
Explanation:

Start of changeThe RESOURCE, PRINTER, or ALTPRINTER ID supplied by the AUTOINSTALL exit program is invalid.End of change The return code n can be one of the following:

n
Meaning
1
Invalid blank in column one
2
Invalid imbedded blank
3
Invalid character used.
System action:

CICS continues but does not install the object.

User response:

Change the AUTOINSTALL exit program to create IDs that contain only valid characters. These are specified in the CICS Resource Definition Guide.

Destination:

CADL

Modules:

Start of changeDFHZATA, DFHZATA2End of change

Start of changeXMEOUT Parameters: date, time,applid, {1=netname, 2=consolename}, id, X'termid', {1=RESOURCE, 2=PRINTER, 3=ALTPRINTER}, nEnd of change

DFHZC6966 I
date time applid Autoinstall delete for restype resid with {netname | consolename} id was successful.
Explanation:

CICS has successfully deleted the autoinstalled resource restype resid. Start of changeThe restype can be a terminal, an APPC connection, or a console.End of change

System action:

CICS continues.

User response:

None.

Destination:

CADL

Modules:

DFHZATD

XMEOUT Parameters: date, time,applid, restype, resid, {1=netname, 2=consolename}, id

DFHZC6987 W
date time applid Autoinstall best failure for NETNAME netname was model model.
Explanation:

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:

System action:

CICS continues.

User response:

  1. Determine whether the model model is suitable. If there are several models which have options, such as TRANSECKEYS, then only the first such model is named in the above message. It will be up to the user-program to make the choice, when the logmode table entry is corrected.
  2. Identify the entry in the VTAM logmode table that is being used.
  3. Check that this logmode table entry is not successfully in use with other applications, so that to change it might cause this other use of it to fail.
  4. Amend the logmode table entry by switching the bits corresponding to ‘1’ bits in the mismatch string. That is, if the bit in the VTAM bind image corresponding to the bit position set to ‘1’ in xxxxxxxx... is ‘1’, set it to ‘0’. If it is ‘0’, set it to ‘1’.

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

Destination:

CADL

Modules:

DFHZATA

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

[[ Contents Previous Page | Next Page Index ]]