While every care has been taken in the preparation of this material, no liability will be accepted by Xerox Corporation arising
out of any inaccuracies or omissions.
Printed in the United States of America.
Other company trademarks are acknowledged as follows:
Many users will interact with the FreeFlow Output Manager (FFOM) only through its browser
based GUIs. However all FreeFlow Output Manager capabilities are also accessible through its
command line interface (CLI). This document helps you understand how to use the Xerox
FreeFlow Output Manager command line interface.
FFOM CLI commands can be used from a command window to interact with FFOM but they can
also be used in scripts that will be automatically executed by FFOM. This is a powerful way to
customize FFOM to a specific workflow. This document tells you how to use this feature of
FFOM.
Command Line User Guide 1-1
IntroductionFreeFlow Output Manager
1-2 Command Line User Guide
FreeFlow Output
2
Manager overview
What is FreeFlow Output Manager
FFOM is an output management system. Its primary purpose is to sit in front of a fleet of
production printers and manage the flow of print jobs submitted to them.
Print jobs are created by client applications, frequently residing on other hosts in a network.
FFOM accepts jobs requests from:
•LPR network printing protocol
•IPP network printing protocol
•JMF protocol (receives JDF jobs)
•Multi-function device (job is scanned at a MFD and sent to FreeFlow Output Manager for
printing at a Production Printer)
•a local command line interface
•either local or network mounted “hot-folders”
•clients sending data to a predefined TCP/IP port
Note that the last two mechanisms rely on the command line interface to perform job
submission.
There are seven user-visible objects in FFOM:
•Job: The job object is a model of a print job. The job object is the managed unit of work
within FFOM. It contains information on the characteristics and state of the job and its
documents. A job can include one or more documents.
•Document: The document object represents the data to be printed and information about
how the data is to be printed.
•Queue: A queue is the central object in FFOM. It maintains a pool of jobs and is responsible
for management of the distribution of these jobs to devices. Each queue has a name and
zero or more associated devices.
•Device: A device represents a printer and a port on an actual printer (for example, a specific
IPP port/virtual printer on a DocuSP). It is possible to have more than one FFOM device that
represents the same printer.
•Server: The server object contains server statistic information. The data includes snapshots
of the internal counters. The internal counters record the number of jobs, number of pages,
and number of bytes received by the queue, sent to devices, and received by the clients
such as CLI, IPP, LPR, GUI, and JMF. Refer to section 5 for details.
•Custom View Group: The Custom View Group defines the objects that are accessible to the
logged in operator. Objects such as printers and queues can be added to the custom view
group. If printers and queues are accessible to the logged in operator, their jobs and
documents are accessible as well.
The feature can be enabled or disabled. When enabled, FFOM administrators still have
access to all objects in the system. FFOM operators can only access the objects that are
associated with the Custom View Groups that the FFOM operator belongs.
•Multi-Function Device (MFD): A device used to scan a job and forward it to FFOM for
further processing. The MFD is used as a client job submitter to FFOM.
All these objects can be dynamically created and deleted. Queues and devices have names
given by the administrator; jobs have names (id’s) that are created by the system; documents
are identified by their position in the job.
FFOM supports a rich set of job processing attributes. Job attributes may be supplied via a
default job ticket associated with a queue, a job ticket prepended to the print data stream or
from instructions delivered via the submission protocol. FFOM supports jobs that contain both
the ASCII Job Ticket and the XPIF Job Ticket. While the job is held or pending in an FFOM
queue, a job ticket editor can be used to inspect and set job ticket instructions.
An FFOM queue is the client submission point. They map to devices in the following ways:
•A queue can accept submissions from any inbound gateway or MFD.
•A queue can send jobs to any number of devices (including zero);
•A device can accept jobs from any number of queues.
In other words, a queue provides a 1-to-n mapping from an inbound service to devices.
Although FFOM does not export a formal, programming interface, it does have a command line
interface and supports three mechanisms through which a sophisticated user can customize job
processing and/or manipulate the document data to be printed. These are the hot-folder
submission method and the queue preprocessing and postprocessing program. The first two
mechanisms allow a user to cause an arbitrary script to be executed when a job enters the
FFOM system. This script, a DOS bat file using FFOM’s CLI, has access to the job object, its
attributes, and for hot-folder submission, the document data. The script can do whatever its
writer wants.
FFOM supplies one program executable intended for use in preprocessing programs. This
program will read a document and guess its PDL, the number of pages in the document, and
whether or not the document is color or monochrome.
In addition to preprocessing, an FFOM queue can be configured so that another script is
executed when the job enters a terminal state. This postprocessing program is intended to
perform things like sending e-mail notification but, again, it can do anything its writer wants.
FFOM supports two job scheduling paradigms:
•First-in, First-out—this is the underlying scheduling mechanism, all other things being equal
(or irrelevant), the first job to enter a queue will be the first job to be sent to a printer
•Priority—incoming jobs can have or be given a priority and the higher the priority, the more
quickly the job will be sent to a printer
•Round-robin—this is the default, underlying device selecting algorithm; all other things
being equal, a queue will cycle through its associated printers and assign a job to the next
available device.
•High-watermark—since most FFOM printers are “spooling” printers; they accept numerous
jobs and have internal queues. FFOM devices can be configured to stop accepting jobs
when they a specified number of jobs already queued-up for printing.
•Capability matching—FFOM devices have attributes that specify their capabilities (‘xxxsupported’ attributes). If so configured, FFOM will match these printer capabilities against
the job’s requirements and not schedule a job to a printer that cannot support all of the
job’s needs.
•Least-busy by job count—Send a job to a printer with the least number of uncompleted
jobs.
•Least-busy by page count—Send a job to a printer with the least pages pending to print.
This applies only to jobs forwarded from FreeFlow Output Manager to the printer.
FFOM supports the following five job splitting models:
•Copies—If a job specifies multiple copies, FFOM will distribute the number of copies of the
job evenly amongst the printers that can print the job.
•B/W and Color Pages—If a job contains color and black and white (B/W) pages, FFOM will
send pages containing color to a Color printer and the B/W pages to a monochrome printer.
•Page range—For a job, FFOM will distribute to each of the printers that can print the job
specifying specific pages to print.
•Documents—If a job contains multiple documents, FFOM will distribute the documents
amongst the printers that can print the job.
•Sets— If the job contains a document that is a VI Container and the VI Container is a VIPP
file with a database, FFOM will distribute to each of the printers that can print the job
specifying the document sets to print.
The FFOM will transform a document whose data is a PDF file to PostScript if the device that will
print the job only supports PostScript.
Users will benefit from the following features of FFOM:
•Centralized control over a printer farm—Through a single FFOM operator interface, an
operator can control how jobs are routed to a set of printers, see their status and redirect
them if necessary.
•Intelligent routing—A client can submit jobs to a single FFOM queue and expect that it will
be routed to a printer that is capable of printing the job and is available.
•Better utilization of printer resources—The print shop will realize more efficient utilization
of its printers since FFOM will ensure that jobs aren’t sent to devices that cannot print
them.
•Quicker turnaround—By taking advantage of FFOM’ job splitting features, multiple copy
jobs can be spread across several printers resulting in less time to print the entire job.
The user-visible objects, (queues, jobs, documents and devices), all have attributes that define
the object’s properties and behaviors. This section describes the model of an object and its
attributes that FFOM presents.
There are three operations that affect an attribute: get, set and remove. The get operation
returns the current value of an attribute, the set operation creates the attribute (if necessary)
and gives it a value; the remove operation removes the attribute from the object. The CLI
explicitly implements the get, set and remove operations for each object.
From the perspective of the end-user, attributes are either read-only or read-write. A read-only
attribute cannot be set or removed. These attributes are typically created when the object is
created and the FFOM software manages their values.
A read-write attribute is instantiated when it is given a value; either explicitly by a user of the
GUI/CLI or, in the case of jobs, through instructions processed by the inbound gateways. A
read-write attribute has its value removed by “removing” the attribute.
In general, read-write attributes do not have default values that are set by the FFOM software.
(But, if there is one, it will have its value explicitly set to that default value.)
The get operation on an attribute that has not been instantiated fails.
will succeed (assuming queue1 exists). If this is followed by:
xomgetque –x queue-connect-to-all-devices queue1
the command will succeed and the write the string
queue1:queue-connect-to-all-devices=true
to standard-out (stdout). If this is followed by:
xomremque –x queue-connect-to-all-devices queue1
and then
xomgetque –x queue-connect-to-all-devices
the final get-queue-attributes will return an error and display the message “queue-connect-toall-devices” does not exist.
This means that a script can use the return of a CLI get operation to determine if an attribute
has been instantiated (i.e., has a value). It also means that for the “-all” argument for the CLI
get operation, the command will return only the attributes that have been instantiated (i.e.,
that have values).
2-4 Command Line User Guide
CLI operation and
3
commands
This section describes the FFOM CLI commands, their options and operands.
CLI overview
Although it is expected that most FFOM users will use the GUIs for most day-to-day operations,
FFOM includes a CLI that provides access to all FFOM functionality. This CLI will be used by
customers or analysts in hot folder, port controller, pre or post-processing scripts.
CLI operation
Security considerations
Since the CLI allows access to all FFOM operations including potentially destructive ones, its
use is restricted to running on the same host as the server software and particular
operations are restricted to members of the FFOM authorization groups.
Return value
The CLI commands will return 0 if successful and a positive integer if an error occurred.
Error messages will be written to standard error. All other data from the CLI is written to
standard out (stdout). A complete list of error codes is given in Appendix B. Commonly
expected error codes are also shown with each command, although these should not be
considered exhaustive.
Command syntax
The FFOM CLI is patterned after a traditional UNIX command. The basic syntax of a FFOM
CLI command is:
command [-options [option argument]] operand
The options are all single letters, option arguments are not optional, and the options must
precede the operand. To ensure uniqueness (and that they are unpronounceable), all FFOM
CLI commands are prefixed with “xom” (signifying “Xerox Output Management”).
Command Line User Guide 3-1
CLI operation and commandsFreeFlow Output Manager
Extended attribute string syntax
The set, get and remove CLI commands use the –x option to specify attribute/value pairs
and attribute names.
In the initial implementation, specifying multiple attributes in a single set command
requires that the attribute/value pairs be separated by commas and that there be no white
space in the –x string (unless it’s the value of an attribute and has been enclosed by
quotes). For example, in a set command the CLI wants to receive:
-x attr=value,attr=value,attr = value
rather than
-x attr=value attr=value.
When setting an attribute, the entire attribute/value pairs must be enclosed in double
quotes. Example:
xomsetque Ross –x “queue-connected-to-all-devices=true”
Attribute Files
In addition to attributes specified using the -x option, one or more attributes can be
specified in a file. The attributes specified are written in XPIF format.
Object identifiers
FFOM objects (jobs, documents, queues and devices) are often the operands of CLI
commands. Queues and devices are identified by their unique names. Although jobs have a
unique numeric id, the FFOM CLI requires that user also specify the queue the job resides in
along with the job id. The syntax for this is “queue:id”. A document’s id consists of the job
identifier followed by a “:” followed by the number of the document within the job. For
example ‘queue1:123’ identifies job 123, which is currently contained in queue1 and
queue1:123:2 identifies the second document in the same job.
Note that if a job has only one document, it is not necessary to specify the document
number. For example, if job 123 has only one document associated with it
The following section shows the CLI string representation for the attribute syntaxes.
boolean
The boolean attribute syntax has only two values: ‘true’ and ‘false’. For example:
xomsetque –x “queue-connect-to-all-devices=true”
queue1
followed by
xomgetque –x queue-connect-to-all-devices queue1
would return
queue1:queue-connect-to-all-devices = true
3-2 Command Line User Guide
FreeFlow Output ManagerCLI operation and commands
Note that the CLI prints the string ‘queue1:queue-connect-to-all-devices = true’ to
standard-out. The command returns a 0 even if the value of the attribute is false.
collection
The collection attribute syntax is a container holding a set of attributes, called member
attributes. The names of each member attribute are unique for a collection attribute, but
may be the same as the name of a member attribute in another collection attribute or the
same as the name of an attribute that is not a member of a collection.
FreeFlow Output Manager validates and processes each member attribute of a collection
attribute in the same way that it validates and processes normal attributes. The collection
merely serves as a ‘container’ for the member attributes. Each member attribute can
have any attribute syntax type, including 'collection', and can be either single-valued or
multi-valued (1setOf). The length of a collection value is not limited. However, the length of
each member attribute must not exceed the limit of its attribute syntax.
The CLI represents collection syntax as the member attributes and their values enclosed in
curly braces (‘{‘and ‘}’). Each member attribute is delimited by a comma with no spaces
within the collection.
The enum attribute syntax is an enumerated integer value in the range 1 to MAX and each
value has an associated ‘keyword’ name. The CPSS spec uses 'type1', 'type2' and 'type3'
prefixes to indicate different levels of review and/or standards bodies that are involved in
the definition of the values. This specification has removed those indicators.
Since each integer in the enum has an associated keyword, either the enum or associated
keyword can be used when specifying the enum value.
Command Line User Guide 3-3
CLI operation and commandsFreeFlow Output Manager
integer
The integer syntax include an inclusive range constraint of the form (min:max). Valid values
for attributes must be within these ranges. The MIN value for integers is –2**31 and the
MAX value for integers is 2**31-1.
For example
xomsetjob –x “job-priority=202” queue1:123
would return an error since the maximum value for job-priority is 100.
keyword
The keyword syntax is a sequence of characters of length 1 to 255 containing only the USASCII encoded values for lowercase letters, uppercase letters, hyphen, dot and underscore.
The first character must be lowercase and the keywords must be U.S. English.
This syntax type is used for enumerating semantic identifiers. Keyword values for attributes
are listed in the description of the attribute.
mimeMediaType
The mimeMediaType attribute syntax is the Internet Media Type (called MIME type) as
defined by RFC 2046 for identifying a document format. The value may include a charset,
or other, parameter, depending on the specification of the Media Type in the IANA registry.
Although most other syntax types allow for only lower-case values, this syntax type allows
for both mixed-case values which are case insensitive.
The FFOM CLI recognizes only the following mimeMediaType values for input:
•‘text/plain’: An plain text document in US-ASCII
•‘application/postscript’: A PostScript document
•‘application/vnd.hp-PCL’: A PCL document
•‘application/pdf’: A PDF document
•‘application/octet-stream’: An unspecified representation
•‘image/tiff’: A Tagged Image File Format document.
•'application/vnd.xerox-VI-project-container': A VI container file.
would set the job’s document format attribute to PostScript.
name
This syntax type is used for user-friendly strings. Names are never translated from one
natural language to another. The maximum length of a name syntax type is 255 octets. If
the attribute will always contain less than 255 octets, the syntax can be qualified by the
maximum allowable length (for example, device-name is limited to 127 octets).
The delimiters for inputting the name syntax are right and left quotation marks. To avoid
parsing problems, the FFOM CLI restricts the name syntax type to exclude:
•left and right quotation marks
•the colon (“:”)
•left and right curly braces (“{“and “}”)
For example:
xomcreque “Useless Queue”
does exactly what you’d think it does.
3-4 Command Line User Guide
FreeFlow Output ManagerCLI operation and commands
rangeOfInteger
This syntax is an ordered pair of integers that defines an inclusive range of integer values.
The first integer specifies the lower bound and the second specifies the upper bound. If a
range constrain is specified (e.g., 1:100), then the constraint applies to both integers.
will fail with an INVALID PARAMETER error since the maximum value allowed for the
attribute job-priorities accepted is 100.
text
A text attribute is an attribute whose value is a sequence of zero or more characters
encoded in a maximum of 1023 (‘MAX’) octets. MAX is the maximum length for each value
of any text attribute. However, if an attribute will always contain values whose maximum
length is much less than MAX, the definition of that attribute will include a qualifier that
defines the maximum length for values of that attribute.
The delimiters for inputting the text syntax are right and left quotation marks. To avoid
parsing problems, the FFOM CLI restricts the text syntax type to exclude:
•left and right quotation marks
•the colon (“:”)
•left and right curly braces (“{“and “}”)
uri
The uri attribute syntax is any valid Uniform Resource Identifier (see RFC 2396). The
particular uri scheme supported for a given attribute is described in that attribute’s
description.
1setOf
The 1setOf attribute is one or more values of the above attribute syntax types (except
1setOf itself). The attribute is called 1setOf rather than just setOf as a reminder that the
set of values must not be empty. The sets are normally unordered but a given attribute can
specify that the values must be in a particular order.
Command Line User Guide 3-5
CLI operation and commandsFreeFlow Output Manager
The CLI represents 1setOf syntax as the values enclosed in curly braces (‘{‘and ‘}’) with the
values separated by commas. For example:
Every FFOM CLI command accepts the options “-h” or “-?”. These options cause the
command to write a brief help message to standard out.
Software Version
Every FFOM CLI command accepts the option "-v". This option will display the version of
FFOM.
Example:
xomlisjob -v
might return
8.0.0.0_808[10305.20090225]
add-document
This command adds a document to an existing job. For this operation to be successful, the jobstate must be held. The job attribute number-of-documents is incremented by 1. If the
document is located in a document repository, a username and password is required to retrieve
the document from the repository.
This operation has the following optional argument:
• "open". If specified, the job is kept open which delays preprocessing until the job is
"closed". The job is considered closed when any of the commands xomrepjob, xomsetjob,
xomsetdoc, xomadddoc does not specify the -e option is invoked.
Command name:
xomadddoc
Operand:
uri uridesignating the file to be added to the job.
Options:
-j queue:jobId
-e open (delays preprocessing of job)
-u username required to login to the document repository
-s password required to login to the document repository
3-6 Command Line User Guide
FreeFlow Output ManagerCLI operation and commands
Returns:
0 if successful
JOB_NOT_IN_QUEUE (12) if the job does not exist
INVALID_PARAMETER (22) if the uri is invalid (i.e., file
This command will create a backup of FFOM. The created backup file is a zip file which is used
to restore FFOM through the restore-server command. The user invoking the command must
have Windows Administrator privileges as FFOM processes are stopped and restarted during
this operation.
The backup file contains the following:
•Configuration settings
•Jobs, Queues, Printers
–Jobs in the pending, held state will be backed up and restored successfully. Jobs in
processing, and completed states will be backed up but upon restore will be deleted.
•Printers registered in Printer Registration Utility
•Hot Folder and Port Configuration configuration settings
•Accounting Module database and reports
The command must be invoked from the "bin" sub-directory of the FFOM installation directory
(e.g. C:\Program Files\xerox\FreeFlow Output Manager).
Command name:
ffom_backup
Operand:
Fully qualified path to the backup file to be created. If the operand is not specified, the
generated file is written to the FFOM installation sub-directory called "Backups". The
name of the file is ffbackup_OutputManager_YYYYMMDD_n.zip where:
•YYYY is the year
•MM is the numerical month (e.g. 01 is January)
•DD is the day of the month
•n is the incremental version to avoid conflicts of existing files with the same name in
This command will return the list of items and their associated repository IDs contained in the
specified directory. The IDs for the files are used as input for the xomprijob, xomadddoc,
xomcpfdoc, xomcptdoc commands when specifying an item in a document repository.
Command name:
xombrorps
Operand:
Directory ID in the form "repository://<id>"
Options:
-u username required to login to the document repository
-s password required to login to the document repository
Returns:
0 if successful
INVALID_PARAMETER (22) if the attribute is not
recognized
Example:
xombrorps -u ross -s mypassword
xombrorps -u ross -s mypassword repository://
0234348324024055389043
cancel-document
This command cancels a document associated with an existing job. The cancel-document
operation prevents the document from being printed. The operation is successful if the job-state
is pending, held, or processing. If the document-state is processing, best effort is made to cancel
printing at the device. If the job contains only a single document, the document cannot be
cancelled; the job must be cancelled.
The document-state is set to “aborted” and document-state-reasons is set to “cancelled-byoperator”. The associated document data is not deleted.
Command name:
xomcandoc
3-8 Command Line User Guide
FreeFlow Output ManagerCLI operation and commands
Operand:
queue:jobId:docId
Options:
None
Returns:
0 if successful
DOCUMENT_NOT_FOUND (25) if document does not exist
JOB_ERROR (13) if attempting to cancel last document in
the job
Examples:
xomcandoc myQueue:14:3
cancel-job
This command cancels a job (i.e., sets its job-state to canceled). As much as is practical, no
further processing or printing will occur on a cancelled job; if it is printing when the cancel is
issued, FFOM will attempt to stop printing. The job-state is set to "aborted" and job-statereasons is set to "job-canceled-by-operator".
FFOM will accept or reject the cancel operation depending on the job’s state. The following
table shows the effect the cancel operation has on job-state.
Current job-statusNew job-statusStatus
pendingabortedOk, cancel occurs immediately
heldabortedOk, cancel occurs immediately
processingabortedOk, may return before completed
abortedabortedOperation returns an error
completedcompletedOperation returns an error
A canceled job is not necessarily removed from the system. If, for example, the job’s job-retention-period attribute has a value, the job will stay in FFOM until the retention period
expires.
Command name:
xomcanjob
Operand:
queue:id
Command Line User Guide 3-9
CLI operation and commandsFreeFlow Output Manager
Options:
none
Returns:
0 if successful
JOB_NOT_IN_QUEUE (12) if the job does not exist
JOB_IN_INVALID_STATE (11) if the job cannot be canceled
Examples:
xomcanjob queue1:123
check-job
This command returns a list of job attributes that fail capability scheduling against a specified
device. The job attributes are listed via stdout.
Command name:
xomchkjob
Operand:
job-id
Options:
-d name of device
Returns:
0 if successful
JOB_NOT_IN_QUEUE (12) if the job does not exist
DEVICE_NOT_FOUND (7) if the device does not exist
Examples:
xomchkjob myQ:34 –d MyPrinter
media-col
sides
clear-counters
This command resets the "counters since last reset" to 0. Refer to chapter 5, Server Attributes on
page 1 for more information on counters.
Command name:
xomclrcnt
Options:
None
3-10 Command Line User Guide
FreeFlow Output ManagerCLI operation and commands
Returns:
0 if successful
Examples:
xomclrcnt
copy-to-document
This command replaces the document data for the document with the specified file. This
operation is used by preprocessing or postprocessing scripts that may wish to modify the
original document data and store an updated version associated with the document.
If the document data is stored in a document repository, a username and password is required
to retrieve the document from the repository.
To obtain a copy of the original document data, the script uses the copy-from-document
operation.
Command name:
xomcptdoc
Operand:
Filename
-d queue-name:jobId:document-number
Options:
-b max number of bytes to store. If not specified, the
entire document data is stored.
-u username required to login to the document repository
-s password required to login to the document repository
Returns:
0 if successful
DOCUMENT_NOT_FOUND (25) if document does not exist
INVALID_PARAMETER (22) if can’t read data from file
Examples:
xomcptdoc –d myQueue:14:1 newdocdata
Replaces the current document data for the document referenced by myQueue:14:1 with
the contents of the file newdocdata
xomcptdoc –d myQueue:14:1 –b 100 newdocdata
Replaces the current document data for the document referenced by myQueue:14:1 with
the first 100 bytes from the contents of the file newdocdata.
xomcptdoc -d myQueue:14:1 repository://
32349028342390423 -b 100 -u ross -s mypassword
Replaces the current document data for the document referenced by myQueue:14:1 with
the first 100 bytes from the contents of the file contained in the repository.
Command Line User Guide 3-11
CLI operation and commandsFreeFlow Output Manager
copy-from-document
This command copies the document data associated with the document to a file or provides an
absolute filepath to the document data. The –f option will instruct copy-from-document to
copy the document data content to the specified filename. Otherwise, the command will return
the absolute file path to the file in FFOM’s spool directory.
This is used by preprocessing or postprocessing scripts that may wish to perform some action on
the document data such as analyzing the data for the PDL format, estimating the number of
impressions the document represents.
If the document data will be stored to a repository, a username and password is required to
store the document into the repository.
Command name:
xomcpfdoc
Operand:
queue:jobId:docId
Options:
-b max number of bytes to retrieve.
If not specified, entire document data is retrieved.
-f <filename>absolute filepath where the document data
is copied
-a prepend document attributes using an XPIF job ticket
-u username required to login to the document repository
-s password required to login to the document repository
Returns:
0 if successful
DOCUMENT_NOT_FOUND (25) if document does not exist
INVALID_PARAMETER (22) if can’t write data to file
JOB_IN_INVALID_STATE (11) if document is in wrong state
Examples:
xomcpfdoc myQueue:14:1
Returns the filepath to the document data referenced by document 1 of job-id 14 in queue
“myQueue”.
xomcpfdoc myQueue:14:1 –f C:\mylocalcopy
Copies the document data referenced by document 1 of job-id 14 in queue “myQueue” to
the file “C:\mylocalcopy”.
xomcpfdoc myQueue:14:1 –f C:\mylocalcopy –a
Copies the document data referenced by document 1 of job-id 14 in queue “myQueue” to
the file “C:\mylocalcopy” prepending the document attributes in XPIF job ticket format
xomcpfdoc myQueue:14:1 -f repository://
2340928342390423908 -u ross -s mypassword
3-12 Command Line User Guide
FreeFlow Output ManagerCLI operation and commands
Copies the document data referenced by document 1 of job-id 14 in queue "myQueue" to a
file in the repository.
copy-job
The copy-job operation creates a duplicate copy of the original job and its associated
documents and submits the job to the specified queue. The operation applies to the job in any
state with the exception of "pre-processing".
The new copy is processed the same way as a newly submitted job into the system.
This operation has the following optional arguments:
• "open". If specified, the job is kept open which delays preprocessing until the job is
"closed". The job is considered closed when any of the commands xomcpyjob, xomrepjob,
xomsetjob, xomsetdoc, xomadddoc does not specify the -e option is invoked.
• "hold-job". If the option is specified, the new job will be put in the held state. This allows
modification of the new job's attributes prior to the job being released for scheduling.
The job template attributes of the created job are identical to those in the original job.
The document template attributes of the create documents within the job are identical to
those in the original.
The following table indicates how the read-only job attributes of the new job are affected.
AttributeValue in new job
date-time-at-completedAttribute deleted (i.e., no value)
date-time-at-creationAbsolute time of the copy operation
date-time-of-processingAttribute deleted (i.e., no value)
date-time-at-processing-completedAttribute deleted (i.e., no value)
date-time-at-markingAttribute deleted (i.e., no value)
date-time-at-marking-completedAttribute deleted (i.e., no value)
job-impressions-completedAttribute deleted (i.e., no value)
job-impressions-completed-colorAttribute deleted (i.e., no value)
job-impressions-completed-blackonly
Attribute deleted (i.e., no value)
duration-markingAttribute deleted (i.e., no value)
document-nameSame as original job
job-idAssigned by system
job-id-on-clientSame as original job
job-id-on-printerAttribute deleted (i.e., no value)
Command Line User Guide 3-13
CLI operation and commandsFreeFlow Output Manager
AttributeValue in new job
pagesSame as original job
job-k-octetsSame as original job
job-originating-user-nameSame as original job
job-originating-host-nameSame as original job
job-nameSame as original job
job-parent-job-idJob ID of original job
job-reprocessing-job-idsAttribute deleted (i.e., no value)
job-statepending or held
job-state-reasonsAttribute deleted (i.e., no value)
number-of-documentsSame as original job
output-device-actualAttribute deleted (i.e., no value)
output-deviceSame as original job if submitted to saame queue.
Otherwise attribute deleted
The following table indicates how the read-only document attributes of the new job are
affected.
AttributeValue in newdocument
date-time-at-completedAttribute deleted (i.e., no value)
date-time-at-creationAbsolute time of the copy operation
date-time-of-processingAttribute deleted (i.e., no value)
date-time-at-processing-completedAttribute deleted (i.e., no value)
date-time-at-markingAttribute deleted (i.e., no value)
date-time-at-marking-completedAttribute deleted (i.e., no value)
impressions-completedAttribute deleted (i.e., no value)
impressions-completed-colorAttribute deleted (i.e., no value)
impressions-completed-black-onlyAttribute deleted (i.e., no value)
duration-markingAttribute deleted (i.e., no value)
document-nameSame as original document
impressionsSame as original job
job-id-on-printerAttribute deleted (i.e., no value)
k-octetsSame as original document
document-statepending
3-14 Command Line User Guide
Loading...
+ 150 hidden pages
You need points to download manuals.
1 point = 1 manual.
You can buy points or you can get point for every manual you upload.