User s Manual. DCM for HP-UX. Version 4.3 P/N

Transcription

1 User s Manual DCM for HP-UX Version 4.3 P/N

2 Intermec Corporation th Avenue West P.O. Box 4280 Everett, WA U.S. technical and service support: U.S. media supplies ordering information: Canadian technical and service support: Canadian media supplies ordering information: Outside U.S. and Canada: Contact your local Intermec service supplier. The information contained herein is proprietary and is provided solely for the purpose of allowing customers to operate and/or service Intermec manufactured equipment and is not to be released, reproduced, or used for any other purpose without written permission of Intermec. Information and specifications in this manual are subject to change without notice by Intermec Corporation All Rights Reserved The word Intermec, the Intermec logo, JANUS, IRL, DURATHERM, and CrossBar are trademarks of Intermec Corporation. Throughout this manual, trademarked names may be used. Rather than put a trademark ( ) symbol in every occurrence of a trademarked name, we state that we are using the names only in an editorial fashion, and to the benefit of the trademark owner, with no intention of infringement.

3 Contributors Author Editor Technical Illustrators Dean Meinert Craig Thompson John Bickley Dean Meinert

4 Manual Change Record This page records the changes to this manual. The manual was originally released as Rev Revision Date Description of Change /94 This manual has been revised to incorporate new features added to the DCM for HP-UX software. Corrections to Rev. 001 have also been incorporated into the manual /95 This manual has been revised to incorporate the new features added to the DCM for HP-UX software for version 4.3. Corrections to Rev. 002 have also been incorporated into the manual.

5 Contents Contents Before You Begin xiii Warranty Information xiii Notes xiii About This Manual xiii Conventions xv Suggested Reading xvi 1 Learning About DCM What Is DCM? 1-3 Features 1-3 Communications 1-4 User Flexibility 1-4 Documented With Manuals and Online Help 1-5 How to Use DCM 1-5 Installing and Configuring Intermec Hardware 1-5 Installing and Configuring DCM 1-6 Starting DCM 1-6 Verifying Installation 1-6 Preparing Applications Installing DCM Upgrade Information 2-3 Tasks for the UNIX System Administrator 2-4 Creating a DCM User Account 2-4 Copying the Tape 2-5 Modifying /etc/services 2-6 Adding Display Station Names to /etc/hosts 2-8 Updating the Network Information Service 2-8 v

6 DCM for HP-UX User's Manual Setting Up Serial Ports 2-9 Local RS-232 Ports 2-10 Setting Up for Terminal Emulation 2-11 Tasks for the DCM User 2-12 Modifying Shell Scripts and User Login Files 2-12 Korn Shell Setup 2-13 C Shell Setup 2-14 Setting Up.vueprofile 2-15 Setting DISPLAY 2-17 Giving DCM Access to Oracle Databases 2-18 Sample Oracle Environment Variable Settings 2-19 Installing a DCM License 2-22 License-Related Event Messages Configuring a DCM System Starting Conman 3-3 Using Configuration Files 3-4 Exiting Conman 3-6 Setting Up Downline Devices 3-7 Editing a Device 3-11 Editing Station Parameters 3-13 Changing the Colors of the Station Map 3-15 Viewing a List of Stations 3-15 Deleting a Device 3-17 Configuring Interface Types 3-17 File Interface 3-17 Editing a File Interface 3-19 Deleting a File Interface 3-19 Database Interface 3-20 Editing a Database Interface 3-22 Deleting a Database Interface 3-23 vi

7 Contents Application Interface 3-23 Changing an Application Interface Name 3-24 Deleting an Application Interface 3-24 Terminal Emulation Interface 3-24 Editing a Terminal Emulation Interface 3-26 Deleting a Terminal Emulation Interface 3-26 Configuring Destinations 3-27 Editing a Destination 3-30 Deleting a Destination 3-30 Configuring a Receive Server Destination 3-30 Configuring Network Connections 3-32 Editing a Network Connection 3-35 Deleting a Network Connection 3-35 Specifying Network Connection Preferences 3-35 Configuring a Transaction ID 3-36 Specifying the System Delimiter 3-37 Adding a Transaction ID 3-39 Defining and Editing Transaction Fields 3-40 Deleting a Transaction Field 3-42 Validating Transaction Fields 3-42 Selecting a Destination for a Transaction ID 3-45 Configuring Database Operations 3-46 Configuring Database Reads 3-46 Setting Up an Output Transaction ID 3-47 Setting Up an Input Transaction ID 3-47 Selecting the Output Transaction ID and Specifying the Database Tables You Want to Read 3-48 Defining Field Mappings for the Read Results 3-51 Editing Output Transaction ID Field Mappings 3-53 Deleting Output Transaction Field Mappings 3-53 Specifying Output Information 3-53 Setting Up Read Conditions 3-56 Configuring Database Inserts (Writes) 3-57 Editing Input Transaction ID Field Mappings 3-59 vii

8 DCM for HP-UX User's Manual Deleting Input Transaction ID Field Mappings 3-60 Configuring Database Updates 3-60 Editing Input Transaction ID Field Mappings 3-63 Deleting Input Transaction ID Field Mappings 3-63 Setting Up Conditions for the Update Operation 3-64 Configuring Database Deletes 3-64 Setting Up Conditions for a Delete Operation 3-66 Defining Conditions for a Database Operation 3-66 Editing a Database Condition 3-70 Deleting a Database Condition 3-70 Configuring Database Server Handshaking 3-70 Configuring System Parameters 3-73 Configuring DCM for Terminal Emulation 3-75 TE Transaction Routing Process 3-77 Using Sample Configuration Files to Set Up TE 3-78 Creating Your Own Configuration File to Set Up TE 3-79 Setting Up an IRL Device for Terminal Emulation 3-82 Setting Up a JANUS Device for Terminal Emulation 3-83 Configuring a JANUS Device for Terminal Emulation 3-84 Starting a TE Session on a JANUS Device 3-88 Ending a TE Session on a JANUS Device Managing DCM Status Watch 4-3 Using a Configuration File to Run DCM 4-4 Starting DCM 4-5 Starting DCM From Conman 4-5 Starting DCM From the Command Line 4-7 Examples 4-7 Controlling DCM System Parameters 4-8 viii

9 Contents Recovering Audit File Data 4-10 IPC Channel Watch 4-13 Stopping DCM 4-14 Using Conman to Shut Down DCM 4-14 Stopping DCM From the Command Line Troubleshooting DCM Contacting Intermec Technical Services 5-3 Error Message Format 5-4 Error Subsystem Environment Variables 5-5 Understanding SQL Errors 5-6 Remote Oracle System 5-6 Understanding DCM Error and Event Messages 5-7 A System Considerations Runtime Files A-3 Environment Variables A-3 Killing Conman A-9 Updating the /etc/services File A-9 JANUS Mode Terminal Emulation Support A-12 VT220/320 Terminals A-13 Keyboard Mapping A-13 Numeric Keypad Mapping A-14 Arrow Keys A-15 Cursor Control Commands A-15 Screen Editing Commands A-16 ix

10 DCM for HP-UX User's Manual Visual Character Attributes A-16 Setting and Selecting Character Set Commands A-17 Mapping Character Set Commands A-17 Operating Level Commands A-18 Mode Commands A-18 Reporting Commands A-19 Miscellaneous Commands A-20 8-Bit Code Extension A-20 Character Sets A-21 VT100 Terminal A-21 Numeric Keypad Mapping A-21 Arrow Keys A-22 Cursor Movement Commands A-22 Screen Erasing Commands A-23 Tab Stop Commands A-23 Character Set (G0 and G1 Designators) Commands A-23 Mode Commands A-23 Report Commands A-24 Miscellaneous Commands A-24 Character Sets A-24 ANSI Terminal A-25 Arrow Keys A-25 Cursor Control Commands A-25 Screen Editing Commands A-26 Screen Control Commands A-27 Tab Stop Commands A-27 Character Attribute Commands A-28 Mode Commands A-28 Report Commands A-28 Character Set A-28 x

11 Contents B Example Applications TCP/IP Applications B-3 Local Applications B-4 I Index xi

12

13 Before You Begin Before You Begin This section introduces you to standard warranty provisions, safety precautions, warnings and cautions, document formatting conventions, and sources of additional product information. Warranty Information To receive a copy of the standard warranty provision for this product, contact your local Intermec sales organization. In the U.S. call (800) , and in Canada call (800) Otherwise, refer to the Worldwide Sales & Service list that was shipped with this manual for the address and telephone number of your Intermec sales organization. Notes Notes are statements that either provide extra information about a topic or contain special instructions for handling a particular condition or set of circumstances. About This Manual The DCM for HP-UX User s Manual provides information on installing, configuring, and operating Data Collection Manager (DCM) for the HP-UX operating system. Depending on your familiarity with DCM and on how you want to configure its operation, you may find that you use some parts of this manual more often than others. This manual has been written to make DCM as easy to use as possible; however, some chapters may require an understanding of the UNIX operating system and TCP/IP communications protocols. xiii

14 DCM for HP-UX User s Manual This manual is divided into several chapters describing different components of DCM. A list of topics and where to find the information are given in this table: Chapter Learning About DCM Installing DCM Configuring a DCM System Managing DCM Troubleshooting DCM System Considerations Example Programs Information Chapter 1 provides an overview of the DCM software. Chapter 2 lists the requirements for installing and running DCM on the HP-UX operating system. Chapter 3 gives you step-by-step instructions on using the Configuration and Control Manager (Conman) interface to work with configuration files, and to add, edit, and delete devices, interface items, destinations, and transactions in your DCM-based data collection system. Chapter 4 describes how to start, stop, and audit DCM and explains the status and channel watch functions. Chapter 5 lists error messages and possible solutions for problems that may occur when running DCM. Appendix A lists a variety of system information, including DCM runtime files, UNIX environment variable settings, and killing DCM processes from the command line. Appendix B provides information on the various example programs that are included with the DCM software. xiv

15 Before You Begin Conventions Throughout this manual certain typographical conventions are followed to make it easier for you to recognize keystrokes, user actions, and cautionary notes. These conventions are described below. Keystrokes Names of keys that you are instructed to press are in bold face type. The three types of keystrokes are pressing one key, pressing multiple keys simultaneously, and pressing multiple keys in succession. Examples of these keystrokes and how they appear in this manual are shown below. Example F1 Ctrl-Alt-Del Shift F1 Keystroke Single key Multiple keys pressed simultaneously Multiple keys pressed in succession Mouse Actions You can use a mouse to navigate within menus and dialog boxes. The following commands describe specific mouse actions: Select Move the mouse pointer to an item and press the primary mouse button (usually the left button) once. The item becomes highlighted. You select items from list boxes. Choose Move the mouse pointer to the menu item or button and press the primary mouse button once. You choose commands from menus and buttons from within dialog boxes. Double-Click Move your mouse pointer to the item and click the primary mouse button twice quickly. At many dialog boxes, you can double-click on an item instead of selecting it and choosing a button. Enable/Disable This action is the same as clicking. You enable or disable radio buttons and check buttons by clicking on them. Radio buttons are diamond shaped and when one is enabled it appears pushed in and filled. A check button is a square that is filled when it is enabled. An unfilled button that appears pushed out is disabled. xv

16 DCM for HP-UX User s Manual Command Syntax Data that you enter in a dialog box or on a command line appears in special type: tar xvf /dev/rmt/0m. Command syntax may also contain parameters that appear in italic type to indicate variable data. For example, the format of the dcmstart command is: dcmstart -h -n config_filename where config_filename is the name of the configuration file (*.cnf) you want DCM to use upon startup. Directories, Filenames, and Environment Variables Unless otherwise specified, names of directories and files appear lowercase and in bold face type. For example, you can open /etc/services in one TextEditor window and services.add in another TextEditor window. Environment variables appear uppercase and in bold face type. For example, the preset value of DCMMAIN is /users/intermec/dcm. Suggested Reading You may need additional information for working with DCM in your data collection network. Additional documents that directly relate to the use of this product are: HP C/HP-UX Reference Manual, HP 9000 Series 700/800 Computers (HP Part Number ). Using the HP DTC Manager/UX, HP 9000 Series 800 Computers (HP Part Number J ). DTC Device File Access Utilities and Telnet Port Identification, HP 9000 Computers (HP Part Number B ). Installing and Administering NFS Services, HP AdvanceNet (HP Part Number B ). Using the X Window System (HP Part Number B ). HP Visual User Environment 3.0 User s Guide (HP Part Number B ). ORACLE Tools for UNIX Administrator's Reference Guide. xvi

17 Before You Begin ORACLE7 Server for UNIX Administrator's Reference Guide & Configuration Guide. ORACLE for HP 9000 Series 700/800 Installation & Configuration Guide. Data Communications Manual (Intermec Part Number ). To order additional Intermec manuals, contact your local Intermec representative or distributor. xvii

18

19 1 Learning About DCM

20

21 Learning About DCM 1 What Is DCM? This chapter explains what DCM is, what you can do with it, and how it improves your data collection process. Data Collection Manager is software that transports data from a data collection network to applications running locally or remotely on systems accessible through a computer network. DCM for HP-UX uses TCP/IP protocols to communicate across a UNIX network and sockets to implement its local data routing mechanisms. Once DCM is started, it runs in the background. You have to work with it only if you want to change your configuration or respond to an error message. Features DCM has many beneficial features: Routing Data Files and Transactions DCM can route data files or transactions (data strings in a format DCM can understand) to and from remote or local applications, local databases, and data collection devices. It can route this type of information by either a transaction identifier (transaction ID) placed in a field of the data string or a station address. All routing that takes place is transparent and automatic. Database Access You can configure DCM to perform read, insert, update, and delete operations on a local or remote Oracle database. Terminal Emulation You can log into your host system using an Intermec JANUS or IRL reader that is emulating a VT100/220/320 or ANSI terminal. Time Synchronization DCM can keep the internal clocks in your data collection equipment synchronized with the DCM host system. Data Validation DCM can validate data against alphanumeric ranges, ASCII files, and Oracle databases. Buffering Interprocess Communication (IPC) channels buffer data before and during transmission. If DCM cannot deliver transactions to an application, it uses a disk file to buffer the data. This buffering of data is referred to as hot standby. 1-3

22 DCM for HP-UX User s Manual OSF/Motif-style GUI DCM s Configuration and Control Manager (Conman) uses a Motif-style graphical user interface to configure and control the software. LRC DCM supports longitudinal redundancy check (LRC) in Intermec controllers. Data Collection Network Configuration You can selectively enable or disable station addresses on a controller in Conman. DCM enables the specified stations when it is started. Communications DCM uses the following forms of communication: Operating system services allow different operating system processes to communicate with each other. TCP sockets provide reliable data transfer with application programs running on remote systems. A variety of Intermec device protocols: controllers use standard controller protocol, printers use standard printer protocol or XON/XOFF protocol, and readers use XON/XOFF with ACK/NAK protocol. User Flexibility If you have just a single application, DCM is an easy, straightforward way of getting a data collection system up and running quickly by using the example configuration files and device profiles. You may even elect not to use certain modules, for example, local validation, and still take advantage of other features like device drivers or transaction routing. Many possible system configurations and applications work with DCM. Refer to Chapter 2, Transaction Fundamentals, and Chapter 3, Creating Applications, of the DCM for HP-UX Reference Manual for detailed information. 1-4

23 Learning About DCM 1 How to Use DCM Documented With Manuals and Online Help DCM is fully documented with a user s and a reference manual, and online help. The online help system not only provides descriptions of dialog boxes and fields, but also includes instructions for performing the tasks involved in configuring, controlling, and managing DCM. To fit DCM into your data collection system, you must complete the following tasks: Install and configure Intermec hardware Install and configure DCM Start DCM Run the selftest program to verify the installation Prepare your applications Although this manual discusses these tasks in detail in later chapters, the following pages present a summary of each task. Installing and Configuring Intermec Hardware Install any Intermec devices, such as controllers, readers, and printers by: 1. Connecting the device to the system with the correct cable. You can use a 25-pin connector cable (Intermec P/N ) or a 9-pin connector cable (Intermec P/N ). These cables have both a DTE and a DCE connector on one end. Use the DTE connector to connect a 9154 controller. 2. Setting device operational parameters (baud rate, parity, stop bits, data bits, LRC). Note: These device parameters must match the ones you use to configure the device through the Configuration and Control Manager (Conman) software. 3. Powering on the device. 1-5

24 DCM for HP-UX User s Manual For more information on installing and configuring Intermec hardware, refer to the documentation that came with the device you are installing. Installing and Configuring DCM Before DCM can work for you, it must be loaded onto the hard drive of a workstation. This process involves confirming that any third-party software you will use with DCM is installed on the workstation and running properly, making sure all hardware is connected properly, and then loading DCM from your Intermec tape. Chapter 2, Installing DCM, gives you step-by-step procedures for installing DCM. Once DCM is installed, you need to configure it to interact with all the connected downline devices and local and remote applications running on your system. Configuration is accomplished using the Configuration and Control Manager (Conman) in DCM. For more information about configuring DCM, refer to Chapter 3, Configuring a DCM System. Starting DCM After everything is installed and configured and your application programs are in place, you may start DCM. Once you start DCM, it runs in the background and you only have to work with it if you want to change your configuration or respond to some type of error. To learn how to start and control DCM, refer to Chapter 4, Managing DCM. Verifying Installation DCM provides the example program selftest that you can use to confirm that DCM is correctly installed. It verifies the communication path from an Intermec reader, through a concentrator, into a serial port, through the DCM software, and to the selftest application. For more information about using the selftest sample program, refer to selftest.doc found in the examples subdirectory. 1-6

