On Monday 04 May 2009 22:07, Patrick O'Keefe wrote: > Is there any way to get TSO XMIT to use a reasonable blksize? > I reblocked an XMIT dataset of a PDS to BLKSIZE=27920 and > TSO RECEIVE had no trouble processing it. I assume that means > there is no technical reason that the blocksize has to be 3120 > (at least for my simple purposes). > > Is there an option that allows XMIT to use the blocksize of a pre- > allocated output dataset? BTW, I'm on z/OS 1.8.
See ZAP, below, which is in ZAPXMIT member of FILE 183 of the CBT tape, also distributed here: http://gsf-soft.com/Freeware/ I applied this ZAP to all of the OS/390 and z/OS systems I installed on my P/390. I have another ZAP job which converts more 3120 values to zero in the XMIT command, but I don't use it. I only use the ZAP below which is very useful, and I don't understand why IBM hasn't fixed this type of situation, particularly because 3120 is an "optimal" BLKSIZE on 3330 drives. Since the late 1980s (DFP 2.3 in XA 2.2, IIRC), OPEN calculates a half-track BLKSIZE when DS1BLKL=0 in the F1-DSCB. -- Gilbert Saint-Flour GSF Software http://gsf-soft.com/ //*--------------------------------------------------------- //* REMOVE BLKSIZE=3120 IN TRANSMIT OUTDS() COMMAND //* REFRESH LLA TO ACTIVATE //*--------------------------------------------------------- //ZAPXMIT EXEC PGM=AMASPZAP //SYSPRINT DD SYSOUT=* //SYSLIB DD DSN=SYS1.LINKLIB,DISP=SHR NAME INMXM VER 19FC 00000C30 HTE7708 REP 19FC 00000000 /* REFRESH LLA TO ACTIVATE NAME INMXM VER 19B4 00000C30 HTE26D2 REP 19B4 00000000 /* REFRESH LLA TO ACTIVATE ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
