-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
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
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
Sent: Friday, March 11, 2016 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:
.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
-Original Mes
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.
It's the be
TSERV.UA.EDU
>Subject: Re: [EXTERNAL] Re: Corrupt PDSE dataset
>
>Liz - good to see you
>
>How should I do the copy? IEBCOPY fails as does ispf 3.3 as well as pds copy.
> I can copy specific members but I don't know all the members that were added
>after the backup was taken. Those m
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
>>
>> I have the Serena program
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
9 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, but I am curious
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, but I am curious as to what happened to it.
Is the broken PDSE shared outside of the sysplex?
--
Tom
o: 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 largely because you
] 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 experiment with. The options
and when trying to access it the result is
an Abend 0F4 :(
-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf
Of Lizette Koehler
Sent: Thursday, March 10, 2016 3:56 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: [EXTERNAL] Re: Corrupt PDSE
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 on
100's of PDS's
copy to new file. See what is broken
Lizette
-Original Message-
>From: "Dyck, Lionel B. (TRA)" <lionel.d...@va.gov>
>Sent: Mar 10, 2016 11:19 AM
>To: IBM-MAIN@LISTSERV.UA.EDU
>Subject: Re: [EXTERNAL] Re: Corrupt PDSE dataset
>
>Tried restore from backup
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
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
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 directory?
Lionel,
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] Re: Corrupt
12:09 PM
Subject: Corrupt PDSE dataset
What do y'all recommend when a PDSE goes bad and the IEBPDSE just
reports that it has a bad directory?
Thanks
--
Lionel B. Dyck (Contractor)
Mainframe Systems Programmer
Enterprise Infras
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 directory?
What do y'all recommend when a PDSE goes bad and the IEBPDSE just reports that
it has a bad directory?
Thanks
--
Lionel B. Dyck (Contractor)
Mainframe Systems Programmer
Enterprise Infrastructure Support (Station 200)
===start
The dataset has a member which has all configuration Parms for a running STC
This was updated when STC was up and running
So This could be a reason for a possible corruption ?
end===
Yes.
how about moving the members to a sequential file each ?
- ravi.
ps: never peek at another SYSPLEX's PDSEs ...
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the
At 22:43 +0530 on 07/15/2015, Jake Anderson wrote about Re: Corrupt PDSE:
Hi
The dataset has a member which has all configuration Parms for a running STC
This was updated when STC was up and running
So This could be a reason for a possible corruption ?
Why not move that member to a PDS
Of Jake Anderson
Sent: Wednesday, July 15, 2015 10:13 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Corrupt PDSE
Hi
The dataset has a member which has all configuration Parms for a running
STC
This was updated when STC was up and running
So This could be a reason for a possible corruption
AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Corrupt PDSE
Hello,
I get below message when i try to access a PDSE dataset, but when I try to
access the same Dataset from a different SYSPLEX it opens up. We do share
the Dasd .
IGW702I PDSE Directory Validation Unsuccessful DESC:ND Structure
-MAIN@LISTSERV.UA.EDU javascript:;
Subject: Re: Corrupt PDSE
Ibm Info on corrupted PDSEs:
http://www-01.ibm.com/support/docview.wss?uid=isg1II14252
On Wed, Jul 15, 2015 at 11:39 AM, Jake Anderson
justmainfra...@gmail.com javascript:;
wrote:
Hello,
I get below message when i
Look into the fact that you can't share PDSE's across SYSPLEX's.
-
-teD
-
Original Message
From: Jake Anderson
Sent: Wednesday, July 15, 2015 17:31
To: IBM-MAIN@LISTSERV.UA.EDU
Reply To: IBM Mainframe Discussion List
Subject: Corrupt PDSE
Hello,
I get below message when i try to access
jo.skip.robin...@sce.com
-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf
Of Staller, Allan
Sent: Wednesday, July 15, 2015 8:46 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Corrupt PDSE
PDSE's *CANNOT* be shared across SYSPLEX Boundaries
Hello,
I get below message when i try to access a PDSE dataset, but when I try to
access the same Dataset from a different SYSPLEX it opens up. We do share
the Dasd .
IGW702I PDSE Directory Validation Unsuccessful
DESC:ND Structure is corrupted
LTK:
PDSE's *CANNOT* be shared across SYSPLEX Boundaries.
PDSE's *CAN* be shared within a SYSPLEX if the SMSPDSE* address spaces are
running...
HTH,
snip
I get below message when i try to access a PDSE dataset, but when I try to
access the same Dataset from a different SYSPLEX it opens up. We do
Ibm Info on corrupted PDSEs:
http://www-01.ibm.com/support/docview.wss?uid=isg1II14252
On Wed, Jul 15, 2015 at 11:39 AM, Jake Anderson justmainfra...@gmail.com
wrote:
Hello,
I get below message when i try to access a PDSE dataset, but when I try to
access the same Dataset from a different
Hank Oerlemans,
IBM Fault Analyzer
From: Thomas Berg thomas.b...@swedbank.se
To: IBM-MAIN@LISTSERV.UA.EDU
Date: 26/05/2015 11:48
Subject:Re: Corrupt PDSE - IGW699I PDSE Directory Validation
Unsuccessful
Sent by:IBM Mainframe Discussion List IBM-MAIN@LISTSERV.UA.EDU
BTW
)
Interactive is 'manual.' Batch is 'automatic.'
-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On
Behalf Of
Hank Oerlemans
Sent: Tuesday, May 26, 2015 8:14 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Corrupt PDSE - IGW699I PDSE Directory
@LISTSERV.UA.EDU
Subject: Re: Corrupt PDSE - IGW699I PDSE Directory Validation Unsuccessful
Yea, it looks damaged to me too. I'd still recommend that you validate the
integrity of the restored dataset, just to be safe.
Mark Jacobs
Thomas Berg mailto:thomas.b...@swedbank.se May 25, 2015 at 10:00 PM
Tried
Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On
Behalf Of
Lizette Koehler
Sent: Tuesday, May 26, 2015 3:33 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Corrupt PDSE - IGW699I PDSE Directory Validation Unsuccessful
Check the dataset on other systems. See if the error is consistent.
How
@LISTSERV.UA.EDU] On
Behalf Of
Mark Jacobs - Listserv
Sent: Tuesday, May 26, 2015 3:50 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Corrupt PDSE - IGW699I PDSE Directory Validation Unsuccessful
Three more questions.
1. Do you have all the required toleration maintenance applied on your
@LISTSERV.UA.EDU
Subject: Corrupt PDSE - IGW699I PDSE Directory Validation Unsuccessful
Got a corrupt PDSE. Will throw the problem at some of the responsible
sysprogs.
But in the meantime I wonder if any of the esteem members of this list can
give some hints leading to the cause.
Got this when tying
Could it have been shared(R/W) outside of a sysplex boundary?
Mark Jacobs
Thomas Berg mailto:thomas.b...@swedbank.se
May 25, 2015 at 8:43 PM
Got a corrupt PDSE. Will throw the problem at some of the responsible
sysprogs.
But in the meantime I wonder if any of the esteem members of this list
-MAIN
Mark Jacobs - Listserv mailto:mark.jac...@custserv.com
May 25, 2015 at 9:09 PM
Could it have been shared(R/W) outside of a sysplex boundary?
Mark Jacobs
Thomas Berg mailto:thomas.b...@swedbank.se
May 25, 2015 at 8:43 PM
Got a corrupt PDSE. Will throw the problem at some of the responsible
Yea, it looks damaged to me too. I'd still recommend that you validate
the integrity of the restored dataset, just to be safe.
Mark Jacobs
Thomas Berg mailto:thomas.b...@swedbank.se
May 25, 2015 at 10:00 PM
Tried on another prodsystem. Got this:
IGW699I PDSE Directory Validation Unsuccessful
: Corrupt PDSE - IGW699I PDSE Directory Validation Unsuccessful
Could it have been shared(R/W) outside of a sysplex boundary?
Mark Jacobs
Thomas Berg mailto:thomas.b...@swedbank.se
May 25, 2015 at 8:43 PM
Got a corrupt PDSE. Will throw the problem at some of the responsible
sysprogs
Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On
Behalf Of
Mark Jacobs - Listserv
Sent: Tuesday, May 26, 2015 3:27 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Corrupt PDSE - IGW699I PDSE Directory Validation Unsuccessful
If you take a physical dump of the dataset and send it into IBM
.'
-Original Message-
From: Thomas Berg
Sent: Tuesday, May 26, 2015 3:46 AM
To: 'IBM Mainframe Discussion List'
Subject: RE: Corrupt PDSE - IGW699I PDSE Directory Validation Unsuccessful
Did run IEBPDSE, but no new info compared to the abend result I posted below:
IGW699I PDSE Directory
[mailto:IBM-MAIN@LISTSERV.UA.EDU] On
Behalf Of
Mark Jacobs - Listserv
Sent: Tuesday, May 26, 2015 3:50 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Corrupt PDSE - IGW699I PDSE Directory Validation Unsuccessful
Three more questions.
1. Do you have all the required toleration maintenance applied
)
Interactive is 'manual.' Batch is 'automatic.'
-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On
Behalf Of
Mark Jacobs - Listserv
Sent: Tuesday, May 26, 2015 4:04 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Corrupt PDSE - IGW699I PDSE
Got a corrupt PDSE. Will throw the problem at some of the responsible
sysprogs.
But in the meantime I wonder if any of the esteem members of this list can give
some hints leading to the cause.
Got this when tying a browse from ISPF 3.4 (linecmd B):
IGW699I PDSE Directory Validation
...@listserv.ua.edu with the message: INFO IBM-MAIN
Mark Jacobs - Listserv mailto:mark.jac...@custserv.com
May 25, 2015 at 9:09 PM
Could it have been shared(R/W) outside of a sysplex boundary?
Mark Jacobs
Thomas Berg mailto:thomas.b...@swedbank.se
May 25, 2015 at 8:43 PM
Got a corrupt PDSE. Will throw
Sent: Tuesday, May 26, 2015 4:04 AM
To: IBM-MAIN@LISTSERV.UA.EDU javascript:;
Subject: Re: Corrupt PDSE - IGW699I PDSE Directory Validation
Unsuccessful
Yea, it looks damaged to me too. I'd still recommend that you validate
the integrity of the restored dataset, just to be safe
)
Interactive is ‘manual.’ Batch is ‘automatic.’
-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On
Behalf Of Dan
Little
Sent: Tuesday, May 26, 2015 4:40 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Corrupt PDSE - IGW699I PDSE Directory
javascript:;] On Behalf Of Dan
Little
Sent: Tuesday, May 26, 2015 4:40 AM
To: IBM-MAIN@LISTSERV.UA.EDU javascript:;
Subject: Re: Corrupt PDSE - IGW699I PDSE Directory Validation
Unsuccessful
Sounds like oa45027.
On Monday, May 25, 2015, Thomas Berg thomas.b...@swedbank.se
53 matches
Mail list logo
