IBM Support

PK49141: CMAS SLOW PERFORMANCE DURING TOPOLOGY JOIN METHOD TSLG TSG2

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • CMAS unnecessarily requests topology resource map data during
    topology join processing resulting in possible maxtask in CMAS
    and overhead in topology resmap hardening to the EYUDREP data
    repository.
    .
    Additional Symptom(s) Search Keyword(s): TSSJ TSMJ SETUP_LISTREQ
     TSLG TSG2 signature base active delta PROCESS_LISTS resmap
    RTDB
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All CICSPlex SM V3R2M0 Users                 *
    ****************************************************************
    * PROBLEM DESCRIPTION: Topology Join processing for a MAS may  *
    *                      be elongated if a large number of       *
    *                      MASes are being Joined concurrently.    *
    *                                                              *
    *                      This can result in various problems if  *
    *                      a CMAS must Join a great number of      *
    *                      MASes when it initializes.              *
    *                                                              *
    *                      Problems seen include, but are not      *
    *                      limited to, the following:              *
    *                                                              *
    *                      -  the CMAS may go maxtask (MXT)        *
    *                      -  the CMAS may go short-on-storage     *
    *                         (SOS).                               *
    *                      -  the CMAS may experience connection   *
    *                         problems with other CMASes.          *
    *                      -  some of the Join attempts may fail.  *
    ****************************************************************
    * RECOMMENDATION: In a mixed CICSPlex SM V3R2M0 and V3R1M0     *
    *                 CMAS network, the PTF that resolves this     *
    *                 APAR must be installed on all CICSPlex SM    *
    *                 V3R2M0 CMASes before installing the PTF      *
    *                 that resolves APAR PK47823 on any CICSPlex   *
    *                 SM V3R1M0 CMASes.                            *
    *                                                              *
    *                 After applying the PTF that resolves this    *
    *                 APAR, all CMASes, MASes and WUI servers must *
    *                 be restarted.                                *
    *                                                              *
    *                 The restarts need not be performed at the    *
    *                 same time, however if systems are not        *
    *                 restarted at the same time, the following    *
    *                 rules apply:                                 *
    *                                                              *
    *                 - Maintenance point CMASes must be restarted *
    *                   on the updated code before non Maintenance *
    *                   point CMASes, MASes and WUI Servers.       *
    *                                                              *
    *                   If you have more than one Maintenance      *
    *                   point CMAS and those Maintenance point     *
    *                   CMASes are connected directly or           *
    *                   indirectly, then these maintenance point   *
    *                   CMASes must be restarted at the same time. *
    *                                                              *
    *                 - Before a MAS or WUI server runs with the   *
    *                   updated code, the CMAS to which the MAS or *
    *                   WUI server connects must be restarted      *
    *                   with the updated code.                     *
    ****************************************************************
    During Topology connect processing, the CMAS will build Topology
    Resource maps (Resmaps) for each MAS that connects. The Resmaps
    exist for each different CICS object type that is maintained
    within CICSPlex SM Topology, for example, Programs, Files,
    Transactions etc.
    
    When the Resmap is originally created, a base signature is
    generated. An additional signature, the current signature, is
    also created. The current signature is initially set to the base
    signature.
    
    The Resmap and the current signature are hardened to the
    CMASes data repository for later use on MAS restart.
    
    If a resource is installed or discarded, the CMAS will update
    its Resmap through the use of a delta list.  This delta list
    identifies changes that must be applied to the Resmaps. When the
    Resmaps are updated, the current signature (but not the base
    signature) is updated.
    
    During Topology Join processing, the joining CMAS will check
    to see if it has the necessary Resmaps with the correct
    signatures. If they are correct, then the joining CMAS will
    use the Resmaps from its local data repository.
    
    If the Resmaps do not exist or do not have the correct
    signature, then the correct Resmaps must be requested from
    the CMAS that connected the MAS.
    
    In order to request the Resmaps for a MAS, the joining CMAS will
    send the connecting CMAS up to two requests (TSLG and TSG2).
    These requests will run under XLST transactions in the
    connecting CMAS.
    
    Because of a number of logic errors in the processing of the
    Resmaps, the joining CMAS may needlessly send the connecting
    CMAS the TSLG and TSG2 requests asking for Resmaps that are not
    necessary. If a number of CMASes are processing the join
    requests, the connecting CMAS may receive a large number of
    requests, which in turn may lead to the connecting CMAS reaching
    MXT, or the other symptoms described above.
    

