Table of Contents
Advertisement
A6nn 500C
|
|
You executed a second 21 to cause an action, such as setting the console to another value.
|
A6nn 500D
You waited too long after entering edit mode to cause an action so you will have to enter edit
|
mode again if you intended to make a change. A 21 at this time will force the console to DST, not
|
|
cause an action.
If you do not want to make a change after entering edit mode you can wait 3 minutes and this
|
|
completion code should show up indicating a change is no longer pending or you do a function 66 to
cancel any pending changes and exit edit mode.
|
|
Note: You have 45 seconds between a 65 and the 21 to start display mode or edit mode changes. If the
time between these codes exceeds this limit the 21 will become a "force DST console" request.
|
|
An example would be:
|
The console type is 01 (twinaxial) and you want to use LAN (03).
65 - 21 = A601 500A You are in display mode and the console mode is 01
|
|
65 - 21 = A602 500B You entered edit mode and incremented the counter
65 - 21 = A603 500B You incremented the counter again
|
21 = A603 500C You invoked the action (set the console mode to 03)
|
If the LAN adapter already had a valid configuration, for example you previously configured the LAN
|
adapter for use with the service tool server, then you would be ready to create a local console on a
|
|
network configuration on the client, if one didn't already exist. You could then power off the twinaxial
device and connect the Operations Console LAN configuration.
|
|
Note: To reset the console without changing the console mode value you can do a 65 - 21 - 21. The server
should respond with A6nn500A after the first 21 and a A6nn500C after the second 21. This will
|
cause the connection to the console to be dropped during the reset process. It is recommended that
|
|
this function not be used when you already have a working console. This function will not correct
all errors associated with a console failure, but rather resets the hardware associated with the
|
configured console connection.
|
Using the OPSCONSOLE native macro
|
Native macros are advanced debug and analysis tools resident on the server. These tools are intended to
|
|
be used only with the direction of support personnel since inappropriate use of these tools can cause
unpredictable problems with your system. If you are not comfortable in the service tools area you should
|
call your service provider for assistance before using these tools. These instructions assume you do not
|
|
have a console device but do have another workstation capable of using the System Service Tools (SST).
Note: Improper use of native macros could result in a change requiring a complete system reload. It is
|
|
strongly suggested that you use these native macros only at the request of a support representative
To use the Operations Console native macro support, follow these steps:
|
|
1. Access System Service Tools (SST).
|
2. Select Start a service tool.
3. Select Display/Alter/Dump.
|
4. Select Display/Alter storage.
|
5. Select Licensed Internal Code (LIC) data.
|
|
6. Select Advanced analysis. (You will have to page down to see this option.)
91
Operations Console
Advertisement
Table of Contents
