JPH0390941A - Journal control system - Google Patents

Abstract

PURPOSE:To faciliate the development of a user application program which is used for processing the journal information by merging the journal information acquired via plural scattered media with each other and giving these journal information to the user application program based on the actual acquiring order. CONSTITUTION:A user application program interface part 1181 receives a request from a user application program 117 via a parameter list, for example, and analyzes the contents of the request. Then the part 1181 gives the process requests to a journal information input part 1182 and a journal information merging part 1183 and then transfers a return code showing the process result and the journal information obtained from a merging process to the program 117. The part 1183 has a function to merge the journal information received via a journal information input part in the acquiring order. In such a constitution, an acquiring medium of the journal information is not required to be conscious of its constitution and the merging process. Then the development of a program is faciliated.

Description

DETAILED DESCRIPTION OF THE INVENTION [Industrial Application Field] The present invention relates to a data processing system, and relates to a data processing system, in which journal information is distributed and acquired on multiple media in a complex subsystem type online system or a single online system. Regarding management methods.

[Conventional technology]

As a method for merging journal information in a complex subsystem type online system, for example, Japanese Patent Laid-Open No. 63-2
There is a method shown in Publication No. 01846.

[Problem to be solved by the invention]

The above conventional technology is only concerned with merging journal information that has been distributed and acquired in multiple media by an online system, and is concerned with reducing the burden on the user abridgment program that inputs and processes the journal information. is not taken into account. Therefore, in order for a user application program to process journal information, the user application program must be aware of the journal information acquisition medium and its structure when performing merging processing, which places a significant burden on program development. There was a problem.

In addition, there is a method in which journal information that has been distributed and acquired on multiple media is merged and reacquired on another medium, and the newly created journal information is input to the user application program. There was a problem in that it became necessary to perform an operation to re-acquire the data to a medium, which placed a burden on the operator.

An object of the present invention is to facilitate the development of a user application program that processes journal information without increasing the burden on the operator.

[Means to solve the problem]

The above object is achieved by a journal management method that merges journal information obtained in a distributed manner on a plurality of media and passes the merged journal information to a user application program in accordance with the actual order of acquisition.

[Effect]

A user application program that processes journal information by merging journal information obtained in multiple media and passing it to the user application program in accordance with the actual acquisition order can be configured to There is no need to be aware of merge processing, making program development easier.

〔Example〕

An embodiment of the present invention will be described below with reference to the drawings.

FIG. 1 shows an example of the overall configuration when the present invention is implemented in a complex subsystem type online system. The computer system Chimney] and the computer system 12 are connected by CTCA (interchannel coupling device) ↓3 as a system communication means. Computer system 1↓ has an operating system 111.1 complex subsystem controller 112 that controls one subsystem. The subsystems under the control of the composite subsystem controller 112 include a data communication system DCI: 115 with online terminals 1151, 1152, and a database system DB↓: 116 with a database 1161.

The composite subsystem controller 112 executes a user ablation program API: 113. AP2: ↓14
The history information is managed by journal information acquisition medium 1.
It was acquired on 121.1122. Computer system 12
Similarly, the operating system 121. Composite subsystem controller 122. Online terminal 125
Data communication system DC2 with 1.1252:125. There is a database system DB2:126 having a database 1261, and a composite subsystem controller 122 has user application programs AP4:123. It manages AP5:124 and acquires B layer information to journal acquisition media 1221.1222. Additionally, the computer system 11 includes a user application program AP3:117 which is outside the control of the composite subsystem controller 112 and is started by the user application program AP3:117 for processing journal information, and which acquires journal information in accordance with its requests. Medium 1121.1122,12
Journal merge program JM that inputs journal information from 21, 1222, merges it with the actual acquisition order, and passes it to the user application program AP3:117
There is P:118. In FIG. 1, the journal merge program JMP: 118, which operates independently of the composite subsystem controller 1-roller 112, allows the user application program AP3: 118 to
However, by providing the composite subsystem controllers 112 and 122 with a function similar to that of the journal merge program JMP:118, it is possible to process the journal information of user application programs under their control. An embodiment that enables processing as input is also possible. Furthermore, although FIG. 1 shows an embodiment of the present invention in a complex subsystem-type online system distributed over multiple computer systems, there are multiple online systems in one computer system,
If each obtains journal information on different media,
Alternatively, even when journal information is distributed and acquired on multiple media using a single online system, the same function as the journal merge program JMP:118 in Figure 1 can be achieved by inputting multiple journal information acquisition media. By doing so, embodiments of the present invention can be considered.

