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

Explanation

An attempt to establish a session has failed. This can be because a physical path to the device could not be found for one of the following reasons:

  • The device does not exist

  • The device has been defined incorrectly

  • The device has rejected the bind

This imbed is inserted in DFHZC xxxx messages with sense inserts. For the meaning of sense , see message DFHZC2400.

If this is a LU62 or LU61 session and the partner LU has sent sense bytes of X'0835nnnn' where nnnn 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 can mean that the partner LU has failed to autoinstall a connection.

If the VTAM RETURN CODE FEEDBACK is X'1018' then VTAM generic resource is in use but the coupling facility is unavailable.

If instance is 1 with sense code '0805', and the following are true:

  • This system (TOR2) is a member of a generic resource (GR) and the partner (AOR) is not

  • An affinity already exists between another member (TOR1) of the same generic resource (GR) and the AOR

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. DFHZC2411 indicates 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'0835nnnn' (where nnnn is the offset of the NETNAME in the BIND), the partner LU was 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 messages DFHZC2411 and 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.

If instance is 1 with 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 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 the CEMT SET CONNECTION ENDAFFIN, CEMT PERFORM ENDAFFIN or EXEC CICS ENDAFFIN command.

  3. Use a batch program described in 'Writing a batch program to end affinities' in the Getting started with intercommunication.

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 you need to use a HUB as described in 'Using a HUB' in the Getting started with intercommunication 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.

Module

DFHZSYX

XMEOUT parameters/Message inserts

  1. date
  2. time
  3. applid
  4. termid
  5. tranid
  6. sense
  7. instance
  8. Value chosen from the following options:

Destination

CSNE