Try issuing this:

$DJOBCLASS(a),XEQMEMBER(b)                       Display jobclass a for lpar b

If the values are not what you expect, issue:

$TJOBCLASS(a),XEQMEMBER(b)=(MAXIMUM=c)    Change jobclass information

Also, post the output of the $DJOBCLASS command. Perhaps that will provide us 
with a clue.

Bob

-----Original Message-----
From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf 
Of Ambrose Jr
Sent: Tuesday, April 04, 2017 6:09 AM
To: [email protected]
Subject: Re: Job hold on jes2 input queue

@ mike, We are not submitting from another jes2 .

I found some of them are WLM managed.I tried submitting the jobs with 
non-managed WLM initiators but still facing the same issue (freeze on input q).
I have no idea on WLM but I presume this not WLM issue. If its related to 
WLM,how the jobs started running after manual submission from jes2 input queue?.




On Tue, Apr 4, 2017 at 12:13 PM, Vernooij, Kees (ITOPT1) - KLM < 
[email protected]> wrote:

> Are the jobs in JES2 or WLM managed jobclasses?
> If WLM, check the CPU utilization and goals why WLM does not allow the 
> jobs.
>
> Kees.
>
> > -----Original Message-----
> > From: IBM Mainframe Discussion List 
> > [mailto:[email protected]] On Behalf Of Ambrose Jr
> > Sent: 03 April, 2017 20:15
> > To: [email protected]
> > Subject: Job hold on jes2 input queue
> >
> > Hi Team,
> >
> >
> > We recently migrated test lpar from mainframe to RDT. All our 
> > submitted jobs are hold(freeze )in jes2 input queue until we 
> > manually submit by command *SJ* in front of the job to execute.  What would 
> > be the issue ?.
> > I
> > have no clue. Your guidenes would be more  helpful
> >
> > .
> >
> >
> > Note:-  (This migrated test lpar is sysplex on mainframe .On RDT 
> > it's in monoplex) . Also Verified there is no hold parameter 
> > ,initiator .
> >
> >
> > Regards,
> >
> > Ambrose jr
> >
> > --
> >
> > --------------------------------------------------------------------
> > -- For IBM-MAIN subscribe / signoff / archive access instructions, 
> > send email to [email protected] with the message: INFO 
> > IBM-MAIN
> ********************************************************
> For information, services and offers, please visit our web site:
> http://www.klm.com. This e-mail and any attachment may contain 
> confidential and privileged material intended for the addressee only. 
> If you are not the addressee, you are notified that no part of the 
> e-mail or any attachment may be disclosed, copied or distributed, and 
> that any other action related to this e-mail or attachment is strictly 
> prohibited, and may be unlawful. If you have received this e-mail by 
> error, please notify the sender immediately by return e-mail, and delete this 
> message.
>
> Koninklijke Luchtvaart Maatschappij NV (KLM), its subsidiaries and/or 
> its employees shall not be liable for the incorrect or incomplete 
> transmission of this e-mail or any attachments, nor responsible for any delay 
> in receipt.
> Koninklijke Luchtvaart Maatschappij N.V. (also known as KLM Royal 
> Dutch
> Airlines) is registered in Amstelveen, The Netherlands, with 
> registered number 33014286
> ********************************************************
>
>
> ----------------------------------------------------------------------
> For IBM-MAIN subscribe / signoff / archive access instructions, send 
> email to [email protected] with the message: INFO IBM-MAIN
>



--
Regards,

Ambrose jr.
--------------------

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions, send email to 
[email protected] with the message: INFO IBM-MAIN

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN

Reply via email to