This page records changes that have been made to this manual. This manual
was originally released at version -001
VersionDateDescription of Change
00209/96Added information on using the TRAKKER® Antares™
terminals with the Model 200 Controller. Made other
minor corrections throughout the entire manual.
Combined the information in the JANUS™ Devices QuickReference Guide with the Model 200 Controller User’s Manual.
00304/97Addendum 065395-001 was added to the manual. This
addendum supports version 2.4 of the controller software,
which includes VT and ANSI screen mapping and a direct
TCP/IP socket interface.
00410/97Added information from the addendum to the manual.
This manual supports controller software v3.0, which
includes 3270 and 5250 terminal emulation on devices that
run in Intermec’s 900 MHz radio frequency network. The
Script Builder tool was improved and a firmware upgrade
utility for the TRAKKER Antares RF terminals was added.
00507/98This manual supports controller software v3.1, which adds
DHCP and DNS support. It also contains information
about a new remote console option, new system
diagnostics, and new screen mapping functionality.
Page 3
test
Page 4
Quick Reference Guide
Fast Setup
Page 5
Intermec Technologies Corporation
6001 36th Avenue West
P.O. Box 4280
Everett, WA 98203-9280
U.S. service and technical support: 1-800-755-5505
U.S. media supplies ordering information: 1-800-227-9947
Canadian service and technical support: 1-800-688-7043
Canadian media supplies ordering information: 1-800-268-6936
Outside U.S. and Canada: Contact your local Intermec service supplier.
The information contained herein is proprietary and is provided solely for the purpose of
allowing customers to operate and/or service Intermec manufactured equipment and is not to
be released, reproduced, or used for any other purpose without written permission of Intermec.
Information and specifications in this manual are subject to change without notice.
1998 by Intermec Technologies Corporation
All Rights Reserved
The word Intermec, the Intermec logo, JANUS, IRL, TRAKKER, Antares, Adara, Duratherm,
EZBuilder, Precision Print, PrintSet, Virtual Wedge, and CrossBar are either trademarks or
registered trademarks of Intermec.
Throughout this manual, trademarked names may be used. Rather than put a trademark
( or ) symbol in every occurrence of a trademarked name, we state that we are using the
names only in an editorial fashion, and to the benefit of the trademark owner, with no intention
of infringement.
Page 6
Contents
Contents
About Fast Setup 5
Network Adapter Cards 5
Using Online Help 6
Step 1 - Complete the Worksheets 8
Step 2 - Set Up the Controller 8
Power Cord 9
Monitor 9
Keyboard 9
Mouse 9
Step 3 - Install the Controller 10
Connecting to Your Data Collection Network 10
Connecting to Your Host Environment 10
Turning on the Controller 11
About the Fast Setup Main Menu 12
Step 4 - Set the System Parameters 13
Step 5 - Set Up the Data Collection Environment 16
Configuring an RF Card for Your Network 18
Configuring a UDP Plus Network 19
Configuring an Intermec Controller for Your Network 21
Verify Your Data Collection Environment 21
Step 6 - Set Up the Host Communications Environment 24
Step 7 - Configure the Host Environment Parameters 30
Setting Up Telnet Terminal Emulation 31
Setting Up 5250 SNA Terminal Emulation 36
iii
Page 7
Fast Setup Quick Reference Guide
Setting Up 3270 SNA Terminal Emulation 41
Setting Up Peer-to-Peer Links 47
Setting Up a Terminal Session 53
Verify Your Host Connection 65
Step 8 - Start the Controller 66
Where Do You Go From Here? 68
Index
I
iv
Page 8
This quick reference guide explains how to use Fast Setup to configure the Model
200 Controller.
About Fast Setup
Use Fast Setup to configure the Model 200 Controller quickly so you can
• demonstrate the controller.
• verify your network environment is functioning.
• learn about the controller and its graphical user interface (GUI) before
using Advanced Setup.
• do preliminary configuration for your data collection network.
Fast Setup uses default values for many of the configuration parameters and
it only prompts you to enter a few required parameters.
When you configure the controller in Fast Setup, you set up a host
connection, define your Intermec equipment, and set up the routing for data
to the correct destination.
Fast Setup Quick Reference Guide
Network Adapter Cards
Depending on the upline network cards in your controller, you can connect
the controller to
• any TCP/IP host on an Ethernet or token ring network that supports
Telnet.
• any SNA host on a token ring, twinaxial, coaxial, or SDLC network that
supports APPC and 5250 or 3270 terminal connections.
Note: You can also set up VT, ANSI, 3270, and 5250 terminal sessions, but you
can only start these terminal sessions on your controller. Fast Setup does not let
you configure screen mapping.
Depending on the downline cards in your controller, you can connect the
controller to
The controller also has two serial ports (COM1 and COM2) that let you
connect external Intermec controllers for CrossBar™ network support, a
9180 Network Controller, an uninterruptable power supply, or an external
modem.
Using Online Help
The Model 200 Controller includes online help that provides descriptions of
the toolbars, dialog boxes, and options. Help also includes step-by-step
procedures and some background information.
To get help
• Choose the Help button.
The Help window opens and displays the topic for the toolbar or dialog box
you were using. If you requested Help from the main menu, the Getting
Started topic appears. You can resize and move your Help window to see
more of a topic at one time or to see more of the configuration window.
Colored or underlined text indicates that you can jump to topics.
To jump to another help topic
• Double-click the topic name. Or, press Tab until the topic is highlighted,
and then press Enter.
To use the help buttons
• Choose Previous or press Esc to jump to the previous topic.
• Choose Search to search for Help on a specific word or phrase.
• Choose Index to look up a topic in the Index.
• Choose Contents to look up a topic in the Contents.
6
Page 10
Connecting the Controller to Your Data Collection Network
Fast Setup Quick Reference Guide
9181
RS- 485
900 MHz
Host
Model 200
Controller
2.4 GHz
T2425
JG2050
JG2020
Access Point
Ethernet
RS-232
CrossBar
9154
9189
RS-232
JR2020
3400
9445
J2050
3400
J2010
0200-024
7
Page 11
Fast Setup Quick Reference Guide
Step 1 - Complete the Worksheets
Before you use Fast Setup, complete the relevant worksheets in Appendix E
in the Model 200 Controller User’s Manual. You will need to obtain much of
this information from your network administrator. After you have
completed the worksheets, you will have all the information you need to
run Fast Setup and to configure the controller successfully.
Step 2 - Set Up the Controller
Connect these accessories to the Model 200 Controller: power cord, monitor,
keyboard, and mouse. Use the figure below to help you locate the ports for
these accessories. For help, see Chapter 2, “Setting Up the Controller,” in the
Model 200 Controller User’s Manual.
Model 200 Controller Rear Panel
Fan
AC
out
AC
in
Voltage
110V
Keyboard
port
select
KEYBD
Mouse
port
COM1
MOUSE
COM2
LPT1VIDEO
LPT1
Video
port
0200-003
8
Page 12
Fast Setup Quick Reference Guide
Power Cord
The standard power cord that comes with the controller is a 110V U.S. cord.
If you need another power cord, contact your local Intermec representative.
Note: Intermec recommends that you plug the power cord into a surge protector or
an uninterruptable power supply.
1. Plug the power cord’s 3-pin connector into the AC in receptacle in the
rear panel of the controller.
2. Plug the other end of the power cord into an AC power outlet, a surge
protector, or an uninterruptable power supply.
3. Set the voltage select switch to 110V or 220V.
Monitor
1. Plug the end of the monitor cable into the video port in the rear panel of
the controller.
2. Attach one end of the power cable to the monitor and the other end to an
AC outlet.
Keyboard
• Plug the keyboard connector into the keyboard port in the rear panel of
the controller.
Mouse
• Plug the mouse connector into the mouse port in the rear panel of the
controller.
9
Page 13
Fast Setup Quick Reference Guide
Step 3 - Install the Controller
You must physically connect the Model 200 Controller to your data
collection network and to your host environment.
Connecting to Your Data Collection Network
• Connect the controller to your data collection network. For help, see
“Installing the Controller” in the chapter designed for your downline
network in the Model 200 Controller User’s Manual.
Connecting to Your Host Environment
• Connect the controller to your host environment. For help, see “Installing
the Controller” in the chapter designed for your upline network in the
Model 200 Controller User’s Manual.
Note: If you are using 10Base2, make sure that you connect the cable to the port
and connection before turning on the controller.
10
Page 14
Fast Setup Quick Reference Guide
Turning on the Controller
When you turn on the controller for the first time, a dialog box appears that
lists the network adapter cards, RF controller cards, and COM ports in your
controller. Choose one of the following options:
• If you want this dialog box to appear every time the controller boots,
choose Show at Boot Time. This dialog box may be helpful when
troubleshooting the controller.
• If you never want this dialog box to appear, choose Hide at Boot Time.
The main menu appears. Choose Fast Setup. The Fast Setup main menu
appears.
11
Page 15
Fast Setup Quick Reference Guide
About the Fast Setup Main Menu
This main menu appears whenever you turn on the Model 200 Controller. In
the title bar, [Save] and [Activate] appear when you make changes to the
configuration that you need to save and activate. The Fast Setup main menu
has three parts.
Toolbar Buttons
The buttons across the top of the main menu are grouped into two sections:
Fast Setup and Advanced Setup. This quick reference guide (QRG)
addresses how to use the first button, Fast Setup. For more information on
Advanced Setup, see the Model 200 Controller User’s Manual.
Sidebar Buttons
The buttons on the right side of the main menu perform system functions on
the controller. This QRG explains how to use Save Configuration, Save and
Activate, Start Data Collection, Stop Data Collection, Shutdown Controller,
System Parameters, and some of the commands in the System Maintenance
dialog box. For more information on the other buttons, see the Model 200Controller User’s Manual.
Checklist Box
The checklist box on the bottom left side of the main menu lists the three
steps you complete to configure the controller in Fast Setup:
1. Local Network Adapters.
2. Downline Network.
3. Host Connections.
12
This box is checked after you enter the required parameters that identify
the network adapter cards in the controller to the network.
This box is checked after you configure the controller for your downline
data collection network, including configuring any RF controller cards,
the UDP Plus network, and any external Intermec controllers.
This box is checked after you configure the host connections for terminal
emulation, peer-to-peer applications, or terminal sessions for screen
mapping.
Page 16
Fast Setup Quick Reference Guide
Step 4 - Set the System Parameters
When you set these system parameters, you are defining the operating
parameters for the Model 200 Controller.
13
Page 17
Fast Setup Quick Reference Guide
FieldDescriptionValueDefault
Send to downline
devices every...
...minutesThis field specifies how often in
File Transfer
Time
ID delimiterThe character that the data collection
Bad ID response
(Optional)
Max connections
(Peer-to-peer)
Strip pad
(Peer-to-peer,
APPC only)
This check box determines if the Model
200 Controller sends its time to all
external Intermec controllers.
minutes the controller sends the time
synchronization message.
This box specifies how long in seconds
the controller waits for a response from
the data collection device when it is
downloading files, before it times out.
devices use to separate the transaction
ID from the transaction fields.
The message that the controller sends to
the source of the transaction if the
controller does not recognize the
transaction ID.
A tuning value that defines the
maximum number of connections for
each NetComm process.
The pad character, which is used by
fixed-length transactions from a host
application, that you want the
controller to remove before sending the
transaction.
Check, ClearCheck
0 to 999960
0 to 9999180
Predefined, (comma)
1 to 39 charactersNone
1 to 25610
PredefinedNone
Auto-start data
collection when
the Model 200
Controller is
booted.
Terminal
Emulation Setup
Screens
This check box determines if the
controller starts data collection when it
is booted.
This box allows you to customize
which terminal emulation buttons
appear in the main menu.
14
Check, ClearClear
VT/ANSI, 5250,
3270
All
Page 18
Fast Setup Quick Reference Guide
To set the system parameters
1. From the main menu sidebar buttons, choose System Parameters. The
System Parameters dialog box appears.
2. Enable or disable time synchronization. A check in the check box
indicates that time synchronization is enabled. Enter how often you want
the controller to send the time broadcast to all external Intermec
controllers and BRUs.
3. In the File Transfer Time box, enter how long you want the controller to
wait for a response from a device when it is downloading files to that
device, before it times out.
4. In the ID delimiter field, click the down arrow on the right side of the
field. A list of available delimiters appears. Select the delimiter that you
want to use to separate the transaction ID from the rest of the transaction
fields in data coming from data collection devices.
5. (Optional) In the Bad ID response field, enter the message that you want
sent back to the source of the transaction if the controller does not
recognize the transaction ID.
6. In the Peer-to-Peer Network Connection Parameters box, enter the
maximum number of connections for each NetComm process.
7. (Peer-to-peer applications, APPC only) In the Strip pad field, click the
down arrow on the right side of the field. A list of characters that a host
application may use to pad fixed-length transactions appears. Select the
character that the controller removes before sending on the transaction.
8. In the Auto-Start box, enable or disable the controller from automatically
starting data collection when it boots. A check in the check box indicates
that the controller automatically starts data collection.
9. In the Terminal Emulation Setup Screens box, choose which type of
terminal emulation you want displayed in the main menu.
10. Choose OK to save your changes and return to the main menu.
15
Page 19
Fast Setup Quick Reference Guide
Step 5 - Set Up the Data Collection Environment
Worksheets available
•Model 200 Controller to RF Card Worksheet
•Model 200 Controller to TRAKKER Antares Terminals Worksheet
•Model 200 Controller to 9180 and CrossBar Worksheet
•Model 200 Controller to 9180 Worksheet
•Model 200 Controller to CrossBar Worksheet
You can use Fast Setup to define the parameters for any external Intermec
controllers that exist downline from the Model 200 Controller, for RF
controller cards that you may have inside the controller, and for the
controller to communicate with the TRAKKER® Antares™ terminals using
UDP Plus. Fast Setup assumes that any downline device that you add to the
network is configured with factory defaults.
RF controller cards Fast Setup configures the controller to communicate
with the first 9181 BRU on RF Card 1 and it enables this BRU. It also sets up
this BRU to communicate with the first eight RF devices. If you have more
than one RF card or more than one BRU, you will need to configure their RF
parameters. For help configuring the other RF card, see Chapter 3,
“Connecting to the Intermec RF Network” in the Model 200 Controller User’s
Manual. For help configuring the BRU, see the 900 MHz RF Equipment User’s
Manual.
UDP Plus network Fast Setup configures the controller to communicate with
JANUS devices and TRAKKER Antares terminals through the access points
on an Ethernet or token ring network. You also need to define IP addresses
for each of the terminals. Before you can verify your connection to the UDP
Plus network, you must define an IP address for the Ethernet or token ring
card. For help, see “Ethernet Adapter Card” and “Token Ring Adapter
Card” later in this quick reference guide.
External Intermec controllers Fast Setup configures a few of the parameters
that let the controller communicate with the external Intermec controller.
However, you may still need to configure your external controller to send
and receive transactions to the devices. Refer to your controller’s user’s
manual.
Note: Once you define your external Intermec controllers, your RF controller cards,
or UDP Plus and you choose Configure, Fast Setup does not let you edit the
configuration. You need to use Advanced Setup to change any parameters.
16
Page 20
Fast Setup Quick Reference Guide
To get to the Fast Setup for Downline Network dialog box, from the main
menu choose Fast Setup and then choose Downline Network.
FieldDescriptionValueDefault
Configured
Connections
Available
Connections
The external Intermec controllers, RF
controller cards, or UDP Plus that you
have already configured.
The UDP Plus, RF controller cards, or
any external Intermec controllers that
are available to be configured.
NoneNone
If you have an
open serial port,
the direct connect
controllers are
listed.
If you have an
unconfigured RF
card or UDP
Plus, it is listed.
None
17
Page 21
Fast Setup Quick Reference Guide
FieldDescriptionValueDefault
Serial portThe serial port on the controller that
connects to the external Intermec
controller.
RFNC addressThe radio frequency network address of
the RF controller card. Devices use this
address to communicate with the BRUs
attached to this card.
Network IDThe network ID of the RF controller
card. Devices use this ID during a
channel search to locate the RF
controller card’s RFNC address.
RF channelThe channel that the RF controller card
will use.
Multi-Drop and
RF
Point-to-Point
(9161 only)
The number of device addresses to be
enabled for the RF controller card, UDP
Plus, or an external Intermec controller.
The number of device addresses to be
enabled on the 9161 controller.
Configuring an RF Card for Your Network
COM1, COM2COM1
0 to 630
If 0 is being used,
the next available
number is the
default.
1 to 2541
If 1 is being used,
the next available
value is used.
0 to 60
Varies8
Varies9161-01 is 8
9161-02 is 0
1. In the Available Connections list box, select the RF card you want to
2. In the RF Card Parameters box, enter the RFNC address, network ID,
3. In the Multi-Drop and RF field, enter the number of device addresses
4. Choose Configure to save your changes. The RF card appears in the
5. Choose Close to close the dialog box and return to the main menu.
18
configure.
and RF channel.
you want to enable on the controller.
Configured Connections list box.
Page 22
Fast Setup Quick Reference Guide
Configuring a UDP Plus Network
1. In the Available Connections list box, select UDP Plus.
2. Choose Configure to save your changes. The Setup for UDP Plus
Terminals dialog box appears.
To set up the UDP Plus devices using a DNS server
1. In the Number of terminals to enable field, enter the number of logical
names that you want the controller to generate.
2. Check the Use DNS check box.
Note: Before you can use DNS, you must use Advanced Setup to configure a
DNS server in the DNS Configuration dialog box.
3. In the Base logical name field, enter the base name that the controller
uses to create a unique logical name for each terminal. The controller
appends a sequential 3-digit number to this name for each terminal.
19
Page 23
Fast Setup Quick Reference Guide
4. In the Domain field, enter the name of the domain that all of the
terminals are in.
Note: If you enable the Use DNS check box and you do not enter a domain, the
server searches the domains that are listed in the DNS Configuration dialog box.
5. Choose OK. The controller generates the logical names and you return to
the Fast Setup for Downline Network dialog box.
6. Choose Close to close the dialog box and return to the main menu.
To set up the UDP Plus devices using the controller to generate IP addresses
1. In the Number of terminals to enable field, enter the number of IP
addresses that you want the controller to generate.
2. Clear the Use DNS check box.
3. In the Base logical name field, enter the base name that the controller
uses to create a unique logical name for each terminal. The controller
appends a sequential 3-digit number to this name for each terminal.
20
4. In the Starting IP address field, enter the starting IP address. The IP
address must be a valid IP v4 address.
5. In the Subnet mask field, enter the subnet mask that the server uses to
validate the IP addresses. The controller verifies that they do not cross a
subnet boundary.
6. Choose OK. The controller assigns valid sequential logical names and IP
addresses to the terminals starting with the starting IP address and then
you return to the Fast Setup for Downline Network dialog box.
7. Choose Close to close the dialog box and return to the main menu.
Page 24
Fast Setup Quick Reference Guide
Configuring an Intermec Controller for Your
Network
1. In the Available Connections list box, select the external Intermec
controller you want to configure.
2. In the Serial port field, click the down arrow on the right side of the field.
A list that contains the available serial ports appears. Choose the serial
port on the Model 200 Controller that is connected to the external
controller.
3. In the End Devices Enabled box, enter the number of Multi-Drop or
Point-to-Point device addresses you want to enable on the controller.
ProtocolControllerEnd Devices Enabled
Multi-Drop and RF9180 v1.x, 9180 v2.x0 through 128
91540 through 32
9161-020 through 128
Point-to-Point9161-010 through 16
9161-020 through 12
4. Choose Configure to save your changes. The controller appears in the
Configured Connections list box.
5. Choose Close to return to the main menu.
Verify Your Data Collection Environment
Once you configure the Fast Setup for Downline Network dialog box, you
may want to verify that you have a connection between the Model 200
controller and a device.
When sending a transaction to a device (destination), make sure that your
device is ready to accept the transaction. If your device is not ready, the
transaction is written to the Hot Standby file. If the device does not know
how to interact with the Hot Standby file, subsequent transactions will also
be written to the Hot Standby file. In this case, clear the Hot Standby file
before sending another transaction to the device. For help, see “Clearing the
Hot Standby Files” in Appendix A in the Model 200 Controller User’s Manual.
21
Page 25
Fast Setup Quick Reference Guide
Before you verify your data collection environment, make sure you activate
your current configuration and start data collection.
To get to the Send Transaction dialog box, from the main menu sidebar
buttons choose System Maintenance. The System Maintenance dialog box
appears. Select Send Transactions and then choose Start. The Send
Transaction dialog box appears.
FieldDescriptionValueDefault
Source ID
(Optional)
Destination ID
(Optional)
Transaction ID
(Optional)
Data or SystemThis field identifies the transaction as
Data (Optional)This field contains any data that you
This field can contain the destination
name that you want to use as the source
of the transaction.
This field can contain the logical name
of the device.
This field can contain the transaction ID
of the transaction that you want to send
to all devices that accept it.
either a data or a system transaction.
want to send with the transaction ID.
22
1 to 16
alphanumeric
characters
1 to 16
alphanumeric
characters
1 to 20
alphanumeric
characters
D, SD
1 to 1024
characters
None
None
None
None
Page 26
Fast Setup Quick Reference Guide
To verify your data collection environment
1. (Optional) In the Source ID field, enter a destination name that you want
to use as the source of the transaction.
2. If you want to send the transaction to one device, in the Destination ID
field enter the logical name of the device that you are using to verify the
connection.
Note: If you are using the Send Transactions feature to verify your host
connection, enter the name of the host application.
Or, if you want to send the transaction to all the devices that are
configured to accept it, in the Transaction ID field enter the unique name
of the transaction.
3. In the Data or System field, enter D or S. This field defines the
transaction as either a data or a system transaction.
4. (Optional) In the Data field, enter any data you want to send with the
transaction ID.
5. Choose Send to send the transaction to the device.
6. Choose Close to close the dialog box and return to the System
Maintenance dialog box.
7. Choose Close to return to the main menu.
23
Page 27
Fast Setup Quick Reference Guide
Step 6 - Set Up the Host Communications
Environment
To set up the host communications environment, you need to configure any
network adapter cards in your Model 200 Controller. The network adapter
cards that your controller may contain are:
• Ethernet
• token ring
• coaxial
• twinaxial
• SDLC
To configure the network adapter cards
1. From the main menu, choose Fast Setup.
2. Choose Local Network Adapter.
24
Note: Fast Setup grays out the buttons for any network adapter cards that are
not installed in your controller.
3. Choose the button for the network adapter card you want to configure
and follow the appropriate instructions in this section.
Page 28
Fast Setup Quick Reference Guide
Ethernet Adapter Card
If you are using Ethernet adapter cards in the controller in a TCP/IP
network, use Fast Setup to enter the parameters required for the TCP/IP
protocol for each of the cards. Use the information from the Network
Adapter Cards Worksheet to help you fill in the fields in this dialog box.
Note: The default setting for the Ethernet adapter card is 10BaseT. Contact your
local Intermec representative if you are using 10Base2 or 10Base5.
Note: If your controller contains two cards (two Ethernet cards or one Ethernet and
one token ring card) that communicate using TCP/IP, each card must use a
different subnet.
If you are not using the Ethernet adapter cards in a TCP/IP network, you do
not need to configure them.
25
Page 29
Fast Setup Quick Reference Guide
FieldDescriptionValueDefault
Ethernet TCP/IP
card
Use DHCPThis check box enables this network
Local host name
(Optional)
Local IP addressThe IP address that identifies the
Subnet maskThe mask that is used in the IP protocol
The Ethernet card that you are
configuring.
adapter card to be administered by a
DHCP server.
A meaningful name that identifies the
controller to the network.
Ethernet card. The IP address must be a
valid IP v4 address.
layer to separate the subnet address
from the local IP address.
xxx.xxx.xxx.xxx
where xxx is a
value between 0
and 255
xxx.xxx.xxx.xxx
where xxx is a
value between 0
and 255
Ethernet 1
ACCNET
None
Calculated based
on IP address
4. In the Ethernet TCP/IP Card field, click the down arrow on the right
5. To enable DHCP, check the Use DHCP check box. Go to Step 9.
26
side of the field. A list of Ethernet cards that are installed in your
controller appears. Select the card you want to configure.
Note: If you have two or more 10 Mbps Ethernet cards, Ethernet 1 is the
Ethernet card that is in the slot the furthest left if you are facing the controller
front panel. If you have a 100 Mbps Ethernet card, it is Ethernet 1.
Or, to disable DHCP, clear the Use DHCP check box. Go to Step 6.
Page 30
Fast Setup Quick Reference Guide
6. (Optional) In the Local host name field, enter a meaningful TCP/IP host
name for the controller.
7. In the Local IP address field, enter the address that identifies this
Ethernet card in the controller (host) to the network. This IP address
must be a valid IP v4 address.
8. In the Subnet mask field, enter the mask used in the IP protocol layer to
separate the subnet address from the local IP address.
9. Choose OK to save your changes and return to main menu.
Token Ring Adapter Card
If you are configuring the token ring card in the controller for a TCP/IP
network, you need to use Advanced Setup. For help, see Chapter 5,
“Connecting to an Ethernet/Token Ring Network” in the Model 200Controller User’s Manual.
If you are not using your token ring card in a TCP/IP network, you do not
need to set any parameters for a token ring adapter connection. All
parameters are set to default values. If you choose Token Ring, a message
box appears.
Choose OK to close the message box and return to the main menu.
Coaxial Adapter Card
You do not need to set any parameters for a coaxial adapter connection. All
parameters are set to default values. If you choose Coaxial, a message box
appears.
Choose OK to close the message box and return to the main menu.
27
Page 31
Fast Setup Quick Reference Guide
Twinaxial Adapter Card
If you have a twinaxial adapter card in the controller, you can use Fast
Setup to establish a twinaxial connection between the controller and your
host. Use the information from the Network Adapter Cards Worksheet to
help you fill in the Controller address field in this dialog box.
FieldDescriptionValueDefault
Controller
address
The unique host connection address.0 to 60
To set the controller address
1. Choose Twinaxial. The Twinaxial Protocol Configuration dialog box
appears.
2. In the Controller address field, enter the host connection address. Each
twinaxial device on a twinaxial line must have a unique address.
3. Choose OK to save your changes and return to the main menu.
28
Page 32
Fast Setup Quick Reference Guide
SDLC Adapter Card
If you have an SDLC adapter card in the controller, you can use Fast Setup
to establish an SDLC connection between the controller and your host. Use
the information from the Network Adapter Cards Worksheet to help you fill
in the Local station field in this dialog box.
Fast Setup assumes that you are using a leased line for your SDLC
configuration. To change this parameter, you must use Advanced Setup. For
help, see Chapter 7, “Connecting to an SDLC Network” in the Model 200
Controller User’s Manual.
FieldDescriptionValueDefault
Local stationThe address of the controller on the
SDLC network.
To configure the SDLC adapter
1. Choose SDLC. The SDLC Adapter Configuration dialog box appears.
2. In the Local station field, enter the controller station address. This
address must match the controller workstation address defined on the
host.
3. Choose OK to save your changes and return to the main menu.
01 to FE01
29
Page 33
Fast Setup Quick Reference Guide
Step 7 - Configure the Host Environment Parameters
You need to define the host environment parameters that tell the Model 200
Controller how to communicate with the host. Perform one of these
procedures:
• Set up VT100/220/320, ANSI, 5250, or 3270 terminal emulation.
• Set up peer-to-peer links to run remote TCP/IP or APPC applications.
• Set up VT100/220/320, ANSI, 5250, or 3270 terminal sessions for screen
mapping.
Note: Once you define your hosts and you choose OK, Fast Setup does not let you
edit the configuration. You need to use Advanced Setup to change any parameters.
To configure the host environment parameters
1. From the main menu, choose Fast Setup.
2. Choose Host Connection.
30
3. Choose the button for the type of communications you want to configure
and follow the appropriate instructions in this section.
Page 34
Fast Setup Quick Reference Guide
Setting Up Telnet Terminal Emulation
You can use Fast Setup to set up VT100/220/320 or ANSI terminal
emulation (TE) between JANUS™ devices and TRAKKER Antares terminals
and your TCP/IP hosts. You can also set up TN5250 or TN3270 TE between
your JANUS 2.4 GHz RF devices that are running UDP Plus and your
JANUS 900 MHz RF devices and an IBM host that supports Telnet. You
need to identify all remote host names and their IP addresses.
You also need to decide which terminals from the Available Terminals list
box you want to explicitly link to a host. If an explicit link is set up between
a terminal and a host, it means that the terminal can only start TE sessions
with that host. If no explicit link is set up, the terminal can start a TE session
with any host in the Host Name list. The controller starts a TE session with
the host that is configured on the terminal.
You can link as many device addresses as you want. However, the number
of terminals that can simultaneously communicate through the controller
depends on
• the number of devices you enabled in the Fast Setup for Downline
Network dialog box.
• the number of terminals in your terminal license.
Note: You may need to load the correct TE software on all of the JANUS devices
that you will be using as terminals. This software is available on the Model 200
Controller. Refer to Chapter 8, “Using Terminal Emulation” in the Model 200
Controller User’s Manual.
Use the information from the Telnet Terminal Emulation Worksheet to help
you fill in this dialog box.
31
Page 35
Fast Setup Quick Reference Guide
FieldDescriptionValueDefault
Host NameThis list box contains the names of the
defined TCP/IP hosts.
Host Name Linked Terminals
Available
Terminals
The list of terminals that are linked to a
selected host.
The list of all the terminals that are
available to link to a host.
2. Make sure you have added all the Telnet hosts that the terminals will
access. The Host Name list box contains all the defined host names.
To add a host, follow the instructions in “Adding a TCP/IP Host” in the
next section.
3. (Optional) Create any explicit links between hosts and terminals.
a. In the Host Name list box, select the host that you want to link to a
terminal.
b. In the Available Terminals list box, select the logical name of the
terminal you want to link to the host.
c. Choose Link. The host name and the logical name appear in the Host
Name - Linked Terminals list box.
4. (Optional) Unlink any explicit links between hosts and devices.
a. In the Host Name - Linked Terminals list box, select the terminal that
you want to unlink from a host.
b. Choose Unlink. The host name and the logical name are removed
from the Host Name - Linked Terminals list box.
5. Choose Close to close this dialog box and return to the main menu.
33
Page 37
Fast Setup Quick Reference Guide
Adding a TCP/IP Host
To communicate with TCP/IP hosts, the Model 200 Controller must know
their IP addresses. You can either use DNS to resolve these IP addresses or
you can enter them in manually.
FieldDescriptionValueDefault
Host nameThe name that logically identifies the
TCP/IP host to the network.
Use DNSThis check box determines if you use a
DNS server to resolve the IP address of
this host.
IP addressThe address that identifies the TCP/IP
host to the network.
1 to 256
alphanumeric
characters
Check, ClearClear
xxx.xxx.xxx.xxx
where xxx is a
value between 0
and 255.
None
None
34
Page 38
Fast Setup Quick Reference Guide
To determine the host IP address using DNS
1. From the Telnet Terminal Emulation Configuration dialog box, choose
Add. The TCP/IP Host Connection dialog box appears.
2. In the Host name field, enter the abbreviated or long host name. If you
enter the abbreviated name, the controller searches the domain names in
the DNS Configuration dialog box to determine the long host name.
3. Enable the Use DNS check box.
Note: Before you enable this check box, you must first configure a DNS server
in the DNS Configuration dialog box.
4. (Optional) Choose Resolve. The controller searches in the domains that
are listed in the DNS Configuration dialog box for the host name and
resolves the IP address.
5. Choose OK to save your changes and return to the Telnet Terminal
Emulation Configuration dialog box.
To configure the host IP address manually
1. From the Telnet Terminal Emulation Configuration dialog box, choose
Add. The TCP/IP Host Connection dialog box appears.
2. In the Host name field, enter the host name.
3. Make sure the Use DNS check box is disabled.
4. In the IP address field, enter the host’s IP address.
5. Choose OK to save your changes and return to the Telnet Terminal
Emulation Configuration dialog box.
35
Page 39
Fast Setup Quick Reference Guide
Setting Up 5250 SNA Terminal Emulation
You can use Fast Setup to set up 5250 SNA terminal emulation (TE) between
your JANUS 900 MHz RF devices or your TRAKKER Antares terminals and
SNA hosts. You need to identify all remote host names.
You also need to decide which terminals from the Available Terminals list
box you want to explicitly link to a host. If an explicit link is set up between
a terminal and a host, it means that the terminal can start a TE session only
with that host. If no explicit link is set up, the terminal can start a TE session
with any host in the Host Name list. It will start a TE session with the host
that is configured on the terminal.
You can link as many terminals as you want. However, the number of
terminals that can simultaneously communicate through the controller
depends on
• the number of devices you enabled in the Fast Setup for Downline
Network dialog box.
• the mode you are using to define the terminal session characteristics
between the controller and the SNA host. The default mode is #INTER.
For help, see “Creating Terminal Sessions” in Chapter 10 in the Model200 Controller User’s Manual.
36
• the number of terminals in your terminal license.
• the maximum number of virtual devices the AS/400 5250 Display Station
Pass-Through program supports.
Note: Your JANUS 900 MHz RF devices and your TRAKKER Antares terminals
come with the 5250 TE software already loaded. However, this software is also
available on the Model 200 Controller.
Also, you must configure your terminals to use the SNA protocol.
Use the information from the 5250 Terminal Emulation Worksheet to help
you fill in this dialog box.
Page 40
Fast Setup Quick Reference Guide
FieldDescriptionValueDefault
Host NameThis list box contains the names of the
defined SNA hosts.
Use device
names
Host Name Linked Terminals
Available
Terminals
This check box determines if the
selected host in the Host Name list box
uses the logical name of the devices
when establishing terminal sessions.
The list of terminals that are linked to a
selected host.
The list of all terminals that are
available to link to a host.
2. Make sure you have added all the SNA hosts that the terminals will
access for terminal emulation. The Host Name list box contains all the
defined host names.
To add a host, follow the instructions in “Adding an IBM SNA Host” in
the next section.
3. Check the Use device names check box if you want the selected host to
use the logical name of the devices when establishing terminal sessions.
A Yes appears next the host name under the Names column.
4. (Optional) Create any explicit links between hosts and terminals.
a. In the Host Name list box, select the host that you want to link to a
terminal.
b. In the Available Terminals list box, select the terminal you want to
link to the host.
c. Choose Link. The terminal appears in the Host Name - Linked
Terminals list box.
38
5. (Optional) Unlink any explicit links between hosts and terminals.
a. In the Host Name - Linked Terminals list box, select the terminal you
want to unlink from a host.
b. Choose Unlink. The host name and logical name are removed from
the Host Name - Linked Terminals list box.
6. Choose Close to close this dialog box and return to the main menu.
Page 42
Fast Setup Quick Reference Guide
Adding an IBM SNA Host
FieldDescriptionValueDefault
Host nameA name that identifies this SNA host.
You can use this internal name to make
the host LU name more meaningful.
Adapter cardThe network adapter card you are
using to connect to the host.
Network IDIdentifies the network ID on which the
host resides. This ID must match the
network ID configured on the host.
Host LUThe LU name that identifies the host.
This field must match the control point
(CP) name or node name of the host.
Local PU
(Ethernet or
token ring only)
Address
(Ethernet or
token ring only)
A unique PU name for the host that
allows the terminals to communicate
with more than one host using the same
upline adapter card.
The LAN adapter address of the host.Token ring MAC
1 to 8
alphanumeric
characters
Ethernet, token
ring, twinaxial,
SDLC
1 to 8
alphanumeric
characters
1 to 8 alphanumeric and
special characters
8 uppercase
alphanumeric or
special characters
address format
None
Ethernet 1
Controller’s
network ID from
the SNA local
node definition
Host name
SNA node name
+ 2-digit suffix,
starting with 01
None
39
Page 43
Fast Setup Quick Reference Guide
To add an IBM SNA host
1. From the 5250 Terminal Emulation Configuration dialog box, choose
Add. The Host Connection Configuration dialog box appears.
2. In the Host name field, enter a meaningful name for the host.
3. In the Adapter card field, click the down arrow on the right side of the
field. A list that contains the available adapter cards appears. Select the
adapter card you are using to connect to the host.
4. In the Network ID field, enter the network ID of the network on which
the host resides.
5. In the Host LU field, enter the LU (logical unit) name that identifies the
host. This field must match the control point (CP) name or node name of
the host.
6. (Ethernet or token ring only) In the Local PU field, enter a unique PU
(physical unit) name for the host. The default name is the local SNA
node name plus a 2-digit suffix.
7. (Ethernet or token ring only) In the Address field, enter the LAN adapter
address of the remote host.
40
8. Choose OK to save your changes and return to the 5250 Terminal
Emulation Configuration dialog box.
Page 44
Fast Setup Quick Reference Guide
Setting Up 3270 SNA Terminal Emulation
You can use Fast Setup to set up 3270 SNA terminal emulation (TE) between
your JANUS 900 MHz RF devices or your TRAKKER Antares terminals and
SNA hosts. You need to identify all remote host names.
You also need to decide which terminals from the Available Terminals list
box you want to explicitly link to a host. If an explicit link is set up between
a terminal and a host, it means that the terminal can start a TE session only
with that host. If no explicit link is set up, the terminal can start a TE session
with any host in the Host Name list, as long as the host has NAU addresses
available. It will start a TE session with the host that is configured on the
terminal.
You can link as many terminals as you want. However, the number of
terminals that can simultaneously communicate through the controller
depends on
• the number of devices you enabled in the Fast Setup for Downline
Network dialog box.
• the number of terminals in your terminal license.
• the NAUs available on the remote hosts. You need to define these NAUs
on the controller. You can add these NAUs to an NAU pool. Then,
terminals that want to communicate with a host can dynamically link
with them. Or, you can explicitly link an NAU to a terminal and a host.
Note: Your JANUS 900 MHz RF devices and your TRAKKER Antares terminals
come with the 3270 TE software already loaded. However, this software is also
available on the Model 200 Controller.
Also, you must configure your terminals to use the SNA protocol.
Use the information from the 3270 Terminal Emulation Worksheet to help
you fill in this dialog box.
41
Page 45
Fast Setup Quick Reference Guide
FieldDescriptionValueDefault
Host NameThis list box contains the names of the
defined SNA hosts.
Host Name Linked Terminal
- NAU
Available
Terminals
The list of terminals and their NAUs
that are linked to a selected host.
The list of all terminals that are
available to link to a host.
2. Make sure you have added all the SNA hosts that the terminals will
access for terminal emulation. The Host Name list box contains all the
defined host names.
To add a host, follow the instructions in “Adding an IBM SNA Host”
later in this section.
3. Decide how to set up NAUs for the terminals:
• Fill the NAU pool for each of the hosts, but do not explicitly link any
terminals to hosts.
• Do not fill the NAU pool for any of the hosts. When you explicitly
link terminals to hosts, the controller generates NAUs starting at 002.
• Fill the NAU pool for each of the hosts and explicitly link some
terminals with hosts, and NAUs. You cannot link the NAUs in the
pool.
For help, see “Filling the NAU Pool” later in this section.
4. (Optional) Create any explicit links between hosts, terminals, and NAUs.
a. In the Host Name list box, select the host that you want to link to a
terminal.
b. In the Available Terminals list box, select the terminal you want to
link to the host.
c. Choose Link. The host, terminal, and first available NAU appear in
the Host Name - Linked Terminal - NAU list box.
To change the NAU that the controller assigns to the terminal, follow
the instructions in “Editing a Link” later in this section.
5. (Optional) Unlink any explicit links between hosts, terminals, and NAUs.
a. In the Host Name - Linked Terminal - NAU list box, select the
terminal you want to unlink from a host.
b. Choose Unlink. The host, terminal, and NAU are removed from the
Host Name - Linked Terminal - NAU list box.
6. Choose Close to close this dialog box and return to the main menu.
43
Page 47
Fast Setup Quick Reference Guide
Adding an IBM SNA Host
FieldDescriptionValueDefault
Host nameA name that identifies this SNA host.
You can use this internal name to make
the host LU name more meaningful.
Adapter cardThe network adapter card you are
using to connect to the host.
Local PU
(Ethernet or
token ring only)
Address
(Ethernet or
token ring only)
Node IDSpecifies the last eight characters in the
A unique PU name for the host that
allows the terminals to communicate
with more than one host using the same
upline adapter card.
The LAN adapter address of the host.Token ring MAC
host XID that are used for establishing a
connection with the controller.
1 to 8
alphanumeric
characters
Ethernet, token
ring, SDLC
8 uppercase
alphanumeric or
special characters
address format
8 hexadecimal
characters
None
Ethernet 1
SNA node name
+ 2-digit suffix,
starting with 01
None
05D00000
44
Page 48
Fast Setup Quick Reference Guide
To add an IBM SNA host
1. From the 3270 Terminal Emulation Configuration dialog box, choose
Add. The Host Connection Configuration dialog box appears.
2. In the Host name field, enter a meaningful name for the host.
3. In the Adapter card field, click the down arrow on the right side of the
field. A list that contains the available adapters appears. Select the
adapter you are using to connect to the host.
4. (Ethernet or token ring only) In the Local PU field, enter a unique PU
(physical unit) name for the host. The default name is the local SNA
node name plus a 2-digit suffix.
5. (Ethernet or token ring only) In the Address field, enter the LAN adapter
address of the remote host.
6. In the Node ID field, enter the last eight characters in the XID that
establish a host connection. The Node ID is the same as the XID.
Note: When establishing a connection, the host or controller with the higher
Node ID number is the primary workstation.
7. Choose OK to save your changes and return to the 3270 Terminal
Emulation Configuration dialog box.
Filling the NAU Pool
45
Page 49
Fast Setup Quick Reference Guide
1. From the 3270 Terminal Emulation Configuration dialog box, choose
NAU Pool. The 3270 NAU Pool dialog box appears.
2. Add all the NAUs to the NAU pool.
Note: Once an NAU is in the pool, you cannot use it in an explicit link.
a. In the New NAU field, type in the address.
b. Choose Add. The NAU is added to the Unlinked NAUs pool.
3. Remove any NAUs that you do not want in the pool or that you want to
use in an explicit link.
a. In the Unlinked NAUs pool, choose the NAU to remove.
b. Choose Delete. The NAU is removed from the pool. You can now use
this NAU in an explicit link.
Editing a Link
1. From the 3270 Terminal Emulation Configuration dialog box in the Host
Name - Linked Terminal - NAU list box, select the NAU to change.
3. In the Current NAU field, enter a new NAU for the terminal.
4. Choose OK to save your changes and return to the 3270 Terminal
Emulation Configuration dialog box.
Page 50
Fast Setup Quick Reference Guide
Setting Up Peer-to-Peer Links
To run TCP/IP or APPC applications in your data collection network, you
must define all the destination names in the Model 200 Controller. The
controller puts these names in a peer-to-peer destination list. You must also
specify which transactions the controller routes to each application.
The Peer-to-Peer Destination Parameters dialog box also lets you set the Hot
Standby timeout and delivery response messages.
47
Page 51
Fast Setup Quick Reference Guide
FieldDescriptionValueDefault
Destination nameThe name of the destination
(application).
Hot Standby
timeout
Transactions held
in volatile
memory
International text
pass-through
SelectedThis list box contains the transaction
AvailableThis list box contains all the transaction
The number of seconds the controller
waits for a response from a destination
before it places the transactions going
to that destination in a Hot Standby file.
The number of transactions the
controller keeps in RAM before it
writes them to a Hot Standby file.
This check box determines how much
of the transaction is converted.
Check this box to enable this feature.
The server converts only the transaction
header.
Clear this box to use limited EBCDIC
mapping. The server converts the entire
transaction.
IDs that are routed to this destination.
IDs that are available to add to the
Selected list box.
1 to 16
alphanumeric
characters
0 to 999920
None, Unlimited,
Maximum
Check, ClearClear
NoneNone
PredefinedNone
None
Maximum 50
Interactive
response
(Optional)
Hot standby
(Optional)
The message that is sent to the source of
the transaction when the transaction for
the destination is delivered
successfully.
The message that is sent to the source of
the transaction when the transaction for
the destination is written to a Hot
Standby file.
48
1 to 39 charactersNone
1 to 39 charactersNone
Page 52
Fast Setup Quick Reference Guide
To set up your peer-to-peer link
1. Choose Peer-to-Peer. The Peer-to-Peer Destination Parameters dialog box
appears.
2. In the Destination name field, enter the name of the destination
(application) that will accept the transactions in the Transaction box.
Note: You need to add the name of each data collection device in a 2.4 GHz RF
network that will communicate with the Model 200 Controller.
3. In the Hot Standby timeout field, enter the number of seconds the
controller waits for an acknowledgment from the destination before it
places the transactions going to that destination in a Hot Standby file.
4. Choose the number of transactions you want the controller to keep in
RAM before it writes them to a Hot Standby file.
• Choose None if you want the transaction always written to the file.
This setting is the safest setting and it is also the slowest.
• Choose Unlimited if you do not want the transaction written to the
file unless the time you set for the Hot Standby timeout expires. This
setting is the fastest.
• Choose Maximum and enter the maximum number of transactions
the controller stores in RAM before it writes them to a file.
5. Enable or disable international text pass-through. A check in the check
box means that international text pass-through is enabled.
6. Add all transaction IDs that you want routed to the destination to the
Selected list box.
a. From the Available list box, select a transaction to be added to the
Selected list box.
b. Choose Select. The transaction ID appears in the Selected list box.
7. Remove any transactions that you do not want routed to the destination
from the Selected list box.
a. From the Selected list box, select a transaction to be removed.
b. Choose Remove. The transaction ID is removed from the Selected list
box.
49
Page 53
Fast Setup Quick Reference Guide
8. Add any transaction IDs that are not listed in the Available list box.
Follow the instructions in the next section, “Adding a Transaction.”
9. (Optional) In the Delivery Responses box, enter the messages you want
to send to the transaction source.
• In the Interactive response field, enter the message you want to send
to the source of the transaction when the transaction for the
destination is successfully delivered in Interactive mode.
• In the Hot standby field, enter the message you want to send to the
source of the transaction when the transaction for the destination is
not successfully delivered and is written to a Hot Standby file.
10. Choose OK to save your changes and return to the main menu.
Adding a Transaction
You need to define transaction IDs so the controller can route them to their
proper destination.
50
Page 54
Fast Setup Quick Reference Guide
FieldDescriptionValueDefault
Transaction IDThe unique name of the transaction.1 to 20
alphanumeric
characters
Hot Standby
message
(Optional)
DelimiterThe character that separates the fields in
The message that is sent to the source of
the transaction when the controller
places the transactions for the
destination in a Hot Standby file.
the transaction.
1 to 39 charactersNone
Predefined, (comma)
To add a transaction
1. From the Peer-to-Peer Destination Parameters dialog box, choose Add.
The Transaction Parameters dialog box appears.
2. In the Transaction ID field, enter the unique ID for the transaction.
3. (Optional) In the Hot Standby message field, enter the message that the
controller sends to the source of the transaction when it places the
transactions for the destination in a Hot Standby file.
4. In the Delimiter field, click the down arrow on the right side of the field.
A list of delimiter characters appears. Choose one.
Note: This delimiter may differ from the delimiter set in the System Parameters
dialog box.
None
5. (Optional) Add, edit, or delete transaction fields from the list box. For
help, see the next sections.
6. Choose OK to save your changes and return to the Peer-to-Peer
Destination Parameters dialog box.
51
Page 55
Fast Setup Quick Reference Guide
To add transaction fields
FieldDescriptionValueDefault
Field nameThe unique name for the transaction
field.
NumberThe position of the field in the
transaction.
1. From the Transaction Parameters dialog box, choose Add. The
Transaction Field Parameters dialog box appears.
2. In the Field name field, enter a name for the transaction field.
3. In the Number field, enter the order or position of the field in the
transaction. The first field in the transaction is at position 1.
4. Choose OK to save your changes and return to the Transaction
Parameters dialog box.
1 to 16
alphanumeric
characters
1 to 999None
None
52
Page 56
Fast Setup Quick Reference Guide
Setting Up a Terminal Session
You can use Fast Setup to establish VT, ANSI, 5250, or 3270 terminal
sessions between the controller and your host. Use these sessions to access
your host directly from the controller. By accessing your host, you can
verify your host connection and you can start remote applications. Later,
using Advanced Setup, you can use this session to configure and run screen
mapping.
To set up a terminal session
1. Choose Terminal Session. This message box appears.
2. Choose the button for the type of terminal session you want to configure
and follow the appropriate instructions for configuring this terminal
session.
53
Page 57
Fast Setup Quick Reference Guide
Configuring a VT/ANSI Terminal Session
FieldDescriptionValueDefault
NameA meaningful name for this terminal
session.
Terminal modeThe type of terminal mode you want to
use for this terminal session.
Host NameThe name of the TCP/IP host to which
the terminal session connects.
Number of
sessions
Port numberThe port number on which this session
The number of terminal sessions you
want to run on the controller.
will communicate with the Telnet
daemon on the host.
54
1 to 8
alphanumeric
characters
VT100, VT220,
VT320, ANSI
PredefinedNone
1 to 2281
0 to 6553523
None
VT220
Page 58
Fast Setup Quick Reference Guide
To configure a VT/ANSI terminal session
1. Choose VT. The Terminal Session Definition dialog box appears.
2. In the Session box, enter a meaningful name for the session.
3. In the Terminal mode field, click the down arrow on the right side of the
field. A list that contains the different terminal modes appears. Select the
type of terminal mode you want to use for this terminal session.
4. In the Host Name box, click the down arrow on the right side of the
field. A list that contains existing TCP/IP host names appears. Select the
host that you want to connect with for this session.
Or, add a new host. For help, see “Adding a TCP/IP Host” earlier in this
quick reference guide.
5. In the Number of sessions field, enter the number of terminal sessions
that you want to run on the controller.
6. In the Port number field, enter the host port number on which this
session will communicate.
Note: Telnet uses port number 23 (default).
7. Choose OK to save your changes. A message box appears.
8. Choose Default to use the default terminal setup. The message box closes
and you return to the main menu.
Or, choose Custom to customize the terminal setup. The VT Setup dialog
box appears. For help, see “Customizing the VT Terminal Setup” later in
this section.
55
Page 59
Fast Setup Quick Reference Guide
Customizing the VT Terminal Setup
When you add a new VT or ANSI terminal session and you choose Custom,
the VT Setup dialog box automatically appears. If you have already created
a terminal session and you want to edit the fields in this dialog box, from
the Terminal Session list box, select the terminal session and then choose
Edit. The Terminal Session Definition dialog box appears. Choose the Edit
button that appears above the Terminal mode field. The VT Setup dialog
box appears.
56
Page 60
Fast Setup Quick Reference Guide
FieldDescriptionValueDefault
Cursor keysDetermines whether the arrow keys on
the terminal control cursor movement
or they send their application control
functions.
KeypadDetermines whether the number keys
on the terminal send their keycap
characters or they send their
programming functions.
Line wrap
enabled
ControlsDefines the type of control characters
User-Defined
Key
Save as new
defaults
This check box determines if text
automatically wraps to the next line
when it reaches the right margin.
that your terminal uses.
Determines whether or not the host can
change the user-defined keys.
This check box determines if the current
parameter settings are the default
parameter settings.
Normal,
Application
Numeric,
Application
Check, ClearClear
7 bit, 8 bit7 bit
Unlock, LockUnlock
Check, ClearClear
Normal
Numeric
57
Page 61
Fast Setup Quick Reference Guide
To customize the terminal setup
Note: If you are defining VT100 terminals, the option buttons in the Controls box
and the User-Defined Key box are grayed out.
1. In the Terminal Keys box, choose Normal if you want to use the terminal
cursor keys to move the cursor.
Choose Application if you want the cursor keys to send their application
control function.
2. In the Terminal Keys box, choose Numeric if you want the terminal
number keys to send their numbers.
Choose Application if you want the terminal number keys to send their
programming functions.
3. Check or clear the text to automatically wrap to the next line when it
reaches the right margin.
If line wrap is cleared, when the cursor reaches the right margin, the
terminal displays each new character in the last column of the line. Each
new character overwrites the previous character.
58
4. In the Controls box, choose 7-bit if you want the terminal to use all the
VT320 features. This mode also supports 8-bit graphic display characters
and 7-bit control characters. Choose this setting for all VT220
applications.
Choose 8-bit if you want the terminal to use all the VT320 features in an
8-bit environment with 8-bit control characters. Choose this setting for
VT220 applications that use 8-bit control characters.
5. In the User-Defined Key box, choose Lock if you do not want the host to
change the user-defined key definitions.
Choose Unlock if you want the host to be able to add or to change the
user-defined key definitions.
6. Check the Save as new defaults check box if you want to use the current
custom terminal configuration as the default for all other terminals of the
same type.
7. Choose OK to save your changes and to return to the main menu.
Page 62
Fast Setup Quick Reference Guide
Configuring a 5250 Terminal Session
59
Page 63
Fast Setup Quick Reference Guide
FieldDescriptionValueDefault
NameA meaningful name for this terminal
session.
Host NameThe name of the SNA host to which the
terminal session connects.
Mode nameThis name describes the class of service
and other session characteristics that
you may want for your network.
Host user IDThe user ID that lets you log into the
remote host.
PasswordThe password that goes with the user
ID that lets you log into the remote
host.
ShowDetermines if your password appears
in the field as you enter it.
Clear this check box to show asterisks
for each character you type instead of
the actual characters.
Number of
sessions
The number of terminal sessions you
want to configure to this host.
1 to 8
alphanumeric
characters
PredefinedNone
Predefined#INTER
1 to 10
alphanumeric
characters
1 to 10
alphanumeric
characters
Check, ClearClear
151
None
None
None
60
Page 64
Fast Setup Quick Reference Guide
To configure a 5250 terminal session
1. Choose 5250. The Terminal Session Definition dialog box appears.
2. In the Session box, enter a meaningful name for the session.
3. In the Host Name box, click the down arrow on the right side of the
field. A list that contains existing host names appears. Select the host that
you want to connect with for this session. For help, see “Adding an IBM
SNA Host” earlier in this document.
4. In the Mode name field, click the down arrow on the right side of the
field. A list of communication modes appears. Select the mode that you
want to use to communicate with your SNA host.
5. In the Host user ID field, enter the ID that allows you to log in to the
AS/400. In the Password field, enter the password that goes with your
user ID that allows you to log into the AS/400.
Enable the Show check box to show asterisks instead of the characters
you are typing.
Disable the Show check box to show the characters that you are typing in
the field.
6. In the Number of sessions field, enter the number of terminal sessions
you want to run on the controller. You can enter up to 15 sessions.
7. Choose OK to save your changes and return to the main menu.
61
Page 65
Fast Setup Quick Reference Guide
Configuring a 3270 Terminal Session
FieldDescriptionValueDefault
NameA meaningful name for this terminal
session.
Host NameThe name of the SNA host to which the
terminal session connects.
Number of
sessions
NAU addressThe network addressable unit (NAU)
The number of terminal sessions you
want to configure to this host.
that is specified for the workstation LU
name.
62
1 to 8
alphanumeric
characters
PredefinedNone
See table in Step
4
1 to 254None
None
1
Page 66
Fast Setup Quick Reference Guide
To configure a 3270 terminal session
1. Choose 3270. The Terminal Session Definition dialog box appears.
2. In the Session box, enter a meaningful name for the session.
3. In the Host Name box, click the down arrow on the right side of the
field. A list that contains existing host names appears. Select the host that
you want to connect with for this session. For help, see “Adding an IBM
SNA Host” earlier in this document.
4. In the Number of sessions field, enter the number of terminal sessions
you want to run on the controller.
Session TypeCoaxialNon-Coaxial
3270526
5. (non-coaxial only) In the NAU address field, enter the NAU address that
is specified for the workstation LU name.
6. Choose OK to save your changes and return to the main menu.
63
Page 67
Fast Setup Quick Reference Guide
Starting a Host Session
Once you have set up your terminal sessions on the controller, you can start
the host session from the controller.
To start a host session
1. From the main menu sidebar buttons, choose System Maintenance. The
System Maintenance dialog box appears.
2. In the System Maintenance list box, select Start Host Sessions and then
choose Start. The Start Host Session dialog box appears.
64
3. In the Host session field, click the down arrow on the right side of the
field. A list of the terminal sessions you have configured appears. Select
one to start.
4. Choose Start. The host session starts and the host window appears.
5. Choose Close to close the dialog box and return to the System
Maintenance dialog box.
6. Choose Close to return to the main menu.
Page 68
Fast Setup Quick Reference Guide
Verify Your Host Connection
Once you configure the network adapter cards and your host connection,
you may want to use the Send Transactions feature to verify that you have a
connection between the Model 200 Controller and your host. For help, see
“Verifying Your Data Collection Environment” earlier in this quick
reference guide.
When sending a transaction to your host application (destination), make
sure that your application is ready to accept the transaction. If your
application is not ready, the transaction is written to the Hot Standby file. If
the application does not know how to interact with the Hot Standby file,
subsequent transactions will also be written to the Hot Standby file. In this
case, clear the Hot Standby file before sending another transaction to the
application. For help, see “Viewing and Clearing the Hot Standby Files” in
Appendix A in the Model 200 Controller User’s Manual.
Before you verify your host connection, make sure you activate your current
configuration and start data collection.
65
Page 69
Fast Setup Quick Reference Guide
Step 8 - Start the Controller
Before you start the Model 200 Controller, make sure you have performed
these tasks:
1. Connected and configured all external Intermec controllers and devices.
2. Connected the Model 200 Controller to the host and the data collection
network.
3. Used Fast Setup to configure the data collection environment.
4. Used Fast Setup to configure the host communications environment.
5. Used Fast Setup to configure terminal emulation, peer-to-peer
applications, or terminal sessions.
To start the controller
1. From the main menu sidebar buttons, choose Save and Activate
Configuration. A message box appears confirming that you want to save
your changes and activate the configuration.
2. Choose Activate. You may be asked to shutdown the controller and
66
press Ctrl-Alt-Del to boot it. If not, a message box appears informing
you when your activate is successful.
Page 70
Fast Setup Quick Reference Guide
3. From the main menu on the controller, choose Start Data Collection. A
message box appears confirming that you want to start data collection.
4. Choose Start.
5. Start the applications on the host.
6. Start the applications on the devices.
To stop the controller
1. From the main menu sidebar buttons, choose Stop Data Collection. A
message box appears confirming that you want to stop data collection.
2. Choose Stop. When the controller is done stopping data collection, the
main menu appears.
67
Page 71
Fast Setup Quick Reference Guide
Where Do You Go From Here?
Now that your controller is installed in your network, you can perform
terminal emulation or send transactions from your Intermec data collection
devices to your host. If you need to perform Advanced Setup to edit or
delete some of the parameters, or if you need to configure screen mapping,
see the Model 200 Controller User’s Manual.
68
Page 72
I
Index
Page 73
Fast Setup Quick Reference Guide
Page 74
Index
I
Numbers
2.4 GHz RF network, 5, 7.
network.
3270 NAU Pool dialog box, 45
New NAU field, 46
Unlinked NAUs pool, 46
3270 screen mapping, See 3270 terminal sessions
3270 SNA terminal emulation
setting up, 30, 41
3270 Terminal Emulation Configuration dialog
box, 42
Available Terminals list box, 42
Edit Link button, 46
Host Name - Linked Terminal - NAU list box,
keyboard, 8, 9
monitor, 8, 9
mouse, 8, 9
power cord, 9
power supply, 8
activating your configuration, 12
Adapter card field, 39, 44
adapter cards,
adding a TCP/IP host, 34
adding a transaction, 50
adding an IBM SNA host, 39, 44
adding transaction fields, 52
Address field, 39, 44
ANSI screen mapping, See VT/ANSI terminal
sessions
ANSI terminal emulation, See Telnet terminal
emulation
APPC applications
setting up, 30
Auto-Start box, 14
Available Connections list box, 17
Available list box, 48
Available Terminals list box, 32, 37, 42
See
local network adapter
B
Bad ID response field, 14
BRU, 16
C
cards, See local network adapter
checklist box, 12
coaxial adapter card, configuring, 27
COM ports, See serial ports
communications environment, See host
communications environment
Configure button, 16
Configured Connections list box, 17
configuring a 3270 terminal session, 62
configuring a 5250 terminal session, 59
configuring a UDP Plus network, 19
configuring a VT/ANSI terminal session, 54
configuring an RF card, 18
configuring external Intermec controllers, 21
configuring the host environment parameters,
30
configuring the local network adapter cards, 24
connecting to your data collection network, 10
connecting to your host environment, 10
Controller address field, 28
verifying connection, 21
Data field, 22
Data or system field, 22
Delimiter field, 51
delivery response messages, 47
Destination ID field, 22
Destination name field, 48
E
Edit Link button, 46
Edit NAU Address dialog box, 46
Current NAU field, 46
editing a link, 46
environment parameters, See host environment
box, 25
Ethernet TCP/IP card field, 26
Local host name field, 26
Local IP address field, 26
Subnet mask field, 26
Use DHCP check box, 26
Ethernet TCP/IP card field, 26
explicit links
editing an NAU, 46
setting up, 31, 36, 41
external Intermec controllers, 16
configuring, 21
F
Fast Setup for Downline Network dialog box,
17
Available Connections list box, 17
Configured Connections list box, 17
Multi-Drop and RF field, 18
Network ID field, 18
Point-to-Point field, 18
RF channel field, 18
Serial port field, 18
Fast Setup for Intermec Hardware dialog box,
16
Configure button, 16
Fast Setup toolbar button, 11
Field name field, 52
File Transfer Time box, 14
filling the NAU pool, 45
H
help, using, 6
Hide at Boot Time button, 11
host
adding, 34
adding an IBM SNA host, 39, 44
types of, 5
verifying your connection, 65
host communications environment, setting up,
24
Host Connection Configuration dialog box, 39,
44
Adapter card field, 39, 44
Address field, 39, 44
Host LU field, 39
Host name field, 39, 44
Local PU field, 39, 44
Network ID field, 39
Node ID field, 44
Host Connections step, 12
host environment parameters, configuring, 30
host environment, connecting to, 10
Host LU field, 39
I-4
Page 76
Index
I
Host Name - Linked Terminal - NAU list box,
42
Host Name - Linked Terminals list box, 32, 37
Host Name box, 54, 60, 62
Host name field, 34, 39, 44
Host Name list box, 32, 37, 42
Host session field, 64
Host user ID field, 60
Hot standby field, 48
Hot Standby message field, 51
Hot Standby timeout, 47
Hot Standby timeout field, 48
I
IBM host, using with Telnet terminal emulation,
31
IBM SNA host, adding, 39, 44
ID delimiter field, 14
installing the controller, 10
Interactive response field, 48
Intermec Hardware step, 12
International text pass-through check box, 48
introduction to Fast Setup, 5
IP address field, 34
J
JANUS devices
using with 3270 SNA terminal emulation, 41
using with 5250 SNA terminal emulation, 36
using with Telnet terminal emulation, 31
K
keyboard, 8, 9
Keypad option buttons, 57
L
Line wrap enabled check box, 57
links, See explicit links
Local host name field, 26
Local IP address, 26
local network adapter
upline cards, 5
Local Network Adapters step, 12
Local PU field, 39, 44
Local station field, 29
M
main menu, 11, 12
checklist box, 12
sidebar buttons, 12
title bar, 12
toolbar buttons, 12
Max connections field, 14
Mode name field, 60
Model 200 Controller to 9180 and CrossBar
Worksheet, 16
Model 200 Controller to 9180 Worksheet, 16
Model 200 Controller to CrossBar Worksheet, 16
Model 200 Controller to RF Card Worksheet, 16
Model 200 Controller to TRAKKER Antares
Name field, 54, 60, 62
NAU address field, 62
NAU Pool button, 45
NAU pool, filling, 45
network adapter cards,
adapter
Network Adapter Cards Worksheet
using with the Ethernet card, 25
using with the SDLC card, 29
using with the twinaxial card, 28
Network ID field, 18, 39
New NAU field, 46
Node ID field, 44
Number field, 52
Number of sessions field, 54, 60, 62
Number to enable field, 19, 20
setting up links, 47
Peer-to-Peer Destination Parameters dialog box,
47
Available list box, 48
Destination name field, 48
Hot standby field, 48
Hot Standby timeout field, 48
Interactive response field, 48
International text pass-through check box, 48
Selected list box, 48
Transactions held in volatile memory field,
48
Peer-to-Peer Network Connection Parameters
box, 15
Point-to-Point field, 18
Port number field, 54
power button, 11
power cord, 9
powering on the controller, 11
Save and Activate sidebar button, 66
Save as new defaults check box, 57
saving your configuration, 12
screen mapping, 5, 53
SDLC adapter card
configuring, 29
default setting, 29
SDLC Adapter Configuration dialog box, 29
Local station field, 29
Selected list box, 48
Send Transaction dialog box, 22
Data field, 22
Data or System field, 22
Destination ID field, 22
Source ID field, 22
Transaction ID field, 22
Serial port field, 18
serial ports, 6
setting the system parameters, 13
setting up 3270 SNA terminal emulation, 41
setting up 5250 SNA terminal emulation, 36
setting up a terminal session, 53
setting up peer-to-peer links, 47
setting up Telnet terminal emulation, 31
setting up the controller, 8
setting up the data collection environment, 16
setting up the host communications
environment, 24
Setup for UDP Plus Terminals dialog box, 19, 20
Number to enable field, 19, 20
Starting IP address field, 20
Show at Boot Time button, 11
Show check box, 60
sidebar buttons, 12
Save and Activate, 66
Start Data Collection, 67
Stop Data Collection, 67
System Parameters dialog box, 13
SNA host
setting up explicit links with terminals, 36, 41
using with 3270 terminal emulation, 41
using with 5250 terminal emulation, 36
Source ID field, 22
Start button, 64
Start Data Collection sidebar button, 67
Start Host Session dialog box, 64
starting data collection, 66
Starting IP address field, 20
steps, configuring controller
Host Connections, 12
Intermec Hardware, 12
Local Network Adapters, 12
Stop Data Collection sidebar button, 67
stopping data collection, 67
Strip pad field, 14
Subnet mask, 26
System Maintenance sidebar button
Send Transactions, 22
Start Host Sessions, 64
System Parameters dialog box
62
Host Name box, 54, 60, 62
Host user ID field, 60
Mode name field, 60
Name field, 54, 60, 62
NAU address field, 62
Number of sessions field, 54, 60, 62
Password field, 60
Port number field, 54
Show check box, 60
Terminal mode field, 54
terminal sessions, See VT/ANSI terminal
sessions. See 3270 terminal sessions. See
5250 terminal sessions
terminals, setting up explicit links with hosts,
31, 36, 41
Time Synchronization box, 14
title bar, 12
TN3270 terminal emulation, See Telnet terminal
emulation
TN5250 terminal emulation,
emulation
token ring adapter card
configuring, 27
default setting, 27
toolbar buttons, 12
TRAKKER Antares terminals, 16
using with 3270 SNA terminal emulation, 41
using with 5250 SNA terminal emulation, 36
using with VT/ANSI terminal emulation, 31
Transaction Field Parameters dialog box, 52
Field name field, 52
Number field, 52
transaction fields, adding, 52
Transaction ID field, 22, 51
See also
3270 SNA terminal
Se also
5250 SNA terminal
See also
Telnet terminal
See
Telnet terminal
I-7
Page 79
Fast Setup Quick Reference Guide
Transaction Parameters dialog box, 50
Delimiter field, 51
Hot Standby message field, 51
Transaction ID field, 51
Transactions held in volatile memory field, 48
transactions, adding, 50
turning on the controller, 11
twinaxial adapter card, configuring, 28
Twinaxial Protocol Configuration dialog box, 28
Controller address field, 28
U
UDP Plus network, 16
configuring, 19
Unlinked NAUs pool, 46
Use device names check box, 37
Use DHCP check box, 26
Use DNS check box, 34
User-Defined Key option buttons, 57
V
verifying your data collection environment, 21
verifying your host connection, 65
voltage select switch, 9
VT screen mapping, See VT/ANSI terminal
Intermec Technologies Corporation
6001 36th Avenue West
P.O. Box 4280
Everett, WA 98203-9280
U.S. service and technical support: 1-800-755-5505
U.S. media supplies ordering information: 1-800-227-9947
Canadian service and technical support: 1-800-688-7043
Canadian media supplies ordering information: 1-800-268-6936
Outside U.S. and Canada: Contact your local Intermec service supplier.
The information contained herein is proprietary and is provided solely for the purpose of
allowing customers to operate and/or service Intermec manufactured equipment and is not to
be released, reproduced, or used for any other purpose without written permission of Intermec.
Information and specifications in this manual are subject to change without notice.
1998 by Intermec Technologies Corporation
All Rights Reserved
The word Intermec, the Intermec logo, JANUS, IRL, TRAKKER, Antares, Adara, Duratherm,
EZBuilder, Precision Print, PrintSet, Virtual Wedge, and CrossBar are either trademarks or
registered trademarks of Intermec Corporation.
Throughout this manual, trademarked names may be used. Rather than put a trademark
( or ) symbol in every occurrence of a trademarked name, we state that we are using the
names only in an editorial fashion, and to the benefit of the trademark owner, with no intention
of infringement.
Page 82
Contents
Contents
Before You Begin xvii
Warranty Information xvii
Safety Summary xvii
Warnings and Cautions xviii
About This Manual xix
Other Intermec Manuals xxii
Learning About the Controller
1
Chapter Checklist 1-3
Features 1-4
What’s New for Release 3.1? 1-5
Unpacking the Controller 1-7
Description 1-9
Understanding the Front Panel 1-9
Understanding the Rear Panel 1-10
About the Graphical User Interface 1-11
Using Help 1-12
Navigating Through Dialog Boxes 1-13
Understanding the Dialog Box Buttons 1-14
How the Controller Works 1-15
About Transactions 1-17
Data Transactions 1-17
System Transactions 1-17
How the Controller Routes Transactions 1-18
Routing Transactions From Applications 1-18
Routing Transactions From Devices 1-21
iii
Page 83
Model 200 Controller User’s Manual
How the Controller Acknowledges Transactions 1-25
How the Controller Ensures Data Integrity 1-25
Interactivity With Data Collection Devices 1-25
Fully Interactive System 1-26
Partially Interactive System 1-27
Noninteractive System 1-27
Data Integrity Modes 1-28
Faster Mode 1-28
Safer Mode 1-28
Retaining Transactions in Memory 1-29
How the Controller Sets Application Status 1-30
Active Applications 1-31
Nonactive Applications 1-31
Sending Hot Standby Messages 1-32
Changing from Nonactive to Active Status 1-33
Active Recovery Mode 1-33
Setting Up the Controller
2
iv
Chapter Checklist 2-3
Plugging In the Power Cord 2-4
Plugging In the Keyboard 2-5
Plugging In the Mouse 2-6
Connecting the Monitor 2-7
Connecting an Uninterruptable Power Supply 2-8
Connecting a Modem 2-11
Setting the System Parameters 2-14
Page 84
About the Configuration Files 2-17
Restoring Default Configuration 2-17
Backing Up the Controller Configuration 2-18
Backing Up Your System Files and Run-Time Configuration 2-18
Backing Up Your User Files 2-19
Restoring the Controller Configuration 2-20
Restoring Your System Files and Run-Time Configuration 2-20
Restoring Your User Files 2-21
Deleting User Files 2-23
Using the Controller 2-24
Starting Data Collection 2-24
Stopping Data Collection 2-25
Turning Off the Controller 2-25
Accessing a Command Prompt 2-26
Contents
Connecting to the Intermec RF Network
3
Chapter Checklist 3-3
Connecting the Controller to the 900 MHz RF Network 3-4
Configuring RF Controller Cards 3-6
Adding RF Controller Card and BRUs 3-7
Setting the Time Parameters 3-11
Identifying the RF Devices 3-15
Editing an RF Device 3-17
Connecting the Controller to the 2.4 GHz RF Network 3-19
Configuring a UDP Plus Network 3-21
Adding a UDP Plus Network 3-22
Setting Up the UDP Plus Devices 3-25
Setting the Time Parameters 3-28
Identifying the UDP Plus Devices 3-31
v
Page 85
Model 200 Controller User’s Manual
Editing a UDP Plus Device 3-33
Determining a UDP Plus Device’s IP Address 3-36
Editing a UDP Plus Device’s IP Address 3-37
Saving Your Run-Time Configuration 3-37
Connecting to the 9180 and the Intermec
4
5
CrossBar Network
Chapter Checklist 4-3
Configuring an External Intermec Controller 4-4
Adding a Controller 4-5
About the Controller Parameters 4-6
Adding a 9154 Controller 4-7
Adding a 9161 Controller 4-10
Adding a 9180 Controller 4-13
Setting the Time Parameters 4-15
Identifying the CrossBar Devices 4-19
Editing a CrossBar Device 4-21
Saving Your Run-Time Configuration 4-23
Connecting to an Ethernet/Token Ring
Network
Chapter Checklist 5-3
Installing the Controller in an Ethernet Network 5-4
Installing the Controller in a Token Ring Network 5-5
vi
Page 86
Contents
Configuring the Network Adapter Card for TCP/IP 5-6
Using DNS 5-10
Clearing the IP Address and Subnet Mask 5-12
Using the Routing Daemon 5-12
Configuring Routing Tables 5-14
Configuring the Network Adapter Card for IEEE 802.2 5-16
Saving Your Run-Time Configuration 5-19
Connecting to a Coaxial/Twinaxial Network
6
7
Chapter Checklist 6-3
Installing the Controller 6-4
Configuring the Coaxial Adapter Card 6-5
Configuring the Twinaxial Adapter Card 6-6
Saving Your Run-Time Configuration 6-7
Connecting to an SDLC Network
Chapter Checklist 7-3
Installing the Controller 7-4
Configuring the Network Adapter Card 7-5
Configuring Advanced SDLC Parameters 7-6
Saving Your Run-Time Configuration 7-8
vii
Page 87
Model 200 Controller User’s Manual
Using Terminal Emulation
8
Chapter Checklist 8-3
About Terminal Emulation 8-5
JANUS TE Application 8-6
TRAKKER Antares TE Application 8-7
Setting Up Telnet Terminal Emulation 8-7
Configuring the Controller 8-7
Adding a TCP/IP Host 8-10
Setting Up 5250 SNA Terminal Emulation 8-12
Configuring the Host 8-12
Configuring the Controller 8-12
Adding an IBM SNA Host 8-15
Configuring the Controller SNA Node 8-17
Selecting an IBM Mode 8-18
Setting and Removing the User ID and Password 8-19
Performing a Double Pass-Through on the IBM AS/400 Host 8-21
Setting Up 3270 SNA Terminal Emulation 8-22
Configuring the Host 8-22
Configuring the Controller 8-22
Adding an IBM SNA Host 8-25
Filling the NAU Pool 8-28
Editing a Link 8-29
Saving and Activating Your Run-Time Configuration 8-29
Configuring Your JANUS Devices 8-30
viii
Configuring for 900 MHz RF Communications 8-30
Configuring for UDP Plus Communications 8-31
Downloading the JANUS TE Application 8-31
Using the Download Server to Download the JANUS TE
Application 8-33
Using FTP to Load the JANUS TE Application 8-34
Accessing the TE Configuration Menu 8-35
Page 88
Exiting the TE Configuration Menu 8-36
Starting TE 8-36
Ending TE 8-37
About Running TE 8-37
About the Auto-Login Feature 8-38
Displaying International Characters 8-39
Configuring Your TRAKKER Antares Terminals 8-40
Configuring for Communications 8-40
Downloading the TRAKKER Antares TE Application 8-41
Accessing the TE Configuration Menu 8-43
Exiting the TE Configuration Menu 8-44
About Running TE on Your Terminals 8-45
About the Auto-Login Feature 8-45
Displaying International Characters 8-45
Setting Security for the TE Configuration Menu 8-46
Verifying That Security Is Set 8-49
Contents
9
Using Peer-to-Peer Applications
Chapter Checklist 9-3
About Peer-to-Peer Applications 9-4
Configuring the Host for Peer-to-Peer Applications 9-5
TCP/IP Applications 9-5
APPC Applications 9-5
Setting Up Peer-to-Peer Links on the Controller 9-6
Adding a Destination 9-8
Using International Text Pass-Through 9-11
Adding a Transaction 9-13
Adding a Transaction Field 9-14
Saving and Activating Your Run-Time Configuration 9-15
ix
Page 89
Model 200 Controller User’s Manual
Communicating With TCP/IP Applications 9-16
How the Controller Communicates With Applications 9-18
Understanding Transaction Routing in a TCP/IP Network 9-20
Communicating Through the Direct TCP/IP Socket Interface 9-23
Direct TCP/IP API vs. NetComm API 9-25
About the $IPT Transaction ID 9-26
About the Host Application Requirements 9-26
Using International Text Pass-Through 9-27
Communicating With APPC Applications 9-28
APPC Verbs 9-29
IMS Applications 9-30
NetComm Pairs 9-30
Using Terminal Sessions
10
Chapter Checklist 10-3
About Terminal Sessions 10-4
Configuring the Host for Terminal Sessions 10-5
Setting Up 5250 Terminal Sessions Using SDLC 10-5
Setting Up 3270 Terminal Sessions Using Ethernet 10-5
Setting Up 3270 Terminal Sessions Using SDLC 10-6
Creating Terminal Sessions 10-6
Adding a VT/ANSI Terminal Session 10-8
Adding a TCP/IP Host 10-10
Customizing the VT Terminal Setup 10-12
Adding a 5250 Terminal Session 10-15
Adding an IBM SNA Host 10-18
Configuring the Controller SNA Node 10-20
Adding a 3270 Terminal Session 10-21
Adding an IBM SNA Host 10-23
Saving and Activating Your Run-Time Configuration 10-25
x
Page 90
Contents
Starting a Host Session 10-26
Mapping Terminal Keyboards to the Model 200 Controller Keyboard 10-27
Using Screen Mapping
11
Chapter Checklist 11-3
About Screen Mapping 11-5
About Script Files 11-7
Preparing to Use the Script Builder Tool 11-7
Single Transaction Script Files vs. Multiple Transaction Script Files 11-8
Identifying Key Elements for the Script File 11-10
Example 1 - Single Transaction Script File 11-10
Example 2 - Multiple Transaction Script File 11-12
Understanding How the Script Builder Tool Flows 11-14
Using the Script Builder Tool 11-16
Creating a New Script File 11-17
Opening an Existing Script File 11-18
Saving the Script File 11-18
Copying a Script File 11-19
Deleting a Script File 11-21
Setting Options for the Script File 11-22
About the Data Response Timeout (VT/ANSI) 11-25
Creating Host Access Sequences 11-26
Creating a Logon Sequence 11-27
Creating a Normal Logoff Sequence 11-29
Creating an Abnormal Logoff Sequence 11-31
Editing the Captured Keystrokes 11-33
Deleting Lines in the Captured Keystrokes Box 11-33
Changing Lines in the Captured Keystrokes Box 11-33
Inserting New Lines in the Captured Keystrokes Box 11-33
xi
Page 91
Model 200 Controller User’s Manual
Selecting Transactions for the Script 11-34
Selecting Host Screens for the Current Transaction 11-36
Defining Next Screen Sequences for Host Screens 11-37
Selecting Host Screen Fields for the Current Host Screen 11-39
Adding a Host Screen Field 11-40
Getting Host Screen Field Attributes From a Host Screen 11-42
Selecting Regions for the Current Host Screen 11-43
Adding a Region 11-44
Getting a Region From a Host Screen 11-49
Capturing Keystrokes 11-50
Defining Next Host Screen Sequences for Regions 11-51
Creating Screen and Region Messages 11-53
Adding a Message 11-55
About Message Types (Status vs. Transaction) 11-57
Changing the Order of Screen Events 11-59
Maintaining the Host Screens 11-61
Adding a Host Screen 11-63
Getting the Screen Identifier From the Host Screen 11-64
xii
Defining User Blocks 11-65
Adding a User Block 11-68
Viewing the Script 11-69
Checking a Script File 11-70
Verifying the Script File Syntax 11-70
Verifying the Script File Logic 11-71
Setting Up Screen Mapping Sessions 11-76
Adding a Screen Mapping Session 11-77
Mapping Transaction Fields 11-80
Adding a Screen Mapping Field Placement Entry 11-82
Saving and Activating Your Run-Time Configuration 11-83
Page 92
Contents
Building Terminal Screens for Data Collection Devices 11-83
Adding a Terminal Screen 11-87
Adding a Terminal Field 11-89
Validating a Terminal Field 11-93
Getting Terminal Field Attributes From a Host Screen 11-95
Getting Terminal Field Attributes From the Script File 11-96
Defining Next Screen Sequence for Terminal Screens 11-97
Copying a Terminal Screen 11-99
Building Menus From Screens 11-100
Adding a Menu 11-101
Generating Menus Into Templates 11-102
Saving and Activating Your Run-Time Configuration 11-103
Configuring for UDP Plus Communications 11-109
Downloading the Terminal Template Application 11-110
Downloading the Template 11-113
Loading a Validation File 11-116
Running the Application 11-117
Configuring Your TRAKKER Antares Terminals 11-118
Configuring the Terminals for the First Time 11-118
Downloading the Template 11-119
Loading a Validation File 11-122
Running the Application 11-123
xiii
Page 93
Model 200 Controller User’s Manual
Troubleshooting
A
General Troubleshooting A-3
Using the System Reporting Tools A-5
Viewing the Configuration A-5
Viewing and Clearing the Hot Standby Files A-7
Message Box Error Messages A-9
Error Log Error Messages A-26
Viewing the Error Messages A-26
Using the Status Monitor A-26
Using the Error Log A-28
Understanding the Error Messages A-29
Using the System Diagnostics Tools A-59
Using the Message Log Formatter A-60
Using SNA Subsystem Management A-61
Using the Trace Utility A-62
Adding a Network Trace A-64
Adding a Screen Mapping Trace A-65
Adding a System Trace A-66
Understanding the Monitor Message Handler Transactions Dialog
Box A-67
Helpful Information
B
xiv
System Cabling Specifications B-3
Converting Ethernet Addresses to Token Ring MAC Format B-5
Using the Controller to Verify Your Network Connections B-7
Limitations when Downloading IRL Programs B-12
Adding a Group in the Download Server B-13
Copying Information Between Terminals or Groups B-15
Using the Download Server to Transfer Files B-16
Using Download Server Commands to Transfer Files B-18
Using the Controller to Configure TRAKKER Antares Terminals B-20
Using Remote Console
C
D
About Remote Console C-3
Configuring the NetOp Host (Model 200 Controller) C-3
Configuring for TCP/IP or Dial-Up SLIP C-4
Configuring for APPC C-6
Configuring Security C-8
Configuring the NetOp Guest (Remote PC) C-11
Using NetOp Guest for Windows C-11
Using NetOp Guest for OS/2 C-13
Upgrading Your Controller and Devices
Upgrading Your Licenses D-3
Upgrading Your Terminal License D-3
Upgrading to Screen Mapping D-4
Upgrading to Remote Console D-5
Using the Controller to Upgrade TRAKKER Antares Terminals D-6
Adding Upgrade Events D-8
Loading Firmware and Applications From a Disk D-12
Defining a Group D-14
Renaming a Group D-16
Performing the Upgrade D-16
xv
Page 95
Model 200 Controller User’s Manual
Managing System Firmware and Applications D-17
Viewing Upgrade Event Details D-18
Viewing the Event Log D-20
Worksheets
E
Glossary
G
xvi
Index
I
Page 96
Before You Begin
This section introduces you to standard warranty provisions, safety
precautions, warnings and cautions, document formatting conventions, and
sources of additional product information.
Warranty Information
To receive a copy of the standard warranty provision for this product,
contact your local Intermec sales organization. In the U.S. call (800) 7555505, and in Canada call (800) 688-7043. Otherwise, refer to the Worldwide
Sales & Service list that comes with this manual for the address and
telephone number of your Intermec sales organization.
Safety Summary
Your safety is extremely important. Read and follow all warnings and
cautions in this book before handling and operating Intermec equipment.
You can be seriously injured, and equipment and data can be damaged if
you do not follow the safety warnings and cautions.
Before You Begin
Do not repair or adjust alone Do not repair or adjust energized equipment
alone under any circumstances. Someone capable of providing first aid must
always be present for your safety.
First aid Always obtain first aid or medical attention immediately after an
injury. Never neglect an injury, no matter how slight it seems.
Resuscitation Begin resuscitation immediately if someone is injured and
stops breathing. Any delay could result in death. To work on or near high
voltage, you should be familiar with approved industrial first aid methods.
Energized equipment Never work on energized equipment unless
authorized by a responsible authority. Energized electrical equipment is
dangerous. Electrical shock from energized equipment can cause death. If
you must perform authorized emergency work on energized equipment, be
sure that you comply strictly with approved safety regulations.
xvii
Page 97
Model 200 Controller User’s Manual
Warnings and Cautions
The warnings and cautions in this manual use the following format.
Warning
A warning alerts you of an operating procedure, practice, condition, or
statement that must be strictly observed to avoid death or serious injury to
the persons working on the equipment.
Avertissement
Un avertissement vous alerte d’une procédure de fonctionnement, d’une
méthode, d’un état ou d’un rapport qui doit être strictement respecté pour
éviter l’occurrence de mort ou de blessures graves aux personnes
manupulant l’équipement.
Caution
A caution alerts you to an operating procedure, practice, condition, or
statement that must be strictly observed to prevent equipment damage or
destruction, or corruption or loss of data.
xviii
Conseil
Une précaution vous avertit d’une procédure de fonctionnement, d’une
méthode, d’un état ou d’un rapport qui doit être strictement respecté pour
empêcher l’endommagement ou la destruction de l’équipement, ou
l’altération ou la perte de données.
Notes: Notes are statements that either provide extra information about a topic or
contain special instructions for handling a particular condition or set of
circumstances.
Page 98
Before You Begin
About This Manual
All the information you need to install, configure, maintain, and
troubleshoot the Model 200 Controller is in this manual. Information in this
manual should be used by the person who will be installing and configuring
the controller. Many of the parameters need to be set by the network
administrator. This manual assumes that you are familiar with your
network and data communications.
Terms
• The Model 200 Controller is usually referred to as “the controller.”
• “JANUS devices” refers to all the readers and vehicle-mount computers
(VMC) in the JANUS® family of data collection computers.
• “TRAKKER Antares terminals” refer to the radio frequency and batch
terminals, respectively, in the TRAKKER® Antares™ terminal family.
• “TCP/IP terminals” refers to all the devices and terminals that
communicate using TCP/IP, instead of UDP Plus.
• “UDP Plus terminals” refers to all the devices and terminals that
communicate using the UDP Plus protocol, instead of TCP/IP.
• “Data collection devices” and “devices” refers to the JANUS devices,
TRAKKER Antares terminals, and other devices that communicate
through the Model 200 Controller.
Conventions
This manual uses these conventions to explain how to use your mouse and
to emphasize input from a PC keyboard, a data collection device keypad,
and a bar code. It also uses special conventions for commands.
Mouse Actions
All the procedures in this manual assume that you are using a mouse to
navigate within menus and dialog boxes. The following commands describe
specific mouse actions:
Select/Choose Move the mouse pointer to an item and press the left mouse
button once. The item or command is highlighted. For example, when you
select an object in a list box, it is highlighted.
xix
Page 99
Model 200 Controller User’s Manual
Double-click Move your mouse pointer to the item and click the left mouse
button twice quickly. In many dialog boxes, you can double-click on an item
instead of selecting it and choosing a button.
Input From a Host or PC Keyboard
When you need to press keys on your host or PC, they are emphasized in
bold. For example, “press Enter” means you press the key labeled “Enter”
on the keyboard.
When you need to press and release a series of keys in order, the keys
appear in order with no connectors. When you need to press more than one
key at the same time, the keys are connected by a dash in the text. For
example, press Ctrl-Alt-Del to perform a warm boot on a PC. When the
keys are connected by a dash, you need to press and hold the keys in the
order they appear in the text.
Input From a Data Collection Device Keypad
When you need to press keys on the data collection devices, they are
illustrated with icons that resemble the keys. For example, “press
means you press the key labeled “Enter” on the device keypad.
@
”
xx
Input From a Bar Code
You can use your data collection devices to scan the bar codes that are
provided in this manual to enter data or perform a command The bar code
labels in this manual are printed in the Code 39 symbology. Each bar code
includes the name and human-readable interpretation.
200.103
Page 100
Before You Begin
Commands
Command syntax is shown in the text as it should be entered. For example,
to see a list of directories on the JANUS device, type this command:
dir
If a command line includes both required and optional parameters, optional
parameters are enclosed in braces [ ].
Configuration commands use the convention data to indicate variables.
Replace the term data with one of the options listed with the command
syntax. For example, the configuration command for beep volume is BVdata
where data can be a number from 0 through 4.
Procedures
Throughout this manual you add, edit, and delete objects. For example, an
object can be a host or a terminal session. Whenever you need to add
objects, the procedure contains descriptions of all the fields, default values,
and step-by-step instructions. Use these instructions for editing and deleting
objects.
Editing an Object
1. In the dialog box, from the list box, select an object to edit.
2. Choose Edit. The next dialog box appears.
3. Edit the information in the fields.
4. Choose OK to save your changes and return to the first dialog box.
Deleting an Object
1. In the dialog box, from the list box, select an object to delete.
2. Choose Delete. A message box appears confirming that you want to
delete the object.
Note: You may not be able to delete an object if it is linked to another object.
3. Choose Delete. The object is removed from the list box.
4. Choose OK to save your changes and return to the main menu.
xxi
Loading...
+ hidden pages
You need points to download manuals.
1 point = 1 manual.
You can buy points or you can get point for every manual you upload.