The processing of a transmission request is performed by a function called a transmission initiator. A set of 16 initiators is maintained for each remote system to which transmissions can take place.
Each initiator services one or more transmission classes (A to Z) and each transmission request has a transmission class assigned when it is defined. Consequently, a given transmission request can be processed only by a transmission initiator that services its transmission class. The initiator/transmission class concept is similar to the standard operating system initiator and job class mechanism, and is designed to be used in the same manner.
You need to consider how many initiators in each initiator set you want to define for each target system and whether certain types of transmission are assigned to specific transmission classes.
The system default, in the absence of specifically defined initiator sets, is to provide a single active initiator that services all transmission classes for each remote system. If transmissions are infrequent and of short duration, this default may be sufficient; however, if there are many transmissions to be scheduled, of varying priorities and duration, it is necessary to adopt appropriate standards for the scheduling of different requests under different classes.