IBM Support

PI77062: ENHANCEMENT TO IMPROVE TRANSACTION THROUGH-PUT WHEN MULTIPLE DLI CALLS ACCESS THE SAME NON-AUDITED DBD/SEG

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • When the IMS STAP policy is configured so cause DLI calls to be
    rejected due to the DBD/SEG pair being EXCLUDED, or not
    INCLUDED in
    the candidate database list, every DLI call must be routed
    through the
    filtering process. This change allows the IMS ONLINE portion of
    the
    IMS STAP to use STAGE 1 filtering to reduce the number of calls
    to the
    IMS CTX ITASK and filter, which can improve IMS performance and
    transaction through-put.
    
    If ALL rules in the policy contain DBD/SEGs which have ALL DLI
    call
    types referenced, when a DLI call is rejected due to the
    DBD/SEG pair,
    a flag is set that will allow the STAGE1 filter to reject the
    DLI call
    for subsequent DLI calls if: the USERID, PSB, DBD and SEGMENT
    of the
    rejected DLI call are the same as the current DLI call.
    
    If the policy rules contain DBD/SEGs which do not have all DLI
    call
    types referenced, the STAGE1 filtering may still occur, but
    only for
    DLI calls with which the USERID, PSB, DBD, SEGMENT AND DLI call
    of the
    rejected DLI call are the same as the current DLI call.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: Users of IBM Security Guardium S-TAP for     *
    *                 IMS on z/OS                                  *
    ****************************************************************
    * PROBLEM DESCRIPTION: When the IMS STAP policy is configured  *
    *                      to cause DLI calls to be rejected due   *
    *                      to the DBD/SEG pair being EXCLUDED,     *
    *                      or not INCLUDED in the candidate        *
    *                      database list, every DLI call must be   *
    *                      routed through the filtering process.   *
    *                      This change allows the IMS ONLINE       *
    *                      portion of the IMS STAP to use STAGE 1  *
    *                      filtering to reduce the number of calls *
    *                      to the IMS CTX ITASK and filter, which  *
    *                      can improve IMS performance and         *
    *                      transaction through-put.                *
    *                                                              *
    *                      If ALL rules in the policy contain      *
    *                      DBD/SEGs which have ALL DLI call types  *
    *                      referenced, when a DLI call is rejected *
    *                      due to the DBD/SEG pair, a flag is set  *
    *                      that will allow the STAGE1 filter to    *
    *                      reject the DLI call for subsequent DLI  *
    *                      calls if: the USERID, PSB, DBD and      *
    *                      SEGMENT of the rejected DLI call are    *
    *                      the same as the current DLI call.       *
    *                                                              *
    *                      If the policy rules contain DBD/SEGs    *
    *                      which do not have all DLI call types    *
    *                      referenced, the STAGE1 filtering may    *
    *                      still occur, but only for DLI calls     *
    *                      with which the USERID, PSB, DBD,        *
    *                      SEGMENT AND DLI call of the rejected    *
    *                      DLI call are the same as the current    *
    *                      DLI call.                               *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    Apply the supplied PTF to resolve this issue.
    

Problem conclusion

  • N/A
    

Temporary fix

Comments

APAR Information

  • APAR number

    PI77062

  • Reported component name

    SEC GUAR STAP I

  • Reported component ID

    5655STM00

  • Reported release

    A00

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2017-02-22

  • Closed date

    2017-03-24

  • Last modified date

    2017-04-03

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

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

    UI45878

Modules/Macros

  •    AUICPY4B AUICPY4C AUICPY4D AUICPY4E AUICPY4F
    AUIDLA0B AUIDLA0C AUIDLA0D AUIDLA0E AUIDLA0F AUILOG0B AUILOG0C
    AUILOG0D AUILOG0E AUILOG0F AUILOO0B AUILOO0Z AUIMCOM
    

Fix information

  • Fixed component name

    SEC GUAR STAP I

  • Fixed component ID

    5655STM00

Applicable component levels

  • RA00 PSY UI45878

       UP17/04/01 P F703

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":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSCJM6A","label":"IBM Security Guardium S-TAP for IMS on z\/OS"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"A00","Edition":"","Line of Business":{"code":"LOB24","label":"Security Software"}},{"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":"A00","Edition":"","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
03 April 2017