Patent Description:
An image forming apparatus interrupts a print job when an abnormality, such as a paper jam, that makes printing unable to continue occurs during execution of the print job. Then, when the abnormality is resolved, the interrupted print job is restarted.

When a user leaves the image forming apparatus after requesting the execution of the print job, if the print job is interrupted due to the occurrence of the abnormality described above, another user may perform work for resolving the abnormality. The interrupted print job is then restarted. In this case, there is a concern that the user who resolved the abnormality may take printed matter of another user from the image forming apparatus.

Under these circumstances, the image forming apparatus that can prevent the printed matter from being handed over to the hands of a user other than the user associated with the print job is preferred.

<CIT>, <CIT>, and <CIT> describe an image processing or forming apparatus in the related art. In <CIT> an image processing apparatus is configured to execute a job requested by a user. The apparatus includes: a notifying section configured, when execution of the job is interrupted and an uncompleted job is generated, to notify the execution state of the job to a terminal apparatus of the requesting user of the uncompleted job; and a permitting section configured to permit an operation to perform the notification.

The present invention is defined by independent claims, and advantageous embodiments are described in dependent claims.

At least one embodiment provides an image forming apparatus that can prevent printed matter produced by a print job from being handed over to a user different from a user associated with the print job and a control method thereof.

In general, according to at least one embodiment, an image forming apparatus including a stop unit (e.g., a stop device), a setting unit (e.g., a setting device), and a restart unit (e.g., a restart device) is provided. The stop unit is configured to stop a print job in progress if there is an occurrence of an abnormality that makes the print job unable to continue. The setting unit is configured to set the print job stopped by the stop unit to a skip state. The restart unit is configured to restart the print job set to the skip state by the setting unit according to a restart instruction by a user associated with the print job and not to receive the restart instruction by a second user different from the original user associated with the print job.

Hereinafter, an example of at least one embodiment will be described with reference to the accompanying drawings. In at least one embodiment, a multifunction peripheral (MFP) having a function as an image forming apparatus will be described as an example.

<FIG> is a block diagram illustrating a circuit configuration of a main part of an MFP <NUM> according to at least one embodiment.

The MFP <NUM> includes a processor <NUM>, a main memory <NUM>, an auxiliary storage unit <NUM> (e.g., an auxiliary memory), an operation and display unit <NUM> (e.g., an operation and display device), a scan unit <NUM> (e.g., a scanner), a print unit <NUM> (e.g., a printer), a facsimile unit <NUM> (e.g., a facsimile machine), a communication unit <NUM> (e.g., a communication device or interface), a transmission line <NUM>, and the like. The processor <NUM>, the main memory <NUM>, the auxiliary storage unit <NUM>, the operation and display unit <NUM>, the scan unit <NUM>, the print unit <NUM>, the facsimile unit <NUM>, and the communication unit <NUM> are connected through the transmission line <NUM>.

A computer that performs information processing for controlling the MFP <NUM> is configured by connecting the processor <NUM>, the main memory <NUM>, and the auxiliary storage unit <NUM> through the transmission line <NUM>.

The processor <NUM> corresponds to a central part of the computer. The processor <NUM> executes information processing (e.g., by executing instructions stored in the main memory <NUM>) for controlling one or more parts of the computer in order to realize various functions as the MFP <NUM> according to an information processing program such as an operating system and an application program.

The main memory <NUM> corresponds to a main memory portion of the computer. The main memory <NUM> includes a non-volatile memory area and a volatile memory area. The main memory <NUM> stores the information processing program described above in the non-volatile memory area. The main memory <NUM> may store data necessary for the processor <NUM> to execute a process for controlling each part in the non-volatile or volatile memory area. In the main memory <NUM>, the volatile memory area is used as a work area where data is appropriately rewritten by the processor <NUM>.

