Horsefeathers. Agreed that it bypasses JES3 resource pre-allocation, but aside from that the rest of that rant is bunkum. Sophisticated schemes for dynamically reading and collecting into one place asynchronous and only sometimes presented client transmissions into nightly production batch runs is one important use that would be impossible or at least difficult to automate without dynamic allocation.
It's all in the tools you use to control it flexibly and reliably. SMOP. No security risk that I can see, presuming proper operation control and approval procedures of course. Peter -----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of Paul Gilmartin Sent: Wednesday, December 20, 2017 5:38 PM To: [email protected] Subject: Disable DYNALLOC? From a recent thread (rant?) in ASSEMBLER-LIST: ... Do you stand by "SVC 99 for good measure"? Generally, products do not implement it for good reason. Irrelevant in CICS and IMS. In batch, it bypasses job scheduler, job restart, violates production control requirements, bypasses JES3 resource management and potentially poses a production security risk. TSO has the alloc command which can easily be used in clists. It exists because of MVS UNIX. ... Disregard the anachronism in the last sentence. If, hypothetically, DYNALLOC except by initiator is so harmful as to be prohibited in production jobs, is there any way to do so? If it were possible, what would be the collateral damage? What fraction of production jobs would work, unmodified, without using DYNALLOC? Are code reviews a better technique? Other (specify)? -- This message and any attachments are intended only for the use of the addressee and may contain information that is privileged and confidential. If the reader of the message is not the intended recipient or an authorized representative of the intended recipient, you are hereby notified that any dissemination of this communication is strictly prohibited. If you have received this communication in error, please notify us immediately by e-mail and delete the message and any attachments from your system. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
