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

PC435A

Ethernet to Twinax/Coax Print Server

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.

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.

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.

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.

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.

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

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

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

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

ETHERNET TO TWINAX/COAX PRINT SERVER

1. Specifications

Compliance: FCC: Part 15, Class A;

: 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)

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:

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.

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.

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.

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.

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 inhouse 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.

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.”

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 printcontrol utility.

This completes the hardware installation. Proceed to install the included printcontrol software in preparation for configuring the print server for the LAN protocols of your choice. See Section 3.2.

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 printcontrol 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.

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.)

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.

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.)

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.

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

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,

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.

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.

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.

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.

ETHERNET TO TWINAX/COAX PRINT SERVER

4.5 Configuring OS/400 for AnyNet

AnyNet is an IBM gateway technology that allows any application to run over any networking protocol. Black Box’s implementation of AnyNet allows printing of SNA (APPC) data over TCP/IP, giving users the security and functionality of SNA (APPC) as well as the routability and ease-of-use of the popular TCP/IP protocol.

Use this protocol for all SCS twinax printers. This protocol may also be used with IPDS printers when PSF/400 is not installed on the AS/400.

Proceed with the following steps to configure the print server and your AS/400 for AnyNet printing:

AnyNet Configuration Worksheet. . . . . . . . . . . . . . . . . . . . . . Section 4.5.1

Configuring the AS/400 for AnyNet. . . . . . . . . . . . . . . . . . . . Section 4.5.2

Configuring the Print Server for AnyNet Printing. . . . . . . . . Section 4.5.3

4.5.1 ANYNETC

ONFIGURATIONWORKSHEET

As you configure the AS/400 and later the print server, you will be asked to supply various names and parameters. To make the process easier, you should retrieve or decide on the information now. Before you proceed, you should enter the requested names and parameters in the following worksheet:

1. Host Network ID: _________________________

The AS/400’s network ID can be retrieved from the network attributes listing: On the AS/400 command line type DSPNETA (Display Network Attributes). Press <Enter>. The Host Network ID is listed as the Local network ID.

2. Host Control Point Name: ________________________

The AS/400’s control point name can be retrieved from the network attributes listing. On the AS/400 command line type, DSPNETA (Display Network Attributes) and press <Enter>. The Host Control Point Name is listed as the Local control point name. While in the DSPNETA screen, page down to the third page and verify that the field Allow AnyNet Support is set to *YES.

3. Print Server Name: ______________________

Choose a unique name to assign to the print server later. This name must comply with the following requirements:

CHAPTER 4: TCP/IP Printing

A. This name must be unique to the AS/400.

B. The name must be no longer than 8 characters.

C. The name must start with an alpha character (A–Z).

D. The name must consist of the characters A–Z, a–z, or 0–9. Spaces,

underscores, slashes, etc. are not accepted.

E. The first four characters should uniquely identify the device, since the

print server will automatically create printer devices on your AS/400 using the first four characters of the name you assigned to the print server followed by PRTXX.

4. AS/400 TCP/IP Address: ______________________

The AS/400’s TCP/IP address can be retrieved by typing cfgtcp at the AS/400 command line and pressing <Enter>. Then select option 1, Work with

TCP/IP interfaces. The correct address for the AS400 will have a line type of *ELAN.

5. Print Server TCP/IP Address: ___________________

Choose a unique IP address to assign to the print server. At the AS400 command line, type cfgtcp and press <Enter>. Choose option 10, Work with

TCP/IP host table entries. Verify Host Name is in the following format:

Black BoxPrintServerName.HostNetworkID.SNA.IBM.COM

For example:

IO5450PS.APPN.SNA.IBM.COM

6. AnyNet Controller Name: __________________

If you already have an AnyNet Controller defined on your AS/400 and plan to use the print server under this controller, enter the AnyNet controller name in the worksheet space above. To check for the name of the AnyNet controller, type WRKCFGSTS at the command line then press F4. The type is *CTL and the Configuration description should be *APPC. Press <Enter> twice, and you’ll see all the APPC controllers on your system. If you are unsure of the name of the AnyNet controller, you’ll need to display each controller. To display a controller, type an “8” in front of each controller and press <Enter>. Then enter a “5” to display the controller and find the one with the link type of *Anynw.

ETHERNET TO TWINAX/COAX PRINT SERVER

If there is not an AnyNet controller already configured on the AS/400, you will have to create one.

If you are not following Black Box’s recommended method of using only one AnyNet controller for all your AnyNet devices (including print servers), the AnyNet controller name and the AnyNet remote control name must be different from the print server Name. If your AS/400 is using more than 254 AnyNet devices, you should configure one AnyNet controller for every print server. In this case, the name of the AnyNet controller and the AnyNet remote control point must be the same as the print server name. The AnyNet controller name can be up to 10 characters long.

7. AnyNet Remote Control Point Name: _____________________

If you already have an AnyNet Controller defined on your AS/400 and plan to use the print server under this controller, do the following:

On the AS/400 command line, type WRKCTLD and press <Enter>.

Locate the AnyNet Controller, enter the value “5” in front of that controller, and press <Enter>.

Locate the Remote Control Point and enter the value in the worksheet space above.

Otherwise, if you are not following Black Box’s recommended method of using only one AnyNet controller for all your AnyNet devices (including print servers) and you are creating a new AnyNet controller, the AnyNet Remote Control Point Name should be different from the print server name.

If your AS/400 supports more than 254 AnyNet devices, you should configure one AnyNet controller for every print server. In this case, the AnyNet Remote Control Point Name should be the same as the print server name.

4.5.2 C

ONFIGURING THE

AS/400

FORANYNET

Changing the AS/400’s Network Attribute

To allow AnyNet communication from your AS/400, the Allow AnyNet Support option must be set to *Yes. You may want to check the current setting first by executing the DSPNETA command and then scrolling to the last page of the available parameters. If the value is set to *No, return to the command prompt (CMD3) and enter the following:

CHGNETA ALWANYNET (*YES)

CHAPTER 4: TCP/IP Printing

Adding the Print Server to the AS/400 TCP/IP Host Table

1. On your AS/400’s command line, type cfgtcp to enter the configure TCP/IP menu.

2. Select 10 Work with TCP/IP host table entries. Scroll down and make sure there are no duplicate print server addresses.

3. Place a 1 in front of the blank line on top of the list to add another TCP/IP device. Press <Enter>.

4. Enter the print server TCP/IP address in the Internet address field.

5. Under Host names: Name..., enter the following:

print server Name.Host Network ID.SNA.IBM.COM

(for example: IO5450PS.APPN.SNA.IBM.COM)

6. If you wish, you may enter an additional description for the print server in the Text description field.

7. Press <Enter>.

Creating an AnyNet Controller

Black Box’s recommended method for configuring the print server is to have only one AnyNet APPC controller on the AS/400. However, this method is limited to attaching a maximum of 254 AnyNet devices (including the print server). If you are using more than 254 AnyNet devices, you should skip to the section below. Otherwise, proceed with these instructions:

1. If you already have an AnyNet Controller defined on your AS/400, skip to step 2. Otherwise, type the following on the AS/400 command prompt:

CRTCTLAPPC CTLD (AnyNet Controller Name) LINKTYPE (*ANYNW)

RMTCPNAME (AnyNet Remote Control Point Name) RMTNETID (*NETATR)

Press <Enter>.

2. Vary On the AnyNet controller by typing the following on the AS/400 command prompt:

WRKCFGSTS *CTL AnyNet Controller Name

ETHERNET TO TWINAX/COAX PRINT SERVER

Press <Enter>.

3. Type a 1 in front of the APPC controller and press <Enter>.

Alternate Method: Creating One AnyNet Controller for Each Print Server

It is possible to create an individual AnyNet controller for every print server installed. However, this approach can be confusing since any programmable AnyNet APPC device (and the printers attached to the print server will fall into this category) will randomly configure under the different APPC controllers. Although this does not affect operation, it does make it more difficult to locate and administer the various AnyNet APPC devices.

To create an AnyNet controller specifically for the print server, type the following on the AS/400 command prompt:

CRTCTLAPPC CTLD (print server Name) LINKTYPE (*ANYNW) RMTCPNAME (print server Name) RMTNETID (*NETATR)

Press <Enter>.

Changing the AS/400’s APPN Remote Configuration List

When using Black Box’s recommended method of just one AnyNet APPC controller for all AnyNet APPC devices, each print server needs to be added to the AS/400’s APPN remote configuration list. To accomplish this follow these steps:

1. On the AS/400 command prompt, type:

CHGCFGL *APPNRMT

Press <Enter>.

2. Scroll to the bottom of the displayed list and enter the requested parameters. Refer to the worksheet for the needed information. The other parameters are optional. Press <Enter> when done.

Remote Location: Print Server Name

Remote Network ID: Host Network ID

Local Location: Host Control Point Name

Remote Control Point: AnyNet Remote Control Point Name

Control Point Net ID: Host Network ID

CHAPTER 4: TCP/IP Printing

4.5.3 C

ONFIGURING THEPRINTSERVER FORANYNETPRINTING

1. After starting the print-control utility, select the desired print server from the displayed 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.

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 TCP/IP by clicking on 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 the subnet

mask. You may need to get this from the system administrator.

4. Select AS/400 AnyNet by clicking on the white box in front of that selection in the left column of the print-control configuration screen.

5. The column titled “Object Information” will display the available configuration parameters.

a. In the field titled “AS/400 IP Address,” enter the AS/400’s TCP/IP

address. Make sure to use the format specified in the field (for example, XXX.XXX.XXX.XXX).

b. Enter the Host Network ID.

c. Enter the Host Control Point Name.

d. In the field titled “Interface Control Point Name,” enter the print server

name.

6. If you want to configure additional protocols, refer to the respective section. If your configuration of the print server is complete, click on the Apply Changes button on the bottom of the configuration window and reset the print server. Then Exit the PrintControl utility.

ETHERNET TO TWINAX/COAX PRINT SERVER

7. The print server will now automatically create the following devices on your AS/400:

• A 5494 Controller with the first five characters of the “Interface Control

Point” name followed by the identifier RMT.

• A printer device for every printer that was attached to the print server at the time the new configuration was sent to the print server or when the print server was last reset. Names for the printer devices are actually given by the AS/400 system and follow this format:

ABCDPRTXX

where

ABCD are the first four characters of the “Interface Control

Point”;

PRT is a fixed identifier for printers;

XX identifies the printer(s) that was(were) actually attached

to the print server at the time the SNA (APPC) configuration was applied to the print server or at the time the print server was last reset.

NOTE

If the twinax attached printer is an IPDS printer, you will need to change one parameter on the AS/400. Using the WRKDEVD command, enter the name of the printer device just created. Then change “Advanced Function Printing” value to *YES.

4.6 Configuring Windows NT V3.x

Make sure your Windows NT workstation has the TCP/IP protocol and the TCP/IP Printing service active. If you are unsure do the following:

1. Go to the workstation’s Main group and double-click on the Control Panel icon.

2. In the Control Panel, double-click on the Network icon.

CHAPTER 4: TCP/IP Printing

3. Review the Installed Network Software list.

If the TCP/IP protocol and Microsoft TCP/IP Printing service are not found, you must add them before continuing with the instructions below. Consult your Microsoft documentation for more information.

Follow the procedures below to create printers for the print server on a Windows NT workstation. If there is more than one printer attached to the print server, perform this procedure once for each attached printer.

1. Go to the Main program group and open the Print Manager.

2. Go to the Print Manager’s Printer menu and choose Create Printer….

3. In the Create Printer’s Printer Name dialog box, enter a name for the printer.

4. Use the Driver pull-down list to choose a printer driver that matches the type of printer that you are creating on the workstation.

5. In the Description text box, enter a description that helps you remember the printer.

6. In the Print to: pull-down list, go to the bottom of the list and choose Other….

7. In the Print Destination dialog box’s Available Print Monitors list, click on LPR Port and choose OK.

8. In the Name or Address of host providing lpd: text box, enter the IP address you assigned to the print server (see Section 4.1.1).

9. In the Name of printer on that machine text box, enter the physical or logical

port of the print server that the target printer is attached to (that is, LPT1, TCP1).

NOTE

Selecting one of the TCP/IP logical ports will give you added configuration options, such as turning banner (header and trailer) pages off and suppressing blank pages when printing to an HP LaserJet printer.

