Access support device for mainframe devices, access support terminal, mainframe device, access support system device, method for accessing mainframe devices, and program

Abstract

To provide an access support device to a main frame device which enables easy utilization of a resource in a main frame from an open system.SOLUTION: An access support device of the present invention includes: an access information acquisition unit which acquires access information including transaction identification information and input information; an access information analysis unit which analyzes the access information to extract the transaction identification information and the input information; an execution request generation unit which generates execution request information to a main frame device on the basis of the input information, the transaction identification information, and a transaction definition; and an execution request transmission unit which transmits the execution request information to the main frame device at an access destination identified on the basis of the transaction identification information and the transaction definition. The transaction definition is information obtained by linking resource identification information of a resource included in the main frame device and an execution order of the resource for each transaction identification information.SELECTED DRAWING: Figure 1

Description

Technical Field

[0001] The present invention relates to an access support device for a mainframe device, an access support terminal, a mainframe device, an access support system device, a method for supporting access to a mainframe device, and a program.

Background Art

[0002] As an information processing device used in a core system such as a financial institution, a large general-purpose computer called a mainframe (also referred to as a general-purpose machine or the like) is used. In a mainframe, hardware and software configured independently by its vendor are used. While it has excellent operation stability and the like, its versatility is low. Therefore, a system for migrating a mainframe to an open environment is known (Patent Document 1).

Prior Art Documents

Patent Documents

[0003]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0004] In a migration system such as Patent Document 1, it is necessary to replace the application construction language in the mainframe with Java, which is costly and time-consuming. For this reason, as a method of enabling access from an open system to various resources in the mainframe without migrating the mainframe, access is performed by a cooperation application using the API (Application Programming Interface) of a cooperation library provided by the mainframe vendor. In this case, there is a problem that the development of the cooperation application is costly and time-consuming.

[0005] Therefore, the present invention aims to provide an access support device for mainframe equipment that enables easy utilization of resources within the mainframe from open systems. [Means for solving the problem]

[0006] To achieve the above objective, the present invention provides an access support device, an access support device for a mainframe device, It includes an access information acquisition unit, an access information analysis unit, an execution request generation unit, and an execution request transmission unit, The aforementioned access information acquisition unit acquires access information, The aforementioned access information includes transaction identification information and input information, The access information analysis unit analyzes the access information and extracts the transaction identification information and the input information. The execution request generation unit, Based on the input information, the transaction identification information, and the transaction definition, execution request information to the mainframe device is generated. The transaction definition is information that, for each transaction identification information, associates the resource identification information of the resources included in the mainframe device with the execution order of those resources. The execution request transmission unit transmits the execution request information to the mainframe device to be accessed, which is identified based on the transaction identification information and the transaction definition.

[0007] The access support terminal of the present invention is an access support terminal for a mainframe device, Including an access information input section and an access information transmission section, The access information input unit is capable of inputting the access information, The access information transmission unit transmits the access information to the access support device of the present invention.

[0008] The mainframe device of the present invention, Includes an execution request information acquisition unit and an execution unit, The execution request information acquisition unit acquires the execution request information from the access support device of the present invention, The execution unit generates the execution result information based on the execution request information.

[0009] The access support system device of the present invention, It includes a server, a terminal, and a mainframe device. The server and the terminal are capable of communicating with each other. The server and the mainframe device are capable of communicating with each other. The server is the access support device of the present invention, The aforementioned terminal is the access support terminal of the present invention, The aforementioned mainframe device is the mainframe device of the present invention.

[0010] The present invention provides an access support method for a mainframe device, This includes an access information acquisition process, an access information analysis process, an execution request generation process, and an execution request transmission process. The aforementioned access information acquisition step acquires access information, The aforementioned access information includes transaction identification information and input information, The access information analysis step involves analyzing the access information to extract the transaction identification information and the input information. The execution request generation step is: Based on the input information, the transaction identification information, and the transaction definition, execution request information to the mainframe device is generated. The transaction definition is information that, for each transaction identification information, associates the resource identification information of the resources included in the mainframe device with the execution order of those resources. The execution request transmission step transmits the execution request information to the mainframe device to be accessed, which is identified based on the transaction identification information and the transaction definition.

[0011] The program of the present invention is a program for causing a computer to execute an access information acquisition procedure, an access information analysis procedure, an execution request generation procedure, and an execution request transmission procedure, and the access information acquisition procedure acquires access information, the access information includes transaction identification information and input information, the access information analysis procedure analyzes the access information to extract the transaction identification information and the input information, the execution request generation procedure generates execution request information for the mainframe device based on the input information, the transaction identification information, and a transaction definition, the transaction definition is information in which resource identification information of resources included in the mainframe device and the execution order of the resources are linked for each transaction identification information, the execution request transmission procedure is a program that transmits the execution request information to the mainframe device at the access destination specified based on the transaction identification information and the transaction definition.

Advantages of the Invention

[0012] According to the present invention, resources within the mainframe can be easily utilized from an open system.

Brief Description of the Drawings

