On 2/11/2011 8:59 AM, Jeff Holst wrote:
I ran into an issue recently when testing the Fault Analyzer GUI. One of its
functions causes the Fault Analyzer GUI server to try to read a member if the
user's ISPF profile data set. This was failing because we have this data set
allocated as DISP=OLD in the TSO user's address space. Needless to say the
function does not work so well when the TSO user is logged on.
I did some research and found that the ISPF documentation has plenty of
examples showing how to set up a TSO logon proc or CLIST to allocate the
required ISPF data sets. Some show ISPPROF with DISP=SHR, but more show
it with DISP=OLD. I have yet to find a firm recommentation as to which way
this should be allocated.
I doubt that update integrety would be an issue in our environment, as the
userid is the HLQ for the data set, and we do not permit users to be logged on
more than once within the same sysplex.
Is allocating this data set DISP=OLD a throwback to some earlier epic, and the
doc (and our shop) has simply not caught up, or is there a good reason why
we should keep this as it is?
Jeff Holst
Fiserv
But if the Fault Analyzer server is trying to read, it should
be using DISP=SHR, so even if you have DISP=OLD on the same
data set, there should be no conflict. I can read a member in
a PDS from ISPF edit and a colleague can view the same member
from their TSO session. Maybe the Fault Analyzer needs to be
set up with DISP=SHR for the data set in question.
--
Kind regards,
-Steve Comstock
The Trainer's Friend, Inc.
303-393-8716
http://www.trainersfriend.com
* To get a good Return on your Investment, first make an investment!
+ Training your people is an excellent investment
* Try our new tool for calculating your Return On Investment
for training dollars at
http://www.trainersfriend.com/ROI/roi.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
