Jobs Interface

public abstract void add(JobAddParameter job)

Adds a Job to the specified Account. The Batch service supports two ways to control the work done as part of a Job. In the first approach, the user specifies a Job Manager Task. The Batch service launches this Task when it is ready to start the Job. The Job Manager Task controls all other Tasks that run under this Job, by using the Task APIs. In the second approach, the user directly controls the execution of Tasks under an active Job, by using the Task APIs. Also note: when naming Jobs, avoid including sensitive information such as user names or secret project names. This information may appear in telemetry logs accessible to Microsoft Support engineers.

Parameters:

public abstract void add(JobAddParameter job, JobAddOptions jobAddOptions)

Adds a Job to the specified Account. The Batch service supports two ways to control the work done as part of a Job. In the first approach, the user specifies a Job Manager Task. The Batch service launches this Task when it is ready to start the Job. The Job Manager Task controls all other Tasks that run under this Job, by using the Task APIs. In the second approach, the user directly controls the execution of Tasks under an active Job, by using the Task APIs. Also note: when naming Jobs, avoid including sensitive information such as user names or secret project names. This information may appear in telemetry logs accessible to Microsoft Support engineers.

Parameters:

public abstract Observable addAsync(JobAddParameter job)

Adds a Job to the specified Account. The Batch service supports two ways to control the work done as part of a Job. In the first approach, the user specifies a Job Manager Task. The Batch service launches this Task when it is ready to start the Job. The Job Manager Task controls all other Tasks that run under this Job, by using the Task APIs. In the second approach, the user directly controls the execution of Tasks under an active Job, by using the Task APIs. Also note: when naming Jobs, avoid including sensitive information such as user names or secret project names. This information may appear in telemetry logs accessible to Microsoft Support engineers.

Parameters:

Returns:

public abstract Observable addAsync(JobAddParameter job, JobAddOptions jobAddOptions)

Adds a Job to the specified Account. The Batch service supports two ways to control the work done as part of a Job. In the first approach, the user specifies a Job Manager Task. The Batch service launches this Task when it is ready to start the Job. The Job Manager Task controls all other Tasks that run under this Job, by using the Task APIs. In the second approach, the user directly controls the execution of Tasks under an active Job, by using the Task APIs. Also note: when naming Jobs, avoid including sensitive information such as user names or secret project names. This information may appear in telemetry logs accessible to Microsoft Support engineers.

Parameters:

Returns:

public abstract ServiceFuture addAsync(JobAddParameter job, JobAddOptions jobAddOptions, ServiceCallback serviceCallback)

Adds a Job to the specified Account. The Batch service supports two ways to control the work done as part of a Job. In the first approach, the user specifies a Job Manager Task. The Batch service launches this Task when it is ready to start the Job. The Job Manager Task controls all other Tasks that run under this Job, by using the Task APIs. In the second approach, the user directly controls the execution of Tasks under an active Job, by using the Task APIs. Also note: when naming Jobs, avoid including sensitive information such as user names or secret project names. This information may appear in telemetry logs accessible to Microsoft Support engineers.

Parameters:

Returns:

public abstract ServiceFuture addAsync(JobAddParameter job, ServiceCallback serviceCallback)

Adds a Job to the specified Account. The Batch service supports two ways to control the work done as part of a Job. In the first approach, the user specifies a Job Manager Task. The Batch service launches this Task when it is ready to start the Job. The Job Manager Task controls all other Tasks that run under this Job, by using the Task APIs. In the second approach, the user directly controls the execution of Tasks under an active Job, by using the Task APIs. Also note: when naming Jobs, avoid including sensitive information such as user names or secret project names. This information may appear in telemetry logs accessible to Microsoft Support engineers.

Parameters:

Returns:

public abstract Observable<>> addWithServiceResponseAsync(JobAddParameter job)

Adds a Job to the specified Account. The Batch service supports two ways to control the work done as part of a Job. In the first approach, the user specifies a Job Manager Task. The Batch service launches this Task when it is ready to start the Job. The Job Manager Task controls all other Tasks that run under this Job, by using the Task APIs. In the second approach, the user directly controls the execution of Tasks under an active Job, by using the Task APIs. Also note: when naming Jobs, avoid including sensitive information such as user names or secret project names. This information may appear in telemetry logs accessible to Microsoft Support engineers.

Parameters:

Returns:

public abstract Observable<>> addWithServiceResponseAsync(JobAddParameter job, JobAddOptions jobAddOptions)

Adds a Job to the specified Account. The Batch service supports two ways to control the work done as part of a Job. In the first approach, the user specifies a Job Manager Task. The Batch service launches this Task when it is ready to start the Job. The Job Manager Task controls all other Tasks that run under this Job, by using the Task APIs. In the second approach, the user directly controls the execution of Tasks under an active Job, by using the Task APIs. Also note: when naming Jobs, avoid including sensitive information such as user names or secret project names. This information may appear in telemetry logs accessible to Microsoft Support engineers.

Parameters:

Returns:

public abstract void delete(String jobId)

Deletes a Job. Deleting a Job also deletes all Tasks that are part of that Job, and all Job statistics. This also overrides the retention period for Task data; that is, if the Job contains Tasks which are still retained on Compute Nodes, the Batch services deletes those Tasks' working directories and all their contents. When a Delete Job request is received, the Batch service sets the Job to the deleting state. All update operations on a Job that is in deleting state will fail with status code 409 (Conflict), with additional information indicating that the Job is being deleted.

Parameters:

public abstract void delete(String jobId, JobDeleteOptions jobDeleteOptions)

Deletes a Job. Deleting a Job also deletes all Tasks that are part of that Job, and all Job statistics. This also overrides the retention period for Task data; that is, if the Job contains Tasks which are still retained on Compute Nodes, the Batch services deletes those Tasks' working directories and all their contents. When a Delete Job request is received, the Batch service sets the Job to the deleting state. All update operations on a Job that is in deleting state will fail with status code 409 (Conflict), with additional information indicating that the Job is being deleted.

Parameters:

public abstract Observable deleteAsync(String jobId)

