HMC 5250 Console Errors

The initial screens presented on the HMC 5250 console sign-on involve communications with the HMC 5250 console proxy. During that time, two sets of error codes may display on the error line (bottom line) of the screen. The first set consists of standard Operator Error Codes. These are 4-digit 5250 device errors such as 0005 and 0024. No secondary text is displayed with them.

The second set of errors is generated from HMC. The format is xxxx <msg> where xxxx is a 4-digit number whose range overlaps with the device errors. <msg> is a description of the error. The existence of the message text is what distinguishes between an Operator Error Code and HMC Proxy Error Code.

Operator Error Codes



These errors can be found in manuals such as the 5494 User's Guide at the following website:

http://publib.boulder.ibm.com/cgi-bin/bookmgr/BOOKS/CO2A2002/10.4?DT=19961015143739

A few common examples are as follows:

0005 Cause: Cursor in protected area of display.
You have tried to enter data. However, the cursor is not in an input field on the display. Data cannot be entered in a protected area of the display.
Customer Action: Press Error Reset, and move the cursor to a valid input field.

0024 Cause: Decimal field; entry not valid.
You pressed a key that is not valid. Only characters 0 through 9 and Dup (if specified in the field format word) are allowed in this field.
Customer Action: Press Error Reset, and continue by entering digits in this field.

Note: On some HMCs, the right Ctrl key may not be mapped to the error reset key. To send a error reset keystroke, select the Control menu for the emulation window. Then, select the Reset key option.


HMC Proxy Error Codes



Some of the common messages are listed below. The Reason column explains when each message might be displayed.

 

