JPH04168532A - Multi-task device - Google Patents

Abstract

PURPOSE:To construct the sufficient multi-task system by using an application software by setting the corresponding flag memory, when a non-set state of a flag memory corresponding to the other task is decided. CONSTITUTION:When data is received from a handy terminal 6, and a task (1) is actuated in this state, first of all, a flag memory 16b is checked. As a result, when the flag memory 16b is '0', it is decided that a transmitting data file 15 is not used by a task (2), a flag memory 16a is set to '1' and received data is written in the transmitting data file 15, and when write is finished, the flag memory 16a is set to '0'. In such a way, a file memory can be shared between each task, and by using an application software which can execute plural tasks independently from each other and by a time division, a sufficient multi-task system is constructed.

Description

DETAILED DESCRIPTION OF THE INVENTION [Field of Industrial Application] The present invention relates to a multitasking device that executes a plurality of tasks independently of each other in a time-sharing manner.

[Prior Art] It is conceivable to build a multitasking system on a personal computer using commercially available application software that can execute multiple tasks independently of each other in a time-sharing manner. Since the software does not have a shared area between tasks, it was insufficient as a multitasking system as it was.

[Problems to be Solved by the Invention] As described above, in the past, it has not been possible to construct a sufficient multitasking system using commercially available application software.

Therefore, the present invention aims to provide a multitasking device that can construct a sufficient multitasking system using application software that can execute a plurality of tasks independently and in a time-sharing manner.

[Means for Solving the Problem] The invention corresponding to claim (1) provides a multitasking device that executes a plurality of tasks independently and in a time-sharing manner, including a file memory shared by each task and a memory corresponding to each task. a flag memory set during task execution; a flag memory set corresponding to another task at the start of task execution; A means is provided for setting a corresponding flag memory and accessing the file memory when a non-set state is determined.

The invention corresponding to claim (2) is a multitasking device that executes a plurality of tasks independently of each other in a time-sharing manner, including a file memory shared by each task, and a common device commonly provided for each task that accesses the file memory. a driver, a means for determining whether or not the common driver is in use at the start of task execution, and a means for driving the common driver to access file memory when it is determined by this means that the common driver is not in use. It has been established.

[Operation] In the present invention having such a configuration, at the start of task execution, it is determined whether a flag memory provided corresponding to another task is set or not set, and the unset state of this flag memory is determined. Set the flag memory corresponding to the task to be executed when the file memory is accessed.

This allows file memory to be shared between tasks.

Also, at the start of task execution, it is determined whether or not the common driver is in use, and when it is determined that the common driver is not in use, the common driver is driven to access the file memory. This allows file memory to be shared between tasks.

