JP2002373254A - Distributability notification network system, information processor, distributability notification method, program and storage medium - Google Patents

Abstract

PROBLEM TO BE SOLVED: To provide a distributability notification network system surely distributing information required by members or the like an finding the fault of the system in an early stage. SOLUTION: This distributability notification network system is provided with a server computer 4 distributing settlement information or the like to a member 2 side. The server computer 4 is provided with a means distributing distributability information indicating that the settlement information or the like is made to be distributable, a state notification information storage means storing state notification information including the information indicating that the data setup completion/distributability information of the settlement information is notified to a client computer 9 side and the information indicating that it is downloaded and browsed in the client computer 9, and a state notification information utilization means performing processing utilizing the state notification information.

Description

DETAILED DESCRIPTION OF THE INVENTION

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a distributable notification network system, an information processing apparatus, a distributable notification method,
The present invention relates to a program and a storage medium, and more particularly, to a deliverable notification network system and an information processing apparatus, a deliverable notification method, a program, and a storage medium that can early detect a failure in the information transmission / reception state between a server computer and a client computer. .

[0002]

2. Description of the Related Art In general, principal risk in securities settlement (that is, a risk that a seller of a security does not make payment even though a security has been delivered, or that a security has been delivered by a buyer of a security but has not been delivered). There is a need to reduce or eliminate this. The principal risk of a securities settlement system is usually systemic risk (ie, the inability of one institution to meet its obligations by its due date, the inability of other institutions to meet its obligations by its due date, and ultimately the payment of (The risk that the stability of the system and financial markets is at risk).

Prior to the settlement date, such risks are subject to replacement cost risk (ie, if one party fails before the settlement date, the other non-failing party). Are exposed to the risk of losing unrealized gains on such open contracts). The resulting exposure is nothing less than the cost of replacing the original contract with the current market price. The magnitude of the replacement cost risk depends on the volatility of the security price and the period between the trading date and the settlement date. These risks can be mitigated by shortening the period between trading and settlement.

[0004] The greatest risk associated with securities settlement is the settlement process (ie, the final (unconditional) transfer of securities from seller to buyer and the final transfer of funds from buyer to seller). (The process of ending with (payment)).

[0005] Since the above-mentioned principal risk deserves the total value of the transferred securities, the failure of a participant in a securities settlement system in which such a risk exists involves a huge credit loss so as to cause a systemic problem. Probability is high. For this reason, establishing the strongest possible linkage between delivery and payment is considered critical to a securities settlement system.

[0006] Liquidity risk is a risk that a seller of a security that cannot receive a payment by the due date is forced to borrow funds or sell assets to execute another payment, or It refers to the risk that a buyer of an undeliverable security will be required to borrow the security to fulfill his delivery obligations.

[0007] Generally, the following three methods are considered as a securities settlement system. For example, a first method is a system that executes a transfer instruction on a gross basis for both securities and funds, and the final (unconditional) transfer (delivery) of securities from seller to buyer is , And at the same time as the final transfer of money from the buyer to the seller (payment). Second, for securities, the transfer order is executed on a gross basis, and the final transfer (delivery) of the security from the seller to the buyer is always performed during the settlement processing time period, but for the funds, The transfer instruction is executed on a net basis, and the final transfer (payment) of the funds from the buyer to the seller is performed at the end of the settlement processing time zone. As a third method, transfer instructions are executed on a net basis for both securities and funds, and final transfers of both securities and funds are made at the end of the settlement processing time zone.

[0008] In such a method, the liquidity risk is defined as the risk that the counterparty cannot fulfill the settlement in full on the due date and will make it on an unspecified date in the future. If the other party is unable to settle due to technical or temporary reasons, it is not a default but a failed transaction.
and the party will settle in full at a later date, and is therefore believed to have no credit loss. However, when a settlement breach is known, the parties generally cannot determine with certainty whether it is a default or a failed transaction. As a result, a failure for technical reasons could lead to a loss of trust in the party that caused the failure, which could cause the other party to stop clearing other transactions with that party as well. .

[0009] Even if there is no loss of trust, liquidity risk is still a concern. For a seller of securities, liquidity risk is the risk of not being able to receive payment from the buyer, in which case the seller will probably borrow or borrow money to avoid defaulting on his payments for other transactions. Forced to dispose of assets. For a security buyer, the liquidity risk is the risk of not being able to receive the delivery from the seller, and the buyer will have to borrow the security to fulfill the delivery to a third party it is conceivable that.

[0010] The largest source of credit risk in securities settlement, and thus the largest source of systemic risk, is the principal risk that occurs on the settlement date. Such risks can be eliminated if the security settlement system provides a mechanism that ensures that delivery is only performed when payment is made. further,
Eliminating principal risk concerns reduces the likelihood of participants stopping delivery or payments in times of financial market pressure, thereby reducing liquidity risk.

[0011]

As described above, settlement of securities is preferably performed by DVP (Delivery Versus Payment), but at present, settlement of securities is performed on a paper basis. Payment processing using a network or the like was not performed.

However, paper-based information distribution requires a great deal of time and effort for paper distribution, and paper-based information distribution has been reduced due to the time required for information distribution and labor saving of paper resources. Alternative means were desired.

[0013] As described above, it is known that it is necessary to use DVP for securities settlement. Specifically, what kind of system, method, apparatus, program, or the like is used is as follows. It was not clear, and the solution needed to come up with new systems, methods, devices, programs, and the like.

Further, in order to settle by DVP,
It is necessary to send payment information to members using a network system.However, if information is sent using a network system, it may not be possible to send information due to a system failure. It is necessary to detect obstacles early and respond to them. Furthermore, when transmitting information using a network system, it is necessary to confirm whether the information has been transmitted to the member side.

Further, the new system, method, device,
It is preferable that the program or the like sufficiently establish connection with an existing system or a system of another institution.

A first object of the present invention is to construct a new system relating to settlement information instead of the conventional paper-based information distribution, and to cooperate with other systems as described above. Principal risk, systemic risk, replacement cost risk,
The purpose of the present invention is to provide a system, a method, an apparatus, a program, and the like that do not cause various risks such as a risk in a settlement process, a liquidity risk, and a risk in an office procedure. A second object of the present invention is to provide a distribution notice network system and an information processing apparatus that can reliably distribute information required by members and the like, and that can be detected early when a system failure occurs. , A payment information distribution method, a program, and a storage medium.

[0017]

According to the first aspect of the present invention, there is provided a server computer for distributing public information including at least one of a business message and settlement information relating to the operation of a stock exchange, and the server. A client computer on the member side of a stock exchange that receives the public information from a computer, the server computer comprising: a server capable of transmitting the public information to the effect that the public information can be distributed. Distributable information distributing means for distributing, and setup completion notified information that the data setup completion of the payment information has been notified to the client computer side,
Distributable notification information indicating that the distributable information has been notified to the client computer, downloaded information indicating that the payment information has been downloaded on the client computer, and viewing the payment information on the client computer. Status notification information storage means for accumulating status notification information including the viewed information that has been read, and status notification information use means for performing processing using the status notification information, wherein the client computer is capable of transmitting the distributable information. This is solved by providing a deliverable information receiving means for receiving the information.

According to the ninth aspect of the present invention, the above-mentioned problem is connected to a client computer on a member side of a stock exchange so as to be able to transmit and receive, and includes at least one of a business message and settlement information relating to the operation of the stock exchange. A storage device that distributes public information and stores a program that defines the operation of the information processing device, a storage device that stores a public information database storing the public information, and a server that creates the information. An input device that receives information from the outside, an output device that sends information to the outside, an operation using the information received from the storage device or / and the input device, and the operation result is stored in the storage device or / and the And a central processing unit that delivers the public information to the output device. Information distributing means for distributing information, information on the completion of setup completion notification to the effect that the data setup completion of the payment information has been notified to the client computer, and information that the distributable information has been notified to the client computer side. And status notification information including downloaded information indicating that the payment information has been downloaded on the client computer side, and browsed information on which the payment information has been viewed on the client computer. The problem is solved by including a status notification information storage unit and a status notification information using unit that performs processing using the status notification information.

As described above, the server computer includes the distributable information distributing means for distributing the distributable information indicating that the public information including at least one of the business message related to the operation of the stock exchange and the settlement information can be distributed. Therefore, the amount of information to be transmitted can be reduced as compared with the case where each piece of public information itself is transmitted to the client computer, and the member can be quickly notified of the existence of the public information. In addition, since the amount of information to be transmitted is small, it is possible to reduce the capacity of a computer, a transmitting unit, and the like to be used, thereby reducing the scale and cost of the system. As a result, a network system that can be easily introduced by both stock exchanges and members can be provided.

[0020] Since the server computer transmits to the client computer the distributable information indicating that the public information including at least one of the business message and the settlement information relating to the operation of the stock exchange can be distributed, the member side can distribute. By looking at the information, you can select and download or browse only the necessary information.
It will not be stored on the client computer.

The server computer may further include a setup completion notification information indicating that the data setup completion of the payment information has been notified to the client computer, and a delivery notification indicating that the deliverable information has been notified to the client computer. A status notification that accumulates status notification information including possible notification information, downloaded information indicating that the payment information has been downloaded on the client computer side, and browsed information on which the payment information has been viewed on the client computer. Since the information storage means is provided, the client computer side can check the data setup completion notification information, the distribution possible notification information, the downloaded information, and the browsed information stored in the status notification information storage means. Deliverable if information has arrived It is possible to know the contents of the information and public information has been confirmed, it is possible to centralized management of each member of the information confirmation situation. In addition, the status notification information can be stored by assigning the ID of each member in charge of the member who browsed, downloaded, and viewed the public information to the deliverable notification information, downloaded information, and browsed information. By checking the information stored in the means, it is possible for the member side to know which business person has viewed the information, etc., and it is also possible to manage the information confirmation status by the business person in each member .

[0022] At this time, the server computer generates the deliverable notified information based on a deliverable information reception completion signal automatically transmitted from the client computer upon receiving the deliverable information, and Based on the download completion signal automatically transmitted based on the download execution from the client computer, and generates the browsed information based on the browse execution signal automatically transmitted based on the browse execution from the client computer. , Is preferably generated.

As described above, the server computer generates the information indicating that the distribution is possible, based on the distribution completion information reception signal automatically transmitted from the client computer based on the reception of the distribution information. Based on the download completion signal automatically transmitted based on the download execution from the client computer, and generates the browsed information based on the browse execution signal automatically transmitted based on the browse execution from the client computer. , The status notification information is automatically stored in the server computer without any special processing on the client computer side. Therefore, each business person in charge of the client computer does not need to perform any special operation for status notification, and only needs to activate a program for transmitting and receiving distributable information or public information.
The operation procedure of the client computer is simplified.
Further, since the status notification is automatically performed, it is possible to prevent a situation notification from being lost due to a person forgetting to operate. Further, since the status notification is automatically performed, when the status notification is not performed, it is possible to predict that a failure has occurred.

[0024] Further, the distributable information reception completion signal includes:
It is preferable that, when the distributable information is displayed on the client computer screen, it is determined that the distributable information has been received and automatically transmitted. With such a configuration, it is possible to generate the information indicating that the distribution is possible, based on the fact that the contents of the distribution information are actually confirmed on the client computer side.

Further, the server computer transmits a data setup completion notification to another server computer connected to the server computer when the data setup of the payment information is completed, A status notification information transmitting unit that transmits the status notification information stored in the status notification information storage unit to the another server computer, wherein the processing using the status notification information is performed by the another server computer by the data setup. After a lapse of a predetermined time after receiving the completion information, if the status notification information is not received, the information transmission to the client computer is stopped based on a stop command transmitted from the another server computer. It is suitable.

As described above, in the processing using the status notification information, it is determined whether or not the status notification information has not been received after a predetermined time has elapsed after the another server computer has received the data setup completion information. With such a configuration, it is possible to know whether or not there is a problem only in the exchange between the server computer and the client computer.

That is, despite the fact that another server computer has received the data setup completion notice indicating that the setup of the public information has been normally completed, a predetermined time has passed, and none of the status notification information has been received. If not, the public information setup itself is fine,
Since it is possible to predict that transmission / reception between the server computer and the client computer is abnormal, it is possible to know whether or not there is a problem only in the part of the exchange between the server computer and the client computer.

Further, another server computer receives none of the status notification information even though a predetermined time has elapsed after receiving the data setup completion notification indicating that the public information has been set up normally. Otherwise, the server computer is configured to stop sending information to the client computer, so if it is presumed that the communication state between the server computer and the client computer is faulty, By stopping transmission, it is possible to reduce the burden of information processing on the server computer side. In addition, it is possible to construct a more complete and accurate monitoring system of the communication state in combination with other means for monitoring the communication state between the server computer and the client computer.

Further, the server computer transmits a data setup completion notification to another server computer connected to the server computer when the data setup of the settlement information is completed, Status notification information transmitting means for transmitting the status notification information stored in the status notification information storage means to the another server computer, wherein the processing using the status notification information includes After a lapse of a predetermined time after receiving the setup completion information, if the status notification information has not been received, a process of stopping information transmission to the client computer performed based on a stop command transmitted from the another server computer; During the stop state by the stop processing, the client To include, and restart processing of information transmission which is performed when a communication state is determined to be normal between the computer is suitable.

As described above, in the processing using the status notification information, the restart of information transmission performed when it is determined that the communication state with the client computer is normal during the stop state due to the stop processing. Since the configuration is such that the processing is performed, the information is retransmitted after it is confirmed that there is no failure, and the load of information processing on the server computer side can be reduced.

At this time, the server computer connects the member confirmed information generated first for the member among the confirmed information including the downloaded information and the browsed information to the server computer. It is preferable that the server computer further includes a member confirmed information transmitting unit that transmits the member confirmed information to another server computer, and the another server computer includes a member confirmed information storage unit that stores the member confirmed information.

With this configuration, it is possible to centrally manage information such as whether each member has viewed or downloaded the public information and which user among the members has viewed or downloaded the public information. It becomes possible.

At this time, the server computer, among the confirmed information including the downloaded information and the browsed information, connects the member confirmed information generated first with respect to the member to the server computer. The member-confirmed information transmitting means for transmitting the member-confirmed information to another server computer, and the member-side confirmed information receiving means for receiving the member-confirmed information from the another server computer. A member-confirmed information storage unit for storing the member-confirmed information, the distributable information distribution unit transmits the member-confirmed information to the member client computer, and the client computer A confirmed information receiving means for receiving the member confirmed information of the member; There are, together with the distributable information, it is preferable that comprises a distributable information display means capable of displaying the fact that already viewed or downloaded on any client computer of said members.

As described above, the server computer:
A member-side confirmed information receiving unit that receives the member-confirmed information of the member from the another server computer; and the distributable information distribution unit transmits the member-confirmed information of the member to the client computer of the member. And the client computer, the confirmed information receiving means for receiving the member confirmed information of the member, based on the member confirmed information of the member, along with the deliverable information,
Since it is configured to have a distributable information display means capable of displaying that the member has already been viewed or downloaded on any client computer of the member, on the member side, on the screen of the client computer, each public information, It is possible to know whether or not one of the business persons in the same member has already viewed or downloaded, and it is possible to prevent the same business from being repeatedly performed in the member.

At this time, it is preferable that the another server computer is provided in the server computer. With this configuration, processing performed by another server computer can be performed in the same server computer, and the number of computers used can be reduced.

According to the present invention, the member of the stock exchange can notify that the public information including at least one of the business message related to the operation of the stock exchange and the settlement information can be distributed. A method for notifying a client computer of a delivery possibility, wherein the server computer transmits a data setup completion notification to another server computer connected to the server computer when the data setup of the payment information is completed. A setup completion notification that performs a setup completion notification transmission procedure, transmits a data setup completion notification of the payment information to the client computer, and receives a setup completion notification that the date setup completion notification has been received from the client computer. Already Performing an information receiving procedure, transmitting the distributable information indicating that the public information can be distributed to the client computer, and receiving the distributable notified information indicating that the distributable information has been received from the client computer; A deliverable notified information receiving procedure, and a downloaded information receiving procedure of transmitting download information of the payment information to the client computer side and receiving downloaded information indicating that the payment information has been downloaded from the client computer, At least one of a browsed information receiving step of transmitting the payment information browsing information to the client computer side and receiving, from the client computer, browsed information indicating that the payment information is displayed on a screen. Perform the procedure, and complete the setup completion notification Performing a status notification information transmitting step of transmitting, to the another server computer, status notification information including at least one piece of information from a group consisting of the delivery possible notified information, the downloaded information, and the viewed information, After a predetermined period of time after another server computer receives the data setup completion information, if the status notification information has not been received, perform a stop command receiving procedure of receiving a stop command from the another server computer, Based on the stop command receiving procedure,
The problem is solved by performing an information transmission stop procedure for stopping information transmission to the client computer.

[0037] According to the present invention, public information including at least one of a business message relating to the operation of a stock exchange and settlement information is distributed to a client computer on a member side of the stock exchange. A data setup completion notification transmitting step for transmitting, to the computer, a data setup completion notification to another server computer connected to the server computer when the data setup of the payment information is completed; and a data setup completion notification of the payment information. To the client computer side, a setup completion notification received information receiving procedure of receiving the setup completion notification information indicating that the date setup completion notification has been received from the client computer, and a notification that the public information can be distributed. of Transmitting the transmittable information to the client computer side, receiving the transmittable notified information indicating that the transmittable information has been received from the client computer; and Transmitting to the client computer side, a downloaded information receiving procedure of receiving downloaded information indicating that the payment information has been downloaded from the client computer, and transmitting information for viewing the payment information to the client computer side; A viewed information receiving step of receiving the viewed information indicating that the payment information has been displayed on the screen from the client computer, at least one of the procedures, the setup completion notified information, and the delivery possible notified information, Downloaded information and viewed information A status notification information transmitting step of transmitting status notification information including at least one information from the group consisting of: to the another server computer; and elapse of a predetermined time after the another server computer receives the data setup completion information. Later, when the status notification information is not received, a stop command receiving procedure for receiving a stop command from the another server computer, and stopping the information transmission to the client computer based on the stop command receiving procedure. This problem is solved by a program for executing an information transmission stop procedure to be executed.

With such a configuration, it is possible to know whether or not there is any problem only in the exchange between the server computer and the client computer.

That is, despite the fact that another server computer has received the data setup completion notification indicating that the setup of the public information has been normally completed, a predetermined time has passed, and none of the status notification information has been received. If not, the public information setup itself is fine,
Since it is possible to predict that transmission / reception between the server computer and the client computer is abnormal, it is possible to know whether or not there is a problem only in the part of the exchange between the server computer and the client computer.

In addition, another server computer receives none of the status notification information despite the lapse of a predetermined time after receiving the data setup completion notification indicating that the public information has been set up normally. Otherwise, the server computer stops sending information to the client computer, so if it is assumed that there is a failure in the communication state between the server computer and the client computer, the information transmission is stopped. Is stopped, and the load on the server computer for information processing can be reduced. In addition, it is possible to construct a more complete and accurate monitoring system of the communication state in combination with other means for monitoring the communication state between the server computer and the client computer.

According to the eighteenth aspect of the present invention, a member of a stock exchange notifies that public information including at least one of a business message related to the operation of the stock exchange and settlement information can be distributed. A method of notifying a client computer of a delivery possibility, wherein the server computer transmits a data setup completion notification to another server computer connected to the server computer when the data setup of the payment information is completed. Perform the setup completion notification transmission procedure,
A data setup completion notification of the payment information is transmitted to the client computer side, and a setup completion notification information receiving procedure of receiving the setup completion notification information indicating that the date setup completion notification has been received from the client computer is performed. A deliverable notified information receiving procedure for transmitting deliverable information indicating that public information can be delivered to the client computer and receiving deliverable notified information indicating that the deliverable information has been received from the client computer. A download information receiving step of transmitting download information of the payment information to the client computer side and receiving downloaded information indicating that the payment information has been downloaded from the client computer; and Performing at least one of a browsing information receiving procedure of transmitting information to the client computer and receiving a browsing information indicating that the payment information is displayed on the screen from the client computer. A status notification information transmitting step of transmitting status notification information including at least one information from a group consisting of completion notification information, the distributable notification information, the downloaded information, and the browsed information to the another server computer; When a predetermined time elapses after the another server computer receives the data setup completion information, if the status notification information has not been received, a stop command receiving a stop command from the another server computer is received. Performing a procedure, based on the stop command receiving procedure,
Performing an information transmission stop procedure for stopping information transmission to the client computer, and after the information transmission stop procedure, when it is determined that the communication state with the client computer is normal, to the client computer The problem can be solved by performing an information transmission restarting procedure for restarting the information transmission.

According to the present invention, public information including at least one of a business message relating to the operation of a stock exchange and settlement information is distributed to a client computer on the member side of the stock exchange. To the computer, when the data setup of the payment information is completed, perform a data setup completion notification transmission procedure of transmitting a data setup completion notification to another server computer connected to the server computer,
A data setup completion notification of the payment information is transmitted to the client computer side, and a setup completion notification information receiving procedure of receiving the setup completion notification information indicating that the date setup completion notification has been received from the client computer is performed. A deliverable notified information receiving procedure for transmitting deliverable information indicating that public information can be delivered to the client computer and receiving deliverable notified information indicating that the deliverable information has been received from the client computer. A download information receiving step of transmitting download information of the payment information to the client computer side and receiving downloaded information indicating that the payment information has been downloaded from the client computer; and Performing at least one of a browsing information receiving procedure of transmitting information to the client computer and receiving a browsing information indicating that the payment information is displayed on the screen from the client computer. A status notification information transmitting step of transmitting status notification information including at least one information from a group consisting of completion notification information, the distributable notification information, the downloaded information, and the browsed information to the another server computer; When a predetermined time elapses after the another server computer receives the data setup completion information, if the status notification information has not been received, a stop command receiving a stop command from the another server computer is received. Performing a procedure, based on the stop command receiving procedure,
Performing an information transmission stop procedure for stopping information transmission to the client computer, and after the information transmission stop procedure, when it is determined that the communication state with the client computer is normal, to the client computer An information transmission restart procedure for restarting the information transmission of the above is solved by the program for executing the information transmission restart procedure.

With this configuration, the information is retransmitted after it is confirmed that there is no failure.
The burden of information processing on the server computer can be reduced.

According to the nineteenth aspect of the present invention, a member of a stock exchange informs that public information including at least one of a business message related to the operation of the stock exchange and settlement information can be distributed. A distributable notification method for distributing to a client computer, the distributable information transmitting step of transmitting distributable information indicating that the public information can be distributed to the client computer side, and the settlement information download information. To the client computer side, a downloaded information receiving procedure for receiving downloaded information indicating that the payment information has been downloaded from the client computer, and transmitting the payment information browsing information to the client computer side, The payment information is displayed from the client computer. Performing at least one of the viewed information receiving procedure of receiving the viewed information indicating that the information has been displayed above, and regarding the member among the confirmed information including the downloaded information and the viewed information, A member that performs a member-confirmed information transmission procedure of transmitting the member-confirmed information generated first to a server computer different from the server computer, and receives the member-confirmed information of the member from the another server computer. A side-confirmed information receiving procedure is performed, and the member's member-confirmed information is displayed on the member's client computer so that the distributable information can be displayed to be displayed or downloaded by an arbitrary client computer of the member. Is transmitted by attaching an identification that associates it with the corresponding deliverable information. That.

According to the present invention, the public information including at least one of a business message relating to the operation of a stock exchange and settlement information is distributed to a client computer on the member side of the stock exchange. To the computer, a distributable information transmitting procedure of transmitting distributable information indicating that the public information can be distributed to the client computer, and transmitting download information of the settlement information to the client computer,
A downloaded information receiving step of receiving downloaded information indicating that the payment information has been downloaded from the client computer, and transmitting information for viewing the payment information to the client computer side, and displaying the payment information on the screen from the client computer. A viewed information receiving procedure for receiving the viewed information indicating that the information is displayed above,
Among at least one procedure, and among the confirmed information including the downloaded information and the browsed information, the member confirmed information generated first with respect to the member, a server computer different from the server computer. The member-confirmed information transmitting procedure for transmitting to the member, the member-side confirmed information receiving procedure for receiving the member's member-confirmed information from the another server computer, and the distributable information is already transmitted by any client computer of the member In order to be able to display that the browsing or download has been performed, the member's client computer, the member confirmed information of the member,
This is solved by a program for executing a confirmed display procedure of transmitting with an identification associated with the corresponding distributable information.

With this configuration, it is possible to centrally manage information such as whether or not each member has viewed or downloaded the public information and which user among the members has viewed or downloaded the public information. It becomes possible. At this time, it is preferable that the storage medium stores the program according to any one of claims 21 to 24.

[0047]

An embodiment of the present invention will be described below with reference to the drawings. The configuration described below is
The present invention is not limited thereto, and can be variously modified within the scope of the present invention.

[0048] In this specification, the term "computer" is meant to include all information terminals provided with a computing device. For example, in addition to a supercomputer, a general-purpose computer, an office computer, a control computer, a workstation, and a personal computer, a portable information terminal, a mobile phone equipped with an arithmetic device, and the like are also included. The storage medium is the installation,
Computer readable storage media for execution, distribution, etc., eg, flexible disk, magneto-optical disk, CD, CD-ROM, CD-R, CD-RW, DV
D means a program according to the present invention.

The present embodiment relates to a settlement information system included in a stock exchange WAN system 1 which is a wide area network (Wide Area Network) system for securities transactions. The settlement information system according to the present embodiment is a system for transmitting and receiving settlement information and entry information in the stock exchange 14 between the stock exchange 14 and the member 2. This settlement information system includes Stock Exchange 1
As for the public information such as important information for the market operation and information with high urgency, information that can be distributed and ready to be distributed is distributed to a plurality of members 2 of the stock exchange 14.
A broadcast notification system as a distributable notification network system that simultaneously notifies special participants is also included.

The term “broadcast notification” generally refers to simultaneous notification to a plurality of persons. Hereinafter, a plurality of business messages and settlement information relating to the operation of the stock exchange 14, for example, a plurality of this distributable information will be described. Notification to members 2 at the same time is referred to as "broadcast notification". In this specification, notification to a part of members 2 at the same time, notification to some users included in the members 2 at the same time, 2 at the same time.

The stock exchange 14 is an organization that opens a stock market. The stock exchange 14 in the present embodiment is used for trading of securities, futures transactions such as securities indexes, and securities option transactions. An organization that opens the necessary securities trading market. The stock exchange 14 provides a place for buying and selling securities, manages buying and selling securities, examines and lists securities, manages listed securities, manages members 2, and the like. The securities market is a place for long-term funding of companies and countries (issuing market),
It is a place for public securities investment (secondary market).

The stock exchange 14 of the present embodiment is in the form of a member organization in which a securities company is a member 2. The member organization refers to an organizational form in which a person who manages and operates the stock exchange 14 and a person who buys and sells the securities market established by the stock exchange 14 are members of the same personality.

The member 2 of the stock exchange 14 means a regular member, a talented member, and a special participating member of the stock exchange 14. Normal,
Member 2 is a securities company. However, a person other than the securities company may be the member 2. The regular member refers to a securities company that can perform trading and the like on the market of the stock exchange 14 based on entrustment from customers or self-calculation. A talented member is a securities company whose main business is to mediate sales and purchases between regular members in the market of the stock exchange 14, that is, to perform matching operations such as buying and selling orders. A special participant is a non-regular member who has been qualified by the exchange to be eligible for trading in the futures and options markets.

In the present embodiment, DVP (Delivery Versus Payme) on the stock exchange 14 is used.
(nt: simultaneous or same day delivery of funds and securities). Reduce settlement risk and achieve global standards, and link the transfer of funds and securities to reduce the principal risk arising from a counterparty's default (e.g., Risk) can be eliminated.

The features of the DVP settlement employed in this embodiment will be described. First, the background and purpose of the introduction of DVP settlement are as follows. In the conventional settlement method on the stock exchange 14, the link between the securities and the transfer of funds is insufficient, so that when a default (default) occurs in the settlement of funds, the transaction of the securities by the non-performing member is completely completed. Cannot be stopped, and the principal risk cannot be eliminated.

Further, in this case, the damage incurred by the member 2 due to the default is guaranteed by the penalty loss compensation reserve, but the funding of the penalty loss compensation reserve is a special membership fee contributed by the member 2. Therefore, there was also a problem that the principal risk was ultimately borne by the member 2.

Furthermore, in Japan, preparations for executing a payoff are being made, and in consideration of the execution of the payoff, there is a need to further reduce the settlement risk. Improve the settlement environment in the future, such as replacing the securities custody transfer system at custody transfer institutions, starting handling convertible bonds (CB), establishing a system for settlement verification, etc., and using RTGS (immediate gross settlement system) for deposit settlement at the central bank・ Expansion is required. In addition, the G30 Recommendation and the ISSA Amendment Recommendation, which are global benchmarks for improving the settlement system,
It has been suggested that P should be introduced, and there is a need to achieve global standards for payment systems.

The DVP settlement system according to the present embodiment
It solves these problems and responds to requests,
By linking the transfer of funds and securities, there is an effect of eliminating a principal risk (risk of not being able to receive compensation after the funds or securities are delivered) resulting from a default of a counterparty.

FIG. 1 shows a target transaction for DVP settlement according to the present embodiment. In addition, the target transaction is not limited to these,
Of course, it may be changed appropriately. D of the present embodiment
In VP settlement, ordinary trading of domestic stocks, off-auction selling, first issue trading, basket trading, closing price trading, ordinary trading of beneficiary stocks, ordinary trading of convertible bonds, first issue trading, closing trading, off-auction trading Applicable to basket-to-basis transactions. These transactions together account for approximately 99.9% of the trading value of securities on a given stock exchange.

The six types of transactions relating to the securities handled by the custody transfer institutions, such as ordinary transactions, off-auction sales, first issue transactions, basket transactions, closing price transactions, and off-auction basket-to-ask transactions, are based on business rules and the like. Includes trading for error correction.

Here, the custody transfer organization 15 refers to an organization that operates a securities custody transfer system, which centrally stores securities and replaces the delivery of securities with the exchange of the certificate itself.
It refers to an institution that is provided in the custody transfer institution 15 and processes by transfer between accounts. The owner of the securities can exercise the right while depositing the securities with the custody transfer organization 15. The securities custody transfer system is a system aimed at streamlining and streamlining the storage and delivery of securities such as stock certificates in order to smoothly operate the securities secondary market.

The domestic stock certificate means a stock certificate other than a foreign stock certificate, and is a stock certificate issued by a domestic corporation. A convertible bond is a bond that has been granted the right to request the issuing company to convert to shares during the conversion request period. Ordinary trading is a term used on a specified stock exchange, and refers to a trading that is settled on the fourth day (excluding holidays) from the date of the conclusion of the sales contract. This is the most basic form of trading on a stock exchange.

In FIG. 1, ordinary trading of domestic stock certificates includes:
Includes buying and selling of target stocks that are concluded by exercising the rights of stock certificate option transactions deemed as ordinary transactions. Off-auction distributing refers to a trading method for distributing a large number of sell orders outside of a trading session. Specifically, a member receives a large number of sales orders from a customer on the condition that they are executed by off-auction sales, notifies the exchange when it is about to execute, and announces the conditions for sales after the end of the trading session Then the next day 8:
From 20 to 8:45, a method of receiving a bid application and completing a trade is being carried out.

The first issue transaction refers to buying and selling one issue of stock in a certain quantity or a certain amount or more. Transactions that are 100 times or more the trading unit may be referred to as first issue transactions. Basket trading refers to buying and selling multiple stocks simultaneously. A transaction in which 15 or more brands have a total trading value of 100 million yen or more may be called a basket transaction.

The closing price transaction is a transaction at a contract price at the end of the trading session. Off-auction basket pairing is “off-auction trading” in which an electronic trading network system is met.
Of these, transactions with predetermined standards or more, such as 15 or more brands and trading value of 100 million yen or more. It should be noted that the first issue trade, basket trade, and off-auction basket trade shown in FIG. 1 are limited to trades whose settlement date is the same as ordinary trade.

From the viewpoint of maintaining the efficiency of settlement on the stock exchange 14 and the practical feasibility, the DVP settlement system of the present embodiment employs the current netting settlement (the difference between the amount of the transferred securities and the received and paid funds). DV)
Set to P settlement.

The settlement time limit of the DVP settlement system will be described. In the DVP settlement system, the securities settlement time period (time period when the delivery member issues the securities to the stock exchange 14) is noon. Also, the DVP scheduled receipt / payment deposit time limit (the DVP scheduled receipt / payment amount (scheduled payment amount expected deposit amount) deposit time by the payment method (scheduled) member to the stock exchange 14) is noon. The DVP scheduled payment received will be applied to the fund settlement with a time limit for fund payment.

The time limit for paying funds (the time limit for paying funds to the stock exchange 14 by the paying member who has received additional payment of funds due to the failure and the member who has changed from receiving (planned) to paying) is 1:00 pm 30 minutes. The time at which funds are received (the time at which the stock exchange 14 issues funds to the receiving member and the time at which the surplus is returned to the paying member whose surplus amount has been paid due to the failure) is 2:00 pm. In the conventional settlement, the securities settlement time limit, the fund receiving time is 3:00 pm,
The time limit for payment was 1:00 pm.

A method for receiving a security receipt will be described. When the member 2 has delivered the delivered securities to the stock exchange 14, the member 2 can receive the received securities having a value corresponding to the delivered securities before the time limit for paying the funds. In addition, even for securities that have a value higher than the value of the delivered securities, the required early collateral can be deposited on the stock exchange 14 to enable similar early receipt. In order to facilitate the transfer of such securities and securities and the transfer of funds and securities, and the early receipt of securities received, we will adopt a net debit method of securities settlement and introduce a collateral system, a fail system and an accompanying buy-in system.

Here, each term will be explained. The net debit method is a method in which, at each transfer date on the settlement date, the number of receivables that match the value of the delivered securities and the deposited collateral is calculated, and the received securities are received according to a predetermined order.

The DVP scheduled receipt / payment (required collateral) is a DVP scheduled receipt / payment in which the member (scheduled) of paying the fund deposits the scheduled payment amount with the stock exchange 14 by noon on the settlement date. Specifically, the member 2 whose payment obtained by the provisional amount of the settlement price (the amount not considering the failure of the day) and the difference calculated by the mark-to-market difference is overpaid, Is paid to the stock exchange 14 by noon, which is the security settlement time limit, as the scheduled payment for DVP.
The payment of the DVP scheduled payment shall be made by transfer from the member account to the stock exchange account at the fund settlement bank. By depositing the DVP scheduled payment, it becomes possible to receive securities received by noon except for failures.

The deposit received the day before (optional collateral) is the member 2
Means collateral (cash and substitute securities) deposited on the stock exchange 14 the day before the settlement date. This allows for early receipt of a security equivalent to the value of the collateral.

In the case of the fail system, if the securities to be delivered cannot be delivered to the stock exchange 14 on the settlement date (fail), the securities and fund settlement (settlement price) are carried forward to the next day, and the carried-over date is set as the settlement date. Securities related to settlement of trading transactions, settlement price and re-netting (CNS: Conti
nuous Netting Settlement)
This is a system for settlement after payment. The fail system imposes penalties, such as late damages, on fail members.
The failing member shall pay the delinquent damages of 4 yen per day to the receiving member through the stock exchange 14 for the amount equivalent to the failed delivery of 100 yen. The rate of delinquent damages must be set to a rate higher than the lending interest rate, arbitrage rate, etc., in order to control the failure and to eliminate the failure early.

If the fail member does not cancel the fail by the fifth business day from the initial settlement date, the stock exchange 14 will pay the amount of money determined by the stock exchange 14 to the member 2. Will be collected. With the introduction of the fail system, issues related to DVP settlement will be B. No system is adopted. The conventional securities delivery slip (DB) system is a DV system in that the transfer of securities is performed even though the transfer of securities has not actually been completed.
This is because it does not fit the idea of P.

Note that the securities delivery slip (DB) system means that if securities cannot be delivered on the settlement date, the system will return to DB. B. Is a system for settlement (the transfer of securities and the corresponding money) by issuing
D. B. Issue, a securities lending relationship is established between the transferee and the receiver (continues until DB repayment). By introducing the fail system, the receiving member can receive securities with priority in settlement on the next day, and request the securities exchange 14 to buy and deliver securities (buy-in). There is a merit that can be.

However, in order to maintain the current settlement situation that strictly adheres to the settlement date, instead of accepting unlimited failures, penalties such as delay damages for suppressing the occurrence of failures and the rights of failed members A mechanism such as buy-in (purchase and delivery of securities for fail) will be established. In the event of a default, the stock exchange 14 will execute the funds settlement and use the securities that have stopped taking over or the deposited collateral to cover the damages caused by the default.

If a failure occurs on the day before the reference date and time for determining the rights of the shareholders, the stock exchange 14
Collects the amount of money specified by the member 2 from the member 2 concerned. By any chance,
When an overage failure occurs, the processing of rights such as dividends and voting rights is coordinated between the parties.

The buy-in system is a system in which a failed member can request the securities exchange 14 to purchase and deliver (buy-in) the securities related to the fail if the failed member cannot be resolved by settlement on the next day. Say. In the present embodiment, it is assumed that a buy-in request can be made when a failee continues over a security settlement time limit (for example, 1:00 pm, noon, etc.) on the day after the failee day.

The receiving of the fail depends on the priority of the receiving order.
Since there is a high possibility that the failure will be resolved the next day, the request for a buy-in can be made after the settlement on the following day. Depending on the priority of the receiving order,
Since there is a high possibility that the failure will be resolved the next day, the request for a buy-in can be made after the settlement on the following day. The stock exchange 14 executes a buy-in when a fail-in member receives a request for a buy-in, and when the fail-related pertaining to the request is not resolved by the fourth business day from the buy-in request date, Charge the failed member to the failing member with the oldest position.

If the execution of all the scheduled execution quantities is not completed on the original scheduled execution date of the buy-in, the member can withdraw the request (withdrawal of the buy-in request) on the following day. Claims can be withdrawn from the billing position with the oldest billing date, and partial cancellation of the balance of each billing position is not allowed.

In the case of buying securities (buying in a sell order: buy-in order) when executing a buy-in, the order acceptance time is 15:00 to 15:30, and the execution (contract) time is 15:15.
30 + α, the execution method is a competitive bidding method in the range of X% (undecided) from the closing price on the day of the execution day, and the order receiving method is input by the member 2 using the stock exchange WAN system 1.

Referring to FIG. 2 and FIG. 3, the difference between the conventional transfer processing and the DVP settlement of the present embodiment will be described for a transfer request method relating to securities settlement. Conventionally, as for the transfer request of the stock exchange 14 and the account transfer at the custody transfer organization 15, as shown in (A) and (B) of FIG.

On the other hand, in the transfer processing in the DVP settlement of the present embodiment, the transfer request at the stock exchange 14 and the account transfer at the custody transfer organization 15 are performed by both the receiving member and the receiving member as shown in FIGS. ), It is assumed that the counterpart of the delivery is the stock exchange 14. However, in the transfer request of the stock exchange 14 in (A), the transfer from the stock exchange 14 to the receiving member is subject to a transfer condition.
Further, in the account transfer in the custody transfer organization 15 of (B), the transfer from the stock exchange account to the receiving account is performed in accordance with the order determined in advance and according to the value of the securities delivered and collateral deposited by the receiving member. Debit transfer shall be performed.

In the present embodiment, the stock exchange 1
4 and the account transfer at the custody transfer institution 15, both the transfer member and the receiving member claim that the counterparty of the transfer will be the stock exchange 14, so that the principal risk (funds or funds) resulting from the default of the settlement of the counterparty. The risk of not being able to receive compensation after the security has been delivered can be eliminated.

FIG. 4 is a diagram showing the configuration of a DVP settlement system according to this embodiment. The DVP settlement system according to the present embodiment is a stock exchange WAN system 1 which is a wide area network system between the member 2 and the stock exchange 14, DV.
DVP payment system 3, which performs the business processing of P payment, DVP
Settlement system 1422, fund settlement bank system 1423, securities custody transfer system 1421 for settlement of funds for settlement
Is the main component.

The DVP settlement system 3 and the clearing system 1422 are built in the stock exchange 14, and the stock exchange WAN system 1 is built between the stock exchange 14 and the member 2. The funds clearing bank system 1423
The fund account of the member 2 is set up in the opened fund clearing bank, and the fund clearing is performed by exchanging information with the DVP clearing system 3 and the clearing system 1422 in the stock exchange 14.

The securities custody transfer system 1421 is a member 2
DVP settlement system 3 in the stock exchange 14
By exchanging information with the clearing system 1422, securities settlement is performed. The DVP payment system 3 is connected to terminal computers 1426 such as a payment status monitoring terminal computer, an institution participant terminal computer, and a central bank net terminal computer, and is configured to be able to execute each task.

The fund clearing bank system 1423 includes a clearing bank dedicated terminal computer 142 for fund clearing.
4. Central bank net system 1425 is connected. In addition, the clearing system 1422 includes a stock exchange 14
A business processing system 431 is connected.

Next, an outline of the processing performed between the systems will be described. Clearing system 1 of the stock exchange 14
422, the DVP settlement system 3, and the stock exchange WAN system 1, a settlement management process 1427 is performed. Settlement by netting includes
Generation of settlement information, management of deposit / return of collateral paid on the previous day, settlement execution status monitoring, fail / buy-in management, correction / cancellation information of securities transfer request due to fail, and generation of fund adjustment information are performed.

The security depository transfer system 142 is provided between the DVP settlement system 3 and the securities depository transfer system 1421.
1, the settlement and settlement of securities settlement information 1428 of the account transfer by the net debit method is performed. DV
Among the P settlement system 3, the clearing system 1422, and the fund settlement bank system 1423, the fund settlement processing 1429,
That is, transmission and reception of fund settlement information with the fund settlement bank system 1423 are performed.

Between the stock exchange WAN system 1 and the member terminal computer 9, transmission of clearing and settlement information to the member site (registration and browsing of the WWW browser 11 b and file transfer), execution of contracts and settlements, delivery of buy-in requests A paperwork 1430 is performed.

FIG. 5 shows the custody transfer agency 15 and the stock exchange 1
FIG. 4 is a diagram showing an outline of a flow of a settlement business process performed by 4, a member 2, and a fund settlement bank 16. Here, “T” refers to a contract date, and “S” refers to a settlement date. In the present embodiment, the S day corresponds to the T + 3 day. On T day, T + 1 day,
In step 431, the stock exchange 14 transmits a sales collation / settlement schedule information notification to the member 2 side.

On the T + 2 day, the member 2 determines in processing 432 that
A security deposit is posted to the stock exchange 14 the day before. In step 433, the stock exchange 14 sends the securities settlement confirmation information notification to the member 2 side. From the date T to the date T + 2, the stock exchange 14 performs the information generation of the process 434 and the management of the previous day's collateral.

Further, on T + 2 day, the stock exchange 14 transmits a transfer request or the like to the custody transfer organization 15 in a process 435. At this time, the transfer to the receiving member is conditional. Further, in a process 436, information necessary for the judgment of the previous day's deposit is transmitted. In step 437, the securities transfer institution 15 transmits a settlement execution status notification to the stock exchange 14 side.

From 9:00 to 12:00 on T + 3, 1
From 4:00 onward, the stock exchange 14 performs processing 460
To monitor information generation / payment status. 9:00 on T + 3
From 12:00 to 12:00, the stock exchange 14 determines in process 439
A transfer request for the DVP scheduled payment is transmitted to the fund settlement bank 16. In this case, a reverse check is made for members who use the clearing bank account. The member 2 transfers the DVP scheduled payment to the fund settlement bank 16 in process 440. The fund clearing bank 16 performs the account transfer processing of processing 438, and
At 41, a transfer completion notice is transmitted to the stock exchange 14 side.

Upon receiving the transfer completion notification in the process 441, the stock exchange 14 instructs the storage / transfer agency 15 to execute the D in the process 442.
Information necessary for determining the VP scheduled payment is transmitted. The custody transfer organization 15 operates from T + 2 to T + 3 9:00 to 12:
In the process 443a, the transfer condition satisfaction determination and the account transfer are performed until 00.

At 12:00 to 12:30 of T + 3, the custody transfer organization 15 sends to the stock exchange 14 in process 443b.
Send settlement execution status notification. In response to the process 443, the stock exchange 14 determines a fail in a process 444. Then, in process 445, the transfer request is corrected / cancelled by the storage transfer institution 15 side. In addition, the stock exchange 14 transmits a fail information notification to the member 2 in process 446,
In processing 447, the fund settlement confirmation information notification is transmitted, and processing 44 is executed.
At step 8, an additional payment request is transmitted.

At 12:30 to 13:30 of T + 3, the member 2 makes an additional payment to the fund clearing bank 16 in process 449. The fund clearing bank 16 makes an account deposit in process 450. The member 2 transmits an additional payment notice to the effect that additional payment has been made to the stock exchange 14 in the process 451. Stock Exchange 1
4 receives this processing 451 and transmits an additional payment notice to the custody transfer organization 15 in processing 452.

[0099] Receiving this processing 452, the custody transfer organization 15 performs an account transfer processing in processing 453. Stock Exchange 1
4 transmits a fund adjustment / transfer request (fund release) to the fund settlement bank 16 in a process 454. The fund clearing bank 16
In response to the processing 454, the funds are adjusted in the processing 455 until 14:00 of T + 3. 13: 30-1 of T + 3
At 4:00, the custody transfer organization 15 transmits a settlement execution status notification to the stock exchange 14 in process 456.

After 14:00 of T + 3, the fund clearing bank 16 performs an account transfer in a process 457, and releases the fund in a process 458. Also, in processing 459, a fund adjustment / transfer completion notice is transmitted to the stock exchange 14 side.

If the failure is confirmed in the process 444 on the T + 3 day, the member 2 transmits a buy-in request to the stock exchange 14 in the process 461 as needed on the S + n day. Upon receiving the processing 461, the stock exchange 14 performs the processing 462
Perform fail and buy-in management. Stock Exchange 14
Transmits a buy-in information notification to the member 2 in process 463. Thus, the flow of FIG. 5 ends.

FIG. 6 is a diagram showing an outline of the stock exchange WAN system 1 constructed between the member 2 and the stock exchange system center 427c. The member 2 has a client computer 9 and this client computer 9
Is connected to a terminal computer 45.
The client computer 9 is connected to a business server computer in the member 2 installed in a section (securities handling manager) in charge of securities settlement and fund settlement. Member 2
The business server computer and the client computer 9 may be integrally configured.

The member 2 and the stock exchange system center 42
7c is connected by a dedicated line or a communication line network. Normally, a dedicated line is used, but in case of trouble, a communication line network is used as a backup line.
The stock exchange system center 427c includes the stock exchange W
DVP server computer 4 that operates AN system 1
And a DVP settlement system server computer 3s and a clearing system server computer 422s.

On the member 2 side, the client computer 9 or the business server computer of the member 2 installed in the section (securities handling manager) in charge of securities settlement and fund settlement of the member 2 such as a securities company is used. On the member 2 side,
It manages ID and password.

The member 2 receives the member-specific sales statement, summary A, general settlement table, settlement settlement quantity, delivery price calculation table, and the like through the settlement information system of this embodiment. The member 2 transmits a buy-in request report, a buy-in acceptance application, and a buy-in request withdrawal report by the settlement information system of the present embodiment. The transmission method from the stock exchange 14 to the member 2 is such that the electronic document is in an HTML search format or the like, and the data is CSV file transfer. The transmission method from the member 2 side to the stock exchange 14 side is to input and transmit necessary items in a predetermined HTML form.

In the present embodiment, a transaction related to a stock handled by the custody transfer organization 15 is a target transaction of the DVP. Further, in the present embodiment, the DVP can be introduced while continuing the netting settlement (transfer of the difference between securities and money) used conventionally. As a result, the efficiency of settlement on the stock exchange 14 can be maintained.

In the present embodiment, as shown in FIG. 7, in the securities settlement, the securities exchange 1
Issue 4 by noon on the settlement date. In the settlement of funds, payment by the paying member to the stock exchange 14 shall be made by 1:30 pm on the settlement date and payment by the receiving member shall be made at 2 pm by the receiving member. And

Here, the settlement price is the settlement price (the amount of money obtained by multiplying the amount of securities actually delivered by the settlement price) and the mark-to-market difference (contracts related to all sales transactions). The difference between the settlement price and the settlement price, and the amount of money obtained by subtraction calculation of the difference between the settlement price on the previous day and the settlement price on the day related to the delivery carried over by fail).

A specific example of the DVP scheme image is shown in FIG.
Shown in The settlement time limit is as follows. That is, in the example of FIG. 7, the securities settlement period and the DVP scheduled payment receipt / payment period are 1:00 pm, the fund payment period (appropriation from the DVP scheduled receipt / payment) is 2:15 pm, and the fund receiving time is 2:45 pm Minutes. A. Securities can receive the B shares by delivering (sending) the A shares and the DVP scheduled payment to the stock exchange 14 by 1:00 pm. Oto Securities will deliver the B shares to the stock exchange 14 by 1:00 pm. A shares can be received after delivery of B shares. The funds will be received at 2:45 pm The stock exchange 14 will use the scheduled payment for DVP at 2:15 pm for payment related to fund settlement.

Another specific example of the DVP scheme image is as follows.
As shown in FIG. The settlement time limit is as follows. That is, in the example of FIG. 8, the securities settlement period and the DVP scheduled receipt / payment time limit are noon; Time. A. Securities will post the scheduled payment for DVP to the stock exchange 14 by noon. Due to the failure to deliver A shares, the shortfall will be paid by 1:30 pm. The B shares can be received at 1:30 pm

[0111] Otsu Securities will sell B shares by noon on the stock exchange 1
Hand over to 4. The company will receive 1.2 million yen at 2:00 pm, including the value of the failed A shares. The stock exchange 14 will use the DVP scheduled payment at 1:30 pm for payment related to fund settlement.

FIG. 9 shows still another specific example of the DVP scheme image. The settlement time limit is as follows. That is, in the example of FIG. 9, the securities settlement period and the DVP scheduled receipt / payment time limit are at noon, the fund payment period (transfer of the shortfall due to fail) is 1:30 pm, the fund receiving time and the DVP
The return time of the scheduled payment surplus is 2:00 pm.

A-Securities delivers (inserts) the A shares and the scheduled payment for DVP to the stock exchange 14 by noon.
Due to the failure of the delivery of B shares, the funds and the surplus of the scheduled payment for DVP will be received at 2:00 pm (returned). Otsu Securities will pay 900,000 yen by 1:30 pm because of the failure to deliver the B shares. A shares can be received after payment of the funds (1:30 pm).

Next, the link method will be described. When the member 2 delivers the securities to be settled to the stock exchange 14 in order to receive the securities by the receiving member as soon as possible, the securities settled with the value equivalent to the delivered securities are completed. (Payment time limit) It shall be possible to receive it before.

[0115] Receipt of securities that exceed the value of the delivered securities is made possible by posting collateral. By such a link method, securities or money of the same value as the unexecuted debt of each member 2 is reserved inside the clearing house of the stock exchange, and it is possible to eliminate the principal risk in the settlement of the stock exchange 14. At the same time, the securities and funds of the member 2 can be efficiently and smoothly operated.

Next, the scheduled payment for DVP (essential security)
The operation of the collateral system including collateral posted on the previous day (voluntary collateral) will be described. It is assumed that the DVP scheduled payment received from the member 2 will be used for payment relating to fund settlement at 1:30 pm, which is the time limit for fund payment. If the amount of the payment received and calculated after noon in consideration of the failure is different from the amount paid as the DVP scheduled payment, it is 1:30 pm, which is the fund payment time limit, or the time of fund reception. Adjust at 2 pm

[0117] The target transaction of the DVP is a sales transaction relating to the brand handled by the custody transfer organization 15. It should be noted that it is a matter of course that trading transactions relating to non-handled issues may be included in the target transactions.

In the securities settlement, delivery of securities to the stock exchange 14 by the member is performed by noon on the settlement date. In the settlement of funds, payment by the paying member to the stock exchange 14 is performed until 1:30 pm on the settlement date, and receipt by the receiving member from the stock exchange 14 is performed at 2:00 pm.

The quantity of securities to be exchanged for settlement is
Same member 2 for DVP transactions with the same settlement date
The difference between the sold and purchased quantities of securities for each issue. The difference argument amount includes the quantity of securities related to delivery that failed in the settlement on the previous day and was carried forward to the day.

The amount of money to be transferred for settlement is determined by the total selling price (clearing price (closing day closing price of the relevant issue) x the amount to be delivered) and the total purchase This is the balance of the payment (clearing price x underwriting quantity). This balance excludes the amount corresponding to the securities on delivery that failed on the day. As for the amount of money to be given and received for settlement (hereinafter referred to as “settlement price”), the provisional amount (the amount that does not take into account failures) becomes Is calculated after noon on the settlement date.

When a difference is generated by comparing the execution price and the settlement price for all the sales transactions, and when a difference is generated by comparing the settlement price of the previous day with the price of the day for delivery carried over by fail, It is assumed that money corresponding to the difference is transferred through the stock exchange 14 on the settlement date. This transfer of money is called "price washing". The money to be exchanged for the price mark (hereinafter referred to as “price difference”) is
Netted and exchanged with the settlement price. Hereinafter, the money actually transferred is referred to as “receipt and payment”. The amount of money to be given and received for price washing is the difference between the total payment amount of the same member 2 and the total reception amount. The transfer of the mark-to-market difference shall not be carried over to the next day.

FIG. 10 and FIG. 11 are diagrams showing the comparison of the transfer of the price difference with the conventional method. 10 shows the original contract, the upper part of FIGS. 10 and 11 shows the conventional settlement method, and the lower part of FIGS. 10 and 11 shows the DVP settlement method according to the present embodiment. In the transfer of the settlement date in the conventional method (upper column in FIG. 10), as a result of netting, 1
The delivery amount per thousand shares is different. In the case where delivery of 1,000 shares has not been completed in the conventional method (upper right column in FIG. 10), the C member must pay the price even though he cannot actually receive the stock certificate. D. B. The amount of the deposit is based on the previous day's closing price as well as the settlement price in DVP settlement.

On the next day of the conventional method (upper left column in FIG. 11), even if the value of the brand increases, the D.I. B. No additional deposits will be made. D. The next day of the conventional method B. At the time of repayment (Fig. 1
In (1 upper right column), A member delivered 1,000 shares,
D. B. Receive a refund of the deposit. On the settlement date of DVP settlement in the present embodiment (lower column in FIG. 10), in order to avoid recalculation of netting in the event of a failure, the delivery amount per 1,000 shares for each member 2 is unified with the settlement price. I do. The difference from the contract price will be given and received as the price difference. In the case where 1,000 shares have not been delivered in the DVP settlement according to the present embodiment (FIG. 10)
In the lower right column), the C member does not need to pay the settlement price of 1.1 million yen because he cannot receive the stock certificate. Price washing is performed regardless of whether there is a failure.

On the day following the DVP settlement of this embodiment (lower column in FIG. 11), the price of the relevant brand has risen, and the increase is exchanged as a mark-to-market difference. This eliminates price fluctuation risk. On the second day after the DVP settlement of the present embodiment (lower right column in FIG. 11), between the A member and the stock exchange 14 to the C member, the DV of the stock certificate (1,000 shares) and the settlement price (1.3 million yen)
Perform P settlement and transfer of 100,000 yen of price difference.

After delivery of securities from the delivery member to the stock exchange 14 by noon on the settlement day, the settlement price corresponding to the actually delivered securities is transferred.
At this time, in order to allow the receiving member to receive the securities at an early stage, the member 2 transfers the securities passed for settlement to the stock exchange 14
In the case of delivery, the securities received shall be received before the end of fund settlement (payment time limit) corresponding to the delivered securities (considering the amount of mark-to-market difference given and received by the member 2 on that day). Can be done.

In addition, receipt of securities that exceed the value of the delivered securities is made possible by providing collateral. In this way, the securities equivalent to the unexecuted debt of each member 2 are retained in money inside the stock exchange clearing house, and the principal risk in the settlement on the stock exchange 14 can be eliminated. At the same time, efficient and smooth management of the securities and funds of the member 2 becomes possible.

The security settlement is performed as follows. The transfer of securities shall be performed by transfer of the account at the custody transfer agency 15. The stock exchange 14 receives the transfer from the account of the transfer member provided at the custody transfer agency 15 to the account of the stock exchange 14, and It is assumed that the account of the exchange 14 is transferred to the account of the receiving member. Provided, however, that the receiving member's unfulfilled debt (securities and money (receipt payment) that the receiving member has not delivered to the stock exchange 14) will be transferred from the account of the securities exchange 14 relating to the securities of value. The transfer to the receiving member's account shall be performed after the end of the fund settlement (payment time limit) unless the receiving member deposits security corresponding to the value of the securities to be received with the stock exchange 14. At this time,
Assignment designation (designation of the counterparty for the transfer of securities) is not performed.

Delivery of securities from the stock exchange 14 to the receiving member is performed according to the order determined by the following method. That is, the receiving member ranking for each brand is determined in advance according to the following rules. The member who failed in the settlement of the issue on the previous day (failed member) has priority over the other members. The order of failed members and the order of other members are determined by lottery.

The receiving rank (receiving brand ranking by member) of the receiving brand for each member 2 is determined at the time of each transfer on the settlement date on the basis of the delivery status from the transferring member, the balance of the head office account, and the like. The combination is determined so that the securities can be transferred most efficiently. In order to ensure the fairness of the decision of the member 2 to be the fail partner, the status of the deposit of each member 2 and the execution status of the settlement are not considered. The order of receipt from Member 2 is not reported. FIG.
FIG. 2 is a diagram showing a comparison of the receiving member ranking by brand with the conventional assignment designation system when the netting result of brand A is as shown in the leftmost table. The upper part shows the conventional assignment designation system, and the lower part shows the DVP settlement system according to the present embodiment.

FIGS. 13 and 14 are diagrams showing the relationship between unexecuted debts and account transfers. In the case of FIG. 13, when the delivery member (hereinafter, referred to as “fail member”) related to the delivery that has failed has already delivered 90 securities (issued securities: delivered securities), the settlement price is 30.
By paying the price difference 5, the security 120 becomes receivable (acceptance security). In the case of FIG. 14, the fail member has already delivered 90 securities (issued securities:
When the security 90 is received (secured securities), the settlement price 30 is received, and the price difference 5 is paid.

The fund settlement is performed as follows. The transfer of money (payment / receipt) can be made by a member 2 from a bank designated by the stock exchange 14 (hereinafter referred to as “clearing bank”) or a central bank.
Transfer of the account at the bank (hereinafter referred to as “financial settlement bank”) selected by
Is transferred from the account of the paying member provided at the fund clearing bank to the account of the stock exchange 14 and transferred from the account of the stock exchange 14 to the account of the receiving member.

In the present embodiment, a security system is adopted. The receiving member can receive securities before the end of fund settlement (payment time limit) by depositing money or securities corresponding to the value of the securities to be received at the stock exchange 14 as collateral. And The security system includes DVP
There are scheduled payments and collateral paid the day before.

The DVP scheduled payment will be described. Member 2 who has overpaid the amount obtained by subtracting the provisional amount of the settlement price and the mark-to-market difference, uses the amount of the overpaid amount as the scheduled payment for DVP, the securities settlement time limit (For example, by noon), it is assumed to be posted to the stock exchange 14. As a result, in the securities settlement time limit (for example, at noon), it becomes possible to receive all securities except for the failed portion.

It is assumed that the payment of the DVP scheduled receipt / payment is made by transfer from the member account to the stock exchange account at the fund settlement bank. Transfers at clearing banks
Performed by "reverse lookup". DV received from member 2
It is assumed that the scheduled payment received for P will be used for payment related to fund settlement at 1:30 pm, which is the time limit for fund payment.
If the amount of the payment received and calculated after noon in consideration of the failure is different from the amount paid as the DVP scheduled payment, the time of the fund payment is 1:30 pm or the time of fund reception is 2 pm Adjust at times. No “reverse lookup” is performed for the transfer of the shortfall.

[0135] The delivery member ("fail member") related to the delivery that has become a failure has a payment amount of DVP.
Since the expected payment amount will be exceeded, the underpaid amount (= the amount corresponding to the failed delivery) will be transferred to the fund settlement account of the stock exchange 14 by 1:30 pm, which is the fund payment time limit. I will transfer it. At this time, it is assumed that fund settlement (payment) = full application of the DVP scheduled receipt and payment price + transfer of the shortfall amount.

The receiving member relating to the failed delivery (hereinafter, referred to as “failed member”) receives the payment at the time of the 2nd pm, which is the fund receiving time, because the payment amount of the payment is less than the DVP scheduled payment amount. At the time, the surplus amount of collateral (= the amount equivalent to the failed delivery) is
Money transfer account. At this time, it is assumed that fund settlement (payment) = partial appropriation of the DVP scheduled receipt / payment (reception of surplus collateral).

In the case where the failing member or the failed member becomes the delivery or delivery of the failed delivery in the delivery of a different brand, the payment and receipt of the amount equivalent to the delivery of the failed delivery are made. If the result is overpayment, the amount is deemed to be underpaid, and the amount is paid by funds settlement (payment) of the underpaid amount. If the amount is overpaid, the amount is deemed as surplus. Received by fund settlement (payment). If the member 2 who received the amount obtained by subtracting the provisional amount of the settlement price and the mark-to-market difference became an overpayment and became a payment method of the payment due to the failure, the member 2 who paid for the shortfall will receive the funds The payment amount shall be transferred according to ()).

[0138] The security deposit received the day before will be described. Member 2
By posting collateral on the stock exchange 14 by the day before the settlement date, it is possible to receive securities received corresponding to the amount of the pledged security. The use of the security deposit on the previous day is optional for the member 2. The scope of eligible collateral shall be based on the margin on futures / options transactions. Regarding the value of the substitute securities,
Same as the margin for futures and options transactions. Upon receiving a security return application from the member 2, the security shall be returned after the completion of fund settlement (payment time limit) on the application date.

The handling of the fail at the end of the term or the like is as follows. If the member 2 generates a failure on the day before the record date for determining the rights of the shareholders, etc., the member 2 shall collect the amount of money specified by the member 2 from the member 2. I do. The amount should have a deterrent effect since it is necessary to avoid failures on the day as much as possible. Since it is difficult to uniformly handle the processing of rights such as dividends and voting rights due to a fail on that day, the parties will coordinate with each other.

At the time of default, the stock exchange 14 executes the fund settlement and uses the securities whose collection has been stopped or the deposited collateral to cover the damage caused by the default.

FIG. 15 shows the main configuration of the payment information system according to the present embodiment. The settlement information system of the present embodiment is included in the stock exchange WAN system 1 constructed between the stock exchange 14 and the member 2. Stock Exchange W
The AN system 1 refers to a wide area communication network system using a communication network provided by the stock exchange 14, and is constructed between the stock exchange 14 and the member 2, and a buy-in request is made between the member 2 and the member. And the like, transmission and reception of entry information such as, and transmission and reception of provided documents and notification documents. As the stock exchange WAN system 1, there is a Target system.

The stock exchange WAN system 1 includes a settlement information system which is a system for transmitting and receiving settlement information and entry information on the stock exchange 14 between the stock exchange 14 and the member 2. In the present embodiment, the stock exchange WAN system 1 including the settlement information system is provided by the stock exchange 14. However, the present invention is not limited to this. The management organization may provide the stock exchange WAN system 1.

The payment information system includes a DVP server computer 4 on the stock exchange 14 side, a WWW server computer 5, a client computer 9 on the member 2 side,
The DVP server computer 4 has a CSI (Clearing Se as a separate server computer connected to the server computer).
(letter Information) server computer 12.

The DVP server computer 4 as a server computer is a computer that controls the settlement information system. FIG. 16 shows the DVP server computer 4
1 shows a hardware configuration. The DVP server computer 4
C as a central processing unit for calculating and controlling data
PU21, storage device RAM22, ROM23, H
It includes a DD 24 and a storage medium device 25. CPU 21
Executes various processes according to a program stored in the ROM 23 or the HDD 24. The RAM 22 stores data and the like necessary for the CPU 21 to execute various processes.

A keyboard 26 and a mouse 2 as input devices
7 is appropriately operated when a predetermined command is input to the CPU 21. Further, information, images and the like displayed in a predetermined format are output and displayed on the display device 28 and the printer 29 which are output devices.

The storage medium device 25 includes an external hard disk, a magneto-optical disk, a CD-R, a CD-RW, a DVD,
It is constituted by a memory stick or the like, and is configured to appropriately store data transmitted through the communication device 30 and read the data.

Communication device 30 as input device and output device
Are configured to transmit data to the outside and receive data supplied from the outside. The communication device 30 corresponds to a distributable information distribution unit.

The DVP server computer 4 has a storage device provided in the computer, for example, an HDD 24,
Form data acquired from the SI server computer 12,
A settlement database 6 in which settlement information such as contract data is registered, a business message table 176 in which business messages relating to the operation of the stock exchange 14 are registered, and distributable information before a lapse of a predetermined period from when distribution is possible are registered. And a download database 7 in which public information data to be downloaded by the client computer 9 is registered. The HDD 24 also has the notification functions 167 and 16
8, information communication server 166 and the like are stored.

The payment database 6 stores payment information obtained from the CSI server computer 12. That is, when payment information is newly created in the CSI server computer 12, this payment information is registered in the payment information file 13 of the CSI server computer 12, and is transmitted to the DVP server computer 4 side.
It is registered in the settlement database 6.

[0150] The settlement information is also referred to as a form, and in this embodiment, is information relating to settlement of securities. For the reconciliation business, contract reconciliation information such as a sales statement, summary, etc., right exercise information such as a declaration / allocation statement, etc., open interest management information, and for the settlement business, a general clearing sheet, a total payment payment calculation sheet (planned amount) ) Etc., payment receipt calculation table (finalized amount), confirmation notice information such as additional payment notice, counterpart designation information such as receipt / transfer designation sheet related to settlement on base date, settlement report information, etc. For collateral management, the previous day's collateral information such as the previous day's collateral receipt / payment status table, the previous day's collateral balance table, etc., for the previous day's collateral information, margin information, and for fail management, fail information such as fail information notification and buy-in execution notification , And information such as a buy-in information notification such as a buy-in request report.

A business message of the public information is registered in a business message table 176 (not shown). Registration of the business message in the business message table 176 is performed from the terminal computer of the payment information system operator.

In the download database 7, public information that can be distributed is registered in a downloadable file format. When download is instructed on the screen of the broadcast notification program 11c of the client computer 9 or the screen of the WWW browser 11b, the public information is downloaded from the download database 7.

The hardware configuration of the CSI server computer 12 is the same as the hardware configuration of the DVP server computer 4 and will not be described. The CSI server computer 12 is linked in data with a DVP settlement system server computer (not shown) that controls DVP settlement. The CSI server computer 12 transmits public information such as buying, selling, executing, and settlement of securities managed by the DVP settlement system server computer (not shown). It is a computer created every day.

In the CSI server computer 12, a storage device, for example, an HDD stores a settlement information file 13 in which public information such as sales, contracts, settlement, and settlement of the created securities is registered. The DVP server computer 4 is configured to receive payment information from the payment information file 13.

The WWW server computer 5 is a computer for providing, from the stock exchange 14 side to the member 2 side, a home page relating to settlement information and business messages via the Internet which is a communication network. That is, the WWW server computer 5 is provided between the DVP server computer 4 and the client computer 9 and plays a role in transmitting and receiving information between the DVP server computer 4 and the client computer 9.

The hardware configuration of the WWW server computer 5 is the same as the hardware configuration of the DVP server computer 4, and the description is omitted. The WWW server computer 5 stores, in a storage device, for example, an HDD, a content database 8 in which screen content information for displaying various information on the screen of the client computer 9 of the member 2 is registered. When a request to view public information is made on the WWW browser 11b screen or the broadcast notification program 11c screen of the client computer 9, the WWW server computer 5 reads the requested public information from the settlement database 6 of the DVP server computer 4. And adds the information registered in the content database 8 to the client computer 9.
And send it for viewing.

Also, the WWW server computer 5
When the download of public information is requested on the screen of the WW browser 11b, the public information requested to be downloaded is acquired from the settlement database 6 of the DVP server computer 4 and transmitted to the client computer 9 for download. Fulfill. A communication device (not shown) included in the WWW server computer 5 includes a browsing request receiving unit, a browsing data request transmitting unit, a browsing data receiving unit, a browsing information distributing unit, a distributable information history screen data distributing unit, a download request receiving unit, and download data. The request sending unit, the download data receiving unit, and the download past public information distribution unit are configured.

In the present embodiment, the DVP server computer 4, the WWW server computer 5, and the CSI server computer 12 are configured as different computers. , A DVP server and a WWW server may be stored.

The member 2 has a client computer 9
(9a, 9b) are installed. The client computer 9 (9a, 9b) is a computer of the member 2 for using the stock exchange WAN system 1. The hardware configuration of the client computer 9 is the DVP
Since the hardware configuration is the same as that of the server computer 4,
Description is omitted.

The client computer 9b receives, from the WWW server computer 5, distributable information indicating that the public information including the settlement information and the business message can be distributed to the storage device, for example, the HDD, and displays it on the screen. A broadcast notification program 11c, a WWW browser 11b for displaying public information that can be distributed on a screen,
And a payment information data file 10 for storing the received public information. Also, another client computer 9a has a broadcast notification API (Application P) that can execute both the process performed by the broadcast notification program 11c and the process performed by the WWW browser 11b.
(Program Interface) 11a is stored.

[0161] The WWW browser 11b is provided with a download request unit, a download unit, a browse request unit, a browse information reception and display unit, a distributable information history screen data reception unit, a distributable information history screen display unit, a past public information download request unit, a past It constitutes public information download means. The broadcast notification program 11c includes a distributable information receiving unit, a distributable information list screen display unit, a download request unit, a download unit, a browsing request unit, a new distributable information list screen display unit, a new public information download request unit, and a new release. It constitutes information download means.

The broadcast notification API 11a is provided with distributable information receiving means, distributable information list screen display means, download request means, download means, browsing request means, browse information receiving and displaying means, new distributable information list screen displaying means, new It comprises public information download request means, new public information download means, distributable information history screen data receiving means, distributable information history screen display means, past public information download request means, and past public information download means.

As shown in FIG. 47, the client computer 9 is connected to its own server computer 42 to which the terminal computer 45 is connected so that the terminal computer 45 can use the program stored in the client computer 9. It may be configured. Further, on the member 2 side, the client computer 9 and the terminal computer 45 may be connected via an in-house LAN.

Public information such as business messages and settlement information can be viewed and downloaded from the DVP server computer 4 and the WWW server computer 5 from the client computer 9. The member 2 uses the business message and the settlement information data obtained by downloading from the DVP server computer 4 to analyze information using a spreadsheet program and to make use of information such as creation of materials using a word processing function. It is possible.

The relationship among the DVP server computer 4, the CSI server computer 12, and the client computer 9 of the member 2 for controlling the settlement information system according to the present embodiment will be described with reference to FIG. CSI
The server computer 12 is a computer that creates payment information, which is one of the public information, and manages the processing status of the stock exchange WAN system 1 and the DVP payment system (not shown) controlled by the DVP server computer 4. D
Data cooperation with the VP settlement system and data cooperation with the DVP server computer 4 are performed.

The DVP server computer 4 is a computer for controlling the stock exchange WAN system 1 including the settlement information system. For each public information, the distribution / distribution information to be transmitted to the client computer 9 and the creation / production of download information, etc. Perform storage. The DVP server computer 4 performs data cooperation with the CSI server computer 12. Further, it receives public information from the CSI server computer 12 and accumulates data to be provided to the client computer 9 side. Client computer 9
The data to be provided to the side is a business message, the settlement information created by the CSI server computer 12, and data for downloading these business messages and the payment information.

The DVP server computer 4 creates and transmits the deliverable information to be provided to the client computer 9 of the member 2 using the stored business message and data of the settlement information. The distributable information is distributable information indicating that the public information created by the CSI server computer 12 can be distributed. DV
The P server computer 4 transmits the transmitted deliverable information,
The member 2 confirms the reception.

[0168] The member 2 in which the client computer 9 is installed is a subject who utilizes the knowledge information provided by the DVP server computer 4. When the deliverable information from the DVP server computer 4 is transmitted by the notification process by the broadcast notification system included in the payment information system, the client computer 9 of the member 2 transmits the broadcast notification program 11c stored in the client computer 9. To receive. At this time, the broadcast notification program 11c
A acknowledgment to the effect that the distributable information has been received is transmitted to the DVP server computer 4.

When the user of the member 2 confirms the contents of the distributable information on the screen and determines that the public information indicated by the title in the distributable information is the information that needs to be downloaded, the client computer 9 And DVP
A process of downloading information from the server computer 4 is performed.

The DVP server computer 4 stores the distributable information provided to the member 2 side and the public information corresponding to this distributable information,
When the download request is issued from the, the data of the public information is transmitted. Since the data transmission processing is performed from the DVP server computer 4 by the download processing, the client computer 9 extracts the information. By extracting this information, the information can be used. afterwards,
In order to manage the reception status on the DVP server computer 4 side, the broadcast notification program 11c transmits a data reception confirmation notification to the DVP server computer 4. DV
The P server computer 4 receives the data reception confirmation notification and manages the reception status.

Next, an outline of the processing of the payment information system of the present embodiment will be described with reference to FIG. The payment information system includes a client computer 9b having a storage device storing a WWW browser 11b and a broadcast notification program 11c, a WWW server computer 5, and a DVP.
Server computer 4, CSI server computer 12
Has been built between.

[0172] The WWW server computer 5 stores a content generation program 34 for creating content to be transmitted to the client computer 9b. The processing of the payment information system is controlled by the DVP server computer 4. In the processing of the payment information system, first, data setup processing for setting up the DVP server computer 4 is performed on the payment information data registered in the payment information file 13 of the CSI server computer 12 and the business message separately registered (processing 31). ).

Next, a broadcast notification process is performed to transmit to the client computer 9b the distributable information indicating that the public information, which is the settlement information or the business message, can be distributed (process 32). This broadcast notification processing is performed on the broadcast notification program 11c.

Thereafter, upon receiving a download request signal for specifying downloadable information and requesting a download from the broadcast notification program 11c of the client computer 9b, the DVP server computer 4 makes the disclosure corresponding to the specified broadcastable information possible. The information download data is transmitted, and a download process is performed (process 33). The specification of the deliverable information in the client computer 9b is as follows.
This is performed by specifying from the list of downloadable information displayed on the screen of the client computer 9b.

Since only the new deliverable information for which a predetermined period has not elapsed since the preparation for distribution has been displayed is displayed on the screen of the broadcast notification program 11c, the broadcast notification program 11c starts the distribution. Only public information for which a predetermined period has not elapsed after the preparation for distribution of possible information has been completed can be downloaded. The public information for which a predetermined period has passed after the preparation for distribution of the distributable information has been completed is separately stored in the WWW browser 11b.
Can be downloaded using.

In this embodiment, the predetermined period is
It is set to one day. The reason why the predetermined period is set to one day is that it is usually late at night when the payment information is ready for distribution.
Since the settlement information is used on the side from around 9 o'clock in the morning on the next day, it is considered appropriate to display the distributable information about one day after the preparation for distributing the distributable information is completed. That is because The predetermined period is not limited to one day, and may be set to several hours or several days. For example, when the number of pieces of distributable information is large, the predetermined period may be shortened.

The transmission of the download request signal can also be performed from the WWW browser 11b of the client computer 9b. That is, the WWW browser 11
In b, a title list screen of public information can be displayed, and from this screen, the public information can be specified and a download request signal can be transmitted. This WWW browser 11
From the title list screen of the settlement information b, download of the public information after a predetermined period has elapsed after the distribution preparation of the distributable information is completed is possible. This predetermined period is set to one day.

As described above, only public information that has passed a predetermined period after the preparation for distribution of the distributable information has been completed can be downloaded from the WWW browser 11b.
Payment information for which a predetermined period has not elapsed after the delivery preparation of the deliverable information has been completed is made downloadable only from the broadcast notification program 11c, and monitoring of information acquisition on the member 2 side is strictly performed. .

When receiving the download request signal specifying the public information from the WWW browser 11b, the DVP server computer 4 transmits the specified public information to the WWW browser 11b and performs a download process (process 33).

FIG. 19 is a diagram showing an image of business data cooperation in entry processing. In the present embodiment, the member 2
The settlement information of the stock exchange WAN system 1 is used (entry or the like). The DVP server computer 4 of the stock exchange WAN system 1 includes a CSI server computer 12
And process coordination.

FIG. 20 is a diagram showing a user operation of the entry processing. The client computer 9 of the member 2 communicates with the stock exchange WAN system 1 for user authentication processing, credit (access control) processing, entry screen notification reception processing, entry request processing, entry result notification reception processing, when an error occurs. Perform the entry result confirmation processing of

Here, an outline of the entry process will be described. In the entry process, the member / special visitor 2
Data entry is performed in connection with the P settlement system. Processing such as correction to payment data and content information provided by the payment information system and registration of information in the DVP payment system is realized. In the entry process, it is necessary to guarantee the transaction of the process.

The entry processing requirement will be described. Data entry is assured (transaction is guaranteed by application conversation), processing is assured at the time of load concentration (processing is assured at the time of processing load concentration by reliable and high-performance functions), and recovery processing is assured It is necessary to perform (processing confirmation at the time of error by managing the processing status).

For reliable operation (high reliability), system authentication (authentication check at the time of system entry), access management of system resources (access check at the time of resource use), processing status management (processing status) Recovery measures by management) are required.

In order to facilitate operation, it is not necessary to distribute resources to members. It takes a variety of cooperative forms, supports a wide variety of partner system forms, and can support multi-user systems.

Next, details of the business processing of DVP settlement will be described. In the DVP settlement of this embodiment, the transfer of securities by the member 2 is performed by an account transfer at the custody transfer organization 15, and the transfer of funds by the member 2 is performed by an account transfer at a fund clearing bank.

[0187] The transaction to be subjected to the DVP settlement is the next transaction related to the stock handled by the custody transfer organization 15 among the transactions on the stock exchange 14. In other words, domestic stock certificates (including preferred equity securities), ordinary transactions (including the buying and selling of target stocks that are concluded by exercising the rights of stock option transactions), off-auction distribution, single-stock transactions (settlement dates are the same as ordinary transactions) Transactions only), basket transactions (limited to transactions with the same settlement date as ordinary transactions) and trading of closing prices, trading of units of Nikkei 300 index-linked exchange-traded unit trusts, trading of convertible bonds These are trading of ordinary transactions, single-brand transactions (limited to transactions with the same settlement date as ordinary transactions), closing price transactions and off-auction basket pairing transactions (limited to transactions with the same settlement date as ordinary transactions). In addition, “trading” includes trading and lending transactions for error correction, etc. based on business rules. In the present embodiment, the settlement of the day settlement transaction and the issue date settlement transaction are not subject to DVP settlement. Hereinafter, settlement of transactions other than transactions subject to DVP settlement is referred to as “Non
-DVP settlement ".

The handling of securities / fund settlement will be described. First, securities settlement will be described. The transfer of securities by the member 2 is performed by account transfer at the custody transfer organization 15. Here, the member 2 includes a special participant in a stock certificate option transaction. It should be noted that among the non-regular members in the regular futures and options markets,
Are qualified to trade on what they deem appropriate, and those who have obtained this qualification are called special participants.

First, delivery to the stock exchange 14 by the delivery member is performed. Watakata members are the securities exchanges 14
Delivery by the securities settlement deadline. Here, the security settlement time limit is 13:00. 1 for each settlement date
The unfinished transfer from the member account at 3:00 to the stock exchange account at 3:00 is treated as a failure.

Next, delivery to the receiving member by the stock exchange 14 is performed. In the delivery to the receiving member by the stock exchange 14, the flow shown in the flowchart of FIG.
Delivery based on net debit calculation. First, in step S400-1, receivable securities value is calculated by net debit calculation.

The delivery of securities to the receiving member by the stock exchange 14 is performed for the securities that match the value of the collateral deposited on the previous day, the scheduled payment for DVP and the delivered securities, etc., deposited from the receiving member. This is done according to the receiving member ranking by brand and the receiving brand ranking by member. Here, DVP
The scheduled receipt / payment refers to the scheduled receipt / payment related to the DVP settlement that does not take into account the status of the failure on the settlement date.
Such calculation of the receivable value of the receiving member is called net debit calculation.

The value of the receivable securities by net debit calculation is as follows: Receivable securities value = deposit amount of collateral deposited on the previous day + deposit value of expected deposits received at DVP + value of securities delivered + transfer amount of additional payment-received securities Value ± value washing amount ... Calculated by the formula (Formula 1).

In this formula 1, the substitute price is used for the substitute securities as the deposit amount of the collateral deposited on the previous day. Margin deposits in margin transactions and margin deposits and transaction margins in futures and options transactions can be substituted by non-cash securities, public and corporate bonds, and other securities specified by the stock exchange. That.

In addition, the value of the delivered securities in the above formula 1 is represented by the value of the delivered securities = the quantity of securities × the settlement price (Formula 2). In Formula 2, the settlement price refers to the final price on the day before the settlement, and includes the final quote price indicated by Article 10 of the Tokyo Stock Exchange “Rules on Quotes”. However, when there is no final price on the day before the settlement, it refers to the reference price on the day before the settlement. The mark-to-market margin in Formula 1 refers to the difference between the contracted price and the settlement price pertaining to the sale and the difference between the previous day's settlement price and the current day's settlement price pertaining to the delivery carried over by fail.

Next, in step S400-2, a delivery brand or the like is determined based on the received brand ranking by member. In this step, the delivery issue corresponding to the receivable security value of the receiving member calculated in step S400-1 and the quantity thereof are determined in accordance with the order of received issue by member described later.

Next, in step S400-3, it is determined whether or not delivery based on the receiving member rank by brand is possible. In this step, the stock exchange 14 determines whether or not the issue determined in step S400-2 and the quantity thereof can be delivered to the receiving member in accordance with the issue-specific receiving member ranking described later.

When delivery by rank of receiving member by brand is not possible (step S400-3: NO), that is, the cumulative transferred quantity of the brand from the delivery member to the stock exchange 14 is When the transfer request amount to the other receiving member, which has priority over the receiving member, is smaller than the total, the flow returns to step S400-1 again, and the step is executed for the next issue in the receiving issue ranking by member of the receiving member. In S400-1, the receivable security value is calculated by net debit calculation. That is, in step S400-3, steps S400-1 to S400-1 to S2 are executed until the receiving member rank of the receiving member becomes lower than the next-ranked brand in the receiving brand ranking by member until delivery by the brand-specific receiving member rank becomes possible.
The series of processing of 400-3 is repeated.

When the delivery is possible according to the receiving member rank by brand (step S400-3: YES), that is, the cumulative number of transferred goods from the delivery member to the stock exchange 14 for the relevant brand is determined for the relevant brand. If the transfer request amount to the other receiving member, which is prioritized to the receiving member, is larger than the total amount, in step S400-4, in order to transfer the account from the stock exchange 14 of the required number of the issue to the receiving member in step S400-4. Perform the procedure of

Next, in step S400-5, it is determined whether or not the securities settlement time limit (13:00) for the day has come. If the security settlement time has not come (step S400-
5: NO), returning to step S400-1 again to calculate the receivable value of the next issue by net debit calculation. That is, steps S400-1 to S400-5 are sequentially repeated for the issues until the securities settlement time is reached.

[0200] If the securities settlement time limit (13:00) has been reached (step S400-5: YES), step S400 is performed.
At -7, the securities are settled, and it is determined whether or not each account can be debited. That is, 1 which is an example of the securities settlement time limit
At 3:00, the processing of steps S400-1 to S400-4 is temporarily terminated, and step YS400 is performed.
Confirmation of account transfer at -7 and, if necessary, step S40
The determination of 0-8 fail is performed.

In the case where the account transfer cannot be performed (step S400)
-8: YES), the failure is determined. That is,
Failees are allocated in order from the receiving member at the lowest rank of the receiving member rank by brand relating to the failing brand for which the account transfer could not be performed until the number of failed members is reached. After that, the process ends. If the account transfer was successful (step S400-
8: NO), the process ends.

A method for determining the order of receipt of securities will be described. In the order of receipt of the securities, step S
Rank of received stock by member and step S used in 400-2
The receiving member ranking by brand used in 400-3 is included. The method of determining the ranking of received stocks by member is as follows. That is, the ranking of the received issues by member is determined in priority from the one with a small settlement price (settlement quantity × clearing price) regardless of the type of securities. In the ranking of the received brands by member, the received quantity for which buy-in is requested and the other received quantity are calculated as different ranks.

The receiving member ranking by brand is determined according to the following order. The buy-in billing volume is the “top priority group” over all others. Prioritize only the quantity for which the buy-in was requested, of the quantity received on the day by the receiving member. In the order of the buy-in billing quantity of the highest priority group, the buy-in billing date is prioritized in ascending order (in ascending order) for each part. If the buy-in request dates are the same, priority is first given to the longest fail period (failure with the oldest occurrence date: ascending order), and if the fail period is the same, determination is made by lottery.

The priority group next to the highest priority group is a failed member. The failed member is a “priority group” which has priority over the other members 2. If any part of the received quantity on the day is received for the fail, the priority will be given to all the received quantity on the same day.

[0205] The order of the failed members of the priority group is as follows.
Ascending order) Priority is given to member order. If the failed period is the same, it is determined by lottery. The subordinate group of the lowest rank next to the priority group is the member 2 other than the failee. The order of members of the subordinate group other than the failed member is determined by lottery.

[0206] The point in time at which the securities exchange 14 transfers the securities to the receiving member will be described. Delivery to the receiving member is performed at the time of the next transfer in the storage transfer organization 15. (A) 9:00 (Night batch processing on the day before settlement) (b) 9:30, 10:30, 11:30, 12:30 (c) Immediately after 13:00 (d) Immediately after 14:15 At the time of transfer Is not limited to these points, and may be changed as appropriate.

The transfer of securities can also be partially transferred. In the transfer of funds from the member to the stock exchange 14, even if the transfer request amount is less than the required amount, if there is a transferable balance in the account of the transfer member, the account is transferred to the stock exchange 14 each time. And perform a partial transfer. This point is based on the conventional D.A. B. It is the same as in the system.

At the time of account transfer from the stock exchange 14 to the receiving member, even if the transferable amount is less than the transfer request amount, the receiving member has a receivable balance in the stock exchange account. Will transfer the account to the receiving member and make a partial transfer each time. This point is described in D.S. B. Account transfer is executed when the transfer request amount is reached, except when B. Different from the system.

[0209] Next, fund settlement will be described. The transfer (receipt / payment) of the funds by the member 2 is performed by fund transfer at a fund clearing bank (clearing bank or central bank). Here, the payment price means net money which is obtained by netting a settlement price (a monetary amount obtained by multiplying the amount of securities to be delivered by the settlement price) and a mark-to-market margin.

[0210] In the fund settlement period, payment by the paying member to the stock exchange 14 is until 14:15 on the settlement date, and receipt by the receiving member from the stock exchange 14 is 14:45.

[0211] Deposit of the DVP scheduled payment will be described. This scheduled payment for DVP is essential collateral. The member 2 whose amount obtained by calculating the difference between the scheduled payment amount and the mark-to-market difference is overpaid, the member 2 who paid the overpaid amount as the DVP scheduled receipt and payment amount by 13:00. Deposit with the stock exchange 14. The settlement price at this point is the estimated amount because the transfer of funds related to the fail that occurs on the day is not taken into account. D deposited by member 2
The scheduled VP payment is used for payment related to fund settlement.

[0212] The transfer of funds related to a failure will be described. Each member 2 calculates the difference between the amount paid for the fail and the amount received for the failed in the delivery of different brands, and transfers the required amount if the result is overpaid, and receives the amount if the result is overpaid. .

The failing member and the failed member send and receive the amount corresponding to the failed delivery in accordance with the categories (a) to (c) or the categories (a) and (b).
Here, the category (a) is when the fail member is the payment method of the payment (scheduled amount), and the category (b) is the case where the fail member is the payment method of the payment (scheduled amount). The category (c) refers to a case where the fail member received the payment (scheduled amount) but received the payment (final amount) due to the occurrence of the failure.

[0214] First, additional payment by a fail member will be described. In addition, each member 2 calculates the difference between the amount paid for the fail and the amount received for the failed in the delivery of different brands, and transfers the required amount if the result is overpaid, To receive. Classification (a) where the fail member paid the payment (scheduled amount)
In the case of (1), the payment amount of the payment received and paid will exceed the amount of the DVP scheduled payment received in the payment settlement time limit (13:00), so the additional payment of the shortfall will be made by the fund payment time limit (14:15). I do. The underpaid amount is an amount equivalent to the payment amount for the failed delivery.

In the case of the category (b) in which the fail member received the payment (scheduled amount), the fund receiving time (14: 4)
In 5), a payment (finalized amount) is received by subtracting an amount equivalent to the settlement price for the fail. In the case of category (c), in which the fail member received the payment (scheduled amount) but paid the payment (final amount) due to the occurrence of the failure, the relevant member must be paid by the fund payment time limit (14:15). Make an additional payment for the payment amount.

Next, regarding the receipt of funds by the failed member, the category (a) in which the payment (scheduled amount) was paid.
In the case of, description will be made separately for the case of category (b), which is the method of receiving the payment (scheduled amount). In addition, with each member 2,
In the delivery of different brands, the amount paid for the fail and the amount received for the failed are calculated, and if the result is overpaid, the required amount is transferred, and if the result is overdelivered, the received amount is received.

In the case of the category (a) in which the paid-in payment (scheduled amount) was paid, in the settlement securities settlement time limit (13:00), the failed member pays the DVP scheduled paid-in payment amount. Because it will be less than the
4:45), the collateral surplus is received. In the case of the category (b) in which the received payment (scheduled amount) is received, the settlement price corresponding to the fail is received together with the received payment (scheduled amount) at the fund receiving time (14:45).

Next, the trade day (T day) and the day after the trade day (T +
1 day), the day before settlement (T + 2 days), the day of settlement (T + 3 days)
The day-to-day operations related to securities and fund settlement will be explained. In addition, the information exchange performed from T day to T + 3 day,
This is performed by the stock exchange WAN system 1. The time of data transmission may be slightly shifted. Trade day (T
As a clerical work on the day 2), the member 2 has a contract day (T day) 23:
00, data for trade matching from the stock exchange 14, that is, “Domestic stock trading schedule”, “Bond trading trading schedule”,
It becomes possible to receive the data of "Summary A (for collation)" and "Stock Option Trading Exercise Declaration / Allocation Statement".

On the next day (T + 1 day) of the contract day, the reception of the trade verification data, the reception of the securities settlement data, and the reception of the funds settlement data are performed. The member 2 receives the trade matching data from the stock exchange 14 at 21:00 on the day after the trade day (T + 1 day), that is, the trade matching data from the stock exchange 14, that is, “internal stock trading statement (correction)”, “bond trading”. It is possible to receive the “sales statement (correction)” and “summary B (corrected)”.

[0220] As the receipt of the securities settlement data, the member 2 makes a request for 21:00 on the day following the contract day (T + 1 day),
Of “scheduled settlement quantity by brand” from Here, since it is before the netting with the settlement related to the failure that occurs on the next day, it is the estimated quantity. As the receipt of the fund settlement data, the member 2 decides at 21:00 on the day following the contract day (T + 1 day).
0, it is possible to receive the “summary settlement table (contract price)” from the stock exchange 14. The DVP of the present embodiment
For settlement, a third day correction shall not be permitted.

On the day before the settlement (T + 2 day), deposit / return of the collateral deposited on the previous day, receipt of securities settlement data, and receipt of funds settlement data are performed. As a deposit and return of the previous day's security deposit, the member 2 performs the procedure of depositing or returning the previous day's deposit security deposit between 9:00 and 12:00 on the day before the settlement (T + 2 day) as necessary. The security deposit on the previous day is valid for settlement from the day after the deposit date to the date of return.

As reception of the securities settlement data, the member 2 makes a request for 17:00 to 10:00 on the day before the settlement (T + 2 day),
To receive the “Settled Quantity by Brand”. The settlement settlement amount for each issue indicates the settlement settlement amount as a result of netting the settlement (correction processing completed) relating to the T-day contract and the settlement relating to the fail that occurred on T + 2.

As the receipt of the fund settlement data, the member 2 makes a request for 17:00 on the day before the settlement (T + 2 day),
Receives the “summary settlement table (settlement price / clearance margin)” and “total payment amount calculation table (planned / flash report)”. This information does not include fund transfer information relating to futures transactions. In addition, the member 2 has 2 days before the settlement (T + 2 days).
From 2:00, it is possible to receive the “total payment calculation table (planned amount)” from the stock exchange 14. The “total payment calculation table (planned amount)” includes fund transfer information relating to futures transactions and the like.

On the day of settlement (T + 3 day), transfer of securities, transfer of funds, receipt of securities, fail, notification to failed members, receipt of fund settlement information and fulfillment of additional payment, payment of payment Receipt and receipt of the price receipt notification are performed. As a transfer of securities, the transfer member generates the number of securities to be transferred in his / her account by 13:00 on the day of settlement (T + 3).

[0225] Note that if the cancellation of the transfer temporary suspension measure is declared just before 13:00, or if the transfer deposit is made, the transfer may not be completed (fail). If the temporary stop of the transfer is declared to the custody transfer organization 15 and the release time of the suspension measure is set to 13:00 or later, the release specification becomes an error.

As a transfer of funds, the paying member carries out paperwork related to the payment of the funds according to the classification of the clearing bank user and the central bank (current account) user. Here, the paying member refers to the member 2 whose payment amount is described in the “total payment amount” column of the “total payment amount calculation table (planned amount)”.
The payment amount (hereinafter, referred to as “total payment amount”) and the received amount (hereinafter, referred to as “total received amount”) described in the “total received payment amount” column of the “total received payment amount calculation table (planned amount)”. They are exchanged via the stock exchange 14 without calculating the difference. D
The settlement funds for VP settlement and Non-DVP settlement do not perform netting.

Member 2 whose division is a clearing bank user is
By 13:00 on the day of settlement (T + 3 day), the funds allowance for the total payment amount is made to the fund settlement account. The funds are transferred by the clearing bank from the fund settlement account of the member 2 to the fund settlement account of the stock exchange 14 by 13:00 on the day of settlement (T + 3) (reverse lookup processing). The transfer of the total payment amount by the clearing bank is completed, and the stock exchange 14 confirms the status, whereby the amount related to the DVP settlement among the payment amounts is reflected in the net debit calculation. The member 2 whose classification is a member of the central bank (current account) uses the central bank network system,
By 3:00, the total payment is transferred to the fund settlement account of the stock exchange 14.

At the time of each transfer, the receiving member receives the securities at any time by the account transfer based on the net debit calculation.

As notification to the fail / failed member, the delivery securities settlement time limit (1 on the day of settlement (T + 3 days)
At 3:00), after the failure of the day (failed) is determined, each member 2 relating to the failure (failed) receives a “fail” from the stock exchange 14 at 〜13: 30 on the day of settlement (T + 3). Information notification (after delivery) "is received.

The member 2 performs the following tasks a to c in order to receive the fund settlement information and fulfill the additional payment. a Member 2
Receives the “total payment amount calculation table (fixed amount)” and the “additional payment notice” from the stock exchange 14 by 13:30 on the day of settlement (T + 3 day). The “additional payment notice” is transmitted to the member 2 who makes the additional payment. b. The member 2 who makes the additional payment transfers the amount to the fund settlement account of the stock exchange 14 as an additional payment by 14:15 on the day of settlement (T + 3 day). Members of the Central Bank Current Account will make transfers using the Central Bank Network System.

C Among the members who use the clearing bank, the member 2 who has executed the additional payment in b above prints out the “additional payment notice” with the client computer 9,
Fill in the necessary information in the "Additional Payment Transfer Notice" column, seal it, and copy a document certifying that the transfer has been made
And send it to the stock exchange 14 by facsimile immediately (by 14:15 on the day of settlement (T + 3)). Here, the "copy of the document proving that the transfer has been made" is a "transfer receipt" issued by a bank, or a transfer execution confirmation document output from the firm banking system. Farm banking (FB; on li)
ne business banking service
“ce)” refers to a mechanism for connecting a customer such as a company to a financial institution via a communication line and performing various financial operations such as settlement.

The member who uses the clearing bank transmits an “additional payment execution notice” and a “copy of a document certifying that the transfer has been made” to the stock exchange 14 so that the amount of the additional payment is Reflected in calculations. For the member using the central bank current account, the additional amount is reflected in the net debit calculation by transferring the additional payment to the fund settlement account of the stock exchange 14 using the central bank network system. It is not necessary for the central bank current account member to send the "Notice of Execution of Additional Payment Transfer" and "Copy of Document Proving that Transfer was Made".

As the receipt of the payment, the receiving member receives the amount at 14:45 on the day of settlement (T + 3). Here, the “receipt member” refers to the member 2 whose receipt amount is indicated in the “final settlement time total receipt fee” column of the “total receipt and payment price calculation table (final amount)”. As a receipt of the payment receipt notice, the paying member among the clearing bank user members receives a “price receipt notice” from the stock exchange 14 after 14:45 on the day of settlement (T + 3). The term “payment member” here means “total payment price” in the “total payment price calculation table (fixed amount)”.
Member 2 has the payment amount described in the column.

Next, the handling of the collateral deposited on the previous day will be described. A description will be given of the collateral deposited on the previous day (voluntary collateral). The member 2 deposits the security on the stock exchange 14 the day before the settlement date, and completes the settlement of the received securities corresponding to the amount of the deposited collateral on the settlement date (time limit for fund payment).
It will be possible to receive it before.

The range of eligible collateral shall be based on the trading margin (cash and substitute securities) for futures / options transactions. In addition, the processing of claiming the coupon of the substitute securities is similar to the processing of the transaction margin.

The substitute prices of the substitute securities are as follows. The substitute price of the securities deposited as collateral on the previous day is the substitute price (rate) based on the market margin two days before the settlement date when the substitute securities are effective as collateral on the previous day and equivalent to the trading margin. Multiplied by. The substitute price at the time of return shall be the amount obtained by multiplying the market price two days before the return date by the substitute cost (rate) according to the transaction margin.

Next, an outline of the procedure for depositing / returning the collateral deposited on the previous day will be described. Application for deposit / return is made as follows. When the member 2 intends to deposit and return the collateral deposited on the previous day, the member 2 makes a predetermined application to the stock exchange 14 by 9:00 to noon (11:00 on a half-day holiday) in principle. . Regarding the transmission of billing slips that can be used for trading margin, etc., it is also possible to use it for the previous day's security deposit. It should be noted that the previous day's deposit will only be processed on the same day.

The time limit for deposit / return application for transaction margins (excluding emergency transaction margins) is also basically 9:
00 to noon (11:00 on a half-holiday). Here, the emergency trading margin is a margin deposited by a securities company as a regular member when the market price fluctuates abnormally greatly in the morning session and the stock exchange deems it particularly necessary.

The execution of the return is performed as follows. As for the collateral deposited on the previous day, which is equivalent to the amount of the securities received and the price margin, the refund is executed after the fund settlement time limit (14:15) on the refund application date. By performing the transfer processing for the collateral deposited on the previous day (surplus), it is possible to apply the margin to the trading margin on the day.

[0240] The amount of the received securities plus the mark-to-market margin is the amount of the mark-to-market margin subtracted from the received securities if the mark-to-market margin is received, and added if the mark-to-pay is paid. It will be the amount of money.

With respect to the surplus of the previous day's collateral (hereinafter referred to as “surplus”) exceeding the amount of the securities received plus the mark-to-market margin, it will be returned or transferred to transaction margin at the time of accepting the return application. Can be. This transfer procedure conforms to the procedure for trading margin. The combination of the transfer of the previous day's collateral with the trading margin can be changed from 'the previous day's collateral' to 'own' or 'substitution', or from 'substitution' or 'self' to 'the previous day's margin. Security Deposit ". Regarding the return of the surplus cash, the cash settlement payment time limit (14: 1
5) The return is made.

Next, transmission of the security deposit receipt / payment status table etc. the day before will be described. The collateral deposit deposit member on the previous day receives the “credit money, trading / trade margin, and collateral deposit / payment status table” from the stock exchange 14 to 15:00, and
After 2:30, it becomes possible to receive the “previous day deposit balance table”.

Next, regarding the affairs relating to the deposit / return of the collateral deposited on the previous day, the deposit / return procedure by cash, the deposit / return procedure by cash (this ticket), the deposit / return procedure by the stock handled by the custodian (the same day) Transfer request only), transfer / return procedure using transfer government bonds, transfer / return procedure using registered government bonds,
This section describes the items to be sent and returned by the United States Treasury.

First, the cash deposit / return procedure will be described. The member 2 who deposits in cash uses the current “margin selection bank”. In addition, the stock exchange 14
Will be returned by transfer to the current “Margin Return Account”.

As a deposit, the member 2 treats the day before the security deposit deposit procedure on the day before as a deposit, and uses the same day as the margin only account of the stock exchange 14 provided at the margin selection bank (the security deposit on the previous day is also included). Transfer), "copy of documents proving transfer has been made", "previous day deposit (cash) deposit notice" (hereinafter referred to as "deposit notice") and "previous day deposit collateral" A cash deposit / withdrawal / transfer slip (hereinafter referred to as a "cash slip") is submitted to the stock exchange 14 by noon on the deposit date. "Notice of security deposit (cash) received the day before" is used by adding a type to the existing "notice of deposit for member, trading margin, and transaction margin (cash)". In the following, unless otherwise specified, “noon” means 11:
00.

As a return, the member 2 fills in the required items on the "cash slip" and submits it to the stock exchange 14 by noon on the return date. As a transfer, the member 2 fills in "cash slip" and submits it to the stock exchange 14 by noon on the transfer date.

Next, a description will be given of a procedure for inserting / returning the actual (real) ticket. Member 2 fills in the necessary information in the “Shipment / Return slip for the previous day's security deposit” (hereinafter referred to as “Substitute cash voucher”) and then submits a substitute cash in / slip back slip voucher (hereinafter “Submit”). Bag)).
It is submitted to the stock exchange 14 by noon on the date of delivery together with the actual product. After the paperwork of the stock exchange 14, the "substitute cash slip" and "submission bag" submitted at the time of insertion are received. The “substitute cash slip” is also used at the time of return.

As a return, the member 2 fills out the necessary information in the “substitute cash slip” used at the time of insertion, delivers it to the “submission bag”, and submits it to the stock exchange 14 by noon on the return date. After the paperwork of the stock exchange 14 (return for the collateral equivalent to the receivable securities amount is 14:15 or later), the actual returned goods and the “submission bag” are received. If you want to transfer the actual item (genuine ticket), the procedures for insertion and return must be performed at the same time.

[0249] Next, a description will be given of a procedure for inserting / returning by a brand handled by a storage transfer institution (only a transfer request on the day). In the case of insertion by the custody transfer institution handling member, the member 2 makes a transfer request to the trading margin account of the stock exchange 14 provided in the custody transfer institution 15 (also used for the previous day's collateral paid), Fill out the necessary information in the transfer stock (convertible bond) insertion / return slip (hereinafter referred to as “storage transfer slip”) and submit it to the stock exchange 14 by noon.

[0250] In the return by the stock handled by the custody transfer institution, the member 2 fills in the "custody transfer slip" and submits it to the stock exchange 14 by noon on the return date. In the transfer by the stock handled by the custody transfer organization, the member 2 receives the “custody transfer slip”
Fill out the required items on the Stock Exchange 1 by noon on the day of transfer.
Submit to 4.

[0251] Procedures for the transfer / return using the JGB will be described. In the case of the payment by the JGB, the Member 2 fills in the necessary information in the “Job for the previous day, the JGB payment / return / transfer slip” (hereinafter referred to as “the JGB voucher”), By noon on the stock exchange 14. The transfer order in the central bank network system is performed by the stock exchange 14.

[0252] In the return by the determined government bond, the member 2 fills in the necessary items in the "determined government bond slip" and submits it to the stock exchange 14 by noon on the return date. In the transfer by JGB,
The member 2 fills in the necessary items on the “Debt JGB Slip” and submits it to the stock exchange 14 by noon on the transfer day.

[0253] Procedures for insertion / return using registered government bonds will be described. In the insertion, Member 2 is required to submit a “Transaction Margin Registration JGB Insertion / Return Slip” (hereinafter referred to as a “registered JGB Slip”) and a “Registered JGB Supplementary Registration Notice” or “Registered JGB Supplementary Registration Notification (Transformation) And fill in the "Submission Bag" and submit it to the stock exchange 14 by noon on the date of delivery. After the paperwork of the stock exchange 14, the “registered government bond slip” and “submission bag” submitted at the time of insertion are received. The stock exchange 14 issues an instruction for appendix registration in the central bank network system.

In the return, the member 2 fills in the necessary information on the "registered government bond slip" returned at the time of insertion and fills in the necessary information in the "registered government bond registration note" or "registered government bond note". The registration notice (transformation) "is delivered to the" submission bag "and submitted to the stock exchange 14 by noon on the return date.

When the member 2 changes the surplus (changes in the pledge right or the pledge right), the member 2
In order to take the form of refund / delivery, a “registered government bond voucher” for return, a “registered government bond voucher” and a “registered government bond additional registration notification” or “registered government bond additional registration notification (transformation)” Is delivered to the “submission bag” and submitted to the stock exchange 14 by noon on the date of the matter change.

A description will now be given of the procedures for the transfer and return by the United States Treasury. Member 2 fills out the "US Treasury Transfer Instructions"
By submitting to the stock exchange 14 by 6:00, the member 2 is instructed to insert the relevant securities into a stock exchange margin account designated by a local storage organization designated by the member 2.

The stock exchange 14 completes the transfer when it receives the transfer completion notice from the bank designated by the local stock exchange, and increases the deposit balance. If the stock exchange 14 does not receive a transfer completion notification from the local stock exchange designated bank, it is considered that no deposit has been made regardless of the reason. Upon receiving notification from the stock exchange 14,
If necessary, make a deposit with cash or other substitute securities.

In return, Member 2 fills out the "US Treasury Transfer Instructions" and submits it to the stock exchange 14 by noon on the return date, and sends it to the local depository designated by Member 2 Instructs to accept the security from the stock exchange margin account. The stock exchange 14 reduces the balance in custody at the time the “US Treasury Bond Transfer Instruction” is submitted.
If the stock exchange 14 receives a non-return notification from the local stock exchange designated bank on the day following the return date, the return is canceled at that time and the balance in the deposit is increased.

Next, handling of fail and buy-in will be described. First, with regard to a fail, a description will be given of the decision of a fail, the decision of a member to be failed, the re-netting of the fail, the request for a buy-in, the cancellation of a fail such as a late damage, and other handling.

The determination of a failure is performed as follows. In other words, when securities are not delivered by the delivery member by the delivery securities settlement time limit (13:00) on the settlement date (when the balance due to transfer from the delivery member account to the stock exchange account has not occurred) ), This is a failure. The transfer of the securities related to the fail and the corresponding settlement price
Roll over the next day.

In the case where the transfer has been declared to be temporarily suspended to the storage and transfer institution 15 and the designated release time of the suspension measure is set to 13:00 or later, the release designation results in an error. In addition, when the transfer deposit is performed immediately before the settlement time of the transfer securities, the transfer deposit may fail depending on the time.

The determination of a failed member is performed as follows. Fail to be failed is allocated in order from the receiving member at the lowest rank of the receiving member rank of each issue relating to the failing issue until the fail quantity is reached. The transfer of the securities related to the failee and the corresponding settlement price will be carried over to the next day.

The settlement of securities and payments carried over by the fail (and the failee) is exchanged after re-netting with the settlement of a sales transaction whose settlement date is the date carried over.

A request for a buy-in is made as follows. The failed member can request the securities exchange 14 to purchase and deliver (buy-in) the securities related to the failed if the failed continues beyond the settlement time limit of the next day. The request for the buy-in is made by inputting necessary items on a dedicated screen displayed on the client computer 9.

In the case where a fail-in member requests for a buy-in, if the fail-related request for the buy-in is not canceled by the fourth business day from the billing date,
The stock exchange 14 executes the buy-in and charges the cost required for the buy-in to the member 2 having the oldest fail position among the members 2 who failed at the time of requesting the buy-in.

The following is a method of giving and receiving a late penalty, a late penalty, a late penalty, a late penalty, etc., a late penalty, and the like. As a damage after the date of occurrence of the failure, the fail member pays the delay damage related to the failed delivery to the stock exchange 14, and the stock exchange 14 pays the damage to the receiving member (failed member). . The amount of the late loss is 4 yen per 100 yen equivalent to the settlement price, the quantity of failure is the fail quantity determined at the time of settlement of the transfer securities (13:00) on the settlement date, and the amount calculated is the clearing price of the fail issue X target quantity x daily steps. Here, the clearing price of the failing brand is the clearing price on the settlement date on which the failure occurred.

As a penalty penalty after the date of the occurrence of the failure + 4 days, the stock exchange 14 will notify the stock exchange 14 if the fail member does not cancel the failure by the 5th business day from the initial settlement date. And collect the late penalty from the member 2 concerned. This late penalty is calculated as follows:
2 yen per yen, the target quantity will be settled after the 5th business day from the date of the initial failure occurrence, and the delivery securities settlement time limit (13:00)
At 0), the unresolved fail and the calculation of the amount are the settlement price of the fail brand × the target quantity × the daily rate.

As a late penalty penalty penalty, the stock exchange 14 sets the following target quantity and amount in the event that the member 2 generates a failure on the day before the base date for vesting rights to the term-end brand, etc. The amount of money calculated from the calculation is collected from the member 2 concerned. However, it shall be possible to settle the fail on the reference date, etc., and for the part where the fail has been resolved by the same settlement, a partial penalty will be reduced.

[0269] The reference date for deciding the right means a reference date for each of the following. In the case of stock certificates (including preferred equity securities), the date on which the standard for notification of ex-dividends, ex-rights, and stockholders handling custody transfer institutions becomes the standard, and in the case of convertible bonds / preferred shares, the standard for conversion conditions change In the case of convertible bonds, this is the date on which the standard for exemption of redemption rights during the period is applicable.

Here, the target quantity is the fail quantity (= initial quantity) that has not been resolved at the calculation reference time of the previous day such as the reference date, etc., and the fail quantity resolved in the settlement on the current day such as the reference date (= reduced quantity). Is reduced.) In addition, the calculation of the amount is as follows: Amount of late penalty, etc. late penalty penalty = A yen-(A yen x reduced quantity ÷
(Initial quantity x 75%). At this time, [the higher of the settlement price for settlement on the previous day, such as the base date of each issue, or the settlement price for settlement on the due date, such as dividend loss] × initial quantity × 0.08% = A yen. The transfer of late damages, etc. will be made for the current month, and will be performed the following month. Specifically, the same method is used as in the transfer of rent related to the current securities delivery slip.

A description will be given of the elimination of the failure. Fail is resolved in the case of delivery settlement, re-netting, and execution of buy-in. The settlement by delivery settlement, that is, the settlement by delivery settlement up to the delivery securities settlement time limit is handled as follows. The failure elimination by the delivery settlement on the settlement date (hereinafter referred to as “S day”) is considered to have been made on S day. However, late damages will be incurred until the S-1 day.

The cancellation by re-netting, that is, the cancellation by re-netting between the settlement in the case where the delivery settlement on the next day is the receiving side and the settlement carried over to the next day by fail is handled as follows. The resolving of the failure in the re-netting (for the S-day settlement) performed on the S-1 day is considered to have been performed on the S day. However,
Late damages will be incurred until the S-1 day.

The cancellation associated with the execution of the buy-in, that is, the cancellation due to the cost paid by executing the buy-in, is considered to have been performed on the day following the execution date. However, late damages, etc. will be incurred until the relevant execution date.

Fail resolution by delivery settlement, re-netting, or execution of buy-in is performed in order from the oldest fail date. This is a so-called “first-in first-out method”.

[0275] Other handling of the fail will be described. Designation of recipients / deliverers for the failure of term-end issues, etc. is performed as follows. For the term-end issue, etc., the settlement date of the delivery securities on the day before the record date, etc. (13:00)
0) If there is a fail that has not been resolved at the time, the stock exchange 14 will receive the same date on the same day in order to adjust and process the dividend and other rights processing associated with the fail between the fail member and the failed member. The association between the member and the transfer member (designation of the receiver and the transfer person) is performed, and each is notified including the quantity. The designation is performed by the stock exchange 14 by transmitting a “receipt / delivery specification sheet relating to settlement of the reference date” to the member 2 at 17:00 on the day before the reference date.

[0276] For the term-end issue, etc., settlement is not performed on the day such as the reference date by so-called "temporary settlement", but settlement for eliminating the failure can be performed.
Settlement for the end of the term, etc., for the settlement of the fail made on the same day as the base date, etc., is based on the receiving / delivery designation made by the stock exchange 14 on the previous day, based on the delivery member and the stock exchange 14, the stock exchange 14 and the receiving member. A settlement method for resolving a failure performed on the day such as a reference date will be described later.

In addition, on the final delivery settlement date on the fourth business day from the last trading day pertaining to the delisting and on the fourth business day from the day before the commencement of the period trading suspension, the securities No failure can occur. In addition,
The term suspension of trading means suspension of trading in the cases listed in Article 29, Item 1 of the Tokyo Stock Exchange Business Rules.

Next, regarding the buy-in, a buy-in request
Restrictions on buy-in billing / execution, members who are charged
The following describes the assignment of a pay-in, cancellation of a buy-in request, exclusion from the buy-in cost provisional (temporary), reassignment of the cost-bearing member (provisional), execution of the buy-in, determination of the cost-bearing member, settlement of the buy-in.

[0279] The buy-in request will be described. The failed member can request a buy-in from the stock exchange 14 for the failed member that continues beyond the time limit for settlement of the transfer securities on the next day of the failed day.
Claims for buy-ins will be made on and after the day after the failure.
It is possible from 13:30 to 14:30 every day.

A description will be given of restrictions on the buy-in request and execution. A buy-in request cannot be made on the day before the base date for vesting rights (two business days before the base date falls on a holiday) or on the same day. In addition, the buy-in execution is 2
If it is not completed before the business day, the claim for the unexecuted Buy-in is invalidated, and if the Buy-in Claiming Member (hereinafter referred to as “Billing Member”) wishes to buy-in again, After the next day, you will need to make the buy-in request again. FIG. 22 shows the restrictions related to the reference date and the like for the buy-in request and execution.

A buy-in request cannot be made after the delisting date. If the execution of the buy-in has not been completed by the last day of the trading, the claim for the uncompleted execution of the buy-in is invalidated. FIG. 23 shows the restrictions on delisting of the buy-in request and execution. Buy-in requests cannot be made during the trading suspension period (from the trading suspension start date to the cancellation date). If the execution of the buy-in has not been completed by the day before the period commencement date of the suspension of trading, the request for the uncompleted execution of the buy-in is invalidated.
FIG. 24 shows the restrictions on suspension of trading during the buy-in request / execution period. In addition, the request and execution of the buy-in may be restricted as required.

Next, the assignment of members (provisional) subject to cost sharing will be described. If a buy-in request is made, to temporarily determine the correspondence between the buy-in request on the day and the target for which the costs required to execute the buy-in based on the request should be borne (hereinafter referred to as “expense target (provisional)”) ,
After the buy-in billing time limit (14:30), the members 2 to be covered by the cost (hereinafter, referred to as “provisional members (provisional)”) are allocated in the following order.

That is, allocation is performed in order from the oldest failure occurrence date, and if the failure occurrence date is the same, a proportional distribution process is performed according to the number of failures. Here, the reason why the term “provisional” is set is that since the buy-in is executed four business days after the buy-in billing date, the cost-bearing member may fluctuate due to failure cancellation or the like during that time. . The members who will be charged until the buy-in is executed will be provisional.

Next, cancellation of a buy-in request will be described. The buy-in request by the failed member is canceled when the failure is canceled, the buy-in is executed, and the buy-in request is withdrawn. That is, if the fail-in related to the buy-in request is resolved after the buy-in request date, the buy-in request is resolved. Also, when the buy-in is completed,
The buy-in request for the execution will be resolved.

[0285] Withdrawal of the buy-in request cancels the buy-in request. If the billing member does not complete all scheduled executions on the original scheduled buy-in execution date,
The claim can be withdrawn from the following day. In addition,
In this case, it is possible to withdraw the billing in order from the billing position with the oldest buy-in billing date, and it is not possible to partially cancel each billing balance.

For example, a specific example of the withdrawal of a billing ball is shown below.
If there is a billing amount of 5 and the billing date is A day, the billing amount is 10 and the billing date is (A + 1) day, and the billing amount is 6 and the billing date is (A + 2) day, the billable withdrawal quantity is Only one of 5, 15, and 21 which are the accumulated balance of the billing quantity.

Next, the exclusion from the buy-in cost burden (provisional) will be described. The member (provisional) for whom the buy-in cost is borne is excluded from the burden in the case of delivery settlement, in the case of cancellation of the buy-in request, and in the case of exclusion due to completion of the buy-in execution.

That is, in the case where the cost-bearing member (provisional) resolves the failure related to the cost-bearing (provisional) by delivery settlement, the failed portion is excluded from the cost-bearing (provisional). In addition, even if the member (provisional) who is to bear the cost resolves the failure by re-netting, it is not excluded from the member (provisional) who bears the cost. If the member (provisional) who is to bear the cost resolves the failure by re-netting, the delivery and settlement obligation is transferred to the other member 2 at the same time.

If the other member 2 further fails, the failure of the requesting member is not canceled. At this time, the members (provisional) who are eligible to pay the expenses that have resolved the failure by re-netting are excluded from the burden,
Assuming that the new fail member (other member 2) is the member for whom the cost is to be borne (provisional), the other member 2 will not be given the opportunity to cancel the failure, and at the shortest, will bear the cost of executing the buy-in on the day of the failure. There is a possibility of becoming a target member (fixed). This is contrary to the purpose of providing a grace period in the buy-in system, so even if the failure is canceled by re-netting, it will not be excluded from the members (provisional) who bear the cost. However, the members whose costs have been rescinded due to re-netting (provisional) are deemed to have made an effort to resolve the failures, and are excluded from the target in priority to those who have not yet failed (provisional). .

When the buy-in request is canceled by the cancellation of the fail-in request related to the buy-in request or the cancellation of the buy-in request, the corresponding member for whom the buy-in cost is to be paid (provisional) is excluded from the charge. If the costs required for the execution of the buy-in are completed as a result of the completion of the buy-in, the buyer is exempt from the buy-in costs (provisional).

A description will be given of the reassignment of the members (provisional) for which the costs are to be borne. Member who is subject to initial cost (provisional)
After the allotment, the members who bear the expenses (provisional) will be re-allocated along with the cancellation of the buy-in request and the exclusion of the members (provisional) from the expenses. This reallocation is performed in the following a to
f.

A. The balance of the billing position is excluded from the one with the oldest billing date. b. Scheduled buy-in dates for the members (provisional) who bear the costs must not be advanced. c. In the case where the member (provisional) who is to bear the cost cancels the failure by the delivery settlement, the member corresponding to the amount is given the highest priority and is excluded from the member (provisional).

D. To minimize the execution of buy-ins,
The date assigned as the provisional cost (temporary) (hereinafter referred to as the “provisional (provisional) allocation date”) is excluded from the oldest date. e. Of the expenses (temporary), those for which the failure has been resolved by re-netting are excluded from the expenses (temporary) prior to the unresolved failure. f. In the case of excluding (temporary) cost-bearing (temporary) allocation dates with the same assignment date, the cost-taking (temporary) allocations are excluded in order from the latest failure occurrence date.

Next, execution of a buy-in will be described.
In executing the buy-in, the member (provisional) subject to the cost purchases the position subject to the buy-in in the following manner. In other words, the seller is the member 2 who wants to sell, and the buyer is the member (tentative) who is to bear the cost. If there are a plurality of provisional members (provisional), each provisional member (provisional) becomes a buyer for each of the provisionable amounts. The selling order reception time is 15:00 to 15:30, and the execution time is 15:30. The contract method is a competitive bidding method within the range of the final closing price on the day and a price obtained by adding 10% to the price, and the contract price is a unified price based on the highest price among the order prices of all the successful bidders. The order receiving method is a terminal input method by the member 2 using the stock exchange WAN system 1.

The distinction between self and consignment is as follows. The purchase by the provisional member (provisional) shall be based on its own calculation. On the other hand, when the selling member inputs a selling order, the selling member selects and inputs whether the order is outsourced by the customer or based on his own calculation. The settlement date is the day following the buy-in execution completion date.

[0296] The determination of the member for whom the cost is to be paid will be described. For the buy-in execution completed amount determined by the buy-in execution, the cost bearer is allocated in the order of a to d below,
Determine. a. If there is an unresolved failure and an unresolved failure due to re-netting, the allocation is made from the unresolved failure. b. The unresolved failures are allocated in order from the oldest occurrence date of the failure. c. Allotments due to re-netting are assigned in order from the oldest date of failure occurrence. d. B. c. In, if there is a cost burden target (provisional) having the same failure occurrence date, the cost is prorated according to the number of failures.

Next, the settlement of the buy-in will be described. The settlement date of the buy-in shall be the day following the completion date of the buy-in execution. Regarding the settlement method, securities settlement, fund settlement, and delivery related to settlement will be described.

First, securities settlement will be described. FIG. 25 is a diagram illustrating securities settlement related to execution of a buy-in. Securities settlement (delivery) by the selling member 411 accompanying the execution of the buy-in is performed by Non-DVP settlement. In the case of the securities settlement when the buy-in billing member 412 and the seller member 411 are the same, the settlement is performed with respect to the argument amount of the delivery amount.
It is subject to general settlement in Non-DVP settlement. In the Non-DVP settlement of the sales member 411 accompanying the execution of the buy-in, the delivery of the securities delivery slip (DB) is not permitted.

[0299] The securities settlement (reception method) of the buy-in member (buy-in member) 413 accompanying the completion of the buy-in execution is performed by DVP settlement. When the buy-in execution is completed,
The securities settlement (reception) related to the cancellation of the failed position of the buy-in requesting member 412 is performed by Non-DVP settlement. It is subject to general settlement in Non-DVP settlement.

Next, fund settlement will be described. FIG.
FIG. 6 is a diagram showing fund settlement related to execution of a buy-in. Fund settlement (receipt) by the selling member 411 upon completion of the buy-in execution is performed by Non-DVP settlement. Non-D
It is subject to general settlement in VP settlement. Buyer (buy-in cost bearer) 413 associated with completion of buy-in execution
In the settlement of funds, an amount equivalent to (buy-in execution day settlement price) x (purchase amount) (hereinafter referred to as "buy-in purchase price") is exchanged as DVP settlement, and the buy-in purchase is executed from the contract price in the buy-in execution. The deducted amount is exchanged as Non-DVP settlement. The amount obtained by subtracting the buy-in purchase price from the contract price in executing the buy-in corresponds to the cost burden.

In the settlement of funds (payment) of the buy-in execution member 412 upon completion of the execution of the buy-in, the amount obtained by multiplying the settlement amount of the buy-in execution day by the settlement amount is paid by Non-DVP settlement. It is subject to general settlement in Non-DVP settlement.

The delivery related to the settlement will be described. Securities are settled by the account transfer in the custody transfer organization 15, and funds are settled by the fund transfer account transfer. Non-DV out of securities settlement
With regard to the settlement at P (the receipt of securities by the buy-in billing member 412 and the delivery of securities by the selling member 411), the stock exchange 14 requests the transfer of securities to the custody transfer agency 15 on the day (receipt / delivery). (Specified account transfer processing). In this case, the stock exchange 14 uniformly attaches a transfer transfer suspension report to the transfer request. In addition to the settlement related to the execution of the buy-in (Non-DVP settlement), a settlement suspension statement is similarly attached to the settlement on the base day and the settlement related to the issue date settlement transaction.

[0303] Next, the affairs related to the failure performed by the member 2 will be described. The member 2 receives the “failure information notification (after delivery)” from the stock exchange 14 at １３13: 30 after the time limit for settlement of the delivery securities on the S day. Based on this data, it is possible to grasp the status of occurrence and cancellation of the failure / failed on the day (failure / failed grasp first).

Among the fail members, “notice of additional payment”
The member 2 whose amount is described in the additional payment amount column (received at ~ 13: 30) makes a deposit transfer to the fund settlement account of the stock exchange 14 by the fund payment time limit (14:15) (fail member). Transfer of funds related to the failure by). The failed member receives the payment amount corresponding to the fail at the fund settlement account of the member 2 at 14:45, which is the fund settlement receiving time (the failed member gives and receives the fund related to the fail).

Next, the member 2 receives a “failure information notification (after netting)” from the stock exchange 14 at 17:00. Based on this data, the member 2 grasps the status of the cancellation of the fail and the failed which have been subjected to the execution of the buy-in and the re-netting process (the grasp of the failure and the failed 2nd).
Times).

Next, a description will be given of the work relating to the buy-in performed by the member 2 and the stock exchange 14. The following affairs will be performed on the buy-in request date. If the failee makes a buy-in request, 13: 3
After confirming that the failure has continued by the “failure information notification (after delivery)” received from the stock exchange 14 by 0, input from the client computer 9 by 14:30 on the day (failed member By buy-in).

The member 412 who has made the buy-in request confirms the validity / invalidity of the buy-in request on the screen displayed on the client computer 9 (buy-in request acceptance confirmation).

[0308] After accepting the buy-in request, the stock exchange 14 allocates the member (provisional) 411a to which the cost is to be paid. After this allocation, the buy-in billing member 412 and the cost-bearing member (provisional) 411a receive the “buy-in information notification (initial)” from the stock exchange 14 at 15:00 (the buy-in billing / cost-bearing (provisional) member). Grasp (1).

If the buy-in billing member 412 and the cost-bearing member (provisional) 411a do not resolve the buy-in billing / cost-bearing (provisional) 411a by the re-netting process on the day, the buy-in request member 412 and the cost bearer (provisional) 411a are re-listed from the stock exchange 14 at 17:00. A “buy-in information notification (after netting)” reflecting the netting process is received (understand the buy-in request / expense burden target (provisional) (2)). Note that this “buy-in information notification (after netting)” is sent to the relevant member 411a, 412
Will be sent every day until all buy-in requests or expenses (provisional) related to are canceled.

[0310] The following day's clerical work will be described. The buy-in requesting member 412 and the provisional member (provisional) 411a receive a buy-in request /
If the cost burden (provisional) is not resolved, ~ 13: 30
Then, a “buy-in information notification (after delivery)” reflecting the processing by the delivery settlement is received from the stock exchange 14 (acquisition of buy-in billing / cost burden target (3)).

[0311] The "buy-in information notification (after delivery)" is transmitted daily until all the buy-in requests or expenses (provisional) related to the member 2 are resolved. If the buy-in request / cost burden target (provisional) is not resolved on the day, a “buy-in information notification (after netting)” is received at 17:00.

[0312] A buy-in execution notice is received as a business operation two days after the buy-in request (the day before the buy-in execution day).
In other words, if the re-netting process on the day after the buy-in billing day does not eliminate the buy-in billing / cost burden target (provisional), all members 2 will receive a buy-in scheduled to be executed the next day from the stock exchange 14 at 17:00.
Receive “buy-in execution notice (previous day notice)”. Here, all members 2 include members 2 who are not subject to the buy-in request / cost burden. Note that the scheduled buy-in quantity may be smaller than the quantity in the advance notice of the day before the buy-in execution depending on the settlement status on the execution day.

A description will be given of the work on the buy-in execution date (the buy-in request date + the third day or later). If the buy-in billing / cost burden target (provisional) for the buy-in scheduled to be executed on the day is not resolved by delivery settlement on the day, all members 2 will receive 1
After 3:30, a “buy-in execution notification” is received from the stock exchange 14 (buy-in execution notification).

Next, after 15:00, the stock exchange 14
Executes the buy-in in the following manner (execution of the buy-in).
First, in response to execution of a buy-in, the member 2 who intends to sell orders a sales order from the client computer 9 from 15:00 to 15:30. Thereafter, the stock exchange 14 closes the acceptance of the sale related to the buy-in execution at 15:30, and contracts the sell orders in the order of the lowest price within the predetermined execution price range. In this case, irrespective of the price of the sell order, the highest sell order price of all the contracts is set as a uniform contract price.

In the case where the sell order quantity at the same price exceeds the remaining buy-in execution quantity (the quantity excluding the contract quantity at the lower price), the minimum unit is allocated in the order of the member with the highest sell order quantity, Distribution is made by prorating based on the remaining order quantity. In executing the buy-in, the cost-bearing member (temporary) 413 buys the buy-in execution amount, but no practical work is performed at this time.

Thereafter, all the members 2 receive a “buy-in execution result notification” describing the buy-in execution brand, execution price, execution quantity, etc. from the stock exchange 14 to 16:00. If the buy-in execution has not been completed and the buy-in request related to the execution has not been resolved by the next day settlement time for the transfer securities, the buy-in is executed again on the next day for the buy-in unexecuted quantity.

Here, a case related to the execution of buy-in will be described. For example, the buy-in execution volume is 5,000 shares (buy-in billing member: First member 3,000 shares, second member 2,000 shares)
And the trading unit is 1000 shares and the executable price range is 1000
JPY-1100 yen, sales order is 1000 yen / A member 1000
Stock, 1050 yen / B member 3000 shares, C member 2000
If there are 2,000 shares and D-members, the allocation of the contract will be as follows.

First, contracts are made in order from the sales order quantity at the lowest price. In this case, 1000 shares of A member are executed. Next, if there is a sales order for multiple members 2 at the same price, and the total sales order quantity exceeds the buy-in execution remaining quantity (the quantity excluding the contracted quantity at the lower price), in the order of the member with the highest sales order quantity, Allocation is performed by giving the minimum unit priority over the quantity of other parts. In this case, each of the B, C, and D members has a contract of 1,000 shares.

At this time, the quantity other than the minimum unit is apportioned and distributed based on the sales order remaining quantity of each member 2. In this case, the B-member is contracted for 1,000 shares. Based on the above, the contracted amount is 1000 shares for A member and 2000 for B member.
Shares, 1000 shares for C members and 1000 shares for D members. The contract price is 1050 yen for each contract.

[0320] The affairs of the day after the buy-in execution day will be described. On the day following the buy-in execution date, withdrawal of the buy-in request and settlement related to the buy-in are performed.

In the case where the buy-in request member 412 withdraws the request, the following procedure is performed (withdrawal of the buy-in request). The buy-in request member 412 makes a “declare withdrawal of buy-in request” by input from the client computer 9 from 9:00 to 13:00 from the day after the day on which the execution of the buy-in is not completed. The buy-in request member 412 that has made the buy-in withdrawal report confirms the validity or invalidity of the buy-in request by receiving the “buy-in request withdrawal acceptance confirmation data”.

[0320] Buy-in requesting member 412, buy-in cost burden member 413, and buy-in sales member 411.
Performs the next settlement on the day following the buy-in execution completion date (settlement related to the buy-in). Buy-in request member 412
Means the settlement of securities by the receipt of securities related to the failure elimination due to the completion of the buy-in (Non-DVP settlement) and the payment of the payment related to the elimination of the fail (Non-DVP settlement)
Performs fund settlement.

[0323] The buy-in cost-bearing member 413 receives the purchased securities upon completion of the buy-in execution (DVP settlement).
, Settlement of buy-in purchase price and mark-to-market margin (DVP settlement), and settlement of funds related to completion of buy-in execution (Non-DVP settlement).

[0324] The selling member 411 related to the buy-in executes the securities settlement (N
(on-DVP settlement) and fund settlement by receiving the contract price related to the execution of the buy-in (Non-DVP settlement).
Regarding the securities settlement by Non-DVP relating to the execution of buy-in, the stock exchange 14 uniformly attaches a transfer transfer suspension report to a transfer request to the custody transfer organization 15 (a request on the day). The delivery member must cancel the suspension report at the time of fund transfer. In the case of Non-DVP settlement, delivery of securities delivery slip (DB) is not permitted.

Next, regarding handling of special processing,
The explanations are divided into items such as settlement on the base date, delisting, suspension of trading during the period, and merger of members and stocks. A description will be given of the designation of receiving / transferring of the settlement and the paperwork on the base date. The stock exchange 14 designates the receiving / delivery designation of the settlement on the base date or the like. In other words, the reference date, etc. (vesting date)
If there is an unresolved fail at the time of securities settlement the day before,
The settlement for the failure cancellation performed on the next day (the day such as the base date) is performed based on the receiving / delivery designation made by the stock exchange 14 on the previous day, with the delivery member and the stock exchange 14 and the stock exchange 14 And between the receiving member. It provides an opportunity to negotiate a prior failure resolution. The processing of dividends and other rights is coordinated between the parties designated by the stock exchange 14.

A description will be given of a paperwork processing procedure for settlement on a reference date or the like. First, at 17:00 on the day before the reference date or the like, the failing member and the failed member receive the "receipt / transfer specification sheet for settlement on the reference date".

Next, the securities exchange 14 is requested by the stock exchange 14 on the day of settlement on the day of settlement on the day of settlement (account transfer processing designated for receiving / transferring) on settlement on the base date or the like. . In addition, the stock exchange 14 attaches a transfer transfer suspension report uniformly to the transfer request. In addition to settlement on the base date, etc., settlement related to the execution of buy-in (No
In the same manner, a transfer suspension declaration is attached to the settlement relating to the settlement transaction on the issue date (n-DVP settlement).

[0328] The delivery member generates the number of delivered securities in his or her account by 13:00. At this time, the delivery member cancels the delivery suspension uniformly attached by the stock exchange 14.

If the transfer member transfers the securities from the transfer member account to the stock exchange account by the process of generating the number of securities to be transferred to its own account, the value of the transferred securities is calculated on the net.・ Included in the value of acceptable securities in debit calculation.

The transfer from the stock exchange account to the receiving member account is performed by transferring the securities from the transferring member account to the stock exchange account by the above-mentioned process in which the transferring member generates the number of securities to be transferred to its own account. Will be implemented as soon as the In this transfer, the transfer can be performed without being based on the net debit calculation.

[0331] Here, with respect to the receiving transfer request relating to the same day transfer request, transfer relating to a part of the requested amount is not performed, and the transfer request amount is generated in the stock exchange account, or "the same day transfer request When a transfer is made from a member's account to a stock exchange account for a part of the quantity, and the transfer to the receiving member's account is fulfilled due to the correction of the reduction in the transfer amount on the day. '' Is executed when the stock exchange 14 corrects the decrease in the transfer request amount.

[0332] When securities are transferred from the stock exchange account to the receiving member account, the value of the receivable securities in the net debit calculation is not reduced.

At the time of the delivery securities settlement period (13:00),
If the transfer of the securities from the member account to the stock exchange account has not been completed, the stock exchange 14 cancels or corrects the transfer request. As a correction, if a transfer amount was transferred from the member account to the stock exchange account for a part of the transfer request amount on the day, the transfer request amount was transferred to the receiving member account by reducing the transfer request amount on the day. Is implemented. If the settlement is not completed, the same settlement as the failure of the normal DVP settlement is performed in the settlement on the next day.

[0334] The delivery member who has generated a failure on the day such as the reference date, etc., shall issue a "Dividend / right delivery notice" in writing to the receiving member (failed member) who is the other party of the failure. I do.

The handling of fail and buy-in at the time of delisting is as follows. Fail is not allowed for the final settlement date of the delisting issue. In addition, buy-in requests cannot be made on days after the delisting date.
If the buy-in execution cannot be completed by the last day of trading, the claim for the uncompleted buy-in execution will be invalid.

The handling of fail and buy-in during suspension of trading during the period is as follows. Here, the term suspension of trading means suspension of trading in the case listed in Article 29, Item 1 of the Tokyo Stock Exchange Business Rules. Fail is not allowed for settlement on the day before the suspension of trading during the period + 3 days. No request for buy-in during suspension of trading during the period will be accepted. If the buy-in execution has not been completed by the day before the period of suspension of trading, the claim for the uncompleted buy-in execution will be invalid.

The handling at the time of member merger is as follows.
For contract positions executed before the merger date, settlements made after the merger date will be handled as follows.
In securities settlement, the contract between the merged member and the merged member is netted and settled by the merged member (the merged member is not settled). In the settlement of funds, the settlement price of the merged member and the merged member is netted and settled by the merged member (the merged member is not settled).

[0338] All existing deposits on the previous day of the merged member are returned on the day before the date of the merger. Data regarding the failed member and the buy-in of the merged member is transferred to the merged member immediately before the re-netting process on the day before the merger date. If the fail position and the failed position coexist, a cancellation process is performed.

At the time of issue merger (excluding peer merger), settlement of the merged issue is handled as follows in accordance with the treatment of delisting. Fail is not allowed for the final settlement date of the merged stock, which will be delisted due to the merger. Buy-in requests cannot be made on or after the delisting date. If the buy-in execution has not been completed by the last day of trading, the claim for the uncompleted buy-in execution will be invalid.

[0340] The handling of a fail-by in a brand merger by an equal merger will be described. If the merger registration date is within the merger date + 2 days, the settlement of the merged issue coming after the day following the merger registration date will be performed by adding and subtracting the settlement of the surviving issue with the same settlement date. Handle as follows. That is, the data relating to the fail and buy-in of the merged issue is transferred to the merged issue immediately before the re-netting process on the registration date. If the fail position and the failed position coexist, a cancellation process is performed.

If the merger registration date is after the merger date + 3 days, the settlement of the merged issue will not be combined with the settlement of the surviving issue, and the balance will not be calculated. . In other words, no fail will be accepted on the final delivery date of the merged issue that will be delisted due to the merger. In addition, buy-in requests cannot be made on days after the delisting date. If the buy-in execution has not been completed by the last day of trading, the claim for the uncompleted buy-in execution will be invalid.

The handling of convertible bonds in DVP settlement will be described with respect to DVP settlement, handling of accrued interest in net debit calculation, handling of accrued interest in fail, and handling of interest payment date. D
The target of VP settlement is ordinary trade, single stock trade, close price trade, and off-auction basket trade. However, single stock transactions and off-auction basket counterparties are limited to transactions with settlement dates similar to ordinary transactions.

Regarding the handling of accrued interest in the net debit calculation, the securities value in the net debit calculation of the convertible bond is calculated including the accrued interest. That is, the security value is calculated by the following equation. Securities value of convertible bonds = securities amount (number of units) x
(1 par value x settlement price / 100 + accrued interest per unit) (rounded down to the nearest yen) "securities value" in this formula
Applies to both the value of securities delivered when securities are delivered to a stock exchange account and the value of securities received when securities are received from a stock exchange account.

The handling of the accrued interest at the time of a failure is as follows. In other words, if a failure occurs in the settlement of the convertible bond, the accrued interest during the fail period is subjected to daily mark-down processing. Here, the mark-to-market margin relating to the accrued interest in the event of a failure in the settlement of convertible bonds is referred to as “accrued interest adjustment (fail)”.
As a result of the mark-to-price process, the accrued interest during the fail period will be received by the failed member.

As a specific example, an example of handling of accrued interest at the time of a failure will be described. First, the preconditions of this case will be described. The F-member has failed the delivery of the par value of 1 million yen on the S and S + 1 days (resolved on S + 2). The T-member has failed to receive a par value of 1,000,000 yen on the S and S + 1 days (cancelled on S + 2). The contract price is 1,000,000 yen (excluding interest). S day ~
The settlement price on S + 2 is 100 yen (the payment price is 1
100,000 yen). Accrued interest is 10,000 yen until S day, S +
It costs 11,000 yen until 1st and 12,000 yen until S + 2nd.

The flow of settlement when the above prerequisites exist is as follows:
It is as follows. The settlement on the S day is as follows. 9:
From 00 to 13:00, the T-member deposits 1.010 million yen as the DVP scheduled payment. This 10.1 million yen is calculated as 1 million yen (settlement price) + 10,000 yen (interested interest until S day). At 13:00, the F-member's fail is confirmed. At 14:45, the T-member receives 1.01 million yen as a surplus of the DVP scheduled payment.

The settlement on the (S + 1) th day is as follows. 9:
From 00 to 13:00, the T-member deposits 1.010 million yen as the DVP scheduled payment. This 1,100,000 yen is calculated by 1,000,000 yen (settlement price) + 11,000 yen (interest interest until S + 1 day)-01,000 yen (price margin on the elapsed interest). At 13:00, the F-member's fail is confirmed. From 13:30 to 14:15, the F-member pays an additional payment of ¥ 10,000. The 0.1000 yen is a price difference for accrued interest. At 14:45, the T-member receives 101,000 yen as a surplus of the scheduled payment for DVP. This 1011,000 yen is calculated as 1,000,000 yen (settlement price) + 111,000 yen (elapsed interest until S + 1 day).

The settlement on the S + 2 day is as follows. 9:
At 00-13: 00, the T-member deposits 1011,000 yen as the DVP scheduled payment. This 1011,000 yen is
It is calculated by 1,000,000 yen (settlement price) + 12,000 yen (S + interest accrued up to 2 days)-0.10 yen (price difference on accrued interest). From 13:30 to 14:15, the F member cancels the failure by delivering the securities. 14: 4
On F5, the F member receives the delivery price of 1011,000 yen. This 1011,000 yen is 1,000,000 yen (settlement price) +1.2
Calculated as 10,000 yen (S + interest accrued up to 2 days)-0.10 yen (price difference on accrued interest).

The handling related to the interest payment date will be described separately for the settlement date and the interest handling. The settlement date is determined as follows. In the case of ordinary transactions, for sales transactions in which the fourth business day from the date of the conclusion of the sales transaction is the day before the interest payment date (hereinafter referred to as "X day"), 5 days from the date of the conclusion of the sales transaction. The business day (interest payment date) is the settlement date. X
Same-day settlement transactions with a settlement date of -1 day are not allowed. X-1
For a buy-in execution whose day is the next business day, the settlement date is the third business day (interest payment date) counted from the date of the buy-in execution.

The handling of interest is performed as follows. For settlements made on the day of the interest payment date, the accrued interest shall not be added to the trading value, and shall be treated as a falling interest rate issue. When a failure occurs on the X-2 day, the difference between the interest payment amount (full amount) and the accrued interest amount up to the X-2 day is added to the mark-up processing of the accrued interest relating to the fail. The X-1 day on which settlement is not performed is subject to the calculation period for late damages. If a failure occurs on the X-2 day, settlement is not performed on the X-1 day, so the resolution of the failure will be X days at the shortest. It will be 2 days from 2 to 1.

The settlement of the issue date settlement transaction is performed as follows. The transfer request of the securities to the custody transfer organization 15 relating to the settlement of the issue date settlement transaction is performed by the same day transfer request (acceptance / transfer designation account transfer processing) after the start of the DVP settlement. This is to change what was conventionally performed by the stock exchange 14 on the previous day's transfer request.

The stock exchange 14 uniformly attaches a transfer transfer temporary suspension report to the transfer request on the day. Watakata members
By 14:45 (14:00 on a half-holiday), the number of securities to be delivered is generated in its own account. At this time, the delivery member cancels the temporary suspension provided by the stock exchange 14.

In introducing DVP settlement, Non-DV
The transfer time limit for funds and securities settlement related to P settlement is as follows. However, here, the settlement of the JGB spot transaction after the central bank network system RTGS conversion and the delivery settlement of the JGB futures transaction are excluded. Payment from the payment method to the stock exchange 14 is made until 13:00 on the settlement date, and receipt from the stock exchange 14 by the receiving party is made at 14:45. In securities settlement, exchange of securities is 14:45
(Semi-holiday is 14:00).

Next, a handling policy in the event of a failure in the stock exchange WAN system 1 will be described. If clearing data cannot be received by the stock exchange WAN system 1, the following measures are taken. If the transmission data at night cannot be received, a paper-based form is created and distributed to each member 2 or the like in principle. Here, as night transmission data,
"Trading Schedule", "Summary", "Declaration and Allocation Schedule of Stock Option", "Scheduled Settlement Volume by Brand",
"Overall Clearing Sheet (Contract Price)", "Previous Day Collateral Balance Table", "Total Payment Price Calculation Table (Scheduled Amount)" are applicable.
If it is not possible to receive data during the day, each member 2
FAX transmission. However, depending on the situation of the obstacle, there is a case where the buy-in request on the day, withdrawal of the buy-in request, and execution of the buy-in may be restricted.

If the client computer 9 cannot input a buy-in request, withdrawal of a buy-in request, or an order for a sell order related to execution of a buy-in,
The stock exchange 14 receives a document describing the input contents from the member 2 or the like who cannot make an input by facsimile, and makes an input from the stock exchange terminal computer on behalf of the member 2. If there are a large number of members 2 who cannot make an input, limit measures may be taken for a buy-in request and execution.

The handling in the event of a failure in the storage transfer organization system will be described. If a failure occurs in the storage transfer organization system, the following processing is performed in principle depending on the time of the failure and the situation of the failure. Depending on the situation of the obstacle, flexible measures may be taken regardless of the principle. Note that the buy-in request, withdrawal of the buy-in request, and execution of the buy-in may be restricted depending on the state of the failure.

If the recovery time of the failure of the storage transfer agency system is in the early time zone of the settlement date and the settlement is expected to be completed by resuming the settlement, the settlement is resumed. In this case, the settlement time limit may be changed (extended). Even if the storage transfer organization system failure is recovered, if it is expected that the processing on the day is difficult to complete, the processing is performed according to the following cases depending on the time zone of the failure occurrence.

[0358] The first case is a case where a failure occurs before the start of night batch processing at the storage and transfer agency system on the day before the settlement. In this case, the entire settlement is postponed to the next day. In this case, the deferred settlement is processed by offsetting the settlement on the day after the deferment. Note that the deferred settlement in this case is not treated as a fail / failed.

[0359] The second case is a case that occurred before the batch processing on the day before the settlement and before the online start of the storage transfer institution system on the day of settlement, and in this case, for the securities settlement which has not been completed by the night batch processing, the next day. Is deferred to In this case, the deferred settlement portion is processed by offsetting the settlement portion on the day after the deferral. Note that the deferred settlement in this case is not treated as a fail / failed. In addition, fund settlement related to securities settlement completed by night batch processing is performed, and other fund settlements are deferred to the next day. In this case, the deferred settlement portion is processed by offsetting the settlement portion on the day after the deferral.

[0360] The third case is that, after the online transfer of the custody transfer institution system on the day of settlement, the delivery settlement settlement period (13:
00) This occurs before, and in this case, the following processing is performed without continuing DVP settlement. In other words, securities remaining in the securities exchange settlement account shall be forcibly transferred to the receiving member account without using net debit calculation,
After that, for unsettled securities settlement, the securities will be delivered by the same day transfer request on the next day. Note that the deferred settlement in this case is not treated as a fail / failed. In addition, fund settlement is performed assuming that no failure has occurred on the settlement day.

The fourth case is a case in which the settlement has occurred on or after the settlement date (13:00) of the day-to-day securities settlement. In this case, the securities remaining in the settlement account on the stock exchange are calculated by the net debit calculation. Will be forcibly transferred to the receiving member's account, and any unsettled securities settlement will be treated as a fail, and settlement will be deferred to the next day. In this case, the deferred settlement portion is processed by offsetting the settlement portion on the day after the deferral. In addition, the settlement of funds for the settlement of securities is completed, and the settlement of funds for the fail of securities is deferred to the next day. In this case, the deferred settlement portion is processed by offsetting the settlement portion on the day after the deferral. Here, it is considered that the securities settlement in which the forcible transfer to the receiving member account is performed has been completed, and this is referred to as “securities settlement completion”.

FIG. 27 is a diagram showing a specific example of securities settlement based on net debit calculation. In this figure, the plus sign of each value indicates receipt, and the minus sign indicates payment. The premise of this specific example is as follows. (1) X Securities settles the following stock trading. [Sell] A Trading 1,000 shares, contract price 1,200 yen [Buy] B Electric 1,000 shares, contract price 1,400 yen

(2) The settlement price (closing price on the day before settlement) for both A Trading and B Electric is 1,000 yen. X Securities does not deposit the previous day's collateral. X Securities member stock receiving order: 1st B Electric (1,00
0 shares, 1 million yen) B-Electricity member receiving order by brand: 1st
0 shares), 2nd place X Securities (1,000 shares), 3rd place Second Party Securities ... There is no other settlement of X Securities.

Next, the receivable securities amount is calculated. X Securities pays 200,000 yen for DVP
Deposited as the expected payment, X Securities A Trading 1,000
Assuming that the stock (equivalent to 1 million yen) has been delivered to the stock exchange account, the amount of receivable securities is: receivable amount of securities = deposit amount of collateral deposited on the previous day + deposit value of DVP expected deposit + deposit value of delivered securities + Additional payment transfer amount-Received securities value ± Price difference amount = 0 yen + 200,000 yen + 1 million yen + 0 yen-0 yen-200,000 yen = 1 million yen.

Next, a search is performed based on the issue receipt order by member. B-Electricity, which is the No. 1 issuer by stock of X Securities, has 1
Since it is 100,000 yen, B Electricity 1,000,000 yen ≦ net debit amount 1,000,000 yen, and B Electricity is a receivable securities.

[0366] Thereafter, the balance of the stock exchange account is confirmed based on the receiving member ranking by brand. Assuming that 3,000 shares have been transferred to the stock exchange account by the other member 2 for B Electric, 3,000 shares of the receiving member ranking by brand (2,000 shares for the first place and 2,000 shares for the second place X securities one securities X Since the transfer amount is 3,000 shares, it means that the transfer of the B electric stock received by X Securities to the stock exchange account has been made. From the above,
In the account transfer, the account transfer from the stock exchange account to the X securities is executed for B electricity.

FIG. 28 is a specific example of the method of determining the receiving member rank by brand, and is a diagram showing the determination of the receiving member rank by brand on September 15 for a certain brand. In the case of FIG. 28, a buy-in request is made (highest priority group), the buy-in request date is the first set (September 11), and the failed date is the first set (9
Member CBI (1) on the 5th and 9th of the month) is ranked first and the buy-in is requested (highest priority group).
On March 11), the member ABI (1) whose failed day is the second set (September 8) is ranked 2nd and the buy-in is requested (highest priority group), and the buy-in request date is the second set (September 12). However, the member EBI (1) whose failed day was the same day (September 8) but was given priority based on the lottery result was ranked third, and the failed day was the second set (9
Member ABI (1) on the 8th of March is ranked 2nd and a buy-in is requested (highest priority group), and the buy-in request date is set to
Member ABI (2), who failed on the same day (September 8) but was subordinated by the lottery result, is in fourth place.

Subsequently, the number of failed members (priority group) and the member C whose failure date is the first set (September 9) is 5
Member B, who is the failing member (priority group), the member B whose failure date is the same day in the latter group (September 12) based on the result of the lottery, is ranked sixth, and the failing member (priority group), failing On the same day (September 12), the member A, who was subordinated by the lottery result, is ranked 7th. continue,
Member 2 who has not been charged in and is not a failed member (subordinate group), member F with the highest priority based on the lottery result, member E with priority 9th, member D with subordination Is in 10th place.

FIG. 29 shows the DVP settlement system of this embodiment and the conventional D.P. B. It is a figure which shows the security deposit on the day before of a system, and margin deposit / return work (image). Conventional D. B. Under the system, margin deposit at 9:00 to 12:00, 9:00
At about 14:00, the margin return was accepted and executed. In contrast, in the present embodiment, margin deposit is performed at 9:00 to 12:00, and margin return reception and execution are performed at 9:00 to 14:00. Also, with the introduction of the “day before collateral deposit” system, the previous day's collateral deposit from 9: 00 to 12: 00
0, 9:00 to 12:00 on the day before,
9: 00 to 12: Acceptance of the previous day's deposit (surplus) return
00, the previous day's collateral refund execution is 14:15 to 15: 0
Perform 0.

[0370] Also, after 15:00, the delivery / receipt status is distributed by the stock exchange WAN system 1, and
After 00, the security exchange WAN system 1 distributes the previous day's deposit balance (surplus information). Here, the surplus of the previous day's security deposit is a deposit of the previous day's security deposit that exceeds the amount of the securities to be received plus the mark-to-market margin. In addition to the ones shown in FIG. 29, there is also an emergency transaction margin deposit.

Next, a specific example of a settlement scheme for executing a buy-in will be described. In this specific example, the buy-in execution date is X days, and the buy-in execution brand is the A brand. The X-1 closing price (= X day clearing price) of this brand is 1,000 yen, the X day closing price (= X + 1 day clearing price) is 1,100 yen, and the buy-in execution volume is 1000.
Assume that the stock and buy-in contract price is 1,300 yen.

The settlement scheme related to the execution of the buy-in is as follows. The settlement related to the buy-in execution is performed on the business day following the buy-in execution date. FIGS. 30 to 33 show settlements performed by the billing member, the cost bearing member, and the selling member, respectively. It should be noted that, on the day following the buy-in execution date, there is no other member 2 except for the execution of the buy-in and the delivery related to the fail / failed regarding the execution.

FIG. 30 is a diagram showing securities settlement performed by each of the billing member, the cost-bearing member, and the selling member when the cost-bearing member continues to fail based on the buy-in. With the execution of the buy-in, the settlement relating to the failed party that is the basis of the execution shifts from DVP settlement to Non-DVP settlement. Therefore, the billing member's securities settlement is Non
-By DVP settlement. The settlement of the purchase amount of the member who bears the cost associated with the execution of the buy-in is performed by DVP settlement, which is offset by the securities settlement related to the fail which is the basis of the execution, and FIG.
A member who bears a cost of 0 will not receive or deliver.

FIG. 31 is a diagram showing fund settlement performed by each of the billing member, the cost-bearing member, and the selling member when the cost-bearing member continues to fail based on the buy-in. With the execution of the buy-in, the settlement relating to the failed party that is the basis of the execution shifts from DVP settlement to Non-DVP settlement. Therefore, the fund settlement of the billing member is Non
-By DVP settlement.

[0375] Out of the contract price paid by the member who bears the costs associated with the buy-in execution, the fund settlement corresponding to "buy-in execution day settlement price x quantity" is performed by DVP settlement, and therefore the fund settlement relating to the failure that is the basis of the execution. 31. In the DVP settlement, the member bearing the cost in FIG. 31 does not receive or deliver. However, the buy-in cost contribution amount corresponding to the difference between the buy-in contract price and the “buy-in execution day settlement price × quantity” is made by Non-DVP settlement.
Therefore, the cost-paying member pays 300 (1,000 yen) N
Perform by on-DVP settlement.

FIG. 32 is a diagram showing securities settlement performed by each of the billing member, the cost-bearing member, and the selling member when the cost-bearing member has resolved the failure on which the buy-in execution is based by re-netting. With the execution of the buy-in, the settlement relating to the failed party that is the basis of the execution shifts from DVP settlement to Non-DVP settlement. Therefore, the securities settlement of the billing member is based on the Non-DVP settlement. The settlement of the purchase amount of the member who bears the cost associated with the execution of the buy-in is performed by DVP settlement.

FIG. 33 is a diagram showing fund settlement performed by each of the billing member, the cost-bearing member, and the selling member when the cost-bearing member has resolved the failure on which the buy-in is executed by re-netting. With the execution of the buy-in, the settlement relating to the failed party that is the basis of the execution shifts from DVP settlement to Non-DVP settlement. Therefore, the fund settlement of the billing member is based on the Non-DVP settlement.

[0378] Fund settlement corresponding to "buy-in execution day settlement price x quantity" in the contract price of the member who bears the cost of executing the buy-in is performed by DVP settlement. The payment amount (1,000 thousand yen) of the cost-bearing member shown in FIG. 33 is calculated by the following expression: payment amount (1,000 thousand yen) = settlement price (1,100 thousand yen) -price margin (100 thousand yen). You. The buy-in cost share amount corresponding to the difference between the buy-in contract price and the “buy-in execution day settlement price × quantity” is made by Non-DVP settlement. Therefore, the cost-bearing member pays 300 (thousand yen) by Non-DVP settlement.

[0379] Fig. 34 to Fig. 38 show office work time tables relating to DVP settlement.

FIG. 39 is a diagram showing a daily work / data flowchart. In FIG. 39, the normal system refers to processing from execution to settlement, and the abnormal system refers to
This refers to processing from the occurrence of a failure when a failure occurs in settlement to the execution of a buy-in. As described above, the T date is the contract date, the S date is the settlement date,
= T + 3.

[0381] The top column shows the daily work schedule. The settlement is executed at 12:20, and the funds are released at 14:00. At 17:00 in the evening, the settlement value base and the collateral valuation calculation are performed. In the evening, 2nd day correction at 21:00, price base at 21:00 and 22:00, 23:00
Is collated.

FIGS. 40 to 42 are diagrams showing the outline of the business / data flow, and illustrate the flowchart of FIG. 39 in more detail.

FIGS. 43 to 46 are diagrams showing the flow of the entry process and the validity of the application contents. FIG. 43 shows the flow of the buy-in request declaration and the buy-in request cancellation, and the validity of the application content. The entry possible period of the buy-in billing is S
+ N from 12:30 to 14:30. The maximum number of shares that can be requested for buy-in is acquired by the DVP server computer 4 when the CSI server computer 12 is linked. The billable quantity is set for two members. The number of shares in the "fail information notification (after DEL)" to be sent on the day is the basis.
Separately, there is only one case per issue. Version number management is performed for each entry. In order to secure the entry immediately before the end of the claimable time, the reception time on the system may be set slightly later.

[0384] If a fail-in member reports a buy-in request in process 501-01, process 501-02.
Then, the DVP server computer 4 (stock exchange WAN system 1) determines whether the input data is appropriate. If the input data is not appropriate (process 501-02: NG),
In the process 501-04, the reception status is set to “not accepted”.

When input data is appropriate (process 501)
-02: OK), the processing reception status is set to “temporary reception”. Also, regardless of the result of the input check in the process 501-01, the DVP server computer 4
The input data is transmitted from the (stock exchange WAN system 1) to the CSI server computer 12. Next, processing 5
In 01-06, data verification is performed in the CSI server computer 12, and it is determined whether the data is authenticated.
If the data is not determined to be appropriate (process 501-0)
6: NG), and the reception status is “not accepted” in the processing 501-08
And

When the data is determined to be appropriate (step 50
1-06: OK), the reception status is set to “main reception” in processing 501-07. Until the Buy-In Claim is declared “Accepted”, Buy-In Claims cannot be canceled. Version number management is performed only on the day of filing (within the time allowed for entry). If the processing 501-04, 08 indicates "not accepted", the status of the list on the WWW, the broadcast notification tool (broadcast notification API 11a, the broadcast notification program 11c), and e-mail means Communicate to the user in an appropriate manner. The content of the buy-in request is executed on the day of entry + the third day.

The member 2 who has made a buy-in request can cancel the buy-in request. The entry available period for canceling the buy-in request is from 12:30 to 1 on the day of entry.
It is until 4:30. The cancellation unit for a buy-in request is
Executable in the unit of “buy-in claim report”. When the buy-in request is canceled in the process 502-01 by the member 2 who made the buy-in request, in the process 502-02, the DVP server computer 4 (stock exchange WAN system 1) determines whether the input data is appropriate.

If the input data is not appropriate (process 502)
-02: NG), the acceptance status is set to "not accepted" in the process 502-04. If the input data is appropriate (process 502
-02: OK), the processing reception status is set to "temporary cancellation". Further, regardless of the result of the input check processing of the processing 502-02, the DVP server computer 4 is executed in the processing 502-05.
The input data is transmitted from the (stock exchange WAN system 1) to the CSI server computer 12. Next, processing 5
In 02-06, data verification is performed in the CSI server computer 12, and it is determined whether or not the data has been authenticated.
If the data is not determined to be appropriate (process 502-0)
6: NG), and the reception status is “not accepted” in the process 502-08.
And

When the data is determined to be appropriate (step 50
2-06: OK), the reception status is set to "cancelled" in process 502-07. Until the entry becomes “cancelled”, cancellation of the cancellation of the buy-in request (reinstatement of the claim report) cannot be performed.

FIG. 44 shows the flow of a buy-in sales order and cancellation of the buy-in sales order and the validity of the application contents. A buy-in sales order is an order to sell a security for which a buy-in has been made. The flow of the buy-in sale order is the same as the flow of the buy-in bill declaration in FIG. 43 except that the “buy-in bill order” and the “buy-in sale order” are different, and therefore the description is omitted.

The possible entry period of the buy-in sale order is from 15:00 to 15:30 on the buy-in execution date. The maximum number of shares to be ordered is set in order units. There can be multiple entries across the same security. Version number management is performed for each entry. In order to secure the entry immediately before the end of the claimable time, it is preferable to set the reception time on the system slightly later.

When the reception status is set to "not accepted", the status / broadcast notification tool (broadcast notification API 11a, broadcast notification program 11
c)-Inform the user by an appropriate method out of e-mail means.

Also, canceling a buy-in sales order order at the bottom of FIG. 44 means canceling an order for a sell order of a security for which a buy-in has been requested. The flow of canceling a buy-in sales order is as follows:
Except for the difference between the “buy-in request declaration” and the “buy-in sales order order”, the flow is the same as that of the buy-in request cancellation in FIG. Entry period for buy-in sale order cancellation is 15:00 on the day of entry
It is until 15:30. The cancellation unit of the buy-in sales order is executable in the unit of “buy-in sales order”.

FIG. 45 shows the flow of withdrawal of the buy-in request, cancellation of the withdrawal of the buy-in request, and the validity of the application contents. The flow of the withdrawal of the buy-in request is the same as the flow of the withdrawal of the buy-in request in FIG. In addition, the cancellation of the buy-in withdrawal withdrawal in the lower part of FIG. 45 means canceling the order of the sell order of the securities for which the buy-in has been requested. The flow of canceling a buy-in request is the same as the flow of canceling a buy-in request shown in FIG. 43 except that “buy-in request declaration” and “buy-in request withdrawal” are different from each other, and a description thereof will be omitted.

The entry possible period of withdrawal of a buy-in request is from 9:00 to 12:00 on the day following the execution day. The number of shares that can be withdrawn is described on a separate page in CSI
The data is transmitted from the server computer 12 to the DVP server computer 4. The remaining number of shares in the “buy-in execution result notification” sent the day before is used as a reference. It is preferable that the withdrawal entry be made possible from the “buy-in execution result notification” list because of its better operability.

[0396] The entry of withdrawal is a remaining quantity unit for each "buy-in request report", and enables the withdrawal of the buy-in request from the oldest. Version number management is performed for each entry. In order to secure the entry immediately before the withdrawal time expires, it is preferable to set the reception time on the system slightly later. When the reception status is set to “rejected”, the status / broadcast notification tool (broadcast notification API 11a, broadcast notification program 11) of the list on the WWW
c)-Inform the user by an appropriate method out of e-mail means.

FIG. 46 is a diagram showing the flow of each entry process and the time zone in which each entry process is performed.

Next, based on the broadcast notification API 11a of FIG. 47 or the processing block diagram by applying the WWW browser 11b and the broadcast notification program 11c, the broadcast notification API 11
a or WWW browser 11b / broadcast notification program 1
Processing by applying 1c will be described. The processing block diagram of FIG. 47 shows that the client computer 9 of the member 2
When the broadcast notification API 11a is provided (a), the client computer 9 of the member 2
And (b) when the broadcast notification program 11c is provided.

First, the case (a) in which the client computer 9 of the member 2 has the broadcast notification API 11a will be described. A storage device of the client computer 9,
For example, the broadcast notification API 11a is stored in the HDD. Further, the client computer 9 stores the payment information data file 10, the company business application 44
Is stored in the server computer 42 of the company. The settlement information data file 10 is stored in the stock exchange WAN.
This is a database for storing public information transmitted from the system 1. The company business application 44
This is an application program for managing the internal operations of the member 2.

The in-house server computer 42 is a computer that controls the processing of the in-house business application 44. It is connected to the client computer 9 in which the broadcast notification API 11a is stored, and the storage device stores a payment information data file 10. Further, a plurality of terminal computers 45 used by each user of the member 2 are connected to the company server computer 42.

The broadcast notification API 11a corresponds to the stock exchange WA.
An application interface for transmitting and receiving information to and from a WWW server computer 5 (not shown) of the N system 1. Specifically, the broadcast notification API 11
The access and connection management is performed between a and the WWW server computer 5 of the stock exchange WAN system 1. That is, the client computer 9 is connected to the stock exchange WA
When accessing and connecting to the N system 1, the stock exchange WAN system 1 receives a notification of the access and connection from the API 11a and manages it. Also, from the WWW server computer 5 of the stock exchange WAN system 1, distributable information indicating that public information can be distributed is provided.
Broadcast notifications are sent in real time. Regarding the deliverable information, a data download process is performed from the WWW server computer 5 of the stock exchange WAN system 1 in response to a download request from the broadcast notification API 11a.

The client computer 9 of the member 2 is
A case (b) in which a WWW browser 11b and a broadcast notification program 11c are provided will be described. A broadcast notification program 11c and a browser 11b are stored in a storage device of the client computer 9, for example, an HDD. Further, the client computer 9 stores the payment information data file 10, the company business application 44 in the storage device.
Is connected to the server computer 42 of the company. The payment information data file 10 and the company business application 44 have the same configuration as that in the case where the client computer 9 of the member 2 has the broadcast notification API 11a (a).

[0403] C (not shown) of the client computer 9
The PU executes the broadcast notification program 11 stored in the storage device.
c) Control the processing of the browser 11b. Further, it transmits and receives various information to and from the server computer 42 of the company, such as transmission of data acquired from the stock exchange WAN system 1 and reception of a command from the server computer 42 of the company. Further, a terminal computer used by each user of the member 2 may be connected to the client computer 9.

The broadcast notification program 11c is a program for performing processing for transmitting and receiving information to and from a WWW server computer 5 (not shown) of the stock exchange WAN system 1. Specifically, access / connection management is performed between the broadcast notification program 11c and the WWW server computer 5 of the stock exchange WAN system 1. That is, the broadcast notification program 11c is sent from the client computer 9.
Is used to access and connect to the stock exchange WAN system 1, the stock exchange WAN system 1 sends a notification that the access and connection has been made to the broadcast notification program 11c.
Receive from and manage. In addition, from the WWW server computer 5 of the stock exchange WAN system 1, deliverable information that public information can be delivered is broadcasted in real time. In response to a download request from the broadcast notification program 11c, the D of the stock exchange WAN system 1
Data download processing is performed from the VP server computer 4 or the WWW server computer 5.

[0405] The browser 11b is connected to the stock exchange WA.
A process for transmitting and receiving information to and from a WWW server computer 5 (not shown) of the N system 1 is performed. Specifically, access management is performed between the browser 11b and the WWW server computer 5 of the stock exchange WAN system 1.
That is, from the client computer 9, the browser 1
1b, when the stock exchange WAN system 1 is accessed and connected, the stock exchange WAN system 1
The notification of the access / connection is received from the browser 11b and managed. In response to a download request from the browser 11b, a data download process is performed from the WWW server computer 5 of the stock exchange WAN system 1.

Next, the broadcast notification program 11c shown in FIG.
Broadcast notification program 11c based on the functional block diagram of FIG.
The function of will be described. The function shown in FIG. 48 is controlled by a CPU (not shown) of the client computer 9b. First, an input device of the client computer 9b,
For example, the broadcast notification program 11c is activated in response to an instruction input from a mouse or a keyboard (process 51). At the time of this startup processing, an authentication procedure such as user ID authentication is executed. Next, prior to the start of the broadcast notification program 11c, the latest deliverable information indicating that the public information can be delivered, which is broadcast to the client computer 9b, is acquired from the DVP server computer 4 (processing). 52).

After that, with the broadcast notification program 11c activated, every time the deliverable information is transmitted from the DVP server computer 4, real-time reception processing of the deliverable information for automatically receiving the latest deliverable information is performed. (Process 53). Each time this information is received in real time (process 53), the client computer 9a
A communication status management process for managing the communication status is performed (process 5).
7). When the real-time information receiving process is performed (process 53), a process of displaying on the screen a broadcast notification that the information is ready for timely delivery is performed (process 5).
4).

[0408] In the received broadcast notification of the distributable information, the user who operates the client computer 9b looks at the title of the information listed on the screen, selects the information that needs to be downloaded, and clicks the "download" button. When the download is clicked and the download instruction is issued, the client computer 9b downloads the information from the DVP server computer 4 (process 55).

When the download process (process 55) by the client computer 9b is performed, the stock exchange W
The DVP server computer 4 of the AN system 1 performs a download monitoring process for monitoring a download status (process 56). On the other hand, looking at the title of the information listed in the broadcast notification received by the broadcast notification reception process,
When the user operating the client computer 9b clicks and selects an information title that needs to be browsed and gives a browsing instruction, the client computer 9 first performs a process of activating the WWW browser 11b (process 5).
9). Then, via the WWW browser 11b, the WWW
A browsing process for displaying information from the server computer 5 as a WWW page is performed (process 60).

[0410] When the browsing process is performed by the client computer 9b (process 60), the WWW server computer 5 of the stock exchange WAN system 1 performs a browsing result monitoring process for monitoring the browsing status (process 61). When the communication state management processing (processing 57) and the information display processing on the WWW page (processing 60) are performed by the client computer 9b, the D of the stock exchange WAN system 1 is changed.
The VP server computer 4 executes these processes (process 5
7, the process 60) is received, and the process of monitoring the information reception status is performed (process 62).

While the broadcast notification program 11c is running, the processes 53 to 61 are repeated, and the latest information is received from the WWW server computer 5 every time a broadcast notification is made. Then, the client computer 9
When the user clicks the "end" button on the screen b, it is determined that a program end instruction has been issued, and the broadcast notification program 11c is ended (process 63). During the period from the start-up process (process 51) of the broadcast notification program 11c to the end process (process 63) of the broadcast notification program 11c, it is necessary to confirm receipt of a live notification from the client computer 9b notifying that the live is alive. By
The DVP server computer 4 performs a session management (survival monitoring) process (process 64). Thus, the processing in FIG. 48 is completed.

Next, the broadcast notification API 11a will be described. The broadcast notification API 11a is used by being stored in the client computer 9a of the member 2. Broadcast notification AP
Preconditions for applying I11a will be described. Broadcast notification A
The precondition for connecting by applying the PI 11a is LO
During the period from GIN to LOGOUT, a “connection management thread (survival notification exit)” is activated to notify the stock exchange WAN system 1 that the server or the like on the member site is alive.

[0413] The stock exchange WAN system 1 manages which user ID is connected and whether the connection destination is operating normally. The stock exchange WAN system 1 requests the client computer 9 of the member 2 to guarantee connection with the stock exchange WAN system 1.

[0414] The precondition for receiving information by applying the broadcast notification API 11a is as follows: during the period from LOGIN to LOGOUT, "accumulated data management thread (information reception exit)"
To guarantee the reception status of the member site. The stock exchange WAN system 1 manages which member 2 has referred information and which member 2 has been notified of which information. The stock exchange WAN system 1 provides the client computer 9 of the member 2 with the stock exchange W
It is required to guarantee a reception exit to the AN system 1.

As shown in FIG. 49, the broadcast notification API 11
a is, as a component, connection management (Connect
TionMonitor) class 74, accumulated data management (AccumulationData) class 75, environmental information management (Environ) class 78, message management (MessageController) class 7
6. Connection interface (AgentConnect
ionInterface) class 72 is provided.

Here, the connection management class 74 is a class for managing / executing connection / disconnection to / from the stock exchange WAN system 1 and notification processing of the existence of a member site (member server computer). Stored data management class 7
5 is distributable information (notification of preparation of distribution information,
This class stores and manages business messages. It performs data reception (reception confirmation), download, and data update processing. The environment information management class 78 is a class that manages environment setting information (such as a directory for saving a file to be downloaded). The set value is Tar
getEnvironment. Ini file. The message management class 76 is a class for recording, managing, and displaying events that have occurred in each class.

The above connection management class, stored data management class, environment information management class, and message management class
Configure the broadcast notification connection package. The connection interface class 72 is a class implemented when a main class (a class created when connecting to the stock exchange WAN system 1 using an API) 73 is used. The main class processes events generated from the connection management class 74, the stored data management class 75, the environment information management class 78, and the message management class 76 via the connection interface.

FIG. 49 is a diagram showing the relationship between components provided by the broadcast notification API 11a and the role of each component. The stock exchange WAN system 1 is connected to the connection management class 74 and the stored data management class 75 of the broadcast notification connection package 71, and the connection management class 74 of the broadcast notification connection package 71 via the connection interface 72. The stored data management class 75 and the main class 73 are connected.

[0419] The connection management class 74, the stored data management class 75, and the message management class 76 are connected. The message management class 76 is connected to a log database 77 for storing logs. The broadcast notification connection package supports connection management (monitoring) of the DVP server computer 4, management of a notification data message, and a message / log management function. The interface class 72 required to use this class
Prepare

Next, based on FIG. 49, the broadcast notification API
The role of each component provided by 11a will be described. First, a description will be given of a process in a case where information disclosed in the stock exchange WAN system 1 is browsed from the client computer 9 via the broadcast notification connection package 71.

[0421] The main class 73 performs an authentication procedure (process 95). This authentication procedure is transmitted to the connection management class 74 of the broadcast notification connection package 71 via the connection interface 72. Broadcast notification connection package 71
Performs a connection notification process to the stock exchange WAN system 1 (process 89). Upon receiving the connection notification (step 89), the stock exchange WAN system 1 performs surviving monitoring processing (step 81).

[0422] The main class 73 performs a connection request procedure (process 96). This connection request procedure is transmitted to the connection management class 74 of the broadcast notification connection package 71. The broadcast notification connection package 71 performs a LOGIN process on the stock exchange WAN system 1 (process 90). When the LOGIN process is performed (process 90), the stock exchange WAN system 1 performs an authentication procedure process (process 82).

The main class 73 performs a disconnection request procedure (process 97). This disconnection request procedure is transmitted to the connection management class 74 of the broadcast notification connection package 71. The broadcast notification connection package 71 performs a LOGOUT process on the stock exchange WAN system 1 (process 91).

[0424] The stock exchange WAN system 1 is LOGO
When the UT process is performed (process 91), a LOGOUT process is performed (process 83). When the LOGOUT processing is performed (processing 83), the termination processing of the survival monitoring is performed (processing 8).
4). That is, the survival monitoring by the stock exchange WAN system 1 is performed from when the connection request processing (processing 96) is performed by the main class 73 to when the disconnection request processing (processing 97) is performed.

[0425] Next, a description will be given of the case where the stock exchange WAN system 1 broadcasts to the client computer 9 via the broadcast notification connection package 71 to the effect that information distribution is ready. When the stock exchange WAN system 1 is ready to deliver the information to be broadcasted, that is, the deliverable information, it notifies that the delivery is ready,
A delivery preparation notification process for transmitting a list of public information ready for delivery is performed (process 85). Upon receiving the notification of the distribution preparation (process 85), the stored data management class of the broadcast notification connection package performs an information reception process of receiving a notification that the distribution is ready and a public information list that is ready for distribution (process 85). 92). When the information receiving process is performed (process 9
2), the stock exchange WAN system 1 performs a reception confirmation process of a notification for confirming that the information has been received (Process 8).
6).

When the information receiving process is performed (process 9)
2) The information received by the stored data management class 75 via the connection interface 72 is transmitted to the main class 73. The main class 73 executes update data reception processing (processing 100) for receiving update data or notification data. The notification data receiving process (process 99) to be received is performed. The received data that has undergone the update data reception processing (processing 100) or the notification data reception processing (processing 99) is registered in the reception database 98.

Next, the stock exchange W is sent from the client computer 9 via the broadcast notification connection package 71.
A process for acquiring the latest information disclosed in the AN system 1 will be described. The main class 73 performs data update request processing for requesting data update (processing 10
1). When the data update request processing from the main class 73 is performed (processing 101), the broadcast notification connection package 71
The stored data management class 75 performs a process of acquiring the latest information (process 93).

When the latest information is obtained by the stored data management class 75 (process 93), the stock exchange WA is executed.
The N system 1 performs a process of distributing the latest information (process 8).
7). When the latest information distribution process is performed by the stock exchange WAN system 1 (process 87), the stored data management class 75 performs the latest information acquisition process (process 93).

Next, the client computer 9
The exchange-prepared data is transferred to the stock exchange WAN system 1.
A process for downloading from the side will be described.
First, the main class 73 performs a download request process for requesting information download (process 102). When the download request processing is performed by the main class 73 (processing 102), the stored data management class performs information downloading processing (processing 94).

In response to the download process (process 94) of the stored data management class 75, the stock exchange WAN system 1 performs a process of transmitting a CSV file for download (process 88). When the CSV file is transmitted by the stock exchange WAN system 1 (process 88), the stored data management class 75 performs a download process (process 94) for receiving the CSV file and transmitting it to the main class 73. When a download process is performed by the stored data management class 75 and the CSV file is transmitted by the stored data management class 75 (process 94), the main class 73 performs a process of receiving the transmitted CSV file (process 103).

FIG. 50 is a diagram showing an example of a data processing procedure by a component provided by the broadcast notification API 11a. A delivery possible notice indicating that delivery is possible for a domestic stock trading list, which is an example of settlement information, is shown. Broadcast notification,
Then, a case where the domestic stock certificate trading schedule is downloaded in response to a download request from the member 2 will be described. First, when the stock exchange WAN system 1 prepares for distribution of the domestic stock trading statement, which is the settlement information, the stock exchange WAN system 1 transmits the distributable information indicating that the settlement information is ready for distribution. Perform notification processing (processing 11
1).

[0432] When notification processing of the distributable information indicating that the information has been prepared for distribution is performed (processing 111), the client computer 9 of the member 2 displays "Ready for distribution of domestic stock certificate trading statement" on the screen. Is performed (process 121). The client computer 2
A receiving database registration process for registering the received deliverable information in the receiving database 98 is performed (process 122), and a process of displaying link information of the domestic stock trading statement on a screen displaying the deliverable information is performed (process 123). ).

When the user operating the client computer 9 wishes to download the domestic stock trading statement, the user issues a download instruction for the domestic stock trading statement on the screen (process 124). The client computer 9 performs a process of setting a download request flag in the domestic stock certificate trading statement based on the download command (process 125). Next, with respect to the domestic stock certificate trading schedule with the download request flag set (processing 12
5) A process for requesting the download of the CSV file is performed (process 126).

When the client computer 9 performs the download request process (process 126), the stock exchange WAN system 1 performs a process of receiving the download request (process 112). Next, a CSV that stores a CSV file created for downloading the domestic stock trading statement with the download request flag set is downloaded.
Extracted from the file database 254 (Process 11
3) A process of transmitting a CSV file of the extracted information is performed (process 114).

Next, the client computer 9
A process for receiving the transmitted CSV file is performed (process 127). In this process, the received CSV file is
It is registered in the CSV file database on the client computer 9 side (process 128).

FIG. 51 is a diagram showing a process of connecting to the stock exchange WAN system 1 in an application creation procedure using the broadcast notification API 11a. When the client computer 9 connects to the stock exchange WAN system 1 using the broadcast notification API 11a, the connection management class 7
4 and the stored data management class 75 (reception exit) need to be started by another thread.

First, the main class 73 performs a class initialization process of the connection management class 74, the message management class 76, and the environment information management class 78 (process 139). Next, the main class 73 uses the login method of the connection management class 74 to connect to the stock exchange WAN system 1. The connection to the stock exchange WAN system 1 is performed in the following procedure. That is, main class 7
3 performs LOGIN processing to the stock exchange WAN system 1 (processing 140). L by this main class 73
In response to the OGIN process (process 140), the connection management class 74 sets the LOGIN to the stock exchange WAN system 1.
Processing is performed (processing 135). When the LOGIN process is performed by the connection management class 74 (process 135), the stock exchange WAN system 1 performs an authentication procedure process (process 131).

If the above LOGIN processing is successful (processing 1
40), the main class 73 performs a process of activating the connection management thread (process 141). Main class 73
Then, when the processing for activating the connection management thread is performed (processing 141), the connection management thread is activated in the connection management class 74 (processing 136). When the connection management thread is activated (process 136), the stock exchange WAN system 1
Performs a connection monitoring process of monitoring a connection management thread (process 132).

Next, the main class 73 performs processing for initializing the stored data management class 75 (processing 14).
2). Thereafter, the main class 73 calls the latest information acquisition method of the stored data management class 75, and performs the latest information acquisition process (process 143). Here, the latest information refers to difference information for the current day that occurred before the LOGIN processing (processing 135). When the process of acquiring the latest information by the main class 73 is performed (process 143), the stored data management class 75 performs a process of acquiring the latest information from the stock exchange WAN system 1 (process 13).
7). When the latest information acquisition process is performed by the stored data management class 75 (process 137), the stock exchange WAN system 1 distributes the notification data including the title list of the information ready for distribution to the stored data management class 75. Processing is performed (processing 133).

Next, the main class 73 performs a process of activating a stored data management thread (information receiving exit) (process 144). When the process of activating the accumulated data management thread by the main class 73 (process 144) is performed, the accumulated data management thread is activated in the accumulated data management class 75 (process 138). When the accumulated data management thread is activated (processing 138), the stock exchange WAN system 1 performs a notification data distribution processing (processing 13).
4).

FIG. 52 is a diagram showing a data download process in an application creation procedure using the broadcast notification API 11a. When the connection with the stock exchange WAN system 1 is completed in the process 136 of FIG. 51, each event is transmitted as event information to a required method of the connection interface 72. The event received by the main class 73 includes a change in the state of data, preparation of new data, and the like. The main class 73 refers to the received event, confirms the content thereof, and executes a download process as necessary.

The procedure for downloading the information ready for distribution in the stock exchange WAN system 1 is as follows. First, the stock exchange WAN system 1 performs distribution processing of broadcast notification data (processing 134). Stock Exchange WA
When the notification data is delivered from the N system 1 (processing 13
4), the stored data management class 74 performs an information receiving process through the stored data management thread (process 152). When the information receiving process is performed in the stored data management class 74 (process 152),
The main class 73 receives the notification data.

The main class 73 determines the content of the received notification data (event), and performs a process of extracting the notification data related to the preparation of the payment information distribution (process 156). The stored data management class 74 performs a process of acquiring the latest information as appropriate (process 153). Next, the main class 73
Performs a process of setting a download request flag in notification data in which link information of a file to be downloaded is recorded (process 157). The setting of the download request flag is performed by setting a flag in the notification data registered in the reception database 98.

Thereafter, the main class 73 performs a process of requesting the stored data management class 74 to update the information (process 158). When the process of requesting information update is performed by the main class 73 (process 158), the stored data management class 74 performs a process of updating the stored data stored in the database (process 154).

Thereafter, the main class 73 calls the download method of the stored data management class 74,
Download request processing is performed (processing 159). When the download request process is performed by the main class 73 (process 159), the stored data management class 74 performs a download process of the information for which the flag is set by the main class 73 (process 155).

[0446] When the information download process is performed by the stored data management class 74 (process 155), the stock exchange WAN system 1 performs a process of transmitting a CSV file of the information flagged by the main class 73 (step 155). Process 151). When the transmission of the CSV file for download is performed, the stored data management class 74 (process 1).
51), a download process of the transmitted CSV file is performed (process 155), and the CSV file database 1
Register at 28.

Next, an outline of the process of the broadcast notification of the distributable information controlled by the DVP server computer 4 will be described. The process of the broadcast notification of the distributable information is performed by the CSI server computer 12 that creates the payment information data,
The system includes a payment database 6 that receives payment information from the server computer 12 and stores payment information, a CSV file database 254 that stores a CSV file for downloading payment information, and a distribution information management database 172 that stores deliverable information. A DVP server computer 4 for broadcasting notification of distributable information to the client computer 9;
And between.

FIG. 53 shows an outline of the processing of the notification task function performed between the CSI server computer 12, the DVP server computer 4, and the client computer 9. The notification function 16 is a notification function 16 for notifying the client computer 9 of the member 2 of settlement information such as a notice of a request for transmission and reception of information created by the CSI server computer 12 and a notification from the administrator as a business message.
7, 168 and status notification functions 169, 171 for notifying the CSI server computer 12 that the client computer 9 has recognized the notified information. Since the transmission of the information to the client computer 9 is ultimately performed by the information communication function 164, the notification task function includes the data setup system application 173 requesting the notification and the program of the information communication server 166 of the information communication function 164. Provides the interface function of. The information communication function 164 refers to a function of performing a broadcast notification, and is a generic term including an information communication client and a server.

The outline of the flow of the processing of the notification service function shown in FIG. 53 will be described. Note that (1) to (1) in FIG.
5) represents each process described below. Processing (1) to (1)
5) will be described. The data setup business application 173 of the DVP server computer 4
A process of receiving payment information from the SI server computer 12 is performed, and a series of processes, such as a storage process of a payment database 6 (not shown), a CSV file creation process as download data of the payment information, and a CSV file database 254 storage process of the created CSV file, are performed. Is performed (process (1)).

Next, after the data setup processing (processing (1)) is completed normally, the data setup system business application 173 executes the distribution information table (2 members).
At 172a, a process for registering information necessary for the broadcast notification of the distributable information indicating that the public information such as the settlement information, the business message, and the operation control information can be distributed is performed (process (2)). At this time, when the public information is the immediate transmission type in which the public information is highly urgent information, the data setup application 173 immediately transmits the notification function (immediate transmission) 16.
7 is processed (process (2)).

The notification function (immediate notification) 167 requests notification of the requested distributable information to the information communication server 166 (processing (4a)).
A “data setup completion notification” is transmitted to the I server computer 12 in information units. This transmission procedure,
This corresponds to the data setup completion notification transmission procedure. The notification function (immediate notification) 167 corresponds to a data setup completion notification transmitting unit. At this time, the notification status flag of the distribution information management database 172 is updated to the completion of the notification to the broadcast notification (process (4b)).

The notifying function (time designation) 168 checks the distribution information management database 172 at regular intervals (in units of 10 minutes) (processing (5a)), and sends the distributable information at the distribution time to the communication information server 166. A notification request is made (process (5b)). If the notification is normally received, a "data setup completion notification" is transmitted to the CSI server computer 12 in information units. At this time, the notification status flag of the distribution information management database 172 is updated to the completion of the notification to the broadcast notification.

The information communication server 166 as the distributable information distributing means searches the distribution information management database 172 for the member 2 to be transmitted based on the distributable information requested from the notification functions 167 and 168 (processing (processing ( 6a)), the data is converted into user units and transmitted to the information communication client 163 (process (6b)). For more information about distributable information,
The payment system distributable information is acquired from the distribution information management / distribution information detailed table 172 (process (6c)), and the business message is obtained from the business message table 176 (process (6d)).

When a business message, which is a kind of public information, is registered on the terminal 178 of the operator of the DVP server computer 4, the registration is made in the business message table 176, and the notification function (cooperation command) 175 is called ( Processing (7)). The notification function (cooperation command) 175
The information received from the business message registration function is registered in the distribution information management database 172 (process (8)).
At this time, if the business message is of the immediate transmission type, a notification request is sent to the notification function (immediate transmission) 167 (process (9)).

[0455] The information communication server 166 uses the status from the client 163 for the information notified in the processing as status notification information as a status notification function (acceptance & immediate transmission) 169.
(Step (10)). A business message reception completion signal that is automatically created by receiving a business message from the client computer 9, a download completion signal that is automatically created by downloading, and a browsing that is automatically created by being displayed on the screen. An execution signal is transmitted. The status notification information is created on the server computer 4 side based on the business message reception completion signal, the download completion signal, and the browse execution signal.

Here, the status notification information notified from the information communication server 166 to the status notification function (acceptance & immediate transmission) 169 includes “the completion of the payment information setup notification to the client computer 9 side” and “business message”. Has been notified to the client computer 9 side ",
"The payment information was downloaded by the client computer 9" and "The payment information was referred to by the browser of the client computer 9". It should be noted that “distributable information is notified to the client computer 9 side” may be treated in the same manner as “business message is notified to the client computer 9 side”.

[0457] Of these information, the first one of "payment information has been downloaded" or "payment information has been referred to by the browser" is regarded as "confirmation completed" and the CSI server computer 12 Notify to Among the confirmed information including “the payment information has been downloaded” and “the payment information has been referred to by the browser”, the first notified information corresponds to the member confirmed information. The notification of the member confirmed information corresponds to a member confirmed information transmitting procedure. The member-confirmed information is transmitted from the DVP server computer 4 to the client computer 9 side, and is displayed in the confirmation status item 209 of FIG. This transmission corresponds to the confirmed display procedure.

[0458] Of the status notification information, "the completion of the payment information setup notification to the client computer 9 side" is the setup completion notification information, and "the business message has been notified to the client computer side" is the delivery possible notification information. The “payment information has been downloaded by the client computer 9” corresponds to the downloaded information, and the “payment information has been referred to by the browser of the client computer 9” corresponds to the browsed information.

Also, the status notification information requested from the information communication server 166 has a status notification function (acceptance & immediate transmission) 1
At the time of reception at 69, the log is stored as an operation log for each ID, and the status notification management table 170 collectively manages it for two members. The two members are units for notifying the CSI server computer 12. The status notification management table 170 corresponds to a status notification information storage unit.

[0460] The status notification function 169 is the information communication server 1.
The information requested from the server 66 is registered in the status notification table 170 (process (11)). At this time, if the status notification requires immediate transmission, the transmission status flag to the CSI server computer 12 in the status notification table 170 is updated to “transmitted” and immediately transmitted to the CSI server computer 12 (processing (12 )). This transmission process corresponds to a status notification information transmission procedure. The status notification function 169 corresponds to a status notification information transmission unit.

The status notification function (periodic transmission) 171 checks and blocks the status notification table 170 at regular intervals (in units of 10 minutes),
Send to At this time, the CSI of the status notification table 170
The transmission status flag to the server computer 12 is updated to “transmitted” and immediately transmitted to the CSI server computer 12. This transmission process corresponds to a status notification information transmission procedure. The status notification function (periodic transmission) 171 corresponds to a status notification information transmission unit.

The notification function (immediate notification) 167 notifies the information communication function (broadcast notification function) 164 of the operation control information from the control function 174 (process (14)). When the operation control information notified here is accepted by the DVP server computer 4, the operation control information is immediate notification type information immediately notified to the client computer 9, and is not managed in the distribution information management database 172. The operation control information includes information such as a notification of a daily change, a business stop, and a business start. The control function 177 controls the CSI server computer 12
Receiving the reception confirmation message corresponding to the status notification notified to the CSI server computer 12 in the status notification table 170
Update the transmission status flag.

Note that the CSI server computer 12
If the status notification information has not been received even though the predetermined time has elapsed after receiving the data setup completion information,
The DVP server computer 4 may be sent a stop command to stop the information transmission to the client computer 9. After the information transmission stop processing, D
When it is determined that the communication state between the VP server computer 4 and the client computer 9 is normal,
The configuration may be such that information can be transmitted between the DVP server computer 4 and the client computer 9.

Next, the configuration of the notification service function will be described. Here, the notification task function includes a notification function and a status notification function. That is, notification functions 167, 168, and 175 that receive notification requests from the respective business applications operating on the DVP server computer 4 and the administrator function (business message) and notify the client computer 9 via the information communication function 164 are provided. And a status notification function 169, 171 for receiving the processing status of the client computer 9 from the information communication function 164 and notifying the CSI server computer 12. The outline of each process will be described below.

[0466] The notification function is the DVP server computer 4
The storage device, for example, a program stored in the HDD, includes three subfunctions: a notification function (immediate notification) 167, a notification function (time notification) 168, and a notification function (cooperation command) 175. Notification function (immediate notification) 167
Receives the deliverable information that needs to be transmitted immediately to the member 2 side, and requests the information communication server 166 for notification. The processing performed by the notification function (immediate notification) 167 is shown in FIG.
This will be described with reference to the flowchart of FIG.

First, the process starts upon receiving a notification request from the data setup system business application 173, the notification function (cooperation command) 175, and the control function 174. The information requested to be notified is checked, and it is determined whether the information should be notified immediately (step S1). This step S1
Corresponds to the distribution timing determination procedure. In the case of time designation that does not require immediate notification (step S1; No), the process ends. This process corresponds to a distribution time standby procedure. If immediate notification is required (step S1; Ye
s), a notification request is sent to the information communication server 166 (step S2), and the information received from the data setup system business application 173, the notification function (cooperation command) 175, and the control function 174 is transferred to the information communication server 166. This step S2 corresponds to the immediate delivery procedure.

Next, it is determined whether the notification request is a notification request from the control function 174 (step S3). If the notification request is a notification request from the control function 174 (step S3; Yes), the process is output after outputting the business log (step S7). If the notification request is not a notification request from the control function 174 (step S3;
No), the delivery information management database 1 of the delivered information
The notification flag in 72 is updated to the notification of the broadcast function (step S4).

The status notification function (reception & immediate transmission) 169 is requested to transmit a “data setup completion notification” to the CSI server computer 12 (step S).
5). The notification flag in the distribution information management database 172 of the information requested to transmit the “data setup completion notification” is updated to the CSI server computer notified (step S6). The job log is output (step S7), and the process ends.

The data setup system business application 173, the notification function (cooperation command) 175 in FIG.
In the process of receiving the notification request from the control function 174 (step S1), the distribution information type (data type: form, business message, control information), cycle (branch number of distribution information type), creation date (year / month of business date) Day), the information of the business message document code is exchanged. Since the details of the distributable information are registered in advance in the distribution information management database 172, in step S1, the above-described information for searching for information to be notified is transferred.

When the deliverable information is a business message, the business message document code which is a search key of the business message table 176 is passed. If the deliverable information is other than the business message, the business message document code is not used.

In the process of requesting notification to the information communication server 166 (step S2 in FIG. 54), the distribution information type (data type: form, business message, control information), cycle (branch number of distribution information type), creation The date (year / month / day of the business date) and the information of the business message document code are exchanged. Since the details of the distributable information are registered in advance in the distribution information management database 172, the above information is transferred as information for searching for information to be notified. The business message document code is stored in the business message table 1 only when the distribution information type is business message.
Key information for searching 76 is passed.

In the process of requesting the status notification function (acceptance & immediate transmission) 169 to transmit a “data setup completion notification” to the CSI server computer 12 (step S5 in FIG. 54), the distribution information type (data type (Form), cycle of deliverable information, creation date of deliverable information (work date, date), sending member code (clearing member code (unused: all blank)), member code (non-clearing member code (not available) Use: all blank)), person in charge ID (unused:
All blanks), status identification to be notified (data setup completed, etc.), processed execution date and time, code: information of a business message document code for identifying a business message is transferred.

The process of receiving a notification request from the data setup system business application 173, the notification function (cooperation command) 175, and the control function 174 by the notification function (immediate notification) 167, and the process of requesting the information communication server 166 to notify (step S2), status notification function (reception &
The process of requesting the (immediate transmission) 169 to transmit a “data setup completion notification” to the CSI server computer 12 (step S5) is performed through the CORBA interface.

[0474] The notification function (time notification) 168 is a distribution function that specifies a publication time (settlement information) or a posting time to the member 2 from among the distributable information registered in the distribution information management database 172. The information is requested to be notified to the information communication server 166. Notification function (time notification) 168
Will be described with reference to the flowchart of FIG.

The notification function (time notification) 168
Is started at regular intervals (in units of 10 minutes), and performs the following processing. First, for a predetermined time, that is, 1
It is determined whether 0 minutes have elapsed (step S21). If 10 minutes have not elapsed since the previous processing (processing S21;
No), the process returns to step S21, and it is again determined whether 10 minutes have elapsed since the previous process (step S2).
1). That is, step S21 is repeated until ten minutes have elapsed from the previous processing.

If ten minutes have elapsed since the last processing (step S21; Yes), the distribution information management database 1
From 72, information that has reached the publication date and time (publication time or publication time) is searched (step S22). Next, distribution-enabled information is created from the searched information, and a notification request is made to the information communication server 166 (step S23). The notification flag in the distribution information management database 172 of the information requested to be notified is updated to the notification of the broadcast function (step S2).
4). Request the status notification function (acceptance & immediate transmission) 169 to transmit a “data setup completion notification” to the CSI server computer 12 (step S2)
5).

Then, the notification flag in the distribution information management database 172 of the information requested to be transmitted is updated to the CSI server computer notified (step S26). Thereafter, a business log is output (step S27). The number N of information obtained by searching from the distribution information management database 172 in step S22 and the number n of information for which a notification request to the information communication server 166 in step S23 and a transmission request of “data setup completion notification” in step S25 are made. It is determined whether the difference is 0 (step S28). When N−n is not 0, that is, when the notification request / transmission request has not been performed for the number of acquired information (step S28; No), a notification request process to the information communication server 166 is performed (step S23).

If N−n is 0, that is, if a notification request / transmission request has been made for the number of pieces of acquired information (step S28; Yes), the process ends. That is, steps S23 to S27 are performed for all the acquired information.

[0479] Deliverable information is created from the retrieved information,
Processing for requesting notification to the information communication server 166 (FIG. 5)
In step S23), the following information 1 to 4 are exchanged. Since the details of the distributable information are registered in advance in the distribution information management database 172, in step S1, information for searching for information to be notified, that is, distribution information type (form identification code, business message code), cycle The information on the business message document code and the business date, date, and date of the creation date is transferred. When the distribution information type is a business message, key information for searching the business message table 176 is passed to the business message document code. When the delivery information type is other than the business message, the business message document code is not used.

In the process of requesting the status notification function (reception & immediate transmission) 169 to send a “data setup completion notification” to the CSI server computer 12 (step S25 in FIG. 55), Information cycle, creation date of distributable information, sending member code (clearing member code (unused: all blank)), member code (non-clearing member code (unused: all blank)), person in charge ID ( Unused: all blanks), status identification to be notified (data setup completed, etc.), and information on the processed execution date / time business message document code is passed.

[0480] The distribution function creates information that can be distributed from the searched information of the notification function (time notification) 168, and sends the information communication server 166.
The process of requesting a notification to the CSI server computer 12 for the status notification function (acceptance & immediate transmission) 169 (step S23) and the status notification function (acceptance & immediate transmission) 169 (step S25)
Done through the interface.

The notification function (cooperation command) 175 receives the “business message” transmitted from the administrator of the stock exchange WAN system 1 and performs the notification function (immediate notification) 167.
This is a function of relaying to the notification function (time notification) 168 as distributable information. Notification function (cooperation command) 175
Performs the following processing. That is, first, a process of receiving a notification from the business message registration function 176 is performed.

Second, a process for registering the requested information in the distribution information management database 172 is performed. In the process of registering in the distribution information management database 172, information including a distribution information type, a cycle, a creation date, a distribution form, and a publication time is registered. Third, the date and time of publication are checked, and if it is an immediate transmission, a process of requesting a notification to the notification function (immediate notification) 167 is performed. If the posting time is specified, the process ends.

In the process of receiving the notification from the business message registration function 176, the information of the business message document code and the date and time of publication (including the immediate transmission / time designation) is exchanged. Since the details of the business message are registered in the business message table 176 in advance, in this process, the information is passed as information for searching for the business message information to be notified.

In the process of requesting the notification function (immediate notification) 167 for notification, the following information 1 to 4 are transferred. For details of the business message, see the business message table 176.
In this processing, as information for searching for the business message information to be notified, the distribution information type (business message code), cycle, creation date, date, business message document code (business message table (Key information for retrieving) is passed.

The process in which the notification function (cooperation command) 175 receives a notification from the business message table 176 is as follows.
This is done by invoking the shell. Notification function (cooperation command) 17
The process of requesting the notification function 167 to notify the notification function (immediate notification) 167 is performed through the CORBA interface.

[0487] The following information is available as the distributable information handled by the notification functions 167, 168, and 175. Domestic stock trading schedule (intra-auction transactions), Domestic stock trading schedule (other than off-auction and basket transactions), Domestic stock trading schedule (off-auction and basket transactions), Domestic stock trading schedule (total issues), Bond transaction sales schedule (intra-auction transactions), bond transaction sales schedule (excluding off-auction transactions, basket transactions), bond transaction sales schedule (off-auction transactions, basket transactions), bond transaction sales statements (total issues), Summary A (for reconciliation), Statement of Exercise Declaration and Allotment of Stock Options, Domestic Stock Trading Statement (List of Intra-Auction Transactions and Corrections), Domestic Stock Trading Statement (Non-trading and Correction List), Domestic Stock Trading Details Table (basket transaction / correction list), Bond transaction sales statement (list of intra-auction transactions / correction), Bond transaction sales statement (non-auction transaction / correction list), Bond transaction sales statement (basket transaction / correction list) Correct list), Summary B (corrected), Scheduled Settlement Volume by Brand, General Settlement Table (Contract Price), Settlement Settled Volume by Brand, General Settlement Table (Settlement Price / Market Clearance), Total Payment Settlement Calculation Schedule (planned) Amount / flash report), Receipt / Delivery appointment sheet related to settlement of base date, etc., Total payments calculation sheet (planned amount), additional payment notification, total payments payment calculation sheet (fixed amount), payment receipt notification, fail information Notification (after DEL), Fail information notification (CNS
After), buy-in information notification (initial), buy-in information notification (after DEL), buy-in information notification (after CNS), buy-in execution notification (previous day notice) (for buy-in billing members), buy-in execution notification (previous day notice) (buy-in cost Notification of buy-in (for members who pay), buy-in execution notice (previous day notice) (for all members: information to be distributed is the same for all members), notice of buy-in execution (for members requesting buy-in), notification of buy-in execution (for members who pay buy-in costs) Execution notification (for all members: information to be distributed is the same for all members), buy-in execution result notification (for buy-in requesting members), buy-in execution result notification (for buy-in cost bearing members), buy-in execution result notification (for seller members) ,
Notification of buy-in execution results (for all members), notification of buy-in invalidation, member's credit, trading / trade margin, previous day's collateral receipt / payment status table, previous day's collateral balance table, transaction margin, transaction margin,
A refundable table, a notice of securities in custody, a membership deposit,
Trading / trade margin, collateral posted on the previous day Real stockholder / collateral receipt balance notice, business message, operation control: business start,
Operation control: Operation end, operation control: emergency stop / other.

[0488] Each of these pieces of information is provided with an information-specific code. Among these, “notice” is a business message, “operation control: business start”, “operation control: business end”, “operation control: emergency stop / other” is control information, and the other is information on a form.

Next, status notification functions 169 and 171 and C
A description will be given of a message specification when communication is performed between the SI server computers 12. The status notification functions 169 and 171 use a status notification message and a status notification acknowledgment message.
The status notification message is a status notification message transmitted to the CSI server computer 12. The status notification receipt confirmation message is a control message, and is a receipt confirmation message of the transmitted status notification message.

[0490] The status notification message uses a file transmission type message format including a header section, a data section, and a footer section shown in FIG. The header section is not used for the data section, and consists only of the control section. The data section blocks a maximum of 580 records / block and transmits a plurality of records.

The details of the message item will be described. In the header section, the item names are message type, control type, data type, cycle number, creation date, and serial number. The message type is a type of a message such as a file transmission message. The control type is a distinction between transmission start / data transmission / transmission end. The cycle number is a cycle for each data type. It is reset on a daily basis, and shows the number of status notifications per day. The creation date is a business date (year, month, day) managed by the DVP server computer 4. The serial number of the header is “1”.

[0492] In the data section, the item names are message type, control type, data type, cycle number, creation date, serial number, number of data, exchange classification, destination member code, member code,
Notification completion date and time, form type, form cycle, form creation date, and status type. The serial numbers of the data section are “2 to n”. The number of data items is the number of blocked data items. Blocking is performed with the exchange classification, destination member code, member code, status type, notification completion date and time, form type, form cycle, form creation date, and state type as one. The exchange category indicates the category of the stock exchange 14.

[0493] The transmission destination member code is the member code of the member 2 who has completed the notification. If the status type is data setup completed, there is no destination member code. The member code is a code of the member 2 indicated by the contents of the form. If the status type is data setup completed, there is no member code. The notification completion date and time is the date and time (year, month, day, hour, minute, second) at which the corresponding situation type was executed, that is, the system date and time in the DVP server computer 4.

The form type is the type of the notified form.
The form cycle is a cycle of the form notified. The form creation date is the business date (year, month, and day) when the notified form was created, that is, the business date when the form data was created by the CSI server computer 12. The status type indicates whether data setup is completed or confirmation (download or browser reference) is completed. Completion of data setup is in units of information, and confirmation completion is in units of two members. Others are the same as the header part.

In the footer section, the item names are message type, control type, data type, cycle number, creation date, serial number, and number of data items. The serial number of the footer section is “n + 1”. The number of data items is the number of status notification information items transmitted in the data section. Others are the same as the header part.

The status notification functions 169 and 171 are composed of two functions, a status notification function (reception and immediate transmission) 169 and a status notification function (periodic transmission) 171. The status notification function (reception & immediate transmission) 169 is
Receives the status notification information of the member 2 requested by the user and registers it in the status notification management table 170 (process (11) in FIG. 53). Also, the requested status notification information is CSI
If the information needs to be transmitted immediately to the server computer 12, it is transmitted to the CSI server computer 12 (process (12) in FIG. 53).

The processing performed by the status notification function (acceptance & immediate transmission) 169 will be described with reference to the flowchart of FIG.
This will be described in more detail. When the processing flow starts, first, a status notification from the information communication server 166 is received (step S31). Next, the operation log collected for each ID is output (step S32). The ID unit is a unit for which the information communication server 166 requests a status notification. The requested information is registered in the status notification management table 170 (step S33).

[0498] Thereafter, it is determined whether or not the received information relates to payment information that requires immediate transmission (step S34). In this step S34, the presence or absence of the record of the corresponding member 2 (ID), the update of the notified status flag, the same member 2
Also check whether the notification has been made to If there is no need for immediate transmission (step S34; No),
The process ends. If the received information relates to payment information that needs to be transmitted immediately (step S34;
Yes), the transmission flag to the CSI server computer 12 is set to be notified (step S35).

[0499] Thereafter, a request is made to the CSI server computer 12 to transmit the payment information that requires immediate transmission (step S36). At this time, the transmission is performed only once at the first time, ie, the completion of the confirmation for each member 2 / information, that is, the completion of the download or the browser reference performed first. Also, at that time, CS
If there is an untransmitted portion of the I server computer 12, it is transmitted together. Next, a task log collected by two members, which is a unit of information to be notified to the CSI server computer 12, is output (step S37). Thereafter, the processing flow ends.

In the process of accepting the status notification from the information communication server 166 (step S31 in FIG. 57), the distribution information type of the distributable information (type of form or business message), the cycle of the distributable information, Date, sending member code (clearing member code), member code (non-clearing member code), person in charge, status identification to notify status identification (notification confirmation, download completion, browser reference), execution date and time processed, Delivery of a business message document code for identifying the business message is performed.

[0501] Information communication server 166 as status notification information
The information requested from is provided by the notification functions 167, 168, 17
5 is transmitted to the information communication server 166 as a basis. The business message document code is notified only when the information is a business message.

[0502] Regarding the settlement information required for immediate transmission, C
In the transmission request processing to the SI server computer 12 (step S36 in FIG. 57), the distribution information type of the distributable information, the cycle of the distributable information, the creation date of the distributable information, the transmission member code (clearing member code) ), The member code (non-clearing member code), and the information on the execution date and time of the notification of the status identification (data setup completed or confirmation completed) are performed. Among the information requested from the information communication server 166, the CSI server computer 1
The information transmitted to the member 2 is the first confirmation information on the member 2 side for the notified payment-related deliverable information.

The process of accepting the status notification from the information communication server 166 (step S31 in FIG. 57) is performed through the CORBA interface. The transmission request process (step S36 in FIG. 57) for the CSI server computer 12 for the payment information that requires immediate transmission is performed by calling the C function.

[0504] The status notification function (periodic transmission) 171 converts the status notification information that has not been transmitted to the CSI server computer 12 from the status notification information registered in the status notification management table 170, into the CSI server computer. (Step (13)). The processing performed by the status notification function (periodic transmission) 171 will be described in more detail with reference to the flowchart in FIG.

The status notification function (regular transmission) 171
It is started at a fixed interval (in units of 10 minutes) from on and performs the following processing. First, it is determined whether a predetermined time, that is, 10 minutes has elapsed from the previous processing (step S4).
1). If 10 minutes have not elapsed since the previous processing (S
41; No), the process returns to step S41, and it is again determined whether 10 minutes have elapsed since the previous processing (step S4).
1). That is, step S41 is repeated until 10 minutes have elapsed since the previous processing.

If ten minutes have elapsed since the last processing (step S41; Yes), the status notification management table 170
To obtain the untransmitted information of the CSI server computer 12 (step S42). Next, it is determined whether there is a plurality of pieces of acquired information (step S43). If the acquired information is plural (Step S43; Yes), the acquired information is blocked (Step S44), and the CSI
A request for information transmission is made to the server computer 12 (step S45). If the acquired information is not plural (step S43; No), a request for information transmission is made to the CSI server computer 12 (step S4).
5). The transmission target is all information that has not been notified to the CSI server computer 12.

After transmission is completed, CSI server computer 1
2 Set the transmitted flag to notified (step S4)
6). Next, the business log collected by two members, which is a unit of information to be notified to the CSI server computer 12, is
Output (Step S47). The number N of untransmitted information of the CSI server computer 12 retrieved from the status notification management table 170 in step S42 and the value of step S45
It is determined whether or not the difference from the number n of information items for which the information transmission request has been made to the CSI server computer 12 is 0 (step S48). At this time, if blocking is performed in step 44, n is calculated by adding the number of pieces of information included in the blocked information group. If N−n is not 0, that is, if the transmission request has not been made for the number of acquired information (step S48; No), a process of determining whether there is a plurality of acquired information is performed (step S43).
If N−n is 0, that is, if a transmission request is made for the number of acquired information (step S48; Yes),
The process ends. That is, steps S43 to S47 are performed for all the acquired information.

[0508] C by the status notification function (periodic transmission) 171
In the process of requesting transmission of information to the SI server computer 12 (step S45 in FIG. 58), the distribution information type of the distributable information, the cycle of the distributable information, the creation date of the distributable information, the transmission member code (clearing) The member code), the member code, the status identification to be notified (whether the data setup is completed or the confirmation is completed), and information on the processed execution date and time are transferred.

[0509] Among the information retrieved from the status notification management table 170, the information transmitted to the CSI server computer 12 is the first confirmation information on the member 2 side for the notified payment-related deliverable information. The status notification is made by the person in charge I
D, so if only the first confirmation information on the member 2 side is checked, the deliverable information notified at the same time will be
This is because it can be regarded as notified.

[0510] C by the status notification function (periodic transmission) 171
The process of requesting the transmission of information to the SI server computer 12 (step S45) is performed by calling a C common function provided by the CSI server computer 12 (MQ cooperation function).

The information handled by the status notification functions 170 and 171 requested by the information communication server 166 is status information for the following information. That is, domestic stock trading schedule (intra-auction transactions), domestic stock trading schedule (off-auction transactions,
Non-Basket Transactions), Domestic Stock Trading Statement (Off-Auction / Basket Trading), Domestic Stock Trading Statement (Total Brands), Bond Trading Statement (Intra-Auction Trading), Bond Trading Statement (Off-Auction Trading) Non-Basket Transactions), Bond Transactions (Off-auction / Basket Transactions), Bond Transactions (Total Brands), Summary A (for Verification), Stock Option Trading Exercise Declaration and Allocation Statement, Domestic Stock Trading Schedule (list of intra-auction transactions / corrections), Schedule of domestic stock trading (list of non-auction transactions / corrections), Schedule of domestic stock trading (list of basket transactions / corrections), Schedule of bond trading (trade / corrections of auction) ), Bond Transaction Details (List of Off-Auction Transactions / Correction), Bond Transaction Details (Basket Transaction / Correction List), Summary B (Corrected), Scheduled Settlement Volume, Overall Clearing Table ( Settlement amount), settlement settlement quantity by brand, general settlement table (settlement price / clearance margin), total receipt / payment calculation table (planned / flash report), receipt / transfer specification Payment Receipt Calculation Sheet (Scheduled Amount), Additional Payment Notification, Total Receipt Payment Calculation Sheet (Fixed Amount), Payment Receipt Notification, Fail Information Notification (after DEL), Fail Information Notification (CNS)
After), buy-in information notice (initial), buy-in information notice (after DEL), buy-in information notice (after CNS), buy-in execution notice (previous day notice) (for buy-in billing members), buy-in execution notice (previous day notice) (buy-in cost Buy-in execution notice (for the previous day) (for all members), buy-in execution notice (for the buy-in billing member), buy-in execution notice (for the buy-in cost bearer), buy-in execution notice (for all members), Buy-in execution result notification (for buy-in billing members), buy-in execution result notification (for buy-in cost bearing members), buy-in execution result notification (for seller members), buy-in execution result notification (for all members), buy-in invalidation notification,
Member Margin, Trading / Margin, Margin Receivable / Receiving Status Table, Margin Balance List, Trading Margin, Repatriable / Returnable Table, Securities Balance Notice, Member Margin, Trading・ Trading margin, collateral posted on the previous day Real stockholder / collateral receipt balance notice, business message, disconnection. Each of these pieces of information is provided with a code unique to the information.

[0512] The "additional payment notice" and the "total received / paid price calculation table (determined amount)" are immediate transmission information. Also,
The “business message” and the “disconnection” are not notified to the CSI server computer 12.

The information handled by the status notification functions 170 and 171 requested by the information communication server 166 includes the following status information 1 to 1 of the public information distributable information including any of the above-mentioned settlement information, business message, and operation control information. 5 That is, the situation information 1 is information indicating that the data setup of the public information has been completed. The transmission timing of the status information 1 is a time when the notification request to the information communication function (broadcast notification function) 164 is completed.

[0514] Status information 2: Information indicating that the notification of the distributable information has been completed, that is, information indicating that the notification has been displayed on the distribution status screen of the information communication function (broadcast notification function) 164. Status information 3: Regarding the public information that has notified the distributable information, this is information indicating that the download of the CSV file has been completed. Situation information 4: Information indicating that the browser has referred to the public information that has notified the distributable information.

[0515] Status information 5: Information indicating that the notification of the business message has been completed among the distributable information, that is, information indicating that the information communication function (broadcast notification function) 164 has been displayed on the screen of the distribution status. is there. Among the status information 1 to 5, the “confirmation completed” information to be notified to the CSI server computer 12 is any one of the status information 3 and 4 that has been notified earlier.

When communicating between the status notification functions 168 and 169 and the CSI server computer 12, the status notification function uses a status notification message transmitted to the CSI server computer 12 and a message for confirming receipt of the transmitted status notification message. A status notification receipt confirmation message as a certain control message is used.

The distribution information management database 172 shown in FIG.
Will be described. Distribution information management database 172
Is a database for storing information to be notified to the member 2, and is composed of two tables, a distribution information table 172a and a distribution information detail table 172b.

[0518] The distribution information table 172a includes a distribution information type, a cycle, a creation date (business date), a reference date, a reference date category, a form date, a distribution form, a release date and time, a form pattern, a notification status, a business message document code, and a registration. It consists of date and time items. The distribution information type indicates a form or a business message. The creation date (business date) is the date. The reference date item has no data in the case of a business message.
The reference date category is a trade date, a settlement date, and other categories.
There is no data for business messages.

[0519] The form date is the date, and there is no data in the case of a business message. The distribution form is "provide information by member", "provide information by member (no data available)",
Indicates "Providing the same information to all members". There is no data for business messages. The publication date and time indicates year, month, day, hour, minute, and second, and the case of immediate transmission of a business message is identified.
The initial value of the form pattern is NULL. Single form,
Indicates the form of continuous form, and there is no data for business message.

[0520] The notification status is classified into non-notification, notification completion of broadcast notification, notification completion of data setup completion notification (to the status notification function), and notification incomplete (notification processing failure, broadcast notification error, etc.). Is shown. The initial value is “not notified”.
The business message document code contains data only in the case of a business message. This is a key item to the business message table. The initial value is NULL. The registration date and time is date data, and is a record creation date (year / month / day / hour / minute / second).

[0521] The distribution information detail table 172b includes distribution information type, cycle, creation date (business date), transmission member code, member code, clearing member code, distribution information presence / absence flag, CSV storage destination directory, CSV file name, C
SV file size and registration date and time.

[0522] The transmission member code is a code of the member 2 who notifies data. The member code is a code of the member 2 indicated by the contents of the form. The clearing member code is a code of the clearing member for the content of the data. The distribution information presence / absence flag identifies presence / absence of data to be notified. The registration date and time
Date data, record creation date (year / month / day / hour / minute / second)
It is.

In the present embodiment, the following correspondence method is adopted for the clearing member system. In the data transmitted from the CSI server computer 12, in addition to the member code of the data, a member code of a clearing member is also provided. DB with member code and member code of clearing member
When the DB is accessed from the WWW browser 11b and the member code to which the accessing user belongs hits the member code in the data, or when the clearing member code in the data hits, the hit data is extracted. And display. If the delivery information is a business message, no record is generated in the delivery information detail table 172b.

The status notification management database 170 shown in FIG.
Will be described. Status notification management database 170
Is a database for storing a processing status to be notified to the CSI server computer 12, and includes a status notification management table.

[0525] The status notification management table 170 includes status status, distribution information type, cycle, creation date, transmission member code, member code, CSI server computer 12 transmission status flag, notification confirmation flag, notification confirmation date, download flag, download date and time. , Browser reference flag, browser reference date and time, business message document code, CSI server computer 12 transmission cycle number, CSI server computer 12 transmission date, and data setup completion date and time.

The status category identifies data setup and non-data setup. The creation date is the business date (year, month, and day) when the form was created in the case of a form, and the issue date (year, month, and day) in the case of a business message. Sending member code,
The member code is a dummy set when the status category is data setup.

The transmission status flag of the CSI server computer 12 is “not transmitted”, “transmitted”, “CSI server computer 1”.
(2) Normal reception end, CSI server computer 12 reception abnormal end is identified. The control function updates the reception completion of the CSI server computer 12 and the abnormal termination of the reception of the CSI server computer 12 in response to the reception completion message from the CSI server computer 12.

[0528] The notification confirmation flag identifies whether confirmation has not been performed or has been confirmed. The notification confirmation date and time is date data, and is the date and time (year / month / day / hour / minute / second) when the notification was confirmed on the member 2 side. The download flag identifies whether the file has not been downloaded or has been downloaded. The download date and time is date data, and Member 2
It is the date and time (year, month, day, hour, minute, second) downloaded on the side.
The browser reference flag identifies browser reference not yet performed and browser reference completed. The browser reference date and time is date data, and is the date and time (year / month / day / hour / minute / second) when the browser was referenced on the member 2 side.

The business message document code is a search key for the business message table 176. The transmission cycle number of the CSI server computer 12 is C as the status notification.
This is a cycle when the data is transmitted to the SI server computer 12. The transmission date of the CSI server computer 12 is a business date (year, month, day) when the status notification is transmitted to the CSI server computer 12. The data setup completion date and time is date data, and is the date and time (year / month / day / hour / minute / second) when the data setup completion is notified to the member 2.

Next, the relationship between the notification task function and each function in the DVP server computer 4 will be described. Figure 59
FIG. 6 is a block diagram showing a flow of a request to transmit the deliverable information to the member 2 (client computer 9) side. The notification functions (immediate notification, time notification) 167 and 168 make a notification request to the information communication server 166 to transmit the deliverable information to the member side terminal 45 (process (4a)).

[0531] Notification function (immediate notification, time notification) 167,
The information to be passed when making a notification request from the 168 to the information communication server 166 is only information necessary for searching the distribution information management database 172 and the business message table 176. The information communication server 166 searches the distribution information management database 172 for the detailed information necessary for displaying the transmission target member 2 and the member side terminal 45 using the passed information as a key, and acquires the detailed information.

FIG. 60 is a block diagram showing a flow of accepting the processing status of the member 2 side. The status notification function (acceptance & immediate transmission) 169 receives status notification information from the information communication server 166 in order to manage the processing status of the member 2 in the DVP server computer 4 and transmit it to the CSI server computer 12. (Process (10)).

The information received from the information communication function 164 by the status notification function (reception & immediate transmission) 169 is the information communication function 1
This relates to the status of the member 2 with respect to the distributable information sent from 69. Other information is managed by the information notification function 169 as needed. Also,
The notification confirmation made by the information communication server computer 166 is
Only the management in the DVP server computer 4 is performed without notifying the CSI server computer 12.

Next, the relationship with the business message registration function will be described. FIG. 61 is a block diagram showing a flow of receiving a business message notification request. The notification function (cooperation command) 175 requests the notification function 167 to transmit the business message requested by the business message registration function 180 to the member 2 side.

[0535] The block diagram in Fig. 61 will be described. DVP
When the business message is registered by the business message registration function 180 of the terminal 178 of the server computer 4 operator, the business message registration function 180 registers the business message in the business message table 176 (process (7a)). . The business message registration function 180
At the same time, the notification function (cooperation command) 175 is called (process (7b)).

When the business message registration function 180 calls the notification function (cooperation command) 175 (processing (7
b)) If the business message is of the immediate transmission type, the notification function (cooperation command) 175 requests the notification function (immediate transmission) 167 to notify the business message (process (9)). Here, the determination as to whether or not the notification is of the immediate transmission type, that is, whether or not to notify immediately, is performed by the notification function (cooperation command) 175 based on the posting time at which the business message is passed from the business message registration function 180. .

Also, a notification function (cooperation command) 175
Registers the information received from the business message registration function in the distribution information management database 172 (process (8)). When the notification function (immediate notification) 167 is requested to notify the business message (process (9)), the notification function (167) requests the information communication server 166 to notify the requested distributable information (process (4a)). If received, a "data setup completion notification" is transmitted to the CSI server computer 12 in information units via the status notification function (reception & immediate transmission) 169 (processing (4b)). At this time, the notification status flag in the distribution information table 172 is updated to the completion of the notification to the broadcast notification. When a business message is registered in the business message registration table 176 (process (7a)), the information communication server 166 acquires detailed information necessary for display on the information communication client 163 side from the business message table 176 ( Processing (6
d)).

The notification function (time notification) 168 checks the distribution information table 172 at regular intervals (in units of 10 minutes), extracts information that has reached the posting time of the business message (processing (5a)), and To the communication information server 166.
(Process (5b)). This processing (5
In b), even if a plurality of pieces of distributable information exist at the same time, a transmission request to the information communication server 166 is made on a case-by-case basis.

Next, the relationship with the data setup system business application will be described. FIG. 62 is a block diagram illustrating a flow of accepting a transmission request for a data setup completion notification of payment information.

[0540] Notification function (immediate notification, time notification) 167
168 requests the information communication server 166 to transmit a data setup completion notification of the payment information requested by the data setup business application 173 to the client computer 9 (processing (4)
a), (5b)). Notification function (immediate notification, time notification) 1
67 and 168 indicate the status notification function (acceptance & immediate transmission) 16 when the notification request to the information communication server 166 is completed.
9, a "data setup completion notification" is transmitted to the CSI server computer 12 (processing (1
2)).

At this time, even if a plurality of pieces of distributable information exist at the same time, a request to the information communication server is made on a case-by-case basis. Data setup business application 17
3 performs a process of requesting a notification to the notification function (immediate transmission) 167 when the payment information is the immediate transmission type (processing). At this time, the business application 173 determines whether to notify immediately. Further, even in the case of the time-designated information, if the published time is past the current time, the notification request (immediate notification) 167 is requested to be transmitted.

After the data setup process (process (1)) is completed normally, the data setup system business application 173 stores the data setup process (process 2) in the distribution information table (member 2 unit) 172.
A process for registering information necessary for notification is performed (process (2)). The information communication server 166 acquires the detailed information necessary for the display on the information communication client 163 side from the distribution information database 172 by the information communication server 166 (process (6a)). The member 2 to be transmitted is searched by referring to the distribution management database 172 based on the distribution available information requested from the notification functions 167 and 168. The notification function (time designation) 168 checks the distribution information table 172 at regular intervals (in units of 10 minutes) (processing (5a)), and requests the communication information server 166 to notify the distributable information of the distribution time ( Processing (5b)).

Next, the relationship with the control function will be described. FIG. 63 is a block diagram showing a flow of accepting a transmission request for operation control information. The operation control information requested by the control function 174 is requested to be transmitted to the notification function (immediate notification) 167 to notify the information communication server 166 (process (14)). This operation control information is information used inside the information communication function (broadcast notification function) 164,
It is not displayed on the side client screen. The operation control information notified here is information of an immediate notification type, and is not managed in the distribution management table.

Next, the relationship with the MQ cooperation function will be described. FIG. 64 is a block diagram illustrating a flow of a status notification information transmission request. Status notification function (reception & immediate transmission,
The periodic transmissions 169 and 171 receive the status notification information in user ID units from the information communication server 166 (process (10)). The status notification function (reception & immediate transmission, periodic transmission) 169, 171 requests the MQ cooperation API 181 to transmit this status notification information (processing (16a) (16)
b) (16c)).

[0545] At this time, the status notification function (acceptance & immediate transmission) 169 transmits a data setup completion notification for the information of one information unit (for one case) (processing (16
a)). In addition, about the information (for one case) of two members,
A confirmation completion notification (download completion or browser reference completion) is transmitted (process (16b)). Further, the status notification function (periodic transmission) 171 transmits a confirmation completion notification (download completion or browser reference completion) for the information of the two units of the member that has been blocked and made into a plurality of cases (processing (16c)). The MQ cooperation API 181 transmits the status notification information to the CSI server computer 12 (process (17)).

Next, the relationship with the log function will be described. FIG. 65A is a block diagram illustrating a flow of collecting a task log of the notification function. In the notification functions 167 and 168,
The notification function (immediate notification) 167, the notification function (time notification) 168, and the distributable information at the time of requesting the information communication server 166 are collected as a business log and transmitted to the log management function (API) 182 (processing (18a )). Then, the log management function (API) 182
7 and 168, the distributable information at the time of requesting the information communication server 166 is registered in the log database 77 (processing (18b)).

FIG. 65 (B) is a block diagram showing the flow of collecting the business log of the status notification function. Status notification function 16
In steps 9 and 171, the distributable information at the time requested by the information communication server 166 is collected as a business log for each ID, and transmitted to the log management function (API) 182 (processing (19a)).

In the status notification functions 169 and 171,
The status notification function (acceptance & immediate transmission) 169 and the status notification function (regular transmission) 171 collect the status notification information at the time of requesting the MQ cooperation API 181 as a business log for each two members, and a log management function (API) 182 (processing (19a)). And log management function (API)
182, the distributable information at the time of requesting the information communication server 166 received from the status notification functions 169 and 171,
It is registered in the log database 77 (process (19b)).

FIGS. 66 to 76 show the entry processing flow. In each figure, the process enclosed by a thick line is an entry-specific process. The storage device of the DVP server computer 4, for example, the table design of the HDD 24 will be described. The DVP server computer 4 has a storage device in which the following tables are stored. The buy-in request table 230-01 manages the status of the claim-in declaration / cancellation for each member 2.

The buy-in order table 230-02 manages the buy-in order application / cancellation status for each member 2. The buy-in request withdrawal table 230-03 manages the status of the buy-in request withdrawal / cancellation for each member 2. The buy-in billing target table 230-04 manages the brand code of the buy-in billing target brand, the maximum billing quantity, the scheduled buy-in execution date, and the like for each member 2. It is re-created from the buy-in claim report entry information received from the CSI server computer 12. (All past data will be deleted.) Refer to a buy-in claim declaration. Brands that have not been canceled and have been declared for buy-in (“provisional receipt”, “real receipt”) disable the new declaration flag.

The buy-in order target issue table 230-0
Reference numeral 5 manages the issue code of the issue target buy-in order and the maximum order quantity. It is created from the buy-in order application entry information received from the CSI server computer 12.
(All past data will be deleted.) Refer to a buy-in order application.

[0555] Buy-in order target member table 230-0
No. 6 is created from the buy-in order application entry information received from the CSI server computer 12 which manages the member code of the member 2 who can make a buy-in order. (All past data will be deleted.) Refer to a buy-in order application.

[0556] Buy-in request withdrawal target table 230-0
Reference numeral 7 manages bill-in withdrawal target bills (brand code, billing date, bill withdrawable quantity) for each member 2. It is created from the buy-in withdrawal withdrawal entry information received from the CSI server computer 12. (All past data will be deleted.) Refer to in case of withdrawal declaration / change of buy-in request. Brands that have not been canceled and have been withdrawn (“provisional receipt”, “final receipt”) have their new filing flag disabled.

FIGS. 66 to 68 show the buy-in request processing flow. In the flow of FIG. 66, when the CSI server computer 12 performs the buy-in billing target brand information notification processing 227-01, the DVP server computer 4
Is the buy-in claim report entry information (X date, ~ 12: 3
0) is received, and in the buy-in bill report entry information download processing 227-02, message reception / transmission, billing target information management and operation management are performed, and buy-in bill report entry information download processing is performed. The billing target information is registered in the buy-in billing target table 230-04, and the operation management information is registered in the operation management table 230-08. As the operation management, for example, when a buy-in request is selected on the fail management tab screen outside business hours, the buy-in request status reception screen is displayed as a read-only screen, and the bill declaration button is not displayed, so that input cannot be performed. Perform operation management. The CSI server computer 12 is a DVP
Entry control reception processing 227-for receiving a buy-in request declaration entry information reception confirmation from server computer 4
Perform 03.

[0555] When the CSI server computer 12 performs the entry control transmission process 227-04, the DVP server computer 4 receives the buy-in request report acceptance start notice (X date,
12:30), a message reception / transmission and a process of registering information in the numbering management table 230-09 are performed in a process 227-05 of the control message monitoring / receiving application. After receiving the confirmation to start accepting the buy-in
The SI server computer 12 receives the entry control in a process 227-06.

In the flow of FIG. 67, the client computer 9 performs the buy-in request processing 227-07, and
The P server computer 4 performs a buy-in billing target brand information search process 227-08. In other words, when the client computer 9 transmits the buy-in billing target brand information request in the buy-in request processing 227-07 to request acquisition of the buy-in target brand information, the DVP server computer 4
Is a buy-in invoice target issue information search process 227-08 in the buy-in invoice target table 230-04, the issue master 23
0-10, information is acquired from the operation management table 230-08, and the buy-in billing target brand information is notified. The client computer 9 completes the acquisition of the buy-in billing target brand information.

The client computer 9 performs a buy-in request process 227-07, and the DVP server computer 4 performs a buy-in request report process 227-09.
That is, when the client computer 9 transmits a buy-in request report in the buy-in request process 227-07, the DV
The P server computer 4 performs the buy-in request report processing 227
In step -09, information is acquired from the operation management table 230-08 and the numbering management table 230-09, and declaration information management, numbering / version number management, message transmission, and upload result notification processing are performed. The client computer 9 receives the bill report upload notification and completes the buy-in bill report.

When the DVP server computer 4 performs the buy-in request report processing 227-09, the CSI server computer 12 that has received the buy-in request report performs the buy-in request reception processing 227-10. The DVP server computer 4 receives the buy-in bill report reception confirmation, and receives the message in the buy-in bill report reception confirmation processing 227-11.
Version number management and report information management are performed, and a buy-in billing table 230-01 and a buy-in billing target table 230-04 are performed.
Register the information to.

In the flow shown in FIG. 68, the CSI server computer 12 notifies the buy-in request report completion notice (X day, 1
4:30) Entry control transmission processing 227-1
2, the DVP server computer 4 performs message reception / transmission and operation management for registering information in the operation management table 230-08 in the process 227-13 of the control message monitoring / receiving application. Next, the CSI server computer 12 receives the buy-in request acceptance completion confirmation information from the DVP server computer 4, and performs the entry control reception process 227-14.

Also, the DVP server computer 4 transmits the buy-in billing report entry end information and performs the billing entry end message creation / storage, message transmission, and upload result notification in the buy-in billing report processing 227-15. The computer 12 performs a buy-in request acceptance process 227-16. Next, the DVP server computer 4 receives the acknowledgment of the completion of the buy-in request declaration entry from the CSI server computer 12, and receives the message in the buy-in request declaration reception confirmation processing 227-17.
Performs declaration information management processing.

FIG. 69 to FIG. 71 are flowcharts showing the buy-in order processing flow. In the flow of FIG. 69, the CSI server computer 12 transmits the buy-in order application entry information (X
+3 days, up to 15:00) to perform the buy-in order target brand information notification processing 228-01, the DVP server computer 4 receives the message reception / transmission and the order target information in the buy-in order application entry information download processing 228-02. Performs management and operation management processing. Next, the CSI server computer 12 receives the buy-in order application entry information reception confirmation (“file transmission” type message reception confirmation) from the DVP server computer 4 and performs entry control reception processing 228-03.

[0562] When the CSI server computer 12 transmits the buy-in order application reception start (X + 3rd, 15:00) and performs the entry control transmission processing 228-04, the client computer 9 executes the control message monitoring / reception application processing 228-05. Performs message reception / transmission and operation management processing. As operation management, for example, when a buy-in order is selected on the fail management tab screen outside business hours, the buy-in order status reception screen is displayed as a read-only screen, and the order application button etc. is not displayed and input cannot be performed. Perform operation management. Next, the CSI server computer 12 receives the confirmation to start accepting the buy-in order application, and performs the entry control reception process 228-06.

In the flow of FIG. 70, the client computer 9 performs the buy-in order processing 228-07, and
The P server computer 4 performs a buy-in order target brand information search process 228-08. That is, when the client computer 9 transmits a buy-in order target issue information request in the buy-in order processing 228-07 and requests acquisition of the buy-in order target issue information, the DVP server computer 4
Is a buy-in order target issue information search process 228-08 in a buy-in order target issue table 230-05, a buy-in order target member table 230-06, and a brand master 230-.
The information is acquired from 10 and the stock information for the buy-in order is issued. The client computer 9 receives the buy-in order target issue information and completes the acquisition of the buy-in order target issue information.

[0564] The client computer 9 performs the buy-in order processing 228-07, and the DVP server computer 4 performs the buy-in order application processing 228-09.
That is, when the client computer 9 sends an order application and makes a buy-in order application in the buy-in order processing 228-07, the DVP server computer 4 makes an operation management table 230-0 in the buy-in order application processing 228-09.
8. Acquire information from the numbering management table 230-09 and the buy-in order table 230-02 and perform application information management, numbering / version number management, message transmission, and upload result notification processing. The client computer 9 receives the buy-in order application upload notification and completes the buy-in order application.

When the DVP server computer 4 performs the buy-in order application process 228-09, the CSI server computer 12 receives the buy-in order application information and performs the buy-in order reception process 228-10. The DVP server computer 4 receives the buy-in order application reception confirmation, receives the message, manages the version number, and manages the application information in the buy-in order application reception confirmation processing 228-11, and registers the information in the buy-in order table 230-02. .

In the flow of FIG. 71, the end of buy-in order application reception (X + 3rd, 15:30) is transmitted, and the CSI server computer 12 transmits the entry control transmission processing 228-1.
2, the DVP server computer 4 performs message reception / transmission and operation management for registering information in the operation management table 230-08 in the process 228-13 of the control message monitoring / receiving application. Next, the CSI server computer 12 receives the buy-in order application acceptance completion confirmation information and performs entry control reception processing 228-14.

Also, the DVP server computer 4 transmits the buy-in order application entry end information, and performs the order application entry end message creation / storage, message transmission, and upload result notification in the buy-in order application processing 228-15. 12 performs buy-in order reception processing 228-16. DVP server computer 4
Receives the buy-in order application entry end reception confirmation information and performs message reception and application information management processing in the buy-in order application reception confirmation processing 228-17.

FIG. 72 to FIG. 74 are diagrams showing the buy-in request withdrawal processing flow. In the flow of FIG. 72, when the CSI server computer 12 transmits the buy-in request withdrawal entry entry information (X + 4th, up to 9:00) and performs the buy-in request withdrawal target brand information notification processing 229-01, the DV
The P server computer 4 performs message reception / transmission, withdrawal information management, and operation management in the buy-in request withdrawal declaration entry information download processing 229-02. The information is registered in the buy-in request withdrawal target table 230-07 and the operation management table 230-08. The CSI server computer 12 receives the buy-in request withdrawal declaration entry information reception confirmation (“file transmission” type message reception confirmation) and performs entry control reception processing 229-03.

When the CSI server computer 12 transmits the buy-in request withdrawal report acceptance start information (X + 4, 9:00) and performs the entry control transmission processing 229-04, D
In the process 229-05 of the control message monitoring / reception application, the VP server computer 4 receives the buy-in request withdrawal report acceptance start confirmation information and receives / transmits the message.
Perform operation management. The information is registered in the numbering management table 230-09. The CSI server computer 12 performs an entry control reception process 229-06.

In the flow of FIG. 73, the client computer 9 performs a buy-in request withdrawal process 229-07,
The DVP server computer 4 performs a buy-in request withdrawal target issue list search process 229-08. That is, the client computer 9 executes the buy-in request withdrawal processing 229-0.
In step 7, when a buy-in withdrawal target issue list request is transmitted and acquisition of buy-in request withdrawal target list information is requested, D
The VP server computer 4 obtains information from the buy-in request withdrawal target table 230-07, the brand master 230-10, and the operation management table 230-08 in the buy-in request withdrawal target brand list search processing 229-08, and withdraws the buy-in request. Notify the target issue list. The client computer 9 completes the acquisition of the buy-in request withdrawal target list.

When the client computer 9 performs the buy-in request withdrawal processing 229-07, the DVP server computer 4 performs the buy-in request withdrawal target charge information search processing 229-09. In other words, when the client computer 9 sends a buy-in request withdrawal target billing information request and requests acquisition of the withdrawal target list information of the selected brand in the buy-in request withdrawal processing 229-07, the DVP server computer 4 Withdrawal target billing information search processing 2
Buy-in request withdrawal target table 230-0 at 29-09
7, brand master 230-10, operation management table 230
Information is acquired from -08 to acquire / notify the bill-in withdrawal target billing information. The client computer 9 completes the acquisition of the withdrawal target bill list information of the selected brand.

When the client computer 9 performs the buy-in request withdrawal processing 229-07, the DVP server computer 4 executes the buy-in request withdrawal declaration processing 229-1.
Perform 0. That is, the client computer 9 transmits a buy-in request withdrawal report and executes the buy-in request withdrawal processing 22
When the buy-in request withdrawal declaration is made in 9-07, the DVP server computer 4 executes the buy-in request withdrawal declaration processing 229-
In step 10, information is acquired from the operation management table 230-08 and the numbering management table 230-09, and declaration information management, numbering / version number management, message transmission, and upload result notification processing are performed. The client computer 9 receives the buy-in request withdrawal report upload notification and completes the buy-in request withdrawal report.

The DVP server computer 4 transmits a buy-in request withdrawal report and performs a buy-in request withdrawal report processing 229.
After performing -10, the CSI server computer 12 performs a buy-in request withdrawal receiving process 229-11. The DVP server computer 4 receives the buy-in request withdrawal report acceptance confirmation information and receives the buy-in request withdrawal report acceptance confirmation processing 229.
At -12, message reception, version number management, and declaration information management are performed, and information is registered in the buy-in request withdrawal table 230-01 and the buy-in request withdrawal target table 230-04.

In the flow shown in FIG. 74, the CSI server computer 12 sends the buy-in request withdrawal report acceptance completion notice (X +
4th, 12:00) to transmit the entry control transmission processing 2
When 29-13 is performed, the DVP server computer 4 performs message reception / transmission and operation management in processing 229-14 of the control message monitoring / receiving application. The information is registered in the operation management table 230-08. Next, the CSI server computer 12 is connected to the DVP server computer 4.
Receives buy-in claim withdrawal acceptance acceptance confirmation information from
An entry control reception process 229-15 is performed.

The DVP server computer 4 transmits the buy-in request withdrawal entry entry end information, and in the buy-in withdrawal withdrawal declaration processing 229-16, creates / stores the message with the end of the request withdrawal entry entry, sends the message, and notifies the upload result. Is performed, the CSI server computer 12 performs a buy-in request withdrawal receiving process 229-17. Then
The DVP server computer 4 receives the buy-in request withdrawal report entry end acknowledgment and performs message reception and report information management processing in the buy-in request withdrawal report acceptance confirmation processing 229-18.

FIG. 75 and FIG. 76 are flowcharts showing the processing flow for confirming each buy-in reception status. In the flow of FIG. 75, when the client computer 9 transmits the buy-in request reception status request information and makes a buy-in request reception status request in the buy-in request process 229-19, the DVP server computer 4 executes the buy-in request reception status search process 229-20. Performs request reception status search and client display data creation.
At this time, the authentication database 230-12 is searched to determine whether the buy-in request reception status request has been made using a user ID having authority to view the buy-in request reception status. The authentication database 230-12 stores information on authentication including authority. The client computer 9 receives the buy-in request reception status information from the DVP server computer 4 and performs a buy-in request reception status display.

When the client computer 9 transmits a buy-in order reception status request in the buy-in order processing 229-21 and makes a buy-in order reception status request, the DVP
The server computer 4 performs order reception status search and client display data creation in a buy-in order reception status search process 229-22. The client computer 9 is a DV
The buy-in order reception status information is received from the P server computer 4 to display the buy-in order reception status.

In the flow of FIG. 76, when the client computer 9 sends a buy-in request withdrawal acceptance status request in the buy-in request withdrawal processing 229-23 to make a buy-in request withdrawal acceptance status request, the DVP server computer 4 In the request withdrawal reception status search process 229-24, a request withdrawal reception status search and client display data creation are performed.
At this time, the buy-in request withdrawal reception status request is a user ID having authority to browse the buy-in request withdrawal reception status.
Is performed using the authentication database 230-12.
Search and judge. This authentication database 230-1
2 stores information on authentication including authority.
The client computer 9 receives the buy-in request withdrawal reception status information from the DVP server computer 4 and displays the buy-in request withdrawal reception status.

Next, an outline of the log management function will be described. The log management can be used from each processing unit 183 on the DVP server computer 4. The types of logs are roughly classified into two types: business logs and debug logs. Regarding the management of each log, the business log is managed by a table 77b, and the debug log is managed by a file 77a. Information required for log management can be switched at system startup.

[0580] The business log is a log that records the exchange between the member 2 and each processing unit 183 in the DVP server computer 4. It outputs all normal and abnormal information.
The information is recorded in the operation log table 77b, and the information is output to the console 188. The debug log is a log mainly used at the time of development and recording a detailed data flow in processing. The information is recorded in the debug log file 77a, and the information is also output to the console 188.
During production operation, only error logs are collected. The path for storing the debug log file is stored in an environment variable.

FIG. 77 shows a configuration related to log management. The DVP server computer 4 has a notification function 167
(168, 175), entry function 184, control function 1
74 (177), MQ coordination function 181, processing unit 183 including data setup business application 173
A debug log output function 186 that performs predetermined processing on a log input from the processing unit and outputs the processed log, a log management function 187 having a business log output function, and a debug that records a debug log from the debug log output function 186. A log file 77a, a business log table 77b for recording a business log from the business log output function 187, and a console 188 for outputting a log from the debug log output function 186 and the business log output function 187 are provided.

[0582] The log acquisition target functions are the entry function 184, the control function 174 (177), and the MQ cooperation function 1.
81, data setup business application 17
3. Notification function 167 (168, 175). Acquire business logs and debug logs (only error information) for all functions. Regarding the entry function 184,
At the time of execution of the entry function, the member ID and the contents of the request are recorded and managed. The control function 174 (177) records and manages information on the start and end of work. For the MQ cooperation function 181, the CSI server computer 12 and the D
It records and manages information about exchanges between the VP server computers 4 and the date and time. As for the data setup system business application 173, database storage, CS
It records and manages the date and time when the V file and the like were created, data, and the like. The notification function 167 (168, 175) records and manages information notified at the time of various notifications, a notification target person, date and time, and the like.

FIG. 78 is a block diagram showing a business flow in a normal system, that is, when there is no error. With reference to FIG. 78, the flow of the normal business will be described. First, D
The processing unit 183 of the VP server computer 4 performs database connection processing (processing 191.00) as preprocessing as first business processing. After that, other preprocessing is performed as needed.

Thereafter, the present processing is performed. In this processing, the business 1 processing (processing 191.02) and the business 2 processing (processing 19
1.04). Thereafter, post-processing is performed (processing 19).
1.10). The transaction management of this process will be described. After starting a transaction (processing 191.0
1), perform job 1 (process 191.02). Next, a debug log is output by the debug log output function to the debug log file 77a and the console 188 (process 191.03). Next, the business 2 processing is performed (processing 19).
1.04). Thereafter, the transaction ends (processing 191.05).

Then, transaction log output transaction management is performed. After the transaction of the business log output is started (process 191.06), the business log output processing is performed by the business log output function 187, and the business log table 77 is executed.
b, output to the console 188 (processing 191.0
7). Then, the transaction for outputting the business log ends (processing 191.08).

FIG. 79 is a block diagram showing the flow of business when an abnormal system, that is, an error occurs. With reference to FIG. 79, the flow of the abnormal business will be described. First, D
The processing unit 183 of the VP server computer 4 performs database connection processing (processing 192.00) as preprocessing as first business processing. After that, other preprocessing is performed as needed. Thereafter, the present processing is performed. In this process,
Business 1 processing (Process 192.02), Business 2 processing (Process 1
92.10). Thereafter, post-processing is performed (processing 19).
2.11).

[0587] The transaction management of this processing will be described. After starting a transaction (processing 192.0
1), perform job 1 (process 192.02); If no error has occurred, the business log is output to the business log table 77b and the console 188 by the business log output function (process 192.04), and then the transaction is terminated by the commit process (process 192.). 0
5).

Next, when an error has occurred (process 192.03), the transaction is ended by the Rollback process (process 192.06). Thereafter, the business log output function reissues the transaction again (process 192.07), and the output process of the business log is performed.
The job log table 77b is output to the console 188 (process 192.08). Next, the transaction is terminated by a commit process (process 192.0).
9). As described above, in the process of FIG. 79, when an error log is output when an error occurs, the current transaction is temporarily terminated, the transaction is reissued, and the error log is output.

The log record format of the business log will be described. The business log record includes items of log type, function name, application name, data type, cycle, creation date (business date), member code, user ID, log creation date, message code, and comment.

[0590] The log type is information (inf
o), warning (war) and error (err) are identified. The function names are entry, control, MQ cooperation, data setup, and notification. The application name is the name of the application that output the log. The log creation date is composed of date data and is the date and time (month, date, minute, second) at which the log was output. The message code is a code obtained from the message table when displaying a fixed message. The debug log file includes items of a log type, an application name, a log creation date, and a comment.

[0591] The message table for storing the business message includes a message code for identifying a fixed message, and a message item.

The log function will be described. The log output function (business log) is a function used when a business log is obtained. In the function, the log is written to a business log table and also output to a console. The return value is the execution result (int) (normal or error), and the argument is the same item (all in) as in the business log table except for the creation date.

The log output function (debug log)
This function is used as a method for investigating the cause when a failure occurs during development. During operation, only error logs are collected. The log type acquired by the argument is compared with the output level set in the environment variable, and if the type is applicable, writing to the debug log file and console output are performed.
The return value is the execution result (int) (whether normal or error), and the arguments are the same items (all in) and the application type as the debug log file format except for the creation date.

Next, the DVP server computer 4 and C
The range of cooperation with the SI server computer 12 will be described. FIG. 80 shows the DVP server computer 4 and the CS
The outline of the I server computer 12 is shown. The process of cooperating with the CSI server computer 12 of the DVP server computer 4 is a process within the DVP server computer 4 that is started upon transmission / reception of a message between the DVP server computer 4 and the CSI server computer 12 and reception from the CSI server computer 12 ( Database development 231, C
SV creation 232).

From 4:00 am at the time of receiving the final message from the CSI server computer 12 to 8:00 am at the time of receiving the starting message from the CSI server computer 12,
There is no coordination between the DVP server computer 4 and the CSI server computer 12. Among the data transmitted from the DVP server computer 4 to the CSI server computer 12, the data other than the control data is transmitted in the form of "transmission start", "data", and "transmission end".

[0596] There are two types of form data: a fixed number of rows form and a tabular form. The fixed line number form is a form in which the number of lines, items, and the like are fixed in the display content.
All members 2 have the same format. For example,
A summary table, a general settlement table, a total payment calculation table, etc. correspond to this. The tabular form is a form in which the number of detail lines is variable. The items are constant, and the number of pages differs for each member 2. For example, the scheduled settlement quantity for each brand, the settlement settlement quantity for each brand, notification of fail information, and the like correspond to this.

[0597] The data acquisition timing will be described. Asynchronously with the transmission from the CSI server computer 12 to the message queue, the DVP server computer 4
The queue monitors the queue in a certain cycle, and acquires the data if it has arrived. Data acquisition is CSI
The period from when a business start request message is received from the server computer 12 to when a business end message is received is targeted.

The data type of the entry will be described.
The data for the buy-in withdrawal declaration input screen of the buy-in withdrawal declaration is data for creating the withdrawal input screen and checking the MAX value of the numerical value.
2 to the DVP server computer 4. The control data buy-in withdrawal report acceptance start notification is notified at 9:00. DVP from CSI server computer 12
It is transmitted to the client computer 9 via the server computer 4.

[0599] The control data buy-in withdrawal report acceptance start confirmation notice is transmitted from the DVP server computer 4 to the CSI server computer 12. The buy-in withdrawal report of the buy-in withdrawal report is transmitted from the client computer 9 to the CSI server computer 12 via the DVP server computer 4.

The buy-in withdrawal report receipt confirmation notification of the buy-in withdrawal report is transmitted from the CSI server computer 12 to the DV.
It is transmitted to the client computer 9 via the P server computer 4. Member 2 with a withdrawal declaration
Will be sent to The cancellation of the buy-in withdrawal of the buy-in withdrawal report is transmitted from the client computer 9 to the CSI server computer 12 via the DVP server computer 4.

[0601] The CSI server computer 12 sends a DV notification from the CSI server computer 12 to the DVB.
It is transmitted to the client computer 9 via the P server computer 4. Member 2 withdrawal cancellation
Will be sent to The control data buy-in withdrawal report acceptance end notification is transmitted from the CSI server computer 12 to the client computer 9 via the DVP server computer 4.

[0606] The confirmation notice of the completion of acceptance of the buy-in withdrawal report of the control data is notified at 12:00. It is transmitted from the DVP server computer 4 to the CSI server computer 12. Data for the buy-in request report input screen of the buy-in request report is transmitted from the CSI server computer 12 to the DVP server computer 4. This is data for creating a declaration input screen and checking the numerical MAX value.
The data for the sales order application input screen for selling orders is C
The data is transmitted from the SI server computer 12 to the DVP server computer 4. Input of sales order application and MA of numerical value
This is data for checking the X value.

The control data buy-in request acceptance start notification is sent at 12:30. The data is transmitted from the CSI server computer 12 to the client computer 9 from the DVP server computer 4. The notification destination is all members 2. The control data buy-in report acceptance start confirmation notice is transmitted from the DVP server computer 4 to the CSI server computer 12.

[0606] The buy-in request report of the buy-in request is transmitted from the client computer 9 to the CSI server computer 12 via the DVP server computer 4. The confirmation of the acceptance of the buy-in request for the buy-in request is transmitted from the CSI server computer 12 to the client computer 9 via the DVP server computer 4. The destination is the member 2 who has reported the buy-in request. The notice of cancellation of the buy-in request for the buy-in request is transmitted from the client computer 9 to the CSI server computer 12 via the DVP server computer 4.

[0605] The buy-in request cancellation confirmation of the buy-in request is transmitted from the CSI server computer 12 to the client computer 9 via the DVP server computer 4. The destination is the member 2 who has canceled the buy-in request. A notice of completion of acceptance of the buy-in request report of the control data is sent at 14:30. It is transmitted from the CSI server computer 12 to the client computer 9 via the DVP server computer 4. The DVP server computer 4 transmits the control data buy-in request acceptance completion confirmation notice to the CSI server computer 12.

[0606] An order acceptance start notification of a sell order of control data is sent at 15:00. It is transmitted from the CSI server computer 12 to the client computer 9 via the DVP server computer 4. The notification of the start of receiving the order for the sales order of the control data is transmitted from the DVP server computer 4 to the CSI server computer 12. The sales order application notice of the sales order is sent from the client computer 9 via the DVP server computer 4 to the CSI.
The information is transmitted to the server computer 12.

[0607] The confirmation of the acceptance of the sales order application for the sales order
It is transmitted from the CSI server computer 12 to the client computer 9 via the DVP server computer 4. The destination is the member 2 who has applied for a sales order. The sales order cancellation notice of the sales order is transmitted from the client computer 9 to the CSI server computer 12 via the DVP server computer 4. The confirmation of the acceptance of the cancellation of the sales order is transmitted from the CSI server computer 12 to the client computer 9 via the DVP server computer 4. The destination is the member 2 who has been notified of the sales order cancellation.

[0608] A notice of order reception end of the sales order of the control data is notified at 15:30. It is transmitted from the CSI server computer 12 to the client computer 9 via the DVP server computer 4. The notification of the completion of the acceptance of the order for selling the control data is transmitted from the DVP server computer 4 to the CSI server computer 12.

[0609] Buy-in request report notification, buy-in request cancellation notification, sell order application notification, sell order cancellation notification, buy-in cancellation report notification, buy-in cancellation cancellation notification, notification of end of entry information acceptance from DVP server computer 4 to CSI server computer 12. Is transmitted immediately upon request. DVP server computer 4
Since the exchange between the member 2 and the CSI server computer 12 is asynchronous, there is a time lag for the member 2 to receive the result. Therefore, a separate confirmation screen is required.

There are two types of data, such as status notification information, a data setup completion notification and a confirmation notification.
The notification of the completion of the data setup is a notification that "the member 2 has been notified that the form data has been created", and is performed for each form. The same information that is sent to the CSI server computer 12 is stored in the DVP server computer 4. The process is completed when the notification is executed on the DVP server computer 4.

[0611] The confirmation notification means that the first of "payment information is downloaded" or "payment information is referred to by the browser" is transmitted to the CSI server computer 12 as a "confirmation notification". Notify. The same information that is sent to the CSI server computer 12 is stored in the DVP server computer 4.

The status notification information is processed according to the flow shown in FIG. That is, the DVP server computer 4
The settlement data is received from the SI server computer 12 (process 241). Next, the received payment data is stored in the database (process 242). Next, a CSV file is created from the received payment data (process 24).
3). The information communication server computer 166 of the DVP server computer 4 performs a notification process of transmitting the created file to the client computer (process 24).
4). At this time, when the setup of the data for notification is completed, the information communication server computer 166
The status notification function (acceptance & immediate transmission) 169 notifies the completion of data setup.

The client computer 9 performs a notification display process of displaying the notification received from the DVP server computer 4 on the screen (process 245). Next, according to an instruction from the user of the client computer, CS
A process for downloading or browsing the V file is performed (process 246). When the CSV file is downloaded or the browser is browsed, the client computer 9 sends a status notification function (acceptance & immediate transmission) 169
At the end of the confirmation.

[0614] Status notification function (reception & immediate transmission) 169
Transmits the notification status to the CSI server computer 12 (process 247). At this time, when a plurality of users of the same member 2 confirm the same information, only the first one is notified to the CSI server computer 12. Further, the status notification function (reception & immediate transmission) 169 performs a process of registering a business log related to the status notification in the log management database 77 (process 248).

The transmission timing of the status notification information data will be described. Basically, the DVP server computer 4 accumulates the status notification information data for a certain period of time and transmits it collectively even if there is a request. However, for those that require immediacy, they are transmitted immediately when requested. Batch transmission or immediate transmission involves segmentation for each data.

The status notification data includes the control unit, the transmission member code (the member code of the member 2 that has completed the notification), the member code (the member code that is the content of the notified data), and the notification completion date and time (the notification to the member 2). Date and time (year / month / day / hour / minute / second)), type of notified form, cycle of notified form, business date (year / month / day) when the notified form was created, status type (data setup completed / viewing or downloading) Completion).

There are five types of form master data: member master, issue master / bond master, kanji constant, bank master, and stock option master. The member master is used to display the member kanji name. The issue master and the bond master are used to display stock kanji names of stocks (stock master) and non-stocks (bond master). Kanji constant is used for displaying kanji names in general. The bank master is
Used to display bank, branch, and account names. The stock certificate option brand master is used to display the original stock kanji and the like.

[0618] The form master data is basically transmitted every day. Normally, the user wants to use the master data as of the settlement date for the settlement data and the master data as of the contract date for the contract data.
What is necessary is just to use the master data of the latest date.

[0619] As for the acquisition timing of the form master data by the DVP server computer 4, the DVP server computer 4 monitors the queue in a certain cycle asynchronously with the transmission from the CSI server computer 12 to the message queue, and the data arrives. If so, it shall be acquired. Data acquisition is performed from when a business start request message is received from the CSI server computer 12 to when a business end message is received.
Carried out in 00 during the (18:00 prospect a).

The control data includes a business start request response, a business end request response, a previous day security deposit / insertion return reception start response, a previous day security / insertion return reception end response, a buy-in request reception start response. , Buy-in claim report acceptance end response, Sell order order acceptance start response, Sell order order acceptance end response, Buy-in withdrawal report acceptance start response, Buy-in withdrawal report acceptance end response, CS from DVP server computer 4
There are types of a form data retransmission request message to the I server computer 12, a control data retransmission request message from the DVP server computer 4 to the CSI server computer 12, a form data reception confirmation, and the like. The control data is transmitted immediately upon receipt of the response target message.

[0621] A method of mounting MQ and MQD will be described. As the concept of the message format of the DVP server computer 4 and the CSI server computer 12, data other than control data includes a header (start message), N (N is 1 or more) data portions, a footer (end message), Consists of Control data has no header / footer,
It consists only of control data.

The message item definition of the control message is as follows. 1. The message type is an item for identifying a control message by a code. 2. The control types include a business start request response, a business end request response, a previous day's deposit / return return acceptance start response, a previous day's collateral / return return acceptance end response, a buy-in request acceptance start response, a buy-in request declaration Controlled code such as reception end response, sell order order reception start response, sell order order reception end response, buy-in withdrawal report reception start response, buy-in withdrawal report reception end response, retransmission request message, reception confirmation message, etc. The item to be identified.

[0623] 3. Data type is not used. 4. The cycle is fixed at 0. 5. The creation date is the date of the business date. 6. Serial number, 7. Includes user data section.

The message item definition of the business message is as follows. 1. The message type is an item for identifying a single data by a code. 2. The control type is an item for identifying an inquiry or a response. 3. The data type is an item for identifying a buy-in request report, a buy-in request report end, a buy-in order application, a buy-in order application end, a buy-in withdrawal report, and a buy-in withdrawal report end.

[0625] 4. The cycle number is a cycle item for each data type. 5. The creation date is the date of the business date. 6. The serial number is a serial number. 7. Subsequent items are data-dependent items and depend on each business of the entry. Regarding withdrawal tasks for which multiple selections can be made, a summary is sent with assurance that they are in the oldest order.

The message item definition of the header in the header / footer format (notification) is as follows. 1. The message type is an item for identifying the type of the message by a code. 2. The control type, which has been a “telegram type” item in the past, is an item for identifying a header. 3. The data type is an item for identifying a status notification.

[0627] 4. This is the cycle number item. 5. The creation date is a “send date” item in the past, and is the date of the business date. 6. The serial number is a serial number, which has conventionally been the “telegram ID” item. 7. The following items are data-dependent items and depend on each business.

The message item definition of the data section in the header / footer format (notification) is as follows. 1. The message type is an item for identifying the type of the message by a code. 2. The control type is the item of “telegram type” in the related art, and is an item for identifying the data as a code. 3. The data type is an item for identifying a status notification. 4. This is the cycle number item.

[0629] 5. The creation date is a “send date” item in the past, and is the date of the business date. 6. The serial number is a serial number, which has conventionally been the “telegram ID” item. 7. The number of records is conventionally “the number of records”, and is the number of records included in one data portion. 8. Subsequent items are data-dependent items and depend on each task of notification.

The message item definition of the footer part in the header / footer format (notification) is as follows. 1. The message type is an item for identifying the type of the message by a code. 2. The control type is the item of “telegram type” in the related art, and is an item for identifying a footer by a code. 3. The data type is an item for identifying a status notification.

[0631] 4. This is the cycle number item. 5. The creation date is a “send date” item in the past, and is the date of the business date. 6. The serial number is a serial number which is conventionally “telegram ID”. 7. The total number of data is the total number of data in the data section.

[0632] The types of faults related to the cooperation between the CSI server computer 12 and the DVP server computer 4, and the actions to be taken when they occur, will be described. Describe work and obstacles.

[0633] A failure in the form processing in the notification operation will be described. When a failure occurs in the CSI server computer 12, CSV creation and notification to members are disabled, and the recovery method is to wait for the CSI server computer 12 to recover. Network (CSI server computer 12-D
When a failure occurs in the VP server computer 4),
CSV creation and notification to the member are not allowed, and the recovery method is to hand data or fax by electronic medium. DV
When a failure occurs in the P server computer 4, CS
V creation, notification to members is not allowed, recovery method is DVP
The recovery of the server computer 4 is awaited. In the notification work, a failure in form processing is basically handled immediately, but the urgency is low.

[0634] A failure in the settlement process in the notification operation will be described. When a failure occurs in the CSI server computer 12, CSV creation and notification to members are disabled, and the recovery method is to wait for the CSI server computer 12 to recover. Network (CSI server computer 12-D
When a failure occurs in the VP server computer 4),
Creation of CSV and notification to the member are not allowed, and the recovery method is to hand data by electronic medium. When a failure occurs in the DVP server computer 4, the CSV creation and notification to the member are disabled, and the recovery method is to wait for the recovery of the DVP server computer 4. The failure of the settlement process in the notification work is extremely urgent. The time limit is tight.

[0635] The failure of the confirmation processing in the notification work will be described. When a failure occurs in the CSI server computer 12, CSV creation and notification to members are disabled, and the recovery method is to wait for the CSI server computer 12 to recover. Network (CSI server computer 12-D
When a failure occurs in the VP server computer 4),
Creation of CSV and notification to the member are not allowed, and the recovery method is to hand data by electronic medium. When a failure occurs in the DVP server computer 4, the CSV creation and notification to the member are disabled, and the recovery method is to wait for the recovery of the DVP server computer 4. Obstacles in the confirmation process in the notification work are basically immediate, but urgency is low.

[0636] A failure in the application / withdrawal processing in the entry business will be described. When a failure occurs in the CSI server computer 12, notification to the CSI is not possible, the application from the member can be stored in the DVP, and the recovery method is collective processing after recovery and telephone communication. Network (CS
When a failure occurs in the I server computer 12-DVP server computer 4), it is impossible to notify the CSI. The application from the member can be stored in the DVP, and the recovery method is collective processing after recovery, telephone communication, and handing over data by electronic medium. If a failure occurs in the DVP server computer 4, the business is stopped and the recovery method is D
Waiting for the recovery of the VP server computer 4 and making a telephone call. Obstacles in the application / withdrawal processing of entry work are highly urgent.

[0637] A failure of the sales order processing in the entry business will be described. When a failure occurs in the CSI server computer 12, notification to the CSI is not possible, reception from members is allowed to be stored in the DVP, and the recovery method is collective processing after recovery and telephone communication. Network (CSI server computer 12-DVP server computer 4)
In the event of a failure, notification to the CSI is not possible, reception from the member is allowed to be stored in the DVP, and the recovery method is to collectively process after recovery, telephone communication, and hand data via electronic media. When a failure occurs in the DVP server computer 4, the business is stopped and the recovery method is DVP
Waiting for the server computer 4 to recover, and then making a telephone call. Obstacles in sales order processing in the entry business are extremely urgent.

The following describes a failure in the control processing. CSI
When a failure occurs in the server computer 12, the business cannot be started if the start message does not come, and the business cannot be ended if the end message does not come. Recovery method is CS
Wait for the recovery of the I server computer 12. When a failure occurs in the network (CSI server computer 12-DVP server computer 4), the business cannot be started if the start message does not arrive, and cannot be terminated if the end message does not arrive. The recovery method is telephone communication.
When a failure occurs in the DVP server computer 4,
If the start message does not come, the business cannot be started, and if the end message does not come, the business cannot be ended. Recovery method is DV
Wait for the recovery of the P server computer 4. The failure of the control process is highly urgent for the start message. The end message can be covered by the operation even if recovery is slightly delayed.

The types of faults in the DVP server computer 4 will be described. The failure point is the hardware body,
An example of a failure in the case of a peripheral device is a failure, and the effect on business is a system down or business stop. An example of a failure when the failure location is a hardware communication device is a failure, and the business impact is a business suspension.

[0640] Examples of failure when the failure location is a hardware communication path include line disconnection, timeout, garbled data, data disappearance, and queue overflow. An example of a failure when the failure location is the software OS is a bug, and the business impact is a system down or business suspension.

[0641] Examples of failures when the failure location is software middleware (DB, INTERSTAGE, etc.) include bugs and resource depletion, and the effect on business is business suspension. An example of a failure when the failure location is a software application is a bug, and the effect on the business is the suspension of the target business. An example of a failure when the failure location is software data is inconsistent data, and the impact on the business is the suspension of the target business.

The recovery method at the time of failure is as follows.
When the fault location is the hardware main body, peripheral device, or communication device, the recovery method is to elucidate the cause and repair / replace the fault location. When the failure point is a hardware communication path, the recovery method is to elucidate the cause, restart the system, change the environment setting, wait, clear the queue, and retransmit (retransmission from the CSI server computer 12, DVP,
2 of retransmission by sending retransmission request from server computer 4
Pattern).

When the fault location is the software OS or middleware (DB, INTERSTAGE, etc.), the recovery method is to elucidate the cause and restart the system. When the failure is a software application, the recovery method is to determine the cause by using logs, correct the source,
Stop / restart the application, clear the queue. When the failure location is software data, the recovery method is data re-creation and re-transmission (two patterns of re-transmission from the CSI server computer 12 and re-transmission by transmitting a re-transmission request from the DVP server computer 4).

The alternative route for each data in the case of a failure in the communication part is as follows. If the route is form data, the operation function is provided with a manual rerun function as an alternative route, or the data is stored in an electronic medium and handed over. A mechanism for capturing data from electronic media is required separately. If the route is an entry, the log of the DVP server computer 4 is referred to as an alternative route, or downloaded from the log to CSV and handed over by electronic medium.

If the route is a status notification (confirmation completion notification), the log of the DVP server computer 4 is referred to as an alternative route, or downloaded from the log to CSV,
Hand over electronic media. When the route is the master data, the operation function is provided with a manual rerun function as an alternative route, or the data is stored in an electronic medium and handed over. A mechanism for capturing data from electronic media is required separately.

[0646] The failure notification and monitoring method will be described.
As coordination with log management, CSI server computer 1
All communications with 2 are recorded as a log. Enable to display on the console as well as the normal system abnormal system at any time. The log acquisition timing and the failures that can be acquired are as follows.
When the log is acquired at the time of transmitting a message from the DVP server computer 4, it is possible to acquire a failure of connection failure or transmission failure in units of transmission information.

[0647] If the log is acquired at the time of receiving a message from the CSI server computer 12, it is possible to acquire failures such as connection failure, data loss, and data inconsistency in units of received information. If the log acquisition timing is when the DB is stored, it is possible to acquire failures such as DB inactivation, data inconsistency, and resource depletion in table units. If the log is acquired at the time of CSV creation, it is possible to acquire a resource depletion or a failure due to a file authority error in CSV file units.

[0648] The storage method in the database and the handling of the CSV file will be described. The data stored in the database is used as an HTML data source. The download CSV file is created separately from the data in the database. The storage method and storage unit in the database will be described with reference to FIGS.

FIG. 82 is a diagram showing a method of storing form data and a storage unit. First, the DVP server computer 4 acquires the form data from the CSI server computer 12 and performs a first-in first-out process using a queue (queue) 251. Next, the cooperative communication process is performed on the job extracted from the queue 251 (process 252).

[0650] Thereafter, with reference to the form master data stored in the master database 257, a process of creating a CSV for each record is performed for the form data (process 253), and the created CSV file database 25 is processed.
4 is stored. Also, after performing the cooperative communication processing (processing 2
52) The acquired form data is registered in the form management database 258 and the form database 259.

FIG. 83 is a diagram showing a storage method and storage units of master data and entry data. First, DV
The P server computer 4 acquires master data and entry data from the CSI server computer 12 and performs a first-in first-out process using a queue (queue) 251. Next, the job extracted from the queue 251 is stored in each table 26 of the database server computer 256.
1 is stored (process 260).
At this time, the master data is stored after replacing all items, and the entry data is additionally stored.

[0652] The CSV file is managed by a CSV management information table. As a result, CS provided to member 2
V file search and CSV file status management are possible. FIG. 84 is a diagram illustrating a table of CSV management information. The table of CSV management information includes a form type, a cycle, a creation date, a transmission member code, a member code, a storage destination directory name, a CSV file name, and a distribution information presence / absence flag. The transmission member code is the member 2 who downloads the CSV, and the member code is the code of the member 2 indicated by the contents of the CSV. The storage directory name is created from the form type, member code, and creation date. The CSV file name is created from the form type, member code, and creation date. The distribution information presence / absence flag is a flag for identifying the presence / absence of distribution information (CSV file). The storage period of the CSV file is 6 business days, and files whose storage period has expired are deleted.

The CSV creation method will be described. If the same member 2 is to be notified of the generation of a CSV file of the same form within one day, the entire CSV file is replaced. The created CSV file is stored for a predetermined period of time, and the CSV files that are not stored are deleted. The predetermined storage period in this case is determined by the specification of the search process. The form data is received from the CSI server computer 12, and is output to a CSV file line by line at the timing of writing the record to the database.

Only the data for the current day is registered in the CSV file, and the past data is not registered. The CSV file is
Create for each member + report. When storing in a CSV file, a blank line is a line having only a comma in a fixed line number form. That is, a blank line record exists in the form table of the DVP server computer 4. No blank line exists in the tabular form.

[0655] Fig. 85 is a flow chart of a process of transmitting the distributable information to the member 2 (client computer 9) side, in which the scheduled settlement quantity for each brand is distributed as an example. When the process starts, step S51
Then, the prefix of the CSV file creation directory is obtained from the operation management table.

Next, in step S52, common information such as the data type and the broadcast notification members 1 to 700 is extracted from the message header portion. In step S53, it is determined whether or not there is a record in distribution information management database 172.

If there is no record in the distribution information management database 172 (step S53: No), step S5
In step S4, the distribution information detailed table 172b and the CSV file are deleted, and in step S55, one message is read from the message data part. If there is a record in the distribution information management database 172 (step S53: Yes), the electronic mail is read one by one from the electronic mail data section in step S55. In the reading from the message data part in step S55, first, the number of records is read, and items are cut out in record units until there is no more data. Obtain the accountant member name, member name, kanji, bank name, etc. from each master. Create a CSV directory and CSV file name. The data is output to CSV, and the data is added to the scheduled settlement amount by brand. In step S55, the above processing is repeated as a loop.

Next, at step S56, the broadcast notification member 1
Reading is repeated until no data remains. In the member reading in step S56, first, the distribution information detailed table 172b is searched. If no data is found as a result of the search, the distribution information detailed table 172b
Is added to the distribution information type, cycle, creation date, and data indicating that there is no data.

[0659] Next, in step S57, it is determined whether or not the information is immediate transmission information for which the notification time is not specified or information for which the specified notification time has elapsed. If the information is the immediate transmission information with no notification time specified or the information for which the specified notification time has elapsed (step S57: Yes), the distribution timing flag is specified to be immediate transmission in step S58, and step S60 is performed.
It is determined whether or not the number of records in the distribution information management database is zero.

[0660] If the information is not immediate transmission information for which the notification time is not specified or information for which the specified notification time has elapsed (step S57: No), the distribution timing flag is specified for the time specification in step S59, and the distribution information management is performed in step S60. It is determined whether the number of records in the database is 0 or not.

If the number of records in the distribution information management database is 0 (step S60: Yes), the information is added to the distribution information notification in the distribution information management database 172 in step S61, and the number of data in the footer section is reduced in step S63. Determine if they are consistent. When the number of records in the distribution information management database is not 0 (step S6)
0: No), the distribution information notification in the distribution information management database 172 is updated in step S62, and it is determined in step S63 whether the number of data items in the footer section matches.

If the number of data items in the footer section matches (step S63: Yes), a response message is transmitted in step S65. If the number of data items in the footer section does not match (step S63: No), error processing such as rollback of the database and message queue, deletion of all CSV files, and log output is performed in step S64, and a response message is generated in step S65. Send

After transmitting the response message in step S65,
In step S66, it is determined whether the distribution timing is immediate transmission. When the delivery timing is immediate transmission (step s
66: Yes), the notification function 167 is called, and a log value such as "notification processing started", "notification processing ended normally", "notification processing returned an error", etc. is performed by looking at the return value. . After that, the process ends. If the distribution timing is not immediate transmission (step s66: No), the process ends.

In the case of the distribution of the total received / paid price calculation table (planned amount), the bank name is not obtained from the master in the reading from the telegram data portion in step S55, and the total amount is set instead of the scheduled settlement amount by brand. Except for adding data to the receipt / payment calculation table (planned amount), the processing flow is substantially the same as the processing flow of distribution of scheduled settlement amount by brand in FIG. 85.

[0665] Also, notification of buy-in execution result (for all members)
In the case of the distribution process, the process of determining whether or not there is a record in the distribution information management database 172 in step S53 is performed to determine whether or not there is the same cycle. Just before C
Create SV directory, CSV file name,
The data is added to the buy-in execution result notification (for all members) instead of the scheduled settlement amount for each brand, and the distribution information type is added to the distribution information detailed table 172b without searching the distribution information detailed table 172b in the member reading process in step S56. 85, except that data such as cycle, creation date, etc. are added, and the member code is set to “all members” in the member reading process in step S56. It is.

[0666] The outline of the entry operation will be described. In the present embodiment, a system for declaring a buy-in request for a buy-in operation, applying for a buy-in order accompanying execution of a buy-in, and declaring a withdrawal of a buy-in request. Realize the linkage with the authentication / credit and monitoring functions in the actual operation.

[0667] An outline of the flow of the buy-in billing-related business will be described. The implementation date of the buy-in billing related business is X
+ N) day, and the day after the settlement date (failed date). The target member receives the “fail information notification (D)” which is notified by 12:30 from the day after the settlement date (failed date).
"After EL)" is a failed member whose failure has not been resolved.

The flow of data related to a buy-in request will be described. The fail information notification (after DEL) is one of the forms of the broadcast notification, and all members 2
Sent to. DV from CSI server computer 12
It is transmitted to the client computer 9 via the P server computer 4. Non-information is notified to members other than the fail / failed member.

[0669] The buy-in billing target brand information is 1 on X day.
DV from CSI server computer 12 by 2:30
It is transmitted to the P server computer 4. The notice to start accepting the buy-in request is transmitted from the CSI server computer 12 to the DVP server computer 4 at 12:30 on the X day. The broadcast notification to the member 2 is not performed.

[0670] The buy-in request declaration reception start response is a notification that the buy-in request reception start notification has been received,
At 12:30 on the X day, the DVP server computer 4 sends C
The information is transmitted to the SI server computer 12. The buy-in request is transmitted from the client computer 9 to the CSI server computer 12 via the DVP server computer 4 from 12:30 to 14:30 on the X day. The sender is a failed member or a buy-in requesting member. There are three cases: a new declaration, a change declaration, and a cancellation declaration.

The notice for confirming the acceptance of the buy-in request is a notification of the validity / invalidity of the request for the buy-in request.
It is transmitted from the CSI server computer 12 to the DVP server computer 4 from 30 to 14:30. There is no voluntary notice to Member 2. Notice of end of acceptance of buy-in claim report
It is transmitted from the CSI server computer 12 to the DVP server computer 4 at 14:30 on the X day. There is no broadcast notification to member 2.

[0672] The buy-in request declaration reception end response is a notification that the buy-in request report reception end notification has been received.
It is transmitted from the DVP server computer 4 to the CSI server computer 12 after 14:30 on the day. The end of the buy-in declaration is a notification that all the buy-in declarations have been transmitted, and is transmitted from the DVP server computer 4 to the CSI server computer 12 after 14:30 on X day.

[0673] The buy-in request declaration end response is a notification that the buy-in request declaration end has been received.
After 0, it is transmitted from the CSI server computer 12 to the DVP server computer 4. The buy-in information notification (initial) is a form for notifying the buy-in request date, which is notified to the buy-in requesting member and the member to be paid at 15:00 on X day. From the CSI server computer 12 via the DVP server computer 4 to the client computer 9
Is transmitted to

[0674] The buy-in information notification (after the CNS) is a form notified to the buy-in requesting member and the member to whom the cost is to be paid, and is sent from the CSI server computer 12 to the client computer 9 via the DVP server computer 4 at 17:00 every day after X. Is transmitted. You will be notified daily until all relevant buy-in requests or expenses (provisional) have been resolved.

The function outline of the CSI server computer 12 is as follows. CSI server computer 12
Creates a “failure information notification (after DEL)” of all members 2 by 12:30 every day and transmits it to the DVP server computer 4. The CSI server computer 12 has X
By 12:30 on the day, “buy-in billing target brand information” is created and transmitted to the DVP server computer 4.

At 12:30 on the X day, the CSI server computer 12 sends a “buy-in claim report acceptance start notice” to the DV server.
The request is transmitted to the P server computer 4 to start a buy-in request report acceptance process. CSI server computer 12
Performs a receiving process on the “buy-in claim report” received from the DVP server computer 4, and transmits the result to the DVP server computer 4.

At 14:30 on the X day, the CSI server computer 12 sends a “buy-in claim report acceptance end notice” to the DV server.
When transmitting to the P server computer 4 and receiving the “buy-in billing report acceptance end response” and the “buy-in billing report end” from the DVP server computer 4, a “buy-in billing report end response” is returned to the DVP server computer 4, and the buy-in billing is returned. The process of accepting the declaration ends.

[0678] The CSI server computer 12 transmits the "buy-in information notification (initial)" to the buy-in billing member and the member to whom the cost is to be paid at 15:00 on the DV invoice date.
Send to P server computer 4. The CSI server computer 12 operates at 17:00 every day after the buy-in billing date.
If necessary for 0, "Buy-in information notification (after CNS)" to notify buy-in requesting members and cost-bearing members to DV
Send to P server computer 4.

The function outline of the DVP server computer 4 is as follows. The DVP server computer 4 broadcasts “fail information notification (after DEL)” received from the CSI server computer 12 to all members 2 every day until 12:30.

[0680] The DVP server computer 4 reads the X day 1
The buy-in billing target table is re-created with the “buy-in billing target brand information” received from the CSI server computer 12 by 2:30. DVP server computer 4
At 12:30 on X day, the CSI server computer 12
Receives a “buy-in bill report acceptance start notification” from the customer, and sends a “buy-in bill report acceptance start response” to the CSI server computer 12 within the bill report acceptance time. However, if the “brand information for buy-in billing” has not yet been received from the CSI server computer 12, the time is not within the billing report acceptance time. And

After receiving the “buy-in claim report” from the client computer 9, the DVP server computer 4 assigns a billing number (at the time of a new report), updates the version number, updates the buy-in billing table, and sends the “ "Bill-in claim declaration". Further, the member 2 is notified of the “temporary receipt” or “temporary cancellation” and the billing number in real time by the “buy-in billing report upload notification”. Check inside and outside of the buy-in request reception time.
If the time is out of time, the member 2 is not transmitted to the CSI server computer 12 and the out-of-time error is notified to the member 2 by "buy-in request report upload notification".

The DVP server computer 4 updates the buy-in request table with the “buy-in request acceptance confirmation notice” received from the CSI server computer 12. DVP
When the server computer 4 receives the “buy-in billing report acceptance end notice” from the CSI server computer 12 every day at 14:30, the server computer 4 deems it outside the billing bill accepting time,
A “buy-in claim report acceptance end response” is transmitted to the server computer 12. The DVP server computer 4 transmits all the unsent “buy-in bill report” to the CSI server computer 12 and reports “buy-in bill end” to the CS.
Send it to the I server computer 12.

The DVP server computer 4 arbitrarily notifies the “buy-in information notice (initial)” received from the CSI server computer 12 at 15:00 on the buy-in billing date to the buy-in billing member and the member to whom the cost is to be paid. The DVP server computer 4 operates every day after the buy-in billing date.
At 7:00, the "buy-in information notification (after CNS)" received from the CSI server computer 12 is arbitrarily notified to the buy-in requesting member and the member to be paid.

The function outline of the client computer 9 is as follows. Every day, the client computers 9 of all the members 2 receive a broadcast notification of “failure information notification (after DEL)” from the DVP server computer 4 by 12:30. The failing member's client computer 9 inputs the billing brand, quantity, etc. from the buy-in claim report screen, and transmits “buy-in claim report” to the DVP server computer 4.

The client computer 9 of the buy-in billing member selects the billing report to be changed from the buy-in billing reception status table, changes the quantity, and transmits a “buy-in billing report” to the DVP server computer 4. The buy-in billing member client computer 9 selects a bill report to be canceled from the buy-in bill acceptance status table, and transmits “buy-in billing request” to the DVP server computer 4.

[0686] The client computer 9 of the buy-in billing member and the member for whom the cost is to be paid is notified by the DVP server computer 4 of a "buy-in information notification (initial)" at 15:00 on the buy-in billing date and one day after the buy-in billing date.
At 7:00, an optional notification of “buy-in information notification (after CNS)” is received.

An outline of the flow of the buy-in order application-related business accompanying the execution of the buy-in will be described. The execution date of the business related to the buy-in order application is X + 3 days or later, and the failure is canceled or the buy-in is withdrawn from 3 days after the buy-in billing date. Target members are all regular members and special participants in stock certificate options trading.

The flow of data related to a buy-in order application associated with the execution of a buy-in will be described. The buy-in information notification (after DEL) is a form distributed to the buy-in billing member and the member to be paid at 12:30 every day after the X + 1 day, and is transmitted from the CSI server computer 12 to the client computer 9 via the DVP server computer 4. Is done. You will be notified daily until all relevant buy-in requests or expenses (provisional) have been resolved.

[0689] The buy-in execution notice is 1 after the X + 3 day.
At 2:30, the form is distributed to the billing member, the member for whom the cost is to be paid, and all members, and is transmitted from the CSI server computer 12 to the client computer 9 via the DVP server computer 4. There are three types, one for billing members, one for cost-bearing members, and one for all members. The buy-in order target brand information is transmitted from the CSI server computer 12 to the DVP server computer 4 by 15:00 after X + 3 day.

[0690] The notice to start accepting the buy-in order application is X + 3
At 15:00 after the date, the information is transmitted from the CSI server computer 12 to the DVP server computer 4. There is no broadcast notification to member 2. The buy-in order application acceptance start response is a notification that the buy-in order application acceptance start notification has been received, and is transmitted from the DVP server computer 4 to the CSI server computer 12 at 15:00 after X + 3 day.

[0690] Buy-in order application must be made on the day after X + 3
From 5:00 to 15:30, it is transmitted from the client computer 9 to the CSI server computer 12 via the DVP server computer 4. The sender is the member who wants to sell,
As a sales order member, new application, change application, cancellation application
There are two cases. The notification of the acceptance of the buy-in order application is a notification such as the validity / invalidity of the buy-in order application data.
The data is transmitted from the CSI server computer 12 to the DVP server computer 4 from 15:00 to 15:30 after +3 days. There is no voluntary notice to Member 2.

[0699] The notice of the completion of the acceptance of the buy-in order application is X + 3
The data is transmitted from the CSI server computer 12 to the DVP server computer 4 at 15:30 after the date. There is no broadcast notification to member 2. The buy-in order application acceptance end response is a notification that the buy-in order application acceptance end notification has been received, and is transmitted from the DVP server computer 4 to the CSI server computer 12 at 15:30 on or after X + 3 day. The end of the buy-in order application is a notification that all the buy-in order applications have been sent, and 15: 3 after X + 3 day.
After 0, it is transmitted from the DVP server computer 4 to the CSI server computer 12.

[0693] The buy-in order application end response is a notification that the buy-in order application end has been received.
It is transmitted to the VP server computer 4. The notice of the buy-in execution result is transmitted from the CSI server computer 12 to the client computer 9 via the DVP server computer 4 at 16:30 after X + 3 day. The notification destination is any one of a billing member, a cost-bearing member, a selling member, and all members. There are four types of notification destinations: a billing member, a cost-bearing member, a selling member, and all members.

[0694] The buy-in invalid information notification is 1 after X + 3 day.
At 7:00, the client computer 9 passes from the CSI server computer 12 via the DVP server computer 4.
Is transmitted to The notification destination is the member 2 having the invalid buy-in. There are billing members and cost-paying members, which are determined for each brand. Notification of buy-in information (after CNS) is received from the CSI server computer 12 at 17:00 every day after the X day.
It is transmitted to the client computer 9 via the VP server computer 4. The notification destinations are the buy-in requesting members and the members to whom the cost is to be paid, and are notified daily until all related buy-in requests or the members to whom the cost is to be paid (provisional) are resolved. The buy-in execution notice (previous day notice) is CSI at 17:00 on X + 2
It is transmitted from the server computer 12 to the client computer 9 via the DVP server computer 4. The notification destination is one of a billing member, a cost-bearing member, and all members. There are three types of notification destinations: a billing member, a cost-bearing member, and all members.

An outline of functions of the CSI server computer 12 is as follows. The CSI server computer 12
Every day after the buy-in billing date, 17:00 if necessary
Then, a “buy-in information notification (after CNS)” is sent to the DVP server computer 4 to notify the buy-in requesting member and the cost-bearing member.

[0696] The CSI server computer 12 operates daily at 12:30 if necessary after the day following the buy-in billing date.
Then, a “buy-in information notification (after DEL)” is sent to the DVP server computer 4 to notify the buy-in requesting member and the cost-bearing member. The CSI server computer 12
At 17:00 two days after the buy-in billing date, a “buy-in execution notice (previous day notice)” is sent to the DVP server computer 4 to notify the buy-in billing member, the member to whom the cost is to be paid, and all members. At 12:30 on the buy-in execution date, the CSI server computer 12 sends a “buy-in execution notice” to notify the buy-in requesting member, the member to whom the cost is to be paid and all the members at DVP
Send it to server computer 4.

The CSI server computer 12 transmits “buy-in order target brand information” to the DVP server computer 4 by 15:00 on the buy-in execution date. CSI
The server computer 12 executes the buy-in execution date at 15: 0
At 0, a "buy-in order application acceptance start notice" is transmitted to the DVP server computer 4, and the acceptance process of the buy-in order application is started. The CSI server computer 12 is a DVP
The reception processing is performed for the “buy-in order application” received from the server computer 4, and the result is transmitted to the DVP server computer 4.

The CSI server computer 12 transmits a “buy-in order application acceptance completion notice” to the DVP server computer 4 at 15:30 on the buy-in execution date, and the DVP server computer 4 sends a “buy-in order application acceptance completion response” and “buy-in order acceptance response”. DV after receiving "Order application end"
A "buy-in order application end response" is returned to the P server computer 4, and the acceptance of the buy-in order application is terminated.

At 16:30 on the buy-in execution date, the CSI server computer 12 transmits to the DVP server computer 4 a “buy-in execution result notification” for notifying the buy-in billing member, the member to be paid the cost, the selling member and all members. C
The SI server computer 12 executes the buy-in execution day 1
At 7:00, a “buy-in invalidation information notification” is sent to the DVP server computer 4 to notify the buy-in requesting member having a buy-in to be invalidated and the cost-bearing member.

The function outline of the DVP server computer 4 is as follows. The DVP server computer 4 receives the “buy-in information notification (CNS) received from the CSI server computer 12 at 17:00 every day after the buy-in billing date.
) Is voluntarily notified to the buy-in requesting member and the member who bears the cost.

The DVP server computer 4 receives the “buy-in information notification (DEL) received from the CSI server computer 12 at 12:30 every day after the day following the buy-in request date.
) Is voluntarily notified to the buy-in requesting member and the member who bears the cost. At 17:00 two days after the buy-in request date, the DVP server computer 4
The “buy-in execution notice (previous day notice)” received from is voluntarily / broadcasted to the buy-in requesting member, the member to be charged, and all members.

The DVP server computer 4 arbitrarily / broadcasts the “buy-in execution notification” received from the CSI server computer 12 at 12:30 on the buy-in execution date to the buy-in requesting member, the member to be charged, and all members. DVP
The server computer 4 recreates the buy-in order target table based on the “buy-in order target brand information” received from the CSI server computer 12 by 15:00 on the buy-in execution date. The DVP server computer 4 starts the CSI server computer 12 at 15:00 on the buy-in execution date.
Receives a “buy-in order application reception start notice” from the above, the time is within the order application reception time, and a “buy-in order application reception start response” is transmitted to the CSI server computer 12.

After receiving the “buy-in order application” from the client computer 9, the DVP server computer 4
Numbering of order numbers (at the time of new application), update of version number, update of buy-in order table are performed, and CSI server computer 12
Send “buy-in order application” to Further, the member 2 is notified in real time of "temporary receipt" or "temporary cancellation" and the order number by "buy-in order application upload notification". It checks the inside and outside of the buy-in order reception time, and if it is outside the time, it does not transmit to the CSI server computer 12,
Overtime error "buy-in order application upload notification"
To notify the member 2.

[0704] The DVP server computer 4 updates the buy-in order table with the "buy-in order application acceptance confirmation notice" received from the CSI server computer 12. DV
The P server computer 4 executes the buy-in at 15:30
When a “buy-in order application reception completion notice” is received from the CSI server computer 12, the order is outside the order reception time, and a “buy-in order application reception completion response” is transmitted to the CSI server computer 12. The DVP server computer 4 transmits all the untransmitted “buy-in order application” to the CSI server computer 12 and transmits “buy-in order application end” to the CSI server computer 12.

The DVP server computer 4 arbitrarily / broadcasts the “buy-in execution result notification” received from the CSI server computer 12 at 16:30 on the buy-in execution date to the buy-in billing member, the member to be charged, the selling member, and all members. Notice. The DVP server computer 4 broadcasts the “buy-in invalid information notification” received from the CSI server computer 12 at 17:00 on the buy-in execution date to the buy-in requesting member having the invalid buy-in and the member to be paid the cost.

An outline of the functions of the client computer 9 is as follows. The client computer 9 of the buy-in billing member and the member for whom the cost is to be paid, receives the DVP server computer 4 at 17:00 every day after the buy-in billing date.
Receives an optional notification of "buy-in information notification (after CNS)".

[0707] The client computer 9 of the buy-in requesting member and the member for whom the cost is to be received receives an optional notification of "buy-in information notification (after DEL)" from the DVP server computer 4 at 12:30 every day after the day following the buy-in request date. The client computer 9 of the buy-in billing member, the member for whom the cost is borne, or all the members
At 17:00 a day later, an optional / broadcast notification of “buy-in execution notice (previous day notice)” is received from the DVP server computer 4.

The buy-in billing member, the member for whom the cost is borne, or the all members client computer 9 receives an arbitrary / broadcast notification of “buy-in execution notification” from the DVP server computer 4 at 12:30 on the buy-in execution date. The client computer 9 of all regular members and the special participant in the stock certificate option transaction inputs the brand, price, quantity, self / consignment category, etc. from the buy-in order application screen, and transmits a “buy-in order application” to the DVP server computer 4. The client computer 9 of the buy-in order member selects the order application to be changed from the buy-in order reception status table, changes the quantity and the like, and transmits “buy-in order application” to the DVP server computer 4.

The buy-in order member's client computer 9 selects the order application to be canceled from the buy-in order reception status table, and transmits a “buy-in order application” to the DVP server computer 4. At 16:30 on the buy-in execution date, the client computer 9 of the buy-in billing member, the member to be paid, the selling member, or all members receives an optional / broadcast notification of “buy-in execution result notification” from the DVP server computer 4. The client computer 9 of the buy-in requesting member and the member for whom the cost is to be paid with the invalid buy-in receives a broadcast notification of “buy-in invalid information notification” from the DVP server computer 4 at 17:00 on the buy-in execution date.

An outline of the flow of the business related to withdrawal of a buy-in request will be described. The execution date of the withdrawal of the buy-in request is X + 4 days or later, and is the day following the day after the execution of the buy-in has not been completed. The target member is a buy-in request member whose execution of the buy-in has not been completed.

The flow of data related to withdrawal of buy-in request will be described. Brand information for buy-in withdrawal is X
It is transmitted from the CSI server computer 12 to the DVP server computer 4 by 9:00 after +4 days. The notice to start accepting the withdrawal of the buy-in request is transmitted from the CSI server computer 12 to the DVP server computer 4 at 9:00 after X + 4. There is no broadcast notification to member 2.

[0712] The buy-in request withdrawal report acceptance start response is a notification that the buy-in request withdrawal request acceptance start notice has been received, and is transmitted from the DVP server computer 4 to the CSI server computer 12 at 9:00 on or after X + 4. You. Declaration for withdrawal of buy-in must be made at 9:00 on or after X + 4
~ 12: 00 DVP from client computer 9
The information is transmitted to the CSI server computer 12 via the server computer 4. The transmission source is a buy-in request member and a buy-in withdrawal member whose execution of the buy-in has not been completed, and there are three cases of a new report, a change report, and a cancellation report.

[0713] The notification of acceptance of the withdrawal of the buy-in request is a notification of the validity / invalidity of the withdrawal of the buy-in request, and is transmitted from the CSI server computer 12 to the DVP server computer 4 from 9:00 to 12:00 after X + 4. You.
There is no voluntary notice to Member 2. The notice of completion of acceptance of the withdrawal of the buy-in request is transmitted from the CSI server computer 12 to the DVP server computer 4 at 12:00 after X + 4. There is no broadcast notification to member 2.

[0714] The buy-in request withdrawal report acceptance end response is a notification that the buy-in request withdrawal report acceptance end notification has been received, and is transmitted from the DVP server computer 4 to the CSI server computer 12 after 12:00 on the X + 4th day. Is done. The end of the buy-in withdrawal declaration is a notification that all the buy-in withdrawal declarations have been transmitted, and the DVP server computer 4 sends the CS from the DVP server computer 4 after 12:00 on X + 4 days.
It is transmitted to the I server computer 12. The buy-in request withdrawal report end response is a notification that the buy-in request withdrawal report end has been received, and is transmitted from the CSI server computer 12 to the DVP server computer 4 at 12:00 on or after X + 4.

[0715] The functional outline of the CSI server computer 12 is as follows. The CSI server computer 12
By “9:00 on the day following the buy-in execution date,“ buy-in claim withdrawal target brand information ”is created and transmitted to the DVP server computer 4. The CSI server computer 12 transmits a “buy-in request withdrawal report acceptance start notification” to the DVP server computer 4 at 9:00 on the day after the buy-in execution date, and starts the accepting processing of the buy-in request withdrawal report.

The CSI server computer 12 is a DVP
Performs acceptance processing for the “buy-in request withdrawal declaration” received from the server computer 4 and sends the result to the DVP
Send it to server computer 4. The CSI server computer 12 transmits a “buy-in request withdrawal report acceptance completion notice” to the DVP server computer 4 at 12:00 the next day of the buy-in execution date, and the DVP server computer 4
Receives a “buy-in request withdrawal acceptance end response” and a “buy-in request withdrawal end” from the client, returns a “buy-in request withdrawal end response” to the DVP server computer 4, and accepts the buy-in withdrawal declaration. To end.

The function outline of the DVP server computer 4 is as follows. The DVP server computer 4 recreates the buy-in request withdrawal target table using the “buy-in request withdrawal target brand information” received from the CSI server computer 12 by 9:00 on the day following the buy-in execution date.

The DVP server computer 4 sends the CSI server computer 1 at 9:00 on the day following the buy-in execution date.
Upon receiving the “buy-in request for withdrawal report acceptance start notification” from 2, the request is within the claim withdrawal reception time, and a “buy-in request for withdrawal report acceptance start response” is transmitted to the CSI server computer 12. However, if the “buy-in request withdrawal target brand information” has not been received from the CSI server computer 12 yet, it will not be within the billing withdrawal acceptance time. Within the reception hours.

[0719] After receiving the "buy-in request withdrawal report" from the client computer 9, the DVP server computer 4 renumbers the withdrawal number (at the time of new filing), updates the version number, updates the withdrawal table of the buy-in request, and updates the CSI. A “buy-in request withdrawal declaration” is transmitted to the server computer 12. Further, the member 2 is notified in real time of the "temporary receipt" or "temporary cancellation" and the withdrawal number by "buy-in request withdrawal report upload notification". DVP server computer 4
Performs a check inside or outside the buy-in request withdrawal reception time, and if it is outside of the time, does not send it to the CSI server computer 12, but notifies the member 2 of the over-time error by "buy-in request withdrawal report upload notification".

The DVP server computer 4 updates the buy-in request withdrawal table with the “buy-in request withdrawal acceptance confirmation notice” received from the CSI server computer 12. When the DVP server computer 4 receives the “buy-in withdrawal withdrawal report acceptance completion notice” from the CSI server computer 12 at 12:00 the next day of the buy-in execution date, the DVP server computer 4 sets the CSI server computer 12 to “buy-in withdrawal acceptance time” "Request for withdrawal declaration acceptance end response" is transmitted. The DVP server computer 4 transmits all unsent “buy-in request withdrawal declaration” to the CSI server computer 12 and transmits “buy-in request withdrawal end” to the CSI server computer 12.

[0721] The functional outline of the client computer 9 is as follows. The client computer 9 of the buy-in billing member who has not completed the execution of the buy-in selects the bill to be withdrawn from the buy-in bill withdrawal declaration screen and selects the DV.
A “buy-in request withdrawal declaration” is transmitted to the P server computer 4.

The client computer 9 of the withdrawal request withdrawal member selects the withdrawal report to be changed from the buy-in request withdrawal reception status table, changes the withdrawal request,
A “buy-in request withdrawal declaration” is transmitted to the DVP server computer 4. The client computer 9 of the buy-in request withdrawal member selects a request for withdrawal declaration to be canceled from the buy-in request withdrawal reception status table, and transmits a “buy-in request withdrawal report” to the DVP server computer 4.

[0723] The outline of the flow of operations related to the confirmation of the status of each buy-in application acceptance status will be described. The date of conducting the buy-in application acceptance status confirmation is every day, and the target members are all members.

The flow of data related to each buy-in application reception status confirmation-related will be described. The buy-in request acceptance status request is transmitted from the client computer 9 of all members to the DVP server computer 4 as needed every day. The buy-in request acceptance status data is transmitted from the DVP server computer 4 to the client computer 9 of the requesting member as needed every day.

[0725] The buy-in order reception status request is transmitted from the client computers 9 of all members to the DVP server computer 4 as needed every day. The buy-in order reception status data is transmitted from the DVP server computer 4 to the client computer 9 of the requesting member every day at any time. The buy-in request withdrawal reception status request is transmitted from the client computers 9 of all members to the DVP server computer 4 as needed every day. The buy-in request withdrawal reception status data is transmitted from the DVP server computer 4 to the client computer 9 of the requesting member as needed every day.

[0726] Each buy-in application reception status confirmation relationship includes C
SI server computer 12 is irrelevant. The functional outline of the DVP server computer 4 is as follows. DV
Upon receiving the “buy-in request acceptance status request” from the client computer 9, the P server computer 4 searches the buy-in request table and transmits the search result to the client computer 9 that has received the request.

The DVP server computer 4 sends a “buy-in order reception status request” from the client computer 9.
Upon receiving the request, the buy-in order table is searched, and the search result is transmitted to the client computer 9 that has received the request. Upon receiving the “buy-in request withdrawal reception status request” from the client computer 9, the DVP server computer 4 searches the buy-in request withdrawal table and transmits the search result to the client computer 9 that has received the request.

The function outline of the client computer 9 is as follows. The client computer 9 is a DV
A “buy-in request acceptance status request” is transmitted to the P server computer 4. Client computer 9 for all members
Has this transmission function. When the client computer 9 receives the “buy-in request reception status data” from the DVP server computer 4, it displays it in the buy-in request reception status table.

The client computer 9 sends a “buy-in order reception status request” to the DVP server computer 4. The client computers 9 of all members have this transmission function. Upon receiving the “buy-in order reception status data” from the DVP server computer 4, the client computer 9 displays the data in the buy-in order reception status table. The client computer 9 is a DVP
A “buy-in request withdrawal acceptance status request” is transmitted to the server computer 4. Client computer 9 for all members
Has this transmission function. When the client computer 9 receives the “buy-in request withdrawal reception status data” from the DVP server computer 4, the client computer 9 displays the buy-in request withdrawal reception status table.

The authentication of the user and the check of the authority are performed in the processing of the WWW server computer 5 which calls the entry processing, and are not performed in the entry processing. In the case of a user who cannot perform a certain entry process, the WWW server computer 5 is prevented from executing the entry process.

[0731] The functional range of the CSI server computer 12 will be described. The CSI server computer 12
As described below, information of each entry business is exchanged with the DVP server computer 4. That is, the CSI server computer 12 transmits to the DVP server computer 4 the buy-in bill target brand information, the buy-in order target brand information, and the buy-in bill withdrawal target brand information. In addition, the DVP server computer 4
To start the reception process for each entry business. DV
Each entry business report notification received from the P server computer 4 is passed to the reception process of each entry business. Each entry business reception confirmation notice output from the reception process of each entry business is transmitted to the DVP server computer 4. DVP server computer 4 notifies the end of acceptance of each entry business
When receiving the reception completion confirmation notice and the declaration end message of each entry business from the DVP server computer 4, the reception process of each entry business is completed. The declaration end message of each entry job is transmitted to the DVP server computer 4.

[0732] The functional range of the DVP server computer 4 will be described. The DVP server computer 4 uses the CS
The I-server computer 12 and the client computer 9 control transmission and reception of information of each entry business and store information.

[0733] That is, the CSI server computer 12
If an entry business report request is received from the client computer 9 during a time period until the reception of each entry reception start notification or after receiving each entry reception end notification, an error notification outside the reception time is sent to the client computer 9. Send. Further, it creates and records each entry target issue information from the buy-in request target issue information, the buy-in order target issue information, and the buy-in request withdrawal target issue information received from the CSI server computer 12. CS
When receiving the reception start notification and the reception end notification of each entry business from the I server computer 12, each entry business is started / terminated, and a reception response is returned to the CSI server computer 12. Upon receipt of each entry business declaration notification from the client computer 9, it is provisionally received or temporarily canceled, recorded in each entry business table, and transmitted to the CSI server computer 12. Upon receipt of the normal acceptance confirmation notice of each entry business declaration from the CSI server computer 12, this receipt or cancellation is determined and recorded in each entry business table. Even if each entry business acceptance notification is received from the CSI server computer 12, each entry business declaration notification that has been received from the client computer 9 but has not been transmitted to the CSI server computer 12 is received by the CSI server computer 12.
The data is transmitted to the SI server computer 12. Subsequent to the transmission of each entry business report notification to the CSI server computer 12, a report completion message of each entry business is transmitted to the CSI server computer 12, and a report completion response message of each entry business is received from the CSI server computer 12.

[0734] Upon receiving a new declaration notification of each entry business from the client computer 9, each entry business number is assigned in units of business dates. Version number management common to each entry business is as follows. Manages the version number of the declaration notice for each business date and each entry business number. When a notification of the entry business is received from the client computer 9, the version number is provisionally updated. The version number is determined at the point in time when the CSI server computer 12 returns a notification of the completion of each entry business reception confirmation. CSI server computer 1
When the entry business acceptance confirmation notice of the entry error of the reception error is returned from 2, the version number is canceled and the version number management is not performed. When the version number of the notification of cancellation of each entry work is determined, the version number is completed, and thereafter, the version number is not updated. Only the latest version that can be updated is subject to change / cancellation of each entry business (only the confirmed version). Version management unique to withdrawal of buy-in requests is as follows. In other words, a claim can be withdrawn on a billing date basis, but can only be withdrawn from the oldest billing date.

If a plurality of declarations of the same brand are received from the same member 2 on the same day in the new declaration of the buy-in request and the new declaration of the withdrawal of the buy-in request, an error notification is returned to the client computer 9. The same member 2 on the same day with a new buy-in order application
If the self / consignment category receives a plurality of applications for the same brand and the same price at the same price, an error notification is returned to the client computer 9.

Upon receiving each entry reception status information reference request from the client computer 9, the DVP server computer 4 retrieves the entry reception status data of the requesting member 2 for today from each entry business table and receives the request. Send to client computer 9.

The function range of the client computer 9 will be described. Input of each entry business declaration made by the client computer 9 and the DVP server computer 4
Will be described. The client computer 9 allows the user to input a declaration of each entry business from the browser screen.

[0738] The declaration of each entry business includes a buy-in claim report, a buy-in bill change, a buy-in bill cancel, a buy-in order application, a buy-in order change, a buy-in order cancel,
There are buy-in claim withdrawal declaration, buy-in claim withdrawal change, and buy-in claim withdrawal. On the buy-in claim screen,
The selection items are target brands (selection from the pull-down menu),
The input item is the billing amount, and the automatic display item is the scheduled buy-in execution date and current date.

[0739] On the screen for changing the buy-in request, the selection items are the target claim report (selection from the buy-in request reception status table),
The input item is the billing quantity, and the automatic display items are the current date, the scheduled date of the buy-in execution, the billing number, the brand name, and the brand code. On the screen for canceling the buy-in request, the selection item is a target claim report (selection from the buy-in request reception status table). On the buy-in order application screen, the selected items are the target brand (selection from the pull-down menu), the self / consignment category (selection with the radio button), the input items are the order price, the order quantity, and the automatic display item is the current date.

[0740] On the buy-in order change screen, the selection items are target order application (selection from the buy-in order reception status table),
The input items are the order quantity, and the automatic display items are the current date, order number, brand name, brand code, order price, and self / consignment category. On the screen for canceling the buy-in order, the selected item is the target order application (selection from the buy-in order reception status table).

[0741] On the buy-in request withdrawal declaration screen, the selection items are the target brand (selection from the pull-down menu), the target request (selection from the buy-in request withdrawal target list), and the automatic display item is the current date. On the screen to change the withdrawal of the buy-in request, the selection items are the target withdrawal declaration (selection from the buy-in request withdrawal status table) and the target request (selection from the buy-in withdrawal target list). , Withdrawal number, brand name and brand code.

On the screen for canceling the withdrawal of the buy-in request, the selected item is a target claim withdrawal declaration (selection from the buy-in request withdrawal status table). As input checks, the client computer 9 performs a check of essential items, a numerical check of numeric items, a maximum value check of each quantity, and a multiple of the trading unit of each quantity.

[0743] The client computer 9 creates a report message for each entry job from the input data, and sends it to the DVP server computer 4. When the DVP server computer 4 receives a CSI server computer 12 upload notification of each entry business declaration, the client computer 9 updates the new input screen or the reception status table.

[0744] The client computer 9 refers to each entry business reception status. That is, the client computer 9 creates each entry business reception status search request message and transmits it to the DVP server computer 4.
When the client computer 9 receives each entry business reception status result from the DVP server computer 4,
A list of received data is displayed in each entry business reception status table on the browser.

The cooperation between the DVP server computer 4 and the client computer 9 is based on Java (registered trademark) / C
ORBA (Common Object Requests)
(tBroker Architecture) cooperation. What is Java (registered trademark) / CORBA cooperation?
This is a mechanism for realizing CORBA cooperation using Java (registered trademark). Netscape Navigat
Java that connects an ORB with an applet dynamically downloaded from the WWW server computer 5 to transfer HTTP protocol, parameters and processing results using a browser having a Java (registered trademark) virtual machine such as or.
va (R) / CORBA Gateway and IIOP
Use a protocol. By using this cooperation function and the transaction function of CORBA together, an efficient and highly reliable communication path can be used from the browser. FIG. 86 shows the DV
P server computer 4 and client computer 9
FIG. 3 is a diagram illustrating an interoperation mode.

The corresponding client-side entry processing program 521-01 performs buy-in request processing, buy-in order processing, and buy-in request withdrawal processing. In the corresponding server-side entry processing program 521-02, the buy-in bill report entry information download processing, the buy-in billing target brand information search processing, the buy-in bill report processing, the buy-in bill report acceptance confirmation processing, the buy-in order application entry information download processing, the buy-in order target Brand information search processing, buy-in order application processing, buy-in order application acceptance confirmation, buy-in request withdrawal entry entry information download processing, buy-in request withdrawal target list search processing, buy-in withdrawal target billing information search processing, buy-in request withdrawal It performs a reporting process, a buy-in request withdrawal report reception confirmation process, a buy-in request reception status search process, a buy-in order reception status search process, and a buy-in request withdrawal reception status search process.

The corresponding communication data of Java (registered trademark) / CORBA cooperation is as follows. The buy-in declaration is transmitted from the client computer 9 to the DVP server computer 4. There are three cases: new filing, change filing, and cancellation filing. The upload notification of the buy-in claim report is used to transfer the buy-in claim report information to the CSI server computer 1.
2 is transmitted from the DVP server computer 4 to the client computer 9. There are three cases: new filing, change filing, and cancellation filing. An error such as a case outside the reception hours is also notified to the client computer 9 by this notification.

The buy-in order application is transmitted from the client computer 9 to the DVP server computer 4.
There are three cases: new application, change application, and cancellation application. The buy-in order application upload notification is a notification of whether or not the buy-in order application information has been transmitted to the CSI server computer 12, and is transmitted from the DVP server computer 4 to the client computer 9. There are three cases: new application, change application, and cancellation application. In the case of outside the reception time, the client computer 9 is notified by this notification.

[0749] The buy-in claim withdrawal report is transmitted from the client computer 9 to the DVP server computer 4. There are three cases: new filing, change filing, and cancellation filing. The buy-in request withdrawal report upload notification is a notification of whether or not the buy-in request withdrawal report information has been transmitted to the CSI server computer 12, and is transmitted from the DVP server computer 4 to the client computer 9. There are three cases: new filing, change filing, and cancellation filing. In the case of outside the reception time, the client computer 9 is notified by this notification.

[0750] The buy-in bill target issue information request is a search request for buy-in request target issue information for each member 2, and is transmitted from the client computer 9 to the DVP server computer 4. The buy-in billing issue information is the buy-in billing issue information for each member 2 and is transmitted from the DVP server computer 4 to the client computer 9.

The buy-in order target brand information request is a search request for buy-in order target brand information, and is transmitted from the client computer 9 to the DVP server computer 4. The buy-in order target issue information is buy-in order target issue information, and is transmitted from the DVP server computer 4 to the client computer 9. The buy-in withdrawal target issue list request is a search request for the buy-in withdrawal target issue list for each member 2, and is transmitted from the client computer 9 to the DVP server computer 4.

The buy-in withdrawal target issue list is a list of buy-in withdrawal target issues for each member 2 and is transmitted from the DVP server computer 4 to the client computer 9. Request for bill-in withdrawal target claim information is Member 2
This is a search request for withdrawal target billing information of a certain brand, and is transmitted from the client computer 9 to the DVP server computer 4. The buy-in claim withdrawal target billing information is one brand's withdrawal target claim information for each member 2 and is transmitted from the DVP server computer 4 to the client computer 9.

[0753] The buy-in request reception status request is a search request for the buy-in request reception status information for each member 2, and is transmitted from the client computer 9 to the DVP server computer 4. The buy-in request reception status information is the buy-in request reception status information (for the current day) for each member 2, and is transmitted from the DVP server computer 4 to the client computer 9.

[0754] The buy-in order reception status request is a search request for the buy-in order reception status information for each member 2, and is transmitted from the client computer 9 to the DVP server computer 4. The buy-in order reception status information is the buy-in order reception status information (for the current day) for each member 2, and is transmitted from the DVP server computer 4 to the client computer 9.

[0755] The buy-in request withdrawal reception status request is a search request for the buy-in request withdrawal reception status information for each member 2, and
It is transmitted from the client computer 9 to the DVP server computer 4. The buy-in request withdrawal reception status information is the buy-in request withdrawal reception status information (for the current day) for each member 2 and is transmitted from the DVP server computer 4 to the client computer 9.

[0756] Fig. 87 is a diagram showing members 2, etc., the stock exchange WAN system 1, and the DVP settlement system 3 in this embodiment.
FIG. 9 is a diagram showing an outline of a process between the steps. In the stock exchange WAN system 1, connection / access management processing 531-01,
Broadcast notification processing 531-02, information distribution processing 531-0
3. Perform entry processing 531-04.

[0757] That is, in the stock exchange WAN system 1, in the connection / access management processing 531-01, the access management status monitoring processing 531-15 is performed. When the client computer 9 of the member 2 enters the user ID and password from the WWW browser screen to perform the authentication procedure processing 531-11, the stock exchange WAN system 1 confirms the user ID and password and permits access. The process 531-12 is performed. After that, on the stock exchange WAN system 1 side, the member 2 side and the stock exchange WA
The N system 1 performs status monitoring processing 531-14 such as connection with the system 1. Also, on the stock exchange WAN system 1, the person in charge of the stock exchange 14 monitors the access status and the information delivery on the terminal computer.

[0758] In the broadcast notification processing 531-02, when the data linkage processing 531-22 is performed from the payment information file 13 of the DVP payment system 3, the stock exchange WAN system 1 side prepares the payment data distribution preparation processing 531-22. Is performed. The payment data is stored in the distribution payment information file 531-31, and the payment data distribution preparation processing 531-22 is performed.
Is completed, a broadcast notification process 531-23 is performed.
This broadcast notification process 531-23 corresponds to a deliverable information delivery procedure.

[0759] In the broadcast notification processing 531-23, the delivery possible notification processing 5 from the stock exchange WAN system 1 to the member 2 side is performed.
31-24 is performed, and the broadcast confirmation notification processing 531-25 is performed from the member 2 to the stock exchange WAN system 1. On the member 2 side, the contents of the distribution available notification can be confirmed on a dedicated screen or the like of the broadcast notification program 11c.
The client computer 9 which is the business server computer of the member 2 receives the message. The process of displaying on the client computer 9 screen of the member 2 is
This corresponds to the distributable information list screen display procedure.

In the information distribution process 531-03, in response to an information distribution request from the client computer 9 side, the stock exchange WAN system 1 acquires information from the distribution settlement information file 531-31, and executes the information distribution process 531. −
Perform 32. The information distribution request from the client computer 9 corresponds to a browse data request transmission procedure, and the information distribution processing 531-32 corresponds to a browse information distribution procedure. When the information distribution process 531-32 is performed, the member 2 performs the information browsing / receiving process 531-34 from the stock exchange WAN system 1. The received information can be confirmed on the WWW browser screen. The processing to be displayed on the screen of the client computer 9 corresponds to the browsing information receiving and displaying procedure. From the member 2 side, the stock exchange WAN system 1
A confirmation process 531-35 to the effect that information has been delivered is transmitted to the server.

[0764] When a download request is issued from the member 2 side, the stock exchange WAN system 1 performs a download process 531-33. Download processing 53
In 1-33, the member 2 side downloads information 53
Perform 1-36. This download processing 531-36
Corresponds to the download information distribution procedure. The member 2 receives the data with the WWW browser 11b or the settlement data with the business server computer. Member 2
The side transmits an acquisition confirmation notice to the effect that the information for download has been acquired to the stock exchange WAN system 1 side.

In the entry processing 531-04, the stock exchange WAN system 1 executes the entry transmission / reception processing 531
Perform 41. The member 2 performs entry processing 531 to 42 of information input from the WWW browser screen. The stock exchange WAN system 1 performs an entry reception process 531-43 of the received information. The stock exchange WAN system 1 communicates with the DVP settlement system 3 and the data linkage processing 531-
46, 531-47, and the DVP settlement system 3 performs entry content confirmation processing 531-48. The stock exchange WAN system 1 performs data linkage processing 531-46, 5
When the entry contents are acquired from the DVP settlement system 3 by 31-47, the result transmission processing 531-44 is performed, and
An entry result transmission process 531-45 is performed on the member 2 side. The member 2 checks the entry result on the WWW browser screen.

FIGS. 88 to 95 are explanatory diagrams showing screen transitions and the like in FIG. 87. FIG. 88 shows a WWW browser 1 used between the member 2 and the stock exchange WAN system 1.
FIG. 2 is a diagram showing a relationship between 1b and a broadcast notification program 11c (API 11a). FIG. 89 is a diagram showing information classification in the conventional example of the WWW screen provided by the stock exchange 14 (conventional WWW
FIG.

[0764] Information classification (configuration of screen switching tab) on the WWW screen will be described. In the screen switching tab of the present embodiment, the payment information is roughly classified into payment business units.
In this way, by classifying business units that differ depending on the company but are highly versatile, it is possible to expect an effect of simply displaying a display screen and improving operability. In addition, it is expected that the transaction type and system will change in the future, but it is unlikely that such a change in the transaction type or system will cause a large change in the classification of the settlement business,
It is preferable to classify the payment information in units of payment business. In addition, since some settlement information handles a plurality of transaction types, it is difficult to adopt as a unit of classification, and non-DVP
Since various types of transactions are involved in transactions, the screen configuration and hierarchy etc. are complicated, operability is impaired, and changes in new transaction types and systems are likely to affect the screen configuration and hierarchy. However, it is not preferable to use the classification of the transaction type unit.

In this embodiment, the “screen switching tab” is configured based on the settlement business. As screen switching tabs, there are “Home”, “Verification business”, “Settlement business”, “Collateral management”, “Fail management”, “Information inquiry”, and “Help” tabs. Of these tabs, "Reconciliation", "Settlement", "Collateral Management"
“Fail management” is a business associated with the DVP settlement system, and “collation business”, “settlement business”, “collateral management”, “fail management”, and “information inquiry” are businesses involved in transactions other than DVP settlement. In the present embodiment, the business name is displayed on the screen switching tab as described above.

FIGS. 90 to 95 are diagrams showing information classification on the WWW screen. That is, FIG. 90 is a diagram showing the configuration of the page switching menu, and FIGS. 91 to 95 are diagrams showing the configuration of the information screen page.

[0767] Next, regarding the login / logout operation performed at the start or end of use of the settlement information system provided by the DVP server computer 4, the client computer 9 of the member 2 uses the WWW browser 11b used to browse the deliverable information. The operation will be mainly described. Note that the distribution available notification network system according to the present invention is included in the settlement information system.

In this embodiment, since access management / connection state management is performed, a single login method is adopted. The single login method is performed for all users who access the stock exchange WAN system 1. That is, only one user can access at the same time with one user ID. While a specific user is accessing the payment information system, another user cannot use the payment information system using the same user ID.
When a plurality of users use the payment information system, it is necessary to adjust the access time for each user or to apply for user IDs by the number of users.

[0769] The login operation will be described. After starting the WWW browser 11b, a predetermined URL is inputted to the browser 11b.
Of the payment information system shown in FIG. 96 is displayed. When the Target logo 300 on the screen is clicked with a mouse, an authentication window is displayed. Enter the user ID and password for which the registration procedure for the payment information system WAN user has been completed,
Click the "OK" button.

[0770] If incorrect authentication information is entered, a screen stating "Authentication failed. Do you want to retry?" Is displayed. To retry, click "OK". Check the authentication information and enter it again. If you do not want to try again, click Cancel to end the operation. Once the user ID and password are authenticated,
Login is completed, and a home screen corresponding to the access authority of the user ID is displayed.

[0771] Unless the Cookie is accepted, the settlement information system cannot be accessed. "Browser Co
If okie is disabled, please enable it. "
Is displayed at the time of the login operation, the setting of the WWW browser 11b being used is changed to Co.
Change to enable okie.

[0772] The termination operation (logout) of the payment information system is executed in the following procedure. When the use of the payment information system is completed, click the logout menu button on each screen. As a result, a logout confirmation screen of "Are you sure you want to log out?" Is displayed. Click the OK button to log out. When the logout is completed normally, the display returns to the top screen of the payment information system. At this stage, the user ID used so far can be used by other users.

[0773] The payment information system adopts a single login system in which another user cannot access using the same user ID while a user is transmitting and receiving information using a specific user ID. Therefore, if the "logout" operation is not executed at the time when the information transfer is completed, other users cannot access the system using the same user ID. A correct logout operation cannot be executed using a closed box or an end menu of the WWW browser 11b.

[0774] When another user accesses the same user ID while viewing payment information or the like (during login), a warning screen indicating "login rejected" is displayed. Clicking the OK button on the warning screen rejected the login, such as "The entered user ID is being connected normally from another client computer. You must close all browsers and log in again." The "Login Error Screen" showing the reason is displayed.

After clicking the OK button on the “login error screen”, a few seconds later, “Do you want to close the window?”
Is displayed. If the user clicks the OK button, the WWW browser screen in use is closed.
If the error "The entered user ID is normally connected from another client computer. You need to close all browsers and log in again.", An unused user ID at the time of login It is better to use and access again.

[0776] When the error "The entered user ID is normally connected from another client computer. It is necessary to log in again after closing all browsers once" is displayed, a plurality of WWWs are displayed. When the browser screen is open, it is preferable to close all the screens once and then execute the login operation again. Depending on the version of the WWW browser 11b, the authentication information once entered may be stored, and this storage may be recognized as a double login and an error may occur. At this point, the WWW browser 11b is terminated.

[0777] When the user A who has accessed the payment information system has left the WWW browser 11b displayed for a certain period of time and has been left unattended, another user B uses the same user ID and enters the payment information system. It becomes possible to access. In this case, if the other user B logs in to the payment information system with the same user ID, and the user A who has been using so far attempts to perform another operation on the payment information system, the "processing" The connection has been disconnected due to a timeout. The connection is currently being established normally from another client computer. It is necessary to close all browsers and then log in again. " Unable to use until person B logs out.

While a specific user A has left the WWW browser 11b displayed for a certain period of time, another user B
If the user logs out after accessing the payment information system using the same user ID, the user A who has been left during that time can continue to use the payment information system.

[0779] An error occurring due to single login and a countermeasure will be described. "Input user ID
Is connecting normally from another client. Once you close all browsers, you need to log in again. Is issued, this error has occurred because another user is accessing the payment information system using the same user ID. If the other user logs out of the system, the error is resolved.

[0780] "Connection has been disconnected due to processing time-out. Normal connection is currently being established from another client.
Once you close all browsers, you need to log in again. Is issued, this error is caused by the fact that a certain period of time has passed after accessing with the currently used user ID, and that another user has temporarily accessed using the same user ID. After a certain period of time has elapsed since the access occurred or with the currently used user ID, after another user has temporarily accessed using the same user ID, the other user will follow the correct procedure. This is caused by not executing the logout operation. The same user ID cannot be used for a certain period of time. If another user logs out of the payment information system, the error will be resolved. Alternatively, after a certain period of time, the same user ID can be used again due to timeout.

At the time of the logout operation, if an error warning "The current time is not being logged in due to timeout" is given, this error means that a certain period of time has passed after accessing with the currently used user ID. This is caused by another user temporarily accessing using the same user ID. For this reason, the logout operation of the user who has been used until now becomes invalid.

[0782] This user ID cannot be used. After the error screen is displayed, the screen returns to the authentication screen. Therefore, once the WWW browser 11b is completely closed, access is made with another user ID. The time required for the timeout to occur or to be eliminated may be appropriately adjusted by the WAN administrator in consideration of the usage situation and the like. Considering the general access time of the user, it is preferable to adjust to about 10 minutes.

FIG. 97 is a diagram showing a login / logout operation. FIG. 97 (a) shows a login method in the operation of the WWW browser 11b. As shown in FIG. 97 (a), while user A is using, user B cannot log in using the same user ID. After the user A has successfully logged out, the user B can log in using the same user ID. After a certain period of time in which the user A does not use, the user A can log in using the same user ID.

FIG. 97 (b) is a diagram showing patterns of user IDs that can be used simultaneously. As shown in FIG. 97 (b), the WWW browser 11b and the broadcast notification program 11c
(Or API 11a) can be used simultaneously using one user ID. However, the broadcast notification program 11c and the broadcast notification API 11a cannot be used simultaneously using one user ID.

[0785] The WWW server computer 5 manages the connection status. Hereinafter, “operating browser” refers to a browser operated by a predetermined user, and “another browser” is a browser different from the operating browser and uses the same user ID as the predetermined user. Refers to the browser that is operated. When the user logs in using the predetermined ID, three possible cases are considered in which the connection status is assumed to be "normal end", "processing", or "abnormal end / process timeout" as the monitoring status. here,
The connection status for which the monitoring status "Successfully completed" is displayed
When the logout has been completed normally and this monitoring status is displayed, both the operating browser and the browsers other than the operating browser can log in.

[0786] The connection status in which the monitoring status "processing in progress" is displayed is a case where the user is continuing the operation after the normal login (= the fixed time has not elapsed).
When this monitoring status is displayed, the operating browser is operable, but browsers other than the operating browser cannot log in / operate.
The connection status where the monitoring status “abnormal termination / processing timeout” is displayed is a case where a certain time has elapsed from the last access time without normal logout. For example, this case corresponds to the case where the browser is left after logging in. When this monitoring status is displayed, the operating browser is operable, and browsers other than the operating browser can log in. In this case, the browser that is being operated (the browser after a certain period of time) among the browsers other than the browser that is being operated may be allowed to continue the operation.

[0787] The monitoring target is "normal end" or "processing in progress".
It will be monitored by the monitoring status of “abnormal termination / processing timeout”. The monitoring targets are four groups: a person in charge of the securities handling group (possible entry), a person in charge (no entry possible), a person in charge of securities trading group (possible entry), and a person in charge (no entry possible). The user that belongs.

FIG. 98 is a flowchart in the case of normal login. W by the user on the client computer 9
When the start of the WWW browser 11b is instructed, the WWW browser is started, a predetermined address is input on the WWW browser 11b, and the process starts. First, step S541
At -01, the input predetermined address is accessed.

Next, in step S541-02, encrypted communication is started. In step S541-03, authentication processing of the "user ID" and "password" input on the top screen is performed. That is, it is checked whether the user ID and the password match, and if they do not match, the login is rejected. If they match, "User I
D "and" password "are authenticated.

[0790] Next, in step S541-04, it is determined whether the connection status of another browser is "processing". When the connection status of another browser is "processing" (step S5
41-04: Yes), in step S541-08, an error display A indicating "the input user ID is being connected normally from another client" is displayed, and the process ends. When the connection status of another browser is either “normal end” or “abnormal termination / processing timeout” and the connection status of another browser is not “processing” (step S
541-04: No), the login is permitted as "single login", and in step S541-05, the screen transits to the initial screen for operation.

Next, in step S541-06, the connection status of the operating browser is "processing" or "abnormal termination /
It is determined whether or not "processing timeout". When the connection status of the operating browser is "processing" or "abnormal termination / processing timeout" (step S541-06: Ye)
s) In step S541-07, the operation is continued. If the connection status of the operating browser is “normal end” and the connection status of the operating browser is not “processing” or “abnormal termination / processing timeout” (step S541-06: No), the process proceeds to step S541-07. ,
It is determined whether or not the connection status of another browser is “processing”.

[0792] If the connection status of another browser is "processing" (step S541-07: Yes), that is, the connection status of the operating browser is "normal end" and the connection status of another browser is "processing". In this case, step S54
In step 1-10, an error display A indicating "the input user ID is being connected normally from another client" is displayed on the screen, and the process ends.

If the connection status of another browser is not "processing" (step S541-09: No), step S5
At 41-11, it is determined whether or not the connection status of another browser is "abnormal termination / processing timeout". If the connection status of another browser is "abnormal termination / processing timeout" (step S541-11: Yes), that is, the connection status of the operating browser is "normal termination" and the connection status of another browser is "abnormal termination / processing timeout". Is displayed, an error message C is displayed on the screen at step S541-12, stating that "Connection has been disconnected due to processing timeout. Normal connection is currently being established from another client", and the processing ends. .

[0794] When the connection status of another browser is not "abnormal termination / processing timeout" (step S541-11:
No), that is, when the connection status of the operating browser is “normal termination” and the connection status of another browser is “normal termination”, in step S541-13, “the connection has been disconnected due to processing timeout” on the screen. Please launch the browser again and log in. "And terminate the process. Thus, the processing in FIG. 98 ends.

FIG. 99 is a flowchart in the case of normal logout. When the user selects “logout” from the operation menu on the WWW browser 11b of the client computer 9, the process starts. First, in step S542-01, it is determined whether the connection status of the operating browser is "processing" or "abnormal termination / processing timeout". The connection status of the operating browser is "normal end"
If the connection status of the operating browser is not “processing” or “abnormal termination / processing timeout” (step S542-01: No), step S542-05 is performed.
Then, it is determined whether or not the connection status of another browser is “processing”.

If the connection status of the operating browser is “processing” or “abnormal termination / processing timeout” (step S542-01: Yes), it is determined that normal login is being performed, and the screen is displayed on the screen in step S542-02. A logout permission confirmation screen asking whether logout is permitted is displayed, the user is confirmed whether logout is permitted, and it is determined whether a logout instruction is issued. If no logout instruction has been given on the logout availability confirmation screen (step S54)
2-02: No), the process ends.

[0797] When a logout instruction is given on the logout availability confirmation screen (step S542-02: Yes, at step S542-03, it is again determined whether the connection status of the operating browser is "processing" or "abnormal termination / processing timeout". If the connection status of the operating browser is "processing" or "abnormal termination / processing timeout" (step S542-03: Yes), it is determined that the normal login is being performed, and the encrypted communication is performed in step S542-04. To log out, display a logout completion screen, and end the process.

[0798] The connection status of the operating browser is "normal termination".
If the connection status of the operating browser is not “processing” or “abnormal termination / processing timeout” (step S542-03: No), step S542-05 is performed.
Then, it is determined whether or not the connection status of another browser is “processing”.

[0799] When the connection status of another browser is "processing" (step S542-05: Yes), that is, the connection status of the operating browser is "normal end" and the connection status of another browser is "processing". In this case, step S54
At step 2-06, an error display A indicating "the input user ID is being connected normally from another client" is displayed on the screen, and the process ends. If the connection status of another browser is not “processing” (step S542-05: No), it is determined in step S542-07 whether the connection status of another browser is “abnormal termination / processing timeout”.

When the connection status of another browser is “abnormal termination / processing timeout” (step S542-07:
Yes), that is, when the connection status of the operating browser is “normal termination” and the connection status of another browser is “abnormal termination / processing timeout”, step S542-08.
On the screen, "The connection has been disconnected due to a processing timeout. The other client is currently connecting normally."
Is displayed, and the process ends.

If the connection status of another browser is not “abnormal termination / processing timeout” (step S541-07:
No), that is, when the connection status of the operating browser is “normal end” and the connection status of another browser is “normal end”, in step S542-09, “the connection is disconnected due to processing timeout” is displayed on the screen. Please launch the browser again and log in. "And terminate the process. Thus, the processing in FIG. 99 ends.

The status of each of the error displays A to C displayed on the screen in the flow of FIG. 98 and FIG. 99 is as follows.
Error A "The input user ID is normally connected from another client" indicates that the user is normally connected on another machine, and that the user has not logged out normally and a certain period of time has passed. Displayed when not available.

[0803] The error B of "The connection has been disconnected due to processing timeout. Please start the browser again and log in."
If a processing timeout occurs (a certain period of time has passed, the browser remains displayed), then the machine 2 logs in normally, logs out normally, and then accesses the machine 1 with the browser displayed as it is Will be displayed.

[0804] "Connection has been disconnected due to processing timeout. Another client is currently connecting normally."
Error C indicates that the process timed out (after a certain period of time, the browser remains displayed) after the normal login on the machine 1, and then the machine 2 is normally logged on, and is normally being processed, or Displayed when the specified time has not passed without logging out.

Next, access right management will be described. In the access right management, information receivable by the broadcast notification program 11c is managed by the access right. The information on the access right is set in the access right management on the WWW browser 11b. First, in the payment information system,
Two site managers who are responsible for managing each site are appointed. At each site, a site administrator manages WAN users of the site. In the present embodiment, the access right is set in the settlement information system. However, the present invention is not limited to this, and the access right of the entire stock exchange WAN system 1 provided by the stock exchange 14 and limited to the member 2 is set. In the settlement information system, the same access right may be used.

[0806] In the settlement information system, due to the nature of the business to be handled, the WAN users who are in charge of the respective operations of the securities handling manager and the securities trading manager specified in the business rules are grouped, and the securities handling manager group 301a is formed. A security trading group 301b is configured to limit users who can exchange information related to settlement business. As shown in FIG. 100, each group is composed of responsible persons 302a and 302b, persons in charge (possible entry) 303.1a and 303.1b, and persons in charge (entry impossible) 303.2a and 303.2b. The managers 302a and 302b appoint the WAN users 305 of the group to which the managers belong and grant access rights necessary for business.

[0807] The responsible persons 302a and 302b of each group.
Is selected by the site administrator 304 from the existing WAN users 305 in a range of up to two people. The responsible person 302
a, 30b, assignees 303.1a, 30
For 3.1b, 303.2a, and 303.2b, the site administrator 304 prepares required WAN users in advance. The persons in charge 303.1a, 303.1b, 3
There is no limitation on the numbers of 03.2a and 303.2b.

[0808] In the payment information system, as shown in Fig. 101, the management of user information is operated in the following system.
In this figure, the responsible persons 302a and 302b
And the persons in charge 303.1a, 303.1b, 303.2
a, 303.2b is displayed as the person in charge 303. The site administrator 304 creates and changes the WAN user 305. The site administrator 304 sets each group 301a, 30
The person in charge 1b is appointed. The responsible person 302 selects a person in charge 303 belonging to each of the groups 301a and 301b. The responsible person 302 is the responsible person 302 and the person in charge 303
, An access right for giving and receiving information related to the settlement business.

[0809] In the settlement information system, users are managed by the following four types of access rights. As the access right of the site administrator's authentication permission, the site administrator 304
Can access the settlement information system within the range of appointing the responsible person 302 of each group 301a, 301b.

[0810] The person in charge 302 selected by the site administrator 304 as an access right for authentication permission of the person in charge can access the settlement information system. As the access right for the authentication permission of the person in charge, the person in charge 30 selected by the person in charge 302
3 has access to the payment information system. Each person in charge 303 (including the person in charge 302) can send and receive information within the range of the authority assigned by the person in charge 302 as the access authority related to the transfer of information related to the settlement business.

The setting of the access right in the settlement information system is as follows. Among the above types of access rights, regarding the transfer of information related to the settlement business, the work that can be handled differs depending on the group to which the user belongs. In other words, the securities handling manager group 301a can send and receive information related to collation work, settlement business, collateral management, and fail management, but cannot send and receive information related to buy-in orders.

[0812] Also, securities trading manager group 301
b is a collation operation and a fail-in notification of a buy-in,
You can exchange information about buy-in orders,
Information related to fail management other than settlement business, collateral management, and buy-in notification cannot be given or received. Each person in charge 30
2a, 302b, persons in charge 303.1a, 303.1b,
The business that can be handled by 303.2a and 303.2b is shown in FIG.
02. The site administrator 304 cannot handle any of collation, settlement, collateral management, fail, and buy-in order.

[0813] Note that the "collation business" in FIG. 102 includes a domestic stock trading schedule, a bond transaction trading schedule, a summary, and exercise of rights.
This includes notification of confirmation and designation of the other party, and “collateral management” includes collateral deposited on the previous day and margin. The “fail notification” of the “fail” includes a fail information notification,
The “buy-in notification” includes a buy-in information notification, a buy-in execution notification, and a buy-in execution result notification, and the “buy-in request” includes a buy-in request and withdrawal of a buy-in request.

In the range of authority in each group, the authority level can be set for the responsible person 302 and the person in charge 303 as follows. That is, the responsible person 302
The access rights a and 302b can be set for all information that can be exchanged within the group 301a or 301b.

[0815] Also, person in charge (possible entry) 303.1
a, 303.1b is the group 301a or 301b
The access right can be set for the information that can be viewed and entered within. Person in charge (no entry allowed) 303.2
a, 303.2b is the group 301a or 301b
It is possible to browse information within. As for the entry, only the result of the procedure can be browsed.

[0816] The responsible person 302 of each of the groups 301a and 301b selected by the site administrator 304, and the responsible person 302
The user ID of the person in charge 303 selected is the WWW browser 11b, the broadcast notification program 11c, the broadcast notification API
11a can be used in common. However, since the settlement information system employs the single login method, the setting is performed in consideration of the use conditions of the single login method described above. Note that while using the settlement information system by the single login method, another client computer 9 in the same member 2 can use another site provided by the stock exchange 14 using the same user ID.
The setting of the access right can be performed in units of “screen switching tab”, “information name”, and “user ID”. Each person in charge
Set access right management, including your own ID.

Next, the procedure for setting the access right will be described. First, the site administrator 304 accesses the payment information system and sets the user ID used by the payment information system.
Create D. Next, the site manager 304 selects the responsible persons 302a and 302b of each group according to the following procedure. First, the site administrator 304 accesses a predetermined URL to display the top screen of the payment information system, and then clicks an authentication window button to input a user name and a password in an authentication window displayed. And log in.

Next, when the "site user management" menu button of the page selection menu is clicked on the settlement information system home page displayed after login, the screen is switched to a site user management screen. This "Site User Management" menu button is
4 or when the managers 302a and 302b of each group access the payment information system. The site user management screen displays a site user list button, a list (CSV format) button, and a participant site group edit button. Click the participant site group edit button.

[0819] Thereby, the participant site group editing screen shown in Fig. 103 is displayed. This screen displays the ID of the WAN user who has already been registered in the settlement information system by the member site administrator 304, and displays the “current site WAN”.
User list "306, current site WAN user 30
5, "Current DVP user list" 307a displaying the ID of the WAN user who uses the payment information system
To c, a “current security manager list” 308 that displays the ID of the WAN user selected as the security manager 302a among the current DVP users, the current DVP
A “current securities trade manager list” 309 displaying the ID of the WAN user selected as the securities trade manager among the users is displayed.

[0820] The member site administrator 304 selects a WAN user who uses the payment information system from the current site WAN user list 306, and clicks the registration button 311 to move to the current DVP user list 307a. The current DVP user list 307a includes the responsible person 3
02 and the person in charge 303 are registered. There is no limit on the number of WAN users that can be registered in the current DVP user list 307a. To remove a WAN user registered in the current DVP user list 307a, select the WAN user to be removed from the list 307a and click the delete button 310.

Next, the securities handling manager group 301
a and securities trading manager 301b Group manager 3
02a and 302b are selected. A current DVP user list 307b of the current security officer 302a;
In the current DVP user list 307c of the current securities trading manager 302b, WAN users assigned to the settlement information system by the member site administrator 304 are listed.

[0827] From the current DVP user lists 307b and 307c of the responsible person groups 302a and 302b, select the WAN user to be appointed as the responsible person, and click the registration button 3
Click 13 or 315 to register in the current securities handling manager list 308 or the current securities trading manager list 309. Each person in charge 302a, 302b
The maximum number of WAN users that can be assigned to is 2. By selecting a WAN user from the current securities handling manager list 308 or the current securities trading manager list 309 and clicking the delete button 312 or 314, the managers 302a and 302b can be dismissed.

After the above procedure by the site administrator 304 is completed, the person in charge 302a of the group 301a responsible for handling securities and the person 302b of the group responsible for buying and selling securities 301b become the person in charge 303a of each group 301a, 301b. , 303b. First, log in to the payment information system. The login procedure will be described later. Next, when the site user management menu button on the “Home” tab screen is clicked, the screen is switched to the site user management screen, so that the securities handling person setting button or the securities trading person setting button is clicked.

If the security staff member setting button is clicked, a security staff member setting screen shown in FIG. 104 is displayed. On the securities handling person setting screen, the member site manager 304 displays the current DVP user column 321 displaying the DVP users (WAN users who can use the settlement information system) registered on the participant site group editing screen in FIG. The current person in charge of securities handling (entry permitted) column 322 that displays the user ID selected as the WAN user of the securities handling person in charge group 301a by which the person in charge 302a can perform the entry operation, and the person in charge 302a
Securities handling manager group 3 who cannot perform entry operation
Current securities clerk (entry not allowed) 323 displaying the user ID selected as WAN user 01a
Is displayed. It should be noted that the WAN users in the securities handling manager group 301a who cannot perform the entry operation can also view the information.

In order to appoint the person in charge 303a, a WAN user is selected from the current DVP user list 321a, b and the registration button 325 or 327 is clicked. When the person in charge 303a is dismissed, the WAN user is selected from the current securities handling person in charge list 322 or 323, and the delete button 324 or 326 is clicked.

[0827] On the other hand, when the securities trading clerk setting button is clicked, a securities trading clerk setting screen is displayed as shown in FIG. On the securities trading person setting screen, the member site manager 304 displays the DVP user (WAN user who can use the payment information system) registered on the participant site group editing screen in FIG. 103 in the current DVP user field 328a. , The person in charge 302b is allowed to perform an entry operation,
The current securities trader (possible entry) column 329 displaying the user ID selected as the WAN user of the third party, and the manager 302b selects the user ID selected as the WAN user of the securities trade manager group 301b that cannot perform the entry operation. The current securities handler (entry not allowed) 330 to be displayed is displayed. In addition, the WAN of the securities trading manager group 301b for which entry operation cannot be performed.
The user can also browse the information.

In order to appoint each person in charge 303b, a WAN user is selected from the current DVP user lists 328a, b and the registration buttons 332, 334 are clicked. When dismissing each person in charge 303b, the WAN security trader list 329, 330 is used to remove the WAN.
This is performed by selecting a user and clicking delete buttons 331 and 333. In addition, each group 301a, 30
The person in charge 303 of 1b can also serve as the person in charge of each other.
Cannot serve as the head of another group.

[0827] After the manager 302 and the manager 303 of the securities manager group 301a and the securities manager group 301b are selected in the above procedure, each user is set with a right to view or entry to each information. . In the screen for setting the access right described below, it is possible to set the WAN user registered on the securities handling person setting screen or the securities trading person setting screen.

The procedure for setting the access right in units of information (form) will be described. First, "Login to the payment information system. When logging in, the user is authenticated by inputting the user ID and password of the responsible person 302 who has the right to set the access right. Next, the" Home "tab screen shown in FIG. The access right management menu button 358 is clicked to display a user access right management menu 364. The access right management menu button 358
These buttons are displayed as one of the page selection menus 350 when the manager 302 of each group accesses the payment information system.

In the access right management menu 364, access rights can be set for each user by three types of methods. In the form "specify form" menu 361, individual information (form)
Set the access authority of each user for each unit. In the form “designation of form classification” menu 362, the access authority of each user is set for each page switching menu (form classification).

[0831] In the form "user ID designation" menu 363, an access right for individual information (form) is set for each user ID. That is, in the form “designate form” menu 361 and the form “designate form classification” menu 362, first, a form or form classification is selected, and a user ID is designated for the selected form or form classification. In the "user ID designation" menu 363, first, the user I
D is selected, and a form is designated for the selected user ID.

[0832] The operation procedure of the access right setting by each method will be described. In FIG. 106, when the form “form specification” menu 361 of the access right management menu is selected, when the form “form specification” button 361 is clicked, information available to the group 301 of the responsible person 302 who is currently accessing is displayed. As shown in FIG. 107, it is displayed in a list format.

The responsible person 302 clicks a form name from the list shown in FIG. 107 to select a form for which access right is to be set. In this example, the user clicks on “Internal Stock Trading Statement (Auction Trading)” at the top of the list. In this case, as shown in FIG. 108, the WAN users belonging to the group 301 of the manager 302 who is currently accessing are displayed in a list format. In addition, at the upper left of the WAN user list, the name of a form for which an access right is to be set is displayed, "Internal Stock Trading Statement (Intranet Trading)".

[0834] By activating the check box 373 of the WAN user who is permitted to view or enter, the corresponding form,
In this example, the access right of the “internal stock trading statement (trade trading)” is set to the WAN user. If the check box 373 is invalidated, the access right is not granted to the WAN user. When the setting of the access right is completed, the execution button 374 is clicked, and the setting of the access right is determined. When the reset button 375 is clicked, all the check boxes 37 for which the access right is enabled are set.
3 can be disabled.

In FIG. 106, when the form “designation of form classification” menu 362 is selected, when the form “designation of form classification” button 362 is clicked, information that can be used by the group 301 of the responsible person 302 who is currently accessing is displayed. Fig. 109
As shown in (1), the information is displayed in the form of a list in the form classification unit. In the list of FIG. 109, information classification names such as “collation business” and “payment business” which are set in advance in the payment information system are displayed in the classification 1 column 376 of the form included in the classification of the classification 1 column 376. The name is displayed in the category 2 column 377.

In the list shown in FIG. 109, classification 1 column 376
Click the form classification name, in this example, the "collation business" at the top, and select the information classification for which the access right is to be set. As a result, as shown in FIG. 110, the WAN users belonging to the group of the responsible person who is currently accessing are displayed in a list format. In addition, at the upper left of the WAN user list, the name of the form classification for which the access right is to be set, “collation work”, is displayed.

[0837] By activating the check box 373 of the WAN user who is permitted to browse or make entries, the access right of the relevant form classification, in this example, "verification work" is set to the WAN user. If the check box 373 is invalidated, the access right is not granted to the WAN user.
When the setting of the access right is completed, the execution button 374 is clicked, and the setting of the access right is determined. When the reset button 375 is clicked, all the check boxes 373 for which the access right is valid can be invalidated.

In FIG. 106, when the form “user ID designation” menu 363 of the access right management menu is selected,
When the user clicks a form "user ID designation" button 363, the group 30 of the responsible person 302 who is currently accessing the form
All the WAN users belonging to No. 1 are displayed in a list format as shown in FIG. The responsible person 302 sets the access right from the list shown in FIG.
Select an AN user.

[0839] As a result, the information (form) that can be used by the group 301 of the responsible person 302 who is currently accessing is
As shown in FIG. 112, it is displayed in a list format.
Further, at the upper left of the information (form) list, the ID of the WAN user who sets the access right is displayed.

[0840] The check box 373 of a form that allows browsing or entry is enabled, and the access right of the checked form is set to the WAN user. When the check box 373 is invalidated, the access authority of the form is not given to the WAN user. When the setting of the access right is completed, an execution button (not shown) is clicked to confirm the setting of the access right. When a reset button (not shown) is clicked, all check boxes 373 for which access rights are enabled can be disabled.

Next, a method for browsing settlement information and the like using the WWW browser 11b will be described. After completing the login procedure of the payment information system, the home screen of FIG. 113 is displayed. The display names and functions on the screen are as follows. The screen switching tab 340 includes page selection menus 341 to 347 in units of settlement business or services.
Switch. The first page when a tab is selected is “Today's distribution information”. The page selection menu 350 displays notifications, procedures, and names of services 351 to 360 that can be used by the accessed WAN user in units of screen switching tabs 340. Clicking menu buttons 351 to 360 displays the target information screen page.

[0832] The information screen page 365 displays the contents corresponding to each menu. Simple link (MY TARGE
T) 366 is a menu that directly links to frequently used information or service. Clicking the add button 366a shifts to a link add page, and clicking the edit button 366b shifts to a link edit page. Links can be added and edited on the link addition page and the edit page, respectively. The user ID information column 367 displays the user ID of the currently accessed WAN user.

[0843] On the home 341 tab screen, by selecting the page selection menu 350, it is possible to display the following menu relating to posting notices as business messages and managing user information. As shown in the information screen page 365 in FIG. 113, the notification menu button 351 includes a notification 391 from a common administrator of the stock exchange WAN system 1, a system operation report 392, and a payment operation report 393 specific to the payment operation.
Has been posted. Site administrator 304, responsible person 302,
The person in charge 303 can access.

[0844] The related site menu button 352 lists link information to other sites on the stock exchange WAN system 1. The site administrator 304, the responsible person 302, and the person in charge 303 can access. The archive menu button 353 is a page for downloading software related to the payment information system. Site administrator 30
4. The person in charge 302 can access, but the person in charge 30
3 is not accessible.

[0845] The password change menu button 354 is
Change the password of the user ID. Site administrator 30
4, the person in charge 302 and the person in charge 303 can access. The user information menu button 355 changes user information corresponding to the user ID. Site administrator 304,
The responsible person 302 and the person in charge 303 can access. The broadcast notification list menu button 356 is displayed on the stock exchange WAN.
The information distributed to the broadcast notification program 11c of the system 1 is posted. The site administrator 304, the responsible person 302, and the person in charge 303 can access.

[0846] Site user management menu button 357
Selects the person in charge 302 and the person in charge 303. Although the site administrator 304 and the responsible person 302 can access,
The person in charge 303 cannot access. The access right management menu button 358 sets the access rights of the responsible person 302 and the person in charge 303. The responsible person 302 can access, but the site administrator 304 and the person in charge 303 cannot access.

[0847] The logout menu button 360 ends the use of the settlement information system. Site administrator 304,
The responsible person 302 and the person in charge 303 can access. Of these menus, the logout menu button 36
0 is also provided on other tab screens, and all logout menu buttons have the same function.

FIG. 114 shows the collation business 342 tab screen. As shown in FIG. 114, the following menu is prepared on the collation service 342 tab screen. Today's distribution information 40
In 1, the distribution information for the day received from the settlement information system is posted on the list 414.

[0849] The domestic stock trading statement 402 includes a domestic stock trading statement (intra-auction transaction), a correction of the domestic stock trading statement (intra-auction transaction), a domestic stock trading statement (off-auction transaction),
Includes a domestic stock trading statement (off-auction transaction) correction, a domestic stock trading statement (basket transaction), a domestic stock trading statement (basket transaction) correction, and a domestic stock trading statement (total issues). The bond transaction sales statement 403 includes a bond transaction sales statement (trade trading), a bond transaction sales statement (trade trade) correction, a bond transaction sales statement (off-trade transaction), and a bond transaction trade statement (non-auction transaction). Off-auction transactions) corrections, bond transaction sales statements (basket transactions), bond transaction sales statements (basket transactions) corrections, and bond transactions sales statements (total issues).

[0850] The summary 404 includes summary A and summary B. Exercise 405 includes a stock option trading right exercise declaration / allocation statement. In browsing 406 by distribution date, past distribution information including today is listed in the list by distribution date.

In the form search 407, a search is performed within the range of information belonging to the collation work tab screen. The respective menus on the collation business 342 tab screen can be used by the managers 302 and 303 who belong to the securities handling manager group and the securities trading manager group. The site administrator 304 cannot use it.

The following menu is prepared on the settlement business 343 tab screen. In today's distribution information, the distribution information for the day received from the settlement information system is listed in the list. The settlement notice includes a general settlement table (contract price), a total receipt / payment calculation sheet (planned / flash report), a total receipt / payment calculation sheet (planned amount), a scheduled settlement amount for each brand, a general clearing table (payment price / clearing price) Difference).

[0853] The confirmation notice includes a total receipt / payment price calculation table (confirmed amount), a settlement settlement quantity for each brand, an additional payment notice, and a payment receipt notice. The other party designation includes a recipient / transfer designation document relating to settlement on the base date. When browsing by delivery date,
Past distribution information including today is posted on the list by distribution date.

In the form search, a search can be performed within the range of information belonging to the settlement business tab screen. Settlement business 343
Each menu on the tab screen can be used by the person in charge 302 and the person in charge 303 belonging to the group in charge of handling securities. The site administrator 304 cannot use it.

The following menu is prepared on the security management 344 tab screen. In today's distribution information, the distribution information for the day received from the settlement information system is listed in the list. The collateral posted on the previous day includes a member's trust deposit, trading / trade margin, a deposit / payment status table for the collateral received on the previous day, and a balance table for collateral deposited on the previous day.

[0856] The margin includes a transaction margin, a deposit / returnable table, a notice of balance of securities in custody, and a notice of balance of received real stockholders and collateral. In browsing by distribution date, past distribution information including today is listed in the list by distribution date.

In the form search, a search is performed within the range of information belonging to the security management 344 tab screen. Each menu on the security management 344 tab screen can be used by the manager 302 and the manager 303 belonging to the securities manager group and the securities manager group. The site administrator 304 cannot use it.

The following menus are prepared on the fail management 345 tab screen. In today's distribution information, the distribution information for the day received from the settlement information system is listed in the list. The person in charge 302 and the person in charge 303 belonging to the securities handling manager group and the securities trading manager group can be used. The site administrator 304 cannot use it.

[0859] The fail information notification includes a fail information notification (after DEL) and a fail information notification (after CNS). The responsible person 302 can access, but the site administrator 304 and the person in charge 303 cannot access. The menu related to the fail notification can be used by the person in charge 302 and the person in charge 303 belonging to the securities handling person in charge group. The site administrator 304 cannot use it.

[0860] The buy-in information notification includes a buy-in information notification and a buy-in invalid information notification. The buy-in execution notice includes a buy-in execution notice (for billing members), a buy-in execution notice (for burden members), a buy-in execution notice (for all members)
Is included.

The buy-in execution result notice includes a buy-in execution result notice (for billing members), a buy-in execution result notice (for paying members), a buy-in execution result notice (for sellers), and a buy-in execution result notice (for all members). included. Menu related to buy-in notification (buy-in information notification, buy-in execution notification,
The notification of the buy-in execution result) is issued to the person in charge 30 belonging to the group responsible for securities handling and the group responsible for securities trading.
2. The person in charge 303 can use it. The site administrator 304 cannot use it.

In the buy-in request, a buy-in request is made.
In the withdrawal of the buy-in request, the withdrawal of the buy-in request is performed. The buy-in billing menu and the buy-in withdrawal menu can be used by the person in charge 302 and the person in charge 303 belonging to the securities handling person in charge group. The site administrator 304 cannot use it.

In the buy-in order, a buy-in order is performed.
The buy-in order menu can be used by the manager 302 and the person in charge 303 belonging to the securities trading manager group. The site administrator 304 cannot use it. In browsing by distribution date, past distribution information including today is listed in the list by distribution date. The person in charge 302 and the person in charge 303 can access, but the site administrator 304 cannot. In the form search, a search is performed within a range of information belonging to the fail management tab screen. The person in charge 302 and the person in charge 303 can access, but the site administrator 304 cannot.

[0864] On the information inquiry 346 tab screen, "stock exchange address book" which is an e-mail address book is prepared. The stock exchange address book contains e-mail addresses of stock exchange departments related to the settlement information system. The site administrator 304, the responsible person 302, and the person in charge 303 can use it.

On the help 347 tab screen, a help desk, a business contact, a usage rule, and an operation manual for supporting the user are prepared. The help desk describes how to contact the operation help desk and the failure help desk, and the operation hours. The business contact point describes the contact point for business related to the payment information system.

[0866] The usage rules include rules regarding the use of the stock exchange WAN system 1. The operation manual discloses operation manuals and the like related to the settlement information system. Help desk, business contact, usage rules and operation manual are provided by site administrator 304, responsible person 302,
The person in charge 303 can use it.

A method of browsing settlement information on each tab screen of the collation business 342, the settlement business 343, the security management 344, and the fail management 345 will be described. In addition, since the browsing procedure is common to each tab screen, the collation operation 342 will be described as an example in this section. When the screen switching tab of the collation operation 342 is clicked, the payment information ready for distribution by the time of the browsing operation is posted in a list form on the today's distribution information menu 401 screen as shown in FIG. The settlement information posted on the list is the range of the menu belonging to the screen switching tab being viewed, and in the case of FIG. 114, is the range of today's distribution information.

[0868] On the today's distribution information menu screen, among the forms belonging to the "collation business", a list of forms for which the form date is today is displayed. If no CSV is created, no link is displayed. Information name (form name) for each information
414a, distribution time 414b, file capacity 414c,
A confirmation status 414d (browsing process status (unconfirmed / confirmed)) and a download 414e are displayed. The information name (form name) 414a displays the information name and distribution date of each piece of information. When the information name (form name) 414a is clicked, the screen is switched to a detailed screen of the clicked information. The delivery time of the information is displayed in the delivery time 414b. The file capacity of the CSV file is displayed in the file capacity 414c. Confirmation status 414d
, The confirmation status of the member 2 is displayed as one of “confirmed”, “viewed”, “unconfirmed”, and “broken”. The download 414e is an icon for download, and is configured to download a CSV file when clicked.

The previous day posting button 408a, next day posting button 408c, and date designation field 408b are buttons for designating the form date. Click the previous day posting button 408a or next day posting button 408c, or click the date designation field 408b. By specifying a date in, a list of forms related to “collation work” corresponding to the date is displayed. That is, the screen of FIG. 114 is browsing by distribution date, and displays a list of documents related to the collation operation using the form date as a key. Also, the button 408a for the previous day and the button 408 for the next day
c, a date can be designated by the date designation field 408b, and the previous / next day can be displayed.

[0870] The today's search button 415 is a button for performing a search process on the forms listed in "Today's distribution information". Clicking on each information name (form name) 414a displayed on today's distribution information menu screen switches to a detailed screen of the clicked information. In the screen of FIG. 114, only distribution records for each predetermined number, for example, every 30 cases are displayed, and distribution records exceeding the predetermined number are displayed on the next page, and a “previous page” button, a “next page” button For example, distribution records of different pages may be displayed.

[0871] If the notification name to which the information to be browsed belongs is selected from the page switching menu 400 in Fig. 114 and clicked, a screen corresponding to the page switching menu is displayed. For example, when the domestic stock sales statement 402, the bond transaction sales statement 403, the summary 404, and the exercise of rights 405 are clicked, the distribution status of the past 5 business days, that is, the latest 5 cases, for the form belonging to each category,
A list is displayed for each information (form). For example, FIG.
Then, when you click on "Internal Stock Trading Statement" 402,
As shown in FIG. 115, the distribution status of the five most recent domestic stock trading statements is displayed.

[0887] When a list display button 421 on the screen in Fig. 115 is clicked, all past distribution records including the latest five items are displayed and can be browsed as shown in Fig. 116. Fig. 116
FIG. 115 shows a case where the list display button 421a of the domestic stock trading statement (trade trading) is clicked in FIG.

[0873] Each posting item displayed on the list screen of Fig. 115 will be described. Page switching menu name 422
Displays the name of the page switching menu selected by the user. The information name title 423 displays the title of the list.

[0874] The list display button 421 is a button for displaying past distribution information in a list format. The information name and distribution date 424 are columns for displaying the name of information and the distribution date.
When 4 is clicked, the screen is switched to a screen on which the contents of the information are posted. The distribution time 425 indicates the distribution time of the information. The file capacity 426 indicates the file capacity of the CSV data.

[0875] The confirmation status 427 is a column indicating whether there is a record of browsing the information or the like. “Confirmed” indicates that the information has already been viewed, etc., and “Unconfirmed”
Indicates that there is no record of browsing the information. When the CSV file of the information is downloaded using the broadcast notification program 11c, when the detailed screen of the information is displayed on the WWW browser screen using the link function of the broadcast notification program 11c, the WWW browser 11b is used. When the detailed screen of the information is displayed, the confirmation status 4
27 is “confirmed”.

[0887] The download icon 428 is an icon for starting the download processing of the CSV file. Clicking this icon starts the CSV file download process. The download icon 428 is not displayed in the information for today's distribution.

[0877] Fig. 117 shows information names and distribution dates 424.
5 shows a detail screen for displaying the content of the information displayed by clicking an arbitrary item in the column. In the case of information covering a plurality of pages, a “previous page” button 431 and a “next page” button 432 are displayed on the left and right sides of the screen. By clicking the buttons 431 and 432,
It is possible to switch the page to be displayed.

[0887] The CSV file download operation will be described. When the download icon 428 in the list of FIG. 115 is clicked on information desired to be downloaded, a screen shown in FIG. 118 is displayed. On this screen, the save destination of the CSV file is designated, and the download is performed by clicking the save button. CS
V file names include data type code, cycle,
Includes member code and creation date.

[0887] The contents displayed on the WWW browser 11b are not automatically updated. Therefore, when redisplaying the latest content, it is necessary to perform the operation executed in the process of displaying the information again.

[0880] The concept of the date on the WWW browser screen will be described. The payment information system of the present embodiment manages payment information based on the concept of three types of dates (base date, business date, and form date) as follows. The reference date is a contract date and a settlement date related to the settlement information. FIG.
7 is a reference date display screen. The reference date is also applied to a date condition used when searching for payment information on the WWW browser 11b. The business date is a date when the payment information system is ready to distribute payment information. The work date is W
The information is displayed in the information name of the list displayed on the WW browser screen + delivery date column or the date type column of the broadcast notification program 11c. FIG. 115 is a work date display screen.

The settlement date manages the date on which the user will use the settlement information in the settlement information system. For example, the form date of the domestic stock trading statement (intra-auction transaction), which is ready for information distribution at around 23:00 of the previous day, is:
Assuming that the user will browse on the next day, the business date + 1 business day is managed as the form date. The form date is adopted as today's distribution information for browsing the settlement information on a distribution day basis on the WWW browser screen, the posting standard of the browsing menu on a distribution day basis, the date condition used when searching for the settlement information, and the like. .

FIG. 117 is a form date display screen. As in the above example, the form date is a date management adopted for the purpose of improving the operability of the WWW browser screen used by humans.

[0883] Information on the latest business date + 1 business day is posted on the distribution status panel and the like of the broadcast notification program 11c. Information beyond the posting period will be automatically deleted from the display on the panel.

In the payment information system, a CSV data file containing payment information is stored for the latest business date + 6 business days. For payment information beyond the same period,
Each time the user performs an operation, a CSV is individually set using the payment information system.
Since the data file is created, the time required for downloading is longer than the information of the above period.

Next, the search function of the WWW screen will be described. The settlement information system provides three types of search functions: a screen switching tab unit, a distribution date unit, and specific information (form) unit. In keyword search of screen switching tab unit,
For information (form) belonging to each screen switching tab, payment information and the like distributed in the past can be searched. In the keyword search, two types of dedicated screens of “search within an arbitrary period” and “search limited to today's distribution” are prepared for each period to be searched.

[0886] In the search with an arbitrary period as a range, a search is performed for a certain period in the past including today, within the range of the payment information belonging to the currently viewed tab screen. In the search limited to today's distribution, the search is performed on the payment information distributed today, within the range of the payment information belonging to the currently viewed tab screen.

[0887] In the search on a distribution day basis, information (forms) distributed on the relevant day is browsed in a list format for information (forms) belonging to each screen switching tab. In the search by distribution day, two types of dedicated screens are prepared for each date to be searched, that is, "search within an arbitrary distribution date" and "search limited to today's distribution". In the search with an arbitrary distribution date as a range, a search is performed for an arbitrary distribution date within the range of the payment information belonging to the currently viewed tab screen.

In the search limited to today's distribution, a search is performed for today's distribution within the range of payment information belonging to the currently viewed tab screen. In a search in units of specific information (form), information (form) over a plurality of pages can be searched within a range of information currently being viewed. This function cannot be used when browsing information that fits on one page (screen).

Next, the operation procedure of each search will be described. Home search, information inquiry screen,
When the form search menu button 551-01 displayed on each tab screen other than the help screen is clicked, the screen is switched to a search-only screen as shown in FIG.

[0890] Items displayed on the search-only screen include the form name 551-02, select all / clear all 551-03, and date 55.
1-04. Each search item becomes an AND condition. In other words, the search is performed using the “selected form name” and the “specified date range”. In the form name 551-02, information belonging to the currently viewed screen tab is displayed. The displayed information is the range of the access right granted to the user. Enable the check box of the information name to be searched.

[0891] In select all / clear all 551-03, all check boxes of the form names are selected or all cleared.
In the date 551-04, the item 551-05 without date designation
When is selected, a search that does not specify the search target period is executed. When the reference date item 551-06 is selected, the reference date within the designated period is set as a search condition. When the form date item 551-07 is selected, the form date 551-08 within the designated period is set as a search condition.

In the brand name 551-09, the input brand name is used as a search condition. If you do not want to search for stock names,
Leave this item blank. In the security code 551-10, the input security code is used as a search condition. If the security code is not to be searched, leave the item blank. In the new security code 551-11, the input new security code is used as a search condition. If the new securities code is not to be searched, leave the item blank.

[0893] To execute a search, after setting search conditions, a search button 551-12 is clicked. To temporarily cancel the already set search conditions, the user clicks a reset button 551-13. If there is information matching the specified search condition, the search result screen of FIG. 120 is displayed. When the user clicks on the information name + delivery date field 551-21 on the list of the search result screen in FIG. 120, the screen is switched to a detailed display screen of the information.

In the search limited to today's distribution among the keyword search in screen switching tab units, today's retrieval icon 5 displayed on today's distribution information menu screen 551-31
Clicking on 51-33 displays a search-only screen 551-32 corresponding to a form search menu. In the search-only screen 551-32, the date item 551-04 is fixed to today's date (form date). Other items are shown in FIG.
This is the same as the form search menu screen.

[0895] Searching by distribution date will be described. In the search for an arbitrary delivery date in the search for each delivery date, the browse menu button 5 for each delivery date displayed on each tab screen other than the home screen, the information inquiry screen, and the help screen
Clicking on 51-41 switches to a search-only screen as shown in Fig. 122. Using the date designation pop-up menu 551-42 or the date shift button 551-43 at the top of the search-only screen in FIG. 122, the past settlement information distributed on any day (form date) is confirmed in a list.

In a search limited to today's distribution among searches by distribution day, when a distribution information menu button 551-51 of today displayed on each tab screen other than the home screen, the information inquiry screen, and the help screen is clicked, The screen is switched to a search-only screen as shown in FIG. 123, and the payment information (for today's distribution) ready for distribution can be confirmed in the list by the time the user browses.

[0897] Retrieval in units of specific information (form) will be described. When browsing payment information across multiple pages, Figure 1
As shown in FIG. 24, a form search icon 551-61 is displayed on the left side of the next page button. The same icon 551-6
When 1 is clicked, a form search window 551-62 is displayed as shown in FIG.

[0898] Items displayed in the form search window 551-62 include the brand name 551-63 and the security code 551.
-64, new securities code 551-65. Each search item becomes an AND condition. The brand name 551-63 uses the input brand name as a search condition. If the stock name is not to be searched, leave the item blank.

[0899] The security code 551-64 uses the input security code as a search condition. If the security code is not to be searched, leave the item blank. New securities code 551-
Reference numeral 65 designates the input new security code as a search condition. If the new securities code is not to be searched, leave the item blank. When executing a search, after setting search conditions, a search button 551-12 is clicked. When canceling the already set search conditions, the reset button 551-
13 Click

If there is information that matches the specified search conditions, the search result screen shown in FIG. 125 is displayed. If there is information that hits the search condition, the user directly goes to the page on which the information is posted, and in the page, the information is identified by a color different from other information, for example, a light pink color.

If a search is continuously performed under the same search condition,
The search is executed starting from the page that was just moved.
On the other hand, if the search is continuously performed under another search condition, the search returns to the first page of the payment information (form) and the search is executed. W
An entry operation procedure on the WW screen, that is, an operation procedure relating to a fail management tab screen buy-in request, buy-in request withdrawal, and buy-in order will be described. There are three types of entry operations in the DVP settlement system: buy-in billing, withdrawal of buy-in billing, and buy-in order.

In the buy-in request, the declaration of the buy-in request,
Provides entry operations for changes and cancellations. The operation related to the buy-in request is 12: 3 on the day of the entry operation
Operation is possible between 0 and 14:30. In the withdrawal of buy-in requests, entry operations for declaring, changing, and canceling withdrawal of buy-in requests are prepared. The operation related to the withdrawal of the buy-in request can be performed between 9:00 and 12:00 on the business day following the buy-in execution date (buy-in request date + 4 business days).

In the buy-in order, entry operations for applying, changing, and canceling the buy-in order are prepared. The operation related to the buy-in order can be performed between 15:00 and 15:30 on the buy-in execution date (buy-in billing date + 3 business days). The entry reception time is shown in FIG.
(B).

FIG. 126 shows the procedure for receiving entry information.
This will be described with reference to FIG. When entry operations such as declaration and cancellation are performed, the input entry information is temporarily received 561-0.
1 or the state of temporary cancellation 561-04.
Thereafter, the entry information is verified by the payment information system, and if there is no problem in the input contents, the reception 561-0
1 or canceled 561-05. On the other hand, if there is a problem with the entry information, the rejection 561-0
3, 561-06.

[0905] The status of the entry information is displayed in the reception status column of each status screen described later. The contents displayed in the reception status column are provisional receipt, provisional cancellation, main receipt, canceled, non-accepted or non-accepted reason. Provisional receipt means entry operation (declaration / change)
Is performed immediately after the payment information system performs the verification of the entry contents.

[0906] The temporary cancellation is a state from immediately after the entry operation (cancellation) is performed until the settlement information system completes the verification of the entry contents. This receipt means that the payment information system has been verified and entry information (declaration / change)
This is the situation at the time when no problem was accepted. The term “cancelled” means a state at the time when the verification of the payment information system is completed and the entry information (cancellation) is accepted without any problem.

[0907] The rejection or the reason for rejection is displayed when the verification of the payment information system is completed, the entry information is inconvenient, and the entry becomes invalid. The entry information in the state of provisional reception cannot be changed or canceled until it is switched to the actual reception. The entry information in the temporarily canceled or canceled state cannot be changed or canceled. That is, the entry information cannot be changed / cancelled until the transfer to this reception is made. If the entry information in the provisionally received state is rejected for some reason, the entry information becomes invalid.

[0908] Therefore, the version number of the entry information described later is not revised if it is rejected as follows. In other words, when a buy-in claim declaration is newly entered, "1st edition, claim declaration, main receipt" is displayed on the screen. After that, the state immediately after the change of the buy-in request is displayed as “2nd edition, request change, provisional receipt”. If the claim change is subsequently rejected, "1st edition, claim declaration, rejection" will be displayed, and the entry information of the provisional receipt will be invalidated. As a result, only the 1st version claim declaration will be valid. is there.

Regarding the rejection of the reception status, the reason why the entry information has become invalid may be displayed. For example, "display order price error" when the order price is incorrect in the entry information, "self-consigned category error" when the self-consigned category is incorrect in the entry information, or when the same information is already registered "Additional error", "No data to be corrected" when the data to be corrected is not registered, "No data to be canceled" when the data to be canceled is not registered, "Member code error" when there is an error, "Stock code error" when there is an issue code in the entry information, "Trading unit error" when there is an error in the trading unit in the entry information, “Invoiced quantity error” when the requested quantity is incorrect, “Removed quantity error” when the withdrawn quantity in the entry information is incorrect, "Order quantity error" when there is an error in the order quantity in the bird information, "Processing category error" when it is other than the predetermined category such as declaration, change, cancellation, etc., entry was made outside the operable time zone "Error outside reception hours"
This is the reason.

[0911] Version number management of entry information will be described. The information that has been entered manages state changes by version number in units of entry date and billing number (described later). The version number is displayed in a version number column of each status screen described later. In each entry operation, the information of new declaration (application) is handled as one version. Thereafter, each time the information is changed, the version number is updated (second edition, third edition, etc.). When the information is canceled (when the reception status is canceled), version management of the information is completed. After the cancellation is completed, if the same brand is declared again (application), the edition will be treated as one edition. The version number of the rejected entry information is not updated.
The change or cancel operation is invalidated.

[0911] A specific example of the number-of-versions management of a buy-in bill declaration and a buy-in sales order will be described by taking as an example a case where the buy-in billable quantity is 10 shares. In this example, in order to change the quantity without cancellation, the first edition: request for buy-in of 5 shares 2nd edition: request for buy-in of 7 shares (change in quantity) Third edition: request for buy-in of 9 shares (change in quantity) Become.

[0912] After the cancellation, the quantity was changed, and the first edition: request for 5 buy-ins 2nd edition: cancellation of 5 buy-in claims 3rd edition: 7 buy-in claims (change in quantity) 4th edition: 7 stocks Cancellation of request for buy-in 5th edition: There is a plan to request buy-in of 9 shares (change of quantity), but the latter plan requires more operations and
Since the procedure differs greatly from the operation procedure of the conventional system, a method of correcting data based on the first version is adopted as in the former plan.

[0913] A specific example of version management of withdrawal of a buy-in request will be described. The unit in which the buy-in claim can be withdrawn is on each billing date. For example, if there are 5 shares (remaining quantity on invoice date a), 10 shares (remaining quantity on invoice date b), and 6 shares (remaining quantity on invoice date c), the withdrawal will be made in invoice day units and on invoice date Are in the descending order (a → b → c). Therefore, the withdrawable quantity is one of 5, 15, and 21.

[0914] Regarding the withdrawable quantity, the CSI server computer 12 can cooperate with the DVP server computer 4 in units of 5, 10, and 6 shares. After confirming the remaining quantity of the "buy-in execution result notification", the user distributes the "buy-in execution result notification" on an execution day basis to judge whether or not to withdraw, and then withdraws from each information. It is preferable to use these units, but the configuration may be such that cooperation is possible in units of 5, 15 and 21 shares.

[0915] The billing number of the entry information will be described. In the payment information system, a billing number is automatically assigned to the declared (applied) entry information as shown in FIGS. 155, 162, and 169. The billing number is serially managed on an entry day basis throughout the system. Care must be taken because the billing number is not a serial number management for each site.

[0916] The claim number is valid from declaration (application) to cancellation. As with the version number management, the billing number becomes invalid when the entry information is canceled. After the cancellation is completed, if the same brand is declared again (application), a different billing number is assigned. This billing number is referred to as a “billing number” for a buy-in bill, a “withdrawal number” for withdrawing a buy-in bill, and an “order number” for a buy-in order. FIG.
26 to 130 show the status management in the entry,
It is a figure which shows the outline of the unit of change, cancellation procedure (relationship between reception status and version number management), request, etc.

FIGS. 131 to 137 show screen transition diagrams of the WWW screen. FIG. 131 is a screen transition diagram of the home. Upon receiving authentication on the top screen 561-01 of the WWW page, a home screen 561-02 is displayed. On the home screen 561-02, by selecting a tab,
Matching business screen 561-04, settlement business screen 561-0
5. Security management screen 561-06, fail management screen 56
1-07, information introduction screen 561-08, help screen 56
1-09 is displayed.

[0918] When the menu button on the home screen 561-02 is selected, a notice list 561-1 is displayed.
0, related sites 561-11, archive list 561
12, password change 561-13, user information change 5
61-14, a broadcast notification list 561-15, a site user management 561-16, an access right management 561-17, and a billing information display 561-18 are displayed. In the news list 561-10, the news list 5 for each category is displayed.
It is possible to shift to the 61-19 screen, and from the notification list 561-19 screen for each category, it is possible to shift to the notification display 561-20 where the notification can be downloaded and the notification registration / deletion 561-21 where the notification can be uploaded. .

From site user management 561-17, participant site registration / deletion, participant site group editing, securities handling person setting, securities trading person setting, site user list / CSV, site manager list / It is possible to shift to a screen corresponding to each administrator among the setting screens 561-23 including CSV. From the access right management 561-17, target member management (form specification), target member management (form classification specification), target member management (member specification), target member management (attribute specification), user access right management (form specification) Management screen 561-24 including user access right management (form classification designation) and user access right management (user ID designation)
Can be switched to a screen corresponding to each administrator.

FIG. 132 is a screen transition diagram of the collation work. By selecting with the menu button of the collation business screen 561-04, today's distribution information 561-31, category A / category B categorized by the information item amount
A list 561-33 of the past 5 business days of the form for displaying a list of the past 5 business days of each form such as the category C, a browsing 561-37 for each distribution date, and a form search screen 561-38 are displayed.

[0921] Today's distribution information 561-31 is the first page when a tab is selected. A list of today's forms among the forms belonging to the "collation business" is displayed. Display items are a form name, a browsing process status, a form distribution time, and a CSV file size, and have a link to a form display (HTML) 561-34. List of past 5 business days list display 561
From 33, a form list screen 561-34 can be displayed. The form list screen 561-34 is available for CSV download, and has a form display (HTML) 561-34.
, It is possible to shift to the form search screen 561-36.

FIG. 133 is a screen transition diagram of the settlement business. The screen transition diagram shown in FIG.
The screen is the same as the screen transition diagram of the collation business in FIG. 132 except that the respective screens are transition-displayed from -05 and each screen displays information relating to the settlement business, and thus the description is omitted.

FIG. 134 is a screen transition diagram of security management. The screen transition diagram shown in FIG.
The screen is the same as the screen transition diagram of the collation work in FIG. 132 except that the screens are transition-displayed from −06, and that each screen displays information related to collateral management, and a description thereof will be omitted.

FIG. 135 is a screen transition diagram for fail management. From the fail management screen 561-07, the buy-in request is withdrawn via the buy-in request screen 561-39.
40, the buy-in order 561-41 is displayed. FIG.
The screen transition diagram shown in FIG. 5 is a fail management screen 561-07.
132 is the same as the screen transition diagram of the collation work in FIG. 132 except that each screen is transition-displayed, and each screen displays information related to fail management, and a description of the same configuration is omitted.

FIG. 136 is a screen transition diagram for information introduction. By selecting a menu button on the information introduction screen 561-51, the stock exchange address book 561-53,
Your site administrator screen 561-54, member address book 5
61-55 are displayed.

FIG. 137 is a transition diagram of the help screen.
When the menu button is selected on the help screen 561-09, the help desk is registered via the help desk 561-56, the help desk registration screen 561-60, the business contact 561-57, the business contact registration screen 561-61, and the usage rule 561-58. Regulation registration screen 561-62, operation manual 561
An operation manual registration screen 561-63 can be displayed via -59.

Next, the screen design of the WWW screen will be described. In the present embodiment, it is configured such that a report, change, and cancellation operations can be performed from the reception status screen. In the screen menu display section when the fail management tab on the WWW home screen is selected, three operations of "buy-in request", "buy-in request withdrawal", and "buy-in order" are selected.

FIG. 138 is a screen transition diagram after the fail management tab is selected. Buy-in billing business main screen 571
When the buy-in order button is selected at -01, the buy-in order business main screen 571-03 is selected.
02, when the bill report button is selected, a buy-in bill report screen 571-04 is displayed, and when the bill change button is selected, a buy-in bill change screen 571-05 is displayed.

[0929] Cancel button on buy-in request declaration screen 571-04 or buy-in request change screen 571-0
If the user selects the OK button or the cancel button in step 5, the buy-in request business main screen 571-01 is displayed. When the buy-in request button is selected on the buy-in request withdrawal business main screen 571-02, the buy-in request business main screen 5
71-01, if a buy-in order button is selected, a buy-in order business main screen 571-03, if a bill withdrawal declaration button is selected, a buy-in withdrawal declaration screen 571-06,
When the bill withdrawal change button is selected, a buy-in withdrawal withdrawal change screen 571-07 is displayed.

[0930] Cancel button on Buy-in request withdrawal declaration screen 571-06 or Buy-in request withdrawal change screen 5
When the OK button or the cancel button is selected in 71-07, the buy-in request withdrawal business main screen 571-02 is displayed. When the buy-in billing button is selected on the buy-in order business main screen 571-03, the buy-in billing business main screen 571-01 is selected. Order application screen 571
-08, When the order change button is selected, a buy-in order change screen 571-09 is displayed. When the cancel button is selected on the buy-in order application screen 571-08 or the OK button or the cancel button is selected on the buy-in order change screen 571-09, the buy-in order business main screen 571-0 is selected.
3 is displayed.

[0931] Next, screen transition of each business screen will be described. FIG. 139 is a screen transition diagram illustrating a buy-in billing business screen (flow of billing report processing). When the buy-in request is selected on the fail management 345 tab screen displayed by selecting the fail management 345 tab on the home screen in FIG. 113, the processing in FIG. 139 starts.

[0932] In step S501-01, it is determined whether the time is outside the entry reception time. If it is outside the reception time of the entry (S501-01: Yes), step S501-
At 02, a buy-in request status reception screen, which is a main screen related to a buy-in request, is displayed as a read-only screen. That is, a claim report button (8) and a claim change button (9)
148 except that the buttons such as are not displayed.
A screen similar to the buy-in request status reception screen is displayed.
In this screen, since each button is not displayed, an input operation such as a button click cannot be performed.

[0932] If the time is not outside the entry reception time (S50)
1-01: No), that is, if it is within the entry reception time, in step S501-03, the buy-in request status reception screen of FIG. 148, which is the main screen for the buy-in request, is displayed. At this time, if there is buy-in request reception status data, the reception status data is displayed as a list as shown in FIG. 148, and if there is no buy-in request reception status data, only the title portion is displayed as shown in FIG. 151. . Next, in step S501-04, it is determined whether the claim report button (8) in FIG. 148 has been clicked. If the billing report button (8) is not clicked (step S501-04: No), step S501-03
And the display of the buy-in request status reception screen is continued.

If the claim report button (8) is clicked (step S501-04: Yes), step S5
At 01-05, it is determined whether or not it is outside the reception time of the buy-in request report entry. If it is outside the reception time of the buy-in request report entry (step S501-05: Yes), an error screen of "cannot be received because it is outside the buy-in request report reception time" of FIG. 150 is displayed in step S501-06. It is determined whether the "OK" button on the error screen has been clicked in step S501-07. If the “OK” button on the error screen has not been clicked (Step S501-07: No), Step S501-06
Continue to display the error screen. When the "OK" button on the error screen is clicked (step S501-07:
Yes), returns to step S501-03, and displays a buy-in request status reception screen.

[0935] If it is not outside the reception time of the buy-in claim report entry (step S501-05: No), that is, if it is within the reception time of the entry, step S501-0.
At 8, it is determined whether there is brand information for which a buy-in claim report entry is possible. If there is no brand information for which a buy-in claim report entry can be made (step S501-08: No), in step S501-12, a brand-less screen "No brand available for buy-in request" is displayed, and step S50 is performed.
At 1-13, it is determined whether the "OK" button on the brand-less screen has been clicked. When the "OK" button on the brand-less screen is not clicked (step S501-13: N
o), the screen display without brand of step S501-12 is continued. When the “OK” button on the brand-less screen is clicked (step S501-13: Yes), the process returns to step S501-03, and the buy-in request status reception screen is displayed.

If there is brand information for which a buy-in claim report entry can be made (step S501-08: Yes), a buy-in claim report entry screen shown in FIG. 152 is displayed in step S501-09. Next, Step S501-01
At 0, it is determined whether or not the “OK” button (5) on the buy-in claim entry screen has been clicked. When the “OK” button (5) has not been clicked (step S501)
-10: No), it is determined whether the "cancel" button (6) has been clicked in step S501-11.

If the "cancel" button (6) is not clicked (step S501-11: No), it is determined that the user has not finished the process on the screen, and the process returns to step S501-09 to request the buy-in shown in FIG. Continue to display the declaration entry screen. When the "Cancel" button (6) is clicked (step S501-1)
1: Yes), assuming that there is no intention to report a buy-in request, the process returns to step S501-03, and a buy-in request status reception screen is displayed.

[0938] "OK" on the buy-in claim report entry screen
When Button (5) is Clicked (Step S501)
(-10: Yes), it is determined in step S501-14 whether a check on the client computer 9 side has determined that there is no mistake in the input data.

[0939] If it is not determined by the check on the client computer 9 side that there is no mistake in the input data (step S501-14: No), that is, if there is a mistake in the input data by the check, step S501 is performed.
At -15, an error screen such as "Please input at least one billing quantity" is displayed. At step S501-14, it is determined whether the "OK" button on this error screen has been clicked. If the “OK” button on the error screen has not been clicked (step S501-16: No), the step S
The error screen display of 501-015 is continued. When the "OK" button on the error screen is clicked (step S
501-16: Yes), returning to step S501-09 to display the buy-in request entry screen shown in FIG.

If the client computer 9 determines that there is no mistake in the input data (step S501-14: Yes), the process proceeds to step S501-1.
7. In "Declare the claim. Are you sure?" Yes /
No ”” is displayed. Next, in step S501-18, it is determined whether or not “Yes” on the buy-in request declaration screen has been clicked. When "Yes" is not clicked (step S501-18: N
o) In step S501-19, it is determined whether or not "No" is clicked on the buy-in request declaration screen. If “No” on the buy-in claim report screen has not been clicked (step S501-19: No), neither “Yes” nor “No” has been clicked, and the user ends the processing on the buy-in claim report screen. If not, the process returns to step S501-17, and the buy-in request report screen display is continued.

[0941] If "No" is clicked on the buy-in request declaration screen (step S501-19: Yes),
Returning to step S501-09 via A in FIG. 139, the buy-in claim report entry screen in FIG. 152 is displayed. If "Yes" is clicked on the buy-in request declaration screen (step S501-18: Yes), step S50
In 1-20, it is determined whether the check on the server computer 4 side has determined that there is no mistake in the operation on the client computer 9 side.

[0942] If it is determined by the check on the server computer 4 that there is no mistake in the operation on the client computer 9 (step S501-20: Yes),
In step S501-23, "Bill number nnn" in FIG.
Was assigned and provisionally received. Will you continue to file a buy-in claim? A temporary receipt confirmation screen of "Yes / No" is displayed. Next, Step S501-24
It is determined whether or not "Yes" on the temporary receipt confirmation screen has been clicked. If “Yes” is not clicked (step S
501-22: No), and in a step S501-25, it is determined whether or not “No” on the temporary receipt confirmation screen is clicked.
If "No" on the provisional receipt confirmation screen has not been clicked (step S501-25: No), "Yes"
Assuming that none of "No" has been clicked and the user has not finished the processing on the temporary receipt confirmation screen, the process returns to step S501-23, and the temporary receipt confirmation screen display is continued.

If "No" on the temporary receipt confirmation screen is clicked (step S501-25: Yes), the flow returns to step S501-03 to display a buy-in request status reception screen. If “Yes” is clicked on the provisional receipt confirmation screen (step S501-24: Yes), the process returns to step S501-09 via A in FIG. 139, and displays the buy-in bill entry entry screen in FIG. 152.

If the server computer 4 does not determine that there is no mistake in the operation on the client computer 9 (step S501-20: N)
o), that is, when it is determined that there is an error in the operation on the client computer 9 side, step S501-2
In step S501-22, an error screen such as a screen "No acceptance due to outside buy-in request reception time" is displayed. In step S501-22, it is determined whether the "OK" button on the error screen is clicked. "O" on the error screen
If the “K” button is not clicked (step S5
01-22: No), the error screen display in step S501-21 is continued. When the “OK” button on the error screen is clicked (Step S501-22: Yes)
s), the process returns to step S501-03, and a buy-in request status reception screen is displayed. In the flowchart of FIG. 139, the above processing is repeated.

FIG. 140 is a screen transition diagram showing a buy-in billing business screen (flow of billing change processing). FIG.
When the buy-in request is selected on the fail management 345 tab screen displayed by selecting the fail management 345 tab on the home screen, the processing in FIG. 140 starts.

[0946] In step S502-01, it is determined whether it is outside the entry reception time. If it is outside the entry reception time (S502-02: Yes), step S502-
At 02, a buy-in request status reception screen, which is a main screen related to a buy-in request, is displayed as a read-only screen. That is, a claim report button (8) and a claim change button (9)
148 except that the buttons such as are not displayed.
A screen similar to the buy-in request status reception screen is displayed.
In this screen, since each button is not displayed, an input operation such as a button click cannot be performed.

[0947] If it is not outside the entry reception time (S50)
2-01: No), that is, if it is within the entry reception time, in step S502-03, the buy-in request status reception screen of FIG. 148, which is the main screen related to the buy-in request, is displayed. At this time, if there is buy-in request reception status data, the reception status data is displayed as a list as shown in FIG. 148, and if there is no buy-in request reception status data, only the title portion is displayed as shown in FIG. 151. . Next, in step S501-04, FIG.
It is determined whether the charge change button (9) is clicked.
If the bill change button (9) has not been clicked (Step S502-04: No), Step S502-0.
3, the display of the buy-in request status reception screen is continued.

If the bill change button (9) is clicked (step S502-04: Yes), step S5
In 02-05, it is determined whether or not it is outside the reception time of the buy-in change report entry. If the buy-in billing change entry is outside the acceptance time (step S502-05: Yes), an error screen of "cannot be accepted because it is outside the buy-in bill report acceptance time" in FIG. 150 is displayed in step S502-06. It is determined whether the "OK" button on the error screen has been clicked in step S502-07. If the “OK” button on the error screen has not been clicked (Step S502-07: No), Step S502-06
Continue to display the error screen. When the "OK" button on the error screen is clicked (step S502-07:
Yes), returns to step S502-03, and displays a buy-in request status reception screen.

[0949] If it is not outside the reception time of the buy-in request entry (step S502-05: No), that is, if it is within the reception time of the entry, step S502-0.
At 8, it is determined whether the entry whose change is specified is a modifiable version. If the version is not changeable (step S50
2-08: No), at step S502-12, an error screen saying "Charge cannot be made" is displayed, and at step S502-13, it is determined whether the "OK" button on the error screen has been clicked. When the "OK" button on the error screen is not clicked (step S502-1)
3: No), the error screen display in step S502-12 is continued. When the “OK” button on the error screen is clicked (step S502-13: Yes), the process returns to step S502-03, and the buy-in request status reception screen is displayed.

If the entry whose change is specified is a changeable version (step S502-08: Yes), the buy-in request change entry screen shown in FIG. 156 is displayed in step S502-09. Next, Step S502-10
Then, it is determined whether the "OK" button (6) on the buy-in request change entry screen is clicked. When the "OK" button (6) has not been clicked (step S502)
-10: No), it is determined whether the "cancel" button (7) has been clicked in step S502-11.

If the “cancel” button (7) has not been clicked (step S502-11: No), it is determined that the user has not finished the processing on the screen, and the process returns to step S502-09 to request the buy-in shown in FIG. 156. Continue the change entry screen display. When the "Cancel" button (7) is clicked (step S502-1)
1: Yes), it is determined that there is no intention to change the buy-in request, and the process returns to step S502-03 to display a buy-in request status reception screen.

[0952] "OK" on the buy-in billing change entry screen
When Button (6) is Clicked (Step S502)
(-10: Yes), it is determined in step S502-14 whether a check on the client computer 9 side has determined that there is no mistake in the input data. When the client computer 9 does not determine that there is no mistake in the input data (step S502-14: N
o), that is, if there is a mistake in the input data as a result of the check, an error screen such as "Please input a billing quantity of 1 or more" is displayed in step S502-15, and in step S502-16, " It is determined whether the "OK" button has been clicked. When the "OK" button on the error screen is not clicked (step S502-1)
6: No), the error screen display in step S502-014 is continued. If the "OK" button on the error screen is clicked (step S502-16: Yes), the flow returns to step S502-09, and the buy-in request change entry screen of FIG. 156 is displayed.

If it is determined by the check on the client computer 9 side that there is no mistake in the input data (step S502-14: Yes), step S502-1 is performed.
7. In the "Change billing. Are you sure?" Yes /
No ”” is displayed. Next, in step S502-18, it is determined whether or not “Yes” on the buy-in request change screen has been clicked. When "Yes" is not clicked (step S502-18: N
o), it is determined in step S502-19 whether "No" on the buy-in request change screen is clicked. If "No" on the buy-in request change screen has not been clicked (step S502-19: No), neither "Yes" nor "No" has been clicked, and the user ends the processing on the buy-in request change screen. If not, the process returns to step S502-17 to continue the buy-in request change screen display.

[0954] If "No" is clicked on the buy-in request change screen (step S502-19: Yes),
After returning to step S502-09 via B in FIG. 140, the buy-in request change entry screen in FIG. 156 is displayed. If "Yes" on the buy-in request change screen is clicked (step S502-18: Yes), step S50
In 2-20, it is determined whether or not it is determined by the check on the server computer 4 side that there is no mistake in the operation on the client computer 9 side.

If the server computer 4 checks to determine that there is no mistake in the operation on the client computer 9 (step S502-20: Yes),
In step S502-23, a temporary receipt confirmation screen "Temporary received" is displayed. Next, step S50
In 2-24, it is determined whether or not “OK” on the temporary receipt confirmation screen is clicked. If "OK" has not been clicked (step S502-24: No), step S502-2
3 and the display of the temporary receipt confirmation screen is continued.

If "OK" on the temporary receipt confirmation screen is clicked (step S502-24: Yes), the flow returns to step S502-03 to display a buy-in request status reception screen. When it is not determined that there is no mistake in the operation on the client computer 9 by the check on the server computer 4 side (step S502-20: No),
That is, if it is determined that there is an error in the operation on the client computer 9 side, an error screen such as a screen "No reception is accepted because the buy-in request is not accepted" is displayed in step S502-21 in FIG. Then, it is determined whether or not the “OK” button on the error screen is clicked in step S502-22. When the “OK” button on the error screen is not clicked (step S502-2)
2: No), the error screen display in step S502-21 is continued. If the “OK” button on the error screen is clicked (step S502-22: Yes), the process returns to step S502-03, and the buy-in request status reception screen is displayed. In the flowchart of FIG. 140, the above processing is repeated.

[0957] Fig. 141 is a screen transition diagram showing a buy-in billing business screen (flow of billing cancellation processing). FIG.
When the buy-in request is selected on the fail management 345 tab screen displayed by selecting the fail management 345 tab on the home screen, the processing in FIG. 141 starts.

[0958] In step S503-01, it is determined whether it is outside the entry reception time. If the time is outside the entry reception time (S503-02: Yes), step S503-
At 02, a buy-in request status reception screen, which is a main screen related to a buy-in request, is displayed as a read-only screen. That is, a claim report button (8) and a claim change button (9)
148 except that the buttons such as are not displayed.
A screen similar to the buy-in request status reception screen is displayed.
In this screen, since each button is not displayed, an input operation such as a button click cannot be performed.

[0959] If it is not outside the entry reception time (S50)
3-01: No), that is, if it is within the entry reception time, in step S503-03, the buy-in request status reception screen of FIG. 148, which is the main screen related to the buy-in request, is displayed. At this time, if there is buy-in request reception status data, the reception status data is displayed as a list as shown in FIG. 148, and if there is no buy-in request reception status data, only the title portion is displayed as shown in FIG. 151. .

Next, in step S503-04, FIG.
It is determined whether the request cancel button (10) at 48 has been clicked. If the request cancel button (10) has not been clicked (Step S503-04: No), Step S5
Returning to 03-03, the display of the buy-in request status reception screen is continued. When the request cancel button (10) is clicked (Step S503-04: Yes), Step S5
In 03-05, it is determined whether or not it is outside the reception time of the buy-in request cancellation entry.

[0961] If the buy-in request cancellation entry is outside the acceptance time (step S503-05: Yes), an error screen of "not accepted due to outside of the buy-in request declaration acceptance time" in Fig. 150 in step S503-06 is displayed. Is displayed, and "O" on the error screen is displayed in step S503-07.
It is determined whether the "K" button has been clicked. If the “OK” button on the error screen has not been clicked (step S503-07: No), the error screen display in step S503-06 is continued. When the "OK" button on the error screen is clicked (step S503-07: Yes)
s), the process returns to step S503-03, and a buy-in request status reception screen is displayed.

[0962] If the time is not within the reception time of the buy-in request cancellation entry (step S503-05: No), that is, if it is within the reception time of the entry, step S503-0 is executed.
At 8, it is determined whether the buy-in request can be canceled. If the buy-in request is not a cancelable version (step S
503-08: No), an error screen "Cannot cancel request" is displayed in step S503-12, and "O" in the error screen is displayed in step S503-13.
It is determined whether the "K" button has been clicked. If the “OK” button on the error screen has not been clicked (step S503-13: No), the error screen display in step S503-12 is continued. When the "OK" button on the error screen is clicked (step S503-13: Yes)
s), the process returns to step S503-03, and a buy-in request status reception screen is displayed.

If the buy-in request is a version that can be canceled (step S503-08: Yes), step S5
03-09, "Do you want to cancel the following claim declaration?
(No., edition number, classification, brand name, brand code, billing quantity) "buy-in claim report cancellation entry screen" Yes / No "is displayed. Next, step S503-1
At 0, it is determined whether the “Yes” button on the buy-in request declaration cancellation entry screen has been clicked. If the “Yes” button has not been clicked (step S503-10: N
o) In step S501-11, it is determined whether the "No" button has been clicked.

[0964] If the "No" button has not been clicked (step S503-11: No), it is determined that the user has not finished the process on the screen yet, and the process proceeds to step S50.
Returning to 3-09, the display of the buy-in request declaration cancellation entry screen is continued. If the “No” button is clicked (step S503-11: Yes), it is determined that there is no intention to cancel the buy-in request declaration, and the process proceeds to step S503-0.
3 and a buy-in request status reception screen is displayed.

[0965] When the "Yes" button on the buy-in request declaration cancel entry screen is clicked (step S503-
10: Yes), in a step S503-14, it is determined whether or not the check on the server computer 4 side has determined that there is no mistake in the operation on the client computer 9 side. If it is determined by the check on the server computer 4 side that there is no mistake in the operation on the client computer 9 side (step S503-14: Yes), a temporary cancellation confirmation screen stating "Temporarily canceled" in step S503-17. Is displayed. Next, Step S503-16
It is determined whether "OK" on the temporary cancellation confirmation screen has been clicked. If "OK" is not clicked (step S
503-18: No), returning to step S503-17 to continue displaying the temporary cancellation confirmation screen.

If "OK" on the temporary cancellation confirmation screen is clicked (step S503-18: Yes), the flow returns to step S503-03 to display a buy-in request status reception screen. If it is not determined by the check on the server computer 4 that there is no mistake in the operation on the client computer 9 (step S503-14: No),
That is, if it is determined that there is an error in the operation on the client computer 9 side, an error screen such as a screen “No receivable due to outside of the buy-in request declaration reception time” in FIG. 150 is displayed in step S503-15. Then, it is determined whether the “OK” button on the error screen is clicked in step S503-16. When the "OK" button on the error screen is not clicked (step S503-1)
6: No), the error screen display in step S503-15 is continued. If the “OK” button on the error screen is clicked (step S503-16: Yes), the process returns to step S503-03, and the buy-in request status reception screen is displayed. In the flowchart of FIG. 141, the above processing is repeated.

[0967] Fig. 142 is a screen transition diagram showing a buy-in withdrawal withdrawal business screen (a processing flow of a claim withdrawal declaration). When the buy-in request withdrawal is selected on the fail management 345 tab screen displayed by selecting the fail management 345 tab on the home screen in FIG. 113, the processing in FIG. 142 starts.

[0968] In step S504-01, it is determined whether the time is outside the entry reception time. If it is outside the entry reception time (S504-01: Yes), step S504-
At 02, a buy-in request withdrawal status reception screen, which is a main screen related to a buy-in request, is displayed as a read-only screen. That is, a screen similar to the buy-in request withdrawal status reception screen of FIG. 165 is displayed except that the buttons such as the request for withdrawal declaration button (8) and the request for withdrawal change button (9) are not displayed. . In this screen, since each button is not displayed, an input operation such as a button click cannot be performed.

[0969] If it is not outside the entry reception time (S50)
4-01: No), that is, if it is within the entry reception time, in step S504-03, a buy-in request withdrawal status reception screen of FIG. 165 which is a main screen of the buy-in request withdrawal relationship is displayed. At this time, if there is buy-in request withdrawal reception status data, the list of reception status data is displayed as shown in FIG. 165, and if there is no buy-in request withdrawal reception status data, only the title portion is displayed.

[0970] Next, in step S504-03, FIG.
It is determined whether the claim withdrawal declaration button (8) is clicked. If the bill withdrawal declaration button (8) has not been clicked (step S504-04: No), the process returns to step S504-03, and the display of the buy-in withdrawal withdrawal status reception screen is continued. When the request for withdrawal declaration button (8) is clicked (step S504-04: Yes), it is determined in step S504-05 whether or not it is outside the reception time of the buy-in withdrawal declaration entry.

[0971] If it is outside the reception time of the buy-in request withdrawal entry (step S504-05: Yes), it will not be accepted in step S504-06 because it is outside the "buy-in request withdrawal reception acceptance time" in Fig. 167. Is displayed, and it is determined in step S504-07 whether the "OK" button on the error screen has been clicked. If the “OK” button on the error screen has not been clicked (step S504-07: No), step S504
The error screen display of -06 is continued. "O" on the error screen
When the "K" button is clicked (step S504-
07: Yes), returning to step S504-03 to display a buy-in request withdrawal status reception screen.

[0972] If it is not outside the reception time of the buy-in request withdrawal entry (step S504-05: No), that is, if it is within the entry reception time, step S504 is executed.
At -08, it is determined whether there is brand information that can be entered for a buy-in withdrawal declaration entry. When there is no brand information for which a buy-in claim withdrawal entry can be made (step S504-08: N
o) In step S504-12, a screen with no brand "No buyable brands can be withdrawn" is displayed. In step S504-13, "OK" on the brand-less screen is displayed.
Determine if the button was clicked. If the "OK" button on the brand-less screen is not clicked (step S504-13: No), the brand-less screen display of step S504-12 is continued. When the “OK” button on the brand-less screen is clicked (step S504-13:
Yes), returns to step S504-03, and displays a buy-in request withdrawal status reception screen.

[0973] If there is brand information that can be entered for a buy-in withdrawal declaration entry (step S504-08: Yes),
In step S504-09, the buy-in request withdrawal declaration entry screen of FIG. 168 is displayed. Next, step S50
In 4-10, select "O" on the buy-in withdrawal declaration entry screen.
It is determined whether the "K" button (3) has been clicked. "O
If the “K” button (3) has not been clicked (Step S504-10: No), it is determined in Step S504-11 whether the “Cancel” button (4) has been clicked.

If the “cancel” button (4) has not been clicked (step S504-11: No), it is determined that the user has not finished the processing on the screen, and the process returns to step S504-09 to request the buy-in shown in FIG. 168. Continue to display the withdrawal entry screen. When "Cancel" Button (4) is Clicked (Step S504-
11: Yes), it is determined that there is no intention to withdraw the buy-in request, and the process returns to step S504-03 to display a buy-in request withdrawal status reception screen.

[0975] In the buy-in request withdrawal declaration entry screen, "O
When the "K" button (3) is clicked (step S5
04-10: Yes), it is determined in step S504-14 whether it is determined by the check on the client computer 9 side that there is no mistake in the input data.

[0976] If it is not determined by the check on the client computer 9 side that there is no mistake in the input data (step S504-14: No), that is, if there is a mistake in the input data by the check, step S504 is performed.
At -15, an error screen such as "Please select withdrawal request" is displayed, and at step S504-16, it is determined whether the "OK" button on this error screen has been clicked.
If the “OK” button on the error screen has not been clicked (step S504-16: No), step S50
The error screen display of 4-015 is continued. When the “OK” button on the error screen is clicked (step S50)
4-16: Yes), returning to step S504-09;
The buy-in request withdrawal entry screen of FIG. 168 is displayed.

If it is determined by the check on the client computer 9 side that there is no mistake in the input data (step S504-14: Yes), step S504-1 is performed.
7. In step 7, a "Declare claim withdrawal. Are you sure? 'Yes / No'" buy-in claim withdrawal screen is displayed.

[0978] Next, in step S504-18, it is determined whether or not "Yes" is clicked on the buy-in request withdrawal declaration screen. If “Yes” has not been clicked (step S504-18: No), it is determined in step S504-19 whether “No” on the buy-in request withdrawal declaration screen has been clicked. When “No” is not clicked on the buy-in request withdrawal declaration screen (step S504-1)
9: No), it is determined that neither “yes” nor “no” has been clicked, and the user has not finished the processing on the buy-in request withdrawal declaration screen, and the process proceeds to step S504-17.
And the display of the buy-in request withdrawal declaration screen is continued.

[0979] When "No" is clicked on the buy-in request withdrawal declaration screen (step S504-19: Ye)
s), and returns to step S504-09 via C in FIG. 142, and displays the buy-in request withdrawal declaration entry screen in FIG. 168. If "Yes" is clicked on the buy-in request withdrawal declaration screen (step S504-16: Yes), it is determined in step S504-18 that there is no mistake in the operation on the client computer 9 side by checking the server computer 4 side. It is determined whether it has been performed.

[0980] If it is determined by the check on the server computer 4 that there is no mistake in the operation on the client computer 9 (step S504-20: Yes),
In step S504-23, “withdrawal number nnn” in FIG.
Was assigned and provisionally received. Do you want to continue to file a buy-in withdrawal declaration? A temporary receipt confirmation screen of "Yes / No" is displayed. Next, step S504-
At 24, it is determined whether or not “Yes” on the temporary receipt confirmation screen has been clicked. If "yes" has not been clicked (step S504-24: No), it is determined in step S504-25 whether "no" on the temporary receipt confirmation screen has been clicked. If "No" on the temporary receipt confirmation screen has not been clicked (step S504-25: No), neither "Yes" nor "No" has been clicked, and the user ends the processing on the temporary receipt confirmation screen. If not, the process returns to step S504-23 to continue displaying the temporary receipt confirmation screen.

[0981] If "No" on the provisional receipt confirmation screen is clicked (step S504-25: Yes), the flow returns to step S504-03, and the buy-in request withdrawal status reception screen is displayed. When "Yes" is clicked on the temporary receipt confirmation screen (step S504-24: Yes), FIG.
After returning to step S504-09 via C of FIG.
Display the buy-in request withdrawal declaration entry screen of.

[0982] If it is determined by the check on the server computer 4 that there is no mistake in the operation on the client computer 9 (step S504-20: N
o), that is, when it is determined that there is an error in the operation on the client computer 9 side, step S504-2
In step S504-22, an error screen such as a screen saying that "it is not accepted because it is outside the buy-in request withdrawal report acceptance time" is displayed in step S504-22.
It is determined whether the "K" button has been clicked. If the “OK” button on the error screen has not been clicked (step S504-22: No), the error screen display in step S504-21 is continued. When the "OK" button on the error screen is clicked (step S504-22: Yes)
s), returning to step S504-03 to display a buy-in request withdrawal status reception screen. In the flowchart of FIG. 142, the above processing is repeated.

FIG. 143 is a screen transition diagram showing a buy-in withdrawal withdrawal business screen (flow of bill withdrawal change processing). When the user selects the withdrawal of the buy-in request on the fail management 345 tab screen displayed by selecting the fail management 345 tab on the home screen in FIG. 113, the processing in FIG. 143 starts.

[0984] In step S505-01, it is determined whether it is outside the entry reception time. If it is outside the entry reception time (S505-01: Yes), step S505-
At 02, a buy-in request withdrawal status reception screen, which is a main screen related to a buy-in request, is displayed as a read-only screen. That is, a screen similar to the buy-in request withdrawal status reception screen of FIG. 165 is displayed except that the buttons such as the request for withdrawal declaration button (8) and the request for withdrawal change button (9) are not displayed. . In this screen, since each button is not displayed, an input operation such as a button click cannot be performed.

[0985] If not outside the entry reception time (S50)
5-01: No), that is, if it is within the entry reception time, in step S505-03, a buy-in request withdrawal status reception screen of FIG. 165 which is the main screen of the buy-in request withdrawal relationship is displayed. At this time, if there is buy-in request withdrawal reception status data, the list of reception status data is displayed as shown in FIG. 165, and if there is no buy-in request withdrawal reception status data, only the title portion is displayed.

Next, in step S505-04, FIG.
It is determined whether the request withdrawal change button (9) at 65 has been clicked. If the bill withdrawal change button (9) is not clicked (step S505-04: No), the process returns to step S505-03, and the display of the buy-in withdrawal status acceptance screen is continued. If the bill withdrawal change button (9) is clicked (step S505-04: Yes), it is determined in step S505-05 whether it is outside the reception time of the buy-in withdrawal change change entry.

[0987] If the buy-in request withdrawal change entry is outside the acceptance time (step S505-05: Yes), it will not be accepted in step S505-06 because it is outside the "buy-in request withdrawal report acceptance time" in Fig. 167. Is displayed, and it is determined in step S505-07 whether the "OK" button on the error screen has been clicked. If the “OK” button on the error screen has not been clicked (Step S505-07: No), Step S505
The error screen display of -06 is continued. "O" on the error screen
When the "K" button is clicked (step S505-
07: Yes), returning to step S505-03 to display a buy-in request withdrawal status reception screen.

[0988] If it is not outside the reception time of the buy-in request withdrawal entry (step S505-05: No), that is, if it is within the reception time of the entry, step S505 is performed.
At -08, it is determined whether the entry specified to be changed is a changeable version. If the version is not changeable (step S
505-08: No), at step S505-12, an error screen "Cannot withdraw." Is displayed, and at step S505-13, "OK" on the error screen is displayed.
Determine if the button was clicked. "O" on the error screen
If the “K” button is not clicked (step S5
05-13: No), the error screen display in step S505-12 is continued. When the “OK” button on the error screen is clicked (step S505-13: Ye)
s), returning to step S505-03, and displaying a buy-in request withdrawal status reception screen.

If the entry whose change is specified is a modifiable version (step S505-08: Yes), the buy-in withdrawal change entry screen of FIG. 170 is displayed in step S505-09. Next, step S505-
At 10, it is determined whether the “OK” button (4) on the buy-in withdrawal change entry screen has been clicked. If the “OK” button (4) has not been clicked (step S50)
5-10: No), it is determined whether or not the “cancel” button (5) is clicked in step S505-11.

If the “cancel” button (5) has not been clicked (step S505-11: No), it is determined that the user has not finished the processing on the screen, and the process returns to step S505-09 to request the buy-in shown in FIG. 170. Continue withdrawal change entry screen display. When the "Cancel" button (5) is clicked (step S505-
11: Yes), it is determined that there is no intention to change the withdrawal of the buy-in request, and the process returns to step S505-03 to display the withdrawal status of the buy-in request.

[0909] In the buy-in request withdrawal change entry screen, "O
"K" button (4) is clicked (step S5
05-10: Yes), in step S505-14, it is determined whether or not a check on the client computer 9 side has determined that there is no mistake in the input data. When the client computer 9 does not determine that there is no mistake in the input data (step S505-1)
4: No), that is, if there is a mistake in the input data as a result of the check, an error screen such as "Please input a billing withdrawal quantity of 1 or more" is displayed in step S505-15, and this error is displayed in step S505-16. "O" on the error screen
It is determined whether the "K" button has been clicked. If the “OK” button on the error screen has not been clicked (step S505-16: No), the error screen display in step S505-015 is continued. When the “OK” button on the error screen is clicked (step S505-16: Y
es), the process returns to step S505-09, and the buy-in request withdrawal change entry screen of FIG. 170 is displayed.

If it is determined by the check on the client computer 9 side that there is no mistake in the input data (step S505-14: Yes), step S505-1 is performed.
In step 7, a "Bill withdrawal change. Are you sure? 'Yes / No'" buy-in bill withdrawal change screen is displayed. Next, in step S505-18, it is determined whether or not “Yes” is clicked on the buy-in withdrawal withdrawal change screen.
If "Yes" is not clicked (step S50)
5-18: No), it is determined in step S505-19 whether "No" on the buy-in request withdrawal change screen is clicked. When "No" is not clicked on the buy-in request withdrawal change screen (step S505-19: N
o) Assuming that neither "Yes" nor "No" has been clicked and the user has not finished the processing on the buy-in request withdrawal change screen, the process returns to step S505-17, and the buy-in request withdrawal change screen display To continue.

[0993] When "No" is clicked on the buy-in request withdrawal change screen (step S505-19: Ye)
s), the process returns to step S505-09 via D in FIG. 143, and the buy-in request withdrawal change entry screen in FIG. 170 is displayed. If "Yes" is clicked on the buy-in request withdrawal change screen (step S505-18: Yes), it is determined in step S505-20 that there is no mistake in the operation on the client computer 9 side by checking the server computer 4 side. It is determined whether it has been performed.

If it is determined by the check on the server computer 4 side that there is no mistake in the operation on the client computer 9 side (step S505-20: Yes),
In step S505-23, a temporary receipt confirmation screen "Temporary received" is displayed. Next, step S50
In 5-24, it is determined whether or not “OK” on the temporary receipt confirmation screen is clicked. If "OK" is not clicked (step S505-22: No), step S505-2
4, the display of the temporary receipt confirmation screen is continued.

[0995] If "OK" is clicked on the temporary receipt confirmation screen (step S505-24: Yes), the flow returns to step S505-03, and the buy-in request withdrawal status acceptance screen is displayed. When it is not determined by the check on the server computer 4 that there is no mistake in the operation on the client computer 9 (step S505-20: N
o), that is, when it is determined that there is an error in the operation on the client computer 9 side, step S505-2.
In step S505-22, an error screen such as a screen "No acceptance due to outside of buy-in request withdrawal request acceptance time" is displayed in step S505-22.
It is determined whether the "K" button has been clicked. If the “OK” button on the error screen has not been clicked (step S505-22: No), the error screen display in step S505-21 is continued. When the “OK” button on the error screen is clicked (step S505-22: Ye
s), returning to step S505-03, and displaying a buy-in request withdrawal status reception screen. In the flowchart of FIG. 143, the above processing is repeated.

[0996] Fig. 144 is a screen transition diagram showing a buy-in withdrawal withdrawal business screen (a flow of bill withdrawal cancellation processing). When the user selects the withdrawal of the buy-in request on the fail management 345 tab screen displayed by selecting the fail management 345 tab on the home screen of FIG. 113, the processing of FIG. 144 starts.

[0997] In step S506-01, it is determined whether it is outside the entry reception time. If it is outside the entry reception time (S506-01: Yes), step S506-
At 02, a buy-in request withdrawal status reception screen, which is a main screen related to a buy-in request, is displayed as a read-only screen. That is, a screen similar to the buy-in request withdrawal status reception screen of FIG. 165 is displayed except that the buttons such as the request for withdrawal declaration button (8) and the request for withdrawal change button (9) are not displayed. . In this screen, since each button is not displayed, an input operation such as a button click cannot be performed.

[0998] If the time is not outside the entry reception time (S50)
6-01: No), that is, if it is within the entry reception time, in step S506-03, a buy-in request withdrawal status reception screen of FIG. 165, which is the main screen of the buy-in request withdrawal relationship, is displayed. At this time, if there is buy-in request withdrawal reception status data, the list of reception status data is displayed as shown in FIG. 165, and if there is no buy-in request withdrawal reception status data, only the title portion is displayed.

[0999] Next, in step S506-04, FIG.
It is determined whether the withdrawal request withdrawal button (10) is clicked. If the request cancellation button (10) has not been clicked (step S506-04: No), the process returns to step S506-03 and the display of the buy-in request withdrawal status reception screen is continued. When the request withdrawal button (10) is clicked (step S506-04: Ye)
s) In step S506-05, it is determined whether or not it is outside the reception time of the buy-in request cancellation entry.

[1000] If it is outside the acceptance time of the buy-in withdrawal cancellation entry (step S506-05: Yes), it will not be accepted in step S506-06 because it is outside the "buy-in request withdrawal report acceptance time" in FIG. Is displayed, and it is determined in step S506-07 whether the “OK” button on the error screen has been clicked. If the “OK” button on the error screen has not been clicked (step S506-07: No), step S506
The error screen display of -06 is continued. "O" on the error screen
When the "K" button is clicked (step S506-
07: Yes), returning to step S506-03 to display a buy-in request withdrawal status reception screen.

[1001] If it is not outside the acceptance time of the buy-in request withdrawal cancellation entry (step S506-05: No), that is, if it is within the entry acceptance time, step S506 is executed.
At -08, it is determined whether the withdrawal of the buy-in request is a cancelable version. If the withdrawal of the buy-in request is not a cancelable version (step S506-08: No), step S506 is performed.
At -12, an error screen "Cannot cancel withdrawal cannot be canceled" is displayed, and at step S506-13, it is determined whether the "OK" button on the error screen has been clicked. If the "OK" button on the error screen has not been clicked (step S506-13: No), step S506
The error screen display of 506-12 is continued. When the "OK" button on the error screen is clicked (step S5
06-13: Yes), returning to step S506-03, and displaying a buy-in request withdrawal status reception screen.

[1002] If the withdrawal of the buy-in request is a version that can be canceled (step S506-08: Yes), the process proceeds to step S506-09. Version number, category, brand name, brand code, withdrawal quantity) A "yes / no""buy-in request withdrawal cancellation cancellation entry screen" is displayed. Next, in step S506-10, it is determined whether the “Yes” button on the buy-in request withdrawal declaration cancellation entry screen has been clicked. If the “Yes” button has not been clicked (Step S506-10: No), Step S501-11
To determine if the "No" button has been clicked.

[1003] If the "No" button has not been clicked (step S506-11: No), it is determined that the user has not finished the process on the screen yet, and the process proceeds to step S50.
Returning to 6-09, the display of the buy-in request withdrawal cancellation cancellation entry screen is continued. If the "No" button is clicked (step S506-11: Yes), it is determined that there is no intention of canceling the withdrawal of the buy-in request, and step S5 is determined.
Returning to 06-03, a buy-in request withdrawal status reception screen is displayed.

[1004] When the "Yes" button on the buy-in request withdrawal declaration cancellation entry screen is clicked (step S50)
6-10: Yes), it is determined in step S506-14 whether it is determined by the check on the server computer 4 side that there is no mistake in the operation on the client computer 9 side. If it is determined by the check on the server computer 4 side that there is no mistake in the operation on the client computer 9 side (step S506-14: Yes), a temporary cancellation confirmation screen stating "Temporarily canceled" in step S506-17. Is displayed. Next, step S506-1
In step 8, it is determined whether "OK" on the temporary cancellation confirmation screen has been clicked. If "OK" has not been clicked (step S506-18: No), the process returns to step S506-17, and the temporary cancellation confirmation screen display is continued.

If "OK" on the temporary cancellation confirmation screen is clicked (step S506-18: Yes), the flow returns to step S506-03 to display a buy-in request withdrawal status acceptance screen. When it is not determined that there is no mistake in the operation on the client computer 9 by the check on the server computer 4 side (step S506-14: N
o), that is, when it is determined that there is an error in the operation on the client computer 9 side, step S506-1
In step S506-16, an error screen such as a screen "No, it cannot be accepted because it is outside the buy-in request withdrawal acceptance time" is displayed in step S506.
It is determined whether the "K" button has been clicked. If the “OK” button on the error screen has not been clicked (step S506-16: No), the error screen display in step S506-15 is continued. When the "OK" button on the error screen is clicked (step S506-16: Yes)
s), returning to step S506-03, and displaying a buy-in request withdrawal status reception screen. In the flowchart of FIG. 144, the above processing is repeated.

FIG. 145 is a screen transition diagram showing a buy-in execution business screen (a flow of an order application process). FIG.
145 starts when the buy-in order is selected on the fail management 345 tab screen displayed by selecting the fail management 345 tab on the home screen of FIG.

In step S507-01, it is determined whether the time is outside the entry reception time. When it is outside the reception time of the entry (S507-01: Yes), step S507-
At 02, a buy-in order status reception screen, which is a main screen related to the buy-in order, is displayed as a read-only screen. That is, a screen similar to the buy-in order status reception screen of FIG. 157 is displayed except that the buttons such as the claim withdrawal declaration button (8) and the claim withdrawal change button (9) are not displayed. In this screen, since each button is not displayed, an input operation such as a button click cannot be performed.

[1008] If not outside the entry reception time (S50)
7-01: No), that is, if it is within the entry reception time, in step S507-03, the buy-in order status reception screen of FIG. 157, which is the main screen related to the buy-in order, is displayed. At this time, if there is buy-in order reception status data, the reception status data is displayed as a list as shown in FIG. 157, and if there is no buy-in order reception status data, only the title portion is displayed. Then
In step S507-04, it is determined whether the order application button (8) in FIG. 157 has been clicked. When the order application button (8) is not clicked (step S507)
-04: No), the process returns to step S507-03, and the display of the buy-in order status reception screen is continued.

If the order application button (8) is clicked (step S507-04: Yes), step S5
At 07-05, it is determined whether it is outside the reception time of the buy-in order application entry. If it is outside the reception time of the buy-in order application entry (step S507-05: Yes), an error screen is displayed in step S507-06, stating that "it cannot be accepted because it is outside the reception time of the buy-in order application" in FIG. It is determined whether the "OK" button on the error screen has been clicked in step S507-07. If the “OK” button on the error screen has not been clicked (Step S507-07: No), Step S507-06
Continue to display the error screen. When the "OK" button on the error screen is clicked (step S507-07:
Yes), returns to step S507-03, and displays a buy-in order status reception screen.

[1010] If it is not outside the reception time of the buy-in order application entry (step S507-05: No), that is, if it is within the reception time of the entry, step S507-0.
At 8, it is determined whether there is brand information for which a buy-in order application can be entered. If there is no brand information for which a buy-in order application entry can be made (step S507-08: No), a non-brand screen "No brand available for sell-in for buy-in" is displayed in step S507-12, and in step S507-13 It is determined whether the “OK” button on the brand-less screen has been clicked. When the “OK” button on the brand-less screen has not been clicked (step S507-1)
3: No), the brand-less screen display of step S507-12 is continued. If the “OK” button on the brand-less screen is clicked (step S507-13: Yes), the process returns to step S507-03 and displays the buy-in order status reception screen.

If there is brand information that allows a buy-in order application entry (step S507-08: Yes), a buy-in order application entry screen shown in FIG. 160 is displayed in step S507-09. Next, Step S507-10
It is determined whether the "OK" button (7) on the buy-in order application entry screen has been clicked. When the "OK" button (7) has not been clicked (step S507)
-10: No), it is determined whether or not the "cancel" button (8) is clicked in step S507-11.

If the “cancel” button (8) has not been clicked (step S507-11: No), it is determined that the user has not finished the processing on the screen, and the process returns to step S507-09, and the buy-in order shown in FIG. Continue to display the application entry screen. When the “Cancel” button (8) is clicked (step S507-1)
1: Yes), assuming that there is no intention to apply for a buy-in order, the process returns to step S507-03, and a buy-in order status reception screen is displayed.

[1013] "OK" on the buy-in order application entry screen
When Button (7) is Clicked (Step S507)
-10: Yes), it is determined in step S507-14 whether a check on the client computer 9 side has determined that there is no mistake in the input data.

[1014] When it is not determined that there is no mistake in the input data by the check on the client computer 9 side (step S507-14: No), that is, when there is a mistake in the input data by the check, step S507 is performed.
At -15, an error screen such as "Please input an order quantity of 1 or more" is displayed. At step S507-16, it is determined whether the "OK" button on this error screen is clicked. If the “OK” button on the error screen has not been clicked (step S507-16: No), step S
The error screen display of 507-15 is continued. When the "OK" button on the error screen is clicked (step S5
07-16: Yes), returning to step S507-09, and displaying the buy-in order application entry screen of FIG. 160.

If the client computer 9 determines that there is no mistake in the input data (step S507-14: Yes), the process proceeds to step S507-1.
7. In the "Apply for order. Are you sure?" Yes /
No ”” is displayed. Next, in step S507-18, it is determined whether “Yes” on the buy-in order application screen has been clicked. When "Yes" is not clicked (step S507-18: N
o) In step S507-19, it is determined whether or not "No" on the buy-in order application screen is clicked. When "No" on the buy-in order application screen is not clicked (step S507-19: No), neither "Yes" nor "No" is clicked, and the user finishes the processing on the buy-in order application screen. If not, the process returns to step S507-17 to continue displaying the buy-in order application screen.

[1016] If "No" is clicked on the buy-in order application screen (step S507-19: Yes),
Returning to step S507-09 via E in FIG. 145, the buy-in order application entry screen in FIG. 160 is displayed. If "Yes" is clicked on the buy-in order application screen (step S507-18: Yes), step S50
In 7-20, it is determined whether or not it is determined by the check on the server computer 4 side that there is no mistake in the operation on the client computer 9 side.

[1017] When it is determined by the check on the server computer 4 that there is no mistake in the operation on the client computer 9 (step S507-20: Yes),
In step S507-23, “order number nnn” in FIG.
Was assigned and provisionally received. Do you want to continue ordering? A temporary receipt confirmation screen of "Yes / No" is displayed. Next, in step S507-24, it is determined whether or not “Yes” on the temporary receipt confirmation screen has been clicked. If "Yes" is not clicked (step S507-
24: No), it is determined in step S507-25 whether "No" on the temporary receipt confirmation screen is clicked. If "No" on the temporary receipt confirmation screen has not been clicked (step S507-25: No), neither "Yes" nor "No" has been clicked, and the user ends the processing on the temporary receipt confirmation screen. If not, the process returns to step S507-23, and the temporary receipt confirmation screen display is continued.

[1018] If "No" on the temporary receipt confirmation screen is clicked (step S507-25: Yes), the flow returns to step S507-03, and the buy-in order status reception screen is displayed. If "Yes" is clicked on the temporary receipt confirmation screen (step S507-24: Yes), the process returns to step S507-09 via E in FIG. 145, and displays the buy-in order application entry screen in FIG. 160.

[1019] If it is not determined by the check on the server computer 4 that there is no mistake in the operation on the client computer 9 (step S507-20: N
o), that is, when it is determined that there is an error in the operation on the client computer 9 side, step S507-2.
In step S507-22, it is determined whether or not the "OK" button on the error screen is clicked in step S507-22. "O" on the error screen
If the “K” button is not clicked (step S5
07-22: No), the error screen display in step S507-21 is continued. When the “OK” button on the error screen is clicked (Step S507-22: Ye
s), returning to step S507-03, and displaying a buy-in order status reception screen. In the flowchart of FIG. 145, the above processing is repeated.

FIG. 146 is a screen transition diagram showing a buy-in execution business screen (flow of order change processing). FIG.
146 starts when the buy-in order is selected on the fail management 345 tab screen displayed by selecting the fail management 345 tab on the home screen of FIG.

[1021] In step S508-01, it is determined whether it is outside the entry reception time. If it is outside the reception time of the entry (S508-01: Yes), step S507-
At 02, a buy-in order status reception screen, which is a main screen related to the buy-in order, is displayed as a read-only screen. That is, a screen similar to the buy-in order status reception screen of FIG. 157 is displayed except that the buttons such as the claim withdrawal declaration button (8) and the claim withdrawal change button (9) are not displayed. In this screen, since each button is not displayed, an input operation such as a button click cannot be performed.

[1022] If not outside the entry reception time (S50)
8-01: No), that is, if it is within the entry reception time, in step S508-03, the buy-in order status reception screen of FIG. 157, which is the main screen related to the buy-in order, is displayed. At this time, if there is buy-in order reception status data, the reception status data is displayed as a list as shown in FIG. 157, and if there is no buy-in order reception status data, only the title portion is displayed as shown in FIG. 151. .

Next, in step S501-04, FIG.
It is determined whether or not the 57 order change button (9) is clicked. If the order change button (9) is not clicked (Step S508-04: No), Step S508
Returning to -03, the display of the buy-in order status reception screen is continued. If the order change button (9) is clicked (step S508-04: Yes), step S508-
At 05, it is determined whether it is outside the reception time of the buy-in order change entry.

If the buy-in order change entry is outside the acceptance time (step S508-05: Yes), in step S508-06, an error screen of FIG. Is displayed, and “O” on the error screen is displayed in step S508-07.
It is determined whether the "K" button has been clicked. If the “OK” button on the error screen has not been clicked (step S508-07: No), the error screen display of step S508-06 is continued. When the "OK" button on the error screen is clicked (step S508-07: Ye
s), returning to step S508-03, and displaying a buy-in order status reception screen.

[1025] If it is not outside the reception time of the buy-in order application entry (step S508-05: No), that is, if it is within the reception time of the entry, step S508-0.
At 8, it is determined whether the entry whose change is specified is a modifiable version. If the version is not changeable (step S50
8-08: No), an error screen "Order cannot be placed" is displayed in step S508-12, and it is determined in step S508-13 whether the "OK" button on the error screen is clicked. When the "OK" button on the error screen is not clicked (step S508-1)
3: No), the error screen display in step S508-12 is continued. If the "OK" button on the error screen is clicked (step S508-13: Yes), the process returns to step S508-03, and the buy-in order status reception screen is displayed.

If the entry whose change is specified is a changeable version (step S508-08: Yes), the buy-in order change entry screen of FIG. 163 is displayed in step S508-09. Next, Step S508-10
Then, it is determined whether the "OK" button (8) on the buy-in order change entry screen is clicked. When the "OK" button (8) has not been clicked (step S508)
-10: No), it is determined whether or not the "cancel" button (9) is clicked in step S508-11.

[1027] If the "cancel" button (9) is not clicked (step S508-11: No), it is determined that the user has not finished the processing on the screen, and the process returns to step S508-09, and the buy-in order shown in FIG. Continue to display the change entry screen. When the “Cancel” button (9) is clicked (step S508-1)
1: Yes), assuming that there is no intention to change the buy-in order, the process returns to step S508-03, and the buy-in order status reception screen is displayed. If the “OK” button (8) on the buy-in order change entry screen is clicked (step S508-10: Yes), step S508-14
It is determined whether there is no mistake in the input data by the check on the client computer 9 side.

[1028] If it is not determined by the check on the client computer 9 that there is no mistake in the input data (step S508-14: No), that is, if there is a mistake in the input data by the check, step S508 is performed.
At -15, an error screen such as "Please input an order quantity of 1 or more" is displayed. At step S508-16, it is determined whether the "OK" button on this error screen is clicked. If the "OK" button on the error screen has not been clicked (step S508-16: No), step S508
The error screen display of 508-015 is continued. When the "OK" button on the error screen is clicked (step S
508-16: Yes), returning to step S508-09 to display the buy-in order change entry screen of FIG. 163.

If it is determined by the check on the client computer 9 side that there is no mistake in the input data (step S508-14: Yes), step S508-1
Step 7: "I will change the order. Are you sure?" Yes /
No ”” is displayed.

[1030] Next, in step S508-18, it is determined whether or not "Yes" on the buy-in order change screen is clicked. If “Yes” is not clicked (step S
508-18: No), it is determined in step S508-19 whether "No" on the buy-in order change screen is clicked. When "No" is not clicked on the buy-in order change screen (step S508-19: N
o) Assuming that none of "Yes" and "No" has been clicked, and the user has not finished the processing on the buy-in order change screen, the process returns to step S508-17, and the buy-in order change screen display is continued.

[1030] If "No" on the buy-in order change screen is clicked (step S508-19: Yes),
Returning to step S508-09 via E in FIG. 146, the buy-in order change entry screen in FIG. 163 is displayed. If “Yes” is clicked on the buy-in order change screen (step S508-18: Yes), step S50
In step 8-20, it is determined whether or not the server computer 4 has determined that there is no mistake in the operation on the client computer 9 side.

[1032] If it is determined by the check on the server computer 4 that there is no mistake in the operation on the client computer 9 (step S508-20: Yes),
In step S508-23, a temporary receipt confirmation screen "Temporary received" is displayed. Next, step S50
At 8-24, it is determined whether or not “OK” on the temporary receipt confirmation screen is clicked. If "OK" has not been clicked (step S508-24: No), step S508-2
3 and the display of the temporary receipt confirmation screen is continued.

If "OK" on the temporary receipt confirmation screen is clicked (step S508-24: Yes), the flow returns to step S508-03, and the buy-in order status reception screen is displayed. If it is not determined by the check on the server computer 4 that there is no mistake in the operation on the client computer 9 (step S508-20: No),
That is, if it is determined that there is an error in the operation on the client computer 9 side, an error screen such as a screen such as "cannot be accepted due to outside of the buy-in application acceptance time" in FIG. 150 is displayed in step S508-21. Then, it is determined whether or not the “OK” button on the error screen has been clicked in step S508-22. When the "OK" button on the error screen is not clicked (step S508-2)
2: No), the error screen display in step S508-21 is continued. If the "OK" button on the error screen is clicked (step S508-22: Yes), the process returns to step S508-03, and the buy-in order status reception screen is displayed. In the flowchart of FIG. 146, the above processing is repeated.

FIG. 147 is a screen transition diagram showing a buy-in execution business screen (flow of processing for canceling an order). FIG.
147 is started when the buy-in order is selected on the fail management 345 tab screen displayed by selecting the fail management 345 tab on the home screen of FIG.

[1035] In step S509-01, it is determined whether the time is outside the entry reception time. If it is outside the entry reception time (S509-01: Yes), step S509-
At 02, a buy-in order status reception screen, which is a main screen related to the buy-in order, is displayed as a read-only screen. That is, a screen similar to the buy-in order status reception screen of FIG. 157 is displayed except that the buttons such as the claim withdrawal declaration button (8) and the claim withdrawal change button (9) are not displayed. In this screen, since each button is not displayed, an input operation such as a button click cannot be performed.

[1036] If it is not outside the entry reception time (S50)
9-01: No), that is, if it is within the entry reception time, in step S509-03, the buy-in order status reception screen of FIG. 157, which is the main screen related to the buy-in order, is displayed. At this time, if there is buy-in order reception status data, the reception status data is displayed as a list as shown in FIG. 157, and if there is no buy-in order reception status data, only the title portion is displayed as shown in FIG. 151. .

[1037] Next, in step S509-04, FIG.
It is determined whether or not the 57 order cancel button (10) is clicked. If the order cancel button (10) is not clicked (Step S509-04: No), Step S5
Returning to 09-03, the display of the buy-in order status reception screen is continued. If the order cancel button (10) is clicked (Step S509-04: Yes), Step S5
In 09-05, it is determined whether or not it is outside the reception time of the buy-in order cancellation entry.

[1038] If the buy-in order cancellation entry is out of the reception time (step S509-05: Yes), an error screen is displayed in step S509-06, "The purchase is not accepted because of the buy-in order cancellation reception time." In step S509-07, it is determined whether the “OK” button on the error screen is clicked. "O" on the error screen
If the “K” button is not clicked (step S5
09-07: No), the error screen display in step S509-06 is continued. When the “OK” button on the error screen is clicked (step S509-07: Ye
s), returning to step S509-03 to display a buy-in order status reception screen.

[1039] If it is not outside the reception time of the buy-in order cancellation entry (step S509-05: No), that is, if it is within the reception time of the entry, step S509-0.
At 8, it is determined whether the buy-in order is a cancelable version. If the buy-in order is not a cancelable version (step S
509-08: No), an error screen "Cannot cancel order" is displayed in step S509-12, and "O" in the error screen is displayed in step S509-13.
It is determined whether the "K" button has been clicked. If the “OK” button on the error screen has not been clicked (step S509-13: No), the error screen display in step S509-12 is continued. When the "OK" button on the error screen is clicked (step S509-13: Ye)
s), returning to step S509-03 to display a buy-in order status reception screen.

If the buy-in order is a cancelable version (step S509-08: Yes), step S5
In 09-09, "Can you cancel the following order application? (No., edition number, classification, brand name, brand code,
Order price, order quantity, self / consignment) A "buy-in order cancellation entry screen""Yes / No" is displayed. Next, in step S509-10, it is determined whether the “Yes” button on the buy-in order cancellation entry screen has been clicked. If the “Yes” button has not been clicked (Step S509-10: No), Step S501
At -11, it is determined whether the "No" button has been clicked.

[1041] If the "No" button has not been clicked (step S509-11: No), it is determined that the user has not finished the process on the screen yet, and the process proceeds to step S50.
Returning to 9-09, the display of the buy-in order cancellation entry screen is continued. If the "No" button is clicked (step S509-11: Yes), it is determined that there is no intention to cancel the buy-in order, and the process returns to step S509-03 to display the buy-in order status reception screen.

[1042] "Yes" on the buy-in order cancellation entry screen
When the button is clicked (step S509-1)
0: Yes), and in a step S509-14, it is determined whether or not it is determined by the check on the server computer 4 side that there is no mistake in the operation on the client computer 9 side.
If it is determined by the check on the server computer 4 side that there is no mistake in the operation on the client computer 9 side (step S509-14: Yes), step S5 is performed.
At 09-17, a temporary cancellation confirmation screen "temporarily canceled" is displayed. Next, it is determined in step S509-18 whether "OK" on the temporary cancellation confirmation screen has been clicked.
When "OK" is not clicked (step S50)
9-18: No), the process returns to step S509-17, and the temporary cancellation confirmation screen display is continued.

[1043] If "OK" on the temporary cancellation confirmation screen is clicked (step S509-18: Yes), the flow returns to step S509-03, and the buy-in order status reception screen is displayed. When it is not determined that there is no mistake in the operation on the client computer 9 side by the check on the server computer 4 side (step S509-14: No),
That is, if it is determined that there is an error in the operation on the client computer 9 side, an error screen such as a screen such as "cannot be accepted because the buy-in order is not accepted" is displayed in step S509-15. S
In step 509-16, it is determined whether the “OK” button on the error screen has been clicked. When the “OK” button on the error screen is not clicked (step S509-16: N
o), the error screen display in step S509-15 is continued. If the “OK” button on the error screen is clicked (step S509-16: Yes), step S5
Returning to 09-03, a buy-in order status reception screen is displayed. In the flowchart of FIG. 147, the above processing is repeated.

Next, the screen for the buy-in related business will be described. FIG. 148 shows a main screen related to a buy-in request in the business buy-in request business screen. (1) in FIG. 148 is a fail information notification button for shifting to a main screen related to fail information notification. (2) in FIG. 148 is a buy-in execution notification button for shifting to a buy-in execution notification-related main screen.

[1045] (3) in FIG. 148 is a buy-in execution confirmation notification button for shifting to a main screen related to a buy-in execution confirmation notification. (4) in FIG. 148 is a buy-in request button, which is in a selected state. The left lamp is on. (5) in FIG. 148 is a buy-in request withdrawal button for shifting to a main screen for the buy-in request withdrawal relationship. (6) of FIG. 148 is a buy-in order button for shifting to a main screen related to the buy-in order. FIG.
48 (7) is a fail management screen tab, which is in a selected state.

(8) of FIG. 148 is for acquiring the latest declarable claim brand information from the DVP server computer 4 side program, displaying the buy-in claim report screen of FIG. 152, and performing a new buy-in claim report. This is a claim report button. (9) of FIG. 148 is a charge change button. If the bill report selected in the buy-in bill acceptance status table can be changed, this button can be used to display a buy-in bill change screen and change the selected bill report.

FIG. 148 (10) is a request cancel button. If the claim report selected in the buy-in claim acceptance status table can be canceled, clicking this button displays the confirmation message screen in FIG. 149. If "Yes" is clicked on the screen in FIG. 149, the selected claim report is canceled. If "No" is clicked, the screen returns to the buy-in request acceptance status table screen.

(11) of FIG. 148 is a new display button for acquiring the latest buy-in request reception status from the program on the DVP server computer 4 side and displaying the latest buy-in request reception status table. (12) in FIG. 148 is a display order switching button for alternately switching the display in the order of reception and in the order of brand code. The display of the button title name is switched between “reception order” and “brand order” so that the current sort order can be clearly understood. The issue code order is displayed in ascending order, but only the lines of the version that can be changed are displayed collectively from the top. For example, if the current sort order is the order of reception, the title of the button is displayed as “brand name”, and if the current sort order is the order of the brand code, the title of the button is displayed as “order of reception”. .

FIG. 148 (13) is a buy-in request acceptance status table. Each item of the buy-in request reception status table will be described. “No.” is a billing number display area. "Version number" is a column for notifying the version number.
“Segment” is a display area for a process category such as “claim declaration”, “claim change”, “claim cancellation”, and the like. At this time, the “claim report” is the first claim report. The "brand name" is a display area for the brand name. The “brand code” is a display area of the brand code. “Billed quantity” is a number with a comma. Display the trading unit name after the number.

[1050] The "acceptance status" has the following contents. In other words, the “temporary receipt” is a case where the billing report is transmitted to the CSI server computer 12 and the receipt confirmation notification from the CSI server computer 12 is awaited. "Receipt"
This is a case where a bill report acceptance confirmation notice of completion of bill report acceptance is received from the CSI server computer 12. "Temporary cancellation" is a case where a request cancellation is transmitted to the CSI server computer 12 and the reception confirmation notification from the CSI server computer 12 is awaited. “Cancelled” means a case where a request for confirmation of receipt of completion of receipt of a request for billing has been received from the CSI server computer 12. This is a case where a reception error message or a “rejection” → a non-reception request report reception confirmation notice is received from the CSI server computer 12.

[1051] The "acceptance time" is the time at which the CSI server computer 12 accepted. It is in minutes. The “input time” is a time received on the DVP server computer 4 side. It is in minutes. "Department in charge" is Member 2
This is the name of the department in charge of the declaration / change / cancellation by the side.

[1052] If the display does not fit on the screen, a vertical / horizontal scroll bar is displayed. The horizontal scroll bar is automatically displayed by the browser. Requests that can be changed / cancelled are displayed in a different color. The display order of the data is
There are two types: order of reception and order of brand. The order of acceptance is grouped in descending order for each billing number, and within the same billing number, the order of the newest input time is assumed. The issue order is, in principle, in ascending order of issue codes, but is displayed from the beginning around the line of the edition that can be changed. Within the same brand, the order with the newest input time is used.

[1053] Data to be displayed is only input data of the current day (business date). The operation of selecting the request to be changed / cancelled is performed by clicking with the mouse or using the cursor keys on the personal computer keyboard. The selected billing line is highlighted and the selectable number is one. “Current date” (14) in FIG. 148 displays the current business date.

[1054] The criteria for determining a changeable / cancelable request will be described. If there is "request cancellation" whose reception status is "temporarily canceled" or "cancelled", all the reception lines with the same claim number cannot be changed / canceled. If it has never been canceled or the cancellation has resulted in a reception error, only the latest version of “Billing Change” with a status of “Accepted” can be changed / cancelled. If it has never been changed, the “claims” with the status “Received” can be changed / cancelled. If the reception status is a reception error, do not assign a version number.

An error display (message box display) when the claim report / claim change / claim cancel button is clicked will be described. CSI server computer 12
Is out of the buy-in claim report acceptance time, it is determined by the response from the program on the DVP server computer 4 side,
A message “The application is not accepted because it is outside the buy-in report acceptance time” is displayed in the message box shown in FIG.

[1056] When there is no buy-in billing target brand (when the billing report button is clicked), a message "No brand available for buy-in request" is displayed in a message box (not shown). Since the same member 2 changed / canceled the same version of the same billing number from another terminal,
If you select a version that cannot be revoked (when you click the Change Bill / Cancel button), the message "Your billing has been changed or canceled from another terminal, so you can no longer select it. Press the Refresh button. Please update the display. "
Is displayed in a message box (not shown).

[1057] If an unchangeable version is selected and the billing change button is selected, a message "cannot be billed." Is displayed in a message box (not shown). If you select a non-cancelable version and click the cancel request button, a message stating "cannot cancel request" is displayed in a message box (not shown).

At the time of activation, after execution of a bill report, after execution of a bill change, and after execution of a bill cancellation, the buy-in bill acceptance status table is updated. The “current number of displayed items” (15) in FIG.
The number of reception status data currently displayed in the buy-in request reception status table is displayed. When the number of cases is 0, the buy-in request reception status table displays only the title portion as shown in FIG.

[1059] Buttons that are not processed even if clicked are displayed as invalid. In the case of FIG. 151, three buttons of “change billing”, “cancel billing”, and “order of brand” (or “order of receiving”) are disabled. If you update the reception status table to the latest state, if you are outside the buy-in request reception time,
The buttons of “Change request” and “Cancel request” are disabled.

Next, the buy-in request report screen will be described with reference to FIG. The current date and the scheduled buy-in execution date display area (1) are automatically displayed, and the current date is the business date, and the scheduled buy-in execution date is three business days after the current day. In the issue selection combo box (2), a list of issue-indicated issue codes and issue names is made selectable. The brands to be displayed are the billable brands acquired when the claim report button is clicked. One-byte space is provided between the brand code and the brand name. If the total length of the brand code and the brand name is larger than the size of the combo box, the selected combo box is expanded and displayed as shown in FIG.
However, the configuration may be such that the brand name is displayed only halfway.

[1061] The brand list displayed in this combo box is received from the DVP server computer 4, but if there are many brands, the response is expected to deteriorate. Therefore, the number of brands received from the DVP server computer 4 is limited, and only the brands are displayed in a list as shown in FIG. Then, at the end of the list display, an item 581 “Next List” is provided, and “Next List” is displayed.
When the item 581 is clicked, the next brand list is received from the DVP server computer 4 and displayed as shown in FIG. 154 (b). FIG. 154 (a) shows a case where a limited number of brands are received from the DVP server computer 4;
(B) shows a brand selection combo box display screen when the brand is completely received from the DVP server computer 4.

[1062] The billing quantity input area (3) in Fig. 152 is an area for keying in the billing quantity. Must be an integer multiple of the trading unit of the selected symbol. The maximum billable quantity display area (4) in FIG. 152 displays the maximum billable quantity of the specified brand. When the OK button (5) in FIG. 152 is clicked, a confirmation message is displayed, stating "I will make a claim report. Are you sure?" If "Yes" is clicked on the confirmation message, the input data is confirmed, and a claim is made. If “No” is clicked on the confirmation message, the screen returns to the buy-in claim declaration screen.

[1064] After executing the billing report, a message box shown in FIG. 155 is displayed. If “Yes” is clicked in the message box in FIG. 155, the input values on the screen are cleared, and a new input screen is displayed. If "No" is clicked, the screen returns to the reception status screen. If the cancel button (6) in FIG. 152 is clicked, the input data is discarded, the claim report is terminated, and the display returns to the buy-in request main screen.

The trading unit name (7) in FIG. 152 is the name of the trading unit for each brand. Displays the name of the trading unit such as stock, 1,000 yen, unit, etc. of the selected brand. When the OK button (5) in FIG. 152 is clicked, if the next error occurs, an error message is displayed in the message box and the billing is not executed. In other words, if the brand or billing quantity has not been entered, the error message "There are required items that have not been entered."
In the following cases or if it is not an integral multiple of the trading unit, the error message "Please enter a multiple of the trading unit for the invoiced amount." If the invoiced amount exceeds the maximum value, "The invoiced amount is too large. Error message,

[1065] If the billing quantity includes characters other than single-byte numbers, "Please enter the billing quantity with single-byte numbers."
Error message is displayed, and the claim is not executed. If "Yes" is clicked in the confirmation message box in FIG. 155, if the next error occurs, an error message is displayed in the message box and the billing is not executed. In other words, the response from the program on the DVP server computer 4 side allows the SI server computer 1
If the two sides are determined to be outside the buy-in claim report acceptance time, the issue is not accepted due to the error message "The purchase is not accepted because it is outside the buy-in claim report acceptance time" and the response from the server-side program. (For example, when the same brand is continuously selected, or when the same member 2 claims the same brand from another terminal, etc.), the message "Bill-in claim has already been declared, Unable to file. ", And do not submit the claim.

Referring to FIG. 156, the buy-in request change screen will be described. The current date and the scheduled buy-in execution date display area (1) are automatically displayed. The current date is a business date, and the scheduled buy-in execution date is three business days after the current day. The charge number (2) indicates the charge number of the selected charge. The brand display area (3) displays the brand name and brand code of the selected bill. The billing quantity input area (4) is an area for keying in the billing quantity. Since the billed quantity declared last time is displayed, correct it by overwriting. Must be an integer multiple of the trading unit of the selected symbol.

The maximum billable quantity display area (5) displays the maximum billable quantity of the specified brand. OK button (6)
Is clicked, a confirmation message is displayed, stating "Change billing. Are you sure?" If "Yes" is clicked on the confirmation message, the input data is confirmed and the claim is filed. After executing the claim report, a message "Provisionally received" is displayed in the message box, and the screen returns to the main screen for the buy-in request. If "No" is clicked on the confirmation message, the screen returns to the buy-in billing change screen.

When the cancel button (7) is clicked, the input data is discarded, the billing is completed, and the display returns to the buy-in billing main screen. The trading unit name (8) is the name of the trading unit for each brand. The stock of the selected brand, 1,000 yen,
Displays the name of a trading unit such as a unit. When the OK button (6) is clicked, if there is an error, an error message is displayed in a message box, and the billing change is not executed. In other words, if you have n’t entered a symbol or billed quantity,
Displays the error message "There are required items that have not been entered." If the billed quantity is less than 0 or not an integral multiple of the trading unit, "Please enter the billing quantity in multiples of the trading unit." Error message,
If the billing quantity exceeds the maximum value, an error message "Billing quantity is too large." Is displayed. If the billing quantity contains characters other than single-byte numbers, the message "Charge Please do not change the billing message.

If "Yes" is clicked in the confirmation message box "Change billing. Are you sure?" If there is an error, an error message is displayed in the message box and billing change is not performed. In other words, the response from the server-side program causes C
If the SI server computer 12 determines that it is outside the buy-in request declaration / cancellation reception time, it displays an error message “The purchase is not accepted because it is outside the buy-in request declaration / cancellation reception time” and responds from the server-side program. If it is determined that the same member 2 has changed / cancelled the same request from another terminal and thus cannot be changed, the request cannot be changed because the request has been changed or canceled from another terminal. Display an error message and do not execute billing change.

[1070] The buy-in order business screen will be described.
FIG. 157 is a main screen related to the buy-in order. The fail information notification button (1) is a button for shifting to a main screen related to fail information notification. The buy-in execution notification button (2) is a button for shifting to a main screen related to the buy-in execution notification. Buy-in execution confirmation notification button (3) This button is used to shift to a main screen related to a buy-in execution confirmation notification. Buy-in request button (4) This button is used to shift to a main screen related to a buy-in request. Buy-in request withdrawal button (5) This button is used to shift to a main screen relating to withdrawal of a buy-in request.

[1071] The buy-in order button (6) is in a selected state. The left lamp lights up. The fail management screen tab (7) is in a selected state. The order application button (8) is a button for acquiring the latest available order brand information from the server-side program, displaying a buy-in order application screen, and performing a new buy-in order application. Order change button (9)
Is a button for displaying a buy-in order change screen if the order application selected in the buy-in order reception status table can be changed, and changing the selected order application. The order cancel button (10) displays the confirmation message in FIG. 158 if the order application selected in the buy-in order reception status table can be canceled, and clicks "Yes" if "Yes" is clicked.
Cancel the selected order application. If "No" is clicked, the screen returns to the buy-in order application acceptance status table screen.

The latest display button (11) acquires the latest buy-in order reception status from the server-side program, and displays the latest buy-in order reception status table. The display order switching button (12) is a button that can be alternately switched in the reception order and the brand code order. At this time, the titles of the buttons are changed to “reception order” and “brand name” so that the current sort order can be clearly understood. The order of the brand code is displayed in ascending order, but only the versions that can be changed are displayed together from the top. If the current sort order is the order of acceptance, the title of the button is “brand name”, and if the current sort order is the order of the brand code, the title of the button is “acceptance order”.

The items in the buy-in order reception status table (13) will be described. “No.” is an order number display area,
"Version number" is a column for notifying the version number. "Division"
Is a display area for processing categories such as "order application", "order change", and "order cancellation", and "order application" is the first order application. The “brand name” is a display area for the brand name, the “brand code” is a display area for the brand code, the “order price” is displayed in yen, and the sen is displayed in two digits after the decimal point. "Order quantity" displays the trading unit name after the number.

[1074] In the "reception status", "temporary reception" transmits an order application to the CSI server computer 12, and when waiting for a reception confirmation notification from the CSI server computer 12, "real reception" is performed by the CSI server computer 12. When the order application reception confirmation notification of the completion of the order application reception is received, the “temporary cancellation” transmits the order cancellation to the CSI server computer 12, and when the reception confirmation notification from the CSI server computer 12 is received, “canceled” Indicates that the order application has been received from the CSI server computer 12 when the order cancellation confirmation has been received. Show. “Reception time” indicates the time of reception on the CSI server computer 12 side, and is in minutes. "Input time"
The time received by the DVP server computer 4 is indicated in minutes.

[1075] "Self / consignment classification" is "self", "consignment"
Show another. “Department in charge” is the signature of the department in charge of the order application / cancellation performed by the member 2.

If the display does not fit on the screen, a vertical / horizontal scroll bar is displayed. The horizontal scroll bar is automatically displayed by the browser. Requests that can be changed / cancelled are displayed in a different color. The display order of the data is
There are two types: order of reception and order of brand.

[1077] As the "acceptance order", the order numbers are grouped in descending order, and within the same order number, the order of the input time is the newest. The “brand name” is, in principle, in the ascending order of the brand code, but is displayed from the beginning around the line of the edition that can be changed. Within the same brand, the order with the newest input time is used. The data to be displayed is only the input data of the current date (business date). The operation of selecting an order to be changed / cancelled is performed by clicking with the mouse or using the cursor keys of the personal computer keyboard. The selected order line is highlighted and the selectable number is one. The current day (1
4) displays the work date.

[1078] The criteria for determining a changeable / cancelable order are as follows. When there is "order cancellation" in which the reception status is "temporarily canceled" or "cancelled", all the reception lines with the same order number cannot be changed / cancelled. If it has never been canceled or the cancellation has resulted in a reception error, only the latest version of “Change Order” whose reception status is “Received” can be changed / cancelled. If it has never been changed, the “order application” whose reception status is “this receipt” can be changed / cancelled.

If the reception status indicates a reception error, the version number is not assigned and excluded from the judgment. The error processing when the order application / order change / order cancel button is clicked is as follows. If the CSI server computer 12 is determined to be outside the buy-in order application reception time according to a response from the server-side program, a message “The purchase is not accepted because the buy-in order application is not available” is displayed in the message box shown in FIG. indicate.

[1080] If there is no buy-in order target brand and the order application button is clicked, a message "No brand available for sell-in for buy-in" is displayed in a message box. If the same member 2 changes / cancels the same order from another terminal, and selects an order that cannot be changed / canceled (when the order change / cancel order button is clicked), "Order from another terminal" The message "Cannot be selected because it has been changed or the order has been cancelled. Please refresh the display by pressing the refresh button." If you select an unchangeable version and select the order change button, a message box saying "Orders cannot be placed" will be displayed in a message box. If you select a non-cancelable version and click the cancel order button, a message box saying "cannot cancel order" will be displayed in a message box.

At the time of activation, after executing an order application, executing an order change, and executing an order cancellation, the buy-in order reception status table is updated. The current display number (15) in FIG. 157 indicates the number of reception status data currently displayed in the buy-in order reception status table. When the number of cases is 0, the buy-in order reception status table displays only the title portion. Figure 1 shows the screen image when there is no buy-in request acceptance status data
This is the same as the screen 51. At this time, the three buttons of “order change”, “order cancellation”, and “order of brand” (or “order of reception”) are invalidated. When updating the reception status table, when the buy-in order reception time is outside, the “order application”,
Disable the "Change Order" and "Cancel Order" buttons.

FIG. 160 is a buy-in order application screen when the issue is stock, and FIG. 161 is a buy-in order application screen when the issue is convertible bonds.

FIG. 160 and FIG. 161 will be described. The current date display area (1) is automatically displayed and displays the work date. The brand selection combo box (2) displays a list of brand names and brand codes for the buy-in order application and makes them selectable. The brands to be displayed are the orderable brands acquired at the time of clicking the order application button. The display method is the same as that of the brand selection combo box of “buy-in claim report”.

[1084] The order price input area (3) is an area for key input of the order price. If the selected brand is a stock, input up to 9 digits in yen units. If the selected issue is convertible bonds, enter in yen and monetary units. Enter up to four digits for yen and up to two digits for money. The order quantity input area (4) is an area for inputting the order quantity by key. Must be an integer multiple of the trading unit of the selected symbol.

[1085] The self / consignment division selection area (5) is selected by a radio button. The initial selection value is “self”. The buy-in execution quantity display area (6) displays the order application available quantity. When the OK button (7) is clicked, a confirmation message "Apply for order. Are you sure?" Is displayed. If "Yes" is clicked on the confirmation message, the input data is confirmed and the order application is executed. If "No" is clicked on the confirmation message, the screen returns to the buy-in order application screen. After executing the order application, a message box shown in FIG. 162 is displayed.

In the message box shown in FIG. 162, "Yes"
When is clicked, the input value on the screen is cleared and a new input screen is displayed. If "No" is clicked, the screen returns to the reception status screen. Cancel button (8) in FIG. 161
When is clicked, the input data is discarded, the order application is completed, and the display returns to the main screen of the buy-in order. The trading unit name (9) is the name of the trading unit for each brand. Displays the name of the trading unit such as the stock, 1,000 yen, and unit of the selected brand.

[1087] When the OK button (7) is clicked,
In the case of the following errors, display an error message in the message box and do not execute the order application. In other words, if any of the brand, order price, or order quantity is not entered, an error message stating "There is a required item that has not been entered." If the order quantity is 0 or less, or an integral multiple of the trading unit If not, an error message "Please enter a multiple of the trading unit for the order quantity." If the order price is 0 or less, "Please enter an order price of 1 or more." If the error message, order price or order quantity contains characters other than single-byte numbers, an error message stating "Please enter the order price and order quantity in single-byte numbers." Do not execute.

[1088] When the self / consignment category is "self",
The entered "order quantity" and "buy-in execution quantity" are compared. If "buy-in execution quantity" is exceeded, a message "Order quantity is too large" is displayed. In the case of “consignment”, it is not compared with “buy-in execution quantity”.

If "Yes" in the confirmation message box shown in FIG. 162 is clicked and the following error occurs,
Display an error message in the message box and do not execute the order application. In other words, when the CSI server computer 12 determines that the buy-in order application / cancellation reception time is not within the response time from the response from the server-side program, the request is not received because the buy-in order application reception time is outside.
Error message from the server side program when the self / consignment category is “self”, and there are orders with the same brand and the same price for orders that have not been canceled (including “temporary receipt”) If the judgment is made, an error message stating that "an order cannot be made because there is already an order for the same brand and the same price" is displayed, and the order application is not executed.

[1090] Fig. 163 is a buy-in order change screen when the issue is stock, and Fig. 164 is a buy-in order change screen when the issue is convertible bonds.

FIG. 163 and FIG. 164 will be described. The current date display area (1) automatically displays the work date. The order number display area (2) displays the order number of the selected order. The brand name / brand code display area (3) displays the brand name and brand code of the selected order. The order price display area (4) displays the order price of the selected order. If the selected issue is a stock, it is displayed in yen. If the selected issue is convertible bonds, it is displayed in yen and monetary units.

[1092] The order quantity input area (5) is an area for key input of the order quantity. Since the order quantity entered last time is displayed, correct it by overwriting. Must be an integer multiple of the trading unit of the selected symbol. The self / consignment division display area (6) displays the self / consignment division of the selected order. Display "self" or "consignment". The buy-in execution quantity display area (7) displays the order application available quantity.

[1093] When the OK button (8) is clicked,
The confirmation message "Change order. Are you sure?" Is displayed. If "Yes" is clicked on the confirmation message, the input data is confirmed and the order application is executed. After executing the order application, a message "Provisionally received" is displayed in the message box, and the main screen of the buy-in order is returned. If "No" is clicked on the confirmation message, the screen returns to the buy-in order change screen.

[1094] When the cancel button (9) is clicked, the input data is discarded, the order change is completed, and the display returns to the buy-in order main screen. The trading unit name (10) is the name of the trading unit for each brand. Displays the name of the trading unit such as stock, 1,000 yen, unit, etc. of the selected brand. If the next error occurs when the OK button (8) is clicked, an error message is displayed in a message box and the order is not changed. In other words, if the order quantity is not entered, an error message "There are required items not entered." If the order quantity is 0 or less or if it is not an integral multiple of the trading unit, the "Order quantity is Please enter a multiple of trading unit. "
If the order quantity contains characters other than single-byte numbers, an error message "Please enter the order price and order quantity in single-byte numbers." Is displayed, and the order is not changed.

[1095] When the self / consignment category is "self", the inputted "order quantity" is compared with the "buy-in execution quantity".
If "buy-in execution quantity" is exceeded, a message "Order quantity is too large" is displayed. In the case of “consignment”, it is not compared with “buy-in execution quantity”.

[1096] If "Yes" in the confirmation message "Change order. Are you sure?" Is clicked, an error message is displayed in the message box and the order change is not executed in the following cases. That is, C
If the SI server computer 12 determines that the buy-in order application / cancellation has not been accepted and the response from the server-side program has made a response, an error message stating that "because the buy-in order application has not been accepted, it will not be accepted." If it is determined by the response from the server-side program that the same member 2 has changed / canceled the same order due to the same member 2 from the server-side program, the message "The order cannot be changed because the order has been changed or canceled from another terminal. Is displayed, and the order is not changed.

[1097] The buy-in request withdrawal business screen image will be described. FIG. 165 is a main screen related to the withdrawal of a buy-in request. The fail information notification button (1) is a button for shifting to a main screen related to fail information notification. The buy-in execution notification button (2) is a button for shifting to a main screen related to the buy-in execution notification. The buy-in execution confirmation notification button (3) is a button for shifting to a main screen related to the buy-in execution confirmation notification. The buy-in request button (4) is a button for shifting to a main screen related to a buy-in request. Buy-in order button (5) This button is used to shift to a main screen related to a buy-in order. The buy-in request withdrawal button (6) in FIG. 165 is in a selected state. The left lamp lights up. The fail management screen tab (7) in FIG. 165 is in a selected state.

[1098] The claim withdrawal declaration button (8) is used to obtain the latest declarable withdrawal brand information from the server-side program, display a buy-in withdrawal declaration screen, and perform a new buy-in withdrawal declaration. Button. The withdrawal change button (9) displays the buy-in withdrawal change screen if the withdrawal declaration selected in the buy-in withdrawal acceptance status table can be changed, and displays the selected withdrawal declaration. It is a button for changing. Cancel request button (10)
166 displays a confirmation message in FIG. 166 when the request for withdrawal declaration selected in the buy-in / withdrawal acceptance status table can be canceled. If “Yes” is clicked on the confirmation message in FIG. 166, the claim withdrawal declaration is canceled. "No"
When is clicked, the screen returns to the buy-in request withdrawal reception status table screen.

The latest display button (11) is a button for acquiring the latest buy-in request withdrawal reception status from the server-side program, and displaying the latest buy-in request withdrawal reception status table. The display order switching button (12) is a button for alternately switching the display in the order of reception and in the order of brand code.
By switching, the title names of the buttons are switched and displayed as “reception order” and “brand name order” so that the current sort order can be clearly understood. The issue code order is displayed in ascending order, but only the lines of the version that can be changed are displayed collectively from the top. If the current sort order is the order of reception, the title of the button is set to “brand name”. If the current sort order is the order of the brand code, the title name of the button is set to “reception order”.

[1100] Each item in the buy-in withdrawal acceptance status table (13) will be described. No. Is a withdrawal number display area. The version number is a column for notifying the version number. The category is a display area of a processing category such as "withdrawal declaration", "withdrawal change", "withdrawal cancellation" and the like. "Declaration of Withdrawal" shall be the first withdrawal of claim. The brand name is a display area for the brand name, and the brand code is a display area for the brand code. In the withdrawal quantity, the trading unit name is displayed after the number.

[1101] The reception status is displayed as follows. The “temporary receipt” display indicates a case where a request for withdrawal is transmitted to the CSI server computer 12 and the reception confirmation notification from the CSI server computer 12 is awaited. The “reception” display indicates a case where a notice of completion of receipt of a claim withdrawal report has been received from the CSI server computer 12. The “temporary cancellation” display indicates a case in which a request for cancellation is transmitted to the CSI server computer 12 and a reception confirmation notification from the CSI server computer 12 is awaited. "Cancelled" indication is C
This shows a case where a notice of confirmation of receipt of a request for withdrawal of cancellation of receipt of a request for withdrawal from the SI server computer 12 is received.
The reception error message or “rejection” indicates a case where a request for withdrawal report acceptance confirmation of unacceptability is received from the CSI server computer 12.

[1102] The reception time is the CSI server computer 12
This is the time received on the side, displayed in minutes. The input time is the time received by the DVP server computer 4 and is displayed in minutes. The department in charge is the signature of the department in charge of which the member 2 has made a claim withdrawal declaration / change / cancellation.

[1103] If the display does not fit on the screen, a vertical / horizontal scroll bar is displayed. The horizontal scroll bar is automatically displayed by the browser. Requests that can be changed / cancelled are displayed in a different color. The display order of the data is
There are two types: order of reception and order of brand. The reception order is set in descending order collectively for each number, and within the same withdrawal number, the order of the latest input time is set. In the issue order, in principle, the order of the issue code is ascending, but only the lines of the version that can be changed are collectively displayed from the top. The data to be displayed is the current date (business date)
Input data only. The operation of selecting the change / cancellation request withdrawal is performed by clicking with the mouse or using the cursor keys on the keyboard. The selected withdrawal line is highlighted and the selectable number is one.

[1104] The current date (14) indicates the work date.
The criteria for withdrawal that can be changed / cancelled are as follows. If there is a “cancellation withdrawal” whose acceptance status is “temporarily canceled” or “cancelled”, all the accepted lines with the same withdrawal number cannot be changed / canceled. If it has never been canceled or the cancellation has resulted in a reception error, only the latest version of "Change withdrawal" whose reception status is "Received" can be changed / canceled. If it has never been changed, the "withdrawal declaration" whose reception status is "this receipt" can be changed / cancelled. If the reception status is a reception error, do not assign a version number.

[1105] The message box display as error processing when the claim withdrawal report / claim withdrawal / claim withdrawal button is clicked is as follows. If the CSI server computer 12 determines from the response from the server-side program that the time is outside the buy-in request withdrawal report acceptance time, as shown in FIG. Is displayed in a message box. If there is no issue to be withdrawn and the claim withdrawal declaration button is clicked, a message saying "There is no issue with which the buy-in claim can be withdrawn." Is displayed in a message box. When the same member 2 changes / cancels the same request withdrawal from another terminal, and selects the withdrawal that cannot be changed / canceled (when the withdrawal change / cancel withdrawal button is clicked) ), A message box saying "Cannot be selected because billing was changed or canceled from another terminal. Press the refresh button to update the display." If you select a non-changeable version and select the withdrawal change button, a message stating that the request cannot be withdrawn is displayed in a message box. If you select a non-cancelable version and press the withdrawal withdrawal button, the message "Cannot cancel withdrawal." Is displayed in a message box.

At the time of startup, after execution of the bill withdrawal process, and after execution of the cancel process, the buy-in withdrawal withdrawal acceptance status table shown in FIG.

[1107] The current display number (15) in Fig. 165 indicates the number of reception status data currently displayed in the buy-in request withdrawal reception status table. If the number of cases is 0, the buy-in request withdrawal reception status table displays only the title portion. The screen image when the number of cases is 0 is the same as the screen in FIG. 151. “Changing billing withdrawal”, “Cancelling billing withdrawal”
The three buttons of “order of brand” (or “order of reception”) are invalidated. When the reception status table is updated to the latest state, the buttons of “declare withdrawal claim”, “change withdrawal of claim”, and “cancel withdrawal of claim” are invalidated when the time is outside the buy-in withdrawal reception time.

[1108] FIG. 168 is a buy-in withdrawal declaration screen when the brand is a stock. The present date and the scheduled buy-in execution date display area (1) are automatically displayed. In the issue selection combo box (2), a list of issue names and issue codes for withdrawal of the buy-in request can be displayed for selection. The brands to be displayed are the withdrawable brands acquired when the claim withdrawal declaration button is clicked. As for the combo box (2), the selection combo box can be expanded and displayed as shown in FIG.
As shown in (a) and (b), the list may be displayed only for the limited number, and the next list may be displayed by clicking the item “next list”. When the OK button (3) is clicked, a confirmation message stating "Declare the withdrawal of the request. Are you sure?" Is displayed. When "Yes" is clicked on the confirmation message, the input data is confirmed and the claim withdrawal declaration is executed. If "No" in the confirmation message is clicked, the screen returns to the buy-in request withdrawal declaration screen.

[1109] After executing the claim withdrawal declaration, a message box shown in FIG. 169 is displayed. When "Yes" is clicked in the message box in FIG. 169, the input value on the screen is cleared and a new input screen is displayed. If "No" is clicked, the screen returns to the reception status screen. If the cancel button (4) in FIG. 168 is clicked, the claim withdrawal declaration is terminated, and the main screen returns to the buy-in withdrawal withdrawal. The buy-in withdrawal target list (5) in FIG. 168 displays the withdrawal target data of the brand selected by the brand name selection combo box. In the initial state (when no brand is selected), only the title is displayed.

[1110] Each item of the buy-in claim withdrawal target list (5) will be described. The billing date indicates the date when the claim was filed. The remaining billing amount indicates the remaining buy-in amount, and the trading unit name is displayed after the number. The accumulated invoice remaining quantity indicates the accumulation of the invoice remaining quantity in the order of the oldest invoice date. Display the trading unit name after the number. If the display does not fit on the screen, display a vertical / horizontal scroll bar. The horizontal scroll bar is automatically displayed by the browser. The data is displayed in ascending order of the billing date (oldest first). The operation of selecting a request to be withdrawn is performed by clicking with a mouse or using a cursor key on a keyboard. All data older than the selected item on the billing date are selected. Selected rows are displayed in different colors.

If "Yes" in the confirmation message in FIG. 169 is clicked, an error message is displayed in the message box in the following cases, and the claim withdrawal declaration is not executed. In other words, if the CSI server computer 12 determines from the response from the server-side program that the time is outside the buy-in request withdrawal report acceptance time, an error stating that "because it is outside the buy-in request withdrawal request acceptance time, it will not be accepted." If it is determined from the message and the response from the server-side program that the same member 2 has declared the same brand as the same brand from another terminal, the following message is displayed. Is displayed, and the claim withdrawal declaration is not executed.

[1112] If the OK button (3) in FIG. 168 is clicked and the withdrawal target is not selected, an error message "Please select withdrawal request." Is displayed, and a claim withdrawal declaration is made. Do not execute. The current number of displayed items (6) indicates the number of data items currently displayed in the buy-in request withdrawal target list. When the number of cases is 0, only the title part is displayed in the buy-in request withdrawal target list.

FIG. 170 is a buy-in withdrawal change screen when the issue is convertible bonds. The current date and the scheduled buy-in execution date display area (1) are automatically displayed, and the current date and the scheduled buy-in execution date are the same date and the current business date. The withdrawal number (2) indicates the withdrawal number of the selected billing withdrawal.
The brand name and brand code display area (3) displays the brand name and brand code of the selected billing withdrawal.

[1114] When the OK button (4) is clicked, a confirmation message is displayed, stating, "Change request withdrawal. Are you sure?" When "Yes" is clicked on the confirmation message, the input data is confirmed and the claim withdrawal declaration is executed. After executing the claim withdrawal declaration, a message "Provisionally received" is displayed in a message box, and the main screen returns to the buy-in withdrawal withdrawal.

[1115] If "No" is clicked on the confirmation message "Change billing withdrawal. Are you sure?", The screen returns to the buy-in billing withdrawal change screen. When the cancel button (5) is clicked, the change in the withdrawal of the request is terminated, and the main screen for withdrawing the buy-in request is returned. The buy-in withdrawal target list (6) displays the withdrawal data of the brand of the selected withdrawal withdrawal. The contents of the buy-in request withdrawal target list (6) are the same as the buy-in request withdrawal target list (5) on the buy-in request withdrawal declaration screen in FIG.

[1116] If the "Yes" button on the confirmation message "Change billing withdrawal. Are you sure?" Is clicked, an error message is displayed in a message box in the following cases, and the billing withdrawal change is made. Do not execute. In other words, when the CSI server computer 12 determines from the response from the server-side program that the time is outside the buy-in request withdrawal report acceptance time, the error message "The request cannot be accepted because it is outside the buy-in request withdrawal report acceptance time". If it is determined by the response from the server-side program that the same member 2 has changed or withdrawn the same brand from another terminal by the same program, the following message is displayed. Therefore, the change cannot be made. "Is displayed and the billing withdrawal change is not executed.

If the OK button (4) in FIG. 170 is clicked and the withdrawal target is not selected, an error message "Please select the request to withdraw." Is displayed in a message box. Do not perform billing withdrawal changes. The current number of displayed items (7) indicates the number of data items currently displayed in the buy-in request withdrawal target list. When the number of cases is 0, only the title part is displayed in the buy-in request withdrawal target list.

[1118] Hereinafter, information transmission from the stock exchange 14 to the member 2 by the broadcast notification program 11c will be described. From the client computer 9 side of the member 2,
The connection method to the DVP server computer 4 can be set. FIG. 171 shows the broadcast notification program 11
This is a screen when the connection information tab 582-01 is selected on the initial setting screen c. The user can use a “Obtain information by static NAT method” button 582-02 on the screen of FIG.
"Acquire information by dynamic NAT method" button 582-0
By selecting any one of the three methods, it is possible to select a connection method to the server.

FIG. 172 shows the static NAT (Network)
FIG. 2 is a diagram illustrating an outline of an Address Translation method. Here, the static NAT means that the client computer 9 notifies the server computer 4 of the IP address at the time of login, the server computer 4 specifies the IP address of the new information client computer 9, and, when new information is generated, the server computer 4. 4
Is a method of notifying the client computer 9 of the information.

FIG. 173 is a diagram showing an outline of the dynamic NAT system. Here, the dynamic NAT method means that the client computer 9 notifies the server computer 4 that the IP address is not fixed at the time of login, the server computer 4 suspends the notification data, and a survival notification is received from the client computer 9. In this case, it refers to a method of notifying data. In the case of the dynamic NAT method, since information is added to the communication from the client computer 9, the client computer 9 does not need to wait for reception. Therefore, the client computer 9 side receives the IP
There is no need to fix the address and the terminal computer. A plurality of terminal computers can be operated by one address.

When the static NAT method is selected, information is notified to the designated IP address. However, when the information notification from the server computer 4 to the client computer 9 fails, the communication is changed from the static NAT method to the dynamic NAT method. As described above, in the present embodiment, since the NAT system is converted, the client computer 9 can always receive the information notification if the client computer 9 can log in to the server computer 4.

FIG. 174 is a screen displayed when the browser information tab 582-04 is selected on the initial setting screen of the broadcast notification program 11c. On this screen, the start browser can be selected. When starting the browser, the browser to be started can be selected by clicking the item 582-05 of the browser to be started. The browser information selected on this screen is read as installation information in the client computer 9, and the selected browser is started.

[1123] Broadcast notification program 1 of payment information system
The configuration of the main screen displayed by 1c will be described. FIG. 175 shows the broadcast notification program 11 of this embodiment.
It is a figure showing the main screen displayed by c. This main screen is displayed on the client computer by starting up the broadcast notification program 11c and displaying it on the DVP server computer 4.
Displayed by connecting to.

[1124] On the main screen, a distribution status panel 201,
Unconfirmed information panel 202, downloaded panel 20
3. Business message panel 204, date operation item 20
5, operation button 206, notification information telop 207,
A communication status display panel 208 is included. The distribution status panel 201, the unconfirmed information panel 202, the downloaded panel 203, and the business message panel 204 can be switched by selecting a panel on the list switching tab.

[1125] On the distribution status panel 201, all payment related information notified from the broadcast notification system of the payment information system is displayed in a list format. If the number of payment messages is too large to display all payment related information in the display area, a scroll bar is automatically displayed on the right side.
The reception time is displayed in ascending and descending order.

[1126] The distribution status panel 201 displays a confirmation status item 209, a content 210, and a reception time 21 for each information.
1, contents 212, and selection (check box) 213 items are displayed. The confirmation status item 209 displays the status of reception confirmation. The types of confirmation states are as follows. That is, "confirmed: downloading or browsing of the WWW browser 11b has been completed via the broadcast notification program 11c", "unconfirmed: no confirmation operation", and "blank: information not to be downloaded".
Is a seed.

[1127] The content 210 displays the title of the settlement information or business message information that can be distributed. The content 210 corresponds to the distributable information of the settlement information or the public information of the business message. When the item is clicked, the WWW browser 11b starts up when there is information to be referred to, and moves to the page.

[1128] At the reception time 211, information selected in the "date operation item" is displayed. That is, “reception time: the time at which the broadcast notification program 11c received the information”, “contract date: what content is associated with which contract date”, “settlement date: content where each information is associated with which settlement date” Is displayed. " In the size 212, the capacity of a downloadable file is displayed. Selection (check box) 213
Is a button for selecting a file to be downloaded. After the selection, when the download button 214 is clicked subsequently, the information in which the selected check box is enabled can be downloaded as a file.

[1129] On the unconfirmed information panel 202, among the settlement information notified from the broadcast notification system, information having no record of confirmation operation by downloading or referring to the WWW browser 11b is displayed. By performing the confirmation operation, it is deleted from the display of the same panel. Downloaded panel 20
3 shows information of the payment information notified from the broadcast notification system that the download or the confirmation operation by referring to the WWW browser 11b has been completed.

[1130] The business message panel 204 displays a business message (notification information) of the payment information notified from the broadcast notification system. The "Importance" column displays the importance of the business message, the "Content" column displays the content of the business message, the "Subtitle" column displays the subtitle of the business message, and the "Date" displays the information selected in the date operation item. A "type" column and a "reception time" column for displaying the time at which the broadcast notification program 11c received the information are provided. The date operation item 205 is a column for selecting date information to be adopted in the “date type” list on the display panel.

The operation button 206 is a button for executing each function implemented by the broadcast notification program 11c. As shown in FIG. 175, the operation buttons 206 include a download button 214 for downloading information as a file from a payment information system including a broadcast notification system,
Select All button 215 to enable all check boxes on the panel, Cancel All button 216 to disable all check boxes on the panel, Update information button to manually receive the latest information from the payment information system 217, initial setting button 218, broadcast notification program 1
An end button 219 for ending 1c is included. When the user clicks the initial setting button 218, the user I
The screen shifts to an initial setting screen including a D setting button, a download destination folder setting field, a telop setting field, and the like.

[1132] In the notification information telop 207, the latest business message (notification information) is displayed while scrolling. The communication status display panel 208 displays information notices transmitted from the payment information system, user operation results, and the like.

[1133] Next, the screen transition of the broadcast notification program 11c will be described. The user starts up the broadcast notification program 11c, connects to the payment information system, and receives the new arrival information broadcasted from the stock exchange WAN system 1. FIG. 175 is a diagram showing a screen immediately after eight pieces of new arrival information are received. FIG. 175 shows the distribution status panel 20
In FIG. 1, the unconfirmed settlement information “general settlement table (contract price)” is selected.

[1134] Next, as shown in FIG. 175, when the user clicks the download button 214 in a state where the unconfirmed settlement information "general settlement table (contract price)" is selected, the browser 11b is activated and selected. The settlement information “General settlement table (contract price)” is downloaded. When the download is completed, as shown in FIG. 176, on the distribution status panel 201, the confirmation status item 201 of the downloaded settlement information “general clearing table (contract price)” is downloaded.
Is displayed on the communication status display panel 20.
8 indicates that the download of the specified information has been completed normally.

In the state of FIG. 176, the unconfirmed information panel 20
When the tab 2 is clicked, as shown in FIG. 177, only the information that has not been downloaded or referred to in the WWW browser 11b is displayed on the unconfirmed information panel 202. In this example, among the information displayed on the screen of FIG. 176, only the “unconfirmed information”, which is the only unconfirmed information, is displayed on the unconfirmed information panel 202.

When the tab of the downloaded panel 203 is clicked in the state of FIGS. 176 and 177, the state shown in FIG.
As shown at 78, only the information obtained by downloading or referring to the WWW browser 11b is the downloaded panel 2.
03 is displayed. In this example, only the “summary settlement table (contract price)”, which is information downloaded after acquiring new arrival information, is displayed on the downloaded panel 203.

In the state shown in FIGS. 175 to 178, when the tab on the business message panel 204 is clicked,
As shown in (1), a business message (notification information) transmitted from the broadcast notification system of the payment information system is displayed. In this example, four business messages (notification information) “Target DV” acquired by acquiring new arrival information
"P notice" 1-4 are displayed on the business message panel 204.

FIG. 180 is a screen displayed by clicking the initial setting button 218 in the screens of FIGS. 175 to 179. FIG. 180 shows an initial setting: user ID panel 218-1 when “test_user01” is adopted as the user ID when the broadcast notification program 11c is started. FIG. 181 is a screen when the tab of the download panel 218-2 is selected on the initial setting screen. A setting is shown in which the download destination of the payment information is specified in advance, and the download file is automatically saved.

FIG. 182 is a screen when the tab of the telop panel 218-3 is selected on the initial setting screen. This shows a state in which default display colors, telop speeds, and the like are adopted. FIG. 183 shows the initial setting screen of the alarm panel 2
It is a screen at the time of selecting the tab of 18-4. This shows a state in which when the new arrival information is received from the broadcast notification system of the payment information system, the cancellation of the alarm by clicking the mouse is selected. FIG. 184 is a screen when the tab of the appearance panel 218-5 is selected on the initial setting screen. The state where the default look and feel is adopted is shown.

[1140] Next, the processing of the broadcast notification API 11a will be described with reference to the block diagram of FIG. 185. In the broadcast notification API 11a, the server application 583
-08 to the client application 583-07
Notify the message to. The client application 583-07 uses a part of the notified message as display data.

[1141] Notification data transmitted from the DVP server computer 4 of the stock exchange WAN system 1 to the broadcast notification API 11a of the client computer 9 includes a notification of distribution preparation, a business message, and other information. The notification data of the notification of the preparation for distribution is notification data that informs the client computer 9 from the DVP server computer 4 that the preparation for distribution of the settlement information indicated by the notification data message is ready. The notification data does not include the settlement information. To obtain the relevant payment information, download the CSV data containing the payment information.
It is necessary to make a request to the DVP server computer 4.

[1142] The notification data of the business message is DVP
Server computer 4 to client computer 9
Is the notification data for notifying the user of the settlement business. In the notification data, the subtitle of the actual notice is distributed. In order to refer to the body of the announcement, it is necessary to separately browse the "announcement" bulletin board of the stock exchange WAN system using the WWW browser 11b. As the notification data of other information, in addition to the notification data relating to the above-described operations, information indicating a result or a state regarding an authentication procedure, a download process, a network connection, or the like can be acquired using each class. is there.

FIG. 186 is a diagram showing a message notified by the broadcast notification function. When the broadcast notification API 11a is stored in the client computer 9, information is transmitted and received between the client application 583-07 on the client computer 9 side and the server application 583-08 on the DVP server computer 4 side shown in FIG. Is performed. First, the client application 583-07 performs start-up processing 583-01. Even when the activation is completed, the server application 583-08 is not connected. The client application 583-07 can be used with a plurality of IDs.
Only one application can be started on one terminal.

Next, a login process is performed to enable reception of the broadcast-distributable information. In the login process,
First, a user ID and a password are set. There are the following two methods for setting the user ID and password required for the login process. The first method of setting a user ID and a password is a method of setting user information, that is, a user ID and a password used for a login process in a login method of the connection management class.

At this time, user information is set by the login method of the connection management class. Therefore, the initialization of the user management class is performed by the API 11a itself. Second
Is a method of inputting user information on an authentication screen. According to the first method, when a user ID and a password are not set in the login method, an authentication screen as shown in FIG. 187 is displayed. On the authentication screen, input authentication information.

Next, the login processing is called. By calling the login method of the connection management class, the login process to the DVP server computer 4 is started. At this time, a screen shown in FIG. 188 is displayed on the client computer 9. Have the user enter the user ID and password. User ID entered
And the password to the server application 583-08 to authenticate the user. Outputs the message during login. The result of the login process can be confirmed by the return value of the login method. With the above processing, when the login is completed, new arrival information is automatically obtained. At this time, a screen shown in FIG. 189 is displayed on the client computer 9.

When confirming the details of the processing result, it is possible to obtain a constant indicating the state defined in the field of the user management class using the detailed code confirmation method of the user management class. In the field of the user management class, an error in the authentication information, an error occurrence, a normal end, a processing result indicating that the same user ID is being used by another server computer or the like, and the API 11a is double-started on the same server computer A constant indicating a processing result or the like indicating that there is a possibility of being present is defined.

[1148] In the broadcast notification API 11a, as in the case of the broadcast notification program 11c, when the broadcast notification API 11a is executed by one server computer, the single login method and the suppression of the double startup are performed. When the user ID and the password are set by the login method, the user ID already used by the other member 2 side server computer or the client computer 9 storing the WWW browser 11b and the broadcast notification program 11c.
When logging in using, the detailed code confirmation method returns a processing result indicating that there is a possibility of double activation, and login is not possible.

If the user tries to log in with a plurality of user IDs on the same server computer, the detailed code confirmation method returns a processing result indicating that there is a possibility of double activation, and the user cannot log in. If a user ID and a password are not set in the login method and a login is performed using a user ID that has already been used, a warning screen as shown in FIG. 190A is displayed and login cannot be performed. Further, if an attempt is made to log in using a plurality of user IDs on the same server computer, FIG.
A warning screen such as 0 (B) is displayed, and the user cannot log in.

[1150] Client application 583-0
7 notifies the server application 583-08 of the input user ID and password, and authenticates the user. Outputs the message during login. When user authentication is completed, the latest information is automatically obtained. At this time,
The screen of FIG. 189 is displayed on the screen of the client computer 9. When the latest information is obtained, display the main screen.

[1151] Client application 583-0
No. 7 performs the latest information acquisition processing 583-02 at the time of login. If information is updated during operation, the information is updated in cooperation with the server program. This function complements the countermeasures and functions for occurrence of abnormalities. The operation is as follows. First, when the user clicks the latest acquisition button on the main screen, the client application 583-07
Get the latest information dynamically. FIG. 191 is a diagram illustrating information updating. The main screen becomes inoperable, and displays that the latest information is being acquired. Update the information when reception is completed. As shown in the communication status display panel 208 in FIG.
A message indicating that the acquisition of new information has been completed is output,
Displayed on the screen. If an alarm is set by default, an audible alarm sounds.

In the case of the broadcast notification function, all operations can be confirmed in real time by operations from notification of information to reception confirmation to the user. It is possible to monitor the status, such as whether the user is connected or not and whether there is a disconnection trouble during use. "Can the user be notified in real time?" FIG. 192
FIG. 3 is a block diagram showing a flow of connection monitoring.

The information notification processing 583-03 will be described. The client application 583-07 is started, and when the login is completed, the server application 5
It becomes a state where information notification from 83-08 is possible. A change in a case where information is notified from the server application 583-08 will be described. If there is no information on the reception state, a screen state where no message is displayed is displayed as shown in FIG. 193. When information is notified from the server computer, an item is added in red at the top line of the screen, and as shown in FIG. If an alarm is set by default, an audible alarm sounds.

[1154] The information download processing 583-04 will be described. The download operation can be performed from any of the distribution status panel 201, the unconfirmed information panel 202, and the downloaded panel 203. In the present embodiment, the case where the user selects the unconfirmed information panel 202 will be described as an example. The operation procedure is as follows. First,
The user selects the unconfirmed information panel 202 to download, as shown in FIG. Next, the user checks the selection (check box) 213 as shown in FIG. 194 and selects the item to be downloaded. When an item is selected, the download button 214 in FIG. 177 becomes valid. When the all-selection button 215 is clicked, all items for which the confirmation status item column 209 is “unconfirmed” are in a selected state.

[1155] Then, the download button 2 in FIG.
Click 14. The main screen becomes inoperable and the file selection screen is displayed. Check the file storage location. When the button is selected, a file dialog shown in FIG. 195 is displayed. If the “Store in the same folder” field in FIG. 195 is checked, the subsequent inquiry processing is not performed even for a plurality of files, and the file dialog of FIG. 196 is displayed thereafter. When it is necessary to specify the storage folder, the storage folder is specified in the file dialog of FIG. 197. When the file designation is completed, the file dialog shown in FIG. 195 is displayed again, and the download button is instructed by selecting the OK button. Thus, a screen indicating that downloading is being performed is displayed as shown in FIG. 198.

[1156] When the download is completed, a completion message is output to the log, and the communication status display panel 2 shown in FIG. 176 is displayed.
As in 08, a download completion message is displayed on the top line of the screen. When a plurality of files are designated for download, confirmation of the file storage destination, designation of the storage destination folder, and processing of the download instruction by selecting the OK button are repeated.

When browsing the notified information, an Internet browser activation process 583-05 is performed by clicking the content of the displayed list, and
Browse information with a browser. When each process ends, the client application 583-07 notifies the server application 583-08 and logs out. In the logout process, first, the logout process is called. By calling the logout method of the connection management class, the DVP server computer 4
Logout processing is started for. The result of the logout process can be confirmed by the return value of the logout method.

When confirming the details of the logout processing result, it is possible to verify a constant indicating a state defined in the field of the user management class by using the detailed code confirmation method of the user management class. In the field of the user management class, constants indicating the occurrence of abnormality, normal termination, and the like are defined. After the logout processing is completed, the client application termination processing 58-3-0
Perform Step 6.

FIG. 199 to FIG. 201 show a list of clearing / settlement information transmitted and received in this embodiment. In this list, the information transmitted from the stock exchange 14 to the member 2 is shown in the column of the inquiry screen in FIGS. 199 to 201, and the column of the entry screen in FIG. The screen of the entry information transmitted to the side is shown.

[1160] A description will be given of a method of acquiring notification data using the broadcast notification API 11a on the client computer 9 side. The method of acquiring the deliverable information and the business message is as follows. The deliverable information and the business message are collectively managed by a thread of the storage management class. Each time it is transmitted in real time from the DVP server computer 4,
The thread receives the notification data. The notification data received by the thread is transmitted via the connection interface via the reception method implemented in the main class or the change method.
NotifyDataPerformed.

[1161] The client computer 9 sends the broadcast notification A
The notification data message received by the PI 11a can be operated using the following classes. The notification data message is managed by a notification data management class. To obtain detailed information recorded in each notification data, use the method of the notification data management class.

The detailed information that can be obtained by using the method of the notification data management class includes notification of the content of the notification information (data recording content), creation date (settlement information creation date), and reception date and time (notification data reception date and time) , Server reception time (notification data reception time at DVP server computer 4), cycle number (payment information cycle number), URL information (payment information storage destination URL), information type code (payment information information type code), Notification data type (data type of notification data), secure type (secure type of notification data), country code (country code of payment information), stock exchange code (exchange code of payment information), member code (payment Information target member code), download information (whether or not download processing is possible), download completion (whether or not download is complete) Unload request (whether download request), a download result (result of the download process).

If the creation date, the cycle number, and the information type code match among these detailed information, they can be regarded as the same information. In the actual reception of the notification data, the same notification data may be transmitted a plurality of times. In that case, the notification data whose reception date is new is treated as the latest data. When the data stored in the CSV file is updated in the settlement information with the same information type code, a different cycle number is adopted as the cycle number. If notification data with a different cycle number is received, addNotic of the connection interface
The eDataPerformed method is called. In addition, CSV files corresponding to the cycle numbers are individually created.

[1164] The notification data based on the DVP settlement system is D
It is managed by the VP settlement data management class. To obtain detailed information recorded in individual notification data, use DVP
Use the method of payment data management class. The detailed information that can be obtained by using the method of the DVP payment data management class is as follows.

The detailed information that can be obtained by using the method of the DVP settlement data management class includes a file name (file name of distribution information), a file size (file size of distribution information), and a file type (file type of distribution information). , Member code (member code related to the settlement information), contract date (the contract date of the settlement information), and settlement date (the settlement date of the settlement information).

[1166] The business message (notification) relating to the settlement business is managed by the business message management class. To obtain detailed information recorded in each notification data, use the method of business message management class.
The detailed information that can be obtained using the method of the business message management class is as follows.

The detailed information that can be acquired by using the method of the business message management class is the subtitle (business message title) and the importance (business message importance).

A method for acquiring information other than the deliverable information and the business message is as follows. That is, when the method of the connection interface is used, the progress information at the time of downloading the CSV file and the stock exchange WAN
Information about disconnection from the system 1 can be obtained. By implementing each of the above methods in the main class, information corresponding to each event can be obtained.

By using the method of the user management class, it is possible to obtain a detailed result of an authentication procedure with the stock exchange WAN system 1 and a login state.

[1170]

As described above, according to the present invention, the server computer distributes the distributable information indicating that the public information including at least one of the business message related to the operation of the stock exchange and the settlement information can be distributed. Since it is equipped with a distributable information distributing means, the amount of information to be transmitted is smaller than in the case where each public information itself is transmitted to a client computer, and the member side can be quickly notified of the existence of the public information. It becomes possible. In addition, since the amount of information to be transmitted is small, it is possible to reduce the capacity of a computer, a transmitting unit, and the like to be used, thereby reducing the scale and cost of the system. as a result,
A network system that can be easily introduced by both stock exchanges and members can be provided.

[1171] The server computer transmits to the client computer distributable information indicating that public information including at least one of a business message relating to the operation of the stock exchange and payment information has been made distributable. By looking at the information, you can select only the necessary information and download or browse it.
It will not be stored on the client computer.

[1172] Also, the server computer may provide a setup completion notification information indicating that the data setup completion of the payment information has been notified to the client computer, and a delivery notification indicating that the deliverable information has been notified to the client computer. A status notification that accumulates status notification information that includes information that has been notified, that the payment information has been downloaded on the client computer side, and that the payment information has been viewed on the client computer. Since the information storage means is provided, the client computer side can check the data setup completion notified information, the distributable notification information, the downloaded information, and the browsed information stored in the status notification information storage means. Deliverable if information has arrived It is possible to know the contents of the information and public information has been confirmed, it is possible to centralized management of each member of the information confirmation situation. In addition, the status notification information can be stored by assigning the ID of each member in charge of the member who browsed, downloaded, and viewed the public information to the deliverable notification information, downloaded information, and browsed information. By checking the information stored in the means, it is possible for the member side to know which business person has viewed the information, etc., and it is also possible to manage the information confirmation status by the business person in each member .

[1174] The server computer generates the information indicating that distribution is possible, based on the distribution completion information reception completion signal automatically transmitted from the client computer based on the reception of the distribution information, and generates the downloaded information. Is generated based on a download completion signal automatically transmitted from the client computer based on download execution, and the browsed information is generated based on a browse execution signal automatically transmitted from the client computer based on browse execution. The status notification information is automatically stored in the server computer without any special processing on the client computer. For this reason, each business person in charge of the client computer does not need to perform any special operation for status notification, and only needs to activate a program for transmitting and receiving distributable information or public information. The procedure is simplified. Also,
Since the status notification is performed automatically, it is possible to prevent a situation notification from being lost due to a person forgetting to operate.
Further, since the status notification is automatically performed, when the status notification is not performed, it is possible to predict that a failure has occurred.

[1174] Further, the processing using the status notification information is as follows.
Since the other server computer is configured to determine whether or not the status notification information has been received after a lapse of a predetermined time after receiving the data setup completion information, the exchange between the server computer and the client computer is performed. You can tell if there was a problem only for the part.

In other words, despite the fact that another server computer has received the data setup completion notification indicating that the setup of the public information has been normally completed, a predetermined time has elapsed, and none of the status notification information has been received. If not, the public information setup itself is fine,
Since it is possible to predict that transmission / reception between the server computer and the client computer is abnormal, it is possible to know whether or not there is a problem only in the part of the exchange between the server computer and the client computer.

[1176] In addition, although another server computer receives a data setup completion notice indicating that the setup of the public information has been normally completed, a predetermined time has passed, and any of the status notification information has been received. Otherwise, the server is configured to stop sending information from the server computer to the client computer, so if it is assumed that the communication between the server computer and the client computer is faulty, By stopping transmission, it is possible to reduce the burden of information processing on the server computer side. In addition, it is possible to construct a more complete and accurate monitoring system of the communication state in combination with other means for monitoring the communication state between the server computer and the client computer.

[Brief description of the drawings]

FIG. 1 is an explanatory diagram showing the background and purpose of introducing DVP settlement.

FIG. 2 is an explanatory diagram showing a conventional transfer process related to securities settlement.

FIG. 3 is an explanatory diagram showing a transfer process in DVP settlement relating to securities settlement.

FIG. 4 is an explanatory diagram showing an example of a system configuration image of the present invention.

FIG. 5 is an explanatory diagram showing an example of an outline of a settlement business processing flow of the present invention.

FIG. 6 is an explanatory diagram showing an outline of a stock exchange WAN system according to an embodiment of the present invention.

FIG. 7 is an explanatory diagram showing an example of a scheme image of DVP settlement according to the embodiment of the present invention.

FIG. 8 is an explanatory diagram showing an example of a scheme image of DVP settlement according to the embodiment of the present invention.

FIG. 9 is an explanatory diagram showing an example of a scheme image of DVP settlement according to the embodiment of the present invention.

FIG. 10 is an explanatory diagram showing the comparison between the transfer of the price difference and the conventional method according to the embodiment of the present invention.

FIG. 11 is an explanatory diagram showing the comparison between the transfer of the price difference and the conventional method according to the embodiment of the present invention.

FIG. 12 is an explanatory diagram showing a comparison between a receiving member ranking by brand and a conventional assignment designation system according to the embodiment of the present invention.

FIG. 13 is an explanatory diagram showing a relationship between an unexecuted debt and an account transfer.

FIG. 14 is an explanatory diagram showing a relationship between an unexecuted debt and an account transfer.

FIG. 15 is an explanatory diagram showing the entire system according to the embodiment of the present invention.

FIG. 16 is an explanatory diagram showing a hardware configuration of a server computer according to the embodiment of the present invention.

FIG. 17 is an explanatory diagram showing the relationship between the computers constituting the system according to the embodiment of the present invention.

FIG. 18 is an explanatory diagram showing a relationship between computers constituting the system according to the embodiment of the present invention.

FIG. 19 is an explanatory diagram showing an entry processing business data cooperation image according to the embodiment of the present invention.

FIG. 20 is an explanatory diagram showing an entry processing user operation according to the embodiment of the present invention.

FIG. 21 is a flowchart showing a flow of an entry process according to the embodiment of the present invention.

FIG. 22 is an explanatory diagram showing restrictions on a reference date and the like according to the embodiment of the present invention.

FIG. 23 is an explanatory diagram showing restrictions on delisting according to the embodiment of the present invention.

FIG. 24 is an explanatory diagram showing restrictions on suspension of trading during a period according to the embodiment of the present invention.

FIG. 25 is an explanatory diagram showing securities settlement related to execution of a buy-in according to the embodiment of the present invention.

FIG. 26 is an explanatory diagram showing fund settlement related to execution of a buy-in according to the embodiment of the present invention.

FIG. 27 is an explanatory diagram showing fund settlement related to execution of a buy-in according to the embodiment of the present invention.

FIG. 28 is an explanatory diagram showing a method of determining a receiving class member ranking by brand according to the embodiment of the present invention.

FIG. 29 is an explanatory diagram showing a security deposit and a margin deposit / return operation (image) on the previous day.

FIG. 30 is an explanatory diagram showing an example of securities settlement according to the embodiment of the present invention.

FIG. 31 is an explanatory diagram showing an example of fund settlement according to the embodiment of the present invention.

FIG. 32 is an explanatory diagram showing an example of securities settlement according to the embodiment of the present invention.

FIG. 33 is an explanatory diagram showing an example of fund settlement according to the embodiment of the present invention.

FIG. 34 is an explanatory diagram showing a business processing time table relating to DVP settlement.

FIG. 35 is an explanatory diagram showing a business processing time table relating to DVP settlement.

FIG. 36 is an explanatory diagram showing a business processing time table relating to DVP settlement.

FIG. 37 is an explanatory diagram showing a business processing time table relating to DVP settlement.

FIG. 38 is an explanatory diagram showing a business processing time table relating to DVP settlement.

FIG. 39 is a daily work / data flowchart according to the embodiment of the present invention.

FIG. 40 is an explanatory diagram showing an outline of a business / data flow according to the embodiment of the present invention.

FIG. 41 is an explanatory diagram showing an outline of a business / data flow according to an embodiment of the present invention.

FIG. 42 is an explanatory diagram showing an outline of a business / data flow according to the embodiment of the present invention.

FIG. 43 is an explanatory diagram showing a flow of entry processing and the validity of application contents according to the embodiment of the present invention.

FIG. 44 is an explanatory diagram showing a flow of entry processing and the validity of application contents according to the embodiment of the present invention.

FIG. 45 is an explanatory diagram showing the flow of entry processing and the validity of application contents according to the embodiment of the present invention.

FIG. 46 is an explanatory diagram showing a flow of entry processing and the validity of application contents according to the embodiment of the present invention.

FIG. 47 is a processing flow block diagram by a broadcast notification API according to the embodiment of the present invention.

FIG. 48 is a functional flow block diagram of a broadcast notification program according to the embodiment of the present invention.

FIG. 49 is an explanatory diagram showing components (roles of components) provided by the broadcast notification API according to the embodiment of the present invention.

FIG. 50 is an explanatory diagram showing components (an example of a data processing procedure) provided by the broadcast notification API according to the embodiment of the present invention.

FIG. 51 is an explanatory diagram showing a process of connecting to a stock exchange WAN system using a broadcast notification API according to an embodiment of the present invention.

FIG. 52 is an explanatory diagram showing a data download process using the broadcast notification API according to the embodiment of the present invention.

FIG. 53 is an explanatory diagram showing an outline of processing of a notification task function according to the embodiment of the present invention;

FIG. 54 is a flowchart showing a process performed by a notification function (immediate notification) of the DVP server computer according to the embodiment of the present invention.

FIG. 55 is a flowchart showing a process performed by a notification function (time notification) of the DVP server computer according to the embodiment of the present invention.

FIG. 56 is a diagram showing a message format (status notification message) according to the embodiment of the present invention.

FIG. 57 is a flowchart showing processing performed by a status notification function (acceptance & immediate transmission) of the DVP server computer according to the embodiment of the present invention.

FIG. 58 is a flowchart showing a process performed by a status notification function (periodic transmission) of the DVP server computer according to the embodiment of the present invention.

FIG. 59 is an explanatory diagram showing a request to transmit notification information to a member according to the embodiment of the present invention.

FIG. 60 is an explanatory diagram showing reception of a member-side processing status according to the embodiment of the present invention.

FIG. 61 is an explanatory diagram showing a business message notification request reception according to the embodiment of the present invention.

FIG. 62 is an explanatory diagram showing reception of a transmission request for a data setup completion notification of payment information according to the embodiment of the present invention.

FIG. 63 is an explanatory diagram showing reception of a transmission request for operation control information according to the embodiment of the present invention.

FIG. 64 is an explanatory diagram showing a transmission request for status notification information according to the embodiment of the present invention.

FIG. 65 is an explanatory diagram showing the operation log collection of the notification function according to the embodiment of the present invention.

FIG. 66 is an explanatory diagram showing a buy-in request in the entry processing flow according to the embodiment of the present invention.

FIG. 67 is an explanatory diagram showing a buy-in request in the entry processing flow according to the embodiment of the present invention.

FIG. 68 is an explanatory diagram showing a buy-in request in the entry processing flow according to the embodiment of the present invention.

FIG. 69 is an explanatory diagram showing a buy-in order according to the embodiment of the present invention.

FIG. 70 is an explanatory diagram showing a buy-in order according to the embodiment of the present invention.

FIG. 71 is an explanatory diagram showing a buy-in order according to the embodiment of the present invention.

FIG. 72 is an explanatory diagram showing withdrawal of a buy-in request according to the embodiment of the present invention.

FIG. 73 is an explanatory diagram showing withdrawal of a buy-in request according to the embodiment of the present invention.

FIG. 74 is an explanatory diagram showing withdrawal of a buy-in request according to the embodiment of the present invention.

FIG. 75 is an explanatory diagram showing each buy-in reception status check according to the embodiment of the present invention.

FIG. 76 is an explanatory diagram showing each buy-in reception status check according to the embodiment of the present invention.

FIG. 77 is a configuration diagram of a DVP server computer according to an embodiment of the present invention.

FIG. 78 is an explanatory diagram showing a flow of a normal business according to the embodiment of the present invention.

FIG. 79 is an explanatory diagram showing a flow of an abnormal business according to the embodiment of the present invention.

FIG. 80 is an explanatory diagram showing a range of CSI server computer cooperation according to the embodiment of the present invention.

FIG. 81 is a block diagram showing processing of status notification information.

FIG. 82 is an explanatory diagram showing a form data storage method according to the embodiment of the present invention.

FIG. 83 is an explanatory diagram showing a method of storing master data and entry data according to an embodiment of the present invention.

FIG. 84 is a CSV management information table according to the embodiment of the present invention.

FIG. 85 is a flowchart of a process of transmitting deliverable information to a member according to the embodiment of the present invention.

FIG. 86 is an explanatory diagram showing a cooperative system between a DVP server computer and a member client computer according to an embodiment of the present invention.

FIG. 87 is an explanatory diagram showing an outline of functions involved in digitizing payment information according to the embodiment of the present invention.

FIG. 88 is an explanatory diagram showing a relationship between a WWW browser and a broadcast notification program (API) according to the embodiment of the present invention.

FIG. 89 is an explanatory diagram showing information classification (conventional WWW screen concept) on a WWW screen according to an embodiment of the present invention.

FIG. 90 is an explanatory diagram showing information classification (configuration of a page switching menu) on the WWW screen according to the embodiment of the present invention.

FIG. 91 is an explanatory diagram showing information classification (configuration of an information screen page) on a WWW screen according to an embodiment of the present invention.

FIG. 92 is an explanatory diagram showing information classification (configuration of an information screen page) on a WWW screen according to an embodiment of the present invention.

FIG. 93 is an explanatory diagram showing information classification (configuration of an information screen page) on a WWW screen according to an embodiment of the present invention.

FIG. 94 is an explanatory diagram showing information classification (configuration of an information screen page) on a WWW screen according to an embodiment of the present invention.

FIG. 95 is an explanatory diagram showing information classification (configuration of an information screen page) on a WWW screen according to the embodiment of the present invention.

FIG. 96 is an explanatory diagram showing a top screen of the payment information system according to the embodiment of the present invention.

FIG. 97 is an explanatory diagram showing a login / logout operation (using a single login method) according to the embodiment of the present invention.

FIG. 98 is a flowchart in the case of normal login according to the embodiment of the present invention.

FIG. 99 is a flowchart in the case of normal logout according to the embodiment of the present invention.

FIG. 100 is an explanatory diagram showing a concept of user management in computerization accompanying the DVP settlement system according to the embodiment of the present invention.

FIG. 101 is an explanatory diagram showing management of user information according to the embodiment of the present invention.

FIG. 102 is an explanatory diagram showing setting of an access right in the settlement information system according to the embodiment of the present invention.

FIG. 103 is an explanatory diagram showing a participant site group editing screen according to the embodiment of the present invention.

FIG. 104 is an explanatory diagram showing a security handling person setting screen according to the embodiment of the present invention.

FIG. 105 is an explanatory diagram showing a securities trading clerk setting screen according to the embodiment of the present invention.

FIG. 106 is an explanatory diagram showing a home tab screen according to the embodiment of the present invention.

FIG. 107 is an explanatory diagram showing a form access right management screen according to the embodiment of the present invention.

FIG. 108 is an explanatory diagram showing a form access right management screen according to the embodiment of the present invention.

FIG. 109 is an explanatory diagram showing a form user access right management screen according to the embodiment of the present invention.

FIG. 110 is an explanatory diagram showing a form user access right management screen according to the embodiment of the present invention.

FIG. 111 is an explanatory diagram showing a form access right management screen according to the embodiment of the present invention.

FIG. 112 is an explanatory diagram showing a form access right management screen according to the embodiment of the present invention.

FIG. 113 is an explanatory diagram showing a business message screen (notification) according to the embodiment of the present invention.

FIG. 114 is an explanatory diagram showing a collation operation tab screen according to the embodiment of the present invention.

FIG. 115 is an explanatory diagram showing a domestic stock trading statement list screen according to the embodiment of the present invention.

FIG. 116 is an explanatory diagram showing a domestic stock trading statement list screen according to the embodiment of the present invention.

Fig. 117 is an explanatory diagram showing a domestic stock trading schedule screen according to the embodiment of the present invention.

FIG. 118 is an explanatory diagram showing a CSV file storage destination designation screen according to the embodiment of the present invention.

FIG. 119 is an explanatory diagram showing a search operation on the WWW screen according to the embodiment of the present invention.

FIG. 120 is an explanatory diagram showing a search operation on the WWW screen according to the embodiment of the present invention.

FIG. 121 is an explanatory diagram showing a search operation on the WWW screen according to the embodiment of the present invention.

FIG. 122 is an explanatory diagram showing a search operation on the WWW screen according to the embodiment of the present invention.

FIG. 123 is an explanatory diagram showing a search operation on the WWW screen according to the embodiment of the present invention.

FIG. 124 is an explanatory diagram showing a search operation on the WWW screen according to the embodiment of the present invention.

FIG. 125 is an explanatory diagram showing a search operation on the WWW screen according to the embodiment of the present invention.

FIG. 126 is an explanatory diagram showing handling of a reception operation in an entry according to the embodiment of the present invention.

FIG. 127 is an explanatory diagram showing status management in an entry according to the embodiment of the present invention.

FIG. 128 is an explanatory diagram showing a change / cancel procedure (relationship between reception status and version number management) in an entry according to the embodiment of the present invention.

Fig. 129 is an explanatory diagram showing a unit such as a charge in an entry according to the embodiment of the present invention.

FIG. 130 is an explanatory diagram showing a unit such as a charge in an entry according to the embodiment of the present invention.

FIG. 131 is a screen transition diagram of a home according to the embodiment of the present invention.

FIG. 132 is a screen transition diagram of a collation operation according to the embodiment of the present invention.

FIG. 133 is a screen transition diagram of a settlement business according to the embodiment of the present invention.

FIG. 134 is a screen transition diagram of security management according to the embodiment of the present invention.

FIG. 135 is a screen transition diagram for fail management according to the embodiment of the present invention.

Fig. 136 is a screen transition diagram for information introduction according to the embodiment of the present invention.

Fig. 137 is a transition diagram of a help screen according to the embodiment of the present invention.

FIG. 138 is a screen transition diagram (after selection of a fail management tab) according to the embodiment of the present invention.

FIG. 139 is a flowchart showing the flow of an entry process according to the embodiment of the present invention.

FIG. 140 is a flowchart showing a flow of an entry process according to the embodiment of the present invention.

FIG. 141 is a flowchart showing a flow of entry processing according to the embodiment of the present invention.

FIG. 142 is a flowchart showing a flow of entry processing according to the embodiment of the present invention.

FIG. 143 is a flowchart showing the flow of an entry process according to the embodiment of the present invention.

FIG. 144 is a flowchart showing a flow of entry processing according to the embodiment of the present invention.

FIG. 145 is a flowchart showing a flow of an entry process according to the embodiment of the present invention.

FIG. 146 is a flowchart showing a flow of an entry process according to the embodiment of the present invention.

FIG. 147 is a flowchart showing a flow of processing of an entry according to the embodiment of the present invention.

FIG. 148 is a main screen for a buy-in request according to the embodiment of the present invention.

FIG. 149 is a buy-in request declaration cancellation confirmation message display screen according to the embodiment of the present invention.

FIG. 150 is a message box display screen in a case where a buy-in request cannot be canceled according to the embodiment of the present invention.

FIG. 151 is a screen when there is no buy-in request acceptance status data according to the embodiment of the present invention.

FIG. 152 is a buy-in request report screen according to the embodiment of the present invention.

FIG. 153 is a brand selection combo box display screen according to the embodiment of the present invention.

FIG. 154 is a brand selection combo box display screen according to the embodiment of the present invention.

FIG. 155 is a message box display screen after execution of a buy-in claim report according to the embodiment of the present invention.

FIG. 156 is a buy-in request change screen according to the embodiment of the present invention.

FIG. 157 is a main screen showing a buy-in order related to the embodiment of the present invention.

FIG. 158 is a confirmation message display screen for canceling a buy-in order application according to the embodiment of the present invention.

FIG. 159 is a message box display screen when a buy-in order cannot be canceled according to the embodiment of the present invention.

FIG. 160 is a buy-in order application screen (when the brand is a stock) according to the embodiment of the present invention.

FIG. 161 is a buy-in order application screen (when the issue is convertible bonds) according to the embodiment of the present invention.

FIG. 162 is a confirmation message display screen for a buy-in order application according to the embodiment of the present invention.

FIG. 163 is a buy-in order change screen (when the stock is a stock) according to the embodiment of the present invention.

FIG. 164 is a buy-in order change screen (when the issue is convertible bonds) according to the embodiment of the present invention.

FIG. 165 is a main screen showing a buy-in request withdrawal relationship according to the embodiment of the present invention.

FIG. 166 is a confirmation message display screen for a buy-in request withdrawal declaration according to the embodiment of the present invention.

FIG. 167 is a message box display screen according to the embodiment of the present invention in a case where withdrawal of a buy-in request cannot be canceled.

FIG. 168 is a buy-in request withdrawal declaration screen (when the brand is a stock) according to the embodiment of the present invention.

FIG. 169 is a message box display screen after execution of a buy-in withdrawal declaration according to the embodiment of the present invention.

FIG. 170 is a buy-in request withdrawal change screen (when the issue is convertible bonds) according to the embodiment of the present invention.

FIG. 171 is an explanatory diagram showing selection of a connection method to a DVP server computer according to an embodiment of the present invention.

FIG. 172 is an explanatory diagram showing a static NAT method according to the embodiment of the present invention.

FIG. 173 is an explanatory diagram showing a dynamic NAT scheme according to the embodiment of the present invention.

FIG. 174 is a startup browser selection screen according to the embodiment of the present invention.

FIG. 175 is an explanatory diagram showing a display example of a distribution status panel of a broadcast notification program according to an embodiment of the present invention.

FIG. 176 is an explanatory diagram showing a display example of a distribution status panel of the broadcast notification program according to the embodiment of the present invention.

FIG. 177 is an explanatory diagram showing a display example of an unconfirmed information panel of the broadcast notification program according to the embodiment of the present invention.

FIG. 178 is an explanatory diagram showing a display example of a downloaded panel of the broadcast notification program according to the embodiment of the present invention.

FIG. 179 is an explanatory diagram showing a display example of a business message panel of the broadcast notification program according to the embodiment of the present invention.

FIG. 180 is an explanatory diagram showing a display example of the user ID initial setting of the broadcast notification program according to the embodiment of the present invention.

FIG. 181 is an explanatory diagram showing a display example of download initial setting of a broadcast notification program according to an embodiment of the present invention.

FIG. 182 is an explanatory diagram showing a display example of telop initial setting of the broadcast notification program according to the embodiment of the present invention.

FIG. 183 is an explanatory diagram showing a display example of alarm initial setting of the broadcast notification program.

FIG. 184 is an explanatory diagram showing a display example of appearance initial settings of the broadcast notification program according to the embodiment of the present invention.

FIG. 185 is an explanatory diagram showing a series of flows when a user uses the broadcast notification function according to the embodiment of the present invention.

FIG. 186 is an explanatory diagram showing a relationship between a server and a client and an example of a message in the broadcast notification function according to the embodiment of the present invention.

FIG. 187 is a login screen of the client application according to the embodiment of the present invention.

FIG. 188 is a message output screen during login according to the embodiment of the present invention.

FIG. 189 is a screen showing that the latest information is being acquired according to the embodiment of the present invention.

FIG. 190 is an explanatory diagram showing a warning screen for a login according to the embodiment of the present invention.

FIG. 191 is a screen showing that the latest information is being acquired according to the embodiment of the present invention.

FIG. 192 is a diagram showing a connection monitoring status according to the embodiment of the present invention.

Fig. 193 is a screen when there is no information on the reception state according to the embodiment of the present invention.

FIG. 194 is a screen when an item to be downloaded is selected according to the embodiment of the present invention.

FIG. 195 is a file dialogue display screen according to the embodiment of the present invention.

FIG. 196 is a file dialogue display screen according to the embodiment of the present invention.

FIG. 197 is a storage destination folder designation screen according to the embodiment of the present invention.

FIG. 198 is a screen showing download in progress according to the embodiment of the present invention.

FIG. 199 is an explanatory diagram showing a clearing / settlement information list according to the embodiment of the present invention.

FIG. 200 is an explanatory diagram showing a settlement / payment information list according to the embodiment of the present invention.

FIG. 201 is an explanatory diagram showing a settlement / payment information list according to the embodiment of the present invention.

[Explanation of symbols]

1 Stock Exchange WAN System 2 Member 3 DVP Payment System 4 DVP Server Computer 5 WWW Server Computer 6 Payment Database 7 Download Database 8 Content Database 9 Client Computer 10 Payment Information Data File 11a Broadcast Notification API 11b WWW Browser 11c Broadcast Notification Program Reference Signs List 12 CSI server computer 13 Settlement information file 14 Stock exchange 15 Storage transfer agency 16 Fund settlement bank 21 CPU 22 RAM 23 ROM 24 HDD 25 Storage medium device 26 Keyboard 27 Mouse 28 Display device 29 Printer 30 Communication device 32 Content generation program 35 WWW Browser 42 Company server computer 43 Payment information database 44 Company business application 5 terminal computer 72 connection interface class 73 main class 74 connection management class 75 accumulated data management class 76 message management class 77 log database 77a debug log file 77b business log table 78 environment information management class 98 reception database 161 notification information display 162 notification information confirmation 163 Information communication client 164 Information communication function 165 New information (ID unit) 166 Information communication server 167 Notification function (immediate notification) 168 Notification function (time notification) 169 Status notification function (acceptance & immediate transmission) 170 Status notification table 171 Notification function (periodic transmission) 172 Distribution information management database 172a Distribution information table (member unit) 172b Distribution information detailed table 173 Data setup related tasks Application 174 Control function 175 Notification function (Cooperation command) 176 Business message table 177 Control function 178 DVP operator terminal 180 Notification registration function 181 MQ cooperation API 182 Log management function (API) 183 Processing unit 184 Entry function 186 Debug log output Function 187 Log management function 188 Console 193 Business log output example 194 Debug log output example 201 Distribution status panel 202 Unconfirmed information panel 203 Downloaded panel 204 Business message panel 205 Date operation item 206 Operation button 207 Notification information ticker 208 Communication status display Panel 209 Confirmation status item 210 Contents 211 Date type 212 Size 213 Selection (check box) 214 Download button 215 All Select button 216 Clear all button 217 Information update button 218 Initial setting button 218-1 Initial setting: User ID 218-2 Download panel 218-3 Ticker panel 218-4 Alarm panel 218-5 Appearance panel 218-6 OK 218-7 Cancel 219 End button 220 Logout method 221 User management class 222 Detailed code confirmation method 230-12 Authentication database 231 DB expansion 232 CSV creation 251 Queue (queue) 254 CSV file database 256 DB server computer 257 Master database 258 Report management database 259 Form database 261 Each table 300 Target logo 301a Group responsible for securities handling 301b Trading of securities Assignee group 302 Manager 303 Manager 304 Site administrator 305 WAN user 306 "Current site WAN user list" 307a-c "Current DVP user list" 308 "Current securities handling manager list" 309 "Current" Securities Trading Representative List "311, 313, 315, 332, 334 Registration button 312, 314, 324, 326, 331, 333 Delete button 321 Current DVP user field 322 Current security handling person (entry available) field 323 Current securities handling person (no entry allowed) 328a, b Current DVP user field 329, 330 Current securities trading person list 340 Screen switching tab 341 Home tab 342 Matching business tab 343 Settlement business tab 344 Security management tab 345 Fail management 346 Information inquiry tab 347 Help tab 350 Page selection menu 351 Information menu button 352 Related site menu button 353 Archive menu button 354 Password change menu button 355 User information menu button 356 Broadcast notification list menu button 357 Site user management menu button 358 Access Right management menu button 360 Logout menu button 361 Form "Form specification" menu 362 Form "Form classification specification" menu 363 Form "User ID specification" menu 364 User access right management menu 365 Information screen page 366 Add simple link (MY TARGET) 366a Button 366b Edit button 367 User ID information field 373 Check box 374 Execute button 37 5 Reset button 376 Category 1 column 377 Category 2 column 391 Information 392 System operation report 393 Settlement business report 400 Page switching menu 401 Today's distribution information 402 Domestic stock trading statement 403 Bond transaction trading statement 404 Summary 405 Exercise 406 Distribution date Browsing units 407 Form search 408a Previous day posting button 408b Date specification field 408c Next day posting button 414 List list 414a Information name (form name) 414b Delivery time 414c File size 414d Confirmation status 414e Download 415 Today's search button 421 List display button 422 Page switching menu name 423 Information name title 424 Information name and distribution date 425 Distribution time 426 File capacity 427 Confirmation status 428 Download icon 431 “Previous page” button 432 “Next page” button 551-01 Form search menu button 551-02 Form name 551-03 Select / Clear all 551-04 Date 551-05 Date unspecified item 551-06 Reference date item 551 -07 Report date item 551-08 Report date 551-09 Brand name 551-10 Securities code 551-11 New securities code 551-12 Search button 551-13 Reset button 551-21 Information name + distribution date column 551-31 Today Distribution information menu screen 551-32 Search-only screen 551-33 Today's search icon 551-42 Date designation pop-up menu 551-43 Date move button 551-51 Distribution information menu button 551-61 Form search icon 551-62 Form search Window 82-01 Connection information tab 582-02 "Acquire information by static NAT method" button 582-03 "Acquire information by dynamic NAT method" button 582-04 Browser information tab 583-07 Client application 583-08 Server application 1421 Securities custody transfer system 1422 Clearing system, 1423 Cash settlement bank system

Claims (25)

[Claims] 1. A server computer that distributes public information including at least one of a business message and settlement information relating to the operation of a stock exchange, a client computer of a member of the stock exchange that receives the public information from the server computer, and The server computer further comprises: a distributable information distributing means for distributing distributable information indicating that the public information is distributable; and completion of the data setup of the settlement information. The setup completion notification information that the client computer has been notified, the distributable notification information that the distribution information has been notified to the client computer, and the payment information are downloaded on the client computer side. Downloaded information And a status notification information storage unit that stores status notification information including the payment information where the client computer has viewed the browsed information, and a status notification information using unit that performs a process using the status notification information. The distributable notification network system, wherein the client computer includes a distributable information receiving unit that receives the distributable information. 2. The server computer according to claim 1, wherein said server is configured to generate said deliverable notified information based on a deliverable information reception completion signal automatically transmitted based on reception of said deliverable information from said client computer. Information is generated based on a download completion signal automatically transmitted from the client computer based on download execution, and the browsed information is generated based on a browse execution signal automatically transmitted from the client computer based on browse execution. The network system according to claim 1, wherein the notification is generated. 3. The distributable information reception completion signal indicates that the distributable information is displayed on the client computer screen, so that it is determined that the distributable information has been received and automatically transmitted. 3. The network system according to claim 2, wherein 4. The server computer, when the data setup of the payment information is completed,
A data setup completion notification transmitting unit for transmitting a data setup completion notification to another server computer connected to the server computer; and transmitting the status notification information stored in the status notification information storage unit to the another server computer. A status notification information transmitting unit, wherein the processing using the status notification information is performed when the another server computer has not received the status notification information after a lapse of a predetermined time after receiving the data setup completion information. 2. The delivery possible notification network system according to claim 1, wherein the process is a process of stopping information transmission to the client computer, which is performed based on a stop command transmitted from the another server computer. 5. The server computer, when the data setup of the payment information is completed,
A data setup completion notification transmitting unit for transmitting a data setup completion notification to another server computer connected to the server computer; and transmitting the status notification information stored in the status notification information storage unit to the another server computer. A process using the status notification information, wherein the another server computer receives the data setup completion information after a lapse of a predetermined time, and does not receive the status notification information. A process for stopping transmission of information to the client computer performed based on a stop command transmitted from the another server computer; and during a stop state by the stop process, a communication state with the client computer is normal. Information transmission restart processing performed when it is determined that there is 2. The distribution enable notification network system according to claim 1, further comprising: 6. The server computer is connected to the server computer for member-confirmed information generated first for the member among the confirmed information including the downloaded information and the browsed information. The distribution according to claim 1, further comprising: a member confirmed information transmitting unit that transmits the member confirmed information to another server computer, wherein the another server computer includes a member confirmed information storage unit that stores the member confirmed information. Possible notification network system. 7. The server computer, wherein, among the confirmed information including the downloaded information and the browsed information, the member confirmed information generated first for the member is connected to the server computer. A member-confirmed information transmitting unit that transmits to another server computer; and a member-side confirmed information receiving unit that receives the member-confirmed information of the member from the another server computer. A member-confirmed information storage unit that stores the member-confirmed information; the distributable information distribution unit transmits the member-confirmed information to the client computer of the member; A confirmed information receiving means for receiving the member confirmed information of the member; and The together distributable information, distributable notification network system according to claim 1, characterized in that it comprises a distributable information display means capable of displaying the fact that already viewed or downloaded on any client computer of said members. 8. The network system according to claim 4, wherein said another server computer is provided in said server computer. 9. A public computer which is connected to a client computer on a member side of a stock exchange so as to be able to transmit and receive, and distributes public information including at least one of a business message and a settlement information relating to the operation of the stock exchange. A storage device that stores a program that defines the operation of the processing device, a storage device that stores a public information database that stores the public information, a server that creates the information, an input device that receives information from outside, and an external device. An output device for transmitting information; and an operation using the information received from the storage device or / and the input device, and the operation result is stored in the storage device or /
And a central processing unit that passes the output information to the output device. A distributable information distributing unit that distributes distributable information indicating that the public information can be distributed, and a data setup of the payment information. The setup completion notified information that the completion has been notified to the client computer side, the distributable notified information that the distributable information has been notified to the client computer side, and the payment information is stored on the client computer side. Status notification information storage means for accumulating status notification information including downloaded information indicating that the download has been performed, and the payment information viewed by the client computer; and performing a process using the status notification information. An information processing apparatus comprising: status notification information using means. 10. The distribution-enabled notification information is generated based on a distribution-enabled information reception completion signal automatically transmitted based on the reception of the distribution-enabled information from the client computer, and the downloaded information is generated by the client computer. It is generated based on a download completion signal automatically transmitted based on download execution from a computer, and the browsed information is generated based on a browse execution signal automatically transmitted based on browse execution from the client computer. The information processing apparatus according to claim 9, wherein 11. The information processing apparatus according to claim 10, wherein the reception of the deliverable information is determined to have been performed by displaying the deliverable information on the client computer screen. 12. A data setup completion notification transmitting unit that transmits a data setup completion notification to another server computer connected to the server computer when the data setup of the payment information is completed, and the status notification information storage unit. And a status notification information transmitting means for transmitting the status notification information stored in the server server to the another server computer. In the processing using the status notification information, the another server computer receives the data setup completion information After a predetermined time has elapsed, if the status notification information has not been received, the process is a process of stopping information transmission to the client computer performed based on a stop command transmitted from the another server computer. 10. The information processing apparatus according to claim 9, wherein 13. A data setup completion notification transmitting unit that transmits a data setup completion notification to another server computer connected to the server computer when the data setup of the payment information is completed, and the status notification information storage unit. And a status notification information transmitting means for transmitting the status notification information stored in the server server to the another server computer, wherein the processing using the status notification information is performed by the another server computer receiving the data setup completion information. After a predetermined time has elapsed, if the status notification information has not been received, a process of stopping information transmission to the client computer performed based on a stop command transmitted from the another server computer, and During the stop state, communication with the client computer is performed. The information processing apparatus according to claim 9, further comprising: a process of restarting information transmission performed when the communication state is determined to be normal. 14. Among the confirmed information including the downloaded information and the browsed information, the member confirmed information generated first for the member is transmitted to another server computer connected to the server computer. 10. The information processing apparatus according to claim 9, further comprising a member confirmed information transmitting unit for transmitting. 15. Among the confirmed information including the downloaded information and the browsed information, the member confirmed information generated first for the member is transmitted to another server computer connected to the server computer. A member-confirmed information transmitting unit for transmitting; a member-side confirmed information receiving unit for receiving the member-confirmed information of the member from the another server computer; Transmitting to the computer the member-confirmed information of the member, with an identification associated with the corresponding distributable information;
15. The information processing apparatus according to claim 14, wherein it is possible to display that the distributable information has already been viewed or downloaded by an arbitrary client computer of the member. 16. The information processing apparatus according to claim 12, wherein said another server computer is provided in said server computer. 17. A distributable notification method for distributing to a client computer on a member side of a stock exchange that public information including at least one of a business message relating to the operation of the stock exchange and settlement information has become distributable. The server computer, when the data setup of the payment information is completed,
Performing a data setup completion notification transmission procedure of transmitting a data setup completion notification to another server computer connected to the server computer, transmitting a data setup completion notification of the payment information to the client computer side, and from the client computer Performing a setup completion notified information receiving procedure of receiving the setup completion notified information that the date setup completion notification has been received, transmitting to the client computer side distributable information that the public information can be distributed, Transmitting the delivery possible notified information receiving procedure for receiving the delivery possible notified information indicating that the deliverable information has been received from the client computer, and transmitting the payment information download information to the client computer side; A download information receiving step of receiving the downloaded information indicating that the payment information has been downloaded from the client computer, and transmitting the information for viewing the payment information to the client computer side, and displaying the payment information on the screen from the client computer. Performing at least one of the viewed information receiving procedure of receiving the viewed information indicating that the information has been displayed, the setup completion notified information, the delivery possible notified information, the downloaded information, and the viewed information. Status notification information including at least one piece of information from the group consisting of
Perform a status notification information transmission procedure to transmit to the another server computer, after a predetermined time after the another server computer receives the data setup completion information, if the status notification information has not been received, the Performing a stop command receiving procedure for receiving a stop command from another server computer; and performing an information transmission stopping procedure for stopping information transmission to the client computer based on the stop command receiving procedure. Method. 18. A delivery notification method for delivering to a client computer on the member side of a stock exchange that public information including at least one of a business message and settlement information relating to the operation of the stock exchange has become available. The server computer, when the data setup of the payment information is completed,
Performing a data setup completion notification transmission procedure of transmitting a data setup completion notification to another server computer connected to the server computer, transmitting a data setup completion notification of the payment information to the client computer side, and from the client computer Performing a setup completion notified information receiving procedure of receiving the setup completion notified information that the date setup completion notification has been received, transmitting to the client computer side distributable information that the public information can be distributed, Transmitting the delivery possible notified information receiving procedure for receiving the delivery possible notified information indicating that the deliverable information has been received from the client computer, and transmitting the payment information download information to the client computer side; A download information receiving step of receiving the downloaded information indicating that the payment information has been downloaded from the client computer; and transmitting information for viewing the payment information to the client computer side, and the payment information is displayed on the screen from the client computer. Performing at least one of the viewed information receiving procedure of receiving the viewed information indicating that the information has been displayed, the setup completion notified information, the delivery possible notified information, the downloaded information, and the viewed information. Status notification information including at least one piece of information from the group consisting of
Perform a status notification information transmission procedure to transmit to the another server computer, after a predetermined time after the another server computer receives the data setup completion information, if the status notification information has not been received, the Performing a stop command receiving procedure for receiving a stop command from another server computer; performing an information transmission stopping procedure for stopping information transmission to the client computer based on the stop command receiving procedure; And transmitting an information transmission to the client computer when the communication state with the client computer is determined to be normal. 19. A distributable notification method for distributing to a client computer on a member side of a stock exchange that public information including at least one of a business message relating to the operation of a stock exchange and settlement information has become distributable. Performing a distributable information transmitting step of transmitting distributable information indicating that the public information can be distributed to the client computer side; transmitting the payment information download information to the client computer side; And a download information receiving procedure for receiving downloaded information indicating that the payment information has been downloaded from the client computer, and transmitting information for viewing the payment information to the client computer side, and displaying the payment information on the screen from the client computer. Receive browsed information indicating that Performing at least one of the viewed information receiving procedure, and among the confirmed information including the downloaded information and the viewed information, the member confirmed information generated first with respect to the member, Performing a member-confirmed information transmitting procedure for transmitting to a server computer different from the server computer; performing a member-side confirmed information receiving procedure for receiving the member's member-confirmed information from the another server computer; Is attached to the client computer of the member so that the member's confirmed information can be displayed on any client computer of the member. And performing a confirmed display procedure for transmitting the information. 20. The method according to claim 17, wherein said another server computer is provided in said server computer. 21. The computer for distributing public information including at least one of a business message relating to the operation of a stock exchange and settlement information to a client computer on a member side of the stock exchange, the data setup of the settlement information has been completed. sometimes,
A data setup completion notification transmitting procedure for transmitting a data setup completion notification to another server computer connected to the server computer, and transmitting a data setup completion notification of the payment information to the client computer side, and the client computer sends the date. A setup completion notified information receiving procedure for receiving setup completion notified information that a setup completion notification has been received, and distributable information indicating that the public information can be distributed to the client computer side, and the client A distributable notified information receiving step of receiving distributable notified information indicating that the distributable information has been received from a computer, and transmitting download information of the settlement information to the client computer side; A downloaded information receiving step of receiving downloaded information indicating that the payment information has been downloaded from the computer, and transmitting browsing information for the payment information to the client computer side; and the payment information is displayed on a screen from the client computer. A viewed information receiving procedure for receiving the viewed information indicating that the information has been displayed, at least one of the following steps: from the setup completion notified information, the delivery possible notified information, the downloaded information and the viewed information Status notification information including at least one piece of information from the group
Transmitting the status notification information to the another server computer, and after a predetermined time has elapsed after the another server computer has received the data setup completion information, if the status notification information has not been received, A stop command receiving procedure for receiving a stop command from the server computer, an information transmission stopping procedure for stopping information transmission to the client computer based on the stop command receiving procedure,
The program to execute. 22. The computer for distributing public information including at least one of a business message relating to the operation of the stock exchange and settlement information to a client computer on the member side of the stock exchange, the data setup of the settlement information is completed. sometimes,
Performing a data setup completion notification transmission procedure of transmitting a data setup completion notification to another server computer connected to the server computer, transmitting a data setup completion notification of the payment information to the client computer side, and from the client computer Performing a setup completion notified information receiving procedure of receiving the setup completion notified information that the date setup completion notification has been received, transmitting to the client computer side distributable information that the public information can be distributed, Transmitting the delivery possible notified information receiving procedure for receiving the delivery possible notified information indicating that the deliverable information has been received from the client computer, and transmitting the payment information download information to the client computer side; A download information receiving step of receiving the downloaded information indicating that the payment information has been downloaded from the client computer, and transmitting the information for viewing the payment information to the client computer side, and displaying the payment information on the screen from the client computer. Performing at least one of a browsed information receiving procedure of receiving the browsed information indicating that the information has been displayed, the setup completion notified information, the delivery possible notified information, the downloaded information, and the viewed information. Status notification information including at least one piece of information from the group consisting of
Perform a status notification information transmission procedure to transmit to the another server computer, after a predetermined time after the another server computer receives the data setup completion information, if the status notification information has not been received, the Performing a stop command receiving procedure for receiving a stop command from another server computer; performing an information transmission stopping procedure for stopping information transmission to the client computer based on the stop command receiving procedure; And an information transmission restarting procedure for restarting information transmission to the client computer when it is determined that the communication state with the client computer is normal. 23. The public information can be distributed to a computer that distributes public information including at least one of a business message relating to the operation of the stock exchange and settlement information to a client computer on the member side of the stock exchange. Transmitting the distributable information to the client computer side, and transmitting the payment information download information to the client computer side, and downloading the payment information from the client computer to the effect that the payment information has been downloaded. A downloaded information receiving procedure for receiving information, and browsing for transmitting the payment information browsing information to the client computer side and receiving browsed information indicating that the payment information has been displayed on the screen from the client computer. Information reception procedure Transmitting at least one procedure, among the confirmed information including the downloaded information and the browsed information, the member confirmed information generated first for the member to a server computer different from the server computer; A member-confirmed information transmitting procedure, a member-side confirmed information receiving procedure for receiving the member's member-confirmed information from the another server computer, and the distributable information has already been viewed or Executing a confirmed display step of transmitting, to the client computer of the member, the member's member confirmed information with an identification associated with the corresponding distributable information so as to be able to display the download. Program to let you. 24. The program according to claim 21, wherein said another server computer is provided in said server computer. 25. A storage medium storing the program according to claim 21.