A lot of this is personal preference.....and now I have to live with another group's preference...I can live with that. (i.e. I get to support SYS3.*, SYS5.*, SYS7.* and SYS9.* as well)
In the area of change all ServerPac (IBM Product) HLQs to SYS1.*, this meant that a single RACF rule protected ALL system datasets. I did understand the packaging rules required the shipped prodcut datasets use the 3char product identifier as the "usual" HLQ. It also meant that the special support for SYS1.* datasets built into DFDSS worked. Personally, I liked coding a human-readable second level qualifier, like SYS1.ISPF.SISP*....those people who didn't understand IBM 3/4 char product identifiers could at the least suss out which product a dataset belonged to, using a quailifier that matched the product acronym. On Sun, 13 Apr 2008 02:51:34 +0000, Ted MacNEIL <[EMAIL PROTECTED]> wrote: >>I often see SYS1.ISF.SISF* , SYS1.ISP.SISP*, SYS1.GIM.SGIM* etc. even though the MLQ is redundant. > >I agree with the redundancy argument; what's wrong with each product having the same library name(s) at every site? > > >>Hard to change that stuff in a production environment... well, maybe not hard, just a PITA when there are batch processes and people with their own clists etc. > >In production, standards should be enforced, so it won't become a PITA. > >If unsupported software breaks, you get to keep both parts. 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
