Re: DFSORT and SAS

5, 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) an

Re: DFSORT and SAS

Referenced date . . : 2021/01/25 >Expiration date . . : ***None*** > SMS Compressible . : YES > > >> -Original Message- >> From: IBM Mainframe

Re: DFSORT and SAS

> But, all datasets are on disk. Dave, If the files are on DISK , DFSORT should be able to get the stats. Can you please send me the COMPLETE joblog to my email offline? I want to check allocation messages for the ddname SASSIN. > My Tape management is CA-7 I guess you meant CA-1(Tape managemen

Re: DFSORT and SAS

ssible . : YES > -Original Message- > From: IBM Mainframe Discussion List 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

Re: DFSORT and SAS

>> OPTION SORTDD=SASS,MSGDDN=SYSOUT,MAINSIZE=MAX,MSGPRT=CRITICAL,NOLIST 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 messag

Re: DFSORT and SAS

IBM-MAIN@LISTSERV.UA.EDU > Subject: Re: DFSORT and SAS > > SAS application programs often invoke multiple PROC SORT requests (some > thru SQL-type invocations, or otherwise) and so there really should not be an > OPTION FILESZ=Ennn necessary, given the SAS program-invoked >

Re: DFSORT and SAS

he settings other than the ones I >mentioned in original note. > >> -Original Message- >> From: IBM Mainframe Discussion List On >> Behalf Of Martin Packer >> Sent: Tuesday, January 19, 2021 1:09 PM >> To: IBM-MAIN@LISTSERV.UA.EDU >> Subject: Re: DFS

Re: DFSORT and SAS

anuary 19, 2021 1:09 PM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: Re: DFSORT and SAS > > I'd ask over on MXG-L if there are methods for SAS to pass the record > count and average record length estimate to DFSORT. > > Cheers, Martin > > Martin Packer > >

Re: DFSORT and SAS

Date: 19/01/2021 20:14 Subject:[EXTERNAL] Re: DFSORT and SAS Sent by:IBM Mainframe Discussion List Thank you. Adding the suggested parm allowed my job to succeed. Ultimately, there where 15,890,801 records. I looked again and there was not an ICE118I issued in the original

Re: DFSORT and SAS

> Thank you. Adding the suggested parm allowed my job to succeed. Dave, Glad to hear that the job is successful. > Ultimately, there where 15,890,801 records. May be you should pass 18 million as estimated filesize to account for future growth. Thanks, Kolusu DFSORT Development IBM Corporatio

Re: DFSORT and SAS

tance. > -Original Message- > From: IBM Mainframe Discussion List On > Behalf Of Sri h Kolusu > Sent: Tuesday, January 19, 2021 11:37 AM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: Re: DFSORT and SAS > > > ICE752I 0 FSZ=0 RE IGN=0 C AVG=188 0 WSP=0 E DYN=2313 1635

Re: DFSORT and SAS

> ICE752I 0 FSZ=0 RE IGN=0 C AVG=188 0 WSP=0 E DYN=2313 16352 Dave, When DFSORT is invoked via program, it needs to know how many records it is sorting so that it can optimally allocate resources needed to sort that data. Since the program is feeding the records DFSORT does not have a clue a

DFSORT and SAS

I recently switched to DFSORT. Hopefully this is the last glitch. My weekly MXG (SAS) job failed in the TRNDDSNS step. I am not yet familiar with DFSORT messages. The step has REGION=0M and I have no special memory exits. The SAS SORT options are: DYNALLOC SORTDEV=3390 SORTBLKMODE SORTDEVWARN If