1985-1988 TSI: GrandAd: The System/36 Conversion

TSI’s first big conversion. Continue reading

A fairly detailed description of the design of the GrandAd System can be found here. More information about IBM’s System/36 (S/36) is posted here.

The purchase of the GrandAd software system in early 1985 by Keiler Advertising (KA) was definitely a milestone for TSI. The agency was one of the two largest in the Hartford area, and its founder and president, Dick Keiler1, was highly respected in the local advertising community.

Although I had recommended to Sandy Procko3, KA’s finance manager and our liaison on the installation, that they buy two Datamasters and a hard drive, IBM had talked her into ordering the recently announced S/36 model 5362. They made the right decision.2 The Datamaster was on its way out, and the S/36 gave them better peripherals and room for growth. It also had many more subtle advantages.

Her decision was a great break for us. We would have needed to convert the system anyway. The sooner that we got started on it the better.

The only problem was that no one at TSI had ever worked on a System/36. We knew that the system had a BASIC interpreter, but we were uncertain about the compatibility of the two versions. IBM provided KA with a huge stack of documentation. I read the BASIC manual thoroughly and was relieved to find that it was very similar to what we were accustomed to. I read enough of the other manuals to get an idea about how to set up their system.

I also had to write the file definitions for each file. We had versions of these created in the Datamaster’s word processing program, but on the S/36 it was important that they be stored as Data Definition Specifications (DDS). The final preliminary step was to write a procedure for creating all of the empty data files from the DDS.

IBM’s office had a 5360, the “washer-dryer” model.

IBM allowed us to work on the S/36 in its downtown Hartford office before KA’s system was delivered. I saved our programs onto 8″ disks. I created a library for them on IBM’s 5360. Then I restored them as text files. I edited them to conform with the S/36 syntax and changed the names of all of the files to use the dot format that SSP required. I then tried to load them in the interpreter. If any lines were rejected, I fixed them and kept trying until the program loaded. Then I went on to the next program, of which there were several hundred.

When I was done with the programs and procedures, I saved the library onto diskettes, brought the diskettes to KA, and restored them. Then I executed the procedures to create all of the files. It never occurred to us that there might some day be a way of populating the data files from files that they had stored on their PC’s. I think that it was possible to save the specs table, which was a fixed-record-length file.

For nearly all of its forty-two years of its existence KA was located in a large house in Farmington, CT. It is portrayed in the photo at the right. During the period in which I was regularly vising the agency, the trees and the bushes were much smaller, and they were surrounded by wood chips. Sandy called Dick “the mulch king” of Farmington.

From the beginning, or shortly thereafter, Sandy was assisted by a younger woman named Shelly. I don’t remember her last name

Getting the code to work on the S/36 caused us fewer problems than one might imagine. By this time we understood how IBM thought about things. The fact that all of our programs followed strict procedures also made it easier to adjust to the differences. I don’t remember encountering any problems that necessitated consulting IBM or anyone else.

Here are my most vivid recollections of the installation.

KA’s 5224 printer was much faster than anything available on a Datamaster.
  • KA not only had a kitchen. It had a chef who prepared meals for clients and prospects and a dining room as well. I was never invited to one of these occasions.
  • The parking lot at KA, which was in the back of the house, had a few narrow grass covered areas with skinny trees in them. I parked my Celica to the left of one of them once. When I exited I turned the wheel too soon. The mirror on the right side of the car got caught on the tree and broke off. Thenceforward there was no mirror on the Celica’s right side. Changing lanes to the right required extreme caution.
  • The first few monthly closings at KA were, as always, difficult. Query/36 sometimes helped the reconciliation process. Nevertheless, on one occasion we had a discrepancy of ten cents in the accounts payable account. Sandy told me not to worry about it, but we had the tools to find it, and so I persisted. I eventually discovered that no vendor was off by a dime. Instead, three invoices were off; all three had discrepancies of more than $100, but they almost perfectly balanced one another.
  • Sandy taught me that if a discrepancy was divisible by nine, it was probably a transposition error.
  • On one occasion guys from the Australian national swimming team were in the office for some reason. Sandy and most of the other female staff members thought that they were very hot.
  • Sandy liked the system’s reports a lot. I am pretty sure that she asked for a couple of revisions, but I do not remember the details. I do remember that, despite the fact that we spent a lot of time making sure that the results of the cost accounting system agreed with the cost accounting system, she never showed any client profitability reports to Dick. She said that that would open a can of worms.
  • I went to KA once during the period in which I was weak from cat scratch fever (as described here). It happened to be on the day that KA was moving its accounting department from the ground floor to the second floor. I carried a printer or something, but the effort totally exhausted me.
  • At some point in 1988, I think, Sandy fell out of Dick’s favor. She was reassigned to take charge of the scheduling of production jobs, a clear demotion. I never learned why all of this happened.
  • Dick hired a woman with experience from a New York agency to replace Sandy. I tried to explain to her why the system’s method of calculating work in process (WIP) was superior to the method advocated by the AAAA, but I don’t think that she bought it.
  • The last time that I went to KA Shelly was in charge of the finance department, and the New Yorker was gone. On that occasion Michael Symolon, our salesman at the time, accompanied me. Evidently he had gone on a date with Shelly once and was embarrassed about it. He stayed in the background. That was the only time that I ever remember him being shy.

When the system had been working successfully for a few months, Dick Keiler arranged to be interviewed by AdWeek New England about our system. It was a very nice article that heaped praise upon our system. It started on the front page, and it continued for several paragraphs in the middle. I had only one minor quibble: THEY NEVER MENTIONED THE NAME OF THE SOFTWARE OR THE COMPANY THAT DEVELOPED IT!!!

TSI had, for the first and only time in its existence purchased an ad. It appeared somewhat close to the article’s continuation page. However the ad was not precisely the same size as the hole that the magazine needed to fill. The way that they floated it in made it look really unprofessional.

I was quite upset about this. I wrote a letter to the editor complaining about both of these things. He called me. He did not apologize. He said that he did not think that it would have been proper to identify TSI. I reminded him that the article clearly identified the hardware vendor as IBM. What was the difference? He repeated that it just did not seem proper. He also thought that our ad looked fine. I hung up on him.

I made lemonade out of this by writing to all the prospects in the northeast about the article, providing “what AdWeek neglected to mention.” It generated a few inquiries.


1. Dick Keiler founded the agency in 1972. He started his retirement process in 1999 and left the company five years later. In 2021 he lives in Tucson Arizona. The agency went out of business in 2015. The last few years are described here.

2. I am pretty sure that in 2021 Sandy Procko resides in Westbrook, CT.

3. I was slow to come to the realization that when trying to sell systems that generated no revenue for the purchaser, it was best to strike when the iron was hot. One of our clients later told me “Christmas only comes once.” The person recommending the purchase always dreaded making a mistake. He/she most feared the prospect of telling the boss a little later that the company needed to purchase more hardware. I always thought that IBM proposed systems that were bigger and more experience than necessary, but they were more experienced at this process than I was.

4. The S/36 operating system, called SSP, used the term “procedure” for a list of commands that were to be executed sequentially. In addition, BASIC used the same term for a sequential list of BASIC commands that could be executed inside the interpreter. On the Datamaster the user was always in the interpreter, and so there was no confusion.

1983-1988 The IBM System/36

A true multi-user system. Continue reading

A 5360. The box on the top left is the diskette magazine drive.

IBM’s introduction of the System/36 (S/36) in May of 1983 was not a monumental event for TSI. From our perspective the new system seemed more like a marginal upgrade of the System/34, which had always been much too pricey for anyone who would talk to us. The new system had only one basic model, the 5360. The starting price for one of these was still $140,000. It was also gigantic and had special electrical requirements. It was clearly designed for a small data processing department, not a small business without one.

The biggest advantage of the System/36 over any system that we had worked with was that it supported a fairly large number of terminals and printers. This was because it could run a number of jobs at the same time. It also supported batch processing, which meant that time-consuming jobs need not tie up any workstations.

We appreciated these benefits. In fact, we drooled over them. However, no prospective customer of ours ever had a six-figure budget for hardware.

The 5250 screen showed one color, green.

The peripherals were also rather expensive. IBM in those days ignored standards used in the rest of the industry. It set its own standards, and they were all proprietary. So, cheaper hardware from other vendors would not work with IBM systems.

Although the price went down through the years, a 5250 terminal cost around $2,000 when the 5360 was introduced. The cheapest printers, which used dot-matrix technology, were in the $5,000 range.

Both ends of twinax cables were male. A device with two female ends was needed to connect two together

The cabling was also not cheap. The system used twinaxial cables for direct attachment of these devices. Most competing systems used serial or parallel connections. Twinax was decidedly better, but it was also more expensive.

