FWIW, my usage involves no check for existence. I am allocating new, temporary, non-passed datasets. I'm going to check my SVC 99 to make sure there are no unnecessary text units specified.
Charles -----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of Lennie Dymoke-Bradshaw Sent: Wednesday, August 7, 2019 5:40 PM To: [email protected] Subject: Re: CPU time cost of dynamic allocation Which simply means that if UNIT and VOLUME are not supplied then it looks in the catalog, where it detects a MIGRAT value if the data set is migrated. Lennie Dymoke-Bradshaw | Security Lead | RSM Partners Ltd Web: www.rsmpartners.com ‘Dance like no one is watching. Encrypt like everyone is.’ -----Original Message----- From: IBM Mainframe Discussion List <[email protected]> On Behalf Of Paul Gilmartin Sent: 07 August 2019 21:15 To: [email protected] Subject: Re: [IBM-MAIN] CPU time cost of dynamic allocation On Wed, 7 Aug 2019 16:25:52 +0000, Seymour J Metz wrote: >The Initiator does not check that the data set exists; ... > ... and yet it checks for whether it's migrated. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
