SOURCE: BLD FLASH 9645 SOURCE MATERIAL DATED: 10/96 ¦ CONFIGURING THE 3130, NP OR NPS FOR ASCII LAN PRINTING ON OS/400 The following provides sample configuration detail for TCP/IP attachment of ASCII LAN printers to the AS/400, V3R1 and above. These instructions include information for the 3130 native attachments (Ethernet and Token Ring), the Network Printers, or the Network Print Server (NPS) feature provided for the 6400, 4247 and 3130 printers. This information assumes the Ethernet or Token Ring line description is al- ready configured. When configuring a TCP/IP network to include LAN attached printers, it is im- portant that the customer understand the concepts of TCP/IP subnetting or follow the basic addressing scheme used in the following CLASS C example. 1. Obtain a unique IP address and host name (what the printer will be called on the AS/400) from your LAN Administrator to be used for this printer. In addition, the system administrator needs to provide the subnet mask being used for the network on which the printer will be attached. 2. Verify that your AS/400's LAN adapter and IP address are entered in the TCP/IP interfaces list. Verify that the interface is active (PF11 show this) as well. The printer's host name and IP address SHOULD NOT be on this list. NOTE: If the AS/400 LAN adapter is not on the list, you may need to cre- ate a line description for the adapter or change an existing one. The primary point is that the line description must include SSAP's of AA and 12 in the SSAP list. This enables TCP/IP. See the OS/400 Communications and TCP/IP Configuration books and help text for further information. Make sure that the line is varied on as well. Enter CFGTCP and select Option 1 to view the TCP/IP Interface General Information. The following is a Token Ring example: TCP/IP Interface General Information Internet Subnet -------Line-------- Address Mask Description Type Status 198.114.110.100 255.255.255.0 TRNLINE *TRLAN Active 198.114.110.80 255.255.255.0 *LOOPBACK *NONE Active 3. Verify that a host name (the name of your AS/400) and a local domain name have been entered in the host name and local domain name parameters in option 12 on the CFGTCP menu. 4. Enter CFGTCP Option 10 'Work with TCP/IP Host Table Entries'. Add a host table entry associating the printer IP address to a Host name. This name will be used as the 'Remote System' name when creating the output queue. See the example below: Work with TCP/IP Host Table Entries Internet Host Address Name 198.114.110.121 PRT6400 < *** Define for printer/NPS 198.114.110.100 AS400A 198.114.110.80 LOOPBACK 5. Upload and create a workstation customization object using the CRTWSCST command. More specific instructions are included with the readme file on the driver diskette (for a 3130) or the readme file on the Network Printer driver Web site. ( http://www.can.ibm.com/ibmprinters/ ) The WSC object is used by OS/400's Host Print Transform (HPT) to convert OS/400 spool files to PCL5 ASCII. You could use a generic PCL printer WSC object provided with OS/400, such as *HP4 for a 3130 or Network Printer, or *IBM42023 for the 6400 or 4247 printers, the specific WSC object created for the printer however, will give more complete support for the printer (ex. drawer selection, orien- tation, paper sizes, etc.). 6. Using the CRTOUTQ command, create a remote outq that specifies the print- er's IP address or host name, the printer's internal queue name ('afccu2' for a 3130, 'PASS' for a Network Printer, 'pr1' for the Network Print Server feature). ** YOU MUST PLACE SINGLE QUOTES AROUND afccu2 SO OS/400 DOES NOT CONVERT THIS TO UPPER CASE. ** Specify connection type of *IP, destination type of *OTHER, set Transform SCS to ASCII=YES, and specify *WSCST (or *HP4, *IBM42023 etc, for simple testing of the network connection) for manufacturer type/model and enter the name of the WSC ob- ject that you created. NOTE: No device description should be created for this printer since this is not intended for IPDS printing. The following is an example of an outq created for the 6400 attached via the Network Print Server feature. Create Output Queue (CRTOUTQ) Output queue . . . . . . . . . . . .> LPR6400Q Name Library . . . . . . . . . . . . .> QUSRSYS Name, *CURLIB Maximum spooled file size: Number of pages . . . . . . . . .> *NONE Number, *NONE Starting time . . . . . . . . . .> Time Ending time . . . . . . . . . . .> Time Order of files on queue . . . . . .> *FIFO *FIFO, *JOBNBR Remote system . . . . . . . . . . .> PRT6400 Remote printer queue . . . . . . . .> 'pr1' Writers to autostart . . . . . . . . *NONE 1-10, *NONE **************** Page Down for Additional parameters ***************** Queue for writer messages . . . . .> QSYSOPR Name Library . . . . . . . . . . . . .> *LIBL Name, *LIBL, *CURLIB Connection type . . . . . . . . . .> *IP *SNA, *IP Destination type . . . . . . . . . .> *OTHER *OS400, *PSF2.. Transform SCS to ASCII . . . . . . .> *YES *YES, *NO Manufacturer type and model . . . .> *IBM6404 Workstation customizing object . . .> *NONE Name, *NONE Library . . . . . . . . . . . . .> Name, *LIBL, Destination options . . . . . . . .> *NONE Text 'description' . . . . . . . . .> 'cfg of 6400 NPS, 198.114.110.121' NOTES FOR ABOVE: o The REMOTE SYSTEM name should match the HOST NAME associated with the IP Address of the printer from the CFGTCP Host Table Entry. As an alternative to creating a Host Table Entry, you may enter *INTNETADR in the Remote System field. Paging down, you will then be prompted to enter the IP address of the printer. o The REMOTE PRINTER QUEUE must be pr1, pr2.... pr8 for the Network Print Server Adapter. These names are associated with the eight 'logical' printer ports available on the NPS device. For the 3130 native Token Ring and Ethernet ports, the REMOTE PRINTER QUEUE must be 'afccu2' and must be surrounded by single quotes to remain in lower case. This is hardcoded in the AFCCU and is not configurable. For the Network Printers, the remote printer queue should be 'PASS'. o If a WORKSTATION CUSTOMIZATION OBJECT has been provided with the printer (such as the 3130), under 'Manufacturer type and model' enter *WSCST, then enter the Workstation customization object name and li- brary where installed in the next two fields. (Refer to the README provided on the diskette with the 3130 Workstation Customization Ob- ject for instructions on uploading and creating the object on the AS/400.) ******************* 3130 EXAMPLE ************************** Manufacturer type and model . . . .> *WSCST Workstation customizing object . . .> IBM3130A Name, *NONE Library . . . . . . . . . . . . .> IBMPRTS Name, *LIBL, o If using an object supplied with OS/400, then for 'Manufacturer type and model' enter it there, as the example *IBM6404. You may press (F4) for a list of IBM supplied objects. If you created your own, still specify the IBM supplied table and then put your modified table in the WSCST parm. The system needs to see an IBM table entry for the MFRTYPMDL parm in order to decide on the forms feed used. If you enter your modified table there, the system will default to *CONT132 for forms feed. This is because there is no device description (DEVD) to get forms feed info from. 7. Verify the appropriate data streams and attachment are enabled on the printer (ex. on the Network Printer, set the LAN cards PERSONALITY parm via the op panel to AUTO. For the 3130, verify the physical attachment, datastream and protocol functions (TCP/IP & LPR) are all enabled) 8. Power the printer off, attach the printer to the LAN, then power the printer back on. 9. Type the OS/400 command STRTCP at the command line to start OS/400 TCP (or to get confirmation that it has been started). If key OS/400 parms were changed in the steps above, you may need to end TCP/IP and then re- start it. You should now be able to PING the printer to verify that a physical link exists between the printer and the AS/400. 10. Start the remote writer for the output queue you have just created by is- suing the STRRMTWTR command. (NOTE: DO NOT use the STRPRTWTR command) You should specify the name of the outq that you created above using the CRTOUTQ command. (Do not specify the name of the printer's internal queue). Start Remote Writer (STRRMTWTR) Output queue . . . . . . . . . . . .> LPR6400Q Name, *ALL Library . . . . . . . . . . . . .> *LIBL Name, *LIBL Queue for writer messages . . . . .> *OUTQ Name, *OUTQ Library . . . . . . . . . . . . .> Name, *LIBL Form type options: Form type . . . . . . . . . . . .> *ALL Form type, *ALL Message option . . . . . . . . . .> *NOMSG *NOMSG, *INQMSG Additional Parameters Writer . . . . . . . . . . . . . . .> *OUTQ Name, *OUTQ Auto-end options: Automatically end writer . . . . .> *NO *NO, *YES If yes, when to end . . . . . . .> *NORDYF *NORDYF, *FILEEND NOTE FOR 3130 & NETWORK PRINTERS: __________________________________ Jobs placed in the remote queue do not require a spool file type of *USRASCII because HPT will convert the data to PCL5 using the WSC object. If a user program (or a client program like CA/400) actually creates PCL5 data, then the file type should be *USRASCII. COMMON PROBLEMS: _________________ o Do not add the printer IP address to the AS/400 TCP/IP Interface list. Only the AS/400's LAN cards IP addresses should be in this list. The Printer IP address goes into the Host Table Entries list. o If the printer is remote across a bridge or router, you must configure the AS/400's Default Route. Enter CFGTCP and select option 2. Note when configuring this default route, you will also be able to configure the maximum MTU size for this route. Be sure to set this to an appropriate value matching the line description or a maximum MTU size configured in the Router. $EOM