yes Scott in first case no error message . It immediately returns to command
line.

and the other is running .. for more than 5-10 min .. with no output.

I tried connecting to a public as400 server using <tn5250 Server-Ip> to
check if tn5250 is working ,and found it to be good.I was able to get a sign
on . So i hope my tn5250 pkg is ok.


Rhishabh


On Sat, Apr 10, 2010 at 1:17 AM, Scott Klement <tn5250@xxxxxxxxxxxxxxxx>wrote:

Hello,

1. Now when i give tn5250 AS4 in shell i get the prompt again instantly
with
nothing happening .

No error messages, nothing? It just immediately returns to the
command-line?

2. When i used the command tn5250 ssl:XXX.XX.XXX.XX as Scott said .. it
just
does nothing and gives me prompt after 5 min . Am i missing anything ?'

Hmmmm... 5 min?? Hmmm... Is there some way I can attempt to
reproduce this issue?

Log file entry in first case is
tn5250_ssl_stream_init() entered.
SSL Method = SSLv23_client_method()

These are normal messages that are always there for a SSL connection.
They don't me anything other than that you're using SSL.

Since i have not used tshark, tcpdump earlier so dont know how to use it,
man pages are lengthy and hence trying to read/use it .

I'll let Holger respond to that, since I'm not sure what he has in mind
for these network sniffers.
--
This is the Linux 5250 Development Project (LINUX5250) mailing list
To post a message email: LINUX5250@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/linux5250
or email: LINUX5250-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/linux5250.



This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2020 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].