PM72042: LOCAL AFFINITY SET BY EXIT DFSMSCE0 IS IGNORED FOR OTMA-ENTERED CONVERSATIONAL TRANSACTIONS WITH SMQ ENABLEMENT (AOS=Y) ACTIVE.

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• The DFSMSCE0 exit is used to force local processing based on the
  transaction class. This works fine for all but OTMA-entered
  conversational transactions running in an environment with OTMA
  SMQ Enablement active (AOS=Y). The tranaction ends up processing
  on another IMS in the shared queues group and gets cancelled. It
  appears that the MSTR2LSQ bit set by DFSMSCE0 is ignored in this
  case.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED: All IMS V11 users with OTMA, SMQ enablement  *
  *                 (AOS=Y) active, and local affinity set by    *
  *                 the DFSMSCE0 exit.                           *
  ****************************************************************
  * PROBLEM DESCRIPTION: When local affinity is set by the exit  *
  *                      DFSMSCE0, it is ignored for OTMA        *
  *                      entered conversational transactions     *
  *                      with SMQ enablement (AOS=Y) active.     *
  *                                                              *
  ****************************************************************
  * RECOMMENDATION: INSTALL CORRECTIVE SERVICE FOR APAR/PTF      *
  ****************************************************************
  When the MSTR2LSQ bit is set by DFSMSCE0 to indicate local
  affinity processing for OTMA conversational transactions running
  with OTMA SMQ Enablement active (AOS=Y), the local bit is
  ignored.  Since, the message does not have local affinity,
  another system in the shared queues group processes the message
  and ends up discarding the message.
  
  On the first iteration of the conversation, OTMA fails to set
  CLBV9LOC.  CLBV9LOC informs queue manager to append the IMSID to
  the queue name which forces local affinity on the message.
  
  On subsequent iterations of the conversation, IMS currently does
  not call DFSMSCE0, therefore, there is not an option to set
  local affinity.  This will be addressed by requirement
  MR0906126151.
  
  In the meantime, IMS should set local affinity for OTMA
  conversational messages based on the decision made by the
  DFSMSCE0 exit called on the first iteration.  Therefore, if
  DFSMSCE0 elects to run the conversational transaction local, all
  subsequent iterations will run locally even deferred program
  switches.
  
  Also, when DFSMSCE0 specifies that the OTMA conversation
  transaction is to run on a back-end system by setting the bit
  Mscec_BEroute, all conversational iterations should have
  affinity to the specified system.
  

Problem conclusion

• GEN:
  KEYWORDS:
   SYSPLEXSQ
  
  *** END IMS KEYWORDS ***
  DFSMSCE0 will determine if all iterations for OTMA
  conversational messages will run with local affinity.  Once
  the decision is made, all iterations for the OTMA conversation
  will run locally.  The same will hold true when DFSMSCE0 sets
  bit Mscec_BEroute to have OTMA conversations run on a specific
  back-end system.
  
  DFSYTIB has been modified to define YTIB_MSCEC_LOCAL to indicate
  that local affinity has been set by DFSMSCE0.  This bit will be
  used to indicate that all conversation iterations will use the
  affinity specified by DFSMSCE0.
  
  DFSYTIB0 has been modified as follows:
  - Ytib_Mscec_Local is set when DFSMSCE0 indicates that the
    conversational transaction is to be processed locally.  This
    flag will be set to allow subsequent conversation iterations
    to be processed with local affinity.
  
  - Set CLBVFLG9 if DFSMSCE0 indicates that the conversational
    transaction is to have local affinity.
  
  - Set CCBAFFIN from MSCEBAFIN if the transaction is to
    run a backend system (Mscec_BEroute).  This will allow all
    the conversational iterations to run on the specific backend
    system.
  
  DFSAOAM2 and DFSAOA00 have been re-compiled for the DFSYTIB
  changes.
  
  ICLI has been modified to add the following field for BE
  processing.
  - CCBAFFIN has been defined to indicate the system where
    affinity is attached.
  - Note that the offset of the field CCBSRPST has changed.
  
  DFSQC050 has been modified to determine if CCBAFFIN is
  available.  If CCBAFFIN is available, it will be moved into the
  shared queues prefix.  This will allow iterations other than the
  first to be processed with affinitly to that system.
  
  DFSCRPX0 and DFSCRPQ0 have been re-compiled for the ICLI
  changes.
  

Temporary fix

• *********
  * HIPER *
  *********
  

Comments

APAR Information

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

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

  PM79758 PM79759 UK91317 UK91318

Modules/Macros

• DFSAOAM2 DFSAOA00 DFSCRPQ0 DFSCRPX0 DFSQC050
  DFSYTIB  DFSYTIB0 ICLI
  

Fix information

• Fixed component name

  IMS V11

• Fixed component ID

  5635A0200

Applicable component levels

• R100 PSY UK91317

     UP13/02/07 P F302 Ž

• R102 PSY UK91318

     UP13/02/07 P F302 Ž

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.