Deletes a Job. Deleting a Job also deletes all Tasks that are part of that Job, and all Job statistics. This also overrides the retention period for Task data; that is, if the Job contains Tasks which are still retained on Compute Nodes, the Batch services deletes those Tasks' working directories and all their contents. When a Delete Job request is received, the Batch service sets the Job to the deleting state. All update operations on a Job that is in deleting state will fail with status code 409 (Conflict), with additional information indicating that the Job is being deleted.

Parameters:

Returns:

public abstract Observable deleteAsync(String jobId, JobDeleteOptions jobDeleteOptions)

Deletes a Job. Deleting a Job also deletes all Tasks that are part of that Job, and all Job statistics. This also overrides the retention period for Task data; that is, if the Job contains Tasks which are still retained on Compute Nodes, the Batch services deletes those Tasks' working directories and all their contents. When a Delete Job request is received, the Batch service sets the Job to the deleting state. All update operations on a Job that is in deleting state will fail with status code 409 (Conflict), with additional information indicating that the Job is being deleted.

Parameters:

Returns:

public abstract ServiceFuture deleteAsync(String jobId, JobDeleteOptions jobDeleteOptions, ServiceCallback serviceCallback)

Deletes a Job. Deleting a Job also deletes all Tasks that are part of that Job, and all Job statistics. This also overrides the retention period for Task data; that is, if the Job contains Tasks which are still retained on Compute Nodes, the Batch services deletes those Tasks' working directories and all their contents. When a Delete Job request is received, the Batch service sets the Job to the deleting state. All update operations on a Job that is in deleting state will fail with status code 409 (Conflict), with additional information indicating that the Job is being deleted.

Parameters:

Returns:

public abstract ServiceFuture deleteAsync(String jobId, ServiceCallback serviceCallback)

Deletes a Job. Deleting a Job also deletes all Tasks that are part of that Job, and all Job statistics. This also overrides the retention period for Task data; that is, if the Job contains Tasks which are still retained on Compute Nodes, the Batch services deletes those Tasks' working directories and all their contents. When a Delete Job request is received, the Batch service sets the Job to the deleting state. All update operations on a Job that is in deleting state will fail with status code 409 (Conflict), with additional information indicating that the Job is being deleted.

Parameters:

Returns:

public abstract Observable<>> deleteWithServiceResponseAsync(String jobId)

Deletes a Job. Deleting a Job also deletes all Tasks that are part of that Job, and all Job statistics. This also overrides the retention period for Task data; that is, if the Job contains Tasks which are still retained on Compute Nodes, the Batch services deletes those Tasks' working directories and all their contents. When a Delete Job request is received, the Batch service sets the Job to the deleting state. All update operations on a Job that is in deleting state will fail with status code 409 (Conflict), with additional information indicating that the Job is being deleted.

Parameters:

Returns:

public abstract Observable<>> deleteWithServiceResponseAsync(String jobId, JobDeleteOptions jobDeleteOptions)

Deletes a Job. Deleting a Job also deletes all Tasks that are part of that Job, and all Job statistics. This also overrides the retention period for Task data; that is, if the Job contains Tasks which are still retained on Compute Nodes, the Batch services deletes those Tasks' working directories and all their contents. When a Delete Job request is received, the Batch service sets the Job to the deleting state. All update operations on a Job that is in deleting state will fail with status code 409 (Conflict), with additional information indicating that the Job is being deleted.

Parameters:

Returns:

public abstract void disable(String jobId, DisableJobOption disableTasks)

Disables the specified Job, preventing new Tasks from running. The Batch Service immediately moves the Job to the disabling state. Batch then uses the disableTasks parameter to determine what to do with the currently running Tasks of the Job. The Job remains in the disabling state until the disable operation is completed and all Tasks have been dealt with according to the disableTasks option; the Job then moves to the disabled state. No new Tasks are started under the Job until it moves back to active state. If you try to disable a Job that is in any state other than active, disabling, or disabled, the request fails with status code 409.

Parameters:

public abstract void disable(String jobId, DisableJobOption disableTasks, JobDisableOptions jobDisableOptions)

Disables the specified Job, preventing new Tasks from running. The Batch Service immediately moves the Job to the disabling state. Batch then uses the disableTasks parameter to determine what to do with the currently running Tasks of the Job. The Job remains in the disabling state until the disable operation is completed and all Tasks have been dealt with according to the disableTasks option; the Job then moves to the disabled state. No new Tasks are started under the Job until it moves back to active state. If you try to disable a Job that is in any state other than active, disabling, or disabled, the request fails with status code 409.

Parameters:

public abstract Observable disableAsync(String jobId, DisableJobOption disableTasks)

Disables the specified Job, preventing new Tasks from running. The Batch Service immediately moves the Job to the disabling state. Batch then uses the disableTasks parameter to determine what to do with the currently running Tasks of the Job. The Job remains in the disabling state until the disable operation is completed and all Tasks have been dealt with according to the disableTasks option; the Job then moves to the disabled state. No new Tasks are started under the Job until it moves back to active state. If you try to disable a Job that is in any state other than active, disabling, or disabled, the request fails with status code 409.

Parameters:

Returns:

public abstract Observable disableAsync(String jobId, DisableJobOption disableTasks, JobDisableOptions jobDisableOptions)

Disables the specified Job, preventing new Tasks from running. The Batch Service immediately moves the Job to the disabling state. Batch then uses the disableTasks parameter to determine what to do with the currently running Tasks of the Job. The Job remains in the disabling state until the disable operation is completed and all Tasks have been dealt with according to the disableTasks option; the Job then moves to the disabled state. No new Tasks are started under the Job until it moves back to active state. If you try to disable a Job that is in any state other than active, disabling, or disabled, the request fails with status code 409.

Parameters:

Returns:

public abstract ServiceFuture disableAsync(String jobId, DisableJobOption disableTasks, JobDisableOptions jobDisableOptions, ServiceCallback serviceCallback)

Disables the specified Job, preventing new Tasks from running. The Batch Service immediately moves the Job to the disabling state. Batch then uses the disableTasks parameter to determine what to do with the currently running Tasks of the Job. The Job remains in the disabling state until the disable operation is completed and all Tasks have been dealt with according to the disableTasks option; the Job then moves to the disabled state. No new Tasks are started under the Job until it moves back to active state. If you try to disable a Job that is in any state other than active, disabling, or disabled, the request fails with status code 409.