10. Choose OK. The printer attached to the print server is now available. Simply

select it from your application as you would any other printer.

11. (Optional) Go to the Print Manager’s Default pull-down list and select the new printer as the workstation’s default printer.

ETHERNET TO TWINAX/COAX PRINT SERVER

4.7 Configuring Windows NT V4.x

Make sure your Windows NT workstation has the TCP/IP protocol and the TCP/IP Printing service active. If you are unsure do the following:

1. Click on Start, then select Settings, and lastly Control Panel.

2. Double-click on the Network icon and review the lists under the Protocol and Services tabs.

If the TCP/IP protocol and Microsoft TCP/IP Printing service are not found, you must add them before continuing with the instructions below. Consult your Microsoft documentation for more information.

1. From the Windows NT desktop, click on Start.

2. Select Settings, then open the Printer folder.

3. Double click on the Add Printer icon.

4. Choose My Computer.

5. Select Add Port.

6. From the Available Printer Ports list, double-click on LPR Port.

7. In the Name or address of server providing lpd: field, enter the IP address

you assigned to the print server (see Section 4.1.1).

8. In the Name of printer or print queue on that server: field, enter the physical

or logical port of the print server that the target printer is attached to (that is, LPT1, TCP1)

NOTE

Selecting the TPC1 logical port will give you added configuration options, such as turning banner (header and trailer) pages off and suppressing blank pages when printing to an HP LaserJet printer.

9. Click OK and Close the Printer Ports screen.

10. From the Add Printer Wizard screen, select the LPR port you just added and

press Next.

CHAPTER 4: TCP/IP Printing

11. Complete the remaining requests from the Windows NT Add Printer Wizard. The printer attached to the print server is now available. Simply select it from your application as you would any other printer.

4.8 TCP/IP DirectPort Printing for Windows 95/98

Print servers can be accessed directly from a PC running Windows 95/98 with TCP/IP by installing the TCP/IP DirectPort client software on the PC. Any number of PCs can be easily configured to print directly to a SCS or SCS/DSC printer connected through an print server.

SCS twinax and SCS/DSC coax printers can only accept text characters (no graphics or rasterized data). Therefore the “generic” windows print driver must be selected. Also the spool settings must be set to “raw” data.

4.8.1 TCP/IP D

IRECTPORTINSTALLATION

To install the TCP/IP DirectPort print driver for Windows 95/98, follow these simple steps:

1. Insert the CD or floppy containing the TCP/IP DirectPort utility in the PC’s CD-ROM or floppy drive.

2. If installing from a CD and the autorun feature is active, the CD will automatically load the Black Box Startup Menu. If the autorun feature has been disabled, click Start, select Run, type d:\autorun (d: represents the drive letter for your CD-ROM drive), then press Enter.

If installing from a floppy drive, click Start, select Run, type a:\setup.exe (a: represents the drive letter of your floppy drive), then press Enter.

3. Follow the instructions that appear on your computer screen during the

installation process. During this process, you will be given the opportunity to either accept the suggested TCP/IP DirectPort peer-to-peer printer port name (IPPort1) or enter a name of your choice. Remember this name, as you will need it to complete the configuration process.

4.8.2 S

ELECTINGDIRECTPORTPRINTING

To access a printer attached to a print server using the TCP/IP DirectPort print driver, you may either add a new printer to your Windows 95/98 system, or reconfigure an existing printer to use the TCP/IP DirectPort print driver.

ETHERNET TO TWINAX/COAX PRINT SERVER

To add a new printer, follow these steps:

1. Click on Start, select Settings, and then go to Printers.

2. Click on the Add Printer Wizard icon. Follow the normal Windows process to add a local printer. Select generic for the type of printer attached to the print server.

3. When the screen appears giving you a listing of the available ports, select IPPort1 Black Box TCP/IP DirectPort (or the port name you choose during the DirectPort installation process).

4. Click on the Configure Port… button.

5. On the Port Configuration screen, enter the TCP/IP address of the print server in the IP address field.

6. Specify LPT1 as the physical port that the printer is attached to on the print server. Verify that LPT1 appears in the Select Device Port… field. If not, click on the Select Device Port button and select LPT1.

7. Make any other desired changes to port configuration. Then click OK.

8. Continue with the remainder of the Add Printer Wizard steps to complete the process.

4.8.3 R

EMOVINGDIRECTPORT FROMWINDOWS

95/98

To remove the DirectPort print driver from your Windows 95/98 system, use the standard Windows Add/Remove Programs option from within the control panel.

Do not attempt to delete the folder that the DirectPort installation program creates. Doing so will cause the Windows Add/Remove Programs function to fail. In addition, you will not be able to reinstall the DirectPort print driver. If the DirectPort folder has been deleted, you must also delete the IOPMON.DLL file from the Windows/System directory.

CHAPTER 5: Novell NetWare Printing

5. Novell NetWare Printing

Refer to this chapter for instructions on setting up the print server and NetWare fileserver.

Please note that only SCS twinax or SCS/DSC coax printers attached to the print server can be printed to using a “generic” text Epson FX, or IBM Proprinter print driver from the PC/LAN host. Rasterized data (such as most Windows print drivers send out) cannot be converted into EBCDIC text.

If you have not already installed the print-control utility, please go back to Section

3.2 and do so now. Then skip to the section that applies to your NetWare setup.

Configuring the Print Server . . . . . . . . . . . . . . . . . . . . . . . . . . . Section 5.1

Controlled or Public Access Printer, Novell NetWare 5.x

(NDPS), NWAdmin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Section 5.2

Print Server, Novell NetWare 4.x (NDS), NWAdmin . . . . . . . . Section 5.3

Print Server, Novell NetWare 4.x (NDS), PCONSOLE . . . . . . Section 5.4

Remote Printer, Novell NetWare 4.x (NDS), NWAdmin . . . . . Section 5.5

Remote Printer, Novell NetWare 4.x (NDS), PCONSOLE . . . Section 5.6

Print Server, Novell NetWare 3.x and 2.x . . . . . . . . . . . . . . . . . Section 5.7

Remote Printer, Novell NetWare 3.x and 2.x, PCONSOLE. . . Section 5.8

5.1 Configuring the Print Server

ETHERNET TO TWINAX/COAX PRINT SERVER

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 according to the Connection Type you chose previously. The options were:

Remote (printer on IPX). . . . . . . . . . . . . . . . . . . . . . . . . . . . . Section 5.1.1

Remote (LRP on IP). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Section 5.1.2

Forward Jobs to a Queue . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Section 5.1.3

5.1.1 R

EMOTE(PRINTER ON

IPX)

1. Select NW Remote Printer by clicking on the white box in front of that selection.

2. The column titled “Object Information” will display the available configuration parameters.

a. In the Print Server field, enter the SAP Name assigned during step 8A in

Section 5.2.2.

b. In the field next to the print server’s local port (LPT1) that the target

printer is attached to, enter the printer number.

3. If you want to configure additional protocols, refer to the respective section. If your configuration of the print server is complete, click on the Apply Changes button on the bottom of the configuration window. Then Exit the utility.

5.1.2 R

EMOTE

(LPR ONIP)

1. If you haven’t already done so, assign an IP address to the print server. Refer to Section 4.1.1 for more information.

2. To turn off the printing of the banner page, the trailer page or any possible blank pages, configure the TCP/IP logical port as TCP1. On the main Print Server Information screen, click on Printer Ports/Emulation and then on the respective TCP/IP Logical Port.

5.1.3 F

ORWARDJOBS TO AQUEUE

If the print server isn’t already configured for servicing a NDS queue, refer to Section 4.1 for more information.

CHAPTER 5: Novell NetWare Printing

5.1.4 C

LIENTCONFIGURATION

Public Access printers can be configured from any client running the NetWare 5 client software. The user does not have to be signed on to the Novell network. To set up a Controlled Access printer, the client has to be signed on to the Novell network.

5.1.5 P

UBLICACCESSPRINTERS

1. Double-click on the Network Neighborhood icon on the Windows desktop.

2. Double-click on the Entire Network icon.

3. Open the NDPS Public Access Printers folder.

4. Double-click on the desired Public Access printer.

5. Follow the instructions given by the Windows Add Printer Wizard.

5.1.6 C

ONTROLLEDACCESSPRINTERS

1. Double-click on the Network Neighborhood icon on the Windows desktop.

2. Open the NDS context the NDPS printer object resides in.

3. Locate the desired NDPS printer object and double-click its icon.

4. Follow the instructions given by the Windows Add Printer Wizard.

5.2 Controlled or Public Access Printer, Novell NetWare 5.x (NDPS), NWAdmin

Under NetWare 5.x, printers attached through a print server can be configured as Controlled Access or Public Access printers. The instructions below cover both types unless noted otherwise. The following steps are covered:

Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Section 5.2.1

Creating a NDPS Printer Object . . . . . . . . . . . . . . . . . . . . . . . Section 5.2.2

ETHERNET TO TWINAX/COAX PRINT SERVER

5.2.1 P

REREQUISITES

To create a Printer Agent under NDPS, the following requirements must be met:

• The user must have at least Read, Write, Modify, and Create rights for the destination container where its associated Printer object will reside. This is not necessary when creating a Public Access printer.

• The user must be designated as a Manager of the NDPS Manager that will control this Printer Agent.

• A NDPS Broker must be running.

• A NDPS Manager object must be created.

Please refer to your Novell documentation for more information on these requirements. An on-line user’s guide can be found at www.novell.documentation.com.

5.2.2 C

REATING A

NDPS P

RINTEROBJECT

1. After logging into the Novell network with the above-mentioned rights, start the NetWare Administrator.

2. Creating a printer:

a. When creating a Controlled Access printer, click on the container where

you want the NDPS Printer object to reside.

i. From the Object menu, select Create.

ii. From the displayed list, select NDPS Printer. Click OK.

iii.Enter a name of your choice in the NDPS Printer Name field.

iv. Select Create a New Printer Agent as the Printer Agent Source and click

Create.

v. If desired, change the default Printer Agent (PA) Name, then browse

for the NDPS Manager Name.

b. When creating a Public Access printer, double-click on the NDPS

Manager.

i. Click on the Printer Agent List button on the right side of the displayed

window.

CHAPTER 5: Novell NetWare Printing

ii. Click New.

iii.Enter a name of your choice in the Printer Agent (PA) Name field.

3. Click on the Novell Printer Gateway and then click OK.

4. If the NDPS Manager has not been loaded before, you will now be prompted to do so. Click OK, then respond with OK again.

5. Select the most appropriate Printer Type and then highlight the Novell Port Handler in the bottom window. Click OK.

6. Select the appropriate Connection Type (see below).

a. Remote (printer on IPX)

b. Remote (LPR on IP)

c. Forward Jobs to a Queue

NOTE

The last option (Forward Jobs to a Queue) should only be selected if you have already created and linked the following NDS objects: Print Server, Printer, and Print Queue. You also should have configured the print server for NDS Print Server mode printing. See Section 5.3.

7. If you selected Remote (printer on IPX), select Port Type Other.

8. Click Next.

a. If you selected Remote (printer on IPX), specify a SAP Name and a Port

Number. These values will later be used to configure the print server. (Note: The SAP Name is specific to the print server. If multiple printers are attached to the print server, then the SAP Name should be different from the name of the Printer Agent, since it will be shared by the other printer[s].)

b. If you selected Remote (LPR on IP), enter the print server’s IP address in

the Host Address field. In the Printer Name field, enter TCPx, where x corresponds to the print server’s physical port(s).

c. If you selected Forward Jobs to a Queue, enter the Queue Name that is

associated with the print server and a Queue User Name.

ETHERNET TO TWINAX/COAX PRINT SERVER

9. Click Finish. (Note: If you have selected Remote [printer on IPX] your workstation will post an error message. Click OK. Once you have configured the print server, this error condition will be resolved.)

10. Select a printer driver for each client operating system. Click Continue and then OK.

11. Proceed with configuration of the print server.

5.3 Print Server, Novell NetWare 4.x (NDS), NWAdmin

Configuring the print server as a NetWare Print Server under NDS requires the following steps:

Entering NWAdmin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Section 5.3.1

Adding a Print Server Object. . . . . . . . . . . . . . . . . . . . . . . . . . Section 5.3.2

Adding Printer Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Section 5.3.3

Adding Print Queue Objects . . . . . . . . . . . . . . . . . . . . . . . . . . Section 5.3.4

