Initiator Requirements

When an INMC link becomes active for the first time, a set of 16 transmission initiators reserved for the transmission of files is built.

Each initiator is assigned one or more transmission classes and has a status of STOPPED or STARTED. Each file transmission operation to the other CA SOLVE:FTS region uses one initiator for the duration of the transmission, so the number of concurrent transmissions that can take place is limited to the number of defined and started initiators.

File transmissions are assigned a transmission class (alphabetic, A to Z) that determines which initiators the transmission may use. The meaning of these classes is similar to that of operating system job classes—that is, the class of a transmission governs the choice of initiators that are able to service that transmission. The installation may therefore separate testing and production, or high and low priority transmissions by class.

Initiator Definitions

You can use the default settings for a group of initiators for a particular definition and CA SOLVE:FTS builds an initiator set configured as follows:

   1 : Services classes A - Z in order. Initial status is `STARTED'.
2-15 : Service class A only. Initial status is 'STOPPED'.

If this default set of initiators is sufficient, you need take no further action. If, however, you want to set up a different set of initiators for this particular destination, you must define the initiator set.

When you start the INMC link between the two regions, if an initiator is defined, it is used; otherwise, the default settings are used.

Define Custom Initiators

To define custom initiators

  1. Enter /FTSADMN at the prompt.

    The FTS : Administration Menu appears.

  2. Select option A.

    The FTS : Transmission Initiator Definition panel appears.

  3. Complete the following fields:
  4. (Optional) Issue a LINK STOP command to close the link, then a LINK RESET command followed by a LINK START command. This refreshes the link definition and the initiator definitions, and activates the new initiator definitions.

Example: Initiator Definition

The following example shows an initiator set with five initiators defined, servicing 12 different classes between them.

PROD-------------- FTS : Transmission Initiator Definition --------------------
Command ===> Function=ADD

Destination name ... NEW YORK Initially enabled? ... Y
Maximum concurrent inbound files
Init Service Classes (A to Z) Started? Com Hi-Pr? Pref-Session
1 XY Y 3 Y
2 CFAB Y 3 N
3 AB Y 3 N
4 D Y 3 N
5 PQRST Y 3 N
6
7
8
9
10
11
12
13
14
15
16
F1=Help F2=Split F3=File F4=Save
F9=Swap F12=Cancel

When multiple initiators are defined and a request is available for execution with a transmission class that is serviced by more than one (available) initiator, the request is scheduled under the initiator that has the highest preference for that class.

For example, if none of the five initiators shown are busy and a Class A transmission request is available for execution, CA SOLVE:FTS finds that initiators 2 and 3 both service class A, but that initiator 2 accepts class A requests only if no class C or F requests are available. Initiator 3, however, services class A in preference to any other class. In this case, CA SOLVE:FTS assigns the request to initiator 3 for execution. A second class A request issued while initiator 3 is executing the first request would be allocated to initiator 2.


Copyright © 2010 CA. All rights reserved.