25 Learning About DCM 1 Preparing Applications For DCM to work, it must have an application program to communicate with. The application program must be written it is not supplied with DCM. However, DCM does supply sample applications for you to use and modify. For guidelines on writing your own application programs, refer to Chapter 3, Creating Applications, in the DCM for HP-UX Reference Manual. 1-7

26

27 2 Installing DCM

28

29 Installing DCM 2 Upgrade Information This chapter describes how to install the DCM software, set up your HP-UX system to accommodate DCM, and modify DCM command scripts. If you are upgrading your DCM software from a previous release, follow the steps below before installing the new software. 1. Make sure all DCM related processing is stopped by: a. Accessing a command prompt on the system that runs DCM. b. Logging in as intermec. c. Entering the following command: $ dcmstop If DCM is running, the dcmstop command causes an orderly shut down of the software. If DCM is not running, dcmstop issues an error message and terminates. 2. Rename the directory that contains the old DCM software using the following command: $ mv current_directory_name new_name where: current_directory_name the name of the directory where the current version of your DCM software resides. new_name the new name you want for the directory containing your DCM software. For example, you could rename your dcm directory to include the version number as follows: $ mv dcm dcmv41 After you have completed the above steps, proceed with the installation of the new DCM software. You will copy your existing DCM configuration, error log, and hot standby files to the new dcm directory after you load the software. These files are compatible with newer versions of DCM. 2-3

30 DCM for HP-UX User s Manual Tasks for the UNIX System Administrator To install and set up DCM on your system, you must complete the following tasks: Create a DCM user account. Copy the DCM software from tape. Modify the /etc/services file. Add display station names to the /ect/hosts file. Update the Network Information Service. Set up serial ports on your system. Set up for terminal emulation. Note: When following the procedures given in this chapter, it is very important that you type the commands exactly as they are shown. For example, look at the following command:. $HOME/.kshdcm To enter this command, you type a period (.), followed by a space, followed by $HOME/.kshdcm, and then you press Enter. Creating a DCM User Account If you are upgrading an existing copy of DCM, the DCM account already exists on your system so you can skip this section and refer to the following section, Copying the Tape. To create a DCM user account 1. Log in to your system as root. 2. Create a new user account (intermec) using the facility provided by HP SAM. Refer to the HP documentation on SAM for more information. If you set up the account using SAM, you select the shell through the Startup Program push button. 2-4

31 Installing DCM 2 If you do not have access to SAM, use the method you are comfortable with to create the new user account for DCM. You can set the account to use the Korn shell or the C shell, but the Korn shell (/bin/ksh) is preferred. Copying the Tape All the files for the DCM software are provided in tar format on a magnetic tape. Although you can load the files into any directory, the examples in this chapter assume that you are using the /users/intermec/dcm directory. To extract the DCM files from the tape If you are upgrading an existing copy of DCM, skip to Step Log out of the root account and then log in to the new account (intermec) to copy the DCM software. Note: It is very important that you log out of the root account. If you copy the installation tape while you are logged in as root, the DCM files will not be created with the proper permissions. 2. Create a dcm subdirectory using the following command: mkdir dcm 3. Change to the dcm home directory: cd /users/intermec/dcm 4. Use tar to read the contents of the tape into the current directory. The tar command creates the entire DCM directory structure. The command shown below assumes the name of the tape drive is /dev/rmt/0m. tar xvf /dev/rmt/0m. Substitute the name of your tape drive into this command. 2-5

32 DCM for HP-UX User s Manual Modifying /etc/services If you are upgrading DCM from an older version of the software, you can skip this section and refer to one of the following sections later in this chapter: Setting Up Serial Ports, Setting Up for Terminal Emulation, or Tasks for the DCM User. All of the IPC channel names DCM uses must be listed in /etc/services. Without these entries, the DCM interprocess communication mechanism (IPC functions) will not operate. DCM does not modify /etc/services because it is controlled by your system administrator. You must log in as root and key in the IPC channel names required by DCM using a standard text editor such as vi. To get started quickly, you can use the template file services.add located in the tools subdirectory. It uses network port numbers starting at 4000 and contains application (destination) names used in the example DCM configuration files. Note: Since services.add is a template file, it is not guaranteed to work for your system. You must inspect services.add for any conflicts or duplicate names before you add it to /etc/services. To add socket names to /etc/services 1. Log in as root. 2. Make a backup copy of /etc/services. For example, you could rename this file to services.old. 3. Add the contents of services.add to the end of the /etc/services file on the system. You can accomplish this task by using the UNIX editor vi as follows: a. Edit the services file by entering the following command: vi /etc/services b. Place the cursor at the end of the file by entering: :$ c. Read in the services.add file by entering the following command: :r /users/intermec/dcm/tools/services.add 2-6

33 Installing DCM 2 d. Check that the port numbers you added from the services.add file start at 4000 and do not conflict with any of the port numbers you are already using. If there are port numbers in the file that are being used, change the DCM entries to unique port numbers to remove any conflicts. For detailed information on what names must exist in the /etc/services file, refer to Updating the /etc/services File in Appendix A. e. Save your work. Since the services file is typically a read-only file, you must use the following commands to save the contents of the file and exit from the editor: :w! followed by, :q If you use the HP-UX application, Text Editor, follow the steps below: a. Search for Text Editor by entering the following command: find / -name TextEditor 2>/dev/null Text Editor will typically be in the /usr/vue/config/types/tools/utilites directory. b. Start two copies of Text Editor by entering the following command twice: /usr/vue/config/types/tools/utilites/texteditor& Note: The ampersand at the end of the command is very important. It informs the shell to start the program without tying up your current window. c. Open /etc/services in one Text Editor window and services.add in the other Text Editor window. d. Select the entire services.add file and choose Copy from the Edit menu. e. From the window containing /etc/services, position the cursor at the end of the file and choose Paste from the Edit menu. The contents of the clipboard are inserted into the file. 2-7

34 DCM for HP-UX User s Manual f. From the File menu, choose Save to save the /etc/services file. 4. Check the services file to make sure the port numbers DCM uses start at 4000 and are not used elsewhere in the file. If the port numbers in the file are being used, change the DCM entries to unique port numbers to remove any conflicts. For detailed information on what names must exist in the /etc/services file, refer to Updating the /etc/services File in Appendix A. 2-8 Adding Display Station Names to /etc/hosts If you are upgrading DCM from an older version of the software, you can skip this section and refer to one of the following sections later in this chapter: Setting Up Serial Ports, Setting Up for Terminal Emulation, or Tasks for the DCM User. The /etc/hosts file contains the host names and IP addresses of all computers and display stations on your network. You must have an entry for each display station that will be used to set up or control DCM. Your system administrator can modify this file and should know how to obtain and assign the IP addresses of all display stations. Updating the Network Information Service If you are upgrading DCM from an older version of the software, you can skip this section and refer to one of the following sections later in this chapter: Setting Up Serial Ports, Setting Up for Terminal Emulation, or Tasks for the DCM User. The Network Information Service (NIS) is a distributed information system supplied by HP-UX. It allows commonly-used configuration files to be propagated throughout the network using a centralized management facility named the NIS master-server. Your system administrator will know if your HP-UX system is running as an NIS master-server, slave-server, or client. NIS allows you to centrally manage typical UNIX configuration files. Typical files include: /etc/group, /etc/netgroup, /etc/networks, /etc/passwd, /etc/protocols, /etc/rpc, /etc/hosts, and /etc/services. Changes made to these files on the NIS master-server are propagated to the NIS slave-servers. When NIS client machines run programs that make system calls that access the information in these files, an NIS master-server supplies the required information.

