Some additional questions 1) How man volumes are in the pool? How many 54s and how many 27s
2) How large will the allocation be? Using 16 extents for the dataset (this may vary), then this is 2000 + (2000*15) or 32,000 cylinders total for the file. Is there sufficient space? 3) How fragmented are the volumes? Is there enough for a primary allocation of 2000 (This can be gotten in a maximum of 5 extents). Is there sufficient for the secondary to be taken on 20 volumes? 637-BC code is a situation that says there is not enough space on the VOLUME to allocate a new extent or file. This is not a no space in the file situation. The BC return code notes the volume designation. When you review the dump that is produced you will see that the end of volume has been reached at allocation. It may help identify the issue by changing the TEMP dsns to real DSNs and seeing what allocations (and where) is being done. Lizette > -----Original Message----- > From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On > Behalf Of Richards, Robert B. > Sent: Sunday, August 06, 2017 2:50 AM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: Re: IEC026I - 637-BC > > Oops! > > I meant the TEMP DDs (TEMP1 and TEMP2) > > Bob > > -----Original Message----- > From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On > Behalf Of Richards, Robert B. > Sent: Sunday, August 06, 2017 5:47 AM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: Re: IEC026I - 637-BC > > Theo, > > S637 - BC > The last known volume for the data set could not be located while > reading a multivolume DASD data set. > > I have personally never seen the above. But based on the space you are > requesting, try adding DSNTYPE=LARGE to both CONCAT DDs and see if that > helps. > > Bob > > -----Original Message----- > From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On > Behalf Of Buckton, T. (Theo) > Sent: Sunday, August 06, 2017 5:10 AM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: IEC026I - 637-BC > > Hi, > > We have a batch job that abends with the above code when creating a temp file > on a model-54 volume. We are in the middle of a data migration, and model-54s > are being allocated to this pool. However, we still have model-27s which will > be removed at a later stage. What I have done to bypass the issue is to > disable the model-54s as I noticed that batch job does not abend if the temp > file is written to the model-27s. > Can somebody shed light on this issue - in simple terms please :) ? > > IEC710I 82AF,APWKA2,NDCP351Z,SPDT02,CONCAT ANOTHER VOLUME EXPECTED > IEC026I 637-BC,IFG0553P,NDCP351Z,SPDT02,CONCAT,82AF,APWKA2, 375 > SYS17216.T214401.RA000.NDCP351Z.SPDT021.H02 > IEA995I SYMPTOM DUMP OUTPUT 376 > SYSTEM COMPLETION CODE=637 REASON CODE=000000BC > > //TOOLMSG DD SYSOUT=* > //DFSMSG DD SYSOUT=* > //IN1 DD DSN=PNGG00.DCPACK.NDCP351Z.EXTRACT.DTL, > // DISP=SHR > //IN2 DD DSN=PNGG00.DCPACK.NDCP351Z.EXTRACT.NP02, > // DISP=SHR > //TEMP1 DD DSN=&&SPDT021,DISP=(,PASS),SPACE=(CYL,(2000,2000)), > // UNIT=(SYSDA,20) > //TEMP2 DD DSN=&&SPDT022,DISP=(,PASS),SPACE=(CYL,(2000,2000)), > // UNIT=(SYSDA,20) > //CONCAT DD DSN=*.TEMP1,VOL=REF=*.TEMP1,DISP=(OLD,PASS) > // DD DSN=*.TEMP2,VOL=REF=*.TEMP2,DISP=(OLD,PASS) > //COMBINE DD DSN=PNGG00.DCPACK.NDCP351Z.DTLNP02.DATA, > // DISP=(,PASS),UNIT=(SYSDA,4), > // SPACE=(CYL,(1500,200),RLSE), > // DCB=(LRECL=1477,RECFM=FB,BLKSIZE=0) > > > ******************** ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
