On Aug 26, 2011, at 17:54, John P. Hartmann wrote:
> 64K-1 should feel like a CCW restriction for those who do not know
> data chaining.
>
Duh! Sorry (twice).
> 32K-8 is an OS/360-ism. MVS does not have that restriction.
It persists in RDWs. There may be alternatives, but they're
not widely supported, and perhaps restricted to tape. In:
Title: z/OS V1R12 DFSMS Using Data Sets
Document Number: SC26-7410-10
3.2.3.1.1 Large Block Interface (LBI)
| The large block interface (LBI) lets your program handle much larger
| blocks with BSAM or QSAM. On the current level of the system you can use
| LBI with BSAM, BPAM, and QSAM for any kind of data set except unit record
| or a TSO/E terminal. Currently blocks of more than 32 760 bytes are
| supported only on tape, dummy data sets, and BSAM UNIX files.
On Aug 26, 2011, at 16:30, John P. Hartmann wrote:
> We are speaking LIST3820 and similar beasts. But of course, that
> piece of information was left out of the original query.
>
The original file came from z/OS, where the JES spool makes no
distinction among device types. That decision is deferred until
the file is rendered on a physical UR device. Or perhaps
RSCS made the decision.
SMTP appears to dislike VAFP files. Can't tell why yet.
with a VAFP printer, every null record I issue intending to flush
the printmc buffer appears as a blank tag ('03404040...'x). I
don't know whether that's what upsets SMTP.
Thanks,
gil