When do we use Dump option in Dlinks?

[Preethi]

Hi All,

Can anyone tell me the usage of Dump option in Dlinks with an example?

And also scenario where we use Dcube Allocation?

Thanks in Advance....


Regards,
Preethi

[andyhofer]

When the source contains too much data for the target to take, some of the data will be rejected. You can capture this rejected data by enabling one of the "Dump" options. These are

Ignore - Does not record the data rejected (Default)
Edit - This displays the dump data in a seperate table. You can look at this table but you cannot save it, but you can copy it into Clipboard and paste it into Excel for viewing
Print - Creates a print file of the data
File - Allows you to save the rejected data to a text file, you will be prompted to where you want to save the file

I don't think an example is necessary, as it's all about the source containing too much data for the target to handle.

Hope that helps. your question has helped me understand it a lot better.

Andy

[Preethi]

Thank you, Andy.

Can you tell me about Dcube Allocation where exactly we use it and how it is different from other allocations?

Preethi

[andyhofer]

Are you asking if you can use a D-Cube as an allocation table, if so the answer is yes, but to do so you need to reduce the D-Cube to a two-dimensional slice. The setup needs to be the same as an A-Table.

Andy

[rturpyn]

The benefit to using a Dcube Allocation is that you can use Dlinks to populate/update the allocation within the Dcube.  I have not found a way to automate updating A-Tables.

[vishalbhandari]

Just to add, A- Table update can be automated if it is refreshed from ODBC.

It works in our environment