TSS0211E ACCESSOR-ID MISSING OR INVALID
search cancel

TSS0211E ACCESSOR-ID MISSING OR INVALID

book

Article ID: 21754

calendar_today

Updated On:

Products

Cleanup Datacom DATACOM - AD CIS COMMON SERVICES FOR Z/OS 90S SERVICES DATABASE MANAGEMENT SOLUTIONS FOR DB2 FOR Z/OS COMMON PRODUCT SERVICES COMPONENT Common Services CA ECOMETER SERVER COMPONENT FOC Easytrieve Report Generator for Common Services INFOCAI MAINTENANCE IPC UNICENTER JCLCHECK COMMON COMPONENT Mainframe VM Product Manager CHORUS SOFTWARE MANAGER CA ON DEMAND PORTAL CA Service Desk Manager - Unified Self Service PAM CLIENT FOR LINUX ON MAINFRAME MAINFRAME CONNECTOR FOR LINUX ON MAINFRAME GRAPHICAL MANAGEMENT INTERFACE WEB ADMINISTRATOR FOR TOP SECRET Xpertware Top Secret Top Secret - LDAP Top Secret - VSE

Issue/Introduction

Previously creating acids with an asterisk (*) at the end (example PROFADM*) worked without a problem. 

Now you are receiving the following error message:

TSS CREATE(USERID*) DEPT(DEPT1) NAME() PASSWORD(USERID)
TSS0211E ACCESSOR-ID MISSING OR INVALID
TSS0301I CREATE FUNCTION FAILED, RETURN CODE = 4

 

Environment

Release: TOPSEC00200-15-Top Secret-Security
Component:

Resolution

The code in TSS 15.0 was changed as follows:

Top Secret documents that allowable characters for an ACID name are a-z, 0-9, and national characters ($,#,@,%,&,=,?).
Other characters may cause unpredictable results and are not supported.
TSS 15.0 added checks during the CREATE of an ACID to verify that unsupported characters are not used.

The asterisk '*' should not have been allowed in prior releases of TSS.

TSS r15 has fix RO32792 that deals with some of the special characters in an acid, however, the only characters allowed as a result RO32792 are the three mentioned:

'_' '-' and '+'.

The '*' is no longer allowed in an acid name.