JPH0341848B2 - - Google Patents

Description

[Detailed Description of the Invention] [Summary] When there is a product A and a product B that internally uses the product A, a unique information area is provided for the product A, and the product B uses the function α provided by the product A. When the time has come to enhance the product, write information to that effect in the specific information area above, write a macro instruction to read the contents of the specific information area in product B, and write the information in the specific information area of product A in product B. This is a matching processing method when combining software that checks and matches the software.

[Industrial application field]

The present invention relates to a matching processing method for product A and product B, for example, a matching processing method for a relational database and a compiler.

[Conventional technology and problems]

FIG. 6 is a diagram illustrating a conventional example of matching processing between a PL/I compiler and a relational database. In Figure 6, version 10
Level 10 relational database,
A version 10 level 20 relational database is illustrated. A relational database has an identifier indicating its version and level. version 10 level 2
0 relational databases have X routines, and version 10 level 10 relational databases do not have X routines. When a compiler creates an object instruction sequence that calls an X routine in a relational database based on a source program created by a user, it is necessary to check whether the target relational database has an X routine. Therefore, as shown in Figure 7, the compiler checks whether the relational database is new (version 10, level 20 or not), and if yes, creates an object to call the X routine. ,
If No, do not create an object to call the X routine.

By the way, you can use PTF (Program
Temporary Fix).
When a program is modified using PTF, the version and level identifiers are not changed.
When a program is modified by PTF, the two become inconsistent, and when a user program attempts to use a newly added function of the relational database, the user program converted to machine language may abend. There is.

[Purpose of the invention]

The present invention is based on the above invention, and includes:
The object of the present invention is to provide a matching processing method when combining software, which makes it possible to easily check the consistency between program product A and program product B.

[Means to achieve the purpose]

Therefore, the consistency processing method during software combination of the present invention checks the consistency between program product A and program product B that internally uses program product A during software combination. A harmonization processing method in which a unique information area for the program product B is provided in the program product A, and the program product B performs some of the functions provided by the program product A. When the time comes for the product to be supported, a support level indicating this is written in the specific information area, a macro instruction is provided in the program product B to read the contents of the specific information area, and the program product This is characterized in that B reads the contents of the specific information area using the macro instruction and checks the consistency between them.

[Embodiments of the invention]

Hereinafter, the present invention will be explained with reference to Examples.
To summarize, the present invention has the following constituent elements.

(a) Create a specific information area for product B in product A, and product B
When the time comes to incorporate and support functions α, β, and γ provided by , the corresponding bit in the specific information area is turned on.

(b) Check the unique information area in product A in product B and ensure consistency.

FIG. 1 is a diagram for explaining the outline of the present invention. In FIG. 1, SDT indicates the specific information area of product B, and DLiB indicates the distribution library.
Product A is, for example, a relational database, and product B is a compiler.
Next, FIG. 1 will be explained. At the point in time, α, β, and γ functions are expanded to product A. Assuming that product B has built in a function that supports α at the point in time, a request is made to set information in the specific information area of product A (). Product B announces to the user that the function of α can be used by executing the PTF.

If the PTF of is implemented, the function of α can be used in t _z . If the user makes a mistake in the combination of conditions, the specific information area remains at 000 and the user program does not abend. However, Product B (compiler) outputs an appropriate error message when a user program requests to use the function of α. α to product B
Provided library DLib to support
In order to improve services, it is desirable to ship a PTF for writing 1 to the bit corresponding to α in the specific information area SDT at the same time. Note that in Figure 1, one bit is allocated to each of α, β, and γ, but if a 2-bit configuration is used and product B can support the function α, the unique information area will be
Write 01 to SDT, and if α and β functions can be supported, write 10 to the specific information area, α, β, γ
If the function can be supported, 11 may be written in the specific information area.

