Print Job Manager PJM in Command Line Mode
A29247-X3-X-6-7670 285
Usage of Ticket, Print and File parameter groups:
These parameter groups may be used exclusively or combined (where they supplement
each other). The idea behind is to allow to print either without a Job Ticket or with a Job
Ticket/Oct and replacing parameters in the ticket.
– No local Ticket
for simple print jobs. Normally only the "file parameter" would be used here, maybe with set-
ting a job name and printer by "print parameters".
Example: -jn simple -nc 2 -f test.afp
– Local Ticket only
for fully prepared print jobs. All parameters are defined in the Job Ticket.
– Local Ticket + Print/Files:
for prepared print jobs. A few parameters in the job ticket must be updated.
Example: -t test.tic -f test.afp -prt myprinter
– Local Ticket + Oct
for print jobs which are based on a default ticket and where a lot of parameters must be
updated. All dynamic parameters are contained in the Oct.
– Local Ticket + Oct + Print/Files
should not be used. Either the dynamic parameters are written in an Oct or the Print/Files
group is used for overwriting.
– Reprint request
the special request -r, where a job kept in intermediate storage should be reprinted. The
Job Ticket for the reprint is supposed to be the ticket of the original job.
-cancel <job-id>… cancel job(s) listed
Cancels a job / a list of jobs. The jobid is the 8-digit number displayed when
a job is submitted.
-rdelete <resource-id>… name(s) of Reprint/ Resource
Delete documents in Print File Libraries and Resource files. You have to
add the fully qualified virtual path. $ can be replaced by @, as the use of
the $ character is restricted in some operating systems.
If you are logged in as 'admin', 'root' or 'system' you can replace the the
userid in the filename by the wildcard *.
Example:
/$PFL/Archive/User/Document for private reprints
/@OVERLAYS/User#Document for
public overlays
To Next Page
Loading...
