"The client supplies a Job Template attribute and the attribute value
is not among the values supported by the Printer: This case depending
on the value of the "best-effort" attribute (see section 4.2.8), tIf the client
supplies a "best-effort" of 'false' (or supplies no "best-effort" attribute and
the printer's default behavior attribute is set to 'false') the Printer SHALL
reject the Job and return the 'client-error-attribute-unsupported" error
code and the unsupported attribute in the "unsupported attributes"
output parameter. If the client supplies a "best-effort" of 'true' (or
supplies no "best-effort" attribute and the Printer's default behavior
attribute is set to 'true') the printer SHALL accept the Job and
substitute supported values for all unsupported values supplied by
the client. In this case, if everything else is ok, the Printer returns a
"successful-ok" status code. The client must query the newly create
Job object to find out if any of the requested values have been
modified."
1) When the job is rejected, shouldn't the error code say something
like 'client-error-attribute-value-unsupported'? Otherwise it is not
clear that the attribute itself is supported, but the supplied value is not.
2) Should the unsupported values be returned as parameters's?
3) As the text currently reads, when substitution occurs, the Printer
may choose any supported attribute value that it chooses. Is this
is what is intended? I would prefer that the default value be used
and the text reflect the same processing as in case 5 (the value
is not assigned at job creation, but at job processing time).
4) At one time, I thought we had a status code the said something
like "ok-values substituted" for the case where "best-effort" was
set to true. This alerts the end user that the ouput may not appear
exactly as intended, but is printing anyway.
Roger K deBry
Senior Techncial Staff Member
Architecture and Technology
IBM Printing Systems
email: rdebry@us.ibm.com
phone: 1-303-924-4080