kshapley, Defining and enforcing naming standards is a job by itself, and no standard utility is provided to do that job. The best you could do is scanning all your definitions, either from EM or from CTM/SV database (in that case, it is a bit late). To do so, you need to develop SQL code, more part...

PI_Check

Check your private mail box on this forum

Nicolas Mulot

Bsglover, The orderid of the target job is accessible from the CMR_AJF table. The value returned is numeric, instead of alphanumeric. For example, if your target job has an orderid of abc , the returned value will be 13368. The ctmpsm utility accepts decimal orderids: in that case, the value should ...

PI_Check, As everyone told you, there is no automatic solution to your problem using control-m calendars. You may use a periodic calendar, as suggested by vassi168, but this will force you to manually input your calendar and update it year after year, which is very boring and error prone. Another so...

Soissons, ctmpsm is actually the right source to count your jobs. Given the following input .. ctmpsm -listjob executing Submitted/Executing Jobs ORDERID JOBNAME TYPE ODATE PID RUNCNT -------- ----------------- ----- -------- ---------------- ------ 00000nhy PSVCAL000 TBL 20111008 1 00000ni2 PSVCAL0...

Meanjean, If you have a controlm mainframe available, you can find a solution based on the CTMBLCAL and CTMRCAL utilities. CTMBLCAL combines 2 calendars with “plus”, “minus” and “AND” operators, to produced a resulting calendar. CTMRCAL creates calendars based on the scheduling parameters of the job...

Futre25, This feature is actually new to V7. The principle is to get a more detailed and more flexible on the global workload. It might be confusing for it might seem to replace and expand the concept of resources. Basically, it acts like queues: You can define a queue to submit jobs, and open/close...

Soissons, First, don’t be sorry being French. It happens to 60 millions people with no problem, and bad English disease does not affect only the French. You say that every occurrence of your job is important. In that case, how can you manage the rerun of any failing execution with your job being cyc...

Futre25, The concept of scheduling groups has been introduced in V6.00 and includes several interesting features, among which the scheduling tags. Scheduling tags combine scheduling parameters as you can find in the traditional “Scheduling” tab of your jobs definition. You can define as many schedul...

futre25, Which version do you come from? RBC are nothing else than the former scheduling tags, which have been named so from version 6.0.0 till 6.4.0. According to your background in that forum, one can beleive you have been using at least one 6.xx version. If you never used scheduling groups - whic...

be_incontrol, I noticed you run 630. In 640 the structure of the EM tables has changed. The following sql request should do the job (supplied in MS/SQL format, against the EM database) update DEF_DO_COND set CONDITION = replace(CONDITION,'_Dv','_Ut') where CONDITION like '%/_Dv' escape '/' Additiona...

abhishek_82, The complexity depends on what kind of information you intend to obtain. If you want an instant info on the number of jobs loaded, the GUI is enough: Just build a viewpoint which includes the ODATE as a high hierarchical level, right click on the block representing the current ODATE and...

futre25, Please be a bit more detailed in your explanations. You say “I have disabled …” then “I have not changed anything” in the same line, which is what I would call a contradiction. What are exactly the symptoms? Under which environment do you observe the problem: desktop, EM GUI, ctmorder, dail...

There is no easy way to send an alert on the first failure only. It is possible, but I don’t believe it is our case for now. The best is to specify alarm and rerun together On Stmt * Code NOTOK Do Rerun Do Shout <blabla> The shout will be sent every time the job fails. You can limit the number of au...

be_incontrol , There is basically no smart solution to your problem, for the time frame for shout is from 00 :00 to 23 :59, and is strictly a HHMM on 4 chars (no day type delay) 1°) There is a possibility, available since version 630 and called Time Synonyms, and which can extend the time frame from...