Francois, Hope this helps. Question1: will the new block be moved to the end of the memory or will = it be split onto two areas? The compiled sequence code for each sequence block must run in a = contiguous segment of memory in the CP. Each time a sequence is = compiled and you say "DONE" in ICC, the previous code for the sequence = is removed from memory and the CP finds a contiguous segment to load and = run the new code. If the compiled size of the new code is too large to = fit back in the previous space, the CP will find a free segment to put = it in somewhere else. .CSPACE reserves contiguous memory space in the = CP even if the code doesn't currently use all of it. This is a way to = insure that your sequence will have a contiguous memory segment large = enough to install should you expand the code in the future. If you look = at the CPLBUG:Station block detail display, it shows both "Total Free = Memory" and the "Largest Segment" available. Question2: If this maneuver creates some empty spaces within the memory, = will these spaces be filled with new blocks or existing one which have = been modified? Spare memory spaces will be managed and reused by the CP when needed. Question3: What happen if I create a block which need more space than = pre-allocated with the CSPACE parameter? We have done this in past releases and we received an error when trying = to install the sequence. I'm not sure if that has changed or not. Call = Foxboro and ask. Question4: Will this problem occur in case of Fault tolerant modules? = (is the memory "snapshot" of the two CPFT necessary the exact copy?) I am pretty sure that the memory storage locations of the two FT modules = is identical. Tom VandeWater Dow Corning Corp. Carrollton, KY USA -----Original Message----- From: foxboro-bounce@xxxxxxxxxxxxx [mailto:foxboro-bounce@xxxxxxxxxxxxx] = On Behalf Of "Perrot, Fran=E7ois" Sent: Thursday, October 06, 2005 10:46 AM To: foxboro@xxxxxxxxxxxxx Subject: [foxboro]=20 Content-Type: text/plain; charset=3D"iso-8859-1" Content-Transfer-Encoding: quoted-printable =3D20 Dear all, =3D20 I am facing a problem regarding the CP60 memory management when using = =3D lots of sequential blocks. =3D20 According my understanding of the Foxboro documentation, the parameter CSPACE is booking a certain amount of memory within the limit of = 32Kb.=3D20 =3D20 e.g. I would like to modify an existing sequential block (IND) using CSIZE=3D3D20kb and CSPACE=3D3D0 with the new parameters like = CSIZE=3D3D20kb =3D and CSPACE 30kb =3D20 Question1: will the new block moved to the end of the memory or will it = =3D be split onto two areas? =3D20 Question2: If this manoeuvre creates some empty spaces within the =3D memory, will these spaces be filled with new blocks or existing one which have = =3D been modified? =3D20 Question3: What happen if I create a block which need more space than pre-allocated with the CSPACE parameter? =3D20 Basically, the SHRINK command affects the work file. Is there any way = =3D to do the same on the CP's memory without doing a reboot. Will this problem occurs in case of Fault tolerant modules. (is the memory "snapshot" of = =3D the two CPFT necessary the exact copy?) =3D20 Thanks. =3D20 Fran=3DE7ois PERROT =3D20 <http://www.fp-consulting.com>=3D20 =3D20 =3D20 Francois Perrot Consultant=3D20 FP consulting=3D20 <mailto:francois.perrot@xxxxxxxxxxxxxxxx> =3D francois.perrot@xxxxxxxxxxxxxxxx=3D20 mobile:=3D20 (060) 941-2129=3D20 =3D20 =3D <https://www.plaxo.com/add_me?u=3D3D17180619476&v0=3D3D1479401&k0=3D3D198= 68609=3D 79> Add me to your address book... <http://www.plaxo.com/signature> Want a signature like this? =3D20 -- No attachments (even text) are allowed -- -- Type: image/jpeg -- File: image001.jpg =20 =20 _______________________________________________________________________ This mailing list is neither sponsored nor endorsed by Invensys Process Systems (formerly The Foxboro Company). Use the info you obtain here at your own risks. Read http://www.thecassandraproject.org/disclaimer.html =20 foxboro mailing list: //www.freelists.org/list/foxboro to subscribe: = mailto:foxboro-request@xxxxxxxxxxxxx?subject=3Djoin to unsubscribe: = mailto:foxboro-request@xxxxxxxxxxxxx?subject=3Dleave =20 _______________________________________________________________________ This mailing list is neither sponsored nor endorsed by Invensys Process Systems (formerly The Foxboro Company). Use the info you obtain here at your own risks. Read http://www.thecassandraproject.org/disclaimer.html foxboro mailing list: //www.freelists.org/list/foxboro to subscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=join to unsubscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=leave