Gee, who in the first place decided to use numeric userids, possibly
supported by ACF2, but not by the rest of MVS? Sounds like allowing
Syncsort options and then return to DFSORT, or allow PDSFAST options and
then return to IEBCOPY or...

If you did already prefix the userid with an Alpha character, can't you
definitely change the userid to that prefixed value? It won't make any
difference for the datasets, only the users have to get used to their
'new' userid, which they already know from their datasets?

Kees.

"Mark Wilson" <[EMAIL PROTECTED]> wrote in message
news:<[EMAIL PROTECTED]>...
> Cross Posted to RACF-L and re posted to IBM Main
> 
> Could anybody offer any ideas at all in this area?
> 
> Regards
> 
> Mark
>  
>
************************************************************************
****
> **********************************************************************
> 
> Hi,
> 
> I am in the middle of migrating a customer from ACF2 to RACF and have
> encountered a problem.
> 
> ACF2 supports the use of fully numeric TSO Userids.
> 
> The customer has an exit in place that forces all dataset allocations
to be
> prefixed with a Alpha character, getting around the dataset issues.
> 
> However, if I migrate them to RACF, TSO does NOT support a fully
numeric
> Userid.
> 
> I know this is not supported by IBM, but does anyone have any ideas
(TSO
> exit?), that I can use to support fully numeric TSO Userids.
> 
> The customer does not what to change the RACF Userids to start with an
alpha
> character for business/application reasons.
> 
> Any help gratefully received.
> 
> Regards,
> 
> Mark
> 
> ----------------------------------------------------------------------
> 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
> 
**********************************************************************
For information, services and offers, please visit our web site:
http://www.klm.com. This e-mail and any attachment may contain
confidential and privileged material intended for the addressee
only. If you are not the addressee, you are notified that no part
of the e-mail or any attachment may be disclosed, copied or
distributed, and that any other action related to this e-mail or
attachment is strictly prohibited, and may be unlawful. If you have
received this e-mail by error, please notify the sender immediately
by return e-mail, and delete this message. 

Koninklijke Luchtvaart Maatschappij NV (KLM), its subsidiaries
and/or its employees shall not be liable for the incorrect or
incomplete transmission of this e-mail or any attachments, nor
responsible for any delay in receipt.
Koninklijke Luchtvaart Maatschappij N.V. (also known as KLM Royal
Dutch Airlines) is registered in Amstelveen, The Netherlands, with
registered number 33014286 
**********************************************************************

----------------------------------------------------------------------
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

Reply via email to