typhoeus, You dont do anything wrong. You just ask ctm to set a status OK when RC=99 and ask to force a job when status is OK. The logic of ctm is shown in the log messages as follows: TR5100 ENDED AT 20110422220255. OSCOMPSTAT 99. RUNCNT 1 TR5169 Message from Agent: Job completed TR5132 STATUS SET ...

arunveer, The "Interval" parameter(s) you find in the "Execution" tab, which looks to be designed for cyclic jobs only, also acts for Do Rerun actions. You cannot rerun a cyclic job and this parameter acts for both cases. The smallest rerun interval unit is minutes: specify 2 minutes for 120 seconds...

Largonir, You are right, in the former versions (640, 630 and probably older ones), the ctmgrpdef did not accept the –TABLE parameter, then the subsequent ctmdefine do not recognise the jobs as belonging to the previously created scheduling group, As a consequence, and this is a bug in the design of...

Largonir, The problem is that ctmcreate does not work exactly like a job creation under Desktop. When defining your job under Desktop, you may either edit your entire script, or load it (bottom left of the edit windows) from a file. This last option implies that your script resides in the neighbourh...

amirths, It should work. ctmdefine must have created your table in the ctm server base. First check that your table has actually been created using ctmpsm --> 71 You can also check thet using an sql request (on server side) like: select * from CMS_SCHEDT where SCHEDTAB='your_table_name' If it does n...

kylo_h, Walty’s suggestion is excellent, as usual. I’ve been used to that kind of situation where people want to see what happened in the past (from Saturday till Monday as you suggest, or simply from day to day, in case the daily runs before the working hours, like 0500 AM while people arrive by 09...

moha1984 First, the month codes (JAN, FEB etc..) you intend to use are not covered by any autoedit variable. For that reason, you must associate the month codes available in autoedit to your own codes (01=JAN, 02=FEB etc..) Do do so, you can either rely to a %%LIBMEMSYM table, which would contain: %...

Brownbag, The script you coded as the physical dest of the logical dest you shout to receives the following : 1) the nodeid of the job 2) the full text of the shout message 3) the urgency of the shout The message text can include any system or user autoedit variable. This means you can process as a ...

Ajomarquez, Lets clarify your question : Newday has run on day n Your system has been down long enough so newday at day n+1 has not run Your system is up again and newday is to run or ptrobably has run on n+2 If this is correct, your question is: how can I order my jobs for n+1, which have not been ...

Moha1984, Is it a new installation or an existing server? You’re not supposed to change the newday time to « any time you want” on an existing server. The impact of changing the controlm time has been mentioned in many posts of this forum, and you have to consider, among other issues, those jobs hav...

Shashwat , Actually, “from start” counts the start time of the previous run while “from target” count an exact number of cycles, from a “TIMEFROM” boundary. Lets consider a job having the following parms: TIMEFROM 0715 Cyclic Y Interval 15M If you order you job at 0700 or any time before 0715, there...

Bruno, Pour la première, voir le manuel « admin » ou « utilities » selon les versions. La syntaxe est : ctmkiljob –orderid <orderno_36> Ou : ctmkiljob –orderid « *<orderno_10> » <orderno_36> est l’orderid en alphanumérique tel qu’affiché sous EM par exemple <orderno_10> est l’orderid en numérique ba...

BreakFix, The easiest is to run a ctmrpln against all your tables for a given date (here next october 1st): ctmrpln dj y “*” “*” 20101001 This is to be run under ctm server account. The output looks more or less like this: Daily Job Order Report For Table TTSCND_TB, Job * ===========================...

Yes, good idea.
Read the manual. I have to admit it is not always that clear if you start from scratch.
Coem back to that forum if you need further explainations or provide more details on your case.

Cheers

The retention control is set at the ctm/server level ctm_menu --> 6 - Parameter Customization --> 3 - System Parameters and Shout Destination Tables --> 2) System Parameters --> n) Next Page 6) Maximum Days Retained by CONTROL-M Log : 7) Maximum Days to Retain Sysout Files : Check your DB space if y...