Client Access PC5250 Emulation

235 pts.
Tags:
Client Access 5.4
I am using Client Access for Windows Ver 5.4. I use the PC5250 emulator to start a session with our AS400 iSeries. I cannot connect and get a signon screen. I can, however thru DOS telnet get a sign on screen. I am not maxed out on sessions. What am I missing to be able to use the emulator and start a session ? Where telnet works ? Thank you so much for any ideas

Software/Hardware used:
iSeries Access for Windows V5r4

Answer Wiki

Thanks. We'll let you know when a new response is added.

Add your answer…

Discuss This Question: 13  Replies

 
There was an error processing your information. Please try again later.
Thanks. We'll let you know when a new response is added.
Send me notifications when members answer or reply to this question.

REGISTER or login:

Forgot Password?
By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy
  • TomLiotta
    I cannot connect and get a signon screen.   Why not? What happens? Is there an error message and/or code?   Do other users connect okay? Did it work previously for you? Is a current V5R4 service pack installed on this PC?   Tom
    125,585 pointsBadges:
    report
  • ckidder
    Nothing happens.......There is no error message or code.  No one can connect.  We received a different router from Frontier.  We could connect prior to that.    
    235 pointsBadges:
    report
  • TomLiotta
    Again, is a current V5R4 service pack installed on this PC?   It doesn't make sense that "nothing happens". A form of timeout message/code at the least should be shown. If it's not shown, something is wrong on the PC itself. It's possible that an iSeries Access service pack might fix it or that a Windows service pack will (though that's less likely).   I don't currently have a V5R4 client available, but somebody else might correct any differences from V5R3. On the Start/Programs iSeries Access menu under Emulator, there should be a Trace Facility menu option. Start it and choose 5250 Emulator-> Communication data-> TCP/IP. Then try to start the emulator and Connect.   After waiting at least a couple minutes (I'd wait five full minutes), go ahead and close it all down. The trace will need to be saved, and you can also save a formatted version. Review the formatted version to see if or where it either stops or begins to attempt retransmitting. You should be watching the PC clock and noting a few relevant timestamps to track against the trace data records.   That might help isolate where things are getting off track. Commonly, a new router can require various ports to be opened or configured in both directions. For iSeries Access there may be half a dozen or more depending on what functions are used and the protocols.   Tom
    125,585 pointsBadges:
    report
  • ckidder
    I was unsuccessful with the Trace Facility...BUT......if I go to the Dos prompt and Telnet....."address" I can get a sign on screen.  If I go thru the emulator I says its trying to connect but the sign on screen never appears....It will time out....what would prohibit the emulator from getting to the sign on screen ?  (I am very thankful for your help BTW.....I am obviously not a pro at this....)  
    235 pointsBadges:
    report
  • TomLiotta
    ...the sign on screen never appears….It will time out….   How do you know it times out if there is no error message/code?   what would prohibit the emulator from getting to the sign on screen ?   Most common cause with a new router is ports that aren't open. If nobody made changes to the server when the router was changed, it's unlikely that a required host Signon server isn't started; but it's another possibility. For the Signon server not being started, a 'timeout' shouldn't be the symptom (if that's what happens).   The iSeries emulator uses the telnet protocol, but it's TN5250E rather than plain telnet. It also performs license checks that simple telnet doesn't do. Additional ports must be open and appropriate host servers should be running.   Tom
    125,585 pointsBadges:
    report
  • ckidder
    Again, thank you for your help in helping me solve this.   Heres everything I know.  In my attempt to sign on to the AS400 it says....."Sign onto iSeries....'  In the Server box I have the address.....50.102......           At the very bottom left it says...."connecting"      Just above the word connecting it has the letter "V"  and then......."a"          After a few seconds the message displays......"CWBC1048   A time-out occured trying to connect"    My router in port forwarding has two entries.......one of which is telnet using port 23.     The other entry is TN5250E with ports 23,8476, 9475 I CAN go to a DOS prompt and type "telnet.....50.102......and get a normal AS400 sign on screen. Why can I not connect then, using the iSeries Windows PC5250 emulator ? We have been using the PC5250 for years.   We lost this function when we replaced routers a few months ago.   I've called the phone co. who provided the router and could not get any help as they are unfamilier with the IBM emulator software.    
    235 pointsBadges:
    report
  • TomLiotta
    ……”CWBC1048   A time-out occured trying to connect”   Ah, finally an error message to think about.   From a Windows command line, run CWBPING [server] to see which functions can/cannot connect.   Do you not have a Support group you can get help from?   Tom
    125,585 pointsBadges:
    report
  • ckidder
    I can indeed ping (not cwping ?) the server.  That is what is so puzzling in that I can ping and yet it just won't get to the sign on screen.....?   (I do not have a support group)    Thank you for any ideas you may have.
    235 pointsBadges:
    report
  • TomLiotta
    I can indeed ping (not cwping ?) the server.   Use CWBPING, not CWPING. If CWBPING reports failures, what are the failures?   The PING command is relatively meaningless and doesn't help. It mostly just tells you if a network route exists to the server. It doesn't tell you if anything works.   Tom
    125,585 pointsBadges:
    report
  • ckidder
    Using CWBPING I get the following failures: CWBC01003 - Sockets error, function connect <> returned 10060 CWBC01048 - A time-out occurred trying to connec tto the iSeries CWBC01006 - Unable to connect to server mapper CWBC01011 - Remote port could not be rsolved CWBC01008 - Unable to connect to server application Central Client, returned 10060  
    235 pointsBadges:
    report
  • TomLiotta
    Okay, then the very first thing is to run ENDHOSTSVR *ALL on the server. This should be done when things are fairly quiet and there aren't a lot of remote systems (PCs or otherwise) trying to connect to the server. Do not tell the ENDHOSTSVR command to end any active connections. That is, leave everything at the default except the *ALL for the initial parameter.   That will cause a few minutes where no new connections can be made, but anything that's already running will continue. By ending host servers, you give them a chance to clean up whatever is going on. Then...   Run STRHOSTSVR *ALL on the server. Make sure that there are no important errors reported in the joblog after the STRHOSTSVR command runs. There might be a few conditional errors telling you that one or more server functions can be accessed using a particular protocol but not others, or that one or more are already active. Most general messages can be ignored for this, but report any troublesome error messages back here. The server should be back in its original condition at the very least at this point. Or it might be ready to receive connections.   The STRHOSTSVR command will cause new server instances to be started. They will all have fresh joblogs in case more errors need to be watched.   So far, it should only take a couple minutes or so to get to this point. After a couple minutes have gone by, try CWBPING from the PC again. If you run it from a Windows command line, you can copy/paste any messages or error results back here. That will help tell us what service (and port) needs attention. We need service names from message texts and return codes together.   It's possible that all that's needed is starting (or restarting) the host servers. I suspect that the router needs to be configured to open a few specific ports that allow the iSeries Access emulator to make all of its required connections. The iSeries Access emulator can do a lot more than plain simple telnet. The telnet port by itself is not sufficient.   Tom
    125,585 pointsBadges:
    report
  • ckidder
    These are the results of first ENDHOSTSVR *ALL and then STRHOSTSVR *ALL and then CWBPING......Thank you for your help...... STRHOSTSVR *ALL Job 067095/QUSER/QZSCSRVSD started on 12/03/12 at 16:46:48 in subsystem QSYSW Job 067096/QUSER/QZHQSRVD started on 12/03/12 at 16:46:48 in subsystem QSYSWR Job 067097/QUSER/QNPSERVD started on 12/03/12 at 16:46:48 in subsystem QSYSWR Job 067098/QUSER/QZRCSRVSD started on 12/03/12 at 16:46:48 in subsystem QSYSW Job 067099/QUSER/QZSOSGND started on 12/03/12 at 16:46:49 in subsystem QSYSWR Job 067100/QUSER/QPWFSERVSD started on 12/03/12 at 16:46:49 in subsystem QSER Job 067101/QUSER/QZDASRVSD started on 12/03/12 at 16:46:50 in subsystem QSERV Job 067102/QUSER/QZSOSMAPD started on 12/03/12 at 16:46:50 in subsystem QSYSW CWBPING Microsoft Windows [Version 6.1.7601] Copyright (c) 2009 Microsoft Corporation.  All rights reserved. C:\Users\Connie> C:\Users\Connie>CWBPING 50.102.238.246 IBM iSeries Access for Windows Version 5  Release 4  Level 0 Connection Verification Program (64-bit) (C) Copyright IBM Corporation and Others 1984, 2005.  All rights reserved. U.S. Government Users Restricted Rights - Use, duplication or disclosure   restricted by GSA ADP Schedule Contract with IBM Corp. Licensed Materials - Property of IBM To cancel the CWBPING request, press CTRL-C or CTRL-BREAK I - Verifying connection to system 50.102.238.246... E - CWBCO1003 - Sockets error, function connect() returned 10060 E - CWBCO1048 - A time-out occurred trying to connect to the iSeries E - CWBCO1006 - Unable to connect to server mapper E - CWBCO1011 - Remote port could not be resolved E - CWBCO1008 - Unable to connect to server application Central Client, returned  10060  
    235 pointsBadges:
    report
  • TomLiotta
    You show that STRHOSTSVR started the server mapper (i.e., QZSOSMAPD), and CWBPING could not access the server mapper. It seems likely that the router/firewall needs ports to be opened. Review the Establish client/server communications topic in Information Center. Drill into its sub-topics to see lists of ports that need to be opened in order to use various iSeries Access functions. -- Tom
    125,585 pointsBadges:
    report

Forgot Password

No problem! Submit your e-mail address below. We'll send you an e-mail containing your password.

Your password has been sent to:

To follow this tag...

There was an error processing your information. Please try again later.

REGISTER or login:

Forgot Password?
By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy

Thanks! We'll email you when relevant content is added and updated.

Following