I was of the opinion that shared consoles work best if they are first started on the vHMC but I'm starting to question even that. "IF" you have "console takeover" configured on your IBM i it may not matter then.
https://www.ibm.com/docs/en/i/7.4?topic=connection-enabling-console-takeover
At least one person on this list doesn't like it because "operators" using the system console to do saves get prompted for a SST user who has console takeover capability.
I can understand where they are coming from but I figure it's not hard to train some monkey to enter in a SST user id and password also. You could even create some special SST user who only has console takeover capability.
Having a console drop connection when working remote during a long save or RCLSTG is no longer frustrating when you have console takeover enabled. Before this capability one would have to ensure that you went to the HMC and started the shared console first. Then you could use a remote connection and if the your session dropped it was no big sweat. I still remember Larry helping me at a mini COMMON in Dallas when I was trying to initialize disks remotely and kept dropping the session. Finally talked the operator into starting the shared console on the hmc directly. We were pretty new to HMC and she wasn't one for new stuff.
Rob Berendt
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.