The Network Computing Chess Game: It's Your Move

  • Smaller Small Medium Big Bigger
  • Default Helvetica Segoe Georgia Times

AS/400 IT managers are being presented with a baffling array of network computing architectures designed to lower your Total Cost of Ownership (TCO), increase user efficiency, and provide for future network expansion and capabilities. Affecting this process, a technical and marketing chess game is currently being played out to determine the future architecture of the network computing environment in our IT shops. This match offers us a number of different ways we can network our organizations, and the winners stand to control our networking environment for years to come.

In this article, I examine the network computing chess game and provide some basic information to help you determine your next move. (Make no mistake about it; you are a player.) I look at the concepts behind network computing, the various competing architectures, and some of the issues surrounding these new technologies. While I can’t tell you everything you need to know to redesign your network today, I can give you some basic information to help you evaluate your options.

The Opening: What Is Network Computing?

Start with a simple idea. The ideal networking device—be it a PC, network computer, or other type of device—should satisfy the following criteria:

• It is inexpensive.
• It has a unique identity on the network and the Internet.
• It has complete access to all the information it needs, wherever that information resides, and can quickly present that information through a powerful local user interface.

• It is always connected to the network.
• It has extremely low configuration and maintenance costs for performing its function (a fraction of today’s PC maintenance costs).

• You can change its configuration on the fly from a remote location. In an ideal world, one of these network devices would be on every desktop. Network computing is a very broad term that describes how you provide these functions to client network devices. With network computing, these functions are distributed between your desktop network clients and the centralized servers to which they are connected (via your network or the Internet). The servers provide software and data to the clients on

demand, and the clients have enough processing power to support a powerful user interface. When evaluating network computing, IT managers must think about the network architecture of their information systems, how users access widespread information, and how much it will cost to deploy and maintain these systems. The goal, of course, is the best information access at the lowest cost.

To continue this analysis, it’s also important to explain how network computing is different from a network computer. A network computer is an intelligent device that functions solely as a client to a network computing server. This device is a very simple desktop machine that contains little or no disk storage, a lower-speed processor, and graphics and basic I/O capabilities. It communicates with a larger server that does some (or all) of the processing and sends the results back to the network computer for display or printing. Although you can configure PCs to function as network computers, several vendors offer specific hardware devices that can be classified as network computers. (See “The Nuts and Bolts of Thin-client Hardware” for a review of the current marketplace.)

One problem in trying to create a definition of a network computer is that no one wants to use the term network computer anymore. There are several reasons for this reluctance, but many people believe it took hold because Oracle and Sun unsuccessfully tried to introduce Java-based network computers a few years ago, so now different vendors have different terms for a network computer. You may hear vendors refer to them as thin clients, network or Internet appliances, or a number of other terms. The marketing of these devices is interfering with our understanding, and that hinders the technology’s acceptance. The important point to remember is that network computing is a rapidly changing marketplace struggling to find its vocabulary and default technology.

Further complicating the situation is the fact that at least four competing architectures are attempting to carry the network computing banner. These architectures work with different server systems, including Java-based servers, Microsoft Windows NT Terminal Server Edition, standard Intel PC file servers, and UNIX servers. Contrary to what some marketing people might say, the network computing marketplace is not homogeneous, nor is it predestined to be played out in any one particular way. You need to evaluate your options carefully to find the solution that best fits your current and future networking environment.

The Middle Game: Network Computing Client Types

Before I discuss the different network computing architectures, it is important to understand the types of clients each architecture deals with. There are three different types of network devices that a network computing environment will service. Be aware, however, that the lines between these devices are often blurry, so you may see different definitions coming out of different quarters. For our discussion, let’s define the following client types as the basic architectural building blocks of a network computing environment:

• Fat client. A device in which the operating system and applications reside locally on the hardware. Applications are executed on the client, and data is stored either on the client or on the server. Most traditional PCs are considered fat clients.

