Troubleshoot Other Operations Console Problems; Related Information - IBM eServer iSeries Manual

Access for windows operations console
Hide thumbs Also See for eServer iSeries:
Table of Contents

Advertisement

Troubleshoot other Operations Console problems

When using Operations Console you can encounter the following problems:
Operations Console remains in QCTL
Solutions for when Operations Console remains in QCTL when it should be CTLxx.
Local console receives message: Remote Access Service server did not start
Solutions for when the local console gets Remote Access Service Server did not start message
(Windows NT only).
System requests will not work
Solutions for when system requests will not work.
Operations Console remains in QCTL
This usually shows up after a migration but could be found at any time you have been working with
resources. QCONSOLE still remains in QCTL when you would have expected it to be reassigned as
another workstation. Be sure that the system has not been IPLed with DEBUG turned on. A good
indication is that no other interactive subsystem has started, if present, and others may also be absent.
Check SYSVAL QIPLTYPE it should be 0.
Note: If the new console fails to work in OS/400 you may need to use another workstation to manually
delete the controller and device description associated with the old console device.
Local console receives message: Remote Access Service server did not start
If a local console is set up to receive calls and there is no PC modem configured to receive those calls, it
will post a Remote Access Service Server did not start message. To fix this, either set up the local
console to not receive calls or configure a modem (even one that does not exist). But be careful with this
latter approach. If both serial ports are assigned to Operations Console, the modem will have to reside on
COM3 and many PCs will not have one. This can also be caused by not having the Windows NT Service
pack installed.
System requests will not work
When using Operations Console, SYSREQ equals Shift+ESC as defined as the default for 5250
emulation. Most keyboards have the Prt Screen key labeled as SYSREQ would be activated by using that
key with the Ctrl key, but Windows has that key reserved. You have to remap the keyboard by using the
operating system, not 5250, in order to change it.

Related information

Listed below are the iSeries manuals and IBM Redbooks
Center topics that relate to the Operations Console topic. You can view or print any of the PDFs.
Manuals
v Twinaxial Console
The twinaxial console uses a command line interface to access and manage your iSeries, and it
does not require the use of a personal computer to act as a console. You access the iSeries through a
console screen, keyboard, and twinaxial cables.
Web site
v iSeries Access Web site
This web site includes online product information about iSeries Access and Operations Console.
Other information
108
iSeries: iSeries Access for Windows Operations Console
(in PDF format), Web sites, and Information

Advertisement

Table of Contents
loading

Table of Contents