FIG. 2 shows a functional configuration diagram of the journal merge program JMP:118 in FIG. 1. User application program AP3:117 and journal information acquisition medium 1121゜1122.1221,12 in FIG.
22 represents the same symbol in FIG. The user application program interface unit 1181 is
When a request from the user application program AP3:117 is received, for example in the form of a parameter list, the content of the request is analyzed and a processing request is made to the journal information input section 1182 or the journal information merging section 1183. At step 117, a return code representing the processing result and journal information obtained as a result of the merge processing are delivered. The journal information input unit includes journal information acquisition media 1121, 1122,
Manual input of journal information from 1221 and 1222, pre-input processing, post-input processing, and format check of input journal information. Journal information acquisition medium 1
221.1222 is connected to a computer system 12 different from the computer system Chimney 1 on which the journal merge program JMP:118 operates in FIG.
When inputting journal information via the A (interchannel coupling device) 13 and when using a medium on the computer system 1 that is not in use while the composite subsystem controller of the computer system 12 is operating, the journal merge program JMP: 118 There may be cases where the user directly inputs journal information. The journal information merging unit 1183 has a function of merging the journal information input by the journal information input unit in the acquisition order.

FIG. 3 is an example of a processing flow when the user application program 117 of FIG. 2 inputs journal information using the journal merge program 118. In this example, user application program 1
17 to the journal merge program 118, the INIT request 32.17 is used to set the operating environment of the journal merge program 118. GET request 39. Requests delivery of the log code of journal information after input merging. Three types of requests are set: and TERM request 50 for notifying the end of journal information input processing. Transfer of information from the user application program 117 to the journal merge program 118 at the time of issuing each request, return code representing the result of each request processing from the journal merge program 118 to the user application program 117, and the route of journal information after input merging. The code is transferred via a parameter list created by the user application program 117 when each request is issued. The flow of processing when inputting journal information will be explained using FIG. First, the user application program 117 creates a parameter list for an INIT request and issues a 31° INIT request.The journal merge program 118 analyzes the passed parameter list when control is transferred from the user application program 117. When it recognizes that the request type is an NIT request, it performs input pre-processing such as creating and initializing a processing table necessary for inputting journal information.
．． If input conditions are specified in the parameter list, such as inputting only journal records with certain key information, those input conditions are set as the operating environment35, and the processing results are used as return codes in the parameter list. 36 and enter the user application program 117. The user application program 117 determines the INIT request code and 37. If it does not return normally, it will terminate abnormally at 55.
If normal, create parameter list l- for GET request 38 and issue GET request 39. , the journal merge program 118 analyzes the parameter list passed from the user application program 117 and performs 40. When it recognizes that it is a GET request, it inputs the journal information from the acquisition medium 41, checks the format of the input journal information 42, and merges the journal information 43. For merging journal information, for example, refer to JP-A-63 There is a method shown in Japanese Patent No. 201846, but its details are omitted here. Also, depending on the merge method, journal information input 41 may be performed multiple times for one GET request, or may be performed once.
The number of times it is performed is generally not constant. As a result of merging, the log code of the journal information to be delivered to the user application program 117 is
It is determined by taking into account the conditions set at the time of the NIT request, and is set in the record receiving area in the parameter list 44.
The processing result is also set in the parameter list as a return code 245, and the user application program 117
Return to . User application program 11
7, the GET request return code is determined 46, and if the return is not normal, it terminates abnormally 55, but if it is normal, the user application performs user-specific processing on the journal record set in the parameter list. The program 117 continues to run until it receives a journal information entry completion code from the journal merge program 118 or until the user's unique termination condition is met.
ET requests and processes for journal records are repeated 48. When all GET requests are completed, the user application program 117 creates a parameter list for the TERM request 49 and issues the TERM request 5
The 00 journal merge program 118 analyzes the parameter list passed from the user application program 117 51, and when it recognizes that it is a TERM request, performs post-input processing of journal information such as releasing the processing table area 52, and returns the processing results. It is set as a code in the parameter list 53 and returned to the user application program 117. The user application program 117 determines the TERM request return code 54, and if it does not return normally, terminates abnormally 55.
However, if it is normal, all processing is terminated normally 56. Note that the journal merge program 11 shown in FIG.
8, journal information input preprocessing 34, journal information input condition setting 35, journal information input 4
1. Format check of journal information 42. The journal information input post-processing 52 is performed by the journal information input section 1182 in the functional configuration diagram of FIG. 2, and the journal information merging section 1183 of FIG. All other processing of the journal merge program 118 shown in FIG. 3 is performed by the application program interface unit 1181 shown in FIG.

