As J.O.Skip mentioned I had a similar issue, but I was joining 2 systems into a JES2 MAS and there was a previous definition for another SYSNAME in the definition, after I followed the doc some have pointed me to I was about to modify the node name and get my jobs running after being submitted, which is a good thing :) Lizette suggested I display the jobs in the input queue to see the reason why the jobs would not run using the $dj'myjob',long display, not sure you've tried this .
Carmen ----- Original Message ----- From: "Ambrose Jr" <[email protected]> To: [email protected] Sent: Thursday, April 6, 2017 11:00:13 PM Subject: Re: Job hold on jes2 input queue Hi, yes, those are all WLM managed initiators. i have changed them from mode=wlm to jes but it didn't work :(. Any other way to skip this? .Also, I noted if I submit the wrong(error) jcl it starts executing automatically but the same jcl is on hold on input queue after the fix. Note: we are using the same WLM in RDT which was defined in the mainframe. 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
