>IMO, writing an exit in LE C/C++ just isn't worth the hassle. To write a >proper glue code stub you will need to call your C program via the LE >CEEPIPI service. Trying to get the CAA from the TCB is a shot in the >dark as each ISPF screen runs in a subtask, and IIRC using the SELECT >CMD(...) service will use ATTACH. I'm not sure what TCB in the hierarchy >LE stores the CAA.
>Check out the Metal/C or Systems Programming C (SPC) features of the >compiler, both of which will suffice for writing an exit. Unfortunately the exit is part of a larger product and needs to access a body of language environment C++ code, so it has to be written in a way compatible with that. If I can work out the necessary glue to get the LE hooked up then that's largely all I need. I've made some progress, but so far not enough. __________ Information from ESET NOD32 Antivirus, version of virus signature database 4754 (20100108) __________ The message was checked by ESET NOD32 Antivirus. http://www.eset.com ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
