RE: CA/400 CWBLM0006 message

This could explain why they are shipping new systems with QMAXPWDLEN set
to 8.
I though it had to do with mainframe compatibility - haven't seen it
documented anywhere re CA/400. 

... Neil Palmer                                     AS/400~~~~~      
... NxTrend Technology - Canada     ____________          ___  ~     
... Thornhill, Ontario,  Canada     |OOOOOOOOOO| ________  o|__||=   
... Phone: (905) 731-9000  x238     |__________|_|______|_|______)   
... Cell.: (416) 565-1682  x238      oo      oo   oo  oo   OOOo=o\   
... Fax:   (905) 731-9202         ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 
... mailto:NPalmer@NxTrend.com          http://www.NxTrend.com


        -----Original Message-----
        From:   Steve Glanstein [SMTP:mic@aloha.com]
        Sent:   Saturday, January 03, 1998 7:23 PM
        To:     Steve Glanstein; Mark Lazarus; Liu Kean Keong; Neil
Palmer; mr; David Mahadevan
        Subject:        RE:  CA/400 CWBLM0006 message

        Gentlemen:

        Here's the current status of this CWBLM0006 dilemna.  I was able
to connect
        via TCP/IP and install the latest service pack (SF45545).  Same
results
        were received.

        I ran several communication traces and found out some things
that make the
        SNA connection work.

        First, a little background info.  This AS/400 is at security 50
with the
        audit journal enabled as well as a network journal that logs all
client
        access requests.  This logging is a great diagnostic aid to see
if we even
        get to the exit program area.  Also, authority errors can be
detected and
        corrected quickly.

        My personal passwords have always been an unmemorizable 10
        characters/numbers, different for each client as well as the
network area. 
        One set is all powerful and the other set is normal.  Access to
CA/400 has
        been at the lowest tolerable level, though. (limited capability
user
        profile who can't do anything)  Password caching is not done for
obvious
        reasons.

        It appears that use of a password of more than eight characters
somehow
        corrupts the BIND that is performed when an attempt is made to
start a 5250
        session.  This generates the CPF1269 error message with a 2021
qualifier. 
        This says a startup attempt was made without a password.  I'm
not sure if
        this relates to the first USE of client access for the AS/400 of
FROM a PC,
        but the communications trace certainly has familiar sense
code-080F6051. 
        The audit journal is not consistent and is usually silent at
this point.

        More later...if anybody has experienced this problem with longer
passwords,
        please let me know.



+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to "MIDRANGE-L@midrange.com".
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---