When IBM announced System/360 back in 1964 with 24-bit addressing, people said
"who will ever need 2**24 = 16M bytes?"
The 640K limit was CHOSEN by IBM to avoid their PCs threatening their
mainframes. IBM had a choice between Intel 8086 (20-bit = 1M addressing) and
Motorola 68000 (architected 3
On 2016-04-22, at 09:38, Gregg wrote:
> Back in Yore, who ever thought we'd need more than 640K or 8M?
>
That's why there's BROWSE MODULE, both in CMS and an analogue in
MVS, which doesn't load the file into main storage as XEDIT does.
https://what-if.xkcd.com/63/
https://what-if.xkcd.com
On 2016-04-22, at 02:10, John P. Hartmann wrote:
> Under the bonnet, XEDIT support for BFS are pipelines to load and write the
> file into the existing
>
So close! If only similar hooks could be used with an arbitrary pipeline as
input!
What does it use as FN FT FM? Or has XEDIT itself been
Back in Yore, who ever thought we'd need more than 640K or 8M?
On Fri, Apr 22, 2016 at 10:46 AM, Paul Gilmartin
wrote:
> On 2016-04-21, at 19:38, Glenn Knickerbocker wrote:
>
> > On 4/19/2016 11:09 AM, Paul Gilmartin wrote:
> Trust No 1 V 255 Trunc=255 Size=0 Line=1 Col=1 Alt=0
>
>
On 2016-04-21, at 19:38, Glenn Knickerbocker wrote:
> On 4/19/2016 11:09 AM, Paul Gilmartin wrote:
Trust No 1 V 255 Trunc=255 Size=0 Line=1 Col=1 Alt=0
>> Still an unfortunate choice. For BFS, the Width and Trunc default
>> should be, "Doesn't matter", or "As much as you like".
>
> T
Under the bonnet, XEDIT support for BFS are pipelines to load and write
the file into the existing structure. If you want a width larger than
the default, you must specify so at the initial XEDIT command. Also
note that the ring can contain a mix of BFS and normal files.
On 04/22/2016 03:38
