>As far as I know that is not true. The appl env. asid is created on demand.
You are mixing terminology. There is the application environment which consists of: 1. An 8-byte name. 2. A 32-byte lable. 3. An associated PROC, with optional parameters. 4. A limit. If the application environment is stopped, the PROC is never invoked. If the application environment is started then the PROC is invoked, as needed, subject to the limits specified. All AE's are started everywhere, by default, when you IPL. It takes a modify command applied to the WLM to start and stop AE's. The WLM will not start an AE that is stopped. It will invoke more PROCs, if applicable, if the AE is started. This is independent of DB2, except DB2 will use the associated PROC for DDF work. DB2 is not the only sub-system that uses AE's. I worked with an ISV that used them as well. We kept it under tight control, by stopping the AE on all systems where it didn't run. And, during testing, we kept the limit to one per SYSPLEX. Since, we couldn't control when the user was submitting tests, we would stop the AE, whenever we had to do (sub-system or application) maintenance. We did the same with DDF. We were comparing the ISV product to DB2/DDF. - Too busy driving to stop for gas! ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