Configuring the Print Server . . . . . . . . . . . . . . . . . . . . . . . . . . Section 5.3.5

Client Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Section 5.3.6

5.3.1 E

NTERING

NWA

DMIN

1. Login to NetWare as ADMIN, or as a user with ADMIN security equivalence.

2. Open the NetWare Tools group and double click on NWAdmin.

3. Check the current context on the title bar. If it is incorrect, select the appropriate context from the displayed list.

5.3.2 A

DDING APRINTSERVEROBJECT

1. Using the right mouse button, click the context to which the print server is to be added.

2. Select Create from the displayed menu.

3. Select Print Server and type a new print server name.

CHAPTER 5: Novell NetWare Printing

IMPORTANT

Observe the following points concerning the print server’s name:

• Do not use more than 19 characters in the print server’s name.

NWAdmin allows you to enter print server names longer that this, but the print server does not support names longer than 19 characters.

• Do not use spaces in the print server name. Use dashes or

underscores instead. NWAdmin allows spaces in the print server name, but the print server does not support this. However, you can use spaces in the names of the queues or printer objects.

4. Click the Create button.

5.3.3 A

DDINGPRINTEROBJECTS

1. Using the right mouse button, click the context to which the printer is to be added.

2. Select Create from the displayed menu.

3. Select Printer Object.

4. Enter the new printer name.

5. Click the Create button.

6. At the main NWAdmin screen, double-click the icon for the just-created print server.

7. From the Print Server window, click the Assignments button.

8. Select Add.

9. Select Printer.

10. Select OK.

11. Select OK at the Print Server window.

5.3.4 A

DDINGPRINTQUEUEOBJECTS

1. Using the right mouse button, click the context in which the queue is to be created.

2. Select Create from the displayed menu.

3. Select Print Queue.

ETHERNET TO TWINAX/COAX PRINT SERVER

4. At the Create Print Queue window, enter the queue name in the Print Queue Name field.

5. Select the volume from the Print Queue Volume pull-down list in the Select Object window.

6. Click OK.

7. Click the Create button on the Create Print Queue window.

8. Double-click the icon for the just-created printer.

9. Click the Assignments button.

10. Click the Add… button.

11. Select the Queue name. This name becomes the selected object.

NOTE

The selected printer is automatically set as the default.

12. Click OK.

13. Click OK.

5.3.5 C

ONFIGURING THEPRINTSERVER

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 in the tool bar. Follow these simple steps to configure the print server as a Novell NetWare 4.x NDS Print Server:

1. Select NW Print Server by clicking on the white box in front of that selection.

2. The column titled “Object Information” will display the available configuration parameters.

a. Replace the default Print Server Name (the Black Box serial number) with

the Print Server Name assigned during Adding a Print Server Object (see Section 5.3.2).

CHAPTER 5: Novell NetWare Printing

b. If necessary, enter the Password for this print server object and change the

Ethernet [frame] Type and the Queue Polling Time.

The Queue List and Notify List are for information only. This information must be changed on the Novell NetWare server.

3. In the left column of the print-control screen, click on the white circle in front of NDS.

4. Then click the NDS button.

5. The column titled “Object Information” will display the available configuration parameters. Enter the name of the correct NDS Tree and NDS Context manually or using the Browse button.

5.3.6 C

LIENTCONFIGURATION

To enable a client workstation to print to a NetWare queue, a local port must be captured. This can be accomplished using the NetWare User Tools from within MS Windows or through a capture command from the DOS prompt.

To capture a local port using NetWare User Tools from within MS Windows:

1. Open NetWare User Tools from your desktop.

2. Click on the printer icon on the top tool bar. The client’s available ports

(LPT1...) will be displayed on the left side of the screen. The available queues (resources) will be displayed on the right.

3. Click on the desired port, then on the queue you want to capture, and finally

on the Capture button.

4. Complete the capture process by configuring the LPT Settings and making

the capture Permanent, if so desired. Then Exit the program.

The same results can be obtained by using the Capture command from the DOS prompt:

At the DOS prompt, type the following command:

capture local=n queue=name

ETHERNET TO TWINAX/COAX PRINT SERVER

where n is the number of the LPT port you want to assign the queue to and name is the name of the queue you want to capture.

5.4 Print Server, Novell NetWare 4.x (NDS), PCONSOLE

Configuring the print server as a NetWare print server under NDS requires the following steps:

Adding a Print Server Object. . . . . . . . . . . . . . . . . . . . . . . . . . Section 5.4.1

Adding Printer Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Section 5.4.2

Adding Print Queue Objects . . . . . . . . . . . . . . . . . . . . . . . . . . Section 5.4.3

Configuring the Print Server . . . . . . . . . . . . . . . . . . . . . . . . . . Section 5.4.4

Client Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Section 5.4.5

5.4.1 A

DDING APRINTSERVEROBJECT

1. Login to NetWare as ADMIN, or as a user with ADMIN security equivalence.

2. Start NetWare’s PCONSOLE program.

3. If necessary, use PCONSOLE’s Change Context selection to change to the context where you want to install the print server. If you are not sure which context you should install the print server in, install the print server in the context that contains the users that will be using the print server most. For more information about contexts and other NetWare 4.x concepts, see your NetWare manuals.

4. On a piece of paper, write down the context in which you are installing the print server. You can read this from the Context: item at the top of PCONSOLE’s screen. Later, you will use this information to configure the print server.

5. Go to PCONSOLE’s Available Options menu and choose Print Servers. The Print Servers list appears.

6. Press <Ins> to add a new print server to the list. The New Print Server Name form appears.

7. Enter a name for the new print server and press <Enter>.

CHAPTER 5: Novell NetWare Printing

IMPORTANT

Observe the following points concerning the print server’s name:

• Do not use more than 19 characters in the print server’s name.

PCONSOLE allows you to enter print server names longer that this, but the print server does not support names longer than 19 characters.

• Do not use spaces in the print server name. Use dashes or

underscores instead. PCONSOLE allows spaces in the print server name, but the print server does not support this. However, you can use spaces in the names of the queues or printer objects.

After a moment, PCONSOLE returns to the Print Servers list. The new print server appears in the list.

5.4.2 A

DDINGPRINTEROBJECTS

Perform the procedures below to associate NetWare printer objects with the printers connected to the print server's ports. Do this when installing a new print server, or when connecting a new printer to the print server to service NetWare print queues.

1. If you haven’t already done so, start PCONSOLE, and change to the context where the print server is installed.

2. In the Print Servers list, select the print server and press <Enter>. The Print Server Information menu appears.

3. In the Print Server Information menu, select Printers and press <Enter>. The Serviced Printers list appears.

4. Press <Ins> to insert a new printer into the print server’s Serviced Printers list. The Object, Class list appears.

5. Navigate the Object, Class list to the context where the printer object resides, or where you want to install a new printer object. This should be the context where the majority of the printer’s users reside.

6. If the printer you want to add to the Serviced Printer list does not exist yet, press <Ins> to add a new printer to the Object, Class list. PCONSOLE prompts you for a name, then adds the new printer to the Object, Class list.

7. In the Object, Class list, select a printer to add to the print server’s Serviced Printers list. If you just added a new printer to the Object, Class list, select that new printer. Then press <Enter>. The new printer appears in the print server’s Serviced Printers list.

ETHERNET TO TWINAX/COAX PRINT SERVER

8. In the Serviced Printers list, select the printer you just added, and press <Enter>. The Printer Configuration form appears.

NOTE

Ignore the Printer Type, Configuration, Buffer Size, and Sampling Interval items on the Printer Configuration form. These items are not relevant to print server installations.

9. Select the Printer Number entry, and enter a value from the table below to associate that printer with the print server’s port.

10. If you are going to add a print queue to the new printer, go to Section 5.4.3.

Otherwise, reset the print server by powering it OFF and back ON again or by using the Reset button in the print-control utility.

5.4.3 A

DDINGPRINTQUEUEOBJECTS

Perform the procedure below to associate NetWare print queue objects with the print server’s NetWare Printer objects (see Section 5.4.2). Do this when installing a new print server, or when adding a new queue to be serviced by an existing NetWare Printer object associated with the print server.

1. If you haven’t already done so, start PCONSOLE, and change to the context where the print server’s NetWare Printer object resides. Then select the printer you want to associate the print queue(s) with and press <Enter>. The Printer Configuration form appears.

2. Select the Print queues assigned entry and press <Enter>. The Print Queues list appears. Make sure that there is at least one queue in the list.

3. Press <Ins> to add a queue to the Print Queues list. The Object, Class list appears.

4. Navigate the Object, Class list to the context where the print queue object resides, or where you want to create a new print queue object. This should be the context where the majority of the queue users reside.

5. If the queue you want to add to the Print Queue list does not exist yet, press <Ins> to add a new queue to the Object, Class list. PCONSOLE prompts you for a name and volume, then adds the new queue to the Object, Class list.

6. In the Object, Class list, select a Printer Queue to add to the printer’s Print Queues list. Then press <Enter>. The new queue appears in the printer’s Print Queues list.

CHAPTER 5: Novell NetWare Printing

7. Press <Esc> several times until the Exit? menu appears. Select Yes and press <Enter>.

8. If you are installing a new print server, proceed to Section 5.4.4. Otherwise, reset the print server by powering it OFF and back ON again or by using the

Reset button in the print-control utility.

5.4.4 C

ONFIGURING THEPRINTSERVER

1. Select NW Print Server by clicking on the white box in front of that selection.

2. The column titled “Object Information” will display the available configuration parameters.

a. Replace the default Print Server Name (the Black Box serial number)

with the Print Server Name assigned during Adding a Print Server Object (see Section 5.4.1).

b. If necessary enter the Password for this print server object and change the

Ethernet [frame] Type and the Queue Polling Time.

The Queue List and Notify List are for information only. This information must be changed on the Novell NetWare server.

3. In the left column of the print-control screen, click on the white circle in

front of NDS.

4. Then click the NDS button.

5. The column titled “Object Information” will display the available

configuration parameters. Enter the name of the correct NDS Tree and NDS Context manually or using the Browse button.

ETHERNET TO TWINAX/COAX PRINT SERVER

5.4.5 C

LIENTCONFIGURATION

To capture a local port using NetWare User Tools from within MS Windows:

1. Open NetWare User Tools from your desktop.

2. Click on the printer icon on the top tool bar. The client’s available ports

(LPT1, LPT2,...) will be displayed on the left side of the screen. The available queues (resources) will be displayed on the right.

3. Click on the desired port, then on the queue you want to capture, and finally

on the Capture button.

4. Complete the capture process by configuring the LPT Settings and making

the capture Permanent, if so desired. Then Exit the program.

The same results can be obtained by using the Capture command from the DOS prompt by typing the following command:

capture local=n queue=name

where n is the number of the LPT port you want to assign the queue to and name is the name of the queue you want to capture.

5.5 Remote Printer, Novell NetWare 4.x (NDS), NWAdmin

Configuring the print server as a NetWare remote printer under NDS requires the following steps:

Entering NWAdmin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Section 5.5.1

Optional: Adding a Print Server . . . . . . . . . . . . . . . . . . . . . . . Section 5.5.2

Adding Printer Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Section 5.5.3

Adding Print Queue Objects . . . . . . . . . . . . . . . . . . . . . . . . . . Section 5.5.4

CHAPTER 5: Novell NetWare Printing

Reloading the Print Server NLM. . . . . . . . . . . . . . . . . . . . . . . Section 5.5.5

Configuring the Print Server . . . . . . . . . . . . . . . . . . . . . . . . . . Section 5.5.6

Client Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Section 5.5.7

5.5.1 E

NTERING

NWA

DMIN

1. Login to NetWare as ADMIN, or as a user with ADMIN security equivalence.

2. Open the NetWare Tools group and double click on NWAdmin.

3. Check the current context on the title bar. If it is incorrect, select the appropriate context from the displayed list.

5.5.2 O

PTIONAL

: A

DDING APRINTSERVER

If the print server NLM is already running on your Novell server, skip this section and proceed directly to Section 5.3.3. Otherwise, follow these steps:

1. Using the right mouse button, click the context to which the Novell print server is to be added.

2. Select Create from the displayed menu.

3. Select Print Server and type a new print server name.

IMPORTANT

Observe the following points concerning the print server’s name:

