IZ30099: UADVISOR SITUATIONS ARE AUTOSTARTED ON TEMS NOT DISTRIBUTED TO

APAR status

• Closed as program error.

Error description

• UADVISOR *.his situations are supplying a QIBSCOPE 'I' value
  rather than an 'E' value, causing them to start at the hub TEMS.
  
  Even though it is an application responsibility to provide a
  *.his member - the KIB code should really now be ignoring the
  qualifier since QIBSCOPE is deprecated.  The KIB code needs to
  be changed to ignore this value.
  
  This change causes the correct behavior to happen at TEMS
  startup which is to say that any historical UADVISOR not found
  to have a distribution for the TEMS that is starting up is
  properly discarded.
  

Local fix

• Modify the *.his UADVISOR situations to change QIBSCOPE 'I'
  values to 'E' values
  

Problem summary

• History uadvisors are started on a zOS based HUB when they are
  not distributed to that HTEMS.
  
  At HUB startup, the HTEMS fails to determine which uadvisors are
  actually distributed to other RTEMS and starts all of the
  uadvisor history situations.
  

Problem conclusion

• A string compare fails to determine if the uadvisor is an old
  format when the pedicate is not treated as a UTF8 defined
  string.  This compare always fails on machines that use EBCIDIC
  (zOS).  Use defined strings in place of literals and the string
  compare will return the proper value on zOS systems.
  
  The fix for this APAR is contained in the following maintenance
  packages:
   | interim fix | 6.1.0.7-TIV-ITM-IF0002
  

Temporary fix

Comments

APAR Information

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

  OA23171

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

Fix information

• Fixed component name

  TEMS

• Fixed component ID

  5724C04MS

Applicable component levels

• R610 PSY

     UP