IBM Support

PI52347: EZASMI TYPE=CANCEL CALL NOT TAKING EFFECT

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • .
    An application is using the EZASMI macro to perform asynchronous
    socket calls (APITYPE=3 on the INITAPI call).  If a CANCEL call
    is used to end a call that is still outstanding, that previous
    call is not terminated.  For ASYNC='ECB' the event associated
    with the cancelled call is not posted, for ASYNC=('EXIT,...) the
    exit routine is not invoked.  Depending how the application is
    designed, this could eventually lead to all tasks in the job in
    WAIT or exhaustion of the MAXSOC specification.
    

Local fix

  • Monitor the affected application, and issue a VARY TCPIP,,DROP
    command for the socket associated with the intended CANCEL call.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * All users of the IBM Communications Server for z/OS Version  *
    * 2 Release 2: EZASMI socket interface                         *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * EZASMI TYPE=CANCEL does not cancel the specified call        *
    ****************************************************************
    * RECOMMENDATION:                                              *
    * Apply PTF                                                    *
    ****************************************************************
    The EZASMI TYPE=CANCEL does not cancel the asynchronous call
    represented by the REQAREA passed on the CALAREA paraemeter.
    The asynchronous call being canceled will not terminate until
    the original call type is satisified.  This can cause the socket
    application to stall waiting on the canceled call to complete.
    The async request information is not being stored correctly in
    the REQAREA on the socket call to be canceled.  This prevents
    the async call from being located which in turn prevents it from
    being canceled.
    

Problem conclusion

  • The EZASMI sockets interface has been amended to correctly save
    the async call information in the callers REQAREA.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PI52347

  • Reported component name

    TCP/IP V3 MVS

  • Reported component ID

    5655HAL00

  • Reported release

    220

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    YesHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2015-11-12

  • Closed date

    2016-01-28

  • Last modified date

    2016-04-05

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

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

    UI34846 UI40054

Modules/Macros

  • EZBSOMIE EZBSOMT1 EZBSOMIV EZBSOMTU EZBSOMSE EZBSOMIA EZBTCFAC
    EZBSOMIF EZBSOMIS
    

Fix information

  • Fixed component name

    TCP/IP V3 MVS

  • Fixed component ID

    5655HAL00

Applicable component levels

  • R220 PSY UI34846

       UP16/03/24 P F603 ¢

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.

[{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG19M","label":"APARs - z\/OS environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"220","Edition":"","Line of Business":{"code":"","label":""}},{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SSCY4DZ","label":"All"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"220","Edition":"","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
05 April 2016