PQ78898: USE OF SOCKETS API IN NESTED REXX EXECS GETS ESOCKETNOTDEFINED

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• A REXX exec running under ISPF uses the REXX Sockets API.  As a
  part of its processing, it invokes another exec via the ISPF
  SELECT CMD service.  If that exec also performs REXX Sockets API
  calls, After return the calling exec is no longer able to use
  sockets that were open before the call.  The return value from
  any calls trying to use a previously open socket is:
  
     2009 ESOCKETNOTDEFINED Socket not defined
  

Local fix

• If no ISPF services are used by the called exec, use a different
  form of nested invocation (CALL statement, EXEC command,
  implicit command invocation).
  

Problem summary

• ****************************************************************
  * USERS AFFECTED: All users of the IBM Communications Server   *
  *                 for z/OS Version 1 Release 5 IP:             *
  *                 REXX/Sockets.                                *
  ****************************************************************
  * PROBLEM DESCRIPTION: It is possible for users of REXX        *
  *                      Sockets running under ISPF to get a     *
  *                      return code of 2009 ESOCKETNOTDEFINED   *
  *                      if they have a REXX exec that invokes   *
  *                      another REXX exec.                      *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  REXX/Sockets requires that each task use a unique Sockets
  data area. During nested REXX exec calls the pointer to that
  data area is lost when control is returned to the original REXX
  exec.
  +-------------------------------------------------------------+
  + 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

• REXX/Sockets have been modified to use callable Name/Token
  Services to keep track of the pointer to the REXX Sockets data
  area.
  
  * Cross Reference between External and Internal Names
  EZAAE05M (SOCMVS  )  EZAAE05M (SOCMVS  )  EZAAE05M (SOCMVS  )
  

Temporary fix

Comments

APAR Information

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

  PQ76829

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

  UQ80987

Modules/Macros

• EZAAE05M
  

Fix information

• Fixed component name

  TCP/IP V3 MVS

• Fixed component ID

  5655HAL00

Applicable component levels

• R150 PSY UQ80987

     UP03/11/05 P F311

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.