II06501: STOP DDF HANGS WHEN PARTNER HAS SESSION OUTAGE.

APAR status

• Closed as canceled.

Error description

• 5740XYR00 R220 R230 DB2DDF
  User enters STOP DDF (or STOP DB2 which initiates a stop of
  DDF) but the shutdown of DDF never completes (thus stop DB2
  never completes if DDF shutdown was a result of a DB2
  shutdown).
  DB2 issues message DSNL005I but message DSNL006I is
  never issued.
  DDF did not come down because DB2 called VTAM to negotiate
  session limits (CNOS) to zero but VTAM never returned control
  to DB2. In this case, the partner LU had a session outage
  because the partner was powered off (in this case the partner
  was an OS/2 workstation).
  This is a VTAM problem described by VTAM APAR OY26850.  Please
  see OY26850 for more information.
  ****************************
  Additional symptoms and keywords:
    STOP DDF DB2
    MSGDSNL005I MSGDSNL005 DSNL005I DSNL005
    MSGDSNL006I MSGDSNL006 DSNL006I DSNL006
    shutdown termination hung hang hangs wait waits CNOS
  

Local fix

• The hang apparently occurs because VTAM did not receive a
  response to the CDINIT it sends to the partner.  VTAM waits
  for ever to hear the responce (but the parner is down so it
  cannot respond).  Apparently, a new 'CDINIT TIMEOUT' value
  was introduced in VTAM 3.4 to help control this.
  

Problem summary

Problem conclusion

Temporary fix

Comments

• Closing informational APAR.
  

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

Fix information

Applicable component levels