JPH01316093A - Checking device for call processing program - Google Patents

Abstract

PURPOSE:To correctly check the macro-parameter data of a call processing program by reading the macro-data of a call processing program, and comparing and checking them with macro-parameter pattern data. CONSTITUTION:The prepared call processing program is held 1, and the respective macro-parameter pattern data of the call processing program are held 2. Further, the macro-data of the call processing program is read from the holding part 1, compared with the corresponding macro-parameter pattern data in the holding part 2, and they are processed 3. Consequently, the inconsistency between the parameters can be checked.

Description

[Detailed Description of the Invention] [Summary] An object of the present invention is to provide a call processing program checking device that can accurately check the parameter data of a created call processing program macro, regarding a call processing program checking device used in an exchange. A call processing program holding unit that holds the created call processing program, a parameter pattern data table holding unit that has a table of parameter pattern data of each macro of the call processing program, and a call processing program holding unit that holds the created call processing program. The configuration includes a check processing section that reads out the macro and checks it by comparing it with the parameter pattern data of the corresponding macro in the parameter pattern data table holding section.

[Industrial application field]

The present invention relates to a call processing program checking device for checking whether a created call processing program used in an exchange is correct.

[Conventional technology]

Figure 4 is a diagram showing a macro parameter pattern data table of an example call processing program, Figure 5 is a diagram showing the relationship between parameters and parameter values of an example call processing program, and Figure 6 is a diagram showing the relationship between parameters and parameter values of an example call processing program. It is a figure which shows the macro salt of a processing program, and the parameter data created.

As shown in Figure 6, the call processing program macros include the state number setting macro %CCN5T, the call control data work area acquisition release macro %CDBWC, the terminal release macro %TIDLM, and the trunk acquisition macro %. T
)-I NTM or % of a task end processing macro.
TSKFL, etc., and FIG. 6 shows the created first to third parameter data corresponding to each macro. Note that the parts marked with * are incorrect.

The parameter pattern data for these macros is as follows:
As shown in FIG. 4, there are some cases in which there are multiple types.

For example, in the parameter pattern data of %CCN5T, as a pattern PTI, the first parameter P1 has 5CCN indicating the case of transitioning to its own module.
As a pattern PT2, write the PCCN that will transition into your own module and other modules in the first parameter P1, write the module number 1 to 255 that will transition to the second parameter P2, and write 3. The transition state number O to 31 is written in the th parameter P3, and the pattern PT3 is the 1st parameter P1.
In , write the PCCN that will transition into your own module and other modules, in the second parameter P2 write NIL that indicates the module that will transition, and in the third parameter P3 write the state number to transition to. There are some that write numbers 0-31.

In addition, in the parameter pattern data of %CDBWC, as a pattern PTI, the first parameter P1 is written with R3T indicating release, and the second parameter P2 is 1 to 15 indicating the area number of the work area to be released. something that writes
In the pattern PT2, SET indicating reservation is written in the first parameter P1, and 1 to 15 indicating the area number of the work area to be secured is written in the second parameter P2.

Some of the parameters of the call processing program have parameter values, and this relationship is shown in FIG.

Conventionally, an assembler was used to check whether the parameter data of each macro in a created call processing program was correct.

When checking with this assembler, for example, the 6th
As shown in the first section of the figure, if the parameter data for macro salt %CCN5T is written as 5CCN, 1.2, then in order to express it numerically, 5CCN is converted to O from the table in Figure 5, and the parameter data is is set to 0.1.2.

Next, in order to numerically express the parameter pattern data of macro salt %CCN5T in Figure 4, from the table in Figure 5, the first parameter is 5CCN or PCCN, so O or 1, and the second parameter is NIL. or 1 to 255, the third parameter is NIL or 0 to 31, and the pattern data is set, the first parameter is 0 or 1. or O~31.

And the first parameter data created.

The second and third data 0 and 1.2 are compared with the first, second and third parameters of the parameter pattern data, respectively, and it is sufficient that they match.

Therefore, this parameter data of 5CCN, 1.2 is good regardless of whether it is not included in the parameter pattern data of macro salt %CCN5T.

Also, if the pattern data of macro salt %CDBWC in item 2 of Figure 6 is 5Top and 1, then this numerical expression is 0.
, 1.

Also, if the parameter pattern data of macro salt % CDBWC in Figure 4 is expressed numerically, the first parameter is O or 1, and the second parameter is 1 to 15, so 5T.
Parameter data of OP, 1 is macro salt %CDBWC
It is a good thing regardless of whether it is not in the parameter pattern data.

61 [Problem to be solved by the invention] In other words, in the conventional method, it is possible to check the allowable values of individual parameters, but it is not possible to check for inconsistencies between parameters, and there is a problem that it cannot be checked accurately. .

SUMMARY OF THE INVENTION An object of the present invention is to provide a call processing program checking device that can accurately check macro parameter data of a call processing program.

[Means to solve the problem]

FIG. 1 is a block diagram of the principle of the present invention.

As shown in FIG. 1, there are a call processing program holding section 1 that holds a created call processing program, a parameter pattern data table holding section 2 that has a table of parameter pattern data of each macro of the call processing program, and a call processing program holding section 2 that holds a created call processing program. A check processing section 3 is provided which reads a macro of a call processing program from the program holding section 1 and compares it with the parameter pattern data of the corresponding macro in the parameter pattern data table holding section 2 for checking.

[For production]

According to the present invention, the check processing section 3 reads out the macro of the tricked call processing program from the call processing program holding section 1 and
Since it is checked by comparing it with the parameter pattern data of the corresponding macro, it is possible to check for inconsistencies between parameters and to perform accurate checking.

〔Example〕

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

