When allocating files via SMS, the SMS attributes then either have to be explicitly assigned or allowed to be assigned. You mention that the DC is one that is not listed in the parmlib and the volume is a non-sms volume; thus, check your ACS routines for the SMS allocation of these files.
Thanks, Hervey -----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of Ken Leidner Sent: Friday, February 10, 2012 11:06 AM To: [email protected] Subject: System Dumps and SMS allocation fails First this is a long entry, but I wanted to have all the information here in hope that someone would have the answer. We are trying to convert to using SMS managed volumes for our system dumps since we need the LARGE attribute for our large DB2 dumps. But something is preventing the dumps from allocation when MVS tries to make the allocation. What? HELP! I can make the allocation find from 3.2 or even IEFBR14 in batch. Correct volumes correct size - all is well, but MVS still fails when it tries. (using just the dataclas, storclas and mgmtclas in the allocation) SMS volumes are 2 empty mod-9 (other than VTOC, VTOCIX and VVDS).with largest free space as 9,993 cylinders on each one. Here are the messages we receive when a dump occurs. All standard messages, other than I cannot explain the DO NOT HAVE SUFFICIENT SPACE message. Plus the messages after that are odd! The IEF196I IGD100I message. The address D913 is for volume SYX5D1 (one of the non SMS volumes). The dataclass is also not the one in parmlib. Maybe this is just a sequence "error" in that this message should appear after the WILL TRY VOLUME ALLOCATION. Any help in what the meaning of the message below is trying to tell me or where and what to look up would be helpful DYNALLOC FAILED RETURN CODE=04 ERROR RSN CODE=970C INFO RSN CODE=0000 The messages IGD17272I VOLUME SELECTION HAS FAILED FOR INSUFFICIENT SPACE FOR DATA SET ZP.DUMP.PLXB.S00009 JOBNAME (DUMPSRV ) STEPNAME (DUMPSRV ) PROGNAME (IEAVTDSV) DDNAME (SYS00016) REQUESTED SPACE QUANTITY = 2311283 KB STORCLAS (SCDUMP) MGMTCLAS (MCDUMP) DATACLAS (DCDUMP) STORGRPS (SGDUMP ) IKJ56893I DATA SET ZP.DUMP.PLXB.S00009 NOT ALLOCATED+ IGD17273I ALLOCATION HAS FAILED FOR ALL VOLUMES SELECTED FOR DATA SET ZP.DUMP.PLXB.S00009 IGD17277I THERE ARE (2) CANDIDATE VOLUMES OF WHICH (2) 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:SGDUMP IGD17279I 2 VOLUMES WERE REJECTED BECAUSE THEY DID NOT HAVE SUFFICIENT SPACE (041A041D) IEF196I IGD100I D913 ALLOCATED TO DDNAME SYS00017 DATACLAS (DCDFALT) IEA799I AUTOMATIC ALLOCATION OF SVC DUMP DATASET FAILED 168 DUMPID=009 REQUESTED BY JOB (*MASTER*) DYNALLOC FAILED RETURN CODE=04 ERROR RSN CODE=970C INFO RSN CODE=0000 SMS RSN CODE=4379, WILL TRY VOLUME ALLOCATION Here is the parmlib entries for the dumps. Note that the VOL parameter is for the old non SMS volumes that we "use to use" - still do since SMS isn't working. COM='DD ALLOC=ACTIVE' COM='DD ADD,SMS=(DATA=DCDUMP,MGMT=MCDUMP,STOR=SCDUMP)' COM='DD ADD,VOL=(SYX5D1,SYX5D2)' COM='DD NAME=ZP.DUMP.PLXB.S&SEQ.' COM='CD SET,SDUMP=(ALLPSA,NUC,SQA,LSQA,RGN,LPA,TRT,SWA,CSA,SUM),Q=NO' COM='CD SET,SDUMP=(XESDATA)' COM='CD SET,SDUMP=(GRSQ)' COM='CD SET,SDUMP,MAXSPACE=2816M' The complete dataclass - The space is large 128,000 tracks or 6,240,000 KB. Do I even need to code the space? LRECL? RECFM? Data Class Name : DCDUMP Description : Recfm . . . . . . . . . : FBS Lrecl . . . . . . . . . : 4160 Override Space . . . . . : NO Space Avgrec . . . . . . : K Avg Value . . . . : 24960 Primary . . . . . : 250 Secondary . . . . : 60 Directory . . . . : Retpd Or Expdt . . . . . : Volume Count . . . . . . : Add'l Volume Amount . . : Data Set Name Type . . . . . : LARGE If Extended . . . . . . . . : Extended Addressability . . : NO Record Access Bias . . . . : Space Constraint Relief . . . : NO Reduce Space Up To (%) . . : Dynamic Volume Count . . . : Compaction . . . . . . . . . : Spanned / Nonspanned . . . . : Media Interchange Media Type . . . . . . . . : Recording Technology . . . : Performance Scaling . . . . : Performance Segmentation . : Encryption Management Key Label 1: Encoding for Key Label 1 : Key Label 2: Encoding for Key Label 2 : System Managed Buffer . . . : System Determined Blocksize : YES Block Size Limit . . . . . . : EATTR . . . . . . . . . . . : Recorg . . . . . . . . . . . : Keylen . . . . . . . . . . . : Keyoff . . . . . . . . . . . : CIsize Data . . . . . . . . : % Freespace CI . . . . . . . : CA . . . . . . . : Shareoptions Xregion . . . . : Xsystem . . . . : Reuse . . . . . . . . . . . : NO Initial Load . . . . . . . . : RECOVERY BWO . . . . . . . . . . . . : Log . . . . . . . . . . . . : Logstream Id . . . . . . . . : FRlog . . . . . . . . . . . : RLS CF Cache Value . . . . . : ALL RLS Above the 2-GB Bar . . . : NO Extent Constraint Removal . : NO CA Reclaim . . . . . . . . . : YES Ken Leidner [email protected] ---------------------------------------------------------------------- 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