• Thin client. A device in which the operating system resides locally on the hardware. Applications are downloaded from a central server and executed on the client hardware, but the resulting data is stored on the central server. Java-based network computers, Net PCs, and managed PCs are thin clients.

• Ultra-thin client. A device with a small operating system that processes only graphical displays. All application processing occurs on a central server, and only the results of that processing are displayed on the client. The data resides on the central server. Windows-based terminal devices are ultra-thin clients.

Each network computing architecture is designed to service one of these clients, and the architecture you select will determine what clients and servers you install.

An Overview of Strategies: Network Computing Architectures

The four basic types of network computing architectures you can install are as follows:

• Java-based network
• Microsoft Windows NT Terminal Server (TSE) network
• Net PC network
• X.11 network for UNIX server Let’s look at each architecture in detail.
• Java-based networks are based on a thin-client model. As shown in Figure 1, this architecture downloads applications from the Java server and executes them locally on a PC with a Java Virtual Machine (JVM) or on a Java-based network computer. For complicated processing, you can run heavy-duty applications directly on a Java server (such as an AS/400 or a UNIX box), and the results can be sent to the client, so this technique offers a little more flexibility than other architectures. All graphical processing is performed on the client, and data is stored on the server. Client applications can be stored in ROM or in flash memory so the client has an “instant-on” desktop that starts from local memory. AS/400 access can be gained from any product or application that reaches the AS/400 through a Web browser or a Java-based AS/400 connectivity package.

• A Microsoft Windows NT Terminal Server Edition (TSE) network (Figure 2) is based on the ultra-thin client model. Here, a Windows NT 4.0 server that has Citrix MetaFrame installed acts as your network computing server. This architecture works with Windows clients and Windows-based terminals, although some other types of clients, such as UNIX workstations, Macintosh desktops, and Java Virtual Machines, can also access your TSE server. Application processing is performed on the server, and the results are sent back to the client. Data is stored on the server. As opposed to the Java-based networks, graphical processing is also performed on the Windows NT server, and only the results are sent back to the client. While this setup allows you to use extremely lightweight client software, server graphical processing can create a capacity problem on your Windows NT server that may force you to install multiple servers and implement load- balancing techniques to handle the demand. For AS/400 access, Client Access for Windows 95/NT or the new Client Access Express for Windows (the Express client) can be run on a Windows TSE for user access.

• A Net PC network (Figure 3) is a thin-client model that is similar to the classic Network Operating System (NOS) model. Applications are downloaded from a central server (such as a Windows NT or Novell NetWare server) and executed locally on the PC. Graphical processing is done at the client desktop, and data is generally stored on the network. A Net PC usually doesn’t contain expansion slots or a local hard drive. (In some cases, however, the Net PC may use a local hard drive for caching purposes but not for application execution.)

Alternatively, you may hear a Net PC referred to as a managed PC, which is basically a normal PC without a floppy disk drive or a CD-ROM. A Net PC network takes advantage of the central server’s user configuration and security features to control access to centrally loaded network software. Since the Net PC doesn’t contain input drives, maintenance and configuration are also controlled from the central server. For Microsoft networks, this maintenance is controlled through Microsoft’s Zero Administration for Windows (ZAW) Initiative. Your clients communicate with your AS/400s by using your usual AS/400 connectivity software.

• An X.11 network for UNIX servers is another ultra-thin-client model for a UNIX environment (Figure 4). In this network, an X.11 server on a UNIX network server serves X applications to PCs with PC X server software installed, X terminals, or network

computers that have built-in X servers. The application processing is performed on the server, while the graphical processing is performed on the client. Data is stored on the server.

In addition, you may run into other products/techniques that are variations on these architectures or expand network computing into different areas (such as GraphOn’s jBridge, which allows Java-based network computers to access newer 32-bit Windows applications on a Windows NT server, or the UNIX-based SCO Tarentella server, which attempts to provide any-client-to-any-server connectivity). As I mentioned before, the network computing arena is large and diverse, containing many different solutions for the same needs.

