IBM Support

PI19825: TRANSACTIONS FAIL TO ROUTE CORRECTLY WHEN SPECIFYING A NETWORK NAME ON THE WLMDEF

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • When testing workload seperation using  Terminal LU name
    pattern matching, depending on the LUNAME specified on the
    WLMDEF, the transaction may not be routed to any available
    target as expected.
    
    For example, if transaction "ABCD" with the WLMDEF LUname set
    to .ABCDE*, the transaction is successfully routed to one of
    the available targets.  If the WLMDEF is altered to specify
    NETWORK.ABCDE* and installed in the workload, any attempt to
    run transaction "ABCD" is not routed but ran locally where it
    fails.
    
    During workload processing, CICSPlex SM evaluates the terminal
    and user names associated with each occurrence of a request to
    determine where the request should be routed.
    - If the terminal and user names associated with the
    transaction match the selection criteria specified in an
    installed workload definition, the request is routed to the
    target
    - If either the terminal or user name does not match the
    selection criteria, the request is routed to the default set of
    target regions identified in the workload specification.
    
    Additional Symptom(s) Search Keyword(s): KIXREVCTC
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All CICSPlex SM V5R2M0 Users                 *
    ****************************************************************
    * PROBLEM DESCRIPTION:    When performing workload separation  *
    *                      using Terminal LUNAME pattern matching, *
    *                      if the LUNAME mask in the WLMDEF        *
    *                      contains a fully qualified LUNAME in    *
    *                      the form of "networkid.netname", the    *
    *                      transaction might not be routed to an   *
    *                      available region in the target scope    *
    *                      of the proper WLMDEF, as expected.      *
    ****************************************************************
    * RECOMMENDATION:    After applying the PTF that resolves this *
    *                 APAR, all MASes defined as Routing Regions   *
    *                 in a CPSM workload must be recycled to pick  *
    *                 up the code changes.  Note that regions do   *
    *                 not have to be brought down and restarted    *
    *                 at the same time.                            *
    ****************************************************************
       When entered to determine a target region for a terminal
    initiated transaction, program EYU9XLOP (XLOP - CPSM Dynamic
    Workload Routing URM) retrieves the NETNAME of the originating
    terminal from CICS.  This is passed to module EYU0WDTR (WDTR -
    Dynamic / Distributed Routing Mainline) and on to module
    EYU0WDIN (WDIN - Dynamic / Distributed Routing Initialization)
    where a truncated LUNAME ".netname" is constructed and stored
    in the Transaction Data Area (WTDA).  Because CPSM is not aware
    of the fully qualified LUNAME for the originating terminal,
    workload separation based on fully qualified LUNAME (that is,
    "networkid.netname") will select a target region from the scope
    of the wrong WLMDEF, or will fail to find a matching WLMDEF and
    will select the default target region.
    

Problem conclusion

  • Module EYU0WDIN was modified to retrieve the fully qualified
    LUNAME of the initiating terminal from CICS.  If a fully quali-
    fied name is not available, the truncated LUNAME is constructed
    as before.  Module EYU0WTCL (WTCL - WLM Classify Transaction)
    was updated to avoid attempting to match the Process Type of
    the transaction being routed against the Process Type mask in
    each WLMDEF, if it is not part of a BTS (Business Transaction
    Services) workload.
    

Temporary fix

  • FIX AVAILABLE BY PTF ONLY
    

Comments

  • ž**** PE15/04/24 FIX IN ERROR. SEE APAR PI39741  FOR DESCRIPTION
    

APAR Information

  • APAR number

    PI19825

  • Reported component name

    CICS TS Z/OS V5

  • Reported component ID

    5655Y0400

  • Reported release

    90M

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2014-06-11

  • Closed date

    2014-07-18

  • Last modified date

    2015-06-25

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

    PM66404

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

    UI19749

Modules/Macros

  • EYU0WDIN EYU0WTCL
    

Fix information

  • Fixed component name

    CICS TS Z/OS V5

  • Fixed component ID

    5655Y0400

Applicable component levels

  • R90M PSY UI19749

       UP14/07/22 P F407

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":"SSGMGV","label":"CICS Transaction Server"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"5.2","Edition":"","Line of Business":{"code":"LOB35","label":"Mainframe SW"}},{"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":"5.2","Edition":"","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
25 June 2015