 |
Home: www.argecy.com |
 |
sales@argecy.com |
 |
Instant Message |
|
|
|
|
|||||||||||
BOS eTwinax Controller
IPDS
Printing on Twinax via TCP/IP
Tests show that IPDS printing takes one third the number of TCP/IP packets to print the same document via native TCP/IP than via SNA. Imagine the performance improvement by moving a 56K frame relay circuit supporting a number of IPDS printers using SNA to TCP/IP with an e-Twinax Controller!
Our easy to install Twinax controller improves performance of your twinax network while protecting your investment. The controller supports all Twinax display stations, SCS and IPDS printers, and existing cabling.
Problems with Areas Anynet (MPTN)
As users started to use Anynet, flaws
began to appear, particularly when large amounts of data needed to be
transported.
Typical problems included disconnecting sessions and slow performance.
These problems were not readily apparent on local networks; they were
much
more prevalent when the timing between the host and device is delayed.
In recent tests we tried to establish a connection across the Internet.
We were able to get a session started using a PC with the NS/Router,
however
within three minutes of working with this session it disconnected. We
also
tried connecting with a remote controller, which used the same
protocol.
We were able to vary on the controller, however the terminals on the
controller
never established a connection.
TCP/IP Makes its Entrance
In recent years IBM has focused their
development on TN5250. With the arrival of V4R2 (and later PTFs to
support
older versions) IBM supported TN5250e and TN3270e. This enhanced TCP/IP
support enabled the AS/400 and 3270 hosts to support device naming and
SCS printer support. For the first time, users could really take
advantage
of native TCP/IP support on these hosts. IPDS was also supported
directly
with TCP/IP using PPD/PPR (a special protocol developed for this
specific
purpose). Recent versions of Client Access (Client Access Express)
contain
support for native TCP/IP only, providing proof that IBM’s direction is
to provide better support for native TCP/IP on these host computers.
Advantages of TCP/IP over Anynet
(MPTN)
Because TN5250 and TN3270 use native
support
on the system, they do not require as many CPU cycles to make use
of
it. TN5250e and TN3270e do not have the timing limitations that SNA
has,
therefore these protocols can be used over the Internet with no
problem.
IBM has realized this and that is one of the reasons that Client Access
Express supports SSL encryption, to enable users who want to connect
using
the Internet a way to do so without encountering security issues.
Recent
tests show that IPDS printing takes three times the number of TCP/IP
packets
to print the same document via SNA than via native TCP/IP. Imagine the
effect on the performance of a 56K frame relay circuit supporting a
number
of IPDS printers using SNA!
IBM 5494 Controller has been
Withdrawn
The IBM 5494 Controller was discontinued
at the end of 1999, and now both Perle and NLynx are developing TN5250
controllers of their own. BOScom clearly leads the field with its
e-Twin@x
Controller, since it uses the same TCP/IP protocol as the very stable
and
field-tested BOSâNOVA TCP/IP TN5250e emulator, which has been
installed
and working on hundreds of thousands PCs since 1997. For experience and
state-of-the-art technology, choose BOScom.
Secure,
Reliable, Low Cost Connection using theInternet
When the
traditional SDLC connection is replaced with a Wide Area Network (WAN)
connection using TCP/IP, the e-Twin@x Controller can be used to
maintain
legacy Twinax devices (such as high-speed printers and dumb terminals)
at your remote sites. In this configuration, all the devices will
appear
on the AS/400 as TN5250 devices, and all PC devices can connect to the
AS/400 either by using dumb terminal emulation or by installing the
e-Twin@x
version of BOS?NOVA TCP/IP or IBM TCP/IP drivers to connect to the
AS/400
over TCP/IP.
Secure
connection via the Internet using modem(s) for a mixed Twinax and LAN
environment
The
e-Twin@x
Controller can be connected to the AS/400 via the Internet, saving you
a fortune in leased line expenses. Requirements are minimal:
Configuration
and Maintenance with Ease
The
e-Twin@x
Controller is managed via a standard Web browser, which enables all of
the units to be managed from a central point anywhere on the network,
or
via a modem dialed in to the RAS. Configuration can also be done using
a dumb terminal attached to any of the ports. The Controller software
can
also be updated over the network or via dial-in. Terminals, PCs or
printers
can be added to the Controller very simply using a plug-and-play
feature
in Auto mode. The device name can be changed at any time, without
restarting
the Controller. The Controller also verifies the host connection,
including
which PTFs are installed for each OS version.
Configuration
and management can be done via standard Web browser from anywhere on
the
network
e-Twin@x
Controller as an IP Gateway
The e-Twin@x Controller connects to the network using a standard network hub, which is attached to the local office via a standard IP router. Ethernet PCs can be connected to the same network hub as the Controller for mixed Ethernet and Twinax infrastructures.
With the TCP/IP drivers loaded on the PC, the user can take full advantage of the WAN, and get:
Dial Backup*
The Dial Backup feature ensures improved uptime for Controllers that are connected to an AS/400 using a LAN connection (via the Internet routers or a separate Frame Relay network). If the LAN connection fails, the Dial Backup provides (via an attached modem) an additional method to connect to the AS/400. Two configurations are available: Always, which provides a simultaneous connection at all times; and "On LAN Failure, which causes the Controller to activate the modem connection only when LAN connectivity failure is detected.
* Optional
Automatic Session Recovery
In the event that a router on a frame-relay network disconnects and then re-connects, users of remote Twinax-attached devices can choose to resume their current session. The e-Twin@x Controller can be set to automatically recover the session, within a user-defined time period, ensuring smooth and efficient operations even in cases of network instability.
Customized Object for Specialty Printers
The e-Twin@x Controller supports a wide variety of Twinax printers, including label and barcode printers that are often called upon to deal with special printing requirements such as oversized fonts, graphics, and unusual page sizes. A parameter can be set to instruct the host to send a pure data stream through the e-Twin@x Controller, allowing it to override the original complex formatting commands with simplified commands that are supported by most printer models, before releasing the job to the destination printer.
e-TwinSt@r Series Reduces Need for Need for Active Star Hubs
The e-TwinSt@r Series Controller includes a built-in unit featuring 8 (or 16) RJ45 sockets. Twinax devices working over CAT5 lines are connected directly to the Controller, saving the cost of an active star hub and eliminating the need for power sources and additional space in the communications closet, as well as the extra set-up and maintenance time.
E-mail on Dumb Twinax Terminals*
Basic e-mail functionality, known as TwinMailTM, is supported on dumb Twinax terminals. In addition to sending and receiving e-mail, TwinMail includes a personal address book that can be organized according to user-defined preferences.
* Optional
PC
Remote Access
The
e-Twin@x
Controller supports a 2- or 6-port* Remote Access Server (RAS),
providing
remote PC users with network access in addition to AS/400 access.
Remote
users can dial in to the e-Twin@x Controller and gain access to the
network
using the RAS. This RAS includes a firewall for restricting access per
user to specific IP devices or ports (e.g. one group of users may be
allowed
access to the AS/400 for display emulation, but not file transfer). The
RAS also automatically logs all remote access activity. The RAS
component
can use the services of any RADIUS server for authentication, if
required.
* Optional