RE: Automatic Signon/Telnet: How can the 5250 client differentiate between V5R1 and Pre-V5R1 Releases at signon time?

Great, much thanks for your help. 
I think get in the second 2 for V5R3 with password level 2 when I set the
first byte to 1. Looking at the V5R3 password level, it is set to 2 which
matches the server value. I guess we have it now. 

Is there any reference or interface description for all that? Important for
me are the new protocol changes. I appreciate it that much if you can point
me to any reference.

Thanks again
N.Khoury

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Patrick Botz
Sent: Thursday, February 10, 2005 6:13 PM
To: Midrange Systems Technical Discussion
Subject: RE: Automatic Signon/Telnet: How can the 5250 client differentiate
between V5R1 and Pre-V5R1 Releases at signon time?

The bit's are exchanged in the 2 byte header id (first byte is for client,
second is for host).  On the client seed flow up, set the client byte to 1
indicating the client can support SHA.  Then in the reply, the host byte
will be 0 or 1 for DES, or 2 or 3 for SHA.

FYI...I'm getting this info from someone on the Client Access team (I don't
know this stuff personally :-) )...

Patrick Botz
Senior Technical Staff Member
eServer Security Architect
(507) 253-0917, T/L 553-0917
email: botz@xxxxxxxxxx

-- 
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.