JP4854363B2 - Data item verification program - Google Patents

Description

  The present invention relates to a data item verification program, and more particularly to a data item verification program for data items on an input screen in which at least some data items can be hidden.

In an application for inputting or referring to many data items, if all data items are displayed, it becomes difficult to find necessary data items (frequently input or referenced) on the screen. May end up. Thus, some of these applications allow user settings so that data items that are not normally used can be hidden on the screen (for example, Patent Document 1).
Japanese Patent Laid-Open No. 2001-166864

However, when an error related to a hidden data item occurs, the user must display the data item again in order to re-input or refer to the data item.

  The redisplay of the non-display items is not only troublesome, but there is a problem that it is very complicated to find the data items that are not displayed from many data items.

  The present invention has been made in view of the above points, and in the event that an error occurs with respect to a data item that is not displayed, data item verification that can simplify the confirmation or correction of the data item The purpose is to provide a program.

  Therefore, in order to solve the above-described problem, the present invention provides a computer with values of the plurality of data items when at least some of the data items are hidden on an input screen on which a plurality of data items can be input. A verification procedure for executing the verification, a determination procedure for determining whether or not a data item in which an error is detected in the verification procedure is hidden on the input screen, and a data item in which the error is detected When it is determined that the data item is displayed, a data item display procedure for automatically displaying the data item on the input screen is executed.

  In such a data item verification program, when an error occurs with respect to a data item that is not displayed, it is possible to simplify the confirmation or correction of the data item.

  ADVANTAGE OF THE INVENTION According to this invention, when an error generate | occur | produces about the data item made into non-display, the data item verification program which can simplify the confirmation or correction work of the said data item can be provided.

  Hereinafter, embodiments of the present invention will be described with reference to the drawings.

  FIG. 1 is a diagram illustrating a hardware configuration example of a job schedule creation device according to an embodiment of the present invention. The job schedule creation device 10 in FIG. 1 is a device for allowing a user to input schedule information of a batch job to be executed in another computer (not shown) (hereinafter referred to as “job execution server”). The drive device 100, the auxiliary storage device 102, the memory device 103, the arithmetic processing device 104, the display device 105, and the input device 106 are connected to each other.

  A job schedule creation program 11 for realizing the functions of the job schedule creation apparatus 10 is provided by a recording medium 101 such as a CD-ROM. When the recording medium 101 on which the job schedule creation program 11 is recorded is set in the drive device 100, the job schedule creation program 11 is installed from the recording medium 101 to the auxiliary storage device 102 via the drive device 100. The auxiliary storage device 102 stores the installed job schedule creation program 11 and also stores necessary files and data.

  The memory device 103 reads the job schedule creation program 11 from the auxiliary storage device 102 and stores it when there is an instruction to start the job schedule creation program 11. The arithmetic processing unit 104 implements functions related to the job schedule creation device 10 according to the job schedule creation program 11 stored in the memory device 103. The display device 105 displays a GUI (Graphical User Interface) or the like by the job schedule creation program 11. The input device 106 includes a keyboard and a mouse, and is used for inputting various operation instructions.

  The job schedule creation program 11 need not always be installed from the recording medium 101, and may be downloaded from another computer via a network (not shown).

  By the way, in the job schedule creation program 11 in the present embodiment, it is possible to create and edit a schedule in units of “job nets”. In the present embodiment, a job net refers to a set of one or more related jobs.

  FIG. 2 is a diagram illustrating a display example of a batch edit sheet displayed by the job schedule creation program.

  In FIG. 2, a batch edit sheet 200 is a sheet (screen) for editing the schedule information of the job net. In the batch edit sheet 200, one row corresponds to one job net, and data items related to job net attribute information 211, start condition 212, operation period 213, and the like are input for each row, that is, for each job net. It is configured as follows. In the present embodiment, each data item is referred to as an “operand”.

  For example, as the attribute information 211, it is possible to input operands related to a job net name, a job net name, the number of jobs in the job net, and execution attributes. The activation condition 212 and the operation period 213 are also composed of a large number of operands. Therefore, the user can schedule each job net by inputting these operands for each job net.

  FIG. 3 is a diagram illustrating a display example of a batch edit sheet to which a job net is input. In FIG. 3, the same parts as those of FIG.

  In FIG. 3, in the batch edit sheet 200, “job net name”, “job net name”, “number of jobs in job net”, “single / multiple activation”, and “expiration start date” of three job nets. An example is shown in which values are entered in operands such as. It is assumed that 300 job nets can be defined in the batch edit sheet 200 in the present embodiment. The value of each operand can be read from a CSV file created in advance by clicking the CSV input button 203.

  In FIG. 2 and FIG. 3, etc., some operands of the start condition 212 and columns related to operands constituting information other than the attribute information 211, the start condition 212, and the operation period 213 are omitted for convenience. In the batch edit sheet 200, the shaded portion indicates an input-protected area and cannot be input by the user.

  When the user clicks a cell related to the job information column 214 in a row of an arbitrary job net in the batch edit sheet 200, the job schedule creation program 11 causes the display device 105 to display the job information sheet related to the job net.

  FIG. 4 is a diagram illustrating a display example of a job information sheet. In FIG. 4, a job information sheet 300 is a sheet for inputting an operand for each job belonging to a job net in which a cell related to the job information column 214 is clicked in the batch edit sheet 200. Therefore, the user displays the job information sheet 300 for each job net, and inputs the operand of the job belonging to each job net. In the present embodiment, it is assumed that a maximum of 255 jobs can belong to one job net. Therefore, in the job information sheet 300, it is possible to input about 255 lines.

  Note that information input to the job information sheet 300 is associated with the job net and managed on the memory (memory device 103).

  By the way, in the batch edit sheet 200 and the job information sheet 300, since many operands are displayed, the visibility of each operand deteriorates. Therefore, in the batch edit sheet 200, a column related to an arbitrary operand can be hidden.

  For example, when the setting sheet display button 220 is clicked on the batch edit sheet 200, the job schedule creation program 11 displays a setting sheet for setting display or non-display of each operand on the batch edit sheet 200.

  FIG. 5 is a diagram illustrating a display example of the setting sheet. As shown in FIG. 5, in the setting sheet 400, display or non-display setting on the batch edit sheet 200 can be set in the “display” item provided for each operand of the job net. That is, an operand whose value of the “display” item is “◯” is displayed, and an operand whose value is “x” is not displayed. In the figure, operands such as “calendar name 5”, “shift upper limit days”, and “expiration end date” are “x”. In this case, for example, the “expiration date end date” that should be displayed between the “expiration date start date” and the “invalid expiration date” is not displayed. 2 and 3 show this state. That is, in FIG. 2 and FIG. 3, the “expiration end date” is not displayed between the expiry date start date column 2131 and the invalid expiry date start date column 2133.

  In the setting sheet 400, the column position (hereinafter referred to as “column symbol”) on the batch edit sheet 200 is registered in the “column” item for each operand. For example, if it is an expiration date, the column symbol is registered as “FA: FA”. However, since the setting sheet 400 is mainly for setting display or non-display of each operand, the column in which the “column” item is registered is normally hidden.

  The job information sheet 300 can be set to display or not display each operand using the same user interface as the setting sheet 400.

  A user who has entered values of each operand related to a job net and a job in the batch edit sheet 200 and the job information sheet 300 can verify the validity of the input values by clicking the operand check button 204 of the batch edit sheet 200. it can. That is, when the operand check button 204 is clicked, the job schedule creation program 11 executes the processing shown in FIG.

  FIG. 6 is a flowchart for explaining the processing outline of processing executed by the job schedule creation program when the operand check button is pressed.

  First, the sheet name indicating the operand check target is reset to the sheet name of the batch edit sheet 200 on which the operand check button 204 is clicked (S11), and the batch edit sheet 200 is selected as the check target (S12). Subsequently, the input event for the batch edit sheet 200 is invalidated (S13), and updating of the operand value on the sheet is suppressed (S14). Subsequently, the validity of each operand value input to the batch edit sheet 200 and the job information sheet 300 (hereinafter referred to as “operand check process”) is executed (S15).

  If there is an error in the operand value as a result of the check (Y in S15), the suppression of the update of the operand value on the batch edit sheet 200 is canceled (S17), and the input event is validated (S18). Thereby, the value of the operand on the batch edit sheet 200 can be corrected.

  On the other hand, if there is no error (N in S15), input protection is applied to the batch edit sheet 200 so that it is not updated by the user (S19).

  FIG. 7 is a diagram showing a display example of the batch edit sheet when there is no error in the operand check.

  In FIG. 7, the batch edit sheet 200 has limited input protection for all cells except the print-designated column 215 (as described above, the shaded portion is input-protected in the figure). Showing). By applying the input protection, it is possible to prevent the operand from being updated due to a user's erroneous operation or the like when there is no error in the input of the operand.

  When there is no error in the operand check, the CSV input button 203 displayed in FIGS. 2 and 3 is switched to the CSV output button 205. When the CSV output button 205 is clicked in the state of FIG. 7, the job schedule creation program 11 switches the display format of the batch edit sheet 200 as shown in FIG.

  FIG. 8 is a diagram illustrating a display example of the batch edit sheet when the CSV output button is pressed. As shown in FIG. 8, when the CSV output button 205 is clicked, a folder name column 215 and a file name column 216 that are hidden cells in the batch edit sheet 200 are newly displayed. The folder name column 215 and the file name column 216 are areas for designating the output destination of the setting contents (setting values for the operands of each job net) in the batch edit sheet 200 for each job net. In other words, the job schedule creation program 11 outputs the setting contents for each job net in the CSV format to the file specified in the cell according to the folder name column 215 and the file name column 216 of the job net.

  Next, details of the operand check process in step S15 in FIG. 6 will be described.

  FIG. 9 is a flowchart for explaining the procedure of the operand check process.

  First, as an initialization process, the colors of all the cells of the batch edit sheet 200 are made colorless (S101). As will be described later, for the operand in which an error is detected in the operand check process, the color of the cell of the operand is changed in order to improve the visibility of the location. In view of this, in consideration of the case where the cell color has been changed as a result of the previous operand check process, all the cell colors are initialized to colorless.

  Subsequently, in step S103 and subsequent steps, loop processing (that is, loop processing for each job net) for the number of rows of the batch edit sheet 200 is executed (S102). As described above, 300 job nets can be defined in this embodiment. Therefore, the following processing is executed for each of the 300 rows one by one in order from the first row.

  First, one line is extracted, and it is determined whether or not the line (hereinafter referred to as “current line”) has passed the last line (S103). If the current line is not the last line (N in S104), it is determined whether or not the current line is a blank line (a line in which nothing is input) (S105). If the current line is a blank line (Y in S104), it is determined whether or not the current line is a line corresponding to the first job net (S105). In this embodiment, even if there is a line (input line) in which a job net is input after a blank line, the input line is ignored (excluded from being output to a CSV file). . Therefore, if the first job net is a blank line (Y in S105), all lines are excluded from being output to the CSV file. Therefore, in this case, error information is recorded on the memory (S106), and the error location (for example, a blank line) is set to red (S107). Subsequently, a termination process is executed (S115), and the operand check process is terminated. In step S106, error information is recorded using an array of job net error information structures. The job net error information structure is, for example, a job net No. , Job net name, error ID, error message, and other member variables. When one error is detected, a member variable of the error information structure, which is one element of the array, corresponds to the error. Stores the value.

  On the other hand, if it is determined in step S105 that the current line that is a blank line is not a line corresponding to the first job net (N in S105), a variable (for counting the number of input lines after the blank line) ( Hereinafter, it is determined whether or not the value of “variable A” is 0 (S108). The variable A is initialized to 0 in the initialization process (S101), and is incremented every time an input line is detected after a blank line, as will be described later. Therefore, in step S108, it is determined whether or not an input line has already been detected after the blank line, that is, whether or not an input line that will be ignored has already been detected. If the determination is affirmative (Y in S108), the value of the variable A is set to “1”, and the number of valid job nets (hereinafter referred to as “valid job net number”) is the value of the number of input rows so far. And return to step S103. If this determination is negative (N in S108), the value of variable A returns to step S103 without incrementing.

  On the other hand, if it is determined in step S104 that the current line is not a blank line (an input line) (N in S104), the process proceeds to step S110, and it is determined whether or not the value of the variable A is zero. This determines whether or not the current line as the input line is an input line after the blank line. This is because if the blank line has already been detected before the current line, the value of the variable A is set to 1 at least in step S109.

  If the determination is affirmative, that is, if there is no blank line before the current line (Y in S110), the line number of the current line is held in the memory (S111), and the job net (hereinafter “current” A check process for each operand (hereinafter referred to as “job net check process”) is executed (S112). Details of this processing will be described later. Furthermore, the operands of the jobs belonging to the current job net are checked (S113), and the process returns to step S103. On the other hand, if the determination in step S109 is negative, that is, if there is a blank line before the current line (N in S110), the current line is not subject to output to the CSV file, so the operand is not checked. In step S103, the variable A is incremented. Note that the variable A is used, for example, to display the number of input lines existing after the blank line in the error message after all the lines have been processed.

  When the above process is performed for 300 rows in the batch edit sheet 200 (Y in S103), a finalization process is executed (S115), and the operand check process is terminated. Details of the termination process will be described later.

  Next, the job net check process in step S112 will be described. FIG. 10 is a flowchart for explaining the processing procedure of the job net check processing.

  First, the validity of each operand value of the current job net is checked (S201). The check is also performed on operands that are not displayed (for example, “expiration date” in the case of FIGS. 2 and 3). The validity of the value differs for each operand. Therefore, the contents of the check are also different from each other. For example, in the case of the “expiration date end date”, it is checked whether the description format of the date is in accordance with a predetermined format or whether a date before the “expiration date” is designated.

  If there is an operand whose check result is determined to be an error, the error information is recorded in the job net error information structure array (S203), and the cell address of the operand is stored in the error location storage variable (S204). ).

  FIG. 11 is a diagram illustrating an example of the contents of the error location storage variable. In FIG. 11, a rectangle with a broken line indicated by reference numeral v1 indicates an error location storage variable. As shown in FIG. 11, the error location storage variable v1 is a character string type variable in which cell addresses of operands (error operands) determined to be errors are stored separated by commas (","). That is, in the figure, “$ EB $ 10”, “$ EE $ 10”, and “$ FA $ 10” indicate the cell addresses of the error operands. Therefore, FIG. 11 shows an example in which the cell addresses of three error operands are stored.

  On the other hand, if there is no error for all operands (N in S202), the processes in steps S203 and S204 are not executed.

  In the case of N in step S202 or following step S204, the process proceeds to step S205 to determine whether or not the contents of the error location storage variable v1 are empty. If the content of the error location storage variable v1 is empty (Y in S205), that is, if there is no error for all operands, the job net check process is terminated.

  On the other hand, when the content of the error location storage variable v1 is not empty (N in S205), that is, when the cell address of at least one error operand is stored in the error location storage variable v1, the cell ( The background color of the error cell) is changed to a color that can be easily recognized as an error target (in this embodiment, red) (S206). At this time, the cell related to the job net name of the current job net may be changed to red. By doing so, it is possible to easily recognize a job net including an error operand.

  Subsequently, when an operand that is not displayed is included in the error operand, the column (cell) related to the operand is displayed (recovered) on the batch edit sheet 200 (S207). Furthermore, the background color of the cell of the error operand that has been changed from the non-display state to the display state is changed to a color that allows the error object to be easily recognized (S208). In this case, a color different from red may be used in order to easily recognize that it has not been displayed. In this embodiment, the color is changed to yellow.

  FIG. 12 is a diagram illustrating a display example of a batch edit sheet when an error operand is detected in the job net check process.

  FIG. 12 shows a display example when the job net in the second row is the current job and the “expiration date” is an error. In FIG. 2 and FIG. 3, the “expiration date” is a hidden operand, but in FIG. 12, the expiration date column 2132 is displayed and the error cell is displayed in yellow (in the figure, It is represented by a thick frame.) In addition, the cell related to the job net name of the current job net is displayed in red (indicated by a thick frame in the figure). The cause of the error of the “expiration end date” of the current job is that the value (“December 31, 2005”) is earlier than the “expiration start date” (December 1, 2006). .

  Next, details of the process for displaying a non-displayed error cell in step S207 of FIG. 10 will be described. FIG. 13 is a flowchart for explaining a display process of non-displayed error cells.

  First, in steps S302 to S304, a loop process from the start line to the end line (that is, for the operand) on the setting sheet 400 (see FIG. 5) is executed (S301).

  That is, one row is taken out from the setting sheet 400, and it is determined whether or not the row (hereinafter referred to as “current row”) has passed the last row (S302). If the current line is not the last line (N in S303), it is determined whether or not “x” is set in the “display” item of the current line. When “x” is set in the “display” item (Y in S303), the column symbol registered in the “column” item of the current row is registered in the column symbol array (S304). Here, the column symbol array is an array variable for storing column symbols of operands that are not displayed. Therefore, when “◯” is set in the “display” item of the current line (N in S303), step S304 is not executed. When the process is completed up to the last line for the setting sheet 400 (Y in S302), it is determined in step S305 whether or not a column symbol is stored in the column symbol array. For example, based on the setting sheet 400 of FIG. 5, at this stage (S305), the contents of the column symbol array are as shown in FIG.

  FIG. 14 is a diagram illustrating an example of the contents of the column symbol array. In FIG. 14, a rectangle indicated by reference sign v2 indicates a column symbol arrangement. In the column symbol array v2, the elements of the array are separated by broken lines. The column symbol array v2 in FIG. 14 is generated based on the setting sheet 400 in FIG. 5. Therefore, in the setting sheet 400, the “display” item is “x”, “calendar name 5”, “shift” Column symbols (EB: EB, EE: EE, FA: FA) of “upper limit days” and “expiration date end date” are registered as values of the respective elements.

When no column symbol is stored in the column symbol array, that is, when there is no operand set as non-display on the setting sheet 400 (N in S305), a non-display error cell cannot exist. The process of FIG. 13 is terminated.

On the other hand, as shown in FIG. 14, when the column symbol is stored in the column symbol array (Y in S305), the error location storage variable shown in FIG. 11 is converted into the error location storage array (S306).
FIG. 15 is a diagram showing a state of conversion of an error location storage variable into an error location storage array.

  In FIG. 15, a rectangle indicated by reference sign v3 indicates an error location storage array. In the error location storage array v3, the elements of the array are separated by broken lines. That is, the process of step S306 is to set each cell address delimited by a comma in the error location storage variable v1 as a value of each element of the error location storage array v3 so that it can be easily processed later.

  Subsequently, in steps S308 to S316, loop processing for the number of elements in the error location storage array (hereinafter referred to as “first loop processing” only in FIG. 13) is executed (S307).

  First, one cell address is extracted from the error location storage array v3 (the cell address extracted here is hereinafter referred to as “current cell address” in FIG. 13 only), and whether or not the processing has been completed for all the cell addresses. Is determined (S308). If there is an unprocessed cell address (N in S308), it is determined whether or not the error operand related to the current cell address is hidden on the batch edit sheet 200 (S309). This determination is made not by referring to the setting sheet 400 but by checking the actual state on the batch edit sheet 200. That is, on the setting sheet 400, even an operand set as non-display may be displayed manually by the user.

  When the error operand related to the current cell address is not displayed on the batch edit sheet 200 (Y in S309), the loop processing for the number of elements of the column symbol array v2 in FIG. 14 in steps S311 to S316, that is, Then, the loop processing for the operands set as non-display on the setting sheet 400 (hereinafter referred to as “second loop processing” only in FIG. 13) is executed in the first loop processing (S310). As a result, it is searched whether there is any column symbol stored in the column symbol array that matches the current cell address (S312), and the matching column symbol (hereinafter referred to as "target column symbol"). Is retrieved (Y in S312), the error operand column relating to the current cell address is displayed in the batch edit sheet 200 (S313). Further, the value of the “display” item of the error operand in the setting sheet 400 is changed to “◯” (display) (S314), and the target column symbol is saved in the changed column symbol array (S315). That is, the column symbol of the operand whose “display” item is changed from “×” to “◯” in the setting sheet 400 is stored in the changed column symbol array. Subsequently, the name of the operand whose column symbol is saved in the changed column symbol array (for example, “the expiration date”) is stored in the operand storage variable. In the process of executing the second loop process, when a plurality of operand names are stored in the operand storage variable, each operand name is separated by a comma, for example.

  When the second loop processing is completed for the current cell address (Y in S311), the above processing is executed using the next cell address stored in the error location storage array as the current cell address. When the process is completed for all the cell addresses stored in the error location storage array (Y in S308), the first loop process is terminated and the process of FIG. 13 is terminated.

  Next, the process of changing the background color of the error cell that has been changed from the non-display state to the display state in step S208 in FIG. 10 will be described. FIG. 16 is a flowchart for explaining the processing procedure for changing the background color of the error cell that has been changed from the non-display state to the display state.

  First, similarly to step S306 in FIG. 13 (see FIG. 15), the error location storage variable is converted into an error location storage array (S401).

  Subsequently, in steps S403 to S407, a loop process for the number of elements in the error location storage array (hereinafter referred to as “first loop process” in FIG. 16 only) is executed (S402).

  First, one cell address is extracted from the error location storage array v3 (the cell address extracted here is hereinafter referred to as “current cell address”), and it is determined whether or not the processing has been completed for all the cell addresses ( S403). If there is an unprocessed cell address (N in S403), the number of elements of the changed column symbol array (array of error operand column symbols changed from non-display to display) generated in step S315 of FIG. A loop process (hereinafter referred to as “second loop process” only in FIG. 16) is executed in the first loop process (S404).

  Thus, it is searched whether there is any column symbol stored in the changed column symbol array that matches the current cell address (S406), and this column symbol (hereinafter referred to as “target column symbol”) is searched. ) Is retrieved (Y in S406), the background color of the cell associated with the current cell address is changed to yellow (S407).

  When the second loop processing is completed for the current cell address (Y in S405), the above processing is executed using the next cell address stored in the error location storage array as the current cell address. When the process is completed for all the cell addresses stored in the error location storage array (Y in S403), the first loop process is terminated and the process of FIG. 13 is terminated.

  10, 13, and 16, the details of the check processing of each operand of the current job net in step S <b> 112 of FIG. 9 have been described. However, the operand of each job belonging to the current job net in step S <b> 113 This check process can also be executed by the same processing procedure. In this case, when an error is detected for a certain job, information regarding the error is recorded in an array of job error information structures. The job error information structure includes, for example, the job net No. of the job net to which the job belongs. , Job No. , Job names, error IDs, and member variables such as error messages.

  The cell address of the error operand of the job in which the error is detected corresponds to the job in an array in which 255 elements are secured for each job net (hereinafter referred to as “error job cell address array”). Stored as element value.

  Next, details of the termination process in step S115 of FIG. 9 executed after the check process of all job nets and jobs belonging to the job net are executed will be described. FIGS. 17 and 18 are flowcharts for explaining the processing procedure of the finalizing process of the operand check process.

  First, it is determined whether the number of job nets defined in the batch edit sheet 200 is 300 and the value of the number of input lines after the blank line is 0 (S501). If there is (Y in S501), the value of the number of valid job nets is set to 300 (S502). If the determination in S501 is negative (N in S501), the number of valid job nets is the value set in step S109 in FIG.

  Subsequently, whether the number of elements in the array of the job net error information structure is not 0, or whether the number of elements in the array of the job error information structure is not 0, that is, job net check processing (S112 in FIG. 9). Alternatively, in the job check process (S113 in FIG. 9), it is determined whether an error operand is detected (S503). If an error operand has been detected for at least one of the job net and job (Y in S503), whether the number of elements in the array of the job error information structure is not 0 (that is, whether an error operand has been detected for the job) ) Is determined (S504).

  If the number of elements in the array of the job error information structure is not 0 (Y in S504), a loop process corresponding to the number of elements is executed in steps S506 to S508 (S505). That is, for each element (job error information structure) stored in the array of job error information structures (S506), a job net No. Is stored (S507), the job net No. is stored. Is stored (Y in S507), the job net No. is displayed on the batch edit sheet 200. The cell of “job information” in the row of the job net relating to is red. By doing so, it is possible to recognize that an error has occurred in any job belonging to the job net on the batch edit sheet 200.

  When the processing from S506 to S508 is completed for all the elements of the job error structure array (Y in S506), loop processing for the number of valid job nets is subsequently executed (S509). That is, for each valid job net, each element (first element to 255th element) of the error job cell address array associated with the job net is searched (S512, S513), and the cell address is stored. In this case (Y in S513), the same processing as in FIG. 13 is executed for the job information sheet 300 (S514). That is, in the job information sheet 300, when the operand related to the cell address is not displayed, the operand is displayed.

  When the processing from step S511 to S514 is completed for all job nets (Y in S510), an error message file is generated (S515), and an array of job net error information structures and jobs are generated for the generated error message file. The error message stored in the error information structure array is output and the content is displayed (S516). FIG. 19 is a diagram illustrating a display example of an error message file.

  If the display of the error message file has failed (Y in S517), an error message for notifying that is displayed (S518).

  Subsequently, in step S316 of FIG. 13 described above, the change to the “display” item of the setting sheet 400 is made by referring to the operand storage variable in which the name of the error operand changed from the non-display state to the display state is stored. The presence or absence is determined (S519). When the name of at least one operand is stored in the operand storage variable, that is, when the “display” item of the setting sheet 400 is changed, a message is displayed to notify the user to that effect (S520). .

  FIG. 20 is a diagram illustrating a display example of an error message notifying that an error operand that has not been displayed is displayed.

  In FIG. 20, the error dialog 600 shows that the value of the “display” item in the setting sheet 400 has been changed from “×” to “◯” for the error operand, and the name of the error operand (“expiration date has expired”) Day ") is displayed. By referring to such an error dialog 600, the user can easily confirm which operand has been changed from the non-display state to the display state. The name of the error operand is displayed based on the operand storage variable.

  If the determination in step S503 is negative (N in S503), the process proceeds to step S521 in FIG. 18 to check whether the number of elements in the job net error information structure array and the job error information structure array is zero. judge. When the number of elements is 0 (Y in S521), that is, when no error is detected for all operands, the definition information (values of each operand) in the batch edit sheet 200 is held in the memory (S522). The entire sheet is shaded (S523), and input protection is applied to the entire sheet (S524). This prevents an input due to a user's erroneous operation.

  On the other hand, if there is an error (N in S521), the process ends without executing steps S522 to S524. Therefore, in this case, input protection is not applied. Therefore, the user can correct the operand that has an error. This correction can also be made for error operands that were hidden but displayed upon error detection.

  FIG. 21 is a diagram illustrating a display example of a batch edit sheet with error operands corrected. In FIG. 21, the same components as those in FIG.

  In FIG. 21, the “expiration end date” of the job net in the second line, which was regarded as an error in FIG. 12, is corrected from “December 31, 2005” to “December 31, 2006”. After this correction, the user clicks the operand check button 204 again to re-execute the operand check process.

  In FIG. 10, the job net check process has been simplified for convenience. A more detailed example of the job net check process will be described below. FIG. 22 is a flowchart for explaining the processing procedure of the job net check process in detail.

  First, the job net name and job net name of the current operand are checked for errors, character number restrictions, etc. (S601). If there is an error (Y in S602), the job net name or the cell address of the job net name is stored in the error location storage variable (see FIG. 11) (S603). Subsequently, a check process (start condition check process) is executed for the operands constituting the start condition 212 in the job net information (S604). Details of the start condition check process will be described later. If an error is detected by the activation condition check process (Y in S605), it is determined whether the cell address of the error operand detected by the activation condition check process is stored in the error location storage variable (S606). When the cell address is stored in the error location storage variable, the background color of the cell related to the cell address is set to red, and the process of FIG. 22 is terminated.

  On the other hand, if no error is detected in the startup condition check process (N in S605), the “execution attribute”, “treatment when power is not turned on”, “treatment at startup”, and “predicted execution time” of the current job net. ”,“ Startup date bit pattern ”,“ Calendar name ”,“ Holiday shift ”,“ Shift upper limit days ”,“ Operation instruction ”,“ Carryover processing ”,“ Stop time ”,“ Default host name ”, etc. Is checked (S608), and the operand in which an error is detected (Y in S609) is stored in the error location storage variable (S610).

  Subsequently, it is determined whether a cell address is stored in the error location storage variable (S611). If the cell address is stored (Y in S611), the same processing as in steps S206 to S208 in FIG. 10 is executed in steps S612 to S614. That is, when the background color of the cell address is red (S612) and the operands that are not displayed are included in the error operands, the column (cell) related to the operands is displayed on the batch edit sheet 200. It is displayed (S613). Further, the background color of the cell of the error operand that is changed from the non-display state to the display state is changed to yellow (S614).

  Next, details of the activation condition check process in step S604 of FIG. 22 will be described. FIG. 23 is a flowchart for explaining the processing procedure of the activation condition check processing.

  First, it is determined whether or not a value is specified for each operand constituting the start condition 212 (S701). If a value is not specified (“not specified” in S701), error information is recorded in the array of the job net error information structure (S702), and a cell address whose value is not specified is stored in an error location storage variable ( S703). In this case, the activation condition check process returns an error and ends the process.

  On the other hand, when a value is specified for the operand that configures the start condition 212 (“designation” in S701), processing for checking the operand that configures the operation period 213 in the job information of the current job (hereinafter “operation period check process”). Is executed (S704). If an error is detected in the operation period check process (“error” in S704), the error is returned as the start condition check process, and the process ends. On the other hand, when no error is detected in the operation period check process (“normal” in S704), other various operands are initialized (S705), and normal termination is returned as the start condition check process.

  Next, details of the operation period check process in step S704 in FIG. 23 will be described. FIG. 24 is a flowchart for explaining the procedure of the operation period check process.

  First, check processing (hereinafter referred to as “operation period operand check process”) is performed for each operand (expiration date start date, expiration date end date, invalid expiration date start date, invalid expiration date end date) constituting the operation period 213. (S801). If an error is detected in the operation period operand check process (“error” in S801), the cell address where the error is detected is stored in the error location storage variable (S802), and the error is returned. On the other hand, if no error is detected (“normal” in S801), a normal end is returned.

  Next, details of the operation period operand check process in step S801 in FIG. 24 will be described. FIG. 25 is a flowchart for explaining the procedure of the operation period operand check process.

  First, it is determined whether or not the operand to be processed in FIG. 25 is an operand constituting the operation period 213 (whether it is an operand to be checked) (S901). If it is not the operand to be checked, record the error information in the job net error information structure array and return the error. On the other hand, if it is an operand to be checked, the validity of the value of the operand is checked (S903). If an error is detected as a result (Y in S903), error information is recorded in the array of job net error information structures, and the error is returned. On the other hand, if no error is detected, a normal end is returned.

  As described above, according to the job schedule creation program 11 in the present embodiment, even when an error occurs in a non-displayed data item (operand), the data item is automatically displayed. Therefore, the user can easily refer to and input the data item without manually displaying the data item.

  In addition, since the background color of the data item is displayed in a color (yellow) different from the color (red) when an error occurs in the previously displayed data item, the user does not display the data item. Can be easily recognized.

  As mentioned above, although the Example of this invention was explained in full detail, this invention is not limited to the specific embodiment which concerns, In the range of the summary of this invention described in the claim, various deformation | transformation * It can be changed.

