Thanks for reminding me. We have that PTF received but not applied. We'll correct that.
I don't know exactly how the sysprog copied the DATACLAS definitions from 1.13 to 2.1 but, obviously, in the process that value got incorrectly set. What confused us and made us think we'd found a bug was the fact that we couldn't find any multi-volume VSAM files on our system. So, we thought something must be wrong. But we finally figured out that our production volume pool for VSAM files just has so much available space that there hadn't been any opportunities for data sets extending to another volume -- until yesterday. Greg Shirey Ben E. Keith Company -----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of Vernooij, CP (ITOPT1) - KLM Sent: Friday, February 26, 2016 1:04 AM To: [email protected] Subject: Re: VSAM file not extending to new volume This reminds me of an ISMF problem I has last year: did you do some updates to the dataclass definitions. Search the archives for: Heads up: ISMF error using the EOF key. It was solved by PTF UA77758, available in aug 2015. Kees. -----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of Greg Shirey Sent: 25 February, 2016 18:50 To: [email protected] Subject: Re: VSAM file not extending to new volume Hmm, thanks for that. It looks like the EA value was NO instead of YES. I'll have to figure out how that happened. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
