What a wonderful Christmas present!
I worked for IBM for 25 years (from '88-'13). I worked in Burlington, VT in the chip design area. It's likely the IBM chips you see in this would have been made in East Fishkill, NY, which handled the bipolar chips used by the IBM Server group, whereas Burlington handled CMOS chips, more commonly used in IBM's consumer and low-end products like the PC division, at least until the mid 90's when Fishkill eventually switched over to CMOS. Unfortunately I have no information on the PCB layout style, but my best guess is that it did enable very early design automation. IBM has an extremely proud EDA (Electronic Design Automation) heritage going well back before I joined (hey, when you have giant mainframes at your disposal to use, you might as well use them!)
Well before commercial EDA tools were available, IBM had an in-house EDA group (this was the group I worked in most of my career) that wrote their own schematic entry and synthesis systems, logic simulators, transistor-level simulators, test pattern generation tools, static timing analysis, chip place and route, you name it. And this was LONG before any of the 3rd party tool vendors existed. And like Alien posted, at least prior to the late 80's, these all ran on mainframes accessible via terminals with very limited graphics capability. Everything was driven by esoteric text files with a zillion three letter acronyms in addition to ALD. This was all for chip design, but I suspect the board designers had similar technology. When you are limited to designing on a more or less text-based display using very primitive (by today's standards) layout and routing tools, it's no wonder you'd wind up with that grid-based board design technique.
My first job at IBM was working on one of the first truly graphical EDA environments (at least for chip design). It still ran on the mainframe and was originally written in Pascal, but it did use a 5080 graphics terminal. A few years later we ported it to the RS/6000 UNIX environment. This was a little after other EDA vendors were starting to have legitimate offerings on Sun, Apollo and HP machines, so we were somewhat behind the times, but most of the IBM design community was still running on mainframes.
The IBM EDA group continues to this day and certainly has its niche areas of expertise. Cadence's Encounter Test tool is based on an IBM test tool and still has "hidden" IBM environment variables that are used for certain IBM proprietary uses (nothing outrageous, just turns on certain output formats used by custom IBM chip test equipment), and IBM's static timer is state of the art, albeit not really industry compatible (IBM's solution is the "Beta" to the industry's "VHS"). But once IBM sold its chip manufacturing business to GlobalFoundries in 2015, I wonder if the EDA group is sustainable.
One last comment to add: at 5:56 IPL = Initial Program Load (what we would call a "boot" today).