JPS61264443A - Informing system for task generation state - Google Patents

Abstract

PURPOSE:To reduce a communication area and also to perform both the information of generation of a task and the process to eliminate a waiting state of the requester task just in a single step, by writing an end code and a waiting state releasing macro to an event control block ECB. CONSTITUTION:When a main task 1 wants the generation of a subtask, this request is written to a communication area ECB-1. A requester task is kept waiting until the generation of the subtask is through. A task production part 2-2 discriminates the task production request and prepares the environment where a new task works to produce a new task. A deciding part 2-3 receives the result of operation from the part 2-2 to decides whether it is normal or not and informs each state value (end code) to a state end informing part 2-4. This state value and the POST macro are written to a communication area ECB-2. Then the waiting state of the task 1 is released.

Description

[Detailed description of the invention] [Table of contents] Overview Industrial application field (Figure 3) Prior art (Figure 4) Problems to be solved by the invention Means for solving the problems (Figure 1) ) Functional Example (1) Structure of the Example (Fig. 2) (2) Effect of the Operational Invention of the Example [Summary] In the task structure of a management task and its child tasks, the present invention provides an example of the operation of the management task from the child task to the management task. When requesting the creation of another task, the management task, after creating the task, notifies the creation status and releases the waiting state of the child task that requested the creation of another task in a specific area of the event management block. This is especially true.

[Industrial application field]

The present invention relates to a task generation status notification method in a multitask configuration of the PL/I language, and in particular to a notification method for efficiently notifying the task generation status from a management task to a requesting task in task generation processing. In the PL/I language, a plurality of tasks can be operated in a time-division manner, and from an external perspective, the plurality of tasks can be operated simultaneously.

