Exactly. I am no VSAM guy ... but whatever magic you have to do manually go get the VSAM file to be readable, why can't AMS just do that when it creates the file? Is there any reason anyone would want a "virginal" (unreadable) VSAM file specifically?
How many ABENDs, how many application problems, how many stupid little customer fixup programs and PROCs could have been saved if AMS just did that from the get-go? Or am I missing something? As I say, I am no VSAM guy. Charles -----Original Message----- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Seymour J Metz Sent: Sunday, May 27, 2018 12:41 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: empty KSDS behavior - why? Not really. It's more like making you create a VTOC after you've formated the drive instead of making the creation of the VTOC part of the formatting. Pre-SMS there was a similar problem with sequential DASD files; you had to open them for output if you wanted to use them as empty input files. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
