is it a control-m server installation problem or a control-m EM installation problem? the control-m server parameters for installation are the following : 2 : Custom - Install a CONTROL-M/Server optionally changing selected settings. == <H> Help <C> Cancel <N> Next Panel == Enter command : 2 === Ins...

like the following ? END USER LICENSE AGREEMENT BY OPENING THE PACKAGE, INSTALLING, PRESSING "AGREE" OR "YES" OR USING THE PRODUCT, THE ENTITY OR INDIVIDUAL ENTERING INTO THIS AGREEMENT AGREES TO BE BOUND BY THE FOLLOWING TERMS. IF YOU DO NOT AGREE WITH ANY OF THESE TERMS, DO NOT INSTALL OR USE THE ...

like the following ? END USER LICENSE AGREEMENT BY OPENING THE PACKAGE, INSTALLING, PRESSING "AGREE" OR "YES" OR USING THE PRODUCT, THE ENTITY OR INDIVIDUAL ENTERING INTO THIS AGREEMENT AGREES TO BE BOUND BY THE FOLLOWING TERMS. IF YOU DO NOT AGREE WITH ANY OF THESE TERMS, DO NOT INSTALL OR USE THE ...

dont you arrive to the END USER LICENSE AGREEMENT ??

for the controlm job i've created a cyclic job every 30 min, with the range parameter:
PARM1=%%$ODATE
PARM2=%%$CALCDATE %%$ODATE -7
corresponding to 7 days of statistics of runinf.

apres qqes modifs ca tourne, seul hic constat?, les jobs tres rapides sont souvent remont?s parceque le serveur controlm met du temps a mettre ses donnees a jour...

PAC is stopping with AIX, 5.3 - 64-bit
but don't think that beta version never supported, is it the new AIX version?
Regards
Philmalmaison

no needs to learn the BMC product documentation, other than user guides to monitor applications under control-m. but it is important to have a look to the control-m server admin guide (to understand "utilities" you can or have to use. for the real monitoring of DATACENTERS, i think a production envi...

finally i've made somethink like that : #!/bin/ksh tmp="/tmp/tmp.$$" tmp2="/tmp/ResultatExectime-`date '+%d%m%Y'`-`date '+%H%M'`.txt" touch ${tmp2} cd $HOME # 1. ODATE # 2. PREVDATE ODATE=${1} PREVDATE=${2} ctmpsm -LISTALL TIME | grep "${ODATE} Executin" > ${tmp} if [ -s ${tmp} ] then cat ${tmp} | ...

no my case is to create a cyclic job, able to scan ajf, select the executing jobs, and calculate if the executing job is to long or not regarding a calculation made from its average medium statistics (ctmruninf -total)

your answer concerning oracle , i'm working with sybase...

what are you meaning about templates on AJF should you be a little more accurate ?

correction: stop the agent by shut-ag with root user where </tmp> is to replace by your directorie: mkdir -p /tmp/ctm/sysout chown <agent>:<group> /tmp/ctm/sysout so remove sysout directorie on your agent (by rmdir) in $HOME/<agent>/ctm do the following link: tunis% ln -s /tmp/ctm/sysout sysout tuni...

the only way to do that seams to be a solaris problem. Should you redirect your sysout, after making the new directorie (dumps/ctma/ctm/sysout), (dont forgot to stop agent), give rights on it to ctrlm agent user, in $HOME/ctm rename sysout directorie by sysout.old, and in ctm directorie, make a link...

depending of the informations you need (and changing * by fields of the alarm table, you can do the following: make a controlm job in confirm mode, adding a %%PARM1=<Alert_Id> Alert_Id can be found in Alert Details submitting the foll. script: #!/bin/ksh tmp="/tmp/tmp.$$" SQL <<EOF> ${tmp} select * ...

does anyone had made a job scanning the AJF in cyclic mode and extracting jobs whoses execution time is > to a range time ?