SG Printing

IBM Network Station Printing Guide
Claude Bechard, Michael Miller

Michael Burkhart, Marvin Heffler, Ravi Mandava
International Technical Support Organization

http://www.redbooks.ibm.com
SG24-5212-00
International Technical Support Organization

May 1998
SG24-5212-00
Take Note!
Before using this information and the product it supports, be sure to read the general information in Appendix D, Special
Notices on page 259.
First Edition (May 1998)

This edition applies to Release 3 of of the IBM Network Station Manager for use with OS/390, OS/400, AIX, Windows NT and
WinCenter.
Note
This book is based on a pre-GA version of a product and may not apply when the product becomes generally available. We
recommend that you consult the product documentation or follow-on versions of this redbook for more current information.
Comments may be addressed to:

IBM Corporation, International Technical Support Organization
Dept. HZ8 Building 678
P.O. Box 12195
Research Triangle Park, NC 27709-2195
When you send information to IBM, you grant IBM a non-exclusive right to use or distribute the information in any way it believes
appropriate without incurring any obligation to you.
Copyright International Business Machines Corporation 1998. All rights reserved.
Note to U.S. Government Users Documentation related to restricted rights Use, duplication or disclosure is subject to
restrictions set forth in GSA ADP Schedule Contract with IBM Corp.
Contents
Figures
Tables
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
vii
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
xiii
Preface . . . . . . . . . . . . . . . .
The Team That Wrote This Redbook
Comments Welcome . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . .
Chapter 1. Overview . . . . . . . . . . . . . . . . . . . . .
1.1 History . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.2 Release 3 Print Support . . . . . . . . . . . . . . . . .
1.3 Particularities of the IBM Network Station . . . . . . .
1.4 Configuration Using the IBM Network Station Manager
1.5 What This Document Contains . . . . . . . . . . . . .
Chapter 2. A Few Concepts . . . . . . . . . . . . . . . .
. . . . . . .
2.1 What Are Printer Queues and Spooling?
2.2 What Are Printer Data Streams? . . . . . . . . . . . .
2.2.1 ASCII-Based Printer Data Streams . . . . . . . .
2.2.2 EBCDIC-Based Printer Data Streams . . . . . . .
2.3 What Are Printer Drivers? . . . . . . . . . . . . . . . .
2.4 What Are LPRs and LPDs? . . . . . . . . . . . . . . .
2.4.1 What Is Streaming Mode LPR/LPD? . . . . . . .
2.4.2 LPR/LPD Subcommands . . . . . . . . . . . . . .
2.4.3 What Is Non-Streaming Mode Send and Receive?
2.4.4 What Is Streaming Mode Send and Receive? . .
. . . . . . . . . . . . .
. . . . . . . . . . . . .
. . . . . . . . . . . . .
. . . . . . . . . . . . .
. . . . . . . . . . . .
. . . . . . . . . . . . .
. . . . . . . . . . . . .
. . . . . . . . . . . . .
. . . . . . . . . . . .
. . . . . . . . . . . .
. . . . . . . . . . . .
. . . . . . . . . . . .
. . . . . . . . . . . .
. . . . . . . . . . . .
. . . . . . . . . . . .
. . . . . . . . . . .
. . . . . . . . . . . .
Chapter 3. How Printing Works on the IBM Network Station

3.1 History of the IBM Network Station Printing Capabilities . . .
3.1.1 Release 1 Print Support (November 1996) . . . . . . . .
3.1.2 Release 2 Print Support (November 1997) . . . . . . . .
3.2 Summary of Release 3 Print Capabilities (June 1998) . . . .
3.3 How an IBM Network Station Application Prints
. . . . . . .
3.4 The Printer Selection Process . . . . . . . . . . . . . . . . . .
3.4.1 The Print Dialog . . . . . . . . . . . . . . . . . . . . . . .
3.4.2 The Printer Selector . . . . . . . . . . . . . . . . . . . . .
3.4.3 The IBM Network Station Printer Table . . . . . . . . . .
3.5 Printer Access Control (Security) on the IBM Network Station
3.6 How the IBM Network Station Implements LPR/LPD . . . . .
3.6.1 The LPR on the IBM Network Station . . . . . . . . . . .
3.6.2 The LPD on the IBM Network Station . . . . . . . . . . .
3.7 What is SERIALD? . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . .
. . . . . . . .
. . . . . . . .
. . . . . . . .
. . . . . . . .
. . . . . . . .
. . . . . . . .
. . . . . . . .
. . . . . . . .
. . . . . . . .
. . . . . . .
. . . . . . . .
. . . . . . . .
. . . . . . . .
. . . . . . . .
Chapter 4. Configuration Using the IBM Network Station Manager

4.1 Printer Settings - System Defaults . . . . . . . . . . . . . . . . . .
4.1.1 Print Client LPR . . . . . . . . . . . . . . . . . . . . . . . . . .
4.1.2 The Print Server (LPD) . . . . . . . . . . . . . . . . . . . . . .
4.1.3 Controlling Access to the IBM Network Station Printers . . .
4.2 Adding Printers to the Printer List . . . . . . . . . . . . . . . . . . .
4.3 Removing a Printer from the Printer List . . . . . . . . . . . . . . .
Copyright IBM Corp. 1998
. . . .
. . . . .
. . . . .
. . . . .
. . . . .
. . . . .
. . . . .
xv
xv
xvi
1
1
1
4
5
6
9
9
12
13
14
14
16
18
18
19
20
23
23
23
25
27
30
32
32
34
35
36
36
38
40
43
47
49
50
51
52
53
56
iii
4.4 Parallel and Serial Port Configuration
. . . . . . . . . . . . . . . . . . . . .
Chapter 5. Host Applications Printing to IBM Network Station Local

Printer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.1 Printing from an AIX Host . . . . . . . . . . . . . . . . . . . . . . . .
5.1.1 Using a Remote Print Queue
. . . . . . . . . . . . . . . . . . .
5.1.2 Using a Modified JetDirect Queue . . . . . . . . . . . . . . . . .
5.2 Printing from a Windows NT Host
. . . . . . . . . . . . . . . . . . .
5.2.1 Installing TCP/IP Printing Services . . . . . . . . . . . . . . . .
5.2.2 Creating a Definition for the IBM Network Station Printer . . .
5.3 Printing from a WinCenter Host . . . . . . . . . . . . . . . . . . . . .
5.3.1 Printing from WinCenter Using a WinStation Printer . . . . . .
5.3.2 Printing from WinCenter Using LPR . . . . . . . . . . . . . . . .
5.4 Printing from an AS/400 Host . . . . . . . . . . . . . . . . . . . . . .
5.4.1 Using a Remote Output Queue . . . . . . . . . . . . . . . . . .
5.4.2 Using an AS/400 Device Description . . . . . . . . . . . . . . .
5.5 Printing from a VM Host . . . . . . . . . . . . . . . . . . . . . . . . .
5.5.1 Printing a PostScript File Using the LPR Command . . . . . .
5.5.2 Printing a Text File Using the LPR Command . . . . . . . . . .
5.5.3 Printing by Spooling to RSCS . . . . . . . . . . . . . . . . . . .
5.6 Printing from an OS/390 Host . . . . . . . . . . . . . . . . . . . . . .
5.6.1 Using Network Print Facility . . . . . . . . . . . . . . . . . . . .
5.6.2 Using Netspool and IP Printway . . . . . . . . . . . . . . . . . .
5.7 Printing from an OS/2 Host . . . . . . . . . . . . . . . . . . . . . . .
Chapter 6. IBM Network Station Applications Printing Examples
6.1 Printing from the 3270/5250 Emulator . . . . . . . . . . . . . . .
6.1.1 3270 Emulator Printing Functions . . . . . . . . . . . . . . .
6.2 Printing from NC Navigator . . . . . . . . . . . . . . . . . . . . .
6.2.1 Printing from the NC Navigator Browser . . . . . . . . . . .
6.2.2 Printing from the IBM Network Station Browser . . . . . . .
6.3 Printing from Java Applications . . . . . . . . . . . . . . . . . . .
6.3.1 An Example of a Java Program That Prints . . . . . . . . .
6.4 VTxxx Emulator . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.5 Printing from Lotus eSuite . . . . . . . . . . . . . . . . . . . . . .
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . . .
. . . . .
. . . . .
. . . . .
. . . . .
. . . . .
. . . . .
. . . . .
. . . . .
. . . . .
Chapter 7. Printing from an IBM Network Station to Remote Print

Servers
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
7.1 Printing to a Windows NT Server . . . . . . . . . . . . . . . . . . . .
7.1.1 Is the LPD Installed and Running? . . . . . . . . . . . . . . . .
7.1.2 Verifying Access Authority to Printers . . . . . . . . . . . . . . .
7.1.3 Choosing the Windows NT Printer Queue to Receive Print . .
7.1.4 Adding a New Printer to a Windows NT Server . . . . . . . . .
7.2 Printing to an OS/400 Host . . . . . . . . . . . . . . . . . . . . . . .
7.2.1 Is LPD Active on the AS/400? . . . . . . . . . . . . . . . . . . .
7.2.2 Starting the LPD on the AS/400 . . . . . . . . . . . . . . . . . .
7.2.3 Verifying Access Authority . . . . . . . . . . . . . . . . . . . . .
7.2.4 Choosing the AS/400 Output Queue to Receive Print Requests
7.2.5 Adding a New Printer to the AS/400 . . . . . . . . . . . . . . .
7.2.6 Data Stream Conversion on the AS/400 . . . . . . . . . . . . .
7.3 Printing to an AIX Host . . . . . . . . . . . . . . . . . . . . . . . . . .
7.3.1 Is the LPD Active on AIX? . . . . . . . . . . . . . . . . . . . . .
7.3.2 Starting LPD on AIX . . . . . . . . . . . . . . . . . . . . . . . . .
7.3.3 Verifying Access to AIX Printers . . . . . . . . . . . . . . . . . .
iv
. . . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. .
. . .
. . .
. . .
. . .
. . .
. . .
56
57
59
59
65
72
72
74
80
82
93
98
99
107
113
113
115
116
117
118
118
119
121
122
125
126
126
129
130
133
135
136
137
138
138
139
139
139
144
144
145
146
146
146
150
151
151
152
152
7.3.4 Enabling Print Access on AIX . . . . . . . . . . . . . . . . .

7.3.5 Choosing the AIX Printer Queue to Receive Print Requests
7.3.6 Adding a New Printer to the RS/6000 . . . . . . . . . . . . .
7.4 Printing to an OS/2 Host . . . . . . . . . . . . . . . . . . . . . . .
7.4.1 Is the LPD Active on OS/2? . . . . . . . . . . . . . . . . . .
7.4.2 Verifying Access Authority to the LPD . . . . . . . . . . . .
7.4.3 Starting the LPD on OS/2
. . . . . . . . . . . . . . . . . . .
7.4.4 Choosing the OS/2 Print Queue to Receive Print . . . . . .
7.5 Printing to an S/390 Host . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . .
Chapter 8. Practical Examples
8.1 Using the Spooling Capabilities of Other Hosts . . . .
8.2 Using the Transform Capabilities of Other Hosts . . .
8.3 A Sample Fictional Scenario - The Blundies Company
8.3.1 Introducing Blundies . . . . . . . . . . . . . . . . .
8.3.2 Nomenclature Used . . . . . . . . . . . . . . . . .
8.3.3 Defining the PAY6400 Printer . . . . . . . . . . .
8.3.4 Define the PAYNP17 Printer . . . . . . . . . . . .
8.3.5 Defining the PAY4029 Printer . . . . . . . . . . .
8.3.6 Creating a Payroll Group User Profile
. . . . . .
8.3.7 Creating a Group Profile on the AS/400 . . . . .
8.3.8 Adding Users to the Group . . . . . . . . . . . . .
8.3.9 Changing the Group Defaults . . . . . . . . . . .
. . . . . . . . . . .
8.3.10 Changing the User Defaults
8.3.11 Using Host Print Transform . . . . . . . . . . . .
. . . . .
. . . .
. . . . .
. . . . .
. . . . .
. . . . .
. . . . .
. . . . .
. . . . .
. . . . . . . . . . .
. . . . . . . . . . .
. . . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . . .
. . . . . . . . . . .
. . . . . . . . . . .
. . . . . . . . . . .
. . . . . . . . . . .
. . . . . . . . . . .
. . . . . . . . . . .
. . . . . . . . . . .
. . . . . . . . . . .
. . . . . . . . . . .
. . . . . . . . . . .
Chapter 9. Problem Determination Tools, Tips and Techniques . . .

9.1 Mini Console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
9.2 Printer Hex Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
9.3 PING . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
9.4 Problems When Sending from an IBM Network Station to an AS/400
9.5 Problems When Sending from an AS/400 to an IBM Network Station
9.6 Using Windows NT Event Viewer . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . .
9.7 Message Log on the IBM Network Station
9.7.1 Accessing the IBM Network Station Message Log Remotely . .
9.8 Checking the Version of an IBM Network Station . . . . . . . . . . . .
9.9 Verifying the Currently Loaded IBM Network Station Configuration .
9.9.1 The Print Section Configuration . . . . . . . . . . . . . . . . . . .
9.9.2 The Access Control Section Configuration . . . . . . . . . . . . .
9.9.3 Parallel and Serial Port Configuration Parameters . . . . . . . .
9.10 LPR/LPD Control Commands and Data Types . . . . . . . . . . . .
9.10.1 Control File Names
. . . . . . . . . . . . . . . . . . . . . . . . .
9.10.2 Control File Options Used by the IBM Network Station . . . . .
9.10.3 A Sample Control File . . . . . . . . . . . . . . . . . . . . . . . .
9.10.4 Using the LPQ Command . . . . . . . . . . . . . . . . . . . . . .
9.10.5 Viewing the Control File . . . . . . . . . . . . . . . . . . . . . . .
9.10.6 Control Commands As Used in Windows NT
. . . . . . . . . .
9.10.7 Control Commands Used by OS/2 . . . . . . . . . . . . . . . . .
9.10.8 Control Commands Used by AIX
. . . . . . . . . . . . . . . . .
9.11 Working with Windows NT Printers/Queues . . . . . . . . . . . . . .
9.11.1 Assigning Printers to Ports . . . . . . . . . . . . . . . . . . . . .
9.11.2 Local Spooling for a LAN Printer . . . . . . . . . . . . . . . . . .
9.11.3 Printing to File . . . . . . . . . . . . . . . . . . . . . . . . . . . .
9.12 Typical and Common Situations . . . . . . . . . . . . . . . . . . . . .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
Contents
154
154
155
159
159
159
159
159
159
161
161
163
164
164
165
166
166
166
167
168
168
169
173
177
179
179
179
180
180
180
181
181
181
182
182
183
188
191
194
194
194
197
198
201
201
212
213
213
213
216
218
218
9.12.1 No Printers Configured . . . . . .

9.12.2 Load Letter Message on the Printer
9.12.3 Waiting Message on the Printer .
. . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . .
Chapter 10. Application Programming Interfaces (APIs)

10.1 Release 1 APIs . . . . . . . . . . . . . . . . . . . . . .
10.2 Release 2 APIs . . . . . . . . . . . . . . . . . . . . . .
10.3 Release 3 APIs . . . . . . . . . . . . . . . . . . . . . .
Chapter 11. DBCS Considerations
218
218
219
. . . . . . . . . .
221
221
221
221
. . . . . . . . . . . . . . . . . . . . . . .
225
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
Appendix A. Special Values of Image Configurations (AS/400)
. . . . .
229
Appendix B. Printing from the VTxxx Emulator to a Remote IBM Network

Station . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 233
Appendix C. Printing Related Configuration Parameters
Appendix D. Special Notices
. . . . . . . . .
237
. . . . . . . . . . . . . . . . . . . . . . . . . . .
259
Appendix E. Related Publications

. . . . . . . . . . . . . .
E.1 International Technical Support Organization Publications
E.2 Redbooks on CD-ROMs . . . . . . . . . . . . . . . . . . .
E.3 Other Publications . . . . . . . . . . . . . . . . . . . . . .
How to Get ITSO Redbooks . . . . . . . . . .
How IBM Employees Can Get ITSO Redbooks
How Customers Can Get ITSO Redbooks . .
IBM Redbook Order Form . . . . . . . . . . . .
Index
. . . . . . . .
. . . . . . . . .
. . . . . . . . .
261
261
261
261
. . . . . . . . . . . . . . . . . .
263
263
264
265
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
267
ITSO Redbook Evaluation
vi
. . . . . . . . .
. . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . .
269
Figures
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.
11.
12.
13.
14.
15.
16.
17.
18.
19.
20.
21.
22.
23.
24.
25.
26.
27.
28.
29.
30.
31.
32.
33.
34.
35.
36.
37.
38.
39.
40.
41.
42.
43.
44.
45.
46.
47.
48.
49.
50.
Release 3 Printing Capabilities Overview . . . . . . . . . . . . . . . . . .

A Sample Print Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
The Printer Selector . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
The IBM Network Station Manager Printer Settings Configuration . . .
Printer List Parameters - System Defaults . . . . . . . . . . . . . . . . .
Spooling Output to Tape . . . . . . . . . . . . . . . . . . . . . . . . . . .
Print Flow on a Typical Large Computer System . . . . . . . . . . . . .
One Printer Serving Multiple Queues . . . . . . . . . . . . . . . . . . . .
Printer Pooling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Using the Driver at Application Print Time . . . . . . . . . . . . . . . . .
Using the Driver at the Time the Output Is Sent to the Printer
. . . . .
Sending a Spool File between Two Devices . . . . . . . . . . . . . . . .
Non-Streaming Mode Send/Receive
. . . . . . . . . . . . . . . . . . . .
Streaming Mode Send/Receive . . . . . . . . . . . . . . . . . . . . . . .
Release 1 Printing Capabilities . . . . . . . . . . . . . . . . . . . . . . . .
An IBM Network Station Application Print Request . . . . . . . . . . . .
The Java Application Print Dialog . . . . . . . . . . . . . . . . . . . . . .
The NC Navigator Print Dialog . . . . . . . . . . . . . . . . . . . . . . . .
The Emulators Print Dialog . . . . . . . . . . . . . . . . . . . . . . . . . .
The Printer Selector Panel . . . . . . . . . . . . . . . . . . . . . . . . . .
Network Station - Streaming Mode Send (1) . . . . . . . . . . . . . . . .
Network Station Streaming Mode Send (2) . . . . . . . . . . . . . . . . .
LPD on the IBM Network Station . . . . . . . . . . . . . . . . . . . . . .
Network Station Streaming Mode Receive . . . . . . . . . . . . . . . . .
Port Numbers Associated with Printing on the IBM Network Station . .
Using the IBM Network Station Manager . . . . . . . . . . . . . . . . . .
The IBM Network Station Manager Printer Defaults Configuration Panel
The Printer Settings - System Defaults . . . . . . . . . . . . . . . . . . .
Sample LPRD Messages . . . . . . . . . . . . . . . . . . . . . . . . . . .
Sample LPD Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Hosts Specified in the Access Control List . . . . . . . . . . . . . . . . .
Printer List Parameters - System Defaults . . . . . . . . . . . . . . . . .
The Printer Selector with PRT51 Added . . . . . . . . . . . . . . . . . .
Printing from Host Applications to the IBM Network Station Printer . . .
Host Application to Network Station - Components . . . . . . . . . . . .
Selecting an Attachment Type of Remote . . . . . . . . . . . . . . . . .
Selecting Local Filtering before Sending to Print Server . . . . . . . . .
Selecting the Remote Printer Type Manufacturer . . . . . . . . . . . . .
Selecting the Remote Printer Type Model . . . . . . . . . . . . . . . . .
Printer Support Not Installed . . . . . . . . . . . . . . . . . . . . . . . . .
Add a Remote Print Queue with Local Filtering . . . . . . . . . . . . . .
COMMAND STATUS Panel Showing Successful Completion . . . . . .
The New Printer in the Printer List
. . . . . . . . . . . . . . . . . . . . .
An external JetDirect device . . . . . . . . . . . . . . . . . . . . . . . . .
Selecting an Attachment Type of hpJetDirect . . . . . . . . . . . . . . .
Selecting the Remote Printer Manufacturer
. . . . . . . . . . . . . . . .
Selecting the Remote Printer Type . . . . . . . . . . . . . . . . . . . . .
BOOTP/TFTP Server Choice . . . . . . . . . . . . . . . . . . . . . . . . .
. .
. .
. .
. .
. .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
2
3
4
5
6
10
11
12
12
15
16
17
20
21
24
26
28
31
33
33
34
34
39
40
41
42
44
47
48
50
51
52
53
53
56
57
58
60
60
61
62
62
63
64
65
65
66
67
67
68
vii
51.
52.
53.
54.
55.
56.
57.
58.
59.
60.
61.
62.
63.
64.
65.
66.
67.
68.
69.
70.
71.
72.
73.
74.
75.
76.
77.
78.
79.
80.
81.
82.
83.
84.
85.
86.
87.
88.
89.
90.
91.
92.
93.
94.
95.
96.
97.
98.
99.
100.
101.
102.
103.
104.
viii
Add a Print Queue . . . . . . . . . . . . . . . . . . . . . .

Messages when Creating the Queue . . . . . . . . . . .
Change/Show Characteristics of a Queue Device . . . .
Change/Show Characteristics of a Queue Device . . . .
Results of the more /etc/qconfig Command . . . . . . .
Network Services
. . . . . . . . . . . . . . . . . . . . . .
Network Services - Add . . . . . . . . . . . . . . . . . . .
Add Printers Wizard . . . . . . . . . . . . . . . . . . . . .
Add Printers - Add Port . . . . . . . . . . . . . . . . . . .
Adding a Printer Port . . . . . . . . . . . . . . . . . . . .
Add LPR Compatible Printer . . . . . . . . . . . . . . . .
Add Printer Wizard - New LPR Port Added
. . . . . . .
Choosing the Printer Driver . . . . . . . . . . . . . . . . .
Naming the Printer . . . . . . . . . . . . . . . . . . . . . .
Choosing Whether to Share the Printer . . . . . . . . . .
Choosing Whether to Print a Test Page . . . . . . . . .
Did the Test Page Print Correctly? . . . . . . . . . . . .
A Sample Test Page Output . . . . . . . . . . . . . . . .
The New Printer in the Printers Folder . . . . . . . . . .
Windows NT Help . . . . . . . . . . . . . . . . . . . . . .
Printing from WinCenter Applications . . . . . . . . . . .
IBM Network Station Print Components - WinCenter . .
WinStation Printer Configuration . . . . . . . . . . . . . .
Administrative Tools Folder . . . . . . . . . . . . . . . . .
WinStation Configuration . . . . . . . . . . . . . . . . . .
Edit WinStation Configuration . . . . . . . . . . . . . . .
Advanced WinStation Configuration . . . . . . . . . . . .
User Manager . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . .
User Properties
User Configuration . . . . . . . . . . . . . . . . . . . . . .
Create a Printer . . . . . . . . . . . . . . . . . . . . . . .
Printer Details
. . . . . . . . . . . . . . . . . . . . . . . .
Printer Manager . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . .
Parallel Port
Serial Port
. . . . . . . . . . . . . . . . . . . . . . . . . .
IBM Network Station Print Components - Using LPR/LPD
Create a Printer in WinFrame . . . . . . . . . . . . . . .
Create a Printer in WinFrame . . . . . . . . . . . . . . .
Print Destinations . . . . . . . . . . . . . . . . . . . . . .
LPR Port . . . . . . . . . . . . . . . . . . . . . . . . . . .
Printer Details
. . . . . . . . . . . . . . . . . . . . . . . .
Selecting a Printer . . . . . . . . . . . . . . . . . . . . . .
Print Manager
. . . . . . . . . . . . . . . . . . . . . . . .
Accessing the Same Printer through Two Methods . . .
The Prompted Create Output Queue Command . . . . .
Create Output Queue Command - First Panel . . . . . .
Create Output Queue Command - Second Panel . . . .
Specifying Manufacturer, Type and Model . . . . . . . .
Entering the IP Address . . . . . . . . . . . . . . . . . . .
Entering a Printer Description . . . . . . . . . . . . . . .
The Output Queue Created Message . . . . . . . . . . .
Create Device Description (Printer) Command
. . . . .
Specifying a Font Identifier . . . . . . . . . . . . . . . . .
The Error Message . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . .
. . . . . . . . .
. . . . . . . . .
. . . . . . . . .
. . . . . . . . .
. . . . . . . . .
. . . . . . . . .
. . . . . . . . .
. . . . . . . . .
69
69
70
71
72
73
73
74
74
75
75
76
76
77
77
78
78
79
79
80
81
82
84
85
85
86
87
88
88
89
90
90
91
91
92
93
94
94
95
95
96
97
97
98
99
100
101
102
103
103
104
105
105
106
105.
106.
107.
108.
109.
110.
111.
112.
113.
114.
115.
116.
117.
118.
119.
120.
121.
122.
123.
124.
125.
126.
127.
128.
129.
130.
131.
132.
133.
134.
135.
136.
137.
138.
139.
140.
141.
142.
143.
144.
145.
146.
147.
148.
149.
150.
151.
152.
153.
154.
155.
156.
157.
The Start Remote Writer Command . . . . . . . . . . . . . . . . . . . . .

Success Message When Starting the Writer . . . . . . . . . . . . . . . .
The End Writer Command . . . . . . . . . . . . . . . . . . . . . . . . . .
Success Message When Ending the Writer . . . . . . . . . . . . . . . .
The Create Device Description (Printer) Command . . . . . . . . . . . .
LAN Attachment and Port Number Parameters . . . . . . . . . . . . . .
Host Print Transform Parameter . . . . . . . . . . . . . . . . . . . . . . .
Manufacturer Type and Model Parameter . . . . . . . . . . . . . . . . .
Remote Location Parameter . . . . . . . . . . . . . . . . . . . . . . . . .
Device Description Created Message . . . . . . . . . . . . . . . . . . . .
Printing a PostScript file from VM . . . . . . . . . . . . . . . . . . . . . .
Messages on VM Following an LPR Command . . . . . . . . . . . . . .
IBM Network Station Message Log for Print Job from VM . . . . . . . .
Printing a Text File from VM . . . . . . . . . . . . . . . . . . . . . . . . .
Printing a Text File from VM with Intermediate Spool . . . . . . . . . . .
Network Print Facility . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
NetSpool and IP PrintWay . . . . . . . . . . . . . . . . . . . . . . . . . .
IBM Network Station Applications . . . . . . . . . . . . . . . . . . . . . .
Print Screen Function . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3270/5250 Emulator Print Dialog
. . . . . . . . . . . . . . . . . . . . . .
Printer Selector . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3270 LU1/LU3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
The NC Navigator Browser . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . .
The NC Navigator Browser Print Dialog
The NC Navigator Browser Print Dialog in Release 2
. . . . . . . . . .
The Network Station Browser Print Dialog . . . . . . . . . . . . . . . . .
The Network Station Browser - Printer List . . . . . . . . . . . . . . . . .
Print Dialog on IBM Network Station . . . . . . . . . . . . . . . . . . . .
Printer Selector on IBM Network Station . . . . . . . . . . . . . . . . . .
SimplePrint - Sample Java Application Window . . . . . . . . . . . . . .
SimplePrint Sample Output - IBM 4029 Printer . . . . . . . . . . . . . .
SimplePrint Sample Output - Print to File
. . . . . . . . . . . . . . . . .
A Sample Java Print Program . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . .
Printing to Remote Print Servers
The Windows NT Services Window - TCP/IP Print Server . . . . . . . .
Add Printer Wizard
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Select a Printer Port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Select a Printer Type . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Name the Printer/Queue . . . . . . . . . . . . . . . . . . . . . . . . . . .
Shared Printer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Adding a Network Printer . . . . . . . . . . . . . . . . . . . . . . . . . . .
Work with Active Jobs, Showing QTLPDxxxxx Jobs Running . . . . . .
Changing LPD Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . .
Work with All Output Queues
. . . . . . . . . . . . . . . . . . . . . . . .
Create Device Desc (Printer) - 1 of 3 . . . . . . . . . . . . . . . . . . . .
Changing Remote Output Queue to Allow Conversion from PostScript to
PCL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Show Status of the Print Server Subsystem . . . . . . . . . . . . . . . .
Print Spooling Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Manage Print Server Menu . . . . . . . . . . . . . . . . . . . . . . . . . .
List of Remote Clients . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Add Print Access for a Remote Client
. . . . . . . . . . . . . . . . . . .
Figures
106
107
107
107
108
109
110
111
112
112
113
114
114
115
116
118
119
121
123
124
125
126
127
128
129
130
130
131
132
133
134
134
135
137
138
140
140
141
142
142
143
144
145
146
148
149
149
151
152
152
153
153
154
ix
158.
159.
160.
161.
162.
163.
164.
165.
166.
167.
168.
169.
170.
171.
172.
173.
174.
175.
176.
177.
178.
179.
180.
181.
182.
183.
184.
185.
186.
187.
188.
189.
190.
191.
192.
193.
194.
195.
196.
197.
198.
199.
200.
201.
202.
203.
204.
205.
206.
207.
208.
209.
210.
211.
List All Print Queues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Local Attachment Type . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Printer Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Printer Selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Interface Selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Parent Adapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Entering a Print Queue Name . . . . . . . . . . . . . . . . . . . . . . . .
Printer Queue Added . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Local Printing via Remote Spooler Host . . . . . . . . . . . . . . . . . .
Printing via Remote Spooler Host to a Centralized Printer . . . . . . . .
Network Diagram for Blundies . . . . . . . . . . . . . . . . . . . . . . . .
The PAYNP17 Printer Parameters
. . . . . . . . . . . . . . . . . . . . .
The PAY4029 Printer Parameters . . . . . . . . . . . . . . . . . . . . . .
Select User's Group Panel . . . . . . . . . . . . . . . . . . . . . . . . . .
Select Group for RAVI
. . . . . . . . . . . . . . . . . . . . . . . . . . . .
Printing from IBM Network Stations Directly to PAYNP17 . . . . . . . .
Using the AS/400, PAYROLL, to Queue Print for PAYNP17 . . . . . . .
Selecting PAYGRP for Group Defaults . . . . . . . . . . . . . . . . . . .
Adding PAYNP17 to the PAYGRP for Group Defaults . . . . . . . . . .
Marvin's Printer Selector . . . . . . . . . . . . . . . . . . . . . . . . . . .
Using the AS/400, PAYROLL, to Transform PostScript to PCL . . . . .
The Printer Defaults Screen, Selecting Marvin's User Defaults . . . . .
Printer Settings for MARVIN . . . . . . . . . . . . . . . . . . . . . . . . .
Marvin's Printer Selector . . . . . . . . . . . . . . . . . . . . . . . . . . .
Sample Mini Console . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Show Version . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
The Setup Menu on the Console . . . . . . . . . . . . . . . . . . . . . .
The Sections Available through Setup . . . . . . . . . . . . . . . . . . .
The Print Configuration Section . . . . . . . . . . . . . . . . . . . . . . .
The LPRD/LPD Buffer Size Parameters . . . . . . . . . . . . . . . . . .
The Printer Table Configuration Parameters . . . . . . . . . . . . . . . .
The Printer Configuration Panel in IBM Network Station Manager . . .
. . . . . . . . . . . . . . . . . . . . . .
Changing the Local serial printer
Printer Selector with PARALLEL1 and SERIAL1 Removed . . . . . . .
Access Control List for Serial and Parallel Ports
. . . . . . . . . . . . .
The Serial Daemon Access Control Configuration Parameters . . . . .
Access Control List for the LPD Daemon . . . . . . . . . . . . . . . . . .
LPD Access Control List Parameters . . . . . . . . . . . . . . . . . . . .
Parallel Port
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Parallel Port Configuration Parameters . . . . . . . . . . . . . . . . . . .
Serial Port
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Serial Port Configuration Parameters . . . . . . . . . . . . . . . . . . . .
Parallel Daemon . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Connection Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Sample Control File - Text File . . . . . . . . . . . . . . . . . . . . . . . .
Sample Control File - Binary File . . . . . . . . . . . . . . . . . . . . . .
LPQ Command Output - AIX LPD Server . . . . . . . . . . . . . . . . .
LPQ Command Output - Windows NT LPD Server . . . . . . . . . . . .
The IBM 4029 Printer Queue - Two LPR Jobs Paused . . . . . . . . . .
Two Print Jobs in the Windows NT Spooler Queue . . . . . . . . . . . .
A Sample SHD File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
The Windows NT 3.51 Registry Editor . . . . . . . . . . . . . . . . . . .
The Windows NT 3.51 Registry Editor with SimulatePassThrough Added
The Windows NT 3.51 Registry Editor with new LPD key created . . .
155
155
156
156
157
157
158
158
162
163
165
166
167
168
169
170
171
172
172
173
174
175
176
176
179
182
182
183
184
185
185
186
187
188
189
189
190
190
191
192
192
193
193
194
198
198
199
199
199
200
200
204
204
205
212. The Windows NT 3.51 Warning Message . . . . . . . . . . . . . . . . .

213. The Windows NT 3.51 Registry Editor with the LPDSVC Key Copied to
the LPD Key . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
214. The Windows NT 4.0 Registry Editor . . . . . . . . . . . . . . . . . . . .
215. The Windows NT 4.0 Registry Editor with SimulatePassThrough Added
216. The Windows NT 4.0 Registry Editor . . . . . . . . . . . . . . . . . . . .
217. The Windows NT 4.0 Registry Editor with SimulatePassThrough Added
218. Document Details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
219. Document Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
220. Windows NT - Printers and Ports . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . .
221. Windows NT - Printer Properties - Port Assignment
222. Windows NT - Printer Properties - Printer Pooling
. . . . . . . . . . . .
223. Windows NT - Printer Properties - Multiple Printers per Port
. . . . . .
224. Windows NT - Add Printer - Local Port . . . . . . . . . . . . . . . . . . .
225. Windows NT - A Local Port for a LAN Printer . . . . . . . . . . . . . . .
226. DBCS Conversion Processing . . . . . . . . . . . . . . . . . . . . . . . .
227. Printer List Parameters - System Defaults . . . . . . . . . . . . . . . . .
228. ASCII Options Configuration Panel . . . . . . . . . . . . . . . . . . . . .
229. From IBM Network Stationto IBM Network Station . . . . . . . . . . . .
230. From VTxxx Emulator to Remote IBM Network Station . . . . . . . . . .
231. VTxxx Emulator File Pull-Down . . . . . . . . . . . . . . . . . . . . . . .
Figures
205
206
207
208
209
210
211
212
213
214
215
216
217
217
226
227
228
233
234
235
xi
xii
Tables
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.
11.
12.
Local Applications in Release 1 . . . . . . . . . . . . . . . . . . . . . . . .

Host-Based Applications in Release 1 . . . . . . . . . . . . . . . . . . . .
LPR/LPD Support on Major Platforms
. . . . . . . . . . . . . . . . . . . .
Printers Supporting PCL Data Streams . . . . . . . . . . . . . . . . . . .
Printers Supporting PostScript Data Streams . . . . . . . . . . . . . . .
Printers Supporting IPDS Data Streams . . . . . . . . . . . . . . . . . .
Printers Supporting PCL and PostScript Data Streams . . . . . . . . . .
Recommended Image Configuration Objects for Some Common Printers
25
25
27
27
29
30
37
229
229
230
230
230
xiii
xiv
Preface
This redbook describes the printing capabilities of the IBM Network Station. It
applies to Release 3 of the IBM Network Station software, and to previous
releases.
It is designed to help the reader understand how printing works on the IBM Network
Station by discussing some of the basic concepts involved, illustrating the major
components of the printing subsystem, providing examples of how local applications
print to local printers and/or send printer output to remote print servers, as well as
how remote applications can send print jobs to local printers.
These examples are provided for many platforms, such as OS/390, OS/400, AIX,
Windows NT and WinCenter, and they include instructions on how to prepare these
systems to receive print jobs from an IBM Network Station.
Details are also provided on the configuration requirements of the IBM Network
Station, how to use the IBM Network Station Manager program to manipulate these
configuration parameters, and a few tools, tips and techniques helpful in performing
problem determination.
The Team That Wrote This Redbook

This redbook was produced by a team of specialists from around the world working
at the Systems Management and Networking ITSO Center, Raleigh.
Claude Bechard is a Senior Technical Marketing Support Representative at the
Systems Management and Networking ITSO Center, Raleigh. When he joined the
ITSO seven years ago, his responsibility was to support SNA communications
products and he produced numerous redbooks on IBM Communications Server
products. His responsibility in the last year has been to write and teach IBM
classes worldwide on the IBM Network Station. He is an IBM Canada employee,
with 29 years of service with IBM, and holds a degree in Mechanical and Industrial
Engineering from the University of Montreal.
Michael Miller is an AS/400 Support Specialist in IBM UK. His current role is in
the Assist/400 Printing group, supporting customers with AS/400 printing issues.
He has been working for IBM in this role for two years. He holds a degree in
Computer Science from the University of Brighton.
We also include as authors the following people from the Network Computer Device
Drivers Department in the IBM Network Computer Division development
organization without whom this project would not have been possible.
We owe them a very special mention because of their invaluable contributions to
this project, for their ideas, help, cooperation, access to early code, review, and for
sharing their design documents from which we extracted some of the material in
this document.
Michael Burkhart is a Software Engineer on the IBM Network Computer Print
Development Team in Austin. He has a B.S. in Computer Science from the
University of Texas and he has been working with IBM for four years. His expertise
lies in Xterminals, Xwindows, TCP/IP networking and Java programming.
xv
Marvin Heffler is a Development Programmer Manager in the Network Station

Device Drivers department of the IBM Network Computer Division. He manages
the department responsible for device drivers and print support on the IBM Network
Station. His previous assignment was as a team leader of print development for
AIX in the RISC System/6000 Division. Marvin has 14 years of experience in
software development and has worked for IBM for five years. His areas of
expertise include printing, commands, libraries, and project management.
Ravi Mandava is an Advisory Programmer in the IBM Network Computer Division
Development. He has a BS in Mechanical Engineering and a MS in Computer
Science from Osmania University in India. He has over 10 years of experience in
the system software development and has worked for IBM for about four years.
His areas of expertise include printing, communications, GUIs and databases, and
he has written articles on printing in AIX, SNMP and EMS in DCE, and the IBM
Network Station model 1000.
Comments Welcome
Your comments are important to us!
We want our redbooks to be as helpful as possible. Please send us your
comments about this or other redbooks in one of the following ways:
Fax the evaluation form found in ITSO Redbook Evaluation on page 269 to
the fax number shown on the form.
Use the electronic evaluation form found on the Redbooks Web sites:
For Internet users
For IBM Intranet users
http://www.redbooks.ibm.com/
http://w3.itso.ibm.com/
Send us a note at the following address:

redbook@us.ibm.com
xvi
Chapter 1. Overview
Our objective in this chapter is to provide you with a summary of the information
you need to understand the printing facilities that are available on the IBM Network
Station.
Hopefully, we can accomplish this in just a few pages, leaving you to rummage
through some of the other chapters when you require additional levels of detail.
From the start, we assume that you are already familiar with what the IBM Network
Station is, and how it functions generally. Our focus here is specifically, and only,
on the printing functionality of the IBM Network Station.
Our aim is to answer questions such as:
Which local applications are able to print?
Can applications print to the native serial or parallel port on the IBM Network
Station?
Can local applications send printer output to remote print servers?
Can host-based applications send printer output to an IBM Network
Station-attached printer?
Can WinCenter applications print locally on the IBM Network Station?
1.1 History
The IBM Network Station history only goes back to the end of 1996, at which time
the IBM Network Station only had what could be called rudimentary print support.
At that time, only the IBM Network Station browser and the local ASCII terminal
emulator were able to print to a locally attached printer. Some remote systems,
such as a WinCenter server, had the ability to send a print job to the local printer
as well by directly accessing the local daemon controlling the serial and parallel
ports.
In a second release of the support software at the end of 1997, these capabilities
were only marginally improved by the addition of a 5250 emulator which could print
to the local printer.
However, it is with the advent of the Release 3 of the software in the summer of
1998 that the printing capabilities of the IBM Network Station were significantly
enhanced with the addition of LPR/LPD capabilities.
1.2 Release 3 Print Support

Release 3 of the IBM Network Station software provides support for the TCP/IP
LPR/LPD protocol (RFC 1179), which allows the IBM Network Station to act as
either a print client or print server. This includes also LPR/LPD streaming support,
which is a draft extension to RFC 1179.
This is summarized in the following diagram:
Figure 1. Release 3 Printing Capabilities Overview
The printing capabilities of the IBM Network Station are as follows:

LPD capabilities
On the right-hand side of the diagram, we show typical hosts systems that
implement LPR/LPD functionality and that therefore have the ability to send
print requests to an LPD server.
The LPD server on the IBM Network Station can receive print requests from
any remote system that implements the LPR functionality as described in RFC
1179.
On receipt of these requests, the LPD server routes the print job through the
local API and to the module controlling access to the local serial or parallel port
where local printers are attached.
Note that the LPD server can reject print requests based on an access control
list of hosts with the required authority to use the printing facility on the IBM
Network Station.
LPR capabilities
On the left-hand side of the diagram, we show typical hosts systems that
implement LPR/LPD functionality and that therefore have the ability to receive
print requests from an LPR requester.
The LPRD requester on the IBM Network Station can send print requests to
any remote system that implements the LPR functionality as described in RFC
1179.
Note that this LPR requester is labeled LPRD to indicate that it is a daemon.
This daemon runs in the background, handling requests from local applications
to route print jobs to remote hosts instead of to the local printer(s).
Note that print requests can only come from local applications. Print requests
originating on remote hosts, and received by the LPD on the IBM Network
Station cannot be routed back to another remote host through the use of the
LPRD daemon.
Printer Selector
In the top right-hand corner of the IBM Network Station, notice the Printer
Selector component. This component is called by local applications when the
user elects to print data, in order to provide the user with a choice of printers to
select from.
The printers listed in the Selector can be either the printers attached locally to
the network station or can be printers on remote hosts. Since all print requests
from local applications go through the print API, the API routes the request to
either the SERIALD component, which handles local printers, or to the LPRD
component if the requested printer is a remote printer.
Here are examples of the panels displayed to the user, on the IBM Network
Station, when he or she elects to print. The user first gets a Print Dialog panel,
such as the one illustrated below, on which he or she gets to choose a few
characteristics of the print job such as the number of copies, or paper size. The
entries available on this particular dialog panel varies dependent on the
application used.
Figure 2. A Sample Print Dialog
If the printer selected by default is not appropriate, and the user wants to make
another choice, clicking on the Browse button or Select Printer button brings
up the Printer Selector panel, a sample of which appears in the figure below.
Chapter 1. Overview
Figure 3. The Printer Selector
This panel looks the same for all applications. Notice that this one shows a
local parallel printer, a local serial printer as well as some remote printers,
some being PostScript-capable, some being PCL-capable.
The list of printers appearing in this panel is configured by the Administrator
using the IBM Network Station Manager and are loaded by the IBM Network
Station at boot time. Since the administrator has the ability to configure
printers for all users, or for certain specific workstations, or for certain groups of
users and finally for specific users, this list of printers can be different for every
user dependent on who he or she is, on the group he belongs to and on the
specific IBM Network Station that he or she is using.
Local parallel and serial port
Although not shown in the summary diagram of the Release 3 capabilities, the
print APIs now allow applications to print to either the local serial port or to the
local parallel port, as demonstrated by the entries available in the Print Selector
panel.
DBCS conversion
Also not shown in the diagram is the ability for local applications to invoke a
data conversion program to convert ASCII data streams containing DBCS
characters into bitmap images that can be sent to printers that do not have
DBCS fonts loaded.
1.3 Particularities of the IBM Network Station

When considering the use of the printing capabilities of the IBM Network Station, it
is important to remember that as opposed to traditional systems, the IBM Network
Station does not have local disk storage and that it has a limited amount of memory
for applications and data.
These limitations negate the need for a traditional spooling system or for a print
management system. However, it still has the capability to handle large print jobs,
whether received from a remote host or generated by a local application, by
implementing a streaming mode version of the LPR/LPD support.
This provides the IBM Network Station with the ability to stream print output to a
local printer without having yet received the whole job, or to stream output to a
remote host without having generated the whole print job yet, assuming that the
remote print server also implements streaming mode.
1.4 Configuration Using the IBM Network Station Manager

Most of the important parameters that relate to printing are available for
configuration using the IBM Network Station Manager.
All these parameters are accessible through the Printers task of the IBM Network
Station Manager Setup tasks menu. Below is an illustration of one section of the
main configuration panel, to specify the print buffer sizes for the LPR and LPD
daemons, and the access control list identifying the hosts that are authorized to
send print jobs to the IBM Network Station. These parameters can be specified at
the system default level and at the workstation default level.
Figure 4. The IBM Network Station Manager Printer Settings Configuration
The second part of that same panel is shown below, where remote printers can be
added to the list of available printers, and where the local printers can be specified
as available or not.
Chapter 1. Overview
Figure 5. Printer List Parameters - System Defaults
Remote printers can be configured not only at the system default level but also at
the workstation, group and user defaults levels.
1.5 What This Document Contains

The rest of this document provides you with additional details to understand the
facilities we have highlighted above.
Here is a very brief overview of each chapter:
A Few Concepts
A brief review of concepts such as spooling, printer queues, data streams,
printer drivers, and LPR/LPD for those who may be new or rusty.
How Printing Works on the IBM Network Station
Diagrams and tables summarizing all the printing capabilities since Release 1
of the product, and an explanation of the main components involved in
providing the print support as well as the particularities of the IBM Network
Station, especially the streaming mode support for LPR/LPD.
Configuration Using the IBM Network Station Manager
How to use the IBM Network Station Manager tool to configure all the main
printing-related parameters of the IBM Network Station.
Host Applications Printing to IBM Network Station Local Printer
For each major platform, a look at how to define printers, or queues, or ports
allowing applications on these hosts to print on printers attached to the IBM
Network Station. These platforms include AIX, Windows NT, WinCenter,
OS/400, VM and OS/390.
IBM Network Station Application Printing Examples
This provides details on some of the particularities of each of the local
applications on the IBM Network Station which need to use the printing
capabilities. They include the 3270 and 5250 emulators, the NC Navigator
browser, Java applications and Lotus eSuite.
Printing from the IBM Network Station to Remote Hosts
Here we take a look at the preparations required on remote hosts to receive

print requests generated by applications on the IBM Network Station, such as
ensuring that the LPD daemon is functional, and that there are printers queues
defined corresponding to the printers configured in the IBM Network Station
Printer Selector table.
Problem Determination Tools, Tips and Techniques
A collection of miscellaneous considerations that might prove helpful in
attempting to solve some of the problems that might arise initially. Also some
additional details on some of the more detailed and involved facilities, such as
direct access to some of the SERIALD daemon's port.
Application Programming Interfaces
A very brief overview of the print APIs available. Since these APIs are not
available to the user, this information is provided mainly for the sake of
completeness and because it may help in understanding how some of the
functions work.
DBCS Considerations
A very brief look at some of the parameters pertaining to using the DBCS
conversion facility.
Chapter 1. Overview
Chapter 2. A Few Concepts

In this chapter, we explain a few concepts, mainly for the benefit of the uninitiated.
The intent is not to produce an in-depth tutorial on all topics related to printing but
rather to review some of the basic elements that one needs to be aware of in order
to better understand some of the requirements for printing and some of the
functions discussed in this document.
2.1 What Are Printer Queues and Spooling?

In the early days of electronic computing, it was very undesirable to have a
computer application print directly to the printer. Printers were slow devices,
compared to the processor. They did not have large buffers to hold printed output
and controlling them wasted valuable processor time, as the mechanical printer
operated slower than the computer as the computer waited constantly for the
printer.
The solution to this was for the application to send its output to tape, a device
which operated much faster than the printer. This used less processing time, and
meant that the tape could be taken to another less expensive machine and then the
data could be read from the tape and sent to a printer attached to that machine.
The term used to describe this process was to spool data off to a peripheral device,
maybe because it was an action somewhat reminiscent of the action of spinning
wool onto a spool. Whether it was or not, the acronym spool was assigned a
meaning of Simultaneous Peripheral Operation On-Line.
This spooling process is illustrated in the figure below.
Figure 6. Spooling Output to Tape
As computers became more powerful and processor time and storage became less
expensive, operating systems came into being in order to help manage all the
resources attached to the computer, including printers, and to allow multiple
operations to be done simultaneously.
It became economical for the printer to be attached to the computer; however,
since printers were still slow devices, it was still desirable to use spooling, so that
the application producing the printed output did not have to wait for the printer, but
executed more rapidly by sending its printed output to a faster device such as tape
(or disk later on). That printed output could then be sent to a printer by another
application, processing either in the background as a lower priority application or at
night.
This technique evolved considerably over time with the availability of faster and
larger disk storage capabilities and the sophistication of multitasking operating
systems.
Today, even the personal computer operating systems have printing subsystems,
whose job it is to manage any output produced by an application and destined for a
printer, whether that printer is locally attached or attached to a remote computer.
The proliferation of the types of printed output created by applications as well as
the different types of printers available also created the need to dissociate even
more the link between an application and the physical printing device and gave rise
to printer queues.
Printer queues are a mechanism allowing print jobs (a print job consisting of the
output data produced by an application) to be held in storage in a wait area which
has certain characteristics. These characteristics are usually representative of the
10
printer which will be used to print these specific jobs and allows a much finer
control and management over the print jobs than a general spooling area.
For example, some systems allow an application to give a priority to output, so that
some reports can always jump to the front of the queue or wait at the back of the
queue. In addition, some queues can be aware of different form types, so that if
different applications use different preprinted forms, the queue can print all spool
files of one type before prompting the printer operator to load the next form type. If
multiple printers are available, they can each have an individual queue so that
different types of reports can be sent to different printers.
This mechanism is illustrated in the diagram below.
Figure 7. Print Flow on a Typical Large Computer System
In the figure above, the application, when printing, usually sends its data to a
specific queue which represents a (logical) printer.
As jobs accumulate in a queue, an application called a print manager or job writer
(the terminology used varies by platforms) takes these jobs one at at time and
sends them to a printer.
If a printer becomes unavailable, the operator has the ability to reassign the queue
to another printer. The operator also has the ability to move jobs from one queue to
another.
In some cases, more than one queue can be assigned to a single printer, or
multiple printers can be assigned to one queue, sometimes called printer pooling.
11
Figure 8. One Printer Serving Multiple Queues
Figure 9. Printer Pooling
2.2 What Are Printer Data Streams?

The term data stream refers to the data generated by an application when it
creates data to be sent to a printer device. These data streams are, for example,
ASCII, PCL, PPDS, PostScript, SCS, IPDS and AFPDS.
Some printers have the ability to support more than one data stream; in that case,
the printer can be set to receive a specific data stream, and in many cases, the
printer has the ability to automatically detect the type of data stream received, by
examining the first few lines, and automatically switch itself to the proper mode to
process the received data.
Most data streams are based around two character sets:
ASCII - American National Standard Code for Information Interchange
This is typical of Personal Computers and RISC/6000 computers.
EBCDIC - Extended Binary Coded Decimal Interchange Code
12
This is typical of large systems such as S/390 and intermediate systems such
as AS/400.
2.2.1 ASCII-Based Printer Data Streams

ASCII data streams are based on the ASCII character set. Many of the ASCII data
streams use escape sequences to send special commands to the printer. The
sections below (2.2.1.2, PCL - Printer Control Language and 2.2.1.3, PPDS Personal Printer Data Stream) give examples of printer escape sequences.
For many years, each printer manufacturer used their own different set of escape
sequences. Modern ASCII printers still tend to have their own proprietary sets of
escape sequences, but also tend to emulate some of the more popular printers.
For example, many printers today offer PCL5 emulation.
2.2.1.1 Plain ASCII

Plain ASCII can be sent to the printer. This allows the printer to make all decisions
about the output, such as which font and paper orientation to use. It may contain
very basic control characters such as carriage returns and line feeds. This can
cause messy output, as lines may not fit on the page correctly and may be
truncated.
2.2.1.2 PCL - Printer Control Language

PCL is a data stream devised by Hewlett-Packard. There are various versions of
PCL, and one of the most widely used is PCL5. PCL is an ASCII-based data
stream, which allows printer commands to be inserted into the data stream using
escape sequences. It is called an escape sequence, because the start of each
command is indicated by the ASCII escape character, which is 1B in hex or 27 in
decimal. For example, the escape sequence to instruct the printer to use
landscape page orientation is:
Esc & l 1 O
Translated into hexadecimal using an ASCII table this would be:
1B 26 6C 31 4F
PCL is supported on many printers from many printer manufacturers.
2.2.1.3 PPDS - Personal Printer Data Stream

PPDS is a printer data stream devised by IBM, and it is similar in many ways to
Hewlett Packard's PCL.
For example, the escape sequence to instruct the printer to use landscape page
orientation is:
Esc l
Translated into hexadecimal using an ASCII table this would be:
1B 6C
13
2.2.1.4 PostScript
PostScript was developed by Adobe, and was first introduced in 1985. It is a
language that describes how a printed page should appear. The language is very
similar to a high-level programming language and describes in detail what the page
should look like when printed. Each print file that is created is like a program. This
program is then sent to the printer, which generates the page based on the
instructions it is given. For example, the command to instruct the printer to use
portrait page orientation is:
%%Orientation: Portrait
2.2.2 EBCDIC-Based Printer Data Streams

EBCDIC data streams are based on the EBCDIC character set and are in use
mainly on large and intermediate systems.
2.2.2.1 SCS - SNA Character Stream

The SCS data stream is used to print basic text. It is possible to choose between
printer fonts and to perform some printer control using SCS, and this is typically
used to control line printers.
2.2.2.2 IPDS - Intelligent Printer Data Stream

The IPDS data stream was developed by IBM. An IPDS data stream can use
functions available on the printer. Each model of printer can support different
options of the IPDS. Resources such as fonts and images cannot be downloaded
to the printer using IPDS, unless special software is used. IPDS can only use the
functionality provided by the printer. It has more two-way conversation between the
host and the printer, which assists with error recovery on the printer.
2.2.2.3 AFPDS - Advanced Function Presentation Data Stream

AFPDS is an IBM data stream used for printing to AFP printers. Using AFP, it is
possible to download objects such as fonts, overlays and images to the printer.
2.3 What Are Printer Drivers?

There are a multitude of printers on the market today and even though they all
have many similar characteristics, each and every printer can be different from the
next. These differences have to do with the different features and functions that
each printer and manufacturer offers as well as the way that they react to
commands received from an application.
A simplistic example of this might be the command to go to a new page, which is
called a page eject command. If the manufacturer of printer X1 decides that a page
eject command will be represented by a sequence of characters such as 1234,
whereas manufacturer of printer Y2 decides that in his or her case, the command is
4321, then each of these manufacturers needs to provide a program called a
device driver, which is going to be aware of these specific commands, and when
receiving a generic page eject command from an application, will translate this
page eject into the physical command appropriate to this specific printer.
Therefore, printer drivers are programs that convert output from applications into
printer specific data streams, which allows an application to be unaware of the
printer that will be used to produce output.
14
The application can specify the page layout it requires, and then pass this
information to a printer driver. The printer driver is then responsible for producing a
printer-specific data stream which can then be sent to the printer.
There are two main advantages of using printer drivers:
The application does not have to have print routines for every possible printer
that it may use.
The routines to convert the application output into printer-specific output only
need to be written once. Once the driver is written, it can be used by any
application.
There are two main ways in which printer drivers can be used by applications:
1. Some systems need the driver to be used at the time the application prints, as
illustrated in the figure below:
Figure 10. Using the Driver at Application Print Time
As is shown above, since the application uses the printer driver at the time that
it generates the print data, this data is then printer-specific, in the sense that it
already contains all the commands that are applicable only to the printer that
corresponds to the printer driver that was used. Notice that the application
could also, if it was written to do so, generate printer-specific data directly
without using a printer driver, but this would be rare today.
The main disadvantage of this method is that, once created, it is not possible to
redirect the output to another printer because the print file is printer-specific.
2. A preferred method is to have the application create generic print data
(sometimes called a metafile) which is not specific to any printer. This case is
illustrated in the figure below.
15
Figure 11. Using the Driver at the Time the Output Is Sent to the Printer
As shown in the figure, the print data is then put in a queue, and it is only when
the data is taken from the queue and sent to a printer that a printer driver is
used by the job writer or print manager responsible for emptying the queue.
The conversion to printer-specific data only takes place at the last stage.
The main advantage of this method is that the print data generated by the
application, once in a queue, can be moved to different queues and printed on
different printers.
2.4 What Are LPRs and LPDs?

LPR and LPD is a TCP/IP-based printing facility. LPR is the Line Printer Requester
(the client), used by the sending machine to communicate over IP with the LPD
(Line Printer Daemon), which resides on the receiving machine (the server) and
deals with incoming print requests by listening on TCP/IP port 515. LPD is defined
in RFC 1179.
16
Figure 12. Sending a Spool File between Two Devices
Once the request is received, the printer output is placed onto a printer queue on
the receiving system. (The printer queue is identified in the incoming request.) On
computer systems with many printer queues, the printer queue name ensures that
the output is placed on the correct output queue.
There are printer adapter devices available, such as the IBM Network Print Server,
which have several printer ports, and the printer queue value is used to differentiate
between the various ports available. When printing to such devices it is important to
know what the correct printer queue name is.
LPD itself does not do any data stream conversion; it sends whatever it receives to
the printer, as is. It is the responsibility of the sending machine to ensure that the
data is suitable to be sent to the printer.
When sending a spool file using LPR, the sending system sends two parts to the
receiving system:
1. A control file
The control file contains details about the print job such as the number of
copies requested, the type of formatting (PostScript, or passthrough mode,
etc.), the user ID of the print job, job name, banner request or forced banner,
etc.
2. A print file
This is the actual print data.
The original version of LPR/LPD was in BSD UNIX where the flow of information
was always to send the data file first followed by the control file. Because BSD
UNIX was used as the initial source of different varieties of UNIX, most
implementations of LPR/LPD chose to maintain the same ordering of the two files.
17
Several years later, RFC 1179 was issued to document the existing
implementations of LPR/LPD in an attempt to standardize how print clients and
print servers communicate. However, RFC 1179 chose not to restrict the order of
data and control files. Specifically, the RFC states that "LPR servers must be able
to receive the control file subcommand first and should be able to receive the data
file subcommand first". Effectively this says that the control file and data file can be
sent in either order. Therefore, when new versions of LPR/LPD were developed
after RFC 1179 was issued, some of them chose to reverse the order used in
defacto implementations of LPR/LPD and decided to send the control file before the
data file.
2.4.1 What Is Streaming Mode LPR/LPD?

Streaming mode LPR/LPD is a facility that allows the LPR on a sending system to
begin sending data before the system has finished creating the spool file. On a
receiving system, streaming mode allows LPD to begin sending the data to the
printer before the entire file has been received.
Therefore, streaming mode is useful for thin clients and systems with limited
storage capabilities, such as the IBM Network Station.
Note that streaming is not part of the original specification for RFC 1179, and
therefore is not supported by all LPR/LPD implementations, but it is supported by
the Release 3 of the IBM Network Station. (See Table 7 on page 37 for a list of
systems that support streaming.)
The advantages of streaming are:
Less storage is required on the originating system. If streaming is not used,
then storage is required for the entire spool file. With streaming, data can be
deleted as it is sent to the receiving system, thereby minimizing the storage
requirement on the originating system.
The output may be printed faster. With streaming, the printer may begin printing
the first page of output, before the sending system has generated the last page
of output.
Following are a few diagrams to explain how LPR/LPD works generally on typical
systems when it functions in non-streaming mode as well as in streaming mode. In
the next chapter (see 3.6, How the IBM Network Station Implements LPR/LPD on
page 36) we also illustrate how specifically the IBM Network Station implements
these two LPR/LPD modes, because of the particular characteristics of the IBM
Network Station.
2.4.2 LPR/LPD Subcommands

To better understand how LPR/LPD works, whether it is in streaming or
non-streaming mode, one must first be aware of a few of the commands used
between the LPR and LPD components.
We do not cover all the commands and subcommands here, but only those which
are required to have an appreciation for how this works, at a high level.
The following four subcommands are the primary ones we need to understand:
18
Receive Data File (RDF)

Sent to the remote LPD to ask the LPD to start receiving the
data file. The size of the file to be sent in specified in the
request. The LPD does not start printing until it receives the
control file. This command is for when streaming mode is
not used.
Receive Control File (RCF)
Sent to the remote LPD to ask the LPD to receive the control
file. This command is for when streaming mode is not used.
Receive Control File First (RCFF)
Sent to the remote LPD when streaming mode is used.
Receipt of this command by the LPD is an indication that the
LPR wants to use streaming mode instead of normal mode.
It asks the LPD to receive the control file first, so that the
LPD has the required specifications necessary to start
printing the data file as soon as it start receiving it. (Without
the control file, the LPD normally cannot print since it does
not know the job id, job name, banner or not, etc.)
Receive Data File with Unspecified Length (RDFUL)
Sent to the remote LPD after the RCFF has been accepted.
It asks the remote LPD to receive a data file even though it
has not computed the length of the data file and therefore
even though there is not length indication in the data file.
This allows the LPD to start receiving the data file in
streaming mode (while it is still being generated on the
sending system) and to start printing it (based on the control
file received earlier) before the entire file has been received.
Now that we understand a few of these subcommands, we use them in the
explanations below, to illustrate simplified flows of sending and receiving print data.
2.4.3 What Is Non-Streaming Mode Send and Receive?

The diagram below illustrates a normal LPR/LPD process when streaming is not
used.
19
Figure 13. Non-Streaming Mode Send/Receive
Here is a brief description of the process illustrated in the above diagram:

1. The application initiates the process by making a print request to the LPR, and
sending printer output.
2. The LPR spools the entire file into storage and then creates the control file
(number of copies, job name, formatting, etc.).
3. The LPR then establishes a session with the LPD and requests to send the
data file, specifying the size of the data file.
4. The LPD receives the data file and stores it on disk. At this time, the LPD
cannot yet print the data file since it does not have the control file containing
the print specifications.
5. The LPR then requests to send the control file, which the LPD accepts and
stores on disk.
6. The LPD then uses the control file to send the data file to the printer, according
to the specifications in the control file, such as number of copies, etc.
2.4.4 What Is Streaming Mode Send and Receive?

Streaming mode send allows the LPR to start sending data as soon as it has data
to send, without waiting for the entire data file to be generated.
In order for the receiving LPD side to be able to print the data as it is received, the
control file must therefore be sent before the data, which is where the streaming
mode commands come into play.
Assuming that both the sending and receiving node support streaming mode
LPR/LPD, the scenario is as follows:
20
1. The application requests to send data to the LPR component. The LPR first
creates the control file for this data.
2. The LPR establishes a session with the LPD and requests to send the control
file first, using the RCFF subcommand. The LPD receives the control file and
stores it.
3. LPR then sends the Receive Data with Unspecified Length to the LPD,
requesting that the LPD starts accepting data without knowing the size of the
entire file.
4. Upon acceptance from the LPD, the LPR starts receiving data from the
application and immediately starts sending it to the LPD.
5. The LPD receives the data, and starts printing the data based on the
specifications of the control file received earlier.
This process is illustrated in the figure below where we use water as an analogy to
explain streaming.
Figure 14. Streaming Mode Send/Receive
This process minimizes the amount of storage required to hold the data in both the
sending system and receiving nodes.
Streaming is not supported by all implementations of the LPR/LPD. Systems that
can use streaming mode send will usually attempt to use streaming first. If the
receiving system does not implement streaming, it either rejects the streaming
request, returns an error, or sometimes just waits. When this occurs, the sending
system recognizes the error and reverts to using normal (non-streaming) mode.
See 3.6, How the IBM Network Station Implements LPR/LPD on page 36 for
additional details on how streaming mode the LPR/LPD is implemented on the IBM
Network Station.
21
22

This chapter discusses the architecture and the components of the IBM Network
Station related to printing. The intent is to make the reader understand how the IBM
Network Station is structured to handle printing requests and to highlight areas that
are specific to the IBM Network Station relative to other printing subsystems.
There are three characteristics that one needs to remember about the IBM Network
Station:
It does not have any local disk storage and therefore cannot do any spooling.
It has a limited amount of RAM and operates as a real memory system, and
therefore only has a limited print buffer capability.
It does not use any printer drivers, so it must receive printer ready data
streams.
3.1 History of the IBM Network Station Printing Capabilities

This documents focuses on the printing capabilities available on the IBM Network
Station as of Release 3 of the support software. However, it is appropriate to start
by taking a look back to review the printing support that was available prior to
Release 3.
3.1.1 Release 1 Print Support (November 1996)

Release 1 was the initial release of the IBM Network Station and it provided only
rudimentary print support.
A set of print APIs were provided to allow local client applications to print directly to
the parallel port on the IBM Network Station. The APIs did not allow printing to the
serial port or over the network to remote print servers.
These print APIs are used by the local applications but are not available directly to
the user. However, if you need to know a bit more about these APIs, please refer
to Chapter 10, Application Programming Interfaces (APIs) on page 221.
In addition to the print APIs, the operating system on the IBM Network Station
provided a mechanism for printing directly to the parallel or serial ports, either from
a local application or from a remote system. This method used a simple TCP/IP
sockets protocol that is not part of any standard specification. The only local
application that used this method for printing is the VTxxx emulator, which provided
the capability to do screen prints to either serial or parallel printers.
The same method worked for remote systems allowing them to print directly to
either serial or parallel printers similar to the way attached printing is supported on
X terminals. When Release 1 shipped, the AS/400 had the capability to use this
function, as well as WinCenter and the IP PrintWay product on an S/390 host.
In Release 1, there was no support for local applications to send print jobs to
remote print servers or LAN-attached printers.
23
The following diagram provides a visual summary of the Release 1 print capabilities
and the tables that follow the diagram describe the same functions in tabular format
for local applications and for host-based applications.
Figure 15. Release 1 Printing Capabilities
For the local applications, Table 1 on page 25 shows whether or not the
application uses the print APIs, whether or not the application can print on serial or
parallel printers, whether or not the application can print to remote printers, and
what print data streams are generated by the application.
24
Table 1. Local Applications in Release 1

Applications
Uses API
Local Print
Remote Print
Data Streams
5250 Emulator
No
No
No
N/A
3270 Emulator
No
No
No
N/A
Spyglass Browser
Yes
Yes (1)
No
PostScript
Java Applications
No
No
No
N/A
VTxxx Emulator
No
Yes (2)
No (3)
ASCII
Notes:
(1) Although the application can print locally, it is limited to using only the parallel port.
(2) The emulator does not use the APIs but uses SERIALD to send data to either the serial or parallel port.
(3) There is a way for the VTxxx emulator to send jobs to remote print servers using instructions from NCD Inc.
See also Appendix B, Printing from the VTxxx Emulator to a Remote IBM Network Station on page 233 for an
example.
For host-based applications, Table 2 shows whether applications on the particular

host can print to an IBM Network Station-attached printer, whether the host can
print to a host-attached or LAN-attached printer, and what print data streams
applications on the host are capable of producing.
Table 2. Host-Based Applications in Release 1
Host
NS-Attached Printing
Host-Attached or
LAN-Attached Printing
Printers/Data Streams
OS/400
Yes
Yes
Any OS/400 Printer
OS/390
No (1)
Yes
Any OS/390 Printer
VM/ESA
No
Yes
Any VM Printer
AIX
No (2)
Yes
Any AIX Printer
OS/2
N/A
N/A
N/A
Windows NT
No
No
Any Windows/NT Printer
WinCenter
Yes (3)
Yes
Notes:
(1) Using IP PrintWay, OS/390 can print directly to the IBM Network Station's serial or parallel port. Additionally,
an AFP-capable printer must be attached to that port.
(2) AIX has the ability to print directly to the IBM Network Station serial or parallel port, but there are no
instructions telling a user or system administrator how to do it.
(3) WinCenter has the ability to print directly to the IBM Network Station SERIALD daemon by defining, on the
WinCenter Server, a WinStation printer.
3.1.2 Release 2 Print Support (November 1997)

The second release of the Network Station client code provided some small
improvements for printing.
One new API, printOpenSerial, was added to allow applications to print to the serial
port but it was not advertized because it is removed in Release 3. It was added
specifically for the 5250 emulator which had a requirement to print to the serial port.
The rest of the print APIs did not change in Release 2.
25
For Release 2, the NC Navigator Browser became available on the client. The
initial version of NC Navigator did not make use of the print APIs. Instead, it used
the same process as the VTxxx emulator to print directly to the parallel port on the
IBM Network Station The NC Navigator Browser cannot print to the serial port or to
remote printers in release 2.
From the host perspective, the only change in the time frame for Release 2 was for
AIX and OS/390. Now there are published instructions for configuring a print queue
on AIX that can print directly to either the serial or parallel port on the IBM Network
Station; for the OS/390 server, the NetSpool support can receive 3270 application
print data and the IP PrintWay can then print these 3270 application print files
directly to the IBM Network Station parallel port.
The following diagram provides a visual summary of the Release 2 printing
capabilities, and it is followed by tables that provide the same information in tabular
format for local applications and for host-based applications.
For the local applications, Table 3 on page 27 shows whether or not the
application uses the print APIs, whether or not the application can print on serial or
parallel printers, whether or not the application can print to remote printers, and
what print data streams are generated by the application.
26

Application
Uses API
Local Print
Remote Print
Data Streams
5250 Emulator
Yes
Yes (1)
No
ASCII
3270 Emulator
No
No
No
N/A
Spyglass Browser
Yes
Yes
No
PostScript
NC Navigator Browser
No
Yes (2)
No
PostScript
Java Applications
No
No
No
N/A
VTxxx Emulator
No
Yes (3)
No (4)
ASCII
Notes:
(1) The 5250 emulator can now print to both the serial and parallel ports using the print APIs.
(2) The NC Navigator browser can print to the local parallel port only. Additionally, NC Navigator does not use
the print APIs.
(4) There is a way for the VTxxx emulator to send jobs to remote print servers using instructions from NCD Inc..
example.

Host
Host or LAN-Attached
Printing
OS/400
Yes
Yes
Any OS/400 Printer
OS/390
No (1)
Yes
Any OS/390 Printer
VM/ESA
No
Yes
Any VM Printer
AIX
Yes
Yes
Any AIX Printer
OS/2
N/A
N/A
N/A
Windows NT
No
No
WinCenter
Yes (2)
Yes
Notes:
(1) Using IP PrintWay, OS/390 can print directly to the IBM Network Station's serial or parallel port. Additionally,
an AFP-capable printer must be attached to that port.
(2) WinCenter has the ability to print directly to the IBM Network Station SERIALD daemon by defining, on the
WinCenter Server, a WinStation printer.
3.2 Summary of Release 3 Print Capabilities (June 1998)

As there are many new capabilities in Release 3, the following diagram attempts to
provide a visual summary of all these capabilities. It is followed by tables which
provide the same information in tabular format, and by some additional details on
each important feature.
27
The main points to notice in the diagram above are:

1. The capability of the 3270 and 5250 emulators to now produce PostScript, or
PCL or ASCII output. Since a user might not have a PostScript capable printer
at his or her disposal, he or she has the capability to specify PCL output
instead.
Notice that the NC Navigator browser and Java applications, however, only
produce PostScript output.
2. The addition of a Printer Selector component allows local applications to
choose a print destination, which can be a local or a remote printer.
When a user prints from an application, a print dialog panel is presented first
(choice of number of copies for example), then a Browse or Select printer
button is available to display a list of target printers to choose from.
3. The addition of an LPRD daemon used to channel print requests from local
applications to remote print servers. Notice that we have indicated here the
remote systems that support streaming and those that do not. If the print job
generated on the IBM Network Station is larger than the available print buffer, it
is important that the receiving systems support streaming mode receive;
otherwise the print job fails on the IBM Network Station. On the IBM Network
Station receive side (LPD), this is less important since the LPD can
automatically stream data to the printer when the print buffer if overflowed.
4. The addition of an LPD daemon to accept print requests from the LPR
requesters wanting to print on the local printer. Note that print requests
incoming to the LPD daemon cannot be rerouted back out to a remote printer
through the LPRD daemon; they can only be routed to local printers by the
LPD daemon.
28
5. The SERIALD daemon (which was the only component to which print requests
could be directed at prior to Release 3) is still present and can still accept direct
requests from applications that are able to connect directly to the SERIALD's
ports, such as WinCenter.
6. The addition of a DBCS converter module that can be used to send ASCII text
with DBCS code point to printers that do not have DBCS code points loaded.
The following tables provide information for what print capabilities are available for
local applications and for host-based applications.
For the local applications, Table 5 shows whether or not the application uses the
print APIs, whether or not the application can print on serial or parallel printers,
whether or not the application can print to remote printers, and what print data
streams are generated by the application.
Application
Uses API
Local Print
Remote Print
Data Streams
5250 Emulator
Yes
Yes
Yes
PostScript,
PCL, ASCII
3270 Emulator
Yes
Yes (1)
Yes
PostScript,
PCL, ASCII
NC Navigator Browser
Yes
Yes
Yes
PostScript
Java Applications
Yes
Yes
Yes
PostScript
VTxxx Emulator
No
Yes (2)
No (3)
ASCII
Notes:
(1) The 3270 emulator only provides print screen support. It does not include 3270 LU1/LU3 client printing
support at this time.
(3) There is a way for the VTxxx emulator to send jobs to remote print servers using instructions from NCD Inc.
example.
For host-based applications, Table 6 on page 30 shows whether applications on

the particular host can print to an IBM Network Station-attached printer, whether the
host can print to a host-attached or LAN-attached printer, and what print data
streams applications on the host are capable of producing.
29

Host
Host or LAN-Attached
Printing
OS/400
Yes
Yes
Any OS/400 Printer
OS/390
Yes
Yes
Any OS/390 Printer
VM/ESA
Yes
Yes
Any VM Printer
AIX
Yes
Yes
Any AIX Printer
OS/2
Yes
Yes
Any OS/2 Printer
Windows NT
Yes
Yes
WinCenter
Yes (1)
Yes
Note:
(1) Applications on a WinCenter server can now use the LPR/LPD print support but also retain the capability to
use a WinStation Printer to print directly to the SERIALD daemon.
3.3 How an IBM Network Station Application Prints

The following diagram shows the way in which a typical IBM Network Station
application initiates a print request.
30
Figure 18. An IBM Network Station Application Print Request
An IBM Network Station application always goes through the print APIs whenever it
needs to print, whether it is to a local printer or to a remote printer.
The application obtains from the print APIs a list of available printers and also an
indication of a default printer.
The user is presented with that information, and after he or she selects a target
printer, the print request is directed at the print APIs.
If the target printer is local, the print API forwards the print request to the SERIALD
daemon which controls the local parallel and serial ports. If the target printer is
remote, the print API forwards the print request to the LPRD daemon, which opens
a connection with the destination print server and the proper print queue on that
server.
31
3.4 The Printer Selection Process

Whenever an application on the IBM Network Station needs to print, it first presents
the user with a Print dialog panel, on which the user can select entries that affect
the way the job is printed, and on which he or she can also select the destination
printer for the print job.
This destination printer is chosen from information displayed when the application
calls the Printer Selector GUI interface and displays a list of available (configured)
printers.
We take a look here at some of the display panels used for the Print dialog and the
Printer Selector. We take a look at some of the details of the printer table.
3.4.1 The Print Dialog

The Print dialog is usually the first panel that gets displayed when clicking on the
Print button, and it allows the user to select certain characteristics of the print job,
such as number of copies for example.
The Print dialog may be different dependent on what the application allows in terms
of selections. Here are samples of these panels, to give you a feel for the
selections that can be made on these panels.
The specific entries are explained in more detail in Chapter 6, IBM Network
Station Applications Printing Examples on page 121 where we describe how each
type of local application can use the printing facilities of the IBM Network Station.
From Java applications, the Print... option causes the following dialog box to be
displayed:
32
Figure 19. The Java Application Print Dialog
From the NC Navigator Browser, the Print... option causes the following dialog box
to be displayed:
Figure 20. The NC Navigator Print Dialog
From an emulator session, the Print... option causes the following dialog box to be
displayed:
33
Figure 21. The Emulators Print Dialog
3.4.2 The Printer Selector

In each of the print dialog panels above, there is a button labeled either Browse or
Select Printer which causes the application to retrieve a list of printers from the
configuration tables (using API calls) and to display them in a Printer Selector
panel.
The Printer Selector panel appears as shown below:
Figure 22. The Printer Selector Panel
The printers that appear in this list have been configured by the administrator using
the IBM Network Station Manager, and they have been read by the IBM Network
Station at boot time when reading the configuration files. When an application
34
needs to display the list, it queries the API which retrieves the list from the
configuration files.
Print Queue
This identifies the location of the printer, in the form of:
printer queue @ remote location
For example, prt07 @ as400b.austin.ibm.com would indicate that the
printer is connected to a system called as400b, and that the remote
printer queue prt07 is to be used. If the printer is local to the IBM
Network Station, a print queue name of PARALLEL1 or SERIAL1 is
used.
Description
This is a text description used to identify the printer with a name
meaningful to the user. This value does not affect printing; it is purely to
assist the user in choosing a printer. For example, it could say
something such as IBM Network Printer 17 on AS4B.
Set as system default
This specifies that the selected printer should be marked as the system
default printer. In other words, if an application requests the name of
the default printer, this is the printer name that is returned by the API, in
the current boot cycle of the IBM Network Station.
However, please note that if an application is already running, and if that
application has been designed to retain the last printer that was chosen
by the user as the application default printer, that application may elect
to use this printer as the default, instead of the system default printer,
the next time that a user initiates a print request.
So, setting a printer as the system default is not a guarantee that this
printer will indeed be selected as the default, when the application has
the ability to retain an application default printer.
Once a printer is selected, we can click OK to use the new selection, or Cancel to
keep the printer that was originally selected.
3.4.3 The IBM Network Station Printer Table

The printer table is an internal configuration table containing a list of printers
available, along with the characteristics of each of these printers.
This table is configured by the administrator using the IBM Network Station
Manager. The administrator has the option of configuring printers that are available
to all users, or only to a certain workstation, or some that are available only to
certain groups of users, or only to specific users.
After the administrator configures the different printers using the IBM Network
Station Manager, the actual print-lpr-servers parameter is added to one or more of
the configuration files that get read by the IBM Network Station at boot time.
The printer table contains the following information about the printers:
Location of the printer (host name/IP address or local)
Printer queue name on the target system
Data stream capability (PS, PCL, ASCII)
35
Description
Some DBCS related information
Banner page requirements (remote printers only)
Whether the printer is the default printer
See Chapter 4, Configuration Using the IBM Network Station Manager on
page 47 for details on the configuration of this table using the IBM Network Station
Manager.
3.5 Printer Access Control (Security) on the IBM Network Station

Access to the local printers is controlled through configuration options in the IBM
Network Station Manager.
The options are that access can be granted to:
All systems
In other words, any remote host can send print requests to the local printers.
No systems
This option restricts access to local printer(s) to local applications only.
Selected systems
In this case, specific host names or IP addresses are entered in an access
control list. Only print requests originating from these hosts are accepted by
the IBM Network Station.
page 47 for information on how to configure access control using the IBM Network
Station Manager.
3.6 How the IBM Network Station Implements LPR/LPD

The IBM Network Station has been enhanced in Release 3 to support the LPR/LPD
protocol as specified in RFC 1179. This allows local client applications on the IBM
Network Station to send print jobs to remote print servers or remote printers.
Additionally, remote print clients are able to send print jobs to either the serial port
or parallel port on the IBM Network Station.
The accepted LPR/LPD protocol requires that the data file for a print job be
generated completely before submitting the request to the remote print server. This
causes difficulty for the IBM Network Station because there is no disk that can be
used for spooling print data files and the LPR/LPD on the IBM Network Station
must then allocate RAM to store the print data file. Some of the print data files
generated from graphical applications, such as a Web browser, can be several
megabytes in size, and if multiple applications are running on the IBM Network
Station, the LPR/LPD may run out of memory before it can completely spool the
print data file.
In 1992, a proposal was made to extend the LPR/LPD protocol to support what is
known as the streaming mode LPR/LPD. The protocol extensions allow a print
client to send a print request to a print server while the print data file is still being
36
generated. This is very useful for a print client or print server that has little or no
storage, such as the IBM Network Station. Although the streaming mode proposal
was never accepted, some vendors are adding support; within IBM, the OS/400
and AIX already support streaming mode and S/390 as well through the Print
Server product.
The following table (Table 7) gives a snapshot of the current LPR/LPD support
across major platforms. The information was accurate, to the best of our
knowledge, at the time that the table was built, but is very likely to change in the
near future.
Please note that the last column entitled LPR/LPD Streaming refers to the draft
revision of RFC 1179 dated March, 1992 by Glenn Trewitt (Line Print Daemon
Protocol with streaming extensions); it does not have anything to do with the
upcoming IPP standards work in process.
Table 7 (Page 1 of 2). LPR/LPD Support on Major Platforms
OPERATING
SYSTEM
HARDWARE
VERSION
AIX
RS/6000
3.2.5
N/A
No
AIX
RS/6000
4.1.5
N/A
No
AIX
RS/6000
4.2.1
N/A
No
AIX
RS/6000
4.3(10/97)
N/A
Yes
OS/2
PC Server
2.1.1
LAN Server 4.0
No
OS/2
PC Server
Warp Connect 3.0
N/A
No
OS/2
PC Server
Warp 4.0
N/A
No
OS/2
PC Server
N/A
Yes
WorkSpace On
Demand R2
ADDL. SW.
LPR/LPD
STREAMING
OS/390(1)
S/390
1, 2, 3, and 4(9/97)
N/A
No
OS/390
S/390
5 (3/98)
Print Server (2)
Yes
VM/ESA
S/390
VM TCP/IP Version
2 (3)
No
VM/ESA
S/390
2.1.0 and 2.2.0
VM TCP/IP Version
2 (3)
No
VM/ESA
S/390
2.3.0(1Q98)
N/A
No
OS/400 (RISC)
AS/400
3.6,3.7,4.1,4.2
N/A
YES
OS/400
(NON-RISC)
AS/400
3.1,3.2
N/A
YES
Windows NT
PC Server
3.51
N/A
No
37
Table 7 (Page 2 of 2). LPR/LPD Support on Major Platforms

OPERATING
SYSTEM
Windows NT
HARDWARE
PC Server
VERSION
ADDL. SW.
LPR/LPD
STREAMING
4.0
N/A
No
Notes:
(1) OS/390 in Versions 1-4 has RFC 1179-compliant LPD/LPR support. However, they cannot handle PostScript
files received via LPD due to ASCII/EBCDIC conversion problems. This is resolved in Version 5 with an optional
product called Print Server.
(2) Print Server is a separately priced product. It includes IP PrintWay and NetSpool, along with several other
print-related packages. This product supplies both streaming LPR and LPD support. Please see
www.printers.ibm.com for more information.
(3) RSCS Version 3 Release 2 provides enhanced LPR and LPD services that can be used instead of those that
are provided with the VM TCP/IP product.
An overview of the streaming mode LPR/LPD was discussed in 2.4.1, What Is

Streaming Mode LPR/LPD? on page 18, but here we discuss how it is
implemented on the IBM Network Station.
3.6.1 The LPR on the IBM Network Station

The LPR on the IBM Network Station is slightly different from LPR implementations
on other platforms. The differences are mainly because of the fact that there is no
local disk storage on the IBM Network Station to use for spooling and to the
restricted amount of memory available on the IBM Network Station
To print using the LPR, the user selects a remote printer from the Printer Selector.
The Printer Selector list is built from the print-lpr-servers table which is loaded when
the IBM Network Station is booted and has been configured by the administrator to
include a list of printers available to the user, local and remote. The remote entries
contains the host IP address and queue name of the remote LPD systems.
On that list, when the user selects a printer that is at a location other than localhost
(localhost meaning a printer that is attached locally to the IBM Network Station),
then the LPR function is used to route the request to the remote printer.
The simplified process is as follows; we address two situations, one where the
target LPD node does not support streaming mode, and one where the target LPD
node does support streaming mode.
The target LPD node does not support streaming mode. This situation is
38
Figure 23. Network Station - Streaming Mode Send (1)
The flow, in the figure above, is as follows:

1. LPR contacts the target LPD and sends a Receive Control File First
subcommand.
LPR always attempts to use streaming mode to find out if the target LPD
supports streaming, and it does so by sending a RCFF.
2. Because the LPD does not support streaming mode, it either closes the
connection, or returns an error message, or simply waits.
3. That causes the sending LPR to recognize that the LPD target does not
support streaming mode, and it then switches to non-streaming mode. It
accepts data from the application and builds the control file and data file in
storage.
4. If the entire data file does not fit into the available print buffer in RAM, the
job fails.
There is a buffer size value on the IBM Network Station which defines how
much memory may be used when spooling a file. By default this is 10% of
the free memory at the time the print was requested. This free memory can
vary greatly dependent on the number of active applications at the time that
the print request is submitted. See Chapter 4, Configuration Using the
IBM Network Station Manager on page 47 for details on the configuration
of these parameters.
5. If the print buffer is sufficient to hold the entire data file and control file,
then LPR sends a Receive Data File (includes the length of the data file) to
the target LPD, which the LPD accepts and the data file is received.
6. The LPR sends a receive control file, and the LPD receives the control file.
39
7. The LPD then uses the control file information to print the data file.
The target LPD node supports streaming mode.
This situation is illustrated in the figure below:
Figure 24. Network Station Streaming Mode Send (2)
1. The LPD accepts the RCFF, receives the control file, and stores it in the
print buffer.
2. The LPR sends a receive data file with unspecified length.
3. The LPD accepts the RDFUL and receives the data file as it is still being
generated by the application.
4. The LPD can then start printing the data file as it is received.
3.6.2 The LPD on the IBM Network Station

The line printer daemon on the IBM Network Station receives print requests from
remote systems and it uses the print API to send the data to the local printers, via
the SERIALD. (SERIALD is discussed in more detail in 3.7, What is SERIALD?
on page 43.)
40
Figure 25. LPD on the IBM Network Station
The LPD on the IBM Network Station only sends data to the local parallel or
serial-attached printers. It is not possible to configure the IBM Network Station to
take a print job request that is received by the LPD and to forward it on to the
LPRD component in order to reroute it to a remote printer. This is because the
IBM Network Station is not really suited to act as a print job router.
The only two remote printer queues that can be accessed by an incoming LPR
request are:
PARALLEL1 - This uses LPD passthrough to the parallel port printer.
SERIAL1 - This uses LPD passthrough to the serial port printer.
If print access control has been enabled on the IBM Network Station, it verifies
whether the sending system is authorized to print on the IBM Network Station. The
options for selecting print access control and updating the authorization table are
configured in the IBM Network Station Manager. These options are discussed in
3.5, Printer Access Control (Security) on the IBM Network Station on page 36.
On the receive side, the IBM Network Station also has a print buffer size which can
be configured to hold incoming print requests. By default this is also 10% of the
free memory at the time that the print request is received.
41
See the figure below for an illustration of the LPD streaming mode receive process:
Figure 26. Network Station Streaming Mode Receive
If the received data file exceeds the available buffer size, then the IBM Network
Station has the ability to begin emptying the data onto the printer before the entire
file is received. This is sort of an internal streaming mode capability which can be
used even if the streaming protocol is not used between the remote LPR and the
local LPD.
In fact, even if non-streaming mode receive is used by the LPD, it still has the
ability to begin printing the data file even if the entire file has not yet been received
and even if the control file has not been received.
One of the reasons is that, at the moment, the LPD on the IBM Network Station
does not use the specifications present in the control file. Because of the special
nature of the IBM Network Station and the limited amount of storage, it is not
currently set up to do more print management functions and does not support such
functions as multiple copies, or banner page, or job ID, job class, job title, etc.,
which are specified in the control file. It can therefore start printing without waiting
for the control file.
If internal streaming (to start printing when the print buffer is exceeded) is not
desired, there is a configurable parameter called Bypass Print Buffer that can be
set to NO. In that case, if a request is received which exceeds the print buffer, the
job fails.
If the LPD buffer size is configured as zero, then the Bypass Print Buffer is
automatically set to YES. Setting it to NO when the LPD buffer size is set to zero
causes print jobs to fail.
Following is a simplified description of the flow when receiving a print job from a
non-streaming send node.
42
1. The LPD receives a receive data file (RDF) from a remote LPR requester which
contains the size of the data file.
If the data file is small enough to fit into the print buffer, the job is accepted
and the data is read into the print buffer.
If the job is too large to fit into the print buffer, and the Bypass Print Buffer
configuration option is set to NO, the print job request is rejected.
If the job is too large to fit into the print buffer, but the Bypass Print Buffer
configuration option is set to YES, the job is accepted, received, and
emptied onto the printer as it is being received.
2. The remote LPR then sends a receive control file (RCF) which is accepted and
the control file is read into the print buffer.
If the sending node is a streaming mode node, then the flow is as follows:
1. The LPD receives a Receive Control File First from a remote LPR, indicating
that the remote node wants to use streaming mode.
2. The control file is received by the LPD.
3. The LPD then receives a Receive Data File with Unspecified Length (RDFUL),
accepts it and the data file is streamed to the printer.
3.7 What is SERIALD?

SERIALD is a daemon responsible for controlling the serial and parallel interfaces.
It is not limited to use for printing, but because printers can be connected to the
parallel and serial interfaces, it supports printers. SERIALD is misleadingly named,
because it controls both the serial and parallel port. Sometimes, it is referred to as
PARALLELD, but internally to the IBM Network Station, PARALLELD is just an
alias for SERIALD. SERIALD has its own IP ports which can be accessed directly
by remote systems.
43
Figure 27. Port Numbers Associated with Printing on the IBM Network Station
For implementing new applications it is preferable to send print requests to the IBM
Network Station using LPR requests. However, for special applications such as
WinCenter using WinStation printers, or for special needs, or for those still
operating at a software level prior to Release 3, SERIALD is still available to allow
compatibility.
The ports available to communicate with SERIALD are:
Serial interface uses port 87 or 6461
If port 6461 is used, command mode is always used, whereas port 87 uses
command mode if the Use Serial Protocol option is set to true and it uses
passthrough mode if the Use Serial Protocol option is set to false.
See 9.9.3, Parallel and Serial Port Configuration Parameters on page 191 for
details on how to verify and set these parameters.
Parallel interface uses port 5964 or 6464.
44
If port 6464 is used, command mode is always used; whereas port 5964 uses
command mode if the Use Parallel Protocol option is set to true and it uses
passthrough mode if the Use Parallel Protocol option is set to false.
See 9.9.3, Parallel and Serial Port Configuration Parameters on page 191 for
details on how to verify and set these parameters.
An example of a remote application that currently sends print data directly to
SERIALD's port 5964 is WinCenter. This is described in 5.3, Printing from a
WinCenter Host on page 80.
We also provide examples for printing from the RS/6000 and AS/400 directly to port
6464.
45
46
Chapter 4. Configuration Using the IBM Network Station

Manager
The IBM Network Station Manager is a user-friendly tool that allows the
configuration of IBM Network Station parameters and should always be used.
In certain cases, when certain parameters are not available through the IBM
Network Station Manager configuration interface, then the administrator can resort
to editing configuration files directly.
Most of the printer-related parameters can be configured using the IBM Network
Station Manager. Only the serial port and parallel port-specific parameters cannot
be configured through the IBM Network Station Manager, but these are usually not
required except in some special cases.
The IBM Network Station Manager is a Web server application (a CGI program)
accessible from any JavaScript-enabled browser. As long as you have such a
browser and network access to the server where the IBM Network Station
configuration files are located, you can use that browser to configure the IBM
Network Station parameters. This is illustrated in the figure below.
Figure 28. Using the IBM Network Station Manager
You must be provided with the address (the URL) of the IBM Network Station
Manager by the administrator in order to connect your browser to the proper Web
server and application. Once connected, you are asked for a user ID and
47
password, after which, if properly authenticated, you are presented with the main
panel of the IBM Network Station Manager.
On the left-hand side of the main panel, there is a list of tasks identified as Setup
Tasks. If you click on Hardware, it expands into two choices: Workstations and
Printers.
Selecting Printers displays the panel as shown below, which is the main panel for
working on Printer Configuration parameters.
Figure 29. The IBM Network Station Manager Printer Defaults Configuration Panel
Notice that it shows four levels at which you can configure printer-related
parameters:
System Defaults
Parameters configured at this level apply to all workstations and all users. Any
printers defined here appears on the printer selection list for any user on any
48
workstation. Every printer's configuration parameters can be configured at this

level. These are:
The
The
The
The
The
The
LPR buffer size

LPD buffer size
Bypass Print Buffer streaming option
Access Control parameters
printer table which lists available printers
default printer
Workstation Defaults
Parameters configured at this level apply to a particular workstation. All
parameters that can be configured at the system defaults level are also
configurable at the workstation defaults level, but they apply only to the specific
identified workstation.
Group Defaults
This is new in IBM Network Station Manager for Release 3, and it allows
parameters to be configured for a group of users. At this level, only the Printer
Table and Default Printer can be configured. This is so that certain printers can
be identified as being available to only certain users. For example, a printer in
the accounting office may be reserved for use only by the members of the
accounting department.
User Defaults
Parameters at this level apply to a single individual user. Here also, only a
Printer Table and a Default Printer can be configured, and this would be used
for example if a printer needs to be dedicated and available only to a specific
user.
Entries configured in the printer table are cumulative. In other words, a specific user
will see, when presented with a list of printers to choose from, printers defined at
the system level, and those defined for his or her workstation (if any), and those
defined for the group to which he or she belongs and those defined specifically for
his or her user ID. He or she will not see printers defined for other groups, other
users or other workstations.
4.1 Printer Settings - System Defaults

Let us first take a look at the parameters that can be configured at the system
level. Clicking on System Defaults and on the Next button at the bottom of the
main panel brings up the following panel:
49
Figure 30. The Printer Settings - System Defaults
4.1.1 Print Client LPR

The Print Client (LPR) parameter is used to specify the maximum size of the LPR
buffer.
This LPR buffer is the print buffer used when a print job generated by an
application on the IBM Network Station needs to be routed to a remote printer.
By default, this is set to 10% of the free memory at the time that the print job is
generated. In other words, the actual size of the print buffer can vary according to
how much actual memory is free at the time that a print job is created by an
application.
It is possible to change this setting, so that up to 95% of the free memory can be
used as a print buffer, or as low as 0%. If the user specifies a value lower than
0%, then 0% is used, and if he or she specifies a value greater than 95%, then
95% is actually used. However, note that if the chosen percentage of available
memory computes to less than 5 KB, then a minimum of 5 KB is used in all cases.
50
This determination of the cache size is done at the beginning of processing of a

print job. In addition, throughout the processing of a print job, the LPRD and LPD
daemons monitor how much memory they are using to ensure that the total
memory used at any one point does not exceed this cache size; they also make
sure that the available system memory (at that time) does not fall below 10 KB.
This is valid for both streaming and non-streaming sends and receives, and
whenever buffer allocation is done, such as during creation of a control file or data
file for example.
This buffer size is important because, when the LPRD daemon initially connects
with the remote print server, it always attempts to use streaming mode send.
If the remote host supports streaming mode, then the size of the LPR print
buffer is less important because the LPRD daemon is able to send data as it is
generated and therefore does not need to hold the entire print job in the buffer
before sending it.
However, if the remote host does not allow streaming mode, then the IBM
Network Station must build the entire print file in the LPR print buffer before
sending it. If the buffer is too small to contain the entire print file, the print job
fails.
If the job fails because of insufficient print buffer space, the message log contains
an NSK6108 message, as illustrated below:
NSC621: lprd: Starting.

NSC626: lprd: Print job memory cache size set to 243239 bytes
(1 percent of free memory).
NSC6211: lprd: Sending print job STDIN to host 9.24.14.32.
NSC618: lprd: Out of memory.
NSC629: lprd: Cannot send print job STDIN to host 9.24.14.32.
NSC622: lprd: Ending.
Figure 31. Sample LPRD Messages
4.1.2 The Print Server (LPD)

The Print Server (LPD) parameter is used to specify the maximum size of the LPD
buffer.
This LPD buffer is the print buffer used when a print job request is received from a
remote host, to be printed on a local printer.
By default, this is also set to 10% of the free memory at the time that the print job
is received, and it can be set from 0% to 95%.
This LPD buffer size is less important than the LPR size because the LPD daemon
has the ability to switch internally to steaming mode when the size of the print job
exceeds the size of the LPD buffer. (This is true whether the actual protocol used
between the remote LPR and the local LPD is using streaming mode or not.)
In other words, when the LPD print buffer is exceeded, the LPD daemon starts
streaming the data to the printer right away. However, this can be controlled with
51
the parameter Bypass print buffer when file exceeds buffer size, which is located
just below the Maximum LPD Buffer Size.
If the Bypass print buffer parameter is set to Yes, then the IBM Network Station
begins passing the print file to the printer before it has received the complete file.
However, if however the Bypass print buffer parameter is set to No, then the print
job fails, and the message log contains an NSC6216 error message, as shown
below:
NSC621: lpd: Starting.

NSC626: lpd: Print job memory cache size set to 33871 bytes
(1 percent of free memory).
NSC6218: lpd: Host WTR585.itso.ral.ibm.com requests local host
to receive a printer job for queue PARALLEL1.
NSK-??-: 8-1:accepting PARALLELD connection
from itsonct1.itso.ral.ibm.com
NSK531: parallel 1: opened session from 9.24.14.189
NSC6216: lpd: File dfA23MILLERMG from host
WTR585.itso.ral.ibm.com too large for cache.
NSC621: lpd: Print job huge.doc received from host
WTR585.itso.ral.ibm.com
NSC6214: lpd: Print job huge.doc from host WTR585.itso.ral.ibm.com
failed.
NSC622: lpd: Ending.
NSK534: parallel 1: closed session from 9.24.14.189
Figure 32. Sample LPD Messages
4.1.3 Controlling Access to the IBM Network Station Printers

When print requests are received by the IBM Network Station from remote systems,
the administrator can specify whether these requests are to be accepted or not.
The parameter for controlling this access is called Remote systems allowed to print
on this IBM Network Station. and is located just after the Bypass print buffer
parameter.
This parameter can be set to:
Accept requests from all systems, which is the default setting.
Reject all requests, which is the last option No systems. This means that only
local applications are allowed to print on the IBM Network Station-attached
printer and that requests from remote hosts are all rejected.
Accept requests on a selective basis, based on the hosts names specified in
the list appearing besides the Selected systems radio button. As indicated
below the list, host names or host IP addresses are entered in this list and
separated by commas, as illustrated in the figure below.
52
Figure 33. Hosts Specified in the Access Control List
Note that this option controls access to both the LPD daemon and the SERIALD
daemon. So whether the print request is received by the LPD daemon from an LPR
requester, or by the SERIALD daemon on a specific port such as 87 or 5964, the
access control list is used if it is enabled.
4.2 Adding Printers to the Printer List

The next printer configuration task is to define all the printers to be made
accessible to the users.
On the same panel where we are defining System Defaults parameters such as
LPR and LPD Print buffer size, if you scroll down to the bottom, the Printer List
specifications appear, as shown in the figure below:
All printers that are defined on this list, since this is at the System Defaults level,
are available to all IBM Network Station users.
Notice that the first two entries are already pre-specified for the local printers, which
might be using the serial or parallel port and that the queue names are fixed to
53
either PARALLEL1 or SERIAL1. These two entries are in the default printer table
shipped with Release 3. Their stream types are pre-specified as PS for PostScript.
Note that these default entries can also be removed if needed by blanking out all
the fields and specifying None attached. This might be needed if none or most of
the IBM Network Stations have local printers attached and you do not want these
entries to take up space in the Printer Selector panel which gets displayed to the
user when selecting a printer to use.
These entries for local printers are only available at either the System Defaults level
or the other Workstation Defaults level.
The last entry is for defining one or more remote printers.
Let us examine each of the parameters that can be specified here, starting with the
Local parallel printer line.
Local Parallel printer
Default Printer
Notice that there is a radio button besides each entry. This is to
indicate which printer, of all those that are defined here, should be
considered the default printer. Once a printer is indicated as being
the default one, it is this printer which appears as pre-selected in the
Printer Selector list that the user gets when selecting a printer to
use.
Printer
There are only two choices here, either None attached as shown
here or Printer attached to indicate that there is a printer physically
attached to this port or not.
Queue Name
This is fixed to either PARALLEL1 (or SERIAL1 in the case of the
printer attached to the serial port).
Stream Type
The three choices are PostScript, PCL or ASCII.
Description
A meaningful description to identify the printer. This is the
description that is displayed in the Printer Selector panel from which
the user chooses a printer.
Banner Page
This option is not supported for local printers.
ASCII Options...
This button presents an additional panel where additional values
relative to DBCS are specified when using DBCS conversion
processing.
These values are used by the 3270 and 5250 emulators to provide
Double Byte Character Set (DBCS) support and convert the symbols
on the screen into bitmaps suitable for the printer. The parameters
describe attributes of the printer such as dots per inch and the
printer control language. These parameters are only used by the
3270 and 5250 emulators, when using DBCS. They are discussed
in more detail in Chapter 11, DBCS Considerations on page 225.
54
Local Serial printer

The options here are identical to the local parallel printer, except for the queue
name which is set to SERIAL1.
Remote Printer Server
This line, and the additional lines that can be added, are for defining target
printers that exist on remote print servers. Remote printers can be defined at
this level, that is System Defaults, as well as at the Workstation Defaults level,
Group Defaults and User Defaults level.
Remote printer server
This is the host name or IP address of the remote server where the
target print queue resides. In this example, we have used
ralyas4c.itso.ral.ibm.com.
Queue name
The name of the printer queue on the remote system to which we
are sending the printer output. In this example, we have used
PRT51. This may be an optional parameters, in some cases,
because some network printers do not need the queue name while
receiving a remote print job.
Stream type
Most IBM Network Station applications can only generate a
PostScript data stream. However, the 5250 and 3270 emulators are
also able to generate ASCII and PCL output, and these emulator
applications are able to examine this parameter at print time and
generate the data stream appropriate to the chosen printer. In this
example, we have selected PCL. Most applications ignore this
parameter and produce PostScript anyway.
Description (optional)
The description is an optional field, which is used to provide the user
with a helpful description, which is displayed by the Printer Selector
(see 3.4.2, The Printer Selector on page 34). In this example, we
use a value of To AS/4 printer.
Banner page
This value determines whether a banner page is to be produced
when printing to this remote printer. In this example, we have
selected to print a banner page. Note that this option is valid only
for remote printers.
ASCII Options...
As described above for the local printers.
To add more than one remote printer, click on the Add a Remote Printer
button; this action produces another blank set of parameters to fill out.
Once completed, click on Finish to add the printer to the list.
The result of the above configuration of remote printer PRT51 is that it should
appear in the Printer Selector, as shown below:
55
Figure 35. The Printer Selector with PRT51 Added
4.3 Removing a Printer from the Printer List

To remove a printer from the Printer List, start the IBM Network Station Manager
and select Hardware Printers from Setup Tasks.
From the Printer Defaults screen, select the default that you wish to edit. In the
following example, we remove a printer from the user defaults, but the same
method can be used for removing a printer from any of the other printer lists.
On the line for the printer that you wish to remove, blank out the Remote printer
server, Queue name and Description.
Once the fields are blanked out, click on the Add a Remote Printer button.
The screen refreshes, and the line for the removed printer disappears from the
screen. Now click on Finish to finish removing the printer.
The printer no longer appears in Printer Selector for the users affected by the
default selected.
4.4 Parallel and Serial Port Configuration

There are parameters that can be specified for the parallel and serial ports;
however, these parameters are not configurable through the IBM Network Station
Manager.
Please refer to Chapter 9, Problem Determination Tools, Tips and Techniques on
page 179 for details on the parallel and serial port parameters.
56
Chapter 5. Host Applications Printing to IBM Network Station

Local Printer
This chapter illustrates multiple scenarios where host applications need to print on
an IBM Network Station local printer. The host platforms we discuss are:
AIX
Windows NT
WinCenter
OS/400
VM/ESA
OS/390
OS/2
These are not the only systems that can be used with the IBM Network Station for
printing purposes. Any system that implements LPR/LPD is capable of printing to
the IBM Network Station and receiving printed output from the IBM Network Station.
The figure below summarizes the environment that we are using.
Figure 36. Printing from Host Applications to the IBM Network Station Printer
In these examples, we are not concerned about applications residing in the IBM
Network Station wishing to print to the local printer or to a remote printer, but only
about applications residing on a host, remote from the IBM Network Station, and
wishing to print on a printer attached to the IBM Network Station.
57
There are two methods that applications can use in this situation:
1. Use the TCP/IP LPR/LPD facilities. In this case, an LPR request is sent by the
requesting system to the LPD daemon on the IBM Network Station.
This is the recommended method to use as of the availability of Release 3.
2. Print directly to the SERIALD daemon using ports such as 87, 5964, 6461 or
6464.
This method is the only one that can be used with IBM Network Station
operating at a release earlier than Release 3 since LPR/LPD was not availble
prior to Release 3.
This method is also used by a WinCenter server for example, when using
WinStation printer definitions on the server to represent the printer attached to
a client such as an IBM Network Station. It can also be used by systems that
have the capability to address these ports directly, such as OS/400 or IP
Printway on an S/390.
We provide some examples of how this is accomplished in the following
chapters, when discussing the individual platforms that support this option.
These two methods are summarized in the figure below, where we highlight the
components involved by greying out some of the other components.
Notice that the LPD daemon receives print requests from LPR requesters on
remote hosts and forwards these requests to the print API, which in turn, transmits
these to the SERIALD daemon for printing. On the other hand, certain systems
can also access the SERIALD directly through some specific ports.
Figure 37. Host Application to Network Station - Components
58
The recommended, and easiest method is to use the LPR/LPD facility. In fact, with
the availability of the LPD daemon on the IBM Network Station, any application on
the network that can issue LPR requests can now print on the IBM Network Station
attached printer. The other method should only be used in cases where the
LPR/LPD facility cannot be used.
From remote hosts, it is only possible to send printer output to the IBM Network
Station for printing on the local printer(s) attached to the serial or parallel port. In
other words, the IBM Network Station cannot be used to receive a print request on
the LPD and send it back out to another remote hosts through the LPRD. Such
intermediate routing capability is applicable only to systems which have the ability
to spool locally in order to store and forward, which cannot be done on the IBM
Network Station because of the lack of sufficient storage.
In the text that follows, we use scenarios to give an example of the configuration
steps required in order for applications to be able to send printed output to a IBM
Network Station-attached printer. The objective is not a detailed tutorial on how
printing is implemented on each of the platforms discussed but only to give the
essential steps required to successfully implement printing from these platforms.
5.1 Printing from an AIX Host

In this section, we discuss the case of applications residing on an AIX host wishing
to print to a printer attached to an IBM Network Station.
There are two methods that can be used to print to the IBM Network Station local
printer from AIX:
1. Using a print output queue
This utilizes LPR/LPD functionality and is the preferred method for IBM Network
Stations that are at least at the Release 3 level of the IBM Network Station
software.
2. Using a modified JetDirect queue
This method allows you to specify a specific port to connect to on a target
system and therefore allows us to go directly to the SERIALD daemon on the
IBM Network Station instead of the LPD daemon. This is useful for IBM
Network Stations that are not at the Release 3 level and therefore do not have
an LPD daemon, or for special cases where this functionality might be desired.
5.1.1 Using a Remote Print Queue

We illustrate here the steps required on the AIX host to create a remote output
queue.
1. Start SMIT.
First, start SMIT and at the System Management menu, select Print
SpoolingAdd a Print Queue.
2. Specify the attachment type.
We are then prompted for the attachment type. We need to create a remote
print queue, so we select Remote.
Chapter 5. Host Applications Printing to IBM Network Station Local Printer
59
Figure 38. Selecting an Attachment Type of Remote
3. Specify the type of processing.

On the next screen we are prompted by a box titled Type of Remote Printing,
which asks us to specify the type of processing we wish to use on the print file.
Figure 39. Selecting Local Filtering before Sending to Print Server
The choices are:

Standard processing
This sends the print file as-is, without any modifications to the data
stream. This is used when passing print files on from another host,
60
when the sending host already created a printer-specific data

stream, or when sending to a print server that has its own printer
drivers.
Local filtering
This means that AIX changes the data stream to make it
printer-specific. When we select this option, we are prompted for
the printer model in a later screen, so that AIX knows what type of
changes it should make to the data dependent on the type of
destination printer.
When printing to an IBM Network Station, this is the most likely type
of queue that we use. This is because the IBM Network Station
does not have printer drivers and we therefore need to convert the
data stream before we send it to the printer.
In this example, we are using an HP LaserJet 4 PCL printer attached to the
parallel port, so we need to make the print file printer-specific. We select Local
filtering before sending to the print server.
4. Specify the type of printer.
On the next two screens we are prompted to select the manufacturer and type
of printer that is used. In this example, we are using a Hewlett Packard
LaserJet 4, printer, so we choose Hewlett Packard on the first panel and
hplj-4 on the second panel.
Figure 40. Selecting the Remote Printer Type Manufacturer
61
Figure 41. Selecting the Remote Printer Type Model
5. Install a printer driver, if required.

It may be necessary to install the printer driver if the selected printer does not
already have the required printer driver installed. If that is the case, we get the
following panel:
Figure 42. Printer Support Not Installed
62
In that case, follow the online instructions to load the relevant printer support
software package.
In this example, the printer support was already installed on the system, so we
proceed to the next step.
6. Specify a remote host name and queue name.
In this step, we identify the characteristics of the remote print queue.
Figure 43. Add a Remote Print Queue with Local Filtering
Here are a few details on the entries in the above panel:

Names of NEW print queues to add
In this example, the printer is a PCL printer, so we enter the queue
name, nshp4, into the PCL space. If we had a printer capable of
PCL and PostScript, we could create two queues, so that we could
choose which data stream to send, or we could send both file types
to the same queue and let the printer auto detect the format.
HOST NAME of remote server
We enter the remote location of the IBM Network Station. In this
example, we use the IP address, but we could use a host name if
required.
Name of QUEUE on remote server
The printer we are using in this example is attached using the
parallel port, so we use a queue name of PARALLEL1. If the printer
was attached to the serial port, the name of the queue to use would
be SERIAL1.
TYPE of print spooler on remote server
This is used for formatting the status information received back from
the IBM Network Station. It is best to set this to AIX Version 3 or 4.
63
Send PASS-THROUGH FLAG to queue on remote server?

We wish the IBM Network Station to use pass through (that is, not
to perform any conversion on the data), so we select yes.
7. Complete the queue creation.
Once these details have been entered, press Enter, and messages are
displayed while the queue is created. Once the queue creation process is
completed, the Command field changes to .OK/, as shown below:
Figure 44. COMMAND STATUS Panel Showing Successful Completion
8. List the printer queue.

Once the printer queue has been added, press F10 to exit. To see the printer
queue that we just added, start SMIT, and select Print SpoolingList All
Print Queues to see the list of printers:
64
Figure 45. The New Printer in the Printer List
5.1.2 Using a Modified JetDirect Queue

As mentioned previously, it is preferable to use the Remote Printer Queue method
(5.1.1, Using a Remote Print Queue on page 59) to print to an IBM Network
Station printer. However, if you need to access the SERIALD daemon directly for
some reason, here are the instructions on how to accomplish this.
The Hewlett-Packard JetDirect devices allow a printer to be connected to the LAN.
They come in two main types, external and internal.
Internal - A card that is installed in a printer, to provide a printer network
interface. The internal versions of the JetDirect device are referred to as
JetDirect Cards.
External - A box (or "brick") that connects the LAN, and has either one or three
parallel ports and a LAN connector.
They can be used with LPD functionality, or the parallel port can be driven by
special JetDirect software.
Figure 46. An external JetDirect device
65
When the data is sent to the port directly, TCP/IP port 9100 is used. This is very
similar to the IBM Network Station, which can send data to the parallel port directly
using port 6464 (or 87). We can take advantage of this similarity, and use a
modified JetDirect printer queue to print to the IBM Network Station printer through
port 6464 (or 87). To do this, we need to create a JetDirect queue, and modify it.
5.1.2.1 Installing the JetDirect Software

Note: The instructions below were reproduced from RS/6000 - IBM Network
Station - A Companion Guide, SG24-2016, page 166.
If the software is not already installed, install the latest Hewlett-Packard JetDirect
Network Printer attachment software from the hpJetDirect.attach fileset, found in the
printers.hp bundle delivered with the AIX system media. At AIX 4.1.5, make sure to
also install APAR IX68615 after installing the rest of the software. Even though this
is Hewlett-Packard based software, it will work well for all types of printers attached
to the IBM Network Station.
5.1.2.2 Creating a JetDirect Queue

To install a JetDirect queue, follow these steps:
1. Start SMIT.
Start SMIT, and at the System Management menu, select Print Spooling
Add a Print Queue.
2. Specify the attachment type.
We are then prompted for the ATTACHMENT TYPE. We need to create an HP
JetDirect queue, so we select hpJetDirect:
Figure 47. Selecting an Attachment Type of hpJetDirect
3. Specify printer type and model.
66
Next we are prompted to select a printer type and model. In this example, we
are using a Hewlett-Packard LaserJet 4 printer, so we select Hewlett-Packard
on the first panel and hplj-4 on the second panel.
Figure 48. Selecting the Remote Printer Manufacturer
Figure 49. Selecting the Remote Printer Type
4. Specify BOOTP/TFTP server.

We are then prompted for whether to add this system as a BOOTP/TFTP
server. Select Do NOT make this system a BOOTP/TFTP server:
67
Figure 50. BOOTP/TFTP Server Choice
5. Specify target host and queue.

Next we are prompted for the details of the JetDirect device:
Names of NEW print queues to add
In this example, the printer is a PCL printer, so we enter the queue
name, nshp4, into the PCL space. If we had a printer capable of
PCL and PostScript, we could create two different queues, so that
we could send either data stream to the printer.
HOSTNAME of the JetDirect Card
We enter the remote location of the IBM Network Station, instead of
the JetDirect address. In this example, we have used the host
name, itsonct1.itso.ral.ibm.com, but it is also possible to use the
IP address if required.
PORT
Leave this set to 91.
68
Figure 51. Add a Print Queue
6. Complete the queue creation.

Press Enter to see the messages while queue is created. When this has
successfully completed, the Command field shows as .OK/:
Figure 52. Messages when Creating the Queue
Once the queue has been added successfully, it can be changed to use the IBM
Network Station SERIALD port (6464 or 87) instead of JetDirect port (9100).
69
5.1.2.3 Changing the JetDirect Queue for Use with IBM Network
Station
These steps detail how to change the JetDirect Queue which was created in
5.1.2.2, Creating a JetDirect Queue on page 66.
1. Start SMIT.
Start SMIT, and at the System Management menu, select Print Spooling
Programming Tools Queues and Queue Device Queue Devices
Change/Show Characteristics of a Queue Device.
2. Select the queue to work on.
We see the Change/Show Characteristics of a Queue Device screen. Enter
the name of the queue we just created into the QUEUE to which device is
attached field:
Figure 53. Change/Show Characteristics of a Queue Device
3. Change the port number.

On the following panel, select BACKEND PROGRAM pathname, scroll to the
far right of the entry, and overwrite 9100 with 6464
70
Figure 54. Change/Show Characteristics of a Queue Device
4. Complete the process.

Press Enter to make the change. We see the command run and complete
successfully, and we can now press F10 to exit SMIT.
The changes we made are now reflected in the queue configuration file. We can
examine this by listing the file, and using the command more /etc/qconfig, which
displays the qconfig file one screen at a time (press Enter to see the next screen).
Because we just added this entry, it is likely to be at the end. Notice, in the next
figure, that the backend line now shows 6464, the port number for SERIALD
parallel interface. This confirms that the change has been successfully made, and
that this will now send data that is queued to the port 6464 on the IBM Network
Station.
71
Figure 55. Results of the more /etc/qconfig Command
5.2 Printing from a Windows NT Host

Printer output from applications on a Windows NT system can be sent to an IBM
Network Station local printer, using the LPR on the Windows NT machine, provided
that the Microsoft TCP/IP Printing Services are installed.
If these services are not installed, the following section shows the procedure
required to install TCP/IP Printing Services on Windows NT.
5.2.1 Installing TCP/IP Printing Services

To install the TCP/IP printing services on a Windows NT 4.0 system, follow these
steps:
Click on StartSettingsControl PanelNetwork, which brings up the
following panel:
72
Figure 56. Network Services
Select the Services tab and click on Add to get the next panel:
Figure 57. Network Services - Add
Select TCP/IP Printing Services, click on OK and follow the rest of the
instructions.
73
5.2.2 Creating a Definition for the IBM Network Station Printer

Once the TCP/IP Printing Services are installed, create a printer definition to
represent the printer attached to the remote IBM Network Station.
Click on StartSettingsPrinters to bring up the Printers folder, on which you
double-click the Add Printers icon, to start the Add Printers Wizard.
Figure 58. Add Printers Wizard
On the above screen, select that the printer should be controlled from our computer
by selecting My Computer, and then clicking Next.
Note: You might be tempted to choose the Network Printer Server instead,
because the description states Connect to a printer on another machine, but that
refers to a printer that has already been defined on another server.
Figure 59. Add Printers - Add Port
On the above panel, click on Add Port, which brings up the following panel:
74
Figure 60. Adding a Printer Port
Select LPR port and click on New Port.
Figure 61. Add LPR Compatible Printer
Enter the hostname or IP address of the host to which the printer is attached; in
this case, it is the address of the IBM Network Station which, in our example, is
9.24.104.189. Also enter the name of the printer or print queue on that host. Since
our destination printer is on an IBM Network Station we need to use a print queue
names, which in our case is PARALLEL1. For a serially attached printer we would
use SERIAL1.
Note: If our destination was another Windows NT server for example, that name
would be a printer name, which represents a queue on a Windows NT system.
Click on OK to return to the Add Printer Wizard panel which lists the available
ports, and where you should now see the port that was just added. In our case, this
shows up in the list as 9.24.104.189:PARALLEL1.
75
Figure 62. Add Printer Wizard - New LPR Port Added
Click on Next to go to the next step, which is to specify a printer driver to be

associated with the printer. In this example, we use the driver for the IBM 4029
LaserPrinter.
Figure 63. Choosing the Printer Driver
Click on Next to get to the next panel where we need to assign a name to the
printer we just finished defining.
76
Figure 64. Naming the Printer
Enter a name for the printer and click on Next.

Note: We have used a very long name in this example. This might not be a good
idea if this name is used on some of the remote commands to send output to this
queue. For example, if one uses the LPR command from a command prompt, one
of the parameters to enter is the queue name. It is therefore probably easier to use
a shorter name. If the user does not have to use a command, but select a printer
from a list, then the length of the name is less important.
The next Add Printer Wizard panel allows us to choose whether we wish to share
this printer with other network users. In this example, we choose not to share the
printer, as shown below:
Figure 65. Choosing Whether to Share the Printer
A click on Next brings us to a panel where we are asked if we wish to print a test
page. If we choose to generate a test page, it automatically sends a test page to
77
the printer. It is useful to produce a test page, to ensure that we have configured
the printer correctly.
Figure 66. Choosing Whether to Print a Test Page
Click on Finish to complete the process. If we selected to print a test page, the
following screen is displayed.
Figure 67. Did the Test Page Print Correctly?
Check to see if the printer produced any output, and whether the output is correctly
formatted. If the test is successful, the test page should appear as shown below:
78
Figure 68. A Sample Test Page Output
If the test page prints correctly, click Yes. The printer is now installed and appears
in the Printers folder, illustrated below:
Figure 69. The New Printer in the Printers Folder
If the test page does not print correctly, one of the possible causes is that we have
selected an incorrect driver for the printer. When that happens, a click on No
automatically brings up a Help panel to offer suggestions, as illustrated below:
79
Figure 70. Windows NT Help
5.3 Printing from a WinCenter Host

In this section, we discuss the case of applications residing on a WinCenter server
wishing to print to an IBM Network Station-attached printer. In other words, an IBM
Network Station user logs on to a WinCenter server, from his or her IBM Network
Station, in order to use such Windows applications as Freelance Graphics or Lotus
Spreadsheet and requires the ability to print from these applications to a printer
attached to the parallel port of his or her IBM Network Station, as illustrated in the
figure below.
80
Figure 71. Printing from WinCenter Applications
With the availability of the LPR/LPD print support on the IBM Network Station,
applications on remote hosts wishing to print to the printer attached to an IBM
Network Station can use the standard TCP/IP LPR/LPD print facility to send print
output request to the LPD port (port 515), as illustrated in the figure below:
81
Figure 72. IBM Network Station Print Components - WinCenter
The LPR request is received and processed by the LPD daemon on the remote
IBM Network Station and the output directed at the print API by the LPD
component.
However, WinCenter applications also have the ability to print directly to the
SERIALD module of the IBM Network Station using either port 5964 for the parallel
port or port 87 for the serial port. This is accomplished by defining a WinStation
printer on the WinCenter server to represent the printer attached to the IBM
Network Station. We describe both of these methods in more detail below, starting
with the WinStation method.
5.3.1 Printing from WinCenter Using a WinStation Printer

In this case, we define a printer on the WinCenter server called a WinStation
Printer, which is a special definition representing a printer device attached to a
client (a WinStation) connecting into the WinCenter server.
This allows a WinCenter client to direct printer output back to itself by selecting a
print destination that has been defined as a device attached to itself.
In reality, this definition allows the WinCenter server to associate an IP address
(that of the client) and a device driver (specified during the definition of this
WinStation printer) with the real device attached to the client (the IBM Network
Station).
When a print request from an application is issued with the printer attached to the
IBM Network Station as the target, the WinCenter server generates the output
according to the device driver specified and then sends the output directly to the
SERIALD port by establishing a TCP connection with the appropriate port. Since
82
the output is already in the correct format for that printer, it is simply passed
through by the SERIALD module to the actual physical printer.
5.3.1.1 WinStation Printer Configuration Requirements

What do we require then, in terms of configuration, on either the WinCenter server
or the IBM Network Station in order for applications on the WinCenter server to
print on the IBM Network Station attached printer.
The configuration requirements are as follows:
1. Configure WinStations definitions on the WinCenter server in order to indicate
whether client devices, such as a printer, should be connected at logon time for
every WinStation connecting in, or whether the user configuration should be
used to determine the client device connection.
2. If we indicated above that the user configuration should be used (inherit user
configuration), then configure the user configuration, which is similar (but not
identical) to the WinStation configuration.
3. Create a printer definition on the WinCenter server to represent the actual
printer attached to the IBM Network Station. This printer definition is therefore
specific to a client and one definition is required for each client (IBM Network
Station) that has a printer attached.
4. Configure the parallel port interface on the IBM Network Station to match the
characteristics expected by the WinCenter server, which are that port 5964 is
used for the parallel port interface, port 87 for the serial port and that the
passthrough mode should be used (that is, use of the parallel protocol or serial
protocol configured as false).
These steps are summarized and illustrated in the figure below, where the
application on the WinCenter server, when making a request for printing, is
presented with a list of available printers.
83
Figure 73. WinStation Printer Configuration
One of these printers is the one called claudea#LPT1 which has been defined by
user claudea to represent the IBM 4029 printer attached to his IBM Network
Station. This identifies the printer driver that should be used and where the print
output should be sent. In this case, the destination is client/LPT1, which is an
indication to WinCenter that the printer is at a remote IBM Network Station, for
which WinCenter knows the IP address (since this is the client currently connected
as user claudea).
This triggers the establishment of a TCP connection to port 5964 of the IBM
Network Station and print output is sent on that connection, where the SERIALD
daemon passes it through to the parallel port and hence to the IBM 4029 printer.
In the following few pages, we illustrate the steps above by taking you through the
required configuration panels.
5.3.1.2 WinStation Configuration

The first step is to configure the WinStations. In the Administrative tools folder on
the WinCenter desktop, double-click the icon labeled WinStation Configuration as
shown in the figure below.
Note: This step must be done from the Console of the WinCenter server while
logged on as Administrator.
84
Figure 74. Administrative Tools Folder
Before you make modifications to the WinStations' configuration, you must ensure
that no other users are logged on. To do so, double-click on the WinStation
Administration icon in the Administrative Tools folder, and view users. If some
users are actually logged on, you can send them a message asking them to log off
or you can force them off by selecting their names and clicking Logoff.
The figure below illustrates the main WinStation Configuration panel which lists the
currently configured WinStations. In this example, we happen to have configured
six WinStations (numbered WinCenter#001-006) which use a transport mode of
WinCenter, and we also have configured four WinStations to use a transport mode
of tcp and type of Citrix ICA. In other words, six of these WinStations connect into
the WinCenter server using NCD's WinCenter protocol and four use the Citrix ICA
protocol. (We used those in our tests with Citrix Java ICA client running on the
IBM Network Station.) Notice that the console is also listed as a separate entry.
Figure 75. WinStation Configuration
Double-clicking on the WinCenter#001-006 entry brings up the following Edit

WinStation Configuration panel. Notice that this is where transport mode and type
of protocol used is configured.
85
Figure 76. Edit WinStation Configuration
Double-clicking on the Advanced button brings up the Advanced WinStation

Configuration panel illustrated in the figure below.
86
Figure 77. Advanced WinStation Configuration
On the panel above, the only information we need to focus on at this point is the
section labeled Client Devices in the bottom left-hand corner of the panel.
If every IBM Network Station using this WinCenter server has a printer attached
and you want users on that IBM Network Station to be able to use this printer when
they log on, then the entries in this section should be selected (which is the default)
the entry labeled inherit user config should not be selected.
On the other hand, if only a few IBM Network Station have a printer attached, then
you might want to set the default here for every IBM Network Station to NO (do not
connect client printer at logon) but instead use the inherit user config button to
indicate to WinCenter that it should look up the user configuration information
instead to determine whether a printer is attached or not. This latter case is the
one we chose to illustrate in our example.
5.3.1.3 User Configuration

We then need to update the user configuration to reflect the presence of a printer
that we want to connect when a user logs on. To do this, we click the User
Manager for Domains application also located in the Administrative Tools folder,
which presents the panel shown below:
87
Figure 78. User Manager
In the above panel, double-clicking on the user claudea for example opens up the
User Properties panel, as illustrated in the following figure.
Figure 79. User Properties
On this panel, notice on the bottom the button labeled Config located to the right of
the Groups button. This button is specific to WinFrame/WinCenter and allows us to
configure characteristics similar to the ones in the WinStation Configuration panel
we saw earlier, except that this panel is specific to a particular user.
Clicking on the Config button displays the panel illustrated below entitled User
Configuration.
88
Figure 80. User Configuration
Once more, the only area of interest at this point, if we talk about printing, is the
section in the bottom left-hand corner labeled Client Devices. Notice that it is
identical to the one we saw earlier in Figure 77 on page 87 except that in this case
there is no inherit user config since the user configuration is what we are looking at
now.
So in the case of this user, we do select the entries indicating that there is a printer
attached to the IBM Network Station that we want connected when this user logs
on.
5.3.1.4 Creating a Printer Definition

The next step is to create a printer definition to represent the actual physical printer
which is attached to the IBM Network Station.
Note: To create this printer, you must log on to WinCenter as the user who will be
using this printer. This can be done from either the WinCenter Console, logging on
as user claudea for example, or from an IBM Network Station logging on as user
claudea.
To create a printer, double-click Control Panel located in the Main Program group,
double-click Printers, then select PrinterCreate Printer which brings up the
panel shown below entitled Create Printer.
89
Figure 81. Create a Printer
On the above panel, leave the Printer Name field empty; it will be filled
automatically when you set the Print to field. In the Driver field, select the printer
driver that corresponds to the physical printer attached to your IBM Network
Station, and in the Print to field, select CLIENT/LPT1 for a printer attached to the
parallel port or CLIENT/COM1 for a printer attached to the serial port. Click OK to
complete.
Other characteristics can be set by clicking on the Details button, which brings up
the panel shown below.
Figure 82. Printer Details
90
Once this printer is defined, it can be managed through the Print Manager
application, as shown in the figure below. Notice that the Print Manager shows two
printers defined, one for user claudea and one for user Administrator.
Currently, the claudea#LPT1 printer is processing a print job originating from a
Freelance Graphics application.
Figure 83. Printer Manager
5.3.1.5 IBM Network Station Configuration

The last step to accomplish in order to use our IBM Network Station-attached
printer from a WinCenter application is to ensure that the IBM Network Station
configuration is correct.
This is typically not done by the IBM Network Station user but rather by the
administrator and is transparent to the user. When the user boots his or her IBM
Network Station from a boot server, the configuration files that have been set up on
the boot server or on the configuration server already should have the proper
configuration parameters to enable the IBM Network Station-attached printer.
If the user has access to the Console menus for the Setup commands, he or she
can verify that the configuration is correct by accessing the Setup parameters
menu, selecting Parallel then locating the Parallel Daemon table, illustrated in the
figure below:
Figure 84. Parallel Port
91
In the figure above, verify that the Use Parallel Protocol value reads False and that
the TCP Port shows as 5964, since this is the port that WinCenter uses to access
the print daemon.
If the serial port is the one used instead of the parallel port, then select the entry
called Serial in the Change Setup parameters menu, which brings up the panel
shown below.
Figure 85. Serial Port
Verify the entries in the Serial Daemons table to ensure that Use Serial Protocol
shows as false (it is set to true, by default, in the example above) and that the TCP
port is 87.
In the Serial Interfaces Table, the Port Use at Boot and the Current Port Use
should both be set to printer. As well, settings for Baud rate, Data Bits, Stop Bits,
Parity and Handshake should match the settings recommended for the attached
printer.
If these values are not correct, then the administrator in charge of the configuration
files for your network station should be asked to correct these values.
For test purposes, these values can be changed temporarily through the IBM
Network Station console setup panels, but remember that these changes are
temporary and will be overwritten when the configuration files are read again.
For additional details on the settings of these parameters, and for an example of
the settings of the parameters in the configuration files and how to do problem
determination, please refer to 9.9.3, Parallel and Serial Port Configuration
Parameters on page 191.
92
5.3.2 Printing from WinCenter Using LPR

Since a WinCenter server is basically a Windows NT 3.51 system, it also has the
capability to use the LPR/LPD TCP/IP Print support, as long as that particular
service is installed on the server.
An LPR print port can therefore be defined, just as we do in the Windows NT 4.0
example (see 5.2, Printing from a Windows NT Host on page 72), so that any
application can print to an LPR port, and that an LPR port can be configured to
point to a network station printer.
This is illustrated in the figure below:
Figure 86. IBM Network Station Print Components - Using LPR/LPD
The process of creating a printer definition on a WinFrame system is similar to a

Windows NT 4.0 system; however, since there are slight differences in the panel,
we briefly illustrate this process here.
From the Main folder, click on Control Panel and then Printers. This brings up
the Printer Manager panel, and from the Printer pull-down, illustrated in the figure
below, select Create Printer.
93
Figure 87. Create a Printer in WinFrame
In this example, we create a printer for the IBM 4029 printer attached to a network
station at 9.24.105.189, so we name the printer NS4029, select the IBM 4029
Laser Printer driver or a compatible driver, enter a description and select Other in
the Print to field.
Figure 88. Create a Printer in WinFrame
This brings up the Print Destination panel on which we select LPR Port. This is
94
Figure 89. Print Destinations
In the next panel, enter the host name or IP address of the destination host, and in
the field titled Name of printer on that machine enter the queue name on the IBM
Network Station, which can only be PARALLEL1 or SERIAL1, dependent on
whether the physical printer is attached to the parallel or serial port.
Figure 90. LPR Port
Back on the Create Printer panel, clicking on Details brings up the following
information.
95
Figure 91. Printer Details
When wishing to print from an application, clicking on the Print button brings up the
following panel where one can use the pull-down to choose a specific printer. In
this example, we chose our NS4029 printer; notice that the Where field displays
9.24.105.189:PARALLEL1.
96
Figure 92. Selecting a Printer
In the Print Manager window shown below, our NS4029 printer appears with an
active entry spooled. Notice the other printer called claudea#LPT1, which is the
WinStation printer we used in the other method of printing to the IBM Network
Station.
Figure 93. Print Manager
Both claudea#LPT1 and NS4029 represent the same physical printer except that
the method of sending the printed output from the WinCenter server to the physical
printer differs dependent on which printer queue is chosen. This is illustrated in the
figure below.
97
Figure 94. Accessing the Same Printer through Two Methods
Notice that when the application chooses the NS4029 printer/queue, which is
defined as an LPR port, the output is routed to the LPR requester which makes a
connection to the LPD daemon on the IBM Network Station and the output is
routed to the physical printer attached to the IBM Network Station.
Similarly, if the application chooses the claudea#LPT1 printer/queue instead, then
the output is routed through the WinStation Printer mechanism of WinCenter, which
establishes a connection directly with port 5964 of the SERIALD daemon, which
routes the output to the same physical printer attached to the IBM Network Station.
Notice that in both cases, an IBM 4029 printer driver is used on the WinCenter
machine to produce an output that is compatible with the real printer used.
5.4 Printing from an AS/400 Host

There are two main methods that can be used to print to the IBM Network Station
local printer from the AS/400 depending on the release of OS/400:
Using a remote output queue
It is possible to use a remote output queue at any release of OS/400 after
R310. This method uses the LPR/LPD printing services.
Using a device description
A device description can be used at OS/400 releases of R370 and later. This
method uses direct connections to the SERIALD daemon ports.
It is preferable to use LPR/LPD for printing to the IBM Network Station, when the
IBM Network Station is at Release 3 or later. The SERIALD instructions have been
included here only to illustrate how SERIALD works and can be used, and to
enable people with IBM Network Station Releases 1 and 2 to print.
98
5.4.1 Using a Remote Output Queue

In the following example, we are connecting an IBM 4029 printer to the IBM
Network Station. We define the printer with an output queue named NS4029.
5.4.1.1 Creating a Remote Output Queue

From the OS/400 command line we enter the CRTOUTQ command and use the F4
(Prompt) key to get the following screen:
Figure 95. The Prompted Create Output Queue Command
Output queue and Library

We need to use the QUSRSYS library, so that if it later becomes
necessary to create a dummy device description, this will be easier.
Dummy device descriptions are explained after the instructions for
creating the output queue (see 5.4.1.2, Creating a Dummy Device
Description on page 104).
Remote system
If the IBM Network Station has an assigned host name (for example,
windy.raleigh.ibm.com) then we can enter this name in the Remote
system field. Otherwise, we can specify *INTNETADR which will later
cause a prompt for the IP address.
Press Enter to get the Remote Printer Queue parameter.
Remote printer queue
If the printer is physically attached to the IBM Network Station using a
parallel cable, then specify PARALLEL1, or if the printer is attached
using a serial cable, then specify SERIAL1. In this example, we are
using a printer attached to the parallel port:
99
Figure 96. Create Output Queue Command - First Panel
Then use the Page Down key to get the next panel.
Connection type
Change this to *IP.
Destination type
This parameter is used by the AS/400 to identify the type of LPD that is
implemented on the receiving node (in other words, does the receiving
side support streaming or not).
Streaming mode
If this is set to *OTHER, it indicates a basic LPR implementation
which does not support streaming.
If this is set to *OS400, it uses an implementation suitable for talking
to other AS/400s, which includes support for streaming. This
implementation is also suitable for use with the IBM Network Station
since streaming is supported by the IBM Network Station.
In this particular example, we use *OTHER, which does not use
streaming mode.
100
Figure 97. Create Output Queue Command - Second Panel
Press Enter. We are now presented with:

Host print transform
Host Print Transform converts the spool file on the AS/400 to an
ASCII-based data stream such as PCL5 or PPDS. Set this to \YES.
See 8.3.11, Using Host Print Transform on page 177 for more
information on host print transformation.
Press Enter again, and we get additional parameters, as follows:
101
Figure 98. Specifying Manufacturer, Type and Model
Manufacturer type and model

This parameter tells the AS/400 what type of printer the output is being
sent to. This allows the AS/400 to create the correct ASCII-based data
stream. The default value is *IBM42011, but in this example we are
using an IBM 4029, so we change this to \IBM429. A complete list of
the possible values, can be obtained by pressing F4 while the cursor is
in this field.
Internet address
If we previously used *INTNETADR for Remote system, we then need to
enter here the IP address of the IBM Network Station to which the
printer is attached. In our example, this address is 9.24.14.189.
102
Figure 99. Entering the IP Address
Then page down to the last panel where we enter a text description for the printer:
Figure 100. Entering a Printer Description
Press Enter and the remote output queue is created. We see the message Object
NS429 type \OUTQ created in library QUSRSYS at the bottom of the screen:
103
Figure 101. The Output Queue Created Message
5.4.1.2 Creating a Dummy Device Description

Printers that are physically attached (for example, using Twinax) to the AS/400 use
device descriptions to store information about the printer configuration, and an
output queue to store the spool files waiting to use this printer. When using a
remote output queue, the Output Queue definition contains:
The printer configuration information, such as the IP address and the printer
type.
The queued spool files waiting to be sent to the printer.
Therefore, since a remote output queue contains all of the information required, a
device description is usually not necessary when using remote output queues.
However, a dummy device description is usually required when an AS/400
application gives the user a list of printers to choose from because applications
generate a list of printers for the user by looking at the printer device descriptions
available on the AS/400. As the remote output queues do not have a device
description, such applications are not able to list the printers attached using remote
output queues.
Sometimes, applications validate the users' choice of printer, by ensuring that there
is a device description with the name the user specified.
OfficeVision/400 is an example of an application that uses device descriptions.
A dummy device description can thus be used to satisfy the above requirements,
while still allowing the remote output queue to control sending the data to the
printer.
To create a dummy device description, type CRTDEVPRT at the command line, and
press the F4 key.
Device description
Enter the name of the device, which must be the same name as the
output queue we just created, in this case NS429.
Device class
As this is not a device description for a printer that is directly connected
to the AS/400, we use virtual - \VRT.
Device type and model
For the Device type, enter 3812 and Device model 1. We use 3812, as
this is a printer with many features. By using this value, applications are
able to use more printer features. Where possible, the Host Print
Transform functionality converts the data so that these equivalent printer
features are used on the actual ASCII printer used.
104
Figure 102. Create Device Description (Printer) Command
Press Enter to see additional parameters and to specify a font identifier:
Figure 103. Specifying a Font Identifier
105
Font identifier
In this example we use 11 which represents a Courier font at 10 CPI. A
font is required, as some applications use the default printer font. An
alternative font ID can be specified if required. For a list of font IDs
available on the AS/400, please refer to the AS/400 Printer Device
Programming, SC41-5713 which has an appendix listing the font
identifiers.
When we have finished changing these fields, we can press Enter.
When this command is run, a dummy device description is created in the QSYS
library. In addition, we receive a message Output queue NS429 in QUSRSYS
already exists This is because the CRTDEVPRT command usually creates:
A device description in QSYS library
An output queue, with the same name as the device description, in the
QUSRSYS library
The CRTDEVPRT command finds that there is already an output queue with the
same name as the device description in QUSRSYS. This is normal because we
have already created a remote output queue in QUSRSYS, containing all of the
details for printing to the IBM Network Station printer using the LPR, and the
CRTDEVPRT command cannot create a new output queue.
Figure 104. The Error Message
5.4.1.3 Starting a Printer Writer to a Remote Output Queue

A printer writer job is a job that runs on the AS/400, usually in the QSPL
subsystem, and is responsible for taking spool files from an output queue and
sending them to a printer. To start a writer job, use the STRRMTWTR command
(start a remote writer). A remote writer is a special kind of printer writer used for
sending spool files to remote systems as opposed to locally attached printer
devices.
Figure 105. The Start Remote Writer Command
When this command is run, we see a message at the bottom of the screen that
says Reader or writer xxxxxx/xxxxxxx/xxxxxx submitted to job queue QSPL in
lib..., as shown below:
106
Figure 106. Success Message When Starting the Writer
5.4.1.4 Ending a Printer Writer to a Remote Output Queue

To end a writer job, use the ENDWTR command.
Figure 107. The End Writer Command
When this command is run, a message at the bottom of the screen says Writer
xxxxxx/xxxxxxx/xxxxxx in process of ending, as shown below:
Figure 108. Success Message When Ending the Writer
5.4.2 Using an AS/400 Device Description

This is the second method that can be used; however, we remind you that it is
preferable to use the remote output queue method because it uses the LPR/LPD
protocol to communicate with the printer.
Creating a device description for an IBM Network Station is possible at releases
R370 and later of OS/400, and we include these instructions here for two reasons:
For situations where the IBM Network Stations are not yet at the Release 3
level
To explain that SERIALD can be used as an alternative in special situations
where this might be warranted.
5.4.2.1 R370, R410 and Later

At R370, PTFs are required to add functions to support IBM Network Station
printing on the AS/400. The PTF that can be ordered using the group PTF is
SF99081.
To create a device description, type CRTDEVPRT at the command line and press F4.
107
Figure 109. The Create Device Description (Printer) Command
Device description
In this example, we use the name 'NS4029'.
Device class
Enter this as \LAN because we connect to the printer through a network.
Device type and model
For the Device type, enter 3812 and Device model 1:
Press Enter to see a new parameter appear called LAN attachment. We specify
\IP, as we need to use the TCP/IP protocol.
Press Enter to see additional parameters.
108
Figure 110. LAN Attachment and Port Number Parameters
Port number
This refers to the port number on the IBM Network Station. Enter 6464
for a parallel-attached printer, or 87 for a serial-attached printer. These
port numbers are explained in 3.7, What is SERIALD? on page 43. If
a printer is attached to the serial port, then it is necessary to ensure that
the printer serial port settings match the IBM Network Station serial port
settings.
Font identifier
For Font Identifier, enter 11 which represents a Courier font at 10 CPI.
A font is required, as some applications use the default printer font. We
could use a value other than 11, if required. For a list of font IDs
available on the AS/400, please refer to AS/400 Printer Device
Programming, SC41-5713, which has an appendix that lists the font IDs.
Press Enter for more parameters and then page down to see the panel below:
109
Figure 111. Host Print Transform Parameter
The meaning of the parameters on the panel is following:

Activation timer
Specifies the amount of time to wait for the IBM Network

Station to respond to an activation request. If there is no
response, the AS/400 issues a message CPA337B asking if
the request should be retried or canceled. Choose any value
that is suitable for your environment. In this example, we
have left it at the default, 17.
Inactivity timer
This is used by the AS/400 to decide when to release the

connection. In this example, we use \ATTACH which means
that the AS/400 uses the default value for a LAN attachment,
which is 15 seconds. Different values may be suitable in
different environments.
Host Print Transform

Specify \YES, so that AS/400 data streams such as SCS and
AFPDS can be converted to ASCII data streams such as
PCL or PPDS.
Press Enter to continue.
110
Figure 112. Manufacturer Type and Model Parameter

This allows us to specify which conversion to use to transform the
AS/400 EBCDIC-based spool file to an ASCII printer-specific data
stream. In this example, we use an IBM 4029 printer, so we specify
\IBM429. This parameter can be prompted using F4 to see all of the
available conversions.
We also need to specify the paper that will be loaded into the printer. In this
example, we specify that the paper trays contain letter-sized paper and
monarch-sized envelopes.
Leave the other parameters and page down.
111
Figure 113. Remote Location Parameter
Remote location (Name or address)

In this example, we specify the IP address of the IBM Network Station,
but we can also use a host name, such as windy.raleigh.ibm.com.
System driver program
We use \NETSTNDRV. This means that when the AS/400 sends the spool
file, it knows that it is communicating with an IBM Network Station.
Text 'description'
We give the device description a meaningful text description, and press
Enter.
A message at the bottom of the screen informs us that the device description is
created:
Figure 114. Device Description Created Message
5.4.2.2 Controlling a Printer Writer for the Device Description

Controlling printing on a IBM Network Station-attached printer when a device
description is used is identical to controlling a printer which is physically attached to
the AS/400 using Twinax.
To start the printer, it is necessary to vary it on first, using the VRYCFG or
WRKCFGSTS commands.
112
Once the device is in VARIED ON status, use the STRPRTWTR command to start
a printer writer.
To end the printer, end the writer using the ENDWTR command, and then vary it
off.
5.5 Printing from a VM Host

In this section, we address the case of applications residing on a VM host wishing
to print to a printer attached to an IBM Network Station.
5.5.1 Printing a PostScript File Using the LPR Command

In this first example, we have a PostScript file generated on the VM host by
BookMaster. The file is a binary file, ready to be printed on a PostScript printer. In
our example, the file is called 5212TEST PSBIN A.
Figure 115. Printing a PostScript file from VM
To send the file to be printed on the IBM Network Station-attached PostScript

printer, we use the LPR command, as follows:
LPR
5212TEST SCRIPT A (host 9.24.14.189 pr PARALLEL1 postscript binary
The option binary is used so that the data stream will not be converted from
EBCDIC to ASCII, since the data is already in ASCII format, as produced by
BookMaster.
113
The option postscript indicates that this is PostScript data.

If we add the TYPE option after the binary option, the following messages are
displayed in the VM session, indicating the progress of the command.
lpr 5212TEST script a (host 9.24.14.189 pr PARALLEL1 postscript binary type

LPR version V2R4, Internal version id 2.3 PN7663
lpr to printer "PARALLEL1" at host "9.24.14.189"
Connected to 9.24.14.189
Data file sent.
Control file sent.
Connection closed.
Ready; T=.1/.2 12:44:47
Figure 116. Messages on VM Following an LPR Command
Simultaneously, the message log on the network station displays the following
messages:
NSC621: lpd: Starting.

NSC626: lpd: Print job memory cache size set to 275674 bytes
(1% of free memory).
NSC6218: lpd: Host 192.168.4.12 requests local host to receive a
printer job for queue PARALLEL1.
NSK81: accepting PARALLELD connection from localhost.itso.ral.ibm.com
NSK651: parallel 1: opened session from 127...1
NSC621: lpd: Print job 5212TEST.PSBIN received from host 192.168.4.12.
NSC6213: lpd: Print job 5212TEST.PSBIN from host 192.168.4.12 printed.
NSC622: lpd: Ending.
Figure 117. IBM Network Station Message Log for Print Job from VM
The steps illustrated in the figure above are:

On receipt of the connection request from the LPR daemon on the VM host,
the network station LPD daemon is started.
The LPD service then issues a message indicating that it will use only 10% of
the available free memory on the IBM Network Station for the purpose of
storing the incoming print job. The figure of 10% is the default and can be
changed using the IBM Network Station Manager.
We then see the address of the requesting host, in this case 192.168.40.120
which is our VM host, and the name of the print queue requested.
The next line (message NSK8001) indicates that the IBM Network Station is
accepting a connection from itself. (localhost is hostname of the local loopback
interface.) This is an indication that the LPD daemon is making a connection
request to the SERIALD daemon, and since both reside in the IBM Network
Station, the request is made on the loopback interface.
The next line (message NSK6501) indicates that the parallel1 port of the
SERIALD daemon has accepted the connection (from the LPD daemon).
Finally, the next two lines indicate that the job has been received from the VM
host, and then printed on the local printer.
114
5.5.2 Printing a Text File Using the LPR Command

In this case, we use a simple text file on a VM host, which we created with Xedit,
and we want to print it to our local printer attached to the IBM Network Station.
We can also use here the LPR command from the VM command line. However,
we must be aware that using the LPR command, each line is terminated with a line
feed (LF) but no carriage return (CR).
Therefore, if we use the LPR command as is, and send the output directly to the
IBM Network Station, the output will print as shown in the diagram below, with each
line indented to where the previous line ended. This is because this text file is not
processed by any program, and it is sent directly to the printer by the receiving an
LPD. (Remember that there are no printer drivers on the IBM Network Station and
that the received data must already be in the format expected by the printer.)
Figure 118. Printing a Text File from VM
One way to get around this is to use a program on the host which processes the
text data in the proper format before invoking the LPR program to send it (as we
did in the preceding PostScript example).
Another possible solution is to set the printer Auto CR after LF mode, assuming
that the printer has this capability.
115
Another way is to use an intermediate spool system that has been configured with
a printer driver corresponding to the printer attached on the IBM Network Station.
Figure 119. Printing a Text File from VM with Intermediate Spool
In the case above, the text data send by the LPR program on the VM host is
received by the intermediate spooling system, and since it is directed at the queue
corresponding to the printer which is attached to the IBM Network Station, any data
in that queue is forwarded to the destination printer on the IBM Network Station, but
before it is sent, it is processed using the printer driver, thereby adding the required
carriage return (CR) at the end of each line.
The text data should then print normally, as expected, because of the extra
processing by the printer driver.
5.5.3 Printing by Spooling to RSCS

Instead of using the LPR command directly from a VM session, it is also possible to
spool data to RSCS and let RSCS subsystem then issue the LPR request to a
remote LPD server.
This requires an LPR link definition in RSCS, such as the examples below:
116
LINKDEFINE NS429 TYPE LPR

QUEUE FIFO FO \
PARM NS429 EXIT=LPRXPSE HOST=9.24.14.24 PORT=515 PR=NS429
LINKDEFINE NSTATION TYPE LPR
QUEUE FIFO FO \
PARM NSTATION EXIT=LPRXPSE HOST=9.24.15.189 PORT=515 PR=PARALLEL1
LINKDEFINE IBM429 TYPE LPR
QUEUE FIFO FO \
PARM IBM429 EXIT=LPRXONE HOST=9.24.14.24 PORT=515 PR=IBM429
The first link definition is for a PostScript type printer. The EXIT=LPRXPSE is used
indicating that the data is binary. For a TEXT type of link, use EXIT=LPRXONE as
in the third definition.
Notice the NSTATION link definition which points to the PARALLEL1 port of a
network station at 9.24.105.189.
Once these link definitions are in place and activated, the VM user can use the
following commands to direct print output to the NSTATION spool queue.
SPOOL PRT TO RSCS

CP SPOOL TAG DEV PRT NSTATION
Instead of using the LPR command, the print command then sends the output to
RSCS which takes care of issuing the LPR request to the remote print server.
5.6 Printing from an OS/390 Host

In this section, we briefly discuss the case of applications residing on an OS/390
host wishing to print to a printer attached to an IBM Network Station.
With the availability of an LPD daemon on the IBM Network Station as of Release 3
of the IBM Network Station Manager code, it is now easier for applications residing
on an S/390 host to print to an IBM Network Station-attached printer.
Any application or subsytem that supports the LPR/LPD function is able to send
printed output to a printer attached to an IBM Network Station.
At the moment, there are three main ways to print from VTAM, CICS, IMS and from
the JES spooling system:
Using the Network Print Facility (NPF).
Using NetSpool and IP Printway (recommended).
Printing to an intermediate spool host, such as AIX, AS/400 or Windows NT to
redirect the output to the LPD port on the IBM Network Station.
117
5.6.1 Using Network Print Facility

The Network Print Facility (NPF) is a free feature of TCP/IP V 3.2 that provides
basic LPR support. It can therefore be used to send print data to the LPD daemon
on the IBM Network Station.
Note that NPF does not have LPR streaming mode send support, whereas IP
Printway does.
Figure 120. Network Print Facility
5.6.2 Using Netspool and IP Printway

Netspool and IP Printway are separately orderable products, which are also priced
separately.
These products have more functionality than NPF and should be considered as the
recommended method to print from OS/390.
One of the features of IP Printway, which is not included in NPF, is LPR streaming
support. With the latest PTF UW46928, IP Printway now supports LPR streaming
as defined in the RFC extension of the 1992 proposal. With this new
enhancement, IP Printway can use streaming mode to send print data to the
network station LPD. This IP Printway enhancement will work on all versions of the
OS/390 operating system and is available now.
Note as well that OS/390 V2R5 available March 1998 has an LPD that also
supports streaming. This function facilitates IBM Network Station LPR clients to
send print data to OS/390 LPD for printing on the host.
118
IP Printway also allows you to print directly to the port 6464 of SERIALD daemon of
the IBM Network Station. However, there should now be little use for that particular
function since LPD support is now available on the IBM Network Station.
Figure 121. NetSpool and IP PrintWay
For additional details on how to use the LPR/LPD facility in an MVS environment,
please see IBM TCP/IP V3 Release 2 for MVS Implementation Guide,
SG24-3687-03, Chapter 13 entitled Printing in a TCP/IP Network, from which the
above figures on NOF and IP PrintWay have been taken.
5.7 Printing from an OS/2 Host

With the availability of an LPD daemon on the IBM Network Station as of Release 3
of the IBM Network Station Manager code, applications on OS/2 hosts can also
print to an IBM Network Station-attached printer using the TCP/IP LPR facility.
Any application or subsytem that supports the LPR/LPD function is able to send
printed output to a printer attached to a IBM Network Station.
The LPR/LPD support available on OS/2 is somewhat similar to the one available
on Windows NT, in the sense that there are two ways to send jobs to a remote
LPD server:
Use the command line version of the LPR requester
Define a printer queue as an LPR port, and spool the data to the local queue,
which then uses the LPR to establish a connection to the remote LPD server
119
The LPD server on OS/2 can be started either from the command line, at which
time you can specify a few startup options, or it can be started using INETD which
does not allow startup options to be specified. There are a few options available.
For additional details on how to use the LPR/LPD facility in an OS/2 environment,
please refer to TCP/IP Implementation in an OS/2 Warp Environment, SG24-4730,
Chapter 10 entitled Remote Printing.
120
Chapter 6. IBM Network Station Applications Printing

Examples
In this section, we discuss local applications on the IBM Network Station, that want
to print to either a local printer or to remote print servers.
The applications concerned are:
3270/5250 emulator
NC Navigator browser
Java applications
VTxxx emulator
Figure 122. IBM Network Station Applications
In summary, the capabilities are as follows, and are illustrated in the diagram
above:
All applications, except the VTxxx emulator, can select either a local or remote
printer.
Java applications and browsers generate only PostScript output. The printer
selected by these applications must therefore support PostScript, unless you
use the transform capabilities of another host. See 8.2, Using the Transform
Capabilities of Other Hosts on page 163 for more details and an example.
The 3270 and 5250 emulators have the capability to generate either PostScript,
PCL or ASCII output.
121
When selecting a printer, the emulator looks at the data type indicated for the
selected printer and generates the output according to the data type of the
selected printer.
Note that the 3270 emulator only supports Print Screen at this time.
Note equally that these emulators can produce ASCII output and take
advantage of DBCS conversion capabilities. See Chapter 11, DBCS
Considerations on page 225 for more details.
The VTxxx emulator does not use the print APIs but sends its output directly to
the SERIALD daemon. There is a way to send output to a printer on a remote
IBM Network Station; see Appendix B, Printing from the VTxxx Emulator to a
Remote IBM Network Station on page 233 for details.
6.1 Printing from the 3270/5250 Emulator

It is possible to make screen prints (printing of the presentation space of an
emulator session) in two ways:
Using the print screen function on the host to which the user session is
connected.
This means sending a request to the host, using a Print Screen request, so that
the host is the one that prints the content of the presentation space.
When remapping the emulator keyboard, this function is called, PrintSystem().
Note that the printer queue selected on the host to receive the output of the
Print Screen operation can be defined to route the output to any remote printer,
including the one attached to the IBM Network Station from which the
command is issued.
Printing the screen through the local IBM Network Station print process.
This means asking the local processor to print the content of the presentation
space.
When mapping the emulator keyboard, this function is called PrintScreen().
In this case, as illustrated in the diagram below, the output can also be routed
to a local printer, or it can be sent to a remote printer through the LPRD
function.
122
Figure 123. Print Screen Function
When printing on the host, it is necessary to ensure that the host is correctly
configured. For example, on the AS/400, the Print Key Output will use the
QSYSPRT printer file to decide which output queue the screen print will be spooled
on.
When printing screens locally on the IBM Network Station, the user is prompted to
choose printer settings, such as Orientation and/or Form Feed, as shown in the
figure below:
123
Figure 124. 3270/5250 Emulator Print Dialog
The user may also select a different printer, by clicking the Select a Printer button.
The emulator produces either a PostScript, PCL or ASCII data stream, depending
on the value set in the printer table, either ps, pcl or asc. This value is
automatically picked up when a user selects a printer in the Printer Selector and is
configured by the administrator using the IBM Network Station Manager. See
Chapter 4, Configuration Using the IBM Network Station Manager on page 47 for
details on how to configure printers.
If the selected printer is ASCII and DBCS conversion is required, see Chapter 11,
DBCS Considerations on page 225 for additional details on DBCS.
Select a Printer
This shows the printer that is currently selected. If the button is
selected, the Printer Selector is displayed, and a different printer may be
chosen. The Printer Selector is discussed in more detail below.
Orientation
This specifies the page orientation to use, either landscape or portrait.
Form Feed
The Form Feed option is only used for printers defined as PCL or ASCII.
(To see how to define a printer as an ASCII or PCL printer, please see
4.2, Adding Printers to the Printer List on page 53.) If the Form Feed
parameter is set to Yes, then a Form Feed is issued at the end of the
printout.
Form Feed is a command that can be sent to the printer. On a laser
printer, the Form Feed command tells the printer that all the data for the
page has been received, and that the page can be printed.
If a laser printer does not receive a Form Feed command, it may display
a status of Waiting, and a button on the printer needs to be pressed in
order to print the page.
124
For example, on the IBM 4029, the printer displays 2 Waiting PCL5
and it is necessary to press the Print Buffer button on the printer to get
the printer to continue.
On a line printer, the Form Feed command tells the printer to advance
the continuous paper to the start of the next page.
Print
This accepts the print settings, and causes the emulator to print to the
selected printer.
Cancel
Ignore the changes that were made, and return to the emulator without
printing.
Figure 125. Printer Selector
6.1.1 3270 Emulator Printing Functions

The 3270 emulator available with the Release 3 level of the IBM Network Station
support enables Print Screen Support only (as illustrated in Figure 123 on
page 123).
TN3270E support for LU1/LU3 printing is currently planned for a follow-on release.
In the meantime, until the TN3270E functions become available, one possible
temporary solution might be to use the NetSpool and IP PrintWay products to
intercept the VTAM LU1/LU3 traffic, convert it to ASCII and send it to an IBM
Network Station via the LPR client.
125
Figure 126. 3270 LU1/LU3
6.2 Printing from NC Navigator

As of Release 3, only the NC Navigator browser is shipped with the IBM Network
Station software. The IBM Network Station browser, which was shipped with
previous releases, along with the Navio browser, is no longer available.
Navio is now NC Navigator
Please note that the Navio browser has had its name changed to NC Navigator,
and we are therefore using the name NC Navigator throughout this publication
to designate the Navio browser.
6.2.1 Printing from the NC Navigator Browser

The figure below illustrates the main panel for the NC Navigator browser.
126
Figure 127. The NC Navigator Browser
Note that the NC Navigator browser is only capable of printing using the PostScript
data stream.
When you use the File pull-down and select Print, the NC Navigator Browser's
Print dialog is displayed, as shown in the figure below:
127
Figure 128. The NC Navigator Browser Print Dialog
Here are a few details on the parameters:

Print To:
This gives us the choice between printing to a printer, or printing to a
file. If File is specified, the name of the file to be created must be
entered.
Printer Name
This shows which printer will be used, shown in the form
printer_queue_name@print_server. It is possible to click on the Select
Printer... button to choose a different printer using the standard IBM
Network Station Printer Selector.
File Name
This is used when Print To: File is selected. It specifies where the file
should be created. This field is greyed out until the Print To: option is
set to File. It is possible to use the associated Browse button to bring
up a dialog box which allows the user to point and click to choose where
the file will be created.
Print First/Last Page First
This specifies which page of output should come out of the printer first.
This is useful for printers that stack pages face up. Depending on the
printer used, this can be set to ensure that the printed pages are in the
correct order, when the printing is completed.
Orientation
This specifies whether portrait or landscape paper orientation is to be
used.
Print Greyscale or Color
This specifies whether the PostScript data stream generated will be
prepared for a color printer. If there is only a monochrome printer
available, then Grayscale is a more efficient choice because the
generated output is smaller.
Paper Size
This specifies the paper size that the PostScript data stream will be
generated for.
128
NC Navigator remembers the paper preference for a user in the NC

Navigator file for that user, so that when the user next uses the print
function, the print preference can be recalled. These settings are
remembered, even if the IBM Network Station is rebooted and the user
logs back in, because they are stored in a file on the boot server.
The Print button is used to print the data. Cancel is used to cancel the print
operation.
6.2.1.1 Printing from Navio (Prior to Release 3)

Prior to Release 3, the NC Navigator browser print dialog was fairly similar except
that it did not have the ability to select a printer. The printer choice was hard
coded as local printer, as shown below:
Figure 129. The NC Navigator Browser Print Dialog in Release 2
6.2.2 Printing from the IBM Network Station Browser

The IBM Network Station Browser was an additional browser that could be used
instead of the NC Navigator browser in releases prior to Release 3. This browser
supported PostScript printing on the local parallel port.
Note - IBM Network Station browser is not shipped in R3
Please note that the IBM Network Station browser is no longer shipped as of
Release 3. However, we mention it here for the sake of completeness and for
those users that might still operate at a release prior to Release 3.
The IBM Network Station browser had a print dialog which was substantially
different from the NC Navigator browser. Below is the representation of the IBM
Network Station print dialog in Release 2:
129
Figure 130. The Network Station Browser Print Dialog
There is a button labeled Printers under the caption Current Printer: Local parallel
attached printer. Clicking on that button brings up an additional panel entitled
Printer List on which there is only one choice, which is Local parallel attached
printer as shown below.
Figure 131. The Network Station Browser - Printer List
6.3 Printing from Java Applications

This chapter briefly outlines the way in which Java applications print on the IBM
Network Station.
This chapter is not intended to be a guide to writing Java applications that print.
For detailed information regarding printing in Java, the reader should refer to Java
reference information, such as The Java AWT Reference from O'Reilly, by John
130
Zukowski and the Sun Java Web site

http://java.sun.com/products/jdk/1.1/docs/guide/awt/designspec/printing.html.
Printing in Java was introduced in Java 1.1.
The Java implementation on the IBM Network Station uses the same method as
other Java implementations. The IBM Network Station-specific print APIs are
automatically be used without any IBM Network Station-specific code being
required in the Java application.
By using the APIs, the standard Java Print Dialog and the IBM Network Station
Print Selector are used. Using the Print Dialog and Printer Selector means that the
printing interface is consistent across Java applications, and therefore makes the
user interface for the applications more intuitive.
Below is a representation of the Print Dialog which gets presented to the user when
printing from a Java application:
Figure 132. Print Dialog on IBM Network Station
Copies
This specifies the number of copies to be printed.
Print to
The user can choose between:
Printing to a Printer.
131
The default printer that will be used is shown. If we wish to select

another printer, we can click on Browse to start the Printer Selector.
The Printer Selector is discussed in 3.4.2, The Printer Selector on
page 34 below.
Printing to a File.
If Print to File is used, then we must specify the path and name for
the file to be created, and we must ensure that the File Services
have been correctly configured on the IBM Network Station to allow
access to a remote file server.
If Print to File is selected, the Copies, Printer and Banner Page Title
options are grayed out to indicate that these are ignored.
Banner Page Title
We can use this to specify the title used for printing banner pages.
Print Command Options
This is currently grayed out.
It is only included to retain a consistent look and feel with the UNIX Java
Developers Kit Print Dialog. The IBM Network Station does not use the
Print Command Options field.
Paper Size
This is used to decide what paper size will be used. It is currently
possible to specify Letter, Legal, Executive and A4.
Orientation
We can use this to determine which page orientation to use.
There are two buttons at the bottom of the Print Dialog, Print and Cancel.
Print produces the requested print, and then returns the user to the application.
Cancel cancels the print operation, and then returns the user to the application.
Figure 133. Printer Selector on IBM Network Station
In addition, using the Printer Selector means that users have the ability to print to
any of the printers that have been made available to them by the administrator.
They can print to local or remote printers.
132
All printing using Java generates a PostScript data stream on the IBM Network
Station.
Page layout is the responsibility of the application, not the IBM Network Station.
This is the same in all implementations of Java.
Note that Java applications do not have any restrictions, security-wise, when it
comes to printing. However, printing from applets instead of applications does come
with some restrictions.
This is because applets are usually loaded over the network and are therefore
considered to be untrusted. For this reason, Web browsers and applet viewers
restrict what an applet is allowed to do. For example, one of the restrictions is that
they are prevented from creating print jobs, as they would have the ability to print
anything to the printer. This is a restriction imposed by the Java APIs, not by the
IBM Network Station implementation.
In Java 1.1 however, you can get around these restrictions by using a digital
signature on the JAR file, which is an archive file that contains the applet or
applets. When a JAR file is signed by a trusted entity (the user specifies what is a
reliable source), the applet may then be allowed to perform operations, such as
printing, that are not available to unsigned applets.
A Java application can be written to keep the printer settings used, by storing the
returned data from the print function. This enables an application to remember
which printer and paper size and orientation it last used, and to store this
information. Next time the user signs on to the application, he or she can retrieve
these settings, and set them as the defaults for the next print request. This can be
extremely useful in countries that use A4 paper; the user only has to change the
Letter paper size to A4 once, and the application stores this setting as the default.
6.3.1 An Example of a Java Program That Prints

The following example illustrates how the IBM Network Station print APIs are called
automatically by the Java implementation. It is not intended to explain how to
implement printing in a user-written Java application.
This small Java program (for which we supply the source code below) displays a
window with a Print button, as shown here:
Figure 134. SimplePrint - Sample Java Application Window
When users click on the Print button, they see the Print Dialog, and from here are
able to browse the printers and select the desired printer.
133
The output for the printer is produced in PostScript. Here is what the output looks
like when printed on an IBM 4029 printer:
Figure 135. SimplePrint Sample Output - IBM 4029 Printer
When the output is printed, it is possible that some of the output may be missing
near the edge of the page, as it appears in the figure above. This is due to
unprintable borders that are a limitation of the printer used, and the size of the
unprintable borders vary between different models of printer. Unprintable borders
are an effect of the hardware design of the printer.
Note that it is the responsibility of the Java application developer to take into
account the unprintable area. Advanced Java applications, such as eSuite for
example, take the unprintable area into account and produce high quality print
output from Java.
In fact, if the same output was sent to a file instead of directly to the printer, and
then the output is examined with a program like GSView32 for example, the output
looks like it should normally, as illustrated below. This is also how it prints when
printed on an IBM3130 printer for example.
Figure 136. SimplePrint Sample Output - Print to File
Here is the source code for the very simple Java program called SimplePrint which
we used to test printing from Java on the IBM Network Station, as we just
illustrated above:
134
import java.awt.\;
import java.awt.event.\;
public class SimplePrint extends Frame {
Button printButton, closeButton;
public SimplePrint() {
add(new Label("A Simple Java Printing Application"), "North");
add(printButton = new Button ("Print"), "West");
printButton.addActionListener( new PrintCommand() );
add(closeButton = new Button ("Close"), "East");
closeButton.addActionListener( new CloseCommand() );
pack();
}
public static void main (String args[]) {
SimplePrint sP = new SimplePrint();
sP.show();
}
class CloseCommand implements ActionListener {
public void actionPerformed (ActionEvent e) {
System.exit ();
}
}
class PrintCommand implements ActionListener {
public void actionPerformed (ActionEvent e) {
PrintJob pjob = getToolkit().getPrintJob(SimplePrint.this, "Simple Print", null);
if (pjob != null) {
Graphics pg = pjob.getGraphics();
if (pg != null) {
printAll(pg);
pg.dispose();
}
pjob.end();
}
}
}
}
Figure 137. A Sample Java Print Program
6.4 VTxxx Emulator

The VTxxx emulator that you can use to telnet to another host for example allows
the user to print a copy of the presentation space or a selected portion of the
presentation space to the local serial or parrallel printer.
These choices are available on the File pull-down on the emulator menu bar, and
the output is ASCII only.
However there is a way to configure an entry on the pull-down menu of the VTxxx
emulator in order to send output to a printer attached to a remote IBM Network
Station. See Appendix B, Printing from the VTxxx Emulator to a Remote IBM
Network Station on page 233 for an explanation and example of this function.
135
6.5 Printing from Lotus eSuite

The Lotus eSuite application is a Java application and therefore uses the standard
Java classes for printing. Therefore, all considerations applicable to Java
applications also apply to eSuite.
136
Chapter 7. Printing from an IBM Network Station to Remote

Print Servers
This chapter explains the preparations required on remote hosts in order to receive
print requests generated by applications on an IBM Network Station.
Print requests received from an IBM Network Station can be printed to printers
locally attached to the remote print servers, as illustrated in the figure below:
Figure 138. Printing to Remote Print Servers
However, note that all these systems also have the ability to have printers queues
defined that represent printers located on other remote print servers. Therefore, a
print job can be spooled locally on a remote print server, and then re-routed to a
further remote print server. An example of this situation is provided in Chapter 8,
Practical Examples on page 161.
Generally, to print from the IBM Network Station to a remote system, it is necessary
to:
1. Ensure that an LPD daemon is started on the remote system.
Since the IBM Network Station uses LPR requests to send print jobs to remote
hosts, any host that runs an LPD daemon is able to receive print requests from
the IBM Network Station.
2. Ensure that the remote system is configured to accept print requests (access
control) from the sending IBM Network Station.
On some host systems, it is possible to control access to the LPD daemon
based on an IP host name for example. However, if such an access in not a
137
configurable item, then basically any remote host is allowed to send print
requests.
3. Know the queue name on the remote system of the printer to be used as a
target printer.
Most systems define in their print subsystems, multiple logical printers or
queues. These queue or printer names must be specified in the print job
requests in order for the target system to route output to the appropriate printer.
4. Know the IP address or Host Name of the remote print server.
5. Configure remote printers using the IBM Network Station Manager so that they
appear in the Printer Selector panel on the IBM Network Station where the user
chooses a target remote printer.
7.1 Printing to a Windows NT Server

Since the IBM Network Station is using LPR requests to send print requests to
remote hosts, a Windows NT server destined to function as a print server must
have the TCP/IP Printing Services installed in order to accommodate LPR requests.
In addition, the LPD Service must be started and active in order to listen for
incoming LPR requests.
7.1.1 Is the LPD Installed and Running?

You can verify that the LPD daemon is installed and running on the Windows NT
system by verifying its status in the active services. To display the Services panel,
select StartSettingsControl PanelServices.
Figure 139. The Windows NT Services Window - TCP/IP Print Server
If TCP/IP printing is installed, a TCP/IP Print Server entry appears in the Services
list, as illustrated in the figure above.
However, it may be that the TCP/IP print services are installed but that the LPD
daemon (print server) has not been configured to start automatically, or has been
shut down.
138
If the status is not indicated as Started, then select the TCP/IP Print Server entry
and click on Start. It is also possible to ensure that the TCP/IP print server starts
automatically at Windows NT boot time by selecting the Startup... button, and
selecting a Startup Type of Automatic in the Service dialog box.
If the Services panel does not have a TCP/IP Print Server entry, then you need to
install the TCP/IP Print Services. The procedure for installing this component is
described in 5.2.1, Installing TCP/IP Printing Services on page 72.
7.1.2 Verifying Access Authority to Printers

By default, in Windows NT, printer access permissions are set so that everyone
has access. Permission is granted on a per user (NT user) basis or per group (NT
group) basis.
It is possible to set the Everyone permission to No Access, in which case all LPR
requests, no matter where they originate from, will be accepted. However, it is not
possible to restrict access to a particular print queue on a hostname basis.
7.1.3 Choosing the Windows NT Printer Queue to Receive Print

To see which printers are available to use on the NT server, select
StartSettingsPrinters to display the window containing all the printers defined
on the system.
The names appearing under the icons represent both the printer name and the
queue name since in Windows NT a printer is a queue.
In this window, we can see all of the available printer queues. We need to make a
note of the printer/queue name to which we want to send print to; note that the
spaces in the printer/queue name are to be specified as is when using that queue
name in the definitions on the IBM Network Station. When selecting a queue,
remember that the IBM Network Station applications usually generate PostScript
data and that a PostScript-capable printer must therefore be selected.
7.1.4 Adding a New Printer to a Windows NT Server

If there is a need to add a new printer/queue to a Windows NT system, click on
StartSettingsPrinters and click on the Add Printers icon, which starts the
Add Printer Wizard. On the first panel, a selection is made as to whether this is a
local printer or a network printer.
Chapter 7. Printing from an IBM Network Station to Remote Print Servers
139
Figure 140. Add Printer Wizard
Select My Computer, which is the default, and you are presented with a list of
ports to select.
Figure 141. Select a Printer Port
In this case, this is a local printer attached to the parallel port so we select LPT1
and click on Next, which displays the panel to select a specific printer type.
140
Figure 142. Select a Printer Type
In this case, we select an IBM 4029LaserPrinter. Since this is a printer type for
which we already had a driver installed, we get a question as to whether we want
to keep the same driver, to which we reply Yes.
The next panel asks us to name the printer. This is the name that is specified by
remote LPR requesters as the target queue name when they want to send printer
output to this printer.
141
Figure 143. Name the Printer/Queue
You can also specify here whether that printer is now the default printer on this
machine. We selected No.
The next panel is to specify whether we want to make this printer available on the
network as a shared printer. We reply No because we intend to make this printer
available through the TCP/IP LPD service as opposed to using the NetBEUI facility.
Figure 144. Shared Printer
142
This task of defining a new printer is basically completed. You get asked if you
want to print a test page. We select No, and the printer gets added to our Printers
folder.
That procedure was for a local parallel port attached printer. If you want to define a
network printer instead, select Network Printer Server on the first Add Printer
Wizard panel (Figure 140 on page 140), which then presents you with the following
panel:
Figure 145. Adding a Network Printer
Here, you have a choice of directly entering the name of the network printer, if it is
known, in the Printer field. This has the format \\servername\printername. In this
example, we chose the IBM4029 printer defined on the NSTATIONSERVER
machine.
The other alternative is wait for Windows NT to expand the list (assuming the
Expand by Default check box is selected) and to display a list of shared printers on
the network.
Notice that our IBM4029 appears in the list. It has a share name of IBM4029CB
and is located on the NSTATIONSERVER machine in the NSTATIONDOMAIN
domain. Selecting it automatically fills the Printer field with the correct network
name.
Notice that this share name is what you were being asked about when we defined
a local printer in the previous example. If we had indicated that we wanted this
printer shared, and specified a share name of IBM4029XX, then this printer would
143
appear in this list under the name \\servername\IBM4029XX when other machines
on the network search for shared printer resources.
This printer is then added to the Printers folder with the name IBM4029 on
NSTATIONSERVER.
7.2 Printing to an OS/400 Host

If the target printer chosen on the IBM Network Station by the user resides on an
OS/400 system, you can verify that the AS/400 system is ready to receive these
requests with some of the following tasks.
7.2.1 Is LPD Active on the AS/400?

To check whether the OS/400 system is ready to accept LPR requests from remote
systems, we need to verify that an LPD daemon is active. This is accomplished by
verifying that an LPD job is running.
The LPD jobs are named QTLPDxxxxx, where xxxxx is a unique number. These
jobs run in the QSYSWRK subsystem. To see if there are any of these jobs
running, enter the command WRKACTJOB SBS(QSYSWRK).
This brings up the Work with Active Jobs screen, and shows all of the jobs running
in the QSYSWRK subsystem. We can then page down through the list of jobs and
check that there is a QTLPDxxxxx job running. In the figure below, we can see
four LPD jobs waiting, which are the last four jobs in the list:
There are multiple jobs running here because there are multiple LPD servers.
Additional servers can be started specifically or they can be automatically started
by the OS/400 as required.
Figure 146. Work with Active Jobs, Showing QTLPDxxxxx Jobs Running
144
7.2.2 Starting the LPD on the AS/400

There are two ways of starting the LPD on the AS/400:
Using Start TCP/IP Server (STRTCPSVR), to start the LPD only.
Using Start TCP/IP (STRTCP), to start TCP/IP services, including the LPD.
7.2.2.1 Starting TCP/IP Server (STRTCPSVR)

The LPD server can be started from the command line, using the STRTCPSVR
*LPD command.
7.2.2.2 Starting TCP/IP (STRTCP)

We can configure the LPD to start automatically whenever the STRTCP command
is used. The advantage of doing this is that STRTCP is normally incorporated into
the startup program on the AS/400, so that it starts automatically at Initial Program
Load (IPL).
On the command line, type CFGTCP and press Enter to reach the Configure TCP/IP
screen. From this screen, select option 20, Configure TCP/IP applications which
brings up the Configure TCP/IP Applications screen. Then choose option 13 to
Change LPD Attributes, which displays the following panel:
Figure 147. Changing LPD Attributes
We see two attributes, Autostart servers and Number of initial servers. We can set
Autostart servers to \YES in order to specify that LPD jobs should start automatically
when STRTCP is run. The Number of initial servers is used to specify the number
of LPD servers to start when the STRTCP command is executed. This can be set
at a low value since OS/400 automatically starts extra LPD jobs if it determines that
they are needed. In this example, we have set Number of initial servers to 2.
Once this has been configured, the STRTCP command starts LPD with the number
of jobs we specified.
145
7.2.3 Verifying Access Authority

There isn't a way, in OS/400, to control access to the LPD daemon based on a
host's IP hostname (at least not as far as we could determine).
7.2.4 Choosing the AS/400 Output Queue to Receive Print Requests

When the IBM Network Station sends output to the AS/400 using the LPR, it must
specify the AS/400 output queue in which the output should be placed.
To see a list of all of the available output queues on the AS/400, type WRKOUTQ \ALL
and press Enter, which displays a panel similar to the one shown below:
Figure 148. Work with All Output Queues
Simply make note of the appropriate queue that you want to use and specify that
name in the remote printer entries that you configure in IBM Network Station
Manager.
7.2.5 Adding a New Printer to the AS/400

If the OS/400 does not have the type of printer queue that you need, you can add
such a queue to the system if required.
The AS/400 supports many different printers, with many different connections and it
would be impractical to include instructions for adding all the different possible
types of printers here. However, we include a simple example here as a general
guide.
The following example shows how to add a device description for an IBM Network
Printer 17 attached to a token-ring network. This example is specific to an IBM
Network Printer, and will not work for other models of printer, but it gives an idea of
the steps involved to add a printer.
146
More information on this topic can be found in AS/400 Printer Device Programming,
SC41-5713 and in AS/400 Printing V, SG24-2160.
The IBM Network Printer used in the example has a host name of
astnp17.havant.ibm.com and is loaded with A4 paper.
Type CRTDEVPRT and press F4 to bring up the Create Device Desc (Printer) screen.
Enter the values below for the fields shown. Leave all of the other parameters as
the defaults.
Device description
This is the name which will be given to the printer. In this example, we
have used HAVANTNP17.
Device class
This is the type of connection used for the printer. For a printer
attached to the token-ring we use \LAN.
Device type
We use 3812. For an explanation of why we use this value, please see
5.4.1.2, Creating a Dummy Device Description on page 104.
Device model
We use 1.
LAN attachment
We are using TCP/IP, so we use \IP for this value.
Port number
This is the IP port number for the Printer Job Language (PJL) interface.
In the case of the IBM Network Printer, this is port 251.
Font Identifier and Point Size
We use 11. For an explanation of why we use this value, please see
5.4.1.2, Creating a Dummy Device Description on page 104.
Form feed
The IBM Network Printer uses trays of cut sheet paper, so we use
\AUTOCUT.
147
Figure 149. Create Device Desc (Printer) - 1 of 3
Activation timer
The amount of time in seconds to wait for the device to respond. If it
does not respond in this time, an error will be generated. We use the
default value of 17.
Inactivity timer
The amount of time the AS/400 will keep a connection to the printer
when it has finished printing all the jobs on the printer queue. We use
the value of \SEC15 for 15 seconds.
This value determines whether EBCDIC spool files (such as, SCS and
AFPDS) should be converted into ASCII by the AS/400. In this
example, we use \YES.
We use the value for the IBM Network Printer 17, which is \IBM4317.
Paper source 1 and 2
The printer is loaded with A4 paper, so we specify \A4.
Image configuration
This specifies the type of data stream which this queue should produce.
In this example, we are using an IBM Network Printer 17 which supports
PCL at 600 DPI, so we use \IMGA2. For a more detailed explanation of
the Image configuration parameter, please see 7.2.6, Data Stream
Conversion on the AS/400 on page 150. By specifying this value, we
enable a feature of the AS/400 which converts printer data streams. If
PostScript data is sent to this queue, it can be converted to PCL
automatically by the AS/400.
148
Remote location
This is the IP address or the host name of the printer. In this example,
it is astnp17.havant.ibm.com.
System driver program
To control an IBM Network Printer, we use \IBMPJLDRV.
Text 'description'
This is a meaningful description of the printer. In this example, we use
IBM Network Printer 17 in Havant.
149
Once the device description is created, it is necessary to vary it on, using either
VRYCFG or WRKCFGSTS. For example:
VRYCFG HAVANTNP17 \DEV \ON
Once it is varied on, the print writer must be started using STRPRTWTR. For
example:
STRPRTWTR HAVANTNP17
If it is necessary to turn the printer off, we end the writer, using ENDWTR
HAVANTNP17, and then vary the printer off, using VRYCFG HAVANTNP17 *DEV
*OFF.
7.2.6 Data Stream Conversion on the AS/400

At the OS/400 R420 and later, the system can perform some conversions on the
data stream. For example, the AS/400 can convert PostScript Level 1 to the IPDS
or PCL data streams.
This is particularly useful when using the IBM Network Station, as most IBM
Network Station applications can only generate PostScript output. Using the image
print transform functions, it is possible to use existing AS/400 printers, instead of
upgrading to PostScript-capable printers. It is also possible to use the AS/400 to
convert spool files, to be sent on to other systems.
It is possible to convert spool files created on the AS/400 or which have been
created on another system and then sent to the AS/400. Once the conversion has
been performed, it is possible to print to an AS/400 printer, or to send the
converted spool file to another system to be printed.
In brief, the transform can be specified by setting the parameters in the device
description or remote output queue on the AS/400. For example, to change a
device description to convert PostScript to PCL5, we change the following
parameters on the device description:
This must be set to *YES to enable the transformation of spool files on
this queue.
Image configuration
This value is used to determine what the data will be transformed to.
There are many possible values for this parameter, and for each
different model of printer, we need to select the correct value. In
general:
*IMGA01 - *IMGA09 are for PCL printers.
*IMGB01 - *IMGB15 are for PostScript printers.
*IMGC01 - *IMGC11 are for IPDS/AFP printers.
*IMGD01 - *IMGD11 are for printers which support PCL and
PostScript.
For a complete list of all of the Image configuration objects, please see
Appendix A, Special Values of Image Configurations (AS/400) on
page 229, AS/400 Printer Device Programming, SC41-5713, and
AS/400 System API Reference, SC41-5801.
150
As an example, *IMGA02 would be used for 600-DPI PCL printers, such

as:
HP LaserJet 4, 5 and 6
IBM Network Printer 12, 17 and 24
Lexmark Optra S
Xerox 4230 DocuPrinter
In the following screen we are changing an existing output queue to an IBM
Network Printer 17. We are specifying Host Print Transform as \YES and Image
configuration as \IMGA2:
Figure 152. Changing Remote Output Queue to Allow Conversion from PostScript to PCL
For more information on Image Print transform, please refer to IBM AS/400 Printing
V, SG24-2160.
7.3 Printing to an AIX Host

If the target host for an LPR request from the IBM Network Station is an AIX host,
the following tasks can be accomplished on the AIX system to verify that the
required facilities are available.
7.3.1 Is the LPD Active on AIX?

To verify that an LPD server is running on AIX, start System Management and
choose Print Spooling.
The System Management program is started by typing smit or smitty at the
command line, and pressing Enter. From the Print Spooling screen, choose
Manage Print Server and then Show Status of the Print Server Subsystem.
This brings up a screen, such as the one displayed in the next figure, where we
can check that the status of the LPD:
151
Figure 153. Show Status of the Print Server Subsystem
7.3.2 Starting LPD on AIX

If the LPD job is not active, it can be started from the Manage Print Server panel
using the Start the Print Server Subsystem (lpd daemon) option.
7.3.3 Verifying Access to AIX Printers

To ensure that the IBM Network Station is granted access to the AIX system in
order to send print requests, type smit and select Print Spooling in the System
Management program which displays the choices shown below:
Figure 154. Print Spooling Menu
152
Select Manage Print Server, which displays the following menu:
Figure 155. Manage Print Server Menu
Select List all Remote Clients with Print Access to bring up a panel where we
can verify that the IBM Network Station is listed as a client that has print access to
AIX. In the example below, there is only one entry (itsonct1.itso.ral.ibm.com).
Figure 156. List of Remote Clients
153
7.3.4 Enabling Print Access on AIX

If the IBM Network Station is not listed in the list of clients that have been granted
print access, you can add an entry by selecting the Add Print Access for a
Remote Client option on the Manage Print Server menu.
Figure 157. Add Print Access for a Remote Client
Simply enter the host name of the client being granted access.
7.3.5 Choosing the AIX Printer Queue to Receive Print Requests

To find out which printer queues exist on AIX, start smit, and choose Print
Spooling, and from the Print Spooling panel select List All Print Queues. This
brings up a screen with a list of all the print queues, as illustrated below:
154
Figure 158. List All Print Queues
From this list, choose a PRINT QUEUE name and use that name in IBM Network
Station Manager as the queue name of a remote printer definition.
7.3.6 Adding a New Printer to the RS/6000

If the print queue you wish to use is not in the list of available queues, you can add
a printer queue to the AIX system with the following procedure.
Go back to the Print Spooling menu and select Add a Print Queue. You get a
panel on which you need to select the attachment type.
Figure 159. Local Attachment Type
155
Say we want to define an IBM 4039 Laser Printer attached to the parallel port.
Select the attachment type as Local, and you get a list of printer types, as shown
below:
Figure 160. Printer Types
In this case, select IBM and you get a list of different printers to choose from.
Figure 161. Printer Selection
Select the IBM 4039. At this point, if the proper software to support this printer is
not installed, you are asked if you want to proceed with the installation of the
required software. You must have access to the source files for these printer
drivers and you can follow the instructions for the installation.
If the proper drivers are already installed, you are asked for the interface to which
the printer is attached.
156
Figure 162. Interface Selection
In our example, we choose Parallel, which brings up the next panel asking for the
parent adapter.
Figure 163. Parent Adapter
There is only one choice so we press Enter to get the next panel.
157
Figure 164. Entering a Print Queue Name
Since this printer supports both PostScript and PCL, we have entered a queue
name for each of these options. We used the names IBM4039PS for the PostScript
queue and IBM4029PCL for the PCL queue.
Pressing Enter displays a panel that shows the command to create the queue is
running. When it completes, the printer we just added shows as Added printer lp0
along with the two queue names we created for this local printer.
Figure 165. Printer Queue Added
The queue names of IBM4039PS and IBM4029PCL can now be used as target
queues when defining remote printers in the IBM Network Station Manager.
158
7.4 Printing to an OS/2 Host

7.4.1 Is the LPD Active on OS/2?
You can verify if the LPD is running on OS/2 by either looking at the tasks list to
see if there is an LPD.EXE started, or you can issue the netstat - s command and
look to see if the LPD service is listening on port 515.
7.4.2 Verifying Access Authority to the LPD

The OS/2 system does not have a facility to restrict access to the LPD server
based on the host name requesting the print job.
7.4.3 Starting the LPD on OS/2

The LPD service on OS/2 can be started from the command line using an LPD
command. Issue lpd -? for the available options.
The LPD service can also be started using INETD, in which case startup options
are not available.
7.4.4 Choosing the OS/2 Print Queue to Receive Print

The printers available to the LPD daemon are all the printers defined in OS/2. To
see which printers have been defined, open the Connections folder and the Printers
folder. The name that should be used on the requesting LPR is the physical name
of the printer. This is the name that appears in the Physical Name field when you
open up Properties of the printer.
7.5 Printing to an S/390 Host

For details on how to use the LPR/LPD facility in an MVS environment, please see
IBM TCP/IP V3 Release 2 for MVS Implementation Guide, SG24-3687-03, Chapter
13 entitled Printing in a TCP/IP Network.
159
160

This section deals with some examples where we address considerations
associated with the fact that the IBM Network Station does not have any spooling
capabilities or in fact any local disk storage capabilities.
In some cases, implementation can be made in such a way as to take advantage of
the capabilities of other hosts to enhance the printing capabilities of the IBM
Network Station user.
We describe here some of these considerations, and in particular, build a scenario
of a fictional company where we implement some of the facilities that have been
described in earlier chapters.
8.1 Using the Spooling Capabilities of Other Hosts

Because the IBM Network Station itself does not have the capability to store printed
output on a local disk, it does not have the capability to spool print jobs.
One of the drawbacks to this is that a user who has already sent a print job to the
local printer is not able to send another one until the first job has finished
processing.
If the printer usage is a casual one, with small and infrequent print jobs, there might
not be a problem, but if a user has many print jobs to submit, or large print jobs,
then the wait time between each attempt to send a print job can be eliminated by
taking advantage of the spooling capabilities of other hosts.
In this way, the user can queue any number of print jobs to the spooling system of
the other host, which takes care of scheduling the jobs to be sent back to the local
printer.
Another advantage of this method is that it provides the capability to use a large
variety of printers on the IBM Network Station. Indeed, if for example, the remote
host used as an intermediate spooling system is a Windows NT system, then any
printers supported by Windows NT can be attached to the IBM Network Station.
The IBM Network Station itself does not have the printer drivers for the printer used
but the Windows NT system does, and it is the Windows NT printing subsystem
that controls the printer.
Let us first illustrate the example of a user who does have a printer attached to his
or her IBM Network Station and who has a very frequent need for printing. We give
this user the capability to spool by using a remote print server, yet directing the
output back to his or her printer. In this specific case, we use a Windows NT print
server, but other hosts with better spooling capabilities can be used as well.
The following figure illustrates this scenario:
161
Figure 166. Local Printing via Remote Spooler Host
In the figure above, a local application on the IBM Network Station wishes to print
to the local printer. If the user selects, in the Printer Selection window, the local
PARALLEL1 printer, the printed output is sent to the API for local printing, as
indicated by the circle labeled 1 in the diagram.
Instead, we have prepared a printer definition on a Windows NT server to represent
the printer on the IBM Network Station. We have done this by defining an LPR
port, giving it the name NS4029, associating an IBM 4029 printer driver to it, and
indicating that the destination of this LPR port is the LPD residing on the network
station host and queue PARALLEL1.
See 5.2, Printing from a Windows NT Host on page 72 for an example of how to
define an LPR port on a Windows NT server to represent a printer attached to a
IBM Network Station.
See also 7.1, Printing to a Windows NT Server on page 138 and 7.1.1, Is the
LPD Installed and Running? on page 138 for instructions on how to prepare a
Windows NT system to receive print jobs through LPD.
This printer definition (NS4029 on the Windows NT Server host) has been added
by the administrator as a selectable printer destination on the IBM Network Station.
Therefore, when the user wishes to print, he or she selects the NS4029 printer
definition, which causes the IBM Network Station to send the output to the LPR
daemon, which transmits it to the LPD daemon on the Windows NT server. At that
point, the print job is queued for the NS4029 destination. When the printer becomes
available, the job is spooled to the LPR port thereby making its way back to the
162
IBM Network Station via the LPR on the Windows NT system and the receiving
LPD on the IBM Network Station, and printed on the IBM Network Station printer.
The result is that the user has been able to send multiple print jobs, in succession,
without waiting each time for the previous print job to terminate. Therefore he or
she is using the Windows NT server as a buffer, accumulating print jobs, large or
small, and delivering them automatically as the printer becomes available.
A variation of the previous example might be an office with many IBM Network
Stations but with only one of the network stations having a printer attached.
In this situation, all IBM Network Station users direct their printed output to a
specific queue on the remote print server/spooler, which manages all jobs going to
the shared office printer, as opposed to each individual IBM Network Station user
sending his or her print output directly to the IBM Network Station to which the
office printer is attached.
This is illustrated in the diagram below:
Figure 167. Printing via Remote Spooler Host to a Centralized Printer
8.2 Using the Transform Capabilities of Other Hosts

The AS/400 system, for example, has the capability to transform one data stream
into another.
If IBM Network Station applications generate PostScript data, but you only have a
PCL type printer attached to the IBM Network Station, the print request can be sent
to the AS/400, transformed from PostScript to PCL, and routed back to the IBM
Network Station PCL printer.
163
An example of this situation is described in the Blundies scenario which follows.
8.3 A Sample Fictional Scenario - The Blundies Company

This scenario of a fictional company called Blundies is used to further illustrate
some of the various situations discussed previously in this document. It attempts to
define what could be a typical and practical office environment, and how some of
the printing capabilities could be designed to provide users with the functions they
need.
8.3.1 Introducing Blundies

Blundies is a small company that uses AS/400s and has just acquired some IBM
Network Stations for the users in the Payroll department.
The Payroll department at Blundies uses an AS/400 application to print pay slips
and checks at the end of each month.
There are four people in the Payroll department: Marvin, the manager, and his
three employees, Ravi, Michael and Linna.
They are all migrating to using IBM Network Stations. They already have several
printers, and they do not want to acquire more printers at the moment.
The IBM Network Stations are used for:
5250 emulation sessions to the AS/400
Using the Intranet, and accessing the Internet with a browser
Lotus eSuite for e-mail and word processing
They have an IBM 6400 printer, attached directly to the AS/400 using Twinax,
which is only used for printing checks and pay slips.
They have an IBM Network Printer 17 attached directly to the LAN and used as a
shared printer. It has the PostScript feature installed so that it can handle both
PCL and PostScript data streams.
There is also an IBM 4029 PCL printer that Marvin would like to use as his
personal printer.
The office network environment is illustrated in the figure below:
164
Figure 168. Network Diagram for Blundies
8.3.2 Nomenclature Used

Blundies already has a TCP/IP network setup, and they use the domain name of
blundies.com.
The AS/400 is called PAYROLL, and its host name is payroll.blundies.com.
The IBM Network Stations are given the names PAYNS01, PAYNS02, PAYNS03
and PAYNS04, so that the host names would be, for example,
payns03.blundies.com.
The IBM 6400 printer is attached to the AS/400, with a device name of PAY6400.
The IBM Network Printer 17 is defined with a host name of paynp17.blundies.com,
and is defined to the AS/400 as PAYNP17. An example of adding an IBM Network
Printer 17 to an AS/400 was included in 7.2.5, Adding a New Printer to the
AS/400 on page 146.
The IBM 4029 printer has a parallel printer port. It is connected directly to Marvin's
IBM Network Station, PAYNS01.
Lets look now as some of the configuration tasks required to make this environment
work.
165
8.3.3 Defining the PAY6400 Printer

PAY6400 is already setup on the AS/400, and is working okay. There will be no
requirement to print from the IBM Network Stations to this printer, as this printer is
only used for printing pay slips and checks from the AS/400-based payroll
application.
We do not need to make any changes to this printer device description.
8.3.4 Define the PAYNP17 Printer

PAYNP17 is also already defined to the AS/400, but if we wanted to create the
device description for this printer from scratch, we could use the CRTDEVPRT
command.
In the example below, only the parameters that were required for this printer to
work successfully are shown. (This is in order to simplify the description of this
definition.) Where parameters are not shown we accepted the default value.
Create Device Desc (Printer) (CRTDEVPRT)

Device description . . . . .
Device class . . . . . . . .
Device type . . . . . . . .
Device model . . . . . . . .
LAN attachment . . . . . . .
Port number . . . . . . . .
Font:
Identifier . . . . . . . .
Point size . . . . . . . .
Form feed . . . . . . . . .
Activation timer . . . . . .
Inactivity timer . . . . . .
Host print transform . . . .
Image configuration . . . .
Remote location:
Name or address . . . . .
Object type . . . . . . .
System driver program . . .
Text 'description' . . . . .
.
.
.
.
.
.
.
.
.
.
.
.
DEVD
DEVCLS
TYPE
MODEL
LANATTACH
PORT
FONT
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. SYSDRVPGM
. TEXT
FORMFEED
ACTTMR
INACTTMR
TRANSFORM
MFRTYPMDL
IMGCFG
RMTLOCNAME
PAYNP17
\LAN
3812
1
\IP
251
11
\NONE
\AUTOCUT
17
\ATTACH
\YES
\IBM4317
\NONE
PAYNP17.BLUNDIES.COM
\IBMPJLDRV
'Payroll Network Printer'
Figure 169. The PAYNP17 Printer Parameters
8.3.5 Defining the PAY4029 Printer

Finally we need to define PAY4029 to the AS/400, similar to the method used in
5.4, Printing from an AS/400 Host on page 98.
Since the PAY4029 printer is a PCL, we can use an image configuration object to
perform a transform to PCL for any PostScript output that comes onto this queue.
As the IBM 4029 is a 300 DPI PCL printer, we use the *IMGA01 image
configuration object.
See 8.3.11, Using Host Print Transform on page 177 for additional details on
Host Print Transform.
166
The printer is connected to the parallel port of PAYNC01, so we need to use a

remote printer queue value of PARALLEL1.
The commands to CRTOUTQ and CRTDEVPRT are used to create the output
queue and a dummy device description. In the examples below, only the
parameters that were required for this printer to work successfully are shown.
Where parameters are not shown, we accepted the default value.
Notice that we have set, in this case, the Destination type parameter to *OS400.
Even though the real destination is an IBM Network Station, setting this parameter
to *OS400 enables the use of streaming, which is supported by the IBM Network
Station.
Create Output Queue (CRTOUTQ)

Output queue . . . . . . . .
Library . . . . . . . . .
Remote system . . . . . . .
Remote printer queue . . . .
Connection type . . . . . .
Destination type . . . . . .
Host print transform . . . .
Image configuration . . . .
Text 'description' . . . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
OUTQ
RMTSYS
RMTPRTQ
CNNTYPE
DESTTYPE
TRANSFORM
MFRTYPMDL
IMGCFG
TEXT
PAY429
QUSRSYS
PAYNS1.BLUNDIES.COM
PARALLEL1
\IP
\OS4
\YES
\IBM429HP
\IMGA1
'Marvins IBM 429'
Create Device Desc (Printer) (CRTDEVPRT)

Device description
Device class . . .
Device type . . .
Device model . . .
Online at IPL . .
Font:
Identifier . . .
Point size . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
DEVD
DEVCLS
TYPE
MODEL
ONLINE
FONT
. . . . . . .
. . . . . . .
PAY429
\VRT
3812
1
\YES
11
\NONE
Figure 170. The PAY4029 Printer Parameters
The AS/400 can now send spool files to all three printers when the following
queues are used:
PAY6400 to use the IBM 6400 printer
PAYNP17 to use the IBM Network Printer 17
PAY4029 to use the IBM 4029 printer
8.3.6 Creating a Payroll Group User Profile

We need to make a group user profile on the AS/400 and make MARVIN, RAVI,
LINNA and MICHAEL members of the group. The group user profile is called
PAYGRP.
167
We may need to make changes to the user profiles to allow them to use the IBM
Network Stations, but we can also create a group profile called PAYGRP, and
make the users members of this group. We can use this to make changes to the
Group defaults, instead of changing each individuals user defaults.
We then use IBM Network Station Manager to add the Marvin, Ravi, Linna and
Michael users to the group PAYGRP.
8.3.7 Creating a Group Profile on the AS/400

Use the Create User Profile (CRTUSRPRF) command to create a group profile on
the AS/400.
8.3.8 Adding Users to the Group

We need to add the users into the group on the AS/400, by using the
CHGUSRPRF command. We use this command to tell the user profiles that they
are in the group called PAYGRP:
CHGUSRPRF username GRPPRF(PAYGRP)
Once we have done this, we can check that the users have been added to the
group correctly by using NSM, and from the list of Setup Tasks, selecting Select
User's Group.
Figure 171. Select User's Group Panel
The Select User's Group panel appears, and we are prompted to choose the user
to add to the group. We can either enter the name directly, or click on Browse...
and select a name from the list. Once we have chosen the user, we need to click
on the Next button. In the example we are selecting Ravi's user profile.
We then see the Select Group for RAVI screen, where we can select PAYGRP, so
that the user profile RAVI now picks up the group defaults for PAYGRP:
168
Figure 172. Select Group for RAVI
Once we select PAYGRP, we click on the Finish button, and we are returned to
the Select User's Group screen where we can repeat the process for the other user
profiles, LINNA, MICHAEL and MARVIN.
8.3.9 Changing the Group Defaults

We now add the IBM Network Printer, PAYNP17 to the Group defaults printer list
for PAYGRP.
Instead of setting the IBM Network Stations to print directly to the IBM Network
Printer 17, we send the spool files to the PAYNP17 queue on the AS/400.
By using the AS/400 to spool the print, we gain the following advantages:
The AS/400 probably receives the data faster than the printer. This means that
the print process completes faster on the IBM Network Station, and that
memory is released faster.
The AS/400 queues the print request.
Imagine a situation where PAYNS01 and PAYNS02 both attempt to print
directly to PAYNP17 within a few seconds of each other. This is illustrated in
Figure 173 on page 170.
169
Figure 173. Printing from IBM Network Stations Directly to PAYNP17
PAYNS01 starts printing first. When PAYNS02 starts to print, the printer
cannot accept another connection, so the PAYNS02 returns an error to the
user that the printer is not available.
Note: This might not be true of all network printers as it is dependent on the
amount of buffer space and disk space that the network printer has in order to
accept print requests.
Now imagine that PAYNS01 and PAYNS02 both print to a queue on the
AS/400, PAYROLL. The queue that they send print to is set up to print to the
IBM Network Printer, PAYNP17. This is illustrated in Figure 174 on page 171.
170
Figure 174. Using the AS/400, PAYROLL, to Queue Print for PAYNP17
PAYNS01 starts printing first, and then PAYNS02 starts printing. The AS/400
has multiple LPD jobs running, so it is can handle both of the requests at the
same time. Both IBM Network Stations print jobs complete successfully, and
they then disconnect. The print is queued on the AS/400 which then sends the
print jobs to IBM Network Printer in turn. By doing this, the user on PAYNS02
does not get error messages, and does not have to wait for the printer to
become available before sending the print again; the AS/400 queue does this
on behalf of the user.
From the IBM Network Station Manager select Hardware Printers. On the
Printer Defaults screen, select the Group defaults for PAYGRP.
171
Figure 175. Selecting PAYGRP for Group Defaults
We click on Next to see the Printer Settings for PAYGRP screen where we add a
new printer definition to be used in the printer list. In this case we add the IBM
Network Printer. We use a remote location of payroll.blundies.com, which is the
AS/400, and a printer queue of PAYNP17 on the AS/400.
Figure 176. Adding PAYNP17 to the PAYGRP for Group Defaults
Once all the details are entered, we click on Finish.

The next time one of the group members signs on onto the IBM Network Station,
he or she sees this printer queue in the Printer Selector:
172
Figure 177. Marvin's Printer Selector
8.3.10 Changing the User Defaults

We now need to make the PAY4029 printer available to user MARVIN.
By default, he sees a queue of PARALLEL1@localhost, which sends data directly
to the local printer. But, since most IBM Network Station applications generate a
PostScript data stream, and Marvin's printer is a PCL printer, we have a
compatibility problem to solve. If the PostScript data stream was sent to this
default PARALLEL1 printer, we would see incorrect output, as the printer does not
understand the PostScript commands in the data stream.
So that Marvin can continue to use his PCL printer, we need to transform the
PostScript data stream into a PCL data stream. At R420 and later at OS/400, there
is a feature of the operating system that can perform such a transform.
We need to change Marvin's User defaults so that he has a printer queue that
sends the print request to the AS/400, PAYROLL, where it can be transformed from
PostScript to PCL, and then sent back to the IBM Network Station, PAYNS01,
where it can be passed to the printer, PAY4029. This process is illustrated in the
figure below:
173
Figure 178. Using the AS/400, PAYROLL, to Transform PostScript to PCL
We have already configured the AS/400 queue to perform this transform for us
(8.3.5, Defining the PAY4029 Printer on page 166), so we now need to add this
printer queue to Marvin's User defaults so that it appears in his printer selector list.
From the IBM Network Station Manager we select Hardware Printers. On the
Printer Defaults screen, we select the User Defaults for MARVIN:
174
Figure 179. The Printer Defaults Screen, Selecting Marvin's User Defaults
We click on Next. We are now presented with the Printer Settings for MARVIN
screen. Here we must add the details of the printer.
Remote printer server
This is the host name of the LPD server, in this case, the AS/400. We
use payroll.blundies.com.
Queue name
The printer queue on the LPD server that output should be placed on.
In this case, it is PAY4029, the queue which was defined in 8.3.5,
Defining the PAY4029 Printer on page 166.
Stream type
This will only be used by the 5250 and 3270 emulators (see 6.1,
Printing from the 3270/5250 Emulator on page 122). The queue on the
AS/400 will convert output from PostScript to PCL, so we can leave this
as the default of PostScript.
Description
The Description field is optional, but we have specified it as Marvin's
4029.
175
Figure 180. Printer Settings for MARVIN
We click on Finish.
Next time Marvin signs on, in addition to the System default printers and the group
printer, PAYNP17, he will also see his personal printer, PAY4029:
Figure 181. Marvin's Printer Selector
It is important to notice that the list contains the Group and User defaults. The list
is created by adding the System, Workstation, Group and User defaults, but since
there were no Workstation defaults defined, we only get the User, Group and
System defaults.
PARALLEL1 is shown because it is in the System defaults.
SERIAL1 is shown because it is in the System defaults.
PAYNP17 is shown because it is in the Group defaults for PAYGRP, and
Marvin is a member of this group.
PAY4029 is shown because it is in the User defaults for Marvin.
176
8.3.11 Using Host Print Transform

Now we describe a few additional details on the transform function we used in the
example above.
There are four types of datastream which the AS/400 can handle:
*SCS
*IPDS
*AFPDS
*USERASCII
One can see which type a spool file is by looking at the spool file attributes. Use
the command WRKSPLF, then opt8, and press Page Down once.
When *USERASCII is used, in general the AS/400 does not understand the data
stream (with the exception of Image Print Transform) and it is just passed through.
It cannot be displayed on the screen in the same way as the other data streams
can. Even the number of pages shown in WRKSPLF is an approximation only,
calculated by the AS/400 based on the size of the spool file.
There are two types of transforms that can take place:
1. Host Print Transform
Host Print Transform is used to convert AS/400 data streams into ASCII data
streams.
It takes SCS, IPDS and AFPDS data streams and transforms them into ASCII
data streams such as PCL (HP), PPDS (IBM) and ESC/2 (Epson), but not
PostScript. This only works for EBCDIC to ASCII, and cannot be used in
reverse.
The AS/400 looks at the Host Print Transform parameter in the printer queue
definition to see if it should transform the data. If the Host Print Transform
parameter is set to *YES, then it examines the Manufacturer Type and Model
field to see the transform that should be used, for example *HP5, *IBM4019,
*EPFXnnnn, etc.
2. Image Print Transform
Image Print Transform, which is new with R420 of OS/400, allows converting
data from GIF, TIFF, BMP and PostScript only. These data streams can be
converted into PostScript, PCL or AFPDS only.
In summary then,
Host Print Transform:
SCS
IPDS
AFPDS
----> HPT ----> ASCII escape-code-based datastreams

such as PCL, PPDS and ESC/2
Image Print Transform:

PS
TIFF
GIF
BMP
----> IPT ---->
PCL
PS
AFPDS
177
Please reference AS/400 Printing V, SG24-2160 for additional details on the host
print transform and image print transform capabilities of the AS/400.
178
Chapter 9. Problem Determination Tools, Tips and

Techniques
The objective of this section is to highlight some of the tools and techniques that
might be useful in doing problem determination. This is by no means an
exhaustive list, but we tried to document here some of the situations we ran into
and some of the ways that we used to get the information required to identify a
problem and solve it.
Another source that can be used is the Problem Determination chapter in the
redbook entitled IBM Network Station Guide for Windows NT, SG24-2127-01, which
is more complete in terms of problem determination as it relates to the IBM
Network Station in general, as opposed to just the printing issues.
9.1 Mini Console

In Release 3, a mini console facility has been added with the objective of providing
the user a more visual feedback when an error occurs.
When the error occurs, the error messages are logged normally to the regular
console, but a mini console is also displayed drawing the attention of the user to
the abnormal condition.
Below is an example of a mini console showing up on the user display in the case
where an unknown host name has been specified as the print destination.
Figure 182. Sample Mini Console
9.2 Printer Hex Mode

Some printers have a Hex Mode that can be enabled. If the printer has a Hex
Mode and it is enabled, the printer does not print normally.
Any data sent to the printer is printed as hexadecimal numbers. This is sometimes
useful when comparing prints from various systems to identify the difference. It is
179
also useful when we suspect that the data received by the printer is not the data
that was originally sent.
9.3 PING
PING is a command that sends a request to an IP address, asking for a response if
the command is received. This is a useful tool to verify that two devices are able to
communicate with each other on the network.
For example, to check that the device at IP address 9.24.104.189 can receive from
a PC, we could type the following command at the command prompt:
PING 9.24.14.189
The IBM Network Station responds to PINGs as soon as its network interface is up
and running. To ping from the IBM Network Station, click Test Network... from the
Utilities menu on the console.
9.4 Problems When Sending from an IBM Network Station to an

AS/400
If problems occur when sending spool files from the IBM Network Station to the
AS/400, it is useful to check for:
Messages on the IBM Network Station (see 9.7.1, Accessing the IBM Network
Station Message Log Remotely on page 181 and 9.7, Message Log on the
IBM Network Station on page 181).
Messages in the AS/400 Operator message queue, QSYSOPR.
To see the contents of the QSYSOPR message queue, we can type DSPMSG
QSYSOPR. Further help for any message can be obtained by putting the cursor
over the message and pressing F1.
A job log for the LPD job.
To see the job log for the LPD job, we can use the DSPJOBLOG command
and specify the details for the LPD job for example, DSPJOBLOG
JOB(xxxxxx/QTCP/QTLPxxxxx).
If the job has ended, we may find a job log in the QEZJOBLOG output queue.
This can be displayed using the command WRKOUTQ QEZJOBLOG. The most
recently written logs will be at the bottom of the list, which can be reached by
pressing F18 (or SHIFT and F6)
9.5 Problems When Sending from an AS/400 to an IBM Network

Station
If problems occur when sending files from the AS/400 to the IBM Network Station, it
is useful to check for:
Messages on the IBM Network Station (see 9.7.1, Accessing the IBM Network
Station Message Log Remotely on page 181 and 9.7, Message Log on the
IBM Network Station on page 181).
Messages in the AS/400 Operator message queue, QSYSOPR.
180
To see the contents of the QSYSOPR message queue, we can type DSPMSG
QSYSOPR. Further help for any message can be obtained by putting the cursor
over the message and pressing F1.
A job log for the Printer Writer.
To see the job log for the writer, we can use the DSPJOBLOG command and
specify the details for the writer job, for example, DSPJOBLOG
JOB(xxxxxx/QSPLJOB/PRTxx).
If the job has ended, we may find a job log in the QEZJOBLOG output queue.
This can be displayed using the command WRKOUTQ QEZJOBLOG. The
most recently written logs will be at the bottom of the list, which can be reached
by pressing F18 (or SHIFT and F6).
9.6 Using Windows NT Event Viewer

When the destination host of an LPR request is a Windows NT system, any error
messages issued by the LPD server is logged to the System Event viewer.
If there are too many messages, you can use the View pull-down to specify display
filters. Under the Source drop-down list, you find the LPDSVC category and the
Print category, which pertain to messages issued by the LPD service or the Print
subsystem.
9.7 Message Log on the IBM Network Station

The message log on the IBM Network Station is accessed through the console. To
display the console, press the left Shift key, the left Alt key and the Home key
together.
Note that this key combination to display the console is configurable and may
therefore have been changed on your system. Another popular key sequence for
the console is the Pause key.
Once the console is displayed, the messages can be viewed by a clicking on the
Messages box which appears just below the Console pull-down.
Alternatively, if the Terminals pull-down menu is available on the console, selecting
New Terminal and then the Diag service brings up a window which lists all the
console messages.
9.7.1 Accessing the IBM Network Station Message Log Remotely

It is possible to access the messages on the network station remotely, using a
TELNET session to port 5998 on the IBM Network Station from a remote system.
For example, in Windows NT at the command prompt, you can type:
TELNET 9.24.14.189 5998
In OS/400 at the command line, we can type:
TELNET RMTSYS(\INTNETADR) INTNETADR('9.24.14.189') PORT(5998)
Chapter 9. Problem Determination Tools, Tips and Techniques
181
9.8 Checking the Version of an IBM Network Station

It is possible to find the version of the IBM Network Station from the console, using
StatisticsShow Version.... This brings up the Show Version screen, which
displays the model type, the software (the version of code which was downloaded
from the server) and the boot monitor (the version of firmware). Other useful
information such as the MAC address, the IP address, the IP hostname are also
displayed:
Figure 183. Show Version
9.9 Verifying the Currently Loaded IBM Network Station Configuration

It is strongly recommended that all configuration changes be made using the IBM
Network Station Manager. However, there are cases where you might need to
verify if a particular parameter has indeed been set correctly, or you might need to
temporarily change the value of a parameter in order to test a particular situation or
do general problem determination.
You can have access to all the IBM Network Station configuration parameters using
the commands available on the Setup menu on the IBM Network Station console,
provided that you have been given the proper level of authority to do so.
To bring up the console on your IBM Network Station, the default key sequence is
Alt+Shift+Home. However, this is a configurable parameter and it might have been
changed to the Pause key for example, which is also popular, or some other key
sequence. The figure below illustrates the console and the pull-down menu for
Setup.
Figure 184. The Setup Menu on the Console
182
There are three menu entries that give access to the configuration parameters. The
ones we deal most often with are under the Change Setup Parameters option. We
have listed in the figure below all the sections that we have access to from this
menu.
Figure 185. The Sections Available through Setup
There are four of these sections that contain parameters directly related to printing.
They are:
Print
This contains the parameters related to the LPD and LPRD daemon, such as
the print buffers size specifications, the printer selection table and the access
control list for the LPD daemon.
Access Control
The Access Control parameters for the SERIALD daemon are located here.
Parallel
This is for the configuration parameters related specifically to the parallel port.
Serial
This is for the configuration parameters related specifically to the serial port.
9.9.1 The Print Section Configuration

This section of the Setup Parameters concerns the configuration parameters for the
LPD and LPRD daemons. The Print section is displayed in the figure below:
183
Figure 186. The Print Configuration Section
At the top of the panel, notice the Lpd Cache Size and Lprd Cache Size which are
currently set to the default of 10%. These are the parameters that determine the
amount of free RAM dedicated to the print buffers for LPRD and LPD. The
minimum that can be specified is 0% (5 KB) and the maximum is 95%. If the user
enters a value outside of that range, it is automatically adjusted to be within the
allowable range.
The next entry is the Lpd Stream Large Jobs parameter, which is also referred to
as the Bypass Print Buffer parameter. When this is set to Yes, print jobs that
exceed the capacity of the print buffer automatically cause the LPD to begin
streaming out the data to the printer. If this parameter is set to NO and the print
buffer is exceeded while the LPD reads data in, the print job fails.
Next is the Enable Access Control and Print Access Control List configuration
parameters. These determine whether remote hosts that issue LPR requests to the
LPD daemon on the IBM Network Station are allowed to use the LPD service or
not. In the example here, the Enable Access Control is not set so that any host is
allowed to use the LPD daemon. If set to Yes, then the table should contain
entries listing the authorized hosts.
The figure below illustrates the configuration parameters as they appear in a
configuration file, for the items discussed above.
184
set print-lprd-cache-size = 1
set print-lpd-cache-size = 1
set print-lpd-stream-large-jobs = true or false
set print-access-control-enabled = true or false
set print-access-control-list = {
{ hostname1 }
{ hostname2 }
}
Figure 187. The LPRD/LPD Buffer Size Parameters
The next and perhaps most important and visible parameter is the Lpr Servers
table, or the printer table as it is sometimes referred to. (The actual parameter
name is print-lpr-servers.) This is the table containing the list of printers, local and
remote, to which local applications have access to. When an application requests
to print and the user clicks on Browse in the Print Dialog to see which printers are
available, the printers that get listed in the Printer Selector panel are supplied from
this table.
In the figure above (Figure 186 on page 184), we can only see the first two
entries, which are labeled localhost PARALLEL1
ps Local Parallel Printer
and localhost SERIAL1
ps Local Serial Printer, but the figure below
illustrates what the complete table looks like in the actual configuration parameter
that builds the printer table.
print-lpr-servers = {
{ "localhost" "PARALLEL1" "ps" "Local Parallel Printer" nil nil nil nil false true }
{ "localhost" "SERIAL1" "ps" "Local Serial Printer" nil nil nil nil false false }
{ "burkhart.austin.ibm.com" "locps" "ps" "ITSO Queue" nil nil nil nil true false }
{ "linna.austin.ibm.com" "javaps" "ps" "Remote AIX4.2.1 server" nil nil nil nil true false }
{ "9.53.113.131" "javaps" "ps" "Remote AIX4.2.1" nil nil nil nil true false }
}
Figure 188. The Printer Table Configuration Parameters
The printer table contains a list of printers available, along with the characteristics
of each of these printers.
This table is configured by the administrator using the IBM Network Station
Manager, and he or she has the option of configuring printers that are available to
all users, or some that are available only to certain groups of users, or only to
specific users.
After the administrator configures the different printers using the IBM Network
Station Manager, this creates the actual print-lpr-servers table which is added to
one or more of the configuration files that get read by the IBM Network Station at
boot time.
The printer table contains the following information about the printers:
Location of the printer.
This can be a host name or IP address. If the printer is local to the IBM
Network Station, this will be localhost.
185
Printer queue to use on the remote system.

If this is a local printer it will be either PARALLEL1 or SERIAL1.
The data stream that the printer handles.
This can be:
ps for PostScript
pcl for PCL
asc for ASCII
A description of the printer.
For example, IBM 429 printer on 5th Floor near Pillar Q.
DBCS parameters
Four parameters to allow Double Byte Character Sets to be printed on
ASCII printers. (These parameters are explained in more detail in
Chapter 11, DBCS Considerations on page 225.)
Transformation Module
DBCS Type
Printer Resolution
DBCS Font Encoding Method
Banner Page
Whether a banner page is required when printing to this printer. This
can be true or false and can be specified only for remote printers.
Banners are not supported for local printers.
Default printer
Whether the printer is the default printer. This can be true or false.
Below is a sample panel from the IBM Network Station Manager where the
administrator can configure remote printers.
Figure 189. The Printer Configuration Panel in IBM Network Station Manager
More details on using the IBM Network Station Manager for configuring this table
are given in Chapter 4, Configuration Using the IBM Network Station Manager on
page 47.
186
9.9.1.1 Removing Local Printers from the Selector List

If most of the IBM Network Stations do not have printer attached, the administrator
may elect to avoid displaying the PARALLEL1 and SERIAL1 entries in the list of
selectable printers for all stations. However, care must be exercised in the way
that this is done if some of the IBM Network Stations do have a printer attached.
To illustrate this, we use our Blundies scenario of the previous chapter where only
the user called Marvin has a printer attached to his IBM Network Station. Since
none of the other users has a printer, you might decide to configure the system
defaults in such a way as to eliminate the PARALLEL1 and SERIAL1 queues from
the printer selector list, but you then must make sure to add them back for the user
Marvin's workstation.
Indeed, even though user Marvin does not use the PARALLEL1 selection directly
when he chooses a printer (he uses the PAY4029 entry in order to send the output
to the AS/400 to be transformed into PCL data), the printer queue definition on the
AS/400 points back to the PARALLEL1 queue on Marvin's IBM Network Station.
When the LPD daemon receives the print request, it uses uses the print APIs (and
therefore the printer selector table) to confirm that the queue stated in the received
print job request exists. An entry for PARALLEL1 must therefore exists in order for
the job to be processed by the LPD daemon.
If you need to remove the local printers entries from the the user's Printer Selector
by making a change to the System defaults, here is the way to proceed.
From the IBM Network Station Manager Setup Tasks, select Hardware Printers.
From the Printer Defaults screen, select System defaults, and select Next.
On the Printer Settings - System Defaults screen, scroll down to the Printer List.
In the Printer List, change the Local parallel printer and Local serial printer fields to
None attached.
Figure 190. Changing the Local serial printer
Then click on Finish. The next time that any user looks at the Printer Selector,
they no longer see the SERIAL1 or PARALLEL1 queues.
187
Figure 191. Printer Selector with PARALLEL1 and SERIAL1 Removed
9.9.2 The Access Control Section Configuration

Access control is the mechanism by which we control which remote hosts have the
authority to send print requests to the IBM Network Station.
Printer access control in Release 3 consists of two mechanisms:
One for controlling access to SERIALD from remote hosts (direct access to
serial and parallel ports via SERIALD)
One for controlling access to LPD from remote hosts
In this section, we show the details of the different access control lists that exist in
the configuration parameters of the IBM Network Station. However, remember that
when you use the IBM Network Station Manager to configure access control, there
is only one access control list defined which is automatically applied in the
configuration files to both the SERIALD access control list and the LPD access
control list.
Please refer to Chapter 4, Configuration Using the IBM Network Station Manager
on page 47 for details on how to use the IBM Network Station Manager to
configure printer access control.
9.9.2.1 The SERIALD Access Control

To access the SERIALD access control list configuration on the IBM Network
Station, use the Setup Parameters command on the Setup pull-down menu on the
console and select the Access Control section.
Under that section, there are multiple access control lists; scroll down to the one
entitled Serial and Parallel Daemon, as illustrated in the figure below:
188
Figure 192. Access Control List for Serial and Parallel Ports
Note
This specific access control list controls the access to the SERIALD daemon, as
opposed to the access control list described above (Figure 186 on page 184) in
the Print section, which controls access to the LPD daemon.
Notice that in the example above, the Enable Serial and Parallel Access Control
button is not set, and therefore any host has access to the SERIALD daemon. If
this button was set to Enable, entries would appear or could be made in the Access
Control list.
The configuration parameters that control this are as follows, where hostname
represents the name or IP address of the host which is granted authority to access.
The parameter tcpip remains as tcpip and identifies the connection type over which
the host accesses the IBM Network Station.
set serial-access-control-enabled = true or false

set serial-access-control-list = {
{ localhost tcpip }
}
Figure 193. The Serial Daemon Access Control Configuration Parameters
189
9.9.2.2 Controlling Access to the LPD from Remote Hosts

The previous access control list for SERIALD concerned direct access to the
SERIALD daemon. Access to the LPD daemon is controlled by another access
control list.
This particular access control list configuration panel in the IBM Network Station is
not located in the Access Control section like all the other access control lists but
rather in the Print section, along with the other LPD-related configuration
parameters, as illustrated below:
Figure 194. Access Control List for the LPD Daemon
There are also two configuration parameters for this access control list:
print-access-control-enabled = true or false

print-access-control-list = {
{ localhost }
{ hostname1 }
{ hostname2 }
}
Figure 195. LPD Access Control List Parameters
localhost, hostname1, hostname2 are the IP addresses or IP host names of the

hosts authorized to access the LPD daemon.
190
When print-access-control-enabled = true, LPD validates the remote host during

connection establishment to see if the remote host is listed in the
print-access-control-list table. If the print-access-control-enabled is set to false,
then the next parameter is not required as this gives access to any host.
page 47 for information on how to configure access control using the IBM Network
Station Manager.
9.9.3 Parallel and Serial Port Configuration Parameters

The parallel and serial ports also have specific configuration parameters that can
be set, dependent on how these ports are used.
For example, as discussed in 5.3.1.5, IBM Network Station Configuration on
page 91, when printing from a WinCenter server, the settings of the parallel and/or
serial ports on the IBM Network Station must be set to reflect what the WinCenter
server expects.
9.9.3.1 Parallel Daemon Configuration

Under the Parallel section, look for the Parallel Daemon table, illustrated in the
figure below:
Figure 196. Parallel Port
In the figure above, the Use Parallel Protocol value can be toggled from false to
true. When printing from WinCenter, the value under the heading Use Parallel
Protocol should read False. This puts the SERIALD daemon in passthru mode, so
that any data received on this port is simply passed through the daemon, without
any modification, and handed over to the parallel port. Since the printer driver used
on the WinCenter server is the one for the physical printer attached to this port, the
received print data stream is ready to be handed over directly to the print device.
If you leave the value of Use Parallel Protocol as true, this puts the daemon in
command mode, which triggers SERIALD to examine the incoming data looking for
commands such as a query of the port status, or setting port characteristics such
as baud rate, or parity, etc. This mode is used when the application needs to have
a finer control over the port as well as have the ability to monitor the status of the
data transmission.
These commands are imbedded in the data stream by the application and consist
of a 0xF0 character followed by some data.
191
If the sockets 6461 (serial) and 6464 (parallel) are used to connect to SERIALD,
command mode is always used. If sockets 87 (serial) and 5964 (parallel) are used,
SERIALD uses the command mode only if the Use Parallel Protocol option is set to
true, otherwise it uses passthrough mode.
If command mode is used but there are no commands in the data stream, then this
is the equivalent of passthrough mode since the SERIALD module will simply pass
the data through when there are no commands to act upon.
The port number under the heading of TCP Port should also be set to 5964, since
this is the port number that WinCenter will attempt to connect to in order to send
the print data stream.
These values are set by configuration statements in the configuration files on the
server from which the IBM Network Station reads its configuration data, and the
parameters for the parallel port are as follows:
set parallel-daemons-table = {
{ 1 false 5964 }
}
Figure 197. Parallel Port Configuration Parameters
9.9.3.2 Serial Port Configuration

If the serial port is used instead of the parallel port, then select the section called
Serial in the Change Setup parameters menu, which brings up the panel shown
below.
Figure 198. Serial Port
If you are using WinCenter, verify the entries in the Serial Daemons table to ensure
that Use Serial Protocol shows as false (it is set to true in the example above) and
that the TCP port is 87.
In the Serial Interfaces Table, the Port Use at Boot and the Current Port Use
options should both be set to printer. As well, settings for Baud rate, Data Bits,
192
Stop Bits, Parity and Handshake should match the settings recommended for the
attached printer.
The configuration statements used in a configuration file to set the above values
are as follows:
set
{
}
set
{ 1
}
serial-daemons-table = {
1 false 87 }
serial-interfaces-table = {
printer printer 96 8 1 none dtr/dsr none }
Figure 199. Serial Port Configuration Parameters
Once you have verified that the parallel or serial port configuration is correct, there
are a few statistics that can be monitored to see if certain functions have been
activated.
One place to look is under the Statistics pull-down on the IBM Network Station
console, where choosing the Parallel Daemons entry brings up the panel below
where one can see the number of connections that have been accepted by the
parallel daemon. Each time a connection is made from WinCenter to the parallel
daemon to send printer output, this counter is incremented by one.
Figure 200. Parallel Daemon
Another useful tool is the Connection Table, also located under User Preferences,
where one can see the local IP address and local port, remote IP address and port
as well as status for each TCP connection.
In the example below, notice the first line which shows an established connection
between 9.24.104.178 (this is the WinCenter Server) port 1859 and 9.24.104.189
(this is the IBM Network Station) port 5964.
193
Figure 201. Connection Table
9.10 LPR/LPD Control Commands and Data Types

When an LPR requester sends a print request to an LPD server, it sends a control
file along with the data file. This control file contains various options that tells the
LPD how to process the print job.
For example, one of these options tells the LPD what type of data is present in the
data file. This allows the receiving LPD to determine whether it should examine the
data and do some processing on it or whether it should just pass the data as is to
the printer.
Other options are, for example, the name of the job, the class of the job, name of
the user sending the job, etc.
9.10.1 Control File Names

There is a naming convention for control files and data files exchanged between an
LPR and an LPD. The names have the following format:
Control files
Data files
cfANNNhost
dfCNNNhost
cfA
Prefix for all control files.
df
Prefix used for data files.
A letter uniquely identifying the data file within the print job. The first
data file uses the letter A, the second the letter B, and so on.
NNN
A print job number unique within the queue on the originating host.
host
The originating host name. For the IBM Network Station, if the
originating host does not have a host name, the LPRD generates a
name in the form IPnnn.nnn.nnn.nnn where nnn.nnn.nnn.nnn is the IP
address of the IBM Network Station sending the data.
9.10.2 Control File Options Used by the IBM Network Station

Here is a description of some of the control file options and how they are used by
the LPRD or LPD daemons on the IBM Network Station.
9.10.2.1 Control File Options Used by the LPRD Daemon

The folowing are the control options used by the LPRD daemon:
C
Class for banner page.

Built using the class sent by the printOpen API, if specified. Otherwise,
built using the IBM Network Station host name or IP address.
194
Host name of the origin host.

This is the IBM Network Station host name or IP address if no host
name is available.
Indent printing.
Used with the l and f print request options. Not used by the IBM
Network Station.
Job name for the banner page.

This is the job description sent by the printOpen API, if specified.
Otherwise, it is not used by the IBM Network Station.
Print banner page.

Built by the print banner option sent by the printOpen API, if specified.
Otherwise, built based on the configuration parameter option to print
banner pages.
Mail when printed.

Send mail to the user who submitted the print job when it completes.
Not used by the IBM Network Station.
Name of the source file.

Built using a blank name since there is no source file in the case of the
User identification.
Name of the user requesting the print job. Used for authentication when
using the remove job function and when reporting queue status via the
Send Queue State command. Built using the name of the user currently
signed on to the IBM Network Station.
Symbolic link data.

Indicates that the data file is a symbolic link to the source file (instead of
copying the source file to the spool queue directory). Used to conserve
space in the spool queue directory. Not used by the IBM Network
Station.
Title for pr.

Used by the pr filter to put a title line in the output. Not used by the IBM
Network Station.
Unlink data file.

Specifies that the specified data file is no longer needed and should be
deleted. Built for each data file that is sent.
Width of output.
Specifies the width (in columns) for the f, l, p and r print requests/filters.
1, 2, 3, 4 Troff R, I, B, and S fonts.

Specifies the fonts to be used for the t, n and d print requests/filters.
195
Extended print option.

Specifies a platform-dependent option that extends the LPD protocol.
Formatted print request.

Tells the LPD to print the data file with the name specified on this
option. The data file name must match the name specified on a
Receive Data File or Receive Data File with Unspecified Length
command.
Literal print request.

Tells the LPD to print the data file with the name specified on this
option. The data file name must match the name specified on a
Receive Data File or Receive Data File with Unspecified Length
command.
This is the default used by the IBM Network Station. One print request is
built for every copy of the file that was requested.
c, d, g, k, n, p, r, t, v and x Other print request commands.

Tells the LPD to print the data file with the name specified on this option
using a filter program that corresponds to the print request type.
9.10.2.2 Control File Options Used by the LPD Daemon

The following control file options are used by the LPD daemon:
C
Class for banner page.

Not used; banner pages are not implemented in Release 3 of the IBM
Network Station.
Host name of the origin host.

This is ignored since no authority checking is done by the LPD on the
Indent printing.
Ignored since filters are not supported by the IBM Network Station.
Job name for the banner page.

Network Station.
Print banner page.

Network Station.
Mail when printed.

Ignored since mail requires a filter which is not supported.
Name of the source file.

Ignored.
196
User identification.
Ignored.
Symbolic link data.

Ignored.
Title for pr.

Ignored.
Unlink data file.

Deallocates storage that was associated with the specified file.
Width of output.
Ignored.
1, 2, 3, 4 Troff R, I, B, and S fonts.

Ignored.
X
Extended print option.

Ignored.
Formatted print request.

The specified data file is printed (no filtering).
Literal print request.

The specified data file is printed (no filtering).
c, d, g, k, n, p, r, t, v and x Other print request commands.

Tells the LPD to print the data file with the name specified on this option
using a filter program that corresponds to the print request type.
The specified data file is printed as if the f print request had been
specified (no filtering). A message is issued to the IBM Network Station
console stating that the print job data format may be incorrect.
9.10.3 A Sample Control File

Here is an example of what a control file looks like. We use an example of one
sent by a Windows NT system to another Windows NT system.
This very simple example sends the autoexec.bat file using the LPR command. We
use the command:
LPR -S 9.24.14.24 -P IBM429 -C CLASS1 - J JOBTEST c:\autoexec.bat
There is no mechanism by which we can actually take a look at this control file on
Windows NT, so we used the Network Monitor Tool to capture the frames sent from
the LPR to LPD.
Below is an example of what the control information that was sent as a result of the
above command.
197
4
5
6
7
8
9
A
41
4C
41
66
41
61
64
41
64
41
31
75
6D
53
6D
31
36
74
69
53
69
36
34
6F
6E
31
6E
34
42
65
69
A
69
42
45
78
48
73
4A
73
45
43
65
42
74
4A
74
43
48
63
45
72
4F
72
48
41
2E
43
61
42
61
41
52
62
48
74
54
74
52
44
61
41
6F
45
6F
44
A
74
52
72
53
72
A
4E
A
44
A
54
A
55
63
A
43
A
66
64
3A
5
43
4C
64
66
5C
HBECHARD.P
Administrator.CC
LASS1.JJOBTEST.L
Administrator.fd
fA164BECHARD.Udf
A164BECHARD.Nc:\
autoexec.bat..
Figure 202. Sample Control File - Text File
If we lay out the information appearing in this frame, we get the following:
H
P
C
J
L
f
U
N
BECHARD
Administrator
CLASS1
JOBTEST
Administrator
dfA164BECHARD
dfA164BECHARD
c:\autoexec.bat
Target Host Name (Host at 9.24.14.24)

Source User Name
Job Class
Job Name
Print Banner Page
Process as TEXT - Data File Name = dfA164
Unlink the data file named dfa164
Name of Source File
If the file to send is a binary file, such as a PostScript file, the command to use
should include the option -o l to indicate that this is not a TEXT file. For example:
LPR -S 9.24.14.24 -P IBM429 -o l -C CLASSX - J MINE c:\test.psbin
A sample of the resulting control file sent would be:
4
5
6
7
8
9
A
41
4C
69
3
39
74
64
41
6E
39
42
2E
6D
53
69
42
45
7
69
53
73
45
43
73
6E
58
74
43
48
62
69
A
72
48
41
69
48
73
4A
61
41
52
6E
42
74
4D
74
52
44
A
45
72
49
6F
44
A
43
61
4E
72
A
4E
48
74
45
A
55
63
41
6F
A
6C
64
3A
52
72
4C
64
66
5C
44
A
41
66
41
74
A
43
64
41
38
65
5
43
6D
38
3
73
HBECHARD.P
Administrator.CC
LASSX.JMINE.LAdm
inistrator.ldfA8
9BECHARD.UdfA8
9BECHARD.Nc:\tes
t.psbin..
Figure 203. Sample Control File - Binary File
Notice that the f option has been changed to l (position 7B in the above record)
indicating this file should be passthrough without any modifications.
9.10.4 Using the LPQ Command

On some platforms, the LPQ command can be used to find out the status of LPD
jobs in the queue.
Here is an example of the output of the LPQ command when executed from a
Windows NT command line to a target AIX system.
198
D:\sg245212\artwork\work>lpq -S venus -P ral313a -l

Queue
Dev
Status
Job
Name
From
To
Submitted
Rnk Pri
Blks Cp
PP %
------- ----- ------- ----------- ------- ----- ral313 @ral3 DOWN
QUEUED 121
c:\autoexec.ba Administrator@ Administrator@
4/16/98 12:44:32
1 15
1
1
/var/spool/lpd/dfA891BECHARD
QUEUED 122
c:\autoexec.ba Administrator@ Administrator@
4/16/98 12:47:23
2 15
1
1
/var/spool/lpd/dfA288BECHARD
ral313 afccu READY
afccu2 pcl1 READY
Figure 204. LPQ Command Output - AIX LPD Server
It shows two jobs (the same print job) waiting in the queue.
If we execute the same command but this time to a target Windows NT server, the
output is as follows:
C:\>lpq -S 9.24.14.24 -P IBM429

Windows NT LPD Server
Printer IBM429 (Paused)
Owner
Status
Jobname
Job-Id
Size
Pages Priority
------------------------------------------------------------------------Administrat Waiting
c:\autoexec.bat
41
5
1
Administrat Waiting
c:\autoexec.bat
42
5
Figure 205. LPQ Command Output - Windows NT LPD Server
If we take a look at the actual printer queue called IBM4029 on the Windows NT
server where the target LPD resides, these entries appear as shown in the panel
below:
Figure 206. The IBM 4029 Printer Queue - Two LPR Jobs Paused
The same two files were sent to the remote printer where they are currently held
because the printer queue has been paused.
Notice, in the display output of the LPQ command, the Job-Id indicated here as
being 41 and 42. These numbers are the same that Windows NT used to store the
jobs in the spooler queue.
199
You can see these files, using your Windows NT Explorer, by looking at the
directory \WINNT\System32\Spool\Printers. This directory is displayed in the panel
below.
Figure 207. Two Print Jobs in the Windows NT Spooler Queue
Notice that for each of the print jobs in the queue, there are two files. The
00041.shd is a header file which identifies the characteristics of this job. The
00041.spl is the actual data to be printed. If one uses an hex editor to look at the
contents of an shd file, the following figure would appear.
Figure 208. A Sample SHD File
Notice the following data is present in this header file:

BECHARD is the host name of the LPD server.
ADMINISTRATOR is the user name on the LPD server.
ADMINISTRATOR is the name of the owner of the print job.
9.24.14.175 is the IP address of the source host.
c:\autoexec.bat is the name of the source file.
IBM429 is the name of the destination printer queue to which this file belongs.
IBM429 Laser Printer is the name of the device driver for that queue.
WINPRINTis the name of the Print Processor to be used.
TEXT is the data type of the print job.
200
9.10.5 Viewing the Control File

In Windows NT, the control file is not available to the user. For the examples
above, we captured the incoming frames to the LPD server using Windows NT's
Network Monitor.
In OS/2, the control file is easily accessible by putting the printer queue in HOLD
mode. The control file appears as a separate entry in the queue and can simply be
examined with any editor.
In AIX, the control and data file are stored in the directory /var/spool/lpd, and they
bear names starting with cfA or dfA. However, the control file is discarded
immediately after it is processed, so that it is not really available for viewing by the
user.
9.10.6 Control Commands As Used in Windows NT

In Windows NT, there are two ways that an LPR request can be sent to a remote
LPD server:
Using the LPR command from a command line
Defining an LPR port associated to a remote printer and sending print output to
that port
9.10.6.1 Using the LPR Command Line

The LPR command in Windows NT has the following format:
C:\>lpr /?
Sends a print job to a network printer
Usage:
lpr -S server -P printer [-C class] [-J job] [-o option] [-x] [-d] filename
Options:
-S server
-P printer
-C class
-J job
-o option
-x
-d
Name or ipaddress of the host providing lpd service

Name of the print queue
Job classification for use on the burst page
Job name to print on the burst page
Indicates type of the file (by default assumes a text file)
Use "-o l" for binary (e.g. postscript) files
Compatibility with SunOS 4.1.x and prior
Send data file first
By default, the command line version of the LPR sends f as the default control
command indicating that the data type of the file is TEXT.
However, the user can override this default, on a per job basis, by using the -o
option on the command line. For example, to send a PostScript file called
myfile.psbin to a remote printer called myqueue on a remote host called myprinter,
the user would use the command below causing the default f control flag to be
changed to the l control flag, indicating that the file is a binary file to be passed
through to the printer.
LPR
-S myprinter -P myqueue -o l myfile.psbin
201
9.10.6.2 Using an LPR Port

If data is sent instead using an LPR port (See 5.2.2, Creating a Definition for the
IBM Network Station Printer on page 74 for an example of how to define such a
port), all jobs going through that port use a control command flag of l by default,
which is an indication to the receiving LPD to make no alterations to the data being
received.
9.10.6.3 Changing the Default LPR Control Command Flag

If for any reason the default flag of l used by the LPR port needs to be changed to f
for example, this can only be done by altering the Registry entry for this port. It
cannot be done on a job basis, which we can do when using the command line
version of LPR.
To change this default, use the regedt32 registry editor and locate the following
key:
HKEY_LOCAL_MACHINE\
SYSTEM\
CurrentControlSet\
Control\
Print\
Monitors\
LPRPorts\
Ports\
portname\
ipaddress:portname
Insert a value named PrintSwitch, of type REG_SZ and enter the default control
command that you want this LPR port to use.
9.10.6.4 Receiving LPR Requests (by LPD)

On the receiving side of a Windows NT system, the LPD daemon assigns a data
type of TEXT whenever it receives a control flag of f, o or p.
For a control flag of l, it assigns a data type of RAW so that the print processor
does not alter the data in any way.
Note that the LPD assigns this data type specifically, based on the received control
flag, which means that the default data type specified in the print pre-processor has
no effect.
If you want to always force passthrough on a Windows NT printer/queue, see the
instructions in the section below (9.10.6.5, Forcing LPD Passthrough on Windows
NT).
9.10.6.5 Forcing LPD Passthrough on Windows NT

When Windows NT receives a spool file from an LPR requester, the LPD daemon
may process the data differently dependent on the flags specified by the LPR
requester.
If Windows NT assumes that the spool file is Text which needs to be passed
through a Windows NT printer driver, but the file is already processed (such as a
PostScript file), the effect is undesirable.
202
Print jobs received from the IBM Network Station should be processed correctly by
Windows NT because the IBM Network Station sets the proper flag in the control
file (the l flag).
However, should it become necessary to force the use of passthrough when
queuing LPR print jobs for a certain printer, this can be accomplished by making
changes to the Windows NT Registry to alter the way it behaves when receiving
spool files.
Using the Registry Editor
Using the Registry Editor incorrectly can cause serious system-wide problems
that may require you to reinstall Windows NT to correct them. Microsoft does
not guarantee that any problems resulting from the use of the Registry Editor
can be solved. Use this tool at your own risk.
In Windows NT 3.5, 3.51 and 4.0, the change affects all output that is received by
the LPD server. In Windows NT 4.0 Service Pack 2, it becomes possible to
configure LPD passthrough on a per-printer basis.
The following sections detail how to make the change in Windows NT versions
3.51, 4.0 and 4.0 with Service Pack 2 loaded. If after using these instructions,
Windows NT still prints incorrectly, please refer to 9.10.6.5, Forcing LPD
Passthrough on Windows NT on page 202.
9.10.6.6 Configuring Windows NT 3.5 and 3.51 for LPD

Passthrough
In Windows NT 3.5 and 3.51, it is necessary to make a change that will affect all
output received from LPR clients.
Start the Registry Editor. This can be done by selecting Program
ManagerFileRun.... In the Run dialog box, type REGEDT32 into the Command
Line box, and then click on OK. The Registry Editor will then start.
Find the window titled HKEY_LOCAL_MACHINE on Local Machine. Select the
SYSTEM\CurrentControlSet\Services\LPDSVC\Parameters folder. We now see
the following screen:
203
Figure 209. The Windows NT 3.51 Registry Editor
From the Edit menu, we select Add Value... to get the Add Value dialog. In this
window we enter:
Value Name
SimulatePassThrough
Data Type
REG_DWORD
Once we have we entered this information, we click OK. The DWORD Editor
window will appear, and we can enter the Data as 1. A value of 0 for this will
mean that the LPD will assign data types according to the control commands. A
value of 1 will mean that the LPD will just pass the received data through, without
altering it.
We can now click OK, so that the Registry Editor now looks like this:
Figure 210. The Windows NT 3.51 Registry Editor with SimulatePassThrough Added
204
Windows NT 3.51 looks for this new registry entry in the LPD key, instead of the
LPDSVC key. We therefore need to create a new key called LPD, and copy the
contents of the LPDSVC key into it.
Still in the Registry Editor, find the window titled HKEY_LOCAL_MACHINE on Local
Machine. Select SYSTEM\CurrentControlSet\Services. Go to the Edit menu, and
select Add Key... The Add Key dialog appears. In this window, enter:
Key Name
LPD
Class
Leave this blank.
Once we have entered this data, we click on OK. Scroll down to see that there is a
new key called LPD which has just been created:
Figure 211. The Windows NT 3.51 Registry Editor with new LPD key created
Now we select the LPDSVC key, and then, from the Registry menu, choose Save
Key..., and save the key as LPDSVC.KEY. We have now saved a copy of the
LPDSVC key to disk.
Next select the LPD key, and then, from the Registry menu, choose Restore..., and
restore the LPDSVC.KEY key that was just saved. A warning message appears:
Figure 212. The Windows NT 3.51 Warning Message
We do wish to restore the LPDSVC values, so we select Yes.
205
We now have an LPD key which is an exact copy of the LPDSVC key:
Figure 213. The Windows NT 3.51 Registry Editor with the LPDSVC Key Copied to the LPD
Key
In order for our changes to take effect, we need to stop and restart the printing
services. To get the Services tool we choose Program ManagerMainControl
PanelServices. The services that we need to stop and then start again are the
Spooler and the TCP/IP Print Server.
We have now configured Windows NT so that print files received on the LPR will
use passthrough, and will not be changed by Windows NT.
9.10.6.7 Configuring Windows NT 4.0 for LPD Passthough

In Windows NT 4.0, it is necessary to make a change that will affect all output
received from LPR clients.
Start the Registry Editor. This can be started by clicking StartRun..., and typing
REGEDT32 as the name of the program that we want to start. Click OK, and the
Registry Editor will start.
SYSTEMCurrentControlSetServicesLPDSVC Parameters folder. We
see the following screen:
206
From the Edit menu, select Add Value..., to get the Add Value window. In this
window, enter:
Value Name
SimulatePassThrough
Data Type
REG_DWORD
Once this information is entered, click OK. The DWORD Editor window appears,
and we can enter the Data as 1. A value of 0 for this means that the LPD assigns
data types according to the control commands. A value of 1 means that the LPD
just passes the received data through, without altering it.
Now click on OK, so that the Registry Editor now looks like this:
207
Close the Registry Editor. For the change to take effect, we stop and start the
affected spooling services. To get the list of Services, use
StartSettingsControl PanelServices. The services that we need to stop
and then start are the Spooler and the TCP/IP Print Server.
We have now configured Windows NT so that print files received on LPR will use
passthrough, and will not be changed by Windows NT.
9.10.6.8 Configuring Windows NT Service Pack 2 for LPD

passthrough
When using Windows NT with Service Pack 2 and later, it is possible to configure
LPD passthrough on a per-printer basis.
Start the Registry editor using StartRun..., and typing REGEDT32 as the name of
the program. Click OK.
SYSTEMCurrentControlSetControlPrint
PrintersprinterPrinterDriverData, where printer is the printer that we wish to
change.
208
From the Edit menu, select Add Value to get the Add Value window. In this
window, enter:
Value Name
SimulatePassThrough
Data Type
REG_DWORD
Once this information is entered, click on OK. The DWORD Editor window
appears, and we can enter the value as 1. A value of 0 for this means that the LPD
will queue the print with a Data Type of TEXT, which means that it will change the
spool file. A value of 1 for this means that the LPD will just pass the received data
through without altering it.
Click on OK so that the Registry Editor now looks like this:
209
Close the Registry Editor. For the change to take effect, we need to stop and start
the affected spooling services. To get the Services list, click
StartSettingsControl PanelServices. The services to stop and then start
are the Spooler and the TCP/IP Print Server.
We have now configured Windows NT, so that print files received on LPR to this
printer will not be changed by Windows NT.
9.10.6.9 Verifying If Passthrough Is Actually Used

If after using the instructions above spool files still print incorrectly, check the
following:
In Windows NT 3.51, start the Print Manager, by clicking on Program
ManagerMainPrint Manager and select PrinterPause to pause the
queue. Send print to the queue again, and when it appears, select
DocumentDetails... to display the details of the document:
210
Figure 218. Document Details
In Windows NT 4.0, open the Printers folder, by clicking on

StartSettingsPrinters, and double-click on the printer icon. A window
appears with the the name of the printer queue as the title. Choose
PrinterPause Printing to pause the queue, and send a document to the
printer again. When the file appears, select it and click DocumentProperties
to look at the properties of the document.
211
Figure 219. Document Properties
If the data type is RAW, then the changes to the Registry have taken effect.
If the data type is TEXT then the changes to the Registry have not taken effect,
and we need to:
Check in the Registry Editor to ensure that the SimulatePassThrough value
has been added correctly. It should read as:
SimulatePassThrough : REG_DWORD : x1
Ensure that the print services were stopped and restarted.
9.10.7 Control Commands Used by OS/2

The LPD server in OS/2 assumes that the received file is binary if there is no
indication of the file type in the control file. If the sender identifies the data type as
binary, the data is put in the queue as is. If the type is indicated as TEXT, then the
LPD on OS/2 converts LFs into CRLFs.
The LPD default can be changed to TEXT if the LPD server is started from the
command line with the -f option.
212
For the lpr parameters available in OS/2, use the lpr -? command.
9.10.8 Control Commands Used by AIX

On an AIX system, the LPD daemon uses the control commands to determine
which flags to generate to the AIX spooler backend.
The spooler backend then, based on the control flags, may choose to parse the
print data to determine its datastream type, and use appropriate filtering to convert
the data suitable to the target printer.
On the sending side, the LPR requester in UNIX almost always sends a control flag
of f.
9.11 Working with Windows NT Printers/Queues

Here are a few pointers and tips when working with printers/queues in Windows
NT.
This is not meant as a complete explanation of all one needs to know about
printing on Windows NT, but only as a few pieces of information that might be
useful if the user is not familiar with working with these printer definitions.
9.11.1 Assigning Printers to Ports

When a printer/queue is defined, it represents a logical entity or container into
which print jobs are stored until such time that they actually get sent to a printer.
Figure 220. Windows NT - Printers and Ports
At the time that you define a printer, you identify the printer driver to be used for
that logical printer, and you also identify the port to which this printer is connected.
For example, the IBM4029 printer illustrated in the figure below has been defined
as connected to port LPT1. This display is obtained by selecting the printer icon,
clicking the right mouse button and selecting Properties.
213
Figure 221. Windows NT - Printer Properties - Port Assignment
If we also had a printer attached to the LPT2 port, we could use the printer pooling
facility and assign this IBM4029 printer to both the LPT1 and LPT2 ports, which
causes jobs in this printer queue to be serviced by two printers.
This is done by selecting the Enable printer pooling button at the bottom of the
panel, which then allows you to click on LPT2. You have to click on OK before
these changes take place. If you then re-open Properties for that printer, you
should see the following display:
214
Figure 222. Windows NT - Printer Properties - Printer Pooling
If on the other hand, what you need to do is assign a second printer queue to the
same LPT1 port, then open the other printer icon's Properties (in our example, we
also have a printer called NS4029), select the Ports tab, click on LPT1, and click
on OK.
When you re-open the properties for this printer or for any other printer, you will
see two printer names appear besides the LPT1 port, as illustrated in the figure
below:
215
Figure 223. Windows NT - Printer Properties - Multiple Printers per Port
If you noticed, we took the NS4029 printer, which was previously assigned to the
LPR port called 9.24.105.189:PARALLEL1 and we re-assigned it to LPT1, the same
port as the IBM4029 printer.
We had originally intended the NS4029 printer queue to send print jobs to our IBM
Network Station printer. Print jobs could have accumulated in the queue because
the remote printer at the IBM Network Station was down for example. In this case,
re-assigning the NS4029 printer queue to the LPT1 port allows us to reroute the
jobs in the NS4029 printer queue to the local LPT1 port and print them there
(assuming that the printer on LPT1 has the same capabilities as the one that is
attached to the IBM Network Station).
9.11.2 Local Spooling for a LAN Printer

Another facility that might be useful when working with Windows NT printer queues
is the ability to define a local printer to represent a LAN printer.
Normally, when defining a network printer (see Figure 145 on page 143), you only
need to select a printer in the shared printer list. In the example shown in the
referenced figure, we selected the IBM4029 printer on the NSTATIONSERVER
server. Notice that the Share name of that printer is IBM4029CB, which we use in
a moment to make another printer definition.
When a printer is defined that way, as a LAN printer, data sent to this printer is not
spooled locally but it is sent directly to the printer, and the network connection must
be available at the time that the print job is sent to that printer.
However, in Windows NT you can define a local printer port which represents that
LAN printer, in order to benefit from local spooling capabilities. In that case, data
sent to that printer is spooled locally, and then sent to the remote LAN printer. Jobs
216
can be held in the local spool queue, if required (for example if our LAN connection
is not available at that moment), and later de-spooled to the LAN printer.
You can define such a local printer in a fashion similar to what we did earlier to
define an LPR port. If you look at Figure 60 on page 75, instead of selecting LPR
Port, select Local Port.
You are then presented with the following panel, on which we enter
\\servername\sharename. In this example, we used \\nstationserver\IBM4029CB,
and then gave that printer the name IBM 4029 Laser Printer in the next panels.
Figure 224. Windows NT - Add Printer - Local Port
The result, after the printer is created, is as follows. If you select that printer, open
its Properties and select the Ports tab, you get a display similar to the one below:
Figure 225. Windows NT - A Local Port for a LAN Printer
217
Notice that the port to which this printer is attached shows as

\\nstationserver\IBM4029CB. When this printer called IBM4029 Laser Printer is
selected by the application, the print data is spooled here first before being sent to
the shared LAN printer called IBM4039CB.
If you also define the same LAN printer as a network printer in the normal fashion,
it appears in your Printers folder under the same name that it has on the server,
with the additional text on servername. When you open this printer icon, and select
Properties, you are in fact looking at the actual printer properties on the server
itself, and the ports listed under the Properties tab are the ports defined on the
server and not on your local system.
9.11.3 Printing to File

If for some reason you need to send printed output to a file rather than a real
printer, you should have noticed in all the above examples that there is a port
called File.
Select the printer icon that you want to use, open its Properties, select the Ports
tab, click on the File port, and click OK to finish.
When you send output to that printer, you are prompted to supply a filename where
the output is to be stored.
9.12 Typical and Common Situations

In this section, we list a few of the common situations or error conditions that you
may encounter, the symptoms and the potential causes.
9.12.1 No Printers Configured

When you use the Print pull-down of an application, such as the 3270 emulator for
example, you might get a message such as There are no printers configured. See
System Administrator.
This is an indication that the printer table has not been defined and configured with
entries for local and remote print destinations.
See 9.9.1, The Print Section Configuration on page 183 for instructions on how to
verify the contents of the printer table.
9.12.2 Load Letter Message on the Printer

Sometimes, the printer stops between pages and displays a message saying LOAD
LETTER or something similar on the front panel. There are two probable main
causes:
The printer has run out of paper.
The wrong type of forms are loaded.
Some printers are able to detect what paper size has been loaded, and compare
this with the paper that is requested by the print job. If these do not match, the
printer requests that the proper form type be loaded.
218
It is possible to tell the printer to continue printing on the incorrect paper size
anyway, by using a button on the printer such as Continue.
The usual reason for this to occur is that many applications default to using U.S.
paper sizes, such as Letter, whereas many countries use different paper sizes,
such as A4. Some applications seem to always default to Letter status, while some
do "remember" the last setting that was used by the user.
9.12.3 Waiting Message on the Printer

If the file to be printed is a PostScript file that contains imbedded fonts, these fonts
must be loaded by the printer, as part of the print job, before the data can be
printed.
This can take a long time. If you get the message WAITING on the printer, and it
should alternate between BUSY and WAITING for a while, then one needs to be
patient and wait until the fonts have been downloaded.
For example, using an IBM4029 PostScript printer attached to an IBM Network
Station Series 1000 model, and a PostScript file of 279 KB in length that includes
imbedded fonts, the processing time before the printer starts printing was
approximately 4 minutes and 45 seconds, and an additional 30 seconds to print the
three pages of the actual print data.
If the same file is processed without the imbedded fonts, the file size drops to 16
KB, instead of 279 KB, and the total print time is then approximately 50 seconds.
219
220

Because the print APIs available with the IBM Network Station are not really
accessible directly by the user, but only by developers, we only provide here a
summary of the functions provided by this API as a matter of reference and
information.
We do not provide examples of using these APIs or any in-depth information on
their features and functions.
10.1 Release 1 APIs

Release 1 was the initial release of the IBM Network Station and it provided only
rudimentary print support. A set of print APIs were provided to allow local client
applications to print directly to the parallel port on the IBM Network Station. The
APIs did not allow printing to the serial port or over the network to remote print
servers.
The set of print APIs available in Release 1 were as follows:
getPrintAPIs
This routine returns an array of function pointers to the

individual print API routines.
getPrinterList
This routine returns information from the printer list created

by the system administrator. For Release 1, the API is hard
coded with the only entry being the parallel port.
setDefaultPrinter
This routine designates which printer in the printer list is the

default printer for all local applications. For Release 1, the
API only accepts the first printer in the list since the list is
hard coded with only one entry.
printOpen
This routine opens a socket connection to the printer

selected by the application.
printWrite
This routine writes print data to the printer.
printClose
This routine closes the socket connection to the printer.
10.2 Release 2 APIs

One new API, the printOpenSerial was added in Release 2 to allow applications to
print to the serial port, but this API is removed in Release 3 since it is no longer
required.
10.3 Release 3 APIs

The print APIs have been modified for Release 3 to support printing to the serial
port and to remote printers. Several of the APIs have been modified, and one API
that was available in prior releases has been deleted. Here is a list of the APIs that
were modified along with a brief description of what changed in each one:
getPrintAPIs
This routine returns an array of function pointers to the

individual print API routines.
221
222
getPrinterList
This routine returns information from the list of printers

maintained by the system administrator in the configuration
files. This list may contain the local serial printer, the local
parallel printer, and any number of remote printers. Certain
information about each printer is maintained in the list and
can be retrieved with the getPrinterList API. The information
in the list includes printer queue name, system hostname for
remote printers, type of data stream supported by the printer,
description of the printer, whether or not the printer is the
default for the network station, whether or not banner pages
should be sent to remote printers, and some DBCS
conversion information.
setDefaultPrinter
This routine allows the user to indicate which printer from the
printer list should be the default printer for all local
applications.
getDefaultPrinter
This routine is used to retrieve the index of the default

printer. The routine returns the index into the printer list table
that was last set using the routine setDefaultPrinter in the
current boot cycle of the network station. However, if no
system-wide default has been set yet, this routine determines
the default printer by browsing the printer table in the order of
per-user, per-terminal and per-system entries from last to first
in each group, checking to see if the configuration parameter
use-as-default is set to true. It returns the index of the first
entry that is found matching this criteria. If no entry is found
with the value for the configuration parameter use-as-default
as true, the API returns the index of the first printer entry in
the printer list.
printOpen
This routine was modified to allow sending print job options,

such as number of copies and whether or not to print a
banner page. Additionally, if the printer being opened is a
DBCS printer, the DBCS converter module may provide an
initialization routine to set the printer to the correct mode
before sending any application data via the printWrite API.
printOpenSerial
This routine has been deleted in Release 3 because it is no

longer needed. Printing to the local serial port is supported
by the printOpen API with the index value for the serial
printer.
printWrite
This routine has been enhanced to call a separate converter

module if so indicated in the printer list. For Release 3, the
only supported converter module is the DBCS converter. The
printWrite API accepts write requests from a local application
and then calls the DBCS converter to transform the data in a
form the printer understands. The DBCS converter also
performs the actual writing of data to the printer.
printClose
This routine has been enhanced for the situation where a

DBCS printer is being used. Before closing the connection to
the printer, a reset routine may be called in the DBCS
converter to return the printer to some known state before
terminating the connection.
printAbort
This routine aborts the connection to the printer in the middle

of printing. It should be invoked by the applications in the
event of a printer error (such as printer being offline, out of
paper, etc.) when the user elects to cancel the print job.
Upon invocation, this routine causes the SERIALD daemon
to flush the rest of the pending data and to close the
connection to the port (parallel or serial). If this routine is
invoked for a socket connection to the LPRD daemon (for
remote printer queues), the routine simply closes the
connection to the socket without waiting for the data to drain.
Note that once a connection is aborted using the routine
printAbort, there is no need to invoke the routine printClose
as the socket connection would have already been closed by
the routine printAbort.
getPrintXAPIs
This routine returns an array of function pointers to the print

GUI API routines.
printerSelectorGUI
This routine displays a list of printers (local and remote) to

allow the user to select a printer, and optionally to set one of
the printers as the system default applicable to all client
applications.
Local client applications are being encouraged to use this
new API, but they are not required to do so. These
applications can still call the getPrinterList API to get a list of
available printers and display them using a different user
interface. However, for a consistent look and feel, future
clients should use the printerSelectorAPI.
The routine can be used in three different ways:
1. The API can be directed to create its own application
context and a panel containing the printer selection. The
API retains control of X event processing for the panel.
2. The API can be directed to use the application context
created by the client application, and to create a panel in
this context. The API retains control of X event
processing for the panel.
3. The API can be directed to use the application context
and top widget created by the application, thus letting the
API only create the printer list inside the panel already
created by the client application. The client application
retains control of X event processing for the panel it has
created.
223
224

In a Single Byte Character Set (SBCS) environment, a single byte is used to
represent characters. This gives us the ability to represent 256 characters, which is
sufficient for the numbers, letters and special symbols used in western style
languages.
However, this is not sufficient for some languages such as Chinese, Japanese or
Korean which require a lot more than 256 characters, thereby the need to use two
bytes to represent characters, which provides the ability to code 65,536 characters.
In an SBCS environment, when an application sends data to a printer, each
character is represented by a single byte. (For example, the capital letter A is
represented by Ox41 when using code page 850.)
The printer receiving these characters knows how to interpret an 0x41 and how to
convert it into the printable A character.
Similarly, when using DBCS and printers that are DBCS-enabled, the application
can send 2 bytes for each character that it wants to print, and the printer can
translate these two bytes into the proper character to print.
However, what about situations where we have printers that are not DBCS-enabled
but that we want to use anyway to print some DBCS characters? That can be
accomplish by transforming DBCS characters into bitmaps images before sending
the data to the printer, and sending bitmaps rather than normal characters.
225
Figure 226. DBCS Conversion Processing
This facility, which is transforming DBCS print data from code points to character
bitmaps, has been added in Release 3. This is accomplished by a conversion
program that gets loaded and executed by the print APIs.
An application is now able to generate ASCII text with DBCS code points, send the
resulting output to a conversion program, which then sends the output to a printer
that does not have DBCS code pages loaded. The conversion program needs
certain information about the target printer to facilitate the transformation; this
information is stored in the printer list when configuring printers in IBM Network
Station Manager:
Transformation Module - This is the loadable module the print APIs will invoke.
For now only the DBCS conversion module is a choice but in the future,
additional conversion modules may be available.
DBCS Type - This is the type of DBCS output being generated by the
conversion program. The choices are ESC/P, IBM PS/55, IBM PAGES,
Cannon LIPS, NEC, KS, KSSM, and PCL.
Printer Resolution - This is the resolution, in dots per inch, of the target printer.
Resolution is needed to properly generate the bitmap image of the characters
226
being converted. Possible resolutions include 180, 300, 360, 600, 720, and
1200.
DBCS Font Encoding Method - This it the method used for encoding font
information in the output data stream. For Release 3, this field is not be used
by the DBCS converter. It is being reserved for future use. Possible font
encoding methods include BIG-5, 5550, shift-JIS, JIS, GB, GBK, KSSM, KS,
and TG.
For Release 3, the only applications generating ASCII text that can take advantage
of the DBCS conversion are the 5250 and 3270 emulators. The NC Navigator
browser generates PostScript data, so DBCS conversion is not possible.
These additional parameters from DBCS conversion processing are configured in
the IBM Network Station Manager when defining printers in the printer list. Please
refer to Chapter 4, Configuration Using the IBM Network Station Manager on
page 47 for general instructions on how to access the IBM Network Station
Manager and how to configure printers.
The figure below displays the panel on which the user defines printers. Notice the
button labeled ASCII Options... to the right of each entry in the panel.
When using DBCS conversion processing, this button allows the specification of the
parameters we discussed above, which are specific to DBCS processing. The next
figure is included for illustration purposes of the configuration of a DBCS printer; it
represents the panel displayed when a user clicks on the ASCII Options... button.
227
Figure 228. ASCII Options Configuration Panel
228

The following values are allowed for the image configuration (IMGCFG) field of the
CRTDEVPRT, CHGDEVPRT, CRTOUTQ and CHGOUTQ commands. You can
also use these values when using the convert image API. For more information on
how to use these values, see AS/400 System API Reference, SC41-5801. Each
value is described in terms of the data streams that are supported, the maximum
resolution in dots per inch (dpi), and whether the printer has color or supports
compression.
Table 8. Printers Supporting PCL Data Streams
Name
Printer
*IMGA01
PCL 300-dpi printer
*IMGA02
PCL 600-dpi printer
*IMGA03
PCL 1200-dpi printer
*IMGA04
PCL 300-dpi color printer
*IMGA05
*IMGA06
*IMGA07
PCL 75-dpi printer (No compression)
*IMGA08
PCL 600-dpi color printer with larger no-print border
*IMGA09
PCL 300-dpi printer (No compression)
Table 9. Printers Supporting PostScript Data Streams

Name
Printer
*IMGB01
PostScript 300-dpi printer
*IMGB02
*IMGB03
*IMGB04
PostScript 300-dpi color printer
*IMGB05
*IMGB06
*IMGB07
PostScript 600x300-dpi color printer
*IMGB08
*IMGB09
*IMGB10
*IMGB11
*IMGB12
*IMGB13
*IMGB14
PostScript 600-dpi color printer with larger no-print border
*IMGB15
PostScript 300-dpi color printer with larger no-print border
229
Table 10. Printers Supporting IPDS Data Streams

Name
Printer
*IMGC01
IPDS 240-dpi printer
*IMGC02
*IMGC03
*IMGC04
*IMGC05
IPDS 240-dpi printer with no-print border
*IMGC06
*IMGC07
*IMGC08
*IMGC09
IPDS 240-dpi printer (IM/1 image)
*IMGC10
IPDS 240-dpi printer (IM/1 image) with no-print border
*IMGC11
IPDS 240-dpi printer (CCITT G4)
Table 11. Printers Supporting PCL and PostScript Data Streams

Name
Printer
*IMGD01
PCL/PostScript 300-dpi printer
*IMGD02
*IMGD03
*IMGD04
PCL/PostScript 300-dpi color printer
*IMGD05
*IMGD06
*IMGD07
PCL 300-dpi/PostScript 600-dpi printer
*IMGD08
*IMGD09
*IMGD10
*IMGD11
PCL/PostScript 600-dpi color printer with larger no-print border
Table 12 (Page 1 of 3). Recommended Image Configuration Objects for Some Common Printers
Name
Printer
*IMGD01
Compaq Pagemarc 20
*IMGA01
Epson EPCL-4 Printer
*IMGA02
Epson EPCL-5 Printer
*IMGB10
Epson Stylus Photo with PostScript
*IMGB11
Epson Stylus Color 600, 800 with PostScript
*IMGA04
HP Color Laserjet 5
*IMGD04
HP Color Laserjet 5M
*IMGA04
HP Deskjet 560C, 820C, 1200C
*IMGA01
HP Deskjet 500, 600, 1200
230
Name
Printer
*IMGA04
HP Deskjet 1600C, 1600CN
*IMGD04
HP Deskjet 1600CM
*IMGA09
HP Laserjet II, IID, IIP
*IMGB01
HP Laserjet II, IID, IIP with PostScript
*IMGA01
HP Laserjet III, IIID, IIISi, 4L
*IMGD01
HP Laserjet III, IIID, IIISi, 4L with PostScript
*IMGA02
HP Laserjet 4, 4P, 4V, 4Si, 4 Plus
*IMGD02
HP Laserjet 4M, 4MP, 4MV, 4Si MX, 4M Plus
*IMGA02
HP Laserjet 5, 5P, 5Si
*IMGD02
HP Laserjet 5M, 5MP, 5Si MX
*IMGA02
HP Laserjet 6, 6P, 6L
*IMGD02
HP Laserjet 6M, 6MP
*IMGD02
IBM 3112, 3116 Page Printer with IPDS feature
*IMGA02
IBM 3112, 3116 Page Printer (ASCII/LAN)
*IMGD02
IBM 3112, 3116 Page Printer with PostScript
*IMGC01
IBM 3130, 3160-1 AF Printer (240-pel mode)
*IMGC02
IBM 3130 AF Printer (300-pel mode)
*IMGC09
IBM 3825, 3827, 3828 AF Printer
*IMGC01
IBM 3825, 3827, 3828 AF Printer (with AFIG)
*IMGC01
IBM 3829 AF Printer
*IMGC10
IBM 3835-001 AF Printer
*IMGC05
IBM 3835-001 AF Printer (with AFIG)
*IMGC05
IBM 3835-002, 3900 AF Printer
*IMGA01
IBM 3912, 3916 Page Printer (ASCII/LAN)
*IMGC06
IBM 3912, 3916 Page Printer with IPDS feature (twinax)
*IMGA01
IBM 3930-03 Page Printer
*IMGD01
IBM 3930-03 Page Printer with PostScript
*IMGC02
IBM 3935 AF Printer
*IMGA09
IBM 4019 LaserPrinters (HP mode)
*IMGB01
IBM 4019 LaserPrinters with PostScript
*IMGC06
IBM 4028 LaserPrinters
*IMGA01
*IMGB02
*IMGA01
*IMGD07
*IMGA02
*IMGD02
*IMGB09
IBM 4079 Color Jetprinter PS
231
Name
Printer
*IMGB05
IBM 4303 Network Color Printer
*IMGC06
IBM 4312, 4317, 4324 NP with IPDS feature (twinax)
*IMGC06
IBM 4312, 4317, 4324 NP with IPDS feature (LAN)
*IMGA02
IBM 4312, 4317, 4324 NP (ASCII/LAN)
*IMGD02
IBM 4312, 4317, 4324 NP with PostScript (ASCII/LAN)
*IMGC03
IBM InfoPrint 60
*IMGC05
IBM InfoPrint 62 Model 2
*IMGC06
IBM InfoPrint 62 Model 3
*IMGB05
IBM InfoColor 70
*IMGC05
IBM InfoPrint 4000
*IMGC06
IBM InfoPrint 4000 High Resolution
*IMGB02
Lexmark 4039Plus
*IMGD11
Lexmark Optra C Color Printer
*IMGA02
Lexmark Optra E, E+
*IMGD02
Lexmark Optra N
*IMGD02
Lexmark Optra R+, Rx+, Lx+, Lxn+
*IMGD02
Lexmark Optra S Printers
*IMGD05
Lexmark Optra SC Color Printer
*IMGA01
Okidata OL400 LED Page Printer
*IMGA02
Okidata OL800, OL810 LED Page Printers
*IMGB12
QMS 2025, 3225
*IMGD04
QMS Magicolor CX
*IMGB09
Tektronix Phaser 140
*IMGB04
*IMGB05
*IMGB05
Tektronix Phaser 540, 550
*IMGB06
*IMGA01
Xerox 4219/MRP
*IMGA02
Xerox 4220/MRP
*IMGA02
Xerox 4230 DocuPrinter
*IMGA02
Xerox 4512, 4517 Network Printer
*IMGB13
Xerox 4520mp Printer
*IMGD04
Xerox 4700 II Color Document Printer
*IMGB08
Xerox 4915 Color Laser Printer
*IMGB05
Xerox 4920, 4925 Color Laser Printer
232
Appendix B. Printing from the VTxxx Emulator to a Remote

IBM Network Station
The VTxxx emulator of the IBM Network Station, which is accessible through the
Terminal Console menu, allows a user to establish a telnet session to remote
hosts.
Data appearing in the terminal emulation window can be printed to a printer
attached to the parallel or serial port. However, in cases where there is no local
printer, there is a facility allowing the terminal emulator to print to the serial or
parallel port of a remote IBM Network Station.
This sort of a special situation, undocumented for the most part, might be useful in
certain situations, which is why we mention it here.
Figure 229. From IBM Network Stationto IBM Network Station
The VTxxx emulator on the IBM Network Station already has the ability to print to
the local serial or parallel port on the IBM Network Station where it executes. This
facility is used to normaly either print the content of the display (Print Screen), print
selected areas of the the display, such as a few lines of text in the message log for
example, or to print the content of the log buffer.
One can set some of the xserver-initial-x-resources parameter in such a way as to
configure a remote host on which to print the output of the VTxxx emulator.
As illustrated in the figure below, the required statement is:
set xserver-initial-x-resources =
"NCDterm\printerHost: itsonct1:5964
NCDterm\defaultPrintMode: Remote"
233
Figure 230. From VTxxx Emulator to Remote IBM Network Station
As a result, when the user starts the VTxxx emulator and uses the file pull-down,
the default entry Print to Remote is replaced by the entry Print on host:port as
shown in the figure below.
234
Figure 231. VTxxx Emulator File Pull-Down
When this entry is selected by the user, instead of the normal Print on Parallel 1,
the output of the print command is sent to the remote host specified.
Appendix B. Printing from the VTxxx Emulator to a Remote IBM Network Station
235
236

We summarize here, for your convenience, an example of all the configuration
parameters that are directly related to printing, which have been discussed in the
preceding chapters.
set print-lprd-cache-size = 1
set print-lpd-cache-size = 1
set print-lpd-stream-large-jobs = true
set print-access-control-enabled = true
set print-access-control-list = {
{ hostname }
}
set print-lpr-servers = {
{ "localhost" "PARALLEL1" "ps" "Local Parallel Printer" nil nil nil nil false true }
{ "localhost" "SERIAL1" "ps" "Local Serial Printer" nil nil nil nil false false }
{ "burkhart.austin.ibm.com" "locps" "ps" "ITSO Queue" nil nil nil nil true false }
{ "linna.austin.ibm.com" "javaps" "ps" "AIX4.2.1 server" nil nil nil nil true false }
{ "9.53.113.131" "javaps" "ps" "Remote AIX4.2.1" nil nil nil nil true false }
}
set serial-access-control-enabled = true

set serial-access-control-list = {
{ hostname tcpip }
}
print-access-control-enabled = true
print-access-control-list = {
{ hostname tcpip }
}
set parallel-daemons-table = {
{ 1 false 5964 }
}
set serial-daemons-table = {
{ 1 false 87 }
}
set serial-interfaces-table = {
{ 1 printer printer 96 8 1 none dtr/dsr none }
}
We also include here sections of the configd.doc file, which describes in detail each
of these parameters. We only included the PRINT, PARALLEL and SERIAL
groups, where most of the parameters directly related to printing are located.
Please refer to the copy of the configd.doc (or configd2.doc on Windows NT) file on
your installed boot server for a description of all the parameters.
If you are not already familiar with the information contained in the configd.doc file,
please refer to IBM Network Station Guide for Windows NT, SG24-2127-01,
Appendix D, for a short description of how to interpret this file.
237
GROUP print
NAME
HIDEBOX
SNMP NAME
SNMP PATH
TYPE
DEFAULT
PERMISSION
EFFECT
NVRAM
DESCRIPTION
print-access-control-enabled
Console=>Setup=>Change Setup Parameters=>
Print=>Enable Access Control
ncdPrintAccessControlEnabled
ncdPrint 4
BOOL
false
READ-WRITE
IMMEDIATE
NO
Indicates whether to check the access control list.
NAME
HIDEBOX
SNMP NAME
SNMP PATH
TYPE
PERMISSION
EFFECT
NVRAM
DESCRIPTION
print-access-control-list
Print=>Print Access Control List
ncdPrintAccessControlTable
ncdPrint 5
TABLE
READ-WRITE
IMMEDIATE
NO
Specifies the list of IP hosts that are allowed
access to the print daemon
BEGIN TABLE ROW ENTRIES

NAME
SNMP NAME
SNMP PATH
TYPE
VIEW
MIN
MAX
PERMISSION
NVRAM
DESCRIPTION
index
ncdPrintAccessControlTableIndex
ncdPrintAccessControlTable 1
INTEGER
SNMP ONLY
4294967295
READ-ONLY
NO
Index into the Print Access Control table
NAME
SNMP NAME
SNMP PATH
TYPE
DEFAULT
PERMISSION
EFFECT
NVRAM
DESCRIPTION
host
ncdPrintAccessControlTableHost
ncdPrintAccessControlTable 2
STRING
nil
READ-WRITE
IMMEDIATE
NO
Specifies the network name/address
of a node granted permission to
access the print daemon.
238
END TABLE ROW ENTRIES

NAME
HIDEBOX
SNMP NAME
SNMP PATH
TYPE
MIN
DEFAULT
MAX
PERMISSION
EFFECT
NVRAM
DESCRIPTION
print-lpd-cache-size
Print=>Lpd Cache Size
ncdPrintLpdCacheSize
ncdPrint 1
INTEGER
1
95
READ-WRITE
IMMEDIATE
NO
Maximum percentage of available memory LPD will allocate for
print job
NAME
HIDEBOX
SNMP NAME
SNMP PATH
TYPE
DEFAULT
PERMISSION
EFFECT
NVRAM
DESCRIPTION
print-lpd-stream-large-jobs
Print=>Lpd Stream Large Jobs
ncdPrintLpdStreamLargeJobs
ncdPrint 3
BOOL
true
READ-WRITE
IMMEDIATE
NO
Indicates whether incoming jobs that overflow
the cache are switched to streaming mode
NAME
HIDEBOX
SNMP NAME
SNMP PATH
TYPE
PERMISSION
EFFECT
NVRAM
DESCRIPTION
print-lpr-servers
Print=>Lpr Servers
ncdPrintLprServersTable
ncdPrint 6
TABLE
READ-WRITE
IMMEDIATE
NO
Print server information

NAME
SNMP NAME
SNMP PATH
TYPE
VIEW
MIN
MAX
PERMISSION
index
ncdPrintLprServersTableIndex
ncdPrintLprServersTable 1
INTEGER
SNMP ONLY
4294967295
READ-ONLY
239
NVRAM
DESCRIPTION
NO
Index into the Print Lpr Servers table
NAME
SNMP NAME
SNMP PATH
TYPE
DEFAULT
PERMISSION
EFFECT
NVRAM
DESCRIPTION
server
ncdPrintLprServersTableServer
STRING
nil
READ-WRITE
IMMEDIATE
NO
server name
NAME
SNMP NAME
SNMP PATH
TYPE
DEFAULT
PERMISSION
EFFECT
NVRAM
DESCRIPTION
queue-name
ncdPrintLprServersTableQueueName
STRING
nil
READ-WRITE
IMMEDIATE
NO
queue name
NAME
SNMP NAME
SNMP PATH
TYPE
DEFAULT
PERMISSION
EFFECT
NVRAM
DESCRIPTION
datastream-type
ncdPrintLprServersTableDatastreamType
STRING
nil
READ-WRITE
IMMEDIATE
NO
datastream type
NAME
SNMP NAME
SNMP PATH
TYPE
DEFAULT
PERMISSION
EFFECT
NVRAM
DESCRIPTION
description
ncdPrintLprServersTableDescription
STRING
nil
READ-WRITE
IMMEDIATE
NO
description
NAME
SNMP NAME
SNMP PATH
TYPE
DEFAULT
240
transform-file
ncdPrintLprServersTableTransformFile
STRING
nil
PERMISSION
EFFECT
NVRAM
DESCRIPTION
READ-WRITE
IMMEDIATE
NO
full path to transform file
NAME
SNMP NAME
SNMP PATH
TYPE
DEFAULT
PERMISSION
EFFECT
NVRAM
DESCRIPTION
dbcs-type
ncdPrintLprServersTableDbcsType
STRING
nil
READ-WRITE
IMMEDIATE
NO
DCBS type
NAME
SNMP NAME
SNMP PATH
TYPE
DEFAULT
PERMISSION
EFFECT
NVRAM
DESCRIPTION
print-resolution
ncdPrintLprServersTablePrintResolution
STRING
nil
READ-WRITE
IMMEDIATE
NO
print resolution
NAME
SNMP NAME
SNMP PATH
TYPE
DEFAULT
PERMISSION
EFFECT
NVRAM
DESCRIPTION
dbcs-font-encoding
ncdPrintLprServersTableDbcsFontEncoding
STRING
nil
READ-WRITE
IMMEDIATE
NO
DBCS font encoding
NAME
SNMP NAME
SNMP PATH
TYPE
DEFAULT
PERMISSION
EFFECT
NVRAM
DESCRIPTION
request-banner-page
ncdPrintLprServersTableRequestBannerPage
BOOL
false
READ-WRITE
IMMEDIATE
NO
request banner page
NAME
SNMP NAME
SNMP PATH
use-as-default
ncdPrintLprServersTableUseAsDefault
241
TYPE
DEFAULT
PERMISSION
EFFECT
NVRAM
DESCRIPTION
BOOL
false
READ-WRITE
IMMEDIATE
NO
indicates whether this entry should be the default

NAME
HIDEBOX
SNMP NAME
SNMP PATH
TYPE
MIN
DEFAULT
MAX
PERMISSION
EFFECT
NVRAM
DESCRIPTION
print-lprd-cache-size
Print=>Lprd Cache Size
ncdPrintLprdCacheSize
ncdPrint 2
INTEGER
1
95
READ-WRITE
IMMEDIATE
NO
Maximum percentage of available memory LPRD will allocate for
print job
GROUP parallel
NAME
HIDEBOX
SNMP NAME
SNMP PATH
TYPE
PERMISSION
EFFECT
NVRAM
DESCRIPTION
parallel-daemons-lat-service-passwords
Access Control=>Parallel Daemon LAT Service Passwords
ncdAccessParalleldLatPasswdTable
ncdAccess 36
TABLE
READ-WRITE
IMMEDIATE
NO
Specifies the LAT service passwords required to
gain access to the parallel port daemon using LAT.

NAME
SNMP NAME
SNMP PATH
TYPE
VIEW
MIN
MAX
PERMISSION
NVRAM
DESCRIPTION
index
ncdAccessParalleldLPTIndex
ncdAccessParalleldLatPasswdTable 1
INTEGER
SNMP ONLY
4294967295
READ-ONLY
NO
Index into the Parallel Daemons LAT Passwds Table
242
NAME
SNMP NAME
SNMP PATH
TYPE
MIN
MAX
PERMISSION
NVRAM
DESCRIPTION
port-number
ncdAccessParalleldLPTPortNumber
INTEGER
1
2
READ-ONLY
NO
The name of the parallel port.
NAME
SNMP NAME
SNMP PATH
TYPE
DEFAULT
PERMISSION
EFFECT
NVRAM
DESCRIPTION
password
ncdAccessParalleldLPTPassword
STRING
nil
WRITE-ONLY
AT_BOOT
NO
Specifies the LAT service password.

NAME
HIDEBOX
SNMP NAME
SNMP PATH
TYPE
PERMISSION
NVRAM
DESCRIPTION
parallel-daemons-statistics-table
Console=>Statistics=>Show Statistics=>
Parallel Daemons=>Parallel Daemon Statistics Table
ncdParallelDStatsTbl
ncdParallel 2
TABLE
READ-ONLY
NO
Specifies the table of parallel daemon statistics.

NAME
SNMP NAME
SNMP PATH
TYPE
MIN
MAX
PERMISSION
NVRAM
DESCRIPTION
port-number
ncdParallelDStatsTblPortNumber
ncdParallelDStatsTbl 1
INTEGER
1
2
READ-ONLY
NO
NAME
SNMP NAME
SNMP PATH
TYPE
MIN
connections-accepted
ncdParallelDStatsTblConnAccepts
INTEGER
243
MAX
PERMISSION
NVRAM
DESCRIPTION
4294967295
READ-ONLY
NO
The number of connections made to the parallel daemon.
NAME
SNMP NAME
SNMP PATH
TYPE
MIN
MAX
PERMISSION
NVRAM
DESCRIPTION
connections-with-access-control-errors
ncdParallelDStatsTblConnBadAccesses
INTEGER
4294967295
READ-ONLY
NO
The number of connections that were closed by the
parallel daemon due to the remote address not being
present in the parallel daemon's access control list.
NAME
SNMP NAME
SNMP PATH
TYPE
MIN
MAX
PERMISSION
NVRAM
DESCRIPTION
connections-with-io-errors
ncdParallelDStatsTblConnIOErrors
INTEGER
4294967295
READ-ONLY
NO
parallel daemon due to the a local I/O error. This
includes the user aborting the connection via local
mechanisms.
NAME
SNMP NAME
SNMP PATH
TYPE
MIN
MAX
PERMISSION
NVRAM
DESCRIPTION
connections-with-normal-completion
ncdParallelDStatsTblConnEofCloses
INTEGER
4294967295
READ-ONLY
NO
remote host. This is the normal mode of ending a
connection to the parallel daemon.

NAME
HIDEBOX
SNMP NAME
SNMP PATH
TYPE
244
parallel-daemons-table
Parallel=>Parallel Daemons Table
ncdParallelDTable
ncdParallel 1
TABLE
PERMISSION
EFFECT
NVRAM
DESCRIPTION
READ-WRITE
IMMEDIATE
NO
Specifies the table of parallel daemon parameters.

NAME
SNMP NAME
SNMP PATH
TYPE
VIEW
MIN
MAX
PERMISSION
NVRAM
DESCRIPTION
parallel-daemon-table-index
ncdParallelDTableIndex
ncdParallelDTable 1
INTEGER
SNMP ONLY
4294967295
READ-ONLY
NO
The index into the parallel daemons table
NAME
SNMP NAME
SNMP PATH
TYPE
MIN
MAX
PERMISSION
NVRAM
DESCRIPTION
port-number
ncdParallelDTablePortNumber
ncdParallelDTable 2
INTEGER
1
2
READ-ONLY
NO
NAME
SNMP NAME
SNMP PATH
TYPE
DEFAULT
PERMISSION
EFFECT
NVRAM
DESCRIPTION
use-parallel-protocol
ncdParallelDTableUseParaProt
ncdParallelDTable 3
BOOL
false
READ-WRITE
IMMEDIATE
NO
Specifies that the parallel daemon control protocol
should be used. Note that this could cause some data
loss if enabled with old host software.
NAME
SNMP NAME
SNMP PATH
TYPE
MIN
DEFAULT
MAX
PERMISSION
EFFECT
tcp-port
ncdParallelDTableTCPPort
ncdParallelDTable 4
INTEGER
1
5964
65535
READ-WRITE
AT_BOOT
245
NVRAM
DESCRIPTION
NO
Specifies the TCP port on which the terminal
listens for raw TCP connections to the parallel
daemon.
NAME
SNMP NAME
SNMP PATH
TYPE
DEFAULT
PERMISSION
EFFECT
NVRAM
DESCRIPTION
ncdnet-object-name
ncdParallelDTableNCDnetObjName
ncdParallelDTable 5
STRING
PARALLELD
READ-WRITE
AT_BOOT
NO
Specifies the NCDnet object on which the terminal
listens for NCDnet connections to the parallel
daemon.
NAME
SNMP NAME
SNMP PATH
TYPE
DEFAULT
PERMISSION
EFFECT
NVRAM
DESCRIPTION
enable-lat-service
ncdParallelDTableEnableLAT
ncdParallelDTable 6
BOOL
false
READ-WRITE
AT_BOOT
NO
Specifies that the unit is to accept incoming
LAT solicit messages for a service which
allows access to the parallel daemon. This is used
to support VMS print services to the unit.
NAME
SNMP NAME
SNMP PATH
TYPE
DEFAULT
PERMISSION
EFFECT
NVRAM
DESCRIPTION
lat-service-name
ncdParallelDTableLATServName
ncdParallelDTable 7
STRING
nil
READ-WRITE
AT_BOOT
NO
Specifies the name of the parallel daemon LAT service.
NAME
SNMP NAME
SNMP PATH
TYPE
MIN
DEFAULT
MAX
PERMISSION
EFFECT
246
lat-service-rating
ncdParallelDTableLATServRating
ncdParallelDTable 8
INTEGER
5
255
READ-WRITE
AT_BOOT
NVRAM
DESCRIPTION
NO
Specifies the rating of the parallel daemon LAT service.
GROUP serial
NAME
HIDEBOX
SNMP NAME
SNMP PATH
TYPE
DEFAULT
PERMISSION
EFFECT
NVRAM
DESCRIPTION
serial-access-control-enabled
Access Control=>Enable Serial and Parallel Access Control
ncdAccessSerialdAccessControlEnabled
ncdAccess 31
BOOL
false
READ-WRITE
IMMEDIATE
NO
Specifies whether xhost-style access control
is on or off for requests to connect to the
serial or parallel port daemon.
NAME
HIDEBOX
SNMP NAME
SNMP PATH
TYPE
PERMISSION
EFFECT
NVRAM
DESCRIPTION
serial-access-control-list
Access Control=>Serial and Parallel Access Control List
ncdAccessSerialdAccessControlTable
ncdAccess 32
TABLE
READ-WRITE
IMMEDIATE
NO
Specifies the host access control list for the serial
or parallel port daemon.

NAME
SNMP NAME
SNMP PATH
TYPE
VIEW
MIN
MAX
PERMISSION
NVRAM
DESCRIPTION
index
ncdAccessSerialdACTIndex
ncdAccessSerialdAccessControlTable 1
INTEGER
SNMP ONLY
4294967295
READ-ONLY
NO
Index into the Serial Access Control List
NAME
SNMP NAME
SNMP PATH
host
ncdAccessSerialdACTAddress
247
TYPE
DEFAULT
PERMISSION
EFFECT
NVRAM
DESCRIPTION
STRING
nil
READ-WRITE
IMMEDIATE
NO
Specifies the network name/address
of a node granted permission to
remotely access the serial or parallel
port daemon.
NAME
SNMP NAME
SNMP PATH
TYPE
CHOICES
DEFAULT
PERMISSION
EFFECT
NVRAM
DESCRIPTION
family
ncdAccessSerialdACTFamily
CHOICE
{ tcpip ncdnet lat }
tcpip
READ-WRITE
IMMEDIATE
NO
Specifies the type of network connection for
which this entry applies.

NAME
HIDEBOX
SNMP NAME
SNMP PATH
TYPE
PERMISSION
EFFECT
NVRAM
DESCRIPTION
serial-daemons-lat-service-passwords
Access Control=>Serial Daemon LAT Service Passwords
ncdAccessSerialdLatPasswdTable
ncdAccess 3
TABLE
READ-WRITE
IMMEDIATE
NO
Specifies the LAT service passwords required to
gain access to the serial port daemons using LAT.

NAME
SNMP NAME
SNMP PATH
TYPE
VIEW
MIN
MAX
PERMISSION
NVRAM
DESCRIPTION
index
ncdAccessSerialdLPTIndex
ncdAccessSerialdLatPasswdTable 1
INTEGER
SNMP ONLY
4294967295
READ-ONLY
NO
Index into the Serial Daemons LAT Passwds Table
248
NAME
SNMP NAME
SNMP PATH
TYPE
MIN
MAX
PERMISSION
NVRAM
DESCRIPTION
port-number
ncdAccessSerialdLPTPortNumber
INTEGER
1
3
READ-ONLY
NO
The name of the serial port.
NAME
SNMP NAME
SNMP PATH
TYPE
DEFAULT
PERMISSION
EFFECT
NVRAM
DESCRIPTION
password
ncdAccessSerialdLPTPassword
STRING
nil
WRITE-ONLY
AT_BOOT
NO
Specifies the LAT service password.

NAME
HIDEBOX
SNMP NAME
SNMP PATH
TYPE
PERMISSION
NVRAM
DESCRIPTION
serial-daemons-statistics-table
Serial Daemons=>Serial Daemon Statistics Table
ncdSerialDaemonStatsTable
ncdSerialDaemon 1
TABLE
READ-ONLY
NO
Specifies the table of serial daemon statistics.

NAME
SNMP NAME
SNMP PATH
TYPE
MIN
MAX
PERMISSION
NVRAM
DESCRIPTION
port-number
ncdSerialDaemonPortNumber
ncdSerialDaemonStatsTable 1
INTEGER
1
3
READ-ONLY
NO
NAME
SNMP NAME
SNMP PATH
TYPE
MIN
MAX
connections-accepted
ncdSerialDaemonConnAccepts
INTEGER
4294967295
249
PERMISSION
NVRAM
DESCRIPTION
READ-ONLY
NO
The number of connections made to the serial daemon.
NAME
SNMP NAME
SNMP PATH
TYPE
MIN
MAX
PERMISSION
NVRAM
DESCRIPTION
connections-with-access-control-errors
ncdSerialDaemonConnBadAccesses
INTEGER
4294967295
READ-ONLY
NO
serial daemon due to the remote address not being
present in the serial daemon's access control list.
NAME
SNMP NAME
SNMP PATH
TYPE
MIN
MAX
PERMISSION
NVRAM
DESCRIPTION
connections-with-io-errors
ncdSerialDaemonConnIOErrors
INTEGER
4294967295
READ-ONLY
NO
serial daemon due to the a local I/O error. This
includes the user aborting the connection via local
mechanisms.
NAME
SNMP NAME
SNMP PATH
TYPE
MIN
MAX
PERMISSION
NVRAM
DESCRIPTION
connections-with-normal-completion
ncdSerialDaemonConnEofCloses
INTEGER
4294967295
READ-ONLY
NO
remote host. This is the normal mode of ending a
connection to the serial daemon.

NAME
HIDEBOX
SNMP NAME
SNMP PATH
TYPE
PERMISSION
250
serial-daemons-table
Serial=>Serial Daemons Table
ncdSerialSDTable
ncdSerial 3
TABLE
READ-WRITE
EFFECT
NVRAM
DESCRIPTION
IMMEDIATE
NO
Specifies the table of serial daemon parameters.

NAME
SNMP NAME
SNMP PATH
TYPE
VIEW
MIN
MAX
PERMISSION
NVRAM
DESCRIPTION
serial-daemon-table-index
ncdSerialSDTableIndex
ncdSerialSDTable 1
INTEGER
SNMP ONLY
4294967295
READ-ONLY
NO
The index into the serial daemons interface table
NAME
SNMP NAME
SNMP PATH
TYPE
MIN
MAX
PERMISSION
NVRAM
DESCRIPTION
port-number
ncdSerialSDTablePortNumber
ncdSerialSDTable 2
INTEGER
1
3
READ-ONLY
NO
NAME
SNMP NAME
SNMP PATH
TYPE
DEFAULT
PERMISSION
EFFECT
NVRAM
DESCRIPTION
use-serial-protocol
ncdSerialSDTableUseSerialProt
ncdSerialSDTable 3
BOOL
false
READ-WRITE
IMMEDIATE
NO
Specifies that the new serial daemon control protocol
should be used. Note that this could cause some data
loss if enabled with old host software.
NAME
SNMP NAME
SNMP PATH
TYPE
MIN
DEFAULT
MAX
PERMISSION
EFFECT
NVRAM
DESCRIPTION
tcp-port
ncdSerialSDTableTCPPort
ncdSerialSDTable 4
INTEGER
1
87
65535
READ-WRITE
AT_BOOT
NO
251
Specifies the TCP port on which the terminal

listens for raw TCP connections to the serial
daemon.
NAME
SNMP NAME
SNMP PATH
TYPE
DEFAULT
PERMISSION
EFFECT
NVRAM
DESCRIPTION
ncdnet-object-name
ncdSerialSDTableUseNCDnetObjName
ncdSerialSDTable 5
STRING
SERIALD
READ-WRITE
AT_BOOT
NO
Specifies the NCDnet object on which the terminal
listens for NCDnet connections to the serial
daemon.
NAME
SNMP NAME
SNMP PATH
TYPE
DEFAULT
PERMISSION
EFFECT
NVRAM
DESCRIPTION
enable-lat-service
ncdSerialSDTableEnableLAT
ncdSerialSDTable 6
BOOL
false
READ-WRITE
AT_BOOT
NO
Specifies that the unit is to accept incoming
LAT solicit messages for a service which
allows access to the serial daemon. This is used
to support VMS print services to the unit.
NAME
SNMP NAME
SNMP PATH
TYPE
DEFAULT
PERMISSION
EFFECT
NVRAM
DESCRIPTION
lat-service-name
ncdSerialSDTableLATServName
ncdSerialSDTable 7
STRING
nil
READ-WRITE
AT_BOOT
NO
Specifies the name of the serial daemon LAT service.
NAME
SNMP NAME
SNMP PATH
TYPE
MIN
DEFAULT
MAX
PERMISSION
EFFECT
NVRAM
DESCRIPTION
lat-service-rating
ncdSerialSDTableLATServRating
ncdSerialSDTable 8
INTEGER
5
255
READ-WRITE
AT_BOOT
NO
Specifies the rating of the serial daemon LAT service.
252

NAME
HIDEBOX
SNMP NAME
SNMP PATH
TYPE
PERMISSION
NVRAM
DESCRIPTION
serial-interface-statistics-table
Serial=>Interface Statistics Table
ncdSerialTable
ncdSerial 1
TABLE
READ-ONLY
NO
The table of serial interfaces.

NAME
SNMP NAME
SNMP PATH
TYPE
MIN
MAX
PERMISSION
NVRAM
DESCRIPTION
port-number
ncdSerialInPortNumber
ncdSerialTable 5
INTEGER
1
3
READ-ONLY
NO
NAME
SNMP NAME
SNMP PATH
TYPE
MIN
MAX
PERMISSION
NVRAM
DESCRIPTION
reception-overruns
ncdSerialInOverruns
ncdSerialTable 1
INTEGER
4294967295
READ-ONLY
NO
The number of times an incoming octet overwrote a
previously received octet in the UART's buffer.
NAME
SNMP NAME
SNMP PATH
TYPE
MIN
MAX
PERMISSION
NVRAM
DESCRIPTION
reception-frame-errors
ncdSerialInFrameErrors
ncdSerialTable 2
INTEGER
4294967295
READ-ONLY
NO
The number of times an incoming octet had bad bit
alignment.
NAME
SNMP NAME
reception-parity-errors
ncdSerialInParityErrors
253
SNMP PATH
TYPE
MIN
MAX
PERMISSION
NVRAM
DESCRIPTION
ncdSerialTable 3
INTEGER
4294967295
READ-ONLY
NO
The number of times the parity bit of an incoming
octet was incorrect.
NAME
SNMP NAME
SNMP PATH
TYPE
MIN
MAX
PERMISSION
NVRAM
DESCRIPTION
reception-break-errors
ncdSerialInBreakErrors
ncdSerialTable 4
INTEGER
4294967295
READ-ONLY
NO
The number of times a stop bit was not received
at the expected time after a start bit, and the
intervening bits were all zero.
NAME
SNMP NAME
SNMP PATH
TYPE
MIN
MAX
PERMISSION
NVRAM
DESCRIPTION
total-characters-transmitted
ncdSerialInTotCharXmit
ncdSerialTable 6
INTEGER
4294967295
READ-ONLY
NO
Total characters transmitted
NAME
SNMP NAME
SNMP PATH
TYPE
MIN
MAX
PERMISSION
NVRAM
DESCRIPTION
total-transmit-interrupts
ncdSerialInTotXmitInt
ncdSerialTable 7
INTEGER
4294967295
READ-ONLY
NO
Total transmission interrupts
NAME
SNMP NAME
SNMP PATH
TYPE
MIN
MAX
PERMISSION
NVRAM
DESCRIPTION
254
total-characters-received
ncdSerialInTotCharRcv
ncdSerialTable 8
INTEGER
4294967295
READ-ONLY
NO
Total of characters received
NAME
SNMP NAME
SNMP PATH
TYPE
MIN
MAX
PERMISSION
NVRAM
DESCRIPTION
total-receive-interrupts
ncdSerialInTotRcvInt
ncdSerialTable 9
INTEGER
4294967295
READ-ONLY
NO
Total of reception interrupts
NAME
SNMP NAME
SNMP PATH
TYPE
MIN
MAX
PERMISSION
NVRAM
DESCRIPTION
total-receive-errors
ncdSerialInTotRcvErr
ncdSerialTable 1
INTEGER
4294967295
READ-ONLY
NO
Total of reception errors

NAME
HIDEBOX
SNMP NAME
SNMP PATH
TYPE
PERMISSION
EFFECT
NVRAM
DESCRIPTION
serial-interfaces-table
Serial=>Serial Interfaces Table
ncdSerialIfTable
ncdSerial 2
TABLE
READ-WRITE
IMMEDIATE
YES
Specifies the table of serial port parameters.

NAME
SNMP NAME
SNMP PATH
TYPE
VIEW
MIN
MAX
PERMISSION
NVRAM
DESCRIPTION
serial-interface-table-index
ncdSerialIfTableIndex
ncdSerialIfTable 1
INTEGER
SNMP ONLY
4294967295
READ-ONLY
NO
The index into the serial interface table
255
NAME
SNMP NAME
SNMP PATH
TYPE
MIN
MAX
PERMISSION
NVRAM
DESCRIPTION
port-number
ncdSerialIfTablePortNumber
ncdSerialIfTable 2
INTEGER
1
3
READ-ONLY
NO
NAME
SNMP NAME
SNMP PATH
TYPE
CHOICES
DEFAULT
PERMISSION
EFFECT
NVRAM
DESCRIPTION
is booted.
NAME
SNMP NAME
SNMP PATH
TYPE
CHOICES
DEFAULT
PERMISSION
EFFECT
NVRAM
DESCRIPTION
mode
ncdSerialIfTableMode
ncdSerialIfTable 3
CHOICE
{ terminal printer serial-daemon slip console input-device xremote ppp }
terminal
READ-WRITE
AT_BOOT
YES
Specifies what the serial port should be used for, but takes
effect the next time the unit
The choices
'Printer' and 'Serial Daemon' are equivalent.
current-mode
ncdSerialIfTableCurMode
ncdSerialIfTable 9
CHOICE
{ terminal printer serial-daemon slip console input-device xremote ppp }
terminal
READ-WRITE
IMMEDIATE
NO
Specifies what the serial port should be used for. Any
change takes effect immediately, but the value of this
parameter is ignored at boot time in favor of the 'mode'
value.
NAME
SNMP NAME
SNMP PATH
TYPE
CHOICES
DEFAULT
PERMISSION
EFFECT
NVRAM
DESCRIPTION
baud-rate
ncdSerialIfTableBaudRate
ncdSerialIfTable 4
CHOICE
{ 5 75 11 134.5 15 2 3 6 15 12 18 2
24 48 72 96 144 192 384 576 768
1152 }
96
READ-WRITE
IMMEDIATE
YES
Specifies the baud rate of the serial port.
256
NAME
SNMP NAME
SNMP PATH
TYPE
CHOICES
DEFAULT
PERMISSION
EFFECT
NVRAM
DESCRIPTION
data-bits
ncdSerialIfTableDataBits
ncdSerialIfTable 5
CHOICE
{ 8 7 }
8
READ-WRITE
IMMEDIATE
YES
Specifies the number of data bits per
character of the serial port.
NAME
SNMP NAME
SNMP PATH
TYPE
CHOICES
DEFAULT
PERMISSION
EFFECT
NVRAM
DESCRIPTION
stop-bits
ncdSerialIfTableStopBits
ncdSerialIfTable 6
CHOICE
{ 1 2 }
1
READ-WRITE
IMMEDIATE
YES
Specifies the number of stop bits per
character of the serial port.
NAME
SNMP NAME
SNMP PATH
TYPE
CHOICES
DEFAULT
PERMISSION
EFFECT
NVRAM
DESCRIPTION
parity
ncdSerialIfTableParity
ncdSerialIfTable 7
CHOICE
{ none odd even space mark }
none
READ-WRITE
IMMEDIATE
YES
Specifies the form of parity generated by
and expected by the serial port.
NAME
SNMP NAME
SNMP PATH
TYPE
CHOICES
DEFAULT
PERMISSION
EFFECT
NVRAM
DESCRIPTION
handshake
ncdSerialIfTableHandshake
ncdSerialIfTable 8
CHOICE
{ none xon/xoff dtr/dsr rts/cts }
none
READ-WRITE
IMMEDIATE
YES
Specifies the type of flow control
of the serial port.
257
NAME
SNMP NAME
SNMP PATH
TYPE
CHOICES
DEFAULT
PERMISSION
EFFECT
NVRAM
DESCRIPTION
hangup
ncdSerialIfTableActionOnDiscon
ncdSerialIfTable 1
CHOICE
{ none drop-dtr send-break }
none
READ-WRITE
IMMEDIATE
NO
Specifies what a local NCDterm client will do
when closing the serial port. Also specifies
what the serial daemon will do to
signal the end of a network connection.
258
Appendix D. Special Notices

This publication is intended to help any user who needs to understand how to use
the printing capabilities of the IBM Network Station. The information in this
publication is not intended as the specification of any programming interfaces that
are provided by the IBM Network Station Manager. See the PUBLICATIONS
section of the IBM Programming Announcement for the IBM Network Station
Manager for more information about what publications are considered to be product
documentation.
References in this publication to IBM products, programs or services do not imply
that IBM intends to make these available in all countries in which IBM operates.
Any reference to an IBM product, program, or service is not intended to state or
imply that only IBM's product, program, or service may be used. Any functionally
equivalent program that does not infringe any of IBM's intellectual property rights
may be used instead of the IBM product, program or service.
Information in this book was developed in conjunction with use of the equipment
specified, and is limited in application to those specific hardware and software
products and levels.
IBM may have patents or pending patent applications covering subject matter in
this document. The furnishing of this document does not give you any license to
these patents. You can send license inquiries, in writing, to the IBM Director of
Licensing, IBM Corporation, 500 Columbus Avenue, Thornwood, NY 10594 USA.
Licensees of this program who wish to have information about it for the purpose of
enabling: (i) the exchange of information between independently created programs
and other programs (including this one) and (ii) the mutual use of the information
which has been exchanged, should contact IBM Corporation, Dept. 600A, Mail Drop
1329, Somers, NY 10589 USA.
Such information may be available, subject to appropriate terms and conditions,
including in some cases, payment of a fee.
The information contained in this document has not been submitted to any formal
IBM test and is distributed AS IS. The use of this information or the implementation
of any of these techniques is a customer responsibility and depends on the
customer's ability to evaluate and integrate them into the customer's operational
environment. While each item may have been reviewed by IBM for accuracy in a
specific situation, there is no guarantee that the same or similar results will be
obtained elsewhere. Customers attempting to adapt these techniques to their own
environments do so at their own risk.
Any pointers in this publication to external Web sites are provided for convenience
only and do not in any manner serve as an endorsement of these Web sites.
The following document contains examples of data and reports used in daily
business operations. To illustrate them as completely as possible, the examples
contain the names of individuals, companies, brands, and products. All of these
names are fictitious and any similarity to the names and addresses used by an
actual business enterprise is entirely coincidental.
259
The following terms are trademarks of the International Business Machines

Corporation in the United States and/or other countries:
Advanced Function Presentation
AIX
AT
CICS
IBM
InfoColor
Intelligent Printer Data Stream
IPDS
NetSpool
OS/2
OS/400
S/390
VTAM
AFP
AS/400
BookMaster
eNetwork
IMS
InfoPrint
IP PrintWay
MVS
OfficeVision/400
OS/390
RS/6000
VM/ESA
400
The following terms are trademarks of other companies:

C-bus is a trademark of Corollary, Inc.
Java and HotJava are trademarks of Sun Microsystems, Incorporated.
Microsoft, Windows, Windows NT, and the Windows 95 logo are trademarks
or registered trademarks of Microsoft Corporation.
PC Direct is a trademark of Ziff Communications Company and is used
by IBM Corporation under license.
Pentium, MMX, ProShare, LANDesk, and ActionMedia are trademarks or
registered trademarks of Intel Corporation in the U.S. and other
countries.
UNIX is a registered trademark in the United States and other
countries licensed exclusively through X/Open Company Limited.
Other company, product, and service names may be trademarks or
service marks of others.
260
Appendix E. Related Publications

The publications listed in this section are considered particularly suitable for a more
detailed discussion of the topics covered in this redbook.
E.1 International Technical Support Organization Publications

For information on ordering these ITSO publications see How to Get ITSO
Redbooks on page 263.
IBM Network Station Guide for Windows NT, SG24-2127-01
S/390 - IBM Network Station - Getting Started, SG24-4954-01
AS/400 - IBM Network Station - Getting Started, SG24-2153
RS/6000 - IBM Network Station - A Companion Guide, SG24-2016
AS/400 Printing V, SG24-2160
IBM TCP/IP V3 Release 2 for MVS Implementation Guide, SG24-3687-03
TCP/IP Implementation in an OS/2 Warp Environment, SG24-4730
The IBM eNetwork Communications Suite, SG24-2111
E.2 Redbooks on CD-ROMs

Redbooks are also available on CD-ROMs. Order a subscription and receive
updates 2-4 times a year at significant savings.
CD-ROM Title
System/390 Redbooks Collection
Networking and Systems Management Redbooks Collection
Transaction Processing and Data Management Redbook
Lotus Redbooks Collection
Tivoli Redbooks Collection
AS/400 Redbooks Collection
RS/6000 Redbooks Collection (HTML, BkMgr)
RS/6000 Redbooks Collection (PostScript)
RS/6000 Redbooks Collection (PDF Format)
Application Development Redbooks Collection
Subscription
Number
SBOF-7201
SBOF-7370
SBOF-7240
SBOF-6899
SBOF-6898
SBOF-7270
SBOF-7230
SBOF-7205
SBOF-8700
SBOF-7290
Collection Kit
Number
SK2T-2177
SK2T-6022
SK2T-8038
SK2T-8039
SK2T-8044
SK2T-2849
SK2T-8040
SK2T-8041
SK2T-8043
SK2T-8037
E.3 Other Publications

These publications are also relevant as further information sources:
AS/400 Printer Device Programming, SC41-5713
AS/400 System API Reference, SC41-5801
261
262
How to Get ITSO Redbooks

This section explains how both customers and IBM employees can find out about ITSO redbooks, CD-ROMs,
workshops, and residencies. A form for ordering books and CD-ROMs is also provided.
This information was current at the time of publication, but is continually subject to change. The latest information
may be found at http://www.redbooks.ibm.com/.
How IBM Employees Can Get ITSO Redbooks

Employees may request ITSO deliverables (redbooks, BookManager BOOKs, and CD-ROMs) and information about
redbooks, workshops, and residencies in the following ways:
PUBORDER to order hardcopies in United States
GOPHER link to the Internet - type GOPHER.WTSCPOK.ITSO.IBM.COM
Tools disks
To get LIST3820s of redbooks, type one of the following commands:
TOOLS SENDTO EHONE4 TOOLS2 REDPRINT GET SG24xxxx PACKAGE
TOOLS SENDTO CANVM2 TOOLS REDPRINT GET SG24xxxx PACKAGE (Canadian users only)
To get BookManager BOOKs of redbooks, type the following command:
TOOLCAT REDBOOKS
To get lists of redbooks, type the following command:
TOOLS SENDTO USDIST MKTTOOLS MKTTOOLS GET ITSOCAT TXT
To register for information on workshops, residencies, and redbooks, type the following command:
TOOLS SENDTO WTSCPOK TOOLS ZDISK GET ITSOREGI 1998
For a list of product area specialists in the ITSO: type the following command:
TOOLS SENDTO WTSCPOK TOOLS ZDISK GET ORGCARD PACKAGE
Redbooks Web Site on the World Wide Web
http://w3.itso.ibm.com/redbooks/
IBM Direct Publications Catalog on the World Wide Web
http://www.elink.ibmlink.ibm.com/pbl/pbl
IBM employees may obtain LIST3820s of redbooks from this page.
REDBOOKS category on INEWS
Online send orders to: USIB6FPL at IBMMAIL or DKIBMBSH at IBMMAIL
Internet Listserver
With an Internet e-mail address, anyone can subscribe to an IBM Announcement Listserver. To initiate the
service, send an e-mail note to announce@webster.ibmlink.ibm.com with the keyword subscribe in the body of the
note (leave the subject line blank). A category form and detailed instructions will be sent to you.
Redpieces
For information so current it is still in the process of being written, look at "Redpieces" on the Redbooks Web Site
(http://www.redbooks.ibm.com/redpieces.html). Redpieces are redbooks in progress; not all redbooks become
redpieces, and sometimes just a few chapters will be published this way. The intent is to get the information out
much quicker than the formal publishing process allows.
263
How Customers Can Get ITSO Redbooks

Customers may request ITSO deliverables (redbooks, BookManager BOOKs, and CD-ROMs) and information about
redbooks, workshops, and residencies in the following ways:
Online Orders send orders to:
In United States:
In Canada:
Outside North America:
IBMMAIL
usib6fpl at ibmmail
caibmbkz at ibmmail
dkibmbsh at ibmmail
Internet
usib6fpl@ibmmail.com
lmannix@vnet.ibm.com
bookshop@dk.ibm.com
Telephone orders
United States (toll free)
Canada (toll free)
1-800-879-2755
1-800-IBM-4YOU
Outside North America

(+45) 4810-1320 - Danish
(+45) 4810-1420 - Dutch
(+45) 4810-1540 - English
(+45) 4810-1670 - Finnish
(+45) 4810-1220 - French
(long distance charges apply)

(+45) 4810-1020 - German
(+45) 4810-1620 - Italian
(+45) 4810-1270 - Norwegian
(+45) 4810-1120 - Spanish
(+45) 4810-1170 - Swedish
Mail Orders send orders to:

IBM Publications
Publications Customer Support
P.O. Box 29570
Raleigh, NC 27626-0570
USA
IBM Publications
144-4th Avenue, S.W.
Calgary, Alberta T2P 3N5
Canada
IBM Direct Services

Sortemosevej 21
DK-3450 Allerd
Denmark
Fax send orders to:

United States (toll free)
Canada
Outside North America
1-800-445-9269
1-403-267-4455
(+45) 48 14 2207 (long distance charge)
1-800-IBM-4FAX (United States) or (+1)001-408-256-5422 (Outside USA) ask for:

Index # 4421 Abstracts of new redbooks
Index # 4422 IBM redbooks
Index # 4420 Redbooks for last six months
Direct Services - send note to softwareshop@vnet.ibm.com
On the World Wide Web
Redbooks Web Site
IBM Direct Publications Catalog
http://www.redbooks.ibm.com/
http://www.elink.ibmlink.ibm.com/pbl/pbl
Internet Listserver
With an Internet e-mail address, anyone can subscribe to an IBM Announcement Listserver. To initiate the
service, send an e-mail note to announce@webster.ibmlink.ibm.com with the keyword subscribe in the body of the
note (leave the subject line blank).
Redpieces
For information so current it is still in the process of being written, look at "Redpieces" on the Redbooks Web Site
(http://www.redbooks.ibm.com/redpieces.html). Redpieces are redbooks in progress; not all redbooks become
redpieces, and sometimes just a few chapters will be published this way. The intent is to get the information out
much quicker than the formal publishing process allows.
264
IBM Redbook Order Form

Please send me the following:
Title
First name
Order Number
Quantity
Last name
Company
Address
City
Postal code
Country
Telephone number
Telefax number
VAT number
Card issued to
Signature
Invoice to customer number

Credit card number
Credit card expiration date
We accept American Express, Diners, Eurocard, Master Card, and Visa. Payment by credit card not
available in all countries. Signature mandatory for credit card payment.
How to Get ITSO Redbooks
265
266
Index
Numerics
3270
3270
3270
3270
5250
5250
emulator
emulator
emulator
emulator
emulator
emulator
28
- LU1/LU3 29
- print screen 29
- printing from 122
28
- printing from 122
A
access control 36, 52, 188
access control - LPD daemon 190
access control - SERIALD 188
Add Printer Wizard 72
adding a printer 53
AIX 155
NT 139
OS/400 146
Advanced Function Presentation Data Stream 14
AFP 14
AFPDS 14
AIX - printing from 59
AIX - printing to 151
Alt+Shift+Home - console key sequence 182
APIs 221
application default printer 35
AS/400 - printing from 98
AS/400 message log 180
ASCII 13
ASCII Options 227
assign printer to port - NT 213
Auto CR after LF 115
client/LPT1 90
command mode - parallel daemon 191
components - network station printing 82
configd.doc file 237
configuration parameters 182, 237
configuration requirements - printing 83
configuring
LPD 51
LPD passthrough - NT 202
LPR 50
network station 91
parallel port 191
printing 47
serial port 56, 192
the printer List 53
user 87
WinStation 84
connection table 193
console 182
console - Network Station 181
control commands
AIX 213
OS/2 212
Windows NT 201
control file 17
name 194
options 194
sample 197
converting data stream 150
Create Output Queue 99
creating - printer 89
CRLF 115
CRTDEVPRT 104
CRTOUTQ 99
B
banner page 195
baud rate - serial port 193
bibliography 261
boot monitor 182
Browser 126
buffer size - LPD and LPRD 184
bypass print buffer 42, 184
C
cacher size - LPD and LPRD 184
carriage return, line feed 115
CFGTCP 145
class 194
client devices 87, 89
client/COM1 90
D
data bits - serial port 193
data stream 12, 29
data stream conversion 150
data type - RAW, TEXT 202
DBCS 225
conversion 226
converter 29
font encoding 227
type 226
default control command flag 202
deleting printers 56
Device Description (AS/400) 98
Document Properties - NT 212
drivers 14
267
dummy device description 104

Dummy Device Description (AS/400)
98
E
EBCDIC 14
emulator - printing from 122
emulator print dialog 33
enable access control parameter 184
eSuite 136
Event Viewer - Windows NT 181
F
file - printing to 218
Form Feed 124
formatted print request
196
G
greyscale
128
H
handshake - serial port 193
hex mode - printer 179
hexadecimal output 179
Host Print Transform 101, 177
I
IBM Network Station Browser 129
image configuration 150
image conversion 150
image print transform 177
inherit user configuration 87
Intelligent Printer Data Stream 14
IP address of Network Station 182
IPDS 14
J
Java application - Print dialog
Java applications 130
JetDirect 65
job name 195
joblog - AS/400 180
33
L
Line Printer Daemon 16
Line Printer Requester 16
literal print request 196
LOAD FORMS 218
LOAD LETTER 218
local application - printing from
268
local IP address 193

local port 193
local spooling - LAN printer 216
localhost 38
logging messages - Network Station 181
LPD 16, 28, 36
cache size 184
daemon configuration parameters 183
key 205
on OS/2 159
on OS/400 144
passthrough - forcing - NT 202
passthrough configuration - NT 202
queue names 41
server on AIX 151
stream large jobs parameter 184
LPD access control
AIX 152
NT 139
OS/2 159
OS/400 146
LPDSVC key 205
LPQ command 198
LPR 16, 36
LPR command - VM 113
LPR command - Windows NT 201
Lpr servers table 185
LPR/LPD control commands 194
LPR/LPD control file 194
LPR/LPD support 38
LPRD cache size 184
LPRD daemon 28
LPRD daemon configuration parameters 183
LPT1, LPT2 213
M
MAC address of Network Station 182
Manage Print Server - AIX 151
Manufacturer Type and Model 102
maximum LPD buffer size 51
maximum LPR buffer size 50
message log
AS/400 180
Network Station 181
Windows NT 181
messages - accessing remotely 181
121
NC Navigator 28, 126

NC Navigator - print dialog 33
Network Station Browser 129
Network Station Manager 47
network station print components
82
NSK6501 message
NSK8001 message
NSM 47
114
114
O
OS/2 - printing to 159
OS/400 - printing to 144
Output Queue (AS/400) 98
P
paper sizes 218
paralled 43
parallel daemons table 91, 191
parallel port configuration 191
parallel protocol 92, 191
parallel-daemons-table 192
PARALLEL1 41
PARALLELD 43
passthrough 202
passthru mode - parallel port 191
Pause - console key sequence 182
PCL 13
Personal Printer Data Stream 13
ping utility 180
port
2501 147
515 16
5964 44, 82, 191, 192
5998 181
6461 44, 192
6464 44, 192
87 44, 192
9100 66
serial - configuration 192
PostScript 14
PPDS 13
print access control list 184
Print Client (LPR) 50
print configuration section 183
print dialog 28, 32
print dialog - emulator 33
print dialog - NC Navigator 33
Print Manager 91
print screen 122
Print Server Status - AIX 151
Print Spooling - AIX 151
print-access-control-enabled 190
print-access-control-list 190
print-lpr-servers parameter 185
printer
access control 36, 188
default 35
definition 89
drivers 14
printer (continued)
list 35
pooling example - NT 214
queues - NT 213
selection 32
table 35, 185
Printer Control Language 13
Printer Selector 28, 34
Printer Selector GUI 32
printing from
3270 122
5250 122
AIX 59
AS/400 98
browser 126
emulator 122
eSuite 136
host 57
IBM Network Station 137
Java applications 130
local application 121
NC Navigator 126
Network Station Browser 129
OS/2 119
OS/390 117
RS/6000 59
VM 113
VTxxx 233
WinCenter 80
Windows NT 72
printing to
AIX 151
file 218
IBM Network Station 57
OS/2 159
OS/400 144
S/390 159
Windows NT 138
Q
queue names
queues 9
41
R
RAW data type 202
Registry Editor - Windows NT 203
release 182
Release 1 23
Release 2 25
Release 3 28
remote IP address 193
Remote Output Queue (AS/400) 98
remote port 193
Index
269
Remote Print Queue 59

remote printer queue 41
removing local printers 187
removing printers 56
RFC 1179 16
RS/6000 - printing from 59
RSCS EXIT 117
RSCS link definition 117
RSCS spooling 116
transformation module - DBCS
S/390 - printing to 159

sample control file 197
sample SHD spooler file - Windows NT 200
screen print 122
SCS 14
security 36
security - AIX 152
security - NT 139
serial daemons table 92, 192
serial interfaces table 92, 192
serial port - configuration 192
serial protocol 92, 192
serial-access-control-enabled 189
serial-access-control-list 189
serial-daemons-table 193
serial-interfaces-table 193
SERIAL1 41
SERIALD 43, 107
SERIALD daemon 28
Services window - NT 138
setup menu - console 182
SimulatePassThrough 204
smit 151
smitty 151
SNA Character Stream 14
software level 182
spool 9
start TCP/IP - OS/400 145
start TCP/IP server - OS/400 145
statistics - number of connections 193
stop bits - serial port 193
streaming 18, 36
streaming on AS/400 LPR 100
STRTCP 145
STRTCPSVR 145
system default printer 35
T
TCP/IP Print Server - NT
TELNET 181
test page 78
TEXT data type 202
270
138
U
use parallel protocol 92, 191
use serial protocol 92, 192
user configuration 87
user identification 195
user properties 88
version 182
VM - printing from 113
VTxxx 233
VTxxx emulator 29
W
waiting message 219
waiting message - printer 124
Web Browser 47
WinCenter - printing from 80
Windows NT
printing from 72
printing to 138
test page 78
WinStation configuration 84
WinStation printer 84
226
ITSO Redbook Evaluation

SG24-5212-00
Your feedback is very important to help us maintain the quality of ITSO redbooks. Please complete this
questionnaire and return it using one of the following methods:
Use the online evaluation form found at http://www.redbooks.ibm.com
Fax this form to: USA International Access Code + 1 914 432 8264
Send your comments in an Internet note to redbook@us.ibm.com
Which of the following best describes you?
Customer
Business Partner
Independent Software Vendor
None of the above
IBM employee
Please rate your overall satisfaction with this book using the scale:
(1 = very good, 2 = good, 3 = average, 4 = poor, 5 = very poor)
Overall Satisfaction
____________
Please answer the following questions:

Was this redbook published in time for your needs?
Yes____ No____
If no, please explain:

_____________________________________________________________________________________________________
_____________________________________________________________________________________________________
_____________________________________________________________________________________________________
_____________________________________________________________________________________________________
What other redbooks would you like to see published?

_____________________________________________________________________________________________________
_____________________________________________________________________________________________________
_____________________________________________________________________________________________________
Comments/Suggestions:
( THANK YOU FOR YOUR FEEDBACK! )
_____________________________________________________________________________________________________
_____________________________________________________________________________________________________
_____________________________________________________________________________________________________
_____________________________________________________________________________________________________
_____________________________________________________________________________________________________
271
SG24-5212-00
SG24-5212-00
Printed in the U.S.A.

SG Printing

Загружено:

Сведения о документе

Оригинальное название

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

SG Printing

Загружено:

Авторское право:

Доступные форматы

IBM Network Station Printing Guide

Claude Bechard, Michael Miller

International Technical Support Organization

International Technical Support Organization

First Edition (May 1998)

Comments may be addressed to:

Chapter 3. How Printing Works on the IBM Network Station

Chapter 4. Configuration Using the IBM Network Station Manager

4.4 Parallel and Serial Port Configuration

Chapter 5. Host Applications Printing to IBM Network Station Local

IBM Network Station Printing Guide

Chapter 7. Printing from an IBM Network Station to Remote Print

7.3.4 Enabling Print Access on AIX . . . . . . . . . . . . . . . . .

Chapter 9. Problem Determination Tools, Tips and Techniques . . .

9.12.1 No Printers Configured . . . . . .

Chapter 10. Application Programming Interfaces (APIs)

Appendix A. Special Values of Image Configurations (AS/400)

Appendix B. Printing from the VTxxx Emulator to a Remote IBM Network

Appendix E. Related Publications

ITSO Redbook Evaluation

IBM Network Station Printing Guide

Release 3 Printing Capabilities Overview . . . . . . . . . . . . . . . . . .

Add a Print Queue . . . . . . . . . . . . . . . . . . . . . .

IBM Network Station Printing Guide

The Start Remote Writer Command . . . . . . . . . . . . . . . . . . . . .

List All Print Queues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

IBM Network Station Printing Guide

212. The Windows NT 3.51 Warning Message . . . . . . . . . . . . . . . . .

IBM Network Station Printing Guide

Copyright IBM Corp. 1998

Local Applications in Release 1 . . . . . . . . . . . . . . . . . . . . . . . .

IBM Network Station Printing Guide

The Team That Wrote This Redbook

Marvin Heffler is a Development Programmer Manager in the Network Station

Send us a note at the following address:

IBM Network Station Printing Guide

1.2 Release 3 Print Support

Copyright IBM Corp. 1998

Figure 1. Release 3 Printing Capabilities Overview

The printing capabilities of the IBM Network Station are as follows:

IBM Network Station Printing Guide

Figure 2. A Sample Print Dialog

Figure 3. The Printer Selector

1.3 Particularities of the IBM Network Station

IBM Network Station Printing Guide

1.4 Configuration Using the IBM Network Station Manager

Figure 4. The IBM Network Station Manager Printer Settings Configuration

Figure 5. Printer List Parameters - System Defaults

1.5 What This Document Contains

IBM Network Station Printing Guide

Here we take a look at the preparations required on remote hosts to receive

IBM Network Station Printing Guide

Chapter 2. A Few Concepts

2.1 What Are Printer Queues and Spooling?

Copyright IBM Corp. 1998

Figure 6. Spooling Output to Tape

IBM Network Station Printing Guide

Figure 7. Print Flow on a Typical Large Computer System

Chapter 2. A Few Concepts

Figure 8. One Printer Serving Multiple Queues

Figure 9. Printer Pooling

2.2 What Are Printer Data Streams?

IBM Network Station Printing Guide