The plot thickens...

I forgot that Ed Jaffe refuted this a few years ago:

http://bama.ua.edu/cgi-bin/wa?A2=ind0301&L=ibm-main&P=R23966&I=1

As to not re-hash the entire thread, *please* search the archives
or google for "TSO ISPPROF heavy usage".

Mark
--
Mark Zelden
Sr. Software and Systems Architect - z/OS Team Lead
Zurich North America and Farmers Insurance Group
mailto: [EMAIL PROTECTED]
Systems Programming expert at http://Search390.com/ateExperts/
Mark's MVS Utilities: http://home.flash.net/~mzelden/mvsutil.html




On Tue, 30 Aug 2005 10:27:48 -0500, Mark Zelden <[EMAIL PROTECTED]>
wrote:

>On Tue, 30 Aug 2005 09:49:22 -0500, John P Kalinich <[EMAIL PROTECTED]>
>wrote:
>
>>Below is the discussion from ISPF-L that Mark Zelden was referring to.
>
>That's it!  Thank you John... saved me a search of the archives.  BTW,
>that post was from 7 years ago (Oct. 5 1998).
>
>Mark
>
>
>>
>>Regards,
>>John Kalinich
>>Computer Sciences Corp
>>--
>>
>>Monitor your ECSA usage.  It may increase if you have dozens or hundreds
of
>>users with ISPPROF datasets as PDSEs.
>>
>>We normally recommend against having ISPF profile datasets being PDSEs
>>because ISPF uses update-in-place and has padding in profile dataset
>>members to usually avoid x37 abends while writing to ISPPROF.  Also, as
>>mentioned above, open PDSEs use storage in ECSA, even if they are not
>>shared.  Finally, the performance of PDS is usually better than PDSE for
>>ISPF profile datasets.
>>
>>Dave Levish
>>Former PDSE Developer
>>
>
>----------------------------------------------------------------------
>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

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

Reply via email to