IV58616: DIRECTSQL EXECUTE CAUSES EXCEPTION IN POLICY EXECUTION

6.1.1-TIV-BSM-FP0004-windows
6.1.1-TIV-BSM-FP0004-zlinux
6.1.1-TIV-BSM-FP0004-solaris
6.1.1-TIV-BSM-FP0004-linux
6.1.1-TIV-BSM-FP0004-aix
6.1.1-TIV-NCI-FP0004-windows
6.1.1-TIV-NCI-FP0004-zlinux
6.1.1-TIV-NCI-FP0004-solaris
6.1.1-TIV-NCI-FP0004-aix
6.1.1-TIV-NCI-FP0004-linux
6.1.1-TIV-BSM-FP0003-aix
6.1.1-TIV-NCI-FP0003-zlinux
6.1.1-TIV-NCI-FP0003-windows
6.1.1-TIV-NCI-FP0003-solaris
6.1.1-TIV-NCI-FP0003-linux
6.1.1-TIV-NCI-FP0003-aix
6.1.1-TIV-BSM-FP0003-zlinux
6.1.1-TIV-BSM-FP0003-windows
6.1.1-TIV-BSM-FP0003-solaris
6.1.1-TIV-BSM-FP0003-linux
6.1.1-TIV-BSM-FP0002-windows
6.1.1-TIV-BSM-FP0002-zlinux
6.1.1-TIV-BSM-FP0002-solaris
6.1.1-TIV-BSM-FP0002-aix
6.1.1-TIV-BSM-FP0002-linux
6.1.1-TIV-NCI-FP0002_zlinux
6.1.1-TIV-NCI-FP0002_windows
6.1.1-TIV-NCI-FP0002_solaris
6.1.1-TIV-NCI-FP0002_linux
6.1.1-TIV-NCI-FP0002_aix
IBM Tivoli Netcool/Impact V6.1.1 Fix Pack 2 (6.1.1-TIV-NCI-FP0002)
IBM Tivoli Business Service Manager V6.1.1 Fix Pack 3(6.1.1-TIV-BSM-FP0003)
IBM Tivoli Netcool/Impact V6.1.1 Fix Pack 3 (6.1.1-TIV-NCI-FP0003)
IBM Tivoli Netcool/Impact V6.1.1 Fix Pack 4 (6.1.1-TIV-NCI-FP0004)
IBM Tivoli Business Service Manager V6.1.1 Fix Pack 4(6.1.1-TIV-BSM-FP0004)
IBM Tivoli Netcool/Impact V6.1.1 Fix Pack 5 (6.1.1-TIV-NCI-FP0005)
IBM Tivoli Business Service Manager V6.1.1 Fix Pack 5(6.1.1-TIV-BSM-FP0005)

APAR status

• Closed as program error.

Error description

• Customer's code causes issue with exception handling when doing
  an execute.  Customer's policy code:
  ___________________________________________________
  
  function suppressAlarmAction (suppressAlarm, ticketNumber) {
      sqlString = "execute WS_Clear_Action_Automation(" +
          suppressAlarm.Serial +
          ", 'netcool', 'Impact_" + ticketNumber + "')";
  
      DirectSQL('NetcoolOS', sqlString, True);
  
  ___________________________________________________
  
  Observed Exception:
  
  WS_Clear_Action_Automation_Bulk([84671294,84653468,84619362,8466
  5892,84606720,84660973,84673155,84704341,84696763,84698986,84662
  979,84648628,84607318,84607253,84637723,84648715,84610165,846184
  02], 'netcool', 'Impact_WS_Master_Alarms_Customer')
  java.sql.SQLException: JZ0R2: No result set for this query.
   at com.sybase.jdbc3.jdbc.ErrorMessage.raiseError(Unknown
  Source)
   at com.sybase.jdbc3.jdbc.SybStatement.queryLoop(Unknown Source)
   at com.sybase.jdbc3.jdbc.SybStatement.executeQuery(Unknown
  Source)
   at com.sybase.jdbc3.jdbc.SybStatement.executeQuery(Unknown
  Source)
   at
  com.micromuse.common.datasource.JDBCVirtualStatement$ResultSetEx
  ecutor.doit(JDBCVirtualStatement.java:259)
   at
  com.micromuse.common.util.TimedExecutor$CallableTransBlockAdapte
  r.call(TimedExecutor.java:112)
   at
  com.micromuse.common.util.concurrent.NamedDelegatingCallable.cal
  l(NamedDelegatingCallable.java:71)
   at
  java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:31
  4)
   at java.util.concurrent.FutureTask.run(FutureTask.java:149)
   at
  com.micromuse.common.util.concurrent.TrackingExecutor$1.run(Trac
  kingExecutor.java:105)
   at
  java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoo
  lExecutor.java:897)
   at
  java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExe
  cutor.java:919)
   at java.lang.Thread.run(Thread.java:738)
  29 Jan 2014 04:28:19,282 WARN  [JDBCVirtualStatement] Bad
  connection
  java.sql.SQLException: JZ0R2: No result set for this query.
  
  ________________________________________________________
  
  Exception handling in policy does not mitigate the DSA
  disconnecting after policy executes.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * All Impact Users                                             *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  * When runing the DirectSQL function with SQL that contains    *
  * "execute" an error will be generated in the server log file. *
  ****************************************************************
  * RECOMMENDATION:                                              *
  * The SQL will run, but the error in the log is misleading.    *
  * The error can be ignored.                                    *
  ****************************************************************
  When the "execute" statement is run with the DirectSQL function,
  it is run as a "select" statement instead of as an "update"
  statement.
  

Problem conclusion

• Changed to run the "execute" command correctly so that the error
  message is not generated.
  
  The fix for this APAR is contained in the following maintenance
  package:
  
  |Fix Pack|6.1.1-TIV-NCI-FP0002
  

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

• UNKNOWN
  

Fix information

• Fixed component name

  NC/IMPACT OBJSE

• Fixed component ID

  5724O59OS

Applicable component levels

• R611 PSY

     UP