On Sat, 10 Jul 2010 13:00:39 -0500, Rick Fochtman wrote: >---------------------------------<snip>------------------------------------ >Would people agree with the following? > >If a vendor were shipping a product that resided in two datasets, >FOO.THIS and FOO.THAT, best practice would be to recommend that the >installer either create a user catalog named FOO or a user catalog with >an alias of FOO so that the FOO.xxxx datasets would not take up space in >the master catalog? >--------------------------------<unsnip>----------------------------------- >Charles, there are several reasons I can think of to discourage this idea. > ... > Also, since there's no way to ensure that any vendor's particular choice of 'FOO' won't collide with some customer's existing data set names, the vendor should provide a way of tailoring JCL and PROCs to avert such collisions.
However, in the absence of such collisions, the customer should follow the vendors' naming recommendations to facilitate portability from site to site of procedures, utility commands, programmer skills, and documentation. It's been suggested here documentation be delivered in markup source so the customer can tailor the documentation to match the data set names selected for the product before rendering. Do any vendors and customers do this, really? -- 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
