How to make the waiting job to get executed



JES, JES2, JCL utilities, IDCAMS, Compile & Run JCLs, PROCs etc...

How to make the waiting job to get executed

Postby satham ussain » Thu Nov 22, 2012 9:28 pm

2.In the ST Panel , the job are in waiting state. Why they
are in waiting & below mentioned is INIT panel display.


NP ID Status Classes JobName StepName ProcStep JobID C ID
17 DRAINED HPDAM
18 DRAINED HPDAM
19 DRAINED HPDAM
20 DRAINED HPDAM
21 DRAINED BYETQZ
22 DRAINED BYETQZ
23 DRAINED BYETQZ

24 DRAINED BYETQZ
25 DRAINED BYETQZ

How to make the waiting job to get executed?
satham ussain
 
Posts: 1
Joined: Thu Nov 22, 2012 9:17 pm
Has thanked: 1 time
Been thanked: 0 time

Re: How to make the waiting job to get executed

 

Re: jes

Postby steve-myers » Thu Nov 22, 2012 10:36 pm

Operations has chosen to "drain" the initiators you displayed. This means they cannot run jobs. Period. End of story. You cannot "start" a drained initiator; only operations can do this.

A job waiting to execute is just that; no active initiator is available to run the job.

There are two methods an initiator can select a job.
  • The JES2 standard method; a job is selected based on job class and job priority. For example, if initiator 17 was active, it would select the highest priority class H job, then the highest priority class P job and so on to the highest priority class M job. If there were no jobs in those classes, the initiator would go idle.
  • "Goal" mode selection. z/OS tells JES2 which job to select. I've never closely studied this and can't tell you very much.
Some shops define some initiators as goal mode and others as traditional. Traditional initiators are often restricted to special jobs; it would be unwise to fake a special job if you see an idle traditional initiator.

These users thanked the author steve-myers for the post:
satham ussain (Fri Nov 23, 2012 2:53 pm)
steve-myers
Global moderator
 
Posts: 1885
Joined: Thu Jun 03, 2010 6:21 pm
Has thanked: 4 times
Been thanked: 197 times

Re: How to make the waiting job to get executed

Postby Dinesh anbu » Sat Nov 24, 2012 10:04 am

By using TYPRUN=hold/scan in job statement
Hold means job to be detained in input queue until explicity released by operator.
Scan means jcl tobe scanned for syntax errors only and does not execute.

//ADM012D JOB P999,
// ADM012,
// NOTIFY=ADM012,CLASS=A,TYPRUN=HOLD,
// MSGLEVEL=(1,1)
Dinesh anbu
 
Posts: 3
Joined: Sat Nov 24, 2012 9:31 am
Has thanked: 0 time
Been thanked: 0 time

Re: How to make the waiting job to get executed

Postby NicC » Sat Nov 24, 2012 10:37 pm

Dinesh anbu

What, exactly, has your post to do with enquiring about why a job is not executing? Why put a hold on the job? That will definitely stop the job running which is the opposite of what is required, and a scan will not help it run. Please provide information that will supply an answer/resolution not something unrelated to the topic in question.
The problem I have is that people can explain things quickly but I can only comprehend slowly.
Regards
Nic
NicC
Global moderator
 
Posts: 2690
Joined: Sun Jul 04, 2010 12:13 am
Location: Pushing up the daisys (almost)
Has thanked: 4 times
Been thanked: 105 times

Re: How to make the waiting job to get executed

Postby bodatrinadh » Tue Nov 27, 2012 7:50 am

Hi Satham,

Apart from Drained status, if the job is on HOLD, then Issue 'A' corresponding to that job, if you are executing the job manually/holding intentionally...If the job is triggered via scheduler then go through the particular scheduler manuals...
Thanks
-3nadh
User avatar
bodatrinadh
 
Posts: 67
Joined: Thu Jan 12, 2012 9:05 pm
Has thanked: 0 time
Been thanked: 4 times


Return to JCL

 


  • Related topics
    Replies
    Views
    Last post