Using INFO Print Server (AOP Printing) gets unexpected ACF2 violations for user = *NONE*

Products

• ACF2
• ACF2 - z/OS
• ACF2 - MISC

Issue/Introduction

Using INFO Print Server (AOP Printing) gets unexpected ACF2 violations for user = *NONE*. What can be done to address the violation?

Resolution

The error can be caused by RACROUTE VERIFY call issued from an address space with no USERID or a null USERID (RACROUTE call with USER=*NONE*) and there is no ACF2 batch default LOGONID specified.

Message "ACF01097 NO USERID SPECIFIED ON SYSTEM ENTRY VALIDATION REQUEST" can also be a symptom.

The ACF01097 message states:

ACF01097 NO USERID SPECIFIED ON SYSTEM ENTRY VALIDATION REQUEST
REASON: No Userid was supplied on the system entry validation request and no default LOGONID was available.

The violation for *NONE* is caused by a RACROUTE REQUEST=VERIFY with no USERID specified. This would normally cause the default logonid to be used. If there is no default logonid defined you will get this error.

To establish a default LOGONID for this region, MUSDLID(xxxxxxxx) can be specified on the region LOGONID. Then define LOGONID xxxxxxxx with the required authority in the ACF2 logonid database.

The MUSDLID description from the ACF2 documentation states:

MUSDLID(logonid)
Specifies the default logonid for a multiple-user single address space system (MUSASS) address space. The logonid specified does not need the MUSASS attribute. Currently, this field is used only for SAF. (eight characters)