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

Previous Topic: ACF2 and TSS Account Templates Created in the User Console Do Not Support User-Defined Fields

Next Topic: Field with Parentheses Could Appear Out of Sync
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.