Terminal Emulator or Network: A Management Guide

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

Brief: The number of PCs connected to AS/400s has increased dramatically in recent years. At the same time, the equations that govern whether to use a Lan solution or a terminal emulation solution have also been changing. This article guides you through an analysis of why (or even if) PCs should be attached to your AS/400. The results will help you to determine which attachment method to use.

One of the most difficult choices for MIS managers who have PCs to attach to their AS/400 is deciding between a terminal emulation card solution or a local area network (LAN)-based one. This problem can be difficult to resolve due to its rather fuzzy nature. What are the strengths of a LAN? What about the costs associated with them? Does a definition of terminal emulation include PC Support? Which solution offers the most flexibility? ...the least cost? ...the most performance? In this article, I'll sort out these issues for you and give you grounds from which to make a rational, informed decision.

Defining the Problem

The point of this exercise is deceptively simple. You have numerous PCs in- house and have decided (or your user community has decided) that the PCs need to talk to your AS/400. Your first pass at the problem has yielded the following choices:

1. You can put terminal emulation cards in every PC, thereby allowing them to talk to the AS/400.

2. You can install a LAN, hook all the PCs into it and then attach that to the AS/400.

Which choice is for you? In order to determine the answer, we have to start with the basic issue of why your PCs need to connect to the AS/400! Many times I've had clients so caught up in the technology of the question that they've lost sight of the most important point of the whole issue: Why?

That question should bring to light the business reasons for connecting the PCs to the AS/400 in the first place. Connecting PCs to the AS/400 (or to each other, for that matter) for the sake of connection alone is dumb. Without a good, solid business reason, the PCs should be left alone.

Numerous articles deal with the technical side of corporate networking (see "Networking in the Corporate Climate," MC, June 1992); and while the technical issues are important, my contention is that they're pointless without sound business reasons behind them.

The following list of issues comprises 80 percent of the business requirements for connecting a PC to an AS/400:

o Common terminal access

o File transfer capabilities

o Resource sharing

o Electronic mail (E-mail)

Let's look at each of these in turn.

Common Terminal Access

Common terminal access can be defined as the ability to reach any application from any terminal. For example, many users want access to the AS/400 from their PCs to eliminate having both a PC and an AS/400 terminal on their desk. But an important issue presents itself at this point. Why a PC in the first place? If the reason you're connecting to your AS/400 is merely to create a common terminal access-a connection to the AS/400 with no PC tasks required at that location-stay with a terminal. The only reason to enter this emulator/LAN debate is if business needs require the PC.

If the situation does call for PCs, both terminal emulation cards and LANs can eliminate the clutter of devices on your desktop with ease. Terminal emulation cards make the AS/400 terminal unnecessary by allowing a PC to emulate an IBM terminal. LANs give your PC the functionality of an AS/400 terminal in one of two ways. In one method, the LAN routes requests for attachment to the AS/400 to a PC server containing software such as Novell's NetWare for SAA, which handles the LAN-to-AS/400 connection. In the second method, employed by traditional AS/400 LANs, the AS/400 acts as the server and contains the required token-ring or Ethernet protocol. The mechanisms are different, but the results are basically the same.

So, from the "I just need my PC to talk to the AS/400" perspective, the contest between the LAN and the terminal emulation card is basically a draw. Speed is probably the main difference. Normally, LAN protocols run at higher speeds (4-16Mbps) than standard AS/400 workstations support (around 1.2Mbps). The extent to which this affects response time depends on many factors, but if throughput is an important factor, LANs are generally more effective than terminal emulation. I'd caution you that speed for the sake of speed is not a sufficient business reason for selecting the LAN approach.

Other positive "side effects" of implementing common terminal access include centralizing E-mail, standardizing terminal types and configurations and eliminating duplicate communications links necessary for two tubes on one desk. These are the benefits which give weight to common terminal access as a legitimate business reason for entering the emulation/LAN debate.

File Transfer

