[prev in list] [next in list] [prev in thread] [next in thread] 

List:       racf-l
Subject:    Re: [EXTERNAL] Re: RACF =- Max number of Users
From:       Mark Jacobs <00000abbff4629b6-dmarc-request () LISTSERV ! UGA ! EDU>
Date:       2022-04-19 20:52:12
Message-ID: 9bB0HHOqTIL_zEUp_Hbl084hlm8gvXZy4yPhFohQ_eNdLe8cdQkXYhRweuAYyyBTxU57AL7i08S0kRK-9c_dySIDSGuAGrSyp4e5XvqUBnI= () protonmail ! com
[Download RAW message or body]

39 + 39^2 + 39^3 + 39^4 + 39^5 + 39^6 + 39^7 + 39^8 == 5,492,851,609,440

Mark Jacobs


Sent from ProtonMail, Swiss-based encrypted email.

GPG Public Key - https://api.protonmail.ch/pks/lookup?op=get&search=markjacobs@protonmail.com


Sent with ProtonMail secure email.
------- Original Message -------
On Tuesday, April 19th, 2022 at 4:40 PM, David Spiegel <dspiegelcan@HOTMAIL.COM> \
wrote:


> Hi Charles,
> 39 1-character IDs, 392 2-character IDs, 393 3-character IDs ...
> 397 7-character IDs and (finally) 398 8-character IDs.
> N'est-ce pas?
> 
> On 2022-04-19 16:02, Charles Mills wrote:
> 
> > Also somewhat more than 39^8 because of shorter userid's. Steam is coming out of \
> > my ears trying to do the arithmetic but in addition to 39^8 eight-character IDs \
> > there are 39 one-character IDs, 39^2 two-character IDs, and so forth. 
> > Charles
> > 
> > -----Original Message-----
> > From: RACF Discussion List [mailto:RACF-L@LISTSERV.UGA.EDU] On Behalf Of Pommier, \
> >                 Rex
> > Sent: Tuesday, April 19, 2022 12:10 PM
> > To: RACF-L@LISTSERV.UGA.EDU
> > Subject: Re: [EXTERNAL] Re: RACF =- Max number of Users
> > 
> > Charles,
> > 
> > Nope, I thought the same thing so I went to my sandbox and built a userID of \
> > 1234567Z and it took. :-) 
> > Rex
> > 
> > -----Original Message-----
> > From: RACF Discussion List RACF-L@LISTSERV.UGA.EDU On Behalf Of Charles Mills
> > Sent: Tuesday, April 19, 2022 1:52 PM
> > To: RACF-L@LISTSERV.UGA.EDU
> > Subject: [EXTERNAL] Re: RACF =- Max number of Users
> > 
> > This is Friday silliness, but doesn't the first character have to be non-numeric? \
> > So 29 * 39^7? 
> > You probably hit database size issues first. How much space in the RACF DB does \
> > one userid take up? What is the maximum size for a RACF DB? 
> > In answer to the OP, yes, there is surely some limit, but you probably won't hit \
> > it. 
> > This was kicked around on IBM-MAIN in January and Attila Fogarsi posted
> > 
> > I know of RACF/ACF2/TSS databases with over 1 million userids, <1% of these would \
> > be used for TSO logon however. I would expect there are systems with over 10 \
> > million userids. In the past IBM has released benchmarks of z/OS with over \
> > 100,000 concurrently active network connections, and that would be much larger \
> > for current hardware. 
> > Charles
> > 
> > -----Original Message-----
> > From: RACF Discussion List [mailto:RACF-L@LISTSERV.UGA.EDU] On Behalf Of David \
> >                 Spiegel
> > Sent: Tuesday, April 19, 2022 11:11 AM
> > To: RACF-L@LISTSERV.UGA.EDU
> > Subject: Re: RACF =- Max number of Users
> > 
> > Hi Juan,
> > 368 is incorrect, because, you forgot about the 3 national characters:
> > @, #, $.
> > So, it should've been 398.
> > 
> > Regards,
> > David
> > 
> > On 2022-04-19 13:59, Mautalen Juan Guillermo wrote:
> > 
> > > No. The only limit (in this respect) is given by the RACF database size.
> > > 
> > > Juan G. Mautalen
> > > 
> > > PD: a precise mathematical answer is indeed YES, because userids being 8 \
> > > alphanumeric characters (or less), their limit is indeed around 36^8. :-)
> > > 
> > > -----Mensaje original-----
> > > De: RACF Discussion List RACF-L@LISTSERV.UGA.EDU En nombre de
> > > Solange Fernanda Ricci Enviado el: martes, 19 de abril de 2022 14:24
> > > Para: RACF-L@LISTSERV.UGA.EDU
> > > Asunto: [RACF-L] RACF =- Max number of Users
> > > 
> > > CUIDADO: Este correo electrónico se originó fuera de la ANSES. No haga clic \
> > > en enlaces / links, ni abra los adjuntos salvo que sepa que el contenido es \
> > > seguro. 
> > > Hello , good afternoon !
> > > 
> > > Please, s there a maximum number of users that we can define in RACF ?
> > > I don't think so , but I would like to confirm with you.
> > > 
> > > Thank you,
> > > Solange Ricci
> > > 
> > > El contenido del presente mensaje y sus anexos es privado, confidencial y de \
> > > exclusivo uso para el destinatario referenciado. Puede contener informacion \
> > > privilegiada o amparada por el secreto profesional o por disposiciones legales \
> > > y/o reglamentarias vigentes. Cualquier modificacion, retransmision, \
> > > diseminacion o divulgacion de su informacion se encuentra expresamente \
> > > prohibida y su uso inadecuado puede derivar en responsabilidad civil para el \
> > > usuario o configurar los delitos previstos en los articulos 153 a 157 del \
> > > Codigo Penal. Si no fuere uno de los destinatarios consignados o lo hubiere \
> > > recibido por error, Ud. NO ESTA AUTORIZADO a utilizar total o parcialmente, \
> > > copiar, enviar, revelar, imprimir, divulgar de manera alguna el contenido del \
> > > presente mensaje o el de sus adjuntos. En consecuencia, tenga a bien \
> > > comunicarselo inmediatamente al emisor y ELIMINARLO. ANSES no garantiza la \
> > > seguridad, integridad, exactitud u oportunidad de lo transmitido por este medio \
> > > ni se responsabiliza de posibles perjuicios derivados de la captura, \
> > > incorporaciones de virus o cualquier otra manipulación efectuada por terceros. \
> > > Asimismo, las opiniones expresadas en este mensaje y en los archivos adjuntos \
> > > son propias del remitente y no representan la opinion o politicas de ANSES, \
> > > salvo que se diga expresamente y el remitente se encuentre autorizado para \
> > > ello. Por ende, ANSES no asumira -en ningun caso- responsabilidad alguna frente \
> > > al destinatario y/o terceros en virtud de dichas comunicaciones y ademas, no \
> > > sera responsable frente a los usuarios por la correspondencia o los mensajes de \
> > > correo electronico enviados por terceros u otras personas distintas a ANSES, ya \
> > > sea que estos hubieren o no solicitado el envio de tales mensajes. ANSES se \
> > > reserva el derecho de bloquear el acceso o remover en forma parcial o total \
> > > todo mensaje y sus adjuntos que a su criterio pudiere resultar abusivo, \
> > > difamatorio, obsceno, fraudulento, artificioso, engañoso, ofensivo o \
> > > violatorio a los terminos de la presente. PD: Tildes omitidas intencionalmente.
> > 
> > ----------------------------------------------------------------------
> > The information contained in this message is confidential, protected from \
> > disclosure and may be legally privileged. If the reader of this message is not \
> > the intended recipient or an employee or agent responsible for delivering this \
> > message to the intended recipient, you are hereby notified that any disclosure, \
> > distribution, copying, or any action taken or action omitted in reliance on it, \
> > is strictly prohibited and may be unlawful. If you have received this \
> > communication in error, please notify us immediately by replying to this message \
> > and destroy the material in its entirety, whether in electronic or hard copy \
> >                 format. Thank you.
> > .


[prev in list] [next in list] [prev in thread] [next in thread]