Use of the information contained in this unapproved document is at your own risk.

Last update: 10 April,2001

								1003.1-96  #113

 _____________________________________________________________________________

	Interpretation Number:	XXXX
	Topic:			scheduling
	Relevant Sections: P 306 L 713, P 290 L 141


PASC Interpretation Request: (Defect Report)
----------------------------  

        Date: 2000 June 16
	Ref: XSH 472


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

 7  Defect Report concerning (number and title of International Standard
    or DIS final text, if applicable): 

IEEE Std 1003.1-1996 (incorporates 1003.1-1990, 1003.1b-1993, 1003.1c-1995,
1003.1i-1995) (ISO 9945-1:1996)
------------------------------------------------------------------------ 

 8  Qualifier (e.g. error, omission, clarification required):

3

Error=1 , Omission=2, Clarification=3

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

 9  References in document (e.g. page, clause, figure, and/or table
    numbers):

P 306 L 713
P 290 L 141
------------------------------------------------------------------------ 

10  Nature of defect (complete, concise explanation of the perceived
    problem):

The phrase "moving to the tail of the scheduling queue" is not defined
elsewhere in the document.  Although it's intuitively obvious to _authors_
of the document, it is not precise (not legally defendable as meaning
the same thing as whatever it DOES mean in a court of law, should 
it ever come to that).

It's apparently referring to the text at P290 L141, but that to some
degree is guesswork on my part.  The same phrasing is not used.
------------------------------------------------------------------------ 

11  Solution proposed by the submitter (optional):

Instead of "moving to the tail of the scheduling queue"...
change (starting at the *):

"While a thread is holding...protocol attributes *it shall not subject to
the requirement that it resume execution after all other runnable processes
at equal or greater priority have been scheduled to run as required
by sched_setparam() and similar calls".  (2 places).

Also, add at 34508 (in sched_setparam):
"except as specified under pthread_mutexattr_getprotocol()".

It would not hurt to collect these requirements together under General
Concepts and refer to them from both locations.  I'll
HELP draft words should that be acceptable, but I'm not expert enough
in this area to do it alone.  (I believe there's a start to this in
the Austin Group draft.)

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




Interpretation response
------------------------
The standard is clear, see the definition on page 287, lines 23-27.
This is also a duplicate of interpretation #100.
No change is required.

Rationale
-------------
None.

Forwarded to Interpretations group: 19 June 2000
Proposed resolution: 25 July 2000
Finalised interpretation: 29 August 2000