So true Dave,
What is obvious to some of us is obviously not so obvious to others ;-)
Another thing that has been suggested on this list is to have a section of
the USER DIRECT for LINUX guests so you can see what you have by just
looking at the USER DIRECT of course this is for those that are using
DIRECTXA and have no directory maintenance product .
ex:
***************************************************************
* z/VM 5.3.0 SYSTEM DIRECTORY *
***************************************************************
************************************************************
* 3rd Party Products
************************************************************
************************************************************
* BBH User Id's
************************************************************
************************************************************
* BBH z/LINUX user id's
************************************************************
************************************************************
* BBH 2nd Level Guest for NEW Version of z/VM 5.4.0
************************************************************
munson
201-418-7588
Dave Jones <d...@vsoft-software.com>
Sent by: The IBM z/VM Operating System <IBMVM@LISTSERV.UARK.EDU>
08/13/2009 09:31 AM
Please respond to
The IBM z/VM Operating System <IBMVM@LISTSERV.UARK.EDU>
To
IBMVM@LISTSERV.UARK.EDU
cc
Subject
Re: How to tell how many linux running on z/VM?
Well, simple for you, Bill, with your mumble, mumble years of VM
experience....:-) You already know that the ESAxxxx machines are
Velocity products, FTPSERVE, PORTMAP, SMTP, etc. are part of the VM
TCP/IP stack, and so forth. That knowledge may not be available to folks
just now getting their feet wet in a VM environment.
That's why I suggested the TRACK approach....it's an explicit and
deterministic method for identifying Linux guests.
Have a good one.
Bill Munson wrote:
> I too am confused as to why "Q NAMES" would not work ?
>
> q names
> WATCHER - DSC , MLXORA2S - DSC , MLXORA1S - DSC , MLXWP01S - DSC
> MLXAP01S - DSC , MLXESS2S - DSC , MLXESS1S - DSC , DTCVSW1 - DSC
> VSMPROXY - DSC , VMRMADMN - DSC , VMRMSVM - DSC , VMBACKUP - DSC
> VMUTIL - DSC , ESAALERT - DSC , ESAWEB02 - DSC , ESAWEB01 - DSC
> ESAADMIN - DSC , PERFSVM - DSC , ESAWRITE - DSC , ESATCP - DSC
> RSCS - DSC , ESASERVE - DSC , GCS - DSC , VSMSERVE - DSC
> SMTP - DSC , REXECD - DSC , PORTMAP - DSC , FTPSERVE - DSC
> SNMPD - DSC , TCPIP - DSC , DTCVSW2 - DSC , OPERSYMP - DSC
> DISKACNT - DSC , EREP - DSC , OPERATOR - DSC , NJ2W002 -L0004
> VSM - TCPIP
> Munson at zVM3; T=0.01/0.01 08:09:23
>
> It is pretty easy to pick out the 6 LINUX guests running on my sandbox
> system
>
> Bill Munson
> Sr. z/VM Systems Programmer
> Brown Brothers Harriman & CO.
> 525 Washington Blvd.
> Jersey City, NJ 07310
> 201-418-7588
>
>
>
>
> sunny...@wcb.ab.ca
> Sent by: The IBM z/VM Operating System <IBMVM@LISTSERV.UARK.EDU>
> 08/12/2009 05:49 PM
> Please respond to
> The IBM z/VM Operating System <IBMVM@LISTSERV.UARK.EDU>
>
>
> To
> IBMVM@LISTSERV.UARK.EDU
> cc
>
> Subject
> How to tell how many linux running on z/VM?
>
>
>
>
>
>
>
> I was asked to find out how many linux guests are running on our z/VM?
> the cp commands:Q N is not very suitable for this question.
> What is the better way?
> This message is intended only for the addressee. It may contain
privileged
> or confidential information. Any unauthorized disclosure is strictly
> prohibited. If you have received this message in error, please notify us
> immediately so that we may correct our internal records. Please then
> delete the original email. Thank you. (Sent by Webgate1)
>
--
Dave Jones
V/Soft
www.vsoft-software.com
Houston, TX
281.578.7544
*************************** IMPORTANT
NOTE***************************** The opinions expressed in this
message and/or any attachments are those of the author and not
necessarily those of Brown Brothers Harriman & Co., its
subsidiaries and affiliates ("BBH"). There is no guarantee that
this message is either private or confidential, and it may have
been altered by unauthorized sources without your or our knowledge.
Nothing in the message is capable or intended to create any legally
binding obligations on either party and it is not intended to
provide legal advice. BBH accepts no responsibility for loss or
damage from its use, including damage from virus.
************************************************************************