Message ID	Message Text	Reason
0001	"Key not valid"	Invalid AID key pressed. This is usually caused by an unsupported emulator or attempting to use a pass-through session (for example, telnet to an i5 partition, then telnet from the i5 partition to the HMC).
0002	"Option not valid"	Invalid option number entered.
0003	"Userid or password not valid"	Authentication failed.
0004	"Option entered in multiple fields"	Option entered in more than one field when only one permitted on current screen. When selecting an action to perform on a partition, there is a field to enter the option next to each partition -- only one partition may be acted on.
0005	"Session key not valid"	The session key (like a password) is incorrect.
0006	"Session keys do not match"	Session keys did not match (when creating a new session key, it must be typed twice and these are compared to ensure they match).
0007	"Session already in use by dedicated console"	Attempt to connect to a partition which already has a dedicated session.
0008	"Session already in use"	Attempt to establish a dedicated connection to a partition which already has an active session.
0009	"Not authorized to perform action"	Not authorized to perform the requested action (such as disconnect session).
0010	"Communication error. Try again"	The most common cause is attempting to connect to an existing shared console session when the current session is input inhibited. If the shared session that is input inhibited is either the IBM i access for Linux emulator or some service packs of IBM i access for Windows, this error results, disconnecting all shared sessions.
0011	"Session ended due to management console signon failure"	User did not sign on to hmc with valid user id/pw
0012	"Session key must contain six or more characters"	Session key invalid (length).
0013	"Session key cannot contain repeating characters"	Session key invalid (duplicate characters).
0014	"Session key must contain one or more numeric digits"	Session key invalid (no numeric digits).
0015	"Session key must contain one or more alphabetic characters"	Session key invalid (no alpha characters).
0020	"Unknown HMC internal error - contact service"	The 0020 will occur if the managed system connection is not in a connected state or the console is unable to query the partitions. To check for connection status open a restricted command shell and run the following commands: lssysconn -r all; lssyscfg -r sys -F name,state; lssyscfg -m <M-T*S> -r lpar -F name,lpar_id,state . Check for any errors or duplicate connection entries for the server. Other causes: - 0020 can occur intermittently if the HMC is "rebuilding" the managed system. A rebuild takes place if a user issues a rebuild-managed system, immediately after a restart of the HMC and after a reset connection on the managed system. Check or correct the connection state, wait 2 or 3 minutes for the rebuild to complete, and then try again. - Trailing spaces or special characters in the server or partition(s) name. Trailing spaces can be difficult to detect - neither the HMC GUI nor the command line will show the trailing spaces. To resolve, click partition properties. The properties panel will automatically trim the trailing spaces, just click OK to save the changes. Repeat for each partition.
0022	"Unknown HMC internal error 0022 - 5250 lost contact"	One cause is attempting to open an IBM ACS console session directly to a partition but specifying an incorrect or invalid partition id. In the ACS configuration, ensure the partition is correct and an IBM i partition. One possible cause is the user profile used to log on to the HMC does not have sufficient privilege to start a 5250 session. For task role requirements to start a 5250 session refer to Creating a Customized Task Role to Allow V7 HMC 5250 Remote Console
0023	"No information retrieved - verify configuration"	One possible cause is duplicate managed system entries for the same system. For further information, refer to 0023 on HMC Console
0024	"Request timeout"	One possible cause is network switch inactivity/idle timer ending the tcp/ip session on port 30001. This is typically only seen when the HMC-server connection is over a wide area network. To recover: wait for all open attempts to timeout; issue a reset connection; wait for HMC to reconnect; then open the console.
0025	"Authentication failure"	The requested operation was rejected because of invalid authentication information.
0030	"Connection refused - partition not configured for HMC console"	The partition's console type is not set correctly to allow this type of connection. If a profile was created using Version 7.3.3, without required efix MH01102 or later applied, the console tag is incorrectly set to slot 0. The recovery is to upgrade/apply a service pack, edit the profile and change the console type to another value (does not have to be valid), save the profile, then edit the profile again and set the value to HMC. Note that just upgrading the HMC does not repair any profiles with the incorrect setting.
0031	"Connection refused - partition failed when accepting connection"	This is due to a software error on the partition. The usual cause is an error creating or varying on the controller. Check if there is a conflict caused by restoring an older device configuration such as one from a partition with a twinax console.
0040	"Connecting to"	A connection is being attempted to the named target.
0041	"Connecting"	A connection is being attempted. This is a normal status message when the partition is powering on or off. If the partition status is "Running" with reference code 00000000 then verify the console type is set to HMC console and that the i5 version and PTF level supports HMC console. Firmware 240_415 was removed from fix central after confirmation that it causes intermittent 0041's. To resolve the error either remove 240_415 or apply a newer level. If the problem persists on only one partition, an IPL of the partition may be needed to recover. Verify the partition has the console recommended fixes (or latest cumulative PTF). If the problem occurs on all partitions then a circumvention may be to use a redundant HMC that manages the same server. The console connections on the failing HMC can sometimes be recovered by resetting the FSP/HMC connection using one of the following methods: o Restart the HMC or issue reset connection. o Remove the connection (remove not reset), wait 5 minutes, add the connection back (this requires the HMC access password). Ensure server firmware is up to date.
0042	"Connected - waiting for screen data from "	A connection has been established and data is expected to be received from the named target.
0043	"Connected - waiting for screen data"	A connection has been established and data has not yet been received for displaying on the screen. If 0043 is displayed for an extended period of time, verify the console device is not varied off, failed, or deleted. To vary on the device perform one of the following. If tcp/ip is not active and no twinax devices are available: - IPL If telnet is active or a twinax device is available: - Run the command DSPSYSVAL QCONSOLE to view the console device. - Run WRKCFGSTS *DEV dsp01 (where dsp01 is the actual device description returned by QCONSOLE system value). - Vary on the device. If IBM i Access is available and host servers are running: - Use RMTCMD. From the PC command prompt issue the command: rmtcmd //system_name "vrycfg cfgobj(dsp01) cfgtype(*dev) status(*on)" Where system_name = the hostname of the partition and "dsp01" is the device name of the console. If FTP is active: - FTP <system name> where <system name> is the hostname or ip address of the partition. - log in - Run the ftp command: quote rcmd "vrycfg cfgobj(dsp01) cfgtype(*dev) status(*on)" where "dsp01" is the device name of the console.
0044	"Connection lost - reconnecting to"	The existing connection dropped - a new connection is being attempted to the named target.
0045	"Connection lost - reconnecting"	The existing connection dropped - a new connection is being attempted.
0050	"System not available"	The requested system is not in a state in which it may be queried for partition information. For further information see IBM Knowledge Center "Correcting a connection problem": http://www-01.ibm.com/support/knowledgecenter/8247-22L/p8ha1/correctingthemanagedsystemoperatingstate.htm?lang=en
00FF	"Unknown HMC internal error - contact service"	The following problems have been linked to this return code: o Attempting to start a console session, shared or dedicated from a redundant HMC when a console session for the partition already exists on other HMC. (i.e. two console sessions to the same partition cannot be started from the same HMC or redundant HMC). o Error connecting to port 30001. - Firewall: If the HMC-FSP connection is on an open network, the network must allow connections on port 30001. - Incorrect access password: This can occur if the HMC access password was changed from another interface (ASMI or dual HMC) but not updated on the HMC. Restart the HMC or reset connection to confirm the connection state changes to failed authentication. Enter the correct password. o Partition issues If the problem impacts only one partition on the server it is likely a problem with the console code on the partition. - Partition IPL: This reference code may appear intermittently if the console is opened during certain steps of a partition IPL. To recover, close the console and re-open. - Old IBM i PTF levels: See IBM i Group PTFs with level o HMC issues If the problem impacts all partitions or all partitions on one server it may indicate a problem on the HMC such as an out of memory issue. - Restart the HMC and verify the server status returns to operating. Retry the connection. - Check for HMC serviceable events such as E3xxxxxx. o Server Firmware issues If the problem impacts all or one partition on one server, it can indicated a failure in the FSP virtual serial interface. - A FSP IPL (AC power cycle/pinhole reset of the server or server firmware update) will reset the interface. Note that all but a concurrent code update are disruptive resulting in a full server IPL. - Collect FSPDUMP and contact hardware support for further debug.