Re: The 'S' status on the job queue

JEMILLER

VIP Member
Re: The \'S\' status on the job queue

Hi Sebastián,

The S or "In Queue" status means that a job has been noticed by a UBE kernel
process but has not yet been passed to a runbatch or runube process for
execution. The UBE kernels basically sit in a loop scanning the F986110
table looking for jobs in W status. When one of these kernels finds a job
and is ready to start it running is updates the record to S. Once the job
has started executing, the status moves to P.

Normally a job should not sit in S status for very long. There is a bug
that was in a recent Breaking News item where certain UBE's can lock a
servers spec files while they run. This will prevent other UBE's from
moving from S to P status. I have applied this fix to a few clients and it
seems to have cleared up the problem.

Regards,

Justin Miller




Justin Miller
[email protected]

working with B7332 and XE on AS/400, NT, Solaris and AIX
 
RE: The \'S\' status on the job queue

Another note, on the enterprise server on the jde.ini, under 'network queue
settings' there is a key, QueueDelay=30. Does anyone know if this is used,
or what it pertains to? I was under the impression that this is the number
of seconds the system waits between checking the queue for something
waiting. Is this incorrect?

John

Xe, SP14.2, NT/SQL7, Citrix/Metaframe
 
Re: RE: The \'S\' status on the job queue

John,

I believe you are correct. I have experimented with this setting and have watched Oracle's SQL buffer. If I decrease the value to 15 I get 1 select query against the F986110 where status is Waiting for each job queue configured approximately every 15 seconds.

Regards,

Justin Miller
[email protected]

working with B7332 and XE on AS/400, NT, Solaris and AIX
 
Re: The \'S\' status on the job queue

Actually, this is incorrect. When a job is submitted to a server, a network message is sent to the UBE kernel process (jdenet_k) on the server. All this job does is insert your job request into the F986110 table, and put the version specs for your job in a subdirectory of the pathcode's spec directory for merging with main specs later.

When a queue process (jdequeue) picks up this job, it moves it from a 'W' to an 'S' status. Think of 'S' as 'Spec Install'. Then the jdequeue kicks off the runbatch process - the first thing that this job does is merge the spec files that were sent from the client machine. Then, and only then, will the job move to a 'P' status. At that point the Batch Engine is called and the job actually processes.

I had this explained in detail to me by JDE...
 
Re: The \'S\' status on the job queue

Thank you for the clarification.

