RE: OCL36 EVOKE vs JOBQ

- are you asking about the current S36 environment implementation, or the
original S36 system or the M36 (which was like the orig s36) ?

As others have said, jobq is putting a job into a single thread queue,
whether in S36 environment under IBM I or an actual S36.
// JOBQ lets you set a priority in the same way a SBMJOB has the JOBPTY
parameter which is the priority in the queue.
// JOBQ also allows you to set the current library or a specific library, as
well as identify the procedure name and parameters.

// EVOKE is similar but in S36 environment, is submitted to a multi thread
jobq (QS36EVOKE)

If you look at a system with s36 stuff on it, you will see

Subsystem description: QBATCH

Seq Job Max
Nbr Queue Library Active
10 QBATCH QGPL 1
20 QS36EVOKE QGPL *NOMAX

If you want more flexibility in S36 procedures (in S36 Environment), just
run a SBMJOB command -native commands are supported


Jim Franz

-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxxxxxxxx] On Behalf Of
Justin Taylor
Sent: Thursday, June 13, 2019 5:05 PM
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxxxxxxxx>
Subject: OCL36 EVOKE vs JOBQ

I'm trying to determine the difference between these two OCL36 commands:
EVOKE and JOBQ. From what I've found on Google, they both appear to be like
SBMJOB. Does anyone know the difference between them?

TIA
--