It is currently 12 Dec 2017 12:58


Post new topic  Reply to topic  [ 4 posts ] 
Author Message
PostPosted: 10 Oct 2006 7:05 
Offline
Nouveau
Nouveau
User avatar

Joined: 10 Oct 2006 12:00
Posts: 5
I have 2 parallel environment (Em-CTM-Agent).
I have some cases I need to use dependencies between jobs which belongs to a different Control-M/Server, which are not linked to the same EM.
Question: do you have an idea how to simulate the Global Condition feature, in order to replicate a condition posted by a first Control-M/Server, to another Control-M/Server ?

May thanks in advance for your solution or idea.

Mamy_r


Top
   
 Post subject:
PostPosted: 10 Oct 2006 8:11 
Offline
Nouveau
Nouveau
User avatar

Joined: 26 Apr 2005 12:00
Posts: 696
Location: PARIS
Hi,

It's not so simple. There is a solution, may be.

Create a job waiting for the condition from the first Control-M Server.
That job could execute ctmcondb command on the second Control-M Server to add the same condition.

To do that, of course you need to install a Control-M Agent on the box where the second Control-M Server is installed, linked with the first Control-M Server.


Top
   
 Post subject:
PostPosted: 11 Oct 2006 2:30 
Offline
Nouveau
Nouveau
User avatar

Joined: 10 Oct 2006 12:00
Posts: 5
Merci Franck for your idea.
It's true it's not that easy.
Your idea is one of the ideas I am currently thinking about, see below the current list of ideas:
1- Create an additional job in the table, which adds a condition with ctmcontb, in the second CTM/Server.
Advantage: simple
Disadvantage: 1) require to install an agent on each source Control-M/Server. 2) need to update each Table which require that feature

2- Develop a script which does a Sql query in the EM Global Condition table. This script is ran on the source EM unix account in order to share it's current Database client with it's profile
Advantage: No need to update Tables, we trap the GC at EM level
Disadvantage: 1) require to install an agent on source Control-M/EM Server.

3- Develop a script which does a Sql query in the EM Global Condition table. This script is ran on Target unix server
Advantage: No need to update Tables, we trap the GC at EM level
Disadvantage: 1) require to install a database client on this Target Unix account.

4- Develop a script which analyzes the GCS_LOG file updated at the Source EM account when an event occurs (new incoming GC)
Advantage: No need to update Tables, we trap the GC at EM level. No need to install any software
Disadvantage: I don't know yet.

I am likely going for the 4th idea, still investigating for any potential issues or other ideas.

Mamy_r


Top
   
 Post subject:
PostPosted: 11 Oct 2006 4:58 
Offline
Nouveau
Nouveau
User avatar

Joined: 26 Apr 2005 12:00
Posts: 696
Location: PARIS
Hi Mamy,

This is another idea.
If you give some rights between your Control-M Servers to be able to run rexec or rsh, or something like that. It will be simple to create a script to execute ctmcontb on the both server in the same time with the same parameters.

No need to add antother Control-M agent
No nee SQL client and database script, being able to be dangerous for the integrity of your database.


Top
   
Display posts from previous:  Sort by  
Post new topic  Reply to topic  [ 4 posts ] 

All times are UTC+01:00


Who is online

Users browsing this forum: No registered users and 1 guest


You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot post attachments in this forum

Search for:
Jump to:  
Powered by phpBB® Forum Software © phpBB Limited
The site created by Franck YOT. Images, logo, content and trademarks about Control-M products are property of BMC Software.
All the comments are property of their posters. Images, logo, content and design are © copyright by Scheduler-Usage.com. All Rights Reserved