If you install the fabric node on a system which already has ITM processes running, the RunInfo and RunInfo_Description files are overwritten. While all the ITM processes remain running, if you do a ./cinfo -r it will only show the agent as running.
So first need to determine if the fabric node is allowed to be installed on a system which already has ITM processes running. If so the data in these files need to be preserved.
Pinned topic RunInfo/RunInfo_Description files modified incorrectly
Answered question This question has been answered.
Unanswered question This question has not been answered yet.
Updated on 2012-09-20T18:45:54Z at 2012-09-20T18:45:54Z by PaulRuocchio
RM03_Chris_Barlock 270001RM0343 Posts
Re: RunInfo/RunInfo_Description files modified incorrectly2012-09-20T17:01:33ZThis is the accepted answer. This is the accepted answer.Sandra, no, you can't do that. Our fabric node includes an OS agent & we just overwrite /opt/IBM/ITM. We might have to reconsider this...
PaulRuocchio 060001EXFU3 Posts
Re: RunInfo/RunInfo_Description files modified incorrectly2012-09-20T18:45:54ZThis is the accepted answer. This is the accepted answer.
- RM03_Chris_Barlock 270001RM03
Chris is right, CCM was never intended to be installed in or with an existing ITM environment. Obviously we need to at least update our docs to indicate that, but we will also need to get a little more defensive in our install. We'll look at ways to prevent a CCM install on an existing ITM install.