|
Thanks Bruce! -----Original Message----- From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Bruce Vining Sent: Thursday, February 10, 2005 11:27 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? Go to the PartnerWorld Server and Storage site (www.developer.ibm.com/iseries) Select "Special IBM eServer benefits" Log in with your IBM ID Select "Licensed Internal Programming Interfaces (LIPIs)" You will need to be a PartnerWorld member, and if you have problems you can call PartnerWorld Contact Services at 1-800-426-9990 Bruce Vining "Khoury.com" <nageeb@xxxxxxxxx m> To Sent by: "'Midrange Systems Technical midrange-l-bounce Discussion'" s@xxxxxxxxxxxx <midrange-l@xxxxxxxxxxxx> cc 02/10/2005 11:06 Subject AM RE: Automatic Signon/Telnet: How can the 5250 client differentiate between V5R1 and Please respond to Pre-V5R1 Releases at signon time? Midrange Systems Technical Discussion You are right, were could I order this document? -----Original Message----- From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Bruce Vining Sent: Thursday, February 10, 2005 6:28 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? Given the information you seem to have available it sounds like you have a pre-V5R1 version of the Signon Server LIPI document. You need to order a more up to date level of the LIPI documentation. Bruce Vining "Khoury.com" <nageeb@xxxxxxxxx m> To Sent by: "'Midrange Systems Technical midrange-l-bounce Discussion'" s@xxxxxxxxxxxx <midrange-l@xxxxxxxxxxxx> cc 02/10/2005 04:14 Subject AM RE: Automatic Signon/Telnet: How can the 5250 client differentiate between V5R1 and Pre-V5R1 Releases Please respond to at signon time? Midrange Systems Technical Discussion Thanks Patrick, I do send a seed request of 28 bytes at the beginning, but the seed reply does not contain any QPWDLVL bit. Can you please give a sample showing how identify the QPWDLVL bit or any reference that can help here? I am using the following 28 bytes Host Seed Reply structure: {Length(4)|Header ID(2)|Server ID(2)|CS Instance(4)|Correlatio ID(4)|Template Length(2)|Reply ID(2)|Primary RC(2)|Secondary RC(2)|Host Seed(8)} Thanks N.Khoury -----Original Message----- From: midrange-l-bounces+nageeb=khoury.com@xxxxxxxxxxxx [mailto:midrange-l-bounces+nageeb=khoury.com@xxxxxxxxxxxx] On Behalf Of Patrick Botz Sent: Thursday, February 10, 2005 1:51 AM 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 TN5250e protocol lacks any way for the client to know when to send SHA or DES. This is because the password substitute protocol you are referring to was invented for use only with Client Access/iSeries Access bypass-signon. Since that client requires a license, it's already made other connections/flows to the iSeries and discovered the host password level along the way. The current solution/hacks are: - make a seperate connection to any iSeries Access server and send the seed flow (28 bytes), the returning host seed flow (28 bytes) also contains the QPWDLVL bit. Then you can cache this or discover it each time. - require all iSeries to move up to SHA - use kerberos instead Patrick Botz -- 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. -- 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. -- 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. -- 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. -- 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.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 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].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.
midrange.com
