Just to close the loop on this, I completed sufficient record conversions to
satisfy my requirement using the method described below. I would post a longer
example here but I think LISTSERV would make hash out of it. Here is a
three-line example of my resulting C header fields. Hopefully LISTSERV does not
hash it too much. Thanks all for your suggestions.
char Date[8]; // The date of the compilation in the format
YYYYMMDD
char Time[4]; // The time of the compilation in the format
HHMM
char Product_number[8]; // The product number of the compiler
that produced the associated data file
CM
On Sat, 16 Dec 2023 12:28:11 -0600, Charles Mills <[email protected]> wrote:
>You know what I am actually looking at doing? You may laugh but it has worked
>for me in the past. I am thinking of pulling the IBM HTML documentation into
>MS-Word and massaging it there into C declarations. I did this for a *LOT* of
>RACF record layouts for the CorreLog product, so I know whereof I speak. Why
>MS-Word?
>
>- IBM's HTML tables map to MS-Word tables. You can then manipulate stuff by
>columns. For example, the doc's Foo CL8 wants to become char Foo[8]; So you
>duplicate the CL8 column and have CL8 Foo CL8. Then you change the first
>column's CL8 to char and the third column's CL8 to [8]; and you are most of
>the way there. Not sure if this description make sense, but it works, at least
>for me.
>- Good visual text manipulation tools
>- I have done it before and am familiar with it.
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
