Omni 37xx Reference Manual VeriFone Part Number 22412, Revision A
Reference Manual © 2003 VeriFone, Inc. All rights reserved. No part of the contents of this document may be reproduced or transmitted in any form without the written permission of VeriFone, Inc. The information contained in this document is subject to change without notice. Although VeriFone has attempted to ensure the accuracy of the contents of this document, this document may include errors or omissions. The examples and sample programs are for illustration only and may not be suited for your purpose.
CONTENTS P R E F A C E . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 CHAPTER 1 Introduction CHAPTER 2 Terminal Setup CHAPTER 3 Using the Terminal Keys CHAPTER 4 System Mode Audience. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Organization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Related Documentation . . . . . . . . . . . . . . . . . . . . . .
CHAPTER 5 File Authentication CHAPTER 6 Performing Downloads 4 Enter and Exit System Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . System Mode Menu 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . System Mode Menu 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . System Mode Menu 3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . System Mode Menu 4 . . . . . . . . . .
CHAPTER 7 Troubleshooting and Service Software Checklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Telephone Download Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Back-to-Back Application Downloads. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Hardware Checklist. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Software Checklist . . . . . . . . . . . . . . . . . . . . . . . . . . .
OMNI 37XX REFERENCE MANUAL
LIST OF FIGURES Figure 1 Figure 2 Figure 3 Figure 4 Figure 5 Figure 6 Figure 7 Figure 8 Figure 9 Figure 10 Figure 11 Figure 12 Figure 13 Figure 14 Figure 15 Figure 16 Figure 17 Figure 18 Figure 19 Figure 20 Figure 21 Figure 22 Figure 23 Figure 24 Figure 25 Omni 37xx Product Components Direct Telephone Connection Printer Latch Button Removing Partial Paper Roll Loading Paper Roll Closing Paper Roll Cover MSAM Compartment Door and Optional Locking Screw MSAM Holder Close-Up Using an MSAM Holder Smart Card Re
OMNI 37XX REFERENCE MANUAL
LIST OF TABLES Table 1 Table 2 Table 3 Table 4 Table 5 Table 6 Table 7 Table 8 Table 9 Table 10 Table 11 Table 12 Table 13 Table 14 Table 15 Table 16 Table 17 Table 18 Table 19 Table 20 Table 21 Table 22 Table 23 Table 24 Optional Devices Supported Example of Last Character Changing Example ALPHA Key Entries Using ALPHA and the 12-Key Keypad System Mode Menus Procedural Description Example Enter System Mode System Mode Menu 1 System Mode Menu 2 System Mode Menu 3 System Mode Menu 4 System Mode Menu 5 Syste
OMNI 37XX REFERENCE MANUAL
PREFACE This guide is your primary source of information for setting up and installing the Omni 37xx series of terminals. Audience Organization This document has two primary audiences, but is useful for anyone installing and configuring the Omni 37xx terminal: • Deployment Administrators prepare multiple units for deployment to their customers, configuring the units with applications, network configurations, phone numbers, and security.
P REFACE Related Documentation This guide also contains appendices for System Messages, Port Pinouts, ASCII Table, and Glossary.
P REFACE Guide Conventions Guide Conventions Various conventions are used to help you quickly identify special formatting. The following table describes these conventions and provides examples of their use. Convention Meaning Example Blue Text in blue indicates terms that are cross referenced. See Guide Conventions. Italics Italic typeface indicates book titles or emphasis. You must not use this unit underwater.
P REFACE Guide Conventions 14 OMNI 37XX REFERENCE MANUAL
CHAPTER 1 Introduction Omni 37xx Series of Terminals NOTE This chapter provides a brief description of the Omni 37xx series of terminals. The Omni 37xx terminal series represents the shape of things to come in e-payment. The bold ergonomic design is sleek and stylish, offering countertop power and 32-bit performance in an integrated terminal that can be handed to the consumer for input.
I NTRODUCTION Features and Benefits Features and Benefits Exceptional Ease Of Use Countertop Performance in a “Hand-Over” Design True MultiApplication Capability 16 Omni 37xx terminals provide the right combination of features and functions at the right price. This includes a vertical magnetic-stripe card reader, smart card reader, integrated PIN pad, and a quiet, fast, integrated thermal printer (ITP).
CHAPTER 2 Terminal Setup This chapter describes the terminal setup procedure. You will learn how to: Select Terminal Location Ease of Use Environmental Factors • Select a location and protect the terminal from adverse Environmental Factors. See Select Terminal Location. • Unpack the shipping carton. See Unpack the Shipping Carton. • Establish telephone line connections. See Establish Telephone Line Connections. • Install paper roll in the printer. See Install Paper Roll.
T ERMINAL S ETUP Unpack the Shipping Carton • WARNING Unpack the Shipping Carton Do not use the terminal near water or in moist conditions. Due to risk of shock or terminal damage, do not use the terminal near water, including a bathtub, wash bowl, kitchen sink or laundry tub, in a wet basement, or near a swimming pool. Open the shipping carton and carefully inspect its contents for possible tampering or shipping damage.
T ERMINAL S ETUP Establish Telephone Line Connections 4 Save the shipping carton and packing material for future repacking or moving the terminal. Establish Telephone Line Connections Connect the telephone cord to the communication port on the terminal, then route it directly to a telephone wall jack (see Figure 2). This is a direct connection, and the line is dedicated to the terminal. Figure 2 Direct Telephone Connection CAUTION To reduce the risk of fire, use only No.
T ERMINAL S ETUP Install Paper Roll To Install a Paper Roll 1 Turn on the terminal. The green LED indicator will blink on and off, indicating that the printer needs paper. 2 Press the button on the side of the terminal to unlatch the paper roll cover, then rotate the cover up and back (see Figure 3). Figure 3 Printer Latch Button 3 Remove partial rolls of paper in the printer tray by lifting up (see Figure 4).
T ERMINAL S ETUP Install/Replace MSAM Cards Figure 5 Loading Paper Roll 7 Close the paper roll cover by gently pressing directly on the cover until it clicks shut. Allow a small amount of paper to extend outside the cover (see Figure 6). NOTE To prevent damage to the print roller on the paper roll cover, always close the cover by gently pressing down on the paper roll cover. Figure 6 Closing Paper Roll Cover For paper ordering information, refer to Accessories and Documentation.
T ERMINAL S ETUP Install/Replace MSAM Cards To change or install SAMs 1 Remove the power cord from the back of the terminal. 2 Place the terminal upside-down on a soft, clean surface to protect the lens from scratches. 3 To access the MSAM holders, remove the optional locking screw and remove the MSAM compartment door (see Figure 7).
T ERMINAL S ETUP Connect Optional Device(s) 7 Install an MSAM card by aligning the card and carefully sliding it within the guides on the cover until it is fully inserted. NOTE Before inserting the MSAM card, position it as shown in Figure 9, with the card’s gold contacts facing the smart car reader end of the terminal. The holder connector base has a set of contacts and a notch post on one corner to ensure the MSAM card is positioned correctly when the cover is closed.
T ERMINAL S ETUP Connect Optional Device(s) Connect PIN Pad, Smart Card Reader, or Bar Code Wand To Connect PIN Pad, Smart Card Reader, or Bar Code Wand 1 If necessary, insert the small modular plug on one end of the PIN pad cable into the PIN pad’s modular jack. For a bar code wand, insert the RJ45-type connector into the PIN pad serial port on the back panel. 2 If installing a PINpad 101, PINpad 201, or PINpad 1000, position and insert the grommet to secure the cable connection.
T ERMINAL S ETUP Connect Terminal Power Pack Figure 11 External Printers Supported Connect Terminal Power Pack CAUTION CR 600 Check Reader Connection Although most Omni 37xx variants have an internal thermal printer, it may be convenient to print larger print runs (for example, daily, or weekly reports) to an external printer. The Omni 37xx terminal supports the P250, P350,P900, and P950 VeriFone external printers. Contact your VeriFone representative or visit the online store at www.store.verifone.
T ERMINAL S ETUP Connect Terminal Power Pack Figure 12 Omni 37xx Power Pack Connection a To lock the connector into the power port, align the plastic lock tab so it points up. Insert the connector and twist to the left. b To unlock the connector, twist it to the right. 2 Insert the power cable into the power pack. 3 Plug the power pack cable into a wall outlet or surge protector. WARNING Do not plug the power pack into an outdoor outlet or operate the terminal outdoors.
CHAPTER 3 Using the Terminal Keys Before proceeding to other tasks, familiarize yourself with the operational features of the Omni 37xx terminal keypad to enter data. This section describes how to use the keypad, which consists of a 12-key Telcostyle keypad, three color-coded keys below the keypad, the ALPHA key above the keypad, four ATM-style function keys (F1, F2, F3, and F4) to the right of the display (Figure 13), and four programmable function (PF) keys directly above the keypad.
U SING THE T ERMINAL K EYS Data Entry Modes Data Entry Modes NOTE Before you can use the keys on the front panel to enter ASCII characters, the Omni 37xx must be in a mode that accepts keyed data entry. There are two terminal operating modes, each enables you to press keys to enter data under specific circumstances: • Normal mode: This is the terminal operating mode where an application program is present in memory and currently running.
U SING THE T ERMINAL K EYS Function Key Descriptions Function Key Descriptions NOTE The four programmable function (PF) keys directly above the keypad allows navigation though the system mode menus and selection of specific terminal operations. The terminal’s operating mode and context determine the specific action performed when you press one of the following function keys.
U SING THE T ERMINAL K EYS Function Key Descriptions Continue pressing ALPHA as many times as required to display the desired character. For example, press 2 to display the number 2; press ALPHA once to display the letter A, twice to display B, or three times to display C. If you press ALPHA one more time, you cycle back to the number 2. 3 NOTE If you firmly press and hold down one of the keys on the 12-key keypad without using ALPHA, the same character repeats until you stop pressing the key.
U SING THE T ERMINAL K EYS Programmable Function (PF) Key Descriptions Table 4 Using ALPHA and the 12-Key Keypad Key to Press Without Pressing ALPHA Press ALPHA One Time Press ALPHA Two Times Press ALPHA Three Times 6 MNO 6 M N O 7 PRS 7 P R S 8 TUV 8 T U V 9 WXY 9 W X Y 0 -SP 0 – [space] + ,’ ” * , ‘ “ # ! : ; * #a a. NOTE The # key also supports additional characters: (@), (=), (&), (/), (\), (%), ($), and (_).
U SING THE T ERMINAL K EYS Programmable Function (PF) Key Descriptions 32 OMNI 37XX REFERENCE MANUAL
CHAPTER 4 System Mode This chapter describes a category of terminal functions called system mode operations. • Use a special key combination and password to invoke the system mode. See Entering System Mode. • Assign files and applications to groups for access control. See File Groups. • Use system and file group passwords to secure applications and information on the terminal. See Passwords.
S YSTEM M ODE Verifying Terminal Status • Remote operations require communication between the terminal and a host computer (or another terminal) over a telephone line or a cable connection. Perform remote system mode operations to download application software to the terminal, upload software from one terminal to another, and perform diagnostics over a telephone line. This chapter contains descriptions on how to perform local system mode operations.
S YSTEM M ODE File Groups File Groups The Omni 37xx operating system implements a file system in volatile, batterybacked RAM and non-volatile flash memory. Files are assigned to one of 15 groups for access control. Groups are similar to directories on a computer in that different applications can be stored in separate file groups, just like different computer applications can be stored in separate directories. Groups are referred to as Group n or GIDn throughout this manual.
S YSTEM M ODE System Mode Menus When you key in the system password to enter system mode, an asterisk (*) appears on the display for each character you type. These asterisks prevent your password from being seen by an unauthorized person. You can use the ALPHA key to change the characters or symbols you enter; this does not cause additional asterisks to appear. NOTE File Group Passwords Some application program downloads automatically reset the system password.
S YSTEM M ODE System Mode Menus To return to a previous menu, press the PF1 key (below the up arrow). To go to the next menu, press the PF2 key (below the down arrow). To return to the main system mode menu and cancel any changes, press the cancel key. Each menu has items to select; sometimes these items contain submenus or a series of prompts. When prompted to enter alphabetic or special characters, use the procedure described in Chapter 3.
S YSTEM M ODE System Mode Menus • Provides additional explanations or information about the steps of that particular system mode menu. A Submenu row indicates a specific procedure evoked from a main menu screen. A description of that procedure immediately follows the Submenu row. The following keys have the same function from all submenus: Enter and Exit System Mode NOTE • Press the enter key to save changes from a submenu and return to the menu screen.
S YSTEM M ODE System Mode Menus Table 7 Enter System Mode Display Action SYSTEM MODE ENTRY PASSWORD ---------- If an application prompt appeared in Step 2 and you chose to enter system mode you are prompted to type the system password. If DOWNLOAD NEEDED appeared in Step 2, use the default password “Z66831.” This password is entered as: 1 ALPHA ALPHA 6 6 8 3 1, and press [↵] Use the backspace [←] key to delete the entry and correct any mistakes.
S YSTEM M ODE System Mode Menus Table 8 System Mode Menu 1 Display Action CLOCK F3 Note: The terminal clock is battery-backed to retain date and time settings when the terminal is shut off. SYS MODE CLOCK YEAR: 2003 MONTH: 02 DAY: 07 ↑ ↓ This example shows February 07, 2001. To set YEAR, press F2 and type a four-digit number for the current year. To set MONTH, press F3 and type a two-digit number for the current month (between 01– 12).
S YSTEM M ODE System Mode Menus System Mode Menu 2 NOTE In this menu, you can accomplish full or partial downloads to your terminal, clear RAM files, and clear flash files. Before performing a download to flash memory in an initialized terminal (one that contains an application), reclaim all available flash space. Unlike RAM, unused flash and duplicate flash information are not automatically reclaimed during a download.
S YSTEM M ODE System Mode Menus Table 9 System Mode Menu 2 Display Action SYS MODE DOWNLOAD G _1 MODEM F2 COM1 F3 COM2 F4 Select a download mode: MODEM F2, COM1 F3, or COM2 F4. To return to the main menu without saving your selection, press the cancel key. ↑ SYS MODE DOWNLOAD G _1 ***------DOWNLOADING NOW The terminal is ready to receive a download. During the download, a line of asterisks appears that shows percentage of completion. Each asterisk equals approximately 10% of the download.
S YSTEM M ODE System Mode Menus Table 9 System Mode Menu 2 Display Action FLASH FILES F4 SYS MODE FLASH CLEAR GROUP _1 F2 CLEAR ALL FILES F3 DEFRAG 0 F4 To clear a file group’s flash files, type the file group number (1–15) and press F2. To correct a mistake, press [←] to delete the number, and type a new entry. To clear the flash files of all file groups, press F3.
S YSTEM M ODE System Mode Menus System Mode Menu 3 In this menu, you can view terminal configuration information, edit the CONFIG.SYS or another keyed file, and change system mode and file group passwords. NOTE Some application program downloads automatically reset the system password. Table 10 System Mode Menu 3 Display Action SYS MODE MENU 3 To view terminal configuration information, select CONFIG INFO F2. To edit the CONFIG.
S YSTEM M ODE System Mode Menus Table 10 System Mode Menu 3 Display Action SYS MODE CONF RAM 512 FLASH 1024 SERNO xxxxxxxxx PTID 12000000 PART xxxxxxxxx VERS A This screen shows configuration information specific to your terminal: ↑ ↓ • Total kilobytes of RAM memory • Total kilobytes of flash memory • Serial number • Permanent terminal identification number (PTID) • Terminal part number • Terminal hardware version number Your terminal’s screen may vary depending on your terminal’s model and the op
S YSTEM M ODE System Mode Menus Table 10 System Mode Menu 3 Display Action EDIT F3 To search for keyed records in a particular file group, type the appropriate group number and press [↵]. SYS MODE FILE FILE GROUP _1 If you cannot locate a particular keyed record, it may be stored in another file group. To search for keyed records in another file group, return to the main menu by pressing the cancel key, then type the appropriate group number and press [↵ ].
S YSTEM M ODE System Mode Menus Table 10 System Mode Menu 3 Display Action SYS MODE EDIT G 1 (Key name) KEY F2 (Key value) ↑ ↓ ← VALUE F3 To scroll through the search keys, press [↵]. Or use the PF1 or PF2 keys to scroll the up and down respectively, as needed. To manually enter another key name, select KEY F2 and use [←] to clear the previous key name from the display. Then, type the appropriate key name and press [↵ ].
S YSTEM M ODE System Mode Menus Table 10 System Mode Menu 3 Display Action SYSTEM MODE FILE GROUP nn PASSWORD ---------- Type the current password for the selected file group and press [↵ ]. If you enter an incorrect password, the following message appears: SYS MODE PASSWORD PLEASE TRY AGAIN Press [↵]. Verify your password and re-enter it. SYS MODE PASSWORD G _1 Type the new password and press [↵]. To correct a mistake, press [←] to delete the number, and then type the new entry.
S YSTEM M ODE System Mode Menus For example, in CONFIG.SYS, the VeriCentre key for the application serial ID number is *ZT. The value for the key is the actual application ID number. By entering *ZT using the editor, the terminal can quickly locate the application serial ID number. You can also use [↵] to scroll through the search keys instead of entering the characters *ZT through the keypad.
S YSTEM M ODE System Mode Menus Table 11 System Mode Menu 4 Display Action REMOTE DIAGS F2 LOAD TERMINAL MANAGEMENT AGENT REMOTE DIAGS: This function is reserved for VeriFone use. To return to the previous system mode menu, press the PF1 key; to return immediately to SYS MODE MENU 1, or to quit any operation within this menu, press the cancel key. ERROR LOG F3 SYS MODE ERR LOG TYPE 0004 FRAME 00040040 03DE0000 00000000 00001002 ↓ The first filename is shown on line two.
S YSTEM M ODE System Mode Menus Table 11 System Mode Menu 4 Display Action SYSTEM MODE FILE GROUP nn PASSWORD ---------- To continue, enter the required password. If you enter an incorrect password, the following message appears: SYS MODE PASSWORD PLEASE TRY AGAIN Press [↵]. Verify your password and re-enter it. Invoking the Debugger starts the application program’s debug monitor, if installed, on the selected file group.
S YSTEM M ODE System Mode Menus Table 12 System Mode Menu 5 Display Action MAG CARD DIAG F4 To test the magnetic-stripe card reader, swipe a magnetic-stripe card through it. SYS MODE TRK 1:VALID DATA TRK 2:VALID DATA TRK 3:VALID DATA A successful test displays VALID DATA for each track that read valid data.
S YSTEM M ODE System Mode Menus Table 13 System Mode Menu 6 Display Action IPP KEY LOAD F3 Select this mode when using SecureKit or programming from your PC to inject keys into your terminal. In this mode, a pipe is opened through COM1 to the IPP to allow key loading. INTERNAL PIN PAD KEY LOADING MODE BYTES SENT 0 BYTES RCVD 0 END F4 Press the cancel key to stop the key load session; press F4 when finished with the key load.
S YSTEM M ODE System Mode Menus Table 14 System Mode Menu 7 Display Action RAM DIRECTORY F3 SYS MODE FILE FILE GROUP _1 Type the number of the file group (1 for the primary application; between 1–15 for other applications) and press [↵] to view a list of files in the flash directory. To search for files in a particular file group, type the appropriate group number and press [↵]. If you cannot locate a particular file, it may be stored in another file group.
S YSTEM M ODE System Mode Menus Table 14 System Mode Menu 7 Display Action SYSTEM MODE FILE GROUP nn PASSWORD ---------- To continue, enter the required password. If you enter an incorrect password, the following message appears: SYS MODE PASSWORD PLEASE TRY AGAIN Press [↵]. Verify your password and re-enter it. FLASH DIRECTORY G 3 A.OUT 1234567 09/27/03 A CARDDATA.DAT 9876543 09/27/03 - The first filename is shown on line two.
S YSTEM M ODE System Mode Menus 56 OMNI 37XX REFERENCE MANUAL
CHAPTER 5 File Authentication This chapter discusses VeriShield’s file authentication security architecture. • Overviews the VeriShield file authentication module, and the organizational infrastructure that supports it. See Introduction to File Authentication. • Explains how the file authentication process may affect the tasks normally performed by application programmers, terminal deployers, site administrators, or by entities authorized to download files to an Omni 37xx terminal.
F ILE A UTHENTICATION Introduction to File Authentication • A digital signature is a piece of information based on both the file and the signer’s private cryptographic key. The file sender digitally signs the file using a private key. The file receiver uses a digital certificate to verify the sender’s digital signature. • Signer private keys (*.key files) are securely conveyed to clients on smart cards.
F ILE A UTHENTICATION Introduction to File Authentication NOTE Only one sponsor certificate is permitted per terminal. • Signer certificate: Certifies the right to sign and authenticate files for terminals belonging to the sponsor. A signer certificate is authenticated under the authority of a higher-level client certificate (the sponsor certificate).
F ILE A UTHENTICATION Introduction to File Authentication 3 The application file becomes a required input for the FILESIGN.EXE tool (included in the SDK). 4 The default certificate (K2SIGN.CRT) and default key (K2SIGN.KEY) included in the SDK are inputs for the FILESIGN.EXE tool. 5 Using the application file, default certificate, and default key, FILESIGN.EXE creates a signature file (*.p7s).
F ILE A UTHENTICATION Introduction to File Authentication Figure 14 The Development Process Pre-Deployment Process In this process: 1 A sponsor goes to the VeriFone CA Web site and requests certificates for deployment terminals. 2 Based on information provided by the sponsor through the VeriFone CA Web site, the VeriFone CA determines the required certificate structure. 3 VeriFone CA generates the following items for the sponsor: a Smart card containing a set of certificates and keys.
F ILE A UTHENTICATION Introduction to File Authentication 4 VeriFone CA sends the smart card and smart card PIN to the sponsor. 5 The sponsor uses the smart card and smart card PIN as inputs for the deployment process. Refer to Figure 15 illustrates the pre-deployment process.
F ILE A UTHENTICATION Introduction to File Authentication b If a signature file is found, the operating system then searches for a matching application file. c If a matching application file is found, the operating system compares the signature file’s signature against the values stored in the application file’s calculated signature. d If the values match, the two files are authenticated and the ATTR_NOT_AUTH bit is set to 0.
F ILE A UTHENTICATION Introduction to File Authentication Figure 16 Planning for File Authentication 62 The Deployment Process File authentication is an integral part of every Omni 37xx terminal. To safeguard the terminal’s logical security, the file authentication module requires that any executable code file must be successfully authenticated before the operating system allows it to execute on the terminal.
F ILE A UTHENTICATION Introduction to File Authentication Authentication Requirements for Specific File Types For the purposes of file authentication, executable code files include two file types that can be recognized by their filename extensions: Table 15 Executable File Extensions File Type Extension Compiled and linked application files *.out Global function libraries *.
F ILE A UTHENTICATION Introduction to File Authentication It is not mandatory to always download a signature file at the same time as its target application file. For example, you can download the corresponding signature file in a separate operation.
F ILE A UTHENTICATION Introduction to File Authentication For non-executable files, it is the application’s responsibility to confirm that all of the files it uses successfully authenticated on download completion, and when the application executes the first time following a restart. NOTE Because the application is responsible for verifying data files and prompt files, it is recommended that each application check the ATTR_NOT_AUTH bit of all relevant files on restart.
F ILE A UTHENTICATION Introduction to File Authentication A development set of higher-level certificates is downloaded into each Omni 37xx terminal at manufacture. When you take a new Omni 37xx terminal out of its shipping carton, certificate data is already stored in the terminal’s certificate tree. In this just-out-of-the-box condition, the Omni 37xx terminal is called a development terminal.
F ILE A UTHENTICATION Introduction to File Authentication NOTE With the factory set of certificates stored in the terminal memory, anyone who has the Omni 37xx SDK and included file signing tool, FILESIGN.EXE, can generate valid signature files for downloading and authenticating files on the Omni 37xx platform.
F ILE A UTHENTICATION Introduction to File Authentication Figure 17 Certificate Trees in Development and Deployment Terminals Permanency of the Certificate Tree The data contained in a digital certificate is stored in the terminal’s certificate tree when the certificate is authenticated, and the certificate file itself is erased from RAM. The certificate tree file is stored in a reserved area of non-volatile memory and is therefore relatively permanent.
F ILE A UTHENTICATION Introduction to File Authentication Table 16 Differences Between Required Inputs Development Terminals Deployment Terminals Manufacturing inputs to the file signing process are included, together with the file signing tool, FILESIGN.EXE, in the Omni 37xx SDK. These inputs make it possible for anyone who has the Omni 37xx SDK to sign and authenticate files. The required inputs to FILESIGN.
F ILE A UTHENTICATION File Authentication and the File System Figure 18 File Authentication and the File System Certificate Replacement Process Application Memory Logically Divided Into File Groups The memory of an Omni 37xx terminal is logically divided into two main areas, or partitions: One partition is for the operating system and the other partition is reserved for applications. The application partition is further divided into subpartitions. These sub-partitions are called file groups or GIDs.
F ILE A UTHENTICATION File Authentication and the File System Figure 19 NOTE Omni 37xx Application Memory Partitions The Omni 37xx operating system only enforces the rule that the main application always be stored in GID1. You can, for example, store a shared library in any file group. Rules for Storing Applications in Specific File Groups states reasons to follow the guidelines previously described for storing applications and libraries in specific file groups.
F ILE A UTHENTICATION File Authentication and the File System Because each application is responsible for verifying its own data and prompt files, the other application files should have their own matching signature files. The master .OUT file should validate that these additional signature files are authenticate before the signature files are used.
F ILE A UTHENTICATION FILESIGN.EXE File Signing Tool Restrictions on Downloading Different File Types A typical application download includes a variety of different file types. There are the following restrictions on how you can download different kinds of files to the Omni 37xx terminal and how files are stored in the file system: Table 17 Download File Extensions File Type Restriction Certificate (*.crt) Must be downloaded into the RAM of the target file group (GID1– GI15) selected in system mode.
F ILE A UTHENTICATION FILESIGN.EXE File Signing Tool Operating Modes for FILESIGN.EXE FILESIGN.EXE can run on the host computer in two user modes: • Command-line mode (Windows PC DOS shell): Command-line mode is useful for application developers who perform batch file downloads and is convenient when using file download tools provided by VeriFone such as VeriCentre Download Management Module (DMM), VeriCentre, and the direct download utility, DDL.EXE.
F ILE A UTHENTICATION FILESIGN.EXE File Signing Tool Command-Line Entries for FILESIGN.EXE Table 18 Table 18 lists and describes the switches that make up the command-line mode syntax for FILESIGN.EXE. Command-Line Mode Switches for FILESIGN.EXE Switch Description Requirements -C, -c Signer certificate file name (*.crt). Required input for development terminals and deployment terminals. For development terminals, you can use the default signer certificate, K2SIGN.CRT.
F ILE A UTHENTICATION FILESIGN.EXE File Signing Tool • The default signer certificate and default signer key file names that are provided by VeriFone as part of the Omni 37xx SDK are entered on the command line instead of customer-specific customer signer certificate and customer signer private key file names.
F ILE A UTHENTICATION FILESIGN.EXE File Signing Tool If you want to store the file in flash memory on download to the terminal, check the “Stored in FLASH” checkbox. This adds the “F:” prefix to the target file name. • Press ALT-S or click on the [...] button to the right of the “Signature file” field to enter a filename for the signature file to be generated. The filename extension must always be *.p7s. You can also choose another directory to store the generated signature file.
F ILE A UTHENTICATION FILESIGN.
CHAPTER 6 Performing Downloads This chapter contains information and procedures to allow you to perform the various types of data transfers required to: • Develop applications for the Omni 37xx terminal. • Prepare Omni 37xx terminals for deployment. • Maintain Omni 37xx terminal installations in the field. • Transfer data to/from terminals. In this chapter, information pertaining to file authentication is only discussed in the context of procedures while performing file downloads.
P ERFORMING D OWNLOADS Download Tools • Download Tools NOTE Back-to-back downloads: Files and data transfer from a sending Omni 37xx terminal to a receiving Omni 37xx terminal. A special cable (VPN 05651-xx) connects the RS232 serial ports of the two terminals. Three software tools are available from VeriFone for performing downloads: VeriCentre Download Management Module (DMM), VeriCentre, and DDL.EXE (Direct Download Utility).
P ERFORMING D OWNLOADS Full and Partial Downloads Omni 37xx applications can be developed by VeriFone, customers, or third parties on customer request. One or more applications must be downloaded to the Omni 37xx terminal before it can be deployed at a customer site and used to process transactions. • Files related to file authentication: The logical component of the VeriShield security architecture in the Omni 37xx terminal is file authentication.
P ERFORMING D OWNLOADS Full and Partial Downloads Table 19 Types of Full and Partial Downloads Download Type Description and Effects Full application download An entire application, including all executables and data files, transfers from one system to another in a single operation.
P ERFORMING D OWNLOADS Full and Partial Downloads Table 19 Types of Full and Partial Downloads Download Methods Supported Download Type Description and Effects Full operating system download An entire OS version transfers from a host PC to the Omni 37xx terminal. • Direct downloads Files related to file authentication and terminal configuration settings can be included in a full OS download. During this process, RAM is cleared.
P ERFORMING D OWNLOADS Omni 37xx Download Differences configuration settings in an Omni 37xx terminal and then return control to the main application. • Omni 37xx Download Differences Support for Multiple Applications Full downloads restart the terminal; partial downloads return control to system mode or the issuing application. OS and application downloads can be combined. The file authentication module is not invoked until the terminal is restarted following the download procedure.
P ERFORMING D OWNLOADS Omni 37xx Download Differences The Main Application is Always Stored in GID1 The main application stored in GID1 is the controlling application for the terminal. Any function call that invokes a related program or a secondary application stored in GIDs 2–14 must be initiated by the GID1 application. An application stored in a file group other than GID1 is limited in that it can only access executables and files stored in its own file group and in GID15.
P ERFORMING D OWNLOADS Omni 37xx Download Differences In a typical download procedure, all files are loaded into the RAM file system of the target group selected in system mode. Specific files included in the download package must be redirected, as necessary, to the flash file system of the target group or to the RAM or flash file system of another file group. To redirect files during a download procedure, see the following sections.
P ERFORMING D OWNLOADS Omni 37xx Download Differences To create a zero-length SETDRIVE file on the download computer, use the DOS command, REM, as in the following example: REM >SETDRIVE.F To redirect a file from RAM of the target group to flash of the same file group, insert the zero-length SETDRIVE.F file into the batch of application files to download. All files that follow the SETDRIVE.F file in the download list automatically load into flash memory (F:) of the target group.
P ERFORMING D OWNLOADS Omni 37xx Download Differences Redirecting Files to Other File Groups GID1 is the default system mode setting for performing downloads. Using the system mode menu options, you can select another file group (GID 2–15) as the target group for the application download. If you select another group, files download directly into the RAM of that file group.
P ERFORMING D OWNLOADS Omni 37xx Download Differences SETGROUP.2 GOO.OUT GOO.P7S SETGROUP.15 COMN.LIB COMN.P7S NOTE You can only use zero-length SETGROUP.x files for batch application downloads, either direct or telephone, and only using the Download Manager or VeriCentre download tools (not DDL.EXE). You cannot use this special file convention for operating system downloads or back-to-back application downloads. Using DDL.EXE to Automatically Redirect Files The version of DDL.
P ERFORMING D OWNLOADS Omni 37xx Download Differences A downloaded OS is processed and authenticated while stored in Group 1 RAM. As the files are authenticated under the authority of the certificates and signature files included in the OS download package, they move automatically into Group 0. This process, which usually takes a few minutes, is completely transparent during the download procedure.
P ERFORMING D OWNLOADS Omni 37xx Download Differences • A signature file must be downloaded together with each executable that makes up an application. An executable can be a compiled and linked object file (*.out) or a shared function library (*.lib). In most cases, an application consists of multiple executables and requires a number of corresponding signature files.
P ERFORMING D OWNLOADS Omni 37xx Download Differences 1 All certificate files (*.crt), signature files (*.p7s), and application files (*.out, *.lib, *.fon, *.vft, *.dat, and so on) download to the Omni 37xx deployment terminal in batch mode. 2 When the terminal restarts after the download, the file authentication module searches the RAM-based file system for the following two file types: • Authenticated certificate files (*.crt) to add to the permanent certificate tree • Signature files (*.
P ERFORMING D OWNLOADS Omni 37xx Download Differences Figure 21 Display Prompts During the File Authentication Process 5 Signature files are processed next (after certificate files). The file authentication module calls the signature checking routine one time for each new signature file it detects. Each *.p7s file is checked as it is detected; a list is not built and multiple processing passes are not required.
P ERFORMING D OWNLOADS Omni 37xx Download Differences not halt the process if a signature file fails to authenticate, but continues to the next step: storing the downloaded files in their final locations in the terminal file system. 6 Certificate files and signature files are retained in the RAM file system until the file authentication process is complete. These special files are then either deleted or automatically redirected to another file system or file group, as previously described.
P ERFORMING D OWNLOADS Omni 37xx Download Differences Download an Operating System Update Provided by VeriFone Because the operating system software for the Omni 37xx is developed and controlled by VeriFone for its customers, VeriFone provides the necessary certificates and signature files to ensure the authenticity and integrity of the operating system update as part of the download package.
P ERFORMING D OWNLOADS Omni 37xx Download Differences takes a few minutes), the terminal restarts automatically and the OS download procedure is complete. CAUTION If the power supply to the receiving terminal is accidentally cycled during an operating system download procedure, the terminal may permanently lock up. In that case, return the terminal to VeriFone for service.
P ERFORMING D OWNLOADS Omni 37xx Download Differences terminal, the application executes and the application prompt or logo displays on the terminal. Timing Considerations Due to the Authentication Process The file authentication process takes some time.
P ERFORMING D OWNLOADS Effect of Downloads on Existing Files and Data • Support for File Compression Effect of Downloads on Existing Files and Data NOTE 98 Before you perform a download, use system mode menu selections to clear the entire RAM and/or flash or the RAM or flash of a specific file group, as necessary to ensure proper use of available memory in the target group. For information regarding file compression, refer to refer to the Verix Operating System Programmer’s Manual (VPN 19733).
P ERFORMING D OWNLOADS Set Up the Download Environment Set Up the Download Environment The first step in performing a download to an Omni 37xx terminal is to establish the physical communication link between the sending and receiving system required to support the desired download method: • Direct serial cable connection for direct application and OS downloads. The link is between the COM1 port of a download computer (PC) and the COM1 port on the receiving Omni 37xx terminal.
P ERFORMING D OWNLOADS Set Up the Download Environment Figure 22 Telephone Line Connection for Telephone Downloads Serial Cable Connection for Direct Downloads To set up the telephone line connection for application or OS downloads between a host computer and an Omni 37xx terminal: 1 Confirm proper configuration of the dial-up telephone line and modem connection on the host computer. 2 Confirm the parameters for the download by telephone are set in the download tool.
P ERFORMING D OWNLOADS Direct Application Downloads Cable Connection for Back-to-Back Application Downloads To prepare for a back-to-back application download: 1 Insert the RJ45 modular connector on one end of the download cable (VPN 05651-00) into the RS232 port of the sending terminal. 2 Insert the RJ45 connector on the other end of the cable into the RS232 port on the back panel of the receiving terminal. Direct Application Downloads This section provides procedures for direct downloads.
P ERFORMING D OWNLOADS Direct Application Downloads Download, clear, and defragment operations cannot proceed in system mode if an application is executing. If you see the message DEVICE BUSY, PLEASE RESTART STAND ALONE, press the cancel key and restart the terminal from SYS MODE MENU 1. When you see the VeriFone copyright screen, enter system mode within 3 seconds (before the application starts).
P ERFORMING D OWNLOADS Direct Application Downloads Table 20 Common Steps to Start a Download Step Display 3 SYSTEM MODE ENTRY PASSWORD ------------------- Action Enter the system mode password. If an application already resides on the terminal, a unique system mode password may already exist. In this case, type that password and press enter to confirm your entry. If DOWNLOAD NEEDED displayed in step 2, enter the default password, “Z66831”.
P ERFORMING D OWNLOADS Direct Application Downloads Table 21 Step 4 Direct Application Download Procedure Display SYS MODE DOWNLOAD G _1 MODEM F2 COM1 F3 COM2 F4 ↑↓ 5 SYS MODE DOWNLOAD G _1 DOWNLOADING NOW Action Select the terminal port to use for the data transfer from the host computer to the receiving terminal. (To display additional menu options, press the PF2 key.) For a direct application download, always select the COM1 menu option by pressing F3.
P ERFORMING D OWNLOADS Direct Application Downloads Table 21 Step 7 Direct Application Download Procedure Display **VERIFYING FILES** COMPARE SIGNATURE FILENAME.P7S FILENAME.OUT **AUTHENTIC** or else --- F AILED --- Action The file authentication module proceeds to authenticate any new signature files downloaded with the OS files. When the signature file authentication routine starts, the status display shown at left informs you of the progress of the authentication process.
P ERFORMING D OWNLOADS Direct Operating System Downloads Direct Operating System Downloads Hardware Checklist Software Checklist This section presents procedures for direct downloads. • The correct cable connects the download computer serial port (COM1 or COM2) to the Omni 37xx RS232 serial port (COM1) (refer to Cable Connection for Direct Downloads). • Verify that the RAM size on the receiving terminal is large enough to receive files uploaded from the sending terminal.
P ERFORMING D OWNLOADS Direct Operating System Downloads • NOTE Checklist for Effects on Files and Settings in the Receiving Terminal Direct Operating System Download Procedure NOTE Use system mode menu options to clear the entire RAM or the RAM of Group 1 on the receiving terminal (as necessary). Download, clear, and defragment operations cannot proceed in system mode if an application is executing.
P ERFORMING D OWNLOADS Direct Operating System Downloads Table 22 Step 1 Direct Operating System Download Procedure Display SYS MODE FILE FILE GROUP _1 Action Enter the target file group for the download. File Group _1 (Group 1) is the default. Operating system files must always download into Group 1. This is the default group number in system mode. To select Group 1 as the target file group, press enter.
P ERFORMING D OWNLOADS Download by Telephone Table 22 Step 7 Direct Operating System Download Procedure Display Action **VERIFYING FILES** COMPARE SIGNATURE The file authentication module proceeds to authenticate new signature files downloaded with the OS files. When the signature file authentication routine begins, the progress of the authentication process displays.
P ERFORMING D OWNLOADS Download by Telephone NOTE Telephone Download Procedure Table 23 Step 1 • Baud rate settings for the data transfer • Terminal ID • Application ID • Operating system name or serial number For detailed information about the setup requirements and download procedures for Download Manager and VeriCentre, please refer to the user documentation supplied by VeriFone with these software products.
P ERFORMING D OWNLOADS Download by Telephone Table 23 Step 6 Download by Telephone Procedure Display **VERIFYING FILES** CHECK C ERTIFICATE (FILENAME.CRT) **AUTHENTIC** or else --- F AILED --- Action When the OS download is complete, the terminal restarts automatically. The file authentication module on the receiving terminal then checks for new certificate (*.crt) and signature (*.p7s) files included in the download.
P ERFORMING D OWNLOADS Back-to-Back Application Downloads Back-to-Back Application Downloads Hardware Checklist Software Checklist NOTE 112 This section presents procedures for back-to-back terminal downloads. • The correct serial cable connects the RS232 ports of the sending and receiving Omni 37xx terminals (refer to Cable Connection for Back-to-Back Application Downloads). • Verify the RAM size on the receiving terminal is large enough to receive files uploaded from the sending terminal.
P ERFORMING D OWNLOADS Back-to-Back Application Downloads Checklist for Effects on Files and Settings in the Receiving Terminal Back-to-Back Application Download Procedure • A back-to-back application download overwrites existing applications, libraries, or any other files stored in RAM of the receiving terminal. • All CONFIG.SYS records and settings on the receiving terminal—protected and non-protected—are replaced with those of the sending terminal.
P ERFORMING D OWNLOADS Back-to-Back Application Downloads Download Application Files to Target Terminal 1 Configure a Gold terminal for an application download operation to a deployment terminal: • If the *FA variable (if present in the application) is set to 1, you can reset it to 0. For more information on the *FA variable, refer to the Verix Programmer’s Manual (VPN 19733). • Ensure the download is exactly what you want your Target terminals to receive.
P ERFORMING D OWNLOADS Back-to-Back Application Downloads Figure 23 Back-To-Back Download Process The procedure in Table 24 steps you through a back-to-back application download from a sending Omni 37xx terminal (Gold) to a receiving Omni 37xx terminal (Target).
P ERFORMING D OWNLOADS Back-to-Back Application Downloads Back-to-back downloads require that one terminal, the Gold terminal, be loaded with the required applications. The receiving terminal is the Target terminal. The procedure in Table 24 assumes the following: NOTE • The Target terminal has no applications loaded. • There is enough memory in the Target terminal to complete the download. The Target terminal does not display an error message if there is not enough memory to complete the download.
CHAPTER 7 Troubleshooting and Service VeriFone follows stringent quality control standards in the manufacture of Omni 37xx terminals. Each unit that leaves the factory receives numerous tests to ensure quality and reliable operation. However, should you encounter a problem in operation, read this section for possible causes and solutions. NOTE NOTE Perform only those adjustments or repairs specified in this guide. For all other services, contact your local VeriFone distributor or service provider.
T ROUBLESHOOTING AND S ERVICE Troubleshooting Troubleshooting Terminal Display Does Not Show Correct or Readable Information Telephone Line Connection Does Not Work Properly Printer Does Not Work Serial Port Does Not Work Terminal Does Not Process Transactions During normal, day-to-day operation of your Omni 37xx terminal, it is possible that minor malfunctions may occur. Here are some examples of possible problems, and steps you can take to resolve them.
T ROUBLESHOOTING AND S ERVICE Cleaning and Care 2 Perform a test transaction using several different magnetic stripe cards to ensure the problem is not a defective card. 3 Make sure you are swiping cards properly. With the Omni 37xx card reader, the black, magnetic stripe on the card should face down, toward the keypad. 4 Process a transaction manually using the keypad instead of the card reader. If the manual transaction works, the problem may be a defective card reader.
T ROUBLESHOOTING AND S ERVICE VeriFone Service and Support CAUTION Never use thinner, trichloroethylene, or ketone-based solvents — they can deteriorate plastic or rubber parts. Do not spray cleaners or other solutions directly onto the keypad or display. CAUTION Do not attempt to clean the smart card reader. Doing so may void your warranty. For smart card reader service, contact your VeriFone distributor or service provider.
T ROUBLESHOOTING AND S ERVICE Returning a Terminal • Please address the fax clearly to the attention of the “VeriFone MRA Dept.” • Include a telephone number where you can be reached and your fax number. • You will be issued MRA number(s) and the fax will be returned to you. • NOTE One MRA number must be issued for each terminal you return to VeriFone, even if you are returning several of the same model.
T ROUBLESHOOTING AND S ERVICE Specifications Specifications Power DC Power Pack Omni 37xx terminal: 24 V DC; 1.5 A For non-switching power supplies: • UL, ITE listed, Class 2 power supply • Input rated: 110 - 127V AC, 60 Hz • Output rated: 24V DC 1.5 A For switching power supplies: • UL, ITE listed, Class 2, switching power supply • Input rated: 100 - 240 V AC, 50/60 Hz • Output rated: 24 V DC, 1.
T ROUBLESHOOTING AND S ERVICE Accessories and Documentation Accessories and Documentation Power Pack VeriFone produces accessories and documentation for the Omni 37xx terminal, as listed below. When ordering, refer to the part number in the left column. • VeriFone Online Store at www.store.verifone.com • USA: VeriFone Customer Development Center, 1-800-233-0522, Monday– Friday, 7 A.M.–5 P.M.
T ROUBLESHOOTING AND S ERVICE Accessories and Documentation Documentation 124 OMNI 37XX REFERENCE MANUAL 22429 Omni 37xx Certifications and Regulations 22398 22407 22409 22408 22403 Omni 3750 Quick Installation Guide Omni 3740 Quick Installation Guide Omni 3720 Quick Installation Guide Omni 3710 Quick Installation Guide Omni 3705 Quick Installation Guide 19733 Verix Operating System Programmer’s Manual 22399 Omni 37xx Series Installation Guide 22410 Omni 37xx Privacy Shield Quick Installation G
APPENDIX A System Messages This appendix describes error and information messages that may appear when the Omni 37xx terminal is in system mode. For ease of use, these messages are grouped alphabetically.
System Messages This message displays when a system mode function queried an internal device that is busy. This message can also occur if you entered system mode with an application running. For example, if the application opened the magnetic stripe card reader and you try to invoke the card reader diagnostic through MAG CARD READER F4 in SYS MODE MENU 5, the attempt fails and this message appears. Restart the terminal and enter system mode before the application starts.
System Messages LOAD DBMON.OUT The DEBUGGER F4 option in SYS MODE MENU 4 was selected. The debugging monitor program, DBMON.OUT, is included in the SDK, but is not stored in the terminal memory of a factory unit. To use the debugging tool, you must sign, download, and authenticate the DBMON.OUT application.
System Messages PINPAD LIFE RSET RCNT MODEM CTRY This message displays when you select CONFIG INFO F2 in SYS MODE MENU 3 and press the PF2 key (below the down arrow) three times. This fourth display, in a series of four, provides the following information about the current terminal configuration: • PINPAD: • LIFE: • RSET: • RCNT: • MODEM CTRY: A 1-digit code (0 or 1) to indicate that a PIN pad is integrated. The number of seconds the terminal has run since first powered on.
System Messages RAM CHKSUM ERROR A corrupt file is detected in the RAM file system at terminal start up, after poweron, or during restart. This message may indicate a hardware problem or the error condition may be resolved through another download of the file. RAM FILES INUSE AVAIL FLASH FILES INUSE AVAIL This message displays when you select CONFIG INFO F2 in SYS MODE MENU 3.
System Messages SYS MODE CLEAR CLEARING RAM PLEASE WAIT This message displays when you select RAM FILES F3 in SYS MODE MENU 2 and select CLEAR GROUP_nn F2 or CLEAR ALL FILES F3 to clear files from the RAM of a specific file group (Group 1–15) or from the entire RAM. This message remains until the files either within the file group or all files in RAM are deleted. If you select CLEAR ALL FILES F3, only the application file(s) stored in RAM—not the files stored in flash—are erased.
System Messages SYS MODE EDIT FILE KEY VALUE This message displays when you select EDIT F3 in SYS MODE MENU 3 to invoke the keyed file editor to edit files (such as, CONFIG.SYS), as follows: • FILE: • KEY: • VALUE: Make the appropriate menu selections to select or create a file to edit. Search for a specific keyed record. Add a new value for a selected keyed record. SYS MODE ERROR LOG TYPE FRAME USP TCB TIME This information appears when you select ERROR LOG F3 in SYS MODE MENU 4.
System Messages SYS MODE PASSWORD FILE GROUP nn GROUP nn PASSWORD This message displays when you initiate the procedure for modifying existing system mode passwords through PASSWORDS F4 in SYS MODE MENU 3. Additional menu options display to let you change the password of a file group (F2) or the system mode password (F3). SYS MODE PASSWORD NEW AGAIN PASSWORD CHANGED This message displays when you select PASSWORDS F4 in SYS MODE MENU 3 to modify the existing system mode password.
System Messages TRK1: TRK2: TRK3: When you invoke a local system mode diagnostic test of the magnetic stripe card reader, status information appears for data track (TRK1, TRK2, and TRK3) on a magnetic stripe card.
System Messages ** VERIFYING FILES ** Check Certificate (or System Certificate) filename.crt ** Authentic ** (or ---Failed---) This message displays when the file authentication module detects a new digital certificate, together with the filename of the certificate to authenticate, during a download to the Omni 37xx terminal.
APPENDIX B ASCII Table An ASCII table for the Omni 37xx display is presented as Figure 25 below. The table is formatted for quick reference, as follows: • The letters and numbers in the column to the left of the table and in the row above the table are, when combined, the hexadecimal value of an ASCII character located in the corresponding row and column coordinate.
ASCII Table Figure 25 136 OMNI 37XX REFERENCE MANUAL ASCII Table for the Omni 37xx Display
APPENDIX C Port Pinouts PIN Pad Serial Port The tables in this appendix list pinouts for the Omni 37xx connectors. Connector 1 10 LOOKING INTO CONNECTOR RS232 Port Connector 1 10 LOOKING INTO CONNECTOR a.
Port Pinouts Ethernet Port ISDN Port Connector Connector Barrel Connector Polarity 138 OMNI 37XX REFERENCE MANUAL Pin Function Description 1 TXD+ Transmit data + 2 TXD- Transmit data - 3 RXD+ Receive data + 4 NC No connection 5 NC No connection 6 RXD- Receive data - 7 NC No connection 8 NC No connection Pin Function Description 1 NC No connection 2 NC No connection 3 STA Signal Transmit A 4 SRA Signal Receive A 5 SRB Signal Receive B 6 STB Signal Transm
GLOSSARY Access code A code number dialed to gain access to a telephone line, such as dialing the number 9 to reach an outside line. Application ID An alphanumeric code that identifies an application program downloaded to a terminal from a download computer. For VeriCentre application downloads, the application ID is stored in the CONFIG.SYS record which begins with the *ZA key. An Omni 37xx application ID can be up to 21 characters long.
G LOSSARY Block A collection of data units such as words, Certificate Also called a digital certificate. A digital characters, or records (generally more than a single word) that are stored in adjacent physical positions in memory or on a peripheral storage device. A block can therefore be treated as a single unit for reading, writing, and other data communication operations.
G LOSSARY Delete To remove a record, field, or item of data. File authentication A process through which one Diagnostics Techniques employed for detection proves and verifies the origin of a file, the identity of the sender, and the integrity of the information it contains. and isolation of malfunctions and errors in programs, systems, and devices. In a diagnostic test, a program or routine is run to detect failures or potential failures.
G LOSSARY Keyed file character set A limited set of 95 Memory A device or medium that can retain infor- ASCII characters, from 00h to 5Fh (or 0 to 95 decimal), that is used by the Omni 37xx keyed file editor. Although an application program can download all 95 characters in this set, you can only enter 50 of these characters from the terminal keypad: 0–9, A– Z, and 14 special characters. mation for subsequent retrieval.
G LOSSARY Packet A group of bits of fixed maximum size and Port An opening or connection that provides electri- well-defined format that is switched and transmitted as a composite whole through a packet switching network. Any message that exceeds the maximum size is partitioned and carried as several packets. cal or physical access to a system or circuit. Also, a connection point with associated control circuitry that allows I/O devices to be connected to the internal bus of a microprocessor.
G LOSSARY RAM Random-access memory. The type of memo- Search key Also called key. In the Omni 37xx, a ry in which storage locations are addressable and can therefore be accessed in any order. In the Omni 37xx terminal, the RAM (or SRAM) is commonly used to store applications and temporary data generated during a transaction. short character string used by an application to identify a keyed file record stored in CONFIG.SYS file(s). For example, *ZA or *OT.
G LOSSARY System Mode For the Omni 37xx, system mode Telephone jack Also, telephone line wall jack. In- temporarily disables normal mode operations, allowing you to perform local functions such as downloads, diagnostics, and other operations that cannot be performed while the application program is running. sert a modular connector into a telephone jack or receptacle. Also, modular-type sockets for connecting telephone line cords.
G LOSSARY Track 1, 2, or 3 data Information stored on tracks 1, 2, or 3 of a debit or credit card magnetic stripe, which can be read by a magnetic card reader device, such as the one that is integrated in the Omni 37xx terminal. Transaction An exchange of data resulting in a transfer of goods, services, value, and/or information between two parties. Variable A string of characters that denotes some value stored within the computer and that can be changed during execution.
INDEX A Accessories 123 Ordering 123 accessories cables for optional peripherals 123 documentation 124 download cables 123 ordering 123 paper roll spindle 123 power packs 123 telephone line cord 123 thermal printer paper 123 VeriFone cleaning kit 123 application debugging 49 B back-to-back downloads 79, 80 file authentication 96 redirect files during 90 set up environment 99 bar code wand connect 24 C cables ordering cables for optional peripherals 123 ordering download cables 123 certificates and signatu
I NDEX Software checklist 106 Performing downloads by telephone 109 Hardware checklist 109 Procedure 110 Software checklist 109 downloads applications and related files 80 back-to-back 79 back-to-back application 80 back-to-back application downloads cable connection 101 by telephone 79 definition 79 direct download utility (DDL) 80 direct downloads cable connections 99 download types 82 effect on existing files and data 98 file authentication and back-to-back application downloads 96 file authentication a
I NDEX Hierarchical relationships 56, 65 How certificates control file signing privileges 67 How they are authenticated 65 In a deployment terminal 66 In a development terminal 66 Main functions 65 Platform Root Certificate 56 Signer Certificate 57 Sponsor Certificate 56 What happens when you download a certificate 66 Deciding which files to authenticate 63 Definition of file authentication 55 Deployment process 57, 60 Development process 57 Digital signature 56 File signing Customer Signer PIN 69 FILESIG
I NDEX I O installation connecting a PIN pad 24 connecting a smart card reader/writer 24 connecting optional device(s) 23 connecting the terminal power pack 25 connecting the terminal to a telephone line 19 MSAM cards 21 MSAM holders 21 peripherals 24 setting up a direct telephone line connection 19 table of peripheral devices 23 terminal location 17 unpack the shipping carton 18 integrated PIN pad 45 diagnostic 52 key loading mode 52 operating system downloads 83 optimize memory space 97 optional devic
I NDEX R RAM 41 clear 42 display memory used 44 Remote diagnostics For troubleshooting 117 reset date and time 45 restart the terminal 40 S SecureKit 53 Service 117 Returning a terminal 120 signature file 73 smart card reader/writer connecting 24 System Mode CONFIG.
I NDEX Troubleshooting 117 Display 118 Guidelines 117 Keypad 119 Printer 118 Serial port connection 118 Smart card reader 117 Terminal transactions 118 Using remote diagnostics 117 Using system messages 117 U upload 79 V VeriCentre 2000 80 VeriCentre Download Management Module 48 152 REFERENCE M ANUAL
I NDEX REFERENCE M ANUAL 153
VeriFone, Inc. 2455 Augustine Drive Santa Clara CA 95054-3002 Tel: (800) VeriFone (837-4366) www.verifone.