When the job starts, the main task starts at the same time. When it becomes necessary to operate a subtask in accordance with the operation of the main task, the subtask can be called by the program statement CALL 5UBTASK.0Of course, a subtask also depends on its operation, and its subordinate tasks (
The current task will be called and executed. By the way, the main task can tell whether the subtask's operation has ended normally or abnormally, but it cannot know whether the owning task has ended normally or abnormally. Therefore, as shown in FIG. 3, a management task 20 is provided above a main task 21 and a plurality of subtasks 22-1 to 22-n. - 22-n are all located in a "parent-child relationship" so that the management task 20 can manage the status of the main task 21 and subtasks 22-1 to 22-n. In this case, the main task is always generated, but the other tasks 1 to n are generated by the management task when a generation request is made from the main task or the generated task.

[Conventional technology]

When requesting the generation of a new task from the main task.

Conventionally, as shown in FIG.
1-1 is the area division E of the event management block (ECB) 23
Display this request on CB 1. The reception unit 20-1 of the management task 20 thereby identifies the existence of the new task generation request, and controls the task generation unit 20-2 to perform new task generation processing. This process involves creating a task control block (TCB) for the requested task, connecting it to an appropriate TCB queue, and preparing to transfer control to the first program for that task.

The task generation unit 20-2 thus prepares the environment for the new task to operate and prepares to generate the new task. By the way, as a result of such generation preparation, the task generation module reports failures such as failures such as the TCB queue creation area not being able to connect due to lack of free space, and results such as successful generation. 2
0-2 is transmitted to the determination unit 20-3. The determining unit 20-3 receives the result from the task generating unit 20-2, converts it into a status value, and transmits this to the status notification unit 20-4. The status notification unit 20-4 sets this status value (completion code) in the return area 24. In addition, the completion notification unit 20-5 uses the notification from the status notification unit 20-4 to inform the event management block BCB of the completion of task generation to the main task.
Enter this in area division ECB-2. At this time, P.O.
Issues an 8T macro (waiting state release) to release the requesting task from waiting. In the main task 21, the completion reception unit 21-2 determines whether task generation is completed using the ECB-2. This process is repeated until completion. When the task is completed, this is reported to the inspection section 21-3, and the inspection section 21-3 examines the return area 24 to inspect whether the task was correctly generated. In FIG. 4, solid lines indicate the flow of data, and wide arrows indicate control signals.

[Problem that the invention seeks to solve]

By the way, the conventional notification method shown in FIG. 4 requires two areas, an event management block (ECB) 23 and a return area 24, in nine communication areas. Therefore, not only does this communication area become large, but each interface requires two interfaces for these two areas, which creates the problem of having to have two interfaces for the communication area. .

The object of the present invention is that two such interfaces are required, and as described above, (1) setting a status value in the return area 24; ■It provides a task creation state notification method that makes it possible to perform in one step what previously required two steps: writing a waiting state release macro in the ECB-2 and releasing the requesting task from the waiting state. be.

[Means for solving problems]

In the present invention, as shown in FIG. 1, when there is a task generation request from the main task (request source task).

A PO8T macro (waiting state release macro) is issued along with a completion code that reports the generation status (normal or abnormal). These completion codes and PO8T macros are written into specific areas of the event management block. The requesting task identifies this and releases it from the waiting state, and also analyzes the completion code to determine whether it is normal or abnormal, and in the case of abnormal termination, distributes processing according to the content. Become.

[For production]

According to the present invention, the nine communication areas include the event management block (
Since only the ECB area is required and there is no need for a return area as in the past, the communication area can be made smaller and only one interface is required. Moreover, since the process of notifying the task generation status and releasing the requesting task from the waiting state are performed simultaneously (by writing them in the BCB), this can be done in one step.

〔Example〕

An embodiment of the present invention will be described with reference to FIG. 2 and other figures.

(1) Configuration of Embodiment FIG. 2 is a configuration diagram of an embodiment of the present invention. In the figure, 1 is the main task, 2 is the management task, and 3 is the event management block (BCB).
) is a multi-communications area.

In order to request task generation to the management task 2, the main task 1 includes a request section 1-1. Completion receiving unit 1-2 that determines whether task generation is completed based on data entered in section ECB-2 of event management block 3. An inspection unit 1- that checks the status value in the ECB-2 when the task generation is completed to check whether the task generation has been performed correctly.
3rd class is provided. The completion reception unit 1-2 reads the data of the ECB-2 and repeats the determination process until task generation is completed.

The management task 2 includes a reception unit 1-1 that determines whether or not there is a task generation request based on the data of the ECB-1.
Similar to the task generation unit 20-2, a task generation unit 2-2 generates a new task by preparing the environment until the new task operates, and a task generation unit 2-2 receives the result from the task generation unit 2-2. A determination unit 2-3 that converts the status value into a value, and a status/completion notification unit 2-4 that writes and displays the status value and the completion of task generation in the ECB-2 to notify the status value and the completion of task generation. There is. The reception unit 2-1 reads the FliCB-1 and repeats the determination process until a task generation request is received.

(2) Operation of the embodiment When the main task 1 needs to generate a subtask (new task) as it performs data processing, the requesting unit 1-1 of the main task 1 sends the request to the ECB-1. Enter. The requesting task remains in a waiting state until task generation is completed.

The reception unit 2-1 of the management task 2 identifies the task generation request by looking at the ECB-1, and transmits it to the task generation unit 2-2. Accordingly, the task flow generation unit 2-2 creates an environment for the new task to operate, such as creating a new task control block (TCB) and connecting it to the TCB queue, and generates the new task.

The task generation unit 2-2 then reports to the determination unit 2-3 whether such generation result is normal or abnormal.

The determining unit 2-3 receives the result from the task generating unit 2-2, and if it is normal, it outputs a status value (completion code) indicating it.
In the case of an abnormality, it is converted into a status value (completion code) indicating what kind of abnormality it is.0 This status value is transmitted to the status/completion notification unit 2-4, so the status/completion notification unit 2-4 notifies ECB-2 of the state value and completion of task generation, and sends this state value and PO
Write the 8T macro and perform processing to release the main task from waiting.

Since the completion receiving unit 1-2 of the main task 1 checks the ECB-2 until the task generation is completed, the BCB-
When the above-mentioned information is entered in 2, it is read out and the waiting state is released. At this time, the status value is decoded by the inspection unit 1-3 to determine whether it is normally generated.

Is it abnormal? If so, the abnormal state is determined and the corresponding work 2-processing is distributed.

Although the above explanation deals with the case where the main task requests the generation of a status flow, the present invention is of course not limited to this, and there may also be a case where a request to generate a status flow is made by a PL/I task that has already been generated. The same is true.

〔Effect of the invention〕

According to the present invention, in the conventional case, the event management block EC
It requires two communication areas, B and return area, and therefore requires two Ink 7 Aces for these, making the configuration complex and requiring a wide communication area.Furthermore, a completion code is required for the return area. Set up B.
The disadvantage of having to enter the PO8T macro to release the wait state for the CB is now that you just need to enter the completion code and the wait state release macro in the ECB, so you only need one Inter7Ace. Furthermore, the communication area can also be made smaller. Furthermore, a completion code and a waiting state release macro can be written in one step.

[Brief explanation of drawings]

FIG. 1 is a diagram showing the principle of the present invention. FIG. 2 is a configuration diagram of an embodiment of the present invention. Figure 3 is a multitasking configuration diagram. FIG. 4 shows a conventional task generation status notification method. In the figure, 1...main task. 2... Management tasks. 3...Event management block.

Claims (1)

[Claims] A task generation request source task and a management task (2),
In a data processing method in which a management task processes a task generation request and the task that is the source of the task generation request is placed in a waiting state when the task request is made, the management task (2) has the following:
In addition to providing a reception means, a task generation means, a determination means, and a status/completion notification means, a communication means (3) is provided in which requirements, commands, etc. are entered, and the task that requests task generation is provided with the communication means. A completion reception unit is provided which reads out the items entered in the task information and performs control accordingly, and writes the status and standby state release signal in accordance with the task generation result into the communication means and performs processing accordingly. A task generation status notification method characterized by the following.