Actually if it's something web accessible I was wondering if the way back
machine had it??
Rob
On Mon, May 2, 2022, 17:03 Attila Fogarasi wrote:
> Is this sufficient?
> https://www.ibm.com/docs/en/linux-on-systems?topic=setup-hyperpav
>
> On Mon, May 2, 2022 at 9:27 PM Seymour J Metz wrote:
>
I can attest to that. I once updated a shared JES2 PDSE outside of a plex
and toasted the thing. Required a restore.
On Mon, May 2, 2022 at 3:21 PM Doug wrote:
> You can't use PDSE's across SYSPLEX boundaries. Period. Read works most
> of the time, but no guarantees.
> Write really not at all.
It's bizarre, no? IBM did it for VSE but not z/OS -- isn't that right?
Charles
-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf
Of Doug
Sent: Monday, May 2, 2022 1:20 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Serialization of PDSE Que
Is this sufficient?
https://www.ibm.com/docs/en/linux-on-systems?topic=setup-hyperpav
On Mon, May 2, 2022 at 9:27 PM Seymour J Metz wrote:
> A wiki editor recently removed the HyperPAVs section from [[Unit Control
> Block]] with the explanation "Rm old uncited". Is there a good online
> secondar
You can't use PDSE's across SYSPLEX boundaries. Period. Read works most
of the time, but no guarantees.
Write really not at all.
Doug Fuerst
d...@bkassociates.net
-- Original Message --
From: "Petersen, David" <041cefae9839-dmarc-requ...@listserv.ua.edu>
To: IBM-MAIN@listserv.ua.edu
I don't think MIM changes anything on this issue. If the PDSE is subject to
updates from anywhere, you cannot safely share it across Sysplex boundaries.
Read-only works, but is not, TBOMK, supported.
> -Original Message-
> From: IBM Mainframe Discussion List On
> Behalf Of Carmen Vitull
We are currently a MIM shop, soon to be converting to a GRS RING, 3
system sysplex, all PDSE sharing is controlled via XCF, in your IGDSMSxx
parms you specify PDSESHARING(EXTENDED), you can also supply the
optional PDSE_RESTARTAB LE_AS(YES)
I checked our MIM parms and I don't see anything spec
HI,
We are a MIM Shop that does not use GRS. Our shop has a two LPAR SYSPLEX and a
MONOPLEX that shares DASD/Datasets/Master Catalog. We are a little behind
installing z/OS2.4 and the necessary push to move to PDSE.
Does anyone have experience with using MIM to sequence/serialize PDSE access
Meant to reply to this and it slipped my mind.
Looking at code of mine -- not thought about since 2018 -- it *looks* like I
assume Header, then General, then Control, then Program Objects, then Text
Objects, in that order. I'm not saying that is the right way to do things but I
can say that the
Peter,
Thanks.
This makes a world of difference.
Regards, Pierre.
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Pierre,
You can probably accept the text objects in the order you find them because
as you note, you don't really have other options. However, you probably
shouldn't make assumptions regarding the other objects.
In SYS1.SAMPLIB you can find an example of processing MDBs. IEAMDBLG reads
MDB
On Mon, 2 May 2022 11:20:59 +, Seymour J Metz wrote:
>Requiring a manual install mighyt redfuce the appeal of the product.
>
Supply JCL to move the putative script into SYSEXEC, avoiding
manual install.
Then supply a tool to move that JCL into PROCLIB.
Then supply ... Rats! Infinite regres
Hmm ... Sounds like IOF's ARChive command.
On 2022-05-02 08:07, Lionel B. Dyck wrote:
Kirk - I know of no way to add a descriptor record separating each DD when
extracting multiple DD's using SDSF to a single target dataset.
That does look to be a useful feature - you should submit an RFE for i
Kirk - I know of no way to add a descriptor record separating each DD when
extracting multiple DD's using SDSF to a single target dataset.
That does look to be a useful feature - you should submit an RFE for it.
Lionel B. Dyck <><
Website: https://www.lbdsoftware.com
Github: https://github.com/l
I'm sorry if I was not clear. I was looking for something that used standard
SDSF commands and does not require that a client have some REXX code of any
kind. It's more about the usage context rather than anything pejorative about
REXX.
On Sun, May 1, 2022, at 6:30 PM, Paul Gilmartin wrote:
A wiki editor recently removed the HyperPAVs section from [[Unit Control
Block]] with the explanation "Rm old uncited". Is there a good online secondary
source for PAV and HyperPAV? Thanks.
--
Shmuel (Seymour J.) Metz
http://mason.gmu.edu/~smetz3
--
Requiring a manual install mighyt redfuce the appeal of the product.
--
Shmuel (Seymour J.) Metz
http://mason.gmu.edu/~smetz3
From: IBM Mainframe Discussion List [IBM-MAIN@LISTSERV.UA.EDU] on behalf of
Kirk Wolf [k...@dovetail.com]
Sent: Sunday, May 1, 2
It would be a lot more work to install z/OS without using REXX, and REXX would
still be there even if you didn't use it.
--
Shmuel (Seymour J.) Metz
http://mason.gmu.edu/~smetz3
From: IBM Mainframe Discussion List [IBM-MAIN@LISTSERV.UA.EDU] on behalf of
There isn't; REXX is part of TSO/E.
--
Shmuel (Seymour J.) Metz
http://mason.gmu.edu/~smetz3
From: IBM Mainframe Discussion List [IBM-MAIN@LISTSERV.UA.EDU] on behalf of
Gibney, Dave [03b5261cfd78-dmarc-requ...@listserv.ua.edu]
Sent: Sunday, May 1, 20
19 matches
Mail list logo
