HPOS 4.0 technical note 3

HP Web Services for Output Server 15
Using HP Web Services for Output Server
Multiple-document print failure
The following is an example of a queryJobs response:
<wsg-response>
<status-code>0</status-code>
<status-message>success</status-message>
<operation-attributes>
<status-code>has-more-chunks</status-code>
<status-message>false</status-message>
</operation-attributes>
<job-info>
<job-client-id>dlm:1:72</job-client-id>
<status-code>0</status-code>
<status-message>success</status-message>
<subjob-info>
<status-code>0</status-code>
<status-message>success</status-message>
<job-identifier>jqm:2530598</job-identifier>
<current-job-state>retained</current-job-state>
<job-completion-status>success</job-completion-status>
<queue-assigned>qfile</queue-assigned>
<destination>lfile</destination>
</subjob-info>
</job-info>
</wsg-response>
The has-more-chunks tag in the response indicates if there are more jobs waiting to be fetched on the server. The
client can make subsequent requests to fetch further responses, unless the has-more-chunks tag value has been
set to false. All requests for a batch must be made in a single session.
Querying subjobs
The querySubJobs API is used to query HP Output Server subjobs. The structure of the API is:
Web Service Name: querySubJobs
Web Service Parameters
Parameter 1 - XML querySubJobs contract
For .NET clients,
Input param- querySubJobs object
querySubJobs will have only one argument.
1. XML queryJobs contract
Response- querySubJobsResponse object
Users are authorized at the HP Output Server level to query subjobs.
Table 1-8. querySubJobs attributes
Type Name Value Requirement
Operation -job-identifier JQM ID(s) Mandatory
Operation batch-size Size of the response batch Not mandatory
Operation Filter attributes such as
-job-owner
Owner of the job (dazel user) Not mandatory