Re: Page Datasets in User Catalog

2023-11-29 Thread Lennie Dymoke-Bradshaw
The last sentence of the requirement reads,
"I believe IBM needs a new approach to the handling of these situations. Either 
there needs to be a formally agreed process for having 2 or more master 
catalogs in a sysplex, or there needs to be a way for VSAM data sets to be 
“multiply-owned” by more than one catalog."

I think this includes a "dual MCAT solution".
Lennie

-Original Message-
From: IBM Mainframe Discussion List  On Behalf Of 
Radoslaw Skorupka
Sent: 29 November 2023 18:32
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Page Datasets in User Catalog

Lennie,
I won't support it, because I don't want it. In my opinion it is bad approach.
BTW: there is quite new feature
F CATALOG,RESTART(new.mcat.dsn)
which I like.

As an alternative I would consider some solution like dual MCAT - similar to 
dual RACF db, or Db2 log.

--
Radoslaw Skorupka
Lodz, Poland



W dniu 29.11.2023 o 19:27, Lennie Dymoke-Bradshaw pisze:
> Radoslaw and others,
> Please consider supporting my idea on the ideas portal.
>
> Better support for multiple master catalogs in a sysplex.
> https://ibm-z-hardware-and-operating-systems.ideas.ibm.com/ideas/ZOS-I-3890
>
> Lennie Dymoke-Bradshaw
> https: //rsclweb.com
> -Original Message-
> From: IBM Mainframe Discussion List  On Behalf Of 
> Radoslaw Skorupka
> Sent: 29 November 2023 15:42
> To:IBM-MAIN@LISTSERV.UA.EDU
> Subject: Re: Page Datasets in User Catalog
>
> W dniu 29.11.2023 o 04:56, Mark Zelden pisze:
>> On Thu, 23 Nov 2023 14:20:51 -0600, Jon Perryman   
>> wrote:
>>
>>> On Wed, 22 Nov 2023 22:35:13 +, Seymour J Metz   wrote:
>>>
>>>> I suspect that there was a game of telegraph, whereby crucial details got 
>>>> lost.
>>>>
>>>> It is normal to allocate page datasets in a user catalog that will 
>>>> eventually be used as a master catalog.
>>>> I'm suspicious of the claim that z/OS can use  a page dataset that is not 
>>>> in its own master catalog, but I can't rule it out.
>>> There are definitely crucial details lost. Page and swap are special 
>>> datasets. For instance, a page dataset can be in multiple catalogs (I think 
>>> using recatalog).
>> Pagespace can be in multiple catalogs (which should be a master to the
>> system that is using it) via RECATALOG.  I think at one time it had to
>> have a HLQ of PAGE or SYS1 but my memory is fuzzy on that part.  I know for 
>> a long time the HLQ doesn't matter at all  for pagespace and it could still 
>> be in
>> multiple catalogs.   This also applies to swapspace and VSAM linear ZFS that 
>> is indirectly cataloged.
>> Any SYS1 VSAM dataset can be in multiple catalogs via recatalog.
>>
>> Don't ask me where this is documented now. :)  I'm guessing "DFSMS managing 
>> catalogs".
>
> I dare to correct the above considerations.
> 1. Any non-VSAM and non-SMS dataset can be catalogued twice or multiple 
> times. Reason is obvious: there is no backward reference. It is just entry in 
> BCS, which contains DSN, UNIT and VOLSER.
> 2. VSAM datasets *cannot* be catalogued multiple times. And there is a way to 
> enforce it - VVDS.
> 3. IBM created exceptions for the 2. but only for SYS1 and PAGE HLQ.
> Note - this is matter or HLQ, not VSAM type or flavour. In other words one 
> can "multi-catalog" any SYS1.VSAM.DSN regardless of its purpose and any 
> PAGE.VSAM.DSN, also regardless of its purpose.
> 4. Page dataset is specific kind of VSAM, because it is somehow formatted 
> before use. As one may know DEF PAGE takes significantly more time than 
> regular DEF CL and depends on its size.
> 5. So, it is still possible to have good reason to create some page datasets, 
> even cataloged in UCAT, but for future use. And future use will require page 
> datasets to be in MCAT. How? a) recatalog. b) my current UCAT is de facto 
> other system's MCAT. Other scenarios may apply.
>
>
> My €0.02
>
> --
> Radoslaw Skorupka
> Lodz, Poland
>

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN


Re: Page Datasets in User Catalog

2023-11-29 Thread Radoslaw Skorupka

Lennie,
I won't support it, because I don't want it. In my opinion it is bad 
approach.

BTW: there is quite new feature
F CATALOG,RESTART(new.mcat.dsn)
which I like.

As an alternative I would consider some solution like dual MCAT - 
similar to dual RACF db, or Db2 log.


--
Radoslaw Skorupka
Lodz, Poland



W dniu 29.11.2023 o 19:27, Lennie Dymoke-Bradshaw pisze:

Radoslaw and others,
Please consider supporting my idea on the ideas portal.

Better support for multiple master catalogs in a sysplex.
https://ibm-z-hardware-and-operating-systems.ideas.ibm.com/ideas/ZOS-I-3890

Lennie Dymoke-Bradshaw
https: //rsclweb.com
-Original Message-
From: IBM Mainframe Discussion List  On Behalf Of 
Radoslaw Skorupka
Sent: 29 November 2023 15:42
To:IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Page Datasets in User Catalog

W dniu 29.11.2023 o 04:56, Mark Zelden pisze:

On Thu, 23 Nov 2023 14:20:51 -0600, Jon Perryman   wrote:


On Wed, 22 Nov 2023 22:35:13 +, Seymour J Metz   wrote:


I suspect that there was a game of telegraph, whereby crucial details got lost.

It is normal to allocate page datasets in a user catalog that will eventually 
be used as a master catalog.
I'm suspicious of the claim that z/OS can use  a page dataset that is not in 
its own master catalog, but I can't rule it out.

There are definitely crucial details lost. Page and swap are special datasets. 
For instance, a page dataset can be in multiple catalogs (I think using 
recatalog).

Pagespace can be in multiple catalogs (which should be a master to the
system that is using it) via RECATALOG.  I think at one time it had to
have a HLQ of PAGE or SYS1 but my memory is fuzzy on that part.  I know for a 
long time the HLQ doesn't matter at all  for pagespace and it could still be in
multiple catalogs.   This also applies to swapspace and VSAM linear ZFS that is 
indirectly cataloged.
Any SYS1 VSAM dataset can be in multiple catalogs via recatalog.

Don't ask me where this is documented now. :)  I'm guessing "DFSMS managing 
catalogs".


I dare to correct the above considerations.
1. Any non-VSAM and non-SMS dataset can be catalogued twice or multiple times. 
Reason is obvious: there is no backward reference. It is just entry in BCS, 
which contains DSN, UNIT and VOLSER.
2. VSAM datasets *cannot* be catalogued multiple times. And there is a way to 
enforce it - VVDS.
3. IBM created exceptions for the 2. but only for SYS1 and PAGE HLQ.
Note - this is matter or HLQ, not VSAM type or flavour. In other words one can 
"multi-catalog" any SYS1.VSAM.DSN regardless of its purpose and any 
PAGE.VSAM.DSN, also regardless of its purpose.
4. Page dataset is specific kind of VSAM, because it is somehow formatted 
before use. As one may know DEF PAGE takes significantly more time than regular 
DEF CL and depends on its size.
5. So, it is still possible to have good reason to create some page datasets, 
even cataloged in UCAT, but for future use. And future use will require page 
datasets to be in MCAT. How? a) recatalog. b) my current UCAT is de facto other 
system's MCAT. Other scenarios may apply.


My €0.02

--
Radoslaw Skorupka
Lodz, Poland



--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN


Re: Page Datasets in User Catalog

2023-11-29 Thread Lennie Dymoke-Bradshaw
Radoslaw and others,
Please consider supporting my idea on the ideas portal.

Better support for multiple master catalogs in a sysplex.
https://ibm-z-hardware-and-operating-systems.ideas.ibm.com/ideas/ZOS-I-3890

Lennie Dymoke-Bradshaw
https: //rsclweb.com
-Original Message-
From: IBM Mainframe Discussion List  On Behalf Of 
Radoslaw Skorupka
Sent: 29 November 2023 15:42
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Page Datasets in User Catalog

W dniu 29.11.2023 o 04:56, Mark Zelden pisze:
> On Thu, 23 Nov 2023 14:20:51 -0600, Jon Perryman  wrote:
>
>> On Wed, 22 Nov 2023 22:35:13 +, Seymour J Metz  wrote:
>>
>>> I suspect that there was a game of telegraph, whereby crucial details got 
>>> lost.
>>>
>>> It is normal to allocate page datasets in a user catalog that will 
>>> eventually be used as a master catalog.
>>> I'm suspicious of the claim that z/OS can use  a page dataset that is not 
>>> in its own master catalog, but I can't rule it out.
>> There are definitely crucial details lost. Page and swap are special 
>> datasets. For instance, a page dataset can be in multiple catalogs (I think 
>> using recatalog).
> Pagespace can be in multiple catalogs (which should be a master to the 
> system that is using it) via RECATALOG.  I think at one time it had to 
> have a HLQ of PAGE or SYS1 but my memory is fuzzy on that part.  I know for a 
> long time the HLQ doesn't matter at all  for pagespace and it could still be 
> in
> multiple catalogs.   This also applies to swapspace and VSAM linear ZFS that 
> is indirectly cataloged.
> Any SYS1 VSAM dataset can be in multiple catalogs via recatalog.
>
> Don't ask me where this is documented now. :)  I'm guessing "DFSMS managing 
> catalogs".


I dare to correct the above considerations.
1. Any non-VSAM and non-SMS dataset can be catalogued twice or multiple times. 
Reason is obvious: there is no backward reference. It is just entry in BCS, 
which contains DSN, UNIT and VOLSER.
2. VSAM datasets *cannot* be catalogued multiple times. And there is a way to 
enforce it - VVDS.
3. IBM created exceptions for the 2. but only for SYS1 and PAGE HLQ. 
Note - this is matter or HLQ, not VSAM type or flavour. In other words one can 
"multi-catalog" any SYS1.VSAM.DSN regardless of its purpose and any 
PAGE.VSAM.DSN, also regardless of its purpose.
4. Page dataset is specific kind of VSAM, because it is somehow formatted 
before use. As one may know DEF PAGE takes significantly more time than regular 
DEF CL and depends on its size.
5. So, it is still possible to have good reason to create some page datasets, 
even cataloged in UCAT, but for future use. And future use will require page 
datasets to be in MCAT. How? a) recatalog. b) my current UCAT is de facto other 
system's MCAT. Other scenarios may apply.


My €0.02

--
Radoslaw Skorupka
Lodz, Poland

--
For IBM-MAIN subscribe / signoff / archive access instructions, send email to 
lists...@listserv.ua.edu with the message: INFO IBM-MAIN

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN


Re: Page Datasets in User Catalog

2023-11-29 Thread Radoslaw Skorupka

W dniu 29.11.2023 o 04:56, Mark Zelden pisze:

On Thu, 23 Nov 2023 14:20:51 -0600, Jon Perryman  wrote:


On Wed, 22 Nov 2023 22:35:13 +, Seymour J Metz  wrote:


I suspect that there was a game of telegraph, whereby crucial details got lost.

It is normal to allocate page datasets in a user catalog that will eventually 
be used as a master catalog.
I'm suspicious of the claim that z/OS can use  a page dataset that is not in 
its own master catalog, but I can't rule it out.

There are definitely crucial details lost. Page and swap are special datasets. 
For instance, a page dataset can be in multiple catalogs (I think using 
recatalog).

Pagespace can be in multiple catalogs (which should be a master to the system 
that is using it) via
RECATALOG.  I think at one time it had to have a HLQ of PAGE or SYS1 but my 
memory is fuzzy on
that part.  I know for a long time the HLQ doesn't matter at all  for pagespace 
and it could still be in
multiple catalogs.   This also applies to swapspace and VSAM linear ZFS that is 
indirectly cataloged.
Any SYS1 VSAM dataset can be in multiple catalogs via recatalog.

Don't ask me where this is documented now. :)  I'm guessing "DFSMS managing 
catalogs".



