On Thu, Dec 21, 2017 at 12:39 PM, Jon Perryman <[email protected]> wrote:

> Thanks for pointing out dynalloc in Cobol. A few decades since I actually
> looked at these languages. In fact, The only LE programming language I've
> used is C.
> Do you know if companies allow the use of this feature in production? For
> those that don't, how do they protect themselves against intentional abuse
> of dynalloc in situations where they can gain read access to data that
> would otherwise have been protected? Is it a simple code review? Or do they
> say it's allowed on their Unix systems which are far less protected?
>

​I, personally, have _NO_ idea if anybody uses this or, if so, how they use
it. I just remembered seeing it and decided to make an "off the cuff"
observation. The programmers that I work with would most likely do a "deer
in the headlights" act if I tried to talk to the about dynamic allocation
in COBOL with them. They're not stupid, but they just do things the tried &
true way. ​



> Thanks, Jon.
>     On Wednesday, December 20, 2017 3:13 AM, John McKown <
> [email protected]> wrote:
> ​Which "production" languages would that be? Enterprise COBOL and PL/I
> _both_ support dynamic allocation of files.
>
> COBOL ref:
> https://www.ibm.com/support/knowledgecenter/en/SS6SG3_6.2.
> 0/com.ibm.cobol62.ent.doc/PGandLR/ref/rliosass.html
>
> PL/I ref:
> https://www.ibm.com/support/knowledgecenter/SSY2V3_5.1.0/
> com.ibm.ent.pl1.zos.doc/pg/allodynallo.html
>
>
>


-- 
I have a theory that it's impossible to prove anything, but I can't prove
it.

Maranatha! <><
John McKown

Reply via email to