JPS6015752A - Dd/d control information synchronizing system - Google Patents

Abstract

PURPOSE:To improve the data processing efficiency by excecuting the schedule processing to the reinput of a DD/D control list when the update of DD/D is carried out by a system after the execution of said update is recorded. CONSTITUTION:A control list controlling part 10 contains a reinput schedule part 31, a rereading processing part 32 and a composite system expanding part 33. The part 31 performs the schedule processing by a schedule request signal sent from a system at an end part based on the DD/D update. The part 32 gives an access to the DD/D and checks whether the reinput is scheduled when said access is requested. If the reinput is scheduled, the control list of the DD/D is read again and written to a memory. The part 33 gives a schedule request to all systems which are capable of communication with the inter-system communication procedure, etc. and requests the rereading of the DD/D. Then the part 33 confirms that all other systems are through with their schedules.

Description

DETAILED DESCRIPTION OF THE INVENTION [Technical Field of the Invention] The present invention provides data processing between multiple systems, DD/I'J (Data
Dict-4,onary/Directory)
When sharing the D D/D management book from one system, the other system updates the D D/D management book held within its own system every time this rewriting is performed. By holding update occurrence information without any data processing, it is possible to synchronize the D/D management information required for data processing.

[Conventional technology and problems]

For example, in an online data processing system, *source definition information for the entire system and its relationships are entered in a file called January)/D. This I month J/D includes definition information regarding database resources, information regarding the data communication system, and the name of the application program.

Various information such as attributes and operating conditions are stored.

The information stored in the DD/D, which shows what kind of information is stored in the DD/D, its storage location, registration date, etc., is said to be poorly managed.

This is made resident not only on the DD/D but also on the memory of the normal system as a DD/D management board. and DD/D
If there is an update to DD/D, the DD/D update program
DD/D in memory at the same time as updating the management list on D
The v-management book is also updated in synchronization.

However, as shown in FIG. 1, in the case of a composite 7-stem system in which DD/D 1 is shared by systems #1 to #4.

DD/D on the memory in each system #1 to #4
It becomes necessary to maintain the management j'ti31-M to 4-M. At this time, the terminal device 5 of system #11) D
When an update of D/D 1 is made and its management interface is also updated, the 671
M~4-M is also Kono tube, f! l! It must be updated by referring to Book 10. For this purpose, as shown in FIG. 1, in a complex system, in order to update the DD/D management (1) on each memory, the management (1-1) on each DD/Dj is updated.
It becomes necessary to access 0, and the purpose of the tree invention is to access I)
1) In order to solve the above problems when sharing the DI)/ , own system is DJ)/ ])
1)])/l When you need to access the management list
) DD/I in the own system according to the above management list)? I started modifying ¥Rirou and synchronizing its management information I)D
/L) y< layer information synchronization method.

[Structure of the invention]

To achieve this purpose, wooden inventions 1) 1. ) / In the D management information synchronization method, is it possible to manage DD/D? In a data processing method in which DD/D is held in the own system and DD/D is shared by multiple data processing devices, I) update indicating that the D/D management list has been updated by another data processing device. Information retention department and updated information? 1) an update information entry section that writes data into the storage section 14; a schedule transmission section that notifies other data processing devices when the management list of 1)/D is updated; and a schedule transmission section that reads out the update information storage section. It is equipped with a reading processing unit that accesses the DD/D management information when update information is written therein and updates the DD/D management information held in its own data processing device 1″l, and other data When the processing device updates the DD/D, the update information is held in the update information holding unit, and when the own data processing device accesses the DD/D and the above update information exists, it accesses the DD/D before management. The present invention is characterized in that the DD/D management list of its own data processing device is updated.

[Embodiments of the invention]

An embodiment of the misfire J will be described based on FIGS. 2 and 6.

FIG. 2 is a block diagram of one embodiment of the present invention, and FIG. 3 is a detailed diagram of its management control section.

In the figure, 10 is '/ stem 441 (7) fiy,
E! p (PJ control unit.

11 is a schedule section, 12 is a memory, 13 is a communication control section, 14 is an input/output section, and 2o is a system #2 management (
σ control unit, 21 is a schedule unit, 22 is a memory, 26
24 is a correspondence phloem and an input/output section.

Here, system IL1. #2 is the system in Figure 1'#
i, +2, which corresponds to IN)/1. )
This is a data processing device that shares 1.

The management 1υ control unit 10 reads/writes the DD/D1, reads/writes the schedule unit 11, or notifies other systems that DI)/l) 10 has been updated, etc. When the system of DI)/D 1 is notified that DI)/D 1 has been updated, this is recorded in the schedule section 11, and when DI)/I) 1 is referenced, the management list 1-0 is saved in the memory 12. ) to make reservations for input.

The management book control unit 10 has the same configuration as the system 112 (11 book control unit 20), so in FIG. .

The management book control unit 10 includes a tannin card schedule unit 31, a reread processing unit 52. '4t7 is created by the complex system extension section Roro, and the complex system extension section 53 further sends the schedule request section 54. Completion synchronization processing unit 65. Schedule request receiving section 36. It has a schedule completion notification section 37 and the like.

Here, the re-input schedule section 31 records, for example, "1" in the schedule section 11 in response to a schedule request signal sent based on the DD/D update from another system, and indicates that the DD/ and DI are updated by the other system. Therefore, when there is a definition program information reference request from the own system, the DD/I
This schedule process is to re-input the management list 1-0 of D into the memory.

The reread processing unit 52 id accesses the DD/D, and each time this access request is made, it checks whether the above re-input is scheduled. If scheduled, the DD/D management list 1-0 is reread and written into the memory before processing the access request.

