HPOS 4.0 technical note 3

HP Web Services for Output Server 8
Using HP Web Services for Output Server
Multiple-document print failure
Response- createJobResponse object
For .NET clients,
Input param- createJob object
createJob object will have only one argument.
1. XML createJob contract
Response- createJobResponse object
The following is an example of a createJobs request:
<wsg-request>
<operation-attributes>
<destination>labld_ps1</destination>
</operation-attributes>
<request-attributes>
<copy-count>1</copy-count>
</request-attributes>
</wsg-request>
The following is an example of a createJobs response:
<wsg-response>
<status-code>0</status-code>
<status-message>Success</status-message>
<operation-attributes>
<status-code>0</status-code>
<status-message>Success</status-message>
<wsg-job-handle>JOB:3FE4B2A742576E73B5704DC909B8D0DA:7</wsg-job-handl
e>
</operation-attributes>
</wsg-response>
NOTE: Ensure that the destination to which the client submits a job is valid and available before
submitting a job.
NOTE: Ensure proper using of -document-filename and -job-comment attributes while
submitting a job. For more information, see HP Output Server System Administrator’s
Attribute Reference.
Sending Documents
The sendDocuments API uses the job handle returned with the createJobs API response to send the document
data along with the document contract. The structure of the API is:
Table 1-2. createJobs attributes
Type Name Value Requirement
Operation Destination HP Output Server logical destination Mandatory
Request Job attributes All job attributes in HP Output Server such
as job-owner, -job-name, and
-copy-count
Not mandatory
Request document-filename File name of the document Mandatory