PM99585: eXtremeIO (XIO) should send a pool ID for all XIO thread pools.

APAR status

• Closed as program error.

Error description

• Queries that originate from the XIOWritePool thread pool
  mistakenly run on the remote XIOPrimaryPool thread pool.
  

Local fix

• NA
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:  Users of the eXtremeIO transport            *
  ****************************************************************
  * PROBLEM DESCRIPTION: Queries that originate from the         *
  *                      XIOWritePool thread pool mistakenly     *
  *                      run on the remote XIOPrimaryPool        *
  *                      thread pool.                            *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  Messages that are sent from the thread pool, XIOWritePool,
  are running on the remote XIOPrimaryPool thread pool instead
  of the expected XIOSecondary thread pool.
  

Problem conclusion

• The thread pool ID is supposed to be included in the eXtremeIO
  header; however, only the primary and secondary worker thread
  pools were including their ID. Because the write thread pool
  did not include its ID, requests were handled on the primary
  worker thread pool.
  

Temporary fix

Comments

APAR Information

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

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

Fix information

• Fixed component name

  WS EXTREME SCAL

• Fixed component ID

  5724X6702

Applicable component levels

• R860 PSY

     UP