Parameters:

Returns:

public abstract ServiceFuture disableAsync(String jobId, DisableJobOption disableTasks, ServiceCallback serviceCallback)

Disables the specified Job, preventing new Tasks from running. The Batch Service immediately moves the Job to the disabling state. Batch then uses the disableTasks parameter to determine what to do with the currently running Tasks of the Job. The Job remains in the disabling state until the disable operation is completed and all Tasks have been dealt with according to the disableTasks option; the Job then moves to the disabled state. No new Tasks are started under the Job until it moves back to active state. If you try to disable a Job that is in any state other than active, disabling, or disabled, the request fails with status code 409.

Parameters:

Returns:

public abstract Observable<>> disableWithServiceResponseAsync(String jobId, DisableJobOption disableTasks)

Disables the specified Job, preventing new Tasks from running. The Batch Service immediately moves the Job to the disabling state. Batch then uses the disableTasks parameter to determine what to do with the currently running Tasks of the Job. The Job remains in the disabling state until the disable operation is completed and all Tasks have been dealt with according to the disableTasks option; the Job then moves to the disabled state. No new Tasks are started under the Job until it moves back to active state. If you try to disable a Job that is in any state other than active, disabling, or disabled, the request fails with status code 409.

Parameters:

Returns:

public abstract Observable<>> disableWithServiceResponseAsync(String jobId, DisableJobOption disableTasks, JobDisableOptions jobDisableOptions)

Disables the specified Job, preventing new Tasks from running. The Batch Service immediately moves the Job to the disabling state. Batch then uses the disableTasks parameter to determine what to do with the currently running Tasks of the Job. The Job remains in the disabling state until the disable operation is completed and all Tasks have been dealt with according to the disableTasks option; the Job then moves to the disabled state. No new Tasks are started under the Job until it moves back to active state. If you try to disable a Job that is in any state other than active, disabling, or disabled, the request fails with status code 409.

Parameters:

Returns:

public abstract void enable(String jobId)

Enables the specified Job, allowing new Tasks to run. When you call this API, the Batch service sets a disabled Job to the enabling state. After the this operation is completed, the Job moves to the active state, and scheduling of new Tasks under the Job resumes. The Batch service does not allow a Task to remain in the active state for more than 180 days. Therefore, if you enable a Job containing active Tasks which were added more than 180 days ago, those Tasks will not run.

Parameters:

public abstract void enable(String jobId, JobEnableOptions jobEnableOptions)

Enables the specified Job, allowing new Tasks to run. When you call this API, the Batch service sets a disabled Job to the enabling state. After the this operation is completed, the Job moves to the active state, and scheduling of new Tasks under the Job resumes. The Batch service does not allow a Task to remain in the active state for more than 180 days. Therefore, if you enable a Job containing active Tasks which were added more than 180 days ago, those Tasks will not run.

Parameters:

public abstract Observable enableAsync(String jobId)

Enables the specified Job, allowing new Tasks to run. When you call this API, the Batch service sets a disabled Job to the enabling state. After the this operation is completed, the Job moves to the active state, and scheduling of new Tasks under the Job resumes. The Batch service does not allow a Task to remain in the active state for more than 180 days. Therefore, if you enable a Job containing active Tasks which were added more than 180 days ago, those Tasks will not run.

Parameters:

Returns:

public abstract Observable enableAsync(String jobId, JobEnableOptions jobEnableOptions)

Enables the specified Job, allowing new Tasks to run. When you call this API, the Batch service sets a disabled Job to the enabling state. After the this operation is completed, the Job moves to the active state, and scheduling of new Tasks under the Job resumes. The Batch service does not allow a Task to remain in the active state for more than 180 days. Therefore, if you enable a Job containing active Tasks which were added more than 180 days ago, those Tasks will not run.

Parameters:

Returns:

public abstract ServiceFuture enableAsync(String jobId, JobEnableOptions jobEnableOptions, ServiceCallback serviceCallback)

Enables the specified Job, allowing new Tasks to run. When you call this API, the Batch service sets a disabled Job to the enabling state. After the this operation is completed, the Job moves to the active state, and scheduling of new Tasks under the Job resumes. The Batch service does not allow a Task to remain in the active state for more than 180 days. Therefore, if you enable a Job containing active Tasks which were added more than 180 days ago, those Tasks will not run.

Parameters:

Returns:

public abstract ServiceFuture enableAsync(String jobId, ServiceCallback serviceCallback)

Enables the specified Job, allowing new Tasks to run. When you call this API, the Batch service sets a disabled Job to the enabling state. After the this operation is completed, the Job moves to the active state, and scheduling of new Tasks under the Job resumes. The Batch service does not allow a Task to remain in the active state for more than 180 days. Therefore, if you enable a Job containing active Tasks which were added more than 180 days ago, those Tasks will not run.

Parameters:

Returns:

public abstract Observable<>> enableWithServiceResponseAsync(String jobId)

Enables the specified Job, allowing new Tasks to run. When you call this API, the Batch service sets a disabled Job to the enabling state. After the this operation is completed, the Job moves to the active state, and scheduling of new Tasks under the Job resumes. The Batch service does not allow a Task to remain in the active state for more than 180 days. Therefore, if you enable a Job containing active Tasks which were added more than 180 days ago, those Tasks will not run.

Parameters:

Returns:

public abstract Observable<>> enableWithServiceResponseAsync(String jobId, JobEnableOptions jobEnableOptions)

Enables the specified Job, allowing new Tasks to run. When you call this API, the Batch service sets a disabled Job to the enabling state. After the this operation is completed, the Job moves to the active state, and scheduling of new Tasks under the Job resumes. The Batch service does not allow a Task to remain in the active state for more than 180 days. Therefore, if you enable a Job containing active Tasks which were added more than 180 days ago, those Tasks will not run.

Parameters:

Returns:

public abstract CloudJob get(String jobId)

Gets information about the specified Job.

Parameters:

Returns:

public abstract CloudJob get(String jobId, JobGetOptions jobGetOptions)

Gets information about the specified Job.

Parameters:

Returns:

public abstract Observable getAsync(String jobId)

