× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



Yep, IBM thought of that problem.

That's why I insist that all my customers start a console session on the
physical HMC for each partition and just leave it without signing on. That
way when you use a remote connection the local HMC connection is also
started and remains in place in the event of a remote communications failure
to the HMC.

--
Jim Oberholtzer
Chief Technical Architect
Agile Technology Architects


-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Jim
Franz
Sent: Monday, September 29, 2014 9:35 AM
To: Midrange Systems Technical Discussion
Subject: SAVE 21 remote hmc and pc energy saver

Our admin ran a save21 from his laptap remoted into hmc.
All was running well till laptop energy saver blacked out the display.
Was an hour into it.
He went to HMC and had blank screen for console.

Used web access of tape library to monitor activity.
Save 21 kept running, and tape drive was set to autoload. Not using BRMS.
V7r1
It kept running (3 more hours, including load of 2nd tape) and completed the
save 21 In previous releases I've seen this fail. The CPF5080 has "ignore"
thoughout log.



CPF5140 Diagnostic 70 09/28/14 18:17:56.041199
QWSERROR QSYS 0630 QWSUIEH
Message . . . . : Session stopped by
a request from device DSP01.


CPF5503 Diagnostic 30 09/28/14 18:17:56.041241
QWSERROR QSYS 0652 QWSUIEH
Message . . . . : Input or Output
request failed. See message CPF5140.


CPF5080 Notify 30 09/28/14 18:18:06.437840
QWSDSMSG QSYS 0546 QMHSNSTA Q
Message . . . . : Display status
message request failed. See message


CPF5263.
Cause . . . . . : Various error
conditions detected. Recovery . . . :
Close the active file, if any, and
see the message CPF5263 for corrective
action. Correct the errors and then
try the request again. Possible choices
for replying to message . . . . . .
. . . . . . . . . : I -- Ignore the

request.
*NONE Reply 09/28/14 18:18:06.437844
QMHSNINQ QSYS 0F84 QMHSNSTA Q
Message . . . . : I



Jim Franz
--
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 thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.