DFHZC2411 E date time applid termid tranid nodeid attempted invalid logon. sense ((instance) Module name: {DFHZSCX | DFHZBLX | DFHZBLX | DFHZBLX | DFHZBLX | DFHZBLX | DFHZATA | DFHZLGX | DFHZLGX | DFHZLGX | DFHZSCX | | DFHZLGX | DFHZLGX | DFHZLGX | DFHZLGX | DFHZLGX | DFHZLGX | DFHZLGX | DFHZLGX | DFHTFP | DFHZLGX | DFHZSCX | DFHZLGX | DFHZLGX | DFHZSCX | DFHZLGX | DFHZBLX | DFHZBLX | DFHZBLX | DFHZBLX | DFHZBLX | DFHZBLX | DFHZBLX | DFHZBLX | DFHZBLX | DFHZBLX | DFHZLGX | DFHZBLX | DFHZSCX | DFHZBLX})
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:
-
The bind did not contain a modename.
-
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
-
ISC support is not present because ISC=NO specified in the SIT.
- 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
-
An 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.
- 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 if the partner is a member of a generic resource, and this system is not, and an affinity already exists between this system and another member of the same generic resource. See message DFHZC2403, which is issued for the partner's equivalent sessions, for how you correct the situation.
- 37
-
The current session count has exceeded the maximum session count indicated in the mode group entry.
This can be caused by a VTAM LU definition with a duplicate netname. At session initiation time VTAM cannot detect that there may be two Independant Logical Units (ILUs) with the same netname. This can lead to CICS being requested to bind more sessions than specified in the mode group.
- 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.
- 39
-
This 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.
- 40
-
This 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.
- 41
-
A 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.
This imbed is inserted in DFHZC xxxx messages with sense inserts. For the meaning of sense , see message DFHZC2400.
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.
Module
XMEOUT parameters/Message inserts
- date
- time
- applid
- termid
- tranid
- nodeid
- sense
- instance
- Value chosen from the following options:
1=DFHZSCX, 2=DFHZBLX, 3=DFHZBLX, 4=DFHZBLX, 5=DFHZBLX, 6=DFHZBLX, 7=DFHZATA, 8=DFHZLGX, 9=DFHZLGX, 10=DFHZLGX, 11=DFHZSCX, 12= , 13=DFHZLGX, 14=DFHZLGX, 15=DFHZLGX, 16=DFHZLGX, 17=DFHZLGX, 18=DFHZLGX, 19=DFHZLGX, 20=DFHZLGX, 21=DFHTFP, 22=DFHZLGX, 23=DFHZSCX, 24=DFHZLGX, 25=DFHZLGX, 26=DFHZSCX, 27=DFHZLGX, 28=DFHZBLX, 29=DFHZBLX, 30=DFHZBLX, 31=DFHZBLX, 32=DFHZBLX, 33=DFHZBLX, 34=DFHZBLX, 35=DFHZBLX, 36=DFHZBLX, 37=DFHZBLX, 38=DFHZLGX, 39=DFHZBLX, 40=DFHZSCX, 41=DFHZBLX
Destination
CSNE