The auxiliary storage unit <NUM> corresponds to an auxiliary storage portion of the computer. As the auxiliary storage unit <NUM>, for example, an electric erasable programmable read-only memory (EEPROM), a hard disk drive (HDD), a solid state drive (SSD), or various other well-known storage devices can be used. The auxiliary storage unit <NUM> stores data used by the processor <NUM> for performing various processes and data generated by the processes in the processor <NUM>. The auxiliary storage unit <NUM> may store the information processing program described above. A part of the storage area of the auxiliary storage unit <NUM> is used as an area for storing a job management table TAA. The job management table TAA is a data table for managing a print job (hereinafter referred to as an uncompleted job) that is not completed. The uncompleted job is a print job in a start waiting state. Alternatively, the uncompleted job is a print job that was started once but skipped.

<FIG> is a table schematically illustrating a configuration of a data record DRA included in the job management table TAA.

The job management table TAA includes the data record DRA with which the uncompleted job is associated. The data record DRA includes fields FAA, FAB, FAC, FAD, FAE, FAF, and FAG. In the field FAA, a job identifier (ID) as an identifier of the uncompleted job is set. In the field FAB, the date and time when the uncompleted job was generated is set. In the field FAC, a user ID of the user associated with the uncompleted job is set. In the field FAD, a file path of an image file representing an image to be printed by the uncompleted job is set. In the field FAE, data representing a state of the uncompleted jobs is set. In the field FAF, the date and time when the uncompleted job was skipped is set in the field FAF. In the field FAG, data indicating in which state the uncompleted job is skipped is set.

The operation and display unit <NUM> inputs an operation by the user and displays various information for presenting to the user. The operation and display unit <NUM> may appropriately include various operation devices and display devices such as a touch panel, a keyboard, a key switch, an LED lamp, or a liquid crystal display panel.

The scan unit <NUM> reads a document and generates image data of an image displayed on the document.

The print unit <NUM> prints the image represented by the image data on recording paper. The print unit <NUM> includes a well-known print device such as an electrophotographic image forming device.

The facsimile unit <NUM> performs various well-known processes for performing image communication conforming to a facsimile standard through a communication network (not illustrated) such as a public switched telephone network (PSTN).

The communication unit <NUM> executes a communication process for performing data communication through a communication network <NUM>. For example, an existing communication device for a local area network (LAN) can be used as the communication unit <NUM>.

The communication network <NUM> may be the Internet, virtual private network (VPN), LAN, public communication network, mobile communication network, and the like, used alone or in an appropriate combination. , For example, the LAN is used as s the communication network <NUM>.

A computer terminal <NUM> is an information processing device having a function of data communication through the communication network <NUM>. The computer terminal <NUM> is, for example, an information terminal for requesting the MFP <NUM> to execute the print job through the communication network <NUM>.

Next, an operation of the MFP <NUM> configured as described above will be described. The contents of the processes described below are examples, and it is possible to appropriately change the order of some processes, omit some processes, or add another process.

In the MFP <NUM>, the processor <NUM> controls each part of the MFP <NUM> in order to control a print function, a copy function, a scan function, a facsimile function, and the like in the same manner as those performed by the existing the MFP of the same type. The description of information processing for this control will be omitted. In the following, the management of print jobs will be described.

When the processor <NUM> is started in an operation mode that enables the print job to be executed, the processor <NUM> executes information processing (hereinafter referred to as a management process) based on the information processing program stored in the main memory <NUM> or the auxiliary storage unit <NUM>.

<FIG> and <FIG> are flowcharts of the management process.

As ACT <NUM> in <FIG>, the processor <NUM> waits for a login request by a user.

When a user intends to request the MFP <NUM> to execute some function accompanied by a print job, the user requests login by, for example, a predetermined operation in the operation and display unit <NUM>. In response to this request, the processor <NUM> determines that the result in ACT <NUM> is YES and proceeds to ACT <NUM>. The functions accompanied by the print job include, for example, the print function, the facsimile function, and the copy function. The print function is a function of printing by the print unit <NUM> in response to a print request through the communication network <NUM>. The facsimile function is a function of printing an image, which is acquired by facsimile communication by the facsimile unit <NUM>, by the print unit <NUM>. The copy function is a function of printing an image, which is obtained by scanning a document with the scan unit <NUM>, by the print unit <NUM>.

