Configuring Pull Print Actual Destinations

To set an AIX, CUPS, Passthrough, or PSF Other actual destination as a Pull Print actual destination, you must set the pull-print-printer attribute to true. You cannot set the pull-print-printer attribute to true unless:

• The logical-destinations-assigned attribute is set to the logical destination through which submissions to this actual destination are made.
• The printer-tcpip-internet-address attribute is set to the address of one of the supported printers. This should be the same printer identified in the printer-command or the device-name attributes.
  Note: Setting the printer-tcpip-internet-address attribute turns on the SNMP monitoring for the actual destination. If you do not want to use the SNMP function, then set the use-snmp attribute to false.
• The force-destination-setup attribute is set to false.

When an actual destination is identified as a Pull Print printer, jobs that have the authenticated-login attribute set are held for pull-print reason in the queue until they are requested by the authenticated user at the printer.

Since the owner has to be at the printer to request the job print, you may choose to turn off banner pages for your Pull Print actual destinations. To turn off the banner pages, use the auxiliary-sheets-selection-supported, printer-start-sheet, printer-separator-sheet, and printer-end-sheet actual destination attributes.

Configuration considerations for Pull Print actual destinations

Jobs submitted with the LDAP-enabled clients are authenticated jobs. Authenticated jobs that can be scheduled only to an actual destination with the pull-print-printer attribute set to true require that the jobs be pulled from the printer. These jobs are held for Pull Print on the queue and you must pull them from the printer console. If the pull-print-printer attribute is set to false, the authenticated jobs sent to that actual destination are printed without being pulled from the printer.

Your logical destinations to queue to actual destinations configuration is very important when using Pull Print. For example, you can pool your Pull Print printer actual destinations to allow users to pull their jobs to any of those printers. It is important to understand that authenticated jobs can be printed on a non-Pull Print printer actual destination, including a non-Pull Print printer actual destination in a pool with Pull Print printer actual destinations could empty your queue of Pull Print jobs. If you want to require that jobs be pulled from a printer, you must make sure that your configuration does not allow for authenticated jobs to be scheduled to a non-Pull Print printer actual destination.

Since it is also possible to create more than one actual destination for sending jobs to the same printer, you can create separate logical destination to queue to actual destination configurations allowing the jobs to be sent to the printer as normal with one actual destination, while requiring them to be pulled from the printer with the other actual destination. By controlling which users are allowed to submit jobs to the different logical destinations, you can control which users have to pull their jobs from the printer and which users do not.