Gets information about the specified Job.

Parameters:

Returns:

public abstract Observable getAsync(String jobId, JobGetOptions jobGetOptions)

Gets information about the specified Job.

Parameters:

Returns:

public abstract ServiceFuture getAsync(String jobId, JobGetOptions jobGetOptions, ServiceCallback serviceCallback)

Gets information about the specified Job.

Parameters:

Returns:

public abstract ServiceFuture getAsync(String jobId, ServiceCallback serviceCallback)

Gets information about the specified Job.

Parameters:

Returns:

public abstract TaskCountsResult getTaskCounts(String jobId)

Gets the Task counts for the specified Job. Task counts provide a count of the Tasks by active, running or completed Task state, and a count of Tasks which succeeded or failed. Tasks in the preparing state are counted as running. Note that the numbers returned may not always be up to date. If you need exact task counts, use a list query.

Parameters:

Returns:

public abstract TaskCountsResult getTaskCounts(String jobId, JobGetTaskCountsOptions jobGetTaskCountsOptions)

Gets the Task counts for the specified Job. Task counts provide a count of the Tasks by active, running or completed Task state, and a count of Tasks which succeeded or failed. Tasks in the preparing state are counted as running. Note that the numbers returned may not always be up to date. If you need exact task counts, use a list query.

Parameters:

Returns:

public abstract Observable getTaskCountsAsync(String jobId)

Gets the Task counts for the specified Job. Task counts provide a count of the Tasks by active, running or completed Task state, and a count of Tasks which succeeded or failed. Tasks in the preparing state are counted as running. Note that the numbers returned may not always be up to date. If you need exact task counts, use a list query.

Parameters:

Returns:

public abstract Observable getTaskCountsAsync(String jobId, JobGetTaskCountsOptions jobGetTaskCountsOptions)

Gets the Task counts for the specified Job. Task counts provide a count of the Tasks by active, running or completed Task state, and a count of Tasks which succeeded or failed. Tasks in the preparing state are counted as running. Note that the numbers returned may not always be up to date. If you need exact task counts, use a list query.

Parameters:

Returns:

public abstract ServiceFuture getTaskCountsAsync(String jobId, JobGetTaskCountsOptions jobGetTaskCountsOptions, ServiceCallback serviceCallback)

Gets the Task counts for the specified Job. Task counts provide a count of the Tasks by active, running or completed Task state, and a count of Tasks which succeeded or failed. Tasks in the preparing state are counted as running. Note that the numbers returned may not always be up to date. If you need exact task counts, use a list query.

Parameters:

Returns:

public abstract ServiceFuture getTaskCountsAsync(String jobId, ServiceCallback serviceCallback)

Gets the Task counts for the specified Job. Task counts provide a count of the Tasks by active, running or completed Task state, and a count of Tasks which succeeded or failed. Tasks in the preparing state are counted as running. Note that the numbers returned may not always be up to date. If you need exact task counts, use a list query.

Parameters:

Returns:

public abstract Observable<>> getTaskCountsWithServiceResponseAsync(String jobId)

Gets the Task counts for the specified Job. Task counts provide a count of the Tasks by active, running or completed Task state, and a count of Tasks which succeeded or failed. Tasks in the preparing state are counted as running. Note that the numbers returned may not always be up to date. If you need exact task counts, use a list query.

Parameters:

Returns:

public abstract Observable<>> getTaskCountsWithServiceResponseAsync(String jobId, JobGetTaskCountsOptions jobGetTaskCountsOptions)

Gets the Task counts for the specified Job. Task counts provide a count of the Tasks by active, running or completed Task state, and a count of Tasks which succeeded or failed. Tasks in the preparing state are counted as running. Note that the numbers returned may not always be up to date. If you need exact task counts, use a list query.

Parameters:

Returns:

public abstract Observable<>> getWithServiceResponseAsync(String jobId)

Gets information about the specified Job.

Parameters:

Returns:

public abstract Observable<>> getWithServiceResponseAsync(String jobId, JobGetOptions jobGetOptions)

Gets information about the specified Job.

Parameters:

Returns:

public abstract PagedList list()

Lists all of the Jobs in the specified Account.

Returns:

public abstract PagedList list(JobListOptions jobListOptions)

Lists all of the Jobs in the specified Account.

Parameters:

Returns:

public abstract Observable<>> listAsync()

Lists all of the Jobs in the specified Account.

Returns:

public abstract ServiceFuture<>> listAsync(ListOperationCallback serviceCallback)

Lists all of the Jobs in the specified Account.

Parameters:

Returns:

public abstract Observable<>> listAsync(JobListOptions jobListOptions)

Lists all of the Jobs in the specified Account.

Parameters:

Returns:

public abstract ServiceFuture<>> listAsync(JobListOptions jobListOptions, ListOperationCallback serviceCallback)

Lists all of the Jobs in the specified Account.

Parameters:

Returns:

public abstract PagedList listFromJobSchedule(String jobScheduleId)

Lists the Jobs that have been created under the specified Job Schedule.

Parameters:

Returns:

public abstract PagedList listFromJobSchedule(String jobScheduleId, JobListFromJobScheduleOptions jobListFromJobScheduleOptions)

Lists the Jobs that have been created under the specified Job Schedule.

Parameters:

Returns:

public abstract Observable<>> listFromJobScheduleAsync(String jobScheduleId)

Lists the Jobs that have been created under the specified Job Schedule.

Parameters:

Returns:

public abstract ServiceFuture<>> listFromJobScheduleAsync(String jobScheduleId, ListOperationCallback serviceCallback)

Lists the Jobs that have been created under the specified Job Schedule.

Parameters:

Returns:

public abstract Observable<>> listFromJobScheduleAsync(String jobScheduleId, JobListFromJobScheduleOptions jobListFromJobScheduleOptions)

Lists the Jobs that have been created under the specified Job Schedule.

Parameters:

Returns:

public abstract ServiceFuture<>> listFromJobScheduleAsync(String jobScheduleId, JobListFromJobScheduleOptions jobListFromJobScheduleOptions, ListOperationCallback serviceCallback)

Lists the Jobs that have been created under the specified Job Schedule.

Parameters:

Returns:

