Jobs stay at job queue forever

[Achilleas Boulogiorgos]

I am having a 9402 200 model with V3R2M0 and running an application there.
In the past two weeks I experienced a problem that I can't explain. Whatever
Batch job I am sending from the application to the system it remains in job
queue and unless I will change it and place it in another job queue (e.g.
qs36evoke) it will never run!!!!

What can I look in order to solve this problem? The QBATCH subsystem works.
I have compared the max activity level in the QBATCH subsystem and also in
the system values with a similar system in another company and I found it
exactly the same. I looked also if there is a subsystem inoperative but all
look ok.

What can go wrong?

Achilleas Boulogiorgos
Softecon Greece

[Mike McIntire]

Well let's see --
1) The job that isn't starting could have been submitted with
HOLD(*YES). But this doesn't seem likely since it starts if you move it
to S36EVOKE.
2) The jobq could be on hold
3) The jobq could be single-threaded and another job could already be
running from the queue
4) The active subsystems may not have the jobq listed as a jobq entry
5) ...anyone with other ideas?

[Ian Simmons]

Hi,

I'm not sure what you've tried so far, but... remember that a job-queue
must be attached to an active sub-system via the sub-system description.
When you submit a job, what job-queue (and library) is the job going into?
And what sub-system are you expecting it to run in?

E.g. if you are expecting to run in QBATCH, do WRKSBSD QBATCH and firstly
see that there is only one sub-system and that it is the active one. Take
option 5 to see the description in detail, and take option 6 to see the
job-queue entries. If your job-queue is not one of those listed, your job
won't run there.

You can add your job-queue to a sub-system description: make sure the
sub-system is ended (ENDSBS), execute a command ADDJOBQE (Add Job Queue
Entry), specifying the position in the list of queues, maximum number of
active jobs to run from that queue at one time etc.; then start the
sub-system again (STRSBS).

Hope this shows something

Achilleas Boulogiorgos <aboul...@ath.forthnet.gr> wrote in article
<712r0t$an7$1...@sharon.forthnet.gr>...

[Evan Harris]

Achilleas,

What is the name of the jobq ?

use the WRKJOBQ command to display all job queues and see if the status
on the jobq queue is HLD - it will need to be released if this is the
case.

Also look through all your subsystems by using WRKSBS and option 5 to
display the description for each subsystem. Use option 6 to display the
job queue entries and look for an entry with the same name as the job
queue your jobs are being placed in.

For the time being I can't think of anything else.

Cheers.
Evan

[tho...@inorbit.com]

Achilleas:

A couple commands that others have suggested are WRKSBSD and WRKSBS. Although
there are numerous similarities between these commands, there is a significant
difference in how they choose which subsystems to list.

WRKSBS will list subsystems that are active at the moment the command is
executed (or the display is refreshed). WRKSBSD will list subsystem
descriptions based on the filtering supplied through the SBSD() parameter
regardless of whether the subsystem descriptions are ever used.

For your puposes, I'd definitely suggest using WRKSBS. You want to be certain
you're looking at the subsystem description that's actually in use.

Tom Liotta

In article <712r0t$an7$1...@sharon.forthnet.gr>,

"Achilleas Boulogiorgos" <aboul...@ath.forthnet.gr> wrote:
> I am having a 9402 200 model with V3R2M0 and running an application there.
> In the past two weeks I experienced a problem that I can't explain. Whatever
> Batch job I am sending from the application to the system it remains in job
> queue and unless I will change it and place it in another job queue (e.g.
> qs36evoke) it will never run!!!!
>
> What can I look in order to solve this problem? The QBATCH subsystem works.
> I have compared the max activity level in the QBATCH subsystem and also in
> the system values with a similar system in another company and I found it
> exactly the same. I looked also if there is a subsystem inoperative but all
> look ok.
>
> What can go wrong?
>
> Achilleas Boulogiorgos
> Softecon Greece
>
>

-----------== Posted via Deja News, The Discussion Network ==----------
http://www.dejanews.com/ Search, Read, Discuss, or Start Your Own

[Jack Callahan]

Mike McIntire wrote:
>
> Well let's see --
> 1) The job that isn't starting could have been submitted with
> HOLD(*YES). But this doesn't seem likely since it starts if you move it
> to S36EVOKE.
> 2) The jobq could be on hold
> 3) The jobq could be single-threaded and another job could already be
> running from the queue
> 4) The active subsystems may not have the jobq listed as a jobq entry
> 5) ...anyone with other ideas?
>

The job queue may be defined as part of a subsystem which is currently
inactive (use the STRSBS command, and jobs will be accepted off the
queue).

[Orangtang]

Do a WRKSBSD and look at the JOBQ entries for that subsystem..sounds like your
JOBQ is not assigned to an active subsystem....Ron