IBM Support

II13257: Z/OS CS V1R4: SC31-8807-01 IP CICS SOCKETS GUIDE TCPIPINFO BOOKAPAR

Subscribe to this APAR

By subscribing, you receive periodic emails alerting you to the status of the APAR, along with a link to the fix after it becomes available. You can track this item individually or track all items by product.

Notify me when this APAR changes.

Notify me when an APAR for this component changes.

 

APAR status

  • INTRAN

Error description

  • ===============================================================
    INFOAPAR for z/OS Communications Server:
    IP CICS
    ===============================================================
    *************************************************************
    Updates to this Informational APAR can be found at:
    
    http://www.ibm.com/support/docview.wss?rs=852&uid=swg21178966
    *************************************************************
    ADDITIONAL SYMPTOMS:  ABEND23E at PLT shutdown 5655hal00
    

Local fix

  • ***********************************************************
    In Chapter 2, "Setting up and configuring CICS TCP/IP," in the
    "Transaction definitions" section, add the following under the
    first Note:
    
       Note: The user ID invoking the EZAO transaction to activate
       or deactivate the IP CICS sockets interface requires the
       UPDATE access to the EXITPROGRAM security class. The user ID
       invoking the EZAC transaction requires the UPDATE access to
       the EXITPROGRAM security class. Failure to have at least the
       UPDATE access to the EXITPROGRAM security class will cause
       the IP CICS Sockets interface and listener to either not
       start when starting or not stop when stopping.
    ****************************************************************
    
    In Chapter 4, "Starting and stopping CICS sockets,"  in the
    "Starting/stopping CICS TCP/IP automatically" section, add the
    following after the "Shutdown (PLTSD)" bullet:
    
       Requirement: If the IP CICS Sockets Interface is started in
       the PLT (started by invoking EZACIC20), then the PLTPIUSR
       user ID also requires the UPDATE access to the EXITPROGRAM
       security class. Failure to have at least the UPDATE access to
       the EXITPROGRAM security class causes the IP CICS Sockets
       Interface and Listener to not start when starting or not stop
      when stopping. Message EZY1350E is issued and the IP CICS
       Sockets Interface does not start.
    ****************************************************************
    
    In Chapter 5,  "Writing your own Listener," in the  "Using IBM's
    environmental support" section, make the following changes:
    ************
    Change the following text:
    
    Obtain address of the GWA. This can be done using the following
    CICS command:
    
      EXEC  CICS EXTRACT EXIT PROGRAM(EZACIC01) GASET(ptr)
    GALEN(len)
    
    where ptr is a register and len is a halfword binary variable.
    The address of the GWAus returned in ptr and the length of the
    GWA is returned in len.
    
    To:
    
    Obtain address of the GWA. This can be done using the following
    CICS command:
    
       EXEC  CICS EXTRACT EXIT PROGRAM(EZACIC01) GASET(ptr)
    GALEN(len)
    
    where ptr is a register and len is a halfword binary variable.
    The address of the GWA is returned in ptr and the length of the
    GWA is returned in len.  Use of the Extract Exit command
    requires RACF update access to the EXITPROGRAM. Failure to have
    at least the UPDATE access to the EXITPROGRAM security class
    will cause the IP CICS Sockets interface and listener to either
    not start when starting or not stop when stopping.
    ************
    After the following text:
    
    For shared files: If the user-written listener reads the
    configuration file, it must first issue an EXEC CICS SET command
    to enable and open the file. When the file operation is
    complete, the user-written listener must issue an EXEC CICS SET
    command to disable and close the file. Failure to do so will
    result in file errors in certain shared-file situations.
    
    Add:
    
    Requirement: Use of the EXEC CICS ENABLE command requires RACF
    update access to EXITPROGRAM. Failure to have at least the
    UPDATE access to the EXITPROGRAM security class will cause the
    IP CICS Sockets Interface and Listener to either not start when
    starting or not stop when stopping.
    ***********************************************************
    In Chapter 8, "Sockets extended application programming
    interface (API)," in the tables "OPTNAME options for GETSOCKOPT"
    and "OPTNAME options for SETSOCKOPT," add the following note to
    the SO_LINGER option description.
    
    Note: If you set a zero linger time, the connection cannot close
    in an orderly manner, but stops, resulting in a RESET segment
    being sent to the connection partner. Also, if the aborting
    socket is in nonblocking mode, the close call is treated as
    though no linger option had been set.
    ***************************************************************
    In Appendix D, "CICS sockets messages" the following new message
    was added:
    
    EZY1301E mm/dd/yy hh:mm:ss CONNECTION CLOSED BY CLIENT
    TRANSACTION= transactionid PARTNER INET ADDR= ipaddr PORT= port
    
    Explanation: A remote client connected to the CICS Listener but
    then closed the  connection before sending the entire amount of
    data required by the Listener as determined by the MINMSGL
    standard Listener configuration parameter or the MSGLEN enhanced
    Listener configuration parameter.
    
    mm/dd/yy is the date (month/day/year) of the message.
    
    hh:mm:ss is the time (hours:minutes:seconds) of the message.
    
    transactionid is the transaction name of the CICS Listener.
    
    ipaddr is the internet address of the remote client.
    
    port is the port number of the remote client.
    
    System Action: The Listener transaction transactionid continues.
    
    User Response: Correct the client program.
    
    System Programmer Response: None.
    
    Module: EZACIC02
    
    Destination: LISTENER
    ***********************************************************
    In Chapter 2, "Setting up and configuring CICS TCP/IP," in the
    "Optional programs, CICS transaction and program definition
    needed" section, make the following changes.
    *************
    Change the following text from:
    **
    The following 2 programs are optional. They are the supplied
    samples. They are also in hlq.SEZATCP:
    ZACICSS
    is a sample iterative server. It establishes the connection
    between CICS and TCPIP, and receives client request from
    workstations. See the EZACICSC sample in Appendix E.
    EZACICSC
    is sample child server that works with the Listener (EZACIC02).
    See the EZACICSS sample in Appendix E.
    *************
    to:
    **
    The following programs are optional. They are the supplied as
    samples. They are
    also in hlq.SEZAINST:
    EZACICSS
    is a sample iterative server. It establishes the connection
    between CICS and TCP/IP, and receives client request from
    workstations. See the EZACICSS sample in Appendix E.
    EZACICSC
    is sample child server that works with the Listener (EZACIC02).
    See the EZACICSC sample in Appendix E.
    **************************************************************
    

Problem summary

Problem conclusion

Temporary fix

Comments

APAR Information

  • APAR number

    II13257

  • Reported component name

    PA LIB INFO ITE

  • Reported component ID

    INFOPALIB

  • Reported release

    001

  • Status

    INTRAN

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2002-04-08

  • Closed date

  • Last modified date

    2005-06-15

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

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

Fix information

Applicable component levels

[{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG19N","label":"APARs - OS\/390 environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"001","Edition":"","Line of Business":{"code":"","label":""}},{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG32M","label":"APARs - VSE\/ESA environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"001","Edition":"","Line of Business":{"code":"","label":""}},{"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":"001","Edition":"","Line of Business":{"code":"","label":""}},{"Business Unit":{"code":null,"label":null},"Product":{"code":"SG19O","label":"APARs - MVS environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"001","Edition":"","Line of Business":{"code":"","label":""}},{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SSSN3L","label":"z\/OS Communications Server"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"001","Edition":"","Line of Business":{"code":"LOB35","label":"Mainframe SW"}},{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG27M","label":"APARs - z\/VM environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"001","Edition":"","Line of Business":{"code":"LOB16","label":"Mainframe HW"}}]

Document Information

Modified date:
15 June 2005