RE: pcAnywhere 9.0

I use PCAnywhere a lot and it's extremely useful. However, it does sometimes
take a long time to reflect changes on the host screen or unlock the
keyboard. When I see that happening I press CTRL/ALT/R, which forces
PCAnywhere to completely refresh the screen. That always works for me.

Albert York     


        -----Original Message-----
        From:   Jerry Kern [SMTP:Jerry.Kern@midwayproducts.com]
        Sent:   Monday, June 11, 2001 8:08 AM
        To:     MIDRANGE-L@midrange.com
        Subject:        pcAnywhere 9.0

        I have an AS/400 running V4R5, and my local office pc is ethernet
attched and running CA/Express at V4R5M0 & SF65345. My intent is to
communicate with my network using pcAnywhere version 9.0 to dial into my
local pc at my office, from home.

        My connections are working as expected. I do however have one
nagging problem I cannot seem to figure out.

        If I leave a green screen session active on the host pc, when I dial
in I can log on to the 400 and use the command line to do normal 400 stuff.

        The problem is that once I try any non-AS/400 activity (outside of
the 5250 session), I cannot utilize my keyboard for any functions including
returning to the CA 5250 session. The keyboard simply stops responding, with
no error messages.... I just type and nothing appears on the screen.

        Even after I've used the 5250 session, if for instance, I try to
start a new session and have to enter an AS/400 user ID & password into a
logon prompt (not a green screen login), the keyboard shows nothing.

        If I cancel the remote session, and dial back into the system again,
things seem to be reset until I repeat this chain of events. Normally I only
need to monitor the AS/400, but occasionally I need to access my Groupwise
(Novell) email or an Access database, and this is where the death of the
keyboard response becomes an issue. 

        There is a setting in pcAnywhere that I've set to allow my defined
caller options to enable the mouse and keyboard to be active for the session
at both the host and remote locations.

        I've also tried the various Application settings options for DOS
sessions. There are 3 levels of keyboard handling. So far I've had this set
to disabled and Level 1. I just changed this to be at Level 3 and if that
doesn't work when I go home tonight I will try Level 2. Those are my
remaining options and at this point I'm at a loss as to what else to try.
I've scoured the internet, midrange-l, client access, and symantec web sites
looking for any useful info.

        Any input you may have would be appreciated.

        Regards, Jerry Kern
        Senior Analyst, Midway Products
        IBM Certified RPG Programmer
        jerry.kern@midwayproducts.com

        +---
        | This is the Midrange System Mailing List!
        | To submit a new message, send your mail to
MIDRANGE-L@midrange.com.
        | To subscribe to this list send email to
MIDRANGE-L-SUB@midrange.com.
        | To unsubscribe from this list send email to
MIDRANGE-L-UNSUB@midrange.com.
        | Questions should be directed to the list owner/operator:
david@midrange.com
        +---
+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---