Partition dataset got corrupted and is giving I/O error

Neil Culleton · New User Joined: 16 Jul 2008 Posts: 1 Location: Australia

For the next person who <blush> corrupts a dataset by writing to it using a wrong LRECL, the above solution works.

In my case i needed more DCB parms:
===================================
//COPY1 EXEC PGM=IEBGENER
//SYSUT1 DD *
DUMMY RECORD
/*
//SYSUT2 DD DISP=OLD,DSN=HLQ.XXX.YYY(DUMMY),
// DCB=(RECFM=FB,LRECL=80,BLKSIZE=27920)
===================================

Using just LRECL or just BLKSIZE was giving:
'IEB311I CONFLICTING DCB PARAMETERS' on the IEBGENER.

Cheers,
Neil.

Pedro

gcicchet · Senior Member Joined: 28 Jul 2006 Posts: 654

Hi,

I'm surprised to hear how often PDS become corrupted, surely it warrants investigating the problem.

I remember having the occasional one and found that utilities like IEBGENER, IDCAMS, SORT and even REXX's causing problems, I found by creating temporary PDS's and using IEBCOPY to copy the member to the target library, problems seemed to disappear.

I don't remember corruptions being caused by IEBCOPY.

Now that's not to say I don't use these utilities to write directly into the target libraries, but I try to avoid it.

Gerry

dick scherrer · Posted: Thu Jul 17, 2008 7:36 pm Post subject:

Hi Gerry,

dbzTHEdinosauer · Posted: Thu Jul 17, 2008 7:55 pm Post subject:

or people writting rexx scripts to modify and don't bother creating and using a test (copy) pds first.

Pedro

Instead of PDSs, I think people should use PDSEs. Functionality is the same. But the underlying organization is different. I think you can you avoid many of the problems that you might have with a PDS.