IBM Mainframe Forum

[saurabh pune]

Hi,
I am using the below JCL for.

1) Sorting the input files with KEY1, KEY2, KEY3 and KEY4 ( Already using 46 SortWK files)
2) Sorting the o/p of 1st step with KEY1, KEY2 and KEY3 using SUMFIELDS=NONE for removing duplicates( Already using 46 SortWK files)

3) Cobol program to compare the current file (O/P from 2nd step with previous version)
4) Cobol Program : Formatting of File
5) Sort Step : Adding a header to this file
6) Copying the O/P from 2nd step as previous file for comaring it next time.

The majority of time (80%) is taken by the 1st and 2nd steps to complete.

I/P File : RECFM=FB,LRECL=265
We are using SYNCSORT FOR Z/OS 1.4.0.1R

SYSOUT for the SORT in the first step is :

Select all

WER276B  SYSDIAG= 104402, 282114, 282114, 392325                             
WER164B  18,032K BYTES OF VIRTUAL STORAGE AVAILABLE, MAX REQUESTED,           
WER164B     0 BYTES RESERVE REQUESTED, 17,696K BYTES USED                     
WER146B  32K BYTES OF EMERGENCY SPACE ALLOCATED                               
WER108I  SORTIN   : RECFM=FB   ; LRECL=   265; BLKSIZE= 27825                 
WER073I  SORTIN   : DSNAME=HLQ.ABC.XYZ.G001V00                       
WER110I  SORTOUT  : RECFM=FB   ; LRECL=   265; BLKSIZE= 32595                 
WER074I  SORTOUT  : DSNAME= HLQ.XYZ.ABC1                         
WER410B  17,004K BYTES OF VIRTUAL STORAGE AVAILABLE ABOVE THE 16MEG LINE,     
WER410B     0 BYTES RESERVE REQUESTED, 16,980K BYTES USED                     
WER036B  G=61165,B=17,BIAS=01                                                 
WER162B  2,235,000 PREALLOCATED SORTWORK TRACKS, 0 DYNAMICALLY ALLOCATED,     
WER162B     0 ACQUIRED IN SECONDARY EXTENTS, 676,995 RELEASED, TOTAL OF 1,557,
WER124I  PREALLOCATED/USED SORTWORK SPACE USAGE FACTOR = 1.43                 
WER045C  END SORT PHASE                                                       
WER211B  SYNCSMF  CALLED BY SYNCSORT; RC=0000                                 
WER449I  SYNCSORT GLOBAL DSM SUBSYSTEM ACTIVE                                 
WER416B  BSAM WAS USED FOR SORTIN                                             
WER416B  BSAM WAS USED FOR SORTOUT                                           

Please let me know If I could provide you with any other information

Is there some way here to tune the performance of the first two sort steps and reduce the run time ?

Thanks,
S

[dick scherrer]

Hello,

Is there some way here to tune the performance of the first two sort steps and reduce the run time

Maybe. . .

On what media is the input data? How long does each step now run? How busy was the system (nearly empty or very busy). Running a test at some off-peak hour may change the run time.

Was there some reason to post only part of the Syncsort informational messages?

[saurabh pune]

Hi Dick,

Some More Info :
I/P File is on the Disk, Not on Tape
1st step runs for almost 4-5 hrs and 2nd step 1.5 - 2 hrs and other 4 in almost 30 mins.
System Busy or Empty? Could you please guide me on how to check this info.
Ran the test at Off-Peak hour improves the total run time by arnd 20-30 mins , marginally not much of a difference .

Posted all the Messages, Nothing intentional. Let me know if we would need other parts I would surely post those If that helps me .

Thanks a lot for your time Dick.

Regards,
Saurabh

[NicC]

I am not familiar with Syncsort but nowhere do I see the record count - nor do you mention it in your post. Also, nowhere do I see your sort cards so no one can comment on them. Have you tried letting Syncsort dynamically allocate its work files?

[dick scherrer]

Hello,

You're welcome

Posted all the Messages

Hmmm. . .

When i run Syncsort, i get:
The product release.
The sort control statements submitted.
Record counts.
And a bit of other info. . .

System Busy or Empty? Could you please guide me on how to check this info.

Best to check with your Scheduling or Operations people. They will know when the system is heavily loaded and when it is nearly empty (if it ever is). You can also display all of the active processes and when there are several screens of things running the system will most likely be busy while when there are few active, the system will be not so busy. At the top of the display there should be a line that shows how busy the system is overall. Some organizations also publish hour by hour statistics of how busy the system has been over the last day/week/month - whatever.

Is there some chance that either of the 2 large files are being used by some other process at the same time? If yes, this can be a killer.

It may help if you post the JCL used for the first 2 steps.

[BillyBoyo]

From what you have said, but not yet shown, your second step is sorting an already-sorted file. You've used Cobol elsewhere, I'm surprised you didn't consider it for this. Even then, you have to think "it must be possible in sort" and start to look at the "tool" options and start to wonder if anything can even be built into the first step to do it.

But we'd need to see what your sort steps look like, as has already been asked.

[Alissa Margulies]

Hello saurabh pune.

If you are still looking to tune this application, please forward the complete job listing (including the JES Job Log, JCL, SYSOUT, and SYNCSORT messages) to zos_tech@syncsort.com and we would be happy to further assist you.

Regards,

[saurabh pune]

Thanks, Stopped working on this got a partial solution, Combined 1st and 2nd step, although not much successful in the results.

Thanks a ton though..

[BillyBoyo]

Can't believe you're going to let the offer go by. It's not work you have to do, beyond sending an e-mail

[anurag_87]

Hi Saurabh,
Can you try this:-
1)Combine Step1 and Step2:-Also verify in the job log how many sort work volumes your job uses while sorting and remove if you are having additional volumes.Sort work volumes should be much more costlier than CPU sec.
Specify MINCORE parm too for such huge sorting.This will ensure your job does not fail with error mention.

2)Step3-Step6 may also be done by using syncosrt join keys and outrec etc.Sort is most of the time more effecient then cobol.

Also last but not the least,can you check if your job is more I/O bound or CPU bound.
If its I/O bound I would recommend to do all your step via a assembler/cobol program, it would complete faster.

Regards
Anurag