MKMSGF LT2G ¡ ░ │ ╢ ╣ ╝ ┐ ┬ ┼ ╚ ╦ ╬ ╤ ╘ ╫ ┌ ▌ α π µ Θ ∞ ∩ ╓┘z`yKNS ╢ ╣ p f ìvû|*Θ∞╫▄< ∞ ╡#╕#╗#╛#┴#─#⌠%%(((Ç)U,.σ0⌠1)4 555è6▓7╡7╕7╗7╛7┴7? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ICause: This is a generic initialization failure message. If the IBMTOK.OS2 device driver encounters any errors during initialization, the specific message related to the error will accompany this generic message. Action: Resolve the specific error message that accompanies this message. In addition, ensure that the Protocol Manager device driver, PROTMAN.OS2, is located in the \IBMCOM directory, and that a DEVICE statement for PROTMAN.OS2 exists in the CONFIG.SYS file. ? ICause: The value provided for the parameter is not the correct type or is not a valid value. Action: Change the value for the parameter in PROTOCOL.INI. ICause: Conflicting parameter values were found while processing the IBM Token-Ring Network Driver section of PROTOCOL.INI. Action: Examine the configuration parameters and correct the conflicting values in PROTOCOL.INI. ICause: One of the following conditions has caused this error. - The logical primary/alternate setting in the PROTOCOL.INI file does not map to the physical primary/alternate setting. - The adapter is not responding to a request to start. - There is no physical adapter in this machine. Action: If there is already an adapter in this system, check the logical primary/alternate setting. Check the cable and ensure that the connection to the token-ring network addressable unit (NAU) is functioning properly. Then run the hardware diagnostics for the token-ring adapter to ensure that the adapter and options are correctly installed. If there is no adapter in this machine, install a token-ring adapter or remove the device driver statement from the CONFIG.SYS file. ICause: An unexpected error occurred when the program attempted to open the protocol manager. Action: Check the drive and directory to ensure that the protocol manager is located in the specified path. ? ICause: The IBM Token-Ring Network adapter encountered a wire fault. Action: 1. Check and secure all cable connections between your adapter and the Multistation Access Unit (MSAU). Correct any related problems and try the operation again. 2. If there are no related problems, refer to the documentation that was shipped with your adapter to run adapter diagnostics; then try the operation again. 3. If the problem persists, print or save the LANTRAN.LOG file and contact your service coordinator. ICause: The requested DIR.OPEN.ADAPTER parameter has not allowed enough receive buffer space in the adapter shared RAM area. Action: Reduce the RAM requirements by reconfiguring the parameters in PROTOCOL.INI. The parameters that will reduce the space requirements for the receive buffer are the transmit buffers (if more than 1 is specified). ? ICause: The node address defined is not valid. Action: Specify a valid node address. Refer to the IBM Token-Ring network architecture reference for node address restrictions. ICause: The receive buffer length defined in PROTOCOL.INI is not valid. The value specified must be greater than the allowable minimum, less than the allowable maximum, and a multiple of 8. Action: Specify a valid receive buffer length. ICause: The adapter transmit buffer length defined in PROTOCOL.INI is not valid. The value specified must be greater than the allowable minimum, less than the allowable maximum, and a multiple of 8. Also, the IBM Token-Ring Network adapter may have switched from 16 Mbps to 4 Mbps, causing the transmit buffer length specified to exceed the maximum. Action: Specify a valid adapter transmit buffer length. If it is suspected that the IBM Token-Ring Network adapter switched to 4 Mbps, restart the computer to reset the protocol drivers. ICause: You are attempting to load more than two Token-Ring Shared Ram device drivers. Action: Use the "Configure LAN transports" utility in LAPS to configure a maximum of two "IBM Token-Ring Network Adapters" or "Token-Ring Network Adapters" in any combination. Also, verify that you are attempting to load no more than two instances of any combination of IBMTOK.OS2 or TOK.OS2 in your CONFIG.SYS file. ICause: While attempting to open a new Token-Ring adapter using the autosense configuration option, it was determined that the adapter was the only station on the ring. The adapter will not be allowed to open in order to prevent possible network disruptions. User Action: Restart the application at a later time, when at least one other station is on the ring. As an alternative, reconfigure the adapter for manual mode, specifying the correct speed of the Token-Ring to which the adapter is connected, then restart the computer. ICause: The adapter was closed because of an unexpected error condition. Action: See the message log, LANTRAN.LOG, for additional information about this error. The error must be corrected before you can use this adapter. ICause: The IBM Token-Ring Network adapter has either detected a monitor contention failure or received a beacon frame from the ring. The problem may be that your adapter speed is different from the speed at which the LAN is running. Action: 1. Check and secure all cable connections between your adapter and the Multistation Access Unit (MSAU). Correct any related problems and try the operation again. 2. If there are no related problems, refer to the documentation that was shipped with your adapter to run adapter diagnostics; then try the operation again. 3. If the problem persists, print or save the LANTRAN.LOG file and contact your service coordinator. ICause: A command forcing the adapter to remove itself from the ring was received. Action: Contact your LAN personnel to determine why the REMOVE command was issued for your machine. ? ICause: The IBM Token-Ring Network adapter has detected a problem on your local lobe between the adapter and the Multistation Access Unit (MSAU). Action: 1. Check and secure all cable connections between your adapter and the Multistation Access Unit (MSAU). Correct any related problems and try the operation again. 2. If there are no related problems, refer to the documentation that was shipped with your adapter to run adapter diagnostics; then try the operation again. ICause: The IBM Token-Ring Network adapter has detected one of the following open errors while trying to insert into the LAN: - Ring Failure - Ring beaconing - Timeout Action: 1. Check and secure all cable connections between your adapter and the Multistation Access Unit (MSAU). Correct any related problems and try the operation again. 2. If there are no related problems, refer to the documentation that was shipped with your adapter to run adapter diagnostics; then try the operation again. ICause: The IBM Token-Ring Network adapter has detected one of the following open errors during the address verification phase of the adapter open process: - Signal loss - Timeout - Ring failure - Ring beaconing - Duplicate node - REMOVE command received Action: 1. Check and secure all cable connections between your adapter and the Multistation Access Unit (MSAU). Correct any related problems and try the operation again. 2. If there are no related problems, refer to the documentation that was shipped with your adapter to run adapter diagnostics; then try the operation again. ICause: The IBM Token-Ring Network adapter has detected one of the following open errors during the roll call poll phase of the adapter open process: - Signal loss - Timeout - Ring failure - Ring beaconing - REMOVE command received Action: 1. Check and secure all cable connections between your adapter and the Multistation Access Unit (MSAU). Correct any related problems and try the operation again. 2. If there are no related problems, refer to the documentation that was shipped with your adapter to run adapter diagnostics; then try the operation again. 3. If the problem persists, print or save the LANTRAN.LOG file and contact your system coordinator. ICause: The IBM Token-Ring Network adapter has detected one of the following open errors during the request parameter phase of the adapter open process: - Signal loss - Timeout - Ring failure - Ring beaconing - Parameter request - REMOVE command received Action: 1. Check and secure all cable connections between your adapter and the Multistation Access Unit (MSAU). Correct any related problems and try the operation again. 2. If there are no related problems, refer to the documentation that was shipped with your adapter to run adapter diagnostics; then try the operation again. 3. If the problem persists, print or save the LANTRAN.LOG file and contact your service coordinator. ? ? ? ? ? ICause: The IBM Token-Ring Network adapter has detected a lobe media failure while trying to open the adapter. Action: 1. Check and secure all cable connections between your adapter and the Multistation Access Unit (MSAU). Correct any related problems and try the operation again. 2. If there are no related problems, refer to the documentation that was shipped with your adapter to run adapter diagnostics; then try the operation again. 3. If the problem persists, print or save the LANTRAN.LOG file and contact your service coordinator. ICause: The IBM Token-Ring Network adapter has detected a signal loss failure while trying to open the adapter. Action: 1. Check and secure all cable connections between your adapter and the Multistation Access Unit (MSAU). Correct any related problems and try the operation again. 2. If there are no related problems, refer to the documentation that was shipped with your adapter to run adapter diagnostics; then try the operation again. 3. If the problem persists, print or save the LANTRAN.LOG file and contact your service coordinator. ? ICause: The IBM Token-Ring Network adapter has detected that the ring is operating at a speed other than the speed at which it was inserting. Action: Make sure the IBM Token-Ring Network adapter and the ring are set for the same speed. If the problem persists, print or save the LANTRAN.LOG file and contact your service coordinator. ICause: The IBM Token-Ring Network adapter has detected an insertion timer expiration while trying to open the adapter. This condition indicates that the ring may be congested, experiencing a high bit-error rate, or is losing an unusually high number of tokens or frames. Action: 1. Check and secure all cable connections between your adapter and the Multistation Access Unit (MSAU). Correct any related problems and try the operation again. 2. If there are no related problems, refer to the documentation that was shipped with your adapter to run adapter diagnostics; then try the operation again. 3. If the problem persists, print or save the LANTRAN.LOG file and contact your service coordinator. ICause: The IBM Token-Ring Network adapter has detected a ring failure while trying to open the adapter. Action: 1. Check and secure all cable connections between your adapter and the Multistation Access Unit (MSAU). Correct any related problems and try the operation again. 2. If there are no related problems, refer to the documentation that was shipped with your adapter to run adapter diagnostics; then try the operation again. 3. If the problem persists, print or save the LANTRAN.LOG file and contact your service coordinator. ICause: The IBM Token-Ring Network adapter has detected a monitor contention failure or has received a beacon frame from the ring while trying to open the adapter. Action: 1. Check and secure all cable connections between your adapter and the Multistation Access Unit (MSAU). Correct any related problems and try the operation again. 2. If there are no related problems, refer to the documentation that was shipped with your adapter to run adapter diagnostics; then try the operation again. 3. If the problem persists, print or save the LANTRAN.LOG file and contact your service coordinator. ICause: The IBM Token-Ring Network adapter has detected a that another station on the ring has an adapter address equal to the address specified for your adapter. Action: Note the identification number of this message and then contact your system administrator. ICause: The IBM Token-Ring Network adapter has detected a parameter request error while trying to open the adapter. Action: 1. Check and secure all cable connections between your adapter and the Multistation Access Unit (MSAU). Correct any related problems and try the operation again. 2. If there are no related problems, refer to the documentation that was shipped with your adapter to run adapter diagnostics; then try the operation again. 3. If the problem persists, print or save the LANTRAN.LOG file and contact your service coordinator. ICause: While attempting to insert into the ring, a command forcing this adapter to remove from the ring was received. Action: Contact your LAN personnel to determine why the REMOVE command was issued for your machine. ? ? ICause: RPL station is the first station attempting to insert onto the ring. Action: 1. Retry the operation. 2. If the problem persists, refer to the documentation that was shipped with your adapter to run adapter diagnostics; then try the operation again. 3. If the problem persists, print or save the LANTRAN.LOG file and contact your service coordinator. ICause: Physical insertion of RPL station onto the ring failed. Action: 1. Check the adapter configuration and retry the open request. 2. If the problem persists, refer to the documentation that was shipped with your adapter to run adapter diagnostics; then try the operation again. ? ? ? ? ? ICause: A problem was detected on micro-code level "00 00 00 C2 45 50". Action: Request and install engineering change ECA0066, part# 92F9122, on your system, or use the configuration feature of the LAN Adapter and Protocol Support installation program to change the value for the number of transmit buffers to be greater than 1.