35 Installing DCM 2 If your HP-UX system is an NIS slave-server or client, the changes to /etc/services and /etc/hosts described in this chapter may have to be made on the NIS master-server. Consult your system administrator. Refer to the HP document, Installing and Administering NFS Services, for help with NIS. Setting Up Serial Ports If you have set up serial ports for an older version of DCM, you can skip this section and refer to Setting Up for Terminal Emulation later in this chapter. 1. Log in as root. 2. Make sure the serial ports DCM will use are not designated as login ports. The /etc/inittab file is composed of records that contain four fields delimited by colons. The last field in a record can contain a /etc/getty command followed by a device name. If the serial port you are using (for example, /dev/tty00, /dev/tty01) is associated with a getty statement, comment out the statement or remove it. To comment out a line, insert a pound sign (#) at the beginning of the line. For example, #tty00:234:respawn:/etc/getty /dev/tty After removing any getty commands from the inittab file, have the system read the file using the following command: init q Note: Consult with your system administrator to ensure this procedure does not cause any problems with your system. 2-9

36 DCM for HP-UX User s Manual 4. Your system administrator must set the protection on any serial port that DCM accesses in order for DCM to read from and write to that port. For example, the following command allows any user to perform read and write operations on the device named /dev/tty00. chmod o+rw /dev/tty00 Note: The above command is very important. If this command is not issued, DCM will not be able to access your system s serial ports and will emit many errors. Local RS-232 Ports The serial ports on HP-UX Series 700 workstations are located on the back of the machine. HP-UX Series 800 business servers can contain a MUX card that is connected to a box of serial port connections as well having serial ports on the back of the system. In either type of system, these ports can be considered local and have a device file associated with them, for example, /dev/tty00. To determine the names of the serial devices on your HP-UX system 1. Run SAM. 2. Choose Peripheral Devices and then choose View All. SAM displays a list of all hardware devices on the system. Look for the following RS-232 device descriptions: Built-in RS-232 device or MUX card. 3. Select one of the above device descriptions. 4. From the Action menu, choose Show Device Files. SAM displays a list of all possible device file names. For example, on a 700 Series workstation, SAM reports the device file name for the RS-232 port as /dev/ptr_rs232_a. 5. Once you know the device file name(s), use the ls -l command to get the device address. ls -l /dev/ptr_rs232_a This command returns, crw-r--r- 2 lp bin 0x Dec /dev/ptr_rs232_a 2-10

37 Installing DCM 2 6. To find any alias device names, use the hexadecimal number returned from the ls -l command as follows: ls -l /dev grep 0x On a 700 Series system, one of the device file names listed is tty00. Therefore, use /dev/tty00 as a serial port name when setting up devices in Conman. Setting Up for Terminal Emulation To use the terminal emulation capability of DCM, you must update your system with new terminal information files that describe how programs interact with Intermec readers. Terminal information files describe the different terminal types your UNIX system can interact with and are called the terminfo database. Note: The command script will run under the Bourne and Korn shells only. It will not run under the C shell. To set up your system for terminal emulation 1. Change to the tools directory. cd /users/intermec/dcm/tools 2. Run the following command script: im_termsetup.sh This command script copies terminal characteristics to the terminfo database for the following Intermec devices: Device 944x series terminfo File rdr944x 9450 rdr rdr x series rdr946x 9550 rdr rdr9560 JANUS rdransi 2-11

38 DCM for HP-UX User s Manual Tasks for the DCM User Users who want to log into the host system with an IRL device must provide the IRL terminal emulation program with the exact reader model number, for example, 9440 or The IRL terminal emulation program supports only a subset of the commands that a VT100 can implement. JANUS devices emulating VT100/220/320 terminals do not need a terminal information file. However, for ANSI terminal emulation you may want to include the file rdransi in terminfo for a generic ANSI terminal description. DCM uses UNIX environment variables, such as PATH and ENV, to control how it executes in the HP-UX operating system. You must set the environment variables and export them to your Korn or C shell: For help setting the environment variables, follow the steps in the next section, Modifying Shell Scripts and User Login Files. For help exporting the environment variables, refer to your operating system documentation for the Korn export or C setenv command Modifying Shell Scripts and User Login Files The environment variables that DCM uses are defined in two shell scripts:.kshdcm for the Korn shell and.cshdcm for the C shell. You can refer to Appendix A for detailed descriptions of the environment variables. You must select and modify the shell script that matches the shell you chose for the new account you are setting up. First, find the files d.kshdcm and d.cshdcm in the tools subdirectory. These files are templates for the shell scripts, so you should not edit them. To copy a template and create a shell script you can edit and use, follow the instructions for your shell: Korn shell Copy d.kshdcm to.kshdcm in the dcm root directory and make it executable: cd dcm cp tools/d.kshdcm $HOME/dcm/.kshdcm chmod 775.kshdcm

39 Installing DCM 2 C shell Copy d.cshdcm to.cshdcm in the dcm root directory and make it executable: cd dcm cp tools/d.cshdcm $HOME/dcm/.cshdcm chmod 775.cshdcm Next, perform the steps in the following sections to set up the Korn or C shell,.vueprofile (optional), DISPLAY, and gain access to Oracle databases. Korn Shell Setup 1. Login as intermec. 2. Access the dcm directory. cd $HOME/dcm 3. Use an editor (like vi) to modify the.kshdcm file. vi.kshdcm 4. Set the DCMMAIN environment variable to point to the correct directory. As shipped, the environment variables assume DCM is installed in /users/intermec/dcm. 5. Use an editor (like vi) to modify the.profile file located in the $HOME directory. Add the following statement, which includes the current directory and the directory that contains xterm in PATH: PATH=${PATH}:.:/usr/bin/X11; export PATH If.profile does not exist, you must create it. Use d.profile (located in the tools directory) as a template by copying it to the home directory of the intermec account as follows: cp $HOME/dcm/tools/d.profile $HOME/.profile chmod 775 $HOME/.profile Note: If you created.profile from d.profile, remove any statements from.profile that you do not need. 6. Define the ENV environment variable in.profile. The Korn shell translates ENV to determine the location of the shell resource file,.kshrc. A typical setup is: ENV=$HOME/.kshrc; export ENV 2-13

40 DCM for HP-UX User s Manual 7. Modify your.kshrc file to source the.kshdcm file you created or modified. Add the following line to the end of the.kshrc file:. $HOME/dcm/.kshdcm If.kshrc does not exist, you must create it. Use the d.kshrc file (located in the tools directory) as a template by copying it to the home directory of the intermec account. cp $HOME/dcm/tools/d.kshrc $HOME/.kshrc chmod 775 $HOME/.kshrc 8. After you modify.profile and.kshrc, activate the changes by sourcing the following files: cd $HOME../.profile../.kshrc C Shell Setup 1. Login as intermec. 2. Access the dcm directory. cd $HOME/dcm 3. Use an editor (like vi) to modify the.cshdcm file. vi.cshdcm 4. Set the DCM environment variable to point to the correct directory. As shipped, the environment variables assume DCM is installed in /users/intermec/dcm. 5. Use an editor (like vi) to modify the.login file. Add the following statement, which includes the current directory and the directory that contains Xterm in PATH: setenv PATH.:/usr/bin/X11:${PATH} 6. Modify your.cshrc file to source the.cshdcm file you created or modified. Add the following line to the end of the.cshrc file: source $HOME/dcm/.cshdcm If.cshrc does not exist, you must create it. 2-14

41 Installing DCM 2 7. After you modify the.login and the.cshrc files, activate the changes by sourcing the following files: cd $HOME source./.login source./.cshdcm Setting Up.vueprofile If you are not running the HP VUE window manager on your X terminal, you can ignore this section. When you log in to HP-UX under a Visual User Environment (VUE) window, HP-UX reads.vueprofile. The HP Visual User Environment 3.0 User s Guide discusses modifications you need to make to.vueprofile located in the intermec directory. By default, HP VUE does not read.profile (ksh) or.login (csh), so you must modify.vueprofile to make it read the correct file. Follow the directions in the HP Visual User Environment 3.0 User s Guide section To use a shell environment file with.vueprofile to make.vueprofile source.profile or.login. The tools subdirectory in the dcm account contains the following template files: d.vueprofile, d.profile, d.kshrc. Use these files as a reference for setting up the following files on your system:.vueprofile,.profile,.kshrc. You know your workstation is running HP VUE if you see the Front Panel, similar to the one shown below, on your display. From the Front Panel, you can customize the settings of your visual environment. It is recommended that you configure the following two visual elements of HP VUE before running the Configuration and Control Manager (Conman) for the first time: Window behavior Font size 2-15

42 DCM for HP-UX User s Manual To change window behavior 1. From the Front Panel, choose the Style Manager icon. 2. From the Style Manager menu, choose the Window button. The Style Manager - Window dialog box appears. 3. In the Window Behavior box, select the Click In Window For Focus radio button. This setting requires that you click the mouse button in a window before that window becomes active. 4. Choose OK to save your changes. To specify the font size 1. From the Front Panel, choose the Style Manager icon. 2. From the Style Manager menu, choose the Font button. The Style Manager - Font dialog box appears. 3. In the Size box, select a font size that is adequate for your display. For most displays, Intermec recommends using a font size of 13.5 for running Conman. 4. Choose OK to save your changes. You may also change the default font that Conman uses in its dialog boxes and windows; however, this procedure cannot be done from the Front Panel. To specify the font and font size Note: If you installed DCM in your login directory, do not use this procedure as it will cause a conflict with the conman executable file for the Conman application. 1. Change to the /usr/bin/x11 directory. 2. Use the following command to display the contents of the xlsfonts file: xlsfonts more This file lists all the available fonts for your system. Some font names are very long and cryptic, while others are short and vague. The first number in the name is usually the point size of the font. An example of a short font name that your system might have is helvr12 (12 point medium Helvetica). 2-16

43 Installing DCM 2 3. Create the file conman in your login directory. 4. Add the following line to the conman file you created in Step 3: conman*fontlist: helvr12 You can enter a different font entry from the xlsfonts file instead of helvr12. Be sure you type the left side of the line exactly as shown above (note the capital L in fontlist) and that you correctly type the font entry on the right side of the line. The system will pick a font for you if you mistype the font entry. The next time you start Conman, the font you specified in the conman file will be used. You may need to experiment with the different fonts available in the xlsfonts file until you find a font to your liking. Note: If you pick a large font, some text may be visually crowded or clipped in the Conman windows and dialog boxes. However, this will not affect the application s performance or accuracy. Setting DISPLAY When you log in to HP-UX, you need to set the DISPLAY environment variable to point to the network name of your display station. The display station can be an X terminal or another computer you are using to access the HP machine. The setdisplay script (located in the tools subdirectory) will set DISPLAY to whatever value you specify. For example, if the host name of your display station is boxer, enter the following command in the DISPLAY variable:. setdisplay boxer The script sets DISPLAY to boxer:0.0. HP-UX uses DISPLAY to determine which display to use when it runs X programs such as the DCM configuration program, conman. The name you use in the setdisplay command must exist in the /etc/hosts file. Refer to Adding Display Station Names to /etc/hosts in this chapter for more information. If your display station is a computer, you will have to allow HP-UX to access the X server running on your local system. For example, you might be using a PC or another UNIX machine as your display station. To allow HP-UX to display bitmap output on your local machine, use either the xhost command or modify the /etc/x0.host file. 2-17

44 DCM for HP-UX User s Manual For example, suppose your HP-UX machine is named speedy and you access it through a SUN system or a PC running an X emulator. On your SUN or PC, enter the following command: xhost speedy This command allows the X client on speedy to access the X server on your local machine. Note: Use the xhost command only once per login. The xhost command is usually located in the /usr/bin/x11 directory. To make this change permanent, add the host name to the /etc/x0.host file. This file contains the host name of each remote host that is allowed access to your local X server. If the X0.host file does not exist, you must create it. For more information on the DISPLAY environment variable and the X0.host file, refer to the HP manual, Using the X Window System. Giving DCM Access to Oracle Databases If you have already modified your user login files to allow DCM access to your Oracle database, or you do not want DCM to be able to access the Oracle database system, or you do not have the Oracle RDBMS installed on your system, you can skip this section and refer to Installing a DCM License later in this chapter. ORACLE_HOME and ORACLE_SID are the key environment variables used by the Oracle system. They uniquely identify each Oracle database and its root directory. You can use the TWO_TASK environment variable to determine the default database. ORACLE_HOME Represents the full path name of an Oracle system home directory. You can use this information to find executable programs and data files. You must set the ORACLE_HOME variable to identify the root directory of the Oracle Server directory hierarchy. Use this home directory to locate Oracle system files. ORACLE_SID This is the Oracle Server system identifier. You can also think of it as the Oracle Database name. Each Oracle system has its own unique ORACLE_SID. 2-18

45 Installing DCM 2 TWO_TASK This environment variable is read by the Oracle two-task interface to determine the default driver (protocol), host, and database. Setting TWO_TASK overrides the values of ORACLE_HOME and ORACLE_SID in determining the database to which you will connect. If your database is running on the local HP machine (the same HP machine as DCM), then you need to specify ORACLE_HOME and ORACLE_SID in your.profile (ksh) or.login (csh). If your database resides on a remote machine, then you need to specify the TWO_TASK environment variable in your.profile (ksh) or.login (csh) files. Sample Oracle Environment Variable Settings If Oracle is running on the local HP machine and you are using: Korn shell (place in.profile) ORACLE_HOME=/users/oracle/dba/oracle/product/ ; export ORACLE_HOME ORACLE_SID=SFTPRD ; export ORACLE_SID PATH=${PATH}:$ORACLE_HOME/bin ; export PATH C shell (place in.login) setenv ORACLE_HOME /users/oracle/dba/oracle/product/ setenv ORACLE_SID SFTPRD setenv PATH ${PATH}:$ORACLE_HOME/bin If Oracle is running on a remote machine with the following information: Driver (protocol): TCP/IP Host machine name: mfgserver Database name (SID): SHIPPING You need to set the Oracle environment variable, TWO_TASK. This environment variable defines the protocol Oracle s SQL*Net will use to communicate with the database, the host name of the machine where the database resides, as well as the name of the database. SQL*Net V1 and V2 use different formats for the TWO_TASK environment variable. 2-19

46 DCM for HP-UX User s Manual SQL*Net V1.X In order to allow DCM Database Server applications to access the remote database SHIPPING, you define TWO_TASK as: Korn shell (place in.profile and.kshrc) TWO_TASK=T:mfgserver:SHIPPING ; export TWO_TASK C shell (place in.login and.cshrc) setenv TWO_TASK T:mfgserver:SHIPPING SQL*Net V2.X Set TWO_TASK to the service name for the remote database. This name can be thought of as an alias for the remote database and is found in the tnsnames.ora file. Your system administrator sets up this file. Note: See your Oracle system administrator to learn the values for ORACLE_HOME, ORACLE_SID, and TWO_TASK. If you need more information about Oracle environment variables, see the following Oracle manuals: ORACLE Tools for UNIX Administrator's Reference Guide ORACLE7 Server for UNIX Administrator's Reference Guide & Configuration Guide ORACLE for HP 9000 Series 700/800 Installation & Configuration Guide After the Oracle environment variables have been placed in your.profile (Korn shell) or.login (C shell), you need to run the files to have the environment variables take effect. 1. Do one of the following: Log out, log in, and then proceed with Step 2. Enter the following commands: Korn shell. $HOME/.profile. $HOME/.kshrc C shell source $HOME/.login source $HOME/.cshrc 2-20

47 Installing DCM 2 2. Enter the following commands: echo $ORACLE_HOME echo $ORACLE_SID echo $TWO_TASK 3. Confirm that the displayed values are what you expect. If they are not, check your.profile or.login file and confirm that they were typed correctly. If the values do not appear when you run the echo command, you probably did not execute your.profile and.kshrc or.login and.cshrc in the current session. Make sure the files are executed in the session that you are in. After you execute.profile or.login, confirm that you can access the Oracle database by running the Intermec supplied utility dbverify to log in to the database pointed to by your environment variables. 1. Change to the DCM tools directory. If you installed DCM in the dcm directory you would enter: cd dcm/tools 2. Run the dbverify utility to confirm that you can access the database. dbverify You should see the following: Input operation: Connect to Database.. (c) Quit dbverify..... (q) > 3. Enter c to connect to the database. You are prompted for your user ID and password. If the connection is successful, you will see: Please wait...connecting to ORACLE database Connect SUCCESSFUL!...Disconnecting 4. Enter q to quit. This procedure verifies that you can access the Oracle database pointed to by your environment variables. 2-21

48 DCM for HP-UX User s Manual If you are unable to connect to the Oracle database, you will see something similar to the following: Please wait...connecting to ORACLE database ERROR while trying to Connect Sql Return Code: ORA-03114: not connected to ORACLE 1. Confirm that you entered the correct user ID and password. 2. Reconfirm that the values you set for the environment variables are correct by entering the following commands at the UNIX prompt: echo $ORACLE_HOME echo $ORACLE_SID echo $TWO_TASK If the values that display are not what you expect, check your.profile or.login file and confirm that the values were entered correctly. If the values do not appear when you run the echo command, then you probably did not execute your.profile and.kshrc or.login and.cshrc files in the current session. Make sure that you are running dbverify in the same session as the one you run your.profile and.kshrc or.login and.cshrc. Installing a DCM License Your copy of DCM comes with an Intermec Software License Information letter that contains your software license key. The license key consists of five groups of four uppercase characters separated by dashes: XXXX-XXXX-XXXX-XXXX-XXXX If you purchased a Level 1 license, you have a single license letter. If you purchased a Level 2 license, you have two license letters. Purchasers of a Level 3 license receive three license letters. You must install the licenses in increasing order. For example, if you purchased a Level 3 license, you must first install the Level 1 license, then the Level 2 license, and finally the Level 3 license. 2-22

49 Installing DCM 2 To install the license(s) 1. Log in using the intermec account. If you perform this step as root, DCM may not be able to read the license file while it is running. 2. Change to the DCMMAIN directory. cd $DCMMAIN 3. Run the license manager program by entering the following command: lm You are prompted for the license key found in your license letter. 4. Type the key and press Enter. The license manager prompts you for confirmation of the information you entered before applying it to the file. 5. Verify that you entered the license key correctly, press Y, and then press Enter. License-Related Event Messages DCM employs a license key that limits the number of data collection devices to which DCM can communicate. The key is stored in the file intermec.lic. If intermec.lic does not exist or is corrupt, DCM will communicate with only a maximum of three devices. This is the default value. When DCM cannot find or read from the license file, it sends the following error message: :15: Could not get license information from license file. License filename was intermec.lic. Function return code = 102. DCM registers a device or an application program the first time it sends data to DCM. DCM maintains an internal count of the number of registered devices. Every time a new device or application sends or is sent data, DCM increments its count. If the count reaches the maximum value, DCM will not accept data from nor send transactions to any new device or application. 2-23

50 DCM for HP-UX User s Manual Every time DCM registers a new device, it sends an event message to the status session window and to the error log file. The event message contains the logical name of the device and a count of how many devices have been registered. Two sample event messages follow: :32: Supported device count information: Current device count is now 29. Transaction was destined for device: rdrpa :33: Supported device count information: Current device count is now 30. Transaction originated from device: rdrpb If DCM determines it cannot send a transaction because the device count limit has been reached, it discards the transaction. The transaction is not saved in the audit file, the event message file, or any hot standby file and it results in an error message that looks similar to the following messages: :36: Active device count exceeded. Transaction not routed. Transaction originated from device: rdrpz :36: Active device count exceeded. Transaction not routed. Transaction was destined for device: rdrpz 2-24

51 3 Configuring a DCM System

52

53 Configuring a DCM System 3 Starting Conman This chapter shows you how to use Conman to configure your DCM system. It includes information about working with configuration files, devices, interface types, destinations, and transaction IDs so that your downline data collection network can communicate with DCM. The Configuration and Control Manager (Conman) is the software interface that enables you to interact with the DCM message handler. Through Conman you can view performance statistics or alter the configuration or operation of the DCM system. To start Conman 1. Start a shell window. 2. Go to the DCM root directory. cd dcm 3. Run Conman by entering one of the following commands: conman conman& where & causes the shell to start Conman independently of your terminal window. As Conman starts, a message appears on the screen indicating that Conman is checking the status of DCM. If DCM is running in the background, Conman attempts to establish communications with it. When the DCM Configuration and Control Manager is running, you see the DCM Conman menu. 3-3

54 DCM for HP-UX User s Manual Using Configuration Files Use the File menu to create, access, save, and load configuration files in DCM. Configuration files (filename.cnf) contain information on how DCM interacts with downline devices and applications. There can be several configuration files, but DCM can only use one at a time. The configuration file contains the names of all devices connected to your system, the names of all applications that run with your system, and the directions for transferring data between the applications and the devices. Before you start DCM for the first time, you need to load a configuration file for DCM to use. You can build a file from scratch or modify one of the example files that come with DCM. The example configuration files are located in the dcm root directory. To open a configuration file 1. From the File menu, choose Open. You see the file selection dialog box. The fields in this dialog box are described below: Filter Enter the path where you want to search for configuration files. For example, you could enter /dcm/examples/*.cnf and choose Filter to have Conman search the examples subdirectory for all files with a.cnf extension. Directories Select the directory where your configuration files are stored. Files Select the name of the file you want to open from the list. Select DCM config file Enter the path and the name of the file you want to open. 3-4

55 Configuring a DCM System 3 2. Choose OK to load the configuration file. When you make a change to a configuration file, the Conman menu bar title displays an asterisk (*) at the end of the filename. The asterisk is a reminder that you have unsaved changes in your configuration file. To save a configuration file From the File menu, choose Save. Your configuration file is saved, overwriting the previous version of the file. If changes are made to a configuration file, but you want to keep the original file unchanged, you can save the changes under another filename. To save a file under a new name 1. From the File menu, choose Save as. You see the file selection dialog box. 2. Type the new filename in the Save DCM config file edit box. Note: You can also select or enter a new directory and/or path for the file. 3. Choose OK to save your file under the new name and/or location. Once you assign a configuration file to DCM, you can create new or edit existing configuration files in Conman without affecting the one being used by DCM. To see which file is currently being used by DCM, look in the Status Watch window. The configuration file shown in the Conman menu bar title may not be the one currently in use by DCM. Refer to Chapter 4, Managing DCM, for help on understanding the DCM Status Watch window. To have DCM use a specific configuration file 1. From the File menu, open the configuration file you want DCM to use. 2. From the File menu, choose Use to run DCM. A message box appears. 3. Choose Use to have DCM use the configuration file you selected the next time it is started. 3-5

56 DCM for HP-UX User s Manual Exiting Conman To create a new configuration file From the File menu, choose New. The file you open is named untitled.cnf and you are returned to the Conman menu. Use the Save as command on the File menu to rename this file. You can quit Conman at any time, whether you have started DCM or not. If DCM is running, it keeps running even when you exit Conman and log out. To exit Conman 1. From the File menu, choose Exit. If you have made changes to your configuration file, a message box appears allowing you to save them. 2. Do one of the following: Choose Save to save the changes to your configuration file and exit Conman. Choose Discard to exit Conman without saving changes to the configuration file. Choose Cancel to remain in Conman. 3-6

57 Configuring a DCM System 3 Setting Up Downline Devices Before you begin running DCM, you need to configure it for the Intermec devices (controllers, concentrators, and readers) and stations (readers, printers, and wand stations) used in your data collection system. You should verify that all devices are properly connected to the DCM workstation and that all stations are properly connected to the appropriate devices. Once you have a device physically connected to your DCM workstation, you identify it in Conman by setting communication parameters and establishing a logical name. This information is stored in a configuration file on disk and accessed by DCM during startup. Note: Refer to individual product manuals for instructions on cabling, placement, and initialization when installing devices and stations. To add a device to your DCM configuration 1. From the Setup menu, choose Downline devices. The Downline Device List dialog box appears. All devices connected to your system must be logically defined through this dialog box. This dialog box lists the devices in order by device type. 3-7

58 DCM for HP-UX User s Manual 2. From the Downline Device List dialog box, choose Add. The Add Downline Device dialog box appears. This dialog box contains the following fields: Device type Click the down arrow to select the device type from the list. Channel If you are configuring a 9154 controller, enable the channel (m, n, o, or p) you will be using with your station(s). Connection Type the name of the serial port where the device is connected. For example, /dev/tty0p1. 3. Choose Options. The Connection Options dialog box appears. 3-8

59 Configuring a DCM System 3 4. Verify that the dialog box information is consistent with the configuration parameters on the device. If any of the information is incorrect, edit the field(s) or select the correct option(s). Baud Use the down arrow to display a list of available baud rates. Parity Enable the correct parity for the device. LRC enabled Enable this check button if the longitudinal redundancy check (LRC) character is appended to data transmitted by an Intermec controller. LRC provides horizontal error checking of data blocks received and transmitted by the controller by performing an exclusive OR of the data bits, excluding the SOM, but including the received or transmitted EOM characters. If the device you are configuring is not a controller, the LRC enabled check button is unavailable. Data bits Enable the number of data bits used by the device. Accept Time Sync Enable this check button if you want the device (Intermec controllers and readers) to accept time synchronization messages from DCM. If the device you are configuring cannot accept a set time command from the system, this check button is unavailable. You must also do one of the following operations in order for the device to accept time synchronization messages: Enable Time Synchronization in the DCM System Operation Setup dialog box to allow DCM to transmit the host time to this device at an interval (in minutes) that you specify. Choose Now (enabled only when DCM is running) in the Control DCM System Operation dialog box to have DCM issue an immediate time synchronization message to the device. Stop bits Enable the number of stop bits used by the device. Protocol Enable the communication protocol the printer is using: Standard or XON/XOFF. If the device you are configuring is not a printer, the Protocol box is unavailable. Note: It is important to ensure that the communication options (baud, parity, data bits, stop bits, protocol, and LRC) set up in DCM for a device are duplicated in the actual device. 3-9

60 DCM for HP-UX User s Manual Destination Parameters If the device you are configuring is to be used as a destination for transactions, provide information for the following parameters: File transfer timeout For downloading files to a device, enter the timeout period in seconds you want DCM to wait for a response from the device before it times out the file transfer process. The default value is appropriate for most systems. Hot Standby timeout Enter the timeout period in seconds you want DCM to wait for a response from the device before it writes the transaction to disk. The default value is appropriate for most systems. Transactions held in volatile memory by DCM Enable one of the following radio buttons to specify how you want DCM to handle an application s transactions: None Any transaction that is not immediately acknowledged by the application is written to the hot standby file. No transactions are held in the application s auxiliary channel. Unlimited DCM holds all transactions for the application in memory (the application s auxiliary channel) unless the application times out. If this occurs, DCM writes the contents of the auxiliary channel to the hot standby file. This is the fastest mode; however, in the event of a system failure any data in memory will be lost. Maximum Enter the number of transactions you want DCM to be able to hold in an application s auxiliary channel before it will write the contents of the channel to disk if the application times out or the number of transactions you specify for the channel is exceeded. You can enter a zero if you do not want DCM to hold any transactions in memory. Integrity mode DCM can operate in one of two data integrity modes: faster or safer. The integrity mode you select determines how a DevComm implements the protocol level handshake that occurs between the host system and the Intermec controller or reader. Faster In faster integrity mode, the DevComm acknowledges a controller or reader immediately after it receives data from the device. The DevComm then passes the data to the message handler and the message handler routes the data to the application program. 3-10

61 Configuring a DCM System 3 Safer Safer mode can provide extra data integrity as the DevComms will withhold the delivery of a data link ACK to the device until one of the following situations has occurred: The application sends an ACK transaction to DCM, indicating it has received the transaction from the device. The transaction is stored by DCM on disk in a hot standby file. 5. Choose OK to return to the Add Downline Device dialog box. 6. Choose OK to add the new device. Editing a Device 1. From the Downline Device List dialog box, do one of the following: Select the device you want and then choose Edit. Double-click the device in the list. The DCM Downline Device dialog box appears. 3-11

62 DCM for HP-UX User s Manual 2. Use this dialog box to change a device s connection or communication options or to edit the parameters of one or more of its stations. Connection Indicates the device s serial port connection. To change serial ports, enter the name of the port in this entry box. For example, /dev/tty0p1. Options Choose this button to change the device s options by accessing the Connection Options dialog box. For more information on the fields in this dialog box, refer to pages 3-9 to Below the Device box, you will see a graphical representation (map) of the device and its stations, or a text representation (list) of the device and its stations. The previous figure shows the map, which is the default display. Note: A direct connect device, such as a printer or a reader, is only displayed in the list format. It is always enabled and cannot be disabled by DCM. The three box key shown on the left is located below the station map. The boxes display the color designations for the device stations that are enabled, disabled, and selected. When a station is enabled, it has the same text and background color as the Enabled key box. The same is true for stations that are disabled. When you select a station to modify its parameters, that station has the same text color as the Selected key box and its background color will match the color for its enabled/disabled state. In the map, each station is represented by its physical address. You can enable/disable a station by doing one of the following: Double-clicking on the specific station s icon box. Select a station and then enable/disable the Enabled check button. Note: You can enable/disable a station, but you cannot enable/disable a device. Devices are always enabled. For a only, enabling/disabling a single multi-drop station causes that station's entire channel to be enabled/disabled. 3-12

63 Configuring a DCM System 3 Editing Station Parameters Stations are the Intermec equipment that are connected to a controller in your data collection network, like readers, printers, and wand stations. To edit station parameters 1. From the DCM Downline Device dialog box, select an address and choose Station. The Station Parameters dialog box appears. 2. Verify that the dialog box information is correct. If any of the information is incorrect, edit the field(s) or select the correct option(s). Logical name Enter a name for the device. This name is usually how you refer to the device in your system. For example, reader1 or printer8. Able to receive data Enable this check button if the station is an Intermec device that can receive data from the system. This button should be enabled for Intermec readers that have a display and for Intermec printers. If this check button is disabled, data will not be forwarded to the station. Physical name This field displays the station s name by its physical address on the Intermec data collection network. 3-13

64 DCM for HP-UX User s Manual Device type Enter the station s device type or click the down arrow to choose from a list of available devices. Transaction ID to insert Click the down arrow to choose the transaction ID you want the DevComm to insert in transactions coming from this station. This field is used for stations such as printers, scales, and wedges that do not have the capability to place transaction IDs in the transactions they send. Delivery Responses If you want the sending application to receive responses from the DevComm for the device (controller and/or direct connect reader or printer) connected to it, enter the following information: Success The response entered in this field is sent from the DevComm to the application to indicate that the device received the transaction sent by the application. This response can be a maximum of 39 characters. Failure The response entered in this field is sent from the DevComm to the application to indicate that the device did not receive the transaction sent by the application. This response can be a maximum of 39 characters. Note: When the DevComm is communicating with an Intermec controller, the delivery responses the DevComm sends to the application indicate the success or failure of transactions reaching the controller and not the station(s) connected to it. Note: If the device connected to the DevComm is an Intermec 3000 printer, then only "success" responses are returned from the printer. 3. Choose OK to return to the DCM Downline Device dialog box. 3-14

65 Configuring a DCM System 3 Changing the Colors of the Station Map 1. Choose Map color in the DCM Downline Device dialog box. The Conman Station Map Colors dialog box appears. 2. Select the item you want to change and then select its color from the list. Your color changes are shown in the map key boxes. 3. Do one of the following to return to the DCM Downline Device dialog box: Choose Default to return to the preset colors. Choose OK to save your changes. Viewing a List of Stations Choose View List in the DCM Downline Device dialog box to display a list of all possible stations for the device. Note: The last entry in the list is for the device itself (for example, 9180, 9154, 9161). 3-15

66 DCM for HP-UX User s Manual When the list appears, the View List button changes to View map. The list of stations has an Enable column indicating if the station is enabled (Y) or disabled (-). You can enable/disable a station by: Double-clicking the station entry in the list. If the station was disabled, it becomes enabled; if the station was enabled, it becomes disabled. Clicking the station entry in the list and then selecting/deselecting the Enabled check box. All stations are disabled when you configure a new device. If you select a station and enable it, you can modify its parameters by choosing the Station button. Note: You can enable/disable a station, but you cannot enable/disable a device. Devices are always enabled. For a only, enabling/disabling a single multi-drop station causes that station's entire channel to be enabled/disabled. 3-16

67 Configuring a DCM System 3 Deleting a Device 1. Select the device you want to delete from the Downline Device List dialog box. 2. Choose Delete. A message box appears. 3. Choose Delete to remove the device from your configuration. Configuring Interface Types An interface type is a group of data within DCM that identifies and describes a physical entity such as an application or a file. Interface types are used to set up destinations or for validating data. DCM uses the following interface types: file, database, application, and terminal emulation. To configure an interface type, you give it a unique name and define properties for it. The advantage of using interface types is that you need only enter the information that describes an interface type once. You can then configure many destinations and/or validation setups that refer to the same interface type. File Interface DCM uses file interface information to perform data validation. To add a file interface 1. From the Setup menu, choose Interface types. 2. From the Interface types menu, choose File. 3-17

68 DCM for HP-UX User s Manual The File Interface List dialog box appears. The Interface Name list box contains all file interface names that have been defined in DCM. 3. From the File Interface List dialog box, choose Add. The File Interface Setup dialog box appears. This dialog box contains the following fields and buttons: Interface name A unique name that identifies the file to DCM. File name The path and name of the file you want associated with the interface name. You can use the Find button to locate the file and its path on the system. 3-18

69 Configuring a DCM System 3 Find Choose this button to display a file selection dialog box in which you can locate the path and name of the file you want to use. 4. Choose OK. Editing a File Interface 1. From the File Interface List dialog box, do one of the following: Select the file interface you want and choose Edit. Double-click the file interface name. The File Interface Setup dialog box appears. 2. Edit the field(s) you want to change. 3. Choose OK. Deleting a File Interface 1. From the File Interface List dialog box, select the file interface you want to delete. 2. Choose Delete. A message box appears. 3. Choose Delete to remove the file interface from your configuration. Note: After choosing Delete, you may see a message box informing you that the file interface is being used for validation purposes. You must remove all configuration usage of the file interface before it can be deleted from your configuration. 3-19

70 DCM for HP-UX User s Manual Database Interface Database interfaces are required if you want DCM to validate transaction fields against a database or if you want to set up DCM to perform read, write, update, or delete operations on a database. To add a database interface 1. From the Setup menu, choose Interface types. 2. From the Interface types menu, choose Database. The Database Interface List dialog box appears. The Interface Name list box contains a list of all database interfaces that have been defined in DCM. 3. From the Database Interface List dialog box, choose Add. The Database Interface Setup dialog box appears. 3-20

71 Configuring a DCM System 3 This dialog box contains the following fields: Interface name Enter a unique name (up to 16 characters) that identifies the database interface to DCM. You define an interface for each unique database access you require. For example, if you need to access the same database using two different user ID/password combinations, you would define two separate database interfaces. Type Enter the type of database you are using. At this time, DCM for HP-UX supports the Oracle for UNIX database, and DCM for OS/2 supports DB2/2 and Oracle for OS/2 databases. Network protocol Enter the protocol used to communicate with your remote Oracle database. If your database is located on the same machine as DCM (local), select none from the list box. 3-21

72 DCM for HP-UX User s Manual The following table lists the fields in this dialog box that require information based on the network protocol of your database. Network Protocol Related Field(s) None Database name Enter the database name. This information is optional. If you leave this field blank, DCM will use the ORACLE_SID or the TWO_TASK environment variable to determine the database name. As a result, you can have a local or a remote database for which DCM uses the standard Oracle environment variables to determine the database location. SQL*Net v1.x Database name Enter the database name. This information is required. Available protocols are: TCP/IP, SPX/IPX, TCP/IP TLI, and Netbios (OS/2 only). Server Enter the host name of the machine where the database resides. This information is required. On UNIX systems, the host name can be found in the /etc/hosts file and on OS/2 machines, the host name is located in the \tcpip\etc\hosts file. SQL*Net v2.x Database alias Enter the alias name of the database. Look in the tnsnames.ora file, setup by your database administrator, to determine the names of any aliases. This information is required. User ID Enter your database access user ID. Show password Enable this check button to display your password in the Password edit box. Conman encrypts your password before storing it in the configuration file. Password Enter your database access password. 4. Choose OK. Editing a Database Interface 1. From the Database Interface List dialog box, do one of the following: Select the database interface you want and choose Edit. Double-click the database interface name you want. The Database Interface Setup dialog box appears. 2. Edit the field(s) you want to change. 3. Choose OK. 3-22

73 Configuring a DCM System 3 Deleting a Database Interface 1. From the Database Interface List dialog box, select the database interface you want to delete. 2. Choose Delete. A message box appears. 3. Choose Delete. Note: When you choose Delete, you may see a message box stating that a destination is using this database interface. You must remove all configuration usages of the database interface before it can be deleted from the system. Application Interface Application interfaces only have a name property that identify your local and remote applications to DCM. To add an application interface 1. From the Setup menu, choose Interface types. 2. From the Interface types menu, choose Application. The Application Interface dialog box appears. The Application Interface dialog box contains a list of all application interfaces that have been defined in Conman. 3-23

74 DCM for HP-UX User s Manual 3. Enter a unique name in the Interface name box. 4. Choose Add to save the new application interface name. Changing an Application Interface Name 1. From the Application Interface dialog box, select the application interface you want to rename. 2. Enter the new name in the Interface name box. 3. Choose Change to rename the application interface. Deleting an Application Interface 1. From the Application Interface dialog box, select the application interface name you want to delete. 2. Choose Delete. A message box appears. 3. Choose Delete. Note: When you choose Delete, you may see a message box stating that a destination is using this application interface. You must remove all configuration usages of the application interface before it can be deleted from the system. Terminal Emulation Interface DCM uses terminal emulation interfaces to provide VT100/220/320 and ANSI display capabilities to Intermec readers. It allows you to use your reader to transparently communicate with applications running on the DCM host machine or on any remote host on the same network. If you are using only DOS-based readers (JANUS family), configure one JANUS TE interface. If you are using only IRL devices, configure one IRL TE interface for each IRL device. To add a terminal emulation interface 1. From the Setup menu, choose Interface types. 2. From the Interface types menu, choose Terminal emulation. 3-24

75 Configuring a DCM System 3 The Terminal Emulation Interface List dialog box appears. 3. From the Terminal Emulation Interface List dialog box, choose Add. The Terminal Emulation Interface dialog box appears. This dialog box contains the following fields: Interface name Specify a unique terminal emulation interface name. Emulation type Enable one of the following emulation types: JANUS To support a JANUS (20X0) reader. IRL To support Intermec IRL devices (94XX and 95XX). 4. Choose OK. 3-25

76 DCM for HP-UX User s Manual Note: To use the terminal emulation feature, you must configure a destination that uses a terminal emulation interface type. Refer to Configuring a Transaction ID and Configuring DCM for Terminal Emulation for more information. Editing a Terminal Emulation Interface 1. From the Terminal Emulation Interface List dialog box, do one of the following: Select the terminal emulation interface you want and choose Edit. Double-click the terminal emulation interface name you want. The Terminal Emulation Interface dialog box appears. 2. Edit the field(s) you want to change. 3. Choose OK. Deleting a Terminal Emulation Interface 1. From the Terminal Emulation Interface List dialog box, select the terminal emulation interface you want and choose Delete. A message box appears. 2. Choose Delete. Note: Choosing Delete may display a message box that states a destination is using this interface. You must remove all system usages of the interface before it can be deleted from your configuration. 3-26

77 Configuring Destinations Configuring a DCM System 3 A destination is a location where DCM will deliver transactions. When you create a destination, you are creating a location where DCM can route transactions. Each destination you create must be given a unique name and must be based on an existing device or on a database, application, or terminal emulation interface. Before DCM can send transactions to a destination, you need to create a route. The route establishes a relationship between a transaction ID and one or more destinations. The next section, Configuring a Transaction ID, describes how to create a route. To add a destination 1. From the Setup menu, choose Destinations. The Destination List dialog box appears. Connections This button allows you to configure network parameters for remote user application destinations. For more information, refer to Configuring Network Connections later in this chapter. 2. From the Destination List dialog box, choose Add. 3-27

78 DCM for HP-UX User s Manual The Destination Parameters dialog box appears. This dialog box contains the following fields and buttons: Name Enter the physical name of the destination (up to 16 characters). Interface type Use this field to specify the interface type you are associating with this destination: User Application or Terminal Emulation. Network info This button allows you to set up the network parameters for a receive server application program. It is available only for User Application interface types in order to set up TCP/IP communication with a remote application. Refer to Configuring a Receive Server Destination for more information. Interface name Choose the down arrow to display a list of available interface names to associate with this destination. 3-28

79 Configuring a DCM System 3 List Selecting this button opens one of the following dialog boxes based on the interface type: Interface Type Database User Application Terminal Emulation Dialog Box Database Interface List Application Interface Terminal Emulation Interface List From these dialog boxes you can add, edit (change), or delete the appropriate interface types. Hot Standby timeout Enter the timeout period (in seconds) you want DCM to wait for a response from the destination before it writes the transactions to disk. Transactions held in volatile memory by DCM Enable one of the following radio buttons to specify how you want DCM to handle an application s transactions: None Any transaction that is not immediately acknowledged by the application is written to the hot standby file. No transactions are held in the application s auxiliary channel. If a system failure occurs, no transactions will be lost. Unlimited DCM holds all transactions for the application in memory (the application s auxiliary channel) unless the application times out. If this occurs, DCM writes the contents of the auxiliary channel to the hot standby file. This is the fastest mode; however, if a system failure occurs, any data held in memory will be lost. Maximum Enter the number of transactions you want DCM to be able to hold in an application s auxiliary channel before it will write the contents of the channel to disk if the application times out or the number of transactions you specify for the channel is exceeded. 3. Choose OK. 3-29

80 DCM for HP-UX User s Manual Editing a Destination 1. From the Destination List dialog box, do one of the following: Select the destination you want and choose Edit. Double-click the destination you want to edit. The Destination Parameters dialog box appears. 2. Edit the information in the fields. 3. Choose OK. Deleting a Destination 1. From the Destination List dialog box, select the destination you want and choose Delete. A message box appears. 2. Choose Delete. Note: You may see a message informing you that the destination is associated with a transaction ID. You must remove this association before the destination can be deleted from your configuration. Configuring a Receive Server Destination If the destination you are configuring is a remote application that acts as a receive server, you can use the Destination Parameters dialog box to configure DCM to initiate the network connection. Note: In most instances you will also want to configure a send server connection for the remote application so it can send information to DCM. For more information on configuring this type of connection, refer to Configuring Network Connections later in this chapter. 3-30

81 Configuring a DCM System 3 To configure a receive server connection for a destination 1. From the Destination Parameters dialog box, choose Network info. The Destination Network Information dialog box appears. This dialog box contains the following fields: Protocol The default protocol for UNIX systems is TCP/IP. Host name Enter the name of the host machine. On UNIX systems, the host name is defined in the /etc/hosts file. You may also use the straight IP address of the host, which has the form xxx.xxx.xxx.xxx. Port The port number that the remote application uses to open a socket and listen on in order to complete the network connection. The range of the port number is 0 to Choose OK to return to the Destination Parameters dialog box. 3-31

82 DCM for HP-UX User s Manual Configuring Network Connections When you configure a network connection in Conman, the information you specify pertains to the remote application. DCM uses this information to determine the network connections it needs to initiate in order to communicate with the remote application. For an understanding of the ways remote applications can interact with DCM, refer to Creating Remote TCP/IP Applications in Chapter 3, Creating Applications, of the DCM for HP-UX Reference Manual. To add a network connection 1. Do one of the following: From the Setup menu, choose Network and then choose Connections. From the Destination List dialog box, choose Connections. The Network Connection List dialog box appears. 2. Choose Add. 3-32

83 Configuring a DCM System 3 The Network Connection dialog box appears. This dialog box contains the following fields: Protocol The default protocol for UNIX systems is TCP/IP. Remote connection Enter the type of connection the remote application will establish: receive server, send server, or send/receive requester. Choose the down arrow to select the connection type from the list. Note: The fields in the Connection Parameters box change according to the parameters you set in the Protocol and Remote connection fields. The following table shows the field information that is required based on the network connection you are configuring. 3-33

84 DCM for HP-UX User s Manual Remote Connection Receive Server and Send Server Connection Parameters Host name The name of the host machine. On UNIX systems, the host name is defined in the /etc/hosts file. You may also use the straight IP address of the host, which has the form xxx.xxx.xxx.xxx. Port The port number that the remote application uses to open a socket and listen on in order to complete the network connection. The range of this port number is 0 to Destination The destination name you want to associate with the receive server connection. Click the down arrow to choose the destination you want from a list of configured User Application type destinations. Add If you need to configure a new destination for your receive server connection, choose Add to access the Destination Parameters dialog box. Refer to Configuring Destinations earlier in this chapter for more information on using this dialog box. Note: The Destination field and the Add button only apply to receive server connections. Send/Receive Requester Send port The port number that the remote application opens a socket on to establish a send connection. The application uses this connection to send data to DCM. The range of this port number is 0 to and it must be different than the receive port number. Receive port The port number that the remote application opens a socket on to establish a receive connection. The remote application uses this connection to receive data from DCM. The range of this port number is 0 to and it must be different than the send port number. 3. Choose OK. 3-34

85 Configuring a DCM System 3 Editing a Network Connection 1. From the Network Connection List dialog box, do one of the following: Select the network connection you want and choose Edit. Double-click the network connection you want to edit. The Network Connection dialog box appears. 2. Edit the fields you want to change in the Connection Parameters box. 3. Choose OK. Deleting a Network Connection 1. From the Network Connection List dialog box, select the network connection you want and choose Delete. A message box appears. 2. Choose Delete to remove the network connection from your configuration. Specifying Network Connection Preferences The Network Connection Preferences dialog box is used to provide general tuning parameters that apply to all NetComm connections for each network connection type. To specify network connection preferences 1. From the Setup menu, choose Network. 2. From the Network menu, choose Preferences. The Network Connection Preferences dialog box appears. 3-35

86 DCM for HP-UX User s Manual This dialog box contains the following fields: Network retries The number of times you want a requester NetComm to attempt to establish a network connection. This value is required and can be any whole number from -1 (forever) to Network retry timeout The amount of time in seconds you want a requester NetComm to wait between each connection retry attempt. This value is required and can be from 0 to 64,000. Max connections The maximum number of connections you want a single NetComm to manage. This value is required and can be any real number from 1 to 256. Padding character The character you want stripped from the end of a data stream sent from the remote application. Click the down arrow to select the character from a list. This field is optional. 3. Choose OK. Configuring a Transaction ID There are two types of data transactions: those that contain a name in the destination field of the transaction header and those that contain a transaction ID. The message handler uses either the destination name or the transaction ID to route a data transaction to its appropriate destination(s). The transaction ID is used only if the destination name is not present in the transaction header. For transactions that contain a transaction ID, you use Conman to define the transaction ID and to configure the data portion of the transaction for that ID. You also associate destination(s) to a transaction ID so DCM knows where to route the transaction that contains that ID. This operation is referred to as defining a route. 3-36

87 Configuring a DCM System 3 To access the Transaction ID List dialog box From the Setup menu, choose Transactions. The Transaction ID List dialog box appears. Specifying the System Delimiter The system delimiter is a single character that only the DevComms use to locate the end of the transaction ID in a transaction sent from a station. When the DevComm receives the transaction, it removes the transaction ID from the data and places it in the header of the transaction that it forwards to the message handler. The default system delimiter is a comma (,). Note: Before configuring transactions, set the transaction ID system delimiter. If you change this delimiter after audit files and transaction files have been created, you will invalidate the transactions that already exist in the audit files. To specify transaction ID options 1. From the Setup menu, choose Transactions. You see the Transaction ID List dialog box. 2. Choose Options. 3-37

88 DCM for HP-UX User s Manual The Options for all Transactions dialog box appears. This dialog box contains the following fields: Transaction ID delimiter Type or choose the character you want the message handler to use as the system delimiter for the transaction ID. The default character is a comma (,). This delimiter is used by the DevComms to separate the transaction ID from the data in a transaction. Bad transaction ID response Type the response you want the DevComm to send to the device that originates an invalid transaction ID. This field can hold a maximum of 39 characters and is optional. An invalid transaction is one that is not defined in the DCM system. This response is used systemwide. 3. Choose OK. 3-38

89 Configuring a DCM System 3 Adding a Transaction ID 1. From the Transaction ID List dialog box, choose Add. The Add Transaction ID dialog box appears. This dialog box contains the following fields and buttons: ID name Enter a unique name for the transaction ID. Note: Because of conflicts with Intermec controller control codes, transaction ID names cannot start with the following characters: SS, SQ, US, UT, or EG. Fields are Enable the appropriate radio button to define the transaction fields as follows: Fixed length DCM locates fields based on their size and location within a transaction. When a transaction is configured with fixed length fields, the fields within the transaction can overlap. Delimited DCM locates fields in the transaction by the field number based on the transaction delimiter you specify. Field numbers start at one and the transaction delimiter is specific to this transaction ID, which can be different than the system delimiter. The default delimiter character is a comma (,). You can choose the down arrow to display a list of appropriate characters. Hot Standby message Enter the message you want DCM to send to the target destination(s) if they time out. This field is optional. 3-39

90 DCM for HP-UX User s Manual 2. Choose Add. The Transaction Parameters dialog box appears. Defining and Editing Transaction Fields The Define Fields button allows you to add, edit, or delete the characteristics of the data fields in the transaction for a particular transaction ID. Field definitions are required if you want DCM to perform one or more of the following operations: Validate transaction fields against a database or a file Read Information from a database table Write information into a database table Update information in a database table Delete information from a database table 3-40

91 Configuring a DCM System 3 To define or edit a transaction field 1. From the Transaction Parameters dialog box, choose Define fields. The Field Definitions for Transaction dialog box appears. 2. Do one of the following: Choose Add. Select the transaction field you want and choose Edit. Double-click the transaction field you want to edit. The Field Definition Parameters dialog box appears. 3-41

92 DCM for HP-UX User s Manual This dialog box contains the following fields: Name Enter a name for the transaction field. Number The order or position (1st, 2nd, 3rd, etc.) of the field in the transaction. Fields start at one (1). If your transaction fields are fixed length (specified in the Transaction Parameters dialog box), the following fields are displayed in place of the Number field: Offset The character offset value for the field (starting at zero). Length The character length of the field. Note: Transaction fields that are fixed length can overlap one another. Data type Choose one of the following data types from the list box: Character, Numeric, Date, Time, or Time Stamp. 3. Choose OK to save the information and return to the Field Definitions for Transaction dialog box. Deleting a Transaction Field 1. From the Field Definitions for Transaction dialog box, select the field name you want and choose Delete. A message box appears. 2. Choose Delete to remove the field definition from your configuration. 3. If the fields in your transaction are delimited, choose Renumber to have Conman automatically renumber the transaction fields. You see the message: Field numbering cannot be undone. Continue? 4. Choose Continue to have the transaction fields renumbered. 5. Choose Close to return to the Transaction Parameters dialog box. Validating Transaction Fields DCM can validate transaction field data against a file, a numeric range, or a database. Validation may be performed on one or more fields in a transaction. DCM performs the validation process before it determines the destination(s) where the transaction is to be sent. Transactions that fail validation are always written to the audit file. 3-42

93 Configuring a DCM System 3 To configure data validation for transaction fields 1. From the Field Definitions for Transaction dialog box, select the field name you want. 2. Choose Validate. The Field Validation Parameters dialog box appears. This dialog box contains the following fields and buttons: Name A static field that identifies the transaction field you want to validate. Data type A static field that identifies the data type of the transaction field. Remove Choose this button to remove a transaction field from being validated. All validation parameters are discarded. 3-43

94 DCM for HP-UX User s Manual 3-44 Range Enable this radio button to check the field against one of the following ranges: numeric, date, time, or timestamp. Define the validation limits of the range in the from and through fields, where the through value must be greater than or equal to the from value. Below the from and through edit fields is additional information that is specific to the data type of the field being validated. For a numeric range, you must enable the radio button that specifies the number type; either Integer or Floating Point. For date, time, or timestamp ranges, you must specify your values in the following formats respectively: YYYY-MM-DD, hh:mm:ss, or YYYY-MM-DD hh:mm:ss. Database Enable this radio button to check the field against a database entry. You must specify the database interface name, table, and column to define the comparison for the validation. interface Identifies the database interface. Choose the down arrow to select from a list of available database interface names configured in the system. Databases Choose this button to modify a database interface or to add a new database interface. The Database Interface List dialog box appears. Fill lists Choose this button if you want Conman to query the database system to obtain the names of the tables and columns available in the database. This process may take some time to complete depending on the size and the location of your database and the speed of the host system. table Identifies the table in the database that the information is validated against. You can type the table name or use the down arrow to list the database tables if you chose the Fill lists button. column Identifies the column in the database table that the information is validated against. You can type the column name or use the down arrow to list the table columns if you chose the Fill lists button. File Enable this button to validate the field against a file. The records in the file do not need to be sorted or fixed length. interface Identifies the file interface. Choose the down arrow to select from a list of available file interface names configured in the system. Files Choose this button to modify a file interface or to add a new file interface. The File Interface List dialog box appears.

95 Configuring a DCM System 3 Valid if This designates whether the data is valid if it is included in or excluded from the validation conditions (range, database, or file). Response if invalid Enter the response you want returned to any device originating data that failed DCM s validation process. This field is optional. 3. Choose OK. Selecting a Destination for a Transaction ID When you are setting up transactions, you need to specify where you want the transaction sent. DCM allows a transaction to be sent to more than one destination. To select a destination for a transaction ID 1. From the Transaction Parameters dialog box, choose Destinations. The Select Destination dialog box appears. This dialog box contains the following fields and buttons: Add To add a destination to the Selected list box, do one of the following: Select the destination you want in the Available list box and choose Add. Double-click the destination you want in the Available list box. All destinations added to the Selected list box are removed from the Available list box. Remove To remove a destination from the Selected list box, do one of the following: Select the destination you want in the Selected list box and choose Remove. Double-click the destination you want in the Selected list box. 3-45

96 DCM for HP-UX User s Manual All destinations removed from the Selected list box are returned to the Available list box. Destinations Choose this button to display the Destination List dialog box in order to add, edit, or delete destinations. 2. Choose OK. Configuring Database Operations When you specify a database destination for a transaction ID, you have four operations you can perform: Reads allow you to read information in a database table and map that information to an output transaction that is routed to the sending device or application or by transaction ID. Inserts allow you to add new information to a database table. Updates allow you to update (change) existing information in a database table. Deletes allow you to remove information from a database table. Note: A database insert operation is not the same as a database update operation. If you repeatedly insert the same record into a database, the database engine will insert duplicate copies of the record into the database assuming that the table and row constraints allow it. Configuring Database Reads The database read capability of DCM allows you to set up input and output transaction IDs that are used to read information from a database. The input transaction ID tells DCM to perform the read using its transaction fields as the read conditions. The results of the database read operation are placed into an output transaction based on the fields you define for the output transaction ID. When you configure a database read, define the fields for the output transaction ID first and then set up the input transaction ID to initiate the read operation. 3-46

97 Configuring a DCM System 3 Setting Up an Output Transaction ID 1. From the Setup menu, choose Transactions. 2. From the Transaction ID List dialog box, choose Add. 3. From the Add Transaction ID dialog box, enter an ID name and specify if the fields in the output transaction are fixed length or delimited. 4. Choose Add. 5. From the Transaction Parameters dialog box, choose Define fields. 6. From the Field Definitions for Transaction dialog box, choose Add. 7. Define the fields for the output transaction ID. These fields will contain the values read from the database columns. Note: It is important that you are familiar with the information you are reading in the database columns. You need to know the length (number of characters) and the data type of the information in each column you want to read so you can define the output transaction fields properly. 8. When you have finished configuring the fields for the output transaction ID, close all dialog boxes until you return to the Transaction ID List dialog box. You are now ready to configure the input transaction ID for the database read operation. Setting Up an Input Transaction ID 1. From the Setup menu, choose Transactions. 2. From the Transaction ID List dialog box, choose Add. 3. From the Add Transaction ID dialog box, enter an ID name and specify if the fields in the input transaction are fixed length or delimited. 4. Choose Add. 5. From the Transaction Parameters dialog box, choose Define fields. 6. From the Field Definition for Transaction dialog box, choose Add. 3-47

98 DCM for HP-UX User s Manual 7. Define the fields for the input transaction ID. These fields specify what information you want to read in the database columns. Note: It is important that you are familiar with the information you are reading in the database columns. You need to know the data type of each column you intend to use for the read condition so you can define the input transaction fields properly. 8. When you have finished configuring the fields for the input transaction ID, return to the Transaction Parameters dialog box. 9. Choose Destinations. 10. From the Select Destination dialog box, specify a database destination for the input transaction ID and then choose OK. Selecting the Output Transaction ID and Specifying the Database Tables You Want to Read 1. From the Transaction Parameters dialog box for the input transaction ID you are using for the read operation, choose Field usage. The first time you choose the Field usage button for a transaction ID, the Select Database Operation dialog box appears. 2. Select Read and choose OK. Note: Once you select a database operation for a transaction ID, you cannot perform a new database operation with that transaction ID without removing and recreating the transaction ID. The Select DB Read Output Transaction dialog box appears. 3-48

99 Configuring a DCM System 3 3. Choose the down arrow to select the output transaction ID for the read operation and then choose OK. The Database Tables Accessed dialog box appears. This dialog box contains the following buttons and fields: Fill list Choose this button if you want Conman to query the database system to obtain the names of the tables available in the database and display them in the Table name list box. This process can take some time to complete depending on the size and location of your database. Table name Enter the name of the database table you want the input transaction ID to access. If you chose the Fill list button, you can click the down arrow to select a table name from the list. You may also access the database tables of another owner for this database interface by entering owner name.table name, where owner name is the user ID associated with this database interface and table name is the name of the database table you want to access. Note: You cannot use the Fill list button to provide the table names of a different owner. Add Choose this button to add the table name to the Selected Tables list box. Remove Select a table name in the Selected Tables list box and then choose this button to remove the table from being accessed by the input transaction ID. 3-49

100 DCM for HP-UX User s Manual 4. Choose Close when you have finished adding and/or removing database tables. Note: You must choose a table for the input transaction ID to access or the database operation will be discarded and you will be returned to the Transaction Parameters dialog box. The Database Read Field List dialog box appears. This dialog box contains the following fields and buttons: Database interface This is a static field that displays the name of the database interface you have associated with the read operation. Input transaction ID This is a static field that displays the name of the input transaction ID you are using for the read operation. Output transaction ID This is a static field that displays the name of the output transaction ID you are using for the results of the read operation. Route to originator This is a static field that indicates if the output transaction is being routed to the destination that originated the database read input transaction. 3-50

101 Configuring a DCM System 3 Tables accessed Choose this button to open the Database Tables Accessed dialog box. From this dialog box you control what tables are read by the input transaction. Read conditions Choose this button to access the Database Conditions List dialog box in order to define or edit the number of rows that the read operation will affect. For more information on defining the conditions of a database read operation, refer to page 3-66, Defining Conditions for a Database Operation. Note: If you do not define any conditions for a read operation, DCM will read every row in every table you have selected. Output information Choose this button to access the Database Read Output Information dialog box. From this dialog box you can specify a new output transaction ID for the read results, routing the output transaction ID to the originator of the input transaction ID, and the amount and order of the returned data. Options This button accesses the Transaction Handling Options dialog box so you can configure handshaking options between the database server and a destination. Refer to page 3-70, Configuring Database Server Handshaking, for more information. Defining Field Mappings for the Read Results Based on the conditions you defined for the database read operation, you need to provide DCM with the information you want placed in the output transaction. To add output transaction field mappings 1. From the Database Read Field List dialog box, choose Add. The Database Read Field Mapping dialog box appears. 3-51

102 DCM for HP-UX User s Manual This dialog box contains the following fields and buttons: Fill lists Choose this button if you want Conman to query the database system to obtain the names of the tables and columns available in the database. This process can take some time to complete depending on the size and location of your database. Table Enter the name of the database table that contains the column you are mapping to the output transaction field. You can choose the down arrow to select this name from a list if you chose the Fill lists button. You may also access the database tables of another owner for this database interface by entering owner name.table name, where owner name is the user ID associated with this database interface and table name is the name of the database table you want to access. Note: You cannot use the Fill list button to provide the table names of a different owner. Column Enter the name of the database column you are mapping to the output transaction field. You can choose the down arrow to select this name from a list if you chose the Fill lists button. Name The name of the output transaction field. Choose the down arrow to select this name from the list. Data type This is a static field that displays the data type of the transaction field you selected. 2. Choose OK. 3-52

103 Configuring a DCM System 3 3. Repeat Steps 1 and 2 to add another read field. Editing Output Transaction ID Field Mappings 1. From the Database Read Field List dialog box, do one of the following: Select a read field in the output field list box and choose Edit. Double-click a read field in the output field list box. 2. From the Database Read Field Mapping dialog box, you can edit the database table and column name and the transaction field name. 3. Choose OK after making your changes to return to the Read Field List dialog box. Deleting Output Transaction Field Mappings 1. From the Database Read Field List dialog box, select a field in the Read field list box and choose Delete. You see the message: Are you sure you want to delete table.column name from the list? 2. Choose Delete to remove the field from the output transaction. Specifying Output Information The Output information button in the Database Read Field List dialog box allows you to control the information returned from the input transaction. You can: Specify a new output transaction ID for the read results. Route the output transaction(s) containing the read results to the destination that originated the input transaction ID. Control the amount and order of the returned data. Since a database read can result in more than one row of returned data, you can specify how many rows of data (one per output transaction) are returned from a database read. The default action is to return all rows that were read; however, some applications or reader programs may not be able to handle more than one row of returned data. 3-53

104 DCM for HP-UX User s Manual To specify output information 1. From the Database Read Field List dialog box, choose Output information. The Database Read Output Information dialog box appears. This dialog box contains the following fields and buttons: Output transaction ID This field displays the output transaction ID you have associated with this read operation. You can choose the down arrow to select a different output transaction ID. Route to originator only This check button affects the destination of the output transaction created by the database server as follows: If you disable this option, the database server only places the output transaction ID in the header of the output transaction. The destination field in the transaction header is blank. The message handler determines where to route transactions that contain this output transaction ID based on destinations you have set up for it in the Transaction Parameters dialog box. Note: If you want to specify the destination(s) for the output transaction, you may do so after you have configured the database read operation. Refer to Selecting a Destination for a Transaction ID earlier in this chapter for more information. When this option is enabled (default), the output transaction is sent to the destination that originated the input read transaction. The database server accomplishes this routing by placing the name of the device or application that requested the read in the destination field of the output transaction header. Note: If the handshaking option is enabled in the Transaction Handling Options dialog box, the Route to originator only check button is automatically enabled and cannot be accessed. 3-54

105 Configuring a DCM System 3 Transactions returned Enable one of the following options: All Returns all the rows of data that were read. First only Returns only the first row of data that was read. 2. Choose Sort order to access the DB Read Transaction Sort Order dialog box. This dialog box allows you to specify the order of output transactions when the database read returns more than one transaction or to determine which database row is returned in the first transaction. You add or remove output fields as follows: Add To add an output field to the Selected list box, do one of the following: Select the table.column name you want in the Available Columns list box and choose Add. Double-click the table.column name you want in the Available Columns list box. All columns added to the Selected list box are removed from the Available Columns list box. 3-55

106 DCM for HP-UX User s Manual Remove To remove an output field from the Selected list box, do one of the following: Select the table.column name you want in the Selected list box and choose Remove. Double-click the table.column name you want in the Selected list box. All columns removed from the Selected list box are returned to the Available Columns list box. 3. Make sure that the table.column names in the Selected list box are in the order you want them. By default, all table.column names mapped to the output transaction are sorted in ascending order where the first entry in the list is the primary sort key, the second entry is the secondary sort key, and so on. To change the sorting order, select a table.column name in the Selected list box and enable the Ascending or the Descending radio button. 4. Choose OK to return to the Database Read Field List dialog box. Setting Up Read Conditions You can set up conditions in order to limit the number of rows read by the database read operation. The condition statement is made up of individual condition clauses that you define, one at a time, through the Condition Clause Parameters dialog box. The condition statement is complete after you define all the individual condition clauses. Note: You are not required to define any read conditions. However, if no conditions are defined, every row in the table(s) will be read by the database read operation. For more information on setting up conditions for a database read operation, refer to page 3-66, Defining Conditions for a Database Operation. 3-56

107 Configuring a DCM System 3 Configuring Database Inserts (Writes) DCM s database insert capability allows you to set up transaction fields that are written into a database table. To configure a database insert 1. Create an input transaction ID for the database insert operation. Refer to page 3-47, Setting Up an Input Transaction ID, for more information. 2. From the Transaction Parameters dialog box, choose Field usage. The first time you choose the Field usage button for a transaction ID the Select Database Operation dialog box appears. 3. Select Insert and choose OK. Note: Once you select a database operation for a transaction ID, you cannot perform a new database operation with that transaction ID without deleting and recreating the transaction ID. The Database Insert Field List dialog box appears. This dialog box contains the following fields and buttons: Transaction ID This is a static field that displays the name of the input transaction ID you are using for the insert operation. Database interface This is a static field that displays the name of the database interface associated with the insert operation. 3-57

108 DCM for HP-UX User s Manual Options This button accesses the Transaction Handling Options dialog box so you can configure handshaking options between the database server and a destination. Refer to page 3-70, Configuring Database Server Handshaking, for more information. 4. Choose Add. The Database Insert Field Mapping dialog box appears. This dialog box contains the following fields and buttons: Name Enter the name of the transaction field that contains the value you want to insert in the database column. You can click the down arrow to display a list box of available transaction field names. Data type This is a static field that displays the data type of the transaction field you selected. Fill lists Choose this button if you want Conman to query the database system to obtain the names of the tables and columns available in the database. This process can take some time to complete depending on the size and location of your database. Table Enter the name of the database table where you are mapping the transaction field value. If you chose the Fill lists button, you can click the down arrow to select the table name from the list box. 3-58

109 Configuring a DCM System 3 You may also access the database tables of another owner for this database interface by entering owner name.table name, where owner name is the user ID associated with this database interface and table name is the name of the database table you want to access. Note: You cannot use the Fill list button to provide the table names of a different owner. Column Enter the name of the database column where you are mapping the transaction field value. If you chose the Fill lists button, you can click the down arrow to select the column name from the list box. Note: Conman provides data type compatibility between transaction fields and database columns as follows: any transaction field containing the key word getdate(), CURRENT, or sysdate that has a data type of date, time, or timestamp can be mapped to a database column with one of these three data types. 5. Choose OK. 6. Repeat Steps 4 and 5 to add another insert field to the input transaction. 7. From the Database Insert Field List dialog box, choose Close to return to the Transaction Parameters dialog box. Editing Input Transaction ID Field Mappings 1. From the Database Insert Field List dialog box, do one of the following: Select a field in the Insert field list box and choose Edit. Double-click a field in the Insert field list box. 2. From the Database Insert Field Mapping dialog box you can edit the transaction field name and the database table and column names. 3. Choose OK after making your changes. 3-59

110 DCM for HP-UX User s Manual Deleting Input Transaction ID Field Mappings 1. From the Database Insert Field List dialog box, select a field in the Insert field list box and choose Delete. You see the message: Are you sure you want to delete table.column name from the list? 2. Choose Delete to remove the field from the input transaction mapping. Configuring Database Updates DCM s update capability allows you to set up fields in a transaction that are used to locate and update existing rows of information in a database table. You will usually want to define a set of conditions that specify which rows in the database table DCM will update. Only one table can be modified per input transaction ID. To configure a database update operation 1. Create an input transaction ID for the database insert operation. Refer to page 3-47, Setting Up an Input Transaction ID, for more information. 2. From the Transaction Parameters dialog box, choose Field usage. The first time you choose the Field usage button for a transaction ID, the Select Database Operation dialog box appears. 3. Select Update and choose OK. Note: Once you select a database operation for a transaction ID, you cannot perform a new database operation with that transaction ID without deleting and recreating the transaction ID. The Select Single Table dialog box appears. 3-60

111 Configuring a DCM System 3 4. Enter the name of the database table you want the input transaction ID to access. If you choose the Fill list button, you can click the down arrow to select the table name from the list box. 5. Choose OK. The Database Update Field List dialog box appears. This dialog box contains the following fields and buttons: Transaction ID This is a static field that displays the name of the input transaction ID you are using for the update operation. Database interface This is a static field that displays the name of the database interface you associated with the update operation. Database table This is a static field that displays the name of the database table you want to update. You defined this table in the Select Single Table dialog box. Update conditions This button accesses the Database Conditions List dialog box so you can define a set of conditions that specify which rows in the table DCM will update. Choose table This button accesses the Select Single Table dialog box in order to select a different table to update. Options This button accesses the Transaction Handling Options dialog box so you can configure handshaking options between the database server and a destination. Refer to page 3-70, Configuring Database Server Handshaking, for more information. 3-61

112 DCM for HP-UX User s Manual 6. From the Database Update Field List dialog box, choose Add. The Database Update Field Mapping dialog box appears. This dialog box contains the following fields and buttons: Name Enter the name of the input transaction field. Click the down arrow to select this name from the list box. Data type This is a static field that displays the data type of the transaction field you selected. Note: Conman provides data type compatibility between transaction fields and database columns as follows: any transaction field containing the key word getdate(), CURRENT, or sysdate that has a data type of date, time, or timestamp can be mapped to a database column with one of these three data types. Table This is a static field that displays the name of the database table you are updating. This information was specified in the Select Single Table dialog box. Fill list Choose this button if you want Conman to query the database system to obtain the names of the columns in the database table you are updating. Column Enter the name of the database column you are mapping to the input transaction field. You can click the down arrow to select this name from the list box after choosing the Fill lists button. 3-62

113 Configuring a DCM System 3 Note: You do not need to map all of the transaction fields to database columns. You only map the fields used to update the database. Some fields are used in the update condition statement to specify which rows will be updated. 7. Choose OK. 8. Repeat Steps 6 and 7 to add another update field. 9. From the Database Update Field List dialog box, choose Update conditions to define the number of rows that the update operation will affect. For more information on defining the conditions of a database update operation, refer to page 3-66, Defining Conditions for a Database Operation. Note: If you do not define any conditions for an update operation, DCM will update every row in the table. 10. From the Update Field List dialog box, choose Close to complete the setup of the update operation. Editing Input Transaction ID Field Mappings 1. From the Database Update Field List dialog box, do one of the following: Select a field in the Update field list box and choose Edit. Double-click a field in the Update field list box. 2. From the Database Update Field Mapping dialog box, you can edit the transaction field name and the database column name. 3. Choose OK after making any necessary changes to return to the Update Field List dialog box. Deleting Input Transaction ID Field Mappings 1. From the Database Update Field List dialog box, select a field in the Update field list box and choose Delete. You see the message: Are you sure you want to delete table.column name from the list? 2. Choose Delete to remove the field mapping from the input transaction ID. 3-63

114 DCM for HP-UX User s Manual Setting Up Conditions for the Update Operation You can set up conditions in order to limit the number of rows update by the database update operation. The condition statement is made up of individual condition clauses that you define, one at a time, through the Condition Clause Parameters dialog box. The condition statement is complete after you define all the individual condition clauses. Note: You are not required to define any update conditions. However, if no conditions are defined, every row in the table will be updated by the database operation. For more information on setting up conditions for an update operation, refer to page 3-66, Defining Conditions for a Database Operation. Configuring Database Deletes DCM s database delete capability allows you to set up input transaction fields that locate rows in a database table and remove them. You may define a set of conditions that provide DCM with the information as to which rows to delete. Only one table can be modified per transaction ID. To configure database deletes 1. Create an input transaction ID for the delete operation. Refer to page 3-47, Setting Up an Input Transaction ID, for more information. 2. From the Transaction Parameters dialog box, choose Field usage. The first time you choose Field usage for a transaction ID, the Select Database Operation dialog box appears. 3. Select Delete and choose OK. Note: Once you select a database operation for a transaction ID, you cannot perform a new database operation with that transaction ID without removing and recreating the transaction ID. The Select Single Table dialog box appears. 4. Enter the name of the database table you want. If you choose the Fill list button, you can click the down arrow to select the table name from the list box. 5. Choose OK to display the Database Row Delete dialog box. 3-64

115 Configuring a DCM System 3 This dialog box contains the following fields and buttons: Transaction ID This is a static field that displays the name of the input transaction ID you are using for the delete operation. Database interface This is a static field that displays the name of the database interface you have associated with the delete operation. Database table This is a static field that displays the name of the database table you have selected for the delete operation. You defined this table in the Select Single Table dialog box. Delete conditions This button accesses the Database Conditions List dialog box so you can define a set of conditions that specify which rows in the table DCM will delete. Choose table This button accesses the Select Single Table dialog box so you can select a different table for the delete operation. Options This button accesses the Transaction Handling Options dialog box so you can configure handshaking options between the database server and a destination. For more information, refer to page 3-70, Configuring Database Server Handshaking. 6. Choose Delete conditions to define the number of rows that the delete operation will affect. For more information on defining the conditions of a delete operation, refer to the following section, Defining Conditions for a Database Operation. Note: If you do not define any conditions for the delete operation, DCM will delete every row in the database table. 7. From the Database Row Delete dialog box, choose Close to complete the setup of the delete operation. 3-65

116 DCM for HP-UX User s Manual Setting Up Conditions for a Delete Operation You can set up conditions to limit the number of rows deleted by a database delete operation. The condition statement is made up of individual condition clauses that you define in the Condition Clause Parameters dialog box. For more information on setting up conditions for a delete operation, refer to the next section, Defining Conditions for a Database Operation. Note: You are not required to define any delete conditions. However, if no conditions are defined, every row in the table will be deleted by the database operation. Defining Conditions for a Database Operation You can set up conditions that affect DCM s database operations. The purpose of setting up conditions is to limit the number of rows that an operation will affect. The condition statement is made up of individual condition clauses that you define, one at a time, using Conman. The condition statement is complete after you define all the individual condition clauses. Note: You are not required to define conditions, but this will cause the database operation to affect every row in a table. The Database Condition List dialog box allows you to manipulate the individual condition clauses that make up a condition statement. In the condition statement you create, each condition clause is displayed on a separate line as shown in the following example: EMP.DEPTNO = field[dept_num] AND EMP.JOB = 'CLERK' AND EMP.SAL >= AND EMP.DEPTNO = DEPT.DEPTNO A condition clause contains a left operand, a comparison operator, and a right operand. All clauses, other than the first one, also contain a logical operator (AND or OR) that links it to the previous clause. The left operand is always a database table name and a column name, but the right operand can be an input transaction field, a static value, or another table and column name. 3-66

117 Configuring a DCM System 3 The following table shows the format of the left and right operands and the database operations that can use them. Left Operand Right Operand Database Operation table name.column name table name.column name field[field name] where field name is the name of the input transaction field nnn or nnn where nnn (enclosed in single quotes) is a character or date value and nnn is a numeric value Read, Update, and Delete Read, Update, and Delete table name.column name table name.column name Read When the right operand is a field from an input transaction, DCM uses information from the input transaction to limit the scope of the database operation. This is the most common way to have data from a transaction affect a database operation. When the right operand is a static value, DCM compares the information from the database to the static value that you enter in the Condition Clause Parameters dialog. This static value will be used in the comparison every time DCM performs a database operation using this transaction ID. Having a table and column name pair as the right operand can only be used in a database read operation, as it forces DCM to perform a joined read where information from two different tables is being compared. You can join as many tables as you want, but the data type of the columns that are being compared must be the same and you must enter the tables being used in the comparison in the Tables Accessed dialog box. If you choose more than one table in the Tables Accessed dialog box, but do not limit the scope of the read operation with a join in the condition statement, the result of the read will be a table product. For information on joined reads and table products, consult your database documentation. 3-67

118 DCM for HP-UX User s Manual To define database conditions 1. Do one of the following: From the Database Read Field List dialog box, choose Read conditions. From the Database Update Field List dialog box, choose Update conditions. From the Database Delete Row dialog box, choose Delete conditions. The Database Condition List dialog box appears. 2. Choose Add. The Condition Clause Parameters dialog box appears. 3-68

119 Configuring a DCM System 3 This dialog box contains the following fields and buttons: Logical operator Choose the down arrow to select one of the following logical operators: AND or OR. This field is unavailable if you are specifying the first condition clause. Fill columns Choose this button if you want Conman to query the database system to obtain the names of the columns available in the database. This process may take some time to complete depending on the size and location of your database. Column on left Enter the name of the database column you want to use for the left operand in the condition clause. You can use the down arrow to select this name from the list box after choosing the Fill columns button. Comparison operator Choose the down arrow to select one of the following condition operators: equal, not equal, greater than, less than, greater than or equal, less than or equal. Right Side of Comparison The information required in this box depends on the right side operand you enable: Transaction Field Choose the edit box down arrow to select an input transaction field name from the list. Static value Enter the value in the Static value edit box and assign it a data type from the edit box to the right. Column Enter the column name. You can use the down arrow to select a column name from a list box after choosing the Fill columns button. Note: The column comparison option is unavailable if you are defining conditions for a database update or delete operation or you are only accessing one table in the database for a read operation. 3. Choose OK. 4. Repeat Steps 2 and 3 to add a new condition clause to the condition statement. 5. When you have finished your condition statement, choose Close in the Database Condition List dialog box. 3-69

120 DCM for HP-UX User s Manual Editing a Database Condition 1. From the Database Condition List dialog box, do one of the following: Select a condition clause in the Conditions list box and choose Edit. Double-click a condition clause in the Conditions list box. 2. From the Condition Clause Parameters dialog box, you can edit the condition clause you selected. 3. Choose OK after making any necessary changes to return to the Database Condition List dialog box. Deleting a Database Condition 1. From the Database Condition List dialog box, select a condition in the Conditions list box and choose Delete. You see the message: Are you sure you want to delete the selected condition from the list? 2. Choose Delete to remove the condition. Configuring Database Server Handshaking The database server handshaking feature allows DCM to send the status of database operations to a destination (device or DCM-compliant application program). When handshaking is enabled, the handshake protocol received from the database server can include: An identifier that lets the receiving program know the type of database operation performed. A sequence identifier echoed from the original transaction. Database server or SQL error codes. Error text. 3-70

121 Configuring a DCM System 3 This feature provides important information about database operations to the destination program. For example, a program running in a reader can send DCM a read transaction in which no records are read from the database. With the database server handshaking feature, this information is communicated to the reader program, informing it that there was no data in the database or that the read operation failed. By enabling the extra protocol information, a destination can always be ensured of a response for every database operation. To enable handshaking options Choose Options from one of the following dialog boxes: Database Insert Field List, Database Read Field List, Database Update Field List, or Database Row Delete. The Transaction Handling Options dialog box appears. This dialog box contains the following handshaking options for transactions sent to a database server: Handshaking Active Enable this check button to have all database operations send a response to the sending program or device, informing it when the operation is complete. The default setting is disabled. Handshaking can be enabled or disabled for each transaction ID with a database destination defined in DCM. Because handshaking increases data integrity, you may want to disable the database server auditing capabilities. Instead of having the database server emit an error and write the errant transaction to a private audit file, you can use the handshaking feature to communicate the status of the database operation to the sending program. 3-71

122 DCM for HP-UX User s Manual If you enable this feature, the Respond to originator check button in the Database Read Field List dialog box is automatically enabled and inactivated so handshaking can occur between a database server and one application program only. Process Batched Enabling this check button causes the database server to process all transactions it receives, independent of their interactivity flag. Disabling this check button causes the database server to discard all batched transactions without performing database operations on them. By default this check button is enabled so that batched transactions are processed. You cannot change this setting unless Handshaking Active is enabled. Batched transactions are those transactions that have been saved in a hot standby file before being delivered to a database server. In previous versions of DCM, the behavior is for batched transactions to be processed as interactive transactions no distinction is made between the two types. In some circumstances, you may want to be working with near real-time data, requiring that only those transactions with an interactive flag set be processed. As a result, batched transactions would be discarded in this case. Skipped Batch Reporting Enabling this check button causes the database server to send a response to the originator of the transaction, informing it that the transaction was ignored because it was previously batched. Disabling this check button causes the database server to silently discard batched transactions without informing the sending application program. By default, this check button is enabled when Processed Batched is disabled. Failure Auditing Enable this check button if you want the database server to write failed database transactions to a private audit file. The database server audit filename (located in the local subdirectory) has the format dest_name.aud, where dest_name is the destination name of the database server. Blank field is a Null Enable this check button to have the database server treat all fixed length transaction fields that contain only blanks as NULL fields. For detailed information on the database server handshaking feature, refer to Chapter 1, Theory of Operation, in the DCM for HP-UX Reference Manual. 3-72

123 Configuring System Parameters Configuring a DCM System 3 The DCM System Parameters dialog box affects the auditing trail and the time synchronization feature. Conman allows you to change the system parameters from two different menus: Setup You can use the Setup menu before starting DCM to set system parameters in a DCM configuration file. This procedure is discussed in this section. Control You can use the Control menu after starting DCM to affect system parameters during runtime. See Controlling DCM System Parameters in Chapter 4. To change DCM system parameters 1. From the Setup menu, choose DCM system operation. The DCM System Operation Setup dialog box appears. 2. Enable the appropriate check buttons to affect time synchronization and/or auditing. 3-73

124 DCM for HP-UX User s Manual Time Synchronization Time synchronization is relevant for Intermec controllers (9154 and 9180 v2.0 only) and Intermec readers. When you enable time synchronization, you allow DCM to transmit the host time, at the time interval you specify, to all controllers and readers directly connected to the system. The time that is sent to a controller is not sent to the individual devices that may be connected to the controller. You must configure your controller to broadcast time to its downline devices (refer to your controller manual). See Appendix A for a description of the portnametbi environment variable that gives you extra control over the format of the time message that DCM sends to a controller. You can synchronize the data collection system time with the time on the DCM system repeatedly or just once. If you want to synchronize the time repeatedly, enable the DCM sends push button and enter the time synchronization interval in minutes. Audit Trail The audit trail is the file dcmaud.dat (located in the audit subdirectory), maintained by the message handler that contains transactions that have been sent to DCM. The transactions can come from the data collection network or they can be sent by application programs (destinations). You can enable or disable DCM s ability to log transactions in the Audit file by setting the check boxes that control this feature. Undeliverable transactions are transactions that contain an invalid transaction ID, destination, or have failed validation. Such transactions are always written to the audit file. There are two kinds of data transactions flowing through a DCM system: (1) those that contain a destination name in the transaction header and (2) those that contain a transaction ID. Transactions that come from a station are always of the second type (transaction ID with no destination). Transactions sent by application programs are typically, but not necessarily, of the first type (destination set in the transaction header). The two push buttons in the audit trail portion of this dialog box refer to these two kinds of transactions. You can tell DCM to log both types of transactions, neither type, or just one type. However, DCM always audits undeliverable transactions. 3-74

125 Configuring a DCM System 3 The DCM System Parameters dialog box also allows you to specify the time of day when you want the audit file renamed. DCM keeps the audit file open while it is running. Renaming it allows you to backup or remove old audit data. The audit file is renamed at the first occurrence of the specified time. For example, if you start DCM at 14:00 with an audit file rename time of 14:10, the audit file will be renamed 10 minutes after DCM starts. Note: If you change the rename time while DCM is running, the new rename time takes effect immediately. When the audit file is renamed, it has the format: yymmddhh.aud where: yy is the year mm is the month dd is the day hh is the hour of the day Note: Maintaining an audit trail for all transactions causes slower response time from DCM and increases disk usage. Remote Startup Enable this check box if you want remote applications to have the capability to start DCM through a connection request by a server NetComm. This feature can only be initiated by the remote application if the message handler is not running. 3. Choose OK. Configuring DCM for Terminal Emulation DCM provides terminal emulation for the DOS-based Intermec JANUS devices (20X0) and Intermec IRL devices (94XX and 95XX). Terminal emulation allows these devices to communicate through DCM to the host system as if they were directly connected to the host. A JANUS device can be configured to act as a VT100, VT220, VT320, or ANSI terminal, while an IRL device emulates a subset of VT100 commands. Intermec devices can communicate with the host system in a variety of ways: through an RF network or a multi-drop controller, or they can directly connect to a serial port on the host system. 3-75

126 * ( DCM for HP-UX User s Manual DCM routes the reader data to the terminal session manager application. The terminal session manager handles the communication between DCM and a Telnet session and returns the data to the Intermec reader in a screen mode format that emulates a host terminal. This process is illustrated in the following figure with the numbers representing the sequence of the data flow. 3-76

127 Configuring a DCM System 3 TE Transaction Routing Process This example shows how DCM routes device data during a terminal emulation session. Data is entered or scanned by the Intermec device and converted by the terminal emulation program it is running to the host terminal format (VT 100/220/320 or ANSI). The transaction is then transmitted to a controller or directly to DCM. In this example, the JANUS reader is directly connected to the DCM host, so its transaction goes directly to the DevComm. The DevComm receives the transaction through its hardware link. A header is attached to the transaction and the transaction is placed in the message handler s data channel (DCM_Q). The message handler retrieves the transaction from its data channel. The message handler determines the correct destination for the transaction and forwards it to the Terminal Session Manager s input channel (TSM). The Terminal Session Manager application reads the transaction from its TSM channel. The transaction is forwarded to Telnet, which sends the transaction to the host terminal just as if the information were entered from the host s keyboard. The response transaction from the host terminal (VT 100/220/320 or ANSI) is sent back to the Terminal Session Manager. The Terminal Session Manager application sends the transaction to the message handler s data channel (DCM_Q). The message handler reads the data transaction from its DCM_Q channel. Since the transaction contains data for the JANUS reader, it is forwarded to the DCD channel. The DevComm reads the data transaction from its DCD channel. The terminal emulation data is sent from the DevComm to the JANUS reader, where it is interpreted and then displayed on the reader s screen. 3-77

128 DCM for HP-UX User s Manual Using Sample Configuration Files to Set Up TE DCM is shipped with several terminal emulation configuration files (te*.cnf), each of which is set up for a different Intermec controller and contains the setup information for communications with Intermec JANUS and IRL devices. All you need to do is use Conman to set the name of the serial port where the Intermec controller is connected and specify which stations to enable or disable. The following template configuration files are available: File Name te9180v2.cnf te9180v1.cnf te9154.cnf te9161.cnf Configuration TE for 9180 v2.x controller TE for 9180 v1.x controller TE for 9154 controller TE for concentrator To set up terminal emulation using sample configuration files 1. From the File menu, choose Open. 2. From the file selection dialog box, select the template configuration file appropriate for your system s configuration and choose OK. 3. From the File menu, choose Save as. 4. Type the new configuration filename in the File Name box and choose OK. You have just made a copy of a template configuration file that can now be modified. 5. From the Setup menu, choose Downline devices. 6. From the Downline Device List dialog box, select the proper device and choose Edit. 7. From the DCM Downline Device dialog box, do any of the following that apply: Specify the name of the serial port in the Connection edit box. Choose Options to set up the connection options for your device. 3-78

129 Configuring a DCM System 3 Each DCM TE configuration file has the controller set up to communicate using 7 data bits and even parity with DCM auditing and time synchronization disabled. Enable the stations that will be running TE. Set the logical name of a station by selecting the station and choosing Edit Station. Note: You will need the logical name of any station that is used for IRL mode TE. The logical name of the station is used when you download the TE IRL program to an IRL device. 8. Choose OK until you return to the Downline Device List dialog box and then choose Close. 9. From the Control menu, choose Start DCM. Note: This step assumes that all Intermec hardware (controller or JANUS device) is connected to the host system. You are now ready to set up an IRL or JANUS device for terminal emulation. Refer to Setting Up an IRL Device for Terminal Emulation or Setting Up a JANUS Device for Terminal Emulation later in this chapter. Creating Your Own Configuration File to Set Up TE Before you configure an Intermec reader for terminal emulation, you need to use Conman to create a configuration file by performing the following tasks: Configure DCM for the device(s) and station(s) running TE. Define a terminal emulation destination. Create a transaction ID. Define a route for the transaction ID to the terminal emulation destination. To configure the device(s) and station(s) running TE 1 From the Setup menu, choose Downline devices. 2. From the Downline Device List dialog box, add the device (direct connect reader) you want to run TE or add an Intermec controller. 3-79

130 DCM for HP-UX User s Manual 3. Edit the new device to access the DCM Downline Device dialog box and do one of the following: If the device is a reader, choose Edit station. If the device is a controller, enable a station address and choose Edit station. 4. From the Station Parameters dialog box, enter the information in the appropriate fields. Do not define any inserted transaction IDs or any positive or negative response strings for any device or station that will be used for terminal emulation. To define a terminal emulation destination 1. From the Setup menu, choose Destinations. 2. From the Destination List dialog box, choose Add. 3. From the Destination Parameters dialog box, define the following field information: Name Enter a destination name. For UNIX systems, the name you enter must be in the /etc/services file. Conman will warn you if the name you specify does not exist. TEJANUS_1 is a good name to use the first time you configure a terminal emulation destination because this name is located in the template services file (services.add) that is provided with DCM. Interface type Select Terminal Emulation. Transactions held in volatile memory Select Unlimited as the number of transactions to hold in volatile memory. 4. Choose List. 5. From the Terminal Interface List dialog box, choose Add. 6. From the Terminal Interface dialog box, do the following: Enter the interface name you want (tejanus_if1 is a good name to use, but it does not matter). Select JANUS as the Emulation type. Choose OK. 7. From the Terminal Interface List dialog box, choose Close. 3-80

131 Configuring a DCM System 3 8. From the Destination Parameters dialog box, choose OK. 9. From the Destination List dialog box, choose Close. Note: For JANUS mode TE, one TE destination can support up to 15 JANUS readers. For IRL mode TE, you must configure a TE destination for each IRL device that will be running terminal emulation. To define a route for the transaction ID to the TE destination 1. From the Setup menu, choose Transactions. 2. From the Transaction ID List dialog box, choose Add. 3. From the Add Transaction ID dialog box, define the following fields: ID name Enter a transaction ID name (tejanus is a good name to use for the first transaction ID). Fields are It does not matter if you choose fixed length or delimited fields since there are no fields to set up for terminal emulation. Hot Standby message Enter a message similar to: TE mgr down - Contact sys admin. 4. Choose Add. 5. From the Transaction Parameters dialog box, choose Destinations. 6. From the Select Destination dialog box, double-click the destination name you defined earlier (TEJANUS_1). This name is added as a target destination route for the transaction ID. 7. Choose OK. 8. From the Transaction Parameters dialog box, choose OK. 9. In the Transaction ID List dialog box, choose Close. Note: For JANUS mode TE you can use one transaction ID to support up to 15 JANUS devices. You can configure a separate transaction ID for each device, but it is not required. For IRL mode TE, you must create a separate transaction ID for each IRL device that will be running terminal emulation. Make sure that each transaction ID is routed to its own TE destination. 3-81

132 DCM for HP-UX User s Manual To save your configuration file and start DCM 1. From the File menu, choose Save or Save as to save the configuration changes you made. 2. From the File menu, choose Use to run DCM to use this configuration file when you start DCM processing. 3. From the Control menu, choose Start DCM. You are now ready to set up an IRL or JANUS device for terminal emulation. Note: This step assumes that all Intermec hardware (controller or JANUS device) is connected to the host system. Setting Up an IRL Device for Terminal Emulation Note: If DCM is not running, start it by using Conman or the dcmstart program. 1. Configure the device to use Transparent display mode by scanning this label: Transparent *$+OC2$-* *$+OC2$-* 2. Transfer the teirl.irl program to all IRL devices that you plan to use for terminal emulation. You can use the sample application programs download, writeit, or irldl to download IRL programs to devices. For example, if the logical name of the device is rdr1 and DCM is installed in the directory /users/intermec/dcm, you could send the teirl.irl program to the device by entering the following commands: download -f /users/intermec/dcm/tools/teirl.irl -d rdr1 -w The download program clears both reader preambles, so you must set preamble A to the proper transaction ID. 3. Set up preamble A for each device by scanning this label: Enter Preamble A *+.* *+.* 3-82

133 Configuring a DCM System 3 Use the device s keypad to type the transaction ID name and the system delimiter and then press Enter. DCM treats this preamble like a transaction ID, so the transactions are routed correctly. 4. Start the TE IRL program on the device by pressing Ctrl-Enter and then pressing B or by scanning this label: Run Program *//* *//* The TE IRL program connects to DCM and then displays the host system login prompt. You can exit the TE IRL program by pressing Ctrl-Enter and then pressing E or by scanning this label: Exit Program */$* */$* Setting Up a JANUS Device for Terminal Emulation 1. Use the JANUS configuration application IC.EXE to: Determine the version of the JANUS firmware you are using. You must be using version 1.24 or higher to run terminal emulation on your JANUS device. Configure your JANUS device for the proper communications protocol. Refer to the user s manual of your device for specific information. 2. Transfer the following files (located in DCM s tools subdirectory) from your UNIX machine to a DOS PC: te.bat batch file to start TE te.cfg configuration file for TE te124.exe TE executable program run on a JANUS device using firmware version 1.24 te130.exe TE executable program run on a JANUS device using firmware version 1.30 or higher 3-83

134 DCM for HP-UX User s Manual You need UNIX connectivity software such as FTP or PC-NFS running on your PC in order to receive the TE programs from the UNIX system. If you cannot transfer the JANUS TE programs to a DOS PC, you can obtain them from Intermec as follows: Contact your Intermec Technical Services representative to get the programs for you from the Intermec Bulletin Board Service (BBS). Contact Intermec Technical Services at or and request the DCM JANUS Mode Terminal Emulation programs on DOS diskette. 3. Use Interlink to download te.bat, te.cfg, and the TE executable program for the version of your JANUS firmware from the DOS PC to the JANUS device. Refer to the user s manual for your JANUS device for more information. 4. Make sure you have the appropriate protocol handler loaded: JANUS Device Port Protocol Handler J2010, J2020 COM1 phimec 1 JR2020, J2050, and J2010 with RF back COM4 rfph 4 Configuring a JANUS Device for Terminal Emulation JANUS terminal emulation is controlled by the configuration file te.cfg. You can edit this file through a menu driven interface in order to configure your JANUS device for terminal emulation. To configure terminal emulation on your JANUS device 1. From the DOS prompt, enter the following command: te.bat nnn config where: te.bat nnn config is the batch file that starts TE on the device is the JANUS firmware version number specifies running TE in configuration mode 3-84

135 Configuring a DCM System 3 You see the Environment Config screen. Use the and keys to move between fields and use the and keys to move within fields when you are using the configuration screens. 2. Set up your environment as follows: Terminal Type Select the terminal type that is used by the host system. The supported terminal types are: VT100, VT220 (default), VT320, ANSI, and RDRANSI. Transaction ID Enter the transaction ID and system delimiter you want to use for the TE session. Comm Port Select the communications port your JANUS device is using. Available communications ports are: COM1 for non-rf communications and COM4 (default) for RF communications. Host Name Enter the name of the remote host you want to connect to or leave this field blank to connect to the DCM host. 3. Choose Ok to save your changes or choose Cancel to discard any changes to your environment configuration. You see the DCM/JANUS TE menu. Note: When you exit the Environment Config screen, the field parameters you set become static and cannot be changed during the current configuration session. 4. From the DCM/JANUS menu, choose JANUS Cfg and press Enter to access the JANUS Config screen. This screen contains the following fields: Preamble You can tailor JANUS bar code label input by adding a preamble to scanned data. This field can contain any text character string, and the default value is blank. 3-85

136 DCM for HP-UX User s Manual Postamble You can also add a postamble to scanned input. This feature is particularly useful in a data entry application where each scanned input needs to be followed by a carriage return (CR). By specifying a CR (\r) in the postamble of the input, you do not need to press Enter every time you scan an item. This field can contain any text character string, \r for CR (default), or \t for Tab. Numeric Keypad Use this field to enable or disable (default) numeric keypad mode on the JANUS device. When numeric keypad mode is enabled, numeric keys function like the numeric keys on the numeric keypad. When numeric keypad mode is disabled, numeric keys function like the numeric keys on the main keyboard. Text Size Use this field to specify the text size displayed on the JANUS device screen. Two text sizes are available, regular height (default) and double height. 5. Choose Ok to accept your changes or choose Cancel to discard any changes to your JANUS configuration. 6. From the DCM/JANUS TE menu, choose Session Cfg and press Enter to access the Session Config screen. This screen contains the following fields: Input Mode Line mode enables you to enter a line of characters on the JANUS device before it is transmitted to the host machine. Communications overhead are reduced in this mode, because any input is echoed one line at a time instead of one or a few characters at a time. In character mode (default), any keyboard input is immediately forwarded to the DCM host. Viewport Mode Auto viewport mode (default) enables the viewport to automatically follow the cursor during a terminal emulation session. Manual viewport mode requires that you move the viewport on the device to follow the cursor. 3-86

137 Configuring a DCM System 3 Protocol Intermec controllers and readers depend on 7-bit standard ASCII character handshaking for communications. As a result, TE communications are encoded before transmitting and decoded upon receiving. As Intermec introduces new controllers and readers that take advantage of true 8-bit binary communications, Enhanced protocol can be used to bypass the communications encoding/decoding overhead. Note: This feature is only supported by JANUS devices with firmware version 1.30 or later and controllers that support true 8-bit communications. 7. Choose Ok to accept your changes or choose Cancel to discard any changes to your session configuration. 8. For VT terminals only, you can choose VT Terminal Cfg and press Enter to access the VT Terminal Config screen. This screen contains the following fields: Keypad Mode In VT series terminals, there are two modes for function keys, editing keys, and numeric keys: application mode and numeric mode (default). These keys generate different key codes depending on the mode your VT terminal is using. Cursor Mode VT series terminals have two modes for arrow keys: application mode and cursor mode (default). These keys generate different key codes depending on the mode your terminal is using. Term Mode This field specifies the mode VT series terminals use to exchange escape sequences, control commands, and status reports with an application. VT terminal types are backward compatible, so the possible terminal modes for each terminal type are listed below: VT 100 Terminal VT 220 Terminal VT 320 Terminal VT 100 VT 100 VT 220, 7-bit (default) VT 220, 8-bit VT 100 VT 220, 7-bit VT 220, 8-bit VT 320, 7-bit (default) VT 320, 8-bit 3-87

138 DCM for HP-UX User s Manual User Defined Key There are 15 programmable function keys for VT 220 and 320 terminals: F6 through F14, Do, Help, and F17 through F20. When this field is set to Unlock (default) you can program the function keys you want. Setting this field to Lock prevents programming or reprogramming of these keys. For more information on JANUS device key mapping between the different terminal types, refer to JANUS Mode Terminal Emulation Support in Appendix A of this manual. 9. Choose Ok to accept your changes or choose Cancel to discard any changes to your VT terminal configuration. 10. From the DCM/JANUS TE menu, choose Exit Cfg. You see the message: Save new configuration? 11. Do one of the following: Choose Yes to save any changes you made to the configuration file te.cfg and to return to the DOS prompt. The previous configuration file is saved as te.bak. Choose No to discard any changes you made to the configuration file te.cfg and to return to the DOS prompt. Choose Cancel to return to the DCM/JANUS TE menu. Starting a TE Session on a JANUS Device 1. On the DCM machine, use Conman or the dcmstart command to start DCM using a valid configuration file. Note: You can enter dcmstart -h at the command line for information on how to use this command. 2. Start a terminal emulation session on the JANUS device by entering the following command: te.bat nnn where nnn is the JANUS firmware version number (124 or 130). For example, if your JANUS device contains firmware version 1.30, you would enter: te.bat

139 Configuring a DCM System 3 The TE program on the JANUS device establishes a connection with DCM and displays a login prompt for the host system. Note: You can modify your TE configuration and view your environment parameters during a terminal emulation session by pressing Ctrl-F3 on your JANUS device. This hot key configuration allows you to access the DCM/JANUS TE menu where you can make changes to your JANUS, Session, and VT Terminal configurations. When you exit the DCM/JANUS TE menu, your TE session is restored. Ending a TE Session on a JANUS Device Do one of the following on your JANUS device: Enter exit at the UNIX prompt. Press Ctrl-F

140

141 4 Managing DCM

142

143 Managing DCM 4 Status Watch This chapter explains how to start, stop, and make use of the runtime features of DCM. DCM has two configurations: static and volatile. The static configuration is maintained on disk in a configuration file. The volatile configuration is held in memory while DCM is running. Initially, the volatile configuration is a duplicate of the static configuration. The procedures described in this chapter affect the volatile configuration. The DCM Status Watch window displays the audit file size, the status file size, and the amount of free space on the working drive. DCM updates the file sizes and free space size every 30 seconds. If a file size is zero, then the file does not exist or it is empty. The window also displays the configuration file DCM will use if DCM had stopped, or the one used if DCM is running. This configuration file may not be the same one displayed in the Conman window title. If you want DCM to use the configuration that is currently opened in Conman, you must update DCM. Updating DCM is discussed in more detail later in this section. The DCM Status Watch window also displays icons indicating DCM s execution status. Icon Description DCM stopped DCM running DCM recovery Note: If DCM is in the middle of recovery, both the running icon and the recovery icon are displayed. 4-3

144 DCM for HP-UX User s Manual To display the DCM Status Watch window From the View menu, choose Status Watch. The DCM Status Watch window appears. To remove the DCM Status Watch window, click its system menu button and choose Close. Using a Configuration File to Run DCM Before starting DCM, you need to load a configuration file. After DCM is running, you can also change or update the configuration file it is using. To select a configuration file for DCM 1. From the File menu, choose Open. 2. From the dialog box, choose the configuration file you want DCM to use or you want to modify, and then choose OK. If you want to change the configuration file, use the Conman Setup menu. Refer to Chapter 3, Configuring a DCM System, for specific information on how to use the choices available on the Setup menu. 3. From the Conman menu, choose File. 4. From the File menu, choose Use to run DCM. 5. If changes to the configuration file have not been saved, a message box appears and prompts you to save the changes. If you choose Yes, the changes made to the file are saved before DCM uses it. If you choose No, the changes made to the file are not saved for DCM to use, but they are retained in memory for the current session. 4-4

145 Managing DCM 4 6. You are prompted with another message box. If DCM is stopped: Choose Use to have DCM use the currently opened configuration file the next time it is started. The configuration file name appears at the bottom of the DCM Status Watch window as the DCM runtime file. Choose Cancel to quit the configuration file update. If DCM is running: Choose Restart to shutdown DCM and restart it with the currently opened configuration file. A series of messages are displayed during this process. Once the shutdown process is complete, a DCM start message box appears. Choose Yes to restart DCM. Choose Cancel to cancel the update process. Note: If you make changes to the configuration file DCM is using, it is necessary to choose Use to run DCM on the File menu to update DCM s operating parameters. Starting DCM There are two methods you can use to start DCM: (1) from within Conman or (2) from the command line. Starting DCM From Conman Before you start DCM, complete the following checklist: Configure all applications and runtime parameters. Physically connect and configure all stations. Start all your applications so they are waiting for DCM. Verify that the DCM Status Watch window displays the correct configuration file DCM will use. If it does not, load the configuration file into Conman and choose Use to run DCM on the File menu to load the configuration file you want DCM to use. 4-5

146 DCM for HP-UX User s Manual To start DCM 1. From the Control menu, choose Start DCM. The Start DCM dialog box appears. 2. Choose Start DCM. Conman starts DCM s execution as a background process while displaying a series of messages. The first message is: Starting DCM in the background... When the startup process has completed successfully, the Status Watch window displays the Running icon. On the Control menu, Start DCM is disabled and Stop DCM, DCM system operation, and Audit recovery are enabled. Note: DCM software continues to run in the background even when Conman is exited or when you log out. 4-6

147 Managing DCM 4 Starting DCM From the Command Line You can start DCM from the command line by running the executable program, dcmstart. This program is useful when you do not need to use the configuration capabilities provided by Conman. However, since dcmstart uses Conman s input channel upon execution, it cannot be run while Conman is active. The format of the dcmstart command is: dcmstart -h -n config_filename where: -h displays command usage information. -n runs DCM without a Status Session window. This option is necessary when running dcmstart from non-x terminals on UNIX systems. config_filename is the configuration file (*.cnf) you want DCM to use upon startup. This file is copied to config.dcm. If you do not specify a configuration file, the current contents of config.dcm are used to start DCM. The following processes are spawned in order when dcmstart is executed: Status session (if -n option is not specified) Message handler All DevComms, terminal session managers, and NetComms specified in the configuration file All informational and/or error messages generated by dcmstart are written to the Status Session window. Examples dcmstart -h dcmstart dcmstart example.cnf dcmstart /users/intermec/dcm/mycfg.cnf 4-7

148 DCM for HP-UX User s Manual Controlling DCM System Parameters You can control the following two system parameters from within Conman: time synchronization of the data collection network and the audit trail. To change DCM systemwide parameters 1. From the Control menu, choose DCM system operation. The Control DCM System Operation dialog box is displayed. 2. Use the following fields to control DCM s volatile configuration: Controller Time Synch Time synchronization is only relevant for Intermec 9154 and 9180 v2.0 controllers. Choosing Now (enabled only when DCM is running) initiates Conman to request the message handler to issue a systemwide time synchronization message to all controllers. The message handler responds to this request by issuing the time synch message (current host time) to those DevComms, which in turn update the controllers. If you want extra control over the format of the time synch message, refer to Appendix A for a description of the portnametbi environment variable. 4-8

149 Managing DCM 4 Note: In order for Intermec controllers (9154 or 9180 v2.0 only) and readers to accept time synchronization, the device must have the Accept Time Sync push button enabled in the Connection Options dialog box. Time synchronization is sent to controllers only, not to the individual stations connected to the controllers. To enable time broadcast for controllers, set the portnametbi environment variable. Audit Trail This edit box allows you to specify which good transactions are audited: those routed by destination and/or those routed by transaction ID. Transactions sent by application programs typically, but not necessarily, contain a destination name in the transaction header. Transactions that come from a station always contain a transaction ID in the header; they cannot contain a destination name. Note: Undeliverable transactions (which contain an invalid transaction ID or an invalid destination, or have failed validation) are always written to the audit file. The Audit Trail box also allows you to specify the time of day (24-hour format) you want the audit file renamed. DCM keeps the audit file open while it is running. Renaming the file allows you to back up or remove old audit data. The audit file is renamed at the first occurrence of the time you specify. For example, if you start DCM at 14:00 hours and the file rename time is set at 14:10, the audit file is renamed 10 minutes after DCM starts. Note: If you change the rename time while DCM is running, the new rename time takes effect immediately. When the audit file is renamed, it has the format: yymmddhh.aud where: yy is the year mm is the month dd is the day hh is the hour of the day Note: Maintaining an audit trail for all transactions causes slower response time from DCM and increased disk usage. 3. Choose OK. 4-9

150 DCM for HP-UX User s Manual Recovering Audit File Data You can reprocess the data stored in the audit file. This feature is useful for diagnosis and recovery from application or system problems. When you access the audit file, the data is time-stamped and processed as if transactions were currently being collected. You can specify criteria for the transactions you want to recover. For example, you can pick all transactions entered within a certain time period or containing a particular transaction ID. The parameters you specify for a recovery operation must be valid for a transaction to pass through the message handler to a destination. Also, a recovery operation accesses only those transactions contained in the currently opened audit file; it does not access any transactions from old, renamed audit files. To run audit file recovery 1. From the Control menu, choose Audit recovery. The Audit File Recovery dialog box appears. 4-10

151 Managing DCM 4 2. Enter the appropriate information in the following fields: From beginning of file Enable this box if you want DCM to start reprocessing transactions in the audit file using the earliest transaction date and/or time. Through end of file Enable this box if you want DCM to reprocess transactions in the audit file using the latest date and/or time. Date/24-Hour Time If you have not enabled one of the above boxes, use this field to specify the date and time ranges you want to use for transaction reprocessing. The following guidelines will help you enter information in the Start and Stop fields: Use a zero (0) at the beginning of one digit months or hours. Enter four digits for the current year. Use 24-hour, military time. For example, enter for 1:00 P.M. Press Tab to move the cursor into the date and hour boxes. Transaction Status Select the type of transactions you want to recover from the audit file: Both Enable this button to have all transactions recovered from the audit file. Good Enable this button to have only good transactions recovered from the audit file. Failed Enable this button to have only failed transactions recovered from the audit file. Transactions that fail validation are treated as failed transactions and are written to the audit file. Destinations and Transaction IDs Enable the All radio button in each field to recover all transactions routed by destination or by transaction ID respectively. Enable the List radio button in each field to recover destinations selected from the Audit Recovery Destination List dialog box and transaction IDs selected from the Audit Recovery Transaction List dialog box respectively. The Audit Recovery Destination List dialog box is shown on the following page. 4-11

152 DCM for HP-UX User s Manual You can add or remove audit recovery destinations or transaction IDs from their respective dialog boxes as follows: Add To add a destination or transaction ID to the Include list box, do one of the following: Select the destination or the transaction ID you want in the Available list and choose Add. Double-click the destination or the transaction ID you want in the Available list box. All destinations or transaction IDs added to the Include list box are removed from the Available list box. Remove To remove a destination or a transaction ID from the Include list box, do one of the following: Select the destination or the transaction ID you want in the Include list box and choose Remove. Double-click the destination or the transaction ID you want in the Include list box. All destinations or transaction IDs removed from the Include list box are returned to the Available list box. 3. Choose Start to begin transaction recovery from the audit file. The DCM Status Watch window displays the recovery icon. Depending on the size of the audit file, recovery could take several minutes. 4-12

153 Managing DCM 4 IPC Channel Watch The IPC Channel Watch feature monitors the number of transactions currently held in each of DCM s Inter Process Communication (IPC) channels. You can use this feature to diagnose bottlenecks in the system or to view the number of transactions backing up in the various channels. In a system that is not heavily loaded, all transaction counts will typically be zero or one. If you contact an Intermec service technician regarding a problem with DCM, you may be asked to run IPC Channel Watch. To run IPC Channel Watch From the View menu, choose IPC Channel Watch. The IPC Channel Watch window appears. This display updates automatically every 1, 2, or 5 seconds as specified by the radio buttons at the bottom of the dialog box. The default is 2 seconds. 4-13

154 DCM for HP-UX User s Manual Stopping DCM If the system is running correctly, the channel names are typically preceded by a zero or a one. If transactions are backing up in the channel, the number is incremented as transactions are received. A channel name preceded by a dash ( ) indicates the channel is closed or unavailable. There are two methods you can use to stop DCM s background activity and shut it down in an orderly manner: (1) from within Conman or (2) from the command line. Note: During shutdown, the message handler creates the file dcmstop.dat. The message handler uses this file during the next startup to determine which destinations were active when it shut down. Using Conman to Shut Down DCM 1. From the Control menu, choose Stop DCM. The Stop DCM dialog box appears. 2. Choose DCM Stop to begin the shutdown process. All data collection activities are concluded, but Intermec controllers continue polling and buffering data. Readers using IRL programs requiring a response directly from a destination (interactive mode) halt until DCM activity is resumed. 4-14