Black Box PC435A User Manual

CUSTOMER
SUPPORT
INFORMATION
Order toll-free in the U.S.: Call 877-877-BBOX (outside U.S. call 724-746-5500) FREE technical support 24 hours a day, 7 days a week: Call 724-746-5500 or fax 724-746-0746 Mailing address: Black Box Corporation, 1000 Park Drive, Lawrence, PA 15055-1018 Web site: www.blackbox.com • E-mail: info@blackbox.com
MARCH 2003
Ethernet to Twinax/Coax Print Server
1
FCC AND IC RFI STATEMENTS
FEDERAL COMMUNICATIONS COMMISSION AND INDUSTRY CANADA
RADIO-FREQUENCY INTERFERENCE STATEMENTS
This equipment generates, uses, and can radiate radio-frequency energy, and if not installed and used properly, that is, in strict accordance with the manufacturer’s instructions, may cause interference to radio communication. It has been tested and found to comply with the limits for a Class A computing device in accordance with the specifications in Subpart B of Part 15 of FCC rules, which are designed to provide reasonable protection against such interference when the equipment is operated in a commercial environment. Operation of this equipment in a residential area is likely to cause interference, in which case the user at his own expense will be required to take whatever measures may be necessary to correct the interference.
Changes or modifications not expressly approved by the party responsible for compliance could void the user’s authority to operate the equipment.
This digital apparatus does not exceed the Class A limits for radio noise emission from digital apparatus set out in the Radio Interference Regulation of Industry Canada. It complies with ICES-003.
Le présent appareil numérique n’émet pas de bruits radioélectriques dépassant les limites applicables aux appareils numériques de la classe A prescrites dans le Règlement sur le brouillage radioélectrique publié par Industrie Canada. Se conforme à ICES-003.
2
ETHERNET TO TWINAX/COAX PRINT SERVER
EUROPEAN UNION DECLARATION OF CONFORMITY
This product is in conformity with the protection requirements of EU Council Directives 72/23/EEC and 89/336/EEC on the approximation of the laws of the Member States relating to standards EN60950 (Safety of Information Technology Equipment); EN50082-1 (Generic Immunity Standard for Residential, Commercial, and Light Industrial Products); and EN55022 (Limits and Methods of Measurement of Radio Interference from Information Technology Equipment).
CAUTION
This is a Class A product. In a domestic environment, this product may cause radio interference, in which case the user may be required to take adequate corrective measures.
3
TRADEMARKS USED IN THIS MANUAL
TRADEMARKS USED IN THIS MANUAL
AnyNet, AS/400, IBM, OS/2, and OS/400 are registered trademarks of
International Business Machines Corporation.
Microsoft, Windows, and Windows NT are registered trademarks or trademarks of
Microsoft Corporation in the United States and/or other countries.
NetWare and Novell are registered trademarks of Novell, Inc.
UL is a registered trademark of Underwriters Laboratories Incorporated.
UNIX is a registered trademark of UNIX System Laboratories, Inc.
Any other trademarks mentioned in this manual are acknowledged to be the property of the
trademark owners.
4
ETHERNET TO TWINAX/COAX PRINT SERVER
NORMAS OFICIALES MEXICANAS (NOM)
ELECTRICAL SAFETY STATEMENT
INSTRUCCIONES DE SEGURIDAD
1. Todas las instrucciones de seguridad y operación deberán ser leídas antes de que el aparato eléctrico sea operado.
2. Las instrucciones de seguridad y operación deberán ser guardadas para referencia futura.
3. Todas las advertencias en el aparato eléctrico y en sus instrucciones de operación deben ser respetadas.
4. Todas las instrucciones de operación y uso deben ser seguidas.
5. El aparato eléctrico no deberá ser usado cerca del agua—por ejemplo, cerca de la tina de baño, lavabo, sótano mojado o cerca de una alberca, etc..
6. El aparato eléctrico debe ser usado únicamente con carritos o pedestales que sean recomendados por el fabricante.
7. El aparato eléctrico debe ser montado a la pared o al techo sólo como sea recomendado por el fabricante.
8. Servicio—El usuario no debe intentar dar servicio al equipo eléctrico más allá a lo descrito en las instrucciones de operación. Todo otro servicio deberá ser referido a personal de servicio calificado.
9. El aparato eléctrico debe ser situado de tal manera que su posición no interfiera su uso. La colocación del aparato eléctrico sobre una cama, sofá, alfombra o superficie similar puede bloquea la ventilación, no se debe colocar en libreros o gabinetes que impidan el flujo de aire por los orificios de ventilación.
10. El equipo eléctrico deber ser situado fuera del alcance de fuentes de calor como radiadores, registros de calor, estufas u otros aparatos (incluyendo amplificadores) que producen calor.
11. El aparato eléctrico deberá ser connectado a una fuente de poder sólo del tipo descrito en el instructivo de operación, o como se indique en el aparato.
5
NOM STATEMENT
12. Precaución debe ser tomada de tal manera que la tierra fisica y la polarización del equipo no sea eliminada.
13. Los cables de la fuente de poder deben ser guiados de tal manera que no sean pisados ni pellizcados por objetos colocados sobre o contra ellos, poniendo particular atención a los contactos y receptáculos donde salen del aparato.
14. El equipo eléctrico debe ser limpiado únicamente de acuerdo a las recomendaciones del fabricante.
15. En caso de existir, una antena externa deberá ser localizada lejos de las lineas de energia.
16. El cable de corriente deberá ser desconectado del cuando el equipo no sea usado por un largo periodo de tiempo.
17. Cuidado debe ser tomado de tal manera que objetos liquidos no sean derramados sobre la cubierta u orificios de ventilación.
18. Servicio por personal calificado deberá ser provisto cuando:
A: El cable de poder o el contacto ha sido dañado; u
B: Objetos han caído o líquido ha sido derramado dentro del aparato; o
C: El aparato ha sido expuesto a la lluvia; o
D: El aparato parece no operar normalmente o muestra un cambio en su
desempeño; o
E: El aparato ha sido tirado o su cubierta ha sido dañada.
6
ETHERNET TO TWINAX/COAX PRINT SERVER
Contents
Chapter Page
1. Specifications ........................................................................................................8
2. Introduction ........................................................................................................11
2.1 Overview .......................................................................................................11
2.2 The Complete Package .............................................................................. 11
2.3 The Print Server’s External Components ...................................................12
2.3.1 LED Indicators ................................................................................. 12
2.3.2 Connectors and Switch ...................................................................... 13
2.4 Network Connectivity....................................................................................14
2.5 Multiprotocol LAN Printing.........................................................................14
2.6 Multi-Host Printing .......................................................................................14
2.7 Multiprotocol IBM Host-to-LAN Printing ...................................................15
2.7.1 AS/400 to LAN Printing.....................................................................15
2.7.2 IBM Mainframe Printing ....................................................................15
3. Installation ........................................................................................................ 18
3.1 Hardware Installation ................................................................................. 18
3.2 Print-Control Software Installation ........................................................... 19
3.3 Using the Print-Control Software ...............................................................19
3.4 Proceeding with System Configuration .......................................................20
4. TCP/IP Printing ...................................................................................................21
4.1 Configuring the Print Server........................................................................22
4.1.1 Assign TCP/IP Address ......................................................................22
4.1.2 Verify Correct Installation ..................................................................22
4.1.3 Configuring a Print Server on a Remote TCP/IP Subnet ...............23
4.1.4 Where to Now…..................................................................................24
4.2 Configuring the IBM Mainframe for TN3270e ..........................................24
4.3 Configuring for IPDS Printing .....................................................................25
4.4 Configuring OS/400 for TN5250e ..............................................................25
4.4.1 Configuring the AS/400.....................................................................25
4.4.2 Configuring the Print Server for TN5250e Printing ........................27
4.5 Configuring OS/400 for AnyNet .................................................................30
4.5.1 AnyNet Configuration Worksheet .....................................................30
4.5.2 Configuring the AS/400 for AnyNet .................................................32
4.5.3 Configuring the Print Server for AnyNet Printing ...........................35
4.6 Configuring Windows NT V3.x ....................................................................36
4.7 Configuring Windows NT V4.x ....................................................................38
4.8 TCP/IP DirectPort Printing for Windows 95/98........................................39
4.8.1 TCP/IP DirectPort Installation..........................................................39
4.8.2 Selecting DirectPort Printing .............................................................39
4.8.3 Removing DirectPort from Windows 95/98 .....................................40
7
CONTENTS
Chapter Page
5. Novell NetWare Printing......................................................................................41
5.1 Configuring the Print Server........................................................................41
5.1.1 Remote (Printer on IPX) ..................................................................42
5.1.2 Remote (LPR on IP)..........................................................................42
5.1.3 Forward Jobs to a Queue ...................................................................42
5.1.4 Client Configuration..........................................................................43
5.1.5 Public Access Printers ........................................................................43
5.1.6 Controlled Access Printers ................................................................43
5.2 Controlled or Public Access Printer, Novell NetWare 5.x (NDPS),
NWAdmin ..................................................................................................43
5.2.1 Prerequisites .......................................................................................44
5.2.2 Creating a NDPS Printer Object.......................................................44
5.3 Print Server, Novell NetWare 4.x (NDS), NWAdmin.................................46
5.3.1 Entering NWAdmin...........................................................................46
5.3.2 Adding a Print Server Object ............................................................46
5.3.3 Adding Printer Objects......................................................................47
5.3.4 Adding Print Queue Objects.............................................................47
5.3.5 Configuring the Print Server.............................................................48
5.3.6 Client Configuration..........................................................................49
5.4 Print Server, Novell NetWare 4.x (NDS), PCONSOLE..............................50
5.4.1 Adding a Print Server Object ............................................................50
5.4.2 Adding Printer Objects......................................................................51
5.4.3 Adding Print Queue Objects.............................................................52
5.4.4 Configuring the Print Server.............................................................53
5.4.5 Client Configuration..........................................................................54
5.5 Remote Printer, Novell NetWare 4.x (NDS), NWAdmin...........................54
5.5.1 Entering NWAdmin...........................................................................55
5.5.2 Optional: Adding a Print Server .......................................................55
5.5.3 Adding Printer Objects......................................................................55
5.5.4 Adding Print Queue Objects.............................................................56
5.5.5 Reloading the Print Server NLM ......................................................57
5.5.6 Configuring the Print Server.............................................................57
5.5.7 Client Configuration..........................................................................58
5.6 Remote Printer, Novell NetWare 4.x (NDS), PCONSOLE........................59
5.6.1 Optional: Adding a Print Server .......................................................59
5.6.2 Adding Printer Objects......................................................................60
5.6.3 Adding Print Queue Objects.............................................................61
5.6.4 Reloading the Print Server NLM ......................................................62
5.6.5 Configuring the Print Server.............................................................62
5.6.6 Client Configuration..........................................................................63
5.7 Print Server, Novell NetWare 3.x and 2.x...................................................64
5.7.1 Creating NetWare Objects.................................................................64
5.7.2 Client Configuration..........................................................................66
8
ETHERNET TO TWINAX/COAX PRINT SERVER
Contents (continued)
Chapter Page
5.8 Remote Printer, Novell NetWare 3.x and 2.x, PCONSOLE ......................66
5.8.1 Adding Print Queue Objects on the Novell Server .........................67
5.8.2 Optional: Adding a Print Server Object on the Novell Server .......67
5.8.3 Adding Printer Objects on the Novell Server ..................................68
5.8.4 Associating Printer Objects with Print Queue Objects ...................69
5.8.5 Reloading the NetWare PServer NLM .............................................69
5.8.6 Configuring the Print Server.............................................................69
5.8.7 Client Configuration..........................................................................70
6. SNA (APPC) Printing...........................................................................................71
6.1 Configuring the Print Server........................................................................71
6.2 Retrieving AS/400 Parameters.....................................................................73
6.2.1 Adapter Address (AS/400)................................................................73
6.2.2 Host Network ID and Host Control Point Name ............................73
6.2.3 AS/400 Autoconfiguration................................................................74
7. Twinax/Coax Configuration ...............................................................................75
7.1 Twinax Port Configuration...........................................................................77
7.2 3270-Coax Port Configuration .....................................................................78
7.3 ASCII Printing Configuration ......................................................................79
7.4 Command Pass-Through ..............................................................................82
8. IBM IPDS Printing................................................................................................84
8.1 Configuring the AS/400 for IPDS Printing.................................................84
8.1.1 Requirements .....................................................................................85
8.1.2 Creating a Line Description on the AS/400....................................86
8.1.3 Configuring a TCP/IP Host Table Entry .........................................86
8.1.4 Configuring V3R1 or V3R6 ...............................................................86
8.1.5 Configuring for V3R2 ........................................................................88
8.1.6 Configuring for V3R7, V4R1, and Above .........................................89
8.1.7 Verifying the IPDS Configuration on the AS/400...........................91
8.2 Configuring the IBM Mainframe for IPDS Printing ..................................91
8.2.1 Requirements .....................................................................................92
8.2.2 Define the Communications Control Unit to MVS.........................92
8.2.3 Modify the TCP/IP Profile in MVS...................................................93
8.2.4 Verify the Print Connection (Ping the Print Server) ......................94
8.2.5 Handling MVS Connectivity Problems.............................................95
8.2.6 Define the Printer to JES...................................................................96
8.2.7 Define the Printer to PSF/MVS ........................................................97
8.2.8 Using the Print Server with MVS ......................................................98
9
CONTENTS
Chapter Page
9. Troubleshooting ................................................................................................100
9.1 Performing Software/Firmware Updates..................................................100
9.2 The Print Server’s Self-Test ........................................................................100
9.2.1 Printing a Self-Test Using the Print-Control Utility ......................100
9.2.2 Printing a Self-Test Using the Print Server’s Mode Button ..........101
9.3 The Print Server’s Diagnostic Report ........................................................101
9.4 Restoring the Print Server’s Factory Defaults ...........................................102
9.4.1 Restoring Factory Defaults for the Print Server Using the
Print Control Utility.........................................................................102
9.4.2 Restoring Factory Defaults for the Print Server
Using the Mode Button...................................................................102
9.5 Problems, Causes, and Solutions ...............................................................102
9.5.1 SNA (APPC) Printing ......................................................................102
9.5.2 TCP/IP Printing...............................................................................104
9.5.3 TN5250e Printing ............................................................................105
9.5.4 TN5250e Connection Status Message ............................................107
9.5.5 IPDS Printing ...................................................................................109
9.5.6 NetWare Printing .............................................................................111
9.5.7 Print-Server Operation ....................................................................115
9.5.8 Hardware Problems .........................................................................119
9.5.9 TN3270e Printing ............................................................................120
9.6 LED Sequence .............................................................................................121
9.7 AS/400 Communication Trace..................................................................122
9.8 Calling Black Box ........................................................................................122
9.9 Shipping and Packaging .............................................................................123
Appendix: ASCII Commands....................................................................................124
10
ETHERNET TO TWINAX/COAX PRINT SERVER
1. Specifications
Compliance: FCC: Part 15, Class A;
UL
®
: 8M28 E150854;
cUL: E1550854
LAN Hosts Supported: IBM
®
AS/400®, 3270 type mainframes, Novell®NetWare®,
UNIX
®
, Windows®95/98/Me, Windows 2000, Windows NT
®
Host Systems: IBM AS/400 System, IBM 3270-type Mainframes, UNIX, Windows,
Novell
Printers Supported: SCS: All 5250 SCS twinax and 3270 SCS/DSC coax printers;
IPDS: All 5250 and 3270 laser printers; All 4224, 4230, and 4234 line/dot-matrix printers
Connectors: Coax: (1) BNC for 3270 printer;
Ethernet: (1) RJ-45; Twinax: (1) DB9 for 5250 printer (DB9 to twinax autoterminating “V” barrel
connector included):
Diagnostic port: (1) DB25 female
Indicators: LEDs: (1) Power, (1) Line Sync, (1) LAN Data, (1) Printer Activity,
(1) Printer Error;
Dual LEDs for mode of operation: Off/Off = Normal Operation, Off/On =
EBCDIC Self Test, On/Off = ASCII Self Test, On/On = Diagnostic Dump
Operating Environment: Temperature: 40 to 100°F (4 to 38°C);
Humidity: 10 to 90%, noncondensing
Power: External power supply: Input: 110–240 VAC, 47–63 Hz, autosensing;
Output: 5 VDC, 3 amp
Size: 1.4"H x 8.4"W x 5.6"D (3.6 x 21.3 x 14.2 cm)
Weight: 0.9 lb. (0.4 kg)
11
CHAPTER 2: Introduction
2. Introduction
2.1 Overview
The Ethernet to Twinax/Coax Print Server connects an IBM®or IBM compatible twinax or 3270-coax printer to an AS/400
®
or IBM mainframe across an Ethernet topology using SNA and TCP/IP protocols. It lets you retain your investment in expensive but reliable twinax or 3270-coax printers where you have converted from twinax or 3270-coax to Ethernet.
The print server also allows PCs and other ASCII hosts (such as UNIX
®
servers)
using Windows
®
, OS/2®, or DOS to send text (non-rasterized) print jobs across LAN/WANs to SCS twinax or SCS/DSC 3270-coax printers. This increases the value of your twinax or 3270-coax printers by allowing them to be used for more than just a host printer.
The print server connects to the IBM host using any one of several protocols.
These include SNA(APPC), AnyNet
®
, PPR/PPD, TN5250e, and TN3270e. For AS/400 connectivity, generally TN5250e is used to connect 3812-1 printers while AnyNet is used for all IBM dot-matrix printers as well as page printers. SNA(APPC) can be used for connecting all AS/400 printers if there are no routers in the LAN. IPDS printers will be connected using PPR/PPD (an IBM proprietary TCP/IP protocol) in both the AS/400 and IBM mainframe environments. Other IBM mainframe printers (SCS/DSC types) are connected using TN3270e. Choose the protocol that best fits your needs.
Here are the steps you’ll take to set up the print server:
• Install the print server itself.
• Install the PrintControl utility.
• Configure the print server for the host connection.
• Configure the print server for the attached twinax or 3270-coax printer.
• Configure the AS/400 or IBM mainframe.
2.2 The Complete Package
When you receive the Ethernet to Twinax/Coax Print Server, check the packaging for water or physical damage, and notify the carrier immediately if any damage is evident. If not, keep the original packaging in case the print server needs to be moved or shipped. At the time of this writing, the following items are included in the package:
12
ETHERNET TO TWINAX/COAX PRINT SERVER
• (1) Print Server
• (1) CD (manual and software)
• (1) Twinax “V” cable (DB9 female to two twinax female)
• (1) Power supply
• (1) Power cord
2.3 The Print Server’s External Components
The Ethernet to Twinax/Coax Print Server has labels on both the top and bottom panels that indicate what the switch and each of the connectors and LEDs are. Please refer to these labels as you read the rest of this section.
2.3.1 LED I
NDICATORS
The Ethernet to Twinax/Coax Print Server has these LEDs on its left side and top panel:
Link: This green LED on the side of the print server indicates that the print server has established communication with an Ethernet hub and has verified link integrity.
Activity: This green LED on the side of the print server indicates that the print server is detecting signals on the network.
Power: This green LED on the top cover will light to indicate that the print server has successfully completed its internal self-tests and is ready to operate. If this light blinks slowly, the print server is not in operating mode (for example, during flash upgrade). A rapidly blinking light indicates a problem with the print server (for example, a failed self-test, faulty power supply, etc.).
Line Sync: This green LED on the top cover will light to indicate that the print server is connected to a twinax or 3270-coax printer and that the printer is turned on. During the power-up cycle, this LED will blink while the print server is connecting to the twinax or 3270-coax printer. For twinax printers, it will blink about two times per second. For 3270-coax printers, it will blink about four times per second. The default setting for the print server’s printer connection is twinax.
LAN Data: This green LED on the top cover will light when network data is received by the print server. This light may seem to be blinking at times since the print server receives many small data packets in the form of status requests or other inquiries by servers in the network.
13
CHAPTER 2: Introduction
Printer Activity: This green LED on the top cover will light while data is being sent to the twinax or 3270-coax printer. It will go dark when all data has been transmitted to the attached printer.
Printer Error: This green LED on the top cover will go dark during print-server operation. If there is an error condition, this LED will either light steadily or blink.
Mode: These two orange LEDs on the top cover are associated with the mode button and indicate which print-server function is currently active. When both of these orange LEDs are dark, the print server is in normal operating mode. Other functions include the power-up self-test, EBCDIC self-test, ASCII self-test, diagnostic dump mode, and restoring factory defaults.
2.3.2 C
ONNECTORS ANDSWITCH
Power: This connector is used for the 5-VDC, 2.5A power supply shipped with the
print server.
10/100BASE-T: This connector is used for attaching a 10BASE-T or 100BASE-T cable.
10/100: This switch should only be used when the autosensing 10/100BASE-T connector does not seem to function properly. The possible settings are shown below. The DOWN position is achieved by moving the switches toward the bottom of the print server.
Setting Switch 1 Switch 2
Auto-sensing (default) UP UP 100BASE-T Only DOWN UP 10BASE-T Only DOWN DOWN
5250 Twinax: This DB9 port is where the twinax V-cable is attached to the print server. The twinax line is then attached to the V-cable and the twinax printer. The V-cable is self-terminating (so only one connector is attached, leaving the other open).
3270 Coax: This BNC port is where the 3270-coax cable is attached to the print server.
Diagnostic Port: This DB25 connector is where a standard PC type parallel printer cable is attached for printing diagnostic reports.
14
ETHERNET TO TWINAX/COAX PRINT SERVER
2.4 Network Connectivity
The Ethernet to Twinax/Coax Print Server acts as a node in the local area network with its own unique network address. It receives data from across the network in the form of packets. If the data is from an IBM AS/400 or mainframe, the data package is passed on to the twinax or 3270-coax printer in its native format. That format may be SCS, IPDS, or SCS/DSC (LU1/LU3). If the data is from an ASCII host (UNIX, Windows, DOS, OS/2), the ASCII data will be converted to EBCDIC and sent to the twinax or 3270-coax printers. (Note that only SCS or SCS/DSC printers can support this function.)
2.5 Multiprotocol LAN Printing
When printing from ASCII hosts (PC, UNIX), the print server supports the following protocols:
TCP/IP (LPR/LPD): Used by UNIX, NetWare, Windows 95/98/2000,
Windows Me, Windows NT
®
, Windows XP, OS/2.
IPX/SPX: Used by NetWare.
NOTE
Due to the limited ability of IBM SCS printers, only non-rasterized text can be printed from PCs, LANs, Windows, UNIX, and other non IBM EBCDIC hosts.
2.6 Multi-Host Printing
The print server can support printing from several different types of hosts at the same time. This expands the capability of a printer attached to a print server, yet still provides the benefits of a dedicated host-printer relationship.
For example, in LAN printing, you may have UNIX systems, PCs, and other ASCII-type hosts, all using various combinations of NetWare and TCP/IP. All systems can send their printed data to a single print server.
The print server is also capable of supporting up to 10 different IBM mainframe or AS/400 hosts for the twinax or 3270-coax attached printer (when using TN5250e or TN3270e), greatly expanding the number of hosts that can utilize the printer attached to the print server. The twinax or 3270-coax printer settings must be configured the same way on each IBM host.
15
CHAPTER 2: Introduction
2.7 Multi-Protocol IBM Host-to-LAN Printing
2.7.1 AS/400 TOLAN P
RINTING
When printing from an AS/400 host, the Ethernet to Twinax/Coax Print Server supports several protocols. Which protocol to use depends on the type of printer being attached to the print server and whether the print server and printer are located within a local area network or remotely located (using routers).
For SCS data streams:
SNA: Use with all local SCS printers when there is not a router between the
AS/400 and the print server. When using this protocol, the AS/400 will automatically configure the printer device. Very little configuration is required at the print server.
AnyNet: Use with all remote SCS printers when routers are used to connect the
AS/400 and a remote LAN. When using this TCP/IP protocol, the AS/400 will also automatically configure the printer device. Very little configuration is required at the print server, but much more extensive configuration is required at the AS/400 to set up the first AnyNet device. After that, adding new AnyNet devices is much easier.
TN5250e: Use with 3812-1 page printers. This TCP/IP protocol is self-
configuring on the AS/400. Be aware that the AS/400 will only configure a 3812-1 printer device, so this protocol is limited to supporting only 3812-1 page printers. Very little configuration of the print server is required, and none at the host.
For IPDS data streams:
PPR/PPD: Use this IBM proprietary TCP/IP protocol with all IPDS printers,
whether located locally or remotely. Configuration of the print server is minimal, but extensive configuration is required at the AS/400. PSF/400 is required on the AS/400.
AnyNet: May be used when PSF/400 is not installed on the AS/400.
2.7.2 IBM M
AINFRAMEPRINTING
When printing from an IBM mainframe, the Ethernet to Twinax/Coax Print Server supports two TCP/IP printing protocols. Which protocol to use depends on the type of the 3270-coax printer that is being attached to the print server.
16
ETHERNET TO TWINAX/COAX PRINT SERVER
For SCS/DSC data streams: Use the TN3270e TCP/IP protocol for 3287 type SCS/DSC printers. Configuration of the print server is very simple. However, the
mainframe will require much more extensive configuration, including the installation of a Telnet server. A brief overview is included later in this manual, but because there are many varieties of mainframe telnet servers (both internal and external), configuration of the mainframe must be performed by either your in­house systems administrator or an IBM representative.
For IPDS data streams: Use the IBM proprietary PPR/PPD TCP/IP protocol with all IPDS printers. Configuration of the print server is minimal, but extensive configuration is required at the mainframe. Only certain mainframe operating systems support printing of IPDS data over TCP/IP. A brief overview of the process is included later in this user’s guide. Configuration of the mainframe must be performed by either the end-user’s in-house knowledgeable system administrator or an IBM representative.
Table 2-1 shows the association of the various connectivity protocols and supported data streams.
17
CHAPTER 2: Introduction
Table 2-1. Protocols to use for IBM mainframe printing.
Host Data Type In Network Protocols Data to Printer Printer Type
AS/400 SCS SNA, AnyNet, TN5250e* SCS Twinax
AS/400 IPDS TCP/IP (PPR/PPD, IPDS Twinax
AnyNet)
DOS ASCII (Epson/ IPX/SPX, TCP/IP SCS Twinax
PPDS)
Windows ASCII (Generic) IPX/SPX, TCP/IP SCS Twinax
(DirectPort)
UNIX, NT, ASCII (Epson/ TCP/IP (LPR/LPD) SCS Twinax other PPDS)
Mainframe SCS/DSC TCP/IP (TN3270e) SCS/DSC 3270-Coax
Mainframe IPDS TCP/IP (PPR/PPD) IPDS 3270-Coax
DOS ASCII IPX/SPX, TCP/IP SCS 3270-Coax
(Epson/PPDS)
Windows** ASCII (Generic) IPX/SPX, TCP/IP SCS 3270-Coax
(DirectPort)
UNIX, NT, ASCII TCP/IP (Epson/PPDS) SCS (LPR/LPD) 3270-Coax
other
* When you use TN5250e for connection to the AS/400, only a 3812-1 page printer may be
attached.
** Only the “generic” print driver that sends out text is supported. Set the spool file’s data stream
to “raw.”
18
ETHERNET TO TWINAX/COAX PRINT SERVER
3. Installation
3.1 Hardware Installation
1. Perform a self-test of the printer you want to attach (check the printer’s manual). Then power OFF the printer.
2. Attach the LAN cable to the Ethernet to Twinax/Coax Print Server’s 10/100BASE-T connector. The print server will automatically sense which Ethernet data rate to use. If the Link LED does not come on, you will need to set the print server’s 10/100 switch as follows:
Setting Switch 1 Switch 2 Auto-sensing (default) UP UP 100BASE-T only DOWN UP 10BASE-T only DOWN DOWN
NOTE
Do not change this setting while the print server is powered ON.
3. Attach an appropriate printer cable (not included) to the print server and power ON the printer.
4. Connect the power supply to the print server.
5. The print server will generate its own self-test and send a report of the results to the printer. If the self-test report does not print, make sure that the printer’s start button has been pressed. After the self-test page prints, review it for more information regarding print-server settings. By default, a print-server self-test page will print on the attached printer. This default setting can be overridden through port-specific selections made through the included print­control utility.
This completes the hardware installation. Proceed to install the included print­control software in preparation for configuring the print server for the LAN protocols of your choice. See Section 3.2.
19
CHAPTER 3: Installation
3.2 Print-Control Software Installation
The print-control software is a utility that runs under Windows 3.1/95/98/2000, Windows NT, Windows XP, or Windows Me. Before you begin to install it, make sure that the PC you want to put it on is attached to the same LAN segment as the Ethernet to Twinax/Coax Print Server and has at least 2 MB of disk space available. Also, the PC will have to be able to communicate with other network devices across TCP/IP or IPX/SPX.
1. Insert the CD-ROM containing the print-control utility into your PC’s CD-ROM drive.
2A. If you are installing the utility on a Windows 3.x or Windows NT 3.x PC: Click File
in the Program Manager, then select Run.
2B. If you are installing the utility on a Windows 95/98/2000, Windows XP, or Windows
NT 4.x PC: If the autorun feature has been disabled, click Start, then select
Run. Otherwise, the PC will automatically load the Black Box startup menu
(skip to step 4).
3. Type d:\autorun, then press Enter. (If “d:” isn’t the letter of the drive that the software CD-ROM or floppy is in, use the appropriate drive letter instead.)
4. Click the button on the menu and follow the instructions that appear on your computer screen during the installation process.
This installation creates a separate group for the print-control utility. The icon for the print-control utility and a help file will appear in the group.
3.3 Using the Print-Control Software
The print-control utility is used to configure, monitor, and reset the Ethernet to Twinax/Coax Print Server. Additional functions include downloading firmware upgrades to the print server and restoring its factory defaults. By default, the print­control utility software uses the TCP/IP protocol to communicate with the print server on the network. Novell’s IPX/SPX can also be enabled through the Protocol Menu. The PC running the print-control utility has to support at least one of these protocols (TCP/IP or IPX/SPX) in order for the utility to function.
20
ETHERNET TO TWINAX/COAX PRINT SERVER
3.4 Proceeding with the System Configuration
Once you’ve finished installing the Ethernet to Twinax/Coax Print Server and its print-control utility, configure your print server, host computer(s), operating system(s), and/or printer for the appropriate protocols as described in Chapters 4, 5, and 6. Then configure the print server’s twinax or coax characteristics as described in Chapter 7. (If the attached printer is an IPDS printer, you will also need to follow the procedures in Chapter 8.)
21
CHAPTER 4: TCP/IP Printing
4. TCP/IP Printing
Refer to this chapter for instructions on setting up TCP/IP connectivity protocols to both the IBM mainframe and AS/400.
If you have not already installed the print-control utility, please go back to Section
3.2 and do so now. Then proceed configuring the print server and the hosts that you will be printing from. Chapter 4 consists of the following sections:
Configuring the Print Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Section 4.1
Configuring the IBM mainframe for TN3270e . . . . . . . . . . . . . . . . . . Section 4.2
Configuring for IPDS Printing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Section 4.3
Configuring OS/400 for TN5250e . . . . . . . . . . . . . . . . . . . . . . . . . . . . Section 4.4
Configuring OS/400 for AnyNet. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Section 4.5
Configuring Windows NT V3.x . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Section 4.6
Configuring Windows NT V4.x . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Section 4.7
TCP/IP DirectPort Printing for Windows 95/98 . . . . . . . . . . . . . . . . . Section 4.8
NOTE
LPR/LPD is not supported when sending unconverted print jobs (in EBCDIC format) from an IBM mainframe or AS/400. LPR/LPD is, however, supported when printing ASCII jobs from any host system (including UNIX, Windows 95/98/NT/2000, Novell, OS/2, etc.) when the printer attached to the print server is a SCS type printer.
After you have completed the configuration of these protocols, go to Chapter 7 to complete the print server’s setup. If the attached printer is an IPDS printer, you will also need to go to Chapter 8.
22
ETHERNET TO TWINAX/COAX PRINT SERVER
4.1 Configuring the Print Server
4.1.1 A
SSIGN
TCP/IP A
DDRESS
After starting the print-control utility, select the desired print server from the displayed list. The print servers are identified through their serial number and network address. Both of these are unique to the specific print server and can be found on the bottom of the print server as well as on the self-test print out.
Open the configuration dialog box by double clicking on the desired print server or by highlighting the desired print server and then pressing the Configure button displayed in the tool bar. Follow these simple steps to configure the print server for TCP/IP printing.
1. Select TCP/IP by clicking on the white box in front of that selection.
2. The column titled Object Information will display the available configuration parameters.
a. Enter the TCP/IP address of the print server.
b. If necessary, enter the IP address for the default router and the subnet
mask. If you intend to communicate remotely with the print server (for printing or configuration), the default router and subnet mask must be entered here.
3. Click on the Apply Changes button on the bottom of the configuration window.
4.1.2 V
ERIFYCORRECTINSTALLATION
From the command line (or DOS prompt) of a TCP/IP enabled host type:
Ping <TCP/IP address of print server>
If you receive a successful response to the ping command, you have a TCP/IP attached device. To ensure this device is the Black Box PrintServer, remove power from the PrintServer and again ping the same TCP/IP address. If the response is successful, you have a duplicated TCP/IP address and need to change the TCP/IP address of the Black Box PrintServer. If the response is negative, you can be certain the TCP/IP address of the Black Box PrintServer is correct. (Be certain to apply power to the Black Box PrintServer after pinging its TCP/IP address.)
23
CHAPTER 4: TCP/IP Printing
4.1.3 C
ONFIGURING APRINTSERVER ON AREMOTE
TCP/IP S
UBNET
The print-control utility can also change the configuration of a print server that is located on a remote TCP/IP subnet. The print server must initially be configured with an IP address from a PC running PrintControl that is located within the same TCP/IP subnet as the print server. After this step is completed, the print server may be moved to a remote location.
There are two ways to change the configuration of an print server that is located on a remote TCP/IP subnet. The first is to have the exact IP address of the print server.
The second is to scan the remote TCP/IP subnet where the print server is located. To do this, you will need to have the “subnet mask” and an IP address of any device on that subnet (the device does not have to be an print server). Obtain this information from your network manager. With these two pieces of addressing information, the PrintControl utility can scan the remote TCP/IP subnet and find all print servers on that subnet.
The following steps will guide you through selecting a remotely or locally attached print server:
1. From the menu bar in PrintControl, select the VIEW option.
2. Select the SCAN option.
• To scan for a specific print server located on a remote TCP/IP subnet:
a. Check the radio button to the left of the “Scan for a Single Print Server”
option.
b. Enter the IP address of the print server in the “IP Address” field. You
may view the last eight addresses entered in this field by clicking on the down arrow. If the desired IP address is listed, click on that entry.
c. Click OK.
• To scan a remote TCP/IP subnet for all print servers located on that subnet:
a. Check the radio button to the left of the “Scan a Remote Subnet”
option.
b. Enter the address of any device in the remote TCP/IP subnet in the “IP
Address” field. You may view the last eight addresses entered in this field by clicking on the down arrow. If the desired IP address is listed, click on that entry.
24
ETHERNET TO TWINAX/COAX PRINT SERVER
c. Enter the remote TCP/IP subnet mask in the “Remote Subnet Mask”
field. You may view the last eight subnet mask entries made in this field by clicking on the down arrow. If the desired subnet mask is listed, click on that entry.
d. Click OK.
• To scan for all print servers located on the local subnet:
a. Check the radio button to the left of the “Scan the local subnet” option.
b. Click OK.
3. Once you have made a selection of scanning the local subnet, a remote
TCP/IP subnet, or for a specific print server, pressing the Scan button on the button bar will refresh the listing of print server(s). From here, you can double click on the desired print server or clicking on the Configure button to view or change the highlighted print server’s configuration.
4.1.4 W
HERE TONOW
. . .
You are now ready to configure the host(s). From here go to the appropriate section for each host to be configured.
Configuring the Print Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Section 4.1
Configuring the IBM Mainframe for TN3270e . . . . . . . . . . . . . . . . Section 4.2
Configuring for IPDS Printing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Section 4.3
Configuring OS/400 for TN5250e . . . . . . . . . . . . . . . . . . . . . . . . . . Section 4.4
Configuring OS/400 for AnyNet . . . . . . . . . . . . . . . . . . . . . . . . . . . . Section 4.5
Configuring Windows NT V3.x . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Section 4.6
Configuring Windows NT V4.x . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Section 4.7
TCP/IP DirectPort Printing for Windows 95/98 . . . . . . . . . . . . . . . Section 4.8
4.2 Configuring the IBM Mainframe for TN3270e
The Ethernet to Twinax/Coax Print Server communicates to the IBM mainframe with TCP/IP using the TN3270e protocol. TN3270e is an extension of the Telnet display protocol. IBM has limited the types of printers that can be configured in
25
CHAPTER 4: TCP/IP Printing
TN3270e to type 3287. Connection to the IBM mainframe is accomplished through a TN3270e server. The TN3270e server can be either internal to the IBM mainframe or externally attached, such as a channel or LAN-attached gateway. The print server then accepts SCS/DSC (LU1/LU3) data from the IBM mainframe application through TCP/IP (TN3270e). Printer messages are returned through the same TN3270e link.
In general, configuring the IBM mainframe to print to the Ethernet to Twinax/Coax Print Server is the same as configuring for a new TN3270e printer. The VTAM TCP/IP profile is modified to include the Telnet device, the printer group name, the IP address group, and the printer group. JES is then modified to include the Ethernet to Twinax/Coax Print Server destination id and description. Lastly the mainframe’s print application, such as JES23X or VPS, is configured for the remote printer.
Refer to the appropriate IBM mainframe and TN3270e server documentation for configuration instructions.
Once you have assigned a TCP/IP address to the Ethernet to Twinax/Coax Print Server and verified the address, go to Section 7.2 to continue the configuration of the print server.
4.3 Configuring for IPDS Printing
Once you have assigned a TCP/IP address and verified the address (see Section
4.1.1), go to Chapter 8 to continue the configuration of the AS/400 or IBM
mainframe system.
4.4 Configuring OS/400 for TN5250e
TN5250e is an extension of the Telnet display protocol used in IBM AS/400 systems. IBM has limited printer support in TN5250e to only one type of printer, a 3812-1 SCS Page Printer. Use this protocol only if you are attaching a 3812-1 printer.
4.4.1 C
ONFIGURING THE
AS/400
To configure your AS/400 to support TN5250e printing, the AS/400 must meet the following software requirements:
• Be running OS/400 V3R2 or newer,
26
ETHERNET TO TWINAX/COAX PRINT SERVER
• Have the most recent version of Client Access installed on the AS/400 (Client Access for Windows 95/NT V3R1M3 or newer, or Client Access Enhanced for Windows 3.1 V3R1), and
• Have the most recent version of the Telnet server installed.
The following is a list of the necessary PTFs that support TN5250e. This list is based upon the IBM APAR# II11226 dated January 4, 1999. Newer PTFs may be available—check with IBM for an up-to-date listing.
Version Product PTF Required
Version 4 Release 4 5769TC SF60281
5769999 MF23060 5769SS1 SF61082
Version 4 Release 3 Mod 0: SF53489
5769TC1 SF55398 5769999 MF21682 5769SS1 SF51877
Version 4 Release 2 Mod 0: SF53486
5769TC1 SF47715 & SF49539 5769999 MF19784 5769SS1 SF49336, SF47792,
SF47400, & SF48804
Version 4 Release 1 Mod 0: SF53485
5769TC1 SF49568 & SF47714 5769999 MF20046 5769SS1 SF49335
Version 3 Release 7 Mod 0: SF53483
5716TC1 SF47713 & SF49569 5716999 MF19931 5716SS1 SF47406 & SF49317
Version 3 Release 2 Mod 0: SF53481
5763TC1 SF50008 & SF47712 5763999 MF19563 5763SS1 SF49121 & SF50345
To determine what version of OS/400 is running on your AS/400, enter (at the AS/400 command line) either the DSPLICKEY or the GO LICPGM command, then press F13, and take option 10.
27
CHAPTER 4: TCP/IP Printing
To determine if your AS/400 has these PTFs installed and actively running, use the following steps:
1. At the AS/400 command prompt, type
DSPPTF
2. Press F4 to provide the list.
3. Type in the product number and press <Enter>.
4. Scroll down to select the desired PTF. The PTF status should be temporarily applied, permanently applied, or superceded.
In addition, the AS/400’s system administrator will need to have done the following:
• Make certain that the AS/400 can create virtual devices and that there is a sufficient number of devices available to be created. This is done using the AS/400 command:
CHGSYSVAL SYSVAL(QAUTOVRT) + VALUE(?)
The “?” is the maximum number of user-created virtual devices that can be created.
• If the OS/400 version is earlier than V4R2, the Telnet server will need to be started using the AS/400 command:
STRTCPSVR SERVER(*TELNET)
V4R2 and newer versions will automatically start the Telnet server.
After these requirements are met, the AS/400 will automatically configure TN5250e printer devices as 3812 printers.
4.4.2 C
ONFIGURING THEPRINTSERVER FOR
TN5250EP
RINTING
1. After starting the print-control utility, select the desired print server from the displayed list. (Only those print servers located on the same LAN segment as the PC where the print-control utility is running are seen in the list.) Print servers are identified through their serial number and network address. Both of these are unique to the specific print server and can be found on the bottom of the print server as well as on the self-test print out.
28
ETHERNET TO TWINAX/COAX PRINT SERVER
2. Open the configuration dialog box by double clicking on the desired print server or by highlighting the desired print server and then pressing the Configure button displayed in the tool bar.
3. If the print server already has an IP address, proceed directly with step 4. Otherwise, follow these instructions:
a. Select the TCP/IP by checking the white box in front of that selection.
The column titled “Object Information” will display the available configuration parameters.
b. Enter the print server IP address.
c. If necessary, enter the IP address for the default router and sub-net mask.
You may need to get this from your system administrator.
4. Select TN5250e by checking the white box in front of that selection in the left column of the print-control configuration screen. The column titled “Object Information” will display the available configuration parameters.
5. The print server supports up to 10 IBM hosts. Enter the host IP address (see your system administrator for this address). A host may not be entered more than one time.
6. In the Type field, select the type of IBM host by clicking on the drop-down arrow and highlighting the type of host.
7. Click on the Printer button to display the Printer Device Names screen. The print server supports an individual TN5250e printer session for each attached printer. Click on the box for each printer that is attached and enter a printer name (maximum of 8 characters).
When the print server is reset, the AS/400 will automatically configure a printer device for each attached printer that has been selected and named here.
The printer must be in the “ready” mode for this auto-configuration to occur.
If the printer name is left blank, the host AS/400 will still automatically create a 3812 device but will give the printer the name of QPADEVnnnn, with nnnn being a 4-digit number. However, each time the print server connects to the host, the nnnn number for the printer may be different. This may cause problems where a specific printer name is used in specifying the location of printed output. Black Box does not recommend that you let the AS/400 create the printer name.
29
CHAPTER 4: TCP/IP Printing
8. The print server will automatically restart a TN5250e printer session on the AS/400 whenever any of the attached printers are powered on. However, at times it may be advantageous to restart a TN5250e printer session while leaving other protocols uninterrupted. This can be accomplished by clicking on the Restart Now button.
9. To ensure continued communication with the AS/400 host, the print server can be configured to periodically contact the host and attempt to re-establish TN5250e sessions if required. Clicking on the Options button sets these
options.
a. The automatic restarting of a TN5250e session when a printer is powered
on is checked by default and cannot be changed. The print server will always restart TN5250 sessions when an attached printer is powered on.
b. You may select to have the print server restart sessions every five minutes
that have been terminated by the AS/400 by checking the box to the left of this option.
c. You may also set the print server to restart sessions only upon receiving a
TCP/IP PING command by checking the box to the left of this option. The PING can come from any other device with an IP address or from a specific AS/400 by entering the desired host’s IP address in the address field. Leave this field as 0.0.0.0 if you do not want to select a specific host.
d. The print server reports the success or failure of an attempt to
communicate with the AS/400 by printing a brief connection status message on each attached printer.
For a description of the connection status message, see Section 9.5.3. Printing of these status messages can be disabled in order to save paper or to preserve alignment of continuous forms. Checking the box to the left of this option will turn this option off.
e. After setting these options, click on the Return button.
10. Set up any other protocols desired, then click on the Apply Changes button,
and exit the PrintControl utility.
Loading...
+ 109 hidden pages