Zhang, If you don't have any automation to add a volume when all extents or space are used on a single volume, then the dataset is never given the option to extend to a new volume - which may or may not be your spill SG.
Change your JCL to be - SPACE=(CYL,(1500,500)),UNIT=(,5) - and your dataset will look for up to four candidates to extend to. If the space cannot be satisfied from SGIMSDB it will extend to a volume in SGSPILL. Ron > -----Original Message----- > From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On > Behalf Of Smartcurl Zhang > Sent: Thursday, December 04, 2008 7:35 PM > To: IBM-MAIN@bama.ua.edu > Subject: Re: [IBM-MAIN] a question about storage group attribution > OVERFLOW and EXTEND SG NAME > > Dear Kees, > > I have try many times with a SMF merge job, make space in SGIMSDB can > only > hold a primary allocation,hope SMF merged dataset could been allocated > primarily in SGIMSDB and secondarily in SGSPILL according to > SPACE=(CYL,(1500,500)) in JCL. > But whatever i try,the merge job always give me a ABEND SB37,and i > found > that merged dateaset successfully allocated in SGIMSDB but failed in > allocating SGSPILL. > > help me,please > and thank you for you patience to my poor english. > > Zhang > ---------------------------------------------------------------------- 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
