B
bleicher
Guest
The issue you are experiencing is a bug. The language team's model / goal is that rcode should always execute properly in a previous version (same major release) as long as the application does not take advantage of a new feature. In the example noted above the program is not utilizing a new feature and therefore this should have worked properly in a previous release (11.1. for example). A defect (PSC00286613 ) was logged to track this issue. The problem is that the compiler now stores the PAUSE value as a Decimal (in order to store sub-second values) and not an Integer (as it used to). When developer takes an 11.3 generated rcode file and deploys it in an 11.1 environment, the AVM (runtime) wants to interpret the PAUSE value as an Integer but it is stored in the rcode as a decimal. Hence the error.
Continue reading...
Continue reading...