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. . . J.O.Skip Robinson Southern California Edison Company Electric Dragon Team Paddler SHARE MVS Program Co-Manager 323-715-0595 Mobile 626-543-6132 Office ⇐=== NEW robin...@sce.com -----Original Message----- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Bill Ashton Sent: Wednesday, October 18, 2017 10:43 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: (External):How to fix blocksize of PDS Hello friends...I ran some job some time in the past, and it whacked my PDS blocksize (and reset it to the LRECL). I thought I remembered that there is a slick little job I can run to reset it back to what I need, but I can't remember the particulars. I know it did not involve copying the file, but IIRC, I had only to open the file, and use a disp of old,keep with the correct DCB. Am I remembering correctly, or is my old brain showing errors? Billy -- Thank you and best regards, *Billy Ashton* ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