[0013] [Figure 1] FIG. 1 is a block diagram showing an example of the configuration of an access support system device including the access support device of Embodiment 1. [Figure 2] FIG. 2 is a block diagram showing an example of the hardware configuration of the access support device of Embodiment 1. [Figure 3] FIG. 3 is a block diagram showing an example of the hardware configuration of the access support terminal of Embodiment 1. [Figure 4] FIG. 4 is a block diagram showing an example of the hardware configuration of the mainframe device of Embodiment 1. [Figure 5] Figure 5 is a flowchart showing an example of processing in the access support device of Embodiment 1. [Figure 6] Figure 6 is a block diagram showing the configuration of an example of an access support system device including the access support device of Embodiment 2. [Figure 7] Figure 7 is a flowchart showing an example of processing in the access support device of Embodiment 2. [Figure 8] Figure 8 is an explanatory diagram showing an example of the execution result conversion process in the access support device of Embodiment 2. [Figure 9] Figure 9 is an explanatory diagram showing an example of the execution result conversion process in the access support device of Embodiment 2. [Modes for carrying out the invention]

[0014] In this invention, "open system" means a system configured by combining products from different vendors, for example, by utilizing software and / or hardware that conform to publicly available specifications.

[0015] Embodiments of the present invention will be described with reference to the drawings. The present invention is not limited to the following embodiments. In the following drawings, the same parts are denoted by the same reference numerals. Furthermore, unless otherwise specified, the descriptions of each embodiment can be used interchangeably with those of the others, and unless otherwise specified, the configurations of each embodiment can be combined.

[0016] [Embodiment 1] An access support system device, including an access support device for a mainframe device according to this embodiment, will be described with reference to Figure 1. Figure 1 is a block diagram showing an example configuration of an access support system device 100, including an access support device 10, an access support terminal 20, and a mainframe device 30 according to this embodiment. Although not shown, the access support system device 100 may include, for example, multiple access support terminals 20. The access support device 10 and the access support terminals 20 may be connected to each other, for example, by a REST (REpresentational State Transfer) interface. The REST interface will be described later. The access support system device 100 may also include, for example, multiple mainframe devices 30. As shown in Figure 1, the access support device 10 and the access support terminals 20 are connected to each other via a communication network 40, and the access support device 10 and the mainframe device 30 are also connected to each other via the communication network 40. The access support terminals 20 and the mainframe device 30 may or may not be connected to each other via the communication network 40. Although not shown in the diagram, the access support device 10 may be able to connect to an external database via the communication network 40. Also, although not shown in the diagram, the access support device 10 may be able to connect to, for example, the system administrator's external terminal via the communication network 40, and the system administrator may manage the access support device 10 from the external terminal.

[0017] The access support device 10 (hereinafter also referred to as "this device 10") includes an access information acquisition unit 11, an access information analysis unit 12, an execution request generation unit 13, and an execution request transmission unit 14. Although not shown in the figures, this device 10 may also include, for example, a storage unit.

[0018] The device 10 may be, for example, a single device including the aforementioned parts, or it may be a device in which each of the aforementioned parts can be connected via a communication network. Furthermore, the device 10 can be connected to external devices described later via a communication network. The communication network is not particularly limited and can use any known network, such as a wired or wireless network. Examples of communication networks include the Internet, WWW (World Wide Web), telephone lines, LAN (Local Area Network), SAN (Storage Area Network), DTN (Delay Tolerant Networking), LPWA (Low Power Wide Area), L5G (Local 5G), etc. Examples of wireless communication include Wi-Fi (registered trademark), Bluetooth (registered trademark), Local 5G, LPWA, etc. The wireless communication may be in the form of direct communication between devices (Ad Hoc communication), infrastructure communication, or indirect communication via an access point. The device 10 may, for example, be incorporated into an open system web server and implemented as a web application. Furthermore, the device 10 may be, for example, a personal computer (PC, e.g., desktop or notebook type), smartphone, tablet terminal, etc., on which the program of the present invention is installed. Moreover, the device 10 may be in a form such as cloud computing or edge computing, where, for example, at least one of the aforementioned parts is on a server and the other aforementioned parts are on a terminal.

[0019] Figure 2 illustrates a block diagram of the hardware configuration of the device 10. The device 10 includes, for example, a CPU 101, memory 102, bus 103, storage device 104, input device 106, display (display device) 107, communication device 108, etc. Each part of the device 10 is interconnected via the bus 103 through its respective interface (I / F).

[0020] The CPU 101 operates in conjunction with other components, such as a controller (system controller, I / O controller, etc.), and is responsible for the overall control of the device 10. In the device 10, the CPU 101 executes, for example, the program 105 of the present invention and other programs, and also reads and writes various types of information. Specifically, for example, the CPU 101 functions as an access information acquisition unit 11, an access information analysis unit 12, an execution request generation unit 13, and an execution request transmission unit 14. The device 10 is equipped with a CPU as its computing device, but it may also be equipped with other computing devices such as a GPU (Graphics Processing Unit) or an APU (Accelerated Processing Unit), or a combination of the CPU and these.