Regarding the above description, the following items are further disclosed.
(Appendix 1)
On the computer,
A verification procedure for verifying values of the plurality of data items when at least some of the data items are hidden on an input screen capable of inputting a plurality of data items;
A determination procedure for determining whether or not a data item in which an error is detected in the verification procedure is hidden on the input screen;
A data item verification program for executing a data item display procedure for automatically displaying the data item on the input screen when it is determined that the data item in which the error is detected is not displayed .
(Appendix 2)
A setting procedure for setting display or non-display on the input screen for each of the data items;
In the determination procedure, based on whether the data item in which an error is detected in the verification procedure is included in the data item that is set to be hidden in the setting procedure, the data item in which the error is detected is The data item verification program according to appendix 1, wherein it is determined whether or not the input screen is hidden.
(Appendix 3)
The data item verification program according to appendix 1 or 2, wherein a display mode changing procedure for changing a display mode of a data item in which an error is detected in the verification procedure is executed.
(Appendix 4)
The data item displayed in the data item display procedure is subjected to a change different from the change in the display mode of the data item that is displayed in advance and in which an error is detected in the verification procedure. Supplementary item 3 data item verification program.
(Appendix 5)
The data item verification program according to any one of appendices 1 to 4, wherein a message display procedure for displaying a message including an identification name of the data item displayed in the data item display procedure is executed.
(Appendix 6)
A computer-readable recording medium on which the data item verification program according to any one of appendices 1 to 5 is recorded.
(Appendix 7)
A data item verification method executed by a computer,
A verification procedure for verifying values of the plurality of data items when at least some of the data items are hidden on an input screen capable of inputting a plurality of data items;
A determination procedure for determining whether or not a data item in which an error is detected in the verification procedure is hidden on the input screen;
A data item display procedure for automatically displaying the data item on the input screen when it is determined that the data item in which the error is detected is not displayed; Method of verification.
(Appendix 8)
A setting procedure for setting display or non-display on the input screen for each of the data items;
In the determination procedure, based on whether the data item in which an error is detected in the verification procedure is included in the data item that is set to be hidden in the setting procedure, the data item in which the error is detected is The data item verification method according to appendix 7, wherein it is determined whether or not the input screen is not displayed.
(Appendix 9)
9. The data item verification method according to appendix 7 or 8, wherein a display mode changing procedure for changing a display mode of a data item in which an error is detected in the verification procedure is executed.
(Appendix 10)
The data item displayed in the data item display procedure is subjected to a change different from the change in the display mode of the data item that is displayed in advance and in which an error is detected in the verification procedure. The data item verification method according to attachment 9.
(Appendix 11)
The data item verification method according to any one of appendices 7 to 10, wherein a message display procedure for displaying a message including the identification name of the data item displayed in the data item display procedure is executed.
(Appendix 12)
A verification means for performing verification of values of the plurality of data items when at least some of the data items are hidden on an input screen capable of inputting a plurality of data items;
Determination means for determining whether or not the data item in which an error is detected in the verification means is hidden on the input screen;
Data item display means for automatically displaying the data item on the input screen when it is determined that the data item in which the error is detected is hidden. Verification device.

