Why do you see many of the following message in your TEMS logs?
kglcmsrv.c,549,"MonitorCMS") <0x11BFCE4,0x7> CMSMSG_Receive
+50814ACE.0002 00000000 43484543 4B4453
What is happening is that the cms.exe and kdsmain.exe applications are writing to the same log file. The "MonitorCMS" messages are normal in the cms log file. It is not normal in the TEMS log file (*_ms_*).
The problem lies with the KBB_RAS1_LOG variable in the TEMS configuration files. Both cms.exe and kdsmain.exe read the same configuration files. Thus if you do not set up the KBB_RAS1_LOG variable correctly, then both applications can end up writing to the same log file. For example:
KBB_RAS1_LOG=C:\IBM\ITM\logs\$(sysid)_MS_$(sysutcstart)-.log INVENTORY=C:\IBM\ITM\logs\$(sysid)_MS.inv MAXFILES=32 LIMIT=8 COUNT=5 PRESERVE=1
Because "_MS_" is hardcoded in the above example, both executables may end up writing to the same log file.
Similarly, the "systask" substitution parameter does not produce the expected result on Windows. If you look at the header block on the RAS1 logs for the cms and TEMS application, you will see they have the task name of "cms" on Windows. So the following variable setting on Windows:
KBB_RAS1_LOG=C:\IBM\ITM\logs\$(sysid)_$(systask)_$(sysutcstart)-.log INVENTORY=C:\IBM\ITM\logs\$(sysid)_$(systask).inv MAXFILES=32 LIMIT=8 COUNT=5 PRESERVE=1
Both the cms and kdsmain application may write to the same log file.
In the first variable above, do not use a hardcoded value. Instead, replace "MS" with "$(systask)" or "$(syspgm)" in the two places that "MS" occurs. Most documentation refers to "systask" here, but that does not always work satisfactorily on Windows. Use "syspgm" on Windows instead of "systask". When you use "syspgm", the filename of the TEMS logs will be similar to *_kdsmain_*.log. You should end up with something like the following for Windows version of the variable:
KBB_RAS1_LOG=C:\IBM\ITM\logs\$(sysid)_$(syspgm)_$(sysutcstart)-.log INVENTORY=C:\IBM\ITM\logs$(sysid)_$(syspgm).inv MAXFILES=32 LIMIT=8 COUNT=5 PRESERVE=1
This may apply to other platforms, but I have not investigated that. It is safe to use "syspgm" on all platforms.