Specify Job Classes and Number of Initiators

Specify Job Classes and Number of Initiators
The initiator.class parameter sets the maximum number of active jobs of a particular class that the agent allows. By default, the agent allows up to 1000 jobs of the default class at a given time. You can further control jobs the agent allows by setting up more initiator classes and indicating which job types they control. For example, you can have a UNIX class that only allows 100 active UNIX jobs simultaneously.
To specify job classes and number of initiators, configure the following parameters on the agent:
  • initiators.class_
    n
    =
    jobclass
    ,
    number_of_initiators
    Describes job classes and the number of initiators that can process jobs that are assigned a particular job class. Use a new line for each initiators.class_
    n
    parameter, where
    n
    is an integer starting at the value 1. By controlling the type and number of initiators, you can have greater control over the initiation of jobs and manually balance the loads on system resources.
    The parameter initiators.afmjobclassmap_
    n
    relates to this parameter. However, the value of
    n
    does not have to match in both parameters.
    For UNIX workload, depending on the number of initiators you assign, you may need to increase the number of threads that can be run per process on your operating system.
    Examples:
    initiators.class_1=Default,1000
    initiators.class_2=POJO,100
  • initiators.afmjobclassmap_
    n
    =
    verb
    ,
    subverb
    ,
    jobclass
    Maps verb and subverb combinations of a job request to a job class. When the agent sees an AFM containing a defined pair of verb and subverb, it assigns the specified job class to that job.
    The defined pair must be a valid verb and subverb combination. Write a separate instance of this parameter for each pair. For some job types, you can also specify a job class in a job definition.
    To find out which verbs and subverbs you can use, see the agent receiver log.
Example: Limit the Number of Web Services Jobs the Agent Initiates
Suppose that you want to limit the number of Web Service jobs the agent initiates to 100. In this example, the job class is defined as WS. The following agent receiver log contains the verb and subverb: WEBSERVICE and RUNRPC.
AM STRESS HELLO4.TXT/OA.1/MAIN WEBSERVICE RUNRPC TargetNS(http://tempuri.org/) Operation(HelloWorld) WSDLURL(http://138.42.98.127:3247/WebSite3/Service.asmx?WSDL) ServiceName(Service) PortName(ServiceSoap)
The verb and subverb in the agent receiver log follow the job ID, HELLO4.TXT/OA.1/MAIN.
To set the job class and number of initiators, you configure the following parameters to the values shown.
initiator.class_1=Default,1000 initiator.class_2=WS,100 initiators.afmjobclassmap_1=WEBSERVICE,RUNRPC,WS
Example: Limit the Number of IBM i Jobs the Agent Initiates
Suppose that you want to limit the number of IBM i jobs the agent initiates to 100. In this example, the job class is defined as IBM i. The following agent receiver log contains the verb and subverb: RUN and '.' (dot).
OS400AGNT CENTRAL_MANAGER TEST/ I5OS_NATIVE.2/MAIN RUN . Data(CCExit=*SEVERITY) Command(CHGCURLIB) Parameters('QGPL')
The verb and subverb in the agent receiver log follow the job ID, I5OS_NATIVE.2/MAIN.
To set the job class and number of initiators, you configure the following parameters to the values shown.
initiator.class_1=Default,1000 initiator.class_2=i5,100 initiators.afmjobclass_1=RUN,'.',i5