On Fri, May 22, 2015 at 8:07 AM, Russell Witt <[email protected]> wrote:
> Ok, that brings up some follow-up questions. First of course is why do you > want an XML formatted copy of the TMC records? And second is do other > clients want to see an XML formatted copy of TMC records? > Actually, I didn't want XML. I originally just wanted to load the TMC into a PostgreSQL data base. Why? Because I love SQL as a quick way to make reports. Personal weirdness, I guess. I went to XML simply because it was relatively easy. And then to JSON because it was a simple change to emit JSON instead of XML. And that opens the data up to being manipulated using JavaScript in a web browser or via node.js . To me, this is "nice" simply because nobody yells at me for "wasting MSUs" when I run code on my Linux PC. I guess my post sort of went sideways. I was basically trying to make the point that _I_ like to get a the "raw" TMC data by "unloading" it with TMSBINQ instead of using CA-Earl, or TMSGRW, or by reading an IEBGENER copy of the actual TMC itself. I've been infected by the UNIX "try to use a textual file when possible" bug. It's also faster for me to code and debug. I prefer to leave the difficult coding to you and the other CA people. > > Russell Witt > > -- My sister opened a computer store in Hawaii. She sells C shells down by the seashore. If someone tell you that nothing is impossible: Ask him to dribble a football. He's about as useful as a wax frying pan. 10 to the 12th power microphones = 1 Megaphone Maranatha! <>< John McKown ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
