JP3241278B2 - Network print system - Google Patents

Description

DETAILED DESCRIPTION OF THE INVENTION

[0001]

[0001] 1. Field of the Invention [0002] The present invention relates to a network print system which transfers print data from a spooler of a client to a spooler of a server and outputs the print data from a printer connected to the server in a network system constructed by a client and a server.

[0002]

2. Description of the Related Art FIG. 16 shows, for example, Net published by Nikkei BP.
1 is an overall configuration diagram of a conventional network print system described in a Ware system construction technique. The client 100 has a spooler 102 that receives a print data stream sent by executing the print program 101 and transfers the print data stream to the server 200. Spooler 102
Is a spool creation unit 103 that converts a received print data stream into a transferable format to create a spool file, and a data output unit 104 that sends print data (spool) to the connected server 200.
And The spool to be transferred is strictly created as a file, but the file is created only for the sake of convenience inside the spooler 102 and is not stored outside. I will use expressions.

[0003] On the other hand, the server 200
And a spool file 202 for temporarily storing print data.
And a spooler 203 that receives print data sent from the client 100 and outputs the print data to the printer 201. A spooler 203 includes a data output unit 204 that outputs print data to a printer 201, and a spool file management unit 205 that creates a spool file 202 that stores print data in a printable format and deletes an unnecessary spool file 202. have.

A conventional printing process having the above configuration will be described below. First, a description will be given of a process in a case where the transfer of the print data is normally completed. FIG. 17 shows a system time chart when the printing process is completed normally.

When a print data stream created by executing the print program 101 is received, a spool creation unit 103 creates a spool from the print data stream. The spooler 102 converts the created spool into a predetermined transfer format such as data compression, and then transfers the spool from the data output unit 104 to the server 200 via an output port.

In the server 200, a spool file management unit 205 creates a spool file 202 for storing the received spool, and stores the spool file 202 in a printable format. The spooler 203 schedules an output process of the print data stored in the spool file 202,
After confirming that the printer 201 is not in use, printing of the spool is started. When printing is completed, the spool file management unit 205 deletes the spool file 202 that stores the print data for which printing has been completed.

Next, a printing process when an abnormality is detected in the communication between the client and the server will be described. FIG. 18 shows a system time chart when this abnormality is detected.
Shown in

When a print data stream is created as in the normal case and a failure is detected when the first spool is transferred from the data output unit 104 to the server 200, the process waits until the failure is recovered. After the recovery from the failure, the spool is transferred to the server 200. Server 20
At 0, the operation is the same as in the normal case, the received spool is stored in the spool file 202, and the stored print data is output. Then, the spool file 202 for storing the print data for which printing has been completed is deleted.

Japanese Patent Application Laid-Open No. Hei 8-6747 discloses a configuration in which a client is provided with means for storing and storing print data and print control information. In this conventional example, a print program is created. By terminating the processing of the print program when the print data is stored in the storage means, the processing speed of the print program can be reduced, and the saved print data can be re-transferred after recovery from a failure that has occurred. ing.

[0010]

However, in the related art, the transfer processing to the server is performed after all the print data to be transferred to the server is received, so that the print processing is not very efficient. I can't say. That is, for example, if it is assumed that the process of creating print data takes one hour, the print data created at the beginning of this process waits for at least one hour even though printing is possible. Therefore, a system that is more efficient and can reduce the time required for the printing process is desired.

[0011] Further, if it is assumed that an error has occurred in the communication between the client and the server, conventionally, a communication failure is detected only at the time of the transfer processing to the server after the creation of the print data. That is, for example,
If it takes one hour to create print data,
Fault detection will only be noticed after at least one hour has passed. Therefore, a system that can reduce the time required for print processing even when a failure occurs is desired.

SUMMARY OF THE INVENTION The present invention has been made to solve the above problems, and a first object of the present invention is to shorten the time required for printing by enabling the server to start printing more quickly. It is to provide a network print system capable of performing such operations.

