Lifecycle margin versus actual station database resource count in Niagara R2.


Lifecycle margin versus actual station database resource count in Niagara R2.

Product Line

TAC I/A Series


Niagara R2


When pasting objects that are over the maximum allowance size, it will not paste the object because the copy or cut maximum size is depend on the Lifecycle margin.


The UNC-410, UNC-510, and UNC-520 platforms all have a resource count limitation of 600,000.  The TRD-NXT has a resource count limit of 2,500,000. The total number of available resources is the same regardless of support for Web services. The (Search > Resource Count) function under the WorkPlace Pro Search menu item will count the number of resources used. The count is performed from the object currently selected on the JDE tree and includes all child objects.

By selecting the station's root name, the resource value for the entire station database will be provided. The dialog box with the information provides the calculated actual Resource count and also will indicate the Lifecycle margin: 20,000. The Lifecycle margin is a JDE term that specifies the maximum size (in resource count) of any “cut” or “copy” permitted in a running station. A cut or copy effectively creates a temporary new tree of objects within the memory of the host. This mechanism is used to support the JDE's “undo” operation (Edit > Undo).

As an example, try to cut & paste something and it won't be allowed because of resources.  After checking, for instance, that there is a 43,000 resource count with a lifecycle margin of 20,000, what is happening is that the cut and paste has a total resource count higher than 20,000 which is the max. Perform the cut and paste in smaller portions.