A run in IMP Manager comprises the following objects:
Trigger
Objects determined by the trigger
A run has the following attributes:
Application class to which the run belongs
Technical key
Short text that provides the following information:
Application class
User who created the run
Point in time at which the run was created
Status
This status influences the functions that can be used (see “Status of a Run” below).
You can group several objects in a workset in one block. The system then processes the objects in a block together.
Note the following:
You can use a block to control the number of objects that are saved in the database's main memory or the size of a database commit. The following guidelines apply to the size of a block:
A block should not be too small otherwise this could result in an excessive and unnecessary number of database calls.
A block should not be too large otherwise this could result in performance problems.
All the objects within a block must be without errors in order to receive the status Ended Successfully
. If a single object in a block returns an error, all the objects in this block are given the status Not Processed or Processed with Errors
and have to be processed again.
Note
This object status is not to be confused with the workset status, which is described under “Status of a Run”.
Before you can group objects in a block you have to enter parameter IMP_BLOCK_SIZE in your user profile. Execute the following activities:
Choose
.Select the Parameters
tab page.
Enter parameter IMP_BLOCK_SIZE with a parameter value (for example, 5 = a block contains five objects).
Example
A workset has 13 objects and parameter IMP_BLOCK_SIZE has the value 5. First the system processes the first five objects, then it processes the next five objects, and finally it processes the remaining three objects.
The following table lists the different statuses and applicable restrictions:
Status of Run | Description Including Any Restrictions |
---|---|
| The system has created the run. If the system has created new triggers with the same application class, it adds these new triggers to the run. As soon as you start the mass activity, the run is given the status |
| You cannot add any more triggers to the run. The system uses the existing triggers to determine the objects. |
| You cannot add any more objects to the run. Test or simulation runs retain this status. |
| The system has started parallel processing. If the run still has the same status after completion of the mass activity, this means that serious errors have occurred, such as a job cancellation. In this case, you can set the status manually to |
| An error occurred during the run in at least one interval. You can start runs with this status once again in the mass activity. The system tries to process the intervals containing errors. In this case, you can set the status manually to For more information, see “Functions in Dialog Mode”. |
| The system has ended the run successfully. In this case, you can set the status manually to For more information, see “Functions in Dialog Mode”. |
| The system has deleted the triggers and objects of the run. |