Runtime > Online Changes > Client Side Online Changes > Handling Cicode Changes during Runtime

Handling Cicode Changes during Runtime

You are able to reload a page at runtime even if the associated Cicode library has changed. However, the system will compare the Cicode library that was used to create the page to the one that is in memory. If they do not match, the hardware alarm "Cicode library timestamp differs" is raised. The page is displayed, but the Cicode that is executed will be from the memory version of the Cicode library and not the latest compiled version.

A restart of the client is needed to update the Cicode library version to the latest compiled version.

  

UNINTENDED EQUIPMENT OPERATION

Restart the client process if the hardware alarm "Cicode library timestamp differs" is raised after a page is opened.

Failure to follow these instructions can result in death, serious injury, or equipment damage.

Note: A hardware alarm of "Cicode library timestamp differs" will be raised if the Cicode library used by a page has a different timestamp from the one in memory. The timestamps will be different if the project has been fully recompiled, the project has been incrementally recompiled after the page has been modified, or if the project has been incrementally recompiled after any Cicode has been modified.

It is recommended that the ServerGetProperty Cicode function be used with the LibRDBMemTime and LibRDBDiskTime properties to check if there is a change to the Cicode library before attempting a reload. Following a reload, it is recommended that you check the corresponding server's syslog.dat file for any reload messages.

See Also

Client Side Online Changes

PageDisplay

PageGoTo

Published June 2018