[Default] On 16 May 2019 04:55:33 -0700, in bit.listserv.ibm-main [email protected] (Peter Relson) wrote:
><snip> >...where IBM provides some guidelines for doing exit work in Metal-C ></snip> > >I'd say that the guideline is to get Metal C to do what you would have >done if you were coding in assembler. > >What you typically need are mappings in (Metal) C for the data structures >that the exit routine needs to access. Most ISVs have likely rolled their >own over time, but z/OS is (finally) beginning to provide some (and is >looking for help in prioritizing which to provide first -- the goal is to >do most of the mappings in maclib and modgen, but that goal would be >accomplished incrementally). If you have such a prioritized list (it can >be for your own needs, or a group's or any scale you choose) please send >it to me so that we can try to make the best plan. Of course exit routines >are not the only things that can benefit from the availability of such >mappings. While being retired I am in no position to submit an RFE, what I have alway wanted was a tool that would convert Assembler DSECTs to COBOL record descriptions, PL1 mappings etc.. It would have saved me much time in writing COBOL programs to deal with SMF records and would allow easier usage of IBM callable routines. This would be a better approach for providing C mappings because it then allows relatively easy update and doesn't require manual effort for each update. Clark Morris > >Peter Relson >z/OS Core Technology Design > > >---------------------------------------------------------------------- >For IBM-MAIN subscribe / signoff / archive access instructions, >send email to [email protected] with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