• Do not use more than 19 characters in the print server’s name.

NWAdmin allows you to enter print server names longer that this, but the print server does not support names longer than 19 characters.

• Do not use spaces in the print server name. Use dashes or

underscores instead. NWAdmin allows spaces in the print server name, but the print server does not support this. However, you can use spaces in the names of the queues or printer objects.

4. Click the Create button.

5.5.3 A

DDINGPRINTEROBJECTS

1. Using the right mouse button, click the context to which the printer is to be added.

2. Select Create from the displayed menu.

ETHERNET TO TWINAX/COAX PRINT SERVER

3. Select Printer Object.

4. Enter a new Printer Name.

5. Click the Create button.

6. Double-click the Printer icon for the just-created printer.

7. Click the Configuration button.

8. At the Printer Type window, select Other/Unknown.

9. Optionally, set the IPX/SPX network address.

10. Click OK.

11. At the main NWAdmin window, double-click the Novell print server that exists in the context.

12. From the Print Server window, click the Assignments button.

13. Select Add.

14. Select Printer.

15. Select OK.

16. Select OK at the Print Server window.

5.5.4 A

DDINGPRINTQUEUEOBJECTS

1. Using the right mouse button, click the context in which the queue is to be created.

2. Select Create from the displayed menu.

3. Select Print Queue.

4. At the Create Print Queue window, enter the queue name in the Print Queue Name field.

5. Select the volume from the Print Queue Volume pull-down list on the Select Object window.

6. Click OK.

7. Click the Create button on the Create Print Queue window.

CHAPTER 5: Novell NetWare Printing

8. Double-click the Printer icon for the just-created printer.

9. Click the Assignments button.

10. Click the Add... button.

11. Select the Queue name. This name becomes the selected object. The selected printer is automatically set as the default.

12. Click OK.

13. Click OK.

5.5.5 R

ELOADING THEPRINTSERVER

NLM

1. Go to the console of the file server where the print server NLM is running or will be running.

2. If you already have a print server NLM loaded, unload it now by typing

unload pserver

at the prompt. Otherwise proceed directly to step 3.

3. Reload the print server NLM by typing the following at the prompt:

load pserver pserver_name

pserver_name is the name of the existing print server NLM or of the print server created in Section 5.5.2).

5.5.6 C

ONFIGURING THEPRINTSERVER

1. Select NW Remote Printer by clicking on the white box in front of that selection.

ETHERNET TO TWINAX/COAX PRINT SERVER

2. The column titled “Object Information” will display the available configuration parameters.

a. In the Print Server field, enter then name of the Novell Print Server NLM.

b. In the field next to the print server’s local port that the target printer is

attached to, enter the Printer Number that was assigned in Section 5.5.3, or select the printer by name from the pop-up menu.

5.5.7 C

LIENTCONFIGURATION

To capture a local port using NetWare User Tools from within MS Windows:

1. Open NetWare User Tools from your desktop.

2. Click on the printer icon on the top tool bar. The client’s available ports

(LPT1...) will be displayed on the left side of the screen. The available queues (resources) will be displayed on the right.

3. Click on the desired port, then on the queue you want to capture, and finally

on the Capture button.

4. Complete the capture process by configuring the LPT Settings and making

the capture Permanent, if so desired. Then Exit the program.

The same results can be obtained by using the Capture command from the DOS prompt:

At the DOS prompt type the following command:

capture local=n queue=name

where n is the number of the LPT port you want to assign the queue to and name is the name of the queue you want to capture.

CHAPTER 5: Novell NetWare Printing

5.6 Remote Printer, Novell NetWare 4.x (NDS), PCONSOLE

Configuring the print server as a NetWare remote printer under NDS requires the following steps:

Optional: Adding a Print Server . . . . . . . . . . . . . . . . . . . . . . . Section 5.6.1

Adding Printer Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Section 5.6.2

Adding Print Queue Objects . . . . . . . . . . . . . . . . . . . . . . . . . . Section 5.6.3

Reloading the Print Server NLM. . . . . . . . . . . . . . . . . . . . . . . Section 5.6.4

Configuring the Print Server . . . . . . . . . . . . . . . . . . . . . . . . . . Section 5.6.5

Client Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Section 5.6.6

5.6.1 O

PTIONAL

: A

DDING APRINTSERVER

If the print server NLM is already running on your Novell server, skip this section and go to Section 5.6.2. Otherwise, follow these steps:

1. Login to NetWare as ADMIN, or as a user with ADMIN security equivalence.

2. Start NetWare’s PCONSOLE program.

5. Go to PCONSOLE’s Available Options menu and choose Print Servers. The Print Servers list appears.

6. Press <Ins> to add a new print server to the list. The New Print Server Name form appears.

7. Enter a name for the new print server and press <Enter>.

ETHERNET TO TWINAX/COAX PRINT SERVER

IMPORTANT

Observe the following points concerning the print server’s name:

• Do not use more than 19 characters in the print server’s name.

PCONSOLE allows you to enter print server names longer that this, but the print server does not support names longer than 19 characters.

• Do not use spaces in the print server name. Use dashes or

underscores instead. PCONSOLE allows spaces in the print server name, but the print server does not support this. However, you can use spaces in the names of the queues or printer objects.

After a moment, PCONSOLE returns to the Print Servers list. The new print server appears in the list.

5.6.2 A

DDINGPRINTEROBJECTS

Perform the procedures below to associate NetWare printer objects with the printers connected to the print server’ ports. Do this when installing a new print server, or when connecting a new printer to the print server to service NetWare print queues.

1. If you haven’t already done so, start PCONSOLE, and change to the context where the print server is installed.

2. In the Print Servers list, select the desired Novell print server and press <Enter>. The Print Server Information menu appears.

3. In the Print Server Information menu, select Printers and press <Enter>. The Serviced Printers list appears.

4. Press <Ins> to insert a new printer into the print server’s Serviced Printers list. The Object, Class list appears.

6. If the printer you want to add to the Serviced Printer list does not exist yet, press <Ins> to add a new printer to the Object, Class list. After you have entered a new name, PCONSOLE adds the new printer to the Object, Class list.

CHAPTER 5: Novell NetWare Printing

8. In the Serviced Printers list, select the printer you just added and press <Enter>. The Printer Configuration form appears.

NOTE

Ignore the Configuration, Buffer Size, and Sampling Interval items on the Printer Configuration form. These items are not relevant to print server installations.

9. We recommend that you use the default Printer Number. If you do need to change the number, make sure it uniquely identifies the printer among other printers associated with the Novell print server.

10. In the Printer Type field, select Other/Unknown.

11. Return to the Available Options menu by pressing <Esc> repeatedly.

5.6.3 A

DDINGPRINTQUEUEOBJECTS

Perform the procedure below to associate NetWare print queue objects with the print server’s NetWare Printer objects (see Section 4.6.2). Do this when installing a new print server, or when adding a new queue to be serviced by an existing NetWare Printer object associated with the print server.

2. Select the Print queues assigned entry and press <Enter>. The Print Queues list appears. Make sure that there is at least one queue in the list.

3. Press <Ins> to add a queue to the Print Queues list. The Object, Class list appears.

4. Navigate the Object, Class list to the context where the print queue object resides, or where you want to create a new print queue object. This should be the context where majority of the queue users reside.

6. In the Object, Class list, select a Printer Queue to add to the printer’s Print Queues list. Then press <Enter>. The new queue appears in the printer’s Print Queues list.

ETHERNET TO TWINAX/COAX PRINT SERVER

7. If you want to add another queue to the printer’s Print Queues list, repeat step 2 through 6 of this procedure.

8. Press <Esc> several times until the Exit? menu appears. Select Yes and press

<Enter>.

5.6.4 R

ELOADING THEPRINTSERVER

NLM

1. Go to the console of the file server where the print server NLM is running or will be running.

2. If you already have a print server NLM loaded, unload it now by typing

unload pserver

at the prompt. Otherwise proceed directly to step 3.

3. Reload the print server NLM by typing the following at the prompt:

load pserver pserver_name

pserver_name is the name of the existing print server NLM or of the print server created in Section 5.6.1.

5.6.5 C

ONFIGURING THEPRINTSERVER

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 in the tool bar.

Follow these simple steps to configure the print server as a Novell NetWare Remote Printer.

1. Select NW Remote Printer by clicking on the white box in front of that selection.

2. Click the NW Remote Printer button.

3. The column titled “Object Information” will display the available configuration parameters.

CHAPTER 5: Novell NetWare Printing

a. In the Print Server field, enter then name of the Novell Print Server NLM.

b. In the field next to the print server local port that the target printer is

attached to, enter the Printer Number that was assigned in Section 5.6.2, or select the printer by name from the pop-up menu.

4. If you want to configure additional protocols, refer to the respective section. If your configuration of the print server is complete, click on the Apply Changes button on the bottom of the configuration window. Then Exit the utility.

5.6.6 C

LIENTCONFIGURATION

To capture a local port using NetWare User Tools from within MS Windows:

1. Open NetWare User Tools from your desktop.

2. Click on the printer icon on the top tool bar. The client’s available ports

(LPT1...) will be displayed on the left side of the screen. The available queues (resources) will be displayed on the right.

3. Click on the desired port, then on the queue you want to capture, and finally

on the Capture button.

4. Complete the capture process by configuring the LPT Settings and making

the capture Permanent, if so desired. Then Exit the program.

The same results can be obtained by using the Capture command from the DOS prompt by typing the following:

capture local=n queue=name

where n is the number of the LPT port you want to assign the queue to and name is the name of the queue you want to capture.

ETHERNET TO TWINAX/COAX PRINT SERVER

5.7 Print Server, Novell NetWare 3.x and 2.x

Configuring the print server as a bindery print server under NetWare can be done from within the PrintControl utility. This section contains the following two parts:

Creating NetWare Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . Section 5.7.1

Client Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Section 5.7.2

5.7.1 C

REATINGNETWAREOBJECTS

1. Login to a NetWare file server as SUPERVISOR, or as a user with SUPERVISOR security equivalence. If there are more than one file server on your network, log into the one you want to be the print server’s master file server.

IMPORTANT

When installed as NetWare Print Server, the print server’s master file server must have a name that is no longer than 19 characters. If your file server has a longer name, you must either choose a different file server as the print server’s master file server, or shorten the file server’s name.

2. If you haven’t already done so, start the print-control utility.

3. 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.

4. 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 in the tool bar.

5. Select NW Print Server by clicking on the white box in front of that selection.

6. Then click the NW Print Server button.

7. The column titled “Object Information” will display the available configuration parameters.

a. Replace the default Print Server Name (the Black Box serial number) with

a Print Server Name of your choice.

CHAPTER 5: Novell NetWare Printing

IMPORTANT

Observe the following points concerning the print server’s name:

• Do not use more than 19 characters in the print server’s name.

PCONSOLE allows you to enter print server names longer that this, but the print server does not support names longer than 19 characters.

• Do not use spaces in the print server name. Use dashes or

underscores instead. PCONSOLE allows spaces in the print server name, but the print server does not support this. However, you can use spaces in the names of the queues or printer objects.

b. If necessary enter the Password for this print server object and change the

Ethernet [frame] Type and the Queue Polling Time.

8. In the left column of the print-control screen, click on the white circle in front of bindery.

9. Then click the bindery button.

10. The column titled “Object Information” will display the available configuration parameters. Enter the name of the Master File Server.

11. Click on the Queues button.

12. Select the print server’s printer port you want to assign queues to from the available options displayed in the field labeled “Ports.”

13 Add a new queue by typing the name of the new queue into the field labeled

“New Queue Name”.

14. Click on the Add>> button (it’s next to the “New Queue Name” field).

15. Repeat steps 12 through 14 to add additional queues. Click OK.

16. If you want to configure additional protocols, refer to the respective section. If your configuration of the print server is complete, click on the Apply Changes button on the bottom of the configuration window. Then Exit the utility.

17. Print-control will automatically create the following objects on the NetWare file server:

• a print server object,

• print queue object(s), and

ETHERNET TO TWINAX/COAX PRINT SERVER

• printer objects for all physical ports on the print server.

5.7.2 C

LIENTCONFIGURATION

To capture a local port using NetWare User Tools from within MS Windows:

1. Open NetWare User Tools from your desktop.

2. Click on the printer icon on the top tool bar. The client’s available ports (LPT1, LPT2,...) will be displayed on the left side of the screen. The available queues (resources) will be displayed on the right.