A second object of the present invention is to make it possible to start printing on a server more quickly by quickly detecting the failure even when an error occurs in the communication between the client and the server, so that printing can be performed quickly. An object of the present invention is to provide a network print system that can reduce the time required.

[0014]

In order to achieve the above object, a network print system according to a first aspect of the present invention transfers print data obtained by executing a print program from a spooler of a client to a spooler of a server. In the network printing system for outputting from a printer connected to the server, the client sequentially stores a spool file for storing a predetermined amount of print data every time a predetermined amount of print data is obtained by executing the print program. Spool creation means to be created,
Server information holding means for holding a transfer enable / disable state with the server, and periodically monitoring a communication state between the servers;
A server information management means for setting a transfer disabled state between a client and a server in the server information holding means, and a transfer disabled state set in the server information holding means constantly monitored at the time of failure recovery to recover the failure; the spool file to be transferred was that to the server that the failure is recovered at the time of recognizing the and a print data reintroduction means to be introduced into the spooler of the Kurainto, the spool
Creating means, irrespective of a communication state between the servers,
Created by continuing the spool file, the client-side spooler every time the spool file is created by the spool creating means, the spool file
Spool file creation processing in the spool creation means
The spool file is transferred to the spooler of the server in parallel with the processing, or the spool file is transferred to the spooler of the server every time the spool file is input from the print data re-input unit.

[0015] In a second aspect of the present invention, in the network print system according to the first aspect, the client comprises:
And a print data deletion unit for deleting the spool file whose transfer to the server has been normally completed.

According to a third aspect of the present invention, in the first aspect of the present invention, the spooler of the server receives the spool file transferred from the client each time the spooler receives the spool file. Is output to the printer.

According to a fourth aspect of the present invention, in the network print system according to the first aspect, the server does not normally receive print data including the series of spool files sent from the client until the end. Printing stop means for stopping the printing process when the printing operation is stopped.

[0018]

[0019]

[0020]

[0021]

According to a fifth aspect of the present invention, in the network print system according to the first aspect, wherein the client
When the transfer to the server is impossible, there is provided transfer destination switching means for switching the transfer destination of the spool file from the spooler of the server to another.

[0023]

Preferred embodiments of the present invention will be described below with reference to the drawings.

FIG. 1 is an overall configuration diagram showing an embodiment of a network print system according to the present invention.
FIG. 1 shows a configuration in which a client 10 that requests printing and a server 20 that undertakes printing are connected.
Note that the client 10 can be connected to a plurality of servers 20, and the server 20
Can be connected, but only one unit is shown for convenience.

The client 10 includes a spool file 11 for storing a predetermined amount of divided print data, a spooler 12 for receiving a print data stream sent by executing the print program 1 and transferring the stream to the server 20,
Copy the spool file 11 to the spooler 12 of the client 10
A spool file re-input unit 13 serving as a print data re-input unit to be input to the printer 1 and a printer 1 connected locally.
And 4. The spooler 12 includes a spool file creation unit 15, a spool file deletion unit 16, a server information table 17, a server information management unit 18, and an output destination switching unit 19. Spool file creation unit 15
Is provided as a spool creating unit, and sequentially creates a spool file 11 for storing a predetermined amount of print data every time a predetermined amount of print data is obtained by executing the print program 1. The spool file deletion unit 16 is provided as a print data deletion unit, and deletes the spool file 11 that has been normally transferred to the server 20. The server information table 17 is provided as a server information holding unit, and holds a state in which transfer with the server 20 is not possible. FIG. 2 is a diagram showing an example of the setting contents of the server information table 17, in which a transfer enable flag is set for each server. In the present embodiment, transfer is enabled when the transfer enable flag is "0", and transfer is disabled when the transfer enable flag is "1". The server information management unit 18 is a server information management unit, and sets a transfer enable flag of the server information table 17 in accordance with a transfer enable / disable state to the server 20. That is, “1” indicating that transfer is not possible when an error occurs in the client-server communication, and “0” indicating that transfer is possible when the communication failure is recovered, are respectively assigned to the server 20. Is set to the transfer enable flag corresponding to. The output destination switching unit 19
It is provided as a transfer destination switching means, and switches the spool transfer destination from the spooler of the server 20 to another when transfer to the server 20 is impossible. The output destination switching unit 19 in the present embodiment is configured to output to the locally connected printer 14 as shown in FIG.