Problem conclusion

  • A number of changes have been made to correct the Resmap
    processing:
    
    - A new object, TOPSIGNS has been created. This is used to
      store the current and base signatures for each Resmap
      along with a Resmap changed indicator.
    - During CICSPlex SM Network Topology import/export, each
      MAS's TOPSIGNS data will also be imported/exported when
      it is available.
    - A resmap's base signature will now be saved (along with the
      current signature) when the resmaps are hardened to the
      data repository.
    - During Topology Join processing, the new TOPSIGNS
      information will be used to determine if the TSLG and
      TSG2 requests should be sent to the connecting CMAS.
      These changes should insure that these requests only
      run when necessary. When they do run, they should only
      be retrieving the required data.
    - The CICSPlex SM online utility (COLU) will now include the
      MAS's Topology sign information when the COLU COM NETOP
      transaction is run.
    

Temporary fix

  •             *********
                * HIPER *
                *********
    FIX AVAILABLE BY PTF ONLY
    

Comments

  • ž**** PE07/11/08 FIX IN ERROR. SEE APAR PK56207  FOR DESCRIPTION
    

APAR Information

  • APAR number

    PK49141

  • Reported component name

    CICSTS V3 Z/OS

  • Reported component ID

    5655M1500

  • Reported release

    50M

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    YesHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2007-07-18

  • Closed date

    2007-08-30

  • Last modified date

    2008-01-14

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

    PK47823

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

    UK28633

Modules/Macros

  •    CONNDSEG EYUCXXRS EYUQCPAM EYUQCPLM EYUQCPMI
    EYUQCPMX EYUQCPUM EYUQXCRB EYUQXCRS EYUQXLRD EYUQXXRC EYURCPAM
    EYURCPEQ EYURCPLM EYURCPMI EYURCPMX EYURCPUM EYURXCRB EYURXCRL
    EYURXCRS EYUR2436 EYUR2453 EYUR2644 EYUTMOMI EYUTMOSD EYUTRCHE
    EYUTRCOM EYUTRDIR EYUTVOSX EYUT2436 EYUT2453 EYUT2644 EYUUTPEQ
    EYUUXCEQ EYUUXXFI EYUUXXRS EYUUXXTC EYUYCPAM EYUYCPLM EYUYCPMI
    EYUYCPMX EYUYCPUM EYUYXCRB EYUYXCRS EYUY2436 EYUY2453 EYUY2644
    EYUZCPAM EYUZCPLM EYUZCPMI EYUZCPMX EYUZCPUM EYUZXCRB EYUZXCRS
    EYU0CPAM EYU0CPAP EYU0CPBM EYU0CPCU EYU0CPDM EYU0CPDP EYU0CPEJ
    EYU0CPLM EYU0CPMI EYU0CPMX EYU0CPSL EYU0CPTI EYU0CPTX EYU0CPUM
    EYU0TICT EYU0TSCJ EYU0TSCM EYU0TSDD EYU0TSEM EYU0TSGC EYU0TSLM
    EYU0TSMB EYU0TSMC EYU0TSMD EYU0TSMH EYU0TSMI EYU0TSMJ EYU0TSMM
    EYU0TSMR EYU0TSMU EYU0TSRA EYU0TSRC EYU0TSRM EYU0TSSC EYU0TSSD
    EYU0TSSE EYU0TSSH EYU0TSSJ EYU0TSSM EYU0TSTP EYU0TSXC EYU0XCRB
    EYU0XCRS EYU0XL80 EYU9CMPU EYU9CMP3 EYU9CMP4 EYU9CMRU EYU9CMR3
    EYU9CMR4 EYU9XCPU EYU9XCP3 EYU9XCP4 JCI650MJ MASDIR   TOPRMINF
    TOPSIGNS
    

Fix information

  • Fixed component name

    CICSTS V3 Z/OS

  • Fixed component ID

    5655M1500

Applicable component levels

  • R50M PSY UK28633

       UP07/08/31 P F708

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":"3.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":"3.2","Edition":"","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
14 January 2008