Shift-Esc ( [sys req] ) in the workstation screen only works a few
times then stops. I've tried remapping another key to rule out a
keyboard problem, and it does nothing no matter what key I map. I've
tried other keyboards with no success. Users are limited users, but
they have full access to C:\Program files\IBM.
I've renamed the keyboard file and recreated another, and it worked a
few times then stopped working. I've logged on as three different
users with the same results.
I support 300 computers, many exactly like this one, and I do not have
this problem on any others.
Any advice would sure be appreciated.
http://support.microsoft.com/kb/310417
"A keyboard shortcut does not work if it conflicts with a keyboard combination that is used in the program that is currently active."
Keyword "CURRENTLY ACTIVE"
The article talks about setting a shortcut for launching a program, but the quoted statement above is also true for a running program with internal keybd shortcuts.
Close all other programs and see if the keybd shortcut works...Then figure out which program has a custom shortcut and remove that shortcut from the OTHER program or programs
This is the only thing I can think of which would cause this behavior.
I can log on and Shift-Esc will work from 2 to 5 times then stop. I
can log off and back on, and it'll work again a few times then stop.
I appreciate your response. I have tried remapping the tilde (~) to
[sys req] just as an experiment, and it doesn't work for that either.
I would think that would rule out keyboard problems, but I'm not
really sure of anything at this point.
Just signing off and then signing on again at the same device
emulation session [at the active emulation session which was not
stopped\restarted] of the PC5250 emulator enables the SysRqs feature to
start functioning again? With regard to how the feature "stops", does
the emulation show the System Request command line, but nothing happens
when Enter is pressed? Or instead, does the SysReq line does not even
get displayed?
If the SysRqs simply fails to perform the requested action when
requested [e.g. by Enter with no option to present SysRqsMenu, by
option-1 to effect the TFRSECJOB, or by option-2 to effect EndRqs], but
the SysRqs line does appear, that symptom would seem to suggest an issue
in the OS software; i.e. the job is "masked" from receiving and
processing the System Request "event".
Regards, Chuck
It sounds OS-related to me too. I wonder if it has anything to do
with the Windows accessibility features. Try opening Control Panel-
>Accessibility Options->Keyboard. Maybe one of those is interfering
with iSeries Access. Or perhaps some other memory-resident software
on the PC.
John
I'm thinking along the same lines as John, something Windows related.
Could you log on to that PC under a different user account and see if
iSeries Access still exhibits the same issues? I've remember having a
problem similar to this (not iSeries Access though) and it had
something to do with the users settings on a particular PC. Other
users on the same PC were fine. Couldn't find the issue in the end so
simply performed a software rebuild from Windows up, which resolved it.
In response to Chuck, I meant I could log off the computer and back
on, it'd start working again. Just closing the session has no
effect. And "does not work", I mean it does absolutely nothing that I
can tell.
John, I have not checked accessibility features, but every user I've
tried have the same results. Shift-Esc works two to four times then
stops until the user logs off the computer and back on.
I appreciate the responses. I've been embroiled in another problem
this week and have had to put this one one hold, but I need to get
back on it.