IC87312: SCC ISSUING FALSE ALERTS FOR SI BUSINESS PROCESS

APAR status

• Closed as program error.

Error description

• Business processes that are being marked successful in Sterling
  Integrator, are having alerts generated from Sterling Control
  Center saying they have failed.
  
  SI introduced two new status recently, those being "BP Queued"
  and "JMS Queued". At the step level, the numeric status value
  for those is "11" and "12". When SCC interrogates the BP steps
  to determine success/failure, it's seeing those unrecognized
  values and flagging them as errors.
  

Local fix

• STRRTC - 352935
  SF / SF
  Circumvention: None
  

Problem summary

• Description of issue: Getting alerts when a BP ran successfully
  on the SI node. The BP runs successfully,
  but is run with full persistence and there are a few steps that
  have status "JMS Queued" and "BP queued"
  which apparently equate to WF_STATUS 11 and 12. These statuses
  are apparently being passed to Control Center
  as "inError true", which in turn causes a return code 8, thus
  causing alerts to be issued (a rule is set up to alert if return
  code is not 0).
  

Problem conclusion

• Description of fix: Added status codes 11 and 12 to a table in
  Control Center.  These entries indicate to treat these
  conditions as successful.
  

Temporary fix

• Fix published on 10/22/2012.
  

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

  STR CONTROL CEN

• Fixed component ID

  5725D0200

Applicable component levels

• R530 PSY

     UP

• R540 PSY

     UP