DB2 Development Center Advanced Topics for z/os

Transcription

1 IBM Software Group DB2 Development Center Advanced Topics for z/os Peggy Rader - peggyr@us.ibm.com Agenda Getting Started Environment Settings JDBC Driver Support Using Java SDK and SDK Multiple versions of SQL and Java SPs Miscellaneous February 2005 (c) IBM Corporation 1-2

2 Getting Started Development Center (DC) Included in Application Development Client in DB2 UDB for Windows,Linux and Unix V8.1 Fixpak 7 latest available at the time of this presentation Known as DC 8.1 Included in Application Development Client in DB2 UDB for Windows, Linux and Unix V8.2 Known as DC 8.2 DC 8.1 at FP7 is equal to DC 8.2 base level code Code name "Stinger" pre GA Most DC functions included in WSAD V5 (no SQL for z/os debugging support) RAD V6 (no SQL for z/os debugging support).net (SQL only, includes debugging) Getting Started... Development Center Overview Presentation Getting Started with the DB2 Development Center to Create SQL and Java SPs - 2 Parts ftp://ftp.software.ibm.com/software/db2storedprocedure/db2zos390/techdocs/getstarteddc.pdf Part 1 - Platform Neutral DB2 Application Development Tools Overview Development Center Prereqs Setup Development Center Overview Other Wizard Options Part 2 - z/os Specific including Setup Steps Development Center and z/os Stored Procedures Processing Overview Prereqs Setup DB2Build Utility SQL SP Debugger with DB2 for z/os V8 IBM Redbook - Chapter 29 Refreshed in November search for SG February 2005 (c) IBM Corporation 3-4

3 Environment Settings Debugger Set Java Debugger listening port (distributed DB2) Set SQL timeout value (distributed DB2 and z/os V8 DB2) Editor Specify options for editing source code for selected language Output Specify settings for results and refreshing of objects Process Specify settings for building, running and tracing User-assistance features Specify settings for field help and diagnostics Build options Specify settings for z/os and OS/390 SQL and Java SPs Select menu option Project->Environment Settings JDBC Driver Support In the beginning there was a single JDBC driver on OS/390 that was called the "JDBC/SQLJ Driver for OS/390" This driver can be used in Java applications and Java stored procedures that process on OS/390 and z/os only Supports type 2 connectivity February 2005 (c) IBM Corporation 5-6

4 JDBC Driver Support... Next came the Universal JDBC driver, sometimes referred to as the JCC driver Java Common Client This driver can be used in Java applications and Java stored procedures on DB2 for OS/390 V7 and DB2 for z/os V8 DB2 for Unix, Windows and Linux V8 Supports both Type 2 connectivity Type 4 connectivity JDBC Driver Support... To distinguish the new Universal JDBC driver from the original JDBC driver a renaming was done JDBC/SQLJ for OS/390 became known as the "Legacy JDBC driver" sometimes also known as the "Classic JDBC driver" February 2005 (c) IBM Corporation 7-8

5 JDBC Driver Support... Java stored procedures JDBC Dynamic *.class files SQLJ Static SQL *.class files *.ser file (serialized profile) Presence of a *.ser file created at when SP is "built" and the DB2PROFC or DB2SQLJCUSTOMIZE routine is run Development Center and JDBC Drivers 1 SERVER 2 GENERATED SP 3 CONNECTION z/os Server Java SQLJ DSNTJSPP uses Legacy JDBC Driver *.ser RUNTIME WLM SPAS Legacy JDBC driver //JAVAENV... DB2_HOME Uses JDBC Driver in 3 steps DC Developer No DSNTJSPP uses Universal JDBC Driver z/os V8 only *.ser Universal JDBC driver //JAVAENV... JCC_HOME End-User of Java SP February 2005 (c) IBM Corporation 9-10

