Limitations when Implementing Stored Procedures

Certain limitations apply when regarding implementing stored procedures.
carcudb2
Certain limitations apply when regarding implementing stored procedures.
Limitations regarding RC/Alter are as follows:
  • RC/Update Mode A is not supported for stored procedures.
  • A response of A to the DDL Execution Confirmation window is not supported for stored procedures.
  • The product does not support some changes that require an object drop/create due to an RC/Alter analysis being required in order to generate the necessary utility, drop, and create statements. This includes some changes where object interdependencies with other objects require an RC/Alter analysis to determine whether changes to other objects are needed. When a drop/create can be performed without an RC/Alter analysis, a DROP will be generated, followed by a CREATE; otherwise, no DDL is generated.
Stored procedure create, alter, and template limitations are as follows:
  • Stored procedures created with a CREATE or ALTER statement that is longer than 32767 bytes are not eligible for alteration or templating in CA RC/Update.
  • The SQL Body is not extracted from a CREATE or ALTER procedure statement for an alter or template.
  • Stored procedures cannot be created with an SQL Body that exceeds 32767 bytes.
  • Altering Language for an existing stored procedure will generate a drop/create.
  • Altering the TT option from NO to YES in the Parameter Declaration List is not supported and will cause bad DDL to be generated.
  • When creating or templating stored procedures, specifying YES for the TT option in the Parameter Declaration List is not supported and will cause bad DDL to be generated.
Drop limitations are as follows:
  • Drop Impact reporting is not supported.
  • You cannot drop stored procedures that have dependent objects.
  • Drop with Recovery is not supported for stored procedures, meaning that dropped stored procedures cannot be automatically recovered.
The following option limitations exist:
  • Comment is not supported and if set to Y will not generate COMMENT ON PROCEDURE.
  • Add Ver is not supported.
  • Active is not supported.
  • Decimal does not reflect the value stored in the DB2 catalog.
  • FOR UPDATE CLAUSE does not reflect the value stored in the DB2 catalog.
  • Date Format does not reflect the value stored in the DB2 catalog.
  • Time Format does not reflect the value stored in the DB2 catalog.
  • TT in the Parameter Declarations list cannot be altered from NO to YES during an alteration; otherwise, bad DDL will be generated.
Miscellaneous support limitations are as follows:
  • The Table Like clause is not currently supported.
  • The TT line command (Table Like) is disabled in the Parameter Declaration List.
  • ADD, REPLACE, and REGENERATE version is not currently supported for a native SQL stored procedure.
  • You cannot drop/create a native SQL stored procedure having multiple versions.
  • Altering any parameter declaration attribute on an existing native SQL stored procedure causes a drop/create.