View Full Version : CLIENT ACCESS TO REMOTE AS/400
01-01-1995, 02:00 AM
I have a pc using client access and I want to access a remote AS/400 thru satellite communication (delay 1.2 second,to send a packet and to get the response). I am using now NSrouter (ANYNET over TCP/IP)and it works fine but I am facing intermittent sessions hang and I think this due to APPC problems and satellite delay. I tried to use TCP/IP and I have the AS/400 successfully connected but I ma not able to atart a 5250 session.When I try to start a session ,I am getting a blank screen and no signon display. Any help ?
09-07-2000, 03:41 AM
Even if from V4R2 shouldn't be a problem, have you checked if host servers are active on AS/400 side ? Simone
09-07-2000, 09:53 AM
Ziad, Almost always if someone is successfully connected -and- doesn't have a signon screen -and- doesn't have a 657 or 658 error at the bottom has system value QAutoVrt set to 0. Do a DspSysVal QAutoVrt . Write down the number (most likely 0). Do a ChgSysVal QAutoVrt *NoMax . Try getting your signon screen now. Then reset QAutoVrt back to it's original value. Bill
09-07-2000, 07:05 PM
Since, as you say, there is a connection, you must have TCP/IP running. However, did you check if the TELNET server is running?
09-07-2000, 10:47 PM
Hello, Telnet server is running. I can telnet the AS/400 from Windows or DOS. I can ping also the AS/400. Sorry,I forget to mention that I have a 657 error on the screen. Thanks and Regards
09-08-2000, 05:29 AM
This could mean that you had an active session and the PC got disconnected without signing off. If the timeout value is too high, the AS/400 doesn't realize that your session has been disconnected and therefore you can not get a signon screen again. Go to the system terminal or another computer's session and run WRKACTJOB. See if your user ID is still signed on. If so, force the job to end. After the job drops off, you should be able to launch C/A and get the signon screen. ==Scott==
09-08-2000, 07:39 AM
Ziad, A 657 on the screen will usually mean that it can't find the correct entry in the HOSTS. file. Check to make sure that the HOSTS file exists in your Windows folder. If it's not there, you should have a HOSTS.SAM file that you can copy and edit. The instructions on what the HOSTS file should look like are in the .SAM file. Bill
Powered by vBulletin® Version 4.1.5 Copyright © 2013 vBulletin Solutions, Inc. All rights reserved.