<![CDATA[
<HTML><HEAD>
<!-- Begin Header Records ========================================== -->
<!-- D:\DCCONN\help\e9ivbase.scr converted by B2H R3.11 (313) (OS2) -->
<!-- on 25 Jun 1999 at 02:27:15 -->
<META HTTP-EQUIV="updated" CONTENT="Fri, 25 Jun 1999 02:26:40">
<META HTTP-EQUIV="review" CONTENT="Sun, 25 Jun 2000 02:26:40">
<META HTTP-EQUIV="expires" CONTENT="Mon, 25 Jun 2001 02:26:40">
</HEAD><BODY BGCOLOR="ffffff">
<!-- End Header Records ============================================ -->
<A NAME=Top_Of_Page></A>
<H1>Installing and Configuring ERPBridge and DCConnect Programs</H1>
<HR><H2><A NAME=ToC>Table of Contents</A></H2>
<MENU>
<P><B><LI><A NAME=ToC_1 HREF="#Header_1" >Installing and Configuring ERPBridge and DCConnect Programs</A></B>
<P><B><LI><A NAME=ToC_2 HREF="#Header_2" >Preface</A></B>
<MENU>
<LI><A NAME=ToC_3 HREF="#Header_3" >Overview</A>
<LI><A NAME=ToC_4 HREF="#Header_4" >About This Book</A>
</MENU></MENU>
<HR><P><I><B><A NAME=ToC_5 HREF="#HDRPART1" >Installing DCConnect</A></B></I><BR>
<MENU>
<P><B><LI><A NAME=ToC_6 HREF="#Header_6" >DCConnect Overview</A></B>
<MENU>
<LI><A NAME=ToC_7 HREF="#HDRSRVR" >Server</A>
<LI><A NAME=ToC_8 HREF="#HDRDTOOLK" >Development Toolkit</A>
</MENU>
<P><B><LI><A NAME=ToC_9 HREF="#HDRHSRQ" >Hardware and Software Requirements</A></B>
<MENU>
<LI><A NAME=ToC_10 HREF="#Header_10" >Hardware Requirements</A>
<MENU>
<LI><A NAME=ToC_11 HREF="#Header_11" >Adapters</A>
<LI><A NAME=ToC_12 HREF="#HDR3012" >Devices Supported by DCConnect</A>
</MENU>
<LI><A NAME=ToC_13 HREF="#Header_13" >Software Requirements for OS/2</A>
<LI><A NAME=ToC_14 HREF="#Header_14" >Software Requirements for Windows NT</A>
</MENU>
<P><B><LI><A NAME=ToC_15 HREF="#HDRINST" >DCConnect Installation</A></B>
<MENU>
<LI><A NAME=ToC_16 HREF="#Header_16" >Viewing Files from the CD-ROM Before Installing</A>
<LI><A NAME=ToC_17 HREF="#HDRINSDISK" >Installing DCConnect Products</A>
<LI><A NAME=ToC_18 HREF="#Header_18" >Starting DCConnect Development Toolkit or Graphical User Interface</A>
<LI><A NAME=ToC_19 HREF="#Header_19" >Starting DCConnect Server on OS/2</A>
<LI><A NAME=ToC_20 HREF="#Header_20" >Starting DCConnect Server on Windows NT</A>
<LI><A NAME=ToC_21 HREF="#Header_21" >Installing DCConnect as a Service on Windows NT</A>
<LI><A NAME=ToC_22 HREF="#Header_22" >Directory Structure and Environment Variables Used by DCConnect</A>
</MENU>
<P><B><LI><A NAME=ToC_23 HREF="#Header_23" >Getting Started</A></B>
<MENU>
<LI><A NAME=ToC_24 HREF="#Header_24" >Tutorial Hardware and Software Requirements</A>
<LI><A NAME=ToC_25 HREF="#Header_25" >Starting the Tutorial</A>
</MENU>
<P><B><LI><A NAME=ToC_26 HREF="#Header_26" >Utilities</A></B>
<MENU>
<LI><A NAME=ToC_27 HREF="#Header_27" >DCConnect Backup and Restore Utility</A>
<LI><A NAME=ToC_28 HREF="#HDRDCCONFG" >DCConnect Configuration</A>
<LI><A NAME=ToC_29 HREF="#Header_29" >Set API Environment (OS/2 Only)</A>
</MENU></MENU>
<HR><P><I><B><A NAME=ToC_30 HREF="#HDRPART2" >Installing Other ERPBridge Products</A></B></I><BR>
<MENU>
<P><B><LI><A NAME=ToC_31 HREF="#HDR7524" >Installing 7524 Interface Support</A></B>
<P><B><LI><A NAME=ToC_32 HREF="#Header_32" >Installing and Configuring Transaction Connection</A></B>
<MENU>
<LI><A NAME=ToC_33 HREF="#Header_33" >Prerequisite Hardware and Software</A>
<LI><A NAME=ToC_34 HREF="#Header_34" >Installing Transaction Connection</A>
<LI><A NAME=ToC_35 HREF="#HDRCONFGCM" >Configuring Personal Communications</A>
<LI><A NAME=ToC_36 HREF="#Header_36" >Starting Transaction Connection Script Files</A>
<LI><A NAME=ToC_37 HREF="#HDRSTRTDB" >Starting Transaction Connection</A>
<LI><A NAME=ToC_38 HREF="#Header_38" >Multiple Sessions</A>
</MENU>
<P><B><LI><A NAME=ToC_39 HREF="#HDRJDE" >ERPBridge for J.D. Edwards</A></B>
<P><B><LI><A NAME=ToC_40 HREF="#HDRMAPICS" >Installing and Configuring ERPBridge for MAPICS</A></B>
<MENU>
<LI><A NAME=ToC_41 HREF="#Header_41" >Prerequisite Hardware and Software</A>
<LI><A NAME=ToC_42 HREF="#Header_42" >Installing ERPBridge for MAPICS</A>
<LI><A NAME=ToC_43 HREF="#Header_43" >MAPICS XA Release 2.2 and Release 2.3</A>
<LI><A NAME=ToC_44 HREF="#Header_44" >Configuring ERPBridge for MAPICS</A>
<LI><A NAME=ToC_45 HREF="#Header_45" >Configuring Personal Communications</A>
</MENU>
<P><B><LI><A NAME=ToC_46 HREF="#Header_46" >Installing Terminal Services for DOS/Windows</A></B>
<MENU>
<LI><A NAME=ToC_47 HREF="#HDRPREQHWS" >Prerequisite Hardware and Software</A>
<LI><A NAME=ToC_48 HREF="#HDRCRCON" >Creating the Terminal Services for DOS and for Windows Configuration Diskette</A>
<LI><A NAME=ToC_49 HREF="#HDRINSDOSW" >Installing Terminal Services for DOS and for Windows on the DOS or Windows PC</A>
<LI><A NAME=ToC_50 HREF="#HDRCONTDW" >Configuring Terminal Services for DOS and for Windows</A>
<LI><A NAME=ToC_51 HREF="#Header_51" >Directory Structure and Environment Variables Used by Terminal Services for DOS and for Windows</A>
</MENU>
<P><B><LI><A NAME=ToC_52 HREF="#Header_52" >Installing the DCConnect Transaction Building Tool</A></B>
<MENU>
<LI><A NAME=ToC_53 HREF="#Header_53" >Installing the Transaction Building Tool</A>
</MENU>
<P><B><LI><A NAME=ToC_54 HREF="#HDRNOTICES" >Notices</A></B>
<MENU>
<LI><A NAME=ToC_55 HREF="#Header_55" >Trademarks</A>
</MENU>
<P><B><LI><A NAME=ToC_56 HREF="#HDRHARDINS" >Installing Native Serial Ports and Data Collection Terminals</A></B>
<MENU>
<LI><A NAME=ToC_57 HREF="#HDRHSTEP2" >Plant Wiring Installation</A>
<LI><A NAME=ToC_58 HREF="#Header_58" >Installing RS-422 Cable</A>
<LI><A NAME=ToC_59 HREF="#HDRDCTHSU" >Data Collection Terminal Hardware Setup</A>
<LI><A NAME=ToC_60 HREF="#HDROPS" >DCT Operating Parameter Setup</A>
<MENU>
<LI><A NAME=ToC_61 HREF="#HDR25SETUP" >7525 Terminal Setup</A>
<LI><A NAME=ToC_62 HREF="#HDR26SETUP" >7526 Terminal Setup</A>
<LI><A NAME=ToC_66 HREF="#HDR27SETUP" >7527 Terminal Setup</A>
<LI><A NAME=ToC_67 HREF="#HDR24RFSTP" >7524 RF Terminal Setup</A>
<LI><A NAME=ToC_68 HREF="#Header_68" >7524 Batch Terminal Setup</A>
</MENU></MENU>
<P><B><LI><A NAME=ToC_69 HREF="#HDRCABLE" >Native Serial Port Cables</A></B>
<MENU>
<LI><A NAME=ToC_70 HREF="#Header_70" >Cabling RS-232 Computer Port to RS-232 Terminal Port</A>
<LI><A NAME=ToC_71 HREF="#Header_71" >Cabling RS-232 Computer Port to RS-422 Terminal Port</A>
</MENU>
<P><B><LI><A NAME=ToC_72 HREF="#HDRINDEX_START" >Index</A></B>
</MENU><HR><P>
<P>
<H1><A NAME="Header_1" HREF="#ToC_1">Installing and Configuring ERPBridge and DCConnect Programs</A></H1>
<BR>
<TABLE BORDER WIDTH=100%><TR><TH ALIGN=LEFT>Note</TH><TR><TD>
<P>Before using this information and the product it supports,
be sure to read the general information.
(<A HREF="#HDRNOTICES">Notices</A>)
</TD></TR></TABLE>
<P><B>Fifth Edition (July 1999)</B>
<P>This is a major revision of, and obsoletes, SC28-9809-03.
<P>This edition applies to the following IBM ERPconnect
licensed programs, and to all subsequent versions
and releases, until otherwise indicated in new editions.
<UL COMPACT>
<LI>IBM Data Collection Connection Development Toolkit for OS/2 and Windows NT,
Licensed Program 5639-H35, Release 4, Modification Level 0
<LI>IBM Data Collection Connection Server for OS/2 and Windows NT, Licensed
Program 5639-H34, Release 4, Modification Level 0
<LI>IBM 7524 Interface Support for OS/2 and for Windows NT,
Licensed Program 5696-977, Release 3, Modification Level 1
<LI>IBM Terminal Services for DOS and for Windows, Licensed
Program 5639-H39, Release 4, Modification Level 0
<LI>IBM ERPBridge for J.D. Edwards, Licensed Program 5799-QTA,
Release 2, Modification Level 0
<LI>IBM ERPBridge for MAPICS, Licensed Program 5639-H33,
Release 4, Modification Level 0
<LI>IBM Transaction Connection for OS/2 and Windows NT,
Licensed Program 5639-H36, Release 4, Modification 0
</UL>
<P>
Make sure you are using the correct edition for the level of the
product.
<P>Order publications through your IBM representative or the IBM
branch office serving your locality. Publications are not
stocked at the address below.
<P>A form for reader's comments is provided at the back
of this publication. If the form has been removed,
address comments to:
<DL COMPACT>
<DD>International Business Machines Corporation
<DD>Information Development Department 27X
<DD>1798 N.W. 40th Street
<DD>Boca Raton, Florida 33431 U.S.A.
</DL>
<P>
When you send information to IBM, you grant IBM a nonexclusive
right to use or distribute the information in any way it believes
appropriate without incurring any obligation to you.
<HR>
<H1><A NAME="Header_2" HREF="#ToC_2">Preface</A></H1>
<P>This section describes the ERPBridge(TM)
products and how this book is
organized. It also explains the book conventions for differentiating
between information that is specific to OS/2(TM) or to Windows NT®.
<HR>
<H2><A NAME="Header_3" HREF="#ToC_3">Overview</A></H2>
<P>
<P>ERPBridge consists of the following products:
<UL COMPACT>
<LI>Data Collection Connection(TM) (DCConnect)
<UL COMPACT>
<LI>Server for OS/2 and Windows NT (5639-H34)
<LI>Development Toolkit for OS/2 and for Windows NT (5639-H35)
<LI>7524 Interface Support (5695-977)
<LI>Terminal Services for DOS and for Windows (5639-H39)
<LI>Transaction Connection for OS/2 and for Windows NT (5639-H36)
<LI>Transaction Building Tool (5639-H37)
<LI>752x Emulator for DOS (5639-H38)
</UL>
<LI>ERPBridge for J.D. Edwards
<LI>ERPBridge for MAPICS(TM)
</UL>
<HR>
<H2><A NAME="Header_4" HREF="#ToC_4">About This Book</A></H2>
<P>
This book is divided into three parts:
<UL COMPACT>
<LI>Part 1. Installing DCConnect
<LI>Part 2. Installing Other Products
<LI>Part 3. Appendixes
</UL>
<P>Parts 1 and 2 are intended for installers, programmer
analysts, and other technical personnel who work with ERPBridge
products.
<P>To use Part 1 and Part 2, you need a general knowledge of data
processing and must be familiar with the following:
<UL COMPACT>
<LI>IBM OS/2 Warp or Warp Connect or Windows NT
<LI>IBM Industrial Computers or PCs
<LI>IBM Data Collection Terminals (DCTs)
</UL>
<P>
Part 3 provides notices and
technical reference material for the person
responsible for the Data Collection Terminal (DCT) network.
<P>To use Part 3, you should have experience in wiring and
cabling DCTs.
<TABLE BORDER WIDTH=100%><TR><TH ALIGN=LEFT>Important</TH><TR><TD>
Review this book thoroughly before attempting to perform the
described activities. Complete each step in the order given
wherever a sequence of steps is specified, and do not skip any
steps unless they are designated as optional. Otherwise, the
activity may not be completed successfully and errors may occur.
</TD></TR></TABLE>
<P><B>Book Conventions</B>
<P>Some statements and sections of this book apply only to OS/2
and others apply only to Windows NT. When an entire section
applies to only one operating system, the section title contains
the text
<B>(OS/2 only)</B> or <B>(Windows NT only)</B>. For parts of
a section which apply to only one operating system, the pertinent
statements begin with <B>(On OS/2)</B> or <B>(On Windows
NT)</B>.
<HR>
<H1><A NAME="HDRPART1" HREF="#ToC_5">Installing DCConnect</A></H1>
<P><A NAME="PToC1" HREF="#ToC">Partial Table-of-Contents</A>
<MENU>
<P><B><LI><A NAME=PToC_6 HREF="#Header_6" >DCConnect Overview</A></B>
<MENU>
<LI><A NAME=PToC_7 HREF="#HDRSRVR" >Server</A>
<LI><A NAME=PToC_8 HREF="#HDRDTOOLK" >Development Toolkit</A>
</MENU>
<P><B><LI><A NAME=PToC_9 HREF="#HDRHSRQ" >Hardware and Software Requirements</A></B>
<MENU>
<LI><A NAME=PToC_10 HREF="#Header_10" >Hardware Requirements</A>
<MENU>
<LI><A NAME=PToC_11 HREF="#Header_11" >Adapters</A>
<LI><A NAME=PToC_12 HREF="#HDR3012" >Devices Supported by DCConnect</A>
</MENU>
<LI><A NAME=PToC_13 HREF="#Header_13" >Software Requirements for OS/2</A>
<LI><A NAME=PToC_14 HREF="#Header_14" >Software Requirements for Windows NT</A>
</MENU>
<P><B><LI><A NAME=PToC_15 HREF="#HDRINST" >DCConnect Installation</A></B>
<MENU>
<LI><A NAME=PToC_16 HREF="#Header_16" >Viewing Files from the CD-ROM Before Installing</A>
<LI><A NAME=PToC_17 HREF="#HDRINSDISK" >Installing DCConnect Products</A>
<LI><A NAME=PToC_18 HREF="#Header_18" >Starting DCConnect Development Toolkit or Graphical User Interface</A>
<LI><A NAME=PToC_19 HREF="#Header_19" >Starting DCConnect Server on OS/2</A>
<LI><A NAME=PToC_20 HREF="#Header_20" >Starting DCConnect Server on Windows NT</A>
<LI><A NAME=PToC_21 HREF="#Header_21" >Installing DCConnect as a Service on Windows NT</A>
<LI><A NAME=PToC_22 HREF="#Header_22" >Directory Structure and Environment Variables Used by DCConnect</A>
</MENU>
<P><B><LI><A NAME=PToC_23 HREF="#Header_23" >Getting Started</A></B>
<MENU>
<LI><A NAME=PToC_24 HREF="#Header_24" >Tutorial Hardware and Software Requirements</A>
<LI><A NAME=PToC_25 HREF="#Header_25" >Starting the Tutorial</A>
</MENU>
<P><B><LI><A NAME=PToC_26 HREF="#Header_26" >Utilities</A></B>
<MENU>
<LI><A NAME=PToC_27 HREF="#Header_27" >DCConnect Backup and Restore Utility</A>
<LI><A NAME=PToC_28 HREF="#HDRDCCONFG" >DCConnect Configuration</A>
<LI><A NAME=PToC_29 HREF="#Header_29" >Set API Environment (OS/2 Only)</A>
</MENU></MENU><HR><P>
<HR>
<H1><A NAME="Header_6" HREF="#PToC_6">DCConnect Overview</A></H1>
<P>DCConnect consists of the following:
<UL COMPACT>
<LI>DCConnect Server for OS/2 and Windows NT
<LI>DCConnect Development Toolkit for OS/2 and Windows NT
</UL>
<TABLE><TR><TD ALIGN=LEFT VALIGN=TOP><B>Note:</B></TD><TD ALIGN=LEFT VALIGN=TOP>
This book uses the term <I>DCConnect</I> when referring
to the installation of the Server or the Development Toolkit products.
</td></tr></table>
<HR>
<H2><A NAME="HDRSRVR" HREF="#PToC_7">Server</A></H2>
<P>The Server product is a data collection server system that
provides a runtime environment for network configuration,
terminal communications management, transaction handling, and an
application programming interface (API).
<P>
You configure your data collection network using the
point-and-click Graphical User Interface (GUI) that
displays the data collection network as a series of
interconnected icons. To configure a network, select an icon
representing the adapter, line, or terminal type from a toolbar
and drop it onto a graphical representation of the network at the
desired location. Then customize the network by selecting the
object and changing its parameters using the settings notebook
for that object. Additional views are provided that show
Transaction/Mailbox configuration, Function Group configuration,
and applications.
<P>
Prior to version 1.4.0, the Server product was sold with option to purchase
different tiers depending on the number of terminals that were to be
configured. Starting with version 1.4.0 only one option for the server is
available, supporting the maximum of 256 configured terminals attached on
any combination of line types: ARTIC, serial,
RF, TCP/IP or DOS/Windows terminals.
<P>
Although 256 terminals
can be configured, the practical maximum number may be less depending
on many factors including the level of transaction activity, the way the
terminals are distributed across the different kinds of lines, the
server processor speed, amount of RAM installed, the other applications
running on the system, the performance of target data bases and/or host
systems, other non-DCConnect traffic on networks, . . .
<HR>
<H2><A NAME="HDRDTOOLK" HREF="#PToC_8">Development Toolkit</A></H2>
<P>
The Development Toolkit is functionally the same as the Server product
except that it provides an editor that is used to create
transaction programs. A transaction program is a set of
terminal-specific commands that run on a data collection
terminal such as the IBM 7524, 7525, 7526, or 7527 terminal, or
terminals supported by the 752x Emulator for DOS.
These commands provide prompts, messages, and input fields.
Transaction programs can also include data validation routines
and dictate terminal interaction with attached devices such as
printers.
<P>
The Development Toolkit, like the Server, provides a runtime environment
for network configuration, terminal communications management,
transaction handling, and an API. Unlike the Server, it supports
only one data collection terminal attached to an active line.
(Many terminals can be configured, but only one can be active.)
<P>For more information, see the online <CITE>DCConnect
User's Guide.</CITE>
<HR>
<H1><A NAME="HDRHSRQ" HREF="#PToC_9">Hardware and Software Requirements</A></H1>
<P>This chapter lists the hardware and software requirements for
the Development Toolkit and Server products. This chapter also introduces the
concept of "networks" of Data Collection Terminals (DCTs) and describes how
they are cabled. A network is limited to a series of terminals
interconnected among themselves and to a communications port.
The communications port can be on an ARTIC adapter, a native
serial port, an adapter that provides support equivalent to the
native serial port, or a TCP/IP-supported adapter. You can
develop your DCT programs using Graphical User Interface (GUI)
tools.
<P>
The following picture shows a typical terminal network setup,
making use of an ARTIC adapter. The same terminal setup can
also be attached to a non-ARTIC RS-422 adapter using the native
COMx support provided by OS/2 or Windows NT.
<P><B><A NAME="FIGNTWR">Figure 1. An Example of a Data Collection Terminal Installation</A></B><BR>
<B><BR><IMG SRC="e9ivnet1.gif" ALT="Figure e9ivnet1 not displayed."><BR></B><BR>
<HR>
<H2><A NAME="Header_10" HREF="#PToC_10">Hardware Requirements</A></H2>
<P>The following are the hardware requirements for DCConnect:
<UL COMPACT>
<LI>IBM-compatible Pentium PC or higher
<LI>120 MHz or higher processor speed
<LI>32 MB RAM
<LI>CD-ROM drive
<LI>SVGA display (recommended)
<LI>77 MB disk space (32 MB for Swap file, 45 MB for DCConnect) in
addition to that required for OS/2 or Windows NT
<LI>Adapters
</UL>
<P>
<H3><A NAME="Header_11" HREF="#PToC_11">Adapters</A></H3>
<P>
The following adapters are supported for attaching terminals:
<UL>
<P><LI><B>Realtime Interface Co-Processor(TM) (ARTIC) Adapters (within the IBM Industrial Computer or PC)</B>
<UL>
<P><LI>Micro Channel(TM) bus Realtime Interface Co-Processor Multiport/2 in one of the following
configurations
<DL COMPACT>
<DD>4-Port RS-422 plus 4-Port RS-232 Electrical Interface Board
<DD>8-Port RS-422 Electrical Interface Board
<DD>8-Port RS-232 Electrical Interface Board
<DD>4-Port RS-232 Electrical Interface Board
</DL>
<P><LI>ISA bus Realtime Interface Co-Processor Multiport
<DL COMPACT>
<DD>4-Port built-in RS-232 Electrical Interface Board
<DD>Additional expansion 4-Port RS-232 or RS-422 Electrical
Interface Board
</DL>
<P><LI>ISA Dual Port ARTIC Adapter
<DL COMPACT>
<DD>2 ports; either port can be RS-232 or RS-422 depending on the
Electrical Interface Board installed
</DL>
<P><LI>Micro Channel bus Realtime Interface Co-Processor Portmaster or ISA bus Multiport model 2
in one of the following configurations
<DL COMPACT>
<DD>8-Port RS-422 Electrical Interface Board
<DD>8-Port RS-232 Electrical Interface Board
</DL>
</UL>
<P>
Up to four ARTIC adapters are supported (any mix of the above
types) in each DCConnect system. The number of Data Collection Terminals (DCTs)
connected to each RS-422 port on each ARTIC adapter is limited
as follows:
<UL COMPACT>
<LI>32 terminals for each port on the Multiport/2, Multiport, and Dual
port
<LI>10 terminals for each port on the Portmaster or Multiport Model 2
</UL>
<P>Terminal types can be mixed on a port, but each terminal on
that port must have a unique address (A-Y, 0-6).
DCConnect
does not support, for example, a 7527 terminal configured
as 'A' and a 7526 terminal configured as 'a' when both of these
terminals are on the same communications line.
<P>
When using the ARTIC adapter, you can set up to eight ARTIC
ports on each
ARTIC adapter. Each ARTIC port can connect up to 32 DCTs
(10 for Portmaster(TM) adapters) through
an RS-422 or RS-485 electrical interface specification.
<P>For information on installing and configuring the 7524 RF
network,
(See<A HREF="#HDR7524">Installing 7524 Interface Support</A>) .
<P>For details on what is required for attaching these DCTs to
the ARTIC adapters on an IBM Industrial Computer or PC, refer to the following IBM
publications:
<UL>
<CITE>
<P><LI>7525 Data Collection Terminal Installation, Setup, and
Problem Determination Guide
<P><LI>7526 Data Collection Terminal Hardware Information
and Site Preparation
<P><LI>7526 Data Collection Terminal Installation, Operation,
and Problem Determination
<P><LI>7526 Data Collection Terminal Maintenance Information
<P><LI>7527 Data Collection Terminal General Information
<P><LI>7527 Data Collection Terminal Installation, Operation,
and Problem Determination
<P><LI>7527 Data Collection Terminal Maintenance Information
</CITE>
</UL>
<P><LI><B>Native Serial Port or Equivalent Adapter</B>
<P>These are the serial ports that are part of the IBM Industrial Computer or PC, or an
adapter, that supports operation compatible with the
COM1-COM4 Character Device I/O support. Under OS/2, this
support is described in the <CITE>OS/2 Warp Command
Reference</CITE> in the Information Folder.
<P>
If you are attaching DCTs to the native RS-232 serial
port or an equivalent RS-232 adapter, only one terminal can
be directly connected to each port. The IBM 7527 and 7524 batch
terminals are the only DCTs that support RS-232
communication to the host PC.
<P>
To connect multiple terminals (including 7525 and 7526 terminals)
to an RS-232 port, an RS-232-to-RS-422 converter must be
connected between the serial port and the line of multidropped
terminals. See the specifications of the converter chosen to
determine how many terminals can be dropped off a single line
(port).
<P>
If the converter supports RS-422, the drivers support only
10 terminals connected over up to 4 000 feet of cable.
If the drivers support the RS-485 specification, they will
accept up to 32 terminals.
<P>
If you have an RS-422 or RS-485 adapter installed in
the IBM Industrial Computer or PC, up to 32 terminals can be configured per line.
However, it is recommended that if more than 10 terminals are
to be connected to a single IBM Industrial Computer or PC, an ARTIC adapter should be
used to off-load the processing needed to handle the
communications for the terminal network.
<P>
Depending on the number of terminals and amount of activity, a
larger number of terminals attached to a non-ARTIC adapter
could degrade the performance of OS/2 or Windows NT and the
applications running on it.
<P>
For more information about cabling of terminals to a serial port
on the IBM Industrial Computer or PC,
(See<A HREF="#HDRCABLE">Native Serial Port Cables</A>) .
<P><LI><B>TCP/IP Supported Adapters</B>
<UL>
<P><LI>7526 Ethernet Network
<P>Although the 7526 terminals have only an Ethernet connection
to a TCP/IP network, the DCConnect PC itself can attach to the
network using any adapter supported by TCP/IP for OS/2 Warp or
TCP/IP for Windows NT, (for example, Ethernet or Token Ring).
<P>A network of 7526 terminals can be configured with up to
256 terminals.
DCConnect interfaces to Ethernet using standard TCP/IP protocols,
specifically user datagram protocol (UDP). As a result,
DCConnect uses the term <I>TCP/IP</I> instead of Ethernet for
configuration items dealing with the Ethernet network.
<P><LI>DOS or Windows Terminal Network
<P>Any adapter supported by TCP/IP for OS/2 Warp or Windows NT
can be used to connect to a network of PCs running Terminal Services for DOS and for Windows. Up to
256 PCs can be connected. Depending on the number of PCs
connected and the amount of activity, a large number of PCs could
degrade the performance of the operating system and the
applications running on it. For more information about
installing the TCP/IP supported adapter, refer to your TCP/IP
documentation.
</UL>
<P><LI><B>RF Terminal Network</B>
<P>A network of 7524 radio frequency (RF) terminals includes a
7524 network controller that attaches to the
DCConnect PC at one of
its COMx ports. The 7524 RF controller cannot be attached to an
ARTIC port. The COMx port used to attach to the RF controller
cannot be used to attach directly to other 752x terminals.
<P><B>Note: </B>Although IBM no longer logos the 7524 equipment from Intermec/Norand, the
equivalent Intermec equipment is supported: 11xx, 17xx and 59xx terminals,
3250 and RC4030E controllers, RB4030E bases, 6710 and 2100 access points.
<P>For information on installing and configuring a 7524 RF
network,
(See<A HREF="#HDR7524">Installing 7524 Interface Support</A>) .
<P>
For information about setting up communications adapters and
DCTs,
(See<A HREF="#HDRHARDINS">Installing Native Serial Ports and Data Collection Terminals</A>) .
</UL>
<P>
<H3><A NAME="HDR3012" HREF="#PToC_12">Devices Supported by DCConnect</A></H3>
<P>All models of the IBM 7524, 7525, 7526, and 7527 DCTs
are supported in any combination.
<P>
In addition, certain specific models from serveral 3rd party terminal
vendors are supported. Support of these 3rd party terminals requires one
license, per terminal, of the IBM 752x Emulator for DOS. As of July 1999,
the following 3rd party terminals are supported:
<PRE>
Data Collection Terminal Screen Connectivity
------------------------ ------ ------------
Intermec 6540 4x40 Wired ethernet or serial, RF optional
Intermec MaxiLAN DX 200S/200H (former name of Intermec 6540)
Intermec Janus 2010 16x20 Portable RF/batch serial - flashlight
Intermec Janus 2020 16x20 Portable RF/batch serial - gun style
Intermec Janus 2050 20x40 Vehicle mount RF
Symbol FMT1020 2x40 Wired ethernet or serial
Symbol FMT1040 2x40 Wired ethernet or serial
Symbol FMT1060 2x40 Wired ethernet or serial
Symbol LRT3840 8x20 Portable RF - gun style
Symbol PDT3140 8x20 Portable RF - flashlight style
Symbol VRC3940 8x20 Vehicle mount RF
Symbol WSS1140 8x20 Wearable RF
Symbol PDT6840 16x20 Portable RF - flashlight style
Telxon 960SL/960X 16x20 Portable RF - gun style
Telxon 860IM 8x40 Vehicle mount RF
IBM 2483 = Telxon 960X
IBM 2493 = Telxon 960SL
IBM 2484 = Telxon 860IM
</PRE>
<P>For an up-to-date list of supported terminals, please visit our website:
<PRE>
http://www.software.ibm.com/data/dcconnect
</PRE>
and follow the links to '3rd party terminals'.
<P>The IBM 7524 RF terminal requires the IBM 7524 Interface
Support product to be installed on any PCs that have a 7524
controller attached. Batch 7524 terminals can be serially
attached to a PC or ARTIC card; therefore, they do not require
the 7524 Interface Support product. PCs that have been
programmed for interaction with DCConnect using the API supplied
with the Terminal Services for DOS and for Windows product are also supported through a TCP/IP
connection. A maximum of 256 devices can be connected to a
single Server PC. However, the practical limit may be less,
depending on your PC's capabilities and the amount of data
collection device activity.
<P>Fixed-station terminals (IBM 7524 batch, 7525, 7526, and 7527)
can be attached to a PC's serial port or an ARTIC adapter.
<UL COMPACT>
<LI>To connect to the PC's serial port, use an
RS-232-to-RS-422/485 adapter to multidrop up to 32 terminals off
a single line (no more than 10 terminals are recommended because
of the impact on system performance). If only 1 terminal is
attached to the PC's serial port, the RS-232 port on the
terminal can be used as the host PC connection (for those
terminals that have RS-232 capabilities). If the terminal's
serial port and PC or ARTIC serial ports are RS-422/485, up to
32 terminals can be multidropped. However, due to the potential
impact on system performance, it is recommended that no more than
10 terminals be attached to a PC's serial port.
<LI>ARTIC adapters installed with the correct electronic
interface board (EIB) and cable are supported on OS/2 and Windows
NT systems.
<TABLE><TR><TD ALIGN=LEFT VALIGN=TOP><B>Note:</B></TD><TD ALIGN=LEFT VALIGN=TOP>When you are using the ARTIC RS-232 EIB, an
RS-232-to-RS-422/485 converter must be used. If you don't use
this converter, the port will support only a single terminal at a
distance of 50 feet or less (unless an RS-232 repeater is used).
</td></tr></table>
<LI>7526 terminals with Ethernet adapters can be attached
for TCP/IP-based communications.
</UL>
<HR>
<H2><A NAME="Header_13" HREF="#PToC_13">Software Requirements for OS/2</A></H2>
<P>DCConnect requires OS/2 Warp, Warp Connect, or later version
to be running on the hardware
previously specified.
<TABLE><TR><TD ALIGN=LEFT VALIGN=TOP><B>Note:</B></TD><TD ALIGN=LEFT VALIGN=TOP>
REXX support must be installed.
</td></tr></table>
<P><B>Optional Software</B>
<P>The following is optional software that may be needed:
<UL>
<P><LI><B>7524 Interface Support (5696-977)</B>
<P>If any 7524 RF-based DCTs are used.
<P><LI><B>Development Toolkit (5639-H35) or Transaction Building Tool (5639-H37)</B>
<P>To create and modify transaction programs.
<P><LI><B>Terminal Services for DOS and for Windows (5639-H39)</B>
<P>To use any DOS or Windows PCs as DCTs.
<P><LI><B>COM.SYS - OS/2 Communications Device Driver</B> and
<B>VCOM.SYS - OS/2 Communications Virtual Device Driver</B>.
<P>
To use the native serial port of the IBM Industrial Computer or PC.
<P>Statements for starting these device drivers must be included
in the OS/2 CONFIG.SYS file. For example, if OS/2 is installed
on drive F, the following statements are needed in the
OS/2 CONFIG.SYS file:
<BLOCKQUOTE>
<PRE>
DEVICE=F:\OS2\COM.SYS
DEVICE=F:\OS2\MDOS\VCOM.SYS
</PRE>
</BLOCKQUOTE>
<P><LI><B>IBM C/2 Compiler</B>
<P>To develop Custom Function Routines (CFRs).
<P>The compiler can be run either on a DOS system or on an
OS/2 system.
<P><LI><B>IBM VisualAge 3.0 Compiler
IBM C Set++ Compiler
IBM C Set/2 Compiler</B>
<P>Use any one of these compilers to develop DCConnect applications.
<P><LI><B>OS/2 TCP/IP 2.0 (UN64092) or later</B>
<P>To use 7526 (using Ethernet) and to use the Terminal Services for DOS and for Windows product.
<P>To send transactions to MAPICS/XA on an AS/400(TM).
</UL>
<HR>
<H2><A NAME="Header_14" HREF="#PToC_14">Software Requirements for Windows NT</A></H2>
<P>
DCConnect requires Windows NT 4.0 or later to be running on the hardware previously
specified.
<TABLE><TR><TD ALIGN=LEFT VALIGN=TOP><B>Note:</B></TD><TD ALIGN=LEFT VALIGN=TOP>
To listen to the Tutorial, you must have a supported sound card,
and Multimedia support must be installed.
However, you can run the tutorial without a sound card by
following the instructions displayed on the screen.
</td></tr></table>
<P><B>Optional Software</B>
<P>The following is optional software that may be needed:
<UL>
<P><LI><B>7524 Interface Support (5696-977)</B>
<P>If any 7524 RF-based DCTs are used.
<P><LI><B>Development Toolkit (5639-H35) or Transaction Building Tool (5639-H37)</B>
<P>To create and modify transaction programs.
<P><LI><B>Terminal Services for DOS and for Windows (5639-H39)</B>
<P>To use any DOS or Windows PCs as DCTs.
<P><LI><B>IBM VisualAge(TM) 3.5 Compiler
Microsoft(TM) Visual C++ 4.0 or later</B>
<P>Use any one of these compilers to develop DCConnect applications.
</UL>
<HR>
<H1><A NAME="HDRINST" HREF="#PToC_15">DCConnect Installation</A></H1>
<P>
The prerequisite hardware and software,
(See<A HREF="#HDRHSRQ">Hardware and Software Requirements</A>) , must be installed before DCConnect can be
installed.
<P><B>
Be sure to read this chapter thoroughly before proceeding to the
actual installation.
</B>
<P><B>Note: </B>Although the various DCConnect and ERPBridge products now ship on
separate CDs, the instructions that follow apply to any of these CDs, except
where noted.
<HR>
<H2><A NAME="Header_16" HREF="#PToC_16">Viewing Files from the CD-ROM Before Installing</A></H2>
<P>
You can view the read.me file, Tutorial, or online
documentation (for example, the
<CITE>DCConnect User's Guide</CITE>), directly from
the CD-ROM without adding files to your hard disk.
<P><B>To view the read.me file, do the following:</B>
<OL COMPACT>
<LI>Insert the product
CD in the CD-ROM drive.
<LI>Open a command prompt (under OS/2, this is an OS/2 window or
full-screen session; under Windows NT, this is a DOS prompt).
<LI>From the command line, change to the CD-ROM drive.
<LI>Type <B>print read.me</B> (to print)
or
<B>(On OS/2) e read.me</B> (to view online)
or
<B>(On Windows NT) edit read.me</B> (to view online)
</OL>
<P><B>To view the Tutorial, do the following:</B>
<P><B>Note: </B>The tutorial is provided only on the CDs for the DCConnect Server and
the DCConnect Toolkit.
<OL COMPACT>
<LI>Insert the product CD in the CD-ROM drive.
<LI>Open a command prompt.
<LI>From the command line, change to the CD-ROM drive.
<LI>Change to the directory containing the tutorial, for example:
<PRE>
cd \tutorial
</PRE>
<LI>Type: <B>tutorial</B>
</OL>
<P><B>To view online documentation, do the
following:</B>
<OL COMPACT>
<LI>Insert the product CD in the CD-ROM drive.
<LI>Start a frame-enabled browser such as Netscape
<LI>Enter the following URL:
<PRE>
file:///d:\manuals\index.htm
</PRE>
where d: is the drive letter for the CD-ROM drive.
<LI>This will provide a list of the available manuals. Just click on
the name of the manual you want to read. Also provided is a link to
the DCConnect/ERPBridge home page.
</OL>
<HR>
<H2><A NAME="HDRINSDISK" HREF="#PToC_17">Installing DCConnect Products</A></H2>
<P>
Perform the following steps to install DCConnect products:
<OL>
<P><LI>Insert the appropriate product CD into the CD-ROM drive on your
personal computer.
<P><LI><B>(On OS/2)</B> Bring up the <B>Drives</B> icon.
<P><B>(On Windows NT)</B> Start the <B>Windows/NT Explorer</B>
<P><LI>Select the CD drive
<P><LI><B>(On OS/2)</B> Click on <B>setupos2</B>
<P><B>(On Windows NT)</B> Click on <B>setup</B>
<P><LI>Follow the screen instructions as the installation program
steps you through the rest of the process.
<P>
If DCConnect or one of the features is being reinstalled, a prompt
appears asking if existing data files should be preserved or
overwritten during the reinstall process.
<P><LI>When all selected software has been installed, pull down the
<B>File</B> menu and choose <B>Exit</B>.
<P><LI>Be sure to store the CD in a secure place.
</OL>
<P><B>(On OS/2)</B> If this is a first-time installation of
DCConnect and you also have the DCC/2 32 bit product installed,
you are asked if you would like to migrate your DCC/2 data files
to DCConnect.
<P>Select <B>Yes</B> or <B>No.</B>
<HR>
<H2><A NAME="Header_18" HREF="#PToC_18">Starting DCConnect Development Toolkit or Graphical User Interface</A></H2>
<P>To start the graphical user interface for the DCConnect Development Toolkit or
Server, open the DCConnect folder on the Desktop and
double-click on the
DCConnect User Interface icon using mouse button 1.
<HR>
<H2><A NAME="Header_19" HREF="#PToC_19">Starting DCConnect Server on OS/2</A></H2>
<P>
DCConnect Server is the nongraphical user interface part of
DCConnect.
<P>
To set up the DCConnect Server executable so that it starts when OS/2 starts, add the
following to the OS/2 STARTUP.CMD file assuming DCConnect was installed
on drive C:
<BLOCKQUOTE>
<PRE>
c:
cd \dcconn\bin
dcxcpos2
</PRE>
</BLOCKQUOTE>
<P>where c: and \dcconn are the drive and directory where DCConnect
is installed and dcxcpos2 is the executable file for the server.
<P>To run an unattended system or to start
the Server and bring up the DCConnect User Interface at a later
time, start the Server from a command prompt.
<P><B>Note: </B>You can enter commands in either lowercase or uppercase.
<P>To start the Server executable from the command line C:
prompt, do the following:
<OL>
<P><LI>Change to the directory where DCConnect is installed. For example:
<PRE>
c:
cd \dcconn\bin
</PRE>
<P>
where C: is the drive and DCCONN\BIN is the directory.
<P><LI>Type: <B>dcxcpos2</B>
<P><LI>Press <B>Enter</B>.
</OL>
<HR>
<H2><A NAME="Header_20" HREF="#PToC_20">Starting DCConnect Server on Windows NT</A></H2>
<P>
DCConnect Server is the nongraphical user interface part of
DCConnect.
<P>
To set up the DCConnect Server executable so that it starts when Windows NT starts,
add the Server executable to the Startup folder by following
these steps:
<OL>
<P><LI>Open the Taskbar Properties by clicking on the
<B>Start button</B>, and then moving the
mouse up to Settings and over to Taskbar.
<P><LI>Select the Start Menu Programs page by clicking on the
<B>index</B>
at the top of the box.
<P><LI>Click on the <B>Add</B> button.
<P><LI>Type <B><I>c:\dcconn</I></B><B>\bin\dcxcpos2</B>
where <I>c:\dcconn</I> is the directory where DCConnect
was installed. You can also choose to use the Browse button to
find DCXCPOS2 in the directory where you installed DCConnect.
<P><LI>Either press <B>Enter</B> or click on <B>Next</B>
to move to the next
window where you select the folder in which
to put the DCConnect server.
<P><LI>Select the <B>Startup</B> folder and click on <B>Next</B>.
<P><LI>Enter <B>DCConnect Server</B> or any name you want for
the DCConnect server icon and click on <B>Finish.</B>
<P><LI>Click <B>OK</B> to close the Taskbar dialog.
</OL>
<P>The next time you start Windows NT and log on, the DCConnect
Server is started.
<P>To run an unattended system or to start
the server and bring up the DCConnect User Interface at a
later time, start the server from a command prompt.
<P><B>Note: </B>You can enter commands in either lowercase or uppercase.
<P>To start the server executable from the command line C:
prompt, do the following:
<OL>
<P><LI>Change to the directory where DCConnect is installed.
<PRE>
c:
cd \dcconn\bin
</PRE>
<P>
where C: is the drive and DCCONN is the directory where
DCConnect is installed.
<P><LI>Type: <B>dcxcpos2</B>
<P><LI>Press <B>Enter</B>.
</OL>
<HR>
<H2><A NAME="Header_21" HREF="#PToC_21">Installing DCConnect as a Service on Windows NT</A></H2>
<P>
If you want the DCConnect Server to start without a user login
whenever the PC boots to Windows NT, you need to configure the
DCConnect service in the Windows NT <B>Control Panel.</B>
This configuration is useful once DCConnect is fully configured and
tested, as it allows the system to recover immediately from a
power outage without any user intervention.
Follow these steps:
<OL>
<P><LI>Open the <B>Control Panel.</B>
<P><LI>Double-click on the <B>Services</B> icon.
<P><LI>Select <B>DCConnect</B> from the services list.
<P><LI>Click on <B>Startup.</B>
<P><LI>Select the appropriate <B>Startup Type</B> from the top
of the window. (Typically, the Startup Type is
<B>Automatic</B>.)
<P><LI>Select an entry under <B>Log On As</B>.
<TABLE><TR><TD ALIGN=LEFT VALIGN=TOP><B>Note:</B></TD><TD ALIGN=LEFT VALIGN=TOP><B>This Account</B> with a User ID and password is the
recommended response.
</td></tr></table>
<P><LI>If you select <B>System Account</B>, you can also select
<B>Allow Service to Interact with Desktop.</B>
<P><LI>Click on <B>OK</B> to close the Service Setup for
DCConnect.
<P><LI>Click on <B>Start</B> to start the DCConnect service.
<P><LI>Click on <B>Close</B> to close the Services window.
<P><LI>Close the <B>Control Panel</B>.
</OL>
<P>
If the DCConnect service is set to login with a particular user
name and password, a user who logs in to Windows NT using the
same user name and password as DCConnect uses can start other
DConnect applications (such as the Graphical User Interface).
These applications can interact with the DCConnect Server
started via the service. However, the text-mode server window
itself is not visible to any user. Any applications registered
with DCConnect in the Applications folder that has the
<B>Autostart</B> box checked also automatically start
when the DCConnect server starts, but the applications are not
visible.
<P>
If the DCConnect service uses the system account to login, the
DCConnect server window is visible. However, user applications
cannot access DCConnect, and therefore the User Interface cannot
display the status of terminals, mailboxes, and so forth, even
though the DCConnect Server is running. However, it is possible
to see the Server window and the window for any applications that
are started by the server.
<P>
Because there is no method for determining the state of the data
collection system if the DCConnect service uses the system account,
it is recommended that you use a user account. The disadvantage
of not being able to see the DCConnect Server window is minimized
by the ability to use the User Interface to view the status of
the Server. There is no such offsetting advantage for a system
account login because no user program can interact with the
server.
<HR>
<H2><A NAME="Header_22" HREF="#PToC_22">Directory Structure and Environment Variables Used by DCConnect</A></H2>
<P>
When DCConnect is installed, it creates the following subdirectories
relative to the target path (default is C:\DCCONN) specified during
the installation:
<BLOCKQUOTE>
<PRE>
c:\dcconn\bin - Executables
data - Configuration, mailbox logfiles,
system error message file
dll - Dynamic link libraries
include - API header file
help - Message and online documentation
lib - API library
val - Validation files
graph - Graphics files
cfr - Custom Function Routines (CFRs)
job - Terminal job and program files
samples - Sample API code and executables
</PRE>
</BLOCKQUOTE>
<P>
The base directory (in this case, C:\DCCONN) is assigned to the
environment variable <I>DCCONN</I>. This environment
variable is used by DCConnect to determine where its data files are
installed.
<P>
<B>(On OS/2)</B> The original DCC/2 product used the
environment variables
<I>DCCROOT, DCC,</I> and <I>DCXROOT</I> to determine
where DCC/2 was installed and where its data files were located.
<P>
<I>DCCONN, DCXROOT,</I> and <I>DCCROOT</I>
should not indicate the same directory.
<HR>
<H1><A NAME="Header_23" HREF="#PToC_23">Getting Started</A></H1>
<P>
To help you become familiar with using DConnect, the Server and Toolkit
product CDs include an online interactive tutorial. The tutorial
leads you through setting up a typical system.
We recommend that you run through the tutorial at least once
before using the product. You can rerun specific sections of it
later to refresh yourself on particular functions.
<TABLE><TR><TD ALIGN=LEFT VALIGN=TOP><B>Note:</B></TD><TD ALIGN=LEFT VALIGN=TOP>
If your Personal Computer does not have a sound card to allow you
to hear audio instructions, you can follow the instructions
displayed on the screen.
</td></tr></table>
<P>
The tutorial covers the following areas of the Toolkit and Server
products:
<UL COMPACT>
<LI>System Operation
<LI>Node Configuration
<LI>Function Group Configuration
<LI>Transaction Mailbox Configuration
<LI>Transaction Program Editor
<LI>Validation File Editor
</UL>
<HR>
<H2><A NAME="Header_24" HREF="#PToC_24">Tutorial Hardware and Software Requirements</A></H2>
<P><B>Hardware</B>
<P>
The following hardware is required as a minimum to run the
tutorial:
<UL COMPACT>
<LI>IBM Compatible 486 or higher Personal Computer
<LI>3.5 MB of RAM
<LI>SVGA display (recommended)
<LI>Sound card (if audio instructions are desired)
</UL>
<P><B>Software</B>
<P>
One of the following products is required to run the tutorial:
<UL COMPACT>
<LI>OS/2 WARP or WARP Connect with WIN-OS/2(TM) support installed
<LI>Windows 3.1
<LI>Windows 95
<LI>Windows NT
</UL>
<HR>
<H2><A NAME="Header_25" HREF="#PToC_25">Starting the Tutorial</A></H2>
<P>You can run the tutorial either before or after DCConnect is
installed.
<P><B>To start the tutorial before DCConnect is installed:</B>
<OL COMPACT>
<LI>Insert the DCConnect Server or Toolkit CD into the CD-ROM drive.
<LI>Open a command prompt.
<LI>From the command line, change to the CD-ROM drive.
<LI>Change to the directory containing the tutorial, for example:
<PRE>
cd \tutorial
</PRE>
<LI>Type: <B>tutorial</B>
</OL>
<HR>
<H1><A NAME="Header_26" HREF="#PToC_26">Utilities</A></H1>
This chapter describes the DCConnect utilities.
<HR>
<H2><A NAME="Header_27" HREF="#PToC_27">DCConnect Backup and Restore Utility</A></H2>
<P>
The DCConnect Backup and Restore Utility allows you to back up all
the files that make up a DCConnect configuration for a
DCConnect system. You can back up the configuration either to a set
of diskettes or to a hard disk directory location. The hard disk
is ideal for short-term backups while you make changes to the
DCConnect configuration. For long-term backups, it is recommended
that you use the diskette option. The backup
diskettes can then be stored for safe keeping or they can be
used to restore to other DCConnect systems, if you need to replicate
a DCConnect environment.
<P><B>Note: </B>Backups from the DCC/2 32-bit Runtime can be restored using this utility.
<P>
The following types of files make up a DCConnect configuration
and are copied to and from the backup location during the
backup and restore process.
<TABLE CELLPADDING=3>
<TR VALIGN=TOP><TD><B>DCConnect configuration files
</B></TD><TD>dcconn\data\dcx2.ini
dcconn\data\dc*.dat
dcconn\data\messages.dat
</TD></TR><TR VALIGN=TOP><TD><B>Extra configuration file
</B></TD><TD>dcconn\data\extra.cfg
</TD></TR><TR VALIGN=TOP><TD><B>Job files/Transction programs
</B></TD><TD>dcconn\job\*.*
</TD></TR><TR VALIGN=TOP><TD><B>Graphics files
</B></TD><TD>dcconn\graph\*.*
</TD></TR><TR VALIGN=TOP><TD><B>CFR files
</B></TD><TD>dcconn\cfr\*.*
</TD></TR><TR VALIGN=TOP><TD><B>Validation files
</B></TD><TD>dcconn\val\*.*
</TD></TR><TR VALIGN=TOP><TD><B>Artic Configuration
</B></TD><TD>dcconn\bin\icaparm.prm
</TD></TR><TR VALIGN=TOP><TD><B>CS2 (DAE) Configuration
</B></TD><TD>\cs2\sys\cfscbf0*.cfs
</TD></TR></TABLE>
<P>The DCConnect Toolkit and Server product must be shut down before
you start either a Backup or a Restore operation.
<P>
Start the DCConnect Backup and Restore Utility by opening
the DCConnect folder located on the Desktop and
double-clicking on the DCConnect Backup and Restore Utility icon.
On Windows/NT this selection can be made from the Start button:
<PRE>
Start -> Programs -> DC Connect -> DC Connect Backup and Restore Utility
</PRE>
<P>
You can select the operation to be performed by clicking on
either the Backup or Restore radio buttons. The Backup/Restore
drive is selected by clicking a drive spin button. If the
selected drive is a nondiskette drive, you will be required to
enter the complete Backup/Restore directory path location.
During a Backup operation, if the directory name entered does not
currently exist, the Backup and Restore utility creates it.
<P>
During the diskette backup process, you are prompted to insert
blank diskettes in the selected diskette drive. However, you
will be able to format each diskette before files are copied to
it.
<P>
The diskette backup process also creates the file
<B>dcxstart.bak</B> on the
first backup diskette and creates the file
<B>dcxend.bak</B> on the last diskette in
the set. These files indicate how many diskettes were used for
the restore process. Do not delete these files from the backup
diskettes if you intend to restore from them.
<P>
The diskette restore process prompts you to insert each diskette
and copies the files on the diskettes to the appropriate DCConnect
directories.
<P><B>Attention</B> During the
restore process, the current DCConnect environment
is overwritten if a file with the same name is being restored.
<P>
If you attempt to restore a backup from one computer onto a
different computer or attempt to restore a backup from one
operating system to another operating system, the Backup and
Restore Utility will give you instructions on how to complete the
migration of the configuration.
<HR>
<H2><A NAME="HDRDCCONFG" HREF="#PToC_28">DCConnect Configuration</A></H2>
<P>
The DCConnect Configuration utility is called during the installation
process. The utility is made up of three entry fields: the DCConnect
node name, the TCP/IP node address, and a "well known
port" number. The node name field information is required
and must be entered, whereas the other two TCP/IP information
fields are optional.
<P>
The node name you provide must be from one to eight characters in
length. This name is used to identify this Data Collection
Connection node.
<P>
The TCP/IP node address and "well known port" number
information is required only if you will be using the Terminal Services for DOS and for Windows
product. During the configuration of a Terminal Services for DOS and for Windows PC, this
information is needed to make a TCP/IP connection to the DCConnect
node.
<P>
The TCP/IP node address refers to the local DCConnect Server
TCP/IP node address. The "well known port" number is
preloaded with a default number. This number can be changed if it
conflicts with another port in your TCP/IP network.
<P>
If in the future you need to change or add to any of the
configuration information you entered during installation, you
can start the utility as follows:
<OL COMPACT>
<LI>Shut down the Data Collection Connection Toolkit or Server
product.
<LI>Open the <B>DCConnect</B> folder located on the Desktop.
On Windows/NT you can also use the Start button:
<PRE>
Start -> Programs -> DC Connect
</PRE>
<LI>Select the <B>DCConnect Configuration</B> icon.
</OL>
<TABLE><TR><TD ALIGN=LEFT VALIGN=TOP><B>Note:</B></TD><TD ALIGN=LEFT VALIGN=TOP>
Changes to any of the fields require that each of the
Terminal Services for DOS and for Windows PC terminals be reconfigured with the new information.
Be sure to
(See<A HREF="#HDRCRCON">Creating the Terminal Services for DOS and for Windows Configuration Diskette</A>) and
(See<A HREF="#HDRCONTDW">Configuring Terminal Services for DOS and for Windows</A>) .
in this book.
</td></tr></table>
<HR>
<H2><A NAME="Header_29" HREF="#PToC_29">Set API Environment (OS/2 Only)</A></H2>
<P>
If you have data collection applications that use either the
16-bit or 32-bit DCC/2 APIs to communicate with either the DCC/2
16-bit or DCC/2 32-bit runtime, you may need to run those
applications with the DCC/2 runtime after installing DCConnect.
<P>
In order for those applications to run properly with one of the
DCC/2 runtimes, the API environment must be set to work with that
runtime. When DCConnect is installed, the API environment is
automatically set so that existing applications can run with
DCConnect.
<P>
The Set API Environment utility allows you to select where 16-bit
and 32-bit APIs are to be routed. When this utility is started,
you will be prompted to choose the runtime that you will be
using. The utility can be started as follows:
<OL COMPACT>
<LI>Shut down the Data Collection Connection Toolkit or Server
product.
<LI>Open the <B>DCConnect</B> folder located on the OS/2 Desktop.
<LI>Double-click on the <B>DCConnect Set API Environment</B> icon.
</OL>
<P>
After your selection is made, the utility renames DLLs in the
directories of the different runtimes so that the APIs are
properly routed to the runtime that you specified.
<P>
Before you make your selection, the utility indicates where the
16-bit and 32-bit APIs are currently routed. If more than one
runtime is listed, look at the LIBPATH statement
in your CONFIG.SYS to determine where the APIs will be routed.
<P><B>Note: </B>Once DCConnect is installed, the DCC/2 32-bit Migration Utility should <B>not</B>
be used to change the API environment before because DCC/2 does not know
about DCConnect and it therefore will not set up the API environment correctly.
<HR>
<H1><A NAME="HDRPART2" HREF="#PToC_30">Installing Other ERPBridge Products</A></H1>
<P><A NAME="PToC2" HREF="#ToC">Partial Table-of-Contents</A>
<MENU>
<P><B><LI><A NAME=PToC_31 HREF="#HDR7524" >Installing 7524 Interface Support</A></B>
<P><B><LI><A NAME=PToC_32 HREF="#Header_32" >Installing and Configuring Transaction Connection</A></B>
<MENU>
<LI><A NAME=PToC_33 HREF="#Header_33" >Prerequisite Hardware and Software</A>
<LI><A NAME=PToC_34 HREF="#Header_34" >Installing Transaction Connection</A>
<LI><A NAME=PToC_35 HREF="#HDRCONFGCM" >Configuring Personal Communications</A>
<LI><A NAME=PToC_36 HREF="#Header_36" >Starting Transaction Connection Script Files</A>
<LI><A NAME=PToC_37 HREF="#HDRSTRTDB" >Starting Transaction Connection</A>
<LI><A NAME=PToC_38 HREF="#Header_38" >Multiple Sessions</A>
</MENU>
<P><B><LI><A NAME=PToC_39 HREF="#HDRJDE" >ERPBridge for J.D. Edwards</A></B>
<P><B><LI><A NAME=PToC_40 HREF="#HDRMAPICS" >Installing and Configuring ERPBridge for MAPICS</A></B>
<MENU>
<LI><A NAME=PToC_41 HREF="#Header_41" >Prerequisite Hardware and Software</A>
<LI><A NAME=PToC_42 HREF="#Header_42" >Installing ERPBridge for MAPICS</A>
<LI><A NAME=PToC_43 HREF="#Header_43" >MAPICS XA Release 2.2 and Release 2.3</A>
<LI><A NAME=PToC_44 HREF="#Header_44" >Configuring ERPBridge for MAPICS</A>
<LI><A NAME=PToC_45 HREF="#Header_45" >Configuring Personal Communications</A>
</MENU>
<P><B><LI><A NAME=PToC_46 HREF="#Header_46" >Installing Terminal Services for DOS/Windows</A></B>
<MENU>
<LI><A NAME=PToC_47 HREF="#HDRPREQHWS" >Prerequisite Hardware and Software</A>
<LI><A NAME=PToC_48 HREF="#HDRCRCON" >Creating the Terminal Services for DOS and for Windows Configuration Diskette</A>
<LI><A NAME=PToC_49 HREF="#HDRINSDOSW" >Installing Terminal Services for DOS and for Windows on the DOS or Windows PC</A>
<LI><A NAME=PToC_50 HREF="#HDRCONTDW" >Configuring Terminal Services for DOS and for Windows</A>
<LI><A NAME=PToC_51 HREF="#Header_51" >Directory Structure and Environment Variables Used by Terminal Services for DOS and for Windows</A>
</MENU>
<P><B><LI><A NAME=PToC_52 HREF="#Header_52" >Installing the DCConnect Transaction Building Tool</A></B>
<MENU>
<LI><A NAME=PToC_53 HREF="#Header_53" >Installing the Transaction Building Tool</A>
</MENU>
<P><B><LI><A NAME=PToC_54 HREF="#HDRNOTICES" >Notices</A></B>
<MENU>
<LI><A NAME=PToC_55 HREF="#Header_55" >Trademarks</A>
</MENU>
<P><B><LI><A NAME=PToC_56 HREF="#HDRHARDINS" >Installing Native Serial Ports and Data Collection Terminals</A></B>
<MENU>
<LI><A NAME=PToC_57 HREF="#HDRHSTEP2" >Plant Wiring Installation</A>
<LI><A NAME=PToC_58 HREF="#Header_58" >Installing RS-422 Cable</A>
<LI><A NAME=PToC_59 HREF="#HDRDCTHSU" >Data Collection Terminal Hardware Setup</A>
<LI><A NAME=PToC_60 HREF="#HDROPS" >DCT Operating Parameter Setup</A>
<MENU>
<LI><A NAME=PToC_61 HREF="#HDR25SETUP" >7525 Terminal Setup</A>
<LI><A NAME=PToC_62 HREF="#HDR26SETUP" >7526 Terminal Setup</A>
<MENU>
<LI><A NAME=PToC_63 HREF="#Header_63" >Starting Setup Mode</A>
<LI><A NAME=PToC_64 HREF="#Header_64" >Setup Mode Key Usage</A>
<LI><A NAME=PToC_65 HREF="#HDRSETTAB" >Setup Configuration Items</A>
</MENU>
<LI><A NAME=PToC_66 HREF="#HDR27SETUP" >7527 Terminal Setup</A>
<LI><A NAME=PToC_67 HREF="#HDR24RFSTP" >7524 RF Terminal Setup</A>
<LI><A NAME=PToC_68 HREF="#Header_68" >7524 Batch Terminal Setup</A>
</MENU></MENU>
<P><B><LI><A NAME=PToC_69 HREF="#HDRCABLE" >Native Serial Port Cables</A></B>
<MENU>
<LI><A NAME=PToC_70 HREF="#Header_70" >Cabling RS-232 Computer Port to RS-232 Terminal Port</A>
<LI><A NAME=PToC_71 HREF="#Header_71" >Cabling RS-232 Computer Port to RS-422 Terminal Port</A>
</MENU>
<P><B><LI><A NAME=PToC_72 HREF="#HDRINDEX_START" >Index</A></B>
</MENU><HR><P>
<HR>
<H1><A NAME="HDR7524" HREF="#PToC_31">Installing 7524 Interface Support</A></H1>
<P>The 7524 Interface Support (7524 IS) product was shipped on the single
ERPBridge/DCConnect CD - the latest being the -03 revision. This product
was not moved to its own CD when other products were moved to their own 1.4.0
version on separate CDs.
<P>
Therefore this and future versions of the Installation and Configuration
guide do not include installation instructions for 7524 IS.
Please refer to the version of this guide on the -03 CD for those
installation instructions - including instructions for installing CD
Showcase.
<P>
However, the 1.4.0 version of the DCConnect Server and Toolkit will work
properly with the version of 7524 IS from the -03 CD. In
fact, if 7524 IS is installed after the 1.4.0 version of the DCConnect
Server (which is required because of prerequisites), the DCConnect Server
does not have to be reinstalled.
<P><B>Note: </B>Although IBM no longer logos 7524 terminals from Intermec/Norand, the equivalent
Intermec terminals (11xx, 17xx and 59xx) are supported when they are loaded
with the 7524 ETS flash.
<HR>
<H1><A NAME="Header_32" HREF="#PToC_32">Installing and Configuring Transaction Connection</A></H1>
<P>The Transaction Connection product lets you integrate
IBM's DCConnect data collection solutions into a
Database 2(TM) (DB2) database
and/or AS/400 or 3270 applications. Transaction Connection
supports IBM 7524, 7525, 7526, 7527 DCTs, or a supported device running either
Terminal Services for DOS and for Windows or 752X Emulator for
DOS. Transaction Connection:
<UL COMPACT>
<LI>Sets up and performs database updates
<LI>Responds immediately to terminal requests
<LI>Manipulates transaction and database data
<LI>Performs database queries
<LI>Provides an interface between IBM's software and a host
application screen
<LI>Can be easily customized to your needs
</UL>
<HR>
<H2><A NAME="Header_33" HREF="#PToC_33">Prerequisite Hardware and Software</A></H2>
<P>The following hardware and software should be installed before
you install Transaction Connection.
<P><B>Hardware</B>
<UL>
<P><LI>For AS/400 or 3270 connectivity
<P><LI>3270 or 5250 Emulation adapter or token-ring adapter that is
supported by IBM eNetwork Personal Communications Versoin 4.2 for OS/2,
Windows NT, Windows 95
</UL>
<P><B>Software</B>
<UL>
<P><LI>For database connectivity
<P>DB2 Version 5.2, Universal Database Personal Edition (P/N: 31L1533)
<P><LI>For AS/400 or 3270 connectivity
<P>IBM eNetwork Personal Communications Version 4.2 for OS/2, Windows NT,
Windows 95 (P/N: 4074548).
</UL>
<P>
Before you can use Transaction Connection to access a database,
you must start DB2 and log on. A database must be accessible to
the DB2 system. You need
information about the table names, column names and types, and
you must have administrator access authority for the logon on
which Transaction Connection will operate.
<HR>
<H2><A NAME="Header_34" HREF="#PToC_34">Installing Transaction Connection</A></H2>
<P>To install Transaction Connection, do the following:
<OL COMPACT>
<LI>Insert the product CD into the CD-ROM drive on your
personal computer.
<LI><B>(On OS/2)</B> Bring up the <B>Drives</B> icon.
<P><B>(On Windows NT)</B> Start the <B>Windows/NT Explorer</B>
<LI>Select the CD drive
<LI><B>(On OS/2)</B> Click on <B>setupos2</B>
<P><B>(On Windows NT)</B> Click on <B>setup</B>
<LI>Follow the screen instructions as the installation program
steps you through the rest of the process.
</OL>
<P>The Transaction Connection product is installed on your system.
<HR>
<H2><A NAME="HDRCONFGCM" HREF="#PToC_35">Configuring Personal Communications</A></H2>
<P>If you use Transaction Connection to communicate with a remote host, you
must configure Personal Communications for communications with
that host and include the session ID when calling Transaction
Connection. If Transaction Connection
is used only to connect to a database,
Personal Communications is not necessary. You can continue to
the next section.
<P>Because there are several versions of the Personal
Communications program and the PC can be attached to the host
through several different types of connections, all the necessary
steps to configure the communications software to
work with Transaction Connection are not described in this book.
<P>
Transaction Connection requires that a 5250/3270 session be set
up to communicate with the host system. When the session is
created, give it a short session ID that uniquely identifies that
session. This ID is a single character (for example, A, B, or
C). Specify that short session ID as the ID that is to
communicate with Transaction Connection.
<P>Refer to your Personal Communications documentation for
information on how to set up a 5250 or 3270 session to
communicate to the host system through your installed connection
type.
<P><B>Notes: </B><OL>
<P><LI>Transaction Connection does not require any special
configuration.
<P><LI>
All DBITS and AHISS script files that run with DCC/2 or DCConnect
are compatible with the Transaction Connection version that
runs with DCConnect.
</OL>
<HR>
<H2><A NAME="Header_36" HREF="#PToC_36">Starting Transaction Connection Script Files</A></H2>
<P>
Transaction Connection script files can be run either from a window
or full screen. They can also be defined in the Application
Notebook for automatic startup when DCConnect is started. Refer
to the
<CITE>DCConnect User's Guide</CITE> for more information on
configuring Transaction Connection in the DCConnect Application
notebook.
<HR>
<H2><A NAME="HDRSTRTDB" HREF="#PToC_37">Starting Transaction Connection</A></H2>
<P>If your command file (script) is not in the current directory,
you will need to enter the fully qualified path of the file on
the command line when Transaction Connection is started. You can
create a Transaction Connection application in the DCConnect
Application folder to start your command file.
<P>If you are using database connectivity, you must start the
DB2 product and log on before starting Transaction Connection.
On OS/2, you can automatically start DB2/2 each time
you start OS/2 by editing the STARTUP.CMD file.
<P>On Windows NT, you can automatically start DB2 each time the
PC is booted by opening <B>Services</B> in the <B>Control
Panel</B> and setting the <B>Startup</B> option for the
DB2 services to <B>Automatic</B>
<P>You can start Transaction Connection from the command line or
in a command file (.CMD in OS/2 or .BAT in Windows NT) in either
of the following two ways:
<P><B>Example 1</B>
<PRE>
TC2 <command file>
/MAILBOX=[<mailbox>|REMOTE_VALIDATION|DATA_REQUEST|NO_DCCONNECT]
/DB=<database>
/CNTLR=<controller id>
/APPL=<application>
/DBTYPE=[NONE|DB2]
/EMULTYPE=[NONE|CM|PCOMM|ITT]
[/TRACE|NO_DISPLAY]
</PRE>
<P>In this example, several parameters are explicitly stated on
the command line. Some of the parameters are optional. The
angle and square brackets are
<I>not</I> part of the syntax that should be typed on the
command line or in a command file.
Type the parameters continuously; do not break them apart on separate
lines as shown.
<P><B>Example 2</B>
<PRE>
TC2 @ <command file>
</PRE>
<P>In this example, the only parameter is the name of the command
file immediately preceded by the @ character. The
parameters that otherwise would have been defined on the command
line are instead defined in the command file or in a file that is
embedded by it.
The following script commands are used to define the values for
these parameters:
<DL COMPACT>
<DD>mailbox()
<DD>cntlr()
<DD>application()
<DD>database()
<DD>db()
<DD>trace
<DD>no_display_execute
</DL>
<P>In all cases, the <command file> is the name of the command
file for this instance of Transaction Connection. This file is a
script that tells Transaction Connection what you want to do with
each transaction, validation request, or data request.
<TABLE><TR><TD ALIGN=LEFT VALIGN=TOP><B>Note:</B></TD><TD ALIGN=LEFT VALIGN=TOP>
Throughout this documentation, the terms
<I>script file</I> and <I>command file</I> can be
used interchangeably.
</td></tr></table>
<P>If you are specifying the parameters on the command line as
indicated previously, the parameters should be specified as
follows:
<TABLE CELLPADDING=3>
<TR VALIGN=TOP><TD><P><B><mailbox>
</B></TD><TD><P>This is the name of the DCConnect mailbox this instance of
Transaction Connection should use when connecting to DCConnect.
The name must match exactly (including capitalization) the
mailbox name created in ERPBridge.
<P>If Transaction Connection is processing validation requests
instead of transactions, instead of an actual mailbox name, you
should specify the following keyword:
<PRE>
REMOTE_VALIDATION
</PRE>
<P>
In this case, Transaction Connection determines which validation
files should be handled from all of the StartVal commands
encountered in the script. The application name parameter can be
used to override the default application name Transaction
Connection would otherwise use when registering with DCConnect to
receive validation requests. The default application name is
based on the controller ID.
<P>If the Transaction Connection application is processing data
requests instead of transactions or validation requests, instead
of an actual mailbox name, you should specify the following
keyword:
<PRE>
DATA_REQUEST
</PRE>
<P>In this case, you must specify an application name on the
command line or in the script. Transaction Connection uses that
application name when registering itself with DCConnect to handle
data requests.
<P>If you want to run a session of Transaction Connection that
does not handle transactions, validation requests or data
requests, in place of the mailbox name, use the following
keyword:
<PRE>
NO_DCCONNECT
</PRE>
<P>This keyword is useful if Transaction Connection is going to
be performing only a simple operation on a time interval basis,
such as downloading files from an AS/400 twice a day.
</TD></TR><TR VALIGN=TOP><TD><P><B><session>
</B></TD><TD><P>This is the "short name" of the Personal Communications
terminal emulation session to which this instance of Transaction
Connection tries to connect. This is a single character (for
example, A).
<P>This parameter is required for remote host connectivity.
</TD></TR><TR VALIGN=TOP><TD><P><B><controller id>
</B></TD><TD><P>This is a single character to use as an arbitrary controller
identification. This character is used in the name of the error
log file, transaction log file, and trace log file that can be
generated by each instance of Transaction Connection that is
running. If Transaction Connection is processing remote
validation requests, the controller ID is part of the default
application name used when Transaction Connection registers with
DCConnect to receive validation requests. Each Transaction
Connection application should be started with a unique controller
ID.
<P>This parameter is optional, unless multiple Transaction
Connection applications are running at the same time.
<P>The default controller ID is Z.
</TD></TR><TR VALIGN=TOP><TD><P><B><application>
</B></TD><TD><P>This parameter can be specified if Transaction Connection is
processing validation requests or data requests. It is ignored
if transactions are being processed.
<P>If Transaction Connection is processing validation requests,
the application name specified here overrides the default name
that would be based on the controller ID. This name is used by
Transaction Connection when it registers with DCConnect to
receive validation requests.
<P>
If Transaction Connection is processing data requests, the
application name is required. This name is used by Transaction
Connection when it registers with DCConnect to receive data
requests. All terminals or programs acting as the clients that
make the data requests must specify the application name in the
request. DCConnect uses that application name to route the
request to the application that has registered itself using that
name.
<P>The application name can be up to 32 characters long.
</TD></TR><TR VALIGN=TOP><TD><P><B><database>
</B></TD><TD><P>This is the name of the database with which Transaction
Connection is working.
<P>The database name can be up to eight characters and must match
the name of a database that has already been created under DB2.
<P>This parameter is required for database connectivity.
</TD></TR><TR VALIGN=TOP><TD><P><B>TRACE
</B></TD><TD><P>This optional parameter is used to turn on execution or
compile tracing for debug purposes.
<P>If used, this parameter should appear at the end of the
parameter list. TRACE builds a file in the directory where
Transaction Connection is installed. If TRACE is specified, NO_DISPLAY should not be
used.
</TD></TR><TR VALIGN=TOP><TD><P><B>NO_DISPLAY
</B></TD><TD><P>This optional parameter is used to improve processing speed
by turning off the display of each executed step.
<P>If used, this parameter should appear at the end of the
parameter list. If NO_DISPLAY is specified, TRACE should not be
used.
</TD></TR></TABLE>
<HR>
<H2><A NAME="Header_38" HREF="#PToC_38">Multiple Sessions</A></H2>
<P>You can start multiple sessions (instances) of the programs
to do the following:
<UL>
<P><LI>Process transactions against more than one database. Each
instance of a program works with a single database.
<P><LI>Process transactions against more than one host connection
allowing for multiple connections to the same host or connections
to several hosts. Each instance of a program works with a single
host connection.
<P><LI>Provide multiple parallel resources to handle the traffic
of transactions against a single database. The number of program
instances working with a database is limited only by DB2 resources.
You can configure many of these resources in DB2 to allow more
users to connect to a database.
<P><LI>Provide multiple parallel resources to handle the traffic of
transactions to a single remote host. This can provide faster
response times when many transactions need to be sent to the same
host at the same time.
<P><LI>Provide transaction processing and remote validation on the
same computer.
</UL>
<P>
Each instance of the program must be started with a unique
mailbox or data request application. DCConnect allows only one
application to request data from an individual mailbox. Each
instance also has to have a unique <I>controller ID</I>.
This ID is used as the last character of the TC2ERRx.LOG error
log file, and the TC2TRCx.LOG trace file that are opened by each
session.
<HR>
<H1><A NAME="HDRJDE" HREF="#PToC_39">ERPBridge for J.D. Edwards</A></H1>
<P>
The ERPBridge for J.D. Edwards (JDE) product is an interface between J.D. Edwards
Enterprise Resource Planning (ERP) software running on an AS/400 and an IBM Data Collection Connection (DCConnect)
system running on a personal computer (PC). This product enables
the collection of transaction data required for inventory,
distribution, shop floor control, and equipment tracking with the
use of IBM fixed and portable data collection terminals. Data
that normally would be entered by a data entry clerk at a native
5250 terminal now can be entered at the source, on the plant
floor or in the warehouse, as the activity occurs. This system
provides real-time updates to the JDE database, and a method for
storing collected data when the JDE host system is unavailable.
<P>
Fixed and portable data collection terminals provide
more complete and accurate data to users of the shop
floor and inventory data, enabling them to make more informed
decisions, spot production bottlenecks, and improve work flow.
<P>
Use of bar codes for data input speeds transaction data entry, and
improves data accuracy by eliminating keystroke errors. Extensive
use of the PC and the DB2 database maximizes data collection system
availability.
<TABLE BORDER WIDTH=100%><TR><TH ALIGN=LEFT>Installing and Configuring ERPBridge for J.D. Edwards</TH><TR><TD>
Installation and configuration of ERPBridge for J.D. Edwards is an involved process
which is beyond the scope of this installation manual. For more
information about the installation and configuration of ERPBridge for J.D. Edwards,
refer to the online publication <I>ERPBridge for J.D. Edwards</I>.
</TD></TR></TABLE>
<HR>
<H1><A NAME="HDRMAPICS" HREF="#PToC_40">Installing and Configuring ERPBridge for MAPICS</A></H1>
<P>
The ERPBridge for MAPICS product provides a total solution for customers of
MAPICS XA who have Production Monitoring and Control (PM&C)
installed. ERPBridge for MAPICS is a set of DCConnect transaction programs
for the IBM 7524, 7526, and 7527 data collection terminals, along
with
Transaction Connection
scripts that collect PM&C transactions and forward them to the
MAPICS XA system running on an AS/400. The prerequisite TC is
included with ERPBridge for MAPICS .
<TABLE><TR><TD ALIGN=LEFT VALIGN=TOP><B>Note:</B></TD><TD ALIGN=LEFT VALIGN=TOP>
ERPBridge for MAPICS was formerly known as HostConnect for MAPICS.
</td></tr></table>
<HR>
<H2><A NAME="Header_41" HREF="#PToC_41">Prerequisite Hardware and Software</A></H2>
<P>The Development Toolkit or Server product is a prerequisite for ERPBridge for MAPICS .
(See<A HREF="#HDRHSRQ">Hardware and Software Requirements</A>) .
<P><B>Hardware</B>
<UL COMPACT>
<LI>AS/400 computer
<P>3270 or 5250 Emulation adapter or token-ring adapter that is
supported by IBM eNetwork Personal Communications Version 4.2 for OS/2,
Windows NT, Windows 95
</UL>
<P><B>Software</B>
<UL COMPACT>
<LI>On the AS/400, MAPICS/XA PM&C release 2.2 and 2.3 are supported
<LI>IBM eNetwork Personal Communications Version 4.2 for OS/2, Windows NT,
Windows 95 (P/N: 4074548).
</UL>
<HR>
<H2><A NAME="Header_42" HREF="#PToC_42">Installing ERPBridge for MAPICS</A></H2>
<P>To install ERPBridge for MAPICS , do the following:
<OL COMPACT>
<LI>Insert the product CD into the CD-ROM drive on your
personal computer.
<LI><B>(On OS/2)</B> Bring up the <B>Drives</B> icon.
<P><B>(On Windows NT)</B> Start the <B>Windows/NT Explorer</B>
<LI>Select the CD drive
<LI><B>(On OS/2)</B> Click on <B>setupos2</B>
<P><B>(On Windows NT)</B> Click on <B>setup</B>
<LI>Follow the screen instructions as the installation program
steps you through the rest of the process.
</OL>
<P>The ERPBridge for MAPICS product is installed on your system.
<HR>
<H2><A NAME="Header_43" HREF="#PToC_43">MAPICS XA Release 2.2 and Release 2.3</A></H2>
<P>
ERPBridge for MAPICS provides transaction programs and
TC
scripts for both Release 2.2 and 2.3 of MAPICS XA PM&C. The
primary difference between the two releases is the length of the
<B>Goods Received Note (GRN)</B>
field and the addition of a <B>Goods Received Note Invoice
(GRNI)</B> field in certain transactions that collect data on
materials receipt and return. The transaction formats for both
releases are described in detail in the HostConnect for MAPICS
online documentation. Based on the Release of the MAPICS XA
system being used, select the release (R22 or R23) to match your
particular environment. If you are not using either of these two
releases, select the environment that more closely matches the
release being used. Transaction formats can be modified using
the information provided in the ERPBridge for MAPICS online documentation.
<HR>
<H2><A NAME="Header_44" HREF="#PToC_44">Configuring ERPBridge for MAPICS</A></H2>
<P>
After installation of the ERPBridge for MAPICS product, you need to
perform some basic configuration.
The product
requires a User ID and password to access the MAPICS XA PM&C
application. Refer to PM&C documentation for information on
setting up the data collection controller User ID and password on
the AS/400.
<P>
Go to the DCConnect Application Settings notebook. Several pages of
the application settings notebook must be configured as follows.
<OL>
<P><LI>
Select the <B>GENERAL</B> tab. In the <B>Type</B>
field, scroll through the selections until MAPICS is displayed.
This enables the MAPICS notebook configuration page.
<P><LI>
Select the <B>TC Series</B> notebook page on
TC
Parameters. Change the default settings as required, ensuring
the Session matches the Personal Communications short session ID
for the 5250 emulated session that will be assigned to ERPBridge for MAPICS .
Ensure that the Script File name matches the version of MAPICS
that you have installed. For Release 2.2, the file name is
STARTR22; for Release 2.3, the file name is STARTR23.
<P><LI>Select <B>Transaction</B> as the Mode.
<P><LI>Deselect <B>Trace</B> and <B>Display</B>
for maximum performance.
<P><LI>Leave Mailbox at the default of "mapics_xa" for a single
session. If multiple sessions are used for maximum transaction
throughput, change the mailbox name to match the mailbox name as
assigned in DCConnect.
<P><LI>
Select the <B>Mapics</B> tab on the Settings notebook.
Enter the User ID and password that matches those configured in
MAPICS PM&C for this data collection controller. If the host
User ID and password were manually created on the AS/400 system
without an initial program to call, the procedure and library may
be entered here.
<P><LI>
Set the Sign On Rate as desired. This is the time period (in
minutes) that ERPBridge for MAPICS waits after a system failure (or Dedicated
Application Mode) before attempting to sign back on to the AS/400.
See the ERPBridge for MAPICS documentation for additional information
on configuration parameters and handling of host system outages.
<P><LI>Save the file when you have finished.
</OL>
<HR>
<H2><A NAME="Header_45" HREF="#PToC_45">Configuring Personal Communications</A></H2>
<P>
Personal Communications provides 5250 emulation through a
variety of hardware and software protocols. It is beyond the
scope of this document to provide configuration information on
all the methods that can be used. Refer to the documentation
provided with your hardware and Personal Communications to
correctly configure a 5250 emulation session. Note that the
connection methodology must support the EHLLAPI interface.
<P>
During configuration, note the Short Session ID. This value must
be placed in the TC setup notebook. If this session is used
for any other purpose other than
ERPBridge for MAPICS ,
improper operation of the system, including data loss, can result.
<HR>
<H1><A NAME="Header_46" HREF="#PToC_46">Installing Terminal Services for DOS/Windows</A></H1>
<P>The Terminal Services for DOS and for Windows product enables a PC running DOS or Windows to
generate transactions for, and make requests to the Server
as does a data collection terminal (DCT). This product comes
with its own set of APIs that can be called from a Visual Basic
or C language program to interact with the
Server. Using the API set, a program can send transactions,
request validation of data, get the Server's current time of
day, request data from an application registered with the
DCConnect Server, and set terminal user variables.
<P>The Terminal Services for DOS and for Windows product maintains full data integrity.
Transactions received from your DOS and Windows programs are
safely stored on the hard disk before your programs receive a
successful return code.
<HR>
<H2><A NAME="HDRPREQHWS" HREF="#PToC_47">Prerequisite Hardware and Software</A></H2>
<P>Before creating the Terminal Services for DOS and for Windows installation diskette, the following
must be installed and available:
<UL>
<P><LI>The Development Toolkit or Server product
<P>For hardware and software requirements of these products,
(See<A HREF="#HDRHSRQ">Hardware and Software Requirements</A>) .
</UL>
<P><B>Hardware</B>
<UL COMPACT>
<LI>IBM-compatible 386DX processor
<LI>8MB RAM
<LI>10MB disk space in addition to operating system requirements
<LI>VGA display (Windows only)
<LI>Diskette drive
</UL>
<P><B>Software</B>
<UL>
<P><LI>One of the following compilers
<P>For DOS
<UL COMPACT>
<LI>Microsoft C 7.0
<LI>Microsoft Visual C++ 1.5
</UL>
<P>For Windows
<UL COMPACT>
<LI>Microsoft C 7.0
<LI>Microsoft Visual C++ 1.5
<LI>Microsoft Visual Basic 4.0
</UL>
<P>For Windows 95/NT
<UL COMPACT>
<LI>Microsoft Visual C++ 6.0
<LI>Microsoft Visual Basic 4.0 or greater
</UL>
<P><LI>IBM PC DOS or MS DOS 6.0 or later versions
or
Microsoft Windows 3.1, Windows 95, or Windows NT
<P><LI>One of the following TCP/IP products
<P>For DOS
<UL COMPACT>
<LI>IBM TCP/IP for DOS 2.1.1.4 (UB10767) or later versions
<LI>FTP Software PC/TCPIP 3.2 for DOS
</UL>
<P>For Windows 3.1
<UL COMPACT>
<LI>IBM TCP/IP for DOS 2.1.1.4 (UB10767) or later versions
<LI>FTP Software OnNet for Windows version 2.1
<LI>Trumpet Winsock
</UL>
<P>For Windows 95/NT
<UL COMPACT>
<LI>Microsoft TCP/IP protocol
</UL>
<TABLE><TR><TD ALIGN=LEFT VALIGN=TOP><B>Note:</B></TD><TD ALIGN=LEFT VALIGN=TOP>
Support for Novell networks is available by configuring Trumpet
Winsock to run over your existing Novell network.
</td></tr></table>
</UL>
<HR>
<H2><A NAME="HDRCRCON" HREF="#PToC_48">Creating the Terminal Services for DOS and for Windows Configuration Diskette</A></H2>
<P>In addition to the diskettes provided with the product, you
must create a configuration diskette.
<P>During the install process, you are asked to insert the
Terminal Services for DOS and for Windows configuration diskette. Before the configuration
diskette can be created, one or more Terminal Services for DOS and for Windows PC terminals must be
configured under the DCConnect Server. Also, the DCConnect
Configuration utility must be run to configure DCConnect for TCP/IP
communication.
(See<A HREF="#HDRDCCONFG">DCConnect Configuration</A>) See the Tutorial or
online user's guide for information on how to configure a
DCConnect terminal.
<P>
To create the configuration diskette, do the following:
<OL COMPACT>
<LI>Open the <B>DCConnect</B> folder located on the Desktop.
On Windows/NT you can also use the Start button:
<PRE>
Start -> Programs -> DC Connect
</PRE>
<LI>Select the Terminal Services for DOS and for Windows Configuration Diskette icon.
<P>A dialog box appears asking for a blank formatted
diskette to be inserted in drive A.
<LI>Insert the diskette and click on the <B>Enter</B> button.
<P>A completion message displays when the diskette is
successfully created.
</OL>
<HR>
<H2><A NAME="HDRINSDOSW" HREF="#PToC_49">Installing Terminal Services for DOS and for Windows on the DOS or Windows PC</A></H2>
<P>The following explains how to install the Terminal Services for DOS and for Windows product on the
DOS or Windows PC.
<TABLE><TR><TD ALIGN=LEFT VALIGN=TOP><B>Note:</B></TD><TD ALIGN=LEFT VALIGN=TOP>
A supported TCP/IP product must be installed and configured
before you install Terminal Services for DOS and for Windows on the DOS or Windows PC. On Windows 95/NT,
TCP/IP is part of the operation system, but you must install it
See the TCP/IP product information for more information on installing the
TCP/IP stack.
</td></tr></table>
<P><B>If you have a DOS-only system,</B> do the following:
<OL COMPACT>
<LI>Insert into diskette drive A, the Terminal Services for DOS and for Windows installation diskette you created
following the instructions in the previous section,
(See<A HREF="#HDRCRCON">Creating the Terminal Services for DOS and for Windows Configuration Diskette</A>) .
<LI>On the command line, type <B>a:install</B>.
<LI>Press <B>Enter</B>.
</OL>
<P><B>If you have a Windows system (any kind),</B> do the following:
<OL COMPACT>
<LI>Insert into diskette drive A, the Terminal Services for DOS and for Windows installation diskette
you created following the instructions in the previous section,
(See<A HREF="#HDRCRCON">Creating the Terminal Services for DOS and for Windows Configuration Diskette</A>) .
<LI>Start a DOS session.
<LI>On the command line, type <B>a:install</B>.
<LI>Press <B>Enter</B>.
</OL>
<P>Other methods can be used on Windows systems as well, including:
<UL>
<P><LI>Start the File Manager, select drive A, and double-click
on the <B>Install</B> program.
<P><LI>Select the file pull-down on the Program Manager window
and click on the <B>Run</B> option. A run dialog box with a
command line entry field is displayed. In that box, enter
<PRE>
a:\install
</PRE>
<P><LI>Start the Windows (NT) Explorer, select the floppy drive (A:) and
then double-click on the Install selection in the rightmost list.
</UL>
<P>
The Terminal Services for DOS and for Windows installation program first displays a dialog box asking
for the drive where you would like the support installed:
<PRE>
<B>Please enter the drive letter of the drive where you wish to
install the Terminal Services for DOS and for Windows product.</B>
</PRE>
<P>
The Installation program displays a status window on the screen
to show the status of each step of the installation as it
progresses. During the installation process the Terminal Services for DOS and for Windows
Configuration program is started. See the next section
Configuring Terminal Services for DOS and for Windows.
<P>
For DOS, Windows 3.1 and Windows 95 systems, the
last step of installation is to update the AUTOEXEC.BAT
file. (On Windows NT the registry is updated instead).
You can update the file by doing one of the following:
<UL>
<P><LI>Press the <B>Y</B> key if you want Terminal Services for DOS and for Windows
Installation to back up the current AUTOEXEC.BAT file and add the
new changes.
<P><LI>Press the <B>N</B> key if you prefer the changes that
need to be added to the AUTOEXEC.BAT file be written to
an AUTOEXEC.TXT file in the \DWTS directory.
</UL>
<P>After the install program has ended, you must re-start
your system to have the AUTOEXEC.BAT changes take effect.
<P>
A reboot is not necessary for Windows NT systems.
<HR>
<H2><A NAME="HDRCONTDW" HREF="#PToC_50">Configuring Terminal Services for DOS and for Windows</A></H2>
<TABLE BORDER WIDTH=100%><TR><TH ALIGN=LEFT>Note</TH><TR><TD>
<B>Terminal Services for DOS and for Windows is not operational until the configuration step
is performed.</B>
</TD></TR></TABLE>
<P>This configuration step is performed as part of the
installation. The configuration program can be used at a later
time to change a Terminal Services for DOS and for Windows PC terminal configuration.
<P>To start the configuration program, do the following:
<OL>
<P><LI>At the command line, change to the drive where the product is
installed, for example: <B>C:</B>
<P><LI>Change to the DWTS directory.
<PRE>
<B>cd \dwts</B>
</PRE>
<P><LI>Start the configuration.
<PRE>
<B>config</B>
</PRE>
<P>The configuration program checks to see if the TCP/IP product
has been installed. TCP/IP must be installed for the
configuration program to continue.
<P>
If TCP/IP is installed, the configuration program displays a
message asking you to insert the Terminal Services for DOS and for Windows configuration diskette
in drive A.
<P><LI>Insert this diskette in drive A.
<P>
The configuration diskette contains the configuration information
for all the DCConnect DOS and Windows PCs.
For information on how to create the diskette,
(See<A HREF="#HDRCRCON">Creating the Terminal Services for DOS and for Windows Configuration Diskette</A>) .
<P>
The file contains the host TCP/IP name of each of the DCConnect
DOS and Windows PCs, its TCP/IP address, and the terminal name
that is to be associated with this DOS and Windows PC.
<BR>
<P><B><A NAME="Table_1">Table 1. Terminal Services for DOS and for Windows Configuration</A></B><BR>
<TABLE BORDER>
<TR>
<TH ALIGN=LEFT VALIGN=TOP WIDTH=1%>PC Name
</TH><TH ALIGN=LEFT VALIGN=TOP WIDTH=50%>TCP/IP Address
</TH><TH ALIGN=LEFT VALIGN=TOP WIDTH=50%>Terminal Name
</TH></TR><TR>
<TD ALIGN=LEFT VALIGN=TOP WIDTH=1%>DWTSPC1
</TD><TD ALIGN=LEFT VALIGN=TOP WIDTH=50%>9.3.99.108
</TD><TD ALIGN=LEFT VALIGN=TOP WIDTH=50%>DWTermNumber1
</TD></TR><TR>
<TD ALIGN=LEFT VALIGN=TOP WIDTH=1%>DWTSPC2
</TD><TD ALIGN=LEFT VALIGN=TOP WIDTH=50%>8.63.7.18
</TD><TD ALIGN=LEFT VALIGN=TOP WIDTH=50%>Terminal15
</TD></TR><TR>
<TD ALIGN=LEFT VALIGN=TOP WIDTH=1%>DWTSPC3
</TD><TD ALIGN=LEFT VALIGN=TOP WIDTH=50%>9.52.97.138
</TD><TD ALIGN=LEFT VALIGN=TOP WIDTH=50%>TermNumber12
</TD></TR><TR>
<TD ALIGN=LEFT VALIGN=TOP WIDTH=1%>DWTSPC4
</TD><TD ALIGN=LEFT VALIGN=TOP WIDTH=50%>5.83.22.48
</TD><TD ALIGN=LEFT VALIGN=TOP WIDTH=50%>Shipping1
</TD></TR><TR>
<TD ALIGN=LEFT VALIGN=TOP WIDTH=1%>DWTSPC5
</TD><TD ALIGN=LEFT VALIGN=TOP WIDTH=50%>22.56.33.9
</TD><TD ALIGN=LEFT VALIGN=TOP WIDTH=50%>PartDept2
</TD></TR><TR>
<TD ALIGN=LEFT VALIGN=TOP WIDTH=1%>DWTSP6
</TD><TD ALIGN=LEFT VALIGN=TOP WIDTH=50%>89.78.107.108
</TD><TD ALIGN=LEFT VALIGN=TOP WIDTH=50%>Shipping5
</TD></TR><TR>
<TD ALIGN=LEFT VALIGN=TOP WIDTH=1%>DWTSPC7
</TD><TD ALIGN=LEFT VALIGN=TOP WIDTH=50%>3.83.2.56
</TD><TD ALIGN=LEFT VALIGN=TOP WIDTH=50%>PartDept1
</TD></TR><TR>
<TD ALIGN=LEFT VALIGN=TOP WIDTH=1%>DWTSPC8
</TD><TD ALIGN=LEFT VALIGN=TOP WIDTH=50%>99.83.32.132
</TD><TD ALIGN=LEFT VALIGN=TOP WIDTH=50%>Shipping3
</TD></TR><TR>
<TD ALIGN=LEFT VALIGN=TOP WIDTH=1%>DWTSPC9
</TD><TD ALIGN=LEFT VALIGN=TOP WIDTH=50%>129.83.44.11
</TD><TD ALIGN=LEFT VALIGN=TOP WIDTH=50%>DWTerminal1
</TD></TR><TR>
<TD ALIGN=LEFT VALIGN=TOP WIDTH=1%>DWTSPC10
</TD><TD ALIGN=LEFT VALIGN=TOP WIDTH=50%>49.83.96.38
</TD><TD ALIGN=LEFT VALIGN=TOP WIDTH=50%>Terminal12
</TD></TR><TR>
<TD ALIGN=LEFT VALIGN=TOP WIDTH=1%>DWTSPC11
</TD><TD ALIGN=LEFT VALIGN=TOP WIDTH=50%>89.83.2.183
</TD><TD ALIGN=LEFT VALIGN=TOP WIDTH=50%>Terminal5
</TD></TR><TR>
<TD ALIGN=LEFT VALIGN=TOP WIDTH=1%>DWTSPC12
</TD><TD ALIGN=LEFT VALIGN=TOP WIDTH=50%>79.83.27.56
</TD><TD ALIGN=LEFT VALIGN=TOP WIDTH=50%>PartDept3
</TD></TR><TR>
<TD ALIGN=LEFT VALIGN=TOP WIDTH=1%>DWTSPC14
</TD><TD ALIGN=LEFT VALIGN=TOP WIDTH=50%>5.83.97.1
</TD><TD ALIGN=LEFT VALIGN=TOP WIDTH=50%>ThisTerminalHasALongName
</TD></TR><TR>
<TD ALIGN=LEFT VALIGN=TOP WIDTH=1%>DWTSPC15
</TD><TD ALIGN=LEFT VALIGN=TOP WIDTH=50%>66.383.97.8
</TD><TD ALIGN=LEFT VALIGN=TOP WIDTH=50%>SalesDept1
</TD></TR><TR>
<TD ALIGN=LEFT VALIGN=TOP WIDTH=1%>
</TD><TD ALIGN=LEFT VALIGN=TOP WIDTH=50%>
</TD><TD ALIGN=LEFT VALIGN=TOP WIDTH=50%>
</TD></TR></TABLE>
<P>The Terminal Services for DOS and for Windows configuration program displays the above
information in a list box.
<P><LI>
Select the terminal associated with this DOS or Windows PC by
pressing the <B>Up Arrow</B> or <B>Down Arrow</B> key.
<P><LI>
Press <B>Enter</B> to start the configuration.
<P>The configuration program copies this terminal's
information from the configuration diskette to your DOS or
Windows PC.
</OL>
<HR>
<H2><A NAME="Header_51" HREF="#PToC_51">Directory Structure and Environment Variables Used by Terminal Services for DOS and for Windows</A></H2>
<P>
When Terminal Services for DOS and for Windows is installed, it creates the following subdirectories
relative to the target drive specified during
the installation:
<BLOCKQUOTE>
<PRE>
c:\dwts\dll\win31 - Dynamic link libraries for Windows 3.1
\dll\win95 - Dynamic link libraries for Windows 95/NT
\include - API header file
\lib\win31 - API library for Windows 3.1
\lib\win95 - API library for Windows 95/NT
\lib\ibm - API library for use with IBM DOS TCP/IP
\lib\ftp - API library for use with FTP Software DOS PC/TCP
\samples - Sample API code and executables
\Windows\win31 - Sample API code, executable (Windows 3.1)
\Windows\win95 - Sample API code, executable (Windows 95/NT)
\BASIC\win31 - Sample API code, executable (Windows 3.1)
\BASIC\win95 - Sample API code, executable (Windows 95/NT)
\DOS - Sample API code
\IBM - Sample executable for IBM TCP/IP
\FTP - Sample executable for FTP PC/TCP
</PRE>
</BLOCKQUOTE>
<P>At the completion of the installation and configuration, the
directories contain the following:
<UL COMPACT>
<LI>The INCLUDE directory contains the single combined DWTS
DOS/Windows include file and the DWTS Visual Basic include text
file.
<LI>The SAMPLES directory contains several subdirectories based on the
operating system and TCP/IP stack in use. Each subdirectory contains the
sample executable file, the source code, and the make file for
its appropriate compiler language and run environment.
</UL>
<HR>
<H1><A NAME="Header_52" HREF="#PToC_52">Installing the DCConnect Transaction Building Tool</A></H1>
<P>The Transaction Building Tool is an alternative to the DCConnect
Development for creating Transaction Program files. For complete
information about the use of this product, refer to the Data Collection
Transaction Building Tool documentation which can be found on the product
CD by entering the following URL in your browser:
<PRE>
file:///d:\manuals\index.htm
</PRE>
where d: is the drive letter for your CD-ROM drive.
<HR>
<H2><A NAME="Header_53" HREF="#PToC_53">Installing the Transaction Building Tool</A></H2>
<P>To install the Transaction Building Tool, do the following:
<OL COMPACT>
<LI>Insert the product CD into the CD-ROM drive on your
personal computer.
<LI><B>(On OS/2)</B> Bring up the <B>Drives</B> icon.
<P><B>(On Windows NT)</B> Start the <B>Windows/NT Explorer</B>
<LI>Select the CD drive
<LI><B>(On OS/2)</B> Click on <B>setupos2</B>
<P><B>(On Windows NT)</B> Click on <B>setup</B>
<LI>Follow the screen instructions as the installation program
steps you through the rest of the process.
</OL>
<P>The Transaction Building Tool is installed on your system.
<P><A NAME="PToC3" HREF="#ToC">Partial Table-of-Contents</A>
<HR><P>
<HR>
<H1><A NAME="HDRNOTICES" HREF="#ToC_54">Notices</A></H1>
<P>References in this publication to IBM products, programs, or
services do not imply that IBM intends to make these available in
all countries in which IBM operates.
Any reference to an IBM product, program, or service is not
intended to state or imply that only IBM's product, program, or
service may be used. Any functionally equivalent product,
program, or service that does not infringe any of IBM's
intellectual property rights may be used instead of the IBM
product, program, or service. Evaluation and verification of
operation in conjunction with other products, except those
expressly designated by IBM, is the user's responsibility.
<P>
IBM may have patents or pending patent applications covering
subject matter in this document. The furnishing of this document
does not give you any license to these patents. You can send
license inquiries, in writing, to the IBM Director of Commercial
Relations, IBM Corporation, Purchase, NY 10577.
<HR>
<H2><A NAME="Header_55" HREF="#PToC_55">Trademarks</A></H2>
<P>The following terms are trademarks of the IBM Corporation
in the United States or other countries or both:
<TABLE CELLPADDING=3>
<TR VALIGN=TOP><TD>AIX windows
</TD><TD>MAPICS
</TD></TR><TR VALIGN=TOP><TD>AS/400
</TD><TD>Micro Channel
</TD></TR><TR VALIGN=TOP><TD>C/2
</TD><TD>OS/2
</TD></TR><TR VALIGN=TOP><TD>Database 2
</TD><TD>Portmaster
</TD></TR><TR VALIGN=TOP><TD>DB2
</TD><TD>RISC System/6000
</TD></TR><TR VALIGN=TOP><TD>ERPBridge
</TD><TD>VisualAge
</TD></TR><TR VALIGN=TOP><TD>ERPconnect
</TD><TD>WIN-OS/2
</TD></TR><TR VALIGN=TOP><TD>IBM
</TD><TD>
</TD></TR></TABLE>
<P>Other company, product, and service names may be trademarks
or service marks of others.
<P>Microsoft, Windows, Windows NT, and the Windows logo are
registered trademarks of Microsoft Corporation.
<HR>
<H1><A NAME="HDRHARDINS" HREF="#ToC_56">Installing Native Serial Ports and Data Collection Terminals</A></H1>
<P>This section explains the preparation and installation of
the following hardware for the data collection system:
<UL>
<P><LI>Native Serial Ports - COMx support
<P><LI>One or more IBM 7524, 7525, 7526, or 7527 Data Collection
Terminals.
</UL>
<P>The system unit can be connected to multiple Data Collection
Terminals (DCTs) using RS-422 communication lines connected
to the RS-422/485 adapters installed in the system unit.
This can be done instead of, or in conjunction with, the use of
ARTIC cards. Each communications line consists of transmit and
receive pairs of twisted-pair cable. The DCTs are
connected to this communications line in a <I>multidrop</I>
configuration.
<TABLE><TR><TD ALIGN=LEFT VALIGN=TOP><B>Note:</B></TD><TD ALIGN=LEFT VALIGN=TOP>
The IBM system unit model and the capacity of the hard disk drive
should be selected according to the processing and storage demand
requirements which are expected for the particular data
collection system installation.
</td></tr></table>
<HR>
<H2><A NAME="HDRHSTEP2" HREF="#PToC_57">Plant Wiring Installation</A></H2>
<P>This section gives guidelines for installing RS-422
communications lines between the system unit and the DCTs. The
number of communications lines and number of Data Collection
Terminals supported depend on the type of system unit.
<P>The IBM 7524-Batch, 7525, 7526, and 7527 can be connected to,
and intermixed on, any common communications line. This line
consists of receive and transmit pairs of cable connected to the
RS-422/485 communications adapter installed in the system
unit. Each DCT has an address selected on the terminal display
when installed, allowing the system unit software to recognize
each DCT on the common communications line.
<TABLE><TR><TD ALIGN=LEFT VALIGN=TOP><B>Note:</B></TD><TD ALIGN=LEFT VALIGN=TOP>
If the 7526 and 7527 DCTs are on dedicated communications lines
(no 7525 DCTs), they can operate at the 19200 baud rate. 7525
terminals cannot be intermixed on such a communications line.
Likewise, if 7526 terminals are to run at the 38400 baud rate on
a particular communications line, that line cannot have any 7525
or 7527 terminals attached to it.
</td></tr></table>
<P>It is important to plan the locations of the Data Collection
Terminals and review the RS-422 cable specifications prior to the
actual installation. To facilitate line testing and adjustments,
the cable for the RS-422 communications lines should be run
prior to making connections to the system unit. At least one DCT
must be connected to the system unit with an RS-422
communications cable, to complete the initial installation and
test of the data collection system. Additional DCTs can be added
to the data collection system at any time.
<HR>
<H2><A NAME="Header_58" HREF="#PToC_58">Installing RS-422 Cable</A></H2>
<P>Up to 4,000 feet of communications cable can be run
for each RS-422 communications line supported by the system unit.
Each communications line corresponds to a COM port on the system
unit.
<P>For maximum distance capability, the use of AWG 22
(recommended) or AWG 24 two-twisted-pair cable with
an over-all shield should be used for RS-422 communications
lines; the DCTs should be connected, in multidrop fashion, to the
communications line. Optional accessories are available to
facilitate network connections. The connections to the
communications line can also be made using standard multidrop
(parallel) wiring techniques.
<P>
Refer to the <CITE>IBM 7525 Data Collection Terminal Physical
Planning and Operation Guide</CITE>, <CITE>IBM 7526 Data Collection
Terminal Hardware Information and Site Preparation</CITE> and the
<CITE>IBM 7527 Data Collection Terminal (Models 001 and 002)
General Information</CITE> for additional planning information
and for optional accessories available for making network
connections.
<HR>
<H2><A NAME="HDRDCTHSU" HREF="#PToC_59">Data Collection Terminal Hardware Setup</A></H2>
<P>Before installing DCTs, refer to the publications listed below
to familiarize yourself with the procedures for selecting the
terminal addresses and communications line parameters on each
terminal used in installation:
<UL COMPACT>
<LI><CITE>IBM 7525 Data Collection Terminal Installation, Setup, and
Problem Determination Guide</CITE>; supplied with each order of an
IBM 7525 Terminal
<LI><CITE>IBM 7526 Data Collection Terminal Hardware Information
and Site Preparation</CITE>
<LI><CITE>IBM 7527 Terminal Installation,
Operation and Problem Determination</CITE>;
supplied with each order of an IBM 7527 Terminal
<LI><CITE>IBM 7524 Interface Support Online Manual</CITE>.
</UL>
<HR>
<H2><A NAME="HDROPS" HREF="#PToC_60">DCT Operating Parameter Setup</A></H2>
<P>To set up the DCTs, the terminal operator enters operational
parameters using each DCT's keyboard as prompts appear on the
terminal LCD display. The parameters, once selected, are stored
in memory on the DCT. Select the same communications line
parameters for all terminals associated with a common
RS-422 communications line. The procedure for entering
these parameters differs for 7525, 7526, and 7527 terminals.
<P>
<H3><A NAME="HDR25SETUP" HREF="#PToC_61">7525 Terminal Setup</A></H3>
After powering on the 7525 terminal, the following line is
displayed:
<P>
<B>7525 V1.0 COPYRIGHT IBM CORP. 1987, 1988</B>
<P>The terminal address, baud rate, data character length and
parity (if 7-character lengths are chosen) must be selected. A
unique address must be chosen for each terminal. The default
settings for the baud rate and data character length should be
used. Pressing the <B>Enter</B> key brings up the default
setting for each parameter. To change a parameter, press any
numeric key. When the desired option is displayed, the possible
settings for that parameter are displayed each time a numeric key
is pressed. Pressing <B>Enter</B> automatically saves the
desired option and brings up the next parameter.
<A HREF="#TBLSUPARMS">Table 2</A>
provides the terminal parameters, default and optional settings.
For further information, refer to the <CITE>IBM 7525 Data Collection
Terminal Installation, Setup, and Problem Determination
Guide</CITE>.
<BR>
<P><B><A NAME="TBLSUPARMS">Table 2. 7525 terminal setup parameters, defaults, and optional settings</A></B><BR>
<TABLE BORDER>
<TR>
<TH ALIGN=LEFT VALIGN=TOP WIDTH=33%>Parameter
</TH><TH ALIGN=LEFT VALIGN=TOP WIDTH=33%>Default
</TH><TH ALIGN=LEFT VALIGN=TOP WIDTH=33%>Options
</TH></TR><TR>
<TD ALIGN=LEFT VALIGN=TOP WIDTH=33%>Addr
</TD><TD ALIGN=LEFT VALIGN=TOP WIDTH=33%>A
</TD><TD ALIGN=LEFT VALIGN=TOP WIDTH=33%>B - P
</TD></TR><TR>
<TD ALIGN=LEFT VALIGN=TOP WIDTH=33%>Baud rate
(Network speed)
</TD><TD ALIGN=LEFT VALIGN=TOP WIDTH=33%>9600
</TD><TD ALIGN=LEFT VALIGN=TOP WIDTH=33%>1200, 2400, 4800
</TD></TR><TR>
<TD ALIGN=LEFT VALIGN=TOP WIDTH=33%>Data char length
(Network data bits)
</TD><TD ALIGN=LEFT VALIGN=TOP WIDTH=33%>8
</TD><TD ALIGN=LEFT VALIGN=TOP WIDTH=33%>7
<TABLE><TR><TD ALIGN=LEFT VALIGN=TOP><B>Note:</B></TD><TD ALIGN=LEFT VALIGN=TOP>If 7527 DCTs are used on the same COM line, use 8 data bits
and no parity.</td></tr></table>
</TD></TR><TR>
<TD ALIGN=LEFT VALIGN=TOP WIDTH=33%>Parity
</TD><TD ALIGN=LEFT VALIGN=TOP WIDTH=33%>
<BR></TD><TD ALIGN=LEFT VALIGN=TOP WIDTH=33%>Odd, even
</TD></TR></TABLE>
<TABLE><TR><TD ALIGN=LEFT VALIGN=TOP><B>Note:</B></TD><TD ALIGN=LEFT VALIGN=TOP>If the <B>Data char length</B> is set to 8, the parity
parameter is automatically set to "none" and is not
displayed. If the <B>data char length</B> is set to 7, the
parity parameter may be set to "odd" or "even".
</td></tr></table>
<P>After all parameters are selected, the following line is
displayed:
<P>
OUT OF SERVICE DOWNLOAD NEEDED
<P>
This message indicates that the system is ready to have terminal
file information downloaded. After the information is
downloaded, a prompt is displayed, indicating that the system is
ready for input.
<TABLE><TR><TD ALIGN=LEFT VALIGN=TOP><B>Note:</B></TD><TD ALIGN=LEFT VALIGN=TOP>To reset the communications parameters at the terminal, the
cable which connects the terminal to the base must be
disconnected for a few seconds and then reconnected. When the
cable is reconnected, the copyright message is displayed again
and the parameters can be reset.
</td></tr></table>
<P>
<H3><A NAME="HDR26SETUP" HREF="#PToC_62">7526 Terminal Setup</A></H3>
Setup mode is used to configure various operating parameters on
the 7526, such as terminal address, communications speed, and
national language support.
Whenever a terminal is first installed or has been cold-reset,
use the setup mode to re-establish all desired configuration
items.
<P>
The 7526's built-in diagnostics are also accessed from the
setup mode. These diagnostics:
<UL>
<P><LI>
Allow auditing of the terminal's performance and usage
<P><LI>
Verify the function of various subsystems on the terminal
<P><LI>
Offer support for testing the function of bar code/magnetic
readers and their respective media
</UL>
<P>
<H4><A NAME="Header_63" HREF="#PToC_63">Starting Setup Mode</A></H4>
<P>
If the 7526 comes up with the IBM copyright screen constantly
displayed, this indicates one of the following:
<UL COMPACT>
<LI>
The terminal is being installed for the first time.
<LI>
The terminal has lost its memory retention battery backup.
<LI>
The terminal has been cold-reset.
</UL>
In any of these cases, press the <B>Enter</B> key to
start the setup mode.
<P>
If the terminal has already been configured using setup
(and the setup parameters are still retained),
use the Keylock key sequence to restart the setup mode. To do
the Keylock key sequence, press the <B>Shift</B> key to
select one of the blue-highlighted functions, and then
press the <B>Keylock</B> key, which is marked with a key
symbol on the blue highlight background.
<P>
If a password has been set to protect access to the keylock mode,
enter the correct key sequence at the password prompt.
<P>
Successful entry to setup mode is indicated
when the 7526 display presents one of the following:
<UL>
<P><LI>"ADDR:a"
<P><LI>"SERVER:RS-485"
</UL>
The second one is presented only if the terminal has the Ethernet
port installed. The first one is presented in all other cases.
The one that is shown is the first setup menu item.
<P>
The various configuration items available are listed below.
(See<A HREF="#HDRSETTAB">Setup Configuration Items</A>)
<P>
<H4><A NAME="Header_64" HREF="#PToC_64">Setup Mode Key Usage</A></H4>
<P>
When the terminal is in the setup mode, use the following keys to
proceed through the menus and make selections:
<TABLE CELLPADDING=3>
<TR VALIGN=TOP><TD><P><B>Next selection keys
</B></TD><TD><P>
Press any numeric key, any <B>F</B> key, or the
<B>Alt</B> key to change a parameter to the next possible
value. After the last value is shown, the display wraps around
to the first option on the list.
</TD></TR><TR VALIGN=TOP><TD><P><B>
Accept selection key
</B></TD><TD><P>
Press <B>Enter</B> when the parameter has the desired value
or to accept the current or default value.
</TD></TR><TR VALIGN=TOP><TD><P><B>
Quick-configure key
</B></TD><TD><P>
After the address is set, you may quickly accept the default values
for all other parameters by pressing the <B>Clear</B> key.
(For Model 200, <B>Clear</B> is <B>Shift</B> and
<B>0</B>; for Model 100, press <B>Clear</B>.)
</TD></TR></TABLE>
<P>
<H4><A NAME="HDRSETTAB" HREF="#PToC_65">Setup Configuration Items</A></H4>
<P>
The following table lists all the setup mode
configuration items available.
For each item, it shows the display prompt,
the default value, and the values possible.
<BR>
<TABLE BORDER>
<TR>
<TH ALIGN=LEFT VALIGN=TOP WIDTH=20%>Configuration Item
</TH><TH ALIGN=LEFT VALIGN=TOP WIDTH=20%>Prompt
</TH><TH ALIGN=LEFT VALIGN=TOP WIDTH=20%>User
</TH><TH ALIGN=LEFT VALIGN=TOP WIDTH=20%>Default
</TH><TH ALIGN=LEFT VALIGN=TOP WIDTH=20%>Available parameter values
</TH></TR><TR>
<TD ALIGN=LEFT VALIGN=TOP WIDTH=20%>Data collection server connection port to use
</TD><TD ALIGN=LEFT VALIGN=TOP WIDTH=20%>SERVER:
</TD><TD ALIGN=LEFT VALIGN=TOP WIDTH=20%>
</TD><TD ALIGN=LEFT VALIGN=TOP WIDTH=20%>RS-485
</TD><TD ALIGN=LEFT VALIGN=TOP WIDTH=20%>RS-485, 10baseT, 10base2
This item is displayed only if an Ethernet port is installed in
the terminal. Otherwise, the first prompt is ADDR.
If RS-485 is selected, the next prompt is ADDR. Otherwise, the
IP ADDR prompt follows.
</TD></TR><TR>
<TD ALIGN=LEFT VALIGN=TOP WIDTH=20%>Terminal's IP address
</TD><TD ALIGN=LEFT VALIGN=TOP WIDTH=20%>IP ADDR:
</TD><TD ALIGN=LEFT VALIGN=TOP WIDTH=20%>
</TD><TD ALIGN=LEFT VALIGN=TOP WIDTH=20%>None
</TD><TD ALIGN=LEFT VALIGN=TOP WIDTH=20%>Any valid IP address, input in "dotted decimal" format,
(for
example, 9.86.96.7, 124.376.45.200).
The port number is not specified; it is always 7500. See your
network administrator for the proper IP address to use.
</TD></TR><TR>
<TD ALIGN=LEFT VALIGN=TOP WIDTH=20%>Subnetwork mask
</TD><TD ALIGN=LEFT VALIGN=TOP WIDTH=20%>NETMASK:
</TD><TD ALIGN=LEFT VALIGN=TOP WIDTH=20%>
</TD><TD ALIGN=LEFT VALIGN=TOP WIDTH=20%>None
</TD><TD ALIGN=LEFT VALIGN=TOP WIDTH=20%>Any dotted-decimal IP subnetwork mask pattern (for example,
255.255.240.0).
See your network administrator for the proper subnet mask to use.
</TD></TR><TR>
<TD ALIGN=LEFT VALIGN=TOP WIDTH=20%>Default Router's IP address
</TD><TD ALIGN=LEFT VALIGN=TOP WIDTH=20%>DEFAULT ROUTER:
</TD><TD ALIGN=LEFT VALIGN=TOP WIDTH=20%>
</TD><TD ALIGN=LEFT VALIGN=TOP WIDTH=20%>None
</TD><TD ALIGN=LEFT VALIGN=TOP WIDTH=20%>Any valid IP address, input in "dotted-decimal" format,
(for example, 9.86.96.7, 124.376.45.200).
This tells the 7526 the IP address of an IP host that performs
routing functions when the 7526 finds the server is not on the
same network as itself. See your network administrator for the
proper default router IP address to use.
After this prompt, the next prompt is the TIME prompt.
</TD></TR><TR>
<TD ALIGN=LEFT VALIGN=TOP WIDTH=20%>Terminal network address
</TD><TD ALIGN=LEFT VALIGN=TOP WIDTH=20%>ADDR:
</TD><TD ALIGN=LEFT VALIGN=TOP WIDTH=20%>
</TD><TD ALIGN=LEFT VALIGN=TOP WIDTH=20%>a
</TD><TD ALIGN=LEFT VALIGN=TOP WIDTH=20%>a-y, 0-6
</TD></TR><TR>
<TD ALIGN=LEFT VALIGN=TOP WIDTH=20%>Data speed
</TD><TD ALIGN=LEFT VALIGN=TOP WIDTH=20%>BAUD RATE:
</TD><TD ALIGN=LEFT VALIGN=TOP WIDTH=20%>
</TD><TD ALIGN=LEFT VALIGN=TOP WIDTH=20%>9600
</TD><TD ALIGN=LEFT VALIGN=TOP WIDTH=20%>9600, 19200, 38400, 1200, 2400, 4800
</TD></TR><TR>
<TD ALIGN=LEFT VALIGN=TOP WIDTH=20%>Data character length (bits)
</TD><TD ALIGN=LEFT VALIGN=TOP WIDTH=20%>DATA LENGTH:
</TD><TD ALIGN=LEFT VALIGN=TOP WIDTH=20%>
</TD><TD ALIGN=LEFT VALIGN=TOP WIDTH=20%>8
</TD><TD ALIGN=LEFT VALIGN=TOP WIDTH=20%>8, 7
<P><B>Note: </B>If you are using Custom Function Routines or are using any ASCII
character above 127 (7Fh) in a message file or verification file,
you must use 8 data bits.
</TD></TR><TR>
<TD ALIGN=LEFT VALIGN=TOP WIDTH=20%>Data character parity
</TD><TD ALIGN=LEFT VALIGN=TOP WIDTH=20%>PARITY:
</TD><TD ALIGN=LEFT VALIGN=TOP WIDTH=20%>
</TD><TD ALIGN=LEFT VALIGN=TOP WIDTH=20%>EVEN
</TD><TD ALIGN=LEFT VALIGN=TOP WIDTH=20%>EVEN, ODD, NONE
(Parity of NONE is assumed if DATA LENGTH is set to 8 bits.)
</TD></TR><TR>
<TD ALIGN=LEFT VALIGN=TOP WIDTH=20%>Idle prompt time style
</TD><TD ALIGN=LEFT VALIGN=TOP WIDTH=20%>TIME:
</TD><TD ALIGN=LEFT VALIGN=TOP WIDTH=20%>
</TD><TD ALIGN=LEFT VALIGN=TOP WIDTH=20%>12 HH-MM
</TD><TD ALIGN=LEFT VALIGN=TOP WIDTH=20%>12 HH-MM, 24 HH-MM, 12 HH-t, 12 HH-hh, 24 HH-t, 24 HH-hh
</TD></TR><TR>
<TD ALIGN=LEFT VALIGN=TOP WIDTH=20%>Idle prompt time
separator
</TD><TD ALIGN=LEFT VALIGN=TOP WIDTH=20%>TIME
SEPARATOR:
</TD><TD ALIGN=LEFT VALIGN=TOP WIDTH=20%>
</TD><TD ALIGN=LEFT VALIGN=TOP WIDTH=20%>: (colon)
</TD><TD ALIGN=LEFT VALIGN=TOP WIDTH=20%>: (colon), . (period), - (dash)
</TD></TR><TR>
<TD ALIGN=LEFT VALIGN=TOP WIDTH=20%>Idle prompt date format
</TD><TD ALIGN=LEFT VALIGN=TOP WIDTH=20%>DATE:
</TD><TD ALIGN=LEFT VALIGN=TOP WIDTH=20%>
</TD><TD ALIGN=LEFT VALIGN=TOP WIDTH=20%>MMDDYY
</TD><TD ALIGN=LEFT VALIGN=TOP WIDTH=20%>MMDDYY, DDMMYY, YYMMDD, JJJYY, YYJJJ
</TD></TR><TR>
<TD ALIGN=LEFT VALIGN=TOP WIDTH=20%>Idle prompt date
Separator
</TD><TD ALIGN=LEFT VALIGN=TOP WIDTH=20%>DATE
SEPARATOR:
</TD><TD ALIGN=LEFT VALIGN=TOP WIDTH=20%>
</TD><TD ALIGN=LEFT VALIGN=TOP WIDTH=20%>/ (slash)
</TD><TD ALIGN=LEFT VALIGN=TOP WIDTH=20%>/ (slash), - (dash), . (period)
</TD></TR><TR>
<TD ALIGN=LEFT VALIGN=TOP WIDTH=20%>Decimal
</TD><TD ALIGN=LEFT VALIGN=TOP WIDTH=20%>DECIMAL:
</TD><TD ALIGN=LEFT VALIGN=TOP WIDTH=20%>
</TD><TD ALIGN=LEFT VALIGN=TOP WIDTH=20%>. (period)
</TD><TD ALIGN=LEFT VALIGN=TOP WIDTH=20%>. (period), , (comma)
</TD></TR><TR>
<TD ALIGN=LEFT VALIGN=TOP WIDTH=20%>Keylock mode password
</TD><TD ALIGN=LEFT VALIGN=TOP WIDTH=20%>PASSWORD:
</TD><TD ALIGN=LEFT VALIGN=TOP WIDTH=20%>
</TD><TD ALIGN=LEFT VALIGN=TOP WIDTH=20%>(no
password)
</TD><TD ALIGN=LEFT VALIGN=TOP WIDTH=20%>
Press up to 6 keys in sequence.
Valid keys:
Model 100: F1-F4, Alt
Model 200: F1-F28 (A-Space), 0-9
<BR></TD></TR><TR>
<TD ALIGN=LEFT VALIGN=TOP WIDTH=20%>Display code page
</TD><TD ALIGN=LEFT VALIGN=TOP WIDTH=20%>CODE PAGE:
</TD><TD ALIGN=LEFT VALIGN=TOP WIDTH=20%>
</TD><TD ALIGN=LEFT VALIGN=TOP WIDTH=20%>850
</TD><TD ALIGN=LEFT VALIGN=TOP WIDTH=20%>850, 857
</TD></TR><TR>
<TD ALIGN=LEFT VALIGN=TOP WIDTH=20%>Execute diagnostics
</TD><TD ALIGN=LEFT VALIGN=TOP WIDTH=20%>DIAGNOSTICS:
</TD><TD ALIGN=LEFT VALIGN=TOP WIDTH=20%>
</TD><TD ALIGN=LEFT VALIGN=TOP WIDTH=20%>NO
</TD><TD ALIGN=LEFT VALIGN=TOP WIDTH=20%>NO, YES
(Selecting YES will cause the terminal diagnostics menus to be
presented at this time)
</TD></TR><TR>
<TD ALIGN=LEFT VALIGN=TOP WIDTH=20%>Perform cold start of terminal
</TD><TD ALIGN=LEFT VALIGN=TOP WIDTH=20%>COLD START:
</TD><TD ALIGN=LEFT VALIGN=TOP WIDTH=20%>
</TD><TD ALIGN=LEFT VALIGN=TOP WIDTH=20%>NO
</TD><TD ALIGN=LEFT VALIGN=TOP WIDTH=20%>NO, YES
Selecting YES clears the terminal's memory and performs the
Power-On Self Test.
</TD></TR></TABLE>
<P>
After the last configuration item has been accepted, the terminal
presents the "OUT OF SERVICE" screen until the host
computer has begun the downloading sequence. To change any
parameters or execute diagnostics, press the Shift-Keylock
sequence, and the setup menus will re-appear.
<TABLE><TR><TD ALIGN=LEFT VALIGN=TOP><B>Note:</B></TD><TD ALIGN=LEFT VALIGN=TOP>
As a convenience, you could use a copy of the preceding page to
record the setup values that are to be entered for your
terminals. Record your setup values in the blank
"<B>User value</B>" column. (For security reasons, do
not write your password.)
</td></tr></table>
<P>
<H3><A NAME="HDR27SETUP" HREF="#PToC_66">7527 Terminal Setup</A></H3>
<P>To access the parameter settings for IBM 7527 Terminals, do the
following.
<OL>
<P><LI>Press simultaneously the <B>Shift</B> key and
the key that is labelled with a picture of a key.
<P><LI>When the menu appears press <B>PF3</B> for Maintenance,
and then press <B>PF2</B> for Setup. The first parameter,
Transducer (beeper) volume, is displayed.
<P><LI>Press <B>PF8</B> to show the next parameter or
<B>PF7</B> to show the previous one.
<P><LI>To change any of the parameters, press <B>Enter</B> to
Edit, and then press <B>PF8</B> to display the next setting.
<P>Continue pressing the PF8 key until the desired setting is
displayed.
<P><LI>Press <B>Enter</B> to store the desired setting in memory
and return to the parameter editing menu.
<P><LI>After all parameter settings have been updated, press
<B>PF12</B> to exit and return to the original screen.
</OL>
<P><B>Example:</B>
<P>
To change the amount of expansion memory installed, do the following:
<OL COMPACT>
<LI>Press the <B>PF8</B> key until the expansion memory
parameter is displayed.
<LI>Press <B>Enter</B> to edit.
<LI>Press the <B>PF8</B> key until the desired memory amount is
displayed.
<LI>Press <B>Enter</B> to save the selection.
</OL>
<P>
<A HREF="#TBLSUPARM2">Table 3</A> shows the terminal setup parameters, their
default settings, and their optional settings. The parameters
must be set to the required values for the system.
<TABLE><TR><TD ALIGN=LEFT VALIGN=TOP><B>Note:</B></TD><TD ALIGN=LEFT VALIGN=TOP>The default settings should be used for the four
communications line protocol parameters which are marked with
asterisks.
</td></tr></table>
<BR>
<P><B><A NAME="TBLSUPARM2">Table 3. 7527 Terminal Setup Parameters, Defaults, and Optional Settings</A></B><BR>
<TABLE BORDER>
<TR>
<TH ALIGN=LEFT VALIGN=TOP WIDTH=33%>Parameter
</TH><TH ALIGN=LEFT VALIGN=TOP WIDTH=33%>Default
</TH><TH ALIGN=LEFT VALIGN=TOP WIDTH=33%>Options
</TH></TR><TR>
<TD ALIGN=LEFT VALIGN=TOP WIDTH=33%>Transducer (beeper) volume
</TD><TD ALIGN=LEFT VALIGN=TOP WIDTH=33%>Low
</TD><TD ALIGN=LEFT VALIGN=TOP WIDTH=33%>High, Off
</TD></TR><TR>
<TD ALIGN=LEFT VALIGN=TOP WIDTH=33%>Terminal ID
(address)
</TD><TD ALIGN=LEFT VALIGN=TOP WIDTH=33%>(This is a nonoperational ID that prevents a cold-start
terminal from interfering with communications to other
terminals)
</TD><TD ALIGN=LEFT VALIGN=TOP WIDTH=33%>A-Y, 0-6
</TD></TR><TR>
<TD ALIGN=LEFT VALIGN=TOP WIDTH=33%>Network port
</TD><TD ALIGN=LEFT VALIGN=TOP WIDTH=33%>RS-485
</TD><TD ALIGN=LEFT VALIGN=TOP WIDTH=33%>RS-232C
</TD></TR><TR>
<TD ALIGN=LEFT VALIGN=TOP WIDTH=33%>Network speed
</TD><TD ALIGN=LEFT VALIGN=TOP WIDTH=33%>9600
</TD><TD ALIGN=LEFT VALIGN=TOP WIDTH=33%>110, 150, 300, 1200, 2400, 4800, or 19200 bits per second
</TD></TR><TR>
<TD ALIGN=LEFT VALIGN=TOP WIDTH=33%>Network parity
</TD><TD ALIGN=LEFT VALIGN=TOP WIDTH=33%>None
</TD><TD ALIGN=LEFT VALIGN=TOP WIDTH=33%>Odd or Even
</TD></TR><TR>
<TD ALIGN=LEFT VALIGN=TOP WIDTH=33%>Network data bits
</TD><TD ALIGN=LEFT VALIGN=TOP WIDTH=33%>8
</TD><TD ALIGN=LEFT VALIGN=TOP WIDTH=33%>6 or 7 data bits
</TD></TR><TR>
<TD ALIGN=LEFT VALIGN=TOP WIDTH=33%>Network stop bits
</TD><TD ALIGN=LEFT VALIGN=TOP WIDTH=33%>1
</TD><TD ALIGN=LEFT VALIGN=TOP WIDTH=33%>2 stop bits
</TD></TR><TR>
<TD ALIGN=LEFT VALIGN=TOP WIDTH=33%>Amount of expansion memory installed
</TD><TD ALIGN=LEFT VALIGN=TOP WIDTH=33%>0 bytes
</TD><TD ALIGN=LEFT VALIGN=TOP WIDTH=33%>128KB or 256KB
</TD></TR><TR>
<TD ALIGN=LEFT VALIGN=TOP WIDTH=33%>Terminal user's password
</TD><TD ALIGN=LEFT VALIGN=TOP WIDTH=33%>
<BR></TD><TD ALIGN=LEFT VALIGN=TOP WIDTH=33%>Can be up to 6 alphanumeric characters
</TD></TR><TR>
<TD ALIGN=LEFT VALIGN=TOP WIDTH=33%>Language
</TD><TD ALIGN=LEFT VALIGN=TOP WIDTH=33%>English
</TD><TD ALIGN=LEFT VALIGN=TOP WIDTH=33%>French, German, Spanish, or Swedish
</TD></TR><TR>
<TD ALIGN=LEFT VALIGN=TOP WIDTH=33%>Date separator
</TD><TD ALIGN=LEFT VALIGN=TOP WIDTH=33%>/ (slash)
</TD><TD ALIGN=LEFT VALIGN=TOP WIDTH=33%>- (dash) or . (period)
</TD></TR><TR>
<TD ALIGN=LEFT VALIGN=TOP WIDTH=33%>Time separator
</TD><TD ALIGN=LEFT VALIGN=TOP WIDTH=33%>: (colon)
</TD><TD ALIGN=LEFT VALIGN=TOP WIDTH=33%>. (period)
</TD></TR><TR>
<TD ALIGN=LEFT VALIGN=TOP WIDTH=33%>Date format
</TD><TD ALIGN=LEFT VALIGN=TOP WIDTH=33%>MM/DD/YY (month/day/year)
</TD><TD ALIGN=LEFT VALIGN=TOP WIDTH=33%>
DD/MM/YY
(day/month/year)
YY/MM/DD
(year/month/day)
JJJ/YY
(day-of-the-year/year)
YY/JJJ
(year/day-of-the-year)
<BR></TD></TR><TR>
<TD ALIGN=LEFT VALIGN=TOP WIDTH=33%>Time format
</TD><TD ALIGN=LEFT VALIGN=TOP WIDTH=33%>12-hour
</TD><TD ALIGN=LEFT VALIGN=TOP WIDTH=33%>24-hour
</TD></TR><TR>
<TD ALIGN=LEFT VALIGN=TOP WIDTH=33%>Current date
</TD><TD ALIGN=LEFT VALIGN=TOP WIDTH=33%>
<BR></TD><TD ALIGN=LEFT VALIGN=TOP WIDTH=33%>Set the correct date
</TD></TR><TR>
<TD ALIGN=LEFT VALIGN=TOP WIDTH=33%>Current time
</TD><TD ALIGN=LEFT VALIGN=TOP WIDTH=33%>
<BR></TD><TD ALIGN=LEFT VALIGN=TOP WIDTH=33%>Set the correct time
</TD></TR><TR>
<TD ALIGN=LEFT VALIGN=TOP WIDTH=33%>Touch screen installed
</TD><TD ALIGN=LEFT VALIGN=TOP WIDTH=33%>Disabled (not installed)
</TD><TD ALIGN=LEFT VALIGN=TOP WIDTH=33%>Enabled (installed)
</TD></TR><TR>
<TD ALIGN=LEFT VALIGN=TOP WIDTH=33%>Display mode
</TD><TD ALIGN=LEFT VALIGN=TOP WIDTH=33%>Normal (positive image)
</TD><TD ALIGN=LEFT VALIGN=TOP WIDTH=33%>Reverse (negative image)
</TD></TR></TABLE>
<P>
<H3><A NAME="HDR24RFSTP" HREF="#PToC_67">7524 RF Terminal Setup</A></H3>
<P>Setting up 7524 RF terminals involves not only setting up the
terminals, but also the base or bases, and controller. For
information on configuration, refer to the <CITE>7524 Interface
Support Installation and User's Guide</CITE>.
<P>
<H3><A NAME="Header_68" HREF="#PToC_68">7524 Batch Terminal Setup</A></H3>
<P>Setting up 7524 batch terminals (models -050 and
-100) involves setting up parameters, including the
following:
<UL COMPACT>
<LI>Terminal address
<LI>Communications speed
<LI>Display size
</UL>
<P>
When the 7524 batch terminal is first received or when its
parameters have been reset, the terminal address is set to the
default asterisk (*). All other parameters are also set to
default values.
<P>
You can display the 7524 menus by pressing the gold key followed
by the black key on the terminal. The main menu is displayed
with the following options:
<UL COMPACT>
<LI>LCD CONTRAST
<LI>BEEPER ADJUST
<LI>SYSTEM SETUP
<LI>INFO/STATUS
<LI>EXIT MENU
<LI>SAVE CONFIG
<LI>TEST DEVICES
</UL>
These options lead to lower-level menus and screens with
options to be set. You can:
<UL COMPACT>
<LI>Choose <B>LCD CONTRAST</B> to bring up a screen that
allows you to adjust the black/white contrast of the terminal
screen.
<LI>Choose <B>BEEPER ADJUST</B> to bring up a lower-level
menu and screens that allow you to change the volume, duration,
and frequency of both the key click and the alarm tone.
<LI>Choose <B>SYSTEM SETUP</B> to display a password
prompt to be displayed. The valid password is always
<B>CR52401</B>. After you enter the valid password, the
following menu is displayed:
<OL COMPACT>
<LI>DISPLAY SIZES
<LI>BACKLITE TIME
<LI>RS-232 PARMS
<LI>PASSWORD
<LI>SCANNER TYPE
<LI>RESET PARMS
<LI>RETURN
</OL>
</UL>
<P>These options lead to a third tier of screens. You can:
<UL COMPACT>
<LI>Choose <B>DISPLAY SIZES</B> to define the
number of rows and columns that should appear on the physical
terminal display.
<LI>Choose <B>BACKLITE TIME</B> to define how long the
backlight stays lit once it is turned on. The backlight is
turned on by pressing the gold key followed by the key with the
gold light symbol over it.
<LI>Choose <B>RS-232 PARMS</B> to bring
up another menu that allows you
to select the following parameters:
<UL COMPACT>
<LI>Terminal <B>ADDRESS</B> (A-Y, 0-6)
<LI><B>BAUD</B> rate (300, 1200, 2400, 4800, 9600, 19200, 38400)
<LI><B>RESEND TIMER</B> - the value set
is used to determine when to
resend transactions if they have not been released
within a certain period of
time.
<LI>Communications <B>TRIGGER</B> -- This setting is
used to specify when power is applied to the RS-232 port of
the terminal. The choices are:
<UL COMPACT>
<LI><B>ON</B> means the power to the port is always on.
<LI><B>KEY</B> means the power is applied when you press
the black key at the lower-left corner of the terminal. The
terminal automatically goes to the menu screen, which shows how
many transactions are buffered in the terminal. Power to the
port remains on until you press Enter to leave this screen.
<LI><B>PWR</B> means power to the port is On only when
external power is being applied to the terminal (not just the
battery). When power is applied to the terminal, the terminal
automatically displays the menu screen, which shows how many
transactions are buffered in the terminal. However, unlike the
Key-initiated power, power to the port remains on as long
as power is being applied to the terminal, even if you
press Enter from this screen.
The purpose of this option is to provide a way to increase the
battery life for the terminal.
</UL>
<P>Use the number keys to choose which option should be changed,
then use the <B>Up Arrow</B> and <B>Down Arrow</B> keys
to change the setting of the
current option. Choose the
<B>RESEND TIMER</B> option to
bring up a separate screen allowing you to view or change the setting.
<LI>Choose <B>PASSWORD</B> to set up a password that
restricts access to the menus. This password is considered a
secondary password because the master password, CR52401, can be
used to access the menus, even if the password specified here is
different. Whether or not a password is defined here, the
password for the SYSTEM SETUP is <I>always</I> CR52401.
<LI>Choose <B>SCANNER TYPE</B> to select whether the
tethered or integrated scanner is one of the following: WAND,
LASER, WAND EMULATOR, or AUTO-DETECT.
<LI>Choose <B>RESET PARMS</B> to set all parameters in the
menus to their default values. The terminal address is set back
to asterisk (*). Before the parameters are reset, you must enter
the master password: CR52401. Entering the master password
prevents you from accidentally resetting the parameters. After
you reset the parameters, you must power the terminal off and on
for the reset to complete. After you have entered the
confirmation password, switch off the terminal.
</UL>
<LI>Choose <B>INFO/STATUS</B> to bring up a secondary menu
that allows you to view the version information for the terminal
flash programs. You can also display the screen that shows how
many transactions are buffered in the terminal and how many more
can be buffered.
<P>
From the version information screen, you usually press Enter to
leave the screen. However, if you press the 1 key, you can view
the last 20 messages that were sent to, or received from, the
host PC.
<LI>Choosing <B>EXIT MENU</B> erases the menus and replaces
them with the current idle menu. Pressing Enter accomplishes the
same thing as choosing this option.
<LI>Choose <B>SAVE CONFIG</B> to save the current
parameters to the terminal's flash memory for safe keeping. If
the terminal loses its memory due to a battery completely dying,
the terminal attempts to restore its configuration from the last
one that was saved to flash memory.
<LI>Choose <B>TEST DEVICES</B> to bring up a menu from which
tests can be run for the display, keyboard, clock, and scanner.
These tests are intended to be used during the manufacturing
process to ensure the terminal is working correctly. Therefore,
some of the tests require that the terminal address be set to the
default asterisk (*)
before the test can be run. This can be accomplished
by choosing the <B>RESET PARMS</B> option previously described.
</UL>
<HR>
<H1><A NAME="HDRCABLE" HREF="#ToC_69">Native Serial Port Cables</A></H1>
<P>
There are numerous ways to accomplish the cabling of the serial port
of the IBM Industrial Computer or PC to the data collection terminal:
<UL>
<P><LI>Custom cables meeting the requirements shown in the following
pages of this Appendix.
<P><LI>Standard cables with correct gender and number of pins
and a "Communications Configurator or Breakout Box,"
which allow you to use jumpers to make the required connections.
<P><LI>"Null Modem" cables meeting the requirements of
connectors and wiring.
</UL>
<TABLE><TR><TD ALIGN=LEFT VALIGN=TOP><B>Note:</B></TD><TD ALIGN=LEFT VALIGN=TOP>
The data shown here is typical and may not match all computers that
can support the data collection terminals. Test operation of the
DCT with the computer using <I>one</I> sample cable
before ordering any quantity of cables.
</td></tr></table>
<HR>
<H2><A NAME="Header_70" HREF="#PToC_70">Cabling RS-232 Computer Port to RS-232 Terminal Port</A></H2>
<img src=e9iv0001.GIF>
<HR>
<H2><A NAME="Header_71" HREF="#PToC_71">Cabling RS-232 Computer Port to RS-422 Terminal Port</A></H2>
<img src=e9iv0002.GIF>
<HR>
<H1><A NAME="HDRINDEX_START" HREF="#ToC_72">Index</A></H1>
<A NAME=Bot_Of_Page></A>
</BODY></HTML>
]]>