6 DC and the JDBC Driver Combinations DC 8.1 Legacy Driver type 2 connectivity 1 Universal Driver type 2 connectivity 1 - Server Connection Y - Java SP Build (uses DSNTJSPP on z/os) Y - Runtime for Java JDBC 3 Y Y - Runtime for Java SQLJ Y Universal Driver type 4 connectivity 2 DC 8.2 = DC 8.1(FP7) - Server Connection Y Y Y - Java SP Build (uses DSNTJSPP on z/os) Y - Java SP Build (doesn't use DSNTJSPP on z/os) Y 4 - Runtime for Java JDBC 3 Y Y - Runtime for Java SQLJ Y Y 4 1. Requires DB2 Connect 2. Requires DB2 Connect License Only 3. Java JDBC SP significance at Runtime 4. Java SQLJ SP w/ Universal Driver only created on DB2 for z/os V8 DC 8.2 Build Process Using DSNTJSPP Windows Workstation Press Build - sqlj - javac - make.jar Start DC - Use Wizards to create new Java or import existing Java source - Add User Code After DSNTJSPP called z/os Calls DSNTJSPP DSNTJSPP z/os C SP Calls DSNTBIND z/os REXX SP for SQLJ SPs -CREATE PROCEDURE Perform Tasks Java SQLJ SP Generated using Legacy JDBC Driver - type 2 connectivity SETUP USS ENVIRONMENT DSNTJSPP.properties READ PROPERTIES FILE db2sqljjdbc.properties db2profc (SQLJ only) INSTALL or REPLACE JAR BIND PACKAGE (SQLJ only) Save options and source in DB2 Catalog February 2005 (c) IBM Corporation 11-12

7 DC 8.2 Build Process NOT Using DSNTJSPP Windows Workstation z/os - V8 only Java SQLJ SP Generated using Universal JDBC Driver - type 2 connectivity 3. - sqlj (sqlj only) - javac - jar files 4. db2sqljcustomize (sqlj only) DB2_INSTALL or DB2_REPLACE JAR z/os DB2 JDBC driver command DB2 supplied stored procedure 2. Press Build JDBC call using Server Connection JDBC Driver Save options and source in DB2 Catalog DB2 catalog call 1. Start DC - Use Wizards to create new Java or import existing Java source - Add User Code CREATE PROCEDURE DB2 catalog call How does DC decide to use DSNTJSPP or Not during Build Default determined Project->Environment Settings->Build options->java When Checkbox "checked" build uses DSNTJSPP WLM proc needs //JAVAENV DD specifying DB2_HOME Indicates Legacy JDBC driver When Checkbox "unchecked" build does NOT use DSNTJSPP WLM proc needs //JAVAENV DD specifying JCC_HOME Indicates Universal JDBC driver Default overridden During initial SP build from wizard->options->advanced On previously built SP from Properties->Build panel February 2005 (c) IBM Corporation 13-14

8 Select Default from Project->Environment Settings Build options->java Uncheck -> Build using DSNTJSPP WLM proc needs JCC_HOME in //JAVAENV WLM proc needs DB2_HOME in //JAVAENV Override Specific SP from Properties During initial Build or during Rebuild Select SP->Right Click->Properties->Build->Check Build using DSNTJSPP Optionally check Verbose build February 2005 (c) IBM Corporation 15-16

9 Java Software Development Kit (SDK) Usage Where are they used? Used during Build time By Development Center Used during Runtime By the WLM proc where the Java SP executes Java Methods used during Build time must be available in Java Runtime Environment (JRE) Otherwise - Execution error indicating mismatch EG. Using a Java method from a Java JRE Java SDK and SDK Determine which is available by looking at HFS From OMVS command prompt - Set Path SDK Default directory export PATH=/usr/lpp/java/IBM/J1.3/bin:$PATH SDK Default directory export PATH=/usr/lpp/java/IBM/J1.4/bin:$PATH Enter java -version or java -fullversion java version "1.3.1" Java(TM)2 runtime Environment,Standard Edition (build 1.3.1) Classic VM (build 1.3.1,J2RE IBM OS/390 Persistent Reusable VM build cm13 1s (JIT enabled:jitc)) No Support for SDK February 2005 (c) IBM Corporation 17-18

10 Java Software Development Kit Usage Build Time Using Legacy JDBC Driver with SYSPROC.DSNTJSPP Uses SDK on client Uses DSNTJSPP.properties file SDK on z/os JAVA_HOME environment variable specifies SDK1.3.1 or SDK1.4.1 SDK methods used must be available in both client and z/os SDK Using Universal JDBC Driver (Supported in DC in DB2 V8.2 only) Build uses SDK on workstation only Java Software Development Kit Usage... Build Time Default SDK included with Development Center..\sqllib\java\jdk DC 8.1 SDK default DC (DC 8.1 at FP7 level) SDK default Override default SDK takes 2 steps Specify JDK Level and Directory location Select JDK level from Database Connection February 2005 (c) IBM Corporation 19-20

11 Override SDK Default for Build Process 1. Specify JDK Level/Directory in Project->Environment Settings->Process-> Java Home Set JDK Level Directory 2. From Project View Select Database Connection->Properties -> Java Build Settings Select JDK Release Java Software Development Kit Usage... Run Time WLM Proc //JAVAENV DD statement selects SDK JAVA_HOME environment variable DB2 for OS/390 V7 Supports SDK in base product Supports SDK Requires APAR PQ76769 DB2 for z/os V8 Supports SDK and in base product February 2005 (c) IBM Corporation 21-22

12 Java Software Development Kit Usage... Runtime JAVAENV Statement Examples using Legacy JDBC driver SDK ENVAR("DB2_HOME=/usr/lpp/db2/db2710", "JAVA_HOME=/usr/lpp/java/IBM/J1.3", "DB2SQLJPROPERTIES=/u/DB7PU/db2sqljjdbc.properties"), MSGFILE(JSPDEBUG,,,,ENQ) SDK XPLINK(ON), ENVAR("DB2_HOME=/usr/lpp/db2/db2810", "JAVA_HOME=/usr/lpp/java/IBM/J1.4", "DB2SQLJPROPERTIES=/u/DB8AU/db2sqljjdbc.properties"), MSGFILE(JSPDEBUG,,,,ENQ) Supported with DB2 V7 in APAR PQ76769 Java Software Development Kit Usage... Runtime JAVAENV Statement Examples using Universal JDBC driver SDK ENVAR("JCC_HOME=/usr/lpp/db2/db2810/jcc", "JAVA_HOME=/usr/lpp/java/IBM/J1.3"), MSGFILE(JSPDEBUG,,,,ENQ) SDK XPLINK(ON), ENVAR("JCC_HOME=/usr/lpp/db2/db2810/jcc", "JAVA_HOME=/usr/lpp/java/IBM/J1.4"), MSGFILE(JSPDEBUG,,,,ENQ) Supported with DB2 V7 in APAR PQ76769 Included in base product with DB2 V8 February 2005 (c) IBM Corporation 23-24

13 Java Software Development Kit Usage... DB2 for OS/390 V7 APAR PQ76769 provides support for DB2 Universal JDBC Driver ** SDK SDK continues to be supported Removal of 200 parameter limit for Java stored procedures or Java UDFs ** SQLJ SPs No DC 8.1 or DC 8.2 support for Universal JDBC Driver JDBC SPs Can select Universal JDBC Driver at Runtime with //JAVAENV DD statement JCC_HOME envvar Multiple Versions of SQL or Java SPs When do you need multiple versions? Support for different resource requirements on one DB2 server Test, QA, Production all on same DB2 server using same SP name Multiple SDK support February 2005 (c) IBM Corporation 25-26

14 Multiple Versions of SQL SPs -> DSNTPSMP Create WLM proc for build process Use model of SDSNSAMP(DSN8WLMP) with updated definitions for //SQLLMOD //SQLDBRM //SQLCSRC //SYSEXEC (optionally if usermods on DSNTPSMP) Register additional copy of DSNTPSMP in DB2 Catalog Create copy of SYSPROC version to new Schema version Modify WLM ENVIRONMENT Create WLM proc for SQL SP execution //STEPLIB DD statement Includes dataset from //SQLLMOD DD from the build process Multiple Versions of SQL SPs -> DSNTPSMP... Different STEPLIB, DBRM and C Source Optionally, may need different SYSEXEC If changes needed to DSNTPSMP - would need multiple REXX EXECs TEST SYSIBM.SYROUTINES WLM PROC DB8ASQL1 - used for Build Process WLM PROC DB8ASQL5 - used for SQL SP Execution PROCEDURE SYSPROC.DSNTPSMP... WLM ENVIRONMENT DB8ASQL1 //SYSEXEC DD DISP=SHR,DSN=DB7PU.TEST.SDSNCLST **** //SQLDBRM DD DISP=SHR,DSN=DB7PU.TEST.DBRMLIB.DATA //SQLCSRC DD DISP=SHR,DSN=DB7PU.TEST.SRCLIB.DATA //SQLLMOD DD DISP=SHR,DSN=DB7PU.TEST.RUNLIB.LOAD //STEPLIB DD DISP=SHR,DB7PU.TEST.RUNLIB.LOAD QA SYSIBM.SYROUTINES WLM PROC DB8ASQL2 - used for Build Process WLM PROC DB8ASQL6 - used for SQL SP Execution PROCEDURE MYQA.DSNTPSMP... WLM ENVIRONMENT DB8ASQL2 //SYSEXEC DD DISP=SHR,DSN=DB7PU.QA.SDSNCLST **** //SQLDBRM DD DISP=SHR,DSN=DB7PU.QA.DBRMLIB.DATA //SQLCSRC DD DISP=SHR,DSN=DB7PU.QA.SRCLIB.DATA //SQLLMOD DD DISP=SHR,DSN=DB7PU.QA.RUNLIB.LOAD //STEPLIB DD DISP=SHR,DB7PU.QA.RUNLIB.LOAD February 2005 (c) IBM Corporation 27-28

15 Multiple Versions of Java SPs -> DSNTJSPP Using Legacy JDBC driver -> DSNTJSPP Create additional HFS mount point for DSNTJSPP.properties JAVA_HOME selects SDK db2sqljjdbc.properties Selects DBRMLIB Register additional copy of DSNTJSPP in DB2 Catalog Update RUNOPTs to point to new HFS mount point All versions of DSNTJSPP can run in "Same" WLM Environment No changes or additional copies of DSNTBIND needed Create WLM proc for Java SP execution //JAVAENV DD statement environment variable settings DB2_HOME for Legacy JDBC driver JCC_HOME for Universal JDBC driver JAVA_HOME for SDK Multiple versions of Java SPs -> DSNTJSPP... SDK Example SYSIBM.SYSROUTINES /u/db8au/sdk131/ DSNTJSPP.properties /u/db8au/sdk131/ db2sqljjdbc.propert ies WLM PROC DB8AJAV6 - used for Java SP Execution //JAVAENV DD statement PROCEDURE SYSPROC.DSNTJSPP... RUN OPTIONS 'POSIX(ON),ENVAR("HOME=/u/DB8AU/sdk131")' DB2_HOME=/usr/lpp/db2/db2810 JAVA_HOME=/usr/lpp/java/IBM/J1.3 DB2SQLJPROPERTIES=/u/DB8AU/sdk131/db2sqljjdbc.properties DB2SQLJSSID=DB8A DB2SQLJPLANNAME=DSNSQLJ LIBPATH=$DB2_HOME/lib CLASSPATH=.:$DB2_HOME/classes/db2j2classes.zip PATH=$JAVA_HOME/bin:$DB2_HOME/bin:/ STEPLIB=DB8A.SDSNEXIT:DB8A.SDSNLOAD:DB8A.SDSNLOD2 DB2SQLJDBRMLIB=DB8AU.SDK131.DBRMLIB ENVAR("DB2_HOME=/usr/lpp/db2/db2810", "JAVA_HOME=/usr/lpp/java/IBM/J1.3", "DB2SQLJPROPERTIES=/u/DB8AU/sdk131/db2sqljjdbc.properties"), MSGFILE(JSPDEBUG,,,,ENQ) February 2005 (c) IBM Corporation 29-30

16 Multiple versions of Java SPs -> DSNTJSPP... SDK Example SYSIBM.SYSROUTINES /u/db8au/sdk141/ DSNTJSPP.properties /u/db8au/sdk141/db2 sqljjdbc.properties WLM PROC DB8AJAV7 - used for Java SP Execution //JAVAENV DD statement PROCEDURE SDK141.DSNTJSPP... RUN OPTIONS 'POSIX(ON),ENVAR("HOME=/u/DB8AU/sdk141")' DB2_HOME=/usr/lpp/db2/db2810 JAVA_HOME=/usr/lpp/java/IBM/J1.4 DB2SQLJPROPERTIES=/u/DB8AU/sdk141/db2sqljjdbc.properties DB2SQLJSSID=DB8A DB2SQLJPLANNAME=DSNSQLJ LIBPATH=$DB2_HOME/lib CLASSPATH=.:$DB2_HOME/classes/db2j2classes.zip PATH=$JAVA_HOME/bin:$DB2_HOME/bin:/ STEPLIB=DB8A.SDSNEXIT:DB8A.SDSNLOAD:DB8A.SDSNLOD2 DB2SQLJDBRMLIB=DB8AU.SDK141.DBRMLIB XPLINK(ON), ENVAR("DB2_HOME=/usr/lpp/db2/db2810", "JAVA_HOME=/usr/lpp/java/IBM/J1.4", "DB2SQLJPROPERTIES=/u/DB8AU/sdk141/db2sqljjdbc.properties"), MSGFILE(JSPDEBUG,,,,ENQ) Select Different Build Utility Create New SP Select different Build utility on the Options->Advanced->z/OS Options->Build Options->Build utility Popdown list appears Example shows SQL Build Utility -- Java selection similar -- February 2005 (c) IBM Corporation 31-32

17 Select Different Build Utility... Update Existing SP From Project View, select SP-->Right click->properties->options->advanced->build Options->Build utility If previously created successfully, drop will fail as proc will have different datasets Popdown selection list Miscellaneous Topics Using code fragments Multiple SQL statements with a single result set Multiple SQL statements with multiple result sets Use DC to Copy/Paste SPs between servers Deploying SQL or Java stored procedures without recompiling February 2005 (c) IBM Corporation 33-34

18 Using Code Fragments - SQL Stored Procedures Header fragment Enter code that the wizard will insert in the stored procedure header Variable declaration fragment Enter code that the wizard will insert in the stored procedure variable declaration section Exception handlers fragment Enter code that the wizard will insert in the stored procedure exceptions handlers section Pre-return fragment Enter code that the wizard will insert in the stored procedure pre-return section Using Code Fragments - Java Stored Procedures Header fragment Enter code that the wizard will insert in the stored procedure header Imports fragment Enter code that the wizard will insert in the stored procedure import section Data fragment Enter code that the wizard will insert in the stored procedure data section Method fragment Enter code that the wizard will insert in the stored procedure method section February 2005 (c) IBM Corporation 35-36

19 Multiple SQL Statements with a Single Result Set Using the new wizard when creating SQL or Java stored procedures From the Definition panel, click the "..." to the right of the Statement setting # of Result sets Multiple SQL Statements with a Single Result Set On the SQL Statement panel, select Generate Multiple SQL statements Click the Add button Generates another SQL statement window Click OK to generate CASE statement code February 2005 (c) IBM Corporation 37-38

20 Multiple SQL Statements with a Single Result Set... Sample code generated for Java... public static void javatest2 (int whichquery,resultset []rs1 )throws SQLException,Exception switch (whichquery) { case 0: sql ="SELECT SCHEMA,NAME FROM SYSIBM.SYSROUTINES"; stmt =con.preparestatement(sql ); break; case 1: sql ="SELECT SCHEMA,NAME FROM SYSIBM.SYSROUTINES"; stmt =con.preparestatement(sql ); break; default: sql ="SELECT SCHEMA,NAME FROM SYSIBM.SYSROUTINES"; stmt =con.preparestatement(sql ); } Multiple SQL statements with Multiple Result Sets Repeat steps for multiple SQL statement shown previously From the Definition panel, select Result set Value Select Multiple For each SQL Statement, generated code creates one result set one cursor February 2005 (c) IBM Corporation 39-40

21 Multiple SQL Statements with Multiple Result Sets... Sample code generated for SQL CREATE PROCEDURE DEVL7083.SQLTEST2 (IN whichquery INTEGER ) RESULT SETS 2 LANGUAGE SQL COLLID DEVL7083 WLM ENVIRONMENT DB8ADS1 RUN OPTIONS 'NOTEST(NONE,*,*,*)' SQL Stored Procedure P1:BEGIN --Declare cursors DECLARE cursor1 CURSOR WITH RETURN FOR SELECT SCHEMA,NAME,WLM_ENVIRONMENT FROM SYSIBM.SYSROUTINES; DECLARE cursor2 CURSOR WITH RETURN FOR SELECT SCHEMA,NAME FROM SYSIBM.SYSROUTINES; --Cursor left open for client application OPEN cursor1; --Cursor left open for client application OPEN cursor2; END P1 Use DC to Copy/Paste SPs Between Servers Supports different platforms z/os to z/os, Windows, Linux, Unix or i5/os Windows to Windows, Linux, Unix, z/os or i5/os Unix to Unix, z/os, Linux, Windows or i5/os Linux to Linux, Unix, z/os, Windows or i5/os i5/os to i5/os, z/os, Windows, Linux or Unix Requires same DDL supported on source and target server Open Project Add DB Connection for Source and Target Server Select SP folder in Source Server Successfully create SP Select SP->Right Click->Copy Select SP folder on Target Server Right Click->Paste Modify SP as needed Windows SP to z/os requires WLM Environment added Build SP February 2005 (c) IBM Corporation 41-42

22 Use DC to Copy/Paste SPs Between Servers... Select DB8A z/os V8 server Create DEVL7083.JAVATEST SP Copy from z/os V8 Server Use DC to Copy/Paste SPs Between Servers... Select DB2G OS/390 DB2 V7 server Paste DEVL7083. JAVATEST Update WLM Environment to DB2GDEJ1 via SP properties Build SP February 2005 (c) IBM Corporation 43-44

23 Deploying SQL Stored Procedures Without Recompiling Currently, no direct support in DC or other IBM product Steps Registering the stored procedure Before registering the DDL, you may need to update the COLLID, WLM AE name, and the SCHEMA Copy the DBRMs from the source server and bind the DBRMs in the target server Copy the compiled SQL module into the production data set Grant execute authorization on the stored procedure See SG Appendix C.1.11 Sample REXX execs for configuration management Deploying SQL Stored Procedures Without Recompiling... Promotion of external stored procedures - Compile only once February 2005 (c) IBM Corporation 45-46

24 Deploying Java Stored Procedures Without Recompiling Currently, no direct support in DC or other IBM product DC installs the compiled Java class bytes and *.ser file (SQLJ only) in the DB2 catalog as a BLOB SYSIBM.SYSJARCONTENTS See SG Deploying SQL or Java stored procedures without recompiling * Java stored procedures * Sample code for steps on next 3 slides found in Redbook, Chapter Deploying Java Stored Procedures Without Recompiling... Extract Java SP from source DB2 server catalog FTP Java SP as JAR or *.CLASS (and *.ser files for SQLJ) from source to target DB2 server FTP DBRMs (SQLJ only) from source to target DB2 server Using Legacy JDBC Driver Bind DBRMs in target DB2 server February 2005 (c) IBM Corporation 47-48

25 Deploying Java Stored Procedures Without Recompiling... Register procedure in target DB2 server Modify DDL as necessary (COLLID, WLM ENVIRONMENT) On target DB2 server If SP executed from DB2 catalog Call SQLJ.INSTALL.JAR If SP executed from JVM Classpath Update Java SP execution WLM proc //JAVAENV DD statement classpath with JAR Grant EXECUTE authorization Deploying Java Stored Procedures Without Recompiling... Development Compile once - External procedures Production DB2 Catalog Extract SP Modified DDL Define stored procedure HFS Copy JAR or CLASS and SER HFS DBRMs Copy DB2 DBRM lib Bind DBRMs Yes Run from DB2 Catalog No Call SQLJ.INSTALL_JAR Update WLM proc DB2 Catalog //JAVAENV.. CLASSPATH February 2005 (c) IBM Corporation 49-50

26 DC FP7 Topics New DC 8.2 Support Generate SP for Universal JDBC driver on DB2 for z/os V8 Maximum size of JDBC and SQLJ stored procedures increased from 32 KB to 10 MB when using the Universal JDBC driver applies to both Java source and JAR New Environment Settings Provides default build for Java SPs Select Legacy JDBC driver or Universal JDBC driver Supports COLLID value Server Connection support for Build process Legacy JDBC Driver type 2 connectivity Universal JDBC Driver type 2 connectivity Universal JDBC Driver type 4 connectivity New New February 2005 (c) IBM Corporation 51-52

27 DC 8.2 used for Changing JDBC Drivers Applies to z/os DB2 V8 only Can use DC to migrate SP from Legacy JDBC driver to Universal Driver Select existing SP into DC Project that uses Legacy JDBC driver Modify SP Properties Select Build Options "Uncheck" use DSNTJSPP Update WLM proc to point to proc with //JAVAENV support for Universal JDBC driver e.g. JCC_HOME must point to driver, default ->/usr/lpp/db2/db2810/jcc Rebuild DC 8.2 Security Enhancements for Secondary Auth IDs Database Connection Options SQL Schema or SQL ID If it exists, used for SET CURRENT SQLID Package owner Build owner February 2005 (c) IBM Corporation 53-54

28 DC 8.2 Security Enhancements for Secondary Auth IDs... Package owner Used for package creating and package binding The package owner must hold all the privileges required to create and bind the package for the stored procedure, including BINDADD CREATE ON COLLECTION All privileges necessary for executing the SQL statements within the stored procedure package If no secondary authorization ID is specified here, the Logon Userid is used DC 8.2 Security Enhancements for Secondary Auth IDs Build owner Applies to the procedure registration in the DB2 catalog Must hold the CREATEIN ON SCHEMA privilege If no authorization name is specified for Build owner, the SQL ID becomes the default Build owner If no secondary authorization ID is specified here, the Logon Userid is used February 2005 (c) IBM Corporation 55-56

29 DC 8.1 or DC 8.2 and Secondary Auth IDs Explicitly update Bind Options during initial Build Options panel->advanced button->z/os Options->Build Options->expand Bind options Add OWNER(DBA3) PACKAGE(DSNJDBC) ACT(REP) OWNER(DBA3) DC SQL Debugger on z/os DB2 V8 Running SQL Debugger on multi-ip address client Like a home network SQL Debugger daemon selects default IP Address First in the list as presented in an IPCONFIG command prompt Port 4553 To override default requires FP8 IP address to use is the address to the MVS host that your DB2 V8 resides on If processing behind a firewall PORT address must be opened for input/output on the server FP8 required February 2005 (c) IBM Corporation 57-58

30 New Redbook on DB2 for z/os Stored Procedures SG Refreshed November 2004 Includes additional material - See Appendix C Additional Information IBM Websites DB2 Development Center Data Management Developer Domain DB2 for z/os Stored Procedure Info Redbooks SG : Developing Cross-Platform DB2 Stored procedures SG : Java Stored Procedures Learning by Example SG : DB2 for z/os Stored Procedures: Through the CALL and Beyond White Papers NEW JDBC drivers supported by the DB2 Stored Procedure Builder and DB2 Development Center for OS/390 and z/os Java SDKs for DB2 Development Center on OS/390 and z/os Getting Started - DB2 Dev Ctr to Create SQL and Java SPs - 2 Parts ftp://ftp.software.ibm.com/software/db2storedprocedure/db2zos390/techdocs/getstarteddc.pdf February 2005 (c) IBM Corporation 59-60