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