On Tue, Dec 19, 2017 at 9:51 PM, Jon Perryman <[email protected]> wrote:
> > I wrote: TSO has the alloc command which can easily be > used in clists. > It exists because of MVS UNIX. > MVS UNIX has nothing to do with TSO ALLOC. When I moved the C FOPEN text, > I forgot to delete the MVS UNIX senstence. It's FOPEN dynamic alloc only > exists because of MVS Unix and is considered a production MVS security > exposure. Most production languages do not support dynalloc for this reason. > 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 HLASM doesn't. REXX does & doesn't (EXECIO won't but you can use BPXWDYN before EXECIO). I can't find the z/OS FORTRAN documentation right now. Most of the z/OS UNIX language will because they use the C "fopen()". Interestingly, the Rocket Software Python port does not at this time. But then, it doesn't support DD statements either, only UNIX files (I guess via C's "open()" instead of "fopen()"). -- I have a theory that it's impossible to prove anything, but I can't prove it. Maranatha! <>< John McKown
