job view
Displays information about the specified job, and optionally includes a detailed list of property values or historical information.
For examples of how to use this command, see Examples.
Syntax
job view <jobID> [/detailed[:{true|false}]] [/history[:{true|false}]]
[/scheduler:<name>]
job view {/? | /help}
Parameters
Parameter | Description |
---|---|
jobID | Specifies the identifier of the job for which you want to view information. |
/detailed[:{true|false}] | Specifies whether to display a detailed list of property values for the job. A value of True indicates that the job view command should display a detailed list of property values for the job. A value of False indicates that the job view command should display a short list of property values for the job. When you specify the /detailed parameter without a value, the job view command behaves as if you specified a value of True. If you do not specify the /detailed parameter, the job view command behaves as if you specified a value of False. The /detailed or /detailed:true parameter overrides the /history or /history:true parameter. |
/history[:{true|false}] | Specifies whether to display the history of the job. A value of True indicates that the job view command should display the history of the job. A value of False indicates that the job view command should not display the history of the job. When you specify the /history parameter without a value, the job view command behaves as if you specified a value of True. If you do not specify the /history parameter, the job view command behaves as if you specified a value of False. If you specify the /detailed or /detailed:true parameter, the /history parameter has no effect, and the job view command displays a detailed list of property values for the job. |
/scheduler:<name> | Specifies the host name or IP address of the head node for the cluster that contains the job for which you want to view information. The value must be a valid computer name or IP address. If you do not specify the /scheduler parameter, this command uses the scheduler on the head node that the CCP_SCHEDULER environment variable specifies. |
/? | Displays Help at the command prompt. |
/help | Displays Help at the command prompt. |
Remarks
If you run the job view command with the /detailed parameter for a job that was already submitted, the command lists minimum and maximum values for all resources types, regardless of the resource type for which you specified minimum and maximum values when you configured the job. The minimum and maximum values for the types of resources that do not correspond to the value of the UnitType property originate from the job template for the job and are ignored by the HPC Job Scheduler Service. For example, if you created a job and specify that it should use a minimum of 2 cores and a maximum of 16 cores, you might see the following lines in the output from the job view command with the /detailed parameter after you submit the job:
UnitType : Cores MinCores : 2 MaxCores : 16 MinSockets : 1 MaxSockets : 1 MinNodes : 1 MaxNodes : 1
In this case, the HPC Job Scheduler Service ignores the values for the MinSockets, MaxSockets, MinNodes, and MaxNodes properties.
Starting with Microsoft HPC Pack 2008 R2, the value that the job view command displays for the Allocated Nodes property depends on whether the job is running or complete. Before the job runs, the Allocated Nodes property contains no nodes. While the job runs, the Allocated Nodes property lists the nodes that the currently running tasks in the job are using. When the job is complete, the Allocated Nodes property lists the superset of all of the nodes that the job ever used, including nodes that were reallocated before any task in the job completed on the node.
Examples
To view a short list of property values for the job with an identifier of 27, use the following command:
job view 27
To view a detailed list of property values for the job with an identifier of 18, use the following command:
job view 18 /detailed:true
To view the history of the job with an identifier of 39, use the following command:
job view 39 /history:true