[Implementation fPJE Hereinafter, one embodiment of the present invention will be described with reference to the drawings.

In FIG. 1, 1 is a microprocessor that constitutes the main body of the control unit, 2 is a RAM (random access memory), 3 is a display controller that controls a display 4, and 5 is an externally connected handy terminal 6 and information controller. 7 is a keyboard controller for controlling the keyboard 8; 9 is an I10 port to which a printer 10 is connected; and 11 is an I10 port to which a node disk 12 is connected.

The microprocessor 1, RAM 2, display controller 3, communication interface 5, keyboard controller 7, and each I10 port 9-11 are connected by a path line 13.

The hard disk 12 has a master file 14 storing various management data with indexes, a transmission data file 15, and a control file 16. The control file 16 includes a flag memory (1) 16a and a flag memory (2) 16.
b is provided.

The microprocessor 1 controls each part based on a program, and the program includes, for example, two tasks (1) and (2) that are executed independently and in a time-sharing manner.
Each task using (1).

(2) controls the transmission data file 15 which is a shared file memory.

This control is shown in functional blocks as shown in FIG. 2, and each task (1) and (2) performs the processing shown in FIGS. 3 and 4.

In other words, the data from Handy Terminal 6 is transferred to the task (
When data is transmitted to the transmission data file 15 by task (1) and data from the transmission data file 15 is registered in the mask file 14 by task (2), task (1) first stores the flag memory (2) as shown in FIG. ). Then, if the flag memory (2) is in the non-set state, it is set to the flag memory (1)-1.

Subsequently, the flag memory (2) is checked again.

If the flag memory (2) is -0, the data from the 1st day terminal 6 is written into the transmission data file 15. Then, the flag memory (1) is set to a non-set state, that is, to 0. If the flag memory (2) is -1, it is determined that the task (2) is using the transmission data file 15, and the flag memory (1) is immediately set to 0 to end the process.

Further, in the first check of the flag memory (2), if the flag memory (2) is -1, it is determined that the task (2) is using the transmission data file 15, and the process is immediately terminated.

Also, task (2) first checks flag memory (1) as shown in FIG. And flag memory (1) -
0, that is, if it is in a non-set state, the flag memory (2)
-1.

Subsequently, the flag memory (1) is checked again.

Then, if the flag memory (1) is -0, the data from the transmission data file 15 is called and the data is stored in the master file 14.
Register. Then, the flag memory (2) is set to a non-set state, that is, to 0. If the flag memory (1) is -1, it is determined that the task (1) is using the transmission data file 15, and the flag memory (2) is immediately set to O to terminate the process.

Further, in the first check of the flag memory (1), if the flag memory (1) is -1, it is determined that the task (1) is using the transmission data file 15, and the process is immediately terminated.

In this embodiment having such a configuration, when data is received from the handy terminal 6 and the task (1) is activated in this state, the flag memory (2) is first checked. If flag memory (2) is -0, it is determined that the transmission data file 15 is not used by task (2), and the flag memory (1) is set to "1" and the received data is written to the transmission data file 15. . When this data writing is completed, the flag memory (1) is set to "0".

Also, when task (2) is started, first the flag memory (1
) is checked. If flag memory (1) is -0, it is determined that the transmission data file 15 is not used by task (1), and flag memory (2) is set to "1".
The data is retrieved from the transmission data file 15 and registered in the master file 14. When this data registration is completed, the flag memory (2) is set to "0".

By the way, since task (1) and task (2) are tasks that are executed independently of each other in a time-sharing manner, for example, task (2) may be activated when task (1) is executed. Even if such a state occurs, task (2) will never access the transmission data file 15 because flag memory (1) is set to "1" while task (1) is being executed. Conversely, when task (2) is executed, task (1)
may be activated. Even if such a state occurs, the flag memory (2) remains "1" while task (2) is being executed.
Therefore, task (1) is the send data file 1.
5 is never accessed.

In this way, the transmission data file 15 which is a shared file
Task (1) and task (2) can be exclusively controlled, and a sufficient multitasking system can be constructed.

Note that the master file 14, transmission data file 15, and control file 16 do not necessarily need to be provided on a hard disk, and may be provided on, for example, a RAM.

Next, other embodiments of the present invention will be described with reference to the drawings.

As shown in the functional block in Figure 5, this task (1
) and task (2) use the system memory 18 as a shared file, in which a routine call unit 19 is provided as a common driver for each task.

This routine call section 19 is designed to execute an interrupt routine shown in FIG.

That is, first, interrupts are disabled and registers are saved.

Next, the in-use flag memory provided in the control file 16 is checked, and if the in-use flag memory is 1, it is determined that the other task is using the system memory 18, and the register is immediately restored to enable interrupts. Finish the process.

If the in-use flag memory is 0, the in-use flag memory is set to "1" to permit interrupts and a mode check is performed. In the case of task (1), the mode is write, so data N(
Write the data from the handy terminal 6 to the LX. Further, in the case of task (2), since the mode is read, data is retrieved from the designated area of the system memory 18, ie, the data area X, and is registered in the master file 14.

When this process is completed, interrupts are disabled, the in-use flag memory is set to "0", registers are restored, interrupts are enabled, and the process ends.

In this embodiment with such a configuration, for example, a task (
When task (1) starts the routine call section 19, task (2)
) has not activated the routine call unit 19, the in-use flag memory is set to 0, and in this case, the data from the handy terminal 6 can be written to the data No. and X of the system memory 18 by task (1). .

Also, when task (2) starts the routine call section 19, if task (1) has not started one routine call section, the in-use flag memory is set to 〇. The data can be read from the data NO, X and registered in the master file 14.

Also, task (2) or data NCL of system memory 18
When task (1) starts the routine call section 19 while calling data from x and registering it in the master file 14, the in-use flag memory 1 is set, so at this time, the system memory 18 by task (1)
access is prohibited.

In this way, also in this embodiment, task (1) and task (2) can be exclusively controlled with respect to the system memory 18, which is a shared file, and a sufficient multitasking system can be constructed.

In addition, in the above embodiment, a case was described in which two tasks are executed independently of each other in a time-sharing manner, but the invention is not necessarily limited to this, and even if three or more tasks are used. Similar effects can be obtained.

[Effects of the Invention] As detailed above, according to the present invention, there is provided a multitasking device that can construct a sufficient multitasking system using application software that can execute multiple tasks independently and time-sharingly. It is possible to provide

[Brief explanation of the drawing]

1 to 4 show one embodiment of the present invention, FIG. 1 is a block diagram, FIG. 2 is a functional block diagram for explaining main part control, and FIGS. 3 and 4 are Flowcharts showing task processing, FIGS. 5 and 6 show other embodiments of the present invention, FIG. 5 is a functional block diagram for explaining main part control, and FIG. 6 shows an interrupt routine. This is a flowchart. DESCRIPTION OF SYMBOLS 1... Microprocessor, 14... Master file, 15... Transmission data file, 16a, 16b-flag, 18... System memory, 19... Routine call section. Applicant's agent Patent attorney Takehiko Suzue No. 1 @ Figure 2 Figure 5 @

Claims (2)

[Claims] (1) In a multitasking device that executes multiple tasks independently of each other in a time-sharing manner, a file memory shared by each task, a flag memory provided corresponding to each task and set during task execution, Means for determining whether a flag memory provided corresponding to another task is set or not set at the start of task execution, and setting the corresponding flag memory when the unset state of the flag memory is determined by this means. A multitasking device comprising means for accessing the file memory. (2) In a multitasking device that executes multiple tasks independently of each other in a time-sharing manner, a file memory shared by each task, a common driver provided in common to each task that accesses the file memory, and task execution start means for determining whether or not the common driver is currently in use, and means for driving the common driver to access the file memory when it is determined by this means that the common driver is not in use. A multitasking device characterized by: