On Wed, 24 Aug 2005 15:58:58 -0500, Ed Gould <[EMAIL PROTECTED]> wrote:
>On Aug 24, 2005, at 3:32 PM, Mark Zelden wrote:
>
>> On Wed, 24 Aug 2005 15:44:39 -0400, Thomas Conley
>> <[EMAIL PROTECTED]> wrote:
>>
>>> Guys,
>>>
>>> You WANT VOLUME and UNIT parms so you can tailor the DDDEFs for your
>>> online
>>> and offline res target zones (please tell me you're doing that and not
>> using
>>> renames to install).
>>>
>>> Regards,
>>> Tom Conley
>>>
>>
>> Tom,
>>
>> That is my preference also (for the "MVS" environment), but I have also
>> been at shops that do it via SSA so the access is via catalog.
>>
>> Regards,
>>
>> Mark
>>
>Mark,
>
>Thanks... I am curious though didn't that complicate things when
>changing either volser or devicetype? At least with DDDEFS its
>reasonably straight forward. With datasets cataloged (without a
>stepcat) managing the catalog, is IMO a PITA as there is no really
>easyway to make massive changes (unless you know of a secret that I
>haven't heard).
>
>Ed
>
I didn't ever set it up that way myself, but no. You only defined
new SSAs at install time and they pointed to the maintenence
sysres(es) via catalog. I guess if you had to move the data sets for
some reason you would need to DELETE (noscratch) and DEFINE the
data sets to the new volumes, but how often would one change volsers
within a single release. When's the last time you changed the
devicetype of your maintenance sysres mid-release?!
A simple example would to have data sets cataloged using SSAs
like this (to support multiple maintainable levels of the OS):
TGTZ14.SYS1.LINKLIB
TGTZ15.SYS1.LINKLIB
TGTZ16.SYS1.LINKLIB
I personally like the other method better because my cloning procedures
include creating a tgt zone that matches each sysres set. This has 2
advantages that I like:
1) I could apply a PTF in an emergency to a live sysres (such as an
ISPF fix that could be implemented via dynamic LPA or LLA update):
2) When looking at a problem and IBM asks "do you have PTF UAnnnn on?"
I can trust what SMP/E tells me instead of having to refer to a
chart or some other method that tells me when the sysres was
cloned.
BTW, my target zone names all are prefixed with the actual volser
of the primary sysres. For example (these aren't my actual
names):
zones: RSM60A1 primary sysres: RSM60A (maintenance sysres)
RSM60A2
zones: RSZ61A1 primary sysres: RSZ61A
RSZ61A2
zones: RSZ62A1 primary sysres: RSZ62A
RSZ62A2
etc.
Regards,
Mark
--
Mark Zelden
Sr. Software and Systems Architect - z/OS Team Lead
Zurich North America and Farmers Insurance Group
mailto: [EMAIL PROTECTED]
Systems Programming expert at http://Search390.com/ateExperts/
Mark's MVS Utilities: http://home.flash.net/~mzelden/mvsutil.html
----------------------------------------------------------------------
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
