Hi,
I'm trying to find the most efficient way to access DB2 data on z/OS DB2 V8.
Any suggestions would be welcomed . . .
Situation:
1. Converting a VSAM file to DB2 on z/OS
2. VSAM file will be populated into 4 DB2 tables, 1 parent and 3 child
tables
3. COBOL program that accesses the VSAM file currently does a RANDOM READ on
the VSAM file which should be equal
to a single SELECT statement in SQL
4. Have 2 production DB2 environments: DB2B - true production - no adhoc
reporting allowed. DB2S - adhoc reporting allowed
5. New VSAM to DB2 tables will be located in DB2S
6. Have 1 program in DB2B that needs to access new tables in DB2S during
batch processing. Average now is 3000 to 5000 RANDOM
READs on the VSAM file
7. DB2B and DB2S are on the same CPU, I think SYSPLEX
Questions:
1. DBA recommended writing a Stored procedure to access data from DB2B to
DB2S, returning all rows and building temp table to store
data, and using temp table for program in DB2B, is this the most
efficient ? Argument is: a singlr SELECT would be processing serially and
would be
causing excessive MIPS . . . not taking advantage of the SET PROCESSING
2.Would it be more efficient to have a fully qualified SELECT like SELECT
column from DB2S.OWNER.TABL E_NAME to access the other DB2 subsystem?
3 Would it be more efficient to have a CONNECT TO and then a SELECT
statement for all RANDOM READs and then a DISCONNECT ?
I'm trying to find the most efficient way to access DB2 data on z/OS DB2 V8.
Any suggestions would be welcomed . . .
Situation:
1. Converting a VSAM file to DB2 on z/OS
2. VSAM file will be populated into 4 DB2 tables, 1 parent and 3 child
tables
3. COBOL program that accesses the VSAM file currently does a RANDOM READ on
the VSAM file which should be equal
to a single SELECT statement in SQL
4. Have 2 production DB2 environments: DB2B - true production - no adhoc
reporting allowed. DB2S - adhoc reporting allowed
5. New VSAM to DB2 tables will be located in DB2S
6. Have 1 program in DB2B that needs to access new tables in DB2S during
batch processing. Average now is 3000 to 5000 RANDOM
READs on the VSAM file
7. DB2B and DB2S are on the same CPU, I think SYSPLEX
Questions:
1. DBA recommended writing a Stored procedure to access data from DB2B to
DB2S, returning all rows and building temp table to store
data, and using temp table for program in DB2B, is this the most
efficient ? Argument is: a singlr SELECT would be processing serially and
would be
causing excessive MIPS . . . not taking advantage of the SET PROCESSING
2.Would it be more efficient to have a fully qualified SELECT like SELECT
column from DB2S.OWNER.TABL E_NAME to access the other DB2 subsystem?
3 Would it be more efficient to have a CONNECT TO and then a SELECT
statement for all RANDOM READs and then a DISCONNECT ?