Just because the product is shipped with 2 datasets of specific dataset names does generally require you to use those specific names. We generally have installation datasets placed under "SYSI" and the actual run-time datasets under another hi-level. I've definitely seen it done a myriad of ways.
As a storage admin responsible for catalogs, backups, and recoveries. I would definitely object to a catalog with 2 entries as a total waste. ddk From: Charles Mills <[email protected]> To: [email protected] Date: 07/09/2010 02:28 PM Subject: Re: Dumb question on DEFINE ALIAS Sent by: IBM Mainframe Discussion List <[email protected]> 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? Charles This e-mail message and all attachments transmitted with it may contain legally privileged and/or confidential information intended solely for the use of the addressee(s). If the reader of this message is not the intended recipient, you are hereby notified that any reading, dissemination, distribution, copying, forwarding or other use of this message or its attachments is strictly prohibited. If you have received this message in error, please notify the sender immediately and delete this message and all copies and backups thereof. Thank you. ---------------------------------------------------------------------- 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