File transfer issues in the midrange world are as old as the hills and five times as dusty. We've used everything from card decks (S/3) to diskettes (S/32, S/34 and S/36) to PC Support (S/36, S/38 and AS/400). Also on the scene are 2780 and 3780 RJE emulated card decks, and let's not forget magnetic tape and CD-ROM. Finally, we've all occasionally resorted to "Oh, the heck with it. Just rekey it on the other machine!"

Until recently, terminal emulation and file transfer were not the best of friends. The marketplace historically had a limited number of offerings, PC Support being chief among them. But nowadays, all vendors seem to have some sort of file transfer capability attached to their emulation card offerings. Some, of course, are better than others, but the net result is that most PCs with emulation cards can now transfer files with ease to the AS/400 and vice- versa.

Vendors normally add file transfer capabilities on to emulators-not quite as an afterthought, but let's face it...the main purpose of an emulator is to emulate, not to pass data. LANs were designed the other way around. LANs came into being, in large measure, for the express purpose of transferring data. It's one of the things they do best. In my opinion, LANs have an edge over terminal emulators in that their very design optimizes them for the transmission of data. This is one of the key distinctions between emulators and LANs.

Since the main purpose of LANs is the transfer of data, a LAN is not a good idea if file transfer is a rare occurrence at your installation. But if the "why" we discussed earlier contains the constant or repetitious transfer of data between users and the AS/400, LANs might be the answer.

Resource Sharing

The AS/400 can, in many cases, act as a server in the traditional client/server sense to hold data available to PCs. In this sense, the AS/400 be-comes a kind of library from which PC users check out data so that they can generate their own reports with PC-oriented software.

Certain types of LANs can use the AS/400 as a file server. With this type of setup, you wouldn't need to buy a separate file server; but the LAN is then forced into either a token-ring or Ethernet solution.

Connecting to the AS/400 means sharing physical resources, too. The data-rich nature of the midrange system practically ensures a regular backup regimen for data that might otherwise be stored on PCs with less rigorous backup procedures. Tapping into the AS/400's DASD supply may also minimize your PC hard disk requirements (at a higher cost, mind you). And finally, although PC printers generally offer more sophistication, AS/400 printers (which can be accessed through LANs or emulation) often provide the printing speeds a PC user might need to output an extremely long report.

As you take stock of resource-sharing issues, you may encounter other arguments masquerading as good business reasons for hooking up PCs to your AS/400. Related arguments frequently used to justify PC-to-AS/400 connections are actually pure PC issues-no AS/400 issues are involved at all. Recognize these and remove them from the equation. They may justify a LAN, but they do not warrant a LAN-vs.-emulation debate because access to the AS/400 is no longer the focus-the AS/400 is simply the means to some other end. These issues fall into two broad categories-access to PC software and sharing of DASD and peripherals.

It's tough to validate an intent to share PC-oriented software as a reason to connect all of your PCs to the AS/400. A LAN or file server will allow users to share PC software across many locations. By the same token, any file server can reduce your PC hard disk requirements by acting as a DASD resource. It's not mandatory to involve the AS/400 in any of this, and your midrange system's performance may suffer if you do.

Another common argument I've heard for using a LAN is the sharing of PC printers. This practice is commonplace even though there are other means to address this issue, such as A/B switches. In reality, printer sharing is a thinly veiled version of file sharing. In many cases, the file to be printed at a shared printer is not in the native form that the printer can deal with. It may be an EBCDIC file from an AS/400 which needs to be printed on an ASCII printer. In addition to the printing of the file, the LAN or AS/400 must translate it properly for printing.

Terminal emulators and LANs can both accomplish these tasks. Terminal emulators do it by virtue of "attached" printers or by means of transferring a file from the PC to the AS/400, which in turn routes it through the async controller to an ASCII printer, and so on. LANs handle printer sharing as a matter of course, usually by means of one or more print servers which direct the output from the LAN node to the requested printer.


One of the fastest growing areas in business data communications today, E-mail should be thought of as much more than just message passing. These days, E-mail often includes appointment scheduling, to-do lists, calendars, company bulletin boards and more.

The AS/400's strong suit is not E-mail. I will admit that IBM's solution to E- mail, OfficeVision/400, is a worthy effort. But compared to some of the E-mail products available for LANs, OfficeVision/400 is about two bricks shy of a load.

