Hello Chester, we use Scheduling Environments.
environment: Production systems in one Sysplex.... Development systems in a different sysplex. 1. the same scheduling environments are coded in both environments. Allows promotion of unchanged JCL from dev to prod. 2. Licensed products - every product that requires a license "zap" has a Scheduling environment coded. 3. Servers - code which requries a pre-requisite server task to be active has a Scheduling environment coded. (note: it may be that a group of tasks has to be active for the "server" to be active) 4. System - each system has a SYSNAME scheduling environment. Not usually used by application JCL. 5. Reminder - only one scheduling environment per JOB...this causes the most application developer angst. 6. Automation - most useful in turning ON/OFF scheduling environment resources when the pre-requisite conditions appear/disappear. On Tue, 13 Apr 2010 21:11:44 EDT, Chester Hood <[email protected]> wrote: >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 > Regards Bruce Hewson ---------------------------------------------------------------------- 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
