If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below.

 
Go Back  dBforums > Database Server Software > DB2 > Application Relations in DB2 V6.0 on S/390

Reply
 
LinkBack Thread Tools Search this Thread Display Modes
  #1 (permalink)  
Old 02-19-05, 04:01
tnssrini tnssrini is offline
Registered User
 
Join Date: Dec 2003
Posts: 9
Application Relations in DB2 V6.0 on S/390

Hi All,

We would like to know how to handle Application Relationships while downloading data from 500 tables in DB2 version 6 on S/390.
We know that we can use FILEAID/RDX on mainframes to do similar things, but the issue is it couldn't handle when the number of tables related are very high.
Is there any other way to download the data from tables which are associated with Application relations.

Please let us know asap if anyone has idea regarding this.

We have also BMC tool available on S/390.

Thanks in advance
Reply With Quote
  #2 (permalink)  
Old 02-19-05, 09:26
Marcus_A Marcus_A is offline
Registered User
 
Join Date: May 2003
Location: USA
Posts: 5,196
Can you explain what you mean by "application relations."
__________________
M. A. Feldman
IBM Certified DBA on DB2 for Linux, UNIX, and Windows
IBM Certified DBA on DB2 for z/OS and OS/390
Reply With Quote
  #3 (permalink)  
Old 02-20-05, 18:20
jacampbell jacampbell is offline
Registered User
 
Join Date: Jan 2005
Posts: 191
Princeton Softech has a tool "Move for DB2" on zOS. ("Move for databases" is their Oracle/SQL Server/DB2 LUW product.

I once wrote a "tool" (aka kludge) which basically
- user inserted starting keys into a start-key-table
- precanned SQL to derived the keys of all the rows to be unloaded (going down SQL or application RI chains, manipulating data formats as needed). Fortunately the only recursive loop I had to deal with only required a single iteration.
- precanned SQL then copied the required rows into export tables
- unload from the export tables.

There was no proper handling of table changes - had to be manually tracked and incorporated into SQL.

James Campbell
Reply With Quote
Reply

Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are On