The End Game: Why Network Computing Hasn’t Taken Off...Yet

With all these perceived benefits—lower TCO, inexpensive hardware, flexibility—you have to wonder why thin-client and ultra-thin-client network computing hasn’t totally taken over the world. The hardware and software are in place. What is everyone waiting for?

The first thing to realize is that the climate for deploying network computing and network computers is different than it was when PCs first became available. At the dawn of the PC age, PCs infiltrated organizations through home users and “rebel” departments that sneaked them in when IT wasn’t looking. The PC was pretty much an unstoppable movement once users realized how these machines could improve their work. Today, however, nobody outside of IT is going to install a network computer, much less a network computing environment. The shift to network computing is very much vendor- management-IT driven, an environment that will slow down its adoption.

Because there is no grassroots movement to install network computing, it requires both corporate planning and approval as well as a change in existing technology to implement. IT managers must realize its benefits, write some checks, and then sell their PC-dependent employees on the concept. It’s a longer process to change an already existing environment that, for the most part, works. Unlike the rise of PCs, there is an entrenched technology (standalone and already-networked PCs) that needs to be reworked to make the move to a fully distributed network computing environment.

Next, there is the Achilles’ heel of network computing: server setup. While vendors sing the praises of how easy it is to set up thin and ultra-thin clients, the reality is that setting up the server end (the computers that run the processing and distribute the applications and data) is much more complicated. When you’re selling ease of configuration on the desktop, setup complexity doesn’t vanish. It merely gets shifted to the network servers. The result is that, as you deploy a network computing environment, it will be a long process to configure the central servers correctly and deploy the first few units. After that, it should be simple to expand the network, but the trick is in getting started, and many people may be put off by the learning curve. Distributed network computing has a fairly high learning startup cost.

This isn’t to say that the network computing shift won’t happen. In 1999, there have already been many high-profile sales of thin and ultra-thin client technology to large organizations, with IBM scoring many of the large thin-client hardware sales. However, personal computer sales also continue to perform well, so there is a mixed message in the marketplace.

Will thin and ultra-thin clients in a network computing environment completely replace today’s fat client PCs? Probably not, but they will take their place next to PCs in the corporate environment as more companies find uses for these types of architectures and network devices that aren’t as “fat” as a PC. Only time will tell who will win this particular chess game, but I recommend that you keep an eye on the network computing marketplace. This technology will continue to grow in the coming years.


Thin-client Model

Network Computer

PC with JVM

The_Network_Computing_Chess_Game-_Its_Your_Move05-02.png 87x93

Java Server

The_Network_Computing_Chess_Game-_Its_Your_Move05-00.png 91x89

• Run applications

• Graphical processing

• Stores data

• Downloads applications

• Runs heavy-duty applications

Figure 1: A thin-client model, the Java-based network mostly downloads applications to a PC or NC for execution.

Ultra-thin-client Model

The_Network_Computing_Chess_Game-_Its_Your_Move05-03.png 91x93

Windows- based Terminals


The_Network_Computing_Chess_Game-_Its_Your_Move05-04.png 87x93


NT with TSE and Citrix MetaFrame

The_Network_Computing_Chess_Game-_Its_Your_Move05-01.png 100x131

Display results

The_Network_Computing_Chess_Game-_Its_Your_Move05-05.png 91x93

• Executes applications

• Performs client graphical processing

• Stores data

Figure 2: A Windows NT Terminal Server network is an ultra-thin-client model that does all the processing for its network clients.

Thin-client Model

Managed PC

Network Operating System

The_Network_Computing_Chess_Game-_Its_Your_Move06-00.png 216x202


Net PC

• Execute applications

• Perform graphical processing

• Downloads applications

• Maintains and configures clients

• Stores data

Figure 3: A Net PC network is another thin-client model that configures and maintains its client Windows desktops.

Ultra-thin-client Model

PC with X-server

Software NC with X-Servers

