Hi All,
If a dataset is created using a 2 node config file, then should it always be read by a 2 node config file ideally?. If needed to be read by > 2 node config file (3 or more), then is there a workaround?
Your inputs are greatly appreciated,
Whale.
Dataset Read/Write
Moderators: chulett, rschirm, roy
-
- Premium Member
- Posts: 1255
- Joined: Wed Feb 02, 2005 11:54 am
- Location: United States of America
Dataset Read/Write
Anything that won't sell, I don't want to invent. Its sale is proof of utility, and utility is success.
Author: Thomas A. Edison 1847-1931, American Inventor, Entrepreneur, Founder of GE
Author: Thomas A. Edison 1847-1931, American Inventor, Entrepreneur, Founder of GE
You can always read it with a higher configuration - just make sure that the configuration includes the same nodes that created the DataSets.
The point here is that a data file (containing the actual data that is loaded in the DataSet) is created on each node defined in the configuration file used to create the DataSet. When reading the DataSet - all the data files for that DataSet should be accessible to the Configuration used to read.
The point here is that a data file (containing the actual data that is loaded in the DataSet) is created on each node defined in the configuration file used to create the DataSet. When reading the DataSet - all the data files for that DataSet should be accessible to the Configuration used to read.
------------------
Aneesh
Aneesh
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
... which means that all the nodes named in the configuration file with which it was created must be accessible under the new configuration file's regime. The control file (blah.ds) contains the locations of the data files, though not readily in human-readable format.
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.