ATTENTIONThis FlexSim Community Forum is read-only. Please post any new questions, ideas, or discussions to our new community (we call it Answers) at https://answers.flexsim.com/. Our new Question & Answer site brings a modern, mobile-friendly interface and more focus on getting answers quickly. There are a few differences between how our new Q&A community works vs. a classic, threaded-conversation-style forum like the one below, so be sure to read our Answers Best Practices. |
flexsim.com |
#1
|
|||
|
|||
TASKTYPE_BREAK
In the mannual about TASKTYPE_BREAK, it says:
var2 This parameter specifies whether or not the TaskExecuter should check to receive task sequences from an upstream Dispatcher. By default (0), the TaskExecuter will see if it has any task sequences in its queue. If the queue is empty, or if all of the task sequences in its queue are task sequences that have already been start and broken out of, then it will open its input ports and receive a task sequence from an upstream dispatcher. However, if var2 is not zero, then the TaskExecuter will not receive anything from an upstream dispatcher before calling its break logic. I cannot unstand this, will someone make it more clear? An example is preferred. thanks |
#2
|
|||
|
|||
1. By default (0), the TaskExecuter will see if it has any task sequences in its queue. If the queue is empty, then it will open its input ports and receive a task sequence from an upstream dispatcher.
Does this mean the TE will wait until receive another TS, then go to break logic? If the queue is not empty, what will happen? |
#3
|
||||
|
||||
|
The Following User Says Thank You to Steven Hamoen For This Useful Post: | ||
qin tian (10-30-2008) |