Basic print file handling example

When a job is submitted to InfoPrint Manager:

  1. The pdserver command processor copies the print file to its directory: 
     /var/pd/Serv2/pdprxxxxx
  2. The job is submitted to the logical destination and a job object is stored in the logical destination's queue until scheduled for printing. No file transfer occurs; the job only contains reference information to the location of the print files.The Serv1 and Serv2 pdpr file flow illustration.
  3. The job is scheduled and sent to an actual destination. The actual destination might be in a pdserver on the same machine or a different machine than the command processor pdserver. If the pdserver containing the actual destination is on the same machine as the command processor pdserver, the file is accessed directly by the actual destination.QueueA schedules job to AD2 in Serv2 and the file is local to AD2, so reads it directly illustration.
  4. If the pdserver containing the actual destination is on a different machine than the command processor pdserver, the actual destination's pdserver communicates with the command processor pdserver to pull the file over to its machine.QueueA schedules job to AD1 in server on different machine than Serv2 and the file is not local to AD1, so Serv2 is contacted and asked to send the file to AD1 illustration.

    Files are "pulled" from one server to another using a socket. The command processor pdserver must be running for a file to be "pulled". When a file is "pulled", the actual destination stores it in its pdb directory. The "pulled" file is removed from the actual destination's server's pdb directory when the actual destination finishes processing the job, that is, it is completed or canceled.

Parent topic: Basic print file handling for all DSSs