You might also want to consider the DSNTYPE=LARGE if you are going to put this on DASD. And ensure you have sufficient space in the pool. This may prevent future issues.
However, as others have pointed out. An Image Copy is probably better on Tape than DASD. But if your shop does not have tape (virtual or real), then have a lot of DASD available for this. Lizette > -----Original Message----- > From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf > Of O'Brien, David W. (NIH/CIT) [C] > Sent: Thursday, February 21, 2013 6:58 AM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: Re: [DB2-L] - DB2 V10 upgrade - SMS allocation failure > > Jim, > > You might want to define a dataclass with the following attributes: > > Data Set Name Type .large . . . . (EXT, HFS, LIB, PDS, Large or blank) > If Ext . . . . . . . . . . (P=Preferred, R=Required or blank) > Extended Addressability . . N (Y or N) > Record Access Bias . . . . (S=System, U=User or blank) > Space Constraint Relief . . . y (Y or N) > Reduce Space Up To (%) . 50. (0 to 99 or blank) > Dynamic Volume Count . .5 . (1 to 59 or blank) > > Or include dsntype=large in the jcl for the failing dataset. I imagine a 6k cyl dataset > would require the 'large' definition. > > Alternatively select extended addressing with data compaction. > > Data Set Name Type . EXT. . . . (EXT, HFS, LIB, PDS, Large or blank) > If Ext . . .R . . . . . . . (P=Preferred, R=Required or blank) > Extended Addressability . . Y (Y or N) > Record Access Bias . . . . (S=System, U=User or blank) > Space Constraint Relief . . . N (Y or N) > Reduce Space Up To (%) . . (0 to 99 or blank) > Dynamic Volume Count . 3. . (1 to 59 or blank) > Compaction . . .Y . . . . . . (Y, N, T, G or blank) > > Hope this helps. > > Dave O'Brien > NIH Contractor > -----Original Message----- > From: Lizette Koehler [mailto:stars...@mindspring.com] > Sent: Thursday, February 21, 2013 8:44 AM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: Re: [DB2-L] - DB2 V10 upgrade - SMS allocation failure > > Jim > > > > Does you SMS definitions have Extended Format Extended Address for the VSAM > allocations? I think that is in the DATACLAS definition for this file? > > Since I do not see a DATACLAS defined, I am guessing it does not. For most of your > DB2 files you should have a DATACLAS with Extended Format YES Extended Address > YES > > > > STORCLAS (SCSMS) MGMTCLAS ( ) DATACLAS ( ) > STORGRPS (SGDB2E ) > > > > Lizette > > > > > > From: Jim McAlpine [mailto:jim.mcalp...@gmail.com] > Sent: Thursday, February 21, 2013 6:37 AM > To: db...@lists.idug.org; IBM Mainframe Discussion List > Subject: [DB2-L] - DB2 V10 upgrade - SMS allocation failure > > > > cross posted to DB2-L and IBM-MAIN. > > > > I'm trying to run DSNTIJEN to upgrade to DB2 V10 new function but the job is failing > on the reorg of SPT01. Following are the SMS messages. > > > > IGD17272I VOLUME SELECTION HAS FAILED FOR INSUFFICIENT SPACE FOR 808 DATA > SET DB2E.IMAGCOPY.SPT01.D2013052.T125957 > JOBNAME (DB2DBAA ) STEPNAME (ENFM0027) > PROGNAME (DSNUTILB) DDNAME (SYS00001) > REQUESTED SPACE QUANTITY = 4349339 KB > STORCLAS (SCSMS) MGMTCLAS ( ) DATACLAS ( ) > STORGRPS (SGDB2E ) > IGD17272I VOLUME SELECTION HAS FAILED FOR INSUFFICIENT SPACE FOR 809 DATA > SET DB2E.IMAGCOPY.SPT01.D2013052.T125957 > JOBNAME (DB2DBAA ) STEPNAME (ENFM0027) > PROGNAME (DSNUTILB) DDNAME (SYS00002) > REQUESTED SPACE QUANTITY = 3038417 KB > STORCLAS (SCSMS) MGMTCLAS ( ) DATACLAS ( ) > > STORGRPS (SGDB2E ) > > > > and here are the DB2 messages. > > > > DSNU1035I 052 13:59:57.54 DSNUJTDR - TEMPLATE STATEMENT PROCESSED > SUCCESSFULLY > DSNU050I 052 13:59:57.54 DSNUGUTC - REORG TABLESPACE DSNDB01.SPT01 > SHRLEVEL REFERENCE LOG NO COPYDDN(SYSCOPY) > CONVERTV10 RETRY 255 TIMEOUT TERM RETRY_DELAY 1 DRAIN_WAIT 1 SORTDATA > SORTDEVT SYSDA SORTNUM 99 DSNU3343I ! 052 13:59:57.54 DSNURFIT - REAL-TIME > STATISTICS INFORMATION MISSING FOR TABLESPACE DSNDB01.SPT01 > > DSNU3343I ! 052 13:59:57.54 DSNURFIT - REAL-TIME STATISTICS INFORMATION > MISSING FOR INDEX SYSIBM.DSNSPT01 > > DSNU3343I ! 052 13:59:57.54 DSNURFIT - REAL-TIME STATISTICS INFORMATION > MISSING FOR INDEX SYSIBM.DSNSPT02 > > DSNU1015I 052 14:00:40.18 DSNUGDYN - ERROR ALLOCATING DATA SET > DSN=DB2E.IMAGCOPY.SPT01.D2013052.T125957 > CODE=X'970C0000' > DSNU1042I 052 14:00:40.18 DSNUGDYN - START OF IDCAMS MESSAGES > IKJ56893I DATA SET DB2E.IMAGCOPY.SPT01.D2013052.T125957 NOT ALLOCATED+ > IGD17273I ALLOCATION HAS FAILED FOR ALL VOLUMES SELECTED FOR DATA SET > DB2E.IMAGCOPY.SPT01.D2013052.T125957 > IGD17277I THERE ARE (12) CANDIDATE VOLUMES OF WHICH (12) ARE ENABLED OR > QUIESCED IGD17290I THERE WERE 1 CANDIDATE STORAGE GROUPS OF WHICH THE > FIRST 1 WERE ELIGIBLE FOR VOLUME SELECTION. > THE CANDIDATE STORAGE GROUPS WERE:SGDB2E IGD17279I 12 VOLUMES WERE > REJECTED BECAUSE OF INSUFF TOTAL SPACE > DSNU1043I 052 14:00:40.19 DSNUGDYN - END OF IDCAMS MESSAGES > DSNU012I 052 14:00:52.45 DSNUGBAC - UTILITY EXECUTION TERMINATED, HIGHEST > RETURN CODE=8 > > Following is the available space. > > > > Volser Unit Devtyp FTrk LTrk FCyl LCyl DSCB %Use Mnt VTOC SGRP > DB2E12 0D33 3390-9 49926 49926 3328 3328 7447 0 Prv Actv SGDB2E > DB2E11 0D34 3390-9 49926 49926 3328 3328 7447 0 Prv Actv SGDB2E > DB2E10 0D96 3390-9 49926 49926 3328 3328 7447 0 Prv Actv SGDB2E > DB2E01 0DA4 3390-9 5969 1800 391 120 5360 88 Prv Actv SGDB2E > DB2E02 0DA5 3390-9 7080 1650 451 110 2588 85 Prv Actv SGDB2E > DB2E03 0DA6 3390-9 2848 2835 189 189 2219 94 Prv Actv SGDB2E > DB2E04 0DA7 3390-9 7853 6540 521 436 8194 84 Prv Actv SGDB2E > DB2E05 0DA8 3390-9 11827 10800 787 720 5979 76 Prv Actv SGDB2E > DB2E06 0DA9 3390-9 14333 10650 952 710 7369 71 Prv Actv SGDB2E > DB2E07 0DAA 3390-9 9203 5205 604 347 7227 81 Prv Actv SGDB2E > DB2E09 0DAE 3390-9 49916 49895 3327 3326 7446 0 Prv Actv SGDB2E > DB2E08 0DAF 3390-9 7046 6990 469 466 7424 85 Prv Actv SGDB2E > > > > > I don't understand why I have 2 x IGD17272I messages here but even so I make each > of the allocation requests to be approx 6000 cylinders. Why can't the allocation be > done from the available space above. > > > > Jim McAlpine > ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
