OK, I modified a SMS dataclass to specify datasetype extented and extended
addressability. When I run the job to create the linear cluster I still get the
IDC3014I CATALOG ERROR IDC3009I **
VSAM CATALOG RETURN CODE IS 140 - REASON CODE IS
IDC3009I IGG0CLEV-110
IDC3003I FUNCTION TERMINATED. CONDITION CODE IS 12
I displayed the active dataclass and it shows that it has CDS Name . . . . . :
ACTIVE
Data Class Name . . : DBAGDC
Data Set Name Type . . . . . : EXTENDED
If Extended . . . . . . . . : PREFERRED
Extended Addressability . . : YES
Record Access Bias . . . . : USER
RMODE31 . . . . . . . . . . :
Space Constraint Relief . . . : NO
Reduce Space Up To (%) . . :
Dynamic Volume Count . . . :
Compaction . . . . . . . . . :
Spanned / Nonspanned . . . . :
I am specifying VOLUMES in the DEFINE CLUSTER which are not SMS managed. I
thought, based on ther answers to my initial question, that this would be all
right.
Any additional input would be greatly appreciated.
Bill J.
On Tuesday, July 21, 2015 10:46 AM, Lizette Koehler
<[email protected]> wrote:
It will depend on the OP shop on how this will work.
So how does the ACS routine handle DBAGDC. Also, does it only include Extended
Addressability or more stuff?
I also like to have Extended Format with my Extended Addressability.
Lizette
> -----Original Message-----
> From: IBM Mainframe Discussion List [mailto:[email protected]]
> On Behalf Of william janulin
> Sent: Tuesday, July 21, 2015 6:36 AM
> To: [email protected]
> Subject: Re: VSAM question
>
> Would not modifying an existing DATACLASS to specify Extended
> Addressability do the same thing?
>
> On Tuesday, July 21, 2015 9:32 AM, "Blake, Daniel J [CTR]"
> <[email protected]> wrote:
>
>
> I believe the key is using SMS and setting up a DATACLASS that supports
> extended addressability (because the total size is greater than 4 GB).
>
> Dan
>
>
>
> -----Original Message-----
> From: IBM Mainframe Discussion List [mailto:[email protected]]
> On Behalf Of william janulin
> Sent: Tuesday, July 21, 2015 9:24 AM
> To: [email protected]
> Subject: Re: VSAM question
>
> To list;
> OK. I modified a dataclass to specify extended addressability but I still get
> the 110 error:
> DEFINE -
> CLUSTER -
> ( -
> NAME(WAS850.ZFS) -
> LINEAR -
> CYL(8000 4000) -
> DATACLASS(DBAGDC) -
> VOLUMES(Z1W850 Z1W851) -
> SHAREOPTIONS(3) -
> ) IDC3014I CATALOG ERROR IDC3009I ** VSAM CATALOG RETURN CODE
> IS 140 - REASON CODE IS IDC3009I IGG0CLEV-110 IDC3003I FUNCTION
> TERMINATED. CONDITION CODE IS 12
>
> Am I missing a step with this?
> Bill J.
>
> On Monday, July 20, 2015 8:31 PM, Leonardo Vaz <[email protected]>
> wrote:
>
>
> Beginning in z/OS V2R1, you can have non-SMS managed VSAM Linear Data
> Sets that are larger than 4GB, with the Extended Addressability attribute.
>
> http://www-
> 01.ibm.com/support/knowledgecenter/SSLTBW_2.1.0/com.ibm.zos.v2r1.e0z
> m100/newdasd.htm
>
> Regards,
> Leo
>
> -----Original Message-----
> From: IBM Mainframe Discussion List [mailto:[email protected]]
> On Behalf Of william janulin
> Sent: Monday, July 20, 2015 2:57 PM
> To: [email protected]
> Subject: VSAM question
>
> To list;
> Is there a way around the 4 gig limitation when defining a LINEAR cluster on
> volumes not managed my SMS? I have to download Websphere v8.5 and am
> attempting to define a ZFS dataset large enough to hold the product plus its
> myriad of ptfs.
> Thank you in advance, Bill J.
>
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