My understanding of the process is in line with your explanation. I had never looked into what the kernel was actually doing while the job was in S status. I had assumed it was performing some sort of housekeeping process. If the S state is where version specs are being processed (and therefore merged into the server's specs) then this would explain why jobs would be held up by the spec locking bug I described in my previous post.

Regards,



Justin Miller
[email protected]

working with B7332 and XE on AS/400, NT, Solaris and AIX
 
Re: The \'S\' status on the job queue

Hi,

I think 'S' stands for 'Submitted into jobq', means that the job is sitting
in the jobq waiting for execution.
In B7331, 'In Queue' was equal to a 'Q', that was more relevant.

Best regrds
Mats Thunholm

---------------------------------------------------------------------------------------------------------

Mats Thunholm
APBiotech
Uppsala, Sweden
+46 18 612 0646 (w), +46 70 666 5819 (m)
[email protected]
---------------------------------------------------------------------------------------------------------



Sajaroff
Sebastián To: "'[email protected]'" <[email protected]>
<SSAJAROFF@grupoa cc:
ssa.com> Subject: The 'S' status on the job queue
Sent by:
owner-jdelistml@j
delist.com


2001-07-06 18:42
Please respond to
jdelist






Hi there :

I'd like to ask the JDE gurus on what does exactly the 'S' status mean.
When jobs are submitted, they pass through the following status :

'W' Waiting for the processing
'S' In Queue
'P' Processing
'D' Done or 'E' Error

My question is : what is the technical difference between a process
in 'S' and a process in 'W'?
As far as I've seen on the Task Manager console, a process in 'S'
doesn't use CPU resources, but it's not in 'W' status either ... so
what is 'S' intended for?

Thanks all, Sebastian Sajaroff



B7332 SP11.3, AS400 V4R5
Mats Thunholm
APBiotech
Uppsala, Sweden
 
Re: The \'S\' status on the job queue

REGARDS
[email protected]
PHONE: +27317194056
MOBILE:+27829035857


Hi,

I think 'S' stands for 'Submitted into jobq', means that the job is sitting
in the jobq waiting for execution.
In B7331, 'In Queue' was equal to a 'Q', that was more relevant.

Best regrds
Mats Thunholm

---------------------------------------------------------------------------------------------------------

Mats Thunholm
APBiotech
Uppsala, Sweden
+46 18 612 0646 (w), +46 70 666 5819 (m)
[email protected]
---------------------------------------------------------------------------------------------------------



Sajaroff
Sebastißn To: "'[email protected]'" <[email protected]>
<SSAJAROFF@grupoa cc:
ssa.com> Subject: The 'S' status on the job queue
Sent by:
owner-jdelistml@j
delist.com


2001-07-06 18:42
Please respond to
jdelist






Hi there :

I'd like to ask the JDE gurus on what does exactly the 'S' status mean.
When jobs are submitted, they pass through the following status :

'W' Waiting for the processing
'S' In Queue
'P' Processing
'D' Done or 'E' Error

My question is : what is the technical difference between a process
in 'S' and a process in 'W'?
As far as I've seen on the Task Manager console, a process in 'S'
doesn't use CPU resources, but it's not in 'W' status either ... so
what is 'S' intended for?

Thanks all, Sebastian Sajaroff



B7332 SP11.3, AS400 V4R5
Mats Thunholm
APBiotech
Uppsala, Sweden

--------------------------
 
Re: The \'S\' status on the job queue

The 'S' is actually for subsystem job. For that job you should have a
corresponding record in either F986113 or F986115 (i can't remember which).


----- Original Message -----
From: "mats_thunholm" <[email protected]>
To: <[email protected]>
Sent: Monday, July 09, 2001 1:47 AM
Subject: Re: The 'S' status on the job queue


sitting
-------------------------------
-------------------------------
"'[email protected]'" <[email protected]>
on the job queue
http://198.144.193.139/cgi-bin/wwwthreads/showflat.pl?Cat=0&Board=OW&Number=
15618



JD Nowell
OW: B7332
ES: AS400 V4R4 CO: DB2/400 SP: 11.2
Users: 250 TSE Users: 100
 
RE: The \'S\' status on the job queue

It's the F986113.

Graham Jones
JDE Systems Manager
[email protected]

B7332 SP15 / AS400 V4R4 (CO on AS400) / Fat clients NT4


***** DISCLAIMER ***** This communication contains information which is
confidential. It is for the exclusive use of the intended recipient. If you
are not the intended recipient, please note that any distribution, copying
or use of this communication or the information in it is prohibited. If you
have received this communication in error, please notify us by email or by
telephone on 0151 653 1700 and then delete the email and any copies of it.
*****
 
Re: The \'S\' status on the job queue

Don't think so. Everyone of my companies that is on AS/400 B7332 "in queue"
= 'W' aiting.

'S' is a subsystem process where multiple processes are running (eg. MRP
Rebuild). There should be corresponding jobs in F986113. Run some SQL and
see. Perhaps you should SQL this out of F986110 and F986113.



----- Original Message -----
From: "brother_of_kara" <[email protected]>
To: <[email protected]>
Sent: Wednesday, July 25, 2001 1:36 PM
Subject: Re: The 'S' status on the job queue


http://198.144.193.139/cgi-bin/wwwthreads/showflat.pl?Cat=0&Board=OW&Number=
http://198.144.193.139/cgi-bin/wwwthreads/showflat.pl?Cat=0&Board=OW&Number=
17387
http://198.144.193.139/cgi-bin/wwwthreads/showflat.pl?Cat=0&Board=OW&Number=
17436



JD Nowell
OW: B7332
ES: AS400 V4R4 CO: DB2/400 SP: 11.2
Users: 250 TSE Users: 100
 
Re: The \'S\' status on the job queue

I understand that Subsystem Jobs will sit in queue
with an 'S' status. That does not neccessarily mean
that S= Subsystem. W= Waiting for the queue to come
around and get the job. S= In queue.

Look in the UDC 98/JS for a definition of the
statuses.
I don't know how else I can explain this to you...



--- hotm6654 <[email protected]> wrote:
http://198.144.193.139/cgi-bin/wwwthreads/showflat.pl?Cat=0&Board=OW&Number=
http://198.144.193.139/cgi-bin/wwwthreads/showflat.pl?Cat=0&Board=OW&Number=
http://198.144.193.139/cgi-bin/wwwthreads/showflat.pl?Cat=0&Board=OW&Number=
http://198.144.193.139/cgi-bin/wwwthreads/showflat.pl?Cat=0&Board=OW&Number=17452


__________________________________________________
 
Re: The \'S\' status on the job queue

I don't know how else to explain it to you. UDCs don't mean squat
(particularly system code 98). Maybe someone else could pick up on this
thread and tell us what job status THEY see when a UBE is sitting in a jobq.
A job is either in queue (which on my system is W). Or it is processing
(which on my system is P). This includes processing of the temporary specs
in the QACX* files. (BTW: How do you distinguish being in a queue and "a
queue coming around"?).

A job in a jobq with an S status must be unique to Unix and/or NT. I am
trying to remember from my Unix installs. On my AS/400 installs, I never
have any job records in F986110 with an S status unless and until a
multithreaded-capable UBE is running and/or parallel jobs of the same type
happen to have started processing (eg. R09801, R3483 MRP). If you don't
know what parallel processing is in the context of OneWorld, I can't help
you.






JD Nowell
OW: B7332
ES: AS400 V4R4 CO: DB2/400 SP: 11.2
Users: 250 TSE Users: 100
 
RE: The \'S\' status on the job queue

Just to add - S can be seen even if you have no Subsystem jobs.

S - means what it says in the UDC - In Queue, this means that it has been
identified as ready to run by a Queue process, but has not yet started
Processing.

There are a number of reasons why a job may be in S status for a while,
which have nothing to do with subsystems:

1) There is a dependency between this UBE and another, some UBEs are single
threaded and clever enough to not run if another UBE is processing.

2) Server Package Install: If you are running a Server Package install while
UBEs are processing, then any UBEs which are at P status are allowed to
complete, any at wait will go to S (until all QUEUES are full, others will
stay at Wait), these jobs will to be allowed to go to Processing until the
Server Package has completed.

If the currently processing job takes a long time to complete, this can
result in jobs at status S for a long while.

3) Queue failure - if you get a problem with a QUEUE, then a job may get
'stuck' at status S, I have not seen this recently but it used to be a
regular problem with B732.

