FWIW, the IBM Record Generator for Java (formerly: JZOS RecordGenerator) also processes ADATA records from either COBOL and HLASM and will generate Java mapping classes.
https://www.ibm.com/support/knowledgecenter/en/SSMQ4D_3.0.0/documentation/recgen_overview.html It also has a feature where you can parse the ADATA and generate an XML description of the ADATA. This might be interesting to leverage to generate mappings for other languages. You might also want process this to specify alternate types over the data. Kirk Wolf Dovetailed Technologies http://dovetail.com On Wed, Jul 18, 2018 at 5:00 PM, Paul Gilmartin < 00000014e0e4a59b-dmarc-requ...@listserv.uga.edu> wrote: > On 2018-07-18, at 11:42:43, Charles Mills wrote: > > > > Going from structs to DSECTs would make a lot of sense except that there > is > > no C equivalent of SYSADATA, so the utility would have to have its own > > built-in (partial) C compiler. Going from PL/X to DSECTs (or C headers!) > > makes a lot of (technical) sense. > > > I hadn't understood that CDESECT exploited SYSADATA. That's > a great advantage. > > > Generally. Of course HLASM is all but untyped. A might mean an integer > > constant, especially since A supports expressions while F somewhat > > inexplicably does not. You can code A(BUFF_LEN+7) but not F'BUFF_LEN+7'. > > > OTOH, > DC F'-2147483648' assembles successfully, while > DC A(-2147483648) gets a syntax error. > > A designer's perverse notion of completeness? > > -- gil >
