In the absence of a truly informed response, I'll take a stab. I learned that a (QSAM) I/O request specifying a block size less than the actual size-of-block results in an abend/RC that describes the error. OTOH if the size-of-block is lower than requested, the operation is successful; it's up to the program to manage the shorter-than-expected data.
I've never dealt with BSAM, which may behave differently. There also may be a difference between FB and VB. . . . J.O.Skip Robinson Southern California Edison Company Electric Dragon Team Paddler SHARE MVS Program Co-Manager 626-302-7535 Office 323-715-0595 Mobile jo.skip.robin...@sce.com -----Original Message----- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Paul Gilmartin Sent: Monday, December 22, 2014 8:37 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: BDW length vs. Physical Length For RECFM=V(B)(S), what happens if the physical length of a block exceeds the length in the BDW? o Bytes in the physical block beyond the length in the BDW are ignored? (A writer on another list tells me I can rely on this.) o The access method reports an error? I prefer to follow the rules. Suppose the programmer reads blocks with BSAM and performs strict error checking? Suppose the programmer reads a VBS file on a non-z system and performs strict error checking? (SMP/E copies IEBCOPY relative files to UNIX files and relies on the BDWs to reconstitute the VBS data set.) -- gil ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN