: 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
[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
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
. . . : 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 v
f 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
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
