home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!know!hri.com!ukma!darwin.sura.net!paladin.american.edu!auvm!ISUMVS.BITNET!GG.WSF
- From: GG.WSF@ISUMVS.BITNET (Bill Frazier)
- Newsgroups: bit.listserv.ibm-main
- Subject: RACF and password preservation
- Message-ID: <IBM-MAIN%92101615245739@RICEVM1.RICE.EDU>
- Date: 16 Oct 92 20:22:19 GMT
- Sender: IBM Mainframe Discussion list <IBM-MAIN@RICEVM1.BITNET>
- Lines: 23
- Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
-
- I'm sorry that I've lost the original reference for quoting
- purposes. The question regards password continuity for existing
- users on conversion to RACF.
-
- We run MVS/XA and are now at a 1.9.x version of RACF. We went
- through the conversion process some time ago and had to address this
- problem. As far as I have been able to determine, when you use any
- of the administrative paths provided for setting passwords, the
- password will be created expired and will hence require changing on
- first use. I have written code to circumvent this. It can be done
- using ICHEINTY to update the password and set the last change date
- appropriately. Even if you use DES, this will still work because
- the ICHEINTY interface will properly encrypt what you are passing
- in. I'm sorry that I cannot share the code because it was not stand
- alone but part of things I wrote for our WYLBUR system.
-
- I strongly encourage the use of simple test case programs if you are
- going to do database editing using ICHEINTY. No matter how well you
- think you are at pointing the gun, your foot WILL be in the way.
- The documentation on this interface is not always the clearest,
- although it has improved much since we installed at 1.8.
-
- Bill Frazier
-