PM65729: MS TRAPS ARE NOT TRIGGERED BY PORTAL REQUEST EVENTS

7.1.0.3-TIV-ITCAMAD-IF0004: ITCAM for Application Diagnostics V7.1 FP3 IF4
7.1.0.3-TIV-ITCAMAD-IF0005: ITCAM for Application Diagnostics V7.1 FP3 IF5
7.1.0.3-TIV-ITCAMAD-IF0004: ITCAM for Application Diagnostics V7.1 FP3 IF6

APAR status

• Closed as program error.

Error description

• Problem Abstract: MS Traps do not fire for Portal request events
  
  ---------------------------------
  Users Affected: Users setting traps against Portal requests
  
  ---------------------------------
  Problem Description: Traps created to fire against the names of
  Portal request events are never triggered
  
  The customer creates some Portal type events by accessing WAS
  Portal applications. The portal request events are verified when
  looking at Server Activity Display (in the Recent Requests tab)
  and in the Performance Analysis Reports.
  
  However if the customer takes the string that forms the name of
  the Portal request event and uses this to create a trap, it
  never triggers even though we are sure the portal event was
  created
  
  ---------------------------------
  Keyword/Symptom: INCORROUT
  
  ---------------------------------
  Component ID: 5724Y92MS
  
  ---------------------------------
  Severity: 2
  
  ---------------------------------
  Local Fix/Workaround: N/A
  
  
  ---------------------------------
  Approvals:
  
  L2: Oneil Richardson
  L3: Keyuri Patel
  ---------------------------------
  

Local fix

• N/A
  

Problem summary

• USERS AFFECTED: Customers trying to set traps against portal
  requests
  
  PROBLEM DESCRIPTION: Traps created to fire against the names of
  Portal request events are never triggered
  The customer creates some Portal type events by accessing WAS
  Portal applications. The portal request events are verified when
  looking at Server Activity Display (in the Recent Requests tab)
  and in the Performance Analysis Reports.
  However if the customer takes the string that forms the name of
  the Portal request event and uses this to create a trap, it
  never triggers even though we are sure the portal event was
  created
  
  RECOMMENDATION: Apply the fix 7103 ifix4
  

Problem conclusion

• The traps were not triggered for portal
  requests because DC was never sending a request name in the
  entry/start request. DC only sent request name in the exit
  record. Venkatesh said it is tricky to fix this on DC side so I
  fixed it on MS side with a workaround. I am bypassing the
  condition for portal server where traps condition are checked
  for entry event.
  
  The fix for this APAR is included in 7.1.0.3 Ifix4
  

Temporary fix

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

  TCAM AD MAN SER

• Fixed component ID

  5724Y92MS

Applicable component levels

• R710 PSY

     UP