Observed ACF01030 LOGONID error message. How can this be mitigated.

Products

• ACF2 - z/OS
• ACF2 - MISC

Issue/Introduction

Error message observed in the joblog.

- ACF01030
          LOGONID xxxxxxx HAS THE STC ATTRIBUTE AND CANNOT BE USED FOR NORMAL ACCESS

Environment

Release : 16.0

Component : ACF2 for z/OS

Resolution

To address the ACF01030 message, sites can define GSO STC records for the propagator tasks to assign the task it's own logonid. 

This GSO / STC record allows you to assign a different logonid (without the STC privilege) to a started task different from the procname.

Another feature of this GSO /STC  record is that the new logonid you associate with the started task does not have to have the STC bit,
yet ACF2 will still allow it to be used (this is the only place ACF2 makes an exception). 

For example if the propagator's address space logonid is IDSTC1 you can create a GSO STC record that assigns the IDSTC1 lid to the IDSTC1 address space:             

ACF
SET CONTROL(GSO)                                                              
INSERT STC.IDSTC1 STCID(IDSTC1) LOGONID(IDSTC1)                             

Then:                                                                         
F ACF2,REFRESH(STC)    

This change assign's the IDSTC1 logonid to the propagator's address space so the STC has a lidrec that does not contain the STC attribute and the
message ACF01030 will not be generated when a VERIFY call is issued.

The GSO STC record bypasses the check, that ensures a started task lid has the STC attribute.

Additional Information

Details on the ACF2 GSO STC record can be found in the section 'Started Task (STC)'.