Why is that an enhancement rather than a bug fix? Isn't SDB supposed to be active only if BLKSIZE=0? Are you sure that RECEIVE allocated the target with a nonzero block size?
-- Shmuel (Seymour J.) Metz http://mason.gmu.edu/~smetz3 ________________________________________ From: IBM Mainframe Discussion List [[email protected]] on behalf of Wendell Lovewell [[email protected]] Sent: Tuesday, March 2, 2021 10:35 AM To: [email protected] Subject: TSO RECEIVE and System Determined Blksize - New RFE If anyone has had a problem trying to use System Determined Blocksize with TSO RECEIVE and getting a message IEB1139W like: IEB1139W THE OUTPUT DATA SET BLOCK SIZE IS BEING REDUCED FROM 32720 TO 27920 BYTES. ANY EXISTING PHYSICAL RECORDS LONGER THAN 27920 BYTES ARE FAT BLOCKS AND MAY CAUSE I/O ERRORS. ...because SDB was changing the blksize between the time RECEIVE allocated the file according to the DCB information in the INMR02 record in the XMIT file and the time IEBCOPY tries to open it, I've opened an RFE in the hopes that IBM will correct the problem. Please consider watching and/or voting for RFE # 148961: TSO RECEIVE should correctly handle System Defined Blocksize = YES at http://www.ibm.com/developerworks/rfe/execute?use_case=viewRfe&CR_ID=148961 Thanks for your support. Wendell ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
