Fixes are available
APAR status
Closed as program error.
Error description
Abstract Using Deploy for Java Stored procedures in Rational Application Develpor v8.0.4.1 Data Tools to deploy to z/OS DB2 v10 failed indicating the SQLJ.ALTER_JAVA_PATH used by RAD deploy was not available. The z/OS DB2 v10 was migrated from v8.0 and is in Common Mode (CM). Problem: When attempting to do a deploy on Java Stored Procedure (SP) in the RAD v8 Data Tools it failed as follows: Error: --------------------------------------------------- Deploy {Some DB2 User Id}.PROCEDURE_MEK09 Running {Some DB2 User Id}.PROCEDURE_MEK09 - Deploy started. {Some DB2 User Id}.PROCEDURE_MEK09 - Created temporary working directory C: \Data\Moog\RAD8_DataWorkspace2\.metadata\.plugins\com.ibm.datato ols.db2. routines.deploy.ui\bld1341860387150. C:\Program Files\IBM\SQLLIB\java\jdk\bin\javac -classpath '.;C:\Program Files\IBM\SQLLIB\java\sqlj.zip;C:\IBM\SDPShared\plugins\com.ibm. datatools.db2_2.1.102.v20120412_2209\driver\db2jcc4.jar;C: \IBM\SDPShared\plugins\com.ibm.datatools.db2_2.1.102. v20120412_2209\driver\db2jcc4_license_cisuz.jar' com\{Some DB2 User Id}\{Some DB2 User Id}\PROCEDURE_MEK09_1.java {Some DB2 User Id}.PROCEDURE_MEK09 - Javac completed. C:\Program Files\IBM\SQLLIB\java\jdk\bin\jar cf spjar.jar com\{Some DB2 User Id}\{Some DB2 User Id}\PROCEDURE_MEK09_1.class {Some DB2 User Id}.PROCEDURE_MEK09 - Jar file created. DELETE FROM SYSIBM.SYSJAVAOPTS WHERE JARSCHEMA = '{Some DB2 User Id}' AND JAR_ID = 'DS_20120709013436' Call SQLJ.DB2_INSTALL_JAR (<<C:\Data\Moog\RAD8_DataWorkspace2\. metadata\.plugins\com.ibm.datatools.db2.routines.deploy. ui\bld1341860387150\spjar.jar>>, '{Some DB2 User Id}.DS_20120709013436', 0) {Some DB2 User Id}.PROCEDURE_MEK09 - SQLJ.DB2_INSTALL_JAR using Jar name {Some DB2 User Id}.DS_20120709013436 completed. Call ALTER_JAVA_PATH ('{Some DB2 User Id}.DS_20120709013436', '') NO AUTHORIZED SQLJ.ALTER_JAVA_PATH NAMED HAVING COMPATIBLE ARGUMENTS WAS FOUND. SQLCODE=-440, SQLSTATE=42884, DRIVER=4.8.86 {Some DB2 User Id}.PROCEDURE_MEK09 - Removed temporary working directory C: \Data\Moog\RAD8_DataWorkspace2\.metadata\.plugins\com.ibm.datato ols.db2. routines.deploy.ui\bld1341860387150. {Some DB2 User Id}.PROCEDURE_MEK09 - Deploy failed. {Some DB2 User Id}.PROCEDURE_MEK09 - Roll back completed successfully. --------------------------------------------------- The user also ran installation job DSNTRIN on their z/OS DB2 v10 and received this errormessage: DSNT005I DSNTRIN HAS SKIPPED CREATE PROCESSING OF PROCEDURE SQLJ.ALTER_JAVA_PATH, REASON: REQUIRES NEW FUNCTION MODE This is requirement was specified in redpiece: Data Studio and DB2 for z/OS Stored Procedures -Understand IBM Data Studio V2.2.1 packaging -- Use Data Studio with DB2 10 for z/OS stored procedures http://www.redbooks.ibm.com/redpieces/pdfs/redp4717.pdf Page 12 - 1.4.5 Setup for SQL and Java stored procedures. It shows the need to run DSNTIJRT which was also done. This is also covered in the RAD v8 Info Center - Prerequisites for developing routines that target DB2 for z/OS http://publib.boulder.ibm.com/infocenter/radhelp/v8/topic/com.ib m.datatools.routines.doc/topics/tprereqzos.html It was not possible to have the DB2 v10 catalog pick up certain SQLJ stored procedure routines. RE: DB2 v9 and v10 Info Center- v10: - SQLJ.ALTER_JAVA_PATH stored procedure http://publib.boulder.ibm.com/infocenter/dzichelp/v2r2/index.jsp ?topic=%2Fcom.ibm.db2z10.doc.java%2Fsrc%2Ftpc%2Fimjcc_sqljalter_ java_path.htm The problem is that in this case z/OS DB2 had been migrated from v8 to v10 and is not in New Function Mode (NFM). The DB2 is in Common Mode (CM) v8. SQLJ.ALTER_JAVA_PATH was introduced in z/OS DB2 v9. If the DB was migrated from v9 then it would be in CM v9 and any SQLJ routine introduces in v9 would be in the v10 catalog for common mode (CM) since it is not new function (NFM) for v10. The RAD v8.0 and v8.5 data tools appear to not check the product return code when the database connection is established to distinguish between z/OS DB2 v10 CMv8 and CMv9. If it is z/OS DB2 v10 CMv8, the data tools should use the v8 Deploy that does not make use of SQLJ.ALTER_JAVA_PATH, and should behave as if it is v8 when doing the deploy. Local Fix: Move to DB2 v10 New Function Mode (NFM) if that is an option. If not, then there is no workaround
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: * **************************************************************** * PROBLEM DESCRIPTION: * **************************************************************** * RECOMMENDATION: * **************************************************************** Deploying a Java Stored Procedure against a z/OS V10 CM8 server failed.
Problem conclusion
The fix for this APAR is included in Rational Application Developer v8.0.4.2.
Temporary fix
Comments
APAR Information
APAR number
PM68785
Reported component name
RATL APP DEV WI
Reported component ID
5724J1901
Reported release
804
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2012-07-12
Closed date
2012-12-15
Last modified date
2012-12-15
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fix information
Fixed component name
RATL APP DEV WI
Fixed component ID
5724J1901
Applicable component levels
R804 PSN
UP
[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSRTLW","label":"Rational Application Developer for WebSphere Software"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"8.0.4","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]
Document Information
Modified date:
15 December 2012