• Execute applications

• Perform graphical processing

UNIX Server with X.11 Server



Figure 4: In the ultra-thin UNIX X.11 environment, application processing is done on the server, while graphical processing is done on the client.

• Runs applications

• Stores data

The_Network_Computing_Chess_Game-_Its_Your_Move06-01.png 212x235


Support MC Press Online





  • White Paper: Node.js for Enterprise IBM i Modernization

    SB Profound WP 5539

    If your business is thinking about modernizing your legacy IBM i (also known as AS/400 or iSeries) applications, you will want to read this white paper first!

    Download this paper and learn how Node.js can ensure that you:
    - Modernize on-time and budget - no more lengthy, costly, disruptive app rewrites!
    - Retain your IBM i systems of record
    - Find and hire new development talent
    - Integrate new Node.js applications with your existing RPG, Java, .Net, and PHP apps
    - Extend your IBM i capabilties to include Watson API, Cloud, and Internet of Things

    Read Node.js for Enterprise IBM i Modernization Now!


  • Profound Logic Solution Guide

    SB Profound WP 5539More than ever, there is a demand for IT to deliver innovation.
    Your IBM i has been an essential part of your business operations for years. However, your organization may struggle to maintain the current system and implement new projects.
    The thousands of customers we've worked with and surveyed state that expectations regarding the digital footprint and vision of the companyare not aligned with the current IT environment.

    Get your copy of this important guide today!


  • 2022 IBM i Marketplace Survey Results

    Fortra2022 marks the eighth edition of the IBM i Marketplace Survey Results. Each year, Fortra captures data on how businesses use the IBM i platform and the IT and cybersecurity initiatives it supports.

    Over the years, this survey has become a true industry benchmark, revealing to readers the trends that are shaping and driving the market and providing insight into what the future may bring for this technology.

  • Brunswick bowls a perfect 300 with LANSA!

    FortraBrunswick is the leader in bowling products, services, and industry expertise for the development and renovation of new and existing bowling centers and mixed-use recreation facilities across the entertainment industry. However, the lifeblood of Brunswick’s capital equipment business was running on a 15-year-old software application written in Visual Basic 6 (VB6) with a SQL Server back-end. The application was at the end of its life and needed to be replaced.
    With the help of Visual LANSA, they found an easy-to-use, long-term platform that enabled their team to collaborate, innovate, and integrate with existing systems and databases within a single platform.
    Read the case study to learn how they achieved success and increased the speed of development by 30% with Visual LANSA.


  • The Power of Coding in a Low-Code Solution

    LANSAWhen it comes to creating your business applications, there are hundreds of coding platforms and programming languages to choose from. These options range from very complex traditional programming languages to Low-Code platforms where sometimes no traditional coding experience is needed.
    Download our whitepaper, The Power of Writing Code in a Low-Code Solution, and:

    • Discover the benefits of Low-code's quick application creation
    • Understand the differences in model-based and language-based Low-Code platforms
    • Explore the strengths of LANSA's Low-Code Solution to Low-Code’s biggest drawbacks



  • Why Migrate When You Can Modernize?

    LANSABusiness users want new applications now. Market and regulatory pressures require faster application updates and delivery into production. Your IBM i developers may be approaching retirement, and you see no sure way to fill their positions with experienced developers. In addition, you may be caught between maintaining your existing applications and the uncertainty of moving to something new.
    In this white paper, you’ll learn how to think of these issues as opportunities rather than problems. We’ll explore motivations to migrate or modernize, their risks and considerations you should be aware of before embarking on a (migration or modernization) project.
    Lastly, we’ll discuss how modernizing IBM i applications with optimized business workflows, integration with other technologies and new mobile and web user interfaces will enable IT – and the business – to experience time-added value and much more.


  • UPDATED: Developer Kit: Making a Business Case for Modernization and Beyond

    Profound Logic Software, Inc.Having trouble getting management approval for modernization projects? The problem may be you're not speaking enough "business" to them.

    This Developer Kit provides you study-backed data and a ready-to-use business case template to help get your very next development project approved!

  • What to Do When Your AS/400 Talent Retires

    FortraIT managers hoping to find new IBM i talent are discovering that the pool of experienced RPG programmers and operators or administrators is small.

    This guide offers strategies and software suggestions to help you plan IT staffing and resources and smooth the transition after your AS/400 talent retires. Read on to learn:

    • Why IBM i skills depletion is a top concern
    • How leading organizations are coping
    • Where automation will make the biggest impact


  • Node.js on IBM i Webinar Series Pt. 2: Setting Up Your Development Tools

    Profound Logic Software, Inc.Have you been wondering about Node.js? Our free Node.js Webinar Series takes you from total beginner to creating a fully-functional IBM i Node.js business application. In Part 2, Brian May teaches you the different tooling options available for writing code, debugging, and using Git for version control. Attend this webinar to learn:

    • Different tools to develop Node.js applications on IBM i
    • Debugging Node.js
    • The basics of Git and tools to help those new to it
    • Using as a pre-built development environment



  • Expert Tips for IBM i Security: Beyond the Basics

    SB PowerTech WC GenericIn this session, IBM i security expert Robin Tatam provides a quick recap of IBM i security basics and guides you through some advanced cybersecurity techniques that can help you take data protection to the next level. Robin will cover:

    • Reducing the risk posed by special authorities
    • Establishing object-level security
    • Overseeing user actions and data access

    Don't miss this chance to take your knowledge of IBM i security beyond the basics.



  • 5 IBM i Security Quick Wins

    SB PowerTech WC GenericIn today’s threat landscape, upper management is laser-focused on cybersecurity. You need to make progress in securing your systems—and make it fast.
    There’s no shortage of actions you could take, but what tactics will actually deliver the results you need? And how can you find a security strategy that fits your budget and time constraints?
    Join top IBM i security expert Robin Tatam as he outlines the five fastest and most impactful changes you can make to strengthen IBM i security this year.
    Your system didn’t become unsecure overnight and you won’t be able to turn it around overnight either. But quick wins are possible with IBM i security, and Robin Tatam will show you how to achieve them.

  • Security Bulletin: Malware Infection Discovered on IBM i Server!

    SB PowerTech WC GenericMalicious programs can bring entire businesses to their knees—and IBM i shops are not immune. It’s critical to grasp the true impact malware can have on IBM i and the network that connects to it. Attend this webinar to gain a thorough understanding of the relationships between:

    • Viruses, native objects, and the integrated file system (IFS)
    • Power Systems and Windows-based viruses and malware
    • PC-based anti-virus scanning versus native IBM i scanning

    There are a number of ways you can minimize your exposure to viruses. IBM i security expert Sandi Moore explains the facts, including how to ensure you're fully protected and compliant with regulations such as PCI.



  • Encryption on IBM i Simplified

    SB PowerTech WC GenericDB2 Field Procedures (FieldProcs) were introduced in IBM i 7.1 and have greatly simplified encryption, often without requiring any application changes. Now you can quickly encrypt sensitive data on the IBM i including PII, PCI, PHI data in your physical files and tables.
    Watch this webinar to learn how you can quickly implement encryption on the IBM i. During the webinar, security expert Robin Tatam will show you how to:

    • Use Field Procedures to automate encryption and decryption
    • Restrict and mask field level access by user or group
    • Meet compliance requirements with effective key management and audit trails


  • Lessons Learned from IBM i Cyber Attacks

    SB PowerTech WC GenericDespite the many options IBM has provided to protect your systems and data, many organizations still struggle to apply appropriate security controls.
    In this webinar, you'll get insight into how the criminals accessed these systems, the fallout from these attacks, and how the incidents could have been avoided by following security best practices.

    • Learn which security gaps cyber criminals love most
    • Find out how other IBM i organizations have fallen victim
    • Get the details on policies and processes you can implement to protect your organization, even when staff works from home

    You will learn the steps you can take to avoid the mistakes made in these examples, as well as other inadequate and misconfigured settings that put businesses at risk.



  • The Power of Coding in a Low-Code Solution

    SB PowerTech WC GenericWhen it comes to creating your business applications, there are hundreds of coding platforms and programming languages to choose from. These options range from very complex traditional programming languages to Low-Code platforms where sometimes no traditional coding experience is needed.
    Download our whitepaper, The Power of Writing Code in a Low-Code Solution, and:

    • Discover the benefits of Low-code's quick application creation
    • Understand the differences in model-based and language-based Low-Code platforms
    • Explore the strengths of LANSA's Low-Code Solution to Low-Code’s biggest drawbacks



  • The Biggest Mistakes in IBM i Security

    SB Profound WC Generic The Biggest Mistakes in IBM i Security
    Here’s the harsh reality: cybersecurity pros have to get their jobs right every single day, while an attacker only has to succeed once to do incredible damage.
    Whether that’s thousands of exposed records, millions of dollars in fines and legal fees, or diminished share value, it’s easy to judge organizations that fall victim. IBM i enjoys an enviable reputation for security, but no system is impervious to mistakes.
    Join this webinar to learn about the biggest errors made when securing a Power Systems server.
    This knowledge is critical for ensuring integrity of your application data and preventing you from becoming the next Equifax. It’s also essential for complying with all formal regulations, including SOX, PCI, GDPR, and HIPAA
    Watch Now.

  • Comply in 5! Well, actually UNDER 5 minutes!!

    SB CYBRA PPL 5382

    TRY the one package that solves all your document design and printing challenges on all your platforms.

    Produce bar code labels, electronic forms, ad hoc reports, and RFID tags – without programming! MarkMagic is the only document design and print solution that combines report writing, WYSIWYG label and forms design, and conditional printing in one integrated product.

    Request your trial now!

  • Backup and Recovery on IBM i: Your Strategy for the Unexpected

    FortraRobot automates the routine tasks of iSeries backup and recovery, saving you time and money and making the process safer and more reliable. Automate your backups with the Robot Backup and Recovery Solution. Key features include:
    - Simplified backup procedures
    - Easy data encryption
    - Save media management
    - Guided restoration
    - Seamless product integration
    Make sure your data survives when catastrophe hits. Try the Robot Backup and Recovery Solution FREE for 30 days.

  • Manage IBM i Messages by Exception with Robot

    SB HelpSystems SC 5413Managing messages on your IBM i can be more than a full-time job if you have to do it manually. How can you be sure you won’t miss important system events?
    Automate your message center with the Robot Message Management Solution. Key features include:
    - Automated message management
    - Tailored notifications and automatic escalation
    - System-wide control of your IBM i partitions
    - Two-way system notifications from your mobile device
    - Seamless product integration
    Try the Robot Message Management Solution FREE for 30 days.

  • Easiest Way to Save Money? Stop Printing IBM i Reports

    FortraRobot automates report bursting, distribution, bundling, and archiving, and offers secure, selective online report viewing.
    Manage your reports with the Robot Report Management Solution. Key features include:

    - Automated report distribution
    - View online without delay
    - Browser interface to make notes
    - Custom retention capabilities
    - Seamless product integration
    Rerun another report? Never again. Try the Robot Report Management Solution FREE for 30 days.

  • Hassle-Free IBM i Operations around the Clock

    SB HelpSystems SC 5413For over 30 years, Robot has been a leader in systems management for IBM i.
    Manage your job schedule with the Robot Job Scheduling Solution. Key features include:
    - Automated batch, interactive, and cross-platform scheduling
    - Event-driven dependency processing
    - Centralized monitoring and reporting
    - Audit log and ready-to-use reports
    - Seamless product integration
    Scale your software, not your staff. Try the Robot Job Scheduling Solution FREE for 30 days.