I received the following message when I switched the reference DB2 Connector from Normal to Sparse
main_program: Data set, file set, or file "TCRSTAT_OUT_ref:TCRSTAT_TEST_ref_lnk.v": Non-pipe (or non-virtual data set) with .v in its name
Data set, file set, or file "TCRSTAT_OUT_ref:TCRSTAT_TEST_ref_lnk.v": Non-pipe (or non-virtual data set) with .v in its name
We are dealing with large volumes and I assumed that this would be the optimal way for the SCD to function.
I read a few posts and one suggested, hash partitioning. I tried it and it didn't work.
Does Sparse Lookups work with the SCD stage.
Thanks
SCD - Sparse Lookup - DB2
Moderators: chulett, rschirm, roy
SCD - Sparse Lookup - DB2
Jim Stewart
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact: