Re: SDSF DA in sysplex
You could also use the SYSNAME * and then have them enter two filter lines for SYSNAME EQ xxyy where just those two systems are included in the list. Can't say if it'll perform any better, but it's worth a try! HTH, Gary Diehl MVS Support The glass is neither half full or half empty; the engineer who designed the glass simply allowed for a 100% increase in fluid storage. -Original Message- From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of Beesley, Paul Sent: Wednesday, March 05, 2008 8:51 AM To: IBM-MAIN@BAMA.UA.EDU Subject: Re: SDSF DA in sysplex Thanks Mark, that's what I thought. -- 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
Re: SDSF DA in sysplex
On Wed, 5 Mar 2008 14:55:03 +0100, Beesley, Paul [EMAIL PROTECTED] wrote: A customer currently uses RMF to provide DA information in SDSF; with sysplex scope. They are now joing another sysplex which will have up to 13 members, and SDSF DA command is performing badly due to slow response from other systems. Is there some way to retain sysplex DA capability while restricting the scope to just the customer's 2 LPARs ? I don't think there is. But you can restrict the use of the SYSNAME command or force it to default to the current system in the ISFUSER exit for all but privileged users. I still force LOG S (syslog) if someone issues the LOG command due to past performance problems with the OPERLOG (because the LOG preference is saved in the profile). If someone wants the operlog they have to specify LOG O.We also protect the operlog logstream, but that is a different issue. Mark -- Mark Zelden Sr. Software and Systems Architect - z/OS Team Lead Zurich North America / Farmers Insurance Group - ZFUS G-ITO mailto:[EMAIL PROTECTED] z/OS Systems Programming expert at http://expertanswercenter.techtarget.com/ 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
Re: SDSF DA in sysplex
Thanks Mark, that's what I thought. Pity the LPARs don't start with the same characters, I could have forced SYSNAME XX* or whatever... Paul -Original Message- I don't think there is. But you can restrict the use of the SYSNAME command or force it to default to the current system in the ISFUSER exit for all but privileged users. I still force LOG S (syslog) if someone issues the LOG command due to past performance problems with the OPERLOG (because the LOG preference is saved in the profile). If someone wants the operlog they have to specify LOG O.We also protect the operlog logstream, but that is a different issue. Mark -- Mark Zelden Sr. Software and Systems Architect - z/OS Team Lead Zurich North America / Farmers Insurance Group - ZFUS G-ITO mailto:[EMAIL PROTECTED] z/OS Systems Programming expert at http://expertanswercenter.techtarget.com/ 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 -- 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
Re: SDSF DA in sysplex
On Wed, 5 Mar 2008 15:51:29 +0100, Beesley, Paul [EMAIL PROTECTED] wrote: Thanks Mark, that's what I thought. Pity the LPARs don't start with the same characters, I could have forced SYSNAME XX* or whatever... Even with 13 or more systems, I don't know why sysplex DA would be performing badly due to slow response from other systems. RMF should be running in SYSSTC and access to the data is from the sysplex data server. Also, looking at the doc... perhaps you could prevent access from the other systems using the ERBSDS.MON2DATA RACF profile in the FACILITY class. I've never done this, but it looks like it would be defined on all the other systems you don't want to see in the DA display. Since it would still make the RACF call on the other system, I don't know what this would do in your scenario in regards to performance. But if the userids don't match on the other systems or aren't defined, then even a SYSNAME * should allow just a subset of just the systems you are adding to the sysplex to be displayed. See the RMF and SDSF manuals for more information. Mark -- Mark Zelden Sr. Software and Systems Architect - z/OS Team Lead Zurich North America / Farmers Insurance Group - ZFUS G-ITO mailto:[EMAIL PROTECTED] z/OS Systems Programming expert at http://expertanswercenter.techtarget.com/ 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