FIG. 2 is a diagram showing the relationship between a user program, a compiler, and a relational database. In FIG. 2, 1 is a user program, 2 is a PL/I compiler, 3 is a relational database, SDT 1 is a specific information area for COBOL, SDT is a specific information area for PL/I,
SDT3 indicates the specific information area for FORTRAN. A user code written in PL/I language containing instructions to use α's functions.
When compiling program 1, PL/I compiler 2 issues a predetermined macro instruction (this macro instruction will be explained in FIG.
Read the contents of , check whether information indicating that it can support the functions of α is written,
If Yes, an object instruction sequence for calling the function of α is created, and if No, an object instruction sequence for calling the function of α is not created.

FIG. 3 is a diagram showing the structure of the specific information area.
The specific information area for COBOL, the specific information area for PL/I, and the specific information area for FORTRAN are:
Each consists of 12 bytes, of which 4 bytes are actually used. This 4-byte area is divided into 4-bit units. The first four bits of the first byte are assigned to the operational function level, and the last four bits of the first byte are assigned to the database function level. The following is as shown.

FIG. 4 is a diagram showing an example of values of language functional level information. If COBOL and PL/I can support the public database function, '2'X (0010 in binary) is written in the operation level column (first half of the first byte) of the corresponding specific information area.
If FORTRAN can support the public database function, '1'X (2
0001) is written in decimal format. For example, the column protection function of a relational database also belongs to the operational level, and if COBOL and PL/I can support the column protection function in addition to the public database function, the column of the operational level of the corresponding specific information area is ''. 3'X (0011 in binary) is written,
If FORTRAN can support the column protection function in addition to the public database function, enter '2'X (2) in the operational level column of the corresponding specific information area.
0010) is written in decimal format. The fields of the last 4 bits of the first byte to the last 4 bits of the third byte are likely to be understood from the above explanation, so a description thereof will be omitted.

FIG. 5 is a diagram showing the description format of a linguistic information extraction macro for extracting linguistic information from the specific information area. The function of this macro instruction is to extract the specific information of the specified language from the specific information area SDT and return it. Next, the operands will be explained.

(a) RCOMAD (&RCOMAD) Specifies the address of the main control table (RCOM) of the RDB (relational database).

&RCOMAD:PTR(31) (b) LANG({CO｜PL｜FO}) Specify the language type.

CO: COBOL PL: L/I FO: FORTRAN77 (c) RTNAD (&RTNAD) Specifies the address of the 12-byte information return area.

&RTNAD:PTR(31) [Effect of the invention] As is clear from the above explanation, according to the present invention, product A has its own support level in product B, which prevents abend from occurring in the past. However, an appropriate message (indicating that the combination is defective) is now output, eliminating the need for troubleshooting.

[Brief explanation of the drawing]

Figure 1 is a diagram for explaining the outline of the present invention, Figure 2 is a diagram showing the relationship between a user program, a compiler, and a relational database, and Figure 3 is a diagram for explaining the outline of the present invention.
Figure 4 shows the structure of the specific information area, Figure 4 shows an example of the value of language functional level information, Figure 5 shows the description format of the language information retrieval macro, and Figure 6 shows the format of the language information retrieval macro.
FIG. 7 is a diagram illustrating a conventional example of matching processing between a PL/I compiler and a relational database, and FIG. 7 is a diagram illustrating a portion of the processing for creating an object instruction sequence that calls routine X in FIG. 6. 1...User program, 2...PL/I compiler, 3...Relational database, SDT1...Specific information area for COBOL,
SDT2... Specific information area for PL/I, SDT3
...Specific information area for FORTRAN.

Claims (1)

[Claims] 1. A harmonization processing method when combining software that checks the consistency between a program product A and a program product B that internally uses the program product A,
Providing a specific information area for the program product B in the program product A,
When the time comes for the above program product B to support some of the functions provided by the above program product A, a support level indicating this will be written in the above specific information area, and the support level will be written in the above program product B. A software set characterized in that a macro instruction for reading the content of the specific information area is provided, and the program product B reads the content of the specific information area using the macro instruction and checks consistency between the two. Matching processing method during matching.