It is a figure which shows the hardware structural example of the job schedule creation apparatus in embodiment of this invention. It is a figure which shows the example of a display of the batch edit sheet | seat which a job schedule creation program displays. It is a figure which shows the example of a display of the batch edit sheet | seat in which the job net was input. It is a figure which shows the example of a display of a job information sheet. It is a figure which shows the example of a display of a setting sheet. It is a flowchart for demonstrating the process outline | summary of the process which a job schedule creation program performs when an operand check button is pushed. It is a figure which shows the example of a display of the batch edit sheet | seat when there is no error in an operand check. It is a figure which shows the example of a display of the batch edit sheet | seat when a CSV output button is pushed. It is a flowchart for demonstrating the process sequence of an operand check process. It is a flowchart for demonstrating the process sequence of a job net check process. It is a figure which shows the example of the content of the error location storage variable. FIG. 10 is a diagram illustrating a display example of a batch edit sheet when an error operand is detected in job net check processing. It is a flowchart for demonstrating the display process of a non-displayed error cell. It is a figure which shows the example of the content of a column symbol arrangement | sequence. It is a figure which shows the mode of conversion to the error location storage array of an error location storage variable. It is a flowchart for demonstrating the process sequence of the change process of the background color of the error cell made into the display state from the non-display state. It is a flowchart for demonstrating the process sequence of the termination process of an operand check process. It is a flowchart for demonstrating the process sequence of the termination process of an operand check process. FIG. 10 is a diagram illustrating a display example of an error message file. It is a figure which shows the example of a display of the error message which notifies that the error operand which was not displayed was displayed. It is a figure which shows the example of a display of the batch edit sheet | seat in which the error operand was corrected. It is a flowchart for explaining the processing procedure of job net check processing in detail. It is a flowchart for demonstrating the process sequence of a starting condition check process. It is a flowchart for demonstrating the process sequence of an operation period check process. It is a flowchart for demonstrating the process sequence of an operation period operand check process.

Explanation of symbols

10 Job Schedule Creation Device 11 Job Schedule Creation Program 100 Drive Device 101 Recording Medium 102 Auxiliary Storage Device 103 Memory Device 104 Arithmetic Processing Device 105 Display Device 106 Input Device B Bus

Claims (5)

On the computer,
In a plurality of input can be input screen of the data item, and the verification procedure to perform the verification of the previous Symbol plurality of data items,
Based on each data item in the setting information storing display or hide on the screen, the verification data item an error is detected in step is a determination procedure for determining whether it is set non-displayed,
The error is detected if the data item that is set non-displayed, the data item verification program for executing a data item display procedure for displaying the data items to the entering force screen. Claim 1, wherein the data item validation program which have a setup procedure for setting the display or non-display of the input screen for each of said data items.   3. The data item verification program according to claim 1, wherein a display mode changing procedure for changing a display mode of a data item in which an error is detected in the verification procedure is executed.   The data item displayed in the data item display procedure is subjected to a change different from the change in the display mode of the data item that is displayed in advance and in which an error is detected in the verification procedure. The data item verification program according to claim 3.   The data item verification program according to any one of claims 1 to 4, wherein a message display procedure for displaying a message including an identification name of the data item displayed in the data item display procedure is executed.

Images