<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. 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
