Archiving print jobs with RPM

RPM Provides

It is surprisingly common for users to archive their print jobs to disk. RPM makes this exercise both flexible and productive.

All your information is available

RPM can use all the data associated with your print job to make a unique and more importantly, a meaningful file name. 

To create a file name, RPM can use one or ore of these properties of your print job:

  • job name, with or without extension
  • title
  • unique job id
  • queue name
  • queue sequence number
  • originating host
  • user name
  • class
  • banner
  • email address
  • job received and processed times

Many fields can contain a full path. We can factor out the path part leaving the file name. We can also strip the extension, leaving only the filename part. This may be handy for instance when you want to convert filename.scs to filename.pdf, and prefer not to have filename.scs.pdf.

Local versus shared

Saving to a local folder is no problem. If you provide Windows user credentials in the setup, RPM can save to a shared folder. We have successfully written to folders hosted on Linux systems, and on iSeries systems as well.

Job retention

RPM will also "keep" your print jobs for a specified period, after they are distributed. We provide this on a per-queue basis; one queue might remove jobs when finished, which is the default, another might keep the last 100 jobs, still another might keep jobs for 2.5 days or any priod you choose, down to a few minutes.

So long as the job is retained in RPM it can be reprinted from the GUI.

Further reading