IBM Support

PI50579: HWSS0742W MESSAGE FAILED, ORIGIN=12100 _IC020001 TO DESTID=IMSS R=4, S=NFNDDST , M=SRE4 AFTER DEFINING IMSPLEX TMEMBER

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • The definition of:
    ------------------
    HWS (ID=IMS1CONN,RACF=N,XIBAREA=20)
    TCPIP (HOSTNAME=TCP2,
    PORTID=(12100),
    RACFID=UHWSSS,
    MAXSOC=2000,TIMEOUT=6000,EXIT=(HWSSMPL0,CAGRITCP),IPV6=N)
    DATASTORE(ID=IMS1,GROUP=IMSSS1,MEMBER=IMS1HWS1,TMEMBER=IMSWS100)
    DATASTORE(ID=IMS2,GROUP=IMSSS1,MEMBER=IMS2HWS1,TMEMBER=IMSWS200)
    IMSPLEX (MEMBER=IMS1CON,TMEMBER=IMSSS)
    .
    resulted into:
    .
    HWSS0742W MESSAGE FAILED, ORIGIN=12100 _IC020001 TO DESTID=IMSS
    R=4, S=NFNDDST , M=SRE4  since the activation of the IMSPLEX
    statement.
    ----------------------------------------------------------------
    Seems the IMSplex TMEMBER name was added to the datastore list
    .
    HWS exits HWSJAVA0 and HWSSMPL0 are used to determine a
    datastore when a message is delivered to the IMS connect. Before
    the IMSPLEX statement was added in the two HWSCFG* members there
    were only defined two datastores, IMS1 and IMS2.
    After adding the IMSPLEX statement
    "IMSPLEX (MEMBER=IMS1CON,TMEMBER=IMSSS)" there was created an
    extra  "datastore" entry in the XIB_DATASTORES table with the
    name IMSSS . This was not expected. So the HWS exits sometimes
    choose this entry of "datastore" IMSSS but in its logic it only
    uses the first four characters IMSS. And when the message that
    is handled is getting the "datastore" IMSS assigned that of
    course goes wrong in forwarding the message to this "datastore".
    There is no datastore IMSS or IMSSS.
    

Local fix

  • Adjust the exit to ignore the IMSPLEX datastore
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All IMS V12 IMS Connect users                *
    ****************************************************************
    * PROBLEM DESCRIPTION: Adding an IMSPLEX statement to the      *
    *                      configuration member results in the     *
    *                      following error message.                *
    *                                                              *
    *                      HWSS0742W MESSAGE FAILED,               *
    *                      ORIGIN=portid_clientid TO DESTID=did,   *
    *                      R=4, S=NFNDDST, M=SRE4                  *
    *                                                              *
    *                      The DESTID matches the first 4          *
    *                      characters of the tmember name          *
    *                      specified on the IMSPLEX configuration  *
    *                      member statement.                       *
    ****************************************************************
    * RECOMMENDATION: INSTALL CORRECTIVE SERVICE FOR APAR/PTF      *
    ****************************************************************
    MESSAGE FAILED, ORIGIN=portid_clientid TO DESTID=did, R=4,
    S=NFNDDST, M=SRE4.
    
    The destination id (did) displayed in the message is not a valid
    datastore name but does match the first 4 characters of the
    tmember name from the IMSPLEX configuration statement added to
    the IMS Connect configuration member.
    
    The datastore entry was selected by scaning the exit interface
    block datastore list.  The exit interface block datastore list
    (XIB_DATASTORES) consist of entries that represent IMSPLEX
    members in addition to IMS datastore entries.  Currently there
    is no way to distinguish between the two entry types.
    Therefore, logic in user message exits may select the IMSPLEX
    tmember destination instead of an IMS datastore destination when
    routing input request resulting in error message;
    

Problem conclusion

  • GEN:
    KEYWORDS:
    
    *** END IMS KEYWORDS ***
    Two new flags have been added to the datastore entry dsect
    HWSXIBDS to indicate the type of entry.
    
    The map of the datastore entry HWSXIBDS contains flag byte
    XIBDS_FLAG.
    New flag bit XIBDS_DS equ x'08' is set to indicate that the
    entry is for an IMS datastore.
    New flag bit XIBDS_PLEX equ x'04' is set to indicate that the
    entry is for an IMSPLEX.
    
     note: A copy of the HWSXIBDS macro is in SDFSMAC.
           To see the structure, assemble the macro.
    
    The IMS connect user message exit can examine the new flags
    to determine the datastore entry type when scaning the datastore
    list.
    
    Part HWSXCFG0 has been modified to set either XIBDS_DS or
    XIBDS_PLEX when building the datastore list from the from
    configuration statement definitions during startup.
    
    -------Documentation Update------------------------------------
    The following document is updated to describe two new flag bits
    defined in the format of the XIBDS exit interface block.
    
    IMS V12 Communications and connections - SC19-3012-00
    
    IMS 12.1.0
     >IMS administration
      >Communications and connections  - SC19-3012-00
       >IMS Connect and TCP/IP communications
        >Overview of IMS Connect exit routines
         >Exit interface blocks
          >XIBDS exit interface block for IMS TM data store
           information
           >Format of XIBDS exit interface block
    
    Format of XIBDS exit interface block
    
    -Add new bits X'08' and X'04' to XIBDS_FLAG-
    
    Field        Dec      Hex      length  Value
                 Offset   Offset
    XIBDS_FLAG   9        X'09'    1       Data store entry flags.
                                           X'08'
                                            Entry for DataStore
                                           X'04'
                                            Entry for IMSPLEX
    

Temporary fix

Comments

APAR Information

  • APAR number

    PI50579

  • Reported component name

    IMS V12

  • Reported component ID

    5635A0300

  • Reported release

    200

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2015-10-15

  • Closed date

    2016-02-15

  • Last modified date

    2016-03-02

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

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

    PI56068 PI56069 UI35357

Modules/Macros

  •    HWSXCFG0 HWSXIBDS
    

Publications Referenced
SC19301200    

Fix information

  • Fixed component name

    IMS V12

  • Fixed component ID

    5635A0300

Applicable component levels

  • R200 PSY UI35357

       UP16/02/19 P F602

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"},"Platform":[{"code":"PF054","label":"z Systems"}],"Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
14 December 2020