On pressing the “Technical Settings” button a screen is displayed as below.
The most important parameters for System Copy GT are:
- Number of batch jobs across all servers – Specify the number of jobs with which you want to run the program with. Ensure that sufficient background work processes are available. Be mindful that too much parallel processing can cause database locking issues when updating the same table. Please refer to the Performance Considerations section later in this document for further information.
- Interval Size – This parameter defaults to the standard BDLS parameter “Number of Entries per Commit” and represents the same purpose. It is critical in the sense that the number of entries can directly affect performance of both the standard BDLS transaction and System Copy GT. If this value is set to too low, then far too many COMMIT’s are made to the database – introducing an unnecessary overhead. In addition, too many intervals will be created which will also introduce an unnecessary overhead. Conversely, if set too high the commit area can becomes very large and even cause instability with database interruptions. The optimal value to specify here is in the range of 50,000 to 150,000. It is suggested to set this to a value of 100,000, which is the default setting.
An explanation for the function of each field on the “Technical Settings” screen is as follows:
- Label – The first is a label that can be specified to identify this particular execution
- Interval Count –This specifies the number of intervals (chunks) that the total amount of work to be done is to be broken up into, this is not relevant for System Copy GT
- Interval Size –This specifies the “number of objects” to be put into each interval to be then worked upon independently
- 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
- 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
- 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
Please Note: All of these parameters can be defaulted either when executing the transaction on-line or saved within a variant if executed in the background. See the Diffuser Guide Default Technical Settings for information on how to setup defaults.