× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.


  1.  Home
  2. MIDRANGE-L
  3. April 2016

Re: Thoughts/experiences with JSON/XML on DB2

Over the years my experience has been nearly unanimous: in the end, the old way has too many limitations. The new ways have to be implemented. In other words, a graceful exit from S/36 is the best choice. In my opinion.

On 4/1/2016 9:18 AM, Justin Taylor wrote:
Booth Martin:
--This is live data with new records being added daily.
--Extracting the non-structured data into a traditional RDBMS was my first thought. Then I thought that a NoSQL type approach might be better, since NoSQL was originally intended for use with non-structured data (although the authors probably never considered S/36 files).
--I'm not sure either type of extraction would be significantly more difficult than the other.

Rob Berendt:
--"Multiformat join logical file", those emulate the multiple record formats seen in S/36 files, correct? Does SQL support those?


As an Amazon Associate we earn from qualifying purchases.

This thread ...
Replies:
Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.