/AWS1/IF_OMX=>STARTRUN()
¶
About StartRun¶
Starts a new run and returns details about the run, or duplicates an existing run. A run is a single invocation of a workflow. If you provide request IDs, Amazon Web Services HealthOmics identifies duplicate requests and starts the run only once. Monitor the progress of the run by calling the GetRun
API operation.
To start a new run, the following inputs are required:
-
A service role ARN (
roleArn
). -
The run's workflow ID (
workflowId
, not theuuid
orrunId
). -
An Amazon S3 location (
outputUri
) where the run outputs will be saved. -
All required workflow parameters (
parameter
), which can include optional parameters from the parameter template. The run cannot include any parameters that are not defined in the parameter template. To see all possible parameters, use theGetRun
API operation. -
For runs with a
STATIC
(default) storage type, specify the required storage capacity (in gibibytes). A storage capacity value is not required for runs that useDYNAMIC
storage.
StartRun
can also duplicate an existing run using the run's default values. You can modify these default values and/or add other optional inputs. To duplicate a run, the following inputs are required:
-
A service role ARN (
roleArn
). -
The ID of the run to duplicate (
runId
). -
An Amazon S3 location where the run outputs will be saved (
outputUri
).
To learn more about the optional parameters for StartRun
, see Starting a run in the Amazon Web Services HealthOmics User Guide.
Use the retentionMode
input to control how long the metadata for each run is stored in CloudWatch. There are two retention modes:
-
Specify
REMOVE
to automatically remove the oldest runs when you reach the maximum service retention limit for runs. It is recommended that you use theREMOVE
mode to initiate major run requests so that your runs do not fail when you reach the limit. -
The
retentionMode
is set to theRETAIN
mode by default, which allows you to manually remove runs after reaching the maximum service retention limit. Under this setting, you cannot create additional runs until you remove the excess runs.
To learn more about the retention modes, see Run retention mode in the Amazon Web Services HealthOmics User Guide.
Method Signature¶
IMPORTING¶
Required arguments:¶
iv_rolearn
TYPE /AWS1/OMXRUNROLEARN
/AWS1/OMXRUNROLEARN
¶
A service role for the run. The
roleArn
requires access to Amazon Web Services HealthOmics, S3, Cloudwatch logs, and EC2. An exampleroleArn
isarn:aws:iam::123456789012:role/omics-service-role-serviceRole-W8O1XMPL7QZ
. In this example, the AWS account ID is123456789012
and the role name isomics-service-role-serviceRole-W8O1XMPL7QZ
.
iv_requestid
TYPE /AWS1/OMXRUNREQUESTID
/AWS1/OMXRUNREQUESTID
¶
An idempotency token used to dedupe retry requests so that duplicate runs are not created.
Optional arguments:¶
iv_workflowid
TYPE /AWS1/OMXWORKFLOWID
/AWS1/OMXWORKFLOWID
¶
The run's workflow ID. The
workflowId
is not the UUID.
iv_workflowtype
TYPE /AWS1/OMXWORKFLOWTYPE
/AWS1/OMXWORKFLOWTYPE
¶
The run's workflow type. The
workflowType
must be specified if you are running aREADY2RUN
workflow. If you are running aPRIVATE
workflow (default), you do not need to include the workflow type.
iv_runid
TYPE /AWS1/OMXRUNID
/AWS1/OMXRUNID
¶
The ID of a run to duplicate.
iv_name
TYPE /AWS1/OMXRUNNAME
/AWS1/OMXRUNNAME
¶
A name for the run. This is recommended to view and organize runs in the Amazon Web Services HealthOmics console and CloudWatch logs.
iv_cacheid
TYPE /AWS1/OMXNUMERICIDINARN
/AWS1/OMXNUMERICIDINARN
¶
Identifier of the cache associated with this run. If you don't specify a cache ID, no task outputs are cached for this run.
iv_cachebehavior
TYPE /AWS1/OMXCACHEBEHAVIOR
/AWS1/OMXCACHEBEHAVIOR
¶
The cache behavior for the run. You specify this value if you want to override the default behavior for the cache. You had set the default value when you created the cache. For more information, see Run cache behavior in the Amazon Web Services HealthOmics User Guide.
iv_rungroupid
TYPE /AWS1/OMXRUNGROUPID
/AWS1/OMXRUNGROUPID
¶
The run's group ID. Use a run group to cap the compute resources (and number of concurrent runs) for the runs that you add to the run group.
iv_priority
TYPE /AWS1/OMXINTEGER
/AWS1/OMXINTEGER
¶
Use the run priority (highest: 1) to establish the order of runs in a run group when you start a run. If multiple runs share the same priority, the run that was initiated first will have the higher priority. Runs that do not belong to a run group can be assigned a priority. The priorities of these runs are ranked among other runs that are not in a run group. For more information, see Run priority in the Amazon Web Services HealthOmics User Guide.
io_parameters
TYPE REF TO /AWS1/CL_RT_DOCUMENT
/AWS1/CL_RT_DOCUMENT
¶
Parameters for the run. The run needs all required parameters and can include optional parameters. The run cannot include any parameters that are not defined in the parameter template. To retrieve parameters from the run, use the GetRun API operation.
iv_storagecapacity
TYPE /AWS1/OMXINTEGER
/AWS1/OMXINTEGER
¶
The
STATIC
storage capacity (in gibibytes, GiB) for this run. The default run storage capacity is 1200 GiB. If your requested storage capacity is unavailable, the system rounds up the value to the nearest 1200 GiB multiple. If the requested storage capacity is still unavailable, the system rounds up the value to the nearest 2400 GiB multiple. This field is not required if the storage type isDYNAMIC
(the system ignores any value that you enter).
iv_outputuri
TYPE /AWS1/OMXRUNOUTPUTURI
/AWS1/OMXRUNOUTPUTURI
¶
An output S3 URI for the run. The S3 bucket must be in the same region as the workflow. The role ARN must have permission to write to this S3 bucket.
iv_loglevel
TYPE /AWS1/OMXRUNLOGLEVEL
/AWS1/OMXRUNLOGLEVEL
¶
A log level for the run.
it_tags
TYPE /AWS1/CL_OMXTAGMAP_W=>TT_TAGMAP
TT_TAGMAP
¶
Tags for the run. You can add up to 50 tags per run. For more information, see Adding a tag in the Amazon Web Services HealthOmics User Guide.
iv_retentionmode
TYPE /AWS1/OMXRUNRETENTIONMODE
/AWS1/OMXRUNRETENTIONMODE
¶
The retention mode for the run. The default value is
RETAIN
.Amazon Web Services HealthOmics stores a fixed number of runs that are available to the console and API. In the default mode (
RETAIN
), you need to remove runs manually when the number of run exceeds the maximum. If you set the retention mode toREMOVE
, Amazon Web Services HealthOmics automatically removes runs (that have mode set toREMOVE
) when the number of run exceeds the maximum. All run logs are available in CloudWatch logs, if you need information about a run that is no longer available to the API.For more information about retention mode, see Specifying run retention mode in the Amazon Web Services HealthOmics User Guide.
iv_storagetype
TYPE /AWS1/OMXSTORAGETYPE
/AWS1/OMXSTORAGETYPE
¶
The storage type for the run. If you set the storage type to
DYNAMIC
, Amazon Web Services HealthOmics dynamically scales the storage up or down, based on file system utilization. By default, the run usesSTATIC
storage type, which allocates a fixed amount of storage. For more information aboutDYNAMIC
andSTATIC
storage, see Run storage types in the Amazon Web Services HealthOmics User Guide.
iv_workflowownerid
TYPE /AWS1/OMXWORKFLOWOWNERID
/AWS1/OMXWORKFLOWOWNERID
¶
The 12-digit account ID of the workflow owner that is used for running a shared workflow. The workflow owner ID can be retrieved using the
GetShare
API operation. If you are the workflow owner, you do not need to include this ID.
iv_workflowversionname
TYPE /AWS1/OMXWORKFLOWVERSIONNAME
/AWS1/OMXWORKFLOWVERSIONNAME
¶
The name of the workflow version. Use workflow versions to track and organize changes to the workflow. If your workflow has multiple versions, the run uses the default version unless you specify a version name. To learn more, see Workflow versioning in the Amazon Web Services HealthOmics User Guide.
RETURNING¶
oo_output
TYPE REF TO /aws1/cl_omxstartrunresponse
/AWS1/CL_OMXSTARTRUNRESPONSE
¶
Domain /AWS1/RT_ACCOUNT_ID Primitive Type NUMC
Examples¶
Syntax Example¶
This is an example of the syntax for calling the method. It includes every possible argument and initializes every possible value. The data provided is not necessarily semantically accurate (for example the value "string" may be provided for something that is intended to be an instance ID, or in some cases two arguments may be mutually exclusive). The syntax shows the ABAP syntax for creating the various data structures.
DATA(lo_result) = lo_client->/aws1/if_omx~startrun(
io_parameters = /AWS1/CL_RT_DOCUMENT=>FROM_JSON_STR( |\{"foo":"this is a JSON object..."\}| )
it_tags = VALUE /aws1/cl_omxtagmap_w=>tt_tagmap(
(
VALUE /aws1/cl_omxtagmap_w=>ts_tagmap_maprow(
key = |string|
value = new /aws1/cl_omxtagmap_w( |string| )
)
)
)
iv_cachebehavior = |string|
iv_cacheid = |string|
iv_loglevel = |string|
iv_name = |string|
iv_outputuri = |string|
iv_priority = 123
iv_requestid = |string|
iv_retentionmode = |string|
iv_rolearn = |string|
iv_rungroupid = |string|
iv_runid = |string|
iv_storagecapacity = 123
iv_storagetype = |string|
iv_workflowid = |string|
iv_workflowownerid = |string|
iv_workflowtype = |string|
iv_workflowversionname = |string|
).
This is an example of reading all possible response values
lo_result = lo_result.
IF lo_result IS NOT INITIAL.
lv_runarn = lo_result->get_arn( ).
lv_runid = lo_result->get_id( ).
lv_runstatus = lo_result->get_status( ).
LOOP AT lo_result->get_tags( ) into ls_row.
lv_key = ls_row-key.
lo_value = ls_row-value.
IF lo_value IS NOT INITIAL.
lv_tagvalue = lo_value->get_value( ).
ENDIF.
ENDLOOP.
lv_runuuid = lo_result->get_uuid( ).
lv_runoutputuri = lo_result->get_runoutputuri( ).
ENDIF.