Mark said: <snip> I had the same issue with operlog years ago and I wanted the LOG command to always default to syslog. By the time we implemented OPERLOG, it was already too late since the default was "operlog if active" and already saved in everyone's profile. Besides the performance issues when sdsf operlog support came around, we also protected the logstream which would cause an error like "no records found" when people issued the log command and were not authorized for the logstream. So to this day I have the code in the ISFUSER exit but could probably get rid of the exit if all the profiles were updated via the exit (the SDSF parms were also updated years ago to make SYSLOG the default for new profiles). I probably tested this all way back then, but I can't remember the results (as far as the profile being updated to what I forced in the exit). <unsnip>
I'm looking at the same issue as I try to convert to operlog. My plan was to change the SDSF selection option on an ISPF option screen to invoke a REXX program with the ISF profile, and let the REXX program modify the profile variable before invoking SDSF. That solution might work to help you eliminate your exit and ensure profiles get updated. Taking the same process a little further, you could possibly run an off-hours job to dynamically allocate everyone's profile (one at a time, of course) and execute the REXX code to change their profiles (but not go on into SDSF). On the other hand, I'd be interested in what your exit alters to force the log default to change. ---------------------------------------------------------------------- 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