I dare to correct the above considerations.
1. Any non-VSAM and non-SMS dataset can be catalogued twice or multiple 
times. Reason is obvious: there is no backward reference. It is just 
entry in BCS, which contains DSN, UNIT and VOLSER.
2. VSAM datasets *cannot* be catalogued multiple times. And there is a 
way to enforce it - VVDS.
3. IBM created exceptions for the 2. but only for SYS1 and PAGE HLQ. 
Note - this is matter or HLQ, not VSAM type or flavour. In other words 
one can "multi-catalog" any SYS1.VSAM.DSN regardless of its purpose and 
any PAGE.VSAM.DSN, also regardless of its purpose.
4. Page dataset is specific kind of VSAM, because it is somehow 
formatted before use. As one may know DEF PAGE takes significantly more 
time than regular DEF CL and depends on its size.
5. So, it is still possible to have good reason to create some page 
datasets, even cataloged in UCAT, but for future use. And future use 
will require page datasets to be in MCAT. How? a) recatalog. b) my 
current UCAT is de facto other system's MCAT. Other scenarios may apply.



My €0.02

--
Radoslaw Skorupka
Lodz, Poland

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN


Re: Page Datasets in User Catalog

2023-11-28 Thread Mark Zelden
On Thu, 23 Nov 2023 14:20:51 -0600, Jon Perryman  wrote:

>On Wed, 22 Nov 2023 22:35:13 +, Seymour J Metz  wrote:
>
>>I suspect that there was a game of telegraph, whereby crucial details got 
>>lost.
>>
>>It is normal to allocate page datasets in a user catalog that will eventually 
>>be used as a master catalog.
>> I'm suspicious of the claim that z/OS can use  a page dataset that is not in 
>> its own master catalog, but I can't rule it out.
>
>There are definitely crucial details lost. Page and swap are special datasets. 
>For instance, a page dataset can be in multiple catalogs (I think using 
>recatalog).

Pagespace can be in multiple catalogs (which should be a master to the system 
that is using it) via 
RECATALOG.  I think at one time it had to have a HLQ of PAGE or SYS1 but my 
memory is fuzzy on
that part.  I know for a long time the HLQ doesn't matter at all  for pagespace 
and it could still be in
multiple catalogs.   This also applies to swapspace and VSAM linear ZFS that is 
indirectly cataloged.   
Any SYS1 VSAM dataset can be in multiple catalogs via recatalog. 

Don't ask me where this is documented now. :)  I'm guessing "DFSMS managing 
catalogs".  


Best Regards,

Mark
--
Mark Zelden - Zelden Consulting Services - z/OS, OS/390 and MVS
ITIL v3 Foundation Certified
mailto:m...@mzelden.com
Mark's MVS Utilities: http://www.mzelden.com/mvsutil.html

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN


Re: Page Datasets in User Catalog

