PN88109: SIGIO SIGNAL NOT RECEIVED BY SERVER EVEN THOUGH FCNTL() SPECIFIED F_SETOWN AND CLIENT CONNECT() HAS COMPLETED

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• The server is coded to issue a socket() call
  followed by bind() and listen() calls.  In order to
  receive the SIGIO signal, the server issues a
  fcntl(fd,F_SETOWN,&mypid) call to establish the server's
  process id (mypid) as the recipient of the SIGIO signal.
  Finally, an ioctl(fd,FIOASYNC,1) call is issued in order
  to allow asynchronous I/O interrupts.
   Once these steps are taken by the server, a client issues
  a connect() call to the same socket which should raise the
  SIGIO signal to the server.  However, the server never
  receives the signal.
  

Local fix

• Have the server periodically issue poll() calls.
  

Problem summary

• ****************************************************************
  * USERS AFFECTED: All users of the OE product on MVS TCP/IP    *
  *                 V3R2.                                        *
  ****************************************************************
  * PROBLEM DESCRIPTION: SIGIO signal not received by the        *
  *                      server even though fcntl() specified    *
  *                      f_setown, ioctl() specified FIOASYNC    *
  *                      and client connect() has completed.     *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  SIGIO signal not received by the server even though fcntl()
  specified f_setown, ioctl() specified FIOASYNC and client
  connect() has completed.
  

Problem conclusion

• Checked for SIGIO signal support in TCP/IP and found that the
  SIGIO signal was supported on data transfer but not on a
  connect request. Added code to TCP/IP to generate a SIGIO
  signal on a connect request in the routine
  DoConnectionStateChanged.
  
  Affected Modules:
  EZABB03G TCSOCKRE PASCAL
  

Temporary fix

Comments

APAR Information

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

  PN84155

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

  UN94432

Modules/Macros

• EZABB03G
  

Fix information

• Fixed component name

  TCP/IP V3 MVS

• Fixed component ID

  5655HAL00

Applicable component levels

• R320 PSY UN94432

     UP96/09/02 P F608

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.