Initializing help system before first use

# insightapi2~create_compute_job

Purpose
Create a compute job. The job request can supply a zip containing files, specify a dependency on an existing zip file, or both.
Synopsis
`function create_compute_job(client:insightapi2~insightconfig, req:insightapi2~httprequest, resp:insightapi2~httpresponse):insightapi2~compute_job`
`function create_compute_job(client:insightapi2~insightconfig, compute_job_request:insightapi2~compute_job_request, payload:insightapi2~file_data, resp:insightapi2~httpresponse):insightapi2~compute_job`
`function create_compute_job(client:insightapi2~insightconfig, compute_job_request:insightapi2~compute_job_request, payload:insightapi2~file_data):insightapi2~compute_job`
Arguments

client | An initialized insightapi2~insightconfig to call
req | An initialized insightapi2~httprequest record. The params field may contain these indexes:
computeJobRequest |
payload | (a insightapi2~file_data value)
compute_job_request | A insightapi2~compute_job_request value
payload | A record describing the file to upload
resp | A insightapi2~httpresponse record into which will be written a description of the response

Return value
The response body of the request, if it was of type insightapi2~compute_job
Further information
1. Use the status field of the resp record to distinguish between different status codes returned by the operation, or the success attribute to check for 2xx status codes. If the resp record is not passed to this function, the model will abort with a runtime error if the response's status code does not indicate success. The expected responses from this operation are:

HTTP Status Code | Response body type | Description
--- | --- | ---
201 | insightapi2~compute_job | The initial compute execution status
403 |  | The user did not have authority to create the compute job, or did not have authority to execute the compute job on the execution service
409 | insightapi2~error_response | A compute job already exists with this identifier
413 | insightapi2~error_response | The compute job payload file was too large
422 | insightapi2~error_response | The request was invalid
429 | insightapi2~error_response | Too many jobs are queued

2. If the response body could be read into a Mosel variable, it would be written to the body field of the resp record (and also returned from this function if it was a insightapi2~compute_job), and the bodyfilename field of the resp record will be an empty string.
3. If the bodyfilename field of the resp record is set to a non-empty value on return, this will be a file containing the response body; the caller is responsible for deleting this file when it is no longer required.
Related topics
insightapi2~compute_job
insightapi2~compute_job_request
insightapi2~error_response
insightapi2~file_data
insightapi2~insightconfig
insightapi2~httprequest
insightapi2~httpresponse
Parent Topic ComputeJobs Operations

© 2001-2026 Fair Isaac Corporation. All rights reserved. This documentation is the property of Fair Isaac Corporation (“FICO”). Receipt or possession of this documentation does not convey rights to disclose, reproduce, make derivative works, use, or allow others to use it except solely for internal evaluation purposes to determine whether to purchase a license to the software described in this documentation, or as otherwise set forth in a written software license agreement between you and FICO (or a FICO affiliate). Use of this documentation and the software described in it must conform strictly to the foregoing permitted uses, and no other use is permitted.