[0021] Bus 103 can also be connected to external devices, for example. Examples of such external devices include the access support terminal 20 and the mainframe device 30, or external storage devices (such as external databases), printers, external input devices, external display devices, and external imaging devices. The device 10 can be connected to an external network (the aforementioned communication network) by a communication device 108 connected to bus 103, for example, and can also be connected to other devices via the external network.

[0022] Memory 102 may be, for example, main memory. When the CPU 101 performs processing, memory 102 reads various operational programs, such as the program of the present invention, stored in the storage device 104 (described later), and the CPU 101 receives data from memory 102 and executes the program. The main memory may be, for example, RAM (random access memory). Alternatively, memory 102 may be, for example, ROM (read-only memory).

[0023] The storage device 104 is also called an auxiliary storage device, for example, in relation to the main memory (primary memory). As described above, the storage device 104 stores an operation program 105 that includes the program of the present invention. The storage device 104 may be, for example, a combination of a recording medium and a drive that reads and writes to the recording medium. The recording medium is not particularly limited and may be internal or external, for example, an HD (hard disk), CD-ROM, CD-R, CD-RW, MO, DVD, flash memory, memory card, etc. The storage device 104 may be, for example, a hard disk drive (HDD) in which the recording medium and the drive are integrated, or a solid state drive (SSD). If the device 10 includes, for example, the storage device 104 functions as the storage medium. If the device 10 includes the storage medium, for example, the storage medium may store each piece of information acquired or generated by the device. The storage device 104 may store, for example, a transaction definition, which will be described later.

[0024] In this device 10, the memory 102 and storage device 104 can also store various types of information, such as log information, information obtained from an external database (not shown) or external devices, information generated by this device 10, and information used by this device 10 when executing processing. At least some of this information may be stored, for example, on an external server other than the memory 102 and storage device 104, or it may be stored in a distributed manner across multiple terminals using blockchain technology or the like.

[0025] The device 10 further includes, for example, an input device 106 and a display 107. The input device 106 may include, for example, a pointing device such as a touch panel, trackpad, or mouse; a keyboard; imaging means such as a camera or scanner; a card reader such as an IC card reader or magnetic card reader; and audio input means such as a microphone. The display 107 may include, for example, an LED display or a liquid crystal display. In this embodiment 1, the input device 106 and the display 107 are configured separately, but the input device 106 and the display 107 may be configured as an integrated unit, such as a touch panel display.

[0026] The access support terminal 20 (hereinafter also referred to as "terminal 20") may include, for example, a server or PC configured in an open system; a mobile device such as a mobile phone, smartphone, or tablet; or a smartwatch, smart glasses, or wearable device. The access support terminal 20 may also be equipped with, for example, imaging means such as a camera or scanner, audio input means such as a microphone, or an IC (integrated circuit) card reader. The access support terminal 20 may also be, for example, an application or web service that accesses the mainframe device 30 via the access support device 10, or a device that provides such.

[0027] Figure 3 illustrates a block diagram of the hardware configuration of the access support terminal 20. As shown in Figure 3, the access support terminal 20 includes, for example, a CPU 201, memory 202, bus 203, storage device 204, input device (input unit) 206, communication device (communication unit) 208, display (display unit) 207, etc. In the access support terminal 20, the CPU 201 functions as an access information input unit 21 and an access information transmission unit 22. Each part of the access support terminal 20 is connected via the bus 203 by its respective interface (I / F). The explanation of each component of the access support terminal 20 can be found by referring to the explanation of each component of the access support device 10.

[0028] The mainframe device 30 (hereinafter also referred to as "mainframe 30") is a large computer used in core information systems of companies, government agencies, etc., and is also called a general-purpose machine or legacy system. Specific examples of mainframe devices include the ACOS series from NEC Corporation, but the present invention is not limited to these. The mainframe device 30 includes, for example, core business applications (core business APs) 331, core databases (core DBs) 333, and core DB access applications (core DB access APs) 332 as core resources 33 of the core system.

[0029] Figure 4 illustrates a block diagram of the hardware configuration of the mainframe device 30. As shown in Figure 4, the mainframe device 30 includes, for example, a CPU 301, memory 302, bus 303, storage device 304, input device (input unit) 306, communication device (communication unit) 308, display (display unit) 307, etc. In the mainframe device 30, the CPU 301 functions as an execution request information acquisition unit 31, an execution unit 32, a core business application (core business AP) 331, and a core DB access application (core DB access AP) 332. The storage device 304 functions, for example, as a core database (core DB) 333. Each part of the mainframe device 30 is connected via the bus 303 by its respective interface (I / F). The explanation of each component of the mainframe device 30 can be found by referring to the explanation of each component of the access support device 10.

[0030] Next, an example of the access support method of this embodiment will be described based on the flowchart in Figure 5. The access support method of this embodiment is implemented as follows, for example, using the access support system device 100 shown in Figure 1. Note that the access support method of this embodiment is not limited to the use of the access support system device 100 shown in Figure 1.

