Printronix PrintNet P8000 Line Operation & User’s Manual

CAREFULLY READ THE FOLLOWING TERMS AND CONDITIONS BEFORE USING THIS PRINTER. USING THIS PRINTER INDICATES YOUR ACCEPTANCE OF THESE TERMS AND CONDITIONS. IF YOU DO NOT AGREE TO THESE TERMS AND CONDITIONS, PROMPTLY RETURN THE PRINTER AND ALL ACCOMPANYING HARDWARE AND WRITTEN MATERIALS TO THE PLACE YOU OBTAINED THEM, AND YOUR MONEY WILL BE REFUNDED. Definitions “Software” shall mean the digitally encoded, machine-readable data and program. The term “Software Product” includes the Software resident in the printer and its documentation. The Software Product is licensed (not sold) to you, and Printronix, Inc. either owns or licenses from other vendors who own, all copyright, trade secret, patent and other proprietary rights in the Software Product. License 1. Authorized Use. You agree to accept a non-exclusive license to use the Software resident in the printer solely for your own customary business or personal purposes. 2. Restrictions. a. To protect the proprietary rights of Printronix, Inc., you agree to maintain the Software Product and other proprietary information concerning the typefaces in strict confidence. b. You agree not to duplicate or copy the Software Product. c. You shall not sublicense, sell, lease, or otherwise transfer all or any portion of the Software Product separate from the printer, without the prior written consent of Printronix, Inc. d. You may not modify or prepare derivative works of the Software Product. e. You may not transmit the Software Product over a network, by telephone, or electronically using any means; or reverse engineer, decompile or disassemble the Software. f. You agree to keep confidential and use your best efforts to prevent and protect the contents of the Software Product from unauthorized disclosure or use. 3. Transfer. You may transfer the Software Product with the printer, but only if the recipient agrees to accept the terms and conditions of this Agreement. Your license is automatically terminated if you transfer the Software Product and printer. Limited Software Product Warranty Printronix, Inc. warrants that for ninety (90) days after delivery, the Software will perform in accordance with specifications published by Printronix, Inc. Printronix, Inc. does not warrant that the Software is free from all bugs, errors and omissions. Remedy Your exclusive remedy and the sole liability of Printronix, Inc. in connection with the Software is replacement of defective software with a copy of the same version and revision level. Disclaimer of Warranties and Limitation of Remedies 1. THE PARTIES AGREE THAT ALL OTHER WARRANTIES, EXPRESS OR IMPLIED, INCLUDING WARRANTIES OF FITNESS FOR A PARTICULAR PURPOSE AND MERCHANTABILITY ARE EXCLUDED. Printronix, Inc. does not warrant that the functions contained in the Software will meet your requirements or that the operation of the Software will be uninterrupted or error free. Printronix, Inc. reserves the right to make changes and/or improvements in the Software without notice at any time. 2. IN NO EVENT WILL PRINTRONIX, INC. BE LIABLE FOR LOST PROFITS, LOST DATA, BUSINESS INTERRUPTIONS, OR ANY OTHER DIRECT, INDIRECT, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OF OR INABILITY TO USE THIS PRODUCT, EVEN IF HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES, OR ANY DAMAGES CAUSED BY THE ABUSE OR MANIPULATION OF THE SOFTWARE. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES, SO THE ABOVE LIMITATION MAY NOT APPLY TO YOU. 3. Printronix, Inc. will not be liable for any loss or damage caused by delay in furnishing a Software Product or any other performance under this Agreement. 4. Our entire liability and your exclusive remedies for our liability of any kind (including liability for negligence except liability for personal injury caused solely by our negligence) for the Software Product covered by this Agreement and all other performance or nonperformance by us under or related to this Agreement are limited to the remedies specified by this Agreement. 5. California law governs this Agreement. Termination of License Agreement This License shall continue until terminated. This license may be terminated by agreement between you and Printronix, Inc. or by Printronix, Inc. if you fail to comply with the terms of this License and such failure is not corrected within thirty (30) days after notice. When this License is terminated, you shall return to the place you obtained them, the printer and all copies of the Software and documentation. U.S. Government Restricted Rights Use, duplication or disclosure by the Government is subject to restrictions as set forth in the Rights in Technical Data and Computer Software clause at FAR 242.227-7013, subdivision (b) (3) (ii) or subparagraph (c) (1) (ii), as appropriate. Further use, duplication or disclosure is subject to restrictions applicable to restricted rights software as set forth in FAR 52.227-19 (c) (2). Acknowledgement of Terms and Conditions YOU ACKNOWLEDGE THAT YOU HAVE READ THIS AGREEMENT, UNDERSTAND IT, AND AGREE TO BE BOUND BY ITS TERMS AND CONDITIONS. NEITHER PARTY SHALL BE BOUND BY ANY STATEMENT OR REPRESENTATION NOT CONTAINED IN THIS AGREEMENT. NO CHANGE IN THIS AGREEMENT IS EFFECTIVE UNLESS WRITTEN AND SIGNED BY PROPERLY AUTHORIZED REPRESENTATIVES OF EACH PARTY. BY USING THIS PRINTER, YOU AGREE TO ACCEPT THE TERMS AND CONDITIONS OF THIS AGREEMENT. READ THIS SOFTWARE LICENSE AGREEMENT BEFORE USING THIS PRINTER

No part of this document may be reproduced, copied, translated or incorporated in any other material in any form or by any means, whether manual, graphic, electronic, mechanical or otherwise, without the prior written consent of Printronix®. Printronix makes no representations or warranties of any kind regarding this material, including, but not limited to, implied warranties of merchantability and fitness for a particular purpose. Printronix shall not be held responsible for errors contained herein or any omissions from this material or for any damages, whether direct or indirect, incidental or consequential, in connection with the furnishing, distribution, performance, or use of this material. The information in this manual is subject to change without notice. Copyright 2009, 2013, Printronix, Inc. All rights reserved.

Inc. Copyright 1991-1999 Wyndham Technologies Inc. IGP, LinePrinter Plus, PGL, Network Interface Card, PrintNet and Printronix are registered trademarks of Printronix, Inc. AIX, AS/400, NetView, and OS/2 are registered trademarks, and AFP, Intelligent Printer Data Stream, IPDS, Print Services Facility, and PSF are trademarks of International Business Machines Corporation. Unix is a registered trademark of X/Open Company Limited. Microsoft, MS-DOS, Windows, Windows 95, Windows 98, Windows Me, WIndows NT and Windows 2000 are registered trademarks of Microsoft Corporation. FTP Software and OnNet are trademarks or registered trademarks of FTP Software, Inc. NetManage and Chameleon are trademarks or registered trademarks of NetManage, Inc. Frontier Technologies and SuperTCP are trademarks or registered trademarks of Frontier Technologies Corporation. Solaris is a registered trademark of Sun Microsystems, Inc. HP-UX is a registered trademark of Hewlett-Packard Company. DG/UX is a registered trademark of Data General Corporation. LINUX is a registered trademark of Linus Torvalds. Ultrix is a registered trademark of Digital Equipment Corporation. IRIX is a registered trademark of Silicon Graphics, Inc.

1 Introduction .............................................. 15 Overview ...............................................................................15 What is the PrintNet? .......................................................15 What Special Features are Available?.............................15 Logical Printer Architecture ...................................................17 Destinations/Queues........................................................19 Models..............................................................................19 Interfaces...............................................................................20 PrintNet Card LED.................................................................20 Speed Setting for 10/100Base-T......................................21 Conventions Used in this Manual..........................................22 Notes and Notices.................................................................23 2 Installation And Configuration .................. 25 Installation .............................................................................25 Connecting to the Network...............................................25 Configuration Tools ...............................................................25 Printing an Ethernet Test Page........................................26 PrintNet Verification .........................................................26 HTML Forms ....................................................................27 Telnet ...............................................................................28 Setup through Data Stream .............................................28

3 PrintNet Web Server ................................ 29 Overview ...............................................................................29 Configuration.........................................................................31 Printer....................................................................................32 Printer Configuration ........................................................32 Configuration Management..............................................33 File Management .............................................................34 Network Configuration...........................................................36 TCP/IP Network ...............................................................36 Print Path Configuration ........................................................38 Destination Settings .........................................................39 Chosen Model Settings....................................................41 Chosen Logpath...............................................................41 Print Model Configuration......................................................41 Log Path Configuration .........................................................44 TN5250/3270 Configuration ..................................................46 SNMP Configuration .............................................................50 Administration Configuration .................................................56 System Information ..........................................................56 Passwords .......................................................................58 System Configuration............................................................59 Firmware Upgrade ................................................................60 Job Capture...........................................................................61 Status ....................................................................................61 Status - I/O Port ....................................................................62 Status - Network....................................................................62 Help.......................................................................................62

4 Windows Configuration ............................ 63 Overview ...............................................................................63 Windows Environment Description........................................63 Windows PrintNet Configuration ...........................................64 Mandatory ........................................................................64 Optional............................................................................64 Configuration using ARP..................................................64 Communicating Across Routers.......................................66 Changing Destination Names ..........................................67 5 Unix Configuration.................................... 69 Overview ...............................................................................69 Unix Environment Description...............................................69 Unix PrintNet Configuration...................................................70 Mandatory ........................................................................70 Optional............................................................................70 Using ARP........................................................................70 Using BOOTP ..................................................................72 Communicating Across Routers.......................................73 Unix Host Configuration ........................................................74 Manual System V Host Setup ..........................................74 PrintNet Installation on HP-UX..............................................75 Solaris 2.6 – 7 PrintNet Setup...............................................76 Manual LPR/LPD Host Setup...........................................77 PrintNet Configuration for AIX 4.......................................79 AIX Remote Queue Time–Out Setting.............................81 Printing from AIX..............................................................81 Printing with FTP..............................................................82 Alternate FTP Printing......................................................83 Direct Socket Printing.......................................................84

6 z/OS Configuration, IPDS Printer ............. 85 Overview ...............................................................................85 Requirements...................................................................85 Configuration Checklist ....................................................86 Configuring PSF for z/OS to Print IPDS Files .......................86 Configuration Procedure ..................................................86 Verifying a TCP/IP-Attached Printer on z/OS...................96 Sharing Line Matrix Printers on z/OS....................................97 JES Spool Printer Sharing ...............................................97 Port Switching Printer Sharing .........................................99 Handling z/OS Connectivity Problems ..................................99 Ping is not Successful......................................................99 Ping is Successful..........................................................100 7 AS/400 Configuration, ASCII Printer ...... 101 Overview .............................................................................101 Configuring AS/400 for ASCII using TCP/IP .......................103 Configuring with ADDTCPIFC........................................103 Configuring a Router Definition with ADDTCPRTE........105 Configuring a Local Domain and Hostname ..................105 Configuring A TCP/IP Host Table Entry.........................105 Configuring the AS/400 for Printing.....................................106 Setting Up Printing for ASCII Files.................................106 Verify Printing on AS/400 ....................................................113 AS/400 ASCII Troubleshooting ...........................................114

8 AS/400 Configuration, IPDS Printer ....... 115 Configuring on AS/400 as an IPDS Printer .........................115 Printing AFP, IPDS, and SCS Files................................115 Requirements.................................................................116 Configuration Checklist ..................................................116 Configuring an AS/400 TCP/IP Interface with ADDTCPIFC...................................................................118 Configuring PSF/400 for IPDS on V3R2 ........................120 Configuring PSF/400 for IPDS on V3R7 and Above......126 Configuring PSF for IPDS on V4R2 and Above.............131 Configuring AFP with CRTPSFCFG on V4R3 and Above (Optional) ............................................................132 Configuring PSF with CRTDEVPRT on V4R2 and Above.............................................................................134 Verifying the IPDS Configuration on AS/400.......................138 Sharing the AS/400 Printer on the Network ........................139 Printer Sharing Parameters............................................140 AS/400 Troubleshooting......................................................143 Cannot PING the Printer ................................................143 PSF/400 Terminates when Initialized.............................143 Spooled Print File Remains in PND Status....................144 Spooled Files Disappear without Printing ......................144 Data is Being Clipped.....................................................144

9 z/OS Configuration, TN3270E................ 145 z/OS Configuration for a TN3270E Printer..........................145 Coax Printer Support FMID.................................................145 Program Materials...............................................................146 VTAM Definitions for SCS and DSE TN3270E ..............147 TCPIP Configuration with TN3270E...............................149 Printer Inventory Manager as Defined with TN3270E....150 Configuration Screens.........................................................159 10 AS/400 Configuration, TN5250 .............. 163 Setting Up TN5250 Print Queues on AS/400......................163 Setting Up a TN5250 Connection/Device via a Telnet Session ....................................................................164 User Supplied Values ....................................................165 Using Telnet Commands for TN5250..................................165 Command List................................................................165 Getting Started...............................................................166 TN5250 Job Formatting ......................................................167 Font Identifier (FONT) - Help ..............................................169 11 Monitoring Printers ................................. 171 Implementing Printer Management .....................................171 Agent/Manager Model....................................................171 MIB.................................................................................172 SNMP.............................................................................173 Monitoring Tools..................................................................173 Monitoring with AIX NetView/6000.................................173 PrintNet Enterprise Suite................................................174 Setting the SNMP Community Name.............................174 Disable SNMP Protocol..................................................174

12 Commands............................................. 175 Command Shell Overview...................................................175 npsh Access Methods....................................................175 Main npsh Command Prefixes.......................................176 Getting Command Help..................................................176 Complete Command List.....................................................177 Store Commands ...........................................................177 Set Commands ..............................................................187 List Commands ..............................................................197 Miscellaneous Commands.............................................199 13 Extra Features........................................ 203 PrintNet Security .................................................................203 Users and Passwords ....................................................203 Reset the PrintNet Password.........................................205 TCP Access Lists...........................................................205 PrintNet Naming Schemes..................................................207 Periodic Ping .......................................................................207 A Troubleshooting Tips.............................. 209 Windows Troubleshooting Tips ...........................................209 Technical Support ..........................................................209 PrintNet cannot be Found on the Network.....................210 HTML Configuration Forms will not Display...................210 Errors Occur when Defining an LPR Printer ..................211 Cannot Browse the PrintNet on the Network .................211 Printer Errors when Printing or No Output .....................212 TCP/IP Access Problem.................................................212 Web Browser/HTTP Problem.........................................213 Windows NT 4.0 or 2000 Host Setup Problems.............214

Unix Troubleshooting Tips ..................................................216 PrintNet Cannot be Found on the Network ....................216 Nothing Prints ................................................................217 Stair-Stepped Output .....................................................218 No Form Feed or Extra Page Comes Out......................219 Front Panel Message – Dynamically Set Params Read Only ......................................................................219 B Customer Support .................................. 221 Printronix Customer Support Center ...................................221 Printronix Supplies Department ..........................................222 Corporate Offices ................................................................222 C Glossary ................................................. 225

features, as well as providing information on installation and configuration tools. What is the PrintNet? PrintNet adds 10/100 network interface to Printronix printers. Network settings can be configured through the printer's control panel, telnet, or webpage. What Special Features are Available? PrinNet offers an extensive list of features including: • built-in HTML forms for easy cross-platform configuration • availability of PrintNet® Enterprise, a remote management software utility • a detailed and easy-to-use command shell built-in to the firmware • multi-level configuration security through passwords, permission levels, and access lists • WAN-wide communication access • numerous printer logging methods (e.g., automatic email) to record printer errors and usage

commands, SNMP, and pre-defined log methods • extensive built-in troubleshooting tools • built-in telnet and ping clients • protocols can be individually disabled • multiple destinations/queues for versatile printer manipulation and distinct print setups • header and trailer strings to instruct printers on font, pitch, printing, etc. • flexible naming conventions • automatic network connection and frame type sensing • simultaneous printing across all I/O ports and all supported protocols • multiple network protocol support

PrintNet provides a logical printer architecture which gives the system administrator the possibility to configure the print server to handle and act upon the print data in several ways. When a print job comes through the print server, there is a certain logical print path that it follows before it gets to the printer. Each logical print path consists of a sequence of logical steps where extra processing may be performed on the print data before it is sent to the printer. This ability to preprocess the print data before it is sent to the printer allows elimination of certain printing problems, or implementation of printer enhancements that may be difficult and time consuming to solve or introduce at the system, spool or queue level. The preprocess ability is also simplistic to perform at the print server level. The logical print path for a print job going through PrintNet consists of three different phases: • Phase 1 - the host sends the job to a destination or queue on PrintNet (e.g. d1prn). • Phase 2 - the print job passes through the associated “model” (e.g. model “m1”) on PrintNet for any extra processing associated with the model. • Phase 3 - the processed print job is directed to the printer for output.

18 Figure 1. Print Path Phase 1 Phase 2 Phase 3 Host Destination 4 (d4prn) Destination 2 (d2prn) Destination 3 (d3prn) Destination 1 (d1prn) Model 1 (m1) Model 2 (m2) Model 3 (m3) Model 4 (m4) Printer Destination 8 (d8prn) Destination 6 (d6prn) Destination 7 (d7prn) Destination 5 (d5prn) Model 5 (m5) Model 6 (m6) Model 7 (m7) Model 8 (m8)

logical print queue or destination to accept print jobs destined for it. This includes print jobs that are sent directly to the I/O port, such as port 9100. These queue or destination names are pre-defined but can be changed by the user. Models For every destination or queue, there is a pre-defined model associated with it. The model defines how the print job will be processed as it passes through to the printer. Models are a set of mini filters that can be used to modify the print data stream. The functions available for each model are as follows: 1. Insert carriage return after line feed 2. Insert a banner page before or after each print job 3. Insert header strings 4. Insert trailer strings 5. Log one or all of the following information as each print job passes through the model • Job ID and username • User ID and three messages per job about the start and finish • Miscellaneous messages from the printer • Status of the printer based on the port interface signals

job • Specify a printer configuration to be associated with a print queue. • When a job is sent to that print queue, the associated printer configuration will be loaded before the job is processed. • Feature allows you to define up to eight unique and independent printer personalities in a single printer. • Allows you to effectively have eight virtual printers in one. Interfaces The Ethernet interfaces with the host printer through an Ethernet 10/100Base-T interface connector. PrintNet is enabled with a security element. PrintNet Card LED Table 1. PrintNet LED Indicator NET Indication Description ON flashes Indicates activity OFF constant Indicates that the link is good at 10 Mbps ON constant Indicates that the link is good at 100 Mbps

21 Speed Setting for 10/100Base-T When the router is set to auto-negotiation enable, the following is the correct behavior of the PrintNet with each setting: 1. 10mbps Half Duplex Use parallel detection because the PrintNet is using force mode and thus has auto-negotiation disabled. PORs to 10mbps Half Duplex. Resets to 10mbps Half Duplex. Reconnection at switch maintains 10mbps Half Duplex. 2. 10mbps Full Duplex Use parallel detection because the PrintNet is using force mode and thus has auto-negotiation disabled. PORs to 10mbps Full Duplex. Resets to 10mbps Full Duplex. Reconnection at switch maintains 10mbps Full Duplex. 3. 100mbps Half Duplex Use parallel detection because the PrintNet is using force mode and thus has auto-negotiation disabled. PORs to 100mbps Half Duplex. Resets to 100mbps Half Duplex. Reconnection at switch results in 100mbps Half Duplex. 4. 100mbps Full Duplex Use parallel detection because the PrintNet is using force mode and thus has auto-negotiation disabled. PORs to 100mbps Full Duplex. Resets to 100mbps Full Duplex. Reconnection at switch results in 100mbps Full Duplex. 5. PrintNet in Auto mode in 100mbps Full Duplex environment Use auto negotiation to the highest common local and remote capability, i.e. 100 mbps Full Duplex in this case. PORs to 100 mbps Full Duplex. Resets to 100 mbps Full Duplex. Reconnection at switch remains 100 mbps Full Duplex.

22 6. PrintNet in Auto mode in 10mbps Half Duplex environment (determined using 10 mbps Half Duplex hub) Use auto-negotiation to the highest common local and remote capability, i.e. 10 mbps Half Duplex in this case. PORs to 10 mbps Half Duplex. Resets to 10 mbps Half Duplex. Reconnection at switch maintains 10 mbps Half Duplex. NOTE: With parallel detection, only speed can be determined. The duplex mode sets to half duplex. Conventions Used in this Manual All uppercase print indicates control panel keys. Example: Press the CLEAR key, then press the ONLINE key. Quotation marks (“ ”) indicate messages on the Liquid Crystal Display (LCD). Example: Press the ONLINE key. “OFFLINE” appears on the LCD. Command syntax and examples are formatted as follows: • The Courier font in boldface indicates commands that you type. For example: At the prompt, type: ping ftp.CompanyWebsite.com • Regular Courier font indicates references to command syntax and output. For example: The ftp.CompanyWebsite.com site is working properly. • Variable values are shown in italics in command syntax, output, and in text. For example: ping ipname The ipname is working properly.

For your safety and to protect valuable equipment, read and comply with the notes included in this manual. A description follows: NOTE: A Note gives you helpful information and tips about printer operation and maintenance.

10/100Base-T (UTP) networks. Print a test page to confirm that the Ethernet is installed. Contact your service representative if the Ethernet is not installed. Connecting to the Network To attach the PrintNet to a network, plug the network cable into the RJ-45 connector. Configuration Tools There are two parts to a PrintNet setup: • Configuring the PrintNet so it can be seen on the network. This involves network-related settings (e.g., an IP address within TCP/IP environments) configured through the built-in command shell, npsh, or from the control panel. • Configuring a host with a new printer so it knows how to send data to the PrintNet. Just being able to see the printer on the network does not mean you can automatically print to it. A host has to be told where to send the data.

settings to be configured on the PrintNet. However, all network setups require configuration on the host end. The following methods are available for configuring the Ethernet: • via the control panel • HTML forms • Telnet • PTX_SETUP Printing an Ethernet Test Page Always print an Ethernet Test page before performing any updates or network configuration. Refer to the User’s Manual for instructions on printing a test page. PrintNet Verification Before performing the verification, you must connect PrintNet to the local area network. 1. Print an Ethernet Test page to verify the settings you selected. 2. Verify the network setting is correct.

standard Web browser. The PrintNet Web pages provide a way to access some of the commands built into the print server. NOTE: If a router is used, make sure a Gateway value is configured. To access the PrintNet home page: 1. Make sure the print server has an IP address and Subnet Mask so it is recognizable on your TCP/IP network. 2. Make sure your network station can successfully ping the PrintNet over the network. 3. Direct your Web browser to the URL http://IPaddress (e.g., http://192.75.11.9) where IPaddress is the IP address of your PrintNet. See “PrintNet Web Server” on page 29 for details. Besides the HTML forms and software provided, the PrintNet internal command shell, npsh, can also be reached using Telnet, FTP, and Data Stream:

remotely. A TCP/IP host starts a Telnet session with the print server and logs into the device command shell to alter and view settings. Example: telnet 192.75.11.9 NOTE: The default User ID is root. There is no password by default, just press ENTER. If you have changed the default User ID and password, use the current User ID and the associated password instead of the defaults. For more information on setting passwords, see “PrintNet Security” on page 203. Setup through Data Stream The PTX_SETUP command can also be used to configure PrintNet settings through a printer data port (serial, parallel, or network etc.). This is done by creating a text file containing the PTX_SETUP command and PrintNet internal command shell (npsh) commands. The text file is then sent to the printer through a data port to perform the PrintNet configuration. The following is an example of a PTX_SETUP file that can be used to configure the PrintNet: !PTX_SETUP NIC_SETUP store net 1 addr 190.168.2.11 END_NIC_SETUP PTX_END

Overview The PrintNet comes with a printer management tool that allows you to monitor, configure, and manage both the printer and its print job. The PrintNet comes with a web server that allows System Administrators and users access to its printer management capabilities from a standard web browser. The PrintNet printer’s IP address is used as a URL, similar to the URL of an Internet web page. When a web browser is activated and the printer’s IP address is entered, the printer’s embedded web server displays its home page, with links to the printer’s status and configuration settings. All of PrintNet's configuration settings are protected by a password so unauthorized users cannot make changes. When you try to open any of the PrintNet 's configuration pages, you are asked for your user name and password. At the prompt, you need to enter root (unless you have another user configured with root privileges) followed by the associated password. If there is no password, just press ENTER. For more information on setting passwords, refer to “PrintNet Security” on page 203. After you configure the PrintNet settings, and click the SUBMIT button on the related form, re-power the PrintNet to ensure the latest settings are in use. To reset the PrintNet, go to the System form under the Configuration Menu and click the REBOOT button. The embedded PrintNet HTML server gives you the ability to configure the network setting, printer operation, monitor printer status, and to manage print jobs. The PrintNet Web page structure is divided into several menus.

The main page is divided into three major sections: Configuration, Printer Status, and Print Server. The Printer Status and Print Server sections display on the right side amongst other pages. Configuration This area allows the user to configuration the printer and network settings. The user can click each link to go to page options. Printer Status This area displays the printer type and information, control panel display, and printer state. The user can click “State” to change the printers between Online and Offline mode. Print Server This section shows PrintNet information and active print jobs.

for the following items: • Printer - this menu item allows you to configure the printer. You can change the printer’s form size, character set, and emulation settings. You can also load/save configuration files, print configurations, and manage file systems. • Network - this menu item allows you to change the TCP/IP network setting over TCP/IP. • Print Path - this menu item allows you to change the name of the destination queues, and define how the print job will be preprocessed before printing. It allows you to select what information to log. • Print Model - this menu item allows you to specify the print model name. It also allows you to select banner page types, filters, header and trailer strings, and printer configurations. • Log Path - this menu item allows you to specify the logpath name, type, and destination. • TN5250/3270 - this menu item allows you to configure the TN5250/3270 settings if TN is enabled in the printer. • SNMP - this menu item allows you to configure the SNMP trap manager settings. It also allows you to define the printer event types to monitor, and the e-mail address that should receive alert notifications. • Administration - this menu item allows you to define or change the printer name, location, description, etc.. It also allows you to change the root and guest user passwords, and to specify the SMTP server’s IP address. • System - this menu item allows you to reboot the printer, restore its settings to the factory default, upgrade printer firmware, and capturing the print data.

Configuration, Configuration Management, and File Management. Printer Configuration The Printer Configuration page allows the user to set up print format, host communication, emulation settings, etc.. For descriptions on each option, refer to the printer’s User’s Manual. Figure 3. Printer Configuration Webpage

display printer configurations. For descriptions on each option, refer to the printer’s User’s Manual. Figure 4. Configuration Management Webpage

file system. This webpage has the following functionalities: • Delete - allows you to delete a file using ‘Delete’ link. • Upload – allows you to upload a file stored in the printer. Upon completion of upload, you are prompted to select which application to use for bringing up the data (see Figure 6 on page -35). • Download – allows you to browse for a file and load it to the printer. • Overwrite Files – allows you to protect the files stored in the printer by setting the Overwrite Files option to Disable. • View File List – click this link to view a list of files in the printer. • Optimize&Reboot – removes the deleted files from the flash and reboots the printer. Figure 5. The File Management Webpage

network protocol. Beside each protocol name is a checkbox which allows you to enable or disable each protocol depending on your network printing needs. NOTE: TCP/IP is the only supported protocol which is always enabled. TCP/IP Network Figure 7. TCP/IP Network Configuration

mask, and Gateway. The check boxes enable the BOOTP, DHCP, and Persistent DHCP protocols, which are alternate methods of assigning IP addresses. On most networks, you want to enter a permanent IP address and subnet mask and disable BOOTP and DHCP. However, if your network requires one of these, you should clear the IP address (and possibly the subnet mask) fields and ensure that the appropriate check box is selected. Figure 8. TCP/IP Static Route

38 Routing The routing table tells the PrintNet which router or gateway to use to access other subnets or hosts. In most situations, you can simply add your router's IP address as the default router. All packets destined for other subnets will be forwarded to the default router for delivery to the destination host. If you have more complex routing requirements, add static routing entries for specific hosts or networks in the remaining Routing rows. Packets with IP addresses that match a given Destination and Mask (from the first two fields in a Routing row) will be routed to the router/gateway named in the third field. Packets which do not match any of the listed Destinations and Masks will be routed to the default router if one is set. Print Path Configuration The PrintNet print path is the path a print job takes when it reaches the printer's Ethernet interface. First the job goes to a destination/ queue (e.g. d1prn) where it then passes through an associated model (e.g. m1) for extra processing and logpath (e.g. l1) for job and printer logging. Finally the job reaches printer's data parser. The "Print Path" Webpage displays one destination's settings at a time. From here, you can then select another destination or you can go directly to an I/O port to configure port settings.

40 Name Name of the destination. The default destination queue names are d1prn, d2prn, d3prn, d4prn, d5prn, d6prn, d7prn, and d8prn. The destination name can be modified by entering a new name in the field and clicking “Submit”. Back Channel I/O port to receive printer feedback when a print job passes through this destination. By default, the backchannel for all print queues is enabled. Services Define what type(s) of print services the destination will support. By default all services enabled. Selected Model Defines the model configuration that is to be associated with the current destination. The default model names are m1, m2, m3, m4, m5, m6, m7, and m8. Selected Logpath Defines the logpath configuration associated with the current destination. The default logpath names are l1, l2, l3, l4, l5, l6, l7, and l8. Parameter socket Printing to a TCP port number (e.g. 9100) on the PrintNet lpd Remote printing using the Line Printer Daemon ftpd printing using the File Transfer Protocol (FTP)

41 Chosen Model Settings This section displays the model associated with the displayed destination. To change Print Model settings, see “Print Model Configuration” on page 41. Chosen Logpath This section displays the logpath setting associated with the displayed destination. To change Log Path settings, see “Log Path Configuration” on page 44. Print Model Configuration Figure 10. Print Model Configuration, Model Settings Name Name of the model. The default model names are m1, m2, m3, m4, m5, m6, m7, and m8. The model name can be modified by entering a new name in the field and clicking “Submit”.

42 Banner Page Tells the Ethernet Interface to produce a banner page with each print job. The type of banner page data can be text. You can also specify whether the banner page should come at the front or the end of a print job. Filter Specify whether the Ethernet Interface is to add carriage returns to print jobs passing through that contain solitary linefeeds. This is common with Unix text jobs resulting in stair-stepped output. Header String Define an escape sequence to be sent to the printer before each print job. For example, you may want to send a sequence to print the job in landscape mode. You can specify up to four separate sequences per header string. The Ethernet Interface will execute them in order from top to bottom. If specifying fewer than four sequences, be sure to start at the top leaving undefined fields at the bottom. Trailer String Define an escape sequence to be sent to the printer after each print job. For example, you may want to send a sequence to add a formfeed so you don't have to manually press the formfeed button on the printer. You may also want to tell the printer to reset itself in case you have set a header string which tells the printer to do something special with the job. You can specify up to three separate sequences per trailer string. The Ethernet Interface executes them in order from top to bottom. If specifying fewer than four sequences, be sure to start at the top leaving undefined fields at the bottom. The most common sequence is listed on the form: • Formfeed - tells the printer to do a formfeed at the end of the data. See page -190.

processing the print job. This ability to associate a printer configurations to a logical printer model allows you to define up to eight unique and independent printer personalities in a single printer. Using this feature, you effectively have eight different printers in one. To associate a printer configuration to the currently selected destination queue, just select the desired printer configuration number from the drop down list. Once a printer configuration has been associated with a destination queue, any print job sent to that destination queue name will cause the printer to load the associated printer configuration before processing the print job.

44 Log Path Configuration Figure 11. Log Path Settings Name Name of the log path. The default names are l1, l2, l3, l4, l5, l6, l7, and l8. The Log Path name can be modified by entering a new name and clicking “Submit”. Logpath Type Define what type of log information will be tracked for each print job passing through the associated destination. The types are: • Print Job Started - A notification is sent to 'Destination' when a print job is received in the PrintNet. • Printer Error - A notification is sent to 'Destination' when a printer error occurs during printing. If no print job exists in the PrintNet, the notification will not be sent.

associated destination will be reported. The choices are: • None (default) - do not report any logging information • Email - to an e-mail address (SMTP server address is set in the Administration page) • UDP Syslog - to a host (specified by the IP address in the edit field) running a SYSLOG daemon • TCP/IP port - to a TCP port number.

for up to eight different TN5250/3270 sessions. NOTE: The standard Printronix PrintNet module does not support TN5250/3270 protocol. However, the TN5250/3270 software is available as an option you can order or as factory installed. Figure 12. TN5250/3270 Configuration, TN5250 Mode

Mode Specifies the TN protocol mode for the current configuration. Default: TN5250 Host IP Specifies the IP address or domain name of the host (AS/400 for TN5250) for the current configuration. Default: Unconfigured (empty) host. Port Specifies the UDP port number of the TN5250 or TN3270 server for the current configuration. Default: 23

the current configuration. The resource name entered will be the name of the printer device created on the AS/400 host for the current session. The name is limited to 10 characters in length, must start with an alpha character (a-z, A-Z), and contain only alphanumeric characters and underscores. Default: Unconfigured (empty) resource name Device Description (TN5250 mode) Specifies the name of the printer device for the current configuration. The description entered will be the name of the printer device created on the AS/400 host for the current session. The name is limited to 10 characters in length, must start with an alpha character (a-z, A-Z), and contain only alphanumeric characters and underscores. Default: Unconfigured (empty) description Message Queue Name (TN5250 mode) Specifies the queue name to which system messages will be logged. Default: QSYSOPR Message Queue Library (TN5250 mode) Specifies the queue library to which system messages will be logged. Default: *LIBL

WSCST Name (TN5250 mode) As declared on the AS/400 host for the created printer device. Default: *NONE WSCST Library (TN5250 mode) As declared on the AS/400 host for the created printer device. Auto Connect Specifies whether the PrintNet will automatically connect to the host. Default: Disabled Start/Stop Auto Connect Specifies whether the PrintNet should retry automatic connection to the host. Default: 'Start' if Auto Connect is currently stopped, 'Stop' if Auto Connect is currently started.

managers and the e-mail alert features of PrintNet. It allows you to configure how SNMP alerts are processed by a SNMP trap manager, a Unix syslog logging daemon, and/or have e-mail notifications sent. Up to 10 SNMP trap managers and e-mail recipients may be specified. Individual alerts fall into one of 14 alert group categories, providing the ability to filter alert notices as desired. SNMP Manager Alert Posting Settings Figure 14. SNMP Manager Alert Posting Configuration Specifies whether alerts from the enabled alert group categories for this configuration will be sent to the SNMP manager. If this option is enabled, the following information must be entered: • SNMP Manager IP Address - specifies the IP address of the SNMP trap manager • UDP Port - specifies the UDP port number used by the SNMP trap manager for receiving trap messages. Acceptable values are 162 and 49157 through 65535 • Community Name - up to 15 character string specifying the trap community name.

Figure 15. SNMP Syslog Alert Posting Configuration Specifies whether alerts from the enabled alert group categories for this configuration will be sent to the Unix syslog daemon. If this option is enabled, the syslog daemon IP address must be entered in the syslog field in the System Information section of the Administration Configuration form. Default: Disabled E-mail Alert Posting Settings Figure 16. SNMP Email Alert Posting Configuration

this configuration will be sent to the specified e-mail address. If this option is enabled, the following information must be entered: • E-mail Address - specifies an e-mail address to which alert information will be sent • Short E-mail Format - specifies whether a short (15-80 character) alert e-mail message should be sent. If enabled, the message will contain the alert description, the severity level, device description, and device name (unless the length of the message exceeds the Short E-mail Message Length, in which case the message will be truncated). If disabled, the message will contain additional information including the device description, device name and location, alert description, alert group, alert severity level, and printer status. Default: Disabled • Short E-mail Message Length - Specifies the maximum size of the short e-mail message. Acceptable values are 15 to 80 characters. Default: 80 characters • Send Test Message - Provides a way to test the validity of the e-mail address/SMTP server address. If checked, a test message will be sent to the specified e-mail address when the submit button is pressed. Default: All alert groups are disabled by default. If the alert message is to be sent to a cellular phone or pager, the Short E-mail Format option should be enabled. Once this option is enabled, you may specify the maximum e-mail message length (15-80 characters). When enabled, the message will contain the alert description, the severity level, device description, and device name (unless the length of the message exceeds the Short E-mail Message Length, in which case the message will be truncated).

additional information including the device name and location, alert description, alert group, alert severity level, and printer status. To test the validity of the e-mail address and the SMTP server address, enable the Send Test Message option. If the Send Test Message box is checked, a test message will be sent to the specified e-mail address when the submit button is pressed. Alert Groups Figure 17. SNMP Alert Groups Configuration

configuration. When an alert occurs that is contained in one of the enabled alert groups, it will be posted to the specified SNMP manager, Unix syslog daemon, and/or e-mail address. The following table describes which printer events belongs to which Alert Group. Default: All alert groups are enabled by default. Table 2. Alert Groups and Printer Events Alert Group Printer Events Warning File System Full File Exist Hex Dump Mode Half Speed Mode Offline Printer is Offline Media Input Load Paper Media Output Stacker Full Stacker Jam Time Out Stacker Full Time Out Stacker Fault Time Out Stacker Jam Stacker Fault Stack Over Flow8 Stack Under Flow Stacker Fail Stacker Interlock Fail Stacker Not Ready Media Path Clear Paper Jam

alerts available for monitoring will depend on the printer type and the options installed on the printer. Marker Ribbon Stall Time Out Ribbon Ink Out Ribbon Stall Ribbon Drive Shuttle Over Speed Ribbon Fault Ribbon Detected Ribbon Broken Barcode Barcode Fail Specification Barcode Quiet Zone Too Small Barcode Improper Data Format Intervention These are error messages that need some kind of user intervention to solve them. Consumable Ribbon Low Table 2. Alert Groups and Printer Events Alert Group Printer Events

print server-related settings and password security. System Information Figure 18. Administration Configuration, System Information The System Information form allows you to specify the following information about the printer: Name Name given to the print server in Windows environment. The default name is “P_xxxxxx” where "xxxxxx" equals the last six digits of the PrintNet’s Ethernet address. (e.g. P_01001C). The user can change the printer name in this field. Location Optional field to help identify the printer’s physical location.

the printer. Printer Serial Number Allows the user to enter the printer’s serial number. If the printer's controller board is replaced, this field will be blank. The service representative can enter the printer's serial number in this field. SMTP Server Specifies the IP address or domain name of the SMTP server to be used for processing email messages generated by the PrintNet. Default: Unconfigured (empty). TCP Services There are two protocols that users can disable. Usually major corporations prefer to disable ftp and telnet once configuration of the printer is complete. ftp and telnet protocols are set to enable by default. If these protocols are disabled, you can use the Webpage to enable them. If HTTP protocol is disabled along with ftp and telnet, the only way to enable these protocols is by sending a print job with PTX_SETUP commands. (Refer to printer’s User's Manual for PTX_SETUP syntax.)

Only a user with root privileges can alter the PrintNet's settings. Guest users can only view settings but cannot alter them. Both types of users can be assigned passwords. To change a password, type in the old password in the "Old" field. Then type the new password twice: once in the "New" field, and once in the "Confirm" field. Default: No passwords for root or guest users.

The System Configuration form allows you to change the PrintNet's operation mode. Select "Reboot" to re-power the print server. Select "Default" to reset the print server and have it come up with factory default settings.

Upgrade webpage displays below. Figure 21. Firmware Upgrade Webpage 1. To find the upgrade file click the Printronix Customer Support Center link. 2. Click “Browse...” to navigate to the directory, then click “Upgrade”. NOTE: Upgrading the printer firmware will erase all printer configurations except network setting. You may want to upload the configuration and save it to your PC before the upgrade process. IMPORTANT The upgrade process may take a few minutes. The process cannot be interrupted during upgrade or the printer will not be able to power up again.

Sometimes the job does not work or your barcode does not print. Job Capture allows you to capture data sent to the printer. To start capturing data, click “Start Job Capture”. To stop capturing data, click “Stop Job Capture”. Upon job capture completion, click “Upload” to load the data from the printer to your host system. The captured file size depends on your available DRAM size. Status The Status menu items allow you to view the current status of both the printer and the network. The submenu items available are as follows: • I/O Port - this menu item allows you to view the current status of the printer, including the print jobs that are queued or are currently active. • Network - this menu item allows you to view the current status of the network connection.

62 Status - I/O Port The I/O Port Status form allows you to remotely see what is happening on the PrintNet I/O port. The port's status and a list of active and queued jobs will be displayed. You can cancel a job (as long as you have permission) by clicking the Cancel icon beside the desired job. If you see "waiting" in the "Status" line, this indicates the PrintNet is either waiting for data from the host or for feedback from the printer. If you see "blocked" in this line, this indicates the printer is not allowing the PrintNet to send any more data. The printer could be busy processing data it has already received or it could be in an error state. The printer status display is automatically refreshed every minute. NOTE: You cannot cancel a print job with an IPDS Emulation. Do not click the Cancel icon. The printer’s buffer size may not allow you to monitor the real time status of the printer and the print job at the same time. The status feedback to the host usually reads “printer idle” unless the print job is significantly large. Status - Network This form allows you to view the current status of the network. The statistical data provided is broken down by network protocol. You can use this form to troubleshoot network-related problems. Help Through the provided HTML forms, you can configure settings on the Integrated PrintNet Enterprise and view printer status.

including: • Identifying the PrintNet on the network using TCP/IP as the underlying protocol • Configuring the PrintNet with its mandatory TCP/IP settings (IP address and subnet mask) • Configuring a new printer on the Windows station Windows Environment Description The PrintNet supports network printing under Windows environments by using TCP/IP. In a Windows setup, pure TCP/IP is used as the network protocol.

64 Windows PrintNet Configuration The IP address and subnet mask are mandatory TCP/IP settings and are needed before the print server can be detected on the network. There are also additional optional settings. This section offers alternative methods for configuring your PrintNet in a Windows environment and describes some of the more common optional settings available. Mandatory Since TCP/IP is used for Windows printing, the PrintNet must be configured with a minimum of an IP address and subnet mask before it can be seen on the network. Optional Additional settings, like routing entries, can be configured. This allows communication across subnets when no other router exists. You can configure the PrintNet from the printer control panel, Web browser, host commands, or other Printronix utility software. To configure these options, see “Configuration Tools” on page 25. Configuration using ARP To configure the PrintNet with its IP settings using a manual arp command: 1. Log on to a Windows station with TCP/IP loaded and located on the same subnet as the PrintNet. 2. Find the Ethernet address for the PrintNet on the configuration printout. It must be entered as part of this procedure.

65 3. Use the arp command to add an entry into the Windows station ARP table for the PrintNet. This is the most common syntax for this command: Syntax: arp -s ipaddress ethernetaddress Example for Microsoft® TCP stacks: arp -s 192.75.11.9 00-08-96-07-00-60 This example specifies a PrintNet using IP address 192.75.11.9 and Ethernet address 00-08-96-07-00-60. 4. Check if the ARP entry was accepted. arp -a You should see an entry in the listed ARP table with the IP address and Ethernet address specified in Step 3. 5. Ping this IP address to see if the PrintNet can be seen on your network. At this point, you should be able to communicate with the PrintNet from your local Windows station. This means the print server knows about an IP address and subnet mask and has these settings in its current memory. However, if the PrintNet is power cycled, these settings will disappear unless you store them into flash memory. To do this: a. Load a Web browser on your Windows station and direct it to the URL: http://IPaddress (e.g., http://192.75.11.9) where IPaddress is the IP address of your PrintNet. NOTE:If prompted for a “User ID” and password first, type root for the ID and press ENTER at the password prompt (since there is no password by default). b. At the “Network Configuration” HTML form that displays, click in the field below the “IP Address” heading and type in the IP address for the PrintNet.

66 c. Under the “Subnet Mask” heading, enter the PrintNet subnet mask. NOTE:If you would like to communicate with the PrintNet from across routers, you will need to fill in an entry within the “Routing” section. Please see “Communicating Across Routers” on page 66 for more details. 6. Click on the SUBMIT button when done and physically repower the printer to make the new settings take effect. Communicating Across Routers Since Windows environments rely on TCP/IP to communicate with the PrintNet, crossing routers becomes an issue. After you have followed one of the PrintNet configuration methods mentioned, most likely you will only be able to communicate with the print server from the same subnet. This means any hosts across a router will not be able to see your PrintNet. In order for hosts across a router to see your PrintNet, store a default router/gateway within the print server so that any packets destined for another subnet get forwarded to this router automatically. The router (or series of routers) can then take over, ensuring the packets get to their final destination on another subnet on your network. To configure a default router/gateway within the PrintNet: 1. Load a Web browser on your Windows station and direct it to the URL. NOTE: If prompted for a “User ID” and password first, type in root for the ID and press ENTER at the password prompt (since there is no password by default). 2. At the “Network Configuration” HTML form that displays, click in the first field below the “Gateway” heading and type in the IP address of the default router/gateway for the PrintNet subnet. 3. Click on the SUBMIT button when done and physically repower the print server to make the new settings take effect.

67 Changing Destination Names When defining some printers within Windows environments, the PrintNet requires that you specify a predefined destination rather than any name you would like. For example, when creating a new printer under Windows NT, a screen similar to Figure 23 displays. Figure 23. Windows NT Print Setup Dialogue Box The first field requires the IP address for the PrintNet, and the second field must be filled in with a valid destination from the print server (e.g., d1prn). Otherwise, LPR will not be able to access the printer. This name can be changed to something more meaningful using the built-in HTML forms. To do this: 1. Load a Web browser on your Windows station and direct it to the URL: http://NICIPaddress/destConf.html (e.g., http://192.75.11.9/networkConf.html). NOTE: If prompted for a “User ID” and password first, type in root for the ID and press ENTER at the password prompt (since there is no password by default).

68 2. At the “Print Path Configuration” HTML form that displays, select a destination link from the top of the page to bring up the appropriate destination form. By default, you should see a line near the top of the form showing the destinations. 3. Once the desired destination HTML form displays, highlight the “Name” field and type in the new name for this destination. 4. Click the SUBMIT button when done and physically repower the print server to make the new setting take effect.

• Configuring the PrintNet with its mandatory TCP/IP settings (e.g., IP address and subnet mask). • Configuring the Unix host station with a new printer. Unix Environment Description The PrintNet supports network printing under various TCP/IP environments including all variations of Unix. Printing can come from multiple hosts directly or through central spooling machines.

70 Unix PrintNet Configuration There are mandatory settings needed before the print server can be detected on the network, as well as some additional optional settings. This section offers alternative methods for configuring your PrintNet and mentions some of the more common optional settings available. Mandatory Since TCP/IP is used, the PrintNet must be configured with a minimum of an IP address and subnet mask before it can be seen on the network. To configure these options, see “Configuration Tools” on page 25. Optional Additional settings, like routing entries, can be configured allowing for communication across subnets. Configuration of the PrintNet can be done from the control panel or through host commands. To configure these options, see “Configuration Tools” on page 25. Using ARP To configure the Ethernet Interface with its TCP/IP settings using a manual arp command, the syntax is: arp -s ipaddress ethernetaddress For the aix command, the syntax is: aix -s ether ipaddress Mac_address To use either of these commands: 1. Log on to a Unix station as superuser or root. This station must be located on the same subnet as the PrintNet since ARP is limited to subnets.

configuration or reading it from the control panel. It must be entered as part of this procedure. 3. Use the arp command to add an entry into the Unix station ARP table for this PrintNet. Here is the most common syntax for this command: arp -s ipaddress ethernetaddress Example for Microsoft TCP stacks: arp -s 192.75.11.9 00:08:96:07:00:60 This example specifies a PrintNet using IP address 192.75.11.9 and Ethernet address 00:08:96:07:00:60. 4. Verify that the ARP entry was properly applied. arp -a You should see an entry in the listed ARP table with the IP address and Ethernet address specified in step 3. 5. Try to ping this IP address to see if the PrintNet can be seen on your network. At this point, you should be able to communicate with the PrintNet from your local Unix station. This means the printer knows about an IP address and subnet mask and has these settings in its current memory. However, if the PrintNet is shut off, these settings will be lost unless you store them in flash memory, as follows: 1. Load a Web browser on your Windows station and direct it to the URL: http://NICIPaddress/networkConf.html (e.g., http://192.75.11.9/networkConf.html). NOTE: If prompted for a “User ID” and password first, type in root for the ID and press ENTER at the password prompt (since there is no default password). 2. At the “Network Configuration” HTML form that displays, click in the field below the “IP Address” heading and type in the IP address for the PrintNet.

72 3. Under the Subnet Mask heading, enter the PrintNet subnet mask. NOTE: If you would like to communicate with the PrintNet from across routers, you will need to fill in an entry within the “Routing” section. Please see “Communicating Across Routers” on page 73 for further details. 4. Click the Submit button when done and physically repower the print server to make sure the new settings are in effect. Using BOOTP BOOTP allows you to dynamically assign an IP address to the PrintNet upon bootup. In addition, the BOOTP server can provide additional details like a default router/gateway address. To configure the PrintNet with its TCP/IP settings using BOOTP: 1. On your BOOTP server, make an entry in the /etc/bootptab file for the PrintNet. Syntax: IPname:\ :sm=netmask:\ :hd=homedirectory:\ :bf=null:\ :gw=defaultgateway:\ :ht=ethernet:\ :ha=ethernetaddress:\ :ip=ipaddress:\ :ts=timeserver:\ :to=timezone: Example: spike:\ :sm=255.255.255.0:\ :hd=/usr/null:\ :bf=null:\ :gw=192.75.11.1:\ :ht=ethernet:\ :ha=000896070060:\ :ip=192.75.11.9:\ :ts=192.75.11.7:\ :to=25200:

73 2. Turn the PrintNet on so that it immediately sends out a BOOTP request. Wait one minute to allow the IP address assignment process to complete. 3. Try to ping the PrintNet IP address from a network station to see if it can be seen on your network. NOTE: You will be able to communicate with the PrintNet from network stations on different subnets if the print server has been told about its default router/gateway in the BOOTP response from the BOOTP server. Communicating Across Routers Since Unix environments rely on TCP/IP to communicate with the PrintNet, crossing routers becomes an issue. After you have followed one of the PrintNet configuration methods mentioned (other than the BOOTP method), most likely, you will only be able to communicate with the print server from the same subnet. This means any host across a router will not be able to see your PrintNet. In order to communicate across a router, store a default router/gateway within the print server so that any packets destined for another subnet get forwarded to this router automatically. The router (or series of routers) can then take over the process of ensuring the packets get to their final destination on another subnet on your network. To configure a default router/gateway within the PrintNet: 1. Load a Web browser on your Windows station and direct it to the URL http://NICIPaddress/networkConf.html (e.g., http://192.75.11.9/networkConf.html). NOTE: If prompted for a User ID and password first, type in root for the ID and press ENTER at the password prompt (since there is no default password). 2. At the Network Configuration HTML form that displays, click the first field below Gateway and type in the IP address of the default router/gateway for the PrintNet subnet.

74 3. Click Submit when done and physically repower the print server to make sure the new setting is in effect. Unix Host Configuration There may be times when you would prefer or have to perform the manual setup steps for a new printer definition. There may also be times when you require a less common print solution such as direct socket capabilities. This section covers these additional setups. Manual System V Host Setup This setup involves any Unix operating system using System V print spooling (e.g., SCO, Solaris®, HP-UX®, DG/UX®, etc.). This means an interface file is used for each defined printer and, in the case of any System V print setup involving a PrintNet, the RSHD protocol is used to transfer data from the host to the print server. To manually configure a new System V printer on a Unix station, create a dummy device file that acts as a locking mechanism between contending print jobs. Syntax: touch /dev/NICname.portname where NICname is the host or IP name of the print server and portname is one of its four I/O ports. Example: touch /dev/spike.prn

LPR is supported in HP/UX Version 9.0 and greater. To configure a print queue using LPR, issue the following commands. NOTE: Requires root privilege. The default BSD interface file “rmodel” will be used. Syntax: lpshut lpadmin -pqueue_name -mrmodel -v/dev/null -orm[printer_ip] -orpd1prn -ob3 lpsched accept queue_name enable queue_name queue_name = any unique printer name [printer_ip] = IP address of the printer or the DNS name (without brackets) d1prn = PrintNet remote printer name* Explanation of command line: -m indicates the model rmodel -v indicates the use of /dev/null as a file interlock to avoid contention -orm is the name of remote Print Server -orp is the name of the remote printer on the remote Print Server -ob3 declares that the remote Print Server is a BSD type NOTE: The “lpshut” command stops the HP spooling system; do not perform when print jobs are active. The default PrintNet destination name is d1prn, however, this name can be changed. To verify the queue name, print an Ethernet Test Page or telnet to the print server’s IP address and run a “list dest” command.

76 To print to this queue, use normal lp syntax: # lp -dqueue_name filename Solaris 2.6 – 7 PrintNet Setup NOTE: Requires Superuser privilege in the borne shell. Assume that you can ping and Telnet to the adapter. The IP address of the PrintNet must be placed in the /etc/hosts file. Syntax: lpadmin -p [queue_name] -v /dev/null lpadmin -p [queue_name] -i /usr/lib/lp/model/ netstandard lpadmin -p [queue_name] -o dest=[host_name] -o protocol=bsd -o timeout=60 lpadmin -p [queue_name] -s [host_name]!d1prn -I any enable {queue_name] accept [queue_name] where [queue _name] = any name, but not the name in the etc/hosts file or d1prn [host_name] = name in etc/hosts file Troubleshooting This installation procedure assumes that the PrintNet is configured with the correct IP address, subnet mask, and gateway (if required). You can also ping and telnet to the PrintNet. Print an E-Net Test Page to verify the Ethernet settings. See “Printing an Ethernet Test Page” on page 26. The default PrintNet queue name is d1prn, however, the name can be changed. To verify the queue name, print an E-Net Test Page or telnet to the print server’s IP address and run a “list dest” command. NOTE: Depending on the shell, preceed the ! character with a \ to avoid shell script errors.

77 Manual LPR/LPD Host Setup The PrintNet also supports Unix operating systems which follow a BSD print system (e.g., SunOS 4.1.x). This means a printcap file is used to define all printers available on the host, and interface scripts are not commonly used. Instead, LPR/LPD printers are defined. To manually configure an LPR/LPD printer on a BSD Unix system: 1. Define an entry for this new printer within the printcap file, /etc/ printcap. Syntax: printername: :sh:pw#80:mx#0:\ :rm=NICname:\ :rp=NICdestination:\ :lp=:\ :sd=/usr/spool/lpd/printername:\ :lf=/usr/spool/lpd/printername/log:\ :af=/usr/spool/lpd/printername/acct: where printername is any name you would like to give to this new printer, NICname is the host or IP name of the print server, and NICdestination is one of the pre-defined destinations/queues on the device. Example: P5000: :sh:pw#80:mx#0:\ :rm=spike:\ :rp=d1prn:\ :lp=:\ :sd=/usr/spool/lpd/ P5000:\ :lf=/usr/spool/lpd/ P5000/log:\ :af=/usr/spool/lpd/ P5000/acct:

78 2. Create the spool directory specified by the sd= entry in the printcap entry for this printer. Example: touch /usr/spool/lpd/ P5000 3. Create the log and account files specified by the lf= and af= entries in the printcap entry for this printer. Example: touch /usr/spool/lpd/P5000/log touch /usr/spool/lpd/P5000/acct 4. Change permissions and ownership on the spool directory and everything within it. Example: chmod -R g+rwX,o+rX /usr/spool/lpd/ P5000 chmod -R daemon.daemon /usr/spool/lpd/ P5000 5. Start the printer daemon for this new printer. Example: lpc start P5000 You now have a new printer which relies on LPR/LPD to print to a PrintNet printer. Use the following command to test printing: Syntax: lpr -P printername filename Example: lpr -P P5000 /etc/hosts

79 PrintNet Configuration for AIX 4 Before you set up the printer, it is good to know the ways a print job can be filtered. 1. Standard processing. Filtering is done on the printer with no processing on the host. 2. Local Filtering. Filtering is done on the host. Be sure to specify the printer model during install. Standard Processing 1. Enter SMIT select devices. 2. Select Printer/Plotter. 3. Select Print Spooling. 4. Add a Remote Print Queue. 5. Set the type of Remote Printing to Standard processing. 6. Enter the following Remote printer settings: Name of queue any_name, user selectable Host Name of Remote Server name in /etc/hosts file or the PrintNet IP address Name of Queue on Remote Server d1prn Type of Print Spooler BSD (Press the list button and choose BSD)

80 Local Filtering 1. Enter smitty mkvirprt. 2. Add a Remote Print Queue. 3. Set the type of Remote Printing to Local Filtering... 4. Set the Printer Manufacturer to IBM. 5. Set the Printer Type to IBM4202. IMPORTANT You must change the printer emulation to Proprinter. 6. Enter the following Remote Print Queue with Local Filtering settings: Name of queue any_name, user selectable Host Name of Remote Server name in /etc/hosts file or the PrintNet IP address Name of Queue on Remote Server d1prn Type of Print Spooler BSD (Press the list button and choose BSD) Leave Pass-Through Flag Yes

81 Troubleshooting This installation procedure assumes that the PrintNet is configured with the correct IP address, subnet mask, and gateway (if required). In addition you can also ping and telnet to the PrintNet. To verify the PrintNet settings, print an E-net Test Page. See “Printing an Ethernet Test Page” on page 26. The default PrintNet queue name is d1prn (in lower case), however the name can be changed. To verify the queue name, print an E- Net Test Page or telnet to the print server’s IP address and do a “list dest” command. AIX Remote Queue Time–Out Setting Symptoms: Print jobs restart or queue goes down. If the queue is set up for standard processing (not local filtering), add -T50 flag to rembak to the queue device stanza for the queue in /etc/qconfig backend = /usr/lib/lpd/rembak -T50 If the queue was set up for local filtering edit the file /usr/lib/lpd/pio/etc/piorlfb and change the line; typeset piorlfb_rbflags=’’’’ to typeset priorlfb_rbflags=”-T50” Printing from AIX Version 4.0 and higher of AIX® offers LPR/LPD support for network printing. This means, to set up a new printer under this operating system, you only need to define these two parameters: 1. PrintNet IP address. The IP address or host name of the print server to which you want to print. 2. PrintNet destination/queue. A pre-defined name on the print server telling the device to which I/O port to send the jobs. Most likely, you will use d1prn for the PRN.

82 Printing with FTP Print jobs can also be sent to the PrintNet using the File Transfer Protocol (FTP). To do this: 1. On your network station, change to the directory containing the file you want to print. 2. Open an FTP session with the PrintNet. Syntax: ftp NICIPaddress 3. Log in as root. 4. At the password prompt, press ENTER (since there is no default password). 5. Change to the dest directory. Syntax: cd dest 6. List the contents of this directory using the dir command and determine which destination/queue you would like to send the print job through. Most likely, you will select d1prn for the PRN port. 7. Change to this destination directory. Example: cd d1prn 8. Change the mode to correspond with the type of file you are going to print. By default, ASCII is set for text-only files, but if you need to print both text and graphics, select binary using the bin command.

83 9. Place the file to be printed within this directory on the PrintNet, so it can be spooled and printed. Syntax: put filename 10. Close the FTP session, unless you have more jobs to print. Syntax: quit Alternate FTP Printing 1. Change the default ftp directory by entering the following command: store pserver ftp dest 2. Open an FTP session with the PrintNet. Syntax: ftp NICIPaddress 3. Log in as root. 4. At the password prompt, press ENTER (since there is no default password). 5. Change the mode to correspond with the type of file you are going to print. By default, ASCII is set for text-only files, but if you need to print both text and graphics, select binary using the bin command. 6. Send the file to be printed here. Syntax: put filename d1prn 7. Close the FTP session, unless you have more jobs to print. Syntax: quit

84 Direct Socket Printing Within TCP/IP environments, there are some setups which require the host to print directly to a TCP port number on the PrintNet, bypassing all of the higher level destination/queue names. If you run into a setup which requires this, you will need to define two parameters for a new print setup: 1. PrintNet IP address. The IP address or host name of the print server to which you want to print. 2. PrintNet TCP port number. A predefined number for the I/O port on the print server. 9100 is the default port number. Though the host will be sending directly to a TCP port number on the PrintNet, the port numbers are still mapped to destinations/ queues in case there is some type of special processing or logging to be done to the job. However, the destination name is of no concern in this type of printer definition. Only the two parameters mentioned above need to be defined for printing to work.

matrix network printer. To print IPDS files, you must have the IPDS option on the printer. Requirements Verify that you have the following required software: • PSF Version 2.2.0 with APAR OW15599 (for TCP/IP support) • z/OS Scheduler with APAR OW12236 to support two new PRINTDEV keywords: IPADDR and PORTNO • TCP/IP Version 3 Release 1, or higher, installed and configured on z/OS To obtain the PTFs associated with these APARs, contact the support center.

86 Configuration Checklist All of the following configuration steps carried out on z/OS require appropriate RACF authority. 1. Set TCP/IP addresses for the printer, such as IP address, gateway address, or subnet mask. See “Configuration Tools” on page 25. 2. Configure the host environment. See “Configuring PSF for z/OS to Print IPDS Files” on page 86. 3. Verify the configuration. See “Verifying a TCP/IP-Attached Printer on z/OS” on page 96. 4. If you want to share the printer, do the procedure in “Sharing Line Matrix Printers on z/OS” on page 97. 5. If you have problems, refer to “Handling z/OS Connectivity Problems” on page 99. Configuring PSF for z/OS to Print IPDS Files To perform this procedure, you need the IP address of the Ethernet. Configuration Procedure Configuring PSF to print IPDS files includes the following steps: 1. Define the z/OS communications control unit to z/OS. See “Define the Communications Control Unit to z/OS” on page 87. 2. Modify the TCP/IP profile on your z/OS system, if necessary. See “Modify the TCP/IP Profile in z/OS” on page 87. 3. “Ping” the printer. See “Verify the Printer Connection” on page 90. 4. Define the printer as a writer-controlled printer to JES. See “Define the Printer to JES” on page 91.

including the IP address. See “Define the Printer to PSF” on page 92. This section does not provide all the information you need to install and configure TCP/IP on your z/OS system. For more information on installing TCP/IP, refer to TCP/IP for z/OS: Customization and Administration Guide. The routing of information is determined on the basis of the IP address, and is performed by IP gateways. After the network is configured correctly, the z/OS host appears to be communicating directly with the TCP/IP-attached printer. Define the Communications Control Unit to z/OS If you have not already done so, define the communications control unit for the z/OS host, such as the 3172 or the 3745 control unit, to z/OS. Use either an z/OS configuration program (MVSCP) or a hardware configuration definition (HCD), depending on the version of your z/OS system: • When using a version earlier than z/OS 4.1.0, use an MVSCP. • When using a version of z/OS 4.1.0 or later, use an HCD or an MVSCP. For more information about using these methods, refer to: • MVS/ESA* Migration Planning: Dynamic I/O Configuration • MVS/ESA Hardware Configuration: Using the Dialog Modify the TCP/IP Profile in z/OS The TCP/IP profile contains system configuration statements used to initialize the TCP/IP address space. Of those statements, the following are subject to special considerations when you are printing from PSF on TCP/IP-attached printers. Samples of these statements are printed in bold in the example shown in Figure 24.

88 Figure 24. Modifying TCP/IP Profile This section contains information about the statements, the special considerations that apply to them, and the changes they may make necessary. If you change any of the values in the TCP/IP profile, restart TCP/IP to pick up the changes. 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

size of the data buffers. For printing on TCP/IP-attached printers, it is recommended that you specify at least 160 data buffers, 32768 buffer size. SMALLDATABUFFERPOOLSIZE The SMALLDATABUFFERPOOLSIZE statement defines the number of small data buffers. For printing on TCP/IP-attached printers, it is recommended that you specify at least 256 small data buffers. TINYDATABUFFERPOOLSIZE The TINYDATABUFFERPOOLSIZE statement defines the number of tiny data buffers. For printing on TCP/IP-attached printers, it is recommended that you specify at least 256 tiny data buffers. KEEPALIVEOPTIONS PSF relies on TCP to detect when a connection with a TCP/IP- attached printer is no longer usable. When no data has been exchanged between PSF and its connection partner, TCP sends keep-alive probes to the connection partner periodically. These periodic probes, called keep-alive transmissions, enable TCP to discover when a connection is no longer usable even if the connection partner 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 TCP/IP-attached printers, it is recommended that you specify a shorter interval than the default, such as 10 minutes, for the interval between keep-alive transmissions.

90 Also, if any target host requires that the keep-alive packet contain data, specify SENDGARBAGE TRUE. For example: KEEPALIVEOPTIONS INTERVAL 5 SENDGARBAGE TRUE ENDKEEPALIVEOPTIONS GATEWAY NOTE: If the host has keep-alive enabled, be sure to to disable the printer's keep-alive function. See page 183 for the keep-alive command. The Packet Size parameter of the GATEWAY statement defines the maximum transmission unit (MTU) for the z/OS host. For 10/100Base-T Ethernet Interface printers, the MTU size is fixed at 1024 bytes. The value cannot be adjusted. Verify the Printer Connection To verify that the z/OS system can establish a connection with the TCP/IP-attached printer, “ping” the printer from the MVS system. From a TSO session, enter the following command: TSO PING ip_address In JES2, enter the following command from the System Display and Search Facility (SDSF) menu 6: ping ip_address ip_address specifies the IP address of the Ethernet. Here is an example of a successful “ping” command: EZA0458I Ping V3R1: Pinging host 9.99.12.33 (Use ATTN to interrupt.) EZA0463I PING: Ping #1 response took 0.084 seconds. Successes so far = 1. Here is an example of an unsuccessful “ping” command: EZA0458I Ping V3R1: Pinging host 9.99.12.33 (Use ATTN to interrupt.) EZA0464I PING: Ping #1 timed out NOTE: If you have problems “ping”-ing a printer, refer to “Handling z/OS Connectivity Problems” on page 99.

When a TCP/IP-attached printer is to be used with JES, it must be defined for deferred printing mode with JES. JES2 Printer Definitions Below is an example of the JES2 printer definition initialization member, located in the system PARMLIB: FSS(FSS1),PROC=PSFPROC,HASPFSSM=HASPFSSM PRT1 FSS=FSS1,MODE=FSS,PRMODE=(LINE,PAGE,SOSI1), CLASS=C,UCS=0,SEP,NOSEPDS,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 named FSSDEF and would be stated as FSSDEF FSSNAME=FSS1. The value you specify for the PROC parameter must match the name on the PSF Startup procedure. JES3 Printer Definitions Below is an example JES3 printer definition. This example is not executable, but it is intended to help the JES3 systems programmer define the printer to the z/OS host. FSSDEF,TYPE=WTR,FSSNAME=FSS1,PNAME=PSFPROC,SYSTEM=SYS1, TERM=NO DEVICE,JNAME=PRT1,JUNIT=(,SYS1,,OFF), FSSNAME=FSS1, MODE=FSS,PM=(LINE,PAGE,SOSI1), CHARS=(YES,GT12), The value you specify for the JNAME parameter must match the name of the printer in the PSF Startup procedure. The value you specify for the PNAME parameter must match the name on the PSF Startup procedure.

92 Define the Printer to PSF Each TCP/IP-attached printer must be defined to PSF with a PRINTDEV statement in the PSF startup procedure. Figure 25 shows a sample PSFPROC procedure that you can modify to suit your installation. The PRINTDEV statement shows the required IPADDR keyword. No line matrix printer-specific writer procedure is currently supplied. You can, however, copy the APSWPROT sample from the APAR medium and modify it for the line matrix printer. NOTE: The line matrix printer supports only resident symbol sets. //PSFPROC PROC //**************** NETWORK PRINTERS WRITER PROCEDURE **************** //* //*01* MODULE-NAME = PSFPROC //* //*01* DESCRIPTIVE-NAME = START PROCEDURE FOR PSF: //*TCP/IP ATTACHED NETWORK PRINTERS //* //*01* NOTES = THE FULL NAME OF THE DEFAULT PAGEDEF IS //*P1A06462. //*THE FULL NAME OF THE DEFAULT FORMDEF IS //*F1A10110. //*THE FULL NAMES OF THE DEFAULT FONTS ARE //*X0GF10, X0GS10, X0TU10, AND X0GU10. //*THE FULL NAME OF THE SEPARATOR PAGE PAGEDEF IS //*P1V06483. //*THE FULL NAME OF THE SEPARATOR PAGE FONT IS

//STEP01EXEC PGM=APSPPIEP,REGION=4096K //JOBHDR OUTPUT PAGEDEF=V06483,/* JOB SEPARATOR PAGEDEF*/ //FORMDEF=A10110,CHARS=GT15/* JOB SEPARATOR FORMDEF*/ //JOBLTR OUTPUT PAGEDEF=V06483,/* JOB SEPARATOR PAGEDEF*/ //FORMDEF=A10110,CHARS=GT15/* JOB SEPARATOR FORMDEF*/ //DSHDR OUTPUT PAGEDEF=V06483,/* DS SEPARATOR PAGEDEF*/ //FORMDEF=A10110,CHARS=GT15/* DS SEPARATOR FORMDEF*/ //MSGDS OUTPUT PAGEDEF=A06462,/* MESSAGE DATASET PAGEDEF*/ //FORMDEF=A10110/* MESSAGE DATASET FORMDEF*/ //FONT300DDDSN=SYS1.FONT300,/* SYSTEM FONTS - 300 PEL*/ //DISP=SHR //PSEG01DDDSN=SYS1.PSEGLIB,/* SYSTEM PAGE SEGMENTS*/ //DISP=SHR //OLAY01DDDSN=SYS1.OVERLIB,/* SYSTEM MEDIUM OVERLAYS*/ //DISP=SHR/* //PDEF01DDDSN=SYS1.PDEFLIB,/* SYSTEM PAGEDEFS*/ //DISP=SHR //FDEF01DDDSN=SYS1.FDEFLIB,/* SYSTEM FORMDEFS*/ //DISP=SHR //* ******************************************************************************************/

94 //*PRINTDEV //* ******************************************************************************************/ //PRT1CNTL //PRT1PRINTDEV FONTDD=*.FONT300,/* 300 PEL FONT LIBRARY DD*/ //OVLYDD=*.OLAY01,/* OVERLAY LIBRARY DD*/ //PSEGDD=*.PSEG01,/* SEGMENT LIBRARY DD*/ //PDEFDD=*.PDEF01,/* PAGEDEF LIBRARY DD*/ //FDEFDD=*.FDEF01,/* FORMDEF LIBRARY DD*/ //JOBHDR=*.JOBHDR,/* JOB HEADER SEPARATOR*/ //*/* OUTPUT*/ //JOBTRLR=*.JOBTLR,/* JOB TRAILER SEPARATOR*/ //*/* OUTPUT*/ //DSHDR=*.DSHDR,/* DATA SET HEADER*/ //*/* SEPARATOR*/ //MESSAGE=*.MSGDS,/* MESSAGE DATA SET OUTPUT*/ //BUFNO=5,/* NUMBER OF WRITE DATA BUFFERS*/ //PAGEDEF=A06462,/* DEVICE PAGEDEF DEFAULT*/ //FORMDEF=A10110,/* DEVICE FORMDEF DEFAULT*/ //CHARS=(GF10,/* DEVICE*/ //GS10,TU10,GU10),/* DEFAULT FONT SET*/ //PIMSG=YES,/* ACCUMULATE DATA SET*/ //*/* MESSAGES*/ //DATACK=BLOCK,/* REPORT ALL DATA-CHECK*/ //*/* ERRORS*/ //TRACE=NO,/* CREATE INTERNAL TRACE*/ //FAILURE=WCONNECT,/* PSF ACTION ON PRINTER*/

NOTE: To specify a TCP/IP address space name other than the default, TCPIP, code the following exec statement in the writer procedure: //STEP01EXEC PGM=ASPPIEP,REGION=4096K, PARM=(,,,,tcpip_name) where tcpip_name is the name of the TCP/IP address space. If this parameter is not coded, PSF uses the default name, TCPIP. The IP address is the only required parameter. Other parameters may be set to facilitate printer sharing as described in “Sharing Line Matrix Printers on z/OS” on page 97. For a description of the PRINTDEV statement, which is not given here, see the PSF System Programming Guide. IPADDR Specifies the IP address for the printer or attachment, in dotted- decimal notation. Do not specify a hostname in place of the dotted- decimal address. //*/* FAILURE*/ //TIMEOUT=REDRIVE/* PSF ACTION ON TIMEOUT*/ //MGMTMODE=OUTAVAIL,/* PRINTER MANAGEMENT MODE*/ //DISCINTV=15,/* DISCONNECT INTERVAL IN*/ //*/* SECONDS*/ //IPADDR=’xxx.xxx.xxx.xxx’/* IP ADDRESS FOR TCP/IP*/ //PRT1ENDCNTL

96 Verifying a TCP/IP-Attached Printer on z/OS To operate a TCP/IP-attached printer, use JES operator commands. Starting a TCP/IP-attached Printer To start a TCP/IP-attached printer, do the following: 1. Start TCP/IP. 2. Power on the printer. 3. Start the printer FSA. • On JES2, the command is: $Sprinter_name • On JES3, the command is: *VARY printer_name,ON Stopping a TCP/IP-attached Printer You can stop a TCP/IP-attached printer in several ways: • The preferred method is to first stop the PSF FSA for the printer by entering the following command from the z/OS console: JES2: $Pprinter_name JES3: *VARY printer_name,OFF *CANCEL printer_name where printer_name specifies the name of the printer FSA. Then you can turn off power to the printer. • To end the PSF FSA for the printer, use the JES commands. If you are unable to purge or cancel the printer by use of the JES commands, enter the following command: MODIFY FSSname,FORCE,printer_name

97 Resolving IPDS Printing Problems If you have problems printing, do the following: • Print an Ethernet Test Page. Refer to your User’s Manual. • Verify that the IPDS service is enabled. • Verify the service name. • Verify that port number 5001 is being used. If you are still unable to print IPDS files, contact the support center. Sharing Line Matrix Printers on z/OS Line matrix printers can be shared on PSF in one of two ways: • By using the MGMTMODE and DISCINTV parameters via the JES spool. • By port switching on the printer. JES Spool Printer Sharing JES spool printer sharing is valid for TCP/IP attached network printers. A session with the printer is maintained while there is output on the JES spool and the printer is available. When there is no more output on the spool and the disconnect interval expires, PSF ends the session with the printer. PSF attempts to restart the session when there is more work on the spool for the printer. After the session is restarted, PSF must reload the resources required for the print jobs. When using this method of network printer sharing, PSF cannot determine if another print driver is active. You can request this method of network printer sharing by specifying the following parameters in the PSF Startup Proc. MGMTMODE=OUTAVAIL FAILURE=WCONNECT TIMEOUT=REDRIVE DISCINTV=n

98 MGMTMODE Set to OUTAVAIL. OUTAVAIL requests that PSF start a communications session with the printer only when output is available on the JES spool. FAILURE Specifies the action PSF is to take after a printer failure or a TCP/IP network failure. If FAILURE=WCONNECT and the printer is connected to another host when PSF attempts to establish a connection on TCP/IP, PSF continuously retries (up to the limit specified by CONNINTV) until the printer becomes available. FAILURE=STOP stops the attempt to connect to the printer. TIMEOUT Specifies the action that PSF is to take after a timeout when no output is available on JES. The DISCINTV parameter specifies the timeout interval. TIMEOUT=REDRIVE requests that PSF redrive the printer FSA using the value of the MGMTMODE parameter. TIMEOUT=STOP requests that PSF stop the printer FSA, which can then be restarted only by an operator command. DISCINTV Specifies the disconnect interval in seconds. The value can range from zero through 86400. It is recommended that you set the value to 15. When no output is available from JES for this time period, PSF ends the session with the network printer. If the value is set to zero, PSF does not end the session because of lack of output. NOTE: PSF supports two other methods of printer sharing, which are not applicable to 10/100Base-T Ethernet Interface printers. VTAM RELREQ is available for printer sharing under SNA. Port switching is available for SNA- and TCP/ IP-attached printers when a printer can support multiple active ports.

99 Port Switching Printer Sharing To support printer sharing, 10/100Base-T Ethernet Interface printers automatically switch among all attached ports (serial port, the twinax or coax port, or the Ethernet network port). Basically, the printer prints jobs for one port until no new jobs appear and the port “times out”. The printer then switches to the next port and does the same thing. To change the default “time out” value for a port, update the TIMEOUT value for the port on the appropriate menu (Serial Interface, Ethernet, Twinax Interface, or Coax Interface). Handling z/OS Connectivity Problems If you encounter problems when “ping”-ing a network printer from z/OS, here is how to resolve them. Ping is not Successful If the “ping” is not successful, verify the following: • The printer is powered on. • The IP address is unique in the TCP/IP network. If the IP address of the z/OS system is not unique, see your network administrator to resolve the IP address problem. • The Maximum Transmission Unit (MTU) size of the IP packet for the z/OS system is equal to the MTU size of the printer. For information about the values recommended for the z/OS system, see “Modify the TCP/IP Profile in z/OS” on page 87. To change the MTU size for the z/OS system, change the GATEWAY statement in the z/OS TCP/IP profile, and restart TCP/IP to pick up the changes. You cannot change the MTU size on a 10/100Base-T Ethernet Interface printer. The MTU size is fixed at 1024 bytes. If these items are all in order, consult your TCP/IP network administrator about a possible network problem.

100 Ping is Successful A successful “ping” usually indicates that the z/OS system can communicate with the printer; however, you might receive a successful “ping” even though the IP address of the TCP/IP- attached printer is a duplicate of another IP address. If PSF is unable to establish a network connection with the TCP/IP- attached printer or if PSF output for this printer prints elsewhere, follow these steps to determine whether the IP address of the printer is unique: 1. Turn the printer off. 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 TCP/IP z/OS Customization and Administration Guide.) 3. Enter the “ping” command again from the z/OS system. NOTE: If you receive a successful response to the “ping” command, there is a duplicate IP address. Consult your TCP/IP network administrator.