On Thu, 11 Mar 2010 13:50:12 -0800, Starr, Alan <[email protected]> wrote:
>Dave Gibney has already mentioned the only justification that occurs to me: datasets sharing a HLQ have varied sharing requirements (e.g. some datasets are dedicated to an image and others are shared by multiple images). > >Once upon a time, there may have been an additional justification: to isolate release levels of a product and thereby simplify cleanup (of the old release) and implementation (i.e. switching the new release on by changing the UCAT association). SYMBOLICRELATE aliases may now be used to accomplish the same thing. > >I have occasionally noticed that, because it uses its own LOCATE mechanisms, ISPF 3.4 sometimes returns some weird results in MLA environments. > >Alan Starr > A former client of mine had all their system data sets (not application) under things like "PROD.*" and "TEST.*" (not including "IBM sysres"). They never wanted to go back and change JCL and standards. When MLA came along, they were able to split out the catalogs into multiple catalogs in order to help system performance (reduce catalog contention, response time, etc.). For example, PROD.CA1 in USERCATA, PROD.FDR in USERCATB etc. Mark -- Mark Zelden - Zelden Consulting Services - z/OS, OS/390 and MVS mailto:[email protected] Mark's MVS Utilities: http://home.flash.net/~mzelden/mvsutil.html Systems Programming expert at http://expertanswercenter.techtarget.com/ ---------------------------------------------------------------------- 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
