On Wed, 18 Oct 2017 22:10:57 +0000, Jesse 1 Robinson wrote:
>You remember correctly. In my first IT job as a programmer trainee, I came to
>be the 'test proclib fixer'. Some yahoo would copy a member into
>it--specifying incorrect blocksize I suppose--and alter the library's
>blocksize. I would get a help call. I would run IIRC a dummy IEBUPDATE job
>with a null SYSUT1 and a SYSUT2 that specified the correct blocksize.
>
>As long as the DSCB blocksize is at least as large as the largest actual
>member data, no error occurs. But if DSCB is set smaller, attempts to access a
>larger member gets I/O error. At least that's how it was in 1978.
>
You might be able to recover both the PDS and the offending member with:
//EXEC PGM=IEBGENER
//SYSUT1 DD BLKSIZ=bad-blksize,DSN=dsn(offending-member)
//SYSUT2 DD BLKSIZ=good-blksize,DSN=dsn(offending-member)
I believe IEBGENER reblocks from SYSUT1 to SYSUT2
Don't try this unless your backups are current.
-- gil
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
