On Sun, 16 Oct 2005 14:54:25 -0500, Ed Gould <[EMAIL PROTECTED]> wrote:
>>
>Which brings up a question, which has something to do with
>syslog/operlog.
>
>Just curious as to which installations give full viewing of
>syslog/operlog to *ALL* individuals?
>
Programmers and tech support (operations, system programming, etc.) get
syslog. Only operations and system programmers have access to the
operlog logstream (the logstream is protected via RACF).
When I first implemented operlog that was going to cause a problem
because when SDSF first started supporting operlog, the default was
to use it if active when typing the LOG command. That default could
be changed in the ISFPARMS, but no one thought about that at the time.
So hundereds of users ended up with the setting to use operlog saved
in their ISPF profiles (it didn't matter what the ISFPARMS were changed
to). Then once you protect the logstream and the user issues the LOG
command from SDSF, all they would see is (IIRC) "no records found". I
don't think any RACF violation was displayed either, even with WTPMSG
turned on (even if it did, I couldn't guaranted users had WTPMSG turned
on).
I ended up adding 2 lines of code to the sample ISFUSER exit to force
SYSLOG any time the LOG command is issued:
INITCK DS 0H INITIALIZATION USER CHECK
MVI UPRSTLOG,C'S' SET LOG DEFAULT TO "SYSLOG"
B RETURN RETURN TO CALLER
If someone wants the operlog, they have to issue "LOG O". We still
have this exit in place. It had another benefit also. The performance
of SDSF with operlog was really poor back then - especially for
backwards searches - so this kept people in the syslog for the most
part. I think changes were made to both logger and SDSF to help address
the performance issues, but I can't say for sure how much better it is
now.
Unless I'm looking at a "sysplex issue" or issuing a cross system
command where the entire output does not get displayed in my ULOG,
I generally don't get into the operlog. It's great for archiving
and searching after the fact since you only have one combined file
to deal with.
Mark
--
Mark Zelden
Sr. Software and Systems Architect - z/OS Team Lead
Zurich North America and Farmers Insurance Group
mailto: [EMAIL PROTECTED]
Systems Programming expert at http://Search390.com/ateExperts/
Mark's MVS Utilities: http://home.flash.net/~mzelden/mvsutil.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