[0031] First, prior to processing by the access support device 10, a transaction definition is set. The transaction definition is information that associates resource identification information of resources included in the mainframe device with the execution order of those resources for each transaction identification piece. The transaction identification information is, for example, information for identifying a set of multiple core resources (hereinafter also referred to as a core transaction) in the mainframe device 30. The resource is, for example, a core resource 33 of the mainframe device 30, and includes at least one selected from a core business application (core business AP) 331, a core database (core DB) 333, and a core DB access application (core DB access AP) 332. Table 1 below shows a specific example of the transaction definition, but the present invention is not limited in any way to the following specific example. As shown in Table 1 below, for example, transaction identification information tx_id1 is associated with the resource identification information app_id1 and table_name1 in order of execution order, and transaction identification information tx_id2 is associated with the resource identification information app_id2, table_name2, and app_id3 in order of execution order. The transaction definition may be stored, for example, in the storage device 104 or memory 102 of the access support device 10, or in a database or server outside the system, the storage device 204 or memory 102 of the access support terminal 20, or the storage device 304 or memory 302 of the mainframe device 30.

[0032] [Table 1]

[0033] In the transaction definition, for example, the resource identification information may also be linked to the input format information. The input format information is, for example, information required for the execution of the core business AP331 or access to the core DB333. The input format information can be set appropriately for each type of core resource (core business AP, core DB access AP, or core DB). Specifically, for example, for the resource identification information of a core business AP, the input format information can be linked to the service identification name of the core business AP identified by the resource identification information, the data format to be sent to the core business AP, input parameter information required for the execution of the core business AP (for example, the number of input parameters, the type of parameters, the size of the parameters, etc.), and the data format of the received execution result of the core business AP. Furthermore, for resource identification information of the core DB, the following can be associated as input format information: file identifier name, DB type of the core DB identified by the resource identification information, data model, interface supported by the DB, file type, and received data format of the reference result of the core DB. Table 2 below shows specific examples of input format information for each resource identification information associated with the transaction identification information tx_id1, but the present invention is not limited in any way to the following specific examples. When the resource identification information and the input format information are associated as the transaction definition, for example, the user does not need to input the input format information as access information, making it easier to use the resources of the mainframe device from an open system.

[0034] [Table 2]

[0035] The user inputs access information using the access information input unit 21 of the access support terminal 20. The access information includes transaction identification information and input information. The transaction identification information is, for example, information for identifying each core transaction defined in the transaction definition. The input information is, for example, information entered into core resources, such as input parameters for the core business AP331 and search condition parameters for the core DB333.

[0036] Next, the access support terminal 20 connects to the access support device 10, for example, via the communication network 40, and the access information transmission unit 22 transmits the access information to the access support device 10. Specifically, the access support terminal 20 can connect to the access support device 10, for example, via a REST (REpresentational State Transfer) interface. The REST interface is, for example, the interface of a web application that accesses a specified resource by accessing it via HTTP (Hypertext Transfer Protocol) using a URI (Uniform Resource Identifier) ​​containing resource information. In this case, for example, the access support terminal 20 transmits an HTTP request to the access support device 10 via the RESTful API (also called REST API) of the REST interface, which includes a URI containing the transaction identification information and input information as the access information. Note that the URI shown below is just an example, and the present invention is not limited thereto. URI: http: / / ~ / (transaction identifier) / (input information)

[0037] The aforementioned access information may include, for example, other information. Below is an example of the structure of a URI when the access information includes the aforementioned other information. Note that the URI shown below is just an example, and the present invention is not limited thereto. In the URI below, (FQDN·path) indicates, for example, the web location information (address) of the access support device 10, and includes FQDN (Fully Qualified Domain Name), path, etc. In the URI below, (return data format) indicates, for example, return data format information. The return data format information will be described later in Embodiment 2. URI: http: / / (FQDN · Path) / (Return Data Format) / (Transaction Identifier) / (Input Information)

[0038] Furthermore, when the access support terminal 20 performs HTTP access to the access support device 10, the access information transmission unit 22 of the access support terminal 20 may, for example, include some or all of the input information in the message body of the HTTP request. If the input information includes, for example, highly confidential information such as a password, it is preferable from a security standpoint to include the input information in the message body.

[0039] The access information acquisition unit 11 of the access support device 10 acquires the access information (S1, access information acquisition step). The access information acquisition unit 11 acquires, for example, an HTTP request containing the URI sent from the access support terminal 20 via a RESTful API as the access information. The access support device 10 can support the URI as, for example, the REST interface.

[0040] Next, the access information analysis unit 12 analyzes the access information and extracts the transaction identification information and the input information (S2, access information analysis step). Specifically, for example, if in S1 an HTTP request containing the URI "http: / / ~ / (transaction identification information) / (input information)" is obtained as access information, the access information analysis unit 12 extracts the transaction identification information specified in (transaction identification information) (for example, "tx_id1", etc.) and each parameter or search condition contained in (input information) from the URI. Furthermore, if some or all of the input information is included in the message body of the HTTP request, the access information analysis unit 12 may extract the input information contained in the message body.

