IV58916: ERROR FOR OMEGAVIEW AGENTS WHEN CONNECTING TO THE TEMS

APAR status

• Closed as program error.

Error description

• Error trace messages like the folloeing are issued by the TEMS
  when an
  OmegaView subnode agent attempts to connect to the TEMS:
  2014.024 10:29:50.07
  (0001-C7A44AF3:kfastinh.c,1282,"KFA_InsertNodests")
  Unexpected Error <5>.  System MSL does not resolve for nod
  2014.024 10:29:50.07 e <CAA1                            >
  thrunode
  <CP1A:C1AMVAP:KWOSDI             > affinity <W000080000000
  2014.024 10:29:50.07 000000000000000000000000002043 >.
  2014.024 10:29:50.14
  (0002-C7A44AF3:kfastinh.c,1282,"KFA_InsertNodests")
  Unexpected Error <5>.  System MSL does not resolve for nod
  2014.024 10:29:50.14 e <CAA2                            >
  thrunode
  <CP1A:C1AMVAP:KWOSDI             > affinity <W000080000000
  RECREATE INSTRUCTIONS:
  Install an OmegaView application, configure subnodes, start it
  and let
  it connect to the TEMS.
  

Local fix

• No workaround
  

Problem summary

• OmegaView agents never come online when connecting to enterprise
   monitoring server.
  
  This APAR only applies to enterprise monitoring server at
  release level 6.20 or later. Dynamic affinities were introduced
  in 6.20 release level and in turn a strict check is made to be
  sure a system MSL can be generated. If the affinity is not
  recognized, system MSL can not be generated, thus node status is
   rejected and node fails to go online. This check was
  incorrectly being applied to static affinity nodes; OmegaeView
  agent is a static affinity type.
  

Problem conclusion

• Code was added to exempt static affinity agents from system MSL
  check, so that these agents do successfully go online.
  

Temporary fix

Comments

APAR Information

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

  OA44499

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

Fix information

• Fixed component name

  TEMS

• Fixed component ID

  5724C04MS

Applicable component levels

• R623 PSY

     UP