-----------------------------------<snip>------------------------------
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
--------------------------------<unsnip>-----------------------------------------
While I can't comment to your single case, I can tell you that,in
general, processing data from the SPOOL can be pretty slow, because of
all the "machinations" necessary to retrieve the data and get it where
you need it. Let me suggest this: send the report output to a DASD file,
then use IEBGENER to spool it. You ancillary processing can access the
DASD file and you'll still have a SPOOL file you can print, or delete,
as the situation dictates.
--
Rick
--
Remember that if you’re not the lead dog, the view never changes.
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html