public abstract PagedList listFromJobScheduleNext(String nextPageLink)

Lists the Jobs that have been created under the specified Job Schedule.

Parameters:

Returns:

public abstract PagedList listFromJobScheduleNext(String nextPageLink, JobListFromJobScheduleNextOptions jobListFromJobScheduleNextOptions)

Lists the Jobs that have been created under the specified Job Schedule.

Parameters:

Returns:

public abstract Observable<>> listFromJobScheduleNextAsync(String nextPageLink)

Lists the Jobs that have been created under the specified Job Schedule.

Parameters:

Returns:

public abstract Observable<>> listFromJobScheduleNextAsync(String nextPageLink, JobListFromJobScheduleNextOptions jobListFromJobScheduleNextOptions)

Lists the Jobs that have been created under the specified Job Schedule.

Parameters:

Returns:

public abstract ServiceFuture<>> listFromJobScheduleNextAsync(String nextPageLink, JobListFromJobScheduleNextOptions jobListFromJobScheduleNextOptions, ServiceFuture<>> serviceFuture, ListOperationCallback serviceCallback)

Lists the Jobs that have been created under the specified Job Schedule.

Parameters:

Returns:

public abstract ServiceFuture<>> listFromJobScheduleNextAsync(String nextPageLink, ServiceFuture<>> serviceFuture, ListOperationCallback serviceCallback)

Lists the Jobs that have been created under the specified Job Schedule.

Parameters:

Returns:

public abstract Observable<><>,JobListFromJobScheduleHeaders>> listFromJobScheduleNextWithServiceResponseAsync(String nextPageLink)

Lists the Jobs that have been created under the specified Job Schedule.

Parameters:

Returns:

public abstract Observable<><>,JobListFromJobScheduleHeaders>> listFromJobScheduleNextWithServiceResponseAsync(String nextPageLink, JobListFromJobScheduleNextOptions jobListFromJobScheduleNextOptions)

Lists the Jobs that have been created under the specified Job Schedule.

Parameters:

Returns:

public abstract Observable<><>,JobListFromJobScheduleHeaders>> listFromJobScheduleWithServiceResponseAsync(String jobScheduleId)

Lists the Jobs that have been created under the specified Job Schedule.

Parameters:

Returns:

public abstract Observable<><>,JobListFromJobScheduleHeaders>> listFromJobScheduleWithServiceResponseAsync(String jobScheduleId, JobListFromJobScheduleOptions jobListFromJobScheduleOptions)

Lists the Jobs that have been created under the specified Job Schedule.

Parameters:

Returns:

public abstract PagedList listNext(String nextPageLink)

Lists all of the Jobs in the specified Account.

Parameters:

Returns:

public abstract PagedList listNext(String nextPageLink, JobListNextOptions jobListNextOptions)

Lists all of the Jobs in the specified Account.

Parameters:

Returns:

public abstract Observable<>> listNextAsync(String nextPageLink)

Lists all of the Jobs in the specified Account.

Parameters:

Returns:

public abstract Observable<>> listNextAsync(String nextPageLink, JobListNextOptions jobListNextOptions)

Lists all of the Jobs in the specified Account.

Parameters:

Returns:

public abstract ServiceFuture<>> listNextAsync(String nextPageLink, JobListNextOptions jobListNextOptions, ServiceFuture<>> serviceFuture, ListOperationCallback serviceCallback)

Lists all of the Jobs in the specified Account.

Parameters:

Returns:

public abstract ServiceFuture<>> listNextAsync(String nextPageLink, ServiceFuture<>> serviceFuture, ListOperationCallback serviceCallback)

Lists all of the Jobs in the specified Account.

Parameters:

Returns:

public abstract Observable<><>,JobListHeaders>> listNextWithServiceResponseAsync(String nextPageLink)

Lists all of the Jobs in the specified Account.

Parameters:

Returns:

public abstract Observable<><>,JobListHeaders>> listNextWithServiceResponseAsync(String nextPageLink, JobListNextOptions jobListNextOptions)

Lists all of the Jobs in the specified Account.

Parameters:

Returns:

public abstract PagedList listPreparationAndReleaseTaskStatus(String jobId)

Lists the execution status of the Job Preparation and Job Release Task for the specified Job across the Compute Nodes where the Job has run. This API returns the Job Preparation and Job Release Task status on all Compute Nodes that have run the Job Preparation or Job Release Task. This includes Compute Nodes which have since been removed from the Pool. If this API is invoked on a Job which has no Job Preparation or Job Release Task, the Batch service returns HTTP status code 409 (Conflict) with an error code of JobPreparationTaskNotSpecified.

Parameters:

Returns:

public abstract PagedList listPreparationAndReleaseTaskStatus(String jobId, JobListPreparationAndReleaseTaskStatusOptions jobListPreparationAndReleaseTaskStatusOptions)

Lists the execution status of the Job Preparation and Job Release Task for the specified Job across the Compute Nodes where the Job has run. This API returns the Job Preparation and Job Release Task status on all Compute Nodes that have run the Job Preparation or Job Release Task. This includes Compute Nodes which have since been removed from the Pool. If this API is invoked on a Job which has no Job Preparation or Job Release Task, the Batch service returns HTTP status code 409 (Conflict) with an error code of JobPreparationTaskNotSpecified.

Parameters:

Returns:

public abstract Observable<>> listPreparationAndReleaseTaskStatusAsync(String jobId)

Lists the execution status of the Job Preparation and Job Release Task for the specified Job across the Compute Nodes where the Job has run. This API returns the Job Preparation and Job Release Task status on all Compute Nodes that have run the Job Preparation or Job Release Task. This includes Compute Nodes which have since been removed from the Pool. If this API is invoked on a Job which has no Job Preparation or Job Release Task, the Batch service returns HTTP status code 409 (Conflict) with an error code of JobPreparationTaskNotSpecified.

Parameters:

Returns:

public abstract ServiceFuture<>> listPreparationAndReleaseTaskStatusAsync(String jobId, ListOperationCallback serviceCallback)

