SCO Gateway for NetWare print system

Although SCO Gateway for NetWare print jobs are submitted in the same way as any other UNIX system print jobs, the SCO Gateway for NetWare






print system processes the print job differently than the UNIX system print system does. Once submitted, the NetWare print job is:

1. First queued on the UNIX system print queue (the local queue).

2. The system attempts to transfer the print job from the local UNIX system queue to the remote NetWare print queue (the remote queue). This is influenced by your NetWare login status:

   • If you are logged into the NetWare file server attached to the printer, the print job is transferred to the NetWare print queue (the remote queue)

   • If you are not logged into the NetWare file server attached to the printer and autologin is disabled (the default condition for all users), the print job is abandoned and an error message is electronically mailed to you

   • If you are not logged into the NetWare file server attached to the printer and autologin is enabled, the autologin feature produces a graphical window at your console, requesting a login to the NetWare server. After the login and password are verified, the print job is transferred to the NetWare print queue (the remote queue).

See also:

• ``Autologin''

• ``Viewing SCO Gateway for NetWare printers''

While a SCO Gateway for NetWare print job is locally queued, all UNIX system print job management features are available.

Once a SCO Gateway for NetWare print job is remotely queued on NetWare, you must use pconsole on a DOS client to:

• move a remotely queued print job between queues

• change the priority of a remotely queued print job

• put a remotely queued print job on hold

• move a remotely queued print job to the head of the queue