SYS$BATCH - all jobs keep going to PENDING status

April 13, 2012 at 10:12:14
Specs: OPENVMS
I have several command procedures that resubmit themselves before completing - so they are 'looping' continuously (searching for files and then kicking off procedures based on results. Most days this works perfectly -- However, there have been times where suddenly every job in SYS$BATCH goes to a Pending Status - and I have to START SYS$BATCH

Why would the submitted jobs all be in a Pending state? (no jobs executing in the SYS$BATCH queue. Below are the jobs that normally Execute without hitch - as evidenced by the Status column (I checked the queue three times in succession)....
$ pq
Batch queue SYS$BATCH, available, on RES::

Entry Jobname Username Status
----- ------- -------- ------
228 SRGAUTO BACKUP Executing
566 DHLAR DHLEMAILAR Executing
578 FCISREMIT BACKUP Executing
580 FXAR FEDEXAR Executing
647 EMAILDEF2 BACKUP Executing
694 BILLIMAGE BACKUP Executing
713 DHLAR DHLEMAILAR Executing
782 LEGFORWARD BACKUP Executing
895 SRGEMAIL BACKUP Executing
909 YRCGETPAID BACKUP Executing
108 SRGPULLBU BACKUP Executing
121 FACSSUPP BACKUP Executing
326 NOVERIFY BACKUP Holding until 14-APR-2012 00:00:00
$ pq
Batch queue SYS$BATCH, available, on RES::

Entry Jobname Username Status
----- ------- -------- ------
228 SRGAUTO BACKUP Executing
566 DHLAR DHLEMAILAR Executing
578 FCISREMIT BACKUP Executing
580 FXAR FEDEXAR Executing
647 EMAILDEF2 BACKUP Executing
694 BILLIMAGE BACKUP Executing
713 DHLAR DHLEMAILAR Executing
782 LEGFORWARD BACKUP Executing
895 SRGEMAIL BACKUP Executing
909 YRCGETPAID BACKUP Executing
108 SRGPULLBU BACKUP Executing
127 FACSSUPP BACKUP Executing
128 FACSSUPP BACKUP Starting
129 YRCGETPAID BACKUP Starting
326 NOVERIFY BACKUP Holding until 14-APR-2012 00:00:00
$ pq
Batch queue SYS$BATCH, available, on RES::

Entry Jobname Username Status
----- ------- -------- ------
228 SRGAUTO BACKUP Executing
566 DHLAR DHLEMAILAR Executing
578 FCISREMIT BACKUP Executing
580 FXAR FEDEXAR Executing
647 EMAILDEF2 BACKUP Executing
694 BILLIMAGE BACKUP Executing
713 DHLAR DHLEMAILAR Executing
782 LEGFORWARD BACKUP Executing
895 SRGEMAIL BACKUP Executing
108 SRGPULLBU BACKUP Executing
129 YRCGETPAID BACKUP Executing
139 FACSSUPP BACKUP Executing
326 NOVERIFY BACKUP Holding until 14-APR-2012 00:00:00
$


See More: SYS$BATCH - all jobs keep going to PENDING status

Report •


#1
April 13, 2012 at 10:44:14
when the job is in pending status what is the status of the queue?
$show queue sys$batch

also you need to know the job limit of the queue (if the new job goes in pending status while other jobs in the same queue is in execution status)


Report •

#2
May 1, 2012 at 04:38:14
Perform a $sho que/ful sys$batch. Take note of the job_limit as noted above. In most cases the "pending" status indicates that the job is waiting for an available slot for processing. Increasing the job_limit will allow more batch jobs to run on parallel. Your use of the start/que may also indicate that the queue is being stopped by someone else. The bottom line here is that more information is required about your specific situation. If this occurs again, please post the output of the following: SHO QUE/A/FUL SYS$BATCH

Dan


Report •

Related Solutions


Ask Question