I verified the DATACLAS construct.  The volume count is 20.  I am unable to 
confirm if the LISTCAT has a EXT-ADDR because the dsn has been deleted.  Sorry, 
I should have noted it before I made the post.  Going by to my observation in 
general, would coding the VOLSERS in the VOL field cause the abend because the 
DATACLASS has the volume count of 20 and there were 56 volumes in this 
particular STORAGE GROUP POOL?

--- On Thu, 11/11/10, Darth Keller <[email protected]> wrote:


From: Darth Keller <[email protected]>
Subject: Re: IGD17103I CATALOG ERROR WHILE DEFINING VSAM DATA SET
To: [email protected]
Received: Thursday, 11 November, 2010, 7:52 AM


Looking at the 110 Reason code information, I question if your dataset was 
actually assign a dataclass allowing extended format.   The way I 
understand the 110, you exceeded the 4GB limit on 'standard' VSAM. You'll 
need to look at the SMS constructs actually being used for your dataset 
here.  You're not giving us enough information here for us to tell.

Take a close look at the ListCat information for the file which was 
defined & ensure that it actually was defined as extended format.  If it 
is, you should see "EXTENDED     EXT-ADDR " in the ListCat

dd keller


////////////////////
G'Day,

I encountered the following abend when attempting to define a VSAM 
extended dsn.  The SMS routines (STORAGE CLASS, STORAGE GROUP & 
DATACLASS) have been correctly defined.  I verified if the volumes(3390-3) 
were empty and all seem okay.

IGD17103I CATALOG ERROR WHILE DEFINING VSAM DATA SET
VSAMG1.Z56013.VVL000D.MASTER4.SNAP
RETURN CODE IS 140 REASON CODE IS 110 IGG0CLEV
IGD306I UNEXPECTED ERROR DURING IGG0CLEV PROCESSING
RETURN CODE 140 REASON CODE 110

Below is the DEFINE CLUSTER:
DEFINE CLUSTER (NAME(VSAMG1.Z56013.VVL000D.MASTER4.SNAP) -
             INDEXED KEYS(64,0) -
             SHR(2,3) -
             REUSE -
             RECORDSIZE (64,4068) -
             FREESPACE(15,20) -
             VOLUME(A24S11,A24S12,A24S13,A24S14,A24S17,A24S19)) -
             DATA -
             (NAME(VSAMG1.Z56013.VVL000D.MASTER4.SNAP.DATA) -
             CONTROLINTERVALSIZE (16384) -
             CYLINDERS (3815,36)) -
             INDEX -
             (NAME(VSAMG1.Z56013.VVL000D.MASTER4.SNAP.INDEX) -
             CYLINDERS (97,4) -
             CONTROLINTERVALSIZE (4096))
I reran the job successfully after removing all the VOLSERS except for 
A24S11.  Was it a fluke that it worked? Was the cause of the abend due to 
having 6 VOLSERS coded in the VOLUME parm?
/////////////



This e-mail message and all attachments transmitted with it may
contain legally privileged and/or confidential information intended
solely for the use of the addressee(s). If the reader of this
message is not the intended recipient, you are hereby notified that
any reading, dissemination, distribution, copying, forwarding or
other use of this message or its attachments is strictly
prohibited. If you have received this message in error, please
notify the sender immediately and delete this message and all
copies and backups thereof. Thank you.

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html





----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html

Reply via email to