Walt, no one's beating you up! RACF and MVS are wonderful products. I would support Gil's contention that TSO does "it" - "it" being notifying the user of the state of his account. Yes, yes, it gets the information from RACF (or some other SAF-compliant sub-system, no?). But whatever - the TSO-RACF partnership does it, okay?
> (gil) mentioned automated applications that can't respond to an expired > password properly. It is not obvious that they would be able to respond > to a password warning, either. True, but the user might. The user might at least have a prayer of seeing a message that said "your password will expire in nn days" and doing something about it before jobs started failing - perhaps critical (to the user, at least) jobs failing after the user had gone home for the day. Again, no one is beating RACF up. MVS evolved the way it did. I understand that every decision made sense at the time it was made. Charles -----Original Message----- From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of Walt Farrell Sent: Wednesday, September 13, 2006 2:26 PM To: IBM-MAIN@BAMA.UA.EDU Subject: Re: Password expiration message? On 9/13/2006 4:03 PM, [EMAIL PROTECTED] wrote: > This is one of the mystifying things about MVS (there are others). > Why does it take a Papal decree to find the state of one's account? > TSO logon does it readily enough. Sorry, but TSO logon does -not- do it. RACF does it. > This information ought to be > available via a callable service, as readily to any program in > any environment, such as the FTP "230" message text, as it is to > TSO logon. What were the designers thinking? Were they thinking > much at all? Tunnel vision? ("Why would a TSO user _ever_ want > to use an MVS service except via LOGON to TSO?") When we started all this, there were NO other applications that supported RACF except batch jobs and TSO. Remember, you're asking about processing that is, effectively, 30 years old. (We'll be celebrating that birthday on Sept. 24.) ... Of course, this will to some extent depend on what the application can pass back (some protocols may not allow for additional info), and even if the application can pass it back (ftp, for example) that might not completely resolve the problem. Earlier in this thread I think you (gil) mentioned automated applications that can't respond to an expired password properly. It is not obvious that they would be able to respond to a password warning, either. ---------------------------------------------------------------------- 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
