PSC 300-Series Wavelink TN Client User's Guide
PSC 300-Series Wavelink TN Client User's Guide
PSC 300-Series Wavelink TN Client User's Guide
Create successful ePaper yourself
Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.
<strong>PSC</strong> <strong>300</strong>-<strong>Series</strong><strong>Wavelink</strong> <strong>TN</strong> <strong>Client</strong> User’s <strong>Guide</strong>WL<strong>TN</strong>-<strong>PSC</strong><strong>300</strong>-20040428-02Revised 4/28/04
iiCopyright © 2004 by <strong>Wavelink</strong> Corporation All rights reserved.<strong>Wavelink</strong> Corporation6985 South Union Park Avenue, Suite 335Midvale, Utah 84047Telephone: (801) 316-9000Fax: (801) 255-9699Email: info@roisys.comWebsite: http:\\www.wavelink.comEmail: sales@wavelink.comNo part of this publication may be reproduced or used in any form, or by any electrical ormechanical means, without permission in writing from <strong>Wavelink</strong> Corporation. This includeselectronic or mechanical means, such as photocopying, recording, or information storage andretrieval systems. The material in this manual is subject to change without notice.The software is provided strictly on an “as is” basis. All software, including firmware, furnishedto the user is on a licensed basis. <strong>Wavelink</strong> grants to the user a non-transferable and nonexclusivelicense to use each software or firmware program delivered hereunder (licensedprogram). Except as noted below, such license may not be assigned, sublicensed, or otherwisetransferred by the user without prior written consent of <strong>Wavelink</strong>. No right to copy a licensedprogram in whole or in part is granted, except as permitted under copyright law. The user shallnot modify, merge, or incorporate any form or portion of a licensed program with other programmaterial, create a derivative work from a licensed program, or use a licensed program in anetwork without written permission from <strong>Wavelink</strong> . The user agrees to maintain <strong>Wavelink</strong>’scopyright notice on the licensed programs delivered hereunder, and to include the same on anyauthorized copies it makes, in whole or in part. The user agrees not to decompile, disassemble,decode, or reverse engineer any licensed program delivered to the user or any portion thereof.<strong>Wavelink</strong> reserves the right to make changes to any software or product to improve reliability,function, or design.The information in this document is bound by the terms of the end user license agreement.
Table of Contents 1Table of ContentsChapter 1: Introduction 1Document Assumptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1Document Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1About the <strong>TN</strong> <strong>Client</strong> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2<strong>Wavelink</strong> <strong>TN</strong> <strong>Client</strong> Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2<strong>Wavelink</strong> <strong>TN</strong> <strong>Client</strong> Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3Host Profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3Emulation Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3Localization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4<strong>Wavelink</strong> <strong>TN</strong> <strong>Client</strong> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4Chapter 2: Installation 5Installation Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5Device Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5Other Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5Installing the <strong>Wavelink</strong> <strong>TN</strong> <strong>Client</strong>. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6Installation Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6Obtaining the Avalanche Software Package . . . . . . . . . . . . . . . . . . . . . 6Installing the Avalanche Software Package . . . . . . . . . . . . . . . . . . . . . 7Configuring the <strong>Wavelink</strong> <strong>TN</strong> <strong>Client</strong> . . . . . . . . . . . . . . . . . . . . . . . . . . . 10Enabling the <strong>Wavelink</strong> <strong>TN</strong> <strong>Client</strong> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13Deploying the <strong>Wavelink</strong> <strong>TN</strong> <strong>Client</strong> . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14Uninstalling the <strong>Wavelink</strong> <strong>TN</strong> <strong>Client</strong> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15Chapter 3: Configuration 19Overview of Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19Configuring Host Profiles. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19About Host Profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20Host Profile Configuration Overview . . . . . . . . . . . . . . . . . . . . . . . . . . 20Accessing Host Profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20Configuring Host Profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22Creating Host Profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23Modifying Host Profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23Removing Host Profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24Host Profile Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24Host Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24IBM Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25VT Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27Autologin Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27Configuration Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28Configuring Emulation Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29About Emulation Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29Accessing the Configuration Manager . . . . . . . . . . . . . . . . . . . . . . . . . 30
2 <strong>PSC</strong> <strong>300</strong>-<strong>Series</strong> <strong>Wavelink</strong> <strong>TN</strong> <strong>Client</strong> User’s <strong>Guide</strong>Accessing the Configuration Manager for Global Settings . . . . 30Accessing the Configuration Manager for Per-Host Settings . . 32Using the Configuration Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33Emulation Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35Modifying Emulation Parameters . . . . . . . . . . . . . . . . . . . . . . . . . 35Using the Find Function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36Configuring Localization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37About Localization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38Configuring Localization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38Downloading Configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40Chapter 4: Using the <strong>Wavelink</strong> <strong>TN</strong> <strong>Client</strong> 41<strong>Client</strong> Licensing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41Standard Licenses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41Demo Licenses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41Manually Configuring Host Profiles. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41Manually Accessing Host Profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42Modifying an Existing Host Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42Configuring a New Host Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44Host Profile Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45Host Profile Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45IBM Host Profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46VT/HP Host Profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46Control Keys . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47Using and Configuring the <strong>TN</strong> <strong>Client</strong> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47Launching the <strong>TN</strong> <strong>Client</strong> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48Connecting to a Host . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48Disconnecting/Terminating a Session . . . . . . . . . . . . . . . . . . . . . . . . . . 49Working with Multiple Telnet Sessions . . . . . . . . . . . . . . . . . . . . . . . . 49Configuring the <strong>TN</strong> <strong>Client</strong> for Multiple Sessions . . . . . . . . . . . . 49Initiating a New Session . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52Switching Between Active Sections . . . . . . . . . . . . . . . . . . . . . . . . 52Appendix A: Managing <strong>Client</strong>s with Avalanche Manager 53Performing Updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53About Updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53Update Media . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54Preparing for Serial Updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54Preparing Avalanche Manager for Serial Updates . . . . . . . . . . . 54Preparing the Mobile Device for Serial Updates . . . . . . . . . . . . . 55Preparing for RF Updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56Performing the Update . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56Using Network Profiles. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57About Network Profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57Creating and Enabling a Network Profile . . . . . . . . . . . . . . . . . . . . . . . 58Deploying a Network Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
Table of Contents 3Using <strong>Client</strong> Controls . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65About Avalanche <strong>Client</strong> Controls . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65Accessing <strong>Client</strong> Controls . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65About Avalanche <strong>Client</strong> Controls . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66Control Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66Properties Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69Editing the Terminal ID of a <strong>Client</strong> . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70Using Software Packages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71Installing Software Packages in Avalanche Manager . . . . . . . . . . . . . 72Deploying Software Packages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79Removing Software Packages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79About Orphan Packages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79Removing an Orphan Package from a <strong>Client</strong> . . . . . . . . . . . . . . . . 79Removing Orphan Packages from All <strong>Client</strong>s . . . . . . . . . . . . . . . 81Appendix B: Keyboard Maps 85<strong>PSC</strong> 325 Keyboard Maps. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85<strong>PSC</strong> 325 Local Terminal Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85<strong>PSC</strong> 325 5250 Emulation Key Sequences . . . . . . . . . . . . . . . . . . . . . . . . 85<strong>PSC</strong> 325 3270 Emulation Key Sequences . . . . . . . . . . . . . . . . . . . . . . . . 86<strong>PSC</strong> 325 VT Emulation Key Sequences . . . . . . . . . . . . . . . . . . . . . . . . . 87<strong>PSC</strong> 325 HP Emulation Key Sequences . . . . . . . . . . . . . . . . . . . . . . . . . 8825-Key <strong>PSC</strong> 335/345 Keyboard Maps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8925-Key <strong>PSC</strong> 335/345 5250 Emulation Key Sequences . . . . . . . . . . . . . . 8925-Key <strong>PSC</strong> 335/345 3270 Emulation Key Sequences . . . . . . . . . . . . . . 8925-Key <strong>PSC</strong> 335/345 VT Emulation Key Sequences . . . . . . . . . . . . . . . 9025-Key <strong>PSC</strong> 335/345 HP Emulation Key Sequences . . . . . . . . . . . . . . . 9038-Key <strong>PSC</strong> 335/345 Keyboard Maps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9138-Key <strong>PSC</strong> 335/345 5250 Emulation Key Sequences . . . . . . . . . . . . . . 9138-Key <strong>PSC</strong> 335/345 3270 Emulation Key Sequences . . . . . . . . . . . . . . 9238-Key <strong>PSC</strong> 335/345 VT Emulation Key Sequences . . . . . . . . . . . . . . . 9238-Key <strong>PSC</strong> 335/345 HP Emulation Key Sequences . . . . . . . . . . . . . . . 9348-Key <strong>PSC</strong> 345 Keyboard Maps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9348-Key <strong>PSC</strong> 345 Local Terminal Functions . . . . . . . . . . . . . . . . . . . . . . 9448-Key <strong>PSC</strong> 345 5250 Emulation Keys . . . . . . . . . . . . . . . . . . . . . . . . . . 9448-Key <strong>PSC</strong> 345 3270 Emulation Key Sequences . . . . . . . . . . . . . . . . . 9548-Key <strong>PSC</strong> 345 VT Emulation Key Sequences . . . . . . . . . . . . . . . . . . 9648-Key <strong>PSC</strong> 345 HP Emulation Key Sequences . . . . . . . . . . . . . . . . . . 97Appendix C: Emulation Parameters 99COM Port Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99Emulation - 5250 and 3270 - 3270 Parameters . . . . . . . . . . . . . . . . . . . . . . . . 105Emulation - 5250 and 3270 - 5250 Parameters . . . . . . . . . . . . . . . . . . . . . . . . 107Emulation - 5250 and 3270 - Common . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108Emulation - Common . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112Emulation - Display. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115
4 <strong>PSC</strong> <strong>300</strong>-<strong>Series</strong> <strong>Wavelink</strong> <strong>TN</strong> <strong>Client</strong> User’s <strong>Guide</strong>Emulation - Keyboard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121Emulation - Printing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123Emulation - Sound . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125Emulation - VT and HP - Common. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127Emulation - VT and HP - HP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130Emulation - VT and HP - VT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131Scanner - Codabar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133Scanner - Code11 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135Scanner - Code128 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137Scanner - Code39 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139Scanner - Code93 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140Scanner - Common . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142Scanner - D2of5 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153Scanner - EAN13 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154Scanner - EAN8 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156Scanner - I2of5 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157Scanner - MSI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159Scanner - UCC128 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161Scanner - UPCA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162Scanner - UPCE0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163Scanner - UPCE1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165Glossary 169Index 177
Chapter 1: Introduction 1Chapter 1:IntroductionThis document provides information about installing, configuring, and usingthe <strong>Wavelink</strong> Telnet <strong>Client</strong> for <strong>PSC</strong> <strong>300</strong>-series mobile devices.This section provides the following information:• Document assumptions• Document conventions• An overview of the <strong>Wavelink</strong> <strong>TN</strong> <strong>Client</strong>Document AssumptionsThis document assumes that the reader has the following:• Familiarity with <strong>PSC</strong> <strong>300</strong>-series DOS-based mobile devices.• Knowledge of wireless networks and wireless networking protocols.• Knowledge of TCP/IP, including IP addressing, subnet masks, routing,BootP/DHCP, WINS, and DNS.• Knowledge of Telnet services and terminal emulation, including IBM5250/3270, HP, and VT100/220.Document ConventionsThe following section contains information about text-formatting conventionsin this manual.
2 <strong>PSC</strong> <strong>300</strong>-<strong>Series</strong> <strong>Wavelink</strong> <strong>TN</strong> <strong>Client</strong> User’s <strong>Guide</strong>Table 1-1 lists the conventions that are used in this manual.Conventioncourier newboldDescriptionAny time you interact directly with text-based user interfaceoptions, such as a button, or type specific information into antext box, such as a file pathname, that option appears in theCourier New text style. This text style is also used forkeys that you press, filenames, directory locations, andstatus information.For example:Press ENTER.Click OK.Any time this document refers to a labelled user interfaceoption, such as descriptions of the choices in a dialog box,that option appears in the Bold text style.Examples:Enable the DHCP checkbox.Access the TelnetCE <strong>Client</strong> Session menu.italicsItalicized text is used to indicate the name of a window ordialog box.For example:The Update Utility dialog box.The Profile Manager dialog box.Table 1-1: Text-Formatting ConventionsIf you have questions about the terminology in this document, see Glossaryon page 169.About the <strong>TN</strong> <strong>Client</strong>This section provides an overview of the <strong>Wavelink</strong> Telnet <strong>Client</strong>.<strong>Wavelink</strong> <strong>TN</strong> <strong>Client</strong> OverviewThe <strong>Wavelink</strong> <strong>TN</strong> <strong>Client</strong> is a DOS-based application that facilitates IBM 5250/3270, VT 100/220, and HP Telnet emulation.Currently, the <strong>Wavelink</strong> <strong>TN</strong> <strong>Client</strong> for <strong>PSC</strong> <strong>300</strong>-series mobile devices is anAvalanche-deployed software package. That is, installing and configuring the<strong>Wavelink</strong> <strong>TN</strong> <strong>Client</strong> on <strong>PSC</strong> <strong>300</strong>-series mobile devices requires Avalanche
Chapter 1: Introduction 3Manager and an Avalanche Enabler. The <strong>Wavelink</strong> <strong>TN</strong> <strong>Client</strong> is first installedand configured on the Avalanche Manager, which is a Microsoft Windowsbasedutility that provides for the remote management of mobile devices. The<strong>Wavelink</strong> <strong>TN</strong> <strong>Client</strong> and/or the configuration is then downloaded toAvalanche-enabled <strong>PSC</strong> mobile devices.NOTE An Avalanche-enabled mobile device (also called an Avalanche client)is a mobile device on which you have installed the Avalanche Enabler. Formore information about installing the Avalanche Enabler on <strong>PSC</strong> <strong>300</strong>-seriesmobile devices, see the <strong>PSC</strong> <strong>300</strong>-<strong>Series</strong> Avalanche Enabler User’s <strong>Guide</strong>.<strong>Wavelink</strong> <strong>TN</strong> <strong>Client</strong> ComponentsThe <strong>Wavelink</strong> <strong>TN</strong> <strong>Client</strong> has the following components:• Host profiles• Emulation parameters• LocalizationHost ProfilesA host profile contains all of the information that a mobile device needs toconnect to a particular host, including the IP address of the host, the TCP portnumber on which the host is listening for Telnet requests, the emulation type,and login information.Host profiles provide an easy way for users at a mobile device to establish aconnection with a host without having to remember the parameters that arerequired to establish the session.Emulation ParametersThe configuration utility allows you to configure the emulation parametersfor Telnet sessions. For example, you can change the way the virtual screendisplays on the mobile device, the type and size of font that is used, and thetype of printer to which the mobile device may be connected.You can configure global and per-host emulation parameters.Global emulation parameters apply to terminal emulation with hosts forwhich you have not configured a per-host profile.
4 <strong>PSC</strong> <strong>300</strong>-<strong>Series</strong> <strong>Wavelink</strong> <strong>TN</strong> <strong>Client</strong> User’s <strong>Guide</strong>Configuring per-host emulation parameters allows you to specify theemulation parameters for terminal emulation sessions with a particular host.LocalizationLocalization allows you to deploy language profiles with the <strong>Wavelink</strong> <strong>TN</strong><strong>Client</strong>. The language profile that you deploy with the <strong>Wavelink</strong> <strong>TN</strong> <strong>Client</strong>determines the language in which the <strong>Wavelink</strong> <strong>TN</strong> <strong>Client</strong> interface displays.<strong>Wavelink</strong> <strong>TN</strong> <strong>Client</strong>The <strong>Wavelink</strong> <strong>TN</strong> <strong>Client</strong> provides the following functionality:• Use host profiles to initiate Telnet sessions with hosts.• Engage in up to four simultaneous Telnet sessions.• Configure <strong>Wavelink</strong> licensing (authorization).• Configure new host profiles.• View and modify certain global and per-host emulation parameters.• View version information.
Chapter 2: Installation 5Chapter 2: InstallationThis section provides the following information:• <strong>PSC</strong> <strong>300</strong>-series <strong>Wavelink</strong> <strong>TN</strong> <strong>Client</strong> installation requirements• <strong>PSC</strong> <strong>300</strong>-series <strong>Wavelink</strong> <strong>TN</strong> <strong>Client</strong> installation process• <strong>PSC</strong> <strong>300</strong>-series <strong>Wavelink</strong> <strong>TN</strong> <strong>Client</strong> uninstall processInstallation RequirementsThis section provides information about the installation requirements for the<strong>PSC</strong> <strong>300</strong>-series <strong>Wavelink</strong> <strong>TN</strong> <strong>Client</strong>.Device RequirementsThe <strong>PSC</strong> <strong>300</strong>-series mobile device(s) on which you want to install the<strong>Wavelink</strong> <strong>TN</strong> <strong>Client</strong> should meet the following specifications:• Avalanche Enabler installed, operational, and properly configured on the<strong>PSC</strong> <strong>300</strong>-series mobile device.NOTE For more information about obtaining, installing, and configuring theAvalanche Enabler for <strong>PSC</strong> <strong>300</strong>-series mobile devices, see the <strong>PSC</strong> <strong>300</strong>-<strong>Series</strong>Avalanche Enabler User’s <strong>Guide</strong>.Other RequirementsBefore you proceed with the installation of the <strong>Wavelink</strong> <strong>TN</strong> <strong>Client</strong>, ensurethat you also have the following:• Host system with Avalanche Manager and valid licenses for Avalancheclients• Device cradle and proper serial (null modem) cable for the mobile device(for serial installation of the <strong>Wavelink</strong> <strong>TN</strong> <strong>Client</strong> only)• Properly configured IP and RF parameters (for RF installation of the<strong>Wavelink</strong> <strong>TN</strong> <strong>Client</strong> only)
6 <strong>PSC</strong> <strong>300</strong>-<strong>Series</strong> <strong>Wavelink</strong> <strong>TN</strong> <strong>Client</strong> User’s <strong>Guide</strong>Installing the <strong>Wavelink</strong> <strong>TN</strong> <strong>Client</strong>This section provides information about installing the <strong>Wavelink</strong> <strong>TN</strong> <strong>Client</strong> on<strong>PSC</strong> <strong>300</strong>-series mobile devices.Installation OverviewThe following steps provide an overview of the process of installing the<strong>Wavelink</strong> <strong>TN</strong> <strong>Client</strong>:1 Obtain the <strong>PSC</strong> <strong>300</strong>-series <strong>Wavelink</strong> <strong>TN</strong> <strong>Client</strong> Avalanche softwarepackage.2 Install the <strong>Wavelink</strong> <strong>TN</strong> <strong>Client</strong> software package in Avalanche Manager.3 Configure and enable the <strong>Wavelink</strong> <strong>TN</strong> <strong>Client</strong> software package inAvalanche Manager.4 Update the <strong>PSC</strong> <strong>300</strong>-series mobile device(s) to download the <strong>Wavelink</strong> <strong>TN</strong><strong>Client</strong>.Obtaining the Avalanche Software PackageYou can download the most current version of the <strong>PSC</strong> <strong>300</strong>-series <strong>Wavelink</strong><strong>TN</strong> <strong>Client</strong> Avalanche software package at www.wavelink.com/downloads.NOTE You will need to register with <strong>Wavelink</strong> Corporation, before you willbe able to perform any downloads from the <strong>Wavelink</strong> download area.Registration with <strong>Wavelink</strong> Corporation is free.The downloadable version of the <strong>Wavelink</strong> <strong>TN</strong> <strong>Client</strong> is a demonstration(demo) version that allows you to test the <strong>Wavelink</strong> <strong>TN</strong> <strong>Client</strong>. In the demoversion of the <strong>Wavelink</strong> <strong>TN</strong> <strong>Client</strong>, Telnet sessions initiated with the<strong>Wavelink</strong> <strong>TN</strong> <strong>Client</strong> will automatically terminate after an hour of activity.You may obtain a fully licensed version of the <strong>Wavelink</strong> <strong>TN</strong> <strong>Client</strong> from your<strong>Wavelink</strong> Corporation representative.
Chapter 2: Installation 7Installing the Avalanche Software PackageAfter you have obtained the Avalanche <strong>Wavelink</strong> <strong>TN</strong> <strong>Client</strong> softwarepackage, place the software package in an easily accessible location andinstall the software package in Avalanche Manager.Installing the software package requires the following basic steps:1 Create a software collection.2 Install the software package in the software collection.To install the Avalanche <strong>Wavelink</strong> <strong>TN</strong> <strong>Client</strong> package:1 Ensure that the software package is in directory that you can access fromthe system that hosts the Management Console.NOTE Avalanche software packages are denoted with an .ava file extension.2 Launch the Management Console and connect to the Agent.3 In the Avalanche Agents tree, right-click Software Collections.A menu list appears.4 From the menu list, select New Software Collection, as shown in Figure 2-1.Figure 2-1. Creating a New Software Collection
8 <strong>PSC</strong> <strong>300</strong>-<strong>Series</strong> <strong>Wavelink</strong> <strong>TN</strong> <strong>Client</strong> User’s <strong>Guide</strong>The Software Collection Name dialog box appears.5 In the Software Collection Name dialog box, type a name for the softwarecollection, as shown in Figure 2-2.Figure 2-2. Naming a Software Collection6 Click OK.The new software collection now appears beneath Software Collections inthe Avalanche Agents tree.7 From the Management Console Software Management menu, selectInstall Software Package....The Install Software Package Wizard launches and displays the Select theAvalanche package to install dialog box.8 Click the ... icon button.The Select the path dialog box appears.9 Use the browse feature of the Select the path dialog box to locate theAvalanche software package that you want to install.10 After you have located and selected the software package, click Select.The path to the package now appears in the Select the Avalanche package toinstall dialog box.11 Click Next.The Install Software Package Wizard displays the License Agreement dialogbox.
Chapter 2: Installation 912 Select the Yes, I agree option button.13 Click Next.The Install Software Package Wizard displays the Select the softwarecollection dialog box.14 From the list of software collections in the Select the software collectiondialog box, select the software collection in which you want to install thesoftware package, as shown in Figure 2-3.Figure 2-3. Selecting the Software Collection15 Click Next.The Installing the Avalanche package dialog box displays the installationprocess.16 After the software package is installed, click Finish.
10 <strong>PSC</strong> <strong>300</strong>-<strong>Series</strong> <strong>Wavelink</strong> <strong>TN</strong> <strong>Client</strong> User’s <strong>Guide</strong>The software package now appears in the appropriate software collectionin the Avalanche Agents tree of the Management Console, as shown inFigure 2-4.Figure 2-4. Software Package in Software CollectionConfiguring the <strong>Wavelink</strong> <strong>TN</strong> <strong>Client</strong>Before you can download the <strong>Wavelink</strong> <strong>TN</strong> <strong>Client</strong> to mobile devices,configure the software package in Avalanche Manager.To configure and enable the Avalanche <strong>Wavelink</strong> <strong>TN</strong> <strong>Client</strong>:1 Launch Avalanche Manager and connect to the Avalanche Agent.2 In the Avalanche Agents tree, locate and right-click the <strong>Wavelink</strong> <strong>TN</strong><strong>Client</strong> software package.A menu list appears.3 From the menu list, select Configure > Host Profiles, as shown inFigure 2-5.
Chapter 2: Installation 11Figure 2-5. Selecting to Configure Host ProfilesThe Host Profiles dialog box appears.4 Use the Host Profiles dialog box to configure the host profiles that youwant to download to the mobile device.NOTE For more information about configuring host profiles, see ConfiguringHost Profiles on page 19.5 In the Avalanche Agents tree, right-click the <strong>Wavelink</strong> <strong>TN</strong> <strong>Client</strong> softwarepackage.A menu list appears.6 From the menu list, select Configure Package > EmulationParameters, as shown in Figure 2-6.
12 <strong>PSC</strong> <strong>300</strong>-<strong>Series</strong> <strong>Wavelink</strong> <strong>TN</strong> <strong>Client</strong> User’s <strong>Guide</strong>Figure 2-6. Selecting to Configure Emulation ParametersThe Configuration Manager appears.7 Use the Configuration Manager to configure the global emulationparameters for the <strong>Wavelink</strong> <strong>TN</strong> <strong>Client</strong>.NOTE For more information about configuring emulation parameters, seeConfiguring Emulation Parameters on page 29.8 In Avalanche Manager, right-click the <strong>Wavelink</strong> <strong>TN</strong> <strong>Client</strong>.A menu list appears.9 From the menu list, select Configure Package > Localization, as shown inFigure 2-7.
Chapter 2: Installation 13Figure 2-7. Selecting to Configuring LocalizationThe Localize dialog box appears.10 Use the Localize dialog box to configure localization for the <strong>Wavelink</strong> <strong>TN</strong><strong>Client</strong>.NOTE For information about configuring localization, see ConfiguringLocalization on page 37.The software package is now configured with parameters that will bedownloaded to the mobile device along with the software package.Enabling the <strong>Wavelink</strong> <strong>TN</strong> <strong>Client</strong>Before you can download the software package and the configuration to themobile device, you must enable the <strong>Wavelink</strong> <strong>TN</strong> <strong>Client</strong> software package inAvalanche Manager.To enable the <strong>Wavelink</strong> <strong>TN</strong> <strong>Client</strong>:1 Launch Avalanche Manager and connect to the Avalanche Agent.
14 <strong>PSC</strong> <strong>300</strong>-<strong>Series</strong> <strong>Wavelink</strong> <strong>TN</strong> <strong>Client</strong> User’s <strong>Guide</strong>2 In the Avalanche Agent tree, locate and right-click the <strong>Wavelink</strong> <strong>TN</strong> <strong>Client</strong>software package.A menu list appears.3 From the menu list, select Enable Package, as shown in Figure 2-8.Figure 2-8. Enabling the <strong>Wavelink</strong> <strong>TN</strong> <strong>Client</strong> Software PackageThe package is enabled and ready to be downloaded to the mobiledevice(s).Deploying the <strong>Wavelink</strong> <strong>TN</strong> <strong>Client</strong>After you have enabled the <strong>Wavelink</strong> <strong>TN</strong> <strong>Client</strong> software package inAvalanche Manager, it is ready to be downloaded to mobile devices. You candownload the <strong>Wavelink</strong> <strong>TN</strong>C <strong>Client</strong> over a serial or RF connection betweenthe Avalanche Agent and the mobile device.To deploy the <strong>Wavelink</strong> <strong>TN</strong> <strong>Client</strong> to mobile devices:1 Update the client.
Chapter 2: Installation 15NOTE Updates on <strong>PSC</strong> <strong>300</strong>-series mobile devices are performed when theAvalanche Enabler on the mobile device launches. For more informationabout serial and RF updates, see Performing Updates on page 53. Also see the<strong>PSC</strong> <strong>300</strong>-<strong>Series</strong> Avalanche Enabler User’s <strong>Guide</strong>.During the update, the <strong>Wavelink</strong> <strong>TN</strong> <strong>Client</strong> (and its configuration) aredownloaded to the mobile device.After it is downloaded to the mobile device, the <strong>Wavelink</strong> <strong>TN</strong> <strong>Client</strong>automatically launches.Uninstalling the <strong>Wavelink</strong> <strong>TN</strong> <strong>Client</strong>If a mobile device no longer needs the <strong>Wavelink</strong> <strong>TN</strong> <strong>Client</strong>, you can removethe application from the mobile device.Removing the <strong>Wavelink</strong> <strong>TN</strong> <strong>Client</strong> from a mobile device requires thefollowing basic steps:1 Disable or delete the <strong>Wavelink</strong> <strong>TN</strong> <strong>Client</strong> in Avalanche Manager.2 Ensure that the Avalanche client is configured to delete orphan packages.3 Update the client.To remove the <strong>Wavelink</strong> <strong>TN</strong> <strong>Client</strong> from a mobile device:1 Launch Avalanche Manager and connect to the Avalanche Agent.2 In the Avalanche Agents tree, locate and right-click the <strong>Wavelink</strong> <strong>TN</strong><strong>Client</strong> software package.A menu list appears.3 From the menu list, select Disable Package or Delete Package, asshown in Figure 2-9.
16 <strong>PSC</strong> <strong>300</strong>-<strong>Series</strong> <strong>Wavelink</strong> <strong>TN</strong> <strong>Client</strong> User’s <strong>Guide</strong>Figure 2-9. Disabling the <strong>Wavelink</strong> <strong>TN</strong> <strong>Client</strong> Software PackageNOTE If you select Delete Package, the package will be removed fromAvalanche Manager.4 Ensure that Avalanche Manager is set to delete orphan packages on themobile device.NOTE For more information about orphan packages and configuringAvalanche Manager to delete orphan packages on Avalanche clients, seeUsing Software Packages on page 71.5 Update the client.NOTE Updates on <strong>PSC</strong> <strong>300</strong>-series mobile devices are performed when theAvalanche Enabler on the mobile device launches. For more informationabout serial and RF updates, see Performing Updates on page 53. Also see the<strong>PSC</strong> <strong>300</strong>-<strong>Series</strong> Avalanche Enabler User’s <strong>Guide</strong>.
Chapter 2: Installation 17When the update is performed, the <strong>Wavelink</strong> <strong>TN</strong> <strong>Client</strong> is deleted fromthe mobile device.
18 <strong>PSC</strong> <strong>300</strong>-<strong>Series</strong> <strong>Wavelink</strong> <strong>TN</strong> <strong>Client</strong> User’s <strong>Guide</strong>
Chapter 3: Configuration 19Chapter 3: ConfigurationThis section covers the following topics:• Configuring host profiles• Configuring global and per-host emulation parameters• Configuring localization• Downloading configurations to the mobile deviceOverview of ConfigurationAll configuration of the <strong>Wavelink</strong> <strong>TN</strong> <strong>Client</strong> is performed at the AvalancheManagement Console. Use Avalanche Manager to configure the <strong>Wavelink</strong><strong>TN</strong> <strong>Client</strong> software package.The <strong>Wavelink</strong> <strong>TN</strong> <strong>Client</strong> software package allows you to configure thefollowing components of the <strong>Wavelink</strong> <strong>TN</strong> <strong>Client</strong>:• Host profiles• Global and per-host emulation parameters• LocalizationAny time that you make a change to the configuration of the <strong>Wavelink</strong> <strong>TN</strong><strong>Client</strong>, you will need to download the configuration to the mobile device byperforming an update.Configuring Host ProfilesThis section provides the following information:• An overview of host profiles and configuring host profiles.• Accessing the Host Profiles dialog box.• Configuring host profiles.
20 <strong>PSC</strong> <strong>300</strong>-<strong>Series</strong> <strong>Wavelink</strong> <strong>TN</strong> <strong>Client</strong> User’s <strong>Guide</strong>About Host ProfilesThe <strong>TN</strong> <strong>Client</strong> allows you to configure host profiles for mobile devices.Host profiles provide a method to specify the parameters of a Telnetconnection from a mobile device to a host. For example, a host profile allowsyou to specify the IP address of a host and the TCP port number on which thehost listens for Telnet connections from clients.You configure host profiles in the Host Profiles dialog box.Host Profile Configuration OverviewThe following tasks outline the process of configuring host profiles for the <strong>TN</strong><strong>Client</strong>:1 Access the Host Profiles dialog box.2 Add, modify, or remove host profiles and save the changes.3 Download the configuration to mobile devices.When you save the host profiles that you have configured, the applicationthat you are using creates a configuration file that contains the parametersand settings of the host profile.The download process downloads the configuration file to the mobile device.The new configuration file overwrites the existing configuration file on themobile device.Accessing Host ProfilesThe following section explains how to access the Host Profiles dialog box,where you can add, modify, or delete host profile configurations that you canthen download to the mobile device.To access the Host Profiles dialog box.1 Launch Avalanche Manager and connect to the Avalanche Agent.2 In the Avalanche Agents tree, locate and right-click the <strong>Wavelink</strong> <strong>TN</strong><strong>Client</strong> software package.A menu list appears.
Chapter 3: Configuration 213 From the menu list, select Configure Package > Host Profiles, asshown in Figure 3-1.Figure 3-1. Accessing the Host Profiles Dialog BoxThe Host Profiles dialog box appears, as shown in Figure 3-2.
22 <strong>PSC</strong> <strong>300</strong>-<strong>Series</strong> <strong>Wavelink</strong> <strong>TN</strong> <strong>Client</strong> User’s <strong>Guide</strong>Figure 3-2. Host Profiles Dialog Box4 Use the Host Profiles dialog box to add, remove, or configure the hostprofiles that you want to download to the mobile device.NOTE For more information about using the Host Profiles dialog box, seeConfiguring Host Profiles on page 22.5 After you have configured the host profiles that you want to download tothe mobile device, click OK.The host profiles are saved and the Host Profiles dialog box closes.6 Download the new configuration to the mobile device(s).NOTE For more information on downloading configurations to mobiledevices, see Downloading Configurations on page 40.Configuring Host ProfilesThis section provides information on the following tasks:
Chapter 3: Configuration 23• Creating a host profile.• Modifying a host profile.• Removing a host profile.Creating Host ProfilesYou can use the Host Profiles dialog box to create new host profiles for the <strong>TN</strong><strong>Client</strong>.To create a host profile:1 Access the Host Profiles dialog box.2 In the Host Profiles dialog box, click New.The Host Profiles dialog box displays tabs with parameters that allow youto configure the settings for the host profile.The name of the host profiles that you have configured appear in the leftpane of the Host Profiles dialog box.3 Configure the settings for the host profile.NOTE For information about the parameters in the tabs of the Host Profilesdialog box, see Host Profile Settings on page 24.4 After you have configured the settings for the new host profile, click OKto save the configuration.NOTE You can configure several host profiles before you click OK. The <strong>TN</strong><strong>Client</strong> will maintain the settings. If you click Cancel, the dialog box closesand the configurations that you have made are lost.Modifying Host ProfilesYou can use the Host Profiles dialog box to modify existing host profiles.To modify an existing host profile:1 Access the Host Profiles dialog box.
24 <strong>PSC</strong> <strong>300</strong>-<strong>Series</strong> <strong>Wavelink</strong> <strong>TN</strong> <strong>Client</strong> User’s <strong>Guide</strong>2 In the left pane of the Host Profiles dialog box, select the host profile thatyou want to modify.The Host Profiles dialog box displays tabs that contain the settings for thehost profile.3 Use the tabs in the Host Profiles dialog box to modify the host profile.NOTE For more information about the parameters in the tabs of the HostProfiles dialog box, see Host Profile Settings on page 24.4 After you have modified the host profile, click OK to save the newconfiguration.Removing Host ProfilesYou can use the Host Profiles dialog box to remove host profiles from theconfiguration.To remove a host profile:1 Access the Host Profiles dialog box.2 In the left pane of the Host Profiles dialog box, select the host profile thatyou want to remove.3 Click Remove.4 Click OK.The new configuration is saved and the Host Profiles dialog box closes.Host Profile SettingsThis section explains the options in the tabs of the Host Profiles dialog box.Host SettingsFigure 3-3 shows the Host tab in the Host Profiles dialog box.
Chapter 3: Configuration 25Figure 3-3. Host Profiles Host TabThe following list describes the options in the Host tab:NameTypeAddressPortSpecifies the name of the host profile.Determines the type of emulation used to connect tothe host. (The type of emulation that you selectdetermines the tabs that appear in the Host Profilesdialog box for that host profile.)Specifies the IP address of the host.Specifies the TCP port number on which the hostlistens for Telnet connections from clients.IBM SettingsFigure 3-4 shows the IBM Settings tab in the Host Profiles dialog box. (The IBMSettings tab only appears if you have selected IBM-based emulation from theType menu list in the Host tab.)
26 <strong>PSC</strong> <strong>300</strong>-<strong>Series</strong> <strong>Wavelink</strong> <strong>TN</strong> <strong>Client</strong> User’s <strong>Guide</strong>Figure 3-4. Host Profiles IBM Settings TabThe following list explains the options in the IBM Settings tab:Workstation IDSpecifies an identifier for the client. You can use thefollowing variables to provide a unique identifier forthe client:• %a - %d. Captures octets of the IP address of themobile device (%a captures the first octet, %dcaptures the last octet). For example, %a%b%c%dwould capture all four octets of the IP address ofthe mobile unit.• %m - %r. Captures octets of the MAC address ofthe mobile device (%m captures the first octet, %rcaptures all six octets). For example,%m%n%o%p%q%r would capture all six octets ofhardware address of the mobile unit.• %s. Captures the session number.• %t. Captures the terminal ID of the device.
Chapter 3: Configuration 27VT SettingsFigure 3-5 shows the VT Settings tab in the Host Profiles dialog box. (The VTSettings tab only appears if you have selected VT-type emulation from theType menu list in the Host tab.)Figure 3-5. Host Profiles VT SettingsThe following list describes the options in the VT Settings tab:Telnet NegotiationStringSpecifies the Telnet negotiation string the clientshould send to the host to establish a session.Autologin SettingsFigure 3-6 shows the Autologin tab in the Host Profiles dialog box. (TheAutologin only appears if you have selected VT-type emulation from theType menu list in the Host tab of the Host Profiles dialog box.
28 <strong>PSC</strong> <strong>300</strong>-<strong>Series</strong> <strong>Wavelink</strong> <strong>TN</strong> <strong>Client</strong> User’s <strong>Guide</strong>Figure 3-6. Host Profiles Autologin TabThe following list describes the parameters in the Autologin tab:Name (Prompts)Name (Responses)Password (Prompts)Password (Responses)Command (Prompts)Command (Responses)CFG in terminalSpecifies the host-side Telnet login prompt.Specifies the response to the login prompt that theclient should send to the host.Specifies the host-side password prompt.Specifies the response to the password prompt thatthe client should send to the host.Specifies the command prompt at the host.Specifies the response to the command prompt thatthe client should send to the host.Enables or disables the option to allow the user atthe terminal to configure the correspondingresponse.Configuration SettingsFigure 3-7 shows the Configuration tab in the Host Profiles dialog box.
Chapter 3: Configuration 29Figure 3-7. Host Profiles Configuration TabThe following list describes the options in the Configuration tab:ModifyResetOpens the Configuration Manager, where you canconfigure per-host emulation parameters for the hostprofile. For more information about emulationparameters and the Configuration Manager, seeConfiguring Emulation Parameters on page 29.Restores the emulation parameters for the hostprofile to their default settings.Configuring Emulation ParametersThis section provides information about configuring emulation parametersfor the <strong>Wavelink</strong> <strong>TN</strong> <strong>Client</strong>.About Emulation ParametersThe <strong>TN</strong> <strong>Client</strong> allows you to configure the emulation parameters for hostconnections.
30 <strong>PSC</strong> <strong>300</strong>-<strong>Series</strong> <strong>Wavelink</strong> <strong>TN</strong> <strong>Client</strong> User’s <strong>Guide</strong>You make changes to emulation parameters with the Configuration Managerutility, which provides an organized list of the emulation parameters that youcan modify.Emulation parameters are divided into two groups:• Per-host. Per-host emulation parameters apply only to a specific hostprofile on the client. You can access the emulation parameters for a specifichost profile through the Host Profiles dialog box.• Global. Global emulation parameters apply to all of the host profiles withwhich you have configured a client. Per-host emulation parameterconfigurations pre-empt global emulation parameter configurations.The following tasks outline the process of configuring emulation parameters:1 Access the Configuration Manager.2 Use the Configuration Manager to modify emulation parameters and savethe configuration.3 Download the configuration to the mobile device.The Configuration Manager generates a configuration file that contains globaland per-host emulation parameter settings.When you download the configuration file to the mobile device, any existingconfiguration file is overwritten.Accessing the Configuration ManagerThis section contains information about using the <strong>TN</strong> <strong>Client</strong> installationutility to access the Configuration Manager to modify global or per-hostconfiguration parameters for the <strong>TN</strong> <strong>Client</strong>.Accessing the Configuration Manager for Global SettingsYou can access the global emulation parameters through the <strong>TN</strong> <strong>Client</strong>installation utility.To access global emulation parameters:1 Launch Avalanche Manager and connect to the Avalanche Agent.2 In the Avalanche Agents tree, locate and right-click the <strong>Wavelink</strong> <strong>TN</strong><strong>Client</strong> software package.
Chapter 3: Configuration 31A menu list appears.3 From the menu list, select Configure Package > EmulationParameters, as shown in Figure 3-8.Figure 3-8. Accessing Emulation ParametersThe Configuration Manager appears.4 Use the Configuration Manager to configure the global emulationparameters.NOTE For information on using the Configuration Manager, see Using theConfiguration Manager on page 33.5 After you configure the emulation parameters, click the Save icon to savethe configuration to the host.6 Close the Configuration Manager.7 Download the new configuration to the mobile device(s).
32 <strong>PSC</strong> <strong>300</strong>-<strong>Series</strong> <strong>Wavelink</strong> <strong>TN</strong> <strong>Client</strong> User’s <strong>Guide</strong>NOTE For more information on downloading configurations to the mobiledevice, see Downloading Configurations on page 40.Accessing the Configuration Manager for Per-Host SettingsYou can use the <strong>TN</strong> <strong>Client</strong> installation utility to access the ConfigurationManager and modify per-host emulation parameters.To access and modify per-host emulation parameters:1 Launch Avalanche Manager and connect to the Avalanche Agent.2 In the Avalanche Agents tree, locate and right-click the <strong>Wavelink</strong> <strong>TN</strong><strong>Client</strong> software package.A menu list appears.3 From the menu list, select Configure Package > Host Profiles, asshown in Figure 3-9.Figure 3-9. Accessing Per-Host Configuration ParametersThe Host Profiles dialog box appears.
Chapter 3: Configuration 334 In the left pane of the Host Profiles dialog box, select the host profile withthe emulation parameters that you want to modify.The Host Profiles dialog box displays the parameters of the host profile.5 Select the Configuration tab.6 Click Modify.The Configuration Manager appears.7 Use the Configuration Manager to configure the emulation parametersthat will be applied to the host profile that you previously selected.NOTE For information about using Configuration Manager, see Using theConfiguration Manager on page 33.8 After you have modified the emulation parameters in the ConfigurationManager, click the Save icon to save the configuration to the host system.9 Close the Configuration Manager.10 In the Host Profiles dialog box, click OK.11 Download the new configuration to the mobile device.NOTE For information downloading configurations to the mobile device, seeDownloading Configurations on page 40.Using the Configuration ManagerThe Configuration Manager is the utility that allows you to modify globaland per-host emulation parameters.Figure 3-10 shows the Configuration Manager.
34 <strong>PSC</strong> <strong>300</strong>-<strong>Series</strong> <strong>Wavelink</strong> <strong>TN</strong> <strong>Client</strong> User’s <strong>Guide</strong>Figure 3-10. Configuration ManagerThe left pane of the Configuration Manager displays the emulationparameters that you can modify. The emulation parameters are grouped bycategory.When you select a parameter in the left pane, information about theparameter displays in the right pane, as shown in Figure 3-11.Figure 3-11. Emulation Parameter Information
Chapter 3: Configuration 35Emulation ParametersModifiable emulation parameters are grouped by category in the left pane ofthe Configuration Manager.The following list describes the different categories:COMEmulationMagnetic Stripe ReaderScannerParameters in this category configure the function ofthe COM port on mobile devices.Parameters in this category configure terminalemulation functions on mobile devices.Parameters in this category configure the function ofmagnetic stripe readers on mobile devices.Parameters in this category configure the function ofbar code scanners on mobile devices.Appendix C: Emulation Parameters on page 99 contains detailed informationabout each of the modifiable parameters in the Configuration Manager.Modifying Emulation ParametersDetermine the emulation parameters that you want to modify and use theConfiguration Manager to make modifications.To modify an emulation parameter:1 Access the Configuration Manager.2 In the left pane of the Configuration Manager, locate the parameter thatyou want to modify.3 Double-click the emulation parameter or right-click the emulationparameter and choose Edit from the menu list.A dialog box appears that allows you to modify the parameterconfiguration, as shown in Figure 3-12.
36 <strong>PSC</strong> <strong>300</strong>-<strong>Series</strong> <strong>Wavelink</strong> <strong>TN</strong> <strong>Client</strong> User’s <strong>Guide</strong>Figure 3-12. Modifying an Emulation Parameter4 Use the dialog box to configure the parameter.5 After you have configured the parameter, click OK to keep the setting.Click Cancel or the Close button to cancel any changes you have made.6 In the Configuration Manager, click the Save icon, as shown in Figure 3-13.Figure 3-13. Configuration Manager Save IconThe configuration changes are saved to the host system.7 Close the Configuration Manager.8 Download the new configuration to clients.Using the Find FunctionUse the Find function of the Configuration Manager to locate parameters orinformation by supplying a partial or full string that the ConfigurationManager can use to locate the parameter or information that you want to find.To use the find function:1 From the Configuration Manager Edit menu, select Find, as shown inFigure 3-14.
Chapter 3: Configuration 37Figure 3-14. Selecting the Find FunctionThe Find dialog box appears.2 Input the partial or full string for the parameter or information that youwant to find, as shown in Figure 3-15.Figure 3-15. Inputting a String to FindNOTE Enable the Search all text checkbox to search not only the parameters,but also the help files.3 Click Find Next to begin the search.Continue to click Find Next until you locate the parameter orinformation for which you are searching.Configuring LocalizationThis section provides information about the localization capabilities andconfiguring localization for the <strong>TN</strong> <strong>Client</strong>.
38 <strong>PSC</strong> <strong>300</strong>-<strong>Series</strong> <strong>Wavelink</strong> <strong>TN</strong> <strong>Client</strong> User’s <strong>Guide</strong>About LocalizationLocalization allows you to install language files to a mobile device that causethe <strong>TN</strong> <strong>Client</strong> interface to display in a particular language.The <strong>TN</strong> <strong>Client</strong> offers the following languages:• English (United States)• French (European)• Swiss• Spanish• Japanese Katakana• German• Dutch• English (United Kingdom)• French (Canadian)• Swedish• Norwegian• Italian• Finnish• DanishNOTE <strong>Wavelink</strong> Corporation does not provide most language message files.You must install the appropriate language message files on the mobile devicebefore the <strong>TN</strong> <strong>Client</strong> can provide the localization that you require.Configuring LocalizationLocalization is configured through the Localize dialog box, which you canaccess through the <strong>TN</strong> <strong>Client</strong> software package in Avalanche Manager.The following is a list of the tasks for configuring and installing localization:1 Access the Localize dialog box.2 Select the desired language and save the configuration.3 Download the configuration to clients.To configure localization with the <strong>TN</strong> <strong>Client</strong> installation utility:1 Launch Avalanche Manager and connect to the Avalanche Agent.2 In Avalanche Manager, locate and right-click the <strong>Wavelink</strong> <strong>TN</strong> <strong>Client</strong>software package.
Chapter 3: Configuration 39A menu list appears.3 From the menu list, select Configure Package > Localization, asshown in Figure 3-16.Figure 3-16. Accessing the Localization Dialog BoxThe Localize dialog box appears.4 Select the language profile that you want to install on the client.5 Click OK.The configuration is saved to the host system and the Localize dialog boxcloses.6 Download the configuration to the mobile device.NOTE For more information about downloading configurations to mobiledevices, see the next section.
40 <strong>PSC</strong> <strong>300</strong>-<strong>Series</strong> <strong>Wavelink</strong> <strong>TN</strong> <strong>Client</strong> User’s <strong>Guide</strong>Downloading ConfigurationsAfter you have enabled the <strong>Wavelink</strong> <strong>TN</strong> <strong>Client</strong> software package inAvalanche Manager, it is ready to be downloaded to mobile devices. You candownload the <strong>Wavelink</strong> <strong>TN</strong> <strong>Client</strong> over a serial or RF connection between theAvalanche Agent and the mobile device.To deploy the <strong>Wavelink</strong> <strong>TN</strong> <strong>Client</strong> to mobile devices:1 Ensure that the <strong>Wavelink</strong> <strong>TN</strong> <strong>Client</strong> software package is enabled inAvalanche Manager.2 Update the client.NOTE Updates on <strong>PSC</strong> <strong>300</strong>-series mobile devices are performed when theAvalanche Enabler on the mobile device launches. For more informationabout serial and RF updates, see Performing Updates on page 53. Also see the<strong>PSC</strong> <strong>300</strong>-<strong>Series</strong> Avalanche Enabler User’s <strong>Guide</strong>.During the update, the <strong>Wavelink</strong> <strong>TN</strong> <strong>Client</strong> (and its configuration) aredownloaded to the mobile device.After it is downloaded to the mobile device, the <strong>Wavelink</strong> <strong>TN</strong> <strong>Client</strong>automatically launches.
Chapter 4: Using the <strong>Wavelink</strong> <strong>TN</strong> <strong>Client</strong> 41Chapter 4: Using the <strong>Wavelink</strong> <strong>TN</strong> <strong>Client</strong>This section covers the following topics:• <strong>Client</strong> licensing• Manually configuring host profiles at the mobile device• Using the <strong>Wavelink</strong> <strong>TN</strong> <strong>Client</strong><strong>Client</strong> LicensingThe <strong>Wavelink</strong> <strong>TN</strong> <strong>Client</strong> software package is pre-configured with one of thefollowing types of licenses:• Standard• Demonstration (Demo)Standard LicensesA standard license is purchased with the <strong>Wavelink</strong> <strong>TN</strong> <strong>Client</strong> from <strong>Wavelink</strong>Corporation. The standard license allows you to use the <strong>Wavelink</strong> <strong>TN</strong> <strong>Client</strong>without restriction.NOTE To purchase the <strong>Wavelink</strong> <strong>TN</strong> <strong>Client</strong> with a standard license, please seeyour <strong>Wavelink</strong> representative.Demo LicensesThe <strong>Wavelink</strong> <strong>TN</strong> <strong>Client</strong> that is available for download is configured with ademonstration (demo) license. The demo license allows you to use all of thefeatures of the <strong>Wavelink</strong> <strong>TN</strong> <strong>Client</strong>. However, the demo version of the<strong>Wavelink</strong> <strong>TN</strong> <strong>Client</strong> is configured to automatically terminate a Telnet sessionafter the session has been active for 1 hour.Manually Configuring Host ProfilesThe <strong>Wavelink</strong> <strong>TN</strong> <strong>Client</strong> allows you to add or configure host profiles at themobile device.
42 <strong>PSC</strong> <strong>300</strong>-<strong>Series</strong> <strong>Wavelink</strong> <strong>TN</strong> <strong>Client</strong> User’s <strong>Guide</strong>NOTE Any changes that you make to host profiles at the mobile device will beoverwritten, when the mobile device performs an Avalanche update.NOTE The <strong>Wavelink</strong> <strong>TN</strong> <strong>Client</strong> does not allow to configure emulationparameters or localization at the mobile device.Manually Accessing Host ProfilesBefore you can add or modify a host profile, you must access the hostconfiguration (CONFIG HOST) menu.To access the host configuration menu from the <strong>TN</strong> <strong>Client</strong>:1 At the mobile device, press .2 You are prompted for a password.3 Type the password “system” at the prompt.NOTE The default password, “system”, cannot be changed.A warning message appears.4 Press Y to continue.5 The MODIFY menu appears.6 Press 2.7 The host configuration screen (CONFIG HOST) screen appears.Use the host configuration screen to select and modify a host profile tocreate a new host profile.Modifying an Existing Host ProfileYou can use the host configuration screen to modify an existing host profile.To modify an existing host profile:1 Access the host configuration screen.
Chapter 4: Using the <strong>Wavelink</strong> <strong>TN</strong> <strong>Client</strong> 432 Use the arrow keys on the mobile device to select the host profile in theCONFIG HOST menu that you want to configure.3 Press Enter.4 Use the screens to configure the new parameters for the host profile.NOTE For information about the host profile screen, see Host Profile Screen onpage 45.NOTE For information about IBM host profile parameters, see IBM HostProfiles on page 46.NOTE For information about VT/HP host profile parameters, see VT/HP HostProfiles on page 46.NOTE For information about the function of various keys that can be used inthese screens, see Control Keys on page 47.5 After you have finished configuring the host profile, press CTRL S orEnter.The changes that you have made are set, and you are returned to theconfiguration menu.6 Press Esc.A message appears that asks you if you want to save the changes that youhave made.7 Press Y.The changes that you have made are saved, and you are returned to theMODIFY menu.8 Press 3.
44 <strong>PSC</strong> <strong>300</strong>-<strong>Series</strong> <strong>Wavelink</strong> <strong>TN</strong> <strong>Client</strong> User’s <strong>Guide</strong>You are returned to the <strong>Wavelink</strong> <strong>TN</strong> <strong>Client</strong>.Configuring a New Host ProfileYou can use the host configuration menu to create and configure a new hostprofile at the mobile device.To create a new host profile:1 Access the host configuration menu.2 Use the arrow keys on the mobile device to select the host profile in theCONFIG HOST menu to select the last (empty) host profile in the list.3 Press Enter.4 Use the screens to configure the parameters for the new host profile.NOTE For information about the host profile screen, see Host Profile Screen onpage 45.NOTE For information about IBM host profile parameters, see IBM HostProfiles on page 46.NOTE For information about VT/HP host profile parameters, see VT/HP HostProfiles on page 46.NOTE For information about the function of various keys that can be used inthese screens, see Control Keys on page 47.5 After you have finished configuring the host profile, press CTRL S orEnter.The changes that you have made are set, and you are returned to theconfiguration menu.6 Press Esc.
Chapter 4: Using the <strong>Wavelink</strong> <strong>TN</strong> <strong>Client</strong> 45A message appears that asks you if you want to save the changes that youhave made.7 Press Y.The changes that you have made are saved, and you are returned to theMODIFY menu.8 Press 3.You are returned to the <strong>Wavelink</strong> <strong>TN</strong> <strong>Client</strong>.Host Profile SettingsThis section provides information about the different screens that areavailable when you are configuring a host profile.Host Profile ScreenThe following list describes the parameters in the first screen of the hostprofile:Host AddressHost Profile NamePortEmulation TypeF1 = HelpF2 = Next PageIndicates the IP address of the host server withwhich the mobile device will initiate a Telnet session.Indicates the name (alias) of the host.Indicates the TCP port number on which the host islistening for Telnet connections from mobile devices.Indicates the type of emulation that is used. UseCTRL P and CTRL N to cycle through theavailable options in this field.Indicates that by pressing F1 the user can accessthe Help menu. The Help menu displays the keysequences that are available to use to maneuver andmanipulate the current screen. (For moreinformation, see Control Keys on page 47.)Indicates that the user can press F2 to advance tothe next screen.
46 <strong>PSC</strong> <strong>300</strong>-<strong>Series</strong> <strong>Wavelink</strong> <strong>TN</strong> <strong>Client</strong> User’s <strong>Guide</strong>IBM Host ProfilesThe following list describes the options that are available in the IBM screenthat appears for host profiles that are configured for 5250 or 3270 emulation.Workstation IDSpecifies an identifier for the client. You can use thefollowing variables to provide a unique identifier forthe client:• %a - %d. Captures octets of the IP address of themobile device (%a captures the first octet, %dcaptures the last octet). For example, %a%b%c%dwould capture all four octets of the IP address ofthe mobile unit.• %m - %r. Captures octets of the MAC address ofthe mobile device (%m captures the first octet, %rcaptures all six octets). For example,%m%n%o%p%q%r would capture all six octets ofhardware address of the mobile unit.• %s. Captures the session number.• %t. Captures the terminal ID of the device.VT/HP Host ProfilesThe following list describes the parameters that are available in the variousscreens of a host profile when the host profile is configured for VT/HPemulation:Name PromptNamePassword PromptPasswordCommand PromptCommandIndicates the login prompt that the host uses.indicates the reply that the mobile device sends tothe host at the login prompt.Indicates the password prompt that host users.Indicates the reply that the mobile devices sends tothe host at the password prompt.Indicates the command prompt that the host uses.Indicates the command that the mobile device sendsto the host at the command prompt.
Chapter 4: Using the <strong>Wavelink</strong> <strong>TN</strong> <strong>Client</strong> 47Telnet NegotiationStringF1 = HelpF2 = Next PageIndicates the Telnet negotiation string that themobile device should use when connecting to thehost.Indicates that by pressing F1 the user can accessthe Help menu. The Help menu displays the keysequences that are available to use to maneuver andmanipulate the current screen. (For moreinformation, see Control Keys on page 47.)Indicates that the user can press F2 to advance tothe next screen.Control KeysUse the control keys to maneuver through and manipulate the fields of thescreens in a host profile.The following list describes the available key sequences and their function.CTRL-XCTRL-SCTRL-DCTRL-NCTRL-PAborts the changes that you have made to the hostprofile and exits to the host configuration menu.Saves the changes that you have made to the hostprofile and returns you to the host configurationmenu.Deletes the contents of the current field that thecursor is in.Selects the next option in a field in which the cursoris currently located.Selects the previous option in the field in which thecursor is currently located.NOTE Not all key sequences are available in each screen.Using and Configuring the <strong>TN</strong> <strong>Client</strong>This section contains information about the following:
48 <strong>PSC</strong> <strong>300</strong>-<strong>Series</strong> <strong>Wavelink</strong> <strong>TN</strong> <strong>Client</strong> User’s <strong>Guide</strong>• Launching the <strong>TN</strong> <strong>Client</strong>.• Connecting to a host.• Disconnecting from a Telnet session.• Exiting the <strong>TN</strong> <strong>Client</strong>.• Working with multiple Telnet sessions.Launching the <strong>TN</strong> <strong>Client</strong>The <strong>Wavelink</strong> <strong>TN</strong> <strong>Client</strong> launches from the Avalanche Enabler. Dependingon how you have configured the Avalanche Enabler, the <strong>Wavelink</strong> <strong>TN</strong> <strong>Client</strong>will launch using one of the following methods:• Automatically. If you have configured the Avalanche Enabler to disallowusers to access the Avalanche Enabler application menu, then the <strong>TN</strong><strong>Client</strong> will automatically launch once the Avalanche Enabler has started.• Manually. If you have configured the Avalanche Enabler to allow usersaccess to the Avalanche Enabler application menu, then a user at themobile device can access the menu, select the <strong>TN</strong> <strong>Client</strong>, and press Enterto launch the <strong>TN</strong> <strong>Client</strong>.NOTE For more information about configuring the Avalanche Enabler, see the<strong>PSC</strong> <strong>300</strong>-<strong>Series</strong> Avalanche Enabler User’s <strong>Guide</strong>.When the <strong>Wavelink</strong> <strong>TN</strong> <strong>Client</strong> launches, it displays the default screen, whichindicates that there is currently no host connection and that the user shouldpress the Enter key to connect.Connecting to a HostHost profiles allow the <strong>TN</strong> <strong>Client</strong> to easily initiate Telnet sessions with hosts.To initiate a Telnet session with a host:1 At the <strong>TN</strong> <strong>Client</strong> default screen, press Enter.If the <strong>TN</strong> <strong>Client</strong> on the mobile device is configured with only one hostprofile, the mobile device automatically attempts to connect to that host.
Chapter 4: Using the <strong>Wavelink</strong> <strong>TN</strong> <strong>Client</strong> 49If the <strong>TN</strong> <strong>Client</strong> is configured with more than one host profile, the hostselection (SELECT HOST) menu appears.2 In the host selection menu, use the arrow keys to select the host withwhich you want to establish a Telnet session.3 Press Enter.The <strong>TN</strong> <strong>Client</strong> attempts to establish a Telnet session with the host.Disconnecting/Terminating a SessionIf you are no longer using a Telnet session, you can disconnect the session.To terminate a Telnet session:1 Press ALT Z.A message appears that asks if you want to terminate the session.2 Press Y.The Telnet session with the host is terminated.3 Press any key to return to the <strong>TN</strong> <strong>Client</strong> default screen.Working with Multiple Telnet SessionsThis section covers the following:• Initiating multiple sessions• Switching between active sessions• Disconnecting a sessionConfiguring the <strong>TN</strong> <strong>Client</strong> for Multiple SessionsThe <strong>TN</strong> <strong>Client</strong> supports up to four simultaneous Telnet sessions. The defaultconfiguration for the <strong>TN</strong> <strong>Client</strong>, however, only allows one session.You must access the Configuration Manager to configure the <strong>TN</strong> <strong>Client</strong> tosupport more than one Telnet session.To configure the <strong>TN</strong> <strong>Client</strong> for multiple Telnet sessions:1 Launch Avalanche Manager and connect to the Avalanche Agent.
50 <strong>PSC</strong> <strong>300</strong>-<strong>Series</strong> <strong>Wavelink</strong> <strong>TN</strong> <strong>Client</strong> User’s <strong>Guide</strong>2 In the Avalanche Agents tree, locate and right-click the <strong>TN</strong> <strong>Client</strong> softwarepackage.A menu list appears.3 From the menu list, select Configure Package > EmulationParameters, as shown in Figure 4-1.Figure 4-1. Configuring the <strong>TN</strong> <strong>Client</strong> for Multiple SessionsThe Configuration Manager appears.4 In Configuration Manager, select the Emulation > Common > Number ofSessions parameter, as shown in Figure 4-2.
Chapter 4: Using the <strong>Wavelink</strong> <strong>TN</strong> <strong>Client</strong> 51Figure 4-2. Selecting to Configure the Number of Sessions5 Double-click the parameter.The Number of Sessions dialog box appears.6 In the Enter the number of sessions text box, type the number ofsimultaneous Telnet sessions (up to 4) that the <strong>TN</strong> <strong>Client</strong> is permitted, asshown in Figure 4-3.Figure 4-3. Configuring the Maximum Number of Simultaneous Sessions7 Click OK.The Number of Sessions dialog box closes.8 In Configuration Manager, click the Save icon button.9 Close Configuration Manager.10 In Avalanche Manager, ensure that you have enabled the <strong>TN</strong> <strong>Client</strong>software package.
52 <strong>PSC</strong> <strong>300</strong>-<strong>Series</strong> <strong>Wavelink</strong> <strong>TN</strong> <strong>Client</strong> User’s <strong>Guide</strong>11 Update the client.The new configuration is downloaded to the client.NOTE For more information about updating Avalanche clients, seePerforming Updates on page 53. More information is provided in the <strong>PSC</strong> <strong>300</strong>-<strong>Series</strong> Avalanche Enabler User’s <strong>Guide</strong>.Initiating a New SessionIf the <strong>TN</strong> <strong>Client</strong> on the mobile device is configured to support multiplesessions, you can initiate a new session with the same host or with a differenthost.To initiate a new session:1 Press ALT S or ALT N to cycle through the available sessions.As you cycle through the sessions, text at the bottom of the screenindicates the session number.2 When you find an unused session, press Enter.If the <strong>TN</strong> <strong>Client</strong> on the mobile device is configured with only one hostprofile, the mobile device automatically attempts to connect to that host.If the <strong>TN</strong> <strong>Client</strong> is configured with more than one host profile, the hostselection (SELECT HOST) menu appears.3 In the host selection menu, use the arrow keys to select the host withwhich you want to establish a Telnet session.4 Press Enter.The <strong>TN</strong> <strong>Client</strong> attempts to establish a Telnet session with the host.Switching Between Active SectionsUse the ALT S or ALT N key sequences to cycle between sessions.
Appendix A: Managing <strong>Client</strong>s with Avalanche Manager 53Appendix A: Managing <strong>Client</strong>s withAvalanche ManagerThis section provides information about using Avalanche Manager tomanage mobile devices, including:• Performing updates• Using network profiles• Using Avalanche client controls• Installing and removing Avalanche software packagesNOTE The steps in this section were developed with Avalanche Manager 3.3.2and a <strong>PSC</strong> Falcon 345. Screens and steps may vary, depending on the versionof Avalanche Manager that you are using.NOTE For more information about using Avalanche Manager, see the onlinehelp, which is available in the Help menu of the Avalanche ManagementConsole.Performing UpdatesThis section provides information about client-side Avalanche updates.This section discusses the following:• About Updates• Performing Serial Updates• Performing RF UpdatesAbout UpdatesUpdates are the method Avalanche Manager uses to deliver new informationto Avalanche clients (mobile devices with the Avalanche Enabler). The typeof information that is delivered to a mobile device through an update might
54 <strong>PSC</strong> <strong>300</strong>-<strong>Series</strong> <strong>Wavelink</strong> <strong>TN</strong> <strong>Client</strong> User’s <strong>Guide</strong>be a configuration change, an application (software package), or a change toan application (for example, a new configuration for the application or acommand to remove the application) that has already been installed on themobile device.Updates are configured at the Management Console and then pushed to theAvalanche Agent. The update is then downloaded to the appropriate mobiledevice(s) over a serial or RF connection.Update MediaAvalanche Manager can download updates to clients over a serial connectionor over an RF connection. If the Enabler is not configured to update over aserial connection or the serial port is not configured in Avalanche Manager,then only the RF connection will be used.By default, the Avalanche Enabler will attempt to download updates over aserial connection. If a serial connection does not exist between the AvalancheAgent and the mobile device, the Avalanche Enabler will attempt to use theRF network to communicate with Avalanche Manager.Preparing for Serial UpdatesTo perform an update over a serial connection, you must prepare the mobiledevice and the Avalanche Manager.Preparing Avalanche Manager for Serial UpdatesYou must configure Avalanche Manager to use the serial port that isconnected to the mobile device cradle.NOTE Use the serial port on the system that hosts the Avalanche Agent. TheAvalanche Management Console and the Avalanche Agent are separatesoftware components, and they can be installed on separate host systems.To configure Avalanche Manager to use the serial port:1 Ensure that no other applications have control of the serial port on the hostsystem.
Appendix A: Managing <strong>Client</strong>s with Avalanche Manager 55NOTE Windows applications (for example, Microsoft ActiveSync) can takeownership of a COM port. You will need to ensure that the COM port that isconnected to the mobile device is free for Avalanche Manager to takeownership of it.2 Launch the Avalanche Management Console and connect to theAvalanche Agent.3 Expand the Avalanche Agents tree.4 In the Avalanche Agents tree, locate and right-click Serial Ports.A menu list appears.5 From the menu list, select Auto Detect Available Serial Ports, as shown inFigure A-1.Figure A-1. Configuring Serial Ports in Avalanche ManagerAvalanche Manager finds and takes ownership of the available serial portson the system that hosts the Avalanche Agent.6 In the Avalanche Agents tree, expand Serial Ports.7 Ensure that the serial port that is connected to the mobile device is shownin the list.Preparing the Mobile Device for Serial UpdatesYou must prepare the mobile device, before you can perform an update overa serial connection.
56 <strong>PSC</strong> <strong>300</strong>-<strong>Series</strong> <strong>Wavelink</strong> <strong>TN</strong> <strong>Client</strong> User’s <strong>Guide</strong>To prepare the mobile device for serial updates:1 Place the mobile device in the appropriate cradle.2 Connect the device cradle to the system that hosts the Avalanche Agent.NOTE Ensure that you are using a null modem cable.he mobile device is now ready to receive updates from the AvalancheManager.Preparing for RF UpdatesYou can force updates down to an Avalanche client over an RF connectionbetween the mobile device and the Avalanche Agent.The following is a list of guidelines consider, to ensure communicationbetween the mobile device and the Avalanche Agent:• Ensure that the Avalanche Agent and the mobile device have valid IPaddresses. (If you are using DHCP or BOOTP, ensure that they cancommunicate properly with the DHCP/BOOTP server and that the IPparameters the server is serving are correct.)• Ensure that the mobile device is configured with the correct IP address ofthe Avalanche Manager.• Ensure that the mobile device is configured with the correct wirelessparameters (ESSID and encryption method and keys).• Ensure that any firewall service on the network allows Avalanche traffic.(Avalanche Manager communicates on TCP port 1779.)• If the mobile device is on a different IP network than the Avalanche Agent,ensure that the Avalanche Agent and the Avalanche client are configuredwith a valid gateway that provides a valid route to the other network.Performing the UpdateThe Avalanche Enabler automatically communicates with the AvalancheManager and checks for available Avalanche updates, when the AvalancheEnabler launches on the mobile device.
Appendix A: Managing <strong>Client</strong>s with Avalanche Manager 57You can also use a command at the DOS prompt that momentarily launchesan Avalanche Enabler utility that forces the mobile device to communicatewith the Avalanche Manager and check for updates.To check for available Avalanche updates from the mobile device:1 On the mobile device, access the DOS prompt.2 Change the directory to C:\AVA.3 At C:\AVA, type “a”.4 Press ENTER.The Avalanche Enabler launches, attempts to obtain an IP address (if theAvalanche Enabler is configured for BOOTP/DHCP), and then contactsthe Avalanche Manager and checks for updates. Any updates that areavailable on the Avalanche Manager are downloaded to the mobile device.After the updates are complete, you are returned to the DOS prompt.Using Network ProfilesThis section discusses configuring and deploying Avalanche network profilesto Avalanche clients.About Network ProfilesA network profile is a file that can be downloaded to clients. The file providesconfiguration information that the Avalanche Enabler uses to properlyconfigure the network settings of the client. You can use a network profile toprovide an Avalanche client with the following settings:• IP parameters (including static or dynamic address assignment, subnetmask, DNS servers, WINS servers, and default gateway)• the IP address of the Avalanche Manager that manages the mobile device• the ESSID of the wireless network• WEP key settings for the wireless network
58 <strong>PSC</strong> <strong>300</strong>-<strong>Series</strong> <strong>Wavelink</strong> <strong>TN</strong> <strong>Client</strong> User’s <strong>Guide</strong>Creating and Enabling a Network ProfileBefore you can deploy a network profile to clients, you must create thenetwork profile in Avalanche Manager.To create, configure, and enable a new network profile:1 Launch the Avalanche Management Console and connect to theAvalanche Agent.2 In the Avalanche Agents tree, locate and right-click Network Profiles.A menu list appears.3 Select New Network Profile, as shown in Figure A-2.Figure A-2. Creating a New Network ProfileThe Network Profile Name dialog box appears.4 In the Network Profile Name dialog box, type a name for the networkprofile, as shown in Figure A-3.
Appendix A: Managing <strong>Client</strong>s with Avalanche Manager 59Figure A-3. Naming the Network Profile5 Click OK.The network profile is created and now appears in the List View of theManagement Console beneath Network Profiles.6 Locate and right-click the new network profile.A menu list appears.7 Select Settings..., as shown in Figure A-4.Figure A-4. Selecting to Configure the Settings of a Network Profile
60 <strong>PSC</strong> <strong>300</strong>-<strong>Series</strong> <strong>Wavelink</strong> <strong>TN</strong> <strong>Client</strong> User’s <strong>Guide</strong>The Network Profile Settings dialog box for the network profile appears.8 Select and configure the Control tab in the Network Profile Settings dialogbox, as shown in Figure A-5.Figure A-5. Configuring the Network Profile Settings Control TabNOTE For more information about the Control tab in the Network ProfileSettings dialog box, see the Managing <strong>Client</strong>s > Configuring a Network Profilesection of the online help in the Management Console.9 Select and configure the Routing tab in the Network Profile Settings dialogbox, as shown in Figure A-6.
Appendix A: Managing <strong>Client</strong>s with Avalanche Manager 61Figure A-6. Configuring the Network Profile Settings Routing TabNOTE For more information about the Routing tab in the Network ProfileSettings dialog box, see the Managing <strong>Client</strong>s > Configuring a Network Profilesection of the online help in the Management Console.10 Select and configure the Security tab in the Network Profile Settings dialogbox, as shown in Figure A-7.
62 <strong>PSC</strong> <strong>300</strong>-<strong>Series</strong> <strong>Wavelink</strong> <strong>TN</strong> <strong>Client</strong> User’s <strong>Guide</strong>Figure A-7. Configuring the Network Profile Settings Security TabNOTE For more information about the Security tab in the Network ProfileSettings dialog box, see the Managing <strong>Client</strong>s > Configuring a Network Profilesection of the online help in the Management Console.11 After you have configured the various tabs in the Network Profile Settingsdialog box, click OK.The network profile settings are saved and the Network Profile Settingsdialog box closes.The new network profile now appears in the Avalanche Agents tree of theManagement Console beneath Network Profiles.
Appendix A: Managing <strong>Client</strong>s with Avalanche Manager 6312 In the Avalanche Agents tree, locate and right-click the new networkprofile.A menu list appears.13 From the menu list, select Enable Network Profile, as shown inFigure A-8.Figure A-8. Enabling a Network Profile14 Right-click the new network profile again.A menu list appears.15 From the menu list, select Set as Default Profile, as shown in Figure A-9.
64 <strong>PSC</strong> <strong>300</strong>-<strong>Series</strong> <strong>Wavelink</strong> <strong>TN</strong> <strong>Client</strong> User’s <strong>Guide</strong>Figure A-9. Setting the Default Network ProfileThe network profile is now ready to be deployed to Avalanche clients.Deploying a Network ProfileA network profile is a configuration file that is deployed to an Avalancheclient through an update. Any time you create a new network profile ormodify an existing network profile, Avalanche clients must download thenew configuration file before they can use the parameters in the networkprofile.To download the network profile to an Avalanche client, update the client.This can be done over a serial or RF connection and can be initiated from theclient or from Avalanche Manager.NOTE For information about client-initiated updates, see Performing Updateson page 53.
Appendix A: Managing <strong>Client</strong>s with Avalanche Manager 65Using <strong>Client</strong> ControlsThis section discusses accessing and using the Avalanche <strong>Client</strong> Controls dialogbox to manage clients.About Avalanche <strong>Client</strong> ControlsThe Avalanche <strong>Client</strong> Controls dialog box allows you to manage Avalancheclients from the Avalanche Management Console. <strong>Client</strong> controls allow youto perform the following tasks:• Edit the terminal ID of a client• Delete orphan packages on the clientAccessing <strong>Client</strong> ControlsThe Avalanche <strong>Client</strong> Controls dialog box is accessible on a per-client basis.To access the Avalanche <strong>Client</strong> Controls dialog box for a client:1 Launch Management Console and connect to the Agent.2 In the List View of Management Console, locate and right-click the clientthat you want to manage.A menu list appears.3 From the menu list, select <strong>Client</strong> Settings..., as shown in Figure A-10.Figure A-10. Accessing <strong>Client</strong> Settings
66 <strong>PSC</strong> <strong>300</strong>-<strong>Series</strong> <strong>Wavelink</strong> <strong>TN</strong> <strong>Client</strong> User’s <strong>Guide</strong>The Avalanche <strong>Client</strong> Controls dialog box for the Avalanche client appears.About Avalanche <strong>Client</strong> ControlsThe Avalanche <strong>Client</strong> Controls dialog box has two tabs:• Control. This tab allows you to perform many of the control functions forthe client, such as forcing an update or pinging the client. This tab containsinformation about the client, including the client’s IP and MAC addresses,as well as the software packages that are installed on the mobile device.• Properties. This tab displays the Avalanche properties that are associatedwith the mobile device.Control TabFigure A-11 shows the Control tab of the Avalanche <strong>Client</strong> Controls dialog box.
Appendix A: Managing <strong>Client</strong>s with Avalanche Manager 67Figure A-11. Control Tab of Avalanche <strong>Client</strong> Controls Dialog BoxThe following list describes the features of the Control tab in the Avalanche<strong>Client</strong> Controls dialog box:MAC AddressIP AddressLast Known APModelShows the MAC address of the mobile device.Shows the IP address of the mobile device.Displays the last AP with which the mobile devicewas associated. (Currently, this feature is notimplemented in Avalanche Manager and will alwaysdisplay “Unknown”.Displays the name of the Enabler that is installed onthe mobile device.
68 <strong>PSC</strong> <strong>300</strong>-<strong>Series</strong> <strong>Wavelink</strong> <strong>TN</strong> <strong>Client</strong> User’s <strong>Guide</strong>KeyboardDisplay Size (r/c)Terminal IDEdit Terminal IDPing <strong>Client</strong>Send Text MessageUpdate NowAllow user to overrideUpdate NowDisplays the type of keyboard on the mobile device.Indicates the display size of the mobile device’sscreen in rows and columns.Indicates the Avalanche Manager ID of the mobiledevice.Allows you to change the Avalanche ID of themobile device.Allows you to send a TCP (ICMP) ping to verify IPconnectivity to the mobile device. (Unavailable for<strong>PSC</strong> <strong>300</strong>-series devices.)Allows you to send a text message to the mobiledevice. (Unavailable for <strong>PSC</strong> <strong>300</strong>-series devices.)Enables you to force the mobile device to check forupdates. (Unavailable for <strong>PSC</strong> <strong>300</strong>-series devices.)Allows you to enable/disable users at the mobiledevice to override an update. (Not a functionalparameter for <strong>PSC</strong> <strong>300</strong>-series devices.)Delete Orphan Packages Causes the mobile device to delete softwarepackages that have been flagged as orphanpackages. (For information about Avalanchesoftware packages, see Using Software Packages onpage 71.)Current ActivityControl StatusSoftware PackagesCloseIndicates the current communication activitybetween the Agent and the mobile device.Indicates the current communication activity of theAgent to the mobile device.Indicates the Avalanche software packages that areinstalled on the mobile device. (For informationabout Avalanche software packages, see UsingSoftware Packages on page 71.)Closes the Avalanche <strong>Client</strong> Controls dialog box.
Appendix A: Managing <strong>Client</strong>s with Avalanche Manager 69Properties TabThe Properties tab in the Avalanche <strong>Client</strong> Controls dialog box displays theAvalanche-related properties that you have assigned the mobile device. Theproperties tab also allows you to add or remove properties.Figure A-12 shows the Properties tab in the Avalanche <strong>Client</strong> Controls dialogbox.Figure A-12. Avalanche <strong>Client</strong> Controls Properties TabThe following list describes the options in the Properties tab:PropertyValueIndicates the property.Indicates the value of the property.
70 <strong>PSC</strong> <strong>300</strong>-<strong>Series</strong> <strong>Wavelink</strong> <strong>TN</strong> <strong>Client</strong> User’s <strong>Guide</strong>ChangeableChange PendingAdd PropertyDelete PropertyApply ChangesDiscard ChangesCurrent ActivityControl StatusCloseIndicates whether you can modify the value of theproperty.Indicates whether the value of the property has beenchanged on the mobile device.Allows you to add a custom property to the mobiledevice.Allows you to delete a custom property from themobile device.Applies the changes that you have made in theProperties tab to the Agent. (You still need toperform an update to apply the changes to themobile device.)Discards the changes that you have made in theProperties tab.Indicates the current communication activitybetween the mobile device and the Agent.Indicates the current communication activity of theAgent to the mobile device.Closes the Avalanche <strong>Client</strong> Controls dialog box.Editing the Terminal ID of a <strong>Client</strong>The terminal ID of a client is a value that Avalanche Manager associates withthe mobile device. The terminal ID can be used to provide a unique identifierfor certain systems when other parameters are not available or areinsufficient.You can edit the terminal ID of a client from the Avalanche <strong>Client</strong> Controlsdialog box.To change the terminal ID of a client:1 In the Management Console, access the Avalanche <strong>Client</strong> Controls dialogbox for the mobile device.2 Select the Control tab in the Avalanche <strong>Client</strong> Controls dialog box.3 Click Edit Terminal ID.
Appendix A: Managing <strong>Client</strong>s with Avalanche Manager 71The Edit Terminal ID dialog box appears.4 In the New Terminal ID text box, type the new terminal ID for the client, asshown in Figure A-13.Figure A-13. Assigning a New Terminal ID5 Click OK.6 Close the Avalanche <strong>Client</strong> Controls dialog box.The List View in the Management Console displays the current terminalID of the client and the new terminal ID in parenthesis, as shown in FigureA-14.Figure A-14. Terminal ID Change Pending7 Update the client to apply the change.After the update, the List View in the Management Console displays thenew terminal ID.Using Software PackagesSoftware packages are specially bundled applications that can be deployedand installed on mobile devices through Avalanche Manager.
72 <strong>PSC</strong> <strong>300</strong>-<strong>Series</strong> <strong>Wavelink</strong> <strong>TN</strong> <strong>Client</strong> User’s <strong>Guide</strong>This section uses the Hello World application to provide an example ofperforming the following tasks:• Installing software packages in Avalanche Manager.• Deploying software packages to mobile devices.• Removing software packages from mobile devices.Installing Software Packages in Avalanche ManagerBefore you can deploy a software package to mobile devices, you must installthe software package in Avalanche Manager. Avalanche software packagesare denoted with an AVA file extension.NOTE The Avalanche Package Builder allows you to bundle an applicationinto a software package. For more information about Avalanche PackageBuilder, see your <strong>Wavelink</strong> sales representative.Installing a software package in Avalanche Manager and preparing it to bedeployed to clients involves the following tasks:1 Create a software collection in Avalanche Manager that will house thesoftware package.2 Install the software package.3 Create a selection criteria for the software package.4 Enable the software package.To install a software package in Avalanche Manager:1 Ensure that the software package is in directory that you can access fromthe system that hosts the Management Console.2 Launch the Management Console and connect to the Agent.3 In the Avalanche Agents tree, right-click Software Collections.A menu list appears.4 From the menu list, select New Software Collection, as shown in Figure A-15.
Appendix A: Managing <strong>Client</strong>s with Avalanche Manager 73Figure A-15. Creating a New Software CollectionThe Software Collection Name dialog box appears.5 In the Software Collection Name dialog box, type a name for the softwarecollection, as shown in Figure A-16.Figure A-16. Naming a Software Collection6 Click OK.The new software collection now appears beneath Software Collections inthe Avalanche Agents tree.7 From the Management Console Software Management menu, selectInstall Software Package....The Install Software Package Wizard launches and displays the Select theAvalanche package to install dialog box.
74 <strong>PSC</strong> <strong>300</strong>-<strong>Series</strong> <strong>Wavelink</strong> <strong>TN</strong> <strong>Client</strong> User’s <strong>Guide</strong>8 Click the ... icon button.The Select the path dialog box appears.9 Use the browse feature of the Select the path dialog box to locate theAvalanche software package that you want to install.10 After you have located and selected the software package, click Select.The path to the package now appears in the Select the Avalanche package toinstall dialog box.11 Click Next.The Install Software Package Wizard displays the License Agreement dialogbox.12 Select the Yes, I agree option button.13 Click Next.The Install Software Package Wizard displays the Select the softwarecollection dialog box.14 From the list of software collections in the Select the software collectiondialog box, select the software collection in which you want to install thesoftware package, as shown in Figure A-17.
Appendix A: Managing <strong>Client</strong>s with Avalanche Manager 75Figure A-17. Selecting the Software Collection15 Click Next.The Installing the Avalanche package dialog box displays the installationprocess.16 After the software package is installed, click Finish.The software package now appears in the appropriate software collectionin the Avalanche Agents tree of the Management Console, as shown inFigure A-18.
76 <strong>PSC</strong> <strong>300</strong>-<strong>Series</strong> <strong>Wavelink</strong> <strong>TN</strong> <strong>Client</strong> User’s <strong>Guide</strong>Figure A-18. Software Package in Software Collection17 Right-click the software collection in which the software package islocated.A menu list appears.18 From the menu list, select Settings..., as shown in Figure A-19.Figure A-19. Selecting to Configure the Software Collection
Appendix A: Managing <strong>Client</strong>s with Avalanche Manager 77The Software Collection Settings dialog box for the software collectionappears.19 Use the Software Collection Settings dialog box to configure a selectioncriteria for the software collection.NOTE For more information about configuring selection criterion, seeManaging <strong>Client</strong>s > Selection Criteria in the Avalanche Manager online help.You can access the online help by selecting Help Topics from theAvalanche Management Console Help menu.Figure A-20 provides an example of the Software Collections Settings dialogbox.Figure A-20. Software Collection Settings Dialog Box20 Click Apply.The selection criteria is applied.
78 <strong>PSC</strong> <strong>300</strong>-<strong>Series</strong> <strong>Wavelink</strong> <strong>TN</strong> <strong>Client</strong> User’s <strong>Guide</strong>21 Click OK.The Software Collection Settings dialog box closes.22 In the Avalanche Agents tree, locate and right-click the software package.A menu list appears.23 From the menu list, select Configure Package.Another menu list appears that displays the configuration options for thepackage.NOTE The configuration options will vary between software package. Somesoftware packages (for example, the Hello World software package) do nothave any configurable parameters and the Configure Package option isnot available.24 From the menu list, select Enable Package, as shown in Figure A-21.Figure A-21. Enabling a Software Package
Appendix A: Managing <strong>Client</strong>s with Avalanche Manager 79The software package is enabled and ready to be deployed to Avalancheclients.Deploying Software PackagesTo deploy a software package to a mobile device, ensure that the softwarepackage is enabled, then update the mobile device.Removing Software PackagesThis sections provides information about the following topics:• orphan packages• removing orphan packages from clients• configuring Avalanche Manager to remove software packages from allclients.About Orphan PackagesBefore you can remove a software package from an Avalanche client, youmust orphan the software package.You can use one of the following methods to orphan a software package:• Disable the software package in Avalanche Manager.• Delete the software package from Avalanche Manager.A software package on a client is also considered an orphan package, if theAvalanche Agent to which the client reports has no record of the softwarepackage. For example, if you migrate a client to a new Avalanche Agent andthe client has a software package that is not installed on the new Agent, thenthe software package is considered an orphan.Removing an Orphan Package from a <strong>Client</strong>Removing an orphan package from a client requires the following tasks:1 Disable or delete the software package in Avalanche Manager.2 Use the Avalanche <strong>Client</strong> Controls dialog box to configure AvalancheManager to remove orphan packages from the client.3 Perform an update on the client.
80 <strong>PSC</strong> <strong>300</strong>-<strong>Series</strong> <strong>Wavelink</strong> <strong>TN</strong> <strong>Client</strong> User’s <strong>Guide</strong>To remove a software package from a client:1 Launch the Management Console and connect to the Agent.2 In the Avalanche Agents tree, locate and right-click the software package.A menu list appears.3 From the menu list, select Disable Package or Delete Package, asshown in Figure A-22.Figure A-22. Disable a Software PackageThe software package is disabled or deleted in Avalanche Manager.4 In the List View of the Management Console, locate and right-click theclient.A menu list appears.5 From the menu list, select Settings....The Avalanche <strong>Client</strong> Controls dialog box appears.6 In the Avalanche <strong>Client</strong> Controls box, enable the Delete Orphan Packagescheckbox, as shown in Figure A-23.
Appendix A: Managing <strong>Client</strong>s with Avalanche Manager 81Figure A-23. Selecting to Delete Orphan Packages from the <strong>Client</strong>7 Close the Avalanche <strong>Client</strong> Controls dialog box.8 Update the Avalanche client.The update removes the software package from the mobile device.Removing Orphan Packages from All <strong>Client</strong>sYou can configure Avalanche Manager to remove orphan packages from allAvalanche clients.Removing orphan packages from all clients requires the following tasks:1 Orphan the software package in Avalanche Manager.
82 <strong>PSC</strong> <strong>300</strong>-<strong>Series</strong> <strong>Wavelink</strong> <strong>TN</strong> <strong>Client</strong> User’s <strong>Guide</strong>2 Access the <strong>Client</strong> Update Controls dialog box and configure AvalancheManager to delete orphan packages from all clients.3 Update the clients.To configure Avalanche Manager to remove orphan packages from all clients:1 Launch the Management Console and connect to the Agent.2 In the Avalanche Agents tree, locate and right-click the software package.A menu list appears.3 From the menu list, select Disable Package or DeletePackage.The software package is deleted from Avalanche Manager andorphaned on the mobile device.4 Access the Management Console Tools menu and select <strong>Client</strong>Update Controls.The Avalanche <strong>Client</strong> Update Manager dialog box appears.5 In the Avalanche <strong>Client</strong> Update Manager dialog box, click Mark orphanpackages for deletion on all clients, as shown in Figure A-24.
Appendix A: Managing <strong>Client</strong>s with Avalanche Manager 83Figure A-24. Marking Orphan Packages for Deletion on All <strong>Client</strong>s6 Click OK.The Avalanche <strong>Client</strong> Update Manager dialog box closes, and all of theAvalanche clients are now set to delete orphan software packages.
84 <strong>PSC</strong> <strong>300</strong>-<strong>Series</strong> <strong>Wavelink</strong> <strong>TN</strong> <strong>Client</strong> User’s <strong>Guide</strong>
Appendix B: Keyboard Maps 85Appendix B: Keyboard MapsThis section provides the <strong>Wavelink</strong> <strong>TN</strong> <strong>Client</strong> keyboard maps for 25-key, 38-key, and 48-key <strong>PSC</strong> <strong>300</strong>-series mobile devices.<strong>PSC</strong> 325 Keyboard MapsThis section provides keyboard maps for <strong>PSC</strong> Falcon 325 mobile devices.<strong>PSC</strong> 325 Local Terminal FunctionsTable B-1 shows local terminal function key sequences for <strong>PSC</strong> 325 mobiledevices.Local FunctionKey SequenceConfig Hot Key Reconfigure Key Keyclick Silent Mode Status Screen Next Session Previous Session Diagnostics Test Hot Key Kill Session Full Screen Mode Message Recall Free Cursor Mode Table B-1: <strong>PSC</strong> 325 Local Terminal Functions<strong>PSC</strong> 325 5250 Emulation Key SequencesTable B-2 shows 5250 emulation keys sequences for <strong>PSC</strong> 325 mobile devices.5250 Key Key Sequence 5250 Key Key SequenceLeft Arrow F1 Right Arrow q Up Arrow F3 Table B-2: <strong>PSC</strong> 325 5250 Emulation Key Sequences
86 <strong>PSC</strong> <strong>300</strong>-<strong>Series</strong> <strong>Wavelink</strong> <strong>TN</strong> <strong>Client</strong> User’s <strong>Guide</strong>5250 Key Key Sequence 5250 Key Key Sequence F4 Tab F5 Backtab F6 Backspace F7 Delete F8 Send F9 Help F10 Dup F11 Field Exit F12 Roll Down F13 Roll Up F14 Home F15 Erase Input F16 Clear F17 Attention F18 Field Minus F19 Print F20 Reset F21 System Request F22 Full Screen Up F23 Full Screen Down F24 Full Screen Left Full Screen Right Insert Table B-2: <strong>PSC</strong> 325 5250 Emulation Key Sequences<strong>PSC</strong> 325 3270 Emulation Key SequencesTableB-3 shows 3270 emulation key sequences for <strong>PSC</strong> 325 mobile devices.3270 Key Key Sequence 3270 Key Key SequenceClear F1 Clear EOF F2 Enter F3 Field Mark F4 Table B-3: <strong>PSC</strong> 325 3270 Emulation Key Sequences
Appendix B: Keyboard Maps 873270 Key Key Sequence 3270 Key Key SequenceNew Line F5 Reset F6 Tab F7 PA1 F8 PA2 F9 PA3 F10 F11 F12 F13 F14 F15 F16 F17 F18 F19 F20 F21 F22 F23 F24 Table B-3: <strong>PSC</strong> 325 3270 Emulation Key Sequences<strong>PSC</strong> 325 VT Emulation Key SequencesTable B-4 shows VT emulation key sequences for <strong>PSC</strong> 325 mobile devices.VT Key Key Sequences VT Key Key SequenceLeft Arrow F1 Right Arrow F2 Up Arrow F3 Down Arrow F4 TabBacktab F6 Backspace F7 Enter F8 Table B-4: <strong>PSC</strong> 325 VT Emulation Key Sequences
88 <strong>PSC</strong> <strong>300</strong>-<strong>Series</strong> <strong>Wavelink</strong> <strong>TN</strong> <strong>Client</strong> User’s <strong>Guide</strong>VT Key Key Sequences VT Key Key SequenceReturn F9 Hard Reset F10 Find F11 Insert Here F12 Remove F13 Select F14 Previous Screen F15 Next Screen F16 F17 F18 F19 F20 Table B-4: <strong>PSC</strong> 325 VT Emulation Key Sequences<strong>PSC</strong> 325 HP Emulation Key SequencesTable B-5 shows HP emulation key sequences for <strong>PSC</strong> 325 mobile devices.HP Key Key Sequence HP Key Key SequenceLeft Arrow F1 Right Arrow F2 Up Arrow F3 Down Arrow F4 Tab F5 Backtab F6 Backspace F7 Delete F8 Enter ReturnHard Reset Insert Line Insert Character Delete Character Delete Line Table B-5: <strong>PSC</strong> 325 HP Emulation Key Sequences
Appendix B: Keyboard Maps 89HP Key Key Sequence HP Key Key SequencePrevious Screen Next Screen Table B-5: <strong>PSC</strong> 325 HP Emulation Key Sequences25-Key <strong>PSC</strong> 335/345 Keyboard MapsThis section provides key maps for 25-key <strong>PSC</strong> 335/345 mobile devices25-Key <strong>PSC</strong> 335/345 5250 Emulation Key SequencesTable B-6 shows 5250 emulation key sequences for 25-key <strong>PSC</strong> 335/345 mobiledevices.5250 Key Key Sequence 5250 Key Key SequenceLeft Arrow F1 Right Arrow F2 Up Arrow F3 Down Arrow F4 Tab F5 Backspace F6 Send F7 F8 F9 F10 Table B-6: 25-Key <strong>PSC</strong> 335/345 5250 Emulation Key Sequences25-Key <strong>PSC</strong> 335/345 3270 Emulation Key SequencesTable B-7 shows 3270 emulation key sequences for 25-key <strong>PSC</strong> 335/345 mobiledevices.3270 Key Key Sequence 3270 Key Key SequenceClear F1 Enter F2 F3F4Table B-7: 25-Key <strong>PSC</strong> 335/345 3270 Emulation Key Sequences
90 <strong>PSC</strong> <strong>300</strong>-<strong>Series</strong> <strong>Wavelink</strong> <strong>TN</strong> <strong>Client</strong> User’s <strong>Guide</strong>3270 Key Key Sequence 3270 Key Key SequenceF5F6 F7 F8 F9 F10 Table B-7: 25-Key <strong>PSC</strong> 335/345 3270 Emulation Key Sequences25-Key <strong>PSC</strong> 335/345 VT Emulation Key SequencesTable B-8 shows VT emulation key sequences for 25-key <strong>PSC</strong> 335/345 mobiledevices.VT Key Key Sequence VT Key Key SequenceLeft Arrow F1 Right Arrow F2 Up Arrow F3 Down Arrow F4 TabBacktab F6 Backspace F7 Return F8 F9 F10 Table B-8: 25-Key <strong>PSC</strong> 335/345 VT Emulation Key Sequences25-Key <strong>PSC</strong> 335/345 HP Emulation Key SequencesTable B-9 shows HP emulation key sequences for 25-key <strong>PSC</strong> 335/345 mobiledevices.HP Key Key Sequence HP Key Key SequenceLeft Arrow F1 Right Arrow F2 Up Arrow F3 Down Arrow F4 Table B-9: 25-Key <strong>PSC</strong> 335/345 HP Emulation Key Sequences
Appendix B: Keyboard Maps 91HP Key Key Sequence HP Key Key SequenceTab F5 Backspace F6 Return Enter> F7 F8 Table B-9: 25-Key <strong>PSC</strong> 335/345 HP Emulation Key Sequences38-Key <strong>PSC</strong> 335/345 Keyboard MapsThis section provides keyboard maps for 38-key <strong>PSC</strong> 335/345 mobile devices.38-Key <strong>PSC</strong> 335/345 5250 Emulation Key SequencesTable B-10 shows 5250 emulation key sequences for 38-key <strong>PSC</strong> 335/345mobile devices.5250 Key Key Sequence 5250 Key Key SequencesLeft Arrow F1 Right Arrow F2 Up Arrow F3 Down Arrow F4 Tab F5 Backtab F6 Backspace F7 Delete F8 Send F9 Help F10 Dup F21 Field Exit F22 Roll Down F23 Roll Up F24 Home< Erase Input Clear Attention Field Minus Table B-10: 38-Key <strong>PSC</strong> 335/345 5250 Emulation Key Sequences
92 <strong>PSC</strong> <strong>300</strong>-<strong>Series</strong> <strong>Wavelink</strong> <strong>TN</strong> <strong>Client</strong> User’s <strong>Guide</strong>5250 Key Key Sequence 5250 Key Key SequencesPrint Reset System Request Table B-10: 38-Key <strong>PSC</strong> 335/345 5250 Emulation Key Sequences38-Key <strong>PSC</strong> 335/345 3270 Emulation Key SequencesTable B-11 shows 3270 emulation key sequences for 38-key <strong>PSC</strong> 335/345mobile devices.3270 Key Key Sequence 3270 Key Key SequencesClear F1 Clear EOF F2 Enter F3 Field Mark F4 Reset F5 Tab F6 PA2 F7 PA3 F8 F9 F10 F21 F22 F23 F24 Table B-11: 38-Key <strong>PSC</strong> 335/345 3270 Emulation Key Sequences38-Key <strong>PSC</strong> 335/345 VT Emulation Key SequencesTable B-12 shows VT emulation key sequences for 38-key <strong>PSC</strong> 335/345 mobiledevices.VT Key Key Sequence VT Key Key SequencesLeft Arrow F1 Right Arrow F2 Up Arrow F3 Table B-12: 38-Key <strong>PSC</strong> 335/345 VT Emulation Key Sequences
Appendix B: Keyboard Maps 93VT Key Key Sequence VT Key Key SequencesDown Arrow F4 TabBacktab F6 Backspace F7 Return F8 F9 F10 Table B-12: 38-Key <strong>PSC</strong> 335/345 VT Emulation Key Sequences38-Key <strong>PSC</strong> 335/345 HP Emulation Key SequencesTable B-13 shows HP emulation key sequences for 38-key <strong>PSC</strong> 335/345 mobiledevices.HP Key Key Sequence HP Key Key SequencesLeft Arrow F1 Right Arrow F2 Up Arrow F3 Down Arrow F4 Tab F5 Backtab F6 Backspace F7 Return F8 Table B-13: 38-Key <strong>PSC</strong> 335/345 HP Emulation Key Sequences48-Key <strong>PSC</strong> 345 Keyboard MapsThis section provides keyboard maps for 48-key <strong>PSC</strong> 345 mobile devices.
94 <strong>PSC</strong> <strong>300</strong>-<strong>Series</strong> <strong>Wavelink</strong> <strong>TN</strong> <strong>Client</strong> User’s <strong>Guide</strong>48-Key <strong>PSC</strong> 345 Local Terminal FunctionsTable B-14 shows local terminal function key sequences for 48-key <strong>PSC</strong> 345mobile devices.Local FunctionKey SequenceConfig Hot Key Reconfigure Key Keyclick Silent Mode Status Screen Next Session Previous Session Diagnostics Test Hot Key Kill Session Full Screen Mode Message Recall Free Cursor Mode Table B-14: 48-Key <strong>PSC</strong> 345 Local Terminal Functions48-Key <strong>PSC</strong> 345 5250 Emulation KeysTable B-15 shows 5250 emulation key sequences for 48-key <strong>PSC</strong> 345 mobiledevices.5250 Key Key Sequence 5250 Key Key SequencesLeft Arrow F1 Right Arrow F2 Up Arrow F3 Down Arrow F4 Tab F5 Backtab F6 Backspace F7 Delete F8 Send F9 Help F10 Table B-15: 48-Key <strong>PSC</strong> 345 5250 Emulation Key Sequences
Appendix B: Keyboard Maps 955250 Key Key Sequence 5250 Key Key SequencesDup F11 Field Exit F12 Roll Down F13 Roll Up F14 Home F15 Erase Input F16 Clear F17 Attention F18 Field Minus F19 Print F20 Reset F21 System Request F22 Full Screen Up F23 Full ScreenDown F24 Full Screen LeftFull ScreenRightInsert Table B-15: 48-Key <strong>PSC</strong> 345 5250 Emulation Key Sequences48-Key <strong>PSC</strong> 345 3270 Emulation Key SequencesTable B-16 shows 3270 emulation key sequences for 48-key <strong>PSC</strong> 345 mobiledevices.3270 Key Key Sequence 3270 Key Key SequencesClear F1 Clear EOF F2 Enter F3 Field Mark F4 New Line F5 Reset F6 Tab F7 PA1 F8 PA2 F9 Table B-16: 48-Key <strong>PSC</strong> 345 3270 Emulation Key Sequences
96 <strong>PSC</strong> <strong>300</strong>-<strong>Series</strong> <strong>Wavelink</strong> <strong>TN</strong> <strong>Client</strong> User’s <strong>Guide</strong>3270 Key Key Sequence 3270 Key Key SequencesPA3 F10 F11 F12 F13 F14 F15 F16 F17 F18 F19 F20 F21 F22 F23 F24 Table B-16: 48-Key <strong>PSC</strong> 345 3270 Emulation Key Sequences48-Key <strong>PSC</strong> 345 VT Emulation Key SequencesTable B-17 showns VT emulation key sequences for 48-key <strong>PSC</strong> 345 mobiledevices.VT Key Key Sequence VT Key Key SequencesLeft Arrow F1 Right Arrow F2 Up Arrow F3 Down Arrow F4 Tab F6 Backtab F7 Backspace F8 Enter F9 Return F10 Hard Reset F11 Find F12 Insert Here F13 Table B-17: 48-Key <strong>PSC</strong> 345 VT Emulation Key Sequences
Appendix B: Keyboard Maps 97VT Key Key Sequence VT Key Key SequencesRemove F14 Select F15 Previous Screen F16 Next Screen F17 F18 F19 F20 Table B-17: 48-Key <strong>PSC</strong> 345 VT Emulation Key Sequences48-Key <strong>PSC</strong> 345 HP Emulation Key SequencesTable B-18 showns HP emulation key sequences for 48-key <strong>PSC</strong> 345 mobiledevices.HP Key Key Sequence HP Key Key SequencesLeft Arrow F1 Right Arrow F2 Up Arrow F3 Down Arrow F4 Tab F5 Backtab F6 Backspace F7 Delete F8Enter ReturnHard Reset Insert Line Insert Character DeleteCharacter Delete Line Previous Screen Next Screen Table B-18: 48-Key <strong>PSC</strong> 345 HP Emulation Key Sequences
98 <strong>PSC</strong> <strong>300</strong>-<strong>Series</strong> <strong>Wavelink</strong> <strong>TN</strong> <strong>Client</strong> User’s <strong>Guide</strong>
Appendix C: Emulation Parameters 99Appendix C: Emulation ParametersThis section contains information about the <strong>TN</strong> <strong>Client</strong> emulation parametersthat you can modify using Configuration Manager, including descriptionsand possible values for each parameter.This section is divided into the following sub-sections:• COM port parameters• 5250/3270 Emulation parameters• Emulation parameters, including common, display, keyboard, sound, andprinting• VT and HP Emulation parameters• Scanner parametersCOM Port ParametersUse the COM port parameters in Configuration Manager to modify thesettings for the COM port of the mobile device.
100 <strong>PSC</strong> <strong>300</strong>-<strong>Series</strong> <strong>Wavelink</strong> <strong>TN</strong> <strong>Client</strong> User’s <strong>Guide</strong>The following list describes the COM port parameters that appear inConfiguration Manager:Com Port Baud RateThe baud rate of the COM port on the mobile device.Possible values: 12002400480096001920038400Default value: 9600Com Port Block DataSpecifies whether data should be held until the ComPort Data Timeout is reached before adding theblock of data to the keyboard buffer.Possible values:Default value:YesNoNoCom Port Data BitsThe number of data bits that the COM port on themobile device uses.Possible values: 78Default value: 8Com Port Data End Char Select the end character that indicates that datapreceding this character (and following the startcharacter) should be entered into the keyboardbuffer.Possible values: 0 - 255Default value: 3
Appendix C: Emulation Parameters 101Com Port Data EntryModeSpecifies how data sent through the COM port onthe mobile device is entered. If you select“keyboard”, each byte is entered as if it camethrough the keyboard. For 5250 emulation, there isan option to tag a field with an identifier incombination with setting the entry mode to ComEntry Field. With both of these set, data is onlyentered into the field with the data identifier and isfollowed with a field exit.Possible values:Default value:keyboardCom Entry FieldkeyboardCom Port Data StartCharSpecifies the start character to indicate that the datathat follows this character should be entered into thekeyboard buffer.Possible values:0 - 255 (decimal value)0 - FF (hex value)one alpha characterDefault value: 2Com Port DataTerminatorSpecifies the data terminator. You should only addthe terminator when using the start/end character toblock the data or when the Com Port Data Block isset to “Yes”. To add a terminator, enter the four hexdigitscan code of the key to be added after the COMdata is entered. To find the scan code of the desiredkey, use the diagnostics menu and select “KeyboardTest”. Make sure you are connected to the host withthe desired emulation type, since the key valuesactually change for the emulation type. Press thedesired key to display the key’s scan code.Example value: 3B00 (for F1)Default value: -
102 <strong>PSC</strong> <strong>300</strong>-<strong>Series</strong> <strong>Wavelink</strong> <strong>TN</strong> <strong>Client</strong> User’s <strong>Guide</strong>Com Port Data Timeout Specifies the amount of time (in milliseconds) thatthe terminal should wait for the next character formthe COM port, before the mobile device eitherdiscards the data it has received so far (if you areusing start and stop characters) or sending the datato the host (if you are blocking data).Possible values:0 - <strong>300</strong>0 (milliseconds)Default: 50Com Port Flow ControlSpecifies the type of flow control the COM port onthe mobile device uses.Possible values:Default value:SoftwareHardwareNoneNoneCom Port for IOSpecifies the COM port on the mobile device that isused for input/output (IO).Possible values: 12Default value: 1Com Port Ignore NullsSpecifies whether the COM port ignores nullcharacters, when using the COM port for scanning.Possible values:Default value:YesNoNo
Appendix C: Emulation Parameters 103Com Port IO Screen ID(5250/3270 Only)Specifies the screen identifier for the block data sentout of the COM port. The identifier needs to befound at the row and columns specified in the ComPort IO Screen Row and Com Port IO Screen ID Colparameters. The data is followed by a colon and asecond instance of the screen identifier.For example: OUTCOM:EXAMPLE:OUTCOMPossible values: Up to 10 alpha-numeric charactersDefault value: OUTCOMCom Port IO Screen IDCol(5250/3270 Only)Specifies the column on the display screen where theCom Port IO Screen ID will be found.Possible values: 1 - 80Default value: 1Com Port IO Screen IDRow(5250/3270 Only)Specifies the row on the display screen where theCom Port IO Screen ID will be found.Possible values: 1 - 24Default value: 3Com Port ParitySelect the parity that the COM port on the mobiledevice uses.Possible values:Default value:NoneOddEvenSpaceMarkNone
104 <strong>PSC</strong> <strong>300</strong>-<strong>Series</strong> <strong>Wavelink</strong> <strong>TN</strong> <strong>Client</strong> User’s <strong>Guide</strong>Com Port Parity MaskSpecifies the mark for the COM port parity. A maskcan be applied to each bye received through theCOM port. Setting the mask to FF will prevent thedata from being modified.Possible values:Default value:0 - 255 (decimal)0 - FF (hex)FFCom Port Stop BitsSpecifies the number of stop bits the COM port onthe mobile device uses.Possible values: 12Default value: 1Com Port Translate IOIndicates whether data passing through the COMport is translated from a two-digit hex value to asingle byte that contains the value of the two hexdigits. If you select “Yes”, data received from theCOM port will also be translated from a single valueto a two-digit hex value before it enter through thekeyboard buffer.Possible values:Default value:YesNoNo
Appendix C: Emulation Parameters 105Use Com Input/OutputSpecifies whether the COM port can be used for datainput/output. Selecting “auto” enables the COM portfor data entry when the terminal is in a cradle orattached to a charger.Possible values:Default value:YesNoAutoNoUse Com Start/EndCharactersSpecifies whether start and end characters are used.Only data between the start and end characters willbe entered into the keyboard buffer.Possible values:Default value:YesNoNoEmulation - 5250 and 3270 - 3270 ParametersUse the 3270 emulation parameters in Configuration Manager to configureparameters that are specific to 3270-type emulation.
106 <strong>PSC</strong> <strong>300</strong>-<strong>Series</strong> <strong>Wavelink</strong> <strong>TN</strong> <strong>Client</strong> User’s <strong>Guide</strong>The following list describes the 3270 emulation parameters that you canmodify with Configuration Manager:Clear Field On ScansSpecifies whether the mobile device erases thecontents of the current entry field before filling itwith scanned data.Possible values:Default value:YesNoYesTab on ScansSpecifies whether the mobile device uses a tab aftereach scan.Possible values:Default value:YesNoNoUnderscore 3270 FieldsSpecifies whether entry fields are delineated with anunderscore.Possible values:Default value:YesNoNo
Appendix C: Emulation Parameters 107Use Alt 3270 SystemRequestSpecifies whether <strong>TN</strong>3270 System Requests arecoded as Test-Requests. (By default, <strong>TN</strong>3270 SystemRequests are coded as Interrupt-Processes.)Possible values:Default value:YesNoNoUse LXE Coop RulesSpecifies whether emulation allows the 3270 entryfield to be an auto-send field (available as an LXEcooperative programming rule). 3270 emulationdoes not natively support this option.Possible values:Default value:YesNoNoEmulation - 5250 and 3270 - 5250 ParametersUse the 5250 emulation parameters in Configuration Manager to setparameters that are related to 5250-type emulation.
108 <strong>PSC</strong> <strong>300</strong>-<strong>Series</strong> <strong>Wavelink</strong> <strong>TN</strong> <strong>Client</strong> User’s <strong>Guide</strong>The following list describes the 5250 parameters that you can modify withConfiguration Manager:Enter Key SwappedSpecifies whether the ENTER key works as theAS400 Enter key and the Field Exit key is moved tothe previous Enter key location. By default, the Enterkey on mobile devices is set up as the Field Exit key.Possible values:Default value:YesNoNoScan In Fields OnlySpecifies whether the scanner stays even when thecursor is not on an input field. Note that this willaffect the scanning of AID keys when the cursor isnot on an input field.Possible values:Default value:EnableDisableDisableEmulation - 5250 and 3270 - CommonUse the common 5250 and 3270 emulation parameters in ConfigurationManager to set parameters that are common to 5250- and 3270-typeemulation.
Appendix C: Emulation Parameters 109The following list describes the common 5250/3270 emulation parameters thatyou can modify with Configuration Manager:Auto Reset DelaySpecifies the number of seconds to wait before themobile device sends a reset to the host when theReset Required parameter (see below) is set toNever.Possible values:0 - 5 (seconds)Default value: 2Disable Data IDsSpecifies whether to disable data identifiers. (Youmay want to disable data identifiers for emulationtypes that have screens that are not designed for usewith data identifiers, but may mistakenly processthem as such.Possible values:Default value:YesNoNoDisplay TruncateMessageSpecifies whether to display a message that lets theuser at the mobile device know that the bar code hasbeen truncated. (You only need to enable this valueif you have set the Oversize Scanning parameters to“Truncate”.)Possible values:Default value:YesNoYesEnable Free CursorSpecifies whether the user is allowed to enter “freecursor” mode, which lets the user move to protectedareas of the screen. Unless you are certain that noneof the host screens have a use for this feature, set theparameter to “Yes”.Possible values:Default value:YesNoYes
110 <strong>PSC</strong> <strong>300</strong>-<strong>Series</strong> <strong>Wavelink</strong> <strong>TN</strong> <strong>Client</strong> User’s <strong>Guide</strong>Host Message LineSpecifies the screen row that contains the hostmessages. (Set the value to “0” to have the mobiledevice ignore host messages.)Possible values: 0 - 24Default value : 24Oversize ScanningSpecifies how scanned data that is longer than theentry field is managed.Possible values:Do Not AllowSplit (between multiple entry fields)Truncate (to match the length of the field)Default value:Do Not AllowPrint End IdentifierSpecifies the identifier for the print end.Possible values:Default value:Up to 20 alpha-numericcharactersPRNPrint Escape CharacterSpecifies an escape character that is used to embedspecial values within a print screen.Possible values:0 - 255 (decimal)0 - FF (hex)one alpha-numeric characterDefault value:5C (hex), 92 (decimal), or \(character)
Appendix C: Emulation Parameters 111Print Identifier ColumnSpecifies the location (column) of the print startidentifier.Possible values: 1 - 80Default value: 1Print Identifier RowSpecifies the location (row) of the print startidentifier.Possible values: 1 - 24Default value: 3Print Start IdentifierSpecifies the identifier for the print start.Possible values: Up to 20 alpha-numeric charactersDefault value: PRN:Reset RequiredSpecifies when a reset is required. The reset occursafter the number of seconds specified in the AutoReset Delay parameter.Possible values: On ErrorsNeverOn All MessagesDefault value: On Errors
112 <strong>PSC</strong> <strong>300</strong>-<strong>Series</strong> <strong>Wavelink</strong> <strong>TN</strong> <strong>Client</strong> User’s <strong>Guide</strong>Retry Workstation ID Specifies whether to append a letter (starting with A)to the end of a workstation ID that is already in useon the host.Possible values: YesNoDefault value: NoUse Enter as ResetSpecifies whether the Enter key can be configured toalso work as the Reset key when the mobile device isin an error state.Possible values: YesNoDefault value: NoEmulation - CommonUse the common emulation parameters in Configuration Manager to modifyparameters that are common to all types of emulation (VT, HP, and 5250/3270).
Appendix C: Emulation Parameters 113The following list contains descriptions of the common emulation parametersthat Configuration Manager allows you to modify:Auto Connect SessionSpecifies whether the mobile device attempts toreconnect after a connection has closed.Possible values: YesNoDefault value: NoCaps LockSpecifies the initial keyboard mode. If you specify“Default”, the keyboard will default to the defaultmode for the emulation type. 5250/3270 emulationdefaults to Caps Lock On. VT/HP emulation defaultsto Caps Lock Off.Possible values: OnOffDefault value: DefaultKey MacrosSpecifies a key macro so that a key sequence isramped to perform a function other than its defaultfunction. A scan code is produced when pressing akey sequence on the mobile device. The macrofeature involves changing the meaning of a key’sscan code to represent another scan code, a sequenceof text, or a combination of scan codes and text.Use the following syntax for the parameter:CODE:[key sequence | \CODE] [..]Note: Scan codes are not recursive when used in adefinition.Example:0008:\0020 (backspace become space)0020:\0008 (space becomes backspace)
114 <strong>PSC</strong> <strong>300</strong>-<strong>Series</strong> <strong>Wavelink</strong> <strong>TN</strong> <strong>Client</strong> User’s <strong>Guide</strong>Number of SessionsSpecifies the number of concurrent Telnet sessionsthe mobile device can support. (NCU versionssupport only 1 session.)Possible values: 1 - 4Default value: 1Program Exit KeySpecifies the scan code (in hex) to exit the program. Ifyou specify “Default”, then there is no key to exit theprogram.Possible values: Four-digit hex valueDefault value: -Program Exit PasswordSpecifies the password the user must supply whenthe Program Exit Key is pressed. If you leave thisparameter blank, the value “default” is displayedand no password is required.Possible values: Up to 10 alpha-numeric charactersDefault value: DefaultRF Config PasswordSpecifies the password the user at the mobile devicemust supply to access and modify the RF parametersof the mobile device.Possible values: Up to 20 alpha-numeric charactersDefault value: SystemSleep TimeoutSpecifies the amount of time (in minutes) the mobiledevice remains idle before it enters sleep mode topreserve batter power. Use the value “0” to keep themobile device on until the user turns it off.Possible values: 0 - 255 (minutes)Default value: 2
Appendix C: Emulation Parameters 115TCP Keep AliveSpecifies whether the mobile device periodicallypings the host to which it is connected.Possible values: EnableDisableDefault value: EnableTerm Config PasswordSpecifies the password that the user at the mobiledevice must supply to access and modify emulationparameters and host profiles.Possible values: Up to 20 alpha-numeric charactersDefault value: ConfigUse Timing MarkHeartbeatSpecifies whether the mobile device sends a timingmark to the host to verify if the session is still active.Possible values: YesNoDefault value: YesEmulation - DisplayUse the emulation display parameters in Configuration Manager to modifydisplay parameters on the mobile device.
116 <strong>PSC</strong> <strong>300</strong>-<strong>Series</strong> <strong>Wavelink</strong> <strong>TN</strong> <strong>Client</strong> User’s <strong>Guide</strong>The following list contains a description of the emulation display parametersthat Configuration Manager allows you to modify:Backlight TimeSpecifies the amount of time (in seconds) thebacklight remains on after the user at the mobiledevice presses a key. Specify “0” to turn off thebacklight.Possible values: 0 - 99 (seconds)Default value: 5Cursor Column OffsetSpecifies the position on the display screen wherethe cursor will be located when the screen isreposition. This value is ignored if the mobile deviceis operating in fixed or tile mode. If you set thisparameter to “Default”, then the cursor column ispositioned five-eighths of the way from the left edgeof the display screen.Possible values: 0 to 1 less than the screen widthDefaultDefault value: -Cursor Row OffsetSpecifies the position on the display screen wherethe cursor will be located when the screen isreposition. If the mobile device is operating in fixedor tile mode, the value in this parameter is ignored.If the value is set to “Default”, then the cursor row ispositioned three-fourths of the way down the screen.Possible values: 0 to 1 less than the screen heightDefaultDefault value: -Cursor TypeSelect the type of cursor the mobile device displays.Possible values: DefaultNoneDefault value: Default
Appendix C: Emulation Parameters 117Double High FontSpecifies whether the display font on the mobiledevice is in double-high mode.Possible values: YesNoDefault value: NoDouble Wide FontSpecifies whether the display font on the mobiledevice is in double-wide mode.Possible values: YesNoDefault value: NoEnable ScrollingSpecifies whether the user at the mobile device isallowed to enter view mode to scroll around thevirtual display. You should set this parameter to“Yes” unless all applications on the mobile deviceare written to keep display data within the areaaround the entry fields.Possible values: YesNoDefault value: YesFixed Screen Left EdgeIf you have enabled Fixed Screen Mode on themobile device, this parameter specifies the left-edgecolumn of the fixed screen.Possible values: 1 - 80Default value: 1
118 <strong>PSC</strong> <strong>300</strong>-<strong>Series</strong> <strong>Wavelink</strong> <strong>TN</strong> <strong>Client</strong> User’s <strong>Guide</strong>Fixed Screen ModeSpecifies whether Fixed Screen Mode is enabled.When you enable Fixed Screen Mode, the sameportion of the display screen is shown withoutregard to where the cursor is on the virtual displayscreen. Users will not be able to see entry fields thatare beyond the fixed display area.Possible values: EnableDisableDefault value: DisableFixed Screen Top EdgeIf you have enabled Fixed Screen Mode, thisparameter specifies the top row of the fixed screen.Possible values: 1 - 24Default value: 1Horizontal ScrollIf you have enabled View Mode, this parameterspecifies the number of characters to move (scrollhorizontally). The default value, “Displaysize”, isthe current screen size. See Tiling for moreinformation.Possible values: 3 - 80DisplaySizeDefault value: DisplaySizeLeft Edge Cursor ZoneSpecifies how close the cursor can get to the left edgeof the screen before the screen is scrolled. The valueis the number of characters. When the cursoradvances outside of the specified cursor zone on thedisplay of the mobile device, the display isreposition over the full-screen display so that thecursor is placed near the center of the display screen.Possible values: 1 - 10Default value: 4
Appendix C: Emulation Parameters 119Preferred Offset LeftEdgeSpecifies the column of the Preferred Screen Offset.Possible values: 1 - 80Default value: 1Preferred Offset TopEdgeSpecifies the row of the Preferred Screen Offset.Possible values: 1 - 24Default value: 1Preferred Screen OffsetIndicates whether to reposition the physical displayto the location specified in the Preferred Offset TopEdge and Preferred Offset Left Edge parameterswhenever the cursor is located in the preferredoffset.Possible values: EnableDisableDefault value: DisableRight Edge Cursor Zone Specifies how close the cursor can get to the rightedge of the screen before the screen is scrolled. Thevalue is in character positions. When the cursoradvances outside the specified cursor zone on thedisplay of the mobile device, the display isreposition over the full-screen display so that thecursor is near the center of the display screen.Possible values: 1 - 10Default value: 1Tiling HeightSpecifies the height of the display tile of a mobiledevice. If the height is greater than the displayheight on the mobile device, then this parameter willdefault back to the actual display height of themobile device (DisplaySize).Possible values: 1 - 24DisplaySizeDefault value: DisplaySize
120 <strong>PSC</strong> <strong>300</strong>-<strong>Series</strong> <strong>Wavelink</strong> <strong>TN</strong> <strong>Client</strong> User’s <strong>Guide</strong>Tiling HorizontalSpecifies the type of horizontal tiling the mobiledevice uses. Tiling refers to dividing the logicaldisplay into adjacent blocks that are referred to astiles. When a screen is displayed, the physicaldisplay is located directly over the tile that containsthe cursor. In areas of the screen that are not tiled,the physical display will be roughly centered aroundthe cursor, without regard to boundaries betweentiles. Tiling is configured separately for horizontaland vertical components of the display.Possible values: None (centered around cursor)Left Only (centered on leftmostcolumn)All (always tile horizontally)Default value: Left OnlyTiling VerticalSpecifies the type of vertical tiling the mobile deviceuses. See Tiling Horizontal for information aboutTiling.Possible values: None (positioned around cursor)TopOnly (positioned at uppermostrow)All (always tile vertically)Default value: TopOnlyTiling WidthSpecifies the width of a mobile device display tile.Possible values: 1 - 24DisplaySizeDefault value: DisplaySize
Appendix C: Emulation Parameters 121Vertical ScrollSpecifies the number of rows to move when the inscreen mode.Possible values: 3 - 24DisplaySizeDefault value: DisplaySizeViewing ContrastSpecifies the viewing contrast for the mobile device.If you specify “Default”, then the most commonsetting for the mobile device is selected.Possible values: 1 - 31 (for 7000-series devices)0 - 7 (for other devices)Note: The lowest setting is the lightest.Default value: DefaultEmulation - KeyboardUse the emulation keyboard parameters in Configuration Manager to set thekeyboard functions on the mobile device.
122 <strong>PSC</strong> <strong>300</strong>-<strong>Series</strong> <strong>Wavelink</strong> <strong>TN</strong> <strong>Client</strong> User’s <strong>Guide</strong>The following list describes the keyboard parameters that you can modifywith Configuration Manager:Alpha Keyboard Name(5250 Only / VirtualKeyboard Only)You only need to configure this parameter if youhave specified “Yes” in the Shift Keyboard To FieldType parameter. This parameter specifies the nameof the keyboard that should become active when thecursor enters an alpha-only field.Possible values: any keyboard nameDefault value: CapsLockComma PeriodSwappedSpecifies whether the period key is swapped withthe comma key. (In some countries, commas areused more often than periods.)Possible values: YesNoDefault value: NoKeyboard IdentifierColumn(5250/3270 VirtualKeyboard Only)Specifies the location (column) of the string on thehost to indicate that a virtual keyboard commandfollows.Possible values: 1 - 80 (column number)Keyboard Identifier Row(5250/3270 VirtualKeyboard Only)Default value: 1Specifies the location (row) of the string on the hostto indicate that a virtual keyboard commandfollows.Possible values: 1 - 24 (row number)Default value: 3Keyboard IdentifierStringSpecifies the string on the host to indicate that avirtual keyboard command follows.Possible values: up to 10 alpha-numeric charactersDefault value: KBD
124 <strong>PSC</strong> <strong>300</strong>-<strong>Series</strong> <strong>Wavelink</strong> <strong>TN</strong> <strong>Client</strong> User’s <strong>Guide</strong>The following list describes the printing parameters that ConfigurationManager allows you to modify:Print Nulls to Spaces(5250/3270 Only)Specifies whether nulls are converted to anddisplayed as spaces. (Some applications displaynulls instead of spaces.)Possible values: YesNoDefault value: NoPrinter ProtocolSpecifies the printer protocol to send data to theprinter.Possible values: Normal (serial)TCPIP (IP printing)Default value: NormalPrinter TypeSpecifies the type of printer that is connected to themobile device.Possible values: PS1000PS1001PS104Line Printer (generic line printer)Dumb (no line monitoring)ComtecPathfinderRascalRenegadeCotec <strong>PSC</strong>ode CourierComtec RFUserDefinedDefault value: PS1000
Appendix C: Emulation Parameters 125Printer OptionSpecifies whether a reprint prompt is displayed aftera barcode is printed.Possible values: YesNoDefault value: YesRF Printer Retries(Comtec RF PrintersOnly)Specifies the number of RF retries for the Comtec RFprinter.Possible values: 1 - 5Default value: 3Emulation - SoundUse the emulation sound parameters in Configuration Manager to configurethe <strong>TN</strong> <strong>Client</strong> sounds on the mobile device.The following list describes the sound parameters that you can modify withConfiguration Manager:Beep DelaySpecifies the amount of time (in milliseconds)between additional message beeps.Possible values: 0 - 1000 (milliseconds)Default value: 75Beep DurationSpecifies the duration (in milliseconds) of beeps onthe mobile device.Possible values: 0 - 1000 (milliseconds)Default value: 100Beep ToneSpecifies the tone (in Hz) of beeps on the mobiledevice.Possible values: 0 - 1000 (Hz)Default value: 1000
126 <strong>PSC</strong> <strong>300</strong>-<strong>Series</strong> <strong>Wavelink</strong> <strong>TN</strong> <strong>Client</strong> User’s <strong>Guide</strong>Beeper VolumeSpecifies the volume of the beeper on the mobiledevice.Possible values: HighLowDefault value: HighBeeps with MessageSpecifies the number of additional beeps when amessage is displayed on the message line.Possible values: 0 - 9Default value: 0External BeeperSpecifies whether to offer support for the optionalexternal beeper.Possible values: YesNoDefault value: NoIncoming Screen Beep(5250/3270 Only)Specifies whether a beep sounds when a new screenarrives from the host.Possible values: EnableDisableDefault value: Enable
Appendix C: Emulation Parameters 127KeyclicksSpecifies whether the mobile device beeps when auser at the mobile device presses a key.Possible values: YesNoDefault value: NoSilent ModeSpecifies whether the mobile device should operatein silent mode. When the mobile device is in silentmode, it does not beep.Possible values: YesNoDefault value: NoEmulation - VT and HP - CommonUse the common VT and HP parameters in the Configuration Manager tomodify emulation parameters that are common to VT- and HP-typeemulation.The following list describes the common VT and HP parameters that you canmodify with the Configuration Manager:Alternate EscapeCharacterDefine the alternate Esc character to look for whenparsing escape sequences.Possible values: Up to three alpha-numericcharactersDefault value: 1BAuto-loginCurrently unavailable. Configure auto-login in hostprofiles.
128 <strong>PSC</strong> <strong>300</strong>-<strong>Series</strong> <strong>Wavelink</strong> <strong>TN</strong> <strong>Client</strong> User’s <strong>Guide</strong>Break KeySpecifies whether the Break key interrupts theconnection between the mobile device and the host.External Beeper on ErrorBeepPossible values: EnableDisableDefault value: DisableSpecifies whether to use the external beeper for errorbeeps.Possible values: YesNoDefault value: NoHandle TelxonSequencesSpecifies whether to support Telxon escapesequences that the host sends to mobile devices.Possible values: YesNoDefault value: NoLocal EchoSpecifies whether mobile devices use local echoes toreflect data that it sends to the host.Possible values: OnOffDefault value: OffMap UnderlineSpecifies whether the underline attribute isdisplayed as reverse video on mobile devices.Mobile devices do not display the underlineattribute.Possible values: YesNoDefault value: No
Appendix C: Emulation Parameters 129Remove ISO IDsSpecifies whether to remove ISO data IDs from thebeginning of bar codes.Possible values: YesNoDefault value: NoScan TerminatorSpecifies the scan terminator that is added after allscanned data. Precede hex values for letters with abackslash (for example, \0D).Possible values: Up to 10 alpha-numeric charactersDefault value: \0DUse FEDEX EscapeSequenceSpecifies whether the FEDEX escape sequences areenabled.Possible values: YesNoDefault value: NoVT Disable ScannerSpecifies whether the scanner on mobile devices isdisabled after scans.Possible values: NeverAlwaysOnly 1DOnly 2dDefault value: Never
130 <strong>PSC</strong> <strong>300</strong>-<strong>Series</strong> <strong>Wavelink</strong> <strong>TN</strong> <strong>Client</strong> User’s <strong>Guide</strong>VT New Answer BackSpecifies the New Answer Back string the mobiledevice displays when it receives an ENQ from thehost. The New Answer Back option supports thefollowing variables:• %m - %r (MAC address octets)• %a - %d (IP address octets)• %s (session number)• %t (Terminal ID)Default value: -Warning BellsSpecifies whether the mobile device beeps when thehost sends a warning bell.Possible values: YesNoDefault value: YesEmulation - VT and HP - HPUse the HP emulation parameters in the Configuration Manager to setemulation parameters that are specific to HP-type emulation.
Appendix C: Emulation Parameters 131The following list describes the HP-related parameters that the ConfigurationManager allows you to modify:Auto SendSpecifies whether the mobile device automaticallysends scanned data after the last entry field isscanned.Possible values: EnableDisableDefault value: DisableMessage LineIf you are using a message line, specify a line for themessage.Possible values: 0 - 24 (0 for no message line)Default value: 0Emulation - VT and HP - VTUse the VT emulation parameters in the Configuration Manager to setemulation parameters that are specific to VT-type emulationThe following list describes the VT-related parameters that the ConfigurationManager allows you to modify:Backspace KeySpecifies the character that is send by the Backspacekey.Possible values: 08 (Backspace)7F (Delete)Default value: 08Control CodesSpecifies the bit size of the control codes that theTelnetCE <strong>Client</strong> sends to the host.Possible values: 78Default value: 7
132 <strong>PSC</strong> <strong>300</strong>-<strong>Series</strong> <strong>Wavelink</strong> <strong>TN</strong> <strong>Client</strong> User’s <strong>Guide</strong>EZ Block Mode(VT 220 Only)Specifies whether to simulate a simple andconvenient block mode behavior using textdelimiters.Possible values: OnOffDefault value: OffEZ End Field Delimiter(VT 220 Only)Specifies the end field text delimiter when EZ blockmode is turned on.Possible values: Any ASCII character codeDefault value: 3C (““)VT Copy Screen TextAllow screen text at a given row, column, and lengthto be copied to a new row and column. The format ofthe parameter is Original Row, Original Column,New Row, New Column, Length.Possible values: 1 - 24 (row)1 - 80 (column)1-80 (length)Default value: -
Appendix C: Emulation Parameters 133VT Line ModeSpecifies whether the TelnetCE <strong>Client</strong> simulates aline mode-like behavior. Use this feature for hoststhat do not support true line mode.Possible values: OnOffDefault value: OffVT Line Mode Clear Key Specifies the Clear key for line mode. Use the scancode for the desired key.Possible values: scan codeDefault value: 001BScanner - CodabarUse the Codabar scanner emulation parameters in Configuration Manager toconfigure the way the <strong>TN</strong> <strong>Client</strong> handles Codabar scan codes.The following list describes the Codabar scanner parameters thatConfiguration Manager allows you to modify:Codabar Add PostambleStringSpecifies the string to be added to the end ofCodabar barcode data.Possible values: Up to 20 alpha-numeric charactersDefault value: -Codabar Add PreambleStringSpecifies the string to be added to the beginning ofCodabar barcode data.Possible values: Up to 20 alpha-numeric characters.Default value: -
134 <strong>PSC</strong> <strong>300</strong>-<strong>Series</strong> <strong>Wavelink</strong> <strong>TN</strong> <strong>Client</strong> User’s <strong>Guide</strong>Codabar CLSISpecifies whether the 14-character Codabar symbolis reformatted to remove the start and stopcharacters from Codabar barcode scans.Possible values: YesNoDefault value: NoCodabar MaxlengthSpecifies the maximum length (in characters) forCodabar scans.Possible values: 0 - 60Default value: 0Codabar MinlengthSpecifies the minimum length (in characters) forCodabar scans.Possible values: 0 - 30Default value: 0Codabar NOTISSpecifies whether to remove the start and stopcharacters from Codabar scans.Possible values: YesNoDefault value: NoCodabar RedundancySpecifies whether Codabar redundancy is enabled.(Redundancy requires the mobile device to decode abarcode from two separate scans. The two scansoccur with a single activation of the scanner trigger.)Possible values: YesNoDefault value: No
Appendix C: Emulation Parameters 135Codabar Scans Strip End Specify the number of characters to strip from theend of Codabar bar scans.Possible values: 0 - 255Default value: 0Codabar Scans StripStartSpecify the number of characters to strip from thebeginning of Codabar bar scans.Possible values: 0 - 255Default value: 0Symbology CodabarSpecifies whether the Codabar symbology is enabledon the mobile device.Possible values: EnableDisableDefault value: DisableScanner - Code11Use the Code11 scanner emulation parameters in Configuration Manager toconfigure the way the <strong>TN</strong> <strong>Client</strong> handles Code11 scan codes.The following list describes the Code11 parameters that ConfigurationManager allows you to modify:Code11 Add PostambleStringSpecifies the string to be added to the end of Code11barcode data.Possible values: Up to 20 alpha-numeric charactersDefault value: -Code11 Add PreambleStringSpecifies the string to be added to the beginning ofCode11 barcode data.Possible values: Up to 20 alpha-numeric charactersDefault value: -
136 <strong>PSC</strong> <strong>300</strong>-<strong>Series</strong> <strong>Wavelink</strong> <strong>TN</strong> <strong>Client</strong> User’s <strong>Guide</strong>Code11 CDSpecifies the number of check-digits read withCode11 barcodes. This does not include the numberof check digits in the Code11 length specification,even if the application receives a report on thenumber. (This option is not available on the SPT1740).Possible values: 0 - 3Default value: 1Code11 MaxlenghtSpecifies the maximum length of Code11 barcodes.Possible values: 0 - 60Default value: 0Code11 MinlengthSpecifies the minimum length of Code11 barcodes.Possible values: 0 - 30Default value: 0Code11 RedundancySpecifies whether Code11 redundancy is enabled.(Redundancy requires the mobile device to decode abarcode from two separate scans. The two scansoccur with a single activation of the scanner trigger.)Possible values: YesNoDefault value: NoCode11 Return CDSpecifies whether the Code11 check-digit is returnedas part of the scanned data. This field has no effecton Code11 length specification; the lengthspecification only accounts for data characters. (Thisfeature is unavailable on the SPT 1740.)Possible values: YesNoDefault value: No
Appendix C: Emulation Parameters 137Code11 Scans Strip End Specifies the number of characters to strip from theend of a Code11 barcode.Possible values: 0 - 255Default value: 0Code11 Scans StripStartSpecifies the number of characters to strip from thebeginning of a Code11 barcode.Possible values: 0 - 255Default value: 0Symbology Code11Specifies whether Code11 symbology is enabled onthe mobile device.Possible values: EnableDisableDefault value: EnableScanner - Code128Use the Code128 scanner emulation parameters in Configuration Manager toconfigure the way the <strong>TN</strong> <strong>Client</strong> handles Code 128 scan codes.The following list describes the Code128 scanner parameters that you canmodify with Configuration Manager:Code128 Add PostambleStringSpecifies the string to be added to the end ofCode128 barcode data.Possible values: Up to 20 alpha-numeric charactersDefault value: -Code128 Add PreambleStringSpecifies the string to be added to the beginning ofCode128 barcode data.Possible values: Up to 20 alpha-numeric charactersDefault value: -
138 <strong>PSC</strong> <strong>300</strong>-<strong>Series</strong> <strong>Wavelink</strong> <strong>TN</strong> <strong>Client</strong> User’s <strong>Guide</strong>Code128 MaxlengthSpecifies the maximum length for a Code128barcode.Possible values: 0 - 60Default value: 0Code128 MinlengthSpecifies the minimum length for a Code128barcode.Possible values: 0 - 30Default value: 0Code128 RedundancySpecifies whether Code128 redundancy is enabled.(Redundancy requires the mobile device to decode abarcode from two separate scans. Two scans occurwith a single activation of the scanner trigger.)Possible values: YesNoDefault value: NoCode128 Scans StripEndSpecifies the number of characters to strip from theend of a Code128 barcode scan.Possible values: 0 - 255Default value: 0Code128 Scans StripStartSpecifies the number of characters to strip from thebeginning of a Code128 barcode scan.Possible values: 0 - 255Default value: 0Symbology Code 128Specifies whether Code128 symbology is enabled onthe mobile device.Possible values: EnableDisableDefault value: Enable
Appendix C: Emulation Parameters 139Scanner - Code39Use the Code39 scanner emulation parameters in Configuration Manager toconfigure the way the <strong>TN</strong> <strong>Client</strong> handles Code39 scan codes.The following list describes the Code39 scanner parameters thatConfiguration Manager allows you to modify:Code39 Add PostambleStringSpecifies the string to be added to the end of Code39barcode data.Possible values: Up to 20 alpha-numeric charactersDefault value: -Code39 Add PreambleStringSpecifies the string to be added to the beginning ofCode39 barcode data.Possible values: Up to 20 alpha-numeric characters.Default value: -Code39 CDSpecifies whether a Code39 check-digit is returnedas part of the scanned data.Possible values: YesNoDefault value: NoCode39 Full ASCIISpecifies whether Code39 barcodes are processed toallow the full representation of the ASCII characterset.Possible values: YesNoDefault value: NoCode39 MaxlengthSpecifies the maximum length of Code39 barcodes.Possible values: 0 - 60Default value: 0
140 <strong>PSC</strong> <strong>300</strong>-<strong>Series</strong> <strong>Wavelink</strong> <strong>TN</strong> <strong>Client</strong> User’s <strong>Guide</strong>Code39 MinlengthSpecifies the minimum length of Code39 barcodes.Possible values: 0 - 30Default value: 0Code39 RedundancySpecifies whether Code39 redundancy is enabled.(Redundancy requires the mobile device to decode abarcode from two separate scans. The two scansoccur with a single activation of the scanner trigger.)Possible values: YesNoDefault value: NoCode39 Scans Strip End Specifies the number of characters to strip from theend of a Code39 barcode scan.Possible values: 0 - 255Default value: 0Code39 Scans StripStartSpecifies the number of characters to strip from thebeginning of a Code39 barcode scan.Possible values: 0 - 255Default value: 0Symbology Code39Specifies whether Code39 symbology is enabled.Possible values: EnableDisableDefault value: EnableScanner - Code93Use the scanner Code93 emulation parameters in Configuration Manager toconfigure the way the <strong>TN</strong> <strong>Client</strong> handles Code 93 scan codes.
Appendix C: Emulation Parameters 141The following list describes the Code93 parameters that ConfigurationManager allows you to modify:Code93 Add PostambleStringSpecifies the string to add to the end of Code93barcode scans.Possible values: Up to 20 alpha-numeric charactersDefault value: -Code93 Add PreambleStringSpecifies the string to add to the beginning ofCode93 barcode scans.Possible values: Up to 20 alpha-numeric charactersDefault value: -Code93 MaxlengthSpecifies the maximum length for Code93 barcodes.Possible values: 0 - 60Default value: 0Code93 MinlengthSpecifies the minimum length for Code93 barcodes.Possible values: 0 - 30Default value: 0Code93 RedundancySpecifies whether Code93 redundancy is enabled.(Redundancy requires a mobile device to decode abarcode from two separate scans. The two scansoccur with a single activation of the scanner trigger.)Possible values: YesNoDefault value: NoCode93 Scans Strip End Specifies the number of characters to strip from thebeginning of Code93 barcodes.Possible values: 0 - 255Default value: 0
142 <strong>PSC</strong> <strong>300</strong>-<strong>Series</strong> <strong>Wavelink</strong> <strong>TN</strong> <strong>Client</strong> User’s <strong>Guide</strong>Code93 Scans StripStartSpecifies the number of characters to strip from theend of Code93 barcodes.Possible values: 0 - 255Default value: 0Symbology Code93Specifies whether Code93 symbology is enabled onthe mobile device.Possible values: EnableDisableDefault value: EnableScanner - CommonUse the common scanner emulation parameters in the ConfigurationManager to set the way the <strong>TN</strong> <strong>Client</strong> handles all types of scanned data.The following list describes the common scaner emulation parameters thatthe Configuration Manager allows you to modify:Add Scan IdentifierSpecifies whether to add a scan identifier to allscanned data. The identifier is used to indicatescanned data to a host. (If you enable this parameter,you must specify the scan identifier in the ScanIdentifier parameter.)Possible values: YesNoDefault value: NoAll Scan Strip Startspecifies the number of characters that are strippedfrom the beginning of all barcodes.Possible values: 0 - 20Default value: 0
Appendix C: Emulation Parameters 143All Scan Strip EndSpecifies the number of characters that are strippedfrom the end of all barcodes.Possible values: 0 - 20Default value: 0Allow Scan AheadSpecifies whether a user can scan ahead while thehost is processing data from the previous scan. Ifyou do not enable this parameter, the scanner isdisabled while the host process the data from theprevious scan.Possible values: YesNoDefault value: NoAuto Send ScansSpecifies whether the mobile device automaticallysends data to the host after a barcode scan.Possible values: YesNoLast Only (if data is scanned intolast field)Default value: NoBidir RedundancySpecifies whether bi-directional redundancy isenabled. If bi-directional redundancy is enabled,then two decodes of the barcode in opposite lasersweep directors are required. (The default settingallows two decodes of the barcode in the samesweep direction.)Possible values: YesNoDefault value: No
144 <strong>PSC</strong> <strong>300</strong>-<strong>Series</strong> <strong>Wavelink</strong> <strong>TN</strong> <strong>Client</strong> User’s <strong>Guide</strong>Green Scan LED On-TimeSpecifies the amount of time (in milliseconds) thegreen LED light remains on after the mobile devicecompletes a scan.Possible values: 0 - 10000 (milliseconds)Default value: <strong>300</strong>0Remove Barcode Header Specifies a string. If the beginning characters of abarcode scan match the specified string, the string isremoved from the barcode. If you specify a string,then the Scan Identifier, Scans Strip Start, Scans StripEnd, and Preamble String are ignored. (The defaultsetting will not remove any header.)Possible values: any stringDefault value: -Scan Escape Code(5250/3270 Only)Specifies the scan escape code that is used to identifyaid keys (for example, F1, F10, or Enter) that arescanned. Input the hex value of the character.Possible values: hex value of a characterDefault value: 1B
Appendix C: Emulation Parameters 145Scan HandlerSpecifies commands that provide special processingof scanned data. You can specify scans to do any ofthe following:• Strip data from the start/end of a barcode• Replace selected text within a barcode• Append/prepend data to the barcode• Translate data within a barcodeUse the following syntax:symbology(length)[command]Use the following letters in the symbologyparameter to specify a symbology:A = anyB = UPCE0C = UPC1D = UPCAE = MSIF = EAN8G = EAN 13H = CodabarI = Code3of9J = D2of5K = i2of5L = Code11M = Code93N = Code128O = PDF417P = D2of5 IATAQ = UCC/EAN128
146 <strong>PSC</strong> <strong>300</strong>-<strong>Series</strong> <strong>Wavelink</strong> <strong>TN</strong> <strong>Client</strong> User’s <strong>Guide</strong>Specifies the (length) parameter as one of thefollowing:• The minimum and maximum length formatted as[min-max], where min is the minimum lengthand max is the maximum length.• A specific value to match a specific length.• 0 to match any length.For the [command] parameters, specify any of thefollowing single-character codes followed by anyvariables that are specific to that code:• [S(loc)(char)] to strip characters from thebarcode, where:• (loc) is the location, either S (start of barcode)or E (end of barcode)• (char) variable is the number of characters tostripExample: Q(16)[SS1] strips off the firstcharacter of UCC/EAN128 barcodes of length 16.• [R(char)(repl)] to replace characters in thebarcode, where:• (char) is the character to replace• (repl) is the replacement characterNOTE You may specify the character directly, or youmay specify the two-digit hex value for thecharacter.Example: A(9-12)[R29] replaces all 2s with9s in any barcode of lengths between 9 and 12.
Appendix C: Emulation Parameters 147[A(app)] appends data to the end of thebarcode, where:• (app) is the data to append (between 1 and 8bytes)NOTE The data may include two-digit hex values.You must preface each hex value with a backslash(\).Example: A(0)[A123] appends 123 to the endof all barcodes.• [P(pre)] to add data to the beginning of abarcode (prepend), where:• (pre) is the value to prepend (between 1and 8 bytes)NOTE The data may include two-digit hex values.You must preface each hex value with a backslash.Example: A(0)[P123] prepends 123 to allbarcodes.• [X(trans);(repl)] to translate barcode data(between 1 and 8 bytes), where:• (trans) is the data to translate• (repl) is the replacement dataNOTE The data may include two-digit hex values.You must preface each hex value with a backslash.Example: A(0)[X123;ABC] translates alloccurrences of 123 to ABC in all types ofbarcodes.
148 <strong>PSC</strong> <strong>300</strong>-<strong>Series</strong> <strong>Wavelink</strong> <strong>TN</strong> <strong>Client</strong> User’s <strong>Guide</strong>• [C(char);(loc);(siz)] to cut barcode data(1 to 8 characters) based on a starting character,where:• (char) is the search string (1 to 8 characters)• (loc) is the start location of the search (incharacters)• (siz) is the size (in characters)NOTE The data may include two-digit hex values.You must preface hex values with a backslash.Example: A(0)[C00;3;18] coverts to 18 charactersstarting with the third in scan when the barcodestarts with 00.Scan IdentifierSpecifies a scan identifier. The scan identifier isplaced in front of all scanned data to indicatescanned data to the host. You can use two-digit hexvalues to specify a value. Preface hex values with abackslash. (You must set the Add Scan Identifierparameters to “Yes” for the Scan Identifierparameter to be valid.)Possible values: any stringDefault value: -Scanner AngleSpecifies the type of scanner angle for the scanner onthe mobile device.Possible values: NarrowWideDefault value: Narrow
Appendix C: Emulation Parameters 149Scanner TypeSpecifies the type of scanner on the mobile device.Possible values: LRTLaser OnlyContact with PulseContact without PulseAuto with PulseAuto without PulseWand SimulatorDual TriggerSingle TriggerLibertyDefault value: - (automatically selects the type forthe current standard on the mobile device)STLR Scan TimeoutSpecifies the timeout (in seconds) for single-positiontrigger long-range scanners. these are primarily for6840LR mobile devices.Possible values: 0 - 255 (seconds)Default value: 3Symbology SuppsSpecifies whether the scanner reads supplementalbarcodes with UCPC and EAN barcodes.Possible values: EnableDisableDefault value: Disable
150 <strong>PSC</strong> <strong>300</strong>-<strong>Series</strong> <strong>Wavelink</strong> <strong>TN</strong> <strong>Client</strong> User’s <strong>Guide</strong>Transmit Code ID CharSpecifies whether a prefix symbology code is addedto scanned data that is returned to the application .The ASCII characters represent the followingsymbologies:A = UPD, UPCE0, UPCE1, EAN8, EAN13B = Code39C = CodabarD = Code128E = Code 93F = I2of5G = D2of5H = Code11J = MSIK = UCCEAN128Possible values: YesNoDefault value: NoUPC EAN LinearSpecifies whether the decoder must decode all labelblocks in the same sweep.Note: UPC labels are divided into left and rightblocks (manufacturer and item numbers). Settingthis parameter to “No” allows the decoder tocombine a block from a partially decoded UPC labelwith a block decoded in an earlier scan. Setting thisparameter to “Yes” forces the decoder to decode alllabel blocks in the same sweep, which is thepreferred method when scanning multiple labelswith potentially interchangeable blocks in the laserfield.Possible values: YesNoDefault value: No
Appendix C: Emulation Parameters 151UPC EAN SecuritySpecifies the level of the decode algorithm for UPCand EAN barcodes. This parameter preventsincorrect decodes by aiding in decoding poor labels.The lower the level, the less stringent but moreaggressive the decoding. Higher security levelsprovide greater protection against incorrect decodes.Possible values: 0 - 3Default value: 0UPC EAN Supp 2Specifies whether to allow decodes of barcodes withtwo supplemental characters. (This feature is notavailable on the SPT 1740.)Possible values: YesNoDefault value: NoUPC EAN Supp 5Specifies whether to allow decodes of barcodes withfive supplemental characters. (This feature is notavailable on the SPT 1740.)Possible values: YesNoDefault value: No
152 <strong>PSC</strong> <strong>300</strong>-<strong>Series</strong> <strong>Wavelink</strong> <strong>TN</strong> <strong>Client</strong> User’s <strong>Guide</strong>UPC EAN Supp ModeSpecifies the method by which supplementalbarcodes are handled.Possible values:NoSupps (ignore supp barcodes)OnlySuppLabels (verifies that the UPC labels has anattached supp barcode that matches the enabledlengths)SuppsOptional (reports if thedecoder determines there is a suppof any length)NOTE With the OnlySuppsLabel method, twocharacterand five-character supplemental barcodesare valid if you set the UPC EAN Supp 2 and UPCEAN Supp 5 parameters to “Yes”.Default value: NoSuppsUP C EAN Supp RetrySpecifies the number of times the barcode would beread if checking for a supplemental barcode. (Iflabels with or without supplements are returned tothe application, this option determines how manytimes the decoder attempts to decode the UPC labelbefore it registers that there are no supplements.)Possible values: 2 - 10Default value: 5Use Scanner AsKeyboard WedgeSpecifies whether the program can use scanned dataas keybaord data. This will bypass all specialhandling that is performed on data.Possible values: EnableDisableDefault value: Disable
Appendix C: Emulation Parameters 153Scanner - D2of5Use the scanner D2of5 emulation parameters in Configuration Manager toconfigure the way the <strong>TN</strong> <strong>Client</strong> handles D2of5 scan codes.The following list describes the D2of5 parameters that you can modify withConfiguration Manager:D2of5 Add PostambleStringSpecifies the string to be added to the end of D2of5barcode data.Possible values: up to 20 alpha-numeric charactersDefault value: -D2of5 Add PreamableStringspecify the string to be added to the beginning ofD2of5 barcode data.Possible values: up to 20 alpha-numeric characters.Default value: -D2of5 MaxlengthSpecifies the maximum length for a D2of5 barcode.(Use 0 to represent any length.)Possible values: 0 - 60Default value: 0D2of5 MinlengthSpecifies the minimum length for a D2of5 barcode.(Use 0 to represent any length.)Possible values: 0 - 60Default value: 0D2of5 RedundancySpecifies whether D2of5 redundancy is enabled.(Redundancy requires the mobile device to decode abarcode from two separate scans. The two scansoccur with a single activation of the scanner trigger.)Possible values: YesNoDefault value: No
154 <strong>PSC</strong> <strong>300</strong>-<strong>Series</strong> <strong>Wavelink</strong> <strong>TN</strong> <strong>Client</strong> User’s <strong>Guide</strong>D2of5 Scans Strip EndSpecifies the number of characters to strip from theend of D2of5 barcodes.Possible values: 0 - 255Default value: 0D2of5 Scans Strip StartSpecifies the number of characters to strip from thebeginning of D2of5 barcodes.Possible values: 0 - 255Default value: 0Symbology D2of5Specifies whether D2of5 symbology is enabled onthe mobile device.Possible values: EnableDisableDefault value: EnableScanner - EAN13Use the scanner EAN13 emulation parameters in Configuration Manager toconfigure the way the <strong>TN</strong> <strong>Client</strong> handles EAN 13 scan codes.
Appendix C: Emulation Parameters 155The following list describes the EAN13 parameters that you can modify withConfiguration Manager:Convert EAN13 to ISBNSpecifies whether EAN13 codes are converted toISBN codes.Possible values: YesNoDefault value: NoEAN13 Add PostambleStringSpecifies the string to be added to the end of EAN13barcode data.Possible values: up to 20 alpha-numeric charactersDefault value: -EAN13 Add PreambleStringSpecifies the string to be added to the beginning ofEAN13 barcode data.Possible values: up to 20 alpha-numeric charactersDefault value: -EAN13 Scans Strip EndSpecifies the number of characters to strip from theend of an EAN13 barcode.Possible values: 0 - 255Default value: 0EAN13 Scans Strip Start Specifies the number of characters to strip from thebeginning of an EAN13 barcode.Possible values: 0 - 255Default value: 0
156 <strong>PSC</strong> <strong>300</strong>-<strong>Series</strong> <strong>Wavelink</strong> <strong>TN</strong> <strong>Client</strong> User’s <strong>Guide</strong>Hyphenate ISBNSpecifies whether the output ISBN code ishyphenated. (You must also enable the ConvertEAN13 to ISBN parameter.)Possible values: YesNoDefault value: NoSymbology EAN13Specifies whether EAN13 symbology is enabled onthe mobile device.Possible values: EnableDisableDefault value: EnableScanner - EAN8Use the scanner EAN8 parameters in Configuration Manager to configure theway the <strong>TN</strong> <strong>Client</strong> handles EAN8 scan codes.The following list describes the EAN8 parameters that ConfigurationManager allows you to modify:EAN8 Add PostambleStringSpecifies the string to be added to the end of EAN8barcode data.Possible values: up to 20 alpha-numeric charactersDefault value: -EAN8 Add PreambleStringSpecifies the string to be added to the beginning ofEAN8 barcode data.Possible values: up to 20 alpha-numeric charactersDefault value: -
Appendix C: Emulation Parameters 157EAN8 ConvertSpecifies whether EAN8 barcodes are converted toEAN13. The conversion increases the EAN8 label to13 characters by adding 0s. (This parameter isautomatically enabled when you place EAN13 andEAN8 labels into the same input field.)Possible values: YesNoDefault value: NoEAN8 Scans Strip EndSpecifies the number of characters to strip from theend of an EAN8 barcode.Possible values: 0 - 255Default value: 0EAN8 Scans Strip StartSpecifies the number of characters to strip from thebeginning of an EAN8 barcode.Possible values: 0 - 255Default value: 0Symbology EAN8Specifies whether EAN8 symbology is enabled onthe mobile device.Possible values: EnableDisableDefault value: EnableScanner - I2of5Use the I2of5 emulation parameters in Configuration Manager to configurethe way the <strong>TN</strong> <strong>Client</strong> handles I2of5 scan codes.
158 <strong>PSC</strong> <strong>300</strong>-<strong>Series</strong> <strong>Wavelink</strong> <strong>TN</strong> <strong>Client</strong> User’s <strong>Guide</strong>The following list describes the I2of5 parameters that Configuration Managerallows you to modify:I2of5 Add PostambleStringSpecifies the string to be added to the end of I2of5barcode data.Possible values: up to 20 alpha-numeric charactersDefault value: -I2of5 Add PreambleStringSpecifies the string to be added to the beginning ofI2of5 barcode data.Possible values: up to 20 alpha-numeric charactersDefault value: -I2of5 MaxlengthSpecifies the maximum length of an I2of5 barcode.(Use 0 to indicate any length.)Possible values: 0 - 60Default value: 0I2of5 MinlengthSpecifies the minimum length of an I2of5 barcode.(Use 0 to indicate any length.)Possible values: 0 - 30Default value: 0I2of5 RedundancySpecifies whether I2of5 redundancy is enabled.(Redundancy requires the mobile device to decode abarcode from two separate scans. The two scansoccur with a single activation of the scanner trigger.)Possible values: YesNoDefault value: No
Appendix C: Emulation Parameters 159I2of5 Scans Strip EndSpecifies the number of characters to strip from theend of I2of5 barcodes.Possible values: 0 - 255Default value: 0I2of5 Scans Strip StartSpecifies the number of characters to strip from thebeginning of I2of5 barcodes.Possible values: 0 - 255Default value: 0Symbology I2of5Specifies whether I2of5 symbology is enabled onmobile devices.Possible values: EnableDisableDefault value: EnableScanner - MSIUse the MSI emulation parameters in Configuration Manager to configure theway the <strong>TN</strong> <strong>Client</strong> handles MSI scan codes.The following list describes the MSI parameters that Configuration Managerallows you to modify:MSI Add PostambleStringSpecifies the string to be added to the end of MSIbarcode data.Possible values: up to 20 alpha-numeric charactersDefault value: -MSI Add PreambleStringSpecifies the string to be added to the end of MSIbarcode data.Possible values: up to 20 alpha-numeric charactersDefault value: -
160 <strong>PSC</strong> <strong>300</strong>-<strong>Series</strong> <strong>Wavelink</strong> <strong>TN</strong> <strong>Client</strong> User’s <strong>Guide</strong>MSI CDSpecifies the number of check digits scanned. MSIcode has 1 or 2 check digits. Do not include thenumber of check digits in the MSI lengthspecification, even if they are reported back to theapplication.Possible values: 12Default value: 1MSI MaxlengthSpecifies the maximum length for an MSI barcode.(Use 0 to represent any length.)Possible values: 0 - 60Default value: 55MSI MinlengthSpecifies the minimum length for an MSI barcode.(Use 0 to represent any length.)Possible values: 0 - 30Default value: 4MSI RedundancySpecifies whether MSI redundancy is enabled.(Redundancy requires the mobile device to decode abarcode from two separate scans. The two scansoccur with a single activation of the scanner trigger.)Possible values: YesNoDefault value: NoMSI Return CDSpecifies whether MISI check digit is returned aspart of the scanned data.Possible values: YesNoDefault value: No
Appendix C: Emulation Parameters 161MSI Scans Strip EndSpecifies the number of characters to strip from theend of an MSI barcode.Possible values: 0 - 255Default value: 0MSI Scans Strip StartSpecifies the number of characters to strip from thebeginning of an MSI barcode.Possible values: 0 - 255Default value: 0Symbology MSISpecifies whether MSI symbology is enabled on themobile device.Possible values: EnableDisableDefault value: EnableScanner - UCC128Use the UCC128 scanner parameters in Configuration Manager to specify theway that the <strong>TN</strong> <strong>Client</strong> handles UCC128 scan codes.The following list describes the UCC128 parameters that you can specify withConfiguration Manager:UCC/EAN 128 AddPostamble StringSpecifies the string to be added to the end of UCC/EAN128 barcode data.Possible values: up to 20 alpha-numeric charactersDefault value: -UCC/EAN 128 AddPreamble StringSpecifies the string to be added to the beginning ofUCC/EAN128 barcode data.Possible values: up to 20 alpha-numeric charactersDefault value: -
162 <strong>PSC</strong> <strong>300</strong>-<strong>Series</strong> <strong>Wavelink</strong> <strong>TN</strong> <strong>Client</strong> User’s <strong>Guide</strong>UCC/EAN 128 ScansStrip EndSpecifies the number of characters to strip from theend of UCC/EAN128 barcode scans.Possible values: 0 - 255Default value: 0UCC/EAN 128 ScansStrip StartSpecifies the number of characters to strip from thestart of UCC/EAN128 barcode scans.Possible values: 0 - 255Default value: 0Scanner - UPCAUse the UPCA emulation parameters in Configuration Manager to specify theway that the <strong>TN</strong> <strong>Client</strong> handles UPCA scan codes.The following list describes the UPCA parameters that you can specify inConfiguration Manager:Symbology UPCASpecifies whether UPCA symbology is enabled onmobile devices.Possible values: EnableDisableDefault value: EnableUPCA Add PostambleStringSpecifies the string to be added to the end of UPCAbarcodes.Possible values: Up to 20 alpha-numeric charactersDefault value: -UPCA Add PreambleStringSpecifies the string to be added to the beginning ofUPCA barcodes.Possible values: Up to 20 alpha-numeric charactersDefault value: -
Appendix C: Emulation Parameters 163UPCA PreambleSpecifies whether the preamble (first) character isreturned to the application with the scanned data ofa UPCA barcode.Possible values: YesNoDefault value: YesUPCA Return CDSpecifies whether the check digit is returned as partof the scanned data of a UPCA barcode.Possible values: YesNoDefault value: YesUPCA Scans Strip EndSpecifies the number of characters to strip from theend of a UPCA barcode.Possible values: 0 - 255Default value: 0UPCA Scans Strip StartSpecifies the number of characters to strip from thebeginning of a UPCA barcode.Possible values: 0 - 255Default value: 0Scanner - UPCE0Use the UPCE0 scanner emulation parameters in Configuration Manager tospecify the way the <strong>TN</strong> <strong>Client</strong> handles UPCE0 scan codes.
164 <strong>PSC</strong> <strong>300</strong>-<strong>Series</strong> <strong>Wavelink</strong> <strong>TN</strong> <strong>Client</strong> User’s <strong>Guide</strong>The following list describes the UPCE0 parameters that ConfigurationManager allows you to modify:Symbology UPCE0Specifies whether UPCE0 symbology is enabled onmobile devices.Possible values: EnableDisableDefault value: EnableUPCE0 Add PostambleStringSpecifies the string to be added to the end of UPCE0barcodes.Possible values: up to 20 alpha-numeric charactersDefault value: -UPCE0 Add PreambleStringSpecifies the string to be added to the beginning ofUPCE0 barcodes.Possible values: up to 20 alpha-numeric charactersDefault value: -UPCE0 ConvertSpecifies whether the six-character UPCE0 label isconverted to the equivalent 12-character UPCAlabel.Possible values: YesNoDefault value: NoUPCE0 PreambleSpecifies whether the preamble (first) characterreturns to the application with the data of a UPCE0barcode scan.Possible values: YesNoDefault value: No
Appendix C: Emulation Parameters 165UPCE0 Return CDSpecifies whether the verified check digit is returnedto the application as part of the UPCE0 barcode data.Possible values: YesNoDefault value: NoUPCE0 Scans Strip EndSpecifies the number of characters to strip from theend of a UPCE0 barcode.Possible values: 0 - 255Default value: 0UPCE0 Scans Strip Start Specifies the number of characters to strip from thebeginning of a UPCE0 barcode.Possible values: 0 - 255Default value: 0Scanner - UPCE1Use the UPCE1 scanner emulation parameters in Configuration Manager tospecify the way that the <strong>TN</strong> <strong>Client</strong> handles UPCE1 scan codes.
166 <strong>PSC</strong> <strong>300</strong>-<strong>Series</strong> <strong>Wavelink</strong> <strong>TN</strong> <strong>Client</strong> User’s <strong>Guide</strong>The following list explains the UPCE1 parameters that ConfigurationManager allows you to modify:Symbology UPCE1Specifies whether UPCE1 symbology is enabled onthe mobile device.Possible values: EnableDisableDefault value: EnableUPCE1 Add PostambleStringSpecifies the string to be added to the end of UPCE1barcode data.Possible values: up to 20 alpha-numeric charactersDefault value: -UPCE1 Add PreambleStringSpecifies the string to be added to the beginning ofUPCE1 barcode data.Possible values: up to 20 alpha-numeric charactersDefault value: -UPCE1 ConvertSpecifies whether to expand the six-character UPCE1label to the equivalent 12-character UPCA label.Possible values: YesNoDefault value: NoUPCE1 PreambleSpecifies whether the UPC preamble (first) characteris returned to the application as part of the scanneddata of the UPCE1 barcode.Possible values: YesNoDefault value: No
Appendix C: Emulation Parameters 167UPCE1 Return CDSpecifies whether the UPC check digit is returned tothe application as part of the scanned data of theUPCE1 barcode.Possible values: YesNoDefault value: NoUPCE1 Scans Strip EndSpecifies the number of characters to strip from theend of a UPCE1 barcode.Possible values: 0 - 255Default value: 0UPCE1 Scans Strip Start Specifies the number of characters to strip from thestart of a UPCE1 barcode.Possible values: 0 - 255Default value: 0
168 <strong>PSC</strong> <strong>300</strong>-<strong>Series</strong> <strong>Wavelink</strong> <strong>TN</strong> <strong>Client</strong> User’s <strong>Guide</strong>
Glossary 169Glossary802.11/a/b The IEEE standards for wireless Ethernet. 802.11provides for wireless networking speeds up to 2Mbps at 2.4 GHz. 802.11b provides wirelessnetworking speeds up to 11 Mbps at 2.4 GHz.802.11a provides wireless networking speeds up to54 Mbps at 5 GHz.access pointad hoc modeAgentAPautomatic WEPAvalanche AgentAvalanche <strong>Client</strong>Avalanche EnablerA device that acts as a bridge between wirelessLANs and wired LANs.A mode of operation in wireless networks whereinwireless devices communicate directly with eachother without the use of an access point. Alsosometimes referred to as peer-to-peer mode or anindependent basic service set (IBSS).In the context of Avalanche Manager, an AvalancheAgent. See Avalanche Agent.Access Point. See Access Point.A dynamic implementation of WEP keys, whereinthe key used on the wireless network changesperiodically. <strong>Client</strong>s must synchronize their WEPkey use with the AP.An Avalanche Manager Agent. A softwarecomponent that provides the core functionality ofAvalanche Manager. The Agent facilitatescommunication with Avalanche clients.A mobile device with an installed AvalancheEnabler, which allows the client to communicatewith an Avalanche Agent and to be configured andmanaged through Avalanche Manager.A software component that is installed on mobiledevices which allows you to configure and managethe device through Avalanche Manager. The Enablerfacilitates communication between the mobile deviceand an Agent.
170 <strong>PSC</strong> <strong>300</strong>-<strong>Series</strong> <strong>Wavelink</strong> <strong>TN</strong> <strong>Client</strong> User’s <strong>Guide</strong>Avalanche Enabler SDKA software development kit that allows you to createAvalanche Enablers for Windows CE devices.Avalanche ManagementConsoleThe GUI that allows you to interact with andconfigure Avalanche Agents.Avalanche ManagerAvalanche MonitorAvalanche UpdateUtilityAvalanche SoftwarePackageAvalanche UpdateBOOTPclientDHCP<strong>Wavelink</strong> Corporation’s management applicationthat allows you to configure and manage mobiledevices throughout your network infrastructure.A component of certain Avalanche Enablers thatcommunicates with the Avalanche Agent and, atcertain times, checks for available updates.A component of certain Avalanche Enablers thatprovides most of the functionality. You can use theAvalanche Update Utility to configure the networkparameters of the mobile device, view the progressof a download, and/or install updates that have beendownloaded to the client.A specially bundled piece of software, for example afirmware update to a radio card or a commonly usedapplication, that you can download to a clientthrough Avalanche Manager.A download (or modification) that is available to aclient through Avalanche Manager. Examples ofupdates include software packages and networkprofiles. The deletion of orphaned packages from aclient through Avalanche Manager is another type ofupdate.Bootstrap Protocol. A protocol that allows clients toautomatically obtain IP parameters from a BOOTPserver.In the context of Avalanche Manager, an Avalancheclient. See Avalanche <strong>Client</strong>. In the context of the<strong>TN</strong>CE <strong>Client</strong>, a mobile device that connects via the<strong>TN</strong>CE <strong>Client</strong> to a host system.Dynamic Host Configuration Protocol. An IP servicethat allows DHCP clients to automatically obtain IPparameters from a DHCP server.
Glossary 171DNS.edfEmulation ParametersEmulation Parameters,globalEmulation Parameters,host specificEnablerEnabler ConfigurationUtilityEnabler ProfileEnabler SDKESS IDFTPFTP ServerDomain Name System. A service that provides hostname-to-IP address mapping.Enabler Definition FileA feature of the <strong>TN</strong>CE <strong>Client</strong> that allows you to preconfigureand install terminal emulation-relatedfunctions to a mobile device.Terminal emulation-related functions that apply toall host profiles that are configured on a mobiledevice.Terminal emulation-related functions that apply toonly a specific host profile that is configured on amobile device.In the context of Avalanche Manager, an AvalancheEnabler. See Avalanche Enabler.A software package that allows you to configure thevarious Avalanche Windows Enabler settings on aclient from the Avalanche Management Console.(Specific to the Windows Enabler.)In the context of the Avalanche Enabler SDK, a set ofparameters that a developer specifies that are usedby the Avalanche Enabler SDK to produce anAvalanche Enabler. The parameters of the profile arestored in an .edf file.See Avalanche Enabler SDK.Extended Service Set ID. The identifier of anextended service set for devices that areparticipating in an infrastructure mode wirelessLAN.File Transfer Protocol. A TCP-based service thatprovides connection-oriented file transfers.A host system that provides FTP services. Users arerequired to log into the FTP service to gain access tofiles that can be downloaded from the server.
172 <strong>PSC</strong> <strong>300</strong>-<strong>Series</strong> <strong>Wavelink</strong> <strong>TN</strong> <strong>Client</strong> User’s <strong>Guide</strong>gatewayGUIhosthost profileIBSSICMPinfrastructure modeIP addressLANleaselocalizationMAC addressA device on a local network through which data toother networks is routed. Also called a router.Graphical User InterfaceA server or workstation that hosts a specific softwareor network service.A service of the <strong>TN</strong>CE <strong>Client</strong> that allows you toinstall pre-configured host information (such as IPaddress and Telnet service TCP port) on mobiledevices.Independent Basic Service Set. See ad hoc mode.Internet Control Messaging Protocol. Part of theTCP/IP protocol suite that provides services fortesting IP network connections.A wireless network configuration wherein devicescommunicate with each other through an accesspoint.Internet Protocol address. A virtual address thatuniquely identifies a network connection.Local Area NetworkA DHCP lease. The parameters surrounding the IPaddress a client has obtained from a DHCP server.A service of the <strong>TN</strong>CE <strong>Client</strong> that allows you toconfigure the <strong>TN</strong>CE <strong>Client</strong> to display in a specificlanguage.Media Access Controller address. The hard-codedlayer-2 address of a network connection whichconsists of a 12-digit hexadecimal number. The first 6hexadecimal characters identify the manufacturer.The last 6 hexadecimal numbers are unique for eachnetwork device produced by the manufacturer. TheMAC address is also sometimes called the hardwareaddress.
Glossary 173Management ConsoleMBMbpsmobile devicenet masknetwork profileorphaned packagepingRAMRFrouterSDKselection criteriaIn the context of Avalanche Manager, the AvalancheManagement Console. See Avalanche ManagementConsole.MegabytesMegabits / secondA wireless device or a PC with a wireless networkconnection.See subnet mask.A set of pre-configured network parameters (ESS ID,IP address, and so forth) that can be downloaded toa client through Avalanche Manager.A software package that has been deployed to aclient through Avalanche Manager, but has beendisabled or is not recognized by the Agent. You mustorphan a software package before you can useAvalanche Manager to delete it from the client.An IP service that is used to test IP connectivity. Partof the ICMP service.Random Access Memory. Volatile memory in acomputer system.Radio Frequency. Usually used in the context of atype of network connection.See gateway.Software Development Kit.A feature of Avalanche Manager that allows you toconfigure a set of filters that target specific mobiledevices on the network. You can filter by MACaddress, IP address, device type, operating system,and so forth. Selection criteria are used to targetspecific mobile devices on the network forAvalanche Updates.
174 <strong>PSC</strong> <strong>300</strong>-<strong>Series</strong> <strong>Wavelink</strong> <strong>TN</strong> <strong>Client</strong> User’s <strong>Guide</strong>silent installsilent modesoftware packageA feature of the Avalanche Enabler that allows forthe installation of software packages on clientswithout the consent of the user at the client.A feature of the Avalanche Enabler that allows theAvalanche Monitor to run in the background on theclient in a manner that is transparent to the user atthe client.In the context of Avalanche Manager, an Avalanchesoftware package. See Avalanche Software Package.SSID Service Set Identifier. A unique name, up to 32characters long, that is used to identify a wirelessLAN. The SSID is attached to wireless packets andacts as a password to connect to a specific BSS orESS.static WEPsubnetsubnet maskTCP/IPTelnetTFTPStatic (or manual) implementation of WEP keys.When the administrator of the network changes theWEP key, users must manually select the correctkey.A logical network wherein each client isparticipating on the same IP network.A type of filter that allows IP clients to determinewhich part of their IP address defines the networkand which part defines the host.Transmission Control Protocol/Internet Protocol. Asuite of protocols that provides virtual addressing,connection-oriented and connectionlesscommunication, and a number of other networkservices and utilities.A TCP/IP utility that is used for terminal emulationand that allows a client to connect and interact witha remote host system.Trivial File Transfer Protocol. A UDP-based servicethat provides connectionless file transfers.
Glossary 175TelnetCE <strong>Client</strong>updateWEPWindows CEWindows EnablerWINS<strong>Wavelink</strong> Corporation application that providesclient-side terminal emulation services for MicrosoftWindows CE-based mobile devices.In the context of Avalanche Manager, an Avalancheupdate. See Avalanche Update.Wired Equivalent Privacy. An encryption standardfor wireless networks that provides the equivalentsecurity of a wired connection for wirelesstransmissions.A Microsoft Windows-based operating system formobile devices.An Avalanche Enabler that is designed for MicrosoftWindows 9x/ME/NT/2000/XP systems with installed802.11b wireless cards.Windows Internet Naming Service. A service thatprovides Windows name-to-IP address mapping.
176 <strong>PSC</strong> <strong>300</strong>-<strong>Series</strong> <strong>Wavelink</strong> <strong>TN</strong> <strong>Client</strong> User’s <strong>Guide</strong>
Index 177IndexNumerics802.11/a/b 169AaboutAvalanche client controls 65Avalanche updates 53emulation parameters 3, 29host profiles 3, 20localization 4, 38network profiles 57orphan packages 79<strong>TN</strong> <strong>Client</strong> 2updates 53access point 169accessingconfiguration manager 30configuration manager for globalsettings 30configuration manager for per-hostsettings 32host profiles 20, 42ad hoc mode 169agent 169ap 169autologin settings 27automatic wep 169Avalanche Agent, defined 169Avalanche client 169Avalanche client controlsabout 65accessing 65control tab 66properties tab 69using 65Avalanche Enabler 169Avalanche Enabler SDKedf, defined 171enabler profile, defined 171Avalanche Management Console,defined 170Avalanche Managerdefined 170managing clients 53using software packages 71Avalanche Monitor, defined 170Avalanche software package, defined 170Avalanche update 170Avalanche update utility, defined 170Avalanche updatesabout 53media 54performing 56preparing for rf updates 56preparing for serial updates 54Bbootp 170Cclient 170client licensing 41configuration manageraccessing 30accessing global settings 30accessing per-host settings 32com port parameters 99emulation - 5250 and 3270 - 3270parameters 105emulation - 5250 and 3270 - 5250parameters 107emulation - 5250 and 3270 - common 108emulation - common 112emulation - display 115emulation - keyboard 121emulation - printing 123emulation - sound 125
178 <strong>PSC</strong> <strong>300</strong>-<strong>Series</strong> <strong>Wavelink</strong> <strong>TN</strong> <strong>Client</strong> User’s <strong>Guide</strong>emulation - vt and HP - common 127emulation - vt and HP - HP 130emulation - vt and HP - vt 131emulation parameters 99scanner - Codabar 133scanner - Code11 135scanner - Code128 137scanner - Code39 139scanner - Code93 140scanner - common 142scanner - D2of5 153scanner - EAN13 154scanner - EAN8 156scanner - I2of5 157scanner - MSI 159scanner - UCC128 161scanner - UPCA 162scanner - UPCE0 163scanner - UPCEWEP1 165using 33using find function 36configuration settings 28configuringemulation parameters 29host profiles 19, 22host profiles, manually 41localization 37new host profile 44<strong>TN</strong> <strong>Client</strong> 10<strong>TN</strong> <strong>Client</strong> for multiple sessions 49connecting to a host 48control keys 47creating host profiles 23Ddemo licenses 41deployingnetwork profiles 64software packages 79<strong>TN</strong> <strong>Client</strong> 14dhcp 170disconnecting a session 49dns 171documentassumptions 1conventions 1downloading configurations 40Eediting terminal id 70emulation parametersabout 3, 29configuring 29defined 171global, defined 171host-specific, defined 171modifying 35enabler 171enabler configuration utility 171enabler profile 171enabling the <strong>TN</strong> <strong>Client</strong> 13ess id 171Ffiguresaccessing client settings 65accessing emulation parameters 31accessing per-host configurationparameters 32accessing the host profiles dialog box 21accessing the localization dialog box 39assigning a new terminal id 71Avalanche client controls propertiestab 69configuration manager 34configuration manager save icon 36configuring the maximum number ofsimultaneous sessions 51configuring the network profile settingscontrol tab 60
Index 179configuring the network profile settingsrouting tab 61configuring the network profile settingssecurity tab 62configuring the <strong>TN</strong> <strong>Client</strong> for multiplesessions 50control tab of Avalanche client controlsdialog box 67creating a new network profile 58creating a new software collection 7, 73disable a software package 80disabling the <strong>Wavelink</strong> <strong>TN</strong> <strong>Client</strong> softwarepackage 16emulation parameter information 34enabling a network profile 63Enabling a Software Package 78enabling the <strong>Wavelink</strong> <strong>TN</strong> <strong>Client</strong> softwarepackage 14host profiles autologin tab 28host profiles configuration tab 29host profiles dialog box 22host profiles host tab 25host profiles ibm settings tab 26host profiles vt settings 27inputting a string to find 37marking orphan packages for deletion onall clients 83modifying an emulation parameter 36naming a software collection 8, 73naming the network profile 59selecting the find function 37selecting the software collection 9, 75selecting to configure emulationparameters 12selecting to configure host Profiles 11selecting to configure the number ofsessions 51selecting to configure the settings of anetwork profile 59selecting to configure the softwarecollection 76selecting to configuring localization 13selecting to delete orphan packages fromthe client 81setting the default network profile 64software collection settings dialog box 77software package in softwarecollection 10, 76terminal id change pending 71find function 36ftp 171ftp server 171Ggateway 172gui 172Hhost 172host profile screen 45host profile, defined 172host profilesabout 3, 20accessing 20accessing, manually 42autologin settings 27configuration settings 28configuring 19, 22configuring new 44configuring, manually 41control keys 47creating 23host settings 24ibm settings 25, 46modifying 23modifying existing 42removing 24settings 45vt settings 27vt/hp settings 46host settings 24
180 <strong>PSC</strong> <strong>300</strong>-<strong>Series</strong> <strong>Wavelink</strong> <strong>TN</strong> <strong>Client</strong> User’s <strong>Guide</strong>Iibm settings 25ibss 172icmp 172infrastructure mode 172installation requirementsdevice requirements 5other requirements 5installingsoftware packages 72<strong>TN</strong> <strong>Client</strong> 6<strong>TN</strong> <strong>Client</strong> software package 7ip address 172Kkeyboard maps25-key <strong>PSC</strong> 335/345 3270 emulation keysequences 8925-key <strong>PSC</strong> 335/345 5250 emulation keysequences 8925-key <strong>PSC</strong> 335/345 hp emulation keysequences 9025-key <strong>PSC</strong> 335/345 keyboard maps 8925-key <strong>PSC</strong> 335/345 vt emulation keysequences 9038-key <strong>PSC</strong> 335/345 3270 emulation keysequences 9238-key <strong>PSC</strong> 335/345 5250 emulation keysequences 9138-key <strong>PSC</strong> 335/345 hp emulation keysequences 9338-key <strong>PSC</strong> 335/345 keyboard maps 9138-key <strong>PSC</strong> 335/345 vt emulation keysequences 9248-key <strong>PSC</strong> 345 3270 emulation keysequences 9548-key <strong>PSC</strong> 345 5250 emulation keys 9448-key <strong>PSC</strong> 345 hp emulation keysequences 9748-key <strong>PSC</strong> 345 keyboard maps 9348-key <strong>PSC</strong> 345 local terminal functions 9448-key <strong>PSC</strong> 345 vt emulation keysequences 96<strong>PSC</strong> 325 3270 emulation key sequences 86<strong>PSC</strong> 325 5250 emulation key sequences 85<strong>PSC</strong> 325 hp emulation key sequences 88<strong>PSC</strong> 325 keyboard maps 85<strong>PSC</strong> 325 local terminal functions 85<strong>PSC</strong> 325 vt emulation key sequences 87Llan 172launching <strong>TN</strong> <strong>Client</strong> 48lease 172licensingdemo licenses 41standard licenses 41localization 172about 4, 38configuring 37Mmac address 172management console 173managing clients with AvalancheManager 53mb 173mbps 173mobile device 173modifyingemulation parameters 35existing host profiles 42host profiles 23multiple sessionsconfiguring 49initiating a new session 52switching between active sections 52Nnet mask 173network profilesabout 57
Index 181Ocreating and enabling 58defined 173deploying 64using 53obtaining <strong>TN</strong> <strong>Client</strong> software package 6orphan packagesabout 79defined 173removing 79Pperforming updates 56ping 173Rram 173removinghost profiles 24orphan packages from all clients 81software packages 79rf 173rf updates 56router 173Ssdk 173selection criteria 173serial updates 54silent install 174silent mode 174software packagesdefined 174deploying 79installing 72orphan packages 79removing 79removing orphan packages 79using 71ssid 174standard licenses 41static wep 174subnet 174subnet mask 174Ttables25-key <strong>PSC</strong> 335/345 3270 emulation keysequences 8925-key <strong>PSC</strong> 335/345 5250 emulation keysequences 8925-key <strong>PSC</strong> 335/345 hp emulation keysequences 9025-key <strong>PSC</strong> 335/345 vt emulation keysequences 9038-key <strong>PSC</strong> 335/345 3270 emulation keysequences 9238-key <strong>PSC</strong> 335/345 5250 emulation keysequences 9138-key <strong>PSC</strong> 335/345 hp emulation keysequences 9338-key <strong>PSC</strong> 335/345 vt emulation keysequences 9248-key <strong>PSC</strong> 345 3270 emulation keysequences 9548-key <strong>PSC</strong> 345 5250 emulation keysequences 9448-key <strong>PSC</strong> 345 hp emulation keysequences 9748-key <strong>PSC</strong> 345 local terminal functions 9448-key <strong>PSC</strong> 345 vt emulation keysequences 96<strong>PSC</strong> 325 3270 emulation key sequences 86<strong>PSC</strong> 325 5250 emulation key sequences 85<strong>PSC</strong> 325 hp emulation key sequences 88<strong>PSC</strong> 325 local terminal functions 85<strong>PSC</strong> 325 vt emulation key sequences 87text-formatting conventions 2tcp/ip 174telnet 174TelnetCE client 175
182 <strong>PSC</strong> <strong>300</strong>-<strong>Series</strong> <strong>Wavelink</strong> <strong>TN</strong> <strong>Client</strong> User’s <strong>Guide</strong>terminal id, editing 70terminating a session 49tftp 174<strong>TN</strong> <strong>Client</strong>about 2components 3configuring 10configuring for multiple sessions 49connecting to a host 48deploying 14enabling 13installing 6installing software package 7launching 48multiple telnet sessions 49obtaining software package 6overview 2terminating a session 49uninstalling 15using 47Wwepautomatic 169defined 175static wep 174Windows CE 175Windows Enabler 175wins 175working with multiple telnet sessions 49Uuninstalling <strong>TN</strong> <strong>Client</strong> 15updatesabout 53defined 170media 54performing 56preparing for rf updates 56preparing for serial updates 54update, defined 175usingAvalanche client controls 65configuration manager 33find function 36network profiles 53software packages 71Vvt settings 27