Issues for Dynamic Scheduling FTF email list

To comment on any of these issues, send email to scheduling-ftf@omg.org. (Please include the issue number in the Subject: header, thusly: [Issue ###].) To submit a new issue, send email to issues@omg.org.

List of issues (green=resolved, yellow=pending Board vote, red=unresolved)

List options: All ; Open Issues only; or Closed Issues only

Issue 5754: Spawn
Issue 5755: get the thread id from a distributable thread instance
Issue 5756: In section 5.5.2, the semantics for scheduling_policies should be discussed
Issue 5757: In section 5.2.7.2, "scheduling policy" should be "scheduling parameter
Issue 5758: VoidData should be documented
Issue 5759: problem for some schedulers using Portable Interceptors for scheduling pts.
Issue 5760: The RTC1 document needs to be integrated with the RTC2 document
Issue 5761: RTCurrent
Issue 5762: The distributed thread id must be available in all interception points

Issue 5754: Spawn (scheduling-ftf)

Click here for this issue's archive.
Source: Objective Interface Systems (Mr. Bill Beckwith, bill.beckwith@ois.com)
Nature: Uncategorized Issue
Severity:
Summary: 
Spawn should discuss the initial execution state of the
  newly created distributable thread

Resolution:
Revised Text:
Actions taken:
November 12, 2002: received issue

Issue 5755: get the thread id from a distributable thread instance (scheduling-ftf)

Click here for this issue's archive.
Source: Objective Interface Systems (Mr. Bill Beckwith, bill.beckwith@ois.com)
Nature: Uncategorized Issue
Severity:
Summary: 
 It should be possible to get the thread id from a
  distributable thread instance

Resolution:
Revised Text:
Actions taken:
November 12, 2002: received issue

Discussion: 
get the thread id from a distributable thread instance

Issue 5756: In section 5.5.2, the semantics for scheduling_policies should be discussed (scheduling-ftf)

Click here for this issue's archive.
Source: Objective Interface Systems (Mr. Bill Beckwith, bill.beckwith@ois.com)
Nature: Uncategorized Issue
Severity:
Summary: 
In section 5.5.2, the semantics for scheduling_policies should be discussed

Resolution:
Revised Text:
Actions taken:
November 12, 2002: received issue

Issue 5757: In section 5.2.7.2, "scheduling policy" should be "scheduling parameter (scheduling-ftf)

Click here for this issue's archive.
Source: Objective Interface Systems (Mr. Bill Beckwith, bill.beckwith@ois.com)
Nature: Uncategorized Issue
Severity:
Summary: 
In section 5.2.7.2, "scheduling policy" should be "scheduling parameter

Resolution:
Revised Text:
Actions taken:
November 12, 2002: received issue

Issue 5758: VoidData should be documented (scheduling-ftf)

Click here for this issue's archive.
Source: Objective Interface Systems (Mr. Bill Beckwith, bill.beckwith@ois.com)
Nature: Uncategorized Issue
Severity:
Summary: 
VoidData should be documented

Resolution:
Revised Text:
Actions taken:
November 12, 2002: received issue

Issue 5759: problem for some schedulers using Portable Interceptors for scheduling pts. (scheduling-ftf)

Click here for this issue's archive.
Source: Objective Interface Systems (Mr. Bill Beckwith, bill.beckwith@ois.com)
Nature: Uncategorized Issue
Severity:
Summary: 
There is a potential problem for some schedulers in using
  Portable Interceptors for scheduling points.  PICurrent can't
  be updated in receive_reply.

Resolution:
Revised Text:
Actions taken:
November 12, 2002: received issue

Discussion: 




Issue 5760: The RTC1 document needs to be integrated with the RTC2 document                                                                                                                                         (scheduling-ftf)

Click here for this issue's archive.


Source: Objective Interface Systems (Mr. Bill Beckwith, bill.beckwith@ois.com)

Nature: Uncategorized Issue

Severity: 

Summary: 
The RTC1 document needs to be integrated with the RTC2 document


Resolution: 

Revised Text: 

Actions taken:

November 12, 2002: received issue



Issue 5761: RTCurrent                                                                                                                                                                                               (scheduling-ftf)

Click here for this issue's archive.


Source: Objective Interface Systems (Mr. Bill Beckwith, bill.beckwith@ois.com)

Nature: Uncategorized Issue

Severity: 

Summary: 
The RTC1 document needs to assert that RTCurrent must be correct
  in various interception points (in order for Dynamic Scheduling
  to work).



Resolution: 

Revised Text: 

Actions taken:

November 12, 2002: received issue



Issue 5762: The distributed thread id must be available in all interception points                                                                                                                                  (scheduling-ftf)

Click here for this issue's archive.


Source: Objective Interface Systems (Mr. Bill Beckwith, bill.beckwith@ois.com)

Nature: Uncategorized Issue

Severity: 

Summary: 
The distributed thread id must be available in all interception points.


Resolution: 

Revised Text: 

Actions taken:

November 12, 2002: received issue