The local devices were connected in a serial fashion to a controller. Up to seven devices could be connected on one twinax line. Each device had two female twinax connections on the back, either in one T-shaped unit or with two short cables. One was called the “gozinda”; the other was the “gozouta”.

The T-shaped connector.

So, if the S/36 had four devices named A, B, C, and D. A would be connected to the controller by a twinax cable, B would be attached to A by a twinax cable, C would be attached to B, and D would be attached to C.

A switch on device A, B, and C needed to be set to allow pass-through to the next device on the line. On device D that switch needed to be set to denote that it was the last device on the line.

For device D to communicate with the S/36, all of the connections must be functional, and all of the switches set correctly. It reminded me of Christmas tree lights in the old days.

The S/36 also came with a serial port. Since a modem could be attached to this device, it would be possible for support people at IBM or the software vendor (or anyone else, for that matter) to sign on from a remote location. This was, of course, our dream; it would make support so much easier. The announcement brought it a little closer to reality.

The 8809 tape drive.

The hard drive capacity varied from 30 MB to 400 MB. In the twenty-first century, of course, those quantities would only hold a handful of photos. However, to most software vendors in the eighties this meant that total storage was no longer a big concern. However, the default backup device was a magazine that held only ten 8″ diskettes. Each diskette had a capacity of only 1MB each. This was a rather obvious limitation on the practical storage.

It was possible to attach an 8809 1/2″ reel-to-reel tape unit to address this. I could not find a price for these monsters. It may well have been the case that if you had to ask the price, you could not afford it.

The System/36 had two processors. The main processor (MSP) executed the code; the control processor (CSP) managed the work for the main processor. The CSP was four times as fast as the MSP, and they worked perfectly in tandem. The S/36 could perform an amazing amount of work at very fast speeds with embarrassingly puny processors. It was also extremely reliable.

Some actions, such as IPL1 and backing up files, needed to be initiated from the system console. The system console on the 5360 was built in to the top of the box. Your system operator needed a wheelchair? Life was rough all over.

I missed out on this fun stuff.

The System/36 supported five programming languages: RPG II2, COBOL, FORTRAN, BASIC, and Assembler. RPG II, a simplistic column-based language, was the most popular. Wikipedia says that this was because it was the least expensive3. The BASIC language was similar to the one used on the Datamaster. I never heard of anyone who programmed in FORTRAN or Assembler on a S/36.

BASIC programs could not be compiled. Therefore, a copy of the BASIC interpreter needed to be loaded into memory for each program that was running. Nevertheless, because the CSP was so efficient, TSI’s benchmarks showed that there was no noticeable difference in the speed of interpreted BASIC programs and compiled RPG II programs performing the same tasks. So, we never considered converting our program to anything besides S/36 BASIC.

IBM also positioned the System/36 with its DisplayWrite/36 software as a word processing server. We found it to be inferior to the Datamaster product in most ways.


The file structure of the S/36 was somewhat different from the Datamaster’s. Programs and other executable items such as BASIC procedures and system procedures were stored in “libraries”. Libraries were somewhat like directories or folders on a PC. However, there was no such thing as a sub-library.

No directory trees on the S/36.

Data files needed to have unique names. They did not reside in libraries. In order to identify which files belonged to which application, the names were preceded by a short identifier and a period. In GrandAd all the media files started with “M.”, and the other files started with “T.”.

The S/36 did not have a relational database4. However, the fields in each file were defined in the system using field names, positions, and length/type designations. These data definition specifications were called DDS. Programs could access files using the same ISAM techniques with which we were already familiar. However, IBM also offered a product named Query/36 that allowed someone who know how the files were named and structured to write queries in a manner that was similar to SQL. These queries could then be saved and executed on demand.

Query/36 was a valuable debugging tool. TSI required all of our clients to buy it.


IBM announced the 5362 in 1984. It was much smaller than the 5360—only about as large as a two-drawer file cabinets. It also had no special electricity requirements. It used the same operating system as the 5360, which was called SSP. It came with one diskette drive and up to 120MB of hard drives. A QIC (1/4″ cartridge) external tape drive was available. A 5250-type terminal plugged into the first twinax spot served as the system console. Fewer devices could be attached, but none of our clients ever reached the limit. Best of all, the starting price was only $20,000, about the same as two Datamasters and a hard drive.

Many advertising agencies in the northeast could afford this level of investment. It took some time for TSI to convert the ad agency programs. I remember spending many days at IBM’s office in Hartford working on this. After tat we needed to change the focus of our marketing efforts to larger ad agencies. At this point IBM had no system to offer to the many whose needs would be satisfied with one Datamaster with diskette drives.

