Thanks Rob that was my advice too, It's not something we do a lot.

 I was mainly curious as to what SDSF could possibly be doing to take so
long, surely the spool is just on DASD somewhere!

thanks
GA


                                                                           
             Rob Scott                                                     
             <rsc...@rocketsof                                             
             TWARE.COM>                                                 To 
             Sent by: IBM              IBM-MAIN@bama.ua.edu                
             Mainframe                                                  cc 
             Discussion List                                               
             <ibm-m...@bama.ua                                     Subject 
             .edu>                     Re: SDSF - so slow!                 
                                                                           
                                                                           
             03/02/2009 11:36                                              
                                                                           
                                                                           
             Please respond to                                             
               IBM Mainframe                                               
              Discussion List                                              
             <ibm-m...@bama.ua                                             
                   .edu>                                                   
                                                                           
                                                                           




Gerry,

SDSF has quite a bit of overhead to read records from the spool.

My advise would be to change the GCSPROCP job to write its output directly
to a DASD file and then pass it to the next step to be processed by
Filemaster - if you still need the output on JES spool then just add an
extra IEBGENER step to copy to SYSOUT.


Rob Scott
Rocket Software, Inc
275 Grove Street
Newton, MA 02466
617-614-2305
rsc...@rs.com


-----Original Message-----
From: IBM Mainframe Discussion List [mailto:ibm-m...@bama.ua.edu] On Behalf
Of Gerry Anstey
Sent: 03 February 2009 11:25
To: IBM-MAIN@bama.ua.edu
Subject: SDSF - so slow!

OK bad design, we have lot of cack here, probably due to hiring cheap
programmers, any way, I digress.

Here s the SDSF  summary:

 PREFIX=GCSPROCP  DEST=(ALL)  OWNER=*  SYSNAME=FMVS
 NP   DDNAME   STEPNAME PROCSTEP DSID OWNER    C DEST     REC-CNT
      JESMSGLG JES2                 2 PSTGCS   T LOCAL         52
      JESJCL   JES2                 3 PSTGCS   T LOCAL         44
      JESYSMSG JES2                 4 PSTGCS   T LOCAL         94
      DDPRINT  GCSPROCP           106 PSTGCS   0 LOCAL          3
      CMPRINT  GCSPROCP           107 PSTGCS   0 LOCAL     28,559
      CMPRT01  GCSPROCP           108 PSTGCS   T LOCAL     25M

Now we had a need to extract some of the records in CMPRT01, I wrote job to
run SDSF in batch and to use the PRINT ODSN command to extract the data to
a data set.

Then I read the dataset with Filemaster and extracted the desired records
into a smaller file.

My questions are:

1. Any ideas why SDSF takes appox 90 minutes (120000 EXCPs + 31mins CPU) to
read and write out the data and Filemaster takes about 3 minutes to read
25million recs and write about 1.5million?

2. Is there any way to make SDSF extract faster?

thanks
Gerry Anstey




Generally, this communication is for informational purposes only
and it is not intended as an offer or solicitation for the purchase
or sale of any financial instrument or as an official confirmation
of any transaction. In the event you are receiving the offering
materials attached below related to your interest in hedge funds or
private equity, this communication may be intended as an offer or
solicitation for the purchase or sale of such fund(s).  All market
prices, data and other information are not warranted as to
completeness or accuracy and are subject to change without notice.
Any comments or statements made herein do not necessarily reflect
those of JPMorgan Chase & Co., its subsidiaries and affiliates.

This transmission may contain information that is privileged,
confidential, legally privileged, and/or exempt from disclosure
under applicable law. If you are not the intended recipient, you
are hereby notified that any disclosure, copying, distribution, or
use of the information contained herein (including any reliance
thereon) is STRICTLY PROHIBITED. Although this transmission and any
attachments are believed to be free of any virus or other defect
that might affect any computer system into which it is received and
opened, it is the responsibility of the recipient to ensure that it
is virus free and no responsibility is accepted by JPMorgan Chase &
Co., its subsidiaries and affiliates, as applicable, for any loss
or damage arising in any way from its use. If you received this
transmission in error, please immediately contact the sender and
destroy the material in its entirety, whether in electronic or hard
copy format. Thank you.
Please refer to http://www.jpmorgan.com/pages/disclosures for
disclosures relating to UK legal entities.

----------------------------------------------------------------------
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

Reply via email to