DB2 for Z/OS and Os/390: Ready for Java by IBM Redbooks, Bart Steegmans

By IBM Redbooks, Bart Steegmans

Show description

Read or Download DB2 for Z/OS and Os/390: Ready for Java PDF

Best programming: programming languages books

Effektiv Java programmieren : [57 Regeln für eine professionelle Java-Programmierung]

Java-Handbücher neigen zum Wuchern und enden oftmals als fette Backsteine zum Abstützen anderer Bücher im Regal. Wer liest schon 1. two hundred Seiten wirklich durch? Da fällt ein Java-Buch von etwas über 2 hundred Seiten schon ins Auge. Beim Java lernen ist es nicht mit einer umfangreichen Referenz der Sprache selbst getan -- die Denke und die Konzepte dahinter wollen auch verstanden und umgesetzt werden.

Extra resources for DB2 for Z/OS and Os/390: Ready for Java

Sample text

Otherwise, you have to rerun them in order to rebind the affected packages after you make this change. Do as we say, not as we did. This option controls whether DB2 builds a DESCRIBE SQLDA when binding static SQL statements. YES means that DB2 does generate a DESCRIBE SQLDA at BIND time so that DESCRIBE requests for static SQL can be satisfied during execution. Specifying YES increases the size of some packages because the DESCRIBE SQLDA is now stored with each statically bound SQL SELECT statement.

The SMP/E installation steps are described in Chapter 6 of Application Programming Guide and Reference for Java, SG26-9932-03. As the Java area is a very dynamic area, please make sure you have the latest version of this publication. 2 Installing the Universal Driver on a z/OS or OS/390 platform At the time of writing of this publication, the Universal Driver was not generally available on the z/OS and OS/390 platform. On the z/OS platform, the Universal Driver will be part of the DB2 for z/OS V8 base code.

In this case, the Java application runs under Unix System Services (USS), and talks to DB2 through a Type 2 driver. A JDBC call is translated by the Type 2 driver into SQL statements, and executed through the RRS attachment facility by DB2. Figure 3-3. Local T2 connection 34 Part 1: Introduction Part 1: Introduction 35 As the application is local to the DBMS, and we use a Type 2 driver that can do 'native' calls to DB2; this configuration normally provides the best performance. You also use this configuration when running your WebSphere Application Server (WAS) on z/OS.

Download PDF sample

Rated 4.38 of 5 – based on 18 votes