>IPCS won't necessarily think about the WHOLE data space, just enough >locations adjacent to the final byte in the space to fill the screen on >the storage panel. Smart code processing data spaces notices such things >as invalid segments in a data space and produces big numeric answers >along the way. Similar smart code processing address spaces also thinks >about invalid regions. So IPCS is even smarter than I thought!
>After a short while (certainly not instantaneous, or even within 1/2 a >minute - maybe a couple minutes later (I stepped away)) I was presented >with a screen that had only the top line with a message, >stating "7FFFFFFFFF.: FFFFFFFF_FFFFFFFF Storage not available." >When I hit PF7 to go backwards, my TSO session was locked up and timed >out an hour or so later. Whenever I had similar performance problems, my dump directory was very much fragmented with CI/CA splits. It usually helped to just delete/define the dump directory and redo the analysis. If you still have that problem with a fresh directory (you could use a different name to start with and repro the old data in - just make it big enough), then at least you'll know it's not VSAM related. What I also do in cases like this is take a dump of my hung user and look at the trace table to see what I am doing. Best regards, Barbara -- Lust, ein paar Euro nebenbei zu verdienen? Ohne Kosten, ohne Risiko! Satte Provisionen für GMX Partner: http://www.gmx.net/de/go/partner ---------------------------------------------------------------------- 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
