Detour to Dalton
by Bill Holmes
Apparently word got around that I wanted to leave and I got a call from a manager I barely knew. He was starting up a new department that was going to open and staff processing centers around the state. His offer was that I would help set up and open the first remote center in Dalton, Georgia and then set up, open and manage the second center in Valdosta, Georgia. There was a slight pay raise involved too. It sounded exciting and the fact that I'd soon be about 250 miles from the closest boss was a bonus. Well, it was exciting but starting a new department and opening data centers didn't reduce my workload in fact it increased.
The data centers were to process checks and print reports for smaller banks around the state. The new centers would let us sell our processing services to banks farther away from Atlanta. This was similar to the services we were already providing but in a more distributed and far reaching manner. We were also able to eliminate many of the paper tape transmissions into Atlanta from distant banks. These remote data centers were basically input and output locations. The actual account posting was still done on the big computers in Atlanta. Each center would have a small computer (power, not size), check reader/sorter, card reader and printer.
This initial center was housed in the First National Bank of Dalton about 90 miles north of Atlanta. Dalton had a population of around 20,000 and the county 60,000 at the time. A little smaller than Atlanta. Dalton was and still is the carpet manufacturing capital of the world. FNB Dalton was a fairly big bank because of all the carpet mills. This was going to be a hybrid operation. FNB Atlanta would set up the center, train the personnel, lease the equipment and provide technical support. Kind of like a franchise. Day to day operations would be staffed and run by FNB Dalton people once they got trained and the initial kinks were worked out. I think the two banks had some other business relationships and in fact FNB Atlanta bought the Dalton bank several years later. FNB Dalton had just built a new four story building and they had included a small computer room with raised floor in the design. They also had a freight size elevator so physical planning and equipment installation was relatively easy. Now this computer room was a little unusual. One wall, the biggest, of the room was covered in red/white/black long shag carpet. It actually helped deaden the noise but it was a dust magnet. Processing checks, cards and running a high speed printer generates a lot of paper dust. The janitors had to vacuum the wall every so often. The whole bank building was a showroom for carpeting including what was at the time the largest carpet sculpture in the world. It was on the wall behind the tellers in the two story main banking floor.
The equipment configuration at the remote centers was an IBM 360/20 computer, IBM 1419 MICR reader/sorter, IBM 1403 printer, IBM 2501 card reader and an IBM 029 keypunch. In addition there was a leased data telephone line and a modem that was about the size of a toaster oven.
|GTE Phone prior to data phone mods|
Our computer was an IBM 360/20. This was the smallest and cheapest computer in the 360 family. I think the ones we used had 8K of memory. The biggest 360/20's at the time only had a 16K memory. It was primarily designed to replace some of the old tabulating equipment. We used it to drive the check sorter, printer, card reader and handle the data transmissions. The Model 20 had no typewriter console. The operator communicated with it via dials, buttons and lights. It also had no storage device(s) so when we loaded checks on the sorter they were transmitted real time to Atlanta. The same when we were printing reports sent from Atlanta. That caused problems that I'll document in following chapters.
|IBM 1419 MICR Reader/Sorter|
The IBM 1419 MICR reader/sorter was probably overkill for this installation. It was IBM's premier sorter at the time and processed 1,600 documents per minute (DPM). It had 13 pockets, 0 through 9, A, B and reject, just like a card sorter. It was connected to the 360/20 for program control and data transmission. Like the Burroughs sorters, it could do numerical sorts offline from the computer.
|IBM 2501 Card Reader|
|IBM 1403 Printer|
The IBM 1403 printer was an old but still viable device first used on the 1400 series computers that predated the 360 family. It was a chain printer that ran at 600 lines per minute (LPM). That was fast enough to keep up with the sorter and the transmission speeds.
I'll get into more specifics in the next chapters, but basically we would run the checks and deposits through the sorter and simultaneously transmit the data to the mainframes at FNB Atlanta and print a listing of the transactions. We would balance the run, keypunch the rejects and make any corrections/adjustments. We would then transmit the punched cards to Atlanta. Once everything was in balance we would give Atlanta the OK to post/process the bank. They would do that processing on their schedule. While waiting for that, we would begin to sort the items into account number order. Once the bank's checking accounts were processed, Atlanta would transmit the reports back to our printer. It was all pretty amazing for the times and also rife with problems.
Since this was a new venture for FNB we were on a rather limited budget. This was a little skunk works project by the Data Processing Department, not a big deal like the BankAmericard venture. There were two of us in Dalton on and off to set up the data center and then five days a week for a couple of months once we got started. During the set up we mostly drove back and forth from Atlanta and didn't stay overnight. It was a 90 mile trip one way via Interstate 75, a very good road for the times. We drove a little over the speed limit so it wasn't a long trip. Once we started live processing we needed to be there all the time. The other guy I was working with had relatives in Carbondale, GA, about 10 miles south of Dalton. The relatives worked in a carpet mill. We stayed in their spare bedroom rather than a motel. That wouldn't have been so bad except the spare bedroom had a double bed. They were all nice people but it was not the ideal situation. I much prefer sharing a bed with a female. FNB paid them something for our lodging. We would drive up to Dalton on Monday and stay until Friday night or Saturday morning then drive back to Atlanta. The following Monday we'd do it over again. After the first couple of weeks we did switch off on the Friday late shift so one of us could get back to Atlanta by late evening.
The first couple of weeks after going live were a cluster f#*k. I was the only one who understood the check processing procedures and could balance the runs, the keypunch operator was new to the machine, none of us were familiar with the 360/20, the data line was spotty at best, there were some programming errors that didn't show up during testing, the local IBM guys weren't familiar with the maintenance of all the equipment and the guys in the Atlanta computer room were learning remote processing too. Things happened that we never anticipated. There were a few supplies and pieces of equipment we forgot to include in the initial setup. We managed though and since we started with just one bank we had some slack in the schedule. I can not remember whether the Dalton data center ever processed other banks. I had some technical support dealings with them over the years but since it was staffed by FNB Dalton people I had far less contact with them than the other centers once I left.
Once we got up and running it was mostly a second shift operation. We couldn't get hold of the checks to process before 3:00 or 4:00 PM, later many days, and couldn't finish printing reports much before midnight. There wasn't much to do in Dalton at midnight. I think the town and/or the county was dry except for "private" clubs. Being foreigners we didn't belong to any of those clubs. We'd just find a greasy spoon, have a meal and then go to our luxury accommodations.
I knew this was a short term assignment and I would soon be off to start my own data center. That made the commuting and less than ideal lodging tolerable. I learned a lot which helped me avoid many of the same pitfalls. Of course being very resourceful, I managed to find a whole new batch of pitfalls and problems on my next stop.
That next step was to go back to Atlanta for a few weeks to work on the preliminary planning for the Valdosta center. I went back to Dalton a few times to help out but I didn't stay overnight. I made a couple of trips to Valdosta too during that time.
I'll go into more detail about our remote data centers in subsequent chapters. Pack your bags, we're getting ready to permanently move to the other end of Georgia.