To see which instance has the least load for a new job, go to each instance and check the Thread Queue Manager. The queue manager can be found at http://URL:port/jsp/tqm.jsp. This page shows you how many threads are running and pending for each instance. You can pick the least active instance to begin the new job.
The following is an example of the tqm.jsp output:
ThreadId=86 ThreadName=SCHEDULEJOB$86$174_WYETHIDR_IDR_201011 174_WYETHIDR_IDR_201011 Status=Running GroupId=SCHEDULEJOB$86 ParentIds=null
ThreadId=148 ThreadName=JOBSTEP$148$Copy To Destination Status=Running GroupId=JOB$86 ParentIds=null Priority=0
ThreadId=33906 ThreadName=33$RES_FACT$FLAT_FILE Status=Running GroupId=STEP$148 ParentIds=null Priority=1
ThreadId=33914 ThreadName=33$SAMP_BRIDGE$FLAT_FILE Status=Running
GroupId=STEP$148 ParentIds=null Priority=1
Each thread that has "status=Running" will count against the total thread count allocated through the amMaxServerThreads parameter. For example, if you have the parameter set to 30, then, for this instance, 27 threads are left for other processes.
The best instance to start a new job is one where the tqm.jsp returns the following status:
No threads in queue
Effective in ILM 5.3.4, if you set informia.appendHostAndPortInLog parameter=Y to append the host name and port number to the logs, the job logs in View Current Jobs indicate what instance a job is running on. Using this information, you can open the job log for any process in a running state to see which engine has the heaviest load and which one has the lightest load.