[0041] Next, the execution request generation unit 13 generates execution request information to the mainframe device based on the input information, the transaction identification information, and the transaction definition (S3, execution request generation step). Specifically, the execution request generation unit 13 first compares the extracted transaction identification information with the transaction definition and identifies the multiple core resource identification information specified in the transaction identification information included in the access information (URI) and the execution order of the core resources. Then, the execution request generation unit 13 generates execution request information including the input information according to the execution order.

[0042] If the transaction definition associates the resource identification information with the input format information, the execution request generation unit 13 may generate the execution request information based on the input information, the input format information, the transaction identification information, and the transaction definition. In this case, the execution request generation unit 13 may convert the format of each of the input pieces of information for each type of core resource by referring to the input format information.

[0043] The execution request transmission unit 14 then transmits the execution request information to the mainframe device 30, which is the access destination identified based on the transaction identification information and the transaction definition (S4, execution request transmission step). Specifically, the execution request transmission unit 14 can transmit the execution request information to the mainframe device 30, for example, via a cooperation API that executes resources of the mainframe device 30 included in the cooperation library of the mainframe device 30. The cooperation library is, for example, a library provided by the vendor of the mainframe device 30, and includes a cooperation API that enables cooperation between the mainframe device 30 and an open system.

[0044] The mainframe device 30 obtains execution request information from the access support device 10 using the execution request information acquisition unit 31. Specifically, the mainframe device 30 is connected to the access support device 10 by wire or wireless connection, for example, and obtains the execution request information via the cooperation API of the cooperation library.

[0045] The mainframe device 30 then generates execution result information based on the execution request information using the execution unit 32. Specifically, the mainframe device 30 executes the processing of each resource in the order specified in the execution request information and generates execution result information.

[0046] In this embodiment, the access support device associates the resource identification information of the resources included in the mainframe device with the execution order of those resources for each transaction identification information as part of the transaction definition. Therefore, by specifying the transaction identification information as access information, resources within the mainframe can be easily accessed from an open system. Furthermore, according to this embodiment, for example, a user can utilize various core resources of the mainframe device by accessing the access support device of the present invention without having to develop an integration application using the integration API included in the mainframe device's integration library themselves. Therefore, according to the present invention, for example, stable utilization of the mainframe device is possible regardless of the user's integration application development skills, development costs and man-hours for integration applications can be reduced, and a stable system can be provided regardless of the user's application development skills. In addition, integration applications developed by users are usually developed for specific resources, making it difficult to apply the core resources of the mainframe device in data analysis, etc. In contrast, the access support device of this embodiment enables access to multiple core resources from an access support terminal, which is an open system, thus enabling proactive applications that use multiple core resources, such as analyzing multiple core databases with an open system BI tool.

[0047] Furthermore, REST interfaces are, in principle, stateless, and one access corresponds to one transaction. Therefore, generally, when accessing a core system from an open system using a REST interface, only one type of core resource is available per HTTP access. In contrast, the access support device of this embodiment can generate execution requests for multiple core resources in one transaction based on the transaction definition, for example, using the execution request generation unit. Therefore, according to the access support device of this embodiment, multiple core resources can be used with a single HTTP access. Consequently, according to the access support device of the present invention, for example, if an exception occurs during the execution of a resource in a downstream execution order, the transaction can be rolled back, allowing for flexible responses in the event of trouble. In addition, according to the access support device of the present invention, for example, when executing multiple core business applications, they can be executed consecutively within the same transaction, and there is no risk of being interrupted by another transaction, thus suppressing the occurrence of data inconsistencies. Furthermore, according to the access support device of the present invention, for example, the number of HTTP accesses can be reduced, thus suppressing operational costs and communication costs.

[0048] [Embodiment 2] Embodiment 2 is another example of the access support system device of the present invention.

[0049] The access support system device of this embodiment will be described with reference to Figure 6. Figure 6 is a block diagram showing an example configuration of an access support system device 100A, which includes an access support device 10A, an access support terminal 20A, and a mainframe device 30A of this embodiment. Although not shown, the access support system device 100A may include, for example, multiple access support terminals 20A and multiple mainframe devices 30A. As shown in Figure 6, the access support system device 100A is the same as the access support system device 100 of Embodiment 1, except that it includes an access support device 10A, an access support terminal 20A, and a mainframe device 30A instead of the access support device 10, access support terminal 20, and mainframe device 30 of Embodiment 1, and the explanation therefor can be applied.

[0050] In the access support system device 100A of Embodiment 2, the access support device 10A further includes, for example, an execution result acquisition unit 15, an execution result conversion unit 16, and a conversion data output unit 17. The access information includes return data format information. The execution result acquisition unit 15 acquires execution result information based on the execution request information from the mainframe device 30A. The execution result conversion unit 16 generates converted execution result information by converting the data format of the execution result information based on the return data format information. The conversion data output unit 17 outputs the converted execution result information. The access support device 10A of this embodiment is the same as the access support device 10 in the access support system device 100 of Embodiment 1, except for these features, and its description can be applied. The hardware configuration of the access support device 10A is the same as that of the access support device 10 in Figure 2, except that the CPU 101 has the configuration of the access support device 10A in Figure 6 instead of the configuration of the access support device 10 in Figure 1.