3. Click on the desired port, then on the queue you want to capture, and finally on the Capture button.

4. Complete the capture process by configuring the LPT Settings and making the capture Permanent, if so desired. Then Exit the program.

The same results can be obtained by using the Capture command from the DOS prompt by typing the following:

capture local=n queue=name

where n is the number of the LPT port you want to assign the queue to and name is the name of the queue you want to capture.

5.8 Remote Printer, Novell NetWare 3.x and 2.x , PCONSOLE

Configuring the print server as a remote printer under NetWare requires the following steps:

Adding Print Queue Objects on the Novell Server ........................Section 5.8.1

Optional: Adding a Print Server Object on the Novell Server ......Section 5.8.2

Adding Printer Objects on the Novell Server ................................Section 5.8.3

Associating Printer Objects with Print Queue Objects...................Section 5.8.4

Reloading the NetWare PServer NLM ............................................Section 5.8.5

Configuring the Print Server............................................................Section 5.8.6

CHAPTER 5: Novell NetWare Printing

Client Configuration.........................................................................Section 5.8.7

5.8.1 A

DDINGPRINTQUEUEOBJECTS ON THENOVELLSERVER

If you are going to set up the print server remote printer to use print queues that already exist, skip this section. Otherwise, perform the procedure below to create NetWare print queue objects. Do this when installing a new print server, or when adding a new queue to be serviced by an existing NetWare Printer object associated with the print server.

1. Login to a NetWare file server as SUPERVISOR, or as a user with

SUPERVISOR security equivalence. If there are more than one file server on your network, log into the one you want to be the print server’s master file server.

2. If you haven’t already done so, start PCONSOLE.

3. From the Available Options menu, select Print Queue Information and press

<Enter>.

4. Press <Insert> to add a new queue to the list.

5. Type a queue name and press <Enter>.

6. If you want to add additional queues, repeat steps 3 and 4.

7. Press <Esc> until the Available Options menu appears.

5.8.2 O

PTIONAL

: A

DDING APRINTSERVEROBJECT ON THENOVELLSERVER

If the print server NLM is already running on your Novell server, skip this section and proceed directly to Section 5.8.3. Otherwise, follow these steps.

1. From PCONSOLE’s Available Options menu, select Print Server Information.

2. Press <Ins>.

3. Enter a name for the new print server and press <Enter>.

ETHERNET TO TWINAX/COAX PRINT SERVER

IMPORTANT

Observe the following points concerning the print server’s name:

• Do not use more than 19 characters in the print server’s name. PCONSOLE allows you to enter print server names longer that this, but the print server does not support names longer than 19 characters.

• Do not use spaces in the print server name. Use dashes or underscores instead. PCONSOLE allows spaces in the print server name, but the print server does not support this. However, you can use spaces in the names of the queues or printer objects.

After a moment, PCONSOLE returns to the Print Servers list. The new print server appears in the list.

4. Press <ESC> to return to the Available Options menu.

5.8.3 A

DDINGPRINTEROBJECTS ON THENOVELLSERVER

Perform the procedures below to associate NetWare printer objects with the printers connected to the print server’s ports. Do this when installing a new print server, or when connecting a new printer to the print server to service NetWare print queues.

1. From the Available Options menu, select Print Server Information.

2. In the Print Servers list, select the desired Novell print server and press

<Enter>.

3. Select Print Server Configuration and press <Enter>.

4. Select Printer Configuration and press <Enter>.

5. For each of the print server ports to which you are connecting a printer, select

one of the Not Installed printers and press <Enter>.

6. Assign a name to the printer and select the type according to the following table :

6. Press <ESC> and select Save Changes? Yes.

7. Press <ESC> again to return to the Print Server Configuration menu.

Printer Attached to I-O Printer Server’s

Physical Port

NetWare

Printer Type

Twinax/Coax Remote Parallel, LPT1

CHAPTER 5: Novell NetWare Printing

5.8.4 A

SSOCIATINGPRINTEROBJECTS WITHPRINTQUEUEOBJECTS

1. From the Printer Server Configuration menu, select Queues Serviced by Printer and press <Enter>.

2. Select the printer you want to assign a print queue to and press <Enter>.

3. Press <Insert> to add a queue to the list.

4. Select the queue that you want the printer to service and press <Enter>.

5. Enter a priority level and press <Enter>.

6. Press <Esc> until the Exit PCONSOLE dialog box appears. Choose Yes and press <Enter>.

5.8.5 R

ELOAD THENETWAREPSERVER

NLM

1. Go to the console of the file server where the print server NLM is running or will be running.

2. If you already have a print server NLM loaded, unload it now by typing

unload pserver

at the prompt. Otherwise proceed directly to step 3.

3. Reload the print server NLM by typing the following at the prompt:

load pserver pserver_name

pserver_name is the name of the existing print server NLM or of the print server above (see Section 5.8.1).

5.8.6 C

ONFIGURING THEPRINTSERVER

1. Select NW Remote Printer by clicking on the white box in front of that selection.

ETHERNET TO TWINAX/COAX PRINT SERVER

2. The column titled “Object Information” will display the available configuration parameters.

a. In the Print Server field, enter then name of the Novell Print Server NLM.

b. In the field next to the print server’s local port that the target printer is

attached to, enter the Printer Name assigned earlier (see Section 5.8.1). Alternately, you may enter the Novell printer number associated with the printer.

5.8.7 C

LIENTCONFIGURATION

To capture a local port using NetWare User Tools from within MS Windows:

1. Open NetWare User Tools from your desktop.

2. Click on the printer icon on the top tool bar. The client’s available ports

(LPT1...) will be displayed on the left side of the screen. The available queues (resources) will be displayed on the right.

3. Click on the desired port, then on the queue you want to capture, and finally

on the Capture button.

4. Complete the capture process by configuring the LPT Settings and making

the capture Permanent, if so desired. Then Exit the program.

The same results can be obtained by using the Capture command from the DOS prompt by typing the following:

capture local=n queue=name

where n is the number of the LPT port you want to assign the queue to and name is the name of the queue you want to capture.

CHAPTER 6: SNA (APPC) Printing

6. SNA (APPC) Printing

If you haven’t already installed the print-control utility, please go back and do so now. Then proceed with the following instructions.

Configuring the Print Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Section 6.1

Retrieving AS/400 Parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Section 6.2

6.1 Configuring the Print Server

1. Select SNA (APPC) by clicking on the white box in front of that selection.

2. The column titled “Object Information” will display the available configuration parameters.

a. In the “Adapter Address” field, enter the Local adapter address found in

the AS/400’s line description. If the print server is attached to a remote controller or gateway, enter the address of the Ethernet adapter of that remote controller or gateway. Make sure to use the format specified in the field (XX:XX:XX:XX:XX:XX). Refer to Section 6.2.1 if you need help locating this address on your AS/400.

b. In the “Host Network ID” field, enter the Local network ID found in the

AS/400’s network attributes listing. Refer to Section 6.2.2 if you need help locating this information.

c. In the “Host Control Point Name” field, enter the Local control point

name found in the AS/400’s network attributes listing.

ETHERNET TO TWINAX/COAX PRINT SERVER

d. In the “Interface Control Point Name” field, enter a name for the print

server. Make sure the name complies with the following requirements:

1) The name must be exactly 8 characters.

2) The name must start with a alphanumeric character (i.e. A–Z).

3) The name must consist of alphanumeric (a–z, A–Z) or numeric (0–9) characters only. Spaces, underscores, slashes, etc., are not accepted.

4) The first four characters should uniquely identify the device, since the print server will automatically create printer devices on your AS/400 using the first four characters of the name you assigned to the print server followed by PRTXX.

3. If you want to configure additional protocols, refer to the respective section.

If your configuration of the print server is complete, click on the Apply Changes button on the bottom of the configuration window. Then Exit the utility.

4. The print server will now automatically create the following devices on you AS/400:

a. APPC Controller with the name you assigned as the “Interface Control

Point.” This step will be omitted if the print server is attached to a 5494 controller.

b. 5494 Controller with the first five characters of the “Interface Control

Point” name followed by the identifier RMT.

c. A printer device for every printer that was attached to the print server at

the time the new configuration was sent to the print server or when the print server was last reset. Names for the printer devices are actually given by the AS/400 system and follow this format:

ABCDPRTXX

where:

ABCD are the first four characters of the “Interface Control Point” name.

PRT is a fixed identifier for printers.

CHAPTER 6: SNA (APPC) Printing

XX identifies the printer(s) that was (were) actually attached to the print server at the time the SNA (APPC) configuration was applied to the print server or at the time the print server was last reset. XX identifies the printer(s) attached to the print server in the following manner:

6.2 Retrieving AS/400 Parameters

This section explains how to locate the parameters needed for the configuration of the print server, namely:

Adapter Address (AS/400) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Section 6.2.1

Host Network ID and Host Control Point Name . . . . . . . . . . . . . Section 6.2.2

AS/400 Auto-Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Section 6.2.3

6.2.1 A

DAPTERADDRESS

(AS/400)

1. Type WRKLIND (Work Line Description) on the AS/400’s command line. Press Enter.

2. Locate the line that the print server is attached to from the displayed lines. Enter 5 (Display) in the field in front of that line. Press Enter.

3. Locate the Local adapter address. This is the value you wanted to find. As you enter it in the print-control’s menu, make sure to change the format to XX:XX:XX:XX:XX:XX.

6.2.2 H

OSTNETWORK

ANDHOSTCONTROLPOINTNAME

1. Type DSPNETA (Display Network Attributes) on the AS/400’s command line. Press Enter.

Printer Attached to

I-O Print Server

physical port

XX-Value

Corresponding

logical port with

5250 printer

session

00 Twinax SCS1

ETHERNET TO TWINAX/COAX PRINT SERVER

2. The Host Network ID is listed as the Local network ID and the Host Control Point Name is listed as the Local control point name.

6.2.3 AS/400 A

UTO-CONFIGURATION

Make certain that the AS/400 is set up for auto-configuration of new devices by doing the following:

1. On the AS/400 command line, type DSPSYSVAL SYSVAL (QAUTOCFG), then press <Enter>. The Auto Configure device parameter should be set to 1=ON.

2. On the AS/400 command line, type DSPSYSVAL SYSVAL (QATORMT), then press <Enter>. The Auto Configure Remote Controller parameter should be set to 1=ON.

3. On the AS/400 command line, type DSPSYSVAL SYSVAL (QAUTORMT), then press <Enter>. The Number of devices to autoconfigure should be large enough to account for all virtual (APPC) devices on your network. If you are unsure, you may want to increase this number.

4. On the AS/400 command line, type WRKLIND, then press <Enter>. Enter a 5 to display, or 2 to change in front of the line that the print server is attached to. Press <Enter> several times until Autocreate controller is displayed in the lower section of the menu options. Verify that the Autocreate controller parameter is set to *Yes.

CHAPTER 7: Twinax/Coax Configuration

7. Twinax/Coax Configuration

The Ethernet to Twinax/Coax Print Server connects 5250-type twinax or 3270-type coax printers to their respective IBM host (such as an AS/400 or 3270-type mainframe) using Ethernet wiring in lieu of twinax or 3270-coax cables. The print server provides connection to the IBM host by way of SNA, AnyNet, or TCP/IP (TN5250e or TN3270e) for SCS printers. For IPDS printers, the print server communicates to the IBM host using TCP/IP (PPR/PPD). The print server then converts the incoming Ethernet protocol to either IBM twinax or 3270-coax protocols and sends the data on to the printer. Printer messages are passed back to the IBM host through the same process.

The Ethernet to Twinax/Coax Print Server also has the capability of accepting ASCII text data from Windows, DOS, or UNIX and converting it to print on the attached SCS twinax or SCS/DSC coax printer. Communication with these ASCII hosts is done using IPX/SPX or TCP/IP. Black Box’s TCP/IP DirectPort print driver may also be used for Windows 95/98 printing. Only ASCII text data can be converted from ASCII to EBCDIC and passed on to a SCS twinax or SCS/DSC coax printer. It is important to note that Windows print drivers generally output rasterized data which cannot be processed by IBM SCS printers. Therefore, for Windows printing, choose the “generic” print driver, and set the spool settings to pass on “raw” data. The print server will also accept non-rasterized Epson FX or IBM Proprinter (PPDS) dot-matrix data streams, which it converts into the appropriate twinax or 3270-coax printer data streams.

