IBM Support

PI65556: DFS3177E RSNCODE = 28 DUE TO UPD-COMMAND ON PLEX-PARTNER SYSTEM

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • DFS3177E-RSNCODE = 28 due to UPD-Command on plex-partner system
    Links terminated inadvertently when submitting the UPDATE
    MSLINK STOP(COMM) OPTION(FORCE) from another IMS-plex member.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * All IMS 14 MSC-TCP/IP users.                                 *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * DFS3177E RSNCODE = 28 and a residual                         *
    *                                                              *
    * active link session after either a                           *
    *                                                              *
    * /PSTOP LINK FORCE or                                         *
    *                                                              *
    * UPDATE MSLINK STOP(COMM) OPTION(FORCE)                       *
    *                                                              *
    * command.                                                     *
    *                                                              *
    *                                                              *
    * This is a forward fit of PI60449.                            *
    ****************************************************************
    * RECOMMENDATION:                                              *
    * INSTALL CORRECTIVE SERVICE FOR APAR/PTF                      *
    ****************************************************************
    In the following IMS configuration:
    
           IMSPLEX1            IMSPLEX2
    
      IMS1A ---
               ICON1 ------ ICON2 -- IMS2
      IMS1B ---
    
    
    IMSPLEX1 consisted of two IMS systems, IMS1A and IMS1B,
    sharing one IMS Connect system ICON1.
    
    IMS1A and IMS1B both defined the same MSPLINK definition
    
    for communicating to IMS2:
    
       MSPLINK LCLPLKID=MSC1
    
    where MSC1 defines the MSC statement in ICON1.
    
    
    
    ICON1 defined an MSC statement to match the MSPLINK definition:
    
       MSC=(LCLPLKID=MSC1,LCLIMS=(IMS1A))
    
    
    
    The LCLIMS indicates that communication should only be allowed
    
    with IMS1A, not IMS1B.
    
    
    
    
    
    An MSC-TCP/IP session was established between IMS1A and IMS2.
    
    
    
    The operator then attempted to terminate the link with
    
    one of these commands from IMS1B:
    
    - /PSTOP LINK link FORCE
    
    - UPDATE MSLINK NAME(linkname) STOP(COMM) OPTION(FORCE)
    
    
    
    The FORCE option is designed to send a message to the remote
    
    IMS, indicating that the local IMS is immediately
    
    terminating the link session.
    
    
    
    This is done even if the local IMS has no active link session,
    
    to allow the remote IMS to clean up potentially residual session
    
    status in the event that the session previously terminated
    
    abnormally.
    
    
    
    In the error scenario, the /PSTOP or UPDATE command was
    
    processed by IMS1B instead of IMS1A.
    
    
    
    IMS1B had no active link session, but sent a message to ICON1
    
    for the link termination notification.
    
    
    
    When ICON1 processed the message from IMS1B, it validated the
    
    LCLPLKID name, but not the IMSID, and fowarded the message
    
    to ICON2 and IMS2.
    
    
    IMS2 issued DFS3176E RSNCODE=28 to indicate that it received
    an immediate shutdown notification, and then terminated the
    link session.
    
    However, IMS1A was never notified that the link session had
    terminated, and /DISPLAY commands still indicated that the
    link was active.
    
    
    Additional keywords:
    CMDPST CMDUPD RSN28 RSN028
    

Problem conclusion

  • HWSMMSC0 is modified to reject MSC messages that do not
    have a valid IMSID for the MSC datastore being used.
    IMS Connect will reject the message with existing
    reason code x'00006044'.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PI65556

  • Reported component name

    IMS V14

  • Reported component ID

    5635A0500

  • Reported release

    400

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2016-07-08

  • Closed date

    2016-07-29

  • Last modified date

    2016-09-02

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

    PI60449

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

    UI39772

Modules/Macros

  • HWSMMSC0
    

Fix information

  • Fixed component name

    IMS V14

  • Fixed component ID

    5635A0500

Applicable component levels

  • R400 PSY UI39772

       UP16/08/05 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.

[{"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SSEPH2","label":"IMS"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"14.1","Line of Business":{"code":"LOB35","label":"Mainframe SW"}}]

Document Information

Modified date:
01 December 2023