Q IUCV can't help in this case, Q FILEPOOL AGENT has more info: you can see who is active in SFS at that instance; with Q IUCV one can only see who made some connection with SFS since his IPL CMS (once connected to an SFS server, one remains connected). An IUCV report with -by user- counts of IUCV traffic could help to find who's sending/getting much data to/from SFS.
2008/6/11 Mike Walter <[EMAIL PROTECTED]>: > > The QIUCV EXEC level I have reports in part (edited to remove lots of > unrelated info, but leaving at least one line of each message type, and all > our SFS-related servers): > qiucv > Path Target CP System Target Msg Msg Path Path > ID Userid Service PathID Limit Count Flags Type > ----------------------------------------------------------- > 0000 OPERATOR *MSG 0000 00FF 0000 C0 IUCV > ...deleted lines... > 0000 S$SFCRR1 *BLOCKIO 0000 0010 0000 D0 IUCV > 0001 S$SFCRR1 *BLOCKIO 0001 0010 0000 D0 IUCV > 0002 S$SFCRR1 *BLOCKIO 0002 0010 0000 D0 IUCV > 0003 S$SFCRR1 *BLOCKIO 0003 0010 0000 D0 IUCV > 0004 S$SFCRR1 *BLOCKIO 0004 0010 0000 D0 IUCV > 0005 S$SFCRR1 *BLOCKIO 0005 0010 0000 D0 IUCV > 0006 S$SFCRR1 *BLOCKIO 0006 0010 0000 D0 IUCV > 0007 VMSERVS *BLOCKIO 0000 0010 0000 D0 IUCV > 0008 VMSERVS *BLOCKIO 0001 0010 0000 D0 IUCV > 0009 VMSERVS *BLOCKIO 0002 0010 0000 D0 IUCV > 000A VMSERVS *BLOCKIO 0003 0010 0000 D0 IUCV > 000B VMSERVS *BLOCKIO 0004 0010 0000 D0 IUCV > 000C S$SFACT1 *BLOCKIO 0000 0042 0000 D0 IUCV > 000D S$SFGEN1 *BLOCKIO 0000 0081 0000 D0 IUCV > 000E S$SFGEN1 *BLOCKIO 0001 0081 0000 D0 IUCV > 000F S$SFGEN1 *BLOCKIO 0002 0081 0000 D0 IUCV > 0010 S$SFPCS1 *BLOCKIO 0000 0010 0000 D0 IUCV > 0011 S$SFACT1 *BLOCKIO 0001 0042 0000 D0 IUCV > 0012 S$SFACT1 *BLOCKIO 0002 0042 0000 D0 IUCV > 0013 S$SFACT1 *BLOCKIO 0003 0042 0000 D0 IUCV > 0014 S$SFACT1 *BLOCKIO 0004 0042 0000 D0 IUCV > 0015 S$SFACT1 *BLOCKIO 0005 0042 0000 D0 IUCV > 0016 S$SFACT1 *BLOCKIO 0006 0042 0000 D0 IUCV > 0017 S$SFACT1 *BLOCKIO 0007 0042 0000 D0 IUCV > 0018 S$SFACT1 *BLOCKIO 0008 0042 0000 D0 IUCV > 0019 S$SFACT1 *BLOCKIO 0009 0042 0000 D0 IUCV > 001A S$SFACT1 *BLOCKIO 000A 0042 0000 D0 IUCV > 001B S$SFPCS1 *BLOCKIO 0001 0010 0000 D0 IUCV > 001C S$SFPCS1 *BLOCKIO 0002 0010 0000 D0 IUCV > 001D S$SFGEN1 *BLOCKIO 0003 0081 0000 D0 IUCV > 001E S$SFGEN1 *BLOCKIO 0004 0081 0000 D0 IUCV > 001F S$SFGEN1 *BLOCKIO 0005 0081 0000 D0 IUCV > 0020 S$SFGEN1 *BLOCKIO 0006 0081 0000 D0 IUCV > 0021 S$SFAUD1 *BLOCKIO 0000 0042 0000 D0 IUCV > 0022 S$SFPCS1 *BLOCKIO 0003 0010 0000 D0 IUCV > 0023 S$SFPCS1 *BLOCKIO 0004 0010 0000 D0 IUCV > 0024 S$SFPCS1 *BLOCKIO 0005 0010 0000 D0 IUCV > 0025 S$SFPCS1 *BLOCKIO 0006 0010 0000 D0 IUCV > 0026 S$SFPCS1 *BLOCKIO 0007 0010 0000 D0 IUCV > 0027 S$SFPCS1 *BLOCKIO 0008 0010 0000 D0 IUCV > 0029 S$SFPCS1 *BLOCKIO 000A 0010 0000 D0 IUCV > 002A S$SFPCS1 *BLOCKIO 000B 0010 0000 D0 IUCV > 002B S$SFPCS1 *BLOCKIO 000C 0010 0000 D0 IUCV > 002C S$SFPCS1 *BLOCKIO 000D 0010 0000 D0 IUCV > 002D S$SFPCS1 *BLOCKIO 000E 0010 0000 D0 IUCV > 002E S$SFPPS1 *BLOCKIO 0000 0061 0000 D0 IUCV > 002F S$SFPPS1 *BLOCKIO 0001 0061 0000 D0 IUCV > 0030 S$SFPPS1 *BLOCKIO 0002 0061 0000 D0 IUCV > 0031 S$SFPPS1 *BLOCKIO 0003 0061 0000 D0 IUCV > 0032 S$SFPPS1 *BLOCKIO 0004 0061 0000 D0 IUCV > 0033 S$SFPPS1 *BLOCKIO 0005 0061 0000 D0 IUCV > 0034 S$SFGEN1 *BLOCKIO 0007 0081 0000 D0 IUCV > 0035 S$SFGEN1 *BLOCKIO 0008 0081 0000 D0 IUCV > 0036 S$SFPPS1 *BLOCKIO 0006 0061 0000 D0 IUCV > 0037 S$SFPPS1 *BLOCKIO 0007 0061 0000 D0 IUCV > 0038 S$SFAUD1 *BLOCKIO 0001 0042 0000 D0 IUCV > 0039 S$SFAUD1 *BLOCKIO 0002 0042 0000 D0 IUCV > 003A S$SFAUD1 *BLOCKIO 0003 0042 0000 D0 IUCV > 003B S$SFAUD1 *BLOCKIO 0004 0042 0000 D0 IUCV > ...deleted lines... > 0000 VMSECURE *RPI 0001 3E80 0003 C0 IUCV > 0000 ESAWRITE *MONITOR 0001 003C 0000 D0 IUCV > 0000 GCS *SIGNAL 0000 00FF 0000 D0 IUCV > ...deleted lines... > 0000 TCPIP *CCS 0000 000A 0000 E0 IUCV > ...deleted lines... > 0000 OPERSYMP *SYMPTOM 0000 000A 0000 C0 IUCV > 0000 VMACCT *ACCOUNT 0000 000A 0000 C0 IUCV > 0000 EREP *LOGREC 0000 000A 0000 C0 IUCV > 0000 SYSTEM *IDENT 0000 00FF 0000 C0 IUCV > 0001 S$SFCRR1 *IDENT 0007 00FF 0000 C0 IUCV > 0002 S$SFCRR1 *IDENT 0008 00FF 0000 C0 IUCV > 0003 S$SFCRR1 *IDENT 0009 00FF 0000 C0 IUCV > 0004 S$SFCRR1 *IDENT 000A 00FF 0000 C0 IUCV > 0005 S$SFCRR1 *IDENT 000B 00FF 0000 C0 IUCV > 0006 VMSERVS *IDENT 0005 00FF 0000 C0 IUCV > 0007 S$SFPPS1 *IDENT 0008 00FF 0000 C0 IUCV > 0008 S$SFGEN1 *IDENT 0009 00FF 0000 C0 IUCV > 0009 S$SFAUD1 *IDENT 0005 00FF 0000 C0 IUCV > 000A S$SFPCS1 *IDENT 000F 00FF 0000 C0 IUCV > 000B S$SFACT1 *IDENT 000B 00FF 0000 C0 IUCV > 000C S$CPIC *IDENT 0000 00FF 0000 C0 IUCV > 000D AVSVM *IDENT 0003 00FF 0000 C0 IUCV > M2WALTER HALINVA1; T=1.28/1.71 09:09:52 > > I hope that helps to provide some useful clues. > > Mike Walter > Hewitt Associates > Any opinions expressed herein are mine alone and do not necessarily > represent the opinions or policies of Hewitt Associates. > > > > "Alan Ackerman" <[EMAIL PROTECTED]> > > Sent by: "The IBM z/VM Operating System" <IBMVM@LISTSERV.UARK.EDU> > > 06/10/2008 11:41 PM > > Please respond to > "The IBM z/VM Operating System" <IBMVM@LISTSERV.UARK.EDU> > > To > IBMVM@LISTSERV.UARK.EDU > cc > Subject > Re: SFS Control Data Backup > > > > > On Tue, 10 Jun 2008 13:17:39 -0700, Schuh, Richard <[EMAIL PROTECTED]> wrot > e: > >>It sure would be nice to know who is hammering the server. It is tough >>to correct a problem when it can't be defined. >> >>Regards, >>Richard Schuh > > There is some IUCV data in the monitor. I don't have access to <http://w > ww.vm.ibm.com/> (down?) > nor Velocity Software manuals from home. There is a QUERY IUCV command i > n z/VM 5.3.0, but it > does not include message counts. QIUCV EXEC floating around does have som > e such data -- but I'm > not sure to what level of detail. > > Alan Ackerman > Alan (dot) Ackerman (at) Bank of America (dot) com > > > ________________________________ > The information contained in this e-mail and any accompanying documents may > contain information that is confidential or otherwise protected from > disclosure. If you are not the intended recipient of this message, or if > this message has been addressed to you in error, please immediately alert > the sender by reply e-mail and then delete this message, including any > attachments. Any dissemination, distribution or other use of the contents of > this message by anyone other than the intended recipient is strictly > prohibited. All messages sent to and from this e-mail address may be > monitored as permitted by applicable law and regulations to ensure > compliance with our internal policies and to protect our business. E-mails > are not secure and cannot be guaranteed to be error free as they can be > intercepted, amended, lost or destroyed, or contain viruses. You are deemed > to have accepted these risks if you communicate with us by e-mail. -- Kris Buelens, IBM Belgium, VM customer support
