Search found 12 matches
- 17 Jan 2013 2:27
- Forum: SQL Scripts
- Topic: Force-job from Steps with var
- Replies: 2
- Views: 6780
We've had some success with functions like this using the Shout facility since you can pass all manner of autoedit variables into a Shout program. So we've developed a script called "ShoutForceJob", and then instead of a "DO FORCEJOB" we've configured the job with a "DO SHOUT" to this ShoutForceJob ...
- 18 Feb 2010 12:44
- Forum: Exploitation / Operation
- Topic: Looking for a tool that manages my agents
- Replies: 8
- Views: 3758
If you have millions of windows of servers, you may want to consider using an "agentless" model in which you can can install an agent on only one windows host and then use WMI to remotely run processes on other windows hosts. We use a similar process and leverage the excellent "psexec" utility to ru...
- 04 Feb 2010 12:02
- Forum: Control-M Server
- Topic: Semaphore management
- Replies: 4
- Views: 5489
I have the exact same issue, also on 6.3.1, Solaris 10, Oracle, etc and an open case with BMC on the topic. No firm resolution yet. We have noticed that the number of semaphores used by the ctlm role seems to grow by 1 per day. The semaphore appears to be created by the CA process. clean_semaphores ...
- 11 Jan 2010 5:15
- Forum: Job Definition
- Topic: %%PATH Autoedit variable Overrides Shell PATH
- Replies: 5
- Views: 5840
- 08 Jan 2010 9:35
- Forum: Job Definition
- Topic: %%PATH Autoedit variable Overrides Shell PATH
- Replies: 5
- Views: 5840
- 08 Jan 2010 9:33
- Forum: Job Definition
- Topic: %%PATH Autoedit variable Overrides Shell PATH
- Replies: 5
- Views: 5840
- 08 Jan 2010 8:52
- Forum: Job Definition
- Topic: %%PATH Autoedit variable Overrides Shell PATH
- Replies: 5
- Views: 5840
%%PATH Autoedit variable Overrides Shell PATH
It seems as though using an autoedit variable named %%PATH in a job definition causes the corresponding autoedit value to be used as the actual shell path for the job. But I can't seem to find any reference to this in the Job Parameter and Variable Reference Guide. If you have seen this documented s...
- 27 Mar 2009 3:14
- Forum: Job Definition
- Topic: Exotic Month-day Scheduling Rule
- Replies: 3
- Views: 2193
Exotic Month-day Scheduling Rule
Is it possible to use scheduling criteria to run a job as follows:
Every day of the month except the 24th up to but not including the last Friday of the month.
I know how to do one or other other using "month-day" rules, but not both.
Grateful for any help or pointers.
Bill C
Every day of the month except the 24th up to but not including the last Friday of the month.
I know how to do one or other other using "month-day" rules, but not both.
Grateful for any help or pointers.
Bill C
- 05 Feb 2009 3:40
- Forum: Reporting
- Topic: Does anyone have paging setup with Control_M
- Replies: 2
- Views: 2448
Depending how high or low tech you want to be, most paging systems allow pages to be triggered via an email. If that's the case, you can simply define a SHOUT destination to be an email script [e.g. mailx for Unix or blat for Windows/DOS] and define the the job to Shout to that destination when it f...
- 23 Dec 2008 5:57
- Forum: Control-M Enterprise Manager
- Topic: EM GUI Client Command Line Arguments
- Replies: 2
- Views: 2666
Thanks. I had actually tried that but I still get the "popup" box prompting me for a password even if I specify -p. And regardless of what I put in the -m field, the host name drop-down list still preserves whatever value I had entered when I last logged in. I'm assuming its some security setting I ...
- 23 Dec 2008 4:25
- Forum: Control-M Enterprise Manager
- Topic: EM GUI Client Command Line Arguments
- Replies: 2
- Views: 2666
EM GUI Client Command Line Arguments
I would like to setup Windows Shortcuts to login to the EM GUI Client without having to specify username, password or GUI Server. According to EMGUI Help I should be able to do this with the -u, -p, and -m parameters respectively however it seems I am always prompted for a password and the -m parame...
- 08 Mar 2008 3:40
- Forum: Exploitation / Operation
- Topic: time between job
- Replies: 5
- Views: 4075
We had this problem too and were able to solve by changing the default "sleep time" For the TR(acker) and SL (selector) processes. By default, the sleep time is 30 seconds, which means that, depending on the timing of job completion, you could wait up to a minute just for them to figure out that Job...