On the other hand, the server 20 includes a printer 21, a spool file 22 created for temporarily storing data transferred from the client 10, and a spooler for outputting to the printer 21 each time a spool file is received from the client 10. 23. The spooler 23 includes a data output unit 24, a spool file management unit 25, and a print control execution unit 26. The data output unit 24 outputs the print data to the printer 21. The spool file management unit 25 creates the spool file 22 in a printable format and deletes the unnecessary spool file 22. The print control execution unit 26 is provided as a print canceling unit, and cancels a print process when print data including a series of spool files sent from the client 10 cannot be normally received to the end.

In the above configuration, the spool files 11 and 22 are created in a disk device (not shown) connected to each of the computers 10 and 20, and the other components of the printing program 1, the spoolers 12, 23, and the spool The file re-input unit 13 is created by software, and performs each function on the CPU of each of the computers 10 and 20.

A feature of the present embodiment is that print data created on the client 10 side is divided by a predetermined amount to create a spool file 11, and the spool file 11 is created each time the spool file 11 is created. 11 is transferred to the server 20 side. That is, the client 10 can execute the process of creating the spool file 11 based on the print data stream and the process of transferring the created spool file 11 to the server 20 in parallel. This allows
The time required for the printing process can be greatly reduced throughout.

Next, the printing process according to the present embodiment will be described. First, new print data is created,
A process when the print data is normally transferred to the server 20 and printed from the printer 21 will be described. FIG. 3 is a diagram showing a time chart when the printing process is completed normally, and corresponds to FIG. 17 of the conventional example.

First, as shown in FIG. 4, in the print program 1, when a server 20 to be an output destination and a printer 21 connected to the server 20 are designated, print data creation processing is started ( Step 101), a print data stream is created (Step 102). And
The created print data streams are sequentially sent to the spooler 12 (step 103).

FIG. 5 is a flowchart showing a printing process performed by the spooler 12. According to FIG. 5, spooler 1
2 is in a waiting state for occurrence of an event (step 11
1). Here, when the print data stream is sent due to the execution of the print program 1 (step 1).
12), the spool file 11 is created / transferred (step 113). This spool file 11
The details of the creation / transfer process will be described with reference to the flowchart shown in FIG.

First, a spool file creation / transfer routine for executing this processing is a routine called when a print data stream is generated. First, the variables i, R
Initialization is performed by substituting 1 into et (step 121). Upon successively receiving the print data stream, the spool file creator 15 reads the print data stream into a buffer (not shown) having a predetermined size (step 122). Then, the read print data for the buffer size is converted into a predetermined format that can be transmitted over a network, and is created and stored as a spool file 11 (step 12).
3). When one spool file 11 is created, the transfer possibility check process shown in FIG. 7 is performed (step 124). In the present embodiment, the predetermined amount when the print data stream is divided depends on the size of the buffer. However, the predetermined amount does not depend on the buffer size by taking the transfer size into consideration. A fixed amount may be set or a multi-buffer may be used. The setting of the predetermined amount is only a design matter.

The transfer possibility check routine determines whether transfer is possible by referring to the transfer possible flag in the server information table 17 (step 131). In the present embodiment, the value read from the server information table 17 is directly returned to the spool file creation / transfer routine (steps 132 and 133).

In the spool file creation / transfer process shown in FIG. 6, when the spool file 11 can be transferred (transfer enable flag = “0”), the created spool file 11 is transferred to the server 20 ( Step 125). When the transfer ends normally, the variable i is incremented (step 126).

On the other hand, when the transfer of the spool file 11 is not possible (the transfer enable flag = “1”), the server information management unit 18 stores the transfer enable flag corresponding to the transfer destination server 20 of the server information table 17 in the server information table 17. The value is set to "1" (step 127). Then, "0" indicating an abnormality is substituted for the return status Ret of this routine (step 128), and the variable i is incremented (step 126). As is clear from the above processing, the variable i is a variable for calculating the number of divisions of the print data stream, that is, the total number of spool files 11 to be created.

After the above processing, if the reading into the buffer has not reached the end of the print data stream, the flow returns to the processing for reading the print data stream into the buffer (step 122) (step 129). When the end of the print data stream is reached, (i-1) is substituted for the global variable ALL, and a return status Ret is returned (step 130). Note that the value of the global variable ALL is the total number of spool files created by dividing the print data stream.

As described above, according to the present embodiment, the spool file 11 is created based on the created print data stream in the spool file creation / transfer processing (step 113) shown in FIG. Each time, the data is sequentially transferred to the server 20. That is, FIG.
As is apparent from the above description, in the present embodiment, the transfer processing to the server 20 is started only by waiting for the time when the buffer is filled with a part of the print data stream and the spool file 11 is created. Can be greatly reduced.

In FIG. 5, when the transfer / creation processing of the spool file 11 ends abnormally (Ret = 0), the process returns to the event waiting state (Step 111), and when the process ends normally (Ret = 1). Deletes the spool file 11 (step 114). The spool file deletion process performed by the spool file deletion unit 16 in step 114 will be described with reference to the flowchart shown in FIG.

In the spool file deletion routine, after the variable i is initialized to 0 (step 141), the spool file (i) is deleted (step 142). The variable i is incremented (step 143), and the above processing is repeated until the variable i reaches the global variable ALL (step 144). As a result, all the spool files 11 created in the client 10 can be deleted.

Next, a printing process in the server 20 to which the spool file 11 is transferred will be described with reference to FIG. First, a description will be given of a normal process when a series of spool files are received from the client 10.

When the spooler 23 of the server 20 receives the spool file, it stores it as the spool file 22 of the server 20 (step 151).
Then, when the spooler 23 receives the first spool file and the printer 21 is in a print request waiting state, it starts printing the print data included in the spool file 22 (step 152). If it is in a state other than waiting for a print request, output processing to the printer 21 is scheduled. Then, the above processing is repeated until the final spool file is transferred from the client 10 (step 154). When the spooler 23 receives the final spool file and the printer 21 finishes printing normally, it notifies the client 10 to that effect (step 155).

In the present embodiment, one print data stream is divided into a plurality of spool files 11 and transferred to the server 20. Information indicating presence or absence is included. Therefore, the spooler 23 of the server 20 can determine whether or not there is a succeeding spool file and whether or not it is the last by checking this information every time a spool file is received. As a result, in step 152, if the spool file that should have been transferred subsequently is not received within the predetermined time, printing is stopped because a communication failure has occurred (step 156).
Here, the details of the process of canceling printing performed by the print control execution unit 26 will be described with reference to FIG.

When a timeout occurs, the print control execution unit 26 checks whether or not another spool file 22 constituting the same print data stream as the spool file that could not be received is printed (step 161). If there is a print job, a print stop code is sent to the printer 21 to forcibly stop printing (step 16).
2). On the other hand, if there is no print job in progress, the other spool files 22 already received are determined to have not been printed and are deleted from the schedule (step 16).
3). Thereafter, a series of spool files 22 constituting one print data stream are all deleted (step 164). This is because it is useless to hold a series of spool files 22 normally received due to abnormal termination. However, it is more efficient not to delete the received spool file 22 if, for example, a serial number is assigned to the series of spool files 22 and the server 20 notifies the client 10 of a serial number that the client 10 wants to retransmit. In this way, the server 20 can cope with a failure in the communication between the client and the server.