FIG. 2 is a block diagram of an embodiment of the present invention, and FIG. 3 is a flowchart of a program of the check processing section of the embodiment of the present invention.

The call processing program holding unit 1 shown in FIG. 2 holds the created call processing program, and the parameter table holding unit 4 contains a table showing the relationship between parameters and parameter values of the call processing program shown in FIG. It holds
The parameter pattern data table holding unit 2 includes a fourth
It holds a macro parameter pattern data table for the call processing program as shown in the figure.

The check processing unit 3 has a program shown in FIG.
According to this program, each macro of the created call processing program is checked, so if you follow the program shown in Figure 3 and write 5CCN, 1.2 as the parameter data for the macro name %CCN5T in Figure 6, and the macro Name%CD] 5TOP as parameter data of 3WC
, 1 will be described below as an example.

In step 1 of Fig. 3, the parameter data 5CCN, 1.2 created by the macro name %CCN5T is extracted, and in step 2, i = 1, and in step 3, the first parameter 5CCN is set as shown in Fig. 4. Check whether it is in the first parameter of macro name %CCN5T in the parameter pattern data table.

Since it is, proceed to step 8. Since it is not the last parameter, i = 2 in step 9. In step 3, the second parameter 1 is set in the second parameter of the parameter pattern data table in Fig. 4. See what's in there.

Since it is, proceed to step 8. Since it is not the last parameter, i = 3 in step 9. In step 3, the third parameter 2 is included in the third parameter of the parameter pattern data table in Fig. 4. See if there is one.

Since there is, the process proceeds to step 8. Since this is a parameter of H&, the process proceeds to step 12. Since the warning flag is not set, the process proceeds to step 14.

Here, from the table shown in Figure 4, the macro name %CCN5
Take out the parameter pattern data of PTl of pattern 1, PT2 of pattern 2, and PT3 of pattern 3 of T,
In step 15, set j=1, in step 16, take out the first parameter 5CCN for the pattern PTI, and in step 19, take out the first parameter 5C created
It is compared with CN, and since they are equal, the process proceeds to step 20.

Since this is not the last parameter, i=2 is set in step 21, and the second parameter NIL of the pattern PTI is extracted in step 18 and compared with the created second parameter 1.

Since they are not equal, proceed to step 22, and since PTl is not the last pattern, set j = 2, extract pattern PT2 in step 16, set i = 1 in step 17,
In step 18, the first parameter PCCN for pattern PT2 is extracted and compared with the first parameter 5CCN created in step 19.

Since they are not equal, proceed to step 22, and since PT2 is not the last pattern, set j = 3, extract pattern PT3 in step 16, set i = 1 in step 17,
In step 18, the first parameter PCCN for pattern PT3 is extracted and compared with the first parameter 5CCN created in step 19.

Since they are not equal, the process proceeds to step 22, and since PT3 is the last pattern, the process proceeds to step 24, where a warning is output that the parameters of the created macro are incorrect.

Next, in the case of 1, macro name %CDBWC, take out the parameter 5TOP, 1 created in step 1, set it to i-1 in step 2, and change the first parameter 5TOP in step 3 to the parameter in Figure 4. Check whether it is in the first parameter of the macro name %CDBWC in the pattern data table.

Since there is no
Check if there is a parameter value for TOP. In this case, it is 0, so proceed to step 5 and convert 5TOP to 0.

Then, in step 6, it is checked whether the parameter for O is among the first parameters in the table of FIG. Since this is R3T, proceed to step 7, convert O to R3T, set a warning flag, and proceed to step 8.

In step 8, check if this is the last parameter,
Since it is not the last parameter, proceed to step 9 and set i=
2 and return to step 3.

= 11- In step 3, it is checked whether the second parameter 1 is in the second parameter of the parameter pattern data table of FIG. Since there is, go to step 8, and this is the last parameter, go to step 12,
Since the warning flag is set, a warning is issued in step 13 that, for example, 5TOP is not allowed as the first parameter of the macro name %CDBWC.

Then proceed to step 14.

The pattern R3T, 1 is the pattern P of the macro name %CDBWC in the parameter pattern data table in Figure 4.
Since it is in TI, step 15 to step 21 are set to i=2.
The process ends at step 20.

In this way, the parameters of the created macro are checked by comparing them with the parameter pattern data of the corresponding macro, so the checks can be made accurately.

= 12- [Effects of the Invention] As explained in detail above, according to the present invention, the parameters of the macro created by the call processing program are checked by comparing them with the parameter pattern data of the corresponding macro.
This has the effect of allowing accurate checking.

[Brief explanation of the drawing]

Fig. 1 is a block diagram of the principle of the present invention, Fig. 2 is a block diagram of an embodiment of the invention, Fig. 3 is a flowchart of a program of the check processing section of the embodiment of the invention, and Fig. 4 is a call diagram of an example. Figure 5 is a diagram showing the parameter pattern data table of the macro of the processing program. Figure 5 is a diagram showing the relationship between the parameters and parameter values of an example call processing program. Figure 6 is the macro name of an example call processing program and the created one. FIG. 3 is a diagram showing parameter data. In the figure, 2 indicates a call processing program holding section, 2 indicates a parameter pattern data table holding section, 3 indicates a check processing section, and 4 indicates a parameter table holding section.

Claims (1)

[Claims] A call processing program holding unit (1) that holds the created call processing program, a parameter pattern data table holding unit (2) that has a table of parameter pattern data of each macro of the call processing program, and the call processing program holding unit ( A call processing program characterized in that it has a check processing section (3) that reads a macro of the call processing program from 1) and checks it by comparing it with the parameter pattern data of the corresponding macro in the parameter pattern data table holding section (2). checking device.