Mark Wilson wrote:
However, if I migrate them to RACF, TSO does NOT support a fully numeric Userid.
The closest you could come is to maintain an all-numeric logon in a pre-logon exit (examples on the CBT), and convert that to an id acceptable by TSO and RACF internally. If the clients run special software without direct TSO use, this could maintain transparency for them.
(There is of course the alternative of intercepting all terminal I/O, identifying the user ids, and changing them, but I wouldn't seriously recommend that)
A long time ago we had numeric account numbers, and (for billing) decided to use them as part of data set names. We translated A-I to 1-9, and 0 to Z. That worked quite well, but didn't suffer from the TSO userid restrictions.
Gerhard Postpischil Bradford, VT ---------------------------------------------------------------------- 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