As ACT <NUM>, the processor <NUM> performs an authentication process for authenticating the user who requested the login. For example, the processor <NUM> allows the user to input the user ID and a password, and authenticates the user as a user who is associated with a combination of the user ID and the password. Alternatively, the processor <NUM> authenticates the user, for example, based on authentication information read from an ID card by a card reader (not illustrated). The user authentication method may be any method such as other well-known methods.

In ACT <NUM>, the processor <NUM> checks whether or not the authentication in ACT <NUM> is successful. Then, if the authentication fails, the processor <NUM> determines that the result in ACT <NUM> is NO and returns to a waiting state of ACT <NUM>. In this case, the processor <NUM> may execute a notification operation such as causing a screen to display information for notifying the user that the authentication fails on the operation and display unit <NUM>. The processor <NUM> may also return to ACT <NUM>.

If the authentication is successful, the processor <NUM> determines that the result in ACT <NUM> is YES and proceeds to ACT <NUM>.

As ACT <NUM>, the processor <NUM> checks whether or not the print unit <NUM> can start print. Then, if the processor <NUM> cannot start print, the processor <NUM> determines that the result in ACT <NUM> is NO and proceeds to ACT <NUM>.

As ACT <NUM>, the processor <NUM> checks whether or not a logout is instructed. Then, if the corresponding instruction cannot be checked, the processor <NUM> determines that the result in ACT <NUM> is NO and returns to ACT <NUM>.

Thus, as ACT <NUM> and ACT <NUM>, the processor <NUM> waits for the start of print to be possible or logout to be instructed. In this case, the processor <NUM> may execute the notification operation such as generating a notification on a screen for notifying the user that print cannot be started to be displayed on the operation and display unit <NUM>.

If the user gives up the execution of the print job, the user instructs the logout by a predetermined operation or the like in the operation and display unit <NUM>. Then, the processor <NUM> determines that the result in ACT <NUM> is YES and proceeds to ACT <NUM>.

As ACT <NUM>, the processor <NUM> logs out the logged-in user. Then, the processor <NUM> returns to the waiting state of ACT <NUM>.

Now, if the print unit <NUM> can start print, the processor <NUM> determines that the result in ACT <NUM> is YES and proceeds to ACT <NUM> in <FIG>.

As ACT <NUM>, the processor <NUM> checks whether or not an uncompleted job is present. Then, if the uncompleted job is not present, the processor <NUM> determines that the result in ACT <NUM> is NO and proceeds to ACT <NUM>.

As ACT <NUM>, the processor <NUM> checks whether or not the start of a new print job is instructed. Then, if the corresponding instruction cannot be checked, the processor <NUM> determines that the result in ACT <NUM> is NO and proceeds to ACT <NUM>.

As ACT <NUM>, the processor <NUM> checks whether or not logout is instructed. Then, if the corresponding instruction cannot be checked, the processor <NUM> determines that the result in ACT <NUM> is NO and returns to ACT <NUM>.

Thus, as ACT <NUM> or ACT <NUM>, the processor <NUM> waits for an instruction to start or logout made.

Now, when a new function accompanied by a print job is requested, the processor <NUM> executes an update process for updating the job management table TAA for managing a print job (hereinafter referred to as a new job) for the function separately from the management process. Then, in the update process, the processor <NUM> adds a new data record DRA associated with the requested print job to the job management table TAA. The processor <NUM> sets each data in each field of this new data record DRA as follows.

The processor <NUM> determines a new job ID and sets the new job ID in the field FAA so that the new job can be distinguished from one or more other print jobs.

The processor <NUM> sets, for example, the date and time when the data record DRA is generated in the field FAB. The processor <NUM> may set the date and time at another optional time point, such as the time point when an event that triggered generation of a new job occurs, in the field FAB.

When the user ID can be specified, the processor <NUM> sets the user ID in the field FAC. For example, when the new job is related to the print function, the processor <NUM> sets the user ID of a requester in the field FAC when the user ID of the requester can be acquired. For example, when the new job is related to the facsimile function, the processor <NUM> sets a user ID of a recipient in the field FAC when the recipient is designated. For example, when the new job is related to the copy function, the processor <NUM> sets the user ID of the logged-in user in the field FAC. When the user ID cannot be specified, the processor <NUM> sets predetermined invalid data in the field FAC. When the user ID cannot be specified, the processor <NUM> may leave the field FAC in a blank state.

The processor <NUM> sets a file path of the image file to be printed in the new job in the field FAD. The processor <NUM> stores, for example, an image file including image data transmitted along with a request for the print function or the facsimile function and received by the facsimile unit <NUM> or the communication unit <NUM> in the auxiliary storage unit <NUM>, and sets the file path of the image file in the field FAD. For example, in the case of a request for the copy function, the processor <NUM> determines the file path for the image file including the image data obtained by the scan unit <NUM> and sets the file path in the field FAD.

The processor <NUM> sets data indicating that the print job is in the start waiting state in the field FAE.

The processor <NUM> sets predetermined invalid data in the fields FAF and FAG. The processor <NUM> may leave the fields FAF and FAG in the blank state. The processor <NUM> may not include the fields FAF and FAG in the data record DRA generated here.

The processor <NUM> adds the data record DRA to the job management table TAA whenever a new job occurs even in the state where an uncompleted job exists. Thus, the job management table TAA does not include any data record DRA if there is no uncompleted job. The job management table TAA includes only one data record DRA if only one uncompleted job is present. The job management table TAA includes a plurality of data records DRAs associated with a plurality of uncompleted jobs, respectively, when the plurality of uncompleted jobs exist.

For example, if the job management table TAA includes at least one data record DRA, the processor <NUM> determines that an uncompleted job is present and determines that the result in ACT <NUM> in <FIG> is YES and proceeds to ACT <NUM>.

As ACT <NUM>, the processor <NUM> causes a list screen, for example, to be displayed on the operation and display unit <NUM>. The list screen represents a list of uncompleted jobs, and is a screen for allowing the user to designate a print job to be executed from among the uncompleted jobs. For example, the processor <NUM> extracts a data record DRA in which the user ID set in the field FAC matches the user ID of the logged-in user, and a data record DRA in which invalid data is set in the field FAC, from the data records DRA included in the job management table TAA. Then, the processor <NUM> shows the uncompleted jobs with which the data record DRA extracted in this way is associated in the list.

The user determines one of the uncompleted jobs displayed on the list screen as a print job to be executed, and designates the uncompleted job by, for example, a predetermined operation in the operation and display unit <NUM>. Alternatively, if the user instructs the start of a new print job that is not an uncompleted job in order to use the copy function or the like, the user instructs the start of the job by, for example, a predetermined operation in the operation and display unit <NUM>.

As ACT <NUM>, the processor <NUM> checks whether or not an uncompleted job to be executed is designated. Then, if the corresponding designation cannot be checked, the processor <NUM> determines that the result in ACT <NUM> is NO and proceeds to ACT <NUM>.

As ACT <NUM>, the processor <NUM> checks whether or not the start of the new print job is instructed. Then, if the corresponding instruction cannot be checked, the processor <NUM> determines that the result in ACT <NUM> is NO and proceeds to ACT <NUM>.

As ACT <NUM>, the processor <NUM> checks whether or not the logout is instructed. Then, if the corresponding instruction cannot be checked, the processor <NUM> determines that the result in ACT <NUM> is NO and returns to ACT <NUM>.

Thus, as ACT <NUM> to ACT <NUM>, the processor <NUM> waits for a print job to be designated, or to be instructed to start or log out.

