Download Print this page

Intermec DCS300 User Manual

Intermec dcs300 servers: user guide

Hide thumbs Also See for DCS300:

Software manual (1 page)

,

Quick start manual (33 pages)

,

Technical reference manual (206 pages)

Table Of Contents

Table of Contents

Advertisement

Quick Links

Download this manual

User's Manual

P/N 067296-005

DCS 300

Table of Contents

Advertisement

Table of Contents

Troubleshooting

Need help?

Need help?

Do you have a question about the DCS300 and is the answer not in the manual?

Questions and answers

Summary of Contents for Intermec DCS300

Page 1 User's Manual P/N 067296-005 DCS 300...
Page 2 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.
Page 3 DCS 300 User’s Manual Manual Change Record This page records changes that have been made to this manual. This manual was originally released at version 001. Version Date Description 11/98 Added information on using WTP devices with the DCS 300. Removed information on the terminal template application in Chapter 11, “Using Screen Mapping.”...
Page 4 DCS 300 User’s Manual blank...
Page 5: Table Of Contents
Contents Before You Begin xvii Warranty Information xvii Safety Summary xvii Warnings, Cautions, and Notes xviii About This Manual xix Other Intermec Manuals xxi Getting Started Chapter Checklist 1-3 Features 1-4 Unpacking the DCS 300 1-5 Description 1-6 Understanding the Front Panel 1-6...
Page 6 DCS 300 User’s Manual CODE39 About the Web Browser Interface 2-9 Opening the DCS 300 Home Page 2-9 Getting Help 2-11 Setting the Date and Time 2-12 Setting the System Parameters 2-14 About the Configuration Files 2-16 Restoring the Default Configuration 2-16 Backing Up the DCS 300 Configuration 2-17 Backing Up Your System Files and Runtime Configuration 2-17 Backing Up Your User Files 2-18...
Page 7 Configuring the Trakker Antares UDP Plus Terminals 3-24 Configuring the WTP Devices 3-24 Saving Your Runtime Configuration 3-25 Connecting to the Intermec RF Network Chapter Checklist 4-3 Connecting the DCS 300 to the 900 MHz RF Network 4-4 Configuring the RF Card 4-6...
Page 8 Editing the WTP Network 4-36 Enabling the WTP Devices 4-37 Editing a WTP Device 4-38 Saving Your Runtime Configuration 4-39 Connecting to the 9180 and the Intermec CrossBar Network Chapter Checklist 5-3 Configuring an Intermec Controller 5-4 About the Controller Parameters 5-6...
Page 9 Running Terminal Emulation Chapter Checklist 7-3 About Terminal Emulation 7-4 JANUS TE Applications 7-6 Trakker Antares TE Applications 7-6 WTP TE Applications 7-6 Configuring Telnet TE (VT/ANSI, TN5250, and TN3270) 7-7 Configuring the DCS 300 7-7 Adding a TCP/IP Host 7-8 Adding an IP Port 7-9 Configuring Your JANUS Devices 7-10 Downloading the JANUS TE Application 7-11...
Page 10 DCS 300 User’s Manual CODE39 Using the Auto Login Feature 7-34 JANUS Devices 7-34 Trakker Antares Terminals 7-35 Displaying International Characters 7-36 JANUS Devices 7-36 Trakker Antares Terminals 7-37 WTP Devices 7-37 Saving and Activating Your Runtime Configuration 7-38 Running Peer-to-Peer Applications Chapter Checklist 8-3 About Peer-to-Peer Applications 8-4 Configuring the Host for Peer-to-Peer Applications 8-5...
Page 11 Running Terminal Sessions Chapter Checklist 9-3 About Terminal Sessions 9-4 Configuring the Host for Terminal Sessions 9-5 Setting Up 5250 Terminal Sessions Using SDLC 9-5 Setting Up 3270 Terminal Sessions Using Ethernet 9-6 Setting Up 3270 Terminal Sessions Using SDLC 9-6 Creating Terminal Sessions 9-7 Adding a Telnet Terminal Session 9-8 Adding a TCP/IP Host 9-9...
Page 12 DCS 300 User’s Manual CODE39 Using the Script Builder Tool 10-16 Creating a New Script File 10-17 Opening an Existing Script File 10-18 Saving the Script File 10-18 Copying a Script File 10-19 Deleting a Script File 10-21 Setting Options for the Script File 10-22 About the Data Response Timeout (VT/ANSI) 10-24 Creating Host Access Sequences 10-25 Creating a Logon Sequence 10-26...
Page 13 Verifying the Script File Logic 10-61 Setting Up Screen Mapping Sessions 10-65 Adding a Screen Mapping Session 10-66 Mapping Transaction Fields 10-68 Adding a Screen Mapping Field Placement Entry 10-69 Saving and Activating Your Runtime Configuration 10-69 Script Builder Tool Limitations 10-70 VT/ANSI Screen Mapping Limitations 10-71 VT Keyboard Mapping and Script Keystroke Names 10-72 Keystrokes 10-74...
Page 14 DCS 300 User’s Manual CODE39 About the dcBrowser Diagnostics 11-36 Using the Intermec Product Support Web Page 11-39 Specifications and Other Helpful Information Specifications A-3 Converting Ethernet Addresses to Token Ring MAC Format A-4 Using the DCS 300 to Verify Your Network Connections A-6...
Page 15 How the DCS 300 Routes Transactions How the DCS 300 Works C-3 About Transactions C-5 Data Transactions C-5 System Transactions C-5 How the DCS 300 Routes Transactions C-6 Routing Transactions From Applications C-6 Routing Transactions From Devices C-9 How the DCS 300 Acknowledges Transactions C-13 How the DCS 300 Ensures Data Integrity C-13 Interactivity With Devices C-13 Fully Interactive System C-14...
Page 16 DCS 300 User’s Manual...
Page 17: Before You Begin
To receive a copy of the standard warranty provision for this product, contact your local Intermec support services organization. In the U.S. call 1-800-755-5505, and in Canada call 1-800-668-7043. If you live outside of the U.S. or Canada, you can find your local Intermec support services organization on the Intermec Web site at www.intermec.com.
Page 18: Warnings, Cautions, And Notes
DCS 300 User’s Manual Warnings, Cautions, and Notes The warnings, cautions, and notes 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.
Page 19: About This Manual
About This Manual All the information you need to install, configure, operate, maintain, and troubleshoot the DCS 300 is in this manual. Information in this manual should be used by the person who will be installing and configuring the DCS 300. Many of the network parameters must be defined by the network administrator.
Page 20 DCS 300 User’s Manual 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.
Page 21: Other Intermec Manuals
You may need additional information when working with the DCS 300 in a data collection system. Please visit our Web site at www.intermec.com to download many of our current manuals in PDF format. To order printed versions of the Intermec manuals, contact your local Intermec representative or distributor.
Page 22 DCS 300 User’s Manual...
Page 23: Getting Started
Getting Started...
Page 24 DCS 300 System Manual blank...
Page 25: Chapter Checklist
This chapter helps you learn about the features of the DCS 300, how to set up the hardware for the DCS 300, and how to turn on and turn off the DCS 300. Chapter Checklist Done? Task Understand the features of your DCS 300. Unpack the DCS 300.
Page 26: Features
DCS 300 User’s Manual Features The DCS 300 is a high-performance data collection server that connects Intermec’s wired and wireless products to a host, a local area network, a wide area network, or the Internet. Your DCS 300 has many important features that make it easy to integrate it into your data collection network.
Page 27: Unpacking The Dcs 300
• DCS 300 Quick Start Guide 4. Report any damage or defects. Intermec thoroughly tested and inspected the DCS 300 before it was shipped to you. If any items are damaged, please take the following steps to correct the problem.
Page 28: Description
DCS 300 User’s Manual Description The DCS 300 contains several components on the front panel and on the rear panel that you should be able to identify. Note: This user’s manual decscribes a DCS 300 with 0300D hardware. If you are upgrading to software v1.6 and you have a DCS 300 with 0300A or 0300B hardware your front and rear panels will look different.
Page 29: Understanding The Rear Panel
Connects to one end of the AC power cord that provides power to the DCS 300. COM1, COM2 Provides serial port connections for external Intermec controllers, a modem, or other devices that require serial ports to connect to your DCS 300.
Page 30: Plugging In The Power Cord
(UPS). Intermec requires that you use a surge protector in locations that use 115 VAC. Intermec requires that you use a UPS in locations that have wide variations in AC power.
Page 31: Connecting An Uninterruptable Power Supply
Connecting an Uninterruptable Power Supply Intermec requires you to connect an uninterruptable power supply (UPS) to your DCS 300. In case of a power failure, the UPS provides enough backup power to allow the DCS 300 to properly shut down and minimize the loss of data.
Page 32 DCS 300 User’s Manual 9. In the System Maintenance list box, choose Install Accessories and then choose Start. The Install Accessories dialog box appears. 10. Choose UPS. 11. In the Available Ports list box, select the serial port on the DCS 300 that you used to connect to the UPS.
Page 33: Plugging In The Keyboard
Getting Started Plugging In the Keyboard Note: If you have a DCS 300 with 0300A hardware, you must have the keyboard connected to the DCS 300 whenever you boot it. Equipment • Keyboard (standard) To plug in the keyboard 1. Locate the keyboard port on the rear panel of the DCS 300. 2.
Page 34: Connecting The Monitor
DCS 300 User’s Manual The keyboard has mouse function keys on it. Connecting the Monitor Equipment • Monitor with cable and power cord (not provided) To connect the monitor 1. Locate the video port on the rear panel of the DCS 300. 2.
Page 35: Connecting A Modem
Connecting the Monitor (continued) To AC power Connecting a Modem You may want to connect your DCS 300 to a modem. If you are using the remote console feature, you may want to use a modem to let you access the DCS 300 using a PC with a modem.
Page 36 DCS 300 User’s Manual • 9F-25M cable (RS-232, 183 cm/6 ft) to connect the modem to the DCS 300 (Part No. 589182) To attach a modem 1. Make sure the DCS 300 is turned off. The power LED should be off. 2.
Page 37: Mounting The Dcs 300 In A Rack
Connecting a Modem (continued) To AC power Mounting the DCS 300 in a Rack This section explains how to mount your DCS 300 in a rack. When installing the server in a closed or multi-unit rack assembly, you must follow these requirements: •...
Page 38: Turning The Dcs 300 On And Off
DCS 300 User’s Manual To mount the DCS 300 in a rack 1. Locate the two rack handles, two rack ears, four flat head screws, and four round head screws that shipped with the DCS 300. 2. Secure the rack handles to the front of the rack ears with the flat head screws. 3.
Page 39: Turning On The Dcs 300
Turning On the DCS 300 • Push the On/Off button. The DCS 300 Configured Hardware dialog box appears. This dialog box lists the network adapter cards in your DCS 300. Choose one of the following: • If you want this dialog box to appear every time the DCS 300 boots, choose Show at Boot Time.
Page 40: Turning Off The Dcs 300
DCS 300 User’s Manual DCS 300 Window Turning Off the DCS 300 You may need to turn off the DCS 300 for maintenance or relocation. Before you push the On/Off button on the front panel, you must shut down the DCS 300. When you shut down the DCS 300, it performs a series of activities to ensure that no system files or data are lost.
Page 41 To turn off the DCS 300 1. From the main screen sidebar buttons, choose Shutdown DCS 300. The Shutdown DCS 300 message box appears. 2. Check or clear the Save and activate changes check box. If you want to save and activate the changes you made to the configuration, check this check box.
Page 42 blank...
Page 43: Learning About The Dcs 300
Learning About the DCS 300...
Page 44 DCS 300 User’s Manual blank...
Page 45: Chapter Checklist
This chapter explains the DCS 300 local and Web browser interfaces and how to navigate through them, how to use the online help, how to configure the system date and time and the system parameters, and how to maintain your configuration. Chapter Checklist Done? Task...
Page 46: About The Dcs 300 Local Interface
DCS 300 User’s Manual About the DCS 300 Local Interface You access the DCS 300 local interface when you turn on the DCS 300 while you have a monitor connected to it or you are using the remote console feature. You use this interface to •...
Page 47 Learning About the DCS 300 The DCS 300 local interface has three parts: Title bar The title bar at the top of the screen contains the name and version. It also lets you know if data collection is started or stopped. If you are configuring the DCS 300, [Save] and [Activate] may appear in the title bar.
Page 48: Getting Help
DCS 300 User’s Manual Getting Help The DCS 300 local interface includes online help that provides descriptions of the DCS 300 toolbars, dialog boxes, and options. Help also provides procedural information and limited background information. To get help • In any open dialog box, choose the Help button. The Help window opens and displays the topic for the toolbar or dialog box you were using.
Page 49: Navigating Through Dialog Boxes
Navigating Through Dialog Boxes In the DCS 300 local interface, there are various ways that you can move through dialog boxes: To Do This Action Move between fields in a dialog box Activate the buttons in a dialog box Go to the end of a file Go to the top of a file Access a window that shows you which applications are running...
Page 50: Understanding The Dialog Box Buttons
DCS 300 User’s Manual Understanding the Dialog Box Buttons These are the most common buttons that appear in the dialog boxes when you are configuring the DCS 300. Button Cancel Help Close Edit Delete Description Choose OK to save any changes you have made in the dialog box and exit from that dialog box.
Page 51: About The Web Browser Interface
• run dcBrowser diagnostics. • access the Intermec Product Support Web page. Opening the DCS 300 Home Page The home page appears when you enter the DCS 300 IP address in the Address line or the Go to line in your Web browser. It gives you information about the DCS 300, such as its name and its software version.
Page 52 DCS 300 User’s Manual DCS 300 Home Page Web browser menu Navigation menu You can open the DCS 300 home page from a PC that has a Web browser and is connected to your Intranet. Before you can remotely connect to the DCS 300, you must configure it for the Ethernet or token ring network.
Page 53: Getting Help
1. From the navigation menu, click Configuration. 2. If a security screen appears, type Password field, and click OK. You must type Intermec in uppercase letters. 3. In the lower left corner of the page, click Help. Learning About the DCS 300...
Page 54: Setting The Date And Time
1. Open the DCS 300 home page. For help, see “About the Web Browser Interface” earlier in this chapter. 2. Click Configuration. If a security screen appears, type field and in the Password field, and click OK. You must type Intermec in uppercase letters. The DCS 300 Configuration page appears. 2-12...
Page 55 Learning About the DCS 300 DCS 300 Configuration Page 3. Expand the System menu, and click Date and Time. The Change Date and Time page appears. 4. Enter the date in the date field, or click the Popup Calendar to select a date. 5.
Page 56: Setting The System Parameters
DCS 300 User’s Manual Setting the System Parameters When you set system parameters, you are defining the operating parameters for the DCS 300. To set the system parameters • From the main screen sidebar buttons, choose System Parameters. The System Parameters dialog box appears.
Page 57 Send to downline This check box determines if the DCS 300 devices every... sends its time to all Intermec controllers. Note: The time broadcast is not necessarily sent to the devices that are connected to the Intermec controllers. However, when you configure a controller, you can configure it to broadcast the time to its devices.
Page 58: About The Configuration Files
DCS 300 User’s Manual About the Configuration Files The DCS 300 uses three configuration files: Default This configuration is the factory default configuration. If you want to restore the default configuration, for example if you want to move the DCS 300 to a new system, select this option.
Page 59: Backing Up The Dcs 300 Configuration
6. Press Ctrl-Alt-Del to reboot the DCS 300. Backing Up the DCS 300 Configuration Once you have configured your Intermec hardware, have set up your host communications, and have set up your host environment parameters, you can start data collection on your DCS 300.
Page 60: Backing Up Your User Files
1. From the DCS 300 home page, click Management. 2. If a security screen appears, type Password field, and click OK. You must type Intermec in uppercase letters. 3. Click Back Up. A message box appears confirming that you want to back up the current configuration of the DCS 300.
Page 61: Restoring The Dcs 300 Configuration
6. Insert a 3.5-inch disk into the DCS 300 disk drive. The DCS 300 backs up the user files you selected. 7. Remove your disk from the disk drive, label it, and put it in a safe place. Restoring the DCS 300 Configuration If your DCS 300 loses its configuration, you can recover the system files and runtime configuration.
Page 62: Restoring Your User Files
1. From the DCS 300 home page, click Management. 2. If a security screen appears, type Password field, and click OK. You must type Intermec in uppercase letters. 3. Choose Restore. The Restore Configuration page appears. 4. Choose Last User Initiated Backup or choose Last Automatic Backup.
Page 63 3. In the File Handling list box, select Restore User Files and then choose Start. A message box appears with instructions to insert the disk in the drive of the DCS 300. 4. Choose OK. The Restore User Files dialog box appears. The files on the floppy disk appear in the Available Files list box.
Page 64: Deleting User Files
DCS 300 User’s Manual Deleting User Files 1. From the main screen sidebar buttons, choose File Handling. The File Handling dialog box appears. 2. In the File Handling list box, select Delete User Files and then choose Start. The Delete User Files dialog box appears. 3.
Page 65: Starting And Stopping The Downline Network
1. From the DCS 300 home page, click Management. 2. If a security screen appears, type Password field, and click OK. You must type Intermec in uppercase letters. 3. In the Data Collection row, click Start. A message box appears confirming that you want to start data collection.
Page 66: Stopping Data Collection
You may need to stop data collection on the DCS 300 to update its configuration file. When you stop data collection, all data collection activities are stopped, but any external Intermec controllers continue polling and buffering data. Devices using programs that require a response directly from a destination (interactive mode) also stop until the DCS 300 is started again.
Page 67: Accessing A Command Prompt
1. From the DCS 300 home page, click Management. 2. If a security screen appears, type Password field, and click OK. You must type Intermec in uppercase letters. 3. In the Data Collection row, click Stop. A message box appears confirming that you want to stop data collection.
Page 68 blank...
Page 69: Connecting To The Upline Network
Connecting to the Upline Network...
Page 70 DCS 300 System Manual blank...
Page 71: Chapter Checklist
• Chapter 4, “Connecting to the Intermec RF Network” • Chapter 5, “Connecting to the 9180 and the Intermec CrossBar Network” Connecting to the Upline Network Page 3-11...
Page 72: Connecting To An Ethernet Network
DCS 300 User’s Manual Connecting to an Ethernet Network To connect the DCS 300 to an Ethernet network, you must attach it to the wired network and then you must configure the card. The Ethernet card supports both TCP/IP and IEEE 802.2 protocols. Installing the DCS 300 The DCS 300 has a built-in Ethernet interface.
Page 73: Configuring The Ethernet Card For Tcp/Ip
Note: The DCS 300 supports only one network adapter card that is using DHCP. However, the DCS 300 cannot be a DHCP client and a DHCP server. If you are using the DCS 300 as a DHCP server for your Intermec data collection network, you must enter the TCP/IP information manually.
Page 74 DCS 300 User’s Manual 3. Choose Ethernet. The Advanced Protocol Configuration dialog box appears. 4. In the Protocols field, click the down arrow on the right side of the field. Select TCP/IP. 5. Choose Advanced. The TCP/IP Protocol Configuration dialog box appears. Field Description TCP/IP card...
Page 75: Using Dns
In a DHCP environment, the IP address changes frequently. The host may obtain a new IP address every time it is restarted and reconnects to the network. DNS servers let the DCS 300 locate and connect to TCP/IP hosts that are administered by a DHCP server.
Page 76 The DCS 300 appends the complete domain name before attempting to use the DNS server to resolve the IP address. Note: If the host or device name has any dotted notation, such as intermec.com, this list is not used. Value Default x.x.x.x where x is a...
Page 77: Clearing The Ip Address And Subnet Mask
Clearing the IP Address and Subnet Mask When you configure a card for TCP/IP and you do not use DHCP, you must enter the IP address and subnet mask. From the TCP/IP Configuration dialog box of the local interface, the Delete Address button lets you clear the Local IP address and Subnet mask fields.
Page 78 DCS 300 User’s Manual IEEE 802.2 Adapter Protocol Configuration Dialog Box Field Description IEEE 802.2 card The Ethernet adapter that you are configuring. Network adapter The locally administered MAC address in address (Optional) IEEE format (hex) that identifies the card. Ethernet driver The Ethernet frame type you are using.
Page 79: Connecting To A Token Ring Network
Connecting to a Token Ring Network To connect the DCS 300 to a token ring network, you must attach it to the wired network and then you must configure the card. The token ring card supports both TCP/IP and IEEE 802.2 protocols. Note: The token ring card is not available on the 0300D.
Page 80 Note: The DCS 300 supports only one network adapter card that is using DHCP. However, the DCS 300 cannot be a DHCP client and a DHCP server. If you are using the DCS 300 as a DHCP server for your Intermec data collection network, you must enter the TCP/IP information manually.
Page 81 Advanced Protocol Configuration Dialog Box 4. In the Protocols field, click the down arrow on the right side of the field. Select TCP/IP. 5. Choose Advanced. The TCP/IP Configuration dialog box appears. Field Description TCP/IP card The token ring adapter that you are configuring.
Page 82: Using Dns
In a DHCP environment, the IP address changes frequently. The host may obtain a new IP address every time it is restarted and reconnects to the network. DNS servers let the DCS 300 locate and connect to TCP/IP hosts that are administered by a DHCP server.
Page 83: Configuring The Token Ring Card For Ieee 802.2
DNS server to resolve the IP address. Note: If the host or device name has any dotted notation, such as intermec.com, this list is not used. Configuring the Token Ring Card for IEEE 802.2 After you install the DCS 300, you need to turn it on and configure its network adapter cards.
Page 84 DCS 300 User’s Manual Advanced Protocol Configuration Dialog Box 4. In the Protocols field, click the down arrow on the right side of the field. Select IEEE 802.2. 5. Choose Advanced. The IEEE 802.2 Adapter Protocol Configuration dialog box appears. Field Description IEEE 802.2 card...
Page 85: Connecting To A Twinaxial Network
Connecting to a Twinaxial Network To connect the DCS 300 to a twinaxial network, you must attach it to the wired network and then you must configure the card. The DCS 300 can only contain one twinaxial card and it must be in the first ISA slot, which is the ISA slot that is farthest right when you are looking at the rear panel of the DCS 300.
Page 86: Connecting To An Sdlc Network
Note: The SDLC card uses COM1. If you need more than one available serial port (COM2), you can contact your local Intermec representative and purchase an Intermec serial I/O board. Note: The SDLC card is not available on the 0300D.
Page 87: Configuring The Sdlc Card
Note: The default configuration for the SDLC card is V.35. Contact your local Intermec representative if you need to use RS-232 communications. To install the DCS 300 1. Locate the slot that contains the SDLC card on the rear panel of your DCS 300. The SDLC card is the card that is farthest right when you are facing the front panel.
Page 88: Configuring Advanced Sdlc Parameters
DCS 300 User’s Manual 5. Configure any advanced SDLC parameters. For help, see “Configuring Advanced SDLC Parameters” in the next section. 6. Choose OK to return to the SDLC Adapter Configuration dialog box. 7. Choose OK to return to the main screen. Configuring Advanced SDLC Parameters •...
Page 89: Configuring Ip Routes
Field Description Link station role This field sets the role of the DCS 300 to be the primary workstation or the secondary workstation to the host. If you are configuring 3270 SNA terminal emulation or you are communicating with a mainframe, this field is typically Secondary.
Page 90: Configuring Routing Tables
DCS 300 User’s Manual Routing Table Entries Configuration Dialog Box 2. To enable the routing daemon, check the check box for Enable routing daemon. Or, to disable the routing daemon, clear the check box for Enable routing daemon and configure explicit routes. For help, see “Configuring Routing Tables” in the next section.
Page 91: Using The Auto Fallback Feature
Field Description Route type The type of route you are configuring for a destination. Route destination The IP address of the destination of the route (N, S, H route types you are configuring. only) Router IP address The IP address of the router for the destination you are configuring.
Page 92: Configuring The Dcs 300S
DCS 300 User’s Manual Configuring the DCS 300s You must configure each DCS 300 that you want to be available to use with the Auto Fallback feature to accept connections from the terminals that you want to use with this feature.
Page 93: Saving Your Runtime Configuration
Connecting to the Upline Network Saving Your Runtime Configuration When you finish configuring your network adapter card, you should save your changes. To save your runtime configuration • From the main screen sidebar buttons, choose Save Configuration. 3-25...
Page 94 blank...
Page 95: Connecting To The Intermec Rf Network
Connecting to the Intermec RF Network...
Page 96 DCS 300 System Manual blank...
Page 97: Chapter Checklist
Done? Task Connect the DCS 300 to your Ethernet or token ring network. Connect the DCS 300 to your Intermec 900 MHz RF network. Configure the RF cards in the DCS 300 to communicate with the BRUs. Set the time parameters for the 900 MHz RF network.
Page 98: Connecting The Dcs 300 To The 900 Mhz Rf Network
To connect the DCS 300 and the BRU, Intermec provides you with a 4-port interface cable. Insert one end of the cable into the port on the RF card. Use the Intermec cable kit (Part No. 055003) or equivalent to connect to one of the DNLN ports on the other end of the cable.
Page 99 Connecting to the Intermec RF Network Example: The DCS 300 Connected to the Intermec 900 MHz RF Network Host DCS 300 9181 9181 9450 J2050 9189 JR2020 9465 0300U016.eps 3400...
Page 100: Configuring The Rf Card
DCS 300 User’s Manual Configuring the RF Card You must configure the communications parameters, enable the BRUs, set the Hot Standby timeout, and set any special time parameters for the RF card. The RF card must have a unique RFNC address and a unique network ID. To configure the RF card 1.
Page 101 11. Choose Close to return to the main screen. 12. Enable all the RF devices that you want to communicate with the DCS 300. For help, see “Enabling the RF Card Devices” later in this chapter. Connecting to the Intermec RF Network...
Page 102: Adding An Rf Card
DCS 300 User’s Manual Adding an RF Card After you finish configuring the RF card and you choose OK, the RF Card Devices dialog box appears. For help, see “Defining the RF Card Devices” later in this chapter. To add an RF card •...
Page 103 Repeat count The number of repeaters that a message is allowed to pass through for this BRU. Note: Intermec recommends that a message does not pass through more than three repeaters. Hot Standby The number of seconds the DCS 300 waits to...
Page 104: Setting The Time Parameters
DCS 300 User’s Manual Setting the Time Parameters You can configure these time parameters between the BRUs and their devices. Broadcast Parameters These optional parameters let the DCS 300 broadcast a time, with a short string, at certain intervals to all RF devices. These parameters synchronize the RF devices with the DCS 300.
Page 105 This character separates the data from the appended date and time. Julian date This check box determines if the date is in a 3-digit Julian format. Connecting to the Intermec RF Network Value Check, Clear Check, Clear Check, Clear 12 hour, 24 hour...
Page 106: Defining Default Hosts
DCS 300 User’s Manual Defining Default Hosts You can define a default method for the RF card devices to get a host name when they are communicating with different types of hosts. You can configure the RF card devices • explicitly link with a specific host.
Page 107: Defining The Rf Card Devices
The number of logical names that you want to to enable enable to communicate through this RF card to the DCS 300. Each BRU supports 32 devices (4x32=128). Connecting to the Intermec RF Network Value 1 to 13 alphanumeric and special characters...
Page 108: Enabling The Rf Card Devices
DCS 300 User’s Manual Enabling the RF Card Devices When you configured the RF card, you enabled a fixed number of devices to communicate with the DCS 300. You can enable up to 128 devices. Use the Device List dialog box to enable or disable addresses and logical names for devices that you want to communicate with the DCS 300.
Page 109: Editing An Rf Card Device
Editing an RF Card Device • From the Device List dialog box, choose Edit Device. The Device Parameters dialog box appears. Note: If you are using terminal emulation, do not configure transaction IDs or delivery responses. Connecting to the Intermec RF Network 4-15...
Page 110 Able to receive data This check box determines if this device can receive data from the network. Device type This list box contains the current Intermec devices that are supported. Auto-insert from This field provides a transaction ID for this...
Page 111: Connecting The Dcs 300 To The Udp Plus Network
Intermec’s UDP Plus network. • Trakker Antares terminals, such as the T2425, are terminals with network support. The DCS 300 supports these terminals using Intermec’s UDP Plus network. Follow the instructions “Configuring a UDP Plus Network” later in this chapter. •...
Page 112: Configuring A Udp Plus Network
DCS 300 User’s Manual Configuring a UDP Plus Network You must configure a UDP Plus network if you want the DCS 300 to communicate with Trakker Antares terminals and JANUS UDP Plus devices. To configure a UDP Plus network 1. From the main screen, choose the type of host environment you are using to communicate between the DCS 300 and the host.
Page 113: Adding A Udp Plus Network
To add a UDP Plus network • From the Add a Downline Connection Point dialog box, choose UDP Plus and then choose Add. The UDP Plus Network Parameters dialog box appears. Connecting to the Intermec RF Network 4-19...
Page 114 DCS 300 User’s Manual Field Description Lower limit The minimum time in milliseconds the DCS 300 waits for an acknowledgment from the device before resending a transaction. Upper limit The maximum time in milliseconds the DCS 300 waits for an acknowledgment from the device before resending a transaction.
Page 115: Setting The Time Parameters
To set the time parameters • From the UDP Plus Network Parameters dialog box, choose Time Parameters. The Configure Time Parameters dialog box appears. Connecting to the Intermec RF Network 4-21...
Page 116 DCS 300 User’s Manual Field Description Broadcast enabled This check box determines if the DCS 300 sends a time broadcast to all terminals in the UDP Plus network. Include Seconds This check box adds seconds to the time. Note: If you are using JANUS devices to communicate with the BRUs, you must check this check box.
Page 117: Defining Default Hosts
5250 SNA hosts. Telnet (all) The method that the UDP Plus devices will use to get a host name when they communicate with Telnet hosts. Connecting to the Intermec RF Network Value None, Prompt, pre-defined list None, Prompt,...
Page 118: Setting Up The Udp Plus Devices
DCS 300 User’s Manual Setting Up the UDP Plus Devices The DCS 300 must know the IP address for every UDP Plus terminal that it may communicate with. You can either use the DCS 300 to generate logical names for each terminal and use a DNS server to resolve the IP addresses, or you can enter each terminal’s IP address.
Page 119: Enabling The Udp Plus Devices
DCS 300. Note: Do not enable devices that you are not using. If you try to send data to a nonexistent enabled device, your system performance will degrade. Connecting to the Intermec RF Network Value 1 to 254...
Page 120 DCS 300 User’s Manual You can edit each terminal to change its logical name, IP address, device type, transaction IDs, and delivery responses. You can also use DNS to determine the device’s IP address or to edit an IP address. Your DCS 300 can communicate with up to 254 devices.
Page 121: Editing A Udp Plus Device
To edit a UDP Plus device • From the Device List dialog box, choose Edit Device. The Device Parameters dialog box appears. Note: If you are using terminal emulation, do not configure transaction IDs or delivery responses. Connecting to the Intermec RF Network 4-27...
Page 122: Determining A Udp Plus Device's Ip Address
Able to receive data This check box determines if this terminal can receive data from the network. Device type This list box contains all the current Intermec terminals supported. Auto-insert from This field provides a transaction ID for this device terminal if it cannot put a transaction ID in its transactions.
Page 123: Editing A Udp Plus Device's Ip Address
To edit a terminal’s IP address using the local interface 1. Clear the Use DNS check box. 2. In the IP address field, enter a new IP address for the terminal. Connecting to the Intermec RF Network 4-29...
Page 124: Connecting The Dcs 300 To The Wtp Network
DCS 300 User’s Manual Connecting the DCS 300 to the WTP Network The DCS 300 supports communications with WTP devices through access points that are connected to the Ethernet or token ring network. Access points act as bridges between the Ethernet or token ring network and WTP network. The illustration below shows an example of the DCS 300 connected to the WTP network.
Page 125: Configuring A Wtp Network
6. Configure the WTP network. For help, see “Adding a WTP Network” in the next section. 7. Define how the WTP devices will communicate with each of the different types of hosts. For help, see “Adding a WTP Network” in the next section. Connecting to the Intermec RF Network 4-31...
Page 126: Adding A Wtp Network
DCS 300 User’s Manual 8. Choose OK. The WTP Devices dialog box appears. For help, see “Setting Up the WTP Devices” later in this chapter. 9. Choose OK. The RF Hosts Created for WTP dialog box appears. For help, see “About the RF Hosts Created for the WTP Network”...
Page 127 Determines if the WTP devices display their screen on all initialization information (Unit Ready) on the terminals screen when they connect to the DCS 300. Connecting to the Intermec RF Network Value Ethernet 1, Ethernet 2 Token Ring 1 1 to 9999...
Page 128: Setting Up The Wtp Devices
DCS 300 User’s Manual Field Description 5250/3270 clients Determines which emulation type the connect DCS 300 will use to communicate with the host when it receives a transaction from the WTP network. Note: WTP devices must communicate with the DCS 300 using Telnet. The DCS 300 will convert the transaction to the appropriate format for the host type.
Page 129: About The Rf Hosts Created For The Wtp Network
RF host instances that the DCS 300 has created. You must assign each device to the RF host instance that you want it to communicate with. Each RF host instance supports up to 127 terminal sessions. Connecting to the Intermec RF Network Value 1 to 13...
Page 130: Editing The Wtp Network
DCS 300 User’s Manual Editing the WTP Network When you edit the WTP network, the WTP Parameters dialog box looks slightly different than when you added the network. Rename RF Hosts This button lets you rename the RF host. Enter the new name in the field and then choose Rename.
Page 131: Enabling The Wtp Devices
5. Select a terminal whose individual parameters you want to edit and choose Edit Device. Follow the next procedure, “Editing a WTP Device.” 6. Choose OK to save your changes and return to the main screen. Connecting to the Intermec RF Network 4-37...
Page 132: Editing A Wtp Device
Able to receive data This check box determines if this device can receive data from the network. Device type This list box contains all the current Intermec devices supported. Auto-insert from This field provides a transaction ID for this device device if it cannot put a transaction ID in its transactions.
Page 133: Saving Your Runtime Configuration
When you finish configuring your downline network, you should save your changes. To save your runtime configuration • From the main screen sidebar buttons, choose Save Configuration. Connecting to the Intermec RF Network Value 1 to 39 characters 1 to 40 characters...
Page 134 blank...
Page 135: Connecting To The 9180 And The Intermec Crossbar Network
Connecting to the 9180 and the Intermec CrossBar Network...
Page 136 DCS 300 System Manual blank blank...
Page 137: Chapter Checklist
BRUs using the 9180 configuration menu. Refer to your 9180 user’s manual. If you already understand these sections and have already performed these tasks, connect the DCS 300 to your Intermec RF network or host environment as described in these chapters: •...
Page 138: Configuring An Intermec Controller
DCS 300 User’s Manual Configuring an Intermec Controller An Intermec controller is a 9180 Network Controller, 9161 Port Concentrator, or a 9154 Multi-Drop Line Controller that is connected to the DCS 300 through a serial port. The following illustration is an example of a DCS 300 connected to a 9180 and a CrossBar network.
Page 139 Connecting to the 9180 and the Intermec CrossBar Network To configure the DCS 300 to work with an Intermec controller 1. From the main screen, choose the type of host environment you are using to communicate between the DCS 300 and the host.
Page 140: About The Controller Parameters
Intermec controllers with their devices. In the System Parameters dialog box, you can set a time synchronization parameter that synchronizes the time on the DCS 300 with its Intermec controllers. For more help, see “Setting the Time Parameters” later in this chapter.
Page 141 Hot Standby file. Transaction throughput is slower because the DCS 300 cannot accept another transaction from the 9154 until it verifies the previous one. Connecting to the 9180 and the Intermec CrossBar Network Value COM1, COM2 Predefined Check, Clear...
Page 142 DCS 300 User’s Manual Field Description Transactions held in The number of transactions the DCS 300 volatile memory keeps in volatile RAM before it begins to write them to a Hot Standby file. Choose None if you want the transaction always written to the file.
Page 143: Adding A 9161 Controller
The number of bits to use for setting communications protocol. Stop bits The number of bits to use for setting communications protocol. Connecting to the 9180 and the Intermec CrossBar Network Value COM1, COM2 Predefined Check, Clear Even, Odd, None...
Page 144 DCS 300 User’s Manual Field Description Hot Standby The number of seconds the DCS 300 waits Timeout after delivering a transaction to the 9161 controller to receive an acknowledgment for the transaction. If it does not receive an acknowledgment, the DCS 300 writes all transactions for the 9161 to a Hot Standby file.
Page 145: Adding A 9180 V1.X Controller
The number of bits to use for setting communications protocol. Stop bits The number of bits to use for setting communications protocol. Connecting to the 9180 and the Intermec CrossBar Network Value COM1, COM2 Predefined Check, Clear Even, Odd, None...
Page 146 DCS 300 User’s Manual Field Description Hot Standby The number of seconds the DCS 300 waits Timeout after delivering a transaction to the 9180 controller to receive an acknowledgment for the transaction. If it does not receive an acknowledgment, the DCS 300 writes all transactions for the 9180 to a Hot Standby file.
Page 147: Adding A 9180 V2.0 Controller
The number of bits to use for setting communications protocol. Stop bits The number of bits to use for setting communications protocol. Connecting to the 9180 and the Intermec CrossBar Network Value COM1, COM2 Predefined Check, Clear Even, Odd, None...
Page 148 DCS 300 User’s Manual Field Description Hot Standby The number of seconds the DCS 300 waits Timeout after delivering a transaction to the 9180 controller to receive an acknowledgment for the transaction. If it does not receive an acknowledgment, the DCS 300 writes all transactions for the 9180 to a Hot Standby file.
Page 149: Setting The Time Parameters
TCP/IP socket interface. Note: Do not enable time append on both the Intermec controller and the device itself. If it is enabled on both, two timestamps are appended to incoming data.
Page 150 DCS 300 User’s Manual To set the time parameters • From any Configure Controller dialog box, choose Time Parameters. The Configure Time Parameters dialog box appears. 5-16...
Page 151 This field specifies how often in minutes the controller appends the timestamp. If you set this field to 0, every message from a device will have a timestamp. Connecting to the 9180 and the Intermec CrossBar Network Value Check, Clear Check, Clear...
Page 152: Defining Default Hosts (9180 V2.0)
DCS 300 User’s Manual Defining Default Hosts (9180 v2.0) You can configure a default host for each of the types of hosts the 9180 devices will communicate with through the 9180 v2.0 controller. You can configure the devices to • explicitly link with a specific host.
Page 153: Defining The 9180 V2.0 Devices
Number of devices The number of logical names that you want to enable the DCS 300 to generate. Connecting to the 9180 and the Intermec CrossBar Network Value 1 to 13 alphanumeric and special characters...
Page 154: Identifying The Crossbar Devices
The device list is automatically populated with device addresses as you configure the Intermec controllers. The first eight addresses are enabled and are configured as J2020s. You need to change the device type for these addresses and enable the addresses of the other devices that you want to communicate with the host.
Page 155 8. Select a device whose individual parameters you want to edit and then choose Edit Device. For help, see “Editing a CrossBar Device” in the next section. 9. Choose OK to save your changes and return to the main screen. Connecting to the 9180 and the Intermec CrossBar Network 5-21...
Page 156: Editing A Crossbar Device
Able to receive data This check box determines if this device can receive data from the network. Device type This list box contains all the current Intermec devices supported by the DCS 300. Physical address This read-only field displays the physical address of the device.
Page 157: Saving Your Runtime Configuration
When you finish configuring your downline network, you should save your changes. To save your runtime configuration • From the main screen sidebar buttons, choose Save Configuration. Connecting to the 9180 and the Intermec CrossBar Network Value Predefined list 1 to 40 characters...
Page 158 DCS 300 System Manual blank...
Page 159: Running Data Collection Browser
Running Data Collection Browser...
Page 160 DCS 300 System Manual blank...
Page 161: Chapter Checklist
Now that you have configured the DCS 300 to communicate with your LAN and you have configured it to communicate with your Intermec RF network, you are ready to tie the entire data collection network together using Data Collection Browser™...
Page 162: About The Data Collection Browser
• You reduce project risk by using Web-based middleware servers. That is, you can deploy a data collection network and retain the flexibility to change the back-end system.
Page 163 Understanding the dcBrowser DCS 300 Here is how dcBrowser works: 1. A device running the dcBrowser client is turned on and it requests a Web page. 2. The dcBrowser gateway on the DCS 300 identifies the Web home page for this device.
Page 164: About The Environments
DCS 300 User’s Manual About the Environments There are three environments you should understand: Development Environment This environment is where you create the HTML application for your data collection devices. Your application development tool must support the HTML v3.2 syntax. You should test and debug your application in the development environment before you use the test environment.
Page 165: Setting Up The Runtime Environment
Equipment Needed • Web server • Web browser - Internet Explorer 4.0 or higher/Netscape Navigator 4.5 or higher (not provided by Intermec) • DCS 300 v1.3 or higher • Access points • Data collection devices that are loaded with the dcBrowser client.
Page 166: Running Your Html Application
DCS 300 User’s Manual Running Your HTML Application Use the runtime environment to run your HTML application in your data collection network. You need to start the Web server, the dcBrowser gateway, and the dcBrowser clients. The DCS 300 supports up to 127 terminal sessions. To run dcBrowser 1.
Page 167: Mapping Dcbrowser Devices
Mapping dcBrowser Devices If you want the dcBrowser devices to use a configuration other than the default configuration (Device 0), you need to map the dcBrowser devices. When a device connects to the dcBrowser gateway and it does not have its own configuration (as determined by the device's IP address), the gateway assigns it a new device ID and uses the Device 0 configuration.
Page 168 DCS 300 User’s Manual DCS 300 Configuration Page 3. Expand the Services menu and click dcBrowser Gateway. The dcBrowser Gateway Configuration page appears. 4. Enable or disable the links feature. For more information about the links feature, see the help. 5.
Page 169 1 to 223 (not including 127) and x is a value from 0 to 255. Port numbers can be from 1 to 65535. Most Web servers communicate on port 80. Instead of entering an IP address, you can enter the host name of the Web server that the device will communicate with.
Page 170: Starting The Web Server
DCS 300 User’s Manual To change a device’s mapping 1. From the dcBrowser Device Mapping Configuration page, select the device you want to change. 2. Change the information in the fields. 3. Click Update. 4. Click Save. To delete a device 1.
Page 171: Running Terminal Emulation
Running Terminal Emulation...
Page 172 DCS 300 System Manual blank...
Page 173: Chapter Checklist
Now that you have configured the DCS 300 to communicate with your LAN and you have configured it to communicate with your Intermec RF network, you are ready to tie the entire data collection network together using a terminal emulation application.
Page 174: About Terminal Emulation
DCS 300 logs 254 logical names, it will not accept messages from any new addresses. Host (3270) The following tables provide summaries of what TE applications you can run on which networks and what TE applications you can run on Intermec devices. Host Ethernet Token Ring...
Page 175 Host Connectivity Table VTXXX/ANSI 5250 SNA 3270 SNA TN5250 TN3270 TE 2000™ Native (sockets) TE Application Support Table VTXXX/ ANSI Trakker Antares terminal JANUS device WTP device VT220 Host Requirements TCP/IP host that supports Telnet TCP/IP devices do not need DCS 300 to run TE. When you send data from the device, the DCS 300 routes the data to the Telnet session on the host.
Page 176: Janus Te Applications
Note: If you are replacing a 9185 controller with a DCS 300, you must download the new JANUS TE application to all your JANUS devices. The JANUS TE applications are available for you to download from the Intermec Web site at www.intermec.com.
Page 177: Configuring Telnet Te (Vt/Ansi, Tn5250, And Tn3270)
Configuring Telnet TE (VT/ANSI, TN5250, and TN3270) When you set up your data collection network to run Telnet TE, you need to configure the DCS 300 and the devices. You can configure the DCS 300 to communicate with VT100, VT220, VT320, ANSI, TN5250, and TN3270 hosts. Configuring the DCS 300 Before you can run TE, you must identify all the IP hosts and their ports.
Page 178: Adding A Tcp/Ip Host
DCS 300 User’s Manual 3. Choose Add Host, Add Port, Edit, or Delete. Note: You cannot delete a host if it is linked to a device or a terminal session. If you choose Add Host, the TCP/IP Host Connection dialog box appears. For help, see “Adding a TCP/IP Host”...
Page 179: Adding An Ip Port
To determine the host IP address using DNS 1. In the Host name field, enter the abbreviated or long host name. If you enter the abbreviated name, the DCS 300 searches the domain names in the DNS Configuration dialog box to determine the long host name. 2.
Page 180: Configuring Your Janus Devices
DCS 300 User’s Manual Field Description Port name The name that identifies this port for this host. The name must be unique for this host. Port number The number of the port that you are configuring for this host. The number must be unique for this host.
Page 181: Downloading The Janus Te Application
2.4 GHz Terminal Emulation Quick Reference Guide. Downloading the JANUS TE Application You can download the JANUS TE application to your PC from the Intermec Web site at www.intermec.com. TE.CFG This file contains the configuration information that each JANUS device needs to run VT or ANSI TE.
Page 182: Configuring 5250 Sna Te
The device names are the logical names that you assigned when you identified these devices. For help, see Chapter 4, “Connecting to the Intermec RF Network.” To configure the DCS 300 1.
Page 183: Adding An Ibm Sna Host
5250 Terminal Emulation Configuration Dialog Box 3. Choose Add, Edit, or Delete. If you choose Add, the Host Connection Configuration dialog box appears. For help, see “Adding an IBM SNA Host” in the next section. Note: You cannot delete a host if it is linked to a device or a terminal session. 4.
Page 184 DCS 300 User’s Manual To add an IBM SNA host • From the 5250 Terminal Emulation Configuration dialog box, choose Add. The Host Connection Configuration dialog box appears. Field Description Host name A unique name for the SNA host. Use this internal name to make the host LU name easier to identify.
Page 185: Configuring The Sna Local Node
Field Description Address (Ethernet or The LAN adapter address of the host. token ring only) For help, see “Converting Ethernet Addresses to Token Ring MAC Format” in Appendix A. Configuring the SNA Local Node • From the 5250 Terminal Emulation Configuration dialog box, choose Local Node. The SNA Local Node Information dialog box appears.
Page 186: Selecting An Ibm Mode
DCS 300 User’s Manual Selecting an IBM Mode The IBM mode defines the terminal session characteristics between the DCS 300 and the SNA host. The default mode, #INTER, allows only eight sessions. If you need more than eight sessions, select a new IBM mode. Use the #ACCNET mode for systems that need a larger session limit (up to 254).
Page 187: Performing A Double Pass-Through On An Ibm As/400 Host
5250 Terminal Emulation Security Dialog Box Field Description Host user ID The user ID that lets the DCS 300 log into the host. Password The password that goes with the user ID. To remove a user ID and password 1. From the 5250 Terminal Emulation Configuration dialog box, select the host that has a user ID and password that you want to remove.
Page 188: Configuring 3270 Sna Te
DCS 300 User’s Manual To perform a double pass-through 1. On your terminal, log into the AS/400 that you want to use for the pass-through. At the command line on your terminal, type: where hostname is the name of the AS/400 you want to access. This host does not need to be defined on the DCS 300.
Page 189 1. Fill the NAU pool for each of the hosts, but do not explicitly link any terminals to hosts. Terminals can dynamically connect with any host that has available NAUs. Terminals must be configured with a host name, or the DCS 300 must be configured with a default host name.
Page 190: Adding An Ibm Sna Host
DCS 300 User’s Manual 4. (Optional) Fill the NAU pool for the hosts. For help, see “Filling the NAU Pool” later in this chapter. 5. Choose Local Node to configure the SNA local node. For help, see “Configuring the SNA Local Node” earlier in this chapter. Adding an IBM SNA Host You need to identify any hosts you want the DCS 300 to communicate with for your terminal sessions.
Page 191 Field Description Local PU A unique PU name for the host that allows the (Ethernet and token terminals to communicate with more than one ring only) host using the same upline network adapter card. For each host configuration for the upline card, you assign a unique host name and a unique local PU.
Page 192: Filling The Nau Pool
DCS 300 User’s Manual Filling the NAU Pool To edit the NAU pool and link terminals to hosts, see “Configuring TE Links” later in this chapter. 1. From the 3270 Terminal Emulation Configuration dialog box, choose NAU Pool. The 3270 NAU Pool dialog box appears. 2.
Page 193: Configuring Native Applications
You can update your Native client applications for WTP terminals using the terminal Application Development Kit (ADK). For more information on the ADK (Part No. 215- 299-001), contact your local Intermec representative. When you set up your data collection network to run Native applications, you may need to edit your Native host application if you are switching from a Native async serial host to an IP host.
Page 194: Configuring The Dcs 300
An excellent reference book for sockets programming is UNIX Network Programming by W. Richard Stevens (ISBN 0- 13-949876-1). Note: Intermec does not provide application programming support for streams/sockets programming. The DCS 300 initiates communications with the host application through the configured port.
Page 195 To configure an IP host 1. From the main screen, choose Terminal Emulation. 2. Choose IP Host. The IP Terminal Emulation Configuration dialog box appears. The list box contains the host names that you have configured. Hosts that have ports are prefixed by a + (plus) sign or a - (minus) sign. Double-click on a host name with a + sign and the ports that have been configured for that host appear underneath it.
Page 196: Adding A Tcp/Ip Host
DCS 300 User’s Manual Adding a TCP/IP Host • From the IP Terminal Emulation Configuration dialog box, choose Add Host. The TCP/IP Host Connection dialog box appears. Field Description Host name The name that logically identifies the TCP/IP host to the network. Use DNS This check box determines if you use a DNS server to resolve the IP address of this host.
Page 197: Adding An Ip Port
To configure the host IP address manually 1. In the Host name field, enter the host name. 2. Make sure the Use DNS check box is cleared. 3. In the IP address field, enter the host IP address. 4. Choose OK to save your changes and then return to the IP Terminal Emulation Configuration dialog box.
Page 198: Running The Application
DCS 300 User’s Manual Field Description Type These option buttons identify the type of port that you are configuring. Send ID This check box determines if the terminal (Native only) session name, RF host stack number, and the terminal number are sent to the host. Running the Application Once you edit your host application and you configure the DCS 300, you can start running your Native application.
Page 199: Wtp Devices
WTP Devices 1. Verify that each device has its terminal session configured for Native communications. For help, see the WTP device’s user’s manual. 2. Start data collection. For help, see “Starting Data Collection” in Chapter 2. The Native client starts when you turn on the device. WTP devices send a power-up packet that contains a 2-byte device number followed by the device type.
Page 200 DCS 300 uses whatever method that you specified when you configured the connection point. For help, see Chapter 4, “Connecting to the Intermec RF Network.” When the terminal session of the device is started, it will prompt the user to enter a host name.
Page 201: Setting Security For The Te Configuration Menu
c. Choose Link to Host. The terminal session is removed from the Unlinked Device - State list box and it is added to the Linked Terminal Sessions box. 3. Select any terminal sessions that you want to prompt the user for a host. a.
Page 202 DCS 300 User’s Manual You can temporarily change the password on the device. The device stores the new encrypted password in a TE.SEC file. However, each time you start the TE application, the device requests the password that is stored on the DCS 300. Therefore, if you want to permanently change the password, you must change it from the DCS 300.
Page 203 The Terminal Password dialog box appears. 4. In the Password field, enter the password to access the TE Configuration menu. The password can be up to ten alphanumeric characters. 5. Choose Add. The terminal or terminals you selected appear in the Secured Terminals list box.
Page 204: Using The Auto Login Feature
2. Choose View Runtime Configuration and then choose Start. The View Runtime Configuration Options dialog box appears. 3. Make sure that the Intermec controllers/Devices check box is checked and choose Run View. The Runtime Configuration dialog box appears. 4. Scroll through the file until you see a list of the devices that are enabled. If Password Protected is Yes, then security is set.
Page 205: Trakker Antares Terminals
To use the auto-login feature • For VT/ANSI, press < • For 5250 or 3270, press • Or, you can scan: Auto-Login Restart *%ALRS* *%ALRS* To logoff from the host and use the auto-login feature VT/ANSI At the TE prompt, type script file is in the current directory, you return to the first screen after the login screen.
Page 206: Displaying International Characters
DCS 300 User’s Manual Displaying International Characters You can configure your JANUS devices and your Trakker Antares terminals to display single-byte international characters. That is, the device displays screen data using various character sets while running terminal emulation. This feature maps SBCS code pages for various Latin-based languages to SBCS code page 850, a multilingual code page for Latin-based languages.
Page 207: Trakker Antares Terminals
Trakker Antares Terminals On the DCS 300, you can find the .MAP files in the directory. TE\INTERNAT To use international character sets 1. On the DCS 300, rename the desired code page table .MAP file to Refer to the table on the next page. 2.
Page 208: Saving And Activating Your Runtime Configuration
DCS 300 User’s Manual Saving and Activating Your Runtime Configuration If you are done configuring the DCS 300, save and activate your runtime configuration. When the activation is complete, a message box appears if you need to reboot the DCS 300. To save and activate your runtime configuration 1.
Page 209: Running Peer-To-Peer Applications
Running Peer-to-Peer Applications...
Page 210 DCS 300 System Manual blank...
Page 211: Chapter Checklist
Now that you have configured the DCS 300 to communicate with your LAN and you have configured it to communicate with your Intermec network, you are ready to tie the entire data collection network together using an application. This chapter explains how to configure your DCS 300 for using peer-to-peer applications and it provides guidelines on how to write TCP/IP or APPC applications so that they can communicate with the DCS 300.
Page 212: About Peer-To-Peer Applications
DCS 300 User’s Manual About Peer-to-Peer Applications The DCS 300 runs an applications programming interface (API) that makes communicating with remote applications easier. Applications communicate with the DCS 300 through network communications processes called NetComms. NetComms are responsible for safely routing data from remote applications across a network to the DCS 300 and back.
Page 213: Configuring The Host For Peer-To-Peer Applications
Configuring the Host for Peer-to-Peer Applications For peer-to-peer applications, your network administrator needs to set up certain parameters on the host for TCP/IP or APPC applications. TCP/IP Applications IP address The IP address is the address that is assigned to the Ethernet card or token ring card in the DCS 300.
Page 214: Setting Up Peer-To-Peer Links
DCS 300 User’s Manual Setting Up Peer-to-Peer Links To run TCP/IP or APPC applications in your data collection network, you must identify all the application names in the DCS 300. The DCS 300 puts these names in a peer-to- peer destination list. Every time an application connects to the DCS 300, it informs the DCS 300 of its name.
Page 215 Peer-to-Peer Destination Parameters Dialog Box Field Description Destination name The meaningful name that identifies the destination (application). Hot Standby timeout The number of seconds the DCS 300 waits for a response from this destination before it places transactions going to this destination in a Hot Standby file.
Page 216: Using International Text Pass-Through
DCS 300 User’s Manual Field Description International text This check box determines how much of the pass-through transaction is converted. If you check this check box, the DCS 300 converts only the transaction header. If you clear this check box to use limited EBCDIC mapping, the DCS 300 converts the entire transaction.
Page 217: Adding A Transaction
Character Encoding Scheme Table (continued) Host JANUS devices Trakker Antares terminals Before you use this feature, note the following: • The DCS 300 attaches a transaction header to messages that it receives from hosts and it attaches a transaction ID to route messages to and from devices. The characters in the transaction header and the transaction ID are limited by what you can type on the DCS 300.
Page 218: Adding A Transaction Field
DCS 300 User’s Manual Transaction Parameters Dialog Box Field Description Transaction ID The unique ID of the transaction. Hot Standby The message that is sent to the source of the message (Optional) transaction when the DCS 300 places the transaction in a Hot Standby file. Delimiter The character that separates the fields in the transaction.
Page 219: Saving And Activating Your Runtime Configuration
Transaction Field Parameters Dialog Box Field Description Field name The unique name for the transaction field. Number The order or position of the field in the transaction. Fields start at 1. Saving and Activating Your Runtime Configuration When you finish configuring peer-to-peer applications, you should save your changes. If you are done configuring the DCS 300, save and activate your runtime configuration.
Page 220 DCS 300 User’s Manual The server NetComms use the TCP/IP socket API to provide a standard interface to TCP/IP Transport and Internet layers. The API supports the “streams” socket-type interface, which is a reliable, connection-oriented service. When data is sent, the transmission of the data packet is guaranteed and it is received in the same order as it was sent.
Page 221: How The Dcs 300 Communicates With Applications
The DCS 300 supports only requester (client) connections. The remote application initiates both sockets. For help, see the DCS 300 Technical Reference Manual. How the DCS 300 Communicates With Applications To use the NetComms, you must first configure the DCS 300 for TCP/IP communications.
Page 222: Understanding Transaction Routing In A Tcp/Ip Network
DCS 300 User’s Manual NetComms Communicating Directly With Applications Remote machine Local machine Understanding Transaction Routing in a TCP/IP Network The applications you create to interact with the DCS 300 function as remote applications. When your application receives a message from the DCS 300, your application must perform these steps: 1.
Page 223 When your application sends unsolicited data to the DCS 300, your application must perform these steps: 1. The application builds the transaction and provides either a destination or a transaction ID. 2. The application clears the fNetACK flag. 3. The application sends the transaction to the receive NetComm. Because the fNetACK flag is clear, the receive NetComm routes the transaction to the Receive channel, which sends the transaction to the message handler.
Page 224 DCS 300 User’s Manual Your applications will use TCP sockets to communicate with the DCS 300 across a TCP/IP network. The DCS 300 sets up two channels: Receive channel The low priority Receive channel handles unsolicited transactions from devices and applications, and handles system transactions from applications. ACK channel The high priority ACK channel handles acknowledgment (ACK) transactions from applications and devices.
Page 225: Communicating Through The Direct Tcp/Ip Socket Interface
Communicating Through the Direct TCP/IP Socket Interface The direct TCP/IP socket interface allows non-TCP/IP capable devices, such as JANUS 900 MHz RF devices and Trakker Antares terminals, to establish a TCP/IP socket connection to the host through the DCS 300. For more information on using the direct TCP/IP socket interface, see the DCS 300 Technical Reference Manual.
Page 226 DCS 300 User’s Manual Direct TCP/IP Socket Interface TCP/IP network 8-18 Devices Access (TCP/IP clients) point DCS 300 Message Handler/ DevComm Network connection 0300U035.eps Remote application...
Page 227: Direct Tcp/Ip Api Vs. Netcomm Api
Running Peer-to-Peer Applications Direct TCP/IP API vs. NetComm API By using the direct TCP/IP API, you no longer need to write applications that communicate with the peer-to-peer interface of the DCS 300. You write your client application to communicate with an existing TCP/IP server application. The server application does not even know the DCS 300 exists.
Page 228: About The $Ipt Transaction Id
DCS 300 User’s Manual About the $IPT Transaction ID $IPT is a special transaction ID that contains the protocol that allows JANUS RF devices and Trakker Antares terminals to communicate with the DCS 300 using the direct TCP/IP socket interface. Every transaction from a device needs $IPT as the transaction ID, which allows the server DevComm to route the data to the proper queue.
Page 229: Using International Text Pass-Through
Using International Text Pass-Through International text pass-through allows data streams representing characters encoded in various encoding schemes to pass through the DCS 300 without conversion between various hosts and devices. The data streams appear to the DCS 300 as arbitrary streams of bytes passed between the hosts and devices.
Page 230: Communicating With Appc Applications
DCS 300 User’s Manual Communicating With APPC Applications You can use device on an SNA network. Before you write familiarity with communicate with the DCS 300. APPC applications, acting as remote requester applications, initiate the connection to the DCS 300. The DCS 300 waits for the connection to be initiated. The remote applications can be receive, send, interactive, or batch applications.
Page 231: Appc Verbs
DCS 300 and the host. The DCS 300 takes care of communications on its side, but you must make sure you build the applications to handle communications on the host side. Intermec recommends that you have some familiarity with the APPC/LU These are the primary verbs that you can use to communicate with the DCS 300.
Page 232 blank...
Page 233: Running Terminal Sessions
Running Terminal Sessions...
Page 234 DCS 300 System Manual blank...
Page 235: Chapter Checklist
Now that you have configured the DCS 300 to communicate with your LAN and you have configured it to communicate with your Intermec network, you are ready to tie the entire data collection network together using an application. This chapter explains how to set up VT, ANSI, 5250, or 3270 terminal sessions on the DCS 300.
Page 236: About Terminal Sessions
DCS 300 User’s Manual About Terminal Sessions You can establish Telnet, 5250 SNA, or 3270 SNA terminal sessions between the DCS 300 and your host. Use these sessions on the DCS 300 to access your host directly from the DCS 300. By accessing your host, you can verify your host connection and you can start remote applications.
Page 237: Configuring The Host For Terminal Sessions
Configuring the Host for Terminal Sessions For Telnet, 5250 SNA, or 3270 SNA terminal sessions, there are relationships between emulation modes and network adapter cards. This section outlines the network administrator tasks for the special relationships between emulation modes and cards. This table lists the emulation modes and the network adapter cards they support.
Page 238: Setting Up 3270 Terminal Sessions Using Ethernet
DCS 300 User’s Manual Setting Up 3270 Terminal Sessions Using Ethernet If you are setting up 3270 terminal sessions over an Ethernet network, your network administrator needs to create a controller remote workstation and then a device to go with the controller on the host. The device definition provides the local location address (NAU) for the DCS 300.
Page 239: Creating Terminal Sessions
Creating Terminal Sessions This section explains how to define the communications parameters for the Telnet, 5250 SNA, and 3270 SNA terminal sessions between the DCS 300 and your host. You can use these sessions to access the host from the DCS 300 or you can use them for screen mapping sessions.
Page 240: Adding A Telnet Terminal Session
DCS 300 User’s Manual Adding a Telnet Terminal Session • From the Terminal Session List dialog box, choose Telnet. The Terminal Session Definition dialog box appears. Field Description Session name A meaningful name for this terminal session. Mode The type of terminal mode that you want to use for this terminal session.
Page 241: Adding A Tcp/Ip Host
Adding a TCP/IP Host To communicate with TCP/IP hosts, the DCS 300 needs to know their IP addresses. You can either use DNS to resolve these IP addresses or you can enter them in manually. To add a TCP/IP host •...
Page 242: Customizing The Vt Terminal Setup
DCS 300 User’s Manual 3. (Optional) Choose Resolve. The server searches for the host name in the domains that are listed in the DNS Configuration dialog box and resolves the IP address. 4. Choose OK to save your changes and return to the Terminal Session Definition dialog box.
Page 243 Field Description Cursor keys Determines whether the arrow keys on the terminal control cursor movement (normal) or they send their application control functions (application). Keypad Determines whether the number keys on the terminal send their keycap characters (numeric) or they send their programming functions (application).
Page 244: Adding A 5250 Sna Terminal Session
DCS 300 User’s Manual Adding a 5250 SNA Terminal Session Use this dialog box to configure 5250 SNA terminal sessions between your DCS 300 and your host. You also need to define terminal sessions that you can use for screen mapping sessions.
Page 245 Field Description Session name A meaningful long session ID that identifies this terminal session. Short session ID The alpha identifier for this terminal session. Host Name The name of the host to which the terminal session connects. For help adding a host, see “Adding an IBM SNA Host”...
Page 246: Adding An Ibm Sna Host
DCS 300 User’s Manual Adding an IBM SNA Host You need to identify any hosts you want the DCS 300 to communicate with for your terminal sessions. When you add a host, you set up a link to a specific host and this information is available throughout the system.
Page 247 Field Description Host name A name that identifies this SNA host. You use (Optional) this internal name to make the host LU name more meaningful. Adapter card The network adapter card you are using to connect to the host. Network ID Identifies the network ID on which the host resides.
Page 248: Configuring The Sna Local Node
DCS 300 User’s Manual Configuring the SNA Local Node These parameters identify the DCS 300 to the SNA network. Once configured, these parameters apply system-wide for all SNA connection types and you do not need to set them again. To configure the SNA local node •...
Page 249: Adding A 3270 Sna Terminal Session
Adding a 3270 SNA Terminal Session Use this dialog box to configure 3270 SNA terminal sessions between your DCS 300 and your host. You also need to define terminal sessions that you can use for screen mapping sessions. You need to identify the SNA local node. For help, see “Configuring the SNA Local Node”...
Page 250: Adding An Ibm Sna Host
DCS 300 User’s Manual Adding an IBM SNA Host You need to identify any hosts you want the DCS 300 to communicate with for your terminal sessions. When you add a host, you set up a link to a specific host and this information is available throughout the system.
Page 251 Field Description Host name A name that identifies this SNA host. You use (Optional) this internal name to make the host LU name more meaningful. Adapter card The network adapter card you are using to connect to the host. Local PU A unique PU name for the host that allows the (TE only) terminals, when running TE, to communicate...
Page 252: Configuring The Sna Local Node
DCS 300 User’s Manual Configuring the SNA Local Node These parameters identify the DCS 300 to the SNA network. Once configured, these parameters apply system-wide for all SNA connection types and you do not need to set them again. To configure the SNA local node •...
Page 253: Saving And Activating Your Runtime Configuration
Saving and Activating Your Runtime Configuration When you are done configuring your terminal sessions, you should save your changes. If you are done configuring the DCS 300, activate your runtime configuration. When the activation is complete, a message box appears if you need to reboot the DCS 300. To save and activate your runtime configuration 1.
Page 254: Mapping Terminal Keyboards To The Dcs 300 Keyboard
DCS 300 User’s Manual 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 the session you want to start. 4. Choose Start. The host session starts and the host window appears. 5.
Page 255 VT/ANSI Terminal Keyboard Ctrl-[ Delete Return Key Combination Legend Shift Base Running Terminal Sessions F15/Help F16/Do Find Prev Scrn Remove Select Next Scrn ∅ Ctrl-H Enter 0300U.039 9-23...
Page 256 DCS 300 User’s Manual 5250 Terminal Keyboard BckTab RqTab CapsLk CapsLk ShftLk LShft LShft Reset Reset Key Combination Legend Shift Ctrl Base AltGr 9-24 PrtH Help Clear PrtP Help Clear SysReq ImmRst TstReg BckSpc BckSpc RQBS NumLk NumLk NumLk NewLne Enter Home TOPPAG...
Page 257 3270 Terminal Keyboard BckTab NxtWin NxtWin CapsLk CapsLk CapsLk LShft LShft Reset Reset PrCncl Key Combination Legend Shift Ctrl Base AltGr Alt+Shift Running Terminal Sessions ScrLk Restrt Print Clear ScrLk PrCtrl SysReq BckSpc BckSpc Undo NumLk NumLk NumLk NewLne NewLne Home Rshft Rshft...
Page 258 DCS 300 System Manual blank 9-26...
Page 259: Running Screen Mapping
Running Screen Mapping...
Page 260 DCS 300 System Manual blank 10-2...
Page 261: Chapter Checklist
Now that you have configured the DCS 300 to communicate with your LAN and you have configured it to communicate with your Intermec network, you are ready to tie the entire data collection network together using screen mapping. Before you can run screen mapping, you need to have defined your terminal sessions in Chapter 9, “Running Terminal Sessions.”...
Page 262 DCS 300 User’s Manual Chapter Checklist (continued) Done? 10-4 Task View and check the script. Map the transaction fields to the host screen fields. Save the configuration. Page 10-58 10-68 10-69...
Page 263: About Screen Mapping
Note: Transactions sent by Trakker Antares terminals and JANUS devices and running in the Intermec 2.4 GHz RF network have a maximum length of 1024 characters, including delimiters. Transactions sent by JANUS devices running in the Intermec 900 MHz RF network have a maximum length of 254 characters, including delimiters.
Page 264 DCS 300 User’s Manual This figure shows data originating from a JR2020 being sent through a BRU to the DCS 300 to a host application running in a terminal emulator. Typical Screen Mapping Application 10-6 d io R FN R FN WO 1 TRX Part # : 6020...
Page 265: About Script Files
Script files contain the logic for mapping the transaction data that is exchanged between devices and a host. Using script files, the DCS 300 maps transaction fields into host screens. Intermec has designed the Script Builder Tool as a local interface tool that lets you easily create, edit, and check script files.
Page 266: Single Transaction Script Files Vs. Multiple Transaction Script Files
DCS 300 User’s Manual Single Transaction Script Files vs. Multiple Transaction Script Files You can build a script file that contains only one transaction or you can build a script file that contains many transactions, as long as they all branch from one host screen. A single transaction script file is the easiest to build.
Page 267 Multiple Transaction Script vs. Single Transaction Script Example Main host screen First mapping screen Main host screen/First mapping screen Running Screen Mapping Screen 1 ↓ Screen 2 ↓ Screen 3 ↓ Screen 4 ↓ Screen 5 Back to Screen 1 Screen 4 ↓...
Page 268: Identifying Key Elements For The Script File
DCS 300 User’s Manual Identifying Key Elements for the Script File Before you create your screen mapping application, you need to be able to identify key elements, such as the main host screen, transactions, and host screen fields, for the script file.
Page 269 Running Screen Mapping Screen 3 Screen 4 (Main Host Screen) Screen 5 10-11...
Page 270: Example 2 - Multiple Transaction Script File
DCS 300 User’s Manual Example 2 - Multiple Transaction Script File This example adds another transaction to Example 1. Besides the work order add transaction, the script file processes a work order quantity inquiry transaction. The result of the query is sent back to the application that is running on the terminal. These screens show two transaction paths branching from Screen 3.
Page 271 Screen 4 (Menu Option 915) Screen 6 (Menu Option 910) Running Screen Mapping Screen 5 Screen 7 10-13...
Page 272: Understanding How The Script Builder Tool Flows
DCS 300 User’s Manual Understanding How the Script Builder Tool Flows Use this table and the flow chart on the next page to help you understand how to use the Script Builder Tool. Step Button Names New/Open Logon Transaction Field List Region List Next Screen Normal Logoff...
Page 273 Running Screen Mapping Script Builder Tool Flow Chart New Script Logon Sequence Define Main Host Screen Select Transaction Define Fields Define Regions Define Next Screen Normal Logoff Sequence Abnormal Logoff Sequence Save Script 10-15...
Page 274: Using The Script Builder Tool
DCS 300 User’s Manual Using the Script Builder Tool To use screen mapping, you need to create a script file. If you want to capture keystrokes on the host screen for a logon, a normal logoff, and an abnormal logoff, you need to start a temporary host session.
Page 275: Creating A New Script File
Creating a New Script File 1. From the Script Builder Tools window, choose Script. 2. Choose New/Open. The New/Open Script dialog box appears. Field Description Script name The unique name of the script you are creating or opening. Description A paragraph of text that describes the script. (Optional) Session ID The session ID that you want to use when...
Page 276: Opening An Existing Script File
DCS 300 User’s Manual Opening an Existing Script File You need to start a temporary host session to capture keystrokes for logon, logoff, and abnormal logoff sequences. You also need an active host session if you want to use the Get Field feature.
Page 277: Copying A Script File
Copying a Script File 1. Open the script file that you want to copy. For help, see “Opening an Existing Script File” earlier in this chapter. 2. From the Script Builder Tools window, choose Script. 3. Choose New/Open. The New/Open Script dialog box appears. 4.
Page 278 DCS 300 User’s Manual Save As Script With Different Transaction Names Dialog Box 9. In the Transaction name field, enter the name of the new transaction and choose Change Name. The old and new transaction names appear in the Old Transaction Name - New Transaction Name list box.
Page 279: Deleting A Script File
Deleting a Script File 1. From the Script Builder Tools window, choose Script. 2. Choose Delete. The Delete Script dialog box appears. 3. In the Script name field, click the down arrow on the right side of the field. A list of existing script files appears.
Page 280: Setting Options For The Script File
DCS 300 User’s Manual Setting Options for the Script File Within the Script Builder Tools window, you can set certain script variables for the current script. Choose Defaults if you want to set this dialog box to default values. To set options for the entire script 1.
Page 281 Field Description EHLLAPI EHLLAPI uses this character to represent mnemonic special keys. This character must not occur in any keystroke of transaction data. Concatenation char The script uses this character to concatenate components of a message. This character must not occur in any static text of a message, such as a region label, or in any script keystroke name, such as CUR_POS.
Page 282: About The Data Response Timeout (Vt/Ansi)
DCS 300 User’s Manual About the Data Response Timeout (VT/ANSI) In 3270 SNA and 5250 SNA screen mapping, the host application locks the terminal keypad while it is busy. When the keypad is unlocked, the host application is ready for the next action, such as another script command or keystroke.
Page 283: Creating Host Access Sequences
Running Screen Mapping Creating Host Access Sequences For each script, you need to capture the keystrokes for a logon sequence, a normal logoff sequence, and an abnormal logoff sequence. Logon sequences are keystrokes that take the script from the logon screen to the first host screen that receives all transactions for this script, such as the main host screen.
Page 284: Creating A Logon Sequence
DCS 300 User’s Manual Creating a Logon Sequence The logon sequence contains the keystrokes that get you from the login screen to the main host screen. The main host screen is the first host screen where every transaction in the script starts. To create a logon 1.
Page 285 7. In the Main screen field, click the down arrow on the right side of the field. A list of all the available host screens appears. Select a host screen to be the main screen. Or, choose Define to define a new host screen that you want to use as the main screen.
Page 286: Creating A Normal Logoff Sequence
DCS 300 User’s Manual Creating a Normal Logoff Sequence The normal logoff sequence contains keystrokes that exit you from the host application from the main host screen. To create a normal logoff 1. From the Script Builder Tools window, choose Host Access. 2.
Page 287: Creating An Abnormal Logoff Sequence
Example: Keystrokes Appearing in Normal Logoff Sequence Home “signoff” Enter Creating an Abnormal Logoff Sequence The abnormal logoff sequence contains keystrokes that exit you from the host application from any host screen. Abnormal logoffs usually occur when the DCS 300 encounters a critical error.
Page 288: Editing The Captured Keystrokes
DCS 300 User’s Manual 3. Choose Start. 4. In the host window, enter the keystrokes you want to use for your abnormal logoff. The Script Builder Tool captures all the keystrokes that you type. 5. When you finish entering the keystrokes for the abnormal logoff, choose Stop. The keystrokes you typed appear in the Captured Keystrokes box.
Page 289: Selecting Transactions For The Script
3. Choose Before to insert the new keystroke before the selected line. Choose After to insert the new keystroke after the selected line. Selecting Transactions for the Script You need to define all the transactions you want this script to handle. For help, see “Adding a Transaction”...
Page 290: Selecting Host Screens For The Current Transaction
DCS 300 User’s Manual Selecting Host Screens for the Current Transaction You need to identify the host screens that receive transaction data from the current transaction. The current host screen is the host screen for which you are currently defining fields, regions, messages, and events. When you define the main host screen, it automatically becomes the current host screen.
Page 291: Defining Next Screen Sequences For Host Screens
Defining Next Screen Sequences for Host Screens You need to define the sequence of host screens that the current transaction uses for mapping its fields. In the Next Screen box, check the Yes check box if your transaction fields map to host screen fields on more than one host screen.
Page 292 DCS 300 User’s Manual Next Host Screen Dialog Box 7. In the Next Screen box, check Yes if you want to assign the next screen. To select an existing host screen for the next screen, click the down arrow on the right side of the Name field.
Page 293: Selecting Host Screen Fields For The Current Host Screen
Selecting Host Screen Fields for the Current Host Screen You must identify all the fields on the current host screen that receive transaction data. To select host screen fields 1. From the Script Builder Tools window, choose Screen. 2. Choose Fields. The Host Screen Field List dialog box appears. This list box displays all of the fields that are defined for the current host screen, their location in the host screen, and whether they receive their data from a transaction field or a static string.
Page 294: Adding A Host Screen Field
DCS 300 User’s Manual Adding a Host Screen Field Different transactions may contain fields that map to the same host screen field. If you click the down arrow on the right side of the Field label field, you can choose from a list of defined host screen fields.
Page 295 Field Description Field label A unique name for the field. The row position on the host screen of the first character of the field. Column The column position on the host screen of the first character of the field. Length The maximum number of characters this field accepts.
Page 296: Getting Host Screen Field Attributes From A Host Screen
DCS 300 User’s Manual Getting Host Screen Field Attributes From a Host Screen In 5250 field-formatted host screens, there are two types of fields: protected and unprotected. Protected fields are fields that you cannot write over and are usually text on the host screen.
Page 297: Selecting Regions For The Current Host Screen
Selecting Regions for the Current Host Screen Regions are areas on the host screen. You can define a region that the script file examines to determine whether or not a certain condition has been met or you can define a region from which the script file reads data. Specifically, you usually define a region to •...
Page 298: Adding A Region
DCS 300 User’s Manual Adding a Region There are three types of actions that you can define when a region appears: • Send a message to the source of the transaction. • Capture keystrokes to clear the region. • Determine what event happens when the region is done performing its actions. The default action is to continue processing screen events.
Page 299 Host Screen Region Definition Dialog Box Field Description Region label A name for the region that is unique within the current screen. Region group This check box determines if you want this (Optional) region to be part of a group of regions that share the same action in the Actions for Region NOT appearing box.
Page 300 DCS 300 User’s Manual Field Description Specific string Lets you define a specific string the DCS 300 must identify at the specified row and column positions before it recognizes the region. Any string within Specifies the length of a region from the specified row position.
Page 301: Getting A Region From A Host Screen
Getting a Region From a Host Screen In 5250 field-formatted host screens, there are two types of fields: protected and unprotected. Protected fields are fields that you cannot write over and are usually text on the host screen. Unprotected fields are usually input fields. To get region attributes from a host screen field, you position the host cursor anywhere in an unprotected field and then choose Get Region.
Page 302: Capturing Keystrokes
DCS 300 User’s Manual Capturing Keystrokes Before you can use the capture keystrokes feature, you must start a temporary host session. For help, see “Starting a Host Session” in Chapter 9. To capture keystrokes 1. From the Host Screen Region Definition dialog box, check the Keystrokes to clear check box.
Page 303: Defining Next Host Screen Sequences For Regions
Defining Next Host Screen Sequences for Regions You may want the script file to go to a different host screen when it is finished performing all the actions for the region. If you are defining a host screen for the region to go to when it catches an error message, you usually want the script file to return to the main host screen.
Page 304: Creating Screen And Region Messages
DCS 300 User’s Manual 4. In the host window, enter the keystrokes to go to the next screen. The Script Builder Tool captures all the keystrokes that you type and enters them into the Captured Keystrokes box. 5. When you finish entering the keystrokes, choose Stop. The keystrokes you typed appear in the Captured Keystrokes box.
Page 305 To create messages 1. From the Script Builder Tools window, choose Screen. 2. Choose Message List. The Screen Message List dialog box appears. 3. Add, edit, or remove messages for the current host screen. For help, see “Adding a Message” later in this chapter. 4.
Page 306: Adding A Message
DCS 300 User’s Manual Adding a Message Use messages to carry information from the host application to the application that is running on the terminal. You can only define one message per transaction per script file to be sent back to the terminal. You can define two types of messages: Status message This message appears in the status line of your terminal.
Page 307 Field Description Name A unique name for the message. Type The type of message you want to send to the source of the transaction. Status message Use this message type to define a text message in the Text field. This message will appear in the status line at the bottom of the terminal screen that originated the transaction.
Page 308: About Message Types (Status Vs. Transaction)
DCS 300 User’s Manual About Message Types (Status vs. Transaction) Screen and region messages can be sent to the source of the transaction as a status message or as a transaction. A status message is text that appears in the status line at the bottom of the terminal screen.
Page 309: Changing The Order Of Screen Events
Transaction Message Example Terminal Terminal Changing the Order of Screen Events You can change the order of screen events and you can change the order of the regions within a region group. As each host screen appears, certain screen events can occur. These events include •...
Page 310 DCS 300 User’s Manual To change the order of screen events 1. From the Script Builder Tools window, choose Screen. 2. Choose Event Order. The Screen Event Ordering dialog box appears. 3. In the Screen Events list box, select the event you want to move. Events occur in order starting from the top.
Page 311: Maintaining The Host Screens
Running Screen Mapping Maintaining the Host Screens The Maintain Screen List dialog box lets you add any new host screens that you did not create when you defined the host screen sequences. You can also edit and delete host screens. For help, see “Adding a Host Screen” later in this chapter. Note: You may not be able to delete the host screen if other transactions send data to it.
Page 312: Adding A Host Screen
DCS 300 User’s Manual Field Description Selected Screens This list box contains the host screens that receive transaction data from the current transaction. Available Screens This list box contains all the host screens that are available to use. Adding a Host Screen Each host screen definition corresponds to a different host screen.
Page 313: Getting The Screen Identifier From The Host Screen
Field Description Screen label A unique name for the screen Description A description for the screen. (Optional) The row position on the host screen of the first character of the screen identification string. Column The column position on the host screen of the first character of the screen identification string.
Page 314: Defining User Blocks
DCS 300 User’s Manual 3. In the host window, place your cursor on the screen identifier. Note: In VT or ANSI host screens, you must select the entire screen identifier. 4. In the Host Screen Definition dialog box, choose Get Field. The Screen Identifier box is populated with the attributes of the field.
Page 315: Adding A User Block
Running Screen Mapping 5. Choose User Blocks. The User Block List dialog box appears. 6. Add, edit, or delete user blocks. For help, see “Adding a User Block” later in this chapter. 7. Choose Close to return to the Script Builder Tools window. Adding a User Block You can add user blocks after any line in the script that has a plus (+) sign in the left margin.
Page 316: Viewing The Script
DCS 300 User’s Manual User Block Text Dialog Box 3. Enter the comment or command. 4. Choose OK to return to the User Block List dialog box. Viewing the Script This feature provides you with a hierarchical view of the current script. Since the logic flow of the script is driven by transactions, the View Script feature displays the transactions as the top level in the script structure.
Page 317 View Script Structure Dialog Box 2. Scroll through the script. A plus (+) on the left side of a line indicates that more information is underneath the heading that is collapsed. 3. Double-click on a line with a + on the left side to expand it. Or, double-click on a line with a minus (-) on the left side to collapse it.
Page 318: Checking A Script File
When you finish editing the script file, you can use the script checker to check it for correct syntax. Intermec has also provided some general guidelines to help you check the logic of your script file. Always verify the script syntax before you verify the script logic.
Page 319: Verifying The Script File Logic
The top part of the DCS 300 View Results window displays the result of the script checker. You may see some errors and warnings. Your script file should still run with warnings, but you must resolve all errors. Verifying the Script File Logic To test the logic of the script file, you must set up a test environment and start data collection on the DCS 300.
Page 320 DCS 300 User’s Manual 3. From the main screen sidebar, choose Start Data Collection. Note: If you stop data collection because the script fails, clear the Hot Standby file for the screen mapping session you are testing and make sure that the host terminal session is at the logon prompt before you restart data collection.
Page 321 c. In the (D)ata or (S)ystem field, enter D. d. In the Data field, enter the data that the transaction needs to be successful. If the transaction contains data for multiple host screen fields, separate each field with a comma and make sure that the field order matches what you have defined in the script file.
Page 322 DCS 300 User’s Manual Verify that • the script file handles the error properly. Usually, the script file clears the error condition, sends a message to notify the source that the transaction has failed, and then returns to the main host screen to wait for the next transaction. Problem The script file is stuck in a host...
Page 323: Setting Up Screen Mapping Sessions
Setting Up Screen Mapping Sessions When you define a screen mapping session, you define specific transactions to be sent to a specific host terminal session using a specific script file. Screen mapping sessions allow multiple terminal sessions on the DCS 300 to simultaneously communicate with multiple terminal emulator sessions running on different hosts.
Page 324: Adding A Screen Mapping Session
DCS 300 User’s Manual Adding a Screen Mapping Session Intermec highly recommends that you use the Script Builder Tool for creating and editing script files. In the Screen Mapping Session Definition dialog box, if you choose Create or Edit and then you save your changes, the Script Builder Tool will not recognize the script file and you will not be able to open this script file using the Script Builder Tool.
Page 325 Field Description Name A meaningful name that identifies this screen mapping session. Visible when data This check box determines if the screen collection started? mapping application automatically opens the host terminal session when you start data collection. Start session at data This check box determines if the screen collection start mapping application automatically starts when...
Page 326: Mapping Transaction Fields
If you use the Script Builder to generate your script files, you usually do not need to map transaction fields. Intermec highly recommends that you use the Script Builder Tool to generate your script files.
Page 327: Adding A Screen Mapping Field Placement Entry
Adding a Screen Mapping Field Placement Entry • From the Screen Mapping Field List dialog box, choose Add. The Screen Mapping Field Placement dialog box appears. Field Description Name The name of the transaction field that you want to map to a screen field. Name The screen that contains the field that you want to map to the transaction field.
Page 328: Script Builder Tool Limitations
The destination is always fixed to SRC, the source of the transaction, which is assumed to be an Intermec terminal. The SRC can only receive the message if the Wait for response check box is checked in the Terminal Screen and Fields dialog box.
Page 329: Vt/Ansi Screen Mapping Limitations
For transaction messages, the format of this command that is generated by Script Builder Tool is: SEND_MESSAGE userdefinedtext + [regionlabel | CUR_POS | CUR_ROW] The user-defined text contains data in the format of a transaction and again the destination is fixed to SRC. This type of message is delivered to the source of the transaction and the transaction data is mapped to the terminal screen according to the terminal template definition.
Page 330: Vt Keyboard Mapping And Script Keystroke Names
DCS 300 User’s Manual VT Keyboard Mapping and Script Keystroke Names This table shows how VT keyboard keys map to the DCS 300 keyboard and to the script keystroke names. For a diagram of how the VT keyboard maps to the DCS 300 keyboard, see Chapter 7, “Running Terminal Emulation.”...
Page 331 VT Keyboard Map (continued) VT Keyboard F15/Help F16/Do 0 (keypad 0) 1 (keypad 1) 2 (keypad 2) 3 (keypad 3) 4 (keypad 4) Prev Scrn Next Scrn Select Remove Ctrl-[ 5 (keypad 5) 6 (keypad 6) 7 (keypad 7) 8 (keypad 8) 9 (keypad 9) .
Page 332: Keystrokes
DCS 300 User’s Manual Keystrokes A keystroke can be a mnemonic or a string. The table below lists the 3270 and 5250 keystroke mnemonics supported by the DCS 300. Attention Backspace Clear Cursor Down Cursor Left Cursor Right Cursor Up Delete Enter Erase EOF...
Page 333: Troubleshooting
Troubleshooting...
Page 334 DCS 300 System Manual blank...
Page 335: Troubleshooting Tips
Verify that the devices are configured properly and are attempting to communicate with the network. Verify that you have configured the RF card and started data collection. Make sure that all cables are securely plugged into their connections. Contact your local Intermec representative. 11-3...
Page 336: Software Problems (Dcs 300 Local Interface)
Solution Make sure that you have defined the correct configuration for the controller on the DCS 300. Make sure you are using the correct Intermec cable. Replace the cable. Replace the serial card. Make sure the configuration for the controller in the DCS 300 local interface matches the configuration in the controller.
Page 337: Dcbrowser Problems
“About the dcBrowser Diagnostics” later in this chapter and see the online help. Note: You can remotely access the DCS 300 if you have a network modem connected to your Ethernet network. For more information, contact your local Intermec representative. Symptom From the Web browser on your PC, you cannot connect to the DCS 300.
Page 338 DCS 300 User’s Manual dcBrowser Problems (continued) Symptom From your device, you cannot connect to the dcBrowser gateway. You see this error message, “A network error occurred. Unable to connect to server. The server may be down or unreachable.” After you reboot the DCS 300, the response time is slower than expected between the device and the Web server.
Page 339: Troubleshooting Tools
If you need to contact Intermec Product Support, use the Intermec Product Support Web page. For help, see “Using the Intermec Product Support Web Page” at the end of this chapter.
Page 340: Viewing The Configuration
DCS 300 User’s Manual Viewing the Configuration The DCS 300 produces a configuration file ( the parameters that you have defined for the runtime (active) configuration. You can also save this file to disk. To view the configuration 1. From the main screen sidebar buttons, choose System Reporting. The System Reporting dialog box appears.
Page 341: Viewing Error Messages
2. If the error message says to view the error log, open the error log. 3. Contact your network administrator to help you solve the problem. 4. Contact Intermec Product Support to help you solve the problem. For help, see “Using the Intermec Product Support Web Page” later in this chapter.
Page 342: Message Box Error Messages
DCS 300 User’s Manual Message Box Error Messages Message box error messages appear in message boxes on the DCS 300 screen. Most of these error messages provide immediate corrections to input in a field. For example: Choose OK and correct the problem. Your error message may tell you to view the error log.
Page 343 To view the runtime error log, use the DCS 300 status monitor. The status monitor displays the error messages as they are being written to the error log. The clock in the lower right corner of the dialog box lets you verify the exact time when the error message occurred.
Page 344 (10-9999). The default is 50 messages. When the number of error messages reaches this number, the oldest message is deleted. Note: Intermec recommends that you do not make this number too large since these error messages are stored in RAM.
Page 345: Viewing The Hot Standby Files
2. Click View Error Log. 3. If a security screen appears, type INTERMEC in the User Name field and in the Password field, and click OK. You must type Intermec in uppercase letters. 4. Choose OK. The DCS 300 Error Log page appears.
Page 346 DCS 300 User’s Manual To view a Hot Standby file 1. From the main screen sidebar buttons, choose System Reporting. The System Reporting dialog box appears. 2. In the System Reporting list box, select View Hot Standby Files and then choose Start.
Page 347: Using Remote Console
DCS 300 or you can order an upgrade license (Part No. 067188). The guest is a client program that you run on a remote PC. You must purchase one of these Intermec versions of the NetOp v5.3 PC Remote Control guest software: •...
Page 348 DCS 300 User’s Manual To configure the NetOp host for TCP/IP or dial-up SLIP 1. From the main screen, choose System Maintenance. The System Maintenance dialog box appears. 2. In the System Maintenance list box, select Remote Console Support and then choose Start.
Page 349 To configure the NetOp host for APPC 1. From the main screen, choose System Maintenance. The System Maintenance dialog box appears. 2. In the System Maintenance list box, select Remote Console Support and then choose Start. The Remote Console Configuration dialog box appears. Field Description Communication...
Page 350: Configuring Security
DCS 300 User’s Manual Configuring Security The NetOp host software includes security features to prevent unauthorized access to the DCS 300. You can also use the security options to limit the actions that the remote PC can perform. To configure security •...
Page 351 Field Description Receive files from This check box determines if the remote PC DCS 300 user can transfer files from the DCS 300 to the remote PC. Lock DCS 300 This check box determines if the remote PC keyboard and mouse user can lock the DCS 300 keyboard and mouse during a session.
Page 352: Configuring The Netop Guest (Remote Pc)
DCS 300 User’s Manual Configuring the NetOp Guest (Remote PC) For help installing the NetOp guest software, see the NetOp user’s guide that shipped with your guest software. Note: The guest communication settings must match the host communication settings; that is, they must match the communication settings on the DCS 300. Using NetOp Guest for Windows After you install the NetOp guest software on your remote PC, follow these tips to ensure that a connection is made.
Page 353 5. Make sure that the modem that is connected to the DCS 300 is configured. 6. After the modem connection is made, start the NetOp guest software. 7. Call the TCP/IP host using the name 222.222.222.10. Tips for using dial-up SLIP in Windows NT/2000 1.
Page 354: Using The Trace Utilities
DCS 300 User’s Manual Tips for using dial-up SLIP 1. Use the Network Dialer tool to make a SLIP connection to the DCS 300. 2. In the Login Info tab, choose SLIP as the connection type. 3. In the Connect Info tab, type 222.222.222.20 as the destination IP address. 4.
Page 355 Trace Configuration Dialog Box 3. Add all the trace components to the Configured Traces list box. For help, see “Adding a Network Trace,” “Adding a System Trace,” and “Adding a Screen Mapping Trace” in the next sections. Adding a Network Trace Network traces can be useful when troubleshooting IP traffic on the Ethernet or token ring network.
Page 356 DCS 300 User’s Manual Adding a System Trace System traces are useful in tracing transactions and SNA traffic on the system. While you are running a system trace, you can watch the traces in the Monitor Message Handler Transactions dialog box. For help, see “Running System Traces” later in this chapter.
Page 357 Adding a Screen Mapping Trace Screen mapping traces are useful when troubleshooting the script files. You must configure a screen mapping session before you can configure a screen mapping trace. For help, see “Setting Up Screen Mapping Sessions” in Chapter 10. While you are running screen mapping traces, you can also choose to watch the traces in a separate window.
Page 358: Exiting The Dcs 300 Trace Utility
DCS 300 User’s Manual Exiting the DCS 300 Trace Utility 1. From the Trace Configuration dialog box, choose the File menu command. 2. Choose Close. You return to the System Diagnostics Tools dialog box. Running Network Traces Use these procedures to start and stop the network traces. IP traces are named IPTRACE.TXT To start the DCS 300 trace utility 1.
Page 359: Running System Traces
Running System Traces Use these procedures to start and stop the system traces. For help running the TTM utility, see the online help. On the DCS 300, the transaction trace file is named to 10,000 transactions in the order that the DCS 300 received the transactions. The SNA trace file is called SNATRACE.TXT When you start a system trace, the Monitor Message Handler Transactions dialog box...
Page 360 DCS 300 User’s Manual Monitor Message Handler Transactions Dialog Box To pause the trace • Choose Pause. To restart the trace after a pause • Choose Start. To save the system trace • Choose Save. The results are stored in the To clear all the traces in MH_IN, MH_ACK, and Output boxes •...
Page 361: Running Screen Mapping Traces
Running Screen Mapping Traces Use these procedures to start and stop the screen mapping traces. The screen mapping trace is named script.SM, where script is the name of the script file that you are tracing. To start the DCS 300 trace utility 1.
Page 362: Managing The Traces
DCS 300 User’s Manual To stop the Trace utility • In the Trace Control box, choose Stop. The Elapsed Time clock stops. Managing the Traces The current trace session contains all the traces that were created when you started and then stopped the DCS 300 trace utility.
Page 363 3. In the Trace Session/Files list box, double-click on a trace session with a plus (+) on the left side to expand it to show a list of the traces you can view. Or, double-click on a line with a minus (-) on the left side to collapse the list. 4.
Page 364: Saving The Traces
DCS 300 User’s Manual Saving the Traces Each time that you start a new trace, the Trace utility discards the previous trace session’s files. If you want to save a trace session, you give the current session a new name and all the traces are saved in the directory.
Page 365: Deleting The Traces
3. In the Available Sessions list box, add all the trace sessions that you want to back up to the Sessions to Back Up list box. a. Select the session name. b. Choose Select. The session name appears in the Sessions to Back Up list box. 4.
Page 366 DCS 300 User’s Manual To delete selected trace sessions 1. From the Trace Configuration dialog box, choose the File menu command. 2. Choose Selective Delete. The Selective Delete dialog box appears. 3. In the Available Sessions list box, add all the trace sessions that you want to delete to the Sessions to Delete list box.
Page 367: Using The Os/2 Troubleshooting Tools
Using the OS/2 Troubleshooting Tools The DCS 300 local interface provides you with access to the OS/2 message log and the subsystem management tool. For detailed help using these troubleshooting tools, see the online help that is provided by IBM PComm. Viewing the Message Log You can use the message log formatter to view the OS/2 message log, This log may contain messages that the DCS 300 generates.
Page 368: Using The Subsystem Management
You can use these monitoring aids to troubleshoot your application and your data collection network. Each diagnostic reflects the current state of the process. Most of them are only meaningful if you have the help of Intermec Product Support. 11-36...
Page 369 To access the diagnostics screen 1. From the DCS 300 home page, click Diagnostics. The DCS 300 Diagnostic Tools page appears. 2. Click View dcBrowser Diagnostics. The dcBrowser Diagnostics page appears. This table explains the columns that appear when you access the dcBrowser diagnostics.
Page 370 DCS 300 User’s Manual This table provides a short description of the dcBrowser diagnostics that are available. For more detailed explanations of each diagnostic, see the online help. Diagnostic Name Connections Counters Cursors Description Cache Descriptions Diagnostics Events Get URLs Hash Access Hash Config Hash Sizing...
Page 371: Using The Intermec Product Support Web Page
• Telephone number that lets you contact Product Support if you are a U.S. customer. If you are an international customer, contact your local Intermec representative or you can use the Intermec Web page at www.intermec.com. • E-mail address and fax number that let you ask Product Support a specific question using a new case form.
Page 372 blank...
Page 373: Specifications And Other Helpful Information
Specifications and Other Helpful Information...
Page 374 DCS 300 System Manual blank...
Page 375: Specifications
Specifications and Other Helpful Information This appendix provides helpful information for using the DCS 300 to verify your network connections, to transfer files, and to configure the Trakker Antares terminals. Specifications Physical Specifications Length: 45.72 cm (18.0 in.) Height: 8.84 cm (3.48 in.) Width: 43.18 cm (17.0 in.) Weight: 13.5 kg (29.8 lb) Electrical Specifications...
Page 376: Converting Ethernet Addresses To Token Ring Mac Format
DCS 300 User’s Manual Converting Ethernet Addresses to Token Ring MAC Format When configuring the AS/400 host on the DCS 300, the LAN adapter address you specify depends on whether the DCS 300 and the host are on the same type of network. If the DCS 300 and AS/400 are on different types of networks, you must “byte-flip”...
Page 377 Specifications and Other Helpful Information As a shortcut, you can use this table to byte-flip addresses. The table shows what each hexadecimal digit, from 0 to F, becomes when you perform Steps 1 to 3 (from the previous figure). Then you must perform Step 4. Byte Flipped Hexadecimal Equivalents converts to converts to...
Page 378: Using The Dcs 300 To Verify Your Network Connections
DCS 300 User’s Manual Using the DCS 300 to Verify Your Network Connections You can use the DCS 300 to verify it is correctly connected to the downline devices and to your host. You need to start data collection before you can use the DCS 300 to send or receive transactions.
Page 379 Field Description Source ID This field can contain the name that you want (Optional) to use as the source of the transaction. Destination ID This field can contain the name of the device (Optional) that you want to use as the destination of the transaction.
Page 380: Receiving Transactions
DCS 300 User’s Manual Receiving Transactions Once you have configured the DCS 300, you may want to test your configuration by sending transactions from a device to an application without starting the application on the host. Or, you may want to send transactions to a device. The receive transactions feature can troubleshoot your connection to a destination.
Page 381 Specifications and Other Helpful Information 5. In the Application name field, enter the name of a destination. The destination name (application or device) must be defined in the DCS 300. 6. Choose Add. The Receive Transactions dialog box appears and the DCS 300 begins emulating and monitoring incoming transactions for the destination.
Page 382: Using The Dcs 300 To Transfer Files
DCS 300 User’s Manual Using the DCS 300 to Transfer Files You can use the DCS 300 to send binary files, such as the reader program, to JANUS devices and Trakker Antares terminals. You can also send ASCII files, such as IRL files, templates, and validation files, to one or more devices in any network.
Page 383: Limitations When Downloading Irl Programs
Specifications and Other Helpful Information Limitations When Downloading IRL Programs Problem When you download an IRL program from the DCS 300, the mnemonic representation of ASCII control characters (0-31) is converted into actual characters. Usually, you use these characters to create bar code printer labels or to create data that is based on the IRL program execution.
Page 384: Adding A Group In The Download Server
DCS 300 User’s Manual Adding a Group in the Download Server If you want to send files and data to more than one device at the same time, create a group in the download server. You can also edit or delete a group. To add a group 1.
Page 385: Copying Information Between Terminals Or Groups
Specifications and Other Helpful Information 4. In the Group name field, enter a meaningful name for the group of terminals. 5. Add the terminals that you want in this group to the Selected Terminals list box. a. From the Available Terminals list box, select a terminal to add. b.
Page 386: Using The Download Server To Transfer Files
DCS 300 User’s Manual Using the Download Server to Transfer Files Note: The 9154 controller does not support binary file transfer 1. From the Terminal Download Configuration dialog box in the Terminals and Groups list box, select a terminal or group to receive files or data. 2.
Page 387: Using Download Server Commands To Transfer Files
Specifications and Other Helpful Information 4. Enter the file name or data in the field in the Initialization Data box. 5. Choose Add. The file name or data appears in the Files and Data list box. 6. Repeat Steps 3 through 5 until you have entered all the files and data you want to download for this terminal or group.
Page 388 DCS 300 User’s Manual This table lists examples of commands you can use and the results of using the commands. This table assumes that all requests come from a device that has the address pA. Command DEV=pA G=group F=filename D=data E=errormessage You can use one line to send multiple download server commands by stringing the commands together with a comma and no spaces.
Page 389: Using The Dcs 300 To Configure Trakker Antares Terminals
Using the DCS 300 to Configure Trakker Antares Terminals You can use the DCS 300 to configure one or more Trakker Antares terminals by sending configuration commands using the download server. Note: You cannot retrieve configuration data from a terminal. For example, you may want to set the Beep Volume to very loud and turn on Keypad Caps Lock for all the terminals in one area.
Page 390 DCS 300 User’s Manual Configure Device Initialization Download Dialog Box 3. In the Initialization Data box, choose Command. 4. Enter the configuration command and choose Add. The command appears in the Files and Data box. For example, to set the Beep Volume to very loud, type 5.
Page 391: Upgrading The Dcs 300 And Devices
Upgrading the DCS 300 and Devices...
Page 392 DCS 300 System Manual blank...
Page 393: Upgrading The Dcs 300 Software
This appendix provides you with instructions on how to upgrade the DCS 300. It also explains how to use the DCS 300 to upgrade the Trakker Antares terminals. Upgrading the DCS 300 Software You can use the DCS 300 local interface or you can use the Web browser interface to upgrade the DCS 300 software.
Page 394 Major upgrades must be run from the CD. 3. From the DCS 300 home page, click Management. 4. If a security screen appears, type INTERMEC in the User Name field and in the Password field, and click OK. You must type Intermec in uppercase letters.
Page 395: Upgrading To Screen Mapping
Upgrading to Screen Mapping You can purchase screen mapping (Intermec Part No. 067190). Intermec has designed an automated Script Builder Tool that lets you create script files for your JANUS devices, Trakker Antares terminals, and the 6400. To install the license 1.
Page 396: Using The Dcs 300 To Upgrade Trakker Antares Terminals
DCS 300 User’s Manual Using the DCS 300 to Upgrade Trakker Antares Terminals The Firmware Upgrade Utility lets you simultaneously upgrade the firmware on all the Trakker Antares terminals that the DCS 300 can communicate with. It detects which firmware each terminal is running and performs the correct upgrade procedure for that version.
Page 397 In the Scheduled Firmware Upgrades box, you can view the state of all the scheduled upgrade events. Column Description The date on which the upgrade event is scheduled to occur. The time at which the upgrade event is scheduled to occur.
Page 398: Adding Upgrade Events
3. In the Firmware version field, click the down arrow on the right side of the field. A list of firmware versions that you can download appears. Choose one. Or, load the firmware from a disk that was supplied to you by your local Intermec representative or a VAR. For help, see “Loading Firmware and Applications From a Disk”...
Page 399 4. In the Application field, click the down arrow on the right side of the field. A list of applications that you can download appears. Choose one. Or, load the application from a disk that was supplied to you by your local Intermec representative or a VAR. For help, see “Loading Firmware and Applications From a Disk”...
Page 400 DCS 300 User’s Manual 9. In the Device time-out field, enter the number of minutes that the utility waits for the upgrade to complete on each device before it times out. If the upgrade on one of the devices does not finish before the time-out, an Error status appears next to the upgrade event name in the Firmware Upgrade utility window.
Page 401: Loading Firmware And Applications From A Disk
Loading Firmware and Applications From a Disk If you are ready to start scheduling upgrade events and you have received new firmware or an application from Intermec or a VAR, you can load it on your DCS 300. Then you can continue scheduling an upgrade event.
Page 402 DCS 300 User’s Manual Load Firmware File Set Dialog Box 5. In the Firmware comment field, enter any comments you want to be stored with the firmware or application. These comments appear in the Firmware File Set Details message box. You can enter up to 40 alphanumeric characters, special characters, or spaces.
Page 403: Defining A Group
Defining a Group You can define groups so that you can more easily manage upgrading your devices. For example, you may want to upgrade the firmware on the dayshift terminals at night and upgrade the nightshift terminals during the day. You can assign a device to more than one group.
Page 404: Renaming A Group
DCS 300 User’s Manual 6. Add devices to each group. In the Groups list box, a plus (+) on the left side of the group name shows that the group is not expanded to show all the devices that are in it.
Page 405: Performing The Upgrade
Performing the Upgrade Note: Before an upgrade event can happen, you must start data collection on the DCS 300. To perform the upgrade 1. In the third Add a New Upgrade Event to be Scheduled dialog box, check the Immediately check box. When you choose Finish, the utility starts upgrading the terminals.
Page 406: Managing System Firmware And Applications
DCS 300 User’s Manual Managing System Firmware and Applications Once you have loaded firmware and applications onto your DCS 300, you can view the firmware and applications from the Firmware Files Set dialog box. For help loading firmware and applications, see “Loading Firmware and Applications From a Disk” earlier in this appendix.
Page 407 To view details of a firmware file or application • From the Firmware File Sets dialog box, select a system file (firmware) or an application and then choose Details. This message box appears: Choose Close to close the message box and return to the Firmware File Sets message box.
Page 408: Viewing Upgrade Event Details
DCS 300 User’s Manual Viewing Upgrade Event Details The Firmware Upgrade Utility window displays the scheduled upgrade events and their current status. You can view more details of an upgrade event and see the status of each device that is scheduled to be upgraded. Stop Upgrade button If the status of an upgrade on a terminal is Upgrading, you can stop the server thread that is handling/monitoring the upgrade.
Page 409: Viewing The Event Log
Viewing the Event Log The event log contains the history of all upgrade events. The log is sorted by date and time, with the most recent event listed first. To view the event log 1. From the Firmware Upgrade Utility window, choose View Log. The Upgrade Log dialog box appears.
Page 410 DCS 300 User’s Manual a. In the File name field, enter a meaningful file name for the event log. b. If you want to save the file to a floppy disk, check the Save to Removable Floppy check box. If you want to save the file to the hard drive, clear the Save to Removable Floppy check box.
Page 411 How the DCS 300 Routes Transactions...
Page 412 DCS 300 System Manual blank...
Page 413: How The Dcs 300 Routes Transactions
This chapter helps you learn about the features of the DCS 300 and how the DCS 300 works with your LAN and Intermec’s data collection network. How the DCS 300 Works The DCS 300 is composed of several software components working together to perform routing functions.
Page 414 DCS 300 User’s Manual NetComms provide network transparency. For example, the DCS 300 writes a transaction into an input channel for an application. A local send NetComm reads the transaction from the input channel and sends it to a remote application. The remote application processes the transaction and acknowledges the receipt of the transaction from the local send NetComm.
Page 415: About Transactions
About Transactions Communications from an application through the DCS 300 to devices and other applications involve two types of transactions: data transactions and system transactions. Data Transactions The message handler uses the transaction ID to determine the destinations for a transaction;...
Page 416: How The Dcs 300 Routes Transactions
DCS 300 User’s Manual How the DCS 300 Routes Transactions Transactions have a well-defined structure consisting of a header and data. The header contains a transaction ID, which the DCS 300 uses to determine the destination for a transaction. The transaction ID is the primary routing mechanism used by the DCS 300. When the DCS 300 receives a transaction, it checks the system message flag.
Page 417 In this example, the application sends a transaction to a specific destination using the destination name in the transaction header. The numbers on the following paragraphs correspond to the numbers on the illustration on the next page. The remote application (APP3) writes the transaction to the local receive NetComm through the network connection.
Page 418 DCS 300 User’s Manual Routing Transactions From Applications Local area network Device 1 (DCU) Access point Network connection Receive DevComm NetComm Receive Message handler DCS 300 Device 1 Device 2 Remote application (APP3) Network connection Send NetComm APP3 0300U005.eps...
Page 419: Routing Transactions From Devices
Routing Transactions From Devices This example discusses the steps to move data from the device to the application. The numbers on the following paragraphs correspond to the numbers on the illustration on the next page. Data is entered at Device 1 and transmitted through the access point to the DCS 300. A DevComm receives the transaction through its hardware link.
Page 420 DCS 300 User’s Manual Routing Transactions From Devices Access point Local area network C-10 Device 1 DCS 300 Message handler ACK (DCA) Receive Receive DevComm NetComm Network connection Standby (APP3) APP3 Send NetComm Network connection 0300U006.eps Remote application (APP3)
Page 421 Note: Steps 5 through 8 and 12 occur for each application that receives a transaction sent by the message handler. Steps 9, 10, and 11 are different for TCP/IP and APPC applications. The message handler determines the correct destination for the transaction. It then checks a flag for the destination to see if it is currently an active or an inactive application: •...
Page 422 DCS 300 User’s Manual Routing Transactions From Devices (continued) Access point Local area network C-12 Device1 DCS 300 Message handler ACK (DCA) Receive Receive DevComm NetComm Network connection Remote Application (APP3) Standby (APP3) APP3 Send NetComm Network connection 0300U007.eps...
Page 423: How The Dcs 300 Acknowledges Transactions
How the DCS 300 Acknowledges Transactions After the DCS 300 attempts to deliver a transaction from an application to a data collection device, it can send a delivery response (success or failure) to the originating application. If you configure the DCS 300 to send a delivery response, it returns a successful message indicating the transaction was accepted by the device or it returns a failure message if the transaction was not stored in the Hot Standby file.
Page 424: Fully Interactive System
DCS 300 User’s Manual Fully Interactive System A fully interactive system provides the safest way to move information from a device to an application because the application always sends an acknowledgment to the device. As long as the device can retransmit the transaction if communication fails, data is not lost.
Page 425: Data Integrity Modes
How the DCS 300 Routes Transactions Data Integrity Modes The DCS 300 operates in one of two data integrity modes for external Intermec controllers: Faster and Safer. You define the data integrity mode for each external controller that the DCS 300 uses to communicate with devices (such as terminals, readers, and printers).
Page 426: Retaining Transactions In Memory
DCS 300 User’s Manual Retaining Transactions in Memory is an auxiliary queue in volatile memory. By default, the DCS 300 uses this AUX_Q queue as a temporary holding place for transactions that are waiting to be sent to a destination while the DCS 300 is waiting for an ACK from that destination. is used only in this situation: AUX_Q •...
Page 427: How The Dcs 300 Sets Application Status
How the DCS 300 Routes Transactions How the DCS 300 Sets Application Status When the DCS 300 is initialized or first starts up, all application channels listed in the configuration file are assumed to be nonactive or batch destinations. This means that until otherwise notified, the message handler automatically routes transactions for these applications to Hot Standby files.
Page 428: Nonactive Applications
DCS 300 User’s Manual Note: If an application sends a Inter system transaction instead of an acknowledgment to the message handler, the message handler retransmits the last transaction it sent to that application. Nonactive Applications A nonactive application has failed to complete the handshake with the DCS 300 for a transaction.
Page 429: Changing From Nonactive To Active Status
For example, you can define a transaction ID ( destinations (selftest, writeit, and batchit) and has the Hot Standby message, “Data saved on disk.” When the DCS 300 receives the message handler sends a copy of the transaction to each of the defined destinations and starts a Hot Standby timer for each one.
Page 430 blank...
Page 431: Index
Index...
Page 432 DCS 300 System Manual blank...
Page 433 Symbols and Numbers #ACCNET mode, 7-16, 8-5 #INTER mode, 7-16 $IPT transaction ID, 8-17, 8-20 2.4 GHz RF network, See also UDP Plus network 3270 NAU Pool dialog box, 7-22 New NAU field, 7-22 Unlinked NAUs pool, 7-22 3270 screen mapping, Data response timeout field, 10-24 3270 SNA field, 4-12, 4-23, 4-34 3270 SNA terminal emulation feature, 1-4...
Page 434 DCS 300 User’s Manual Add Screen Mapping Trace dialog box (continued) Trace check box, 11-25 Add System Trace dialog box SNA box, 11-24 Transactions box, 11-24 Add/Edit a Terminal Group dialog box, A-12 Available Terminals list box, A-13 Group name field, A-13 Selected Terminals list box, A-13 adding 3270 terminal session, 9-17...
Page 435 Available Screens list box, 10-54 Available Terminals list box, A-13 Available Transactions list box, 10-20 Back Up button, 2-17, 2-18 Back Up System Files message box Back Up button, 2-17 illustrated, 2-17 Back Up User Files dialog box Back Up button, 2-18 opening, 2-18 root directory list box, 2-18, 11-33, 11-34 Selected Files list box, 2-18, 11-33, 11-34...
Page 436 DCS 300 User’s Manual Configure Controller RF Card dialog box, 4-8 Acknowledgment delay field, 4-8 BRU Status check box, 4-9 Card number field, 4-8 Channel - Frequency field, 4-9 Hot Standby Timeout box, 4-9 Network ID field, 4-8 Repeat count field, 4-9 Retry count field, 4-9 RFNC address field, 4-8 Transactions held in volatile memory field, 4-9...
Page 437 dcBrowser (continued) environments, explained, 6-6 equipment needed, 6-7 running, 6-8 running HTML application, 6-12 starting the gateway, 6-8 understanding, 6-5 DcmRsmTran system transaction, C-17 DCS 300 acknowledging transactions, C-13 architecture, C-3 communicating with TCP/IP applications, 8-12 connecting to Ethernet, 3-4 connecting to SDLC, 3-18 connecting to the 2.4 GHz RF network, 4-17 connecting to the 900 MHz RF network, 4-4...
Page 438 DCS 300 User’s Manual Device Parameters dialog box (continued) Hot standby field, 4-16, 4-28, 4-39 Interactive response field, 4-16, 4-28, 4-39 Logical name field, 4-16, 4-28, 4-38 To be routed to device field, 4-16, 4-28, 4-38 Device time-out field, B-10 Device type field, 4-16, 4-28, 4-38 DHCP server, using to provide TCP/IP configurations, 3-5, 3-12...
Page 439 Firmware File Sets dialog box, B-16 Delete button, B-17 Details button, B-17 Load Firmware button, B-16 Firmware Upgrade Utility, B-6 Add a New Upgrade Event to be Scheduled dialog box, B-8 adding upgrade events, B-8 defining a group, B-13 deleting applications, B-17 deleting firmware, B-17 Details button, B-18 Firmware button, B-6, B-16...
Page 440 Inter system transaction, 8-12 interactive applications, 8-22 Interactive response field, 4-16, 4-28, 4-39, 8-8 interactivity full, C-14 noninteractive, C-14 partial, C-14 with devices, C-13 Intermec controllers, data integrity modes, C-15 Intermec product support, contacting, 11-39 Internal clock check box, 3-20...
Page 441 international characters displaying on JANUS devices, 7-36 displaying on Trakker Antares terminals, 7-37 displaying on WTP devices, 7-37 international text pass-through, 8-8 International text pass-through check box, 8-8 Internet interface, See Web interface Interprocess Communication channels ACK channel, C-3 Receive channel, C-3 Interval field, 4-11, 4-22 IP, 8-11 IP address...
Page 442 DCS 300 User’s Manual local interface instructions, configuring (continued) Ethernet card, 3-5 Ethernet card for IEEE 802.2, 3-9 for 3270 SNA, 7-19 for 5250 SNA TE, 7-12 for DNS, 3-8 host IP address manually, 7-9, 7-27, 9-10 IP host, 7-7, 7-25 NetOp host for APPC, 11-17 NetOp host for TCP/IP or dial up SLIP, 11-16 remote control security, 11-18...
Page 443 local interface instructions (continued) using download server to configure a terminal, A-17 download server to transfer files, A-14 message log formatter, 11-35 subsystem management, 11-36 verifying connection, A-6 logic of a script file, 10-61, 10-62, 10-63, 10-64 that security is set, 7-34 viewing configuration, 11-8 details of a firmware file or application, B-17...
Page 444 DCS 300 User’s Manual Name field, 10-49, 10-67, 10-69 Name Server Addresses box, 3-8, 3-15 Native field, 4-34 Native option button, 7-10, 7-28 NAU address field, 9-17 NAU pool, filling, 7-22 navigation menu, Web interface, 2-9 NetACK, 8-14 NetComms, 8-11, C-3 comparing to the direct TCP/IP socket interface, 8-19 figure, 8-13 linking to APPC application, 8-23...
Page 445 Port Configuration dialog box, 7-27 Native option button, 7-10, 7-28 Port name field, 7-10, 7-27 Port number field, 7-10, 7-27 Send ID check box, 7-10, 7-28 Telnet option button, 7-10, 7-28 Port name field, 7-10, 7-27 port number, 8-12 Port number field, 7-10, 7-27, 9-8 Postamble field, 4-11 power cord part numbers, 1-8...
Page 446 DCS 300 User’s Manual RF card, 4-4 Communication Parameters box, 4-6 configuring, 4-6 defining the devices, 4-13 RF Card Default Host Links dialog box, 4-12 3270 SNA field, 4-12 5250 SNA field, 4-12 Telnet (all) field, 4-12 RF Card Devices dialog box, 4-13 Base logical name field, 4-13 Number of devices to enable field, 4-13 RF devices...
Page 447 Screen Mapping Session Definition dialog box (continued) Name field, 10-67 Script File box, 10-67 Selected list box, 10-67 Start session at data collection start check box, 10-67 Visible when data collection started? check box, 10-67 Screen Mapping Session List dialog box, 10-65 screen mapping sessions, adding, 10-66 screen mapping trace, 11-25 Screen Mapping Transaction IDs dialog box, 10-31...
Page 448 DCS 300 User’s Manual Session name field, 9-8, 9-13, 9-17 setting script runtime options, 10-22 security for the TE Configuration menu, 7-31 system parameters, 2-14 time parameters, 4-10, 4-21 setting up 5250 SNA terminal emulation, 7-12 peer-to-peer links, 8-6 screen mapping session, 10-65 terminal sessions, 9-4 UDP Plus devices, 4-24 VT terminals, 9-10...
Page 449 TCP/IP address family, 8-12 configuring routing tables, 3-22 configuring the network adapter card, 3-5 configuring the token ring card, 3-11 enabling routing daemon, 3-21 network address, 8-12 port number, 8-12 using a routing daemon, 3-12 using routing tables, 3-12 TCP/IP adapter field, 3-6 TCP/IP applications communicating with, 8-11, 8-12 IP address, 8-5...
Page 450 DCS 300 User’s Manual token ring (continued) configuring network adapter card for TCP/IP, 3-11 configuring routing tables, 3-22 converting IP addresses, A-4 enabling routing daemon, 3-21 installing the DCS 300, 3-11 manually configuring TCP/IP, 3-12 using a routing daemon, 3-12 using DHCP for TCP/IP configurations, 3-12 toolbar buttons, 2-5 Trace check box, 11-25...
Page 451 UDP Plus network adding, 4-19 configuring, 4-18 figure, 4-17 setting up devices, 4-24 UDP Plus Network Parameters dialog box, 4-19 Hot Standby Timeout box, 4-20 Inactivity timer field, 4-20 Local field, 4-20 Lower limit field, 4-20 Network field, 4-20 Retries field, 4-20 Transactions held in volatile memory field, 4-20 Upper limit field, 4-20 understanding the Script Builder tool, 10-14...
Page 452 DCS 300 User’s Manual VT Setup dialog box (continued) Save as new defaults check box, 9-11 User-Defined Key option buttons, 9-11 VT terminals mapping keyboard to DCS 300 keyboard, 9-23 setting up, 9-10 VT/ANSI screen mapping, Data response timeout field, 10-24 VT/ANSI terminal emulation, 1-4 See also terminal emulation Wait for response check box, 10-48...