JPH06195249A - Name designation method - Google Patents

Abstract

PURPOSE:To eliminate the need of adjusting a job application depending on individual environment, to reduce work man-hour by adjustment and to prevent the occurrence of errors by describing a part depending on the environment of the job application by a virtual name, previously generating an execution definition file where the virtual name and a real name are defined, substituting the virtual name of the job application for the real name at the time of execution and execution it. CONSTITUTION:The job application 2 where the part depending on used environment is described by the virtual name and the execution definition file 3 where the correspondence of the described virtual name and the real name is previously defined are provided. At the time of using the job application 2 under prescribed environment, the virtual name concerned is substituted for the real name by referring to the execution definition file 3 under designated environment as to the virtual name described in the job application 2, and a job application 4 which can be executed is made. Then, it is executed.

Description

Detailed Description of the Invention

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a name designating method for designating a name used in a business application.

[0002]

2. Description of the Related Art When operating an application system on a plurality of different hardware environments, a job control language (JC
L) It is necessary to individually create the correspondence between the logical device of the program specified on the above and the physical device according to the environment of the hardware actually operated.

Therefore, when the business application created at the headquarters is loaded and used in the computer of each business office, the job control language (J
The business application described in (CL) was changed for each business office. For example, in the case of the process of linking with each sales office via the head office and the line, change the ID, change the file name of the headquarters, and change the FPD device number for the part using the FPD for each sales office. I was going.

[0004]

As described above, when operating on hardware with different environments (for example, a computer of each sales office), the correspondence between the logical device and the physical device of the business application specified on the job control language. For business applications created under the test environment of the headquarters, it is necessary to individually change according to the environment of the hardware operating there.The work man-hour increases in proportion to the number of business application installations, and the maintenance man-hour also increases. There has been a problem that an increase in the number of errors and an error caused by individually changing the numbers cause troubles.

The present invention solves these problems.
Describe the part that depends on the environment of the business application with a virtual name and create an execution definition file that defines this virtual name and real name in advance, and replace the virtual name of the business application with the real name to enable execution. The purpose is to eliminate the need for rework of business applications that depend on the individual environment, reduce the number of man-hours required for rework, and prevent the occurrence of mistakes.

[0006]

[Means for Solving the Problems] Means for solving the problems will be described with reference to FIG. In FIG. 1, the business application 2 describes a part that depends on the environment in which it is used, with a virtual name.

The execution definition file 3 is a file in which correspondence between virtual names and real names is defined in advance. The executable business application 4 is an executable business application after the virtual name in the execution application 2 is replaced with the real name.

[0008]

As shown in FIG. 1, the present invention creates a business application 2 in which a part depending on the environment used is described by a virtual name, and an execution definition file 3 in which a virtual name and a real name are associated with each other.
When the business application 2 is used in a certain environment, the virtual name described in the business application 2 is referred to by referring to the execution definition file 3 of the specified environment. Is replaced with a real name to make the executable business application 4, and then the business application 4 is executed.

Further, one business application 2 in which a part depending on a user to be used is described by a virtual name is created, and an execution definition file 3 in which a virtual name and a real name are associated with each other is created, and the business application 2 is stored. When using on a user's computer, the virtual name described in the business application 2 can be executed by replacing the virtual name with the real name by referring to the execution definition file 3 of the specified user. After setting to application 4, it is executed.

Therefore, the environment-dependent part of the business application 2 is described by a virtual name, and an execution definition file 3 defining this virtual name and real name is created in advance, and the virtual name of the business application 2 is used at the time of execution. It becomes possible to execute by substituting the real name. As a result, it is possible to eliminate the need for rework of the business application 2 depending on the individual environment, reduce the work man-hours and prevent the occurrence of mistakes due to the rework.

[0011]

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS Next, the construction and operation of an embodiment of the present invention will be described in detail with reference to FIGS.

FIG. 1 shows a block diagram of an embodiment of the present invention.
In FIG. 1, a computer 1 performs various kinds of processing according to a program, and here is composed of a generator 11 and an execution unit 14 according to the present invention.

The generator 11 analyzes the business application 2 and replaces the virtual name with the real name, and is composed of an analysis unit 12 and a replacement unit 13. The analysis unit 12 analyzes one original business application 2 and finds a virtual name from a program described in the job control language (JCL). For example, it is described as a device virtual definition in the business application 2 of FIG.
・ The device virtual definition HICSID is found from @ HICSID @ surrounded by @.

In the replacing unit 13, the analyzing unit 12 uses the business application 2
With respect to the device virtual definition found from, the corresponding device actual definition is extracted from the predefined execution definition file 3 and replaced to generate the executable business application 4.

The execution unit 14 actually executes the executable business application 4. The business application 2 is an original business application, only one is created, and is composed of a business application program 21, a device virtual definition 22, a business virtual definition 23, and the like.

The business application program 21 is
It is a program that executes tasks and is a part that does not depend on the environment. The business application program 21 that does not depend on this environment is a business application 4 that can be executed as it is.
It is used as the business application program 41 that constitutes the.

Device virtual definition 22 and business virtual definition 23
Is a part that depends on the environment and is defined by a virtual name. This device virtual definition 22 and business virtual definition 2
3, the correspondence relationship between the device actual definition 42 and the job actual definition 43 is previously defined and registered in the execution definition file 3. As a result, for example, the execution definition file 3 for Nagoya
Is specified, the device virtual definition 22 and the business virtual definition 23 of the original business application 2 are automatically changed to the device definition 42 and the business actual definition 43 of the business application 4 for Nagoya.
Will be replaced by.

The execution definition file 3 is a device virtual definition 22 and a business virtual definition 23 in the original business application 2.
The device actual definition 42 of the designated area (for example, for Nagoya)
Also, the correspondence relationship to be replaced with the business actual definition 43 is created and registered in advance.

The business application 4 is an executable business application, for example, a business application for Nagoya, and is composed of a business application program 41, a device real definition 42, and a business real definition 43.

The business application program 41 is
This is the same program as the business application program 21 of the original single business application 2, and is a program that does not change depending on the environment.

The device actual definition 42 and the business actual definition 43 are
This is a part of the program that changes depending on the environment, and refers to the execution definition file 3 of the designated area (for example, for Nagoya) and replaces the device virtual definition 22 and the business virtual definition 23.

Next, the concept of the configuration of FIG. 1 will be described with reference to the conceptual explanatory view of FIG. (1) As one original business application 2, a program is created in which parts that change depending on the environment are described by virtual names (device virtual definition 22, business virtual definition 23).

(2) A virtual name of a part that changes depending on the environment of the business application 2 (device virtual definition 22, business virtual definition 2
3) corresponding to the real name (device real definition 42, business real definition 4
3) is registered in the execution definition file 3.

(3) The replacement process 25 is executed. This is to find the virtual name (device virtual definition 22 and business virtual definition 23) described in the original one business application 2 and refer to the execution definition file 3 for the virtual name found to find the real name ( Device actual definition 42, business actual definition 4
3) is taken out and replaced to create an executable business application 4.

As described above, one original business application 2 is created by describing the part that changes depending on the environment with the virtual name, and the virtual name and the real name are associated with each other and registered in the execution definition file 3. By referring to the execution definition file 3 of the designated area (for example, for Nagoya), the virtual name found in one original business application 2 is replaced with the real name, and the business application 4 of the execution format is created. Run. By this, if you create one original business application 2 and execution definition file 3,
It becomes possible to automatically create the business application 4 in the execution format by the replacement process 25 when using.

Next, the operation of the configuration of FIG. 1 will be described in detail with reference to FIG. 4 in the order shown in the flowchart of FIG. In FIG. 3, S1 creates a business application.
This is, for example, the original business application 2 (see FIG. 1) of FIG.
(The part of the business application program 21) is created.

In step S2, the device virtual definition 22 is created. This is a device virtual definition 2 as a part that changes depending on the environment.
Create 2. For example, the original business application 2 in FIG.
Create the device virtual definition of the part surrounded by the rectangle inside.

In step S3, an execution definition file for the user is created. This creates, for example, the test execution definition file 31 and the Nagoya execution definition file 32 shown in FIG. 4 as the user execution definition file 2. These execution definition files 31 and 32 define and register unique device virtual definitions for testing and Nagoya in association with the device virtual definition of the original business application 2 as shown in the figure.

In step S4, the generator is activated. This activates the generator 11 of FIG. 1 (the generator 11 including the analysis unit 12 and the replacement unit 13). S
5 starts searching for the business application 2. This corresponds to the activation of the generator 11 in S4, and the analysis unit 12
Starts searching for virtual names (device virtual definition 22, business virtual definition 23) from the beginning of the original business application 2 in FIG. 4, for example.

In step S6, it is determined whether there is a virtual definition. The virtual definition determines whether or not a character string enclosed by @ ... @ exists. If YES, the virtual definition was found, so S
Proceed to 7. On the other hand, in the case of NO, since the virtual definition was not found, the process proceeds to S12.

In S7, since the virtual definition is found in the original business application 2 in YES in S6, the business application 2
Get the label name from. As described on the right side, the @ HICCID @ surrounded by @ ... @ was found as a virtual definition from the business application 2, so the label name (virtual name) HIC
Take out the CID.

A step S8 searches for an actual definition corresponding to the label name. This searches for an actual definition corresponding to the label name (virtual name) extracted in S7. For example, as an actual definition corresponding to the above-mentioned label name HICCID, C5C0D20000 is searched for as an actual definition from the execution definition file 32 for Nagoya in FIG.

In step S9, the corresponding definition is retrieved. S10
Replaces the label of the business application 2. This is, for example, the label C5C0D20000 for Nagoya in FIG. 4 found in S8 and taken out in S9, replacing the part of the original business application 2 in FIG. App 4
Set to 2.

In step S11, the replaced line is output. As a result, for example, the line replaced with ″ of the business application 42 for Nagoya is output. In S12, it is determined whether it is END. YE
In the case of S, since the replacement processing has been executed up to the end line of the original business application 2, the business applications 44, 45, etc. replaced in S10 are saved. On the other hand, in the case of NO, since the replacement processing is not completed up to the end line of the original business application 2, S6 and subsequent steps are repeatedly executed for the next line.

As described above, for example, one original business application 2 shown in FIG. 4 is created and the execution definition file 3 is created.
In response to starting the generator 11 of FIG. 1 after creating 1, 32, virtual definition automatically from the first line of the business application 2 (here, the sentence enclosed by @ ... @)
Exists, retrieves the label name (virtual name) when it exists, refers to one of the specified execution definition files 31 and 32, and extracts the real name corresponding to this label name (virtual name). By repeating the replacement, the executable business applications 44 and 45 are created. As a result, it is possible to execute automatically by simply creating the original single business application 2 in which the part that changes depending on the environment is described by the virtual name, and creating the correspondence between the virtual name and the real name as the execution definition files 31 and 32. The business applications 44, 45, etc. can be created.

FIG. 4 shows a specific example of the present invention. In FIG. 4, the original business application 2 shows a part that changes depending on the environment.
It is described by enclosing it in @. Here, the line of the device virtual definition of is described as 0050 * / ID ID1 = @ HICSID @. Here, 0050 represents a line number.

* Represents an annotation line, and the label name (virtual name) line is always an annotation line. @ HICSID @ is @
... @ indicates the existence of the label name (virtual name), and the HICSID therein is the label name (virtual name).

Similarly, the same applies to the part that changes depending on the environment. The execution definition files 31 and 32 represent files for testing and for Nagoya, respectively. Here, the device virtual definition “H” of one original business application 2
For ICSID "and" RCVFILE ", real names for testing and Nagoya are registered as shown in the figure.

The generator 11 searches sequentially from the top line of the original single business application 2 to obtain a virtual name (@ ...
When a level name (enclosed in @) is found, the corresponding real name is extracted by referring to the specified execution definition files 31 and 32, and the business application 4 for testing and Nagoya is replaced.
Create 4, 45.

In the test business application 44, the portion of the virtual name (device virtual definition, etc.) of one original business application 2 is changed to the real name (device actual definition, etc.) by referring to the execution definition file 31. It was created by replacing it with ','.

The business application 45 for Nagoya uses the virtual name (device virtual definition, etc.) of one original business application 2 as a real name (device actual definition, etc.) by referring to the execution definition file 32. It is created by substituting ``, ''.

FIG. 5 is a diagram illustrating a specific example of the present invention. In FIG. 5, S21 is a business application program 21, a label J as the original business application 2.
UMP definition and virtual device name definition are performed. This is as a virtual device name definition. For example, when describing a HICS terminal ID by a label name, describe as * / ID ID1 = @ HICSID @.

Further, as the label JUMP definition, for example: When making a label jump with a SKIP command, * SIKP! END!・ ・ ・ ・ *! END! Is described so as to jump unconditionally to the label name END.

In S22, analysis and replacement are performed. This is a search for the original single business application 2 from the top line, and if the virtual device name definition is found (when @ ... @ is found), the specified execution is performed for the virtual device name definition. The definition file 3 is referred to and replaced with the real device name definition, and the business application program and the label JUMP definition in which the real device name is described are created as an intermediate business application as shown in S23.

In step S24, JUMP calculation is performed. this is,
The relative position of the JUMP command is calculated based on the label JUMP definition of S23, and the executable business application of S25 is obtained. As a result, the executable business application described in JCL has been created.

In step S26, the executable business application 2 is executed.

[0047]

As described above, according to the present invention,
An environment definition part of the business application 2 is described by a virtual name and an execution definition file 3 that defines this virtual name and real name
Is created in advance and the virtual name of the business application 2 is replaced with the real name at the time of execution, so that the business application does not need to be reworked depending on the individual environment, and the number of man-hours required for reworking Can be reduced and the occurrence of mistakes can be prevented. As a result, the developer can automatically create the business application 4 for each user only by creating one original business application 2 and the execution definition file 3 for each user. Bring

(1) The present invention can reduce the number of man-hours required for modifying the conventional business application 2 (job control language program) for individual environments. (2) Further, the workability of the modification is improved, and the system quality can be improved.

(3) Only one original business application 2 needs to be created by the developer, and maintenance man-hours can be reduced.

[Brief description of drawings]

FIG. 1 is a configuration diagram of an embodiment of the present invention.

FIG. 2 is a conceptual explanatory diagram of the present invention.

FIG. 3 is a flowchart for explaining the operation of the present invention.

FIG. 4 is a specific example of the present invention.

FIG. 5 is a diagram illustrating a specific example of the present invention.

[Explanation of symbols]

 1: Computer 11: Generator 12: Analysis unit 13: Substitution unit 14: Execution unit 2: Business application (original) 21: Business application program 22: Virtual device definition 3, 31, 32: Execution definition file 4, 44, 45 : Business application (for each user) 41: Business application program 42: Actual device definition ,: Virtual device definition ',' '', ',' ': Actual device definition

Claims (2)

[Claims] 1. In a name designating method for designating a name to be used in a business application, a business application (2) in which a part depending on an environment to be used is described by a virtual name, and correspondence between the described virtual name and a real name are provided. When the business application (2) is used in a certain environment, the virtual name described in the business application (2) has a predefined execution definition file (3). A method for designating a name, characterized in that the execution definition file (3) is referred to, and the virtual name is replaced with a real name to make an executable business application (4) and then executed. 2. In a name designating method for designating a name used in a business application, one business application (2) in which a part depending on a user to be used is described by a virtual name, and the described virtual name and real name An execution definition file (3) for each user, which defines correspondence in advance, is provided, and when the business application (2) is used by a computer of a user, the virtual description described in the business application (2) is used. Regarding the name, the execution definition file (3) of the specified user is referred to replace the virtual name with the real name to make the executable business application (4), and then the application is executed. How to specify the name.