Yet another strategy is to create a service machine that collects the logs and archives them to disk. Spool the other service machines' consoles to it. With ours, the consoles may be closed as many times as you wish. It appends each arriving reader file to a file having the originating userid as the file name and the date as the file type. Each day, it closes all of the consoles at midnight and starts a fresh set of logs. Logs are retained according to tables we maintain. Some are allowed to default to 7 day retention while others are kept for as long as 6 months.
Regards, Richard Schuh > -----Original Message----- > From: The IBM z/VM Operating System > [mailto:[email protected]] On Behalf Of Tracy Dean > Sent: Monday, March 30, 2009 12:28 PM > To: [email protected] > Subject: Re: look at service machine cons log > > IBM Operations Manager for z/VM also allows you to look at > live streaming= > > copies of one userid's console, a group of consoles, or all > consoles. Th= is includes the ability to scroll and see > historical information as well as = a command line to enter > commands back to that userid's console. > > Operations Manager is a priced product, based on the number > of IFLs you = > > have. > > Tracy Dean > IBM > > On Mon, 30 Mar 2009 15:00:49 -0400, [email protected] wrote: > > >Hello, how do I get a look at a service machine's cons log? I am > >running several service machines and would like to see the cons log > >without logging onto them each individually to see them. > Can this be > >done with operators con log? > >Best Regards, Joe. >
