PI16976: SYSLOGD GENERATES ABEND DUMP, WITH FSUM1223 ERROR 8B/11320000, DURING RESTART COMMAND PROCESSING - FIN REVERSAL OF PI14947

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• This is a FIN Reversal APAR for PI14947. During processing of a
  modify syslogd,restart command, syslogd generates an abend dump
  with the title "SYSLOGD  syslogd abend", along with the message
  FSUM1252 syslogd RECONFIGURATION COMPLETE.  At the same time,
  the error message  "FSUM1223 Error 8B/11320000 was returned
  
  from pthread_mutex_unlock(arcCtlLock(29375650)):  EDC5139I
  Operation not permitted" is found in the syslogd log.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * All users of the Communications Server for z/OS Version 2    *
  * Releases 1: SYSLOGD                                          *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  * SYSLOGD generates abend dump, with FSUM1223 ERROR            *
  * 8B/11320000, during restart command processing.              *
  ****************************************************************
  * RECOMMENDATION:                                              *
  * Apply PTF                                                    *
  ****************************************************************
  Syslogd is processing the sigalrm signal in domark. The customer
  does a restart command at the same time.
  1. Restart thread does a raise SIGHUP to drive the main thread
  2. domark obtains the archive lock on the main thread
  3. The SIGHUP interrupts the domark processing
  4. init starts running on the main thread to process the SIGHUP.
  This routine obtains the archive lock, which returns as lock
  already held-RC_LOCK_BUSY. init continues. At the end of init,
  the archive lock is released. This releases the lock for the
  main thread
  5. domark gets control back. When domark tries to release the
  archive lock, it fails with lock not held. This generates the
  abort error.
  

Problem conclusion

• Syslogd code has been changed to check if the lock was actually
  obtained by the request and remember that. The lock should only
  be released if the thread actually obtained the lock.
  

Temporary fix

Comments

APAR Information

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

  PI16438

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

  UI17613

Modules/Macros

• EZASLOGD
  

Fix information

• Fixed component name

  TCP/IP V3 MVS

• Fixed component ID

  5655HAL00

Applicable component levels

• R210 PSY UI17613

     UP14/07/21 P F407

Fix is available

• Select the PTF appropriate for your component level. You will be required to sign in. Distribution on physical media is not available in all countries.