The question was how to tell how many Linux guests are running. Other types of users may inhabit the system. There are service machines (TCPIP, RSCS, etc.), operations machines (OPERATOR, OPERATNS, etc.), CMS users (MAINT, sysprog userids, etc.) that are included in the mix. If all you are counting are Linux guests, you need some way to either eliminate the non-Linux guests from the results of Q N, or to positively identify which guests are Linux. If you do not filter the results of Q N, then you might as well make it easy on yourself and use Q U, instead.
Regards, Richard Schuh > -----Original Message----- > From: The IBM z/VM Operating System > [mailto:ib...@listserv.uark.edu] On Behalf Of Martin, Terry > R. (CMS/CTR) (CTR) > Sent: Wednesday, August 12, 2009 5:23 PM > To: IBMVM@LISTSERV.UARK.EDU > Subject: Re: How to tell how many linux running on z/VM? > > I agree with Mark, why is the Q N command not suitable, maybe > I am missing something or don't understand what Sunny is > asking. I would just write a simple PIPE grabbing count them > and write them to a file or to the console along with the count. > > Thank You, > > Terry Martin > Lockheed Martin - Information Technology z/OS & z/VM Systems > - Performance and Tuning Cell - 443 632-4191 Work - 410 > 786-0386 terry.mar...@cms.hhs.gov > > -----Original Message----- > From: The IBM z/VM Operating System > [mailto:ib...@listserv.uark.edu] On Behalf Of P S > Sent: Wednesday, August 12, 2009 8:04 PM > To: IBMVM@LISTSERV.UARK.EDU > Subject: Re: How to tell how many linux running on z/VM? > > On Wed, Aug 12, 2009 at 7:22 PM, Schuh, > Richard<rsc...@visa.com> wrote: > > Strong incentive to make sure that either all of the linux > guests IPL > > from the same virtual address or, at the very least, that > none of them > > has a virtual 190. > > > > As long as you are using something fuzzy to make the determination, > > you can also see the virtual storage in the response to IND > USER. CMS > > guests are usually measured in MB, not GB. > > This is a really interesting thread. As Richard notes, all > these methods are "fuzzy", but all are useful; a combination > should be pretty definitive. > > One more approach: set something distinctive for each guest > -- a printer at address FFFF, a specific accounting code, > etc. -- and use that (subject to other site restrictions, of > course). Or do the same for non-Linux guests and divine by > elimination... >
