Thanks for all the responses. To answer the questions (I think): CSA in use is the size of the ENF listener load module and some 256 bytes of working storage from CSA-not a whole lot, but the Started Task that makes the ENF listener start and stop could potentially be bounced a lot while the initial configuration is being worked out. Since the potential is there we're trying to be good citizens, and thus be as protective of CSA storage as we can.
Thanks to the helpful suggestions, we've decided to hang the listener CSA address and its CSA storage off a control block we have in the ECVT, and leave it allocated until an IPL. Multiple versions of our Started Task can then WAIT on the same POST from the one listener for the LPAR. ...phsiii ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN
