That is what I did to fix the problem.  But my question is why this would 
happen.  The SMS rules show that it is VSAM EXTENDED and the volume is a 3390-9 
model.  



________________________________
From: Ernie Takeuchi <e.m.takeu...@att.net>
To: IBM-MAIN@bama.ua.edu 
Sent: Friday, April 20, 2012 12:18:20 PM
Subject: Re: SMS QUESTION

Try a smaller space allocation.
"willie bunter" <williebun...@yahoo.com> wrote in message news: 
<1334937117.83658.yahoomail...@web113615.mail.gq1.yahoo.com>...

Hi,



This post was not answered.  Can anybody help me out?





________________________________

From: willie bunter <williebun...@yahoo.com>

To: IBM-MAIN@bama.ua.edu 

Sent: Tuesday, April 17, 2012 12:13:35 PM

Subject: SMS QUESTION



I encountered the problem with defining a VSAM EXTENDED dsn at a recent 
disaster recovery.  The SMS rules - ACS or DC, MC ,SC & SG - are the same as in 
our production system.  However I could not understand the reason for this 
problem.  As a work around I defined the MCDS to use 4,000

cylinders on HSM001 which is a MOD-9.  What is also suprising is that the BCDS 
which is also VSAM EXTENDED worked fine.  



Below is the output of the failing job.



  DEFINE CLUSTER -                                                      

      (NAME(SYS2.MCDS)  -

      VOLUMES(HSM001)  -                                                  

          CYLINDERS(8000)                  -                              

          RECORDSIZE(435 2040)      FREESPACE(0  0) -                    

          INDEXED  KEYS(44  0)  SHAREOPTIONS(3 3) -                    

          SPEED BUFFERSPACE(530432) -                                    

          UNIQUE  NOWRITECHECK)  -                                      

      DATA  -                                                            

            (NAME(SYS2.MCDS.DATA) -                                      

      CONTROLINTERVALSIZE(12288)) -                                      

      INDEX  -                                                            

            (NAME(SYS2.MCDS.INDEX) -                                    

      CONTROLINTERVALSIZE(2048))                                          

0IGD17103I CATALOG ERROR WHILE DEFINING VSAM DATA SET

SYS2.MCDS

RETURN CODE IS 140 REASON CODE IS 110 IGG0CLEV

IGD306I UNEXPECTED ERROR DURING IGG0CLEV PROCESSING

RETURN CODE 140 REASON CODE 110

THE MODULE THAT DETECTED THE ERROR IS IGDVTSCU

SMS MODULE TRACE BACK - VTSCU VTSCT VTSCH VTSCG VTSCD VTSCC VTSCR SSIRT

SYMPTOM RECORD CREATED, PROBLEM ID IS IGD00025

IGD17219I UNABLE TO CONTINUE DEFINE OF DATA SET

SYS2.MCDS

0IDC3014I CATALOG ERROR

IDC3009I ** VSAM CATALOG RETURN CODE IS 140 - REASON CODE IS

IDC3009I IGG0CLEV-110

1IDCAMS  SYSTEM SERVICES                                          TIME: 
19:20:13        04/02/12    PAGE      2

0IDC3003I FUNCTION TERMINATED. CONDITION CODE IS 12



----------------------------------------------------------------------

For IBM-MAIN subscribe / signoff / archive access instructions,

send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN



----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN

Reply via email to