OA26223: UA SITUATIONS DISTRIBUTED TO SUBNODES CAN FAIL TO START

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• When an agent attaches to a TEMS we have to make sure that all
  situations that are distributed to that agent are started on
  that agent.
  
  Situation distributions are stored in the Access List.
  In response to the on-line event from an agent, FA, a component
  of the TEMS, scans this list for all situations that are
  distributed to the agent and forwards the notifications to
  Sitmon, another TEMS component.
  If the situation has already been started, (on behalf of one or
  more other agents), Sitmon simply notifies the Proxy Controller,
  (yet another TEMS component, one that communicates directly with
  agents attached to the TEMS), that the situation needs to be
  started on that agent.
  
  This scheme works well for standard agents.
  But UA is a subnode application, i.e. the UA agent acts as a
  manager of one or more sub-applications that report directly to
  it.
  
  Situations can be distributed directly to subnodes instead of to
  the subnode manager ... and this is where the problem lies.
  
  It seems that when the subnode manager comes on-line, FA is
  generating Access List notifications not only for situations
  that are distributed directly to the manager itself, but also
  for situations that are distributed to subnodes of that manager.
  
  As before, if those situations are already running on the TEMS,
  Sitmon just taps the Proxy Controller to start it on the
  appropriate subnode.
  BUT, as it stands today, there is no guarantee that the subnode
  itself has actually come on-line by the time the 'start' request
  is sent from Sitmon to Proxy.
  If it hasn't, Proxy ignores the request to start the situation.
  

Local fix

• Restart the situation or STOP/START the Universal Agent
  

Problem summary

• ****************************************************************
  * USERS AFFECTED: All TEMS users.                              *
  ****************************************************************
  * PROBLEM DESCRIPTION: The issue involves situations failing   *
  *                      to start at subnodes of an              *
  *                      IRA Manager. This can occur when the    *
  *                      IRA Manager switches from one TEMS to   *
  *                      another TEMS.                           *
  ****************************************************************
  * RECOMMENDATION: Apply the PTF.                               *
  ****************************************************************
  When an IRA Manager switches from one TEMS to another, it is
  possible for situations to fail to start on the subnodes
  attached to the IRA Manager. This occurs when an attempt is
  made to distribute situations to the subnodes before
  registrations have been received at the HTEMS for the
  subnodes.
  

Problem conclusion

• The code was changed to serialize metadata deployment for a
  switched IRA Manager.
  

Temporary fix

Comments

APAR Information

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

  IZ05788

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

Modules/Macros

• KFAAUTOX KFACOM   KFAOMTEC KFAPRB
  

Fix information

• Fixed component name

  MGMT SERVER DS

• Fixed component ID

  5608A2800

Applicable component levels

• R610 PSY UA43066

     UP08/09/18 P F809

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.