Forum Post: RE: 00271203 (Rocket Software Inc) - Customize OVS to run for zSQL DB2...

Status
Not open for further replies.
N

Neelima

Guest
Hi Brian, Customer wants to make the following changes to the OVS for testing SQL92 DB2 1. Do not DROP and CREATE tables as was done for DB2 OVS. 2. SQL92 DB2 should behave similar to VSAMCICS, IMS for SQL92. There will be the same DELETE and INSERT when the Recreate Tables option is selected. The tables will be mapped as 05DGTABLE which will be mapped from SOVS05.GTABLE O5DITABLE which will be mapped from SOVS05.ITABLE Is this requirement possible? If so, could you explain how can this be done? Thanks & Regards, Neelima From: Brian Derwart [mailto:bounce-briand@community.progress.com] Sent: Wednesday, April 30, 2014 10:07 PM To: IF.DD.CON@community.progress.com Subject: RE: 00271203 (Rocket Software Inc) - Customize OVS to run for zSQL DB2 (3-Question/Inconvenience) ref:_00D307FS._500a0gvpVE:ref RE: 00271203 (Rocket Software Inc) - Customize OVS to run for zSQL DB2 (3-Question/Inconvenience) ref:_00D307FS._500a0gvpVE:ref Reply by Brian Derwart Neelima, I’m not sure what you mean by the “latest version of OVS”. I do not believe that we have added any tables to the OVS test suite for use in testing DB2. I connected to one of the QA test machines and issued a qualified SQLTables call to get the following table list: "TABLE_CAT", "TABLE_SCHEM", "TABLE_NAME", "TABLE_TYPE", "REMARKS" Null , "ODBC05", "GALIAS", "ALIAS", "" Null , "ODBC05", "GLOBTEMP", "GLOBAL TEMPORARY", "" Null , "ODBC05", "BINTABLE", "TABLE", "" Null , "ODBC05", "BITABLE", "TABLE", "" Null , "ODBC05", "BTABLE", "TABLE", "" Null , "ODBC05", "CTABLE", "TABLE", "" Null , "ODBC05", "CTABLE2", "TABLE", "" Null , "ODBC05", "CTABLE3", "TABLE", "" Null , "ODBC05", "CTABLE4", "TABLE", "" Null , "ODBC05", "DATTABLE", "TABLE", "" Null , "ODBC05", "DCTABLE", "TABLE", "" Null , "ODBC05", "DCTABLE2", "TABLE", "" Null , "ODBC05", "DCTABLE3", "TABLE", "" Null , "ODBC05", "DTABLE", "TABLE", "" Null , "ODBC05", "FTABLE", "TABLE", "" Null , "ODBC05", "GBDEF1", "TABLE", "" Null , "ODBC05", "GBLTABLE1", "TABLE", "" Null , "ODBC05", "GBLTABLE2", "TABLE", "" Null , "ODBC05", "GBTRTABLE1", "TABLE", "" Null , "ODBC05", "GBTRTABLE2", "TABLE", "" Null , "ODBC05", "GBTZTABLE", "TABLE", "" Null , "ODBC05", "GBULK1", "TABLE", "" Null , "ODBC05", "GBULK2", "TABLE", "" Null , "ODBC05", "GBULK3", "TABLE", "" Null , "ODBC05", "GBXMLTABLE", "TABLE", "" Null , "ODBC05", "GFORCASC", "TABLE", "" Null , "ODBC05", "GFORREST", "TABLE", "" Null , "ODBC05", "GLIMITS", "TABLE", "" Null , "ODBC05", "GLTABLE", "TABLE", "" Null , "ODBC05", "GLTABLE2", "TABLE", "" Null , "ODBC05", "GLTABLE3", "TABLE", "" Null , "ODBC05", "GLTABLE4", "TABLE", "" Null , "ODBC05", "GPRIM", "TABLE", "" Null , "ODBC05", "GPRIM2", "TABLE", "" Null , "ODBC05", "GTABLE", "TABLE", "OVS Primary Table" Null , "ODBC05", "GTABLE2", "TABLE", "" Null , "ODBC05", "GTABLE3", "TABLE", "" Null , "ODBC05", "GTABLE4", "TABLE", "" Null , "ODBC05", "GUBULK1", "TABLE", "" Null , "ODBC05", "GUBULK2", "TABLE", "" Null , "ODBC05", "GUBULK3", "TABLE", "" Null , "ODBC05", "ITABLE", "TABLE", "" Null , "ODBC05", "LCTABLE2", "TABLE", "" Null , "ODBC05", "LVBTABLE", "TABLE", "" Null , "ODBC05", "LVTABLE", "TABLE", "" Null , "ODBC05", "NTABLE", "TABLE", "" Null , "ODBC05", "NTABLE2", "TABLE", "" Null , "ODBC05", "RTABLE", "TABLE", "" Null , "ODBC05", "SITABLE", "TABLE", "" Null , "ODBC05", "T1", "TABLE", "" Null , "ODBC05", "T2", "TABLE", "" Null , "ODBC05", "T3", "TABLE", "" Null , "ODBC05", "T4", "TABLE", "" Null , "ODBC05", "T5", "TABLE", "" Null , "ODBC05", "TIMTABLE", "TABLE", "" Null , "ODBC05", "TITABLE", "TABLE", "" Null , "ODBC05", "TSTABLE", "TABLE", "" Null , "ODBC05", "TSTABLE2", "TABLE", "" Null , "ODBC05", "TSTABLE3", "TABLE", "" Null , "ODBC05", "UNATABLE", "TABLE", "" Null , "ODBC05", "UNILOB", "TABLE", "" Null , "ODBC05", "UTABLE1", "TABLE", "" Null , "ODBC05", "UTABLE2", "TABLE", "" Null , "ODBC05", "VBTABLE", "TABLE", "" Null , "ODBC05", "VCTABLE2", "TABLE", "" Null , "ODBC05", "VTABLE", "TABLE", "" Null , "ODBC05", "WCTABLE", "TABLE", "" Null , "ODBC05", "WCTABLE2", "TABLE", "" Null , "ODBC05", "WCTABLE3", "TABLE", "" Null , "ODBC05", "WCTABLE4", "TABLE", "" Null , "ODBC05", "WLTABLE", "TABLE", "" Null , "ODBC05", "WLTABLE4", "TABLE", "" Null , "ODBC05", "WLVTABLE", "TABLE", "" Null , "ODBC05", "WVCTABLE2", "TABLE", "" Null , "ODBC05", "WVTABLE", "TABLE", "" Null , "ODBC05", "glower", "TABLE", "" Null , "ODBC05", "GVIEW1", "VIEW", "" Null , "ODBC05", "GVIEW2", "VIEW", "" Null , "ODBC05", "GVIEW3", "VIEW", "" I know a few of the catalog function gens also create/drop a table named G_ABLE or G_TABLE. The DB2 specific gen also creates/drops the following tables for DB2 zOS: CREATE TABLE TSPRECTAB(ts_col timestamp(x), tswtz_col timestamp(x) with time zone) I could be missing a small number of other tables that are created at runtime, but this list should be mostly complete. Regards, Brian From: ngannava [ mailto:bounce-ngannava@community.progress.com ] Sent: Monday, April 28, 2014 8:52 PM To: IF.DD.CON@community.progress.com Subject: FW: 00271203 (Rocket Software Inc) - Customize OVS to run for zSQL DB2 (3-Question/Inconvenience) ref:_00D307FS._500a0gvpVE:ref FW: 00271203 (Rocket Software Inc) - Customize OVS to run for zSQL DB2 (3-Question/Inconvenience) ref:_00D307FS._500a0gvpVE:ref Reply by ngannava Customer\Tier: Rocket Software\ Tier 3 Product: Rocket Shadow for ODBC 7.3 From: ngannava [ mailto:bounce-ngannava@community.progress.com ] Sent: Tuesday, April 29, 2014 6:17 AM To: IF.DD.CON@community.progress.com Subject: 00271203 (Rocket Software Inc) - Customize OVS to run for zSQL DB2 (3-Question/Inconvenience) ref:_00D307FS._500a0gvpVE:ref 00271203 (Rocket Software Inc) - Customize OVS to run for zSQL DB2 (3-Question/Inconvenience) ref:_00D307FS._500a0gvpVE:ref Thread created by ngannava Customer\Tier: Rocket Software Product: Tier 3 Rocket Software would like to know the names of the zSQL DB2 tables that OVS will use in the latest version. Background Information: They customize OVS to run for zSQL DB2. Currently when running OVS test suite, the tables are dropped and recreated each time. They need OVS to be able to run the new zSQL DB2 tables. If the names of the zSQL DB2 tables can be obtained that OVS will use in the new version, they can create them and OVS should be able to run all the tests using these new table names. Similar to the customizations done for zSQL IMS and VSAM I checked in documentation and I did not find any information on this. Could you let me know the names of zSQL tables that OVS will use in the latest version? Thanks & Regards, Neelima Stop receiving emails on this subject. Flag this post as spam/abuse. Stop receiving emails on this subject. Flag this post as spam/abuse. Stop receiving emails on this subject. Flag this post as spam/abuse.

Continue reading...
 
Status
Not open for further replies.
Top