Am I glad to see this thread. I ran across http://publibz.boulder.ibm.com/cgi-bin/bookmgr_OS390/BOOKS/dgt2d4a0/3.2.3.1.2?DT=20110606092005#FIGDTMBS Release 13 Figure 87. Optimum and Maximum Block Size Supported Device Type Optimum Maximum | 3490 Emulation (VTS) | 262 144 (256 KB) | 262 144 (256 KB) On Monday of this week.
For some reason(?) I decided to try a SORT FIELDS=COPY on our new Release 12 LPAR with SYNCSORT PARM SDB=LARGE and BLKSZLIM=256K. Seemed to get good results - SORTOUT BLKSIZE of 225000. So, on to a Release 11 LPAR expecting failure. Copied the 225000 tape with a hard coded SORTOUT BLKSIZE=260000 Suprise also worked. WER161B ALTERNATE PARM USED WER276B SYSDIAG= 2835843, 5208295, 5208295, 3742650 WER164B 8,864K BYTES OF VIRTUAL STORAGE AVAILABLE, MAX REQUESTED, WER164B 0 BYTES RESERVE REQUESTED, 7,828K BYTES USED WER146B 32K BYTES OF EMERGENCY SPACE ALLOCATED WER108I SORTIN : RECFM=FB ; LRECL= 5000; BLKSIZE= 225000 WER110I SORTOUT : RECFM=FB ; LRECL= 5000; BLKSIZE= 260000 WER410B 7,836K BYTES OF VIRTUAL STORAGE AVAILABLE ABOVE THE 16MEG LINE, WER410B 0 BYTES RESERVE REQUESTED, 7,720K BYTES USED WER449I SYNCSORT GLOBAL DSM SUBSYSTEM ACTIVE WER416B SORTIN : EXCP'S=9017,UNIT=3490,DEV=586,CHP=9192D1D2A5A6E5E6 WER416B SORTOUT : EXCP'S=9016,UNIT=3490,DEV=512,CHP=9192D1D2A5A6E5E6 WER416B TOTAL OF 18,033 EXCP'S ISSUED FOR COPYING WER054I RCD IN 6464801, OUT 6464801 WER169I RELEASE 1.3 BATCH 0493 TPF LEVEL 1.1 I haven't tried reading into COBOL or writing from COBOL, file compares on the R11 LPAR etc. Nice to have company. I won't feel quite so naked when I hit my Tech Support guys with a request to allow the application folks to start using this. Thank You! David ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