FIG. 4 shows an example of the parameter list of the third @ INIT request. When issuing an INIT request to the journal merge program 118, the user application program 117 creates a parameter list shown in FIG. 4, and transfers only the parameter address list pointer 41. The parameter address list pointer 41 points to a parameter address list in which addresses 42.46 of each parameter 43.47 are listed.
The final entry of the pointer is 1 on the first l pips 1-45.
(ON state), it is recognized. Parameter 43 pointed to by the first entry in the parameter address list
The request type is set to 1-, but the character string INIT is set when an INIT request is made. After the request type, a return code set area 44 is set where the journal merge program 118 sets a return code for the processing result. The parameter pointed to by the second entry 46 of the parameter address list is the character string C.
ON D 47, indicating that input conditions for journal information are set in the input condition area 48 that follows.

An example of the input condition is, for example, designating a specific key that a journal record has. The user application program (17) needs to clear the return code set area 44 before passing it to the journal merge program it8.

FIG. 5 shows an example of the parameter list of the GET request shown in FIG. The first entry 52 of the parameter address list pointed to by the parameter address list 1 to pointer 51 points to a character string GET 53 indicating that the type is a GET request, and after that, the journal merge program 118 processes There is a return code area 54 in which the return code representing the result is stored. The final entry 55 of the parameter address list is
It points to area 56 starting with the character string SET,
This means that the journal receiving area is specified. The area length of the journal record receiving area prepared by the user application program 117 is as follows.
It is set in area 57 following the character string SET. In the journal merge program 118, the code length of the journal record to be delivered to the user application program as a result of input merging of journal information is set in the record length area 58 in the parameter list I.

The user application program 117 sets the return code set area 54. before passing it to the journal merge program 118. Record length: 58° All information in the parameter list other than the journal record set area 59 must be set.

FIG. 6 shows an example of the parameter list of the TERM request of FIG. The first entry 63 of the parameter address list pointed to by the parameter address pointer 61 has the first bit 62 of 1 (ON state), indicating that it is also the final entry, and since the request type is a TERM request, the character string TERM It points to area 64 starting with . Also, Ritan Code Sera 1 to Area 65
is an area for the journal merge program 118 to set a return code representing the processing result. The user application program F must set all information in the parameter list other than the return code set area 65 before handing it over to the journal merge program 118.

〔Effect of the invention〕

According to the present invention, a user application program that processes journal information does not need to be aware of the acquisition medium of journal information, its structure, and merging processing, and has the effect that development can be facilitated by reducing the burden during program development. There is.

[Brief explanation of drawings]

Fig. 2 is a block diagram showing an embodiment of the present invention in a complex subsystem online system, and Fig. 2 is a functional block diagram of the journal merge program shown in Fig. 1, which is an example for realizing the present invention. , FIG. 3 is a process flow diagram of the user application program and journal merge program in FIG. 2 when inputting journal information, and FIG. FIG. 3 is an explanatory diagram showing an example of the parameter list for the INIT request, FIG. 5 is an explanatory diagram showing an example of the parameter list for the GET request in FIG. 3, and FIG. 6 is an explanatory diagram showing an example of the parameter list for the GET request in FIG. 3. FIG. 2 is an explanatory diagram showing an example of a parameter list. 11, 12... Computer system, 112, 122... Complex subsystem controller 1-roller, 11.21, 1,122, 1,221.1222...
- Journal information acquisition medium, 117... User application program, 1.18... Journal merge program, 1181... User application program interface section, 1182... Journal information input section, 1183...
Journal information merging section, 43...parameter,
53...Parameter, 56-59...Parameter area, 64...Parameter. An example of the draft: Figure zNrr $ - $'s rosemeck list － ~ 3I + Figure 5 Figure 1

Claims (1)

[Claims] 1. In a complex subsystem type online system that has multiple data communication systems and database systems as subsystems, or in a single online system, the journal information that has been distributed and acquired on multiple acquisition media is merged and the journal information is actually acquired. by passing it to the user application program in the order specified.
A journal management method that allows users to perform their own processing.