Re: TSO XMIT BLKSIZE

From: IBM Mainframe Discussion List [IBM-MAIN@LISTSERV.UA.EDU] on behalf of Paul Gilmartin [042bfe9c879d-dmarc-requ...@listserv.ua.edu] Sent: Tuesday, October 25, 2022 12:46 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: TSO XMIT BLKSIZE On Tue, 25 Oct 2022 11:20:03 -0500

Re: TSO XMIT BLKSIZE

On Tue, 25 Oct 2022 12:53:15 -0400, Tony Harminc wrote: >On Tue, 25 Oct 2022 at 12:37, Paul Gorlinsky wrote: >> >> The DSN has to be a SEQuential dataset. XMIT with reallocate it to >> FB/80/3120 ... >> If it is a PDS, XMIT complains that it is not a sequential DSN... > >But for this purpose a

Re: TSO XMIT BLKSIZE

On Tue, 25 Oct 2022 12:19:53 -0500, Paul Gorlinsky wrote: >... >alloc DA(temp.xmit.pds(RRR)) FILE(OUTDD) SHR >xmit (.xxx) DSNAME(V101.brf000.RRR) outFILE(OUTDD) > >HOWEVER, is all cases using the OUTFILE the dsn (PDS/PDSE/SEQ) got modified to >FB/80/3120 even if

Re: TSO XMIT BLKSIZE

Classification: Confidential There is a common usermod for this. Check the CBTTAPE HTH, -Original Message- From: IBM Mainframe Discussion List On Behalf Of Steve Thompson Sent: Tuesday, October 25, 2022 7:49 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: TSO XMIT BLKSIZE [CAUTION

Re: TSO XMIT BLKSIZE

To your original question: The help text has an interesting statement: Referring to OUTDSNAME and OUTDDNAME as the keyword "This keyword is intended to be used in conjunction with the Interactive Data Transmission Facility RECEIVE command INDATASET/INDSNAME/

Re: TSO XMIT BLKSIZE

And if you had been truly following this thread, there appears to be only ONE correction made ... the 1/2 track comment of mine ... Chill!! -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to

Re: TSO XMIT BLKSIZE

On Tue, 25 Oct 2022 12:59:20 -0400, Al Loeffler wrote: >Here's a USERMOD to set the block size to 0 for z/OS 2.5. I have a USERMOD for >each release going back to 1.11. > That seems dangerous. A future release might change the offsets (which "++VER" will probably detedt.) And it's likely to

Re: TSO XMIT BLKSIZE

On a z/OS 2.5 system, the results stand ... Note: NOT SMS managed A PDS or PDSE blocked either FB/80/3120 or other failed with with same message ... With or without the target member and the dataset pre allocated INMX209I TRANSMIT command terminated. Output dataset '.TEMP.XMIT.PDS'

Re: TSO XMIT BLKSIZE

On Tue, 25 Oct 2022 11:54:10 -0500, Paul Gorlinsky wrote: >Is this not a threaded conversation that is being held ... > Yes, but there were at least three previous contributors (a fourth has just joined) and multiple previous plies. "You're correct" doesn't clarify. I loathe contributors'

Re: TSO XMIT BLKSIZE

Here's a USERMOD to set the block size to 0 for z/OS 2.5. I have a USERMOD for each release going back to 1.11. ++USERMOD(XTEMXMI) /* Transmit OUTDA() forces the BLKSIZE of

Re: TSO XMIT BLKSIZE

On Tue, 25 Oct 2022 11:37:18 -0500, Paul Gorlinsky wrote: >... >The DSN has to be a SEQuential dataset. XMIT with reallocate it to FB/80/3120 >... >If it is a PDS, XMIT complains that it is not a sequential DSN... > But :

Re: TSO XMIT BLKSIZE

Is this not a threaded conversation that is being held ... -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: TSO XMIT BLKSIZE

On Tue, 25 Oct 2022 at 12:37, Paul Gorlinsky wrote: > Funny Results: > > The DSN has to be a SEQuential dataset. XMIT with reallocate it to > FB/80/3120 ... > If it is a PDS, XMIT complains that it is not a sequential DSN... > But for this purpose a PDS *member* is treated as a sequential

Re: TSO XMIT BLKSIZE

OMG - You're in this case was Mr. Metz... -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: TSO XMIT BLKSIZE

On Tue, 25 Oct 2022 11:20:03 -0500, Paul Gorlinsky wrote: >You're correct, I mangled a best practice with functional capability. > Too terse. Pleas provide an attribution: Who is the "You" in "You're correct"? And/or some context: What are they correct about? That might make the

Re: TSO XMIT BLKSIZE

I have heard that PDSEs are built on linear VSAM dsn functionality.. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: TSO XMIT BLKSIZE

Funny Results: The DSN has to be a SEQuential dataset. XMIT with reallocate it to FB/80/3120 ... If it is a PDS, XMIT complains that it is not a sequential DSN... So, Either XMIT to a temp file, then copy to a PDS/DSN with a larger block size or apply the ZAP like Lionel suggested... I did

Re: TSO XMIT BLKSIZE

You're correct, I mangled a best practice with functional capability. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: TSO XMIT BLKSIZE

On Tue, 25 Oct 2022 11:06:14 -0500, Paul Gorlinsky wrote: >Previous posts identified the issue for you... If you let the XMIT/TRANSMIT >program allocate the file, it defaults to 3120; however, if you preallocate >the dataset, FB/80/0 it will keep those attributes. > That seems to be

Re: TSO XMIT BLKSIZE

/~smetz3 From: IBM Mainframe Discussion List [IBM-MAIN@LISTSERV.UA.EDU] on behalf of Paul Gorlinsky [p...@atsmigrations.com] Sent: Tuesday, October 25, 2022 9:23 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: TSO XMIT BLKSIZE Like so many of the things IBM does

Re: TSO XMIT BLKSIZE

Previous posts identified the issue for you... If you let the XMIT/TRANSMIT program allocate the file, it defaults to 3120; however, if you preallocate the dataset, FB/80/0 it will keep those attributes. The RECEIVE program will work regardless of the BLKSIZE provided it is has an LRECL of 80

Re: TSO XMIT BLKSIZE

On Tue, 25 Oct 2022 08:49:03 -0400, Steve Thompson wrote: > >I know that I can't override it as a user. I've tried in using a >data set to hold the data (via OUTFILE(ddn) ), but it gets forced >to the above. > Pre-allocate a PDS with BLKSIZE=0. Create a member with 50 records. Allocate a

Re: TSO XMIT BLKSIZE

On Tue, 25 Oct 2022 08:23:53 -0500, Paul Gorlinsky wrote: >Like so many of the things IBM does, it is a left over from when we had >several different DASD types going all the way back to OS/MVT/MFT days... 3120 >was optimum for any... > How about an RFE or even an SR to allow SDB to operate?

Re: TSO XMIT BLKSIZE

Like so many of the things IBM does, it is a left over from when we had several different DASD types going all the way back to OS/MVT/MFT days... 3120 was optimum for any... But today, for the most part, BLKSIZE=0 is OK and the OS will calculate the proper size for the device you are writing

TSO XMIT BLKSIZE

I have a question on this: The doc says that the DCB attributes used by Transmit is BLKSIZE=3120, LRECL=80 and RECFM=FB. Is this somehow tied to JES2|3 and can't be increased? I know that I can't override it as a user. I've tried in using a data set to hold the data (via OUTFILE(ddn) ), but