Re: elapsed time for DFSORT
Hi Dave, I have send the joblog to your..thanks for checking... On Tue, 20 Sep 2011 07:44:18 -0400, David Betten bet...@us.ibm.com wrote: There is not enough information here to determine why the job ran longer. Please send the complete joblog (not just the DFSORT messages) to dfs...@us.ibm.com and we can analyze for you. Also, be sure to send joblogs from multiple days so we can see the variance in elapsed time. Have a nice day, Dave Betten DFSORT Development, Performance Lead IBM Corporation email: bet...@us.ibm.com DFSORT/MVSontheweb at http://www.ibm.com/storage/dfsort/ IBM Mainframe Discussion List IBM-MAIN@bama.ua.edu wrote on 09/20/2011 12:38:45 AM: [image removed] elapsed time for DFSORT Wang Xiaobing to: IBM-MAIN 09/20/2011 12:39 AM Sent by: IBM Mainframe Discussion List IBM-MAIN@bama.ua.edu Please respond to IBM Mainframe Discussion List Hi, Here we have a performance problem on DFSORT. The same DFSORT job run on different day have different elapsed time, the data processed is almost same. Form the job log, we find the different is the longer job show DFSORT COULD NOT DYNAMICALLY ALLOCATE THE OPTIMAL WORK DATA SET SPACE, but our DFSORT job aloways use Hiperspace instead of work data set space. Here is DFSORT log: ICE127I 0 OPTIONS: OVFLO=RC0 ,PAD=RC0 ,TRUNC=RC0 ,SPANINC=RC16,VLSCMP=N,SZERO=Y,RESET=Y,VSAMEMT=Y,DYNSPC=256 ICE128I 0 OPTIONS: SIZE=57313801,MAXLIM=1048576,MINLIM=450560,EQUALS=N,LIST=Y,ERET=RC16 ,MSGDDN=SYSOUT ICE129I 0 OPTIONS: VIO=N,RESDNT=ALL ,SMF=NO ,WRKSEC=Y,OUTSEC=Y,VERIFY=N,CHALT=N,DYNALOC=(SYSDA ,004),ABCODE=MSG ICE130I 0 OPTIONS: RESALL=4096,RESINV=0,SVC=109 ,CHECK=Y,WRKREL=Y,OUTREL=Y,CKPT=N,COBEXIT=COB2 ICE131I 0 OPTIONS: TMAXLIM=6291456,ARESALL=0,ARESINV=0,OVERRGN=65536,CINV=Y,CFW=Y,DSA=64 ICE132I 0 OPTIONS: VLSHRT=N,ZDPRINT=Y,IEXIT=N,TEXIT=N,LISTX=N,EFS=NONE ,EXITCK=S,PARMDDN=DFSPARM ,FSZEST=N ICE133I 0 OPTIONS: HIPRMAX=OPTIMAL,DSPSIZE=MAX ,ODMAXBF=0,SOLRF=Y,VLLONG=N,VSAMIO=N,MOSIZE=MAX ICE235I 0 OPTIONS: NULLOUT=RC0 ... ICE258I 0 DFSORT COULD NOT DYNAMICALLY ALLOCATE THE OPTIMAL WORK DATA SET SPACE ICE165I 0 TOTAL WORK DATA SET TRACKS ALLOCATED: 33480 , TRACKS USED: 0 ICE199I 0 MEMORY OBJECT STORAGE USED = 0M BYTES ICE180I 0 HIPERSPACE STORAGE USED = 11628272K BYTES ICE188I 0 DATA SPACE STORAGE USED = 0K BYTES ... And, we checked the SMF TYPE30 for these 2 job, it shows the total connect time(SMF30TCN) obviously increased..and the increased connect time(SMF30DCT ) is only used for SYSOUT DD.. My question is : Q1, why DFSORT COULD NOT DYNAMICALLY ALLOCATE THE OPTIMAL WORK DATA SET SPACE ? and how to correct it ? we do not change the JOB. Q2, In this case, we use Hiperspace instead of work data set space, ICE258I will impace the total connect time ? and cause the elapsed become longer ? Q3, What's the possible root reason increased the total connect time(SMF30TCN) ? Welcome any comments...TIA. WXB. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: elapsed time for DFSORT
There is not enough information here to determine why the job ran longer. Please send the complete joblog (not just the DFSORT messages) to dfs...@us.ibm.com and we can analyze for you. Also, be sure to send joblogs from multiple days so we can see the variance in elapsed time. Have a nice day, Dave Betten DFSORT Development, Performance Lead IBM Corporation email: bet...@us.ibm.com DFSORT/MVSontheweb at http://www.ibm.com/storage/dfsort/ IBM Mainframe Discussion List IBM-MAIN@bama.ua.edu wrote on 09/20/2011 12:38:45 AM: [image removed] elapsed time for DFSORT Wang Xiaobing to: IBM-MAIN 09/20/2011 12:39 AM Sent by: IBM Mainframe Discussion List IBM-MAIN@bama.ua.edu Please respond to IBM Mainframe Discussion List Hi, Here we have a performance problem on DFSORT. The same DFSORT job run on different day have different elapsed time, the data processed is almost same. Form the job log, we find the different is the longer job show DFSORT COULD NOT DYNAMICALLY ALLOCATE THE OPTIMAL WORK DATA SET SPACE, but our DFSORT job aloways use Hiperspace instead of work data set space. Here is DFSORT log: ICE127I 0 OPTIONS: OVFLO=RC0 ,PAD=RC0 ,TRUNC=RC0 ,SPANINC=RC16,VLSCMP=N,SZERO=Y,RESET=Y,VSAMEMT=Y,DYNSPC=256 ICE128I 0 OPTIONS: SIZE=57313801,MAXLIM=1048576,MINLIM=450560,EQUALS=N,LIST=Y,ERET=RC16 ,MSGDDN=SYSOUT ICE129I 0 OPTIONS: VIO=N,RESDNT=ALL ,SMF=NO ,WRKSEC=Y,OUTSEC=Y,VERIFY=N,CHALT=N,DYNALOC=(SYSDA ,004),ABCODE=MSG ICE130I 0 OPTIONS: RESALL=4096,RESINV=0,SVC=109 ,CHECK=Y,WRKREL=Y,OUTREL=Y,CKPT=N,COBEXIT=COB2 ICE131I 0 OPTIONS: TMAXLIM=6291456,ARESALL=0,ARESINV=0,OVERRGN=65536,CINV=Y,CFW=Y,DSA=64 ICE132I 0 OPTIONS: VLSHRT=N,ZDPRINT=Y,IEXIT=N,TEXIT=N,LISTX=N,EFS=NONE ,EXITCK=S,PARMDDN=DFSPARM ,FSZEST=N ICE133I 0 OPTIONS: HIPRMAX=OPTIMAL,DSPSIZE=MAX ,ODMAXBF=0,SOLRF=Y,VLLONG=N,VSAMIO=N,MOSIZE=MAX ICE235I 0 OPTIONS: NULLOUT=RC0 ... ICE258I 0 DFSORT COULD NOT DYNAMICALLY ALLOCATE THE OPTIMAL WORK DATA SET SPACE ICE165I 0 TOTAL WORK DATA SET TRACKS ALLOCATED: 33480 , TRACKS USED: 0 ICE199I 0 MEMORY OBJECT STORAGE USED = 0M BYTES ICE180I 0 HIPERSPACE STORAGE USED = 11628272K BYTES ICE188I 0 DATA SPACE STORAGE USED = 0K BYTES ... And, we checked the SMF TYPE30 for these 2 job, it shows the total connect time(SMF30TCN) obviously increased..and the increased connect time(SMF30DCT ) is only used for SYSOUT DD.. My question is : Q1, why DFSORT COULD NOT DYNAMICALLY ALLOCATE THE OPTIMAL WORK DATA SET SPACE ? and how to correct it ? we do not change the JOB. Q2, In this case, we use Hiperspace instead of work data set space, ICE258I will impace the total connect time ? and cause the elapsed become longer ? Q3, What's the possible root reason increased the total connect time(SMF30TCN) ? Welcome any comments...TIA. WXB. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
elapsed time for DFSORT
Hi, Here we have a performance problem on DFSORT. The same DFSORT job run on different day have different elapsed time, the data processed is almost same. Form the job log, we find the different is the longer job show DFSORT COULD NOT DYNAMICALLY ALLOCATE THE OPTIMAL WORK DATA SET SPACE, but our DFSORT job aloways use Hiperspace instead of work data set space. Here is DFSORT log: ICE127I 0 OPTIONS: OVFLO=RC0 ,PAD=RC0 ,TRUNC=RC0 ,SPANINC=RC16,VLSCMP=N,SZERO=Y,RESET=Y,VSAMEMT=Y,DYNSPC=256 ICE128I 0 OPTIONS: SIZE=57313801,MAXLIM=1048576,MINLIM=450560,EQUALS=N,LIST=Y,ERET=RC16 ,MSGDDN=SYSOUT ICE129I 0 OPTIONS: VIO=N,RESDNT=ALL ,SMF=NO ,WRKSEC=Y,OUTSEC=Y,VERIFY=N,CHALT=N,DYNALOC=(SYSDA ,004),ABCODE=MSG ICE130I 0 OPTIONS: RESALL=4096,RESINV=0,SVC=109 ,CHECK=Y,WRKREL=Y,OUTREL=Y,CKPT=N,COBEXIT=COB2 ICE131I 0 OPTIONS: TMAXLIM=6291456,ARESALL=0,ARESINV=0,OVERRGN=65536,CINV=Y,CFW=Y,DSA=64 ICE132I 0 OPTIONS: VLSHRT=N,ZDPRINT=Y,IEXIT=N,TEXIT=N,LISTX=N,EFS=NONE ,EXITCK=S,PARMDDN=DFSPARM ,FSZEST=N ICE133I 0 OPTIONS: HIPRMAX=OPTIMAL,DSPSIZE=MAX ,ODMAXBF=0,SOLRF=Y,VLLONG=N,VSAMIO=N,MOSIZE=MAX ICE235I 0 OPTIONS: NULLOUT=RC0 ... ICE258I 0 DFSORT COULD NOT DYNAMICALLY ALLOCATE THE OPTIMAL WORK DATA SET SPACE ICE165I 0 TOTAL WORK DATA SET TRACKS ALLOCATED: 33480 , TRACKS USED: 0 ICE199I 0 MEMORY OBJECT STORAGE USED = 0M BYTES ICE180I 0 HIPERSPACE STORAGE USED = 11628272K BYTES ICE188I 0 DATA SPACE STORAGE USED = 0K BYTES ... And, we checked the SMF TYPE30 for these 2 job, it shows the total connect time(SMF30TCN) obviously increased..and the increased connect time(SMF30DCT ) is only used for SYSOUT DD.. My question is : Q1, why DFSORT COULD NOT DYNAMICALLY ALLOCATE THE OPTIMAL WORK DATA SET SPACE ? and how to correct it ? we do not change the JOB. Q2, In this case, we use Hiperspace instead of work data set space, ICE258I will impace the total connect time ? and cause the elapsed become longer ? Q3, What's the possible root reason increased the total connect time(SMF30TCN) ? Welcome any comments...TIA. WXB. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
