Hi, I have been tasked with being the STG Admin backup for a bit. It has been awhile and just need some opinions on the following philosophy.
Here the stg groups back each other up. I am not sure the impact to doing it this way. And the Stg groups are based on application rather than data set type. For example, I have APPL1, APPL2, DEVL1, DEVL2, PAPPL1, PAPPL3. These represent applications like GL, Distribution, AR, etc... For both production, Qual, and test. APPL1 is used for GL, but is also backed up (SPILL) by APPL2, DEVL1, DEVL2. The PAPPL1 is backed up by PAPPL3, and so on. The applications groups like having unique pool names that match their applications. They feel it makes their cleanup easier (which of course never happens). I have always seen SMS step up by dataset type and functions. Fortunately the dasd names have a standard - GLXXP01 - for all GL Application packs for Production, GLXXT01 - For all GL Applications packs for TEST, and GLXXQ01 - For all GL Packs for QA testing. VSAMEF, HFS, TEMP, SPILL, PRODDB2, DT339003, DT339027, etc... And SPILL is used to back up all pools for emergencies. I really want to disengage the pools from the current philosophy to more of a traditional way. Any thoughts on how I can pursuade everyone else to do it my way? ;-) Or is this other way just as good? The SMS environment has evolved over decades of inhouse staff and contractors. So imagine the spaghetti I will be going through once a solid definition philosophy has been decided upon. Lizette ---------------------------------------------------------------------- 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
