PM54039: CPSM AFFINITY LIFETIME SIGNON PERSISTS AFTER USER SIGNOFF.

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• You  have a TRANGRP defined with Affinity relationship(userid)
  Affinity lifetime (Signon) and Automatic affinity creation
  (Yes).
  You signon to the routing region and enter a transaction
  and see where the affinitiy get created. You then sign off
  from the region.
  After the signoff, the affinitiy still shows up under
  Active workload transaction group affinities.
  You have coded the URM EYU9WRAM program for workload
  separation based on the LUNAME . You optionally modify
  the LUNAME based on application dependendent data.
  The changed LUNAME is used to match the WLMDEF definition
  for successful workload separation.
  When an affinity is created based on relation LUNAME
  and lifetime SIGNON, the affinity is created for the
  changed LUNAME. During user sign off, the actual LUNAME
  is used instead to attempt to delete the affinity,
  and the affinity is never removed.
  .
  Additional Symptom(s) Search Keyword(s):KIXREVSLY
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED: All CICSPlex SM V4R1M0 and V4R2M0 Users      *
  ****************************************************************
  * PROBLEM DESCRIPTION:    You have a WLM Routing Action (WRAM) *
  *                      URM which modifies the incoming LUNAME  *
  *                      for selected transactions, to effect    *
  *                      workload separation.  Your transactions *
  *                      establish an affinity to the target AOR *
  *                      with type LUNAME and lifetime LOGON.    *
  *                      Active affinities are established but   *
  *                      when you sign off the affinities are    *
  *                      not removed.                            *
  ****************************************************************
  * RECOMMENDATION: After applying the PTF that resolves this    *
  *                 APAR, all MASes must be recycled to pick     *
  *                 up the new code.  Note that the restarts     *
  *                 do not need to be done at the same time.     *
  ****************************************************************
     When your affinity is created with type LUNAME and lifetime
  LOGON or type USERID and lifetime SIGNON, the affinity is cre-
  ated for the modified LUNAME or USERID.  When you sign off, the
  actual LUNAME or USERID is compared with the affinity key, but
  because the key contains the LUNAME or USERID modified by your
  EYU9WRAM URM, the affinity will not be removed.
  

Problem conclusion

•    The real LUNAME and USERID are saved in the WLM Transaction
  Data Area (TDA) before your EYU9WRAM URM is called.  The saved
  values are used to establish affinities, so when you sign off
  the LUNAME and USERID will match the LUNAME and USERID used to
  establish the affinity.  The values modified by your EYU9WRAM
  URM will still be used to effect workload separation.
  

Temporary fix

• FIX AVAILABLE BY PTF ONLY
  

Comments

APAR Information

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

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

  UK75758 UK75759

Modules/Macros

•    EYURWTDA EYU0WABL EYU0WDAF EYU0WDIN EYU0WTCL
  

Fix information

• Fixed component name

  CICS TS Z/OS V4

• Fixed component ID

  5655S9700

Applicable component levels

• R60M PSY UK75758

     UP12/01/28 P F201

• R70M PSY UK75759

     UP12/01/28 P F201

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.