Hello, all. A Christmas present in two parts....
1) A ZVMUSERS NAMES file that contains information on the basic components that make up z/VM and the user ids and their minidisks that are used to install, service and test those components. 2) The ZVMNAMES EXEC (and supporting COMPxxxx EXEC files); a simple exec to make queries against the ZVMUSERS NAMES file, and to present those results in a full screen, easy to navigate, format. See the comments in the exec and names files for more information. Download the vmarc file from here: http://www.vsoft-software.com/zvmnames.vmarc The exec uses the VM/SES-E SERIVICE command so it needs access to the VM/SES-E mdisks. Happy Holidays to everyone, too. DJ On 11/25/2014 03:33 PM, Scott Rohling wrote: > Just a note that we also use NAMES files internally to manage zLinux > guests.. Everything from NICs, hostnames, guest names, descriptions, > network info, etc are listed there. Automation helps manage changing > info (release levels, for example) in the names files to keep certain > things current without manual effort. > > We use the files for both an inventory (easily pull reports about > guests) and for the Linux startup. The common PROFILE EXEC used by all > guests uses NAMEFIND to determine things about startup (defining nics, > for example) and this allows us to make individual or global changes to > startup fairly easily. We used to base shutdown automation on it, > before SIGNAL was supported. We have lots of little tools based on > NAMES files as well - for things like pinging them or doing checks on > certain things. > > My preference is one large file.. and use 'viewing' tools to keep it > manageable. Others have broken NAMES files into things like one for > each z/VM system, but I prefer one large one.. Either that or the > tools contain the smarts to know which to use. > > Scott Rohling > > On Tue, Nov 25, 2014 at 1:15 PM, Dave Jones <[email protected] > <mailto:[email protected]>> wrote: > > These are good ideas, all. It does make sense to have all of this > information kept together inside just one NAMES file. Does anyone have > any strong feelings about how to merger these two files? > > DJ > > On 11/25/2014 03:07 PM, Kris Buelens wrote: > > Yes Alan, that's what I was about to suggest. :nicktype. is what > I used in > > the past. > > It would also be useful to allow synonyms (for components), so one > could > > search for PTK or PERFKIT, and CP or HCP, etc. > > > > In my former life I had a DISTRIB NAMES file to describe all VM > systems we > > had. Here the entry for our test system and 4 synonyms for it. > > :nick.BRU :nicktype.SYSTEM > > :node.VMKBBR01 :suba.72 :name.VMTEST :naam.Test System > > :VmStates.15 Swim > > :hostname.VMTEST > > :ipaddr.192.168.9.4 :vipa.192.168.9.4 > > :ipaddr1.10.68.12.201 :ipaddr2.10.68.13.201 > > :nick.TEST :nicktype.SYSTEM :synonym.VMKBBR01 > > :nick.SWIM :nicktype.SYSTEM :synonym.VMKBBR01 > > :nick.VMCCB :nicktype.SYSTEM :synonym.VMKBBR01 > > :nick.VMTEST :nicktype.SYSTEM :synonym.VMKBBR01 > > Our FINDNODE EXEC could get as argument a nodeid (VMKBBR01), a > nick (BRU) > > or a synonym (TEST, SWIM, ...) > > > > Search is easy, basically: > > 'NAMEFIND :nick' compname ':nicktype SYSTEM :synonym ....(FILE > XXX ...' > > parse pull .... or analyze STEM > > if Synonym<>"" then > > 'NAMEFIND :nick' synonym ':nicktype SYSTEM ....(FILE XXX ...' > > > > > > > > > > Kris Buelens, > > --- freelance z/VM consultant, Belgium --- > > > ----------------------------------------------------------------------- > > > > 2014-11-25 21:28 GMT+01:00 Alan Altmark <[email protected] > <mailto:[email protected]>>: > > > >> On Tuesday, 11/25/2014 at 03:18 EST, Michael MacIsaac > >> <[email protected] <mailto:[email protected]>> wrote: > >>> Bummer, four component names that collide with virtual machine > names :(( > >>> > >>> Kludgy no doubt, but I renamed the four component names to end > in 'CMP' > >> and > >>> added an extra test to the wrapper: > >> > >> You're trying too hard. Just add another tag to distinguish > component > >> names. E.g. :Entry_type.COMPONENT or :Entry_type.USERID (maybe > default > >> is :Entry_type.USERID ?) > >> > >> Alan Altmark > >> > >> Senior Managing z/VM and Linux Consultant > >> Lab Services System z Delivery Practice > >> IBM Systems & Technology Group > >> ibm.com/systems/services/labservices > <http://ibm.com/systems/services/labservices> > >> office: 607.429.3323 > >> mobile; 607.321.7556 > >> [email protected] <mailto:[email protected]> > >> IBM Endicott > >> > > > > -- > Dave Jones > V/Soft Software > www.vsoft-software.com <http://www.vsoft-software.com> > Houston, TX > 281.578.7544 > > -- Dave Jones V/Soft Software www.vsoft-software.com Houston, TX 281.578.7544 ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 ---------------------------------------------------------------------- For more information on Linux on System z, visit http://wiki.linuxvm.org/
