Sorry, problems here. Continuing
OMVS.&SYSRS1.. is the high level for the IPL volumes. We don't IPL multiple
images from the same RES volume.
OMVS.SYSPLEX.&SYSPLEX.. is the high level for the "sysplex level" ZFS data
sets.
The above data sets are not SMS managed.
The above are in a separate catalog, on a non-"res" type volume. They are
not SMS managed. I'm not sure why I did that, now. Easy when I first
started out? Stupidity?
I also using an entirely HLQ for what I consider to be "shop" level ZFS
datasets. And they are in yet another catalog, to keep them separate and
easy to migrate to a new release of the OS and to share between different
z/OS images. These are things like: user ${HOME} file systems; product file
systems; application (OK, we don't have any) file systems; and so on.
On Thu, Aug 20, 2015 at 11:17 AM, John McKown <[email protected]>
wrote:
> Which OMVS data sets? I have a bunch of SYS1.?BPX???? data sets - I.e. the
> system PDSes. So far as file systems go, I use OMVS for the "system level"
> filesystem containers (ZFS data sets). They are in a separate catalog. Why?
> Because I am in a sysplex and it much easier to do sharing when I do that.
> For "system level" ZFS data sets, I use OMVS.&SYSR1..
>
> On Thu, Aug 20, 2015 at 10:21 AM, David G. Schlecht <
> [email protected]> wrote:
>
>> Hello all,
>>
>> How do you catalog your OMVS datasets?
>>
>> My predecessor created a catalog in which he put a few OMVS dataset
>> definitions. However, it never really got used. We only have a few dozen
>> OMVS file systems so it doesn’t seem to make sense to have a catalog just
>> for them.
>>
>> What is common practice? What do you do? Do you have a separate catalog
>> for your OMVS datasets? If so, what’s your reasoning?
>>
>>
>> David G. Schlecht | Information Technology Professional
>> State of Nevada | Department of Administration | Enterprise IT Services
>> T:(775)684-4328 | F: (775) 684‐4324 | E:[email protected]
>>
>>
>> ________________________________
>> This communication, including any attachments, may contain confidential
>> information and is intended only for the individual or entity to which it
>> is addressed. Any review, dissemination or copying of this communication by
>> anyone other than the intended recipient is strictly prohibited. If you are
>> not the intended recipient, please contact the sender by reply e-mail and
>> delete all copies of the original message.
>>
>> ----------------------------------------------------------------------
>> For IBM-MAIN subscribe / signoff / archive access instructions,
>> send email to [email protected] with the message: INFO IBM-MAIN
>>
>
>
>
> --
>
> Schrodinger's backup: The condition of any backup is unknown until a
> restore is attempted.
>
> Yoda of Borg, we are. Futile, resistance is, yes. Assimilated, you will be.
>
> He's about as useful as a wax frying pan.
>
> 10 to the 12th power microphones = 1 Megaphone
>
> Maranatha! <><
> John McKown
>
--
Schrodinger's backup: The condition of any backup is unknown until a
restore is attempted.
Yoda of Borg, we are. Futile, resistance is, yes. Assimilated, you will be.
He's about as useful as a wax frying pan.
10 to the 12th power microphones = 1 Megaphone
Maranatha! <><
John McKown
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
