On Wed, 10 Jun 2009 18:06:01 -0600, Frank Swarbrick wrote: >> too!". >>> >> No caching ==> poor performance. Frequent refresh ==> poor performance. > >This is why I would suggest perhaps something similar to LINKLIST in that it >is searched by default, but also like JOBLIB in that there is no caching. > No caching ==> poor performance.
>> Would the JCL INCLUDE facility help you here? >Yes and no. > >Yes, I could have a member that has a JOBLIB concatention with all of the >production libraries I would need for production applications jobs. > >But no, this would not help for testing, because any JOBLIB I specified in my >test JCL in order to add a test library (ahead of production libraries) would >have to be "built from scratch" in order to place it at the beginning. > For testing, INCLUDE a different JOBLIB member. This in turn (I believe) could be selected by a JCL symbolic variable which could also be used as a qualifier in data set names to differentiate your test data from production data. -- gil ---------------------------------------------------------------------- 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