If jobs are held at S for a long time and nothing is running then this is
the most likely culprit, the other two will clear given time, 3) will only
go away if the Queues are restarted and the UBE resubmitted, the S status
job may go to Error or may just stay at S even after the Queues restart,
just delete it.



OW733.3 Xe SP 14.2
Enterprise Server - Intel NT + Oracle 8.0.6
Client - Citrix TSE + 4 NT PC's for development
 
Re: The \'S\' status on the job queue

From my experience:

W - Job is waiting
S - Job has been picked up and specs are being copied to the server
P - Processing
D - Done
E - Error
H - Hold

Subsystem jobs will sit at P (i.e. running!)

I have seen jobs get stuck in S (Corrupt Specs)or take a long time at S (problem with specs being locked.)

If your system is running quickly then you may not see the job in 'S' status it is usually there for a second or two.
 
Re: The \'S\' status on the job queue

IMHO the 'S' status means that it is waiting in the JDE Subsystem Job
Queue. On my system the job does not exist on the Job Queue at this point.
Once the status changes to 'W' then I can see the job on my Job Queue. 'P'
on my system means that the job is either running or has ended in a hard
error. 'D' means that the job reached normal completion (not that it
operated correctly, just that it ended normally).

Tom Davidson
ES: AS/400 V4R5, DS: NT 5.0, TSE NT 5.0 SP 6a Metaframe 1.8.




OW 7332 SP 11.3VER, NT 4.0 SP 5, TSE 4.0 SP 4, Metrframe 1.8, CO SQL 7.0
 

Similar threads

E9.2 Virtual Job Queue?
Replies
4
Views
1K
Segfault
Soumen
E9.2 Sorting jobs in WSJ
Replies
4
Views
1K
markdcci
markdcci
Soumen
E9.2 Delay in UBE Processing
Replies
15
Views
610
Segfault
E9.2 Reports Error: Multiple Records Exist For This Job Fetched Without Server Name - Job Not Unique
Replies
2
Views
223
alfredorz
alfredorz
KoalaBaby
E9.2 How to Capture XDO BI Logs
Replies
0
Views
366
KoalaBaby
KoalaBaby
Back
Top