The complex system expansion unit 56 sends a schedule request to all systems that can communicate using an inter-system communication procedure, etc.
This is to request a D/D oDffiZ fix and confirm that all other systems have completed their schedules. Schedule request unit 34 that requests schedules from other systems. All systems receive schedule completion notifications sent back from other systems in response to schedule requests.

- Completion synchronization process to confirm that the file is completed py i'
i+55, when there is a schedule request from another system, it receives it and sends 11 copies of the re-entry custom schedule 1
Schedule request receiving unit 36. 5tar to schedule part 11 with n person horn schedule HHi,
When the schedule processing is finished, select Kozo1 (l1tl■)
It has a schedule completion notification section 37 that notifies the system.

The memory 12 stores a DD/D management list.

The communication control section 13 performs communication control between system #1 and other systems [F].
The schedule unit 21 in system #2 is for transmitting signals to other systems and receiving signals transmitted from other systems. memory 22
9 communication control unit 23. The input/output section 24 includes the schedule section 111, the memory 129, the communication control section 13. Since it is the same as the input/output section 14, its explanation will be omitted.

Next, the operation of the present invention will be explained with reference to FIGS. 2 and 3.

(1) When data is updated on DD/D 1 in system #1, DD/D 1 management book 1-0
is updated. Then, the schedule requesting section 34 of the management thin control section 10 sends a schedule requesting section M. This schedule request signal is sent to the communication control unit 13. Input/output section 1
4 to the management book control unit 20 of the system 4f2.

(2) In the management thin control unit 2o of 7 stem #2, this is received by the schedule request receiving unit, records “1” in the schedule unit 21, and stores it in the memory 2 of system #2.
The re-input schedule unit performs a schedule process to correct the DD/D management unit stored in 4G in d+, and when this schedule process is completed, the schedule completion notification unit sends a completion report. In the management PI control unit 10 of system #1, the completion synchronization processing unit 65 receives this and confirms that the scheduling in the other system has been completed, and then executes the DI in the own system.
Schedule for inputting +/n into memory 12
I-4 Prefecture carp performance.

(3) Then in system 4t2 DI)/I)
For example, when there is an access request for 1 and a request for reference to definition program information, the rereading processing unit calls the schedule unit 21.
Recognize that the schedule is being processed. The rereading processing section is the country)/I) management record 1-
0 is read and inputted into the memory 22 +Tj. As a result, the J)1)/1) management list in the memory 22 is updated. Therefore, it is possible to obtain the necessary data by using this history ψ1 and the DD/D management book.

+41 On the other hand, when there is a DI)/D access request in system #1, the rereading process j'T+i 32
activates the schedule section 11 and makes g& indicating that schedule processing is being performed. Due to this / Sudem IL1
However, the same control as in (3) above is performed, and the memory 12
Management of DD/D that was first updated by own/stem y3
1-o will be re-entered.

Indicates that the DD/D has been updated in this way.D
D/D tube 1jii Each system retains data that schedules hub re-input, and when that system accesses the DD/D management ai, re-inputting this data allows the DD/D to be updated at that time. The contents can be the same as the management book.

In the present invention, if processing of %:[n of DD/D was performed at one ratio with DD/D update, there would be a problem in processing efficiency when Dll/D update occurs frequently, so this update was made. 2J (When you receive the elephant, add the DD/D management book +I
Please note that this must be revised. The actual processing is performed only when it is necessary to check whether it is necessary to reread the DD/D management list as part of the processing for reading the DD/D members. By doing so, it is possible to reduce the number of times the DD/D management record is rewritten, and it is also possible to shorten the synchronization processing time when rereading the DD/D management list.

〔Effect of the invention〕

According to the present invention, when a DD/D is shared by a plurality of systems (data processing devices), one cystine can be used as a DD/D.
When D is updated, it is recorded that the update has been made and DI) / D management? ' By processing the seven phase inputs on a schedule, the own system manually updates this to the latest version when it is necessary to access I)I)/Dγf(j), so January )/D Each time the IJI of each system is updated)/1) 9'i)□
・So! I! There is no need to update, and data processing efficiency can be improved.

[Brief explanation of the drawing]

Fig. 1 is an explanatory diagram when a DD/D is shared by multiple data processing nodes, Fig. 2 is a configuration diagram of an embodiment of the present invention, and Fig. 3 is a detailed diagram of the management ρ1 control unit, 5111ψ1. Ruru. In the figure, 1 is DD/D, 10 is 'f-4 theoretical control 1Il
11 is a schedule section, 12 is a memory, 15 is a communication control section, 14 is an input/output section, and 20 is a management thin control section. 21 is a schedule section, 22 is a memory, 23 is a communication control section, and 24 is an input/output section. Patent applicant Fujitsu Ltd. Representative Patent Attorney Akira Yamatani

Claims (1)

[Claims] D D
In a data processing system in which a D/D is shared by multiple data processing devices, there is an update information entry section that indicates that the DD/D management list has been updated by another data processing device, and a data storage section that stores data in the update information holding section. an update information entry section for entering D.
A schedule transmission unit that notifies other data processing devices when the D/D management is updated, and a schedule transmission unit that reads the update information holding unit and updates the D/D when update information is written therein.
It is equipped with a reading processing unit that accesses the D/D management book and updates the D/D management information held in its own data processing device. When another data processing device updates D/D, the update information is held in the update information holding unit, and the own data processing device
A DD characterized in that when the D/D is accessed and the update information exists, the DD/D management V+'j is accessed to update the DI)/D management list of the own data processing device. /D management information synchronization method.