Blackout in newday process

[vpaldi]

Hi There,

we have a relatively long blackout time in association with the newday process. Actually it is not the newday itself, but the job download to EM starting right after the newday. We observed 1 minute increase per 1000 jobs of the download time. The problem is that during that time EM is not communicating with the operator (that's why we call it as "blackout")

And now the questions:
- is it normal?
- do you observe similar phenomena in your system?
- any hint to speed up the process?

We are on 6.4 level. Please find below the gateway log.

Best regards,
Vince

[27@06:30:58.300:] ===> INFO: Previous log was "/home480/ctrlmem/log/gtw_log.PROD.20110126.0" time >06:30:58.300:<27> INFO: Opening new log "/home480/ctrlmem/log/gtw_log.PROD.20110127.0" time >06:30:58.300:<GTW> INFO: Control-M ver: 640 (MPM)
[27@06:30:58.300:] ===> INFO: database type: ORACLE.
[27@06:30:58.300:] .===> INFO: start download procedure
[27@06:31:06.267:] ===> INFO: update_bim_svc_ind_before_dwl: number of updated jobs: <0> in previous net: <A110126001_AJOB>
[27@06:31:06.268:] ===> INFO: intialize bim svc cache.
[27@06:31:06.957:] ===> INFO: new net [110127001_A] created.
[27@06:31:07.512:] ===> INFO: 264 global conds out of 20300 conds, net: 110126001_A
[27@06:31:07.512:] ===> INFO: current GC loaded.
[27@06:40:07.647:] ===> INFO: sending post download GC.
[27@06:40:08.051:] ===> INFO: 264 global conds out of 20302 conds, net: 110127001_A
[27@06:40:08.053:] ===> INFO: post download GC ditribution: 0 added, 0 deleted
[27@06:40:08.053:] ===> INFO: gate_down_receive: DDL count semaphore is disabled.
[27@06:40:09.632:] ===> INFO: begin generate post download Ended Not OK alerts.
[27@06:40:09.726:] ===> INFO: 2 Ended Not OK alerts were generated..
[27@06:40:09.800:] ===> INFO: jobs in BIM services at download time: 0
[tid: 1][27@06:40:09.843:] ===> INFO: creating post download RUNINFO records..
[27@06:40:11.328:] ===> INFO: download information:
type : New AJF
base level: 914
update level: 0
order date: 20110127
jobs : 9620
control res: 0
conditions: 20302
quant res: 0
def control res: 0
def prereq conds: 12469
def out conds: 8914
def quant res: 0
def setvar: 303297
def shout: 38
def step range: 0
def on: 1700
def do: 1441
def do setvar: 0
def do shout: 33
def do force job: 0
def do sysout: 0
def do cond: 104
def do ifrerun: 0
def do ctbstep: 0
def do pipes: 0
def do notes: 0
def do mail: 123
def do remedy: 0
def do ctbrule: 0
[27@06:40:11.333:] .===> INFO: end download, free dld end dwl [/b][/quote]

[philmalmaison]

change tables USERDAILY SYSTEM to a userdaily specific launch by the userdaily system.
you can even calculate run time for each new userdaily and launch them only when it's necessary.

You can also parameter controlm server to not do the agent cleanup and the runinformation cleanup during the NDP, by adding some lines in config.dat from the datacenter.

regards,
Philmalmaison

[avaidya10]

if you have large number of jobs have few more userdaily jobs. for example 8amload, 10amload etc