PK93069: PAGENT INTERMITTENTLY NOT ISSUING MESSAGE EZZ8452I

APAR status

• Closed as fixed if next.

Error description

• There is a race condition between pagent and stack
  initialization that causes lock destroy and create failures,
  leaving the lock in an undetermined state. It's always a
  possibility that message EZZ8788I will be issued.  This results
  in the remote listen thread being terminated and the EZZ8452I
  message not to display.
  
  Pagent does contain code to restart the remote listen thread
  once the stack has been recycled.  But if there is a problem
  with an earlier mutex destroy, the mutex create that accompanies
  the thread restart will also fail, and this will result in the
  remote listen thread again being terminated and the EZZ8452I
  message to never display.
  
  As a result, pagent is NOT listening for remote TCP PAPI
  connections.  This means one or both of the following services
  are not available, depending on which services are configured:
  
  - accepting connections from remote policy clients
    (ServerConnection statement)
  - accepting connections from the GUI for the policy import
    function (ServicesConnection statement)
  
  KEYWORDS: AT-TLS SERVICES TTLS POLICY REMOTE CLIENT CONNECTIONS
  

Local fix

• If there is automation keying on the EZZ8452I message, there are
  two local fixes:
  
  1)  Change the message automation keys on from EZZ8452I to
  EZZ4250I.
  
  2)  Start the stack earlier than PAGENT.
  

Problem summary

• ****************************************************************
  * USERS AFFECTED: All users of the IBM Communications Server   *
  *                 for z/OS Version 1 Release(s) 10 and 11      *
  *                 IP: Pagent                                   *
  ****************************************************************
  * PROBLEM DESCRIPTION: PAGENT not issuing message EZZ8452I     *
  *                      indicating listen connection establish  *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  There is a race condition between pagent and stack
  initialization that causes lock destroy and create failures,
  leaving the lock in an undetermined state. Eventually pagent
  should be able to recover and if the stack is available the
  EZZ8452I message should be issued when the pagent listen
  connection is established. This recovery was not happening
  correctly.
  
  Circumvention: Start the stack first to avoid the race
  condition.
  +-------------------------------------------------------------+
  + Please check our Communications Server for OS/390 homepages +
  + for common networking tips and fixes.  The URL for these    +
  + homepages can be found in Informational APAR II11334.       +
  +-------------------------------------------------------------+
  

Problem conclusion

Temporary fix

Comments

• This APAR is being closed FIN (Fixed If Next) with concurrence
  from the submitting customer. This means that a fix to this
  APAR is expected to be delivered from IBM in a release (if any)
  to be available within the next 24 months.
  
  This problem will be tracked as Feature F148674
  by Communications Server for z/OS Development.
  
  The solution for this APAR is included in CS for z/OS Version 1
  Release 12.
  

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

• R1A0 PSN

     UP

• R1B0 PSN

     UP