LI78699: CP-CP SESSIONS MAY NOT RECOVER AFTER OUTAGE

Communications Server for Linux, Version 6.4 -- Latest Fixpack

APAR status

• Closed as program error.

Error description

• Communications Server for Windows, Version 6.1.3 & 6.4
  ------------------------------------------------------
  When a network outage occurs and CP-CP sessions have failed,
  they should immediately attempt to recover once the link
  recovers or to activate on an alternate link if one is active.
  Under some conditions, such as the remote host being slow to
  respond, the activation attempts may time out; after a few
  failed attempts, no more attempts will be made. This leaves the
  node without CP-CP sessions, so no other sessions can be
  activated.
  

Local fix

• Stop/restart the node.
  

Problem summary

• USERS AFFECTED: All users.
  
  PROBLEM DESCRIPTION:
  See error description, above.
  
  PROBLEM SUMMARY:
  When a link becomes active, an attempt is made to establish
  CP-CP sessions as follows:
  - timeout in 5 seconds if unsuccessful
  - retry 5 more times
  - wait 30 seconds
  - try to activate CP-CP sessions over each active link in turn,
    starting with the one(s) marked as preferred NN server, with
    6 5-second timeout periods each
  - This last step will continue to occur at 30 second intervals
    until CP-CP sessions are successfully activated.
  
  The problem is that the initial 30-second timer failed to trip,
  so the subsequent retry attempts never occurred.
  

Problem conclusion

• The root cause has been identified and corrected. This problem
  appears to have been introduced by changes made for APAR
  JR26404.
  

Temporary fix

• appn.sys
  

Comments

APAR Information

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

  JR49602

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

Fix information

• Fixed component name

  CS FOR LINUX

• Fixed component ID

  5724I3300

Applicable component levels

• R640 PSY