If management requires the dsnames to include the version number, then doesn't the JCL have to be changed anyway to avoid confusion? For example, if you're running V1R1 and want to upgrade to V1R2, if you use aliases then the JCL would say V1R1 but would resolve to V1R2. And you know who gets the blame when there's a problem.
- Don Imbriale On Tue, Feb 22, 2011 at 9:52 AM, McKown, John <[email protected] > wrote: > But then the job must run on that system. I would like the option to run on > any system using the identical JCL, but using the proper system-specific > version of the DSN. > > OK, I'm being extreme for my needs. But imagine a parallel sysplex running > 6 systems. I guess those shops properly design things so that system > specific datasets are not needed. Or they exist with the same DSN, but in > different catalogs. > > I'll likely go with the system-specific ALIAS. If someone runs the job on > the wrong system, then that's their worry. > > -- > John McKown > Systems Engineer IV > IT > > Administrative Services Group > > HealthMarkets(r) > > 9151 Boulevard 26 * N. Richland Hills * TX 76010 > (817) 255-3225 phone * > [email protected] * www.HealthMarkets.com > > ---------------------------------------------------------------------- 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
