PI11352: SQL QUERY AND SQL COMMAND ACTIONS ATTRIBUTE "IS STORED PROCEDURE?" HAS NO APPARENT IMPACT

Rational Integration Tester 8.7
Rational Test Virtualization Server 8.7
Rational Performance Test Server 8.7
Rational Test Virtualization Server Fix Pack 1 (8.7.0.1) for 8.7
Rational Integration Tester Fix Pack 1 (8.7.0.1) for 8.7
Rational Performance Test Server Fix Pack 2 (8.7.0.2) for 8.7
Rational Integration Tester Fix Pack 2 (8.7.0.2) for 8.7
Rational Test Virtualization Server Fix Pack 2 (8.7.0.2) for 8.7
Rational Test Virtualization Server Fix Pack 3 (8.7.0.3) for 8.7
Rational Integration Tester Fix Pack 3 (8.7.0.3) for 8.7
Rational Performance Test Server Fix Pack 1 (8.7.0.1) for 8.7
Rational Integration Tester Fix Pack 4 (8.7.0.4) for 8.7
Rational Test Virtualization Server Fix Pack 4 (8.7.0.4) for 8.7
Rational Performance Test Server Fix Pack 4 (8.7.0.4) for 8.7
Rational Performance Test Server Fix Pack 3 (8.7.0.3) for 8.7

APAR status

• Closed as suggestion for future release.

Error description

• There appears to be no way to execute a stored procedure from
  the SQL Query Action, and a stored procedure can be executed
  (with the CALL command) from SQL Command Action regardless of
  the setting on this switch.
  

Local fix

• Use the SQL Command Action (or Stored Procedure Action) when
  calling a Stored Procedure.
  

Problem summary

Problem conclusion

Temporary fix

Comments

• It was not clear to users what at, if anything, the check box
  labelled "is stored procedure?" on the SQL Query Action actually
  does.
  
  An analysis of the code within Rational Integration Tester shows
  that when 'is stored procedure' is checked, the SQLQueryJob will
  use a JDBC callable statement instead of an 'ordinary' JDBC
  statement object. There is no code to explicitly set IN
  parameters, or to reference OUT parameters, so the procedure is
  assumed to return a single result set - which seems to be a
  reasonable assumption given the user is using a SQL query
  action.
  
  It is to be expected that that different JDBC drivers may handle
  this situation differently. Some might let you call a stored
  proc with a regular JDBC statement, others might insist that any
  invocation of a stored procedure is done using a callable
  statement.
  
  In version 8.7.0 of Rational Integration Tester hover text was
  added to this checkbox stating "Use JDBC callable statement
  (rather than ordinary JDBC statement)" to make its function
  clearer.
  

APAR Information

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

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

Fix information

Applicable component levels