shareable image with dynamic data

[Richard J Maher]

Hi,

To me it sounds like you need $crmpsc or a combo of writer - $crmpsc and reader - $mpgblsc. No, it's not easy but then it's not rocket science either. I honestly lament for VMS and the nay-sayers that have made it look so hard :-( I don't have a C example but I can dig up a COBOL one if you're interested.

I'm guessing that you're just trying to avoid a re-build/compile every time your memory needs expanding? If so, just stay away from COMMONs and stick the global area dimensions in a parameter-file/logical-name and re-cycle the servers/application when need be.

Then there's also VLM and the Reserved-Memory Registry if you're feeling adventurous? Whatever happened to Christian Moser eh?

Cheers Richard Maher

[Hoff]

>I go one step further than Hoff..

I'd consider firing the guy that tried to implement a COMMON-based solution on a VMS project I was managing.

[jaydee_1]

Thanks a lot to every one for sharing your views on the subject.

It looks like global sections(on first glance it does seem like rocket science) is a possible solution .

Thanks again.Cheers to the ITRC forum.