That Weekly TREND file has been growing, probably a couple decades. It is quite 
possible that my former SORT product was due to fail for the same general 
reasons.

> -----Original Message-----
> From: IBM Mainframe Discussion List <IBM-MAIN@LISTSERV.UA.EDU> On
> Behalf Of Scott Barry
> Sent: Monday, January 25, 2021 2:45 PM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: Re: DFSORT and SAS
> 
> It appears that you are managing the //TREND PDB as a SAS sequential-
> format (indicated with RECFM=U, and as you mention with prior TMM-
> deployment - also getting zEDC benefit, hopefully) and I expect that SAS
> does not detect the observation/row/record count which is why you see the
> ICE118I  message.  This is clearly a SAS-limitation situation, what with the
> tape-format SAS data library.
> 
> Regards,
> Scott Barry
> SBBTech LLC
> 
> 
> On Mon, 25 Jan 2021 21:04:58 +0000, Gibney, Dave <gib...@wsu.edu>
> wrote:
> 
> >I am sure the ICE118I showed up because of the //SORTDIAG
> >My Tape management is CA-7. But, all datasets are on disk.
> >JCL follows:
> >//TRNDDSNS EXEC MXGSAS,WORK='5000,1000'
> >//**************************************************
> >//* DO MXG WEEKLY DATASET TRENDING PROCESSING
> >//**************************************************
> >//WEEK     DD  DSN=MXG.DATASETS.WEEK(+0),DISP=OLD
> >//TREND    DD  DSN=MXG.DATASETS.TREND,DISP=OLD
> >//SYSIN    DD  *
> > %INCLUDE SOURCLIB(SYS802C);
> >//SORTDIAG DD DUMMY
> >//DFSPARM  DD *
> >OPTION FILSZ=E18000000
> >
> >My Tape management is CA-7. But, all datasets are on disk.
> >
> >/* COPYRIGHT (C) 1993,1994 MERRILL CONSULTANTS DALLAS TEXAS USA
> */
> > /* LAST UPDATED: JUL 1, 1994                                        */
> > /*                                                                  */
> > /*  THIS MEMBER IS A PART OF THE ALL-YOUR-DATA-SETS-TRACKING-
> SYSTEM */
> > /*  SEE ADOCDSNS FOR DESCRIPTION OF ITS OTHER COMPONENTS            */
> > /*                                                                  */
> > /*CHANGE LOG                                                        */
> > /*06/03/94 UPDATED FOR NEW VMXGSUM LOGIC                            */
> >
> /**********************************************************
> **********/
> >OPTIONS NODSNFERR NOVNFERR;
> >%VMXGSUM(INVOKEBY=TRNDDSNS,
> >  INDATA=  WEEK.DATASETS
> >           TREND.TRNDDSNS,
> >  OUTDATA= TREND.TRNDDSNS,
> >  DSNLABEL=TRND DSNS: TREND 1415/64 DATASETS,
> >  SUMBY=   DSNAME,
> >  MIN=     FIRST,
> >  MAX=     LAST LASTPRI LASTLV1 LASTLV2 LASTBKP LASTTMS,
> >  SUM=     ACTIVE SPACE1-SPACE6 DAYS1-DAYS6 BACKUPS VOLUMES TAPES,
> >  OUTCODE=
> >           %INCLUDE SOURCLIB(IMACZDAT); /* SET ZDATE=TODAY() */
> >OPTIONS   DSNFERR   VNFERR;
> >
> >A I understand this, it is just a sort or merge of the newly updated TREND
> with the previous week into a new generation.
> >I don't know why SAS is not informing DFSORT of the data volume. It should
> know the new record count precisely. And should be able to see the raw size
> of the previous generation..
> >
> >The main dataset is a SAS dataset:
> >Data Set Name . . . . : MXG.DATASETS.TREND
> >General Data                           Current Allocation
> > Management class . . : MCRSRC01        Allocated tracks  . : 84,226
> > Storage class  . . . : SCRSRC          Allocated extents . : 7
> >  Volume serial . . . : RSRC10 +
> >  Device type . . . . : 3390
> > Data class . . . . . : BIG
> >  Organization  . . . : PS             Current Utilization
> >  Record format . . . : FS              Used tracks . . . . : 83,488
> >  Record length . . . : 27648           Used extents  . . . : 7
> >  Block size  . . . . : 27648
> >  1st extent tracks . : 49218
> >  Secondary tracks  . : 1000           Dates
> >  Data set name type  :                 Creation date . . . : 2002/03/25
> >                                        Referenced date . . : 2021/01/25
> >                                        Expiration date . . : ***None***
> >  SMS Compressible  . : NO
> >The other is sequential, but still SAS and many years ago, would have been
> tape be for we did the SMS Tape Mount Management stuff:
> >Data Set Name . . . . : MXG.DATASETS.WEEK.G0979V00
> >
> >General Data                           Current Allocation
> > Management class . . : ATMBKUPS        Allocated megabytes : 3,000
> > Storage class  . . . : SCDSKTAP        Allocated extents . : 2
> >  Volume serial . . . : PTAP40 +
> >  Device type . . . . : 3390
> > Data class . . . . . : TMBKUPLG
> >  Organization  . . . : PS             Current Utilization
> >  Record format . . . : U               Used megabytes  . . : 15
> >  Record length . . . : 0               Used extents  . . . : 1
> >  Block size  . . . . : 32760
> >  1st extent megabytes: 1500
> >  Secondary megabytes : 2500           Dates
> >  Data set name type  : EXTENDED        Creation date . . . : 2021/01/11
> >                                        Referenced date . . : 2021/01/25
> >                                        Expiration date . . : ***None***
> >  SMS Compressible  . : YES
> >
> >> -----Original Message-----
> >> From: IBM Mainframe Discussion List <IBM-MAIN@LISTSERV.UA.EDU> On
> >> Behalf Of Sri h Kolusu
> >> Sent: Monday, January 25, 2021 12:29 PM
> >> To: IBM-MAIN@LISTSERV.UA.EDU
> >> Subject: Re: DFSORT and SAS
> >>
> >> >> OPTION
> >>
> SORTDD=SASS,MSGDDN=SYSOUT,MAINSIZE=MAX,MSGPRT=CRITICAL,NOLIS
> >> T
> >>
> >> Dave,
> >>
> >> What type of dataset is the input dataset(ddname SASSIN)?   Is it a tape
> >> dataset? If so what kind of tape management system do you have? RMM
> ?
> >> CA-1 ?
> >>
> >> PS: Your latest joblog shows that you indeed received ICE118I message
> (4th
> >> line in the Sortdiag file)
> >>
> >>
> >> Thanks,
> >> Kolusu
> >> DFSORT Development
> >> IBM Corporation
> >>
> >>
> >>
> >>
> >> ----------------------------------------------------------------------
> >> For IBM-MAIN subscribe / signoff / archive access instructions,
> >> send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
> >
> >----------------------------------------------------------------------
> >For IBM-MAIN subscribe / signoff / archive access instructions,
> >send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
> 
> ----------------------------------------------------------------------
> For IBM-MAIN subscribe / signoff / archive access instructions,
> send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

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

Reply via email to