RE: Thoughts/experiences with JSON/XML on DB2

Yes, it's a PF object, and I can build DDS LF's (but not SQL views) over it. Building LF's for each format would be easy, but I don't think that would give a lot of payoff.

I don't have an S/36 apps to worry about.



-----Original Message-----
From: Joe Roden [mailto:joejoe5161@xxxxxxx]
Sent: Friday, April 01, 2016 1:10 PM
To: midrange-l@xxxxxxxxxxxx
Subject: RE: Thoughts/experiences with JSON/XML on DB2

In a nutshell: My order history data is in a multi-format S/36 file (not sure the exact terminology). The format makes SQL incredibly difficult, and I'm looking for a way to make ad-hoc queries easier. I tried extracting it into DB2 tables. I ended up with five tables before I started looking for other options. From what I've read, I can extract each order into a JSON or XML document, store it in DB2 table, and then run queries over the DB2 table.

Is this multi-format S/36 file a *FILE object of type PF? can you DSPFFD YOURFILE and see a single field?
Sorry not familiar with S/36 stuff.
If so, you could build 25 logical files over it defining the individual format columns using subtring(SST) like this.

A R HEADERREC PFILE(YOURFILE)
A RECORDTYPE 1A SST(YOURFIELD 1 1)
A ORDERNUM 8A SST(YOURFIELD 2 8)
A S RECORDTYPE COMP(EQ 'A')

A R DETAILREC PFILE(YOURFILE)
A RECORDTYPE 1A SST(YOURFIELD 1 1)
A ORDERNUM 8A SST(YOURFIELD 2 8)
A LINENUM 3S 0 SST(YOURFIELD 10 3)
A S RECORDTYPE COMP(EQ 'B')

and so on for each LF. Then your S/36 application runs as usual and you can query the LFs with SQL or any query tool.