Dave,  see Mark Brooks' responses.    

While I see this as more of a cosmetic change than anything, based on 
this thread, my 2% of messages that didn't fit, wanting to satisfy the
health check without deleting it and lastly - because it can't hurt...

I have added transport class definitions to my monoplex
production and sandbox LPARs.   For the production LPARs I 
made the changes dynamically with SETXCF.   

 /****************************************/                          
 /* MONOPLEX CLASSDEF FOR XCF MESSAGES   */                          
 /****************************************/                          
 CLASSDEF CLASS(DEFAULT) CLASSLEN(956)   GROUP(UNDESIG) MAXMSG(2000) 
 CLASSDEF CLASS(XCF4K)   CLASSLEN(4028)  GROUP(UNDESIG) MAXMSG(2000) 
 CLASSDEF CLASS(XCF8K)   CLASSLEN(8124)  GROUP(UNDESIG) MAXMSG(2000) 


Below is a display from a sandbox LPAR where I IPLed with the changes over
the weekend:

D XCF,CD,CLASS=ALL                                               
IXC344I  09.28.34  DISPLAY XCF 360                               
   TRANSPORT     CLASS        DEFAULT     ASSIGNED               
   CLASS         LENGTH       MAXMSG      GROUPS                 
   DEFAULT         956          2000      UNDESIG                
   XCF4K          4028          2000      UNDESIG                
   XCF8K          8124          2000      UNDESIG                
                                                                 
DEFAULT TRANSPORT CLASS USAGE FOR SYSTEM M108                    
SUM MAXMSG:       2000    IN USE:          2  NOBUFF:          0 
  SEND CNT:       3392  BUFFLEN (FIT):   956                     
                                                                 
XCF4K TRANSPORT CLASS USAGE FOR SYSTEM M108                      
SUM MAXMSG:       2000    IN USE:          0  NOBUFF:          0 
  SEND CNT:       1255  BUFFLEN (FIT):  4028                     
                                                                 
XCF8K TRANSPORT CLASS USAGE FOR SYSTEM M108                      
SUM MAXMSG:       2000    IN USE:          0  NOBUFF:          0 
  SEND CNT:         19  BUFFLEN (FIT):  8124                     


--
Mark Zelden - Zelden Consulting Services - z/OS, OS/390 and MVS       
mailto:[email protected]                                        
Mark's MVS Utilities: http://www.mzelden.com/mvsutil.html 
Systems Programming expert at http://expertanswercenter.techtarget.com/


On Sun, 1 Apr 2012 10:18:31 +0200, Vernooij, CP - SPLXM <[email protected]> 
wrote:

>XCF works only within a sysplex.
>D XCF,G tells you which groups have been created.
>D XCF,G,groupname,ALL tells you who has connected to the group and how
>much traffic has travelled in the group.
>
>Kees.
>
>
>"Gibney, Dave" <[email protected]> wrote in message
>news:<[email protected]>...
>>    I run monoplexs. Like I expect most other small shops.
>>    4 LPARS, only shared DASD, no CTC connections. There are TCPIP
>Hipersocket links, but as far as I know, XCF is not aware of these
>links.  What/Who are the typical users of XCF signaling in a monoplex.
>How would I know if they are experiencing degraded or inefficient
>signaling?
>>

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN

Reply via email to