WP1 Cold starts without being explicitly given a command to do so after being manually upgraded (not using ZDU)
Steps to reproduce
1) Install a 12.3.3+hf4 system (I used the One Installer)
2) Log in, use a few things so it's no longer "fresh"
3) Stop the WPs and CPs
4) Upgrade the components:
Utility
AutomationEngine
ServiceManagerDialog
Load the initialdata
5) Start the smgr
6) Note ucsrv.ini file still shows STARTMODE=NORMAL
7) Open smgrdia, point to second smgr port
8) Right-click single WP and choose "Start with SystemStop"
Expected behavior
WP should start with normal start (and systemstop), noted by log entries:
20201120/202306.840 - STARTMODE=NORMAL
...
20201120/202310.729 - U00011817 Server 'AUTOMIC#WP001': Started in mode 'WARM', run mode = 'PRIMARY'.
Actual behavior
WP starts COLD (with systemstop), noted by log entries:
20201120/201856.276 - U00003400 Server 'AUTOMIC#WP' version '12.3.4+hf.1.build.1602180067774' (changelist '1602152325') started.
...
20201120/201856.276 - STARTMODE=NORMAL
...
20201120/201856.292 - U00003492 Server has been started on Host 'lvntest021697' ('10.74.120.141') with process ID '12008'.
...
20201120/201901.547 - U00011817 Server 'AUTOMIC#WP001': Started in mode 'COLD', run mode = 'PRIMARY'.
SMGR log shows:
20201120/201856.139 - U00022004 Starting process 'WP1' ...
20201120/201856.139 - U00022005 ... with command line 'C:\automic\Automation.Platform\ServiceManager2\bin\..\..\AutomationEngine\bin\UCsrvwp.exe -IC:\automic\Automation.Platform\ServiceManager2\bin\..\..\AutomationEngine\bin\ucsrv.ini -svc%port% -parm"SystemStop=Yes"'.
20201120/201856.139 - U00022006 ... and start directory 'C:\automic\Automation.Platform\ServiceManager2\bin\..\..\AutomationEngine\bin'.
20201120/201856.192 - U00022007 Process 'WP1' (ID '12008') successfully started.
20201120/201856.223 - Window: Hnd=006b00f0, Title='UC4 WP-Server'
Release : 12.3
Component : AUTOMATION ENGINE
This is as designed and has been in place for all 12.x versions.
Any time that the initialdata is upgraded manually (via the load utility), a COLD start will be done automatically. This is done when the results of the following statement come back with no rows:
SELECT * FROM MQLS WHERE MQLS_ID='WARMSTRT' AND MQLS_Version=0
Using the ZDU to upgrade will not cause a COLD start (it will continue running as-is and not clear MQ tables, set inconsistent statuses, etc...).
The documentation also reflects this as seen here:
http://docs.automic.com/documentation/webhelp/english/AA/12.3/DOCU/12.3/Automic%20Automation%20Guides/help.htm#Installation_Upgrade/Upgrade_Intro.htm
"If you upgrade the AE manually without using ZDU, the WPs in the new version always start in cold mode."