- Control-M/Enterprise Manager Global Condition Server (GCS) definition is configured to be "UP" on Control-M Configuration Manager (CCM)

- When started via CCM or manually, the GCS process will start but shut down shortly after.

- Following error is found in the gcs_diag log:
1025_03:31:13.562, T@12, "GCS is up...", [INFO], T:sewadcbmccon01p, , com.bmc.ctmem.gcs.Gcs, ::GCS:start, ,
1025_03:31:13.562, T@19, "start main loop", [INFO], T:com.bmc.ctmem.common.emctmrepository.EMCTMRepository, , com.bmc.ctmem.common.emctmrepository.EMCTMRepository, ::EMCTMRepository.run, ,
1025_03:31:13.574, T@16, "connect EM2EMLink [_host=sewadcbmccon01p/ _port=54479 #0] using addr: sewadcbmccon01p/10.100.11.40:54479", [INFO], T:NioProcessor-14, , com.bmc.ctmem.common.emlink.EM2EMLink, ::operationComplete, ,
...
1025_03:31:15.900, T@22, "stop component", [INFO], T:pool-4-thread-1, , com.bmc.ctmem.common.ctl.CTLRequestHandler, ::stop, ,
1025_03:31:15.904, T@12, "ctlserver shutdown.", [INFO], T:sewadcbmccon01p, , com.bmc.ctmem.common.EmComponent, ::main, ,
1025_03:31:16.565, T@19, "end main loop", [INFO], T:com.bmc.ctmem.common.emctmrepository.EMCTMRepository, , com.bmc.ctmem.common.emctmrepository.EMCTMRepository, ::EMCTMRepository, ,
1025_03:31:16.566, T@12, "shutdown CTLClient endpoint.", [INFO], T:sewadcbmccon01p, , com.bmc.ctmem.common.emlink.EmClientLinkEndPoint, ::CTLClient, ,
1025_03:31:16.566, T@12, "ctlclient shutdown.", [INFO], T:sewadcbmccon01p, , com.bmc.ctmem.common.EmComponent, ::main, ,

or

0708_01:52:13.188, T@13, "life check return code: RC_SUCCESS", [WARNING], T:<Control-M/Enterprise Manager Hostname, , com.bmc.ctmem.common.ComponentCanRunCtl, ::canRun, ,
0708_01:52:13.188, T@13, "component type GCS - GCS is running. host <Control-M/Enterprise Manager Hostname>, ctlhost: <Control-M/Enterprise Manager Hostname port 59095 , exit.", [WARNING], T:<Control-M/Enterprise Manager Hostname, , com.bmc.ctmem.common.ComponentCanRunCtl, ::canRun, ,
0708_01:52:13.188, T@13, "return value false", [INFO], T:<Control-M/Enterprise Manager Hostname, , com.bmc.ctmem.common.ComponentCanRunCtl, ::canRunAndRegister, ,
0708_01:52:13.188, T@13, "other such component is running. exit.", [WARNING], T:<Control-M/Enterprise Manager Hostname, , com.bmc.ctmem.common.EmComponent, ::registerAndRunCompStoppableByCtlHandler, ,

- When the Control-M/Enterprise Manager Configuration Manager is being debug, the following error will show in the maint_diag log:
25/10/2018    10:02:08.617    [5]    tcomponentselector    TComponentSelector::Init    Do state-machine activity for component key={CMS/CTM/CMS} - Up ==> Ignored
25/10/2018    10:02:08.617    [5]    tcomponentselector    TComponentSelector::DoIgnored    Ignore EM component key={CMS/CTM/CMS}
25/10/2018    10:02:08.617    [5]    tcomponentselector    TComponentSelector::Init    Do state-machine activity for component key={Forecast Server/CTM/CTM} - Up ==> Up
25/10/2018    10:02:08.617    [5]    tcomponentselector    TComponentSelector::Init    Do state-machine activity for component key={GCS/CTM/GCS} - Down ==> Down
25/10/2018    10:02:08.617    [5]    tcomponentselector    TComponentSelector::Init    Do state-machine activity for component key={GUI Server/CTM/CTM} - Up ==> Ignored
25/10/2018    10:02:08.617    [5]    tcomponentselector    TComponentSelector::DoIgnored    Ignore EM component key={GUI Server/CTM/CTM}
25/10/2018    10:02:08.617    [5]    tcomponentselector    TComponentSelector::Init    Do state-machine activity for component key={Gateway/CTM/CTM} - Up ==> Up
25/10/2018    10:02:08.617    [5]    tcomponentselector    TComponentSelector::Init    Do state-machine activity for component key={Self Service Server/CTM/CTM} - Up ==> Up
25/10/2018    10:02:08.617    [5]    tcomponentselector    TComponentSelector::Init    Going to sleep for 10sec

1. Launch Control-M Configuration Manager

2. Put all Control-M/EM Components to DOWN and wait for the status to be DOWN

3. Stop the Control-M/EM Configuration Agent using Windows Service Console
   
4. Verify that the Control-M/Enterprise Manager Global Condition Server (GCS) Java process is not running when GCS is stopped
i.    Launch Windows Task Manager
ii.  Check that there is no GCS process running (JAVA process)
      - Launch Windows Task Manager
      - Right click the column headers and select the "command line" column which will display the program that is started using the Java process
      - Check on various Java process and ensure that there is no java process started for emgcsrv (GCS) process
        For example,
  iii. If found, kill the Java process

5. Verify that the Control-M/Enterprise Manager Configuration Agent (emmaintag.exe) process is not running using Task Manager
    If found, kill the process

6. Start Control-M/EM Configuration Agent using Windows Service Console
    (Control-M/EM Configuration Management Server and naming Service should be started automatically)

7. Launch Control-M/EM Control-M Configuration Manager (CCM) and start all Control-M/EM components