ajomarquez, It seems your script is called via a job defined with TASKTYPE Command. Otherwise, I don't see how the script could internally resolve an AutoEdit variable, while the command line of the job could resolve both AutoEdit and envirpnment variables. In that case, %%A is necessarilly resolved...

Hubba, Its not so easy to automate the removal of jobs that have been already ordered. The most direct reply to your need is, as you suggest yourself, to order the successors when needed. ON STMT * CODE COMPSTAT != 0 DO OK ON STMT * CODE COMPSTAT = 0 DO FORCEJOB TABLE <TABLE> JOBNAME <JOBNAME> You c...

Hi,
The alerts are physically erased, but still buffered in the GAS Server, which then has to be stopped/restarted. You can automate the global proces using the "ctl" utility

Cheers

Hello,

There used to be a more or less documented script called erase_alerts. This is available in the <em_home>/scripts
Check you ctm housekeeping jobs to check if that script is used.

Nicolas_mulot

Hi,

EM 6.4.0 Fix pack 3 includes the following entry:

CAR00040444 - New alert notifications are received even in cases where the new alert does not match the display filter.


Cheers
Nicolas Mulot

Diablau, The sysout does exist, so we can assume that the .bat specified in the job did run. We can imagine that the one which did not execute is actually D:\was\runtime\Start_Deferred.bat. Whichever the rc of the psexec can be, the subsequent echo and exit /B will always return a RC=0, and the job ...

Nancy, There was a slight mistake in my previous post. Instead of: ON STMT * CODE * DO SETVAR %%\COMP=%%COMPUTERNAME .. which refers to an unexisting %%COMPUTERNAME AutoEdit variable, One should have read: ON STMT * CODE * DO SETVAR %%\COMP=%COMPUTERNAME% .. which refers to the environment variable ...

Well, the idea is to focus on exceptional events. Once notified, the operator should act on the job, probably using a more standard viewpoint. Since this particular viewpoint is only intended to catch attention, the best is to exclude ended jobs (OK or NOTOK) from the viewpoint, and leave the modifi...

I have the same behaviour under Windows server 6.3 FixPack 5.
This sounds new to me and I didnt find any info on that enhancement in neither the base documentation nor in any fixpack release notes.

If anyone has info about when this was released - thanks
Nicolas_Mulot

Admin007 , All suggestions conduct to specifying shouts, and I don’t see any other way to dynamically “mark” those jobs which run for too long. I understand that if you send them messages to the alert window, they could be lost in the traffic. I tested a little trick which works and might help you. ...

ttb_uk, I think you misplaced the absolute stop time, which should be the 10th positional parm. Actually, you did not specify the 8th (monitor file size when wildcard is used) and the 9th (starting time for detecting files). You should try this syntax: ctmfw %%filename CREATE 0 60 10 3 0 N NOW 20100...

Nancy, A good trick is to define those global variables every day using a service job, which runs daily. Typically, this is a Dummy job which includes the following code: ON STMT * CODE * DO SETVAR %%\VAR1=<the> In addition, some control-m parms can be directly specified as environement variable. In...

Venkat, First the target you specified is not the correct one. You should select the ORDERNO which is the unique Id of the job in the AJF (CMR_AJF), while the JOBNO you specified is the unique Id in the definitions (CMS_JOBDEF). You might go in trouble with that request in case the job is available ...

futre25, If I understand well, the requirement is as follows 1) All predecessors must complete with either RC=0 or RC=77 2) At least one must complete RC=0 The conditions from the 5 preds to the unique successor are individual events which are linked to every single predecessor end. The statement th...