Technical Settings

The key part that the user sees is the “Technical Settings” button as below.

If you select the “Technical Settings” button, you will be prompted for Diffuser specific technical settings.

These “Technical Settings” are important when executing an Diffuser program be it in a production environment, or when performing unit testing of your Diffuser program.

Note that you can set up Default Technical Settings and set up user authorizations to control the users ability to change these settings, for more information refer to the Z Accelerators – Developers Guide Authority Checks.

An explanation for the function of each field on the “Technical Settings” screen is as below:

• Label – The first is a label that can be specified to identify this particular execution.

• Perform processing using intervals of – This is the interval object confirmed in the Program Definition

• Interval Variant – The Interval variant provides you with a list of different pre-generated Intervals. As detailed in the section Interval Generation, the interval variants are pre-generated using program /BTR/MDR_INTERVAL_GENERATION

• Number of batch jobs across all servers – This specifies the number of processes with which to run the Diffuser program.

• Distribution according to server grouping – This allows the distribution of jobs over one server group to control the number of processors available to this Diffuser instance.

• Manual Distribution – The server grouping above can also be distributed manually.

• Run online as a single process (debugging mode) – This is only used when debugging Diffuser programs and ensures the whole program runs sequentially, in a foreground process.

• Wait for run to complete before finishing – This is often used when running Diffuser programs on-line or when executing them via a job scheduler. It will ensure the parent process waits until all child processes have completed. Once all child processes have finished, control is returned to the parent for completion.

• Launch Transformation Program after completed run – This means the MiniCube screen is skipped so the user gets straight to their results when the run completes

• Distribution List – After a Diffuser program completes it is able to send a SAP office document or external email to a set of recipients that can be specified here.

• Message log level – Lower limit for the priority of messages output to the application log. For example, you can restrict output of informational application log messages by increasing the log level via this parameter.

When using Dynamic Intervals as set out in the Z Accelerators – Developers Guide Dynamic Interval Generation the “Interval Settings” section will change and be replaced with the two options Interval Count and Interval Size introduced, this looks as per the screenshot below.

The impact of the two fields is as below:

• Interval Count – This specifies the number of intervals (pieces) that the total amount of work to be done is to be broken up into

• Interval Size – This specifies the “number of objects” to be put into each interval to be then worked upon independently