Jobs submitted scheduler with //*LOGONID inherits the scheduler logonid
search cancel

Jobs submitted scheduler with //*LOGONID inherits the scheduler logonid

book

Article ID: 259703

calendar_today

Updated On:

Products

ACF2 - z/OS

Issue/Introduction

Installed the TWS job scheduler in a new zD&T system. Everything is working fine, but the correct logonid(owner ID) is not being assigned to the jobs. The logonid is provided in the JCL using the //*LOGONID card.

Environment

Release : 16.0

Resolution

When using the //*LOGONID card when the jobs runs the JESJCL will show the //LOGONID card modified where LOGONID is changed to L0G0NID(character 'O' replaced by numeric zero '0') and the logond replaced with the text '$ACFJ201 ACF2 CONTROL CARD SUCCESSFULLY SCANNED" as shown in the following example:

1 //ACFBATCH JOB 9999100000,CLASS=A,NOTIFY=USER002,MSGCLASS=X          
//* ACF01137 USER001 LAST SYSTEM ACCESS 00.00-00/00/00 FROM SYSX
  //*L0G0NID $ACFJ201 ACF2 CONTROL CARD SUCCESSFULLY SCANNED          
2 //ACFBATCH EXEC PGM=ACFBATCH                                        
3 //SYSOUT   DD SYSOUT=*                                              
4 //SYSPRINT DD SYSOUT=*   

The JESJCL provided shows:

//TESTTEST JOB 099990000099,'TEST ',CLASS=D,MSGCLASS=F 
  //*LOGONID USR00000                                                   
//*                                                                   
//*          UPDATED ON 24-11-78                                    
  //*                                                                   
  //*                                                                   
2 //STEP1    EXEC PGM=IEFBR14       

Based on the above the //*LOGONID is not being processed by the ACF2/JES2 interface. This can be caused by any of the following.

  1. The ACF2/JES2 interface was not assembled and linked with the correct z/OS libraries when upgrading to a new version of z/OS or when deploying ACF2 to a new system. The ACF2 JXBUMJ2 job in the ACF2 installation library CAX1JCL0 can be used to re-assemble and link the ACF2/JES2 interface.

  2. The required ACF2/JES2 exits are not enabled. The console command $DEXIT(*) can be used to list and verify that the following ACF2/JES2 exits are enabled.

    EXIT2         ROUTINE=ACFEXIT2
    EXIT4         ROUTINE=ACFEXIT4
    EXIT20        ROUTINE=ACFEXT20
    EXIT24        ROUTINE=ACFEXT24
    EXIT26        ROUTINE=ACFEXT26
    EXIT31        ROUTINE=ACFEXT31
    EXIT34        ROUTINE=ACFEXT34
    EXIT46        ROUTINE=ACFEXT46
    EXIT50        ROUTINE=ACFEXT50
    EXIT52        ROUTINE=ACFEXT52
    EXIT54        ROUTINE=ACFEXT54
    EXIT56        ROUTINE=ACFEXT56
    EXIT225       ROUTINE=ACFEX225