Apart from the unreal idea to disable DYNALLOC fully, you have full control 
over the DYNALLOC functions via exit IEGDB401. We did and do beautiful things 
in it, like our own SMS-like volume pooling before we converted to SMS.

Grtn,
Kees.

> -----Original Message-----
> From: IBM Mainframe Discussion List [mailto:[email protected]] On
> Behalf Of Paul Gilmartin
> Sent: 20 December, 2017 23:38
> 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 information, services and offers, please visit our web site: 
http://www.klm.com. This e-mail and any attachment may contain confidential and 
privileged material intended for the addressee only. If you are not the 
addressee, you are notified that no part of the e-mail or any attachment may be 
disclosed, copied or distributed, and that any other action related to this 
e-mail or attachment is strictly prohibited, and may be unlawful. If you have 
received this e-mail by error, please notify the sender immediately by return 
e-mail, and delete this message. 

Koninklijke Luchtvaart Maatschappij NV (KLM), its subsidiaries and/or its 
employees shall not be liable for the incorrect or incomplete transmission of 
this e-mail or any attachments, nor responsible for any delay in receipt. 
Koninklijke Luchtvaart Maatschappij N.V. (also known as KLM Royal Dutch 
Airlines) is registered in Amstelveen, The Netherlands, with registered number 
33014286
********************************************************


----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN

Reply via email to