Explanation: A session is PENDING or in the process of changing states.
Explanation: The manager workstation is connecting to a client workstation. A connection is being established.
Explanation: The RWCcontrol of a workstation has been suspended.
IReserved
Explanation: The client pressed a hot key sequence during an active RWCsession. The session state is changed to MONITORING.
IReserved
Explanation: The manager and client workstations have made a connection and are attempting to establish a session.
Explanation: The manager and client workstations are terminating or ending a session.
Explanation: The client pressed the hot key sequence and is BUSY while choosing states.
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
Explanation: Title added to OS/2 task list.
Explanation: Instructional message displayed on the Remote Workstation Control pop-up window.
IReserved
IReserved
IReserved
Explanation: This is the OS/2 Full Screen description for the icon.
- The message text
- An explanation of the messages
- The recommended user response
- The system response of the product after logging the message
- The recommended programmer response
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
Explanation: The current task could not allocate sufficient memory to continue processing.
User Response: Contact the system programmer.
Programmer Response: Correct the memory allocation problem and restart the task.
System Action: Processing terminates.
Explanation: Unable to complete processing because a disk-full error was encountered.
User Response: Free some disk space by removing unnecessary program or data files.
Programmer Response: None.
System Action: Processing terminates.
Explanation: An event has occurred that requires your attention. Processing will not continue until you press a key.
User Response: Press any key.
Programmer Response: None.
System Action: Processing continues when a key is pressed.
Explanation: The .hlp file for this function was not found in the directory where the Remote Workstation Control service is installed.
User Response: You can continue without help, or contact the system programmer to restore the help file.
Programmer Response: Copy the appropriate help file from the installation diskette.
System Action: Processing continues.
Explanation: Unable to complete the request because of a lack of system resources.
User Response: Contact the system programmer.
Programmer Response: Release some system resources and retry.
System Action: Processing terminates.
Explanation: Unexpected error encountered in the specified component.
User Response: Contact the system programmer.
Programmer Response: Follow your normal problem determination procedures.
System Action: System action depends on the error encountered.
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
Explanation: An error occurred trying to start the Remote Workstation Control service. The following return codes represent possible causes of the failure:
- 1 - System error. A call to the operating system generated an error.
- 3 - Netfinity error. A call to Netfinity generated an error.
User Response: Try to start other remote services. If they start, shut down and restart the workstation and try again to start the Remote Workstation Control service. Otherwise, contact your system programmer.
Programmer Response: To determine the problem, complete the following steps:
- Add the following statement to the bottom of the CONFIG.SYS file on this workstation:
- SET IKODEBUG=path where path is the drive and directory in which you want the debug file to be created
- Shut down and restart the workstation.
- Repeat the action that caused this error.
- One of the following files will be created in the directory you specified.
- IKOTRBAS.001 on the Client workstation.
- IKOTRGUI.00n ,where n is the number of RWC sessions concurrently active, on the Manager workstation.
- Send a copy of the file generated to your IBM representative for assistance.
- NOTE: Remember to remove this statement from the CONFIG.SYS file after you get the debug file.
System Action: The Remote Workstation Control session does not start.
Explanation: Your workstation failed to receive data sent from the remote workstation. The following return codes represent possible causes of the failure:
- 1 - System error. A call to the operating system generated an error.
- 2 - Buffer error. There is not enough space to receive the data sent from the remote workstation.
- 3 - Netfinity error. A call to Netfinity generated an error.
User Response: Try to use other remote services. If they work, shut down and restart the workstation and restart the Remote Workstation Control service. Otherwise, contact your system programmer.
Programmer Response: To determine the problem, complete the following steps:
- Add the following statement to the bottom of the CONFIG.SYS file on this workstation:
- SET IKODEBUG=path where path is the drive and directory in which you want the debug file to be created
- Shut down and restart the workstation.
- Repeat the action that caused this error.
- One of the following files will be created in the directory you specified.
- IKOTRBAS.001 on the Client workstation.
- IKOTRGUI.00n ,where n is the number of RWC sessions concurrently active, on the Manager workstation.
- Send a copy of the file generated to your IBM representative for assistance.
- NOTE: Remember to remove this statement from the CONFIG.SYS file after you get the debug file.
System Action: The Remote Workstation Control session ends.
Explanation: Your workstation failed to send data to the remote workstation. The following return codes represent possible causes of the failure:
- 1 - System error. A call to the operating system generated an error.
- 3 - Netfinity error. A call to Netfinity generated an error.
- 4 - Network timeout error. The remote session partner did not respond within the time limit specified in the Network Timeout Configuration.
User Response: Check that remote applications are still active and that other remote services work.If they work, shut down and restart the workstation and restart the Remote Workstation Control service. Otherwise, contact your system programmer.
Programmer Response: To determine the problem, complete the following steps:
- Add the following statement to the bottom of the CONFIG.SYS file on this workstation:
- SET IKODEBUG=path where path is the drive and directory in which you want the debug file to be created
- Shut down and restart the workstation.
- Repeat the action that caused this error.
- One of the following files will be created in the directory you specified.
- IKOTRBAS.001 on the Client workstation.
- IKOTRGUI.00n ,where n is the number of RWC sessions concurrently active, on the Manager workstation.
- Send a copy of the file generated to your IBM representative for assistance.
- NOTE: Remember to remove this statement from the CONFIG.SYS file after you get the debug file.
System Action: The Remote Workstation Control session ends.
Explanation: An error occurred trying to close the Remote Workstation Control service. A return code of 1 means that a call to the operating system generated an error.
User Response: Contact your system programmer.
Programmer Response: To determine the problem, complete the following steps:
- Add the following statement to the bottom of the CONFIG.SYS file on this workstation:
- SET IKODEBUG=path where path is the drive and directory in which you want the debug file to be created
- Shut down and restart the workstation.
- Repeat the action that caused this error.
- One of the following files will be created in the directory you specified.
- IKOTRBAS.001 on the Client workstation.
- IKOTRGUI.00n ,where n is the number of RWC sessions concurrently active, on the Manager workstation.
- Send a copy of the file generated to your IBM representative for assistance.
- NOTE:
Remember to remove this statement from the CONFIG.SYS file after you get the debug file.
System Action: The Remote Workstation Control session abends.
Explanation: You pressed the Terminate push button.
User Response: Press the 'Yes' push button to continue ending the session. Press the 'No' push button to cancel.
Programmer Response: None.
System Action: If you choose 'Yes', the session ends and control returns to the operating system. If you choose 'No', the Change State window reappears and enables you to choose another state.
- The message text
- An explanation of the messages
- The recommended user response
- The system response of the product after logging the message
- The recommended programmer response
IReserved
Explanation: The remote user refused to allow access to the remote workstation.
User Response: Contact the remote user and convince them to grant you access.
Programmer Response: None.
System Action: The Remote Workstation Control session ends.
Explanation: No one was at the remote workstation, and the request for access timed out without a response.
User Response: Contact a person near the remote machine, and have them respond to the access request, then retry the action.
Programmer Response: None.
System Action: The Remote Workstation Control session ends.
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
Explanation: The RWC device driver was successfully loaded.
User Response: None.
Programmer Response: None.
System Action: Processing continues.
Explanation: The following files may have been erased from the directory in which Netfinity Server is installed:
- EQNKRCLD.EXE
- EQNRCKB.EXE
- EQNKRCSH.EXE
- EQNKRAS.DLL
- EQNRCUT.DLL
- EQNRCVI.DLL
- EQNUT.DLL
User Response: Contact the system programmer.
Programmer Response: Reinstall Netfinity Server on the client.
System Action: Processing terminates.
IReserved
Explanation: The RWC files were successfully loaded and started.
User Response: None.
Programmer Response: None.
System Action: Processing continues.
Explanation: Either the CONFIG.SYS file was not updated correctly when the RWC was installed, or one or more of the following files could not be found when you started the client:
- EQNRCKB.EXE
- EQNKRCLD.EXE
- EQNKRCSH.EXE
- EQNRCUT.DLL
- EQNRCVI.DLL
- EQNKRAS.DLL
- EQNUT.DLL
User Response: Contact the system programmer.
Programmer Response: Perform the following steps:
- Ensure that the following statements appear before any other DEVICE or CALL statements in the CONFIG.SYS file (drive\dir represents the path where the RWC is installed).
- DEVICE=drive\dir\EQNKVKBD.SYS
- DEVICE=drive\dir\EQNKRCSH.EXE
- CALL=drive\dir\EQNKRCLD.EXE
- NOTE:
When you are using the High Performance File System (HPFS), the Installable File System (IFS) statement must appear before the DEVICE and CALL statements.
- Verify that all the files listed in the explanation are in the path where the RWC is installed.
- If you changed the CONFIG.SYS file, shut down and then restart the workstation.
- If one or more RWC files is missing, deinstall and reinstall Netfinity Server.
System Action: Processing terminates.
IReserved
Explanation: You tried to exit the client interface while the communication lines were still open. Your confirmation will close all communications.
User Response: Press the 'Yes' push button to close all communications and exit the client. Press the 'No' push button to cancel and to keep the client and communications running.
Programmer Response: None.
System Action: If you confirm, processing ends normally and control is returned to your operating system. If you cancel, the client and communications keep running.
IReserved
IReserved
IReserved
IReserved
Explanation: The communication link failed because of an undetermined error.
User Response: Restart the RWC session. If the communications continue to fail, contact the system programmer.
Programmer Response: Verify that the network address parameters are correct.
System Action: The session terminates.
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
Explanation: You could not start a session with the client for one of the following possible reasons:
- Network address parameters (for example, the adapter address of the client) are not valid.
- A cable is disconnected on the client.
- Resources required to start a session (such as threads, semaphores, queues, and memory) may not be available on the manager or client.
User Response: Verify the following:
- That the client is running.
- That the network address parameters (for example, the adapter address of the client) entered during configuration are correct.
- That all cables are connected.
- That system resources (such as threads, semaphores, queues, and memory) are available on both workstations.
Programmer Response: None.
System Action: The session does not start and control is returned to your operating system.
IReserved
IReserved
Explanation: The session has ended. You have full control of your workstation.
User Response: None.
Programmer Response: None.
System Action: Control is returned to the operating system. Your workstation is ready for another session.
Explanation: The client has ended the RWC session. You can start a new session with the same or other available clients.
User Response: None.
Programmer Response: None.
System Action: The session ends and control is returned to the operating system.
Explanation: The session was terminated successfully at your request.
User Response: None.
Programmer Response: None.
System Action: The session ends, and control is returned to your operating system.
IReserved
Explanation: The client interrupted the session in order to change to a new state (for example, from controlling to monitoring). The session appears Busy until the client chooses a new state.
User Response: Wait for the client to choose a new state. Otherwise, terminate the session.
Programmer Response: None.
System Action: Processing continues, or, if you terminate the session, processing ends.
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
Explanation: An error occurred when starting the manager or client.
User Response: Retry. If the error persists, contact the system programmer.
Programmer Response: Verify the following:
- That the network address parameters are correct.
- That sufficient resources (such as threads, semaphores, queues, and memory) are available for the RWC.
System Action: Processing terminates and control is returned to the operating system.
Explanation: Graphics applications that run in native DOS or on the virtual DOS machine are not supported and cannot be displayed on your screen.
User Response: On the client, switch out of DOS or switch to an application that is supported (for example, a text application).
Programmer Response: None.
System Action: Processing continues.
Explanation: The manager workstation's code page is different from the client's code page. A character typed on the manager workstation may be displayed as a different character on the client
User Response: Press the 'OK' push button.
Programmer Response: None.
System Action: Processing continues.
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
Explanation: The manager keyboard layout can be changed to match the client keyboard layout for this particular client during this session. The keyboard layout change will only affect this manager-client connection.
User Response: Press the 'Yes' push button if you want to change the manager workstation keyboard layout to that of the client. Press the 'No' push button if you do not want to change the keyboard layout.
Programmer Response: None.
System Action: Processing continues, depending on the user response.
Explanation: Your workstation is not configured to support the requested keyboard layout.
User Response: Press the 'OK' push button.
Programmer Response: None.
System Action: Processing continues, but the keyboard layout is not changed.
IReserved
IReserved
IReserved
IReserved
IReserved
Explanation: Because of an unexpected error, the session ends.
User Response: Restart the session. If the problem continues, shut down and restart the client.
Programmer Response: None.
System Action: The RWC session ends.
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
Explanation: The client workstation is already in session with a manager workstation.
User Response: Retry later or attempt to establish a session with a different client workstation.
Programmer Response: None.
System Action: Processing continues.
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
IReserved
Explanation: Because of an unexpected error, the session ends.
User Response: Restart the session. If the problem continues, shut down and restart the client.