RE: Thoughts/experiences with JSON/XML on DB2

This was in common use in the S36 days. There wasn't a RDBMS option, flat files in arrival sequence ruled the day. To deal with that, you will have to give records a primary key as a part of normalizing the database. Though Rob's minimalistic solution wouldn't support that directly.

Mark Murphy
STAR BASE Consulting, Inc.
mmurphy@xxxxxxxxxxxxxxx


-----Justin Taylor <JUSTIN@xxxxxxxxxxxxx> wrote: -----
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
From: Justin Taylor <JUSTIN@xxxxxxxxxxxxx>
Date: 04/01/2016 12:31PM
Subject: RE: Thoughts/experiences with JSON/XML on DB2


Rob Berendt:
How would you handle sequence? Meaning that a part or configuration of a given record type applies to the parent item which is the most recent record of a different given record type .


Mike Jones:
You're correct that some formats could be combined, but other formats would actually require multiple tables.


Vernon Hamberg:
This a PF. The last position is a letter to indicate the record type. The old-school way is to use different I-specs based on that letter. Procedures don't allow I-specs, so now I read into a generic DS, and then load it into the appropriate DS based on the last letter in the generic DS.

I'm not clear on the exact terminology since I wasn't around when this stuff was in common usage (assuming of course it was ever in common usage).