Mark Zelden wrote: >I didn't find out, just a hunch based on a long history of working on various ISPF issues over the years. When something only affects a single user and there doesn't seem to be a good explanation, it's often due to something in their ISPPROF.
Thanks very much for your kind reply. You've made my day! ;-D As storage admin in a previous life (!) I also found out on the hard way that ISPPROF could be damaged due to buggy apps, full directory or just simply without space for future growth. I agree fully with you - if only one id is affected, something wrong is with the session, otherwise the problem is elsewhere. >Some people take the sledge hammer approach (which I never do except as a test) and delete the entire ISPPROF data set. Or just rename the dataset, followed by re-alloc and copy of members excluding the buggy member. Either restore the ISPPROF or continue with the new ISPPROF depending on the test results. >Sometimes the profile member is corrupted and there is really no choice but to delete it or it isn't worth the time to try and fix it, so deleting it is the easiest thing to do. Agreed. Many thanks! Groete / Greetings Elardus Engelbrecht ---------------------------------------------------------------------- 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
