IZ44037: UA HTTP:SITUATION ON URL,URLALIAS CREATES INVALID MANAGED URL

APAR status

• Closed as program error.

Error description

• Environment: Universal Agent 6.2 FP2; all platforms.
  Problem also reproduced in a 6.2.1 environment.
  Problem Description:
  Using HTTP DataProvider, if an URL is already present
  into the KUMPURLS file, it means that UA is already monitoring
  it.In the KUMPURLS file, the entry related to this URL also
  contains a value for URLAlias.
  If we create a situation using this URLAlias,we can notice
  that a new URL appear into the Managed_URL workspace.
  This new URL should not be added and furthermore looks
  also wrong formatted because the URL field contains a string
  like : http://as EQ AdWS3
  This is a substring of "alias EQ AdWS3"
  statement we put into the KUMPURLS and belonging to the
  URL originally monitored.
  Detailed Recreation Procedure:
  Open KUMPURLS file and put some URLs you want to monitor,
  in example:
  http://ws3.dummy.url.it/ws3_sil_rl/services/Version INTERVAL=300
  CACHE=0 USER=20 ALIAS=AdWS3
  http://www.dummyurl.region.ita.it/xxx/home.do INTERVAL=300
  CACHE=0 USER=30 ALIAS=AdBorsaLavoro
  Then restart the UA.
  You will see two entries into Managed_URL workspace
  Then create a situation using attribute STATUS and URL
  Alias, in example a situation that fires when
  STATUS ]= OK and URLAlias = AsWS3.
  As soon as the situation starts, a new row is added into the
  Managed_URL
  workspace view, having the following URL:
  http://as EQ AdWS3
  that of course returns a "not a recognized network address"
  status.
  

Local fix

• Do not use UrlAlias into the situation formula.
  

Problem summary

• When a Situation is defined to monitor URL and URL Alias, and
  the URL is using the scan operator and the URL Alias is using an
  equality/inequality operator, there will be a resultant invalid
  URL that is added to the Managed URL TEP report.
  

Problem conclusion

• A correction was made to search for "URL " (with a space) rather
  than "URL" (without a space) to avoid mistakenly matching on the
  "URL_Alias" attribute, for example:  Searching for <URL > in the
  text string "<ATTRIBUTES=(URL_Alias EQ Goofy)>" prevents the
  error of parsing out a bogus URL of "as EQ Goofy".
  
  
  The fix for this APAR is contained in the following maintenance
  packages:
  
     | fix pack | 6.2.0-TIV-ITM-FP0003
  

Temporary fix

• Do not define a situation that "scans" URL and checks "URL
  Alias" for equality/inequality.  Situations that check URL for
  equality/inequality may also check URL Alias without any
  perturbations.
  

Comments

APAR Information

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

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

Fix information

• Fixed component name

  UNIVERSAL AGENT

• Fixed component ID

  5724K1000

Applicable component levels

• R620 PSY

     UP