i catalog all datasets on the res with indrect cataloging
LISTC ALL ENT('ASM.SASMMOD1')
NONVSAM --- ASM.SASMMOD1 < dataset on the res
IN-CAT --- CATALOG.HRBDVZ14.MSTRCAT
HISTORY
DATASET-OWNER-(NULL) CREATION2004.334
RELEAS
Mark,
If I'm not wrong, the recommended data set layout is about dataset
placement. I suppose that I'm going to have two MOD-9 SYSRES with all
the TVOLs but my question is: where do I should catalog the datasets
that will be in this SYSRES?.
Thank you.
---
On Thu, 3 Nov 2005 06:49:19 -0600, Matthew Stitt <[EMAIL PROTECTED]>
wrote:
>
>Everyone has their own scheme.
>
But there are best practices that make a heck of a lot of sense.
The dialogs have an option for recommended data set layout. Also,
the planning for installation manual for whatever rel
In <[EMAIL PROTECTED]>, on
11/03/2005
at 10:02 AM, Lucas Morton <[EMAIL PROTECTED]> said:
>I'm installing z/OS 1.6, ¿Should I catalog ALL z/OS serverpac
>datasets in the master or It wowkd be better try to keep some of them
>in user catalogs?.
The rule is to not put anything in the master cata
I go both ways. My general rule of thumb is that if it resides on the
target or dlib volumes they go in the master catalog. The HFS volume has
everything in its own user catalog. So does SMPE stuff. The rest of the
files, like JESx, FFST, MSYS, etc, go on another volume that I regard as a
throw
I'm installing z/OS 1.6, ¿Should I catalog ALL z/OS serverpac datasets
in the master or It wowkd be better try to keep some of them in user
catalogs?.
I'm planning to use Extended indirect alias support and indirect
cataloging for serverpac datasets.
--
6 matches
Mail list logo