On Dec 20, 2011, at 09:10, David Bond wrote: > On Tue, 20 Dec 2011 08:47:00 -0700, Paul Gilmartin wrote: >> Right. If HLASM can do it for EXTRNs, why not for macros. >> If Binder supports a Mixed/UPPER switch, why not HLASM? > > The binder actually supports UNIX files. HLASM uses BPAM. This mess is a > result of z/OS's BPAM support of UNIX files. > I wonder how IBM made POINT work with UNIX files? A more modern assembler design would eschew NOTE/POINT and use multiple DCBs for nested COPYs.
I had a performance APAR where I reported that Binder was orders of magnitude slower writing SYSPRINT to a UNIX file than piping to "cat" writing to a UNIX file. IBM's resolution was to modify Binder to OPEN the SYSPRINT path and use BSAM/QSAM. Apparently Binder had re-invented the flat tire. (In fairness, Binder supported UNIX files before the BSAM/QSAM support was available for such.) (Veering off-topic: when I use the DD: form of local files with FTP, FTP ignores overriding attributes on the DD statement and gets the information elsewhere, often from the DSCB. Again, it fails to employ BSAM/QSAM where I believe it should.) -- gil
