Short answer...to separate application files from the master catalog and to keep the master catalog as small as possible. Only system level datasets should be directly cataloged in the master catalog. It also allows you to separate different applications into their own usercatalogs for performance and security.
Jon L. Veilleux [email protected] (860) 636-9179 -----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of Charles Mills Sent: Friday, July 09, 2010 2:45 PM To: [email protected] Subject: Dumb question on DEFINE ALIAS What is the reason for defining a catalog alias? I think I understand the technical effect but I don't understand the big picture purpose. Suppose I wanted to define and catalog some new datasets FOO.THIS and FOO.THAT. Why would I issue something like DEFINE ALIAS (NAME(FOO ) RELATE(SOME.CATALOG)) I understand the "little picture" reason: to specify FOO as an alias for SOME.CATALOG but big picture, why would I not just create and catalog FOO.THIS and FOO.THAT using JCL? What is the advantage of or reason for defining the alias? Is there an overview somewhere of catalogs and catalog management? Thanks for your patience with an incredibly elementary question. Charles Mills ---------------------------------------------------------------------- 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 This e-mail may contain confidential or privileged information. If you think you have received this e-mail in error, please advise the sender by reply e-mail and then delete this e-mail immediately. Thank you. Aetna ---------------------------------------------------------------------- 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