[0051] In the access support system device 100A of Embodiment 2, the access support terminal 20A further includes, for example, a conversion execution result acquisition unit 23, which acquires the conversion execution result information from the access support device 10A. The access support terminal 20A of this embodiment is the same as the access support terminal 20 in the access support system device 100 of Embodiment 1, except for these features, and the description thereof can be applied. The hardware configuration of the access support terminal 20A is the same as that of the access support terminal 20 in Figure 3, except that the CPU 201 has the configuration of the access support terminal 20A in Figure 6 instead of the configuration of the access support terminal 20 in Figure 1.

[0052] In the access support system device 100A of Embodiment 2, the mainframe device 30A further includes, for example, an execution result transmission unit 34, which transmits the execution result information to the access support device 10A. The mainframe device 30A of this embodiment is the same as the mainframe device 30 in the access support system device 100 of Embodiment 1, except for these features, and the description thereof can be applied. The hardware configuration of the mainframe device 30A is the same as that of the mainframe device 30 in Figure 4, except that the CPU 301 has the configuration of the mainframe device 30A in Figure 6 instead of the configuration of the mainframe device 30 in Figure 1.

[0053] Next, an example of the access support method of this embodiment will be described based on the flowchart in Figure 7. The access support method of this embodiment is implemented, for example, using the access support system device 100A shown in Figure 6, as follows. Note that the access support method of this embodiment is not limited to the use of the access support system device 100A shown in Figure 6.

[0054] First, processes S1 to S4 are performed in the same manner as those of the access support device 10 in Embodiment 1. As described above, in this embodiment, the access information includes the return data format information.

[0055] The mainframe device 30A transmits the execution result information to the access support device 10A via the execution result transmission unit 34.

[0056] The execution result acquisition unit 15 of the access support device 10A acquires execution result information based on the execution request information from, for example, the mainframe device 30A (S5, execution result acquisition step). The execution result information may include, for example, data in the received data format of the input format information in the transaction definition.

[0057] The execution result conversion unit 16 generates converted execution result information by converting the data format of the execution result information based on the return data format information (S6, execution result conversion step). The return data format information is, for example, information on the data format to be returned to the access support terminal 20. The return data format information can be set appropriately according to the specifications or use of the access support terminal 20A, for example, and "records" or "fields" can be specified as specific examples. "records" is, for example, a format in which data is returned with column information and records separated, and "fields" is, for example, a format in which data is returned with column information included in each record. Figures 8 and 9 show examples of return data format information and converted execution result information converted based on the return data format information. Figure 8 is an example when the return data format information is "records", and Figure 9 is an example when the return data format information is "fields". In Figures 8 and 9, the table in the upper right shows the execution result information before conversion by the execution result conversion unit 16, and the list on the left shows the converted execution result information after conversion by the execution result conversion unit 16.

[0058] The conversion data output unit 17 outputs, for example, the conversion execution result information (S7, conversion data output step). The output may be, for example, output to the access support terminal 20A, or to a server or database outside the device.

[0059] The conversion execution result acquisition unit 23 of the access support terminal 20A acquires the conversion execution result information from the access support device 10A, for example. However, the present invention is not limited thereto. For example, if the conversion execution result information is output to a server or database outside the device in S7, the conversion execution result acquisition unit 23 may acquire the conversion execution result information from the server or database outside the device.

[0060] The access support device of this embodiment can, for example, acquire execution result information performed by a mainframe device and output converted execution result information converted based on the return data format information. Therefore, according to the access support system device of this embodiment, an access support terminal, which is an open system device, can acquire the converted execution result information, which is the execution result of the mainframe device.

[0061] [Embodiment 3] The program of this embodiment is a program that causes a computer to execute each step of the access support method described above. Specifically, the program of this embodiment is a program that causes a computer to execute the access information acquisition procedure, the access information analysis procedure, the execution request generation procedure, and the execution request transmission procedure.

[0062] The aforementioned procedure for obtaining access information involves obtaining access information, The aforementioned access information includes transaction identification information and input information, The access information analysis procedure analyzes the access information and extracts the transaction identification information and the input information. The execution request generation procedure is as follows: Based on the input information, the transaction identification information, and the transaction definition, execution request information to the mainframe device is generated. The transaction definition is information that, for each transaction identification information, associates the resource identification information of the resources included in the mainframe device with the execution order of those resources. The execution request transmission procedure transmits the execution request information to the mainframe device to be accessed, which is identified based on the transaction identification information and the transaction definition.

[0063] Furthermore, the program of this embodiment can also be described as a program that causes a computer to function as an access information acquisition procedure, an access information analysis procedure, an execution request generation procedure, and an execution request transmission procedure.

[0064] The program of this embodiment can be based on the description in the access support device and access support method of the present invention. Each of the above steps can be read as, for example, "step" or "process". The program of this embodiment may also be recorded on, for example, a computer-readable recording medium. The recording medium is, for example, a non-transitory computer-readable storage medium. The recording medium is not particularly limited and includes, for example, random access memory (RAM), read-only memory (ROM), hard disk (HD), optical disk, floppy disk (FD), etc.