If the user designates one of the uncompleted jobs as described above, the processor <NUM> determines that the result in ACT <NUM> is YES and proceeds to ACT <NUM>. If the start of the print job is instructed as described above, the processor <NUM> determines that the result in ACT <NUM> or ACT <NUM> is YES, and proceeds to ACT <NUM>.

As ACT <NUM>, the processor <NUM> starts execution of the designated uncompleted job or the instructed new print job. The processor <NUM> instructs the print unit <NUM> to start print, for example, accompanied by designation of a target image file. The processor <NUM> designates the image file, for example, by notifying the file path set in the field FAD of the data record DRA associated with the uncompleted job or the instructed new print job. When the copy function is required, the processor <NUM> instructs the scan unit <NUM> to start scanning accompanied by the notification of the above file path.

When the print function or facsimile function is required, the print unit <NUM> prints an image based on the image data included in the image file specified by the notified file path.

When the copy function is requested, the scan unit <NUM> scans the set document to generate image data and stores the image data in the auxiliary storage unit <NUM> as an image file specified by the notified file path described above. The print unit <NUM> prints an image based on the image data included in the image file specified in the notified file path, that is, the image file stored in the auxiliary storage unit <NUM> as described above.

As ACT <NUM>, the processor <NUM> checks whether or not the print job under execution is completed. Then, if the completion of the print job cannot be checked, the processor <NUM> determines that the result in ACT <NUM> is NO and proceeds to ACT <NUM>.

As ACT <NUM>, the processor <NUM> checks whether or not the print unit <NUM> is stopped abnormally. Then, if the abnormal stop cannot be checked, the processor <NUM> determines that the result in ACT <NUM> is NO and returns to ACT <NUM>.

Thus, as ACT <NUM> and ACT <NUM>, the processor <NUM> waits for the completion or abnormal stop of the print job.

When the print unit <NUM> completes print based on all the image data included in the image file specified by the notified file path, the print unit <NUM> notifies the processor <NUM> of the completion of print. However, the print unit <NUM> stops the print operation when print cannot be continued due to some abnormality such as a paper jam or running-out of paper. Then, in this case, the print unit <NUM> notifies the processor <NUM> of the abnormal stop. In this way, the print unit <NUM> has a function as a stop unit.

When the completion of print is notified as described above, the processor <NUM> determines that the result in ACT <NUM> is YES, returns to ACT <NUM>, and repeats the subsequent actions in the same manner as described above.

When the abnormal stop is notified as described above, the processor <NUM> determines that the result in ACT <NUM> is YES and proceeds to ACT <NUM>.

As ACT <NUM>, processor <NUM> interrupts the print job under execution.

As ACT <NUM>, the processor <NUM> sets the interrupted print job to a skip state. The processor <NUM> rewrites, for example, the field FAE of the data record DRA associated with the interrupted print job with data representing the skip state. The processor <NUM> rewrites, for example, the field FAF of the data record DRA associated with the interrupted print job with the current date and time. For example, the processor <NUM> rewrites the field FAG of the data record DRA associated with the interrupted print job with data indicating how far the interrupted print job is completed. Thus, the computer having the processor <NUM> as a central part functions as a skipping unit (e.g., a skipping device) by executing information processing based on the information processing program by the processor <NUM>.

The processor <NUM> then proceeds to ACT <NUM>. When the processor <NUM> is in the waiting state of ACT <NUM> or ACT <NUM>, or in the waiting state of ACT <NUM> to ACT <NUM>, if the logout instructed, for example, by a predetermined operation in the operation and display unit <NUM> by the user, the processor <NUM> determines that the result in ACT <NUM> or ACT <NUM> is YES, and proceeds to ACT <NUM>.

As ACT <NUM>, the processor <NUM> logs out. Then, the processor <NUM> returns to the waiting state of ACT <NUM> in <FIG>.

When the processor <NUM> proceeds to ACT <NUM> from ACT <NUM>, the processor <NUM> releases an operated state in which the user authenticated by the authentication process in ACT <NUM> in <FIG> is the operator according to the abnormal stop of the print job. Then, the processor <NUM> sets this operated state according to the success of the authentication process in ACT <NUM> in <FIG>. Thus, the computer having the processor <NUM> as the central part functions as an operator management unit (e.g. an operator management device) by executing information processing based on the information processing program by the processor <NUM>.

When the processor <NUM> returns to the waiting state of ACT <NUM> in <FIG> through ACT <NUM> in <FIG>, the interrupted print job is left as the uncompleted job in the skip state. In this case, the processor <NUM> logs out without a logout instruction by the user, and shifts to a state of waiting for a new login request. Thus, even if the abnormality that caused the abnormal stop is resolved and the print unit <NUM> is in a state where print can be stated, the processor <NUM> does not print the interrupted print job.

Then, the print job in the skip state is included as one of the uncompleted jobs in the list displayed on the list screen displayed by ACT <NUM> in <FIG>, and the processor <NUM> enables the print job in the skip state to be designated as the print job to be executed. Then, when the print job in the skip state is designated by the user, the processor <NUM> instructs the print unit <NUM> to perform the print operation following the previous interruption based on the data which is set in the field FAG of the data record DRA with which the print job is associated. When the processor <NUM> executes information processing based on the information processing program in this way, the computer having the processor <NUM> as the central part functions as a restart unit.

The processor <NUM> executes information processing (hereafter referred to as a deletion process) based on the information processing program stored in the main memory <NUM> or the auxiliary storage unit <NUM> separately from the update process and management process described above every time a predetermined execution timing is reached. The execution timing may be optionally determined by the designer or administrator of the MFP <NUM>. As an example, the execution timing is assumed to be the timing at regular time intervals such as every <NUM> hours, the timing when a free capacity of the auxiliary storage unit <NUM> becomes equal to or less than a predetermined threshold value, and the like.

<FIG> is a flowchart of the deletion process.

As ACT <NUM>, the processor <NUM> checks whether or not an uncompleted job that is not selected is present in this deletion process. For example, when the processor <NUM> first proceeds to ACT <NUM> after the start of the deletion process, if the job management table TAA includes at least one data record DRA, the processor <NUM> determines that an unselected uncompleted job is present. Then, if there is an uncompleted job that is not selected, the processor <NUM> determines that the result in ACT <NUM> is YES and proceeds to ACT <NUM>.

As ACT <NUM>, the processor <NUM> selects one uncompleted job.

As ACT <NUM>, the processor <NUM> checks whether or not the selected uncompleted job is in the skip state. For example, if the data, which is set in the field FAG of the data record DRA with which the selected uncompleted job is associated, represents the skip state, the processor <NUM> determines that the selected uncompleted job is in the skip state. Then, if the selected uncompleted job is in the skip state, the processor <NUM> determines that the result in ACT <NUM> is YES and proceeds to ACT <NUM>.

As ACT <NUM>, the processor <NUM> checks whether or not a holding period for the selected uncompleted job is ended. For example, if the elapsed time from the date and time, which is set in the field FAF of the data record DRA associated with the selected uncompleted job, is equal to or longer than a predetermined time limit for the selected uncompleted job, the processor <NUM> determines that the holding period is ended. Then, if the holding period is ended, the processor <NUM> determines that the result in ACT <NUM> is YES and proceeds to ACT <NUM>.

As ACT <NUM>, the processor <NUM> erases the selected uncompleted job. The processor <NUM> deletes, for example, the data record DRA associated with the uncompleted job from the job management table TAA. The processor <NUM> then returns to ACT <NUM>. Thus, by executing information processing based on the information processing program by the processor <NUM>, the computer having the processor <NUM> as the central part functions as an exclusion unit (e.g., an exclusion device).

The processor <NUM> determines that the result in ACT <NUM> is NO if the selected uncompleted job is not in the skip state and the result in ACT <NUM> is NO if the holding period for the selected uncompleted job is not ended, and in either case, the processor passes ACT <NUM> and returns to ACT <NUM>. That is, the processor <NUM> does not erase the uncompleted jobs that are not in the skip state and the uncompleted jobs whose holding periods are not ended.

Now, when the processor <NUM> returns to ACT <NUM> from any of ACT <NUM>, ACT <NUM>, and ACT <NUM>, the processor <NUM> checks whether or not there are uncompleted jobs excluding the uncompleted jobs already selected when ACT <NUM> was executed so far in this deletion process. Then, when the processor <NUM> proceeds to ACT <NUM> because there are corresponding uncompleted jobs, the processor <NUM> selects one of the uncompleted jobs excluding the uncompleted jobs already selected when ACT <NUM> was executed so far. That is, the processor <NUM> executes ACT <NUM> to ACT <NUM> in the same manner as described above while sequentially targeting each of the uncompleted jobs. With this configuration, the processor <NUM> excludes the uncompleted job in the skipped state whose holding period is ended from the uncompleted jobs.

After executing ACT <NUM> to ACT <NUM> targeted for all uncompleted jobs as described above, the processor <NUM> determines that the result in ACT <NUM> is NO and ends the deletion process.

As described above, according to the MFP <NUM>, the print job stopped abnormally is set to the skip state, and even if the abnormality is resolved, the print job is not automatically restarted. Then, the print job in the skip state is restarted according to an execution instruction by the user associated with the print job. The print job in the skipped state is not targeted for an execution instruction by a user other than the user associated with the print job, and is not restarted according to an instruction by such another user. Accordingly, the print job cannot be restarted without the involvement of the user associated with the print job, and the printed matter produced by the print job can be prevented from being handed over to another user.

According to the MFP <NUM>, after the abnormally stopped print job is in the skip state, an execution instruction for another print job is received and the other print job can be started according to such an instruction. Accordingly, another job can be executed without waiting for the abnormally stopped print job to be restarted and completed.

According to the MFP <NUM>, the print job stopped abnormally is set to the skip state, and the interrupted state of the print job is promptly resolved. With this configuration, even if power saving control is performed so as not to shift to a power saving state in the interrupted state of the print job, it is possible to shift to the power saving state without waiting for the abnormally stopped print job to be restarted and completed.

In the MFP <NUM>, the user is not involved in setting the abnormally stopped print job to the skip state. For that reason, there is a concern that the print job in the skip state may be left unattended for a long time. However, the MFP <NUM> excludes the print job in the skip state whose holding period is ended from the uncompleted jobs. With this configuration, the print job left unattended as described above can be prevented from being accumulated in the uncompleted jobs.

At least one embodiment can be implemented by being modified in various ways as follows.

Similar implementation is possible in various devices with print functions, such as printers, facsimile machines, or copiers.

The processor <NUM> may restart an uncompleted job associated with a user other than the instructor according to an instruction from an administrator or the like having special authority.

The processor <NUM> does not need to perform the deletion process. Alternatively, the processor <NUM> may perform the deletion process when the deletion process is set to be performed by the administrator of the MFP <NUM> or the like.

The processor <NUM> may automatically cause the job with which the user is not associated to be restarted after the abnormality is resolved without setting the job to the skip state.

In examples not covered by the claimed invention, after setting the job to the skip state in ACT <NUM> in <FIG>, the processor <NUM> may not shift directly to ACT <NUM>, but may shift to ACT <NUM> upon receiving a logout instruction or upon the lapse of a predetermined wait time.

Claim 1:
An image forming apparatus (<NUM>) comprising:
a processor (<NUM>) configured to:
set an operated state by a logged-in user in response to successful authentication of a user who requested login as the logged-in user;
stop a print job under execution and set the stopped print job to a skip state in response to an occurrence of an abnormality preventing the print job from continuing;
restart the print job set to the skip state in response to a restart instruction in the operated state by the logged-in user who is associated with the print job set to the skip state and not in an operated state by a second user different than the user associated with the print job set to the skip state; and
directly in response to setting the stopped print job to the skip state, log out to release the operated state by the logged-in user and shift to a waiting state for a new login request.