IT31801: SCHEDULED REPORT FAILS WITH "A BIRT EXCEPTION OCCURRED."

APAR status

• Closed as program error.

Error description

• When the VM SLA Policy RPO Compliance or Database SLA Policy
  RPO Compliance reports are run via the scheduled option, they
  can fail with:
  
  Fail to execute script in function
  __bm_onFetch(). Source:
  ------
  " +
  mapOffloadSLAName.put(row["id"]
  row["name"]);
  mapOffloadSLASchedule.put(row["id"]
  row["ScheduleSLA"]);
  mapOffloadSLARPO.put(row["id"]
  row["RPOinMilliseconds"]);if(row["schedule"] !=
  null)
  OffloadSLAsArray.add(row["id"]); + "
  -----
  A BIRT
  exception occurred. See next exception for more
  information.
  ReferenceError: "OffloadSLAsArray" is not defined.
  (/report/data-sets/oda-data-set[@id="10595"]/method[@name="onFet
  ch"]#6)
  
  Running the report manually works successfully.
  
  
  Versions affected: 10.1.5
  
  Keywords: TS003246487
  

Local fix

• Run the report manually
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * IBM Spectrum Protect Plus levels 10.1.5.                     *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  * See ERROR DESCRIPTION                                        *
  ****************************************************************
  * RECOMMENDATION:                                              *
  * Apply fixing level when available.  This problem is          *
  * currently projected to be fixed in IBM Spectrum Protect Plus *
  * levels 10.1.5 patch 1 and 10.1.6. Note that this is subject  *
  * to change at the discretion of IBM.                          *
  ****************************************************************
  

Problem conclusion

• IBM Spectrum Protect Plus has been updated to correct the
  problem. The BIRT exception which occurred due to a typo in the
  declaration of an array list 'offloadSLAsArray' which started
  with a capital letter instead of a small letter, was fixed and
  will no longer occur when the Database/VM SLA RPO Compliance
  reports are run as part of scheduled jobs.
  

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:

Modules/Macros

• reports
  

Fix information

• Fixed component name

  SP PLUS

• Fixed component ID

  5737SPLUS

Applicable component levels