No WLM init's, yet job running in one ?

[Joe Ellis]

we stumbled acrsoo some jobs executing in a WLM init -
$HASP373 CF2PIEX2 STARTED - WLM INIT - SRVCLASS SCBATWLM - SYS SYSC

however, we have no wlm init's set up in JES2 , Does anyone have any idea where to look to see how this is happening ?

thanks
Joe

[Tabor, Rich]

$DJnnnn, look for CLASS=x, then issue $DJOBCLASS(x)

-----Original Message-----
From: JES2 discussion group [mailto:JES2-***@listserv.vt.edu] On Behalf Of Joe Ellis
Sent: Tuesday, January 13, 2015 11:19 AM
To: JES2-***@LISTSERV.VT.EDU
Subject: [JES2-L] No WLM init's, yet job running in one ?

we stumbled acrsoo some jobs executing in a WLM init -
$HASP373 CF2PIEX2 STARTED - WLM INIT - SRVCLASS SCBATWLM - SYS SYSC

however, we have no wlm init's set up in JES2 , Does anyone have any idea where to look to see how this is happening ?

thanks
Joe




NOTICE: This email and any attachments are for the exclusive and confidential use of the intended recipient(s). If you are not an intended recipient, please do not read, distribute, or take action in reliance upon this message. If you have received this in error, please notify me immediately by return email and promptly delete this message and its attachments from your computer.

[Joe Ellis]

I should be more specific, I have no MODE=WLM on any jobclass statements in the JES2 inish deck. So, I'm trying to determine if there is any way WLM will 'decide' to run jobs as WLM managed. When the job starts, it doesn't show any jobclass, on one that was canceled, it showed it had been in a class A init, this is the statement for the A class, it defaults to mode=jes2, this is a 1.13 system

JOBCLASS(A) ACCT=NO,
PGMRNAME=NO,
TIME=(1439,59),
REGION=32M,
COMMAND=VERIFY,
BLP=YES,
AUTH=SYS,
MSGLEVEL=(1,1),
JOURNAL=NO,
OUTPUT=YES,
PERFORM=20,
SWA=ABOVE

[Tabor, Rich]

$TJOBCLASS(A),MODE=WLM is all it takes regardless of your init deck. What does the output from your $DJOBCLASS(A) command look like?

-----Original Message-----
From: JES2 discussion group [mailto:JES2-***@listserv.vt.edu] On Behalf Of Joe Ellis
Sent: Tuesday, January 13, 2015 12:20 PM
To: JES2-***@LISTSERV.VT.EDU
Subject: Re: [JES2-L] No WLM init's, yet job running in one ?

I should be more specific, I have no MODE=WLM on any jobclass statements in the JES2 inish deck. So, I'm trying to determine if there is any way WLM will 'decide' to run jobs as WLM managed. When the job starts, it doesn't show any jobclass, on one that was canceled, it showed it had been in a class A init, this is the statement for the A class, it defaults to mode=jes2, this is a 1.13 system

JOBCLASS(A) ACCT=NO,
PGMRNAME=NO,
TIME=(1439,59),
REGION=32M,
COMMAND=VERIFY,
BLP=YES,
AUTH=SYS,
MSGLEVEL=(1,1),
JOURNAL=NO,
OUTPUT=YES,
PERFORM=20,
SWA=ABOVE




NOTICE: This email and any attachments are for the exclusive and confidential use of the intended recipient(s). If you are not an intended recipient, please do not read, distribute, or take action in reliance upon this message. If you have received this in error, please notify me immediately by return email and promptly delete this message and its attachments from your computer.

[Tom Wasik]

The other way a job is run in a WLM mode initiator is if a start job command is issued. That would be something like $S J1234. In this case a WLM initiator is started to run the job (even though there are no MODE=WLM job classes).

And yes, a $D JOBCLASS(*),MODE=WLM would tell you if there are currently any WLM managed initiators. JES2 remembers the last setting of a job class over a warm start so the initialization deck does not matter (unless this is a cold start or in z/OS 2.1 a new job class).

Tom Wasik
JES2 Development

[Joe Ellis]

here are the outputs, I'm getting the syslog from last time i know one ran to see how it got started.

$D JOBCLASS(*),MODE=WLM
$HASP003 RC=(52),D
$HASP003 RC=(52),D JOBCLASS(*) - NO SELECTABLE ENTRIES FOUND
$HASP003 MATCHING SPECIFICATION
$DJOBCLASS(A)
$HASP837 JOBCLASS(A)
$HASP837 JOBCLASS(A) MODE=JES,QAFF=(ANY),QHELD=NO,
$HASP837 SCHENV=,XEQCOUNT=(MAXIMUM=*,
$HASP837 CURRENT=3),
$HASP837 XEQMEMBER(SYSD)=(MAXIMUM=*,
$HASP837 CURRENT=0),
$HASP837 XEQMEMBER(SYSA)=(MAXIMUM=*,
$HASP837 CURRENT=0),
$HASP837 XEQMEMBER(SYSE)=(MAXIMUM=*,
$HASP837 CURRENT=0),
$HASP837 XEQMEMBER(SYSG)=(MAXIMUM=*,
$HASP837 CURRENT=0),
$HASP837 XEQMEMBER(SYSC)=(MAXIMUM=*,
$HASP837 CURRENT=3),
$HASP837 XEQMEMBER(SYSQ)=(MAXIMUM=*,
$HASP837 CURRENT=0)

