Scheduler Usage

Issue :
The CONTROL-M/EM Gateway crashing during Download due to the fact that the CONTROL-M/Server is transferring data faster than the Gateway can Download.

Reason :
CONTROL-M/Server can transfer data quicker than the Gateway can handle, and when this happens the data is "buffered".
However the buffer has a finite size, so this scenario (of the Gateway crashing at Download) can happen when the buffer is filled - for example when the Download is large due to a very large number of Conditions (for example 100,000 Conditions if they are not being cleaned through the day).
If you are suffering an issue relating to this you will see sequence numbers in the CONTROL-M/EM $HOME/log/GTW*.log file that suddenly jump, and tend to be high sequence numbers too.


Solution from BMC:
Adding CTM_MAX_IPC_Q_SZ parameter in config.dat file on your Control-m Server, starting to 10000 and going up from there, as :
CTM_MAX_IPC_Q_SZ 10000

will help to avoid Gateway crashing during a Download.
That scenario can happen on all versions, from v6.0.01 to v6.3.01, and it is absolutely still aoppropriate to v6.3.01

if the problem still staying, have a look at the followings parameters about "user log cache size" and "procedure cache" and increase them to

sp_configure "user log cache size",4096
go
sp_configure "procedure cache",20
go


if your default parameter is 2048 and 10

regards
Philmalmaison

Philmalmaison,


where do the next two parameters stay?

in config.dat file?

no, it is a database requirement only.
you must be sa to set them by sql as described
those parameters don't change after

regards
philmalmaison