In this embodiment, the spool file is sent to the server 20 every time a predetermined amount of print data stream is created as described above. When FIG. 3 is compared with FIG. 17, it is clear at a glance that not only the job on the client 10 side but also the time required for the printing process can be significantly reduced. Needless to say, the time required to create, transfer, receive, and print the print data is the same as in the conventional example. In the present embodiment, the print data is divided and the spool file is created so that the spool file creation process and the transfer process in the client 10 can be performed in parallel, so that the time required for the print process is greatly reduced. Can be shortened.

In the above processing, basically, the processing when the print data is normally transferred to the server 20 and printed from the printer 21 has been described. Next, the created spool file 11 is not transferred to the server 20. The processing at the time of abnormality when the error occurs will be described. In addition, FIG.
FIG. 19 is a diagram showing a system time chart when an abnormality is detected in the transfer processing between the client and the server, and corresponds to FIG. 18 of the conventional example.

In FIG. 5, when a print data stream is sent while the spooler 12 is waiting for an event to occur, spool creation / transfer processing is executed (steps 111 to 113). Create this spool /
The details of the transfer process have already been described with reference to the flowchart shown in FIG. By the way, it is determined in step 124 in FIG. 6, that is, whether or not communication with the designated server 20 is possible by the transfer possibility check process shown in FIG. 11 is executed when it is created. That is, in the prior art, it is determined whether or not communication with the destination server 20 is possible only after waiting for the entire print data stream to be created. The determination can be made when a part of the data stream, that is, the first spool file 11 is created and is to be transferred.

As described above, when the transfer to the server 20 is not possible, that is, when the return status from the spool creation / transfer processing in step 113 is “0” indicating an abnormal end, the occurrence of the event Although the process returns to the wait state (step 111), the process of creating the remaining spool file 11 is continued even while the transfer cannot be executed.

By the way, the server information management unit 18 monitors the communication state between the servers on a regular basis, or indirectly detects that the failure has been recovered by a setting input by a system administrator or the like, and when the server information management unit 18 detects that the failure has been restored. Is set to "0" in the server information table 17 corresponding to. FIG. 12 shows a flowchart of the processing in the spool file re-entry unit 13. The spool file re-entry unit 13 is started by a system administrator or the like, or constantly monitors the transfer enable flag of the server information table 17 when a failure occurs. When it is detected that the transfer enable flag of the server 20 has been set to "0", it is recognized that the communication has been restored (step 171), and the spool files 11 created in the spooler 12 are sequentially sent out (step 17).
2).

In FIG. 5, when the spooler 12 waiting for an event receives the spool file 11 from the spool file re-input unit 13 (steps 111 and 11).
2, 115), and perform a spool file transfer process (step 116). This process is almost the same as the spool file creation / transfer process shown in FIG. 6 except that the spool file creation process is excluded. FIG. 13 shows a flowchart of the spool file transfer process.

In FIG. 13, the spooler 12 first
Initialization is performed by substituting 1 into variables i and Ret (step 181). Then, the created spool file 11 is transferred to the server 20 (step 18).
2). When the transfer is completed normally, the variable i is incremented (step 183). This process is repeated until the variable i reaches the global variable ALL (step 184).

On the other hand, when the transfer of the spool file 11 has failed, the server information management unit 18 sets the value of the transfer enable flag corresponding to the server 20 of the transfer destination in the server information table 17 to "1" (step 185). ). Then, "0" indicating an abnormality is substituted for the return status Ret of this routine (step 186). Then, when the transfer of the spool file 11 has been normally performed and the end of the print data stream has been reached, or when the transfer of the spool file 11 has not been normally performed, a return status Ret is returned (step 187). finish.