[Lizette Koehler]

If you could issue the following commands and post the results, it may help.
Also, what is the job CF2PIEX2 do? Is it DB2 or something else?

$D PERFDATA(SAMPDATA)

If you have WLM JES inits - then this should show some data.

Or this command
DISPLAY WLM,SCHENV=*|scheduling_environment

Or $DJ#####,LONG
The display will show what SCHENV is used.

Sometimes the WLM is used due to other reasons: SUBSYS= in JCL for
instance.


Hopes this helps.

Lizette

-----Original Message-----
From: JES2 discussion group [mailto:JES2-***@listserv.vt.edu] On Behalf Of Joe
Ellis
Sent: Wednesday, January 14, 2015 6:24 AM
To: JES2-***@LISTSERV.VT.EDU
Subject: Re: No WLM init's, yet job running in one ?

here are the outputs, I'm getting the syslog from last time i know one ran
to see how it got started.

$D JOBCLASS(*),MODE=WLM
$HASP003 RC=(52),D
$HASP003 RC=(52),D JOBCLASS(*) - NO SELECTABLE ENTRIES FOUND
$HASP003 MATCHING SPECIFICATION
$DJOBCLASS(A)
$HASP837 JOBCLASS(A)
$HASP837 JOBCLASS(A) MODE=JES,QAFF=(ANY),QHELD=NO,
$HASP837 SCHENV=,XEQCOUNT=(MAXIMUM=*,
$HASP837 CURRENT=3),
$HASP837 XEQMEMBER(SYSD)=(MAXIMUM=*,
$HASP837 CURRENT=0),
$HASP837 XEQMEMBER(SYSA)=(MAXIMUM=*,
$HASP837 CURRENT=0),
$HASP837 XEQMEMBER(SYSE)=(MAXIMUM=*,
$HASP837 CURRENT=0),
$HASP837 XEQMEMBER(SYSG)=(MAXIMUM=*,
$HASP837 CURRENT=0),
$HASP837 XEQMEMBER(SYSC)=(MAXIMUM=*,
$HASP837 CURRENT=3),
$HASP837 XEQMEMBER(SYSQ)=(MAXIMUM=*,
$HASP837 CURRENT=0)

[Joe Ellis]

looks like our offshore contractors are doing this :

"The other way a job is run in a WLM mode initiator is if a start job command is issued. That would be something like $S J1234. In this case a WLM initiator is started to run the job (even though there are no MODE=WLM job classes)."

they have 10 class A init's to run in, I observed them submitting jobs and when they don't get picked up immediately because there's a queue of work in class A waiting, , they do $S J1234

Thanks to all for your help !!!

[Davidson, Ivan E. , RET-DAY]

Sounds like you lock down their ability to issue that command.

-----Original Message-----
From: JES2 discussion group [mailto:JES2-***@listserv.vt.edu] On Behalf Of Joe Ellis
Sent: Wednesday, January 14, 2015 9:40 AM
To: JES2-***@LISTSERV.VT.EDU
Subject: Re: No WLM init's, yet job running in one ?

looks like our offshore contractors are doing this :

"The other way a job is run in a WLM mode initiator is if a start job command is issued. That would be something like $S J1234. In this case a WLM initiator is started to run the job (even though there are no MODE=WLM job classes)."

they have 10 class A init's to run in, I observed them submitting jobs and when they don't get picked up immediately because there's a queue of work in class A waiting, , they do $S J1234

Thanks to all for your help !!!

[Davidson, Ivan E. , RET-DAY]

I meant to say you *should* lock down their ability to issue that command.

-----Original Message-----
From: JES2 discussion group [mailto:JES2-***@listserv.vt.edu] On Behalf Of Davidson, Ivan E. (RET-DAY)
Sent: Wednesday, January 14, 2015 9:54 AM
To: JES2-***@listserv.vt.edu
Subject: Re: No WLM init's, yet job running in one ?

Sounds like you lock down their ability to issue that command.

-----Original Message-----
From: JES2 discussion group [mailto:JES2-***@listserv.vt.edu] On Behalf Of Joe Ellis
Sent: Wednesday, January 14, 2015 9:40 AM
To: JES2-***@LISTSERV.VT.EDU
Subject: Re: No WLM init's, yet job running in one ?

looks like our offshore contractors are doing this :

"The other way a job is run in a WLM mode initiator is if a start job command is issued. That would be something like $S J1234. In this case a WLM initiator is started to run the job (even though there are no MODE=WLM job classes)."

they have 10 class A init's to run in, I observed them submitting jobs and when they don't get picked up immediately because there's a queue of work in class A waiting, , they do $S J1234

Thanks to all for your help !!!

[Joe Ellis]

correct, we reviewed RACF and this JES2.START.BAT wasn't set, it will be shortly
they are doing a 'J' in sdsf to cause the $S