ZOS Agent submits job with wrong user if 2 jobs are started short after each other,
Article ID: 268097
Updated On:
Products
Issue/Introduction
ZOS Agent submits job with wrong user if 2 jobs are started short after each other (in interval less than 1 second). The second job is started with the user from the login object of the first jobs.
After restarting the failed job, the correct user is used, and job starts.
1. Job1 Z_GVOD80_JOB (RunID: 15909585) is started and runs normally using User "ERNEST" that's fine
2. Job2 Z_ADVE1501_JOB RunID: (15897437) is started short after, and should be submitted as user "HEMINGWAY" the User is also defined defined in the login object, but the Submitter in its JESLOG is "ERNEST" which is wrong.
Extracted from the Agent logs:
20230424/201419.463 - U02000005 Job 'Z_ADVE1501_JOB' with RunID '15897437' is to be started. 20230424/201419.496 - U02000003 Job 'Z_ADVE1501_JOB' started with RunID '15897437'. 20230424/201419.496 - U02000005 Job 'Z_GVOD80_JOB' with RunID '15883112' is to be started. 20230424/201419.514 - U02000003 Job 'Z_GVOD80_JOB' started with RunID '15883112'. 20230424/201427.161 - U02000008 Job 'Z_ADVE1501_JOB' with RunID '15897437' ended normally. 20230424/201428.619 - U02002042 Job 'Z_ADVE1501_JOB' with RunID '15897437' has been removed from the internal job table. 20230424/201539.209 - U02005057 Job 'Z_GVOD80_JOB' with JobID '15883112' has vanished. 20230424/201539.563 - U02005057 Job 'Z_GVOD80_JOB' with JobID '15883112' has vanished. 20230424/201539.606 - U02002042 Job 'Z_GVOD80_JOB' with RunID '15883112' has been removed from the internal job table.
Z_GVOD80_JOB ended as vanished. In the JES output
DJESMSGLG JES2 JOB12171GVOD80 FRANK 0000000013KRANK.GVOD80.JOB12171.D0000002.JESMSGLG 1 J E S 2 J O B L O G -- S Y S T E M OBPSYS -- N O D E A 0 0 0 1 0 20.14.19 JOB12171 ---- MONDAY, 24 APR 2023 ---- 20.14.19 JOB12171 ICH408I USER(HEMINGWAY ) GROUP(APRGKRAN) NAME(BATCHUSER KRANK ) SUBMITTER(ERNEST ) LOGON/JOB INITIATION - SUBMITTER IS NOT AUTHORIZED BY USER -$HASP106 JOB DELETED BY JES2 OR CANCELLED BY OPERATOR BEFORE EXECUTION 0------ JES2 JOB STATISTICS ------ 0 43 CARDS READ 0 13 SYSOUT PRINT RECORDS 0 0 SYSOUT PUNCH RECORDS 0 0 SYSOUT SPOOL KBYTES 0 0.00 MINUTES EXECUTION TIME
The user KRANK is defined in the login object "Z_GVOD80_JOB" but the job was submitted with user ERNEST defined in the login object of Z_ADVE1501_JOB
Both Jobs are of the AE type (JCL + Job Card in AE)
The JCL are submitted via includes (INC)
askracf is set to 0
Some customer reported that the problem occurs when two jobs are executed very rapidly one after the other. The second job will be submitted with the user submitting the previous job.
Environment
Release : Z/OS Agent 21.0.4 HF1
Cause
This is a defect of the Z/OS Agent
Resolution
Resolution : A problem has been solved where a job was executed with a user other than the one defined in the Login object.
This bug is fixed and the fix will come with version 21.0.9 which is currently planned for the first quarter of 2024
Additional Information
The bug is referenced as
Bug ID : AE-32406
Bug Title : ZOS Agent submits job with wrong user if 2 jobs are started short after each other, after restarting the failed job, the correct user is used, and job starts
Feedback
