We are considering using scheduling environments for the first time and are concerned that we might be over-doing it a bit. In a test and development LPAR, we have 16 test/development "environments" that each consist of 3-8 CICS regions, 2-5 ADABAS instances, and a connection to a DB2 subsystem. The total is about 100 CICS regions, 80 ADABAS instances, and 6 DB2 subsystems. To cover any possibility, we would define a scheduling environment and resource for each of these address spaces (186), plus a scheduling environment corresponding to each development environment (16). We believe that this covers the spectrum of batch jobs that might need anywhere from a particular CICS region (open/close files) to an entire development environment (regression test job streams). Is this a reasonable approach or overkill? We would appreciate your comments and suggestions as we don't want to create a monster. Chester Hood Nissan Americas
---------------------------------------------------------------------- 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