LAN E-mail offerings are robust, effective and, generally speaking, network- effective. OfficeVision/400 accessed by a terminal emulation card fails on two of the three points just mentioned.

First, OfficeVision/400-actually, all AS/400-based E-mail packages-have a nasty habit of bogging down the AS/400. They are processor hogs. These packages currently are, in my opinion, examples of software better suited to LANs and not well-suited for the AS/400. Secondly, AS/400 E-mail products like Office Vision/400 pale in comparison to the robust nature and built-in flexibility of LAN E-mail packages.

In this arena, terminal emulators take a back seat to LANs. E-mail should not be the deciding factor in the emulator-vs.-LAN question, though. It's important, but does not qualify as a sole reason why a LAN should be installed over a terminal emulator solution. If E-mail is the only "why" in your installation, then take the OfficeVision/400 (or equivalent) route. It seems hard to imagine that the issues of file transfer, resource sharing and common terminal access won't appear in your list of business reasons; but if they don't, and if E-mail is all that's left, skip the LAN.

The Plot Thickens: Costs

It may appear that LANs have really pulled ahead of terminal emulation in this footrace, but don't call your LAN supplier yet! One area where terminal emulators gain ground is cost.

At first glance, it would seem like no one would ever buy a terminal emulator. Terminal emulation boards are routinely available for between $150 and $700, depending on desired features and options. Under normal conditions, the after- purchase terminal emulator costs from year to year are minimal. There really isn't much to spend money on!

While LAN Network Interface Cards (NICs) are comparatively cheaper-depending on the protocol requirements of your LAN, you can obtain a LAN NIC for around $125-keep in mind that a LAN is not just NIC cards. That's the trap-there may be additional startup costs such as an Ethernet or token-ring card for the AS/400, a Multiple Access Unit (MAU) or network management software. In addition, there will always be ongoing support costs associated with a LAN.

A recent survey of Fortune 1000 companies conducted by Forrester Research reveals that the cost to support a LAN user runs around $1,270 per user, per year! LAN administration accounts for 59 percent of that amount; physical LAN support accounts for 22 percent; bridge and router support, 9 percent; Help desk costs, 8 percent; and dial-in support, 2 percent.

Let's Wrap It Up

At this point, it should be clear that a number of issues must be considered before implementing either a terminal emulation solution or a LAN. We've reviewed the basic decision gates such as common terminal access (the race between LANs and terminal emulators is a push), resource sharing (LANs take this one), file transfer (again, LANs by a clear margin) and, finally, E-mail (LANs for the win).

The big issue is cost.

Any LAN is expensive. The hidden costs of supporting the LAN makes a persuasive case for terminal emulators. And if you're wondering by now whether there's a clear-cut answer to which way you should go on this issue (even with costs aside), the answer is no. Every networking and communications issue is fraught with "ifs." But knowing where to start (with the "whys"), what the main criteria for evaluation should be (the four points we discussed) and the costs (both apparent and hidden) should make the process easier for you.

Kris Neely is the connectivity editor at Midrange Computing.



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.


  • Progressive Web Apps: Create a Universal Experience Across All Devices

    LANSAProgressive Web Apps allow you to reach anyone, anywhere, and on any device with a single unified codebase. This means that your applications—regardless of browser, device, or platform—instantly become more reliable and consistent. They are the present and future of application development, and more and more businesses are catching on.
    Download this whitepaper and learn:

    • How PWAs support fast application development and streamline DevOps
    • How to give your business a competitive edge using PWAs
    • What makes progressive web apps so versatile, both online and offline



  • 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



  • Node Webinar Series Pt. 1: The World of Node.js on IBM i

    SB Profound WC GenericHave 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.
    Part 1 will teach you what Node.js is, why it's a great option for IBM i shops, and how to take advantage of the ecosystem surrounding Node.
    In addition to background information, our Director of Product Development Scott Klement will demonstrate applications that take advantage of the Node Package Manager (npm).
    Watch Now.

  • 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.