On Thu, Dec 21, 2017 at 11:00 AM, Seymour J Metz <[email protected]> wrote:
> 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. > Around here using the DYNALLOC in, say, COBOL would be "frowned upon" is because CA-11 (restart package) could not "clean up" any DSN created using it. Also, CA-7 would not be able to "track" the DSN back to the creating or using job stream. Our production person uses the CA-7 data set "tracking" to answer questions about "which job uses DSN ...?". It's amazing to me that the system designers (programmers) actually ask the production people "what does job ... do?". Mainly because their management, historically, has never required any kind of system documentation from them. -- I have a theory that it's impossible to prove anything, but I can't prove it. Maranatha! <>< John McKown ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