As described above, according to the present embodiment, since the print data stream is stored in the spool file 11, the print data stream can be created without restarting the print program 1 at the time of recovery from the failure. Spool file 1
1 can be transferred to the server 20. And FIG.
Spool file transfer process (step 116)
After that, the above-described spool file deletion processing (step 1)
Perform 14).

As is clear from FIG. 11, in the present embodiment, the transfer processing to the server 20 is started after the creation of one spool file 11 is completed. Abnormality can be detected. As a result, it is possible to immediately start the recovery work from the time without waiting for the creation of all the spool files 11 from the print data stream. In addition, the transfer process to the server 20 can be restarted earlier by the time, so that the time required for the print process can be greatly reduced.

As described above, the server information management unit 18 changes the set value of the server information table 17, but the processing performed in the server information management unit 18 will be described with reference to the flowchart shown in FIG. In short, when the server information management unit 18 receives the server name and the value of the transfer enable flag to be updated (step 191), the transfer specified in the transfer enable flag of the specified server 20 in the server information table 17 is performed. A possible flag value is set (step 192). In this way, whether or not transfer to each server to which the client 10 is connected is set in the server information table 17 can be easily determined.

In the present embodiment, the output destination switching unit 1
9 is also one of the features. The processing in the output destination switching unit 19 will be described with reference to the flowchart shown in FIG.

The output destination switching unit 19 controls the spool file 1
When the output destination of 1 is received, that is, the server name (step 201), the value of the transfer enable flag corresponding to the server 20 in the server information table 17 is set to
(Step 202). If the value is transferable (transferable flag = "0"), the output destination is directed to the server 20 (step 203). If transfer is not possible (transfer enable flag = “1”), the output destination is the printer 14
To the local port where is connected (step 2
04). Thus, even when the output from the printer 21 connected to the server 20 is impossible, the print data can be output from the printer 14 instead of the locally connected printer.

In this embodiment, when the transfer to the server 20 is impossible, the local printer 1 is unconditionally set.
4, the output may be switched to a backup server other than the local printer 14. In addition, by having a table or the like in which the switching destination is set, the output destination can be switched to an arbitrary server.

[0058]

According to the present invention, spool data is created by dividing print data created on the client side by a predetermined amount, and the spool file is transferred to the server each time a spool file is created. I did it. That is, if you wait only for the time when the spool file is created,
The transfer process to the server is started, and after that, the process of creating the spool file based on the print data and the process of transferring the created spool file to the server can be executed in parallel. The time required can be greatly reduced. In addition, failure recovery can be detected.
Created and saved immediately after disaster recovery.
You can restart the transfer of the spool file as it is
You.

Since the print data deleting means is provided,
A spool file that has been successfully transferred can be deleted.

Since printing is started immediately upon receipt of the transferred spool file on the server side, the spool file receiving process and the output process to the printer can be performed in parallel. As a result, the time required for the entire printing process can be significantly reduced.

Further, when the server cannot properly receive the spool file to be transferred, if another spool file constituting the same print data stream as the spool file is in the process of being printed, the spool file is output. Is canceled, and the job is deleted from the schedule if the job has not been printed yet, so that useless printing is not required.

[0062]

[0063]

Further, since the transfer destination switching means is provided, even when communication with the server which should perform printing cannot be normally performed, the output destination can be switched to another server or a local printer.

[Brief description of the drawings]

FIG. 1 is an overall configuration diagram showing an embodiment of a network print system according to the present invention.

FIG. 2 is a diagram showing an example of setting contents of a server information table in the present embodiment.

FIG. 3 is a diagram showing a time chart when the printing process is normally completed in the embodiment.

FIG. 4 is a flowchart illustrating processing in a print program according to the present embodiment.

FIG. 5 is a flowchart illustrating print processing performed by a spooler of a client according to the present embodiment.

