Release Notes › Known Issues › Endpoint Types › ACF2, RACF, and CA Top Secret › RACF Backend Code Does Not Allow Non-ASCII Characters Entered into Account Names

Previous Topic: CA LDAP Server for z/OS must have Appropriate Maintenance Applied before Using the RACF Connector or Using the Create/Delete Alias Processing in r12.0 and Beyond

Next Topic: ACF2 connector problem with CA LDAP r12
RACF Backend Code Does Not Allow Non-ASCII Characters Entered into Account Names

To resolve this issue, contact CA Support to request updated mainframe binaries.