Find Job Status operation
The Find Job Status operation finds the details of all the jobs that match the filter criteria specified.
The following table describes the elements for this request.
Adapter request elements for the Find Job Status operation
Element |
Definition |
Required |
---|---|---|
|
Specifies the name of the operation: |
Yes |
|
Specifies a list of arguments required for the operation |
Yes |
|
Contains the parent XML element for the |
Conditional; required if the adapter configuration is empty in Grid Manager |
|
Contains the child XML Notes
|
Conditional; required if |
|
Specifies the host name or IP address of the server on which NetApp DataFabric Manager is running |
Conditional; required if |
|
Specifies the user name required to log on to the NetApp DataFabric Manager |
Conditional; required if |
|
Specifies the password that corresponds to the |
Conditional; required if |
|
Specifies the communication protocol used by the adapter |
No |
|
Specifies the port on which NetApp DataFabric Manager is enabled |
No |
|
Specifies the child XML element of the
|
No |
|
Specifies the identifier of a job to list |
No |
|
Specifies the state of the jobs to list |
No |
|
Specifies the types of the jobs to list |
No |
|
If specified, this is the maximum number of jobs that the client wishes to receive at once. |
No |
|
Specifies the name or ID of the dataset or a group |
No |
A sample adapter request for this operation is given in the following figure.
Sample adapter request for the Find Job Status operation
<netapp-storage-request>
<operation-name>find-job-status</operation-name>
<arguments>
<targets>
<target>
<host>Server137</host>
<user-name>username</user-name>
<password encryption-type = "Base64">cGFzc3dvcmQ=</password>
<protocol>http</protocol>
<port>8088</port>
</target>
</targets>
<target />
<job-id>1371</job-id>
</arguments>
</netapp-storage-request>
A sample adapter response for this operation is given in the following figure.
Sample adapter response for the Find Job Status operation
<netapp-storage-response>
<metadata>
<status>success</status>
<response-count>1</response-count>
</metadata>
<responses>
<response>
<metadata>
<target>Server137</target>
<status>success</status>
<count>1</count>
</metadata>
<output>
<dp-job-info>
<job-id>1371</job-id>
<job-type>provision_member</job-type>
<started-timestamp>1263444675</started-timestamp>
<completed-timestamp>1263444675</completed-timestamp>
<job-description>Provision a storage container
'Storage 1263446241296' of size 16.0 MB.</job-description>
<dataset-id>607</dataset-id>
<dataset-name>QA-DataSetName1</dataset-name>
<policy-name>QA-Test1</policy-name>
<policy-id>299</policy-id>
<object-id>607</object-id>
<object-name>QA-DataSetName1</object-name>
<object-type>dataset</object-type>
<job-context-obj-id>607</job-context-obj-id>
<job-context-obj-name>QA-DataSetName1</job-context-obj-name>
<job-context-obj-type>dataset</job-context-obj-type>
<submitted-by>domain-name\username</submitted-by>
<job-progress>failure</job-progress>
<job-state>completed</job-state>
<job-overall-status>failed</job-overall-status>
<!--Please note that only the failed status is being captured
but not the actual error description-->
<bytes-transferred>0</bytes-transferred>
<source-node-name>Test1 $ Node Name</source-node-name>
<source-node-id>1</source-node-id>
<destination-node-name />
<destination-node-id>0</destination-node-id>
<provision-request-info>
<provision-member-request-info>
<name>Storage 1263446241296</name>
<description>Provision a storage container
'Storage 1263446241296' of size 16.0 MB.</description>
<size>16777216</size>
<maximum-data-size>0</maximum-data-size>
<initial-snapshot-space>0</initial-snapshot-space>
<maximum-snapshot-space>0</maximum-snapshot-space>
<provisioning-policy-id>289</provisioning-policy-id>
<provisioning-policy-name>QA-JS1</provisioning-policy-name>
</provision-member-request-info>
</provision-request-info>
</dp-job-info>
</output>
</response>
</responses>
</netapp-storage-response>
Comments
Log in or register to comment.