Paul Gilmartin wrote:
But now, I'm thoroughly mystified. If "RACF didn't fold the password" (I'll trust your knowledge of the chronology), how can a signature that RACF derived from a mixed-case password fail when that same mixed-case password is passed to RACROUTE VERIFY, but succeed if the caller folds the password.
I suspect that the ADDUSER, ALTUSER and PASSWORD commands relied upon the default behavior of TSO/E parsing services to uppercase the password values. Likewise, the ISPF panels likely relied on the default behavior of input fields (CAPS(ON)) to uppercase the password values.
Remember, in the old days, everything was uppercase. Nobody wanted to see or deal with lowercase. There was even a blue toggle switch on the front of the 3278s to fold the characters displayed on the screen!
-- Edward E Jaffe Phoenix Software International, Inc 5200 W Century Blvd, Suite 800 Los Angeles, CA 90045 310-338-0400 x318 [email protected] http://www.phoenixsoftware.com/ ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
