Can an STC logonid in ACF2 be used for a batch job or for inheritance to a batch job?

Products

• ACF2
• ACF2 - DB2 Option
• ACF2 for zVM
• ACF2 - z/OS
• ACF2 - MISC

Issue/Introduction

Can an STC logonid in ACF2 be used for a batch job or for inheritance to a batch job?

Environment

Release:
Component: ACF2MS

Resolution

An ACF2 logonid with the STC attribute cannot submit batch jobs or inherit a batch job. Attempting to do so will cause the job to run under the batch default logonid. If a batch default is not specified, the job will fail.

However, the STC attribute can be removed from the logonid and a GSO STC record can be created to associate the logonid with a started task id. This will allow the id to both be used for a started task and to submit jobs provided the logonid is given the JOB attribute. 

Note that the STC region will need to be re-started for the logonid change to take effect. Since this logonid can now be used for batch, consider adding other restrictions to the logonid record such as PROGRAM, SUBAUTH, SOURCE, or even a password. When started as a started task, the password is not checked.

Example of creating a GSO STC record:

SET C(GSO)
INSERT STC.STCBATCH LOGONID(STCBATCH) STCID(STCBATCH)
F ACF2,REFRESH(STC)

To remove the STC attribute:

SET LID
CHANGE STCBATCH NOSTC

STCBATCH           GLSTCOPSTCBATCH       NAME(STC BATCH LID)
                               CO(STC) DEPT(GL) SITE(OP) ) 
PRIVILEGES          CREATE(02/18/16) DUMPAUTH JOB NON-CNCL