Re: VSAM file not extending to new volume
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:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Vernooij, CP (ITOPT1) - KLM Sent: Friday, February 26, 2016 1:04 AM To: IBM-MAIN@LISTSERV.UA.EDU 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:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Greg Shirey Sent: 25 February, 2016 18:50 To: IBM-MAIN@LISTSERV.UA.EDU 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 lists...@listserv.ua.edu with the message: INFO IBM-MAIN
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:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Greg Shirey Sent: 25 February, 2016 18:50 To: IBM-MAIN@LISTSERV.UA.EDU 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. Greg -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Lizette Koehler Sent: Thursday, February 25, 2016 11:21 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: VSAM file not extending to new volume Check for this in your data class DATA CLASS DISPLAY Page 2 of 5 CDS Name . . . . . : ACTIVE Data Class Name . . : DIRECT Data Set Name Type . . . . . : EXTENDED If Extended . . . . . . . . : REQUIRED Extended Addressability . . : YES Record Access Bias . . . . : USER Space Constraint Relief . . . : NO -- -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu 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 lists...@listserv.ua.edu with the message: INFO IBM-MAIN
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. Greg -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Lizette Koehler Sent: Thursday, February 25, 2016 11:21 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: VSAM file not extending to new volume Check for this in your data class DATA CLASS DISPLAY Page 2 of 5 CDS Name . . . . . : ACTIVE Data Class Name . . : DIRECT Data Set Name Type . . . . . : EXTENDED If Extended . . . . . . . . : REQUIRED Extended Addressability . . : YES Record Access Bias . . . . : USER Space Constraint Relief . . . : NO -- -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: VSAM file not extending to new volume
Check for this in your data class DATA CLASS DISPLAY Page 2 of 5 CDS Name . . . . . : ACTIVE Data Class Name . . : DIRECT Data Set Name Type . . . . . : EXTENDED If Extended . . . . . . . . : REQUIRED Extended Addressability . . : YES Record Access Bias . . . . : USER Space Constraint Relief . . . : NO -- Lizette > -Original Message- > From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On > Behalf Of Lizette Koehler > Sent: Thursday, February 25, 2016 10:12 AM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: Re: VSAM file not extending to new volume > > Did you check to see if the file is over 4GB in size? And if it is, does it > have EA/EF specified? > > Do a LISTC ALL and look at the options and HIURBA and HIARBA > > > Lizette > > > > -Original Message- > > From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] > > On Behalf Of Greg Shirey > > Sent: Thursday, February 25, 2016 9:35 AM > > To: IBM-MAIN@LISTSERV.UA.EDU > > Subject: VSAM file not extending to new volume > > > > We upgraded to z/OS 2.1 on the 13th and all seemed well until this > > morning when several jobs were trying to write to a VSAM file and > > received this > > message: > > > > IEC070I 034(004)-220,GSFAQ200,GS200060GS200,VTSREG4,4621,PROD33, > > IEC070I SPP.ALL.SP013V,SPP.ALL.SP013V.DATA,CATALOG.x.xxx > > > > The message indicates the file could not extend - but it should have > > extended to a new volume. The DATACLAS for our VSAM files has a Dynamic > Volcount of > > 20.When we did a LISTCAT on the data set, it showed a second volume with > > VOLSER of * and VOLFLAG as CANDIDATE. (and Attribute of Extended) > > > > In order to recover the batch job, the applications group had to > > rebuild the VSAM file, so they did, then the sysprogs moved it to a > > volume with a lot of free space, and all the jobs ran fine. > > > > We generated a data set listing in ISMF and filtered on MULTIVOL = YES > > and our sequential data sets are successfully being extended to other > > volumes, but all of the VSAM files on the list only had CANDIDATE volumes > after the primary. > > > > We've opened a PMR and searched the database, but we keep thinking we > > must have missed a migration step or something because we aren't seeing > anyone else > > reporting anything like this. Any suggestions? > > > > Thanks, > > Greg Shirey > > Ben E. Keith Company -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: VSAM file not extending to new volume
Did you check to see if the file is over 4GB in size? And if it is, does it have EA/EF specified? Do a LISTC ALL and look at the options and HIURBA and HIARBA Lizette > -Original Message- > From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On > Behalf Of Greg Shirey > Sent: Thursday, February 25, 2016 9:35 AM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: VSAM file not extending to new volume > > We upgraded to z/OS 2.1 on the 13th and all seemed well until this morning > when several jobs were trying to write to a VSAM file and received this > message: > > IEC070I 034(004)-220,GSFAQ200,GS200060GS200,VTSREG4,4621,PROD33, > IEC070I SPP.ALL.SP013V,SPP.ALL.SP013V.DATA,CATALOG.x.xxx > > The message indicates the file could not extend - but it should have extended > to a new volume. The DATACLAS for our VSAM files has a Dynamic Volcount of > 20.When we did a LISTCAT on the data set, it showed a second volume with > VOLSER of * and VOLFLAG as CANDIDATE. (and Attribute of Extended) > > In order to recover the batch job, the applications group had to rebuild the > VSAM file, so they did, then the sysprogs moved it to a volume with a lot of > free space, and all the jobs ran fine. > > We generated a data set listing in ISMF and filtered on MULTIVOL = YES and our > sequential data sets are successfully being extended to other volumes, but all > of the VSAM files on the list only had CANDIDATE volumes after the primary. > > We've opened a PMR and searched the database, but we keep thinking we must > have missed a migration step or something because we aren't seeing anyone else > reporting anything like this. Any suggestions? > > Thanks, > Greg Shirey > Ben E. Keith Company > -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
VSAM file not extending to new volume
We upgraded to z/OS 2.1 on the 13th and all seemed well until this morning when several jobs were trying to write to a VSAM file and received this message: IEC070I 034(004)-220,GSFAQ200,GS200060GS200,VTSREG4,4621,PROD33, IEC070I SPP.ALL.SP013V,SPP.ALL.SP013V.DATA,CATALOG.x.xxx The message indicates the file could not extend - but it should have extended to a new volume. The DATACLAS for our VSAM files has a Dynamic Volcount of 20. When we did a LISTCAT on the data set, it showed a second volume with VOLSER of * and VOLFLAG as CANDIDATE. (and Attribute of Extended) In order to recover the batch job, the applications group had to rebuild the VSAM file, so they did, then the sysprogs moved it to a volume with a lot of free space, and all the jobs ran fine. We generated a data set listing in ISMF and filtered on MULTIVOL = YES and our sequential data sets are successfully being extended to other volumes, but all of the VSAM files on the list only had CANDIDATE volumes after the primary. We've opened a PMR and searched the database, but we keep thinking we must have missed a migration step or something because we aren't seeing anyone else reporting anything like this. Any suggestions? Thanks, Greg Shirey Ben E. Keith Company -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
