PM79308: PAGENT HUNG DURING INITIALIZATION WHEN SPECIFYING SERVICESCONNECTION STATEMENT WITHIN CINET ENVIRONMENT

APAR status

• Closed as fixed if next.

Error description

• PAGENT may be configured within a CINET environment which calls
  for multiple TCPIIMAGE statements to be defined (one for each
  stack).  The ServicesConnection statement may also be coded and
  the stack represented by the second defined TCPIMAGE statement
  may be used as the listening stack via the ImageName parameter.
  Normally, if PAGENT is started before the TCPIP stacks then it
  has the logic to wait for the stacks to initialize in order to
  install the policies.  However, in this case if PAGENT is
  started before the TCPIP stacks are initialized then PAGENT
  will hang and will not take action to install policies once the
  stacks are initialized.
  
  
  Verification Steps:
  
  - PAGENT configuration file looks similar to the following
  where the stack represented by the second TcpImage statement is
  used as the listening stack for the ServicesConnection
  statement.
  **************************************************************
  #
  TcpImage TCPIPA //'TCPIP.PAGENT.PARMS(SAMP0001)' FLUSH NOPURGE
  #
  TcpImage TCPIPB //'TCPIP..PAGENT.PARMS(SAMP0002)' FLUSH NOPURGE
  #
  LogLevel 511
  #
  ServicesConnection
  {
    Port 16311
    ImageName TCPIPB
    Security Basic
  }
  #
  **************************************************************
  
  -  A MODIFY REFRESH command will not resolve the issue
  
  Additional Symptom(s) Search Keyword(s): Policy Agent EDC5112I
  12CA00B6 UpdateMutex
  

Local fix

• Rearrange the order in which the TcpImage statements are
  defined to ensure that the stack coded as the listening stack
  (specified via ImageName parameter) for the Services Connection
  statement is listed first.
  

Problem summary

• ****************************************************************
  * USERS AFFECTED: All users of the IBM Communications Server   *
  *                 for z/OS Version 1 Releases 10, 11, 12,      *
  *                 and 13 IP: Pagent Services                   *
  ****************************************************************
  * PROBLEM DESCRIPTION: PAGENT HUNG DURING INITIALIZATION       *
  *                      WHEN SPECIFYING SERVICESCONNECTION      *
  *                      STATEMENT WITHIN CINET ENVIRONMENT      *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  In this case if PAGENT is started before the TCPIP stacks
  are initialized, and ServicesConnection is specified, then
  PAGENT will hang and will not take action to install
  policies once the stacks are initialized.
  +-------------------------------------------------------------+
  + 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 36 months.
  
  This problem will be tracked as Feature F156172
  by Communications Server for z/OS Development.
  
  The solution for this APAR is included in
  CS for zOS Version 2 Release 1.
  

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

• R1C0 PSY

     UP