ABSOLUTELY! 


CharlesSent from a mobile; please excuse the brevity.
-------- Original message --------From: "Swarbrick, Frank" 
<[email protected]> Date: 12/21/17  5:29 PM  (GMT-05:00) To: 
[email protected] Subject: Re: [EXTERNAL] Re: Macro processor 
Doesn't RACF or other access control protect this data equally?

-----Original Message-----
From: IBM Mainframe Assembler List [mailto:[email protected]] On 
Behalf Of Jon Perryman
Sent: Thursday, December 21, 2017 11:40 AM
To: [email protected]
Subject: [EXTERNAL] Re: Macro processor

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?
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



The information contained in this electronic communication and any document 
attached hereto or transmitted herewith is confidential and intended for the 
exclusive use of the individual or entity named above. If the reader of this 
message is not the intended recipient or the employee or agent responsible for 
delivering it to the intended recipient, you are hereby notified that any 
examination, use, dissemination, distribution or copying of this communication 
or any part thereof is strictly prohibited. If you have received this 
communication in error, please immediately notify the sender by reply e-mail 
and destroy this communication. Thank you.

Reply via email to