We were happy with this announcement, but it was a disappointment that IBM had totally abandoned the market that had produced the majority of TSI’s sales.


The 5364 (or System/36 PC), which was announced in June of 1985, was IBM’s belated attempt to recapture that market. The starting price of $5,995 was quite attractive. For some reason the system console had to be an IBM PC, XT, or AT with a special card inside. The S/36 part was the same size and shape as an AT. It contained a 5 1/4″ diskette drive that was compatible with neither the attached PC nor any previous model of the S/36. Compatibility was not a high priority for IBM.

This is what the system console looked like with the PC on top of the 5364. Manute Bol found it very convenient.

This bizarre arrangement was very difficult to explain to a prospect. Why would a super-reliable S/36 be coupled to the least reliable hardware ever to wear the IBM logo? It did guarantee that at least one IBM PC was installed at each location, I guess. However, most installations probably did what we did—attach the oldest, slowest machine available as the system console, and then use it only when necessary.

The 5364 had two severe limitations. In the first place, only four devices (counting the system console and the printer) could be attached. So, the S/36 customer could really only attach two more displays or one display and a printer. Still, that would suffice at most small ad agencies and at TSI. We immediately ordered one.

The other limitation was, in some ways, worse. The 5364 came with only 256K of RAM. Each session could use up to 64K. However, batch jobs counted as sessions. If one person started some lengthy reports or other process, the system could possibly reach the point where jobs needed to be swapped between memory and disk. This could severely impair the system’s performance.

The announcement of the 5364 created a good deal of business for a company named Black Box. They sold a box with slots for one 8″ and one 5 1/4″ diskette and software to make image copies from one to another. We bought one, and I used it a lot.


This is a 5363 with both a diskette drive and a QIC tape drive.

In 1987 IBM finally fixed all of the problems, at least the ones that most concerned us. The 5363 was a reasonably priced machine that was suitable for almost any small business. If it had been announced two years earlier instead of the 5364, we could have sold a lot of them.

I could not find anything either on the Internet or in our basement that listed the price of one. I don’t remember that anyone balked at the cost. I also could not discover how much memory it had, but I remember distinctly that it was plenty. It could handle at least seven devices, too, and you could get one with a built-in QIC tape drive.

We enthusiastically ordered one for TSI’s office and tried to get our Datamaster customers excited about it.


By the middle of the eighties most office workers had some kind of personal computer on their desks. They did not want someone to install a terminal next to it as well. But how could they gain access to the S/36 without a terminal? There were no networks worth mentioning in the eighties, and there was nothing like USB. The only way to reach the server was through a twinax line, and IBM did not share its knowledge of how the display and printer connections worked. IBM considered anything that it produced was proprietary.

IBM and many third party companies brought 5250 terminal-emulation packages to market. The idea was to be able transform the PC into a terminal on demand and then change it back. Although the other vendors had to reverse-engineer the 5250 interface, they still were able to produce competitive products that were cheaper and had more features than what IBM offered. They generally consisted of a three pieces:

  1. A hardware card that fit into an expansion slot on the motherboard of the PC. That’s right. You had to take the cover off of the machine and add a card that had the brains needed to make the PC act like a 5250 card. You might also need to physically flip switches on the care to configure it. Then you had put the PC back together again. What could possibly go wrong?
  2. A dongle (sometimes lovingly referred to as a “pigtail”) that screwed into the interface on the part of the card that stuck out the back of the PC. It provided a gozinda and a gozouta for the twinax cable(s).
  3. Software to run on the PC.

When they first appeared, the cost of these packages was well over $1,000, nearly as much or more than a PC or terminal. However, the emulators had one very substantial advantage. The inexpensive printer attached to the PC could also be configured as a S/36 printer. This not only saved money and office space; it was also much more convenient.

For a few years the companies selling these packages did a land-office business.


1. IPL stands for Initial Program Load. It just means the starting process for the system. IBM had three-letter abbreviations of everything, including a three-letter abbreviations (TLA).

2. RPG is short for Report Program Generator. I could never understand why anyone used it.

3. IBM required separate licenses for each programming language that was used.

4. Two IBMers, Donald D. Chamberlin and Raymond F. Boyce, codified the Structured Query Language (SQL) used in relational databases in the seventies. IBM rejected it because the Indexed-Sequential ISAM structure that it used in its computers had much better performance. About three decades later the company changed its mind.