The table on the next page shows the association of the various connectivity protocols and data streams supported:

ETHERNET TO TWINAX/COAX PRINT SERVER

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.”

CHAPTER 7: Twinax/Coax Configuration

To setup the Ethernet to Twinax/Coax Print Server, select which protocol you are using to communicate between the IBM host and the print server. Designate whether the printer is attached using twinax or coax. For 3270-coax printers, you will also have to identify if the printer is an IPDS printer. You may also need to customize how the twinax or 3270-coax printer treats some of the instructions coming from the IBM hosts.

If you have not already installed the print-control utility, please go back to Chapter 3 and do so now. Then perform the LAN connectivity configuration of the print server using Chapters 4, 5, or 6. Use this chapter to complete the configuration of the print server emulation function.

Twinax Port Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Section 7.1

3270-Coax Port Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Section 7.2

ASCII Printing Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Section 7.3

Command Pass-Through . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Section 7.4

7.1 Twinax Port Configuration

The twinax port is configured using the print-control utility. From the PC where the PrintControl utility is installed, select the appropriate Ethernet to Twinax/Coax Print Server you wish to configure.

1. From the PrintControl utility’s main window, highlight the desired print server, then click on the Configure button, or double-click on the desired print server.

2. After performing the necessary protocol configurations (if not already completed), click on the Printer Ports/Emulations button.

3. Click on the radio button to the left of the Twinax Port button to activate the

twinax port.

4. Click on the Twinax Port button to display the twinax port configuration

options.

5. Using the check boxes or drop-down menus, you can now customize how the

attached twinax printer will function.

ETHERNET TO TWINAX/COAX PRINT SERVER

a. Print Configuration Report: Check this option if you want to have the

print server’s configuration report printed on the printer attached to this port. The configuration report is printed each time the print server is powered-on or reset, and it lists the current values of the unit’s configuration parameters. An unchecked box is the default setting.

b. Busy on Commands: The twinax protocol requires printers to report

BUSY after a command is received. Some faster IBM and compatible printers do not do this. Choose No to disable checking for BUSY. The default setting is Yes.

c. Busy on Data: The twinax protocol requires printers to report BUSY after

data is received. Some faster IBM and compatible printers do not do this. Choose No to disable checking for BUSY. The default setting is Yes.

d. IBM 5256 Emulation: A true IBM 5256 printer will halt and report an

error when a LPI command is received. However, some printers such as the IBM 5262, emulate a 5256 printer, and will receive LPI commands. You may choose to Send LPI or Don’t send LPI (which is the default).

6. If there are any other configuration changes you wish to make, do so. Then click on the Apply Changes button and reset the print server to complete the process.

7.2 3270-Coax Port Configuration

The 3270-type coax port is configured using the print-control utility. From the PC where the PrintControl utility is installed, select the appropriate Ethernet to Twinax/Coax Print Server you wish to configure.

1. From the PrintControl utility’s main window, highlight the desired print server, then click on the Configure button, or double-click on the desired print server.

2. After performing the necessary protocol configurations (if not already completed), click on the Printer Ports/Emulations button.

3. Click on the radio button to the left of the Coax Port button to activate the

3270-coax port.

4. Click on either the IPDS or SCS radio button to the right of the Coax Port

button to indicate which type of printer is attached to the print server.

5. Click on the Coax Port button to display the 3270-coax port configuration

options.

CHAPTER 7: Twinax/Coax Configuration

6. Using the check boxes or drop-down menus, you can now customize how the attached 3270-coax printer will function.

a. Print Configuration Report: Check this option if you want to have the

b. CPI Support: Use this option to select the character per inch (CPI)

capabilities of the 3270-coax printer. This option must match the 3270coax printer’s capabilities.

c. NLQ Support: Use this option to select whether the 3270-coax printer is

capable of printing text in standard, draft, or near letter quality (NLQ) mode. This option must match the 3270-coax printer’s capabilities.

7. If there are any other configuration changes you wish to make, do so. Then click on the Apply Changes button and reset the print server to complete the process.

7.3 ASCII Printing Configuration

The Ethernet to Twinax/Coax Print Server is capable of receiving text data from ASCII hosts such as PCs running DOS, Windows or OS/2, as well as UNIX systems and other ASCII hosts. The ASCII data is converted into EBCDIC. The print server also converts the Epson FX or IBM Proprinter PPDS dot-matrix command structure into the appropriate IBM SCS twinax or 3270-coax SCS/DSC printer commands. Due to differences between the IBM twinax and 3270-coax printers and ASCII printers, you may need to customize some of the conversion parameters to obtain the best printouts.

1. From the PrintControl utility’s main window, highlight the desired print server, then click on the Configure button, or double-click on the desired print server.

2. After performing the necessary protocol configurations (if not already completed), click on the Printer Ports/Emulations button.

3. Click on the Printer Emulation button. Using the drop-down menus, you will select the type of ASCII print driver that is sending data to the print server as well as the code page that is being used to define the ASCII characters.

ETHERNET TO TWINAX/COAX PRINT SERVER

a. ASCII Printer Emulation: Use this option to select the type of ASCII

printer data stream that is being received by the print server from the ASCII host (a PC, a LAN server, or other ASCII host). You need to make the same selection here as used on the ASCII host so that the print server can convert the incoming ASCII data stream into the appropriate EBCDIC data stream for the attached twinax or 3270-coax printer. For example, on the ASCII host (such as a PC), you have selected Epson FX as the type printer you want to print to, you would also select Epson FX here. Note that only text can be printed. The options available are both dot matrix: Epson FX or IBM Proprinter PPDS (which is the default).

b. ASCII Character Set: Use this option to select the code page that is being

used for the data stream coming from the ASCII host (a PC, a LAN server, or other ASCII host). The Code Page selected here must match the ASCII host’s. The print server needs to know this in order to convert the characters from ASCII to EBCDIC properly. Code Page 850 or Code Page 437 (also known as PC Set 2) are available. Code Page 437 is the default.

4. Click on the SCS Conversion button. Using the drop-down menus, you will make selections about how character per inch, line feed, and carriage returns are handled.

a. Sheet Feed Command: Use this selection to indicate whether sheet feeder

commands in the incoming ASCII data stream will be passed on to the twinax or 3270-coax printer in the form of bin commands. The available options are Send Bin Commands and Not Supported (default).

b. Adjust Position on CPI Change: Characters per inch (CPI) changes that

occur in the middle of a line can result in overprinting or gaps in the text. Use the Yes option to adjust the positioning of the text when a CPI change occurs. Use the Yes +5 positions to correct an error of five print positions that can occur when printing from IBM PC Support or Client Access. If No is selected, the twinax or 3270-coax printer will recalculate the beginning position for the new CPI and start printing at that point. For example, if the original CPI was 12, and 48 characters had been printed, then a 10 CPI command was received, the printer would recalculate the beginning for the remainder of the text on that line at 4.9 inches in from the left margin. This would leave a gap of 0.9 inches as the 12 CPI text would have stopped at 4 inches in from the left margin. Likewise, a change to 15 CPI would cause an overprint to occur of about

1.67 inches of text because the previous text ended at 4 inches in from the left margin and the new text began at 2.34 inches in from the left margin. The available options are Yes, Yes +5 Positions, and No (default).

CHAPTER 7: Twinax/Coax Configuration

c. Adjust MPP on CPI Change: IBM twinax and 3270-coax printers maintain

a Maximum Print Position (MPP) even when CPI changes. MPP normally is associated with the CPI (10 CPI has a MPP of 132 associated with it, 15 CPI has a MPP of 198, and so on). Using this option will cause the print server to adjust the twinax or 3270-coax printer’s MPP so that the maximum amount of text can be printed on a line. For example, if you had been printing at 10 CPI, the MPP would have been 132. If you then change to 15 CPI part way through the line, the IBM twinax or 3270-coax printer would not adjust the MPP but would start a new line when 132 characters had been printed. On an IBM printer, this would result in a line wrapping in the wrong place followed by a short line. The entire page would be thrown out of alignment, possibly even pushing a line or two onto the next page which would in itself be a short page. The print server will adjust the MPP so that the entire line is used, even though part of the characters are compressed. The available options are No and Yes (default).

d. Send LF for ESC J: ESC J is an ASCII command that can be used to move

the printing down in increments of x/216 inches. Since twinax printers cannot do this, you have the option of simply ignoring such commands or sending a line feed (LF) to the system printer every time the print server receives an ESCJ command. The options are Yes and No (default).

e. Change CR to NL: Some ASCII jobs expect the printer to do a New Line

(NL) when a Carriage Return (CR) is received. A NL is defined as a CR and a Line Feed (LF) which positions the cursor at the beginning of the next line. With No selected, the print server will send a CR to the printer when a CR is received from the ASCII host. A CR simply moves the cursor to the beginning of the current line (but not the beginning of the next line). The options are Yes and No (default).

f. Change LF to NL: Some ASCII jobs (primarily UNIX) expect the printer

to do a new line (NL) when a line feed (LF) is received. A NL is defined as a carriage return (CR) and a LF which positions the cursor at the beginning of the next line. With No selected, the print server will send a LF to the printer when a LF is received from the ASCII host. A LF simply moves the cursor to the next line (but not the beginning of the next line. The options are Yes and No (default).

g. PC Support +5 Fix: With Yes selected, the interface will correct an error of

five print positions that can occur when printing from IBM PC Support (now Client Access). The options are Yes and No (default).

ETHERNET TO TWINAX/COAX PRINT SERVER

h. Command Pass-Thru: Command Pass-Thru (CPT) is a useful feature that

allows access to printer features that may not be available through the standard ASCII driver. When using CPT, printer-specific commands are sent with the print data from the host. The commands are in EBCDIC hex format and are flagged with the CPT identifiers &%. When the print server receives CPT commands, it will not attempt to interpret them, but will “pass the command through” to the printer. The options are No and Yes (default).

5. If there are any other configuration changes you wish to make, do so. Then click on the Apply Changes button and reset the print server to complete the process.

7.4 Command Pass-Through

The Black Box Command Pass-Thru (CPT) feature can be used to access all of the built-in features of a SCS or SCS/DSC printer, even if those features are not normally available through the ASCII host software, especially if you must use a generic print driver (such as in Windows). Printer-specific command sequences are inserted into the data sent to the twinax or 3270-coax non-IPDS printer from the host. The Print Box recognizes these special sequences and “passes the command through” to the printer. The steps below describe how to use Command Pass-Thru.

1. Find the command for the print feature in the printer’s manual.

2. Convert the printer command to EBCDIC hexadecimal.

3. Place the Command Pass-Thru delimiter &% into the document at the point where the feature is to take effect. This signals the start of the print feature. Enter the printer command in EBCDIC hexadecimal code, then enter the delimiter &% again. You may enter a space between hexadecimal code pairs to make the command easier to read; however, do not put spaces between the delimiter and the hexadecimal characters.

4. To change the print feature back, move the cursor to the point in the text where the print feature is to be changed. Enter the delimiter, the new printer command, and then the delimiter again.

For example:

2B D2 04 29 00 0F is the command in EBCDIC hexadecimal code for 15 CPI printing on printers supporting this feature. 2B D2 04 29 00 0A is the command in hexadecimal for 10 CPI printing. So, to begin 15 CPI printing, enter the command as follows:

CHAPTER 7: Twinax/Coax Configuration

&%2B D2 04 29 00 0F&%

Then, to change printing back to 10 CPI, enter:

&%2B D2 04 29 00 0A&%

Only characters from 00 to FF are recognized (alphabetical characters must be in upper case). Errors in the Command Pass-Thru sequence will cause the Print Box to ignore the command and printing will resume at the point the error occurred.

Command Pass-Thru may invalidate horizontal spacing. Although the command is displayed on the screen, the Print Box treats it as a command and it is not printed. If part of the sequence is printed, an error has been made while entering the codes. Check the document and make sure you are using the correct format and EBCDIC hexadecimal characters.

Avoid sending codes that would move the print position during Command PassThru. Since the Print Box does not process these commands, it cannot keep track of the print position changes, and this may affect the position of following characters and page layout.

Black Box Command Pass-Thru strings can also be sent to the printer by typing them on the ASCII or IBM host screen and pressing the print screen key.

ETHERNET TO TWINAX/COAX PRINT SERVER

8. IBM IPDS Printing

The Ethernet to Twinax/Coax Print Server is designed to pass through all IPDS commands it receives from the IBM host.

The print server uses IBM’s proprietary TCP/IP protocol, PPR/PPD, for connection between either the IBM mainframe or the AS/400. Configuring the print server is a simple matter of assigning a TCP/IP address to the print server and modifying any of the print server’s default setup parameters.

• For twinax printers, the print server will automatically detect the model number and type of printer (SCS or IPDS). The print server will pass that information on to the AS/400. The AS/400 will require manual configuration. Use Section 8.1 to configure the AS/400

• For 3270-type coax printers, you will need to manually configure the print server to indicate that an IPDS printer is attached. The IBM mainframe will require manual configuration. Use Section 8.2 to configure the IBM mainframe.

See Chapter 7 for more information on setup options. See also Chapter 3 for instructions on setting up the print-control utility.

Configuring the AS/400 for IPDS Printing........................................Section 8.1

Configuring the IBM Mainframe for IPDS Printing .........................Section 8.2

8.1 Configuring the AS/400 for IPDS Printing

The basic configuration of the print server should already have been completed using instructions found in Chapter 4.

Several steps are required to configure the AS/400 host system to enable IPDS printing to a print server. These include ensuring that your AS/400 has the required PTFs installed and configured properly to support TCP/IP printing, verifying that line descriptions and host TCP/IP table entries are made, configuring printer devices for use with PSF/400, and configuring the data area that is used by AFP.

Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Section 8.1.1

Creating a Line Description on the AS/400 . . . . . . . . . . . . . . . . . Section 8.1.2

CHAPTER 8: IBM IPDS Printing

Configuring a TCP/IP Host Table Entry . . . . . . . . . . . . . . . . . . . . Section 8.1.3

Configuring V3R1 or V3R6 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Section 8.1.4

Configuring V3R2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Section 8.1.5

Configuring V3R7, V4R1, and Above . . . . . . . . . . . . . . . . . . . . . . . Section 8.1.6

Verifying the IPDS Configuration on the AS/400. . . . . . . . . . . . . Section 8.1.7

8.1.1 R

EQUIREMENTS

Make sure that the AS/400 host is running a version of OS/400 that supports TCP/IP and that you have the most recent PTFs installed and configured.

The PTF information presented below may have been superceded with more recent releases. For versions not shown below, check with IBM for the appropriate PTF information. Additional information about PTFs to use can be obtained from the IBM AS/400 service Web site http://as400service.rochester.ibm.com.

OS/400 V3R1

General C6198310 Cumulative tape or later

SF35164 TCP/IP for PSF/400 (order cover letter only)

SF24140 IPDS pass through (order cover letter only)

Sockets SF30018

WRKAFP2 SF40039

PSF/400 APAR SA44304

OS/400 V3R2

PSF/400 APAR SA44304

OS/400 V3R6

General C5346360 Cumulative tape or later

SF45620 TCP/IP for PSF/400 (order cover letter only)

SF45624 IPDS pass through

ETHERNET TO TWINAX/COAX PRINT SERVER

Sockets SF30508

WRKAFP2 SF31461

PSF/400 APAR SA44304

OS/400 V3R7

PSF/400 APAR SA44304

8.1.2 C

REATING ALINEDESCRIPTION ON THE

AS/400

If the print server and the AS/400 host are not on the same LAN segment, have the system administrator verify that there is a route defined in the TCP/IP route List. If there is not a route defined, use the AS/400 ADDTCPRTE COMMAND to create a route definition.

Also, verify if a line description has been created for the line to which the print server will be attached. If there is not a line description, have the system administrator use the AS/400 CRTLINETH to create an Ethernet line description.

8.1.3 C

ONFIGURING A

TCP/IP H

OSTTABLEENTRY

This step is optional—IBM suggests that a host entry may be created in the TCP/IP table. Have the system administrator use the AS/400 CFGTCP command to add the host name and TCP/IP address of the print server.

8.1.4 C

ONFIGURING

V3R1 ORV3R6

PSF/400 for V3R1 or V3R6

The following instructions are used to create a printer device description:

1. At the AS/400 command line, enter the command CRTDEVPRT.

2. Press the F11 key to display the keywords.

3. In the Device Description (DEVD) field, enter the name of the printer attached to the print server. The name may comprise of the letters A–Z and numerals 0–9. It must begin with a letter, and a maximum of 10 characters are allowed.

4. In the Device Class (DEVCLS) field, enter *RMT.

5. In the Device Type (TYPE) field, enter *IPDS.

CHAPTER 8: IBM IPDS Printing

6. In the Device Model (MODEL) field, enter 0.

7. In the Advanced Function Printing (AFP) field, enter *YES.

8. In the AFP Attachment (AFPATTACH) field, enter *APPC.

9. In the Font (FONT) field, enter an appropriate value such as 11.

10. In the Form Feed (FORMFEED) field, enter *AUTOCUT. If the printer is a dot matrix, enter *CONT.

11. In the Remote Location (RMTLOCNAME) field, enter TCPIP.

AFP for V3R1 or V3R6

The following instructions are used to create a data area that is used by PSF/400:

1. At the AS/400 command line, enter the command WRKAFP2.

2. Press the F11 key to display the keywords, then press F10 to display additional

values.

3. In the Printer Device Name (DEVD) field, enter the name of the printer attached to the print server. This name must be identical to the name entered for the device name in the DEVD field in the CRTDEVPRT command.

4. In the IPDS Pass Through (IPDSPASTHR) field, enter *YES. This causes PSF/400 to transform SCS into IPDS before printing.5. In the TCP/IP Support (TCPIP) field, enter *YES.

5. In the Remote System (RMTSYS) field, enter the TCP/IP address of the print server. You may also enter the host name if you used the optional CFGTCP command to create a TCP/IP Host Table entry.

6. In the Port (PORT) field, enter 5001.

7. In the Activation Timer (ACTTMR) field, enter *NOMAX. This will cause PSF/400 to wait indefinitely for a response to an activation request.

8. In the Inactivity Timer (INACTTMR) field for V3R1, or Release Timer (RLSTMR) field for V3R6, enter *SEC15. This is parameter should be set to a value at least equal to the timeout value on the printer. This is the time PSF/400 will maintain a session with the print server while there are no spooled files with a status of RDY.

ETHERNET TO TWINAX/COAX PRINT SERVER

8.1.5 C

ONFIGURING

V3R2

PSF/400 for V3R2

The following instructions are used to create a printer device description:

1. At the AS/400 command line, enter the command CRTDEVPRT.

2. Press the F11 key to display the keywords.

4. In the Device Class (DEVCLS) field, enter *RMT.

5. In the Device Type (TYPE) field, enter *IPDS.

6. In the Device Model (MODEL) field, enter 0.

7. In the Advanced Function Printing (AFP) field, enter *YES.

8. In the AFP Attachment (AFPATTACH) field, enter *APPC.

9. In the Font (FONT) field, enter an appropriate value such as 11.

10. In the Form Feed (FORMFEED) field, enter *AUTOCUT. If the printer is a dot matrix, enter *CONT.

11. In the Remote Location (RMTLOCNAME) field, enter TCPIP.

AFP for V3R2

The following instructions are used to create a data area that is used by PSF/400:

1. At the AS/400 command line, enter the command CRTPSFCFG.

2. Press F11 to display the keywords, then press F10 to display additional values.

3. In the PSF Configuration (PSFCFG) field, enter the name of the printer attached to the print server.

4. In the Library field, enter QGPL.

5. In the IPDS Pass Through (IPDSPASTHR) field, enter *YES. This causes PSF/400 to transform SCS into IPDS before printing.

CHAPTER 8: IBM IPDS Printing

6. In the Activation Release Timer (ACTRLSTMR) field, enter *NORDYF. This

will cause PSF/400 to print all spooled files with a status of RDY before releasing the session (which does not terminate the writer).

7. In the Release Timer (RLSTMR) field, enter *SEC15. This is parameter

should be set to a value at least equal to the timeout value on the printer. This is the time PSF/400 will maintain a session with the print server while there are no spooled files with a status of RDY.

8. In the Remote Location Name or Address (RMTLOCNAME) field, enter the

TCP/IP address of the printer attached to the print server.

You may also enter the host name if you used the optional CFGTCP command to create a TCP/IP Host Table entry.

9. In the Port (PORT) field, enter 5001.

10. In the TCP/IP Activation Timer (ACTTMR) field, enter *NOMAX. This will

cause PSF/400 to wait indefinitely for a response to an activation request.

8.1.6 C

ONFIGURING

V3R7, V4R1,

ANDABOVE

AFP for V3R7, V4R1, and Above

1. At the AS/400 command line, enter the command CRTPSFCFG.

2. Press F11 to display the keywords.

3. In the PSF Configuration (PSFCFG) field, enter the name of the print server. This must be the exact name used in the USRDFNOBJ field in the CRTDEVPRT command (see Step 14 on the next page).

4. In the IPDS Pass Through (IPDSPASTHR) field, enter *YES. This causes PSF/400 to transform SCS into IPDS before printing.

5. In the Activation Release Timer (ACTRLSTMR) field, enter *NORDYF. This will cause PSF/400 to print all spooled files with a status of RDY before releasing the session (which does not terminate the writer).

6. In the Release Timer (RLSTMR) field, enter *SEC15. This is parameter

ETHERNET TO TWINAX/COAX PRINT SERVER

PSF/400 for V3R7, V4R1, and Above

The following instructions are used to create a printer device description:

1. At the AS/400 command line, enter the command CRTDEVPRT.

2. Press the F11 key to display the keywords.

3. In the Device Description (DEVD) field, enter the name of the printer

attached to the print server. The name may be comprised of the letters A–Z and numerals 0–9, must begin with a letter, with a maximum of 10 characters allowed.

4. In the Device Class (DEVCLS) field, enter *LAN.

5. In the Device Type (TYPE) field, enter *IPDS.

6. In the Device Model (MODEL) field, enter 0.

7. In the LAN Attachment (LANATTACH) field, enter *IP.

8. In the Advanced Function Printing field, enter *YES.

9. In the Port Number (PORT) field, enter 5001.

10. In the Font (FONT) field, enter an appropriate value such as 11.

11. In the Form Feed (FORMFEED) field, enter *AUTOCUT. If the printer is a dot-matrix, enter *CONT.

12. In the Activation Timer (ACTTMR) field, enter *NOMAX. This will cause the AS/400 host to wait indefinitely for a response to an activation request.

13. In the Remote Location (RMTLOCNAME) field, enter the TCP/IP address of the printer attached to the print server. You may also enter the host name if you used the optional CFGTCP command to create a TCP/IP Host Table entry.

14. In the User-Defined Object (USRDFNOBJ) field, enter the name of the print server. Leave the library blank unless you know its name. Enter *PSFCFG as the object type.

CHAPTER 8: IBM IPDS Printing

8.1.7 V

ERIFYING THE

IPDS C

ONFIGURATION ON THE

AS/400

To test that the AS/400 and the print server are connected and communicating, ping the print server from an AS/400 workstation with the following command:

PING ‘TCP/IP ADDRESS’ or PING HOST NAME

TCP/IP Address is the address of the print server (be sure to include the single quote marks around the address). Host name is the optional name you may have defined for the printer attached to the print server if you created an optional TCP/IP Host Table entry. If the pings are not successful, refer to Chapter 9. If the pings are successful, vary on the print server’s printer device description by typing this command (all on one line):

VRYCFG(print server printer device name)

CFGTYPE(*DEV) STATUS(*ON)

To use PSF/400 to send IPDS files to the print server, start the writer by typing this command:

STRPRTWTR DEV(print server printer device name)

8.2 Configuring the IBM Mainframe for IPDS Printing

The print server’s basic configuration should already have been completed using instructions found in Chapter 4. Additional configuration options for the print server can be set through either the print-control utility or by using host download commands. These functions are described later in this chapter.

Several steps are required to configure the MVS system to print AFP/IPDS files on the print server with PPR/PPD (TCP/IP). These are:

1. Define the MVS communications control units to MVS.

2. Modify the TCP/IP profile on your MVS system.

3. Ping the printer.

4. Define the printer as a writer-controlled printer to JES.

5. Define the printer to PSF/MVS with PRINTDEV, including IP address.

For more information, refer to IBM publications TCP/IP for MVS: Customization and Administration Guide, or PSF V3R1.0 for OS/390 Customization, or PSF/MVS: System Programming Guide

ETHERNET TO TWINAX/COAX PRINT SERVER

Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Section 8.2.1

Define the Communications Control Unit to MVS. . . . . . . . . . . . Section 8.2.2

Modify the TCP/IP Profile in MVS. . . . . . . . . . . . . . . . . . . . . . . . . Section 8.2.3

Verify the Printer Connection (Ping the Print Server). . . . . . . . . Section 8.2.4

Handling MVS Connectivity Problems. . . . . . . . . . . . . . . . . . . . . . Section 8.2.5

Define the Printer to JES. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Section 8.2.6

Define the Printer to PSF/MVS . . . . . . . . . . . . . . . . . . . . . . . . . . . Section 8.2.7

Using the Print Server with MVS . . . . . . . . . . . . . . . . . . . . . . . . . . Section 8.2.8

8.2.1 R

EQUIREMENTS

Make sure that you have at least the following or newer, installed and configured on your system:

• PSF/MVS Version 2.2.0 with APAR OW15599

• MVS Scheduler with APRA 0212236

• TCP/IP Version 3 Release 1 or higher, installed and configured on MVS

To obtain the PTFs associated with these APARs, contact the IBM Support Center.

8.2.2 D

EFINE THECOMMUNICATIONSCONTROLUNIT TO

MVS

If you have not already done so, define the communications control unit (such as a

3172) on the MVS system. Use either an MVS configuration program (MVSCP) or a hardware configuration definition (HCD), depending on the version of your MVS system:

• When using a version earlier than MVS 4.1.0, use an MVSCP.

• When using a version of MVS 4.1.0 or later, use an HCD or an MVSCP.

For more information about using these methods, refer to the IBM publications MVS/ESA Migration Planning: Dynamic I/O Configuration or MVS/ESA Hardware Configuration: Using the Dialog.

CHAPTER 8: IBM IPDS Printing

8.2.3 M

ODIFY THE

TCP/IP P

ROFILE IN

MVS

The TCP/IP profile contains system configuration statements used to initialize the TCP/IP address space. Some statements require special considerations when you are printing from PSF/MVS. The following example shows the specific statements that require consideration shown in bold:

ACBPOOLSIZE 1000 ADDRESSTRANSLATIONPOOLSIZE 1500 CCBPOOLSIZE 150

DATABUFFERPOOLSIZE 160 32768

ENVELOPEPOOLSIZE 750 IPROUTEPOOLSIZE 300 LARGEENVELOPEPOOLSIZE 50 RCBPOOLSIZE 50 SCBPOOLSIZE 256 SKCBPOOLSIZE 256

SMALLDATABUFFERPOOLSIZE 256

TCBPOOLSIZE 512

TINYDATABUFFERPOOLSIZE 256

UCBPOOLSIZE 100

KEEPALIVEOPTIONS INTERVAL 10 SENDGARBAGE FALSE ENDKEEPALIVEOPTIONS GATEWAY

; * Network First hop Linkname Packet Size Subnet mask Subnet value

9 = BPCLAN 2000 0.255.255.0 0.99.12.0

DEFAULTNET 9.99.12.254 BPCLAN 2000 0.255.255.0 0

The following is a description of each statement that needs special consideration, the application and the changes they make necessary. Be aware that if you change any of the values in the TCP/IP profile, you will need to restart TCP/IP in order for the changes to take place.

DATABUFFERPOOLSIZE defines the number and size of the data buffers. It is recommended that you specify 160 data buffers and a buffer size of 32768.

SMALLDATABUFFERPOOLSIZE defines the number of small data buffers. It is recommended that you specify at least 256 small data buffers.

TINYDATABUFFERPOOLSIZE defines the number of tiny data buffers. It is recommended that you specify at least 256 tiny data buffers.

ETHERNET TO TWINAX/COAX PRINT SERVER

KEEPALIVEOPTIONS: PSF relies on TCP to detect when a connection with a print server is no longer usable. When no data has been exchanged between PSF/MVS and the print server, TCP periodically sends keep-alive probes to the print server. These periodic probes, called keep-alive transmissions, enable TCP to discover when a connection is no longer usable, even if the print server is abruptly powered off or is no longer accessible through the network.

The frequency of keep-alive transmissions is controlled by the INTERVAL parameter on the KEEPALIVEOPTIONS statement. The frequency applies to all TCP applications that direct TCP to send keep-alive transmissions. The default frequency is after about two hours of inactivity.

For printing on an print server, it is recommended that you specify a shorter interval than the default, such as 10 minutes, for the interval between keep-alive transmissions. Also, if any target host requires that the keep-alive packet contain data, include the statement SENDGARBAGETRUE.

GATEWAY: The Packet_size parameter of the GATEWAY statement defines the maximum transmission unit (MTU) for the MVS host. For network printers, the MTU size is fixed at 1024 bytes. The value cannot be adjusted.

8.2.4 V

ERIFY THEPRINTERCONNECTION(PING THEPRINTSERVER

)

To verify that the IBM MVS system can establish a connection with the print server, ping the print server from the MVS system.

• From a TSO session, enter the following: TSO Ping ip_address

• In JES2, enter the following command from the System Display and Search Facility (SDSF) menu 6: ping ip_address

The ip_address specifies the IP address of the NIC. The following shows examples of a successful ping and an unsuccessful ping.

Successful ping:

EZA04581 Ping V3R1: Pinging host 9.99.12.33

(Use ATTN to interrupt.)

EZA04631 PING: Ping #1 response took 0.084 seconds.

Successes so far = 1.

CHAPTER 8: IBM IPDS Printing

Unsuccessful ping:

EZA04581 Ping V3R1: Pinging host 9.99.12.33

(Use ATTN to interrupt.)

EZA04631 PING: Ping #1 timed out.

8.2.5 H

ANDLING

MVS C

ONNECTIVITYPROBLEMS

If you encounter problems when pinging the print server from MVS, here’s how to resolve them:

Ping is Not Successful

If the ping is not successful, verify the following:

• The print server and printer both are powered on.

• The IP address is unique in the TCP/IP network. If the IP address of the MVS system is not unique, contact your system administrator.

• The Maximum Transmission Unit (MTU) size of the IP packet for the MVS system is equal to the MTU size of the network printer that is fixed at 1024. To change the MTU size for the MVS system, change the GATEWAY statement in the MVS TCP/IP profile and restart TCP/IP to activate the changes. If these items are in order, consult your system administrator about a possible network problem.

Ping is Successful

A successful ping usually indicates that the MVS system can communicate with the print server; however, you might receive a successful ping even though the IP address of the print server is a duplicate of another IP address. If PSF is unable to establish a network connection with the print server or if PSF output for the printer attached to the print server prints elsewhere, follow these steps to determine whether the IP address of the printer is unique:

1. Turn off the printer.

2. Wait at least 5 minutes for TCP/IP to clear the Address Resolution Protocol (ARP) tables. (If your installation specified a longer interval on the ARPAGE configuration statement in the TCP/IP profile, you may need to wait longer. For information about the ARPAGE statement, refer to the IBM TCP/IP MVS Customization and Administration Guide.)

ETHERNET TO TWINAX/COAX PRINT SERVER

3. Enter the ping command again from the MVS system. If you receive a successful response to the ping command, there is a duplicate IP address. Consult your system administrator.

8.2.6 D

EFINE THEPRINTER TO

JES

When an print server is used with JES, it must be defined for deferred printing mode with JES.

• The JES2 printer definition initialization member, located in the system PARMLIB is shown below:

FSS (FSS1), PROC=PSFPROC,HASPFSSM=HASPFSSM PRT1 FSS=FSS1,MODE=FSS,PRMODE= (LINE,PAGE,SOSI1), CLASS=C, UCS=0, SEP, NOSPEPDS, CKPTPAGE=100 DRAIN, MARK, TRKCELL=YES

The above example is correct for JES2 3.11 and above. For earlier versions of

JES2, the statement is FSSDEF and would be stated as FSSDEF FSSNAME=FSS1.

The value specified for the PROC parameter must match the name on the PSF/MVS startup procedure.

• The JES3 printer definition is shown below. This example is not executable, but is intended to help the JES3 systems programmer define the printer to the MVS host.

FSSDEF, TYPE=WTR, FSSNAME=FSS1, PNAME=PSFPROC, SYSTEM=SYS1, TERM=NODEVICE, JNAME=PRT1, JUNIT=(,SYS1,,OFF), FSSNAME=FSS1, MODE=FSS, PM=(LINE,PAGE,SOSI1),CHARS=(YES,GT12),

The value specified for the JNAME parameter must match the name of the printer in the PSF/MVS startup procedure.

The value specified for the PNAME parameter must match the name on the PSF/MVS startup procedure.

CHAPTER 8: IBM IPDS Printing

8.2.7 D

EFINE THEPRINTER TO

PSF/MVS

Each print server must be defined to PSF with a PRINTDEV statement in the PSF/MVS startup procedure.

Currently, IBM does not supply a network printer-specific writer procedure. (Remember that the print server appears to the IBM mainframe as a network printer.) However, the APSWPROT sample from the APAR medium can be copied and modified for network printers. Make sure that you specify 300-pel font libraries even though the printer attached to the print server may higher resolutions. The following is a sample procedure (PSFPROC) that can be modified to suit your installation.

The following is a description of the statements to be used in the PSF Startup Proc:

FAILURE – Specifies the action that PFS/MVS takes after a printing failure or a TCP/IP network failure. If FAILURE=WCONNECT and the print server is connected to another host when PSF/MVS attempts to establish a connection on TCP/IP, PSF/MVS continuously retries (up to the limit specified in CONNINTV) until the print server becomes available. FAILURE=STOP stops the attempt to connect the print server.

TIMEOUT – Specifies the action that PSF/MVS takes after a timeout when on output is available on JES. The DISCINTV parameter specifies the timeout interval. TIMEOUT=REDRIVE requests that PSF/MVS redrive the printer FSA using the value of the MGMTMODE parameter. TIMEOUT=STOP requests that PSF/MSV stop the printer FSA, which can then be restarted only by an operator command.

MGMTMODE – Set this parameter to OUTAVAIL. OUTAVAIL requests that PSF start a communications session with the print server only when output is available on the JES spool.

DISCINTV – Specifies the disconnect interval in seconds. The value can range from zero to 86,400. It is suggested that the setting be 15. When no output is available from JES for this time period, PSF/MSV ends the session with the print server. If the value is set to zero, PSF/MSV does not end the session because there is no output.

IPADDR – Specifies the IP address of the print server. Replace the

xxx.xxx.xxx.xxx with the IP address you defined using the PrintControl utility (see Section 4.1).

PORTNO – Specifies the TCP/IP socket that is used for AFP/IPDS printing. This

parameter must be 5001.

ETHERNET TO TWINAX/COAX PRINT SERVER

For more information on the PRINTDEV statement, see the IBM publication PSF/MSV System Programming Guide.

8.2.8 U

SING THEPRINTSERVER WITH

MVS

In normal operation, a session with the print server is maintained while there is output on the JES spool and the print server is available. When there is no more output on the spool and the disconnect interval expires, PSF/MVS ends the session with the print server. PSF/MVS attempts to restart the session when there is more work on the spool for the print server. After the session is restarted, PSF/MVS must reload the resources required for the print jobs.

To use an print server with your MVS system, you use the following JES operator commands

Starting a Print Server on MVS

To start a print server on MVS, do the following:

1. Start TCP/IP.

2. Power on the printer.

3. Start the printer FSA.

• For JES2:

$Sprinter-name

• For JES3:

VARY printer-name, ON

Stopping a Print Server on MVS

You can stop an print server on MVS in the following ways:

The preferred method is to first stop the PSF FSA for the print server by entering the following command from the MVS console:

• For JES2:

$Pprinter-name

• For JES3:

VARY printer-name, OFF

CHAPTER 8: IBM IPDS Printing

CANCEL printer-name

where printer-name specifies the name of the printer FSA. The print server and printer can then be turned off.

• To end the PSF FSA for the printer, use the JES commands. If you are unable to purge or cancel the printer using the JES commands, enter the following command:

MODIFY FFSname, FORCE, printer-name

Black Box PC435A User Manual

Specifications and Main Features

Frequently Asked Questions

User Manual