I use RECEIVE into an existing data set all the time. I've never seen DCB corruption.
SEND is another matter. Regardless of what you specify, the output is 3120. This usermod, which I've heard of but never used, apparently just zeroes out the hard-coded 3120 value. XMIT/RECEIVE is waaaay older than SDB. . . . J.O.Skip Robinson Southern California Edison Company Electric Dragon Team Paddler SHARE MVS Program Co-Manager 323-715-0595 Mobile 626-302-7535 Office [email protected] -----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of Paul Gilmartin Sent: Tuesday, May 31, 2016 8:31 AM To: [email protected] Subject: (External):Re: TSO receive on MultiVolume PS error On Tue, 31 May 2016 09:54:22 +0000, Field, Alan wrote: >Blksize 3120 is hardcoded. This usermod removes that restriction: > >++ USERMOD (LM00062) REWORK(2016003) > /* TRANSMIT OUTDA() FORCES THE BLKSIZE OF THE OUTPUT DATA SET > TO 3120 (X'0C30'). > THIS MOD SETS IT TO 0 (SYSTEM DETERMINED BLKSIZE). > INMXM IS IN SYS1.LINKLIB. > */ . >++ VER (Z038) FMID(HTE77A0) > . >++ ZAP (INMXM) . > NAME INMXM > VER 1AC4 0000,0C30 > REP 1AC4 0000,0000 > Clever. I'll assume QSAM cheerfully deals with whatever BLKSIZE SDB selects. Is RECEIVE equally happy with it? But doesn't it still corrupt RECFM or LRECL of an existing data set? Is the performance gain significant with modern DASD? I'd care more for preserving RECFM and LRECL, even at the cost of TRANSMIT's failing. -- gil ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
