Fair enough 😊. -----Original Message----- From: IBM Mainframe Discussion List <IBM-MAIN@LISTSERV.UA.EDU> On Behalf Of Seymour J Metz Sent: 27 April 2023 11:25 To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Unlike data sets concatenation - revised
ObPedant For lo these many years the DASD "physical record" has actually been a logical record in DASD with a different architecture. That said, in DFSMSdfp, "physical record size" refers to the block size as seen at the channel, not to the block size of the underlying DASD; "logical record size" refers to either a segment of a physical record, or, for spanned records, a record constructed from a sequence of such segments, and the meaning of "record" depends upon context. -- Shmuel (Seymour J.) Metz http://mason.gmu.edu/~smetz3 ________________________________________ From: IBM Mainframe Discussion List [IBM-MAIN@LISTSERV.UA.EDU] on behalf of Lennie Dymoke-Bradshaw [0000032fff1be9b4-dmarc-requ...@listserv.ua.edu] Sent: Thursday, April 27, 2023 3:58 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Unlike data sets concatenation - revised The reference to record as a segment of a physical block is really a "logical record". Hence LRECL stands for "logical record length". The "WRNG.LEN.RECORD" reference is speaking of physical records or block. Lennie -----Original Message----- From: IBM Mainframe Discussion List <IBM-MAIN@LISTSERV.UA.EDU> On Behalf Of Mike Schwab Sent: 27 April 2023 00:43 To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Unlike data sets concatenation - revised A DASD record is a physical block. Contents of the block depend on the RECFM=, i.e. U for load modules, VB for variable blocked, FB for Fixed Blocked. On Wed, Apr 26, 2023 at 6:11 PM Seymour J Metz <sme...@gmu.edu> wrote: > > The DASD documentation uses the term record. > > > -- > Shmuel (Seymour J.) Metz > http://mason.gmu.edu/~smetz3 > > ________________________________________ > From: IBM Mainframe Discussion List [IBM-MAIN@LISTSERV.UA.EDU] on > behalf of Paul Gilmartin > [0000042bfe9c879d-dmarc-requ...@listserv.ua.edu] > Sent: Wednesday, April 26, 2023 6:08 PM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: Re: Unlike data sets concatenation - revised > > On Wed, 26 Apr 2023 13:44:21 -0700, Michael Stein wrote: > > >> 000234D0 E6D9D5C7 4BD3C5D5 4BD9C5C3 D6D9C46B | WRNG.LEN.RECORD, > >> | > > > >A likely result from reading a block larger than the blksize. > > > Why does it say "RECORD" if it means "Block"? > > > ... > >What does the *SOURCE* DCB & JCL look like? Do either specify LRECL > >and/or BLKSIZE? > > > Just cut the Gordian Knot and specify the largest BLKSIZE expected; even > 32760. > LRECL likewise. Storage is cheap nowadays. > > -- > gil > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, send > email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, send > email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- Mike A Schwab, Springfield IL USA Where do Forest Rangers go to get away from it all? ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
