Table of contents

Run parameters and Decision Optimization environment

Run parameters and the Decision Optimization environment.

Run configuration parameters

When you click the Run Configuration icon next to the Run button in the Model view of the Model Builder, a window opens showing you the currently set parameter values. You can click Add parameter and then choose from the following parameters from the Select Parameters drop-down menu.

Name Type Description
oaas.timeLimit Number Time limits in milliseconds. You can use this parameter to set a time limit that is smaller than the default limit defined by your subscription.
oaas.engineLogLevel Enum
  • OFF
  • SEVERE
  • WARNING
  • INFO
  • CONFIG
  • FINE
  • FINER
  • FINEST
You can use this to define the level of detail provided by engine log. The default value is INFO.
oaas.jobCores Number This parameter specifies the maximum number of cores used to process the job. The value can vary from 1 to the maximum number of cores of the processing instance. If not specified, by default, the job uses all the cores of the processing instance.
oaas.jobMemoryMbytes Number This parameter specifies the maximum memory in megabytes used to process the job. The value can vary from 512MB to the maximum memory of the processing instance. If not specified, by default value: the job uses all of the instance's available memory.

If you choose Custom parameter... from the Select Parameters drop-down menu you can add the following advanced parameters.

Name Type Description
oaas.dumpZipName can be viewed as Boolean (see Description) If defined, a job dump (input and outputs) zip file is provided with this name as a job output attachment. Name can contain placeholder ${job_id}. If defined with no value, dump_${job_id}.zip attachmentName is used. If not defined, by default, no job dump zip file is attached.
oaas.dumpZipRules String If defined this generates a zip file according to specific job rules (RFC 1960-based Filter). It must be used in conjunction with the {@link DUMP_ZIP_NAME} parameter. Filters can be defined on the duration and the following {@link com.ibm.optim.executionservice.model.solve.SolveState} properties:
  • duration
  • solveState.executionStatus
  • solveState.interruptionStatus
  • solveState.solveStatus
  • solveState.failureInfo.type
Example:
(duration>=1000) or (&(duration<1000)(!(solveState.solveStatus=OPTIMAL_SOLUTION))) or (|(solveState.interruptionStatus=OUT_OF_MEMORY)(solveState.failureInfo.type=INFRASTRUCTURE))
Modeling Assistant only

For CPLEX ma.cplex.parameters.<Python cplex parameter name>

For CPO ma.cpo.parameters.<Python cpo parameter name>

  Python names for CPLEX and CPO parameters can be entered with the prefixes ma.cplex.parameters. or ma.cpo.parameters.

For example,

ma.cplex.parameters.mip.tolerances.absmipgap

ma.cpo.TimeLimit

For a list of parameters see:

Once you have set the run configuration parameters they will remain with those values for all subsequent runs for that scenario. You can set different run configurations for different scenarios.

You can remove set parameters by hovering over the parameter displayed in the Run configuration window and clicking the remove button.

The run configuration parameters are saved together with the model when you select Save as model for deployment from the Scenario panel.

Decision Optimization environment

In the run configuration window you can also see the CPU cores and memory that you have subscribed for. By default all your core and memory are used for each model you run. If you click the pencil icon to edit these, you will open an Edit environment window in your project where you can make change the values and update your environment for your project.

You might, however, want to reduce the CPU cores and memory used for a particular scenario to enable you to run another scenario simultaneously, using the remainder core and memory. You can thus set different run configurations for each scenario from the Run configuration window by choosing the run configuration parameters oaas.jobCores and oaas.jobMemoryMbytes from the Select Parameters drop-down menu.