Use of "pipes" for the transfer of status information between different remote systems

• US 5,506,945 A
• Filed: 09/27/1993
• Issued: 04/09/1996
• Est. Priority Date: 09/30/1992
• Status: Expired due to Term

• Current Assignee: Bull Sas (Atos SE)
• Original Assignee: Bull Sas (Atos SE)
• Inventors: Coutand, Bernard
• Primary Examiner(s): Powell, Mark R.
• Assistant Examiner(s): LEGREE, TRACY MICHELLE
• Application Number:
  US08/127,780
• Time in Patent Office: 925 Days
• Field of Search: 395/114, 395/115, 395/112, 395/200, 395/113, 364/948.34, 364/260.3
• US Class Current: 358/1.15
• CPC Class Codes: G06F 9/544 Buffers; Shared memory; Pipes

Abstract

The files containing status information from remote systems (RS) of a network are transferred automatically to a local system (LS) controlling a printer thanks to this procedure. To do this, with the printer connected to the network, associated with each file transfer two synchronization files or "pipes" are used, the first (P₁) in the direction local system to remote system and the second (P₂) in the direction remote system to local system. Thus, an automaton for retrieving status reports is created for the purpose of printing them on the printer of the local system. These synchronization files principally provide the synchronization and communication between a scan and command process (SCP) of the remote system which is initiated on the local system and a file transfer process (FTP) which returns the status reports to be printed from the remote system to the local system.

Claims

1. A Transfer procedure, to a local system controlling a printer, of a number of files forming reports containing status information from a number of remote systems of a network for printing said status information on the printer of the local system, wherein associated with each file transfer from a remote system are two synchronization files of the type known as "pipes", the first pipe in a direction local system to remote system, and the second pipe in a direction remote system to local system, said synchronization files creating an automaton for retrieval of multiple reports providing primarily synchronization and communication between:

a scan and command process initiated on the local system, the scan and command process monitoring the associated remote system and sending the remote system a command for the report to be transmitted, and

a file transfer process by which the status information to be printed is sent from the remote system to the local system.

2. A file transfer procedure according to claim 1, wherein associated with each scan is a scan configuration file comprising:

parameters for a name of the local system,

a name of the remote system scanned,

a name of a mail box scanned,

a time the scan begins,

a name of a status retrieval disk, and

parameters of the reports to be retrieved.

3. A file transfer procedure according to claim 2, wherein the synchronization files are communicating different messages by means of a specific application, the file transfer procedure further comprising:

a first step wherein the scan and command process queries the file transfer process to obtain the names of the reports to be transferred to the local system for printing and sends a message containing a request for the report name, said request containing data which allows obtaining the name of the mail box of the remote system whereby the name of the desired report is found;

a second step wherein the file transfer process, in response to the request, examines said mail box in order to send, if the mail box is empty, a specific message to the local system and, if the mail box is not empty, to send to the local system the data relating to the name of the report with the report'"'"'s situation on the remote system, and print parameters, said print parameters comprising data which is then used by the scan and command process,

a third step, wherein the scan and command process performs the retrieval of the waiting report, the retrieved report is then stored on a receiving disk of the local system under a directory intended for the local system, and,

a fourth step wherein a print command is initiated for the printing of the report on the desired printer of the local system.

4. A file transfer procedure according to claim 3, wherein the scan and command process begins by reading the appropriate scan configuration file to learn the data necessary for the scan, the data includes the name of the remote system to be monitored and the name of the mail box in which the desired report is stored, the scan and command process then enters a first loop, wherein the scan and command process:

communicates with the remote system through the first synchronization file in which the scan and command process writes the data for the request of the report name,

initiates the command for the specific application for the transmission of the data,

waits to read a response from the remote system, through the second synchronization file, and

enters a second loop, if the response includes a message "mail box empty", the scan and command process;

waits a predetermined time then resends a request, or if the answer includes the name of the report to be retrieved requests transfer of the name of the report through the first synchronization file by means of the specific application,

retrieves this report which is stored in an appropriate directory, and

initiates a print command.

5. A file transfer procedure according to claim 4, wherein the file transfer process in a preliminary monitoring phase:

waits for a message coming from the local system through the first synchronization file,

