[Migrated content. Thread originally posted on 29 September 2011]

Net Express allows define in Working-storage section array with maximal size 256 Mbyte.
What limitation has MF VC R4 in this case?
Thanks.

Hi Sircobol,

Object Maximum Size
Total No limit
Data Division 256 Mbytes
Procedure Division 816 Mbytes
Local-Storage Section Platform specific
COBOL segment 16 Mbytes



Link

---

[Migrated content. Thread originally posted on 29 September 2011]

Net Express allows define in Working-storage section array with maximal size 256 Mbyte.
What limitation has MF VC R4 in this case?
Thanks.

Yes, these documented limits have not changed since Net Express.

Although the compiler will actually allow for larger data items and data divisions much larger than 256MB it is advisable to keep your programs within the documented limits as the behavior of using larger items is at the moment undefined.

Thanks.

---

[Migrated content. Thread originally posted on 29 September 2011]

Net Express allows define in Working-storage section array with maximal size 256 Mbyte.
What limitation has MF VC R4 in this case?
Thanks.

It is a great pity.
256 MB corresponds only 3% from RAM 8GB on ordinary PC.
Obsolete limitation...

Dear developers of MF VC, please, keep up with yours competitors!

---

[Migrated content. Thread originally posted on 29 September 2011]

Net Express allows define in Working-storage section array with maximal size 256 Mbyte.
What limitation has MF VC R4 in this case?
Thanks.

It is a great pity.
256 MB corresponds only 3% from RAM 8GB on ordinary PC.
Obsolete limitation...

Dear developers of MF VC, please, keep up with yours competitors!

---

[Migrated content. Thread originally posted on 29 September 2011]

Net Express allows define in Working-storage section array with maximal size 256 Mbyte.
What limitation has MF VC R4 in this case?
Thanks.

We are currently in the process of updating the documentation so that it reflects the actual limitations (or lack thereof) of the Visual COBOL product.

This will be available in a future product release.

The compiler is now capable of generating both 32-bit and 64-bit code to run under native Windows or Unix/Linux environments as well as generating 32-bit and 64-bit code to run under managed .NET or JVM environments so the compiler dynamics have changed but have not yet been fully documented.

Our question to you would be, in which environment do you wish to deploy, native or managed code?

We are also happy to work directly with you to resolve this using other techniques, for example, using dynamic memory allocation.

Thanks.

---

[Migrated content. Thread originally posted on 29 September 2011]

Net Express allows define in Working-storage section array with maximal size 256 Mbyte.
What limitation has MF VC R4 in this case?
Thanks.

Dear Chris,
I'm ready collaborate with you directly.
I wish to deploy native Windows environment for generating 32-bit and (it is preferable) 64-bit code.

At the time I use NetExpress 5.1.
If you like, we will work in testing mode, because as yet I cannot buy MF VC R4.
Dynamic memory allocation method may be quite acceptable.

My Email: aristos-a@mail.ru
Best regards,
Valentin.

---