2023-11-24 Thread Seymour J Metz
:-(

Is the an outstanding RFE for user catalog support in PAGEADD?

-- 
Shmuel (Seymour J.) Metz
http://mason.gmu.edu/~smetz3
עַם יִשְׂרָאֵל חַי




From: IBM Mainframe Discussion List  on behalf of Jon 
Perryman 
Sent: Friday, November 24, 2023 1:11 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Page Datasets in User Catalog

On Fri, 24 Nov 2023 00:12:34 +, Seymour J Metz  wrote:

>Are you saying that PAGEADD will work with alias entries and that the added 
>datasets will be retained across IPL?

Sorry, I worded it incorrectly. I didn't mean to imply I had experience using 
pageadd in that respect.

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN


Re: Page Datasets in User Catalog

2023-11-23 Thread Jon Perryman
On Fri, 24 Nov 2023 01:42:08 +, Mark Jacobs  
wrote:

>I tried a pageadd of a newly defined page dataset that was cataloged in a user 
>catalog. It didn't work. 

I suspected it would not work but was unsure. Pageadd remains in effect until 
the next CLPA so it would make sense it would fail.

Prior to shared MCAT, I think we recataloged the emergency page dataset to each 
master catalog so it could be used from any system. It's been so long that I 
can't remember for sure and I wasn't responsible for setting it up. I just had 
to know about it in case of emergency.

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN


Re: Page Datasets in User Catalog

2023-11-23 Thread Jon Perryman
On Fri, 24 Nov 2023 00:12:34 +, Seymour J Metz  wrote:

>Are you saying that PAGEADD will work with alias entries and that the added 
>datasets will be retained across IPL?

Sorry, I worded it incorrectly. I didn't mean to imply I had experience using 
pageadd in that respect. 

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN


Re: Page Datasets in User Catalog

2023-11-23 Thread Mark Jacobs
I tried a pageadd of a newly defined page dataset that was cataloged in a user 
catalog. It didn't work. The command said it wasn't cataloged even though a 
listcat command was able to find it using the MLA in the master catalog. I 
didn't try an IPL with it in parmlib. I assumed that if the pageadd failed, it 
wouldn't work at IPL time either.

Mark Jacobs

Sent from ProtonMail, Swiss-based encrypted email.

GPG Public Key - 
https://api.protonmail.ch/pks/lookup?op=get=markjac...@protonmail.com


On Thursday, November 23rd, 2023 at 7:12 PM, Seymour J Metz  
wrote:


> Are you saying that PAGEADD will work with alias entries and that the added 
> datasets will be retained across IPL?
> 
> 
> --
> Shmuel (Seymour J.) Metz
> http://mason.gmu.edu/~smetz3
> עַם יִשְׂרָאֵל חַי
> 
> 
> 
> 
> From: IBM Mainframe Discussion List IBM-MAIN@LISTSERV.UA.EDU on behalf of Jon 
> Perryman jperr...@pacbell.net
> 
> Sent: Thursday, November 23, 2023 3:20 PM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: Re: Page Datasets in User Catalog
> 
> On Wed, 22 Nov 2023 22:35:13 +, Seymour J Metz sme...@gmu.edu wrote:
> 
> > I suspect that there was a game of telegraph, whereby crucial details got 
> > lost.
> > 
> > It is normal to allocate page datasets in a user catalog that will 
> > eventually be used as a master catalog.
> > I'm suspicious of the claim that z/OS can use a page dataset that is not in 
> > its own master catalog, but I can't rule it out.
> 
> 
> There are definitely crucial details lost. Page and swap are special 
> datasets. For instance, a page dataset can be in multiple catalogs (I think 
> using recatalog). Only page datasets specified in PARMLIB must be in the 
> master catalog. Without details, we're only guessing how it's being used.
> 
> --
> For IBM-MAIN subscribe / signoff / archive access instructions,
> send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
> 
> --
> For IBM-MAIN subscribe / signoff / archive access instructions,
> send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN


Re: Page Datasets in User Catalog

2023-11-23 Thread Seymour J Metz
Are you saying that PAGEADD will work with alias entries and that the added 
datasets will be retained across IPL?


-- 
Shmuel (Seymour J.) Metz
http://mason.gmu.edu/~smetz3
עַם יִשְׂרָאֵל חַי




From: IBM Mainframe Discussion List  on behalf of Jon 
Perryman 
Sent: Thursday, November 23, 2023 3:20 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Page Datasets in User Catalog

On Wed, 22 Nov 2023 22:35:13 +, Seymour J Metz  wrote:

>I suspect that there was a game of telegraph, whereby crucial details got lost.
>
>It is normal to allocate page datasets in a user catalog that will eventually 
>be used as a master catalog.
> I'm suspicious of the claim that z/OS can use  a page dataset that is not in 
> its own master catalog, but I can't rule it out.

There are definitely crucial details lost. Page and swap are special datasets. 
For instance, a page dataset can be in multiple catalogs (I think using 
recatalog). Only page datasets specified in PARMLIB must be in the master 
catalog. Without details, we're only guessing how it's being used.

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN


Re: Page Datasets in User Catalog

2023-11-23 Thread Jon Perryman
On Wed, 22 Nov 2023 22:35:13 +, Seymour J Metz  wrote:

>I suspect that there was a game of telegraph, whereby crucial details got lost.
>
>It is normal to allocate page datasets in a user catalog that will eventually 
>be used as a master catalog.
> I'm suspicious of the claim that z/OS can use  a page dataset that is not in 
> its own master catalog, but I can't rule it out.

There are definitely crucial details lost. Page and swap are special datasets. 
For instance, a page dataset can be in multiple catalogs (I think using 
recatalog). Only page datasets specified in PARMLIB must be in the master 
catalog. Without details, we're only guessing how it's being used. 

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN


Re: Page Datasets in User Catalog

2023-11-22 Thread Seymour J Metz
I suspect that there was a game of telegraph, whereby crucial details got lost.

It is normal to allocate page datasets in a user catalog that will eventually 
be used as a master catalog. I'm suspicious of the claim that z/OS can use  a 
page dataset that is not in its own master catalog, but I can't rule it out.

Wasn't there a song called "Charlie on the MLA"?

--
Shmuel (Seymour J.) Metz
http://mason.gmu.edu/~smetz3
עַם יִשְׂרָאֵל חַי




From: IBM Mainframe Discussion List  on behalf of Tom 
Marchant <000a2a8c2020-dmarc-requ...@listserv.ua.edu>
Sent: Wednesday, November 22, 2023 1:22 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Page Datasets in User Catalog

The Initialization and Tuning Reference seems to say otherwise.
https://www.ibm.com/docs/en/zos/3.1.0?topic=ieasysxx-page

"Usually, page data sets specified by any means must have been allocated, 
cataloged in the system's master catalog, and preformatted in VSAM format 
before an IPL can start."

"It is unnecessary to specify either UNIT or VOLSER because all page data sets 
must be cataloged in the system's master catalog."

It might be possible to use PAGEADD to add a page data set that is cataloged in 
a user catalog, but I wouldn't be surprised if that leads to problems at the 
next IPL

Surely, at CLPA time the Catalog address space is not yet available.

--
Tom Marchant

On Wed, 22 Nov 2023 17:32:26 +, Mark Jacobs  
wrote:

>Our storage administrator had told me that in a previous organization they 
>successfully used page datasets that were cataloged in a user catalog rather 
>that in the master catalog by using an MLA in the MCAT. I tried it in our 
>sandbox environment (2.5) and it didn't work. I had never heard of doing this 
>before and I had my doubts, but wanted to try it anyway. Has anyone else tried 
>it and gotten it to work?

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN


Re: Page Datasets in User Catalog

2023-11-22 Thread Willy Jensen
Maybe s/he was thinking about defining them, which I am pretty sure I have done 
in a distant past using MLA, rather actually using them.

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN


Re: Page Datasets in User Catalog

2023-11-22 Thread Tom Marchant
The Initialization and Tuning Reference seems to say otherwise.
https://www.ibm.com/docs/en/zos/3.1.0?topic=ieasysxx-page

"Usually, page data sets specified by any means must have been allocated, 
cataloged in the system's master catalog, and preformatted in VSAM format 
before an IPL can start."

"It is unnecessary to specify either UNIT or VOLSER because all page data sets 
must be cataloged in the system's master catalog."

It might be possible to use PAGEADD to add a page data set that is cataloged in 
a user catalog, but I wouldn't be surprised if that leads to problems at the 
next IPL

Surely, at CLPA time the Catalog address space is not yet available.

-- 
Tom Marchant

On Wed, 22 Nov 2023 17:32:26 +, Mark Jacobs  
wrote:

>Our storage administrator had told me that in a previous organization they 
>successfully used page datasets that were cataloged in a user catalog rather 
>that in the master catalog by using an MLA in the MCAT. I tried it in our 
>sandbox environment (2.5) and it didn't work. I had never heard of doing this 
>before and I had my doubts, but wanted to try it anyway. Has anyone else tried 
>it and gotten it to work?

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN


Page Datasets in User Catalog

2023-11-22 Thread Mark Jacobs
Our storage administrator had told me that in a previous organization they 
successfully used page datasets that were cataloged in a user catalog rather 
that in the master catalog by using an MLA in the MCAT. I tried it in our 
sandbox environment (2.5) and it didn't work. I had never heard of doing this 
before and I had my doubts, but wanted to try it anyway. Has anyone else tried 
it and gotten it to work?

The Ministry of Silly Questions thanks you in advance for your replies!

Sent from [ProtonMail](https://protonmail.com), Swiss-based encrypted email.

GPG Public Key - 
https://api.protonmail.ch/pks/lookup?op=get=markjac...@protonmail.com

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN