Yes, you could disable DYNALLOC in production jobs, but it would be a CLM. A good rule of thumb is to not disable anything unless you thoroughly understand the need and consequences, you have a solid rollout plan and you have a solid fallback plan. But it's not my dog.
-- Shmuel (Seymour J.) Metz http://mason.gmu.edu/~smetz3 ________________________________________ From: IBM Mainframe Discussion List <[email protected]> on behalf of Paul Gilmartin <[email protected]> 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)? -- gil ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
