×
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.
Conrad,
That is the expected behavior if the system is configured to have some other "console" e.g. an async. Operations Console, as was possible with a model 300 ... from around that timeframe.
That would explain why you never see anything on the twinax console, even though it is port 0 address 0, until after the IPL completes, and then a normal sign-on screen shows up, but for DSP16.
Also, system value QLMTSECOFR may be set to the default of "1" so QSECOFR would need to have explicit authority granted to the device description DSP16, to be able to sign-on to that device. This may explain why even after you reset the QSECOFR password with DST, you still cannot sign on.
I think you will need to "do the 65+21 dance" to reset the system to use a Twinax console device. Once you do that, I think things will begin to behave more "as expected."
Hope that helps,
Mark S. Waterbury
On Tuesday, March 24, 2020, 4:02:59 PM EDT, Conrad Kostecki <ck+midrangel@xxxxxxxxxxx> wrote:
Hi Patrik,
Patrik Schindler <poc@xxxxxxxxxx> hat am 24. März 2020 20:33 geschrieben:
Q1: Did you see any IPL status messages from IPL on the screen before the signon display appeared?
I am not sure, there were a lot of codes, which were shown? Or what do you specific mean?
just a quick note. Booting in normal IPL mode does not show any SRC which stays forever, when IPL is finished. It returns to "01 B", when my login screen appears on the terminal.
Cheers
Conrad
midrange.com