[0065] Although the present invention has been described above with reference to embodiments, the present invention is not limited to the above embodiments. Various modifications to the configuration and details of the present invention can be understood by those skilled in the art within the scope of the present invention.

[0066] <Note> Some or all of the above embodiments may be described as follows, but are not limited to the following: (Note 1) It includes an access information acquisition unit, an access information analysis unit, an execution request generation unit, and an execution request transmission unit, The aforementioned access information acquisition unit acquires access information, The aforementioned access information includes transaction identification information and input information, The access information analysis unit analyzes the access information and extracts the transaction identification information and the input information. The execution request generation unit, Based on the input information, the transaction identification information, and the transaction definition, execution request information to the mainframe device is generated. The transaction definition is information that, for each transaction identification information, associates the resource identification information of the resources included in the mainframe device with the execution order of those resources. The execution request transmission unit is a mainframe device that transmits the execution request information to the mainframe device to be accessed, which is identified based on the transaction identification information and the transaction definition. (Note 2) In the transaction definition, the resource identification information and the input format information are linked. The access support device described in Appendix 1, wherein the execution request generation unit generates the execution request information based on the input information, the input format information, the transaction identification information, and the transaction definition. (Note 3) It includes an execution result acquisition unit, an execution result conversion unit, and a conversion data output unit. The aforementioned access information includes return data format information, The execution result acquisition unit acquires execution result information based on the execution request information from the mainframe device. The execution result conversion unit generates converted execution result information by converting the data format of the execution result information based on the returned data format information. The conversion data output unit is an access support device as described in Appendix 1 or 2, which outputs the conversion execution result information. (Note 4) Including an access information input section and an access information transmission section, The access information input unit is capable of inputting the access information, The access information transmission unit is an access support terminal for a mainframe device that transmits the access information to an access support device described in any of the appendices 1 to 3. (Note 5) Includes a conversion execution result acquisition unit, The conversion execution result acquisition unit is an access support terminal as described in Appendix 4, which acquires the conversion execution result information from the access support device described in Appendix 3. (Note 6) Includes an execution request information acquisition unit and an execution unit, The execution request information acquisition unit acquires the execution request information from the access support device described in any of the appendices 1 to 3. The execution unit is a mainframe device that generates the execution result information based on the execution request information. (Note 7) Includes the execution result transmission unit, The execution result transmission unit is a mainframe device as described in Appendix 6, which transmits the execution result information to the access support device. (Note 8) It includes a server, a terminal, and a mainframe device. The server and the terminal are capable of communicating with each other. The server and the mainframe device are capable of communicating with each other. The server is an access support device as described in any of the appendices 1 to 3. The aforementioned terminal is an access support terminal as described in Appendix 4 or 5. An access support system device in which the mainframe device is the mainframe device described in Appendix 6 or 7. (Note 9) This includes an access information acquisition process, an access information analysis process, an execution request generation process, and an execution request transmission process. The aforementioned access information acquisition step acquires access information, The aforementioned access information includes transaction identification information and input information, The access information analysis step involves analyzing the access information to extract the transaction identification information and the input information. The execution request generation step is: Based on the input information, the transaction identification information, and the transaction definition, execution request information to the mainframe device is generated. The transaction definition is information that, for each transaction identification information, associates the resource identification information of the resources included in the mainframe device with the execution order of those resources. The execution request transmission step is a method for supporting access to a mainframe device, which transmits the execution request information to a target mainframe device identified based on the transaction identification information and the transaction definition. (Note 10) In the transaction definition, the resource identification information and the input format information are linked. The access support method described in Appendix 9, wherein the execution request generation step generates the execution request information based on the input information, the input format information, the transaction identification information, and the transaction definition. (Note 11) This process includes an execution result acquisition step, an execution result conversion step, and a converted data output step. The aforementioned access information includes return data format information, The execution result acquisition step involves acquiring execution result information based on the execution request information from the mainframe device. The execution result conversion step generates converted execution result information by converting the data format of the execution result information based on the returned data format information. The conversion data output step is an access support method according to Appendix 9 or 10 that outputs the conversion execution result information. (Note 12) A program that causes a computer to execute a procedure for obtaining access information, a procedure for analyzing access information, a procedure for generating an execution request, and a procedure for sending an execution request, The aforementioned procedure for obtaining access information involves obtaining access information, The aforementioned access information includes transaction identification information and input information, The access information analysis procedure analyzes the access information and extracts the transaction identification information and the input information. The execution request generation procedure is as follows: Based on the input information, the transaction identification information, and the transaction definition, execution request information to the mainframe device is generated. The transaction definition is information that, for each transaction identification information, associates the resource identification information of the resources included in the mainframe device with the execution order of those resources. The execution request transmission procedure is a program that transmits the execution request information to the mainframe device to be accessed, which is identified based on the transaction identification information and the transaction definition. (Note 13) In the transaction definition, the resource identification information and the input format information are linked. The execution request generation procedure is a program described in Appendix 12 that generates the execution request information based on the input information, the input format information, the transaction identification information, and the transaction definition. (Note 14) This includes the procedure for obtaining execution results, the procedure for converting execution results, and the procedure for outputting converted data. The aforementioned access information includes return data format information, The execution result acquisition procedure involves acquiring execution result information based on the execution request information from the mainframe device, The execution result conversion procedure generates converted execution result information by converting the data format of the execution result information based on the returned data format information. The conversion data output procedure is a program described in Appendix 11 or 12 that outputs the conversion execution result information. (Note 15) A computer-readable recording medium containing a program described in any of the appendices 12 to 14. [Industrial applicability]