Lists the execution status of the Job Preparation and Job Release Task for the specified Job across the Compute Nodes where the Job has run. This API returns the Job Preparation and Job Release Task status on all Compute Nodes that have run the Job Preparation or Job Release Task. This includes Compute Nodes which have since been removed from the Pool. If this API is invoked on a Job which has no Job Preparation or Job Release Task, the Batch service returns HTTP status code 409 (Conflict) with an error code of JobPreparationTaskNotSpecified.

Parameters:

Returns:

public abstract Observable<>> listPreparationAndReleaseTaskStatusAsync(String jobId, JobListPreparationAndReleaseTaskStatusOptions jobListPreparationAndReleaseTaskStatusOptions)

Lists the execution status of the Job Preparation and Job Release Task for the specified Job across the Compute Nodes where the Job has run. This API returns the Job Preparation and Job Release Task status on all Compute Nodes that have run the Job Preparation or Job Release Task. This includes Compute Nodes which have since been removed from the Pool. If this API is invoked on a Job which has no Job Preparation or Job Release Task, the Batch service returns HTTP status code 409 (Conflict) with an error code of JobPreparationTaskNotSpecified.

Parameters:

Returns:

public abstract ServiceFuture<>> listPreparationAndReleaseTaskStatusAsync(String jobId, JobListPreparationAndReleaseTaskStatusOptions jobListPreparationAndReleaseTaskStatusOptions, ListOperationCallback serviceCallback)

Lists the execution status of the Job Preparation and Job Release Task for the specified Job across the Compute Nodes where the Job has run. This API returns the Job Preparation and Job Release Task status on all Compute Nodes that have run the Job Preparation or Job Release Task. This includes Compute Nodes which have since been removed from the Pool. If this API is invoked on a Job which has no Job Preparation or Job Release Task, the Batch service returns HTTP status code 409 (Conflict) with an error code of JobPreparationTaskNotSpecified.

Parameters:

Returns:

public abstract PagedList listPreparationAndReleaseTaskStatusNext(String nextPageLink)

Lists the execution status of the Job Preparation and Job Release Task for the specified Job across the Compute Nodes where the Job has run. This API returns the Job Preparation and Job Release Task status on all Compute Nodes that have run the Job Preparation or Job Release Task. This includes Compute Nodes which have since been removed from the Pool. If this API is invoked on a Job which has no Job Preparation or Job Release Task, the Batch service returns HTTP status code 409 (Conflict) with an error code of JobPreparationTaskNotSpecified.

Parameters:

Returns:

public abstract PagedList listPreparationAndReleaseTaskStatusNext(String nextPageLink, JobListPreparationAndReleaseTaskStatusNextOptions jobListPreparationAndReleaseTaskStatusNextOptions)

Lists the execution status of the Job Preparation and Job Release Task for the specified Job across the Compute Nodes where the Job has run. This API returns the Job Preparation and Job Release Task status on all Compute Nodes that have run the Job Preparation or Job Release Task. This includes Compute Nodes which have since been removed from the Pool. If this API is invoked on a Job which has no Job Preparation or Job Release Task, the Batch service returns HTTP status code 409 (Conflict) with an error code of JobPreparationTaskNotSpecified.

Parameters:

Returns:

public abstract Observable<>> listPreparationAndReleaseTaskStatusNextAsync(String nextPageLink)

Lists the execution status of the Job Preparation and Job Release Task for the specified Job across the Compute Nodes where the Job has run. This API returns the Job Preparation and Job Release Task status on all Compute Nodes that have run the Job Preparation or Job Release Task. This includes Compute Nodes which have since been removed from the Pool. If this API is invoked on a Job which has no Job Preparation or Job Release Task, the Batch service returns HTTP status code 409 (Conflict) with an error code of JobPreparationTaskNotSpecified.

Parameters:

Returns:

public abstract Observable<>> listPreparationAndReleaseTaskStatusNextAsync(String nextPageLink, JobListPreparationAndReleaseTaskStatusNextOptions jobListPreparationAndReleaseTaskStatusNextOptions)

Lists the execution status of the Job Preparation and Job Release Task for the specified Job across the Compute Nodes where the Job has run. This API returns the Job Preparation and Job Release Task status on all Compute Nodes that have run the Job Preparation or Job Release Task. This includes Compute Nodes which have since been removed from the Pool. If this API is invoked on a Job which has no Job Preparation or Job Release Task, the Batch service returns HTTP status code 409 (Conflict) with an error code of JobPreparationTaskNotSpecified.

Parameters:

Returns:

public abstract ServiceFuture<>> listPreparationAndReleaseTaskStatusNextAsync(String nextPageLink, JobListPreparationAndReleaseTaskStatusNextOptions jobListPreparationAndReleaseTaskStatusNextOptions, ServiceFuture<>> serviceFuture, ListOperationCallback serviceCallback)

Lists the execution status of the Job Preparation and Job Release Task for the specified Job across the Compute Nodes where the Job has run. This API returns the Job Preparation and Job Release Task status on all Compute Nodes that have run the Job Preparation or Job Release Task. This includes Compute Nodes which have since been removed from the Pool. If this API is invoked on a Job which has no Job Preparation or Job Release Task, the Batch service returns HTTP status code 409 (Conflict) with an error code of JobPreparationTaskNotSpecified.

Parameters:

Returns:

public abstract ServiceFuture<>> listPreparationAndReleaseTaskStatusNextAsync(String nextPageLink, ServiceFuture<>> serviceFuture, ListOperationCallback serviceCallback)

Lists the execution status of the Job Preparation and Job Release Task for the specified Job across the Compute Nodes where the Job has run. This API returns the Job Preparation and Job Release Task status on all Compute Nodes that have run the Job Preparation or Job Release Task. This includes Compute Nodes which have since been removed from the Pool. If this API is invoked on a Job which has no Job Preparation or Job Release Task, the Batch service returns HTTP status code 409 (Conflict) with an error code of JobPreparationTaskNotSpecified.

Parameters:

Returns:

public abstract Observable<><>,JobListPreparationAndReleaseTaskStatusHeaders>> listPreparationAndReleaseTaskStatusNextWithServiceResponseAsync(String nextPageLink)

