Bad Member in a PDS



Help for IBM's record-oriented filesystem VSAM, ESDS, KSDS, RRDS, LDS and Storage management Subsystems

Bad Member in a PDS

Postby hdevang4u » Fri Mar 29, 2013 9:01 am

Hi,

I have a huge PDS with more than 30,000 members in it. There is possibly a corrupted member in the PDS. Is there any JCL utility that can be used to identify the corrupted member?
hdevang4u
 
Posts: 4
Joined: Fri Mar 15, 2013 2:43 am
Has thanked: 0 time
Been thanked: 0 time

Re: Bad Member in a PDS

 

Re: Bad Member in a PDS

Postby BillyBoyo » Fri Mar 29, 2013 2:38 pm

Talk to your technical people. They are less likely to destroy the whole thing whilst attempting to fix it.

30,000 members in a single PDS? How long does it take to add a new member called "A"? Don't experiment until you know the PDS is good :-)
BillyBoyo
Global moderator
 
Posts: 3804
Joined: Tue Jan 25, 2011 12:02 am
Has thanked: 22 times
Been thanked: 264 times

Re: Bad Member in a PDS

Postby dick scherrer » Fri Mar 29, 2013 7:07 pm

Hello,

How might the member have become corrupt? What to you mean by "corrupt"? When did the problem occur?

Is there a backup just before the corruption occurred?
Hope this helps,
d.sch.
User avatar
dick scherrer
Global moderator
 
Posts: 6304
Joined: Sat Jun 09, 2007 8:58 am
Has thanked: 3 times
Been thanked: 91 times

Re: Bad Member in a PDS

Postby enrico-sorichetti » Fri Mar 29, 2013 7:18 pm

There is possibly a corrupted member in the PDS.


The TS does not even know if there is one :geek:
cheers
enrico
When I tell somebody to RTFM or STFW I usually have the page open in another tab/window of my browser,
so that I am sure that the information requested can be reached with a very small effort
enrico-sorichetti
Global moderator
 
Posts: 2644
Joined: Fri Apr 18, 2008 11:25 pm
Has thanked: 0 time
Been thanked: 130 times

Re: Bad Member in a PDS

Postby steve-myers » Sat Mar 30, 2013 12:13 am

BillyBoyo wrote:... 30,000 members in a single PDS? How long does it take to add a new member called "A"? Don't experiment until you know the PDS is good :-)
I'd like to know why the TS believes there is a corrupted member in the PDS!

The issue BillyBoyo raised about how long it would take to add a low member name in the collating sequence to the data set got me interested. I wrote a small Assembler program to add members M30000 through M00001, in that order. I did cheat in one respect. I did not attempt to write ISPF directory statistics. While I could have done that, it wasn't worth the effort for a throw a way program, but it did speed things up: the final directory used 1429 blocks, much less than the 5000 blocks required if the program wrote ISPF directory stats.

An Assembler programmer using BPAM to write to a PDS uses the STOW macro to add a member. When adding a member, the STOW macro does more than update the directory. It also writes a DASD end of file record for the member, and that requires a small amount of time.

I instrumented the program to collect the elapsed time required to execute the STOW macro. It rexorded the time in the next member it wrote. M29999 has the time required for the STOW macro for member M30000, and so on. M00001 has the time for M00002. I did not record the time for M00001.

Here are the raw times.

M00002 0.07 seconds
M00003 0.08 seconds
M00004 0.08 seconds
M30000 0.00 seconds
steve-myers
Global moderator
 
Posts: 1886
Joined: Thu Jun 03, 2010 6:21 pm
Has thanked: 4 times
Been thanked: 197 times


Return to VSAM/SMS

 


  • Related topics
    Replies
    Views
    Last post