FIG. 6 is a flowchart showing details of a spool file creation / transfer process shown in FIG. 5;

FIG. 7 is a flowchart showing a transfer possibility check process shown in FIG. 6;

FIG. 8 is a flowchart illustrating a spool file deletion process performed by the spool file deletion unit illustrated in FIG. 5;

FIG. 9 is a flowchart illustrating a printing process performed by a spooler of a server according to the present embodiment.

FIG. 10 is a flowchart illustrating a print stop process performed by a print control execution unit illustrated in FIG. 9;

FIG. 11 is a diagram showing a system time chart when an abnormality is detected in a transfer process between a client and a server in the present embodiment.

FIG. 12 is a flowchart showing a process in a spool file re-entry section of the present embodiment.

FIG. 13 is a flowchart showing a spool file transfer process shown in FIG. 5;

FIG. 14 is a flowchart illustrating a process performed in a server information management unit according to the present embodiment.

FIG. 15 is a flowchart illustrating a process performed in an output destination switching unit according to the present embodiment.

FIG. 16 is an overall configuration diagram showing a conventional network print system.

FIG. 17 is a diagram showing a time chart when a printing process is normally completed in the related art.

FIG. 18 is a diagram showing a system time chart when an abnormality is detected in a transfer process between a client and a server in the related art.

[Explanation of symbols]

1 printing program, 10 clients, 11 and 22
Spool file, 12, 23 Spooler, 13 Spool file re-input unit, 14, 21, Printer, 15
Spool file creation unit, 16 spool file deletion unit, 17 server information table, 18 server information management unit, 19 output destination switching unit, 20 servers, 24 data output unit, 25 spool file management unit, 26 print control execution unit.

──────────────────────────────────────────────────続 き Continuation of front page (56) References JP-A-4-52738 (JP, A) JP-A-4-80055 (JP, A) JP-A-8-6747 (JP, A) JP-A-2- 99376 (JP, A) JP-A-6-242901 (JP, A) Monthly ASCII DOS / VISSUE (1995-11-01) p133 (screen 12). (58) Fields investigated (Int. Cl. ⁷ , DB) Name) G06F 3/12

Claims (5)

(57) [Claims] 1. A network print system for transferring print data obtained by executing a print program from a spooler of a client to a spooler of a server and outputting the print data from a printer connected to the server, wherein the client executes the print program. A spool creation unit for successively creating a spool file for storing the predetermined amount of print data each time a predetermined amount of print data is obtained, a server information holding unit for holding a transfer disabled state with the server, and the server Server information management means for periodically monitoring the communication state between the servers and setting a transfer enable / disable state between the client and the server in the server information holding means; and a transfer set in the server information holding means at the time of failure recovery. When monitoring the availability status and recognizing that the fault has been recovered A print data reintroduced means that failure to introduce the spool file to be transferred to the server which is restored to the spooler of the Kurainto, wherein the spool creating means includes a communication state between said server
Regardless of whether the spool file is created by the spool creation means, the spooler continues to create the spool file regardless of the spool file .
The pool file is spooled by the spool creation means.
To the server's spooler in parallel with the file creation process
A network print system for transferring the spool file to the spooler of the server each time the spool file is transferred or the spool file is input from the print data re-input unit. 2. The network print system according to claim 1, wherein the client has a print data deleting unit for deleting the spool file that has been normally transferred to the server. 3. The printer according to claim 1, wherein the spooler of the server outputs print data included in the spool file to the printer each time the spooler receives the spool file transferred from the client. Network print system. 4. The printing apparatus according to claim 1, wherein the server has a print stop unit that stops print processing when print data including the series of spool files sent from the client cannot be normally received to the end. The network print system according to claim 1, wherein 5. The server according to claim 1, wherein the client has transfer destination switching means for switching a transfer destination of the spool file from a spooler of the server to another when transfer to the server is impossible. Network print system.