Lists the execution status of the Job Preparation and Job Release Task for the specified Job across the Compute Nodes where the Job has run. This API returns the Job Preparation and Job Release Task status on all Compute Nodes that have run the Job Preparation or Job Release Task. This includes Compute Nodes which have since been removed from the Pool. If this API is invoked on a Job which has no Job Preparation or Job Release Task, the Batch service returns HTTP status code 409 (Conflict) with an error code of JobPreparationTaskNotSpecified.

Parameters:

Returns:

public abstract Observable<><>,JobListPreparationAndReleaseTaskStatusHeaders>> listPreparationAndReleaseTaskStatusNextWithServiceResponseAsync(String nextPageLink, JobListPreparationAndReleaseTaskStatusNextOptions jobListPreparationAndReleaseTaskStatusNextOptions)

Lists the execution status of the Job Preparation and Job Release Task for the specified Job across the Compute Nodes where the Job has run. This API returns the Job Preparation and Job Release Task status on all Compute Nodes that have run the Job Preparation or Job Release Task. This includes Compute Nodes which have since been removed from the Pool. If this API is invoked on a Job which has no Job Preparation or Job Release Task, the Batch service returns HTTP status code 409 (Conflict) with an error code of JobPreparationTaskNotSpecified.

Parameters:

Returns:

public abstract Observable<><>,JobListPreparationAndReleaseTaskStatusHeaders>> listPreparationAndReleaseTaskStatusWithServiceResponseAsync(String jobId)

Lists the execution status of the Job Preparation and Job Release Task for the specified Job across the Compute Nodes where the Job has run. This API returns the Job Preparation and Job Release Task status on all Compute Nodes that have run the Job Preparation or Job Release Task. This includes Compute Nodes which have since been removed from the Pool. If this API is invoked on a Job which has no Job Preparation or Job Release Task, the Batch service returns HTTP status code 409 (Conflict) with an error code of JobPreparationTaskNotSpecified.

Parameters:

Returns:

public abstract Observable<><>,JobListPreparationAndReleaseTaskStatusHeaders>> listPreparationAndReleaseTaskStatusWithServiceResponseAsync(String jobId, JobListPreparationAndReleaseTaskStatusOptions jobListPreparationAndReleaseTaskStatusOptions)

Lists the execution status of the Job Preparation and Job Release Task for the specified Job across the Compute Nodes where the Job has run. This API returns the Job Preparation and Job Release Task status on all Compute Nodes that have run the Job Preparation or Job Release Task. This includes Compute Nodes which have since been removed from the Pool. If this API is invoked on a Job which has no Job Preparation or Job Release Task, the Batch service returns HTTP status code 409 (Conflict) with an error code of JobPreparationTaskNotSpecified.

Parameters:

Returns:

public abstract Observable<><>,JobListHeaders>> listWithServiceResponseAsync()

Lists all of the Jobs in the specified Account.

Returns:

public abstract Observable<><>,JobListHeaders>> listWithServiceResponseAsync(JobListOptions jobListOptions)

Lists all of the Jobs in the specified Account.

Parameters:

Returns:

public abstract void patch(String jobId, JobPatchParameter jobPatchParameter)

Updates the properties of the specified Job. This replaces only the Job properties specified in the request. For example, if the Job has constraints, and a request does not specify the constraints element, then the Job keeps the existing constraints.

Parameters:

public abstract void patch(String jobId, JobPatchParameter jobPatchParameter, JobPatchOptions jobPatchOptions)

Updates the properties of the specified Job. This replaces only the Job properties specified in the request. For example, if the Job has constraints, and a request does not specify the constraints element, then the Job keeps the existing constraints.

Parameters:

public abstract Observable patchAsync(String jobId, JobPatchParameter jobPatchParameter)

Updates the properties of the specified Job. This replaces only the Job properties specified in the request. For example, if the Job has constraints, and a request does not specify the constraints element, then the Job keeps the existing constraints.

Parameters:

Returns:

public abstract Observable patchAsync(String jobId, JobPatchParameter jobPatchParameter, JobPatchOptions jobPatchOptions)

Updates the properties of the specified Job. This replaces only the Job properties specified in the request. For example, if the Job has constraints, and a request does not specify the constraints element, then the Job keeps the existing constraints.

Parameters:

Returns:

public abstract ServiceFuture patchAsync(String jobId, JobPatchParameter jobPatchParameter, JobPatchOptions jobPatchOptions, ServiceCallback serviceCallback)

Updates the properties of the specified Job. This replaces only the Job properties specified in the request. For example, if the Job has constraints, and a request does not specify the constraints element, then the Job keeps the existing constraints.

Parameters:

Returns:

public abstract ServiceFuture patchAsync(String jobId, JobPatchParameter jobPatchParameter, ServiceCallback serviceCallback)

Updates the properties of the specified Job. This replaces only the Job properties specified in the request. For example, if the Job has constraints, and a request does not specify the constraints element, then the Job keeps the existing constraints.

Parameters:

Returns:

public abstract Observable<>> patchWithServiceResponseAsync(String jobId, JobPatchParameter jobPatchParameter)

Updates the properties of the specified Job. This replaces only the Job properties specified in the request. For example, if the Job has constraints, and a request does not specify the constraints element, then the Job keeps the existing constraints.

Parameters:

Returns:

public abstract Observable<>> patchWithServiceResponseAsync(String jobId, JobPatchParameter jobPatchParameter, JobPatchOptions jobPatchOptions)

Updates the properties of the specified Job. This replaces only the Job properties specified in the request. For example, if the Job has constraints, and a request does not specify the constraints element, then the Job keeps the existing constraints.

Parameters:

Returns:

public abstract void terminate(String jobId)

Terminates the specified Job, marking it as completed. When a Terminate Job request is received, the Batch service sets the Job to the terminating state. The Batch service then terminates any running Tasks associated with the Job and runs any required Job release Tasks. Then the Job moves into the completed state. If there are any Tasks in the Job in the active state, they will remain in the active state. Once a Job is terminated, new Tasks cannot be added and any remaining active Tasks will not be scheduled.

Parameters:

public abstract void terminate(String jobId, String terminateReason, JobTerminateOptions jobTerminateOptions)

