Combined Specialization Rules Window
Define rules identifying which requests a concurrent manager can read. With the rules you define here, you may specialize the function of a concurrent manager.
Using this window, you can define several Include and Exclude statements, each referred to as a specialization line, and combine the lines into a single specialization rule referred to as a Combined Rule.
Unlike the individual rules you define using the Specialization Rules window from within the Concurrent Managers window, the combined rules you define here differ in two ways:
- You can combine Include and Exclude statements. This enables you to identify very specific requests for running concurrent programs.
- Within a combined rule, using multiple Include statements restricts a concurrent manager more.
See: Concurrent Managers
With individual rules you define using the Specialization Rules window (within the Concurrent Managers window), the more "Include" rules you define, the less restricted a manager becomes.
Combined Specialization Rules Block
Together, the application name and the name you define for your combined specialization rule uniquely identifies the rule.
The application name does not prevent a concurrent manager from starting programs associated with other applications.
Specialization Rules Block
Define the individual rules (statements) that make up your combined specialization rule.
- Each rule in this block defines one statement.
- The sum of all the specialization rules defines your combined specialization rule.
Select from the poplist whether to include or exclude those requests that are based on the rule to run.
Select the type of specialization rule you want to enforce on a concurrent manager.
You cannot combine two Include rules of the same type.
Based on a rule's action, exclude or include, programs can be run by your manager according to a:
- For example, you cannot include programs to be associated with an ORACLE ID, then, on another line, include programs to be associated with a second, different ORACLE ID.
For example, programs with a certain ORACLE ID are excluded from running. Or conversely, a concurrent manager only includes programs with a specific ORACLE ID.
For example, only the program you select is excluded from running. Or conversely, a concurrent manager only includes the programs you select. You can also include or exclude all programs belonging to a specific application using the Program type by entering the application in the Application field and leaving the Name field empty.
- Request Type (of the program)
For example, programs of a certain request type are excluded from running. Or conversely, a concurrent manager only includes programs with the request type you select.
- User (application username at sign on)
For example, all programs submitted by a certain user are excluded from running. Or conversely, a concurrent manager includes only programs submitted by the user you select.
Overview of Concurrent Processing
Specializing Managers to run only certain programs
Defining Specialization Rules
Defining Combined Specialization Rules
Using Combined Rules
Differences Between Specialization and Combined Rules
Grouping Programs by Request Type
Administer Concurrent Managers field help
Concurrent Managers field help