|
On Apr 6, 2024, at 10:35 AM, Brad Stone <bvstone@xxxxxxxxx> wrote:
So you're saying do F18 from that screen?
On Sat, Apr 6, 2024 at 10:29 AM Jim Oberholtzer <midrangel@xxxxxxxxxxxxxxxxx>--
wrote:
In your case I would turn it back on.
Jim Oberholtzer
Agile Technology Architects
(thatOn Apr 6, 2024, at 10:22 AM, Brad Stone <bvstone@xxxxxxxxx> wrote:
I was able to open another LAN console without issue. Logs say PTFs
applied, etc.. don't see any errors.
But when I did log into the new LAN console the message at the bottom
said Service Tools User ID does not exist) changed to:screen:
Console recovery / take over is currently turned off.
On Sat, Apr 6, 2024 at 10:09 AM Brad Stone <bvstone@xxxxxxxxx> wrote:
I was applying PTFs and IPLing and my LAN console ended up on this
fine.
Console Information Status
System:
Sxxxxxxx
Date and time for previous signon . . :
Previous action taken date and time . :
Take over the console . . . . : NO
Current console user ID . . . :
Current console type . . . . : 3
Current terminal type . . . . :
Client internet address . . . :
Server internet address . . . :
Server resource name . . . . : CMN03
Server adapter type . . . . : 576F
Server adapter model . . . . : 001
Server adapter serial number. : YL50205BY0Z7
Location . . . . . . . . . : U78C9.001.WZS0JX0-P1-C10-T1
F18=Take console. Device power down/up will occur.
Service Tool User ID does not exist.
Normally I'm used to seeing it go through applying PTFs, etc. Now it's
just sitting here on this screen and everything seems to be working
listThe message on the bottom is odd... Service Tool User ID does not exist?--
Any ideas what happened here? Should I just close the session or
something else?
Bradley V. Stone
www.bvstools.com
Native IBM i e-Mail solutions for Microsoft Office 365, Gmail, or any
Cloud Provider!
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxxrelated questions.
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.
Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.
Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related
questions.
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.
Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related questions.
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.