Terminates the specified Job, marking it as completed. When a Terminate Job request is received, the Batch service sets the Job to the terminating state. The Batch service then terminates any running Tasks associated with the Job and runs any required Job release Tasks. Then the Job moves into the completed state. If there are any Tasks in the Job in the active state, they will remain in the active state. Once a Job is terminated, new Tasks cannot be added and any remaining active Tasks will not be scheduled.

Parameters:

public abstract Observable terminateAsync(String jobId)

Terminates the specified Job, marking it as completed. When a Terminate Job request is received, the Batch service sets the Job to the terminating state. The Batch service then terminates any running Tasks associated with the Job and runs any required Job release Tasks. Then the Job moves into the completed state. If there are any Tasks in the Job in the active state, they will remain in the active state. Once a Job is terminated, new Tasks cannot be added and any remaining active Tasks will not be scheduled.

Parameters:

Returns:

public abstract ServiceFuture terminateAsync(String jobId, ServiceCallback serviceCallback)

Terminates the specified Job, marking it as completed. When a Terminate Job request is received, the Batch service sets the Job to the terminating state. The Batch service then terminates any running Tasks associated with the Job and runs any required Job release Tasks. Then the Job moves into the completed state. If there are any Tasks in the Job in the active state, they will remain in the active state. Once a Job is terminated, new Tasks cannot be added and any remaining active Tasks will not be scheduled.

Parameters:

Returns:

public abstract Observable terminateAsync(String jobId, String terminateReason, JobTerminateOptions jobTerminateOptions)

Terminates the specified Job, marking it as completed. When a Terminate Job request is received, the Batch service sets the Job to the terminating state. The Batch service then terminates any running Tasks associated with the Job and runs any required Job release Tasks. Then the Job moves into the completed state. If there are any Tasks in the Job in the active state, they will remain in the active state. Once a Job is terminated, new Tasks cannot be added and any remaining active Tasks will not be scheduled.

Parameters:

Returns:

public abstract ServiceFuture terminateAsync(String jobId, String terminateReason, JobTerminateOptions jobTerminateOptions, ServiceCallback serviceCallback)

Terminates the specified Job, marking it as completed. When a Terminate Job request is received, the Batch service sets the Job to the terminating state. The Batch service then terminates any running Tasks associated with the Job and runs any required Job release Tasks. Then the Job moves into the completed state. If there are any Tasks in the Job in the active state, they will remain in the active state. Once a Job is terminated, new Tasks cannot be added and any remaining active Tasks will not be scheduled.

Parameters:

Returns:

public abstract Observable<>> terminateWithServiceResponseAsync(String jobId)

Terminates the specified Job, marking it as completed. When a Terminate Job request is received, the Batch service sets the Job to the terminating state. The Batch service then terminates any running Tasks associated with the Job and runs any required Job release Tasks. Then the Job moves into the completed state. If there are any Tasks in the Job in the active state, they will remain in the active state. Once a Job is terminated, new Tasks cannot be added and any remaining active Tasks will not be scheduled.

Parameters:

Returns:

public abstract Observable<>> terminateWithServiceResponseAsync(String jobId, String terminateReason, JobTerminateOptions jobTerminateOptions)

Terminates the specified Job, marking it as completed. When a Terminate Job request is received, the Batch service sets the Job to the terminating state. The Batch service then terminates any running Tasks associated with the Job and runs any required Job release Tasks. Then the Job moves into the completed state. If there are any Tasks in the Job in the active state, they will remain in the active state. Once a Job is terminated, new Tasks cannot be added and any remaining active Tasks will not be scheduled.

Parameters:

Returns:

public abstract void update(String jobId, JobUpdateParameter jobUpdateParameter)

Updates the properties of the specified Job. This fully replaces all the updatable properties of the Job. For example, if the Job has constraints associated with it and if constraints is not specified with this request, then the Batch service will remove the existing constraints.

Parameters:

public abstract void update(String jobId, JobUpdateParameter jobUpdateParameter, JobUpdateOptions jobUpdateOptions)

Updates the properties of the specified Job. This fully replaces all the updatable properties of the Job. For example, if the Job has constraints associated with it and if constraints is not specified with this request, then the Batch service will remove the existing constraints.

Parameters:

public abstract Observable updateAsync(String jobId, JobUpdateParameter jobUpdateParameter)

Updates the properties of the specified Job. This fully replaces all the updatable properties of the Job. For example, if the Job has constraints associated with it and if constraints is not specified with this request, then the Batch service will remove the existing constraints.

Parameters:

Returns:

public abstract Observable updateAsync(String jobId, JobUpdateParameter jobUpdateParameter, JobUpdateOptions jobUpdateOptions)

Updates the properties of the specified Job. This fully replaces all the updatable properties of the Job. For example, if the Job has constraints associated with it and if constraints is not specified with this request, then the Batch service will remove the existing constraints.

Parameters:

Returns:

public abstract ServiceFuture updateAsync(String jobId, JobUpdateParameter jobUpdateParameter, JobUpdateOptions jobUpdateOptions, ServiceCallback serviceCallback)

Updates the properties of the specified Job. This fully replaces all the updatable properties of the Job. For example, if the Job has constraints associated with it and if constraints is not specified with this request, then the Batch service will remove the existing constraints.

Parameters:

Returns:

public abstract ServiceFuture updateAsync(String jobId, JobUpdateParameter jobUpdateParameter, ServiceCallback serviceCallback)

Updates the properties of the specified Job. This fully replaces all the updatable properties of the Job. For example, if the Job has constraints associated with it and if constraints is not specified with this request, then the Batch service will remove the existing constraints.

Parameters:

Returns:

public abstract Observable<>> updateWithServiceResponseAsync(String jobId, JobUpdateParameter jobUpdateParameter)

Updates the properties of the specified Job. This fully replaces all the updatable properties of the Job. For example, if the Job has constraints associated with it and if constraints is not specified with this request, then the Batch service will remove the existing constraints.

Parameters:

Returns:

public abstract Observable<>> updateWithServiceResponseAsync(String jobId, JobUpdateParameter jobUpdateParameter, JobUpdateOptions jobUpdateOptions)

Updates the properties of the specified Job. This fully replaces all the updatable properties of the Job. For example, if the Job has constraints associated with it and if constraints is not specified with this request, then the Batch service will remove the existing constraints.

Parameters:

Returns: