PM38751: PAGENT FILE REGISTRATION VIA __W_PIOCTL PASSING _IOCC_REGFILEINT FAILURES ARE NOT EXTERNALIZED

APAR status

• Closed as fixed if next.

Error description

• Pagent registers specific Unix files during initialization so
  that when these files are updated Pagent will be notified. If
  this registration process fails, no message is logged on either
  the system console or in the Pagent joblog. Failures are only
  logged in the pagent.log file, so they maybe un-noticed.
  

Local fix

• If these failures do occur, after the TCP/IP stack has
  initialized, either restart pagent completely or issue the
  MODIFY PAGENT,UPDATE command from the console to allow the
  stack to install the policy files.
  

Problem summary

• ****************************************************************
  * USERS AFFECTED: All users of the IBM Communications Server   *
  *                 for z/OS Version 1 Release(s) 11, 12,        *
  *                 and 13 IP: Pagent                            *
  ****************************************************************
  * PROBLEM DESCRIPTION: Pagent file registration failure may    *
  *                      go unnoticed by the customer            *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  Pagent file registration failure may go unnoticed by the
  customer. The error generates a log message in Pagent's
  log file and Pagent continues; however file monitoring
  for that file cannot occur. The addition of a new system
  console message would assist the customer.
  
  Look in Pagent log file for the following message as an
  example:
  
  SYSERR :004: plfm_update_event_register: Error
  Registering file '/tmp/TCPIP.Pagent.tmp' ..........
  
  There is an errno and errno jr associated with the message
  which one can look up to aid in understanding the problem
  and its resolution.
  +-------------------------------------------------------------+
  + 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 F153478
  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

• R1B0 PSN

     UP

• R1C0 PSN

     UP