My 2-cents; can you imagine if you had to hard-code all user-catalog's into the 
CATALOG started task correctly. The chance of missing one, or defining a new 
user-catalog and not including it in the JCL for the started task would be 
horrible. And if you are using a modern security product (RACF, ACF2, Top 
Secret) what security risk unless you have a wide-open security system already 
in place? No, there is no "security risk" with dynamic allocation that doesn't 
exist for standard DD allocations and the advantages for system-level 
applications far out-weigh any JES3 resource management controls. 

Russell (speaking for myself, not my employeer) Witt

-----Original Message-----
From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf 
Of Paul Gilmartin
Sent: Wednesday, December 20, 2017 4: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

Reply via email to