enters a loop when it detects the arrival of the message, and

reads the information containing, among other items, the name of the mail box in which the report to be retrieved must be stored and the name of the local system waiting for the report to be retrieved, the file transfer process then reads in the appropriate mail box if the desired report is stored there, and issues a response by means of the specific application through the second synchronization file,

if the mail box is empty an error code is provided and the file transfer process sends the local system a message "mail box empty" and,

if the mail box is not empty, after receiving the data pertaining to the name of the desired report with the report'"'"'s exact location and print parameters, the file transfer process sends the local system said data concerning the report to be retrieved.

6. A file transfer procedure according to claim 5, wherein the file transfer procedure further comprises:

a stop process used locally to interrupt one or more scans, and

a stop message being written in the synchronization file of a specific scan for each of the scans to be interrupted.

7. A file transfer procedure according to claim 6, wherein the file transfer procedure further comprises:

a process for monitoring the automaton and for unblocking the local system in the event of a network problem;

the process issuing locally, at each predetermined interval throughout the application of the procedure, a specific message stored in the synchronization file, the scan and command process receives said specific message, analyzes said specific message, and counts the number of times said specific message appears successively, the scan and command process detecting a network block, and the scan and command process is then automatically interrupted when only said message without other data is received a predetermined successive number of times.

8. A file transfer procedure according to claim 1, wherein the synchronization files are communicating different messages by means of a specific application, the file transfer procedure further comprising:

a first step wherein the scan and command process queries the file transfer process to obtain the names of the reports to be transferred to the local system for printing and sends a message containing a request for the report name, said request containing data which allows obtaining the name of the mail box of the remote system whereby the name of the desired report is found;

a second step wherein the file transfer process, in response to the request, examines said mail box in order to send, if the mail box is empty, a specific message to the local system and, if the mail box is not empty, to send to the local system the data relating to the name of the report with the report'"'"'s situation on the remote system, and print parameters, said print parameters comprising data which is then used by the scan and command process,

a third step, wherein the scan and command process performs the retrieval of the waiting report, the retrieved report is then stored on a receiving disk of the local system under a directory intended for the local system, and,

a fourth step wherein a print command is initiated for the printing of the report on the desired printer of the local system.

9. A file transfer procedure according to claim 8, wherein the scan and command process begins by reading the appropriate scan configuration file to learn the data necessary for the scan, the data includes the name of the remote system to be monitored and the name of the mail box in which the desired report is stored, the scan and command process then enters a first loop, wherein the scan and command process:

communicates with the remote system through the first synchronization file in which the scan and command process writes the data for the request of the report name,

initiates the command for the specific application for the transmission of the data,

waits to read a response from the remote system, through the second synchronization file, and

enters a second loop, if the response includes a message "mail box empty", the scan and command process;

waits a predetermined time than resends a request, or if the answer includes the name of the report to be retrieved requests transfer of the name of the report through the first synchronization file by means of the specific application,

retrieves this report which is stored in an appropriate directory, and

initiates a print command.

10. A file transfer procedure according to claim 9, wherein the file transfer process in a preliminary monitoring phase:

waits for a message coming from the local system through the first synchronization file,

enters a loop when it detects the arrival of the message, and

reads the information containing, among other items, the name of the mail box in which the report to be retrieved must be stored and the name of the local system waiting for the report to be retrieved, the file transfer process then reads in the appropriate mail box if the desired report is stored there, and issues a response by means of the specific application through the second synchronization file,

if the mail box is empty an error code is provided and the file transfer process sends the local system a message "mail box empty" and,

if the mail box is not empty, after receiving the data pertaining to the name of the desired report with the report'"'"'s exact location and print parameters, the file transfer process sends the local system said data concerning the report to be retrieved.

11. A file transfer procedure according to claim 10, wherein the file transfer procedure further comprises:

a stop process used locally to interrupt one or more scans, and

a stop message being written in the synchronization file of a specific scan for each of the scans to be interrupted.

12. A file transfer procedure according to claim 11, wherein the file transfer procedure further comprises:

a process for monitoring the automaton and for unblocking the local system in the event of a network problem;

