I'm getting a blank jobclass and *NOT-AVAILABLE* for submitter when processing the $HASP375 while a job is executing. Is this because of the WLM initiator being used or am I having a problem?
MVS2LOG is my debugging WTO.
var = OPSINFO('SUBMITTER')
Returns the user ID that submitted the current job. If the primary job entry subsystem is not JES2,
or JES2 is not active when this function is called, the SUBMITTER function returns a 15-character
data string instead of data: *NOT-AVAILABLE*
$HASP375 SIL90750 ESTIMATE EXCEEDED BY 10,000 LINES
MVS2LOG MSG.$HASP375 JC=,sub=*NOT-AVAILABLE*,secusr=$STCWGS,jobtyp=SCHD2..
SIL90750 was JOB52930
J E S 2 J O B L O G -- S Y S T E M XXXX -- N O D E XXXXXX
--- THURSDAY, 03 OCT 2019 ----
$HASP9551 zOSEM VER 6.2 - JOBROUTING ACTIVE FOR JES2 ON XXXX
$HASP9542 JOB123(JOB52930) * -- RESOURCE ROUTING = DB2I --
IRR010I USERID $STCWGS IS ASSIGNED TO THIS JOB.
$HASP9571 zOSEM VER 6.2 - JCL CONVERTED BY JES2 ON XXXX
$HASP9550 JOB123(JOB52930) * -- JOBROUTE RULE048 SCHENV = PRODJOB --
$HASP9550 JOB123(JOB52930) * -- JOBROUTE RULE080 ROUTING = SAS --
$HASP9550 JOB123(JOB52930) * -- JOBROUTE SET SYSAFF = ANY --
ICH70001I $STCWGS LAST ACCESS AT 09:28:51 ON THURSDAY, OCTOBER 3, 2019
$HASP373 JOB123 STARTED - WLM INIT - SRVCLASS BATPSTD - SYS ATCL
Release : 13.0
Component : OPS/MVS
Job initiators for WLM-managed job classes are controlled dynamically by workload management. These
initiators run under the Master Subsystem and are not assigned JES2 job numbers. WLM can adjust the
number of initiators on each system based on:
• The queue of jobs awaiting execution in WLM managed classes.
• The performance goals and relative importance of this work.
• The success of meeting these goals.
• The capacity of each system to do more work
Since there is no job number the control block that has the submitter does not exist, thus the NOT-AVAILABLE
OPS/MVS gets the jobclass from the SJB jes2 control block, if there was none for the job at the time (as is the case in WLM managed initiators) it would be null.