Re: Feuding with IBM over HMC console disconnects -- MIDRANGE-L

Subject: Re: Feuding with IBM over HMC console disconnects
From: Kevin Monceaux <Kevin@xxxxxxxxxxxxxx>
Date: Wed, 15 May 2019 12:37:48 -0500
List-archive: <https://archive.midrange.com/midrange-l/>
List-help: <mailto:midrange-l-request@lists.midrange.com?subject=help>
List-id: Midrange Systems Technical Discussion <midrange-l.lists.midrange.com>
List-post: <mailto:midrange-l@lists.midrange.com>
List-subscribe: <https://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@lists.midrange.com?subject=subscribe>
List-unsubscribe: <https://lists.midrange.com/mailman/options/midrange-l>, <mailto:midrange-l-request@lists.midrange.com?subject=unsubscribe>

On Wed, May 15, 2019 at 05:15:01PM +0000, Rob Berendt wrote:

Console takeover does work quite well.
In addition to having a QSECOFR in SST I also have my account in SST.

We've been using it for a while where I work also. Our consoles are always
left signed on to a profile that starts the BRMS console monitor on each
console. I have SST users on each LPAR with user names and passwords that
match our BRMS console monitor profiles, so that it's easy for our operators
to remember.

As an Amazon Associate we earn from qualifying purchases.

Follow-Ups:

Re: Feuding with IBM over HMC console disconnects , Jim Oberholtzer
RE: Feuding with IBM over HMC console disconnects , Rob Berendt

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.