IBM Support

SE69933 - OSP-DB RECURSIVE USE OF RUNSQL NOT ALLOWED BUT MESSAGE NOT CLEAR

Subscribe to this APAR

By subscribing, you receive periodic emails alerting you to the status of the APAR, along with a link to the fix after it becomes available. You can track this item individually or track all items by product.

Notify me when this APAR changes.

Notify me when an APAR for this component changes.

 APAR (Authorized Program Analysis Report)

Abstract

OSP-DB RECURSIVE USE OF RUNSQL NOT ALLOWED BUT MESSAGE NOT CLEAR

Error Description

When using the RUNSQL or RUNSQLSTM commands, recursive          
processing is disallowed but no message is issued indicating    
that the second call returned without processing.              
                                                               
For example:                                                    
                                                               
Create procedure test_run                                      
begin                                                          
call qsys2.qcmdexc('RUNSQL SQL(''create schema foo123'')        
commit(*NONE)');                                                
end;                                                            
                                                               
Then call this procedure from a RUNSQL command:                
                                                               
runsql sql('call test_run()') commit(*NONE)                    
                                                               
An SQL9010 message is issued that indicates that the RUNSQL    
command failed, but you don't know why or which of the RUNSQL  
commands failed.                                                
                                                               
Error Description                                              

Problem Summary

When using the RUNSQL or RUNSQLSTM commands, recursive          
processing is disallowed but no message is issued indicating    
that the second call returned without processing.              
                                                               
For example:                                                    
                                                               
Create procedure test_run                                      
begin                                                          
call qsys2.qcmdexc('RUNSQL SQL(''create schema foo123'')        
commit(*NONE)');                                                
end;                                                            
                                                               
Then call this procedure from a RUNSQL command:                
                                                               
runsql sql('call test_run()') commit(*NONE)                    
                                                               
An SQL9010 message is issued that indicates that the RUNSQL    
command failed, but you don't know why or which of the RUNSQL  
commands failed.                                                
                                                               
Error Description                                              

Problem Conclusion

When a RUNSQL or RUNSQLSTM command is recursively called, a new
SQL9024 message will be issued to indicate that the recursive  
call was not run.                                              

Temporary Fix

Comments

Circumvention


PTFs Available

R720 SI68304   9123
R730 SI68303   9116

Affected Modules

         
         

Affected Publications

Summary Information

Status............................................ CLOSED PER
HIPER........................................... No
Component.................................. 5770SS1DB
Failing Module.......................... RCHMGR
Reported Release................... R730
Duplicate Of..............................




System i Support

IBM disclaims all warranties, whether express or implied, including, but not limited to, the implied warranties of merchantability and fitness for a particular purpose. By furnishing this document, IBM grants no licenses to any related patents or copyrights. Copyright © 1996,1997,1998, 1999, 2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009, 2010, 2011, 2012, 2013, 2014, 2015, 2016, 2017, 2018, 2019 IBM Corporation. Any trademarks and product or brand names referenced in this document are the property of their respective owners. Consult the Terms of use link for trademark information

[{"Type":"MASTER","Line of Business":{"code":"LOB57","label":"Power"},"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SWG60","label":"IBM i"},"Platform":[{"code":"PF012","label":"IBM i"}],"Version":"7.2.0"},{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG15Q","label":"APARs - OS\/400 General"},"Component":"","ARM Category":[],"Platform":[{"code":"PF012","label":"IBM i"}],"Version":"V7R1M0;V7R2M0;V7R3M0","Edition":"","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
17 May 2019