Shutting down a TCCS/FCC instance

Whenever you stop a TCCS/FCC instance, it is important that the shutdown process is as clean as possible. You may want to stop a TCCS/FCC instance because: It is no longer needed. You need to stop and restart the instance to receive new configuration information. Regardless of why you stop an FCC, remember that the FCC runs within the TCCS container process. Stopping an FCC also stops the TcServerProxy and TcMEM processes. Before stopping a TCCS/FCC instance, close all client applications and wait 10 seconds. Note Siemens Digital Industries Software does not recommend using the operating system kill command or the Windows Task Manager to stop an FCC unless safer methods have failed. Doing so can cause issues with the FMS fast cache, the FCC cache lock, the TCCS process lock, and any active FCC/TcServerProxy/TcMEM transactions. Warning On Windows, JRE shutdown hooks are not honored, preventing the FCC from closing cleanly. If the TCCS/FCC instance remains running when users log off (or shut down) these operating systems, the FCC segment cache may be corrupted. Siemens Digital Industries Software recommends you add the fccstat -kill command to all user logoff scripts and to any relevant Windows shutdown scripts for Teamcenter clients running on these operating systems. The following methods for stopping an FCC are listed in the order by which they reduce the risk of corrupting the cache or creating a stuck lock file. If after stopping an FCC, it does not properly restart, reset the user’s FCC environment. Method 1 Shut down TCCS/FCC on Windows systems using the using the TCCS system tray icon. Shutting down using the TCCS closes TCCS and all of the applications it contains. Siemens Digital Industries Software recommend this method on Windows systems. Ensure the Windows system tray settings are configured to allow the TCCS icon to appear in the system tray. Method 2 Run FMS_HOME\bin\fccstat -stop. This method stops a TCCS/FCC instance if it is idle. The system confirms that the user has shut down all the attached client processes before stopping the TCCS. If non-idle clients are connected to the FCC or other TCCS applications, a message appears and the FCC is not stopped. If you receive this message, confirm that all client applications are disconnected from FCC/TCCS, wait 10 seconds, and retry. Note An FCC client is non-idle if it holds an open FCC file handle, an open segment cache handle, or an open pipe connection that has made a request within the past 5 to 10 seconds. This method is effective 90 percent of the time and results in the cleanest possible shutdown. The FCC can be restarted afterward with no data loss. Method 3 Run FMS_HOME\bin\fccstat -kill. This method stops a TCCS/FCC if it is idle or non-idle, as long as it is responsive to pipe commands. The system does not confirm that the user has shut down all the attached client processes before stopping the FCC. The system does not display a message that other client applications are connected. Any transactions in progress at the time the FCC is terminated may fail. This can have a negative effect on the connected client applications. This method is effective 99 percent of the time. The FCC can typically be restarted afterward with no data loss. Method 4 If a TCCS/FCC instance is not responsive to FCC pipe commands, it may report FCC Offline though the TCCS/FCC process is running. In this situation, use the tspstat or tcmemstat utility to stop the shared TCCS process. Method 5 (only if TCCS/FCC running in foreground) Press Ctrl+C in the FCC foreground window. The foreground window is available from the interface only if TCCS/FCC is running in a visible command prompt window or shell. (This is not usually the case.) Alternatively, close the TCCS command prompt window (Windows only). Note If the FCC is running in a hidden window, and you have system tools access, you can locate the hidden FCC window and send it a WM_CLOSE message (Windows only). This method is highly effective and usually results in a clean shutdown of the FCC. Method 6 (Linux only) Run the operating system kill command without the -9 option. This method stops an FCC if it is idle or non-idle, even when it is not responsive to pipe commands. This method stops the FCC as cleanly as possible. The effect is similar to method 2, but it is possible that file handles become stuck or that cache states are lost. Method 7 (Linux only) Run the operating system kill command with the -9 option. This method performs a hard stop on the FCC. Usually, the contents of the FCC fast cache (segment cache) are lost. Occasionally, the FCC lock file becomes stuck. Method 8 (Windows only) From the Task Manager, select the user’s FCC process and click End Process. This method performs a hard stop on the FCC. Usually, the contents of the FCC fast cache (segment cache) are lost. Occasionally, the FCC lock file becomes stuck.