No that is not expected behavior. You need to look again.
DSPOBJD OBJ(*LIBL/SBMJOB) OBJTYPE(*CMD)
to ensure that you're looking at the highest one in the library list (they
may have modified QSYSLIBL).
Also make sure you don't have two job descriptions with the same name, but
in different library lists.
Make sure the job list is incorrect and not just missing (or not
authorized).
Cause . . . . . : Job 188284/ROB/QDFTJOBD submitted to job queue QBATCH
in
QGPL from job 188275/ROB/ROBS3. Job 188284/ROB/QDFTJOBD was started
using
the Submit Job (SBMJOB) command with the following job attributes:
JOBPTY(5
OUTPTY(5) PRTTXT() RTGDTA(QCMDB) SYSLIBL(QSYS QSYS2 QHLPSYS
QUSRSYS) CURLIB(ROB) INLLIBL(QTEMP QGPL) INLASPGRP(*NONE) LOG(4 00
*SECLVL) LOGCLPGM(*NO) LOGOUTPUT(*PND) OUTQ(/*DEV) PRTDEV(P2)
INQMSGRPY(*RQD) HOLD(*NO) DATE(*SYSVAL) SWS(00000000) MSGQ(QUSRSYS/ROB)
CCSID(37) SRTSEQ(*N/*HEX) LANGID(ENU) CNTRYID(US) JOBMSGQMX(64)
JOBMSGQFL(*PRTWRAP) ALWMLTTHD(*NO) SPLFACN(*KEEP) ACGCDE(1600 - 09651).
Rob Berendt
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact
[javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.