[0067] According to the present invention, resources within the mainframe can be easily accessed from an open system without the need to develop collaborative applications. For this reason, the present invention is useful in areas such as the utilization and modernization of mainframe assets. [Explanation of symbols]

[0068] 100, 100A Access Support System Device 10, 10A Access Support Device 11 Access Information Acquisition Unit 12 Access Information Analysis Department 13 Execution Request Generation Unit 14 Execution Request Transmission Unit 15 Execution Result Acquisition Unit 16 Execution Result Return Section 17. Conversion Data Output Section 101, 201, 301 CPUs 102, 202, 302 memory Buses 103, 203, and 302 104, 204, 304 storage device Programs 105, 205, and 305 106, 206, 306 Input devices 107, 207, 307 Display device 108, 208, 308 communication devices 20, 20A Access support terminal 21 Access Information Input Section 22 Access Information Transmission Section 23. Unit for obtaining conversion execution results 30, 30A Mainframe Equipment 31 Execution Request Information Acquisition Unit 32 Execution Department 33 Core Resources 331 Core Business AP 332 Core DB Access AP 333 Core DB 34 Execution Result Transmission Unit

Claims

1. It includes an access information acquisition unit, an access information analysis unit, an execution request generation unit, and an execution request transmission unit, The aforementioned access information acquisition unit acquires access information, The aforementioned access information includes transaction identification information and input information, The access information analysis unit analyzes the access information and extracts the transaction identification information and the input information. The execution request generation unit, Based on the input information, input format information, transaction identification information, and transaction definition, execution request information to the mainframe device is generated. The aforementioned input format information is set for each type of resource included in the mainframe device. The transaction definition is information that, for each transaction identification information, associates the resource identification information of the resource with the execution order of the resource and the input format information of the resource. The execution request transmission unit is a mainframe device that transmits the execution request information to the mainframe device to be accessed, which is identified based on the transaction identification information and the transaction definition.

2. It includes an execution result acquisition unit, an execution result conversion unit, and a conversion data output unit. The aforementioned access information includes return data format information, The execution result acquisition unit acquires execution result information based on the execution request information from the mainframe device. The execution result conversion unit generates converted execution result information by converting the data format of the execution result information based on the returned data format information. The access support device according to claim 1, wherein the conversion data output unit outputs the conversion execution result information.

3. It includes a server, a terminal, and a mainframe device. The server and the terminal are capable of communicating with each other. The server and the mainframe device are capable of communicating with each other. The server is the access support device described in claim 2, The terminal includes an access information input unit and an access information transmission unit, The access information input unit is capable of inputting the access information, The access information transmission unit is an access support terminal that transmits the access information to the access support device described in claim 2. The mainframe device includes an execution request information acquisition unit and an execution unit. The execution request information acquisition unit acquires the execution request information from the access support device described in claim 2, The execution unit is an access support system device, which is a mainframe device that generates the execution result information based on the execution request information.

4. An access support method in which each of the following steps, including an access information acquisition step, an access information analysis step, an execution request generation step, and an execution request transmission step, is performed by a computer, The aforementioned access information acquisition step acquires access information, The aforementioned access information includes transaction identification information and input information, The access information analysis step involves analyzing the access information to extract the transaction identification information and the input information. The execution request generation step is: Based on the input information, input format information, transaction identification information, and transaction definition, execution request information to the mainframe device is generated. The aforementioned input format information is set for each type of resource included in the mainframe device. The transaction definition is information that, for each transaction identification information, associates the resource identification information of the resource with the execution order of the resource and the input format information of the resource. The execution request transmission step is a method for accessing a mainframe device, which transmits the execution request information to a mainframe device identified as the access destination based on the transaction identification information and the transaction definition.

5. A program that causes a computer to execute a procedure for obtaining access information, a procedure for analyzing access information, a procedure for generating an execution request, and a procedure for sending an execution request, The aforementioned procedure for obtaining access information involves obtaining access information, The aforementioned access information includes transaction identification information and input information, The access information analysis procedure analyzes the access information and extracts the transaction identification information and the input information. The execution request generation procedure is as follows: Based on the input information, input format information, transaction identification information, and transaction definition, execution request information to the mainframe device is generated. The aforementioned input format information is set for each type of resource included in the mainframe device. The transaction definition is information that, for each transaction identification information, associates the resource identification information of the resource with the execution order of the resource and the input format information of the resource. The execution request transmission procedure is a program that transmits the execution request information to the mainframe device to be accessed, which is identified based on the transaction identification information and the transaction definition.

Images