the process issuing locally, at each predetermined interval throughout the application of the procedure, a specific message stored in the synchronization file, the scan and command process receives said specific message, analyzes said specific message, and counts the number of times said specific message appears successively, the scan and command process detecting a network block, and the scan and command process is then automatically interrupted when only said message without other data is received a predetermined successive number of times.

13. A file transfer procedure, to a local system controlling a printer, of a number of files forming reports containing status information from a number of remote systems of a network for printing of said status information on the printer of the local system, wherein associated with each file transfer from a remote system are two synchronization files of the type known as "pipes", the first pipe in a direction from the local system to one of the remote systems, and the second pipe in a direction from one of the remote systems to the local system, said synchronization files creating an automaton for retrieval of multiple reports providing primarily synchronization and communication between:

a scan and command process initiated on the local system, the scan and command process monitoring the associated remote system and sending the remote system a command for the report to be transmitted, and a file transfer process by which the status information to be printed is sent from the remote system to the local system, wherein said file transfer procedure comprises the steps of;

the scan and command process querying the file transfer process to obtain the names of the reports to be transferred to the local system for printing and sends a message containing a request for a report name, said request containing data which allows obtaining the name of the mail box of the remote system whereby the name of the desired report is found;

the file transfer process, in response to the request, examining said mail box in order to send, if the mail box is empty, a specific message to the local system and, if the mail box is not empty, to send to the local system the data relating to the name of the report with the report'"'"'s situation on the remote system, and print parameters, said print parameters comprising data which is then used by the scan and command process;

the scan and command process performing the retrieval of the waiting report, then storing the retrieved report on a receiving disk of the local system under a directory intended for the local system; and

initiating a print command for the printing of the report on the desired printer of the local system.

14. A file transfer procedure according to claim 13, wherein associated with each scan is a scan configuration file comprising:

parameters for a name of the local system,

a name of the remote system scanned,

a name of a mail box scanned,

a time the scan begins,

a name of a status retrieval disk, and

parameters of the reports to be retrieved.

15. A file transfer procedure according to claim 14, wherein the scan and command process begins by reading the appropriate scan configuration file to learn the data necessary for the scan, the data includes the name of the remote system to be monitored and the name of the mail box in which the desired report is stored, the scan and command process then enters a first loop, wherein the scan and command process:

communicates with the remote system through the first synchronization file in which the scan and command process writes the data for the request of the report name,

initiates the command for the specific application for the transmission of the data,

waits to read a response from the remote system, through the second synchronization file, and

enters a second loop, if the response includes a message "mail box empty", wherein the scan and command process;

waits a predetermined time than resends a request, or if the answer includes the name of the report to be retrieved requests transfer of the name of the report through the first synchronization file by means of the specific application,

retrieves this report which is stored in an appropriate directory, and

initiates a print command.

16. A file transfer procedure according to claim 15, wherein the file transfer process in a preliminary monitoring phase:

waits for a message coming from the local system through the first synchronization file,

enters a loop when it detects the arrival of the message, and

reads the information containing, among other items, the name of the mail box in which the report to be retrieved must be stored and the name of the local system waiting for the report to be retrieved, the file transfer process then reads in the appropriate mail box if the desired report is stored there, and issues a response by means of the specific application through the second synchronization file,

if the mail box is empty an error code is provided and the file transfer process sends the local system a message "mail box empty" and,

if the mail box is not empty, after receiving the data pertaining to the name of the desired report with the status report'"'"'s exact location and print parameters, the file transfer process sends the local system said data concerning the status report to be retrieved.

17. A file transfer procedure according to claim 16, wherein the file transfer procedure further comprises:

a stop process used locally to interrupt one or more scans, and

a stop message being written in the synchronization file of a specific scan for each of the scans to be interrupted.

18. A file transfer procedure according to claim 17, wherein the file transfer procedure further comprises:

a process for monitoring the automaton and for unblocking the local system in the event of a network problem;

the process issuing locally, at each predetermined interval throughout the application of the procedure, a specific message stored in the synchronization file, the scan and command process receives said specific message, analyzes said specific message, and counts the number of times said specific message appears successively, the scan and command process detecting a network block, and the scan and command process is then automatically interrupted when only said message without other data is received a predetermined successive number of times.