|
|
|
To accommodate the diversity of environmental conditions that may exist at different installation sites, Job Management Manager can tune the communication code that lets the manager and the agent communicate.
Sites with slow networks, unreliable networks, heavily burdened nodes, or heavy spikes in CPU utilization may need to adjust these parameters. Tuning parameters have the same names for the manager and for the agent.
These parameters may be logical names or symbols. If the parameters are system logical names, they affect the NSCHED, SCHED$LISTENER retry, and user interface processes. If you want different parameters for these processes, use symbols or process logical names created in the process’s startup file.
The following table lists the parameters with their possible settings:
|
Parameter |
Default |
Minimum |
Maximum |
|---|---|---|---|
|
SCHED_PACKET_WAIT |
2 sec |
1 sec |
60 sec |
|
SCHED_MAX_RETRIES |
3 |
0 |
32 |
|
SCHED_PENDING_DELAY |
60 sec |
1 sec |
– |
SCHED_PACKET_WAIT and SCHED_MAX_RETRIES work together. When one component (manager or agent) tries to communicate with the other, the component tries to connect. If it fails to connect, the component waits the amount of seconds set in SCHED_PACKET_WAIT and tries again. The component repeats this process a number of times equal to SCHED_MAX_RETRIES.
Note: Since packet communication is synchronous, the sending process waits a maximum of SCHED_PACKET_WAIT * SCHED_MAX_RETRIES seconds before ending attempts to send a packet. If you set both parameters high, the component may wait an unacceptably long time before starting other work. A system that has many jobs starting or finishing within a short time of one another requires higher values for these parameters.
| Copyright © 2012 CA. All rights reserved. | Tell Technical Publications how we can improve this information |