&T Service Delivery & Engineering
Office: 512-326-6173
Cell: 925-348-0237
-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf
Of Edward Finnell
Sent: Thursday, March 10, 2016 12:17 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: [EXTERNAL
17 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: [EXTERNAL] Re: Corrupt PDSE dataset
Restore from backup?
In a message dated 3/10/2016 12:12:29 P.M. Central Standard Time,
lionel.d...@va.gov writes:
What do y'all recommend when a PDSE goes bad and the IEBPDSE just reports that
it has a bad direct
Tom - how right you are - I've opened a PMR with IBM and am awaiting their
response.
Are you saying I can back it up with DFDSS and then try to restore it and it
might work?
--
Lionel B. Dyck (Contractor)
Mainframe Systems
Haven't heard from JK in a while. PDS86 has fixpds command. I've used it on
100's of PDS's but not a PDSE. Might try on a unusable restored copy?
In a message dated 3/10/2016 12:48:14 P.M. Central Standard Time,
lionel.d...@va.gov writes:
Are you saying I can back it up with DFDSS and the
copy to new file. See what is broken
Lizette
-Original Message-
>From: "Dyck, Lionel B. (TRA)"
>Sent: Mar 10, 2016 11:19 AM
>To: IBM-MAIN@LISTSERV.UA.EDU
>Subject: Re: [EXTERNAL] Re: Corrupt PDSE dataset
>
>Tried restore from backup but there isn
Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf
Of Edward Finnell
Sent: Thursday, March 10, 2016 10:58 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: (External):Re: [EXTERNAL] Re: Corrupt PDSE dataset
Haven't heard from JK in a while. PDS86 has fixpds command. I've used it
PDSE dataset
copy to new file. See what is broken
Lizette
-Original Message-
>From: "Dyck, Lionel B. (TRA)"
>Sent: Mar 10, 2016 11:19 AM
>To: IBM-MAIN@LISTSERV.UA.EDU
>Subject: Re: [EXTERNAL] Re: Corrupt PDSE dataset
>
>Tried restore from backup but there is
LISTSERV.UA.EDU] On Behalf
Of Jesse 1 Robinson
Sent: Thursday, March 10, 2016 7:08 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: [EXTERNAL] Re: Corrupt PDSE dataset
I have the Serena program product version StarTool. FIXPDS is there for a PDSE,
but I don't have a broken data set to experime
6 7:08 PM
>To: IBM-MAIN@LISTSERV.UA.EDU
>Subject: Re: [EXTERNAL] Re: Corrupt PDSE dataset
>
>I have the Serena program product version StarTool. FIXPDS is there for a
>PDSE, but I don't have a broken data set to experiment with. The options are
>fewer than for PDS
16 8:09 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: [EXTERNAL] Re: Corrupt PDSE dataset
On Thu, 10 Mar 2016 12:12:09 -0600, Dyck, Lionel B. wrote:
>What do y'all recommend when a PDSE goes bad and the IEBPDSE just reports that
>it has a bad directory?
I don't know how to fix it
W dniu 2016-03-11 o 15:20, Dyck, Lionel B. (TRA) pisze:
We have shared dasd between two different sysplexes and grs is only within each
sysplex. How it broke I've no idea but suspect it was updated on each side.
It's the best method to corrupt PDSE.
BTW: GRS won't help, because PDSE use XCF A
nal Message-
>> From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On
>> Behalf Of Jesse 1 Robinson
>> Sent: Thursday, March 10, 2016 7:08 PM
>> To: IBM-MAIN@LISTSERV.UA.EDU
>> Subject: Re: [EXTERNAL] Re: Corrupt PDSE dataset
>>
>>
2016 3:56 PM
>To: IBM-MAIN@LISTSERV.UA.EDU
>Subject: Re: [EXTERNAL] Re: Corrupt PDSE dataset
>
>copy to new file. See what is broken
>Lizette
>
>-Original Message-
>>From: "Dyck, Lionel B. (TRA)"
>>Sent: Mar 10, 2016 11:19 AM
>>To: IBM-MAIN@LI
frame Discussion List
Subject: Re: [EXTERNAL] Re: Corrupt PDSE dataset
W dniu 2016-03-11 o 15:20, Dyck, Lionel B. (TRA) pisze:
> We have shared dasd between two different sysplexes and grs is only within
> each sysplex. How it broke I've no idea but suspect it was updated on each
> side.
I
.EDU] On Behalf
Of Lizette Koehler
Sent: Friday, March 11, 2016 10:05 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: [EXTERNAL] Re: Corrupt PDSE dataset
If you could provide fuller error messages it might help. Subcode for 0f4. And
any ibe-like messages.
It might make more sense
Lizette
-
11:07 AM
Subject: Re: [EXTERNAL] Re: Corrupt PDSE dataset
IBM has always stated that you CANNOT share a PDSE outside SYSPLEX boundaries
without a risk of corruption. It sounds like you did just that.
That's a big OOPS!
-teD
Original Message
From: R.S.
Sent: Friday, March 11, 2016
On Fri, 11 Mar 2016 23:34:32 +, David Mingee wrote:
>Lionel, are all of the DCB values normal or correct, if not they can be
>changed with PDS86.
>
Knowing almost nothing about PDSE internals, I'd hesitate to change DCB
attributes with a tool such as PDS86. Those attributes may be reflected
Mainframe Consulting
9206 Aintree Drive
Indianapolis, IN 46250
317 288-9588 Home317 903-9455 Cell
From: Paul Gilmartin <000433f07816-dmarc-requ...@listserv.ua.edu>
To: IBM-MAIN@LISTSERV.UA.EDU
Sent: Friday, March 11, 2016 7:02 PM
Subject: Re: [EXTERNAL] Re: Corrupt PDSE d
925-348-0237
-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf
Of David Mingee
Sent: Friday, March 11, 2016 5:35 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: [EXTERNAL] Re: Corrupt PDSE dataset
Lionel, are all of the DCB values normal or cor
19 matches
Mail list logo
