When you print from iSeries™ to a remote NetWare printer, you use the standard NetWare print support and an iSeries remote output queue and remote writer.
As the following example shows, NetWare uses a print queue, a print server, and a printer to allow workstations to print to a network printer. The print queue is the object that temporarily holds the print job file until the job prints. The print server provides the service of sending the print job to the printer. The print server monitors the print queue and the printer.
In this environment, an iSeries user ( 1 ) requests print services from the NetWare server. The print job file goes to the iSeries remote output queue ( 2 ). The Remote Writer for that output queue then sends data to the NetWare print queue ( 3 ). The NetWare server acts as the print server and monitors the print queue as well as the printer. When the printer can process the job, the server sends the print job to the assigned printer ( 4 ).
As each user's spool job is processed on the output queue, iSeries authenticates a connection for the user to the appropriate server. Each user must either have a NetWare authentication entry (described in Manage NetWare server connections and authentication) or use the STRNTWCNN command to start a NetWare connection manually.
Ideally, users have an authentication entry that authorizes them to the specified NetWare print queue. The easiest way to set this up for your users is with user enrollment. You can automatically set up your iSeries users in the NDS tree where the print queue object is.
If users do not have an authentication entry, they must specify AUTJOB(*ANY) on the STRNTWCNN command when they start a connection to NetWare. The writer job uses that connection to print the file on NetWare.