Show TOC

 Run Administration

 

Objects of a Run

A run in IMP Manager comprises the following objects:

  • Trigger

  • Objects determined by the trigger

Attributes of a Run

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).

Grouping of Objects in a Workset

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 Note

    This object status is not to be confused with the workset status, which is described under “Status of a Run”.

    End of the note.

Before you can group objects in a block you have to enter parameter IMP_BLOCK_SIZE in your user profile. Execute the following activities:

  1. Choose Start of the navigation path System Next navigation step User Profile Next navigation step Own Data End of the navigation path.

  2. Select the Parameters tab page.

  3. Enter parameter IMP_BLOCK_SIZE with a parameter value (for example, 5 = a block contains five objects).

Example 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.

End of the example.
Status of a Run

The following table lists the different statuses and applicable restrictions:

Status of Run

Description Including Any Restrictions

Open

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 Closed.

Closed

You cannot add any more triggers to the run.

The system uses the existing triggers to determine the objects.

Selected

You cannot add any more objects to the run.

Test or simulation runs retain this status.

Started

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 Ended with Errors or Ended Successfully in IMP Manager. For more information, see Functions in Dialog Mode.

Ended with Errors

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 Ended Successfully in IMP Manager in dialog mode.

For more information, see “Functions in Dialog Mode”.

Ended Successfully

The system has ended the run successfully.

In this case, you can set the status manually to Deleted in IMP Manager in dialog mode.

For more information, see “Functions in Dialog Mode”.

Deleted

The system has deleted the triggers and objects of the run.