OK Thanks Andy, I'll give it gao when I have some time to have a play.
Cheers
Gerry Anstey
Andy Wood
<[email protected]
OM.AU> To
Sent by: IBM [email protected]
Mainframe cc
Discussion List
<[email protected] Subject
.edu> Re: SDSF - so slow!
04/02/2009 23:13
Please respond to
IBM Mainframe
Discussion List
<[email protected]
.edu>
This sounds suspiciously like something I saw with SDSF a long time ago. I
like
to think that things would have improved by now, but who knows? This is how
you could tell:
If you don't have the original job still on spool run a job to create a
test
SYSOUT dataset. Use something that will write records that don't contain
lots
of blanks, and the more records the better - several million would be good.
Create a job to run SDSF in batch to select your test SYSOUT and capture it
to a DASD dataset (or even to DD DUMMY), using the SDSF PRINT command,
but set it up to not capture the whole test dataset - use something
like "PRINT 1 500000".
Run your SDSF batch job a number of times, varying the number of records
printed, by changing the second number of the PRINT range. Try it for say
500000, 1000000, 1500000 etc and see how the resource usage, particularly
CPU time increases as it processes more records.
If you find that CPU time increases disproportionally with increasing
number of
records processed, you probably have the same problem I found, where it
became unusable for very large datasets. If it is still like that you could
try
opening a PMR. If they tell you that you are the only one to ever have this
problem, suggest that they search the PMR archive for about 1998, looking
for
the words ISFDSRC and PARROT.
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 [email protected] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html
