Either way, the user has to reboot. With UPM, however, QNX stops these faults from occurring. The OS can automatically restart any process that attempts to corrupt memory and thus restore full service. No reboot is required. As it turns out, the NCT will function even if the network server goes down.
Users can, for example, continue to send email and access the web.
Better yet, the network administrator doesn't have to reboot every user's terminal once the server comes back online. This efficiency is partially due to QNX's UPM architecture, and to QNX's small footprint, which allows us to store a complete OS and various applications right on the NCT itself. We estimate that, by using QNX, our design team cut the development schedule by over 30 percent. First, QNX provided most of the core functionality we required. It also included source and object code that enabled our engineers to develop a unique protocol for attaching the NCT to 3270 coax cabling.