|
It doesn't seem to matter if I launch the shared key from the HMC and
take it over remotely, or if I start the shared session remotely, or if
I simply start the shared key from the HMC and do nothing else. All
three scenarios time out.
-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Jack Kingsley
Sent: Wednesday, April 13, 2011 11:08 AM
To: Midrange Systems Technical Discussion
Subject: Re: New to HMC- having timeout issue
if you launch the shared key from the HMC and then take it over remotely
how does it react, would be curious to know or are you doing it this way
currently.
On Wed, Apr 13, 2011 at 11:01 AM, Smith, Mike
<Mike_Smith@xxxxxxxxxxxxxxxx>wrote:
Yes.
-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Jack Kingsley
Sent: Wednesday, April 13, 2011 10:58 AM
To: Midrange Systems Technical Discussion
Subject: Re: New to HMC- having timeout issue
you running shared key??
On Wed, Apr 13, 2011 at 10:34 AM, Smith, Mike
<Mike_Smith@xxxxxxxxxxxxxxxx>wrote:
Hi Chris,
I took your advise on this issue, but it seems to be timing out on
the
physical HMC.
I went to the Physical HMC. Logged on using a shared session.
I came back to my desk and opened a shared session
Checked it a couple of hours later and I'm back to a signon screen.
I'm wondering if this is happening because of the QINACTITV system
value?
-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Chris Bipes
Sent: Wednesday, March 30, 2011 10:36 AM
To: Midrange Systems Technical Discussion
Subject: RE: New to HMC- having timeout issue
One way would be to have someone log on to the HMC locally. Have
them
open shared Console session. Then you connect remotely using a
Shared
session and the password they setup for you locally. Then if yourplace.
session times out due to inactivity or communications failure, the
console is still connected. You can reconnect and be at the same
However this means your remote HMC is logged on all the time and the
shared console is available at the remote location as well as your
local session. They share and see the same screens. I do this as
our
HMC is in a secure location, in the same rack as our iSeries. When
all else fails, I can use the remote KVM to open the HMC as if I was
Console.at its keyboard.
--
Chris Bipes
Director of Information Services
CrossCheck, Inc.
-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Smith, Mike
Sent: Wednesday, March 30, 2011 6:10 AM
To: Midrange Systems Technical Discussion
Subject: New to HMC- having timeout issue
We just upgraded to a Power 7 box a week ago, so this is our first
exposure to using a HMC. Previously we had a twinax attached
We are running V7R7.2.0.1 of HMC. The HMC is located offsite.
Now the problem I'm having is that I create a 5250 session to the
console, but it will timeout after about 90 minutes with the
following
messages.
CPF5140 Session stopped by a request from device DSP01.
CPF2677 Device DSP01 no longer communicating
This is not terrible except that we use a custom System Save. The
system save is started on DSP01 and waits until a message is sent
from
the job scheduler to start the save. We can't get this to work nowout?
because of the timeout. How can I prevent the Console from timing
I guess as a side question, Is it still a requirement that the
system
save run from a Console?
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L)
mailing
list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe,http://archive.midrange.com/midrange-l.
unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please
take a moment to review the archives at
NOTICE: This message, including any attachment, is intended as a
confidential and privileged communication. If you have received this
message in error, or are not the named recipient(s), please--
immediately notify the sender and delete this message.
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L)
mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To
subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please
take a moment to review the archives at
http://archive.midrange.com/midrange-l.
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe,http://archive.midrange.com/midrange-l.
unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take
a moment to review the archives at
NOTICE: This message, including any attachment, is intended as a
confidential and privileged communication. If you have received this
message in error, or are not the named recipient(s), please
immediately notify the sender and delete this message.
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe,--
unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take
a moment to review the archives at
http://archive.midrange.com/midrange-l.
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe,
unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a
moment to review the archives at http://archive.midrange.com/midrange-l.
NOTICE: This message, including any attachment, is intended as a
confidential and privileged communication. If you have received this message
in error, or are not the named recipient(s), please immediately notify the
sender and delete this message.
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.
As an Amazon Associate we earn from qualifying purchases.
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.